F.1 Concept maps

The following series of concept maps show module USE FROM connectivity and where Extensible select types are defined. The color coding is provided in Figure F.1.

F.2 Systems engineering concepts

The top level hierarchy of modules used to enable systems engineering concepts is shown in Figure F.2. Below this level of abstraction modules are extensively networked together. To see into this modules networking quagmire, modules have been grouped together relative to a few high level loosely defined natural language concepts. The grouping simply provides a visualization aid that the AP233 development team has found useful.

Capabilites that enable systems engineering concepts are realized by:

• items within the scope of application module Analysis assignment;
• items within the scope of application module Decision support;
• items within the scope of application module Function based behaviour;
• items within the scope of application module Functional breakdown;
• items within the scope of application module Issue management;
• items within the scope of application module Organization structure;
• items within the scope of application module Product data management;
• items within the scope of application module Program management;
• items within the scope of application module Project breakdown;
• items within the scope of application module Project management;
• items within the scope of application module Requirement management;
• items within the scope of application module Risk management;
• items within the scope of application module Schedule;
• items within the scope of application module State based behaviour;
• items within the scope of application module System behaviour;
• items within the scope of application module System modelling;
• items within the scope of application module System structure;
• items within the scope of application module Work structure.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity as realized - continued in Activity concepts figure F.3;
• items within the scope of application module Analysis assignment - continued in the How concepts figure F.6;
• items within the scope of application module Analysis characterized - continued in the How concepts figure F.6;
• items within the scope of application module Configuration item - continued in the System concepts figure F.13;
• items within the scope of application module External analysis representation - continued in the Activity concepts figure F.3;
• items within the scope of application module Function based behaviour - continued in the Behaviour concepts figure F.5;
• items within the scope of application module Group - continued in the Issue-Risk-Group concepts figure F.7;
• items within the scope of application module Justification - continued in the Authorization concepts figure F.4;
• items within the scope of application module Organization type - continued in the Who concepts figure F.18;
• items within the scope of application module Probability distribution - continued in the Representation concepts figure F.10;
• items within the scope of application module Product data management - continued in the Management resource information figure F.8;
• Project breakdown management resource information concepts - continued in the Management resource information figure F.8;
• items within the scope of application module Project management resource information - continued in the Management resource information figure F.8;
• items within the scope of application module Requirement management - continued in the Project concepts figure F.9;
• items within the scope of application module Risk management - continued in the Issue-Risk-Group concepts figure F.7;
• items within the scope of application module Schedule - continued in the Schedule concepts figure F.12;
• items within the scope of application module State based behaviour - continued in the Behaviour concepts figure F.5;
• items within the scope of application module System breakdown - continued in the System concepts figure F.13;
• items within the scope of application module System structure - continued in the System concepts figure F.13;
• System structure decomposition information concepts - continued in the System concepts figure F.13;
• items within the scope of application module System view definition - continued in the System concepts figure F.13;
• items within the scope of application module Verification and validation - continued in the How concepts figure F.6;
• items within the scope of application module Work order - continued in the Project concepts figure F.9.

F.3 Activity concepts

The modules and extensible select information items that are networked together to model activity concepts in AP233 are shown in Figure F.3.

Capabilites that enable activity concepts are realized by:

• items within the scope of application module Activity;
• items within the scope of application module Activity as realized;
• items within the scope of application module Activity method;
• items within the scope of application module Activity method assignment;
• items within the scope of application module Activity method implementation;
• items within the scope of application module Foundation state definition;
• items within the scope of application module Scheme;
• items within the scope of application module State definition;
• items within the scope of application module State observed;
• items within the scope of application module Task element;
• items within the scope of application module Task specification.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Condition - continued in the How concepts figure F.6;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Person organization assignment - continued in the Who concepts figure F.18;
• items within the scope of application module Time interval - continued in the When concepts figure F.16.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• activity_item is an item that can be assigned an activity;
• activity_method_item a product or activity data item to which an applied activity method can be assigned;
• activity_realization_select a product or activity data item that can realize an activity method;
• constraint_context a task element within which a constraint applies;
• scheme_entry_item_select a product or activity data item which can be associated with a scheme entry;
• scheme_subject_select a product or activity data item which can be associated with a scheme;
• scheme_version_select a product or activity data item which can be associated with a scheme version;
• state_definition_of_item an object whose mode of being (i.e. state) can be described and known by a state definition;
• state_of_item an activity or product data item which can have a state or be a state;
• task_item a product or activity item that can be associated with the representation of all or part of how to undertake a task.

