PLM_Data_Exchange_Specification_12-A10DOC-002_Appendix_Table_Fv0.5.xlsx

A-10 Teamcenter Product Lifecycle Management

Desktop Instructions

Specification

Rev F 13 Nov 2015

12-A10DOC-002

A-10 Product Lifecycle Management (PLM)

Data Exchange Specification

Content Owner:

A-10 System Program Office, Hill AFB, Ogden, UT

Table of Contents

1 DOCUMENT OVERVIEW

1.1 PURPOSE OF THIS DOCUMENT

1.2 SCOPE OF THIS DOCUMENT

1.3 TDP CONTENT

1.3.1 TDP Naming

1.3.2 TDP Content Purposes

1.4 TDP CONTENT SUBMISSION

1.5 USE OF CONTRACT NUMBERS IN TDPS

2 TDP SPECIFICATIONS

2.1 NX TDP

2.1.1 NX TDP File Specifications

2.1.2 NX TDP Definitions

2.2 ASIP TDP

2.2.1 ASIP TDP File Specifications

2.3 MRO TDP

2.3.1 MRO TDP File Specifications

2.4 PROGRAM DOCUMENTS TDP

2.4.1 Program Documents TDP File Specifications

3 APPENDIX – DATA DETAILS TABLES

3.1 ATTRIBUTES

3.2 RESTRICTIONS

3.3 VALUES

3.4 DATA HOME

3.4.1 Folder Reference IDs

4 REVISION HISTORY

1 Document Overview

1.1 Purpose of this Document

This document specifies the data format requirements for a Product Lifecycle Management (PLM) Technical Data Package (TDP).

1.2 Scope of this Document

The specifications in this document are limited to data that will be imported into Teamcenter.

A TDP must be one of the following types. This document is organized in sections that correspond to these TDP types.

1. NX – Contains NX Subassemblies and their Components, NX Stand-alone Parts, NX Drawing Assemblies, Engineering Documents. This TDP is used to transfer data from the Contractor to the Air Force.

2. ASIP – Contains Aircraft Structural Integrity Program (ASIP) Data. This TDP is used to transfer data from the Contractor to the Air Force.

3. Maintenance, Repair, & Operations (MRO) Data. This TDP is used to transfer data from the Contractor to the Air Force.

4. Program Documents – Contains Program Documents. This TDP is used to transfer data from the Contractor to the Air Force.

1.3 TDP Content

1.3.1 TDP Naming

1.3.2 TDP Content Purposes

A TDP may include a PLMXML file, a Clone file, and a folder containing the files to be imported.

The PLMXML file is used to:

import Items, Revisions, Forms, & Datasets assign Items, Revisions, Forms, & Datasets attribute values import files into Datasets relate Datasets to Item Revisions relate Items, Item Revisions, Forms, & Datasets relate Item Revisions to the Contract assign Item Revisions and Datasets a Release Status assign Items, Item Revisions, Forms, & Datasets to an Owning Organization & User

Compressed (i.e. ZIP) file

TDP Folder

PLMXML File

File Folder

Clone File

TDP Name Format:

Contract Number (provided at Contract kickoff) underscore Date (in ISO 8601 format) underscore Identifying Number (e.g., Component or Document Number) underscore Numeric TDP Type (see below)

Numeric TDP Type:

1 = NX

2 = ASIP

3 = MRO

4 = Program Documents

The Clone file is used to:

import the assembly structure, including the structure between a drawing and the parts detailed on the drawing import new Item Revisions & Datasets and to specify their ID, revision, name, & description indicate that the import should reference previously imported Item Revisions rather than re‐ importing them assign Items, Item Revisions, Forms, & Datasets to an Owning Organization & User

The file folder is used to:

contain the files to be imported

1.4 TDP Content Submission

A TDP must be submitted in the format described in this specification. A TDP must be submitted in accordance with the procedures described in the Contract.

1.5 Use of Contract Numbers in TDPs

At the Contract Kickoff, the Air Force will provide the Contract Item ID and Revision to be used in the PLMXML files.

2 TDP Specifications

2.1 NX TDP

2.1.1 NX TDP File Specifications

NX files with a .prt extension (within a folder), Engineering Documents (within the same folder as the NX files), a Clone file, and a PLMXML file are allowed within the NX TDP. No other types of files or folders are allowed.

2.1.1.1 NX File Specifications

The TDP’s NX files must fully load into native NX without any warnings or errors.

The TDP’s NX files must be saved with their NX WAVE links broken or frozen as specified in the

3D Modeling Specification.

The TDP’s NX files, generated from Part Families, must be saved with all part family links broken.

The TDP’s file’s filenaming requirements are defined in the Filename Property in Section 3, Appendix – Data Details Tables.

2.1.1.2 Engineering Document File Specifications

The TDP’s Engineering Document file’s filenames are defined in the Filename Property in Section

3, Appendix – Data Details Tables.

2.1.1.3 Clone File Specifications

The TDP’s Clone file may not include multiple revisions of a single part. NX import utilities are not designed to handle this situation.

The TDP’s NX drawing files are normally included within the same Clone file as its children (the

NX files that the drawing details).

o Note: In the case where a drawing file is to be submitted without its children, care must be taken when building the Clone file interactively in NX using the interactive command:

Export Assembly Outside Teamcenter… Take care to add the drawing to the Clone file using the ‘Add Part’ command (which adds the part without its children) instead of ‘Add

Assembly’ command (which adds it and its children).

