Issue raised against: 2410_form

Comment: (Peter Bergström 2006-02-08)
This change has not yet been implemented in template assigning_person_in_organization. There is an issue against the capability.

Comment: (Peter Bergström 2006-05-17)
The change in template "assigning_person_in_organization" has been executed. The business DEX needs to be changed now.

Comment: (Rob Bodington 06-02-06)
A short term solution is to map it to an assesed stated

Comment: (Peter Bergstrom 2006-02-08)
quick fix:
It has been mapped as a classification of the observed state instead (template #5, fig 13). This is however not the optimal solution. It is classified as state_context, which is a subtype of Applied_state_assignment, which it is not. Since the when_discovered_code is conceptually an 'activity involving the aircraft', it would be more logical to represent it as an Activity_actual classified by the code. It would be assigned to the aircraft (Product_as_realized) through an Applied_activity_assignment, classified as 'Product_usage'.

Comment: (Rob Bodington 06-02-09)
The work around is to use the date associated with the activity_actual to indicate the date on which a component was installed or removed. It is then the responsibility of the receiving system to update the effectivities of the product structure.

Comment: (Rob Bodington 05-10-01)
I think that classifying the Applied_activity_assignment is best. The Product_as_individual is only a reportable item in the context of the DA form.

Comment: (Rob Bodington 05-11-05)
classified the Applied_activity_assignment

"Figure 11 - EXPRESS-G diagram for identifying reportable item"
Add Part_version to record the "Software version" from 2410 block Add assigning_code to product_as_individual to represent the WUC code in block 14 on 2410

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).

"Figure 14 - EXPRESS-G diagram for position on aircraft"

Add assigning_code to Next_assembly_usage to represent the Position in Aircraft

Comment: (Rob Bodington 05-11-05)
Used location_indicator attribute instead

Figure 16 - An EXPRESS-G representation of the Information model for assigning_assessed_state

Make assigning dates and person optional and add them to the characterization section of the template. Add all the arguments for assigning_reference_data Do the same for all associated diagrams and update path and parameters accordingly.

Figure 20 - An EXPRESS-G representation of the Information model for assigning_asserted_state

Make assigning dates and person optional and add them to the characterization section of the template. Add all the arguments for assigning_reference_data Do the same for all associated diagrams and update path and parameters accordingly.

"Figure 22 - Entities instantiated by assigning_asserted_state template"

Instance #217 is in yellow - change to white.

Figure 10 EXPRESS-G diagram for recording a form Figure 11 EXPRESS-G diagram for identifying reportable item

Remove the template "assigning_activity" and use the entity Applied_activity_assignment and reference data.

Where the assigning_activity is pointing at assets that are used as resources, e.g. spares that have been replaced during an activity, use Resource_as_realized_assignment

Develop a Resource_as_realized_assignment template. Draw an EXPRESS-G to show this. Corresponds to "Figure 3-16. Sample of a completed DA Form 2410 for normal removal, evacuation, repair, and installation cycle (Repair/Overhaul)" in 738_751

Remove the template "Assigning_resource_property"

Fig 40, 44, 48, 52, 56

Make assigning dates and person optional Make the assiging_reference_data optional for Numerical_representation_context Add them to the characterization section of the template. Add all the date_ecl_id RDL Remove the whitespace from the arguments Do the same for all associated diagrams and update path and parameters accordingly.

Delete the property_value_string template

Template: representing_quantity

This represents a numerical count, e.g. 10 of, 10 bolts. It does not represent Rename to representing_count

a more generic approach may be more apporpriate. I.e. pass in the SI unit flag as an argument to representing_quantity. Make the reference data generic - i.e. don't tie it to the class "Quantity" Create a new template to representing_count that just uses representing_quantity. This one uses the class "Count" (renamed from Quantity).

Fig 64

Make ALL approval dates optional

Make all assining_ref_data that currently has arguments optional except the ref data for approval_status. This should be passed as a parameter, not hard_coded to "Approved"

remove the "legal_requirement" reference data class

Add a role attribute to approval_assignment set to /IGNORE

Change assigning_classified_identification to assigning_identification_with_no_organization

A person needs an identification - this should be assigned as an external template

A person needs an address assignment - this should be assigned as an external template. Probably using aaddress_based_location

Comment: (Peter Bergstrom 2006-02-08)
The Activity_method have been fully represented with attributes etc in Fig 10, and a new paragraph of text is added above the figure to explain the use of it. Its name attribute has been set to "PAM738_751_method" rather than through a classification of "Normal process".
Maybe the name (and purpose) attributes should be set to /IGNORE, and use a classification instead?

Comment: (Rob Bodington 06-02-09)
As PLCS actively discourages the use of attributes in this way, it would be better to classify the Activity_method as "PAM738_751_method".

Comment: (Peter Bergstrom 2006-02-10)
All attributes set to /IGNORE. Template assigning_reference_data used for Name and Purpose of Activity_method (#17 and #18).
New reference data class 'Aviation_Maintenance' created for the Activity_method's purpose.

Comment: (Peter Bergstrom 2006-02-08)
fixed

Comment: (Rob Bodington 06-02-08)
Added DA2410Form-Installation to RDL

Comment: (Peter Bergstrom 2006-02-08)
Installation activity added under section 'Activity record'.

Comment: (Peter Bergstrom 2006-02-08)
Figure 9 is also introducing a new (?) activity called 'Inspection', but there is no mentioning of that before. I recommend deletion of this item.

Comment: (Rob Bodington 06-02-09)
OK

Comment: (Peter Bergstrom 2006-02-08)
What about Serviceable to Unserviceable? Shouldn't we add that in Figure 9 as well?

Comment: (Rob Bodington 06-02-09)
DA2410Form-Unservicable" covers Serviceable to Unserviceable? Perhaps "DA2410Form-Servicability_change" would be better.

Comment: (Peter Bergstrom 2006-02-08)
Equally, there is no mentioning in Fig 9 about the PN, SN, and NSN change. Should we add this?

Comment: (Rob Bodington 06-02-09)
Yes - a change to the PN, SN and NSN implies a change to the interchangability (ICY), so should be a "DA2410Form-interchangebility".

Comment: (Peter Bergstrom 2006-02-10)
Changed "DA2410Form-Unservicable" to "DA2410Form-Servicability_change" in RDL and fig 10.
Added "DA2410Form-Fit_form_function_change" in RDL and fig 10.
Added "DA2410Form-Controlled_exchange" in RDL and fig 10.
Deleted "DA2410Form-Inspection" in fig 10.

Comment: (Rob Bodington 06-02-09)
Heading changed

Comment: (Rob Bodington 06-02-09)
Addressed.

Comment: (Rob Bodington 06-02-09)
The assigning_location has now been developed, so this should be referenced.

Comment: (Peter Bergstrom 2006-02-10)
Fixed.

Comment: (Rob Bodington 06-02-09)
Updated.