2410_form

Business concept:— 2410_form

Date: 2006/06/14 12:11:18
Revision: 1.15

Cover Contents Scope Intro.Terms Business overview Info. model Templates Issues

Scope

The following are within the scope of this business concept:

All activities reported on an U.S. Army DA Form 2410 (See Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)) - a component removal and repair/overhaul record. Namely:
- reporting on inventory loss;
- reporting on inventory gain;
- reporting on maintenance activities.

The following are outside the scope of this business concept:

maintenance activities performed on an aircraft that are not captured by a U.S. Army DA Form 2410;
reporting on activities performed by an aircraft, e.g. sorties;
reporting on the complete configuration status of the aircraft.

Introduction

This business concept describes a mapping of a U.S. Army DA 2410 form (See Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)) to ISO 10303-239 (PLCS).

The DA 2410 form reports on:

Inventory activities: Activities to add to or remove from the U.S.Army inventory;
Maintenance activities: Maintenance activities performed on aircraft or components such as:
- removal of serviceable or unserviceable reportable items from an aircraft;
- installation of reportable items on an aircraft;
- Serial number / Part number changes;

Conformance

This business concept is conformant with the following:

DEX: aviation_maintenance

Terms

For the purposes of this document, the following terms apply:

Auxiliary Power Unit (AUX)

Auxiliary Power Unit

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Aviation Intermediate Maintenance (AVIM)

Aviation Intermediate Maintenance

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Aviation Unit Maintenance (AVUM)

Aviation Unit Maintenance

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Defense Reutilization and Marketing Office (DRMO)

Defense Reutilization and Marketing Office

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Defense Switched Network (DSN)

Defense Switched Network

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Military Assistance Program (MAP)

Military Assistance Program

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

modification work order (MWO)

modification work order

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

personnel identifier (PID)

personnel identifier

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Reportable item

A component or repair part that is classified as a TC (TBO), RC (MAOT), or selected CC items that have been selected by AMCOM for accumulation and reporting of maintenance data on the DA Form 2410.

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Work Unit Code (WUC)

The Work Unit Code (WUC) is a coding structure developed for Army aircraft components/modules to show the relationship of a single component to a major component/module. Work Unit Codes are established to identify functional grouping, major sections, systems installations or major components/modules, specific major components/modules, and subcomponents of the aircraft. These codes are listed in TB 1-1500-341-01 (Aircraft Components Requiring Maintenance Management and Historical Data Reports).

Source

[1] Army Pamphlet 738-751, Glossary, 2004-11-26. http://www.armedforces.net/Detailed/21035.html

Business overview

This section provides a business level overview of this business concept.

The business concept "2410_form" represents the information contained on a U.S. Army DA Form 2410. The DA Form 2410 is described in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html).

The DA Form 2410 provides a method of recording and reporting maintenance data on selected aircraft components and modules. It provides commanders and maintenance managers at all levels with important data needed for effective management of these components and modules. It provides a historical data on removals, repairs, overhauls or rebuilds, installations and gains/losses to the Army inventory for reportable items.

DA Form 2410 is divided into four sections -

Section I-Identification. This section is used to identify the reportable item and to provide necessary usage data, and failure codes.
Section II-Removal Data. This section is used to identify the aircraft, component, or assembly from which the reportable item was removed. It also identifies the unit or activity that removed the item and the unit or activity where the item was shipped.
Section III-Repair/Overhaul/Gain Data. This section is used to identify the organizations that test, repair, modify, overhaul, or rebuild the reportable item. If the item is a gain to the inventory, record the reason for the gain in this section. list the parts replaced during overhaul or repair and reason for failure.
Section IV-Installation/Loss Data. This section is used to identify the aircraft, component, or assembly on which the reportable item is installed and identifies the organization that installed the item. It provides the usage data needed to prepare DA Forms 2408-16 and 2408-16-1. It also shows if the item is a loss to the inventory, and the reason for the loss.

These sections provide a record of:

Inventory activities: Activities to add to or remove from the U.S.Army inventory;
Maintenance activities: Maintenance activities performed on aircraft or components.

These are as follows:

Inventory activities

DA 2410, 3.14. Gains To Inventory: This activity reports when a reportable item is first placed in the Army inventory. This includes installed or uninstalled items and reportable items received from MAP countries, other (non-Army) Government agencies, departments, manufacturers, and military services when reportable items are used or may be used by the U.S. Army. See para. 3.14, and Figure 3-14 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)
DA 2410, 3.19.Loss to inventory: This activity reports when a reportable item is removed from the Army inventory. See para. 3.19, and Figures 3-24 and 3-25 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)

Maintenance activities

DA 2410, 3.15. Removal and evacuation: This activity reports when a serviceable or an unserviceable reportable item is removed from an aircraft or component and the item is not reinstalled on the same aircraft or component. See para. 3.15, and Figure 3-15 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)
DA 2410, 3.15. Repair / Overhaul: This activity reports when a serviceable or unserviceable reportable item is removed from an aircraft or component for repair, overhaul, or rebuild. See para. 3.15, and Figures 3-16 and 3-17 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)
DA 2410, 3.15.Installation: This activity reports when a reportable item is installed on an aircraft or component. See para. 3.15, and Figure 3-18 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)
DA 2410, 3.17.Changes from Serviceable to Unserviceable Status for Uninstalled Items: This activity reports when a serviceable, uninstalled item becomes unserviceable for any reason. See para. 3.16, and Figure 3-19 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)
DA 2410, 3.17. PN, NSN, S/N Change: This activity reports when the Part Number, National Stock Number, and/or Serial Number of a reportable item is changed as a result of a MWO or other directive See para. 3.17, and Figures 3-20 and 3-21 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)
DA 2410, 3.18. Removal of Serviceable Reportable Items for Controlled Exchange.: This activity reports when any removal of a serviceable reportable component and module from one aircraft for installation on another aircraft. This is done within the same organization or in support of another organization. See para. 3.18, and Figures 3-22 and 3-23 in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)

Identification of Reportable Items

The reportable item is identified on the DA 2410 by a combination of Part number, Serial Number and NSN number. It does not currently make use of a Unique Identification (UID) (http://www.acq.osd.mil/dpap/UID/). It is anticipated that the UID will increasingly be used for the identification of reportable items, hence the UID is included in the information model.

DA 2410 form

DA Form 2410 form has the following fields:

NOTE The table is derived from definitions provided in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html) and all tables figures etc that are referred to in the table below are in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html)

Block	Block Name	Description
	Control number	The item name.
1	NOMENCLATURE.	The item name.
2	NSN.	The National Stock Number of the item.
3	PART NUMBER.	The Part Number of the item.
4	SERIAL NUMBER.	The Serial Number of the item.
5	CAGE CODE.	Contractor and Government Entity Code for the item.
6	NO. OF PREV O/Hs.	The number of times that the item has been overhauled. If the item has never been overhauled, enter "0." For Retirement Life Components/Modules and Condition Components/Modules enter "RC" or "CC" in this block.
7	TIME SINCE LAST INST (HRS).	The number of hours, to the nearest hour, that the item has operated since it was last installed.
8	TIME SINCE NEW (HRS).	The total number of hours, to the nearest hour, that the item has been operated since it was new or rebuilt. For H-60 series APUs without an installed hour meter enter "0."
9	TIME SINCE OVERHAUL (HRS).	If the item has been overhauled before, enter the number of hours, to the nearest hour, that the item has operated since the last overhaul. If the item is a RC or CC item, enter "RC" or "CC." For H-60 series APUs, enter "0".
10	FAILURE CODE.	For new items enter "799." For other items enter the appropriate failure code from tables 1-2 or 1-3.
11	POS.	The position that the engine was installed in.
12	HSF.	For T703 engines, the total hot section factors.
13	METER HRS.	The hourmeter reading for items designated by TB 1-1500-341-01 to be tracked using meter hours.
14	WUC.	Enter the work unit code that applies.
15	COMPONENT CUMULATIVE COUNT/HOURS.	For T700 series engines, components/modules, and subcomponents enter the total cumulative counts/hours for the item in block 1. This entry is also required for history recorders. Enter only operating hours, block 15.d., for components/modules, entered on the reverse side of the engine DA Form 2408-16-1, that do not require a separate DA Form 2408-16-1. If the item is new enter "0."
15a	LCF 1.	For T700 series engines, components/modules, or subcomponents enter the total cumulative LCF1 counts.
15b	LCF 2.	For T700 series engines, components/modules, or subcomponents enter the total cumulative LCF 2 counts.
15c	TTI.	For T700 series engines, components/modules, or subcomponents enter the total cumulative TTI counts.
15d	OP HOURS.	The total cumulative operating hours.
16	APU SSN.	The number of times the APU has been started since new. For H-60 series aircraft APUs enter the total starts since new. If the APU is new enter "0."
17	APU HRS.	The total hours since new for the APU.
18	APU SSO.	The number of times the APU has been started since the last overhaul. For H-60 series aircraft APUs, enter the number of starts since the last overhaul. If the APU is new or has never been overhauled, enter "0."
19	VERSION.	Enter the software version for the item entered in block 1 when required by TB 1-1500-341-01.
20	REMOVED FROM (NOMEN NHA).	The name of the next higher assembly, from which the item was removed.
21	NSN (NHA).	The National Stock Number of the next higher assembly, from which the item was removed.
22	PART NUMBER (NHA).	The Part Number of the next higher assembly, from which the item was removed.
23	SERIAL NUMBER (NHA).	The Serial Number of the next higher assembly from which the item was removed.
24	HOURS (NHA).	The current aircraft hours, to the nearest hour, if the next higher assembly is an aircraft. If the next higher assembly is a component, enter the components operating hours since new.
25	NHA CUMULATIVE COUNTS/HOURS.	The total cumulative counts and hours since new for the next higher assembly from which the item was removed.
26	APU START METER.	For H-60 series aircraft enter the reading from the APU start meter at the time of APU removal. If the APU does not have a start meter, leave blank.
27	APU HOUR METER.	For H-60 series aircraft enter the reading from the APU hour meter at the time of APU removal. If the APU does not have a hour meter, leave blank.
28	HISTORY RECORDER S/N.	The serial number of the engine history recorder. If a T700 series engine is entered in block 1 or block 20, enter the engine history recorder serial number. Leave blank if a history recorder is not used. Do not enter a history recorder serial number from a slave engine used for component or module testing. For H-60 series APUs leave blank.
29	HISTORY RECORDER READING.	If a T700 series engine is entered in block 1 or block 20, enter the current reading from the engine history recorder.
30	ACFT MODEL.	The aircraft Mission Design Series if the next higher assembly is an aircraft, otherwise leave blank.
31	ACFT S/N.	The aircraft Serial Number if the next higher assembly is an aircraft.
32	MAINT LEVEL.	The Maintenance Level ("O" for AVUM, "F" for AVIM, "D" for Depot) of the unit/activity doing the removal.
33	DATE REMOVED.	The Julian date that the removal action was completed.
34	UIC.	The Unit Identification Code for the organization taking this action. If a contractor, enter the CAGE code prefixed with a "K."
35	MAN-HOURS (To Remove).	The man-hours it took to remove the item, in hours and tenths. (See Time Conversion Codes, table 1-12 , at the end of chapter 1 or the backside of DA Form 2408.)
36	PID AND TELEPHONE NUMBER.	The individual completing the form will enter his or her PID and phone number (DSN/Commercial). The phone number and PID will be used at the national level to clarify entries.
37	MALFUNCTION CODE.	The Malfunction Effect Code (table 1-6) or the front side of DA Form 2408) that most closely described the effect the malfunction had on the mission.
38	WHEN DISCOVERED.	The When Discovered Code ( Table 1-4 or the front side of DA Form 2408) that identifies when the failure was first detected.
39	DATE CHECKED.	Enter the Julian date that the item, was declared serviceable by the manufacturer/contractor or the Julian date the item was accepted in the Army inventory by the receiving unit.
40	PID AND TELEPHONE NUMBER.	Enter the signature, PID and telephone number of the manufacturer's/contractor's representative declaring the item serviceable. Army units receiving items without DA Form 2410 will fill out the forms and enter their PID and phone number (DSN/Commercial).
41	UIC (THIS ACTION).	Enter the Unit Identification Code for the organization taking this action. If a contractor, enter the CAGE code prefixed with a "K."
42	MAN-HOURS TO REPAIR/OVERHAUL.	The total man-hours, in hours and tenths, it took to repair/overhaul, or rebuild the item (see Time Conversion chart, table 1-12 , at the end of chapter 1 or the backside of DA Form 2408).
43	INSPECTION AND ACTION CODES.	A = serviceable item B = unserviceable item C = change in serviceability status resulted from the publication of an MWO, or other directive enter D = ? E = item for repair F = item for Overhaul
44	REASON FOR GAIN.	Enter "A" for new manufactured items, or other codes from table 1-14 that best describes the reason for gain.
45	CONTRACT NUMBER.	The contract number that the item was procured under.
46	MAINT LEVEL.	The level of the maintenance ("O" for AVUM, "F" for AVIM, "D" for Depot) of the activity performing the action indicated in block 36.
47	ACTUAL FAILURE CODE.	Block 10 of this form identifies the apparent failure code at time of removal. Upon further disassembly and exploration, the root cause for failure may be different from that observed at time of removal. The overhaul/repair facility will enter the actual failure code in this block. See table 1-2 or 1-3 at the end of chapter 1 for the failure code.
48	SRA/ESRA.	If the item in block 1 was repaired using a special repair authorization from AMCOM or the item was repaired by an Enhanced Special Repair Activity enter "Y," all others enter "N."
49a	FAIL CODE.	The failure code that best describes why the item was removed and replaced (see table 1-2 or 1-3 ).
49b	QTY.	The total quantity for each part.
49c	ACT.	The correct Maintenance Action Code, such as "A" for replaced, "B" for adjusted, "C" for repaired (nonserialized) (see table 1-9 ).
49d	NOMENCLATURE.	The name of the part.
49e	PART NUMBER.	The manufacturer's Part Number.
49f	SERIAL NUMBER.	The Serial Number for each part removed. If the part does not have a serial number, leave blank.
49g	CUMULATIVE COUNTS/HOURS LAST DEPOT REPAIR.	For T700 series engines enter the total cumulative counts upon removal of repair parts from the engine or major components/modules. The counts and operating hours can be found on the DA Form 2408-16-1. For H-60 series APUs, enter the number of prior overhauls in the LCF 1 block, starts since overhaul in the LCF 2 block, starts since new in the TTI block, and total operating hours since new for the repair part or subcomponent.
50	INSTALLED ON (NOMEN NHA).	The name of the next higher assembly on which the reportable item is installed.
51	NSN (NHA).	The NSN of the next higher assembly on which the reportable item is installed.
52	PART NUMBER (NHA).	The Part Number of the next higher assembly on which the reportable item is installed.
53	SERIAL NUMBER (NHA).	The Serial Number of the next higher assembly on which the reportable item is installed.
54	HOURS (NHA).	The current aircraft hours, to the nearest hour, if the next higher assembly is an aircraft. If item is a component, enter the operating hours, to the nearest hour, since new or rebuild.
55	NHA CUMULATIVE COUNTS/HOURS.	The total cumulative counts and hours since new for the T700 series engine, component or module entered in block 50. Obtain the total cumulative counts from the DA Form 2408-16-1 for the item. If a T700 series engine, component or module is not entered in block 50, leave blank.
56	APU START METER.	For H-60 series aircraft enter the reading from the APU start meter at the time of APU installation. If the APU does not have a start meter, leave blank.
57	APU HOUR METER.	For H-60 series aircraft enter the reading from the APU hour meter at the time of APU installation. If the APU does not have a hour meter, leave blank.
58	HISTORY RECORDER S/N.	If a T700 series engine is entered in block 1 or block 50, enter the engine history recorder serial number. Leave blank if a history recorder is not used. Do not enter a history recorder serial number from a slave engine used for component or module testing.
59	HISTORY RECORDER READING.	If a T700 series engine is entered in block 1 or block 50, enter the current reading from the engine history recorder.
60	ACFT MODEL.	The Mission Design Series of the aircraft. Leave blank if block 50 is an engine, APU, or component/module.
61	ACFT S/N.	The aircraft Serial Number if the next higher assembly is an aircraft, otherwise leave blank.
62	MAINT LEVEL.	The maintenance level ("O" for AVUM, "F" for AVIM, or "D" for Depot) performing the action.
63	DATE INSTALLED.	The Julian date that the reportable item was installed.
64	UIC (THIS ACTION).	The Unit Identification Code of the organization doing the installation. If a contractor, enter the CAGE code prefixed with a "K."
65	MAN-HOURS (TO INSTALL).	The man-hours, in hours and tenths, it took to install the item in block 1.
66	REASON FOR LOSS.	The Loss Code ( table 1-13 ) that best describes the reason for the loss.
67	NEW NSN.	The new NSN that the item will have after modification. If the NSN will not change, leave blank.
68	NEW PN.	The new part number that the item will have after modification. If the part number will not change, leave blank.
69	NEW SN.	Enter the new serial number that the item will have after modification. If the serial number will not change, leave blank.
70	INSPECTION AND ACTION CODES.	A = serviceable item B = unserviceable item C = change in serviceability status resulted from the publication of an MWO, or other directive enter D = ? E = item for repair F = item for Overhaul
71	PID AND TELEPHONE NUMBER.	The individual completing the form will enter his or her PID and phone number (DSN/Commercial). The phone number and PID will be used at the national level to clarify entries.
72	SHIPPED TO.	The name of the DRMO, the service, agency, department or MAP country that the item was shipped to.
73	LOCATION.	Enter the address of the DRMO, the service, agency, department or MAP country that the item was shipped to.
74	UIC.	Enter the Unit Identification Code DRMO, the service, agency, department or MAP country that the item was shipped to. If a contractor enter the CAGE code prefixed with a "K."
75	Date shipped.	Enter the Julian date that the item was shipped.
REMARKS	REMARKS	Provide any information not considered routine.