The following specifications define the Clone entries that are required in the Clone file. The Clone file must contain only the entries specified in this document. No other entries are allowed. Note that the Clone entry syntax is case sensitive.

The Clone file must begin by identifying the top-level NX Subassembly(s), NX Drawing Assembly(s), and NX Stand-alone Parts that must be selected to import. (Note that the term 'top-level' refers to the top of an assembly included within the TDP and not the top of a contract deliverable assembly; refer to 2.1.2 NX TDP Defintions.

Several top-level assemblies may be submitted within a TDP). They are listed in sections at the beginning of the file as shown below:

List of the top-level NX Subassembly(s) in this Clone file:

160D611201-3 List of the NX Drawing Assembly(s) in this Clone file:

160D611201-3_DWG

List of the NX Stand-alone Parts in this Clone file:

160D611201-103

The List of top-level NX Subassembly(s) in this Clone file includes the part number(s) of the top-level subassembly(s) that must be selected to import.

The List of NX Drawing Assembly(s) in this Clone file includes the part number(s) of the drawing(s) that must be selected to import.

The List of NX Stand-alone Parts in this Clone file includes the part number(s) of the part(s) outside of the top-level subassembly(s) (if any) that must be selected to import.

Each Clone file must include the following set of entries at the beginning of the file (following the lists of NX Subassembly(s), NX Drawing Assemblies, and NX Stand-alone Parts).

Assembly Cloning Log File &LOG Operation_Type: IMPORT_OPERATION &LOG Default_Cloning_Action: OVERWRITE &LOG Default_Naming_Technique: AUTO_TRANSLATE &LOG Default_Copy_Associated_Files: No &LOG Default_Validation_Mode: OFF

&LOG

Each NX Part Revision must be represented in the Clone file by the following set of entries. CAUTION: If a space or a period is used in any value then the value must be entered inside a double quotation mark (e.g., "FORWARD SPAR" or "123.prt"). Null values are indicated by a two consecutive double quotation marks (e.g., &LOG Part_Description: "").

&LOG Part:"160D123456-01_01.prt"

&LOG Cloning_Action:DEFAULT_DISP Naming_Technique: USER_NAME Clone_Name: "@DB/160D123456-01/01"

&LOG Part_Name:"ROCKER MOUNT SUB"

&LOG Part_Description:"ROCKER ARM SHAFT, HIGH TORQUE"

&LOG DB_Owner:"northrop.grumman" "Structural.A10SPO"

&LOG Part_Type:Assembly &LOG Container: Newstuff

&LOG

The &LOG Part entry is defined in the Filename Property in Section 3, Appendix – Data Details Tables.

The &LOG Cloning_Action entry is defined in the Cloning_Action Property in Section 3, Appendix – Data Details Tables.

The Clone_Name entries are defined in the ID & Revision Properties in Section 3, Appendix – Data Details Tables.

&LOG Part_Name entry is defined in the Name (Item) Property in Section 3, Appendix – Data Details Tables.

&LOG Part_ Description entry is defined in the Description Property in Section 3, Appendix – Data Details Tables.

&LOG DB_Owner entries are defined in the Owning User and Discipline Properties in Section 3, Appendix – Data Details Tables.

&LOG Part_Type entry is defined in the Type (Item) in Section 3, Appendix – Data Details Tables.

2.1.1.4 NX TDP PLMXML File Specifications

The following specifications define the PLMXML elements and attributes that are required in the PLMXML file.

The PLMXML file must contain only the elements and attributes specified in this document. No other elements or attributes are allowed. Note that the PLMXML element and attribute syntax is case sensitive.

The PLMXML file and its elements and their attributes must conform to PLMXML standard convention.

The PLMXML file and its elements and their attributes must conform to XML standard convention. For example:

All elements (except the ?xml, ?xml‐stylesheet, PLMXL, AssociatedDataSet, AssociatedForm, Description, UserData, and UserValue elements) must be assigned an "id" attribute that is unique in the PLMXML file.

When an element references other elements, the reference is made by referencing the target element’s "id" attribute.

XML element’s attribute values must not include the five "predefined entities" (Wikipedia).

These "predefined entitites" must be escaped as shown in the Escape Method column in the following table.

Name Character Escape Method Standard Description quot " &quot; XML 1.0 double quotation mark amp & &amp; XML 1.0 ampersand apos ' &apos; XML 1.0 apostrophe (apostrophe-quote) lt < &lt; XML 1.0 less-than sign gt > &gt; XML 1.0 greater-than sign

When referencing an element, the element’s "id" must be prefaced with "#id".

Every element must be described using opening and closing tags.

The PLMXML file and its elements and their attributes must conform to the following A-10-specific conventions:

1. The PLMXML file must not include two Product elements with the same productID attribute value.

2. The PLMXML file must not include a Product element without a ProductRevision element referencing it.

3. The PLMXML file must not include Product elements that do not have corresponding NX Parts in the Clone file.

4. The PLMXML file must not include two Form elements with the same Name attribute value.

5. The PLMXML file must not include two Organization elements with the same Name attribute value.

6. The PLMXML file must only reference files that are included in the TDP’s file folder.

7. The PLMXML file must only include ProductRevision elements that reference a Dataset.

8. The PLMXML file must not reference any NX Datasets that are not defined in the Clone file.

9. The PLMXML file must not include two ReleaseStatus elements with the same Name attribute value (except in the case of differing release dates and/or differing effectivity).

10. The PLMXML file may include previously submitted Item Revisions. Resubmittal, in separate