F.4 Authorization concepts

The modules and extensible select information items that are networked together to model authorization concepts in AP233 are shown in Figure F.4.

Capabilites that enable authorization concepts are realized by:

• items within the scope of application module Approval;
• items within the scope of application module Certification;
• items within the scope of application module Contract;
• items within the scope of application module Information rights;
• items within the scope of application module Justification;
• items within the scope of application module Security classification.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Date time assignment - continued in the When concepts figure F.16;
• items within the scope of application module Foundation state definition - continued in the Activity concepts figure F.3;
• items within the scope of application module Management resource information - continued in the Management resource information figure F.8;
• items within the scope of application module Person organization - continued in the Who concepts figure F.18;
• items within the scope of application module State observed - continued in the Activity concepts figure F.3.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• approval_item an activity or product data item to which can be assigned an approval;
• assumed_itemthe item that is assumed to be true;
• assumption_itemthe item providing the context for the assumption;
• certification_item an activity or product data item to which a certification can be assigned;
• contract_item an activity or product data item to which can be assigned a contract;
• information_usage_right_item a set of information items to which a usage right can apply;
• justification_itema product or activity data item for which a justification can be provided;
• justification_support_item a product or activity data item which can provide evidential support for a justification;
• security_classification_item an activity or product to which a security classification can be assigned.

F.5 Behaviour concepts

The modules and extensible select information items that are networked together to model behaviour concepts in AP233 are shown in Figure F.5.

Capabilites that enable behaviour concepts are realized by:

• items within the scope of application module Behaviour description assignment;
• items within the scope of application module Behaviour identification and version;
• items within the scope of application module Behaviour view definition;
• items within the scope of application module Description assignment;
• items within the scope of application module External functional model;
• items within the scope of application module External state based behaviour model;
• items within the scope of application module Extended task element;
• items within the scope of application module Function based behaviour;
• items within the scope of application module Function based behaviour representation;
• items within the scope of application module State based behaviour;
• items within the scope of application module State based behaviour representation.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity method assignment - continued in the Activity concepts figure F.3;
• items within the scope of application module Alias identification - continued in the What concepts figure F.15;
• items within the scope of application module Collection identification and version - continued in the Issue, risk and group concepts figure F.7;
• items within the scope of application module Condition - continued in the How concepts figure F.6;
• items within the scope of application module Expression assignment - continued in the How concepts figure F.6;
• items within the scope of application module File identification - continued in the Why concepts figure F.19;
• items within the scope of application module Foundation representation - continued in the Representation concepts figure F.10;
• items within the scope of application module Foundation state definition - continued in the Activity concepts figure F.3;
• items within the scope of application module General model parameter - continued in the Representation concepts figure F.10;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Identification relationship - continued in the Where concepts figure F.17;
• items within the scope of application module Product version relationship - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition - continued in the What concepts figure F.15;
• items within the scope of application module Required resource - continued in the Resource concepts figure F.11;
• items within the scope of application module Resource property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Same as external item - continued in the Representation concepts figure F.10;
• items within the scope of application module Task element - continued in the Activity concepts figure F.3;
• items within the scope of application module Textual expression representation - continued in the Representation concepts figure F.10.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• behaviour_item the behaviour item whose behaviour is represented by the behaviour model;
• behaviour_model the behaviour model which is used to represent the behaviour of the a product or activity data item;
• description_item an item to which a description may be assigned.

F.6 How concepts

The modules and extensible select information items that are networked together to model how concepts in AP233 are shown in Figure F.6.

Capabilites that enable how concepts are realized by:

• items within the scope of application module Analysis assignment;
• items within the scope of application module Analysis characterized;
• items within the scope of application module Analysis identification;
• items within the scope of application module Condition;
• items within the scope of application module Condition evaluation;
• items within the scope of application module Expression;
• items within the scope of application module Expression assignment;
• items within the scope of application module Generic expression;
• items within the scope of application module Multi linguism;
• items within the scope of application module Numeric function;
• items within the scope of application module Verification and validation.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Approval - continued in the Authorization concepts figure F.4;
• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Contract - continued in the Authorization concepts figure F.4;
• items within the scope of application module Date time assignment - continued in the When concepts figure F.16;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Person organization assignment - continued in the Who concepts figure F.18;
• items within the scope of application module Product view definition - continued in the What concepts figure F.15;
• items within the scope of application module Product version relationship - continued in the How concepts figure F.6;
• items within the scope of application module Requirement assignment - continued in the Project concepts figure F.9;
• items within the scope of application module Security classification - continued in the Authorization concepts figure F.4.
• items within the scope of application module State observed - continued in the Authorization concepts figure F.1.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• analysed_item a product or activity data item to which an analysis can be assigned;
• condition_item a product or activity data item to which a condition can be assigned;
• condition_parameter_item a product or activity data item which acts as an input parameter to a condition which may or may not be specific;
• condition_evaluation_item a product or activity data item to which a condition evaluation can be applied;
• condition_evaluation_parameter_item a product or activity data item that can be an input parameter in the evaluation of a condition;
• expression_assignment_item an item to which an expression may be assigned;
• string_select a string that can be the considered instance in an attribute translation assignment;
• evidence_item the component data items used to support this evidence;
• validation_item the item which is been validated by this entity.

F.7 Issue-risk-group concepts

The modules and extensible select information items that are networked together to model issue, risk and group concepts in AP233 are shown in Figure F.7.

Capabilites that enable issue, risk and group concepts are realized by:

• items within the scope of application module Collection identification and version;
• items within the scope of application module Disposition;
• items within the scope of application module Group;
• items within the scope of application module Issue;
• items within the scope of application module Issue management;
• items within the scope of application module Risk definition;
• items within the scope of application module Risk management.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity method assignment - continued in the Activity concepts figure F.1;
• items within the scope of application module Approval - continued in the Authorization concepts figure F.4;
• items within the scope of application module Condition - continued in the How concepts figure F.6;
• items within the scope of application module Document assignment - continued in the Why concepts figure F.19;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Identification relationship - continued in the Where concepts figure F.17;
• items within the scope of application module Justification - continued in the Authorization concepts figure F.4;
• items within the scope of application module Observation - continued in the What concepts figure F.15;
• items within the scope of application module Person organization assignment - continued in the Who concepts figure F.18;
• items within the scope of application module Probability - continued in the Representation concepts figure F.10;
• items within the scope of application module Product relationship - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition relationship - continued in the What concepts figure F.15;
• items within the scope of application module Product version relationship - continued in the What concepts figure F.15.
• items within the scope of application module Property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Resource item - continued in the Resource concepts figure F.11;
• items within the scope of application module Same as external item - continued in the Representation concepts figure F.10;
• items within the scope of application module State definition - continued in the Activity concepts figure F.3.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• collection_assignment_select the object to which the collection has relevance;
• collection_member_select an object that represents a member of the collection;
• groupable_item a product or activity data item to which a group can be assigned;
• risk_impact_item a data item for which a risk impact can be assigned;
• risk_preception_source_item a data item for which a risk preception source can be assigned.

F.8 Management resource information concepts

The modules and extensible select information items that are networked together to model management resource information concepts in AP233 are shown in Figure F.8.

Capabilites that enable management resource information concepts are realized by:

• items within the scope of application module Management resource information;
• items within the scope of application module Product data management.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Alias identification - continued in the Where concepts figure F.17;
• items within the scope of application module Approval - continued in the Authorization concepts figure F.4;
• items within the scope of application module Certification - continued in the Authorization concepts figure F.4;
• items within the scope of application module Configuration effectivity - continued in the When concepts figure F.16;
• items within the scope of application module Contract - continued in the Authorization concepts figure F.4;
• items within the scope of application module Date time assignment - continued in the When concepts figure F.16;
• items within the scope of application module Document management - continued in the Why concepts figure F.19;
• items within the scope of application module Effectivity application - continued in the When concepts figure F.16;
• items within the scope of application module External class - continued in the Representation concepts figure F.10;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Incomplete data reference mechanism - continued in the What concepts figure F.15;
• items within the scope of application module Independent property representation - continued in the Representation concepts figure F.10;
• items within the scope of application module Multi linguism - continued in the How concepts figure F.6;
• items within the scope of application module Person organization - continued in the Who concepts figure F.18;
• items within the scope of application module Person organization assignment - continued in the Who concepts figure F.18;
• items within the scope of application module Position in organization - continued in the Who concepts figure F.18;
• items within the scope of application module Process property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Product group - continued in the What concepts figure F.15;
• items within the scope of application module Product relationship - continued in the What concepts figure F.15;
• items within the scope of application module Product structure - continued in the What concepts figure F.15;
• items within the scope of application module Product version relationship - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition properties - continued in the Representation concepts figure F.10;
• items within the scope of application module Project - continued in the Project concepts figure F.9;
• items within the scope of application module Security classification - continued in the Authorization concepts figure F.5;
• items within the scope of application module Selected item - continued in the Project concepts figure F.9;
• items within the scope of application module Time interval assignment - continued in the When concepts figure F.16;
• items within the scope of application module Work order - continued in the Project concepts figure F.9.

F.9 Project concepts

The modules and extensible select information items that are networked together to model project concepts in AP233 are shown in Figure F.9.

Capabilites that enable project concepts are realized by:

• items within the scope of application module Project;
• items within the scope of application module Project management resource information;
• items within the scope of application module Requirement assignment;
• items within the scope of application module Requirement identification and version;
• items within the scope of application module Requirement management;
• items within the scope of application module Requirement view definition;
• items within the scope of application module Requirement view definition relationship;
• items within the scope of application module Selected item;
• items within the scope of application module Work order;
• items within the scope of application module Work request;
• items within the scope of application module Work structure.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity - continued in the Activity concepts figure F.3;
• items within the scope of application module Activity method - continued in the Activity concepts figure F.3;
• items within the scope of application module Class - continued in the Where concepts figure F.17;
• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Collection identification and version - continued in the Issue, risk and group concepts figure F.7;
• items within the scope of application module Document assignment - continued in the Why concepts figure F.19;
• items within the scope of application module Document properties - continued in the Representation concepts figure F.10;
• items within the scope of application module Document structure - continued in the Why concepts figure F.19;
• items within the scope of application module Effectivity application - continued in the When concepts figure F.16;
• items within the scope of application module Event assignment - continued in the When concepts figure F.16;
• items within the scope of application module External class - continued in the Representation concepts figure F.10;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Identification relationship - continued in the Where concepts figure F.17;
• items within the scope of application module Information rights - continued in the Authorization concepts figure F.4;
• items within the scope of application module Person organization - continued in the Who concepts figure F.18;
• items within the scope of application module Position in organization - continued in the Who concepts figure F.18;
• items within the scope of application module Product version relationship - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition relationship - continued in the What concepts figure F.15;
• items within the scope of application module Same as external item - continued in the Representation concepts figure F.10;
• items within the scope of application module Product view definition properties - continued in the Representation concepts figure F.10;
• items within the scope of application module Property as definition - continued in the Representation concepts figure F.10;
• items within the scope of application module Same as external item - continued in the Representation concepts figure F.10;
• items within the scope of application module Schedule - continued in the Schedule concepts figure F.12.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• affected_item_select something that is affected by a work request;
• project_item an entity type that can be associated with a project;
• requirement_assignment_item the item which has the requirement assigned to it;
• requirement_satisfaction_item the item that satisfies the requirement;
• requirement_source_item the item which is the source of the requirement;
• selected_item_context_items the context in which the product or activity data is being identified as being a selected_item;
• selected_item_select the product or activity data that is being designated as a selected_item.

F.10 Representation concepts

The modules and extensible select information items that are networked together to model representation concepts in AP233 are shown in Figure F.10.

Capabilites that enable representation concepts are realized by:

• items within the scope of application module Analysis representation;
• items within the scope of application module Document properties;
• items within the scope of application module Extended measure representation;
• items within the scope of application module External analysis representation;
• items within the scope of application module External class;
• items within the scope of application module External source;
• items within the scope of application module Foundation representation;
• items within the scope of application module General model parameter;
• items within the scope of application module Independent property;
• items within the scope of application module Independent property representation;
• items within the scope of application module Measure representation;
• items within the scope of application module Name assignment;
• items within the scope of application module Parameter value specification;
• items within the scope of application module Probability;
• items within the scope of application module Probability distribution;
• items within the scope of application module Process property assignment;
• items within the scope of application module Product view definition properties;
• items within the scope of application module Property as definition;
• items within the scope of application module Property assignment;
• items within the scope of application module Qualified measure;
• items within the scope of application module Resource property assignment;
• items within the scope of application module Same as external item;
• items within the scope of application module Shape property assignment;
• items within the scope of application module Support resource;
• items within the scope of application module Textual expression representation;
• items within the scope of application module Value with unit.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity - continued in the Activity concepts figure F.3;
• items within the scope of application module Activity method - continued in the Activity concepts figure F.3;
• items within the scope of application module Assembly structure - continued in the What concepts figure F.15;
• items within the scope of application module Class - continued in the Where concepts figure F.17;
• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Document definition - continued in the Why concepts figure F.19;
• items within the scope of application module External model - continued in the What geometry concepts figure F.14;
• items within the scope of application module File identification - continued in the Why concepts figure F.19;
• items within the scope of application module Generic expression - continued in the How concepts figure F.19;
• items within the scope of application module Geometric model relationship - continued in the What geometry concepts figure F.14;
• items within the scope of application module Numeric function - continued in the How concepts figure F.6;
• items within the scope of application module Product view definition - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition relationship - continued in the What concepts figure F.15.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• assigned_name_select an item to which a name may be assigned;
• characterized_activity_definition an data item to which an activity property may be assigned;
• characterized_resource_select a resource data item which has a resource property that can be characterized;
• measure_value a data item that can be a measure value;
• parameter_value_select a product or activity data item for which a parameter can be provided;
• property_assignment_select a product data item which is not of entity type Representation or Representation_item and can be assigned a property;
• represented_definition specifies a role of the represented_definition for the Property_definition_representation;
• represented_proxy_select the item which is acting as a representation item;
• same_as_item the items in the dataset that are the same as the external item.

F.11 Resource concepts

The modules and extensible select information items that are networked together to model resource concepts in AP233 are shown in Figure F.11.

Capabilites that enable resource concepts are realized by:

• items within the scope of application module Required resource;
• items within the scope of application module Resource as realized;
• items within the scope of application module Resource item;
• items within the scope of application module Resource management.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Location assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Requirement identification and version - continued in the Project concepts figure F.9;
• items within the scope of application module Value with unit - continued in the Where concepts figure F.17.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• required_resource_item a product or activity data item to which a required resource can be assigned;
• resource_as_realized_item an entity that consumes a resource in its realization;
• resource_assignment_item a product or activity data item to which a resource item can be assigned;
• resource_item_select a reference to an item that satifies a resource requirement;
• resource_requirement_select a product or activity data item to which a required resource can be assigned.

F.12 Schedule concepts

The modules and extensible select information items that are networked together to model schedule concepts in AP233 are shown in Figure F.12.

Capabilites that enable schedule concepts are realized by:

• items within the scope of application module Schedule;
• items within the scope of application module Work output.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity method assignment - continued in the Activity concepts figure F.3;
• items within the scope of application module Activity method implementation - continued in the Activity concepts figure F.3;
• items within the scope of application module Attribute classification - continued in the Where concepts figure F.17;
• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Collection identification and version - continued in the Issue, risk and group concepts figure F.7;
• items within the scope of application module Condition evaluation - continued in the How concepts figure F.6;
• items within the scope of application module Document assignment - continued in the Why concepts figure F.19;
• items within the scope of application module Effectivity application - continued in the When concepts figure F.16;
• items within the scope of application module Identification relationship - continued in the Where concepts figure F.17;
• items within the scope of application module Information rights - continued in the Authorization concepts figure F.4;
• items within the scope of application module Justification - continued in the Authorization concepts figure F.4;
• items within the scope of application module Observation - continued in the What concepts figure F.15;
• items within the scope of application module Process property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Resource as realized - continued in the Resource concepts figure F.11;
• items within the scope of application module Resource property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Same as external item - continued in the Representation concepts figure F.10;
• items within the scope of application module Scheme - continued in the Activity concepts figure F.3;
• items within the scope of application module Task specification - continued in the Activity concepts figure F.3;
• items within the scope of application module Time interval assignment - continued in the When concepts figure F.16;
• items within the scope of application module Value with unit - continued in the Representation concepts figure F.10.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• work_item an item that can be a source that produces or delivers work output;
• work_output_item any product or activity data item that can be a representation of the item that is defined as work output (actual item or type of item).