Table 1 — DA 2410 form

Information model overview

This section provides an overview of the information model that supports this business concept.

Each of the Inventory and Maintenance activities requires a different subset of the DA 2410 form to be completed. The information required by each activity is summarized diagrammatically in the following sections. Each diagram has been derived from the information provided in Army Pamphlet 738-751 (http://www.armedforces.net/Detailed/21027.html) and shows how the information on the form (the numbered grey boxes in the diagram represent the numbered blocks on the DA2140 form) has been functionally grouped to support the activity. The ISO 10303-239 constructs that are required to represent this information is then described the subsequent section.

The groupings of information captured by the form are:

Activity Record

A record of the activity being reported. In the following diagrams, this is the central orange block.
The mapping of an Activity Record to ISO 10303-239 PLCS is described in Section: Activity Record.

Activity properties

Properties of the activity such as man hours to complete.
The mapping of an Activity properties to ISO 10303-239 PLCS is described in Section: Activity Record.

Activity characterization

Characterization of the activity such as who undertook the activity and when.
The mapping of an Activity characterization to ISO 10303-239 PLCS is described in Section: Activity Record.

Reportable item

The product that was subject of the activity being reported.
The mapping of a Reportable item to ISO 10303-239 PLCS is described in Section: Reportable item identification.

Properties of the Reportable item

The properties, such as lifing information, of the product that was subject of the activity being reported.
The mapping of the properties of the Reportable item to ISO 10303-239 PLCS is described in Section: Properties of the Reportable item.

States of the Reportable item

The states, such as failure state, of the product that was subject of the activity being reported.
The mapping of the states of the Reportable item to ISO 10303-239 PLCS is described in Section: States of the Reportable item.

Part replaced

A list of the parts that have been replaced during the maintenance activity.
The mapping of the parts replaced to ISO 10303-239 PLCS is described in Section: Replaced Parts.

APU

The auxiliary power unit of the aircraft to which the reportable item was fitted.
The mapping of an APU to ISO 10303-239 PLCS is described in Section: APU, History recorder, On Board Monitoring System.

History recorder

The history recorder of the aircraft.
The mapping of a history recorder to ISO 10303-239 PLCS is described in Section: APU, History recorder, On Board Monitoring System.

On board monitoring system

The aircraft on board monitoring system,
The mapping of an on board monitoring system to ISO 10303-239 PLCS is described in Section: APU, History recorder, On Board Monitoring System.

Related activities

Additional activities that were undertaken as part of the overall activity, such as:

overhaul activity;
removal activity;
installation activity.

The mapping of an Activity Record to ISO 10303-239 PLCS is described in Section: Activity Record.

Aircraft activity

The activity that the aircraft was engaged in when fault occurred.
The mapping of an Activity Record to ISO 10303-239 PLCS is described in Section: .

Position on aircraft

The position in which the reportable item was installed or removed from the aircraft.
The mapping of an to ISO 10303-239 PLCS is described in Section: Installation/Removal position on the Aircraft.

Inventory gain

Reportable item added to inventory.
The mapping of an Inventory gain to ISO 10303-239 PLCS is described in Section: Inventory Gain and Loss.

Inventory loss

Reportable item removed from inventory.
The mapping of an Inventory loss to ISO 10303-239 PLCS is described in Section: Inventory Gain and Loss.

DA 2410, 3.14. Gains To Inventory

The information required to support the activity is shown in Figure 1 below.

Figure 1 — Gains To Inventory

DA 2410, 3.19.Loss to inventory

The information required to support the activity is shown in Figure 2 below.

Figure 2 — Loss to inventory

DA 2410, 3.15. Normal Removal, Evacuation, Repair, and Installation Cycle - Removal and evacuation

The information required to support the activity is shown in Figure 3 below.

Figure 3 — Removal and evacuation

DA 2410, 3.15. Normal Removal, Evacuation, Repair, and Installation Cycle - Repair / Overhaul

The information required to support the activity is shown in Figure 4 below.

Figure 4 — Repair / Overhaul

DA 2410, 3.15.Normal Removal, Evacuation, Repair, and Installation Cycle - Installation

The information required to support the activity is shown in Figure 5 below.

Figure 5 — Installation

DA 2410, 3.16.Changes from Serviceable to Unserviceable Status for Uninstalled Items

The information required to support the activity is shown in Figure 6 below.

Figure 6 — Changes from Serviceable to Unserviceable Status for Uninstalled Items

DA 2410, 3.17. PN, NSN, S/N Change

The information required to support the activity is shown in Figure 7 below.

Figure 7 — PN, NSN, S/N Change

DA 2410, 3.18. Removal of Serviceable Reportable Items for Controlled Exchange.

The information required to support the activity is shown in Figure 8 below.

Figure 8 — Removal of Serviceable Items for Controlled Exchange

DA 2410 mapped to ISO 10303-239

The following sections describe how the information contained in the DA 2410 form is represented (mapped) using ISO 10303-239.

The information captured by the form has been summarized in the previous sections. Figure 9 summarizes this information and shows an abstract view of the ISO 10303-239 PLCS constructs that represent the information.

The diagram shows the different types of activity that are recorded on a DA2410 form, such installation, removal etc, and the associated information that is recorded as a result of the activity, such as the identification of the reportable item on which the work was done (the reportable item), the APU lifing measurements and so on.

This high level view of the ISO 10303-239 PLCS representation is detailed in the following sections.

Figure 9 — Information recorded by DA Form 2410

Activity Record

The DA 2410 form is a record of an activity that has been carried out. It is therefore represented in ISO 10303-239 PLCS by an Activity_actual - a representation of an activity that has occurred. The use of an Activity_actual is described in the capability C032: representing_activity and shown in Figure 10 below.

The DA2410 is used to report on a number of different maintenance activities, as summarized in Figure 9. These are:

Removal/Evacuation;
Repair/Overhaul;
Installation;
Serviceable to Unserviceable;
Fit/Form/Function change;
Controlled exchange;
Inventory gain;
Inventory loss.

These activities are all represented by Activity_actual. The different types of activities recorded by a DA2410form are distinguished by using reference data (See capability C010: assigning_reference_data for details on the use of reference data) to classify the Activity_actual.

The Activity_actual representing the different types of DA2410 activities recorded by the form may be classified as follows:

"DA2410Form-Removal" (urn:plcs:rdl:pam738_751:DA2410Form-Removal) - the classification of the Activity_actual recording an activity to remove a reportable item;
"DA2410Form-Overhaul" (urn:plcs:rdl:pam738_751:DA2410Form-Overhaul) - the classification of the Activity_actual recording an overhaul activity.
"DA2410Form-Installation" (urn:plcs:rdl:pam738_751:DA2410Form-Installation) - the classification of the Activity_actual recording an installation activity.
"DA2410Form-Servicability_change" (urn:plcs:rdl:pam738_751:DA2410Form-Servicability_change) - the classification of the Activity_actual recording a reportable item being changed from serviceable to unserviceable.
"DA2410Form-Fit_form_function_change" (urn:plcs:rdl:pam738_751:DA2410Form-Fit_form_function_change) - the classification of the Activity_actual recording a Form/Fit/Function change of the reportable item, resulting in a cnage in PN, NSN and/or S/N.
"DA2410Form-Controlled_exchange" (urn:plcs:rdl:pam738_751:DA2410Form-Controlled_exchange) - the classification of the Activity_actual recording a Removal of Serviceable Items for Controlled Exchange.
"DA2410Form-InventoryGain" (urn:plcs:rdl:pam738_751:DA2410Form-InventoryGain) - the classification of the Activity_actual recording a gain to the inventory;
"DA2410Form-InventoryLoss" (urn:plcs:rdl:pam738_751:DA2410Form-InventoryLoss) - the classification of the Activity_actual recording a loss to the inventory.

The Activity_actual is identified by the DA2410 control number. This is represented by an Identification_assignment. This is described in the capability C001: assigning_identifiers and the template: assigning_identification. The identifier is classified as a: "Activity_identification_code" (urn:plcs:rdl:std:Activity_identification_code)

The Activity_actual is "characterized" by the date when the activity was performed and by whom. Properties such as the time taken to perform the activity are also recorded.

The Activity_actual is related to the items identified on the form, such as the reportable item, the APU, the parts replaced etc, by instances of Applied_activity_assignments. Each role of each instance is provided by classification. The use of Applied_activity_assignment is detailed in the template assigning_activity .

The Activity_actual is also related to an Activity_method representing the process description, or the method, that was used when performing the activity. The DA2410 form do not identify the method used, so "PAM738_751_method" is used for all types of activities.

An EXPRESS-G diagram showing how the Activity_actual is used to represent the activity record is shown in Figure 10 below. The diagram also shows the templates that are required.

Figure 10 — EXPRESS-G diagram for recording a form

The following templates are used in the diagram and represent the various blocks on the DA2410 form:

Template #1 (Figure 10): assigning_activity
Description	The association of the activities reported on the form and the subject (e.g. input and output) of the activity, such as the Reportable item, the APU etc.
Parameter name:	Parameter value:	Parameter description:
role_class_name	Where the activity is related to a reportable item use: "Activity_input_Reportable_item" (urn:plcs:rdl:pam738_751:Activity_input_Reportable_item)	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).
	Where the activity is related to an APU, use: "Activity_input_APU" (urn:plcs:rdl:pam738_751:Activity_input_APU)	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).
	Where the activity is related to a History recorder use: "Activity_input_History_recorder" (urn:plcs:rdl:pam738_751:Activity_input_History_recorder)	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).
	Where the activity is related to an On Board Monitoring System use: "Activity_input_On_board_monitoring_system" (urn:plcs:rdl:pam738_751:Activity_input_On_board_monitoring_system)	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).
	Where the activity is related to an inventory gain or loss use: "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	For items being input/output to the activity, use: "'urn:plcs:rdl:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name.
role_ecl_id	For inventory gain and loss, use: "'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	The activity being reported on the DA 2410 Form.
items	For Reportable item, APU, History recorder and On Board Monitoring System use: Product_as_realized	The activity, product, individual, task_method, etc that is being assigned to the activity.
	For inventory gain: Increasing_resource_event	The activity, product, individual, task_method, etc that is being assigned to the activity.
	For inventory loss: Decreasing_resource_event	The activity, product, individual, task_method, etc that is being assigned to the activity.