TDP’s, is allowed but they must have the exact element attribute values (as in the previous submittal) since each import will overwrite the previously imported element’s attribute values, unless of course, the intent is to correct attribute values.

11. The PLMXML file must not assign a Release Status to a Contract revision.

12. The PLMXML file must only include Datasets that reference a ProductRevision.

13. The PLMXML file must only include Forms that that reference a ProductRevision.

14. The PLMXML file must only include Item Revisions with Types that match the Clone file.

15. The PLMXML file must only include Item Revisions matching the Types specified in the GFI, where provided.

16. The PLMXML file must only include Item Revisions with Types of the same Type as previously submitted revisions for the same part.

The PLMXML file must begin with the following:

<?xml version="1.0" encoding="utf-8" ?> <?xml-stylesheet type="text/xsl" href="PLMXMLviewHTML3.1.xsl"?> <PLMXML xmlns="http://www.plmxml.org/Schemas/PLMXMLSchema" schemaVersion="6"> <Header id="id1" traverseRootRefs="#id28 #id101 #id115" />

The traverseRootRefs maintains a reference to each ProductRevision, primary Occurrence, and GeneralRelation element.

The PLMXML file must include a Product and ProductRevision element (with their attributes) for the Contract revision:

<Product id="id25" productId="FA8635-07-D-6000-A002" name="FA8635-07-D-6000-A002" subType="BB4Document"/> <ProductRevision id="id26" masterRef="#id25" name="FA8635-07-D-6000-A002" subType="BB4Document

Revision" revision="C">

The Product’s productId attribute must be the Contract Number (the format is to be specified at the Contract Kickoff meeting).

The Product’s name attribute must match the productId value.

The ProductRevision’s name attribute must match the productId value.

The ProductRevision’s revision attribute must be the Contract Revision (the revision is to be specified at the Contract Kickoff meeting).

The PLMXML file must include Product elements (with attributes and subelements) for each Item:

<Product id="id27" productId="160D123456-01" name="ROCKER MOUNT SUB" subType="Assembly">

<Description>ROCKER ARM SHAFT, HIGH TORQUE</Description> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> <UserValue type="boolean" value="Y" title="is_configuration_item" />

</UserData> </Product>

The Product’s productId attribute is defined in the ID Property in Section 3, Appendix – Data Details Tables.

The Product’s name attribute is defined in the Name (Item) Property in Section 3, Appendix – Data Details Tables.

The Product’s subType attribute is defined in the Type (Item) Property in Section 3, Appendix – Data Details Tables.

The Product’s Description subelement is defined in the Description Property in Section 3, Appendix – Data Details Tables.

Only when the Item is a Configuration Item, should the UserValue element be included in the PLMXML file.

Otherwise the entire UserValue element should be left out of the PLMXML file. Each Product element’s UserData/UserValue subelements must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: data are case sensitive).

The PLMXML file must include ProductRevision, DataSet, and Form elements (with their attributes and subelements) for each Item Revision (NOTE: not all attributes shown in the example apply to all Item Types):

<ProductRevision id="id28" masterRef="#id27" name="ROCKER MOUNT SUB" subType="Assembly

Revision" revision="01" releaseStatusRefs="#id50"> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData> <AssociatedDataSet id="id29" dataSetRef="#id30" role="IMAN_specification" /> <AssociatedDataSet id="id33" dataSetRef="#id34" role="IMAN_specification" /> <AssociatedForm formRef="#id31" role="IMAN_master_form_rev" />

</ProductRevision> <DataSet id="id30" name="160D123456-01/01" type="PDF" memberRefs="#id42" releaseStatusRefs="#id50">

<UserData> <UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" />

</UserData> <UserData type="Attributes">

<UserValue value="Proprietary" title="ip_classification" /> </UserData>

</DataSet> <ExternalFile id="id42" locationRef="SA_160D123456-01ABC.pdf" format="pdf" />

<Form id="id31" name="160D123456-01/01" subType="Assembly Revision Master"> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData>

<UserData type="FormAttributes"> <UserValue value="some attribute value" title="some attribute title" />

</UserData> </Form>

The ProductRevision’s name attribute is defined in the Name (Item) Property in Section 3, Appendix – Data Details Tables.

The ProductRevision’s subType attribute is defined in the Type (Revision) Property in Section 3, Appendix – Data Details Tables.

The ProductRevision’s revision attribute is defined in the Revision Property in Section 3, Appendix – Data Details Tables.

The Dataset’s type attribute is defined in the Type (Dataset) Property in Section 3, Appendix – Data Details Tables X.

Only with written permission from the A-10 Program Office, can the DataSet subelement UserData, with the "Attributes" type be used (which marks the Datast proprietary)).

The ProductRevision’s locationRef attribute and corresponding ExternalFile element must not be included for NX parts.

The ExternalFile’s locationRef attribute is defined in the Filename Property in Section 3, Appendix – Data Details Tables.

Each Form element’s subType attribute is a combination of the ProductRevisions’s subType attribute value and the word "Master", separated by a space.

Each Form element’s UserData/UserValue subelements must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: attribute values are case sensitive).

The PLMXML file must include Folder elements (with attributes and subelements) to relate Items and/or Item Revisions to their "home" folder:

<Folder id="id838" name="Aircraft Production Drawings" subType="Folder" folderContentRefs="#id28">

<ApplicationRef version="AdSJsxWT4dnW_A" application="Teamcenter" label="AdSJsxWT4dnW_A"></ApplicationRef></Folder>

