The abstract PLM_object class is introduced to provide a mechanism of binding a unique identifier to each PLM class instance. These identifiers must be valid and unique through-out a complete session defined by the computational model. After each session the identifiers may are invalid. The PLM_object_relation is used to relate a PLM_object with a certain role. An Activity is the identification of the occurrence of an action that has taken place, is taking place, or is expected to take place in the future. The procedure executed during that Activity is identified with the Activity_method that is referred to by the chosen_method attribute. EXAMPLE Change, distilling, design, a process to drill a hole, and a task such as training someone, are examples of activities. NOTE 1 Status information identifying the level of completion of each activity may be provided within an instance of Activity_status. NOTE 2 The items that are affected by an Activity, for example as input or output, may be identified within an instance of Applied_activity_assignment. id: the identifier that distinguishes the Activity. name: the label by which the Activity is known. description: the text that provides further information about the Activity. The value of the attribute need not be specified. chosen_method: the Activity_method that specifies the procedure selected to carry out the Activity. An Activity_actual is a type of Activity. It is a record of the occurrence of an Activity. The Activity_actual is related through an Activity_happening to the Activity for which it is an occurrence. The existence of an Activity_actual instance means that the Activity_actual has started. NOTE 1 A Calendar_date or Date_time should be assigned to the Activity_actual with the role "start date" to record when the activity started. NOTE 2 A Calendar_date or Date_time may be assigned to the activity with role "end date" to record when the activity finished. In general, the absence of this assignment cannot be used to infer that the activity is continuing, only that the end of the activity has not yet been recorded. NOTE 3 A more detailed history of the progress of an activity may be recorded by applying states to the activity, but the meaning of these states must be defined through local business rules. An Activity_happening is a type of Activity_relationship. It is a relationship between the definition of an activity (predicted) and its actual occurrence (actual). NOTE 1 The ordinary value for name may be "actual", though this is redundant. NOTE 2 Many Activity_actuals may be the actual for a single Activity. EXAMPLE 1 a single defined activity is recorded historically by several sub-activities. NOTE 3 A single Activity_actual may fulfil several activities. EXAMPLE 2 a single servicing activity takes the opportunity to make additional checks and repairs. An Activity_method is a way to carry out an Activity. NOTE 1 There may be more than one method for producing a required result NOTE 2 This definition may be used to characterize a way to resolve a request for action. The concept of action request is dealt with in module Work request. name: the words by which the Activity_method is known. description: the text that provides further information about the Activity_method. The value of this attribute need not be specified. consequence: the text that describes the results of application of this method. The value of this attribute need not be specified. EXAMPLE an Activity_method is a test that consists of several steps; each may have a positive or negative result. purpose: the text that provides an informal description of the reason for the Activity_method . An Activity_method_relationship is a relationship between two instances of Activity_method. Name: the word or group of words by which the Activity_method_relationship is known. description: the text that provides further information about the Activity_method_relationship. The value of this attribute need not be specified. relating_method: the first instance of Activity_method that is part of the relationship. NOTE 1 The relating_method usually identifies the activity the definition of the related_method is based on, for example, derived from or dependent on. NOTE 2 The meaning of this attribute is defined by the name attribute. related_method: the other instance of Activity_method that is part of the relationship. NOTE 3 The related_method usually identifies the Activity_method, which is based on the definition of the relating_method. An Activity_relationship is a relationship between two instances of Activity. EXAMPLE The activity required to complete a work order, may be decomposed into a series of activities. Their corresponding instances would be related using instances of the Activity_relationship entity. name: the text by which the Activity_relationship is known. description: the text that provides further information about the Activity_relationship. The value of the attribute need not be specified. relating_activity: the first of the instances of Activity that is part of the relationship. NOTE 1 The relating_activity usually identifies the activity the definition of the related_activity is based on, for example, derived from or dependent on. NOTE 2 The meaning of this attribute is defined by the name attribute. related_activity: the second instance of Activity that is part of the relationship. NOTE 3 The related_activity usually identifies the Activity, which is based on the definition of the relating_activity. NOTE 4 The meaning of this attribute is defined by the name attribute. An Activity_status is the assignment of a status to an Activity . assigned_activity: the Activity to which the Activity_status applies. status: the label that provides a user interpretable designation for the level of completion of the Activity. An Advisory_task_step is a type of Task_step. It conveys information. NOTE Some Task_methods may not require any action to be undertaken. EXAMPLE "Beware of hot exhausts", "do not use tool X this way" and similar messages. An Alias_identification is a type of Identification_assignment that provides an alias identifier to product or activity data. NOTE 1 The alias identifier is conveyed within the identifier attribute inherited from Identification_assignment. NOTE 2 Information about the organizational scope in which the alias applies may be provided by a specialization of Organization_or_person_in_organization_assignment. NOTE 3 Alias identification only applies to concepts that possesses an attribute that conveys an identifier. An And_state_cause_effect_definition is a type of State_cause_effect_definition. It relates one or more causing State_definition entities and one effect State_definition. All the causing State_definition entities must exist prior to the single effect. An Applied_activity_assignment is an association of an Activity with product or activity data. It characterizes the role of the concepts represented with these data with respect to the activity. NOTE This entity should not be used to represent the association of an activity with the organizations that are responsible for its execution or its management. That kind of information can be represented with instances of Organization_or_person_in_organization_assignment . assigned_activity: the Activity that is considered. items: the items that are associated with the assigned_activity. role: the text that specifies the purpose of the association of the Applied_activity_assignment with product or activity data. Where applicable, the following values shall be used for role: 'input': the concepts represented by the items are inputs of the Activity; 'output': the concepts represented by the items result from the Activity; 'constraint': the concepts represented by the items influence the execution of the Activity. EXAMPLE Presence of a gas tube may constrain the execution of drilling of a hole. An Applied_activity_method_assignment is an association of an Activity_method with product or activity data. assigned_activity_method: the Activity_method that is to be associated with product or activity data. items: the set of data associated to the assigned_activity_method. role: the text that specifies the purpose of the association of the Applied_activity_method_assignment with product or activity data. An Applied_state_assignment is a relationship that allows a subject to have State or to be in a State. described_state: a State the subject has or is in. assigned_to: the subject which has or is in a State. role: the purpose of the association of the Applied_state_assignment with product or activity data. An Applied_state_definition_assignment is a mechanism that enables an object to have or to be in a State_definition. described_state_definition: the State_definition that is assigned. assigned_to: the object whose State_definition is given by the described_state_definition. role: the purpose of the association of the Applied_state_definition_assignment with product or activity data. An Approval is a formal confirmation of the quality of some activity or product data. status: the Approval_status that provides a user interpretable designation of the level of approval. purpose: the text that completes the information provided within the status attribute, specifying the reason or goal of the Approval. EXAMPLE 'released for production' or 'preliminary design completed' are approval purposes. planned_date: the point in time when the Approval is or was supposed to be performed. The value of this attribute need not be specified. public Modules.date_time1010.date_or_date_time_select planned_date; actual_date: the point in time when the Approval actually became valid. The value of this attribute need not be specified. public Modules.date_time1010.date_or_date_time_select actual_date; An Approval_assignment is the assignment of an Approval to activity or product data. assigned_approval: the Approval that is assigned with activity or product data. items: the activity or product data to which the Approval is assigned. role: the text that precises the role of the Approval with respect to the items it is assigned to. The value of this attribute need not be specified. EXAMPLE 'legal requirement' is an example of role that may be used to represent the fact that a particular approval addresses a legal requirement for a product. An Approval_relationship is a typed association between two instances of Approval. relation_type: the text that specifies the meaning of the relationship. Where applicable, the following values shall be used: 'decomposition': The Approval_relationship defines a relationship where the related Approval is one of the components into which the relating Approval is broken down with no implication of 'sequence' or 'dependency'; 'dependency': The Approval_relationship defines a relationship where the issuing of the related Approval is dependent on the issuing of the relating Approval; 'precedence': the Approval_relationship defines a relationship where the related Approval has higher priority than the relating Approval; 'sequence': The Approval_relationship defines a relationship where the relating Approval shall be completed before the related Approval is given. NOTE The value 'dependency' does not imply the semantics of the the values 'decomposition' or 'sequence'. EXAMPLE 1 The Approval of an assembly may be dependent on the Approval of all of the constituents of the assembly. EXAMPLE 2 In parallel approval processes of two assemblies, assignment of an Approval on one of the assemblies may depend on an Approval assigned to the second assembly. description: the text that provides further information about the Approval_relationship. The value of this attribute need not be specified. relating_approval: one of the Approval objects that is a part of the relationship. related_approval: the other of the Approval objects that is a part of the relationship. If one element of the relationship is dependent of the other, this attribute shall be the dependent one. An Approval_status is a particular rank of approval. status_name: the text by which the Approval_status is designated. EXAMPLE 'approved' and 'disapproved' are examples of Approval_status. An Approving_person_organization is an association between an Approval and the organization or person and organization that has granted this approval. person_organization: the Organization or the Person_in_organization that has granted the approval. approval_date: the point in time when the Approval has been given. This attribute need not be specified. authorized_approval: the Approval that has been given by the considered person or the organization. role: the text that specifies the role of the considered person or organization with respect to the approval. The value of this attribute need not be specified. By default, the person or organization shall only be considered as an approver without any specific role. EXAMPLE 'quality insurance auditor', 'production cost examiner' are examples of values of role of persons or organizations with respect to approvals assigned to product data. An Assembly_component_relationship is a type of View_definition_usage. It identifies a possibly quantified usage of a product version as a component of another product version. The relationship is established between two instances of Product_view_definition. The inherited attribute relating_view identifies the Product_view_definition of the assembly. The inherited attribute related_view identifies the Product_view_definition of the product version that plays the role of component. The Assembly_component_relationship specifies that, in the initial_context of the Product_view_definition that is referred to as relating_view, it is considered that the product version that is indirectly identified with the related_view attribute, is a component of the product version that is indirectly identified with the relating_view attribute. NOTE 1 In another context, the structure of the assembly may be described differently, adding, for example, an intermediate level between the products. NOTE 2 This entity data type may be used to establish assembly relationships during design or to represent the composition of an assembly existing in the real world. NOTE 3 An Assembly_component_relationship identifies an item in a parts list. Should the quantity be zero, the component would still be listed in the parts list. In case the component is a part, the following additional specifications apply: the quantity attribute shall either be not specified or shall characterize a number of occurrences of the component; if the quantity attribute specifies a number of occurrences, these occurrences shall be considered as a single group within the assembly structure; if the quantity attribute is not specified, the relationship actually identifies a single occurrence of the component. In case the component is a non-countable material, the following additional specifications apply: the quantity attribute shall either be not specified or shall characterize the amount of the material used as component; if the quantity attribute is not specified, the amount of material used as component shall be considered as unknown. EXAMPLE An assembly may require inclusion of ten grams of grease. NOTE 4 This version of the Assembly structure module does not enable to represent the fact that the quantity of a fluid component is, for example 'at most 10 grams' or 'between 5 or 20 grams'. However, some ISO 10303 application protocols, for example ISO 10303-214, provide a representation for those requirements. An Assembly_component_relationship shall be either a Next_assembly_usage, a or a Component_upper_level_identification. quantity: the Value_with_unit that defines the amount of this usage of the component in the assembly. This attribute need not be specified. location_indicator: the text that identifies this usage of the component in the assembly in a diagram, list, chart, or on a physical piece of equipment. This attribute need not be specified. An Assigned_property is a property that is assigned to product data. NOTE The mapping provided for that entity and for its attribute described_element is incomplete. It needs to be completed in any module that uses this module and extends the type property_assignment_select. id: the text that provides further an identifier for the Assigned_property. The value of this attribute need not be specified. name: the string that specifies the kind of property. description: the text that provides further information about the property. The value of this attribute need not be specified. A Class is a number of things considered together. A Composition_of_state is a type of state relationship and it relates the nature of states in relation to one another, where two or more State parts compose a whole State; and furthermore, whole states can become parts of yet another whole State. A Composition_of_state_definition is a type of State_definition_relationship. It relates State_definition entities to one another, when two or more State_definition entities act as parts to compose a whole State_definition; and furthermore, whole State_definition entities can become parts of yet another whole State_definition. A Concurrent_elements is a type of Structured_task_element that comprises a set of actions to be performed during the time required for the longest task. No specific order is required. A Condition is a definition of the precedent that must be fulfilled before a statement or relationship becomes valid. NOTE The condition is defined as a text based expression that is represented by the description attribute. The parameters against which the condition is to be evaluated are identified by Condition_parameter. The target or consequence of a condition is represented by Condition_assignment. EXAMPLE "If the engine has been running for 10000 hours then it requires a service" is an example of a conditional statement. The conditional part of the statement is "If the engine has been running for 10000 hours" which is stored in definition attribute on Condition. The parameter or subject of the condition is "the engine" which is represented by a Condition_parameter identifying the Product_as_realized which represents the engine. The consequence of the condition is "then it requires a service". This is represented by Condition_assignment identifying the task to perform the service, a Task_method. name: the words by which a Condition is known. description: the text that provides further information about the Condition. The value of the attribute need not be specified. A Condition_assignment is a relationship that identifies the statement or relationship to which a Condition applies. EXAMPLE Condition 29 applies to the relationship between a Saab 9.3 car and the activity of checking the oil level on that make of car. assigned_condition: the Condition that is being assigned. item: the product or activity data to which the Condition is being assigned. A Condition_parameter is a represention of the product or activity data that is used to specify a Condition. EXAMPLE Oil pressure on gauge 3. NOTE The product or activity data is defined in condition_parameter_item. The contents of this select type are defined in application modules that use this module. name: the words by which a Condition_parameter is known. description: the text that provides further information about the Condition_parameter. The value of the attribute need not be specified. condition: the Condition for which the parameter is an input. parameter: the product or activity data which acts as a parameter to the condition. The value of this attribute need not be specified. A Condition_relationship is a relation between two conditions. NOTE The Condition_relationship normally represents a logical combination of conditions. The logical type is identified by the classification of the Condition_relationship by a Classification_assignment. EXAMPLE "If the engine has been running for 10000 hours AND the engine is fitted with a clog-up-quick Oil filter then change the oil filter" is an example of two conditions related by a logical AND. name: the words by which the Condition_relationship is known. description: the text that provides further information about the Condition_relationship. The value of the attribute need not be specified. relating_condition: one of the instances of Condition that is a part of the relationship. related_condition: the other instance of Condition that is part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one. A Dated_effectivity is a type of Effectivity for which the domain of applicability is defined as an interval of time bounded by dates or events. The interval may be open-ended. EXAMPLE Events may be used to bound a Dated_effectivity period, at planning phase. Depending on whether the end_bound attribute is specified, the actual domain of time defined by a Dated_effectivity is: either, the time interval between the start and end date or event; or, the open time interval that starts at the start date or event. If the end_bound is an event that actually identifies a point in time that comes before the start_bound, then the actual domain of effectivity is empty. IP1: If both attributes are specified with dates, the end_bound shall be greater than the start_bound. start_bound: the date or event that defines the lower bound of the interval of applicability. A Decision_point is a type of Structured_task_element. It requires a decision that determines which further Task_element is to be followed. NOTE The condition on which the decision is based optionally allows a further Task_element to be invoked to provide the basis for the decision. condition: the criterion to be tested in order to make a decision. true_case_element: the Task_element to be performed if the test condition is satisfied. The value of this attribute need not be specified. false_case_element: the Task_element to be performed if the test condition is not satisfied. The value of this attribute need not be specified. unknown_case_element: the Task_element to be performed if the test condition can not be evaluated or returns unknown. The value of this attribute need not be specified. A Defined_state_relationship is a relationship that links a State_assertion to a State_assessment. name: the words by which the Defined_state_relationship is known. description: the text that provides further information about the Defined_state_relationship. The value of this attribute need not be specified. definitive_state: the State_assertion being related to the defined subject State from State_assessment. defined_state: the State_assessment being related to the definitive subject State from State_assertion. A Digital_file is a type of File. A Digital_file contains computer interpretable data and is stored on an electronic device. A Directed_activity is a type of Activity. It identifies an actvity that is governed by a Work_order. Business Object specifics A Document is a type of Product used to identify documentation data that is under configuration change management. A Document_assignment is a mechanism to associate a document with product data, where the assigned document provides information about the data with which it is associated. assigned_document: the Document, Document_version, Digital_document_definition or File that is used to provide information. is_assigned_to: the documented_element_select for the Document_assignment. role: the text that provides the meaning of the Document_assignment. EXAMPLE 'additional information': The assigned document provides information that is relevant for the associated object, but is not a description of the associated object itself; 'behavior': The assigned document specifies information about the behavior of the associated object; 'description': The assigned document provides textual information for the associated object itself; 'informative': The assigned document may or may not be considered; 'mandatory': The associated object shall conform to the content of the assigned document; 'mathematical description': The assigned document specifies the associated object by providing the algorithmic specification of its behavior. A Document_version is a type of Product_version. A Document_version identifies a particular version of a document. An Effectivity is the identification of a domain of applicability. NOTE Instances of Effectivity may be applied to any kind of product or activity data, using the constructs defined in the Effectivity application module. id: the identifier that distinguishes the Effectivity. name: the text by which the Effectivity is known. description: the text that characterizes the Effectivity. The value of the attribute need not be specified. An Effectivity_assignment is the association of an Effectivity with product or activity data. assigned_effectivity: the instance of the Effectivity entity that is assigned. role: the text that specifies the purpose of the association of the Effectivity with items. For an Effectivity that identifies a period of time, if applicable, the following values shall be used: 'actual': The assigned_effectivity defines a period of time during which the associated items are or were effective; 'planned': The assigned_effectivity defines a period of time during which the associated items are or were expected to be effective; 'required': The assigned_effectivity defines a period of time during which the associated items are or were required to be effective. items: the set of effectivity_item whose effectivity is characterized by this entity. An Element_constraint is a type of Task_element_relationship that signifies a constraint between Task_elements. The constraint may only apply within the context of a Task_method or Task_element, specified as the context. applies_in: the Task_element within which the constraint applies. The value of this attribute need not be specified. EXAMPLE Within a specific method, use of test equipment must be preceded by callibration. Or a 30 minute wait is required between stages of a method. An End_task is a type of Task_element. It signifies a point at which to end the task. An Event is the fact of the existence of a state at some point in time. NOTE 1 The event may have occurred or may be not yet started. NOTE 2 The point in time where an event will start or started, may not be known or specified. id: the identifier that distinguishes the Event. name: the words by which the event is known. EXAMPLE 'Start of production' and 'break down of machine A' are examples of event names. description: the text that further characterizes the event. The value of the attribute need not be specified. actual_start_date: the Calendar_date or Date_time when the event started. The value of the attribute need not be specified. planned_start_date: the Calendar_date or Date_time when the event is or was planned to start. The value of the attribute need not be specified. An Exit_loop is a type of Structured_task_element. It signifies a point at which to exit from a loop. An External_item_identification is a type of External_source_identification that provides the identifier of an item in the context of an external source where it can be found. external_id: the identifier of the external item, in its external context. EXAMPLE 1 For a digital file, the file name of a file in the directory where it is located is an example of external_id. EXAMPLE 2 For a book, the external_id could be the ISBN number. An External_source_identification is the identification of the source where an item, that is not fully represented in a population of instances of EXPRESS entity data types but is only referred to, or the components of such an item, can be found. source_id: the text that identifies the context in which the external_id is specified. EXAMPLE 1 For a digital file identified by a filename and directory path, the source_id is the directory path. source_type: the text that identifies the identification scheme of the source_id. EXAMPLE 2 In the case of files, examples of source_type are: 'URL' - for a web page; 'FTP' - for an FTP address; 'ISBN' - for physical documents. item: the external_identification_item whose source is identified. description: the text that provides further information about the external identification. The value of this attribute need not be specified. A File is a file stored on a computer system or in a stack of non-digital documents. A File is either a Hardcopy or a Digital_file. A File_location_identification is a type of External_item_identification that identifies the location of a File in an external storage system where it can be found. EXAMPLE 1 For a computer file identified by a filename and directory path, for example 'D:\project1\specification.txt', the external_id attribute represents the filename, 'specification.txt' and the source_id attribute represents the path name, 'D:\project1\'. EXAMPLE 2 Examples of source_type are: 'URL' - for a web page; 'FTP' - for an FTP address; 'ISBN' - for physical documents. WR1: The identified external item shall be of type File. An Identification_assignment is the assignment of an identifier to product or activity data. identifier: the text that conveys the assigned identifier. NOTE If needed, the organizational context in which this identifier applies, may be specified using a specialization of the object Organization_or_person_in_organization_assignment. role: the text that specifies the purpose of the association of the identification with respect to the product or activity data it is granted to. description: the text that provides further information about the identification. The value of this attribute need not be specified. A Looping_element is a type of Task_element. It invokes a specified number of repetitions of a further Task_element. A Lot_effectivity is a type of Effectivity for which the domain of applicability is defined as a given batch of items. lot_id: the identification of the batch of items. lot_size: the size of the batch of items. A Numerical_item_with_unit is a type of Measure_item that is also a Value_with_unit. The quantity value is therefore provided with its own unit. name: the string by which the Representation_item is known. EXAMPLE The name of a geometric Representation_item may be its element tag in the originating CAD system. An Or_state_cause_effect_definition is a type of State_cause_effect_definition. It relates one or more State_definition entities that are causes to a State_definition that is the effect. At least one cause must exist prior to the effect. An Organization is an administrative structure in which persons are active. id: the identifier that distinguishes the Organization. name: the text by which an Organization is known. A Part is a type of Product that collects the definitional information of the versions of either a part or of a non-countable material. NOTE 1 A Part does not represent an actual physical object that is or was existing in the real world. NOTE 2 A complex instance of the Part entity and of the Document entity may be created in order to represent a document that is a component of a manufactured product, for example a user manual of a car. If the Part represents a non-countable material that is used as a component in an assembly, the Part shall be, in addition, referred to by a Product_category_assignment and the associated category shall have the name 'non-countable material'. NOTE 3 This association is needed for a correct determination of the respective quantity of the components of the assembly. WR1: The Part shall belong to a product category named 'part' or to a product category named 'raw material'. A Part_version is a type of Product_version that identifies a version of a part. NOTE A Part_version is expected to be functionally and physically interchangeable with the other versions of the same Part. A Person is an individual human being. last_name: the Person's name. first_name: the first element of the Person's list of forenames. The value of this attribute need not be specified. prefix_titles: the text that specifies the Person's social or professional standing and appear before his or her names. The value of this attribute need not be specified. A Product is the identification of a product or of a type of product. It is a collector of data common to all revisions of the Product. NOTE 1 Products that this entity data type can represent, include: products existing in the real world; products that may come into existence as a consequence of some realization process. This includes parts and documents; products that are functions. In the interpreted models, these various meanings are represented within instances of the entity product_related_product_category, with prescribed values of the category name. For example, the category name 'document' shall be used when characterizing the fact that a product is actually a document. EXAMPLE 1 The SS Titanic is a product that could be represented by the entity data type Product. EXAMPLE 2 Lifeboat is a class of products that could be represented by the entity data type Product. Each lifeboat on the SS Titanic is a member of this class. NOTE 2 A product is identified by an organization or a person in an organization. The definition of the domain of uniqueness and the mechanism for guaranteeing the uniqueness of product id are outside the scope of this application module. NOTE 3 A product may have zero or more versions. A version of a product is represented with an instance of the entity Product_version or of one of its specializations. id: the identifier that distinguishes the product. NOTE 4 A particular codification for the values of this attribute may be specified in the EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information. EXAMPLE 3 Part numbers, stock item numbers, and serial numbers are examples of product identifiers. name: the words by which the product is known. description: the text which describes the product. The value of the attribute need not be specified. A Product_category is a type of product. id: the identifier that distinguishes the Product_category. The value of this attribute need not be specified. name: the text by which the Product_category is known. EXAMPLE 'piping part', 'boiled output pipe', 'hot water part', 'electrical connectors' are examples of categories of product. description: the text that provides further information about the Product_category. The value of this attribute need not be specified. A Product_version is a revision of a Product. It is a collector of the definitions of this revision of the Product. id: the text that distinguishes the Product_version. description: the text that characterizes the Product_version. The value of this attribute need not be specified. of_product: the Product, the Product_version identifies a version of. A Product_version_relationship is an association between two versions of Product. NOTE A relationship may exist between Product_version of different Products or between different versions of the same Product. relation_type: the string that specifies the meaning of the Product_version_relationship. Where applicable, the following values shall be used: 'derivation': the instance defines a deriving relationship where the related Product_version is based on the relating Product_version which is an earlier version of the same or of a different Product; 'hierarchy': the instance defines a hierarchical relationship where the related Product_version is a subordinate version of the relating Product_version; EXAMPLE 1 'Rev. 1.1' and 'rev. 1.2' are subordinates of 'version 1'. 'sequence': the instance defines a version sequence where the relating Product_version is the preceding version of the related PProduct_version that is the following version. For a given Product_version, there shall be at most one Product_version_relationship of this relation_type referring to this Product_version as 'relating' and at most one Product_version_relationship of this relation_type referring as 'related'. description: a text that provides further information about the Product_version_relationship. The value of this attribute need not be specified. relating_version: the first Product_version that is a part of the relationship. related_version: the other Product_version that is a part of the relationship. If one element of the relationship is dependent up on the other, this attribute shall be the dependent one. A Product_view_definition is a characterization of a Product_version, relevant in one or more application domains and for one or more life cycle stages. A Product_view_definition is a collector of the properties that characterize the Product_version in the initial_context and additional_contexts. EXAMPLE 1 The design of the SS Titanic and the as-built description of the SS Titanic can be represented as two instances of Product_view_definition. WR1: The additional_contexts shall not contain the instance of View_definition_context that is referenced as the initial_context. id: the identifier that distinguishes the Product_view_definition. name: the words by which the Product_view_definition is known. The value of this attribute need not be specified. NOTE 1 This attribute is mapped onto description for compatibility with pre-existing application protocols. additional_characterization: the text that provides further information about the Product_view_definition. The value of this attribute need not be specified. NOTE 2 This attribute may be used to precise the kind of definition. EXAMPLE 2 In case the Product_view_definition characterizes a mating, this attribute may identify the kind of mating. 'clipping', 'welding' are examples of additional_characterization for a mating definition. initial_context: the View_definition_context in which the defined_version has been primarily characterized by the Product_view_definition . additional_contexts: the set of instances of View_definition_context in which this Product_view_definition is also relevant. A Property_value_representation is a type of Representation that represents one or more quantity values. NOTE The present version of this application module does not enable to represent whether the values have been imposed or were derived or measured. It is expected that a future version will add this capability. A Repeat_count is a type of Looping_element. It invokes a specified number of repetitions of the repeated_elementTask_element inherited from the Looping_element supertype. count: the number of times the repeated_element is to be executed. NOTE If the Repeat_count entity is combined with the other subtypes of Looping_element, this becomes the maximum number of repetitions. A Repeat_until is a type of Looping_element. It invokes repetitions of a further Task_element and is repeated until the specified condition is satisfied. The element being repeated shall be executed at least once and the condition tested after the first execution. condition: the criterion to be tested in order to determine that the looping method shall be exited. A Repeat_while is a type of Looping_element. It invokes repetitions of a further Task_element and is repeated while the specified condition is satisfied. The test condition shall be evaluated prior to invoking the method and may result in the Looping_element not being executed at all. condition: the criterion to be tested in order to determine that the Looping_element shall be continued. A Representation is a collection of one or more instances of Representation_item that are related in the specified Representation_context. id: the text that identifies the Representation. The value of this attribute need not be specified. name: the word or group of words by which the Representation is known. EXAMPLE The name of a Representation may be the name of a CAD model. description: the text that provides further information about the Representation. The value of this attribute need not be specified. context_of_items: the Representation_context that specifies the context of the Representation. items: the set of Representation_item instances directly included in the Representation. A Representation_item is an element of representation. A Representation_item shall be in the set of items of one or more instances of Representation or it shall belong to one or more instances of Representation, being referred to, directly of indirectly, by items of these instances of Representation. NOTE this constraint is formally represented in the Express specification of the resource entity that corresponds to Representation_item in the MIM schema. Only specializations of Representation_item can be instantiated. name: the string by which the Representation_item is known. EXAMPLE The name of a geometric Representation_item may be its element tag in the originating CAD system. A Requirement is a type of Product that is used to uniquely identify a requirement. NOTE 1 The term "requirement" is used here in the sense that term is used in systems engineering and similar industrial domains. NOTE 2 There may be many versions of a requirement Requirement_version ). There may also be more than one domain-specific view of a given Requirement_version (using theRequirement_view_definition entity). The requirement entity is simply a placeholder for holding a unique requirement. Most associations and properties are defined at the Requirement_view_definition level - that is in the context of a domain. EXAMPLE A requirement may be identified as "NOx emissions requirement", and uniquely identified as "Req2". NOTE 3 Systems engineering tools and organizations may use differing identification mechanisms. Multiple identifiers may be assigned to a requirement using the Alias_identification entity. A Requirement_assignment is used to relate a requirement (via the Requirement_view_definition entity) to data types representing the items which are affected by the requirement. EXAMPLE A requirement "the vehicle shall have a maximum power output of at least 150BHP" could be assigned to the data types which are used to represent the vehicle's engine. id: an identifier that distinguishes the Requirement_assignment. description: the text that provides further information about the Requirement_assignment. The value of this attribute need not be specified. assigned_requirement: the Requirement_view_definition which is assigned. assigned_to: the item which has the requirement assigned to it. A Requirement_collection_relationship is a type of View_definition_relationship that is used to relate a parent (collection) requirement to its member requirements. This provides a method for collecting together a set of requirements and treating them as a single requirement, whilst still being able to refer to individual requirements. NOTE The inherited "relating_view" and "related_view" attributes have been renamed for purposes of clarity. A Requirement_source is a relationship between a requirement (via the Requirement_view_definition entity) and the data types representing the source of the requirement EXAMPLE The source of the requirement "the vehicle shall have a maximum power output of at least 150BHP" could be a document representing the findings of a market survey of sports car buyers. id: the identifier that distinguishes theRequirement_source. description: the text that provides further information about the Requirement_source. The value of this attribute need not be specified. source: the item which is the source of the requirement. sourced_requirement: the requirement which is to be related to its source. A Requirement_version is a type of Product_version that identifies a particular version of a requirement. NOTE This entity is used to record different versions of a requirement. In this case, the word "version" implies "revision" - that is a particular release of a requirement. EXAMPLE A given requirement might have versions 1.0, 1.1, 1.2 and 2.0. A Scheme is a type of Activity_method. It provides the identification and description of an intended course of action to accomplish an objective. A Scheme enables the ordering of entries. Dates and times may be specified for entries and time intervals between entries. NOTE A Scheme may be classified as a Plan or Schedule, and it may be further classified into specific types of Plans or Schedules. EXAMPLE Acquisition plan, Maintenance plan, Resource schedule are examples of schemes. A Scheme_entry is a type of Activity_method that provides the identification and description of a single entry in a specific Scheme. NOTE 1 A Scheme_entry may be associated with time constraints. NOTE 2 A Scheme_entry only exists within the scope of a specific Scheme. scheme: the Scheme into which the Scheme_entry is included. A Scheme_entry_assignment is a type of Applied_activity_method_assignment. It associates a Scheme_entry with one of more items. NOTE The Scheme_entry_assignment links the single items included in Plans and Schedules with their associated Scheme_entry. These items may be actions, events, or tasks depending on the nature of the Plan or Schedule. A Scheme_entry_relationship is a type of Activity_method_relationship. It relates two Scheme_entry entities. An association may exists between Scheme_entry entities that relate to different Scheme or between different Scheme_entry entity instances for the same Scheme. NOTE The Scheme_entry_relationship provides the ability to relate entries included in Plans or Schedules in different ways. By applying classifications on the Scheme_entry_relationship it can be used for different purposes. EXAMPLE Decomposition, Dependency, and sequencing are examples of kinds of relationships possible between schema entries. A Scheme_relationship is a type of Activity_method_relationship relating two Schemes. NOTE The Scheme_relationship provides the ability to relate Plans or Schedules represented by the Scheme entity in different ways. If classifications are available to the schema using this on, by applying classifications on the Scheme_relationship it can be used for different purposes. EXAMPLE Decomposition, based-on, alternative, version are kinds of relationships between Schemes. A Scheme_subject_assignment is a type of Applied_activity_method_assignment. It associates a Scheme with a specific subject. NOTE The Scheme_subject_assignment links the Plans and Schedules with their associated subjects or targets. This may indicate the intent of the scheme. EXAMPLE The maintenance plan for an individual vehicle, where the subject attribute points to an entity instance representing the individual vehicle. A Scheme_version is a type of Activity_method. It enables version control of Scheme. of_scheme: the Scheme that the entry is related to. A Scheme_version_assignment is a type of Applied_activity_method_assignment. It associates a Scheme with a information describing the version. NOTE The role of the association may be defined through classification. A Scheme_version_relationship is a type of Activity_method_relationship relating two Scheme_versions. NOTE The meaning of the relationship may be defined through classification. A Sequence_of_state is a type of State_relationship in which one set of States precedes another set of States. A Sequence_of_state_definition is a type of State_definition_relationship. It defines a sequence of two or more state definitions. A Sequencing_relationship is a type of Scheme_entry_relationship. It defines a specific type of sequencing and relative timing for two Scheme_entry. NOTE 1 Specific types of sequencing could include start-start, finish-start. sequencing_type: the type of sequencing between the relating scheme entry and related_entry related scheme entry. EXAMPLE finish to start, start to start, finish to finish, start to finish. time_lag: the amount of time, either positive or negative, before the sequencing applies between the relating_entry and the related_entry. The value of this attribute need not be specified. NOTE 2 For a positive time_lag, the relating_entry is the later entry in time. A Serial_effectivity is a type of Effectivity for which the domain of applicability is defined as a possibly open-ended interval of serial numbers. start_id: the first valid serial number. end_id: the last valid serial number. The value of the attribute need not be specified. If the value for this attribute is not specified, the interval of applicability has no upper bound. A Simultaneous_elements is a type of Concurrent_elements that represents two or more actions to be performed together. A State is the mode of being in which something does or could exist or existed for a period of time. NOTE 1 A state's existence can be just a state that an object is currently in, a predicted state that an object will eventually be in, or an observed state that an object has been in. NOTE 2 The period of existence may be an instant or longer. EXAMPLE 1 Main Engine No. 1 is in "operation". EXAMPLE 2 When Generator No. 2 surpasses 5,000 service hours, it will enter "maintenance" mode. EXAMPLE 3 The portable computer's power supply was attached after it displayed a "low-battery" warning. name: the words by which the State is known. description: the text that provides further information about the State. The value of the attribute need not be specified. A State_assertion is used to assert that the subject State is in conformance with a particular State_definition. name: the words by which the State_assertion is known. description: the text that provides further information about the State_assertion. The value of the attribute need not be specified. asserted_state: the subject State being asserted. conformance_state: a particular State_definition the subject State is being asserted against. A State_assessment is used to determine whether the subject State is comparable with a particular State_definition. name: the words by which the State_assessment is known. description: the text that provides further information about the State_assessment. The value of the attribute need not be specified. assessed_state: a subject State that will be assessed against a particular State_definition. comparable_state: a particular State_definition the subject State is assessed against. A State_cause_effect is a type of state relationship and it relates two or more states as one state causing particular resulting effect state(s). In turn, an effect state can become a new causing state yielding in yet more effect states. A State_cause_effect_definition is a type of State_definition_relationship that is used to define a causal relationship between two sets of State_definition entities. At least one State_definition acts as a cause and at least one State_definition acts as a effect. NOTE Additional causal relationships between states can be expressed using the following subtypes: And_state_cause_effect_definition, Or_state_cause_effect_definition, and Xor_state_cause_effect_definition. A State_complement_definition is a type of State_definition_relationship. It is a relationship among three sets of State_definition entities. It defines the complement of a set of State_definition entities relative to a set of State_definition entities that are the universe. NOTE 1 The semantics are the same as in elementary set theory. NOTE 2 The relationship between a State_definition and its complement is symmetrical. A State_definition is a mode of being. A State_definition defines the types of State that can exist. A State's existence can be assessed and asserted against State_definition from State. name: the words by which the State_definition is known. description: the text that provides further information about the State_definition. The value of this attribute need not be specified. A State_definition_relationship is an association between two or more instances of State_definition. NOTE Relationships between State_definition entities may be used to support fault diagnosis. name: the words by which the State_definition is known. description: the text that provides further information about the State_definition. The value of this attribute need not be specified. relating: one of the instances of State_definition that is a part of the relationship. related: the other of the instances of State_definition that is a part of the relationship. A State_definition_role is the purpose of the association of the Applied_state_definition_assignment with product or activity data. name: the words by which the State_definition_role is known. description: the text that provides further information about the State_definition_role. The value of this attribute need not be specified. A State_observed is a type of State. It is an individual or realized State that is observed. A State_predicted is a type of State It is a predicted actual State. Where a predicted state needs to be related to an observed state, the State_predicted_to_observed entity shall be used. A State_predicted_to_observed is a type of state relationship. It specifies the relationship between two individual states, one of which is a State_predicted to a second state which is a State_observed. A State_proper_subset_definition is a type of State_definition_relationship. It is a relationship between two sets of State_definition entities. NOTE The relationship between a state and its environment can be described as a State_proper_subset_definition. The identification of an instrinsic state is the proper_subset. The identification of an extrinsic state is the proper_superset. A State_relationship is a relationship between two or more States. name: the words by which the State_relationship is known. description: the text that provides further information about the State_relationship. The value of this attribute need not be specified. relating: one of the set of instances of State that is a part of the relationship. related: the other of the set of instances of State that is a part of the relationship. A State_role is a specification of the purpose of the association of the Applied_state_assignment with product or activity data. name: the words by which the State_role is known. description: the text that provides further information about the State_role. The value of the attribute need not be specified. A State_subset_definition is a type of State_definition_relationship. It is a relationship between two sets of State_definition entities. NOTE The first set may be equal to the second set. A State_symptom_definition is a type of State_definition_relationship. It relates two or more State_definition entities in regards to symptom, where a symptom is something that indicates the existence of something else. At least one State_definition acts as a symptom_cause and at least one State_definition acts as a symptom_effect. A State_transition is a type of state relationship and it relates two or more states before and after a transition in State, where at least one State is a start state and at least one State is an end state. A State_transition_definition is a type of State_definition_relationship. It relates two or more State_definition entities before and after a transition in state, where at least one State_definition is a start_state and at least one State_definition is an end_state. A Structured_task_element is a type of Task_element. It is made up of other Task_elements A Task_element is a type of Activity_method. It is a representation of all or part of how to undertake a task. A Task_element_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_element with product or activity data. A Task_element_levels is a type of Task_element that provides two or more different descriptions in place of a single method. The actual work will be the same whichever alternative Task_element is followed. NOTE This can be used to provide defferent levels of description of a task for people with varying levels of experience or expertise. alternatives: the Task_elements describing two or more ways in which the same work may be undertaken. A Task_element_relationship is a type of Activity_method_relationship. It relates two instances of Task_element. EXAMPLE Can be used to capture a time dependency that cuts across the structure of the method. A Task_element_sequence is a type of Task_element that comprises a sequence of steps to be followed in a specified order. elements: the Task_elements to be followed in the order specified in the list. A Task_element_state_relationship is an type of Activity_method_relationship. It is an association between a State or a State_definition and a Task_element. The meaning of the entity is determined by classification. Candidate meanings include: assumed starting state; required starting state. state: the State or State_definition being related. task_element: the Task_element being related. A Task_invocation is a type of Task_element. It is an instruction to perform another task. EXAMPLE A Task_element calls a pre-defined task to perform an instrument calibration. task_method: the Task_method to be invoked. A Task_method is a type of Activity_method. It is a specification of work. NOTE The task method may be implemented using people, machines or a combination. objective: the intended result or results of the task. A Task_method_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_method with product or activity data. A Task_method_relationship is a type of Activity_method_relationship. It relates two task methods. NOTE The nature of the relationship is determined from its classification. A Task_method_state_relationship is a relationship between a state and a Task_method. NOTE The meaning of the entity is determined by classification. Candidate meanings include: Assumed starting state; Required starting state. state: the mode of being that is related. task_method: the Task_method being related. A Task_method_version is a type of Activity_method which allows the explicit reference to versions of a Task_methodand to track changes against a Task_method. content: the way in which the task is to be carried out. The value of this attribute need not be specified. of_task_method: the Task_method which this is a version of. A Task_method_version_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_method_version with product or activity data. A Task_method_version_relationship is a type of Activity_method_relationship. It relates two instances of Task_method_version. A Task_objective is a result or objective that is reached by undertaking a Task_method. NOTE More than one Task_method may be defined for a given objective, if there can be several ways to accomplish the objective. name: the word or group of words by which the Task_objective is known. description: the text that provides further information about the Task_objective. A Task_objective_state_relationship is a relationship between a state and a Task_objective. NOTE The meaning of the entity is determined by classification. Candidate meanings include: Intended finishing state; Alternative finishing state. state: the mode of being that is related. task_objective: the Task_objective being related. A Task_step is a type of Task_element that is not further sub-divided. A Time_interval_effectivity is a type of Effectivity for which the domain of applicability is defined as a Time_interval. effectivity_period: the Time_interval that defines the domain of validity. A Tracing_relationship is a type of View_definition_relationship that shows tracing from (traces_from) one requirement to another (traces_to). EXAMPLE A requirement on the performance of a catalytic converter in a car may be traced from a more general emissions requirement. A requirement may trace to many other requirements and vice versa - this is achieved by creating multiple instances of the tracing relationship entity. NOTE 1 The inherited "relating_view" and "related_view" attributes have been renamed for purposes of clarity. NOTE 2 Properties may be attached to tracing relationships. This is intended to deal with "user defined" attributes which are common on tracing relationships in requirements tools. A Unit is a unit quantity. name: the string that specifies the name of the Unit. The value of this attribute need not be specified. si_unit: the boolean value that indicates whether the Unit is one of the units defined in the SI system. A Value_with_unit is the specification of a physical quantity by its value and its unit. unit: the Unit with which the physical quantity is expressed. value_component: the value of the quantity. private Modules.value_with_unit1054.measure_value _value_component; A View_definition_context is the grouping of an application domain and a life cycle stage. It identifies a universe of discourse suitable for the description of products. NOTE Requirements and vocabularies vary among the industrial activity fields. This entity intends to identify such a domain. application_domain: the text that identifies the application context that bounds the universe of discourse. EXAMPLE 1 'assembly study', 'digital mock-up', 'electrical design', 'mechanical design', 'preliminary design', 'process planning' are examples of application domains If application_domain is an empty string, the View_definition_context shall be considered as not specific of any application domain. life_cycle_stage: the text that identifies a stage in the life cycle of a product. EXAMPLE 2 'design phase', 'production', 'recycling phase' are examples of life cycle stages. If life_cycle_stage is an empty string, the View_definition_context shall be considered as not specific of any life cycle stage. description: the text that further characterizes the View_definition_context. The value of this attribute need not be specified. A View_definition_relationship is an association between two instances of Product_view_definition. This association represents a relationship between the product versions, indirectly identified by the instances of Product_view_definition, relevant in the definition contexts of the related instances of Product_view_definition. id: the identifier that distinguishes the View_definition_relationship. relation_type: the meaning of the relationship. The value of this attribute need not be specified. In particular, this attribute is not required in subtypes of this entity. description: the text that provides further information about the View_definition_relationship. The value of this attribute need not be specified. relating_view: one of the instances of Product_view_definition that is a part of the relationship. related_view: the other instance of Product_view_definition that is part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one. A Product_view_definition is a characterization of a Product_version, relevant in one or more application domains and for one or more life cycle stages. A Product_view_definition is a collector of the properties that characterize the Product_version in the initial_context and additional_contexts. EXAMPLE 1 The design of the SS Titanic and the as-built description of the SS Titanic can be represented as two instances of Product_view_definition. WR1: The additional_contexts shall not contain the instance of View_definition_context that is referenced as the initial_context. A Work_order is an authoritative instrument which provides directions to achieve the specified results. A Work_order is the authorization for one or more Activity objects to be performed. name: the text by which the Work_order is known. description: the text that characterizes the Work_order. The value of this attribute need not be specified. in_response_to: the set of zero, one or more instances of Work_request that defines the expected results. A Work_request is the solicitation for some work to be done. NOTE These requests may not be acted upon depending on the authorization granted to the request or its associated Work_order. request_id: the identification that distinguishes the Work_request. version_id: the identification of the version of the Work_request. description: the text that provides further information about the Work_request. The value of this attribute need not be specified. EXAMPLE This attribute may contain a description of the issue that was the origin of the request. purpose: the text description of the reason for the activity request. EXAMPLE 'technical improvement', 'government regulation', 'durability improvement', 'tool improvement', 'production relief', 'production requirement', 'quality improvement', 'security reason', 'standardization', 'cost reduction', 'customer rejection' in case the request results from a rejection by a customer, 'change of standard', 'production alignment', and 'procurement alignment' are examples of purpose. An Xor_state_cause_effect_definition is a type of State_cause_effect_definition. It relates one of the single or many causing state definition(s) and one effect State_definition, whereby any and only one of the causing state definitions exists prior to the single effect to take place. name: the string by which the Representation_item is known. EXAMPLE The name of a geometric Representation_item may be its element tag in the originating CAD system.