Template #2 (Figure 10): assigning_identification
Description	The identification of the activity_actual. For the activity being reported on the form, this is the control number.
Parameter name:	Parameter value:	Parameter description:
id	DA2410 block: control block	The identifier
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.
id_ecl_id	urn:plcs:rdl:std	The id of the External_class_library storing the id_class_name.
org_id	'US Army'	The identifier or name of the organization that "owns" the identifier.
org_id_class_name	For names of organization, use "Organization_name" (urn:plcs:rdl:std:Organization_name)	The name of the class being used to classify the identification of the organization. For example CAGE code.
org_id_class_name	For organization identification codes, e.g. CAGE code, 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.
org_id_ecl_id	urn:plcs:rdl:std	The id of the External_class_library storing the org_id_class_name class items.
items	Activity_actual	The activity that is being reported on by the DA2410 form, represented as an Activity_actual.

Template #3 (Figure 10): assigning_business_specific_reference_data
Description	A classification of the type of activity that is being reported by the DA 2410 form.
Parameter name:	Parameter value:	Parameter description:
class_name	Where the activity being reported is an Overhaul, use: "DA2410Form-Overhaul" (urn:plcs:rdl:pam738_751:DA2410Form-Overhaul)	The name of the class in the business specific reference data library (External_class) being used to classify something
	Where the activity being reported is a Removal use: "DA2410Form-Removal" (urn:plcs:rdl:pam738_751:DA2410Form-Removal)	The name of the class in the business specific reference data library (External_class) being used to classify something
	Where the activity being reported is a Installation use: "DA2410Form-Installation" (urn:plcs:rdl:pam738_751:DA2410Form-Installation)	The name of the class in the business specific reference data library (External_class) being used to classify something
	Where the activity being reported is a Servicability change use: "DA2410Form-Servicability_change" (urn:plcs:rdl:pam738_751:DA2410Form-Servicability_change)	The name of the class in the business specific reference data library (External_class) being used to classify something
	Where the activity being reported is a Fit/Form/Function change use: "DA2410Form-Fit_form_function_change" (urn:plcs:rdl:pam738_751:DA2410Form-Fit_form_function_change)	The name of the class in the business specific reference data library (External_class) being used to classify something
	Where the activity being reported is a Gain to inventory, use: "DA2410Form-InventoryGain" (urn:plcs:rdl:pam738_751:DA2410Form-InventoryGain)	The name of the class in the business specific reference data library (External_class) being used to classify something
	Where the activity being reported is a Loss to inventory, use: "DA2410Form-InventoryLoss" (urn:plcs:rdl:pam738_751:DA2410Form-InventoryLoss)	The name of the class in the business specific reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the business_specific External_class_library that stores the class.
plcs_class_name	"Activity_actual" (urn:plcs:rdl:std:Activity_actual)	The name of the first plcs superclass encountered in the plsc standard reference data library (External_class) when traversing the class hierarchy for the assigned business specific (External_class).
items	Activity_actual	The activity that is being reported on by the DA2410 form, represented as an Activity_actual.