The Folder’s name attribute is defined in Section 3, Appendix – Data Details Tables. It must match the value in the Governance Property.

The Folder’s folderContentRefs attribute must include the id’s of Item and/or Item Revision elements and must link to a folder to match the value in the Governance Property.

The Folder’s ApplicationRef version attribute must be selected from Section 3, Appendix – Data Details Tables.

The Folder’s ApplicationRef label attribute must be selected from Section 3, Appendix – Data Details Tables.

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each Item Revision to relate it to the Contract revision:

<GeneralRelation id="id115" subType="IMAN_reference" relatedRefs="#id26 #id28" />

The first relatedRefs id is the id of the Contract’s ProductRevision element.

The second relatedRefs id is the id of the ProductRevision element.

The PLMXML file must include ProductDef and ProductView elements (with attributes and subelements) for each Note to link it to an Item Revison:

<ProductDef id="id134">

<InstanceGraph id="id135"> <ProductInstance id="id110" partRef="#id111"/>

<ProductRevisionView id="id111" revisionRef="#id28"/> </InstanceGraph> </ProductDef > <ProductView id="id133" rootRefs="id101" subType="List" primaryOccurrenceRef="id101"> < UserData type="TC Specific Properties"> < UserValue value="imprecise" title="BOM_precision_type" />

</UserData> <Occurrence id="id101" instancedRef="#id28" occurrenceRefs="id102" />

<Occurrence id="id102" instancedRef="#id55" instanceRefs="#id110"> <UserData type="AttributesInContext">

<UserValue value="1" title="Quantity" /> </UserData>

</Occurrence> </ProductView>

The ProductInstance element's partRef attribute must match the corresponding ProductRevisionView element's id.

The ProductRevisionView element's revisionRef attribute must match the ProductRevision for the Part, Assembly or Drawing to which the Note is linked.

The ProductView element's rootRef attribute must match the Occurrence for the Part, Assembly or Drawing Revision to which the Note is linked.

The ProductView element's primaryOccurrenceRef attribute must match the Occurrence for the Note.

The first Occurrence element's instancedRef (note the name includes a 'd') attribute must match the Part, Assembly or Drawing Revision to which the Note is linked.

The Occurrence element's occurrenceRef attribute must match the Occurrence for the Note.

The second Occurrence element's instancedRef (note the name includes a 'd') attribute must reference the Note Revision.

The Occurrence element's instanceRef (note the name does not include a 'd') attribute must match the Part, Assembly or Drawing Revision's ProductInstance element.

The PLMXML file must include an Organisation, User, and Person element. The elements must include the following:

<Organisation id="id1500" name="Mechanical.A10SPO" />

<User id="id2000" userId="northrop.grumman" personRef="#id2001" /> <Person id="id2001" lastName="data.manager" />

The name attribute is defined in the Owning Group Property in Section 3, Appendix – Data Details Tables.

The userID attribute is defined in the Discipline in Section 3, Appendix – Data Details Tables.

The PLMXML file must include ReleaseStatus elements (with attributes and subelements). The ReleaseStatus elements must include the following:

<ReleaseStatus id="id50" name="Final" dateReleased="2012-02-10T10:10:10"/>

<UserData> <UserValue value="Final 75-UP (A-10C)" title="effectivity_text"></UserValue>

The ReleaseStatus element’s name attribute is defined in the Status Property in Section 3, Appendix – Data

The value in the ReleaseStatus’ dateReleased attribute on revisions of an Item must never be the same. The dateReleased attribute on revisions of an Item must accurately represent the date the revisions were released. If they were released on the same day, the time must vary.

The ReleaseStatus element’s effectivity attribute is defined in the Effectivity Property in Section 3, Appendix –

The PLMXML file must end with the following:

</PLMXML>

2.1.2 NX TDP Definitions

2.2 ASIP TDP

2.2.1 ASIP TDP File Specifications

ASIP files (within a folder) and a PLMXML file are allowed within the ASIP TDP. No other types of files are allowed.

2.2.1.1 ASIP File Specifications

2.2.1.2 ASIP PLMXML File Specifications

The following specifications define the PLMXML elements and attributes that are required in the PLMXML file.

The PLMXML file must contain only the elements and attributes specified in this document. No other elements or attributes are allowed. Note that the PLMXML element and attribute syntax is case sensitive.

The PLMXML file and its elements and their attributes must conform to XML standard convention. For example:

unique in the PLMXML file.

When an element references other elements, the reference is made by referencing the target element’s "id" attribute.

XML element’s attribute values must not include the five "predefined entities" (Wikipedia).

amp & &amp; XML 1.0 ampersand apos ‘ &apos; XML 1.0 apostrophe (apostrophe-quote)

The PLMXML file and its elements and their attributes must conform to the following A-10-specific conventions:

3. The PLMXML file may include multiple ProductRevision elements for the same Product element.

4. The PLMXML file must not include two Form elements with the same Name attribute value.

5. The PLMXML file must not include two Organization elements with the same Name attribute value.

6. The PLMXML file must only reference files that are included in the TDP’s file folder.

7. The PLMXML file may include ProductRevision elements that do not reference a Dataset.

8. The PLMXML file must not include two ReleaseStatus elements with the same Name attribute value (except in the case of differing release dates and/or differing effectivity).

9. The PLMXML file may include previously submitted Item Revisions. Resubmittal, in separate

TDP’s, is allowed but they must have the exact element attribute values (as in the previous submittal) since each import will overwrite the previously imported element’s attribute values, unless of course, the intent is to correct attribute values.

