Anda di halaman 1dari 611

COMMONWEALTH OF AUSTRALIA

AUSTRALIAN DEFENCE STANDARD

DEF(AUST)5692 Issue 1
Dated 01 March 2003

LOGISTIC SUPPORT ANALYSIS RECORD


REQUIREMENTS FOR THE
AUSTRALIAN DEFENCE ORGANISATION

DEFENCE STANDARD
*
PUBLISHED UNDER AUTHORITY
DEPARTMENT OF DEFENCE
DEF(AUST)5692
DOCUMENT MANAGEMENT INFORMATION

This page lists the ownership and areas responsible for providing technical approval for this Standard. It also
lists applicable documents that should be read in conjunction with this Standard. The information below needs to
be reviewed for currency and applicability as per the 5-year review cycle detailed in the Defence Standardisation
Manual (STANMAN).

Sponsor: Director General Material Policy and Services


Russell Offices
CANBERRA ACT 2600

Approving Authority: Head Electronic Systems Division


Russell Offices
CANBERRA ACT 2600

Applicable Documents: DI(G) LOG (to be issued) Defence Policy for Logistic Support Analysis

DI(G) LOG 03-6, Integrated Logistic Support

DEF(AUST)5691, Logistic Support Analysis

MIL-STD-1388-1A, Logistic Support Analysis (cancelled)

MIL-STD-1388-2B, DOD Requirements for a Logistic Support Analysis Record


(cancelled)

MIL-STD-1390D, Level of Repair Analysis (cancelled)

MIL-STD-1629A, Procedures for Performing a Failure Mode, Effects and Criticality


Analysis (cancelled)

MIL-STD-2173, Reliability-Centered Maintenance Requirements for Naval Aircraft,


Weapon Systems and Support Equipment (cancelled)

ii
DEF(AUST)5692

AMENDMENT LIST

Amendment Effected

No Date of Issue Signature Date Incorporated

Revision Note

DEF(AUST)5692 dated 01 March 2003 is an original document.

Historical Record

The first edition of this document has been converted from MIL-STD-1388-2B and AAP 5102.003.

iii
Blank Page

iv
DEF(AUST)5692

AUSTRALIAN DEFENCE STANDARD

DEF(AUST)5692

LOGISTIC SUPPORT ANALYSIS RECORD


REQUIREMENTS FOR THE
AUSTRALIAN DEFENCE ORGANISATION
01 MARCH 2003

1. Logistic Support Analysis (LSA) is a selected application of systems engineering techniques, originally
developed by the Untied States Department of Defense (US DoD) to provide effective and consistent analytical
processes for identifying and implementing supportability requirements for the development and acquisition of
major capital equipment. LSA, as applied in the Australian Defence Organisation (ADO), expands LSA as a Life
Cycle Discipline to enable the benefits of consistent analytical techniques to be readily applied to major and
minor projects, modifications, In-service analysis for logistic optimisation, and disposal.

2. A key enabler to the success of the LSA Program, and the fourth goal of LSA, is to use a consistent
data source for analysis to ensure an integrated solution between LSA, Integrated Logistic Support and related
disciplines. The LSAR was developed to fulfill this requirement. The ADO has added functionality to the LSAR
developed by the US DoD and defined in MIL-STD-1388-2B (cancelled).

3. DEF(AUST)5692 provides the definition of data elements and structure of the Logistic Support Analysis
Record for the ADO to enable collection, storage, retrieval and review of LSAR data.

4. DEF(AUST)5691 contains information for the analysis activities that are selectively conducted as part
of a Logistic Support Analysis Program conducted in accordance with ADO policy. A number of these activities
provide and use LSAR data.

v
Blank Page

vi
DEF(AUST)5692

CONTENTS
Page
Document Management Information ii
Amendment list iii
Contents vii
List of Figures viii

CHAPTER 1 LOGISTIC SUPPORT ANALYSIS RECORD PROGRAM REQUIREMENTS


INTRODUCTION 1-1
SCOPE OF DEF(AUST)5692 1-2
PROGRAM REQUIRMENTS AND INTERFACES 1-3
DEFINITIONS AND ACRONYMS 1-6
REFERENCES 1-7
CHAPTER 2 LSA RECORD REQUIREMENTS
GENERAL REQUIREMENTS 2-1
LSAR DATA SELECTION SHEETS 2-1
LSAR DATA 2-1
CHAPTER 3 DETAILED INSTRUCTIONS FOR THE PREPARATION OF LSAR RELATIONAL TABLES
INTRODUCTION 3-1
REQUIRING AUTHORITY DATA TABLES 3-1
PERFORMING ACTIVITY DATA TABLES 3-2
LCN ASSIGNMENT AND STRUCTURE 3-4

Annexes:
A. LSAR Relational Tables
B. LSAR Reports
C. Guidance for the assignment of LCN, ALC, UOC, and Parts Application
D. Application and Tailoring Guidance for the LSAR
E. Data Element Dictionary

vii
DEF(AUST)5692

LIST OF FIGURES
Page
Figure 1-1: LSAR data flow and Systems Engineering interface. 1-4
Figure 1-2: RAM Parameter Relationships 1-5
Figure 1-3: RAM Parameter Relationships – continued 1-6

viii
DEF(AUST)5692 CHAPTER 1

CHAPTER 1

LOGISTIC SUPPORT ANALYSIS RECORD PROGRAM REQUIREMENTS


INTRODUCTION
Purpose

1.1 The purpose of a Logistic Support Analysis Record (LSAR) is to provide a consistent information
source to support the conduct of Logistics Support Analysis (LSA) and related analyses, and enable the
development and preparation ILS data products.

1.2 An LSAR applied effectively support analysis and achieves the fourth goal of LSA for both project
and In-service use, to:

"Develop and prepare attendant data products from a consistent information source."

1.3 The purpose of this standard is to define the requirements for the application of a Logistic Support
Analysis Record for and by the Australian Defence Organisation (ADO).

Background

1.4 DEF(AUST)5692 has been developed from MIL-STD-1388-2B with additional ADF requirements.
MIL-STD-1388-2B was through the joint efforts of the US military services and the Federal Aviation
Administration, with assistance of private industry. The goal was to establish uniform requirements for
development and delivery of LSA Record data. The LSA documentation, including LSAR data, was
generated as a result of performing analysis specified in MIL-STD-1388-1A, Logistic Support Analysis.
Although MIL-STD-1388-1A and MIL-STD-1388-2B are no longer supported by the US DoD, their application
has been replaced in the ADO by DEF(AUST)5691 and DEF(AUST)5692 respectively. DEF(AUST)5692
(this standard) defines the LSAR database design to be used for the development and delivery of LSAR data
generated as a result of performing LSA in accordance with DEF(AUST)5691.

1.5 The LSAR, as designed herein, is intentionally structured to accommodate the maximum range of
data potentially required by all Integrated Logistic Support (ILS) element functional areas and a number of
other Systems and Design Engineering functions. This approach permits standardisation of field lengths and
Data Element Definitions (DEDs), and establishes "one face to industry" for government required LSA data.
However, LSA documentation must be tailored to each acquisition program and for each phase of the
materiel life cycle. The tailoring of LSAR data should be consistent with the level and depth of LSA
performed in accordance with (IAW) DEF(AUST)5691 as required to achieve Supportability and other ILS
goals. Application guidance in Annex D is included to provide guidance for tailoring LSAR data requirements
to meet individual program objectives in a cost-effective manner. The general requirements of this standard
also require completion of LSAR Data Selection Sheets to identify the specific data requirements for each
program in order to prevent indiscriminate blanket applications of the data requirements.

1.6 This standard is directed toward improving the cost effectiveness of the generation, maintenance,
acquisition, and use of the technical data required to support an ILS program. This is accomplished through
the following:

a. Standardisation of LSAR Data Element Definitions (DEDs), field lengths, and formats
between the services and industry.

b. Consolidation of logistics orientated technical information for the various engineering


disciplines and ILS elements into one file to reduce redundancy, facilitate timely usage, and
enhance consistency between elements and disciplines.

c. Maximum use of industry developed integrated data systems tied to engineering,


manufacturing, and product support databases as sources of LSA documentation.

d. Requiring delivery of LSAR data in a format which promotes/accommodates current


database technology.
DEF(AUST)5692

1.7 The LSAR documents data across all ILS functional areas. This characteristic makes an LSAR an
ideal vehicle for integration of systems engineering design, manufacturing, and product support databases
for life cycle management of a system. The relational design of LSAR data is intended to facilitate such
integration and to encourage independent development of useful ad hoc queries that promote use of data in
the design process. The use of industry developed, cost-effective automation tools which link "islands of
automation" (eg., computerised drawings and technical manual authoring systems) through the LSAR is
encouraged.

1.8 This standard allows for delivery of LSAR data in manual or automated mode, and on-line access
to LSAR data, as specified by the requiring authority. It does not prescribe Automated Data Processing
(ADP) software that must be used to process LSAR data. The minimum ADP design requirements that must
be adhered to for industry developed LSAR ADP systems are described under General Requirements.
These requirements are the basis for validation by government of industry developed LSAR ADP systems.

Conversion from MIL-STD-1388-2B/AAP 5102.003

1.9 Due to intended compatibility, any program correctly implementing an LSAR for the ADO prior to
the release of this standard will have no conversion requirements, see "Important Note" below.

Important Note: DEF(AUST)5692 has retained all LSAR design requirements from MIL-STD-1388-2B without
change. DEF(AUST)5692 also includes additional ADF requirements from AAP 5102.003. Projects that
have applied MIL-STD-1388-2B or AAP 5102.003 will not need to implement any changes to their LSAR to
meets the requirements of this standard.

SCOPE OF DEF(AUST)5692
Content

1.10 This standard prescribes the Data Element Definitions, data field lengths, and formats for LSAR
data. It identifies the LSAR reports that are generated from the LSAR data and identifies the LSAR relational
tables and automated data processing (ADP) specifications for transmittal and delivery of automated LSAR
data.

Application of Standard

1.11 The requirements of this standard are applicable to major and less than major system/equipment
acquisition programs, major modification programs or capability updates, applicable research and
development projects, and for In-service configuration management, engineering and logistic support
activities.

1.12 DEF(AUST)5692 is for use by both Contractor and government activities. As used in this standard,
the Requiring Authority is generally a government activity, but may be a Contractor when LSA documentation
requirements are levied on subcontractors. The Performing Activity may be either a Contractor or
government activity. The use of the term, contract, in this standard includes any document of agreement
between organisations to include between a government activity and another government activity, between a
government activity and a Contractor, or between a Contractor and another Contractor.

Structure

1.13 DEF(AUST)5692 is structured as followed:

a. Chapter 1: LSAR Program Requirements.

b. Chapter 2: LSAR General Requirements.

c. Chapter 3: Detailed Requirements for the Preparation of an LSAR.

(1) Annex A. Contains the LSAR relational tables necessary for the development of a
relational LSAR database.

(2) Annex B. Contains a description and the required format for each LSAR standard
report.

1-2
DEF(AUST)5692

(3) Annex C. Explains assignment of the key data elements: LSA Control Number (LCN),
Alternate LCN Code (ALC), Usable on Codes (UOC).

(4) Annex D. Contains guidance for tailoring of the LSAR data.

(5) Annex E. Contains an LSAR Data Element Dictionary providing definitions for all data
specified by Annex A.

1.14 Chapter 3, Annexes A, B and E establish requirements and can be included/referenced in


contractual documents. Annexes C and D provide guidance for the implementation of LSAR data entry and
program application of the LSAR.

PROGRAM REQUIRMENTS AND INTERFACES


Tailoring

1.15 The requirements for an LSAR shall not be specified in a contract without also specifying the
requirements for LSA. DEF(AUST)5691 has been developed as the companion standard to this standard. If
DEF(AUST)5692 is being utilised to specify LSAR requirements in a contract, then the Requiring Authority
should also use DEF(AUST)5691 to develop the LSA requirements for the contract, including the LSA
documentation requirements needed to support the ILS/LSA Program. Further tailoring of LSA
documentation requirements shall be based on LSA Activities performed in previous program phases, other
System Engineering program requirements, and logistics related Data Item Descriptions (DIDs) included in
the solicitation documents. Detailed guidance on tailoring LSAR data requirements is included in Annex D.

LSA/LSAR Guidance Conference

1.16 The purpose of the LSAR portion of the LSA Guidance Conference is to ensure the Performing
Activity and Requiring Authority have a firm understanding of the relationship between the LSA Activities to
the LSA documentation, program milestones, and contractual requirements. The LSA Guidance Conference
may be conducted during an offer definition / risk reduction phase if one is programmed, which enables
LSAR data requirements to be defined pre-contract. When a guidance conference is not contractually
specified and the Performing Activity desires a conference, the Performing Activity shall propose a date and
place. The specific date and place for the guidance conference will be determined by the Requiring
Authority and Performing Activity. The guidance provided to the Performing Activity by the Requiring
Authority may include, but shall not be limited to, the following:

a. Performing Activity inquiries relative to contractual LSAR requirements;

b. operational and support concepts, eg., operating rates, conversion factors, maintenance
levels, skill codes, etc;

c. baseline logistics data, ie., available skills, training programs, tools, test equipment, and
facilities;

d. requirement for joint service validation of the Performing Activity developed LSAR data,
when applicable;

e. guidance relative to the use and application of LSAR data elements;

f. review of the LSA candidate list;

g. scheduling the progressive development and delivery of LSAR data; and

h. process of review and feedback of review comments to Performing Activity analysts.

LSA Data Documentation Process

1.17 The LSA process is conducted on an iterative basis through all phases of the system/equipment life
cycle to satisfy the support analysis objectives. Similarly, LSA data is generated in all phases of the
system/equipment life cycle and is used as input to follow-on analyses and as an aid in developing logistics
products. A detailed display of the LSAR data flow and its interface, with the Systems Engineering and the
logistics functional organisations, is provided on Figure 1-1.

1-3
DEF(AUST)5692

Figure 1-1: LSAR data flow and Systems Engineering interface.

1.18 Figure 1-1 represents general data table generation relationships and organisational elements
normally responsible for generation of LSAR data. Figure 1-1 should not be misconstrued to mean that one
type of data table must be completed in its entirety before the next data table can be completed.

1.19 For example, certain reliability and maintainability (R&M) estimates included on the B tables must
be completed prior to estimating logistics elements on other tables (RAM relationships are shown on Figure
1-2 and 1-3). However, generation of LSAR data is also dependent on the design engineering process and
release of drawings (preliminary, development, or final). Completion of B and C tables for a single assembly
would provide the information necessary for initiation of data tables associated with support items (H tables),
and also data related to support and test equipment (E & U tables), facilities (F tables), and skills evaluation
and justification (G tables) when peculiar requirements are identified. The LSAR data flow will be repeated
for each repairable item comprising a system/end item until the total logistics data requirements are
established.

1-4
DEF(AUST)5692

Figure 1-2: RAM Parameter Relationships

1-5
DEF(AUST)5692

Figure 1-3: RAM Parameter Relationships - continued

1.20 Figures 1-2 and 1-3 show the RAM parameter relationships that form the basis to calculations of
the three measures of availability that may be recorded in the LSAR, achieved, inherent and operational
availability (DEDs 001, 164, and 273 respectively). Input sources for establishing data are listed as A to F.
The numbers 1 to 6 are used for cross-referencing between the two figures. These relationships lead to the
identification of the respective availability measures at the top of Figure 1-2. The rest of Figure 1-2 is based
on determining reliability parameters while Figure 1-3 focuses on maintainability parameters (repair times).

1.21 Using Mean Time Between Maintenance Actions (MTBMA) Unscheduled [4] as an example, which
is used in calculating both achieved and operational availability, Figure 1-2 can be read as follows. MTBMA
Unscheduled can be derived from Failure Rates from reliability predictions (A) assessed against inherent
maintenance actions estimated from comparative analysis (B) and combined with induced maintenance and
maintenance actions where no defect was found (induced by user/maintainer error and false indications
respectively).

DEFINITIONS AND ACRONYMS


Definitions

1.22 For commonly used LSA/LSAR terms refer to the Glossary at the end of this standard.

Acronyms

1.23 For commonly used LSA/LSAR Acronyms and Abbreviations refer to the Acronyms and
Abbreviations list at the end of this standard.

1-6
DEF(AUST)5692

REFERENCES
Related Policies

1.24 DI(G) ADMIN 05-1 Defence Capability Management Cycle

1.25 DI(G) LOG (to be issued) Logistic Support Analysis

1.26 DI(G) LOG 03-6 Integrated Logistic Support

1.27 DI(G) LOG 08-6 Reliability, Availability and Maintainability

1.28 DI(G) LOG 03-4 Life Cycle Cost Analysis

Military Standards and Handbooks

1.29 DEF(AUST)5691 Logistic Support Analysis

1.30 MIL-STD-1388-1A Logistic Support Analysis (superseded).

1.31 MIL-STD-1388-2B DOD Requirements for a Logistic Support Analysis Record (superseded).

1.32 MIL-STD-1629A, Procedures for Performing a Failure Mode, Effects and Criticality Analysis
(cancelled)

1.33 MIL-STD-2173, Reliability-Centered Maintenance Requirements for Naval Aircraft, Weapon


Systems and Support Equipment (cancelled)

1.34 MIL-HDBK-1388 (superseded).

Other Publications

1.35 Integrated Logistic Support Handbook, 2nd Edition, James V. Jones.

1-7
DEF(AUST)5692

BLANK PAGE

1-8
DEF(AUST)5692 CHAPTER 2

CHAPTER 2

LSA RECORD REQUIREMENTS


GENERAL REQUIREMENTS
2.1 LSA documentation, including LSAR data, is generated as a result of the analysis specified for the
LSA Program. As such, the LSAR shall serve as the main Integrated Logistic Support (ILS) technical
database applicable to all materiel acquisition programs to satisfy the support acquisition. The DEDs, data
field lengths, and data formats described in Annexes A and E shall be adhered to by the Performing Activity
in establishing the LSAR database. The specific data entry, media, storage, and maintenance procedures
may be left to the Performing Activity. To ensure data exchange, LSAR software products shall comply with
the requirements of DEF(AUST)5692, by meeting the required data table and transfer file formatting
requirements. The LSAR data forms a database to:

a. Determine the impact of design features on logistics support.

b. Determine the impact of the proposed logistics support system on the system/equipment
availability and maintainability goals.

c. Provide data for trade-off studies, life cycle costing, and logistic support modelling.

d. Exchange valid data among functional organisations.

e. Influence the system/equipment design.

f. Provide data for the preparation of logistics products specified by Data Item Descriptions
(DIDs).

g. Provide the means to assess Supportability of the fielded item.

h. Provide the means to evaluate the impact of engineering change, product improvement,
major modification or alternative proposals.

LSAR DATA SELECTION SHEETS


2.2 The LSAR Data Selection Sheet provides a vehicle for identifying the required LSAR data elements
to be completed and, when applicable, the media of delivery (e.g., floppy disk, magnetic tape, CD-ROM, etc).
Preparation of the LSAR data requirements form should be a result of the LSAR tailoring process discussed
in Annex D.

2.3 The data requirements forms are used to identify the specific data elements that are required and
identified on the relational data tables. In addition, the form will be used to specify the data elements
required for each Provisioning Technical Documentation (PTD) list or packaging categorisation of items
required. Generation of the PTD lists (format shown as Table 1, LSA-036 report) may be accomplished
manually or via automation techniques.

2.4 When more than one option of entry for a data element is possible, the options are spelled out as
part of the data element dictionary. In a similar manner, the LSAR Data Selection Sheets list the options for
data elements that have more than one option for entry. Only one option will be specified for a data element
with multiple entry options.

2.5 The LSAR Data Selection Sheets will be attached to the contract SOW through a Contract Data
Requirements List (CDRL). Detailed instructions for completing the LSAR Data Selection Sheet are provided
in Annex D.

LSAR DATA
2.6 The preparation and maintenance of LSAR data is directly related to the hardware and software
design of an end item. The Requiring Authority is responsible for specifying the equipment indenture level
and the level(s) of maintenance for which LSAR data will be prepared and maintained, or identify how they
are to be determined. The LSAR data may be prepared and maintained manually, using the LSAR data
DEF(AUST)5692

tables displayed in Annex A, or equivalent LSAR formats approved by the Requiring Authority. It may also
be prepared and maintained automatically through use of LSAR application software. The decision to
automate the LSAR data versus a manual LSAR must take into account the following factors:

a. Costs and schedules of preparation.

b. Availability of an ADP system.

c. Hardware complexity.

d. Acquisition/life cycle phase.

e. Requiring Authority's schedule requirements.

f. Design stability.

g. Compatibility with other LSAR preparers, as well as the Requiring Authority's ADP system.

h. Requiring authority involvement.

Manual Preparation of LSAR Data

2.7 Manual preparation is defined as not using LSAR software to prepare LSAR data; this practice is
not preferred for major projects but sometimes a suitable option for projects with minimal data requirements.
All manual preparation must comply with table structures, relationships and data element field formats or
considerable manual rework of data will be required for conversion of data into Defence project and In-
service LSAR systems.

2.8 The LSAR data tables would be provided as spreadsheet or word processor tables; the main
problem with this approach is that data may require significant manipulation and most likely re-typing of data
in order to transfer the information into an LSAR. There is also the option of preparing the ASCII text transfer
file directly, this enables data import into a compliant LSAR although this is a detailed and time consuming
task that requires significant understanding of LSAR tables, relationships and transfer file requirements to be
successful.

2.9 It may be preferable to transfer non-LSAR prepared data into an LSAR instead of to manual
preparation of data. This typically requires translation from a Contractor's in-house system, or custom LSAR
database tables, refer to "Use of Non-compliant Logistics Software Packages".

Manual Preparation of LSAR Reports

2.10 When required, any or all of the LSAR reports contained in Annex B can be produced in a non-
automated environment. When the LSAR reports are produced by non-automated means, the reports shall
be in accordance with (IAW) the content, format, sequence, and computational requirements contained in
Annex B.

2.11 There are many disadvantages of manual report preparation, not least it is time consuming and the
effort can quickly outweigh the cost of an automated LSAR software package. Additionally, manual
preparation requires repeated writing of the same data, and lacks the flexibility to keep and easily update the
data through life. Manual preparation is only an option for small programs where data will not be retained.

Automated Data Preparation Using LSAR Software

2.12 The LSAR data preparation may be automated and, as such, a compliant LSAR ADP system shall
be used as follows.

2.13 Performing Activity LSAR System. The Performing Activity shall use a compliant LSAR software
system for the preparation and transfer of data to the Requiring Authority. The systems shall be capable of
fulfilling the basic criteria defined in the paragraph titled "Requirements for Compliant LSAR Software
Packages" below. These systems shall be compliant by exhibiting processing capability to input, edit, and
build LSAR relational tables and output the relational tables and standard LSAR reports.

2.14 Requirements for Compliant LSAR Software Packages. The independently developed LSAR
ADP system will be validated based on the following design criteria:
2-2
DEF(AUST)5692

a. Shall be capable of automatically accepting relational table data in the formats displayed in
Annex A, using the data elements, definitions, data element edits, data field lengths, and
data relationships contained in Annexes A and E.

b. Shall be capable of producing LSAR reports as displayed in Annex B.

c. Shall be capable, as a minimum, of satisfying all Annex E (Data Element Codes) of data
elements.

d. Shall be capable of outputting LSAR ADP relational tables as displayed in Annex A.

e. Shall be capable of outputting change only data from last delivery of LSAR data.

f. Shall provide automated user comment capability.

2.15 These minimum LSAR design criteria are required for compliance with this standard. Additional
system automation is strongly encouraged.

2.16 LSAR data may be prepared using a range of available software packages that may be hosted on
a network file server, a stand-alone personal computer or as an Internet based application. Regardless of
the application delivery method the main criteria for LSAR software are compliance with the structure and
functions of the LSAR specified in DEF(AUST)5692 or approved compatible database definition (such as
MIL-STD-1388-2B with additional ADF data tables).

2.17 Use of Non-compliant Logistics Software Packages. It may occur that large quantities of
suitable, existing logistics data are available in an "LSAR non-compliant" data format. In order to reduce
LSA Program costs, unnecessarily repeating of analysis should be avoided and conversion of the existing
data to LSAR format should be pursued where cost-effective to do so. Provided that the existing data, via a
conversion process, meets the import/export aspects of the data requirements for compliance, the Requiring
Authority may choose not to enforce the requirement for the contractor to maintain a compliant LSAR. In this
instance, access to the developing data should also be provided via access to the Performing Activity's data
source.

2-3
DEF(AUST)5692

BLANK PAGE

2-4
DEF(AUST)5692 CHAPTER 3

CHAPTER 3

DETAILED INSTRUCTIONS FOR THE PREPARATION OF LSAR


RELATIONAL TABLES
INTRODUCTION
3.1 These instructions are applicable for either the automated or manual preparation of the LSAR data.
Each data table contained in Annex A is identified by a three-position code. The first position of this code
identifies the functional area most directly associated with the information contained within the data table.
The second position uniquely identifies the table within a functional area. The third position may be used to
insert additional data tables at a later date.

REQUIRING AUTHORITY DATA TABLES


General

3.2 Information for the "A" and portions of the "X" tables will be provided by the Requiring Authority and
may be incorporated with the solicitation (eg., in the Operational Concept Document and Function and
Performance Specification), or addressed at the LSA/LSAR Guidance Conference. This information will also
be documented on the Data Selection Sheet or provided as an LSAR transfer file.

Cross Functional Requirements

3.3 Data tables that are identified by "X" in the first position have attributes that cross multiple
functional areas or are used as a link to various functional data tables. The tables are used to record
information from the Requiring Authority with respect to supply, maintenance and personnel data, which are
used in trade-off analyses. The individual data elements may be used in conjunction with other LSA data in
several LSA models with only minor adjustments, if any, for compatibility of units.

Operations and Maintenance Requirements

3.4 Data tables identified by "A" are structured to consolidate the pertinent information related to the
anticipated operation of the system, environment in which the system will be operated and maintained, and
the system maintenance requirements which must be met. This information is prepared for the system, and
for each subsystem for which maintenance requirements are to be imposed, and will also be prepared for
Government Furnished Equipment (GFE). When separate operational/maintenance requirements are
established for wartime and peacetime scenarios, each set of requirements will be documented as separate
table rows. The number of rows of information that will be prepared shall be based on the LSA Activities and
depth of analysis performed, or as specified by the Requiring Authority. The Performing Activity shall
incorporate this information into the LSAR and shall complete the appropriate key fields, unless the field has
been completed by the Requiring Authority. Detailed instructions for completion of this information are
contained in Annexes A and E.

ADO Unique Requirements Tables

3.5 Tables containing ADO unique requirements predominantly hold data for scheduled Servicings,
technical maintenance plan preparation, and Mission System role configurations. These areas are subject to
update during the In-service phase, following initial population by the Performing Activity. Refer to the
appropriate Annex for specific details regarding ADF unique requirements.

Additional GFI

3.6 The Requiring Authority may be required to provide additional Government Furnished Data and
Information (GFD/GFI) to populate a number of data fields in addition to Cross Functional Requirements and
Operations and Maintenance Requirements described above. These additional GFD/GFI requirements will
vary depending on the program and Performing Activity involved. Additional GFD/GFI LSAR data
requirements may include:

a. Skill codes required/applicable to the user organisations and support personnel;

b. Preferred Support, Test and Training Equipment Lists;


DEF(AUST)5692

c. Task Remarks for applying predetermined maintenance policies to Task Analysis (eg., non-
economic LORA criteria).

3.7 The above GFD/GFI can be provided in either LSAR format or transferred from other data sources.

PERFORMING ACTIVITY DATA TABLES

General

3.8 The Performing Activity shall complete the required fields of data tables "B", "C", "E", "F", "G", "H",
"J", "U", "M", "R", "V", "W", "Z" and portions of the "X" IAW the information contained in Annexes A and E
and to the extent specified by Data Selection Sheet. When DEDs state that specific information will be
provided by the Requiring Authority, the information may be included in the solicitation or not later than the
LSA/LSAR Guidance Conference.

Reliability, Availability, Maintainability; Failure Mode Effects and Criticality Analysis; and
Maintainability Analysis

3.9 The "B" data tables provide a description of the function of each item within the system; outline the
maintenance concept to be utilised for design and support planning purposes; and, identify any design
conditions such as fail-safe requirements/environmental or nuclear hardness considerations imposed upon
the system. The tables summarise the reliability, maintainability, and related availability characteristics of the
item resulting from the failure modes and effects, criticality, and maintainability analyses, and accommodates
a narrative description of any analysis related to the potential redesign of an item.

3.10 A separate row of information is prepared for the system, for each subsystem contained in the
system, and for each level of breakdown for that subsystem until the lowest repairable item has been
documented. The degree of breakdown shall be specified by the Requiring Authority.

3.11 Additional "B" data tables are designed to accommodate the Failure Modes and Effects Analysis
(FMEA), as described by Task 101 of MIL-STD-1629A. Criticality Analysis added to FMEA (making Failure
Modes, Effects and Criticality Analysis (FMECA)) as described in task 102, and maintainability analyses from
task 103 of MIL-STD-1629A, are recorded within the B tables with linkage to CA for task identification.
These tables will also accommodate the Damage Mode and Effects Analysis, to be utilised for survivability
and vulnerability assessments, as described in task 104 of MIL-STD-1629A. The purpose of the criticality
analysis is to rank each identified failure according to the combined influence of severity classification and
failure probability of occurrence. The relative ranking of the calculated item criticality numbers highlights
system high-risk items.

3.12 The maintainability analysis serves as the starting point for maintenance task analysis. The
FMECA documents the effects of an item failure upon system operations and is used to classify each
potential failure according to the severity of those effects. The FMECA is initiated as an integral part of the
early design process and is derived through a functional analysis. To provide concise information on the
failure analysis, functional block diagrams should be provided. Subsequent to this effort, data is prepared to
the required indenture level. The results are used as a guide in evaluating design features and as a basis for
initial quantitative predictions. The analysis identifies high-risk items, facilitates the evaluation of design
features, and provides the basis for criticality and maintainability analyses. The failure, effects data are the
basis for developing fault location and troubleshooting routines.

3.13 These tables also document Reliability Centered Maintenance (RCM) logic results and
accommodate a narrative description of any analysis related to the potential redesign of an item. These
tables are completed to the same indenture level as the item R&M Characteristics tables.

Task Inventory, Task Analysis, Personnel, and Support Requirements

3.14 The "C" table Operation and Maintenance summary information is used to consolidate the
operations and maintenance tasks identified for each repairable assembly and indicates necessary support
requirements (eg., facilities, training equipment, tools, and support equipment). Included are the
identification of the combination of all human performances required for operation and maintenance of a one-
person position in a system (eg., A job is that of a driver; one of the duties of a driver is emergency repair; a
task within emergency repair is changing a flat tyre).

3-2
DEF(AUST)5692

3.15 The task identification information on these tables is developed from the RCM analysis,
maintainability analysis, and from the maintenance task analysis. This information is completed to the same
indenture level as the R&M and FMECA Tables. This information is identified on "C" data tables.

3.16 Additional "C" data tables provide a detailed step-by-step narrative description of how tasks
identified on the Task Summary are to be performed, the specific skill specialty requirements, and applicable
task work-hours per skill specialty. These tables identify training, personnel, support equipment, and supply
support requirements necessary for the accomplishment of the individual tasks. Data on these tables provide
information necessary for the development of technical publications, training programs of instruction, supply
support, and personnel requirements. This information will be initiated during the detailed system/equipment
design effort.

3.17 For all operational and maintenance level tasks, specific requirements for the completion of the
task analysis, including the documentation of maintenance levels, specific hardware items, and indenture
levels, will be as specified by the Requiring Authority. Included in this documentation are the combination of
all human performances required for operation and maintenance in a hierarchical breakdown, eg., mission,
scenario, function, job, duty, task, subtask and element.

Support Equipment and Training Material Requirements

3.18 Data tables identified by "E" are structured to consolidate the pertinent information related to
existing or new support/test equipment or training material, eg., physical characteristics, calibration
requirements, and test parameters. This information also serves as identification of hardware and software
elements required to conduct off-line tests.

Unit Under Test Requirements and Justification

3.19 Data tables "U" are structured to identify the Unit Under Test (UUT), which will be removed from
the system and those hardware and software elements required to test the UUT with off-line support/test
equipment. The unique combination of these elements required for a specific UUT and support/test
equipment configuration is a Test Program Set (TPS). In addition to defining the TPS elements, this
information provides configuration identification of the UUT (ie., UUT, and the support/test equipment to be
used in the test). This information is established for each UUT, which has a requirement to be tested by the
support/test equipment documented.

Facility Considerations

3.20 Data tables identified by "F" are used to describe and justify all proposed special or additional
facility requirements, which are indicated as a result of the maintenance task analysis. Sketches or other
information may be incorporated as part of the hard copy storage by entering the control fields (LCN and task
code when applicable) on the supplemental data. These data are required to provide facility designers with
the technical information necessary to prepare facility plans.

Personnel Skill Considerations

3.21 Data tables identified by "G" are used to describe and justify any new or modified personnel skills
required to support the system/equipment. This information shall be completed for each new or modified skill
required as a result of the maintenance task analysis and skill analysis.

Packaging and Provisioning Requirements

3.22 Data tables identified by "H" are used to document the static parts data (non-application
dependent) related to provisioning screening results, packaging data, price analysis data, parts break-out
coding results, and common maintenance data. This information is completed for each item that comprises
a system (by reference number) to include, as specified by the Requiring Authority, repairable items, non-
repairable items, bulk materials, common hardware, and common and peculiar support equipment.

3.23 Additional "H" data tables are used to capture application data of items identified by the static data
tables. This information will be prepared for each application of the item in a different next higher assembly
and will document that data required for initial support requirements determination, repair parts manual, etc.

3-3
DEF(AUST)5692

Transportability Engineering Analysis

3.24 Data tables identified by "J" are designed to capture the transportability engineering requirements
for an end item. This information shall be prepared for the end item in its shipping configuration. In the
event the end item is sectionalised for transport, the information shall be completed for each section of the
end item. It may also be completed for critical sub-components or as specified by the Requiring Authority.
External items, which are removed and stored inside the package during transport, are not considered
sectionalisation for transport.

ADF Unique Requirements Tables

3.25 Data tables identified by "M" are used as extended memo tables to record additional narrative
information within the LSAR.

3.26 Data tables identified by "R" are used to hold additional Technical Maintenance Plan and Planned
Servicing Schedule details, supporting the "W" tables.

3.27 Data tables identified by "V" are used to capture alternative configurations of the end item based on
the roles that may be assigned to a multi-role asset. The "V" tables are also used to identify
venue/parts/service cost management details for the In-service management of authorisations, entitlements,
repair costs and spares tracking.

3.28 Data tables identified by "W" are used to capture information for Technical Maintenance Plans,
Planned Servicing Schedules, and authorisations for the use of alternative parts.

3.29 Data tables identified by "Z" (of which there is only ZL) are used to record changes in ALC, such
that all ALCs belonging to the one UOC can be set to the same number. This enables new and complete
LCN structures to be built with the same ALC, for example, when the complete LCN/ALC structure from a
manufacturer is not imported, this enables the purchased system/end item (UOC) to have a uniform ALC
number.

LCN ASSIGNMENT AND STRUCTURE

3.30 The development of the LCN structure and assignment of individual LCNs is the responsibility of
the Performing Activity, and the resulting structure should be approved by the Requiring Authority. The LCN
structure should represent a top-down generation or functional breakdown of hardware and software IAW the
standard engineering drawing structure. LCN sequencing assignment shall adhere to the American
Standard Code for Information Interchange (ASCII). Guidance for assignment of LCN, ALC, and UOC are
contained in Annex C. This annex is not contractual and does not establish requirements. However, the
guidance in Annex C should be followed to ensure proper assignment of LCNs for a given system/equipment
as this is critical for successful configuration management and ILS product development.

Annexes:
A. LSAR Relational Tables
B. LSAR Reports
C. Guidance for the assignment of LCN, ALC, UOC, and Parts Application
D. Application and Tailoring Guidance for the LSAR
E. Data Element Dictionary

3-4
DEF(AUST)5692 ANNEX A TO
CHAPTER 3

CHAPTER 3

LSAR RELATIONAL TABLES


INTRODUCTION
Scope

1. Annex A establishes the Logistic Support Analysis Record (LSAR) relational table titles and data content
and format to be produced by an LSAR relational Automated Data Processing (ADP) system. It defines all
the relational tables that comprise an LSAR database.

Concept

2. In a relational database system, information is organised in the form of tables. Categories or columns of
information are listed across the top of each table. Individual sets of information are listed as rows. LSAR
relational tables are two-dimensional matrices of related data. Tables are defined in terms of columns (or
data element definitions (DED)) and rows (or multiple sets of the columnar data elements). Information in
this format can be easily visualised and understood. Within each table, certain data maybe defined as
foreign key, or key, eg., required to be present when a new row of data is established. These data keys
comprise a unique set of identifiers for each row of information in the data table. Relational tables are
structured according to the data associations, which dictate the table configuration. Although each relational
table is independent and equal, data integrity rules will dictate that a row of information be established in a
table from which foreign keys originate, prior to the establishment of the lower-tiered data table. The
interrelationships and data hierarchies between tables are only established through common data element
keys and data values. The tables listed in Annex A comprise the total LSAR relational database.

RELATIONAL DATA TABLES FORMAT


Functional Areas

3. The relational tables are shown in annex A of DEF(AUST)5692 by functional areas in the following
sequence:

a. X, Cross functional requirement.

b. A, Operations and maintenance requirement.

c. B, Reliability, availability, and maintainability; failure modes, effects and criticality analysis; and,
maintainability analysis.

d. C, Task inventory, task analysis, personnel and support requirements.

e. E, Support equipment and training materiel requirements.

f. U, Unit under test requirements and description.

g. F, Facilities considerations.

h. G, Personnel skill considerations.

i. H, Packaging and provisioning requirement.

j. J, Transportability engineering analysis.

k. M, Australian Aerospace M tables

l. R, Australian Aerospace R tables.

m. V, Australian Aerospace V tables.

n. W, Australian Aerospace W tables.


DEF(AUST)5692

Functional LSAR Relational Table Listing and Table Relationships

4. Preceding the data tables for each functional area are a listing of the applicable data tables and an
illustration showing the data table relationships. The listing contains each LSAR relational table code and
title. These table codes cannot be modified when establishing/creating a relational LSAR ADP System. This
list of relational tables comprises the LSAR database. Each figure depicts the table title and code starting at
the top of the figure, table keys are migrated down to each successive level of related tables shown through
line relationships. Only additional keys are shown as you progress from top to bottom (eg., Figure 4,
contains table XB. This table has data keys End Item Acronym Code (EIAC) (migrated from table XA) and
LSA Control Number (LCN), Alternate LCN Code (ALC) and LCN-Type (listed beneath the line in the table
block)).

LSAR RELATIONAL TABLES


5. The Detailed portion of each functional area (of this Annex) contains each LSAR table, a brief description
of the table contents and business rules, and the format of the data elements. Each Table contains the
following entries:

a. Table Code

b. Table Title

c. Table Description

d. Columnar listing of the table contents

(1) DED Code

(2) Data element title or role name

(3) Data element field format

(4) DED Number

(5) Key indicator

Format

6. The general format for the relational tables is as follows:

TABLE CODE TABLE TITLE

(Description of table)

CODE DATA ELEMENT TITLE/ROLE NAME FORMAT DED KEY

Definition of Terms

7. Table Code. The three-position code, left-justified, assigned to each table in the relational LSAR used
for locating and referencing the data elements to the appropriate relational LSAR table in the DED cross-
reference index.

8. Table Title. A descriptive phrase used to identify the relational table, sufficient adjectival modifiers are
used with the phrase to ensure unique identification.

9. Table Description. A short statement outlining the contents and associated business rules of the data
table.

10. Data Element Code (CODE). A nine-position code, left justified, used to identify the DED. Each DED
Code is unique within the table in which the DED is listed. The DED Code cannot be changed or modified
when independently developing a relational LSAR ADP System. The last three positions of the code are the
table code. When a key migrates to a new table, thus becoming a foreign key, it will retain the table code

3A-2
DEF(AUST)5692

where the key originated, unless the key is required to assume a "roll name" in the new table. Origination of
foreign keys that assume roll names are defined in the business rules for the data table.

11. Data Element Title. The noun phrase name used to identify the data element. Sufficient adjectival
modifiers are used with the noun name to ensure title uniqueness.

12. Field Format. A specification for the length, type, positional justification, and decimal placement of a
data element field, or subfield thereof, as described below:

a. Length. The number of character positions in the data element. In the event the length is
variable, the maximum length is specified.

b. Type. A specification of the character type, wherein:

"A" specifies that all characters of the data entry are upper case alphabetical.

"N" specifies that all characters of the data entry are numerical.

"X" specifies that characters of the data entry are upper case alphabetical, numerical, special, or
any combination thereof.

"D" specifies that characters of the data entry are numerical with floating decimal. Decimals
may be entered as required or exponentially, e.g., "0.0000325" or "3.25E-5".

c. Justification. Specifies from which side of the field the characters of the data element are
entered. Those starting at the left are left justified (L), those starting at the right are right
justified (R). Those that always occupy the entire field are fixed (F), as shown below. A
dash (-) is used if this column is not applicable.

d. Decimal Placement. Specifies the number of character positions to the right of the assumed
decimal point when the data element is numeric in all character positions. A dash (-) is used
if this column is not applicable. AS means "As Specified" and the detailed instructions will
indicate the location of decimal points.

e. Field formats for extended narrative data fields are capable of accepting 99,999, 65-character
lines, of information by means of a text sequencing code.

13. DED Number. A sequentially assigned number to each data element in the dictionary for use in locating
and referencing it throughout the dictionary and data entry instructions (Annex E of this Book).

14. Key Data Element Code (KEY). An indicator that identifies key and mandatory data within a data table.
The indicators are "F", foreign key, "K", key, or "M", mandatory, non-identifying data element. Key data
cannot have a null value (unless specified in the business rules) when attempting to establish a data row in a
given data table.

15. Role Name. A unique modifier of a data element title that describes the use/application of the data
element within a specific relational data table location.

LSAR DATA TABLE EXCHANGE/DELIVERY


16. Depending upon contractual language, exchange/delivery of the LSAR data may take the form of full file
replacement or "change only" data (changes to the LSAR data tables since the previous submittal of the
LSAR data). Both capabilities are required of compliant LSAR Systems. Validated LSAR systems may
employ table upload edits differently; therefore, each system shall be responsible for sorting tables of
imported LSAR files as necessary to pass their table upload edits. Also, LSAR data tables shall be
exchanged/delivered via variable length ASCII file formats. All data elements shall be positioned at their
respective offsets in the table row field. The following paragraphs define the requirements to insure that
automated LSAR systems will produce and load standard outputs not only for all data tables (full file
replacement), but also standard outputs for "change only" data. Each type of transaction shall be identified
by the use of an update code (UC); multiple transactions are possible for "change only" data delivery. The
UC is not a data element within each relational table; instead, the UC appends the appropriate table row(s)
identifying the transactions that have occurred.

3A-3
DEF(AUST)5692

Full File Replacement

17. When providing an initial LSAR file delivery or a full file replacement, a UC - * must be present for the
appropriate row of Table XA. The file structure for full file replacement is as follows:

| UC | Table ID |Table Row |

18. The UC (*) identifies the type of transaction as being full file replacement or initial delivery. The Table ID
is XA in this case and the Table Row only needs the key data element (EIAC) input. Each element of the
transaction shall be contiguous and without the vertical lines shown above.

Change Only Data Delivery

19. "Change only" data delivery requires multiple types of change transactions. Each type of change
transaction is listed below with its definition and appropriate UC.

a. Add Transaction - UC - A. The Add Transaction Code identifies that the record to be loaded is
a new record to be added to the respective table. The appearance of an add implies that the
key data elements do not already exist in the table being accessed. However, those key
data elements must already exist in the prerequisite tables. The add record shall contain
required key fields and shall invoke a full record insert to specified table.

b. Delete Transaction - UC - D. The Delete Transaction Code identifies the transaction record as
a delete of an existing record pertaining to the identified key data elements. If the table is
prerequisite to another table and there is data in the other table matching on the identified
keys, this transaction shall not delete the data in the specified table. A global delete
transaction shall delete table records and associated subordinate table records with respect
to identified key data elements.

c. Element Change Transaction - UC - C. The appearance of an Element Change Transaction


Code for a given table and keys implies that data already exists and is being modified. An
Element Change Transaction shall only contain data in the key fields and the fields which are
being modified. The Element Change Transaction shall update only the specified data
element(s).

d. Element Delete Transaction - UC - X. If deletion of one or more data elements from a table is
desired, each element will contain a "D" in the first position of its respective table position.
An Element Delete Transaction shall also contain the appropriate key data for the specified
data table. The Element Delete Transaction shall delete only the specified data element(s).

e. Global Delete Transaction - UC - R. In the Global Delete Transaction, the identified key data
shall be deleted from the specified table as well as from all tables that are subordinate to the
specified table.

f. File Structure for Change Transactions A, D, C, X. and R. The following file structure shall
be used for the subject change transactions:

| UC | Table ID | Table Row |

The UC (A, D, C, X, or R) identifies the type of transaction. The Table ID is the data table
identification (i.e., XB, CA, etc). The Table Row is self explanatory for each type of transaction.
Each element of the transaction shall be contiguous and without the vertical lines shown above.

g. Key Field Change Transaction - UC - K. In the Key Field Change Transaction, the identified
key data shall be changed in the specified table as well as in all tables which are subordinate
to the specified table. If a key data element in the specified table has a foreign key
identification, the "Change To" key data element (see file structure in next paragraph) must
be established in the foreign key file (and other prerequisite files) before the change can be
implemented (e.g., changing an existing LCN to a new LCN can only be accomplished in
Table XB, where LCN is first introduced as a key data element).

3A-4
DEF(AUST)5692

h. File Structure for Change Transaction K. The following file structure shall be used for Key
Field Change Transactions:

UC Table ID Table Row "Change From" Table Row "Change To"


Key Values Key Values

20. The UC (K) identifies the transaction as a Key Field Change Transaction. The Table ID is the data
table identification. The Table Row "Change From" Key Values are the identified table key values which
exist in the table and are to be changed. The Table Row "Change To" Key Values are values to which all
applicable table keys are being changed. Each element of the transaction shall be contiguous and without
the vertical lines shown above.

21. Update Code Sort Order. The order for the incorporation of change transactions into a database is
critical and shall be dependent upon the UC. The UC sort order is R, K, D, X, A, and C.

3A-5
DEF(AUST)5692

CROSS FUNCTIONAL REQUIREMENTS


22. The following "X" data tables have attributes which cross multiple functional areas or are used as a
link to various functional data tables. Included under these tables are the functional and physical
breakdown, LCN assignment and application of UOCs, technical manual numbers, and government provided
level of repair analysis (LORA) modelling information. Figure 1 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


XA End Item Acronym Code
XB LSA Control Number Indentured Item
XC System/End Item
XD System/End Item Serial Number
XE LCN to Serial Number Usable On Code
XF LCN to System/End Item Usable On Code
XG Functional/Physical LCN Mapping
XH Commercial And Government Entity Code
XI Technical Manual Code and Number Index

3A-6
DEF(AUST)5692

Figure 1 X Table Relationships

TABLE XA, END ITEM ACRONYM CODE


23. This table contains the EIAC (EIACODXA) used to define the LSAR system documented in the relational
database. Also included in this Table are LORA modelling parameters provided by the requiring authority.
When the classical or modified classical LCN assignment is used, then the entry is required in LCN structure
(LCNSTRXA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 K
LCNSTRXA LCN STRUCTURE 18 N L - 202
ADDLTMXA ADMINISTRATIVE LEAD TIME 2NR- 014
CTDLTMXA CONTACT TEAM DELAY TIME 3NR- 052

3A-7
DEF(AUST)5692

CONTNOXA CONTRACT NUMBER 19 X L - 055


CSREORXA COST PER REORDER ACTION 4NR2 061
CSPRRQXA COST PER REQUISITION 4NR2 062
DEMILCXA DEMILITARIZATION COST 2NR- 077
DISCNTXA DISCOUNT RATE 3NR2 083
HLCSPCXA HOLDING COST PERCENTAGE 2NR- 160
ESSALVXA ESTIMATED SALVAGE VALUE 2NR- 102
INTBINXA INITIAL BIN COST 4NR- 166
INCATCXA INITIAL CATALOGUING COST 4NR- 167
INTRATXA INTEREST RATE 3NR2 173
INVSTGXA INVENTORY STORAGE SPACE COST 4NR2 176
LODFACXA LOADING FACTOR 3NR2 195
WSOPLVXA OPERATION LEVEL 2NR- 271
OPRLIFXA OPERATION LIFE 2NR- 272
PRSTOVXA PERSONNEL TURNOVER RATE/CIV 2NR- 289
PRSTOMXA PERSONNEL TURNOVER RATE/MIL 2NR- 289
PROFACXA PRODUCTIVITY FACTOR 3NR2 300
RCBINCXA RECURRING BIN COST 4NR- 333
RCCATCXA RECURRING CATALOGUING COST 4NR- 334
RESTCRXA RETAIL STOCKAGE CRITERIA 2NR- 359
SAFLVLXA SAFETY LEVEL 2NR- 363
SECSFCXA SUPPORT OF SUPPORT EQUIPMENT COST 3NR2 421
FACTOR
TRNCSTXA TRANSPORTATION COST 4NR2 466
WSTYAQXA TYPE ACQUISITION 1AF- 478
TSSCODXA TYPE OF SUPPLY SYSTEM CODE 1AF- 484

TABLE XB, LSA CONTROL NUMBER INDENTURED ITEM


24. This table contains all LCNs and information about the indentured location of the LCN in the
hardware/functional configuration of the system/equipment. Table keys include: EIAC (EIACODXA); LCN
(LSACONXB); ALC (ALTLCNXB); and LCN Type (LCNTYPXB).

a. If LCN Structure (LCNSTRXA) from Table XA (LCNSTRXA) is blank, LCN Indenture Code
(LCNINDXB) is mandatory.

b. If LCN Structure is not blank, the LCN (LSACONXB) must match an indenture level length
specified by the LCN structure, or be a greater length than the total of all LCN Structure
indenture, levels, e.g., if the LCN Structure is "12233", an LCN must either be 1,3,5,8,11 or
greater than 11 positions. If the LCN is greater than 11 positions, the LCN Indenture Code
becomes mandatory.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LOGISTIC SUPPORT ANALYSIS CONTROL 18 X L - 199 K
NUMBER (LCN)
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 K
LCNTYPXB LCN TYPE 1AF- 203 K
LCNINDXB LCN INDENTURE CODE (LCN-IC) 1AF- 200
LCNAMEXB LCN NOMENCLATURE 19 X L - 201
TMFGCDXB TECHNICAL MANUAL FUNCTIONAL GROUP 11 X L - 438
CODE (MAINTENANCE ALLOCATION CHART)
SYSIDNXB SYSTEM/END ITEM IDENTIFIER 1AF- 423
SECITMXB SECTIONALIZED ITEM TRANSPORTATION 1AF- 367
INDICATOR
RAMINDXB RELIABILITY AVAILABILITY MAINTAINABILITY 1AF- 342
INDICATOR

3A-8
DEF(AUST)5692

TABLE XC, SYSTEM/END ITEM


25. This table contains only those LCNs representing a system/End Item (EI) or "A" indenture coded item. A
system/EI is an item capable of independent operation for its intended use, e.g., rifle, radio receiver, or is a
class or group of equipment that is managed and provisioned under a separate Provisioning Contract Control
Number (PCCN). Table keys include: EIAC (EIACODXA); LCN (LSACONXB); ALC (ALTLCNXB); and, LCN
Type (LCNTYPXB).

a. The System/EI Identifier (SYSIDNXB) of "S" or "E" identifies LCNs as representing System/EIs
from table XB for entry into this table.

b. For identical PCCNs (PCCNUMXC), the UOCs (UOCSEIXC) must be different.

c. All alternate assemblies of the same LCN must have the same PCCN.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
UOCSEIXC USABLE ON CODE (UOC) 3XL- 501 M
PCCNUMXC SYSTEM/EI PROVISIONING CONTRACT 6XF- 307 M
CONTROL NUMBER
ITMDESXC SYSTEM/EI ITEM DESIGNATOR CODE 26 X L - 179
PLISNOXC SYSTEM/EI PROVISIONING LIST ITEM 5XL- 309
SEQUENCE NUMBER
TOCCODXC SYSTEM/EI TYPE OF CHANGE CODE 1AF- 481
QTYASYXC SYSTEM/EI QUANTITY PER ASSEMBLY 4X-- 316
QTYPEIXC SYSTEM/EI QUANTITY PER END ITEM 5X-- 317
TRASEIXC TRANSPORTATION END ITEM INDICATOR 1AF- 467

TABLE XD, SYSTEM/END ITEM SERIAL NUMBER


26. This table is only used when parts configuration control is managed by serial numbers (S/N) of a
System/EI. It contains Serial Numbers applicable to a System/End Item, and if required, Serial Number UOC
assignments, e.g., for model V10, identified in table XC, applicable serial numbers may be 110 through 118,
121 and 125-130, while for model V10A, also identified in table XC, the applicable serial numbers may be
119, 122-124, and 131-150. For these serial number(s) specific serial number UOCs may be assigned as
follows:

Model Serial Number UOC Serial Number(s)


(ITMDESXC) (SNUUOCXD) (FRSNUMXD)(TOSNUMXD)

V10 A 110 – 118


V10 B 121 – 121
V10 C 125 – 130
V10A D 119 – 119
V10A E 122 – 124
V10A F 131 - 150

a. S/N From (FRSNUMXD) must be less than or equal to S/N To (TOSNUMXD).

b. S/N UOCs must be different for all EIAC, LCN, ALC and LCN Type combinations within the
same PCCN (pulled from Table XC for subject keys).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F

3A-9
DEF(AUST)5692

FRSNUMXD SERIAL NUMBER FROM 10 X L - 373 K


TOSNUMXD SERIAL NUMBER TO 10 X L - 373 K
SNUUOCXD SERIAL NUMBER USABLE ON CODE 3AL- 375 M

TABLE XE, LCN TO SERIAL NUMBER USABLE ON CODE


27. This table contains LCN and system/EI S/N LCNs in order to determine the associated S/N and S/N
UOCs for the LCN. Table keys include all columns.

a. Table keys LSACONXE, ALTLCNXE, and LCNTYPXE migrate from table XB. Table keys
LCNSEIXE, ALCSEIXE, and LTYSEIXE migrate from table XD. EIACODXA is identical for
keys from tables XB and XD for a given row of data.

b. Rows of information from this table with LCNTYPXE and LTYSEIXE of "P" must match entries
in table HN, when Table HN is established.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXE S/N ITEM LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXE S/N ITEM ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXE S/N ITEM LCN TYPE 1AF- 203 F
LCNSEIXE S/N SYSTEM/EI LCN 18 X L - 199 F
ALCSEIXE S/N SYSTEM/EI ALC 2NF- 019 F
LTYSEIXE S/N SYSTEM/EI LCN TYPE 1AF- 203 F
FRSNUMXE S/N SERIAL NUMBER FROM 10 X L - 373 F
TOSNUMXE S/N SERIAL NUMBER TO 10 X L - 373 F

TABLE XF, LCN TO SYSTEM/END ITEM USABLE ON CODE


28. This table contains LCNs and System/EI LCNs in order to determine the associated UOC for the LCN.
This table and table HO (for provisioning) are critical to qualify an LCN for report requests when a specific
UOC is required for report selection. Table keys include all columns.

a. Table keys LSACONXF, ALTLCNXF, and LCNTYPXF originate in table XB. Table keys
LCNSEIXF, ALCSEIXF, and LTYSEIXF migrate from table XC. EIACODXA is identical for
keys from tables XB and XC for a given row of data.

b. Rows of information from this Table with LCNTYPXF and LTYSEIXF of "P" must match entries
in table HO, when this table is established.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXF UOC ITEM LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXF UOC ITEM ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXF UOC ITEM LCN TYPE 1AF- 203 F
LCNSEIXF UOC SYSTEM/EI LCN 18 X L - 199 F
ALCSEIXF UOC SYSTEM/EI ALC 2NF- 019 F
LTYSEIXF UOC SYSTEM/EI LCN TYPE 1AF- 203 F

TABLE XG, FUNCTIONAL/PHYSICAL LCN MAPPING


29. This table contains a cross-listing of functional/physical LCNs. All data, except EIACODXA, originate in
table XB. EIACODXA is identical for all keys and mandatory data elements across a given row of data.
Physical LCN Type must always be "P"; Functional LCN Type must always be "F". When a functional and
physical LCN are mapped through this table, all data contained against the functional LCN shall migrate to

3A-10
DEF(AUST)5692

the physical LCN (physical LCN data shall take precedence if data duplication has occurred). After the data
is migrated, data additions and updates for this item shall only occur against the physical LCN.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
PLSACNXG PHYSICAL LSA CONTROL NUMBER (LCN) 18 X L - 199 F
PALCNCXG PHYSICAL ALTERNATE LCN CODE 2NF- 019 F
PLCNTYXG PHYSICAL LCN TYPE 1AF- 203 F
FLSACNXG FUNCTIONAL LSA CONTROL NUMBER 18 X L - 199 M
FALCNCXG FUNCTIONAL ALTERNATE LCN CODE 2NF- 019 M
FLCNTYXG FUNCTIONAL LCN TYPE 1AF- 203 M

TABLE XH, COMMERCIAL AND GOVERNMENT ENTITY CODE


30. This table contains all Commercial and Government Entity (CAGE) codes and the CAGE addresses. A
CAGE Street (CASTREXH), city (CACITYXH), state (CASTATXH), nation (CANATNXH), or postal zone
(CAPOZOXH) cannot be included without a CAGE name (CANAMEXH).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH COMMERCIAL AND GOVERNMENT ENTITY 5XF- 046 K
(CAGE) CODE
CANAMEXH CAGE NAME 25 X L - 047
CASTREXH CAGE STREET 25 X L - 047
CACITYXH CAGE CITY 20 X L - 047
CASTATXH CAGE STATE 2AF- 047
CANATNXH CAGE NATION 20 X L - 047
CAPOZOXH CAGE POSTAL ZONE 10 X L - 047

TABLE XI, TECHNICAL MANUAL CODE AND NUMBER INDEX


31. This table contains a cross-reference of TM code to TM number(s). Table keys include both columns.

CODE DATA ELEMENT TITLE FORMAT DED KEY


TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437 K
TMNUMBXI TECHNICAL MANUAL NUMBER 30 X L - 440 K

3A-11
DEF(AUST)5692

OPERATIONS AND MAINTENANCE REQUIREMENTS


32. Data tables beginning with "A" in the first position of the table code are structured to consolidate
information related to the anticipated operation of the system, environment in which the system will be
operated and maintained, and maintenance requirements of the system which must be met. This information
is prepared for the system and for each subsystem for which maintenance requirements are to be imposed.
Figure 2 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


AA Operations and Maintenance Requirement
AB War/Peace Operations and Maintenance Requirement
AC Maintenance Level Requirement
AD Organizational Level Requirement
AE Skill Operations and Maintenance Requirement
AF War/Peace Additional Requirements Narrative
AG Reliability Requirement
AH Interoperability Requirement
AI Modelling Data
AJ Operations And Maintenance Shipping Requirement
AK System/End Item Narrative

3A-12
DEF(AUST)5692

Figure 2 A Table Relationships

TABLE AA, OPERATIONS AND MAINTENANCE REQUIREMENT


33. This table identifies operations, maintenance, and reliability requirements for the new system/equipment
by the service designator code. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC
(ALTLCNXB), LCN Type (LCNTYPXB), and Service Designator Code (SERDESAA). For a given row of
information, Percentile (PERCENAA) is not allowed without a Maximum Time To Repair (MAXTTRAA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SERDESAA SERVICE DESIGNATOR CODE 1AF- 376 K

3A-13
DEF(AUST)5692

MAXTTRAA REQUIRED MAXIMUM TIME TO REPAIR 5NR2 222


PERCENAA REQUIRED PERCENTILE 2NF- 286
ACHAVAAA REQUIRED ACHIEVED AVAILABILITY 8NR6 001
INHAVAAA REQUIRED INHERENT AVAILABILITY 8NR6 164
OMAMDTAA OPERATIONAL MEAN ACTIVE MAINTENANCE 6NR1 223
DOWNTIME
TMAMDTAA TECHNICAL MEAN ACTIVE MAINTENANCE 6NR1 223
DOWNTIME
OPMTTRAA REQUIRED OPERATIONAL MEAN TIME TO 5NR2 236
REPAIR
TEMTTRAA REQUIRED TECHNICAL MEAN TIME TO 5NR2 236
REPAIR
NUOPLOAA NUMBER OF OPERATING LOCATIONS 4NR- 262
CREWSZAA CREW SIZE 4NR- 064
TOSYSUAA TOTAL SYSTEMS SUPPORTED 6NR- 454
RCMLOGAA RELIABILITY CENTERED MAINTENANCE 32 X - - 345
LOGIC UTILIZED

TABLE AB, WAR/PEACE OPERATIONS AND MAINTENANCE REQUIREMENT


34. This table identifies O/M requirements for the new system/equipment based on its projected wartime and
peacetime missions for a given service designator code. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Service Designator Code (SERDESAA), and
Operational Requirement Indicator (OPRQINAB). For a given row, Mean Mission Duration (MMISDUAB)
and Mean Mission Duration Measurement Base (MMISDMAB) must either both be blank, or have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SERDESAA SERVICE DESIGNATOR CODE 1AF- 376 F
OPRQINAB OPERATIONAL REQUIREMENT INDICATOR 1AF- 275 K
ANNOMIAB ANNUAL NUMBER OF MISSIONS 6NR- 021
ANOPDAAB ANNUAL OPERATING DAYS 3NR- 022
ANOPTIAB ANNUAL OPERATING TIME 4NR- 024
MMISDUAB MEAN MISSION DURATION 6NR1 228
MMISDMAB MEAN MISSION DURATION MEASUREMENT 1AF- 238
BASE
OPAVAIAB REQUIRED OPERATIONAL AVAILABILITY 8NR6 273
OPALDTAB REQUIRED ADMINISTRATIVE AND LOGISTIC 3NR- 013
DELAY TIME
OSTBTIAB REQUIRED STANDBY TIME 4NR- 403

TABLE AC, MAINTENANCE LEVEL REQUIREMENT


35. This table identifies O/M requirements for the new system/equipment by O/M level, wartime/peacetime
scenario, and service designator code. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC
(ALTLCNXB), LCN Type (LCNTYPXB), Service Designator Code (SERDESAA), Operational Requirement
Indicator (OPRQINAB), and O/M Level Code (OMLVLCAC). For a given row, Maintenance Level Percentile
(MLPERCAC) is not allowed without a Maintenance Level Maximum Time to Repair (MLMTTRAC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SERDESAA SERVICE DESIGNATOR CODE 1AF- 376 F

3A-14
DEF(AUST)5692

OPRQINAB OPERATIONAL REQUIREMENT INDICATOR 1AF- 275 F


OMLVLCAC OPERATIONS AND MAINTENANCE LEVEL 1AF- 277 K
CODE
MLMTTRAC MAINTENANCE LEVEL MAXIMUM TIME TO 5NR2 222
REPAIR
MLPERCAC MAINTENANCE LEVEL PERCENTILE 2NF- 286
MLNSSUAC NUMBER OF SYSTEMS SUPPORTED 6NR- 265
MLSAMHAC MAINTENANCE LEVEL SCHEDULED ANNUAL 6NR1 020
MAN-HOURS
MLUAMHAC MAINTENANCE LEVEL UNSCHEDULED 6NR1 020
ANNUAL MAN-HOURS
MLSMHOAC SCHEDULED MAN-HOUR PER OPERATING 8NR5 215
HOUR
MLUMHOAC UNSCHEDULED MAN-HOUR PER OPERATING 8NR5 215
HOUR
MLUMETAC UNSCHEDULED MAINTENANCE MEAN 5NR2 499
ELAPSED TIME
MLUMMHAC UNSCHEDULED MAINTENANCE MEAN MAN- 5NR2 499
HOURS

TABLE AD, ORGANIZATIONAL LEVEL REQUIREMENT


36. This table identifies organizational O/M level requirements for the new system/equipment by
wartime/peacetime scenario, O/M level, and service designator code. Table keys consist of EIAC
(EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Service Designator Code
(SERDESAA), Operational Requirement Indicator (OPRQINAB), and O/M Level Code (OMLVLCAC). For a
given row, only "C" and "O" for the O/M Level Code (OMLVLCAC) are allowed for this table.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SERDESAA SERVICE DESIGNATOR CODE 1AF- 376 F
OPRQINAB OPERATIONAL REQUIREMENT INDICATOR 1AF- 275 F
OMLVLCAC OPERATIONS AND MAINTENANCE LEVEL 1AF- 277 F
CODE
DINMETAD DAILY INSPECTION MEAN ELAPSED TIME 5NR2 280
DINMMHAD DAILY INSPECTION MEAN MAN-HOURS 5NR2 280
PREMETAD PRE-OPERATIVE INSPECTION MEAN 5NR2 280
ELAPSED TIME
PREMMHAD PRE-OPERATIVE INSPECTION MEAN MAN- 5NR2 280
HOURS
POIMETAD POSTOPERATIVE INSPECTION MEAN 5NR2 280
ELAPSED TIME
POIMMHAD POSTOPERATIVE INSPECTION MEAN MAN- 5NR2 280
HOURS
PINMETAD PERIODIC INSPECTION MEAN ELAPSED TIME 5 N R 2 280
PINMMHAD PERIODIC INSPECTION MEAN MAN-HOURS 5NR2 280
MPCMETAD MISSION PROFILE CHANGE MEAN ELAPSED 5 N R 2 280
TIME
MPCMMHAD MISSION PROFILE CHANGE MEAN MAN- 5NR2 280
HOURS
TINMETAD TURNROUND INSPECTION MEAN ELAPSED 5NR2 280
TIME
TINMMHAD TURNROUND INSPECTION MEAN MAN-HOURS5 N R 2 280

3A-15
DEF(AUST)5692

TABLE AE, SKILL OPERATIONS AND MAINTENANCE REQUIREMENT


37. This table identifies operational maintenance manpower constraints by SSC at specific O/M levels given
a wartime/peacetime scenario and service designator code. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Service Designator Code (SERDESAA),
Operational Requirement Indicator (OPRQINAB), O/M Level Code (OMLVLCAC), and SSC (SKSPCDGA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SERDESAA SERVICE DESIGNATOR CODE 1AF- 376 F
OPRQINAB OPERATIONAL REQUIREMENT INDICATOR 1AF- 275 F
OMLVLCAC OPERATIONS AND MAINTENANCE LEVEL 1AF- 277 F
CODE
SKSPCDGA SKILL SPECIALTY CODE 7XL- 387 F
AVAIMHAE AVAILABLE MAN-HOUR 6NR- 028
QTYAVAAE AVAILABLE QUANTITY 5NR- 324
UTRATIAE UTILIZATION RATIO 3NR2 503

TABLE AF, WAR/PEACE ADDITIONAL REQUIREMENTS NARRATIVE


38. This is a narrative table which identifies the additional O/M level requirements for the new
system/equipment by wartime/peacetime and service designator code. Table keys consist of EIAC
(EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Service Designator Code
(SERDESAA), Operational Requirement Indicator (OPRQINAB), and Additional Requirements Text
Sequencing Code (TEXSEQAF).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SERDESAA SERVICE DESIGNATOR CODE 1AF- 376 F
OPRQINAB OPERATIONAL REQUIREMENT INDICATOR 1AF- 275 F
TEXSEQAF ADDITIONAL REQUIREMENTS TEXT 5NR- 450 K
SEQUENCING CODE
WPADDRAF ADDITIONAL REQUIREMENTS 65 X - - 009

TABLE AG, RELIABILITY REQUIREMENT


39. This table identifies reliability requirement parameters for the new system/equipment that are dependent
on measurement base (MB). There can be multiple tables depending upon the annual operating
requirements (AOR) MB. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB),
LCN Type (LCNTYPXB), and AOR MB (MEASBSAG). For a given row of information, the following cross-
element edits apply to table AG:

a. AOR (ANOPREAG) and AOR MB (MEASBSAG) must either both be blank, or have entries.

b. Reliability Operational Requirements Indicator (OPRQINAG) must match Operational


Requirements Indicator (OPRQINAB) in Table AB for the given keys. The keys consist of
EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), and LCN Type (LCNTYPXB).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F

3A-16
DEF(AUST)5692

ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F


LCNTYPXB LCN TYPE 1AF- 203 F
MEASBSAG ANNUAL OPERATING REQUIREMENT 1AF- 238 K
MEASUREMENT BASE
ANOPREAG ANNUAL OPERATING REQUIREMENT 6NR- 023 M
OPRQINAG RELIABILITY OPERATIONAL REQUIREMENTS 1 A F - 275 M
INDICATOR
OPMTBFAG REQUIRED OPERATIONAL MEAN TIME 10 D - - 229
BETWEEN FAILURES
TEMTBFAG REQUIRED TECHNICAL MEAN TIME BETWEEN 10 D - - 229
FAILURES
OPMRBMAG REQUIRED OPERATIONAL MEAN TIME 10 D - - 230
BETWEEN MAINTENANCE ACTIONS
TMTBMAAG REQUIRED TECHNICAL MEAN TIME BETWEEN 10 D - - 230
MAINTENANCE ACTIONS
MTBRXXAG REQUIRED MEAN TIME BETWEEN REMOVALS 10 D - - 235

TABLE AH, INTEROPERABILITY REQUIREMENT


40. This table identifies item name, national stock number (NSN), and the TM of the system/equipment with
which the new system/equipment must be able to be transported by/interoperate with. Table keys consist of
EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Interoperable Item
Name (IONAMEAH), and Interoperable Item Number Type (IOINTYAH). For a given row of information, the
following cross-element edits apply to table AH :

a. Interoperable CAGE Number (IOCAGEAH) and Interoperable Reference Number (IOREFNAH)


must either both be blank, or both have entries.

b. Interoperable Item National Item Identification Number (IONIINAH) and Interoperable Item NSN
Federal Supply Classification (IONFSCAH) must either both be blank, or both have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
IONAMEAH INTEROPERABLE ITEM NAME 19 X L - 182 K
IOINTYAH INTEROPERABLE ITEM NUMBER TYPE 1AF- 266 K
IOCAGEAH INTEROPERABLE CAGE CODE 5XF- 046
IOREFNAH INTEROPERABLE REFERENCE NUMBER 32 X L - 337
IONIINAH INTEROPERABLE ITEM NATIONAL ITEM 9XF- 253
IDENTIFICATION NUMBER
IONFSCAH INTEROPERABLE ITEM NSN FEDERAL 4NF- 253
SUPPLY CLASSIFICATION
IOITNMAH INTEROPERABLE ITEM TECHNICAL MANUAL 30 X L - 440
NUMBER

TABLE AI, MODELLING DATA


41. This table documents maintenance level specific information, for a given service designator code, to be
used for LSA modelling. Table keys consist of EIAC (EIACODXA), Modelling Service Designator Code
(SERDESAI), and Modelling O/M Level Code (OMLVLCAI).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
SERDESAI MODELLING SERVICE DESIGNATOR CODE 1AF- 376 K
OMLVLCAI MODELLING OPERATIONS AND 1AF- 277 K
MAINTENANCE LEVEL CODE

3A-17
DEF(AUST)5692

LABRATAI LABOUR RATE 4NR2 189


NOSHPSAI NUMBER OF SHOPS 2NR- 263
RPWSCSAI REPAIR WORK SPACE COST 4NR2 352
RQDSTKAI REQUIRED DAYS OF STOCK 3NR- 357

TABLE AJ, OPERATIONS AND MAINTENANCE SHIPPING REQUIREMENT


42. This table identifies the O/M level from which a spare/repair part is shipped and the O/M level which
receives the part. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN
Type (LCNTYPXB), O/M Level From (OMLVLFAJ), O/M Level To (OMLVLTAJ).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
OMLVLFAJ OPERATIONS AND MAINTENANCE LEVEL 1AF- 277 K
FROM
OMLVLTAJ OPERATIONS AND MAINTENANCE LEVEL TO 1AF- 277 K
SHPDISAJ SHIP DISTANCE 4NR- 085
TIMESHAJ SHIP TIME 3NR- 379

TABLE AK, SYSTEM/END ITEM NARRATIVE


43. This table may be used to identify Additional Supportability Considerations, Additional Supportability
Parameters, and Operational Mission Failure Definition. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), System/EI Narrative Code (SEINCDAK), and
System/EI Narrative Text Sequencing Code (TEXSEQAK).

a. If the System/EI Narrative Code (SEINCDAK) is (B), then this table provides a narrative
description of additional supportability considerations for the item under analysis (Additional
Supportability Considerations, DED 010).

b. If the System/EI Narrative Code (SEINCDAK) is (A), then this table describes additional
supportability parameters which will specify data elements and associated data when
discrete fields are not provided (Additional Supportability Parameters, DED 011).

c. If the System/EI Narrative Code (SEINCDAK) is (C), then this table provides a narrative of the
guidelines to be followed when defining operational mission failures (Operational Mission
Failure Definition, DED 274).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SEINCDAK SYSTEM/END ITEM NARRATIVE CODE 1AF- 424 K
TEXSEQAK SYSTEM END ITEM NARRATIVE TEXT 5NR- 450 K
SEQENCING CODE
SEINARAK SYSTEM END ITEM NARRATIVE 65 X - - ---

3A-18
DEF(AUST)5692

ITEM RELIABILITY, AVAILABILITY AND MAINTAINABILITY CHARACTERISTICS;


FAILURE MODE EFFECTS AND CRITICALITY ANALYSIS; AND MAINTAINABILITY
ANALYSIS
44. Data tables beginning with "B" in the first position of the table code are structured to provide a
description of the function of each item of the end item; outline the maintenance concept to be utilized for
design and support planning purposes; and, identify any design conditions such as fail safe
requirements/environmental or nuclear hardness considerations imposed upon the system. The tables
summarize the item reliability, maintainability, and related availability characteristics of the item resulting from
the failure modes and effects, criticality, and maintainability analyses, and accommodate a narrative
description of any analysis related to the potential redesign of an item. Figure 3 depicts the data relationships
for these tables.

TABLE CODE TABLE TITLE


BA Reliability, Availability, and Maintainability Characteristics
BB Reliability, Availability, and Maintainability Characteristics Narrative
BC Reliability, Availability, and Maintainability Logistics Considerations
BD Reliability, Availability, and Maintainability Indicator Characteristics
BE War/Peace Reliability, Availability, and Maintainability Indicator Characteristics
BF Failure Mode and Reliability Centered Maintenance Analysis
BG Failure Mode and Reliability Centered Maintenance Narrative
BH Failure Mode Task
BI Failure Mode Indicator Mission Phase Code Characteristics
BJ Failure Mode Indicator Mission Phase Code Characteristics Narrative
BK Reliability, Availability, and Maintainability Criticality
BL Mission Phase Operational Mode

3A-19
DEF(AUST)5692

Figure 3 B Table Relationships

TABLE BA, RELIABILITY, AVAILABILITY, AND MAINTAINABILITY


CHARACTERISTICS
45. This table contains logistics considerations, maintenance, and reliability characteristics of the item under
analysis. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), and LCN Type
(LCNTYPXB). For a given row of information, the following cross-element edits apply to table BA :

a. The RAM area can only be used if a (Y) is entered in the RAM Indicator (RAMINDXB) Table XB.

b. Fault Isolation Percent Failure Group 1 (FIPFGABA) is not allowed without Fault Isolation
Ambiguity Group 1 (FIAMBABA).

3A-20
DEF(AUST)5692

c. The combination in (b) is not allowed without Built in Test (BIT) Detection Level Percent group 1
(BDLPGABA).

d. That which applies for the combinations in Group 1 (b, c) also applies to the combination in
group 2.

e. Wearout Life (WEOULIBA) and Wearout Life MB (WOLIMBBA) must either both be blank, or
have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
MEQLINBA MINIMUM EQUIPMENT LIST INDICATOR 1AF- 243
CONVFABA CONVERSION FACTOR 5N-- 059
FIAMBABA FAULT ISOLATION AMBIGUITY GROUP 1 2NR- 143
FIPFGABA FAULT ISOLATION PERCENT FAILURE GROUP 3 N R 1 143
1
BDLPGABA BUILT IN TEST DETECTABILITY LEVEL 2NR- 032
PERCENTAGE PER GROUP 1
FIAMBBBA FAULT ISOLATION AMBIGUITY GROUP 2 2NR- 143
FIPFGBBA FAULT ISOLATION PERCENT FAILURE GROUP 3 N R 1 143
2
BDLPGBBA BUILT IN TEST DETECTABILITY LEVEL 2NR- 032
PERCENTAGE PER GROUP 2
BITNDPBA BUILT-IN-TEST CANNOT DUPLICATE 2NR- 031
PERCENTAGE
BITROPBA BUILT-IN-TEST RETEST OK PERCENT 2NR- 033
FRDATABA FAILURE RATE DATA SOURCE 32 X L - 141
PREOVCBA PILOT REWORK OVERHAUL CANDIDATE 1AF- 292
SECCLEBA SECURITY CLEARANCE 1NF- 369
SUPCONBA SUPPORT CONCEPT 1AF- 410
WEOULIBA WEAROUT LIFE 6NR- 505
WOLIMBBA WEAROUT LIFE MEASUREMENT BASE 1AF- 238
LOGSTABA LOGISTIC CONSIDERATIONS 1AF- 196
STANDARDIZATION
LOGACCBA LOGISTIC CONSIDERATIONS ACCESSIBILITY 1 A F - 196
LOGMAIBA LOGISTIC CONSIDERATIONS MAINTENANCE 1 A F - 196
EASE
LOGSAFBA LOGISTIC CONSIDERATIONS SAFETY 1AF- 196
LOGTEPBA LOGISTIC CONSIDERATIONS TEST POINTS 1AF- 196
LOGSKIBA LOGISTIC CONSIDERATIONS SKILLS 1AF- 196
LOGTRABA LOGISTIC CONSIDERATIONS TRAINING 1AF- 196
LOGCONBA LOGISTIC CONSIDERATIONS CONNECTORS 1 A F - 196
LOGPATBA LOGISTIC CONSIDERATIONS PACKAGING 1AF- 196
AND TRANSPORTATION
LOGFLOBA LOGISTIC CONSIDERATIONS FAULT 1AF- 196
LOCATION
LOGLABBA LOGISTIC CONSIDERATIONS LABELING 1AF- 196
LOGDSPBA LOGISTIC CONSIDERATIONS DESIGN FOR 1AF- 196
SELF PROTECTION
LOGCRCBA LOGISTIC CONSIDERATIONS 1AF- 196
CORROSION/RUST CONTROL

TABLE BB, RELIABILITY, AVAILABILITY, AND MAINTAINABILITY


CHARACTERISTICS NARRATIVE
46. This table may be used to identify RAM Item Functions, RAM Maintenance Concepts, RAM Minimum
Equipment List, and RAM Qualitative and Quantitative Maintainability Requirements. Table keys consist of
EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), RAM Characteristics

3A-21
DEF(AUST)5692

Narrative Code (RAMCNABB), and RAM Narrative Text Sequencing Code (TEXSEQBB). For a given row of
information, the following cross-element edits apply to Table BB :

a. If the RAM Characteristics Narrative Code (RAMCNABB) is (A), then this table identifies the
function, specification, and tolerances of the item under analysis (RAM Item Function, DED
180).

b. If the RAM Characteristics Narrative Code (RAMCNABB) is (B), then this table describes the
broad, planned approach to be employed in sustaining the system/equipment at a defined
level of readiness, or in a specified condition in support of the operational requirement (RAM
Maintenance Concept, DED 207).

c. If the RAM Characteristics Narrative Code (RAMCNABB) is (C), then this table specifies any
limitations on the end item when dispatched on its assigned mission with the item under
analysis inoperative (RAM Minimum Equipment List Narrative, DED 244). RAM Minimum
Equipment List Narrative (MEQLNABB) is not allowed without a (y) selected in Table BA for
the attribute RAM Minimum Equipment List Indicator (MEQLINBA).

d. If the RAM Characteristics Narrative Code (RAMCNABB) is (D), then this table describes the
maintainability design constraints and characteristics that must be considered during the
design process, to include fail safe requirements, environmental considerations, and nuclear
hardened characteristics (RAM Qualitative and Quantitative Maintainability Requirements,
DED 315).

e. If the RAM Characteristics Narrative Code (RAMCNABB) is (E), then this table describes the
support data and analysis used in preparation of the maintenance plan (Maintenance Plan
Rationale, DED 210).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
RAMCNABB RAM CHARACTERISTICS NARRATIVE CODE 1AF- 341 K
TEXSEQBB RAM CHARACTERISTICS NARRATIVE TEXT 5NR- 450 K
SEQUENCING CODE
RAMNARBB RAM CHARACTERISTICS NARRATIVE 65 X - - ---

TABLE BC, RELIABILITY, AVAILABILITY, AND MAINTAINABILITY LOGISTICS


CONSIDERATIONS
47. This table contains narrative information associated with logistics considerations. Table keys consist of
EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Logistics Consideration
Code (LOCOCOBC), and RAM Logistics Considerations Text Sequencing Code (TEXSEQBC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
LOCOCOBC LOGISTICS CONSIDERATION CODE 1XF- 425 K
TEXSEQBC RAM LOGISTICS CONSIDERATIONS TEXT 5NR- 450 K
SEQUENCING CODE
LOGNARBC RAM LOGISTICS CONSIDERATIONS 65 X - - 426

3A-22
DEF(AUST)5692

TABLE BD, RELIABILITY, AVAILABILITY, AND MAINTAINABILITY INDICATOR


CHARACTERISTICS
48. This table contains reliability and maintainability characteristics of the item under analysis categorized by
comparative analysis, allocated, predicted, or measured values. Table keys consist of EIAC (EIACODXA),
LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and RAM Indicator Code (RAMINDBD).
For a given LCN, ALC, and LCN Type combination, each different measurement base must remain constant
for all RAM Indicator Codes (RAMINDBD). For a given row of information, the following cross-element edits
apply to Table BD :

a. Failure Rate (FAILRTBD) and Failure Rate MB (FARAMBBD) must either both be blank, or
have entries.

b. Percentile (PERCENBD) is not allowed without a Maximum Time To Repair (MAXTTRBD).

c. Mean Time Between Failures Operational (OPMTBFBD) and Mean Time Between Failures
Operational MB (OMTBFMBD) must either both be blank, or have entries.

d. Mean Time Between Failures Technical (TEMTBFBD) and Mean Time Between Failures
Technical MB (TMTBFMBD) must either both be blank, or have entries.

e. Mean Time Between Maintenance Actions Operational (OMTBMABD) and Mean Time Between
Maintenance Actions Operational MB (OMTBMMBD) must either both be blank, or have
entries.

f. Mean Time Between Maintenance Actions Technical (TMTBMABD) and Mean Time Between
Maintenance Actions Technical MB (TMTBMMBD) must either both be blank, or have
entries.

g. Mean Time Between Maintenance Induced (INMTBMBD) and Mean Time Between
Maintenance Induced MB (IMTBMMBD) must either both be blank, or have entries.

h. Mean Time Between Maintenance Inherent (INHMTBBD) and Mean Time Between
Maintenance Inherent MB (INHMTMBD) must either both be blank, or have entries.

i. Mean Time Between Maintenance No Defect (NOMTBMBD) and Mean Time Between
Maintenance No Defect MB (NMTBMMBD) must either both be blank, or have entries.

j. Mean Time Between Preventive Maintenance (MTBMPVBD) and Mean Time Between
Preventive Maintenance MB (MTBMPMBD) must either both be blank, or have entries.

k. Mean Time Between Removals (MTBRXXBD) and Mean Time Between Removals MB
(MTBRMBBD) must either both be blank, or have entries.

l. Achieved Availability shall be calculated based on Mean Time Between Failure Technical (Table
BD), Mean Time Between Maintenance - No Defect (Table BD), Mean Time Between
Preventive Maintenance (Table BD), Elapsed Time (Table CA), and Task Frequency (CA).
A change in any of these variables shall result in an update of the Achieved Availability
(Table BD).

m. Inherent Availability shall be calculated based on Mean Time Between Failures Technical (Table
BD) and Mean Time To Repair Technical (Table BD). A change in any of these variables
shall result in an update of the Inherent Availability (Table BD).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
RAMINDBD RAM INDICATOR CODE 1AF- 347 K
ACHAVABD ACHIEVED AVAILABILITY 8NR6 001
INHAVABD INHERENT AVAILABILITY 8NR6 164

3A-23
DEF(AUST)5692

FAILRTBD FAILURE RATE 10 D - - 140


FARAMBBD FAILURE RATE MEASUREMENT BASE 1AF- 238
INHMAFBD INHERENT MAINTENANCE FACTOR 2NR1 165
MAXTTRBD MAXIMUM TIME TO REPAIR (MAXTTR) 5NR2 222
PERCENBD PERCENTILE 2NF- 286
MTTROPBD MEAN TIME TO REPAIR OPERATIONAL 5NR2 236
MTTRTHBD MEAN TIME TO REPAIR TECHNICAL 5NR2 236
OPMTBFBD MEAN TIME BETWEEN FAILURES 10 D - - 229
OPERATIONAL
OMTBFMBD MEAN TIME BETWEEN FAILURES 1AF- 238
OPERATIONAL MEASUREMENT BASE
TEMTBFBD MEAN TIME BETWEEN FAILURES TECHNICAL 10 D - - 229
TMTBFMBD MEAN TIME BETWEEN FAILURES TECHNICAL 1AF- 238
MEASUREMENT BASE
OMTBMABD MEAN TIME BETWEEN MAINTENANCE 10 D - - 230
ACTIONS (MTBMA) OPERATIONAL
OMTBMMBD MTBMA OPERATIONAL MEASUREMENT BASE 1AF- 238
TMTBMABD MTBMA TECHNICAL 10 D - - 230
TMTBMMBD MTBMA TECHNICAL MEASUREMENT BASE 1AF- 238
INMTBMBD MEAN TIME BETWEEN MAINTENANCE 10 D - - 231
INDUCED
IMTBMMBD MEAN TIME BETWEEN MAINTENANCE 1AF- 238
INDUCED MEASUREMENT BASE
INHMTBBD MEAN TIME BETWEEN MAINTENANCE 10 D - - 232
INHERENT (MTBM INHERENT)
INHMTMBD MEAN TIME BETWEEN MAINTENANCE 1AF- 238
INHERENT MEASUREMENT BASE
NOMTBMBD MEAN TIME BETWEEN MAINTENANCE NO 10 D - - 233
DEFECT
NMTBMMBD MEAN TIME BETWEEN MAINTENANCE NO 1AF- 238
DEFECT MEASUREMENT BASE
MTBMPVBD MEAN TIME BETWEEN PREVENTIVE 10 D - - 234
MAINTENANCE
MTBMPMBD MEAN TIME BETWEEN PREVENTIVE 1AF- 238
MAINTENANCE MEASUREMENT BASE
MTBRXXBD MEAN TIME BETWEEN REMOVALS (MTBR) 10 D - - 235
MTBRMBBD MEAN TIME BETWEEN REMOVALS 1AF- 238
MEASUREMENT BASE

TABLE BE, WAR/PEACE RELIABILITY, AVAILABILITY, AND MAINTAINABILITY


INDICATOR CHARACTERISTICS
49. This table contains reliability and maintainability characteristics of the item under analysis categorized by
wartime/peacetime scenarios and comparative, allocated, predicted, or measured values. Table keys
consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), RAM
Indicator Code (RAMINDBD), and Operational Requirement Indicator (OPRQINBE).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
RAMINDBD RAM INDICATOR CODE 1AF- 347 F
OPRQINBE RAM OPERATIONAL REQUIREMENT 1AF- 275 K
INDICATOR
ALDTXXBE ADMINISTRATIVE AND LOGISTIC DELAY TIME 3NR- 013
OPAVAIBE OPERATIONAL AVAILABILITY 8NR6 273
STABYTBE STANDBY TIME 4NR- 403

3A-24
DEF(AUST)5692

TABLE BF, FAILURE MODE AND RELIABILITY CENTERED MAINTENANCE


ANALYSIS
50. This table contains failure mode information and reliability centered maintenance analysis results
associated with the item under analysis failure modes. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and Failure Mode Indicator (FAMOINBF). For a
given row of information, the following cross-element edits apply to Table BF:

a. Engineering Failure Mode Mean Time Between Failure (EFMTBFBF) and Engineering Failure
Mode Mean Time Between Failure MB (EFMMMBBF) must either both be blank, or have
entries.

b. Engineering Failure Mode Mean Time Between Failure shall be calculated based on Failure
Mode Ratio (Table BF) and Failure Rate (Table BD). A change in any of these variables
shall result in an update of the Engineering Failure Mode Mean Time Between Failure (Table
BF).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
FAMOINBF FAILURE MODE INDICATOR (FMI) 4XF- 134 K
EFMTBFBF ENGINEERING FAILURE MODE MEAN TIME 10 D - - 097
BETWEEN FAILURE (MTBF)
EFMMMBBF ENGINEERING FAILURE MODE MTBF 1AF- 238
MEASUREMENT BASE
FMCLASBF FAILURE MODE CLASSIFICATION 1AF- 132
FMRATOBF FAILURE MODE RATIO 4NR3 136
RCMR01BF RELIABILITY CENTERED MAINTENANCE 1XF- 344
(RCM) LOGIC RESULTS 01
RCMR02BF RCM LOGIC RESULTS 02 1XF- 344
RCMR03BF RCM LOGIC RESULTS 03 1XF- 344
RCMR04BF RCM LOGIC RESULTS 04 1XF- 344
RCMR05BF RCM LOGIC RESULTS 05 1XF- 344
RCMR06BF RCM LOGIC RESULTS 06 1XF- 344
RCMR07BF RCM LOGIC RESULTS 07 1XF- 344
RCMR08BF RCM LOGIC RESULTS 08 1XF- 344
RCMR09BF RCM LOGIC RESULTS 09 1XF- 344
RCMR10BF RCM LOGIC RESULTS 10 1XF- 344
RCMR11BF RCM LOGIC RESULTS 11 1XF- 344
RCMR12BF RCM LOGIC RESULTS 12 1XF- 344
RCMR13BF RCM LOGIC RESULTS 13 1XF- 344
RCMR14BF RCM LOGIC RESULTS 14 1XF- 344
RCMR15BF RCM LOGIC RESULTS 15 1XF- 344
RCMR16BF RCM LOGIC RESULTS 16 1XF- 344
RCMR17BF RCM LOGIC RESULTS 17 1XF- 344
RCMR18BF RCM LOGIC RESULTS 18 1XF- 344
RCMR19BF RCM LOGIC RESULTS 19 1XF- 344
RCMR20BF RCM LOGIC RESULTS 20 1XF- 344
RCMR21BF RCM LOGIC RESULTS 21 1XF- 344
RCMR22BF RCM LOGIC RESULTS 22 1XF- 344
RCMR23BF RCM LOGIC RESULTS 23 1XF- 344
RCMR24BF RCM LOGIC RESULTS 24 1XF- 344
RCMR25BF RCM LOGIC RESULTS 25 1XF- 344
RCMDSABF RCM DISPOSITION A 1XF- 084
RCMDSBBF RCM DISPOSITION B 1XF- 084
RCMDSCBF RCM DISPOSITION C 1XF- 084
RCMDSDBF RCM DISPOSITION D 1XF- 084
RCMDSEBF RCM DISPOSITION E 1XF- 084
RCMDSFBF RCM DISPOSITION F 1XF- 084
RCMDSGBF RCM DISPOSITION G 1XF- 084
RCMDSHBF RCM DISPOSITION H 1XF- 084

3A-25
DEF(AUST)5692

RCMDSIBF RCM DISPOSITION I 1XF- 084


RCMDSJBF RCM DISPOSITION J 1XF- 084

TABLE BG, FAILURE MODE AND RELIABILITY CENTERED MAINTENANCE


NARRATIVE
51. This table may be used to identify Failure/Damage Mode Effect End Effect, Failure/Damage Mode Effect
Local, Failure/Damage Mode Effect Next Higher, Failure Cause, Failure/Damage Mode, Failure Mode
Detection Method, Failure Mode Predictability, Failure Mode Remarks, Reliability Centered Maintenance
(RCM) Redesign Recommendations, and RCM Reasoning. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Failure Mode Indicator (FAMOINBF), Failure
Mode Narrative Code (FMNCNABG), and Failure Mode Narrative Text Sequencing Code (TEXSEQBG). For
a given row of information, the following cross-element edits apply to table BG:

a. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (A), then this table describes the
consequences of each failure/damage mode and effect on the item operation, function, or
status (Failure/Damage Effect End Effect, DED 125).

b. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (B), then this table describes the
consequences of each failure/damage mode effect local on the item operation, function, or
status (Failure/Damage Effect Local, DED 126).

c. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (C), then this table describes the
consequences of each failure/damage mode effect next higher on the item operation,
function, or status (Failure/Damage Effect Next Higher, DED 127).

d. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (D), then this table describes all
possible failure causes postulated on the basis of the stated requirements in the system and
failure definitions. All probable independent causes for each failure shall also be identified.
(Failure Cause, DED 124).

e. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (E), then this table describes all
possible failure/damage mode postulated on the basis of the stated requirements in the
system and failure definitions. All probable independent causes for each failure shall also be
identified. A description of all possible damage modes which could result from specific
threats (Failure/Damage Mode, DED 128).

f. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (F), then this table describes the
method(s) by which occurrence of a specific failure mode is detected by the operator or
maintenance technician (Failure Mode Detection Method, DED 129).

g. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (G), then this table provides
information on known incipient failure indicators which are peculiar to the item failure trends
(Failure Predictability, DED 138).

h. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (H), then this is a narrative table
which states a condition not readily identified in a given data element. This Table is related
to a failure mode, therefore, it should prefaced with a reference to a specific failure mode
(Failure Mode Remarks, DED 137).

i. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (I), then this table describes
recommended design changes, disposition of each recommendation, and the results of each
recommendation for which analysis indicates a redesign is warranted (Redesign
Recommendations, DED 426).

j. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (J), then this table describes the
type of age exploration and how it is to be used based on the results of the RCM analysis
made in table BF (RCM Age Exploration, DED 343).

3A-26
DEF(AUST)5692

k. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (K), then this table describes the
reasoning behind the RCM logic results and disposition choices made in table BF (Reliability
Centered Maintenance Reasoning, DED 346).

l. If the Failure Mode and RCM Narrative Code (FMNCNABG) is (L), then this table describes
recommended RCM redesign changes, disposition of each recommendation, and the results
of each recommendation for which analysis indicates a redesign is warranted (RCM
Redesign Recommendations, DED 426).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
FAMOINBF FAILURE MODE INDICATOR (FMI) 4XF- 134 F
FMNCNABG FAILURE MODE & RCM NARRATIVE CODE 1AF- 131 K
TEXSEQBG FAILURE MODE & RCM NARRATIVE TEXT 5NR- 450 K
SEQUENCING CODE
FMNNARBG FAILURE MODE NARRATIVE 65 X - - ---

TABLE BH, FAILURE MODE TASK


52. This table identifies the maintenance task(s) that are required to correct the identified failure mode of the
item under analysis and preventive maintenance tasks that are deemed applicable and effective through an
RCM analysis. Table keys consist of EIAC (EIACODXA), Failure Mode Task (FMT) LCN (LSACONBH).
FMT ALC (ALTLCNBH). FMT LCN Type (LCNTYPBH). FMT Failure Mode Indicator (FAMOINBH), Task
Requirement ALC (TALCNCBH), Task Requirement LCN Type (TLCNTYBH), and Task Requirement Task
Code (TTASKCBH). For a given row of information, the following cross-element edits apply to table BH:

a. The EIAC from Task Requirement Table CA and Failure Mode and RCM Analysis Table BF are
the same; therefore, they are not duplicated.

b. Table keys are migrated from table BF, but are given role name "FMT" to distinguish them
(LSACONBH, ALTLCNBH, LCNTYPBH, and FAMOINBH). Table keys are migrated from
table CA, but are given role name "Task Requirement" to distinguish them (TLSACNBH,
TALCNCBH, TLCNTYBH, and TTASKCBH).

c. Maintenance Interval (MAININBH) and Maintenance Interval MB (MAINMBBH) must either both
be blank, or have entries.

d. Edit c is not allowed unless a preventive Task Type (TATYPEBH) is selected.

e. Task Type (TATYPEBH) must be "P" or "U", if PMCS from the CA table is "Y".

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONBH FAILURE MODE TASK (FMT) LSA CONTROL 18 X L - 199 F
NUMBER (LCN)
ALTLCNBH FMT ALTERNATE LCN CODE 2NF- 019 F
LCNTYPBH FMT LCN TYPE 1AF- 203 F
FAMOINBH FMT FAILURE MODE INDICATOR 4XF- 134 F
TLSACNBH TASK REQUIREMENT LCN 18 X L - 199 F
TALCNCBH TASK REQUIREMENT ALTERNATE LCN CODE 2NF- 019 F
TLCNTYBH TASK REQUIREMENT LCN TYPE 1AF- 203 F
TTASKCBH TASK CODE 7XF- 427 F
TATYPEBH TASK TYPE 1AF- 433
MAININBH MAINTENANCE INTERVAL 10 D - - 208
MAINMBBH MAINTENANCE INTERVAL MEASUREMENT 1AF- 238
BASE

3A-27
DEF(AUST)5692

TABLE BI, FAILURE MODE INDICATOR MISSION PHASE CODE CHARACTERISTICS


53. This table contains FMECA results associated with the item under analysis categorized by failure mode
and mission phase/operational mode. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC
(ALTLCNXB), LCN Type (LCNTYPXB), Failure Mode Indicator (FAMOINBF), and Mission Phase Code
(MISSPCBL). For a given row of information, the following cross-element edits apply to table BI:

a. The EIAC from Mission Phase Operational Mode Table BL and Failure Mode Table BF are the
same; therefore, they are not duplicated.

b. Operating Time (FMOPTIBI) and Operating Time MB (FMOTMBBI) must either both be blank,
or have entries.

c. The Operating Time MB (FMOTMBBI) should be the same as the Failure Rate MB
(FARAMBBD) from Table BD for the calculations to be correct.

d. Failure Mode Criticality Number shall be calculated based on Failure Effect Probability (Table
BI), Failure Mode Ratio (Table BF), Part Failure Rate (Table BD), and Operating Time (Table
BI). A change in any of these variables shall result in an update of the Failure Mode
Criticality Number (Table BI).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
FAMOINBF FAILURE MODE INDICATOR (FMI) 4XF- 134 F
MISSPCBL MISSION PHASE CODE 1XF- 246 F
FMSHSCBI SAFETY HAZARD SEVERITY CODE 1NF- 362 M
FEPROBBI FAILURE EFFECT PROBABILITY 3NR2 130
FACRNUBI FAILURE MODE CRITICALITY NUMBER 10 D - - 133
FPROBLBI FAILURE PROBABILITY LEVEL 1AF- 139
FMOPTIBI OPERATING TIME 6NR2 269
FMOTMBBI OPERATING TIME MEASUREMENT BASE 1AF- 238

TABLE BJ, FAILURE MODE INDICATOR MISSION PHASE CODE CHARACTERISTICS


NARRATIVE
54. This table may be used to identify Compensating Design Provisions and Compensating Operator
Actions. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type
(LCNTYPXB), Failure Mode Indicator (FAMOINBF), Mission Phase Code (MISSPCBL), Failure Mode
Indicator Mission Phase Characteristics Narrative Code (FMMPCNBJ), and Failure Mode Indicator Mission
Phase Code Characteristics Narrative Text Sequencing Code (TEXSEQBH). For a given row of information,
the following cross-element edits apply to Table BJ:

a. If the Failure Mode Indicator Mission Phase Characteristics Narrative Code (FMMPCNBJ) is (A),
then this table describes compensating design provisions which circumvent or mitigate the
effect of the failure (Compensating Design Provisions, DED 049).

b. If the Failure Mode Indicator Mission Phase Characteristics Narrative Code (FMMPCNBJ) is (B),
then this table describes compensating operator action provisions which circumvent or
mitigate the effect of the failure (Compensating Operator Action Provisions, DED 050).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F

3A-28
DEF(AUST)5692

FAMOINBF FAILURE MODE INDICATOR (FMI) 4XF- 134 F


MISSPCBL MISSION PHASE CODE 1XF- 246 F
FMMPCNBJ FMI MISSION PHASE CHARACTERISTICS 1AF- 135 K
NARRATIVE CODE
TEXSEQBJ FMI MISSION PHASE CHARACTERISTICS 5NR- 450 K
NARRATIVE TEXT SEQUENCING CODE
FMCNARBJ FAILURE MODE INDICATOR MISSION PHASE 65 X - - ---
CHARACTERISTICS NARRATIVE

TABLE BK, RELIABILITY, AVAILABILITY, AND MAINTAINABILITY CRITICALITY


55. This table sums up the failure mode criticality numbers related to the failure modes of an item within
specific safety hazard severity classification (SHSC) and mission phases. Table keys consist of EIAC
(EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Mission Phase Code
(MISSPCBL), and RAM SHSC (FMSHSCBK).

a. Item Criticality Number shall be calculated based on the summation of the Failure Mode
Criticality Numbers (Table BI).

b. A change in any of the Failure Mode Criticality Numbers (Table BI) shall result in an update of
the Item Criticality Number (Table BK).

c. Safety Hazard Severity Code (BI.FMSHSCBI) must be established in table BI prior to


establishing a RAM Safety Hazard Severity Code (BK.FMSHSCBK) in this table.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
MISSPCBL MISSION PHASE CODE 1XF- 246 F
FMSHSCBK RAM SAFETY HAZARD SEVERITY CODE 1NF- 362 K
RICRITBK RAM ITEM CRITICALITY NUMBER 10 D - - 178

TABLE BL, MISSION PHASE OPERATION MODE


56. This table identifies the mission phase/operational modes that the new system/equipment is expected to
experience during normal operation. Table keys consist of EIAC (EIACODXA) and Mission Phase Code
(MISSPCBL).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
MISSPCBL MISSION PHASE CODE 1XF- 246 K
MPOPLDBL MISSION PHASE/OPERATIONAL MODE 65 X - - 247

3A-29
DEF(AUST)5692

TASK INVENTORY, TASK ANALYSIS, PERSONNEL AND SUPPORT REQUIREMENTS


57. The following data tables identified by a "C" in the first position of the table code are required for
documentation of task analysis and personnel and support requirement data. These tables equate to MIL-
STD-1388-2A "C" and "D" records. Information will be presented in sufficient detail to define task times,
skills, tools, support equipment, facilities, and supply support requirements. The task taxonomy utilized to
analyze and inventory tasks is located in the glossary of MIL-STD-1388-1, Notice 3 and DED 372 of this
standard. Figure 4 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


CA Task Requirement
CB Subtask Requirement
CC Sequential Subtask Description
CD Subtask Personnel Requirement
CE Task Remark
CF Task Remark Reference
CG Task Support Equipment
CH Task Manual
CI Task Provisioned Item
CJ Job and Duty Assignments
CK Task Inventory

3A-30
DEF(AUST)5692

Figure 4 C Table Relationships

TABLE CA, TASK REQUIREMENT


58. This table contains task level information such as Mean Elapsed Time, Task Frequency, Task Criticality,
Task Identification (ID) and Task Code. It also contains information about personnel and training aspects of
the task. In addition, this table provides the capability to reference an entire task. Table keys consist of
EIAC (EIACODXA), LCN (LSACONXB), LCN Type (LCNTYPXB), ALC (ALTLCNXB) and Task Code
(TASKCDCA).

a. For referencing purposes only, Referenced LCN (REFLCNCA), Referenced LCN Type
(REFTYPCA), Referenced ALC (REFALCCA), Referenced EIAC (REFEIACA), and
Referenced Task Code (REFTSKCA) are mandatory keys. This referencing capability
should only be used when the data of this table and the subordinate tables (tables CB
through CI) are the same for referenced and referencing tasks. All non-key attributes in
Table CA and all subordinate tables; (Tables CB - CI) are pulled from the Referenced Task
and its subordinate tables. Key attributes entered in Table CA will migrate to all subordinate

3A-31
DEF(AUST)5692

tables; but, additional keys which are needed in subordinate tables will be pulled from the
Referenced Task and its subordinate tables. In other words, only key entries and referenced
entries are required in this table and no further entries are required in subordinate tables.

b. Unscheduled task codes, task interval codes of "F", "G", or "J" (2d position of the task code),
must have an MB entered which corresponds to the MB for the AOR. For this reason, the
AOR LCN (AORLCNCA), AOR ALC (AORALCCA), AOR LCN Type (AORTYPCA), and the
AOR MB (AORMSBCA) must match with a set of key values already established in Table
AG.

c. Every Task Code (TASKCDCA) must have a Task ID (TASKIDCA).

d. Secondary Means of Detection (SMDTECCA) is not allowed without Primary Means of


Detection (PMDTECCA).

e. Up to three Performance Standards (PRSTDACA, PRSTDBCA, PRSTDCCA), and Task


Conditions (TCONDACA, TCONDBCA, TCONDCCA) can be entered for a given record.

f. Every task code requires a corresponding task frequency.

g. If the Facility Requirement Code (FTRNRQCA) is "Y", the Facility tables (F tables) should be
addressed.

h. Up to four Training Location Rationale (TRNLOCCA) codes may be entered for each unique
combination of LCN, EIAC, ALC, LCN Type, and task code (codes must be entered in a
continuous string).

i. Up to four Training Rationale (TRNRATCA) codes may be entered for each unique combination
of LCN, EIAC, ALC, LCN Type and task code (codes must be entered in a continuous
string).

j. Measured Mean Man-Hours (MSDMMHCA) are calculated by summing the Mean Man-Minutes
(SUBMMMCD) per Person ID for the given task (see DED 225) and dividing by 60.

k. Measured Mean Elapsed Time (MSDMETCA) is calculated by summing the Mean Minute
Elapsed Times (SBMMETCB) for all subtasks of the task (see DED225) and dividing by 60.

l. Task Frequency (corrective) shall be calculated based on Failure Mode Ratio (Table BF),
Failure Rate (Table BD), Mean Time Between Maintenance Induced (Table BD), Mean Time
Between Maintenance No Defect (Table BD), Conversion Factor (Table BA), and Annual
Operating Requirements (Table AG). Task Frequency (preventive) shall be calculated on
Annual Operating Requirements (Table AG), Conversion Factor (Table BA), Maintenance
Interval (Table BH) or Task Interval Code (Table CA). A change in any of these variables
shall result in an update of Task Frequency (Table CA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 K
REFEIACA REFERENCED EIAC 10 X L - 096
REFLCNCA REFERENCED LCN 18 X L - 199
REFALCCA REFERENCED ALTERNATE LCN CODE 2NF- 019
REFTYPCA REFERENCED LCN TYPE 1AF- 203
REFTSKCA REFERENCED TASK CODE 7XF- 427
AORLCNCA ANNUAL OPERATING REQUIREMENT (AOR) 18 X L - 199
LCN
AORALCCA AOR ALC 2NF- 019
AORTYPCA AOR LCN TYPE 1AF- 203
AORMSBCA TASK AOR MEASUREMENT BASE 1AF- 238
TASKIDCA TASK IDENTIFICATION 36 X L - 431 M
TSKFRQCA TASK FREQUENCY 7NR4 430

3A-32
DEF(AUST)5692

TSKCRCCA TASK CRITICALITY CODE 1AF- 429


HRDCPCCA HARDNESS CRITICAL PROCEDURE (HCP) 1AF- 152
CODE
HAZMPCCA HAZARDOUS MAINTENANCE PROCEDURES 1AF- 155
CODE
PMCSIDCA PREVENTIVE MAINTENANCE CHECKS AND 1AF- 296
SERVICES (PMCS) INDICATOR CODE
MSDMETCA MEASURED MEAN ELAPSE TIME 5NR2 224
PRDMETCA PREDICTED MEAN ELAPSE TIME 5NR2 224
MSDMMHCA MEASURED MEAN MAN-HOURS 5NR2 225
PRDMMHCA PREDICTED MEAN MAN-HOURS 5NR2 225
PMDTECCA PRIMARY MEANS OF DETECTION 1AF- 237
SMDTECCA SECONDARY MEANS OF DETECTION 1AF- 237
FTRNRQCA FACILITY REQUIREMENT CODE 1AF- 358
TRNRQCCA TRAINING EQUIPMENT REQUIREMENT CODE 1AF- 358
TRNRECCA TRAINING RECOMMENDATION TYPE 1AF- 463
TRNLOCCA TRAINING LOCATION RATIONALE 4AL- 461
TRNRATCA TRAINING RATIONALE 4AL- 462
TSEREQCA TOOL/SUPPORT EQUIPMENT REQUIREMENT 1AF- 358
CODE
PRSTDACA TASK PERFORMANCE STANDARD A 1AF- 287
PRSTDBCA TASK PERFORMANCE STANDARD B 1AF- 287
PRSTDCCA TASK PERFORMANCE STANDARD C 1AF- 287
TCONDACA TASK CONDITION A 1AF- 428
TCONDBCA TASK CONDITION B 1AF- 428
TCONDCCA TASK CONDITION C 1AF- 428

TABLE CB, SUBTASK REQUIREMENT


59. This table contains data related to the subtask level such as Work Area Code and Mean Minute Elapsed
Time. All task narrative will be written at the subtask level, then rolled into the task level. It is possible to
reference subtask descriptions within this table. Table keys consist of LCN (LSACONXB), LCN Type
(LCNTYPXB), ALC (ALTLCNXB), EIAC (EIACODXA), Task Code (TASKCDCA), and Subtask Number
(SUBNUMCB).

a. For referencing purposes, Referenced Subtask Number (RFDSUBCB), Referenced Subtask


Task Code (RFDTCDCB), Referenced Subtask LCN (RFDLCNCB), Referenced Subtask
ALC (RFDALCCB), Referenced Subtask LCN Type (RFDALCCB), and Referenced Subtask
EIAC (RFDEIACB) must be included as nonidentifying keys. This referencing capability
should only be used when the data of this table and the subordinate tables SEQUENTIAL
TASK DESCRIPTION and SUBTASK PERSONNEL REQUIREMENTS (tables CC and CD)
are the same for referenced and referencing subtasks. All non-key attributes in table CB and
its subordinate tables (CC and CD) are pulled from the referenced subtask and its
subordinate tables. Keys from table CB migrate down to tables CC and CD. Additional keys
needed for tables CC and CD are pulled from referenced subtask tables CC and CD.

b. Subtask Numbers shall begin with 001 and run through 999 for each unique set of keys (e.g.,
EIAC, LCN, ALC, LCN Type, and task code). Skips are allowed when assigning subtask
numbers.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMCB SUBTASK NUMBER 3NF- 407 K
SUBTIDCB SUBTASK IDENTIFICATION 36 X L - 431
RFDEIACB REFERENCED SUBTASK EIAC 10 X L - 096
RFDLCNCB REFERENCED SUBTASK LCN 18 X L - 199
RFDALCCB REFERENCED SUBTASK ALTERNATE LCN 2NF- 019

3A-33
DEF(AUST)5692

CODE
RFDTYPCB REFERENCED SUBTASK LCN TYPE 1AF- 203
RFDTCDCB REFERENCED SUBTASK TASK CODE 7XF- 427
RFDSUBCB REFERENCED SUBTASK NUMBER 3NF- 407
SBMMETCB SUBTASK MEAN MINUTE ELAPSED TIME 5NR1 227
SUBWACCB SUBTASK WORK AREA CODE 4XL- 514

TABLE CC, SEQUENTIAL SUBTASK DESCRIPTION


60. This table contains the sequential task narrative entered at the subtask level. The narrative will be
entered in a step-by-step basis in order to document all subtasks required to perform the task under analysis.
Subtasks should be detailed and sequenced to eliminate possibilities of technically incorrect procedures.
Elements are subordinate to subtasks. All requirements for power, compressed air, and environmental
considerations will be specified. Qualifying notes must be included when performance to particular
standards, survivability requirements, inspection criteria, special procedures, tolerances, measurement
ranges, cautions and safety precautions are required. Notes and warnings for set up of tasks (e.g.,
identifying support items which need to be on hand and ready, but are not needed until later in the task)
should be documented in the first subtask. Similarly, notes and warnings for close-down of a task should be
documented in the last subtask. In cases of multi-personnel tasks, the communication and coordination
requirements between personnel must be documented (i.e., communication and coordination between
individuals in one crew area with individuals in another area). Table keys consist of LCN (LSACONXB),
LCN Type (LCNTYPXB), ALC (ALTLCNXB), EIAC (EIACODXA), Task Code (TASKCDCA), Subtask Number
(SUBNUMCB), and Text Sequencing Code (TEXSEQCC).

a. The Element Indicator "E" is documented against the first line of a given element narrative and
is blank for all subsequent lines of that element narrative.

b. Element narratives must begin on unique lines (Text Sequence Codes). For example, one
element cannot end on line 12 and the next task element begin on line 12 also.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMCB SUBTASK NUMBER 3NF- 407 F
TEXSEQCC SEQUENTIAL SUBTASK DESCRIPTION TEXT 5NR- 450 K
SEQUENCING CODE
SUBNARCC SEQUENTIAL SUBTASK DESCRIPTION 65 X - - 372
ELEMNTCC ELEMENT INDICATOR 1AF- 095

TABLE CD, SUBTASK PERSONNEL REQUIREMENT


61. This table contains information pertaining to personnel and support requirements for each entered
subtask. Table keys consist of LCN (LSACONXB), LCN Type (LCNTYPXB), ALC (ALTLCNXB), EIAC
(EIACODXA), Task Code (TASKCDCA), Subtask Number (SUBNUMCB), and Person Identifier
(SUBPIDCD).

a. SSC (SKSPCDGA) and New or Modified SSC (MDCSSCGB) are migrated into this table as
nonidentifying attributes which means that they are not required to uniquely identify an
instance of the entity.

b. Unique Person IDs (SUBPIDCD) can be assigned to each person required to perform a subtask
and that Person ID-to-Person can be carried for the entire weapon system/EI. This method
of coding Person IDs is recommended because it facilitates reporting manpower and
personnel information and can be used to relate the Person ID to a specific Job. If this
assignment logic is not used the alternate Person ID assignment logic calls for entering a
code which identifies each person required to perform a subtask or part of a subtask. If a

3A-34
DEF(AUST)5692

person is used to perform more than one subtask, the same Person ID will be used
throughout the entire task analysis. However, from one task to another, the same Person ID
code can be repeated for different personnel.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMCB SUBTASK NUMBER 3NF- 407 F
SUBPIDCD SUBTASK PERSON IDENTIFIER 3XL- 288 K
SKSPCDGA SKILL SPECIALTY CODE 7XL- 387
MDCSSCGB NEW OR MODIFIED SKILL SPECIALTY CODE 7XL- 257
SUBMMMCD SUBTASK MEAN MAN-MINUTES 4NR1 226
SSECDECD SKILL SPECIALTY EVALUATION CODE 1AF- 388

TABLE CE, TASK REMARK


62. This table contains remarks, relating to the task under analysis which are incorporated in the LSA-004
and LSA-033 reports. Table keys are EIAC (EIACODXA) and Task Remark Reference Code (TSKRRCCE).

Note:

1. Every Task Remark Reference Code and Task Remark combination is unique across all rows of information for a
given EIAC. In other words, for the same EIAC, a given Task Remark Reference Code can only correspond to
one Task Remark statement throughout the file structure.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
TSKRRCCE TASK REMARK REFERENCE CODE 2XF- 349 K
TSKREMCE TASK REMARKS 240 X L - 432

TABLE CF, TASK REMARK REFERENCE


63. This table serves as a tie-in table between the TASK REQUIREMENT table (CA) and the TASK
REMARK table (CE). Table keys consist of LCN (LSACONXB), LCN Type (LCNTYPXB), ALC (ALTLCNXB),
EIAC (EIACODXA), and Task Code (TASKCDCA), which are migrated from table CA and the Task Remark
Reference Code (TSKRRCCE), which migrates from table CE. EIACODXA from tables CA and CE must
always be identical therefore, duplication of that key in this table is not needed.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
TSKRRCCE TASK REMARK REFERENCE CODE 2XF- 349 F

TABLE CG, TASK SUPPORT EQUIPMENT


64. This table contains information which relates data needed for the task under analysis to the Support
Equipment (SE) tables. This table serves as the tie-in between Task Analysis and SE areas for data which is
to be incorporated into the LSA-070 series of reports (e.g., LSA-070, 072, 074, etc.). Table keys consist of
LCN (LSACONXB), LCN Type (LCNTYPXB), ALC (ALTLCNXB), EIAC (EIACODXA), Task Code

3A-35
DEF(AUST)5692

(TASKCDCA), Task Support Reference Number (TSREFNCG) and Task Support CAGE Code
(TSCAGECG).

a. In a given row, Quantity Per Task and Quantity Per Task Unit of Measure must either both be
blank, or both have entries.

b. Based on the definitions for Item Category Codes (ICC) (DED 177), it is recommended that only
items which fall under the following ICCs (identified in table EA by SEICCDEA) be entered in
this table: 7, 8, M, D, 1, H, 4, 5, 6, 2, G, N, P, R, 3, S, T, E, F, J, U, V, AC, AD and AF.

c. If the Training Equipment Requirement Code (TRNRQCCA) in table CA is "Y" for the subject
LCN, ALC, and Task Code, at least one item of support equipment identified by the Task
Support Reference Number (TSREFNCG) must have an ICC (SEICCDEA) of "S", "T", or
"AF" against it in the EA table (match TSREFNCG and TSCAGECG with SEREFNEA and
SECAGEEA, then check ICC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
TSCAGECG TASK SUPPORT CAGE CODE 5XF- 046 F
TSREFNCG TASK SUPPORT REFERENCE NUMBER 32 X L - 337 F
SQTYTKCG SUPPORT ITEM QUANTITY PER TASK 5NR2 319
SQTKUMCG SUPPORT ITEM QUANTITY PER TASK UNIT OF 2 A F - 491
MEASURE

TABLE CH, TASK MANUAL


65. This table ties in the narrative for the task under analysis to the corresponding Technical Manual (TM)
which will contain the narrative. Table keys consist of LCN (LSACONXB), LCN Type (LCNTYPXB), ALC
(ALTLCNXB), EIAC (EIACODXA), Task Code (TASKCDCA), and TM Code (TMCODEXI).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437 F

TABLE CI, TASK PROVISIONED ITEM


66. This table will be used to obtain data from the Task Analysis area, which will be used in determining
provisioning technical factors. In other words, this table links the provisioning area directly to the task area.
This table should be used for documenting spares and repair parts needed in support of the subject task.
Table keys consist of Task LCN (TSKLCNCI), Task LCN Type (TSKLTYCI), Task ALC (TSKALCCI), and
Task Provision Task Code (TSKTCDCI), which are migrated from table CA and Task Provision LCN
(PROLCNCI), Task Provision ALC (PROALCCI), Task Provision LCN Type (PROLTYCI), Task Provision
CAGE Code (PROCAGCI), and Task Provision Reference Number (PROREFCI), which migrate from table
HG. The EIACs (EIACODXA), which are resident in tables CA and HG, must be identical.

a. In a given row, Quantity Per Task and Quantity Per Task Unit of Measure must either both be
blank, or both have entries.

3A-36
DEF(AUST)5692

b. For task code functions (1st position of Task Code) of H, there must be one Task Provision LCN
that matches the Task LCN for all items required to support subject task (i.e.,
remove/replace of that LCN).

c. Based on definitions for ICCs (DED177), it is recommended that only items which fall under the
following ICCs be entered in this table (identified in table HG by ITMCATHG): Q, W, X, Y, Z,
9, K, L, AA, AB, AD and AE.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
TSKLCNCI TASK LSA CONTROL NUMBER (LCN) 18 X L - 199 F
TSKALCCI TASK ALTERNATE LCN CODE (ALC) 2NF- 019 F
TSKLTYCI TASK LCN TYPE 1AF- 203 F
TSKTCDCI TASK PROVISION TASK CODE 7XF- 427 F
PROCAGCI TASK PROVISION CAGE CODE 5XF- 046 F
PROREFCI TASK PROVISION REFERENCE NUMBER 32 X L - 337 F
PROLCNCI TASK PROVISION LCN 18 X L - 199 F
PROALCCI TASK PROVISION ALC 2NF- 019 F
PROLTYCI TASK PROVISION LCN TYPE 1AF- 203 F
PQTYTKCI PROVISION QUANTITY PER TASK 5NR2 319
PQTKUMCI PROVISION QUANTITY PER TASK UNIT OF 2AF- 491
MEASURE

TABLE CJ, JOB AND DUTY ASSIGNMENTS


67. This table should be used to document jobs and duties personnel perform in a system. Documentation
in this table is required if the Task Inventory report (LSA-018) is to be processed. Key data elements are Job
Code (JOBCODCJ) and Duty Code (DUTYCDCJ).

CODE DATA ELEMENT TITLE FORMAT DED KEY


JOBCODCJ JOB CODE 2XF- 186 K
DUTYCDCJ DUTY CODE 4XL- 091 K
JOBDESCJ JOB 40 X L - 185
DUTIESCJ DUTY 240 X L - 090

TABLE CK, TASK INVENTORY


68. This table is used as a cross reference to produce the Task Inventory report (LSA-018). Tables CC, CD,
and CJ are combined in this cross reference table to identify the tasks, subtasks, and elements that are
required for a given Job and Duty. Table keys include all columns. EIACODXA, LSACONXB, ALTLCNXB,
LCNTYPXB, TASKCDCA, and SUBNUMCB must be identical for tables CC and CD, migrating SUBPIDCD.
Text Sequence Code From (TSFROMCK) and Text Sequence Code To (TEXTTOCK) migrate from
TEXSEQCC, and therefore, each must match with a TEXSEQCC value for the given subtask.

a. JOBCODCJ and DUTYCDCJ must exist in table CJ prior to table CK.

b. For a given task, Job Code (JOBCODCJ) must have a unique Person ID (SUBPIDCD).

CODE DATA ELEMENT TITLE FORMAT DED KEY


JOBCODCJ JOB CODE 2XF- 186 F
DUTYCDCJ DUTY CODE 4XL- 091 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMCB SUBTASK NUMBER 3NF- 407 F
TSFROMCK SEQUENTIAL SUBTASK DESCRIPTION TEXT 5NR- 450 K

3A-37
DEF(AUST)5692

SEQUENCING CODE FROM


TEXTTOCK SEQUENTIAL SUBTASK DESCRIPTION TEXT 5NR- 450 K
SEQUENCING CODE TO
SUBPIDCD SUBTASK PERSON IDENTIFIER 3XL- 288 K

3A-38
DEF(AUST)5692

SUPPORT EQUIPMENT AND TRAINING MATERIEL REQUIREMENTS


69. Data tables identified by an "E" in the first position of the table code are structured to consolidate the
pertinent information related to existing or new support/test equipment or training equipment. These tables
contain most of the data that was captured on the old "E and El" records. Much of this information serves as
administrative type data for the Support Equipment Recommendation Data (SERD) report. This information
also serves as identification of hardware and software elements required to conduct off-line tests. Figure 5
depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


EA Support Equipment
EB Allocation Data
EC Support Equipment Parameters
ED Support Equipment Authorization
EE Support Equipment Narrative
EF Support Equipment Recommendation Data
EG Support Equipment Recommendation Data Revision Remarks
EH Alternate National Stock Number
EI Input Power Source
EJ Support Equipment Design Data
EK Supercedure Data
EL Support Equipment Integrated Logistic Support Requirement Category Code
EM System Equipment

3A-39
DEF(AUST)5692

Figure 5 E Table Relationships

TABLE EA, SUPPORT EQUIPMENT


70. This table captures a large portion of data which occurs one time per support/training equipment item.
This table is used as the foundation for support/training equipment documentation as a whole. Table keys
are Support Equipment (SE) Reference Number (SEREFNEA) and SE CAGE (SECAGEEA).

a. If Adaptor/Interconnection Device Required (AIDRQDEA) is "Y", tables UI and UJ must be


completed.

b. If entries exist for Operating Dimensions or Weight, Storage Dimensions or Weight, or Support
Equipment Shipping Dimensions or Weight, their respective units of measure must have
entries also.

3A-40
DEF(AUST)5692

c. Up to eight Using Service Designator Codes (USESEREA) can be entered at one time in a
continuous string. This capability allows for all possible combinations of using services to be
entered.

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
FLITNMEA SE FULL ITEM NAME 42 X L - 412
SEICCDEA SE ITEM CATEGORY CODE 2XL- 177
AQDCOFEA ACQUISITION DECISION OFFICE 15 X L - 002
ENDARTEA END ARTICLE ITEM DESIGNATOR 26 X - - 179
AIDRQDEA ADAPTOR/INTERCONNECTION DEVICE 1AF- 005
REQUIRED
DATFADEA DATE OF FIRST ARTICLE DELIVERY 6NF- 071
CALINTEA CALIBRATION INTERVAL 2NR- 037
CALITMEA CALIBRATION ITEM 1AF- 038
CALRQDEA CALIBRATION REQUIRED 1AF- 040
CALSTDEA CALIBRATION STANDARD 1AF- 041
CALTIMEA CALIBRATION TIME 5NR1 042
CMRSRCEA CALIBRATION MEASUREMENT REQUIREMENT 1 X F - 035
SUMMARY RECOMMENDED
CNTRNOEA SE CONTRACT NUMBER 19 X L - 055
CFEGFEEA CFE / GFE 1AF- 056
CUSTCDEA CUSTODY CODE 1AF- 069
DRWCLSEA DRAWING CLASSIFICATION 3X-- 088
ECOANLEA ECONOMIC ANALYSIS 1AF 093
FAMGRPEA FAMILY GROUP 10 X L - 142
GENECDEA GENERIC CODE 5XL- 148
GOVDESEA GOVERNMENT DESIGNATOR 20 X L 149
HDWRPREA HARDWARE DEVELOPMENT PRICE 8NR- 153
ILSPRCEA INTEGRATED LOGISTIC SUPPORT PRICE 8NR- 170
DSNPRCEA DESIGN DATA PRICE 8NR- 080
EXUNPREA EXTENDED UNIT PRICE 8NR- 103
PASTHREA PASS THROUGH PRICE 8NR- 285
OSCOSTEA OPERATING AND SUPPORT COST 8NR- 267
RCURCSEA RECURRING COST 8NR- 332
LICYSTEA LIFE CYCLE STATUS 1AF- 190
LIFSPNEA LIFE SPAN 2NR- 191
LGCTCDEA LOGISTIC CONTROL CODE 1AF 197
LGDCOFEA LOGISTICS DECISION OFFICE 15 X L - 198
LSARCDEA LSA RECOMMENDATION CODE 1AF- 204
MGTPLNEA MANAGEMENT PLAN 1AF- 216
MGCOATEA MANAGING COMMAND/AGENCY 10 X L - 217
SEMTBFEA SE MTBF 10 D - - 229
SMTBMAEA SE MTBMA 10 D - - 230
SEMTTREA SE MTTR 5NR2 236
MOBFACEA MOBILE FACILITY CODE 1AF- 248
MODCHGEA MODIFICATION OR CHANGE 1AF 252
OPRHGTEA OPERATING HEIGHT 4NR1 268
OPLENGEA OPERATING LENGTH 4NR1 268
OPWIDTEA OPERATING WIDTH 4NR1 268
OPRWGTEA OPERATING WEIGHT 6NR1 270
LWHOUMEA OPERATING DIMENSIONS UNIT OF MEASURE 2 A F - 491
WGTOUMEA OPERATING WEIGHT UNIT OF MEASURE 2AF- 491
PCBLVLEA PRINTED CIRCUIT BOARD REPAIR 1AF- 277
OPERATIONS/MAINTENANCE LEVEL
CALLVLEA SE CALIBRATION 1AF- 277
OPERATIONS/MAINTENANCE LEVEL
RPRLVLEA SE REPAIR OPERATIONS/MAINTENANCE 1AF- 277
LEVEL
SMRCSEEA SE SOURCE, MAINTENANCE AND 6XL- 389
RECOVERABILITY CODE
TMRQCDEA TECHNICAL MANUAL REQUIRED CODE 17 X L 441

3A-41
DEF(AUST)5692

OPRMANEA OPERATORS MANUAL 16 X L - 278


SSCOPREA SKILL SPECIALTY CODE (SSC) FOR SE 7XL- 387
OPERATOR (SEO)
PREATYEA PREPARING ACTIVITY 25 X L - 294
PROELEEA PROGRAM ELEMENT 3XL 301
PSICPOEA PROGRAM SUPPORT INVENTORY CONTROL 2XF 303
POINT
SERICCEA REPORTABLE ITEM CONTROL CODE 1NF 356
REVASSEA REVOLVING ASSETS 4XF- 361
SLFTSTEA SELF TEST CODE 1AF- 370
SENTRAEA SENSORS OR TRANSDUCERS 1AF 371
SERDESEA SE SERVICE DESIGNATOR 1AF- 376
USESEREA USING SERVICE DESIGNATOR CODE 1AF- 376
SKETCHEA SKETCH 1AF- 383
SPRFACEA SPARE FACTOR 4XF 390
SPMGNTEA SPECIAL MANAGEMENT CODE 1AF- 393
SIASCNEA STANDARD INTERSERVICE AGENCY SERIAL 7XF 401
CONTROL NUMBER
STOHGTEA STORAGE HEIGHT 4NR1 405
STOLENEA STORAGE LENGTH 4NR1 405
STOWDTEA STORAGE WIDTH 4NR1 405
STOWGTEA STORAGE WEIGHT 6NR1 406
LWHSUMEA STORAGE DIMENSIONS UNIT OF MEASURE 2AF- 491
WGTSUMEA STORAGE WEIGHT UNIT OF MEASURE 2AF- 491
SESHPHEA SE SHIPPING HEIGHT 4NR1 419
SESHPLEA SE SHIPPING LENGTH 4NR1 419
SESHPWEA SE SHIPPING WIDTH 4NR1 419
SESHWTEA SE SHIPPING WEIGHT 6NR1 420
UMSHIPEA SE SHIPPING DIMENSIONS UNIT OF 2AF- 491
MEASURE
UMSEWTEA SE SHIPPING WEIGHT UNIT OF MEASURE 2AF- 491
SEGRCDEA SE GROUPING 3NF- 413
SEREQDEA SE REQUIRED 1AF- 418
TECEVLEA TECHNICAL EVALUATION PRIORITY CODE 3XF 435
TSTLNGEA TEST LANGUAGE 6AL- 443
TSTPTSEA TEST POINTS 1AF- 446
TMDERCEA TEST MEASUREMENT AND DIAGNOSTIC 1AF- 444
EQUIPMENT REGISTER CODE (TMDE CODE)
TMDERIEA TEST MEASUREMENT AND DIAGNOSTIC 7XF- 445
EQUIPMENT REGISTER INDEX NUMBER
TYPCLSEA TYPE CLASSIFICATION 1AF- 479
TYPEEQEA TYPE EQUIPMENT CODE 4XL- 480
YRFLDGEA YEAR OF FIELDING 2NF 518

TABLE EB, ALLOCATION DATA


71. This table allows documenting of specific information relating allocation documents to discrete facility
types and maintenance levels. Ten allowance ranges can be documented to describe the quantity of SE or
Automatic Test Equipment (ATE) items necessary to support the number of end articles related to each
discrete range of supported end item density. DED 015 dictates the value of each range for the number of
pieces of: (a) end items; (b) ATE items; or, (c) depot overhaul requirements that the entered quantity of SE
can support. Table keys are SE Reference Number (SEREFNEA), SE CAGE (SECAGEEA) and Allowance
Document Number (ALDCNMEB).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
ALDCNMEB ALLOWANCE DOCUMENT NUMBER 10 X L - 016 K
ALORG1EB ALLOWABLE RANGE 1 3NR- 015
ALORG2EB ALLOWABLE RANGE 2 3NR- 015
ALORG3EB ALLOWABLE RANGE 3 3NR- 015

3A-42
DEF(AUST)5692

ALORG4EB ALLOWABLE RANGE 4 3NR- 015


ALORG5EB ALLOWABLE RANGE 5 3NR- 015
ALORG6EB ALLOWABLE RANGE 6 3NR- 015
ALORG7EB ALLOWABLE RANGE 7 3NR- 015
ALORG8EB ALLOWABLE RANGE 8 3NR- 015
ALORG9EB ALLOWABLE RANGE 9 3NR- 015
ALRG10EB ALLOWABLE RANGE 10 3NR- 015
ALDNDSEB ALLOCATION DESIGNATION DESCRIPTION 9XF- 015
ALEXRNEB ALLOCATION EXTENDED RANGE 3XR- 015
ALLVCDEB ALLOCATION LAND VESSEL CODE 1AF- 015
ALMLVLEB ALLOCATION MAINTENANCE LEVEL 2XL- 015
FUNCTION
ALSTIDEB ALLOCATION STATION IDENTIFICATION CODE 5 X L - 015

TABLE EC, SUPPORT EQUIPMENT PARAMETERS


72. This table allows documenting the discrete parameters which can be measured, generated etc., by the
support/training equipment. The capabilities documented here are the basis for determining suitability of an
SE item when compared to the unit under test (UUT) parameters. This table can be used to document
parameters for either CMRS Category II or Category III SE. Table keys are SE Reference Number
(SEREFNEA), SE CAGE (SECAGEEA) and Parameter Group Code (PARGPCEC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
PARGPCEC SE PARAMETER GROUP CODE 2AF- 284 K
CALPROEC CALIBRATION PROCEDURE 20 X L - 039
PARPAREC SE PARAMETER 12 X L - 284
RNGFRMEC SE PARAMETER RANGE FROM 10 D - - 284
RNGTOCEC SE PARAMETER RANGE TO 10 D - - 284
PARACCEC SE PARAMETER ACCURACY 26 X L - 284
SPARIOEC SE PARAMETER INPUT/OUTPUT CODE 1AL- 284
PARRVCEC SE PARAMETER RANGE/VALUE CODE 1AF- 284

TABLE ED, SUPPORT EQUIPMENT AUTHORIZATION


73. This table allows documenting specific activities and quantities to which the SE item is to be authorized,
as well as the location of each activity. Table keys are SE Reference Number (SEREFNEA), SE CAGE
(SECAGEEA) and Activity Name/Location (ACTNAMED).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
ACTNAMED ACTIVITY NAME/LOCATION 50 X L - 399 K
TYPACTED TYPE OF ACTIVITY 15 X L - 399
NUMACTED NUMBER OF ACTIVITIES 3NR- 399
SEQTYAED SE QUANTITY PER ACTIVITY 3NR- 399

TABLE EE, SUPPORT EQUIPMENT NARRATIVE


74. This table is used to document different types of narrative text for SE. Each type of narrative is
dependent upon the SE CAGE Code (SECAGEEA) and SE Reference Number (SEREFNEA) as migrating
keys from table EA. Additional keys include SE Narrative Text Sequencing Code (TEXSEQEE) and SE
Narrative Code (SENARCEE). The SE Narrative Codes (DED 414) correspond to the different types of
narratives. The following list gives each of these codes, related narrative title, and (DED) number to refer to
for an understanding of the information that needs to be input:

3A-43
DEF(AUST)5692

CODE NARRATIVE TITLE DED NUMBER


A Functional Analysis 147
B Description and Function of SE 078
C SE Nonproliferation Effort 415
D Characteristics of SE 044
E Installation Factors or Other Facilities 169
F Additional Skills and Special Training Requirements 008
G SE Explanation 411
H Justification 188

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
TEXSEQEE SE NARRATIVE TEXT SEQUENCING CODE 5NR- 450 K
SENARCEE SE NARRATIVE CODE 1AF- 414 K
SEQNAREE SE NARRATIVE 65 X - - ---

TABLE EF, SUPPORT EQUIPMENT RECOMMENDATION DATA


75. This table allows documenting SERD specific information such as, submittal and disposition dates.
Table keys are SE Reference Number (SEREFNEA), SE CAGE Code (SECAGEEA), SERD Number
(SERDNOEF), and SERD Revision (SRDREVEF).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
SERDNOEF SE RECOMMENDATION DATA (SERD) 10 X F - 416 K
NUMBER
SRDREVEF SERD REVISION 2AR- 360 K
STATUSEF SERD STATUS 1AF- 404
INTSUBEF SERD DATE OF INITIAL SUBMISSION 6NF- 071
DTGVDSEF SERD DATE OF GOVERNMENT DISPOSITION 6NF- 071
DTRVSBEF SERD DATE OF REVISION SUBMISSION 6NF- 071

TABLE EG, SUPPORT EQUIPMENT RECOMMENDATION DATA REVISION


REMARKS
76. This table allows documenting, for a SERD revision, the revision letter, revision date, action date, and
revision remarks, which summarize the reason for revision, within a narrative field. For SERDs that have
been revised more than once, this block shall include the revision data and remarks of all previous revisions,
and therefore, serve as a history for the SERD. Table keys are SE Reference Number (SEREFNEA), SE
CAGE Code (SECAGEEA), SERD Number (SERDNOEF), SE Revision (SRDREVEF), and Text Sequencing
Code (TEXSEQEG).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
SERDNOEF SE RECOMMENDATION DATA (SERD) 10 X F - 416 F
NUMBER
SRDREVEF SERD REVISION 2AR- 360 F
TEXSEQEG SERD REVISION TEXT SEQUENCING CODE 5NR- 450 K
REVREMEG SERD REVISION REMARKS 65 X - - 417

3A-44
DEF(AUST)5692

TABLE EH, ALTERNATE NATIONAL STOCK NUMBER


77. This table allows documenting alternate NSNs of items which may be substituted for the subject
Support/Training Equipment item. This information is used specifically by the SERD report (LSA-070).
Table keys are SE Reference Number (SEREFNEA), SE CAGE Code (SECAGEEA), SERD Number
(SERDNOEF), SERD Revision (SRDREVEF), Alternate NSN Federal Supply Classification (ALTFSCEH),
and Alternate NSN National Item Identification Code (ALTNIIEH).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
SERDNOEF SE RECOMMENDATION DATA (SERD) 10 X F - 416 F
NUMBER
SRDREVEF SERD REVISION 2AR- 360 F
ALTFSCEH ALTERNATE NSN FEDERAL SUPPLY 4NF- 253 K
CLASSIFICATION
ALTNIIEH ALTERNATE NSN NATIONAL ITEM 9XF- 253 K
IDENTIFICATION NUMBER

TABLE EI, INPUT POWER SOURCE


78. This table is utilized to document power requirements to operate the support/training equipment under
analysis. Included are voltage levels, frequency ranges, power requirements, phase type, and alternating or
direct current data. Table keys are SE Reference Number (SEREFNEA), SE CAGE Code (SECAGEEA),
and Source Option Number (IPSOPNEI).

a. The Source Option Number should be assigned sequentially from 1 to 99 (manually or


automatically) for each unique set of power requirements for a subject piece of SE.

b. A unique set of power requirements could have only one value different from another set of
power requirements.

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
IPSOPNEI SOURCE OPTION NUMBER 2NR- 168 K
IPACDCEI INPUT POWER SOURCE ALTERNATING 1AF- 168
CURRENT/DIRECT CURRENT
IPFRMXEI INPUT POWER SOURCE FREQUENCY RANGE 3NR- 168
MAXIMUM
IPRGMXEI INPUT POWER SOURCE FREQUENCY RANGE 3NR- 168
MINIMUM
IPSRGMEI INPUT POWER SOURCE OPERATING RANGE 3NR- 168
MAXIMUM
IPOPRGEI INPUT POWER SOURCE OPERATING RANGE 3NR- 168
MINIMUM
IPMXRPEI INPUT POWER SOURCE PERCENT MAXIMUM 4NR2 168
RIPPLE
IPPHASEI INPUT POWER SOURCE PHASE 1NF- 168
IPPOWREI INPUT POWER SOURCE WATTS 5NR- 168

TABLE EJ, SUPPORT EQUIPMENT DESIGN DATA


79. This table allows documenting detailed cost, requirement, and recommendation information for the
various design data elements (see DED 079). Table keys are SE Reference Number (SEREFNEA), SE
CAGE Code (SECAGEEA), as well as Design Data Category Code (codes for each design data element)
(DSNDATEJ).

3A-45
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
DSNDATEJ DESIGN DATA CATEGORY CODE (DDCC) 1AF- 079 K
CNTRECEJ DDCC CONTRACTOR RECOMMENDED 1AF- 057
ESTPRCEJ DDCC ESTIMATED PRICE 8NR- 101
GOVRQDEJ DDCC GOVERNMENT REQUIRED 1AF- 150
DDCCSCEJ DDCC SCOPE 40 X - - 365

TABLE EK, SUPERCEDURE DATA


80. This table provides information about the item replacing, or being replaced, by the SE item under
analysis. This information is normally regulated by SERD number, but may be governed by reference
number and CAGE. Table keys are SE Reference Number (SEREFNEA), SE CAGE Code (SECAGEEA),
as well as Supersedure CAGE Code (SPRCAGEK) and Supersedure Reference Number (SPRREFEK),
which migrate from table HA and are given the role name "Supersedure".

Note:

1. It is mandatory that the Supersedure Type element (SUTYPEEK) be completed.

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
SPRCAGEK SE SUPERCEDURE CAGE CODE 5XF- 046 F
SPRREFEK SE SUPERCEDURE REFERENCE NUMBER 32 X L - 337 F
SUTYPEEK SE SUPERCEDURE TYPE 1AF- 408 M
SUPITNEK SE SUPERCEDURE ITEM NAME 19 X L - 182
SUSRNOEK SE SUPERCEDURE SERD NUMBER 10 X F - 416
REASUPEK REASON FOR SUPERCEDURE/DELETION 2XF- 327
ICCODEEK SUPERSEDURE INTERCHANGEABILITY CODE 2AF- 172

TABLE EL, SUPPORT EQUIPMENT INTEGRATED LOGISTIC SUPPORT


REQUIREMENT CATEGORY CODE
81. This table allows documenting the element(s) of ILS which are required or recommended to be
addressed for the SE item. Also included are the estimated price, whether government required or
contractor recommended, and a scope (normally a data item description) for each ILS element documented.
Table keys are SE Reference Number (SEREFNEA), SE CAGE Code (SECAGEEA), as well as SE ILS
Requirement Category Code (IRCCODEL).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
IRCCODEL INTEGRATED LOGISTIC SUPPORT 1AF- 171 K
REQUIREMENTS CATEGORY CODE (IRCC)
CONRECEL IRCC CONTRACTOR RECOMMENDED 1AF- 057
ESTPRCEL IRCC ESTIMATED PRICE 8NR- 101
GOVRQDEL IRCC GOVERNMENT REQUIRED 1AF- 150
IRCSCOEL IRCC SCOPE 40 X - - 365

TABLE EM, SYSTEM EQUIPMENT


82. This table allows documenting items which are components of the system/equipment and are necessary
to be used in conjunction with the SE item to perform its intended function. For example, a wiring harness

3A-46
DEF(AUST)5692

with the same part number as the one used on the system/equipment might be required at test bench in
order to fault isolate a line replaceable unit (LRU). This wiring harness would be considered a required piece
of system equipment. Table Keys include System CAGE (SCAGECEM) and System Reference Number
(SREFNOEM) (both migrate from table HA, but are given "System" role name), and SE CAGE Code
(SECAGEEA) and SE Reference Number (SEREFNEA) (migrate from table EA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
SCAGECEM SYSTEM CAGE CODE 5XF- 046 F
SREFNOEM SYSTEM REFERENCE NUMBER 32 X L - 337 F
QTYTSTEM SYSTEM EQUIPMENT QUANTITY PER TEST 3NR- 320
GFAEIDEM SYSTEM EQUIPMENT ITEM DESIGNATOR 26 X L - 179

3A-47
DEF(AUST)5692

UNIT UNDER TEST REQUIREMENTS AND DESCRIPTION


83. Data tables beginning with "U" in the first position of the table code are structured to identify the UUT
and those hardware and software elements required to test the UUT with off-line support/test equipment.
The unique combination of these elements required for a specific UUT and support/test equipment
configuration is a Test Program Set (TPS). In addition to defining the TPS elements, this information
provides the configuration identification of the UUT (i.e. the UUT and the support/test equipment to be used
in the test). This information is established for each UUT which has a requirement to be tested by the
support/test equipment documented. Additionally, Calibration and Measurement Requirement Summary
(CMRS) information is captured in these tables. Figure 6 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


UA Article Requiring Support/Unit Under Test
UB Unit Under Test Support Equipment
UC Operational Test Program
UD Unit Under Test Support Equipment Operational Test Program
UE Test Program Instruction
UF Unit Under Test Explanation
UG Unit Under Test Parameter Group
UH Unit Under Test Fault Isolated Replaceable Unit
UI Adaptor Interconnector Device
UJ Unit Under Test Support Equipment Adaptor Interconnector Device
UK Automatic Test Equipment Test Station
UL Unit Under Test Support Equipment Automatic Test Equipment
UM Support Equipment Item Unit Under Test
UN Support Equipment Unit Under Test Parameter Group

3A-48
DEF(AUST)5692

Figure 6 U Table Relationships

TABLE UA, ARTICLE REQUIRING SUPPORT/UNIT UNDER TEST


84. This table identifies the UUT which is a component of weapon system breakdown structure. A UUT can
be either a component of the system/equipment or a piece of complex SE itself which must be documented
under the end article (weapon system) for contractual or provisioning purposes. Table keys are migrated
from table XB, but are given the role name "UUT" to distinguish them (UUTLCNUA, UUTALCUA, and
UTLCNTUA). The EIAC must be the same as in table XB, therefore it, is not role named.

Note:

1. The keys (EIACODXA, UUTLCNUA, UUTALCUA, and UTLCNTUA) must have a matching set of identical values
already established in table CA (Task Requirement).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F

3A-49
DEF(AUST)5692

UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18 X L - 199 F


UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
UTALLOUA UUT ALLOWANCE 10 X L - 016
UMNTPLUA UUT MAINTENANCE PLAN NUMBER 23 X L - 209
UTTRDNUA UUT TEST REQUIREMENTS DOCUMENT 15 X L - 448
NUMBER
UTWPRFUA UUT WORK PACKAGE REFERENCE 6XL- 515

TABLE UB, UNIT UNDER TEST SUPPORT EQUIPMENT


85. This table serves as the tie-in between the SE and the UUT. Keys are migrated into table UB from the
EA and UA tables. Table keys are EIAC (EIACODXA), UUT LCN (UUTLCNUA), UUT ALC (UUTALCUA),
UUT LCN Type (UTLCNTUA), SE Reference Number (SEREFNEA), and SE CAGE Code (SECAGEEA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18 X L - 199 F
UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
UTSTCDUB UUT CALIBRATION/MEASUREMENT 1AF- 036
REQUIREMENT SUMMARY (CMRS) STATUS
UTCMRSUB UUT CMRS RECOMMENDED CODE 1XF- 035

TABLE UC, OPERATIONAL TEST PROGRAM


86. This table allows documenting identification and cost data pertaining to the Operational Test Program
(OTP). The OTP is used in conjunction with another support equipment item, normally ATE. This table
provides supporting information to the UD table. Keys are migrated from the HA table and given the role
name "OTP" to distinguish them (OTPCAGUC and OTPREFUC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


OTPCAGUC OPERATIONAL TEST PROGRAM (OTP) CAGE 5XF- 046 F
CODE
OTPREFUC OTP REFERENCE NUMBER 32 X L - 337 F
OTPACRUC OTP APPORTIONED UNIT COST RECURRING 8NR- 025
OTPACNUC OTP APPORTIONED UNIT COST 8NR- 025
NONRECURRING
OTPCTPUC OTP COORDINATED TEST PLAN 1XF 060
OTPSFCUC OTP STANDARDS FOR COMPARISON 1XF 402
OTPSRDUC OTP SUPPORT EQUIPMENT 10 X F - 416
RECOMMENDATION DATA NUMBER

TABLE UD, UNIT UNDER TEST SUPPORT EQUIPMENT OPERATIONAL TEST


PROGRAM
87. This table ties together the relationship between the SE, UUT, and the OTP to maintain the specific
application of the OTP. Table keys are EIAC (EIACODXA), UUT LCN (UUTLCNUA), UUT ALC
(UUTALCUA), UUT LCN Type (UTLCNTUA), SE Reference Number (SEREFNEA), SE CAGE Code
(SECAGEEA) (these migrate from the UB table), and OTP Reference Number (OTPREFUC) and OTP
CAGE Code (OTPCAGUC), which migrate from the UC table.

3A-50
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18 X L - 199 F
UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
OTPCAGUC OPERATIONAL TEST PROGRAM (OTP) CAGE 5XF- 046 F
CODE
OTPREFUC OTP REFERENCE NUMBER 32 X L - 337 F

TABLE UE, TEST PROGRAM INSTRUCTION


88. This table allows documenting basic identification and cost information pertaining to a test program
instruction (TPI). The TPI is used as an aid in the use of an OTP. Table keys are migrated from the HA
table and given the role name "TPI" to form the following keys: TPI Reference Number (TPIREFUE) and TPI
CAGE Code (TPICAGUE). Also, the keys from table UC (OTP CAGE and Reference Number) are migrated
in as foreign keys.

CODE DATA ELEMENT TITLE FORMAT DED KEY


OTPCAGUC OPERATIONAL TEST PROGRAM (OTP) CAGE 5XF- 046 F
CODE
OTPREFUC OTP REFERENCE NUMBER 32 X L - 337 F
TPICAGUE TEST PROGRAM INSTRUCTION (TPI) CAGE 5XF- 046 F
CODE
TPIREFUE TPI REFERENCE NUMBER 32 X L - 337 F
TPAUCRUE TPI APPORTIONED UNIT COST RECURRRING 8NR- 025
TPAUCNUE TPI APPORTIONED UNIT COST 8NR- 025
NONRECURRING
TPISTSUE TPI SELF TEST 1AF- 370
TPITDPUE TPI TECHINCAL DATA PACKAGE 1AF 434
TPISRDUE TPI SUPPORT EQUIPMENT 10 X F - 416
RECOMMENDATION DATA NUMBER

TABLE UF, UNIT UNDER TEST EXPLANATION


89. Narrative statements may be entered in this table to further explain, justify, or substantiate any data entry
concerning UUT (U tables) related data elements. When the information is related to a specific data
element, the explanation should be prefaced with a reference to that element. Table keys are migrated from
table UA and include EIAC (EIACODXA), UUT LCN (UUTLCNUA), UUT ALC (UUTALCUA), and UUT LCN
Type (UTLCNTUA). Also, Text Sequencing Code (TEXSEQUF) is a key attribute.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18 X L - 199 F
UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
TEXSEQUF UUT EXPLANATION TEXT SEQUENCING CODE 5 N R - 450 K
UTEXPLUF UUT EXPLANATION 65 X - - 498

TABLE UG, UNIT UNDER TEST PARAMETER GROUP


90. This table allows documenting specific information about individual parameters which the unit under test
requires to have measured, generated, etc, by the support equipment. This table is used when the UUT is a
subelement of the system/equipment (CMRS category I item), as opposed to being another piece of support

3A-51
DEF(AUST)5692

equipment, with one exception. This table can be used to document parameters for a piece of complex SE
which is an LSA candidate, thereby, making it the UUT. Table keys are EIAC (EIACODXA), UUT LCN
(UUTLCNUA), UUT ALC (UUTALCUA), UUT LCN Type (UTLCNTUA), SE Reference Number (SEREFNEA),
and SE CAGE Code (SECAGEEA).

Note:

1. The UUT Parameter Grouping Code (UUTPGCUG) and the SE Parameter Grouping Code (PARGPCEC) (table
EC) provide the common link between the parameters that need to be tested by the UUT and the parameters that
the piece of SE can test. Therefore, the values for UUTPGCUG and PARGPCEC must be identical to link the
UUT to the corresponding piece of SE.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18 X L - 199 F
UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
UUTPGCUG UUT PARAMETER GROUP CODE 2AF- 284 K
UUTPPCUG UUT CALIBRATION MEASUREMENT 1AF- 034
REQUIRMENT SUMMARY PARAMETER CODE
UUTPACUG UUT PARAMETER ACCURACY 26 X L - 284
UUTPIOUG UUT PARAMETER INPUT/OUTPUT CODE 1AF- 284
UUTPSOUG UUT PARAMETER 1AF- 284
OPERATIONAL/SPECIFICATION CODE
UUTPARUG UUT PARAMETER 12 X L - 284
UUTPRFUG UUT PARAMETER RANGE FROM 10 D - - 284
UUTPRTUG UUT PARAMETER RANGE TO 10 D - - 284
UUTPRVUG UUT PARAMETER RANGE/VALUE CODE 1AF- 284
UUTPTAUG UUT PARAMETER TEST ACCURACY RATIO 1XF- 442
(TAR) ACTUAL
UUTPTDUG UUT PARAMETER TAR DESIRED 1XF- 442

TABLE UH, UNIT UNDER TEST FAULT ISOLATED REPLACEABLE UNIT


91. This table allows documenting the relationship between SE, UUT, task provisioned items, and Fault
Isolated Replaceable Units (FIRU). The FIRU is an item which is subordinate to the UUT LCN (UUTLCNUA)
and the Task LCN (TSKLCNCI) in hardware breakdown. In fact, the UUT LCN and the Task LCN are one in
the same and therefore, must be identical to each other. This table also allows documenting the percentage
of faults which can be isolated to a given ambiguity group (up to two groups) and its respective number of
items per ambiguity group. Table keys include those which originate in table CI (EIACODXA, TSKLCNCI,
TSKALCCI, TSKLTYCI, TSKTCDCI, PROLCNCI, PROALCCI, PROLTYCI, PROCAGCI, and PROREFCI)
and are migrated to table UH. Keys from table EA migrate down as nonidentifying.

a. PROLCNCI must be subordinate to TSKLCNCI.

b. PROLCNCI identifies the FIRU item.

c. To qualify as an FIRU, the PROLCNCI must have an ICC of X, Y, 9, AA, or AB (identified in


table HG) and must be identifiable through fault isolation procedures for the TSKLCNCI.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
TSKLCNCI TASK LSA CONTROL NUMBER (LCN) 18 X L - 199 F
TSKALCCI TASK ALTERNATE LCN CODE (ALC) 2NF- 019 F
TSKLTYCI TASK LCN TYPE 1AF- 203 F
TSKTCDCI TASK PROVISION TASK CODE 7XF- 427 F
PROLCNCI TASK PROVISION LCN 18 X L - 199 F
PROALCCI TASK PROVISION ALC 2NF- 019 F
PROLTYCI TASK PROVISION LCN TYPE 1AF- 203 F

3A-52
DEF(AUST)5692

PROCAGCI TASK PROVISION CAGE CODE 5XF- 046 F


PROREFCI TASK PROVISION REFERENCE NUMBER 32 X L - 337 F
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046
SEREFNEA SE REFERENCE NUMBER 32 X L - 337
UUTFA1UH UUT FIRU AMBIGUITY GROUP 1 2NR- 143
UUTFA2UH UUT FIRU AMBIGUITY GROUP 2 2NR- 143
UUTFP1UH UUT FIRU PERCENT FAILURE 1 3NR1 143
UUTFP2UH UUT FIRU PERCENT FAILURE 2 3NR1 143
UUTFTDUH UUT FIRU TEST REQUIREMENTS DOCUMENT 1AF- 447
INDICATOR

TABLE UI, ADAPTOR INTERCONNECTOR DEVICE


92. This table contains pricing and identification information about items which are utilized to interface the
UUT with the SE. The table keys are migrated from table HA and given the role names Adaptor
Interconnector Device (AID) Reference Number (AIDREFUI) and AID CAGE Code (AIDCAGUI).

CODE DATA ELEMENT TITLE FORMAT DED KEY


AIDCAGUI ADAPTOR INTERCONNECTOR DEVICE (AID) 5XF- 046 F
CAGE CODE
AIDREFUI AID REFERENCE NUMBER 32 X L - 337 F
AIDUCNUI AID APPORTIONED UNIT COST 8NR- 025
NONRECURRING
AIDUCRUI AID APPORTIONED UNIT COST RECURRING 8NR- 025
AIDSRDUI AID SERD NUMBER 10 X F - 416
AIDCUTUI AID COMMON UNIT UNDER TEST 2NR- 048

TABLE UJ, UNIT UNDER TEST SUPPORT EQUIPMENT ADAPTOR


INTERCONNECTOR DEVICE
93. This table cross-references data pertaining to the relationship between the SE, AID, and the UUT. Table
keys include the CAGE and Reference Number for the AID (AIDCAGUI and AIDREFUI respectively) from
table UI and the keys migrated from table UB which are EIAC (EIACODXA), UUT LCN (UUTLCNUA), UUT
ALC (UUTALCUA), UUT LCN Type (UTLCNTUA), SE Reference Number (SEREFNEA), and SE CAGE
Code (SECAGEEA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18 X L - 199 F
UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
AIDCAGUI ADAPTOR INTERCONNECTOR DEVICE (AID) 5XF- 046 F
CAGE CODE
AIDREFUI AID REFERENCE NUMBER 32 X L - 337 F

TABLE UK, AUTOMATIC TEST EQUIPMENT TEST STATION


94. This table is used to document identification and government designator information concerning the
Automatic Test Equipment (ATE) Test Station required on a SERD summary. Table keys are migrated from
table HA and given role names of ATE Reference Number (ATEREFUK) and ATE CAGE Code
(ATECAGUK).

3A-53
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


ATECAGUK AUTOMATIC TEST EQUIPMENT (ATE) CAGE 5XF- 046 F
CODE
ATEREFUK ATE REFERENCE NUMBER 32 X L - 337 F
ATEGDSUK ATE GOVERNMENT DESIGNATOR 20 X L - 149

TABLE UL, UNIT UNDER TEST SUPPORT EQUIPMENT AUTOMATIC TEST


EQUIPMENT
95. This table cross-references the ATE Test Station (table UK) data with the UUT SE (table UB). Table
keys are ATE Reference Number (ATEREFUK) and ATE CAGE Code (ATECAGUK) migrated from table UK
and the keys migrated from table UB which are EIAC (EIACODXA), UUT LCN (UUTLCNUA), UUT ALC
(UUTALCUA), UUT LCN Type (UTLCNTUA), SE Reference Number (SEREFNEA) and SE CAGE Code
(SECAGEEA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18 X L - 199 F
UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF- 046 F
SEREFNEA SE REFERENCE NUMBER 32 X L - 337 F
ATECAGUK AUTOMATIC TEST EQUIPMENT (ATE) CAGE 5XF- 046 F
CODE
ATEREFUK ATE REFERENCE NUMBER 32 X L - 337 F

TABLE UM, SUPPORT EQUIPMENT ITEM UNIT UNDER TEST


96. This table identifies pieces of SE (Calibration and Measurement Requirement Summary (CMRS)
category II items) that are linked with CMRS category III items (SE in support of the category II SE).
Normally, Tables UM and UN are only used if a CMRS (LSA-076) is required on contract. Table keys are
migrated down from the EA table (Support Equipment) and given a role name of Support Equipment Unit
Under Test to distinguish them (SUTCAGUM and SUTREFUM).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SUTCAGUM SE UNIT UNDER TEST (SE UUT) CAGE CODE 5XF- 046 F
SUTREFUM SE UUT REFERENCE NUMBER 32 X L - 337 F
SUTALLUM SE UUT ALLOWANCE 10 X L - 016
SUTSTCUM SE UUT CMRS STATUS 1AF- 036
MNTPLNUM SE UUT MAINTENANCE PLAN NUMBER 23 X L - 209
TRDNUMUM SE UUT TEST REQUIREMENTS DOCUMENT 15 X L - 448
NUMBER
WKPKRFUM SE UUT WORK PACKAGE REFERENCE 6XL 515

TABLE UN, SUPPORT EQUIPMENT UNIT UNDER TEST PARAMETER GROUP


97. This table allows documenting specific information about individual parameters which a piece of support
equipment (SE) (CMRS category II) requires to have calibrated, measured, etc. by another piece of SE
(CMRS category III item). Data from this table will be used on the CMRS Report (LSA-076). Table keys
include the SE UUT Parameter Group Code (SEUPGCUN), keys migrated from table EA and given role
names of "Testing" (TGSCAGUN and TGSREFUN), and keys from table UM are also migrated into this table
(SUTREFUM and SUTCAGUM).

3A-54
DEF(AUST)5692

Note:

1. The SE UUT Parameter Grouping Code (SEUPGCUN) and the SE Parameter Grouping Code (PARGPCEC)
(table EC) provide the link between the parameters of CMRS category III items and category II items,
respectively. Therefore, the values for PARGPCEC and SEUPGCUN must be identical to link the SE UUT to the
corresponding piece of testing SE.

CODE DATA ELEMENT TITLE FORMAT DED KEY


TGSCAGUN TESTING SUPPORT EQUIPMENT (SE) CAGE 5 X F - 046 F
CODE
TGSREFUN TESTING SE REFERENCE NUMBER 32 X L - 337 F
SUTCAGUM SE UNIT UNDER TEST (SE UUT) CAGE CODE 5 X F - 046 F
SUTREFUM SE UUT REFERENCE NUMBER 32 X L - 337 F
SEUPGCUN SE UUT PARAMETER GROUP CODE 2AF- 284 K
UTPACMUN SE UUT CMRS PARAMETER CODE 1AF- 034
UTPAACUN SE UUT PARAMETER ACCURACY 26 X L - 284
UTPAIOUN SE UUT PARAMETER INPUT/OUTPUT CODE 1 A F - 284
UTPAPAUN SE UUT PARAMETER 12 X L - 284
UTRGFRUN SE UUT PARAMETER RANGE FROM 10 D - - 284
UTPRRTUN SE UUT PARAMETER RANGE TO 10 D - - 284
UTPARVUN SE UUT PARAMETER RANGE/VALUE CODE 1AF- 284
UTPATAUN SE UUT PARAMETER TEST ACCURACY RATIO 1 X F - 442
(TAR) ACTUAL
UTPATDUN SE UUT PARAMETER TAR DESIRED 1XF- 442

3A-55
DEF(AUST)5692

FACILITIES CONSIDERATIONS
98. Data tables beginning with "F" in the first position of the table code are structured to describe and justify
all proposed special and additional facilities requirements, which are indicated as a result of the
operational/maintenance task analysis. Figure 7 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


FA Facility
FB Facility Narrative
FC Baseline Facility Narrative
FD New or Modified Facility Narrative
FE Operations and Maintenance Task Facility Requirement

Figure 7 F Table Relationships

TABLE FA, FACILITY


99. This table identifies the facility by name, category code and type that the system/equipment under
analysis requires. The table keys are Facility Name (FACNAMFA), Facility Category Code (FACCCDFA),
and Facility Type (FACTYPFA). For a given row of information, the following cross-element edits apply to
table FA:

a. Facility Area (FAAREAFA) and Facility Area UM (FAARUMFA) must either both be blank, or
both have entries.

b. Facility Construction Unit of Measure Price (FACNCOFA) and Facility Construction Unit of
Measure (CONUOMFA) must either both be blank, or both have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


FACNAMFA FACILITY NAME 32 X L - 118 K
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 K
FACTYPFA FACILITY TYPE 1AF- 483 K
FACCLAFA FACILITY CLASS 19 X L - 116
DRCLASFA FACILITY DRAWING CLASSIFICATION 3X-- 088
FADNUMFA FACILITY DRAWING NUMBER 32 X L - 089

3A-56
DEF(AUST)5692

FADREVFA FACILITY DRAWING REVISION 2AR- 360


FAAREAFA FACILITY AREA 6NR- 112
FAARUMFA FACILITY AREA UNIT OF MEASURE 2AF- 491
FACNCOFA FACILITY CONSTRUCTION UNIT OF MEASURE 10 N R 2 492
PRICE
CONUOMFA CONSTRUCTION UNIT OF MEASURE 2AF- 491

TABLE FB, FACILITY NARRATIVE


100. This table may be used to identify Facility Capability, and Facility Location of either the baseline facility
or the new or modified facility. The table keys consist of Facility Name (FACNAMFA), Facility Category
Code (FACCCDFA), Facility Type (FACTYPFA), Facility Narrative Code (FNCODEFB), and Facility Narrative
Text Sequencing Code (TEXSEQFB). For a given row of information, the following cross-element edits
apply to table FB:

a. If the Facility Narrative Code (FNCODEFB) is (A), then this table identifies the capacity impact
on the work load of the facility (Facility Capability, DED 114).

b. If the Facility Narrative Code (FNCODEFB) is (B), then this table identifies the existing depot
facility in terms of where the facility is located (e.g., depot name, building, bay, etc.) (Facility
Location, DED 117).

CODE DATA ELEMENT TITLE FORMAT DED KEY


FACNAMFA FACILITY NAME 32 X L - 118 F
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 F
FACTYPFA FACILITY TYPE 1AF- 483 F
FNCODEFB FACILITY NARRATIVE CODE 1AF- 119 K
TEXSEQFB FACILITY NARRATIVE TEXT SEQUENCING 5NR- 450 K
CODE
FACNARFB FACILITY NARRATIVE 65 X - - ---

TABLE FC, BASELINE FACILITY NARRATIVE


101. This table may be used to identify Facility Maintenance Requirements, Facility Requirements for
Operations, Facility Training Requirement, Facility Requirements Special Considerations, and Facility
Requirements Supply and Storage for a baseline facility. Baseline is describing the requirements needed for
a facility, this applies to both an existing facility and a new or modified facility. The table keys consist of
Baseline Facility Name (FACNAMFC), Baseline Facility Category Code (FACCCDFC), Baseline Facility Type
(FACTYPFC), Baseline Facility Narrative Code (FBNACDFC), and Baseline Facility Narrative Text
Sequencing Code (TEXSEQFC). For a given row of information, the following cross-element edits apply to
table FC:

a. If Baseline Facility Narrative Code (FBNACDFC) is (A), then this table identifies the
maintenance concept for the system/equipment under analysis and the facilities that are
required to maintain the system (Facilities Maintenance Requirement, DED 107).

b. If Baseline Facility Narrative Code (FBNACDFC) is (B), then this table identifies what facilities
are needed to support the system in its daily use (Facilities Requirements For Operations,
DED 109).

c. If Baseline Facility Narrative Code (FBNACDFC) is (C), then this table identifies what facilities
are needed for training (Facilities Requirement for Training, DED 110).

d. If Baseline Facility Narrative Code (FBNACDFC) is (D), then this table describes any special
considerations which impact facility requirements (Facility Requirements Special
Considerations, DED 120).

3A-57
DEF(AUST)5692

e. If Baseline Facility Narrative Code (FBNACDFC) is (E), then this table describes where the
system/equipment will be stored, or if there is an impact in other storage facilities (Facility
Requirements Supply/Storage, DED 121).

CODE DATA ELEMENT TITLE FORMAT DED KEY


FACNAMFC BASELINE FACILITY NAME 32 X L - 118 F
FACCCDFC BASELINE FACILITY CATEGORY CODE 6NL- 115 F
FACTYPFC BASELINE FACILITY TYPE 1AF- 483 F
FBNACDFC BASELINE FACILITY NARRATIVE CODE 1AF- 113 K
TEXSEQFC BASELINE FACILITY NARRATIVE TEXT 5NR- 450 K
SEQUENCING CODE
FABNARFC BASELINE FACILITY NARRATIVE 65 X - - ---

TABLE FD, NEW OR MODIFIED FACILITY NARRATIVE


102. This table contains information about modifications of existing facilities or requirements for new
facilities. This table may be used to identify Facility Design Criteria, Facility Installation Lead Time, Facility
Task Area Breakdown, Facility Utilization, Facility Requirements, Facility Unit Cost Rationale, Facility
Justification, Type of Construction, and Utilities Requirement. The table keys consist of New or Modified
Facility Name (FACNAMFD), New or Modified Facility Category Code (FACCCDFD), New or Modified
Facility Type (FACTYPFD), New or Modified Facility Narrative Code (NMFNCDFD), and Text Sequencing
Code (TEXSEQFD). For a given row of information, the following cross-element edits apply to Table FD:

a. If the New or Modified Facility Narrative Code (NMFNCDFD) is (A), then this table describes the
facility design requirements necessary to support the item under analysis (Facility Design
Criteria, DED 105).

b. If the New or Modified Facility Narrative Code (NMFNCDFD) is (B), then this table describes the
facilities installation lead time schedules for contractor produced and installed support, test
equipment, and training devices (Facility Installation Lead Time, DED 106).

c. If the New or Modified Facility Narrative Code (NMFNCDFD) is (C), then this is a narrative
description identifying the breakdown of a new or modified facility for the area by individual
tasks at the job level to determine maximum use of space (Facility Task Area Breakdown,
DED 122).

d. If the New or Modified Facility Narrative Code (NMFNCDFD) is (D), then this is a table
describing the new or modified facility utilization rate (Facilities Utilization, DED 111).

e. If the New or Modified Facility Narrative Code (NMFNCDFD) is (E), then this table describes the
location of and the functions to be performed at the new or modified facility (Facilities
Requirements, DED 108).

f. If the New or Modified Facility Narrative Code (NMFNCDFD) is (F), then this is a narrative field
identifying variations to the appropriate unit cost contained in the military construction guides
(Facility Unit Cost Rationale, DED 123).

g. If the New or Modified Facility Narrative Code (NMFNCDFD) is (G), then this is a narrative field
which identifies the major factors which led to the decision that a new facility was required
(Facility Justification, DED 188).

h. If the New or Modified Facility Narrative Code (NMFNCDFD) is (H), then this table describes
what type of construction is required at a new or modified facility (Type of Construction, DED
482).

i. If the New or Modified Facility Narrative Code (NMFNCDFD) is (I), then this is a narrative
description identifying an estimate of the utilization required for a new or modified facility
(Utilities Requirement, DED 502).

3A-58
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


FACNAMFD NEW OR MODIFIED FACILITY NAME 32 X L - 118 F
FACCCDFD NEW OR MODIFIED FACILITY CATEGORY 6NL- 115 F
CODE
FACTYPFD NEW OR MODIFIED FACILITY TYPE 1AF- 483 F
NMFNCDFD NEW OR MODIFIED FACILITY NARRATIVE 1AF- 255 K
CODE
TEXSEQFD NEW OR MODIFIED FACILITY NARRATIVE 5NR- 450 K
TEXT SEQUENCING CODE
NMFNARFD NEW OR MODIFIED FACILITY NARRATIVE 65 X - - ---

TABLE FE, OPERATIONS AND MAINTENANCE TASK FACILITY REQUIREMENT


103. This table identifies a need for operations/maintenance facilities for a given task. The table keys
consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Facility
Name (FACNAMFA), Facility Category Code (FACCCDFA), Facility Type (FACTYPFA) and Task Code
(TASKCDCA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
FACNAMFA FACILITY NAME 32 X L - 118 F
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 F
FACTYPFA FACILITY TYPE 1AF- 483 F

3A-59
DEF(AUST)5692

PERSONNEL SKILL CONSIDERATIONS


104. Data tables beginning with "G" in the first position of the table code are structured to describe and
justify any new or modified personnel skills required to support the system/equipment. Figure 8 depicts the
data relationships for these tables.

TABLE CODE TABLE TITLE


GA Skill Specialty
GB New or Modified Skill
GC New or Modified Skill Narrative
GD Skill Aptitude Data
GE Physical and Mental Requirements Narrative

Figure 8 G Table Relationships

TABLE GA, SKILL SPECIALTY


105. This table contains information about military and civilian skill specialties. The table key is SSC
(SKSPCDGA). For a given row, Hour Labour Rate (HRLARTGA) is per SSC (SKSPCDGA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


SKSPCDGA SKILL SPECIALTY CODE 7XL- 387 K
SKLVCDGA SKILL LEVEL CODE 1AF- 386
HRLARTGA HOUR LABOUR RATE 4NR2 161
TRNCOSGA TRAINING COST 7NR2 460

3A-60
DEF(AUST)5692

TABLE GB, NEW OR MODIFIED SKILL


106. This table contains information about new or modified skill requirements. The key for this table is New
or Modified SSC (MDCSSCGB). For a given row of information, the following cross-element edits apply to
table GB:

a. SSC (SKSPCDGA) is migrated into this table as nonidentifying key which means that this key is
not required to uniquely identify an instance of the entity.

b. A Security Clearance (SCRSSCGB) is required for each New or Modified SSC (MDCSSCGB).

c. ASVAB AFQT Expected Range Low (AAEXRLGB) and High (AAEXRHGB) are required for
each ASVAB AFQT Score (ABAFQTGB).

d. ASVAB AFQT Lowest Percentage Low (AALPRLGB) and High (AALPRHGB) are required for
each ASVAB AFQT Score (ABAFQTGB).

CODE DATA ELEMENT TITLE FORMAT DED KEY


MDCSSCGB NEW OR MODIFIED SKILL SPECIALTY CODE 7XL- 257 K
MDSCLCGB NEW OR MODIFIED SKILL LEVEL CODE 1AF- 386
SKSPCDGA SKILL SPECIALTY CODE 7XL- 387
DPRNRSGB DUTY POSITION REQUIRING A NEW OR 19 X L - 092
REVISED SKILL
RPPCIVGB RECOMMENDED CIVILIAN GRADE 4XF- 330
RPPMILGB RECOMMENDED MILITARY RANK/RATE 3XF- 330
SCRSSCGB SECURITY CLEARANCE REQUIRED 1NF- 369
SSCTESGB TEST SCORE 3NR- 449
ABAFQTGB ARMED SERVICES VOCATIONAL APTITUDE 2NF- 026
BATTERY (ASVAB) ARMED FORCES
QUALIFICATION TEST (AFQT) SCORE
AAEXRLGB ASVAB AFQT EXPECTED RANGE LOW 2NF- 026
AAEXRHGB ASVAB AFQT EXPECTED RANGE HIGH 2NF- 026
AALPRLGB ASVAB AFQT LOWEST PERCENTAGE - LOW 2NF- 026
AALPRHGB ASVAB AFQT LOWEST PERCENTAGE - HIGH 2NF- 026

TABLE GC, NEW OR MODIFIED SKILL NARRATIVE


107. This table may be used to identify New or Modified Skill Additional Requirements, Educational
Qualifications, Skill Justification, and Additional Training Requirements. The table keys consist of New or
Modified SSC (MDCSSCGB), New or Modified Skill Narrative Code (NMSNCDGC), and New or Modified
Skill Narrative Text Sequencing Code (TEXSEQGC). For a given row of information, the following cross-
element edits apply to table GC:

a. if the New or Modified Skill Narrative Code is (A), then this table describes the new skills that
are required in order to operate and maintain the equipment under analysis (New or Modified
Skill Additional Requirements, DED 007).

b. If the New or Modified Skill Narrative Code is (B), then this table describes the educational
prerequisites recommended to acquire the skill necessary to perform the task (Educational
Qualifications, DED 094).

c. If the New or Modified Skill Narrative Code is (C), then this table identifies the major factors
which led to the decision that training is needed for the new or modified skill (Skill
Justification, DED 188).

d. If the New or Modified Skill Narrative Code is (D), then this table describes the additional
training required for maintenance, operator, and instructor personnel (Additional Training
Requirements, DED 012).

3A-61
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


MDCSSCGB NEW OR MODIFIED SKILL SPECIALTY CODE 7XL- 257 F
NMSNCDGC NEW OR MODIFIED SKILL NARRATIVE CODE 1AF- 256 K
TEXSEQGC NEW OR MODIFIED SKILL NARRATIVE TEXT 5NR- 450 K
SEQUENCING CODE
NMSNARGC NEW OR MODIFIED SKILL NARRATIVE 65 X - - ---

TABLE GD, SKILL APTITUDE DATA


108. This table contains information about Armed Services Vocational Aptitude Battery scores. The table
keys consist of New or Modified Skill Specialty Code (MDCSSCGB) and ASVAB Aptitude Element
(ASVAPEGD).

a. ASVAB Aptitude Element Expected Range Low (AAEERLGD) and High (AAEERHGD) are
required for each ASVAB Aptitude Element (ASVAPEGD).

b. ASVAB Aptitude Element Lowest Percentage Low (AAELPLGD) and High (AAELPHGD) are
required for each ASVAB Aptitude Element (ASVAPEGD).

CODE DATA ELEMENT TITLE FORMAT DED KEY


MDCSSCGB NEW OR MODIFIED SKILL SPECIALTY CODE 7XL- 257 F
ASVAPEGD ASVAB APTITUDE ELEMENT 2AR- 026 K
AAEERLGD ASVAB APTITUDE ELEMENT EXPECTED 3NF- 026
RANGE - LOW
AAEERHGD ASVAB APTITUDE ELEMENT EXPECTED 3NF- 026
RANGE - HIGH
AAELPLGD ASVAB APTITUDE ELEMENT LOWEST 3NF- 026
PERCENTAGE - LOW
AAELPHGD ASVAB APTITUDE ELEMENT LOWEST 3NF- 026
PERCENTAGE - HIGH

TABLE GE, PHYSICAL AND MENTAL REQUIREMENTS NARRATIVE


109. This table contains information which identifies any unique physical/mental personnel attributes
required or recommended as prerequisites to full qualification in the applicable task. The table keys consist
of EIAC (EIACODXA), LCN (LCNCODXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Task Code
(TASKCDCA), Subtask Number (SUBNUMCB), Subtask Person Identifier (SUBPIDCD), New or Modified
SSC (MDCSSCGB), and Physical and Mental Requirements Text Sequencing Code (TEXSEQGE).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMCB SUBTASK NUMBER 3NF- 407 F
SUBPIDCD SUBTASK PERSON IDENTIFIER 3XL- 288 F
MDCSSCGB NEW OR MODIFIED SKILL SPECIALTY CODE 7XL- 257 F
TEXSEQGE PHYSICAL AND MENTAL REQUIREMENTS 5NR- 450 K
TEXT SEQUENCING CODE
PAMENRGE PHYSICAL AND MENTAL REQUIREMENTS 65 X - - 290
NARRATIVE

3A-62
DEF(AUST)5692

PACKAGING AND PROVISIONING REQUIREMENT


110. The following "H" data tables are used to document packaging/provisioning data requirements.
Included in these tables are static parts data (nonapplication dependent) related to provisioning screening
and cataloging, packaging, and common maintenance data. Also included under these data tables are
application data of items used to document the data required for initial support requirements determination,
repair parts manuals, and design change information. Figure 9 depicts the data relationships for these
tables.

TABLE CODE TABLE TITLE


HA Item Identification
HB Additional Reference Number
HC Contractor Technical Information Code (CTIC) CAGE
HD Item Unit of Issue Price
HE Item Unit of Measure Price
HF Item Packaging Requirement
HG Part Application Provisioning
HH Overhaul-Kit Next Higher Assembly PLISN
HI Provisioning Remark
HJ Provisioning Reference Designation
HK Parts Manual Description
HL Parts Manual Provisioning Nomenclature
HM Item Basis of Issue
HN Provisioning Serial Number Usable On Code
HO Provisioning System/End Item Usable On Code
HP Design Change Information
HQ Serial Number Effectivity
HR Design Change Usable On Code

3A-63
DEF(AUST)5692

Figure 9 H Table Relationships

TABLE HA, ITEM IDENTIFICATION


111. This table contains parts information that is not dependent of the part application such as item
identification, cataloging, common maintenance information, special management characteristics and units of
measure and issue. Table keys consist of Reference Number and CAGE (REFNUMHA and CAGECDXH).
For a given row of information, the following cross-element edits apply to table HA:

a. Acquisition Method Suffix Code (AMSUFCHA) is not allowed without Acquisition Method Code
(ACQMETHA).

b. Shelf Life Action Code (SLACTNHA) is not allowed without Shelf Life (SHLIFEHA).

3A-64
DEF(AUST)5692

c. National Item Identification Number (NIINSNHA) is not allowed without Federal Supply
Classification (FSCNSNHA).

d. Unit Length (ULENGTHA), Width (UWIDTHHA), Height (UHEIGHHA) must either be all blank or
all have entries.

e. If UM (UNITMSHA) equals UI (UNITISHA), UI Conversion Factor (UICONVHA) must equal


"00001". Conversely, if UI and UM are not equal, then UI Conversion Factor cannot equal
"00001".

f. If Special Material Content Code (SPMACCHA) is "E", then the Precious Metals Indicator Code
(PMICODHA) cannot be "A".

g. Material Leadtime (MTLEADHA) and Material Weight (MTLWGTHA) are not allowed without
Industrial Materials Analysis of Capacity (INDMATHA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH COMMERCIAL AND GOVERNMENT ENTITY 5XF- 046 F
(CAGE) CODE
REFNUMHA REFERENCE NUMBER 32 X L - 337 K
ITNAMEHA ITEM NAME 19 X L - 182
INAMECHA ITEM NAME CODE 5NF- 183
REFNCCHA REFERENCE NUMBER CATEGORY CODE 1XF- 338
REFNVCHA REFERENCE NUMBER VARIATION CODE 1NF- 339
DLSCRCHA DLSC SCREENING REQUIREMENT CODE 1AF- 073
DOCIDCHA DOCUMENT IDENTIFIER CODE 3AF- 087
ITMMGCHA ITEM MANAGEMENT CODE 1AF- 181
COGNSNHA NATIONAL STOCK NUMBER (NSN) 2XF- 253
COGNIZANCE CODE
SMMNSNHA NSN SPECIAL MATERIAL IDENTIFICATION 2XF- 253
CODE/MATERIEL MANAGEMENT
AGGREGATION CODE
MATNSNHA NSN MATERIEL CONTROL CODE 1XF- 253
FSCNSNHA NSN FEDERAL SUPPLY CLASSIFICATION 4NF- 253
NIINSNHA NSN NATIONAL ITEM IDENTIFICATION 9XF- 253
NUMBER
ACTNSNHA NSN ACTIVITY CODE 2XF- 253
UICONVHA UNIT OF ISSUE CONVERSION FACTOR (UI 5NF- 489
CONVERSION FACTOR)
SHLIFEHA SHELF LIFE (SL) 1XF- 377
SLACTNHA SHELF LIFE ACTION CODE (SLAC) 2XF- 378
PPSLSTHA PROGRAM PARTS SELECTION LIST 1AF- 302
DOCAVCHA DOCUMENT AVAILABILITY CODE 1XF- 086
PRDLDTHA PRODUCTION LEAD TIME 2NR- 299
SPMACCHA SPECIAL MATERIAL CONTENTS CODE (SMCC) 1 X F - 395
SMAINCHA SPECIAL MAINTENANCE ITEM CODE (SMIC) 1 A F - 392
CRITCDHA CRITICALITY CODE 1AF- 066
PMICODHA PRECIOUS METAL INDICATOR CODE 1XF- 293
SAIPCDHA SPARES ACQUISITION INTEGRATED WITH 1AF- 391
PRODUCTION (SAIP)
AAPLCCHA GOVERNMENT FURNISHED PROVISIONING 1AF- 308
LIST CATEGORY CODE (PLCC)
BBPLCCHA INTERIM SUPPORT ITEMS PLCC 1AF- 308
CCPLCCHA LONG LEAD TIME ITEM PLCC 1AF- 308
DDPLCCHA TOOLS AND TEST EQUIPMENT PLCC 1AF- 308
EEPLCCHA COMMON AND BULK ITEM PLCC 1AF- 308
FFPLCCHA REPAIRABLE ITEMS PLCC 1AF- 308
GGPLCCHA INTERIM RELEASED ITEM PLCC 1AF- 308
HHPLCCHA INSTALLATION AND CHECKOUT ITEM PLCC 1AF- 308
JJPLCCHA AUTHORIZATION STOCK LIST ITEM PLCC 1AF- 308
KKPLCCHA RECOMMENDED BUY LIST ITEM PLCC 1AF- 308
LLPLCCHA PRESCRIBED LOAD LIST ITEM PLCC 1AF- 308
MMPLCCHA SYSTEM SUPPORT PACKAGE COMPONENT 1 A F - 308

3A-65
DEF(AUST)5692

LIST PLCC
PHYSECHA PHYSICAL SECURITY PILFERAGE CODE 1XF- 291
ADPEQPHA ADP EQUIPMENT CODE 1NF- 027
DEMILIHA DEMILITARIZATION CODE 1AF- 076
ACQMETHA ACQUISITION METHOD CODE 1NF- 003
AMSUFCHA ACQUISITION METHOD SUFFIX CODE 1XF- 004
HMSCOSHA HAZARDOUS MATERIALS STORAGE COST 8NR- 156
HWDCOSHA HAZARDOUS WASTE DISPOSAL COST 8NR- 157
HWSCOSHA HAZARDOUS WASTE STORAGE COST 8NR- 158
CTICODHA CONTRACTOR TECHNICAL INFORMATION 2A-- 058
CODE
UWEIGHHA UNIT WEIGHT 5X-- 497
ULENGTHA UNIT SIZE LENGTH 4NR1 496
UWIDTHHA UNIT SIZE WIDTH 4NR1 496
UHEIGHHA UNIT SIZE HEIGHT 4NR1 496
HAZCODHA HAZARDOUS CODE 1AF- 154
UNITMSHA UNIT OF MEASURE 2AF- 491
UNITISHA UNIT OF ISSUE (UI) 2AF- 488
LINNUMHA LINE ITEM NUMBER 6XL- 193
CRITITHA CRITICAL ITEM CODE 13 X L - 065
INDMATHA INDUSTRIAL MATERIALS ANALYSIS OF 19 X L - 163
CAPACITY
MTLEADHA MATERIAL LEADTIME 3NR- 219
MTLWGTHA MATERIAL WEIGHT 6NR3 220
MATERLHA MATERIAL 240 X L - 218

TABLE HB, ADDITIONAL REFERENCE NUMBER


112. This table contains Additional Reference Numbers (ARN) that may be used to identify the item of
supply. Table keys include item Reference Number (REFNUMHB) and CAGE (CAGECDHB) from table HA,
additional CAGE (ADCAGEHB) from table XH, and ARN (ADDREFHB). In a given row, when the ARN and
CAGE match the primary Reference Number and CAGE, there must be an entry in Reference Number
Category Code (RNCC) and this entry must be different from the RNCC entry in table HA.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDHB ADDITIONAL REFERENCE NUMBER (ARN) 5XF- 046 F
ITEM CAGE CODE
REFNUMHB ARN ITEM REFERENCE NUMBER 32 X L - 337 F
ADCAGEHB ARN CAGE CODE 5XF- 046 F
ADDREFHB ADDITIONAL REFERENCE NUMBER 32 X L - 006 K
ADRNCCHB ARN REFERENCE NUMBER CATEGORY CODE 1 X F - 338
ADRNVCHB ARN REFERENCE NUMBER VARIATION CODE 1 N F - 339

TABLE HC, CONTRACTOR TECHNICAL INFORMATION CODE (CTIC) CAGE


113. This table contains CTIC CAGEs. Table keys include: item Reference Number (REFNUMHC), and
CAGE (CAGECDHC), from table HA, and CTIC CAGE (CTCAGEHC) from table XH. CTIC (CTICODHA)
must be established in table HA with values of either "-K", "-M", or "-N" for the reference number and CAGE
combination, prior to establishing a value in this table.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDHC ITEM CAGE CODE 5XF- 046 F
REFNUMHC ITEM REFERENCE NUMBER 32 X L - 337 F
CTCAGEHC CTIC CAGE CODE 5XF- 046 F

3A-66
DEF(AUST)5692

TABLE HD, ITEM UNIT OF ISSUE PRICE


114. This table contains UI prices and associated information about the UI price. Table keys include:
Reference Number (REFNUMHA), CAGE (CAGECDXH), and UI Price (UIPRICHD).

a. UI (HA.UNITISHA) must be established in table HA for the Reference Number and CAGE
combination prior to establishing a value in this table.

b. For identical Reference Number and CAGE keys, only one row of information can be
established with a "Y" Provisioning UI Price Code (PROUIPHD).

c. Lot Quantity From (LOTQFMHD) must be less than or equal to Lot Quantity To (LOTQTOHD) in
any row.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
UIPRICHD UNIT OF ISSUE PRICE (UI PRICE) 10 N R 2 490 K
LOTQFMHD UI PRICE LOT QUANTITY FROM 6NR- 205
LOTQTOHD UI PRICE LOT QUANTITY TO 6NR- 205
CURPRCHD UI PRICE CONCURRENT PRODUCTION CODE 1AF- 051
TUIPRCHD UI PRICE TYPE OF PRICE CODE 1AF- 485
PROUIPHD UI PRICE PROVISIONING 1AF- 314
FISCYRHD UI PRICE FISCAL YEAR 2NF- 145

TABLE HE, ITEM UNIT OF MEASURE PRICE


115. This table contains UM prices and associated information about the UM price. Table keys include:
Reference Number (REFNUMHA), CAGE (CAGECDXH), and UM Price (UMPRICHE).

a. UM (HA.UNITMSHA) must be established in table HA for the Reference Number and CAGE
combination prior to establishing a value in this table.

b. For identical Reference Number and CAGE keys, only one row of information can be
established with a "Y" Provisioning UM Price Code (PROUMPHD).

c. Lot Quantity From (LOTQFMHE) must be less than or equal to Lot Quantity To (LOTQTOHE) in
any row.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
UMPRICHE UNIT OF MEASURE (UM) PRICE 10 N R 2 492 K
LOTQFMHE UM PRICE LOT QUANTITY FROM 6NR- 205
LOTQTOHE UM PRICE LOT QUANTITY TO 6NR- 205
CURPRCHE UM PRICE CONCURRENT PRODUCTION CODE1 A F - 051
TUMPRCHE UM PRICE TYPE OF PRICE CODE 1AF- 485
PROUMPHE UM PRICE PROVISIONING 1AF- 314
FISCYRHE UM PRICE FISCAL YEAR 2NF- 145

TABLE HF, ITEM PACKAGING REQUIREMENT


116. This table contains packaging data, as specified by MIL-STD-2073-1 and MIL-STD-2073-2. Table
keys are: Reference Number (REFNUMHA), CAGE (CAGECDXH), and Degree of Protection (DEGPROHF).

a. Unit Pack Length (LENUPKHF), Width (WIDUPKHF) and Depth (DEPUPKHF) must either all be
blank or all have entries for a row of information.

3A-67
DEF(AUST)5692

b. Unit Pack entries must be greater than or equal to Unit Size entries in table HA (LENUPKHF
greater than or equal to ULENGTHA; WIDUPKHF greater than or equal to UWIDTHHA; and,
DEPUPKHF greater than or equal to UHEIGHHA).

c. For numeric entry, Unit Pack Weight (UNPKWTHF) must be greater than or equal to Unit
Weight (UWEIGHHA).

d. Packaging data preparer CAGE (PKCAGEHF) is a nonidentifying key migrating from table XH.

e. When packaging in accordance with special packaging instruction (SPI), enter code ZZ in the
Method of Preservation Code (MEPRESHF) and omit entries in the following fields: Cleaning
and Drying Procedures (CDPROCHF), Preservation Material Code (PRSMATHF), Wrapping
Material (WRAPMTHF), Cushioning and Dunnage Material (CUSHMAHF), Cushioning
Thickness (CUSTHIHF), and Unit Container (UNICONHF).

f. The Container National Stock Number (CONNSNHF) is only the 4th - 16th position of DED 253,
National Stock Number and Related Data.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
DEGPROHF DEGREE OF PROTECTION CODE 1AF- 074 K
UNICONHF UNIT CONTAINER CODE 2XF- 486
UCLEVLHF UNIT CONTAINER LEVEL 1AF- 487
PKGCODHF PACKING CODE 3XF- 283
PACCATHF PACKAGING CATEGORY CODE 4XF- 282
MEPRESHF METHOD OF PRESERVATION CODE 2XF- 239
CDPROCHF CLEANING AND DRYING PROCEDURES 1XF- 045
PRSMATHF PRESERVATION MATERIAL CODE 2XF- 295
WRAPMTHF WRAPPING MATERIAL 2XF- 517
CUSHMAHF CUSHIONING AND DUNNAGE MATERIAL 2XF- 067
CUSTHIHF CUSHIONING THICKNESS 2XF- 068
QTYUPKHF QUANTITY PER UNIT PACK 3X-- 321
INTCONHF INTERMEDIATE CONTAINER CODE 2XF- 174
INCQTYHF INTERMEDIATE CONTAINER QUANTITY 3XF- 175
SPEMRKHF SPECIAL MARKING CODE 2XF- 394
UNPKWTHF UNIT PACK WEIGHT 5X-- 495
LENUPKHF UNIT PACK LENGTH 4NR1 494
WIDUPKHF UNIT PACK WIDTH 4NR1 494
DEPUPKHF UNIT PACK DEPTH 4NR1 494
UNPKCUHF UNIT PACK CUBE 7NR3 493
OPTPRIHF OPTIONAL PROCEDURES INDICATOR 1XF- 279
SPINUMHF SPECICAL PACKAGING INSTRUCTIONS (SPI) 10 X L - 396
NUMBER
SPIREVHF SPI NUMBER REVISION 1NF- 397
SPDATEHF SPI NUMBER JULIAN DATE 5NL- 187
CONNSNHF CONTAINER NSN 13 X F - 253
SUPPKDHF SUPPLEMENTAL PACKAGING DATA 59 X L - 409
PKCAGEHF PACKAGING DATA PREPARER CAGE 5XF- 046

TABLE HG, PART APPLICATION PROVISIONING


117. This table contains parts related information to the part in a specific hardware application. Table keys
include: Reference Number (REFNUMHA), CAGE (CAGECDXH), EIAC (EIACODXA), LCN (LSACONXB),
ALC (ALTLCNXB), and LCN Type (LCNTYPXB).

a. LCN Type must always be "P" (Physical).

b. Maintenance Action Code (MAIACTHG) is not allowed without Maximum Allowable Operating
Time (MAOTIMHG).

3A-68
DEF(AUST)5692

c. Maintenance Task Distribution subfields (OMTDOOHG, FMTDFFHG, HMTDHHHG,


LMTDLLHG, DMTDDDHG, CBDMTDHG, and CADMTDHG) must always total to 100
percent.

d. Replacement Task Distribution subfields (ORTDOOHG, FRTDFFHG, HRTDHHHG,


LRTDLLHG, and DRTDDDHG) must always total to 100 percent.

e. PCCN (PCCNUMXC) and Provisioning List Item Sequence Number (PLISN) (PLISNOHG)
combinations must be unique across all rows of information (PLISNs are mapped to
respective PCCNs in Table XC through table HO).

f. Same as PLISN (SAPLISHG) must be contained in this table as a PLISN (PLISNOHG) having
an identical PCCN. The same as PLISN must be the lowest (EBCDIC value) PLISN in the
table for the same Reference Number, CAGE and PCCN combinations (without an
associated "D" TOCC).

g. Repair Cycle Time (ORCTOOHG, FRCTFFHG, HRCTHHHG, LRCTLLHG, DRCTDDHG and


CONRCTHG) for each Operations/Maintenance (O/M) Level (identified by the first position of
the short name) must be either blank or greater for each higher O/M level. The O/M levels in
ascending order are O, F, H, L, D, and CON (contractor).

h. When numeric, the Quantity Per End Item (QTYPEIHG) must be greater than or equal to the
Quantity Per Assembly (QTYASYHG).

i. Maintenance Task Distribution and Replacement Task Distribution.

(1) OMTDOOHG must be less than or equal to ORTDOOHG.

(2) OMTDOOHG and FMTDFFHG must be less than or equal to ORTDOOHG and
FRTDFFHG.

(3) OMTDOOHG, FMTDFFHG, and HMTDHHHG must be less than or equal to


ORTDOOHG, FRTDFFHG, and HRTDHHHG.

(4) OMTDOOHG, FMTDFFHG, HMTDHHHG, and LMTDLLHG must be less than or equal to
ORTDOOHG, FRTDFFHG, HRTDHHHG, and LRTDLLHG.

(5) OMTDOOHG, FMTDFFHG, HMTDHHHG, LMTDLLHG, and DMTDDDHG must be less


than or equal to ORTDOOHG, FRTDFFHG, HRTDHHHG, LRTDLLHG, and DRTDDDHG.

j. Maintenance Task Distribution and Repair Cycle Time (RCT). When OMTDOOHG,
FMTDFFHG, HMTDHHHG, LMTDLLHG and DMTDDDHG have an entry, then the
corresponding RCT O/M subfield (identified by the first position of the short name) must also
have an entry (ORCTOOHG, FRCTFFHG, HRCTHHHG, LRCTLLHG, and DRCTDDHG).

k. An Allowance Item Quantity (ALIQTYHG) cannot be entered without an Allowance Item Code
(ALLOWCHG).

l. When the Source, Maintenance, and Recoverability (SMR) (SMRCODHG) source code is "PC",
the Shelf Life (SHLIFEHA) in table HA cannot be "0".

m. If the SMR (SMRCODHG) Source Code is "PB", then the Essentiality Code (ESSCODHG)
cannot be "3".

n. If LRU (LRUNITHG) is "Y", then Essentiality Code (ESSCODHG) cannot be "3".

o. If the Special Maintenance Item Code (SMAINCHA) from table HA is "B", and if RCT has
entries, then there must be an entry in the contractor RCT (CONRCTHG). If CONRCTHG is
entered, then SMAINCHA can only be "B".

p. Maintenance Replacement Rate (MRR) I shall be calculated based on the Task Frequency
(Table CA) and the Quantity per Task (Table CI). A change in any of these variables shall
result in an update of the MRRI.

3A-69
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
PLISNOHG PROVISIONING LIST ITEM SEQUENCE 5XL- 309
NUMBER (PLISN)
QTYASYHG QUANTITY PER ASSEMBLY 4X-- 316
SUPINDHG SUPPRESSION INDICATOR 1AF- 422
DATASCHG DATA STATUS CODE 1AF- 070
PROSICHG PROVISIONING SYSTEM IDENTIFIER CODE 3XL- 312
LLIPTDHG LONG LEAD TIME ITEMS LIST (PROVISIONING 1AF- 313
TECHNICAL DOCUMENTATION SELECTION
CODE (PTD))
PPLPTDHG PROVISIONING PARTS LIST (PTD) 1AF- 313
SFPPTDHG SHORT FORM PROVISIONING PARTS LIST 1AF- 313
(PTD)
CBLPTDHG COMMON AND BULK ITEMS LIST (PTD) 1AF- 313
RILPTDHG REPAIRABLE ITEMS LIST (PTD) 1AF- 313
ISLPTDHG INTERIM SUPPORT ITEMS LIST (PTD) 1AF- 313
PCLPTDHG POST CONFERENCE LIST (PTD) 1AF- 313
TTLPTDHG TOOL AND TEST EQUIPMENT LIST (PTD) 1AF- 313
SCPPTDHG SYSTEM CONFIGURATION PROVISIONING 1AF- 313
PARTS LIST (PTD)
ARAPTDHG AS REQUIRED LIST A (PTD) 1AF- 313
ARBPTDHG AS REQUIRED LIST B (PTD) 1AF- 313
TOCCODHG TYPE OF CHANGE CODE (TOCC) 1AF- 481
INDCODHG INDENTURE CODE 1XF- 162
QTYPEIHG QUANTITY PER END ITEM 5X-- 317
PIPLISHG PRIOR ITEM PLISN 5XL- 297
SAPLISHG SAME AS PLISN 5XL- 364
HARDCIHG HARDNESS CRITICAL ITEM 1AF- 151
REMIPIHG REMAIN IN PLACE INDICATOR 1AF- 348
LRUNITHG LINE REPLACEABLE UNIT (LRU) 1AF- 194
ITMCATHG ITEM CATEGORY CODE (ICC) 2XL- 177
ESSCODHG ESSENTIALITY CODE 1NF- 100
SMRCODHG SOURCE, MAINTENANCE AND 6XL- 389
RECOVERABILITY CODE
MRRONEHG MAINTENANCE REPLACEMENT RATE I (MRRI) 8NR4 211
MRRTWOHG MAINTENANCE REPLACEMENT RATE II 8NR3 212
(MRRII)
MRRMODHG MAINTENANCE REPLACEMENT RATE 7XF- 213
MODIFIER
ORTDOOHG ORGANIZATIONAL REPLACEMENT TASK 3NR- 355
DISTRIBUTION (RTD)
FRTDFFHG INTERMEDIATE/DIRECT SUPPORT RTD 3NR- 355
HRTDHHHG INTERMEDIATE/GENERAL SUPPORT RTD 3NR- 355
LRTDLLHG SPECIAL REPAIR ACTIVITY RTD 3NR- 355
DRTDDDHG DEPOT/SHIPYARD RTD 3NR- 355
MINREUHG MINIMUM REPLACEMENT UNIT 3NR- 245
MAOTIMHG MAXIMUM ALLOWABLE OPERATING TIME 4X-- 221
(MAOT)
MAIACTHG MAINTENANCE ACTION CODE (MAC) 1AF- 206
RISSBUHG RECOMMENDED INITIAL SYSTEM STOCK BUY 3NR- 328
RMSSLIHG RECOMMENDED MINIMUM SYSTEM STOCK 3NR- 329
LEVEL
RTLLQTHG RECOMMENDED TENDER LOAD LIST 3NR- 331
QUANTITY
TOTQTYHG TOTAL QUANTITY RECOMMENDED 6NR- 453
OMTDOOHG ORGANIZATIONAL MAINTENANCE TASK 2NR- 214

3A-70
DEF(AUST)5692

DISTRIBUTION (MTD)
FMTDFFHG INTERMEDIATE/DIRECT SUPPORT MTD 2NR- 214
HMTDHHHG INTERMEDIATE/GENERAL SUPPORT MTD 2NR- 214
LMTDLLHG SPECIAL REPAIR ACTIVITY MTD 2NR- 214
DMTDDDHG DEPOT/SHIPYARD MTD 2NR- 214
CBDMTDHG CONDEMNED BELOW DEPOT MTD 2NR- 214
CADMTDHG CONDEMNED AT DEPOT MTD 2NR- 214
ORCTOOHG ORGANIZATIONAL REPAIR CYCLE TIME (RCT) 3NR- 350
FRCTFFHG INTERMEDIATE/DIRECT SUPPORT RCT 3NR- 350
HRCTHHHG INTERMEDIATE/GENERAL SUPPORT RCT 3NR- 350
LRCTLLHG SPECIAL REPAIR ACTIVITY RCT 3NR- 350
DRCTDDHG DEPOT/SHIPYARD RCT 3NR- 350
CONRCTHG CONTRACTOR RCT 3NR- 350
NORETSHG NOT REPAIRABLE THIS STATION 3NR- 261
REPSURHG REPAIR SURVIVAL RATE (RSR) 3NR- 351
DRPONEHG DESIGNATED REWORK POINT (DRP) ONE 6XL- 081
DRPTWOHG DRP TWO 6XL- 081
WRKUCDHG WORK UNIT CODE 7XL- 516
ALLOWCHG ALLOWANCE ITEM CODE 2XF- 017
ALIQTYHG ALLOWANCE ITEM QUANTITY 3NR- 018

TABLE HH, OVERHAUL-KIT NEXT HIGHER ASSEMBLY PLISN


118. This table contains all Next Higher Assembly (NHA), kit or overhaul PLISNs, any associated NHA
PLISN Indicators, and Overhaul Replacement Rates. Table keys include: Reference Number (REFNUMHA),
CAGE (CAGECDXH), EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB)
and NHA PLISN (NHAPLIHH). NHA PLISN must be a PLISN contained in table XC (PLISNOXC) or table
HG (PLISNOHG) with an identical PCCN (PCCNUMXC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
NHAPLIHH NEXT HIGHER ASSEMBLY (NHA) 5XL- 258 K
PROVISIONING LIST ITEM SEQUENCE
NUMBER (PLISN)
NHAINDHH NHA PLISN INDICATOR 1XF- 259
OVHREPHH OVERHAUL REPLACEMENT RATE 3NR2 281

TABLE HI, PROVISIONING REMARK


119. This table contains text remarks associated with a part application for provisioning. Table keys
include: Reference Number (REFNUMHA), CAGE (CAGECDXH), EIAC (EIACODXA), LCN (LSACONXB),
ALC (ALTLCNXB), LCN Type (LCNTYPXB), Provisioning Narrative Code (PRVNACHI), and Provisioning
Text Sequencing Code (TEXSEQHI).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TEXSEQHI PROVISIONING TEXT SEQUENCING CODE 5NR- 450 K
REMARKHI PROVISIONING REMARKS 65 X - - 311

3A-71
DEF(AUST)5692

TABLE HJ, PROVISIONING REFERENCE DESIGNATION


120. This table contains Reference Designations associated with a part application for provisioning. Table
keys include: Reference Number (REFNUMHA), CAGE (CAGECDXH), EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and, Reference Designation (REFDESHJ).
Nonidentifying keys, Technical Manual (TM) Code (TMCODEXI), Figure Number (FIGNUMHK) and Item
Number (ITEMNOHK) migrate from table HK, if applicable, on matching foreign keys.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
REFDESHJ REFERENCE DESIGNATION 64 X L - 335 K
RDCODEHJ REFERENCE DESIGNATION CODE 1AF- 336
TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437
FIGNUMHK FIGURE NUMBER 4XR- 144
ITEMNOHK ITEM NUMBER 4XR- 184

TABLE HK, PARTS MANUAL DESCRIPTION


121. This table contains Repair Parts Manual data associated with a part application for provisioning. Table
keys include: Reference Number (REFNUMHA), CAGE (CAGECDXH), EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), TM Code (TMCODEXI), Figure Number
(FIGNUMHK), and Item Number (ITEMNOHK).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437 F
FIGNUMHK FIGURE NUMBER 4XR- 144 K
ITEMNOHK ITEM NUMBER 4XR- 184 K
TMFGCDHK TM FUNCTIONAL GROUP CODE (REPAIR 11 X L - 438
PARTS MANUAL)
TMINDCHK TECHNICAL MANUAL INDENTURE CODE 1NF- 439
QTYFIGHK QUANTITY PER FIGURE 3NR- 318
TMCHGNHK TECHNICAL MANUAL CHANGE NUMBER 2NR- 436

TABLE HL, PARTS MANUAL PROVISIONING NOMENCLATURE


122. This table contains text for repair parts manual data associated with a part application for provisioning.
Table keys include: Reference number (REFNUMHA), CAGE (CAGECDXH), EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), TM Code (TMCODEXI), Figure Number
(FIGNUMHK), Item Number (ITEMNOHK) and Parts Manual Text Sequencing Code (TEXSEQHL).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F

3A-72
DEF(AUST)5692

LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F


ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437 F
FIGNUMHK FIGURE NUMBER 4XR- 144 F
ITEMNOHK ITEM NUMBER 4XR- 184 F
TEXSEQHL PARTS MANUAL TEXT SEQUENCING CODE 5NR- 450 K
PROVNOHL PROVISIONING NOMENCLATURE 65 X - - 310

TABLE HM, ITEM BASIS OF ISSUE


123. This table contains part manual (tool list) Basis Of Issue (BOI) information. Table keys include:
Reference Number (REFNUMHA), CAGE (CAGECDXH), and BOI Control (BOICTRHM).

a. Either BOI-Level (LVLBOIHM) or BOI-End Item (RATIOBHM) must be entered to establish a


row of information in this table. When one of these is entered, the other must be blank.
Each LVLBOIHM and RATIOBHM value must be a unique value for a given Reference
Number and CAGE combination.

b. A PLCC (DDPLCCHA) entry must be contained in table HA, and an entry in table HK for the
item Reference Number and CAGE combination must occur prior to an entry in this table.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
BOICTRHM BASIS OF ISSUE CONTROL 1NF- 030 K
QTYBOIHM BASIS OF ISSUE QUANTITY 5NR- 030 M
RATIOBHM BASIS OF ISSUE END ITEM 8XL- 030
LVLBOIHM BASIS OF ISSUE LEVEL 1AF- 030

TABLE HN, PROVISIONING SERIAL NUMBER USABLE ON CODE


124. This table relates a part application to the applicable System/EI Serial Number (S/N) and S/N UOC
associated with the part application. Please refer to table XD. Table keys include all columns. Table keys
CAGECDHN, REFNUMHN, LSACONHN, and ALTLCNHN migrate from table HG. Table keys LCNSEIHN,
ALCSEIHN, FRSNUMHN, and TOSNUMHN migrate from table XD. EIACODXA and LCNTYPXB are
identical in both tables XD and HG.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LCNTYPXB LCN TYPE 1AF- 203 F
CAGECDHN S/N PROVISIONING CAGE CODE 5XF- 046 F
REFNUMHN S/N PROVISIONING REFERENCE NUMBER 32 X L - 337 F
LSACONHN S/N PROVISIONING LSA CONTROL NUMBER 18 X L - 199 F
(LCN)
ALTLCNHN S/N PROVISIONING ALTERNATE LCN CODE 2NF- 019 F
(ALC)
LCNSEIHN S/N PROVISIONING SYSTEM/EI LCN 18 X L - 199 F
ALCSEIHN S/N PROVISIONING SYSTEM/EI ALC 2NF- 019 F
FRSNUMHN S/N PROVISIONING SERIAL NUMBER FROM 10 X L - 373 F
TOSNUMHN S/N PROVISIONING SERIAL NUMBER TO 10 X L - 373 F

TABLE HO, PROVISIONING SYSTEM/END ITEM USABLE ON CODE


125. This table relates a part application to the applicable System/EI UOCs and Provisioning Contract
Control Number (PCCN) associated with the part application. Table keys include all columns. Table keys

3A-73
DEF(AUST)5692

CAGECDHO, REFNUMHO, LSACONHO, and ALTLCNHO migrate from table HG. Table keys LCNSEIHO
and ALCSEIHO migrate from table XC, from which UOCs and the PCCN are extracted. EIACODXA and
LCNTYPXB are identical in both tables XC and HG.

Note:

1. Part application LCNs (LSACONHO) are mapped to their respective system/end items by matching on EIAC,
LCN Type, LCN, and ALC between tables HO and XC to extract applicable UOCs and the PCCN. A part
application can have multiple UOCs, but it can have only one PCCN.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LCNTYPXB LCN TYPE 1AF- 203 F
CAGECDHO UOC PROVISIONING CAGE CODE 5XF- 046 F
REFNUMHO UOC PROVISIONING REFERENCE NUMBER 32 X L - 337 F
LSACONHO UOC PROVISIONING LSA CONTROL NUMBER 18 X L - 199 F
(LCN)
ALTLCNHO UOC PROVISIONING ALTERNATE LCN CODE 2NF- 019 F
(ALC)
LCNSEIHO UOC PROVISIONING SYSTEM/EI LCN 18 X L - 199 F
ALCSEIHO UOC PROVISIONING SYSTEM/EI ALC 2NF- 019 F

TABLE HP, DESIGN CHANGE INFORMATION


126. This table contains information about the parts application item affected by a design change. Table
keys include: Reference Number (REFNUMHA), CAGE (CAGECDXH), EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and Change Authority Number (CANUMBHP).

a. Replaced or Superseding PLISN (RSPLISHP) must be established in either table HG or XC


matching the PCCN of the HP table keys (less CANUMBHP). A Replaced or Superseded
PLISN Indicator (RSPINDHP) cannot be entered without a Replaced or Superseded PLISN
(RSPLISHP).

b. Quantity Procured (QTYPROHP) must be entered if there is an entry in Quantity Shipped


(QTYSHPHP). The QTYPROHP must be greater than or equal to the QTYSHPHP.

c. Prorated Exhibit Line Item (PROELIHP) must be entered if there is an entry in Prorated ELIN
Quantity (PROQTYHP).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
CANUMBHP CHANGE AUTHORITY NUMBER 15 X L - 043 K
RSPLISHP REPLACED OR SUPERSEDING (R-S) 5XL- 353
PROVISIONING LIST ITEM SEQUENCE
NUMBER (PLISN)
RSPINDHP R-S PLISN INDICATOR 1AF- 354
INTCHCHP INTERCHANGEABILITY CODE 2AF- 172
TOTICHHP TOTAL ITEM CHANGES 2NR- 452
QTYSHPHP QUANTITY SHIPPED 6NR- 323
QTYPROHP QUANTITY PROCURED 6NR- 322
PROELIHP PRORATED EXHIBIT LINE ITEM NUMBER 6X-- 305
(ELIN)
PROQTYHP PRORATED QUANTITY 6NR- 306

3A-74
DEF(AUST)5692

TABLE HQ, SERIAL NUMBER EFFECTIVITY


127. This table contains the serial number effectivity ranges which are affected by the design change.
Table keys include all columns.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
CANUMBHP CHANGE AUTHORITY NUMBER 15 X L - 043 F
FMSRNOHQ FROM SERIAL NUMBER EFFECTIVITY 10 X L - 374 K
TOSRNOHQ TO SERIAL NUMBER EFFECTIVITY 10 X L - 374 K

TABLE HR, DESIGN CHANGE USABLE ON CODE


128. This table references to the UOC affected by a design change. Table keys include all columns.
Design change UOC is extracted from table XC through table HO for the key of UOC System/EI (LCNSEIHO
and ALCSEIHO) and UOC provisioning LCN/ALC (LSACONHO and ALTLCNHO). REFNUMHO,
CAGECDHO, LSACONHO and ALTLCNHO must be identical with REFNUMHA, CAGECDXH, LSACONXB,
and ALTLCNXB from table HP migrating CANUMBHP into this table. EIACODXA and LCNTYPXB must be
identical in Tables XC, HO, and HR.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LCNTYPXB LCN TYPE 1AF- 203 F
CAGECDHO UOC PROVISIONING CAGE CODE 5XF- 046 F
REFNUMHO UOC PROVISIONING REFERENCE NUMBER 32 X L - 337 F
LSACONHO UOC PROVISIONING LSA CONTROL NUMBER 18 X L - 199 F
(LCN)
ALTLCNHO UOC PROVISIONING ALTERNATE LCN CODE 2NF- 019 F
(ALC)
LCNSEIHO UOC PROVISIONING SYSTEM/EI LCN 18 X L - 199 F
ALCSEIHO UOC PROVISIONING SYSTEM/EI ALC 2NF- 019 F
CANUMBHP CHANGE AUTHORITY NUMBER 15 X L - 043 F

3A-75
DEF(AUST)5692

TRANSPORTABILITY ENGINEERING ANALYSIS


129. Data tables beginning with "J" in the first position of the table code are structured to capture the
information pertaining to the transportability shipping modes and to the transported end item. In the event
that the end item is sectionalized for transport, the information shall be completed for each section of the end
item. Figure 10 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


JA Transportation
JB Transportation Shipping Modes
JC Transported End Item
JD Transported End Item Narrative
JE Transport by Fiscal Year
JF Transportation Narrative

Figure 10 J Table Relationships

3A-76
DEF(AUST)5692

TABLE JA, TRANSPORTATION


130. This table identifies the transportation characteristics of the system/equipment under analysis. It
describes what is required for the system/equipment to be transported. The table keys consist of EIAC
(EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB). For a given row of
information, the following cross-element edits apply to table JA:

a. The transportability area may only be used if an item has been identified by a Sectionalized Item
Transportation Indicator (SECITMXB) table XB, or by a Transportation End Item Indicator
(TRASEIXC) table XC.

b. If the system/equipment is being sectionalized for transportation, then Sectionalized


Identification (SECTIDJA) should be filled out.

c. If the system/equipment has environmental considerations, a (Y) should be entered in the


Environmental Handling and Transportation Indicator (ENHATCJA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TRNINDJA TRANSPORTATION INDICATOR 1AF- 468
SECTIDJA SECTIONALIZED IDENTIFICATION 2NR- 366
ENHATCJA ENVIRONMENTAL HANDLING AND 1AF- 098
TRANSPORTATION INDICATOR
DELSCHJA DELIVERY SCHEDULE 1AF- 075
CONNUMJA TRANSPORTATION CONTRACT NUMBER 19 X L - 055
PROPSNJA PROPER SHIPPING NAME 60 X L - 304
SPSPEDJA SPEED 3NR- 400
TWSPEDJA TOWING SPEED 3NR- 455
MILUNTJA MILITARY UNIT TYPE 240 X L - 242
TRCHRDJA REVISION DATE 6NF- 071
TRCHTHJA THEATRE OF OPERATION 5AL- 451
NOPRFFJA NONOPERABILITY FRAGILITY FACTOR 2NR- 260
NETEXWJA NET EXPLOSIVE WEIGHT 10 N R - 254

TABLE JB, TRANSPORTATION SHIPPING MODES


131. This table identifies the different possible transportation shipping modes for the system/equipment
under analysis. This table can identify the different types of aircraft and whether the aircraft will transport the
item under analysis externally or internally. This table can identify the different type of helicopters, their
mission capabilities, and whether the helicopter will transport the item under analysis externally or internally.
This table can identify the highway prime and alternate model types and what type of payload capacity the
transporter has. This table can identify the type of lighterages and whether the item under analysis can be
stowed on deck. This table can identify the type of rail system that will be used and which countries the rail
system will run through for the item under analysis. This table can identify the type of ships and whether the
item under analysis can be stowed on deck. The table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Transportation Characteristic Number
(TRANCNJB), and Transportation Mode Type (TRCHMTJB). For a given row of information, the following
cross-element edits apply to table JB:

a. This table can only be used if an (S or B) has been entered in the Transportation Indicator
(TRNINDJA) table JA.

b. Transportation Item Designator (TRITDRJB) and External or Internal Load Indicator (EOILINJB)
should only be used when the Transportation Character Mode Type of (A) for an aircraft is
entered.

c. External or Internal Load Indicator (EOILINJB) and Transportation Item Designator (TRITDRJB)
for an aircraft must either both be blank, or both have entries.

3A-77
DEF(AUST)5692

d. Transportation Item Designator (TRITDRJB), Helicopter Mission Altitude (HMATLRJB),


Helicopter Mission Distance (HMDISRJB), Helicopter Mission Payload (HMPAYRJB),
Helicopter Mission Temperature (HMTMPRJB), Helicopter Mission Time (HMTIMRJB), and
External or Internal Load Indicator (EOILINJB) should only be filled out when the
Transportation Character Mode Type (TRCHMTJB) of (B) for a helicopter is entered.

e. External or Internal Load Indicator (EOILINJB) and Transportation Item Designator (TRITDRJB)
for a helicopter must either both be blank, or both have entries.

f. Highway Prime Load (HIPRMLJB), Highway Prime Model Type (HIPRMTJB), Highway Alternate
Load (HALTMLJB), and Highway Alternate Model Type (HALTMTJB) should only be filled
out when the Transportation Character Mode Type (TRCHMTJB) of (C) is entered.

g. Highway Prime Model Load (HIPRMLJB) and Highway Prime Model Type (HIPRMTJB) must
either both be blank, or both have entries.

h. Highway Alternate Model Load (HALTMLJB) and Highway Alternate Model Type (HALTMTJB)
must either both be blank, or both have entries.

i. Sea Deck Stowage (SDECKSJB) and Transportation Item Designator (TRITDRJB) should only
be filled out when the Transportation Character Mode Type (TRCHMTJB) of (D) for a
lighterage is entered.

j. Sea Deck Stowage (SDECKSJB) and Transportation Item Designator (TRITDRJB) for a
lighterage must either both be blank, or both have entries.

k. Transportation Item Designator (TRITDRJB), Rail Use (RAILUSJB) and Rail Transportation
Country (RAILTCJB) should only be filled out when the Transportation Character Mode Type
(TRCHMTJB) of (E) is entered.

l. Rail Use (RAILUSJB) and Rail Transportation Country (RAILTCJB) must either both be blank,
or both have entries.

m. Sea Deck Stowage (SDECKSJB) and Transportation Item Designator (TRITDRJB) should only
be filled out when the Transportation Character Mode Type (TRCHMTJB) of (F) for a ship is
entered.

n. Sea Deck Stowage (SDECKSJB) and Transportation Item Designator (TRITDRJB) for a ship
must either both be blank, or both have entries.

o. Container Length (CONLENJB) and Container Type (CONTYPJB) must either both be blank, or
both have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TRANCNJB TRANSPORTATION CHARACTER NUMBER 2NR- 465 K
TRCHMTJB TRANSPORTATION CHARACTER MODE TYPE 1AF- 464 K
TRITDRJB TRANSPORTATION ITEM DESIGNATOR 26 X L - 469
SHPCONJB SHIPPING CONFIGURATION 2AL- 380
CONLENJB CONTAINER LENGTH 2NR- 053
CONTYPJB CONTAINER TYPE 36 X L - 054
FRCLASJB FREIGHT CLASSIFICATION 7XL- 146
EOILINJB EXTERNAL OR INTERNAL LOAD INDICATOR 1AF- 104
HMATLRJB HELICOPTER MISSION ALTITUDE 5NR- 159
HMDISRJB HELICOPTER MISSION DISTANCE 3NR- 159
HMPAYRJB HELICOPTER MISSION PAYLOAD 5NR- 159
HMTMPRJB HELICOPTER MISSION TEMPERATURE 3NR- 159
HMTIMRJB HELICOPTER MISSION TIME 3NR1 159
HIPRMLJB HIGHWAY PRIME MODEL LOAD 1AF- 250
HIPRMTJB HIGHWAY PRIME MODEL TYPE 19 X L - 251

3A-78
DEF(AUST)5692

HALTMLJB HIGHWAY ALTERNATE MODEL LOAD 1AF- 250


HALTMTJB HIGHWAY ALTERNATE MODEL TYPE 19 X L - 251
RAILUSJB RAIL USE 5AL- 326
RAILTCJB RAIL TRANSPORTATION COUNTRY 240 X - - 325
SDECKSJB SEA DECK STOWAGE 1AF- 072

TABLE JC, TRANSPORTED END ITEM


132. This table provides information pertaining to a System/EI that is to be transported. The table keys
consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Transported
Configuration Number (TRANCNJC), and Mobility Type (MOBTYPJC). For a given row of information, the
following cross-element edits apply to table JC:

a. This table can only be used if an (E or B) has been entered in the Transportation Indicator
(TRNINDJA) table JA.

b. Operational Weight Empty (OPWEEMJC) and Military Load Classification Empty (HICLNEJC)
must either both be blank, or both have entries.

c. Operational Weight Loaded (OPWELDJC) and Military Load Classification Loaded (HICLNLJC)
must either both be blank, or both have entries.

d. Skid Number of Skids (SNUMSKJC), Skid Area (SDSICGJC), and Skid Area UM (SKADUMJC)
should only be used when the Mobility Type (MOBTYPJC) of (A) is entered.

e. Skid Area (SDSICGJC) and Skid Area UM (SKADUMJC) must either both be blank, or both
have entries.

f. Tracked Ground Pressure (TRGRPRJC), Tracked Road Wheel Weight (TRRWWTJC), Tracked
Pads Touching (TRNUPTJC), Tracked Pad Shoe Area (TRPSARJC), and Tracked Pad
Shoe Area UM (TPSAUMJC) should only be used when the Mobility Type (MOBTYPJC) of
(B) is entered. Wheeled Inflation Pressure (WHINPRJC), Wheeled Number of Tires
(WHNUTIJC), Wheeled Tire Load Ratings (WHTLDRJC), Wheeled Tire Size (WHTIFTJC),
and Wheeled Weight Ratings (WHWERAJC) may also apply to tracked vehicles.

g. Tracked Pad Shoe Area (TRPSARJC) and Tracked Pad Shoe Area UM (TPSAUMJC) must
either both be blank, or both have entries.

h. Wheeled Inflation Pressure (WHINPRJC), Wheeled Number of Tires (WHNUTIJC), Wheeled


Tire Load Ratings (WHTLDRJC), Wheeled Tire Size (WHTIFTJC), and Wheeled Weight
Ratings (WHWERAJC) should be used when the Mobility Type (MOBTYPJC) of (C) is
entered.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TRCONMJC TRANSPORTED CONFIGURATION NUMBER 2NR- 473 K
MOBTYPJC MOBILITY TYPE 1AF- 249 K
OPWEEMJC OPERATIONAL WEIGHT EMPTY 4NR1 276
HICLNEJC MILITARY LOAD CLASSIFICATION EMPTY 2NR- 241
OPWELDJC OPERATIONAL WEIGHT LOADED 4NR1 276
HICLNLJC MILITARY LOAD CLASSIFICATION LOADED 2NR- 241
SHWEEMJC SHIPPING WEIGHT EMPTY 4NR1 381
SHWELDJC SHIPPING WEIGHT LOADED 4NR1 381
CREANGJC CREST ANGLE 2NR- 063
TRGRPRJC TRACKED GROUND PRESSURE 7NR- 456
TRRWWTJC TRACKED ROAD WHEEL WEIGHT 6NR1 459
TRNUPTJC TRACKED PADS TOUCHING 2NR- 458
TRPSARJC TRACKED PAD SHOE AREA 6NR1 457

3A-79
DEF(AUST)5692

TPSAUMJC TRACKED PAD SHOE AREA UNIT OF 2AF- 491


MEASURE
WHINPRJC WHEELED INFLATION PRESSURE 3NR- 507
WHNUPLJC WHEELED NUMBER OF PLIES 2NR- 508
WHNUTIJC WHEELED NUMBER TIRES 2NR- 509
WHTLDRJC WHEELED TIRE LOAD RATINGS 10 X L - 510
WHTIFTJC WHEELED TIRE SIZE 10 X L - 512
WHWERAJC WHEELED WEIGHT RATINGS 10 X L - 513
TWALFIJC LENGTH FRONT INSIDE 4NR1 029
TWALFOJC LENGTH FRONT OUTSIDE 4NR1 029
TWALRIJC LENGTH REAR INSIDE 4NR1 029
TWALROJC LENGTH REAR OUTSIDE 4NR1 029
SNUMSKJC SKID NUMBER OF SKIDS 2NR- 264
SDSICGJC SKID AREA 6NR1 384
SKADUMJC SKID AREA UNIT OF MEASURE 2AF- 491

TABLE JD, TRANSPORTED END ITEM NARRATIVE


133. This table may be used to identify Tire Requirements, Skid Remarks, Tracked Wheeled Remarks,
Turning Information, Axle and Suspension Remarks, and Other Transported Equipment. The table keys
consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Transported
Configuration Number (TRANCNJC), and Mobility Type (MOBTYPJC), Transported End Item Narrative Code
(TREINCJD), and Transported End Item Narrative Text Sequencing Code (TEXSEQJD). For a given row of
information, the following cross-element edits apply to table JD:

a. If the Transported End Item Narrative Code (TREINCJD) is (A), then this table identifies any
pertinent information pertaining to the tires for the system under analysis (Wheeled Tire
Requirements, DED 511).

b. If the Transported End Item Narrative Code (TREINCJD) is (B), then this table describes any
pertinent information pertaining to skid areas for the system under analysis (Skid Remarks,
DED 385).

c. If the Transported End Item Narrative Code (TREINCJD) is (C), then this table describes the
tracked/wheeled turning diameter which will include wall-to-wall, curb-to-curb (Turning
Information, DED 477).

d. If the Transported End Item Narrative Code (TREINCJD) is (D), then this table describes any
information pertaining to the axle and suspension system of the item under analysis
(Wheeled Axle and Suspension Remarks, DED 506).

e. If the Transported End Item Narrative Code (TREINCJD) is (E), then this table captures all other
information pertaining to an item that is being transported which is not tracked, wheeled, or
skid mounted (Transported Other Equipment, DED 475).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TRCONMJC TRANSPORTED CONFIGURATION NUMBER 2NR- 473 F
MOBTYPJC MOBILITY TYPE 1AF- 249 F
TREINCJD TRANSPORTED END ITEM NARRATIVE CODE 1AF- 474 K
TEXSEQJD TRANSPORTED END ITEM NARRATIVE TEXT 5NR- 450 K
SEQUENCING CODE
WHTRLOJD TRANSPORTED END ITEM NARRATIVE 65 X - - ---

3A-80
DEF(AUST)5692

TABLE JE, TRANSPORT BY FISCAL YEAR


134. This table contains information about the system/equipment procurement and delivery schedule. The
table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB),
and Transport Fiscal Year (TRAFYRJE).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TRAFYRJE TRANSPORT FISCAL YEAR 2NF- 145 K
FIQPQTJE FIRST QUARTER PROCUREMENT QUANTITY 3NR- 298
SQPQTYJE SECOND QUARTER PROCUREMENT 3NR- 298
QUANTITY
TQPQTYJE THIRD QUARTER PROCUREMENT QUANTITY 3NR- 298
FQPQTYJE FOURTH QUARTER PROCUREMENT 3NR- 298
QUANTITY

TABLE JF, TRANSPORTATION NARRATIVE


135. This table may be used to identify Transportation Shock and Vibration Requirements, Lifting and
Tiedown Remarks, Projection Characteristics, Regulatory Requirements, Special Services and Equipment,
Sectionalized Remarks, Transportation Remarks, Transport To/From Remarks, Environmental
Considerations, Military Distance Classification, Unusual and Special Requirements, Venting and Protective
Clothing, and Disaster Response Force. The table keys consist of EIAC (EIACODXA), LCN (LSACONXB),
ALC (ALTLCNXB), LCN Type (LCNTYPXB), Transportation Narrative Code (TRANCDJF) and
Transportation Narrative Text Sequencing Code (TRANARJF). For a given row of information, the following
cross-element edits apply to table JF:

a. If the Transportation Narrative Code (TRANCDJF) is (A), then this table should state the
fragility, shock, and vibration considerations required for the system/equipment under
analysis (Transportation Shock Vibration Remarks, DED 382).

b. If the Transportation Narrative Code (TRANCDJF) is (B), then this table identifies the number,
location, and strength of the lifting provisions and tiedown remarks for the system/equipment
under analysis (Lifting and Tiedown Remarks, DED 192).

c. If the Transportation Narrative Code (TRANCDJF) is (C), then this table states the dimensions
and locations of any significant projections of the system under analysis (Transportation
Projection Remarks, DED 471).

d. If the Transportation Narrative Code (TRANCDJF) is (D), then this table describes data to show
compliance with regulatory requirements (Regulatory Requirements, DED 340).

e. If the Transportation Narrative Code (TRANCDJF) is (E), then this table provides a narrative
field for transportation remark which may include towing, self-propelled, handling, and air
dropped information, plus any transportation information not captured in other data elements
or other narrative fields. (Transportation Remarks, DED 472).

f. If the Transportation Narrative Code (TRANCDJF) is (F), then this table describes any
information concerning the requirements for special services and equipment (railcars, road
vehicles, or materiel handling equipment) when required for the system under analysis
(Special Service and Equipment, DED 398).

g. If the Transportation Narrative Code (TRANCDJF) is (G), then this t able provides the
sectionalization information for each section that is being transported (Sectionalized
Remarks, DED 368).

3A-81
DEF(AUST)5692

h. If the Transportation Narrative Code (TRANCDJF) is (H), then this table describes from where
the item is transported and to where the item is transported (Transport To and From, DED
476).

i. If the Transportation Narrative Code (TRANCDJF) is (I), then this table provides information
concerning any special environmental/hazardous considerations required for the
transportation of the system/equipment under analysis (Environmental/Hazardous Material
Considerations, DED 099). For this table to be used, a (Y) must be entered into the
Environmental Handling and Transportation Indicator (ENHATCJA) table JA.

j. If the Transportation Narrative Code (TRANCDJF) is (J), then this table describes the military
quantity distance class and storage compatibility groups (Military Distance Classification,
DED 240). For this table to be used, a (Y) must be entered into the Environmental Handling
and Transportation Indicator (ENHATCJA) table JA.

k. If the Transportation Narrative Code (TRANCDJF) is (K), then this table describes any unusual
item transportation characteristics (e.g., temperature limits, humidity limits, escorts required,
etc.) (Unusual and Special Requirements, DED 500). For this table to be used, a (Y) must
be entered into the Environmental Handling and Transportation Indicator (ENHATCJA) table
JA.

l. If the Transportation Narrative Code (TRANCDJF) is (L), then this table describes the venting
and protective clothing requirements (Venting and Protective Clothing, DED 504). For this
table to be used, a (Y) must be entered into the Environmental Handling and Transportation
Indicator (ENHATCJA) table JA.

m. If the Transportation Narrative Code (TRANCDJF) is (M), then this table describes in detail all
disaster response force requirements for a transportation disaster encountered while
transporting the item (Disaster Response Force Requirements, DED 082). For the table to
be used, a (Y) must be entered into the Environmental Handling and Transportation Indicator
(ENHATCJA) table JA.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TRANCDJF TRANSPORTATION NARRATIVE CODE 1AF- 470 K
TEXSEQJF TRANSPORTATION NARRATIVE TEXT 5NR- 450 K
SEQUENCING CODE
TRANARJF TRANSPORTATION NARRATIVE 65 X - - ---

3A-82
DEF(AUST)5692

AUSTRALIAN DEFENCE ORGANISATION M TABLES


136. Data tables beginning with "M" in the first position of the table code are structured as narrative tables
to provide explanatory comments. Narratives may be recorded against specific task or Servicing information,
the LCN Nomenclature or an item's work zone. Figure 11 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


MA Task ID Extended Memo
MB Skill Specialty Code Extended Memo
MC Task Interval Extended Memo
MD Task Facility Extended Memo
ME LCN Item Extended Memo
MF Servicing Extended Memo

Figure 11 M Table Relationships

TABLE MA, TASK ID EXTENDED MEMO


137. This table may be used to record additional comments against a task requirement. A narrative
comment may be recorded against each task in table CA. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Task Code (TASKCDCA), and Task Memo Text
Sequencing Code (TEXSEQMA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F

3A-83
DEF(AUST)5692

TEXSEQMA TASK MEMO TEXT SEQUENCING CODE 5NR- 450 K


NARRATMA NARRATIVE - TASK 65 X L - 944

TABLE MB, SKILL SPECIALTY CODE EXTENDED MEMO


138. This table may be used to record narrative comments against a trade (skill specialty) for a task
recorded in the RM table. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB),
LCN Type (LCNTYPXB), Task Code (TASKCDCA), Maintenance Policy Trade (MPTRADRM), and Skill
Specialty Text Sequencing Code (TEXSEQMB).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
MPTRADRM MAINTENANCE POLICY TRADE 7XL- 387 F
TEXSEQMB SKILL SPECIALTY MEMO TEXT SEQUENCING 5NR- 450 K
CODE
NARRATMB NARRATIVE - MAINTENANCE POLICY TRADE 65 X L - 945
SKILL

TABLE MC, TASK INTERVAL EXTENDED MEMO


139. This table may be used to record additional comments against the allocation of a preventative
maintenance task to a Servicing interval. A narrative may be recorded against each task/event cross-
reference in Table WB. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB),
LCN Type (LCNTYPXB), Task Code (TASKCDCA), Event Measurement Base (EVNTMBWA) and Servicing
Task Text Sequencing Code (TEXSEQMC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
EVNTMBWA EVENT MEASUREMENT BASE 6XL- 923 F
TEXSEQMC SERVICING TASK MEMO TEXT SEQUENCING 5NR- 450 K
CODE
NARRATMC NARRATIVE - TASK INTERVAL 65 X L - 946

TABLE MD, TASK FACILITY EXTENDED MEMO


140. This table may be used to record comments regarding the need for the identified
operations/maintenance facility to perform a given task. A narrative may be recorded against each
Operations and Maintenance Task Facility requirement in Table FE. The table keys consist of EIAC
(EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Task Code (TASKCDCA),
Facility Name (FACNAMFA), Facility Category Code (FACCCDFA), Facility Type (FACTYPFA) and Task
Facility Text Sequencing Code (TEXSEQMD).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F

3A-84
DEF(AUST)5692

TASKCDCA TASK CODE 7XF- 427 F


FACNAMFA FACILITY NAME 32 X L - 118 F
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 F
FACTYPFA FACILITY TYPE 1AF- 483 F
TEXSEQMD TASK FACILITY MEMO TEXT SEQUENCING 5NR- 450 K
CODE
NARRATMD NARRATIVE - TASK FACILITY 65 X L - 947

TABLE ME, LCN ITEM EXTENDED MEMO


141. This table may be used to record extended comments against LCN indentured items. Table keys
consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and LCN
Item Text Sequencing Code (TEXSEQME).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TEXSEQME LCN ITEM TEXT SEQUENCING CODE 5NR- 450 K
NARRATME NARRATIVE - LCN ITEM 65 X L - 948

TABLE MF, SERVICING EXTENDED MEMO


142. This table may be used to record additional comments against a Servicing. The comment can relate
to the Servicing or any of the Servicing attributes, eg., facility, technical data, interval, etc. The table keys
migrate from Table WN and consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type
(LCNTYPXB), Servicing Identifier (SRVCIDWM) and Servicing Text Sequencing Code (TEXSEQMF).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
TEXSEQMF SERVICING TEXT SEQUENCING CODE 5NR- 450 K
NARRATMF NARRATIVE - SERVICING 65 X L - 949

3A-85
DEF(AUST)5692

AUSTRALIAN DEFENCE ORGANISATION R TABLES


143. Data tables beginning with "R" in the first position of the table code records information to support the
production of Technical Maintenance Plans (TMPs) and Planned Servicing Schedules (PSSs), supporting
the V and W tables. The R tables also provide cross-referencing between maintenance tasks summarised in
the TMPs and PSSs to provide traceability with the standard tasks derived through Task Analysis. Figure 12
depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


RA Work Area Code Library
RB Work Area Code Description
RC Initiating Types Library
RD Task Initiating Conditions Assignments
RE Servicing Initiating Conditions Assignments
RF Servicing Claimed Activities Assignments
RG Task Claimed Activities Assignments
RI Referenced Failure Modes
RJ LCN Log Requirements
RL Maintenance Policy Task Cross Reference
RM Maintenance Policy Trades
RN Servicing Subtasks
RO Servicing Subtask Narrative
RP Servicing Subtask Cross Reference

3A-86
DEF(AUST)5692

Figure 12 R Table Relationships

TABLE RA, WORK AREA CODE LIBRARY


144. This table contains the list of Work Area Codes (WAC) and WAC Names for a physical End Item
identified in table XC. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN
Type (LCNTYPXB), and WAC (WACODERA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
WACODERA WORK AREA CODE 5XL- 940 K
WACNAMRA WORK AREA CODE NAME 60 X L - 997

3A-87
DEF(AUST)5692

TABLE RB, WORK AREA CODE DESCRIPTION


145. This table may be used to record the descriptions for each Work Area Code recorded against an End
Item in the RA table. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN
Type (LCNTYPXB), Work Area Code (WACODERA) and WAC Description Text Sequence Code
(TEXSEQRB).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
WACODERA WORK AREA CODE 5XL- 940 F
TEXSEQRB WAC DESCRIPTION TEXT SEQUENCING CODE5 N R - 450 K
WACDESRB WORK AREA CODE DESCRIPTION 65 X L - 996

TABLE RC, INITIATING TYPES LIBRARY


146. This table contains the library of Initiating Types. Initiating types can be selected from the library and
used in defining Initiating Conditions for tasks or Servicings in the RD and RE tables. Table keys consist of
Initiating Type (INTTYPRC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


INTTYPRC INITIATING TYPE 8XL- 915 K
TYPDESRC INITIATING TYPE DESCRIPTION 40 X L - 916

TABLE RD, TASK INITIATING CONDITIONS ASSIGNEMENTS


147. This table can be used to record the Initiating Conditions assigned to any task. This includes where a
task is performed on an LCN indentured item that is different to the LCN indentured item where the initiating
condition is evident. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN
Type (LCNTYPXB), Task Code (TASKCDCA), Initiating Type (INTTYPRC), Initiating Mode (INTMODRD)
and Initiating Condition Sequence Number (ICSQNMRD). For entries in the RD table, the following table
rules apply:

a. Foreign key fields migrate from the CA table for the task that is being assigned the Initiating
Conditions. LCN, ALC, and LCN Type migrate from the XB table as non-key attributes and
are given new role names; Initiating LCN (INTLCNRD), Initiating ALC (INTALCRD), and
Initiating LCN Type (INTLTYRD). The INTLCNRD, INTALCRD, and INTLTYRD fields
migrated from XB must have the same EIAC as the key fields LSACONXB, ALTLCNXB, and
LCNTYPXB migrated from table CA. INITYPRC migrates from the RC Table.

b. Event Measurement Base migrates from the WA table as a non-identifying attribute and is given
the role name Initiating Event Measurement Base (INEVNTRD).

c. Initiating Interval (ININTVRD) and INEVNTRD must either both be blank or both have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
INTTYPRC INITIATING TYPE 8XL- 915 F
INTMODRD INITIATING MODE 1XF- 914 K
ICSQNMRD INITIATING CONDITION SEQUENCE NUMBER 2NF- 912 K
ININSTRD INITIATING INSTANCE 20 X L - 913

3A-88
DEF(AUST)5692

INTLCNRD INITIATING LCN 18 X L - 199


INTALCRD INITIATING ALC 2NF- 019
INTLTYRD INITIATING LCN TYPE 1AF- 203
ININTVRD INITIATING INTERVAL 10 N R - 937
INEVNTRD INITIATING EVENT MEASUREMENT BASE 6XL- 923

TABLE RE, SERVICING INITIATING CONDITIONS ASSIGNEMENTS


148. This table can be used to record the Initiating Conditions assigned to any End Item Servicing. This
includes where a Servicing is performed on an LCN indentured item that is different to the LCN indentured
item where the initiating condition is evident, eg., where the initiating condition is from an item subordinate to
the End Item with the Servicing task. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC
(ALTLCNXB), LCN Type (LCNTYPXB), Servicing Identifier (SRVCIDWM), Initiating Type (INTTYPRC),
Initiating Mode (INTMODRE), and Initiating Condition Sequence Number (ICSQNMRE). For entries in the
RE table, the following table rules apply:

a. Foreign key fields migrate from the WN table for the Servicing that is being assigned the
Initiating Conditions. LCN, ALC, and LCN Type migrate from the XB table as non-key
attributes and are given new role names; Initiating LCN (INTLCNRE), Initiating ALC
(INTALCRE), and Initiating LCN Type (INTLTYRE). The INTLCNRE, INTALCRE, and
INTLTYRE fields must have the same EIAC as the RE table key fields LSACONXB,
ALTLCNXB, and LCNTYPXB. INITYPRC migrates from the RC Table.

b. Event Measurement Base migrates from the WA table as a non-identifying attribute and is given
the role name Initiating Event Measurement Base (INTEVNRE).

c. Initiating Interval (ININTVRE) and INEVNTRE must either both be blank or both have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
INTTYPRC INITIATING TYPE 8XL- 915 F
INTMODRE SERVICING INITIATING MODE 1XF- 914 K
ICSQNMRE SERVICING INITIATING CONDITION 2NF- 912 K
SEQUENCE NUMBER
ININSTRE SERVICING INITIATING INSTANCE 20 X L - 913
INTLCNRE SERVICING INITIATING LCN 18 X L - 199
INTALCRE SERVICING INITIATING ALC 2NF- 019
INTLTYRE SERVICING INITIATING LCN TYPE 1AF- 203
ININTVRE SERVICING INITIATING INTERVAL 10 N R - 937
INEVNTRE SERVICING INITIATING EVENT 6XL- 923
MEASUREMENT BASE

TABLE RF, SERVICING CLAIMED ACTIVITIES ASSIGNMENTS


149. This table is used to record the Servicings identified as Claimed Activities and assigned to an End Item
Servicing. Table keys consist of all columns and all values migrate from the WN table. Both the Claiming
Activity Servicing Identifier (SRVCLGRF) and Claimed Activity Servicing Identifier (SRVCLDRF) migrate from
the Servicing Identifier (SRVCIDWM) column of table WN and are given new role names. For each record in
table RF, EIACODXA, LSACONXB, ALTLCNXB, and LCNTYPXB shall be the same for each occurrence of
SRVCLGRF and SRVCLDRF migrated from the Servicing Identifier in the WN table.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F

3A-89
DEF(AUST)5692

ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F


LCNTYPXB LCN TYPE 1AF- 203 F
SRVCLGRF CLAIMING ACTIVITY SERVICING IDENTIFIER 4XL- 933 F
SRVCLDRF CLAIMED ACTIVITY SERVICING IDENTIFIER 4XL- 933 F

TABLE RG, TASK CLAIMED ACTIVITIES ASSIGNMENTS


150. This table is used to record the tasks identified as Claimed Activities and assigned to a Claiming Task.
Table keys consist of all columns and all values migrate from the CA table. Both the Claiming Activity Task
Code (TSKCLGRG) and Claimed Activity Task Code (TSKCLDRG) migrate from the Task Codes
(TASKCDCA) column of table CA and are given new role names. For each record in table RG the following
cross-element edits apply:

a. EIACODXA, LSACONXB, ALTLCNXB, and LCNTYPXB shall be the same for both values of
TSKCLGRG and TSKCLDRG migrated from the CA table, and therefore are not repeated in
this table.

b. Only Task Codes with an operability code of 'T' or 'P' may be entered as a Claiming Task
Activity Code.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TSKCLGRG CLAIMING ACTIVITY TASK CODE 7XF- 427 F
TSKCLDRG CLAIMED ACTIVITY TASK CODE 7XF- 427 F

TABLE RI, REFERENCED FAILURE MODES


151. This table can be used to record cross-referencing between two failure modes and avoid the repeated
description for identical failure modes on equivalent items installed in different LCN structure locations.
Table keys consist of all columns. For each record in table RI, the EIACODXA must be identical for all keys
migrating from the BF table.

152. EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and Failure
Mode Indicator (FAMOINBF) migrate from the BF table for the referencing failure mode. The LCN, ALC,
LCN Type and FMI for the referenced failure mode migrate from the BF table to the RI table and are given
role names; Referenced LCN (REFLCNRI), Referenced ALC (REFALCRI), Referenced LCN Type
(REFLTYRI), and Referenced Failure Mode Indicator (REFFMIRI).

153. The referencing function should only be used when data in the BF, BG, BJ, BI and VF tables are the
same for the referencing and referenced failure mode. Only the key attributes in the BF table shall be
recorded for the referencing failure mode. All other data from BF, BG, BI, BJ and VF tables shall be pulled
from the Referenced LCN, ALC, LCN Type and FMI recorded in the RI table. In other words, with the
exception of BF table keys, no further entries are required in BF, BG, BI, BJ and VF tables for the referencing
failure modes.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
FAMOINBF FAILURE MODE INDICATOR (FMI) 4XF- 134 F
REFLCNRI REFERENCED FMI LCN 18 X L - 199 F
REFALCRI REFERENCED FMI ALC 2NF- 019 F
REFLTYRI REFERENCED FMI LCN TYPE 1AF- 203 F
REFFMIRI REFERENCED FAILURE MODE INDICATOR 4XF- 134 F

3A-90
DEF(AUST)5692

TABLE RJ, LCN LOG REQUIREMENTS


154. This table records the historical log requirements for an LCN indentured item. Table keys consist of all
columns.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
LCNLOGRJ LOG REQUIREMENT 3XL- 926 K

TABLE RL, MAINTENANCE POLICY TASK CROSS REFERENCE


155. This table can be used to record the mapping of a task from the CA table that represents an ADF
Maintenance Policy task, to one or more standard tasks in the CA table derived through Task Analysis. This
table performs enables an auditing function of standard tasks mapped to ADF Maintenance Policy tasks, for
both Technical Maintenance Plans and Planned Servicing Schedules. Table keys consist of all columns and
all values migrate from the CA table. For each record in RL the following attribute edits apply:

a. The Maintenance Policy Task Code must have an operability code of either 'T' or 'P'.

b. For each record in table RL, EIACODXA shall be identical for both standard and Maintenance
Policy tasks migrated from the CA table, and therefore is not repeated in this table.

c. Table keys for the ADF Maintenance Policy task migrate from the CA table and are given role
names; Maintenance Policy LCN (MPTLCNRL), Maintenance Policy ALC (MPTALCRL),
Maintenance Policy LCN Type (MPTLTPRL), and Maintenance Policy Task Code
(MPTCODRL), to distinguish them from keys for the standard task.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
MPTLCNRL MAINTENANCE POLICY LCN 18 X L - 199 F
MPTALCRL MAINTENANCE POLICY ALC 2NF- 019 F
MPTLTYRL MAINTENANCE POLICY LCN TYPE 1AF- 203 F
MPTCODRL MAINTENANCE POLICY TASK CODE 7XF- 427 F

TABLE RM, MAINTENANCE POLICY TRADES


156. This table records one or more trade assignments for an ADF Technical Maintenance Plan (TMP), or
Planned Servicing Schedule (PSS) Servicing task. Table keys consist of all columns. Skill Specialty Code
(SKSPCGA) migrates from the GA table and is given the role name Maintenance Policy Trade
(MPTRADRM). For each record in table RM, the Task Code migrated from the CA table must have an
operability code of either a 'T' or 'P'.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
MPTRADRM MAINTENANCE POLICY TRADE 7XL- 387 F

3A-91
DEF(AUST)5692

TABLE RN, SERVICING SUBTASKS


157. This table contains the subtasks for an ADF Servicing task. Servicing subtask information includes the
certification and failure reporting requirements for each subtask. Table keys consist of EIAC (EIACODXA),
LSA (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Task Code (TASKCDCA) and Servicing
Subtask Number (SUBNUMRN). For each record in table RN, the Task Code, for the Servicing task
migrated from the CA table must have an operability code of 'P'.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMRN SERVICING SUBTASK NUMBER 3NF- 407 K
SUBTIDRN SERVICING SUBTASK IDENTIFICATION 36 X L - 431
SCRTRQRN SUBTASK CERTIFICATION REQUIREMENT 1XF- 968
FRREQMRN FAILURE REPORTING REQUIREMENT 1AF- 924

TABLE RO, SERVICING SUBTASK NARRATIVE


158. This table contains the sequential task narrative, entered at the subtask level, for each ADF Servicing
task. The narrative will be entered in a step-by-step basis summarising the procedures for the conduct of a
Servicing task. Subtask narratives entered in this table, for the preparation of a Planned Servicing Schedule,
will normally summarise the detailed subtask narratives contained in table CC for the equivalent task or tasks
claimed to the Servicing task through table RG. Elements are subordinate to subtasks and designated by
Element Indicator (ELEMNTRO). Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), LCN Type
(LCNTYPXB), ALC (ALTLCNXB), Task Code (TASKCDCA), Servicing Subtask Number (SUBNUMRO), and
Servicing Subtask Narrative Text Sequencing Code (TEXSEQRO).

a. The Element Indicator "E" is documented against the first line of a given element narrative, and
is blank for all subsequent lines of that element narrative.

b. Element narratives must begin on unique lines (Text Sequence Codes). For example, one
element cannot end on line 12, and the next task element begin on line 12 also.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMRN SERVICING SUBTASK NUMBER 3NF- 407 F
TEXSEQRO SERVICING SUBTASK NARRATIVE TEXT 5NR- 450 K
SEQUENCING NUMBER
SUBNARRO SERVICING SUBTASK NARRATIVE 65 X - - 372
ELEMNTRO ELEMENT INDICATOR 1AF- 095

TABLE RP, SERVICING SUBTASK CROSS REFERENCE


159. This table can be used to record the cross mapping of an ADF Servicing subtask, from the RN table,
to one or more standard subtasks in the CB table. Table keys consist of all columns. Except for EIAC, table
keys migrated from the RN table for ADF Servicing subtasks are given role names; Servicing Subtask LCN
(SSTLCNRP), Servicing Subtask ALC (SSTALCRP), Servicing Subtask LCN Type (SSTLTYRP), Servicing
Subtask Task Code (SSTCODRP), and Servicing Subtask Number (SSTNUMRP), to distinguish them from

3A-92
DEF(AUST)5692

standard subtasks from table CB. For each record in table RP, EIACODXA shall be identical for all keys
migrated from the CB and RN tables, and therefore is not repeated in this table.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SUBNUMCB SUBTASK NUMBER 3NF- 407 F
SSTLCNRP SERVICING SUBTASK LCN 18 X L - 199 F
SSTALCRP SERVICING SUBTASK ALC 2NF- 019 F
SSTLTYRP SERVICING SUBTASK LCN TYPE 1AF- 203 F
SSTCODRP SERVICING SUBTASK TASK CODE 7XF- 427 F
SSTNUMRP SERVICING SUBTASK NUMBER 3NF- 407 F

3A-93
DEF(AUST)5692

AUSTRALIAN DEFENCE ORGANISATION V TABLES


160. Data tables beginning with "V" in the first position of the table code record information for ADF
aerospace requirements and may be used in other applications. These data tables cover a range of
information including parts control, facility task details, system (aircraft) roles, and additional failure mode
data. Figure 13 depicts the data relationships for these tables.

TABLE CODE TABLE TITLE


VA LOAS Entry
VB Authorised to Demand NSN
VC Authorised to Demand NSN - Facility
VD Item Identification Extension
VE Task Facility Requirement Extension
VF ADF Failure Modes
VR System/End Item Role Code
VS Role Code to Mission Phase Cross Reference
VT Role to LCN Cross Reference

Figure 13 V Table Relationships

3A-94
DEF(AUST)5692

TABLE VA, LOAS ENTRY


161. This table can be used to record the entry of Authorised To Demand NSN details on the List of
Available Spares (LOAS) spares management system. The ATD NSN is an NSN whose Reference
Numbers have been investigated by a technical assessor for their technical compatibility for use in the
identified LCN position. Table keys consist of CAGE (CAGECDXH), Reference Number (REFNUMHA),
EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB) and LCN Type (LCNTYPXB).

a. When required, Authority to Demand NSN (AUTHTDVB) migrates into this table as a non-
identifying attribute from table VB, which means that it is not required to uniquely identify a
record in this table.

b. The VA table can be read as follows:

When a part for the LCN position is required, demand the NSN shown to obtain a part. The part
supplied MAY NOT have the same Reference Number/Cage Code as that in this table.

c. The table also has a LOAS Entry Number cross reference and a Requirements Amplification
Code. The Requirements Amplification Code is applied on LOAS by technical assessors to
indicate whether or not the Reference Number/CAGE code combination is codified under the
ATD NSN in CENCAT (Central Cataloguing database).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
AUTHTDVB AUTHORITY TO DEMAND NSN 13 X F - 941
LOASENVA LOAS ENTRY NUMBER 8XL- 942
RQAMCDVA REQUIREMENTS AMPLIFICATION CODE 2XF- 943

TABLE VB, AUTHORISED TO DEMAND NSN


162. This table identifies price and management information for an NSN that is authorised to be demanded
(ATD NSN). Table keys consist of Authorised to Demand NSN (AUTHTDVB). For a given row of
information, the Authorised To Demand NSN Price (ATDPRIVB) and Authorised To Demand NSN Currency
(ATDCURVB) must either both have entries or both be blank.

CODE DATA ELEMENT TITLE FORMAT DED KEY


AUTHTDVB AUTHORITY TO DEMAND NSN 13 X F - 941 K
ATDPRIVB AUTHORISED TO DEMAND NSN PRICE 15 D - - 950
ATDCURVB AUTHORITY TO DEMAND NSN CURRENCY 5XL- 951
ATDEXIVB AUTHORISED TO DEMAND NSN EXISTING 5NR- 952
STOCK
ATDUOIVB AUTHORISED TO DEMAND NSN UNIT OF 2AL- 953
ISSUE
SERLEVVB SERVICING LEVEL 1AF- 954

TABLE VC, AUTHORISED TO DEMAND NSN - FACILITY


163. This table identifies the Operating, Repair and Storage facilities that are authorised to demand the
Authorised to Demand NSN (ATD NSN). Table keys consist of ATD NSN (AUTHTDVB), Facility Name
(FACNAMFA), Facility Category Code (FACCCDFA), and Facility Type (FACTYPFA). For a given row of
information, if the Facility Code (ADF) (FACODEVC) is "O", "R" or "OR" a MSI Unit Entitlement (MSIUENVC)
value is required.

3A-95
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


AUTHTDVB AUTHORITY TO DEMAND NSN 13 X F - 941 F
FACNAMFA FACILITY NAME 32 X L - 118 F
FACTYPFA FACILITY TYPE 1AF- 483 F
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 F
FACODEVC FACILITY CODE (ADF) 3AL- 955
MSIUENVC MAINTENANCE SUPPLY ITEM (MSI) UNIT 5NR- 956
ENTITLEMENT

TABLE VD, ADDITIONAL PART INFORMATION


164. This table records the hazardous goods number and the Part Primary Lifing Parameter for a CAGE
and Reference Number combination. Table keys consist of CAGE (CAGECDXH) and Reference Number
(REFNUMHA). The Part Primary Lifing Parameter migrates from the Event Measurement Base
(EVNTMBWA) in table WA as a non-identifying attribute, and is given the role code of PLIFPAVD.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDXH CAGE CODE 5XF- 046 F
REFNUMHA REFERENCE NUMBER 32 X L - 337 F
HAZMATVD HAZARDOUS MATERIAL 4X-- 957
PLIFPAVD PART PRIMARY LIFING PARAMETER 6XL- 923

TABLE VE, TASK FACILITY REQUIREMENT EXTENSION


165. This table can be used to identify costing information for repair tasks performed on an LCN at a
designated facility. The table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB),
LCN Type (LCNTYPXB), Task Code (TASKCDCA), Facility Name (FACNAMFA), Facility Category Code
(FACCCDFA) and Facility Type (FACTYPFA). For a given row of information, the following cross-element
edits apply to table VE:

a. If Task Cost of Repair Estimated (ESTCSTVE) and/or Task Cost of Repair Actual (ACTCSTVE)
have entries then a Task Cost of Repair Currency (CSTCURVE) must be entered.

b. Facility Task Time (TSKTIMVE) and Facility Task Time Measurement Base (TSKTMBVE) must
either both have entries or both be blank.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
FACNAMFA FACILITY NAME 32 X L - 118 F
FACTYPFA FACILITY TYPE 1AF- 483 F
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 F
ESTCSTVE TASK COST OF REPAIR ESTIMATED 10 N R - 958
ACTCSTVE TASK COST OF REPAIR ACTUAL 10 N R - 959
CSTCURVE TASK COST OF REPAIR CURRENCY 5XL- 960
TSKTIMVE FACILITY TASK TIME 5NR- 961
TSKTMBVE FACILITY TASK TIME MEASUREMENT BASE 1AF- 238

TABLE VF, ADF FAILURE MODES


166. This table can be used to record the Failure Mode Criticality (ADF) for each FMI as a result of RCM.
The Failure Mode Criticality (ADF) is assigned as the failure mode for an item is passed through the RCM

3A-96
DEF(AUST)5692

logic tree. The failure mode of a physical LCN may be linked to the Functional LCN representing the function
to which the FMI applies. This is required if the Physical LCN item has been linked to more than one
Functional LCN item in the XG table. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC
(ALTLCNXB), LCN Type (LCNTYPXB), and Failure Mode Indicator (FAMOINBF).

167. When required, the Functional LCN to which the Physical LCN Failure Mode relates can be mapped
from XG to the FLSACNXG, FALCNCXG, and FLCNTYXG fields in this table. FLSACNXG, FALCNCXG,
and FLCNTYXG must all be blank or all have entries.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
FAMOINBF FAILURE MODE INDICATOR (FMI) 4XF- 134 F
FMCRITVF FAILURE MODE CRITICALITY (ADF) 2XL- 962
FLSACNXG FUNCTIONAL LSA CONTROL NUMBER 18 X L - 199
FALCNCXG FUNCTIONAL ALTERNATE LCN CODE 2NF- 019
FLCNTYXG FUNCTIONAL LCN TYPE 1AF- 203

TABLE VR, SYSTEM/END ITEM ROLE CODE


168. This table identifies the roles which may be assigned to any of the systems/equipment described by
the End Item Acronym Code. Table keys consist of EIAC (EIACODXA) and Role Code (ROLCODVR).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
ROLCODVR ROLE CODE 8XL- 965 K
ROLDESVR ROLE DESCRIPTION 20 X L - 967

TABLE VS, ROLE CODE TO MISSION PHASE CROSS REFERENCE


169. This table can be used as a cross-link to identify the mission phases for the End Item when performing
a role identified in table VR. Each role of the End Item can have one or more mission phases, and mission
phases identified in table BL may be common to more than one role. Table keys consist of EIAC
(EAICODXA), Mission Phase Code (MISSPCBL) and Role Code (ROLCODVR). EIACODXA is identical for
keys from tables BL and VR for a given row of data.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
MISSPCBL MISSION PHASE CODE 1XF- 246 F
ROLCODVR ROLE CODE 8XL- 965 F

TABLE VT, ROLE TO LCN CROSS REFERENCE


170. This table can be used as a cross-link to document those LCN, ALC and LCN Type combinations that
are mandatory, optional, or not to be fitted to an End Item when configured to perform the role identified by
the Role Code. The "Role Required Fit" data element identifies those LCNs which MUST be fitted for the
role to be carried out effectively and safely. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB),
ALC (ALTLCNXB), LCN Type (LCNTYPXB) and Role Code (ROLCODVR). EIACODXA is identical for keys
from tables XB and VR for a given row of data.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F

3A-97
DEF(AUST)5692

ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F


LCNTYPXB LCN TYPE 1AF- 203 F
ROLCODVR ROLE CODE 8XL- 965 F
ROLREQVT ROLE REQUIRED FIT 1XF- 966

AUSTRALIAN DEFENCE ORGANISATION W TABLES


171. Data tables beginning with "W" in the first position of the table code record information for ADF
aerospace requirements and may be used in other applications. These tables are used to hold configuration
and scheduled Servicing information. Figures 14 and 15 depict the data relationships for these tables.

TABLE CODE TABLE TITLE


WA Event Measurement Base Library
WB Task/Event Cross Reference
WC Task Requirement Extension
WE Alternate CAGE and Reference Number Batch Information
WF Alternate CAGE and Reference Number Set Identification
WG Technical Management Code Library
WH Technical Management Code to Physical LCN Cross Reference
WI Alternate CAGE and Reference Number Set
WJ Authority To Fit ACRN on Serial Number System/End Item
WK Authority To Fit ACRN on System/End Item
WM Servicing Library
WN Servicing Identification
WO Servicing Task
WP Servicing Interval and Event Measurement Base
WQ Servicing Facility
WR Servicing Technical Manual
WS Servicing Group
WT Servicing Group Tasks
WU Technical Management Code Log
WY LCN Information Extension

3A-98
DEF(AUST)5692

Figure 14 W Table Relationships - Scheduled Servicings

3A-99
DEF(AUST)5692

Figure 15 W Table Relationships - Part Use

TABLE WA, EVENT MEASUREMENT BASE LIBRARY


172. This table identifies the Event Measurement Bases, which are used in the measurement of scheduled
maintenance tasks and Servicing intervals. The measurement base is to be used with the Interval data
elements (934 and 937) to describe the period between successive preventative maintenance Servicings
and tasks. Table keys consist of Event Measurement Base (EVNTMBWA).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EVNTMBWA EVENT MANAGEMENT BASE 6XL- 923 K
DESCRPWA EVENT MEASUREMENT BASE DESCRIPTION 16 X L - 922

TABLE WB, TASK/EVENT CROSS REFERENCE


173. This table identifies tasks to be performed on a scheduled basis after some interval (number) of events
have elapsed. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type
(LCNTYPXB), Task Code (TASKCDCA) and Event Measurement Base (EVNTMBWA). The example below
requires task WCOXBAA (TASK CODE), to be performed every 100 (TASK INTERVAL) Elapsed Days
(EVENT MEASUREMENT BASE).

eg.

TASK CODE TASK INTERVAL EVENT MEASUREMENT BASE


WCOXBAA 100 ELPDY (Elapsed Days)

3A-100
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
EVNTMBWA EVENT MANAGEMENT BASE 6XL- 923 F
TSKINTWB TASK INTERVAL 10 N R - 937

TABLE WC, TASK REQUIREMENT EXTENSION


174. This table records the contingency requirement flag and historical task frequency for a task. A
Historical Task Frequency may be the task frequency for a preventative maintenance task prior to grouping
into scheduled Servicings. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB),
LCN Type (LCNTYPXB), and Task Code (TASKCDCA). For the WC table the Historical Task Frequency
Narrative (TFQNARWC) may not be entered without a Historical Task Frequency (HTSKFQWC).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
CONTINWC CONTINGENCY REQUIREMENT 1AF- 921
HTSKFQWC HISTORICAL TASK FREQUENCY 7NR4 430
TFQNARWC HISTORICAL TASK FREQUENCY NARRATIVE 100 X L - 964

TABLE WE, ALTERNATE CAGE AND REFERENCE NUMBER BATCH INFORMATION


175. This table is used to record CAGE Codes and Reference Numbers of parts that represent alternatives
to those parts with CAGE Codes and Reference Numbers allocated against LCNs in the HG table. These
alternative parts are arranged into sets through the WI table. This table can record batch numbers for parts
that are not serial numbered items. Recording batch identification enables the management of batched
items, including the recalls if necessary. CAGE Codes and Reference Numbers are migrated from table HA
and given the role of Alternative CAGE and Reference Number (ACRN) CAGE Codes and Reference
Numbers. Table keys consist of ACRN CAGE Code (CAGECDWE), ACRN Reference Number
(REFNUMWE), From Batch Number (FRBTCHWE) and To Batch Number (TOBTCHWE). For a given row
of the WE table the following cross-element edits apply:

a. From Batch Number (FRBTCHWE) must be alphanumerically less than or equal to the To Batch
Number (TOBTCHWE).

b. Where Batch Numbers are not applicable to the ACRN CAGE Code and ACRN Reference
Number, dummy values for the From Batch Number (FRBTCHWE) and To Batch Number
(TOBTCHWE) shall be identified by the Requiring Authority.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDWE ACRN CAGE CODE 5XF- 046 F
REFNUMWE ACRN REFERENCE NUMBER 32 X L - 337 F
FRBTCHWE FROM BATCH NUMBER 10 X L - 917 K
TOBTCHWE TO BATCH NUMBER 10 X L - 917 K
BTCHIDWE BATCH IDENTIFICATION 19 X L - 918 M

3A-101
DEF(AUST)5692

TABLE WF, ALTERNATE CAGE AND REFERENCE NUMBER SET IDENTIFICATION


176. This table is used to form unique identifiers, known as Alternate CAGE and Reference Number
(ACRN) Set Identifiers, for ACRN sets. In this table the CAGE and Reference Number keys from the HA
table, that represent the parts to be applied to an LCN in the HG table, are given the role names of Prime
CAGE Code and Prime Reference Number. The key field of Set Sequence Number enables multiple ACRN
sets to be established for each part identified by the Prime CAGE and Reference Number. Table keys
consist of Prime CAGE Code (CAGECDWF), Prime Reference Number (REFNUMWF) and ACRN Set
Sequence Number (SEQNUMWF).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDWF PRIME CAGE CODE 5XF- 046 F
REFNUMWF PRIME REFERENCE NUMBER 32 X L - 337 F
SEQNUMWF ACRN SET SEQUENCE NUMBER 2NF- 919 K

TABLE WG, TECHNICAL MANAGEMENT CODE LIBRARY


177. This table is used to identify all the Technical Management Codes used, for all the equipment
described in the LSAR. Table keys consist of Technical Management Code (TMNTCDWG).

CODE DATA ELEMENT TITLE FORMAT DED KEY


TMNTCDWG TECHNICAL MANAGEMENT CODE 23 X F - 938 K
TMCSTAWG TECHNICAL MANAGEMENT CODE STATUS 1AF- 939 M
MAXFITWG MAXIMUM FIT 3NR- 927

TABLE WH, TECHNICAL MANAGEMENT CODE TO PHYSICAL LCN CROSS


REFERENCE
178. This table can be used as a cross reference of LCN to Technical Management Code. This information
is necessary to link the Maintenance Analysis And Recording System (MAARS) historical failure and
maintenance data to the LCN structured data of an LSAR. Table keys include all columns. For each row of
table WH LCN Type must always be "P" (Physical).

CODE DATA ELEMENT TITLE FORMAT DED KEY


TMNTCDWG TECHNICAL MANAGEMENT CODE 23 X F - 938 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F

TABLE WI, ALTERNATE CAGE AND REFERENCE NUMBER SET


179. This table is used to identify ACRN Sets by acting as a cross reference between ACRN Set Identifiers
and alternatives parts that may be used as substitutes for the part defined by the Prime CAGE Code and
Reference Number in the ACRN Set Identifier. A group of alternative parts, assigned against an ACRN Set
Identifier, is known as ACRN Set. Table keys include all columns.

180. Prime CAGE Code, Prime Reference Number, and ACRN Set Sequence Number, form the ACRN Set
Identifier migrating from Table WF. ACRN CAGE Code, ACRN Reference Number, From Batch Number,
and To Batch Number, identify alternate parts and migrate from table WE.

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDWF PRIME CAGE CODE 5XF- 046 F
REFNUMWF PRIME REFERENCE NUMBER 32 X L - 337 F

3A-102
DEF(AUST)5692

SEQNUMWF ACRN SET SEQUENCE NUMBER 2NF- 919 F


CAGECDWE ACRN CAGE CODE 5XF- 046 F
REFNUMWE ACRN REFERENCE NUMBER 32 X L - 337 F
FRBTCHWE FROM BATCH NUMBER 10 X L - 917 F
TOBTCHWE TO BATCH NUMBER 10 X L - 917 F

TABLE WJ, AUTHORITY TO FIT ACRN ON SERIAL NUMBER SYSTEM/END ITEM


181. This table can be used to cross reference which parts, identified by CAGE Code and Reference
Number, from an ACRN Set of alternative parts, may be fitted to specific Serial Numbered End Items. The
conditions under which the alternative part from the ACRN Set may be fitted, are identified by the Authority
To Fit. Table keys consist of Prime CAGE Code (CAGECDWF), Prime Reference Number (REFNUMWF),
ACRN Set Sequence Number (SEQNUMWF), ACRN CAGE Code (CAGECDWE), ACRN Reference
Number (REFNUMWE), From Batch Number (FRBTCHWE) and To Batch Number (TOBTCHWE), EIAC
(EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB) From Serial Number
(FRSNUMXD) and To Serial Number (TOSNUMXD).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDWF PRIME CAGE CODE 5XF- 046 F
REFNUMWF PRIME REFERENCE NUMBER 32 X L - 337 F
SEQNUMWF ACRN SET SEQUENCE NUMBER 2NF- 919 F
CAGECDWE ACRN CAGE CODE 5XF- 046 F
REFNUMWE ACRN REFERENCE NUMBER 32 X L - 337 F
FRBTCHWE FROM BATCH NUMBER 10 X L - 917 F
TOBTCHWE TO BATCH NUMBER 10 X L - 917 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
FRSNUMXD SERIAL NUMBER FROM 10 X L - 373 F
TOSNUMXD SERIAL NUMBER TO 10 X L - 373 F
AUTHTFWJ AUTHORITY TO FIT SERIAL NUMBER 1AF- 911

TABLE WK, AUTHORITY TO FIT ACRN ON SYSTEM/END ITEM


182. This table can be used to cross reference which parts, identified by CAGE Code and Reference
Number, from an ACRN Set of alternative parts, may be fitted to End Items. The conditions under which the
alternative part from the ACRN Set may be fitted, are identified by the Authority To Fit. Table keys consist of
ACRN CAGE Code (CAGECDWE), ACRN Reference Number (REFNUMWE), ACRN Set Sequence Number
(SEQNUMWF), Prime CAGE Code (CAGECDWF), Prime Reference Number (REFNUMWF), From Batch
Number (FRBTCHWE), To Batch Number (TOBTCHWE), EIAC (EIACODXA), LCN (LSACONXB), ALC
(ALTLCNXB), and LCN Type (LCNTYPXB).

CODE DATA ELEMENT TITLE FORMAT DED KEY


CAGECDWE ACRN CAGE CODE 5XF- 046 F
REFNUMWE ACRN REFERENCE NUMBER 32 X L - 337 F
SEQNUMWF ACRN SET SEQUENCE NUMBER 2NF- 919 F
CAGECDWF PRIME CAGE CODE 5XF- 046 F
REFNUMWF PRIME REFERENCE NUMBER 32 X L - 337 F
FRBTCHWE FROM BATCH NUMBER 10 X L - 917 F
TOBTCHWE TO BATCH NUMBER 10 X L - 917 F
EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
AUTHTFWK AUTHORITY TO FIT 1AF- 911

3A-103
DEF(AUST)5692

TABLE WM, SERVICING LIBRARY


183. This table identifies the Servicings performed on the End Item that are identified by a Servicing
Identifier code. This code is used in the development of Planned Servicing Schedules (PSS). Table keys
consist of EIAC (EIACODXA) and Serving Identifier (SRVCIDWM).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 K

TABLE WN, SERVICING IDENTIFICATION


184. This table records identification details for Servicings performed on an End Item. The Servicing Title
describes the Servicing to be performed, and the Sign-up Requirement determines whether the printed
format will have signature columns for Tradesmen, Progressive Inspector and Independent Inspector. Table
keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB) and
Servicing Identification (SRVCIDWM). For a given row of table WN the EIAC must be identical for all keys
migrating from tables XC and WM.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
SVTITLWN SERVICING TITLE 120 X L - 935
SIGNUPWN SIGN UP REQUIREMENT 1AF- 936

TABLE WO, SERVICING TASK


185. This table is used as a cross-reference to identify the tasks conducted as part of a particular Servicing.
LCN, ALC, and LCN Type are migrated from Table CA and given the role names of Servicing Task LCN,
Servicing Task ALC, and Servicing Task LCN Type. For a given row of table WO the EIAC must be
identical for all keys migrating from tables CA and WM. Table keys consist of all columns.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
SRVLCNWO SERVICING TASK LCN 18 X L - 199 F
SRVALCWO SERVICING TASK ALC 2NF- 019 F
SRVLTYWO SERVICING TASK LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F

TABLE WP, SERVICING INTERVAL AND EVENT MEASUREMENT BASE


186. This table defines the measurement base (EVENT), and number of occurrences (SERVICING
INTERVAL) between each performance of a Servicing. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Servicing Identification (SRVCIDWM) and Event
Measurement Base (EVNTMBWA). EIACODXA is identical for keys from tables XB and WM for a given row
of data. The following defines an R1 Servicing performed every 28 elapsed days.

SERVICING IDENTIFIER SERVICING INTERVAL EVENT


R1 28 ELPDYS

3A-104
DEF(AUST)5692

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
EVNTMBWA EVENT MANAGEMENT BASE 6XL- 923 F
SVCINTWP SERVICING INTERVAL 10 N R - 934

TABLE WQ, SERVICING FACILITY


187. This table is a cross-reference used to designate where an End Item Servicing is to be performed.
Table keys consist of all columns.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
FACNAMFA FACILITY NAME 32 X L - 118 F
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 F
FACTYPFA FACILITY TYPE 1AF- 483 F

TABLE WR, SERVICING TECHNICAL MANUAL


188. This table is used as a cross-reference to identify the Technical Manual that contains the Servicing
information required for a scheduled Servicing. Table keys consist of all columns.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437 F

ABLE WS, SERVICING GROUP


189. This table identifies groups of tasks conducted during a Servicing on an end item. Groups of tasks are
identified by a Servicing Group Identifier and performed sequentially during a Servicing in the order
designated by the Servicing Group Sequence Number. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Servicing Identification (SRVCIDWM) and
Servicing Group Identifier (GRUPIDWS).

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
GRUPIDWS SERVICING GROUP IDENTIFIER 4XL- 930 K
GRPSEQWS SERVICING GROUP SEQUENCE NUMBER 4NR- 931

3A-105
DEF(AUST)5692

TABLE WT, SERVICING GROUP TASKS


190. This table identifies the tasks required in each Servicing Group. Each task that is assigned to a
Servicing Group is given a Servicing Task Sequence Number to designate the order in which tasks are
carried out. Table keys consist of all columns. For a given row of table WT the EIAC must be identical for all
keys migrating from tables WO and WS.

eg.

A97 E
SERVICING SERVICING SERVICING GROUP TASK CODE TASK LCN NOMENCLATURE
IDENTIFIER TITLE GROUP SEQUENCE SEQUENCE
NUMBER NUMBER
R1 28 DAY ELEC 00 EHDUGAA 00 A01AB83 Generator
SERVICING DUTYGAA 01 A35DG66 Synchrophasor
LOUYGAA 02 A45EO12R Phasegeno
MKLPGAA 03 A94KJ48 Snchrotor
ENG 01 GHSYGAA 00 A23GHYUDD Turbine
IYUEGAA 01 A87ODCIMC Propellor
KUYSGAA 02 A11JUER Turpellor
NJUYGAA 03 A12JNDC Probine

The Servicing Group Task example shown above describes an End Item (A97E) Servicing (R1) which
requires the tasks in SERVICING GROUP ELEC to be performed first (GROUP SEQUENCE NUMBER 00),
and in the sequence listed by the TASK SEQUENCE NUMBER, followed by the tasks in SERVICING
GROUP ENG.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
SRVCIDWM SERVICING IDENTIFIER 4XL- 933 F
GRUPIDWS SERVICING GROUP IDENTIFIER 4XL- 930 F
SRVLCNWO SERVICING TASK LCN 18 X L - 199 F
SRVALCWO SERVICING TASK ALC 2NF- 019 F
SRVLTYWO SERVICING TASK LCN TYPE 1AF- 203 F
TASKCDCA TASK CODE 7XF- 427 F
TSKSEQWT SERVICING GROUP TASK SEQUENCE 4NR- 932 K
NUMBER

TABLE WU, TECHNICAL MANAGEMENT CODE LOG


191. This table identifies the type of historical log required for each TMC. Log Requirement defines the
amount of information recorded on the maintenance management system (ie., CAMM/CAMM2). Table keys
consist of TMC (TMNTCDWG) and Log Requirement (LOGREQWU).

CODE DATA ELEMENT TITLE FORMAT DED KEY


TMNTCDWG TECHNICAL MANAGEMENT CODE 23 X F - 938 F
LOGREQWU LOG REQUIREMENT 3XL- 926 K

TABLE WY, LCN INFORMATION EXTENSION


192. This table can be used to record data used in the Configuration Management and Maintenance
Requirements Determination processes. Table keys, EAICODXA, LSACONXB, ALTCNXB and LCNTYPXB
migrate from table XB.

193. Table RA table keys EIACODXA, LSACONXB, ALTLCNXB and LCNTYPXB migrate from table RA as
non-identifying field values and are given the role name WACEIAWY, WACLCNWY, WACALCWY and

3A-106
DEF(AUST)5692

WACLTYWY. For a given row of information EIACODXA and WACEIAWY must be identical for keys from
RA and XB.

194. For a given row of information, entries are not allowed for CAGECDWF, REFNUMWF, SEQNUMWF,
CFGCODWY, REQFITWY AND REPLEVWY where LCNTYPXB is ‘F’.

195. ACRN Set information; Prime CAGE Code (CAGECDWF), Prime Reference Number (REFNUMWF),
and ACRN Set Sequence Number (SEQNUMWF); migrates from table WF as non-identifying field values.
For a given row in table WY, ACRN Set information may only be assigned where a match exists between the
ACRN set's Prime CAGE Code and Prime Reference Number, and the CAGE Code and Reference Number
combination in the HG table for the LCN of the item being addressed in the given row of the WY table.

196. For a given row in Table WY, CAGECDWF, REFNUMWF and SEQNUMWF must all have entries or
be blank.

197. For a given row in Table WY, WACEIAWY, WACLCNWY, WACALCWY, WACLTYWY and
WACODERA must all have entries or be blank.

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
CAGECDWF PRIME CAGE CODE 5XF- 046
REFNUMWF PRIME REFERENCE NUMBER 32 X L - 337
SEQNUMWF ACRN SET SEQUENCE NUMBER 2NF- 919
CRITEMWY ITEM CRITICALITY 2XL- 925
CFGCODWY CONFIGURATION CODE 1XF- 920
REQFITWY REQUIRED FIT 1AF- 929
MTBFBXWY MEAN TIME BETWEEN FAILURE-B 10 D - - 928
WACEIAWY WAC EIAC 10XL- 096
WACLCNWY WAC LCN 18XL- 199
WACALCWY WAC ALC 2NF- 019
WACLTYWY WAC LCN TYPE 1AF- 203
WACODERA WORK AREA CODE 5XL- 940
EXTNOMWY EXTENDED NOMECLATURE 100 X L - 909
REPLEVWY LCN REPLACEMENT LEVEL 1AF- 910
CMCODEWY COMMON MANAGEMENT CODE 11 X F - 908

3A-107
DEF(AUST)5692

AUSTRALIAN DEFENCE ORGANISATION Z TABLES


198. Data tables beginning with "Z" in the first position of the table code record information for LCN/ALC
configuration information. There is only one table in this group; ZL.

TABLE ZL, ALCS WITHIN ALCS


199. This table identifies the base ALC or base model that an ALC is the alternate to when this is not
apparent from the LCN coding. This traceability is only required when all ALCs in a given LCN structure
have been made identical for compatibility with CAMM2, creating a requirement for structures of ALCs within
ALCs. Each table record identifies the base ALC to which an ALC belongs. Table keys consist of all
columns. For each ALC and Base ALC, all other key fields migrating from table XB shall be equivalent.

Example:

Model A Model B
LCN: A1A0 LCN: A1A0
ALC: 00 ALC: 10
ALC to ALC 00: 01 ALC to ALC 10: 11

Resulting record:

LSACONXB: A1A0 A1A0


ALTLCNXB: 01 11
LCNTYPXB: P P
BASALCZL: 00 10

CODE DATA ELEMENT TITLE FORMAT DED KEY


EIACODXA END ITEM ACRONYM CODE (EIAC) 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
BASALCZL BASE ALC 2NF- 019 F

3A-108
DEF(AUST)5692 ANNEX B TO
CHAPTER 3

LOGISTIC SUPPORT ANALYSIS RECORD REPORTS


INTRODUCTION
Purpose

1. This Annex contains a listing and description of the Logistic Support Analysis (LSA) Record (LSAR)
reports and guidance for data utilisation. Reports will be selected by the requiring authority to tailor and
document the results of the support analysis tasks based on criteria as stated in Annex D. This
documentation provides the capability of developing product summaries from a common data source, thus,
enhancing data uniformity and reducing data product cost. These reports may be automatically produced
from a compliant LSAR Automated Data Processing (ADP) system. Requirements of this Annex will be
referenced and implemented in contractual documents, as specified in the Contract Data Requirements List
(CDRL).

Concept

2. An LSAR ADP system will, as a minimum, produce the reports shown in the example summaries, on
an individual basis from computer stored data. This capability permits automatic generation of product and
analysis reports detailed in the Report descriptions and data element listings of this Annex. A compliant
LSAR ADP system can be used to automatically generate the summaries contained in this Annex based
upon the specific ADP processing requirements of the compliant system. When required, any or all of the
LSAR reports contained in this Annex can be manually produced. When the LSAR reports are manually
prepared, they shall be in accordance with (IAW) the content, format, sequence and computational
requirements contained in the Report descriptions and data element listings of this Annex.

3. LSAR Data Table to Report Matrix. Figure 1 contains a matrix of LSAR data tables to reports.
Finding a report across the top of figure 1, and then reading down the column, a user can determine the
specific data elements required to produce the given report. The data appearing on the summaries; required
to qualify an item for a summary; used in report calculations; modified when used on an output; and, keys of
the tables directly impacting a report generation, are all specified by an identifying code. The data table
"business rules" and edits may dictate that additional data tables must be established prior to making a
specific table entry, eg., establishing a foreign key.

4. General Report Selection Criteria. Unless otherwise specified in the report description, LSA
summaries described here shall be in ASCII sequence. The following basic rules are provided as guidance
for report selection:

a. For Service Designator Code (DED 368) selections, choosing A, F, N, or M results in the
selection of the matched service designator code and X and J codes. Choosing T results in
selection of both T and J codes. All other code selections results in extraction of matched code
data only. Service designator qualification in many instances will occur by task code (DED
419).

b. Lower-tiered or "trailer" LSA Control Number (LCN) and Alternate LCN Code (ALC) selections
may be made against any report which specifies selection by LCN/ALC range. This further
defining a report selection is used when multiple configurations, alternate design or
maintenance concepts, or alternate vendors are contained in the LSAR. For example, as a rule,
the basic configuration of an equipment is identified by LCNs with no ALC entry. Their
alternate(s) at the component level are documented and the alternate is required on the
specified report, the basic selection would have no ALC entry. However, a lower indentured
LCN may also be used with the report selection to obtain the specific LCN(s) and ALC(s) of the
assembly(s) to be substituted for the basic configuration. Lower indentured LCN selections will
include the subordinate items to the alternate selected. Once the alternate assembly(s) and
their breakdown have been selected, the selection process will revert back to the original LCN
selection.

c. The Usable On Code (UOC) (DED 495) is a primary (and often mandatory) selection criteria
when selecting LSAR reports by LCN. It is used to identify the model/configuration relationship
of each LCN comprising a system/equipment and to control these relationships for LSAR report
generation. The UOC is critical, and should therefore be used when establishing an LSAR.
This requirement holds even if only one configuration/model of a system/equipment is being
documented. In accordance with table XC, contained in Annex A, each configuration/model is
DEF(AUST)5692

assigned a unique UOC at the system/end item level LCN. Each individual assembly/
component/ piece part is also "linked" to the assigned UOC of the model of which it is applicable
through tables XF and HO. When an assembly/component/piece part is applicable to more than
one configuration/model, then multiple UOCs are "linked" to the component for a single LCN
and ALC via tables XF and HO. This eliminates the requirement of duplicating analysis and
related data, merely because an item has application to multiple configurations/models. For
further information on the UOC, LCN, and ALC relationship, refer to Annex C.

Standard LSAR Summary Reports

5. The following table lists the 48 standard LSAR summary reports.

Report Report Title Sample


Number Output
LSA-001 Man-Hours by Skill Specialty Code and Level of Maintenance Figure 2
LSA-003 Maintenance Summary Figure 3
LSA-004 Maintenance Allocation Chart Summary Figure 4
LSA-005 Support Item Utilization Summary Figure 5
LSA-006 Critical Maintenance Task Summary Figure 6
LSA-007 Support Equipment Requirements Figure 7
LSA-008 Support Items Validation Summary Figure 8
LSA-009 Support Items List Figure 9
LSA-010 Parts Standardization Summary Figure 10
LSA-011 Special Training Equipment/Device Summary Figure 11
LSA-012 Facility Requirement Figure 12
LSA-013 Support Equipment Grouping Number Utilization Summary Figure 13
LSA-014 Training Task List Figure 14
LSA-016 Preliminary Maintenance Allocation Chart (PMAC) Figure 15
LSA-018 Task Inventory Summary Figure 16
LSA-019 Task Analysis Summary Figure 17
LSA-023 Maintenance Plan Summary Figure 18
LSA-024 Maintenance Plan Figure 19
LSA-025 Packaging Requirements Data Figure 20
LSA-026 Packaging Developmental Data Figure 21
LSA-027 Failure/Maintenance Rate Summary Figure 22
LSA-030 Indentured Parts List Figure 23
LSA-032 Defense Logistics Information System (DLIS) Submittals Figure 24
LSA-033 Preventive Maintenance Checks and Services (PMCS) Figure 25
LSA-036 Provisioning Requirements Figure 26
LSA-037 Spares and Support Equipment Identification List Figure 27
LSA-039 Critical and Strategic Item Summary Figure 28
LSA-040 Authorization List Items Summary Figure 29
LSA-046 Nuclear Hardness Critical Item Summary Figure 30
LSA-050 Reliability Centred Maintenance (RCM) Summary Figure 31
LSA-056 Failure Modes Effects and Criticality Analysis (FMECA) Report Figure 32
LSA-058 Reliability Availability and Maintainability Summary Figure 33
LSA-065 Manpower Requirements Criteria Figure 34
LSA-070 Support Equipment Recommendation Data (SERD) Figure 35
LSA-071 Support Equipment Candidate List Figure 36
LSA-072 Test Measurement and Diagnostic Equipment (TMDE) Requirements Summary Figure 37
LSA-074 Support Equipment Tool List Figure 38
LSA-075 Consolidated Manpower, Personnel and Training Report Figure 39
LSA-076 Calibration and Measurement Requirements Summary (CMRS) Figure 40
LSA-077 Depot Maintenance Interservice Data Summary Figure 41
LSA-078 Hazardous Materials Summary Figure 42
LSA-080 Bill of Materials Figure 43
LSA-085 Transportability Summary Figure 44
LSA-126 Hardware Generation Breakdown Tree Figure 45
LSA-151 Provisioning Parts List Index (PPLI) Figure 46
LSA-152 PLISN Assignment/Reassignment Figure 47
LSA-154 Provisioning Parts Breakout Summary Figure 48
LSA-155 Recommended Spare Parts List for Spares Acquisition Integrated with Production Figure 49
(SAIP)

Table 1: Standard LSAR Summary Reports


3B-2
DEF(AUST)5692

LSA-001, MAN-HOURS BY SKILL SPECIALTY CODE AND LEVEL OF MAINTENANCE


6. A report divided into two parts. It is used to determine manpower requirements of the
system/equipment, and to determine the time required and number of personnel, by Skill Specialty Code
(SSC), and person identifier to perform each subtask. The format is contained on figure 2. Spacing between
rows and columns is not critical on this report.

7. Tasks with operability codes of T and P are excluded from this report.

8. Part I contains a summary of annual man-hour expenditures by maintenance levels and SSC. Man-
hour totals are based on the number of systems supported by level of maintenance. The number of
maintenance tasks used to develop the report are displayed. The man-hour values displayed in each
column (level of maintenance) are derived for each SSC by multiplying the task frequency, times the sum of
the man-minutes per person identifier, divided by 60 and summing those values for each maintenance task
performed by a particular SSC. At the option of the user, more than one end item, system, component, etc.,
supported, at any given maintenance level, may be requested. Then the annual maintenance man-hours
displayed on the output report will be for the number of end items, systems, components, etc., specified.
These values are obtained by multiplying the number of items supported by each maintenance level times
the annual maintenance man-hours involved. Part I is sequenced by ascending SSC.

9. Part II contains a report of the man-hours, by person identifier, expended on each maintenance task.
Man-hours are the sum of the man-minutes per person identifier for the same person identifier involved in a
task, divided by 60. An evaluation of the skill specialty and the requirement for training equipment is
provided for each task code. It provides annual man-hours per item per maintenance task, and total man-
hours per maintenance task based on number of systems supported, and can be obtained for a specific
SSC/ Skill Evaluation Code. The annual man-hours per item column is obtained by multiplying the task
frequency times the man-minutes involved for the maintenance task and for a specific person identifier. The
total annual man-hours column is derived by multiplying the number of systems supported, as specified by
the user, times the annual man-hours per item column. Part II is sequenced by ascending SSC, then LCN,
and finally task code.

LSA-003, MAINTENANCE SUMMARY


10. A report which compares the current status of the system maintenance parameters with the
requirements recorded on the A data tables. The format is contained on figure 3. Spacing between rows
and columns is not critical on this report.

11. Task code functions of "O", "T", "U", "V", "Y", and "3 - 9", task code interval of "Y", and task operability
codes of "P" and "T", are not used in the LSA-003 report calculations. The elapsed time and man-hour
values printed on the status line of the report are calculated from data on the C data tables in the following
manner:

where ETm = Mean elapsed time


M-Hm = Mean man-hours
ETi = Elapsed time for task i (DED 224)
TFi = Task frequency for task i (DED 430)
M-Hi = Total man-hours for task i (DED 225)
N = Total number of tasks performed

The preceding computations are performed for each of the following groupings of tasks at crew and
organizational operation/maintenance (O/M) Levels:

a. Daily Inspection (task code position 1 is "A", and position 2 is "C").

b. Preoperative Inspection (task code position 1 is "A", and position 2 is "A").

3B-3
DEF(AUST)5692

c. Postoperative Inspection (task code position 1 is "A", and position 2 is "H").

d. Periodic Inspection (task code position 1 is "A", and position 2 is "E" or "B").

e. Mission Profile Change (task code position 1 is "M").

f. Turnaround (task code position 5 is "F").

Also, the preceding computations are performed for unscheduled tasks (task code position 2 is F, G, or J) at
all maintenance levels.

12. The scheduled and unscheduled values for annual man-hours per end item are derived by utilizing
data from the C tables for a given LCN using the task interval codes F, G, and J for unscheduled tasks and
all remaining task interval codes scheduled. The following calculations are performed at each maintenance
level:

where (M-Hs)a = Annual man-hours for scheduled maintenance (DED 020)


(M-Hu)a = Annual man-hours for unscheduled maintenance (DED 020)
TFi = Task frequency for task i (DED 430)
(M-Hs)i = Total man-hours for scheduled maintenance task i (DED 225)
(M-Hu)i = Total man-hours for unscheduled maintenance task i (DED 225)
N = Total number of tasks performed

The scheduled and unscheduled values are summed to yield total annual man-hours per end item.

13. The scheduled and unscheduled man-hours per operating hour are calculated by dividing the annual
man-hours per end item from the LSA-003 Report by the annual operating requirements specified on the A
table. This calculation is performed at each O/M level.

14. The status totals for all levels are calculated by summing the man-hours for each level of
maintenance.

15. The organizational inspection section is always shown first. The remainder of the report is sequenced
by ascending maintenance level (crew to depot).

LSA-004, MAINTENANCE ALLOCATION CHART SUMMARY


16. The maintenance allocation chart (MAC) Summary is a report consisting of four sections, three of
which are obtainable from the LSAR. Section I, Introduction is "boiler plate" information developed IAW
either figures 20 or 21 of MIL-M-63038 (TM) Manuals, Technical (Army). Sections II, MAC; III, Tool and Test
Equipment Requirements; and IV, Remarks are produced as separate sections of this summary. The report
is provided in standard or aviation format IAW figures 20, and 21, respectively, of MIL-M63038 (TM) (Army).
A report may be printed on plain bond paper. It is used as source information for the final MAC contained in
the organizational maintenance TM. The formats for the proof standard, and aviation, and draft MAC are
contained on figure 4. Spacing between rows and columns is not critical on the draft MAC.

17. Section II, consists of the man-hour allocations by maintenance function and maintenance level. Task
functions (1st position task code) for the draft MAC will appear as they do in the LSAR database. Task
functions not allowed on a proof MAC will be automatically included as follows:

a. Access, Disassemble/Assemble, Fault Locate times are included as part of the repair time.

b. End-of-Runway Inspection times are included as part of inspect time.

c. Remove and Install times are included as part of the Remove/Install time.

d. Remove and Replace times are included as Replace time.


3B-4
DEF(AUST)5692

e. Lubricate times are included as part of the service times.

f. Task Function Codes of "Q", "M", "U", "V", "O", "Y", "T", and "2 - 9", and task operability codes
of P and T, are not included on the MAC. The Task Interval Code "Y" is also not included on
the MAC.

18. Operations/Maintenance (O/M) Level "G" is not included on the proof MAC. The O/M level "L" is
included as part of Maintenance Category "H" on the standard MAC. Only O/M levels of "O", "F", and "D"
apply when the aviation MAC is developed. Maintenance category aviation unit (AVUM) equates to "O";
aviation intermediate (AVIM) to "F"; and Depot to "D".

19. For each O/M Level, the mean man-hours is calculated for all tasks with the same task function as
follows:

where M-Hm = Mean man-hours


M-Hi = Man-hours for task i (DED 225)
TFi = Task Frequency for task i (DED 430)
N = Total number of tasks performed

Man-hours are rounded to the nearest tenth of an hour. Section II is sequenced by ascending LCN or
Functional Group Code (FGC) (depending on the display option selected), then by ascending maintenance
function based on the first position of the task code.

20. Section III, Tool and Test Equipment Requirements. This section of the MAC consists of tools and test
equipment required by task function and maintenance level. The section may be selected by item category
code (ICC) or combination of ICCs. The section is used to identify tools and test equipment required to
perform the maintenance functions listed on the Section II Maintenance Allocation Summary. Sections II and
III are cross-indexed by the "Tool or Test Equipment Reference Code". Section III is sequenced by
ascending reference numbers.

21. Section IV, Remarks. The Remarks section is based upon Remarks entered against qualified MAC
tasks. Sections II and IV are cross-indexed by the Remarks Code contained in column 6 of section II and the
Reference Code of section IV. Only the proof MAC and Aviation MAC contain section IV. Section IV is
sequenced by ascending remarks reference code.

LSA-005, SUPPORT ITEM UTILIZATION SUMMARY


22. A report, by ICC, showing the use of the item by maintenance level and LCN. The report should be
used to justify the requirement for support equipment and determine the quantity and distribution
requirements. The report should also be used to determine recommended order quantities of repair parts
based on their total use. The format is contained on figure 5. Spacing between rows and columns is not
critical on this report.

23. The user has the option to choose between elapsed time an item of support equipment is used, or the
quantity of support items utilized. If the elapsed time option is selected, only the following ICCs are allowed:
D, E, F, G, H, J, M, N, P, R, S, T, U, V, AC, and 1 through 8. If the quantity option is selected, only the
following ICCs are utilized in the report: K, L, Q, W, X, Y, Z, AA, AB, AD, AE, and 9.

24. At each O/M Level, the total elapsed time for all tasks, where a particular item of support equipment is
used, is calculated as follows:

3B-5
DEF(AUST)5692

where ETt = Total elapsed time


TFi = Task frequency for task i (DED 430)
ETi = Elapsed time for task i (DED 224)
N = Total number of tasks performed

25. At each O/M Level, the total quantity of a repair part is calculated for each task where the repair part is
used as follows:

where TQ = Total quantity


TFi = Task frequency for task i (DED 430)
(QTY/TASK)i = Quantity per task i (DED 319)
N = Total number of tasks performed

26. The total elapsed time usage for support equipment for all maintenance levels, or total quantity for
repair part for all maintenance levels, is calculated by summing the total elapsed time usage or quantity,
respectively, for each level of maintenance.

27. When man-hours or elapsed times are reported, each value will be preceded by (P) or (M) to indicate
predicted or measured values being reported. Where a measured value has not been input, the report will
default to the predicted value.

28. The report is sequenced by ascending ICC first, then by ascending reference number, by maintenance
level, and by LCN or FGC (depending on which is selected in the display option).

LSA-006, CRITICAL MAINTENANCE TASK SUMMARY


29. The report provides a list of all maintenance tasks which exceed a specific value for task frequency, or
elapsed time, or man-hours, or annual man-hours. The specific value(s) exceeded is identified as critical
criteria. The report may be selected for any maintenance level or combination of levels and for scheduled or
unscheduled maintenance. The report should be used to pinpoint problem areas and plan maintenance for
critical components. The format is contained on figure 6. Spacing between rows and columns is not critical
on this report.

30. If unscheduled maintenance is selected, then task codes must contain an F, G, or J in the second
position. If scheduled maintenance is selected, task codes must contain an A, B, C, E, H, K, L, M, N, P, Q,
or R in the second position. Task interval codes (second position) of "Y", battlefield damage assessment
and repair (BDAR), and task operability codes of P and T, are not included in any LSA-006 calculations.

31. Annual man-hours are calculated by multiplying the mean man-hours by the task frequency for a given
task.

32. When man-hours or elapsed times are reported, each value will be proceeded by (P) or (M) to indicate
predicted or measured values being reported. Where a measured value has not been input, the report will
default to the predicted value.

33. The report is sequenced by descending critical value. If the critical values are identical, the report
sequences by ascending LCN, then by ascending task codes (starting with the first position).

3B-6
DEF(AUST)5692

LSA-007, SUPPORT EQUIPMENT REQUIREMENTS


34. A report of all support equipment (i.e., tools, test equipment, etc.) utilized by SSC and level of
maintenance. The report may be selected for any maintenance level or combination of levels. This report
should be used to develop tool kits for each skill specialty at each level of maintenance. The format is
contained on figure 7. Spacing between rows and columns is not critical on this report.

35. ICCs are limited to D, G, H, M, N, P, R, V, AC and 1 through 8. This report is sequenced first
according to the selected sequence option (SEQ OPT) (SSC then O/M Level, or vice-versa), then by LCN or
FGC (depending on the selected display option), and then by ascending reference number.

LSA-008, SUPPORT ITEMS VALIDATION SUMMARY


36. This summary provides a listing of those support items required to support/perform the task at each
maintenance level. The support items are categorized in groups of:

Support/Test Equipment and Tools (ICC D, G, H, M, N, P, R, V, 1 - 8, AC)

Spare and Repair Parts (ICC X, Y, Z, 9, AA, AB, AE)

Other (ICC E, F, J, Q, S, T, W, AD)

37. This summary will be used to review support items requirements for the maintenance and operator
task(s) involved and may be selected for an entire equipment, specific LCN range, maintenance level, or
ICC(s). The ICC grouping sequence is Support/Test Equipment and Tools first, Spare and Repair Parts,
then Other. Within each category, the report is sequenced by ascending maintenance level (crew to depot),
then by ascending reference number. The format is contained on figure 8. Spacing between rows and
columns is not critical on this report.

LSA-009, SUPPORT ITEMS LIST


38. A report by LCN, reference number, and national stock number (NSN), of all repair parts, tools/test
equipment necessary to support the system/equipment. The report may be selected for any ICC or
combination of ICCs, or single or multiple provisioning technical documentation selection code. It is
sequenced in either ascending LCN or reference number/commercial and government entity (CAGE) code.
The provisioning unit of measure price only, appears on the LSA-009 summary. The report should be used
to provide information necessary to assist in performing provisioning. The format is contained on figure 9.
Spacing between rows and columns is not critical on this report.

LSA-010, PARTS STANDARDIZATION SUMMARY


39. A report by reference number of all spare and repair parts comprising the system/equipment. The
report may be selected for any contractor technical information code (CTIC) or CTIC combination and for any
acquisition method code (AMC) or AMC combination. It can be utilized to assist in performance of DOD
Replenishment Parts Breakout Program. The report is sequenced by ascending reference numbers. The
format is contained on figure 10. Spacing between rows and columns is not critical on this report.

LSA-011, SPECIAL TRAINING EQUIPMENT/DEVICE SUMMARY


40. A report of all operator or maintenance tasks, which have been identified as requiring a special training
device and the narrative explanation of the training equipment requirement. The report should be used to
identify the requirements, and provide justification, for the acquisition of training devices. The format is
contained on figure 11. Spacing between rows and columns is not critical on this report.

41. As a minimum, at least one LCN within the selected range must have a qualified task that has a valid
entry for mean man-minutes and for mean minute elapsed time. Also, the qualified LCN must contain a "Y"
code entry for Training Equipment Requirement Code. This report is sequenced by ascending LCN or FGC
(depending on the display option chosen), then by ascending task codes (starting with the first position).

LSA-012, FACILITY REQUIREMENT


42. A report of all tasks which have been identified as requiring new or modified facilities, or facility
requirements identified for training. Tasks reported are limited to those documented against specific LCN
3B-7
DEF(AUST)5692

range and service designator code. In addition, a "Y" must be entered in the CA table, Requirements For, to
qualify for inclusion into the list. Also included in this summary are narrative explanation and justifications of
facility requirements. At the option of the requiring authority, existing facilities may also be documented and
reported. The report should be used to provide requirement and justification for the construction of new
facilities, or to determine additional work load at existing facilities. The format is contained on figure 12.
Spacing between rows and columns is not critical on this report.

43. Tasks with operability codes of T and P are excluded from this report.

44. When man-hours or elapsed times are reported, each value will be preceded by (P) or (M) to indicate
predicted or measured values. Where a measured value has not been input to the LSAR, the report will
default to the predicted value. Overflows of Reference Number exceeding 16 positions are printed on the
next line immediately below the first position of the Reference Number.

45. The LSA-012 report is sequenced by ascending values of LCN, or with an option to sequence by a
selected facility category code and all higher values. The report is selective by RPT TYP which will delineate
between a test, operational, training, or depot facility.

LSA-013, SUPPORT EQUIPMENT GROUPING NUMBER UTILIZATION SUMMARY


46. A report by maintenance level and Support Equipment Grouping Identification Number of the tasks,
which use the support equipment group. The report may be selected for any maintenance level or
combination of levels. The report should be used to provide the requirements, quantity, and justification for
the acquisition of support equipment. The format is contained on figure 13. Spacing between rows and
columns is not critical on this report.

47. When man-hours or elapsed times are reported, each value will be preceded by (P) or (M) to indicate
predicted or measured values being reported. Where a measured value has not been input, the report will
default to the predicted value.

LSA-014, TRAINING TASK LIST


48. A report by SSC of each task identified in the task inventory. As an option, it will display only those
tasks for which training is recommended. If this option is selected, then the report will output the rationale for
training recommendations and training location requirements necessary to perform a given task. The report
should be used to recommend a task for training and provide the basis for recommendation of the training
location of the task. The format is contained on figure 14. Spacing between rows and columns is not critical
on this report.

49. If the Training Recommended option is selected, then LCNs must qualify by checking for a Training
Recommendation Code of B, C or J. This report is sequenced by ascending SSC, then by ascending LCN.

LSA-016, PRELIMINARY MAINTENANCE ALLOCATION CHART (PMAC)


50. A preliminary report of task allocation by maintenance function and maintenance level, and a
preliminary report of tools, equipment, and spares/repair parts required by task function and maintenance
level. The report is used to identify tools and equipment by maintenance levels to perform the maintenance
functions, and to validate Source, Maintenance, and Recoverability (SMR) Codes for spares and repair parts.
It is divided into three parts. Part I is the basic maintenance allocations and is sequenced in either
ascending LCN or TM FGC; part II contains the tool listing; and part III contains the spare/repair part listing.
Both parts II and III are sequenced in ascending Reference Number and CAGE. The format is contained on
figure 15. Spacing between rows and columns is not critical on this report.

51. ICCs for parts II and III, Tools and Parts for the PMAC, may only be chosen from the following ICC
values for each grouping:

Tools (ICC - D, G, H, M, N, P, R, V, 1 - 8, AC, AD)

Parts (ICC - X, Y, Z, 9, AA, AB, AE)

52. Task codes with task functions of Q, Z, P, M, O, U, V, C, Y, T, and 2 through 9, and task interval of Y,
and task operability codes of T and P are excluded from the PMAC. The task function is spelled out on the
report and the O/M level code is displayed, following the function, in parenthesis.

3B-8
DEF(AUST)5692

53. The man-hours (M-HRS) are calculated for all tasks with the same task function as follows:

where M-Hm = Mean man-hours


M-Hi = Man-hours for task i (DED 225)
TFi = Task frequency for task i (DED 430)
N = Total number of tasks performed

54. If any or all of the mean man-hours for the LSA-016 summary are predicted, the man-hour column will
be followed by a (P). If all man-hours are measured, an (M) will appear.

55. The "NUMBER" appearing on part I is assigned based on the sequence of the LCN or FGC. The tool
and part references are assigned based on the sequence of the tool/part in parts II and III, respectively.

LSA-018, TASK INVENTORY SUMMARY


56. This summary is a comprehensive listing of all tasks performed by system personnel to operate and
maintain the item. It can be used in workload analysis to model crew member activities and to create
operating and some maintenance scenarios. The report is capable of producing an inventory of tasks for all
"Jobs" (Table CJ) within a given system, or for selected "Job" combinations. The format is contained on
figure 16. Spacing between rows and columns is not critical on this report.

57. The report will be sequenced by ascending Job Code (Table CJ) and ascending Duty Codes (Table
CJ) within each Job. Duty will be printed out left justified on the output and Job will appear in parentheses
following Duty. Task Identification will be indented beneath Duty and Job; Subtask Identification will be
indented beneath Task Identification; and the Element narrative will be indented beneath Subtask
Identification (if applicable).

LSA-019, TASK ANALYSIS SUMMARY


58. This summary provides a listing of support items and skill specialty requirements needed to perform
maintenance tasks. The report is designed to be used in the preparation of maintenance manuals and
during physical teardown logistic demonstration (PTLD), both to record data as a result of the PTLD, and to
review the results of the PTLD against the LSAR database. At the option of the user, the report may also
contain the narrative sequential subtask description for each task, and the description of those subtasks
which are referenced. The referenced subtask descriptions will appear in the proper sequence of the task
description requested. The summary may be requested by maintenance level, Hardness Critical Procedure
(HCP), task interval, task function, and SSCs/ICC(s). The format is contained on figure 17. Spacing
between rows and columns is not critical on this report.

59. Tasks with operability codes of T and P are excluded from this report.

60. The support items identified in the LSAR database to perform the identified task are categorized by
ICC in the same manner as described for the LSA-008 summary.

61. If the HCP option is selected, then only tasks with an associated HCP code of Y or S will qualify and
be output. If the task interval (second position of task code) option or task function (first position of task
code) option is chosen, only tasks with the selected task interval and/or task function will qualify.

62. If the task narrative option is selected, tasks should have a valid mean man-minute entry and mean
minute elapsed time entry and a support item suppression option can be selected. If the task narrative
option is not selected, then either predicted or measured elapsed times and man-hours are allowable with
measured taken first precedence and the support items cannot be suppressed.

3B-9
DEF(AUST)5692

63. There is a space available at the end of each LCN for the reviewer to manually insert and describe
those support items not identified in the LSAR, but found to be required during the PTLD review. Also, there
is space available for manual entries for manually measured elapsed time, manually measured man-hours,
actual quantity used, manual evaluation, and reviewer's name.

64. This report is sequenced by ascending LCN or FGC (depending on display option selected), then by
ascending task code. The support items portion is sequenced by ascending ICC (A - Z, 1 - 9), then by
ascending reference number.

LSA-023, MAINTENANCE PLAN SUMMARY


65. The report consists of four parts which may be selected either together or individually. Part I contains
general information pertaining to the system/item selected and the maintenance concept and plan rationale.
Part II contains the reliability, availability, and maintenance characteristics of the system/item. This part may
be selected by LCN or work unit code for the desired maintenance level. Part III describes the preventive
and corrective maintenance action requirements. Corrective tasks are determined by task interval code
values of "J", "F", and "G". Part IV contains a listing of required support equipment and associated technical
data by ICC. This part may be selected for any ICC or combination of ICCs. The report can be sequenced
by either LCN or TM-FGC. Format contained on Figure 18. Spacing between rows and columns is not
critical on this report.

66. Tasks with operability codes of T and P are excluded from this report.

67. The LSA-023 summary is selective by mandatory EIAC, Start LCN, ALC, Type, UOC, and Serv Des;
and optional Stop LCN. Part 3 is selected by either preventive, corrective, or both type tasks. Part 4
selection also requires specifying the ICCs for support equipment requirements of each task. The ICCs
allowable for part 4 are: D, G, H, M, N, P, R, V, 1 - 8, and AC (see annex E, DED 177, for a listing and
definitions of various ICCs).

68. In part 1, reference number, CAGE, and item designator code may not appear if LCN Type is
functional (F). In Part 2, NSN and related data, reference number, CAGE, Maximum Allowable Operating
Time (MAOT), Maintenance Action Code (MAC), SMR, Unit of Issue (UI), and UI Price may not appear if
LCN Type is functional. In part 3, the number (NO) SSC can be calculated by summing up the number of
person identifiers in table CD for a given SSC for a given task. When man-hours or elapsed times are
reported, each value will be preceded by (P) or (M) to indicate predicted or measured values being reported.
Where a measured value has not been input to the LSAR, the report will default to the predicted value.
Overflows of Reference Number exceeding 16 positions are printed on the next line immediately below the
first position of the Reference Number.

69. Depending upon the display option chosen, for parts 1, 2, and 4 when the display option of TM FGC is
selected, the output is sorted by ascending TM FGC, then ascending LCN. If LCN option is selected, those
sections are sequenced by LCN first, then TM FGC. Part 3, A and B sections, should be sequenced by
maintenance level (crew to depot), ascending LCN, then ascending task code (starting with the first position).

LSA-024, MAINTENANCE PLAN


70. The report consists of three parts which may be selected either together or individually. Part I contains
general considerations (design description, maintenance plan summary, and maintenance plan rationale) for
the LCN selected. Part II describes the repair capability required to support the LCN selected and includes
maintenance technical data for the LCN selected and its lower indenture level repairable items, and
maintenance significant consumable items. Part III contains a list of the maintenance tasks by category
(preventive, corrective, servicing and calibration) for the LCN selected and its lower assembly repairable
items. The report can be selected for any maintenance level by LCN down to piece part. The format is
contained on figure 19. Spacing between rows and columns is not critical on this report.

71. Tasks with operability codes of T and P are excluded from this report.

72. The following definitions are for header information for the LSA-024 summary which are not contained
in the LSAR:

a. Date of Initial Submission/Revision/Date of Revision. A 19-position field containing the date of


the initial submission of the maintenance plan, alphabetic revision indicator, and date of the
current revision. The dates and revision should be entered in the following format, including
slashes and dashes: MM-DD-YY/A/MM-DD-YY.
3B-10
DEF(AUST)5692

b. Preparing Activity. A 15-position field containing the name of the performing activity having
responsibility for the data.

c. Prepared By. A 15-position field containing the name of the individual having responsibility for
accuracy of the data.

d. Defense Logistics Services Centre (DLSC) Screen Date. An eight position field containing the
date indicating when screening results were accepted by the government on all repairable
items. The date should be entered in the following format, including dashes: MM-DD-YY.

e. Navy Ammunition Logistic Code (NALC). A four position alphanumeric code identifying the
generic description within the Federal Supply Class. The NALC is assigned by Ships Parts
Control Centre (SPCC). The NALC is used for fleet reporting/requisitioning of ammunition and
to indicate functional interchangeability of items.

f. Maintenance Plan Number. A number identifying each maintenance plan. The maintenance
plan number is assigned by the requiring authority (DED 209).

73. Definitions for technical factors are as follows:

a. Maintenance Replacement Factor (MRF) Repairables. The expected rate at which an item is
found to be beyond the capability of maintenance (BCM) below the depot level and is inducted
at the depot for repair or condemnation per maintenance cycle.

b. MRF Consumables. The predicted number of times an item will require replacement (due to
failure, forced removal) in one maintenance cycle at the Organizational/Intermediate levels of
maintenance.

c. Depot Scrap Rate (DSR). The expected percentage of the items scrapped at the depot level
per maintenance cycle.

d. Below DSR (BDSR). The predicted number of times in one maintenance cycle that a field level
repairable will be disposed of at the Organizational/Intermediate levels of maintenance.

e. Rotatable Pool Factor (RPF). The predicted number of times in one maintenance cycle that an
item is removed from its next higher assembly at the Organizational/Intermediate level of
maintenance, repaired at the Intermediate level and returned to ready for issue at this level.

f. System Attrition Rate (SAR). The percentage of depot level repairable items that fail, which will
not, through repair, be returned to a serviceable condition.

g. Repair Survival Rate (RSR). The percent of nonserviceable repairable assets which will,
through depot repair, be returned to serviceable condition.

h. Rework Removal Rate (RRR). The percentage of the total quantity of a repairable assembly
installed in an end item which will require some depth of rework concurrently with that end item.

i. Interval. The recommended operating hours, or usage rate, followed by an alpha character
indicating the type of maintenance requirements for an item. The calculation and codes are as
follows:

P. Preventive (task functions A and Z)


C. Corrective (task functions B, G, R, J, H L, K, N, S, O, W and 2)
T. Servicing (task functions P, M and C)
U. Calibration (task functions D, E and F)

j. Maintenance Cycle. This data is calculated as follows:

3B-11
DEF(AUST)5692

74. The calculations for technical factors are computed as follows:

where MTD = Maintenance task distribution (MTD)


MTD(F) = Second subfield of the MTD
MTD(H) = Third subfield of the MTD
MTD(D) = Fifth subfield of the MTD
MTD(CBD) = Sixth subfield of the MTD
MTD(CAD) = Seventh subfield of the MTD
MRR = Maintenance Replacement Rate

75. Part II interchangeability/replaceability (I/R) code is determined based on the interchangeability code
(IC) entered in table HP:

IC I/R

OW I
OR I
TW I
OM R
TM R
NI Blank
NR Blank

When multiple ICs are contained in table HP for a given reference number, CAGE, LCN and ALC
combination, the order of precedence for I/R assignments are "I" followed by "R", then blank.

76. Part III, Requirement Number (REQ NO) is a five position counter (first four positions are numeric and
the last position is alphabetic), which is generated based on the type of task being displayed. The counter
begins at 0001 for each type of task and the alpha codes consist of P (preventive), C (corrective), T
(servicing) and U (calibration).

77. Part I is sequenced by ascending LCN or FGC (depending on display option selected); Part II is
ascending LCN, then ascending reference number; and, Part III is sequenced by ascending LCN, then
maintenance type (in the order of P, C, T and U).

LSA-025, PACKAGING REQUIREMENTS DATA


78. A report of the basic data requirements for preservation and packing for common, selective, and
special group items. This report consists of four 80-character card record formats of packaging information
as specified by MIL-STD-2073. The report should be used to provide adequate packaging instructions for
DOD users. It is selectable by either LCN range, a specified reference number and CAGE combination, or
by a specified degree of protection (DOP). An optional 80-card column magnetic tape output is also
available. The report is sequenced in ascending reference number and CAGE, and DOP. The format is
contained on figure 20.

3B-12
DEF(AUST)5692

79. The Supplemental Card Indicator (SCI) is generated on the LSA-025 summary based on the following:

If only an "A" card is used, the SCI is "1".

If an "A" and "B" card are used, the SCI is "2".

If an "A", "B", and "C" card are used, the SCI is "3".

If an "A", "B", and "D" card are used, the SCI is "4".

LSA-026, PACKAGING DEVELOPMENTAL DATA


80. A report of the basic item identification data required for packing and preservation. The report can be
requested by a single or multiple LCN, specific reference number or UOC, or SMR source code. The report
can be used as a stand-alone or in conjunction with LSA-025 to provide packaging information for DOD
users. It is sequenced in ascending reference number and CAGE; within each reference number. The UI
prices are listed in descending order; application information is sorted in ascending LCN sequence. The
format is contained on figure 21. Spacing between rows and columns is not critical on this report.

LSA-027, FAILURE/MAINTENANCE RATE SUMMARY


81. A report identifying an item and annual operating requirements by LCN and task code. Only tasks with
a task function of "H" or "J" are included in this report. The report should be used to provide information
necessary to monitor failure rates, failure modes, task frequencies, and MRRs. The format is contained on
figure 22. Spacing between rows and columns is not critical on this report.

82. Tasks with operability codes of T and P are excluded from this report.

83. The user has the option of selecting this report based on the Operating Program, Operating
Measurement Base, and the MRRI/MRRII Ratio. When option 1 of the MRRI/MRRII ratio is selected, the
user should enter the required operating program and its associated measurement base (MB). The
operating MB should correspond to the MB of the AOR of the item under analysis. If the MRRII is to be
calculated, enter the required MRRI/MRRII ratio. If left blank, then MRRII cannot be calculated.

84. The report provides both the table value and the calculated value of task frequency and MRRs I and II.
The task frequency is calculated as described in DED 430, annex E. The MRRI is calculated using the
following formula:

The MRRII is calculated using the following formula:

85. When failure rate, mean time between maintenance (MTBM)-induced, and MTBM-no defect are
reported, each value is preceded by (M), (P), (A), or (C) to indicate measured, predicted, allocated, and
comparative analysis values, respectively. Where a measured value has not been entered, the report will
default to the predicted, then allocated, and finally comparative analysis.

86. The report is sequenced by ascending values of LCN for a given task code, then ascending task
codes. This holds true for the assembly LCN, repair part LCN, and task LCN. For the reliability, availability,
and maintainability (RAM) LCNs, they are sequenced in ascending value, then by failure mode indicators
(FMI).

3B-13
DEF(AUST)5692

LSA-030, INDENTURED PARTS LIST


87. This report consists of four options:

a. Option 1 - Draft Repair Parts and Special Tools List (RPSTL)

b. Option 2 - Proof RPSTL

c. Option 3 - Illustrated Parts Breakdown (IPB)

d. Option 4 - Stockage List Type Four

The format for each option is contained on figure 23.

88. The draft/proof RPSTL consists of four sections prepared IAW MIL-STD-335(TM) or MIL-M-49502(TM)
(Reference MIL-M-49502(TM), paragraph 6.4, for applicable document):

a. Section I, Introduction

b. Section II, Repair Parts List

c. Section III, Special Tools List

d. Section IV, Cross-Reference Indexes

Sections II, III and IV listings are produced as separate sections of this report. The lists may be printed on
plain bond paper or may be output to a word processor file to be used as source information for final RPSTL
preparation. The format contained on figure 30 represents MIL-STD-335(TM). Reference MIL-M-49502(TM)
for the correct format if that document is to be used in lieu of MIL-STD-335(TM).

89. Documentation of kits for RPSTL. In order to produce kit/kit component listings for the RPSTL, a kit
record first must be established and a Provisioning List Item Sequence Number (PLISN) assigned to this
item. In the data table, Overhaul-Kit NHA PLISN, against the application of the kit component record, an
NHA PLISN entry of the Kit PLISN with an NHA PLISN Indicator of "*" is required. Where the kit component
appears in the RPSTL hardware breakout, the phrase "PART OF KIT P/N" (automatically generated),
followed by the reference number of the kit, will be displayed following the provisioning nomenclature in the
description column. The kit components are automatically generated beneath the kit. The component listing
contains the applicable figure number, item number and quantity per assembly/figure duplicated from the
hardware breakout information.

90. FGC Header. A maximum of 9 lines of 36-position FGC or illustration header information may be
entered for each RPSTL figure listing. These headers are not stored in the LSAR.

91. The report is selectable by technical manual (TM) code and number and TM FGC range. Sections II
and III are sequenced by ascending TM FGC, then item number, and PLISN. Section IV, Part Number
Index, is sorted in ascending reference number and CAGE; Stock Number Index in ascending NSN national
item identification number, Reference Designation Index in ascending reference designation; and, Figure
and Item Number Index in ascending figure and item number.

92. Specific RPSTL processing (draft and proof).

a. The FGC headers are placed in the description column preceding the first row of data matching
on FGC with the FGC header key.

b. The PART NUMBER column contains 16-positions of the reference number. If the reference
number exceeds 16 positions, the remainder is printed immediately beneath the first 16 on the
next line.

c. For the description column, the item name will first appear, then two spaces followed by the
provisioning nomenclature, if applicable. The provisioning nomenclature is wrapped in the 36-
positions allocated for the description with "breaks" occurring only at spaces. Trailing periods
are placed following the last position of the item name/provisioning nomenclature to the end of
the description column. If there is an associated TM indenture code, then leading periods are
placed prior to the item name, equal to the number in the TM indenture code field.
3B-14
DEF(AUST)5692

d. If there is a nuclear hardness critical item code of "Y" against the item, the symbol "(HCI)" will
appear following the item name and preceding the provisioning nomenclature.

e. Following the provisioning nomenclature on a separate line, applicable UOCs of the item are
entered, preceded by "UOC: ". For the proof RPSTL, if the item has full effectivity, no UOCs are
displayed. Full effectivity is determined by comparison of the item's associated UOCs with all
the associated UOCs to the PCCN of the item. For the draft RPSTL, applicable UOCs are
always shown regardless of full effectivity.

f. Also extracted for kit entries are information of kit NHAs, which are handled as described in
paragraph "Documentation of kits for RPSTL". The Kit Reference Number is determined by a
match of the Kit NHA PLISN to a PLISN under the same PCCN in the parts application
provisioning data table. One item may be used in multiple "kits" by multiple kit NHA PLISN HH
entries. Beneath each kit, the rows that make up the kit are displayed using by item name, and
in parenthesis the quantity per assembly or quantity per figure, the figure number, a dash, then
the item number.

g. Under the QTY column, the quantity per figure is displayed, unless blank. If quantity per figure
is blank, then quantity per assembly is used.

h. Under the NSN column, a "Y" is displayed if both the federal supply classification (FSC) and
National Item Identification Number (NIIN) are not blank and the NIIN does not contain alpha
characters for the associated item. Otherwise "N" is displayed.

i. Under the Provisioning List Category Code (PLCC) column, only entries in Tools and Test
Equipment PLCC or "D"s are shown.

j. After all information following a FGC header is displayed, and before the next FGC header the
phrase "END OF FIGURE" is printed. The information is printed with no line skips between
rows. At the end of a page, a page number is assigned using the figure number from the first
record following the FGC header, followed by dash then "1". Multiple pages of the same figure
follow the same pattern, e.g., 3-1, 3-2, 3-3, etc. A page break occurs with each new FGC
Header set under a different FGC. If no FGC header is provided, the report "page breaks" each
time the figure number changes.

k. The section III description column is similar to the section II description with the addition of the
interpreted basis of issue (BOI). Each BOI is displayed by "BOI: " quantity, then either level or
end item. The level is interpreted (see DED 030). The end item is preceded by "PER" and
followed by "END ITEMS". The BOI is inserted between the provisioning nomenclature and the
UOC lines.

l. Section IV cross-reference indexes are produced as optional outputs, as specified by the


requester. The reference designations for the reference designation index will either include
those items having a nonidentifying migrating key of the appropriate figure and item number, if
these keys are present, or will include all related figure and item numbers, if these keys are not
in the reference designation table. Overflows of reference numbers or reference designations
exceeding 16 or 32 positions, respectively, are printed on the next line immediately below the
first portion of the element.

93. The IPB consists of four sections prepared IAW MIL-M-38807(USAF):

a. Section I, Front Matter

b. Section II, Maintenance Parts List

c. Section III, Numerical Index

d. Section IV, Reference Designation Index

Sections II, III and IV (each section is optional) listings are produced as separate sections of this report. The
lists may be printed on plain bond paper or may be output to a word processor file to be used as source
information for final IPB preparation.

3B-15
DEF(AUST)5692

94. Documentation of kits for IPB. Extracted for the IBP are any entries in table HH for qualified rows
matching on PLISNs which may have an NHA PLISN with an NHA PLISN indicator of asterisk (*). Where the
row of information is sorted in the report, the phrase "PART OF KIT P/N" will be displayed followed by the
Reference Number of the Kit. The Kit Reference Number is determined by a match of the table HH NHA
PLISN to a table HG PLISN under the same PCCN as the kit component. One row of data may be used for
a kit with multiple table HH row entries (kit components). Beneath each kit, the components that make up
the kit are displayed by item name, and in parentheses, the Quantity per Figure (QTYFIGHK) or Quantity per
Assembly (QTYASYHG), Figure Number (FIGNUMHK), a dash, then Item Number (ITEMNOHK).

95. The IPB report is selectable by technical manual/technical order (TM) code and number. Section II is
sequenced by ascending figure number, then index number and Section III by ascending Reference
Number. Section IV, Reference Designation Index, is sorted in ascending reference designation.

96. Stockage List Type Four. This option provides a listing of support items required for a
system/equipment. The listing is used as source information for preparation of stockage list type four parts
manuals.

97. The following data headers appearing on the LSA-030 are modified DED, or are in addition to the data
element dictionary definitions.

a. Reference Designation (Figure Key) (REF DESIG FIG-KEY). Reference Designation with an
associated Reference Designation Code of "F" (first eight positions only).

b. Special Stockage Indicator (SSI). Assigned by the requiring authority, the SSI is left blank by
the preparing activity.

c. Replacement Factor (REPL FACTOR). MRRI, fourth through seventh positions only.

d. Quantity per Application and Equipment. These entries are the Quantity per Assembly and
Quantity per End Item, respectively.

e. Item No. Item Number is a numeric entry assigned to each item in the report beginning with "1".

98. The report is selected by LCN range and is sequenced in ascending Reference Designation.

LSA-032, DEFENSE LOGISTICS INFORMATION SYSTEM (DLIS) SUBMITTALS


99. This summary provides a cross-reference between reference numbers selected for provisioning
screening and the submitter's control number. DLIS screening is specified by MIL-STD-1388-1A. This
summary provides a valuable tool once the items have been screened through DLSC files, and the screening
results are received as the DLIS results are sequenced by submitter's control number. The format is
contained on figure 24.

100. The following definitions are related to terms located on the LSA-032 summary, but not contained in
the LSAR:

a. Document Identifier Code (DIC). A three-position alphanumeric code which is used for
identifying interservice agency or intraservice agency logistic transactions. Reference number
and CAGE screening requests are identified by DIC "LSR". Items may be excluded from DLIS
screening, if an entry showing a screening result, is already contained in the DIC field for the
reference number and CAGE.

b. Priority Indicator Code (PIC). A single numeric code used to designate the required priority to
be applied to processing transactions (see DOD 4100.38-M).

c. Activity Code. A two-position alpha code identifying a DOD activity, Federal agency or other
authorized government agency for cataloging, standardization or other management purposes
(see DOD 4100.38-M).

d. Destination Code. A five-position alphanumeric code used in conjunction with the activity code
to register the address data for recipients of the results of provisioning screening (see DOD
4100.38-M).

3B-16
DEF(AUST)5692

e. Output Data Request Code (ODRC). A numeric series of established sets of data (Defense
Integrated Data System output segments) identified by specific ODRGs and available for
extraction from DLSC files for provisioning and preprocurement screening purposes (see DOD
4100.38-M).

f. Single/Multiple Output Code. A numeric code used by the submitter to indicate whether the
results of screening are to be furnished to one or all of the recipients as registered under the
applicable activity code and destination code (see DOD 4100.38-M).

g. Submitter's Control Number. A 17-position computer assigned alphanumeric field peculiar to


provisioning and preprocurement screening transactions which is used to control and reference
the transactions. The number consists of a four position julian date (YDDD), and a unique
sequential 13 position number assigned for each reference number and additional reference
number package which is to be screened.

h. Statistical Indicator Code. A code designating whether data submitted for screening is required
for provisioning or other services (see DOD 4100.38-M).

101. Report Processing.

a. Items may be excluded from the report by already having a screening result displayed in the
DIC field, or by DLIS Screening Result Code. The TAPE option results in an 80-column file of
part II information. The report is sequenced in ascending submitter control number.

b. The submitter control number is constructed from the PCCN/PLISN of the qualified record. The
PLISN used is the lowest valued PLISN for the item within the selected PCCN/LCN range (the
Same As PLISN field is blank). If no PCCN/PLISN is recorded for an item, then a Type "l" error
is displayed. No rows of data for the item are placed on part II.

c. If Additional Reference Number Select (ARN SEL) is "YES" and if the item has more than 24
additional reference numbers, then error Type "2" is displayed. The first 24 ARNs in ascending
reference number sequence are placed on part II of the report.

d. If a specific SOURCE CODE is selected and the SMR is not contained against an item, at its
first appearance, then error Type "3" is shown and the item is disqualified from part II.

e. If TYPE SCREEN CODE is "F" or "S", and if ARN SEL is "YES" and if an Additional Reference
Number matches the prime Reference Number, then error type "4" is displayed. Only the
duplicate ARN is disqualified from part II. In part II of the report, columns 41 and 42 are always
left blank for "F" or "S" type screen.

f. If TYPE SCREEN CODE is "P", and if either the reference number category code (RNGC) or
reference number variation code (RNVC) is missing for the reference number/CAGE (in HA) or
if ARN SEL is "YES" and any additional reference number and CAGE (in HB), then error Type
"5" is displayed. If the RNCC/RNVC is an ARN, only the ARN is disqualified from part II. If the
RNGC/RNVG is the prime reference number, then the entire item is disqualified from Part II.

LSA-033, PREVENTIVE MAINTENANCE CHECKS AND SERVICES (PMCS)


102. This summary provides operator/crew and organizational level preventive maintenance task
identification and description and equipment availability results. The PMCS are required for the operator and
organizational level TMs and are based on the results of the reliability centred maintenance analysis. The
report is selectable by either LCN range or TM code and number. The format is contained on figure 25.
Spacing between rows and columns is not critical on this report.

103. Task interval values are interpreted as follows; "A", BEFORE; "D", DURING; "H", AFTER; "C", DAILY;
"L", WEEKLY; "P", MONTHLY; "M", QUARTERLY; "N", SEMIANNUALLY; and "Q", YEARLY. If the interval
is "B", then the maintenance interval (DED 208) and measurement base (DED 238) are displayed under the
interval column. The measurement base is interpreted on the report, e.g., "S" is ROUNDS. If the report is
selected by TM Code, tasks are qualified to the PMCS report by an associated PMCS indicator (Table CA).
If the report is selected by LCN range, tasks are further qualified by maintenance level (Task Code, third
position) of Crew or Organizational. Tasks with operability codes of T and P are excluded from this report.

3B-17
DEF(AUST)5692

104. The report is sequenced in ascending Task Code Interval in the order contained in the previous
paragraph , then by ascending LCN. Each LCN is assigned a numeric item number beginning with "0001".
An alphabetic sequence code beginning with "A" is assigned to each task against the same LCN with the
same Task Code Interval. If the report is selected by LCN range, a page break is required between output of
Operator/Crew level PMCS tasks and Organizational level PMCS tasks.

LSA-036, PROVISIONING REQUIREMENTS


105. This report is a summary of those data recorded on the data tables identified for provisioning
requirements. The summary contains that data required for review at various provisioning conferences (e.g.,
long-lead time items conference, provisioning conference, etc.) and is used in the selection procedures to
identify repair parts requirements in support of the equipment to be fielded. The summary will satisfy the
deliverables cited in MIL-STD-1388-1A. Format contained in table I and sample report on figure 26.

106. The following "header" data required to identify the specified list(s) are not a part of the LSAR, but are
contained in the LSA-036 summary:

a. Procurement Instrument Identification (PII). A 19-position alphanumeric entry used to identify a


specific contractual document. The PII includes the PII number (PIIN) (l3 positions), and the
supplementary PII number (SPIIN) (6 positions).

b. Nomenclature of model or type number. A 21-position alphanumeric entry used to specify the
name, model, or type of equipment being provisioned.

c. Control Data. A 10-position alphanumeric entry used for control information as specified by the
requiring authority. This information may consist of such items as identification of provisioning
data in MIL-STD-1388-2 format or a Weapons System Code.

d. Prime Contractor's CAGE. A five-position alphanumeric entry which identifies the prime
contractor for the equipment being provisioned.

e. Submission Control Code. A five-position numeric entry used to control the submission of
provisioning data. The first submission will be 00001, and each subsequent submission is to be
numbered sequentially, one greater than the prior submission.

f. Date list submitted. A six-position numeric entry used to identify the date of submission. The
first two positions will identify the year, the next two will identify the month, and the last two will
identify the day.

107. DEDs for those data contained on the LSA-036 summary are contained in annex E. The first card
appearing on an LSA-036 list is the header record. Following this record, the LSA-036 report is sequenced
by ascending PLISN in Binary-Coded-Decimal (BCD), or Extended BCD Interchange Code (EBCDIC)
collating sequence. The PLISNs are then sequenced by ascending Card Format Indicator (CFI). Multiple
CFIs are sequenced by Type of Change Code (TOCC) in the following order: blank, D, G, L, Q, and M.
Finally, within the TOCC, items are sorted by ascending Card Sequence Number (CSN).

108. The report will display the following provisioning report control data:

a. CSN. A two-position numeric code which is used to sequence multiple data input cards for a
specific card format indicator. The initial card entry is coded 0l. Subsequent cards are coded
02-99.

b. CFI. A one-position alphabetic code: A-H, J-L used to identify a card format and content.

c. Reference Designation Overflow Code (RDOC) (Card/Block, D/45, on the LSA-036 summary).
A one-position alphabetic code: A and B used to link a long Reference Designation which
exceeds 32 characters. Code "A" is entered against the first 32 characters, and code "B" is
entered against the last 32 characters.

d. Multiple-Configuration UOC. A one, two or three-position alphanumeric code that indicates the
configuration(s) of a system/equipment on which the item under analysis is used based on the
UOC (DED 501) assignments. The UOC is alphabetic in the sequence A-Z, followed by AA-ZZ
(less Is and Os). A blank UOC indicates that the assembly/part is used in all configurations.
For example:
3B-18
DEF(AUST)5692

If there were three different model designations (in table XC) for a given PCCN as shown below:

Model UOC (DED 501)

(V)1 A
(V)2 B
(V)3 C

A single UOC is assigned to each item's application based on the number of model configurations that
the LCN is used on (table HO). (The combination model UOCs (D, E, and F) are automatically
generated).

LCN UOC System/End Item

1A1 (blank) (Used in all configurations)


1A2 A (Used in (V)1 configuration only)
1A21 B (Used in (V)2 configuration only)
1A3 C (Used in (V)3 configuration only)
1A31 D (Used in (V)1 and (V)2 configurations)
1A312 E (Used in (V)1 and (V)3 configurations)
1A318 F (Used in (V)2 and (V)3 configurations)

e. Quantity Per End Item (QPEI) (DED 317). The QPEI (three options) may be computed during
the LSA-036 report preparation using the formulas provided in the data definitions.

f. NHA PLISN (DED 258) and Overhaul Replacement Rate (ORR) (DED 281) Assignment. The
NHA PLISNs may be assigned during the LSA-036 report preparation based on the item having
a P- source code, an ORR entry, and a higher assembly PLISN having an SMR Code of P--D-.
The base ORR of the item is multiplied by the Quantity per Assembly (QPA) for each
succeeding indenture level. For example:

PLISN IND CD SMR QPA NHA PLISN NHA-IND ORR


CFFF F PADZZ 0002 CEAA N 005
CEAA E PAHDD 0002 CDEE N 001
CDEE D PAHDD 0003 CCDD N
CCDD C PAFHH 0001 CB12 N 002
CB12 B PAODD 0002 AAAA E 001
AAAA A PAODD 0001

For PLISN CFFF, the Overhaul PLISNs and associated ORRs are:

OVERHAUL PLISN ORR

CDEE 015
CB12 030
AAAA 030

Note:

1. PLISN CEAA is the item's immediate NHA PLISN. PLISN CCDD is disqualified because it is SMR Coded
PAOHH.

g. Same as PLISN (DED 364). The Same as PLISN may be assigned during the LSA-036
summary preparation.

h. Indenture Code (DED 162). The "A" indenture code (for the XB table system/end item) is
assigned by the LSA-036 process.

109. LSA-036 Update and Design Change Notices. There are five basic types of LSA-036 updates which
can result when LSAR data is added, changed, or deleted affecting provisioning lists (PL) previously
delivered. These transactions can be automatically generated using a validated LSAR ADP system by
establishing baseline records upon initial submission of the LSA-036. These transactions are based upon a
comparison of the current LSAR provisioning oriented data tables and provisioning data baselined by a
previous LSA-036 submittal.

3B-19
DEF(AUST)5692

a. Standard Data Update. For each LSA-036 card affected by data which has been added or
changed since the previous PL delivery or LSA-036 update, mandatory data, i.e., PCCN,
PLISN, CSN, and CFI, an "M" TOCC and the added/ changed data only are entered. If data
has been deleted, a "G" is entered in the TOCC and in the left most position of each field
deleted on the appropriate LSA-036 card. Data deletions and changes/additions occurring on
the same LSA-036 card will require both a change and deletion card for the appropriate data.

(1) If all data on an LSA-036 CFI is deleted, a delete transaction will be generated consisting
of the PCCN, PLISN, CSN "01", CFI (except A), key data associated with that CFI, and a
"G" TOCC.

(2) When an entire PLISN record is deleted, a delete transaction will be generated consisting
of the appropriate PCCN, PLISN, CAGE, Reference Number, and a "D" TOCC on the
01A card. Also, if the reference designation exists, it is displayed with the PCCN and
PLISN on the 01D card with a "G" TOCC. In addition, if any change authority related
information is changed, CFIs "F", "G", and "H" update transactions are also processed.

b. Quantity Data Update. If a quantity field is updated, mandatory data, a "Q" TOCC, and the
updated quantity data field(s) are entered. This will only apply to the following data: QPA, QPEI,
Total Quantity Recommended, Allowance Item Code Quantity, Minimum Replacement Unit,
Recommended Initial System Stock Buy, Recommended Minimum System Stock Level,
Recommended Tender Load List Quantity, Quantity Shipped, Quantity Procured and Prorated
Quantity. If additional data displayed on the same LSA-036 card also changes during the
update, only one change card is entered with TOCC "Q". If quantity data is deleted, a change
card is entered with a zero filled quantity and TOCC "Q".

c. Key Data Update. Certain provisioning data are considered key and associated data elements
and are listed below. Changes to key data requires the submission of both a delete and change
card for the appropriate key data. The deletion card should contain a "G" TOCC and the
original key data. The change card should contain an "M" TOCC with the new key data and the
applicable associated data. Deletion of key data will result in deletion of the corresponding
associated data.

KEY DATA ASSOCIATED DATA

(1) CAGE and Additional Reference Number RNCC and RNVC

(2) NHA PLISN ORR, NHA IND.

(3) UOC None

(4) Reference Designation RDOC


RDC

(5) PLCC None

(6) Change Authority Number Serial Number Effectivity


Prorated Exhibit Line Item Number
Prorated Quantity
IC, Replaced or
Superseding PLISN,
R/S Indicator, Design Change Notice
(DCN) UOC, Total Item Changes
Quantity Shipped
Quantity Procured

(7) Serial Number Effectivity None

(8) DCN UOC None

(9) TM Code Figure Number


Item Number

(10) TM Code, Basis of Issue (BOI)


Figure Number TM Change Number, TM Indenture Code
3B-20
DEF(AUST)5692

Item Number Quantity per Figure


TM FGC

(11) TM Code Provisioning Nomenclature


Figure Number
Item Number

(12) BOI-Control BOI-Quantity Authorized


BOI-End Item, BOI-Level

d. Associated Data Update. Changes to associated data require the submission of a change card
consisting of an "M" TOCC with the changed data and entry of the applicable key data. Deletion
of associated data requires the submission of a deletion card with a "G" TOCC, a "G" in the left
most position of the associated data field and entry of the key data.

e. DCN. DCN information is not distinguished from other updated data for a particular LSA-036
update using a validated LSAR ADP system. DCNs can be processed as a separate and
distinguishable report by specifying that DCN affected data must be processed as an exclusive
update, i.e., by performing an LSA-036 update, entering the DCN information into the LSAR,
and again running an LSA-036 update. An option to obtain an LSA-036 report for updated data
pertaining to a specific Change Authority Number is provided on the LSA-036 report options.
DCN information updates are similar to other update transactions with the following exception:
When a Change Authority Number and Serial Number effectivity are entered, an "L" TOCC is
entered for the replaced item. If a quantity change occurs on a limited effectivity item, an "L"
TOCC is entered in lieu of a "Q".

110. Part II, Standard Edit List. This section is automatically produced when an LSA-036 is requested. The
standard section lists those PLISNs matching the PCCN selected which were disqualified or would degrade
the provisioning list. This list must be reviewed by the user to ascertain what corrections, if any, are needed
to update the parts data tables for subsequent update(s) to the provisioning list.

111. Two optional part III listings are also available. Option 1 provides selectable provisioning data edits for
Army customer use. Option 2 contains Air Force L card data formats to merge with the basic LSA-036 A-K
cards.

LSA-037, SPARES AND SUPPORT EQUIPMENT IDENTIFICATION LIST


112. The purpose of this report is to provide information that identifies the investment spares (Section I),
expense spares (Section II), support equipment (Section III), and tools and test equipment (Section IV)
required for system support under contractor logistic support. Items qualify for a particular section based on
ICCs:

Investment Spare (ICC of X, AA)

Expense Spare (ICC of Y, Z, 9, AB, AE)

Support Equipment (ICC of G, H, 7, AD)

Tool and Test Equipment (ICC of D, M, N, P, R, V, 1-6, 8, AC)

113. This summary may be selected by sections, a specific LCN range, and selected ICCs (which must
qualify according to above criteria). Within each section, the report is sequenced by ascending
manufacturer's part number. The format is contained on figure 27. Spacing between rows and columns is
not critical on this report.

LSA-039, CRITICAL AND STRATEGIC ITEM SUMMARY


114. This report of items assigned a critical item code (CIC) or industrial materials analysis of capacity
(IMAC) code. Part 1 of the report lists CIC items. Part 2 of the report lists IMAC items. The report may be
selected for any CIC or may be selected for specific CIC or IMAC combinations. It may also be sequenced
by LCN or reference number (part I), or by LCN or IMAC (part II). The format is contained on figure 28.
Spacing between rows and columns is not critical on this report.

3B-21
DEF(AUST)5692

LSA-040, AUTHORIZATION LIST ITEMS SUMMARY


115. This summary is divided into two options. The first option consists of four parts: components of end
item, basic issue items list, additional authorization list, expendable durable supplies and materials list. The
items are identified by code A in position 1 and the appropriate list code in position 2 of the Allowance Item
Code (DED 017). These lists are required as source information to prepare an appendix to the operator's
manual, or in combined operator's and maintenance manual (i.e., a -12, -13, or -14), as specified by MIL-M-
63036, Manuals, Technical: Operator's, Preparation of. Each report part is listed in alphabetical sequence
by Item Name. Option 2, stockage list type three, consists of three parts (each selectable); supply system
responsibility, using unit responsibility, and collateral equipment. Items which belong in this summary will
have an "E" in the first position of the Allowance Item Code (Allowance Type). Format is contained on figure
29. Spacing between rows and columns is not critical on this report.

116. Option 1, Part I, Components of End Item (COEI) List. This section provides a listing of those items
which are part of the end item. COEI are removed and separately packaged for transportation or shipment
only when necessary.

117. Option 1, Part II, Basic Issue Items (BII) List. This section provides a listing of those minimum
essential items required to place an equipment in operation, to operate it, and to perform emergency repairs.
These items are removed and separately packaged for transportation.

118. Option 1, Part III, Additional Authorization List (AAL). This section provides a listing of those items
which are not issued with an end item and are not listed/identified on the end item engineering drawings as
part of the end item configuration.

119. Option 1, Part IV, Expendable/Durable Supplies and Materials List (ESML). This section provides a
listing of those expendable/durable supplies and materials required to operate and maintain the equipment.

120. Option 2, Stockage List Type Three. This summary provides a listing of supply system and using unit
responsible items; principal end items; and,collateral equipment identified by entries in the Allowance Item
Code. The lists are used as source information to prepare stockage list type three TMs. It is sequenced by
Allowance Item Code entries, EA and ED (supply system responsibility); then, EC (using unit responsibility)
and EE (collateral equipment) items and by ascending reference designations. The CAGE listing is
sequenced by ascending CAGE. Item Number is a numerically assigned sequence number beginning with
"0001".

LSA-046, NUCLEAR HARDNESS CRITICAL ITEM SUMMARY


121. This summary provides a listing of all support items which are coded as nuclear hardness critical. The
report can be prepared for a specific LCN range and is sequenced by either ascending reference
number/CAGE or PCCN/PLISN. The format is contained on figure 30. Spacing between rows and columns
is not critical on this report.

LSA-050, RELIABILITY CENTRED MAINTENANCE (RCM) SUMMARY


122. This report is divided into three parts. The first part is the RCM analysis conducted on repairable
items of a system by disposition, task code, and safety hazard severity code (SHSC). This part is selectable
by SHSC(s) and sequenced by disposition only, disposition by maintenance level, or maintenance level only.
The second part of the report is a management summary showing RAM characteristics of the item,
preventive maintenance tasks, both table and calculated values for task frequencies, and the total man-
hours associated with the SSC for a given maintenance level. This part is selectable and sequenced similar
to part 1 with the addition of a sequence by SSC. The third part is used to evaluate the items that did not
have an RCM analysis accomplished against them. It is also selectable by SHSC(s) and is sorted by
ascending FMI values. The format is contained on figure 31. Spacing between rows and columns is not
critical on this report.

123. In part 2, Task Frequency is calculated by using the formula provided under DED 430 for preventive
tasks (method 1). The total number of man-hours is the summation of mean man-minutes per person
identification for the identical SSC and O/M level.

124. Tasks with operability codes of T and P are excluded from this report.

3B-22
DEF(AUST)5692

125. When elapsed time and man-hours are reported, each number is preceded by (M) or (P) to designate
either measured or predicted values, respectively. Where a measured value has not been input into the
LSAR, the report will default to the predicted value.

126. When the failure rate is reported, it is preceded by (M), (P), (A), or (C) to indicate measured, predicted,
allocated, and comparative analysis values, respectively. Where a measured value has not been entered,
the report will default to the predicted, allocated, and finally comparative analysis.

LSA-056, FAILURE MODES EFFECTS AND CRITICALITY ANALYSIS (FMECA)


REPORT
127. This summary consists of three parts. The first part contains FMECA, criticality analysis,
maintainability information, damage mode and effects analysis, and minimum equipment listing information
as specified by MIL-STD-1629. The second part is the criticality analysis information which is a listing in
descending order of each item's computed criticality or failure mode criticality number by SHSC. This part is
selectable by SHSC(s) and failure mode criticality numbers greater than a selected value. This part should
be used to identify candidates for RCM analysis or design reviews. The third part is the failure mode
analysis summary which consists of the failure modes and failure rates of each repairable item. The report
should be used to identify failure modes which impact item criticality number and SHSC assignment. The
format is contained on figure 32. Spacing between rows and columns is not critical on this report.

128. If part 1 of this report is selected, enter the SHSC (1, 2, 3, 4) of the failure modes which are of interest.
If the SHSC field is left blank, then only SHSCs 1 and 2 will be considered. A selection must be made for
either minimum Failure Probability Level or minimum Failure Mode Criticality Number. If both are selected,
Failure Probability Level will be disregarded.

129. Tasks with operability codes of T and P are excluded from this report.

130. Parts 1 and 3, Item Criticality Number (Cr) is calculated using the formulas contained in DEDs 178 and
133 (Failure Mode Criticality Number).

131. In Part 3, an edit check is made on this report to ensure that the sum of the failure mode ratios never
exceeds 1.00 for a given LCN. If this occurs, an "***" will be printed out under the Failure Mode Ratio
header.

132. When failure rate is reported, it is preceded by (M), (P), (A), or (C) to indicate measured, predicted,
allocated, and comparative analysis values, respectively. Where a measured value has not been entered,
the report will default to the predicted, then allocated, and finally comparative analysis. In part II, overflows
of Reference Number exceeding 16 positions are printed on the next line immediately below the first position
of the Reference Number.

133. Part 1 of the report is sequenced by ascending LCNs, FMIs, MPCs, then SHSCs. Part 2 is sequenced
by ascending values of Failure Probability Level, then LCN. Part 3 is sequenced by ascending LCNs.

LSA-058, RELIABILITY AVAILABILITY AND MAINTAINABILITY SUMMARY


134. This summary consists of two parts. The first part is the reliability summary redesign which provides a
narrative description for an item on which a redesign is proposed. This part should be used to review
potential candidates for redesign. The second part details the level of repair to be performed on an item for
all maintenance levels. This part is used to review the reliability and maintainability factors for the repair time
of an item. The format is contained on figure 33. Spacing between rows and columns is not critical on this
report.

135. Tasks with operability codes of T and P are excluded from this report.

136. In Part 1 of the report, Failure Mode Criticality Number or Failure Probability Level may be used.
However, Failure Mode Criticality Number should be used whenever possible. Also, if the LCN type of
subject LCN is functional, then the reference number and CAGE may not appear. In part 2, the (P) or (M)
preceding the elapsed time values represent predicted and measured, respectively. Measured values take
precedence.

137. Part 1 of the report is sequenced by ascending LCNs, then FMIs. Part 2 is sequenced by
maintenance level, then ascending LCNs and FMIs within each maintenance level.

3B-23
DEF(AUST)5692

LSA-065, MANPOWER REQUIREMENTS CRITERIA


138. This summary provides man-hour summary information by each task. The format is contained on
figure 34. Spacing between rows and columns is not critical on this report.

139. The following formula applies for Mean Time Between Task Maintenance Actions (MTBTMA) and
Man-Hours per person identifier (M-HRS PER PERS ID):

M-HRS PER PERS ID is computed by summing all subtask mean man-minutes per person identifier
for each entry matching an identical person identifier and SSC and then dividing this value by 60.

140. The report displays the system/component reference number. Within each reference number, tasks
are displayed by unscheduled/on equipment (task interval codes F, G and J; and task operability codes A, B,
C, D and E); unscheduled/off equipment (task interval codes F, G and J; task operability Code G); and,
scheduled (all task interval codes except F, G, J and Y and all operability codes except T and P).

LSA-070, SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD)


141. A report describing requirements for and of one piece of support equipment. This report will include
administrative data, description of equipment, allocation data, design data, and Integrated Logistic Support
(ILS) requirements as specified by MIL-STD-2097. Format is contained in figure 35. Spacing between rows
and columns is not critical on this report.

142. The E-CAGE/PN (Equivalent CAGE and Part Number) code in section 2 is generated based on
whether or not the support equipment reference number and CAGE has equivalent part numbers and
CAGEs. This is determined by searching the HB table additional reference numbers and CAGEs, and if any
are found, a "Y" code is produced for this field; otherwise, an "N" code is produced. If any matches are
found in table HB, they are output in section 2 (following the Articles Requiring Support section) under the
heading of Equivalent CAGE/PN(s) (page 6 of the LSA-070 example).

143. The alternate NSN code in section 2 is generated based on whether or not any alternate NSNs exist
on file for subject support equipment. This is determined by searching the EH table for valid entries. If any
are found, a code of "Y" is generated and alternative NSNs are output in another part of section 2 under the
heading alternative NSN (page 6 of LSA-070 summary).

144. Under the price data header in section 2, the design data and ILS values must equal the total design
data price and total ILS price that are calculated in sections 4 and 5, respectively.

145. Under the header "shipping modes" in section 2, narrative explanation of the different modes of
transportation for the piece of support equipment are explained. This information can be output only if the
reference number and CAGE of the support equipment has been linked to an LCN and ALC for the support
equipment. Once this link has been made, the information can be entered in, and subsequently pulled from,
the JD table under the Transported End Item Narrative element (Transported End Item Narrative Code of
"E").

146. Section 2 is sequenced by ascending reference number. Section 2, articles requiring support; and
section 6, unit under test (UUT) related information will be sequenced by ascending LCNs. Section 6 (OTP,
TPI and AID) will be sequenced by ascending UUT LCNs, then ascending reference numbers.

LSA-071, SUPPORT EQUIPMENT CANDIDATE LIST


147. This summary provides a consolidated listing of support equipment (SE) requirements divided into two
sections. Section I contains active SE candidates and section II contains disapproved SE candidates.
Section I is sequenced by end article LCN and Section II is sequenced by ascending reference number. The
format is contained on figure 36. Spacing between rows and columns is not critical on this report.

3B-24
DEF(AUST)5692

148. Section II, disapproved support equipment candidates, is qualified by finding valid SE candidates
within the specified LCN range with a status code (table EF) of "X". If the status code is not available, the
qualified SE will be included in Section I.

LSA-072, TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT (TMDE)


REQUIREMENTS SUMMARY
149. This report provides a two part summary of TMDE requirements and technical descriptions to verify
the applicability of the test equipment for use on the weapon system/end item. This report can be selected
by a range of LCNs, or by matching on the reference number and CAGE of subject piece of TMDE
equipment. If this report is selected by a range of LCNs, the sequence will be ascending LCNs, then
ascending reference numbers. The format is contained on figure 37. Spacing between rows and columns is
not critical on this report.

150. The part I header, "TMDE item selected by", will show the reference number and CAGE selected if
that option is chosen, or it will show the LCN and ALC which qualifies under the selected range of LCNs.

151. Under Part II, Quantity is calculated by multiplying the values for number of activities by the quantity
per activity (both values in ED table). Manual entries can be made at the end of part II for estimated type
classification date, prepared by, and the date.

LSA-074, SUPPORT EQUIPMENT TOOL LIST


152. This summary provides a listing consisting of four sections: tools currently in inventory; tools in
inventory but not assigned to gaining unit; modified hand tools; and, peculiar tools requiring development.
Each section can be selected by a limited number of ICCs. Section 1 is limited to group B ICCs (see DED
173); section 2 is limited to Group C ICCs; section 3 is limited to ICC of AC only, and, section 4 is limited to
Group A ICCs. The format is contained on figure 38. Spacing between rows and columns is not critical on
this report.

153. Part III, modified hand tools, assumes that a breakdown of the tool exists within the LSAR database. If
so, "make from" items will include those items which are subordinate to subject tool in LCN structure and
which have an Indenture Code greater than that of the tool (e.g., tool indenture code + 1).

154. Within each part of the report, an SE item is only listed once. If more than one qualified entry occurs
for a piece of support equipment, all information must be consolidated. Each part of this report is sequenced
by ascending reference number.

LSA-075, CONSOLIDATED MANPOWER, PERSONNEL AND TRAINING REPORT


155. This summary provides a depiction of critical manpower and personnel data by maintenance level and
new/modified skill requirements needed as a baseline for performing hardware-manpower requirements
analysis. The format is contained on figure 39. Spacing between rows and columns is not critical on this
report. Tasks with operability codes of T and P are excluded from this report to avoid duplication.

156. Available man-hours of 0.00 are significant as opposed to blank values which depict no person on file.
If actual man-hours can be calculated, the available man-hours will be output even if blank. Actual man-
hours are calculated by summing all mean man-minutes for a given SSC at a given maintenance level
across all applicable tasks, then dividing by 60.

157. Actual quantity of an SSC at a given maintenance level can only be calculated correctly if a unique
person identifier has been assigned to each maintenance person for the entire weapon system file and that
relationship is carried out for all tasks. If this method is used, then the actual quantity is simply calculated by
counting the different number of person identifiers for a given SSC at each maintenance level.

158. Section I is sequenced by ascending SSC, then by ascending maintenance level. Section II is
sequenced by ascending original SSC, then by ascending new SSC.

LSA-076, CALIBRATION AND MEASUREMENT REQUIREMENTS SUMMARY (CMRS)


159. This report details TMDE and the calibration standards and equipment required to assure traceability
of measurements through the required metrology and calibration programs to approved National Standards

3B-25
DEF(AUST)5692

as necessary by MIL-STD-1839. The format is contained on figure 40. Spacing between rows and columns
is not critical on this report.

160. Section I items consist of LCNs which have a CMRS Recommended Code (table UB) of 1 (Category I
CMRS). Section II consists of Category II CMRS items with a parameter group code (PGC) that matches the
PGC of the category I item and it also consists of calibration procedures (table EC) for the category II item.
Section III consists of category III CMRS items which have a PGC that matches the category II CMRS PGC.
Section IV consists of a full breakdown of each CMRS category I item from section I and the corresponding
sections II and III items associated with it. If a calibration procedure is identified for the category II CMRS
item, this calibration procedure will be output under the category III header of Section IV. If a calibration
procedure is not identified for the category II CMRS item, all qualifying category III CMRS items will be output
under the category III header of section IV.

161. The "Page" number in section I is generated based on the page number that includes the section IV
full breakdown of that category I item.

162. Section I of the report is sequenced by ascending LCNs. Sections II and III are sequenced by
ascending reference number. Section IV is based on the sequence of section I.

LSA-077, DEPOT MAINTENANCE INTERSERVICE DATA SUMMARY


163. This report contains three parts. Part I contains all depot repairable items and the applicable tasks
which are performed at depot. This part is sequenced in ascending LCN. Part II, section A, provides a
listing of all SE sequenced by ascending reference number and CAGE. Part II, section B, contains the new
or modified depot facilities requirements sorted by ascending facility category code and facility name. Part III
depicts depot SE and associated tasks requiring these support items. Part III is sequenced by ascending
reference number and CAGE of the SE. Within the above sequence, tasks are sorted in ascending LCN and
task code, and within task code by ascending person identifier code. Man-minutes are calculated by
summing all subtask mean man-minutes for the identical person identifier in a given task. The format is
contained on figure 41. Spacing between rows and columns is not critical on this report. Tasks with
operability codes of T and P are excluded from this report.

LSA-078, HAZARDOUS MATERIALS SUMMARY


164. The report provides a summary of all hazardous materials required to support a selected end item.
This summary identifies all items having associated hazardous materials storage, hazardous waste storage
or disposal costs. This summary also identifies the maintenance tasks requiring quantities and costs per
task. The summary is used to eliminate or reduce identified hazardous material items during the system
design process. Format contained at figure 42. Spacing between rows and columns is not critical on this
report.

165. The computed quantity is calculated by multiplying the task frequency times the quantity per task. The
total quantity required is calculated by summing all computed quantity for a given reference number and
CAGE.

166. The report is sequenced by ascending reference number and CAGE. Tasks are sorted in ascending
LCN and task code.

LSA-080, BILL OF MATERIALS


167. Part I (Parts List) identifies each assembly and provides a listing of the items related to or contained in
the assembly. The summary provides a vehicle for comparing the LSAR against the assembly drawings to
ensure items in the topdown breakdown of the assembly are contained in the LSAR data tables. Part II
(Error Listing) is automatically produced when the LSA-080 is requested. The format is contained on figure
43. Spacing between rows and columns is not critical on this report.

168. The LSA-080 summary is selected by either UOC and either LCN range or PCCN. If the report is
selected by LCN, the LCN-CODE should specify if the type of LCNs are either: classical or modified
classical.

169. The LSA-080 report, part I, identifies parts to the assemblies of which they are contained. Each
assembly will only show parts one indenture lower, e.g., a "C" indentured assembly will only show "D"
indentured items. These items may be both repair parts and spares. If the item is a spare, a separate page
breakdown of the item will appear on the report.
3B-26
DEF(AUST)5692

a. If the report is selected by LCN, then either the LCN structure, or LCN-IC and the LCN "values"
are used to place items to assemblies. All items sorted in ascending LCN sequence, with either
an LCN-IC or structure value of one indenture greater, are placed as items to an assembly until
within the sorted range another item is found at the same indenture level, or greater than the
assembly. Items at more than one indenture greater are "grouped" with the item (now
assembly) immediately preceding this indenture change. ALC items are "grouped" together as
an assembly/item set, if there is no indenture level missing between them. If an ALC item does
not have a matching ALC, it is then "grouped" to the blank or basic assembly item.

b. If PCCN is selected, PLISN and IC are used to sort items to assemblies, with all items sorted in
ascending PLISN sequence of one IC greater than the IC of the assembly PLISN record placed
below the assembly PLISN, until an IC is encountered that is equal to or greater than the
assembly IC. The NHA PLISN is a value found in table HH which is one indenture less than the
item with a value closest to the item's PLISN value and without an NHA-Indicator of "*".

170. The part II is produced automatically when the LSA-080 report is requested and data errors are found.
The report identifies the items having erroneous data, and provides a message describing the type of error
found. The errors that the edit routine will detect are:

a. Error Code 1. If an item is SMR coded, with "Z" or "B" in the fourth position, but parts are
contained below this item with source codes other than K- or XA, then this error is output
(appears on part I with asterisks by both the assembly/part location).

b. Error Code 2. An item does not have an identifiable NHA, e.g., if the indenture structure lists
the item as an "F" and the logical NHA by file sort is a "D", this error is output (part II only).

c. Error Code 3. No IC. This item appears on part II only, when the selection is made by PCCN.
If the selection is by LCN, the item is shown on both parts I and II.

d. Error Code 4. An item whose SMR code is blank or incomplete (without 3rd/4th positions).

e. Error Code 5. If LCN-Code is "CLASSICAL" and duplicate LCNs are encountered, each
duplicate receives this error message. The item(s) will appear on both parts I and II.

f. Error Code 6. The following are allowable SMR recoverability codes based on the repair code:

If position 4 (repair) is: Position 5 (recoverability) must be:

Z Z, A

O (2, 3, 4, 5, 6) Navy only O, F, H, G, D, L, A

F F, H, G, D, L, A

H H, G, D, L, A

G G, D, L, A

D D, L, A

L D, L, A

B Z, A

g. An assembly is SMR coded repairable (e.g., SMR-4 is not Z or B) but has no parts breakout
beneath it.

h. Items having the error codes 2 and 3 with PCCN selection are listed on the LSA-080, part II
only. Other errors are flagged with "**" to the right of the line the error appears in Part I and also
displayed in Part II. The error messages are displayed on part II.

171. The report is sequenced in either ascending assembly reference number and CAGE, or in ascending
assembly PLISN and then components of assembly PLISNs based on the selection option specified.

3B-27
DEF(AUST)5692

LSA-085, TRANSPORTABILITY SUMMARY


172. This report provides information critical to the shipping and transport of major end items of equipment.
It includes environmental and hazardous material information necessary for safe transport of an item by air,
highway, rail, and sea. The format is contained on figure 44. Spacing between rows and columns is not
critical on this report.

173. If the LCN type of subject LCN is functional, NSN and related data, reference number, and CAGE may
not be available. Overflows of Reference Number exceeding 16 positions are printed on the next line
immediately below the first position of the Reference Number. This report is sequenced by ascending LCNs.

LSA-126, HARDWARE GENERATION BREAKDOWN TREE


174. This summary provides a concise summary of information pertaining to a system/equipment
breakdown. Each item is blocked in and indented to the proper level in the hardware family tree and
displayed by line relationship beneath the appropriate assembly in which the item is contained. The format is
contained on figure 45. Spacing between rows and columns is not critical on this report.

LSA-151, PROVISIONING PARTS LIST INDEX (PPLI)


175. This summary provides a cross reference between reference numbers and the applicable PLISN of
the provisioning list as required by MIL-STD-1388-1A. It provides a ready reference of usage and location
within the provisioning list for a given reference number. The report can be generated in reference number,
LCN, or PLISN sequence. Additional data which further describes the item at its usage level(s) are provided
for the user's information (i.e., item name, quantities, SMR, etc.). The format is contained on figure 46.
Spacing between rows and columns is not critical on this report.

LSA-152, PLISN ASSIGNMENT/REASSIGNMENT


176. This summary provides a listing, by reference number, of PLISN, Indenture Code (IC), NHA PLISN,
and PRIOR ITEM PLISN, assigned by the LSAR system based on parameters of the assignment select card.
The summary is automatically produced and will depict the file content before and after the assignments or
reassignments are made (PLISNs are assigned using the EBCDIC collating sequence). As an option, this
report can be used to assign provisioning related control and reference data to the LSAR Parts Master File.
The format is contained on figure 47. Spacing between rows and columns is not critical on this report.

177. It is necessary that the LSAR be properly structured using either a uniform (nonbroken) LCN structure
when applying either a classical or modified classical LCN assignment technique; or an LCN-IC (Table XB)
assignment without missing or unlinked indenture levels, when LCNs are assigned using the sequential
method. Using the LSA-080 report, the analyst can review the file for correct structure, or by using the LSA-
152 report detect error conditions in file structure.

178. The LSA-152 report consists of two parts. Part I will only be output when an error in file structure is
encountered, or when the PLISN assignment (with selected PLISN spacing) exceeds the limit of 9999 for the
proposed assigned PMF candidates. When these occur, the error location in the file is depicted on the report
with a display of the unlinked or remaining file segment. If an error condition does occur, the LSA-152
process will not assign any PLISNs, but will continue processing to determine whether additional error
conditions exist in the file. Validated LSAR systems will be required to have the capability to produce an
error listing for the LSA-152 report. However, the format, messages and explanation of those messages for
the error listing is vendor dependent. Part II of the report reflects the results of the PLISN
assignment/reassignment; only a Part I or a Part II will be produced in a processing cycle. Also, PLISN
assignment shall occur as an exclusive cycle.

179. The report selection for PLISN assignment occurs within a Start and Stop LCN range. There is no
capability to select on a particular ALC. It is possible, however, to surpress PLISN assignment om a lower
indentured LCN (a separately provisioned end item) and its subordinate LCNs by means of assigning a
Suppression Indicator Code (SIC) (Table HG). The SIC is entered against the LCN of the separately
provisioned end item (with a Provisioning System/End Item Identifier of "N" in Table HG) representing the
lowest item to be assigned the PCCN of the system (EIAC). PLISN assignment to the system level PCCN
will continue after processing through all LCNs subordinate to the separately provisioned end item (LCNs
within that "leg" of the breakdown). This requires that the LCN structure and/or LCN-IC relationship for all
components be maintained to the system, not to be separately provisioned end item. An LSA-152 option
can then be used to convert LCN-ICs from the system level IC to the separately provisioned end item's IC. If

3B-28
DEF(AUST)5692

a SIC is contained on a basic LCN having ALCs, each of the ALCs must also contain SICs, the Provisioned
System/End Item Identifier of "N", PCCN of the system, and must match either the basic LCN on LCN-IC.
Conversely, a SIC cannot be contained on an ALC item without it also being contained on the basic.

180. Since there are unlimited "correct" structuring techniques using the ALC, there is no system edit to
detect errors in file structure when the ALC is utilized, other than missing an indenture level when the ALC is
being sequenced to the "basic" LCN structure. ALC assignment errors, therefore, can only be detected by a
manual review of the LSA-152 or LSA-080 reports.

181. There is a wide range of options when using the PLISN assignment routine:

a. NHA PLISNs and/or ICs may be assigned to the PMF, if this option is selected on the 152
report.

(1) If the file is constructed using the classical/modified classical LCN assignment technique,
the IC may be assigned, provided the LCN structure or the LCN positions allocated to
each indenture level is entered on the selection card. This does require that the LCN
structure be consistent throughout the range of LCNs selected. Asterisk ICs may be
assigned to the parts file based on the ICC of "9" representing kit components being
previously assigned (Table HG). An option is also available to assign a constant NHA
PLISN indicator of "N" against each NHA PLISN assigned.

(2) When a sequential LCN assignment method is utilized, the LCN structure field is left
blank on the selection, and the LCN-ICs must be manually entered on Table XB in order
to assign NHA PLISN. The IC (Table HG) should be that of the provisioned end item,
while the LCN-IC should be related to the system level in the LSAR. LCN-ICs must be
assigned in this manner, in order to use the SIC to suppress PLISN assignment when
assigning PLISNs to a higher level end item interfacing with a lower level provisioned end
item. A capability to change IC during the PLISN assignment process of the subordinate
end item should be available to convert the LCN-IC to the provisioned end item IC.

b. When assigning PLISNs for a separately provisioned end item, ICs (Table HG) may be
reassigned for the separately provisioned end item and subordinate LCNs. This is based upon
their relationship to the system (EIAC) level, using the LCN-IC to accomplish the reassignment.
For example, a separately provisioned end item at the "C" indenture to the system (LCN-IC,
Table XB) will be reassigned an IC of "A" and subordinate LCNs will likewise be adjusted from
"D" to "B" IC, "E" to "C" IC, etc. The separately provisioned end item (with a Provisioned
System/End Item Identifier of "E" in Table XB) must have a PCCN (Table XC) different from that
of the system level PCCN in this PLISN assignment run (conversely, the separately provisioned
end item must have a SIC against it, the PCCN of the system, and a Provisioned
System/EndItem Identifier of "N" when assigning PLISNs for the system). LCN-ICs must be on
file for all LCNs of the selected LCN range. Selecting against the LCN structure for PLISN
assignment is not allowed with this option (LCN structure field shall be blank on selection
process).

c. PLISNs may be assigned only to items that qualify by PTD Selection Code for a specified
Provisioning List (PL) or lists (Table HG).

d. PLISNs may be assigned in either topdown (LCN) or Reference Number sequence. When
PLISNs are assigned in Reference Number sequence, the system will lock out the option to
assign NHA PLISNs/ICs.

e. PLISNs may be assigned as either all alphabetic, alphanumeric, numeric, or, first position
alphabetic, then second through fourth position numeric.

f. A starting PLISN value may be specified on the report selection card.

g. PLISN values of "AAAA" through "AAAHZ" may be reserved for the system level and separately
provisioned end items (Model Reserve). If this option is selected, a starting model PLISN value
may be specified (within the given range). If none is selected, the first model PLISN assignment
will be "AAAA".

h. PLISNs may be assigned to overlay old PLISN values established in the file; to overlay PLISNs
and to move the old PLISN value to the Prior Item PLISN field; or to assign PLISNs only to

3B-29
DEF(AUST)5692

items that do not have a PLISN value already established (insert) (Insert/Overlay selection on
report). If the insert option is chosen, PLISNs already assigned to the file must match with the
LCN structure or LCN-ICs of the selected LCN range.

i. It is possible to skip PLISN values between the assigned PLISNs for future use, when the item
is impacted by Design Change Notice or Engineering Change Proposals, or for when the item
having PLISNs assigned is not fully broken down to piece part level. This option cannot be
utilized if the insert option (paragraph h) is in use. PLISN gaps may be as great as 1,121.

j. PLISNs may be assigned to items based upon the Data Status Code (Table HG) contained
against the qualified item. This can be useful when performing incremental provisioning on an
LSAR that is not fully mature.

LSA-154, PROVISIONING PARTS BREAKOUT SUMMARY


182. This report provides a two-part summary of each reference number and can be utilized to assist in
performance of the DOD Replenishment Parts Breakout Program. Included in Part I of the report are critical
pricing and breakout program information. It is sequenced in ascending reference number and CAGE. Part
II contains selected parts application data and is sequenced in ascending LCN. If both parts are selected, a
separate page of the report for each reference number and CAGE is prepared. If only Part I is required,
there is no page break between reference numbers. The report may be selected by contractor technical
information codes, source codes, reference number or report parts. The format is contained on figure 48.
Spacing between rows and columns is not critical on this report.

LSA-155, RECOMMENDED SPARE PARTS LIST FOR SPARES ACQUISITION


INTEGRATED WITH PRODUCTION (SAIP)
183. This summary provides the data required for SAIP list, as specified by MIL-STD-1388-1A. Either the
unit of measure or issue prices may be displayed and are presented by ascending reference number and
CAGE. Items are qualified for the SAIP List based on entry of "Y" in the SAIP code (DED 391). The format
is contained on figure 49. Spacing between rows and columns is not critical on this report.

3B-30
LSAR DATA TABLE TO REPORT MATRIX
3B-31

DEF(AUST)5692
Figure 1: LSAR data table to report matrix
DEF(AUST)5692
3B-32

Figure 1 continued: LSAR data table to report matrix.


3B-33

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-34

Figure 1 continued: LSAR data table to report matrix.


3B-35

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-36

Figure 1 continued: LSAR data table to report matrix.


3B-37

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-38

Figure 1 continued: LSAR data table to report matrix.


3B-39

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-40

Figure 1 continued: LSAR data table to report matrix.


3B-41

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-42

Figure 1 continued: LSAR data table to report matrix.


3B-43

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-44

Figure 1 continued: LSAR data table to report matrix.


3B-45

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-46

Figure 1 continued: LSAR data table to report matrix.


3B-47

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-48

Figure 1 continued: LSAR data table to report matrix.


3B-49

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-50

Figure 1 continued: LSAR data table to report matrix.


3B-51

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-52

Figure 1 continued: LSAR data table to report matrix.


3B-53

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-54

Figure 1 continued: LSAR data table to report matrix.


3B-55

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-56

Figure 1 continued: LSAR data table to report matrix.


3B-57

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-58

Figure 1 continued: LSAR data table to report matrix.


3B-59

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-60

Figure 1 continued: LSAR data table to report matrix.


3B-61

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-62

Figure 1 continued: LSAR data table to report matrix.


3B-63

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-64

Figure 1 continued: LSAR data table to report matrix.


3B-65

Figure 1 continued: LSAR data table to report matrix.

DEF(AUST)5692
DEF(AUST)5692
3B-66

Figure 1 continued: LSAR data table to report matrix.


3B-67

DEF(AUST)5692
Figure 1 continued: LSAR data table to report matrix.
DEF(AUST)5692
3B-68

Figure 1 continued: LSAR data table to report matrix.


LSA-001 SUMMARY
3B-69

DEF(AUST)5692
Figure 2: LSA-001 Summary
LSA-003 SUMMARY

DEF(AUST)5692
3B-70

Figure 3: LSA-003 Summary


LSA-004 SUMMARY
3B-71

DEF(AUST)5692
Figure 4: LSA-004 Summary
DEF(AUST)5692
3B-72

Figure 4: LSA-004 Summary continued


3B-73

DEF(AUST)5692
Figure 4: LSA-004 Summary continued
DEF(AUST)5692
3B-74

Figure 4: LSA-004 Summary continued


3B-75

DEF(AUST)5692
Figure 4: LSA-004 Summary continued
DEF(AUST)5692
3B-76

Figure 4: LSA-004 Summary continued


3B-77

DEF(AUST)5692
Figure 4: LSA-004 Summary continued
DEF(AUST)5692
3B-78

Figure 4: LSA-004 Summary continued


3B-79

DEF(AUST)5692
Figure 4: LSA-004 Summary continued
LSA-005 SUMMARY

DEF(AUST)5692
3B-80

Figure 5: LSA-005 Summary


LSA-006 SUMMARY
3B-81

DEF(AUST)5692
Figure 6: LSA-006 Summary
LSA-007 SUMMARY

DEF(AUST)5692
3B-82

Figure 7: LSA-007 Summary


LSA-008 SUMMARY
3B-83

DEF(AUST)5692
Figure 8: LSA-008 Summary
LSA-009 SUMMARY

DEF(AUST)5692
3B-84

Figure 9: LSA-009 Summary


LSA-010 SUMMARY
3B-85

DEF(AUST)5692
Figure 10: LSA-010 Summary
LSA-011 SUMMARY

DEF(AUST)5692
3B-86

Figure 11: LSA-011 Summary


LSA-012 SUMMARY
3B-87

DEF(AUST)5692
Figure 12: LSA-012 Summary
DEF(AUST)5692
3B-88

Figure 12: LSA-012 Summary continued


3B-89

DEF(AUST)5692
Figure 12: LSA-012 Summary continued
LSA-013 SUMMARY

DEF(AUST)5692
3B-90

Figure 13: LSA-013 Summary


LSA-014 SUMMARY
3B-91

DEF(AUST)5692
Figure 14: LSA-014 Summary
LSA-016 SUMMARY

DEF(AUST)5692
3B-92

Figure 15: LSA-016 Summary


3B-93

DEF(AUST)5692
Figure 15: LSA-016 Summary continued
DEF(AUST)5692
3B-94

Figure 15: LSA-016 Summary continued


LSA-018 SUMMARY
3B-95

DEF(AUST)5692
Figure 16: LSA-018 Summary
DEF(AUST)5692
3B-96

Figure 16: LSA-018 Summary continued


LSA-019 SUMMARY
3B-97

DEF(AUST)5692
Figure 17: LSA-019 Summary
LSA-023 SUMMARY

DEF(AUST)5692
3B-98

Figure 18: LSA-023 Summary


3B-99

DEF(AUST)5692
Figure 18: LSA-023 Summary continued
DEF(AUST)5692
3B-100

Figure 18: LSA-023 Summary continued


3B-101

DEF(AUST)5692
Figure 18: LSA-023 Summary continued
DEF(AUST)5692
3B-102

Figure 18: LSA-023 Summary continued


LSA-024 SUMMARY
3B-103

DEF(AUST)5692
Figure 19: LSA-024 Summary
DEF(AUST)5692
3B-104

Figure 19: LSA-024 Summary continued


3B-105

DEF(AUST)5692
Figure 19: LSA-024 Summary continued
DEF(AUST)5692
3B-106

Figure 19: LSA-024 Summary continued


LSA-025 SUMMARY
3B-107

DEF(AUST)5692
Figure 20: LSA-025 Summary
LSA-026 SUMMARY

DEF(AUST)5692
3B-108

Figure 21: LSA-026 Summary


LSA-027 SUMMARY
3B-109

DEF(AUST)5692
Figure 22: LSA-027 Summary
LSA-030 SUMMARY

DEF(AUST)5692
3B-110

Figure 23: LSA-030 Summary


3B-111

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
DEF(AUST)5692
3B-112

Figure 23: LSA-030 Summary continued


3B-113

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
DEF(AUST)5692
3B-114

Figure 23: LSA-030 Summary continued


3B-115

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
DEF(AUST)5692
3B-116

Figure 23: LSA-030 Summary continued


3B-117

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
DEF(AUST)5692
3B-118

Figure 23: LSA-030 Summary continued


3B-119

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
DEF(AUST)5692
3B-120

Figure 23: LSA-030 Summary continued


3B-121

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
DEF(AUST)5692
3B-122

Figure 23: LSA-030 Summary continued


3B-123

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
DEF(AUST)5692
3B-124

Figure 23: LSA-030 Summary continued


3B-125

DEF(AUST)5692
Figure 23: LSA-030 Summary continued
LSA-032 SUMMARY

DEF(AUST)5692
3B-126

Figure 24: LSA-032 Summary


3B-127

DEF(AUST)5692
Figure 24: LSA-032 Summary continued
LSA-033 SUMMARY

DEF(AUST)5692
3B-128

Figure 25: LSA-033 Summary


LSA-036 SUMMARY
3B-129

DEF(AUST)5692
Figure 26: LSA-036 Summary
DEF(AUST)5692
3B-130

Figure 26: LSA-036 Summary continued


3B-131

DEF(AUST)5692
Figure 26: LSA-036 Summary continued
DEF(AUST)5692
3B-132

Figure 26: LSA-036 Summary continued


3B-133

DEF(AUST)5692
Figure 26: LSA-036 Summary continued
DEF(AUST)5692
3B-134

Figure 26: LSA-036 Summary continued


3B-135

DEF(AUST)5692
Figure 26: LSA-036 Summary continued
DEF(AUST)5692
3B-136

Figure 26: LSA-036 Summary continued


3B-137

DEF(AUST)5692
Figure 26: LSA-036 Summary continued
DEF(AUST)5692
3B-138

Figure 26: LSA-036 Summary continued


3B-139

DEF(AUST)5692
Figure 26: LSA-036 Summary continued
LSA-037 SUMMARY

DEF(AUST)5692
3B-140

Figure 27: LSA-037 Summary


LSA-039 SUMMARY
3B-141

DEF(AUST)5692
Figure 28: LSA-039 Summary
LSA-040 SUMMARY

DEF(AUST)5692
3B-142

Figure 29: LSA-040 Summary


3B-143

DEF(AUST)5692
Figure 29: LSA-040 Summary continued
DEF(AUST)5692
3B-144

Figure 29: LSA-040 Summary continued


3B-145

DEF(AUST)5692
Figure 29: LSA-040 Summary continued
DEF(AUST)5692
3B-146

Figure 29: LSA-040 Summary continued


3B-147

DEF(AUST)5692
Figure 29: LSA-040 Summary continued
DEF(AUST)5692
3B-148

Figure 29: LSA-040 Summary continued


LSA-046 SUMMARY
3B-149

DEF(AUST)5692
Figure 30: LSA-046 Summary
LSA-050 SUMMARY

DEF(AUST)5692
3B-150

Figure 31: LSA-050 Summary


3B-151

DEF(AUST)5692
Figure 31: LSA-050 Summary continued
DEF(AUST)5692
3B-152

Figure 31: LSA-050 Summary continued


3B-153

DEF(AUST)5692
Figure 31: LSA-050 Summary continued
LSA-056 SUMMARY

DEF(AUST)5692
3B-154

Figure 32: LSA-056 Summary


3B-155

DEF(AUST)5692
Figure 32: LSA-056 Summary continued
DEF(AUST)5692
3B-156

Figure 32: LSA-056 Summary continued


3B-157

DEF(AUST)5692
Figure 32: LSA-056 Summary continued
DEF(AUST)5692
3B-158

Figure 32: LSA-056 Summary continued


3B-159

DEF(AUST)5692
Figure 32: LSA-056 Summary continued
LSA-058 SUMMARY

DEF(AUST)5692
3B-160

Figure 33: LSA-058 Summary


3B-161

DEF(AUST)5692
Figure 33: LSA-058 Summary continued
LSA-065 SUMMARY

DEF(AUST)5692
3B-162

Figure 34: LSA-065 Summary


LSA-070 SUMMARY
3B-163

DEF(AUST)5692
Figure 35: LSA-070 Summary
DEF(AUST)5692
3B-164

Figure 35: LSA-070 Summary continued


3B-165

DEF(AUST)5692
Figure 35: LSA-070 Summary continued
DEF(AUST)5692
3B-166

Figure 35: LSA-070 Summary continued


3B-167

DEF(AUST)5692
Figure 35: LSA-070 Summary continued
DEF(AUST)5692
3B-168

Figure 35: LSA-070 Summary continued


3B-169

DEF(AUST)5692
Figure 35: LSA-070 Summary continued
DEF(AUST)5692
3B-170

Figure 35: LSA-070 Summary continued


3B-171

DEF(AUST)5692
Figure 35: LSA-070 Summary continued
DEF(AUST)5692
3B-172

Figure 35: LSA-070 Summary continued


3B-173

DEF(AUST)5692
Figure 35: LSA-070 Summary continued
DEF(AUST)5692
3B-174

Figure 35: LSA-070 Summary continued


LSA-071 SUMMARY
3B-175

DEF(AUST)5692
Figure 36: LSA-071 Summary
DEF(AUST)5692
3B-176

Figure 36: LSA-071 Summary continued


LSA-072 SUMMARY
3B-177

DEF(AUST)5692
Figure 37: LSA-072 Summary
DEF(AUST)5692
3B-178

Figure 37: LSA-072 Summary continued


LSA-074 SUMMARY
3B-179

DEF(AUST)5692
Figure 38: LSA-074 Summary
DEF(AUST)5692
3B-180

Figure 38: LSA-074 Summary continued


3B-181

DEF(AUST)5692
Figure 38: LSA-074 Summary continued
DEF(AUST)5692
3B-182

Figure 38: LSA-074 Summary continued


LSA-075 SUMMARY
3B-183

DEF(AUST)5692
Figure 39: LSA-075 Summary
DEF(AUST)5692
3B-184

Figure 39: LSA-075 Summary continued


LSA-076 SUMMARY
3B-185

DEF(AUST)5692
Figure 40: LSA-076 Summary
DEF(AUST)5692
3B-186

Figure 40: LSA-076 Summary continued


3B-187

DEF(AUST)5692
Figure 40: LSA-076 Summary continued
DEF(AUST)5692
3B-188

Figure 40: LSA-076 Summary continued


LSA-077 SUMMARY
3B-189

DEF(AUST)5692
Figure 41: LSA-077 Summary
DEF(AUST)5692
3B-190

Figure 41: LSA-077 Summary continued


3B-191

DEF(AUST)5692
Figure 41: LSA-077 Summary continued
LSA-078 SUMMARY

DEF(AUST)5692
3B-192

Figure 42: LSA-078 Summary


LSA-080 SUMMARY
3B-193

DEF(AUST)5692
Figure 43: LSA-080 Summary
LSA-085 SUMMARY

DEF(AUST)5692
3B-194

Figure 44: LSA-085 Summary


3B-195

DEF(AUST)5692
Figure 44: LSA-085 Summary continued
DEF(AUST)5692
3B-196

Figure 44: LSA-085 Summary continued


LSA-126 SUMMARY
3B-197

DEF(AUST)5692
Figure 45: LSA-126 Summary
LSA-151 SUMMARY

DEF(AUST)5692
3B-198

Figure 46: LSA-151 Summary


LSA-152 SUMMARY
3B-199

DEF(AUST)5692
Figure 47: LSA-152 Summary
LSA-154 SUMMARY

DEF(AUST)5692
3B-200

Figure 48: LSA-154 Summary


LSA-155 SUMMARY
3B-201

DEF(AUST)5692
Figure 49: LSA-155 Summary
DEF(AUST)5692
BLANK PAGE
3B-202
DEF(AUST)5692 ANNEX C TO
CHAPTER 3

GUIDANCE FOR THE ASSIGNMENT OF THE LCN, ALC, AND UOC


INTRODUCTION
Purpose

1. This Annex provides guidance for the assignment of LCNs, ALCs, LCN-Types, and UOCs; their use;
and, their relationship to one another.

Traditional LCN Assignments

2. Traditionally, the LCN was developed using the physical hardware configuration (or engineering
drawings), for LCN assignment. Using this approach, the LCNs assigned, directly tracked with provisioning
documentation requirements, and enabled easy conversion to provisioning data keys (Provisioning List Item
Sequence Numbers (PLISN)). Any product documentation, such as the Maintenance Allocation Chart,
Maintenance Plans, or Repair Parts and Special Tools List requiring a Functional Group Code (FGC) or
Work Unit Code (WUC) sequencing was selected by LCN and then resorted by the data element WUC/TM-
FGC.

Functional and Physical LCN Assignments: Perspective

3. Under the Reliability and Maintainability areas, a physical hardware breakdown may create problems
in "rolling up" failure rates, reliability times, and maintainability frequencies to the appropriate higher item.
For example, if an antenna connected to a wing-tip fails, the failure should be rolled to the communications
system, and not to the wing structure on which it is physically attached.

4. The WUC/TM-FGC cannot be used for functional documentation since this element is used for product
development and may contain a consolidated code for "like" items, which will create problems for
reliability/maintainability summations and calculations. In addition, a WUC/TM-FGC cannot be documented
until a physical (or traditional) LCN has already been assigned. The functional LCN provides the flexibility
necessary to correct these situations. In cases where the functional and physical breakdowns are identical,
separate structures will not be required.

5. When there is a requirement for both physical and functional breakdowns, a cross-reference table
mapping the functional and physical LCNs will be documented to "convert" reliability/maintainability numbers
to provisioning technical factors. In an automated data processing system, the physical LCN structure
should take precedence for data storage, when both a physical and functional LCN exist for the same item.
Under no circumstances should it be necessary to document LSAR data under both physical and functional
LCNs for the same item under analysis. By creating the physical/functional mapping, any data documented
under a functional LCN will be converted from a functional to a physical key. It is important to recognise that
the two structures are completely independent, and that a "mixing" of structures (part physical/part
functional) for a system/end item is not permitted. Also recognise the importance of proper mapping of the
functional and physical LCNs. To document functional/physical LCN assignment requires the LCN-Type
data element. This element is a key and is required where all LCN oriented data resides. The LCN-Type is a
one-position code of either "F", Functional; or "P", Physical.

LCN ASSIGNMENT

6. The LCN may represent either a functional or hardware generation breakdown/disassembly sequence
of system/equipment hardware including support equipment, training equipment, and installation
(connecting) hardware. As such, the LCN is a key field utilised to input data into the LSAR data system and
to extract reports from the data system. Normally, development of the LCN structure and assignment of
LCNs through the subsystem level should be accomplished prior to completion of the first LSAR data tables.

7. Extreme care should be exercised in developing the structure, so that the least number of characters
is used for each indenture level. This can be accomplished by identifying the maximum number of
parts/assemblies, which will be assigned a unique LCN at each indenture level. If the maximum number of
items at a given indenture level is less than or equal to 36, then 1 alphanumeric character would suffice. If
the maximum number of items is greater than 36 but less than or equal to 1296, then 2 alphanumeric
characters would suffice and so on. No more than one position of the LCN should be used to identify the
system. It is useful to develop an LCN structure for the entire system/equipment hardware. Care should be
exercised in assigning the LCNs, since the order in which they are assigned will affect the order of Failure
DEF(AUST)5692

Modes, Effects and Criticality Analysis (FMECA) data and task analysis information, and may affect the order
in which it will be used on a repair parts lists and assignment of PLISNs. For example, if it is a requirement
for attaching hardware to appear on a repair parts list prior to the assembly, these items would have to be
assigned LCNs which are less in value than the one assigned to the assembly. In assigning the LCN early in
the design of an end item, it is also advantageous to skip one or two LCNs, so that an additional item can be
inserted later on due to design changes. This advance planning avoids the possibility of having to re-
sequence at a later point in the program. The above guidance should be considered prior to assigning the
LCNs. In addition, the method for assigning LCNs is provided below.

Classical LCN Assignment

8. This method dictates assignment of a unique LCN to every application of a part numbered item in the
system including piece parts. This method ensures proper identification of an item to its Next Higher
Assembly (NHA) and ensures proper roll-up/summarisation of data for all LSA Record (LSAR) reports.
Figure 1 is an example of the classical LCN assignment method. From a provisioning standpoint, use of the
classical assignment method would allow the automatic assignment of PLISN, NHA PLISN, SAME AS
PLISN, and Indenture Code.

Figure 1 Classical LCN Assignment

Modified Classical Assignment Method

9. This method is a variation of the classical assignment method, which permits piece parts to be
assigned the same LCN at the indenture level below the component/assembly of which they are a part. In

3C-2
DEF(AUST)5692

addition, attaching hardware may be assigned the same LCN at the same indenture level at which the
assembly is located. The assembly to which the attaching hardware is required is provided a separate LCN.
Figure 2 shows an example of the modified classical method. The items with an asterisk have been
assigned the same LCN. Application of this method could economise the number of LCNs required at the
lower indenture levels. Use of this method ensures proper roll-up/summarisation of data for all LSAR
reports. From a provisioning standpoint when hardware breakdown approach is used for the LCN, this
method allows the automatic assignment of all PLISNs and the indenture code.

Figure 2 Modified Classical LCN Assignment

Candidate Items

10. An LCN should, as a minimum, be assigned to all items of the system/end item or support system that
are candidates for analysis, ie., candidate items. LCNs may also be assigned to items of the system/end
item that are not to be analysed but are included in the breakdown structure, for example attaching
hardware, nuts, bolts, etc.

11. A candidate item can be any item of the system or support system to be delivered that has potential
requirements for operation, maintenance or other form of logistic support undertaken by Service operating or
support units. Items of support or training equipment that have logistic support requirements may qualify as
candidate items. Any item to be maintained In-service is a candidate item including those requiring
corrective or preventative maintenance or inspections, as all these actions require logistic resources. The
level of the physical breakdown to which candidate items are established is determined via the LORA
process and usually extends to one level below the level of the item that will be maintained/supported In-
service. This is due to the top down analysis flow of LORA (unless decided by non-economic LORA or
predetermined maintenance policies).

3C-3
DEF(AUST)5692

12. The Requiring Authority may determine that for existing items which the Requiring Authority already
has sufficient information, and there is no need for further analysis of the item in the new system/equipment,
that the item not be a candidate item for analysis. In this case the logistic resource requirements may be
summarised in the LSAR to facilitate the roll-up of all system support resource requirements.

13. Once entered into the LSAR, candidate items of the system/equipment are identified by the requirement
to record RAM data against the item, by the RAM indicator code in Table XB. Hardware items, such as
fasteners, brackets, etc, that are not necessarily candidate items can still be listed in the LSAR for
provisioning purposes. They may be assigned an LCN, or alternatively, will be identified by their part
numbers grouped against an LCN of "attaching hardware" or an "assembly" depending on the needs of the
project.

ALTERNATE LCN CODE (ALC)

14. The ALC (codes 00 through 99 and space) provides the capability to document alternate design
concepts or like items for different models using identical LCNs at the same system breakdown level. As
such, ALC is a key data element and a value of 00 is considered just as significant as a value of 01, 10, or
23. In fact, all LCNs that have a corresponding ALC with a value of 00 represent the "basic system"
hardware. The ALC is LCN oriented and is used to aid in the documentation of the following:

a. Alternate items with different reference numbers (eg., diesel engine versus gas engine), one of
which will be selected for production.

b. Different reference numbered items which are used in the same functional and physical location
(ie., same LCN) in the hardware breakdown, and the usage of either item results in a different
configuration/model designation (ie., different UOCs).

15. The use of ALC for a single configuration/model is discussed in the paragraph titled "ALC usage for a
single configuration/model", while ALC usage for multiple configurations/models is discussed in the
paragraph titled "Usable on Code".

ALC Usage for a Single Configuration/Model

16. A system/end item, which has a single configuration/model designation, will have only one assigned
UOC. When a system/end item has a single UOC, then the ALC can be used to capture analysis data for
alternative designs or maintenance concepts. To properly input LSAR data and establish a traceable LCN
breakdown structure, the following rules should be adhered to:

a. Rule 1. The "basic system" hardware breakdown must be input using ALC values of 00. This is
necessary since the selection process will always default to the "basic system" data, if
alternative data has not been entered.

b. Rule 2. Alternative designs would be broken down completely in terms of LCN and associated
data.

c. Rule 3. To the maximum extent possible, the ALC assigned should be the same value
throughout the alternative design/maintenance concept.

17. Following these rules allows for an orderly build-up of LSAR data and avoids confusion concerning
which items may be common to two or more alternatives and provides for easier retrieval of LSAR reports.

18. Figure 3 is an example of a single configuration/model end item with a UOC of "ABC". The example
also represents how the ALC can be used for alternative hardware design concepts. Three different fuel
pumps are being considered for use on the gas engine, as well as an alternative diesel engine. All "basic"
hardware items have an ALC of 00, while two additional fuel pumps and the entire diesel engine breakdown
have different ALCs. This is in accordance with the first rule stated above.

19. Rule 2 is also followed for the Figure 3 breakdown of the diesel engine because the identical electrical
system was repeated from the gas engine. Rule 3 is followed in assignment of ALCs for the diesel engine.

3C-4
DEF(AUST)5692

Figure 3 Alternate LCN Code Usage

ALC Usage for LSAR Reports

20. For most report selections, the UOC is always the first criteria that must be met for data selection and
LCN is the second criteria. ALC becomes the third select criteria, if the user specifies a specific ALC value
on the report request. As already discussed, an ALC of 00 on the report submittal will result in choosing
"basic system" LCN data (i.e., records with 00 ALCs). If an ALC is requested with a specific numeric value,
only items with a matching ALC will be chosen.

Lower-tiered LCN/ALC Selections

21. In addition to the basic report request, different LCN and ALC combinations at a lower indenture level
from the basic report selection may be chosen to specify the alternative design desired by identifying these
3C-5
DEF(AUST)5692

LCNs and ALCs. This is necessary when rule 3, discussed in the paragraph titled "ALC usage for a single
configuration/model", cannot be strictly adhered to and designation of the ALC on the basic report request
will not result in a complete substitution of the alternative design. This situation will occur when alternative
designs are being considered within the hardware breakdown of another alternative design. The example on
Figure 2 displays this situation; alternative fuel pumps are being considered within the gas engine and two
alternative engines are being considered. Thus, in order to obtain the "basic system" (ie., with gas engine,
but with fuel pump RN5), a lower-tiered LCN/ALC request selection must be input with an LCN of "A203" and
an ALC of "03". The basic report request would have an ALC value of 00. In order to produce a report for
the "basic system" with the diesel engine substituted, the following selection request would be required:

a. A basic selection request with an LCN of "A", UOC of "ABC", and an ALC of "00". This
produces a report of the "basic" truck.

b. A lower-tiered LCN/ALC selection request with an LCN of "A2" and an ALC value of "01". This
information would modify the basic selection request to choose the diesel engine, in lieu of the
gas engine.

22. The lower-tiered LCN/ALC selection request allows the user to create many different variations of a
system/end item via the LSAR reports. While use of the ALC for alternative designs does not reduce the
amount of data required (ie., Rule 2 of ALC usage for a single configuration/model), it does provide for easier
data storage and report generation.

LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER TYPE (LCN-TYPE)

23. The LCN-TYPE is a one-position code used to indicate whether the associated LCN represents a
functional versus physical or hardware generation breakdown structure. Generally, top-down FMECA
documentation and selective task analysis, eg., fault locations, "track" to a functional breakdown. Other
documentation requirements, eg., provisioning, track to a system/equipment hardware breakdown. An
example of a functional and physical breakdown for the same system/equipment is shown on Figure 4.

Figure 4 Functional versus Physical LCN

USABLE ON CODE (UOC)

24. The UOC is used to identify the model/configuration relationship of each LCN comprising a
system/equipment and to control these relationships for LSAR report generation. The UOC is a critical data
element and should therefore be used when establishing an LSAR. This requirement holds even if only one
configuration/model of a system/equipment is being documented. In accordance with table XC, contained in
Annex A, each configuration/model is assigned a unique UOC at the system/end item level LCN. Each
individual assembly/component/piece part is also "linked" to the assigned UOC of the model of which it is
applicable through tables XF and HO. When an assembly/component/piece part is applicable to more than
one configuration/model, then multiple UOCs are "linked" to the component for a single LCN and ALC via
tables XF and HO. This eliminates the requirement of duplicating analysis and related data, merely because
an item has application to multiple configurations/models. It should be stressed that if an item's usage for a
given configuration model differs from another configuration/model in terms of quantity, Source,
3C-6
DEF(AUST)5692

Maintenance, Recoverability (SMR) coding or analysis data, then multiple UOCs should not be used for a
single LCN. This situation dictates input of additional relational table rows using the ALC to indicate different
data for the same LCN and a different UOC.

ALC and UOC Relationship

In order to document multiple configurations/models in the LSAR, the ALC plays an important role. As
already stated, for items that are common to all configurations/models, only one LCN entry is required for the
multiple UOCs. In addition, since such an item is considered part of the "basic system", its ALC would be 00.
For those items that bring about a configuration/model change, the ALC is used in a manner similar to that
discussed in the ALC section of this Annex. Figure 5 is an example of multiple UOCs for a given system/end
item and the usage of ALC in conjunction with multiple model items. In the example, the basic model truck
has a UOC of "ABC", while the new model truck has a UOC of "ABD". The reason for the additional model is
the use of a diesel engine, instead of the gas engine. Since both types of engines physically and functionally
appear in the same location of the truck breakdown, their LCNs are the same. The ALC of "01" has been
used to differentiate new reference numbered items from the basic items.

Figure 5 Usable On Code and Alternate LCN Code

UOC and ALC Usage for LSAR Reports

25. The ALC section of this Annex states that most selection requests for the LSAR reports must have, as
a minimum, LCN and UOC on the request. The reason for this is that UOC is the overall report generation
key that must match to a record before LCN and ALC are considered. In the case of a single
configuration/model, its importance is reduced since every item has the same UOC value. For multiple
configurations/models, the identification of the desired UOC on the selection request will result in building the
desired output LSAR reports without lower-tiered LCN/ALC selections and without knowing which ALC
values were used for that UOC's LCNs. Using the example on Figure 5, a report selection request with an
LCN of "A", an ALC of 00, and a UOC of "ABC" will result in the basic model breakdown being output. This
means that the fuel pump, with reference number RN7, would be chosen over the other two fuel pumps. If
the report selection request had been LCN of "A", a blank ALC, and UOC of "ABC", all items containing the
UOC "ABC" would be selected. Therefore, all three fuel pumps under the basic model would be output. If
the second model of the truck with UOC of "ABD" is to be selected, a report selection request with an LCN of
"A" and a UOC of "ABD" is all that is needed. This would result in all LCN items with UOC values of "ABC"
and "ABD", as well as all LCN items with UOC of "ABD" only being selected. In effect, the basic model with
the diesel engine substituted would be output for the desired reports.

3C-7
DEF(AUST)5692

SERIAL NUMBER CONTROL AS AN ALTERNATIVE FOR CONFIGURATION


MANAGEMENT

26. For complex or major weapon systems in various production stages, the use of serial numbers may be
used for greater control of end item configuration. By documenting Serial Number applicability in tables XD,
and assembly/component/piece part relationships to the serial numbered end item(s) using tables XE and
HN, configuration control may be maintained to the individual end item. This is beneficial when production
changes may occur to individual end items, which may not warrant an official configuration/model
designation change. The LSAR summaries do not use serial number as a selection criteria, but ad hoc
query capability would allow analysis/summary report generation based on serial number qualification.

SUMMARY

27. The assignment of LCNs, UOCs, and ALCs must be approached carefully and logically in order to
ensure that the LSAR reports represent the hardware logistics data desired. In general, a system/end item
development effort normally begins with a single model designation (i.e., one UOC). During this phase of
development, the ALC is needed only when alternative designs are being considered. As the hardware
design stabilises, the "undesirable" alternatives are deleted from the LSAR database in favour of "basic
system" configuration.

28. Once a system/end item enters the production phase, engineering change proposals because of
producibility limitations, design deficiencies, or changes in operational requirements, can dictate a new
configuration model. When this occurs, the ALC once again would be used to aid in the documentation
effort. This orderly application of the ALC to alternative design/maintenance concepts or multiple
configuration/models can preclude user confusion. It is possible that some system/end item developments
will initially be faced with documenting multiple configurations/models and alternative design/maintenance
concepts, simultaneously. When this occurs an orderly and logical approach to UOC and ALC, following the
guidance of this Annex, will result in a properly documented system/end item.

3C-8
DEF(AUST)5692 ANNEX D TO
CHAPTER 3

APPLICATION AND TAILORING GUIDANCE FOR THE LSAR


INTRODUCTION

Purpose

1. The results of LSA, and the related analytical processes that LSA brings together, are recorded in the
LSAR. Thus the LSAR achieves the LSA goal, to implement a single integrated database for collection,
storage and use of logistics data. As a common data source, the LSAR provides an integrated reference to
information needed for the development and on-going optimisation of the Supportability solution. The LSAR
provides a structured, standardised, yet flexible approach to the documentation and use of the data required
to effectively accomplish many contractually invoked LSA Activities and produce consistent logistics data
products.

2. To be effective LSA documentation must be initiated early in the Acquisition Phase, must be updated
to reflect changes in the hardware design and support concept, and must be tailored to be commensurate
with individual program requirements, constraints, and characteristics. The LSAR data is generated as a
result of the performance of LSA and related analysis activities. Tailoring and focussing both the LSA
Activities to be performed, and the resultant LSAR data produced as a part of LSA documentation, is
mandatory. Limitations on system development funding make it imperative that LSA be applied judiciously to
improve hardware design and support concepts, not merely to collect LSAR data.

3. This Annex provides guidance for appropriate application of the LSAR during each phase of the
materiel life cycle and the procedures for tailoring of the LSAR data records, elements, and standard reports
to satisfy program requirements at minimum cost. This Annex does not contain any requirements and is not
to be implemented in contractual documents. The user of this Annex may be a Defence Project Team or
Support Activity, prime contractor, or subcontractor wishing to impose or implement LSAR requirements.

How to use this Annex

4. Tailoring of the LSAR requirements to suit the needs of an individual program is a multi-facetted task.
Some of the considerations common to most LSAR tailoring tasks are:

a. The life cycle phase or stage of a project and the data available and appropriate for the system
development and analysis conducted in that phase.

b. The appropriate level of indenture (system/hardware breakdown) to which analysis will be


conducted and data required; which is also suited to the phase of the project.

c. The LSA Activities to be performed and related analysis that will provide or be based on LSA
data.

d. The depth and areas of analysis appropriate to different parts of the system/equipment. For
example, requirements can differ for mechanical, structural, and electronic systems or hardware
versus software.

e. The LSA data and logistics data products to be produced.

f. The use of existing data, incorporation of GFI and the combination of data for both newly
developed and off the shelf items.

5. Tailoring of the LSAR requirement begins with the identification of the life cycle phase of the
system/equipment acquisition effort. The section "LSAR Application and Use by Life Cycle Phase" in this
Annex addresses the applicability of the LSAR for each of the life cycle phases.

6. Once the life cycle phase has been established, tailoring of the LSAR requirement can be performed.
The section titled "Tailoring LSAR Requirements" provides a stepwise procedure for tailoring the LSAR,
based upon LSA Activities, related engineering and Integrated Logistic Support (ILS) element analysis efforts
which result in LSAR data, and deliverable logistic products specified by data item descriptions (DID) to be
included in the contract. Another factor in the tailoring process is the depth of analysis required, Table 1
depicts general applicability of the LSAR data tables to the system/hardware breakdown.
DEF(AUST)5692

7. The result of this tailoring process is a completed or series of completed Data Selection Sheets,
identifying the LSAR data table and data element requirements for the specific phase of the acquisition
effort.

8. Guidance for determining LSAR completion schedules is contained in the section titled "Scheduling of
the LSAR Data".

9. The final step in tailoring the LSAR effort involves contractual delivery of the LSAR data itself. The
section titled "Alternatives for LSAR Delivery" discusses alternatives for delivery of the LSAR data.

LSAR APPLICATION AND USE BY LIFE CYCLE PHASE

LSA Process

10. The LSA process is applicable to all phases of the life cycle and all types of acquisition programs.
Tailoring of the LSA Activities, and consequent tailoring of the LSAR documentation requirements, are
dependent upon the life cycle phase, type of acquisition, and degree of program control desired.

11. In relation to the Concept and Acquisition Phases, the LSA process can be divided into two basic
categories:

a. LSA encompassing requirements analysis, research and development, conceptual studies, and
development of conceptual designs; and,

b. LSA for design development of the Mission System, Support Systems and logistic data
products.

12. Both categories of LSA respectively address the primary objectives of:

a. Influence the design of Mission Systems and Support Systems to reduce operating and support
costs and increase preparedness.

b. Identification of logistic resource requirements progressively and concurrently with the design.

13. During the In-service phase, LSA supported by the LSAR, continues the objectives of improving
preparedness and reducing the cost of ownership. LSA is used to:

a. monitor and refine the support systems for further reductions in operating and support costs or
improved preparedness,

b. enable cost effective responses in logistic support to match changed requirements; and

c. prepare logistic support required for modifications.

14. LSA, again supported by the LSAR, prepares for the cost-effective disposal of Mission Systems and
their related Support Systems.

15. Application of the LSAR, supporting the LSA process, is discussed in accordance with each life cycle
phase.

a. Concept Phase,

b. Acquisition Phase,

c. In-Service Phase, and

d. Disposal.

CONCEPT PHASE

16. LSA is initiated in the earliest studies and design efforts and continued during all phases of the
materiel life cycle. Initially, the LSA is directed toward establishing Supportability related design factors and
constraints, which must be used in developing design guidelines and trade study plans.

3D-2
DEF(AUST)5692

17. LSA identifies objectives for Reliability, Availability, Maintainability (RAM) and LCC; potential logistic
support problems, constraints and risks; targets for improvement; and enables the projection of gross
logistics resource requirements and costs. The results of conceptual studies are often qualitative, however
the quantified objectives for RAM and the operational and support requirements can be recorded in the
LSAR although that is not mandatory during the Concept phase.

18. Recording this information in the LSAR during Concept offers some benefits. It initiates the use of the
LSAR as a central data source for trade studies and evaluations, identifies different usage rates, and begins
the population of the LSAR with GFI to be provided by the Requiring Authority. The Concept phase LSA
Activities would normally only identify data for the A Table data elements shown in Table 2 of this Annex,
with additional or less information depending on the project. The A Tables would only be populated with
system level data and principle sub-systems that have a significantly different operating requirement or
measurement base, eg. landings instead of flying hours, or rounds fired instead of operating hours.

ACQUISITION PHASE

Acquisition Phase Pre-Contract

19. LSA early in the Acquisition phase continues the Requirements Identification and Functional Analysis
process started during Concept. LSA is directed toward refining objectives for RAM and LCC, and the
related projections of logistics resource requirements and costs associated with different concepts and
potential Supportability solutions. LSA also seeks to identify and define potential logistics problems and
options for improvement, and the evaluation of constraints and risks.

20. During this effort, the LSA Program continually interfaces with System Engineering (SE), RAM and
other TLS Programs through historical data reviews, tradeoff analyses, use studies, design projections, and
other LSA Activities to arrive at the most cost-effective materiel design concept(s) and plan(s) for further
examination, study and development.

21. The LSA Activity for Task Identification, applied at a system/sub-system level, produces a task
inventory that can be used by all engineering specialties. The task inventory enables the identification of
potential system level support resources to be mapped against functional system and sub-system level
tasks, for example the personnel skills, facilities and major S&TE items. This supports the LSA effort of
evaluating alternate system and support concepts and establishing realistic Supportability objectives. The
results of the LSA effort are embodied in the program documents and supplementary technical reports. The
limited volume of LSAR data is usually produced by the Requiring Authority to define and document system
level requirements. Table 2 suggests the LSAR data that might be generated at this time. However, tailoring
these LSAR data requirements is mandatory, and not all data elements may be required to support LSA
objectives. The tenderers would need to perform a similar level of analysis and data documentation for their
offered solution, although the data may already exist in an LSAR or other data source.

Acquisition Phase Post-Contract to Detailed/Critical Design Review

22. After contract and in the lead up to DDR/CDR, LSA Activities are mostly applied by the Performing
Activity to further the Requirements Identification and Functional Analysis process to the levels of indenture
necessary to support design development activities for both the Mission System and the Support System.
Requiring Authority application of LSA includes reviews of the functional allocation of Supportability
requirements to the proposed Mission System design and Support System.

23. Essential to the conduct of the DDR/CDR is the R&M, FMECA, RCM and initial Task Identification and
Analysis Activities that are necessary to determine if the proposed system is supportable and likely to meet
the program objectives for preparedness and LCC. In coordination with the Requiring Authority RAM
program, R&M figures allocated to the Mission System and Support System items, FMECA and RCM data
are reviewed. This data is contained in the B Tables of the LSAR. R&M data along with the identification of
maintenance tasks and their gross resource requirements, recorded in the C Tables, enables estimates of
the size of the logistic resource package, including maintenance personnel, facilities and S&TE utilisation.
Again, in coordination with RAM and LCC programs, projections can be made to determine if the Mission
System is likely to achieve preparedness, cost and Supportability objectives or if changes to design are
required to meet these objectives. Accordingly the LSAR data assists in determining whether functional
analysis has proceeded in line with support concepts or if deviations have occurred.

24. This stage is not only busy applying Functional LSA to establish Mission System and Support System
designs, but with the analysis backed development of the task inventory, this stage truly initiates Physical
LSA and the synthesis of the logistic resource package. A Data Selection Sheet may be specifically

3D-3
DEF(AUST)5692

prepared and placed as a contract DID for LSAR data to be delivered in this period in support of these LSA
Activities.

Acquisition Phase Post-Detailed/Critical Design Review

25. Following DDR/CDR, the design of the Mission System is placed under configuration control and few
changes should occur. The support system design continues into more detail with the identification of
physical resources, thus the Functional LSA process comes to a close. The Physical LSA process involving
the full task analysis, optimisation and the preparation of logistic data products becomes fully established.

26. During this stage, the LSAR effort is a more comprehensive continuation of the effort initiated prior to
DDR/CDR. Analysis results are populated in the LSAR to hardware indenture level required by the
Requiring Authority's maintenance and support concepts, definition of Candidate Items, procurement
requirements with allowances for existing data. For a major developmental program, the documentation
requirements by hardware indenture level are identified in Table 1.

27. The LSA data is used to develop logistics support requirements for ST&E, deployment, and In-service
operation and support. In this period, the LSAR data tables are populated to the requirements of the Data
Selection Sheet for the delivered LSAR. Logistic data products from a highly populated LSAR, and the final
delivered LSAR, can be used to produce comprehensive lists of logistic support resources, including
provisioning lists, S&TE, Training Equipment, personnel requirements, the identification of training
requirements, task requirements, maintenance plans and the content for developing technical manuals.
Many of these will be the basis for deliverable data products, or may replace the requirement for other
logistic data products produced in accordance with DIDs.

Testing and Introduction to In-Service

28. The LSAR data established during the Acquisition phase is retained during this period to support the
logistics analyses that occur as a result of engineering design changes. In addition, the LSAR data is used
to support the ST&E Activities to evaluate the system's Supportability during the testing phase and In-service
monitoring to verify achievement of Supportability requirements. The LSAR data also provides a reference
for analysis and planning for the transition of support resources to the In-service support system.

IN-SERVICE PHASE

29. After the Mission System and its Support System are deployed, the ST&E Activities may continue
monitoring the system for trends in Supportability Characteristics, particularly changes in R&M
characteristics, and initiate further analysis to fine tune the support systems or reprovisioning of resources.
The LSAR provides the benchmark of these Supportability Characteristics and the data necessary to
improve the system. The LSAR can also be used to assist the LSA process to determine the impact of future
equipment modifications, support requirements or changes in operational use, and for product improvement
programs, identify targets for upgrade/replacement. The LSAR data would also be used to establish design
changes, goals, and requirements for succeeding generations of materiel acquisitions and provide
information into the Comparative Analysis Activity for other new programs.

DISPOSAL PHASE

30. The LSAR can be used as a data source for analysing and planning for the disposal of a Mission
System and its Support System. The LSAR provides a ready list of items to be disposed of and support
resources that will be available for other systems. Additionally, if populated in the LSAR, hazardous materiel,
intellectual property and special security requirements can be easily identified.

TAILORING LSAR REQUIREMENTS

General

31. The extent, and consequently the cost, of LSAR inputs and outputs required to document and support
the analyses of LSA Activities will vary from program to program. These variations are attributable to such
factors as the degree of LSA Program visibility and control desired by the Requiring Authority; life cycle
phase; hardware complexity; and, the specific acquisition program characteristics (eg., new development,
major modification, non-developmental). In addition, the data requirements identified in DEF(AUST)5692
have been designed to accommodate the documentation and data manipulation to support Navy, Army, and
Air Force requirements. Each service has requirements for unique capabilities not generally applicable to

3D-4
DEF(AUST)5692

the other services. For the above reasons, the blanket purchase of the LSAR data elements and reports is
an ineffective and costly approach to the utilisation of the LSAR.

32. To realise maximum benefit from the application of the LSAR, it is imperative that extreme care be
exercised in the contractual imposition of the LSAR requirements. Data selection should not only be
concerned with the exclusion of unnecessary data requirements, but also, and just as important, with the
identification of all requirements which will eventually be needed to support a specific LSA Program effort
during Acquisition and In-service. Failure to adequately identify data requirements can be just as costly as
the over purchase of data. To that end, each functional and engineering specialty area must play a part in
tailoring the LSAR, including manpower and human factors engineering personnel. The guidance contained
in the following sections of this Annex have been arranged in a logical, stepwise sequence to assist in the
optimum selection of LSAR features.

LSA Activity Selection

33. The initial step in tailoring of the LSA data requirements involves selection of the analysis Activities
described in DEF(AUST)5691, which are to be accomplished. Detailed guidance for Activities tailoring and
focussing, is provided in Annex A to Chapter 3 of DEF(AUST)5691. Selection of some LSA Activities will
result in data that is documented directly into the LSAR. Output from other tasks becomes the input to
follow-on analyses, and as such, relates only indirectly to the LSAR documentation. Table II provides a list
of the LSA Activities and Steps, which relate directly to the LSAR data tables. A review of each data table is
mandatory to ensure that only those data elements required to document the Activity results are procured.
Once established, the specific data elements required to document the Activities should be recorded on the
Data Selection Sheet.

Interfacing and Coordination with other Program Elements

34. Data required to conduct an effective LSA Program may also be developed as a result of analyses
conducted in support of associated program elements such as:

a. Systems Engineering Program;

b. System/equipment design program;

c. System/equipment Reliability, Maintainability and Testability or RAM Program;

d. Human Factors Engineering program;

e. Standardisation and Parts Control program;

f. System safety program;

g. Packaging, handling, storage, and transportability program;

h. Initial provisioning program;

i. Survivability program;

j. Technical publications program;

k. Training and training equipment program;

l. Facilities program;

m. Support equipment program;

n. Test and Evaluation Program; and

o. Life Cycle Cost program.

35. Coordination and interfacing of engineering disciplines and ILS functional elements is essential to
maximise the use of data developed by each program element, thereby realising analysis economics and
avoiding the generation of incompatible ILS products. Effective coordination with related program elements
will produce benefits by avoiding duplication of effort.
3D-5
DEF(AUST)5692

36. Identification of the engineering and ILS functional element requirements which interface with the LSA
process, and which generate LSAR data, is the next consideration in the tailoring process. Results of
analyses from other program elements can be used as source data for LSA Activities and vice versa. For
example, inputs from the design, reliability, maintainability, human factors engineering, safety, and other
program elements may be required to satisfy the requirements of Task Analysis, as described in
DEF(AUST)5691. Benefits of effective interfacing and coordination may also be achieved by utilising the
features of the LSAR to record, store, and manipulate data in support of requirements levied by other
program elements. As an example, the LSAR data tables can be used to produce the LSA-018, Task
Inventory report. This report is used and reviewed by human systems integration specialists, as well as the
LSA Program.

37. With the program requirements in mind, data requirements that support analysis activities should be
identified, located in the LSAR, and assessed for suitability to meet program requirements. Due to the
relational nature of the LSAR, data tables are associated with discrete functions and organised into
functional groups. Firstly the LSAR tables, described in Annex A, should be identified and then the data
elements within the table reviewed. The definition of individual data elements is contained in Annex E and
this should also be reviewed if the meaning of a data element is not fully understood. The table descriptions
provide guidance regarding table rules that must be followed to correctly populate the applicable table, for
example a data element may need to be entered in one table before another table can be populated.

38. Data element selected from a data table to meet analysis requirements should be recorded in the Data
Selection Sheet (usually included in a DID). All key and mandatory fields in a table are required for any data
to be entered into that table; however, to reduce tailoring burden, the Data Selection Sheet does not repeat
foreign key fields in every table.

39. The next step in the tailoring process is the identification of the logistics DIDs associated with each
element of ILS that will be placed on contract. A detailed review of the DIDs is required to determine the
specific data element requirements of each. Standard LSAR summary reports may satisfy a number of LSA
Program DID requirements, or will satisfy part of the DID and allow the LSAR data to be submitted and the
summary reports generated as supporting information to the DID. Alternatively, ad hoc reports may be more
suitable in providing the necessary supporting information for specific ILS DIDs. If a standard LSAR report
meets the needs of a DID the data elements required to be populated can be found in Figure 1 of Annex B.
Finding the desired report number across the top of Annex B, Figure 1, and then reading down the column
will provide the user with the specific data elements and LSAR data tables required to produce the report.
Repeating the process, data requirements for each desired LSAR standard report would be identified for
listing on the Data Selection Sheet.

40. Standard LSAR Reports cover a major cross-section of LSAR data, but a project's report selection
may not cover all the data required to support an LSA Program and additional reports may not be cost
effective. Therefore careful consideration should be given to the selection of data by table first and the use
of ad hoc reports, instead of selecting additional standard reports that need data not required by the
program.

SCHEDULING OF THE LSAR DATA

41. This paragraph addresses scheduling the development of the LSAR data, so that it can be used in a
timely manner as source data for the development of contractually cited DIDs and other logistics products.
This guidance is applicable to any type of development effort and any phase of the life cycle. To establish
timely completion of the LSAR data, the Requiring Authority and Performing Activity must first establish the
scheduled completion dates for the data products that utilise LSAR data. Required delivery dates for the
products specified by DIDs should be established in conjunction with preparation of the solicitation package,
and should take into account the significant milestones of the project. The milestones will relate to the
development effort of the Mission System, the Support System, and resource development and delivery.

42. Once the scheduled completion dates for all chosen DIDs (in accordance with the Contract Data
Requirements Lists) have been established, the user can determine the required completion schedule for the
LSAR by the standard or ad hoc reports required as or in the production of the DIDs. Referring back to the
Data Element list for each selected standard report or ad hoc report identifies the tables and data required to
be populated for each DID by the applicable delivery date or milestone.

43. As an example, if the FMECA data on a new design project is to be assessed for CDR/DDR then LSA-
056 FMECA reports might be required to satisfy a DID a few weeks prior to CDR/DDR. Checking the LSA-
056 Data Element listing will show the specific data elements to be populated to produce the report, in this
case data comes from the X tables to identify the system/subsystem, FMECA and RAM related data from the

3D-6
DEF(AUST)5692

B tables, CA table data identifying resultant maintenance tasks and H table data for parts identification.
Hence the schedule of LSAR data population can be determined. Instead of requesting DIDs as reports to
fill this role, users from both the Requiring Authority and Performing Activity may seek LSAR data to be
populated by a set date to enable the production of ad hoc reports as required, in either case the schedule is
the same.

44. An example of an ad hoc report is the request of a functional system breakdown structure to a certain
indenture level, eg. 3 or 4 levels, as an LSAR data delivery just after contract or as a tender deliverable. This
may only require population of the XA, XB tables (or more if different models/UOCs are required) to produce
a hardware breakdown structure without waiting for the physical structure and parts allocation required to
produce the LSA-126 report. This is a common ad hoc report that provides a useful reference resource to the
product work breakdown structure for project teams and management.

45. The schedule for the population of data tables must also consider other factors, such as the level of
design freedom, analysis required and existing data. In the example of the FMECA report, the report may
only be required for review of new equipment/subsystems or existing systems they effect or interface with.
Existing off-the-shelf equipment/subsystems, not effected by or interfacing with new design items are less
critical for DDR/CDR, and may be viewed earlier from existing data, after DDR/CDR, or not at all, depending
on the confidence in the analysis of existing equipment/subsystems for the intended operating environment.

46. This approach to scheduling completion of the LSAR data must take into account interim product
delivery dates, final product delivery dates, and scheduled updates to final products. Each of these dates
will impact the range of LSAR data required, depth of data required (ie., the hardware indenture levels and
maintenance levels specified), and the number of updates to the LSAR data required. The LSAR completion
schedule must then be coordinated with the master program schedule and related program schedules (ie.,
drawing release) to ensure availability of data for LSAR development.

47. Finally, by establishing an LSAR completion schedule which is timely for DID product development,
the user now has the option of not requiring delivery of LSAR data as a separate data item and vice versa.
In effect, completion of a deliverable product, by report or completed data delivery, is intimately tied to the
LSAR data and quality. Whichever option is chosen, the Requiring Authority must be careful not to request
and pay for the same information twice, once as a report and secondly as an LSAR data delivery.

ALTERNATIVES FOR DATA DELIVERY

48. The last step in the LSAR data tailoring process involves delivery of the LSAR data itself. LSAR data
can be delivered in manual prepared form such as spreadsheet tables, LSAR data table files, or through on-
line access to a contractor LSA database. The use of a manual LSAR data file is generally applicable to
simple hardware systems, limited report requirements, infrequent use of the data, and uncomplicated
reports. Implementation of an automated LSAR is generally applicable to a complex hardware system or
minor system requiring data for inclusion in its parent system's LSAR, multiple and varied applications, ability
to produce tailored reports, on demand use with short response time, and the ability to manipulate the LSAR
data for specialised reports.

49. An automated LSAR presents the additional decision option of who will be made responsible for
Automated Data Processing (ADP) of the LSAR data. Normally, the Performing Activity would be
responsible for data processing, using a compliant, independently developed LSAR software system. The
alternative, for less complex projects, is to use the in-house capabilities of the Requiring Authority, thus
requiring only a data entry effort by the Performing Activity. Once the decision is made who will be
responsible for developing LSAR data, the media for delivery can be established.

50. Delivery of the LSAR relational tables via magnetic tape/disc other media or electronic transfer
provides options for delivery of data in an automated environment, which should be specified in the
applicable LSAR DID. An internal processing capability is required for each LSAR data file procured by the
Requiring Authority. Delivery of the LSAR relational tables provides the capability to subsequently produce
any of the LSAR reports, other data files, and to produce ad hoc reports via the query capability of a
compliant LSAR system. Separate delivery of the LSAR data files places the responsibility for their
generation with the Performing Activity rather than the Requiring Authority. Because of the flexibility
provided by these processable data files, they can be used to satisfy both interim and final LSAR delivery
requirements. Periodic delivery can reduce time spent for on-site data reviews by providing a vehicle for
advanced review of the data. Final contract deliverables can be consolidated and reduced by internal
processing of LSAR data files, in part or in total. In addition, compliant LSAR systems are required to have
the capability to produce and load standard outputs not only for all data tables, but also standard outputs for

3D-7
DEF(AUST)5692

"change only" data (changes to the data tables since the previous submittal of the LSAR data) as described
in Annex A.

51. The preferred option is on-line access to a Performing Activity's LSA database by using a compliant
LSAR system. On-line access includes the ability to selectively retrieve, review and print, and process
Performing Activity LSA source data. On-line access for faster Requiring Authority review of LSAR
information represents more of a Performing Activity service capability than a specific deliverable
requirement. This capability makes the most current authorised data available to the Requiring Authority and
eliminates the time and cost required for preparation and submission of deliverable products. It can also
significantly reduce the time requirement for on-site reviews, while supporting internal analyses and planning
that requires up-to-date Supportability information. On-line access provides the greatest flexibility for using
LSAR data, either by utilising the Performing Activity's automated LSAR capabilities, or by electronically
transferring the data for review by internal Requiring Authority organisations.

3D-8
DEF(AUST)5692

LSAR DATA TABLE UTILISATION BY HARDWARE BREAKDOWN

LSAR Data System Sub System Repairable Part Support


Tables Item Equipment

XA A A A A N
XB A A A A N
XC A N N N N
XD A N N N N
XE A A A A N
XF A A A A N
XG A A A A N
XH A A A A N
XI A A A A N
AA A B N N N
AB A B N N N
AC A B N N N
AD A B N N N
AE A B N N N
AF A B N N N
AG A B N N N
AH A B N N N
AI A B B N N
AJ A B N N N
AK A B N N N
BA A A A N N
BB A A A N N
BC A A A N N
BD A A A N N
BE A A A N N
BF A A A N N
BG A A A N N
BH A A A N N
BI A A A N N
BJ A A A N N
BK A A A N N
BL A B N N N
CA A A A N N
CB A A A N N
CC A A A N N
CD A A A N N
CE A A A N N
CF A A A N N
CG A A A N N
CH A A A N N
CI A A A A N
CJ B B B N B
CK B B B N B
EA N N N N A
EB N N N N A
EC N N N N A
ED N N N N A
EF N N N N A
EG N N N N A
EH N N N N A
EI N N N N A
EJ N N N N A
EK N N N N A
EM N N N N A

3D-9
DEF(AUST)5692

UA B B B N A
UB B B B N A
UC B B B N A
UD B B B N A
UE B B B N A
UF B B B N A
UG B B B N A
UH B B B N A
UI B B B N A
UJ B B B N A
UK B B B N A
UL B B B N A
UM N N N N A
UN N N N N A
FA A A B N N
FB A A B N N
FC A A B N N
FD A A B N N
FE A A B N N
GA A A A N N
GB A A A N N
GC A A A N N
GD A A A N N
GE A A A N N
HA A A A A A
HB A A A A A
HC A A A A A
HD A A A A A
HE A A A A A
HF A A A A A
HG A A A A A
HH A A A A A
HI A A A A A
HJ A A A A A
HK A A A A A
HL A A A A A
HM A A A A A
HN A A A A A
HO A A A A A
HP A A A A A
HQ A A A A A
HR A A A A A
JA A B N N N
JB A B N N N
JC A B N N N
JD A B N N B
JE A B N N N
JF A B N N N

LEGEND: A - Generally Applicable


B - Dependent Upon Program Requirements
N - Generally Not Applicable

Table 1 LSAR Data Table Use by Hardware Breakdown

3D-10
DEF(AUST)5692

CONCEPT AND EARLY ACQUISITION PHASE LSAR

Data Table DED Data Element

AA 001 Achieved Availability


064 Crew Size
164 Inherent Availability
222 Maximum Time to Repair
223 Operational Mean Active Maintenance Downtime
236 Operational Mean Time to Repair
454 Total Systems Supported

AB 021 Annual Number of Missions


022 Annual Operating Days
024 Annual Operating Time
228 Mean Mission Duration
273 Operational Availability

AG 238 Annual Operating Requirement Measurement Base


023 Annual Operating Requirement

BB 180 Item Function


207 Maintenance Concept
315 Qualitative and Quantitative Maintainability Requirements

CA 427 Task Code


430 Task Frequency
431 Task Identification
358 Facility Requirement Code
358 Tool / Support Equipment Requirement Code
358 Training Equipment Requirement Code

EE 078 Description and Function of Support Equipment


188 Justification

FA 118 Facility Name

FC 107 Facilities Maintenance Requirement

GC 007 New or Modified Skill Additional Requirements


012 Additional Training Requirements
094 Educational Qualifications
188 Skill Justification

Table 2 Concept and Early Acquisition Phase LSAR

3D-11
DEF(AUST)5692

LSAR DATA TABLES RELATED TO LSA ACTIVITIES

LSA ACTIVITY/STEP APPLICABLE LSAR DATA TABLES


(Application)

Use Study/ Quantitative AE, AF, AH, BB, BL


Factors
Comparative Analysis BD, BE, FA, FB, FC
Functional Requirements AA, AB, AC, AD, AE, AG, AH, AI, AJ, GA
Definition
Task Analysis / Task BA, BB, BC, BD, BE, BF, BG, BH, BI, BJ, BK, BL, CA,
Identification CB, CC, CD, CE, CF, CG, CH, CI, CJ, CK, GA, XI
Functional Requirements ID AA, AB, AC, AD, AE, AG, CA, CB, CC, CD, CE, CF, CG,
/ Updates CH, CI, XI
Physical Evaluations and AI, XA, HG
Tradeoffs (LORA)
Task Analysis / Task CA, CB, CC, CD, CE, CF, CG, CH, CI, XI
Characteristics
Task Analysis / Document CA, CB, CC, CD, CE, CF, CG, CH, CI, XI
Task Analysis / New & EA, EB, EC, ED, EF, EG, EH, EI, EJ, EK, EL, EM, FD,
Critical Resources GB, GC, GD, UA, UB, UC, UD, UE, UF, UG, UH, UI
Task Analysis (Training) EE, GA, GB, GC, GD
Task Analysis (Updates) CA, CB, CC, CD, CE, CF, CG, CH, CI, FA, FB, FC, FD,
FE, XI
Task Analysis JA, JB, JC, JD, JE, JF
(Transportability)
Definition of Resource HA, HB, HC, HD, HE, HF, HG, HH, HI, HJ, HK, HL, HM,
Package / Provisioning HN, HO, HP, HQ, HR, XB, XC, XD, XE, XF, XG
Definition of Resource HA, HB, HG
Package / Provisioning
(Screening)
Task Analysis / Validation All tables as applicable, except the "A" tables
Definition of Resource All tables as applicable
Package
Supportability Test and All tables as applicable
Evaluation

Table 3 LSAR Data Tables Related to LSA Activities

3D-12
DEF(AUST)5692

DATA ITEM DESCRIPTION (DID) RELATIONSHIPS TO THE LSAR

DATA ITEM DESCRIPTION PURPOSE LSAR APPLICATION/LSAR


NUMBER AND TITLE INTERFACE

DESIGN INFLUENCE AND


INTEGRATION TO
INCLUDE LOGISTIC
RELATED RELIABILITY
AND MAINTAINABILITY

DI-ILSS-81162A, LSA-050, This report is used to analyze the The LSA-050, summary provides all
Reliability Centered impacts of the RCM decisions in the data to satisfy this DID. This
Maintenance Summary order impact design and requirement is specified in annex B.
Supportability decisions.

DI-ILSS-81163A, LSA-056, This report provides an analysis of The LSAR provides all the FMECA
Failure Modes Effects and independent single item failures worksheet data necessary to satisfy
Criticality Analysis (FMECA) and the resulting potential impact the requirements of this DID.
Report on mission success performance, Additional information such as
personnel safety, and FMECA assumptions block diagrams,
maintainability. The analysis excluded items list, critical
promotes design corrective actions components, etc., may also be
by identifying potential failure risks required. The LSA-056 summary is
in order that appropriate actions the FMECA report specified in annex
may be taken to eliminate or control B.
the high risk items.

MAINTENANCE PLAN

DI-ILSS-81140A , LSA-004, The MAC is a management tool, The LSA-004 summary provides all
Maintenance Allocation which assigns all maintenance the data requirements of this DID for
Chart functions and repair operations sections II, III, and IV. Section I is
performed by the lowest prepared in accordance with MIL-M-
appropriate maintenance category, 630388 (TM). This requirement is
and delineates the tools and test specified in annex B.
equipment requirements required to
perform the operations. The MAC
is used as appendix B of the
Organisational Maintenance
manual.

DI-ILSS-81183A, LSA-023, This report consists of four parts The LSA-023 summary provides all
Maintenance Plan Summary which may be provided together or the data requirements necessary to
individually. Part I contains general completely satisfy this DID. This
information pertaining to the system requirement is specified in annex B.
end item and the
maintenance/support concept. Part
II contains reliability and
maintainability characteristics or the
item. Part III lists corrective and
preventive maintenance required,
and part IV lists support and
associated technical data.

3D-13
DEF(AUST)5692

DATA ITEM DESCRIPTION PURPOSE LSAR APPLICATION/LSAR


NUMBER AND TITLE INTERFACE
DI-ILSS-80119C, LSA-024, This report consists of three parts, The LSA-024 summary provides all
Maintenance Plan Part I contains general the data requirements necessary to
considerations (design description, completely satisfy this DID. This
maintenance plan Summary, and requirement is specified in annex B.
maintenance plan rationale), Part II
describes the repair capability
required to support the item. Part
III contains a list of maintenance
tasks by category (preventive,
corrective, servicing and
calibration).

MANPOWER AND
PERSONNEL

DI-ILSS-81138A, LSA-001, This report provides a summary of The LSA-001 summary provides all
Annual Man-Hours by Skill manpower requirements for a the data requirements necessary to
Specialty Code and Level of system/ equipment, and is used to completely satisfy this DID. This
Maintenance determine time required and requirement is specified in annex B.
number of persons to perform each
operations/maintenance task.

DI-ILSS-8165A, LSA-065, This report identifies a summary of The LSA-065 summary provides all
Manpower Requirements man-hour information by scheduled the data requirements necessary to
Criteria and unscheduled, on equipment; completely satisfy this DID. This
and un-scheduled, off equipment. requirement is specified in annex B.

DI-ILSS-80290B, LSA-075, This report identifies critical man- The LSA-075 summary provides all
Consolidated Manpower, power and personnel data by the data requirements necessary to
Personnel and Training maintenance level and completely satisfy this DID. This
Report. new/modified skill requirements as requirement is specified in annex B.
a baseline for performing
hardware/manpower analysis.

SUPPLY SUPPORT

DI-ILSS-81285, Provisioning The PPL is a listing of components, The LSA-036 summary provides all
Technical Documentation, assemblies, and support items the data requirements necessary to
Provisioning Parts List option used in the end item, which are completely satisfy this DID. This
furnished under contract. The list is requirement is specified in annex B.
used to determine the range and
quantity of support items for an
initial period of time.

Short Form Provisioning The SFPPL serves as an early The LSA-036 summary provides all
Parts List option identification of support items which the data requirements necessary to
are recommended by the contractor completely satisfy this DID. This
for initial provisioning. requirement is specified in annex B.

Long Lead Times Item List The LLTIL is a listing of those items The LSA-036 summary provides all
option which, because of their complexity the data requirements necessary to
of design, complicated completely satisfy this DID. This
manufacturing process or limited requirement is specified in annex B.
production capacity may cause
production cycles, which would
preclude timely delivery if ordered
in advance of normal provisioning.

3D-14
DEF(AUST)5692

DATA ITEM DESCRIPTION PURPOSE LSAR APPLICATION/LSAR


NUMBER AND TITLE INTERFACE
Repairable Items List option This list identifies all items which The LSA-036 summary provides all
are repairable within the breakdown the data requirements necessary to
of the end item. completely satisfy this DID. This
requirement is specified in annex B.

Interim Support Items List This list identifies those items The LSA-036 summary provides all
option required for support between initial the data requirements necessary to
operational capability and the point completely satisfy this DID. This
in time when standard provisioning requirement is specified in annex B.
is accomplished.

Tool and Test Equipment The TTEL identifies support items The LSA-036 summary provides all
List option required to repair an end item. The the data requirements necessary to
list is used in the procurement of completely satisfy this DID. This
required items to support the end requirement is specified in annex B.
item under contract.

Common and Build Items The CBIL provides a composite of The LSA-036 summary provides all
List option common hardware and the data requirements necessary to
consumables necessary to support completely satisfy this DID. This
routine maintenance of a requirement is specified in annex B.
component and not otherwise
classified as a repair part.

Design Change Notice This list identifies those changes The LSA-036 summary provides all
option made to previously provisioned the data requirements necessary to
items. Items are identified as completely satisfy this DID. This
added, deleted, superseded, or requirement is specified in annex B.
modified.

Post Conference List option The PCL provides a reviewed and The LSA-036 summary provides all
approved list of support items the data requirements necessary to
required for the maintenance and completely satisfy this DID. This
support of the system/end item or requirement is specified in annex B.
assembly.

System Configuration The SCPL provides a listing of The LSA-036 summary provides all
Provisioning List option inter-facing items between the data requirements necessary to
provisioned end items relating completely satisfy this DID. This
theme to an entire system requirement is specified in annex B.
breakdown.

DI-ILSS-81287, LSA-151, The PPLI is a companion document The LSA-151 summary provides all
Provisioning Parts List Index to other provisioning lists and the data requirements necessary to
(PPLI) provides summary information on completely satisfy this DID. This
each line item of the provisioning requirement is specified in annex B.
list.

DI-ILSS-80293B, LSA-155, This list provides the contractor's The LSA-155 summary provides all
Recommended Spare Parts recommendations for support item the data requirements necessary to
List for Spares Acquisition candidates for the SAIP program. completely satisfy this DID. This
Integrated with Production requirement is specified in annex B.
(SAIP)

DI-ILSS-81287, Provisioning This summary is used to identify The LSA-032 summary provides all
and Other Preprocurement existing national stock numbers the data requirements necessary to
Screening and cataloging information by completely satisfy this DID. This
creating "LSR" type screening requirement is specified in annex B.
transactions.

3D-15
DEF(AUST)5692

DATA ITEM DESCRIPTION PURPOSE LSAR APPLICATION/LSAR


NUMBER AND TITLE INTERFACE
SUPPORT EQUIPMENT
AND TEST
MEASUREMENT AND
DIAGNOSTIC EQUIPMENT

DI-ILSS-80118C, LSA-070, This report consist of six sections. It The LSA-070 summary provides all
Support Equipment represents the contractor's the data requirements necessary to
Recommendation Data recommendations for maintenance completely satisfy this DID. Annex B
(SERD) level operational support equipment and MIL-STD-2097 cite the
necessary for organizational, requirement for a SERD summary.
intermediate, and depot level
maintenance.

DI-ILSS-81166A, LSA-071, This report provides a consolidated The LSA-071 summary provides all
Support Equipment listing of active and disapproved the data requirements necessary to
Candidate List support equipment (SE) candidates completely satisfy this DID. This
in order to better manage these requirement is specified in annex B.
critical support items.

DI-ILSS-80286B, LSA-072, This report identifies a TMDE item The LSA-072 summary provides all
Test, Measurement, and and provides a summary of TMDE the data requirements necessary to
Diagnostic Equipment requirements and technical completely satisfy this DID. This
(TMDE) Requirements description to verify the applicability requirement is specified in annex B.
Summary of the test equipment for use on the
system/end item.

DI-ILSS-130289B, LSA-074, This report identifies stock listed The LSA-074 summary provides all
Support Equipment Tool List tools, commercially available tools, the data requirements necessary to
modified tools, stock listed and completely satisfy this DID. This
commercial, and tools requiring requirement is specified in annex B.
development.

DI-ILSS-81167A, LSA-076, This report provides information The LSA-076 summary provides all
Calibration and concerning calibration intervals and the data requirements necessary to
Measurement Requirements parameters for calibration completely satisfy this DID This
Summary measurement. requirement is specified in annex B
and MIL-STD-1839.

TECHNICAL DATA AND


MANUALS

DI-ILSS-81153A, LSA-019, This report provides a listing of The LSA-019 summary provides all
Task Analysis Summary personnel and support items to the data requirements necessary to
perform each completely satisfy this DID. This
operations/maintenance task, and requirement is specified in annex B.
the step-by-step sequential task
procedures. It is used as source
information in preparation of
narrative technical publications.

DI-ILSS-81156A, LSA-030, This report consists of four sections This LSA-030 option provides all the
Indentured Parts List, Repair which are used to satisfy the listing data requirements necessary to
Parts and Special Tools List and indexes requirements of a completely satisfy this DID. This
(RPSTL) Option repair parts manual. It consists of requirement is specified in annex B
general instructions, repair parts, and MIL-STD-335, paragraph 5.
list, special tools list, and four
cross-reference indexes.

3D-16
DEF(AUST)5692

DATA ITEM DESCRIPTION PURPOSE LSAR APPLICATION/LSAR


NUMBER AND TITLE INTERFACE
Stockage List Type Four This report is used to satisfy the This LSA-030 option provides all the
Report Option listing portion of part I, Item data requirements necessary to
Identification Listing for a Type completely satisfy this DID. This
Four Stockage List Manual (Marine requirement is specified in annex B.
Corps).

Illustrated Parts Breakdown This report is used to satisfy This LSA-030 option provides all the
Option Section II, Maintenance Parts List, data requirements necessary to
and Section III, Numerical Index, of completely satisfy this DID. This
the IPB. requirement is specified in annex B
and MIL-M-38807.

DI-ILSS-81157A, LSA-033, This report identifies the The LSA-033 summary provides all
Preventive Maintenance crew/operator PMCS necessary for the data requirements necessary to
Checks and Services the operators technical manual. completely satisfy this DID. This
(PMCS) requirement is specified in annex B
and MIL-M-63036 (TM).

DI-ILSS-81160A, LSA-040, This report, consisting of four This LSA-040 option provides all the
Authorization List Items sections, are listings required for an data requirements necessary to
Option operator’s or combined operator's completely satisfy this DID. This
and maintenance manual. The requirement is specified in annex B
sections are: components of end and MIL-M-63036 (TM).
item; basic issue items list;
additional authorization list items;
and, expendable/durable supplies
and materials list items.

Stockage List Type Three This report, consisting of three This LSA-040 option provides all the
Option sections, are listings required for a data requirements necessary to
stockage list type three (Marine completely satisfy this DID. This
Corps) manual. The sections are: requirement is specified in annex B.
supply system responsible items
(also listing principal end items),
using unit responsible items, and
collateral equipment.

PACKAGING, HANDLING
AND STORAGE

DI-PACK-80120, This report provides detailed The LSA-025 summary provides all
Preservation and Packing packing information necessary to the data requirements necessary to
Data determine packing level completely satisfy this DID. This
requirements. requirement is specified in annex B
and MIL-STD-2073-1A, appendix K.

TRANSPORTATION AND
TRANSPORTABILITY

DI-ILSS-81170A, LSA-085, This report identifies information The LSA-085 summary provides all
Transportability Summary critical to the shipping and transport the data requirements necessary to
of major end items of equipment. completely satisfy this DID. This
requirement is specified in annex B.

3D-17
DEF(AUST)5692

DATA ITEM DESCRIPTION PURPOSE LSAR APPLICATION/LSAR


NUMBER AND TITLE INTERFACE
FACILITIES

DI-ILSS-81148A, LSA-012, This report identifies tasks which The LSA-012 summary provides all
Facility Requirement require new or modified facilities or the data requirements necessary to
facility requirements for training. completely satisfy this DID. This
Also included in this summary are requirement is specified in annex B.
narrative explanations,
descriptions, and justifications of
facility requirements

DI-ILSS-80291B, LSA-017, This report identifies depot The LSA-017 summary provides all
Depot Maintenance requirements divided into three the data requirements necessary to
Interservice Data Summary parts. Part I contains all repairable completely satisfy this DID. This
items and the applicable tasks requirement is specified in annex B.
which are performed at depot. Part
II lists all required support
equipment and new, modified, or
existing depot facility requirements.
Part III provides detailed
information concerning depot
support equipment and associated
test program sets.

HUMAN SYSTEMS
INTEGRATION

DI-ILSS-81152, LSA-018, This report provides a complete The LSA-018 summary provides all
Task Inventory Report listing of Jobs and Duties with their the data requirements necessary to
related operating and maintenance completely satisfy this DID. This
tasks, subtasks, and elements. It is requirement is specified in annex B.
useful to human systems
integration specialists in particular.

3D-18
DEF(AUST)5692 ANNEX E TO
CHAPTER 3

DATA ELEMENT DICTIONARY


INTRODUCTION
Purpose

This annex provides the Data Element Dictionary for the Logistic Support (LSA) Analysis Record (LSAR) and
information for interpreting and using it. The dictionary contains all the data elements and names that
appear on the LSAR data relationship tables.

SECTIONS
The dictionary is divided into three sections, followed by the Data Selection Sheet at Appendix 1.

Section 1: Index of Data Element Titles

This section contains listing of Data Element Definition (DED) numbers and titles. For each DED, the
relational table location(s) in which the data element appears, by table and element codes, are depicted.

Section 2: Index of Data Element Codes

This section is an alphabetical listing of the data element codes used on the LSAR data relational tables with
cross-references to the data element roll names they represent. Also listed are the applicable DED
numbers.

Section 3: Data Element Definitions

This section contains definitions for all data elements that appear on the LSAR data relationship tables. The
DED contains some or all of the following entries. When a standard data element acronym applies, this is
also listed in this section.

a. DED Number;

b. Data element title with acronym;

c. Field format;

d. DED;

e. Data item(s);

f. Data code(s); and

g. Role name(s).

Format. The general format for each Data Element Definition is as follows:

DED # DATA ELEMENT TITLE (ACRONYM) FIELD FORMAT


DATA ELEMENT DEFINITION
DATA ITEM(S) DATA CODE(S)
ROLE NAME(S)
DEF(AUST)5692

Example of actual DED entry:

339 RELIABILITY/MAINTAINABILITY INDICATOR CODE 1AF-

A code used to indicate whether the reliability and maintainability parameters entered on the card are
allocated, predicted, measured, or comparability analysis values.

Comparability analysis C
Allocated A
Predicted P
Measured M

Definition of Terms

DED Number. A sequentially assigned number to each data element in the dictionary for use in locating and
referencing it throughout the dictionary and data entry instructions (Annex A).

Data Element Title. The noun phrase name used to identify the data element. Sufficient adjectival modifiers
are used with the noun name to ensure title uniqueness.

Field Format. A specification for the length, type, positional justification, and decimal placement of a data
element field, or subfield thereof, as described below:

a. Length. The number of character positions in the data element. In the event the length is
variable, the maximum length is specified.

b. Type. A specification of the character type, wherein:

"A" specifies that all characters of the data entry are upper case alphabetical.

"N" specifies that all characters of the data entry are numerical.

"X" specifies that characters of the data entry are upper case alphabetical, numerical, special, or
any combination thereof.

"D" specifies that characters of the data entry are numerical with floating decimal. Decimals
may be entered as required or exponentially, e.g., "0.0000325" or "3.25E-5".

c. Justification. Specifies from which side of the field the characters of the data element are
entered. Those starting at the left are left justified (L), those starting at the right are right
justified (R). Those which always occupy the entire field are fixed (F), as shown below. A dash
(-) is used if this column is not applicable.

(L) 3 1 0 2
(R) 3 1 0 2
(F) 1 3 1 0 2 0 5

d. Decimal Placement. Specifies the number of character positions to the right of the assumed
decimal point when the data element is numeric in all character positions. A dash (-) is used if
this column is not applicable. AS means "As Specified" and the detailed instructions will
indicate the location of decimal points.

DED. A narrative definition of the data element in sufficient detail to present a clear and complete
understanding of the precise data or element of information that the data element represents.

Data Item. One of a set of descriptive items of information or values that apply to a data element. For
example, the data element "Skill Level Code" contains the data items "Basic", "Intermediate", and
"Advanced".

Data Code. One or more alphabetical, numerical, special characters, or any combination thereof, that
represent a data item and that are to be entered in a field on an LSAR data record. A code is used instead
of the data item itself, in order to conserve space on the data records and to facilitate machine processing.

3E-2
DEF(AUST)5692

For example, under the data element "Security Clearance", and the Data Items "Top Secret", "Secret",
"Confidential" and "Unclassified", are represented by the data codes "1", "2", "3", and "4", respectively.

Notes:

1. In some cases, a position left blank counts as a data code signifying some particular data item value as specified
in the dictionary. For example for the data element, "Maximum Allowable Operating Time", the third position of
the four-position code designates the appropriate multiplier code. The codes are " " (blank), X, C, or M, with a " "
(blank) designating a multiplier of one (1), "x" a multiplier of ten (10), "C" a multiplier of one hundred (100), and
"M" a multiplier of one thousand (1000).
2. When data items and data codes are too voluminous to be included in this document, reference is made to items
and codes in another document. For example, see Skill Specialty Code, DED No. 379.

Role Name. A unique modifier of a data element title that describes the use/application of the data element
within a specific relational data table location.

3E-3
DEF(AUST)5692

SECTION 1

INDEX OF DATA ELEMENT TITLES

DED DATA ELEMENT TITLE TABLE LOCATION


001 ACHIEVED AVAILABILITY AA.ACHAVAAA, BD.ACHAVABD

002 ACQUISITION DECISION OFFICE EA.AQDCOFEA

003 ACQUISITION METHOD CODE (AMC) HA.ACQMETHA

004 ACQUISITION METHOD SUFFIX CODE (AMSC) HA.AMSUFCHA

005 ADAPTOR/INTERCONNECTION DEVICE REQUIRED EA.AIDRQDEA

006 ADDITIONAL REFERENCE NUMBER HB.ADDREFHB

007 ADDITIONAL SKILL REQUIREMENT: SKILL REQUIRING A GC.NMSNARGC, GC.NMSNCDGC(A)


NEW OR REVISED SKILL CODE

008 ADDITIONAL SKILLS AND SPECIAL TRAINING EE.SEQNAREE, EE.SENARCEE(F)


REQUIREMENTS

009 ADDITIONAL SPECIFICATIONS/REQUIREMENTS AF.WPADDRAF

010 ADDITIONAL SUPPORTABILITY CONSIDERATIONS AK.SEINARAK, AK.SEINCDAK(A)

011 ADDITIONAL SUPPORTABILITY PARAMETERS AK.SEINARAK, AK.SEINCDAK(B)

012 ADDITIONAL TRAINING REQUIREMENTS GC.NMSNARGC, GC.NMSNCDGC(D)

013 ADMINISTRATIVE AND LOGISTIC DELAY TIME (ALDT) AB.OPALDTAB, BE.ALDTXXBE

014 ADMINISTRATIVE LEAD TIME XA.ADDLTMXA

015 ALLOCATION DATA EB.ALORG1EB, EB.ALORG2EB,


EB.ALORG3EB, EB.ALORG4EB,
EB.ALORG5EB, EB.ALORG6EB,
EB.ALORG7EB, EB.ALORG8EB,
EB.ALORG9EB, EB.ALRG10EB,
EB.ALDNDSEB, EB.ALEXRNEB,
EB.ALLVCDEB, EB.ALMLVLEB,
EB.ALSTIDEB

016 ALLOWANCE EB.ALDCNMEB, UA.UTALLOUA,


UM.SUTALLUM

017 ALLOWANCE ITEM CODE (AIC) HG.ALLOWCHG

018 ALLOWANCE ITEM QUANTITY HG.ALIQTYHG

019 ALTERNATE LOGISTIC SUPPORT ANALYSIS CONTROL XB.ALTLCNXB, XC.ALTLCNXB,


NUMBER CODE (ALC) XD.ALTLCNXB, XE.ALTLCNXE,
XE.ALCSEIXE, XF.ALTLCNXF,
XF.ALCSEIXF, XG.PALCNCXG,
XG.FALCNCXG

3E-4
DEF(AUST)5692

AA.ALTLCNXB, AB.ALTLCNXB,
AC.ALTLCNXB, AD.ALTLCNXB,
AE.ALTLCNXB, AF.ALTLCNXB,
AG.ALTLCNXB, AH.ALTLCNXB,
AJ.ALTLCNXB, AK.ALTLCNXB,
BA.ALTLCNXB, BB.ALTLCNXB,
BC.ALTLCNXB, BD.ALTLCNXB,
BE.ALTLCNXB, BF.ALTLCNXB,
BG.ALTLCNXB, BH.ALTLCNBH,
BH.TALCNCBH, BI.ALTLCNXB,
BJ.ALTLCNXB, BK.ALTLCNXB

CA.ALTLCNXB, CA.REFALCCA,
CA.AORALCCA, CB.ALTLCNXB,
CB.RFDALCCB, CC.ALTLCNXB,
CD.ALTLCNXB, CF.ALTLCNXB,
CG.ALTLCNXB, CH.ALTLCNXB,
CI.TSKALCCI, CI.PROALCCI,
CK.ALTLCNXB

UA.UUTALCUA, UB.UUTALCUA,
UD.UUTALCUA, UF.UUTALCUA,
UG.UUTALCUA, UH.TSKALCCI,
UH.PROALCCI, UJ.UUTALCUA,
UL.UUTALCUA

FE.ALTLCNXB, GE.ALTLCNXB

HG.ALTLCNXB, HH.ALTLCNXB,
HI.ALTLCNXB, HJ.ALTLCNXB,
HK.ALTLCNXB, HL.ALTLCNXB,
HN.ALTLCNHN, HN.ALCSEIHN,
HO.ALTLCNHO, HO.ALCSEIHO,
HP.ALTLCNXB, HQ.ALTLCNXB,
HR.ALTLCNHO, HR.ALCSEIHO

JA.ALTLCNXB, JB.ALTLCNXB,
JC.ALTLCNXB, JD.ALTLCNXB,
JE.ALTLCNXB, JF.ALTLCNXB

MA.ALTLCNXB, MB.ALTLCNXB,
MC.ALTLCNXB, MD.ALTLCNXB,
ME.ALTLCNXB, MF.ALTLCNXB

RA.ALTLCNXB, RB.ALTLCNXB,
RD.ALTLCNXB, RD.INTALCRD,
RE.ALTLCNXB, RE.INTALCRE,
RF.ALTLCNXB, RG.ALTLCNXB,
RI.ALTLCNXB, RI.REFALCRI,
RJ.ALTLCNXB, RL.ALTLCNXB,
RL.MPTALCRL, RM.ALTLCNXB,
RN.ALTLCNXB, RO.ALTLCNXB,
RP.ALTLCNXB, RP.SSTALCRP

VA.ALTLCNXB, VE.ALTLCNXB,
VF.ALTLCNXB, VT.ALTLCNXB,
WB.ALTLCNXB, WC.ALTLCNXB,
WH.ALTLCNXB, WJ.ALTLCNXB,
WK.ALTLCNXB, WN.ALTLCNXB,
WO.SRVALCWO, WP.ALTLCNXB,
WQ.ALTLCNXB, WR.ALTLCNXB,
WS.ALTLCNXB, WT.ALTLCNXB,
WT.SRVALCWO, WY.ALTLCNXB,
WY.WACALCWY; ZL.ALTALCZL,
ZL.BASALCZL,
3E-5
DEF(AUST)5692

020 ANNUAL MAN-HOURS AC.MLSAMHAC, AC.MLUAMHAC

021 ANNUAL NUMBER OF MISSIONS AB.ANNOMIAB

022 ANNUAL OPERATING DAYS AB.ANOPDAAB

023 ANNUAL OPERATING REQUIREMENT (AOR) AG.ANOPREAG

024 ANNUAL OPERATING TIME AB.ANOPTIAB

025 APPORTIONED UNIT COSTS UC.OTPACRUC, UC.OTPACNUC,


UE.TPAUCRUE, UE.TPAUCNUE,
UI.AIDUCNUI, UI.AIDUCRUI

026 ARMED SERVICES VOCATIONAL APTITUDE BATTERY GB.ABAFQTGB, GB.AAEXRLGB,


(ASVAB) SCORE GB.AAEXRHGB, GB.AALPRLGB,
GB.AALPRHGB, GD.ASVAPEGD,
GD.AAEERLGD, GD.AAEERHGD,
GD.AAELPLGD, GD.AAELPHGD

027 AUTOMATIC DATA PROCESSING EQUIPMENT CODE HA.ADPEQPHA

028 AVAILABLE MAN-HOURS AE.AVAIMHAE

029 AXLE LENGTH JC.TWALFIJC, JC.TWALFOJC,


JC.TWALRIJC, JC.TWALROJC

030 BASIS OF ISSUE (BOI) HM.BOICTRHM, HM.QTYBOIHM,


HM.RATIOBHM, HM.LVLBOIHM

031 BUILT-IN-TEST CANNOT DUPLICATE PERCENTAGE BA.BITNDPBA

032 BUILT-IN-TEST DETECTABILITY LEVEL PERCENTAGE BA.BDLPGABA, BA.BDLPGBBA

033 BUILT-IN-TEST RETEST OK PERCENTAGE BA.BITROPBA

034 CALIBRATION AND MEASUREMENT REQUIREMENTS UG.UUTPPCUG, UN.UTPACMUN


SUMMARY PARAMETER CODE

035 CALIBRATION AND MEASUREMENT REQUIREMENTS EA.CMRSRCEA, UB.UTCMRSUB


SUMMARY RECOMMENDED

036 CALIBRATION AND MEASUREMENT REQUIREMENTS UB.UTSTCDUB, UM.SUTSTCUM


SUMMARY STATUS

037 CALIBRATION INTERVAL EA.CALINTEA

038 CALIBRATION ITEM EA.CALITMEA

039 CALIBRATION PROCEDURE EC.CALPROEC

040 CALIBRATION REQUIRED EA.CALRQDEA

041 CALIBRATION STANDARD REQUIRED EA.CALSTDEA

042 CALIBRATION TIME EA.CALTIMEA

043 CHANGE AUTHORITY NUMBER HP.CANUMBHP, HQ.CANUMBHP,


HR.CANUMBHP

044 SUPPORT EQUIPMENT CHARACTERISTICS EE.SEQNAREE, EE.SENARCEE(D)

045 CLEANING AND DRYING PROCEDURE HF.CDPROCHF

3E-6
DEF(AUST)5692

046 COMMERCIAL AND GOVERNMENT ENTITY (CAGE) XH.CAGECDXH, AH.IOCAGEAH,


CODE CG.TSCAGECG, CI.PROCAGCI

EA.SECAGEEA, EB.SECAGEEA,
EC.SECAGEEA, ED.SECAGEEA,
EE.SECAGEEA, EF.SECAGEEA,
EG.SECAGEEA, EH.SECAGEEA,
EI.SECAGEEA, EJ.SECAGEEA,
EK.SECAGEEA, EK.SPRCAGEK,
EL.SECAGEEA, EM.SECAGEEA,
EM.SCAGECEM, UB.SECAGEEA,
UC.OTPCAGUC, UD.SECAGEEA,
UD.OTPCAGUC, UE.OTPCAGUC,
UE.TPICAGUE, UG.SECAGEEA,
UH.PROCAGCI, UH.SECAGEEA,
UI.AIDCAGUI, UJ.SECAGEEA,
UJ.AIDCAGUI, UK.ATECAGUK,
UL.SECAGEEA, UL.ATECAGUK,
UM.SUTCAGUM, UN.TGSCAGUN,
UN.SUTCAGUM

HA.CAGECDXH, HB.CAGECDHB,
HB.ADCAGEHB, HC.CAGECDHC,
HC.CTCAGEHC, HD.CAGECDXH,
HE.CAGECDXH, HF.CAGECDXH,
HF.PKCAGEHF, HG.CAGECDXH,
HH.CAGECDXH, HI.CAGECDXH,
HJ.CAGECDXH, HK.CAGECDXH,
HL.CAGECDXH, HM.CAGECDXH,
HN.CAGECDHN, HO.CAGECDHO,
HP.CAGECDXH, HQ.CAGECDXH,
HR.CAGECDHO

VA.CAGECDXH, VD.CAGECDXH,
WE.CAGECDWE, WF.CAGECDWF,
WI.CAGECDWF, WI.CAGECDWE,
WJ.CAGECDWF, WJ.CAGECDWE,
WK.CAGECDWE, WK.CAGECDWF,
WY.CAGECDWF, RH.CAGECDXH

047 COMMERCIAL AND GOVERNMENT ENTITY CODE XH.CANAMEXH, XH.CASTREXH,


ADDRESS XH.CACITYXH, XH.CASTATXH,
XH.CANATNXH, XH.CAPOZOXH

048 COMMON UNIT UNDER TEST UI.AIDCUTUI

049 COMPENSATING DESIGN PROVISIONS BJ.FMCNARBJ , BJ.FMMPCNBJ(A)

050 COMPENSATING OPERATOR ACTION PROVISIONS BJ.FMCNARBJ , BJ.FMMPCNBJ(B)

051 CONCURRENT PRODUCTION CODE (CPC) HD.CURPRCHD, HE.CURPRCHE

052 CONTACT TEAM DELAY TIME XA.CTDLTMXA

053 CONTAINER LENGTH JB.CONLENJB

054 CONTAINER TYPE JB.CONTYPJB

055 CONTRACT NUMBER XA.CONTNOXA, EA.CNTRNOEA,


JA.CONNUMJA

056 CONTRACTOR FURNISHED EQUIPMENT/GOVERNMENT EA.CFEGFEEA


FURNISHED EQUIPMENT (CFE/GFE)

057 CONTRACTOR RECOMMENDED EJ.CNTRECEJ, EL.CONRECEL


3E-7
DEF(AUST)5692

058 CONTRACTOR TECHNICAL INFORMATION CODE (CTIC) HA.CTICODHA

059 CONVERSION FACTOR BA.CONVFABA

060 COORDINATED TEST PLAN (CTP) UC.OTPCTPUC

061 COST PER RECORDER ACTION XA.CSREORXA

062 COST PER REQUISITION XA.CSPRRQXA

063 CREST ANGLE JC.CREANGJC

064 CREW SIZE AA.CREWSZAA

065 CRITICAL ITEM CODE HA.CRITITHA

066 CRITICALITY CODE HA.CRITCDHA

067 CUSHIONING AND DUNNAGE MATERIAL CODE HF.CUSHMAHF

068 CUSHIONING THICKNESS HF.CUSTHIHF

069 SUPPORT EQUIPMENT MANAGEMENT CODE EA.CUSTCDEA

070 DATA STATUS CODE HG.DATASCHG

071 DATE EA.DATFADEA, EF.INTSUBEF,


EF.DTGVDSEF, EF.DTRVSBEF,
JA.TRCHRDJA

072 DECK STOWAGE JB.SDECKSJB

073 DEFENSE LOGISTICS SERVICES CENTER SCREENING HA.DLSCRCHA


REQUIREMENT CODE

074 DEGREE OF PROTECTION CODE HF.DEGPROHF

075 DELIVERY SCHEDULE JA.DELSCHJA

076 DEMILITARIZATION CODE (DMIL) HA.DEMILIHA

077 DEMILITARIZATION COST XA.DEMILCXA

078 DESCRIPTION AND FUNCTION OF SUPPORT EE.SEQNAREE, EE.SENARCEE(B)


EQUIPMENT

079 DESIGN DATA CATEGORY CODE EJ.DSNDATEJ

080 DESIGN DATA PRICE EA.DSNPRCEA

081 DESIGNATED REWORK POINT (DRP) HG.DRPONEHG, HG.DRPTWOHG

082 DISASTER RESPONSE FORCE JF.TRANARJF, JF.TRANCDJF(M)

083 DISCOUNT RATE XA.DISCNTXA

084 DISPOSITION BF.RCMDSABF, BF.RCMDSBBF,


BF.RCMDSCBF, BF.RCMDSDBF,
BF.RCMDSEBF, BF.RCMDSFBF,
BF.RCMDSGBF, BF.RCMDSHBF,
BF.RCMDSIBF, BF.RCMDSJBF

085 DISTANCE AJ.SHPDISAJ

3E-8
DEF(AUST)5692

086 DOCUMENT AVAILABILITY CODE (DAC) HA.DOCAVCHA

087 DOCUMENT IDENTIFIER CODE (DIC) HA.DOCIDCHA

088 DRAWING CLASSIFICATION EA.DRWCLSEA, FA.DRCLASFA

089 DRAWING NUMBER FA.FADNUMFA

090 DUTY CJ.DUTIESCJ

091 DUTY CODE CJ.DUTYCDCJ, CK.DUTYCDCJ

092 DUTY POSITION REQUIRING A NEW OR REVISED SKILL GB.DPRNRSGB

093 ECONOMIC ANALYSIS EA.ECOANLEA

094 EDUCATIONAL QUALIFICATIONS GC.NMSNARGC, GC.NMSNCDGC(B)

095 ELEMENT INDICATOR CC.ELEMNTCC, RO.ELEMNTRO

096 END ITEM ACRONYM CODE (EIAC) XA.EIACODXA, XB.EIACODXA,


XC.EIACODXA, XD.EIACODXA,
XE.EIACODXA, XF.EIACODXA,
XG.EIACODXA

AA.EIACODXA, AB.EIACODXA,
AC.EIACODXA, AD.EIACODXA,
AE.EIACODXA, AF.EIACODXA,
AG.EIACODXA, AH.EIACODXA,
AI.EIACODXA, AJ.EIACODXA,
AK.EIACODXA

BA.EIACODXA, BB.EIACODXA,
BC.EIACODXA, BD.EIACODXA,
BE.EIACODXA, BF.EIACODXA,
BG.EIACODXA, BH.EIACODXA,
BI.EIACODXA, BJ.EIACODXA,
BK.EIACODXA, BL.EIACODXA

CA.EIACODXA, CA.REFEIACA,
CB.EIACODXA, CB.RFDEIACB,
CC.EIACODXA, CD.EIACODXA,
CE.EIACODXA, CF.EIACODXA,
CG.EIACODXA, CH.EIACODXA,
CI.EIACODXA, CK.EIACODXA

UA.EIACODXA, UB.EIACODXA,
UD.EIACODXA, UF.EIACODXA,
UG.EIACODXA, UH.EIACODXA,
UJ.EIACODXA, UL.EIACODXA

FE.EIACODXA, GE.EIACODXA

HG.EIACODXA, HH.EIACODXA,
HI.EIACODXA, HJ.EIACODXA,
HK.EIACODXA, HL.EIACODXA,
HN.EIACODXA, HO.EIACODXA,
HP.EIACODXA, HQ.EIACODXA,
HR.EIACODXA

JA.EIACODXA, JB.EIACODXA,
JC.EIACODXA, JD.EIACODXA,
JE.EIACODXA, JF.EIACODXA

MA.EIACODXA, MB.EIACODXA,
3E-9
DEF(AUST)5692

MC.EIACODXA, MD.EIACODXA,
ME.EIACODXA, MF.EIACODXA

RA.EIACODXA, RB.EIACODXA,
RD.EIACODXA, RE.EIACODXA,
RF.EIACODXA, RG.EIACODXA,
RI.EIACODXA, RJ.EIACODXA,
RL.EIACODXA, RM.EIACODXA,
RN.EIACODXA, RO.EIACODXA,
RP.EIACODXA

VA.EIACODXA, VE.EIACODXA,
VF.EIACODXA, VR.EIACODXA,
VS.EIACODXA, VT.EIACODXA,
WB.EIACODXA, WC.EIACODXA,
WH.EIACODXA, WJ.EIACODXA,
WK.EIACODXA, WM.EIACODXA,
WN.EIACODXA, WO.EIACODXA,
WP.EIACODXA, WQ.EIACODXA,
WR.EIACODXA, WS.EIACODXA,
WT.EIACODXA, WY.EIACODXA,
WY.WACEIAWY; ZL.EIACODXA

097 ENGINEERING FAILURE MODE MEAN TIME BETWEEN BF.EFMTBFBF


FAILURE (EFM-MTBF)

098 ENVIRONMENTAL HANDLING AND TRANSPORTATION JA.ENHATCJA


INDICATOR

099 ENVIRONMENTAL/HAZARDOUS MATERIALS JF.TRANARJF, JF.TRANCDJF(I)


CONSIDERATIONS

100 ESSENTIALITY CODE HG.ESSCODHG

101 ESTIMATED PRICE EJ.ESTPRCEJ, EL.ESTPRCEL

102 ESTIMATED SALVAGE VALUE XA.ESSALVXA

103 EXTENDED UNIT PRICE EA.EXUNPREA

104 EXTERNAL OR INTERNAL LOAD INDICATOR JB.EOILINJB

105 FACILITIES DESIGN CRITERIA FD.NMFNARFD, FD.NMFNCDFD(A)

106 FACILITIES INSTALLATION LEAD TIME FD.NMFNARFD, FD.NMFNCDFD(B)

107 FACILITIES MAINTENANCE REQUIREMENTS FC.FABNARFC, FC.FBNACDFC(A)

108 FACILITIES REQUIREMENTS FD.NMFNARFD, FD.NMFNCDFD(E)

109 FACILITIES REQUIREMENTS FOR OPERATIONS FC.FABNARFC, FC.FBNACDFC(B)

110 FACILITIES REQUIRED FOR TRAINING FC.FABNARFC, FC.FBNACDFC(C)

111 FACILITIES UTILIZATION FD.NMFNARFD, FD.NMFNCDFD(D)

112 FACILITY AREA FA.FAAREAFA

113 FACILITY BASELINE NARRATIVE CODE FC.FBNACDFC

114 FACILITY CAPABILITY FB.FACNARFB, FB.FNCODEFB(A)

115 FACILITY CATEGORY CODE FA.FACCCDFA, FB.FACCCDFA,


FC.FACCCDFC, FD.FACCCDFD,
FE.FACCCDFA, MD.FACCCDFA,
3E-10
DEF(AUST)5692

VC.FACCCDFA, VE.FACCCDFA,
WQ.FACCCDFA

116 FACILITY CLASSES FA.FACCLAFA

117 FACILITY LOCATION FB.FACNARFB, FB.FNCODEFB(B)

118 FACILITY NAME FA.FACNAMFA, FB.FACNAMFA,


FC.FACNAMFC, FD.FACNAMFD,
FE.FACNAMFA

MD.FACNAMFA, VC.FACNAMFA,
VE.FACNAMFA, WQ.FACNAMFA

119 FACILITY NARRATIVE CODE FB.FNCODEFB

120 FACILITY REQUIREMENTS: SPECIAL CONSIDERATIONS FC.FABNARFC, FC.FBNACDFC(D)

121 FACILITY REQUIREMENTS: SUPPLY/STORAGE FC.FABNARFC, FC.FBNACDFC(E)

122 FACILITY TASK AREA BREAKDOWN FD.NMFNARFD, FD.NMFNCDFD(C)

123 FACILITY UNIT COST RATIONALE FD.NMFNARFD, FD.NMFNCDFD(F)

124 FAILURE CAUSE BG.FMNNARBG, BG.FMNCNABG(D)

125 FAILURE/DAMAGE EFFECTS: END EFFECT BG.FMNNARBG, BG.FMNCNABG(A)

126 FAILURE/DAMAGE EFFECTS: LOCAL BG.FMNNARBG, BG.FMNCNABG(B)

127 FAILURE/DAMAGE EFFECTS: NEXT HIGHER BG.FMNNARBG, BG.FMNCNABG(C)

128 FAILURE/DAMAGE MODE BG.FMNNARBG, BG.FMNCNABG(E)

129 FAILURE DETECTION METHOD BG.FMNNARBG, BG.FMNCNABG(F)

130 FAILURE EFFECT PROBABILITY (B) BI.FEPROBBI

131 FAILURE MODE & RELIABILITY CENTERED BG.FMNCNABG


MAINTENANCE (RCM) NARRATIVE CODE

132 FAILURE MODE CLASSIFICATION BF.FMCLASBF

133 FAILURE MODE CRITICALITY NUMBER (Cm) BI.FACRNUBI

134 FAILURE MODE INDICATOR BF.FAMOINBF, BG.FAMOINBF,


BH.FAMOINBH, BI.FAMOINBF,
BJ.FAMOINBF

RI.FAMOINBF, RI.REFFMIRI,
VF.FAMOINBF

135 FAILURE MODE INDICATOR MISSION PHASE BJ.FMMPCNBJ


CHARACTERISTICS NARRATIVE CODE

136 FAILURE MODE RATIO (a) BF.FMRATOBF

137 FAILURE MODE REMARKS BG.FMNNARBG, BG.FMNCNABG(H)

138 FAILURE PREDICTABILITY BG.FMNNARBG, BG.FMNCNABG(G)

139 FAILURE PROBABILITY LEVEL BI.FPROBLBI

140 FAILURE RATE BD.FAILRTBD

3E-11
DEF(AUST)5692

141 FAILURE RATE DATA SOURCE BA.FRDATABA

142 FAMILY GROUP EA.FAMGRPEA

143 FAULT ISOLATION BA.FIAMBABA, BA.FIPFGABA,


BA.FIAMBBBA, BA.FIPFGBBA

UH.UUTFA1UH, UH.UUTFA2UH,
UH.UUTFP1UH, UH.UUTFP2UH

144 FIGURE NUMBER HJ.FIGNUMHK, HK.FIGNUMHK,


HL.FIGNUMHK

145 FISCAL YEAR (FY) HD.FISCYRHD, HE.FISCYRHE,


JE.TRAFYRJE

146 FREIGHT CLASSIFICATION JB.FRCLASJB

147 FUNCTIONAL ANALYSIS EE.SEQNAREE, EE.SENARCEE(A)

148 SUPPORT EQUIPMENT GENERIC CODE EA.GENECDEA

149 GOVERNMENT DESIGNATOR EA.GOVDESEA, UK.ATEGDSUK

150 GOVERNMENT REQUIRED EJ.GOVRQDEJ, EL.GOVRQDEL

151 HARDNESS CRITICAL ITEM (HCI) HG.HARDCIHG

152 HARDNESS CRITICAL PROCESS (HCP) CA.HRDCPCCA

153 HARDWARE DEVELOPMENT PRICE EA.HDWRPREA

154 HAZARDOUS CODE HA.HAZCODHA

155 HAZARDOUS MAINTENANCE PROCEDURES CODE CA.HAZMPCCA

156 HAZARDOUS MATERIALS STORAGE COST HA.HMSCOSHA

157 HAZARDOUS WASTE DISPOSAL COST HA.HWDCOSHA

158 HAZARDOUS WASTE STORAGE COST HA.HWSCOSHA

159 HELICOPTER MISSION REQUIREMENTS JB.HMATLRJB, JB.HMDISRJB,


JB.HMPAYRJB, JB.HMTMPRJB,
JB.HMTIMRJB

160 HOLDING COST PERCENTAGE XA.HLCSPCXA

161 HOURLY LABOUR RATE PER SSC GA.HRLARTGA

162 INDENTURE CODE HG.INDCODHG

163 INDUSTRIAL MATERIAL ANALYSIS OF CAPACITY (IMAC) HA.INDMATHA

164 INHERENT AVAILABILITY (Ai) AA.INHAVAAA, BD.INHAVABD

165 INHERENT MAINTENANCE FACTOR BD.INHMAFBD

166 INITIAL BIN COST XA.INTBINXA

167 INITIAL CATALOGUING COST XA.INCATCXA

168 INPUT POWER SOURCE EI.IPSOPNEI, EI.IPACDCEI,


EI.IPFRMXEI, EI.IPRGMXEI,
EI.IPSRGMEI, EI.IPOPRGEI,
3E-12
DEF(AUST)5692

EI.IPMXRPEI, EI.IPPHASEI,
EI.IPPOWREI

169 INSTALLATION FACTORS OR OTHER FACILITIES EE.SEQNAREE, EE.SENARCEE(E)

170 INTEGRATED LOGISTIC SUPPORT PRICE EA.ILSPRCEA

171 INTEGRATED LOGISTIC SUPPORT REQUIREMENTS EL.IRCCODEL


CATEGORY CODE

172 INTERCHANGEABILITY CODE EK.ICCODEEK, HP.INTCHCHP

173 INTEREST RATE XA.INTRATXA

174 INTERMEDIATE CONTAINER CODE HF.INTCONHF

175 INTERMEDIATE CONTAINER QUANTITY HF.INCQTYHF

176 INVENTORY STORAGE SPACE COST XA.INVSTGXA

177 ITEM CATEGORY CODE (ICC) EA.SEICCDEA, HG.ITMCATHG

178 ITEM CRITICALITY NUMBER (Cr) BK.RICRITBK

179 ITEM DESIGNATOR CODE XC.ITMDESXC, EA.ENDARTEA,


EM.GFAEIDEM

180 ITEM FUNCTION BB.RAMNARBB, BB.RAMCNABB(A)

181 ITEM MANAGEMENT CODE (IMC) HA.ITMMGCHA

182 ITEM NAME AH.IONAMEAH, EK.SUPITNEK,


HA.ITNAMEHA

183 ITEM NAME CODE HA.INAMECHA

184 ITEM NUMBER HJ.ITEMNOHK, HK.ITEMNOHK,


HL.ITEMNOHK

185 JOB CJ.JOBDESCJ

186 JOB CODE CJ.JOBCODCJ, CK.JOBCODCJ

187 JULIAN DATE HF.SPDATEHF

188 JUSTIFICATION EE.SEQNAREE, EE.SENARCEE(H),


FD.NMFNARFD, FD.NMFNCDFD(G),
GC.NMSNARGC, GC.NMSNCDGC(C)

189 LABOR RATE AI.LABRATAI

190 LIFE CYCLE STATUS EA.LICYSTEA

191 LIFE SPAN EA.LIFSPNEA

192 LIFTING AND TIEDOWN REQUIREMENT FOR JF.TRANARJF, JF.TRANCDJF(B)


TRANSPORTATION

193 LINE ITEM NUMBER (LIN) HA.LINNUMHA

194 LINE REPLACEABLE UNIT (LRU) HG.LRUNITHG

195 LOADING FACTOR XA.LODFACXA

196 LOGISTIC CONSIDERATIONS BA.LOGSTABA, BA.LOGACCBA,


3E-13
DEF(AUST)5692

BA.LOGMAIBA, BA.LOGSAFBA,
BA.LOGTEPBA, BA.LOGSKIBA,
BA.LOGTRABA, BA.LOGCONBA,
BA.LOGPATBA, BA.LOGFLOBA,
BA.LOGLABBA, BA.LOGDSPBA,
BA.LOGCRCBA

197 LOGISTIC CONTROL CODE EA.LGCTCDEA

198 LOGISTICS DECISION OFFICE EA.LGDCOFEA

199 LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER XB.LSACONXB, XC.LSACONXB,


(LCN) XD.LSACONXB, XE.LSACONXE,
XE.LCNSEIXE, XF.LSACONXF,
XF.LCNSEIXF, XG.PLSACNXG,
XG.FLSACNXG

AA.LSACONXB, AB.LSACONXB,
AC.LSACONXB, AD.LSACONXB,
AE.LSACONXB, AF.LSACONXB,
AG.LSACONXB, AH.LSACONXB,
AJ.LSACONXB, AK.LSACONXB

BA.LSACONXB, BB.LSACONXB,
BC.LSACONXB, BD.LSACONXB,
BE.LSACONXB, BF.LSACONXB,
BG.LSACONXB, BH.LSACONBH,
BH.TLSACNBH, BI.LSACONXB,
BJ.LSACONXB, BK.LSACONXB

CA.LSACONXB, CA.REFLCNCA,
CA.AORLCNCA, CB.LSACONXB,
CB.RFDLCNCB, CC.LSACONXB,
CD.LSACONXB, CF.LSACONXB,
CG.LSACONXB, CH.LSACONXB,
CI.TSKLCNCI, CI.PROLCNCI,
CK.LSACONXB

UA.UUTLCNUA, UB.UUTLCNUA,
UD.UUTLCNUA, UF.UUTLCNUA,
UG.UUTLCNUA, UH.TSKLCNCI,
UH.PROLCNCI, UJ.UUTLCNUA,
UL.UUTLCNUA

FE.LSACONXB, GE.LSACONXB

HG.LSACONXB, HH.LSACONXB,
HI.LSACONXB, HJ.LSACONXB,
HK.LSACONXB, HL.LSACONXB,
HN.LSACONHN, HN.LCNSEIHN,
HO.LSACONHO, HO.LCNSEIHO,
HP.LSACONXB, HQ.LSACONXB,
HR.LSACONHO, HR.LCNSEIHO

JA.LSACONXB, JB.LSACONXB,
JC.LSACONXB, JD.LSACONXB,
JE.LSACONXB, JF.LSACONXB

MA.LSACONXB, MB.LSACONXB,
MC.LSACONXB, MD.LSACONXB,
ME.LSACONXB, MF.LSACONXB

RA.LSACONXB, RB.LSACONXB,
RD.LSACONXB, RD.INTLCNRD,
RE.LSACONXB, RE.INTLCNRE,
3E-14
DEF(AUST)5692

RF.LSACONXB, RG.LSACONXB,
RI.LSACONXB, RI.REFLCNRI,
RJ.LSACONXB, RL.LSACONXB,
RL.MPTLCNRL, RM.LSACONXB,
RN.LSACONXB, RO.LSACONXB,
RP.LSACONXB, RP.SSTLCNRP

VA.LSACONXB, VE.LSACONXB,
VF.LSACONXB, VT.LSACONXB,
WB.LSACONXB, WC.LSACONXB,
WH.LSACONXB, WJ.LSACONXB,
WK.LSACONXB, WN.LSACONXB,
WO.SRVLCNWO, WP.LSACONXB,
WQ.LSACONXB, WR.LSACONXB,
WS.LSACONXB, WT.LSACONXB,
WT.SRVLCNWO, WY.LSACONXB,
WY.WACLCNWY, ZL.ALTLCNZL

200 LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER- XB.LCNINDXB


INDENTURE CODE (LCN-IC)

201 LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER XB.LCNAMEXB


(LCN) NOMENCLATURE

202 LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER XA.LCNSTRXA


STRUCTURE (LCN STRUCTURE)

203 LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER XB.LCNTYPXB, XC.LCNTYPXB,


TYPE (LCN-TYPE) XD.LCNTYPXB, XE.LCNTYPXE,
XE.LTYSEIXE, XF.LCNTYPXF,
XF.LTYSEIXF, XG.PLCNTYXG,
XG.FLCNTYXG

AA.LCNTYPXB, AB.LCNTYPXB,
AC.LCNTYPXB, AD.LCNTYPXB,
AE.LCNTYPXB, AF.LCNTYPXB,
AG.LCNTYPXB, AH.LCNTYPXB,
AJ.LCNTYPXB, AK.LCNTYPXB

BA.LCNTYPXB, BB.LCNTYPXB,
BC.LCNTYPXB, BD.LCNTYPXB,
BE.LCNTYPXB, BF.LCNTYPXB,
BG.LCNTYPXB, BH.LCNTYPBH,
BH.TLCNTYBH, BI.LCNTYPXB,
BJ.LCNTYPXB, BK.LCNTYPXB

CA.LCNTYPXB, CA.REFTYPCA,
CA.AORTYPCA, CB.LCNTYPXB,
CB.RFDTYPCB, CC.LCNTYPXB,
CD.LCNTYPXB, CF.LCNTYPXB,
CG.LCNTYPXB, CH.LCNTYPXB,
CI.TSKLTYCI, CI.PROLTYCI,
CK.LCNTYPXB

UA.UTLCNTUA, UB.UTLCNTUA,
UD.UTLCNTUA, UF.UTLCNTUA,
UG.UTLCNTUA, UH.TSKLTYCI,
UH.PROLTYCI, UJ.UTLCNTUA,
UL.UTLCNTUA

FE.LCNTYPXB, GE.LCNTYPXB

HG.LCNTYPXB, HH.LCNTYPXB,
HI.LCNTYPXB, HJ.LCNTYPXB,
HK.LCNTYPXB, HL.LCNTYPXB,
3E-15
DEF(AUST)5692

HN.LCNTYPXB, HO.LCNTYPXB,
HP.LCNTYPXB, HQ.LCNTYPXB,
HR.LCNTYPXB

JA.LCNTYPXB, JB.LCNTYPXB,
JC.LCNTYPXB, JD.LCNTYPXB,
JE.LCNTYPXB, JF.LCNTYPXB

MA.LCNTYPXB, MB.LCNTYPXB,
MC.LCNTYPXB, MD.LCNTYPXB,
ME.LCNTYPXB, MF.LCNTYPXB

RA.LCNTYPXB, RB.LCNTYPXB,
RD.LCNTYPXB, RD.INTLTYRD,
RE.LCNTYPXB, RE.INTLTYRE,
RF.LCNTYPXB, RG.LCNTYPXB,
RI.LCNTYPXB, RI.REFLTYRI,
RJ.LCNTYPXB, RL.LCNTYPXB,
RL.MPTLTYRL, RM.LCNTYPXB,
RN.LCNTYPXB, RO.LCNTYPXB,
RP.LCNTYPXB, RP.SSTLTYRP

VA.LCNTYPXB, VE.LCNTYPXB,
VF.LCNTYPXB, VT.LCNTYPXB,
WB.LCNTYPXB, WC.LCNTYPXB,
WH.LCNTYPXB, WJ.LCNTYPXB,
WK.LCNTYPXB, WN.LCNTYPXB,
WO.SRVLTYWO, WP.LCNTYPXB,
WQ.LCNTYPXB, WR.LCNTYPXB,
WS.LCNTYPXB, WT.LCNTYPXB,
WT.SRVLTYWO, WY.LCNTYPXB,
WY.WACLTYWY, ZL.LCNTYPZL

204 LOGISTIC SUPPORT ANALYSIS RECOMMENDATION EA.LSARCDEA


CODE

205 LOT QUANTITY HD.LOTQFMHD, HD.LOTQTOHD,


HE.LOTQFMHE, HE.LOTQTOHE

206 MAINTENANCE ACTION CODE (MAC) HG.MAIACTHG

207 MAINTENANCE CONCEPT BB.RAMNARBB, BB.RAMCNABB(B)

208 MAINTENANCE INTERVAL BH.MAININBH

209 MAINTENANCE PLAN NUMBER UA.UMNTPLUA, UM.MNTPLNUM

210 MAINTENANCE PLAN RATIONALE BB.RAMNARBB, BB.RAMCNABB(E)

211 MAINTENANCE REPLACEMENT RATE I (MRRI) HG.MRRONEHG

212 MAINTENANCE REPLACEMENT RATE II (MRRII) HG.MRRTWOHG

213 MAINTENANCE REPLACEMENT RATE MODIFIER (MRR HG.MRRMODHG


MOD)

214 MAINTENANCE TASK DISTRIBUTION HG.OMTDOOHG, HG.FMTDFFHG,


HG.HMTDHHHG, HG.LMTDLLHG,
HG.DMTDDDHG, HG.CBDMTDHG,
HG.CADMTDHG

215 MAN-HOUR PER OPERATING HOUR AC.MLSMHOAC, AC.MLUMHOAC

216 MANAGEMENT PLAN EA.MGTPLNEA

3E-16
DEF(AUST)5692

217 MANAGING COMMAND/AGENCY EA.MGCOATEA

218 MATERIAL HA.MATERLHA

219 MATERIAL LEADTIME HA.MTLEADHA

220 MATERIAL WEIGHT HA.MTLWGTHA

221 MAXIMUM ALLOWABLE OPERATING TIME (MAOT) HG.MAOTIMHG

222 MAXIMUM TIME TO REPAIR (MAXTTR) AA.MAXTTRAA, AC.MLMTTRAC,


BD.MAXTTRBD

223 MEAN ACTIVE MAINTENANCE DOWNTIME (MAMDT) AA.OMAMDTAA, AA.TMAMDTAA

224 MEAN ELAPSED TIME CA.MSDMETCA, CA.PRDMETCA

225 MEAN MAN-HOURS CA.MSDMMHCA, CA.PRDMMHCA

226 MEAN MAN-MINUTES CD.SUBMMMCD

227 MEAN MINUTE ELAPSED TIME CB.SBMMETCB

228 MEAN MISSION DURATION AB.MMISDUAB

229 MEAN TIME BETWEEN FAILURE (MTBF) AG.OPMTBFAG, AG.TEMTBFAG,


BD.OPMTBFBD, BD.TEMTBFBD,
EA.SEMTBFEA

230 MEAN TIME BETWEEN MAINTENANCE ACTIONS AG.OPMRBMAG, AG.TMTBMAAG,


(MTBMA) BD.OMTBMABD, BD.TMTBMABD,
EA.SMTBMAEA

231 MEAN TIME BETWEEN MAINTENANCE INDUCED (MTBM BD.INMTBMBD


INDUCED)

232 MEAN TIME BETWEEN MAINTENANCE INHERENT BD.INHMTBBD


(MTBM INHERENT)

233 MEAN TIME BETWEEN MAINTENANCE NO DEFECT BD.NOMTBMBD


(MTBM NO DEFECT)

234 MEAN TIME BETWEEN PREVENTIVE MAINTENANCE BD.MTBMPVBD


(MTBPM)

235 MEAN TIME BETWEEN REMOVALS (MTBR) AG.MTBRXXAG, BD.MTBRXXBD

236 MEAN TIME TO REPAIR (MTTR) AA.OPMTTRAA, AA.TEMTTRAA,


BD.MTTROPBD, BD.MTTRTHBD,
EA.SEMTTREA

237 MEANS OF DETECTION CA.PMDTECCA, CA.SMDTECCA

238 MEASUREMENT BASE (MB) AB.MMISDMAB, AG.MEASBSAG,


BA.WOLIMBBA, BD.FARAMBBD,
BD.OMTBFMBD, BD.TMTBFMBD,
BD.OMTBMMBD, BD.TMTBMMBD,
BD.IMTBMMBD, BD.INHMTMBD,
BD.NMTBMMBD, BD.MTBMPMBD,
BD.MTBRMBBD, BF.EFMMMBBF,
BH.MAINMBBH, BI.FMOTMBBI,
CA.AORMSBCA, VE.TSKTMBVE

239 METHOD OF PRESERVATION HF.MEPRESHF

3E-17
DEF(AUST)5692

240 MILITARY DISTANCE CLASSIFICATION JF.TRANARJF, JF.TRANCDJF(J)

241 MILITARY LOAD CLASSIFICATION (EMPTY/LOADED) JC.HICLNEJC, JC.HICLNLJC

242 MILITARY UNIT TYPE JA.MILUNTJA

243 MINIMUM EQUIPMENT LIST INDICATOR BA.MEQLINBA

244 MINIMUM EQUIPMENT LIST NARRATIVE BB.RAMNARBB, BB.RAMCNABB(C)

245 MINIMUM REPLACEMENT UNIT (MRU) HG.MINREUHG

246 MISSION PHASE CODE (MPC) BI.MISSPCBL, BJ.MISSPCBL,


BK.MISSPCBL, BL.MISSPCBL,
VS.MISSPCBL

247 MISSION PHASE/OPERATIONAL MODE BL.MPOPLDBL

248 MOBILE FACILITY CODE EA.MOBFACEA

249 MOBILITY TYPE JC.MOBTYPJC, JD.MOBTYPJC

250 MODEL LOAD (HIGHWAY) JB.HIPRMLJB, JB.HALTMLJB

251 MODEL TYPE (HIGHWAY) JB.HIPRMTJB, JB.HALTMTJB

252 MODIFICATION OR CHANGE EA.MODCHGEA

253 NATIONAL STOCK NUMBER AND RELATED DATA AH.IONIINAH, AH.IONFSCAH,


EH.ALTFSCEH, EH.ALTNIIEH,
HA.COGNSNHA, HA.SMMNSNHA,
HA.MATNSNHA, HA.FSCNSNHA,
HA.NIINSNHA, HA.ACTNSNHA,
HF.CONNSNHF

254 NET EXPLOSIVE WEIGHT JA.NETEXWJA

255 NEW OR MODIFIED FACILITY NARRATIVE CODE FD.NMFNCDFD

256 NEW OR MODIFIED SKILL NARRATIVE CODE GC.NMSNCDGC

257 NEW OR MODIFIED SKILL SPECIALITY CODE (SSC) CD.MDCSSCGB, GB.MDCSSCGB,


GC.MDCSSCGB, GD.MDCSSCGB,
GE.MDCSSCGB

258 NEXT HIGHER ASSEMBLY PROVISIONING LIST ITEM HH.NHAPLIHH


SEQUENCE NUMBER (NHA PLISN)

259 NEXT HIGHER ASSEMBLY PROVISIONING LIST ITEM HH.NHAINDHH


SEQUENCE NUMBER INDICATOR (NHA-IND)

260 NON OPERABILITY FRAGILITY FACTOR (NOFF) JA.NOPRFFJA

261 NOT REPAIRABLE THIS STATION (NRTS) HG.NORETSHG

262 NUMBER OF OPERATING LOCATIONS AA.NUOPLOAA

263 NUMBER OF SHOPS AI.NOSHPSAI

264 NUMBER OF SKIDS JC.SNUMSKJC

265 NUMBER OF SYSTEMS SUPPORTED AC.MLNSSUAC

266 NUMBER TYPE AH.IOINTYAH

3E-18
DEF(AUST)5692

267 OPERATING AND SUPPORT COST EA.OSCOSTEA

268 OPERATING DIMENSIONS EA.OPRHGTEA, EA.OPLENGEA,


EA.OPWIDTEA

269 OPERATING TIME BI.FMOPTIBI

270 OPERATING WEIGHT EA.OPRWGTEA

271 OPERATION LEVEL XA.WSOPLVXA

272 OPERATION LIFE XA.OPRLIFXA

273 OPERATIONAL AVAILABILITY (Ao) AB.OPAVAIAB, BE.OPAVAIBE

274 OPERATIONAL MISSION FAILURE DEFINITION AK.SEINARAK, AK.SEINCDAK(C)

275 OPERATIONAL REQUIREMENT INDICATOR AB.OPRQINAB, AC.OPRQINAB,


AD.OPRQINAB, AE.OPRQINAB,
AF.OPRQINAB, AG.OPRQINAG,
BE.OPRQINBE

276 OPERATIONAL WEIGHT (EMPTY AND LOADED) JC.OPWEEMJC, JC.OPWELDJC

277 OPERATIONS/MAINTENANCE (O/M) LEVEL AC.OMLVLCAC, AD.OMLVLCAC,


AE.OMLVLCAC, AI.OMLVLCAI,
AJ.OMLVLFAJ, AJ.OMLVLTAJ,
EA.PCBLVLEA, EA.CALLVLEA,
EA.RPRLVLEA

278 OPERATOR'S MANUAL EA.OPRMANEA

279 OPTIONAL PROCEDURE INDICATOR HF.OPTPRIHF

280 ORGANIZATIONAL/ON EQUIPMENT/UNIT OPERATIONS AD.DINMETAD, AD.DINMMHAD,


AND MAINTENANCE REQUIREMENTS AD.PREMETAD, AD.PREMMHAD,
AD.POIMETAD, AD.POIMMHAD,
AD.PINMETAD, AD.PINMMHAD,
AD.MPCMETAD, AD.MPCMMHAD,
AD.TINMETAD, AD.TINMMHAD

281 OVERHAUL REPLACEMENT RATE (ORR) HH.OVHREPHH

282 PACKAGING CATEGORY CODE HF.PACCATHF

283 PACKING CODE HF.PKGCODHF

284 PARAMETERS EC.PARGPCEC, EC.PARPAREC,


EC.RNGFRMEC, EC.RNGTOCEC,
EC.PARACCEC, EC.SPARIOEC,
EC.PARRVCEC

UG.UUTPGCUG, UG.UUTPACUG,
UG.UUTPIOUG, UG.UUTPSOUG,
UG.UUTPARUG, UG.UUTPRFUG,
UG.UUTPRTUG, UG.UUTPRVUG,
UN.SEUPGCUN, UN.UTPAACUN,
UN.UTPAIOUN, UN.UTPAPAUN,
UN.UTRGFRUN, UN.UTPRRTUN,
UN.UTPARVUN

285 PASS THROUGH PRICE EA.PASTHREA

286 PERCENTILE AA.PERCENAA, AC.MLPERCAC,


BD.PERCENBD
3E-19
DEF(AUST)5692

287 PERFORMANCE STANDARDS CA.PRSTDACA, CA.PRSTDBCA,


CA.PRSTDCCA

288 PERSON IDENTIFIER CD.SUBPIDCD, CK.SUBPIDCD,


GE.SUBPIDCD

289 PERSONNEL TURNOVER RATE XA.PRSTOVXA, XA.PRSTOMXA

290 PHYSICAL AND MENTAL REQUIREMENTS GE.PAMENRGE

291 PHYSICAL SECURITY/PILFERAGE CODE HA.PHYSECHA

292 PILOT REWORK/OVERHAUL CANDIDATE BA.PREOVCBA

293 PRECIOUS METAL INDICATOR CODE (PMIC) HA.PMICODHA

294 PREPARING ACTIVITY EA.PREATYEA

295 PRESERVATION MATERIAL CODE HF.PRSMATHF

296 PREVENTIVE MAINTENANCE CHECKS AND SERVICES CA.PMCSIDCA


(PMCS) INDICATOR CODE

297 PRIOR ITEM PROVISIONING LIST ITEM SEQUENCE HG.PIPLISHG


NUMBER (PRIOR ITEM PLISN)

298 PROCUREMENT QUANTITY JE.FIQPQTJE, JE.SQPQTYJE,


JE.TQPQTYJE, JE.FQPQTYJE

299 PRODUCTION LEAD TIME (PLT) HA.PRDLDTHA

300 PRODUCTIVITY FACTOR XA.PROFACXA

301 PROGRAM ELEMENT EA.PROELEEA

302 PROGRAM PARTS SELECTION LIST (PPSL) HA.PPSLSTHA

303 PROGRAM SUPPORT INVENTORY CONTROL POINT EA.PSICPOEA

304 PROPER SHIPPING NAME JA.PROPSNJA

305 PRORATED EXHIBIT LINE ITEM NUMBER (PRORATED HP.PROELIHP


ELIN)

306 PRORATED QUANTITY HP.PROQTYHP

307 PROVISIONING CONTRACT CONTROL NUMBER (PCCN) XC.PCCNUMXC

308 PROVISIONING LIST CATEGORY CODE (PLCC) HA.AAPLCCHA, HA.BBPLCCHA,


HA.CCPLCCHA, HA.DDPLCCHA,
HA.EEPLCCHA, HA.FFPLCCHA,
HA.GGPLCCHA, HA.HHPLCCHA,
HA.JJPLCCHA, HA.KKPLCCHA,
HA.LLPLCCHA, HA.MMPLCCHA

309 PROVISIONING LIST ITEM SEQUENCE NUMBER (PLISN) XC.PLISNOXC, HG.PLISNOHG

310 PROVISIONING NOMENCLATURE HL.PROVNOHL

311 PROVISIONING REMARKS HI.REMARKHI

312 PROVISIONING SYSTEM IDENTIFIER CODE HG.PROSICHG

313 PROVISIONING TECHNICAL DOCUMENTATION HG.LLIPTDHG, HG.PPLPTDHG,


3E-20
DEF(AUST)5692

SELECTION CODE HG.SFPPTDHG, HG.CBLPTDHG,


HG.RILPTDHG, HG.ISLPTDHG,
HG.PCLPTDHG, HG.TTLPTDHG,
HG.SCPPTDHG, HG.ARAPTDHG,
HG.ARBPTDHG

314 PROVISIONING UNIT OF MEASURE/ISSUE PRICE CODE HD.PROUIPHD, HE.PROUMPHE

315 QUALITATIVE & QUANTITATIVE MAINTAINABILITY BB.RAMNARBB, BB.RAMCNABB(D)


REQUIREMENTS

316 QUANTITY PER ASSEMBLY (QTY/ASSY) XC.QTYASYXC, HG.QTYASYHG

317 QUANTITY PER END ITEM (QTY/EI) XC.QTYPEIXC, HG.QTYPEIHG

318 QUANTITY PER FIGURE HK.QTYFIGHK

319 QUANTITY PER TASK CG.SQTYTKCG, CI.PQTYTKCI

320 QUANTITY PER TEST EM.QTYTSTEM

321 QUANTITY PER UNIT PACK HF.QTYUPKHF

322 QUANTITY PROCURED HP.QTYPROHP

323 QUANTITY SHIPPED HP.QTYSHPHP

324 QUANTITY SKILL SPECIALITY CODE AVAILABLE AE.QTYAVAAE

325 RAIL TRANSPORTATION COUNTRY JB.RAILTCJB

326 RAIL USE JB.RAILUSJB

327 REASON FOR SUPERSEDURE/DELETION EK.REASUPEK

328 RECOMMENDED INITIAL SYSTEM STOCK BUY HG.RISSBUHG

329 RECOMMENDED MINIMUM SYSTEM STOCK LEVEL HG.RMSSLIHG

330 RECOMMENDED RANK/RATE/PAY PLAN/GRADE GB.RPPCIVGB, GB.RPPMILGB

331 RECOMMENDED TENDER LOAD LIST QUANTITY (RTLL) HG.RTLLQTHG

332 RECURRING EA.RCURCSEA

333 RECURRING BIN COST XA.RCBINCXA

334 RECURRING CATALOGING COST XA.RCCATCXA

335 REFERENCE DESIGNATION HJ.REFDESHJ

336 REFERENCE DESIGNATION CODE (RDC) HJ.RDCODEHJ

337 REFERENCE NUMBER AH.IOREFNAH, CG.TSREFNCG,


CI.PROREFCI, EA.SEREFNEA,
EB.SEREFNEA, EC.SEREFNEA,
ED.SEREFNEA, EE.SEREFNEA,
EF.SEREFNEA, EG.SEREFNEA,
EH.SEREFNEA, EI.SEREFNEA,
EJ.SEREFNEA, EK.SEREFNEA,
EK.SPRREFEK, EL.SEREFNEA,
EM.SEREFNEA, EM.SREFNOEM

UB.SEREFNEA, UC.OTPREFUC,
UD.SEREFNEA, UD.OTPREFUC,
3E-21
DEF(AUST)5692

UE.OTPREFUC, UE.TPIREFUE,
UG.SEREFNEA, UH.PROREFCI,
UH.SEREFNEA, UI.AIDREFUI,
UJ.SEREFNEA, UJ.AIDREFUI,
UK.ATEREFUK, UL.SEREFNEA,
UL.ATEREFUK, UM.SUTREFUM,
UN.TGSREFUN, UN.SUTREFUM

HA.REFNUMHA, HB.REFNUMHB,
HC.REFNUMHC, HD.REFNUMHA,
HE.REFNUMHA, HF.REFNUMHA,
HG.REFNUMHA, HH.REFNUMHA,
HI.REFNUMHA, HJ.REFNUMHA,
HK.REFNUMHA, HL.REFNUMHA,
HM.REFNUMHA, HN.REFNUMHN,
HO.REFNUMHO, HP.REFNUMHA,
HQ.REFNUMHA, HR.REFNUMHO

VA.REFNUMHA, VD.REFNUMHA,
RH.REFNUMHA, WE.REFNUMWE,
WF.REFNUMWF, WI.REFNUMWF,
WI.REFNUMWE, WJ.REFNUMWF,
WJ.REFNUMWE, WK.REFNUMWE,
WK.REFNUMWF, WY.REFNUMWF

338 REFERENCE NUMBER CATEGORY CODE (RNCC) HA.REFNCCHA, HB.ADRNCCHB

339 REFERENCE NUMBER VARIATION CODE (RNVC) HA.REFNVCHA, HB.ADRNVCHB

340 REGULATORY REQUIREMENTS JF.TRANARJF, JF.TRANCDJF(D)

341 RELIABILITY AVAILABILITY MAINTAINABILITY BB.RAMCNABB


CHARACTERISTICS NARRATIVE CODE

342 RELIABILITY AVAILABILITY MAINTAINABILITY (RAM) XB.RAMINDXB


INDICATOR

343 RELIABILITY-CENTRED MAINTENANCE AGE BG.FMNNARBG, BG.FMNCNABG(J)


EXPLORATION

344 RELIABILITY CENTRED MAINTENANCE LOGIC RESULTS BF.RCMR01BF, BF.RCMR02BF,


BF.RCMR03BF, BF.RCMR04BF,
BF.RCMR05BF, BF.RCMR06BF,
BF.RCMR07BF, BF.RCMR08BF,
BF.RCMR09BF, BF.RCMR10BF,
BF.RCMR11BF, BF.RCMR12BF,
BF.RCMR13BF, BF.RCMR14BF,
BF.RCMR15BF, BF.RCMR16BF,
BF.RCMR17BF, BF.RCMR18BF,
BF.RCMR19BF, BF.RCMR20BF,
BF.RCMR21BF, BF.RCMR22BF,
BF.RCMR23BF, BF.RCMR24BF,
BF.RCMR25BF

345 RELIABILITY CENTRED MAINTENANCE LOGIC UTILIZED AA.RCMLOGAA

346 RELIABILITY CENTRED MAINTENANCE REASONING BG.FMNNARBG, BG.FMNCNABG(K)

347 RELIABILITY/MAINTAINABILITY INDICATOR CODE BD.RAMINDBD, BE.RAMINDBD

348 REMAIN-IN-PLACE INDICATOR (RIP) HG.REMIPIHG

349 REMARKS REFERENCE CODE CE.TSKRRCCE, CF.TSKRRCCE

350 REPAIR CYCLE TIME HG.ORCTOOHG, HG.FRCTFFHG,


3E-22
DEF(AUST)5692

HG.HRCTHHHG, HG.LRCTLLHG,
HG.DRCTDDHG, HG.CONRCTHG

351 REPAIR SURVIVAL RATE (RSR) HG.REPSURHG

352 REPAIR WORK SPACE COST AI.RPWSCSAI

353 REPLACED OR SUPERSEDING PROVISIONING LIST HP.RSPLISHP


ITEM SEQUENCE NUMBER

354 REPLACED OR SUPERSEDING PROVISIONING LIST HP.RSPINDHP


ITEM SEQUENCE NUMBER INDICATOR (RS/IND)

355 REPLACEMENT TASK DISTRIBUTION HG.ORTDOOHG, HG.FRTDFFHG,


HG.HRTDHHHG, HG.LRTDLLHG,
HG.DRTDDDHG

356 REPORTABLE ITEM CONTROL CODE EA.SERICCEA

357 REQUIRED DAYS OF STOCK AI.RQDSTKAI

358 REQUIREMENTS FOR CA.FTRNRQCA, CA.TRNRQCCA,


CA.TSEREQCA

359 RETAIL STOCKAGE CRITERIA XA.RESTCRXA

360 REVISION EF.SRDREVEF, EG.SRDREVEF,


EH.SRDREVEF, FA.FADREVFA

361 REVOLVING ASSETS EA.REVASSEA

362 SAFETY HAZARD SEVERITY CODE (SHSC) BI.FMSHSCBI, BK.FMSHSCBK

363 SAFETY LEVEL XA.SAFLVLXA

364 SAME AS PROVISIONING LIST ITEM SEQUENCING HG.SAPLISHG


NUMBER (SAME AS PLISN)

365 SCOPE EJ.DDCCSCEJ, EL.IRCSCOEL

366 SECTIONALIZATION IDENTIFICATION JA.SECTIDJA

367 SECTIONALIZED ITEM TRANSPORTATION INDICATOR XB.SECITMXB

368 SECTIONALIZED REMARKS JF.TRANARJF, JF.TRANCDJF(G)

369 SECURITY CLEARANCE BA.SECCLEBA, GB.SCRSSCGB

370 SELF TEST EA.SLFTSTEA, UE.TPISTSUE

371 SENSORS OR TRANSDUCERS EA.SENTRAEA

372 SEQUENTIAL SUBTASK DESCRIPTION CC.SUBNARCC, RO.SUBNARRO

373 SERIAL NUMBER XD.FRSNUMXD, XD.TOSNUMXD,


XE.FRSNUMXE, XE.TOSNUMXE,
HN.FRSNUMHN, HN.TOSNUMHN,
WJ.FRSNUMXD, WJ.TOSNUMXD

374 SERIAL NUMBER EFFECTIVITY HQ.FMSRNOHQ, HQ.TOSRNOHQ

375 SERIAL NUMBER USABLE ON CODE XD.SNUUOCXD

376 SERVICE DESIGNATOR CODE (SER) AA.SERDESAA, AB.SERDESAA,


AC.SERDESAA, AD.SERDESAA,
3E-23
DEF(AUST)5692

AE.SERDESAA, AF.SERDESAA,
AI.SERDESAI, EA.SERDESEA,
EA.USESEREA

377 SHELF LIFE (SL) HA.SHLIFEHA

378 SHELF LIFE ACTION CODE (SLAC) HA.SLACTNHA

379 SHIP TIME AJ.TIMESHAJ

380 SHIPPING CONFIGURATION JB.SHPCONJB

381 SHIPPING WEIGHT (EMPTY/LOADED) JC.SHWEEMJC, JC.SHWELDJC

382 SHOCK AND VIBRATION REMARKS JF.TRANARJF, JF.TRANCDJF(A)

383 SKETCH EA.SKETCHEA

384 SKID AREA JC.SDSICGJC

385 SKID REMARKS JD.WHTRLODJD, JD.TREINCJD(B)

386 SKILL LEVEL CODE GA.SKLVCDGA, GB.MDSCLCGB

387 SKILL SPECIALTY CODE (SSC) AE.SKSPCDGA, CD.SKSPCDGA,


EA.SSCOPREA, GA.SKSPCDGA,
GB.SKSPCDGA, MB.MPTRADRM,
RM.MPTRADRM

388 SKILL SPECIALTY EVALUATION CODE CD.SSECDECD

389 SOURCE, MAINTENANCE & RECOVERABILITY CODE EA.SMRCSEEA, HG.SMRCODHG


(SMR)

390 SPARE FACTOR EA.SPRFACEA

391 SPARES ACQUISITION INTEGRATED WITH HA.SAIPCDHA


PRODUCTION (SAIP)

392 SPECIAL MAINTENANCE ITEM CODE (SMIC) HA.SMAINCHA

393 SUPPORT EQUIPMENT SPECIAL MANAGEMENT CODE EA.SPMGNTEA

394 SPECIAL MARKING CODE HF.SPEMRKHF

395 SPECIAL MATERIAL CONTENTS CODE (SMCC) HA.SPMACCHA

396 SPECIAL PACKAGING INSTRUCTION NUMBER HF.SPINUMHF

397 SPECIAL PACKAGING INSTRUCTION (SPI) NUMBER HF.SPIREVHF


REVISION

398 SPECIALIZED SERVICE AND EQUIPMENT JF.TRANARJF, JF.TRANCDJF(F)


REQUIREMENTS

399 SPECIFIC AUTHORIZATION ED.ACTNAMED, ED.TYPACTED,


ED.NUMACTED, ED.SEQTYAED

400 SPEED JA.SPSPEDJA

401 STANDARD INTERSERVICE AGENCY SERIAL CONTROL EA.SIASCNEA


NUMBER (SIASCN)

402 STANDARDS FOR COMPARISON UC.OTPSFCUC

3E-24
DEF(AUST)5692

403 STANDBY TIME AB.OSTBTIAB, BE.STABYTBE

404 STATUS EF.STATUSEF

405 STORAGE DIMENSIONS EA.STOHGTEA, EA.STOLENEA,


EA.STOWDTEA

406 STORAGE WEIGHT EA.STOWGTEA

407 SUBTASK NUMBER CB.SUBNUMCB, CB.RFDSUBCB,


CC.SUBNUMCB, CD.SUBNUMCB,
CK.SUBNUMCB, GE.SUBNUMCB

RN.SUBNUMRN, RO.SUBNUMRN,
RP.SUBNUMCB, RP.SSTNUMRP

408 SUPERSEDURE TYPE EK.SUTYPEEK

409 SUPPLEMENTAL PACKAGING DATA HF.SUPPKDHF

410 SUPPORT CONCEPT BA.SUPCONBA

411 SUPPORT EQUIPMENT EXPLANATION EE.SEQNAREE, EE.SENARCEE(G)

412 SUPPORT EQUIPMENT FULL ITEM NAME EA.FLITNMEA

413 SUPPORT EQUIPMENT GROUPING EA.SEGRCDEA

414 SUPPORT EQUIPMENT NARRATIVE CODE EE.SENARCEE

415 SUPPORT EQUIPMENT NON-PROLIFERATION EFFORT EE.SEQNAREE, EE.SENARCEE(C)

416 SUPPORT EQUIPMENT RECOMMENDATION DATA EF.SERDNOEF, EG.SERDNOEF,


NUMBER (SERD NUMBER) EH.SERDNOEF, EK.SUSRNOEK,
UC.OTPSRDUC, UE.TPISRDUE,
UI.AIDSRDUI

417 SUPPORT EQUIPMENT RECOMMENDATION DATA EG.REVREMEG


REVISION REMARKS

418 SUPPORT EQUIPMENT REQUIRED EA.SEREQDEA

419 SUPPORT EQUIPMENT SHIPPING DIMENSIONS EA.SESHPHEA, EA.SESHPLEA,


EA.SESHPWEA

420 SUPPORT EQUIPMENT SHIPPING WEIGHT EA.SESHWTEA

421 SUPPORT OF SUPPORT EQUIPMENT COST FACTOR XA.SECSFCXA

422 SUPPRESSION INDICATOR CODE HG.SUPINDHG

423 SYSTEM/END ITEM IDENTIFIER XB.SYSIDNXB

424 SYSTEM/END ITEM NARRATIVE CODE AK.SEINCDAK

425 SYSTEM REDESIGN/LOGISTICS CONSIDERATION BC.LOCOCOBC


CODE

426 SYSTEM REDESIGN/LOGISTICS CONSIDERATION BC.LOGNARBC,


RECOMMENDATION, DISPOSITION, RESULTS BG.FMNNARBG, BG.FMNCNABG(I),
BG.FMNNARBG, BG.FMNCNABG(L)

427 TASK CODE BH.TTASKCBH, CA.TASKCDCA,


CA.REFTSKCA, CB.TASKCDCA,
CB.RFDTCDCB, CC.TASKCDCA,
3E-25
DEF(AUST)5692

CD.TASKCDCA, CF.TASKCDCA,
CG.TASKCDCA, CH.TASKCDCA,
CI.TSKTCDCI, CK.TASKCDCA

UH.TSKTCDCI, FE.TASKCDCA,
GE.TASKCDCA

MA.TASKCDCA, MB.TASKCDCA,
MC.TASKCDCA, MD.TASKCDCA,
RD.TASKCDCA, RG.TSKCLGRG,
RG.TSKCLDRG, RL.TASKCDCA,
RL.MPTCODRL, RM.TASKCDCA,
RN.TASKCDCA, RO.TASKCDCA,
RP.TASKCDCA, RP.SSTCODRP,
VE.TASKCDCA, WB.TASKCDCA,
WC.TASKCDCA, WO.TASKCDCA,
WT.TASKCDCA

428 TASK CONDITION CA.TCONDACA, CA.TCONDBCA,


CA.TCONDCCA

429 TASK CRITICALITY CODE CA.TSKCRCCA

430 TASK FREQUENCY CA.TSKFRQCA, WC.HTSKFQWC

431 TASK IDENTIFICATION CA.TASKIDCA, CB.SUBTIDCB,


RN.SUBTIDRN

432 TASK REMARKS CE.TSKREMCE

433 TASK TYPE BH.TATYPEBH

434 TECHNICAL DATA PACKAGE (TDP) UE.TPITDPUE

435 TECHNICAL EVALUATION PRIORITY CODE EA.TECEVLEA

436 TECHNICAL MANUAL CHANGE NUMBER (TM CHG) HK.TMCHGNHK

437 TECHNICAL MANUAL CODE (TM CODE) XI.TMCODEXI, CH.TMCODEXI,


HJ.TMCODEXI, HK.TMCODEXI,
HL.TMCODEXI, WR.TMCODEXI

438 TECHNICAL MANUAL FUNCTIONAL GROUP CODE (TM XB.TMFGCDXB, HK.TMFGCDHK


FGC)

439 TECHNICAL MANUAL INDENTURE CODE (TM IND) HK.TMINDCHK

440 TECHNICAL MANUAL NUMBER XI.TMNUMBXI, AH.IOITNMAH

441 TECHNICAL MANUAL REQUIRED CODE(S) EA.TMRQCDEA

442 TEST ACCURACY RATIO (TAR) UG.UUTPTAUG, UG.UUTPTDUG,


UN.UTPATAUN, UN.UTPATDUN

443 TEST LANGUAGE EA.TSTLNGEA

444 TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT EA.TMDERCEA


REGISTER CODE (TMDE CODE)

445 TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT EA.TMDERIEA


REGISTER INDEX NUMBER

446 TEST POINTS EA.TSTPTSEA

447 TEST REQUIREMENTS DOCUMENT INDICATOR UH.UUTFTDUH


3E-26
DEF(AUST)5692

448 TEST REQUIREMENTS DOCUMENT NUMBER (TRD) UA.UTTRDNUA, UM.TRDNUMUM

449 TEST SCORE GB.SSCTESGB

450 TEXT SEQUENCING CODE (TSC) AF.TEXSEQAF, AK.TEXSEQAK,


BB.TEXSEQBB, BC.TEXSEQBC,
BG.TEXSEQBG, BJ.TEXSEQBJ,
CC.TEXSEQCC, CK.TSFROMCK,
CK.TEXTTOCK, EE.TEXSEQEE,
EG.TEXSEQEG, UF.TEXSEQUF,
FB.TEXSEQFB, FC.TEXSEQFC,
FD.TEXSEQFD, GC.TEXSEQGC,
GE.TEXSEQGE, HI.TEXSEQHI,
HL.TEXSEQHL, JD.TEXSEQJD,
JF.TEXSEQJF, MA.TEXSEQMA,
MB.TEXSEQMB, MC.TEXSEQMC,
MD.TEXSEQMD, ME.TEXSEQME,
MF.TEXSEQMF, RB.TEXSEQRB,
RO.TEXSEQRO

451 THEATRE OF OPERATION JA.TRCHTHJA

452 TOTAL ITEM CHANGES (TIC) HP.TOTICHHP

453 TOTAL QUANTITY RECOMMENDED HG.TOTQTYHG

454 TOTAL SYSTEMS SUPPORTED AA.TOSYSUAA

455 TOWING SPEED JA.TWSPEDJA

456 TRACKED GROUND CONTACT PRESSURE JC.TRGRPRJC

457 TRACKED PAD SHOE AREA JC.TRPSARJC

458 TRACKED PADS TOUCHING JC.TRNUPTJC

459 TRACKED ROAD WHEEL WEIGHT JC.TRRWWTJC

460 TRAINING COST GA.TRNCOSGA

461 TRAINING LOCATION RATIONALE CA.TRNLOCCA

462 TRAINING RATIONALE CA.TRNRATCA

463 TRAINING RECOMMENDATIONS CA.TRNRECCA

464 TRANSPORTATION CHARACTERISTICS MODE TYPE JB.TRCHMTJB

465 TRANSPORTATION CHARACTERISTICS NUMBER JB.TRANCNJB

466 TRANSPORTATION COST XA.TRNCSTXA

467 TRANSPORTATION END ITEM INDICATOR XC.TRASEIXC

468 TRANSPORTATION INDICATOR JA.TRNINDJA

469 TRANSPORTATION ITEM DESIGNATOR (SHIP, JB.TRITDRJB


LIGHTERAGE, AIRCRAFT, HELICOPTER)

470 TRANSPORTATION NARRATIVE CODE JF.TRANCDJF

471 TRANSPORTATION PROJECTION REMARKS JF.TRANARJF, JF.TRANCDJF(C)

472 TRANSPORTATION REMARKS (HANDLING, TOWING, JF.TRANARJF, JF.TRANCDJF(E)


3E-27
DEF(AUST)5692

AIR DROP, SELF-PROPELLED)

473 TRANSPORTATION CONFIGURATION NUMBER JC.TRCONMJC, JD.TRCONMJC

474 TRANSPORTED END ITEM NARRATIVE CODE JD.TREINCJD

475 TRANSPORTED OTHER EQUIPMENT JD.WHTRLOJD, JD.TREINCJD(E)

476 TRANSPORT TO AND FROM JF.TRANARJF, JF.TRANCDJF(H)

477 TURNING INFORMATION JD.WHTRLOJD, JD.TREINCJD(C)

478 TYPE ACQUISITION XA.WSTYAQXA

479 TYPE CLASSIFICATION EA.TYPCLSEA

480 TYPE EQUIPMENT CODE EA.TYPEEQEA

481 TYPE OF CHANGE CODE (TOCC) XC.TOCCODXC, HG.TOCCODHG

482 TYPE OF CONSTRUCTION FD.NMFNARFD, FD.NMFNCDFD(H)

483 TYPE OF FACILITY FA.FACTYPFA, FB.FACTYPFA,


FC.FACTYPFC, FD.FACTYPFD,
FE.FACTYPFA, MD.FACTYPFA,
VC.FACTYPFA, VE.FACTYPFA,
WQ.FACTYPFA

484 TYPE OF SUPPLY SYSTEM CODE XA.TSSCODXA

485 TYPE OF UNIT OF MEASURE/ISSUE PRICE CODE HD.TUIPRCHD, HE.TUMPRCHE

486 UNIT CONTAINER CODE HF.UNICONHF

487 UNIT CONTAINER LEVEL HF.UCLEVLHF

488 UNIT OF ISSUE (UI) HA.UNITISHA

489 UNIT OF ISSUE CONVERSION FACTOR (UI HA.UICONVHA


CONVERSION FACTOR)

490 UNIT OF ISSUE PRICE (UI PRICE) HD.UIPRICHD

491 UNIT OF MEASURE (UM) CG.SQTKUMCG, CI.PQTKUMCI,


EA.LWHOUMEA, EA.WGTOUMEA,
EA.LWHSUMEA, EA.WGTSUMEA,
EA.UMSHIPEA, EA.UMSEWTEA,
FA.FAARUMFA, FA.CONUOMFA,
HA.UNITMSHA, JC.TPSAUMJC,
JC.SKADUMJC

492 UNIT OF MEASURE PRICE (UM PRICE) FA.FACNCOFA, HE.UMPRICHE

493 UNIT PACK CUBE HF.UNPKCUHF

494 UNIT PACK SIZE HF.LENUPKHF, HF.WIDUPKHF,


HF.DEPUPKHF

495 UNIT PACK WEIGHT HF.UNPKWTHF

496 UNIT SIZE HA.ULENGTHA, HA.UWIDTHHA,


HA.UHEIGHHA

497 UNIT WEIGHT HA.UWEIGHHA

3E-28
DEF(AUST)5692

498 UNIT UNDER TEST EXPLANATION UF.UTEXPLUF

499 UNSCHEDULED MAINTENANCE AC.MLUMETAC, AC.MLUMMHAC

500 UNUSUAL AND SPECIAL TRANSPORTATION JF.TRANARJF, JF.TRANCDJF(K)


REQUIREMENTS

501 USABLE ON CODE (UOC) XC.UOCSEIXC

502 UTILITIES REQUIREMENT FD.NMFNARFD, FD.NMFNCDFD(I)

503 UTILIZATION RATIO AE.UTRATIAE

504 VENTING AND PROTECTIVE CLOTHING JF.TRANARJF, JF.TRANCDJF(L)


REQUIREMENTS

505 WEAROUT LIFE BA.WEOULIBA

506 WHEELED AND AXLE REQUIREMENTS JD.WHTRLOJD, JD.TREINCJD(D)

507 WHEELED INFLATION PRESSURE JC.WHINPRJC

508 WHEELED NUMBER OF PLIES JC.WHNUPLJC

509 WHEELED NUMBER OF TIRES JC.WHNUTIJC

510 WHEELED TIRE LOAD RATING JC.WHTLDRJC

511 WHEELED TYRE REQUIREMENTS JD.WHTRLOJD, JD.TREINCJD(A)

512 WHEELED TIRE SIZE JC.WHTIFTJC

513 WHEELED WEIGHT RATINGS JC.WHWERAJC

514 WORK AREA CODE CB.SUBWACCB

515 WORK PACKAGE REFERENCE UA.UTWPRFUA, UM.WKPKRFUM

516 WORK UNIT CODE HG.WRKUCDHG

517 WRAPPING MATERIAL HF.WRAPMTHF

518 YEAR EA.YRFLDGEA

908 COMMON MANAGEMENT CODE WY.CMCODEWY

909 EXTENDED NOMENCLATURE WY.EXTNOMWY

910 LCN REPLACEMENT LEVEL WY.REPLEVWY

911 AUTHORITY TO FIT (AFT) WJ.AUTHTFWJ, WK.AUTHTFWK

912 INITIATING CONDITION SEQUENCE NUMBER RD.ICSQNMRD, RE.ICSQNMRE

913 INITIATING INSTANCE RD.ININSTRD, RE.ININSTRE

914 INITIATING MODE RD.INTMODRD, RE.INTMODRE

915 INITIATING TYPE RC.INTTYPRC, RD.INTTYPRC,


RE.INTTYPRC

916 INITIATING TYPE DESCRIPTION RC.TYPDESRC

917 BATCH NUMBER WE.FRBTCHWE, WE.TOBTCHWE,


WI.FRBTCHWE, WI.TOBTCHWE,
3E-29
DEF(AUST)5692

WJ.FRBTCHWE, WJ.TOBTCHWE,
WK.FRBTCHWE, WK.TOBTCHWE

918 BATCH IDENTIFICATION WE.BTCHIDWE

919 ACRN SET SEQUENCE NUMBER WF.SEQNUMWF, WI.SEQNUMWF,


WJ.SEQNUMWF, WK.SEQNUMWF,
WY.SEQNUMWF

920 CONFIGURATION CODE WY.CFGCODWY

921 CONTINGENCY REQUIREMENT WC.CONTINWC

922 EVENT MEASUREMENT BASE DESCRIPTION WA.DESCRPWA

923 EVENT MEASUREMENT BASE MC.EVNTMBWA, WA.EVNTMBWA,


WB.EVNTMBWA, WP.EVNTMBWA,
VD.PLIFAVD

924 FAILURE REPORTING REQUIREMENT RN.FRREQMRN

925 ITEM CRITICALITY WY.CRITEMWY

926 LOG REQUIREMENT WU.LOGREQWU, RJ.LCNLOGRJ

927 MAXIMUM FIT WG.MAXFITWG

928 MEAN TIME BETWEEN FAILURE-B WY.MTBFBXWY

929 REQUIRED FIT WY.REQFITWY

930 SERVICING GROUP IDENTIFIER WS.GRUPIDWS, WT.GRUPIDWS

931 SERVICING GROUP SEQUENCE NUMBER WS.GRPSEQWS

932 SERVICING GROUP TASK SEQUENCE NUMBER WT.TSKSEQWT

933 SERVICING IDENTIFIER MF.SRVCIDWM, WM.SRVCIDWM,


WN.SRVCIDWM, WO.SRVCIDWM,
WP.SRVCIDWM, WQ.SRVCIDWM,
WR.SRVCIDWM, WS.SRVCIDWM,
WT.SRVCIDWM,

934 SERVICING INTERVAL WP.SVCINTWP

935 SERVICING TITLE WN.SVTITLWN

936 SIGN UP REQUIREMENT WN.SIGNUPWN

937 TASK INTERVAL WB.TSKINTWB, RD.ININTVRD

938 TECHNICAL MANAGEMENT CODE WG.TMNTCDWG, WH.TMNTCDWG,


WU.TMNTCDWG

939 TECHNICAL MANAGEMENT CODE STATUS WG.TMCSTAWG

940 WORK AREA CODE WY.WACODERA

941 AUTHORITY TO DEMAND NSN VA.AUTHTDVB, VB.AUTHTDVB,


VC.AUTHTDVB

942 LOAS ENTRY NUMBER VA.LOASENVA

943 REQUIREMENTS AMPLIFICATION CODE VA.RQAMCDVA

3E-30
DEF(AUST)5692

944 NARRATIVE - TASK MA.NARRATMA

945 NARRATIVE - MAINTENANCE POLICY TRADE SKILL MB.NARRATMB

946 NARRATIVE - TASK INTERVAL MC.NARRATMC

947 NARRATIVE - TASK FACILITY MD.NARRATMD

948 NARRATIVE - LCN ITEM ME.NARRATME

949 NARRATIVE - SERVICING TITLE MF.NARRATMF

950 AUTHORISED TO DEMAND NSN PRICE VB.ATDPRIVB

951 AUTHORISED TO DEMAND NSN CURRENCY VB.ATDCURVB

952 AUTHORISED TO DEMAND NSN EXISTING STOCK VB.ATDEXIVB

953 AUTHORISED TO DEMAND NSN UNIT OF ISSUE VB.ATDUOIVB

954 SERVICING LEVEL VB.SERLEVVB

955 FACILITY CODE (ADF) VC.FACODEVC

956 MAINTENANCE SUPPLY ITEM (MSI) UNIT ENTITLEMENT VC.MSIUENVC

957 HAZARDOUS MATERIAL VD.HAZMATVD

958 TASK COST OF REPAIR ESTIMATED VE.ESTCSTVE

959 TASK COST OF REPAIR ACTUAL VE.ACTCSTVE

960 TASK COST OF REPAIR CURRENCY VE.CSTCURVE

961 FACILITY TASK TIME VE.TSKTIMVE

962 FAILURE MODE CRITICALITY (ADF) VF.FMCRITVF

965 ROLE CODE VR.ROLCODVR, VS.ROLCODVR,


VT.ROLCODVR

966 ROLE REQUIRED FIT VT.ROLREQVT

967 ROLE DESCRIPTION VR.ROLDESVR

968 SUBTASK CERTIFICATION REQUIREMENT RN.SCRTRQRN

996 WORK AREA CODE DESCRIPTION RB.WACDESRB

997 WORK AREA CODE NAME RA.WACNAMRA

3E-31
DEF(AUST)5692

SECTION 2

LISTING OF DATA ELEMENT CODES

CODE DED DATA ELEMENT TITLE (ROLE NAMED)

-A-

AAEERHGD 026 ASVAB APTITUDE ELEMENT EXPECTED RANGE - HIGH


AAEERLGD 026 ASVAB APTITUDE ELEMENT EXPECTED RANGE - LOW
AAELPHGD 026 ASVAB APTITUDE ELEMENT LOWEST PERCENTAGE - HIGH
AAELPLGD 026 ASVAB APTITUDE ELEMENT LOWEST PERCENTAGE - LOW
AAEXRHGB 026 ASVAB AFQT EXPECTED RANGE HIGH
AAEXRLGB 026 ASVAB AFQT EXPECTED RANGE LOW
AALPRHGB 026 ASVAB AFQT LOWEST PERCENTAGE - HIGH
AALPRLGB 026 ASVAB AFQT LOWEST PERCENTAGE - LOW
AAPLCCHA 308 GOVERNMENT FURNISHED PROVISIONING LIST CATEGORY CODE
(PLCC)
ABAFQTGB 026 ARMED SERVICES VOCATIONAL APTITUDE BATTERY (ASVAB) ARMED
FORCES QUALIFICATION TEST (AFQT) SCORE
ACHAVAAA 001 REQUIRED ACHIEVED AVAILABILITY
ACHAVABD 001 ACHIEVED AVAILABILITY
ACQMETHA 003 ACQUISITION METHOD CODE
ACTCSTVE 959 TASK COST OF REPAIR ACTUAL
ACTNAMED 399 ACTIVITY NAME/LOCATION
ACTNSNHA 253 NSN ACTIVITY CODE
ADCAGEHB 046 ARN CAGE CODE
ADDLTMXA 014 ADMINISTRATIVE LEAD TIME
ADDREFHB 006 ADDITIONAL REFERENCE NUMBER
ADPEQPHA 027 ADP EQUIPMENT CODE
ADRNCCHB 338 ARN REFERENCE NUMBER CATEGORY CODE
ADRNVCHB 339 ARN REFERENCE NUMBER VARIATION CODE
AIDCAGUI 046 ADAPTOR INTERCONNECTOR DEVICE (AID) CAGE CODE
AIDCUTUI 048 AID COMMON UNIT UNDER TEST
AIDREFUI 337 AID REFERENCE NUMBER
AIDRQDEA 005 ADAPTOR/INTERCONNECTION DEVICE REQUIRED
AIDSRDUI 416 AID SERD NUMBER
AIDUCNUI 025 AID APPORTIONED UNIT COST NONRECURRING
AIDUCRUI 025 AID APPORTIONED UNIT COST RECURRING
ALCSEIHN 019 S/N PROVISIONING SYSTEM/EI ALC
ALCSEIHO 019 UOC PROVISIONING SYSTEM/EI ALC
ALCSEIXE 019 S/N SYSTEM/EI ALC
ALCSEIXF 019 UOC SYSTEM/EI ALC
ALDCNMEB 016 ALLOWANCE DOCUMENT NUMBER
ALDNDSEB 015 ALLOCATION DESIGNATION DESCRIPTION
ALDTXXBE 013 ADMINISTRATIVE AND LOGISTIC DELAY TIME
ALEXRNEB 015 ALLOCATION EXTENDED RANGE
ALIQTYHG 018 ALLOWANCE ITEM QUANTITY
ALLOWCHG 017 ALLOWANCE ITEM CODE
ALLVCDEB 015 ALLOCATION LAND VESSEL CODE
ALMLVLEB 015 ALLOCATION MAINTENANCE LEVEL FUNCTION
ALORG1EB 015 ALLOWABLE RANGE 1
ALORG2EB 015 ALLOWABLE RANGE 2
ALORG3EB 015 ALLOWABLE RANGE 3
ALORG4EB 015 ALLOWABLE RANGE 4
ALORG5EB 015 ALLOWABLE RANGE 5
ALORG6EB 015 ALLOWABLE RANGE 6
3E-32
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


ALORG7EB 015 ALLOWABLE RANGE 7
ALORG8EB 015 ALLOWABLE RANGE 8
ALORG9EB 015 ALLOWABLE RANGE 9
ALRG10EB 015 ALLOWABLE RANGE 10
ALSTIDEB 015 ALLOCATION STATION IDENTIFICATION CODE
ALTALCZL 019 ALC
ALTFSCEH 253 ALTERNATE NSN FEDERAL SUPPLY CLASSIFICATION
ALTLCNBH 019 FMT ALTERNATE LCN CODE
ALTLCNHN 019 S/N PROVISIONING ALTERNATE LCN CODE (ALC)
ALTLCNHO 019 UOC PROVISIONING ALTERNATE LCN CODE (ALC)
ALTLCNXB 019 ALTERNATE LCN CODE
ALTLCNXE 019 S/N ITEM ALTERNATE LCN CODE
ALTLCNXF 019 UOC ITEM ALTERNATE LCN CODE
ALTLCNZL 199 LCN
ALTNIIEH 253 ALTERNATE NSN NATIONAL ITEM IDENTIFICATION NUMBER
AMSUFCHA 004 ACQUISITION METHOD SUFFIX CODE
ANNOMIAB 021 ANNUAL NUMBER OF MISSIONS
ANOPDAAB 022 ANNUAL OPERATING DAYS
ANOPREAG 023 ANNUAL OPERATING REQUIREMENT
ANOPTIAB 024 ANNUAL OPERATING TIME
AORALCCA 019 AOR ALC
AORLCNCA 199 ANNUAL OPERATING REQUIREMENT (AOR) LCN
AORMSBCA 238 TASK AOR MEASUREMENT BASE
AORTYPCA 203 AOR LCN TYPE
AQDCOFEA 002 ACQUISITION DECISION OFFICE
ARAPTDHG 313 AS REQUIRED LIST A (PTD)
ARBPTDHG 313 AS REQUIRED LIST B (PTD)
ASVAPEGD 026 ASVAB APTITUDE ELEMENT
ATDCURVB 951 AUTHORITY TO DEMAND NSN CURRENCY
ATDEXIVB 952 AUTHORISED TO DEMAND NSN EXISTING STOCK
ATDPRIVB 950 AUTHORISED TO DEMAND NSN PRICE
ATDUOIVB 953 AUTHORISED TO DEMAND NSN UNIT OF ISSUE
ATECAGUK 046 AUTOMATIC TEST EQUIPMENT (ATE) CAGE CODE
ATEGDSUK 149 ATE GOVERNMENT DESIGNATOR
ATEREFUK 337 ATE REFERENCE NUMBER
AUTHTDVB 941 AUTHORITY TO DEMAND NSN
AUTHTFWJ 911 AUTHORITY TO FIT SERIAL NUMBER
AUTHTFWK 911 AUTHORITY TO FIT
AVAIMHAE 028 AVAILABLE MAN-HOUR

-B-

BASALCZL 019 BASE ALC


BBPLCCHA 308 INTERIM SUPPORT ITEMS PLCC
BDLPGABA 032 BUILT IN TEST DETECTABILITY LEVEL PERCENTAGE PER GROUP 1
BDLPGBBA 032 BUILT IN TEST DETECTABILITY LEVEL PERCENTAGE PER GROUP 2
BITNDPBA 031 BUILT-IN-TEST CANNOT DUPLICATE PERCENTAGE
BITROPBA 033 BUILT-IN-TEST RETEST OK PERCENT
BOICTRHM 030 BASIS OF ISSUE CONTROL
BTCHIDWE 918 BATCH IDENTIFICATION

-C-

CACITYXH 047 CAGE CITY


CADMTDHG 214 CONDEMNED AT DEPOT MTD
CAGECDHA 046 CAGE CODE
CAGECDHB 046 ADDITIONAL REFERENCE NUMBER (ARN) ITEM CAGE CODE
CAGECDHC 046 ITEM CAGE CODE
CAGECDHN 046 S/N PROVISIONING CAGE CODE
CAGECDHO 046 UOC PROVISIONING CAGE CODE
CAGECDWE 046 ACRN CAGE CODE
CAGECDWF 046 PRIME CAGE CODE
CAGECDXH 046 COMMERCIAL AND GOVERNMENT ENTITY (CAGE) CODE

3E-33
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


CALINTEA 037 CALIBRATION INTERVAL
CALITMEA 038 CALIBRATION ITEM
CALLVLEA 277 SE CALIBRATION OPERATIONS/MAINTENANCE LEVEL
CALPROEC 039 CALIBRATION PROCEDURE
CALRQDEA 040 CALIBRATION REQUIRED
CALSTDEA 041 CALIBRATION STANDARD
CALTIMEA 042 CALIBRATION TIME
CANAMEXH 047 CAGE NAME
CANATNXH 047 CAGE NATION
CANUMBHP 043 CHANGE AUTHORITY NUMBER
CAPOZOXH 047 CAGE POSTAL ZONE
CASTATXH 047 CAGE STATE
CASTREXH 047 CAGE STREET
CBDMTDHG 214 CONDEMNED BELOW DEPOT MTD
CBLPTDHG 313 COMMON AND BULK ITEMS LIST (PTD)
CCPLCCHA 308 LONG LEAD TIME ITEM PLCC
CDPROCHF 045 CLEANING AND DRYING PROCEDURES
CFEGFEEA 056 CFE / GFE
CFGCODWY 920 CONFIGURATION CODE
CMCODEWY 908 COMMON MANAGEMENT CODE
CMRSRCEA 035 CALIBRATION MEASUREMENT REQUIREMENT SUMMARY
RECOMMENDED
CNTRECEJ 057 DDCC CONTRACTOR RECOMMENDED
CNTRNOEA 055 SE CONTRACT NUMBER
COGNSNHA 253 NATIONAL STOCK NUMBER (NSN) COGNIZANCE CODE
CONLENJB 053 CONTAINER LENGTH
CONNSNHF 253 CONTAINER NSN
CONNUMJA 055 TRANSPORTATION CONTRACT NUMBER
CONRCTHG 350 CONTRACTOR RCT
CONRECEL 057 IRCC CONTRACTOR RECOMMENDED
CONTINWC 921 CONTINGENCY REQUIREMENT
CONTNOXA 055 CONTRACT NUMBER
CONTYPJB 054 CONTAINER TYPE
CONUOMFA 491 CONSTRUCTION UNIT OF MEASURE
CONVFABA 059 CONVERSION FACTOR
CREANGJC 063 CREST ANGLE
CREWSZAA 064 CREW SIZE
CRITCDHA 066 CRITICALITY CODE
CRITEMWY 925 ITEM CRITICALITY
CRITITHA 065 CRITICAL ITEM CODE
CSPRRQXA 062 COST PER REQUISITION
CSREORXA 061 COST PER REORDER ACTION
CSTCURVE 960 TASK COST OF REPAIR CURRENCY
CTCAGEHC 046 CTIC CAGE CODE
CTDLTMXA 052 CONTACT TEAM DELAY TIME
CTICODHA 058 CONTRACTOR TECHNICAL INFORMATION CODE
CURPRCHD 051 UI PRICE CONCURRENT PRODUCTION CODE
CURPRCHE 051 UM PRICE CONCURRENT PRODUCTION CODE
CUSHMAHF 067 CUSHIONING AND DUNNAGE MATERIAL
CUSTCDEA 069 CUSTODY CODE
CUSTHIHF 068 CUSHIONING THICKNESS

-D-

DATASCHG 070 DATA STATUS CODE


DATFADEA 071 DATE OF FIRST ARTICLE DELIVERY
DDCCSCEJ 365 DDCC SCOPE
DDPLCCHA 308 TOOLS AND TEST EQUIPMENT PLCC
DEGPROHF 074 DEGREE OF PROTECTION CODE
DELSCHJA 075 DELIVERY SCHEDULE
DEMILCXA 077 DEMILITARIZATION COST
DEMILIHA 076 DEMILITARIZATION CODE
DEPUPKHF 494 UNIT PACK DEPTH

3E-34
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


DESCRPWA 922 EVENT MEASUREMENT BASE DESCRIPTION
DINMETAD 280 DAILY INSPECTION MEAN ELAPSED TIME
DINMMHAD 280 DAILY INSPECTION MEAN MAN-HOURS
DISCNTXA 083 DISCOUNT RATE
DLSCRCHA 073 DLSC SCREENING REQUIREMENT CODE
DMTDDDHG 214 DEPOT/SHIPYARD MTD
DOCAVCHA 086 DOCUMENT AVAILABILITY CODE
DOCIDCHA 087 DOCUMENT IDENTIFIER CODE
DPRNRSGB 092 DUTY POSITION REQUIRING A NEW OR REVISED SKILL
DRCLASFA 088 FACILITY DRAWING CLASSIFICATION
DRCTDDHG 350 DEPOT/SHIPYARD RCT
DRPONEHG 081 DESIGNATED REWORK POINT (DRP) ONE
DRPTWOHG 081 DRP TWO
DRTDDDHG 355 DEPOT/SHIPYARD RTD
DRWCLSEA 088 DRAWING CLASSIFICATION
DSNDATEJ 079 DESIGN DATA CATEGORY CODE (DDCC)
DSNPRCEA 080 DESIGN DATA PRICE
DTGVDSEF 071 SERD DATE OF GOVERNMENT DISPOSITION
DTRVSBEF 071 SERD DATE OF REVISION SUBMISSION
DUTIESCJ 090 DUTY
DUTYCDCJ 091 DUTY CODE

-E-

ECOANLEA 093 ECONOMIC ANALYSIS


EEPLCCHA 308 COMMON AND BULK ITEM PLCC
EFMMMBBF 238 ENGINEERING FAILURE MODE MTBF MEASUREMENT BASE
EFMTBFBF 097 ENGINEERING FAILURE MODE MEAN TIME BETWEEN FAILURE (MTBF)
EIACODXA 096 END ITEM ACRONYM CODE (EIAC)
ELEMNTCC 095 ELEMENT INDICATOR
ELEMNTRO 095 ELEMENT INDICATOR
ENDARTEA 179 END ARTICLE ITEM DESIGNATOR
ENHATCJA 098 ENVIRONMENTAL HANDLING AND TRANSPORTATION INDICATOR
EOILINJB 104 EXTERNAL OR INTERNAL LOAD INDICATOR
ESSALVXA 102 ESTIMATED SALVAGE VALUE
ESSCODHG 100 ESSENTIALITY CODE
ESTCSTVE 958 TASK COST OF REPAIR ESTIMATED
ESTPRCEJ 101 DDCC ESTIMATED PRICE
ESTPRCEL 101 IRCC ESTIMATED PRICE
EVNTMBWA 923 EVENT MANAGEMENT BASE
EXTNOMWY 909 EXTENDED NOMECLATURE
EXUNPREA 103 EXTENDED UNIT PRICE

-F-

FAAREAFA 112 FACILITY AREA


FAARUMFA 491 FACILITY AREA UNIT OF MEASURE
FABNARFC --- BASELINE FACILITY NARRATIVE
FACCCDFA 115 FACILITY CATEGORY CODE
FACCCDFC 115 BASELINE FACILITY CATEGORY CODE
FACCCDFD 115 NEW OR MODIFIED FACILITY CATEGORY CODE
FACCLAFA 116 FACILITY CLASS
FACNAMFA 118 FACILITY NAME
FACNAMFC 118 BASELINE FACILITY NAME
FACNAMFD 118 NEW OR MODIFIED FACILITY NAME
FACNARFB --- FACILITY NARRATIVE
FACNCOFA 492 FACILITY CONSTRUCTION UNIT OF MEASURE PRICE
FACODEVC 955 FACILITY CODE (ADF)
FACRNUBI 133 FAILURE MODE CRITICALITY NUMBER
FACTYPFA 483 FACILITY TYPE
FACTYPFC 483 BASELINE FACILITY TYPE
FACTYPFD 483 NEW OR MODIFIED FACILITY TYPE
FADNUMFA 089 FACILITY DRAWING NUMBER

3E-35
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


FADREVFA 360 FACILITY DRAWING REVISION
FAILRTBD 140 FAILURE RATE
FALCNCXG 019 FUNCTIONAL ALTERNATE LCN CODE
FAMGRPEA 142 FAMILY GROUP
FAMOINBF 134 FAILURE MODE INDICATOR (FMI)
FAMOINBH 134 FMT FAILURE MODE INDICATOR
FARAMBBD 238 FAILURE RATE MEASUREMENT BASE
FBNACDFC 113 BASELINE FACILITY NARRATIVE CODE
FBNACDFC(A) 107 FACILITIES MAINTENANCE REQUIREMENTS
FBNACDFC(B) 109 FACILITIES REQUIREMENTS FOR OPERATIONS
FBNACDFC(C) 110 FACILITIES REQUIREMENT FOR TRAINING
FBNACDFC(D) 120 FACILITY REQUIREMENTS SPECIAL CONSIDERATIONS
FBNACDFC(E) 121 FACILITY REQUIREMENTS SUPPLY/STORAGE
FEPROBBI 130 FAILURE EFFECT PROBABILITY
FFPLCCHA 308 REPAIRABLE ITEMS PLCC
FIAMBABA 143 FAULT ISOLATION AMBIGUITY GROUP 1
FIAMBBBA 143 FAULT ISOLATION AMBIGUITY GROUP 2
FIGNUMHK 144 FIGURE NUMBER
FIPFGABA 143 FAULT ISOLATION PERCENT FAILURE GROUP 1
FIPFGBBA 143 FAULT ISOLATION PERCENT FAILURE GROUP 2
FIQPQTJE 298 FIRST QUARTER PROCUREMENT QUANTITY
FISCYRHD 145 UI PRICE FISCAL YEAR
FISCYRHE 145 UM PRICE FISCAL YEAR
FLCNTYXG 203 FUNCTIONAL LCN TYPE
FLITNMEA 412 SE FULL ITEM NAME
FLSACNXG 199 FUNCTIONAL LSA CONTROL NUMBER
FMCLASBF 132 FAILURE MODE CLASSIFICATION
FMCNARBJ --- FAILURE MODE INDICATOR MISSION PHASE CHARACTERISTICS
NARRATIVE
FMCRITVF 962 FAILURE MODE CRITICALITY (ADF)
FMMPCNBJ 135 FMI MISSION PHASE CHARACTERISTICS NARRATIVE CODE
FMMPCNBJ(A) 049 COMPENSATING DESIGN PROVISIONS
FMMPCNBJ(B) 050 COMPENSATING OPERATOR ACTION PROVISIONS
FMNCNABG 131 FAILURE MODE & RCM NARRATIVE CODE
FMNCNABG(A) 125 FAILURE/DAMAGE MODE EFFECT END EFFECT
FMNCNABG(B) 126 FAILURE/DAMAGE MODE EFFECT LOCAL
FMNCNABG(C) 127 FAILURE/DAMAGE MODE EFFECT NEXT HIGHER
FMNCNABG(D) 124 FAILURE CAUSE
FMNCNABG(E) 128 FAILURE/DAMAGE MODE
FMNCNABG(F) 129 FAILURE MODE DETECTION METHOD
FMNCNABG(G) 138 FAILURE PREDICTABILITY
FMNCNABG(H) 137 FAILURE MODE REMARKS
FMNCNABG(I) 426 REDESIGN RECOMMENDATIONS
FMNCNABG(J) 343 RCM AGE EXPLORATION
FMNCNABG(K) 346 RCM REASONING
FMNCNABG(L) 426 RCM REDESIGN RECOMMENDATIONS
FMNNARBG --- FAILURE MODE NARRATIVE
FMOPTIBI 269 OPERATING TIME
FMOTMBBI 238 OPERATING TIME MEASUREMENT BASE
FMRATOBF 136 FAILURE MODE RATIO
FMSHSCBI 362 SAFETY HAZARD SEVERITY CODE
FMSHSCBK 362 RAM SAFETY HAZARD SEVERITY CODE
FMSRNOHQ 374 FROM SERIAL NUMBER EFFECTIVITY
FMTDFFHG 214 INTERMEDIATE/DIRECT SUPPORT MTD
FNCODEFB 119 FACILITY NARRATIVE CODE
FNCODEFB(A) 114 FACILITY CAPABILITY
FNCODEFB(B) 117 FACILITY LOCATION
FPROBLBI 139 FAILURE PROBABILITY LEVEL
FQPQTYJE 298 FOURTH QUARTER PROCUREMENT QUANTITY
FRBTCHWE 917 FROM BATCH NUMBER
FRCLASJB 146 FREIGHT CLASSIFICATION
FRCTFFHG 350 INTERMEDIATE/DIRECT SUPPORT RCT
FRDATABA 141 FAILURE RATE DATA SOURCE

3E-36
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


FRREQMRN 924 FAILURE REPORTING REQUIREMENT
FRSNUMHN 373 S/N PROVISIONING SERIAL NUMBER FROM
FRSNUMXD 373 SERIAL NUMBER FROM
FRSNUMXE 373 S/N SERIAL NUMBER FROM
FRTDFFHG 355 INTERMEDIATE/DIRECT SUPPORT RTD
FSCNSNHA 253 NSN FEDERAL SUPPLY CLASSIFICATION
FTRNRQCA 358 FACILITY REQUIREMENT CODE

-G-

GENECDEA 148 GENERIC CODE


GFAEIDEM 179 SYSTEM EQUIPMENT ITEM DESIGNATOR
GGPLCCHA 308 INTERIM RELEASED ITEM PLCC
GOVDESEA 149 GOVERNMENT DESIGNATOR
GOVRQDEJ 150 DDCC GOVERNMENT REQUIRED
GOVRQDEL 150 IRCC GOVERNMENT REQUIRED
GRPSEQWS 931 SERVICING GROUP SEQUENCE NUMBER
GRUPIDWS 930 SERVICING GROUP IDENTIFIER

-H-

HALTMLJB 250 HIGHWAY ALTERNATE MODEL LOAD


HALTMTJB 251 HIGHWAY ALTERNATE MODEL TYPE
HARDCIHG 151 HARDNESS CRITICAL ITEM
HAZCODHA 154 HAZARDOUS CODE
HAZMATVD 957 HAZARDOUS MATERIAL
HAZMPCCA 155 HAZARDOUS MAINTENANCE PROCEDURES CODE
HDWRPREA 153 HARDWARE DEVELOPMENT PRICE
HHPLCCHA 308 INSTALLATION AND CHECKOUT ITEM PLCC
HICLNEJC 241 MILITARY LOAD CLASSIFICATION EMPTY
HICLNLJC 241 MILITARY LOAD CLASSIFICATION LOADED
HIPRMLJB 250 HIGHWAY PRIME MODEL LOAD
HIPRMTJB 251 HIGHWAY PRIME MODEL TYPE
HLCSPCXA 160 HOLDING COST PERCENTAGE
HMATLRJB 159 HELICOPTER MISSION ALTITUDE
HMDISRJB 159 HELICOPTER MISSION DISTANCE
HMPAYRJB 159 HELICOPTER MISSION PAYLOAD
HMSCOSHA 156 HAZARDOUS MATERIALS STORAGE COST
HMTDHHHG 214 INTERMEDIATE/GENERAL SUPPORT MTD
HMTIMRJB 159 HELICOPTER MISSION TIME
HMTMPRJB 159 HELICOPTER MISSION TEMPERATURE
HRCTHHHG 350 INTERMEDIATE/GENERAL SUPPORT RCT
HRDCPCCA 152 HARDNESS CRITICAL PROCEDURE (HCP) CODE
HRLARTGA 161 HOUR LABOUR RATE
HRTDHHHG 355 INTERMEDIATE/GENERAL SUPPORT RTD
HTSKFQWC 430 HISTORICAL TASK FREQUENCY
HWDCOSHA 157 HAZARDOUS WASTE DISPOSAL COST
HWSCOSHA 158 HAZARDOUS WASTE STORAGE COST

-I-

ICCODEEK 172 SUPERSEDURE INTERCHANGEABILITY CODE


ICSQNMRD 912 INITIATING CONDITION SEQUENCE NUMBER
ICSQNMRE 912 SERVICING INITIATING CONDITION SEQUENCE NUMBER
ILSPRCEA 170 INTEGRATED LOGISTIC SUPPORT PRICE
IMTBMMBD 238 MEAN TIME BETWEEN MAINTENANCE INDUCED MEASUREMENT BASE
INAMECHA 183 ITEM NAME CODE
INCATCXA 167 INITIAL CATALOGUING COST
INCQTYHF 175 INTERMEDIATE CONTAINER QUANTITY
INDCODHG 162 INDENTURE CODE
INDMATHA 163 INDUSTRIAL MATERIALS ANALYSIS OF CAPACITY
INEVNTRD 923 INITIATING EVENT MEASUREMENT BASE
INEVNTRE 923 SERVICING INITIATING EVENT MEASUREMENT BASE

3E-37
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


INHAVAAA 164 REQUIRED INHERENT AVAILABILITY
INHAVABD 164 INHERENT AVAILABILITY
INHMAFBD 165 INHERENT MAINTENANCE FACTOR
INHMTBBD 232 MEAN TIME BETWEEN MAINTENANCE INHERENT (MTBM INHERENT)
INHMTMBD 238 MEAN TIME BETWEEN MAINTENANCE INHERENT MEASUREMENT BASE
ININSTRD 913 INITIATING INSTANCE
ININSTRE 913 SERVICING INITIATING INSTANCE
ININTVRD 937 INITIATING INTERVAL
ININTVRE 937 SERVICING INITIATING INTERVAL
INMTBMBD 231 MEAN TIME BETWEEN MAINTENANCE INDUCED
INTALCRD 019 INITIATING ALC
INTALCRE 019 SERVICING INITIATING ALC
INTBINXA 166 INITIAL BIN COST
INTCHCHP 172 INTERCHANGEABILITY CODE
INTCONHF 174 INTERMEDIATE CONTAINER CODE
INTLCNRD 199 INITIATING LCN
INTLCNRE 199 SERVICING INITIATING LCN
INTLTYRD 203 INITIATING LCN TYPE
INTLTYRE 203 SERVICING INITIATING LCN TYPE
INTMODRD 914 INITIATING MODE
INTMODRE 914 SERVICING INITIATING MODE
INTRATXA 173 INTEREST RATE
INTSUBEF 071 SERD DATE OF INITIAL SUBMISSION
INTTYPRC 915 INITIATING TYPE
INVSTGXA 176 INVENTORY STORAGE SPACE COST
IOCAGEAH 046 INTEROPERABLE CAGE CODE
IOINTYAH 266 INTEROPERABLE ITEM NUMBER TYPE
IOITNMAH 440 INTEROPERABLE ITEM TECHNICAL MANUAL NUMBER
IONAMEAH 182 INTEROPERABLE ITEM NAME
IONFSCAH 253 INTEROPERABLE ITEM NSN FEDERAL SUPPLY CLASSIFICATION
IONIINAH 253 INTEROPERABLE ITEM NATIONAL ITEM IDENTIFICATION NUMBER
IOREFNAH 337 INTEROPERABLE REFERENCE NUMBER
IPACDCEI 168 INPUT POWER SOURCE ALTERNATING CURRENT/DIRECT CURRENT
IPFRMXEI 168 INPUT POWER SOURCE FREQUENCY RANGE MAXIMUM
IPMXRPEI 168 INPUT POWER SOURCE PERCENT MAXIMUM RIPPLE
IPOPRGEI 168 INPUT POWER SOURCE OPERATING RANGE MINIMUM
IPPHASEI 168 INPUT POWER SOURCE PHASE
IPPOWREI 168 INPUT POWER SOURCE WATTS
IPRGMXEI 168 INPUT POWER SOURCE FREQUENCY RANGE MINIMUM
IPSOPNEI 168 SOURCE OPTION NUMBER
IPSRGMEI 168 INPUT POWER SOURCE OPERATING RANGE MAXIMUM
IRCCODEL 171 INTEGRATED LOGISTIC SUPPORT REQUIREMENTS CATEGORY CODE
(IRCC)
IRCSCOEL 365 IRCC SCOPE
ISLPTDHG 313 INTERIM SUPPORT ITEMS LIST (PTD)
ITEMNOHK 184 ITEM NUMBER
ITMCATHG 177 ITEM CATEGORY CODE (ICC)
ITMDESXC 179 SYSTEM/EI ITEM DESIGNATOR CODE
ITMMGCHA 181 ITEM MANAGEMENT CODE
ITNAMEHA 182 ITEM NAME

-J-

JJPLCCHA 308 AUTHORIZATION STOCK LIST ITEM PLCC


JOBCODCJ 186 JOB CODE
JOBDESCJ 185 JOB

-K-

KKPLCCHA 308 RECOMMENDED BUY LIST ITEM PLCC

3E-38
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)

-L-

LABRATAI 189 LABOUR RATE


LCNAMEXB 201 LCN NOMENCLATURE
LCNINDXB 200 LCN INDENTURE CODE (LCN-IC)
LCNLOGRJ 926 LOG REQUIREMENT
LCNSEIHN 199 S/N PROVISIONING SYSTEM/EI LCN
LCNSEIHO 199 UOC PROVISIONING SYSTEM/EI LCN
LCNSEIXE 199 S/N SYSTEM/EI LCN
LCNSEIXF 199 UOC SYSTEM/EI LCN
LCNSTRXA 202 LCN STRUCTURE
LCNTYPBH 203 FMT LCN TYPE
LCNTYPXB 203 LCN TYPE
LCNTYPXE 203 S/N ITEM LCN TYPE
LCNTYPXF 203 UOC ITEM LCN TYPE
LCNTYPZL 203 LCN TYPE
LENUPKHF 494 UNIT PACK LENGTH
LGCTCDEA 197 LOGISTIC CONTROL CODE
LGDCOFEA 198 LOGISTICS DECISION OFFICE
LICYSTEA 190 LIFE CYCLE STATUS
LIFSPNEA 191 LIFE SPAN
LINNUMHA 193 LINE ITEM NUMBER
LLIPTDHG 313 LONG LEAD TIME ITEMS LIST (PROVISIONING TECHNICAL
DOCUMENTATION SELECTION CODE (PTD))
LLPLCCHA 308 PRESCRIBED LOAD LIST ITEM PLCC
LMTDLLHG 214 SPECIAL REPAIR ACTIVITY MTD
LOASENVA 942 LOAS ENTRY NUMBER
LOCOCOBC 425 LOGISTICS CONSIDERATION CODE
LODFACXA 195 LOADING FACTOR
LOGACCBA 196 LOGISTIC CONSIDERATIONS ACCESSIBILITY
LOGCONBA 196 LOGISTIC CONSIDERATIONS CONNECTORS
LOGCRCBA 196 LOGISTIC CONSIDERATIONS CORROSION/RUST CONTROL
LOGDSPBA 196 LOGISTIC CONSIDERATIONS DESIGN FOR SELF PROTECTION
LOGFLOBA 196 LOGISTIC CONSIDERATIONS FAULT LOCATION
LOGLABBA 196 LOGISTIC CONSIDERATIONS LABELING
LOGMAIBA 196 LOGISTIC CONSIDERATIONS MAINTENANCE EASE
LOGNARBC 426 RAM LOGISTICS CONSIDERATIONS
LOGPATBA 196 LOGISTIC CONSIDERATIONS PACKAGING AND TRANSPORTATION
LOGREQWU 926 LOG REQUIREMENT
LOGSAFBA 196 LOGISTIC CONSIDERATIONS SAFETY
LOGSKIBA 196 LOGISTIC CONSIDERATIONS SKILLS
LOGSTABA 196 LOGISTIC CONSIDERATIONS STANDARDIZATION
LOGTEPBA 196 LOGISTIC CONSIDERATIONS TEST POINTS
LOGTRABA 196 LOGISTIC CONSIDERATIONS TRAINING
LOTQFMHD 205 UI PRICE LOT QUANTITY FROM
LOTQFMHE 205 UM PRICE LOT QUANTITY FROM
LOTQTOHD 205 UI PRICE LOT QUANTITY TO
LOTQTOHE 205 UM PRICE LOT QUANTITY TO
LRCTLLHG 350 SPECIAL REPAIR ACTIVITY RCT
LRTDLLHG 355 SPECIAL REPAIR ACTIVITY RTD
LRUNITHG 194 LINE REPLACEABLE UNIT (LRU)
LSACONBH 199 FAILURE MODE TASK (FMT) LSA CONTROL NUMBER (LCN)
LSACONHN 199 S/N PROVISIONING LSA CONTROL NUMBER (LCN)
LSACONHO 199 UOC PROVISIONING LSA CONTROL NUMBER (LCN)
LSACONXB 199 LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER (LCN)
LSACONXE 199 S/N ITEM LSA CONTROL NUMBER (LCN)
LSACONXF 199 UOC ITEM LSA CONTROL NUMBER (LCN)
LSARCDEA 204 LSA RECOMMENDATION CODE
LTYSEIXE 203 S/N SYSTEM/EI LCN TYPE
LTYSEIXF 203 UOC SYSTEM/EI LCN TYPE
LVLBOIHM 030 BASIS OF ISSUE LEVEL
LWHOUMEA 491 OPERATING DIMENSIONS UNIT OF MEASURE

3E-39
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


LWHSUMEA 491 STORAGE DIMENSIONS UNIT OF MEASURE

-M-

MAIACTHG 206 MAINTENANCE ACTION CODE (MAC)


MAININBH 208 MAINTENANCE INTERVAL
MAINMBBH 238 MAINTENANCE INTERVAL MEASUREMENT BASE
MAOTIMHG 221 MAXIMUM ALLOWABLE OPERATING TIME (MAOT)
MATERLHA 218 MATERIAL
MATNSNHA 253 NSN MATERIEL CONTROL CODE
MAXFITWG 927 MAXIMUM FIT
MAXTTRAA 222 REQUIRED MAXIMUM TIME TO REPAIR
MAXTTRBD 222 MAXIMUM TIME TO REPAIR (MAXTTR)
MDCSSCGB 257 NEW OR MODIFIED SKILL SPECIALTY CODE
MDSCLCGB 386 NEW OR MODIFIED SKILL LEVEL CODE
MEASBSAG 238 ANNUAL OPERATING REQUIREMENT MEASUREMENT BASE
MEPRESHF 239 METHOD OF PRESERVATION CODE
MEQLINBA 243 MINIMUM EQUIPMENT LIST INDICATOR
MGCOATEA 217 MANAGING COMMAND/AGENCY
MGTPLNEA 216 MANAGEMENT PLAN
MILUNTJA 242 MILITARY UNIT TYPE
MINREUHG 245 MINIMUM REPLACEMENT UNIT
MISSPCBL 246 MISSION PHASE CODE
MLMTTRAC 222 MAINTENANCE LEVEL MAXIMUM TIME TO REPAIR
MLNSSUAC 265 NUMBER OF SYSTEMS SUPPORTED
MLPERCAC 286 MAINTENANCE LEVEL PERCENTILE
MLSAMHAC 020 MAINTENANCE LEVEL SCHEDULED ANNUAL MAN-HOURS
MLSMHOAC 215 SCHEDULED MAN-HOUR PER OPERATING HOUR
MLUAMHAC 020 MAINTENANCE LEVEL UNSCHEDULED ANNUAL MAN-HOURS
MLUMETAC 499 UNSCHEDULED MAINTENANCE MEAN ELAPSED TIME
MLUMHOAC 215 UNSCHEDULED MAN-HOUR PER OPERATING HOUR
MLUMMHAC 499 UNSCHEDULED MAINTENANCE MEAN MAN-HOURS
MMISDMAB 238 MEAN MISSION DURATION MEASUREMENT BASE
MMISDUAB 228 MEAN MISSION DURATION
MMPLCCHA 308 SYSTEM SUPPORT PACKAGE COMPONENT LIST PLCC
MNTPLNUM 209 SE UUT MAINTENANCE PLAN NUMBER
MOBFACEA 248 MOBILE FACILITY CODE
MOBTYPJC 249 MOBILITY TYPE
MODCHGEA 252 MODIFICATION OR CHANGE
MPCMETAD 280 MISSION PROFILE CHANGE MEAN ELAPSED TIME
MPCMMHAD 280 MISSION PROFILE CHANGE MEAN MAN-HOURS
MPOPLDBL 247 MISSION PHASE/OPERATIONAL MODE
MPTALCRL 019 MAINTENANCE POLICY ALC
MPTCODRL 427 MAINTENANCE POLICY TASK CODE
MPTLCNRL 199 MAINTENANCE POLICY LCN
MPTLTYRL 203 MAINTENANCE POLICY LCN TYPE
MPTRADRM 387 MAINTENANCE POLICY TRADE
MPTRADRM 387 MAINTENANCE POLICY TRADE
MRRMODHG 213 MAINTENANCE REPLACEMENT RATE MODIFIER
MRRONEHG 211 MAINTENANCE REPLACEMENT RATE I (MRRI)
MRRTWOHG 212 MAINTENANCE REPLACEMENT RATE II (MRRII)
MSDMETCA 224 MEASURED MEAN ELAPSE TIME
MSDMMHCA 225 MEASURED MEAN MAN-HOURS
MSIUENVC 956 MAINTENANCE SUPPLY ITEM (MSI) UNIT ENTITLEMENT
MTBFBXWY 928 MEAN TIME BETWEEN FAILURE-B
MTBMPMBD 238 MEAN TIME BETWEEN PREVENTIVE MAINTENANCE MEASUREMENT
BASE
MTBMPVBD 234 MEAN TIME BETWEEN PREVENTIVE MAINTENANCE
MTBRMBBD 238 MEAN TIME BETWEEN REMOVALS MEASUREMENT BASE
MTBRXXAG 235 REQUIRED MEAN TIME BETWEEN REMOVALS
MTBRXXBD 235 MEAN TIME BETWEEN REMOVALS (MTBR)
MTLEADHA 219 MATERIAL LEADTIME
MTLWGTHA 220 MATERIAL WEIGHT

3E-40
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


MTTROPBD 236 MEAN TIME TO REPAIR OPERATIONAL
MTTRTHBD 236 MEAN TIME TO REPAIR TECHNICAL

-N-

NARRATMA 944 NARRATIVE - TASK


NARRATMB 945 NARRATIVE - MAINTENANCE POLICY TRADE SKILL
NARRATMC 946 NARRATIVE - TASK INTERVAL
NARRATMD 947 NARRATIVE - TASK FACILITY
NARRATME 948 NARRATIVE - LCN ITEM
NARRATMF 949 NARRATIVE - SERVICING
NETEXWJA 254 NET EXPLOSIVE WEIGHT
NHAINDHH 259 NHA PLISN INDICATOR
NHAPLIHH 258 NEXT HIGHER ASSEMBLY (NHA) PROVISIONING LIST ITEM SEQUENCE
NUMBER (PLISN)
NIINSNHA 253 NSN NATIONAL ITEM IDENTIFICATION NUMBER
NMFNARFD --- NEW OR MODIFIED FACILITY NARRATIVE
NMFNCDFD 255 NEW OR MODIFIED FACILITY NARRATIVE CODE
NMFNCDFD(A) 105 FACILITY DESIGN CRITERIA
NMFNCDFD(B) 106 FACILITY INSTALLATION LEAD TIME
NMFNCDFD(C) 122 FACILITY TASK AREA BREAKDOWN
NMFNCDFD(D) 111 FACILITIES UTILIZATION
NMFNCDFD(E) 108 FACILITIES REQUIREMENTS
NMFNCDFD(F) 123 FACILITY UNIT COST RATIONALE
NMFNCDFD(G) 188 FACILITY JUSTIFICATION
NMFNCDFD(H) 482 TYPE OF CONSTRUCTION
NMFNCDFD(I) 502 UTILITIES REQUIREMENT
NMSNARGC --- NEW OR MODIFIED SKILL NARRATIVE
NMSNCDGC 256 NEW OR MODIFIED SKILL NARRATIVE CODE
NMSNCDGC(A) 007 NEW OR MODIFIED SKILL ADDITIONAL REQUIREMENTS
NMSNCDGC(B) 094 EDUCATIONAL QUALIFICATIONS
NMSNCDGC(C) 188 SKILL JUSTIFICATION
NMSNCDGC(D) 012 ADDITIONAL TRAINING REQUIREMENTS
NMTBMMBD 238 MEAN TIME BETWEEN MAINTENANCE NO DEFECT MEASUREMENT BASE
NOMTBMBD 233 MEAN TIME BETWEEN MAINTENANCE NO DEFECT
NOPRFFJA 260 NONOPERABILITY FRAGILITY FACTOR
NORETSHG 261 NOT REPAIRABLE THIS STATION
NOSHPSAI 263 NUMBER OF SHOPS
NUMACTED 399 NUMBER OF ACTIVITIES
NUOPLOAA 262 NUMBER OF OPERATING LOCATIONS

-O-

OMAMDTAA 223 OPERATIONAL MEAN ACTIVE MAINTENANCE DOWNTIME


OMLVLCAC 277 OPERATIONS AND MAINTENANCE LEVEL CODE
OMLVLCAI 277 MODELLING OPERATIONS AND MAINTENANCE LEVEL CODE
OMLVLFAJ 277 OPERATIONS AND MAINTENANCE LEVEL FROM
OMLVLTAJ 277 OPERATIONS AND MAINTENANCE LEVEL TO
OMTBFMBD 238 MEAN TIME BETWEEN FAILURES OPERATIONAL MEASUREMENT BASE
OMTBMABD 230 MEAN TIME BETWEEN MAINTENANCE ACTIONS (MTBMA) OPERATIONAL
OMTBMMBD 238 MTBMA OPERATIONAL MEASUREMENT BASE
OMTDOOHG 214 ORGANIZATIONAL MAINTENANCE TASK DISTRIBUTION (MTD)
OPALDTAB 013 REQUIRED ADMINISTRATIVE AND LOGISTIC DELAY TIME
OPAVAIAB 273 REQUIRED OPERATIONAL AVAILABILITY
OPAVAIBE 273 OPERATIONAL AVAILABILITY
OPLENGEA 268 OPERATING LENGTH
OPMRBMAG 230 REQUIRED OPERATIONAL MEAN TIME BETWEEN MAINTENANCE
ACTIONS
OPMTBFAG 229 REQUIRED OPERATIONAL MEAN TIME BETWEEN FAILURES
OPMTBFBD 229 MEAN TIME BETWEEN FAILURES OPERATIONAL
OPMTTRAA 236 REQUIRED OPERATIONAL MEAN TIME TO REPAIR
OPRHGTEA 268 OPERATING HEIGHT
OPRLIFXA 272 OPERATION LIFE

3E-41
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


OPRMANEA 278 OPERATORS MANUAL
OPRQINAB 275 OPERATIONAL REQUIREMENT INDICATOR
OPRQINAG 275 RELIABILITY OPERATIONAL REQUIREMENTS INDICATOR
OPRQINBE 275 RAM OPERATIONAL REQUIREMENT INDICATOR
OPRWGTEA 270 OPERATING WEIGHT
OPTPRIHF 279 OPTIONAL PROCEDURES INDICATOR
OPWEEMJC 276 OPERATIONAL WEIGHT EMPTY
OPWELDJC 276 OPERATIONAL WEIGHT LOADED
OPWIDTEA 268 OPERATING WIDTH
ORCTOOHG 350 ORGANIZATIONAL REPAIR CYCLE TIME (RCT)
ORTDOOHG 355 ORGANIZATIONAL REPLACEMENT TASK DISTRIBUTION (RTD)
OSCOSTEA 267 OPERATING AND SUPPORT COST
OSTBTIAB 403 REQUIRED STANDBY TIME
OTPACNUC 025 OTP APPORTIONED UNIT COST NONRECURRING
OTPACRUC 025 OTP APPORTIONED UNIT COST RECURRING
OTPCAGUC 046 OPERATIONAL TEST PROGRAM (OTP) CAGE CODE
OTPCTPUC 060 OTP COORDINATED TEST PLAN
OTPREFUC 337 OTP REFERENCE NUMBER
OTPSFCUC 402 OTP STANDARDS FOR COMPARISON
OTPSRDUC 416 OTP SUPPORT EQUIPMENT RECOMMENDATION DATA NUMBER
OVHREPHH 281 OVERHAUL REPLACEMENT RATE

-P-

PACCATHF 282 PACKAGING CATEGORY CODE


PALCNCXG 019 PHYSICAL ALTERNATE LCN CODE
PAMENRGE 290 PHYSICAL AND MENTAL REQUIREMENTS NARRATIVE
PARACCEC 284 SE PARAMETER ACCURACY
PARGPCEC 284 SE PARAMETER GROUP CODE
PARPAREC 284 SE PARAMETER
PARRVCEC 284 SE PARAMETER RANGE/VALUE CODE
PASTHREA 285 PASS THROUGH PRICE
PCBLVLEA 277 PRINTED CIRCUIT BOARD REPAIR OPERATIONS/MAINTENANCE LEVEL
PCCNUMXC 307 SYSTEM/EI PROVISIONING CONTRACT CONTROL NUMBER
PCLPTDHG 313 POST CONFERENCE LIST (PTD)
PERCENAA 286 REQUIRED PERCENTILE
PERCENBD 286 PERCENTILE
PHYSECHA 291 PHYSICAL SECURITY PILFERAGE CODE
PINMETAD 280 PERIODIC INSPECTION MEAN ELAPSED TIME
PINMMHAD 280 PERIODIC INSPECTION MEAN MAN-HOURS
PIPLISHG 297 PRIOR ITEM PLISN
PKCAGEHF 046 PACKAGING DATA PREPARER CAGE
PKGCODHF 283 PACKING CODE
PLCNTYXG 203 PHYSICAL LCN TYPE
PLIFPARH 923 PART PRIMARY LIFING PARAMETER
PLISNOHG 309 PROVISIONING LIST ITEM SEQUENCE NUMBER (PLISN)
PLISNOXC 309 SYSTEM/EI PROVISIONING LIST ITEM SEQUENCE NUMBER
PLSACNXG 199 PHYSICAL LSA CONTROL NUMBER (LCN)
PMCSIDCA 296 PREVENTIVE MAINTENANCE CHECKS AND SERVICES (PMCS) INDICATOR
CODE
PMDTECCA 237 PRIMARY MEANS OF DETECTION
PMICODHA 293 PRECIOUS METAL INDICATOR CODE
POIMETAD 280 POSTOPERATIVE INSPECTION MEAN ELAPSED TIME
POIMMHAD 280 POSTOPERATIVE INSPECTION MEAN MAN-HOURS
PPLPTDHG 313 PROVISIONING PARTS LIST (PTD)
PPSLSTHA 302 PROGRAM PARTS SELECTION LIST
PQTKUMCI 491 PROVISION QUANTITY PER TASK UNIT OF MEASURE
PQTYTKCI 319 PROVISION QUANTITY PER TASK
PRDLDTHA 299 PRODUCTION LEAD TIME
PRDMETCA 224 PREDICTED MEAN ELAPSE TIME
PRDMMHCA 225 PREDICTED MEAN MAN-HOURS
PREATYEA 294 PREPARING ACTIVITY
PREMETAD 280 PRE-OPERATIVE INSPECTION MEAN ELAPSED TIME

3E-42
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


PREMMHAD 280 PRE-OPERATIVE INSPECTION MEAN MAN-HOURS
PREOVCBA 292 PILOT REWORK OVERHAUL CANDIDATE
PROALCCI 019 TASK PROVISION ALC
PROCAGCI 046 TASK PROVISION CAGE CODE
PROELEEA 301 PROGRAM ELEMENT
PROELIHP 305 PRORATED EXHIBIT LINE ITEM NUMBER (ELIN)
PROFACXA 300 PRODUCTIVITY FACTOR
PROLCNCI 199 TASK PROVISION LCN
PROLTYCI 203 TASK PROVISION LCN TYPE
PROPSNJA 304 PROPER SHIPPING NAME
PROQTYHP 306 PRORATED QUANTITY
PROREFCI 337 TASK PROVISION REFERENCE NUMBER
PROSICHG 312 PROVISIONING SYSTEM IDENTIFIER CODE
PROUIPHD 314 UI PRICE PROVISIONING
PROUMPHE 314 UM PRICE PROVISIONING
PROVNOHL 310 PROVISIONING NOMENCLATURE
PRSMATHF 295 PRESERVATION MATERIAL CODE
PRSTDACA 287 TASK PERFORMANCE STANDARD A
PRSTDBCA 287 TASK PERFORMANCE STANDARD B
PRSTDCCA 287 TASK PERFORMANCE STANDARD C
PRSTOMXA 289 PERSONNEL TURNOVER RATE/MIL
PRSTOVXA 289 PERSONNEL TURNOVER RATE/CIV
PSICPOEA 303 PROGRAM SUPPORT INVENTORY CONTROL POINT

-Q-

QTYASYHG 316 QUANTITY PER ASSEMBLY


QTYASYXC 316 SYSTEM/EI QUANTITY PER ASSEMBLY
QTYAVAAE 324 AVAILABLE QUANTITY
QTYBOIHM 030 BASIS OF ISSUE QUANTITY
QTYFIGHK 318 QUANTITY PER FIGURE
QTYPEIHG 317 QUANTITY PER END ITEM
QTYPEIXC 317 SYSTEM/EI QUANTITY PER END ITEM
QTYPROHP 322 QUANTITY PROCURED
QTYSHPHP 323 QUANTITY SHIPPED
QTYTSTEM 320 SYSTEM EQUIPMENT QUANTITY PER TEST
QTYUPKHF 321 QUANTITY PER UNIT PACK

-R-

RAILTCJB 325 RAIL TRANSPORTATION COUNTRY


RAILUSJB 326 RAIL USE
RAMCNABB 341 RAM CHARACTERISTICS NARRATIVE CODE
RAMCNABB(A) 180 ITEM FUNCTION
RAMCNABB(B) 207 MAINTENANCE CONCEPT
RAMCNABB(C) 244 MINIMUM EQUIPMENT LIST NARRATIVE
RAMCNABB(D) 315 QUALITATIVE & QUANTITATIVE MAINTAINABILITY REQUIREMENTS
RAMCNABB(E) 210 MAINTENANCE PLAN RATIONALE
RAMINDBD 347 RAM INDICATOR CODE
RAMINDXB 342 RELIABILITY AVAILABILITY MAINTAINABILITY INDICATOR
RAMNARBB --- RAM CHARACTERISTICS NARRATIVE
RATIOBHM 030 BASIS OF ISSUE END ITEM
RCBINCXA 333 RECURRING BIN COST
RCCATCXA 334 RECURRING CATALOGUING COST
RCMDSABF 084 RCM DISPOSITION A
RCMDSBBF 084 RCM DISPOSITION B
RCMDSCBF 084 RCM DISPOSITION C
RCMDSDBF 084 RCM DISPOSITION D
RCMDSEBF 084 RCM DISPOSITION E
RCMDSFBF 084 RCM DISPOSITION F
RCMDSGBF 084 RCM DISPOSITION G
RCMDSHBF 084 RCM DISPOSITION H
RCMDSIBF 084 RCM DISPOSITION I

3E-43
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


RCMDSJBF 084 RCM DISPOSITION J
RCMLOGAA 345 RELIABILITY CENTERED MAINTENANCE LOGIC UTILIZED
RCMR01BF 344 RELIABILITY CENTERED MAINTENANCE (RCM) LOGIC RESULTS 01
RCMR02BF 344 RCM LOGIC RESULTS 02
RCMR03BF 344 RCM LOGIC RESULTS 03
RCMR04BF 344 RCM LOGIC RESULTS 04
RCMR05BF 344 RCM LOGIC RESULTS 05
RCMR06BF 344 RCM LOGIC RESULTS 06
RCMR07BF 344 RCM LOGIC RESULTS 07
RCMR08BF 344 RCM LOGIC RESULTS 08
RCMR09BF 344 RCM LOGIC RESULTS 09
RCMR10BF 344 RCM LOGIC RESULTS 10
RCMR11BF 344 RCM LOGIC RESULTS 11
RCMR12BF 344 RCM LOGIC RESULTS 12
RCMR13BF 344 RCM LOGIC RESULTS 13
RCMR14BF 344 RCM LOGIC RESULTS 14
RCMR15BF 344 RCM LOGIC RESULTS 15
RCMR16BF 344 RCM LOGIC RESULTS 16
RCMR17BF 344 RCM LOGIC RESULTS 17
RCMR18BF 344 RCM LOGIC RESULTS 18
RCMR19BF 344 RCM LOGIC RESULTS 19
RCMR20BF 344 RCM LOGIC RESULTS 20
RCMR21BF 344 RCM LOGIC RESULTS 21
RCMR22BF 344 RCM LOGIC RESULTS 22
RCMR23BF 344 RCM LOGIC RESULTS 23
RCMR24BF 344 RCM LOGIC RESULTS 24
RCMR25BF 344 RCM LOGIC RESULTS 25
RCURCSEA 332 RECURRING COST
RDCODEHJ 336 REFERENCE DESIGNATION CODE
REASUPEK 327 REASON FOR SUPERCEDURE/DELETION
REFALCCA 019 REFERENCED ALTERNATE LCN CODE
REFALCRI 019 REFERENCED FMI ALC
REFDESHJ 335 REFERENCE DESIGNATION
REFEIACA 096 REFERENCED EIAC
REFFMIRI 134 REFERENCED FAILURE MODE INDICATOR
REFLCNCA 199 REFERENCED LCN
REFLCNRI 199 REFERENCED FMI LCN
REFLTYRI 203 REFERENCED FMI LCN TYPE
REFNCCHA 338 REFERENCE NUMBER CATEGORY CODE
REFNUMHA 337 REFERENCE NUMBER
REFNUMHB 337 ARN ITEM REFERENCE NUMBER
REFNUMHC 337 ITEM REFERENCE NUMBER
REFNUMHN 337 S/N PROVISIONING REFERENCE NUMBER
REFNUMHO 337 UOC PROVISIONING REFERENCE NUMBER
REFNUMWE 337 ACRN REFERENCE NUMBER
REFNUMWF 337 PRIME REFERENCE NUMBER
REFNVCHA 339 REFERENCE NUMBER VARIATION CODE
REFTSKCA 427 REFERENCED TASK CODE
REFTYPCA 203 REFERENCED LCN TYPE
REMARKHI 311 PROVISIONING REMARKS
REMIPIHG 348 REMAIN IN PLACE INDICATOR
REPLEVWY 910 LCN REPLACEMENT LEVEL
REPSURHG 351 REPAIR SURVIVAL RATE (RSR)
REQFITWY 929 REQUIRED FIT
RESTCRXA 359 RETAIL STOCKAGE CRITERIA
REVASSEA 361 REVOLVING ASSETS
REVREMEG 417 SERD REVISION REMARKS
RFDALCCB 019 REFERENCED SUBTASK ALTERNATE LCN CODE
RFDEIACB 096 REFERENCED SUBTASK EIAC
RFDLCNCB 199 REFERENCED SUBTASK LCN
RFDSUBCB 407 REFERENCED SUBTASK NUMBER
RFDTCDCB 427 REFERENCED SUBTASK TASK CODE
RFDTYPCB 203 REFERENCED SUBTASK LCN TYPE

3E-44
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


RICRITBK 178 RAM ITEM CRITICALITY NUMBER
RILPTDHG 313 REPAIRABLE ITEMS LIST (PTD)
RISSBUHG 328 RECOMMENDED INITIAL SYSTEM STOCK BUY
RMSSLIHG 329 RECOMMENDED MINIMUM SYSTEM STOCK LEVEL
RNGFRMEC 284 SE PARAMETER RANGE FROM
RNGTOCEC 284 SE PARAMETER RANGE TO
ROLCODVR 965 ROLE CODE
ROLDESVR 967 ROLE DESCRIPTION
ROLREQVT 966 ROLE REQUIRED FIT
RPPCIVGB 330 RECOMMENDED CIVILIAN GRADE
RPPMILGB 330 RECOMMENDED MILITARY RANK/RATE
RPRLVLEA 277 SE REPAIR OPERATIONS/MAINTENANCE LEVEL
RPWSCSAI 352 REPAIR WORK SPACE COST
RQAMCDVA 943 REQUIREMENTS AMPLIFICATION CODE
RQDSTKAI 357 REQUIRED DAYS OF STOCK
RSPINDHP 354 R-S PLISN INDICATOR
RSPLISHP 353 REPLACED OR SUPERSEDING (R-S) PROVISIONING LIST ITEM
SEQUENCE NUMBER (PLISN)
RTLLQTHG 331 RECOMMENDED TENDER LOAD LIST QUANTITY

-S-

SAFLVLXA 363 SAFETY LEVEL


SAIPCDHA 391 SPARES ACQUISITION INTEGRATED WITH PRODUCTION (SAIP)
SAPLISHG 364 SAME AS PLISN
SBMMETCB 227 SUBTASK MEAN MINUTE ELAPSED TIME
SCAGECEM 046 SYSTEM CAGE CODE
SCPPTDHG 313 SYSTEM CONFIGURATION PROVISIONING PARTS LIST (PTD)
SCRSSCGB 369 SECURITY CLEARANCE REQUIRED
SCRTRQRN 968 SUBTASK CERTIFICATION REQUIREMENT
SDECKSJB 072 SEA DECK STOWAGE
SDSICGJC 384 SKID AREA
SECAGEEA 046 SUPPORT EQUIPMENT (SE) CAGE CODE
SECCLEBA 369 SECURITY CLEARANCE
SECITMXB 367 SECTIONALIZED ITEM TRANSPORTATION INDICATOR
SECSFCXA 421 SUPPORT OF SUPPORT EQUIPMENT COST FACTOR
SECTIDJA 366 SECTIONALIZED IDENTIFICATION
SEGRCDEA 413 SE GROUPING
SEICCDEA 177 SE ITEM CATEGORY CODE
SEINARAK --- SYSTEM END ITEM NARRATIVE
SEINCDAK 424 SYSTEM/END ITEM NARRATIVE CODE
SEINCDAK(A) 010 ADDITIONAL SUPPORTABILITY CONSIDERATIONS
SEINCDAK(B) 011 ADDITIONAL SUPPORTABILITY PARAMETERS
SEINCDAK(C) 274 OPERATIONAL MISSION FAILURE DEFINITION
SEMTBFEA 229 SE MTBF
SEMTTREA 236 SE MTTR
SENARCEE 414 SE NARRATIVE CODE
SENARCEE(A) 147 FUNCTIONAL ANALYSIS
SENARCEE(B) 078 DESCRIPTION AND FUNCTION OF SE
SENARCEE(C) 415 SE NONPROLIFERATION EFFORT
SENARCEE(D) 044 CHARACTERISTICS OF SE
SENARCEE(E) 169 INSTALLATION FACTORS OR OTHER FACILITIES
SENARCEE(F) 008 ADDITIONAL SKILLS AND SPECIAL TRAINING REQUIREMENTS
SENARCEE(G) 411 SE EXPLANATION
SENARCEE(H) 188 JUSTIFICATION
SENTRAEA 371 SENSORS OR TRANSDUCERS
SEQNAREE --- SE NARRATIVE
SEQNUMWF 919 ACRN SET SEQUENCE NUMBER
SEQTYAED 399 SE QUANTITY PER ACTIVITY
SERDESAA 376 SERVICE DESIGNATOR CODE
SERDESAI 376 MODELLING SERVICE DESIGNATOR CODE
SERDESEA 376 SE SERVICE DESIGNATOR
SERDNOEF 416 SE RECOMMENDATION DATA (SERD) NUMBER

3E-45
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


SEREFNEA 337 SE REFERENCE NUMBER
SEREQDEA 418 SE REQUIRED
SERICCEA 356 REPORTABLE ITEM CONTROL CODE
SERLEVVB 954 SERVICING LEVEL
SESHPHEA 419 SE SHIPPING HEIGHT
SESHPLEA 419 SE SHIPPING LENGTH
SESHPWEA 419 SE SHIPPING WIDTH
SESHWTEA 420 SE SHIPPING WEIGHT
SEUPGCUN 284 SE UUT PARAMETER GROUP CODE
SFPPTDHG 313 SHORT FORM PROVISIONING PARTS LIST (PTD)
SHLIFEHA 377 SHELF LIFE (SL)
SHPCONJB 380 SHIPPING CONFIGURATION
SHPDISAJ 085 SHIP DISTANCE
SHWEEMJC 381 SHIPPING WEIGHT EMPTY
SHWELDJC 381 SHIPPING WEIGHT LOADED
SIASCNEA 401 STANDARD INTERSERVICE AGENCY SERIAL CONTROL NUMBER
SIGNUPWN 936 SIGN UP REQUIREMENT
SKADUMJC 491 SKID AREA UNIT OF MEASURE
SKETCHEA 383 SKETCH
SKLVCDGA 386 SKILL LEVEL CODE
SKSPCDGA 387 SKILL SPECIALTY CODE
SLACTNHA 378 SHELF LIFE ACTION CODE (SLAC)
SLFTSTEA 370 SELF TEST CODE
SMAINCHA 392 SPECIAL MAINTENANCE ITEM CODE (SMIC)
SMDTECCA 237 SECONDARY MEANS OF DETECTION
SMMNSNHA 253 NSN SPECIAL MATERIAL IDENTIFICATION CODE/MATERIEL
MANAGEMENT AGGREGATION CODE
SMRCODHG 389 SOURCE, MAINTENANCE AND RECOVERABILITY CODE
SMRCSEEA 389 SE SOURCE, MAINTENANCE AND RECOVERABILITY CODE
SMTBMAEA 230 SE MTBMA
SNUMSKJC 264 SKID NUMBER OF SKIDS
SNUUOCXD 375 SERIAL NUMBER USABLE ON CODE
SPARIOEC 284 SE PARAMETER INPUT/OUTPUT CODE
SPDATEHF 187 SPI NUMBER JULIAN DATE
SPEMRKHF 394 SPECIAL MARKING CODE
SPINUMHF 396 SPECIAL PACKAGING INSTRUCTIONS (SPI) NUMBER
SPIREVHF 397 SPI NUMBER REVISION
SPMACCHA 395 SPECIAL MATERIAL CONTENTS CODE (SMCC)
SPMGNTEA 393 SPECIAL MANAGEMENT CODE
SPRCAGEK 046 SE SUPERCEDURE CAGE CODE
SPRFACEA 390 SPARE FACTOR
SPRREFEK 337 SE SUPERCEDURE REFERENCE NUMBER
SPSPEDJA 400 SPEED
SQPQTYJE 298 SECOND QUARTER PROCUREMENT QUANTITY
SQTKUMCG 491 SUPPORT ITEM QUANTITY PER TASK UNIT OF MEASURE
SQTYTKCG 319 SUPPORT ITEM QUANTITY PER TASK
SRDREVEF 360 SERD REVISION
SREFNOEM 337 SYSTEM REFERENCE NUMBER
SRVALCWO 019 SERVICING TASK ALC
SRVCIDWM 933 SERVICING IDENTIFIER
SRVCLDRF 933 CLAIMED ACTIVITY SERVICING IDENTIFIER
SRVCLGRF 933 CLAIMING ACTIVITY SERVICING IDENTIFIER
SRVLCNWO 199 SERVICING TASK LCN
SRVLTYWO 203 SERVICING TASK LCN TYPE
SSCOPREA 387 SKILL SPECIALTY CODE (SSC) FOR SE OPERATOR (SEO)
SSCTESGB 449 TEST SCORE
SSECDECD 388 SKILL SPECIALTY EVALUATION CODE
SSTALCRP 019 SERVICING SUBTASK ALC
SSTCODRP 427 SERVICING SUBTASK TASK CODE
SSTLCNRP 199 SERVICING SUBTASK LCN
SSTLTYRP 203 SERVICING SUBTASK LCN TYPE
SSTNUMRP 407 SERVICING SUBTASK NUMBER
STABYTBE 403 STANDBY TIME

3E-46
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


STATUSEF 404 SERD STATUS
STOHGTEA 405 STORAGE HEIGHT
STOLENEA 405 STORAGE LENGTH
STOWDTEA 405 STORAGE WIDTH
STOWGTEA 406 STORAGE WEIGHT
SUBMMMCD 226 SUBTASK MEAN MAN-MINUTES
SUBNARCC 372 SEQUENTIAL SUBTASK DESCRIPTION
SUBNARRO 372 SERVICING SUBTASK NARRATIVE
SUBNUMCB 407 SUBTASK NUMBER
SUBNUMRN 407 SERVICING SUBTASK NUMBER
SUBPIDCD 288 SUBTASK PERSON IDENTIFIER
SUBTIDCB 431 SUBTASK IDENTIFICATION
SUBTIDRN 431 SERVICING SUBTASK IDENTIFICATION
SUBWACCB 514 SUBTASK WORK AREA CODE
SUPCONBA 410 SUPPORT CONCEPT
SUPINDHG 422 SUPPRESSION INDICATOR
SUPITNEK 182 SE SUPERCEDURE ITEM NAME
SUPPKDHF 409 SUPPLEMENTAL PACKAGING DATA
SUSRNOEK 416 SE SUPERCEDURE SERD NUMBER
SUTALLUM 016 SE UUT ALLOWANCE
SUTCAGUM 046 SE UNIT UNDER TEST (SE UUT) CAGE CODE
SUTREFUM 337 SE UUT REFERENCE NUMBER
SUTSTCUM 036 SE UUT CMRS STATUS
SUTYPEEK 408 SE SUPERCEDURE TYPE
SVCINTWP 934 SERVICING INTERVAL
SVTITLWN 935 SERVICING TITLE
SYSIDNXB 423 SYSTEM/END ITEM IDENTIFIER

-T-

TALCNCBH 019 TASK REQUIREMENT ALTERNATE LCN CODE


TASKCDCA 427 TASK CODE
TASKIDCA 431 TASK IDENTIFICATION
TATYPEBH 433 TASK TYPE
TCONDACA 428 TASK CONDITION A
TCONDBCA 428 TASK CONDITION B
TCONDCCA 428 TASK CONDITION C
TECEVLEA 435 TECHNICAL EVALUATION PRIORITY CODE
TEMTBFAG 229 REQUIRED TECHNICAL MEAN TIME BETWEEN FAILURES
TEMTBFBD 229 MEAN TIME BETWEEN FAILURES TECHNICAL
TEMTTRAA 236 REQUIRED TECHNICAL MEAN TIME TO REPAIR
TEXSEQAF 450 ADDITIONAL REQUIREMENTS TEXT SEQUENCING CODE
TEXSEQAK 450 SYSTEM END ITEM NARRATIVE TEXT SEQENCING CODE
TEXSEQBB 450 RAM CHARACTERISTICS NARRATIVE TEXT SEQUENCING CODE
TEXSEQBC 450 RAM LOGISTICS CONSIDERATIONS TEXT SEQUENCING CODE
TEXSEQBG 450 FAILURE MODE & RCM NARRATIVE TEXT SEQUENCING CODE
TEXSEQBJ 450 FMI MISSION PHASE CHARACTERISTICS NARRATIVE TEXT SEQUENCING
CODE
TEXSEQCC 450 SEQUENTIAL SUBTASK DESCRIPTION TEXT SEQUENCING CODE
TEXSEQEE 450 SE NARRATIVE TEXT SEQUENCING CODE
TEXSEQEG 450 SERD REVISION TEXT SEQUENCING CODE
TEXSEQFB 450 FACILITY NARRATIVE TEXT SEQUENCING CODE
TEXSEQFC 450 BASELINE FACILITY NARRATIVE TEXT SEQUENCING CODE
TEXSEQFD 450 NEW OR MODIFIED FACILITY NARRATIVE TEXT SEQUENCING CODE
TEXSEQGC 450 NEW OR MODIFIED SKILL NARRATIVE TEXT SEQUENCING CODE
TEXSEQGE 450 PHYSICAL AND MENTAL REQUIREMENTS TEXT SEQUENCING CODE
TEXSEQHI 450 PROVISIONING TEXT SEQUENCING CODE
TEXSEQHL 450 PARTS MANUAL TEXT SEQUENCING CODE
TEXSEQJD 450 TRANSPORTED END ITEM NARRATIVE TEXT SEQUENCING CODE
TEXSEQJF 450 TRANSPORTATION NARRATIVE TEXT SEQUENCING CODE
TEXSEQMA 450 TASK MEMO TEXT SEQUENCING CODE
TEXSEQMB 450 SKILL SPECIALTY MEMO TEXT SEQUENCING CODE
TEXSEQMC 450 SERVICING TASK MEMO TEXT SEQUENCING CODE

3E-47
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


TEXSEQMD 450 TASK FACILITY MEMO TEXT SEQUENCING CODE
TEXSEQME 450 LCN ITEM TEXT SEQUENCING CODE
TEXSEQMF 450 SERVICING TEXT SEQUENCING CODE
TEXSEQRB 450 WAC DESCRIPTION TEXT SEQUENCING CODE
TEXSEQRO 450 SERVICING SUBTASK NARRATIVE TEXT SEQUENCING NUMBER
TEXSEQUF 450 UUT EXPLANATION TEXT SEQUENCING CODE
TEXTTOCK 450 SEQUENTIAL SUBTASK DESCRIPTION TEXT SEQUENCING CODE TO
TFQNARWC 964 HISTORICAL TASK FREQUENCY NARRATIVE
TGSCAGUN 046 TESTING SUPPORT EQUIPMENT (SE) CAGE CODE
TGSREFUN 337 TESTING SE REFERENCE NUMBER
TIMESHAJ 379 SHIP TIME
TINMETAD 280 TURNROUND INSPECTION MEAN ELAPSED TIME
TINMMHAD 280 TURNROUND INSPECTION MEAN MAN-HOURS
TLCNTYBH 203 TASK REQUIREMENT LCN TYPE
TLSACNBH 199 TASK REQUIREMENT LCN
TMAMDTAA 223 TECHNICAL MEAN ACTIVE MAINTENANCE DOWNTIME
TMCHGNHK 436 TECHNICAL MANUAL CHANGE NUMBER
TMCODEXI 437 TECHNICAL MANUAL (TM) CODE
TMCSTAWG 939 TECHNICAL MANAGEMENT CODE STATUS
TMDERCEA 444 TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT REGISTER CODE
(TMDE CODE)
TMDERIEA 445 TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT REGISTER INDEX
NUMBER
TMFGCDHK 438 TM FUNCTIONAL GROUP CODE (REPAIR PARTS MANUAL)
TMFGCDXB 438 TECHNICAL MANUAL FUNCTIONAL GROUP CODE (MAINTENANCE
ALLOCATION CHART)
TMINDCHK 439 TECHNICAL MANUAL INDENTURE CODE
TMNTCDWG 938 TECHNICAL MANAGEMENT CODE
TMNUMBXI 440 TECHNICAL MANUAL NUMBER
TMRQCDEA 441 TECHNICAL MANUAL REQUIRED CODE
TMTBFMBD 238 MEAN TIME BETWEEN FAILURES TECHNICAL MEASUREMENT BASE
TMTBMAAG 230 REQUIRED TECHNICAL MEAN TIME BETWEEN MAINTENANCE ACTIONS
TMTBMABD 230 MTBMA TECHNICAL
TMTBMMBD 238 MTBMA TECHNICAL MEASUREMENT BASE
TOBTCHWE 917 TO BATCH NUMBER
TOCCODHG 481 TYPE OF CHANGE CODE (TOCC)
TOCCODXC 481 SYSTEM/EI TYPE OF CHANGE CODE
TOSNUMHN 373 S/N PROVISIONING SERIAL NUMBER TO
TOSNUMXD 373 SERIAL NUMBER TO
TOSNUMXE 373 S/N SERIAL NUMBER TO
TOSRNOHQ 374 TO SERIAL NUMBER EFFECTIVITY
TOSYSUAA 454 TOTAL SYSTEMS SUPPORTED
TOTICHHP 452 TOTAL ITEM CHANGES
TOTQTYHG 453 TOTAL QUANTITY RECOMMENDED
TPAUCNUE 025 TPI APPORTIONED UNIT COST NONRECURRING
TPAUCRUE 025 TPI APPORTIONED UNIT COST RECURRRING
TPICAGUE 046 TEST PROGRAM INSTRUCTION (TPI) CAGE CODE
TPIREFUE 337 TPI REFERENCE NUMBER
TPISRDUE 416 TPI SUPPORT EQUIPMENT RECOMMENDATION DATA NUMBER
TPISTSUE 370 TPI SELF TEST
TPITDPUE 434 TPI TECHINCAL DATA PACKAGE
TPSAUMJC 491 TRACKED PAD SHOE AREA UNIT OF MEASURE
TQPQTYJE 298 THIRD QUARTER PROCUREMENT QUANTITY
TRAFYRJE 145 TRANSPORT FISCAL YEAR
TRANARJF --- TRANSPORTATION NARRATIVE
TRANCDJF 470 TRANSPORTATION NARRATIVE CODE
TRANCDJF(A) 382 TRANSPORTATION SHOCK VIBRATION REMARKS
TRANCDJF(B) 192 LIFTING AND TIEDOWN REMARKS
TRANCDJF(C) 471 TRANSPORTATION PROJECTION REMARKS
TRANCDJF(D) 340 REGULATORY REQUIREMENTS
TRANCDJF(E) 472 TRANSPORTATION REMARKS
TRANCDJF(F) 398 SPECIAL SERVICE AND EQUIPMENT
TRANCDJF(G) 368 SECTIONALIZED REMARKS

3E-48
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


TRANCDJF(H) 476 TRANSPORTED TO AND FROM
TRANCDJF(I) 099 ENVIRONMENTAL/HAZARDOUS MATERIALS CONSIDERATIONS
TRANCDJF(J) 240 MILTARY DISTANCE CLASSIFICATION
TRANCDJF(K) 500 UNUSUAL AND SPECIAL REQUIREMENTS
TRANCDJF(L) 504 VENTING AND PROTECTIVE CLOTHING
TRANCDJF(M) 082 DISASTER RESPONSE FORCE REQUIREMENTS
TRANCNJB 465 TRANSPORTATION CHARACTER NUMBER
TRASEIXC 467 TRANSPORTATION END ITEM INDICATOR
TRCHMTJB 464 TRANSPORTATION CHARACTER MODE TYPE
TRCHRDJA 071 REVISION DATE
TRCHTHJA 451 THEATRE OF OPERATION
TRCONMJC 473 TRANSPORTED CONFIGURATION NUMBER
TRDNUMUM 448 SE UUT TEST REQUIREMENTS DOCUMENT NUMBER
TREINCJD 474 TRANSPORTED END ITEM NARRATIVE CODE
TREINCJD(A) 511 WHEELED TIRE REQUIREMENTS
TREINCJD(B) 385 SKID REMARKS
TREINCJD(C) 477 TURNING INFORMATION
TREINCJD(D) 506 WHEELED AXLE AND SUSPENSION REMARKS
TREINCJD(E) 475 TRANSPORTED OTHER EQUIPMENT
TRGRPRJC 456 TRACKED GROUND PRESSURE
TRITDRJB 469 TRANSPORTATION ITEM DESIGNATOR
TRNCOSGA 460 TRAINING COST
TRNCSTXA 466 TRANSPORTATION COST
TRNINDJA 468 TRANSPORTATION INDICATOR
TRNLOCCA 461 TRAINING LOCATION RATIONALE
TRNRATCA 462 TRAINING RATIONALE
TRNRECCA 463 TRAINING RECOMMENDATION TYPE
TRNRQCCA 358 TRAINING EQUIPMENT REQUIREMENT CODE
TRNUPTJC 458 TRACKED PADS TOUCHING
TRPSARJC 457 TRACKED PAD SHOE AREA
TRRWWTJC 459 TRACKED ROAD WHEEL WEIGHT
TSCAGECG 046 TASK SUPPORT CAGE CODE
TSEREQCA 358 TOOL/SUPPORT EQUIPMENT REQUIREMENT CODE
TSFROMCK 450 SEQUENTIAL SUBTASK DESCRIPTION TEXT SEQUENCING CODE FROM
TSKALCCI 019 TASK ALTERNATE LCN CODE (ALC)
TSKCLDRG 427 CLAIMED ACTIVITY TASK CODE
TSKCLGRG 427 CLAIMING ACTIVITY TASK CODE
TSKCRCCA 429 TASK CRITICALITY CODE
TSKFRQCA 430 TASK FREQUENCY
TSKINTWB 937 TASK INTERVAL
TSKLCNCI 199 TASK LSA CONTROL NUMBER (LCN)
TSKLTYCI 203 TASK LCN TYPE
TSKREMCE 432 TASK REMARKS
TSKRRCCE 349 TASK REMARK REFERENCE CODE
TSKSEQWT 932 SERVICING GROUP TASK SEQUENCE NUMBER
TSKTCDCI 427 TASK PROVISION TASK CODE
TSKTIMVE 961 FACILITY TASK TIME
TSKTMBVE 238 FACILITY TASK TIME MEASUREMENT BASE
TSREFNCG 337 TASK SUPPORT REFERENCE NUMBER
TSSCODXA 484 TYPE OF SUPPLY SYSTEM CODE
TSTLNGEA 443 TEST LANGUAGE
TSTPTSEA 446 TEST POINTS
TTASKCBH 427 TASK CODE
TTLPTDHG 313 TOOL AND TEST EQUIPMENT LIST (PTD)
TUIPRCHD 485 UI PRICE TYPE OF PRICE CODE
TUMPRCHE 485 UM PRICE TYPE OF PRICE CODE
TWALFIJC 029 LENGTH FRONT INSIDE
TWALFOJC 029 LENGTH FRONT OUTSIDE
TWALRIJC 029 LENGTH REAR INSIDE
TWALROJC 029 LENGTH REAR OUTSIDE
TWSPEDJA 455 TOWING SPEED
TYPACTED 399 TYPE OF ACTIVITY
TYPCLSEA 479 TYPE CLASSIFICATION

3E-49
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)


TYPDESRC 916 INITIATING TYPE DESCRIPTION
TYPEEQEA 480 TYPE EQUIPMENT CODE

-U-

UCLEVLHF 487 UNIT CONTAINER LEVEL


UHEIGHHA 496 UNIT SIZE HEIGHT
UICONVHA 489 UNIT OF ISSUE CONVERSION FACTOR (UI CONVERSION FACTOR)
UIPRICHD 490 UNIT OF ISSUE PRICE (UI PRICE)
ULENGTHA 496 UNIT SIZE LENGTH
UMNTPLUA 209 UUT MAINTENANCE PLAN NUMBER
UMPRICHE 492 UNIT OF MEASURE (UM) PRICE
UMSEWTEA 491 SE SHIPPING WEIGHT UNIT OF MEASURE
UMSHIPEA 491 SE SHIPPING DIMENSIONS UNIT OF MEASURE
UNICONHF 486 UNIT CONTAINER CODE
UNITISHA 488 UNIT OF ISSUE (UI)
UNITMSHA 491 UNIT OF MEASURE
UNKNOWN 963 FUNCTIONAL FAILURE
UNPKCUHF 493 UNIT PACK CUBE
UNPKWTHF 495 UNIT PACK WEIGHT
UOCSEIXC 501 USABLE ON CODE (UOC)
USESEREA 376 USING SERVICE DESIGNATOR CODE
UTALLOUA 016 UUT ALLOWANCE
UTCMRSUB 035 UUT CMRS RECOMMENDED CODE
UTEXPLUF 498 UUT EXPLANATION
UTLCNTUA 203 UUT LCN TYPE
UTPAACUN 284 SE UUT PARAMETER ACCURACY
UTPACMUN 034 SE UUT CMRS PARAMETER CODE
UTPAIOUN 284 SE UUT PARAMETER INPUT/OUTPUT CODE
UTPAPAUN 284 SE UUT PARAMETER
UTPARVUN 284 SE UUT PARAMETER RANGE/VALUE CODE
UTPATAUN 442 SE UUT PARAMETER TEST ACCURACY RATIO (TAR) ACTUAL
UTPATDUN 442 SE UUT PARAMETER TAR DESIRED
UTPRRTUN 284 SE UUT PARAMETER RANGE TO
UTRATIAE 503 UTILIZATION RATIO
UTRGFRUN 284 SE UUT PARAMETER RANGE FROM

UTSTCDUB 036 UUT CALIBRATION/MEASUREMENT REQUIREMENT SUMMARY (CMRS)


STATUS
UTTRDNUA 448 UUT TEST REQUIREMENTS DOCUMENT NUMBER
UTWPRFUA 515 UUT WORK PACKAGE REFERENCE
UUTALCUA 019 UUT ALTERNATE LCN CODE
UUTFA1UH 143 UUT FIRU AMBIGUITY GROUP 1
UUTFA2UH 143 UUT FIRU AMBIGUITY GROUP 2
UUTFP1UH 143 UUT FIRU PERCENT FAILURE 1
UUTFP2UH 143 UUT FIRU PERCENT FAILURE 2
UUTFTDUH 447 UUT FIRU TEST REQUIREMENTS DOCUMENT INDICATOR
UUTLCNUA 199 UUT LSA CONTROL NUMBER (LCN)
UUTPACUG 284 UUT PARAMETER ACCURACY
UUTPARUG 284 UUT PARAMETER
UUTPGCUG 284 UUT PARAMETER GROUP CODE
UUTPIOUG 284 UUT PARAMETER INPUT/OUTPUT CODE
UUTPPCUG 034 UUT CALIBRATION MEASUREMENT REQUIRMENT SUMMARY
PARAMETER CODE
UUTPRFUG 284 UUT PARAMETER RANGE FROM
UUTPRTUG 284 UUT PARAMETER RANGE TO
UUTPRVUG 284 UUT PARAMETER RANGE/VALUE CODE
UUTPSOUG 284 UUT PARAMETER OPERATIONAL/SPECIFICATION CODE
UUTPTAUG 442 UUT PARAMETER TEST ACCURACY RATIO (TAR) ACTUAL
UUTPTDUG 442 UUT PARAMETER TAR DESIRED
UWEIGHHA 497 UNIT WEIGHT
UWIDTHHA 496 UNIT SIZE WIDTH

3E-50
DEF(AUST)5692

CODE DED DATA ELEMENT TITLE (ROLE NAMED)

-W-

WACDESRB 996 WORK AREA CODE DESCRIPTION


WACNAMRA 997 WORK AREA CODE NAME
WACODERA 940 WORK AREA CODE
WEOULIBA 505 WEAROUT LIFE
WGTOUMEA 491 OPERATING WEIGHT UNIT OF MEASURE
WGTSUMEA 491 STORAGE WEIGHT UNIT OF MEASURE
WHINPRJC 507 WHEELED INFLATION PRESSURE
WHNUPLJC 508 WHEELED NUMBER OF PLIES
WHNUTIJC 509 WHEELED NUMBER TIRES
WHTIFTJC 512 WHEELED TIRE SIZE
WHTLDRJC 510 WHEELED TIRE LOAD RATINGS
WHTRLOJD --- TRANSPORTED END ITEM NARRATIVE
WHWERAJC 513 WHEELED WEIGHT RATINGS
WIDUPKHF 494 UNIT PACK WIDTH
WKPKRFUM 515 SE UUT WORK PACKAGE REFERENCE
WOLIMBBA 238 WEAROUT LIFE MEASUREMENT BASE
WPADDRAF 009 ADDITIONAL REQUIREMENTS
WRAPMTHF 517 WRAPPING MATERIAL
WRKUCDHG 516 WORK UNIT CODE
WSOPLVXA 271 OPERATION LEVEL
WSTYAQXA 478 TYPE ACQUISITION

-Y-

YRFLDGEA 518 YEAR OF FIELDING

3E-51
DEF(AUST)5692