Template #4 (Figure 10): assigning_person_in_organization
Description	Identification of the person completing the reporting of the activity.
Parameter name:	Parameter value:	Parameter description:
person_id Error T6: assigning_person_in_organization does not have a parameter person_id	Block 36 PID, and Block 40 PID, and Block 71 PID
person_id_class_name Error T6: assigning_person_in_organization does not have a parameter person_id_class_name	"PID" (urn:plcs:rdl:pam738_751:PID)
person_id_ecl_id Error T6: assigning_person_in_organization does not have a parameter person_id_ecl_id	"'urn:plcs:rdl:pam738_751'"
last_name	"/NULL" [Mandatory value unknown, not provided by DA2410 form]	the last name (surname) of the person doing the approval
person_role_class_name	"Creator_of" (urn:plcs:rdl:std:Creator_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	Block 34 UIC, and Block 41 UIC, and Block 64 UIC	The identifier (UIC) of the organization in which the person completing the reporting of the activity work.
	Block 34 CAGE code (for contractor), and Block 41 CAGE code (for contractor), and Block 64 CAGE code (for contractor)	The identifier (CAGE code) of the contractor organization in which the person completing the reporting of the activity work.
	If organization of person is unknown: "/NULL"	If the organization in which the person completing the reporting of the activity work is unknown, enter "/NULL" for any Block.
org_id_class_name	"UIC" (urn:plcs:rdl:pam738_751:UIC)	The name of the class - Unit Identification Code (UIC) - being used to classify the identification (Identification_assignment) of the organization. This provides the role or reason for the identification.
	"CAGE_code" (urn:plcs:rdl:std:CAGE_code) for contractors	The name of the class ( "CAGE_code" (urn:plcs:rdl:std:CAGE_code)) being used to classify the identification (Identification_assignment) of the contractor's organization. This provides the role or reason for the identification.
	"Unknown_organization" (urn:plcs:rdl:std:Unknown_organization)	If organization is unknown.
org_id_ecl_id	"'urn:plcs:rdl:pam738_751'" for organizations identified with UIC.	The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class.
	"'urn:plcs:rdl:std'" for organizations (contractors) identified with CAGE code.	The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_id_class_name class.
	"'urn:plcs:rdl:pam738_751'" if organization is unknown.	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 being reported on by the DA2410 form represented as a Activity_actual.

Template #5 (Figure 10): assigning_reference_data
Description	Maintenance level of organization unit
Parameter name:	Parameter value:	Parameter description:
class_name	Block 32, 46 and 62: "Maintenance_level" (urn:plcs:rdl:pam738_751:Maintenance_level)	The Maintenance Level ("O" for AVUM, "F" for AVIM, "D" for Depot) of the unit/activity doing the removal.
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the External_class_library that stores the definition for the class being used.
items	The Organization entity instantiated by the template assigning_person_in_organization.	The items to which the External_class is assigned.

Template #6 (Figure 10): assigning_address
Description	Address of person
Parameter name:	Parameter value:	Parameter description:
address_class_name	"Business_address" (urn:plcs:rdl:std:Business_address)	The name of the class being used to classify the address. This provides the type of address, for example 'office_address'.
address_ecl_id	"'urn:plcs:rdl:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @address_class_name.
telephone_number	Block 36 Telephone number, and Block 40 Telephone number, and Block 71 Telephone number	The number at which telephone calls may be received. Parameter is optional.
located_pers_org	The Person entity instantiated by the template assigning_person_in_organization.	The items to which the address is assigned

Template #7 (Figure 10): assigning_organization
Description	This template is used to identify an organization without also identifying a person. It should also be used to identify the organization responsible for the activity, if other than the organization employing/responsible for the person doing the work or reporting the activity.
Parameter name:	Parameter value:	Parameter description:
org_id	Block 34 UIC or CAGE code (for contractor), and Block 41 UIC or CAGE code (for contractor), and Block 64 UIC or CAGE code (for contractor)	The identifier (UIC or CAGE code) of the organization, if other than the organization to which the person doing the activity and/or completing the reporting of the activity belongs. Otherwise use template #4 assigning_person_in_organization.
org_id	Block 74 UIC or CAGE code (for contractor)	The identifier (UIC or CAGE code) of the receiving organization, to which the item was shipped.
org_id_class_name	"UIC" (urn:plcs:rdl:pam738_751:UIC) or, if contractor, "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. Unit Identification Code (UIC), or for contractors, the "CAGE_code" (urn:plcs:rdl:std:CAGE_code).
org_id_ecl_id	"'urn:plcs:rdl:pam738_751'" or, for CAGE code, "'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	"Organization_type" (urn:plcs:rdl:std:Organization_type) For inventory loss activities use "Receiver_of" (urn:plcs:rdl:std:Receiver_of) to indicate the organization receiving a reportable item.	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 'Receiving_organization'.
org_assgn_ecl_id	"'urn:plcs:rdl:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @org_assgn_class_name.
items	Activity_actual	The DA2410 form to which the person is assigned, represented as a Activity_actual.

Error T7: assigning_organization_location does not exist in capability: representing_location

Template #8 (Figure 10): Error T7: assigning_organization_location does not exist in capability: representing_location assigning_organization_location
Description	Organization-based location (address) of receiving organization
Parameter name:	Parameter value:	Parameter description:
la_class_name Error T6: assigning_organization_location does not have a parameter la_class_name	"Shipping_address" (urn:plcs:rdl:std:Shipping_address)
la_ecl_id Error T6: assigning_organization_location does not have a parameter la_ecl_id	"'urn:plcs:rdl:pam738_751'"
loc_id Error T6: assigning_organization_location does not have a parameter loc_id	Block 72 SHIPPED TO	The name of the DRMO, the service, agency, department or MAP country that the item was shipped to.
loc_id_class_name Error T6: assigning_organization_location does not have a parameter loc_id_class_name	"Organization_name" (urn:plcs:rdl:std:Organization_name)
loc_id_ecl_id Error T6: assigning_organization_location does not have a parameter loc_id_ecl_id	"'urn:plcs:rdl:std'"
org_name Error T6: assigning_organization_location does not have a parameter org_name	"US Army"
org_name_class Error T6: assigning_organization_location does not have a parameter org_name_class	"Organization_name" (urn:plcs:rdl:std:Organization_name)
org_name_ecl_id Error T6: assigning_organization_location does not have a parameter org_name_ecl_id	"'urn:plcs:rdl:std'"
loc_val Error T6: assigning_organization_location does not have a parameter loc_val	Block 73 LOCATION	The address of the DRMO, the service, agency, department or MAP country that the item was shipped to.
loc_id_type Error T6: assigning_organization_location does not have a parameter loc_id_type	"Location_identification_code" (urn:plcs:rdl:std:Location_identification_code)
loc_id_type_ecl_id Error T6: assigning_organization_location does not have a parameter loc_id_type_ecl_id	"'urn:plcs:rdl:std'"

Template #9 (Figure 10): assigning_calendar_date
Description	A Date of the activity, either date for finished removal or installation, the date for discovery or check-in, or the date for shipping. If and activity requires more than one date, the template is repeated.
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:pam738_751'"	The id of the External_class_library in which the date class is defined.
year	The 'year' component of Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date year_component
month	The 'month' component of Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date month_component
day	The 'day' component of Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date day_component
items	Activity_actual	The items to which the date is assigned.

Template #10 (Figure 10): assigning_contract
Description	The contract number that the item was procured under.
Parameter name:	Parameter value:	Parameter description:
cnt_id	Block 45 CONTRACT NUMBER	The name or 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:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @cnt_id_class_name class.
cnt_org_id	'US Army' NOTE It is assumed that the contract identifier is owned/assigned by the US Army.	The name or identifier of the organization owning or holding the contract.
cnt_org_id_class_name	"Organization_name" (urn:plcs:rdl:std:Organization_name)	The name of the class being used to classify the identification (Identification_assignment) of the organization. This provides the name of the organization.
cnt_org_id_class_name	For organization identification codes, e.g. CAGE code, 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 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 items to which the contract is assigned

Template #11 (Figure 10): assigning_descriptor
Description	The remarks block is represented by assigning_descriptor.
Parameter name:	Parameter value:	Parameter description:
descr	Block REMARKS	The text being assigned as a descriptor.
class_name	"Comment" (urn:plcs:rdl:std:Comment)	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 entity to which the Document_assignment is assigned.

Error T7: assigning_activity_property does not exist in capability: assigning_process_properties

Template #12 (Figure 10): Error T7: assigning_activity_property does not exist in capability: assigning_process_properties assigning_activity_property
Description	Assignment of properties to the activity. This template assigns the property name, while template #13 Error T7: activity_property_value does not exist in capability: representing_properties_numerically activity_property_value assigns the value and unit to a property instantiated by this template.
Parameter name:	Parameter value:	Parameter description:
property_class_name Error T6: assigning_activity_property does not have a parameter property_class_name	"Man_hours_to_remove" (urn:plcs:rdl:pam738_751:Man_hours_to_remove), or "Man_hours_to_repair_or_overhaul" (urn:plcs:rdl:pam738_751:Man_hours_to_repair_or_overhaul), or "Man_hours_to_install" (urn:plcs:rdl:pam738_751:Man_hours_to_install)
property_ecl_id Error T6: assigning_activity_property does not have a parameter property_ecl_id	"'urn:plcs:rdl:pam738_751'"
described_element Error T6: assigning_activity_property does not have a parameter described_element	Activity_actual

Error T7: activity_property_value does not exist in capability: representing_properties_numerically

Template #13 (Figure 10): Error T7: activity_property_value does not exist in capability: representing_properties_numerically activity_property_value
Description	Assigning the value and unit to an activity property.
Parameter name:	Parameter value:	Parameter description:
value Error T6: activity_property_value does not have a parameter value	Block 35 (assigned to "Man_hours_to_remove" (urn:plcs:rdl:pam738_751:Man_hours_to_remove)) Block 42 (assigned to "Man_hours_to_repair_or_overhaul" (urn:plcs:rdl:pam738_751:Man_hours_to_repair_or_overhaul)) Block 65 (assigned to "Man_hours_to_install" (urn:plcs:rdl:pam738_751:Man_hours_to_install))
unit_class_name Error T6: activity_property_value does not have a parameter unit_class_name	For Block 35, 42 and 65: "hour" (urn:plcs:rdl:std:hour)
unit_ecl_id Error T6: activity_property_value does not have a parameter unit_ecl_id	"'urn:plcs:rdl:pam738_751'"
rep_class_name Error T6: activity_property_value does not have a parameter rep_class_name	"PAM738-751context"
rep_ecl_id Error T6: activity_property_value does not have a parameter rep_ecl_id	"'urn:plcs:rdl:pam738_751'"
property Error T6: activity_property_value does not have a parameter property	The Activity_property entity instantiated by the template Error T7: assigning_activity_property does not exist in capability: assigning_process_properties assigning_activity_property.

Template #14 (Figure 10): assigning_calendar_date
Description	Creation date for property value. Since DA2410 does not provide dates for property creation, the date for when the property was entered on the form is used, i.e. the date of the activity.
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	The 'year' component of the date of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date year_component
month	The 'month' component of the date of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date month_component
day	The 'day' component of the date of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date day_component
items	Property_value_representation	The items to which the date is assigned.

Template #15 (Figure 10): assigning_approval
Description	Any signature that is required should be represented as an approval.
Parameter name:	Parameter value:	Parameter description:
person_id Error T6: assigning_approval does not have a parameter person_id	Block 36 PID, and Block 40 PID, and Block 71 PID
person_id_class_name Error T6: assigning_approval does not have a parameter person_id_class_name	"PID" (urn:plcs:rdl:pam738_751:PID)
person_id_ecl_id Error T6: assigning_approval does not have a parameter person_id_ecl_id	"'urn:plcs:rdl:pam738_751'"
last_name Error T6: assigning_approval does not have a parameter last_name	"/NULL" [Mandatory value is not known, not provided in DA2410 form]
org_id Error T6: assigning_approval does not have a parameter org_id	Block 34 UIC, and Block 41 UIC, and Block 64 UIC	The identifier (UIC) of the organization in which the approving person work.
	Block 34 CAGE code (for contractor), and Block 41 CAGE code (for contractor), and Block 64 CAGE code (for contractor)	The identifier (CAGE code) of the contractor organization in which the approving person work.
org_id_class_name Error T6: assigning_approval does not have a parameter org_id_class_name	"UIC" (urn:plcs:rdl:pam738_751:UIC)	The name of the class (Unit Identification Code "UIC" (urn:plcs:rdl:pam738_751:UIC)) being used to classify the identification (Identification_assignment) of the organization. This provides the role or reason for the identification.
	"CAGE_code" (urn:plcs:rdl:std:CAGE_code) for contractors	The name of the class ( "CAGE_code" (urn:plcs:rdl:std:CAGE_code)) being used to classify the identification (Identification_assignment) of the contractor's organization. This provides the role or reason for the identification.
org_id_ecl_id Error T6: assigning_approval does not have a parameter org_id_ecl_id	"'urn:plcs:rdl:pam738_751'" for organizations identified with UIC.
	"'urn:plcs:rdl:std'" for organizations (contractors) identified with CAGE code.
items	Activity_actual	The items to which the approval is assigned

Template #16 (Figure 10): assigning_reference_data
Description	Further characterization of the activity is possible through external reference data, e.g. an Enhanced Special Repair Activity
Parameter name:	Parameter value:	Parameter description:
class_name	For Block 48: "SRA_ESRA" (urn:plcs:rdl:pam738_751:SRA_ESRA)	The name of the class in the reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the External_class_library that stores the definition for the class being used.
items	Activity_actual	The items to which the External_class is assigned.

Template #17 (Figure 10): assigning_reference_data
Description	Name of Activity_method. The Activity_method is not given by the DA2410 form, but the process is governed by PAM738_751, so a fixed value is used here.
Parameter name:	Parameter value:	Parameter description:
class_name	' "PAM738_751_method" (urn:plcs:rdl:pam738_751:PAM738_751_method)	The name of the class in the reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the External_class_library that stores the definition for the class being used.
items	Activity_method	The items to which the External_class is assigned.

Template #18 (Figure 10): assigning_reference_data
Description	Purpose of the Activity_method. The Activity_method is not given by the DA2410 form, but the process is governed by PAM738_751, so a fixed value is used here.
Parameter name:	Parameter value:	Parameter description:
class_name	"Aviation_maintenance" (urn:plcs:rdl:pam738_751:Aviation_maintenance)	The name of the class in the reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the External_class_library that stores the definition for the class being used.
items	Activity_method	The items to which the External_class is assigned.

Reportable item identification

The subject of the activity that is recorded on the DA 2410 form is referred to as the reportable item. It is normally the aircraft or component on the aircraft on which the activity was undertaken. It 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 reportable item is identified on the DA 2410 form by the part number, serial number, NSN number, part name and the CAGE code of the organization that manufactured the part.

The serial number is the identification of the Product_as_individual and is represented by an Identification_assignment classified as "Serial_identification_code" (urn:plcs:rdl:std:Serial_identification_code).

Each Product_as_individual has a version, represented by a Product_as_realized and identified by an Identification_assignment

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 an Identification_assignment assigned to the Part. (For details of identification, see the capability: C001: assigning_identifiers and the template: C001: assigning_identifiers). The identifiers are classified as a: "Part_identification_code" (urn:plcs:rdl:std:Part_identification_code) and "NSN_code" (urn:plcs:rdl:std:NSN_code).

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: assigning_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 manufacturing organization is represented by assigning (Organization_or_person_in_organization_assignment) an Organization to the Product_as_individual. The assignment is classified as "Manufacturer_of" (urn:plcs:rdl:std:Manufacturer_of) to indicate that the organization is the manufacturer of the part.

The DA 2410 form does not record the Unique Identification (UID) (http://www.acq.osd.mil/dpap/UID/) of a reportable item. If a UID is present, it is treated as an identification represented in ISO 10303-239 PLCS by the assignment of an identification to the Product_as_individual representing the reportable item. The Identification_assignment is classified as "UID" (urn:plcs:rdl:std:UID). For details of identification, see the capability: C001: assigning_identifiers and the template: C001: assigning_identifiers.

The reportable_item is related back to the Activity_actual that represents the DA 2410 form by an instance of Applied_activity_assignments classified as "Activity_input_Reportable_item" (urn:plcs:rdl:pam738_751:Activity_input_Reportable_item). The use of Applied_activity_assignment is detailed in the template assigning_activity.

An EXPRESS-G diagram showing how the reportable item is identified is shown below.

Figure 11 — EXPRESS-G diagram for identifying reportable item

The following templates are used in the diagram and represent the various blocks on the DA2410 form:

Template #1 (Figure 11): assigning_identification
Description	The item name, NOMENCLATURE (the name of the part).
Parameter name:	Parameter value:	Parameter description:
id	Block 1 NOMENCLATURE	The identifier being assigned.
	For Next Higher Assembly: Block 20 REMOVED FROM (NOMEN NHA), and Block 50 INSTALLED ON (NOMEN NHA)	The identifier being assigned.
	For Aircraft Model: Block 30 ACFT MODEL, and Block 60 ACFT MODEL	The identifier being assigned.
	For failing subcomponent: Block 49d NOMENCLATURE	The identifier being assigned.
id_class_name	"Part_name" (urn:plcs:rdl:std:Part_name)	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	"/NULL" NOTE The DA 2410 form only provides a part name, number and serial number. It does not provide the organization that assigned them. Hence /NULL is used. The use of a UID with an associated organization will resolve this.	The identifier or name of the organization that "owns" the identifier.
org_id_class_name	"Unknown_organization" (urn:plcs:rdl:std:Unknown_organization)	Since organization is unknown.
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 by name (and reported on by the DA2410 form), represented as a Part.

Template #2 (Figure 11): assigning_identification
Description	The Part number (identifier) of the item.
Parameter name:	Parameter value:	Parameter description:
id	Block 3 PART NUMBER	The identifier being assigned.
	For Next Higher Assembly: Block 22 PART NUMBER (NHA), and Block 52 PART NUMBER (NHA)	The identifier being assigned.
	For failing subcomponent: Block 49e PART NUMBER	The identifier being assigned.
	For new part number: Block 68 NEW PN	Assign a assigning_calendar_date to the old Part Number Identification_assignment with class_name = "Date_actual_end" (urn:plcs:rdl:std:Date_actual_end), and assign a assigning_calendar_date to this new Part Number identification_assignment with id_class_name = "Date_actual_start" (urn:plcs:rdl:std:Date_actual_start).
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	"/NULL" NOTE The DA 2410 form only provides a part name, number and serial number. It does not provide the organization that assigned them. Hence /NULL is used. The use of a UID with an associated organization will resolve this.	The identifier or name of the organization that "owns" the identifier.
org_id_class_name	"Unknown_organization" (urn:plcs:rdl:std:Unknown_organization)	Since organization is unknown.
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 the DA2410 form), represented as a Part.

Template #3 (Figure 11): assigning_code
Description	The National Stock Number (NSN) of the item.
Parameter name:	Parameter value:	Parameter description:
class_name	Block 2 NSN, and Block 21 NSN (NHA), and Block 51 NSN (NHA), and Block 67 NEW NSN	The text representing the code.
code_class_name	"NSN_code" (urn:plcs:rdl:std:NSN_code)	The name of the class in the reference data library (External_class) being used to determine type of code.
code_ecl_id	urn:plcs:rdl:std	The id of the External_class_library that stores the class.
items	Part	The part that is being identified by NSN (and reported on by the DA2410 form), represented as a Part.

Template #4 (Figure 11): assigning_identification
Description	Software version for the item entered in Block 1, when required by TB 1-1500-341-01.
Parameter name:	Parameter value:	Parameter description:
id	Block 19 VERSION	The identifier being assigned.
id_class_name	"Version_identification_code" (urn:plcs:rdl:std:Version_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	"/NULL" NOTE The DA 2410 form only provides a part name, number and serial number. It does not provide the organization that assigned them. Hence /NULL is used. The use of a UID with an associated organization will resolve this.	The identifier or name of the organization that "owns" the identifier.
org_id_class_name	"Unknown_organization" (urn:plcs:rdl:std:Unknown_organization)	Since organization is unknown.
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_version	The part version of the software, represented as a Part_version.

Template #5 (Figure 11): assigning_identification
Description	The serial number of the item.
Parameter name:	Parameter value:	Parameter description:
id	Block 4 SERIAL NUMBER	The identifier being assigned.
	For Next Higher Assembly: Block 23 SERIAL NUMBER (NHA), and Block 53 SERIAL NUMBER (NHA)	The identifier being assigned.
	For the History Recorder: Block 28 HISTORY RECORDER S/N, and Block 58 HISTORY RECORDER S/N	The identifier being assigned.
	For Aircraft: Block 31 ACFT S/N, and Block 61 ACFT S/N	The identifier being assigned.
	For failing subcomponent: Block 49f SERIAL NUMBER	The identifier being assigned.
	For a New Serial Number: Block 69 NEW SN	The identifier being assigned.
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	"/NULL" NOTE The DA 2410 form only provides a part name, number and serial number. It does not provide the organization that assigned them. Hence /NULL is used. The use of a UID with an associated organization will resolve this.	The identifier or name of the organization that "owns" the identifier.
org_id_class_name	"Unknown_organization" (urn:plcs:rdl:std:Unknown_organization)	Since organization is unknown.
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 the DA2410 form), represented as a Product_as_individual.

Template #6 (Figure 11): assigning_identification
Description	The UID (Unified Identifier) of the item.
Parameter name:	Parameter value:	Parameter description:
id	The UID code [not on DA Form 2410]	The identifier being assigned.
id_class_name	"UID" (urn:plcs:rdl:std:UID)	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:pam738_751'"	The id of the External_class_library storing the id_class_name class
org_id	UIC or CAGE code of UID owner.	The identifier or name of the organization that owns the UID.
org_id_class_name	"UIC" (urn:plcs:rdl:pam738_751:UIC) or "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:pam738_751'" or "'urn:plcs:rdl:std'"	The id of the External_class_library storing the org_id_class_name class
items	Product_as_individual	The individual product that is being identified (and reported on by the DA2410 form), represented as a Product_as_individual.

Template #7 (Figure 11): assigning_organization
Description	Contractor and Government Entity Code that manufactured the item.
Parameter name:	Parameter value:	Parameter description:
org_id	Block 5 CAGE CODE	The name or identifier of the organization.
org_id_class_name	"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	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 to which the organization is being assigned, represented as a Product_as_individual.

Template #8 (Figure 11): assigning_code
Description	Applicable Work Unit Code.
Parameter name:	Parameter value:	Parameter description:
class_name	Block 14 WUC	The text representing the code.
code_class_name	"Work_unit_code" (urn:plcs:rdl:pam738_751:Work_unit_code)	The name of the class in the reference data library (External_class) being used to determine type of code.
code_ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the External_class_library that stores the class.
items	Product_as_individual	The individual product to which the WUC is being assigned, represented as a Product_as_individual.

The use of template #9 assigning_activity in Figure 11 is identical to, and described in, template table: Template #1(Figure 10).

Properties of the Reportable item

The DA2410 form records 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 capabilities C076: assigning_product_properties, C079: representing_properties_numerically and detailed in the templates assigning_product_property and
Error T7: product_property_value does not exist in capability: representing_properties_numerically
product_property_value.

The template 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
Error T7: product_property_value does not exist in capability: representing_properties_numerically
product_property_value is used to represent the value of the property and its unit. The units are represented by reference data.

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 Product_as_individual_view and an associated context represented by a View_definition_context. The context is classified according to the life cycle view and application domain. For the DA2410 form the life cycle view is "Support_stage" (urn:plcs:rdl:std:Support_stage) and the application domain is "Product_life_cycle_support" (urn:plcs:rdl:std:Product_life_cycle_support)

An EXPRESS-G diagram showing how properties on reportable on a reportable item are represented is shown below in Figure 12.

Figure 12 — EXPRESS-G diagram for properties on reportable item

The following templates are used in the diagram and represent the various blocks on the DA2410 form:

Template #1 (Figure 12): assigning_reference_data
Description	The life cycle state in which the product_as_individual is. Should always be set to the same value.
Parameter name:	Parameter value:	Parameter description:
class_name	"Support_stage" (urn:plcs:rdl:std:Support_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 12): 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 12): 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 12).
Parameter name:	Parameter value:	Parameter description:
property_class_name	For Block 6: "Number_previous_overhauls" (urn:plcs:rdl:pam738_751:Number_previous_overhauls)	The class name corresponding to the property name.
	For Block 7: "Time_since_last_installed" (urn:plcs:rdl:pam738_751:Time_since_last_installed)	The class name corresponding to the property name.
	For Block 8: "Time_since_new" (urn:plcs:rdl:pam738_751:Time_since_new)	The class name corresponding to the property name.
	For Block 9: "Time_since_overhaul" (urn:plcs:rdl:pam738_751:Time_since_overhaul)	The class name corresponding to the property name.
	For Block 12: "Hot_section_factors" (urn:plcs:rdl:pam738_751:Hot_section_factors)	The class name corresponding to the property name.
	For Block 13: "Meter_hour_readings" (urn:plcs:rdl:pam738_751:Meter_hour_readings)	The class name corresponding to the property name.
	For Block 15a: "LCF1" (urn:plcs:rdl:pam738_751:LCF1)	The class name corresponding to the property name.
	For Block 15b: "LCF2" (urn:plcs:rdl:pam738_751:LCF2)	The class name corresponding to the property name.
	For Block 15c: "TTI" (urn:plcs:rdl:pam738_751:TTI)	The class name corresponding to the property name.
	For Block 15d: "Cumulative_operating_hours" (urn:plcs:rdl:pam738_751:Cumulative_operating_hours)	The class name corresponding to the property name.
	For Block 16: "Number_starts_since_new" (urn:plcs:rdl:pam738_751:Number_starts_since_new)	The class name corresponding to the property name.
	For Block 17: "Hours_since_new" (urn:plcs:rdl:pam738_751:Hours_since_new)	The class name corresponding to the property name.
	For Block 18: "Number_starts_since_overhauled" (urn:plcs:rdl:pam738_751:Number_starts_since_overhauled)	The class name corresponding to the property name.
	For Block 24 and Block 54: "Aircraft_hours_property" (urn:plcs:rdl:pam738_751:Aircraft_hours_property), or if NHA is not the Aircraft: "NHA_operating_hours" (urn:plcs:rdl:pam738_751:NHA_operating_hours)	The class name corresponding to the property name.
	For Block 25 and Block 55: "NHA_cumulative_counts_hours" (urn:plcs:rdl:pam738_751:NHA_cumulative_counts_hours)	The class name corresponding to the property name.
	For Block 26 and Block 56: "APU_start_meter" (urn:plcs:rdl:pam738_751:APU_start_meter)	The class name corresponding to the property name.
	For Block 27 and Block 57: "APU_hour_meter" (urn:plcs:rdl:pam738_751:APU_hour_meter)	The class name corresponding to the property name.
	For Block 29 and Block 59: "History_recorder_reading" (urn:plcs:rdl:pam738_751:History_recorder_reading)	The class name corresponding to the property name.
	For Block 49g: "Cumulative_counts_hours_last_depot_repair" (urn:plcs:rdl:pam738_751:Cumulative_counts_hours_last_depot_repair)	The class name corresponding to the property name.