10. The PLMXML file must not assign a Release Status to a Contract revision.

11. The PLMXML file must only include Datasets that reference a ProductRevision.

12. The PLMXML file must only include Forms that reference a ProductRevision.

13. The PLMXML file must only include Item Revisions matching the Types specified in the GFI, where provided.

14. The PLMXML file must only include Item Revisions with Types of the same Type as previously submitted revisions for the same Item.

15. The PLMXML file must not create any NX Datasets.

<?xml-stylesheet type="text/xsl" href="PLMXMLviewHTML3.1.xsl"?>

<Header id="id1" traverseRootRefs="#id28 #101 #id115" />

The traverseRootRefs maintains a reference to each ProductRevision, primary Occurrence, and GeneralRelation element.

The PLMXML file must include a Product and ProductRevision element (with their attributes) for the Contract

The Product’s productId attribute must be the Contract Number (the format is to be specified at the Contract

The ProductRevision’s revision attribute must be the Contract Revision (the revision is to be specified at the

<Product id="id27" productId="160D123456-01" name="ROCKER MOUNT SUB" subType="BB4Document">

<UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> <UserValue type="boolean" value="Y" title="is_configuration_item" />

</UserData> </Product>

The Product’s productId attribute is defined in the ID Property in Section 3, Appendix – Data Details Tables.

The Product’s name attribute is defined in the Name (Item) Property in Section 3, Appendix – Data Details Tables.

The Product’s subType attribute is defined in the Type (Item) Property in Section 3, Appendix – Data Details Tables.

The Product’s Description subelement is defined in the Description Property in Section 3, Appendix – Data Details Tables.

Only when the Item is a Configuration Item, should the UserValue element be included in the PLMXML file.

Otherwise the entire UserValue element should be left out of the PLMXML file. Each Product element’s UserData/UserValue subelements must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: data are case sensitive).

subelements) for each Item Revision (NOTE: not all attributes shown in the example apply to all Item Types):

<ProductRevision id="id28" masterRef="#id27" name="ROCKER MOUNT SUB" subType="BB4Document

Revision" revision="01" releaseStatusRefs="#id50"> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData> <AssociatedDataSet id="id29" dataSetRef="#id30" role="IMAN_specification" /> <AssociatedDataSet id="id33" dataSetRef="#id34" role="IMAN_specification" /> <AssociatedForm formRef="#id31" role="IMAN_master_form_rev" />

</ProductRevision> <DataSet id="id30" name="160D123456-01/01" type="PDF" memberRefs="#id42" releaseStatusRefs="#id50">

<UserData> <UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" />

</UserData> <UserData type="Attributes">

<UserValue value="Proprietary" title="ip_classification" /> </UserData>

</DataSet> <ExternalFile id="id42" locationRef="SA_160D123456-01ABC.pdf" format="pdf" />

<Form id="id31" name="160D123456-01/A01" subType="BB4Document Revision Master">

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData>

<UserData type="FormAttributes"> <UserValue value="some attribute value" title="some attribute title" />

The ProductRevision’s name attribute is defined in the Name (Item) Property in Section 3, Appendix – Data

The ProductRevision’s subType attribute is defined in the Type (Revision) Property in Section 3, Appendix – Data Details Tables.

The ProductRevision’s revision attribute is defined in the Revision Property in Section 3, Appendix – Data Details Tables.

Only when a Dataset is to be imported, should the Dataset element (and subelements) be included in the PLMXML file. Otherwise the entire Dataset element should be left out of the PLMXML file. The Dataset’s type attribute is defined in the Type (Dataset) Property in Section 3, Appendix – Data Details Tables X.

Only with written permission from the A-10 Program Office, can the DataSet subelement UserData, with the "Attributes" type be used (which marks the Datast proprietary)).

The ProductRevision’s locationRef attribute and corresponding ExternalFile element must not be included for NX parts.

The ExternalFile’s locationRef attribute is defined in the Filename Property in Section 3, Appendix – Data Details Tables.

Each Form element’s subType attribute is a combination of the ProductRevisions’s subType attribute value and the word "Master", separated by a space.

Only when the ProductRevision is to be imported (and not just referenced), should the Form element (and subelements) be included in the PLMXML file. Otherwise the entire Form element should be left out of the PLMXML file. Each Form element’s UserData/UserValue subelements must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: attribute values are case sensitive).

The PLMXML file must include Folder elements (with attributes and subelements) to relate Items and/or Item

<Folder id="id838" name="Aircraft Production Drawings" subType="Folder" folderContentRefs="#id839 #id841 #id843 #id865 #id867">

The Folder’s name attribute is defined in Section 3, Appendix – Data Details Tables. It must match the value in

The Folder’s folderContentRefs attribute must include the id’s of Item and/or Item Revision elements and must link to a folder to match the value in the Governance Property.

The Folder’s ApplicationRef version attribute must be selected from Section 3, Appendix – Data Details Tables.

The Folder’s ApplicationRef label attribute must be selected from Section 3, Appendix – Data Details Tables.

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each Item

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each Item or Item Revision to be related to another Item or Item Revison:

The subtype a must be a Relation Property selected from Section 3, Appendix – Data Details Tables.

The first relatedRefs id is the id of the Item or Item Revision’s ProductRevision element.

The second relatedRefs id is the id of the linked Item or Item Revision’s ProductRevision element.

The PLMXML file must include ProductDef and ProductView elements (with attributes and subelements) for each Note to link it to an Item Revison:

<ProductDef id="id134">

<InstanceGraph id="id135"> <ProductInstance id="id110" partRef="#id111"/>

<ProductRevisionView id="id111" revisionRef="#id28"/> </InstanceGraph> </ProductDef > <ProductView id="id133" rootRefs="id101" subType="List" primaryOccurrenceRef="id101"> < UserData type="TC Specific Properties"> < UserValue value="imprecise" title="BOM_precision_type" />

</UserData> <Occurrence id="id101" instancedRef="#id28" occurrenceRefs="id102" />

<Occurrence id="id102" instancedRef="#id55" instanceRefs="#id110"> <UserData type="AttributesInContext">

<UserValue value="1" title="Quantity" /> </UserData>

The ProductInstance element's partRef attribute must match the corresponding ProductRevisionView element's id.

The ProductRevisionView element's revisionRef attribute must match the ProductRevision for the Part, Assembly or Drawing to which the Note is linked.

The ProductView element's rootRef attribute must match the Occurrence for the Part, Assembly or Drawing Revision to which the Note is linked.

The ProductView element's primaryOccurrenceRef attribute must match the Occurrence for the Note.

The first Occurrence element's instancedRef (note the name includes a 'd') attribute must match the Part, Assembly or Drawing Revision to which the Note is linked.

The Occurrence element's occurrenceRef attribute must match the Occurrence for the Note.

The second Occurrence element's instancedRef (note the name includes a 'd') attribute must reference the Note Revision.

The Occurrence element's instanceRef (note the name does not include a 'd') attribute must match the Part, Assembly or Drawing Revision's ProductInstance element.

The PLMXML file must include an Organisation, User, and Person element. The elements must include the

The name attribute is defined in the Owning Group Property in Section 3, Appendix – Data Details Tables.

The PLMXML file must include ReleaseStatus elements (with attributes and subelements). The ReleaseStatus elements must include the following:

<ReleaseStatus id="id50" name="Final" dateReleased="2012-02-10T10:10:10"/>

<UserData> <UserValue value="Final 75-UP (A-10C)" title="effectivity_text"></UserValue>

The ReleaseStatus element’s name attribute is defined in the Status Property in Section 3, Appendix – Data

The value in the ReleaseStatus’ dateReleased attribute on revisions of an Item must never be the same. The dateReleased attribute on revisions of an Item must accurately represent the date the revisions were released. If they were released on the same day, the time must vary.

The ReleaseStatus element’s effectivity attribute is defined in the Effectivity Property in Section 3, Appendix –

2.3 MRO TDP

2.3.1 MRO TDP File Specifications

MRO files (within a folder) and a PLMXML file are allowed within the MRO TDP. No other types of files are allowed.

2.3.1.1 MRO File Specifications

2.3.1.2 MRO PLMXML File Specifications

The following specifications define the PLMXML elements and attributes that are required in the PLMXML file.

The PLMXML file must contain only the elements and attributes specified in this document. No other elements or attributes are allowed. Note that the PLMXML element and attribute syntax is case sensitive.

The PLMXML file and its elements and their attributes must conform to XML standard convention. For example:

unique in the PLMXML file.

When an element references other elements, the reference is made by referencing the target element’s "id" attribute.

XML element’s attribute values must not include the five "predefined entities" (Wikipedia).

amp & &amp; XML 1.0 ampersand apos ‘ &apos; XML 1.0 apostrophe (apostrophe-quote)

The PLMXML file and its elements and their attributes must conform to the following A-10-specific conventions:

3. The PLMXML file may include multiple ProductRevision elements for the same Product element.

4. The PLMXML file must not include two Form elements with the same Name attribute value.

5. The PLMXML file must not include two Organization elements with the same Name attribute value.

6. The PLMXML file must only reference files that are included in the TDP’s file folder.

7. The PLMXML file may include ProductRevision elements that do not reference a Dataset.

8. The PLMXML file must not include two ReleaseStatus elements with the same Name attribute value (except in the case of differing release dates and/or differing effectivity).

9. The PLMXML file may include previously submitted Item Revisions. Resubmittal, in separate

TDP’s, is allowed but they must have the exact element attribute values (as in the previous submittal) since each import will overwrite the previously imported element’s attribute values, unless of course, the intent is to correct attribute values.

10. The PLMXML file must not assign a Release Status to a Contract revision.

11. The PLMXML file must only include Datasets that reference a ProductRevision.

12. The PLMXML file must only include Forms that reference a ProductRevision.

13. The PLMXML file must only include Item Revisions matching the Types specified in the GFI, where provided.

14. The PLMXML file must only include Item Revisions with Types of the same Type as previously submitted revisions for the same Item.

15. The PLMXML file must not create any NX Datasets.

16. The PLMXML file must not include a Product or RealizedProduct element without a

ProductRevision or RealizedProduct (respectively) element referencing it.

<?xml-stylesheet type="text/xsl" href="PLMXMLviewHTML3.1.xsl"?>

<Header id="id1" traverseRootRefs="#id28 #id192 #id92 #101 #id115" />

The traverseRootRefs maintains a reference to each ProductRevision, RealizedProductRevision, primary Occurrence, and GeneralRelation element.

The PLMXML file must include a Product and ProductRevision element (with their attributes) for the Contract revision (which authorizes the import):

22subtype="BB4Document" /> <ProductRevision id="id26" masterRef="#id25" name="FA8635-07-D-6000-A002" subtype="BB4Document

