This entity contains information about a system specific project. Normally most PLM systems use the concept of project to define a particular population of data. Registered users are normally related to one, or many, projects. The name of the project. A description of the project. Additional information about the project that might be needed. A project might have relations to other projects, e.g. instances found in one project might be linked to instances found in other projects, hence, there is a relationship between the two projects. Another relationship is typically that one project might contain other sub projects, or partitions. This uniquely identifies the instance of the running server that provides the PLCS PLM Services. This is the version of the server. This is the version of the plcs plm services being implemented. This is the underlaying system that provides the PLCS PLM Services. For example: IBM RequisitePro, Telelogic DOORS, UGS TeamCenter Engineering, Dassault SmarTeam, Eurostep Share-A-space. This uniquely identifies the instance of the running server subscriber profile. The subscriber profile ID is unique for the owner of the subscriber profile, which is the organization in the launching system. This is the subscribing systems, including their access points. This is the projects which is being subject of attention for the subscribers. This is the events which is being subject of attention for the subscribers. This is the PLM_objects which is being subject of attention for the subscribers. This is the activation status. This is the access point for the external system, normally a URL is provided This is the response message when a Part is created. The created Part instance might be different from the requested Part. This is the response message when a Part_version is created. The created Part_version instance might be different from the requested Part_version. This message is used to either create an item instance. This is the response message when retreiving the assembly structure given the parent part. Each assembly component relationship reference the child by the attribute related. If the given number of breakdown is more than the first level, then each subsequent assembly component relationship attribute relating will be either set to null, or by a placeholder PLM object only containing a reference to the boid of the parent. This is to avoid cyclic references (where a parent Part is also a child Part in other levels in the assembly structure). This message is used to remove an item instance. This message is used to either update an existing assembly relationship. This is the response message when a Part is updated. The created Part instance might be different from the requested Part. This is the response message when retreiving the assembly structure given the child part. Each assembly component relationship reference the parent by the attribute relating. This is the response message when having requested to Load characteristics for a PLM object instance. The search operates on a number of given business object types given by the search criteria header(FilterHeader). The primary search criteria can be: identifier(id), name, or description. These primary search criterias can be empty, or contain wildcard charachters(depends on the underlaying system implementation). Additional search criterias are provided in the FilterHeader, such as specifc business object instances being related(the attribute Search Objects), i.e. classification, a property (of a certain kind), or a person/organization. Each resulting business object instance is loaded with its default characteristics. This message returns all used View_definition_contexts This message returns all Organizations This message returns all Persons This message returns all used classifications This message returns all used Properties represented as Class, or External_class This message returns all used Units This is the response message when a Requirement is created. The created Requirementinstance might be different from the requested Requirement This is the response message when a Requirement is updated. The createdRequirement instance might be different from the requested Requirement. This is the response message when a Requirement_version is created. The created Requirement_versioninstance might be different from the requested Requirement_version This is the response message when a Requirement_version is updated. The createdRequirement_version instance might be different from the requested Requirement_version. This is the response message when a Tracing_relationship is created. The created Tracing_relationshipinstance might be different from the requested Tracing_relationship This is the response message when a Tracing_relationship is updated. The createdTracing_relationship instance might be different from the requested Tracing_relationship. This is the response message when a Requirement_collection_relationship is created. The created Requirement_collection_relationshipinstance might be different from the requested Requirement_collection_relationship This is the response message when a Requirement_collection_relationship is updated. The createdRequirement_collection_relationship instance might be different from the requested Requirement_collection_relationship. The name of a given property can be used with optional values. If a value is given an optional unit (its acronym e.g. mm, color) can be given. The classification This is the top entity for all PLM business object filters. This filter is used to define which amount of information that should populate a particular business object instance. This is the top entity for all PLM business object filters. This filter is used to define which amount of information that should populate a particular business object instance. adds all new, removes those provided which exists adds all new, removes all existing adds all new, ignores those provided which exists ignores This is the response message when a Information_collection is created. The created Information_collection instance might be different from the requested Information_collection. This is the response message when a Information_collection_version is created. The created Information_collection_version instance might be different from the requested Information_collection_version. This is the response message when a Information_collection is updated. The created Information_collection instance might be different from the requested Information_collection. An update of a Information_collection version can be configured by a Information_collection version update header. An update message reconcile an existing Information_collection version with the submitted Information_collection version instance. The update Information_collection version applies to characteristics that does not have explicit methods/services for update. This is the response message when a Information_collection version is updated. The created Information_collection version instance might be different from the requested Information_collection version. This method check in the Information_collection version. Normally only the user who have checked out the dcument version should be allowed to check in the Information_collection version. This rule might be implemented differently on a system to system basis. Also, a common rule is that a Information_collection version can only be checked in if it is checked out. This method retreives Information_collection versions that are checked out. Either all checked out Information_collection_versions are retreived, or only the Information_collection versions being checked out by this user. This method retreives Information_collection versions that are checked in. Either all checked in Information_collection versions are retreived, or only the Information_collection versions being checked in by this user. This is the response message when a Document is created. The created Document instance might be different from the requested Document. This is the response message when a Document_version is created. The created Document _versioninstance might be different from the requested Document_version. This is the response message when a digital file is being downloaded by a client. This message is used to create a digital file. The actual file can be either a file which is submitted, or a reference to an external file, in which case the address is submitted. This message is used to update a digital file. The actual file can be either a file which is submitted, or a reference to an external file, in which case the address is submitted. This is the response message when a Document is updated. The created Document instance might be different from the requested Document. An update of a Document version can be configured by a Document version update header. An update message reconcile an existing Document version with the submitted Document version instance. The update Document version applies to characteristics that does not have explicit methods/services for update. This is the response message when a Document version is updated. The created Document version instance might be different from the requested Document version. This method check in the document version. Normally only the user who have checked out the dcument version should be allowed to check in the document version. This rule might be implemented differently on a system to system basis. Also, a common rule is that a document version can only be checked in if it is checked out. This method retreives document versions that are checked out. Either all checked out Document_versions are retreived, or only the document versions being checked out by this user. This method retreives document versions that are checked in. Either all checked in document versions are retreived, or only the document versions being checked in by this user. This is the response message when a serialnumbered part is created. The created serialnumbered part might be different from the requested serialnumbered part This is the response message when a serialnumbered part is created. The created serialnumbered part might be different from the requested serialnumbered part This is the response message when a serialzed part is updated. The created serialzed part instance might be different from the requested serialzed part. This message is used to create an item instance relating a parent product as individula with a child product as indiidua via its definitions. This message is used to remove an item instance relating a parent product as individula with a child product as indiidua via its definitions. This message is used to update an existing assembly relationship. This is the response message when a serialzed part is updated. The created serialzed part instance might be different from the requested serialzed part. This is the response message when a serialzed part is updated. The created serialzed part instance might be different from the requested serialzed part. This is the response message when a serialzed part is updated. The created serialzed part instance might be different from the requested serialzed part. This is the response message when a serialzed part is updated. The created serialzed part instance might be different from the requested serialzed part. This message is used to retreive the roles that this user have been assigned to by organizations. This message is used to retreive the roles that the given user have been assigned to by organizations. NOTE, if a person is given and not an organization, all roles are retreived, else, only the roles for that organization is retrieved. This message is used to retreive the current role that this user is using. This message is used to retreive the roles that this user have been assigned to by organizations. This message is used to retreive favourite PLM object instances. This message is used to remove favourite PLM object instances. This message is used to create a favourite PLM object instance. This message is used to retreive information about the corresponding user(person) of the operating session. This message is used to retreive notifications being sent out to the user governing the session. Notifications can be sent explicitly by another active user, or implicitly being triggered from an active subscriber profile. This message is used to mark an unread notification as being read. A notification being sent out from a subscriber profile is then considered as being processed. This message is used to retreive subscriber profiles being created and managed by this user. Sent out messages will be included and status (if applicable) of each sent out message. This message is used to retreive PLM_object instances that have been assigned to the user for this session. This message is used to create a notification. Notifications can be sent explicitly by another active user, or implicitly being triggered from an active subscriber profile. This message is used to create a subscriber profile. Notifications can be sent explicitly by another active user, or implicitly being triggered from an active subscriber profile. This message is used to update a subscriber profile. Notifications can be sent explicitly by another active user, or implicitly being triggered from an active subscriber profile. This message updates a Scheme_version This message creates a Scheme_version This message updates a Task_method_version. This message updates a Task_method This message updates a Task_step This message creates a State_observed. This message creates a State_definition. This message creates a Task_method This message creates a Task_method_version This message creates a Task_step This message creates a Task_invocation This message Updates a Task_invocation This message creates a Scheme_entry. This message creates a Type_of_person. This message creates a Type_of_person_definition. This message creates a Qualification_type. This message creates a Resource_item. This message creates a Resource_as_realized_resource_item. This message creates a Required_resource_by_specification. This message creates a Required_resource_by_resource_item. This message creates a Managed_resource. This message creates a Decreasing_resource_event. This message creates a Increasing_resource_event. This message creates a Location. This message creates a Address_based_location_representation. This message creates a Global_location_representation. This message creates a Organization_based_location_representation. This message creates a Product_based_location_identification. This message creates a Regional_grid_location_representation. This is the response message when a Breakdown is created. The created Breakdown tinstance might be different from the requested Breakdown This is the response message when a Breakdown is updated. The created Breakdown instance might be different from the requested Breakdown. This is the response message when a Breakdown_version is created. The created Breakdown_version tinstance might be different from the requested Breakdown_version This is the response message when a Breakdown_version is updated. The created Breakdown_version instance might be different from the requested Breakdown_version. This is the response message when a Breakdown_element is created. The created Breakdown_element tinstance might be different from the requested Breakdown_element This is the response message when a Breakdown_element is updated. The created Breakdown_element instance might be different from the requested Breakdown_element. This is the response message when a Breakdown_element_version is created. The created Breakdown_element_version instance might be different from the requested Breakdown_element_version This is the response message when a Breakdown_element_version is updated. The created Breakdown_element_version instance might be different from the requested Breakdown_element_version. This is the response message when a System_breakdown is created. The created System_breakdown tinstance might be different from the requested System_breakdown This is the response message when a System_breakdown is updated. The created System_breakdown instance might be different from the requested System_breakdown. This is the response message when a System_breakdown_version is created. The created System_breakdown_version tinstance might be different from the requested System_breakdown_version This is the response message when a System_breakdown_version is updated. The created System_breakdown_version instance might be different from the requested System_breakdown_version. This is the response message when a System_element is created. The created System_element tinstance might be different from the requested System_element This is the response message when a System_element is updated. The created System_element instance might be different from the requested System_element. This is the response message when a System_element_version is created. The created System_element_version instance might be different from the requested System_element_version This is the response message when a System_element_version is updated. The created System_element_version instance might be different from the requested System_element_version. This is the response message when a Functional_breakdown is created. The created Functional_breakdown tinstance might be different from the requested Functional_breakdown This is the response message when a Functional_breakdown is updated. The created Functional_breakdown instance might be different from the requested Functional_breakdown. This is the response message when a Functional_breakdown_version is created. The created Functional_breakdown_version tinstance might be different from the requested Functional_breakdown_version This is the response message when a Functional_breakdown_version is updated. The created Functional_breakdown_version instance might be different from the requested Functional_breakdown_version. This is the response message when a Functional_element is created. The created Functional_element tinstance might be different from the requested Functional_element This is the response message when a Functional_element is updated. The created Functional_element instance might be different from the requested Functional_element. This is the response message when a Functional_element_version is created. The created Functional_element_version instance might be different from the requested Functional_element_version This is the response message when a Functional_element_version is updated. The created Functional_element_version instance might be different from the requested Functional_element_version. This is the response message when a Physical_breakdown is created. The created Physical_breakdown tinstance might be different from the requested Physical_breakdown This is the response message when a Physical_breakdown is updated. The created Physical_breakdown instance might be different from the requested Physical_breakdown. This is the response message when a Physical_breakdown_version is created. The created Physical_breakdown_version tinstance might be different from the requested Physical_breakdown_version This is the response message when a Physical_breakdown_version is updated. The created Physical_breakdown_version instance might be different from the requested Physical_breakdown_version. This is the response message when a Physical_element is created. The created Physical_element tinstance might be different from the requested Physical_element This is the response message when a Physical_element is updated. The created Physical_element instance might be different from the requested Physical_element. This is the response message when a Physical_element_version is created. The created Physical_element_version instance might be different from the requested Physical_element_version This is the response message when a Physical_element_version is updated. The created Physical_element_version instance might be different from the requested Physical_element_version. This is the response message when a Zone_breakdown is created. The created Zone_breakdown tinstance might be different from the requested Zone_breakdown This is the response message when a Zone_breakdown is updated. The created Zone_breakdown instance might be different from the requested Zone_breakdown. This is the response message when a Zone_breakdown_version is created. The created Zone_breakdown_version tinstance might be different from the requested Zone_breakdown_version This is the response message when a Zone_breakdown_version is updated. The created Zone_breakdown_version instance might be different from the requested Zone_breakdown_version. This is the response message when a Zone_element is created. The created Zone_element tinstance might be different from the requested Zone_element This is the response message when a Zone_element is updated. The created Zone_element instance might be different from the requested Zone_element. This is the response message when a Zone_element_version is created. The created Zone_element_version instance might be different from the requested Zone_element_version This is the response message when a Zone_element_version is updated. The created Zone_element_version instance might be different from the requested Zone_element_version. This is the response message when a Hybrid_breakdown is created. The created Hybrid_breakdown tinstance might be different from the requested Hybrid_breakdown This is the response message when a Hybrid_breakdown is updated. The created Hybrid_breakdown instance might be different from the requested Hybrid_breakdown. This is the response message when a Hybrid_breakdown_version is created. The created Hybrid_breakdown_version tinstance might be different from the requested Hybrid_breakdown_version This is the response message when a Hybrid_breakdown_version is updated. The created Hybrid_breakdown_version instance might be different from the requested Hybrid_breakdown_version. This is the response message when a Breakdown_element_usage is created. The created Breakdown_element_usage tinstance might be different from the requested Breakdown_element_usage This is the response message when a Breakdown_element_usage is updated. The created Breakdown_element_usage instance might be different from the requested Breakdown_element_usage. This is the response message when a System_element_usage is created. The created System_element_usage tinstance might be different from the requested System_element_usage This is the response message when a System_element_usage is updated. The created System_element_usage instance might be different from the requested System_element_usage. This is the response message when a Functional_element_usage is created. The created Functional_element_usage tinstance might be different from the requested Functional_element_usage This is the response message when a Functional_element_usage is updated. The created Functional_element_usage instance might be different from the requested Functional_element_usage. This is the response message when a Physical_element_usage is created. The created Physical_element_usage tinstance might be different from the requested Physical_element_usage This is the response message when a Physical_element_usage is updated. The created Physical_element_usage instance might be different from the requested Physical_element_usage. This is the response message when a Zone_element_usage is created. The created Zone_element_usage tinstance might be different from the requested Zone_element_usage This is the response message when a Zone_element_usage is updated. The created Zone_element_usage instance might be different from the requested Zone_element_usage. This is the response message when a Hybrid_element_usage is created. The created Hybrid_element_usage tinstance might be different from the requested Hybrid_element_usage This is the response message when a Hybrid_element_usage is updated. The created Hybrid_element_usage instance might be different from the requested Hybrid_element_usage. This message returns 0, or more Breakdown_element_usage instances, where the children are populated in the Breakdown_element_usage.related attribute This message returns 0, or more Breakdown_element_usage instances, where the parents are populated in the Breakdown_element_usage.relating attribute. This message returns 0, or more System_element_usage instances, where the children are populated in the System_element_usage.related attribute This message returns 0, or more System_element_usage instances, where the parents are populated in the System_element_usage.relating attribute. This message returns 0, or more Functional_element_usage instances, where the children are populated in the Functional_element_usage.related attribute This message returns 0, or more Functional_element_usage instances, where the parents are populated in the Functional_element_usage.relating attribute. This message returns 0, or more Physical_element_usage instances, where the children are populated in the Physical_element_usage.related attribute This message returns 0, or more Physical_element_usage instances, where the parents are populated in the Physical_element_usage.relating attribute. This message returns 0, or more Zone_element_usage instances, where the children are populated in the Zone_element_usage.related attribute This message returns 0, or more Zone_element_usage instances, where the parents are populated in the Zone_element_usage.relating attribute. This message returns 0, or more Hybrid_element_usage instances, where the children are populated in the Hybrid_element_usage.related attribute This message returns 0, or more Hybrid_element_usage instances, where the parents are populated in the Hybrid_element_usage.relating attribute. This message creates an activity that reports things that have been done in response to a directed activity. This message creates a planned activity that will affect physical items. This message creates an activity. An activity can be decomposed into a number of of activites that each represents a pair of input/output elements. This message creates an activity. An activity can be decomposed into a number of of activites that each represents a pair of input/output elements. A created activity that represents a planned engineerign change can be promoted to an engineering change order. This message creates a work order. A work order can work that have been done in response to a work request, or any request for change. This message creates a work request. A work request can be an issue, or any request for change. This message promote an activity from a planned state to an order. This dynamically should be reflected by changes of the affected elements. An activity can be decomposed into a number of of activites that each represents a pair of input/output elements. A created activity that represents a planned engineerign changeis promoted to an engineering change order can keep its history by creating a new activity for the engineering change order. 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.