property_ecl_id	"'urn:plcs:rdl:pam738_751'"	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

Error T7: product_property_value does not exist in capability: representing_properties_numerically

Template #4 (Figure 12): Error T7: product_property_value does not exist in capability: representing_properties_numerically product_property_value
Description	Used to assign property values to properties instantiated e.g. in the template assigning_product_property. Property values are assumed to have been assigned at the same date as the Product_as_realized has been given. If this is not the case, a specific date should be assigned to the property value through the use of template assigning_calendar_date.
Parameter name:	Parameter value:	Parameter description:
value Error T6: product_property_value does not have a parameter value	Block 6 PREV O/H	The value of the property "Number_previous_overhauls" (urn:plcs:rdl:pam738_751:Number_previous_overhauls) in template table: Template #3(Figure 12)
	Block 7 TIME SINCE LAST INST (HRS)	The value of the property "Time_since_last_installed" (urn:plcs:rdl:pam738_751:Time_since_last_installed) in template table: Template #3(Figure 12)
	Block 8 TIME SINCE NEW (HRS)	The value of the property "Time_since_new" (urn:plcs:rdl:pam738_751:Time_since_new) in template table: Template #3(Figure 12)
	Block 9 TIME SINCE OVERHAUL (HRS)	The value of the property "Time_since_overhaul" (urn:plcs:rdl:pam738_751:Time_since_overhaul) in template table: Template #3(Figure 12)
	Block 12 HSF	The value of the property "Hot_section_factors" (urn:plcs:rdl:pam738_751:Hot_section_factors) in template table: Template #3(Figure 12)
	Block 13 METER HRS	The value of the property "Meter_hour_readings" (urn:plcs:rdl:pam738_751:Meter_hour_readings) in template table: Template #3(Figure 12)
	Block 15a COMPONENT CUMULATIVE COUNT/HOURS; LCF 1	The value of the property "LCF1" (urn:plcs:rdl:pam738_751:LCF1) in template table: Template #3(Figure 12)
	Block 15b COMPONENT CUMULATIVE COUNT/HOURS; LCF 2	The value of the property "LCF2" (urn:plcs:rdl:pam738_751:LCF2) in template table: Template #3(Figure 12)
	Block 15c COMPONENT CUMULATIVE COUNT/HOURS; TTI	The value of the property "TTI" (urn:plcs:rdl:pam738_751:TTI) in template table: Template #3(Figure 12)
	Block 15d COMPONENT CUMULATIVE COUNT/HOURS; OP HOURS	The value of the property "Cumulative_operating_hours" (urn:plcs:rdl:pam738_751:Cumulative_operating_hours) in template table: Template #3(Figure 12)
	Block 16 APU SSN	The value of the property "Number_starts_since_new" (urn:plcs:rdl:pam738_751:Number_starts_since_new) in template table: Template #3(Figure 12)
	Block 17 APU HRS	The value of the property "Hours_since_new" (urn:plcs:rdl:pam738_751:Hours_since_new) in template table: Template #3(Figure 12)
	Block 18 APU SSO	The value of the property "Number_starts_since_overhauled" (urn:plcs:rdl:pam738_751:Number_starts_since_overhauled) in template table: Template #3(Figure 12)
	Block 24 HOURS (NHA), and Block 54 HOURS (NHA)	The value of the property "Aircraft_hours_property" (urn:plcs:rdl:pam738_751:Aircraft_hours_property), or if NHA is not the Aircraft "NHA_operating_hours" (urn:plcs:rdl:pam738_751:NHA_operating_hours), in template table: Template #3(Figure 12)
	Block 25 NHA CUMULATIVE COUNTS/HOURS, and Block 55 NHA CUMULATIVE COUNTS/HOURS	The value of the property "NHA_cumulative_counts_hours" (urn:plcs:rdl:pam738_751:NHA_cumulative_counts_hours) in template table: Template #3(Figure 12)
	Block 26 APU START METER, and Block 56 APU START METER	The value of the property "APU_start_meter" (urn:plcs:rdl:pam738_751:APU_start_meter) in template table: Template #3(Figure 12)
	Block 27 APU HOUR METER, and Block 57 APU HOUR METER	The value of the property "APU_hour_meter" (urn:plcs:rdl:pam738_751:APU_hour_meter) in template table: Template #3(Figure 12)
	Block 29 HISTORY RECORDER READING, and Block 59 HISTORY RECORDER READING	The value of the property "History_recorder_reading" (urn:plcs:rdl:pam738_751:History_recorder_reading) in template table: Template #3(Figure 12)
	Block 49g CUMULATIVE COUNTS/hours LAST DEPOT REPAIR	The value of the property "Cumulative_counts_hours_last_depot_repair" (urn:plcs:rdl:pam738_751:Cumulative_counts_hours_last_depot_repair) in template table: Template #3(Figure 12)
unit_class_name Error T6: product_property_value does not have a parameter unit_class_name	For Block 6: "Count" (urn:plcs:rdl:std:Count)	The unit corresponding to the property "Number_previous_overhauls" (urn:plcs:rdl:pam738_751:Number_previous_overhauls) in template table: Template #3(Figure 12)
	For Block 7: "hour" (urn:plcs:rdl:std:hour)	The unit corresponding to the property "Time_since_last_installed" (urn:plcs:rdl:pam738_751:Time_since_last_installed) in template table: Template #3(Figure 12)
	For Block 8: "hour" (urn:plcs:rdl:std:hour)	The unit corresponding to the property "Time_since_new" (urn:plcs:rdl:pam738_751:Time_since_new) in template table: Template #3(Figure 12)
	For Block 9: "hour" (urn:plcs:rdl:std:hour)	The unit corresponding to the property "Time_since_overhaul" (urn:plcs:rdl:pam738_751:Time_since_overhaul) in template table: Template #3(Figure 12)
	For Block 12: "Hot_section_factor_unit" (urn:plcs:rdl:pam738_751:Hot_section_factor_unit)	The unit corresponding to the property "Hot_section_factors" (urn:plcs:rdl:pam738_751:Hot_section_factors) in template table: Template #3(Figure 12)
	For Block 13: "Hour_meter_unit" (urn:plcs:rdl:pam738_751:Hour_meter_unit)	The unit corresponding to the property "Meter_hour_readings" (urn:plcs:rdl:pam738_751:Meter_hour_readings) in template table: Template #3(Figure 12)
	For Block 15a: "LCF1_unit" (urn:plcs:rdl:pam738_751:LCF1_unit)	The unit corresponding to the property "LCF1" (urn:plcs:rdl:pam738_751:LCF1) in template table: Template #3(Figure 12)
	For Block 15b: "LCF2_unit" (urn:plcs:rdl:pam738_751:LCF2_unit)	The unit corresponding to the property "LCF2" (urn:plcs:rdl:pam738_751:LCF2) in template table: Template #3(Figure 12)
	For Block 15c: "TTI_count" (urn:plcs:rdl:pam738_751:TTI_count)	The unit corresponding to the property "TTI" (urn:plcs:rdl:pam738_751:TTI) in template table: Template #3(Figure 12)
	For Block 15d: "hour" (urn:plcs:rdl:std:hour)	The unit corresponding to the property "Cumulative_operating_hours" (urn:plcs:rdl:pam738_751:Cumulative_operating_hours) in template table: Template #3(Figure 12)
	For Block 16: "Engine_starts" (urn:plcs:rdl:std:Engine_starts)	The unit corresponding to the property "Number_starts_since_new" (urn:plcs:rdl:pam738_751:Number_starts_since_new) in template table: Template #3(Figure 12)
	For Block 17: "Aircraft_hour" (urn:plcs:rdl:pam738_751:Aircraft_hour)	The unit corresponding to the property "Hours_since_new" (urn:plcs:rdl:pam738_751:Hours_since_new) in template table: Template #3(Figure 12)
	For Block 18: "Engine_starts" (urn:plcs:rdl:std:Engine_starts)	The unit corresponding to the property "Number_starts_since_overhauled" (urn:plcs:rdl:pam738_751:Number_starts_since_overhauled) in template table: Template #3(Figure 12)
	For Block 24: "Aircraft_hour" (urn:plcs:rdl:pam738_751:Aircraft_hour) or "hour" (urn:plcs:rdl:std:hour), and Block 54: "Aircraft_hour" (urn:plcs:rdl:pam738_751:Aircraft_hour) or "hour" (urn:plcs:rdl:std:hour)	The unit "Aircraft_hour" (urn:plcs:rdl:pam738_751:Aircraft_hour) corresponding to the property "Aircraft_hours_property" (urn:plcs:rdl:pam738_751:Aircraft_hours_property), or if NHA is not the Aircraft: the unit "hour" (urn:plcs:rdl:std:hour) corresponding to the property "NHA_operating_hours" (urn:plcs:rdl:pam738_751:NHA_operating_hours), in template table: Template #3(Figure 12)
	For Block 25: "hour" (urn:plcs:rdl:std:hour), and Block 55: "hour" (urn:plcs:rdl:std:hour)	The unit corresponding to the property "NHA_cumulative_counts_hours" (urn:plcs:rdl:pam738_751:NHA_cumulative_counts_hours) in template table: Template #3(Figure 12)
	For Block 26: "APU_start_meter_unit" (urn:plcs:rdl:pam738_751:APU_start_meter_unit), and Block 56: "APU_start_meter_unit" (urn:plcs:rdl:pam738_751:APU_start_meter_unit)	The unit corresponding to the property "APU_start_meter" (urn:plcs:rdl:pam738_751:APU_start_meter) in template table: Template #3(Figure 12)
	For Block 27: "Hour_meter_unit" (urn:plcs:rdl:pam738_751:Hour_meter_unit), and Block 57: "Hour_meter_unit" (urn:plcs:rdl:pam738_751:Hour_meter_unit)	The unit corresponding to the property "APU_hour_meter" (urn:plcs:rdl:pam738_751:APU_hour_meter) in template table: Template #3(Figure 12)
	For Block 29: "History_recorder_unit" (urn:plcs:rdl:pam738_751:History_recorder_unit), and Block 59: "History_recorder_unit" (urn:plcs:rdl:pam738_751:History_recorder_unit)	The unit corresponding to the property "History_recorder_reading" (urn:plcs:rdl:pam738_751:History_recorder_reading) in template table: Template #3(Figure 12)
	For Block 49G: "hour" (urn:plcs:rdl:std:hour)	The unit corresponding to the property "Cumulative_counts_hours_last_depot_repair" (urn:plcs:rdl:pam738_751:Cumulative_counts_hours_last_depot_repair) in template table: Template #3(Figure 12)
unit_ecl_id Error T6: product_property_value does not have a parameter unit_ecl_id	"'urn:plcs:rdl:pam738_751'"
rep_class_name Error T6: product_property_value does not have a parameter rep_class_name	"PAM738-751context"
rep_ecl_id Error T6: product_property_value does not have a parameter rep_ecl_id	"'urn:plcs:rdl:pam738_751'"
property Error T6: product_property_value does not have a parameter property	The Assigned_property entity instantiated by the template assigning_product_property.

Template #5 (Figure 12): assigning_calendar_date
Description	Creation date for property value. Since DA2410 does not provide dates for property creation, the date for when the property was entered on the form is used, i.e. the date of the activity.
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	The 'year' component of the date of the activity: Block 33 DATE REMOVED, or Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED, or Block 75 DATE SHIPPED	Calendar_date year_component
month	The 'month' component of the date of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date month_component
day	The 'day' component of the date of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date day_component
items	Property_value_representation	The items to which the date is assigned.

The use of template #6 assigning_activity in Figure 12 is identical to, and described in, template table: Template #1(Figure 10).

States of the Reportable item