The Product’s productId attribute must be the Contract Number (the number is to be specified at the Contract

The Product’s name attribute must match the productId value.

The ProductRevision’s name attribute must match the productId value.

The ProductRevision’s revision attribute must be the Contract Revision (the revision is to be specified at the Contract Kickoff meeting).

The PLMXML file must include Product elements (with attributes and subelements) for each Item (this section does not apply to Aircraft or Physical Parts):

<Product id="id27" productId="160D123456-01" name="ROCKER MOUNT SUB" subType="Assembly">

<UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" />

</UserData> </Product>

The Product’s productId attribute is defined in the ID Property in Section 3, Appendix – Data Details Tables.

The Product’s name attribute is defined in the Name (Item) Property in Section 3, Appendix – Data Details Tables.

The Product’s subType attribute is defined in the Type (Item) Property in Section 3, Appendix – Data Details Tables.

The Product’s Description subelement is defined in the Description Property in Section 3, Appendix – Data subelements) for each Item Revision (NOTE: not all attributes shown in the example apply to all Item Types):

<ProductRevision id="id28" masterRef="#id27" name="ROCKER MOUNT SUB" subType="Assembly

Revision" revision="01" releaseStatusRefs="#id50"> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData> <AssociatedDataSet id="id29" dataSetRef="#id30" role="IMAN_specification" /> <AssociatedDataSet id="id33" dataSetRef="#id34" role="IMAN_specification" /> <AssociatedForm formRef="#id31" role="IMAN_master_form_rev" />

</ProductRevision> <DataSet id="id30" name="160D123456-01/01" type="PDF" memberRefs="#id42" releaseStatusRefs="#id50">

<UserData> <UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" />

</UserData> <UserData type="Attributes">

<UserValue value="Proprietary" title="ip_classification" /> </UserData>

</DataSet> <ExternalFile id="id42" locationRef="SA_160D123456-01ABC.pdf" format="pdf" />

<Form id="id31" name="160D123456-01/01" subType="Assembly Revision Master">

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData>

<UserData type="FormAttributes"> <UserValue value="some attribute value" title="some attribute title" />

The ProductRevision’s name attribute is defined in the Name (Item) Property in Section 3, Appendix – Data

The ProductRevision’s subType attribute is defined in the Type (Revision) Property in Section 3, Appendix – Data Details Tables.

The ProductRevision’s revision attribute is defined in the Revision Property in Section 3, Appendix – Data Details Tables.

Only when a Dataset is to be imported, should the Dataset element (and subelements) be included in the PLMXML file. The Dataset’s type attribute is defined in the Type (Dataset) Property in Section 3, Appendix – Data Details Tables X.

Only with written permission from the A-10 Program Office, can the DataSet subelement UserData, with the "Attributes" type be used (which marks the Datast proprietary)).

The ProductRevision’s locationRef attribute and corresponding ExternalFile element must not be included for NX parts.

The ExternalFile’s locationRef attribute is defined in the Filename Property in Section 3, Appendix – Data Details Tables.

Each Form element’s subType attribute is a combination of the ProductRevisions’s subType attribute value and the word "Master", separated by a space.

Only when the ProductRevision is to be imported (and not just referenced), should the Form element (and subelements) be included in the PLMXML file. Otherwise the entire Form element should be left out of the PLMXML file. Each Form element’s UserData/UserValue subelements must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: attribute values are case sensitive).

The PLMXML file must include RealizedProduct and Form elements (with their attributes and subelements) for each Aircraft and for each Physical Part:

<RealizedProduct id="id91" productId="Aircraft 569 SN 80-0219" name="Aircraft 569 SN 80-0219" subType="PhysicalPart">

<Description>Aircraft 569 SN 80-0219</Description> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" />

<UserValue value="80-0219" title="serialNumber" /> </UserData>

</RealizedProduct>

The RealizedProduct’s productId attribute is defined in the ID Property in Section 3, Appendix – Data Details Tables.

The RealizedProduct’s name attribute must match the attribute value in the RealizedProduct element’s productId attribute.

The RealizedProduct’s Description subelement is defined in the Description Property in Section 3, Appendix –

Each RealizedProduct element’s UserData/UserValue subelements must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: attribute values are case sensitive).

The PLMXML file must include RealizedProductRevision and Form elements (with their attributes and subelements) for each Aircraft and for each Physical Part:

<RealizedProductRevision id="id92" masterRef="#id91" name="Aircraft 569 SN 80-0219" subType="PhysicalPart Revision" revision="01"> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData> <AssociatedForm formRef="#id93" role="IMAN_master_form_rev" />

</RealizedProductRevision> <Form id="id93" name="Aircraft 569 SN 80-0219/01" subType="PhysicalPart Revision Master">

<UserData> <UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData>

<UserData type="FormAttributes"> <UserValue value="some attribute value" title="some attribute title" />

</UserData> </Form>

The RealizedProductRevision’s name attribute must match the attribute value in the RealizedProduct element’s name attribute.

The RealizedProductRevision’s revision attribute is defined in the Revision Property in Section 3, Appendix – Data Details Tables.

Each Form element’s UserData/UserValue subelement must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: not all attributes shown in the example apply to all Item Types).

The PLMXML file must include Product elements (with their attributes and subelements) for each Event:

<Product id="id191" productId="Aircraft 569 SN 80-0219" name="Aircraft 569 SN 80-0219" subType="AF8Event">

<Description>Aircraft 569 SN 80-0219</Description> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" />

</UserData> </Product>

The Product’s productId attribute is defined in the ID Property in Section 3, Appendix – Data Details Tables.