F.13 System concepts

The modules and extensible select information items that are networked together to model system concepts in AP233 are shown in Figure F.13.

Capabilites that enable system concepts are realized by:

• items within the scope of application module Interface;
• items within the scope of application module Physical breakdown;
• items within the scope of application module Product environment definition;
• items within the scope of application module Product environment observed;
• items within the scope of application module System breakdown;
• items within the scope of application module System identification and version;
• items within the scope of application module System structure;
• items within the scope of application module System view definition;
• items within the scope of application module Zonal breakdown.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Assembly structure - continued in the What concepts figure F.15;
• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Collection identification and version - continued in the Issue, risk and group concepts figure F.7;
• items within the scope of application module Conditional effectivity - continued in the When concepts figure F.16;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Identification relationship - continued in the Where concepts figure F.17;
• items within the scope of application module Location assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Product breakdown - continued in the What concepts figure F.15;
• items within the scope of application module Product data management - continued in the Management resource information figure F.8;
• items within the scope of application module Product group - continued in the What concepts figure F.15;
• items within the scope of application module Product identification - continued in the What concepts figure F.15;
• items within the scope of application module Product version - continued in the What concepts figure F.15;
• items within the scope of application module Product version relationship - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition relationship - continued in the What concepts figure F.15.
• items within the scope of application module Same as external item - continued in the Representation concepts figure F.10;

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• connector_on_item a product item for which an Interface_connector_occurrence can provide an interface capability;
• environment_item the product that is or planned to be operating in the environment;
• in_zone_item an item that can exist in a zone;
• observed_environment_item the product that is or was operating in the environment.

F.14 What geometry concepts

The modules and extensible select information items that are networked together to model what geometry concepts in AP233 are shown in Figure F.14.

Capabilites that enable what geometry concepts are realized by:

• items within the scope of application module Contextual shape positioning;
• items within the scope of application module Elemental geometric shape;
• items within the scope of application module External model;
• items within the scope of application module Geometric model relationship;
• items within the scope of application module Single part representation.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Document assignment - continued in the Why concepts figure F.19;
• items within the scope of application module Extended measure representation - continued in the Representation concepts figure F.10;
• items within the scope of application module File identification - continued in the Why concepts figure F.19;
• items within the scope of application module Foundation representation - continued in the Representation concepts figure F.10;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Part view definition - continued in the What concepts figure F.15;
• items within the scope of application module Person organization assignment - continued in the Who concepts figure F.18;
• items within the scope of application module Property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Shape property assignment - continued in the Representation concepts figure F.10.
• items within the scope of application module Support resource - continued in the Representation concepts figure F.10.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• template_definition_select the value from template_definition_select.

F.15 What concepts

The modules and extensible select information items that are networked together to model what concepts in AP233 are shown in Figure F.15.

Capabilites that enable what concepts are realized by:

• items within the scope of application module Assembly structure;
• items within the scope of application module Configuration item;
• items within the scope of application module Incomplete data reference mechanism;
• items within the scope of application module Observation;
• items within the scope of application module Part and version identification;
• items within the scope of application module Part definition relationship;
• items within the scope of application module Part view definition;
• items within the scope of application module Product as individual;
• items within the scope of application module Product breakdown;
• items within the scope of application module Product concept identification;
• items within the scope of application module Product group;
• items within the scope of application module Product identification;
• items within the scope of application module Product relationship;
• items within the scope of application module Product replacement;
• items within the scope of application module Product structure;
• items within the scope of application module Product version;
• items within the scope of application module Product version relationship;
• items within the scope of application module Product view definition;
• items within the scope of application module Product view definition relationship.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity as realized - continued in the Activity concepts figure F.3;
• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Contextual shape positioning - continued in the What geometry concepts figure F.14;
• items within the scope of application module Document definition - continued in the Why concepts figure F.19;
• items within the scope of application module Effectivity application - continued in the When concepts figure F.16;
• items within the scope of application module Identification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Management resource information - continued in the Management resource information figure F.8;
• items within the scope of application module Property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Single part representation - continued in the What geometry concepts figure F.14;
• items within the scope of application module Work order - continued in the Project concepts figure F.9;
• items within the scope of application module Value with unit - continued in the Representation concepts figure F.10.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• breakdown_item a product or activity data item that can be related to a View_definition_relationship or Product_view_definition in a product breakdown;
• observation_recorder a product or a person data item capable of being identified as recording observational information (e.g. an identifiable piece of equipment capable of being represented as a Product_as_realized);
• observation_item a data item capable of being the subject of an observation;
• observed_context a data item serving as the context in which an observation is made;
• product_item General: a product item that may be related to items in a breakdown via a product_definition_element_relationship. Specific: a View_definition_relationship or Product_view_definition that is related to the Breakdown_element_definition or a Breakdown_element_usage;
• product_select a product or activity data item that can be idetentified as a member of a product group.