The DA2410 form records a number of states of the reportable item and the next higher assembly, such as the fault state of the reportable item and the serviceability state.

In ISO 10303-239 PLCS a distinction is made between states that a product could possibly be in, the set of all fault states for example, and the actual state that a product is in. These are referred to defined states and observed states respectively and are represented by State_definition and State_observed.

An observed state is related to the defined state (State_definition), of which it is an occurrence, by State_assessment and State_assertion.

The State_assessment indicates that an assumption has been made that something, such as a Product_as_realized, is in a state (State_observed) that resembles the state defined by the State_definition.

The State_assertion is used to assert that, based on evidence such as measurements, something, such as a Product_as_realized, is in a state (State_observed) that is equal to the state defined by the State_definition.

The representations of defined and observed states are described in the capabilities C007: representing_state_type and C041: representing_state_observed. The representation of an assessed state is detailed in the template assigning_assessed_state and the representation of an asserted state is detailed in the template assigning_asserted_state.

An EXPRESS-G diagram showing how the state of the reportable item is identified is shown below.

Figure 13 — EXPRESS-G diagram for state on reportable item

The following templates are used in the diagram and represent the various blocks on the DA2410 form.

The use of template #1 assigning_reference_data in Figure 13 is identical to, and described in, template table: Template #1(Figure 12).

The use of template #2 assigning_reference_data in Figure 13 is identical to, and described in, template table: Template #2(Figure 12).

Template #3 (Figure 13): assigning_assessed_state
Description	An assessed state of an item, expressed in terms of State_definition (e.g. failure code).
Parameter name:	Parameter value:	Parameter description:
state_class_name	For Block 10 FAILURE CODE: "Failure_code" (urn:plcs:rdl:pam738_751:Failure_code)	The class name of the External_class corresponding to the State_definition name.
	For Block 43 INSPECTION AND ACTION CODES: "Inspection_and_action_codes" (urn:plcs:rdl:pam738_751:Inspection_and_action_codes)	The class name of the External_class corresponding to the State_definition name.
	For Block 37: "Malfunction_code" (urn:plcs:rdl:pam738_751:Malfunction_code)	The class name of the External_class corresponding to the State_definition name.
state_ecl_id	"'urn:plcs:rdl:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @state_class_name.
assigned_to	Product_as_individual_view	The activity, product, individual, task_method, etc to which the state is assigned

Template #4 (Figure 13): assigning_calendar_date
Description	The date the state was assessed. In DA2410, this corresponds best to 'date checked'. If that block is not used, another date should be used here, combined with the proper date_class_name.
Parameter name:	Parameter value:	Parameter description:
date_class_name	"Date_actual_assessment" (urn:plcs:rdl:std:Date_actual_assessment)	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 Block 39 DATE CHECKED	Calendar_date year_component
month	The 'month' component of Block 39 DATE CHECKED	Calendar_date month_component
day	The 'day' component of Block 39 DATE CHECKED	Calendar_date day_component
items	State_assessment	The items to which the date is assigned.

Template #5 (Figure 13): assigning_business_specific_reference_data
Description	Encoding of when the state (fault) was discovered.
Parameter name:	Parameter value:	Parameter description:
class_name	For Block 38 WHEN DISCOVERED: "When_discovered_codes" (urn:plcs:rdl:pam738_751:When_discovered_codes)	The name of the class in the business specific reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the business_specific External_class_library that stores the class.
plcs_class_name	"State_context" (urn:plcs:rdl:std:State_context)	The name of the first plcs superclass encountered in the plsc standard reference data library (External_class) when traversing the class hierarchy for the assigned business specific (External_class).
items	Activity_actual	The activity that is being reported on by the DA2410 form, represented as an Activity_actual.

Template #6 (Figure 13): assigning_asserted_state
Description	An assertion (verification) of a state of an item, expressed in terms of State_definition (e.g. failure code).
Parameter name:	Parameter value:	Parameter description:
state_class_name	For Block 47 ACTUAL FAILURE CODE: "Failure_code" (urn:plcs:rdl:pam738_751:Failure_code)	The class name of the External_class corresponding to the State_definition name.
state_class_name	For Block 49a FAIL CODE: "Failure_code" (urn:plcs:rdl:pam738_751:Failure_code)	The class name of the External_class corresponding to the State_definition name.
state_ecl_id	"'urn:plcs:rdl:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @state_class_name.
assigned_to	Product_as_individual_view	The activity, product, individual, task_method, etc to which the state is assigned

Template #7 (Figure 13): assigning_calendar_date
Description	The date of the state assertion. Since DA2410 does not record the date of the assertion of states, the date of the activity itself should be used.
Parameter name:	Parameter value:	Parameter description:
date_class_name	"Date_actual_assertion" (urn:plcs:rdl:std:Date_actual_assertion)	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 of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date year_component
month	The 'month' component of the date of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date month_component
day	The 'day' component of the date of the activity: Block 33 DATE REMOVED and Block 39 DATE CHECKED; (use one date for each above), or Block 63 DATE INSTALLED; or Block 75 DATE SHIPPED	Calendar_date day_component
items	State_assertion	The items to which the date is assigned.

The use of template #8 assigning_activity in Figure 13 is identical to, and described in, template table: Template #1(Figure 10).

APU, History recorder, On Board Monitoring System

The DA2410 form also provides details of the Auxiliary Power Unit, History recorder, On Board Monitoring System on the aircraft. These are treated like any other products therefore represented by instances of Product_as_individuals as described in Section: Reportable item identification. Properties are represented by instances of Assigned_property as described in Section: Properties of the Reportable item. These two sections also contain more detailed information about the APU, History recorder, and the On Board Monitoring System.

The APU, History recorder, and the On Board Monitoring System are related back to the Activity_actual that represents the DA 2410 form by an instance of Applied_activity_assignments classified as:

"Activity_input_APU" (urn:plcs:rdl:pam738_751:Activity_input_APU) for the APU;
"Activity_input_History_recorder" (urn:plcs:rdl:pam738_751:Activity_input_History_recorder) for the History recorder";
"Activity_input_On_board_monitoring_system" (urn:plcs:rdl:pam738_751:Activity_input_On_board_monitoring_system) for the on board monitoring system.

The use of Applied_activity_assignment is detailed in the template assigning_activity.

Installation/Removal position on the Aircraft

The DA2410 form specifies the position of the reportable item on the aircraft by referring to the next higher assembly from which the reportable item is removed. The next higher assembly is treated like any other product and is therefore represented by instances of Product_as_individuals as described in Section: Reportable item identification.

The relationship between the reportable item and the next higher assembly is represented by a Next_assembly_usage This is described in the capability representing_product_as_realized_assembly
Error C1: Capability representing_product_as_realized_assembly not in dex_index.xml
.

The reportable item can be installed or removed from a series of aircraft. The dates when the installation / removal occurs is represented by dated effectivities (Dated_effectivity) applied to the Next_assembly_usage. This gives the start and end date for which the Next_assembly_usage. is valid. In other words the date of installation / removal. The use of effectivities is described in the capability C006: assigning_effectivity and the assignment of a dated effectivity is detailed in the template assigning_dated_effectivity.

An EXPRESS-G diagram showing how the position of the reportable item on the aircraft is represented is shown below in Figure 14.

Figure 14 — EXPRESS-G diagram for installation/removal position on aircraft

The following templates are used in the diagram and represent the various blocks on the DA2410 form.

The use of template #1 assigning_identification in Figure 14 is identical to, and described in, template table: Template #1(Figure 11).

The use of template #2 assigning_identification in Figure 14 is identical to, and described in, template table: Template #2(Figure 11).

The use of template #3
Error T7: assigning_code does not exist in capability: assigning_reference_data
assigning_code in Figure 14 is identical to, and described in, template table: Template #3(Figure 11).

The use of template #4 assigning_identification in Figure 14 is identical to, and described in, template table: Template #5(Figure 11).

The use of template #5 assigning_identification in Figure 14 is identical to, and described in, template table: Template #6(Figure 11).

The use of template #6 assigning_organization in Figure 14 is identical to, and described in, template table: Template #7(Figure 11).

The use of template #7
Error T7: assigning_code does not exist in capability: assigning_reference_data
assigning_code in Figure 14 is identical to, and described in, template table: Template #8(Figure 11).

The use of template #8 assigning_product_property in Figure 14 is identical to, and described in, template table: Template #3(Figure 12).

The use of template #9
Error T7: product_property_value does not exist in capability: representing_properties_numerically
product_property_value in Figure 14 is identical to, and described in, template table: Template #4(Figure 12).

The use of template #10 assigning_calendar_date in Figure 14 is identical to, and described in, template table: Template #5(Figure 12).

The use of template #11 assigning_assessed_state in Figure 14 is identical to, and described in, template table: Template #3(Figure 13).

The use of template #12 assigning_calendar_date in Figure 14 is identical to, and described in, template table: Template #4(Figure 12).

The use of template #13 assigning_asserted_state in Figure 14 is identical to, and described in, template table: Template #5(Figure 13).

The use of template #14 assigning_calendar_date in Figure 14 is identical to, and described in, template table: Template #6(Figure 12).

The use of template #15 assigning_activity in Figure 14 is identical to, and described in, template table: Template #1(Figure 10).

Template #16 (Figure 14): assigning_dated_effectivity
Description	Start date for item being installed on aircraft (set by activity installation).
Parameter name:	Parameter value:	Parameter description:
start_year	The year component of Block 63 DATE INSTALLED	Calendar_date year_component of the effectivity start date and time.
start_month	The month component of Block 63 DATE INSTALLED	Calendar_date month_component of the effectivity start date and time.
start_day	The day component of Block 63 DATE INSTALLED	Calendar_date day_component of the effectivity start date and time.
start_hour	"" (not given in DA2410)	Local_time hour_component of the effectivity start date and time.
start_minute	"" (not given in DA2410)	Local_time minute_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_second	"" (not given in DA2410)	Local_time day_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
end_year	The year component of Block 33 DATE REMOVED	Calendar_date year_component of the effectivity end date and time. This parameter is optional. If not given, it will remain unset.
end_month	The month component of Block 33 DATE REMOVED	Calendar_date month_component of the effectivity end date and time. This parameter is optional. If not given, it will remain unset.
end_day	The day component of Block 33 DATE REMOVED	Calendar_date day_component of the effectivity end date and time. This parameter is optional. If not given, it will remain unset.
end_hour	"" (not given in DA2410)	Local_time hour_component of the effectivity end date and time. This parameter is optional. If not given, it will remain unset.
end_minute	"" (not given in DA2410)	Local_time minute_component of the effectivity end date and time. This parameter is optional. If not given, it will remain unset.
end_second	"" (not given in DA2410)	Local_time second_component of the effectivity end date and time. This parameter is optional. If not given, it will remain unset.
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	Next_assembly_usage	The items to which the effectivity is assigned, e.g. an identification_assignment, a next_assembly_usage, etc.

Replaced Parts

The DA2410 form provides details of the parts that were replaced during a repair/overhaul cycle. (Blocks 49).

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 and 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. The DA2410 reports on the activity undertaken, it does not make any reference to either the task or the resources. It simply lists the parts that were replaced during an activity. This could be represented in ISO 10303-239 PLCS by assigning the Activity_actual to the representation of the replaced parts. However, in order to enable the representation of the tasks and resources at some stage, it is recommended that the replaced parts are represented by 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.

Figure 15 — EXPRESS-G diagram for recording parts used

The following templates are used in the diagram and represent the various blocks on the DA2410 form:

Template #1 (Figure 15): assigning_reference_data
Description	The correct Maintenance Action Code for each failing item.
Parameter name:	Parameter value:	Parameter description:
class_name	For Block 49c ACT: "Maintenance_action_codes" (urn:plcs:rdl:pam738_751:Maintenance_action_codes)	The name of the class in the reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	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	Total quantity for each failing item.
Parameter name:	Parameter value:	Parameter description:
value	Block 49b QTY	The value of the quantity. Default value is 1. The datatype is always 'any_number_value' and should not be registered together with the value, i.e. enter the value as a number, without datatype.

Note:
Mapping of Block 49a is described in template table: Template #3(Figure 13).
Mapping of Block 49d is described in template table: Template #1(Figure 11).
Mapping of Block 49e is described in template table: Template #2(Figure 11).
Mapping of Block 49f is described in template table: Template #5(Figure 11).
Mapping of Block 49g is described in template table: Template #3(Figure 12) and template table: Template #4(Figure 12).

Change of Part Number, Serial Number, and NSN

During repair or overhaul, an item may be given a new Part Number, Serial Number and NSN code. Typically when a change is made to the fit, form or functionality. In order to track the reportable item through life, it is important to maintain a history of the identifiers that have been assigned to the reportable item. This is represented by assigning multiple identifiers to the reportable item and using dated effectivity (applicability) to determine which of the Part Number, Serial Number, and NSN identifiers are applicable at any moment in time.

The use of effectivities is described in the capability C006: assigning_effectivity and the assignment of a dated effectivity is detailed in the template assigning_dated_effectivity.

An EXPRESS-G diagram showing how the changes to Part Number, Serial Number and NSN codes is represented shown below in Figure 16.

Figure 16 — EXPRESS-G diagram for new PN, SN and NSN

The following templates are used in the diagram and represent the various blocks on the DA2410 form.

The use of template #1 assigning_identification in Figure 16 is identical to, and described in, template table: Template #2(Figure 11).

Template #2 assigning_dated_effectivity in Figure 16 should not be instantiated when assigning an end date to the effectivity. Instead, the relevant existing dated effectivity should be extended with the end date, as described in template table: Template #3(Figure 16) below.

Template #3 (Figure 16): representing_date_time
Description	Adding an End Date to an existing dated effectivity by instantiating an attribute value to entity Dated_effectivity attribute end_bound. The end_bound date of this effectivity (Previous Part number) should be the same as the start_bound date of the effectivity for the New Part number.
Parameter name:	Parameter value:	Parameter description:
year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the date and time.
month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the date and time.
day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the date and time.
hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the date and time.
minute	"" (since there is no time given on DA2410)	Local_time minute_component of the date and time. This parameter is optional. If not given, it will remain unset.
second	"" (since there is no time given on DA2410)	Local_time second_component of the date and time. This parameter is optional. If not given, it will remain unset.
sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.

