| DEX (D011):— aviation_maintenance | Date: 2007/06/15 08:10:54 Revision: 1.84 |
This DEX enables the transmission of information reporting on:
Typically a maintenance activity is performed, or the product used. Information about the activity is then collated, packed in the DEX and sent on. Typical information includes what was done, by whom, on what date. Information about the product on which the activity was done, (the reportable item), such what was replaced, what were the life measurements of the product, e.g hours flown.
The following sections outline the types of maintenance activities that this DEX reports on.
The following product usage events are reported on by this DEX:
The following product status events are reported on by this DEX:
The following maintenance activities are reported on by this DEX:
The following Inventory activities are reported on by this DEX:
On completion of a maintenance or reportable item activity, information about the product and the work done to the product is reported by this DEX. This information is summarized in Figure 2 below. A detailed definition of the information and how it is represented using ISO 10303-239 PLCS is provided in Section: Aviation Maintenance - Implementation details
The information exchanged is contained within a message that is sent to the recipients. The following information is exchanged:
The following sections provide a detailed description on how to represent an aviation maintenance feedback DEX using ISO 10303-239 PLCS. This is defined using PLCS capabilities, templates and PLCS reference data.
This definition may be further tailored by specific parties by extending the reference data defined in the PLCS reference data library.
The information to be exchanged by the Aviation Maintenance DEX has been summarised in Figure 2 in Section: 'Aviation maintenance - Information content' above. A summary of how this information is represented in PLCS is provided in Figure 3 and expanded in subsequent sections.
Figure 3 shows:
The remainder of this section provides more details how the information summarized previously is represented using PLCS. It comprises the following:
Each section contains a UML class diagram that provides an overview of the data to be exchanged, a description of the UML classes and then a definition of how that information is represented in PLCS. The information that is shown in UML class diagram is intended to provide guidance for the type of information that can be represented by the DEX. As different systems and business processes may not support or require the information the DEX does not mandate that all the information shown is exchanged.
NOTE For each template, a table is provided detailing the values for each template parameter, Where the value is to be set by the sending system, value is shown with a ? at the start and end. E.g. ?org_id?.
Information will be extracted and packaged as a message which is then sent to a recipient.
The information associated with a message is summarized in the UML class diagram in Figure 4. This shows the meta data for message, and the activity being reported on in the message - the subclasses of Reportable_activity. The information associated with the activities is detailed in subsequent sections.
NOTE The information shown in the UML class diagram in Figure 4 is intended to illustrate the type of information that can be represented by the DEX. It does not imply that all exchanges must contain this information.
The information detailed in the UML class diagram in Figure 4 is as follows:
Extracted information should be packaged as a message which is then sent to the recipient. The Message containing the reported activity is represented in ISO 10303-239 PLCS by the template #1, representing_message which instantiates Message described in the capability C014: messaging and shown in Figure 5 below. The message identifies who sent the message, when it was sent and who it was sent to. It also identifies the content of the message by linking to the activities that are the contained in message, represented by template #2 representing_work_done. If the date of extract of the data is required this is represented by template #4 assigning_time described in the capability C036: assigning_date_time . If contract identification information is required this is represented by template #3 assigning_contract described in the capability C083: representing_contract. If security information is required this is represented by template #5 assigning_security_classification described in the capability : representing_security.
The following templates are used in the diagram and represent the various types of information:
| Template #1 (Figure 5): representing_message | |||
|---|---|---|---|
| Description | For the identifying the package of data to be exchanged | ||
| Parameter name: | Parameter value: | Parameter description: | |
| rep_msg_id | ?rep_msg_id? | the identifier of the message | |
| rep_msg_id_class_name | "Message_identification_code" (urn:plcs:rdl:std:Message_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the message. This provides the role or reason for the identification. | |
| rep_msg_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the rep_msg_id_class_name. | |
| rep_msg_id_owner | ?rep_msg_id_owner? | The identifier or name of the organization that "owns" the message identifier. | |
| rep_msg_id_owner_class_name | For names of organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
| rep_msg_id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the cnt_org_id_class_name class items. | |
| date_class_name | "Date_message_data_frozen" (urn:plcs:rdl:std:Date_message_data_frozen) | The name of the class being used to classify the role date assignment, e.g. the message sending date. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the date_class_name class items. | |
| year | The 'year' component of: the date the data was sent | Calendar_date year_component | |
| month | The 'month' component of: the date the data was sent | Calendar_date month_component | |
| day | The 'day' component of: the date the data was sent | Calendar_date day_component | |
| hour | The 'hour' component of: the date the data was sent | Local_time hour_component of the date and time. | |
| minute | The 'minute' component of: the date the data was sent | Local_time minute_component of the date and time. This parameter is optional. If not given, it will remain unset. | |
| second | The 'second' component of: the date the data was sent | Local_time second_component of the date and time. This parameter is optional. If not given, it will remain unset. | |
| sense | OFFSET_ORIENTATION.exact | times are assumed to be UTC | |
| hour_offset | 0 | 0 as times are assumed to be UTC | |
| minute_offset | 0 | 0 as times are assumed to be UTC | |
| ap239_id_class_name | "AP239_version" (urn:plcs:rdl:std:AP239_version) | The name of the class being used to classify the message (Message) of the message. This identifies the version of AP239 to which the data in the message conforms. | |
| ap239_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the ap239_id_class_name class items. | |
| dex_id_class_name | "DEX_used" (urn:plcs:rdl:std:DEX_used) | The name of the class being used to classify the message (Message) of the message. This identifies the DEX to which the data in the message conforms. | |
| dex_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the dex_id_class_name class items. | |
| content | Activity_actual | This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
The use of template #2 representing_work_done in Figure 5 is identical to, and described in, template table: Template #3(Figure 7).
| Template #3 (Figure 5): assigning_contract | |||
|---|---|---|---|
| Description | For the identifying the contract that the message is part of. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| cnt_id | ?cnt_id? | the identifier of the contract | |
| cnt_id_class_name | "Contract_identification_code" (urn:plcs:rdl:std:Contract_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the contract. | |
| cnt_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the cnt_id_class_name. | |
| cnt_org_id | 'cnt_org_id' | The identifier or name of the organization that "owns" the identifier. | |
| cnt_org_id_class_name | For names of organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization. | |
| cnt_org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the cnt_org_id_class_name class items. | |
| items | Message | The items to which the contract is assigned | |
| Template #4 (Figure 5): assigning_time | |||
|---|---|---|---|
| Description | The date and time the data within the message is extracted. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| date_class_name | "Date_actual_extraction" (urn:plcs:rdl:std:Date_actual_extraction) | The name of the class being used to classify the role date assignment, e.g. the start date. | |
| date_ecl_id | 'urn:plcs:rdl:std' | The id of the External_class_library in which the date class is defined. | |
| year | The 'year' component of: the date and time of extraction. | Calendar_date year_component | |
| month | The 'month' component of: the date and time of extraction. | Calendar_date month_component | |
| day | The 'day' component of: the date and time of extraction. | Calendar_date day_component | |
| hour | The 'hour' component of: the date and time of extraction. | Local_time year_component of the date and time. | |
| minute | The 'minute' component of: the date and time of extraction. | Local_time month_component of the date and time. This parameter is optional. If not given, it will remain unset. | |
| second | The 'second' component of: the date and time of extraction. | Local_time day_component of the date and time. This parameter is optional. If not given, it will remain unset. | |
| sense | OFFSET_ORIENTATION.exact | times are assumed to be UTC | |
| hour_offset | 0 | 0 as times are assumed to be UTC | |
| minute_offset | 0 | 0 as times are assumed to be UTC | |
| items | Message | The items to which the date is assigned. | |
| Template #5 (Figure 5): assigning_security_classification | |||
|---|---|---|---|
| Description | |||
| Parameter name: | Parameter value: | Parameter description: | |
| security_class_name | "Security_classification" (urn:plcs:rdl:std:Security_classification) | The name of the class being used to classify the security level. (Security_classification_assignment) | |
| security_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @security_assgn_class_name. | |
| items | Message | The items to which the security classification is assigned. | |
| Template #6 (Figure 5): assigning_person_in_organization | |||
|---|---|---|---|
| Description | Identification of the person sending or receiving the message. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| last_name | ?last_name? | The last name of the person sending or receiving the message | |
| first_name | ?first_name? | The first name of the person sending or receiving the message; use "unknown" when the information is not known to the sending system | |
| middle_names | ?middle_names? | The middle name of the person sending or receiving the message; use "unknown" when the information is not known to the sending system | |
| prefix_titles | ?prefix_titles? | The prefix title of the person sending or receiving the message; use "unknown" when the information is not known to the sending system | |
| suffix_titles | ?suffix_titles? | The suffix title of the person sending or receiving the message; use "unknown" when the information is not known to the sending system | |
| person_role_class_name | "Receiver_of" (urn:plcs:rdl:std:Receiver_of) "Sender_of" (urn:plcs:rdl:std:Sender_of) | The name of the class being used to classify the person assignment () This provides the role for the assignment. | |
| person_role_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @person_role_class_name class. | |
| org_id | ?org_id? | The identifier of the organization in which the person sending or receiving the message. | |
| org_id_class_name | For a name identifying an organization, use "Organization_name" (urn:plcs:rdl:std:Organization_name) For a code identifying an organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name or code that identifies (Identification_assignment) an organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| items | Message | The items to which the person is assigned | |
| Template #7 (Figure 5): assigning_organization | |||
|---|---|---|---|
| Description | The identification of the organization sending or receiving the message. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| org_id | ?org_id? | The identifier of the sending or receiving organization | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| org_assgn_class_name | "Receiver_of" (urn:plcs:rdl:std:Receiver_of) "Sender_of" (urn:plcs:rdl:std:Sender_of) | The name of the class being used to classify the assignment of the organization. (Organization_or_person_in_organization_assignment) This provides the role or reason for the assignment. For example 'Owner_of'. | |
| org_assgn_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_assgn_class_name. | |
| items | Message | The items to which the organization is assigned | |
Maintenance activities that are performed on an aircraft normally require a level of authorization. This can be represented by a maintenance work order. The information that can be associated with a maintenance work order is summarized in the UML class diagram in Figure 6.
NOTE The information shown in the UML class diagram in Figure 6 is intended to illustrate the type of information that can be represented by the DEX. It does not imply that all exchanges must contain this information.
The information detailed in the UML class diagram in Figure 6 is as follows:
A work order is required to conduct work on an aircraft. Work orders are the authority to conduct an activity on a reportable_item.
A work order is represented by an instance of Work_order which is defined as part of the template #4 representing_work_order as shown in the EXPRESS-G diagram, Figure 7, below.
The type of activity that is authorized, such as maintenance, installation, repair/overhual is provided by classifying the activity by using the template #18 assigning_reference_data.
The work order is normally raised against a particular reportable item, the item for which work is required. The reportable item is represented by the template #2 representing_product_as_realized described in the capability C045: representing_product_as_individual. The work order is related to the representing_product_as_realized by an Applied_activity_assignment within template #4 representing_work_order. The work order may also be raised against the end item, the item to which the reportable item is fitted. The end item is represented by the template #9 representing_product_as_realized and related to the work order by the template #1 assigning_activity. The end item is related to the reportable item by the template #8 representing_promissory_usage described in the capability C003: representing_assembly_structure. Section: Representing a reportable item provides details of how a reportable item is represented.
A work order identifies the method by which the authorised activity is to be done - a standard maintenance task. This is a description of the work to be done or a more formal task specification. The informal description is represented by the template #5 representing_typical_activity. Where a formal task specification is available, the template #17 referencing_task is used to identify the task.
The work order can have a status which is represented by template #12 assigning_asserted_state described in the capability C041: representing_state_observed. The work order can record a date on which the authorized work was planned to start, a date it was planned to end and the date that the work was actually completed; these are respectively represented by the templates #15, #16 and #13 assigning_time described in the capability C036: assigning_date_time. The organization that raises the work order can be record; this is represented by template #19 assigning_organization described in the capability C094: assigning_organization. The work order can record the organization that conducts the maintenance; this is represented by template #10 assigning_organization described in the capability C094: assigning_organization. The work order can record information about the type of organization that conducts the maintenance, e.g. the line of repair (first line, second line); this is represented by template #11 assigning_reference_data described in the capability C010: assigning_reference_data. The work order can record the description of the work order; this is represented by template #14 assigning_descriptor described in the capability C095: assigning_descriptor.
The relationship between two work orders or a work order and an engineering instruction is represented by Activity_relationship. The related work order and the engineering instruction is also represented by an instance of Work_order represented by templates #7 and #6 representing_work_order as shown in the EXPRESS-G diagram, Figure 7, below.
The activity identifying the work done on the reportable item that was authorised by the maintenance work order is represented by template #3 representing_work_done described in the capability C064: representing_work_done. Section: Representing reportable item maintenance activity provides details of how to represent the work done.
The following templates are used in the diagram and represent the maintenance work order:
| Template #1 (Figure 7): assigning_activity | |||
|---|---|---|---|
| Description | The association of the work order to the end item that is the subject of the work order | ||
| Parameter name: | Parameter value: | Parameter description: | |
| role_class_name | "Activity_output" (urn:plcs:rdl:std:Activity_output) | The class name of the External_class corresponding to the role of the assignment, e.g. "Activity_input" (urn:plcs:rdl:std:Activity_input), or "Activity_output" (urn:plcs:rdl:std:Activity_output). | |
| role_ecl_id | "urn:plcs:rdl:std" | The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name. | |
| assigned_activity | Activity_actual | This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| items | Product_as_realized | This is the Product_as_realized that represents the end item. | |
The use of template #2 representing_product_as_realized in Figure 7 is identical to, and described in, template table: Template #5(Figure 17).
| Template #3 (Figure 7): representing_work_done | |||
|---|---|---|---|
| Description | The work done under the authority of the work order.' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier assigned to the work done | |
| id_class_name | "Activity_identification_code" (urn:plcs:rdl:std:Activity_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the actual activity. This provides the role or reason for the identification. | |
| id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @id_class_name class. | |
| id_owner | ?org_id? | The identifier of the organization that "owns" the identifier. | |
| id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
| id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the org_id_class_name class items. | |
| date_class_name | "Date_actual_start" (urn:plcs:rdl:std:Date_actual_start) | The date the activity was started | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the date_name class items. | |
| year | ?year? | the year component of the start date and time of the work that was done | |
| month | ?month? | the month component of the start date and time of the work that was done | |
| day | ?day? | the day component of the start date and time of the work that was done | |
| hour | ?hour? | the hour component of the start date and time of the work that was done | |
| minute | ?minute? | the minute component of the start date and time of the work that was done | |
| second | ?second? | the second component of the start date and time of the work that was done | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| items | Product_as_individual_view | The reportable item that the work was done on represented as Product_as_individual_view which is part of template representing_product_as_realized. | |
| predicted_work | Directed_activity | The work request that caused the work order represented as a Directed_activity /> which is part of template representing_work_order. | |
| method | Activity_method | The method used to do the work represented as Activity_method which is part of template representing_typical_activity. | |
| Template #4 (Figure 7): representing_work_order | |||
|---|---|---|---|
| Description | The work order.' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier assigned to the work order | |
| id_class_name | "Work_request_identification_code" (urn:plcs:rdl:std:Work_request_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the id_class_name class | |
| org_id | ?org_id? | The identifier of the organization that "owns" the identifier. | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code. | |
| org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the org_id_class_name class items. | |
| date_class_name | "Date_or_date_time_assignment" (urn:plcs:rdl:std:Date_or_date_time_assignment) | The name of the class being used to classify the role date assignment, e.g. the date when the Work_order was issued. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the date_name class items. | |
| year | ?year? | the year component of the start date and time of the work order was raised | |
| month | ?month? | the month component of the start date and time of the work order was raised | |
| day | ?day? | the day component of the start date and time of the work order was raised | |
| hour | ?hour? | the hour component of the start date and time of the work order was raised | |
| minute | ?minute? | the minute component of the start date and time of the work order was raised | |
| second | ?second? | the second component of the start date and time of the work order was raised | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| act_id | ?act_id? | The version identifier assigned to the work order | |
| act_id_class_name | "Activity_identification_code" (urn:plcs:rdl:std:Activity_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| act_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_id_class_name class | |
| act_org_id | ?act_org_id? | The identifier of the organization that "owns" the version identifier. | |
| act_org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization that "owns" the version identifier. For example CAGE code. | |
| act_org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_org_id_class_name class items. | |
| appr_status | "Approval_status" (urn:plcs:rdl:std:Approval_status) | The class name of the External_class corresponding to the approval status of the work order. | |
| appr_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_org_id_class_name class items. | |
| input | Product_as_individual_view | The reportable item that is the subject of the work order, represented as Product_as_individual_view which is part of template representing_product_as_realized. | |
| in_response_to | Work_request | The work request that caused the work order. | |
| chosen_method | Activity_method | The method used to do the work represented as Activity_method which is part of template representing_typical_activity. | |
The use of template #5 representing_typical_activity in Figure 7 is identical to, and described in, template table: Template #1(Figure 9).
| Template #6 (Figure 7): representing_work_order | |||
|---|---|---|---|
| Description | The Engineering Instruction related to the work order.' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier assigned to the engineering instruction | |
| id_class_name | "Work_request_identification_code" (urn:plcs:rdl:std:Work_request_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the id_class_name class | |
| org_id | ?org_id? | The identifier of the organization that "owns" the identifier. | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code. | |
| org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the org_id_class_name class items. | |
| date_class_name | "Date_or_date_time_assignment" (urn:plcs:rdl:std:Date_or_date_time_assignment) | The name of the class being used to classify the role date assignment, e.g. the date when the Work_order was issued. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the date_name class items. | |
| year | ?year? | the year component of the start date and time of the engineering instruction was raised | |
| month | ?month? | the month component of the start date and time of the engineering instruction was raised | |
| day | ?day? | the day component of the start date and time of the engineering instruction was raised | |
| hour | ?hour? | the hour component of the start date and time of the engineering instruction was raised | |
| minute | ?minute? | the minute component of the start date and time of the engineering instruction was raised | |
| second | ?second? | the second component of the start date and time of the engineering instruction was raised | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| act_id | ?act_id? | The version identifier assigned to the engineering instruction | |
| act_id_class_name | "Activity_identification_code" (urn:plcs:rdl:std:Activity_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| act_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_id_class_name class | |
| act_org_id | ?act_org_id? | The identifier of the organization that "owns" the version identifier. | |
| act_org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization that "owns" the version identifier. For example CAGE code. | |
| act_org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_org_id_class_name class items. | |
| appr_status | "Approval_status" (urn:plcs:rdl:std:Approval_status) | The class name of the External_class corresponding to the approval status of the work order. | |
| appr_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_org_id_class_name class items. | |
| input | Product_as_individual_view | The reportable item that is the subject of the engineering instruction. | |
| in_response_to | Work_request | The work request that caused the engineering instruction. | |
| chosen_method | Activity_method | The method of satisfying the engineering instruction. | |
| Template #7 (Figure 7): representing_work_order | |||
|---|---|---|---|
| Description | A work order related the work order described in ' template table: Template #5(Figure 17). | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier assigned to the related work order | |
| id_class_name | "Work_request_identification_code" (urn:plcs:rdl:std:Work_request_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the id_class_name class | |
| org_id | ?org_id? | The identifier of the organization that "owns" the identifier. | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code. | |
| org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the org_id_class_name class items. | |
| date_class_name | "Date_or_date_time_assignment" (urn:plcs:rdl:std:Date_or_date_time_assignment) | The name of the class being used to classify the role date assignment, e.g. the date when the Work_order was issued. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the date_name class items. | |
| year | ?year? | the year component of the start date and time of the related work order was raised | |
| month | ?month? | the month component of the start date and time of the related work order was raised | |
| day | ?day? | the day component of the start date and time of the related work order was raised | |
| hour | ?hour? | the hour component of the start date and time of the related work order was raised | |
| minute | ?minute? | the minute component of the start date and time of the related work order was raised | |
| second | ?second? | the second component of the start date and time of the related work order was raised | |
| sense | ?sense? | Three possible values: 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| act_id | ?act_id? | The version identifier assigned to the related work order | |
| act_id_class_name | "Activity_identification_code" (urn:plcs:rdl:std:Activity_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| act_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_id_class_name class | |
| act_org_id | ?act_org_id? | The identifier of the organization that "owns" the version identifier. | |
| act_org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization that "owns" the version identifier. For example CAGE code. | |
| act_org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_org_id_class_name class items. | |
| appr_status | "Approval_status" (urn:plcs:rdl:std:Approval_status) | The class name of the External_class corresponding to the approval status of the work order. | |
| appr_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the act_org_id_class_name class items. | |
| input | Product_as_individual_view | The reportable item that is the subject of the related work order. | |
| in_response_to | Work_request | The work request that caused the related work order. | |
| chosen_method | Activity_method | The method of satisfying the related work order. | |
The use of template #8 representing_promissory_usage in Figure 7 is identical to, and described in, template table: Template #2(Figure 17).
The use of template #9 representing_product_as_realized in Figure 7 is identical to, and described in, template table: Template #1(Figure 17).
| Template #10 (Figure 7): assigning_organization | |||
|---|---|---|---|
| Description | The identification of the organization conducting the maintenance under the work_order. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| org_id | ?org_id? | The identifier of the maintenance organization | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| org_assgn_class_name | "Maintainer_of" (urn:plcs:rdl:std:Maintainer_of) | The name of the class being used to classify the assignment of the organization. (Organization_or_person_in_organization_assignment) This provides the role or reason for the assignment. For example 'Owner_of'. | |
| org_assgn_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_assgn_class_name. | |
| items | Work_order | The items to which the organization is assigned | |
| Template #11 (Figure 7): assigning_reference_data | |||
|---|---|---|---|
| Description | A classification of the organization to show the line of repair | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | "Classification_assignment" (urn:plcs:rdl:std:Classification_assignment) | The name of the class in the reference data library (External_class) being used to classify something | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the definition for the class being used. | |
| items | Organization | The organization that is being classified, represented as an Organization | |
| Template #12 (Figure 7): assigning_asserted_state | |||
|---|---|---|---|
| Description | An assertion (verification) of a state of a work order. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| state_class_name | "State_definition" (urn:plcs:rdl:std:State_definition) | The class name of the External_class corresponding to the State_definition name. | |
| state_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @state_class_name. | |
| assigned_to | Work_order | The activity, product, individual, task_method, etc to which the state is assigned | |
| Template #13 (Figure 7): assigning_time | |||
|---|---|---|---|
| Description | The date and time the work_order was completed. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| date_class_name | "Date_actual_end" (urn:plcs:rdl:std:Date_actual_end) | The name of the class being used to classify the role date assignment, e.g. the start date. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library in which the date class is defined. | |
| year | ?year? | the year component of the actual end date and time of the work order | |
| month | ?month? | the month component of the actual end date and time of the work order | |
| day | ?day? | the day component of the actual end date and time of the work order | |
| hour | ?hour? | the hour component of the actual end date and time of the work order | |
| minute | ?minute? | the minute component of the actual end date and time of the work order | |
| second | ?second? | the second component of the actual end date and time of the work order | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| items | Work_order | The items to which the date is assigned. | |
| Template #14 (Figure 7): assigning_descriptor | |||
|---|---|---|---|
| Description | The description of the work order | ||
| Parameter name: | Parameter value: | Parameter description: | |
| descr | ?descr? | The description of the work order | |
| class_name | "Description" (urn:plcs:rdl:std:Description) | The name of the class (External_class) being used to determine type of descriptor. | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the class. | |
| is_assigned_to | Work_order | The work order that is being described, represented as a Work_order | |
| Template #15 (Figure 7): assigning_time | |||
|---|---|---|---|
| Description | The date and time the work was planned to start. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| date_class_name | "Date_planned_start" (urn:plcs:rdl:std:Date_planned_start) | The name of the class being used to classify the role date assignment, e.g. the start date. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library in which the date class is defined. | |
| year | ?year? | The 'year' component of the planned start date | |
| month | ?month? | The 'month' component of the planned start date | |
| day | ?day? | The 'day' component of the planned start date | |
| hour | ?hour? | The 'hour' component of the planned start date | |
| minute | ?minute? | The 'minute' component of the planned start date | |
| second | ?second? | The 'second' component of the planned start date | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| items | Work_order | The work order that is the date is for, represented as a Work_order | |
| Template #16 (Figure 7): assigning_time | |||
|---|---|---|---|
| Description | The date and time the work was planned to end. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| date_class_name | "Date_planned_end" (urn:plcs:rdl:std:Date_planned_end) | The name of the class being used to classify the role date assignment, e.g. the start date. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library in which the date class is defined. | |
| year | ?year? | The 'year' component of the planned end date | |
| month | ?month? | The 'month' component of the planned end date | |
| day | ?day? | The 'day' component of the planned end date | |
| hour | ?hour? | The 'hour' component of the planned end date | |
| minute | ?minute? | The 'minute' component of the planned end date | |
| second | ?second? | The 'second' component of the planned end date | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| items | Work_order | The work order that is the date is for, represented as a Work_order | |
The use of template #17 referencing_task in Figure 7 is identical to, and described in, template table: Template #2(Figure 9).
| Template #18 (Figure 7): assigning_reference_data | |||
|---|---|---|---|
| Description | The type of activity being ordered | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | For a controlled exchange activity, use "Controlled_exchange" (urn:plcs:rdl:std:Controlled_exchange) For an installation activity, use "Installation" (urn:plcs:rdl:std:Installation) For a lifing extension activity, use "Lifing_extension" (urn:plcs:rdl:std:Lifing_extension) For a maintenance activity, use "Maintenance" (urn:plcs:rdl:std:Maintenance) For a controlled exchange activity, use "Controlled_exchange" (urn:plcs:rdl:std:Controlled_exchange) For a part number type or serial number change activity, use "Fit_form_function_change" (urn:plcs:rdl:std:Fit_form_function_change) For a removal for access activity, use "Removal" (urn:plcs:rdl:std:Removal) For a repair or overhaul activity, use "Overhaul" (urn:plcs:rdl:std:Overhaul) For a scheduled task activity, use "Scheduled_task" (urn:plcs:rdl:std:Scheduled_task) | The name of the class in the reference data library (External_class) being used to classify something | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the definition for the class being used. | |
| items | Work_order | The work order that is the type of activity is for, represented as a Work_order | |
| Template #19 (Figure 7): assigning_organization | |||
|---|---|---|---|
| Description | The identification of the organization raising the maintenance under the work_order. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| org_id | ?org_id? | The identifier of the organization that raised the maintenance work order | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| org_assgn_class_name | "Maintainer_of" (urn:plcs:rdl:std:Maintainer_of) | The name of the class being used to classify the assignment of the organization. (Organization_or_person_in_organization_assignment) This provides the role or reason for the assignment. For example 'Owner_of'. | |
| org_assgn_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_assgn_class_name. | |
| items | Work_order | The items to which the organization is assigned | |
The Aviation maintenance DEX is used to report on a number of different maintenance activities performed on a reportable item. These are summarized in Section: Aviation maintenance - Reportable activities. and include:
The information necessary to record a maintenance activity performed on a Reportable item can be summarized by the UML class diagram shown in Figure 8.
NOTE The information shown in the UML class diagram in Figure 8 is intended to illustrate the type of information that can be represented by the DEX. It does not imply that all exchanges must contain this information.
The information detailed in the UML class diagram in Figure 8 is as follows:
The maintenance activity is a record of an activity that has been carried out on a product. It is represented in ISO 10303-239 PLCS by an Activity_actual, which is part of template #5 representing_work_done.
The type of activity that has been undertaken, such as maintenance, installation, repair/overhual is provided by classifying the Activity_actual by using template #24 assigning_reference_data. The approval status of the activity is given in template #25 assigning_approval.
The template #3 representing_work_order is used to represent a maintenance work order which is the authority to undertake the work. The template #1 representing_typical_activity is used identify the method used to perform the activity. The template #2 referencing_task can be used to identify the standard maintenance task that the method used to perform the activity was based on. A standard maintenance task is one where there is a set of procedures or a specification defined.
The reportable item that is the focus of the activity, and is input to the activity is represented by the template #4 representing_product_as_realized. If the activity causes a change of identification of the item, such as changes to the part number or serial number then this is represented by another instance of the template #6 representing_product_as_realized related to the template representing_work_done via the template #9 assigning_activity.
The maintenance activity is "characterized" by the date, represented by template assigning_time when the activity was actually started, template #12, and when the activity was reported, template #8, and by whom, represented by template assigning_person_in_organization, templates #23 and #7 respectively. The resources used to perform the activity are represented by template #13 representing_resource_item. Properties such as the time taken to perform the activity can also be recorded, represented by templates #14, #16, #18, #20 assigning_process_property and template #15, #17, #19, #21 process_property_numeric.
If any notes, remarks or comments are to be noted about the maintenance activity these are represented by template #22 assigning_descriptor.
The maintenance activity is described in template representing_work_done and shown in Figure 9 below.
The following templates are used in the diagram and represent the various types of information:
| Template #1 (Figure 9): representing_typical_activity | |||
|---|---|---|---|
| Description | The method used to perform the maintenance activity | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier of the method used. | |
| id_class_name | "Activity_method_identification_code" (urn:plcs:rdl:std:Activity_method_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the typical activity. This provides the role or reason for the identification. | |
| id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @id_class_name class. | |
| id_owner | ?id_owner? | The identifier of the owner owning the identifier of the method used. | |
| id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
| id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the @id_owner_class_name class | |
| type | "Typical_activity" (urn:plcs:rdl:std:Typical_activity) | The name of the class being used to classify the typical activity. | |
| type_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @type class. | |
| Template #2 (Figure 9): referencing_task | |||
|---|---|---|---|
| Description | The standard maintenance task used to perform the maintenance activity | ||
| Parameter name: | Parameter value: | Parameter description: | |
| task_id | ?task_id? | The identifier of the standard maintenance task. | |
| task_id_class_name | "Task_method_identification_code" (urn:plcs:rdl:std:Task_method_identification_code) | The class of the task method identifier. | |
| task_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @task_id_class_name. | |
| task_org_id | ?task_org_id? | The identifier of the organization that owns the standard maintenance task identifier. | |
| task_org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization responsible for creating the task specification | |
| task_org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class used to classify the organization identifier. | |
| task_ver_id | ?task_ver_id? | The identifier of the version of the standard maintenance task | |
| task_ver_id_class_name | "Version_identification_code" (urn:plcs:rdl:std:Version_identification_code) | The class of the task method version identifier. | |
| task_ver_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @task_ver_id_class_name. | |
| task_ver_org_id | ?task_org_id? | The identifier of the organization that owns the version of the standard maintenance task identifier. | |
| task_ver_org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization responsible for creating the task specification version. | |
| task_ver_org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class used to classify the organization identifier. | |
| task_vart_id | ?task_vart_id? | The identifier of the variant of the version of the standard maintenance task | |
| task_vart_id_class_name |
[Task_method_variant_identification_code]![[warning:]](../../../../images/dex/warning.gif){kind=small} Error RDL1: The class Task_method_variant_identification_code does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml |
The class of the task method variant identifier. | |
| task_vart_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @task_vart_id_class_name. | |
| task_vart_org_id | ?task_org_id? | The identifier of the organization that owns the variant of the version of the standard maintenance task identifier. | |
| task_vart_org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the variant identification (Identification_assignment) of the organization responsible for creating the task specification variant | |
| task_vart_org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class used to classify the organization identifier. | |
The use of template #3 representing_work_order in Figure 9 is identical to, and described in, template table: Template #4(Figure 7).
The use of template #4 representing_product_as_realized in Figure 9 is identical to, and described in, template table: Template #5(Figure 17) for the item that is the focus of the maintenance activity.
The use of template #5 representing_work_done in Figure 9 is identical to, and described in, template table: Template #3(Figure 7).
The use of template #6 representing_product_as_realized in Figure 9 is identical to, and described in, template table: Template #5(Figure 17) for the item that is the output of the maintenance activity when the identification information has changed, such as part number, serial number.
| Template #7 (Figure 9): assigning_person_in_organization | |||
|---|---|---|---|
| Description | Identification of the person reporting the activity. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| last_name | ?last_name? | The last name of the person reporting the activity | |
| first_name | ?first_name? | The first name of the person reporting the activity; use "unknown" when the information is not known to the sending system | |
| middle_names | ?middle_names? | The middle name of the person reporting the activity; use "unknown" when the information is not known to the sending system | |
| prefix_titles | ?prefix_titles? | The prefix title of the person reporting the activity; use "unknown" when the information is not known to the sending system | |
| suffix_titles | ?suffix_titles? | The suffix title of the person reporting the activity; use "unknown" when the information is not known to the sending system | |
| person_role_class_name | "Observer_of" (urn:plcs:rdl:std:Observer_of) | The name of the class being used to classify the person assignment () This provides the role for the assignment. | |
| person_role_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @person_role_class_name class. | |
| org_id | ?org_id? | The identifier of the organization in which the person reporting of the activity work. | |
| org_id_class_name | For a name identifying an organization, use "Organization_name" (urn:plcs:rdl:std:Organization_name) For a code identifying an organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name or code that identifies (Identification_assignment) an organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| items | Activity_actual | The activity to which the person is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #8 (Figure 9): assigning_time | |||
|---|---|---|---|
| Description | The date and time the activity was reported. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| date_class_name | "Date_actual" (urn:plcs:rdl:std:Date_actual) | The name of the class being used to classify the role date assignment, e.g. the start date. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library in which the date class is defined. | |
| year | ?year? | The 'year' component of the reporting date | |
| month | ?month? | The 'month' component of the reporting date | |
| day | ?day? | The 'day' component of the reporting date | |
| hour | ?hour? | The 'hour' component of the reporting date | |
| minute | ?minute? | The 'minute' component of the reporting date | |
| second | ?second? | The 'second' component of the reporting date | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| items | Activity_actual | The activity to which the date is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #9 (Figure 9): assigning_activity | |||
|---|---|---|---|
| Description | The association of the activities and the output subject of the activity, such as the reportable_item, etc. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| role_class_name | "Activity_output" (urn:plcs:rdl:std:Activity_output) | The class name of the External_class corresponding to the role of the assignment, e.g. "Activity_input" (urn:plcs:rdl:std:Activity_input), or "Activity_output" (urn:plcs:rdl:std:Activity_output). | |
| role_ecl_id | "urn:plcs:rdl:std" | The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name. | |
| assigned_activity | Activity_actual | This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| items | Product_as_realized | The activity, product, individual, task_method, etc that is being assigned to the activity. | |
| Template #12 (Figure 9): assigning_time | |||
|---|---|---|---|
| Description | The date and time the activity actually started. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| date_class_name | "Date_actual_start" (urn:plcs:rdl:std:Date_actual_start) | The name of the class being used to classify the role date assignment, e.g. the start date. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library in which the date class is defined. | |
| year | ?year? | The 'year' component of the actual start date | |
| month | ?month? | The 'month' component of the actual start date | |
| day | ?day? | The 'day' component of the actual start date | |
| hour | ?hour? | The 'hour' component of the actual start date | |
| minute | ?minute? | The 'minute' component of the actual start date | |
| second | ?second? | The 'second' component of the actual start date | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| items | Activity_actual | The activity to which the date is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #13 (Figure 9): representing_resource_item | |||
|---|---|---|---|
| Description | The resource used to perform the maintenance activity | ||
| Parameter name: | Parameter value: | Parameter description: | |
| resource_item_id |
?resource_item_id? | The identifier of the resource used. | |
| resource_item_id_class_name |
"Resource_item_identification_code" (urn:plcs:rdl:std:Resource_item_identification_code) | ||
| resource_item_id_ecl_id |
urn:plcs:rdl:std | ||
| resource_item_org_id |
?resource_item_org_id? | The identifier of the owner owning the identifier of the resource used. | |
| resource_item_org_id_class_name |
"Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | ||
| resource_item_org_id_ecl_id |
urn:plcs:rdl:std | ||
| resource_item_class_name |
"Material_resource_item" (urn:plcs:rdl:std:Material_resource_item) or id="Financial_resource_item" urn="urn:plcs:rdl:std"/> or id="Human_resource_item" urn="urn:plcs:rdl:std"/> as applicable | ||
| resource_item_ecl_id |
urn:plcs:rdl:std | ||
| res_items |
Activity_actual | The activity to which the resource is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #14 (Figure 9): assigning_process_property | |||
|---|---|---|---|
| Description | Assignment of properties to the activity, in this case the actual time, e.g. man hours, to perform the activity. This template assigns the property name, while template #15 process_property_numeric assigns the value and unit to a property instantiated by this template. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| property_class_name | "Actual_duration" (urn:plcs:rdl:std:Actual_duration) | The class name of the External_class corresponding to the property name. | |
| property_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @property_class_name. | |
| described_element | Activity_actual | The activity to which the property is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #15 (Figure 9): process_property_numeric | |||
|---|---|---|---|
| Description | Assigning the actual time, e.g. hours, value and unit to the activity property. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| value | ?value? | the actual value of the time taken to complete the activity | |
| unit | Where unit is in hours use: "hour" (urn:plcs:rdl:std:hour) Where unit is in minutes use: "minute" (urn:plcs:rdl:std:minute) Where unit is in seconds use: "second" (urn:plcs:rdl:std:second) Where unit is in days use: "day" (urn:plcs:rdl:std:day) | The class name of the unit in which the value is expressed. | |
| unit_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit. | |
| si_unit | "true" |
Value should be set to true if the unit is a SI base unit defined by ISO, i.e.
kilogram (kg) for Mass,
second (s) for Time,
metre (m) for Displacement,
ampere (A) for Electrical current,
kelvin (K) for Temperature,
mole (mol) for Amount of substance, and
candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false". |
|
| context | "Numerical_representation_context" | The name of the class being used to classify the representation context (Numerical_representation_context) of the property. | |
| context_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @context. | |
| property | The Activity_property entity instantiated by the template assigning_process_property. | The target of the template, i.e. the Activity_property (or template assigning_process_property) to which the Activity_property_representation is related. | |
| Template #16 (Figure 9): assigning_process_property | |||
|---|---|---|---|
| Description | Assignment of properties to the activity, in this case the expected time, e.g. man hours, to perform the activity. This template assigns the property name, while template #17 process_property_numeric assigns the value and unit to a property instantiated by this template. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| property_class_name | "Planned_duration" (urn:plcs:rdl:std:Planned_duration) | The class name of the External_class corresponding to the property name. | |
| property_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @property_class_name. | |
| described_element | Activity_actual | The activity to which the property is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #17 (Figure 9): process_property_numeric | |||
|---|---|---|---|
| Description | Assigning the expected time, e.g. hours, value and unit to the activity property. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| value | ?value? | the expected value of the time taken to complete the activity | |
| unit | Where unit is in hours use: "hour" (urn:plcs:rdl:std:hour) Where unit is in minutes use: "minute" (urn:plcs:rdl:std:minute) Where unit is in seconds use: "second" (urn:plcs:rdl:std:second) Where unit is in days use: "day" (urn:plcs:rdl:std:day) | The class name of the unit in which the value is expressed. | |
| unit_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit. | |
| si_unit | "true" |
Value should be set to true if the unit is a SI base unit defined by ISO, i.e.
kilogram (kg) for Mass,
second (s) for Time,
metre (m) for Displacement,
ampere (A) for Electrical current,
kelvin (K) for Temperature,
mole (mol) for Amount of substance, and
candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false". |
|
| context | "Numerical_representation_context" | The name of the class being used to classify the representation context (Numerical_representation_context) of the property. | |
| context_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @context. | |
| property | The Activity_property entity instantiated by the template assigning_process_property. | The target of the template, i.e. the Activity_property (or template assigning_process_property) to which the Activity_property_representation is related. | |
| Template #18 (Figure 9): assigning_process_property | |||
|---|---|---|---|
| Description | Assignment of properties to the activity, in this case the time, e.g. man hours, accomplished on the activity. This template assigns the property name, while template #19 process_property_numeric assigns the value and unit to a property instantiated by this template. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| property_class_name | "Elapsed_duration" (urn:plcs:rdl:std:Elapsed_duration) | The class name of the External_class corresponding to the property name. | |
| property_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @property_class_name. | |
| described_element | Activity_actual | The activity to which the property is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #19 (Figure 9): process_property_numeric | |||
|---|---|---|---|
| Description | Assigning the accomplished time, e.g. hours, value and unit to the activity property. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| value | ?value? | the value of the time accomplished on the activity | |
| unit | Where unit is in hours use: "hour" (urn:plcs:rdl:std:hour) Where unit is in minutes use: "minute" (urn:plcs:rdl:std:minute) Where unit is in seconds use: "second" (urn:plcs:rdl:std:second) Where unit is in days use: "day" (urn:plcs:rdl:std:day) | The class name of the unit in which the value is expressed. | |
| unit_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit. | |
| si_unit | "true" |
Value should be set to true if the unit is a SI base unit defined by ISO, i.e.
kilogram (kg) for Mass,
second (s) for Time,
metre (m) for Displacement,
ampere (A) for Electrical current,
kelvin (K) for Temperature,
mole (mol) for Amount of substance, and
candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false". |
|
| context | "Numerical_representation_context" | The name of the class being used to classify the representation context (Numerical_representation_context) of the property. | |
| context_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @context. | |
| property | The Activity_property entity instantiated by the template assigning_process_property. | The target of the template, i.e. the Activity_property (or template assigning_process_property) to which the Activity_property_representation is related. | |
| Template #20 (Figure 9): assigning_process_property | |||
|---|---|---|---|
| Description | Assignment of properties to the activity, in this case the percentage complete of the activity. This template assigns the property name, while template #21 process_property_numeric assigns the value and unit to a property instantiated by this template. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| property_class_name | "Percentage_complete" (urn:plcs:rdl:std:Percentage_complete) | The class name of the External_class corresponding to the property name. | |
| property_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @property_class_name. | |
| described_element | Activity_actual | The activity to which the property is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #21 (Figure 9): process_property_numeric | |||
|---|---|---|---|
| Description | Assigning the percentage complete value and unit to the activity property. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| value | ?value? | The value of the percentage complete of the activity | |
| unit | "Percentage" (urn:plcs:rdl:std:Percentage) | The class name of the unit in which the value is expressed. | |
| unit_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit. | |
| si_unit | "true" |
Value should be set to true if the unit is a SI base unit defined by ISO, i.e.
kilogram (kg) for Mass,
second (s) for Time,
metre (m) for Displacement,
ampere (A) for Electrical current,
kelvin (K) for Temperature,
mole (mol) for Amount of substance, and
candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false". |
|
| context | "Numerical_representation_context" | The name of the class being used to classify the representation context (Numerical_representation_context) of the property. | |
| context_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @context. | |
| property | The Activity_property entity instantiated by the template assigning_process_property. | The target of the template, i.e. the Activity_property (or template assigning_process_property) to which the Activity_property_representation is related. | |
| Template #22 (Figure 9): assigning_descriptor | |||
|---|---|---|---|
| Description | Describes the work done on the activity. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| descr | ?descr? | the description of the work done on the activity | |
| class_name | "Description" (urn:plcs:rdl:std:Description) | The name of the class (External_class) being used to determine type of descriptor. | |
| ecl_id | "urn:plcs:rdl:std" | The id of the External_class_library that stores the class. | |
| is_assigned_to | Activity_actual | The activity to which the description is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #23 (Figure 9): assigning_person_in_organization | |||
|---|---|---|---|
| Description | Identification of the person performing the activity. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| last_name | ?last_name? | The last name of the person performing the activity | |
| first_name | ?first_name? | The first name of the person performing the activity; use "unknown" when the information is not known to the sending system | |
| middle_names | ?middle_names? | The middle name of the person performing the activity; use "unknown" when the information is not known to the sending system | |
| prefix_titles | ?prefix_titles? | The prefix title of the person performing the activity; use "unknown" when the information is not known to the sending system | |
| suffix_titles | ?suffix_titles? | The suffix title of the person performing the activity; use "unknown" when the information is not known to the sending system | |
| person_role_class_name | "Observer_of" (urn:plcs:rdl:std:Observer_of) | The name of the class being used to classify the person assignment () This provides the role for the assignment. | |
| person_role_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @person_role_class_name class. | |
| org_id | ?org_id? | The identifier of the organization in which the person performing of the activity work. | |
| org_id_class_name | For a name identifying an organization, use "Organization_name" (urn:plcs:rdl:std:Organization_name) For a code identifying an organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name or code that identifies (Identification_assignment) an organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| items | Activity_actual | The activity to which the person is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #24 (Figure 9): assigning_reference_data | |||
|---|---|---|---|
| Description | The type of activity performed | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | For a controlled exchange activity, use "Controlled_exchange" (urn:plcs:rdl:std:Controlled_exchange) For an installation activity, use "Installation" (urn:plcs:rdl:std:Installation) For a lifing extension activity, use "Lifing_extension" (urn:plcs:rdl:std:Lifing_extension) For a maintenance activity, use "Maintenance" (urn:plcs:rdl:std:Maintenance) For a controlled exchange activity, use "Controlled_exchange" (urn:plcs:rdl:std:Controlled_exchange) For a part number type or serial number change activity, use "Fit_form_function_change" (urn:plcs:rdl:std:Fit_form_function_change) For a removal for access activity, use "Removal" (urn:plcs:rdl:std:Removal) For a repair or overhaul activity, use "Overhaul" (urn:plcs:rdl:std:Overhaul) For a scheduled task activity, use "Scheduled_task" (urn:plcs:rdl:std:Scheduled_task) | The name of the class in the reference data library (External_class) being used to classify something | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the definition for the class being used. | |
| items | Activity_actual | The activity to which the activity type is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
| Template #25 (Figure 9): assigning_approval | |||
|---|---|---|---|
| Description | The approval of activity performed | ||
| Parameter name: | Parameter value: | Parameter description: | |
| status | For a not yet approved activity, use "Not_yet_approved" (urn:plcs:rdl:std:Not_yet_approved) For an approved activity, use "Approved" (urn:plcs:rdl:std:Approved) For an activity that is approved but with a concession, use "Approved_with_concession" (urn:plcs:rdl:std:Approved_with_concession) For an activity that has had its approval rejected, use "Rejected" (urn:plcs:rdl:std:Rejected) For an activity that has had its approval withdrawn, use "Withdrawn" (urn:plcs:rdl:std:Withdrawn) | The name of the class being used to classify the status (Approval_status) of the approval. | |
| status_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @status class. | |
| items | Activity_actual | The activity to which the approval is assigned. This is the activity that is represented as a Activity_actual which is part of template representing_work_done. | |
The subject of the activity that is referenced in the Aviation Maintenance messages is referred to as the reportable item. It is normally the aircraft or component on the aircraft on which the activity was undertaken.
The reportable item is identified by the part number, serial number, NSN number and the CAGE code of the organization that manufactured the part, as shown in Figure 10
NOTE The information shown in the UML class diagram in Figure 10 is intended to illustrate the type of information that can be represented by the DEX. It does not imply that all exchanges must contain this information.
The information detailed in the UML class diagram in Figure 10 is as follows:
NOTE The supply code is the code identifying the manufacturer/supplier. Often CAGE code. The manufacturer/supplier "owns" the Part number.
The reportable item is a physical product, therefore is represented in ISO 10303-239 PLCS by a Product_as_individual. This is described in the capability C045: representing_product_as_individual.
The serial number is the identification of the Product_as_individual and is represented by an Identification_assignment represented by template #6 assigning_identification and classified as "Serial_identification_code" (urn:plcs:rdl:std:Serial_identification_code). Occasionally a serial number will have to change therefore the dates that a serial number is valid for is represented by template #7 assigning_dated_effectivity.
Each Product_as_individual has a version, represented by a Product_as_realized.
The part number identifies the part type or design from which the reportable item was manufactured. In ISO 10303-239 PLCS the part type is represented by a Part (For details see the capability C002: representing_parts) which is identified by the part number. The identification is represented by template #1 assigning_identification assigned to the Part and classified as a "Part_identification_code" (urn:plcs:rdl:std:Part_identification_code). The dates that a part number is valid for is represented by template #2 assigning_dated_effectivity. The part can have a description recorded and this is represented by template #5 assigning_descriptor.
The NSN is a classification of the fit, form and function, or interchangeability of the part, therefore the NSN is treated as a classification of the part. This is represented by the template #4 : assigning_reference_data classifying the part by an "NSN_code" (urn:plcs:rdl:std:NSN_code).
A link is maintained between the representation of an actual product, (Product_as_individual) and the part type or design which is represented by a Part by instantiating a Product_design_to_individual.
The owning organization and the supplier organization are represented by assigning instances of template assigning_organization , templates #11 and #12 respectively, to the Product_as_individual. The assignments are classified as either "Owner_of" (urn:plcs:rdl:std:Owner_of) and "Manufacturer_of" (urn:plcs:rdl:std:Manufacturer_of) to indicate that the organization is the owner or manufacturer of the part.
Template #10, representing_work_done is used to show the activity that changed the Product_as_realized that was authorised by template #9, representing_work_order.
NOTE To clarify understanding the information has been described in full above and in the figure below, however, it is advisable to use the template representing_product_as_realized which contains the majority of this data to simplify implementations.
An EXPRESS-G diagram showing how the reportable item is identified is shown below.
The following templates are used in the diagram and represent the various messages:
| Template #1 (Figure 11): assigning_identification | |||
|---|---|---|---|
| Description | The Part number (identifier) of the reportable item. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The part number of the reportable item | |
| id_class_name | "Part_identification_code" (urn:plcs:rdl:std:Part_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the id_class_name class | |
| org_id | ?org_id? | The identifier or name of the organization that "owns" the identifier. | |
| org_id_class_name | For a name identifying an organization, use "Organization_name" (urn:plcs:rdl:std:Organization_name) For a code identifying an organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) For a CAGE code identifying an organization, use "CAGE_code" (urn:plcs:rdl:std:CAGE_code) | The name of the class being used to classify the identification of the organization. For example CAGE code. | |
| org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the org_id_class_name class items. | |
| items | Part | The part that is being identified (and reported on by a message), represented as a Part. | |
| Template #2 (Figure 11): assigning_dated_effectivity | |||
|---|---|---|---|
| Description | The start and end date of the Part number (identifier) of the reportable item. Only used for 'Part Number, Part type or Serial number Change' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| start_year | ?start_year? | The year the part number was effective from | |
| start_month | ?start_month? | The month the part number was effective from | |
| start_day | ?start_day? | The day the part number was effective from | |
| start_hour | ?start_hour? | The hour the part number was effective from | |
| start_minute | ?start_minute? | The minute the part number was effective from | |
| start_second | ?start_second? | The second the part number was effective from | |
| start_sense | ?start_sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| start_hour_offset | ?start_hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| start_minute_offset | ?start_minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| end_year | ?end_year? | The year the part number was effective to | |
| end_month | ?end_month? | The month the part number was effective to | |
| end_day | ?end_day? | The day the part number was effective to | |
| end_hour | ?end_hour? | The hour the part number was effective to | |
| end_minute | ?minute? | The minute the part number was effective to | |
| end_second | ?end_second? | The second the part number was effective to | |
| end_sense | ?end_sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| end_hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| end_minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| role_class_name | "Actual_effectivity" (urn:plcs:rdl:std:Actual_effectivity) | The name of the class being used to classify the effectivity assignment (Effectivity_assignment) This provides the role for the assignment. | |
| role_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name class. | |
| items | Part | The part that is being identified (and reported on by a message), represented as a Part. | |
| Template #4 (Figure 11): assigning_reference_data | |||
|---|---|---|---|
| Description | The National Stock Number (NSN) of the reportable item. Only used for Part Number, Part type or Serial number Change' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | ?class_name? | The National Stock Number (NSN) of the item. | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the definition for the class being used. | |
| items | Part | The part that is being identified by NSN (and reported on by a message), represented as a Part. | |
| Template #5 (Figure 11): assigning_descriptor | |||
|---|---|---|---|
| Description | The description of the reportable item. Only used for 'Part type or Serial number Change' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| descr | ?descr? | The description of the reportable item | |
| class_name | "Description" (urn:plcs:rdl:std:Description) | The name of the class (External_class) being used to determine type of descriptor. | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the class. | |
| is_assigned_to | Part | The part that is being described (and reported on by a message), represented as a Part. | |
| Template #6 (Figure 11): assigning_identification | |||
|---|---|---|---|
| Description | The serial number of the reportable item. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The serial number of the reportable item. | |
| id_class_name | "Serial_identification_code" (urn:plcs:rdl:std:Serial_identification_code) | The name of the class used to classify the identifier and so provide the role or reason for the identification. | |
| id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the id_class_name class | |
| org_id | ?org_id? | The identifier or name of the organization that "owns" the identifier. | |
| org_id_class_name | For a name identifying an organization, use "Organization_name" (urn:plcs:rdl:std:Organization_name) For a code identifying an organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) For a CAGE code identifying an organization, use "CAGE_code" (urn:plcs:rdl:std:CAGE_code) | The name of the class being used to classify the identification of the organization. For example CAGE code. | |
| org_id_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the org_id_class_name class items. | |
| items | Product_as_individual | The individual product that is being identified (and reported on by a message), represented as a Product_as_individual. | |
| Template #7 (Figure 11): assigning_dated_effectivity | |||
|---|---|---|---|
| Description | The start and end date of the serial number of the reportable item. Only used for 'Part Number, Part type or Serial number Change' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| start_year | ?start_year? | The year the serial number was effective from | |
| start_month | ?start_month? | The month the serial number was effective from | |
| start_day | ?start_day? | The day the serial number was effective from | |
| start_hour | ?start_hour? | The hour the serial number was effective from | |
| start_minute | ?start_minute? | The minute the serial number was effective from | |
| start_second | ?start_second? | The second the serial number was effective from | |
| start_sense | ?start_sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| start_hour_offset | ?start_hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| start_minute_offset | ?start_minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| end_year | ?end_year? | The year the serial number was effective to | |
| end_month | ?end_month? | The month the serial number was effective to | |
| end_day | ?end_day? | The day the serial number was effective to | |
| end_hour | ?end_hour? | The hour the serial number was effective to | |
| end_minute | ?minute? | The minute the serial number was effective to | |
| end_second | ?end_second? | The second the serial number was effective to | |
| end_sense | ?end_sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| end_hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| end_minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| role_class_name | "Actual_effectivity" (urn:plcs:rdl:std:Actual_effectivity) | The name of the class being used to classify the effectivity assignment (Effectivity_assignment) This provides the role for the assignment. | |
| role_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name class. | |
| items | assigning_identification | The serial number of the part that is being identified (and reported on by a message). | |
The use of template #9 representing_work_order in Figure 11 is identical to, and described in, template table: Template #4(Figure 7).
The use of template #10 representing_work_done in Figure 11 is identical to, and described in, template table: Template #3(Figure 7).
| Template #11 (Figure 11): assigning_organization | |||
|---|---|---|---|
| Description | The identification of the organization that owns the reportable item. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| org_id | ?org_id? | The identifier of the owning organization | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| org_assgn_class_name | "Owner_of" (urn:plcs:rdl:std:Owner_of) | The name of the class being used to classify the assignment of the organization. (Organization_or_person_in_organization_assignment) This provides the role or reason for the assignment. For example 'Owner_of'. | |
| org_assgn_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_assgn_class_name. | |
| items | Product_as_individual | The individual product that the organization owns, represented as a Product_as_individual. | |
| Template #12 (Figure 11): assigning_organization | |||
|---|---|---|---|
| Description | The identification of the organization that manufactures the reportable item. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| org_id | ?org_id? | The identifier of the manufacturing organization | |
| org_id_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization. | |
| org_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| org_assgn_class_name | "Manufacturer_of" (urn:plcs:rdl:std:Manufacturer_of) | The name of the class being used to classify the assignment of the organization. (Organization_or_person_in_organization_assignment) This provides the role or reason for the assignment. For example 'Owner_of'. | |
| org_assgn_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_assgn_class_name. | |
| items | Product_as_individual | The individual product that the organization manufactures, represented as a Product_as_individual. | |
The messages can contain a number of properties of the reportable item, such as the aircraft hours, the hours since last repair.
The information necessary to record properties of the reportable item can be summarized by the UML class diagram shown in Figure 12.
NOTE The information shown in the UML class diagram in Figure 12 is intended to illustrate the type of information that can be represented by the DEX. It does not imply that all exchanges must contain this information.
The information detailed in the UML class diagram in Figure 12 is as follows:
The messages can contain a number of properties of the reportable item, such as the aircraft hours, the hours since last repair. These are represented as properties in ISO 10303-239 PLCS and are described in the capability C076: assigning_product_properties and detailed in the templates #3 assigning_product_property and #4 and #8 product_property_numeric.
The template #3 assigning_product_property is used to assign a named property to the product. The name of the property is provided by reference data. The template #4 product_property_numeric is used to represent the value of the property and its unit. The template #8 product_property_numeric is used to represent the value of the increment of the property and its unit since the last usage. The relationship of template #8, the increment of the property value, to template #4, the new property value and unit is through template #9 property_value_relationship.
The value type is represented by template #7 assigning_reference_data. The organization declaring the property is represented by template #6 assigning_organization and the date and time the property is declared is represented by template #5 assigning_time.
In ISO 10303-239 PLCS properties on a product are specified in a given context or view on a version of product, for example, the design cost properties would be represented in the design view. The context dependent view of a version Product_as_realized is represented by a Product_as_individual_view and an associated context represented by a View_definition_context. The context is classified according to the life cycle stage, represented by template #1 assigning_reference_data and application domain represented by template #2 assigning_reference_data. For the messages the life cycle stage could be either: "Concept_stage" (urn:plcs:rdl:std:Concept_stage), "Development_stage" (urn:plcs:rdl:std:Development_stage), "Production_stage" (urn:plcs:rdl:std:Production_stage) , "Retirement_stage" (urn:plcs:rdl:std:Retirement_stage), "Support_stage" (urn:plcs:rdl:std:Support_stage) or "Utilization_stage" (urn:plcs:rdl:std:Utilization_stage) and the application domain is "Product_life_cycle_support" (urn:plcs:rdl:std:Product_life_cycle_support)
NOTE To clarify understanding the information has been described in full above and in the figure below, however, it is advisable to use the template representing_product_as_realized which contains some of this data to simplify implementations.
An EXPRESS-G diagram showing how properties on a reportable item are represented is shown below in Figure 13.
The following templates are used in the diagram and represent the various messages:
| Template #1 (Figure 13): assigning_reference_data | |||
|---|---|---|---|
| Description | The life cycle state in which the product_as_individual is. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | Use the applicable life cycle stage "Concept_stage" (urn:plcs:rdl:std:Concept_stage), "Development_stage" (urn:plcs:rdl:std:Development_stage), "Production_stage" (urn:plcs:rdl:std:Production_stage) , "Retirement_stage" (urn:plcs:rdl:std:Retirement_stage), "Support_stage" (urn:plcs:rdl:std:Support_stage) or "Utilization_stage" (urn:plcs:rdl:std:Utilization_stage) | The name of the class in the reference data library (External_class) being used to classify something | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the definition for the class being used. | |
| items | View_definition_context | The items to which the External_class is assigned. | |
| Template #2 (Figure 13): assigning_reference_data | |||
|---|---|---|---|
| Description | The application domain to which this information pertains. Should always be set to the same value. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | "Product_life_cycle_support" (urn:plcs:rdl:std:Product_life_cycle_support) | The name of the class in the reference data library (External_class) being used to classify something | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the definition for the class being used. | |
| items | View_definition_context | The items to which the External_class is assigned. | |
| Template #3 (Figure 13): assigning_product_property | |||
|---|---|---|---|
| Description | Properties can be assigned to individual products through this template. The value of the property is given in template table: Template #4(Figure 13). The previous value of the property is given in template table: Template #8(Figure 13). | ||
| Parameter name: | Parameter value: | Parameter description: | |
| property_class_name | ?property_class_name? | The name of the property | |
| property_ecl_id | ?urn:plcs:rdl:AVM? - the URN for the reference data library storing the class. | The identifier of the External_class_library storing the definition of the class referenced by the parameter @property_class_name. | |
| described_element | Product_as_individual_view | The item to which the property is assigned | |
| Template #4 (Figure 13): product_property_numeric | |||
|---|---|---|---|
| Description | Used to assign property values to properties instantiated e.g. in the template assigning_product_property. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| value | ?value? | The value of the property | |
| unit | ?unit? | The unit that the property value is measured in | |
| unit_ecl_id | ?urn:plcs:rdl:AVM? - the URN for the reference data library storing the class. | The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit. | |
| si_unit | "True" or "False" |
Value should be set to true if the unit is a SI base unit defined by ISO, i.e.
kilogram (kg) for Mass,
second (s) for Time,
metre (m) for Displacement,
ampere (A) for Electrical current,
kelvin (K) for Temperature,
mole (mol) for Amount of substance, and
candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false". |
|
| context | "Numerical_representation_context" (urn:plcs:rdl:std:Numerical_representation_context) | The name of the class being used to classify the representation context (Numerical_representation_context) of the property. | |
| context_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @context. | |
| property | The Assigned_property entity instantiated by the template assigning_product_property. | The target of the template, i.e. the Assigned_property (or template assigning_product_property) to which the Property_representation is related. | |
| Template #5 (Figure 13): assigning_time | |||
|---|---|---|---|
| Description | Creation date and time for property value. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| date_class_name | "Date_actual_observation" (urn:plcs:rdl:std:Date_actual_observation) | The name of the class being used to classify the role date assignment, e.g. the start date. | |
| date_ecl_id | urn:plcs:rdl:std | The id of the External_class_library in which the date class is defined. | |
| year | ?year? | the year component of the creation date of the property value | |
| month | ?month? | the month component of the creation date of the property value | |
| day | ?day? | the day component of the creation date of the property value | |
| hour | ?hour? | the hour component of the creation date of the property value | |
| minute | ?minute? | the minute component of the creation date of the property value | |
| second | ?second? | the second component of the creation date of the property value | |
| sense | ?sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| items | Property_value_representation | TheProperty_value_representation represented by template product_property_numeric | |
| Template #6 (Figure 13): assigning_organization | |||
|---|---|---|---|
| Description | Identification of the organization declaring the property.' | ||
| Parameter name: | Parameter value: | Parameter description: | |
| org_id | ?org_id? | The identifier or name of the organization that "owns" the identifier. | |
| org_id_class_name | For a name identifying an organization, use "Organization_name" (urn:plcs:rdl:std:Organization_name) For a code identifying an organization, use "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) For a CAGE code identifying an organization, use "CAGE_code" (urn:plcs:rdl:std:CAGE_code) | The name of the class being used to classify the identification (Identification_assignment) of the organization. This provides the role or reason for the identification. For example CAGE code. | |
| org_id_ecl_id | "urn:plcs:rdl:std'" for identified organizations. | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class. | |
| org_assgn_class_name | "Observer_of" (urn:plcs:rdl:std:Observer_of) | The name of the class being used to classify the identification (Identification_assignment) of the organization. This provides the role or reason for the identification. | |
| org_assgn_ecl_id | "urn:plcs:rdl:std'" for identified organizations. | The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_assgn_class_name. | |
| items | Property_value_representation | TheProperty_value_representation represented by template product_property_numeric | |
| Template #7 (Figure 13): assigning_reference_data | |||
|---|---|---|---|
| Description | The value type of the property. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | ?class_name? | The value type of the property | |
| ecl_id | ?urn:plcs:rdl:AVM? - the URN for the reference data library storing the class. | The id of the External_class_library that stores the definition for the class being used. | |
| items | Property_value_representation | TheProperty_value_representation represented by template product_property_numeric | |
| Template #8 (Figure 13): product_property_numeric | |||
|---|---|---|---|
| Description | Used to identify a properties variance to previous values to properties instantiated e.g. in the template assigning_product_property. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| value | ?value? | The increment value from the previous property value | |
| unit | ?unit? | The unit the increment value is measured in | |
| unit_ecl_id | ?urn:plcs:rdl:AVM? - the URN for the reference data library storing the class. | The identifier of the External_class_library storing the definition of the class referenced by the parameter @unit. | |
| si_unit | "True" or "False" |
Value should be set to true if the unit is a SI base unit defined by ISO, i.e.
kilogram (kg) for Mass,
second (s) for Time,
metre (m) for Displacement,
ampere (A) for Electrical current,
kelvin (K) for Temperature,
mole (mol) for Amount of substance, and
candela (cd) for Luminous intensity. If this is not the case it should be set to false.
Note that the representation of true and false depends on exchange format. In Part 11 (a STEP file) true is represented by the string ".T.", and false by ".F.", while in Part 28 (XML) they are represented by text strings "true" and "false". |
|
| context | "Numerical_representation_context" (urn:plcs:rdl:std:Numerical_representation_context) | The name of the class being used to classify the representation context (Numerical_representation_context) of the property. | |
| context_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @context. | |
| property | The Assigned_property entity instantiated by the template assigning_product_property. | The target of the template, i.e. the Assigned_property (or template assigning_product_property) to which the Property_representation is related. | |
| Template #9 (Figure 13): property_value_relationship | |||
|---|---|---|---|
| Description | The relationship of the property's new value to the property's incremented (previous) value. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| rel_type | "Succession_relationship" (urn:plcs:rdl:std:Succession_relationship) | Type of relation between property value representations. | |
| rel_type_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @rel_type. | |
| relating | Property_value_representation | TheProperty_value_representation represented by template product_property_numeric identified at template #4 | |
| related | Property_value_representation | TheProperty_value_representation represented by template product_property_numeric identified at template #8 | |
During a maintenance activity, parts (spares) fitted to the aircraft may be replaced. These are listed and related to the activity that was responsible for fitting them. The information required to represent the parts and the maintenance activity can be summarized by the UML class diagram shown in Figure 14.
NOTE These parts are treated as spares and the installation history is not necessarily tracked. If installation history is required, see: Section: Business information.
NOTE The information shown in the UML class diagram in Figure 14 is intended to illustrate the type of information that can be represented by the DEX. It does not imply that all exchanges must contain this information.
The information detailed in the UML class diagram in Figure 14 is as follows:
NOTE The supply code is the code identifying the manufacturer/supplier. Often CAGE code. The manufacturer/supplier "owns" the Part number.
The non trackable parts (spares) fitted to the aircraft during a maintenance activity are represented in the Aviation Maintenance DEX as Resource_item.
Activities to be performed on a product are frequently defined as tasks or maintenance procedures. These are developed as part of the support solution for a product. These tasks specifications provide a structured description of how to perform a maintenance activity and detail the resources that are required. In ISO 10303-239 PLCS tasks are represented by Task_element_assignment described in C015: representing_task. The reason for the replacement is given in template #1 assigning_reference_data. The resources required to perform the task are represented by Resource_item as described in C052: representing_resource. The actual resource that was used to perform the task is represented by Resource_as_realized as described in C085: representing_resource_as_realized.
During a maintenance activity, parts (spares) fitted to the aircraft may be replaced. These are represented in the Aviation Maintenance DEX as Resource_as_realized. The quantity of repaired or replaced items is described in template #2 representing_count. Reference to the task specification is out of scope of the Aviation Maintenance DEX, so a list of the parts that were replaced during an activity are represented. This is represented in ISO 10303-239 PLCS by a set of Resource_as_realized and Resource_item as shown in Figure 15.
The Resource_item represents a resource - something that is required to perform a task. For example tools or spare parts. The Resource_as_realized represents the actual resource that was used during the activity, a particular part - the parts that were replaced.
NOTE To clarify understanding the information has been described in full above and in the figure below, however, it is advisable to use the template referencing_resource_as_realized which contains some of this data to simplify implementations.
The following templates are used in the diagram and represent the various messages:
| Template #1 (Figure 15): assigning_reference_data | |||
|---|---|---|---|
| Description | The reason the replacement | ||
| Parameter name: | Parameter value: | Parameter description: | |
| class_name | ?class_name? | The reason for the replacement | |
| ecl_id | urn:plcs:rdl:std | The id of the External_class_library that stores the definition for the class being used. | |
| items | Resource_as_realized_assignment | The items to which the External_class is assigned. | |
| Template #2 (Figure 15): representing_count | |||
|---|---|---|---|
| Description | Quantity of repaired or replaced items | ||
| Parameter name: | Parameter value: | Parameter description: | |
| value | ?value? | The quantity of repaired or replaced items | |
Some maintenance tasks result in the installation or removal of reportable item on an aircraft. Where the reportable item is a trackable items, it is necessary to maintain the history of the installation and removal, i.e. maintain a record of which part was fitted when. The information required to represent the installation history of parts can be summarized by the UML class diagram shown in Figure 16.
NOTE The information shown in the UML class diagram in Figure 16 is intended to illustrate the type of information that can be represented by the DEX. It does not imply that all exchanges must contain this information.
The information detailed in the UML class diagram in Figure 16 is as follows:
Some maintenance tasks result in the installation or removal of the reportable items, represented by template #5 representing_product_as_realized as described in Section: Representing a reportable item., on an aircraft.
The reportable item's installation or removal activity is represented by template #3 representing_work_done. The serial number which identifies the specific reportable item, and the NSN which classifies it, are represented respectively by template #7 assigning_identification and template #8 assigning_reference_data. The properties and the observed state of the reportable item at time of installation or removal are represented respectively by template #9 assigning_product_property and template #10 assigning_assessed_state.
The position of the reportable item on the aircraft is represented in the Aviation maintenance DEX by referring to the next higher assembly and the aircraft (or end item) from which the reportable item is removed/installed. The next higher assembly and the aircraft (or end item) are treated like any other product and are therefore represented by instances of Product_as_individuals described by template #6 and template #1 respectively; representing_product_as_realized.
The relationship between the reportable item and the next higher assembly is represented by a Next_assembly_usage This is described in the capability C003: representing_assembly_structure and represented by template#4 representing_assembly_structure . Each date when the installation / removal occurs is represented by a (Dated_effectivity), described by template #12 assigning_dated_effectivity, applied to the Next_assembly_usage.
The relationship between the reportable item and the aircraft (or end item) is represented by template#2 representing_promissory_usage. Each date when the installation / removal occurs is represented by a (Dated_effectivity), described by template #11 assigning_dated_effectivity, applied to the representing_promissory_usage.
The reportable item can be installed or removed from a series of aircraft and is represented by a Promissory_usage.
An EXPRESS-G diagram showing how the installation or removal of the reportable item on the aircraft is represented is shown below.
The following templates are used in the diagram and represent the various messages:
| Template #1 (Figure 17): representing_product_as_realized | |||
|---|---|---|---|
| Description | This template identifies the end items. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier of the individual product | |
| id_class_name | "Product_as_individual_identification_code" (urn:plcs:rdl:std:Product_as_individual_identification_code) | The identifier of the individual product | |
| id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @id_class_name class. | |
| id_owner | ?id_owner? | indicates the name or identifier of the organisation the id or name | |
| id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The identifier of the individual product | |
| id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the @id_owner_class_name class | |
| vn_id | ?vn_id? | The identifier of the individual product version | |
| vn_id_class_name | "Version_identification_code" (urn:plcs:rdl:std:Version_identification_code) | The identifier of the individual product version | |
| vn_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @vn_id_class_name class. | |
| vn_id_owner | ?id_owner? | indicates the name or identifier of the organisation the id or name | |
| vn_id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The identifier of the individual product | |
| vn_id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the @vn_id_owner_class_name class | |
| life_cycle_stage | "Life_cycle_stage" (urn:plcs:rdl:std:Life_cycle_stage) | The identifier of the individual product | |
| life_cycle_stage_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @life_cycle_stage class. | |
| domain | "Application_domain" (urn:plcs:rdl:std:Application_domain) | A classification of the planned activity. | |
| domain_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @domain class. | |
| type_id | ?type_id? | The identifier of the product, e.g part number | |
| type_id_class_name | "Part_identification_code" (urn:plcs:rdl:std:Part_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the design (e.g. Part). This provides the role or reason for the identification. | |
| type_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @type_id_class_name class. | |
| type_id_owner | ?type_id_owner? | indicates the name or identifier of the organisation the type_id | |
| type_id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
| Template #2 (Figure 17): representing_promissory_usage | |||
|---|---|---|---|
| Description | This template identifies the relationship between end item and child reportable items. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| quantity | "unknown" | quantity of child in the end item assembly | |
| top_level_part | Product_as_individual_view | This represents the Product_as_individual_view of the end item represented by template Product_as_individual_view | |
| consistuent_part | Product_as_individual_view | This represents the Product_as_individual_view of the reportable item represented by template Product_as_individual_view | |
The use of template #3 representing_work_done in Figure 17 is identical to, and described in, template table: Template #3(Figure 7).
| Template #4 (Figure 17): representing_assembly_structure | |||
|---|---|---|---|
| Description | This template identifies the relationship between parent and child assets | ||
| Parameter name: | Parameter value: | Parameter description: | |
| location_indicator | "unknown" | indicates the location of the child in the parent assembly | |
| quantity | "unknown" | quantity of child in the parent assembly | |
| parent | Product_as_individual_view | This represents the Product_as_individual_view of the reportable item's next higher assembly item represented by template Product_as_individual_view | |
| child | Product_as_individual_view | This represents the Product_as_individual_view of the reportable item represented by template Product_as_individual_view | |
| Template #5 (Figure 17): representing_product_as_realized | |||
|---|---|---|---|
| Description | This template identifies the reportable item. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier of the individual product | |
| id_class_name | "Product_as_individual_identification_code" (urn:plcs:rdl:std:Product_as_individual_identification_code) | The identifier of the individual product | |
| id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @id_class_name class. | |
| id_owner | ?id_owner? | indicates the name or identifier of the organisation the id or name | |
| id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The identifier of the individual product | |
| id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the @id_owner_class_name class | |
| vn_id | ?vn_id? | The identifier of the individual product version | |
| vn_id_class_name | "Version_identification_code" (urn:plcs:rdl:std:Version_identification_code) | The identifier of the individual product version | |
| vn_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @vn_id_class_name class. | |
| vn_id_owner | ?id_owner? | indicates the name or identifier of the organisation the id or name | |
| vn_id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The identifier of the individual product | |
| vn_id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the @vn_id_owner_class_name class | |
| life_cycle_stage | "Life_cycle_stage" (urn:plcs:rdl:std:Life_cycle_stage) | The identifier of the individual product | |
| life_cycle_stage_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @life_cycle_stage class. | |
| domain | "Application_domain" (urn:plcs:rdl:std:Application_domain) | A classification of the planned activity. | |
| domain_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @domain class. | |
| type_id | ?type_id? | The identifier of the product, e.g part number | |
| type_id_class_name | "Part_identification_code" (urn:plcs:rdl:std:Part_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the design (e.g. Part). This provides the role or reason for the identification. | |
| type_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @type_id_class_name class. | |
| type_id_owner | ?type_id_owner? | indicates the name or identifier of the organisation the type_id | |
| type_id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
| Template #6 (Figure 17): representing_product_as_realized | |||
|---|---|---|---|
| Description | This template identifies the parent item. | ||
| Parameter name: | Parameter value: | Parameter description: | |
| id | ?id? | The identifier of the individual product | |
| id_class_name | "Product_as_individual_identification_code" (urn:plcs:rdl:std:Product_as_individual_identification_code) | The identifier of the individual product | |
| id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @id_class_name class. | |
| id_owner | ?id_owner? | indicates the name or identifier of the organisation the id or name | |
| id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
| id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the @id_owner_class_name class | |
| vn_id | ?vn_id? | The identifier of the individual product version | |
| vn_id_class_name | "Version_identification_code" (urn:plcs:rdl:std:Version_identification_code) | The identifier of the individual product version | |
| vn_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @vn_id_class_name class. | |
| vn_id_owner | ?id_owner? | indicates the name or identifier of the organisation the id or name | |
| vn_id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
| vn_id_owner_ecl_id | urn:plcs:rdl:std | The id of the External_class_library storing the @vn_id_owner_class_name class | |
| life_cycle_stage | "Life_cycle_stage" (urn:plcs:rdl:std:Life_cycle_stage) | The identifier of the individual product | |
| life_cycle_stage_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @life_cycle_stage class. | |
| domain | "Application_domain" (urn:plcs:rdl:std:Application_domain) | A classification of the planned activity. | |
| domain_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @domain class. | |
| type_id | ?type_id? | The identifier of the product, e.g part number | |
| type_id_class_name | "Part_identification_code" (urn:plcs:rdl:std:Part_identification_code) | The name of the class being used to classify the identification (Identification_assignment) of the design (e.g. Part). This provides the role or reason for the identification. | |
| type_id_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @type_id_class_name class. | |
| type_id_owner | ?type_id_owner? | indicates the name or identifier of the organisation the type_id | |
| type_id_owner_class_name | "Organization_identification_code" (urn:plcs:rdl:std:Organization_identification_code) | The name of the class being used to classify the identification of the organization. For example CAGE code, or organization name. | |
The use of template #7 assigning_identification in Figure 17 is identical to, and described in, template table: Template #6(Figure 11).
The use of template #8 assigning_reference_data in Figure 17 is identical to, and described in, template table: Template #4(Figure 11).
The use of template #9 assigning_product_property in Figure 17 is identical to, and described in, template table: Template #3(Figure 13).
The use of template #10 assigning_assessed_state in Figure 17 is identical to, and described in, template table: Template #3(Figure 23).
| Template #11 (Figure 17): assigning_dated_effectivity | |||
|---|---|---|---|
| Description | The start and end date of the reportable item on the end item | ||
| Parameter name: | Parameter value: | Parameter description: | |
| start_year | ?start_year? | The year the reportable item was fitted on the end item | |
| start_month | ?start_month? | The month the reportable item was fitted on the end item | |
| start_day | ?start_day? | The day the reportable item was fitted on the end item | |
| start_hour | ?start_hour? | The hour the reportable item was fitted on the end item | |
| start_minute | ?start_minute? | The minute the reportable item was fitted on the end item | |
| start_second | ?start_second? | The second the reportable item was fitted on the end item | |
| start_sense | ?start_sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| start_hour_offset | ?start_hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| start_minute_offset | ?start_minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| end_year | ?end_year? | The year the reportable item was removed from the end item | |
| end_month | ?end_month? | The month reportable item was removed from the end item | |
| end_day | ?end_day? | The day the reportable item was removed from the end item | |
| end_hour | ?end_hour? | The hour the reportable item was removed from the end item | |
| end_minute | ?minute? | The minute the reportable item was removed from the end item | |
| end_second | ?end_second? | The second the reportable item was removed from the end item | |
| end_sense | ?end_sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| end_hour_offset | ?hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| end_minute_offset | ?minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| role_class_name | "Actual_effectivity" (urn:plcs:rdl:std:Actual_effectivity) | The name of the class being used to classify the effectivity assignment (Effectivity_assignment) This provides the role for the assignment. | |
| role_ecl_id | urn:plcs:rdl:std | The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name class. | |
| items | Promissory_usage | The items to which the effectivity is assigned, e.g. an identification_assignment, a next_assembly_usage, etc. | |
| Template #12 (Figure 17): assigning_dated_effectivity | |||
|---|---|---|---|
| Description | The start and end date of the reportable item on the next higher assembly | ||
| Parameter name: | Parameter value: | Parameter description: | |
| start_year | ?start_year? | The year the reportable item was fitted on the next higher assembly | |
| start_month | ?start_month? | The month the reportable item was fitted on the next higher assembly | |
| start_day | ?start_day? | The day the reportable item was fitted on the next higher assembly | |
| start_hour | ?start_hour? | The hour the reportable item was fitted on the next higher assembly | |
| start_minute | ?start_minute? | The minute the reportable item was fitted on the next higher assembly | |
| start_second | ?start_second? | The second the reportable item was fitted on the next higher assembly | |
| start_sense | ?start_sense? | Three possible values 'exact' when times are UTC, 'behind' when time are behind UTC and 'ahead' when times are ahead of UTC | |
| start_hour_offset | ?start_hour_offset? | The hour offset from UTC, use 0 when values are UTC | |
| start_minute_offset | ?start_minute_offset? | The minute offset from UTC, use 0 when values are UTC | |
| end_year | ?end_year? | The year the reportable item was removed from the next higher assembly | |
| end_month | ?en | ||