F.16 When concepts

The modules and extensible select information items that are networked together to model when concepts in AP233 are shown in Figure F.16.

Capabilites that enable when concepts are realized by:

• items within the scope of application module Conditional effectivity;
• items within the scope of application module Configuration effectivity;
• items within the scope of application module Date time;
• items within the scope of application module Date time assignment;
• items within the scope of application module Effectivity;
• items within the scope of application module Effectivity application;
• items within the scope of application module Event;
• items within the scope of application module Event assignment;
• items within the scope of application module Time interval;
• items within the scope of application module Time interval assignment.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Assembly structure - continued in the What concepts figure F.15;
• items within the scope of application module Condition - continued in the How concepts figure F.6;
• items within the scope of application module Configuration item - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition relationship - continued in the What concepts figure F.15;
• items within the scope of application module Value with unit - continued in the Representation concepts figure F.10.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• date_or_date_time_item an activity or product data item to which can be assigned a calendar date or a calendar data with time;
• effectivity_item an activity or product data item which has an effectivity (a domain of applicability) that can be characterized;
• event_item a product or activity data item to which an event can be assigned;
• time_interval_item an activity or product data item to which can be associated a time interval.

F.17 Where concepts

The modules and extensible select information items that are networked together to model where concepts in AP233 are shown in Figure F.17.

Capabilites that enable where concepts are realized by:

• items within the scope of application module Alias identification;
• items within the scope of application module Attribute classification;
• items within the scope of application module Class;
• items within the scope of application module Classification assignment;
• items within the scope of application module Identification assignment;
• items within the scope of application module Identification relationship;
• items within the scope of application module Location;
• items within the scope of application module Location assignment;

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Person organization - continued in the Who concepts figure F.18;
• items within the scope of application module Product version - continued in the What concepts figure F.15;
• items within the scope of application module Value with unit - continued in the Representation concepts figure F.10.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• alias_identification_item a data item to which an identification assignment can be made using an alias;
• classified_attribute_select an assertion that a data item has an attribute that is assigned to be a member of a class;
• classification_item a product or activity data item for which a class can be assigned to classify it;
• identification_item a data item to which an identification assignment can be made;
• location_assignment_select an entity that can be assigned to a specified location;
• product_based_location_representation a product data item that can provide the context for a location that can be specified.

F.18 Who concepts

The modules and extensible select information items that are networked together to model who concepts in AP233 are shown in Figure F.18.

Capabilites that enable who concepts are realized by:

• items within the scope of application module Experience;
• items within the scope of application module Organization type;
• items within the scope of application module Person organization;
• items within the scope of application module Person organization assignment;
• items within the scope of application module Position in organization;
• items within the scope of application module Qualifications;
• items within the scope of application module Type of person.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Activity as realized - continued in the Activity concepts figure F.3;
• items within the scope of application module Certification - continued in the Authorization concepts figure F.4;
• items within the scope of application module Classification assignment - continued in the Where concepts figure F.17;
• items within the scope of application module Date time assignment - continued in the When concepts figure F.16;
• items within the scope of application module Project - continued in the Project concepts figure F.9;
• items within the scope of application module Property assignment - continued in the Representation concepts figure F.10;
• items within the scope of application module Resource as realized - continued in the Resource concepts figure F.11.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• defined_activities an activity data item capable of being a defined activity;
• defined_attributes a product or activity item that can be a required attribute of a person;
• defined_methods a product or activity item that can be a required attribute of a person;
• person_or_organization_or_person_in_organization_select a person, organization or person in organization that can gain an experience;
• organization_or_person_in_organization_item an activity or product data item to which an organization or person in an organization can be assigned;
• position_context_item a position capable of being used by an organization to enable a person to fulfill a function or job;
• position_group_item a position group that can be associated with a product or activity data item;
• position_item position that can be associated with a product or activity data item;
• position_person_or_organization_or_person_in_organization_select a person or organization capable of holding a position;
• position_type_item a product or activity data item to which a position type can be assigned;
• qualifications_select people, organizations or people in organizations to which qualifications can be assigned;
• type_of_person_item_select a product or activity item to which a type of person can be assigned.

F.19 Why concepts

The modules and extensible select information items that are networked together to model why concepts in AP233 are shown in Figure F.19.

Capabilites that enable why concepts are realized by:

• items within the scope of application module Document and version identification;
• items within the scope of application module Document assignment;
• items within the scope of application module Document definition;
• items within the scope of application module Document management;
• items within the scope of application module Document structure;
• items within the scope of application module External item identification assignment;
• items within the scope of application module File identification.

Additionally these modules USE FROM several foundational modules that enable common ISO 10303 project concepts:

• items within the scope of application module Document properties - continued in the Representation concepts figure F.10;
• items within the scope of application module Management resource information - continued in the Management resource information figure F.8;
• items within the scope of application module Product version - continued in the What concepts figure F.15;
• items within the scope of application module Product view definition - continued in the What concepts figure F.15.

Extensible select types provide the cross coupling of concepts needed to realize the whole:

• documented_element_select a product data item to which a document can be assigned that provides information about that product data;
• external_identification_item an external product or activity data item whose source can be identified.

F.20 Extensible type select lists

The problem of creating extensible type lists has proven to be an extreme challenge. To explain what has been done a publish and subscribe analogy is used.

Schemas enable foundational capability that may be at the atomic or macro-molecular level. Schemas enable capabilities via entities that other capabilities can access by "subscription". The extensible type is the subscription list name. The list itself identifies all subscribers (entities).

The problem in STEP is that these lists are defined within schemas that have a domain bounded by the capabilities of all schemas in its USE FROM list and those lists that it inherits. On the bottom line, this creates a list creation problem that is 3 dimensional. The dimensions are: bounded domain, entities and extensible types. To size this, AP233 has about 10 major bounded domains, 1000 entities and 100 extensible types. If one does not apply any organizational logic to the problem this implies a need for 1,000,000 yes/no cognitive decisions to fully resolve the AP233 type extend problem.

In order to penetrate this problem some logical approach to scalability and checkability was required. This has lead to the concept based groupings shown in these Annex F concept maps. These groupings enable the type extend problem to be broken down into scalable and checkable pieces that can be easily aggregated to create the desired whole.

F.21 Harmonizing Extensible type select lists with others

Entries into the type extend lists stem from two primary needs; namely, harmonization with STEP APs relevant to AP233 and satisfaction of AP233 needs. The first group of extends needed for harmonization are derived from the extend lists used within the following STEP modules - not used by AP233:

• 1272 - activity_characterized;
• 1280 - required_resource_characterized;
• 1281 - resource_item_characterized;
• 1282 - resource_management_characterized;
• 1283 - resource_as_realized_characterized;
• 1285 - work_request_characterized;
• 1286 - work_order_characterized;
• 1289 - ap239_management_resource_information;
• 1292 - ap239_product_definition_information;
• 1293 - ap239_part_definition_information;
• 1295 - ap239_properties;
• 1296 - condition_evaluation_characterized;
• 1298 - activity_method_characterized;
• 1301 - work_output_characterized;
• 1306 - ap239_task_specification_resourced;
• 1307 - ap239_work_definition;
• 1628 - design_product_data_management.

NOTE    A large repository of information relevant to users and implementers of the STEP capabilities used in common by Ap239 and 80% of AP233 is at http://docs.oasis-open.org/plcs/dexlib/oasis_cover.htm.

© ISO 2011 — All rights reserved