The use of template #4 assigning_code in Figure 16 is identical to, and described in, template table: Template #3(Figure 11).

Template #5 assigning_dated_effectivity in Figure 16 should not be instantiated when assigning an end date to the effectivity. Instead, the relevant existing dated effectivity should be extended with the end date, as described in template table: Template #6(Figure 16) below.

Template #6 (Figure 16): representing_date_time
Description	Adding an End Date to an existing dated effectivity by instantiating an attribute value to entity Dated_effectivity attribute end_bound. The end_bound date of this effectivity (Previous NSN code) should be the same as the start_bound date of the effectivity for the New NSN code.
Parameter name:	Parameter value:	Parameter description:
year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the date and time.
month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the date and time.
day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the date and time.
hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the date and time.
minute	"" (since there is no time given on DA2410)	Local_time minute_component of the date and time. This parameter is optional. If not given, it will remain unset.
second	"" (since there is no time given on DA2410)	Local_time second_component of the date and time. This parameter is optional. If not given, it will remain unset.
sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.

The use of template #7 assigning_identification in Figure 16 is identical to, and described in, template table: Template #5(Figure 11).

Template #8 assigning_dated_effectivity in Figure 16 should not be instantiated when assigning an end date to the effectivity. Instead, the relevant existing dated effectivity should be extended with the end date, as described in template table: Template #9(Figure 16) below.

Template #9 (Figure 16): representing_date_time
Description	Adding an End Date to an existing dated effectivity by instantiating an attribute value to entity Dated_effectivity attribute end_bound. The end_bound date of this effectivity (Previous Part Serial number) should be the same as the start_bound date of the effectivity for the New Part Serial number.
Parameter name:	Parameter value:	Parameter description:
year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the date and time.
month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the date and time.
day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the date and time.
hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the date and time.
minute	"" (since there is no time given on DA2410)	Local_time minute_component of the date and time. This parameter is optional. If not given, it will remain unset.
second	"" (since there is no time given on DA2410)	Local_time second_component of the date and time. This parameter is optional. If not given, it will remain unset.
sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.

The use of template #10 assigning_identification in Figure 16 is identical to, and described in, template table: Template #6(Figure 11).

Template #11 assigning_dated_effectivity in Figure 16 should not be instantiated when assigning an end date to the effectivity. Instead, the relevant existing dated effectivity should be extended with the end date, as described in template table: Template #12(Figure 16) below.

Template #12 (Figure 16): representing_date_time
Description	Adding an End Date to an existing dated effectivity by instantiating an attribute value to entity Dated_effectivity attribute end_bound. The end_bound date of this effectivity (Previous UID) should be the same as the start_bound date of the effectivity for the New UID.
Parameter name:	Parameter value:	Parameter description:
year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the date and time.
month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the date and time.
day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the date and time.
hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the date and time.
minute	"" (since there is no time given on DA2410)	Local_time minute_component of the date and time. This parameter is optional. If not given, it will remain unset.
second	"" (since there is no time given on DA2410)	Local_time second_component of the date and time. This parameter is optional. If not given, it will remain unset.
sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.

The use of template #13 assigning_identification in Figure 16 is identical to, and described in, template table: Template #2(Figure 11).

Template #14 (Figure 16): assigning_dated_effectivity
Description	Effectivity start date and time for the new part number, i.e. from which date and time this new part number is effective. Note: No end dates should be given.
Parameter name:	Parameter value:	Parameter description:
start_year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the effectivity start date and time.
start_month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the effectivity start date and time.
start_day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the effectivity start date and time.
start_hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the effectivity start date and time.
start_minute	"" (since there is no time given on DA2410)	Local_time minute_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_second	"" (since there is no time given on DA2410)	Local_time day_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
start_hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
start_minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.
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:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name class.
items	Identification_assignment	The items to which the effectivity is assigned, e.g. an identification_assignment, a next_assembly_usage, etc.

The use of template #15 assigning_code in Figure 16 is identical to, and described in, template table: Template #3(Figure 11).

Template #16 (Figure 16): assigning_dated_effectivity
Description	Effectivity start date and time for the new NSN, i.e. from which date and time this new NSN is effective. Note: No end dates should be given.
Parameter name:	Parameter value:	Parameter description:
start_year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the effectivity start date and time.
start_month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the effectivity start date and time.
start_day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the effectivity start date and time.
start_hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the effectivity start date and time.
start_minute	"" (since there is no time given on DA2410)	Local_time minute_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_second	"" (since there is no time given on DA2410)	Local_time day_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
start_hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
start_minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.
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:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name class.
items	Classification_assignment	The items to which the effectivity is assigned, e.g. an identification_assignment, a next_assembly_usage, etc.

The use of template #17 assigning_identification in Figure 16 is identical to, and described in, template table: Template #5(Figure 11).

Template #18 (Figure 16): assigning_dated_effectivity
Description	Effectivity start date and time for the new part serial number, i.e. from which date and time this new part serial number is effective. Note: No end dates should be given.
Parameter name:	Parameter value:	Parameter description:
start_year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the effectivity start date and time.
start_month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the effectivity start date and time.
start_day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the effectivity start date and time.
start_hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the effectivity start date and time.
start_minute	"" (since there is no time given on DA2410)	Local_time minute_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_second	"" (since there is no time given on DA2410)	Local_time day_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
start_hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
start_minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.
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:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name class.
items	Identification_assignment	The items to which the effectivity is assigned, e.g. an identification_assignment, a next_assembly_usage, etc.

The use of template #19 assigning_identification in Figure 16 is identical to, and described in, template table: Template #6(Figure 11).

Template #20 (Figure 16): assigning_dated_effectivity
Description	Effectivity start date and time for the new UID, i.e. from which date and time this new UID is effective. Note: No end dates should be given.
Parameter name:	Parameter value:	Parameter description:
start_year	The 'year' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date year_component of the effectivity start date and time.
start_month	The 'month' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date month_component of the effectivity start date and time.
start_day	The 'day' component of: Block 39 DATE CHECKED, or Block 63 DATE INSTALLED	Calendar_date day_component of the effectivity start date and time.
start_hour	"00" (since there is no time given on DA2410)	Local_time hour_component of the effectivity start date and time.
start_minute	"" (since there is no time given on DA2410)	Local_time minute_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_second	"" (since there is no time given on DA2410)	Local_time day_component of the effectivity start date and time. This parameter is optional. If not given, it will remain unset.
start_sense	"" (since there is no time given on DA2410)	The direction of the offset. Enumeration values: 'ahead', 'exact' or 'behind'.
start_hour_offset	"" (since there is no time given on DA2410)	The number of hours by which a time is offset from Coordinated Universal Time.
start_minute_offset	"" (since there is no time given on DA2410)	The number of minutes by which a time is offset from Coordinated Universal Time. The value of this attribute need not be specified. This parameter is optional. If not given, it will remain unset.
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:pam738_751'"	The identifier of the External_class_library storing the definition of the class referenced by the parameter @role_class_name class.
items	Identification_assignment	The items to which the effectivity is assigned, e.g. an identification_assignment, a next_assembly_usage, etc.

Inventory Gain and Loss

The DA2410 form specifies that a reportable item has been added to or removed from the inventory. The action of reporting this event, the DA 2410 form, is represented in ISO 10303-239 PLCS by an instantiation of an Activity_actual as previously described in Section: Activity Record.

In ISO 10303-239 PLCS a distinction is made between, actual products, such as an aircraft or engine, products that can be used as a resource to do a task and products that are managed in an inventory.

A product that is managed in an inventory is represented by a Managed_resource which refers the resource that is being managed, represented by a Resource_item. The Resource_item identifies a product type or actual product that is required for a particular task. In this case, the Resource_item links to the Product_as_individuals representing the reportable item, as described in Section: Reportable item identification.

ISO 10303-239 PLCS represents the event of increasing or decreasing the inventory by an instantiation of a Increasing_resource_event or Decreasing_resource_event respectively. Each resource event is linked back to the Activity_actual by an instance of Applied_activity_assignment. The use of Applied_activity_assignment is detailed in the template assigning_activity.

An EXPRESS-G diagram showing how the inventory event is represented is shown below.

Figure 17 — EXPRESS-G diagram for representing inventory events

The following templates are used in the diagram and represent the various blocks on the DA2410 form.

Template #1 (Figure 17): representing_count
Description	The total quantity for each item gained or lost to the inventory.
Parameter name:	Parameter value:	Parameter description:
value	"/NULL" (DA Form 2410 does not provide the quantity)	The value of the quantity. Default value is 1. The datatype is always 'any_number_value' and should not be registered together with the value, i.e. enter the value as a number, without datatype.

The use of template #2 assigning_activity in Figure 17 is identical to, and described in, template table: Template #1(Figure 10).

The use of template #3 assigning_activity in Figure 17 is identical to, and described in, template table: Template #1(Figure 10).

Template #4 (Figure 17): assigning_business_specific_reference_data
Description	Block 44 - The reason for the gains to the inventory
Parameter name:	Parameter value:	Parameter description:
class_name	"Equipment_gain_codes" (urn:plcs:rdl:pam738_751:Equipment_gain_codes)	The name of the class in the business specific reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the business_specific External_class_library that stores the class.
plcs_class_name	"Increasing_resource_event" (urn:plcs:rdl:std:Increasing_resource_event)	The name of the first plcs superclass encountered in the plsc standard reference data library (External_class) when traversing the class hierarchy for the assigned business specific (External_class).
items	Increasing_resource_event	The items to which the External_class is assigned.

Template #5 (Figure 17): assigning_business_specific_reference_data
Description	Block 66 - The reason for the loss to the inventory
Parameter name:	Parameter value:	Parameter description:
class_name	"Equipment_loss_codes" (urn:plcs:rdl:pam738_751:Equipment_loss_codes)	The name of the class in the business specific reference data library (External_class) being used to classify something
ecl_id	"'urn:plcs:rdl:pam738_751'"	The id of the business_specific External_class_library that stores the class.
plcs_class_name	"Decreasing_resource_event" (urn:plcs:rdl:std:Decreasing_resource_event)	The name of the first plcs superclass encountered in the plsc standard reference data library (External_class) when traversing the class hierarchy for the assigned business specific (External_class).
items	Decreasing_resource_event	The items to which the External_class is assigned.

Example instantiations

The following sections show some examples of the DA2410 forms and the corresponding ISO 10303-239 instantiations that represent them.

Example DA 2410 - Installation

The following example shows the information recorded on a DA 2410 to record the installation of a component on an aircraft. The example form is given in Table 2 and a corresponding DA2410 XML file (../examples/1_18_2006_10_58_05_AM_98C3.xml) is provided.

Block	Block Name	Block Value	Description
	Control number	010692	The item name.
1	NOMENCLATURE.	TAIL ROTOR GEARBOX	The item name.
2	NSN.	1615011051510	The National Stock Number of the item.
3	PART NUMBER.	70358-06600-043	The Part Number of the item.
4	SERIAL NUMBER.	A00600566A	The Serial Number of the item.
5	CAGE CODE.	78286	Contractor and Government Entity Code for the item.
6	NO. OF PREV O/Hs.	0	The number of times that the item has been overhauled. If the item has never been overhauled, enter "0." For Retirement Life Components/Modules and Condition Components/Modules enter "RC" or "CC" in this block.
7	TIME SINCE LAST INST (HRS).	0	The number of hours, to the nearest hour, that the item has operated since it was last installed.
8	TIME SINCE NEW (HRS).	2124	The total number of hours, to the nearest hour, that the item has been operated since it was new or rebuilt. For H-60 series APUs without an installed hour meter enter "0."
9	TIME SINCE OVERHAUL (HRS).	0	If the item has been overhauled before, enter the number of hours, to the nearest hour, that the item has operated since the last overhaul. If the item is a RC or CC item, enter "RC" or "CC." For H-60 series APUs, enter "0".
10	FAILURE CODE.	799	For new items enter "799." For other items enter the appropriate failure code from tables 1-2 or 1-3.
14	WUC.	06G01	Enter the work unit code that applies.
43	INSPECTION AND ACTION CODES.	A	A = serviceable item B = unserviceable item C = change in serviceability status resulted from the publication of an MWO, or other directive enter D = ? E = item for repair F = item for Overhaul
50	INSTALLED ON (NOMEN NHA).	HELICOPTER, UTILITY	The name of the next higher assembly on which the reportable item is installed.
51	NSN (NHA).	1520012984532	The NSN of the next higher assembly on which the reportable item is installed.
52	PART NUMBER (NHA).	UH-60L	The Part Number of the next higher assembly on which the reportable item is installed.
53	SERIAL NUMBER (NHA).	9326486	The Serial Number of the next higher assembly on which the reportable item is installed.
54	HOURS (NHA).	1498	The current aircraft hours, to the nearest hour, if the next higher assembly is an aircraft. If item is a component, enter the operating hours, to the nearest hour, since new or rebuild.
60	ACFT MODEL.	UH-60L	The Mission Design Series of the aircraft. Leave blank if block 50 is an engine, APU, or component/module.
61	ACFT S/N.	9326486	The aircraft Serial Number if the next higher assembly is an aircraft, otherwise leave blank.
62	MAINT LEVEL.	F	The maintenance level ("O" for AVUM, "F" for AVIM, or "D" for Depot) performing the action.
63	DATE INSTALLED.	2133	The Julian date that the reportable item was installed.
64	UIC (THIS ACTION).	WDLJC0	The Unit Identification Code of the organization doing the installation. If a contractor, enter the CAGE code prefixed with a "K."
65	MAN-HOURS (TO INSTALL).	5	The man-hours, in hours and tenths, it took to install the item in block 1.

Table 2 — DA 2410 form: Example

The following instance diagrams show the templates and entities that need to instantiated to represent the DA 2410 form shown in Table 2.

Figure 18 shows the entities and templates instantiated to represent the record of the installation activity. In addition properties of the activity, such as the time take to perform the activity is also shown.