The Product’s name attribute must match the attribute value in the Product element’s productId attribute.

The ProductRevision’s Description subelement is defined in the Description Property in Section 3, Appendix – Data Details Tables.

The PLMXML file must include ProductRevision and Form elements (with their attributes and subelements) for each Event:

<ProductRevision id="id192" masterRef="#id191" name="Aircraft 569 SN 80-0219" subType="AF8Event

Revision" revision="01"> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData> <AssociatedForm formRef="#id193" role="IMAN_master_form_rev" />

</ProductRevision> <Form id="id193" name="Aircraft 569 SN 80-0219/01" subType="AF8Event Revision Master">

<UserData> <UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData>

<UserData type="FormAttributes"> <UserValue value="some attribute value" title="some attribute title" />

</UserData> </Form>

The ProductRevision’s name attribute must match the attribute value in the Product element’s name attribute.

The ProductRevision’s revision attribute is defined in the Revision Property in Section 3, Appendix – Data Details Tables.

Each Form element’s UserData/UserValue subelement must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: not all attributes shown in the example apply to all Item Types).

The PLMXML file must include Form elements (with attributes and subelements) for each Aircraft’s Quarterly hours Report:

<Form id="id94" name="160D123456-01/A01" subType="AF8QuarterlyHoursForm"> <UserData>

<UserValue type="reference" value="" title="owning_user" dataRef="#id2000" /> <UserValue type="reference" value="" title="owning_group" dataRef="#id1500" /> </UserData>

<UserData type="FormAttributes"> <UserValue value="some attribute value" title="some attribute title" />

</UserData> </Form> The Form name attribute is defined in the Name (Item) Property in Section 3, Appendix – Data Details Tables.

Each Form element’s UserData/UserValue subelement must include titles and values defined in Section 3, Appendix – Data Details Tables. (NOTE: not all attributes shown in the example apply to all Item Types).

The PLMXML file must include Folder elements (with attributes and subelements) to relate Items and/or Item Revision to their "home" folder:

The Folder’s name attribute is defined in Section 3, Appendix – Data Details Tables. It must match the value in

The Folder’s folderContentRefs attribute must include the id’s of Item and/or Item Revision elements and must link to a folder to match the value in the Governance Property.

The Folder’s ApplicationRef version attribute must be selected from Section 3, Appendix – Data Details Table.

The Folder’s ApplicationRef label attribute must be selected from Section 3, Appendix – Data Details Tables.

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each Aircraft Revision, Major Component Revision, Configuration Item Revision, Event Revision, Hours Form to relate them to the Contract revision:

<GeneralRelation id="id115" subType="IMAN_reference" relatedRefs="#id26 #id27" />

The second relatedRefs id is the id of the MRO Data’s Product element.

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each Event to relate them to the Aircraft Revision and the Major Component Revision (or the Configuration Item Revision if applicable):

<GeneralRelation id="id115" subType="af8MROAction" relatedRefs="#id26 #id27" />

The first relatedRefs id is the id of the Aircraft or Major Component's ProductRevision element.

The second relatedRefs id is the id of the Event's Product element.

The PLMXML file must include ProductDef and ProductView elements (with attributes and subelements) for each Major Component to link it to an Item Revison:

<ProductDef id="id134">

<InstanceGraph id="id135"> <ProductInstance id="id110" partRef="#id111"/>

<ProductRevisionView id="id111" revisionRef="#id28"/> </InstanceGraph> </ProductDef > <ProductView id="id133" rootRefs="id101" subType="List" primaryOccurrenceRef="id101"> < UserData type="TC Specific Properties"> < UserValue value="imprecise" title="BOM_precision_type" />

</UserData> <Occurrence id="id101" instancedRef="#id28" occurrenceRefs="id102" />

<Occurrence id="id102" instancedRef="#id55" instanceRefs="#id110"> <UserData type="AttributesInContext">

<UserValue value="1" title="Quantity" /> </UserData>

The ProductInstance element's partRef attribute must match the corresponding RealizedProductRevisionView element's id.

The ProductRevisionView element's revisionRef attribute must match the RealizedProductRevision for the Aircraft to which the Component is linked.

The ProductView element's rootRef attribute must match the Occurrence for the Aircraft Revision to which the Component is linked.

The ProductView element's primaryOccurrenceRef attribute must match the Occurrence for the Component.

The first Occurrence element's instancedRef (note the name includes a 'd') attribute must match the Aircraft Revision to which the Component is linked.

The Occurrence element's occurrenceRef attribute must match the Occurrence for the Component.

The second Occurrence element's instancedRef (note the name includes a 'd') attribute must reference the Component Revision.

The Occurrence element's instanceRef (note the name does not include a 'd') attribute must match the Aircraft Revision's ProductInstance element.

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each MRO Aircraft & Physical Part to their Aircraft or Component:

<GeneralRelation id="id115" subType="TC_Realized_By" relatedRefs="#id26 #id27" />

The second relatedRefs id is the id of the Aircraft or Component's Product element.

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each Aircraft’s Quarterly hours Report to its Aircraft and Major Component:

<GeneralRelation id="id116" subType="IMAN_reference" relatedRefs="#id26 #id94" />

The first relatedRefs id is the id of the Aircraft or Major Component Revision's RealizedProduct element.

The second relatedRefs id is the id of the Aircraft’s Quarterly hours Report Product element.

The PLMXML file must include a GeneralRelation element (with attributes and subelements) for each MRO…