Figure 18 — Instantiation diagram for reporting on the installation activity: Activity

Figure 19 shows the entities and templates instantiated to represent the reportable item.

Figure 19 — Instantiation diagram for reporting on the installation activity: Item

Figure 20 shows the entities and templates instantiated to represent position of the reportable item on the aircraft.

Figure 20 — Instantiation diagram for reporting on the installation activity: Position

The instance model in STEP ASCII exchange file format (ISO 10303 Part 28 syntax) is shown in examples/p28_1_18_2006_10_58_05_AM_98C3.xml The instance model in STEP ASCII exchange file format (ISO 10303 Part 28 syntax) is shown in examples/p21_1_18_2006_10_58_05_AM_98C3.p21

Example DA 2410 - Removal

The following example shows the information recorded on a DA 2410 to record the removal of a component from an aircraft. The example form is given in Table 3 and a corresponding DA2410 XML file (../examples/1_18_2006_10_58_05_AM_152C1.xml) is provided.

Block	Block Name	Block Value	Description
	Control number	R12704	The item name.
1	NOMENCLATURE.	SAS ACTUATOR	The item name.
2	NSN.	TAIL ROTOR GEARBOX	The National Stock Number of the item.
3	PART NUMBER.	70410-02500-049	The Part Number of the item.
4	SERIAL NUMBER.	B11204829	The Serial Number of the item.
5	CAGE CODE.	78286	Contractor and Government Entity Code for the item.
6	NO. OF PREV O/Hs.	0	The number of times that the item has been overhauled. If the item has never been overhauled, enter "0." For Retirement Life Components/Modules and Condition Components/Modules enter "RC" or "CC" in this block.
7	TIME SINCE LAST INST (HRS).	0	The number of hours, to the nearest hour, that the item has operated since it was last installed.
8	TIME SINCE NEW (HRS).	1968	The total number of hours, to the nearest hour, that the item has been operated since it was new or rebuilt. For H-60 series APUs without an installed hour meter enter "0."
9	TIME SINCE OVERHAUL (HRS).	0	If the item has been overhauled before, enter the number of hours, to the nearest hour, that the item has operated since the last overhaul. If the item is a RC or CC item, enter "RC" or "CC." For H-60 series APUs, enter "0".
10	FAILURE CODE.	381	For new items enter "799." For other items enter the appropriate failure code from tables 1-2 or 1-3.
14	WUC.	06G01	Enter the work unit code that applies.
20	REMOVED FROM (NOMEN NHA).	HELICOPTER, UTILITY	The name of the next higher assembly, from which the item was removed.
21	NSN (NHA).	1520012984532	The National Stock Number of the next higher assembly, from which the item was removed.
22	PART NUMBER (NHA).	UH-60L	The Part Number of the next higher assembly, from which the item was removed.
23	SERIAL NUMBER (NHA).	9326520	The Serial Number of the next higher assembly from which the item was removed.
24	HOURS (NHA).	1550	The current aircraft hours, to the nearest hour, if the next higher assembly is an aircraft. If the next higher assembly is a component, enter the components operating hours since new.
30	ACFT MODEL.	UH-60L	The aircraft Mission Design Series if the next higher assembly is an aircraft, otherwise leave blank.
31	ACFT S/N.	9326520	The aircraft Serial Number if the next higher assembly is an aircraft.
33	DATE REMOVED.	2127	The Julian date that the removal action was completed.
34	UIC.	WFJ4C0	The Unit Identification Code for the organization taking this action. If a contractor, enter the CAGE code prefixed with a "K."
35	MAN-HOURS (To Remove).	1	The man-hours it took to remove the item, in hours and tenths. (See Time Conversion Codes, table 1-12 , at the end of chapter 1 or the backside of DA Form 2408.)
37	MALFUNCTION CODE.	2	The Malfunction Effect Code (table 1-6) or the front side of DA Form 2408) that most closely described the effect the malfunction had on the mission.
38	WHEN DISCOVERED.	K	The When Discovered Code ( Table 1-4 or the front side of DA Form 2408) that identifies when the failure was first detected.

Table 3 — DA 2410 form: Example

The following instance diagrams show the templates and entities that need to instantiated to represent the DA 2410 form shown in Table 3.

Figure 21 shows the entities and templates instantiated to represent the record of the removal activity. In addition properties of the activity, such as the time take to perform the activity is also shown.

Figure 21 — Instantiation diagram for reporting on the removal activity: Activity

Figure 22 shows the entities and templates instantiated to represent the reportable item.

Figure 22 — Instantiation diagram for reporting on the removal activity: Item

Figure 23 shows the entities and templates instantiated to represent position of the reportable item on the aircraft.

Figure 23 — Instantiation diagram for reporting on the removal activity: Position

The instance model in STEP ASCII exchange file format (ISO 10303 Part 28 syntax) is shown in examples/p28_1_18_2006_10_58_05_AM_152C1.xml The instance model in STEP ASCII exchange file format (ISO 10303 Part 28 syntax) is shown in examples/p21_1_18_2006_10_58_05_AM_152C1.p21

Business concept templates

A template is a specification of a set of entities that need to be instantiated to represent a given set of information.

No templates have been developed specifically for this business concept. All the templates used have been defined in capabilities.

Dependent capabilities

This business concept "2410_form" is dependent on the following capabilities:

Model reference data

The following classes of reference data are required for this capability:

APU_hour_meter(urn:plcs:rdl:pam738_751:APU_hour_meter)

DAFrom block: 27 APU HOUR METER. DAFrom block: 57 APU HOUR METER. For H-60 series aircraft enter the reading from the APU hour meter at the time of APU removal. If the APU does not have a hour meter, leave blank. The unit of measure for the property is: HourMeterUnit

APU_start_meter(urn:plcs:rdl:pam738_751:APU_start_meter)

DAFrom block: 26 APU START METER. DAFrom block: 56 APU START METER. For H-60 series aircraft enter the reading from the APU start meter at the time of APU removal. If the APU does not have a start meter, leave blank. The unit of measure for the property is: APUStartMeterUnit

Activity_input(urn:plcs:rdl:std:Activity_input)

An Activity_input is an Applied_activity_assignment class whose members are inputs to an Activity.

Activity_input_APU(urn:plcs:rdl:pam738_751:Activity_input_APU)

An Activity_input_APU is an Activity_input that relates a product to an activity in the role of a APU.

Activity_input_History_recorder(urn:plcs:rdl:pam738_751:Activity_input_History_recorder)

An Activity_input_History_recorder is an Activity_input that relates a product to an activity in the role of a History_recorder.

Activity_input_On_board_monitoring_system(urn:plcs:rdl:pam738_751:Activity_input_On_board_monitoring_system)

An Activity_input_On_board_monitoring_system is an Activity_input that relates a product to an activity in the role of a On_board_monitoring_system.

Activity_input_Reportable_item(urn:plcs:rdl:pam738_751:Activity_input_Reportable_item)

An Activity_input_Reportable_item is an Activity_input that relates a product to an activity in the role of a Reportable_item.

Activity_output(urn:plcs:rdl:std:Activity_output)

An Activity_output is an Applied_activity_assignment class whose members are outputs from an Activity.

Aircraft_hour(urn:plcs:rdl:pam738_751:Aircraft_hour)

An Aircraft_hour is an hour operated by an aircraft.

CAGE_code(urn:plcs:rdl:std:CAGE_code)

A CAGE_code is an Organization_assigned_code. A CAGE (Commercial & Government Entity) Code is a five (5) position code that identifies companies doing or wishing to do business with the Federal Government. The codes are assigned by Defense Logistics Information Service (DLIS). The format of the code is that the first and fifth position must be numeric. The second, third and fourth may be any mixture of alpha/numeric excluding I and O. All positions are non-significant. For details see: http://www.dlis.dla.mil/cage_welcome.asp

Component_cumulative_count_hours(urn:plcs:rdl:pam738_751:Component_cumulative_count_hours)

DAFrom block: 15 COMPONENT CUMULATIVE COUNT/HOURS. For T700 series engines, components/modules, and subcomponents enter the total cumulative counts/hours for the item in block 1. This entry is also required for history recorders. Enter only operating hours, block 15.d., for components/modules, entered on the reverse side of the engine DA Form 2408-16-1, that do not require a separate DA Form 2408-16-1. If the item is new enter 0. The unit of measure for the property is: OperatingHour

Cumulative_counts_hours_last_depot_repair(urn:plcs:rdl:pam738_751:Cumulative_counts_hours_last_depot_repair)

DAFrom block: 49g CUMULATIVE COUNTS/HOURS LAST DEPOT REPAIR. For T700 series engines enter the total cumulative counts upon removal of repair parts from the engine or major components/modules. The counts and operating hours can be found on the DA Form 2408-16-1. For H-60 series APUs, enter the number of prior overhauls in the LCF 1 block, starts since overhaul in the LCF 2 block, starts since new in the TTI block, and total operating hours since new for the repair part or ubcomponent. The unit of measure for the property is: OperatingHour

Cumulative_operating_hours(urn:plcs:rdl:pam738_751:Cumulative_operating_hours)

DAFrom block: 15d OP HOURS. The total cumulative operating hours. The unit of measure for the property is: OperatingHour

[DA2410Form-Unservicable]

Error RDL1: The class DA2410Form-Unservicable does not exist in RDL at urn urn:plcs:rdl:pam738_751. Check the dexlib/data/refdata/rdl_index.xml

DA2410Form-Inspection(urn:plcs:rdl:pam738_751:DA2410Form-Inspection)

A DA2410Form-Inspection is an activity_actual that records the actvity to inspect a reportable item that has been reported on a DA 2140 form.

DA2410Form-Overhaul(urn:plcs:rdl:pam738_751:DA2410Form-Overhaul)

A DA2410Form-Overhaul is an activity_actual that records the actvity to overhaul a reportable item that has been reported on a DA 2140 form.

DA2410Form-Removal(urn:plcs:rdl:pam738_751:DA2410Form-Removal)

A DA2410Form-Removal is an activity_actual that records the actvity to remove a reportable item that has been reported on a DA 2140 form.

DA2410Form-InventoryLoss(urn:plcs:rdl:pam738_751:DA2410Form-InventoryLoss)

A DA2410Form-InventoryGain is an activity_actual that records the actvity, as reported on a DA 2140 form, to remove a reportable item from an inventory

DA2410Form-InventoryGain(urn:plcs:rdl:pam738_751:DA2410Form-InventoryGain)

A DA2410Form-InventoryGain is an activity_actual that records the actvity, reported on a DA 2140 form, to add a reportable item to an inventory.

History_recorder_reading(urn:plcs:rdl:pam738_751:History_recorder_reading)

DAFrom block: 29 HISTORY RECORDER READING. If a T700 series engine is entered in block 1 or block 20, enter the current reading from the engine history recorder. The unit of measure for the property is: HistoryRecorderUnit DAFrom block: 58 HISTORY RECORDER READING. If a T700 series engine is entered in block 1 or block 50, enter the current reading from the engine history recorder.

Hot_section_factors(urn:plcs:rdl:pam738_751:Hot_section_factors)

DAFrom block: 12 HSF. For T703 engines, the total hot section factors. The unit of measure for the property is: HotSectionFactorUnit

Hours_since_new(urn:plcs:rdl:pam738_751:Hours_since_new)

DAFrom block: 17 APU HRS. The total hours since new for the APU. The unit of measure for the property is: AircraftHour

LCF1(urn:plcs:rdl:pam738_751:LCF1)

DAFrom block: 15a LCF 1. For T700 series engines, components/modules, or subcomponents enter the total cumulative LCF1 counts. The unit of measure for the property is: LCF1Unit

LCF2(urn:plcs:rdl:pam738_751:LCF2)

DAFrom block: 15b LCF 2. For T700 series engines, components/modules, or subcomponents enter the total cumulative LCF 2 counts. The unit of measure for the property is: LCF2Unit

Man_hours_to_install(urn:plcs:rdl:pam738_751:Man_hours_to_install)

DAFrom block: 65 MAN-HOURS (TO INSTALL). The man-hours, in hours and tenths, it took to install the item in block 1. The unit of measure for the property is: ManHour

Man_hours_to_remove(urn:plcs:rdl:pam738_751:Man_hours_to_remove)

DAFrom block: 35 MAN-HOURS (To Remove). The man-hours it took to remove the item, in hours and tenths. (See Time Conversion Codes, table 1-12 , at the end of chapter 1 or the backside of DA Form 2408.) The unit of measure for the property is: ManHour

Man_hours_to_repair_or_overhaul(urn:plcs:rdl:pam738_751:Man_hours_to_repair_or_overhaul)

DAFrom block: 42 MAN-HOURS TO REPAIR/OVERHAUL. The total man-hours, in hours and tenths, it took to repair/overhaul, or rebuild the item (see Time Conversion chart, table 1-12 , at the end of chapter 1 or the backside of DA Form 2408). The unit of measure for the property is: ManHour

NHA_cumulative_counts_hours(urn:plcs:rdl:pam738_751:NHA_cumulative_counts_hours)

DAFrom block: 25 NHA CUMULATIVE COUNTS/HOURS. DAFrom block: 55 NHA CUMULATIVE COUNTS/HOURS. The total cumulative counts and hours since new for the next higher assembly from which the item was removed. The unit of measure for the property is: OperatingHour

NHA_operating_hours(urn:plcs:rdl:pam738_751:NHA_operating_hours)

DAFrom block: 24 HOURS (NHA). The current aircraft hours, to the nearest hour, if the next higher assembly is an aircraft. If the next higher assembly is a component, enter the components operating hours since new. The unit of measure for the property is: OperatingHour

NSN_code(urn:plcs:rdl:std:NSN_code)

A NSN_code is a NATO_code that identifies the items of supply.

Number_previous_overhauls(urn:plcs:rdl:pam738_751:Number_previous_overhauls)

DAFrom block: 6 NO. OF PREV O/Hs. The number of times that the item has been overhauled. If the item has never been overhauled, enter "0." For Retirement Life Components/Modules and Condition Components/Modules enter "RC" or "CC" in this block. The unit of measure for the property is: Count

Number_starts_since_new