0% found this document useful (0 votes)

638 views791 pages

Mil STD 2549

This standard cannot be cited in a contract without citing the specific data information subpackets. The goal of this document is to establish a standard interface for the delivery of, or access to, electronic configuration management data. This standard is directed toward improving the cost effectiveness of the generation, maintenance, acquisition, and use of the technical data required to support a configuration management program.

Uploaded by

macarsal

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

638 views791 pages

Mil STD 2549

Uploaded by

macarsal

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 791

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

NOT MEASUREMENT
SENSITIVE

MIL-STD-2549
30 June 1997

DEPARTMENT OF DEFENSE
INTERFACE STANDARD

CONFIGURATION MANAGEMENT
DATA INTERFACE

AMSC D7235 AREA CMAN

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

FOREWORD

1. This Military Standard is approved for use by all Departments and Agencies of the Department of Defense (DoD).
This standard cannot be cited in a contract without citing the specific data information subpackets. If this standard is
cited as a whole without citing specific data information subpackets, the contractor is not required to comply with this
standard.

2. This standard is the result of joint efforts of the military services and industry. The goal of this document is to
establish a standard interface for the delivery of, or access to, electronic configuration management data. MIL-STD-973
accommodates digital configuration management data, but because it does not standardize data at the data element level,
it does not enable sharing of digital data. In order to allow for the efficient transition to the shared integrated digital data
environment described by this standard, MIL-STD-973 will remain in effect temporarily.

3. This standard is based on sound configuration management principles. The data interface described in this document
is established through specification of a standard relational data base conceptual schema (business rules view),
intentionally structured to accommodate the maximum range of data potentially required by the services for
configuration management of their materiel and its supporting technical data. This standard presents the data element
relationships needed to allow both services and contractors to exchange all required configuration management
information and product data, either directly or through an appropriate integrated data environment. This approach
standardizes field lengths and data element definitions (DEDs) and establishes “one face to industry” for DoD-required
configuration management data.

4. This standard is directed toward improving the cost effectiveness of the generation, maintenance, acquisition, and use
of the technical data required to support a configuration management program. This is accomplished through the
following:

a. Standardization of the configuration management DEDs, field lengths, and formats between the services and
industry.

b. Consolidation of configuration management information into a defined virtual repository environment to reduce
redundancy, facilitate timely access, and ensure consistency between the various user elements.

c. Maximum utilization of industry developed integrated data systems tied to engineering, manufacturing, and product
support data bases as sources of configuration management related data and documentation.

d. Harmonization of configuration management data elements with other DoD, national, and international standards.

5. This standard does not prescribe automated information system software that must be used to process configuration
management data.

6. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in
improving this document should be addressed to: Director, CALS, 5203 Leesburg Pike, Suite 1609, Falls Church, VA
22041-3466, by using the self-addressed Standardization Document Improvement Proposal (DD Form 1426) appearing
at the end of this document or by electronic mail to: burghels@acq.osd.mil.

ii
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

CONTENTS

PARAGRAPH PAGE

1. SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2. Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3. Tailoring of requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2. APPLICABLE DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

3. DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3.1. Acronyms used in this standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3.2. Definitions used in this standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4. GENERAL REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2. Configuration identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2.1. Configuration identification of configuration items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2.2. Configuration identification of parts and assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.3. Configuration identification of materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.4. Configuration identification of software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.5. Configuration identification of documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.6 Configuration identification of document representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.7. Configuration identification of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2.8. Secondary configuration identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3. Configuration documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.1. Performance-based procurement of a nonrepairable item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.2. Performance-based procurement of a repairable item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.3. Detailed-design procurement of a repairable item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Configuration control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.1. Change control of documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.2. Configuration control of Government products/assets and their designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.5. Configuration audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.5.1. Configuration audit results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.5.2. Configuration audit action item status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6. Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6.1. On-line review and comment on documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6.2. On-line review and comment on data item submittals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6.3. Document protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6.4. Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5. DETAILED REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1. Data information packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.2. Content of data information packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.3. Validation of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6. NOTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1. Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.2. Associated Data Item Descriptions (DIDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.3. Tailoring guidance for contractual application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.4. Subject term (key word) listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.5. Useful references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

iii
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

DATA INFORMATION PACKET PAGE

1 Drawings, Specifications, Standards, Software, and Software Support Documents . . . . . . . . . . . . . . . . . . . . 23

2 General Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3 Product/Asset Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4 Configuration Change Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5 Configuration Management Action Item Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6 Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7 Engineering Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8 Basic Document Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9 Basic File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
10 Basic Document Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

APPENDIX PAGE

A SELECTION AND TAILORING GUIDANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

B CONFIGURATION STATUS ACCOUNTING RELATIONAL TABLES . . . . . . . . . . . . . . . . . . . . . . . . B-1
C CONFIGURATION STATUS ACCOUNTING (CSA) DATA ELEMENT DEFINITIONS . . . . . . . . . . . C-1
D DATA ELEMENT DICTIONARY CROSS REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

TABLE PAGE

I ECP disposition authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

DIP1-I Drawings, specifications, standards, software, and software support documents . . . . . . . . . . . . . . . . 24
DIP2-I General document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
DIP2-II Reference document identifier DEDs for supplement documents . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
DIP2-III Reference revision identifier DEDs for supplement documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
DIP3-I Product/asset configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
DIP3-II Suitable alternate types of tracking identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
DIP4-I Configuration change control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
DIP4-II Cell contents for ECP cost information spread sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
DIP4-III Cell contents for ECP summation cost spread sheet information . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
DIP5-I Configuration management action item status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
DIP5-II Reference DEDs for technical manual document identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
DIP6-I Organization and staff data information subpackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
DIP6-II Reference entity identifier DEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
DIP6-III System/CI/CCB data item data information subpackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
DIP6-IV Contract/Contract data item data information subpackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
DIP6-V Document/CDRL review, disposition, and direction data information subpackets . . . . . . . . . . . . . . 111
DIP6-VI Baseline, CPIN, PAN data information subpackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
DIP6-VII Transfer of CDCA/document custodian and changes to AA/GLAA . . . . . . . . . . . . . . . . . . . . . . . . 120
DIP7-I Engineering parts list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
DIP7-II Reference DED list for component item identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
DIP8-I Basic document protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
DIP9-I Basic file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
DIP10-I Basic document representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
A-I Selection and tailoring guidance for data information subpackets . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
A-II Guidance on tailoring requirements for drawings and associated lists . . . . . . . . . . . . . . . . . . . . . . . A-6
A-III Guidance on tailoring requirements for program-unique specifications . . . . . . . . . . . . . . . . . . . . . . A-9
A-IV Guidance on tailoring requirements for standardization documents . . . . . . . . . . . . . . . . . . . . . . . . A-11
A-V Guidance on tailoring requirements for software and software administrative information . . . . . . A-13
A-VI Guidance on tailoring requirements for software support documents . . . . . . . . . . . . . . . . . . . . . . . A-14
A-VII Guidance on tailoring requirements for electronic models (paperless drawings) . . . . . . . . . . . . . . A-16

iv
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

14TM4 Technical manuals (Part 4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-239
15SUP1 Document supplements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-248
15SUP2 Document supplements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-249
15SUP3 Document supplements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-250
15SUP4 Document supplements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-251
15SUP5 Document supplements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-252
15SUP6 Document supplements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-253
16DID1 Data Item Description (DID) definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-262
17PAN1 Procuring Activity Number (PAN) correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-264
18AUD1 Audit actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-267
19CI1 Configuration item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-271
19CI2 Configuration control board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-272
21REP1 Document representation release status (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-279
21REP2 Document representation release status (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-280
21REP3 Document representation originating organization review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-281
22REV1 Document revision CDCA approval status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-288
22REV2 Document revision CDCA review status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-289
22REV3 Document revision AA approval status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-290
21REV4 Document revision AA review status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-291
B-1 IDEF3 Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-301
B-2 Document release/approval, case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-302
B-3 Document release/approval, case 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-303
B-4 Document release/approval, case 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-304
B-5 Document release/approval, case 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-305
B-6 Document release/approval, case 5 (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-306
B-6 (cont) Document release/approval, case 5 (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-307
B-7 Document release/approval, case 6 (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-308
B-7 (cont) Document release/approval, case 6 (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-309
23FILE1 File definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-311
24COM1 Company documents/parts/materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-316
24COM2 Company parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-317
24COM3 Company materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-318
24COM4 Company stock number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-319
25ADD1 Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-327
26CON1 Contract & CDRL definition (Part 1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-330
26CON2 Contract & CDRL definition (Part 2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-331
26CON3 Contract data submittal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-332
26CON4 CDRL status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-333
26CON5 CDRL contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-334
26CON6 CDRL-submittal review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-335

vii
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

(This page intentionally left blank)

viii
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

1. SCOPE

1.1. Scope. This document establishes a standard interface for the delivery of, or access to, electronic configuration
management data. This interface prescribes the data elements, the data element definitions, and the data element
relationships that define the conceptual schema for configuration management data. These interface requirements have
been subdivided into data information packets to support various configuration management needs.

1.2. Applicability. This standard applies to all activities responsible for procuring, recording, maintaining, and
disseminating configuration management information.

1.3. Tailoring of requirements. The interface requirements of this standard are applicable only to the extent that
selected portions of specific data information packets are needed to support the configuration management data
requirements identified in a tasking directive or contract statement of work (SOW). This standard shall not be cited in
its entirety. Furthermore, this standard cannot be referenced in a tasking directive or contract SOW to assign
configuration management tasks. If either of these conditions occurs, this standard shall not be binding. The selection of
data information packets from this standard will be tailored to suit the life-cycle phase, complexity, size, intended use
(including joint and combined interoperability), mission criticality, and logistics support of the system/configuration
items (CIs). (See 6.3 for specific tailoring guidance.)

2. APPLICABLE DOCUMENTS

There are no sub-tier documents required for implementation of this document.

3. DEFINITIONS

3.1. Acronyms used in this standard. The acronyms used in this standard are defined as follows:

AA Application Activity
ABL Allocated Baseline
ACD Allocated Configuration Documentation
ACO Administrative Contracting Officer
AECMA Association Europeenne des Construceurs de Materiel Aerospace
AFB [U.S.] Air Force Base
AFM [U.S.] Air Force Manual
AFR [U.S.] Air Force Regulation
AGE Aerospace Ground Equipment
AIA Aeronautical Industry Association
AIS Automated Information System
ALT Alteration Instruction
AMSDL Acquisition Management Systems and Data Requirements Control List
ANSI American National Standards Institute
AR [U.S.] Army Regulation
ARDEC [U.S. Army] Armament Research, Development and Engineering Center
ASCII American Standard Code for Information Interchange
ASTM American Society for the Testing of Materials
BOM Bill of Materials
CAGE Commercial and Government Entity

1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

CALS Continuous Acquisition and Life-cycle Support

CCB Configuration Control Board, Configuration Change Board
CDCA Current Document Change Authority
CDRL Contract Data Requirements List
CFR Code of Federal Regulations
CI Configuration Item
CITIS Contractor Integrated Technical Information Service
CLIN Contract Line Item Number
CM Configuration Management
CMP Configuration Management Plan
CNWDI Critical Nuclear Weapons Design Information
CPIN Computer Program Identification Number
CRYPTO Cryptographic information
CSA Configuration Status Accounting
CSCI Computer Software Configuration Item
DCMC [U.S.] Defense Contract Management Command
DDRS [U.S.] Department of Defense Data Repository System
DED Data Element Definition
DFAR [U.S.] Defense Department supplement to the Federal Acquisition Regulation
DID Data Item Description
DIN Deutsches Industrie Numer
DIP Data Information Packet
DLA [U.S.] Defense Logistics Agency
DoD [U.S.] Department of Defense
DODISS [U.S.] Department of Defense Index of Specifications and Standards
DOE [U.S.] Department of Energy
DOT [U.S.] Department of Transportation
DTIC [U.S.] Defense Technical Information Center
ECN Engineering Change Notice
ECO Engineering Change Order
ECP Engineering Change Proposal
ECS Embedded Computer Software
EDM Enterprise Data Model
EEPROM Electronically Erasable Programmable Read-only Memory
EIA Electronic Industries Association
ELIN Exhibit Line Item Number
Email Electronic mail
FBL Functional Baseline
FCA Functional Configuration Audit
FCD Functional Configuration Documentation
FFT First Flight Test
FSC [U.S.] Federal Supply Class
FSCM [U.S.] Federal Supply Code for Manufacturers
GFD Government-Furnished Documents
GFE Government-Furnished Equipment
GFP Government-Furnished Property
GLAA Government Lead Application Activity
GPLR Government Purpose License Rights
GPO Government Printing Office
GSN Government Serial Number
HEI High Explosive Incendiary
HTML Hypertext Mark-up Language
HWCI Hardware Configuration Item
ICD Interface Control Drawing, Interface Control Documentation

2
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

ICWG Interface Control Working Group

IEEE Institute of Electrical and Electronics Engineering
IFF Identify Friend or Foe.
IGES Initial Graphics Exchange Specification
IPT Integrated Product Team
IRPOD Individual Repair Part Ordering Data
ISO International Standardization Organization
MACHALT Machinery Alteration
MACHALTINST Machinery Alteration Instruction
MICOM [U.S. Army] Missile Command
MIL-STD Military Standard
MIP Modification Improvement Program
MRB Material Review Board
MS Military Standard
MSN Manufacturer's Serial Number
MWO Modification Work Order
NAS [U.S.] National Aerospace Standard
NASA [U.S.] National Aeronautics & Space Administration
NATO North Atlantic Treaty Organization
NAVAIR [U.S.] Naval Air Systems Command
NAVMATINST [U.S.] Naval Materiel Systems Command Instruction
NAVSEA [U.S.] Naval Sea Systems Command
NIIN [U.S.] National Item Identification Number
NIST [U.S.] National Institute of Standards and Technology
NOR Notice of Revision
NSA [U.S.] National Security Agency
NSCM NATO Supply Code for Manufacturers
NSN National Stock Number
NTIS National Technical Information Service
NUCALTINST Nuclear Alteration Instruction
NWS [U.S.] Naval Weapons Station
ORDALTINST Ordnance Alteration Instruction
OSD [U.S.] Office of the Secretary of Defense
OSHA [U.S.] Occupational Safety & Health Agency
PAN Procuring Activity Number
PBL Product Baseline
PCA Physical Configuration Audit
PCD Product Configuration Documentation
PCO Procurement Contracting Officer
PCTSS Provisioning & Cataloging Technical Support System
PDM Product Data Management [System]
PDF Page Description File
PDR Preliminary Design Review
PHST Packaging, Handling, Storage, and Transportation
PIN Part or Identification Number
POC Point of Contact
PROM Programmable Read-only Memory
RAC Rapid Action Change [order]
RFD Request For Deviation
SAE Society of Automotive Engineers
SBIR Small Business Innovative Research
SCN Specification Change Notice
SDR System Design Review
SGML Standard Generalized Markup Language

3
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

SHIPALT Ship Alteration

SHIPALTINST Ship Alteration Instruction
SIE Special Inspection Equipment
SOW Statement of Work
SSAN Social Security Account Number
SSR Software Specification Review
STANAG Standard NATO Agreement
STEP Standard for the Exchange of Product data
TA Tasking Activity
TCTO Time-compliance Technical Order
TD Technical Directive
TDP Technical Data Package
TM Technical Manual
TOPS Technical Order Page Supplement
TPS Test Program Set
U.S. United States [of America]
USAF United States Air Force
VDD [Software] Version Description Document
VECP Value Engineering Change Proposal
VHSIC Very High Speed Integrated Circuit
WINTEL Warning: Intelligence methods and sources disclosed

3.2. Definitions used in this standard. The definitions used in this standard are defined as follows:

Allocated Baseline (ABL). The approved allocated configuration documentation.

Allocated Configuration Documentation (ACD). The documentation describing a CI's functional, performance,
interoperability, and interface requirements that are allocated from those of a system or higher level configuration
item; interface requirements with interfacing configuration items; and the verifications required to confirm the
achievement of those specified requirements.

Application Activity (AA). An activity which has selected an item or a document for use on programs under its
control. However, it is not the current document change authority for the document(s).

Approval. The decision that data is complete and suitable for its intended use. (See also: Application Activity [AA],
Contractual acceptance of data, Current Document Change Authority [CDCA].)

Approved data. Approved data is data that has been approved by the appropriate authority (in the context of this
standard, the Current Document Change Authority [CDCA]), and is the official (identified) version of the data
until replaced by another approved version.

Assembly. A number of basic parts or subassemblies, or any combination thereof, joined together to perform a
specific function. Typical examples are: electric generator, audio-frequency amplifier, power supply.

Computer data base. See Data base.

Computer software. See Software.

Computer Software Configuration Item (CSCI). A configuration item that is computer software.

Computer software documentation. Technical data or information, including computer listings, regardless of
media, which document the requirements, design, or details of computer software; explain the capabilities and
limitations of the software; or provide operating instructions for using or supporting computer software.

4
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

Configuration. The performance, functional, and physical attributes of an existing or planned product, or a
combination of products.

Configuration audit. See: Functional Configuration Audit (FCA), and Physical Configuration Audit (PCA).

Configuration baseline. See: Allocated Baseline (ABL), Functional Baseline (FBL), and Product Baseline (PBL).

Configuration control. The element of configuration management concerning the systematic proposal,
justification, evaluation, coordination, and disposition of proposed changes, and the implementation of all
approved/released changes, in the configuration of a CI.

Configuration Control Board (CCB). A board composed of technical and administrative representatives who
recommend approval or disapproval of proposed engineering changes to, and proposed deviations from, a CI’s
current approved configuration documentation.

Configuration documentation. Technical documentation, the primary purpose of which is to identify and define a
product’s performance, functional, and physical attributes. Several documents might describe the attributes of a
product (for example, a specification, an engineering drawing, a technical manual, sales literature.) Of those, only
the specification and the engineering drawing are considered configuration documentation because their primary
purpose is to define the configuration of the product. Other items of product information are derived using
configuration documentation as source material. (See also: Allocated Configuration Documentation [ACD],
Functional Configuration Documentation [FCD], and Product Configuration Documentation [PCD].)

Configuration identification. The element of configuration management concerning the selection of CIs; the
determination of the types of configuration documentation required for each CI; the issuance of numbers and other
identifiers affixed to the CIs and to the technical documentation that defines the CI's configuration; the release of
CIs and their associated configuration documentation; and the establishment of configuration baselines for CIs.

Configuration Item (CI). A Configuration Item is any hardware, software, or combination of both that satisfies an
end use function and is designated for separate configuration management. Configuration items are typically
referred to by an alphanumeric identifier which also serves a the nonchanging base for the assignment of serial
numbers to uniquely identify individual units of the CI. (See also: Product-Tracking Base-Identifier.)

Configuration Management (CM). A management process for establishing and maintaining consistency of a
product’s performance, functional, and physical attributes with its requirements, design and operational
information throughout its life. As applied to digital documents, it is the application of configuration management
principles to digital documents, their representations, and data files; and the correlation of digital documents to
each other and to the products to which they apply.

Configuration Management Plan (CMP). The document defining how configuration management will be
implemented (including policies and procedures) for a particular acquisition or program.

Configuration Status Accounting (CSA). The configuration management activity concerning capture and storage
of, and access to, configuration information needed to manage products and product information effectively.

Contract. As used herein, denotes the document (for example, contract, memorandum of agreement/
understanding, purchase order) used to implement an agreement between a tasking activity and a performing
activity.

Contractual acceptance of data. The action taken by the tasking activity signifying that an item submitted or
delivered by the performing activity complies with the requirements of the contract.

5
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

Current Document Change Authority (CDCA). The authority currently responsible for the content of a drawing,
specification, or other document and which is the sole authority for approval of changes to that document. (See
also: Application Activity [AA], Approval, Document custodian activity.)

Data. Recorded information of any nature, including administrative, managerial, financial, and technical,
regardless of medium or characteristics.

Data base. A collection of related data stored in one or more computerized files in a manner that can be accessed
by users or computer programs via a data base management system.

Defect. Any nonconformance of a characteristic with specified requirements.

Deficiencies. Deficiencies consist of two types:

(1) conditions or characteristics in any item which are not in accordance with the item's current approved
configuration documentation; or

(2) inadequate (or erroneous) configuration documentation which has resulted, or may result, in units of the
item that do not meet the requirements for the item.

Design change. See Engineering change.

Developmental configuration. The performing activity's design and associated technical documentation that
defines the evolving configuration of a configuration item during development. It is under the performing
activity's configuration control and describes the design definition and implementation. The developmental
configuration consists of the performing activity's released hardware and software designs and associated technical
documentation. Programs may control design file/data bases in lieu of design drawings when implementing
paperless/drawingless design approaches.

Deviation. A specific written authorization to depart from a particular requirement(s) of an item's current
approved configuration documentation for a specific number of units or a specified period of time, and to accept
an item which is found to depart from specified requirements, but nevertheless is considered suitable for use "as
is" or after repair by an approved method. (A deviation differs from an engineering change in that an approved
engineering change requires corresponding revision of the item's current approved configuration documentation,
whereas a deviation does not allow a revision of the item's current approved configuration documentation.)

Distribution Statement. A statement used in marking a technical document to denote the extent of its availability
for distribution, release, and disclosure without need for additional approvals and authorizations from the
controlling DoD office.

Document. A self-contained body of information or data which can be packaged for delivery on a single medium.
Some examples of documents are: drawings, reports, standards, data bases, application software, engineering
designs, etc.

Document custodian activity. The custodian of a document is the activity which is charged with the physical and
electronic safekeeping and maintenance of the "original" documents.

Document representation. A set of digital files which, when viewed or printed together, collectively represent the
entire document. (For example, a set of raster files or a set of IGES files.) A document may have more than one
document representation.

Engineering change. A change to the current approved configuration documentation of a configuration item.

6
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

Engineering Change Proposal (ECP). The documentation by which a proposed engineering change is described,
justified, and submitted to the current document change authority for approval or disapproval.

Exchangeability of items. See: Interchangeable item, Replacement item, and Substitute item.

Firmware. The combination of a hardware device and computer instructions or computer data that reside as read
only software on the hardware device.

Fit. The ability of an item to physically interface or interconnect with or become an integral part of another item.

Form. The shape, size, dimensions, mass, weight, and other physical parameters which uniquely characterize an
item. For software, form denotes the language and media.

Function. The action or actions which an item is designed to perform.

Functional Baseline (FBL). The approved functional configuration documentation.

Functional characteristics. Quantitative performance parameters and design constraints, including operational and
logistic parameters and their respective tolerances. Functional characteristics include all performance parameters,
such as range, speed, lethality, reliability, maintainability, and safety.

Functional Configuration Audit (FCA). The formal examination of functional characteristics of a configuration
item, or system prior to acceptance of the design capabilities, special tooling or developmental testing, to verify
that the item has achieved the requirements specified in its functional and/or allocated configuration
documentation.

Functional Configuration Documentation (FCD). The documentation describing the system's functional,
performance, interoperability, and interface requirements and the verifications required to demonstrate the
achievement of those specified requirements.

Hardware. Items made of material, such as weapons, aircraft, ships, tools, computers, vehicles, and their
components (mechanical, electrical, electronic, hydraulic, pneumatic). Computer software and technical
documentation are excluded.

Hardware Configuration Item (HWCI). See Configuration Item (CI).

Interchangeable item. One which (1) possesses such functional and physical characteristics as to be equivalent in
performance, reliability, and maintainability, to another item of similar or identical purposes; and (2) is capable of
being exchanged for the other item (a) without selection for fit or performance, and (b) without alteration of the
items themselves or of adjoining items, except for adjustments.

Interface. The performance, functional, and physical characteristics required to exist at a common boundary.

Interface control. The process of identifying, documenting, and controlling all functional and physical attributes
relevant to the interfacing of two or more products provided by one or more organizations.

Interface Control Documentation (ICD). Interface control drawing or other documentation that depicts physical,
functional, performance, and test interfaces of related or cofunctioning products.

Interface Control Working Group (ICWG). For programs which encompass a system, configuration item, or a
computer software configuration item design cycle, an ICWG is established to control interface activity among the
tasking activity, performing activities, or other agencies, including resolution of interface problems and
documentation of interface agreements.

7
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

Interoperability. The ability of the defense services and agencies to exchange information with each other (joint
operations) or with an allied system (combined operations) to enable them to operate effectively together.

Item. A nonspecific term used to denote any product, including systems, materiels, parts, subassemblies, sets,
accessories, etc.

Life cycle cost. The total cost to the tasking activity of acquisition and ownership of that system over its life cycle.
It includes the cost of development, acquisition, support, and where applicable, disposal.

Lot number. An identifying number consisting of alpha and numeric characters which, in conjunction with a
manufacturer's identifying CAGE code and a Product-Tracking Base-Identifier, uniquely identifies a group of
units of the same item which are manufactured or assembled by one producer under uniform conditions and which
are expected to function in a uniform manner.

Materiel. A generic term covering systems, equipment, stores, supplies, and spares, including related
documentation, manuals, computer hardware, and software.

Nomenclature. The combination of a Government-assigned designation and an approved item name. In certain
cases, the designation root serves as the basis for assignment of serial and/or lot numbers.

Nonconformance. The failure of a unit or product to meet a specified requirement.

Nonrecurring costs. As applied to ECPs, these are one-time costs which will be incurred if an engineering change
is approved and which are independent of the quantity of items changed, such as cost of redesign, special tooling,
or development testing.

Nonrepairable Item. Any part or assembly which, upon failure or malfunction is either discarded or returned to the
original manufacturer.

Notice of Revision (NOR). A document used to define revisions to configuration documentation which require
revision after Engineering Change Proposal approval. (See also: Engineering Change Proposal [ECP].)

Original. The current design activity’s documents or digital document representation and associated source data
file(s) of record.

Performing activity. Denotes an activity performing any of the requirements contained in a contract. A
"Performing Activity" can be either a contractor or Government activity.

Physical characteristics. Quantitative and qualitative expressions of material features, such as composition,
dimensions, finishes, form, fit, and their respective tolerances.

Physical Configuration Audit (PCA). The formal examination of the "as-built" configuration of a configuration
item against its technical documentation to establish or verify the configuration item's product baseline.

Product Baseline (PBL). The approved product configuration documentation.

Product Configuration Documentation (PCD). The CI’s detail design documentation including those verifications
necessary for accepting product deliveries (first article and acceptance inspections.) Based on program
production/procurement strategies, the design information contained in the PCD can be as simple as identifying a
specific part number or as complex as full design disclosure.

Product-tracking base-identifier. A nonchanging identifier used as a base for the assignment of serial numbers to
uniquely identify individual units of an item or lot numbers to uniquely identify groups of units of an item. The
product-tracking identifier is used rather than the Part or Identifying Number (PIN) because the PIN is altered to

8
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

reflect a new configuration when the item it identifies is modified. The same product-tracking base-identifier may
be used for several similar items (usually defined by a common document) and requires that each such item is
assigned serial or lot numbers distinct from each other such item.

Product Tracking Identifier. A generic term which refers to the sequentially assigned alphanumeric identifier
applied to a product to differentiate units of the product or groups of the product. This may be a Government serial
(or hull) number, manufacturer’s serial number, lot number or date code.

Recurring costs. Costs which are incurred for each item changed or for each service or document ordered.

Release. The designation by the originating activity that data, a document representation, or software version is
approved by the appropriate authority and is subject to configuration change management procedures.

Released Data. Released data is data that has been released by the originating activity after review and internal
approvals. Released data may be selectively provided to a tasking activity for purposes such as design review.

Repair. A procedure which reduces, but does not completely eliminate, a nonconformance. Repair is
distinguished from rework in that the characteristic after repair still does not completely conform to the applicable
drawings, specifications, or contract requirements.

Repairable Item. Any part or assembly which, upon failure or malfunction, is intended to be repaired by
Government personnel (including contract personnel.)

Replacement item. One which is interchangeable with another item, but which differs physically from the original
item in that the installation of the replacement item requires operations such as drilling, reaming, cutting, filing,
shimming, etc., in addition to the normal application and methods of attachment.

Retrofit. The incorporation of new design parts or software code, resulting from an approved engineering change
to a product's current approved product configuration documentation, into products already delivered to and
accepted by customers.

Rework. A procedure applied to a nonconformance to the drawings, specifications, or contract requirements that
will completely eliminate it and result in a characteristic that conforms completely.

Serial number. An identifying number consisting of alpha and numeric characters which is assigned sequentially
in the order of manufacture or final test and which, in conjunction with a manufacturer's identifying CAGE code,
uniquely identifies a single item within a group of similar items identified by a Product-tracking base-identifier.

Software. Computer programs and computer data bases.

Specification. A document which explicitly states essential technical attributes/requirements for a product and
procedures to determine that the product’s performance meets its requirements/attributes.

Specification Change Notice (SCN). See Engineering Change Proposal (ECP).

Submitted data. Released data that has been made available to customers, as required by contractual agreement.

Substitute item. An item that possesses such functional and physical characteristics as to be capable of being
exchanged for another item only under specified conditions or in particular applications and without alteration of
the items themselves or of adjoining items.

Support equipment. Equipment and computer software required to maintain, test, or operate a product or facility
in its intended environment.

9
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

Survivability. The capability of a system to avoid or withstand a hostile environment without suffering an abortive
impairment of its ability to accomplish its designated mission.

System. A complete system includes all equipment, related facilities, material, software, services, and personnel
required for its operation and support to the degree that it can be considered a self-sufficient unit in its intended
operational environment.

Tasking activity. A tasking activity (for example, a Government Contracting Activity which awards a contract to a
contractor, a Government Program Management Office which tasks another Government activity, or a contractor
which tasks a subcontractor) is the activity imposing the requirements contained in a contract on a performing
activity.

Technical data. Technical data is recorded information (regardless of the form or method of recording) of a
scientific or technical nature (including computer software documentation.)

Technical data package. A technical description of an item adequate for supporting an acquisition strategy,
production, engineering, and logistics support. The description defines the required design configuration and
procedures required to ensure adequacy of item performance. It consists of all applicable technical data such as
drawings and associated lists, specifications, standards, performance requirements, quality assurance provisions,
and packaging details.

Technical documentation. See Technical data.

Technical reviews. A series of system engineering activities by which the technical progress on a project is
assessed relative to its technical or contractual requirements. The reviews are conducted at logical transition
points in the development effort to identify and correct problems resulting from the work completed thus far
before the problems can disrupt or delay the technical progress. The reviews provide a method for the performing
activity and tasking activity to determine that the development of a configuration item and its documentation have
a high probability of meeting contract requirements.

Training equipment. All types of maintenance and operator training hardware, devices, audio-visual training aids,
and related software which:

(1) are used to train maintenance and operator personnel by depicting, simulating, or portraying the
operational or maintenance characteristics of an item or facility;

(2) are kept consistent in design, construction, and configuration with such items in order to provide required
training capability.

Version. An identifier used to distinguish one body or set of computer-based data from another. Version
identifiers are usually associated with data used by, or maintained in, computers such as files, data bases, and
software. Modifications to a version of either software, or a computer data base or a file (resulting in a new
version) may require configuration management actions by either the performing activity, the tasking activity, or
both.

Waiver. See Deviation.

Working data. Data that has not been reviewed or released; any data that is currently controlled solely by the
originator including a new version of data that was released, submitted, or approved.

10
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

4. GENERAL REQUIREMENTS

(This section describes the business rules that underlie the principles of CM contained in EIA/IS-649, National
Consensus Standard for Configuration Management. These principles constitute the basis for the conceptual schema
defined in this data interface standard.)

4.1. General. DoD activities are responsible for acquiring (delivery of or access to) the configuration information
necessary to support program development, production, sustainment, modification and disposal. The data which is necessary
for configuration management of these Government assets varies during the life-cycle of the product and is dependent on
the acquisition and logistic support strategies for the system/CI. To accomplish this requirement, the Government will
maintain a system, or set of interconnected systems, which maintain the necessary information in a form which complies with
Appendices B and C. Government activities must:

a. ensure the unique identification of parts, assemblies, materials, software, and supporting documentation;

b. ensure documentation is generated and correlated with the associated parts, assemblies, materials, or software;

c. record the approved and actual structures of fielded units (assets);

d. provide a repository for explanatory and requirements documents;

e. document CCB membership and CCB disposition of proposed changes;

f. maintain a history of the changes to system/CI configuration information and asset configuration;

g. maintain an accurate record of the Government’s decision making role over documents which are delivered to the
Government; and

h. monitor audit actions and change implementation actions.

The Government is responsible for maintaining the Government CM AIS which supports the information needs listed
above. The CM AIS is the data base, or set of interconnected data bases, which contains both the electronic documents
to be configuration controlled and the CSA data about those documents and about fielded Government products/assets.
Usually, several different activities are responsible for different aspects of configuration identification (including
documentation and interface management), control, audits, and status accounting. Therefore, various Government
organizations must be tasked with providing the required information or documents and some of the information or
documents may be procured from performing activities by ordering the appropriate information packets. (See Section 6
for ordering information.)

4.2. Configuration identification. To accomplish the requirement for accurate configuration identification records,
Government responsibilities include:

4.2.1. Configuration identification of configuration items. The Government will select the systems/CIs for management.
Each system will be assigned a name (for example, HARM Missile, Eagle, Javelin, Crusader Artillery System, Trident
Submarine, etc.) and each CI will be assigned a name and may be assigned an alphanumeric identifier (for example:
AGM-88B High-Speed Anti-Radiation Missile; F-15 Fighter Aircraft, WAU-47 Warhead, FMU-111A Fuze, CG47
Ticonderoga Class Guided Missile Cruiser, AN/TAS-4A Night Vision Sight Assembly, etc.). Together, these will
uniquely identify the major end-use item. CSCIs will be identified as indicated in 4.2.4. If a system or CI is composed
of lower level CIs, this hierarchy will be maintained in the CSA system.

11
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

4.2.2. Configuration identification of parts and assemblies. (Some commercial parts do not have a unique identifier, for
example, machine screws are identified by diameter, length, thread, and head instead of by a part number. Such items
will be identified using the requirements for materials in 4.2.3 instead of the requirements in this paragraph.)

4.2.2.1 Part and assembly design identification. The design of each part or assembly will be identified by a design
source and a unique identifier assigned by that design source. This identification will always be associated with one or
more configuration documents which define the design, including a component breakdown list (for example, parts list.)
The design source for the part/assembly and the document source for the document must be the same.

4.2.2.2 Part and assembly unit/lot identification. Each physical part or assembly will be identified with the part
identification (design source and identifier), and a manufacturer. If it is critical to safety or CI performance or operation,
each individual part or assembly will also be identified by a unique product tracking identifier (usually assigned by the
manufacturer.)1 In some cases, more than one type of product tracking identifier may be assigned (for example, a serial
number and a lot number); in this case, the correlation between product tracking identifiers will be recorded.

4.2.3. Configuration identification of materials. (If a part number has been assigned to the material by the design source,
the material will be identified using the requirements for parts in 4.2.2 instead of the requirements in this paragraph.)

4.2.3.1. Material design identification. Each material will be identified by its design specification or standard (design
source, document identifier and document type) and an optional list of up to six parameters, each with an associated
value. The design documentation will also include a component breakdown list (for example, parts list) if required.

4.2.3.2. Material unit/lot identification. Each batch of material, or the package or shipping document for each batch of
material, will be identified by the material design identification and a manufacturer. If it is critical to item safety,
performance, or operation, or necessary to comply with regulatory requirements, each batch of material will also be
identified by a unique product tracking identifier assigned by the manufacturer.1 In some cases, more than one type of
product tracking identifier may be assigned (for example, a serial number and a lot number); in this case, the correlation
between product tracking identifiers will be recorded.

4.2.4. Configuration identification of software. Each software item which is designed to be directly installed in hardware
(for example: computer, PROM, EEPROM, etc.) will be identified by its design source and a unique identifier or title
assigned by that design source. It is further identified with a document type code which is used for tracking in the CM
AIS data base. Each software item will consist of at least one document representation (for example, source code,
executable code, etc.). Each iteration of a software item will be identified by a version identifier (also known as a
revision identifier or release identifier) which is unique to the software item.

4.2.5. Configuration identification of documents. Each document will be identified by a document source2, a unique
identifier assigned by the document source, and a document type. Each document will consist of at least one document
representation. Each iteration of a document will be identified by a revision identifier which is unique to the document.

4.2.6. Configuration identification of document representations. Each document representation will be identified by the
document identification (that is, the document source, unique identifier, and document type) of the document which it
represents and a document representation identifier which is unique for the document. A document representation may
consist of any number of electronic files. Each iteration of a document representation will be identified by a revision
identifier which is unique to the document representation.

1
This requirement does not preclude the assignment of a product tracking identifier to parts, assemblies, and materials which are not critical to
safety, CI performance or operation when the assignment is for manufacturing, inspection, or other purposes.
2
Generally, the document source should be the organization which originates the document and determines the initial content of the document;
however, if the Government is contracting for the creation of documentation with the intent of transferring CDCA and responsibility to the
Government at some future time, then, the document source shown on the document may be different from the organization actually originating the
work. In either case, the CM AIS should record both the originating organization and the CDCA. For drawings, the organization that actually
originates the drawing is sometimes called the preparing activity, and the organization whose number appears in the title block of the drawing is
called the Original Design Activity.

12
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

4.2.7. Configuration identification of files. Each electronic file which is part of a document will be uniquely identified by
the combination of the name of the person and organization (for example, company, service, office, etc.) which created
it, the name assigned to the file by the creator of the file, and the creation date of the file.

4.2.8. Secondary configuration identifiers. Some items or documents may have one or more alternate identifiers. These
are in addition to, not in lieu of, the identifiers in 4.2.2 through 4.2.7 and must be cross-referenced to the primary
configuration identifier.

4.2.8.1. National Stock Numbers (NSN). For the purpose of supplying and stocking parts, assemblies, materials, and
software, an NSN may be assigned. A single NSN may be used for all interchangeable parts/assemblies/
materials/software. Different NSNs may be used for a single item for variations in packaging, preservation, unit of
issue, etc. NSNs should be marked on parts/assemblies and their packaging when appropriate.

4.2.8.2. Contract data item identifiers. If a document (or group of documents) is submitted as a contract required data
item, it may also be additionally identified with a data item identifier consisting of the contract number, contract data
requirements list (CDRL) sequence number, and submittal number. Subsequent submittals of the same item of data (for
example when the original data item submittal is disapproved) may be identified by a revision identifier which uniquely
identifies the submittal iteration. A data item identifier is a method of identifying the specific document representation(s)
which is submitted as the data item. Contract Data Item Identifiers are primarily for tracking purposes, but they may be
marked on the document(s) if desired.

4.2.8.3. Block identifiers. For hardware CIs, a block identifier may be assigned to designate a quantity (a block) of
consecutive production units of the CI which will have essentially the same configuration on delivery or upon the
completion of modification. (Using this concept, the production run is divided into “blocks” of units. The production
line incorporation for an ECP is delayed to coincide with the first unit of the next block, or retrofit is required for at least
all already-delivered units of the current block.)

4.3. Configuration documentation. The configuration documentation which must be accessible via the CM AIS will
vary depending on the acquisition and logistics support scenario. All configuration documentation for which a DoD
organization is the CDCA must be accessible via the Government CM AIS. All configuration documentation which is
necessary for the DoD to perform maintenance/modification/disposal actions to fielded assets must be accessible via the
Government CM AIS but does not have to be controlled by a Government agency. The Government tasking activity will
obtain the configuration documentation3, copies of the configuration documentation, or access to copies of the
configuration documentation as described below.

4.3.1. Performance-based procurement of a nonrepairable item. A Government activity should be the CDCA for the
FCD and ACD for the CI being procured.4 The performing activity will be the CDCA for the PCD. Copies of, or access
to, the PCD by the Tasking Activity is not required.

4.3.2. Performance-based procurement of a repairable item. A Government activity should be the CDCA for the FCD
and ACD for the CI being procured.4 The performing activity usually will be the CDCA for the PCD. The tasking
activity will be responsible for obtaining the top-down breakdown structure of items which are critical to safety,
performance, or operation by obtaining copies of, or perpetual access to, the PCD documents describing the design,
down to and including all replaceable components in the lowest level repairable assembly. The tasking activity will be

3
If the Government procures the configuration document, instead of a copy of the configuration document, control of the master file(s) is transferred
to the Government, the Government becomes the CDCA for the document(s), is solely responsible for all future changes to the content of the
document(s), and can make unilateral changes to it. If the Government procures only a copy of the document, or access to the document, the
Government does not have the authority to change the document unilaterally; the CDCA remains with the originating activity, and any changes
proposed by the Government must be approved and incorporated by the CDCA. If not otherwise stated in the contract, the assumption is that the
Government is procuring a copy of the document, not the master of and not control of the document.
4
The organization which originates the document is always the CDCA unless the authority and responsibility is transferred. Normally, that transfer
should take place prior to the Government using that document as a basis of contracting. The CDCA for the remainder of the document(s) should
remain with the originating activity.

13
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

responsible for obtaining a copy of the complete product configuration of each delivered tracked item (as-built
configuration report) down to and including the replaceable components of the lowest level repairable item.

4.3.3. Detailed-design procurement of a repairable item. A Government activity should be the CDCA for the FCD and
ACD for the CI being procured.4 The tasking activity will be responsible for obtaining a copy of the complete product
configuration of each delivered item (as-built configuration report.) Depending on tasking activity plans for
reprocurement of the CI and for enhancement to the design after the end of production, the tasking activity will be
responsible for either

a. obtaining a copy of, or perpetual access to, the TDP including the PCD describing the complete design, down to
and including all replaceable components in the lowest level repairable assembly (in which case, the performing
activity will be the CDCA), and for reviewing proposed changes to the design documentation for logistics impact,
or

b. obtaining the originals of the PCD (or a portion of the PCD) describing the detailed design, down to and including
all replaceable components in the lowest repairable assembly (in which case, the tasking activity will become the
CDCA for these documents) as part of the TDP, and for reviewing and dispositioning proposed changes to the
design documentation.

4.4. Configuration control.

4.4.1. Change control of documents. There are five categories of document control which are independent of contractual
relationships. In order to provide proper change control of documents, the Government CM AIS must maintain clear
records of the various controlling roles, as discussed below, for each document (or copy of a document) accessible by
the Government CM AIS.

4.4.1.1. Originating activity. The originating activity is the organization which determines the content of, and creates
the initial issue of, the document. The originating activity determines the identification to be used for the document.
Usually, the originating activity assigns itself as the source and assigns a number (or title) of its choosing; however,
when it is preparing the document for another organization, it may be required to assign that tasking organization as the
source and assign a number (or title) provided by the tasking organization. Regardless of the identification of the
document, the originating activity never changes for the life of the document. There is always one originating activity for
each document.

4.4.1.2. Current Document Change Authority (CDCA). When a document is first created, the originating activity is the
CDCA for the document. The CDCA can approve (baseline) the initial document and can unilaterally approve changes
to the document. Therefore, the CDCA has the final authority and responsibility for controlling the content of the
document and for ensuring that changes are incorporated into the document. Coordination with application activities is
not necessary unless a contractual arrangement so dictates (see 4.4.1.4.) The CDCA may be transferred to another
organization. There is always only one CDCA for each document.

4.4.1.3. Custodial activity. When a document is first created, the originating activity is the custodial activity for the
document. The custodial activity is usually the same as the CDCA, but custodial responsibility may be transferred to
another organization. This custodian is responsible for storing the “master” or “original” copy/document
representation(s)/file(s) of the document and the subsequent approved revisions of the document. There is always only
one custodial activity for each document.

4.4.1.4. Application Activity (AA). An application activity is any organization which uses a document for which it is
not the CDCA. The AA may or may not have a contractual relationship with the CDCA and the authority of the AA

14
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

depends on the contractual relationship with the CDCA of the document.5 In general, AAs can provide approval for use
(adoption) of a document or of a change to a document. AAs cannot direct incorporation of a change into the document,
or approve or direct implementation of a proposed change which has been disapproved by that document's CDCA.

4.4.1.5. Government Lead Application Activity (GLAA). When more than one Government organization is an AA
with a contractual relationship with the CDCA of a document, one Government organization is sometimes designated as
the GLAA. If one Government activity has been designated as the lead for Government acquisition of the item (for
example, DLA), and other Government activities “buy” through the lead activity, the designated lead is the GLAA. The
GLAA should consolidate recommendations from all Government AA’s and act as the sole point of contact within the
Government for coordination with the CDCA concerning proposed engineering changes and approval for use (adoption)
of a document or of a change to a document.

4.4.1.6. Contract data item approval. When there is a contractual requirement for a decision about the acceptability of
information submitted to meet contract requirements (as opposed to the always-required technical decision by the
CDCA or AA described in 4.4.2 or 4.4.3) this approval (contractual acceptance) is a separate action by the tasking
activity; however, it is usually dependent, at least in part, on the technical decision by the tasking activity either in its role
as CDCA or as AA. The name of the data submittal approval authority, approval/disapproval disposition decision, and
date will be recorded in the Government CM AIS or be accessible to the Government CM AIS.

4.4.2. Configuration control of Government products/assets and their designs.

4.4.2.1. Configuration control of designs for products/assets. All documents for which the Government is the CDCA
(ranging from performance specifications to detailed design drawings to data items) will be entered into the Government
CM AIS. If the Government is the CDCA for detailed design documents the completed design structure will be entered
into the Government CM AIS. For repairable items which will be repaired by the Government, the complete design
structure and any necessary associated documentation will be entered into the Government CM AIS. Changes to the
design, design structure, or configuration documentation will be proposed by means of an ECP. Prior to delivery of the
unit affected, temporary departures from the design requirements (permanently incorporated in the unit) will be
proposed by means of an RFD. (See also: 4.4.2.1.2)

4.4.2.1.1. Design changes requiring new identification. The CDCA will assign new part/material/software identifiers
when a part, material, or software is changed in such a manner that any of the following conditions occur6:

a. Condition 1: Performance or durability is affected to such an extent that superseded items must be discarded or
modified for reasons of safety or malfunction.

b. Condition 2: Parts, subassemblies, or complete articles (including software) are changed to such an extent that
the superseded and superseding items are not interchangeable.

c. Condition 3: When superseded parts, materials, or software are limited to use in specific articles or models of
articles and the superseding parts are not so limited in use.

5
If there is a contractual relationship between the CDCA and AA, the CDCA should coordinate proposed changes to the document with the AA to
allow the AA to determine if the changes will impact the AA’s use of the product (or ability/cost to produce the product.) The CDCA can
unilaterally make changes to the document provided the changes do not affect the product deliveries currently under contract. The CDCA can also
make unilateral changes to the document which do affect the product, but the CDCA must then negotiate any necessary contract adjustments.
However, if the tasking and performing activities are both AAs, neither has any control over changes to the document (for example, procuring steel
to the ANSI standard for steel.) The CDCA (in this example, ANSI) has no responsibility for coordinating changes with either AA.
6
When a part, assembly, material, or software is changed in such a manner that the conditions listed do not occur, the part/material identifier will
not be changed. Under no condition will the part/material identifier be changed only because a new application is found for an existing item.
When an item has been furnished to the Government, the applicable part/material/software identifier will not be changed unless the conditions
listed apply. However, when the CDCA desires to create a tabulated listing or a standard because of multiple application of an item, the
aforementioned need not apply. The superseded drawing will identify the document which superseded it. The superseding document will identify
the part/material identifiers replaced and provide a complete cross-reference of superseded part/material identifiers to replacement part/material
identifiers.

15
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

d. Condition 4: When an item has been altered, selected, or is a source control item.

e. Condition 5: When a repair part within an item is changed so that it is no longer interchangeable with its previous
version, it will be assigned a new part/material identifier. A new part/material identifier will also be assigned to
the next higher assembly for the changed repair part and to all subsequent higher assemblies up to and including
the level at which interchangeability is re-established.

f. Condition 6: When an item is changed in such a way that it necessitates a corresponding change to software for
operation, self test, acceptance test, or maintenance test, the part/material identifier of the item, its next assembly
and all progressively higher assemblies will be changed up to and including the assembly where the software is
affected.

4.4.2.1.2. Configuration Control Boards (CCBs). Each Government organization or project which is responsible for
the design (CDCA) or acquisition (AA or GLAA) of a system/CI will establish a CCB for the system/CI and maintain a
record of the current members by name and position. The CCB will review proposed changes for their impact on cost,
logistics support, and implementation planning. For each ECP or RFD reviewed by the CCB, the CCB date and results
will be entered in the Government CM AIS. The results will include the disposition of the ECP/RFD and may include a
description of each action item identified as a result of the CCB decision. For each major and subsidiary action item in
the CCB directive, a record of the status of the action item will be maintained, including the organization responsible for
accomplishment of the action item, its estimated completion date, and current status.

4.4.2.1.2.1. Approval of ECPs. When an engineering change proposal affects documents controlled by more than one
CDCA, or when more than one performing activity is involved in accomplishing the change, related ECPs must be
prepared. A separate ECP must be prepared for each package of documents controlled by a single CDCA which are to
be changed to accomplish this single engineering change. Only the CCB convened by the CDCA for the documents
being changed by the ECP can make the final disposition of the ECP. AA CCBs should review proposed ECPs and
make recommendations to the CDCA (or GLAA.) (See also: Table I.)

TABLE I. ECP Disposition Authority

Activity Decision Forwarded to
CDCA Final
GLAA Overall Government AA position CDCA
AA (Government) User Position GLAA if any, CDCA if there is no
GLAA
AA (Nongovernment) User Position CDCA

4.4.2.1.2.2. Approval of RFDs. Disposition of a proposed RFD will be by a CCB convened by, or MRB authorized by,
the tasking activity which is procuring the affected product.

4.4.2.2. Configuration control of parts/materials. A product-tracking base-identifier will be assigned to each part or
material to be tracked. Within a product-tracking base-identifier (for example a unique CI designator), product tracking
identifiers (for example, serial numbers) will not be duplicated even if part numbers change.

4.4.2.3. Product configuration record. For each selected part, assembly, or material (including installed software),
which is critical to the product safety, performance, or operation, a record will be maintained of:

a. the part/assembly (design source, identifier, manufacturer, and product tracking identifier) or material (material
design source, specification or standard identifier, list of material parameters, manufacturer, and product tracking
identifier),

16
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

b. the next higher level of assembly (design source, part identifier [or material specification/standard identifier and
list of part parameters], manufacturer, and product tracking identifier) in which it is installed, and

c. the component software (design source and identifier), part/assembly (design source and identifier) or material
(material design source, specification or standard identifier, and list of material parameters) for each replaceable
part or material to which a product tracking identifier has not been assigned.

4.4.2.4. Configuration control of assets. Each maintenance, modification, update, or retrofit action performed by, or
for, the Government (including contract maintenance/depot personnel) which involves the removal/replacement or re-
identification of a part/assembly/material/software which is critical to safety, performance, or operation will be recorded
in the Government CM AIS. (This is normally accomplished through maintenance data collection systems and fed
electronically to the Government CM AIS.) This record will include:

a. the old part/assembly/material/software identification, manufacturer, and product tracking identifier,

b. the new part/assembly/material/software identification, manufacturer, and product tracking identifier,

c. the old next higher assembly identification, manufacturer, and product tracking identifier,

d. the new next higher assembly identification, manufacturer, and product tracking identifier,

e. the identification of the organization performing the task and when the task was performed, and

f. for modifications, updates, and retrofits, the tasking document (for example, Modification Work Order, Time
Compliance Technical Order, Technical Directive, Ordnance Alteration Instruction, Ship Alteration Instruction,
Machinery Alteration Instruction, etc.).

4.4.2.4.1. ECP requests for changes to assets. After delivery of a product, an ECP will be used to request a change to
the asset(s) if

a. the asset is still being produced or

b. the asset is no longer being produced but the Government is the CDCA for the design document of the
part/material/software being changed. (See also: 4.4.2.1.)

4.4.2.4.2. Modification requests for changes to assets. After delivery of a product, a modification request (for
example, a Modification Improvement Program Request, Proposed Military Improvement, Proposed Technical
Improvement, or approved equivalent) will be used to request a change to the asset(s) if

a. the asset is no longer being produced and the Government is not the CDCA for the design document of the
part/material/software being changed, or

b. the asset is still being produced, but the requested change is temporary in nature (such as modification of an asset
to conduct testing of new equipment.)

4.4.2.4.2.1. Approval of modification requests. Modification requests to deployed hardware and software (assets) will
be reviewed and dispositioned by the activity responsible for the equipment/software. If the modification request is
approved, the approving activity will:

a. Prepare the appropriate tasking document(s) (for example, Modification Work Order, Time Compliance
Technical Order, Technical Directive, Ordnance Alteration Instruction, Machinery Alteration Instruction, Field
Change Instruction, Rapid Action Minor Engineering Change, etc.) and include it in the Government CM AIS.

17
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

b. Create, or direct the creation of, any new engineering drawings (including altered item drawings) which are
necessary to the accomplishment of the modification,

c. Mark, or direct the marking of, any modified parts/materials/software with the altered item part number.7

d. Ensure that the modification is properly recorded in the Government CM AIS upon completion of the modification
(see also: 4.4.2.3),

e. Prepare and issue changes to any technical manuals/orders (including maintenance and operations) which must be
changed to reflect the new configuration resulting from the modification.

4.5. Configuration audit. To accomplish the requirement for accurate configuration audit records, Government
responsibilities include:

4.5.1. Configuration audit results. For each CI, a record of the date and results of each FCA and PCA performed by the
Government will be maintained. The results will include a description of each problem and action item from the audit
and the basis of the problem/action item (for example, contract, specification, etc.).

4.5.2. Configuration audit action item status. For each problem identified by an FCA or PCA, the resulting action
item(s) and a record of the status of the action item will be maintained including the organization responsible for
accomplishment of the action item, its estimated completion date, and current status.

4.6. Miscellaneous.

4.6.1. On-line review and comment on documents. The Government CM AIS allows for any document entered into CM
AIS to be reviewed on-line and be commented on by the reviewer(s) prior to approval by the CDCA of the document.
As a minimum, CCB members are reviewers of all configuration documents submitted to the CCB. If the on-line
review/comment capability is to be used for other documents, the name and organization of the reviewers must be
maintained in CM AIS by the CDCA.

4.6.2. On-line review and comment on data item submittals. The Government CM AIS allows for any data item
submittal entered into CM AIS to be reviewed on-line and be commented on by the reviewer(s) prior to contractual
acceptance of the data item. If the on-line review/comment capability is to be used for data item submittals, the name
and organization of the reviewers must be maintained in CM AIS by the Government data manager.

4.6.3. Document protection. Each document, document representation, and electronic file will be coded and marked
with the appropriate protective markings. The following are recognized in the Government CM AIS:

a. Government security classification level, authority, and downgrading,

b. Government security access restrictions (for example: WINTEL, CRYPTO, CNWDI, etc.),

c. Export Controlled item warning,

d. Document Distribution Limitations, controlling office, and date,

e. Government Rights in Technical Data and Computer Software and expiration date,

7
If parts (or materials) change sufficiently to become non-interchangeable (see 4.4.2.1.1), an altered item drawing must be created by the approving
activity and the modified part/material must be marked with the altered item part identifier. An altered item drawing will also be created, and
altered item part/material identifiers marked on the next higher assembly and all subsequent higher assemblies up to and including the level at
which interchangeability is re-established. If the change is to software, or necessitates a corresponding change to software for operational, self test,
acceptance test, or maintenance test, the approving activity will assign a new identifier to the software, create an altered item drawing for, and
mark, the part/material item, its next assembly and all progressively higher assemblies up to and including the assembly where the software is
affected.

18
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

f. Copyright information and limitations,

g. Company proprietary rights and competition sensitive information.

4.6.4. Access. Access to documents/document representations/files will be limited to those personnel with the
appropriate authorization for the particular file.

5. DETAILED REQUIREMENTS

5.1. Data information packets. To streamline the effort required to obtain this information and eliminate redundant or
overlapping responsibilities, the required information has been broken into data information input packets, each dealing
with a different major aspect of configuration management. These packets are then further broken into subpackets.
Each subpacket includes only that information which would be expected to be provided by a single activity. The packets
are:

a. Data information packet 1: Drawings, specifications, standards, software and software support documents. This
packet includes information about, and may include actual documents (or access to documents) that define the
configuration requirements for hardware or software, or establish standards for materials, products, or processes.
This includes all engineering drawings (including primary item, test equipment, tooling, etc.), program-unique
specifications, software, and software support documents, and documents that are referenced as part of the
configuration design but which do not define parts or materials. This includes such documents as industry
organization specifications/standards, military specification/standards/ handbooks, other U.S. Government agency
(for example: DOE, DOT, OSHA, etc.) standards, etc., and other non-U.S. standards (for example: NATO
STANAG, ISO, etc.).

b. Data information packet 2: General document. This packet includes information about, and may include actual
documents (or access to documents), that are ancillary to the configuration definition but necessary to
management of the configuration of the deployed product, that are used for logistics support of the product, or that
are submitted to the Government for some other purpose. This includes technical manuals/orders and their
changes/supplements, decision documents, and other miscellaneous contract data items associated with the
product.

c. Data information packet 3: Product/asset configuration. This packet includes the actual current configuration (by
part and serial/lot number) of fielded hardware/software. It includes a correlation of serial, lot, and block numbers
when multiple tracking identifiers are used for a single item.

d. Data information packet 4: Configuration change control. This packet includes information concerning requests
for change/modification of engineering designs and/or fielded equipment/software.

e. Data information packet 5: Configuration management action item status. This packet includes information
concerning CCB-directed actions and configuration audit actions and their status.

f. Data information packet 6: Project management. This packet includes system and configuration item
designations and CCB organization, contract and contract data item requirements, document review and approval
and other miscellaneous configuration management information.

g. Data information packet 7: Engineering parts list. This packet includes the contents of parts lists (including
integral and separate parts lists) and proposed changes to parts lists.

h. Data information packet 8: Basic document protection. This packet includes document/file security classification,
Government rights in technical data, document distribution restrictions, company proprietary rights, etc. This
packet is used only in conjunction with the other packets when documents, files, or information on documents or

19
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

files are provided. It is treated separately solely to prevent redundancy within this standard. It cannot be ordered
separately.

i. Data information packet 9: Basic file. This packet includes file identification, file administrative information, and
may contain the actual files. This packet is used only in conjunction with the other packets when files, or
information on files, are required by the packet. It is treated separately solely to prevent redundancy within this
standard. It cannot be ordered separately.

j. Data information packet 10: Basic document representation. This packet includes document representation
identification and administrative information. This packet is used only in conjunction with the other packets when
documents, or information on documents, require this information. It is treated separately solely to prevent
redundancy within this standard. It cannot be ordered separately.

5.2. Content of data information packets. The data information packets define the elements and documents/files to be
provided and correlates the information elements with the conceptual CM AIS data base described in Appendices B and
C. For each packet, the subpacket identifier shall be followed by the various elements listed. These elements shall be
provided in the order shown, except that fields which are not applicable (denoted by blank) and optional fields (denoted
by O) for which data is not being submitted shall be skipped. Each element shall be preceded by the table and data
element code, separated by a decimal, as shown in the column labeled “Date Element Tag”. The full field size for the
data element, as shown in Appendix C, shall be used and shall immediately follow the data element code. The end of
each data packet will be indicated by the inclusion of “/end”.

5.3. Validation of data. CM information is highly interrelated. Any information to be added to the DoD CM AIS data
base must be validated against information already existing in the data base. For example, information on an ECP
cannot be added to the data base unless the identification of the document(s) affected by the ECP is already in the data
base. Therefore, some of the information included in each of the information packets is there solely for validation of the
input. Data information packets will also be validated based on their conformance to 5.2.

6. NOTES

(This section contains information of a general or explanatory nature which may be helpful, but is not mandatory.)

6.1. Intended use. This Military Interface Standard establishes the business rules view (conceptual schema) for DoD
standard automated information systems used for configuration management of Defense materiel items and the
management of data related to those items. It also defines the configuration management data requirements that may be
selected by the Government to be provided by performing activities. This data is typically ordered by the Government in
Statements of Work and Contract Data Requirements Lists invoking the Data Item Descriptions listed in 6.2.

6.2. Associated Data Item Descriptions (DIDs). When it is necessary to obtain data, the applicable one time use DIDs
must be listed on the Contract Data Requirements List (DD Form 1423), except where the DoD Federal Acquisition
Regulation Supplement exempts the requirement for a DD Form 1423.

Selection and Tailoring

DID Number DID Title Guidance
DI-CMAN-81551 Drawings, Specifications, Standards, Software and A.4.2
Software Support Documents Data Information Packet
DI-CMAN-81552 General Document Data Information Packet A.4.4
DI-CMAN-81553 Product/Asset Configuration Data Information Packet A.4.3, A.4.5
DI-CMAN-81554 Configuration Change Control Data Information Packet A.4.6
DI-CMAN-81555 Configuration Management Action Item Status Data A.4.7
Information Packet
DI-CMAN-81556 Project Management Data Information Packet A.4.8

20
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

The above DIDs were current as of the date of this standard. The following DIDs must also be listed on the DD Form
1423 when it is necessary to obtain the data.

6.3. Tailoring guidance for contractual application. This Standard defines the Government interface for digitized
configuration management data. Data Information Packets (DIPs) in this Standard define the required data formats.
Selection and use of the appropriate DIPs is determined by the requirements specified in the tasking activity’s statement
of work and contractually invoked by specifying the appropriate DIDs in the CDRL. On-line delivery or on-line access
to the data is preferred. Tailoring guidance for the DIPs is provided in Appendix A.

6.4. Subject term (key word) listing.

Application activity
Approved data
Configuration audit
Configuration baseline
Configuration control
Configuration control board
Configuration documentation
Configuration identification
Configuration item
Configuration status accounting
Current document change authority
Data Information Packet
Document custodian activity
Document representation
Engineering change proposal
Interface control
Lot number
Notice of revision
Product-tracking base-identifier
Released data
Request for Deviation
Serial number
Submitted data
Technical data package
Working data

6.5. Useful references.

a. EIA Standard IS-649, National Consensus Standard for Configuration Management. This standard explains the
major configuration management functions rather than mandates them. The explanation includes purpose,
benefits, and best practices. Within each topic, the basic principles of configuration management are addressed.
The principles are selectively applicable to a broad range of customers, products and industries. This standard
has been DoD adopted, and copies are available to Government personnel through the DoD Single Supply Point,
Bldg. 4/Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5094; or by FAX to 215-697-1462. The
standard is available to industry from Global Engineering Documents, 15 Inverness Way East, Englewood, CO
80112-5704, or call USA and Canada 1-800-854-7179, International (303) 397-7956.

b. Draft MIL-HDBK-61, DoD Configuration Management. This handbook provides guidance to military acquisition
Program Managers and all Integrated Product Team (IPT) members on how to ensure the selective application of
product and data configuration management to defense materiel items. The document can be downloaded from
the Internet at http://www.magicnet.net/~noble/eia/.

21
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

c. The Software Engineering Institute’s A Systems Engineering Capability Maturity Model. This model describes
the role configuration management plays in the systems engineering process, and provides a reference for
comparing actual practices against essential elements. The document is available from the National Technical
Information Service (NTIS), U.S. Department of Commerce, Springfield, VA 22161, Phone (703) 487-4600; or
from the Defense Technical Information Center (DTIC), Attn: DTIC-OCP, 8725 John J. Kingman Road, Suite
0944, Ft. Belvoir, VA 22060-6218.

d. ISO 10303-203, Configuration Controlled 3D Design for Mechanical Parts and Assemblies. This document is a
published international standard addressing a part of the configuration management business area. Harmonization
of this MIL-STD with ISO 10303-203 and other applicable 10303 efforts is an ongoing activity as we move to a
single consensus international standard for the configuration management business area. ISO 10303 documents,
published and in process, can be accessed on the Internet at http://www.nist.gov/sc4/.

22
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 1

Drawings, Specifications, Standards, Software and Software Support Documents

DIP1.1. Purpose. Includes information about and may include actual documents (or access to documents) that define
the configuration design of hardware or software, or establish standards for materials, products, or processes. This
includes all engineering drawings (including primary item, test equipment, etc.), program-unique specifications,
software, and software support documents, and standardization documents that are referenced as part of the
configuration design. This includes such documents as industry organization specifications/standards, military
specifications/standards/handbooks, other U.S. Government agency (for example: DOE, DOT, OSHA, etc.) standards,
etc., and other non-U.S. standards (for example: NATO STANAG, ISO, etc.).

DIP1.1.1 Subpackets. There are six subpackets for this packet:

Subpacket Applicability
1A Design drawings and associated lists
1B Program-unique specifications
1C Standardization documents
1D Software administrative information
1E Software
1F Software support documents

DIP1.2. Content of information subpackets. The information subpackets define the elements and documents/files to be
provided and correlates the information elements with the conceptual CM AIS database described in Appendices B and
C. Within the table, the inclusion of the element in the information subpacket is either mandatory (M) or optional (O).
For each subpacket, the subpacket number (for example: 1C) shall be followed by the various elements in the order
shown in Table DIP1-I, except that fields which are not applicable (denoted by blank) and optional fields (denoted by O)
for which data is not being submitted shall be skipped. Each element shall be preceded by the Data Element Tag as
shown in the table. The full field size for the data element, as shown in Appendix C, shall be used and shall immediately
follow the data element tag. No delimiters will be used between the fields. The end of each data subpacket shall be
indicated by the inclusion of "/end". The last column in the table contains a reference to the contents of the data element.

DIP1.2.1 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CM AIS database, but have the constant value indicated. Because they have constant values, they do not have
to be transmitted as part of the information subpacket.

DIP1.2.2.1 Subpacket 1A. The value of 'Document identifier type code' (sequence 4), 010.IDNTYP010, is always "N".

DIP1.2.2.2 Subpacket 1B.

a. The value of 'Document type code' (sequence 1), 010.DOCTYP010 is always 'P-SPEC'.

b. The value of 'Document identifier type code' (sequence 4), 010.IDNTYP010, is always "N".

c. If the value of 'Product type code' (sequence 33) is 'P' and the value of 'document source type code' (sequence 2) is
'C', then the value of 002.ENTTYP002 is "CAG", the value of 212.DOCTYP212 is 'P-SPEC', and the value of
'Document source' (sequence 3) is also entered in 210.ENTIDN002.

23
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
1
1 Document type code M M2 010.DOCTYP010 Appendix C, DED 0004
3 3 3 3
2 Document source type code M M M M M M 010.ENTTYP010 Appendix C, DED 0100

3 Document source M M M M M M 010.SRCIDN010 If the value of sequence 2 is 'A', see Appendix

C, DED 0069; if the value is 'C', see DED
0001; if the value is 'M', see DED 0170; if the
value is 'O', see DED 0002.
4 Document identifier type code M M M M 010.IDNTYP010 Appendix C, DED 0101 and Table B-I
5 Document identifier M M M M M M 010.DOCIDN010 Table B-I and for subpackets 1A, 1B, and 1C,
Appendix C, DED 0003; for subpackets 1D,
1E, and 1F, the transmitted field must be 120
characters, left justified and consist of an
alphanumeric identifier (Appendix C, DED
0003) or a title (Appendix C, DED 0120), as
appropriate for the type of document.
6 Document revision level M M M M M M 011.DOCREV011 The transmitted field must be 8 characters, left
justified and consist of either an alphanumeric
revision identifier (Appendix C, DED 0009), a
software version (Appendix C, DED 0062), or
a date (Appendix C, DED 0082), as
appropriate for the document type.

7 Originator M M M M M M 010.ORIGIN010 The transmitted field must be 36 characters, left

justified and consisting of either a CAGE code
(Appendix C, DED 0001), an organization
acronym (Apendix C, DED 0002), a company
name (Appendix C, DED 0170), or an author's
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

name (Appendix C, DED 0069).

8 CDCA M M M M M M 010.CCCENT010 Appendix C, DED 0239

9 CDCA effective date M M M M M M 010.CCCADT010 Appendix C, DED 0082

1
The value must be either "DWG", "DL", "IL", or "PL".
2
The value must be either "SWDOC" or "SVD".
3
The value must be either "C" or "M".

24
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
10 Document/Software Custodian M M M M M M 011.CUSORG011 The transmitted field must be 36 characters, left
justified and consisting of either a CAGE code
(Appendix C, DED 0001), an organization
acronym (Apendix C, DED 0002), a company
name (Appendix C, DED 0170), or an author's
name (Appendix C, DED 0069).

11 Document title/Software product name M M M M M M 011.DOCTIT011 Appendix C, DED 0008

12 Preparation Date M M M M M M 011.PREPDT011 Appendix C, DED 0082

13-30 Basic Document Protection subpacket M M M M M M See Data Information Data Information packet 8
Subpacket 8A

31 Separate Parts List flag O4 051.SEPCOD051 Appendix C, DED 0025

32 Control drawing type code O4 051.CONTYP051 Appendix C, DED 0032

33 Product type code/Software paradigm code M M M 100.PRDTYP100 or Appendix C, DED 0034 or 0163
400.PRDTYP400 or
913.PRDTYP913 or
914.PRDTYP914 or
150.SWPARA1505

34 CI indicator O4 060.CIFLAG060 Appendix C, DED 0023

6
35 CI nomenclature O O 060.CINOMN690 or Appendix C, DED 0047
100.CINOMN6907

36 Federal Supply Class Code O 100.FSCCOD100 Appendix C, DED 0073

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

4
Mandatory if the value of 'Document type' (sequence 1) is "DWG"; otherwise, must be blank.
5
For subpacket 1B: If the value of 'document source entity type code' (sequence 2) is 'C', use the Tag that starts with 100; if the value of 'document source entity type code' is 'M', use the Tag that starts with
913.
For subpacket 1C: If the value of 'document source entity type code' is 'O', use the Tag that starts with 400; if the value of 'document source entity type code' is 'M', use the Tag that starts with
914.
For subpacket 1F, use the Tag that starts with 150.
6
Must be blank unless the value of 'CI indicator' (sequence 34) is "Y".
7
Use the Tag that starts with 060 for information subpacket 1A and the Tag that starts with 100 for information subpacket 1B.

25
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
37 Interface control document code M 010.ICDCOD0106 Appendix C, DED 0030
8
38 Specification type code/Software support O O 100.SUBTYP100 or Appendix C, DED 0108 or 0107
document type code 185.SDOCSB1859

39 First Article Test Code O4 M 051.FRSTRT051 or Appendix C, DED 0077

101.FRSTRT10110

40 Specification category code M 101.SPCCAT101 Appendix C, DED 0105

41 Drawing size O 051.DWGSIZ051 Appendix C, DED 0112

42 Total sheets O 051.DWGSHT051 Appendix C, DED 0110

4311 Sheet number M 052.SHTNUM052 Appendix C, DED 0026

11
44 Sheet revision level M 052.SHTREV052 Appendix C, DED 0009
11
45 Sheet revision date O 052.SHTDAT052 Appendix C, DED 0082
12 13
46 Drawing note number O 080.NOTNUM080 Appendix C, DED 0251
14
47 Drawing note text O 080.NOTTXT080 Appendix C, DED 0252

8
Must be blank if value of 'Document type code' (sequence 1) is 'SVD'; mandatory if value of 'Document type code' is 'SWDOC'.
9
For subpacket 1B: Use the Tag that starts with 100
For subpacket 1F: Use the Tag that starts with 185.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

10
For subpacket 1A: Use the Tag that starts with 051.
For subpacket 1B: Use the Tag that starts with 101.
11
Repeat the series of fields 'Sheet number', 'Sheet revision level', and 'Sheet revision date' (sequence 43 through 45), as necessary.
12
Repeat this field as necessary. It must be followed by either (a) ‘Drawing note text’ (sequence 47), or (b) ‘Drawing note special conditions code’ (sequence 48), or (c) ‘Referenced document type’
(sequence 49), ‘Referenced document source (sequence 50), ‘Referenced document identifier’ (sequence 51), and optionally, ‘Referenced document revision level’ (sequence 52), or (d) ‘Referenced part
design source’ (sequence 53) and ‘Referenced part number’ (sequence 54), or (e) ‘Reverenced material source’ (sequence 55), ‘Referenced material identifier/name’ (sequence 56), and ‘Referenced material
identification (parameters & values)’ (sequence 57).
13
Must be blank unless the value of 'Document type code' (sequence 1) is either "DWG" or "PL".
14
Must be blank unless preceded by a 'Drawing note number' (sequence 41).

26
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
14
48 Drawing note special conditions code O 081.SPNOTE081 Appendix C, DED 0257
15 16
49 Referenced document type O O 067.ILTYPE065 or Appendix C, DED 0004
068.PLTYPE068 or
071.CDOCTY071 or
082.RDOCTY082 or
110.RDOCTY11017

5015 Referenced document source O O 067.CILCAG067 or Table B-I. For the Tag that starts with 067 or
068.PLCAGE068 or 068, see Appendix C, DED 0001. For the Tag
071.SRCIDN010 or that starts with 071, 082, or 110, the
082.SRCIDN010 or transmitted field must be 30 characters, left
110.SRCIDN01017 justified and consisting of either a CAGE code
(Appendix C, DED 0001), an organization
acronym (Appendix C, DED 0002), an author's
name (Appendix C, DED 0069), or a company
name (Appendix C, DED 0170), as appropriate
for the type of document.

5115 Referenced document identifier O O 067.CILNUM067 or Table B-I. For the Tag that starts with 067 or
068.PLNUMB068 or 068, see Appendix C, DED 0003. For the Tag
071.DOCIDN010 or that starts with 071, 082, or 110, the
082.DOCIDN010 or transmitted field must be 120 characters, left
110.DOCIDN01017 justified and consisting of either an
alphanumeric identifier (Appendix C, DED
0003) or a title (Appendix C, DED 0008) as
appropriate for the type of document.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

15
The fields 'Referenced document type' (sequence 49), 'Referenced document source' (sequence 50), and 'Referenced document identifier' (sequence 51), must either all be blank or all be nonblank. The field
'Referenced document revision level' (sequence 52) must be blank if 'Referenced document type' is blank. The series may be repeated as necessary. The combination of values appearing in these fields cannot
be the same as the combination of values for 'Document type code' (sequence 1), 'Document source' (sequence 3), 'Document identifier' (sequence 5), and 'Document revision level' (sequence 6).
16
If the value of 'Document type' (sequence 1) is "IL", then the value in this field must be either "PL" or "IL".
17
For subpacket 1A: If the value of 'Document type code' (sequence 1) is 'IL' and if the value of 'Referenced document type' (sequence 49) is 'IL', use the Tag that starts with 067; If the value of 'Document type
code' is 'IL' and the value of 'Referenced document type' is 'PL', use the Tag that starts with 068. If the value of 'Document type code' is 'DL', use the Tag that starts with 071. If the value of 'Document
type code' is 'DWG' or 'PL', use the the Tag that starts with 082.
For subpacket 1B: Use the Tag that starts with 110.

27
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
15
52 Referenced document revision level O O 067.CILREV067 or For the Tag that starts with 067, 068, or 071,
068.PLREVN068 or see Appendix C, DED 0009. For the Tags that
071.DLREVN071 or starts with 082 or 110, the transmitted field
082.RDOCRV082 or must be 8 characters, left justified and
110.RDOCRV11017 consisting of either an alphanumeric revision
(Appendix C, DED 0009),a date (Appendix C,
DED 0082),or a software version (Appendix C,
DED 0062, only if the document type is 'SW'),
as appropriate for the type of document.
5318 Referenced part design source O19 O 084.DESENT210 or The transmitted field must be 30 characters, left
111.DESENT21020 justified and consisting of either a CAGE code
(Appendix C, DED 0001), an organization
acronym (Apendix C, DED 0002), or a
company name (Appendix C, DED 0069).
5418 Referenced part number O O 084.PARNUM210 or Appendix C, DED 0024
111.PARNUM21020

5521 Referenced material source O19 083.DESENT200 The transmitted field must be 30 characters, left
justified and consisting of either a CAGE code
(Appendix C, DED 0001), an organization
acronym (Apendix C, DED 0002), or a
company name (Appendix C, DED 0069).
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

18
Fields 'Referenced part design source' and 'Referenced part number' (sequence 53 and 54) must either both be blank, or both be nonblank. Repeat this series as necessary. The combination of values in these
fields cannot be the same as any combination of values for the fields 'Document source' (sequence 3) and 'Defined part number' (sequence 64) in this subpacket.
19
Must be blank unless the value of 'Document type code' (sequence 1) is 'DWG' or 'PL'.
20
For subpacket 1A: Use the Tag that starts with 084.
For subpacket 1B: Use the Tag that starts with 111.
21
Fields 'Referenced material source', 'Referenced material identifier/name', and 'Referenced material identification (parameters & values)' (sequence 55 through 57) must either all be blank, or all be nonblank.
Repeat this series as necessary. The combination of values in these fields cannot be the same as any combination of values for the fields 'Document source' (sequence 3), 'Defined material identifier' (sequence
62), and 'Defined material identification parameters list' (sequence 63) in this subpacket.

28
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
21
56 Referenced material identifier/name O 083.MATGID200 The transmitted field must be 120 characters,
left justified and consisting of either a material
specification identifier (Appendix C, DED
0192), or a commercial material name
(Appendix C, DED 0191).
5721 Referenced material identification (parameters & O 083.MATIDN200 Appendix C, DED 0038
values)

58 Parts list O22 See Data Information Data Information Packet 7

subpacket 7A

59 Enterprise identification type code M 002.ENTTYP002 Appendix C, DED 0050

60 Organization type identifier O23 004.ORGTYP004 Appendix C, DED 0095

61 DOD organization type identifier O24 034.DODTYP034 Appendix C, DED 0097
25
62 Standardization document series type code O 408.SERIES408 Appendix C, DED 0242
26 26
63 Defined material identifier O O 200.MATGID200 The transmitted field must be 120 characters,
left justified and consisting of either a material
specification identifier (Appendix C, DED
0192), or a commercial material name
(Appendix C, DED 0191).

6427 Defined Material identification parameters list O26 O26 200.MATIDN200 Appendix C, DED 0038
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

22
Must be blank unless either (a) the value of 'document type code' (sequence 1) is 'PL', or (b) the value of 'document type code' is 'DWG' and the value of 'separate parts list flag' (sequence 31) is 'I'.
23
Mandatory if the value of 'Enterprise identification type code' (sequence 59) is 'ORG'; otherwise, must be blank.
24
Mandatory if the value of 'Organization type identifier' (sequence 60) is 'DOD'; otherwise, must be blank.
25
Mandatory if the value of 'Organization type identifier' (sequence 60) is 'DOD'; otherwise, optional.
26
Mandatory entry if the value of 'Product type code' (sequence 33) is 'M'; must be blank for all other values of 'Product type code'.
27
Repeat the series of fields sequence 62, 63, and 65 as necessary.

29
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
28 29 30 30 31 31
65 Defined Part Number O O O O O 210.PARNUM210 or Appendix C, DED 0024
164.PARNUM210 or
166.PARNUM21032

66 Defined Part/Material status code O29 O33 O33 054.PARSTA054 or Appendix C, DED 0035
105.PARSTA105 or
107.MATSTA107 or
423.PARSTA423 or
437.PARSTA437 or
422.MATSTA422 or
435.MATSTA43534

28
For subpacket 1A: Rrepeat the series of fields sequence 65 through 69 as necessary.
For subpackets 1B and 1C: Repeat the series of fields sequence 65 and 66 as necessary.
29
Must be blank unless the value of 'Document type code' (sequence 1) is 'DWG' or 'PL'.
30
Mandatory if the value of 'Product type code' (sequence 33) is 'P'; must be blank for all other values of 'Product type code'.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

31
Mandatory if the value of 'Software paradigm' (sequence 33) is 'P'; must be blank for all other cases. This field may be repeated as necessary.
32
For subpackets 1A, 1B, and 1C: Use the Tag that starts with 210.
For subpackets 1D and 1E: If the value of 'Software source enterprise type code' (sequence 72) is 'CAG', use the Tag that starts with 164; if the value of 'Software source enterprise type code' is 'COM', use
the Tag that starts with 166. In both cases, a subpacket 1A for the software drawing should have preceded this subpacket.
33
Must be blank if the value of the 'product type code' (sequence 33) is 'N'; must be nonblank for all other valued of 'product type code'.
34
For subpacket 1A: Use 054.PARSTA054.
For subpacket 1B: Use 105.PARSTA105 and 107.MATSTA107 for parts and materials (respectively).
For subpacket 1C: If the value of 'Enterprise identification type code' (sequence 59) is 'ORG', use 423.PARSTA423 and 422.MATSTA422 for parts and materials (respectively). If the value of 'Enterprise
identification type code' is 'CAG', use 437.PARSTA437 and 435.MATSTA435 for parts and materials (respectively).

30
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
35 36
67 Vendor identification O 055.DESENT200 or Transmitted field must be 30 characters, left
056.DESENT21037 justified and consisting of either a CAGE code
(Appendix C, DED 0001), an organization
acronym (Appendix C, DED 0002), or a
company name (Appendix C, DED 0170)

6835 Equivalent vendor part number O38 056.VPARNO056 Appendix C, DED 0024

6935 Equivalent vendor material identifier O38 055.VMATID055 Appendix C, DED 0048
70 Software source identifier O39 187.SWSORC170 The transmitted field must be 36 characters, left
justified and consisting of either a CAGE code
(Appendix C, DED 0001), an organization
acronym (Appendix C, DED 0002), an author’s
name (Appendix C, DED 0069), or a company
name (Appendix C, DED 0170).

71 Software identifier M M M 170.SWIDEN170 or The transmitted field must be 248 characters,

187.SWIDEN17040 left justified and consisting of either a part
identifier (Appendix C, DED 0024), a software
alphanumeric identifier (Appendix C, DED
0088), or a software product identifier
(Appendix C, DED 0262).

72 Software source enterprise type code M M 152.SRCTYP152 Appendix C, DED 0050

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

35
Repeat 'Vendor identification' (sequence 67) and 'Equivalent vendor part number' (sequence 67) or 'Vendor identification' and 'Equivalent vendor material identification' (sequence 69) as necessary.
Sequence 68 and 69 can not both be nonblank.
36
Must be blank unless value of 'Control drawing type code' (sequence 32) is 'P', 'S', 'V' or 'X', in which case, it must be nonblank.
37
Use the Tag that starts with 55 with nonblank 'Equivalent vendor material identifier' (sequence 69); use the Tag that starts with 56 with nonblank 'Equivalent vendor part number' (sequence 68).
38
Must be blank unless 'Vendor identification' (sequence 66) is nonblank.
39
Mandatory if the value of 'document type code' (sequence 1) is 'SWDOC'; otherwise, must be blank.
40
For subpackets 1D and 1E: Use the Tag that starts with 170.
For subpacket 1F: Use the Tag that starts with 187.

31
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
41 41
73 Software root-identifier O O 155.SWROOT155 Appendix C, DED 0190
41 41
74 Software dash number O O 156.SWDASH156 Appendix C, DED 0222

75 Software compiler name O O 151.COMIDN151 Appendix C, DED 0031

76 Software compiler version O O 151.COMVER151 Appendix C, DED 0064

77 Computer hardware name O O 151.HWNAME151 Appendix C, DED 0031

78 Software linker name O O 151.LNKIDN151 Appendix C, DED 0031

79 Software linker version O O 151.LNKVER151 Appendix C, DED 0064

80 Operating system name M M 151.SYSIDN151 Appendix C, DED 0031

81 Operating system version O O 151.SYSVER151 Appendix C, DED 0064

82 Supported graphical drawing revision level O42 064.GDWGRV064 Appendix C, DED 0009
43
83-116 Document Representation subpacket M M M M M See Data Information Data Information Packet 10
subpacket 10A

117 Document revision status code M M M M M M 850.REVSTA850 Appendix C, DED 0021

118 Document revision status date M M M M M M 850.STADAT850 Appendix C, DED 0082

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

41
Mandatory if the value of 'Software paradigm' (sequence 33) is 'D'; must be blank for all other cases.
42
Must be blank unless the value of 'Document type code' is "PL". Repeat as necessary.
43
May be repeated to allow both software source and executable code to be addressed.

32
Draft MIL-STD-2549
Data Information Packet 1

TABLE DIP1-I. Drawings, specifications, standards, software and software support documents

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
1A 1B 1C 1D 1E 1F
44 45 46 47
119 CAGE code of ECP authorizing this revision O O O O O 270.ECPCAG250 or Appendix C, DED 0001
285.ECPCAG250 or
286.ECPCAG250 or
287.ECPCAG250 or
288.ECPCAG25048

12044 Identifier of ECP authorizing this revision O O O O O 270.ECPNUM250 or Appendix C, DED 0003
285.ECPNUM250 or
286.ECPNUM250 or
287.ECPNUM250 or
288.ECPNUM25048
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

44
'CAGE code of ECP authorizing this revision' and 'Identifier of ECP authorizing this revision' (sequence 119 and 120) must both be blank, or both be nonblank.
45
Must be blank unless the value of 'document type code' (sequence 1) is either 'DWG' or 'PL'.
46
Must be blank unless the value of 'document source type code' (sequence 2) is 'C'.
47
Must be blank unless the value of 'DOD organization type identifier' (sequence 61) is 'OSD' and the 'standardization document series type code' (sequence 61) is 'DEFSPEC'.
48
For subpacket 1A: If the value of 'document type code' (sequence 1) is 'DWG', use the Tag that starts with 285; otherwise use the Tag that starts with 286.
For subpacket 1B: Use the Tag that starts with 287.
For subpacket 1C: Use the Tag that starts with 288.
For subpacket 1D or 1E: Use the Tag that starts with 270.

33
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

Draft MIL-STD-2549
Data Information Packet 1

d. If the value of 'Product type code' (sequence 33) is 'M' and the value of 'document source type code' (sequence 2)
is 'C', then the value of 002.ENTTYP002 is "CAG", the value of 200.SRCTYP200 is "S", the value of 'Document
source' (sequence 3) is also entered in 200.ENTIDN002, and the value of 'Document type code' (sequence 1) and
'Document identifier' (sequence 5) are concatenated and entered in 200.MATGID200.

DIP1.2.2.3 Subpacket 1C. The value of 'Document type code' (sequence 1), 010.DOCTYP010 is always "STDDOC".

DIP1.2.2.4 Subpacket 1D and 1E.

a. The value of 'Document type code' (sequence 1), 010.DOCTYP010 is always "SW".

b. The value of 'Document source' (sequence 3) is also entered in 170.SWSORC170.

c. The value of 'Defined part number' (sequence 65) is also entered in 210.PARNUM210.

DIP1.2.2.5 Subpacket 1F.

a. The value of 'document type code' (sequence 1) is also entered in 170.SVDTYP180 for the software with a
'software source identifier' which is the same value as the entry for 'document source' (sequence 3,
010.SRCIDN010) and a 'software identifier' as included in sequence 66.

b. The value of 'document identifier' (sequence 5) is also entered in 170.SVDNUM180 for the software with a
'software source identifier' which is the same value as the entry for 'document source' (sequence 3,
010.SRCIDN010) and a 'software identifier' as included in sequence 66.

DIP1.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

34
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 2

General Document

DIP2.1. Purpose. Includes information about and may include actual documents (or access to documents) that are
ancillary to the configuration definition but necessary to management of the configuration of the deployed product, that
are used for logistics support of the product, or that are submitted to the Government for some other purpose. This
includes technical manuals/orders and their changes/supplements, decision documents, and other miscellaneous contract
data items associated with the product. For documents which define parts or materials, or standardize products,
materials or processes (including software) use Data Information Packet 1. For configuration changes or the transfer of
CDCA of a previously delivered document, use Data Information Packet 4. For contracts, use Data Information Packet
6.

DIP2.1.1 Subpackets. There are two subpackets for this packet:

Subpacket Applicability
2A General documents
2B Document supplements

DIP2.2. Content of data information packets. The data information subpackets define the elements and documents/files
to be provided and correlates the information elements with the conceptual CM AIS database described in Appendices B
and C. Within the table, the inclusion of the element in the information subpacket is either mandatory (M) or optional
(O). For each subpacket, the subpacket number (for example: 2A) shall be followed by the various elements in the
order shown in Table DIP2-I, except that fields which are not applicable (denoted by blank) and optional fields (denoted
by O) for which data is not being submitted shall be skipped. Each element shall be preceded by the Data Element Tag
as shown in the table. The full field size for the data element, as shown in Appendix C, shall be used and shall
immediately follow the data element tag. No delimiters will be used between the fields. The end of each data subpacket
shall be indicated by the inclusion of "/end". The last column in the table contains a reference to the contents of the data
element.

TABLE DIP2-I. General document

Seq # Field Name Data Information Data Element Tag For content and
Subpacket validation instructions,
see
2A 2B
1 Document type code M1 010.DOCTYP010 Appendix C, DED 0004

2 Document source type code M M 010.ENTTYP010 Table B-I and Appendix C,

DED 0100

1
Must be ‘ANALYS’, ‘BOOK’, ‘DID’, ‘MISC’, ‘PERIODL’, ‘PLNPROC’, ‘REPORT’, ‘TECHMAN’, or ‘TRD’. (For definitions of these
document types, see Appendix C, DED 0004.)

35
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 2

TABLE DIP2-I. General document

Seq # Field Name Data Information Data Element Tag For content and
Subpacket validation instructions,
see
2A 2B
3 Document source M M 010.SRCIDN010 The transmitted field must be
36 characters, left justified
and consisting of either a
CAGE code (Appendix C,
DED 0001), an organization
acronym (Appendix C, DED
0002), a company name
(Appendix C, DED 0170), or
the Author's name (Appendix
C, DED 0069)..

4 Document identifier type code M M 010.IDNTYP010 Appendix C, DED 0101 and

Table B-I

5 Supplement document type code M 601.SUPTYP601 Appendix C, DED 0162

6 Document identifier M M 010.DOCIDN010 DIP2.2.1.a

2
7 Technical manual iteration type code O 554.ITTYPE554 Appendix C, DED 0196

8 Document revision level M M 011.DOCREV011 DIP2.2.1.b

9 Supplement issue date M 611.SISSDT611 or Appendix C, DED 0082

612.OISSDT612 or
613.RISSDT613 or
614.TOPISS6143

10 Originator M M 010.ORIGIN010 The transmitted field must be

36 chanrachters, left justified
and consisting of either a
CAGE code (Appendix C,
DED 0001), an organization
acronym (Appendix C, DED
0002), a company name
(Appendix C, DED 0170), or
an author's name (Appendix
C, DED 0069)

11 CDCA M M 010.CCENT010 Appendix C, DED 0239

12 CDCA effective date M M 010.CCCADT010 Appendix C, DED 0082

13 Document custodian M M 011.CUSORG011 The transmitted field must be
36 chanrachters, left justified
and consisting of either a
CAGE code (Appendix C,
DED 0001), an organization
acronym (Appendix C, DED
0002), a company name
(Appendix C, DED 0170), or
an author's name (Appendix
C, DED 0069)

14 Document title M M 011.DOCTIT011 Appendix C, DED 0008

15 Preparation date M M 011.PREPDT011 Appendix C, DED 0082

2
Mandatory if the value of ‘document type code’ (Sequence 1) is ‘TECHMAN’; otherwise, must be blank.
3
Use the Tag that starts with 611 if the value of ‘supplement document type code’ (Sequence 5) is ‘S-SUP’; use the Tag that starts with 612 if the
value of sequence 5 is ‘O-SUP’; use the Tag that starts with 613 if the value of sequence 5 is ‘R-SUP’; use the Tag that starts with 614 if the value
of sequence 5 is ‘TOPS’.

36
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 2

TABLE DIP2-I. General document

Seq # Field Name Data Information Data Element Tag For content and
Subpacket validation instructions,
see
2A 2B
16 DOD indicator code O2 550.DODCOD550 Appendix C, DED 0143
17 Technical manual lead activity indicator O2 550.ACQCOD550 Appendix C, DED 0006

18 DOD service identifier O4 552.SERVID552 Appendix C, DED 0002

5
19 Navy command identifier O 559.NAVCOM559 Appendix C, DED 0002
20-37 Basic Document Protection packet M M See Data Information Data Information Packet 8
Subpacket 8A

38-756 Document Representation Subpacket M M See Data Information Data Information Packet 10
Subpacket 10A

76 Document revision status code M M 850.REVSTA850 Appendix C, DED 0021

77 Document revision status date M M 850.STADAT850 Appendix C, DED 0082

DIP2.2.1 Content instructions.

a. For all Data Information Subpackets Table B-I and, if the value of 'document identifier type code' (sequence 4) is
'N', see Appendix C, DED 0003. If the value of sequence 4 is 'T', see Appendix C, DED 0008. For Data
Information Subpacket 2B, also see the appropriate DED in Appendix C as indicated in Table DIP2-II.

TABLE DIP2-II. Reference document identifier DEDs for supplement documents

Value of Supplement document type code See DED:

O-SUP 0218

R-SUP 0218

S-SUP 0218
SCN 0149
TM-CHG 0135

TOP-SUP 0218

b. For Data Information Subpacket 2A, see Appendix C, DED 0009. For Data Information Subpacket 2B, see the
appropriate DED in Appendix C as indicated in Table DIP2-III.

4
Mandatory if the value of ‘DOD indicator code’ (Sequence 16) is ‘O’; otherwise, must be blank.
5
Mandatory if the value of ‘DOD service identifier’ (Sequence 18) is ‘USN’; otherwise, must be blank.
6
Repeat this series of fields for each document representation as necessary.

37
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 2

TABLE DIP2-III. Reference revision identifier DEDs for supplement documents

Value of Supplement document type code See DED:

O-SUP 0244

R-SUP 0244

S-SUP 0244

SCN 0193
TM-CHG 0134

TOP-SUP 0244

DIP2.2.2 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CSA database, but have the constant value indicated. Because they have constant values, they do not have to
be transmitted as part of the information subpacket.

DIP2.2.2.1 Subpacket 2B. The value of 'Document type code' (sequence 1), 010.DOCTYP010, is 'DOCSUP'.

DIP2.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

38
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 3

Product/Asset Configuration

DIP3.1. Purpose. Includes the basic part/material identification, basic information concerning serialization/lot/block
tracking, correlation of serial and lot and block numbers when multiple tracking numbers are used for a single item,
actual current configuration (by part and serial/lot number) of fielded hardware/software, and update information
concerning changes to fielded hardware/software as a result of modification, maintenance, re-grouping, or retrofit.

DIP3.1.1 Subpackets. There are 8 subpackets for this packet:

Subpacket Applicability
3A Basic part/material identification (includes electronic part models)
3B Basic part/material traceability information
3C As-built/as delivered configuration
3D Changes to assemblies (remove & replace, etc.)
3E Changes as a result of re-grouping
3F Changes as a result of part modification
3G NSN assignment
3H Replacement/superseded/substitute parts/material information and company-assigned equivalent
part/material identifiers

DIP3.2. Content of data information subpackets. The data information subpackets define the elements and documents/
files to be provided and correlates the information elements with the conceptual CM AIS database described in
Appendices B and C. Within the table, the inclusion of the element in the information subpacket is either mandatory
(M) or optional (O). For each subpacket, the subpacket number (for example: 3C) shall be followed by the various
elements in the order shown in Table DIP3-I, except that fields which are not applicable (denoted by blank) and optional
fields (denoted by O) for which data is not being submitted shall be skipped. Each element shall be preceded by the
Data Element Tag as shown in the table. The full field size for the data element, as shown in Appendix C, shall be used
and shall immediately follow the data element code. No delimiters will be used between the fields. The end of each data
subpacket shall be indicated by the inclusion of "/end". The last column in the table contains a reference to the contents
of the data element.

DIP3.2.1 Content instructions.

a. For subpackets 3A through 3G, enter the design enterprise of the finished part, material, assembly, or regrouped
lot. For subpacket 3H, enter the design enterprise of the replacement, superseding, or substitute part, material, or
assembly.

b. For subpackets 3A through 3G, enter the part number of the finished part, assembly, or regrouped lot or the
material identifier of the finished material or regrouped lot. For subpacket 3H, enter the part number or material
identifier of the replacement, superseding, or substitute part, material, or assembly.

c. Enter the product-tracking base-identifier which is the basis for the assignment of unique tracking identifiers. The
order of preference for the product-tracking base-identifier is (1) the type and model portion of the configuration
item designation (see Appendix B, Table B-II), (2) the drawing number of a tabulated part or assembly drawing,
(3) the drawing number of one of the non-tabulated parts (or assemblies) within a group of like items, (4) the
specification number of parts or materials defined by a program-unique specification or standardization document,
(5) the part number of a standard part, or (6) the material identifier of any material defined in terms like class,
grade, type, etc., without a part number.

d. Enter the identifier and type of the document which defines the part or material.

39
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
1 Part/material design enterprise type code M 002.ENTTYP002 Appendix C, DED 0050

2 Part/Material design enterprise identifier M M M M M M M M 200.DESENT200 or DIP3.2.1.a. The transmitted field

210.DESENT210 or must be 30 characters, left justified
240.DESENT210 or and consisting of either a CAGE
241.DESENT200 or code (Appendix C, DED 0001), an
521.DESENT210 or organization acronym (Apendix C,
522.DESENT210 or DED 0002), or a company name
523.DESENT210 or (Appendix C, DED 0170).
526.DESENT200 or
529.DESENT210 or
530.DESENT2001

3 Part/Material identifier M M M M M M M M 200.MATGID200 or DIP3.2.1.b and for part numbers

210.PARNUM210 or (###.PARNUM210) see Appendix
240.PARNUM210 or C, DED 0024; for materials
241.MATGID200 or (###.MATGID200) the transmitted
521.PARNUM210 or field must be 120 characters, left
522.PARNUM210 or justified and consisting of either a
523.PARNUM210 or material specification identifier
526.MATGID200 or (Appendix C, DED 0192) or a
529.PARNUM210 or comercial material name (Appendix
530.MATGID2001 C, DED 0191).
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

1
For subpackets 3A, 3G, and 3H: Use The Tag that starts with 200 for items not identified by a part number and The Tag that starts with 210 for items identified by a part number.
For subpacket 3B: If the item is identified by a part number and is tracked by a manufacturer's serial number, use The Tag that starts with 521; if it is tracked by a Government-assigned serial number, use
The Tag that starts with 522; if it is tracked by a lot number, use The Tag that starts with 523; if it is tracked by a date code, use The Tag that starts with 529. If the item is not identified by a part number
and is tracked by a lot number, use The Tag that starts with 526; if it is tracked by a date code, use the Tag that starts with 530.
For subpackets 3C and 3D: If the item is identified by a part number, use the Tag that starts with 240; if the item is not identified by a part number, use the Tag that starts with 241.
For subpacket 3E: If the item is identified by a part number, use the Tag that starts with 523, if the item is not identified by a part number, use the Tag that starts with 526.
For subpacket 3F: If the item is identified by a part number and is tracked by a manufacturer's serial number, use the Tag that starts with 521; if it is tracked by a Government-assigned serial number, use the
Tag that starts with 522; if it is tracked by a lot number, use the Tag that starts with 523. If the item is not identified by a part number and is tracked by a lot number, use the Tag that starts with 526.

40
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
4 Material identification parameter list O2 O2 O2 O2 O2 O2 O2 O2 200.MATIDN200 or Appendix C, DED 0038
241.MATIDN200 or
526.MATIDN200 or
530.MATIDN2003

5 Part/material name M M 200.MATNAM200 or Appendix C, DED 0191 and DED

210.PARNAM2094 0113

6 NSN O M 200.NSNNUM345 or Appendix C, DED 0049

210.NSNNUM3454

7 Product tracking-base source code O5 M M M M M 500.TRKSCD500 Appendix C, DED 0103

5
8 Product-tracking base-identifier O M M M M M 200.BASNUM500 or DIP3.2.1.c and Appendix C, DED
210.BASNUM5004 00566

2
Mandatory for materials not identified by a part number; must be blank for items identified by a part number.
3
For subpackets 3A and 3G, use the Tag that starts with 200.
For subpacket 3B, if the item is tracked by a lot number, use the Tag that starts with 526; if it is tracked by a date code, use the Tag that starts with 530.
For subpackets 3C and 3D, use the Tag that starts with 241.
For subpackets 3E and 3F, use the Tag that starts with 526.
4
Use the Tag that starts with 210 for items identified by part number and the Tag that starts with 200 for items not identified by part number.
5
The ‘product tracking-base source code’ (sequence 7) and the ‘product-tracking base-identifier’ (sequence 8) are paired fields; either both must be blank, or both must be nonblank.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

6
If the value of ‘product tracking-base source code’ (sequence 7) is ‘C’, see Appendix A, DED 0045; the size of the transmitted field is 43.
If the value of sequence 7 is ‘D’, the transmitted field size is 44 and consists of the concatenation of the design CAGE code (DED 0001), the drawing alphanumeric identifier (DED 0003), and the document
type code (DED 0004) which must have a value of ‘DWG’.
If the value of sequence 7 is ‘M’, the transmitted field size is 192 and consists of the concatenation of the material design enterprise (30 characters, left justified which are either a CAGE code [DED 0001],
an organization acronym [DED 0002], or a company name [DED 0170]), the material identifier (120 characters, left justified which is either an alphanumeric identifier [DED 0009] or a material name
[DED 0008]), and a material identifying parameter list (DED 0038).
If the value of sequence 7 is ‘P’, the transmitted field size is 62 and consists of the concatenation of the part design enterprise (30 characters, left justified which are either a CAGE code [DED 0001], an
organization acronym [DED 0002], or a company name [DED 0170]) and a part identifier (DED 0024).
If the value of sequence 7 is ‘S’, the transmitted field size is 69 and consists of the concatenation of the document source enterprise (30 characters, left justified which are either a CAGE code [DED 0001],
an organization acronym [DED 0002], or a company name [DED 0170]), a document alphanumeric identifier (DED 0009), and a document type code (DED 0004) which must be ‘STDDOC’.
If the value of sequence 7 is ‘U’, the transmitted field size is 44 and consists of the concatenation of the design CAGE code of the specification (DED 0001), the document alphanumeric identifier (DED
0003), and the document type code (DED 0004) which must be ‘P-SPEC’.

41
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
9 Defining document identifier and type code M 053.DWGNUM050 and DIP3.2.1.d and for engineering
053.DOCTYP010, or drawings (053.DWGNUM050 &
104.DOCNUM020 and 053.DOCTYP010), see Appendix
104.DOCTYP010, or C, DEDs 0009 and 0004; for paired
106.MATDOC103, or document number and type
201.MATDOC421, or (###.DOCNUM### and
211.DOCNUM020 and ###.DOCTYP###), see Appendix
211.DOCTYP010, or C, DEDs 0003 and 0004; for
434.MATDOC433, or materials (###.MATDOC###), see
436.DOCNUM020 and Appendix C, DED 0192; for paired
436.DOCTYP010, or document identifier and type
919.DOCIDN919 and (###.DOCIDN### and
919.DOCTYP010, or ###.DOCTYP###), see Appendix
923.MATDOC923, or C, DEDs 0009 (for alphanumeric
924.MATNAM9227 identifiers) or 0008 (for document
titles), and 0004; for field
MATNAM, see Appendix C, DED
0191.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

7
If the part/material design enterprise type code (sequence 1) is 'CAG' and the item is identified by a part number, use the Tag that starts with 053 for document type 'DWG'; use the Tag that starts with 104 for
document type 'P-SPEC'; use the Tag that starts with 211 for document type 'STDDOC'.
If the part/material design enterprise type code is 'CAG' and the item is not identified by a part number, use the Tag that starts with 106 for document type 'P-SPEC'; use the Tag that starts with 434 for
document type 'STDDOC'.
If the part/material design enterprise type code is 'ORG' and the item is identified by a part number, use the Tag that starts with 211; if it is not identified by a part number, use the Tag that starts with 201.
If the part/material design enterprise type code is 'COM' and the item is identified by a part number, use the Tag that starts with 919.
If the part/material design enterprise type code is 'COM' and the item is not identified by a part number, use the Tag that starts with 923 for document type 'P-SPEC' or 'STDDOC'; use the Tag that starts with
924 if there is no defining document.

42
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
108 Can be substituted for/replaces part/material O 206.RMENID206 or DIP3.2.1.e and for superseded or
source, or has company stock number9 207.RMENID207 or replaced items (the Tag that starts
assigned by 216.RENTID216 or with 206, 207, 216 or 217), see
217.RENTID217 or Appendix C, DED 0001 (for CAGE
928.COMNAM005 or code), 0002 (for organization
929.COMNAM00510 acronym), or 0170 (for company
name); or for company stock
numbers (the Tag that starts with
928 or 929) see Appendix C, DED
0170
118 Can be substituted for/replaces part/material O 206.RMGNID206 or DIP3.2.1.e. For superseded or
identifier, or is company stock number9 of 207.RMGNID206 or replaced items identified by a part
216.RPARNO216 or number (Tags starting with 216 or
217.RPARNO217 or 217), see Appendix C, DED 0024.
928.STKNUM927 or For company stock numbers (Tags
929.STKNUM92710 starting with 928 or 929), see
Appendix C, DED 0186. For
superseded or replaced items not
identified by a part number (Tags
starting with 206 or 207), the
transmistted field must be 120
characters, left justified and
consisting of either a material
specification identifier (Appendix
C, DED 0192) or a commercial
material name (Appendix C, DED
0191).
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

8
Either the substitute source and identifier (sequence 10 and 11) must be nonblank, or the substitute NSN (sequence 13) must be nonblank.
9
Company stock numbers are alternate identifiers for items for which the company is not the original design activity. They are frequently referred to by terms such as `company part numbers', 'company
equivalent part numbers', or `internal part numbers'.
10
If the replacement/superseding/substitute item (in sequence 2, 3, and 4) is identified by a part number and the replaced/superseded item (here) is identified by a part number, use the Tag that starts with 216;
if the replaced/superseded item (here) is not identified by a part number, use the Tag that starts with 207; if this is a company stock number, use the Tag that starts with 929.
If the replacement/superseding/substitute item (in sequence 2, 3, and 4) is not identified by a part number and the replaced/superseded item (here) is identified by a part number, use the Tag that starts with
217; if the replaced/superseded item (here) is not identified by a part number, use the Tag that starts with 206; if this is a company stock number, use the Tag that starts with 928.

43
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
12 Can be substituted for/replaces material O11 206.RMMTID206 or DIP3.2.1.e and Appendix C, DED
identification parameter list. 207.RMMTID20712 0038

138 Can be substituted for/replaces NSN O 346.OLDNSN346 Appendix C, DED 0049

14 Replacement type code M 206.REPTYP206 or Appendix C, DED 0106

207.REPTYP207 or
216.REPTYP216 or
217.REPTYP217 or
34628.REPTYP346 or
DIP4H.1313

15 Interchangeability code O 206.ONEWAY206 or Appendix C, DED 0063

207.ONEWAY207 or
216.ONEWAY216 or
217.ONEWAY21713

11
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

Mandatory for materials not identified by a part number; must be blank for items identified by a part number.
12
If the replacement/superseding/substitute item (in sequence 2, 3, and 4) is identified by a part number and the replaced/superseded item (here) is not identified by a part number, use the Tag that starts with
207.
If the replacement/superseding/substitute item (in sequence 2, 3, and 4) is not identified by a part number and the replaced/superseded item (here) is not identified by a part number, use the Tag that starts
with 206.
13
If the replaced NSN (sequence 13) is nonblank, use the Tag that starts with 328.
If the replaced NSN (sequence 13) is blank, the replacement/superseding/substitute item (in sequence 2, 3, and 4) is identified by a part number, and the replaced/superseded item (sequence 10 and 11) is
identified by a part number, use the Tag that starts with 216; if the replaced/superseded item (sequence 10 through 12) is not identified by a part number, use the Tag that starts with 207.
If the replaced NSN (sequence 13) is blank, the replacement/superseding/substitute item (in sequence 2, 3, and 4) is not identified by a part number, and the replaced/superseded item (sequence 10 and 11) is
identified by a part number, use the Tag that starts with 217; if the replaced/superseded item (sequence 10 through 12) is not identified by a part number, use the Tag that starts with 206.
If the item identifier (sequence 10 and 11) is a company stock number, use DIP3H.13 and enter a value of 'C'.

44
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
16 Manufacturer identifier M M M M M 515.MFRCAG515 or DIP3.2.1.f and Appendix C, DED
242.AMFRCG242 or 0001
243.AMFRCG243 or
244.AMFRCG244 or
245.MFRCAG515 or
524.RMFRCG524 or
527.RMFRCG527 or
531.MFRCAG515 or
532.MFRCAG515 or
533.MFRCAG515 or
534.MFRCAG51514

17 Date of manufacture, maintenance, M M M M M 515.MFRDAT515 or DIP3.2.1.g and Appendix C, DED

modification, retrofit, or regrouping action 242.STATDT242 or 0082
243.STATDT243 or
244.STATDT244 or
245.STATDT24515

18 Time of manufacture, maintenance, M M M M M 242.STATTM242 or DIP3.2.1.h and Appendix C, DED

modification, retrofit, or regrouping action 243.STATTM243 or 0160
244.STATTM244 or
245.STATTM24515
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

14
For subpacket 3B: Use the Tag that starts with 515.
For subpackets 3C and 3D: If the assembly item (sequence 2 through 4) is identified by a part number and if the component item product type code (sequence 25) is 'P', use the Tag that starts with 242; if it is
'M', use the Tag that starts with 243; if it is 'S', use the Tag that starts with 245. If the assembly item (sequence 2 through 4) is not identified by a part number, the component item product type code
(sequence 25) must be 'M'; use the Tag that starts with 244.
For subpacket 3E: If the assembly item (sequence 2 through 4) is identified by a part number, use the Tag that starts with 524; if it is not identified by a part number, use the Tag that starts with 527.
For subpacket 3F: If the product tracking number type code (sequence 19) is 'M', use the Tag that starts with 531; if it is 'G', use the Tag that starts with 532; if it is 'L' and the modified item (sequence 2
through 4) is identified by a part number, use the Tag that starts with 533 but if it is not identified by a part number, use the Tag that starts with 534.
15
For subpackets 3B, 3E, and 3F: Use the Tag that starts with 515.
For subpackets 3C and 3D: If the assembly item (sequence 2 through 4) is identified by a part number and if the component item product type code (sequence 25) is 'P', use the Tag that starts with 242; if it is
'M', use the Tag that starts with 243; if it is 'S', use the Tag that starts with 245. If the assembly item (sequence 2 through 4) is not identified by a part number, the component item product type code
(sequence 25) must be 'M'; use the Tag that starts with 244.

45
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
19 Product tracking number type code and M M M M M 515.TRKTYP515 and DIP3.2.1.i and for paired tracking
sequentially-assigned tracking identifier 515.TRKIDN515, or type and identifiers
242.ATRKID242, or (###.TRKTYP515 &
243.ATRKID243, or ###.TRKIDN515), see Appendix C,
244.ATRKID244, or DEDs 0057 and 0058; for all
245.TRKTYP515 and others, see Appendix C, DED 0175
245.TRKIDN515, or
524.RLOTNO524, or
527.RLOTNO527, or
531.MSNNUM516, or
532.GSNNUM517, or
533.LOTNUM518, or
534.LOTNUM51814

20 Modification performed by M 531.RMFRCG531 or DIP3.2.1.j and Appendix C, DED

532.RMFRCG532 or 0001
533.RMFRCG533 or
534.RMFRCG53416

2117 Alternate product tracking number type code O O 515.TRKTYP515 DIP3.2.1.k and Appendix C, DED
0057
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

16
If the product tracking number type code (sequence 19) is 'M', use the Tag that starts with 531; if it is 'G', use the Tag that starts with 532; if it is 'L' and the modified item (sequence 2 through 4) is identified
by a part number, use the Tag that starts with 533 but if it is not identified by a part number, use the Tag that starts with 534.
17
The series of fields consisting of ‘alternate product tracking number type code’ and ‘alternate product tracking identifier’ (sequence 21 and 22) may be repeated as necessary.

46
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
2217 Alternate product tracking identifier O O 521.BLKNUM520 or DIP3.2.1.k and Appendix C, DED
521.LOTNUM518 or 0175
522.BLKNUM520 or
522.LOTNUM518 or
522.MSNNUM516 or
525.BLKNUM520 or
528.BLKNUM52018

23 Lot size (quantity and unit of measure) O19 O20 O20 523.QUANTY523 and Appendix C, DEDs 0019 and 0054
523.UOMCOD523, or
524.QUANTY524 and
524.UOMCOD524, or
526.QUANTY526 and
526.UOMCOD526, or
527.QUANTY527 and
527.UOMCOD527, or
529.QUANTY529 and
529.UOMCOD529, or
530.QUANTY530 and
530.UOMCOD53021

18
If the item is identified by a part number (sequence 4 is blank) and if the 'Product tracking number type code' (in sequence 19) is 'G' and the 'Alternate product tracking number type code' (sequence 21) is 'L',
use 522.LOTNUM518; if it is 'M', use 522.MSNNUM516; if it is 'B', use 522.BLKNUM520.
If the item is identified by a part number (sequence 4 is blank) and if the 'Product tracking number type code' (in sequence 19) is 'M' and the 'Alternate product tracking number type code’ (sequence 21) is
'L', use 521.LOTNUM518; if it is 'B', use 521.BLKNUM520.
If the item is identified by a part number (sequence 4 is blank) and if the 'Product tracking number type code' (in sequence 19) is 'L' and the 'Alternate product tracking number type code’ (sequence 21) is 'B',
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

use 525.BLKNUM520.
If the item is not identified by a part number (sequence 4 is nonblank) and if the 'Product tracking number type code' (in sequence 19) is 'L' and the 'Alternate product tracking number type code’ (sequence
21) is 'B', use 528.BLKNUM520.
19
Mandatory if the ‘product tracking number type code’ (sequence 19) or ‘alternate product tracking number type code’ (sequence 21) is 'D' or 'L'; otherwise, must be blank.
20
Mandatory if the ‘product tracking number type code’ (sequence 19) or ‘alternate product tracking number type code’ (sequence 21) is 'L'; otherwise, must be blank.
21
For subpackets 3B and 3F: If the item (sequence 2 through 4) is identified by a part number and the ‘product tracking number type code’ (sequence 19) or ‘alternate product tracking number type code’
(sequence 21) is 'L', use the Tag that starts with 523; if it is 'D', use the Tag that starts with 529. If the item (sequence 2 through 4) is not identified by a part number and the code or alternate code
(sequence 19 or 21) is 'L', use the Tag that starts with 526; if the code is 'D', use the Tag that starts with 530.
For subpacket 3E: If the item (sequence 2 through 4) is identified by a part number and the ‘product tracking number type code’ (sequence 19) or ‘alternate product tracking number type code’ (sequence
21) is 'L', use the Tag that starts with 524; if the item is not identified by a part number and the code or alternate code (sequence 19 or 21) is 'L', use the Tag that starts with 527.

47
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
24 Assembly status code M 242.STATCD242 or DIP3.2.1.l and Appendix C, DED
243.STATCD243 or 0174
244.STATCD244 or
245.STATCD24522

25 Component item product type code M M DIP3.24 DIP3.2.1.m

26 Component item design enterprise identifier M M M 242.CENTID242 or DIP3.2.1.n and Appendix C, DEDs
243.CENTID243 or 0001 (for CAGE code), 0002 (for
244.CENTID244 or organization acronym), or 0170 (for
245.SWSORC170 or company name)
531.ODESEN531 or
532.ODESEN532 or
533.ODESEN533 or
534.ODESEN53423
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

22
If the assembly item (sequence 2 through 4) is identified by a part number and if the ‘component item product type code’ (sequence 25) is 'P', use the Tag that starts with 242; if it is 'M', use the Tag that starts
with 243; if it is 'S', use the Tag that starts with 245. If the assembly item (sequence 2 through 4) is not identified by a part number, the ‘component item product type code’ (sequence 25) must be 'M'; use the
Tag that starts with 244.
23
For subpackets 3C and 3D: If the component item product type code (sequence 25) is 'P', use the Tag that starts with 242; if it is 'S', use the Tag that starts with 245; if it is 'M' and the assembly item
(sequence 2 through 4) is identified by a part number, use the Tag that starts with 243, but if it is not identified by a part number, use the Tag that starts with 244.
For subpacket 3F: If the product tracking number type code (sequence 19) is 'M', use the Tag that starts with 531; if it is 'G', use the Tag that starts with 532; if it is 'L' and the modified item (sequence 2
through 4) is identified by a part number, use the Tag that starts with 533, but if it is not identified by a part number, use the Tag that starts with 534.

48
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
27 Component item part/material/software M M M 242.CPARNO242 or DIP3.2.1.o. For Tags that start with
identifier 243.CMATGI243 or 242, 531, 532, or 533: Appendix
244.CMATGI244 or C, DED 0024. For Tags that start
245.SWIDEN170 or with 243, 244, or 534: the
531.OPARNO531 or transmitted field must be 120
532.OPARNO532 or characters, left justified and
533.OPARNO533 or consisting of either a material
534.OMATGI53423 specification identifier (Appendix
C, DED 0192) or a material name
(Appendix C, DED 0191). For
245.SWIDEN170: the transmitted
field must be 248 characters, left
justified and consisting of either a
software alphanumeric identifier
(Appendix C, DED 0088), a part
number (Appendix C, DED 0024),
or a software product identifier
(Appendix C, DED 0262).

28 Component item material identification O O O 243.CMATID243 or DIP3.2.1.p and Appendix C, DED

parameter list 244.CMATID244 or 0038
534.OMATID534124

29 Component item manufacturer identifier M M M 242.CMFRCG242 or DIP3.2.1.q and Appendix C, DED

243.CMFRCG243 or 0001
244.CMFRCG244 or
524.CMFRCG524 or
527.CMFRCG52725

30 Component item tracking type code and O O M 242.CTRKID242 or DIP3.2.1.r and Appendix C, DED
tracking identifier 243.CTRKID243 or 0175
244.CTRKID244 or
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

524.CLOTNO524 or
527.CLOTNO52725

24
For subpackets 3C and 3D, if the component item product type code (sequence 25) is 'M' and the assembly item (sequence 2 through 4) is identified by a part number, use the Tag that starts with 243, but if it
is not identified by a part number, use the Tag that starts with 244. In all other cases it must be blank.
For subpacket 3F, if the modified item (sequence 2 through 4) is not identified by a part number, this entry is mandatory; use the Tag that starts with 534. In all other cases it must be blank.
25
For subpackets 3C and 3D, if the component item product type code (sequence 25) is 'P', use the Tag that starts with 242; if it is 'M' and the assembly item (sequence 2 through 4) is identified by a part
number, use the Tag that starts with 243, but if it is not identified by a part number, use the Tag that starts with 244.
For subpacket 3E, if the regrouped item (sequence 2 through 4) is identified by a part number, use the Tag that starts with 524, but if it is not identfied by a part number, use the Tag that starts with 527.

49
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
31 Component item quantity & unit of measure M M M 242.QUANTY242 and DIP3.2.1.s and Appendix C, DEDs
242.UOMCOD242, or 0019, 0053, and 0054
243.QUANTY243 and
243.UOMCOD243, or
244.QUANTY244 and
244.UOMCOD244, or
524.QUANTY524 and
524.UOMCOD524, or
527.QUANTY527 and
527.UOMCOD52725

32 Defined Part/Material release date O 200.RELDAT200 or Appendix C, DED 0082

210.RELDAT21026

33 Defined Part/Material supply shelf life code O 200.SHLFCD200 or Appendix C, DED 0094
210.SHLFCD21026

34 Defined Part/material service life period and O 200.SRVCCD200 and Appendix C, DEDs 0086 and 0232
unit 200.SRVCQY200, or
210.SRVCCD210 and
210.SRVCQY21026

35 Defined Part/Material electrostatic discharge M 200.STATIC200 or Appendix C, DED 0074

code 210.STATIC20026

36 Defined Part/Material unit weight O27 210.PARWGT210 and Appendix C, DEDs 0054 and 0114
210.WGTCOD210

37 Defined Part/Material supply hazardous O 200.HAZMAT200 or Appendix C, DED 0078

material code 210.HAZMAT21026

38 Defined Part/Material precious metals code O 200.METALS200 or Appendix C, DED 0093

210.METALS21026
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

39 Part model revision O27 231.PMODRV231 Appendix C, DED 0009

28
40-75 Part model file O See Data Information Data Information subpacket 9A
Packet 9A

26
If the part/material identification (sequence 2 through 4) is identified by a part number, use the Tag that starts with 210; if it is not identified by a part number, use the Tag that starts with 200.
27
Must be blank unless the part/material (sequence 2 through 4) is identified by a part number.
28
Must be blank if the value of 'Part model revision' (sequence 39) is blank.

50
MIL-STD-2549
Data Information Packet 3

TABLE DIP3-I. Product/asset configuration

Seq # Field Name Data Information Subpacket Data Element Tag For content and validation
instructions, see
3A 3B 3C 3D 3E 3F 3G 3H
7629 Source of implemented/incorporated O O O O O 362.RFDCAG350 or DIP3.2.1.t and for RFDs, Appendix
deviation/modification instruction 363.RFDCAG350 or C, DEDs 0001; for Modification
364.RFDCAG350 or Instructions, Appendix C, D (for
535.RFDCAG350 or CAGE code), 0002 (for
536.MINSRC46030 organization acronym), or 0170 (for
company name)

7729 Identifier of implemented/incorporated O O O O O 362.RFDNUM350 or DIP3.2.1.t and Appendix C, DED

deviation/modification instruction 363.RFDNUM350 or 0003
364.RFDNUM350 or
535.RFDNUM350 or
536.MINNUM46030

7829 Document type of implemented/incorporated O 362.RFDTYP350 or DIP3.2.1.t, DIP3.2.1.u, and

deviation/modification instruction 363.RFDTYP350 or Appendix C, DED 0004
364.RFDTYP350 or
535.RFDTYP350 or
536.MINTYP46030
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

29
The fields in this series must either be all blank, or all nonblank. This series (sequence 76 through 78) may be repeated as necessary for this part/material.
30
For subpacket 3B: If the value of 'Document type of implemented/incorporated deviation/modification instruction' (sequence 78) is 'RFD', use the Tag that starts with 535. If the value of 'Document type of
implemented/incorporated deviation/modification instruction' (sequence 78) is 'MODINST', use the Tag that starts with 536.
For subpacket 3C: If the value of 'Document type of implemented/incorporated deviation/modification instruction' (sequence 78) is 'RFD', use the Tag that starts with 535.
For subpackets 3D, 3E, and 3F: If the value of 'Document type of implemented/incorporated deviation/modification instruction' (sequence 78) is 'RFD and the value of 'Component item product type code'
(sequence 25) is 'P', use the Tag that starts with 362; if the value of the 'Component item product type code' is 'M', use the Tag that starts with 363; if the value of 'Component item product type code' is 'S',
use the Tag that starts with 364.

51
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 3

e. Enter the identification of the part or material which is being superseded or replaced by sequence 2 through 4, or
for which sequence 2 through 4 has been assigned as a substitute, or enter the company and company-assigned
stock number31 for the item in sequence 2 through 4.

f. Enter the CAGE code of the manufacturer of the item in sequence 2 through 4.

g. Enter the date of manufacture of the item in sequence 2 through 4.

h. Enter the time of assembly, maintenance, retrofit, modification, or regrouping of the item in sequence 2 through 4.
For subpacket 3C, time can be entered as 000000. For subpackets 3D, 3E, and 3F, time can be estimated to the
nearest quarter hour unless more precision is required to identify sequentially performed changes.

i. Enter the code for the method of tracking (for example: by serial number, by lot, etc.) 32 and the associated product
tracking number (for example: serial number, etc.) for the item(s) built and identified in sequence 2 through 4.

j. Enter the CAGE code of the organization performing the modification.

k. Enter the code for the alternate method of tracking (for example: by serial number, by lot, etc.) and the associated
product tracking number (for example: serial number, etc.) for the item(s) built and identified in sequence 2
through 4. See Table DIP3-II for suitable alternate types of tracking identifiers.

TABLE DIP3-II. Suitable alternate types of tracking identifiers

If the primary tracking identifier is: Then suitable alternates include:

Block number lot number

Date code [none]

Government-assigned serial number manufacturer-assigned serial number, lot number, block number

Lot number block number

Manufacturer-assigned serial number Government-assigned serial number, lot number, block number

l. Indicate whether the component is being reported as removed or installed.

m. Identify the type of item reported in sequence 26 through 31. The allowable values are: 'P' (for part-numbered
item), 'M' (for item not identified by a part number), and 'S' (for software, regardless of how identified).

n. For subpackets 3C and 3D, enter the design enterprise identifier of the part/material/subassembly/software which
is installed or removed as a component of the assembly defined in sequence 2 through 4. For subpacket 3F, enter
the design enterprise identifier of the part or material before it was modified into the new part/material identified
in sequence 2 through 4.

o. For subpackets 3C and 3D, enter the identifier of the part/material/subassembly/software which is installed or
removed as a component of the assembly defined in sequence 2 through 4. For subpacket 3F, enter the identifier
of the part or material before it was modified into the new part/material identified in sequence 2 through 4.

31
Company stock numbers are alternate identifiers for items for which the company is not the original design activity. They are frequently referred
to by terms such as `company part numbers', 'company equivalent part numbers', or `internal part numbers'.
32
'Block number' is not acceptable in this field.

52
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 3

p. For subpackets 3C and 3D, enter the material identification parameter list of the material which is installed or
removed as a component of the assembly defined in sequence 2 through 4. For subpacket 3F, enter the material
identification parameter list of the material before it was modified into the new part/material identified in sequence
2 through 4.

q. For subpackets 3C and 3D, enter the CAGE code of the manufacturer of the part/material/subassembly which is
installed or removed as a component of the assembly defined in sequence 2 through 4. For subpacket 3E, enter
the CAGE code of the manufacturer of the part/material before it was regrouped into the new lot identified in
sequence 19.

r. For subpackets 3C and 3D, if the component item is a tracked item (has a serial number, lot number, etc.) enter
the tracking method (tracking type code) and the tracking identifier of the part/material/subassembly which is
installed or removed as a component of the assembly defined in sequence 2 through 4. For subpacket 3E, enter
the tracking method (tracking type code) and the tracking identifier of the part/material before it was regrouped
into the new lot identified in sequence 19.

s. For subpackets 3C and 3D, enter the quantity and unit of measure of the part/material/subassembly which is
installed or removed as a component of the assembly defined in sequence 2 through 4. For subpacket 3E, enter
the quantity and unit of measure of the component part/material which was regrouped into the new lot identified in
sequence 19.

t. For subpacket 3D, enter the identification of the RFD(s) that has been incorporated into this item. For subpackets
3B, 3C, 3E, and 3F, enter the identification of the RFD(s) and modification instructions (for example: MWOs,
TCTOs, etc.) that have been incorporated into this item.

u. The value of 'Document type of implemented/incorporated deviation/modification instruction' is either 'RFD' or

'MODINST'.

DIP3.2.2 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CSA database, but have the constant value indicated. Because they have constant values, they do not have to
be transmitted as part of the information subpacket.

DIP3.2.2.1 Subpacket 3A. For the defining document (sequence 9) the document source identifier (053.DESCAG053,
104.DESCAG104, 106.DESCAG106, 201.DESORG421, 211.DESORG420, 434.DESCAG434, 436.DESCAG436,
919.DESCOM919, 923.DESCOM923, or 924.DESCOM921) is the same as the part/material design enterprise
(sequence 2).

DIP3.2.2.2 Subpacket 3B. The product-tracking base-identifier (sequence 8) is also used in 515.BASNUM500.

DIP3.2.2.3 Subpacket 3C.

a. The Part/material design enterprise identifier (sequence 2) also identifies the assembly design source
(242.AENTID242, 243.AENTID243, 244.AENTID244, or 245.DESENT210).

b. The Part/material identifier (sequence 3) also identifies the assembly (242.APARNO242, 243.APARNO243,
244.AMATGI244, or 245.PARNUM210).

c. The Material identification parameter list (sequence 4) also identifies the assembled material identification
parameter list (244.AMATID244).

53
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 3

d. The product-tracking base-identifier (sequence 8) is also used in 515.BASNUM500 and either

240.BASNUM500 (if this item is identified by a part number) or 241.BASNUM500 (if this item is not identified
by a part number).

e. The assembly status code 242, 243, 244 or 245 (sequence ) follows the same rules as subpacket 3D sequence 24,
but always has a value of 'I'.

f. If the value of 'Source of implemented/incorporated deviation/modification instruction' (sequence 76) is nonblank,

the value of 'Document type of implemented/incorporated deviation/modification instruction' (sequence 78) is
'RFD'.

DIP3.2.2.4 Subpacket 3D.

a. The Part/material design enterprise identifier (sequence 2) also identifies the assembly design source
(242.AENTID242, 243.AENTID243, 244.AENTID244, or 245.DESENT210).

b. The Part/material identifier (sequence 3) also identifies the assembly (242.APARNO242, 243.APARNO243,
244.AMATGI244, or 245.PARNUM210).

c. The product-tracking base-identifier (sequence 8) is also used in 515.BASNUM500 and either

240.BASNUM500 (if this item is identified by a part number) or 241.BASNUM500 (if this item is not identified
by a part number).

d. If the value of 'Source of implemented/incorporated deviation/modification instruction' (sequence 76) is nonblank,

the value of 'Document type of implemented/incorporated deviation/modification instruction' (sequence 78) is
'MODINST'.

DIP3.2.2.5 Subpacket 3E.

a. The product-tracking base-identifier (sequence 8) is also used in 515.BASNUM500.

b. If the value of 'Source of implemented/incorporated deviation/modification instruction' (sequence 76) is nonblank,

the value of 'Document type of implemented/incorporated deviation/modification instruction' (sequence 78) is
'MODINST'.

DIP3.2.2.6 Subpacket 3F.

a. The product-tracking base-identifier (sequence 8) is also used in 515.BASNUM500.

b. If the value of 'Source of implemented/incorporated deviation/modification instruction' (sequence 76) is nonblank,

the value of 'Document type of implemented/incorporated deviation/modification instruction' (sequence 78) is
'MODINST'.

DIP3.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

54
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

Configuration Change Control

DIP4.1. Purpose. Includes information concerning requests for change/modification of engineering designs and/or
fielded equipment/software.

DIP4.1.1 Subpackets. There are 10 subpackets for this packet. ECPs have been separated into multiple subpackets
to assist in limiting Government oversight of contractors.

Subpacket Applicability
4A Class II ECPs which includes document "from/to" information
4B Class II ECPs which do not include document "from/to" information
4C Message Class I ECPs
4D Preliminary Class I ECPs
4E Final Class I ECPs which address logistics impact information
4F Final Class I ECPs which do not address logistics impact information
4G RFD
4H Modification Request
4I Modification Instruction
4J Notice of revision (This subpacket is not a stand-alone subpacket; can be used only in conjunction with
subpacket 4A through 4F.)

(For definitions of Class I and Class II, see Appendix C, DED 0164; for definitions of message, preliminary, and final
ECPs, see Appendix C, DED 0194.)

DIP4.1.2. Selection of data information subpackets.

a. Subpacket 4A should be used for Class II (minor) ECPs when either (1) the Government is the CDCA of the
document(s) being changed, (2) the Government tasking organization is responsible for determining the logistics
impact of proposed changes (build-to-print or off-the-shelf buys), or (3) the organization that prepares the
engineering change is not the CDCA.

b. Subpacket 4B should be used for Class II (minor) ECPs when the nongovernment organization preparing the ECP
is the CDCA for the document(s) being changed and is either responsible for identifying the logistics impact of the
proposed change or for providing logistics support for the item.

c. Subpacket 4E should be used for Class I (major) ECPs when either (1) the Government has tasked the
nongovernment performing activity to identify logistics impacts of proposed changes, or (2) the Government has
prepared the ECP and is responsible for determining the impact of the ECP on logistics support that will be
performed by the Government.

d. Subpacket 4F should be used for Class I (major) ECPs when either (1) the nongovernment organization (either as
performing or tasking activity) is responsible for the logistics support of the finished item, or (2) the Government
tasking activity is responsible for the logistics support of the finished item and the nongovernment performing
activity is preparing the ECP. If the responsibility for performing logistics support for the delivered item is shared
between a Government tasking activity and a nongovernment performing activity, use subpacket 4E.

55
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
Identification and administrative information:
1 Document source M M 010.ENTTYP010 Appendix C, DED 0100
identification type code
2 ECP/NOR/RFD CAGE M M M M M M M M M M 010.SRCIDN010 Table B-I and Appendix C, DED 0001
code/modification request/ (for CAGE codes), DED 0002 (for
instruction source1 organization acronyms), or DED 0170
(for company names).
3 Document identification type M M 010.IDNTYP010 Appendix C, DED 0101
code

4 ECP/NOR/RFD/ M M M M M M M M M M 010.DOCIDN010 Table B-I and appendix C, DED 0003

modification request/ (for alphanumeric identifiers) or DED
modification instruction 0008 (for documents identified by title).
identifier2

5 ECP/NOR/RFD/ M M M M M M M M M M 011.DOCREV011 DIP4.2.1.a and Appendix C, DED 0009

modification request/ (for revisions identified by alphanumeric
modification instruction characters) or DED 0082 (for revisions
revision identified by a date)

6 ECP/NOR/RFD/ M M M M M M M M3 M3 M 011.DOCTIT011 Appendix C, DED 0008

modification request/
modification instruction title

7-24 Basic document protection M M M M M M M M M M See Data Information Data Information Packet 8
subpacket Subpacket 8A

25 DOD indicator code M 460.DODCOD460 Appendix C, DED 0143

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

1
This is the identity of the organization whose identifier is assigned as the unique identifier of the ECP/RFD/modification request/modification instruction/NOR. For ECPs, RFDs, and NORs, it must be a
valid CAGE code or NSCM. For modification requests and modification instructions, the type of organization identifier is dependent on the value of the 'document source identification type code' (sequence
1).
2
This identifier, together with the source in sequence 2, shall uniquely identify the ECP/RFD/modification request/modification instruction/NOR. The type of document identifier is dependent on the value of
the document identification type code (sequence 3).
3
Mandatory if the value of the 'document identification type code' (sequence 3) is 'N'.

56
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
4
26 Modification request/ O O 450.MODSUB450 or Appendix C, DEDs 0141 (for subpacket
instruction type code 462.MINSUB4625 4I) or DED 0142 (for subpacket 4G)

27 RFD Class code M 351.RFD006351 Appendix C, DED 0125

28 Priority M6 M M M O7 289.ECP070289 or DIP4.2.1.b (for subpacket 4C only) and

465.CATCOD465 or Appendix C, DEDs 0166 (for subpackets
466.PRICOD466 or 4C through 4F) or DEDs 0246, 0247, and
467.PRICOD4678 0248 (for subpacket 4I)

29 Justification Code M M M M 289.ECP060289 Appendix C, DED 0165. If more than

one of these codes are applicable, the one
which is the most descriptive or
significant is assigned to the ECP.

30 CDCA M M M M M M M M M M 010.CCCENT010 DIP4.2.1.c and Appendix C, DED 0239

31 CDCA effective date O9 O9 O9 O9 O9 O9 O9 O9 O9 O9 010.CCCADT010 Appendix C, DED 0082

32 Current Status M M M M M M M M M M 294.REVSTA850 or DIP4.2.1.d, Appendix B, Figures B-1

373.REVSTA850 or through B-7, and Appendix C, DED 0021
308.REVSTA850 or (document-revision-approval-process-
850.REVSTA85010 disposition-status-code)

4
Mandatory if the value of the DoD indicator code (sequence 25) is 'D'.
5
For subpacket 4H: Use the Tag that starts with 450
For subpacket 4I: Use the Tag that starts with 462.
6
Priority must have a value of "U" or "E", unless the value of justification code (sequence 29) is 'C', in which case, "R" is also acceptable.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

7
Mandatory if the value of 'Modification instruction type code' (sequence 26) is 'TECHDIR', 'MWO', or 'TCTO'.
8
For subpackets 4C through 4F: Use the Tag that starts with 289.
For subpacket 4I: If the value of 'Modification instruction type code' (sequence 26) is 'TECHDIR', use the Tag that starts with 465; if it is 'TCTO', use the Tag that starts with 466; if it is 'MWO', use the Tag
that starts with 467.
9
Mandatory on first submittal (revision '-'); optional on all subsequent revisions.
10
For subpackets 4A through 4F: Use the Tag that starts with 294
For subpacket 4G: Use the Tag that starts with 373
For subpackets 4H and 4I: Use the Tag that starts with 850
For subpacket 4J: Use the Tag that starts with 308.

57
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
33 Status Date M M M M M M M M M M 294.STADAT850 or DIP4.2.1.e and Appendix C, DED 0082
373.STADAT850 or
308.STADAT850 or
850.STADAT85010

34 Originator O9 O9 O9 O9 O9 O9 O9 O9 O9 O9 010.ORIGIN010 The transmitted field must be 36

characters, left justified and consisting of
either a CAGE code (Appendix C, DED
0001), a company name (Appendix C,
DED 0170), an organization acronym
(Appendix C, DED 0002), or an author's
name (Appendix C, DED 0069)

3511 Application Activity O O O 861.APPACT033 DIP4.2.1.f. The transmitted field must be

30 characters, left justified and consisting
of either a CAGE code (Appendix C,
DED 0001), a company name (Appendix
C, DED 0170), or an organization
acronym (Appendix C, DED 0002)

3611 AA Status12 O O O 861.AREVST861 Appendix B, Figures B-4 through B-7,

and Appendix C, DED 0021 (document-
revision-application-activity-approval-
process-disposition-status-code)
3711 AA Status date13 O O O 861.AREVDT861 Appendix C, DED 0082

38 In production? M M M M M 251.ECP170251 Appendix C, DED 0223

39 PAN year14 O O O O O O 671.YEARNO670 or Appendix C, DED 0219

672.YEARNO67015
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

11
'Application activity', 'AA status' and 'AA status date' may be repeated as a series as many times as necessary.
12
This field must be blank if 'Application Activity' is blank.
13
This field must be blank if AA status is blank.
14
'PAN year' (sequence 39) and 'PAN number' (sequence 40) are paired fields; either both must be blank, or both must be nonblank. They are always blank for initial release (revision '-'). These fields only
apply to information subpackets generated by, or submitted to, Army activities.
15
For subpackets 4A through 4F: Use the Tag that starts with 671.
For subpacket 4G: Use the Tag that starts with 672.

58
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
14
40 PAN number O O O O O O 671.PANNUM670 or Appendix C, DED 0178
672.PANUNM67015

41 Baseline affected M16 M16 M16 M16 M16 M16 M 254.BLTYPE254 or Appendix C, DED 0098
351.BLYTPE35117

42 Primary/related18 ECP/ M20 M20 O20 M20 M20 M 250.PECPFG250 or Appendix C, DED 0187
sequentially implemented19 351.RFD01835121
ECP/recurring deviation
indicator flag

43 Primary/dependent ECP or O23 O23 O23 O23 O23 O23 O 253.PECPCG253 or DIP4.2.1.g and Appendix C, DED 0001
prior deviation CAGE22 359.PRFDCG359 or
493.ECPCAG35024

16
Repeat this field if more than one type of baseline is affected.
17
For subpackets 4A through 4F: Use 254.BLTYPE254
For subpacket 4G: Use 351.BLTYPE351.
18
When an engineering proposal affects documents controlled by more than one CDCA, or when more than one performing activity is involved in accomplishing the change, related ECPs must be prepared. A
separate ECP must abe prepared for each package of documents controlled by a single CDCA which are to be changed to accomplish this proposed change. One of these ECPs is designated as the "Primary"
ECP and the others are designated as "Related" ECPs.
19
When previously approved engineering changes must be implemented in a specific sequence in relation to this proposed change, such order shall be specified.
20
For subpacket 4A through 4F, if this is a primary or related ECP, enter either 'P' or 'R', respectively. If this is an ECP which is dependent on the implementation of another ECP and therefore must be
implemented in a particular sequence, enter 'S'. If this ECP is independent and neither of these cases apply, enter 'N'.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

21
For subpackets 4A through 4F: Use the Tag that starts with 250.
For subpacket 4G: Use the Tag that starts with 350.
22
'Primary/dependent ECP or recurring deviation CAGE' and 'Primary/dependent ECP or recurring deviation identifier' (sequence 43 and 44) are paired fields, either both must be blank, or both must be
nonblank.
23
For subpackets 4A through 4F: This field is mandatory if the value of 'Primary ECP/recurring deviation indicator flag' (sequence 42) is 'R' or 'S'; otherwise, must be blank.
For subpacket 4G: This field is mandatory if the value of 'Primary ECP/recurring deviation indicator flag' is 'Y'; otherwise must be blank.
24
For subpackets 4A through 4F: Use the Tag that starts with 253.
For subpacket 4G: Use the Tag that starts with 359.
For subpacket 4I: Use the Tag that starts with 493.

59
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
25
44 Primary/dependent ECP or O O O O O O O 253.PECPNO253 or DIP4.2.1.g and Appendix C, DED 0003
prior deviation identifier22 359.PRFDNO359 or
493.ECPNUM35024
45 ECP revision O25 493.ECPREV351 DIP4.2.1.g and Appendix C, DED 0009
26
46 CAGE code of most recent O O O O 359.CRFDCG359 Appendix C, DEDs 0001
recurring deviation resolved
by ECP in sequence 2 and 4
4726 Identifier of most recent O O O O 359.CRFDNO359 Appendix C, DEDs 0003
recurring deviation resolved
by ECP in sequence 2 and 4
4826 Revision of most recent O O O O 359.RFDREV350 Appendix C, DED 0009
recurring deviation resolved
by ECP in sequence 2 and 4

49 Order of implementation O27 O27 O27 O27 O27 250.ECPSEQ250 Appendix C, DED 0119

50 Summary of description of M M M M M M M O 251.ECP190251 or DIP4.2.1.h and Appendix C, DED 0126

change 351.RFD022351 or (for subpacket 4G), DED 0171 (for
460.MODDES46028 subpackets 4A through 4F), or DED 0253
(for subpacket 4I)

51 Link to description of change O O O O O O O 251.SGM190251 or DIP4.2.1.i and Appendix C, DED 0118

351.SGM02223128

52 Summary of need for change M M M M M M M 251.ECP200251 or DIP4.2.1.j and Appendix C, DED 0127
351.RFD02335128 (for subpacket 4G) or DED 0171 (for
subpackets 4A through 4F)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

25
Mandatory if the value of 'ECP CAGE' (sequence 43) is nonblank; otherwise, must be blank.
26
Sequence 46 through 48 is the identification of the recurring deviation(s) resolved by this ECP subpacket. These fields must either all be nonblank, or all be blank. Repeat this series of fields as necessary
for each different recurring problem that is resolved by this ECP.
27
Mandatory if the value of 'Primary ECP/recurring deviation indicator flag' (sequence 42) is 'S'; otherwise, must be blank.
28
For subpackets 4A through 4F: Use the Tag that starts with 251
For subpacket 4H: Use the Tag that starts with 351
For subpacket 4I: Use the Tag stating with 460.

60
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
53 Link to need for change O O O O O O O 251.SGM200251 or DIP4.2.1.k and Appendix C, DED 0118
351.SGM02335128

54 Link to rationale for O29 359.SGMRAT359 DIP4.2.1.l and Appendix C, DED 0118
recurring deviation

55 Summary of corrective M 351.RFD024351 Appendix C, DED 0130

action
56 Link to corrective action M 351.SGM024351 Appendix C, DED 0118

57 Retrofit required? M M M M 289.ECP001289 Appendix C, DED 0240

58 Link to recommendation for O O30 O30 289.SGM430289 DIP4.2.1.m and Appendix C, DED 0118
retrofit/kit delivery

59 Ship class affected31 O O O 260.RETSHP260 DIP4.2.1.n and Appendix C, DED 0031

60 Vehicle class affected31 O O O 260.RETVEH260 DIP4.2.1.n and Appendix C, DED 0031

32 31
61 Locations affected O O O 260.RETLOC260 DIP4.2.1.n and Appendix C, DED 0029
32
62 Quantity at location (and O O O 260.QUANTY260 and DIP4.2.1.n Appendix C, DED 0019 and
unit of measure)33 260.LOCUOM260 0054
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

29
Mandatory if the value of 'Recurring deviation indicator flag' (sequence 42) is 'Y'; otherwise, must be blank.
30
Mandatory if the value of 'Retrofit required?' (sequence 57) is 'Y'; must be blank if the value of sequence 57 is 'N'.
31
Must be blank if the value of 289.ECP001289 is "N"
32
Repeat the series of fields 'Location affected' and 'Quantity at location affected' as necessary.
33
Mandatory if the value of 'Location affected' is nonblank; otherwise, must be blank.

61
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
Supplemental documents and effectivity of change on affected documents/parts/materials/software:
6334,35,36 Supplemental/affected O37 O37 O37 O37 O37 O37 O37 DIP4.63
document flag

6434,35,36 Supplemental/affected O O O O O O O M38 253.DOCTYP010 or Appendix C, DED 0004

document type code 266.DOCTYP010 or
352.DOCTYP010 or
357.DOCTYP01039

34
The series of fields 'Supplemental/affected document flag', 'Supplemental/affected document type', 'Supplemental/affected document source', 'Supplemental/affected document identifier', and (sequence 63
through 66) must all be blank, or all be nonblank.
35
For subpackets 4A, 4B, and 4D through 4G: Repeat the series of fields sequence 63 through 67 for each supplemental or supporting document referenced in the 'Description of Change' (sequence 50 or the
text linked to by the contents of sequence 51) or 'Need for Change' (sequence 52 or the contents of the text linked to by the contents of sequence 53) or other justification paragraphs.
36
For subpackets 4A, 4C, 4D, and 4E: If this ECP is being prepared by the nongovernment CDCA of the document(s) being changed by the ECP and the Government is responsible for performing logistics
support but has tasked the preparing activity to identify the logistics impact of proposed changes,repeat the series of fields sequence 69 through 79 for each part, material, or software which will be
affected by the ECP upon apporval. For all other cases, repeat the series of fields sequence 63 through 79 for each document which will be changed by the ECP upon approval.
For subpackets 4B, 4C, 4D, and 4F: If this ECP is being prepared by the nongovernment CDCA of the document(s) being changed by the ECP and the preparing activity is responsible for providing all
logistics support of the item to the Government, repeat the series of fields sequence 69 through 79 for each part, material, or software which will be affected by the ECP upon apporval. For all other
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

cases, repeat the series of fields sequence 63 through 79 for each document which will be changed by the ECP upon approval.
For subpacket 4G: Repeat the series of fields sequence 63 through 79 for each document which contains a requirement for which this deviation is being requested. At least one series is required in each
subpacket.
37
For subpackets 4A, 4B, and 4D through 4G: For analysis, reports, etc., which are attached to the ECP/RFD to supplement the description of change, the need for change, or other justification paragraphs,
enter an 'S' here.
For subpackets 4A through 4F: For documents which are affected by (will be changed by approval of) the ECP, enter an 'A' here.
For subpacket 4G: For documents which contain the requirement for which the deviation is being requested, enter an 'A' here.
38
The series of fields sequence 64 through 67, apply to the document being changed by the NOR and shall not be repeated.
39
For subpackets 4A through 4F: If the value of 'Supplemental/affected document flag' (sequence 50) is 'A', use the Tag that starts with 266; if it is 'S', use the Tag that starts with 253.
For subpacket 4G: If the value of 'Supplemental/affected document flag' is 'A', use the Tag that starts with 352; if it is 'S', use the Tag that starts with 357.

62
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
34,35,36 40
65 Supplemental/affected O O O O O O O O M38 253.SRCIDN010 or Figure B-I. The transmitted field must be
document source 266.SRCIDN010 or 36 characters, left justified and consisting
352.SRCIDN010 or of either a CAGE code (Appendix C,
357.SRCIDN010 or DED 0001), an organization acronym42
461.SRCIDN010 or (Appendix C, DED 0002), or a company
464.SRCDOD462 or name (Appendix C, DED 0170), or for
468.SRCDOD46839,41 supplemental documents only, an author's
name (Appendix C, DED 0069)
6634,35,36 Supplemental/affected O O O O O O O O40 M38 253.DOCIDN010 or Figure B-I. The transmitted field must be
document identifier 266.DOCIDN010 or 240 characters, left justified and
352.DOCIDN010 or consisting of either an alphanumeric
357.DOCIDN010 or identifier (Appendix C, DED 0003) or a
461.DOCIDN010 or title (Appendix C, DED 0008)
464.DOCNUM020 or
468.ATMNUM55739,41

6735,36 Affected document current O43 O43 O O43 O43 O43 O43 M38 266.DOCCRV266 or The transmitted field must be 8 characters,
revision level 352.DOCREV01139 left justified, and consisting of either an
alphanumeric revision identifier
(Appendix C, DED 0009 or 0193) or a
date (Appendix C, DED 0082
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

40
Repeat the series of fields sequence 65 and 66 for each technical manual associated with the modification instruction.
41
If the value of 'Modiication instruction type code' (sequence 26) is 'MWO', use 468.SRCDOD468; if the value of sequence 26 is 'RAC', use 464.SRCDOD462; for all other values of sequence 26, use
461.SRCIDN010.
42
For U.S. defense specifications, use 'DOD'.
43
Mandatory if the value of 'Supplemental/affected document flag' (sequence 63) is 'A'; otherwise must be blank.

63
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
36 44 44 44 44 44
68 Specific affect on document O O O O O M M38 266.SGM330266 or DIP4.2.1.o and Appendix C, DED 0118
352.SGM22A352 or
301.SGMCHG30145

6936,46 Affected part/material/ O O O O O O M O 258.DESCAG258 or For 258.DESCAG258, see Appendix C,

software design source47 353.SWSORC170 or DED 0001. For 353.SWSORC170:
360.DESENT210 or transmitted field must be 36 characters
365.DESENT200 or left justified and consisting of either a
491.DESENT210 or CAGE code, an organization acronym, a
494.DESENT20048 company name, or an author's name
(Appendix C, DEDs 0001, 0002, 0170,
and 0069, respectively). For
xxx.DESENT2x0: transmitted field must
be 30 characters left justified and
consisting of either a CAGE code, an
organization acronym,or a company name
(Appendix C, DEDs 0001, 0002, and
0170, respectively).

44
For subpackets 4A, 4B, and 4D through 4F: This field and sequence 300 are mutually exclusive; for each affected document in sequence 63 through 68 for which the 'NOR' (sequence 300) is nonblank, this
field must be blank.
For subpackets 4A, 4D and 4E: If this ECP is being prepared by the nongovernment CDCA of the document(s) being changed by the ECP and the Government is responsible for performing logistics support
but has tasked the preparing activity to identify the logistics impact of proposed changes, both sequence 68 and 300 should be blank.
For subpackets 4B, 4D and 4F: If this ECP is being prepared by the nongovernment CDCA of the document(s) being changed by the ECP and the preparing activity is responsible for providing all logistics
support of the item to the Government,both sequence 68 and 300 should be blank.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

45
For subpackets 4A, 4B, and 4D through 4F: Use the Tag that starts with 266.
For subpacket 4G: Use the Tag that starts with 352.
For subpacket 4J: Use the Tag that starts with 301.
46
Repeat the series of fields sequence 69 through 79 as many times as necessary to address each affected assembly/part, software, or material, provide the complete identification of the affected item. Do not
include parts/assemblies being addressed in related ECPs here.
47
'Affected part/material/software design source' and 'Affected part/material/software identifier' are paired fields; either both must be blank, or both must be nonblank.
48
For subpackets 4A through 4F: Use the Tag that starts with 258
For subpacket 4F: Use the Tag that starts with 353, 360, and 365 for software, materials, and parts, respectively.
For subpacket 4I: Use the Tag that starts with 491 and 494 for parts and materials respectively.

64
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
36,46
70 Affected part/material/ O O O O O O M O 258.PARNUM210 or For xxx.PARNUM210: Appendix C,
software identifier46 353.SWIDEN170 or DED 0024. For 353.SWIDEN170: the
360.PARNUM210 or transmitted field must be 248 characters,
365.MATGID200 or left justified and consisting of either a
491.PARNUM210 or software alphanumeric identifier
494.MATGID20048 (Appendix C, DED 0088), a part number
(Appendix C, DED 0024), or a software
identifier (Appendix C, DED 0262. For
xxx.MATGID200: the transmitted field
must be 120 charachters, left justified and
consisting of either a material name
(Appendix C, DED 0191) or a material
document identifier (Appendix C, DED
0192).

7136,46 Affected material identifying O O 365.MATIDN200 or Appendix C, DED 0038

parameters 494.MATIDN20048

7236,46 Part name49 O O O O O O O 210.PARNAM209 Appendix C, DED 0113

36,46 50
73 Lowest level? O O O O O O O 258.PARLVL258 or Appendix C, DED 0121
360.PARLVL360 or
365.PARLVL36548
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

49
Must be blank if 'Affected part/material/software design source', (sequence 69) is blank; must blank if 'Affected material identifying parameters' (sequence 60) is nonblank.
50
Mandatory if 'Affected part/material/software design source' (sequence 69) is nonblank.

65
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
36,46,51 52
74 Product tracking-base O O O O O O M M 259.BASNUM500 or DIP4.2.1.p, DIP4.2.1.q, Table B-II, and
361.BASNUM500 or Appendix C, DED 0056
366.BASNUM500 or
491.BASNUM500 or
494.BASNUM50053

7536,46,51 Manufacturer's CAGE code52 O O O O O O M M 259.MFRCAG515 or DIP4.2.1.q, Appendix C, DED 0001

361.MFRCAG515 or
364.MFRCAG515 or
491.MFRCAG515 or
494.MFRCAG51553

7636,46,51 Type of tracking identifier52 O O O O O O M M 259.TRKTYP515 or DIP4.2.1.q, Appendix C, DED 0057

361.TRKTYP515 or
364.TRKTYP515 or
491.TRKTYP515 or
494.TRKTYP51553

7736,51 Starting effectivity52 O O O O O O M M 259.STREFF259 or DIP4.2.1.q, Appendix C, DED 0058

361.STREFF361 or
364.STREFF364 or
491.STREFF491 or
494.STREFF49453

7836,46,51 Ending effectivity O54 O54 O54 O54 O54 O54 O M 259.ENDEFF259 or DIP4.2.1.q, Appendix C, DED 0058
361.ENDEFF361 or
364.ENDEFF364 or
491.ENDEFF491 or
494.ENDEFF49453
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

51
The fields 'Product tracking-base', 'Manufacturer's CAGE code', 'Type of tracking identifier', 'Starting effectivity', 'Ending effectivity', and 'Forward/retro fit?' may be repeated as necessary in order to define
each effectivity block for each part/material in sequence 63 through 71.
52
The fields 'Product tracking-base', 'Manufacturer's CAGE code', 'Type of tracking identifier', 'Starting effectivity', and 'Forward/retro fit?' must be either all blank, or all nonblank. For subpackets 4C, 4E,
4F, and 4G, there must be at least one nonblank series.
53
For subpackets 4A through 4F: Use the Tag that starts with 259.
For subpacket 4G: Use the Tag that starts with 361 for documents and the Tag that starts with 366 for software departures.
For subpacket 4I: Use the Tag that starts with 491 for parts and 494 for materials.
54
Must be blank if 'Starting effectivity' is blank.

66
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
36,46,51 55
79 Forward/Retro fit? O O O O 259.EFFTIM259 DIP4.2.1.q, Appendix C, DED 0028

Retrofit information:
80 Modification kit identifier56 O 492.KITIDN490 Appendix C, DED 0245

81 Modification instruction M 460.ISSDAT460 Appendix C, DED 0082

issue date
82 Modification instruction M 460.EFFDAT460 Appendix C, DED 0082
effective date
83 Modification instruction M 460.CNXDAT460 Appendix C, DED 0082
cancellation date

84 RAC type/Technical O57 464.CHGTYP464 or Appendix C, DED 0256 or DED 0249

directive task type 465.TSKTYP465

85 Contractor field service O O O 290.ECP470290 Appendix C, DED 0180

required?56

86 Link to description of O O O 290.SGM470290 Appendix C, DED 0118

contractor field service
requirements58
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

55
Must be "F" if the value of 'Retrofit required' is "N"
56
If the value of 'Retrofit required' (sequence 57) is 'N', this field must be blank.
57
Mandatory if the value of 'Modification instruction type code' (sequence 26) is 'RAC' or 'TECHDIR'; must be blank for all other values of sequence 26. If the value of sequence 26 is 'RAC', use
464.CHGTYP464; if the value of sequence 26 is 'TECHDIR', use 465.TSKTYP465.
58
Mandatory if the value of 'Contractor field service required?' (sequence 85) is 'Y'; otherwise, must be blank.

67
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
59 56 60
87 Level of maintenance O O O O 263.RETLVL263 or DIP4.2.1.r and Appendix C, DEDs 0195,
465.LVLCOD465 or 0250, 0254 , or 0255
466.LVLCOD466 or
467.LVLCOD46761

8859 Man-hrs/unit for R&R56 O O62 O62 263.MTNTIM263 DIP4.2.1.r and Appendix C, DED 0087
59 62 62
89 Man-hrs/unit to install O O O 263.KITTIM263 DIP4.2.1.rand Appendix C, DED 0087
retrofit kit56
9059 Man-hrs/unit to test kit O O O 263.KITTST263 DIP4.2.1.r and Appendix C, DED 0087
installation56
9159 Man-hrs/unit for final system O O O 263.ECP450263 DIP4.2.1.r and Appendix C, DED 0087
test56
9259 Hrs out of service time56,63 O O O O 263.ECP480263 or Appendix C, DED 0087
460.WKHOUR46064

9359 Quantity of kits required56 O O O 263.KITQTY263 Appendix C, DED 0019

59
For subpackets 4D through 4F: Repeat the series of fields 'Level of maintenance' (sequence 87) through 'Quantity of kits required' (sequence 93) for each level of maintenance affected.
60
Mandatory if the value of 'Modification instruction type code' (sequence 26) is 'TECHDIR', 'TCTO', or 'MWO'.
61
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

For subpackets 4D through 4F: Use 263.RETLVL263.

For subpacket 4I: (a) If the value of 'Modification instruction type code' (sequence 26) is 'TECHDIR', use 465.LVLCOD465.
(b) If the value of 'Modification instruction type code' (sequence 26) is 'TCTO', use 466.LVLCOD466.
(c) If the value of 'Modification instruction type code' (sequence 26) is 'MWO', use 467.LVLCOD467.
62
If the value of 'Retrofit required' (sequence 51) is 'Y', the value of the 'Man-hrs/unit for R&R' (sequence 78) and the value of the 'Man-hrs/unit to install retrofit kit' (sequence 79) cannot both be blank.
63
For subpackets 4D through 4F: Estimate the total time period from removal of a single unit of the equipment from operational service until that unit of equipment will be returned to operational status after
being retrofitted.
For subpacket 4I: Specify the number of man hours per unit required to accomplish the modification instruction.
64
For subpackets 4D through 4F: Use 263.ECP480263.
For subpacket 4I: Use 460.WKHOUR460.

68
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
Contract information:
9465 Contract identifier M M M M M M M 255.CONIDN950 or Appendix C, DED 0015
355.CONIDN95066

9565 Current contract M M M M M M M 255.CONMOD951 or Appendix C, DED 0120

modification 355.CONMOD95165
9665,67 Contract line item impacted O O M M M 255.CLINID959 or Appendix C, DED 0017
by change 355.CLINID95965

Impact description:
97 Effect on delivery schedule O M M M 251.ECP220251 or DIP4.2.1.s and Appendix C, DED 0171
351.RFD020351

98 Link to developmental O O 289.ECP342289 DIP4.2.1.t and Appendix C, DED 0118

program requirements

99 Link to trade-offs & O O 289.ECP241289 Appendix C, DED 0118

alternate solutions

100 Link to effect on acquisition O O O 289.SGM38A289 or Appendix C, DED 0118

logistics support and 351.SGM02135168
acquisition logistics support
plans

101 Link to effect on O O 289.SGM38B289 Appendix C, DED 0118

maintenance concept, plans
& procedures
102 Link to effect on interim O O 289.SGM38D289 Appendix C, DED 0118
support plan
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

65
Repeat the series of fields 'Contract identifier' through 'Contract line item impacted by change' for each contract under which this ECP/RFD is being submitted.
66
For subpackets 4A through 4F: Use the Tag that starts with 255
For subpacket 4G: Use the Tag that starts with 355.
67
Repeat this field for each contract line item (in the contract identified in sequence 94 and 95) which identifies a product which will be affected by this ECP/RFD.
68
For subpackets 4D and 4E: Use the Tag that starts with 289
For subpacket 4G: Use the Tag that starts with 351.

69
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
103 Link to effect on spares & O O 289.SGM38E289 Appendix C, DED 0118
repair parts
104 Link to effect on tech O O 289.SGM38F289 Appendix C, DED 0118
manuals
105 Link to effect on facilities O O 289.SGM38G289 Appendix C, DED 0118

106 Link to effect on support O O 289.SGM38H289 Appendix C, DED 0118

equipment (including test
procedures and software)
107 Link to effect on personnel O O 289.SGM38J289 Appendix C, DED 0118
108 Link to effect on operator O O 289.SGM38I289 Appendix C, DED 0118
training

109 Link to effect on O O 289.SGM38K289 Appendix C, DED 0118

maintenance training

110 Link to effect on contract O O 289.SGM38M289 Appendix C, DED 0118

maintenance

111 Link to effect on PHST O O 289.SGM38N289 Appendix C, DED 0118

112 Link to effect on safety O O 289.SGM39A289 Appendix C, DED 0118

113 Link to effect on O O 289.SGM39B289 Appendix C, DED 0118

survivability

114 Link to effect on reliability O O 289.SGM39C289 Appendix C, DED 0118

115 Link to effect on O O 289.SGM39D289 Appendix C, DED 0118

maintainability
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

116 Link to effect on service life O O 289.SGM39E289 Appendix C, DED 0118

117 Link to effect on operating O O 289.SGM39F289 Appendix C, DED 0118

procedures

118 Link to effect on O O 289.SGM39G289 Appendix C, DED 0118

electromagnetic interference

119 Link to effect on activation O O 289.SGM39H289 Appendix C, DED 0118

schedule

70
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
120 Link to effect on critical O O 289.SGM39I289 Appendix C, DED 0118
single-point failure items
121 Link to effect on O O 289.SGM39J289 Appendix C, DED 0118
interoperability
122 Link to effect on operational, O O 289.SGM32E289 Appendix C, DED 0118
maintenance, or training
software
123 Date contractual authority O O 289.ECP50A289 DIP4.2.1.u and Appendix C, DED 0082
needed for production
124 Date contractual authority O O 289.ECP50B289 DIP4.2.1.u and Appendix C, DED 0082
needed for retrofit
125 Link to consequences of M M O M M 251.SGM20A251 DIP4.2.1.v and Appendix C, DED 0118
disapproval

126 Link to effect on O O 289.SGM37A289 Appendix C, DED 0118

performance of the product

127 Link to effect on weight- O O 289.SGM37B289 Appendix C, DED 0118

balance-stability of aircraft

128 Link to effect on weight- O O 289.SGM37C289 Appendix C, DED 0118

moment of other equipment

129 Link to effect on GFE or O O 289.SGM40J289 Appendix C, DED 0118

GFD

130 Link to effect on software O O 289.SGM40D289 Appendix C, DED 0118

other than operational,
maintenance or training
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

131 Link to rework required to O O 289.SGM40E289 Appendix C, DED 0118

other equipment

132 Link to effect on system test O O 289.SGM40F289 Appendix C, DED 0118

procedures

133 Link to effect on warranty O O O 289.SGM40G289 Appendix C, DED 0118

134 Link to changes to parts O O 289.SGM40H289 Appendix C, DED 0118

control program

71
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
135 Link to effect on life-cycle O O 289.SGM40I289 Appendix C, DED 0118
cost
136 Link to effect on O O 289.SGM37E289 Appendix C, DED 0118
configuration nomenclature
13769 Name of other effect O O 265.IMPNAM265 Appendix C, DED 0263

13869 Link to description of other O O 265.SGMUNU265 Appendix C, DED 0118

or unusual effect
139 VECP royalty expiration O O 289.ECPROY289 Appendix C, DED 0082
date70

COST:
140 Total cost/savings under M M M 289.CONCOS289 or DIP4.4.3.1 and Appendix C, DED 0172
contract 351.RFD01935171 (for 4E & 4F);
DIP4.2.1.w and Appendix C, DED 0132
(for subpacket 4G)

141 Total cost/savings to M M 289.TOTCOS289 DIP4.4.3.2 and Appendix C, DED 0172

Government

142 Budgetary estimate of O M 289.RDTCOS289 Appendix C, DED 0172

RDT&E costs
143 Budgetary estimate of M M 289.PRDCOS289 Appendix C, DED 0172
production costs

144 RFD price consideration M 351.RFD19A351 DIP4.2.1.x and Appendix C, DED 0104
rationale

14572 DoD service component O O 252.SERVID252 DIP4.2.1.y, DIP4.4.1, and Appendix C,

bearing cost DED 0002
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

69
The 'Name of other effect' (sequence 136) and 'Link to other or unusual effect' (sequence 137) fields are paired fields; they must either both be blank or both be nonblank. This series of fields should be
repeated for each unusual effect of the ECP which not otherwise addressed in the ECP.
70
Mandatory if the value of 'ECP justification code' (sequence 29) is 'V'; otherwise, must be blank.
71
For subpackets 4E and 4F: Use the Tag that starts with 289
For subpacket 4G: Use the Tag that starts with 351.
72
If more than one service component is to share the cost of this ECP and a multi-page spreadsheet is not used, repeat this series of fields for each service component.

72
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
72
146 Cost file originator O O 252.FILORG900 DIP4.2.1.y, DIP4.4.1, and Appendix C,
DED 0069
14772 Cost file originator address O O 252.FILADD900 DIP4.2.1.y, DIP4.4.1, and Appendix C,
DED 0081

14872 Cost file identifier O O 252.FILIDN900 DIP4.2.1.y, DIP4.4.1, and Appendix C,

DED 0206
149- Cost file creation date & O O 252.FILDAT900 and DIP4.2.1.y, DIP4.4.1, and Appendix C,
15072 time 252.FILTIM900 DEDs 0082 and 0160
151- File Identification Subpacket O O See Data Information DIP4.2.1.y, DIP4.4.1, and Data
18472 for cost spreadsheet Subpacket 9B Information Packet 9

Document representations and attached files:

185 Expanded text file originator M M M M 261.FILORG900 or DIP4.2.1.z and Appendix C, DED 0069
358.FILORG900

186 Expanded text file originator M M M M 261.FILADD900 or DIP4.2.1.z and Appendix C, DED 0081
address 358.FILADD900

187 Expanded text file identifier M M M M 261.FILIDN900 or DIP4.2.1.z and Appendix C, DED 0206
358.FILIDN900

188- Expanded text file creation M M M M 261.FILDAT900 and DIP4.2.1.z and Appendix C, DEDs 0082
189 date & time 261.FILTIM900, or and 0160
358.FILDAT900 and
358.FILTIM900

190- File Identification Subpacket M M M M See Data Information DIP4.2.1.z and Data Information Packet 9
223 for expanded text file Subpacket 9B

224 Milestone chart file O M M 261.FILORG900 or DIP4.2.1.aa and Appendix C, DED 0069
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

originator 358.FILORG900

225 Milestone chart file O M M 261.FILADD900 or DIP4.2.1.aa and Appendix C, DED 0081
originator address 358.FILADD900

226 Milestone chart file O M M 261.FILIDN900 or DIP4.2.1.aa and Appendix C, DED 0206
identifier 358.FILIDN900
227- Milestone chart file creation O M M 261.FILDAT900 and DIP4.2.1.aa and Appendix C, DEDs 0082
228 date & time 261.FILTIM900, or and 0160
358.FILDAT900 and
358.FILTIM900

73
MIL-STD-2549
Data Information Packet 4

TABLE DIP4-I: Configuration change control

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
4A 4B 4C 4D 4E 4F 4G 4H 4I 4J
229- File Identification Subpacket O M M See Data Information DIP4.2.1.aa and Data Information Packet
261 for milestone chart file Subpacket 9B 9
262- Document Representation M M M M M M M M M M See Data Information DIP4.2.1.at and Data Information Packet
299 Subpacket Subpacket 10A 10

Specific changes:
300 NOR O73 O73 O73 O73 O73 See Data Information DIP4.2.1.ab and Data Information
Subpacket 4G Subpacket 4G
301- Parts list changes O See Data Information Data information Packet 7
325 Subpacket 7B
32674 Type of change to note O75 325.CHGTYP325 DIP4.2.1.ac and Appendix C, DED 0260
32774 Note number O75 325.NOTNUM325 DIP4.2.1.ac and Appendix C, DED 0215
74 76
328 Note text O 325.NOTTXT325 DIP4.2.1.ac and Appendix C, DED 0252
74 76
329 Type of change to special O 327.CHGTYP327 DIP4.2.1.ac and Appendix C, DED 0261
condition code

33074 Special condition code O77 327.SPNOTE327 DIP4.2.1.ac and Appendix C, DED 0257

73
For subpackets 4A, 4B, and 4D through 4F: This field and sequence 68 are mutually exclusive; for each affected document in sequence 63 through 68 for which the 'Specific affect on document' (sequence
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

68) is nonblank, this field must be blank. If this field is nonblank, the series of fields, 'NOR' through 'Special condition code' (sequence 300 through 330) is must be provided.
For subpackets 4A, 4D and 4E: If this ECP is being prepared by the nongovernment CDCA of the document(s) being changed by the ECP and the Government is responsible for performing logistics support
but has tasked the preparing activity to identify the logistics impact of proposed changes, both sequence 68 and 300 should be blank.
For subpackets 4B, 4D and 4F: If this ECP is being prepared by the nongovernment CDCA of the document(s) being changed by the ECP and the preparing activity is responsible for providing all logistics
support of the item to the Government,both sequence 68 and 300 should be blank.
74
Repeat series of fields 'Type of change to note' through 'Special condition code' (sequence 326 through 330) as necessary.
75
The fields 'Type of change to note' (sequence 326) and 'Note number' (sequence 327) must be either both blank, or both nonblank.
76
Must be blank if the value of 'Type of change to note' (sequence 326) is blank.
77
Must be blank if the value of 'Type of change to special condition code' (sequence 329) is blank.

74
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

DIP4.2. Content of data information subpackets. The information subpackets define the elements and documents/files
to be provided and correlates the information elements with the conceptual CM AIS database described in Appendices B
and C. Within the table, the inclusion of the element in the information subpacket is either mandatory (M) or optional
(O). For each subpacket, the subpacket number (for example: 4E) shall be followed by the various elements listed.
These elements shall be provided in the order shown in Table DIP4-I, except that fields which are not applicable
(denoted by blank) and optional fields (denoted by O) for which data is not being submitted shall be skipped. Each
element shall be preceded by the Data Element Tag as shown in the table. The full field size for the data element, as
shown in Appendix C, shall be used and shall immediately follow the data element tag. No delimiters will be used
between the fields. The end of each data subpacket shall be indicated by the inclusion of "/end". The last column in the
table contains a reference to the contents of the data element.

DIP4.2.1 Content Instructions.

a. Provide the revision level of the ECP/NOR/RFD/modification request/modification instruction. The initial issue
(release) shall be a dash (-) indicating no revision. Subsequent revisions shall be consecutively identified. (For
example, where a Message ECP is followed by a Preliminary ECP, which in turn is followed by a Final ECP, and
there were no intermediate requirements for a resubmittal; the Message ECP would be assigned the "-"; the
Preliminary ECP would be assigned the "R1" revision level; and the Final ECP would be assigned the "R2"
revision level.)

b. The purpose of the message ECP is to expedite the initiation of action on Class I Emergency or Urgent priority, or
Compatibility code ECPs.

(1) An ECP which, in the originator's judgment carries a priority of emergency or urgent, and requires
immediate action, may be initiated verbally (by telephone or personal contact), or in writing (by hard copy
or electronic message). When the initial contact is verbal, a follow-up written confirmation message is
required as soon as possible. If the initial reaction by the addressee of the communication(s) is favorable, a
written preliminary or final ECP is required as soon as practicable.

(a) For an initial verbal contact, the contractor shall specifically identify the affected item(s), briefly describe
the change, and indicate why time is of the essence. The contractor shall make a note of the conversation
for referencing on the follow-up written message.

(b) A written message shall also specifically identify the affected item(s), briefly describe the change,
provide a not-to-exceed/not-less-than cost impact, schedule impacts, and indicate why time is of the
essence. If a verbal contact preceded the written message, it shall be referenced in the written message
as to date and time of occurrence, person(s) contacted, and direction (if any) received.

(2) An ECP which, in the originator's judgment warrants a justification code of 'compatibility' (all aspects of the
compatibility code definition are applicable), may also be submitted as described above. With initial
favorable reaction, corrective action may then be implemented immediately by the performing activity to
resolve such incompatibilities, but only for the specific item(s) situated in the location at which the
deficiency was originally discovered. In addition, a final Class I compatibility code ECP is required within
30 days after initial notification. In those cases where additional action is necessary due to "lead time"
considerations, the performing activity may initiate procurement or manufacturing action, advising the
tasking activity by notification of the serial number(s) and locations of additional items involved. The
performing activity assumes total risk for implementation of such additional action prior to tasking activity
authorization, except in those cases where the tasking activity caused the incompatibility.

75
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

c. Provide the identifier of the CDCA for the ECP78, NOR79, RFD80, modification request81, or modification
instruction82.

d. Provide the current status of the ECP/NOR/RFD/modification request/modification instruction. The tasking
activity cannot act on the ECP/RFD/modification request/modification instruction until it is in the status of
'SUBMIT'.

e. Provide the effective date of the current status of the ECP/RFD/modification request/modification instruction. The
date shall be expressed in eight numeric characters (YYYYMMDD), for example: "19950825."

f. Provide the identifier of the known application activity(s), if any, which have an interest in this ECP. Repeat this
field for all known application activities. This list can be determined from the CSA database based on the
documents affected by this ECP.

g. For subpackets 4A through 4F, if this is a related ECP, enter the CAGE code and identifier of the primary ECP. If
this is a dependent ECP, enter the CAGE code and identifier upon which it depends; otherwise, leave blank. For
subpacket 4H, if this is a recurring deviation, enter the CAGE code and identifier of the most recent prior
deviation for the same problem.

h. Provide a summary description of the proposed change.

(1) For subpackets 4A and 4B (Class II ECPs, Minor engineering changes), the description should include the
purpose and should be given in sufficient detail to adequately describe what is to be accomplished.

(2) For subpacket 4C, the description should include the purpose and should be given in sufficient detail to
adequately describe what is to be accomplished and the logistics impact of the proposed change.

(3) For subpackets 4D through 4F (Preliminary ECPs, Final ECPs, and Major engineering changes), the
description should be phrased in definitive language such that, if it is repeated in the contractual document
authorizing the change, it will provide the authorization desired. A description as to which part of the item
or system is being changed should also be included.

(4) For subpacket 4G (RFDs), provide a summary description of the nature of the proposed departure form the
technical requirements of the configuration documentation for the deviation being requested. Identify the
configuration documentation which contains the relevant technical requirements from which the deviation is
being requested.

i. Provide the Standard Generalized Markup Language (SGML) tag used to identify the part of the ECP/RFD
extended text file that contains the complete description of the proposed change summarized in sequence 50 (see
DIP4.2.1.h). For subpackets 4A, 4B, 4D and 4E, address the impact on operational employment, other systems
and equipment, life cycle costs, warranties, etc. (See also, sequence 68.) If supplemental drawings and sketches
are necessary to clearly portray the proposed change, they shall be referenced here as attachments. If the proposed
change is an interim solution, this should be so stated.

78
All documents affected by an ECP must have the same CDCA as the ECP. If documents with different CDCAs are affected by a proposed change,
then related ECP(s) must be processed.
79
Must be the same as the document being changed by the NOR
80
Must be the same as the tasking activity for the product affected by this RFD.
81
Usually is the proposing organization/agency
82
Usually is the issuing organization/agency

76
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

j. Provide a summary explanation of the need for the change in this field. It is the decision of the originator which
information to include in the summary; however, this section must specifically identify the benefit of the change to
the tasking activity.

(1) For subpackets 4A through 4F (ECPs), the nature of the defect, failure, incident, malfunction, etc.,
substantiating the need for the change shall be described in detail. Full utilization shall be made of available
failure data. If a new capability is to be provided, improvements in range, speed, performance, endurance,
striking power, defensive or offensive capabilities, etc., shall be described in quantitative terms.
Correspondence establishing requirements for the change and any testing accomplished prior to the
submission shall be identified and summarized. If the ECP is needed to correct maintenance/logistics
problems, that fact will be included with sufficient detail to identify the issues. If the ECP is being
submitted as a response to a request for ECP or tasking activity direction, cite that authority herein.

(2) For subpackets 4C through 4F (Class I ECPs), if the ECP priority is 'Urgent' or 'Emergency', explain the
reason for the need for urgent processing of the proposed change.

(3) For subpacket 4G (RFDs), explain why it is impossible or unreasonable to comply with the configuration
documentation within the specified delivery schedule. Also explain why a deviation is proposed in lieu of a
permanent design change.

k. Provide the Standard Generalized Markup Language (SGML) tag used to identify the part of the ECP/RFD
extended text file that contains the complete rationale for the proposed change. If test data, analysis, and other
technical documentation providing supporting rationale for the tasking activity to base their acceptance of the
proposed change are included to clearly define the proposal, they shall be referenced here as attachments and
listed as supplemental documents in sequence 63 through 67.

l. Provide the Standard Generalized Markup Language (SGML) tag used to identify the part of the ECP/RFD
extended text file that contains the complete rationale as to why the recurrence was not prevented by the previous
corrective action(s).

m. If there is at least one effectivity block which is a retrofit, the originating activity of the ECP shall make
recommendations for retrofit of the engineering change into accepted items with substantiating data, any
implications thereto, and a brief description of the action required. If retrofit kit(s) will be required, describe the
estimated kit delivery schedule by quantity and date. When special tooling for retrofit is required for Government
use, include the dates of availability of tools, jigs, and test equipment required in conjunction with the kits to
accomplish the change. When retrofit is not recommended, an explanation of this determination shall be provided
instead.

n. When the delivered CI is installed in one or more ship or vehicle classes, provide the identification of such
classes, or provide the location(s) at which retrofit is to be accomplished along with the quantity to be retrofit at
each location.

o. The description of change should be stated in text or graphics in specific terms, including references to any
attached marked-up documents. Include both the current and new conditions. Terms such as 'From' and 'To', 'As-
is' and 'Should-be', 'Current' and 'Proposed', or similar should be used followed by the pertinent text or graphics.
Alternatively, use the 'redline and strike-out' capability of most text processors, or any other method which clearly
shows what the characteristics are prior to the change and what they are supposed to be after incorporation of the
approved change. Text which is being deleted without replacement must be included in full. Generally, the
description should be complete enough that a person who is not knowledgeable of the document could change the
document as intended by the author based solely on this description.

(1) For subpackets 4A, 4B, and 4D through 4F: If (a) only one document is being changed by the ECP, (b) the
change is not complex, and (c) the CDCA and custodian for the current approved configuration document or

77
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

software program (identified in sequence 65 through 67) which must be changed to accomplish this ECP
are the same, provide the SGML tag used to identify the part of the ECP extended text file which is the start
of the detailed description of the proposed change. However, if the proposed change is to a specification,
defense specification, or engineering drawing and is extensive or includes changes to a parts list or to
drawing notes, this field should be blank and the information should be included in the attached subpacket
4G. (See also: sequence 300.)

(2) For subpacket 4G: Provide the SGML tag used to identify the part of the RFD extended text file which is
the start of the detailed description of the requirement and the deviation being requested from that
requirement.

(3) For subpacket 4J: For extensive proposed changes to a current approved specification, defense
specification, or engineering drawing (excluding changes to parts lists and notes) which must be changed to
accomplish this ECP or when the custodian and CDCA of the document are not the same, provide the
SGML tag used to identify the part of the NOR extended text file which is the start of the description of the
proposed change.

p. In order of preference, the product-tracking base-identifier is:

(1) the Type and Model portion (see Table B-II) of the configuration item designation as assigned in
accordance with MIL-STD-196, MIL-STD-787, MIL-STD-1812 or AR 70-50/NAVMATINST
8800.4/AFR 82-1, or

(2) the drawing number of tabulated part or assembly drawings, or

(3) the drawing number of one of the non-tabulated parts (or assemblies) within the group of like items, or

(4) the specification number of parts or materials defined by a program-unique specification or standardization
document, or

(5) the part number of standard parts, or

(6) the material identifier of any material defined in terms like class, grade, type, etc. (without a part number).

q. Specify the effectivity of the proposed change.

(1) In determining the effectivity point for the proposed change, the performing activity shall consider, in
addition to the time factors, the availability of all support elements affected and the most economical point
of introduction consistent with all the salient factors involved. The earliest production incorporation is not
necessarily the singular or most important factor in the establishment of a proposed change effectivity point.
The effectivity point will be based on concurrent availability of all logistics support elements and materials
affected by the change to the item.

(2) For proposed changes to CSCIs, where applicable, the effectivity of the end item CI, or vehicle (aircraft,
tank, ship, etc.), into which the capability represented by the new version of the software is proposed to be
incorporated, shall also be provided. If the impact of the proposed change merits the release of a new
software version, the ECP submittal shall include a recommendation to this effect.

(3) For each block of one or more units to be affected by this proposed change, including both future production
and retrofit of delivered units, provide the following information:

(a) Provide the product tracking-base identifier (common base number) which is being used as the unchanging
basis for tracking individual units.

78
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

(b) Provide the manufacturer's CAGE Code of the affected units.

(c) Provide the type of tracking identifier (Government serial number, manufacturers serial number, lot
number, etc.) being used to track affected units.

(d) Provide the tracking number of the first unit in the block of affected units.

(e) Provide the tracking number of the last unit in the block of affected units.

(f) Indicate if this effectivity block represents a forward fit into future production units, or a retrofit of
delivered units.

r. For each of the applicable maintenance levels, show the amount of work which must be programmed for various
activities to install retrofit kits, test retrofit installation and test the retrofitted system. Estimate work-hours to
install retrofit kits when weapon system is undergoing overhaul.

s. Provide the estimated delivery date of the first item incorporating the change, either in terms of days after
contractual approval, or by specific dates contingent upon contractual approval by a specified date. If there will
be no effect on the delivery schedule, so state. For a complex ECP, or for related ECPs, this delivery date will be
related to any other events which may adversely affect the projected delivery.

t. Describe the effects of the proposed change on the developmental program as described below.

(1) For CIs, when the proposed engineering change requires a major revision of the development program (e.g.,
new prototypes, additional design review activity, tests to be re-accomplished), the nature of the new
development program shall be described in detail, including the status of programs already begun. If some
already-accomplished work will have to be re-accomplished, the rationale for re-accomplishing the work
shall be included.

(2) For CSCIs, the performing activity shall identify the scheduled sequence of computer software design and
test activities which will be required. ECPs initiated after preliminary design which affect the FBL and/or
the ABL shall identify, as appropriate, significant requirements for computer software redesign, recoding,
repetition of testing, changes to the software engineering/test environments, special installation, adaptation,
checkout, and live environment testing. In addition, the specific impact of these factors on approved
schedules shall be identified. The impact of the software change on the hardware design and input/output
cabling shall also be detailed.

(3) When applicable, the performing activity shall make recommendations as to the additional tests, trials,
installations, prototypes, fit checks, etc., which will be required to substantiate the proposed engineering
change. These recommendations shall include the test objective and test vehicle(s) to be used. If additional
space is required, this analysis shall be included in the ECP document representation.

u. The originating activity shall provide the date(s) by which contractual authority to proceed is needed in order to
achieve the recommended effectivity point(s) of the ECP by citing the date for production and retrofit, as
applicable.

v. Provide a summary of the actions that may be required, the system elements affected, and the overall effects of
disapproving the ECP.

w. Provide the estimated price reduction or other valuable consideration to the tasking activity for the acceptance of
this nonconforming unit(s).

x. Provide the rationale for arriving at the price reduction amount, or other consideration, identified in sequence 133.

79
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

y. This file should be part of the ECP/RFD document representation, or may be a stand-alone file if this is an on-line
ECP without a stored document representation.

z. The SGML tags required for the text paragraphs must appear in this file, followed by the pertinent text. This file
may have other headings, paragraph numbers, etc., and may be part of the ECP/RFD document representation, or
may be a stand-alone file if this is an on-line ECP/RFD without a stored document representation.

aa. This file may be part of the ECP/RFD document representation, or may be a stand-alone file if this is an on-line
ECP/RFD without a stored document representation. It must contain a milestone chart which clearly shows the
following:

(1) CIs: Enter the symbols and text, as appropriate for the activity, to show the time phasing of
accomplishments related to the deliveries of items (CIs, spares/repair parts); the accomplishment of the
retrofit; the generation of the retrofit instructions (MWO/TCTO/SC/ALT/TD); the updates of the tech
manuals, support software, etc.; and the deliveries of support equipment, training equipment, and
documentation incorporating the changes resulting from this ECP. Enter other symbols and notations to
show the initiation or termination of significant actions related to thes accomplishments. All dates shall
be based upon months after contractual approval of the basic ECPs.

(2) CSCIs: Enter the symbols and text as appropriate for the activity, to show the time phasing of
accomplishments related to the development and delivery of the updated software (software engineering,
documentation, replication, distribution, etc.); to the updating of the training equipment (operator,
maintenance, etc.); and to the updating of the software support elements (software engineering
environment upgrade, test environment upgrade, etc.) to reflect the changes resulting from this ECP.
Enter other symbols and notations to show the initiation or termination of significant actions related to
these accomplishments. All dates are based upon months after contractual approval of the basic ECP.

ab. ECPs, RFDs, and NORs may be maintained as "on-line" documents. In this case, there would not be any
stored document representation, but rather, the complete contents of the ECP/RFD/NOR would be contained in
the CM AIS database; thus, the ECP/RFD/NOR could be generated in any format desired at any time. If the
on-line approach is used, the document representation identifier should be "ON-LINE IN CM AIS" or
something similar and only the minimum required information should be reported. If a document
representation is stored, it must contain all the ECP/RFD/NOR information required by the appropriate data
information subpacket.

ac. Specify the addition, deletion, or change to notes, including the addition or deletion of special condition notes.

DIP4.2.2 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CSA database, but have the constant value indicated. Because they have constant values, they do not have to
be transmitted as part of the information subpacket.

DIP4.2.2.1 Subpackets 4A through 4F.

a. The value of document-source-identification-type-code, 010.ENTTYP010, is "C".

b. The value of entity-type-code, 000.ENTTYP000, is "E".

c. The value of enterprise-identification-type-code, 002.ENTTYP002, is "CAG".

d. The value of document-type-code, 010.DOCTYP010, is 'ECP'.

e. The value of document-identification-type-code, 010.IDNTYP010, is "N".

80
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

f. If the value of 250.PECPFG250 is 'R' or 'S', then the value of primary-engineering-change-proposal-document-

type-code, 250.PECPTY250. is 'ECP'.

g. If the value of 250.PECPFG250 is 'R', then the value of engineering-change-proposal-document-implementation-

sequence-code, 250.ECPSEQ250, is 'W'.

h. If the value of 359.CRFDCG359 (sequence 46) is nonblank, the value of 359.ECPTYP250 is 'ECP' and the
values of 359.ECPCAG250 and 359.ECPNUM250 are the values in sequence 2 and 4, respectively.

DIP4.2.2.1.1 Subpackets 4A and 4B.

a. The value of engineering-change-proposal-document-change-class-code, 251.ECP050251, is '2'. (See also:

Appendix C, DED 0164.)

b. The value of the engineering-change-proposal-document-format-type-code, 251.ECP08E251, is 'F'. (See also:

Appendix C, DED 0194.)

DIP4.2.2.1.2 Subpacket 4C.

a. The value of the engineering-change-proposal-document-format-type-code, 251.ECP08E251, is 'M'. (See also:

Appendix C, DED 0194.)

b. The value of engineering-change-proposal-document-change-class-code, 251.ECP050251, is '1'. (See also:

Appendix C, DED 0164.)

c. The value of ECP format, 251.ECP, is 'M'

DIP4.2.2.1.3 Subpacket 4D.

a. The value of the engineering-change-proposal-document-format-type-code, 251.ECP08E251, is 'P'. (See also:

Appendix C, DED 0194.)

b. The value of engineering-change-proposal-document-change-class-code, 251.ECP050251, is '1'. (See also:

Appendix C, DED 0164.)

DIP4.2.2.1.4 Subpackets 4E and 4F.

a. The value of the engineering-change-proposal-document-format-type-code, 251.ECP08E251, is 'F'. (See also:

Appendix C, DED 0194.)

b. The value of engineering-change-proposal-document-change-class-code, 251.ECP050251, is '1'. (See also:

Appendix C, DED 0164.)

DIP4.2.2.2 Subpacket 4G.

a. The value of document-source-identification-type-code, 010.ENTTYP010, is "C".

b. The value of entity-type-code, 000.ENTTYP000, is "E".

c. The value of enterprise-identification-type-code, 002.ENTTYP002, is "CAG".

d. The value of document-type-code, 010.DOCTYP010, is 'RFD'.

81
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

e. The value of document-identification-type-code, 010.IDNTYP010, is "N".

f. If the value of 351.RFD018351 (sequence 42) is 'Y', then the value of 351.RFDCAG350, 351.RFDNUM350,
351.RFDTYP350, and 351.RFDREV351 are inherited into 359.CRFDCG359, 359.CRFDNO359,
359.RFDTYP340, and 359.RFDREV351, respectively.

DIP4.2.2.3 Subpacket 4H. The value of document-type-code, 010.DOCTYP010, is 'MODREQ'.

DIP4.2.2.4 Subpacket 4I.

a. The value of document-type-code, 010.DOCTYP010, is 'MODINST'.

b. If the value of 'Supplemental/affected document source' (sequence 65) is nonblank, the value of
461.TMNTYP550 is 'TECHMAN'.

c. If the value of 'Supplemental/affected document source' (sequence 65) is nonblank and the value of 'Modification
instruction type code' (sequence 26) is 'MWO', the value of 468.TMNTYP550 is 'TECHMAN'.

d. If the value of 'Supplemental/affected document source' (sequence 65) is nonblank and the value of 'Modification
instruction type code' (sequence 26) is 'RAC', the value of 467.TMNTYP550 is 'TECHMAN'.

DIP4.2.2.5 Subpacket 4J.

a. The value of document-source-identification-type-code, 010.ENTTYP010, is "C".

b. The value of entity-type-code, 000.ENTTYP000, is "E".

c. The value of enterprise-identification-type-code, 002.ENTTYP002, is "CAG".

d. The value of document-type-code, 010.DOCTYP010, is 'NOR'.

e. The value of document-identification-type-code, 010.IDNTYP010, is "N".

DIP4.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

DIP4.4. Cost data requirements for Final Class I ECPs. ECP cost information shall be prepared and stored using a
spread sheet.

DIP4.4.1. ECP cost information. A separate spread sheet will be prepared for each service or other government
agency which will have to separately fund a portion of the ECP implementation to show their portion of the costs.83 The
cell contents of these spread sheets are shown in Table DIP4-II. For each spread sheet prepared, provide the DOD
service component or other Government agency identifying acronym and the file identification.

DIP4.4.2 Instructions for preparing the spread sheet. This spread sheet is intended to capture the estimated net total
cost/savings impact of this single ECP. Each cost factor associated with the ECP shall be considered as to whether such
cost or portion thereof under the subject contract is recurring or nonrecurring. Enter cost savings as applicable, using
entries in the "unit" and "quantity" columns when appropriate. Cost increases shall be entered as positive numbers, and
cost decreases as negative numbers. Other costs/savings to the Government resulting from approval of this ECP shall be

83
A multi-sheet spread sheet may be used in lieu of separate files. If a multi-sheet spread sheet is used, label each sheet to indicate to which
service it applies, or if it is the summation sheet. In this case, enter the lead service acronym in 252.SERVID252.

82
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

entered to the extent these costs can be determined by the performing activity. This estimate of cost impact will be used
for planning purposes and for a Cost Reduction (code R) or Value (code V) ECP analysis as to the net saving that would
result. If an ECP affects items being delivered to more than one service, a separate spread sheet shall be filled out for
the quantities to be delivered to each service. Nonrecurring costs shall be prorated between the using services.

DIP4.4.2.1. Production costs/savings. Enter the estimate of costs/savings applicable to production of the CI resulting
from incorporation of the change. Show redesign costs for the CI in the block titled "engineering & engineering data
revision" when the item is in production. Enter the projected life cycle costs/savings applicable to the planned
production and spares buys of the item that are not yet on contract on the CONFIGURATION ITEM/CSCI row.
Calculate the subtotal of production costs (both nonrecurring, recurring, and future life cycle production).

DIP4.4.2.2. Retrofit costs. Enter the estimate of costs applicable to retrofit of the item, including installation and testing
costs. When Government personnel accomplish, or are involved in, the installation and/or testing activities, the
estimated costs shall be entered on the affected rows. Show only those design costs of the retrofit kit and data revision
costs strictly related to retrofit in this section when the CI is in production; show all redesign and data revision costs in
this section when the item is not in production. Costs of modifications required to existing GFE and subsequent testing
also shall be shown. Calculate the subtotal of retrofit costs. If some or all of the retrofit activities and costs will have to
be deferred and placed on contract at a future date, show that deferred portion of the cost applicable to each row.

DIP4.4.2.3. Logistic support costs/ savings. Enter the estimated cost of the various elements of logistics support
applicable to the item covered by the ECP. On the row titled "interim support," estimated costs shall be entered based
upon the period of time between initial installation/operation of the item (aircraft, tank, etc.) as modified by the ECP and
Government attainment of support capability. Such "interim support" costs shall include costs estimates of performing
activity recommended/provided spares and repair parts, special support equipment, training equipment and personnel
training program. On the row titled "maintenance manpower" shall be entered the estimated costs/savings for the
contracted maintenance support for the remainder of existing maintenance contracts. Other logistics support
costs/savings associated with logistics support elements for which appropriate titles do not appear in the spread sheet
may be entered on the row most closely associated with such costs. Calculate the subtotal of logistics support
costs/savings. Calculate the operation and support portion of the life cycle cost/savings.

DIP4.4.2.4. Other costs/savings. If there are other costs under the contract which do not fall under the production,
retrofit or logistics support headings, enter the total of such costs here. If there are other costs to the Government which
do not fall under the production, retrofit or logistics support headings or under "coordination of changes by Government,
enter the total of such costs on this row.

DIP4.4.2.5. Coordination of changes with other performing activities. This term applies to interface changes to items
other than GFE, and changes to GFE being covered under retrofit costs. If such coordination changes are covered by
related ECPs the estimated costs thereof shall not be entered here. However, if there are no related ECPs and
coordination with other performing activities is still required, an estimate of such costs shall be entered here, when
available.

DIP4.4.2.6. Coordination changes by Government. Enter an estimate of the cost to the Government of interface changes
which must be accomplished in delivered items (aircraft, ships, facilities, etc.) to the extent such costs are not covered
above, or in related ECPs.

DIP4.4.3. ECP summation. If the cost of the ECP are to be shared between two or more services or agencies, an ECP
cost summation sheet shall be provided. The cell contents for this summation sheet are shown in Table DIP4-III.

DIP4.4.3.1. Estimated costs/savings under contract. enter the total estimated costs/savings impact of this ECP on the
contract. This is the same as the amount which would appear in Cell G-44 as defined in Table DIP4-III. (See also:
Appendix C, DED 0172.)

83
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

DIP4.4.3.2. Estimated net total costs/savings to the Government. The estimated net total life cycle costs/savings is the
summation of the primary and all related ECPs, including other costs/savings to the Government. This is the summation
of the amount which appears in Cell G-47 (as defined in Table DIP4-III) for the basis and all related ECPs.

TABLE DIP4-II. Cell contents for ECP cost information spread sheet.
Content
Col Row Cell content
type
A 1 text 'ESTIMATED NET TOTAL COST IMPACT (Use parentheses for savings)'

A 2 text 'FACTOR'

A 5 text 'a. PRODUCTION COSTS/(SAVINGS)'

A 6 text ' (1) Configuration Item/CSCI'

A 7 text ' (2) Factory Test Equipment'

A 8 text ' (3) Special Factory Tooling'

A 9 text ' (4) Scrap'

A 10 text ' (5) Engineering & Engineering Data Revision'

A 11 text ' (6) Revision of test procedures'

A 12 text ' (7) Qualification of New Items'

A 13 text ' (8) ' followed by either a blank row, or a user identified production cost factor not identified
in rows a(1) through a(7)

A 14 text ' (9) ' followed by either a blank row, or a user identified production cost factor not identified
in rows a(1) through a(8)

A 15 text ' (10) ' followed by either a blank row, or a user identified production cost factor not identified
in rows a(1) through a(9)

A 16 text ' (11) SUBTOTAL OF PRODUCTION COSTS/(SAVINGS)'

A 17 text 'b. RETROFIT COSTS'

A 18 text ' (1) Engineering Data Revision'

A 19 text ' (2) Prototype Testing'

A 20 text ' (3) Kit Proof Testing'

A 21 text ' (4) Retrofit Kits for Operational Systems'

A 22 text ' (5) Prep of MWO/TCTO/ALT/TD'

A 23 text ' (6) Special tooling for retrofit'

A 24 text ' (7) Installation--contractor personnel'

A 25 text ' (8) Installation--Government personnel'

A 26 text ' (9) Testing after retrofit'

A 27 text ' (10) Modification of GFE/GFP'

A 28 text ' (11) Qualification of GFE/GFP'

A 29 text ' (12) ' followed by either a blank row, or a user identified retrofit cost factor not identified in
rows b(1) through a(11)

A 30 text ' (13) ' followed by either a blank row, or a user identified retrofit cost factor not identified in
rows b(1) through a(12)

84
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

TABLE DIP4-II. Cell contents for ECP cost information spread sheet.
Content
Col Row Cell content
type
A 31 text ' (14) ' followed by either a blank row, or a user identified retrofit cost factor not identified in
rows b(1) through a(13)

A 32 text ' (15) SUBTOTAL OF RETROFIT COSTS/(SAVINGS)'

A 33 text 'c. INTEGRATED LOGISTICS SUPPORT COSTS/(SAVINGS)'

A 34 text ' (1) Retrofit of spares/repair parts'

A 35 text ' (2) New spares/repair parts'

A 36 text ' (3) Supply/provisioning data'

A 37 text ' (4) Support equipment'

A 38 text ' (5) Retrofit kits for spares'

A 39 text ' (6) Operator training courses'

A 40 text ' (7) Maintenance training courses'

A 41 text ' (8) Revision of tech manuals'

A 42 text ' (9) New tech manuals'

A 43 text ' (10) Training/Trainers'

A 44 text ' (11) Interim support'

A 45 text ' (12) Maintenance manpower'

A 46 text ' (13) Computer programs/documentation'

A 47 text ' (14) ' followed by either a blank row, or a user identified logistics cost factor not identified in
rows c(1) through c(13) or c(17)

A 48 text ' (15) ' followed by either a blank row, or a user identified logistics cost factor not identified in
rows c(1) through c(16) or c(17

A 49 text ' (16) ' followed by either a blank row, or a user identified logistics cost factor not identified in
rows c(1) through c(15) or c(17)

A 50 text ' (17) Operations and Support Cost change'

A 51 text ' (18) SUBTOTAL OF LOGISTICS SUPPORT COSTS/(SAVINGS)'

A 52 text 'd. OTHER COSTS/(SAVINGS)'

A 53 text 'e. SUBTOTAL COSTS/(SAVINGS)'

A 54 text 'f. ESTIMATED NET TOTAL COSTS/(SAVINGS)'

B 2 text 'COSTS/(SAVINGS) UNDER CONTRACT'

B 3 text 'Non-Recurring'

B 6-15 dollar value User input field; value is based on titles of row and column

B 16 formula sum of contents of cell B6 through B15

B 18-24
dollar value User input field; value is based on titles of row and column
B 26-31

B 32 formula sum of contents of cell B18 through B31

B 34-49 dollar value User input field; value is based on titles of row and column

85
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

TABLE DIP4-II. Cell contents for ECP cost information spread sheet.
Content
Col Row Cell content
type
B 51 formula sum of values in cells B34 through B50

B 52 dollar value User input field; value is based on titles of row and column

B 53 formula sum of values in cells B16, B32, B51 and B52

C 3 text 'RECURRING'

C 4 text 'Unit'

C 6 and 9

C 18-24
dollar value User input field (unit cost dollar value); value is based on titles of row and column
C 26-31

C 34-49

D 4 text 'Quantity'

D 6 and 9

D 18-24
quantity
User input field (quantity of units); value is based on titles of row and column
value
D 26-31

D 34-49

E 4 text 'Total Recurring'

E 6 and 9 formula product of the contents of cell C# and the contents of cell D# where # is the row number

E 16 formula sum of the contents of cells E6 through E15

E 18-24
formula product of the contents of cell C# and the contents of cell D# where # is the row number
E 26-31

E 32 formula sum of the contents of cells E18 through E31

E 34-49 formula product of the contents of cell C# and the contents of cell D# where # is the row number

E 51 formula sum of the contents of cells E34 through E50

E 52 dollar value User input field; value is based on titles of row and column

E 53 formula sum of values in cells E16, E32, E51 and E52

F 3 text 'Total'

F 6-16

F 18-24

F 26-32 formula Sum of the contents of cell B# and cell E# where # is the row number

F 34-49

F 51-53

G 1 text User input field; Enter the value of the data element engineering-change-proposal-cost-
enterprise-identification-code

G 2 text 'Other Costs/(Savings) to the Tasking Activity'

G 6 dollar value User input field; value is based on titles of row and column

86
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

TABLE DIP4-II. Cell contents for ECP cost information spread sheet.
Content
Col Row Cell content
type
G 16 formula Copy of the contents of cell G6

G 18-31 dollar value User input field; value is based on titles of row and column

G 32 formula Sum of contents of cells G18 through G31

G 34-50 dollar value User input field; value is based on titles of row and column

G 51 formula Sum of contents of cells G34 through G50

G 52 dollar value User input field; value is based on titles of row and column

G 53 formula sum of values in cells G16, G32, G51 and G52

G 54 formula sum of the contents of cells F53 and G53

Notes: (1) The following cells are blank: A3, A4, B1, B4, B5, B17, B25, B33, B50, B54, C1-C2, C5, C7-C8, C10-C12, C16, C17, C25,
C32, C33, C50-54, D1-D3, D5, D7-D8, D10-D12, D16, D17, D25, D32, D33, D50-54, E1-E3, E5, E7-E8, E10-E12, E17, E25,
E33, E50, E54, F1-F2, F4, F17, F25, F33, F50, F54, G3-G5, G7-G12, G17, and G33. If desired by the originator, they can be X-
filled or shaded.
(2) Cell contents surrounded by quotation marks (' ') must be entered exactly as shown unless indicated otherwise.

TABLE DIP4-III. Cell contents for ECP summation cost spread sheet information.
Content
Col Row Cell content
type
A 1 text 'ESTIMATED NET TOTAL COST IMPACT (Use parentheses for savings)'

A 2 text 'FACTOR'

A 5 text 'a. PRODUCTION COSTS/(SAVINGS)'

A 6 text ' (1) Configuration Item/CSCI'

A 7 text ' (2) Factory Test Equipment'

A 8 text ' (3) Special Factory Tooling'

A 9 text ' (4) Scrap'

A 10 text ' (5) Engineering & Engineering Data Revision'

A 11 text ' (6) Revision of test procedures'

A 12 text ' (7) Qualification of New Items'

A 13 text ' (8) ' followed by either a blank row, or the user identified production cost factor identified
in this same cell on the service/agency spread sheet(s)

A 14 text ' (9) ' followed by either a blank row, or the user identified production cost factor identified
in this same cell on the service/agency spread sheet(s)

A 15 text ' (10) ' followed by either a blank row, or the user identified production cost factor
identified in this same cell on the service/agency spread sheet(s)

A 16 text ' (11) SUBTOTAL OF PRODUCTION COSTS/(SAVINGS)'

A 17 text 'b. RETROFIT COSTS'

A 18 text ' (1) Engineering Data Revision'

A 19 text ' (2) Prototype Testing'

87
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

TABLE DIP4-III. Cell contents for ECP summation cost spread sheet information.
Content
Col Row Cell content
type
A 20 text ' (3) Kit Proof Testing'

A 21 text (4) Retrofit Kits for Operational Systems'

A 22 text ' (5) Prep of MWO/TCTO/ALT/TD'

A 23 text ' (6) Special tooling for retrofit'

A 24 text ' (7) Installation--contractor personnel'

A 25 text ' (8) Installation--Government personnel'

A 26 text ' (9) Testing after retrofit'

A 27 text ' (10) Modification of GFE/GFP'

A 28 text ' (11) Qualification of GFE/GFP'

A 29 text ' (12) ' followed by either a blank row, or the user identified retrofit cost factor identified in
this same cell on the service/agency spread sheet(s)

A 30 text ' (13) ' followed by either a blank row, or the user identified retrofit cost factor identified in
this same cell on the service/agency spread sheet(s)

A 31 text ' (14) ' followed by either a blank row, or the user identified retrofit cost factor identified in
this same cell on the service/agency spread sheet(s)

A 32 text ' (15) SUBTOTAL OF RETROFIT COSTS/(SAVINGS)'

A 33 text 'c. INTEGRATED LOGISTICS SUPPORT COSTS/(SAVINGS)'

A 34 text ' (1) Retrofit of spares/repair parts'

A 35 text ' (2) New spares/repair parts'

A 36 text ' (3) Supply/provisioning data'

A 37 text ' (4) Support equipment'

A 38 text ' (5) Retrofit kits for spares'

A 39 text ' (6) Operator training courses'

A 40 text ' (7) Maintenance training courses'

A 41 text ' (8) Revision of tech manuals'

A 42 text ' (9) New tech manuals'

A 43 text ' (10) Training/Trainers'

A 44 text ' (11) Interim support'

A 45 text ' (12) Maintenance manpower'

A 46 text ' (13) Computer programs/documentation'

A 47 text ' (14) ' followed by either a blank row, or the user identified logistics cost factor identified
in this same cell on the service/agency spread sheet(s)

A 48 text ' (15) ' followed by either a blank row, or the user identified logistics cost factor identified
in this same cell on the service/agency spread sheet(s)

A 49 text ' (16) ' followed by either a blank row, or the user identified logistics cost factor identified
in this same cell on the service/agency spread sheet(s)

A 50 text ' (17) Operation and Support Cost change'

88
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 4

TABLE DIP4-III. Cell contents for ECP summation cost spread sheet information.
Content
Col Row Cell content
type
A 51 text ' (18) SUBTOTAL OF LOGISTICS SUPPORT COSTS/(SAVINGS)'

A 52 text 'd. OTHER COSTS/(SAVINGS)'

A 53 text 'e. SUBTOTAL COSTS/(SAVINGS)'

A 54 text 'f. ESTIMATED NET TOTAL COSTS/(SAVINGS)'

B 2 text 'COSTS/(SAVINGS) UNDER CONTRACT'

B 3 text 'Non-Recurring'

B 6-13

B 18-24
Sum of contents of all cell number B# for all instances of engineering-change-proposal-cost-
B 26-31 formula
enterprise-identification-code for this ECP, where # is the row number
B 34-49

B 51-53

C 3 text 'RECURRING'

C 4 text 'Total Recurring'

C 6, 9, and
16
Sum of contents of all cell number E# for each service or agency for which there is an ECP
C 18-24 cost sheet (all instances of engineering-change-proposal-cost-enterprise-identification-code)
formula
for this ECP, where # is the row number
C 26-32

C 34-53

D 3 text 'Total'

D 6-16
Sum of contents of all cell number F# for each service or agency for which there is an ECP
D 18-24
cost sheet (all instances of engineering-change-proposal-cost-enterprise-identification-code)
formula
for this ECP, where # is the row number
D 26-32

D 34-53

E 1 text 'TOTAL for THIS ECP (All Services)'

E 2 text 'Other Costs/(Savings) to the Tasking Activity'

E 6 and 16 Sum of contents of all cell number G# for each service or agency for which there is an ECP
cost sheet (all instances of engineering-change-proposal-cost-enterprise-identification-code)
E 18-32 formula
for this ECP, where # is the row number
E 34-54

Note: (1) The following cells are blank: A3, A4, B1, B4, B5, B17, B25, B33, B47, B55, C1-C2, C5, C7-C8, C17, C25, C33, C54, D1-D2,
D4-D5, D17, D25, D33, D54, E1, E3-E5, E7-E12, E17, E33. If desired by the originator, they can be X-filled or shaded.
(2) Cell contents surrounded by quotation marks (' ') must be entered exactly as shown unless indicated otherwise.

89
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

(This page intentionally left blank)

90
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 5

Configuration Management Action Item Status

DIP5.1. Purpose. Includes information concerning CCB-directed actions and configuration audit actions and their
status.

DIP5.1.1 Subpackets. There are 2 subpackets for this packet:

Subpacket Applicability
5A ECP/RFD implementation actions
5B Configuration audit actions

DIP5.2. Content of data information subpackets. The data information subpackets define the elements to be provided
and correlate the information elements with the conceptual CM AIS database described in Appendices B and C. Within
the table, the inclusion of the element in the information subpacket is either mandatory (M) or optional (O). For each
subpacket, the subpacket number (for example: 5A) shall be followed by the various elements in the order shown in
Table DIP5-I, except that fields which are not applicable (denoted by blank) and optional fields (denoted by O) for
which data is not being submitted shall be skipped. Each element shall be preceded by the Data Element Tag as shown
in the table. The full field size for the data element, as shown in Appendix C, shall be used and shall immediately follow
the data element tag. No delimiters will be used between the fields. The end of each data subpacket shall be indicated
by the inclusion of "/end". The last column in the table contains a reference to the contents of the data element.

TABLE DIP5-I. Configuration management action item status

Seq Field Name Data Information Data Element Tag For content and validation
# Subpacket instructions, see
5A 5B
1 Enterprise identifier M 262.CCBENT262 or DIP5.2.1.a. The transmitted field
370.CCBENT3701 must be 30 characters, left
justified and consisting of either a
CAGE code (Appendix C, DED
0001), an organization acronym
(Appendix C, DED 0002), or a
company name (Appendix C,
DED 0170).
2 Program name M 262.PROGNM691 or DIP5.2.1.b and Appendix C, DED
370.PROGNM6911 0059
3 CCB name M 262.CCBNAM700 or Appendix C, DED 0151
370.CCBNAM7001
4 Document type code/Audit type M M 262.ECPTYP250 or DIP5.2.1.c and for subpacket 5A,
code 370.RFDTYP350 or Appendix C, DED 0004; for
675.AUDTYP6752 subpacket 5B, Appendix C, DED
0070
5 ECP/RFD CAGE code M 262.ECPCAG250 or DIP5.2.1.d and Appendix C, DED
370.RFDCAG3501 0001

1
Use Table 262 for ECPs and Table 370 for RFDs.
2
For subpacket 7A: Use Table 262 for ECPs and Table 370 for RFDs.
For subpacket 7B: Use Table 675.

91
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 5

TABLE DIP5-I. Configuration management action item status

Seq Field Name Data Information Data Element Tag For content and validation
# Subpacket instructions, see
5A 5B
6 ECP/RFD alphanumeric M M 262.ECPNUM250 or DIP5.2.1.e and for subpacket 5A,
identifier/Contract identifier 370.RFDNUM350 or Appendix C, DED 0001; for
675.CONIDN9502 subpacket 5B, Appendix C, DED
0015
7 CI identifier M 675.CIIDEN695 DIP5.2.1.f and Appendix C, DED
0111
8 Audit date M 675.AUDDAT675 Appendix C, DED 0082
9 ECP/RFD revision M 262.ECPREV251 or DIP5.2.1.g and Appendix C, DED
370.RFDREV3511 0009
10 Action item identifier M M 262.ECPACT262 or Appendix C, DED 0072
370.RFDACT370 or
676.AUDACT6763
11 Action item title M M 262.ACTTTL262 or Appendix C, DED 0136
370.ACTTTL370 or
676.ACTTTL6763
12 Action item description M M 262.ACTDES262 or for subpacket 5A, Appendix C,
370.ACTDES370 or DED 0185; for subpacket 5B,
676.ACTDES6763 Appendix C, DED 0065
13 Action item comment O O 262.ACTCOM262 or Appendix C, DED 0066
370.ACTCOM370 or
676.ACTCOM6763
14 Responsible enterprise M M 262.RESPON262 or DIP5.2.1.h. The transmitted field
370.RESPON370 or must be 30 characters, left
676.ENTIDN0023 justified and consisting of either a
CAGE code (Appendix C, DED
0001), an organization acronym
(Appendix C, DED 0002), or a
company name (Appendix C,
DED 0170).
15 Responsible office M M 262.RESOFF262 or DIP5.2.1.i and Appendix C, DED
370.RESOFF370 or 0044
676.OFFSYM9413
16 Affected technical manual source O 262.SRCDOD552 DIP5.2.1.j and Appendix C, DED
0002
17 Affected technical manual iteration O 554.ITTYPE554 DIP5.2.1.j and Appendix C, DED
type code 0196
18 Affected technical manual identifier O 262.DOCNUM552 DIP5.2.1.j
19 ECP/RFD approval status date M 262.STADAT850 or Appendix C, DED 0082
370.STADAT8501
204 Violated document type M 681.DOCTYP010 DIP5.2.1.k and Appendix C, DED
0004

3
For subpacket 7A: Use Table 262 for ECPs and Table 370 for RFDs
For subpacket 7B: Use Table 676.
4
The series of fields 20, 21, 25 (identifying a contract citation), 20, 21, 22, 25 (identifying a SOW citation) and 20, 21, 23, 24, 25 (identifying an
'other document' citation) may be repeated as necessary.

92
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 5

TABLE DIP5-I. Configuration management action item status

Seq Field Name Data Information Data Element Tag For content and validation
# Subpacket instructions, see
5A 5B
4
21 Violated contract modification/ M 679.CONMOD951 or for contract modifications (Tags
document revision 680.CONMOD951 or ###.CONMOD951), Appendix C,
681.DOCREV0115 DED 0120; for other documents
(Tag 681.DOCREV011), the
transmitted field must be 8
characters, left justified and
consist of a revision identifier
conforming to either DED 0009
or 0143, as appropriate to the
document.
224 Violated SOW identifier O 680.SOWIDN957 Appendix C, DED 0229
4 6
23 Violated document source O 681.SRCIDN010 The transmitted field must be 30
characters, left justified and
consist of either a CAGE code
(Appendix C, DED 0001), an
organization acronym (Appendix
C, DED 0002), or a company
name (Appendix C, DED 0170).
See also: Table B-I
244 Violated document identifier O7 681.DOCIDN010 The transmitted field must be 240
characters, left justified and
consist of either an alphanumeric
identifier (Appendix C, DED
0003) or a title (Appendix C,
DED 0008) as appropriate. See
also: Table B-I
254 Violated document reference citation M 679.DOCREF679 or Appendix C, DED 0075
680.DOCREF680 or
681.DOCREF6818
269 ECP CAGE code O 682.ECPCAG250 DIP5.2.1.l and Appendix C, DED
0001
279 ECP identifier O 682.ECPNUM250 DIP5.2.1.l and Appendix C, DED
0003
28 Action item status code M M 264.STACOD264 or Appendix C, DED 0021
372.STACOD372 or
678.STACOD67810

5
If the value of 'violated document type' (sequence 20) is 'CONTRCT', use 679.CONMOD951; if the value of 'violated SOW identifier' (sequence
22) is nonblank, use 680.CONMOD951; otherwise, use 681.DOCREV011.
6
Must be blank if the violated document type (sequence 20) is 'CONTRCT', or if the violated SOW identifier (sequence 22) is nonblank.
7
Must be blank if Violated document source (sequence 23) is blank; must be nonblank if violated document source is nonblank.
8
If the violated document type (sequence 20) is 'CONTRCT', use 679.DOCREF679; if the violated SOW identifier (sequence 22) is nonblank, use
680.DOCREF680; for other documents, use 681.DOCREF681.
9
The series of fields 'ECP CAGE code' (sequence 26) and 'ECP identifier' (sequence 27) may be repeated as necessary.
10
For Data Information subpacket 7A; Use Table 264 for ECPs and Table 372 for RFDs.
For Data Information subpacket 7B: Use Table 678.

93
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 5

TABLE DIP5-I. Configuration management action item status

Seq Field Name Data Information Data Element Tag For content and validation
# Subpacket instructions, see
5A 5B
29 Action item status date M M 264.STADAT264 or Appendix C, DED 0082
372.STADAT372 or
678.STADAT67810
30 Action item status comment O O 264.ACTCOM264 or Appendix C, DED 0066
372.ACTCOM372 or
678.ACTCOM67810

DIP5.2.1 Content instructions.

a. Enter the name of the enterprise which convened the CCB which established these implementation action items.

b. Enter the program name of the program for which the CCB which established these implementation action items
was convened.

c. For subpacket 5A, enter either 'ECP' or 'RFD'.

d. Enter the CAGE code of the ECP or RFD for which these implementation action items were established.

e. For Data Information subpacket 5A, enter the ECP or RFD number for which these implementation action items
were established. For Data Information subpacket 5B, enter the complete identification of the contract on which
this audit was performed.

f. Enter the CI identifier for which this audit was performed.

g. For Data Information subpacket 5A, enter the revision letter of the approved ECP/RFD for which these
implementation action items were established.

h. Enter the identification of the enterprise which is responsible for performing the action identified in sequence 10.

i. Enter the identification of the specific office within the enterprise which is responsible for performing the action
identified in sequence 10.

j. Enter the identification information (sequence 16 through 18) on the technical manual which must be changed as a
result of the approved ECP and which is addressed by this implementation action item. See Table DIP5-II for
guidance on which DED is applicable to sequence 18.

Table DIP5-II. Reference DEDs for technical manual document identifiers

If value of affected technical manual For document identification rules

iteration type code (sequence 17) is: (sequence 18), see Appendix C,
DED:
C 0135

D 0003

S 0218

94
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 5

k. Enter the document type of the document which contains the reference which is the reason for the audit action
item.11

l. Enter the identification of the ECP which corrects the problem identified by this audit action item.

DIP5.2.2 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CSA database, but have the constant value indicated. Because they have constant values, they do not have to
be transmitted as part of the information subpacket.

DIP5.2.2.1 Subpacket 5A.

a. If the value of Affected Technical manual source (sequence 16) is nonblank, then the value of 262.TMNTYP552
is 'TECHMAN'.

b. The ECP/RFD approval status code (262.REVSTA850 or 370.REVSTA850) must have a value of 'APV'. (See
also: Appendix C, DED 0021.)

DIP5.2.2.2 Subpacket 5B. The document type code for the ECP identified in sequence 26 and 27 is 'ECP' and is used
in 682.ECPTYP250.

DIP5.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent
table will not be updated and the information subpacket will be rejected without action.

11
For a Statement of Work, use 'MISC'.

95
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

(This page intentionally left blank)

96
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

Project Management

DIP6.1. Purpose. Includes system/project and configuration item designations and hierarchy, CCB organization and
responsibility, baseline assignment, CDRL information, document review and disposition, CDRL submittal review and
disposition, identify staff and organization address and related contact information.

DIP6.1.1 Subpackets. There are 14 subpackets for this packet:

Subpacket Applicability
6A1 Identify organization
6A2 Add/change/remove staff member
6B1 Establish System/program/project and hierarchy
6B2 Assign CI nomenclature and establish CI hierarchy
6B3 Establish CCB and hierarchy
6C1 Define contract
6C2 Define CDRL
6C3 Define/change contract event (milestone)
6C4 Define data delivery plan
6C5 Submit data item
6D1 Technical review of and comment on document representation
6D2 Technical review of and comment on document
6D3 Technical review of and comment on data item
6D4 Disposition of a document representation
6D5 Disposition of a document
6D6 Disposition of a data item submittal
6D7 Issue CCB directive
6D8 DCMC classification concurrence
6E1 Correlate document to baseline
6E2 Assign CPIN
6E3 Assign PAN
6F1 Transfer CDCA of document
6F2 Add document representation to document
6F3 Change document custodian
6F4 Add, change, or delete application activity (including GLAA)

DIP6.2. Content of data information subpackets. The data information subpackets define the elements and
documents/files to be provided and correlates the information elements with the conceptual CM AIS database described
in Appendices B and C. Within the table, the inclusion of the element in the information subpacket is either mandatory
(M) or optional (O). For each subpacket, the subpacket number (for example: 6A2) shall be followed by the various
elements in the order shown in the appropriate table below, except that fields which are not applicable (denoted by
blank) and optional fields (denoted by O) for which data is not being submitted shall be skipped. Each element shall be
preceded by the data element tag as shown in the table. The full field size for the data element, as shown in Appendices
B and C, shall be used and shall immediately follow the data element tag. No delimiters will be used between the fields.
The end of each data subpacket shall be indicated by the inclusion of "/end". The last column in the table contains a
reference to the contents of the data element.

DIP6.2.1 Subpackets 6A1 and 6A2. Provide the information as required by Table DIP6-I.

97
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

Table DIP6-I: Organization and staff data information subpackets

Seq Field name Data Data Element Tag For content and
# Information validation instructions,
Subpacket see
6A1 6A2
1 Entity type code M 000.ENTTYP000 Appendix C, DED 0076
1
2 Enterprise identification type code O 002.ENTTYP002 Appendix C, DED 0050
3 CAGE type code O2 003.CAGTYP003 Appendix C, DED 0102

4 Organization type identifier O3 004.ORGTYP004 Appendix C, DED 0095

4
5 DOD organization type identifier O 034.DODTYP034 Appendix C, DED 0097
5
6 Service Acronym O DIP6A1.6 Appendix C, DED 0002,
united-states-defense-
component-enterprise-
acronym-identification-code
and DIP6.2.1.1.a

7 Navy command O6 DIP6A1.7 Appendix C, DED 0002,

united-states-navy-command-
enterprise-acronyum-
identification-code and
DIP6.2.1.1.a

8 Entity identifier M M 000.ENTYID000 Table DIP6-II

9 CAGE/NSCM code O7 006.CAGNUM003 or Appendix C, DED 0001 and

007.CAGNUM0038 DIP6.2.1.1.b

10 Organization name O3 004.ENTNAM004 Appendix C, DED 0170 and

DIP6.2.1.1.c

11 Mailing address O M 940.ADDRES940 Appendix C, DED 0039

12 Office symbol O M 941.OFFSYM941 Appendix C, DED 0044
9
13 Office security clearance level O 941.HICLAS941 Appendix C, DED 0224

14 Staff member name M 943.PERNAM943 Appendix C, DED 0069

1
Mandatory if the value of 'Entity type code' (sequence 1) is 'E'; must be blank for all other values of 'Entity type code'.
2
Mandatory if the value of 'Enterprise identification type code' (sequence 2) is 'CAG'; must be blank for all other values of 'Enterprise identification
type code'.
3
Mandatory if the value of 'Enterprise identification type code' (sequence 2) is 'ORG'; must be blank for all other values of 'Enterprise identification
type code'.
4
Mandatory if the value of 'Organization type identifier' (sequence 4) is 'DOD'; must be blank for all other values of 'Organization type identifier'.
5
Mandatory if the value of 'DOD organization type identifier' (sequence 5) is 'SERVICE'; must be blank for all other values of 'DOD organization
type identifier'.
6
Mandatory if the value of 'Service acronym' (sequence 6) is 'USN'; must be blank for all optional for all other values of 'Service acronym'.
7
May be nonblank if the value of 'Enterprise identification type code' (sequence 2) is 'COM', or if the value of 'Organization type identifier'
(sequence 4) is 'DOD'. Must be blank for all other cases.
8
If the value of 'Organization type identifier' (sequence 4) is 'COM', use the Tag that starts with 006. If the value of 'Organization type identifier'
(sequence 4) is 'DOD', use the Tag that starts with 007.
9
Must be blank if 'Office symbol' (sequence 10) is blank.

98
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

Table DIP6-I: Organization and staff data information subpackets

Seq Field name Data Data Element Tag For content and
# Information validation instructions,
Subpacket see
6A1 6A2
15 Telephone number O O 942.TELPHN942 or Appendix C, DED 0225
943.TELPHN94310

16 Fax number O O 942.FAXNUM942 or Appendix C, DED 0225

943.FAXNUM94310

17 EMail address O 943.EMAILX943 Appendix C, DED 0225

DIP6.2.1.1 Content instructions for subpackets 6A1 and 6A2.

a. This is necessary for the validation of the report.

TABLE DIP6-II: Reference entity identifier DEDs

Seq # (from Field Name (from Value of For content instructions, see DED
Table DIP6-I) Table DIP6-I) Field
1 Entity type code H 0069, author-human-name

2 Enterprise CAG 0001, enterprise-defense-logistics--assigned-identification-code

identification type
code COM 0170, commercial-name

4 Organization type INT 0002, international-organization-code

identifier
NON-US- 0002, non--united-states-government-enterprise-acronym-
GOVT identification-code
NON-US- 0002, non--united-states-nongovernment-enterprise-acronym-
NONGOVT identification-code

US-GOV- 0002, united-states-government-nondefense-enterprise-acronym-

NONDEF identification-code

US-NONGOVT 0002, united-states-nongovernment-enterprise-acronym-

identification-code

5 DOD organization AGENCY 0002, united-states-defense-department-enterprise-acronym-

type identifier identification-code
JSTAFF

OSD

UNI/SPEC
6 Service Acronym USA 0002, united-states-defense-component-enterprise-acronym-
identification-code
USAF
USMC

7 Navy command NAVAIR 0002, united-states-navy-command-enterprise-acronym-

identifier identification-code
NAVSEA

10
For subpacket 6A1: Use the Tag that starts with 942.
For subpacket 6A2: Use the Tag that starts with 943.

99
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

b. Enter the CAGE (or NSCM) code associated with the company or U.S. DOD organization identified in sequence
8 ('Entity identifier').

c. Enter the name of the organization whose acronym is used as the entity identifier in sequence 8 ('Entity identifier').

DIP6.2.1.2 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CSA database, but have the constant value indicated. Because they have constant values, they do not have to
be transmitted as part of the information subpacket.

DIP6.2.1.2.1 Subpacket 6A2. If the Mailing address' and 'Office symbol' are both nonblank, they are concatenated
with the Enterprise identifier ('Entity identifier' in sequence 8) and entered in 942.DIVADD942. (See also: Appendix
C, DED 0081.)

DIP6.2.2 Subpackets 6B1, 6B2, and 6B3. Provide the information as required by Table DIP6-III.

Table DIP6-III: System/CI/CCB data information subpackets

Seq Field name Data Information Data Element Tag For content and
# Subpacket validation instructions,
see
6B1 6B2 6B3
1 System/project/program M M M 691.PROGNM691 or Appendix C, DED 0059
name 692.PROGNM691 or
700.PROGNM69111

2 Next higher system/ O 698.SYSNAM698 Appendix C,DED 0059 and

project/program name DIP6.2.2.1.a

3 CI type M M 695.CITYPE695 Appendix C, DED 0115

12
4 CI designation standard O 693.CISTND693 Appendix C, DED 0051
12
5 CI designation O 693.CIDESG693 Appendix C, DED 0045
12
6 CI name O 209.PARNAM209 Appendix C, DED 0046
13
7 Software source O 696.SWSORC170 The transmitted field must be
36 characters, left justified and
consisting of either a CAGE
code (Appendix C, DED
0001), an organization
acronym (Appendix C, DED
0002), a company name
(Appendix C, DED 0170), or
an author's name (Appendix C,
DED 0069).

11
For subpacket 6B1: Use the Tag that starts with 691.
For subpacket 6B2: Use the Tag that starts with 692.
For subpacket 6B3: Use the Tag that starts with 700.
12
If the value of 'CI type' (sequence 3) is 'H', the fields 'CI designation standard', 'CI designation', and 'CI name' (sequence 4 through 6) must be
nonblank; if the value is 'C', they must be blank.
13
If the value of 'CI type' (sequence 3) is 'C', the fields 'Software source' and 'Software identifier' (sequence 7 and 8) be nonblank; if the value is 'H',
they must be blank.

100
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

Table DIP6-III: System/CI/CCB data information subpackets

Seq Field name Data Information Data Element Tag For content and
# Subpacket validation instructions,
see
6B1 6B2 6B3
8 Software identifier O13 696.SWIDEN170 The transmitted field must be
248 characters, left justified
and consisting of either a
software alphanumeric
identifier (Appendix C, DED
0088), a part number
(Appendix C, DED 0024), or a
software product identifier
(Appendix C, DED 0262)

9 CCB type M 700.CCBTYP700 Appendix C, DED 0173

10 CI Identifier O O14 703.CIIDEN695 Appendix C, DED 0111 and

DIP6.2.2.1.b

11 Primary equipment CI O 694.PCIIDN694 Appendix C, DED 0111 and

DIP6.2.2.1.c
12 Program (or project) M M 700.ENTIDN002 or DIP6.2.2.1.d. The transmitted
management/CCB 701.ENTIDN00215 field must be 30 characters, left
convening enterprise justified, and consisting of
either a CAGE code
(Appendix C, DED 0001, an
organization acronym
(Appendix C, DED 0002), or a
company name (Appendix C,
DED 0170).

13 CCB name O16 M 700.CCBNAM700 or Appendix C, DED 0151

703.CCBNAM70017

14 Next higher level CCB O 700.TOPCCB700 Appendix C, DED 0089 and

DIP6.2.2.1.e

15 CCB chairperson O18,19 700.PERNAM943 Appendix C, DED 0069

18,20
16 CCB member name O 702.PERNAM943 Appendix C, DED 0069
19,20
17 CCB chairperson/member O 700.DIVADD942 or Appendix C, DED 0081
address 702.DIVADD94221

14
If the value of 'CCB type' (sequence 9) is 'S', this field must be blank; this field must be nonblank for all other values of 'CCB type'.
15
For subpacket 6B1: Use the Tag that starts with 701.
For subpacket 6B3: Use the Tag that starts with 703.
16
Mandatory if 'CI identifier' (sequence 9) is nonblank; must be blank if 'CI identifier' is blank.
17
For subpacket 6B1: Use the Tag that starts with 703.
For subpacket 6B3: If the 'CI identifier' (sequence 9) is blank, use the Tag that starts with 700; if the 'CI identifier' is nonblank, use the Tag that
starts with 703.
18
If the 'CCB chairperson' (sequence 15) is nonblank, the 'CCB member name' (sequence 16) must be blank. If the 'CCB member name is nonblank,
the 'CCB chairperson' must be blank.
19
The fields 'CCB chairperson' and 'CCB member address' (sequence 15 and 17) must either both be blank, or both be nonblank.
20
The fields 'CCB member name' and 'CCB member address' (sequence 16 and 17) must either both be blank, or both be nonblank.
21
If the 'CCB chairperson' (sequence 15) is nonblank, use 700.DIVADD942; if the 'CCB member name' (sequence 16) is nonblank, use
702.DIVADD942.

101
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

Table DIP6-III: System/CI/CCB data information subpackets

Seq Field name Data Information Data Element Tag For content and
# Subpacket validation instructions,
see
6B1 6B2 6B3
18 CCB position O22 702.RESPON702 Appendix C, DED 0154 and
DIP6.2.2.1.f

DIP6.2.2.1 Content instructions for subpackets 6B1 through 6B3.

a. If the system (sequence 1) is a subsystem, enter the next higher level system/subsystem for which this is a
subsystem.

b. For subpacket 6B1, if this system (sequence 1) consists of one or more CIs, enter the CI identification here. For
subpacket 6B3, if this CCB is responsible for one or more CIs, enter the CI identification here.

c. If the system (sequence 1) is support equipment for another system, enter the name of the supported system(s).

d. For subpacket 6B1, enter the enterprise(s) responsible for management of this system/program. For subpacket
6B3, enter the enterprise which is responsible for all or part of this system and which is the convening authority
for this CCB.

e. If there is a hierarchy of CCBs, and there is a higher level CCB to which this CCB reports for this system and/or
CI (even if it is convened by a different enterprise) enter the complete identity of the higher level CCB.

f. Enter the area of responsibility of this CCB member (for example: logistics, engineering, purchasing, etc.)

DIP6.2.2.2 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CSA database, but have the constant value indicated. Because they have constant values, they do not have to
be transmitted as part of the information subpacket.

DIP6.2.2.2.1 Subpacket 6B2.

a. If the value of 'CI type' (sequence 3) is 'H', the values of 'CI designation' and 'CI designation name' (sequence 5
and 6) are concatenated and entered in 690.CINOMN690 and 695.CIIDEN695.

b. If the value of 'CI type' (sequence 3) is 'C', the values of 'Software source' and 'Software identifier' (sequence 7 and
8) are concatenated and entered in 695.CIIDEN695.

DIP6.2.3 Subpackets 6C1 through 6C4. Provide the information as required by Table DIP6-IV.

DIP6.2.3.1 Content instructions for subpackets 6C1 through 6C4.

a. Enter the paragraph, figure, table, etc. reference in the contract which was the source of the requirement for this
contract data item; or, enter the Statement of Work (SOW) identification and the paragraph, figure, table, etc.
reference in the SOW which was the source of the requirement for this contract data item.

22
If the 'CCB member name' (sequence 16) is blank, this field must be blank.

102
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

b. Enter the cut-off date for collecting information for inclusion in this data submittal. Express this either as a
calendar date, or as an interval of time before or after a specific contractual event.

c. Enter the initial submittal due date for this data submittal. For subpacket 6C2, express this either as a calendar
date, or as the appropriate code. For subpacket 6C4, express this either as a calendar date, or as an interval of
time before or after a specific contractual event.

d. Enter the subsequent submittal due date for this data submittal. For subpacket 6C2, express this either as a
calendar date, or as the appropriate code. For subpacket 6C4, express this either as a calendar date, or as an
interval of time before or after a specific contractual event.

e. For the first submittal of a document (or set of documents) as required by a CDRL item, enter a dash (-). Each
time this document is corrected and resubmitted as part of the same approval cycle for the document, enter a
sequentially assigned letter (for example: A, B, C, etc., except that the letter 'O' will not be used). If a later
revision of the document is submitted to start a new approval cycle, a dash (-) should be used.

f. For subpacket 6C1 enter the addressee of the contract and the number of copies to be delivered.

g. For subpackets 6C2 and 6C5, enter the customer technical office responsible for the technical review and
disposition of the data item document, the method/medium of delivery of the data, and the number of copies to be
delivered by this method/medium.

103
MIL-STD-2549
Data Information Packet 6

Table DIP6-IV: Contract/contract data item data information subpackets

Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6C1 6C2 6C3 6C4 6C5
1 Contract identifier M M M M M 950.CONIDN950 or Appendix C, DED 0015 and for 6C2
961.CONIDN95023 only: DoD 5010.12-M instructions for
DD Form 1423 Block A.

2 Contract modification M M M M 951.CONMOD951 Appendix. C, DED 0120

3 Contract name O 950.CONNAM950 Appendix. C, DED 0071
4 Contract type code O 950.FEETYP950 Appendix. C, DED 0227

5 Performing activity enterprise identifier M 950.SELENT950 The transmitted field must be 30

characters, left justified, and consisting
of either a CAGE code (Appendix C,
DED 0001, an organization acronym
(Appendix C, DED 0002), or a
company name (Appendix C, DED
0170).

6 Performing activity Point of Contact (POC) name O 950.SELNAM950 Appendix. C, DED 0069
24
7 Performing activity Point of Contact (POC) address O 950.SELADD950 Appendix. C, DED 0081

8 ACO name O 950.ACONAM950 Appendix. C, DED 0069

9 ACO address O25 950.ACOADD950 Appendix. C, DED 0081

10 PCO name O 950.PCONAM950 Appendix. C, DED 0069
26
11 PCO address O 950.PCOADD950 Appendix. C, DED 0081

12 Contract/modification effective date M 951.CONDAT951 Appendix. C, DED 0082

13 Modification description O 951.CONDES951 Appendix. C, DED 0140

14 Contract period of performance in months M 951.PERIOD951 Appendix. C, DED 0145

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

23
For subpacket 6C3: Use the Tag that starts with 961:
For all other subpackets: Use the Tag that starts with 950.
24
The value of 'performing activity point of contact address' (sequence 7) must be blank if the value of 'performing activity point of contact name' (sequence 6) is blank.
25
The value of 'ACO address' (sequence 9) must be blank if the value of 'ACO name' (sequence 8) is blank.
26
The value 'PCO address' (sequence 11) must be blank if the value of 'PCO name' (sequence 10) is blank.

104
MIL-STD-2549
Data Information Packet 6

Table DIP6-IV: Contract/contract data item data information subpackets

Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6C1 6C2 6C3 6C4 6C5
15 Modification affect on delivery schedule O 951.CONAFF951 Appendix. C, DED 0198
16 Modification affect on schedule A O 951.SCHAAF951 Appendix. C, DED 0198

17 Modification affect on schedule B O 951.SCHBAF951 Appendix. C, DED 0198

18 Modification affect on schedule C O 951.SCHCAF951 Appendix. C, DED 0198

19 Modification affect on schedule D O 951.SCHDAF951 Appendix. C, DED 0198
20 Modification affect on schedule E O 951.SCHEAF951 Appendix. C, DED 0198

21 Modification affect on schedule F O 951.SCHFAF951 Appendix. C, DED 0198

22 Modification affect on schedule G O 951.SCHGAF951 Appendix. C, DED 0198

23 Modification affect on schedule H O 951.SCHHAF951 Appendix. C, DED 0198

24 Modification affect on schedule I O 951.SCHIAF951 Appendix. C, DED 0198

25 Modification affect on schedule J O 951.SCHJAF951 Appendix. C, DED 0198
26 Modification affect on schedule K O 951.SCHKAF951 Appendix. C, DED 0198

27 Modification affect on CDRL O 951.CDRLAF951 Appendix. C, DED 0198

28 Modification affect on address list O 951.CDADAF951 Appendix. C, DED 0198

29 Modification affect on Statement of Work O 951.SOWAFF951 Appendix. C, DED 0198

30 Modification affect on other attachments O 951.OATTAF951 Appendix. C, DED 0198

31 Modification affect on other exhibits O 951.OTEXAF951 Appendix. C, DED 0198

32 Modification affect on distribution statement O 951.DISSAF951 Appendix. C, DED 0198

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

27
33 Contract line item number (CLIN) O M O 959.CLINUM959 or Appendix C, DED 0017
958.CLINUM95928

27
Repeat the series of fields: 'Contract line item number', 'CLIN description', 'CLIN quantity & unit of measure', and 'Contract exhibit identifier' (sequence 33 through 36) as necessary.
28
If 'Contract exhibit identifier' (sequence 36) is nonblank, use the Tag that starts with 958, otherwise, use the Tag that starts with 959.

105
MIL-STD-2549
Data Information Packet 6

Table DIP6-IV: Contract/contract data item data information subpackets

Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6C1 6C2 6C3 6C4 6C5
28 29
34 CLIN description O 959.CLINDS959 Appendix C, DED 0109
28 29
35 CLIN quantity & unit of measure O 959.CLINQT959 and Appendix C, DED 0144 and 0054
959.UOMCOD959
3628 Contract exhibit identifier O M M M 952.CONEXH952 or Appendix C, DED 0007 and for 6C2
958.CONEXH95230 only: DoD 5010.12-M instructions for
DD Form 1423 Block B
37 CI identifier (DD 1423 Block D) O 952.CIIDEN695 Appendix C, DED 0111

38 CDRL form preparation date (DD 1423 Block H) O 952.PREPDT952 Appendix C, DED 0082

39 CDRL form preparer (DD 1423 Block G) O 952.PREPNM952 Appendix C, DED 0069
40 CDRL form approval date (DD 1423 Block J) O 952.APPRDT952 Appendix C, DED 0082

41 CDRL form approver (DD 1423 Block I) O 952.APPRNM952 Appendix C, DED 0069

42 CDRL form category code (DD 1423 Block C) O 952.CDRLCT952 Appendix C, DED 0201

43 CDRL sequence number (DD 1423 Block 1) M M M 953.CDRLIN953 Appendix C, DED 0005

44 CDRL line item revision indicator O 953.SUFXCD953 Appendix C, DED 0205

45 Title of data item (DD 1423 Block 2) M M M 953.CDR020953 or Appendix C, DED 0008
954.SUBTIT95431

46 Subtitle of data item (DD 1423 Block 3) O 953.CDR030953 Appendix C, DED 0008

47 Data Item Description identifier (DD 1423 Block 4) O 953.CDR040953 Appendix C, DED 0230
48 Contract or statement of work reference (DD 1423 Block O 953.SOWIDN957 Appendix C, DEDs 0075 and 0229, and
5) and/or DIP6.2.3.1.a
953.CDR05095332
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

29
Must be blank if 'Contract line item number' (sequence 33) is blank.
30
If 'Contract line item number' (sequence 33) is nonblank, use the Tag that starts with 958, otherwise use the Tag that starts with 952.
31
For subpackets 6C2 and 6C4: Use the Tag that starts with 953.
For subpacket 6C5: Use the Tag that starts with 954.
32
For a contract reference, use 953.CDR050953 only; for a SOW reference, use both fields.

106
MIL-STD-2549
Data Information Packet 6

Table DIP6-IV: Contract/contract data item data information subpackets

Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6C1 6C2 6C3 6C4 6C5
49 Requiring office/Technical monitor (DD 1423 Block 6) O O O 953.CDR060953 or Appendix DED 0228
954.TSKTEK95433

50 Contractor POC office O 954.PRFTEK954 Appendix C, DED 0228

51 DD 250 Requirement code (DD 1423 Block 7) O 953.CDR070953 Appendix C, DED 0202

52 Approval requirement code (DD 1423 Block 8) O 953.CDR080953 Appendix C, DED 0203

53 Distribution statement requirement (DD 1423 Block 9) M 953.DISCOD014 Appendix C, DED 0014
54 Frequency of submittal (DD 1423 Block 10) O 953.CDR100953 Appendix C, DED 0197
55 As of Date for submittals (DD 1423 Block 11) O M 953.CDR11D953 or Appendix C, DEDs 0082 and 0161, and
953.CDR11T953 or DIP6.2.3.1.b
954.COFFDT954 or
954.COFFDL95434

56 Date of first submission (DD 1423 Block 12) O M 953.CDR12C953 or Appendix C, DEDs 0082, 0233, and
953.CDR12D953 or 0234, and DIP6.2.3.1.c
954.INDUDL954 or
954.INDUDT95435

57 Date of subsequent submission (DD 1423 Block 13) O O36 953.CDR13C953 or Appendix C, DEDs 0082, 0233, and
953.CDR13D953 or 0234, and DIP6.2.3.1.d
954.SBDUDL954 or
954.SBDUDT95437
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

33
For subpacket 6C2: Use the Tag that starts with 953.
For subpackets 6C4 and 6C5: Use the Tag that starts with 954.
34
For subpacket 6C2: Use either 953.CDR11D953 or 953.CDR11T953
For subpacket 6C4: Use either 954.COFFDT954 or 954.COFFDL954.
35
For subpacket 6C2: Use either 953.CDR12C953 or 953.CDR12D953.
For subpacket 6C4: Use either 954.INDUDT954 or 954.INDUDL954.
36
If the value of 'CDRL submittal type code' (sequence 70) is 'F', this field must be blank.
37
For subpacket 6C2: Use either 953.CDR13C953 or 953.CDR13DT953.
For subpacket 6C4: Use either 954.SBDUDT954 or 954.SBDUDL954.

107
MIL-STD-2549
Data Information Packet 6

Table DIP6-IV: Contract/contract data item data information subpackets

Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6C1 6C2 6C3 6C4 6C5
58 CDRL Remarks (DD 1423 Block 16) O O O 953.CDR160953 or For 6C2: Appendix. C, DED 0204; For
954.SUBRMK954 or 6C4 and 6C5: Appendix C, DED 0153
955.SUBCOM95538

59 CDRL price group (DD 1423 Block 17) O 953.CDR170953 Appendix C, DED 0199
60 Estimated CDRL price (DD 1423 Block 18) O 953.CDR180953 Appendix C, DED 0200

61 CDRL item submittal number M M M 954.CDRLSB954 Appendix C, DED 0020

62 CDRL item submittal revision D D M 955.SUBREV955 Appendix C, DED 0099 and

DIP6.2.3.1.e
63 Revised submittal due date O39 955.SUBDUE955 Appendix C, DED 0082

64 Contract/CDRL submittal addressee/reviewing office O O M 962.DIVADD942 or Appendix C, DED 0081 and for 6C1:
963.FILADD96340 DIP6.2.3.1.f; for 6C2 and 6C5:
DIP6.2.3.1.g and DoD 5010.12-M
instructions for DD Form 1423, Block
14a and 14b.
65 Document delivery method O M 964.DELMTH964 Appendix C, DED 0139 and
DIP6.2.3.1.g

66 Quantity of documents to be delivered O O M 962.DOCQTY962 or Appendix C, DED 0158 and for 6C1:
964.DOCQTY96441 DIP6.2.3.1.f; for 6C2 and 6C5:
DIP6.2.3.1.g and DoD 5010.12-M
instructions for DD Form 1423, Block
14a and 14b.
67 Contract event code M O 961.EVNCOD961 Appendix. C, DED 0018
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

38
For subpacket 6C2: Use the Tag that starts with 953.
For subpacket 6C4: Use the Tag that starts with 954.
For subpacket 6C5: Use the tag starting with 955 unless 'CDRL item submittal rivision' (sequence 62) has a value of dash ('-'), in which case the tag starting with 954 should be used.
39
Mandatory if the value of 'CDRL item submittal revision' (sequence 62) is not dash ('-'); otherwise, it this field must be blank.
40
For subpacket 6C1: Use the Tag that starts with 962.
For subpackets 6C2 and 6C5: Use the Tag that starts with 963.
41
For subpacket 6C1: Use the Tag that starts with 962.
For subpackets 6C2 and 6C5: Use the Tag that starts with 964.

108
MIL-STD-2549
Data Information Packet 6

Table DIP6-IV: Contract/contract data item data information subpackets

Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6C1 6C2 6C3 6C4 6C5
68 Contract event name M 961.PRSNAM961 Appendix. C, DED 0156
69 Contract event start date M 961.PRSSDT961 Appendix. C, DED 0082

70 Contract event completion date M 961.PRSEDT961 Appendix. C, DED 0082

71 CDRL submittal type code M M 954.SUBTYP954 Appendix. C, DED 0150

72 Data submittal status M 956.SUBSTA956 Appendix. C, DED 0021
73 Data submittal status code M 956.STATDT956 Appendix. C, DED 0082

74 Data submittal submitter name M 956.DISNAM956 Appendix. C, DED 0069

42
75 Customer final disposition suspense date O 970.FSUSDT970 Appendix. C, DED 0082
42
76 Document source M 965.SRCIDN010 The transmitted field must be 36
characters, left justified and consisting
of either a CAGE code (Appendix C,
DED 0001), an organization acronym
(Appendix C, DED 0002), a company
name (Appendix C, DED 0170), or an
author's name (Appendix C, DED
0069).

7742 Document identifier M 965.DOCIDN010 Appendix. C, DED 0122

42
78 Document type code M 965DOCTYP010 Appendix. C, DED 0004
42
79 Document revision M 965.DOCREV011 Appendix. C, DED 0009
42
80 Document representation identifier M 966.REPIDN800 or Appendix. C, DED 0207
861.REPIDN80043

8142 Document representation revision level M 966.REPREV801 or Appendix. C, DED 0208

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

861.REPREV80141
82- Document representation M See Data Information Data Information Packet 10
12242 Subpacket 10B

42
Repeat the series sequence 75 through 122 for each document included in the data item submittal.
43
If this document is being submitted to the CDCA for the document or by the CDCA of the document, use the Tag that starts with 966; if it is being submitted by an application activity, use the Tag that starts
with 861.

109
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

DIP6.2.4 Subpackets 6D1 and 6D2. Provide the information as required by Table DIP6-V.

DIP6.2.4.1 Content instructions for subpackets 6D1 through 6D8.

a. Enter the identification of the specific contract and CDRL submittal under which this document is being reviewed.

b. Enter the complete identification of the document revision being reviewed or dispositioned.

c. Enter the identification of the document representation associated with the document revision identified in
sequence 7-10 that is being reviewed or dispositioned.

d. Enter the identification of the specific file which is part of the document representation identified in sequence 11-
12 and for which comments are being submitted. If there are no comments against a file which is part of the
document representation, do not include these fields.

e. Enter the identification of the specific file which contains the reviewer's comments against the file identified in
sequence 53-56.

f. If this review or disposition is being performed by an application activity, enter the application activity.

g. Enter the suspense date for technical reviewers to complete their review.

DIP6.2.4.2 Constants. The following fields associated with the subpackets indicated are necessary to properly populate
the DOD CSA database, but have the constant value indicated. Because they have constant values, they do not have to
be transmitted as part of the information subpacket.

DIP6.2.4.2.1 Subpacket 6D1. Document representation release status code (811.REPSTA803) must be 'REVW'.

DIP6.2.4.2.2 Subpacket 6D2.

a. If this review is part of the CDCA document approval process, the value of the document approval status code
(857.SUBSTA852) must be 'SUBMIT' and the value of the document representation release status code
(858.REPSTA803) must be 'RLSE'.

b. If this review is part of the application activity document adoption process, the value of the document approval
status code (867.AREVST861) must be 'SUBMIT' and the value of the document representation release status
code (867.REPSTA803) must be 'RLSE'.

DIP6.2.4.2.3 Subpacket 6D3. The value of the data item submittal approval status code (968.SUBSTA956) must be
'SUBMIT'.

DIP6.2.4.2.4 Subpacket 6D5. If this disposition is part of the CDCA approval process, the value of the document
representation status code (806.REPSTA803) must be 'RLSE'.

110
MIL-STD-2549
Data Information Packet 6

Table DIP6-V. Document/CDRL review, disposition, and direction data information subpackets
Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6D1 6D2 6D3 6D4 6D5 6D6 6D7 6D8
1 Contract identifier M M 968.CONIDN950 DIP6.2.4.1.a and Appendix C,
DED 0015
2 Contract modification M M 968.CONMOD951 DIP6.2.4.1.a and Appendix C,
DED 0120
3 Contract exhibit identifier M M 968.CONEXH952 DIP6.2.4.1.a and Appendix C,
DED 0007
4 CDRL sequence identifier M M 968.CDRLIN953 DIP6.2.4.1.a and Appendix C,
DED 0005
5 Data submittal identifier M M 968.CDRLSB954 DIP6.2.4.1.a and Appendix C,
DED 0020

6 Data submittal revision M M 968.SUBREV955 DIP6.2.4.1.a and Appendix C,

DED 0099
744 Document source identifier M M M M M M M M 250.ECPCAG250 or 294.ECPCAG250 or DIP6.2.4.1.b amd Table B-I. The
373.RFDCAG350 or 704.SRCCAG022 or transmitted field must be 36
803.SRCIDN010 or 812.SRCIDN010 or characters, left justified and
850.SRCIDN010 or 858.SRCIDN010 or consisting of either a CAGE code
861.SRCIDN010 or 867.SRCIDN010 or (Appendix C, DED 0001), an
966.SRCIDN010 or 967.SRCIDN010 or organization acronym (Appendix
968.SRCIDN01045 C, DED 0002), a company name
(Appendix C, DED 0170), or the
author's name (Appendix C, DED
0069).

44
For subpackets 6D3 and 6D6: Repeat the series of fields that identifies the specific document and document representation (sequence 7 through 52) in the data item submittal for each document included in
the data item submittal package.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

45
For subpacket 6D1 (originating organization review prior to initial release of the document representation): Use the Tag that starts with 812.
For subpacket 6D2: (a) For CDCA review of the document representation as part of the document revision approval process, use the Tag that starts with 858.
(b) For Application Activity review of the document representation as part of the document revision adoption process, use the Tag that starts with 867.
For subpacket 6D3 (review of document by tasking activity in conjunction with data item submittal approval process): Use the Tag that starts with 968.
For subpacket 6D4: Use the Tag that starts with 803.
For subpacket 6D5: (a) For CDCA disposition of the document as part of the document revision approval process, use the Tag that starts with 850 except if the value of 'document type code' (sequence 9)
is 'ECP', in which case, use the Tag that starts with 294, and the case where the value of sequence 9 is 'RFD', in which case use the Tag that starts with 373.
(b) For Application Activity disposition of the document as part of the document revision adoption process, use the Tag that starts with 861.
For subpacket 6D6: (a) For data item approval of a document for which the tasking activity is the CDCA of the document, use the Tag that starts with 966.
(b) For data item approval of a document for which the tasking activity is an application activity for the document, use the Tag that starts with 967.
For subpacket 6D7: Use the Tag that starts with 704.
For subpacket 6D8: Use the Tag that starts with 250.

111
MIL-STD-2549
Data Information Packet 6

Table DIP6-V. Document/CDRL review, disposition, and direction data information subpackets
Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6D1 6D2 6D3 6D4 6D5 6D6 6D7 6D8
844 Document identifier M M M M M M M M 250.ECPNUM250 or 294.ECPNUM250 or DIP6.2.4.1.b and Table B-I. The
373.RFDNUM350 or 704.DOCNUM020 transmitted field must be 240
or 803.DOCIDN010 or 812.DOCIDN010 characters, left justified and
or 850.DOCIDN010 or 858.DOCIDN010 consisting of either an
or 861.DOCIDN010 or 867.DOCIDN010 alphanumeric identifier (Appendix
or 966.DOCIDN010 or 967.DOCIDN010 C, DED 0003) or a title (Appendix
or 968.DOCIDN01045 C, DED 0008).

944 Document type code M M M M M M M M 250.ECPTYP250 or 294.ECPTYP250 or DIP6.2.4.1.b, Table B-I, and
373.RFDTYP350 or 704.DOCTYP010 or Appendix C, DED 0004
803.DOCTYP010 or 812.DOCTYP010 or
850.DOCTYP010 or 858.DOCTYP010 or
861.DOCTYP010 or 867.DOCTYP010 or
966.DOCTYP010 or 967.DOCTYP010 or
968.DOCTYP01045

1044 Document revision M M M M M M M M 251.ECPREV251 or 294.ECPREV251 or DIP6.2.4.1.b. For Tags starting

373.RFDREV351 or 704.DOCREV011 or with 251, 294, or 373 , see
801.DOCREV011 or 850.DOCREV011 or Appendix C, DED 0009. For all
858.DOCREV011 or 861.DOCREV011 or other tags, the transmitted field
867.DOCREV011 or 956.DOCREV011 or must be 8 characters, left justified
965.DOCREV01146 and consist of either an
alphanumeric revision (Appendix
C, DED 0009), a date (Appendix
C, DED 0082), a software version
(Appendix C, DED 0062),or a
technical manual change identifier
(Appendix C, DED 0134), as
appropriate for the document type.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

46
For subpackets 6D1 and 6D4: Use the Tag that starts with 801.
For subpacket 6D2: (a) For CDCA review of the document representation as part of the document revision approval process, use the Tag that starts with 858.
(b) For Application Activity review of the document representation as part of the doucment adoption process, use the Tag that starts with 867.
For subpacket 6D3: Use the Tag that starts with 965.
For subpacket 6D5: (a) For CDCA disposition of the doument as part of the documetn revision approval process, use the Tag that starts with 850, except in the case where the value of 'document type
code' (sequence 9) is 'ECP', in which case, the Tag that starts with 294 should be used, and the case where the value of sequence 9 is 'RFD', in which case the Tag that starts with
373 should be used.
(b) For Application Activity disposition of the document as part of the document adoption process, use the Tag that starts with 861.
For subpacket 6D6: Use the Tag that starts with 965.
For subpacket 6D7: Use the Tag that starts with 704.
For subpacket 6D8: Use the Tag that starts with 251.

112
MIL-STD-2549
Data Information Packet 6

1244 Document representation M M M M M M 803.REPREV801 or 806.REPREV801 or DIP6.2.4.1.c and Appendix C,

revision 812.REPREV801 or 858.REPREV801 or DED 0208
861.REPREV801 or 867.REPREV801 or
966.REPREV801 or 968.REPREV80145

1344 Document representation M 806.RELTYP806 Appendix C, DED 0216

release type code

1444 Document representation O 906.RELLIM806 Appendix C, DED 0217

relsease restrictions

15- Document representation M M See Data Information Subpacket 10C DIP6.2.4.1.c and Data Information
5244 Packet 10

5348 File name O49 O49 O49 812.RFILID812 or 858.RFILID858 or DIP6.2.4.1.d and Appendix C,
867.RFILID867 or 968.RFILID96850 DED 0206

47
For subpacket 6D1: Use the Tag that starts with 812.
For subpacket 6D2: (a) For CDCA review of the document representation as part of the document approval process, use the Tag that starts with 858.
(b) For Application activity review of the document as part of the document adoption process, use the Tag that starts with 867.
For subpacket 6D3: Use the Tag that starts with 968.
For subpacket 6D4: Use the Tag that starts with 803.
For subpacket 6D5: (a) For CDCA document approval process, use the Tag that starts with 806
(b) For Application activity document adoption process, use the Tag that starts with 861.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

For subpacket 6D6: (a) If the tasking activity is the CDCA for the document, use the Tag that starts with 966
(b) If the tasking activity is an application activity, use the Tag that starts with 861.
48
For subpacket 6D1, 6D2, and 6D3: Repeat the series of fields which identifies the document file being reviewed and the associated comment file as necessary for each file which is part of the document
representation being reviewed (sequence 51 through 59). This series must be either all nonblank, or all blank.
49
Must be blank if document representation identified in sequence 11 and 12 is paper, stable base material, punch cards, video tape,on-line database, etc.; must be nonblank for all types of digital
representations.
50
For subpacket 6D1: Use the Tag that starts with 812.
For subpacket 6D2: If the CDCA is reviewing the document representation as part of the document approval process, use the Tag that starts with 858; if an application activity is reviewing the document as
part of the document adoption process, use the Tag that starts with 867.
For subpacket 6D3: Use the Tag that starts with 968.

113
MIL-STD-2549
Data Information Packet 6

Table DIP6-V. Document/CDRL review, disposition, and direction data information subpackets
Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6D1 6D2 6D3 6D4 6D5 6D6 6D7 6D8
5448 File originator name O51 O51 O51 812.RFILOR812 or 858.RFILOR858 or DIP6.2.4.1.d and Appendix C,
867.RFILOR867 or 968.FILORG96850 DED 0069
5548 File originator office O51 O51 O51 812.RFILAD912 or 858.RFILAD858 or DIP6.2.4.1.d and Appendix C,
867.RFILAD867 or 968.RFILAD96850 DED 0081
5648 File creation date & time O51 O51 O51 812.RFILDT812 and 812.RFILTM812, or DIP6.2.4.1.d and Appendix C,
858.RFILDT858 and 858.RFILTM858, or DEDs 0082 and 0160
867.RFILDT867 and 867.RFILTM867, or
968.RFILDT968 and 968.RFILTM96850

5748 Comment file name O51 O51 O51 812.CFILID812 or 858.CFILID858 or DIP6.2.4.1.e and Appendix C,
867.CFILID867 or 968.CFILID96850 DED 0206
5848 Comment file originator O52 O52 O52 812.CFILOR812 or 858.CFILOR858 or DIP6.2.4.1.e and Appendix C,
name 867.CFILOR867 or 968.CFILOR96850 DED 0069

5948 Comment file originator O52 O52 O525 812.CFILAD812 or 858.CFILAD858 or DIP6.2.4.1.e and Appendix C,
office 867.CFILAD867 or 968.CFILAD96850 DED 0081
6048 Comment file creation date & O O O 812.CFILDT812 and 812.CFILTM812, or DIP6.2.4.1.e and Appendix C,
time 858.CFILDT858 and 858.CFILTM858, or DEDs 0082 and 0160
867.CFILDT867 and 867.CFILTM867, or
968.CFILDT968 and 968.CFILTM96850

6148 Comment file information O O O See Data Information Subpacket 9B DIP6.2.4.1.e and Data Information
Packet 9

62 Application activity identifier O O O O 861.APPACT033 or 867.APPACT033 or DIP6.2.4.1.f and Appendix C,

967.APPACT03353 DED 0228
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

51
This is a paired field with sequence 53; either both must be blank, or both must be nonblank .
52
This is a paired field with sequence 57; either both must be blank, or both must be nonblank.
53
For subpacket 6D2: Use the Tag that starts with 867.
For subpackets 6D3 and 6D6: Use the Tag that starts with 967.
For subpacket 6D4: Use the Tag that starts with 861.

114
MIL-STD-2549
Data Information Packet 6

Table DIP6-V. Document/CDRL review, disposition, and direction data information subpackets
Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6D1 6D2 6D3 6D4 6D5 6D6 6D7 6D8
63 CCB convening enterprise M 704.ENTIDN002 The transmitted field must be 30
identifier characters, left justified and
cosisting of either a CAGE code
(Appendix C, DED 0001), an
organization acronym (Appendix
C, DED 0002) or a company name
(Appendix C, DED 0170).
64 Program/project/system name M 704.PROGNM691 Appendix C, DED 0059

65 CCB name M 704.CCBNAM700 Appendix C, DED 0151

66 Technical review-- M M M 811.TECHCD811 or 857.TECHCD857 or Appendix C, DED 0021
recommended disposition 866.TECHCD866 or 968.TECHCD96854

67 Technical review (of O O O 811.TECHDT811 or 857.TECHDT857 or DIP6.2.4.1.g and Appendix C,

document representation/ 866.TECHDT866 or 968.TECHDT96855 DED 0082
document) completion date

68 Disposition status code M M M M M 251.ECP27C251 or 294.REVSTA850 or Appendix C, DED 0021

373.REVSTA850 or 704.CCBSTA704 or
803.REPSTA803 or 850.REVSTA850 or
861.AREVST861 or 956.SUBSTA95656

54
For subpacket 6D1: Use the Tag that starts with 811.
For subpacket 6D2: For CDCA review of the document representation as part of the document revision approval process, use the Tag that starts with 857; for Application Activity review of the document
representation as part of the document revision adoption process, use the Tag that starts with 866.
For subpacket 6D3: Use the Tag that starts with 968.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

55
For subpacket 6D4: Use the Tag that starts with 811.
For subpacket 6D5: For CDCA review of the document representation as part of the document revision approval process, use the Tag that starts with 857; for Application Activity review of the document
representation as part of the document revision adoption process, use the Tag that starts with 866.
For subpacket 6D6: Use the Tag that starts with 968.
56
For subpacket 6D4: Use the Tag that starts with 803.
For subpacket 6D5: (a) If the disposition action is part of the CDCA document approval process, use the Tag that starts with 850 except if the value of 'document type code' (sequence 9) is 'ECP', in
which case, the Tag that starts with 294 should be used, or if the value of sequence 9 is 'RFD', in which case the Tag that starts with 373 should be used.
(b) If the disposition action is part of the application activity document adoption process, use the Tag that starts with 861.
For subpacket 6D6: Use the Tag that starts with 956.
For subpacket 6D7: Use the Tag that starts with 704.
For subpacket 6D8: Use the Tag that starts with 251.

115
MIL-STD-2549
Data Information Packet 6

Table DIP6-V. Document/CDRL review, disposition, and direction data information subpackets
Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6D1 6D2 6D3 6D4 6D5 6D6 6D7 6D8
69 Disposition status date M M M M M M 251.ECP27F251 or 294.STADAT850 or Appendix C, DED 0082
373.STADAT850 or 704.CCBDAT704 or
803.RELDAT803 or 850.STADAT850 or
861.AREVDT861 or 858.SUBDAT852 or
867.AREVDT861 or 956.STATDT95657

70 Name of person placing M M M M 251.ECP27E251 or 803.DISPNM803 or Appendix C, DED 0069

document representation/ 850.PERNAM850 or 861.PERNAM861 or
document/data item in 956.DISNAM95658
specified status

71 Address of person placing M M M 251.ECP27D251 or 803.DIVADD942 or Appendix C, DED 0081

document representation/ 850.DIVADD942 or 861.DIVADD94259
document/data item in
specified status

72 Data item resubmittal O60 972.RSUBRQ972 Appendix C, DED 0159

requirement code

73 Source of data item O61 956.RSUBSR956 Appendix C, DED 0235

resubmittal requirement

57
For subpacket 6D2: For review by the CDCA, use the Tag that starts with 858; for review by an application activity, use the Tag that starts with 867.
For subpacket 6D4: Use the Tag that starts with 803.
For subpacket 6D5: (a) If the disposition action is part of the CDCA document approval process, use the Tag that starts with 850 except if the value of 'document type code' (sequence 9) is 'ECP', in
which case, the Tag that starts with 294 should be used, or if the value of sequence 9 is 'RFD', in which case the Tag that starts with 373 should be used.
(b) If the disposition action is part of the application activity document adoption process, use the Tag that starts with 861.
For subpacket 6D6: For disposition of the data item as part of the data item approval process, use the Tag that starts with 956.
For subpacket 6D7: Use the Tag that starts with 704.
For subpacket 6D8: Use the Tag that starts with 251.
58
For subpacket 6D4: Use the Tag that starts with 803.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

For subpacket 6D5: If the disposition is part of the CDCA document approval process, use the Tag that starts with 850; if it is part of the application activity document adoption process, use the Tag that
starts with 861.
For subpacket 6D6: Use the Tag that starts with 956.
For subpacket 6D8: Use the Tag that starts with 251.
59
For subpacket 6D4: Use the Tag that starts with 803.
For subpacket 6D5: If the disposition is part of the CDCA document approval process, use the Tag that starts with 850; if it is part of the application activity document adoption process, use the Tag that
starts with 861.
For subpacket 6D8: Use the Tag that starts with 251.
60
Mandatory if the value of the data item approval status (sequence 68) is 'DISAPV'; otherwise, must be blank.
61
Mandatory if the value of 'Data submittal revision' (sequence 6) is not "-"; otherwise, must be blank.

116
MIL-STD-2549
Data Information Packet 6

Table DIP6-V. Document/CDRL review, disposition, and direction data information subpackets
Seq Field name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6D1 6D2 6D3 6D4 6D5 6D6 6D7 6D8
74 Process next status suspense O O O O M62 803.NSTATD803 or Appendix C, DEDs 0082 and 0159
date 850.NXSTDT850 or
861.NSTATD861 or
970.FSUSDT970 and 970.TSUSDT970, or
972.RSUBRQ972 and 972.RSUBDT97263

75 CCB minutes O 704.CCBMIN Appendix C, DED 0168 (See also:

Data Information Subpacket 5A.)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

62
The entry for 972.RSUBDT972 must be blank unless the value of 972.RSUBRQ972 is 'Y', in which case, it must be nonblank.
63
For subpackets 6D1 and 6D4: Use the Tag that starts with 803.
For subpackets 6D2 and 6D5: If this disposition is part of the CDCA document approval process, use the Tag that starts with 850; if it is part of the application activity document adoption process, use the
Tag that starts with 861.
For subpacket 6D6: If the value of the data item approval process status (sequence 66) is 'SUBMIT', use the Tag that starts with 970; if the value is 'DISAPV', use the Tag that starts with 972.

117
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

DIP6.2.5 Subpackets 6E1, 6E2, and 6E3. Provide the information as required by Table DIP6-VI.

TABLE DIP6-VI. Baseline, CPIN, PAN data information subpackets

Seq Field name Data Information Data Element Tag For content and
# Subpacket validation instructions,
see
6E1 6E2 6E3
1 Baseline type code M DIP6E1.1 Appendix C, DED 009864
2 Program/project/system name O65 330.PROGNM691 Appendix C, DED 0059

3 Contract identifier O66 332.CONIDN950 Appendix C, DED 0015

66
4 Contract modification O 332.CONMOD951 Appendix C, DED 0120
67
5 Configuration item identifier O 331.CIIDEN695 Appendix C, DED 0111
68
6 Product baseline top-level O 331.PBLDOC331 or Appendix C, DED 0124
document 332.PBLDOC33169

7 Document/software source O70 O71 M 100.DESCAG100 or For Tags that start with 100,
194.SWSORC170 or 671, or 672: Appendix C,
330.SRCIDN010 or DED 0001. For all other
332.SRCIDN010 or Tags: the transmitted field
671.ECPCAG250 or must be 36 characters, left
672.RFDCAG35072 justified and consisting of
either a CAGE code
(Appendix C, DED 0001), an
organization acronym
(Appendix C, DED 0002), a
company name (Appendix C,
DED 0170), or an author's
name (Appendix C, DED
0069).

64
Enter the code for the type of baseline being addressed. This element is not entered into the DOD CM AIS anywhere as a result of this data
information subpacket, but is required to validate the completeness of the subpacket and to determine what fields are to be populated with the
other information provided in the subpacket.
65
Mandatory if the value of 'Baseline type code' (sequence 1) is 'T'; must be blank for all other values of 'Baseline type code'.
66
Mandatory if the value of 'Baseline type code' (sequence 1) is 'C'; must be blank for all other values of 'Baseline type code'.
67
Mandatory if the value of 'Baseline type code' (sequence 1) is 'P'; mandatory if the value of the 'Baseline type code' is 'C' and the value of 'Product
baseline top-level document' (sequence 6) is nonblank; must be blank for all other cases.
68
Mandatory if the value of 'Baseline type code' (sequence 1) is 'P'; optional if the value of 'Baseline type code' (sequence 1) is 'C'; must be blank for
all other values of 'Baseline type code'.
69
If the value of 'Baseline type code' (sequence 1) is 'P', use the Tag that starts with 331; if the value is 'C', use the Tag that starts with 332.
70
Must be blank if the value of 'Baseline type code' (sequence 1) is 'P'; mandatory for all other values of 'Baseline type code'.
71
Mandatory if the value of the software-product-united-states-air-force--assigned-applicability-code is 'A'; must be blank for all other values of the
software-product-united-states-air-force--assigned-applicability-code. (The software-product-united-states-air-force--assigned-applicability-code
is embedded in the CPIN [sequence 11]; see Appendix C, DEDs 0236 and 0237.)
72
For subpacket 6E1: (a) If the value of the 'Baseline type code' (sequence 1) is 'A' or 'F', use the Tag that starts with 100.
(b) If the value of the 'Baseline type code' (sequence 1) is 'C', use the Tag that starts with 332.
(c) If the value of the 'Baseline type code' (sequence 1) is 'T', use the Tag that starts with 330.
For subpacket 6E2: Use the Tag that starts with 194.
For subpacket 6E3: If the value of 'Document/media type code' (sequence 9) is 'ECP', use the Tag that starts with 250; if it is 'RFD', use the Tag
that starts with 350.

118
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

TABLE DIP6-VI. Baseline, CPIN, PAN data information subpackets

Seq Field name Data Information Data Element Tag For content and
# Subpacket validation instructions,
see
6E1 6E2 6E3
8 Document/software identifier O70 O71 M 100.DOCNUM020 or For Tag 194.SWIDEN170:
194.SWIDEN170 or the transmitted field must be
330.DOCIDN010 or 248 characters, left justified
332.DOCIDN010 or and consisting of either a
671.ECPNUM250 or software alphanumeric
672.RFDNUM35072 identifier (Appendix C, DED
0088), a part number
(Appendix C, DED 0024), or
a software product identifier
(Appendix C, DED 0262).
For all other Tags: Appendix
C, DED 0003.

9 Document/media type code O70 O71 M 100.DOCTYP010 or Appendix C, DEDs 0004 or

194.MEDTYP194 or 0238
330.DOCTYP010 or
332.DOCTYP010 or
671.ECPTYP250 or
672.RFDTYP35072

10 Document revision O73 332.DOCREV011 The transmitted field must be

8 characters, left justified and
consist of either an
alphanumeric revision
(Appendix C, DED 0009), a
date (Appendix C, DED
0082), or a software version
(Appendix C, DED 0062), as
appropriate for the document
type

11 CPIN or PAN M M 190.CPINNO190 or Appendix C, DEDs 0178 or

670.PANNUM67074 0237

12 PAN year of issue M 670.YEARNO670 Appendix C, DED 0219

75
13 First component CPIN O 193.COMPNO193 Appendix C, DED 0237
75
14 Second component CPIN O 193.COMPNO193 Appendix C, DED 0237

DIP6.2.5.1 Constants for subpackets 6E1 througb 6E3. The following fields associated with the subpackets indicated are
necessary to properly populate the DOD CSA database, but have the constant value indicated. Because they have constant
values, they do not have to be transmitted as part of the information subpacket.

DIP6.2.5.1.1 Subpacket 6E1.

a. If the value of 'Baseline type code' (sequence 1) is 'A', the value of 100.ABLFLG100 is 'Y'; otherwise it is 'N'.

73
Mandatory if the value of 'Baseline type code' (sequence 1) is 'C'; must be blank for all other values of 'Baseline type code'.
74
For subpacket 6E2: Use the Tag that starts with 190.
For subpacket 6E3: Use the Tag that starts with 670.
75
Mandatory if the value of software-product-united-states-air-force--assigned-type-code is 'C' or 'D'; must be blank for all other values of the
software-product-united-states-air-force--assigned-type-code. (The software-product-united-states-air-force--assigned-type-code is embedded in
the CPIN (sequence 11); see Appendix C, DEDs 0188 and 0237.)

119
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

b. If the value of 'Baseline type code' (sequence 1) is 'F', the value of 100.FBLFLG100 is 'Y'; otherwise it is 'N'.

DIP6.2.5.1.2 Subpacket 6E3. The value of the 'Document/media type code' (sequence 9) is also entered in
670.DOCTYP670.

DIP6.2.6 Subpackets 6F1 through 6F5. Provide the information as required by Table DIP6-VII.

Table DIP6-VII. Transfer of CDCA/document custodian and changes to AA/GLAA

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6F1 6F2 6F3 6F4
1 Document type code M M M M 010.DOCTYP010 or Table B-I, and Appendix C, DED
033.DOCTYP01076 0004

2 Document source M M M M 010.SRCIDN010 or Table B-I. The transmitted field

033.SRCIDN01077 must be 36 characters, left
justified, and consisting of either a
CAGE code (Appendix C, DED
0001), an organization acronym
(Appendix C, DED 0002), a
company name (Appendix C, DED
0170) or an author's name
(Appendix C, DED 0069).

3 Document identifier M M M M 010.DOCIDN010 or Table B-I, and Appendix C, DED

033.DOCIDN01077 0122

4 Document revision level M M M 011.DOCREV011 Appendix C, DED 0009

5 Current CDCA M M M M 010.CCCENT010 DIP6.2.6.1.a and Appendix C,

DED 0239
6 New CDCA M 010.CCCENT010 DIP6.2.6.1.a and Appendix C,
DED 0239

7 CDCA effective date M 010.CCCADT010 DIP6.2.6.1.b and Appendix C,

DED 0082

8 Current document/software M M 011.CUSORG011 DIP6.2.6.1.c. The transmitted

custodian field must be 36 characters, left
justified and consisting of either a
CAGE code (Appendix C, DED
0001), an organization acronym
(Appendix C, DED 0002), a
company name (Appendix C, DED
0170), or a person's name
(Appendix C, DED 0069).
9 New document/software M 011.CUSORG011 DIP6.2.6.1.c. The transmitted field
custodian must be 36 characters, left justified
and consisting of either a CAGE
code (Appendix C, DED 0001),
an organization acronym
(Appendix C, DED 0002), a
company name (Appendix C, DED
0170), or a person's name
(Appendix C, DED 0069).

10 Add/Change/Delete action M DIP6F4.13 DIP6.2.6.1.d

11 Application Activity M 033.APPACT033 Appendix C, DED 0228
identifier

76
For subpackets 6F1, 6F2, and 6F3: Use the Tag that starts with 010.
For subpacket 6F4: Use the Tag that starts with 033.

120
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 6

Table DIP6-VII. Transfer of CDCA/document custodian and changes to AA/GLAA

Seq Field Name Data Information Subpacket Data Element Tag For content and validation
# instructions, see
6F1 6F2 6F3 6F4
12 Document revision status M M 850.REVSTA850 Appendix C, DED 0021
code

13 Document revision status date M M 850.STADAT850 Appendix C, DED 0082

14- Document representation M M M See Data Information Data Information Packet 10

5177 subpacket Subpacket 10A

52- Document miscellaneous file O78 See Data Information Data Information Packet 9
85 subpacket Subpacket 9A

DIP6.2.6.1 Content instructions for Subpacket 6F1 through 6F3.

a. For subpackets 6F1 through 6F3, the current CDCA of the document is verified. If it matches, the subpacket 6F1
updates the current CDCA of the document.

b. For subpacket 6F1, enter the date that the new CDCA assumes responsibility for the document; for subpacket 6F4,
enter the date the document number was assigned.

c. The current document/software custodian is validated before it is updated with the new document/software
custodian.

d. This element indicates the type of action being reported by this subpacket submittal. The valid entries are:

(1) 'AA' Add a new organization as an Application Activity for the specified document.

(2) 'AB' Add a new organization as an Application Activity for the specified document and identify that AA as
the GLAA.

(3) 'AG' Designate an existing Application Activity as the GLAA.

(4) 'DA' Delete an Application Activity from the list of Application Activities for the specified document.

(5) 'DG' Delete the GLAA responsibility from the Application Activity currently assigned this responsibility.

DIP6.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

77
Repeat this sequence number as necessary to address all affected document representations.
78
Must be blank unless the value of 'document type code' (sequence 1) is 'ECP'.

121
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

(This page intentionally left blank)

122
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 7

Engineering Parts List

DIP7.1. Purpose. Includes the contents of an engineering parts list (regardless of whether it is an integral part of a
drawing, or a separate parts list drawing). It can also be used to create an engineering "structure" if component parts/
materials/software/documents are called out on the face of the drawing without a parts list; however, alternate parts/
material/software will not be matched to preferred parts/material/software unless they sequentially follow the preferred
parts/material/software.

DIP7.1.1 Subpackets. There are two subpackets for this packet:

Subpacket Applicability
7A Contents of integral parts lists or separate parts list drawings
7B Proposed changes to the contents of integral parts list or separate parts list drawings

DIP7.2. Content of data information subpackets. The data information subpackets define the elements and documents/
files to be provided and correlates the information elements with the conceptual CM AIS database described in
Appendices B and C. Within the table, in the column labeled "M/O", the inclusion of the element in the information
subpacket is either mandatory (M) or optional (O). For each subpacket, the various elements shall be provided in the
order shown in Table DIP10-I, except that optional fields (denoted by O) for which data is not being submitted shall be
skipped. Each element shall be preceded by the Data Element Tag as shown in the table. The full field size for the data
element, as shown in Appendix C, shall be used and shall immediately follow the data element tag. No delimiters will be
used between the fields or at the beginning or end of this data subpacket. The last column in the table contains a reference
to the contents of the data element.

TABLE DIP7-I. Engineering parts list

Seq # Field Name M/O Data Element Tag For content and
validation instructions,
Subpacket 7A Subpacket 7B see
2
1
1 Design CAGE code M 302.DESCAG050 DIP7.2.1.a and Appendix C,
DED 0001
2
2 Drawing number M1 302.DWGNUM050 DIP7.2.1.a and Appendix C,
DED 0003
2
3 Document type code M1 302.DOCTYP010 DIP7.2.1.a, DIP7.2.1.b, and
Appendix C, DED 0004
2
4 Document revision M1 302.DOCREV011 DIP7.2.1.a and Appendix C,
DED 0009

53 Find number M 224.FINDID219 315.FINDID315 DIP7.2.1.c and Appendix C,

DED 0027

63 Type of change to find number O1 315.CHGTYP315 DIP7.2.1.d and Appendix C,

DED 0261

1
Only applies to Subpacket 7B.
2
The value of this field in the Data Information Subpacket 1A which invoked this data subpacket should be used. (See also: DIP7.2.2.3.)
3
For subpacket 7A, repeat the series of fields sequence 5 through 25 for each find number in the parts list.
For subpacket 7B, repeat the series of fields sequence 5 through 25 for each find number in the parts list for which there is a proposed change.

123
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 7

TABLE DIP7-I. Engineering parts list

Seq # Field Name M/O Data Element Tag For content and
validation instructions,
Subpacket 7A Subpacket 7B see
73,4 CI nomenclature O 208.CINOMN690 323.CINOMEN690 DIP7.2.1.e and Appendix C,
DED 0047

83,4 Reference Designator O 208.REFDES208 323.REFDES323 DIP7.2.1.f and Appendix C,

DED 0055

93,4 Type of change to reference O1,5 323.CHGTYP323 DIP7.2.1.g and Appendix C,

designator DED 262
103,6 Referenced drawing note number O 226.NOTNUM080 326.NOTNUM325 Appendix C, DED 0251

113,6 Type of change to note number- O1,7 326.CHGTYP326 Appendix C, DED 0261
find number correlation

123,8 Special condition code O 227.SPNOTE227 324.SPNOTE324 Appendix C, DED 0257

133,8 Type of change to special O1,9 324.CHGTYP324 Appendix C, DED 0261

condition code

143,10 Parts list entry sequence number M 224.PLSEQN224 316.PLSEQN316 DIP7.2.1.h and Appendix C,
DED 0259

153,10 Primary/Alternate indicator M 224.ALTFLG224 316.ALTFLG316 DIP7.2.1.i and Appendix C,

DED 0258

163,10 Component type code M 224.COMPTY224 316.COMPTY316 Appendix C, DED 0241

173,10 Type of change to parts list line M1 316.CHGTYP316 DIP7.2.1.j and Appendix C,
entry DED 0260

183,10 Component design/source M 220.DESENT210 or 319.DESENT210 or DIP7.2.1.k

enterprise identifier 221.DESENT200 or 320.DESENT200 or
222.SWSORC170 or 321.SWSORC170 or
223.SRCIDN01011 322.SRCIDN01012

193,10 Component part/material/ M 220.PARNUM210 or 319.PARNUM210 or DIP7.2.1.k

software/document identifier 221.MATGID200 or 320.MATGID200 or
222.SWIDEN170 or 321.SWIDEN170 or
223.DOCIDN01011 322.DOCIDN01012

4
The fields 'CI nomenclature' and 'Reference Designator' (sequence 7 and 8) must both be blank, or both be nonblank. Repeat this series as
necessary to identify all the reference designator associated with this find number (sequence 5).
5
Must be blank if 'Reference designator' (sequence 8) is blank; must be nonblank if 'Reference designator' is nonblank.
6
Repeat the series of fields sequence 10 and 11 as necessary to identify all the note numbers associated with this find number.
7
Must be blank if 'Referenced drawing note number' (sequence 10) is blank; must be nonblank if 'Referenced drawing note number is nonblank.
8
Repeat the series of fields sequence 12 and 13 as necessary to identify all the special conditions associated with this find number.
9
Must be blank if 'Special condition code' (sequence 12) is blank; must be nonblank if 'Special condition code' is nonblank.
10
The series of fields sequence 14 through 25 represent the 'row' of the parts list. Repeat this series as necessary to address each line entry associated
with this find number.
11
If the value of the 'Component type code' (sequence 16) is 'P', use the Tag that starts with 220; if it is 'M', use the Tag that starts with 221; if it is 'S',
use the Tag that starts with 222; if it is 'D', use the Tag that starts with 223.
12
If the value of the 'Component type code' (sequence 16) is 'P', use the Tag that starts with 319; if it is 'M', use the Tag that starts with 320; if it is 'S',
use the Tag that starts with 321; if it is 'D', use the Tag that starts with 322.

124
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 7

TABLE DIP7-I. Engineering parts list

Seq # Field Name M/O Data Element Tag For content and
validation instructions,
Subpacket 7A Subpacket 7B see
203,10 Component material O13 221.MATIDN200 320.MATIDN200 DIP7.2.1.k
identification parameter list

213,10 Component document type code O14 223.DOCTYP010 322.DOCTYP010 DIP7.2.1.k

223,10,15 "Assembly" part number M 225.PARNUM210 318.PARNUM317 DIP7.2.1.l and Appendix C,
(including dash number) DED 0024

233,10,15 Component quantity O16 225.QUANTY225 318.QUANTY318 Appendix C, DED 0053

3,10,15 17
24 Component unit of measure O 225.UOMCOD225 318.UOMCOD318 Appendix C, DED 0054
3,10,15 1
25 Type of change to assembly M 318.CHGTYP318 DIP7.2.1.m and Appendix C,
DED 0260

DIP7.2.1 Content instructions.

a. Enter the identification of the engineering drawing on which this parts list appears.

b. Enter either 'DWG' (for an integral parts list) or 'PL' (for a separate parts list drawing).

c. For graphic drawings which call out the component parts/materials/software/documents, reference designator, notes,
etc. on the face of the drawing instead of using a parts list, use '0' as the find number.

d. If this is a proposed new find number, enter 'A'; if this is a proposed deletion of the find number, enter 'D'. If it is
neither an addition or deletion, enter 'N'.

e. Enter the CI nomenclature of the item on which the reference designator in sequence 8 is assigned.

f. Enter the complete reference designator for this find.

g. If this is a proposed new reference designator for this find number, enter 'A'. If this is a proposed deletion this
reference designator from this find number, enter 'D'. If this is a change to a reference designator currently
associated with this find number, enter 'C'.

h. The parts list entry sequence number is an arbitrary number assigned to indicate the preferred order of presentation
of component parts/materials/software/documents when there are more than one component part/material/software/
document associated with a given find number, as is the case with alternate parts.

13
Mandatory if the value of 'Component type code' (sequence 16) is 'M'; must be blank in all other cases.
14
Mandatory if the value of 'Component type code' (sequence 16) is 'D'; must be blank in all other cases.
15
The series of fields 'Assembly part number', 'Component quantity', and 'Unit of measure' (sequence 22 through 25) represent the 'quantity column'
(or, for tabulated assemblies, the 'quantity columns') in the parts list. Repeat this series as necessary to address all quantity column(s) on the parts
list.
16
If the 'Component type code' (sequence 16) is 'S' or 'D', this field must be blank. It is mandatory for all other values of 'Component type code.
17
If the 'Component quantity' (sequence 23) is blank or has a value of 0, this field must be blank; this field is mandatory for all nonzero, nonblank
values of 'Component quantity'.

125
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 7

i. Indicate whether this parts list entry sequence number (sequence 10) is the primary or an alternate item for the
parent find number (sequence 5). For each find number, there can be only one parts list entry sequence number
which has a primary/alternate indicator with a value of 'P'.

j. If this is a proposed new line entry in the parts list for this find number, enter 'A'. If this is a proposed deletion of
this line entry for this find number from the parts list, enter 'D'. If this is a change to the 'Primary/alternate indicator'
or 'Component type code' (sequence 14 and 15), enter 'C'. If it is none of the above, enter 'N'.

k. Enter the identity of the component part (design source and part number), component material (design source,
material identifier and material identification parameters), component software (design source and software
identifier) or component document (source, identifier, and document type) which is associated with this find and
parts list entry sequence number. See Table DIP7-II for guidance on appropriate DEDs.

TABLE DIP7-II. Reference DED list for component item identification

Field Condition(s) See

Component design/source enterprise is a CAGE code Appendix C, DED 0001

identifier (Table DIP7-I, Sequence 18)
is a Company name Appendix C, DED 0170

is an Organization acronym Appendix C, DED 0002

is an Author’s name (use only with component Appendix C, DED 0069

document)
Component part identifier (Table DIP7-I, (use only with component part) Appendix C, DED 0024
Sequence 19)
Component material identifier (Table DIP7- (use only with component material) Appendix C, DED 0092
I, Sequence 19)
Component Material identification (use only with component material) Appendix C, DED 0038
parameter list (Table DIP7-I, Sequence 20)
Component software identifier18 (Table using the software release identification method Appendix C, DED 0262
DIP7-I, Sequence 19)
using the software part number identification Appendix C, DED 0024
method (use only with a component design/source
enterprise identifier which is either a CAGE code
or a company name)
using the software dash number identification Appendix C, DED 0088
method
Component document identifier (Table alphanumeric Table B-I and Appendix C, DED 0003
DIP7-I, Sequence 19)
title Table B-I and Appendix C, DED 0008

Component document type code (Table (use only with component documents) Table B-I and Appendix C, DED 0004
DIP7-I, Sequence 21)

l. Enter the complete part number (root number and suffix [dash] number, if any) which is defined by this parts list (or,
in the case of a tabulated assembly parts list, this column of the parts list).

m. If this is a proposed new assembly part number (a new column in a tabulated assembly parts list), enter 'A'. If this
assembly part number that is being proposed to be deleted from the drawing, enter 'D'. If this is a proposed change
to the component quantity or unit of measure, enter 'C'.

18
For a discussion of the various software identification methods supported, see Appendix B, B.5.4.

126
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 7

DIP7.2.2 Assumptions.

a. This data package assumes that all part numbers (both assembly and component) and all component materials which
are cited have been already established in the CM AIS by use of the appropriate Data Information Subpacket 3.

b. It assumes that all documents which are cited have been already established in the CM AIS by use of the appropriate
Data Information Subpacket 1 or 2.

c. It assumes that all software which is cited as component software, and all cited notes have been already established
in the CM AIS by use of the appropriate Data Information Subpacket 1.

d. It assumes that the CI nomenclature cited has been already established in the CM AIS by use of the appropriate Data
Information Subpacket 6.

DIP7.2.2.3. Constants and defaults. The following fields associated with the subpackets indicated are necessary to
properly populate the DOD CM AIS database, but either have the constant value indicated, or are transmitted as part of the
invoking data information subpacket. Because of this, they do not have to be transmitted as part of this information
subpacket.

DIP7.2.2.3.1 Subpacket 7A. The value of the 'Design CAGE code', 'Drawing number', 'Document type code', and
'Document revision' (sequence 1 through 4 in this subpacket) are the same as the values of 'Document source', Document
identifier', 'Document type code', and 'Document revision level' (sequence 3, 5, 1, and 6, respectively, in data information
subpacket 1A). This information is used to populate fields 224.DESCAG050, 224.ASSYNO224, 224.DOCTYP010, and
224.DOCREV051, respectively.

DIP7.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

127
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

(This page intentionally left blank)

128
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 8

Basic Document Protection

DIP8.1. Purpose. There is one series of data elements which is basic to all information packets concerning documents or
files. This series is referred to the "Basic document protection information packet". There are two subpackets, 8A is for
security information for documents and 8B is for security information for files. Both are shown in Table DIP8-I. Other
information packets will refer to this set of elements instead of repeating them.

DIP8.1.1 Subpackets. There are two subpackets for this packet:

Subpacket Applicability
8A Basic Document Protection
8B Basic File Protection

DIP8.2. Content of Information Packet. The information packet defines the elements to be provided and correlates the
information elements with the conceptual CM AIS database described in Appendices B and C. Within the table, in the
column labeled "M/O", the inclusion of the element in the information packet is either mandatory (M) or optional (O). For
each packet, the various elements shall be provided in the order shown in Table DIP10-I, except that optional fields
(denoted by O) for which data is not being submitted shall be skipped. Each element shall be preceded by the Data
Element Tag as shown in the table. The full field size for the data element, as shown in Appendix C, shall be used and
shall immediately follow the data element tag. No delimiters will be used between the fields or at the beginning or end of
this data packet. The last column in the table contains a reference to the contents of the data element.

TABLE DIP8-I. Basic document protection

Seq Field Name M/O Data Element Tag For content and validation
# instructions, see
Subpacket 8A Subpacket 8B
1 Government security class M 011.SECCOD011 900.SECCOD900 Appendix C, DED 0010
1
2 Access restrictions O 019.ACCCOD018 901.ACCCOD018 Appendix C, DED 0085
2
3 Classified by O 011.SECAUT011 900.SECAUT900 Appendix C, DED 0155
4 Classified on O2 011.SCLSDT011 900.SCLSDT900 DIP8.2.1.a and Appendix C, DED
0082
5 Downgrade to O3,4 011.SDWNCD011 900.SDWNCD900 Appendix C, DED 0010

6 Downgrade on O4 011.SDWNDT011 or 900.SDWNDT900 or DIP8.2.1.b and Appendix C, DEDs

011.SDWNEV0115 900.SDWNEV9006 0082 and 0156

1
Repeat this field as necessary.
2
Mandatory if the value of 'Government security class' is not "U" or "FOUO"; must be blank if value of 'Government security class' is "U" or
"FOUO"
3
Must be blank if the value of 'Government security class' is "U", "FOUO", "C", "NC", or "NR"
4
'Downgrade on' and 'Downgrade to' are paired fields; both must be blank, or both must be nonblank
5
Use 011.SDWNDT011 if the downgrade is by date; use 011.SDWNEV011 if the downgrade is by event.
6
Use 900.SDWNDT900 if the downgrade is by date; use 900.SDWNEV900 if the downgrade is by event.

129
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 8

TABLE DIP8-I. Basic document protection

Seq Field Name M/O Data Element Tag For content and validation
# instructions, see
Subpacket 8A Subpacket 8B
2
7 Declassify on O 011.SDCLDT011 or 900.SDCLDT900 or DIP8.2.1.c and Appendix C, DEDs
011.SDCLEV0117 900.SDCLEV9008 0082 and 0156

8 Copyright type M 011.CPYCOD013 900.CPYCOD013 Appendix C, DED 0012

9
9 Copyright by O 011.CPYENT011 900.CPYENT900 DIP8.2.1.d
10 Distribution statement code M 011.DISCOD014 900.DISCOD014 Appendix C, DED 0014
10
11 Distribution statement date O 011.DISDAT011 900.DISDAT900 DIP8.2.1.e and Appendix C, DED
0082

12 Distribution controlling O10 011.DISENT011 & 900.DISENT900 & DIP8.2.1.f and Appendix C, DEDs
organization & office 011.DISOFF011 900.DISOFF900 0044 and 0052

13 Export Control restriction M 011.EXPCOD015 900.EXPCOD015 Appendix C, DED 0079

code

14 Government Rights in M 011.RGTCOD016 900.RGTCOD016 Appendix C, DED 0022

Technical Data code

15 Data Rights contract O11 011.CONIDN950 900.CONIDN950 DIP8.2.1.g

number

16 Data rights expiration O9 011.RGTEXP011 900.RGTEXP900 DIP8.2.1.h and Appendix C, DED

0082

17 Company Proprietary M12 011.PRPCOD017 900.PRPCOD017 Appendix C, DED 0084

Rights code

18 Company name O13 011.PRPCOM011 900.PRPCOM900 DIP8.2.1.i and Appendix C, DED

0170

DIP8.2.1 Content Instructions.

a. Enter the classification date of the document or file.

b. Enter the date or event which will cause the security classification of the document or file to be downgraded.

c. Enter the date or event which will cause the document or file to be declassified.

d. If the document or file has been copyrighted, provide the name of the company holding the copyright.

7
Use 011.SDCLDT011 if the declassification is by date; use 011.SDCLEV011 if the declassification is by event.
8
Use 900.SDCLDT900 if the declassification is by date; use 900.SDCLEV900 if the declassification is by event.
9
This field must be blank if the value of 'copyright type' is "N"; for all other values of 'copyright type', the value of this field must be nonblank.
10
This field must be blank if the value of 'Distribution statement code' is "A00" or "N00", and must be nonblank for all other values of 'Distribution
statement code'
11
This field must be blank if the value of 'Government data rights code' is "N" or "U". For all other values of 'Government data rights code', this
field must be nonblank.
12
If the value of 'Government data rights code' is not "N" or "U", then the value of this field must be "Y".
13
If the value of 'Company proprietary rights code' is "N" and the value of 'Government data right code' is "N" or "U", this field must be blank. For
all other cases, this field must be nonblank.

130
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 8

e. Enter the distribution statement determination date.

f. Enter the controlling enterprise and office associated with the distribution statement.

g. Enter the contract number under which the data rights are granted to the Government.

h. Enter the expiration date of the data rights granted to the Government

i. Enter the name of the company which is claiming proprietary rights and granting (or withholding) Government
rights in technical data and/or computer software.

DIP8.3. Validation. Values (or combinations of values) which are part of these packets and which are shown as inherited
values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table will not be
updated and the information packet will be rejected without action.

131
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

(This page intentionally left blank)

132
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 9

Basic File

DIP9.1. Purpose. There is one series of data elements which is basic to all information packets concerning files. Other
information packets will refer to this set of elements instead of repeating them.

DIP9.1.1 Subpackets. There are two subpackets for this packet:

Subpacket Applicability
9A Basic File Subpacket
9B File Description Subpacket

DIP9.2. Content of data information subpackets. The information subpackets define the elements and files to be provided
and correlates the information elements with the conceptual CSA AIS database described in Appendices B and C. Within
the table, the inclusion of the element in the information subpacket is either mandatory (M) or optional (O). For each
subpacket, the various elements shall be provided in the order shown in Table DIP10-I, except that optional fields
(denoted by O) for which data is not being submitted shall be skipped. Each element shall be preceded by the Data
Element Tag as shown in the table. The full field size for the data element, as shown in Appendix C, shall be used and
shall immediately follow the data element tag. No delimiters will be used between the fields or at the beginning or end of
this data subpacket. The last column in the table contains a reference to the contents of the data element.

TABLE DIP9-I. Basic file

Seq Field Name Data Information Data Element Tag For content and validation
# Subpacket instructions, see
9A 9B
1 Filename M 900.FILNAM900 Appendix C, DED 0211

2 File originator M 900.FILORG900 Appendix C, DED 0069

3 File originator's address M 900.FILADD900 Appendix C, DED 0081

4 File origination date and time M 900.FILDAT900 and Appendix C, DEDs 0082 and 0160
900.FILTIM900

5 File description O O 900.FILDES900 Appendix C, DED 0212

6 File type code M M 900.FILTYP900 Appendix C, DED 0210

7 File compression code M M 900.CMPCOD900 Appendix C, DED 0215
1 1
8 File compression method code O O 900.CMPMTH900 Appendix C, DED 0214
2 2
9 Application software source O O 900.SWSORC170 The transmitted field must be 36
characters, left justified, and
consisting of either a CAGE code
(Appendix C, DED 0001), an
organization acronym (Appendix C,
DED 0002), a company name
(Appendix C, DED 0170) or an
author's name (Appendix C, DED
0069).

1
Mandatory if the value of 'file compression code' is "Y"; otherwise, must be blank.
2
Mandatory if the value of 'file type code' is "PLANG".

133
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 9

TABLE DIP9-I. Basic file

Seq Field Name Data Information Data Element Tag For content and validation
# Subpacket instructions, see
9A 9B
2
10 Application software O O2 900.SWIDEN170 The transmitted field must be 248
characters, left justified, and
consisting of either a software
alphanumeric identifier (Appendix C,
DED 0088), a part number
(Appendix C, DED 0024), or a
software product identifier
(Appendix C, DED 0262).

11 Application software location O3 O3 903.APPLOC902 Appendix C, DED 0209, application-

software-electronic-storage-place-
identifier.

12 Application software launch script O3 O3 903.LAUNCH902 Appendix C, DED 0209, application-

location software-launch-script-electronic-
storage-place-identifier.

13 Computer operating system type code O4 O4 900.OPSYST900 Appendix C, DED 0213

14-31 Basic File Protection Subpacket M M See Data Information See Data Information Packet 8
Subpacket 8B

32 File location O5 O5 900.FILLOC900 Appendix C, DED 0209, document-

file-image-electronic-storage-place-
identifier.

33 File O6 O6 Not applicable This is the actual electronic file.

(Note: DoD will enter it in their
PDM system.)

DIP9.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

3
Nonblank for file access via a CITIS if required by the CITIS; otherwise, blank.
4
Must be nonblank if 'File' is nonblank. Should be nonblank if information is required by CITIS.
5
Required if access to file being granted via a CITIS. If this is nonblank, then sequence 33 must be blank.
6
Required if access to file via CITIS is not being provided. If this is nonblank, sequence 32 must be blank. (Note: if this is nonblank, the DoD
CSA AIS will generate the value for sequence 32 when this information is up-loaded to the DoD PDM.)

134
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 10

Basic Document Representation

DIP10.1. Purpose. There is one series of data elements which is basic to all information packets concerning document
representations. This series is referred to the "Basic document representation subpacket" and is shown in Table DIP10-I.
Other information packets will refer to this set of elements instead of repeating them.

DIP10.1.1 Subpackets. There are two subpackets for this packet:

Subpacket Applicability
10A Basic document representation
10B Document representation description
10C Non-electronic document representation description

DIP10.2. Content of information subpackets. The information subpackets define the elements and files to be provided
and correlates the information elements with the conceptual CM AIS database described in Appendices B and C. Within
the table, the inclusion of the element in the information subpacket is either mandatory (M) or optional (O). For each
subpacket, the various elements shall be provided in the order shown in Table DIP10-I, except that optional fields
(denoted by O) for which data is not being submitted shall be skipped. Each element shall be preceded by the Data
Element Tag as shown in the table. The full field size for the data element, as shown in Appendix C, shall be used and
shall immediately follow the data element tag. No delimiters will be used between the fields or at the beginning or end of
this data subpacket. The last column in the table contains a reference to the contents of the data element.

TABLE DIP10-I. Basic document representation

Seq Field Name Data Information Data Element Tag For content and
# Subpacket validation
instructions, see
10A 10B 10C
1 Document representation identifier M 800.REPIDN800 Appendix C, DED 0207

2 Document representation revision M 801.REPREV801 Appendix C, DED 0208

level
3 Document representation revision M 801.REPORG801 DIP10.2.1.a
originator

4 Document representation creation M M M 801.REPDAT801 DIP10.2.1.b

date
51 Filename O2 O2 802.FILIDN900 Appendix C, DED 0211
1 3 3
6 File originator O O 802.FILORG900 Appendix C, DED 0069
1 3 3
7 File originator's address O O 802.FILADD900 Appendix C, DED 0081

81 File origination date and time O3 O3 802.FILDAT900 and Appendix C, DEDs

802.FILTIM900 0082 and 0160

9-361 File description subpacket O3 O3 O4 See Data Information Data Information Packet
Subpacket 9B 9

1
This series of fields (sequence 5 through 36) should be repeated for each file associated with this revision of this document representation.
2
Must be blank if the document representation is paper, stable-base material, punch-cards, video tape, on-line database, etc; must be nonblank for
all types of digital representations.
3
This is a paired field with 'Filename'; either both must be blank, or both must be nonblank.
4
This is a paired field with ‘Filename’ in DIP6, Sequence 53; either both must be blank, or both must be nonblank.

135
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
Data Information Packet 10

TABLE DIP10-I. Basic document representation

Seq Field Name Data Information Data Element Tag For content and
# Subpacket validation
instructions, see
10A 10B 10C
37 Document representation release M M M 803.REPSTA803 Appendix C, DED 0021
status

38 Document representation release M M M 803.RELDAT803 Appendix C, DED 0082

status date

DIP10.2.1 Content instructions.

a. Enter the identity of the "author" of this revision of the document representation. This may be a name, a CAGE
code, or an acronym for an organization (for example, ANSI, ISO, USAF). If the identity is a person, see Appendix
C, DED 0069; if the identity is a CAGE code, see Appendix C, DED 0001; if the identity is a company name, see
Appendix C, DED 0170; if the identity is an organization acronym, see Appendix C, DED 0002.

b. Enter the creation date of this revision of the document representation. See also Appendix C, DED 0082.

DIP10.3. Validation. Values (or combinations of values) which are part of these subpackets and which are shown as
inherited values in Appendix B, will be verified to exist in the appropriate tables. If a discrepancy exists, the parent table
will not be updated and the information subpacket will be rejected without action.

136
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

SELECTION AND TAILORING GUIDANCE

A.1. SCOPE.

A.1.1 Scope. This appendix provides guidance for selecting the applicable portions of specific Data Information
Packets (DIPs) needed to support configuration management data requirements during the product life cycle. This
appendix is not a mandatory part of this standard. The information contained herein is intended for guidance only.

A.2. APPLICABLE DOCUMENTS.

This section is not applicable to this appendix.

A.3. DEFINITIONS.

The acronyms and definitions in section 3 of this standard apply to this appendix.

A.4. ACQUISITION TECHNIQUES.

A.4.1. General. Each required subpacket of a DIP should be specifically cited in Block 16 on the DD Form 1423,
Contract Data Requirements List (CDRL) included in the contract or purchase order. Since much of the required
data may be obtained from Government sources where a CDRL is not required, the required subpackets should be
included in the Statement of Work or other internal tasking document for data generated internally to the DoD. In all
cases, the procuring activity has the option of physically receiving the data/document in any appropriate form (for
example: paper, digital, microfilm), or of arranging for storage of, and access to, the technical data/document via a
CITIS. The DoD is responsible for maintaining accurate configuration records of delivered material items and their
configuration documentation when such records are required to enable item traceability, logistics support,
demilitarization and eventual disposal.
A.4.2. Use of Table A-1. The type and amount of CM data that the Government requires varies according to the
program and its design maturity, acquisition concept, and logistics support plan. Table A-I provides information
applicable to the selection of Data Information Subpackets. There are three steps to determining the specific
subpackets necessary to support CM data requirements:
a. The first is to identify the type of CM data (document type(s) and associated data) being ordered. For each
type of CM data, the Table indicates whether it is: essential (E) that the data is delivered, or access to the data
begins; recommended (R); optional (O); or not recommended (blank); for each acquisition program phase
related to the product’s design maturity. Identify the selection and tailoring paragraph associated with the CM
data from the first column of Table A-I.
b. The selection and tailoring paragraph provides helpful information about that CM data, and usually refers to a
subsequent Table (Tables II through XIV) containing guidance for tailoring requirements associated with that
particular data under various acquisition concepts. In some instances the second Table was not necessary, and
the tailoring paragraph itself identifies the appropriate Data Information Subpacket(s) associated with that CM
data applicable to the acquisition concept for the program, eliminating the last step below.
c. Finally, where a subsequent Table was used, select the appropriate Data Information Subpacket(s) associated
with that CM data by referring to the Note(s) indicated in Tables II through XIV applicable to the acquisition
concept for the program.

A-1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-I. Selection and tailoring guidance for data information subpackets.
Program Definition & Engineering & Production, Fielding/Deployment, & Operational
Acquisition Life Cycle Phase: Risk Reduction Manufacturing Development Support and Demilitarization & Disposal
System Allocated Production, Post Production
Design Maturity: Definition Performance Design Definition Operations and Support Operations and Support
Definition
Nonrepairable (NR)/Repairable (R): NR R NR R NR R
Performance-based (P-B)/Design-Based (D-B): P-B D-B P-B D-B P-B P-B D-B P-B P-B D-B P-B P-B D-B
Paragraph Type of Data
A.4.2.1 System-to-system interface control drawings E E
Top-level CI external interface control E E
drawings
CI-to-CI interface control drawings E E E
Conceptual design drawings & associated lists R
Developmental design drawings & associated R
lists
Product design drawings & associated lists E
Special inspection equipment drawings & O O
associated lists
Special tooling drawings & associated lists O
Revisions to acquired drawings E E E E E E E E E E E
A.4.2.2 Program-unique system performance E E
specification
Program-unique top-level allocated E E
performance specifications
Program-unique lower level allocated E E E
performance specifications
Program-unique product design specifications E
Revisions to previously acquired specifications E E E E E E E E E E E
A.4.2.3 Standardization documents O O O O O O O O O O O O O
Revisions to previously acquired E E E E E E E E E E E
standardization documents
A.4.2.4 Software & software administrative E
information
Revisions to previously acquired software & E E
software administrative info

A-2
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-I. Selection and tailoring guidance for data information subpackets.
Program Definition & Engineering & Production, Fielding/Deployment, & Operational
Acquisition Life Cycle Phase: Risk Reduction Manufacturing Development Support and Demilitarization & Disposal
System Allocated Production, Post Production
Design Maturity: Definition Performance Design Definition Operations and Support Operations and Support
Definition
Nonrepairable (NR)/Repairable (R): NR R NR R NR R
Performance-based (P-B)/Design-Based (D-B): P-B D-B P-B D-B P-B P-B D-B P-B P-B D-B P-B P-B D-B
Paragraph Type of Data
A.4.2.5 Software support documents E
Revisions to previously acquired software E E
support documents
A.4.3 Paperless hardware designs R
Revisions to previously acquired paperless E E E
hardware designs
A.4.4.1 General documents O O O O O O O O O O O O O
Revisions to previously acquired general docs E E E E E E E E E E E
A.4.4.2 Document supplements R R R
A.4.5.1 Part/material definition E E
A.4.5.2 NSN E E
A.4.5.3 Traceability E E E E E E
A.4.5.4 As-built/as-delivered configuration and E E E E E E
changes to fielded items
A.4.6.1 ECPs to system performance specification & E E E E E E E E E E E
associated interface drawings
ECPs to top-level allocated performance E E E E E E E E E
specifications & associated interface drawings
ECPs to lower level allocated performance O O O E E E E
specifications & CI-to-CI interface drawings
ECPs to all product design documents E E
including internal interface control drawings

A-3
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-I. Selection and tailoring guidance for data information subpackets.
Program Definition & Engineering & Production, Fielding/Deployment, & Operational
Acquisition Life Cycle Phase: Risk Reduction Manufacturing Development Support and Demilitarization & Disposal
System Allocated Production, Post Production
Design Maturity: Definition Performance Design Definition Operations and Support Operations and Support
Definition
Nonrepairable (NR)/Repairable (R): NR R NR R NR R
Performance-based (P-B)/Design-Based (D-B): P-B D-B P-B D-B P-B P-B D-B P-B P-B D-B P-B P-B D-B
Paragraph Type of Data
A.4.6.2 RFDs to system performance specification and E E E E E E E E
associated interface drawings
RFDs to top-level allocated performance E E E E E E
specifications and associated interface
drawings
RFDs to lower level allocated performance O O O E E
specifications and CI-to-CI interface drawings
RFDs to all product design documents E
including internal interface control drawings
A.4.6.3 Modification Requests R R E E
A.4.6.4 Modification Instructions R R E E
A.4.7.1 ECP/RFD action item status R R R R R R R R R R R
A.4.7.2 CM audit action item status R E*
A.4.8.1 Organization & CCBs R R E E E E E E E E E E E
A.4.8.2 System/CI nomenclature O O R R E E E
A.4.8.3 Contract & CDRL requirements R R R R R R R R R R
A.4.8.4 Review, comment, and disposition status of R R R R R R R R R R R R R
documents/CDRLs
A.4.8.5 Issue CCB directive R R R R R R R R R R R
A.4.8.6 Define technical baseline documents O O O O O O O O O O O O O
Define functional baseline documents R R E* E*
Define allocated baseline documents R R E* E* E*
Define product baseline documents R E*
Define contract baseline documents E E
A.4.8.7 CPIN O O O
PAN O O O O O O O O O O O

A-4
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-I. Selection and tailoring guidance for data information subpackets.
Program Definition & Engineering & Production, Fielding/Deployment, & Operational
Acquisition Life Cycle Phase: Risk Reduction Manufacturing Development Support and Demilitarization & Disposal
System Allocated Production, Post Production
Design Maturity: Definition Performance Design Definition Operations and Support Operations and Support
Definition
Nonrepairable (NR)/Repairable (R): NR R NR R NR R
Performance-based (P-B)/Design-Based (D-B): P-B D-B P-B D-B P-B P-B D-B P-B P-B D-B P-B P-B D-B
Paragraph Type of Data
A.4.8.8 Change custodian of a document O O O O O O O O O O O O O
Add, change, or delete Application O O O O O O O O O O O O O
Activity (including GLAA)
Transfer CDCA of system performance R R E* E*
specification & associated interface drawings
Transfer CDCA of top-level allocated R R E* E* E*
performance specifications & associated
interface drawings
Transfer CDCA of lower level allocated R R R E* E*
performance specifications & CI-to-CI
interface drawings
Transfer CDCA of all product design R E*
documents including internal interface control
drawings
Transfer CDCA of other documents (DED O O O O O O O O O O O O O
#0004, Appendix C)
Transfer CDCA of document supplements R R R E E E
(DED #0004, Appendix C)
Transfer CDCA of software O O
A.4.8.9 Add document representation R R R R R R R R R R R R R
* If not previously accomplished.

A-5
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

A.4.2. Selection and tailoring associated with drawings, specifications, standards, software and software support
documents.
A.4.2.1. Design drawings and associated lists.
A.4.2.1.1. Selection. Engineering drawings and associated lists may be required for any product, including mission
equipment, special inspection equipment, training devices, special tooling, etc. Engineering drawings and associated
lists are used:
a. during the program definition and risk reduction phase (when the design maturity is undergoing system
definition and, if applicable, allocated performance definition) to verify preliminary design and engineering
and confirm that the technology is feasible and that the design concept has the potential to be useful in meeting
a specific requirement (see MIL-DTL-31000 for additional guidance),
b. during the engineering and manufacturing development phase (when the design maturity is undergoing
allocated performance definition, if applicable, and/or design definition) to describe a specific design
approach, provide the information to produce material for test or experimentation, and for the analytical
evaluation of the inherent ability of the design approach to attain the required performance (see MIL-DTL-
31000 for additional guidance),
c. during production in the production, fielding/deployment, and operational support phase when there is a
current or future need for the Government to procure or manufacture the equipment, components, or spares
and repair parts from either the original manufacturer or an alternate source (see MIL-DTL-31000 for
additional guidance), or
d. during the production, fielding/deployment, and operational support phase, after production, when the
Government will maintain the equipment using indigenous support or will contract maintenance support from a
supplier other than the original designer of the equipment.
A.4.2.1.2. Tailoring. Engineering documents and associated lists are typically obtained via DIDs such as DI-DRPR-
81000, -81001, -81002, -81003, -81004, and -81008 in the CDRL. Decide (1) if the Government wants to buy the
originals (including all rights to change those originals) or copies1 (with, or without, the right to review/adopt
changes to those originals), (2) if the drawings and associated lists are to be delivered to the Government repository,
or if perpetual access is to be provided by the performing activity, and (3) whether or not to buy electronic CM data
about the drawings and associated lists2. See Table A-II for tailoring guidance.
Table A-II. Guidance on tailoring requirements for drawings and associated lists.
Purchase Delivery or Purchase Electronic CM Internal Tasking or External See Notes:
Originals Access Data Buy
or Copies
Yes Internal a, c, and f
Originals Delivery External a, c, and g
No External a, c, and h
Access Yes External a, d, and i
No External a, d, and j
Delivery Yes External b, e, and g
Copies No External b, e, and h
Access Yes External b, d, and i
No External b, d, and j

Notes:

1
Not applicable to internal taskings

2
The tasking activity is responsible for ensuring that the configuration management information required by DIP1 subpacket 1A is entered
into the CM AIS.

A-6
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

a. Include in the SOW or internal tasking directive the requirement to create engineering drawings and associated
lists. Complete the appropriate MIL-DTL-31000 TDP Option Selection Work Sheet(s) (Product Drawings and
Associated Lists, Conceptual Design Drawings and Associated Lists, Developmental Design Drawings and
Associated Lists, Special Inspection Equipment Drawings and Associated Lists, and/or Special Tooling
Drawings and Associated Lists) specifying digital delivery. It is recommended that use of Government CAGE
and drawing numbers be specified on the Selection Work Sheet(s). In the CDRL for the drawings and
associated lists or in the internal tasking directive specify:
(1) that the intention is to procure the originals and all rights (see also A.4.8.8) to the drawings and
associated lists
(2) the acceptable electronic format of drawings (for example: IGES)
b. Include in the SOW the requirement to create engineering drawings and associated lists. Complete the
appropriate MIL-DTL-31000 TDP Option Selection Work Sheet(s) (Product Drawings and Associated Lists,
Conceptual Design Drawings and Associated Lists, Developmental Design Drawings and Associated Lists,
Commercial Drawings and Associated Lists, Special Inspection Equipment Drawings and Associated Lists,
and/or Special Tooling Drawings and Associated Lists). It is recommended that use of Contractor source
identification (preferably CAGE code) and drawing numbers be specified on the Selection Work Sheet(s). In
the CDRL for the drawings and associated lists specify:
(1) that the intention is to procure copies and, if applicable, the right to review/adopt changes to the original
(see also A.4.8.6) of the drawings and associated lists
(2) the acceptable electronic format (for example: IGES)
c. In the internal tasking directive or CDRL for the drawings and associated lists, specify when the documents are
to be delivered.
d. Include a requirement in the SOW for a CITIS according to MIL-STD-974, specify at what status (for
example; working, released, etc.) the customer is to be provided access and specify at what point in time the
customer is to be provided access. In the remarks section of the CDRL for the drawings and associated lists,
include the requirement for the contractor to provide perpetual3 access to the digital drawings and associated
lists.
e. In the CDRL for the drawings and associated lists, specify when the documents are to be delivered.
f. In the internal tasking directive, attach the completed MIL-DTL-31000 TDP Option Selection Worksheet(s)
and specify: (1) delivery according to the electronic format requirements of data information subpacket 1A and
Table DIP1-I of MIL-STD-2549, (2) whether or not text of notes is to be delivered as part of CM data, (3)
whether or not special item and process notations are to be delivered as part of the CM data, (4) that DIP9
sequence 33 must be blank and sequence 34 is mandatory, and (5) that part identification and administrative
information (and electronic part models, if required) be delivered according to the electronic format
requirements of data information subpacket 3A and Table DIP3-I of MIL-STD-2549 for each part defined by a
drawing.
g. Cite the drawings and associated lists DID number in the CDRL and attach the completed TDP Option
Selection Worksheet(s) to the CDRL. In the remarks section of the CDRL, specify: (1) delivery according to
the electronic format requirements of data information Subpacket 1A and Table DIP1-I of MIL-STD-2549, (2)
whether or not text of notes is to be delivered as part of CM data, (3) whether or not special item and process
notations are to be delivered as part of the CM data, (4) that DIP9 sequence 33 must be blank and sequence 34
is mandatory, and (5) that part identification and administrative information (and electronic part models, if
required) be delivered according to the electronic format requirements of data information subpacket 3A and
Table DIP3-I of MIL-STD-2549 for each part defined by a drawing.
h. Cite the drawings and associated lists DID number in the CDRL, attach the completed TDP Option Selection
Worksheet(s), and specify delivery of the documents according to MIL-STD-1840.

3
“Perpetual” should be defined in the SOW as some period of time in excess of the expected life-time of the last item to be procured to this
drawing set, with options for additional periods of time.

A-7
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

i. Cite the drawings and associated lists DID number in the CDRL and attach the completed TDP Option
Selection Worksheet(s) to the CDRL. In the remarks section of the CDRL, specify: (1) delivery of CM data
for documents according to the electronic format requirements of data information subpacket 1A and Table
DIP1-I of MIL-STD-2549, (2) whether or not text of notes is to be delivered as part of CM data, (3) whether
or not special item and process notations are to be delivered as part of the CM data, (4) that DIP9 sequence 33
is mandatory and sequence 34 must be blank, and (5) that part identification and administrative information
(and electronic part models, if required) be delivered according to the electronic format requirements of data
information subpacket 3A and Table DIP3-I of MIL-STD-2549 for each part defined by a drawing.
j. Cite the drawings and associated lists DID number in the CDRL and attach the completed TDP Option
Selection Worksheet(s). In the remarks section of the CDRL, specify: (1) delivery of a copy of the
document(s)/file(s) identification and location according to the electronic format requirements of data
information subpacket 2A and Table DIP2-I of MIL-STD-2549 and (2) that DIP9 sequence 33 is mandatory
and sequence 34 must be blank.
A.4.2.2. Program-unique specifications.
A.4.2.2.1. Selection. Program-unique specifications may be required for any system, item, software, material or
process.
a. During system definition or early in allocated performance definition, the functional configuration
documentation (FCD) consisting of a system performance specification is developed to document the system-
level functional, performance and interface requirements. The specification also includes methods for
verifying compliance with each requirement identified in the document. (See MIL-STD-961 for additional
guidance on system specifications.)
b. During allocated performance and design definition, the allocated configuration documentation (ACD)
consisting of allocated performance specifications are developed to document the allocation of system-level
functional, performance and interface requirements to subsystems, assemblies, subassemblies and components
below the system-level. These specifications also include methods for verifying compliance with each
requirement identified in them. During this phase, the FCD is updated if required. (See MIL-STD-961 for
additional guidance on item, software, material and process specifications.)
c. During design definition, the product configuration documentation (PCD) is developed to document the design
solutions that satisfy the requirements contained in the ACD. The PCD is developed by combining the design
information with the ACD. This usually occurs by referencing the top assembly drawing or adding a software
code listing to the appropriate specification. Special processes needed to manufacture specific design
solutions are included in the PCD as well. Design information also includes first article and acceptance
requirements. These specifications, like the others, include methods for verifying compliance with each
requirement identified in them. During this phase, the FCD and ACD are updated as required. (See MIL-
STD-961 for additional guidance on item, software, material and process specifications.)
d. In terms of the acquisition life cycle, the FCD normally reaches maturity at the end of the program definition
and risk reduction phase. The high-level ACD normally reaches maturity early in the engineering and
manufacturing development phase with the remaining lower-level ACD, if applicable, maturing at the end of
the engineering and manufacturing development phase. The PCD normally reaches maturity with the first
production representative unit during the production, fielding/deployment and operational support phase.
Once this documentation reaches maturity, it is used to support acquisition and sustainment strategies
throughout the product’s life cycle. During the production, fielding/deployment and operational support
phase, the FCD, ACD and PCD, as applicable, are updated as required to support the procurement,
manufacture and sustainment of the delivered systems as well as their related spares and support equipment.
A.4.2.2.2. Tailoring. Program-unique specifications are typically obtained via DIDs such as DI-SDMP-81493
and/or DI-IPSC-81431, -81433, -81434, and -81441 (or DI-CMAN-81551 if no other appropriate DID exists) in the
CDRL. Decide (1) if the Government wants to buy the originals (including all rights to change those originals) or
copies4 (with, or without, the right to review/adopt changes to those originals), (2) if the program-unique
specifications are to be delivered to the Government repository, or if perpetual access is to be provided by the

4
Not applicable to internal taskings

A-8
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

performing activity, and (3) whether or not to buy electronic CM data about the program-unique specifications5 . See
Table A-III for tailoring guidance.

Table A-III. Guidance on tailoring requirements for program-unique specifications.

Purchase Delivery or Access Purchase Internal Tasking or See Notes:
Originals Electronic CM External Buy
or Copies Data
Originals Delivery Yes Internal a, c, and f
External a, e, and g
No External a, e, and h
Access Yes External a, d, and i
No External a, d, and j
Copies Delivery Yes External b, e, and g
No External b, e, and h
Access Yes External b, d, and i
No External b, d, and j

Notes:
a. Include in the SOW the requirement to create program-unique specifications according to the guidance in
MIL-STD-961, Appendix A. Complete the MIL-DTL-31000 TDP Option Selection Work Sheet for
Specifications, specifying digital delivery. It is recommended that use of Government CAGE and program-
unique specification numbers be specified on the Selection Work Sheet. In the CDRL for the program-unique
specification specify:
(1) that the intention is to procure the originals and all rights (see also A.4.8.8) to the program-unique
specifications
(2) the acceptable electronic format of program-unique specifications (for example: SGML, HTML, etc.)
b. Include in the SOW or internal tasking directive the requirement to create program-unique specifications
according to the guidance in MIL-STD-961 Appendix A. Complete the MIL-DTL-31000 TDP Option
Selection Work Sheet for Specifications. It is recommended that use of Contractor source identification
(preferably CAGE code) and program-unique specification numbers be specified on the Selection Work Sheet.
In the CDRL for the program-unique specification specify:
(1) that the intention is to procure copies and, if applicable, the right to review/adopt changes to the original
(see also A.4.8.6) of the program-unique specification
(2) the acceptable electronic format (for example: SGML, HTML, etc.)
c. In the internal tasking directive or in the CDRL for the program-unique specification, specify when the
documents are to be delivered. (This is life-cycle phase dependent, see MIL-HDBK-61 for guidance.)
d. Include a requirement in the SOW for a CITIS according to MIL-STD-974, specify at what status (for
example; working, released, etc.) the customer is to be provided access and specify at what point in time the
customer is to be provided access. In the CDRL for the program-unique specification, include the requirement
for the contractor to provide perpetual6 access to the digital program-unique specifications.

5
The tasking activity is responsible for ensuring that the configuration management information required by DIP1 subpacket 1B is entered
into the CM AIS.

6
“Perpetual” should be defined in the SOW as some period of time in excess of the expected life-time of the last item to be procured to
which this program-unique specification applies. Options for additional periods of time should also be considered.

A-9
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

e. In the CDRL for the program-unique specification, specify when the documents are to be delivered.
f. In the internal tasking directive, attach the completed TDP Option Selection Worksheet for Specifications and
specify: (1) delivery according to the electronic format requirements of data information subpacket 1B and
Table DIP1-I of MIL-STD-2549, (2) that DIP9 sequence 33 must be blank and sequence 34 is mandatory, and
(3) for material specifications only, that part identification and administrative information (and electronic part
models, if required) be delivered according to the electronic format requirements of data information
subpacket 3A and Table DIP3-I of MIL-STD-2549 for each part defined by a program-unique material
specification.
g. Cite the program-unique specification DID number (or DI-CMAN-81551 if no other appropriate DID exists)
in the CDRL and attach the completed TDP Option Selection Worksheet for Specifications to the CDRL. In
the remarks section of CDRL specify: (1) delivery according to the electronic format requirements of data
information Subpacket 1B and Table DIP1-I of MIL-STD-2549, (2) that DIP9 sequence 33 must be blank and
sequence 34 is mandatory, and (3) for material specifications only, that part identification and administrative
information (and electronic part models, if required) be delivered according to the electronic format
requirements of data information subpacket 3A and Table DIP3-I of MIL-STD-2549 for each part defined by a
program-unique material specification.
h. Cite the program-unique specification DID number (or DI-CMAN-81551 if no other appropriate DID exists)
in the CDRL and attach the completed TDP Option Selection Worksheet for Specifications to the CDRL. In
the remarks section of the CDRL, specify delivery of the documents according to MIL-STD-1840.
i. Cite the program-unique specification DID number (or DI-CMAN-81551 if no other appropriate DID exists)
in the CDRL and attach the completed TDP Option Selection Worksheet for Specifications to the CDRL. In
the remarks section of the CDRL, specify: (1) delivery of configuration data for documents according to the
electronic format requirements of data information subpacket 1B and Table DIP1-I of MIL-STD-2549, (2) that
DIP9 sequence 33 is mandatory and sequence 34 must be blank, and (3) for material specifications only, that
part identification and administrative information (and electronic part models, if required) be delivered
according to the electronic format requirements of data information subpacket 3A and Table DIP3-I of MIL-
STD-2549 for each part defined by a program-unique material specification.
j. Cite the program-unique specification DID number (or DI-CMAN-81551 if no other appropriate DID exists)
in the CDRL and attach the completed TDP Option Selection Worksheet for Specifications to the CDRL. In
the remarks section of the CDRL, specify (1) delivery of a copy of the document/file identification and
location according to the electronic format requirements of data information subpacket 2A and Table DIP1-I
of MIL-STD-2549, and (2) that DIP9 sequence 33 is mandatory and sequence 34 must be blank.
A.4.2.3. Standardization documents.
A.4.2.3.1. Selection. Standardization documents are documents which are issued by international, government,
industry, or other organizations for the purpose of standardizing parts or materials, processes, or practices across a
segment of a company, industry, country, etc. They are called by various names by the issuing entities; for example:
specifications, standards, guidebooks, handbooks, standard practices, protocols, regulations, manuals, standard
agreements, bulletins, etc. Standardization documents are used during all phases of product and project life cycle:
a. To minimize cost by preventing the necessity of re-designing a part, material, process, or practice which is
already in use,
b. To promote interchangeability of parts and materials between assemblies,
c. To promote seamless interface between organizations or software, or
d. To document ‘lessons learned’ and promote ‘best practices’
A.4.2.3.2. Tailoring. Standardization documents are typically obtained via DIDs such as DI-SDMP-81464, -81465,
-81470, -81471, -81472, -81473, -81474, -81475, -81476 (or DI-CMAN-81551 if no other appropriate DID exists)
in the CDRL. Before ordering, determine if a suitable document exists. If so, order a copy from the external
organization which is the custodian for it. If a new document is necessary, determine if it will be a defense document
(for example: defense standard, defense specification, etc.). See Table A-IV for tailoring guidance.

A-10
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A- IV. Guidance on tailoring requirements for standardization documents.

Internal or Defense Document Access / Delivery Purchase Electronic See Notes:
External CM Data
Source
Internal Yes Delivery Yes a, c, and e
Yes Delivery Yes a, c, and f
External No a, c, and g

No Delivery Yes b, c, and h

No b, c, and g

Access Yes b, d, and h

No b, d, and g

Notes:
a. Include in the SOW or internal tasking directive the requirement to create defense documents according to the
guidance in MIL-STD-961, MIL-STD-962, or other appropriate Government documents. If a document is to
be a Defense Specification, complete the MIL-DTL-31000 TDP Option Selection Work Sheet for
Specifications specifying digital delivery of the original. Specify on the Selection Work Sheet that the
document number will be provided by the Government. In the CDRL for the standardization document or
internal tasking directive specify:
(1) that the intention is to procure the originals and all rights (see also A.4.8.8) to the defense document(s)
(2) the acceptable electronic format of documents (for example: SGML, etc.7)
b. In the CDRL for the standardization document specify:
(1) that the intention is to procure copies of the standardization documents
(2) the acceptable electronic format (for example: PDF, raster)
c. In the internal tasking directive, or in the CDRL for the standardization document, specify when the documents
are to be delivered.
d. Include a requirement in the SOW for a CITIS according to MIL-STD-974, specify at what status (for
example; working, released, etc.) the customer is to be provided access and specify at what point in time the
customer is to be provided access. In the CDRL for the standardization document include the requirement for
the contractor to provide perpetual8 access to the digital standardization document(s).
e. In the internal tasking directive, attach the completed TDP Option Selection Work Sheet for Specifications (if
applicable) and specify: (1) delivery according to the electronic format requirements of data information
subpacket 1C and Table DIP1-I of MIL-STD-2549, (2) that DIP9 sequence 33 must be blank and sequence 34
is mandatory, (3) that part identification and administrative information (and electronic part models, if
required) be delivered according to the electronic format requirements of data information subpacket 3A and
Table DIP3-I of MIL-STD-2549 for each part defined by a defense specification.

7
Do not specify just raster, PDF, or any other kind of electronic format which is not easily editable as this will make maintenance of the
document much more difficult.

8
“Perpetual” should be defined in the SOW as some period of time in excess of the expected life-time of the last item to be procured to this
drawing set, with options for additional periods of time.

A-11
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

f. Cite the standardization document DID number (or DI-CMAN-81551 if no other appropriate DID exists) in
the CDRL and attach the completed TDP Option Selection Work Sheet for Specifications (if applicable). In
the remarks section of the CDRL, specify: (1) delivery according to the electronic format requirements of data
information Subpacket 1C and Table DIP1-I of MIL-STD-2549, (2) that DIP9 sequence 33 must be blank and
sequence 34 is mandatory, and (3) that part identification and administrative information (and electronic part
models, if required) be delivered according to the electronic format requirements of data information
subpacket 3A and Table DIP3-I of MIL-STD-2549 for each part defined by a defense specification.
g. Cite the standardization document DID number (or DI-CMAN-81551 if no other appropriate DID exists) in
the CDRL and attach the completed TDP Option Selection Work Sheet for Specifications (if applicable) to the
CDRL. In the remarks section of the CDRL, specify delivery of the documents according to MIL-STD-1840.
h. Cite the standardization document DID number (or DI-CMAN-81551 if no other appropriate DID exists) in
the CDRL. In the remarks section of the CDRL, specify: (1) delivery of configuration data for documents
according to the electronic format requirements of data information subpacket 1C and Table DIP1-I of MIL-
STD-2549, (2) that DIP9 sequence 33 is mandatory and sequence 34 must be blank, and (3) that part
identification and administrative information (and electronic part models, if required) be delivered according
to the electronic format requirements of data information subpacket 3A and Table DIP3-I of MIL-STD-2549
for each part defined by a defense specification.
A.4.2.4. Software and software administrative information. Software may be required for any product, including
mission equipment, special inspection equipment, training devices, special tooling, administrative processes, and
record keeping, etc. Software may be required during any phase of a project; however, it is usually delivered only
during the product deployment phase. Frequently, in order for software to execute, a specific software environment
(including hardware and software) must be available; this is part of the administrative data required.
A.4.2.4.1. Selection.
a. Software administrative information: Selected administrative information about software assets is necessary to
maintain the configuration of interfacing systems.
b. Software: Software may be obtained as executable (also known as compiled or object) code or as source code.
Object code is one representation of software; it allows the user to execute the program and use it as it was
designed to be used, but it does not allow the user to change how the software works or what it does. Source
code allow the user to change how the software works or what it does; it also allows the user to automatically
create object code to execute the program.
A.4.2.4.2. Tailoring. Software and software administrative information is typically obtained via DI-CMAN-81551
in the CDRL. Determine if a record copy of the executable software needs to be stored for any reason.9 Determine
if the Government personnel will need to be able to modify the software or if changes to the software will be
accomplished by contracting the modification efforts from a supplier other than the original designer of the software.
See Table A-V for guidance on tailoring requirements for software/software administrative information.

9
Typically record copies of software are necessary to archive environments for application software or to archive application software for
automatic launch routines to allow launch of the software when the user wishes to view the contents of a file.

A-12
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-V. Guidance on tailoring requirements for software and software administrative information.
Source of Does Will Is Archive Copy Delivery Purchase See Notes:
Software software Government of the Software or Electronic CM
Exist Modify Code Required Access Data
Internal No Yes Yes Delivery Yes a, b, d, and g
External Yes Yes Yes Delivery Yes b, d, and h
No Yes Delivery Yes c and i
No c and j
Access Yes c, e, and k
No c and e
No Delivery Yes f and l
No Yes Yes Delivery Yes a, b, d, and h
No Yes Delivery Yes a, c, and i
No a, c, and j
Access Yes a, c, e, and k
No a, c, and e
No N/A Yes a, f, and l

Notes:

a. In the internal tasking directive or the SOW, include the requirement to develop the software according to the
appropriate standard (for example: MIL-STD-498, J-STD-016.0, ISO/IEC 12207, etc.).

b. In internal tasking directive or contract/CDRL, specify that the intention is to procure the source and
executable code (and all rights) to the software.

c. In the contract/CDRL, specify that the intention is to procure a copy of the executable software code.

d. In internal tasking directive or contract/CDRL specify when the software and software administrative
information is to be delivered.

e. Include a requirement in the SOW for a CITIS according to MIL-STD-974; specify at what status (for
example; working, released, etc.) the customer is to be provided access; specify at what point in time the
customer is to be provided access, and in the contract/CDRL state the period of time the performing activity is
to provide access to the executable software.

f. In the contract/CDRL specify when the software administrative information is to be delivered.

g. In the internal tasking directive, specify delivery of executable code according to DIP1 subpacket 1E and
repeat sequence 82-115 for source code. In DIP9, sequence 33 must be blank and sequence 34 must be
nonblank.

h. Cite DI-CMAN-81551 in the CDRL and in the remarks section specify: (1) delivery of executable code
according to the electronic format requirements of data information subpacket 1E and Table DIP1-I of MIL-
STD-2549 and repeat sequence 82-115 for source code, (2) in DIP9, sequence 33 must be blank and sequence
34 must be nonblank.

i. Cite DI-CMAN-81551 in the CDRL and specify when delivery is due. In the remarks section specify: (1)
delivery of executable code according to the electronic format requirements of data information subpacket 1E
and Table DIP1-I of MIL-STD-2549, and (2) in DIP9, sequence 33 must be blank and sequence 34 must be
nonblank.

j. In the contract specify delivery of the executable software by best commercial practices and when it is to be
delivered. (Tasking activity is responsible for updating the CM AIS with the administrative information about
this software.)

A-13
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

k. Cite DI-CMAN-81551 in the CDRL and in the remarks section specify: (1) delivery of executable code
according to the electronic format requirements of data information subpacket 1E and Table DIP1-I of MIL-
STD-2549, and (2) in DIP9, sequence 33 must be nonblank and sequence 34 must be blank.

l. In the contract or in the CDRL for DI-CMAN-81551, specify delivery of software administrative information
according to the electronic format requirements of data information subpacket 1D and Table DIP1-I of MIL-
STD-2549.

A.4.2.5. Software support documents.

A.4.2.5.1. Selection. Software support documents are required for any software product, including mission
equipment, special inspection equipment, training devices, special tooling, administrative processes and record
keeping, etc. Software support documents are used:
a. during the program definition and risk reduction, and engineering and manufacturing development, phases to
document the differences between consecutive versions of software, or to document testing requirements,
methods, and results (see MIL-STD-498 for additional guidance), or
b. during the production, fielding/deployment, and operational support phase when there is a current or future
need for the Government to operate, maintain, or reproduce software or firmware or the systems on which they
are installed (see MIL-STD-498 for additional guidance).
A.4.2.5.2. Tailoring. Software support documents are typically obtained via DIDs such as DI-IPSC-81430, -81432,-
81435, -81436, -81437, -81439, -81442, -81443, -81444, -81445, -81446, -81447, and/or -81448 (or DI-CMAN-
81551 if no other appropriate DID exists) in the CDRL. Decide (1) if the Government wants to buy the originals
(including all rights to change those originals) or copies10 (with, or without, the right to review/adopt changes to
those originals), (2) if the software support documents are to be delivered to the Government repository, or if
perpetual access is to be provided by the performing activity, and (3) whether or not to buy electronic CM data about
the software support documents11. See Table A-VI for tailoring guidance.

Table A-VI. Guidance on tailoring requirements for software support documents.

Purchase Delivery or Access Purchase Internal Tasking or See Notes:
Originals or Electronic CM External Buy
Copies Data
Originals Delivery Yes Internal a, c, and f
External a, c, and g
No External a, c, and h
Access Yes External a, d, and i
No External a, d, and j
Copies Delivery Yes External b, e, and g
No External b, e, and h
Access Yes External b, d, and i
No External b, d, and j

Notes:

a. Include in the SOW or internal tasking directive the requirement to create software support documents and
specify which documents are desired according to the guidance in MIL-STD-498. In the CDRL for the
software support documents or in the internal tasking directive specify:

10
Not applicable to internal taskings

11
The tasking activity is responsible for ensuring that the configuration management information required by DIP1 subpacket 1F is extracted
from the software support document(s) and entered into the CM AIS along with the software-support documents when they are received.

A-14
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

(1) that the intention is to procure the originals and all rights (see also A.4.8.8) to the software support
documents

(2) the acceptable electronic format of software support documents (for example: SGML, HTML, etc.)

(3) Specify how the documents are to be identified. (It is recommended that use of Government CAGE and
document numbers be specified.)

b. Include in the SOW or internal tasking directive the requirement to create software support documents and
specify which documents are required. (See MIL-STD-498 for guidance.) In the CDRL for the software
support documents or in theinternal tasking directive specify:

(1) that the intention is to procure copies and, if applicable, the right to review/adopt changes to the original
(see also A.4.8.6) of the software support documents

(2) the acceptable electronic format (for example: SGML, HTML, etc.)

(3) specify how the software support documents are to be identified. (It is recommended that use of
contractor identification and either a contractor-assigned number or title be used.

c. In the internal tasking directive or the CDRL for the software support documents, specify when the documents
are to be delivered. (This is life-cycle phase dependent, see MIL-HDBK-61 for guidance.)

d. Include a requirement in the SOW for a CITIS according to MIL-STD-974; specify at what status (for
example; working, released, etc.) the customer is to be provided access; specify at what point in time the
customer is to be provided access, and in the CDRL for the software support documents include the
requirement for the contractor to provide perpetual12 access to the digital software support documents.

e. In the CDRL for the software support documents, specify when the documents are to be delivered.

f. In the internal tasking directive, specify delivery according to the electronic format requirements of data
information subpacket 1F and Table DIP1-I of MIL-STD-2549. Specify that DIP9 sequence 33 must be
blank and sequence 34 is mandatory.

g. Cite the software support document DID number (or DI-CMAN-81551 if no other appropriate DID exists) in
the CDRL. In the remarks section specify: (1) delivery according to the electronic format requirements of data
information Subpacket 1F and Table DIP1-I of MIL-STD-2549, and (2) that DIP9 sequence 33 must be blank
and sequence 34 is mandatory.

h. Cite the software support document DID number (or DI-CMAN-81551 if no other appropriate DID exists) in
the CDRL. In the remarks block, specify delivery of the documents according to MIL-STD-1840.

i. Cite the software support document DID number (or DI-CMAN-81551 if no other appropriate DID exists) in
the CDRL. In the remarks block, specify: (1) delivery of configuration data for documents according to the
electronic format requirements of data information subpacket 1F and Table DIP1-I of MIL-STD-2549, and (2)
that DIP9 sequence 33 is mandatory and sequence 34 must be blank.

j. Cite the software support document DID number (or DI-CMAN-81551 if no other appropriate DID exists) in
the CDRL. In the remarks block, specify: (1) delivery of a copy of the document/file identification and
location according to the electronic format requirements of data information subpacket 2A, and (2) that DIP9
sequence 33 is mandatory and sequence 34 must be blank.

12
“Perpetual” should be defined in the SOW as some period of time in excess of the expected life-time of the last item to be procured, with
options for additional periods of time.

A-15
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

A.4.3. Selection and tailoring associated with paperless hardware designs.

A.4.3.1. Selection. Paperless designs, also called electronic models, may be required for any product (including
mission equipment, special inspection equipment, training devices, special tooling, etc.) in lieu of engineering
drawings. One advantage to this approach is that the part structure is embedded in the design files. One
disadvantage is that they can not be reviewed without access to the commercial software with which they were
created.13 Selection of electronic models is not recommended unless the program has assured itself that they have the
ability to use information in this format. This option is only available for commercial parts.14 Electronic models can
be used:

a. during the program definition and risk reduction phases to verify preliminary design and engineering and
confirm that the technology is feasible and that the design concept has the potential to be useful in meeting a
specific requirement,

b. during the engineering and manufacturing development phase to describe a specific design approach, provide
the information to produce material for test or experimentation, and for the analytical evaluation of the
inherent ability of the design approach to attain the required performance,

c. during the production, fielding/deployment, and operational support phase when there is a current or future
need for the Government to procure or manufacture the equipment, components, or spares and repair parts
from either the original manufacturer or an alternate source, or

d. during the production, fielding/deployment, and operational support phase, after production, when the
Government will maintain the equipment using indigenous support or will contract maintenance support from a
supplier other than the original designer of the equipment.

A.4.3.2. Tailoring. Electronic part models are typically obtained via DI-CMAN-81553 in the CDRL. Decide (1) if
the Government wants to buy the originals (including all rights to change those originals) or copies (with, or without,
the right to review/adopt changes to those originals), (2) if the electronic models are to be delivered to the
Government repository, or if perpetual access is to be provided by the performing activity. If the decision is to buy
the originals, determine that an archive copy of the appropriate application software is available. See Table A-VII
for guidance on tailoring.

Table A-VII. Guidance on tailoring requirements for electronic models (paperless drawings).
Purchase Originals or Copies Delivery or Access See Notes:
Originals Delivery a, c, and f
Access a, d, and g
Copies Delivery b, e, and f
Access b, d, and g

Notes:

a. Include in the SOW the requirement to create electronic models. Specify that the parts defined by these
models are to be identified by the performing activity identification (preferably CAGE code) and a performing
activity assigned unique part number. In the CDRL for the electronic part model or in the internal tasking
directive specify:

(1) that the intention is to procure the originals and all rights (see also A.4.8.8) to the electronic part models

(2) the acceptable electronic format of electronic models (for example: ProEngineer, ISO 10303-AP 203)

13
Translation between commercial tools may be possible by specifying delivery in ISO-10303 AP 203 format (STEP).

14
This limitation is because the DoD does not have a methodology for identifying parts without an associated drawing or material
specification. This does not restrict the ordering of electronic models in conjunction with engineering drawings, program-unique
specifications, or standardization documents. (See also: A.4.2.1, A.4.2.2, and A.4.2.3.)

A-16
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

b. Include in the SOW the requirement to create electronic part models. Require that the parts defined by the
models be identified by use of Contractor source identification (preferably CAGE code) and contractor-
assigned part numbers. In the CDRL for the electronic part model specify:

(1) that the intention is to procure copies and if applicable, the right to review/adopt changes to the original
(see also A.4.8.6) of the electronic part models

(2) the acceptable electronic format (for example: ProEngineer, ISO-10303 AP 203)

c. In the CDRL for the electronic part model, specify when the documents are to be delivered.

d. Include a requirement in the SOW for a CITIS according to MIL-STD-974; specify at what status (for
example; working, released, etc.) the customer is to be provided access; specify at what point in time the
customer is to be provided access, and in the CDRL for the electronic part model include the requirement for
the contractor to provide perpetual15 access to the digital electronic part models.

e. In the CDRL for the electronic part model, specify when the models are to be delivered.

f. Cite DI-CMAN-81553 in the CDRL and specify: (1) delivery according to the electronic format requirements
of data information Subpacket 3A and Table DIP3-I of MIL-STD-2549, (2) that sequence 38 is mandatory,
and (3) that in DIP9 sequence 33 must be blank and sequence 34 is mandatory.

g. Cite DI-CMAN-81553 in the CDRL and specify: (1) delivery according to the electronic format requirements
of data information Subpacket 3A and Table DIP3-I of MIL-STD-2549, (2) that sequence 38 is mandatory,
and (3) that in DIP9 sequence 33 is mandatory and sequence 34 must be blank.

A.4.4. Selection and tailoring associated with general documents and document supplements.

A.4.4.1 General documents.

A.4.4.1.1. Selection. General documents include plans, procedures, analyses, books, technical manuals, etc. which
are required by the Government for any reason and which are not covered elsewhere in this appendix. Various
documents in this category can be required during any phase of a program, or independent of any program.

A.4.4.1.2. Tailoring. Documents are typically obtained via a DID for the document (or DI-CMAN-81552 if no
other appropriate DID exists) in the CDRL. [See DoD 5010.12-L, Acquisition Management and Data Requirements
Control List (AMSDL) for existing DIDs for the documents.] Decide (1) if the Government wants to buy the
originals (including all rights to change those originals) or copies16 (with, or without, the right to review/adopt
changes to those originals), (2) if the documents are to be delivered to the Government repository, or if perpetual
access is to be provided by the performing activity, and (3) whether or not to buy electronic CM data about the
17
documents. See Table A-VIII for tailoring guidance.

15
“Perpetual” should be defined in the SOW as some period of time in excess of the expected life-time of the last item to be procured, with
options for additional periods of time.

16
Not applicable to internal taskings

17
The tasking activity is responsible for ensuring that the configuration management information required by DIP2 subpacket 1A is entered
into the CM AIS.

A-17
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-VIII. Guidance on tailoring requirements for general documents.

Purchase Delivery or Purchase Internal Tasking or See Notes:
Originals or Access Electronic CM External Buy
Copies Data
Originals Delivery Yes Internal a, c, and e
External a, c, and f
No External a, c, and g
Access Yes External a, d, and h
No External a, d, and k
Copies Delivery Yes External b, c, and f
No External b, c, and g
Access Yes External b, d, and h
No External b, d, and i

Notes:

a. Include in the SOW or in the internal tasking directive the requirement to create documents and specify which
documents are desired. In the CDRL for the document or in the internal tasking directive specify:

(1) that the intention is to procure the originals and all rights (see also A.4.8.8) to the documents

(2) the acceptable electronic format of documents (for example: SGML, HTML, etc.)

(3) Specify how the documents are to be identified. (It is recommended that use of Government CAGE and
document numbers be specified.)

b. Include in the SOW the requirement to create the documents and specify which documents are required. In the
CDRL for the document specify:

(1) that the intention is to procure copies and if applicable, the right to review/adopt changes to the original
(see also A.4.8.6) of the documents

(2) the acceptable electronic format (for example: SGML, HTML, etc.)

(3) specify how the documents are to be identified. (It is recommended that use of Contractor identification
and either a contractor-assigned number or title be used.

c. In the internal tasking directive or CDRL for the document, specify when the documents are to be delivered.

d. Include a requirement in the SOW for a CITIS according to MIL-STD-974; specify at what status (for
example; working, released, etc.) the customer is to be provided access; specify at what point in time the
customer is to be provided access, and in the CDRL for the document include the requirement for the
contractor to provide perpetual18 access to the digital documents.

e. In the internal tasking directive, specify delivery according to the electronic format requirements of data
information subpacket 2A and Table DIP2-I of MIL-STD-2549. Specify that DIP9 sequence 33 must be blank
and sequence 34 is mandatory.

f. Cite the document DID number (or DI-CMAN-81552 if no other appropriate DID exists) in the CDRL and, in
the remarks section, specify: (1) delivery according to the electronic format requirements of data information
Subpacket 2A and Table DIP2-I of MIL-STD-2549, and (2) that DIP9 sequence 33 must be blank and
sequence 34 is mandatory.

18
“Perpetual” should be defined in the SOW as some period of time in excess of the expected life-time of the last item to be procured to
which this document applies, with options for additional periods of time.

A-18
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

g. In the CDRL for the document, specify delivery of the document according to MIL-STD-1840.

h. Cite the document DID number (or DI-CMAN-81552 if no other appropriate DID exists in the CDRL and, in
the remarks section, specify: (1) delivery of configuration data for documents according to the electronic
format requirements of data information subpacket 2A and Table DIP2-I of MIL-STD-2549, and (2) that DIP9
sequence 33 is mandatory and sequence 34 must be blank.

i. Cite the document DID number (or DI-CMAN-81552 if no other appropriate DID exists in the CDRL and, in
the remarks section, specify: (1)delivery of a copy of the document/file identification and location according to
the electronic format requirements of data information subpacket 2A and Table DIP2-I of MIL-STD-2549, and
(2) that DIP9 sequence 33 is mandatory and sequence 34 must be blank.

A.4.4.2. Document supplements. Document supplements are used to prevent the necessity and cost of re-
distributing an entire paper document when only a portion of the document has changed and to expedite the
distribution of changes to a document when paper is the primary medium. As a result, complex tiered systems of
identifying changes to revisions, notices to revisions, supplements to changes, etc. have been developed. They are
treated as a separate category only because of these specialized identification requirements.

A.4.4.2.1. Selection. Supplements are used:

a. to distribute changes to revisions of military technical manuals,

b. to distribute (routine, operational, safety, and page) supplements to military technical manuals, or

c. to archive page change notices to program-unique specifications which were created under the requirements of
standardization documents that have been canceled (for example; MIL-STD-490 and MIL-STDs-480, -483, or
-973).

A.4.4.2.2. Tailoring. Document supplements are typically obtained via a DID for the supplement (or DI-CMAN-
81552 if no other appropriate DID exists) in the CDRL. [See DoD 5010.12-L, Acquisition Management and Data
Requirements Control List (AMSDL) for existing DIDs for the documents.] The Government requirements for
acquiring originals, or copies, of supplements are usually identical to the requirements established for the basic
document (see A.4.4.1.2 and Table A-VIII Notes a and b). In the internal tasking directive or the SOW, state what
kind of supplement is required and to which document. If the supplement is to be created internally to the
Government, include the requirement in the internal tasking directive to deliver the supplement according to the
electronic format requirements of data information subpacket 2A and Table DIP2-I of MIL-STD-2549. If the
supplement is to be created externally to the Government, cite the DID number for the supplement (or DI-CMAN-
81552, if no other appropriate DID exists) in the CDRL and specify delivery according to the electronic format
requirements of data information subpacket 2A and Table DIP2-I of MIL-STD-2549.

A.4.5. Selection and tailoring associated with product/asset configuration information.

A.4.5.1. Basic part/material identification information.

A.4.5.1.1. Selection. This basic information about parts and materials is used:

a. during the program definition and risk reduction, and engineering and manufacturing development phases to
identify the parts/materials which are the building blocks for the product (see MIL-STD-100 for additional
guidance),

b. during the production, fielding/deployment, and operational support phase when there is a current or future
need for the Government to repair or maintain equipment, or procure, stock, or distribute spare parts for the
repair and maintenance of equipment, or

c. during all phases to identify approved equivalent/replacement/superseded/substitute parts/materials.

A-19
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

A.4.5.1.2. Tailoring.

a. Basic part design identification is usually obtained by ordering the design document or paperless design for the
part (see also: A.4.2.1, A.4.2.2, A.4.2.3, A.4.2.4, and A.4.3); however, it may be ordered by specifying the part
design-source and part identifier and requesting in the internal tasking directive that information on the part be
delivered according to the electronic format requirements of data information subpacket 3A and Table DIP3-I
of MIL-STD-2549; or cite DI-CMAN-81553 in the CDRL and, in the remarks section, specify that
information on the part be delivered according to the electronic format requirements of data information
subpacket 3A and Table DIP3-I of MIL-STD-2549.

b. For internal design work, include in the internal tasking directive the requirement that replacement/
superseded/substitute item information be reported simultaneously with the approval of the design documents
which identify the replacement/superseded/substitute items and the unrestricted release of the items. Specify
that this information is to be reported according to the electronic format requirements of data information
subpacket 3H and Table DIP3-I of MIL-STD-2549.

c. For external design work, include in the SOW the requirement that replacement/superseded/substitute item
information be reported simultaneously with the incorporation of the design documents which identify the
replacement/superseded/substitute items into the configuration documentation adopted by the tasking activity
or for which the tasking activity is the CDCA. Cite DI-CMAN-81553 in the CDRL and, in the remarks
section, specify that this information is to be reported according to the electronic format requirements of data
information subpacket 3H and Table DIP3-I of MIL-STD-2549.

d. When parts, materials, or assemblies are ordered from a performing activity which is not the original design
activity for the item, and when it is known that the performing activity (supplier) has assigned alternate
identifiers to the parts, material, or assemblies, cite DI-CMAN-81553 in the CDRL and, in the remarks
section, specify the requirement to report performing activity-assigned equivalent identifiers19 according to the
electronic format requirements of data information subpacket 3H and Table DIP3-I of MIL-STD-2549 (or
include the electronic format requirements of data information subpacket 3H and Table DIP3-I of MIL-STD-
2549 in internal tasking directives).

e. When parts, materials, or assemblies are to be designed by a performing activity and are to be initially
identified by the tasking activity CAGE code and tasking activity-provided part numbers/material identifiers,
and when it is known that the performing activity assigns alternate identifiers to the parts/materials for its
internal use, cite DI-CMAN-81553 in the CDRL and, in the remarks section, specify the requirement to report
performing activity-assigned equivalent identifiers19 according to the electronic format requirements of data
information subpacket 3H and Table DIP3-I of MIL-STD-2549.

A.4.5.2. National stock number information.

A.4.5.2.1. Selection.

a. NSN assignment is requested during the engineering and manufacturing development phase to identify the
parts/materials which will be delivered to the Government when there is a current or future need for the
Government to repair or maintain equipment, or procure, stock, or distribute spare parts for the repair and
maintenance of equipment, and which therefore, will be entered into the Government supply system.

b. During the production, fielding/deployment, and operational support phase, NSNs are marked on items and
their packaging as supply identification.

c. During the logistical support phase NSNs are used for determining stock levels, ordering replacement parts,
and can be used for reporting maintenance/repair/modification actions.

d. This basic information about national stock numbers (NSN) is used during all phases to identify approved
replacement/superseded/substitute parts/materials.

19
These alternate identifiers are stock numbers because only the original design activity can assign a part number; however, frequently
companies refer to these alternate identifiers by terms such as ‘company part numbers’ or ‘internal part numbers’.

A-20
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

a. Typically, during system definition, the performing activity is developing the system performance specification
and the interface requirements documents (drawings or specifications) with other systems, and therefore is the
CDCA of these documents. When this functional configuration documentation is approved, it forms the
functional baseline. At the end of system definition or early in allocated performance definition, the CDCA of
the functional configuration documentation is typically moved to the Government tasking activity.

b. During allocated performance definition, the performing activity is developing the top-level allocated
performance specification(s), allocating the requirements to lower-level configuration items and developing
specifications for, and interface requirements between, those lower level items. When this allocated
configuration documentation is approved, it forms the allocated baseline. The performing activity also
develops the engineering drawings necessary to build models and prototypes to demonstrate the technical
feasibility of the requirements. During this stage of the design maturity, the performing activity is the CDCA
for these emerging specifications and drawings. Typically at the end of allocated performance definition or
early in design definition, the CDCA of the top-level allocated performance specification(s) (top-level
allocated configuration documentation) is moved to the Government tasking activity; CDCA of the other
documents remains with the performing activity.

c. During design definition, the performing activity is developing the product design specifications, engineering
drawings, and associated lists. When this product configuration documentation is approved, it forms the
product baseline. As part of this design definition process the performing activity often must re-allocate
requirements between CIs and thus must change the allocated performance specifications and interface
drawings for which it is the CDCA. Also, various standardization documents are usually adopted by the
performing activity as part of the product baseline. At the end of design definition or early in production, the
CDCA of the remaining allocated performance specifications and interface drawings (the remaining allocated
configuration documentation) is moved to the Government tasking activity. If the tasking activity is executing
a performance-based procurement, the CDCA of the product configuration documentation, which defines the
product, remains with the performing activity20. If, however, the tasking activity is executing a design-based
procurement, at the end of design definition or early in production, the tasking activity can either:

(1) have the CDCA of all item-unique product configuration documentation moved to the tasking activity,21
or

(2) establish a contractual product baseline for the production, operations and support stage of the design
maturity, and let the CDCA of the product configuration documentation remain unchanged.

d. During production, operations and support, the tasking activity places orders for the product either by citing
the appropriate item allocated performance specification (for a performance-based procurement) or by citing
the part number of the item (for a design-based procurement). At the end of production, if the tasking activity
has not already done so, the tasking activity should either obtain a copy set of all the product specifications
and drawings, or arrange for perpetual electronic access to the product specifications and drawings (see also:
A.4.2).

e. During post production operations and support, proposed changes to the design of delivered assets may use
either ECPs or Modification Requests, depending primarily on the type of procurement executed during
production.

A.4.6.1.3. Tailoring. ECPs are typically obtained via DID DI-CMAN-81554 in the CDRL. Determine who will be
responsible for logistics support of the delivered item and who will be responsible for documenting the impact to
logistics support that will result upon approval of proposed changes. See Table A-XI for tailoring guidance.

20
This excludes any standardization documents included in the product baseline; their CDCA remains unchanged.

21
In this case, the tasking activity usually has chosen to have specifications and drawings identified by the tasking activity CAGE code and
tasking activity-provided document numbers.

A-24
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-XI. Guidance on Tailoring Requirements for ECPs.

Performance- or Logistics
Design Maturity Internal or
Design-Based In Production Support See Notes:
(see Table A-II) External Tasking
Acquisition Responsibility
system definition,
allocated Internal a and c
Performance or
performance
Design External
definition, and b and d
design definition
Internal a and c
Yes
Performance External b and d
No Internal a, c, and h
Internal a, c, and i
Government is
responsible for
production, b, d, e, and j
identifying
operations & logistics impacts
support and post
production Government and
operations & Yes contractor share
support Design External responsibility to b, d, f, and j
identify logistics
impacts
Contractor is
responsible for
b, d, g, and j
identifying
logistics impacts
No Internal a, h, and k

Notes:

a. In the internal tasking directive, require the creation of ECPs to document proposed changes to the functional
and allocated configuration documentation for which the Government is the CDCA. Require delivery of the
ECPs to the CDCA and tasking activity according to the electronic format requirements of data information
subpacket 4C, 4D, and 4E, as applicable, and Table DIP4-I of MIL-STD-2549.

b. In the SOW, require the creation of ECPs to document proposed changes to the functional and allocated
configuration documentation for which the Government is the CDCA. Cite DI-CMAN-81554 in the CDRL
and require delivery of the ECPs to the CDCA and tasking activity according to the electronic format
requirements of data information subpacket 4C, 4D, and 4E, as applicable, and Table DIP4-I of MIL-STD-
2549.

c. In the internal tasking directive, require the creation of related ECPs if documents from more than one CDCA
are affected by a single change. Require coordination of the ECPs with Application Activities.

d. In the SOW, require the creation of related ECPs if documents from more than one CDCA are affected by a
single change. Require coordination of the ECPs with Application Activities.

e. In the SOW, include a statement that the Contractor is not responsible for the documentation of the logistics
support impact of proposed ECPs.

A-25
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

f. In the SOW, specify the division of responsibility between the Government and contractor for documenting
the logistics support impact of proposed ECPs.

g. In the SOW, require the contractor to document the logistics support impact of all Class I ECPs which are
proposed by the contractor.

h. In the internal tasking directive, require the creation of Modification Requests to document proposed changes
which involve any product configuration documentation for which the Government is not the CDCA. (See
also: A.4.6.3.)

i. In the internal tasking directive, require the creation of ECPs to document proposed changes to the product
configuration documentation. Require delivery of the ECPs to the CDCA and tasking activity according to the
electronic format requirements of data information subpacket 4A through 4F, as applicable, and Table DIP4-I
of MIL-STD-2549.

j. In the SOW, require the creation of ECPs to document proposed changes to the product configuration
documentation. Cite DI-CMAN-81554 in the CDRL and require delivery of the ECPs to the CDCA and
tasking activity according to the electronic format requirements of data information subpackets 4A through
4F, as applicable, and Table DIP4-I of MIL-STD-2549.

k. In the internal tasking directive, require the creation of ECPs to document proposed changes to the product
configuration documentation for which the Government is the CDCA. If documents from more than one
Government CDCA are affected, require the creation of related ECPs. Require coordination of the ECPs with
all Application Activities. Require delivery to the CDCA and tasking activity according to the electronic
format requirements of data information subpacket 4A, 4C, 4D, and 4E, as applicable, and Table DIP4-I of
MIL-STD-2549.

A.4.6.2. Requests for deviation.

A.4.6.2.1. Selection. Requests for deviation are used by a performing activity to request that a tasking activity allow
a limited effectivity change to hardware or software which is contracted to be delivered to the tasking activity. RFDs
are used:

a. during the program definition and risk reduction, engineering and manufacturing development, or production,
fielding/deployment, and operational support phases for a performance based acquisition to request temporary
relief from a functional, interface, or performance requirement on a limited quantity of hardware or software
items which are being built either for completion of the testing necessary to validate that the design meets the
item performance, functional, and interface requirements, or for delivery under a contract, or

b. during the engineering and manufacturing development phase and production, fielding/deployment, and
operational support phase for a design based acquisition to request temporary relief from a design requirement
on a limited quantity of hardware or software items to be delivered under a contract (see EIA IS-649 for
additional guidance).

A.4.6.2.2. Tailoring. Requests for deviation are typically obtained via DI-CMAN-81554 in the CDRL.

a. For internal taskings, specify in the internal tasking directive that RFDs are to be prepared by the performing
activity any time the performing activity wishes to request temporary relief from a requirement of any
functional, allocated or product configuration documentation specified in the internal tasking directive.
Specify that the RFD is to be delivered to the tasking activity according to the electronic format requirements
of data information subpacket 4G and Table DIP4-I of MIL-STD-2549.

b. For external taskings, specify in the SOW that RFDs are to be prepared by the performing activity any time the
performing activity wishes to request temporary relief from a requirement of any functional, allocated or
product configuration documentation specified in the contract/SOW. Cite DI-CMAN-81554 in the CDRL and
specify that the RFD is to be delivered to the tasking activity according to the electronic format requirements
of data information subpacket 4G and Table DIP4-I of MIL-STD-2549.

A.4.6.3. Modification requests.

A-26
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

A.4.6.3.1. Selection. Modification requests document proposed changes to fielded assets and provide a mechanism
for coordination of the proposed changes among all interested parties. Modification requests are used:

a. during the production, fielding/deployment, and operational support phase after completion of production to
propose, justify, and coordinate a change to the configuration of an asset (or limited quantity of assets) such
that upon completion of the change, the asset(s) will no longer comply with design documentation for which
the Government is not the CDCA, or

b. during the production, fielding/deployment, and operational support phase after completion of production to
propose, justify, and coordinate a modification or modernization of all assets of a particular configuration.

A.4.6.3.2. Tailoring. Modification requests are typically obtained via DI-CMAN-81554 in the CDRL. Establish
service or command directives/procedures for preparing modification requests and require that modification requests
be input to the CM AIS according to the electronic format requirements of data information subpacket 4H and Table
DIP4-I of MIL-STD-2549. (If the preparation of Modification Requests is contracted outside the Government, cite
DI-CMAN-81554 in the CDRL and, in the remarks section, specify that the Modification Requests will be delivered
according to the electronic format requirements of data information subpacket 4H and Table DIP4-I of MIL-STD-
2549.)

A.4.6.4. Modification instructions.

A.4.6.4.1. Selection. Modification instructions are used during the production, fielding/deployment, and operational
support phase, and the demilitarization and disposal phase to direct the modification of hardware assets, software
assets, or technical manuals. Modification instructions are known by many names in the DoD, such as TCTOs,
MWOs, Technical Directives, RACs, SHIPALTINST, etc. Sometimes, they are the result of approved ECPs and
sometimes they are the result of approved Modification Requests. Frequently, the creation of a modification
instruction is in conjunction with the creation of a modification kit.

A.4.6.4.2. Tailoring. Modification instructions are typically obtained via DIDs such as DI-CMAN-80225, -80529,
and -81182 and DI-MGMT-81325 (or DI-CMAN-81554 if no other appropriate DID exists) in the CDRL. If the
product CCB approves an ECP which requires the creation of a Modification Instruction, or if the Modification
Request approval authority requires the creation of a Modification Instruction, the Modification Instruction should
be ordered as follows:

a. If the modification instruction is to be prepared internally, include in the internal tasking directive, the
requirement to create the modification instruction, when it is to be delivered, and that it is to be delivered
according to the electronic format requirements of data information subpacket 4I and Table DIP4-I of MIL-
STD-2549 .

b. If the modification instruction is to be prepared externally, include in the SOW, the requirement to create the
modification instruction. If there is a specific format or content requirement, cite the pertinent standard (for
example: DoD-STD-2140 for MACHALT Instructions, MIL-T-38804 for TCTOs, MIL-M-81748 for RACs,
etc.) Cite the modification instruction DID (or DI-CMAN-81554 if no other appropriate DID exists) in the
CDRL and specify when the modification instruction is to be delivered and that it is to be delivered according
to the electronic format requirements of data information subpacket 4I and Table DIP4-I of MIL-STD-2549 .

A.4.7. Selection and tailoring associated with configuration management action item status information.

A.4.7.1. ECP/RFD implementation action status.

A.4.7.1.1. Selection. ECP/RFD implementation action status information is used when it is required to monitor
completion of the actions necessary to fully implement an approved ECP/RFD (for example; for ECPs -
implementing the change in hardware/software; incorporating the change into engineering drawings or program-
unique specifications; designing and procuring new support equipment or documentation; creating, testing,
publishing and disseminating new modification instructions and/or modification kits; etc.; for RFDs - issuance of a
contract modification for consideration due the Government for approving the deviation, implementation of
corrective action to prevent reoccurrence, etc.). This item is useful on major projects where ECP implementation
responsibilities are dispersed among many different organizations or where funding of implementation may be
incremental (for example: only a portion of the units to be retrofitted are funded for retrofit each fiscal year) or by

A-27
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-249
APPENDIX A

functional organization (for example: technical manual changes are funded separately from the hardware
modifications). Using this information helps to prevent tasks from being forgotten.

A.4.7.1.2. Tailoring. ECP/RFD implementation action status information is typically obtained via DI-CMAN-
81555 in the CDRL. See Table A-XII for guidance on tailoring.

Table A-XII. Guidance on tailoring requirements for ECP/RFD action status information.
Applicability Party Responsible for Performing the Action is See Note:
DI-CMAN-81554 (DIP4) subpackets internal a
4E and/or 4F have been ordered
external b
DI-CMAN-81554 (DIP4) internal c
subpacket 4G has been ordered
external d

Notes:

a. Include in the internal tasking directive the requirement to report the status of all assigned ECP
implementation actions according to the electronic format requirements of data information subpacket 5A and
Table DIP5-I of MIL-STD-2549 and specify the frequency of reporting.

b. Include in the SOW the requirement to report the status of all assigned ECP implementation actions. Cite DI-
CMAN-81555 in the CDRL and specify delivery according to the electronic format requirements of data
information subpacket 5A and Table DIP5-I of MIL-STD-2549 and specify the frequency of reporting.

c. Include in the internal tasking directive the requirement to report the status of all assigned RFD
implementation actions according to the electronic format requirements of data information subpacket 5A and
Table DIP5-I of MIL-STD-2549 and specify the frequency of reporting.

d. Include in the SOW the requirement to report the status of all assigned RFD implementation actions. Cite DI-
CMAN-81555 in the CDRL and specify delivery according to the electronic format requirements of data
information subpacket 5A and Table DIP5-I of MIL-STD-2549 and specify the frequency of reporting.

A.4.7.2. Configuration audit action item status.

A.4.7.2.1. Selection. Configuration audit action status information is used after completion of an FCA or PCA at
the end of the engineering and manufacturing development phase to monitor completion of the actions necessary to
correct the discrepancies identified during the FCA or PCA.

A.4.7.2.2. Tailoring. Configuration audit action item status information is typically obtained via DI-CMAN-81555
in the CDRL. Require only if an FCA or PCA is included in the SOW or internal tasking directive. Require PCA
action items only if the Government will assume control of the product configuration documentation after the
completion of the PCA. See Table A-XIII for Tailoring guidance.

Table A-XIII. Guidance on tailoring requirements for FCA/PCA action item status information.
Type of Audit Design Agency Government is to become See Note:
CDCA for PCD
FCA internal N/A a
external N/A b
PCA internal Yes c
external Yes d

Notes:

a. Include in the internal tasking directive the requirement to perform an FCA, to report all actions resulting from
the FCA, and to report the status of those action items from establishment through closure. Specify that the
action items and their status are to be delivered according to the electronic format requirements of data

A-28
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-249
APPENDIX A

information subpacket 5B and Table DIP5-I of MIL-STD-2549. Specify the initial delivery of the action items
as a specific period of time after completion of the FCA meeting and specify the frequency of status updates.

b. Include in the SOW the requirement to perform an FCA, to report all actions resulting from the FCA, and to
report the status of those action items from establishment through closure. Cite DI-CMAN-81555 in the
CDRL and, in the remarks section, specify that the action items and their status are to be delivered according
to the electronic format requirements of data information subpacket 5B and Table DIP5-I of MIL-STD-2549.
Specify the initial delivery of the action items as a specific period of time after completion of the FCA meeting
and specify the frequency of status updates.

c. Include in the internal tasking directive the requirement to perform a PCA, to report all actions resulting from
the PCA, and to report the status of those action items from establishment through closure. Specify that the
action items and their status are to be delivered according to the electronic format requirements of data
information subpacket 5B and Table DIP5-I of MIL-STD-2549. Specify the initial delivery of the action items
as a specific period of time after completion of the PCA meeting and specify the frequency of status updates.

d. Include in the SOW the requirement to perform a PCA, to report all actions resulting from the PCA, and to
report the status of those action items from establishment through closure. Cite DI-CMAN-81555 in the
CDRL and, in the remarks section, specify that the action items and their status are to be delivered according
to the electronic format requirements of data information subpacket 5B and Table DIP5-I of MIL-STD-2549.
Specify the initial delivery of the action items as a specific period of time after completion of the PCA meeting
and specify the frequency of status updates.

A.4.8. Selection and tailoring associated with project management information.

A.4.8.1. Organizational information, including CCB organization.

A.4.8.1.1. Selection. Organizational and CCB information is used to identify organizations and personnel which
participate in the identification or change process for configuration management of documents and assets. This
information can also used by the CM AIS manager to establish passwords, etc.

A.4.8.1.2. Tailoring. Organizational and CCB information is typically obtained via DI-CMAN-81556 in the CDRL.

a. For Government organizations, include a requirement in the internal tasking directive to provide the
informationaccording to the electronic format requirements of data information subpacket 6A1 and Table
DIP6-I and DIP6-II of MIL-STD-2549 at the beginning of a task. Require that changes in personnel who are
to review, release, approve, disapprove documents (including ECPs and RFDs) or CDRL submittals be
identified within a specified number of days according to the electronic format requirements of data
information subpacket 6A2 and Tables DIP6-I and DIP6-II of MIL-STD-2549.

b. For non-Government organizations, include a requirement in the SOW to provide organization and key
personnel information. Cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify: (1) delivery
of the information according to the electronic format requirements of data information subpacket 6A1 and
Tables DIP6-I and DIP6-II of MIL-STD-2549 at the beginning of the contract; (2) that changes in personnel
who are to review, release, submit, approve, disapprove documents (including ECPs and RFDs) or CDRL
submittals be identified within a specified number if days according to the electronic format requirements of
data information subpacket 6A2 and Tables DIP6-I and DIP6-II of MIL-STD-2549 .

c. For Government organizations which are the CDCA for configuration documentation and wish to establish a
CCB with that responsibility, or which have adopted documents and included them in a contractual baseline
and wish to establish a CCB for review and comment of ECPs and review and disposition of RFDs, include in
the internal tasking directive that the CCB identification and membership must be delivered according to the
electronic format requirements of data information subpacket 6B3 and Table DIP6-III of MIL-STD-2549. (If
CCB responsibilities are contracted outside the Government, cite DI-CMAN-81556 in the CDRL and specify
that CCB identification and membership be delivered according to the electronic format requirements of data
information subpacket 6B3 and Table DIP6-III of MIL-STD-2549.)

A.4.8.2. System/CI nomenclature information.

A-29
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

A.4.8.2.1. Selection. System/CI nomenclature information is used:

a. during the program definition and risk reduction and the engineering and manufacturing development phases
to identify the system/CIs and the high-level hierarchy of (and relation among) systems, subsystems, and major
end items and their related documentation, and

b. during all phases to identify the scope of CCB responsibilities.

A.4.8.2.2. Tailoring. System and CI nomenclatures are typically obtained via DI-CMAN-81254 in the CDRL.
System/CI nomenclature information is typically obtained via DI-CMAN-81556 in the CDRL. Determine who will
be responsible for obtaining the nomenclatures for the system/CIs and who will be responsible for reporting that
nomenclature information.

a. If the item is being designed internally, include in an internal tasking directive the requirement to request
nomenclature using DD Form 61 as required by MIL-STD-196, MIL-STD-787, or MIL-STD-1812.22 Include
the requirement to report the assignment of system name(s) and system hierarchical relationships according to
the electronic format requirements of data information subpacket 6B1 and Table DIP6-III of MIL-STD-2549,
and to report the assignment of CI nomenclatures and CI hierarchical relationships according to the electronic
format requirements of data information subpacket 6B2 and Table DIP6-III of MIL-STD-2549.

b. If the design of the item is being created to meet Government program-unique requirements, include in the
SOW the requirement to request nomenclature using DD Form 61 as required by MIL-STD-196, MIL-STD-
787, or MIL-STD-181222 and the requirement to report the nomenclature information. Cite DI-CMAN-81556
in the CDRL and specify the requirement to: (1) report the assignment and updates of CI nomenclatures and CI
hierarchical relationships within a specified period of time after the action is accomplished, and (2) report the
nomenclature information according to the electronic format requirements of data information subpacket 6B2
and Table DIP6-III of MIL-STD-2549 for each CI.

c. If the item is a commercial item, being created to meet Government program-unique requirements, Cite DI-
CMAN-81556 in the CDRL and specify the requirement to report the design-agency assigned CI
nomenclatures and CI hierarchical relationships according to the electronic format requirements of data
information subpacket 6B2 and Table DIP6-III of MIL-STD-2549 for each CI.

A.4.8.3. Contract and CDRL information.

A.4.8.3.1. Selection. Contract and CDRL information is used during all phases to identify contracts, the parties to
the contract, the data delivery requirements, and modifications to either.

a. Contract identification information is always ordered when the work is being performed by an activity external
to the DoD because this information is used for verification of inputs in several other data information packets,
most notably the document protection subpackets, and should be part of the password access system for
documents.

b. CDRL requirements are the tasking activity orders for the delivery of specific packages of technical,
management, and other data, including the delivery addressees, format and timing. The subpacket 6C2 for
CDRL requirements should be ordered only if the Government desires to track delivery and disposition of
technical data or includes the requirement for on-line review and comment on delivered contract technical data
items.

c. Data delivery plan and milestones provide the performing activity delivery dates for the technical data required
by the CDRL; they can be ordered only if the contract includes CDRL requirements.

A.4.8.3.2. Tailoring. Contract and CDRL information is typically obtained via DI-CMAN-81556 in the CDRL.

a. For contract administrative information, include in the internal tasking directive the requirement to deliver
contract administrative information according to the electronic format requirements of data information

22
Other standards for nomenclature may be used provided that they result in unique designations.

A-30
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

subpacket 6C1 and Table DIP6-IV of MIL-STD-2549. (If an external organization is preparing the contract
or responsible for updating the CM AIS, cite DI-CMAN-81556 in the CDRL and require the delivery of
contract administrative information according to the electronic format requirements of data information
subpacket 6C1 and Table DIP6-IV of MIL-STD-2549.)

b. For CDRL information, include in the internal tasking directive, the requirement to deliver the CDRL
according to the electronic format requirements of data information subpacket 6C2 and Table DIP6-IV of
MIL-STD-2549. (If an external organization is preparing the contract or responsible for updating the CM
AIS, cite DI-CMAN-81556 in the CDRL and require the delivery of contract administrative information
according to the electronic format requirements of data information subpacket 6C2 and Table DIP6-IV of
MIL-STD-2549.)

c. For data delivery planning information, in the SOW require that the performing activity plan a schedule for the
delivery of the data required by the CDRL. Cite DI-CMAN-81556 in the CDRL and specify: (1) that the
technical data planned delivery schedule and the contract event milestone schedule upon which it is based be
delivered according to the electronic format requirements of data information subpackets 6C4 and 6C3,
respectively, and Table DIP6-IV of MIL-STD-2549, and (2) the frequency of updates to the contract event
milestone schedule.

A.4.8.4. Review, comment, and disposition status of documents/CDRLs.

A.4.8.4.1. Selection. Document/CDRL status information is used:

a. during all phases of the program when the program concept of operations includes electronic on-line technical
review and comment on documents during the disposition cycle for the documents, including the CDRL
submittal/review/approval cycle, or

b. during all phases of the program when the program concept of operations includes electronic disposition of
documents or approval of CDRL submittals

A.4.8.4.2. Tailoring. Review, comment, and disposition status information are typically obtained via DI-CMAN-
81556 in the CDRL. Actions 2, 6, and 9 in Table A-XIV are required only if the program concept of operations
includes performing on-line review and comment, or storing comments about documents on line. Actions 1, 3, 4, 5,
and 7 are necessary for all documents and address the status of the document. Actions 8 and 10 only apply to CDRL
submittals. In all cases, the action to be performed and to what organization the person performing the action
belongs, determines what needs to be ordered and from whom. See Table A-XIV for guidance on tailoring
requirements for document review, comment, and status information.

A-31
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Table A-XIV. Guidance on tailoring requirements for document review, comment, and status information.
Action If the Action is: It is to be Accomplished by: Internal / Delivery or With CM See
# External Access Data? Notes:
Disposition a Internal Delivery Yes a
3 document personnel at the originating
representation as activity for the document Delivery Yes b and u
part of the release representation External
process for the
document Access Yes b and v
representation
Initiate a document Internal Delivery Yes e
4 revision as part of personnel at the CDCA for
the approval process the document External Delivery Yes f and u
for the document
Access Yes f and v
revision
Submit a document Internal Delivery Yes g
5 revision as part of personnel at the originating
the approval/ activity for the document Yes h, s, and u
adoption process for revision or at an application External Delivery
the document activity No h and w
revision Access Yes h, s, and v
On-line review & Internal Delivery Yes c and i
6 comment on a personnel at the originating External Delivery Yes d, i, and u
document revision activity for the document
as part of the revision Access Yes d, i, and v
document revision Internal Delivery Yes j
approval process personnel at the CDCA for External Delivery Yes k and u
the document Access Yes k and v
Internal Delivery Yes l
personnel at an application External Delivery Yes m and u
activity Access Yes m and v
Disposition a personnel at the CDCA for Internal Delivery Yes e
7 document revision the document External Delivery Yes f and u
as part of the Access Yes f and v
document revision
approval process personnel at an application Internal Delivery Yes n
activity External Delivery Yes o and u
Access Yes o and v
Initiate preparation Delivery Yes p, t, and u
8 of, or submit, a personnel at the performing External
contract data item activity No p and w
Access Yes p, t, and v
On-line review & Internal q
9 comment on a personnel at the tasking
contract data item activity
submittal as part of
the CDRL submittal
approval process
Disposition a Internal r
10 contract data item personnel at the tasking
submittal as part of activity
the CDRL submittal
approval process

A-32
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

Notes:

a. Include in the internal tasking directive the requirement to report the release status of new document
representations of existing documents and initial document representations of new documents/revisions.
Specify delivery according to the electronic format requirements of data information subpacket 6D4 and Table
DIP6-V of MIL-STD-2549.

b. Include in the SOW the requirement to report the release status of new document representations of existing
documents which are under Government CDCA, and initial document representations of new document
revisions to documents which are under Government CDCA. Cite DI-CMAN-81556 in the CDRL and, in the
remarks section, specify delivery according to the electronic format requirements of data information
subpacket 6D4 and Table DIP6-V of MIL-STD-2549.

c. Include in the internal tasking directive the requirement to review and report comments on the content of new
document representations of existing documents, and initial document representations of new
documents/revisions, as part of the document representation release process. Specify delivery according to the
electronic format requirements of data information subpacket 6D1 and Table DIP6-V of MIL-STD-2549.

d. Include in the SOW the requirement to review and report comments on the content of new document
representations of existing documents which are under Government CDCA, and initial document
representations of new document revisions to documents which are under Government CDCA, as part of the
document representation release process. Cite DI-CMAN-81556 in the CDRL and, in the remarks section,
specify delivery according to the electronic format requirements of data information subpacket 6D1 and Table
DIP6-V of MIL-STD-2549.

e. Include in the internal tasking directive the requirement to report the status of new document revisions as part
of the document approval process. Specify delivery according to the electronic format requirements of data
information subpacket 6D5 and Table DIP6-V of MIL-STD-2549.

f. Include in the SOW the requirement to report the status of new document revisions to documents, which are
included in a contractual baseline by the Government, as part of the document approval process. Cite DI-
CMAN-81556 in the CDRL and, in the remarks section, specify delivery according to the electronic format
requirements of data information subpacket 6D5 and Table DIP6-V of MIL-STD-2549.

g. Include in the internal tasking directive the requirement to submit proposed document revisions to the CDCA
for approval and to the AA(s) for adoption. Specify delivery according to the electronic format requirements
of data information subpacket 6D5 and Table DIP6-V of MIL-STD-2549.

h. Include in the SOW the requirement to submit new document revisions to documents which are under
Government CDCA, or which are included in a contractual baseline by the Government, to the CDCA for
approval and to the AA(s) for adoption.

i. This is accomplished by review of the document representation as part of the document representation release
process, see Action 2.

j. Include in the internal tasking directive the requirement to review and report comments on the content of
proposed new documents, and proposed new revisions to existing documents, as part of the document approval
process. Specify delivery according to the electronic format requirements of data information subpacket 6D2
and Table DIP6-V of MIL-STD-2549.

k. Include in the SOW the requirement to review and report comments on the content of proposed new document
revisions of existing documents, which are under Government CDCA, as part of the document approval
process. Cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify delivery according to the
electronic format requirements of data information subpacket 6D2 and Table DIP6-V of MIL-STD-2549.

l. Include in the internal tasking directive the requirement to review and report comments on the content of new
documents, and new revisions to existing documents, proposed for adoption as part of the document adoption

A-33
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

process. Specify delivery according to the electronic format requirements of data information subpacket 6D2
and Table DIP6-V of MIL-STD-2549.

m. Include in the SOW the requirement to review and report comments on the content of new documents, and
revisions of existing documents, which are proposed for adoption as part of the document adoption process.
(This should be limited to documents which are included in, or beng proposed for inclusion in, a contractual
baseline by the Government.) Cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify
delivery according to the electronic format requirements of data information subpacket 6D2 and Table DIP6-V
of MIL-STD-2549 .

n. Include in the internal tasking directive the requirement to report the status of new document revisions as part
of the document adoption process. Specify delivery according to the electronic format requirements of data
information subpacket 6D5 and Table DIP6-V of MIL-STD-2549.

o. Include in the SOW the requirement to report the status of new document revisions to documents as part of the
document adoption process. (This should be limited to documents which are included in a contractual baseline
by the Government.) Cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify delivery
according to the electronic format requirements of data information subpacket 6D5 and Table DIP6-V of MIL-
STD-2549.

p. Include in the SOW the requirement that all contract data submittals will be accomplished electronically and
be accompanied by administrative information required by the CDRL.

q. Include in the internal tasking directive the requirement to review and report comments on the content,
timeliness, and acceptability of contract data item submittals, as part of the contract data item approval
process. Specify delivery according to the electronic format requirements of data information subpacket 6D3
and Table DIP6-V of MIL-STD-2549.

r. Include in the internal tasking directive the requirement to report the status of contract data submittals as part
of the contract data item approval process. Specify delivery according to the electronic format requirements of
data information subpacket 6D6 and Table DIP6-V of MIL-STD-2549.

s. Cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify delivery according to the electronic
format requirements of data information subpacket 6D5 and Table DIP6-V of MIL-STD-2549.

t. Cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify delivery according to the electronic
format requirements of data information subpacket 6C5 and Table DIP6-IV of MIL-STD-2549 .

u. In the CDRL remarks section, specify that DIP9, sequence 33 must be blank and sequence 34 is mandatory.

v. Include in the SOW the requirement to provide a CITIS according to MIL-STD-974. In the CDRL remarks
section, specify that DIP9, sequence 33 is mandatory and sequence 34 must be blank.

w. In the CDRL, specify delivery according to MIL-STD-1840. (In this case, the tasking activity is
responsible for entering the configuration management data into the CM AIS.)

A.4.8.5. CCB decisions and directives.

A.4.8.5.1. Selection. CCB decisions and directives information is used:

a. during all phases of the program when the Government program configuration management plan includes the
establishment of a CCB and it is desirable to store the discussion and results of the CCB, or

b. when it is desired to track the status of ECP/RFD implementation actions.

A.4.8.5.2. Tailoring. CCB decisions and directives information is typically obtained via DI-CMAN-81556 in the
CDRL. In the internal tasking directive which establishes the CCB, require that CCB decisions and implementation
actions resulting from the approval of an ECP/RFD be recorded. Specify the level of detail desired for

A-34
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

implementation actions23. Specify that the CCB results and required implementation actions be delivered according
to the electronic format requirements of data information subpacket 6D7 and Table DIP6-V of MIL-STD-2549. (If
this effort is contracted, cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify delivery according
to the electronic format requirements of data information subpacket 6D7 and Table DIP6-V of MIL-STD-2549.)

A.4.8.6. Document/baseline correlation.

A.4.8.6.1. Selection. This element is a listing of documents24. This information is used:

a. during all phases when the program has decided to maintain a technical baseline consisting of all documents
which document the decisions made during the life of the program,

b. when the Government adopts25 nongovernment configuration documentation to define the product
requirements or design, or

c. when a specific subset of design (or requirements) documents are used in conjunction with a contract to define
a product to be delivered instead of using the complete design set.

A.4.8.6.2. Tailoring. Document/baseline correlation information is typically obtained via DI-CMAN-81556 in the
CDRL. In the internal tasking directive, require identification of documents to be included in a baseline to be
reported according to the electronic format requirements of data information subpacket 6E1 and Table DIP6-VI of
MIL-STD-2549. (If this effort is contracted to an external source, cite DI-CMAN-81556 in the CDRL and, in the
remarks section, specify delivery according to the electronic format requirements of data information subpacket 6E1
and Table DIP6-VI of MIL-STD-2549.)

A.4.8.7. Assign CPIN or PAN.

A.4.8.7.1. Selection. This information is used:

a. by the Army when an alternate identifier (PAN) is used to identify ECPs and RFDs within the service (for
additional information, see U.S. Army Armament Research, Development and Engineering Center
Configuration Management Policy Memos), or

b. by the Air Force when an alternate identifier (CPIN) is used to identify software or software documentation for
the purpose of determining distribution authority (for additional information, see USAF TO 00-5-16 and TO
00-5-17).

A.4.8.7.2. Tailoring. Information about PANs and CPINs is typically obtained via DI-CMAN-81556 in the CDRL.
These identifiers are typically supplied by DoD activities upon receipt of a request from a performing activity for the
issuance of an identifier for a software item or documentation package.

a. For assignment of a CPIN, include in the internal tasking directive or in the SOW the requirement to assign a
CPIN to all software and software documentation in accordance with USAF TO 00-5-16 and to deliver the
information according to the electronic format requirements of data information subpacket 6E2 and Table
DIP6-VI of MIL-STD-2549. If contracting for maintenance of this information, include the requirement to
assign a CPIN to all software and software documentation in accordance with USAF TO 00-5-16 in the SOW;
cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify delivery according to the electronic
format requirements of data information subpacket 6E2 and Table DIP6-VI of MIL-STD-2549.

23
For example: ‘Publish change to technical manual’ as opposed to ‘Draft change to technical manual, create photo-ready copy of technical
manual change, print and bind change to technical manual, distribute change to technical manual’.

24
For the documents themselves, see A.4.2, A.4.3, or A.4.6.

25
No input is required for documents which are included in a FBL, ABL, or PBL if the Government is the CDCA of the document, because
inclusion in the baseline is automatic upon approval by the CDCA.

A-35
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

b. For assignment of a PAN, include the requirement to assign a PAN to all ECPs and/or RFDs and to deliver the
information according to the electronic format requirements of data information subpacket 6E3 and Table
DIP6-VI of MIL-STD-2549, in the internal tasking directive or SOW. If contracting for maintenance of this
information, include in the SOW the requirement to assign a PAN (according to U.S. Army Armament
Research, Development and Engineering Center procedures) to all ECPs and/or RFDs; cite DI-CMAN-81556
in the CDRL and, in the remarks section, specify delivery according to the electronic format requirements of
data information subpacket 6E3 and Table DIP6-VI of MIL-STD-2549.

A.4.8.8. Establish or transfer CDCA of a document; change document custodian; or add, change, or delete
Application Activity (including GLAA).

A.4.8.8.1. Selection. This information is used:

a. during all phases when the Government has required that CDCA for one or more documents be transferred to
the Government,

b. when it is determined by the CDCA that there is reason to ‘subcontract’ the custodian responsibility for one
or more documents, or

c. during all phases when Government activities decide to start using the item/material and establish a contractual
baseline for it or when they have completed their contractual deliveries.

A.4.8.8.2. Tailoring. This information is typically obtained via DI-CMAN-81556 in the CDRL.

a. To transfer CDCA, include in the SOW the requirement that the specified document(s) are to be transferred to
Government CDCA and the exact organization (or CCB) to which document change authority is to transfer.
Cite DI-CMAN-81556 in the CDRL and specify (1) when it is to transfer (usually, for the product TDP,
transfer is after all FCA and PCA action items have been completed), and (2) that transfer of control be
accomplished according to the electronic format requirements of data information subpacket 6F1 and and
Table DIP6-VII of MIL-STD-2549 .

b. To transfer custody of a document, specify in the internal tasking directive or SOW that the transfer of custody
will be reported. In the internal tasking directive, include the requirement to deliver this notification according
to the electronic format requirements of data information subpacket 6F3 and Table DIP6-VII of MIL-STD-
2549. Cite DI-CMAN-81556 in the CDRL and, in the remarks section, specify delivery of this notification
according to the electronic format requirements of data information subpacket 6F3 and Table DIP6-VII of
MIL-STD-2549

c. To add, change, or delete an Application Activity (or GLAA), specify in the internal tasking directive or SOW
that the change in AA/GLAA status will be reported. In the internal tasking directive, include the requirement
to deliver this notification according to the electronic format requirements of data information subpacket 6F4
and Table DIP6-VII of MIL-STD-2549. Cite DI-CMAN-81556 in the CDRL and, in the remarks section,
specify delivery of this notification according to the electronic format requirements of data information
subpacket 6F4 and Table DIP6-VII of MIL-STD-2549.

A.4.8.9. Add a document representation to a document already received.

A.4.8.9.1. Selection. This information is used during all phases when a new document representation is created for
a document and the decision is made to maintain multiple representations (for example: source and executable
software code, AutoCad and IGES drawings, etc.)

A.4.8.9.2. Tailoring. Document representations are typically obtained via DI-CMAN-81556 in the CDRL.
Documents (with the exception of software) usually are initially approved with only one document representation. If
other document representations are required (for example: an AutoCad representation is released, but an IGES
representation is also required), an activity must be tasked to create the alternate representation, release it, and
deliver it to the custodian of the document. To accomplish this:

a. If an internal organization is to be tasked, include the requirement in the internal tasking directive (1) to create
the particular type of document representation required, (2) to review and release it, and (3) to deliver it

A-36
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

according to the electronic format requirements of data information subpacket 6F2 and Table DIP6-VII of
MIL-STD-2549. (If the comments resulting during the review and comment process or the release process
status dates are desired, see A.4.8.4.)

b. If an external organization is to be tasked, include the requirement in the SOW (1) to create the particular type
of document representation required, (2) to review and release it. Cite DI-CMAN-81556 in the CDRL and, in
the remarks section, specify that it is to be delivered according to the electronic format requirements of data
information subpacket 6F2 and Table DIP6-VII of MIL-STD-2549. (If the comments resulting during the
review and comment process or the release process status dates are desired, see A.4.8.4.)

A.5. OTHER DATA ACQUISITION CONSIDERATIONS.

A.5.1. Continuous Acquisition and Life-Cycle Support (CALS) implementation. The following paragraphs
provide guidance on acquiring data products in digital form:

A.5.1.1. Department of Defense policy. DoD Regulation 5000.2-R states that technical data will be prepared,
delivered and used in digital form unless it is not cost-effective for the Government. In addition, maximum use
should be made of available contractor automated data bases.

A.5.1.2. Implementation. MIL-HDBK-59, Continuous Acquisition and Life-Cycle Support (CALS) Program
Implementation Guide, provides information and guidance to personnel responsible for the acquisition and use of
weapon system technical data. Its purpose is to assist in the transition from paper-intensive processes to digital data
delivery and access. In addition to MIL-HDBK-59, Government personnel acquiring data should consult Service or
Agency and Command regulations, directives and instructions for additional information on specifying the delivery
of data in digital form.

A.5.2. Data requirements versus work tasks. Contractual data requirements cannot be used to impose design
requirements on the item being procure, or to impose engineering work tasks on the contractor. Such tasks are
identified in the Statement of Work of the contract or purchase order, or in a design requirements specification.

A.5.3. Previous submission. Government activities acquiring technical data should tailor the delivery and
submission requirements for TDPs to avoid unnecessary charges to the Government resulting from duplicate delivery
of data products.

A-37
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX A

(This page intentionally left blank)

A-38
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

CONFIGURATION STATUS ACCOUNTING RELATIONAL TABLES

B.1. GENERAL

B.1.1. Scope. This appendix establishes the Configuration Status Accounting (CSA) relational tables which
constitute the minimum requirements for the Government CM AIS. This appendix prescribes the use of data
elements and the format of specific CM records to be used for electronic database access. This appendix defines
the business-rule view (also known as the conceptual schema) for the Configuration Management business area for
a CALS data dictionary. This appendix is a mandatory part of the standard. The information contained herein is
intended for compliance.

B.2. APPLICABLE DOCUMENTS

B.2.1. Subsidiary required documents. There are no sub-tier documents required for implementation of this
appendix. The source documents for the various requirements in this appendix (including those cited for legacy
data) are included for information only.

B.2.2. Reference specifications, standards, handbooks and industry standards. A list of documents which may be
referred to as references for understanding the content of this appendix are included in B.6.

B.3. DEFINITIONS

B.3.1. Acronyms used in this appendix. The acronyms in Section 3 of this standard apply to this appendix. In
addition, the following acronyms are used in this Appendix:

AK Alternate Key
CODE Data Element Code, Field Code
FK Foreign Key
K Key
M Mandatory [data element]
O Optional [data element]

B.3.2. Definitions used in this appendix. The definitions in Section 3 of this standard apply to this appendix. In
addition, the following definitions are used in this Appendix:

a. Alternate key. Sometimes there may be more than one attribute or combination of attributes that uniquely
identifies an instance of an entity (for example: a row of a table). These are identified with the letters AK
and a number (for example: AK1). When the table is invoked, values for alternate keys are always
mandatory and cannot be null-valued unless specifically denoted as optional.

b. Assertion. A statement that specifies a condition that must be true. (Cardinality assertions are stated on
the appropriate figure near the relationship to which they apply. all other assertions are in the appropriate
paragraph of Section B.5.

c. Attribute. A property or characteristic that is common to some or all of the instances of an entity.

B-1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

d. Categorization. The classification of instances in an entity (table) into mutually exclusive sub-entities
(also called subtypes) based on the value of a single attribute in the entity. Categorization is used when:

(1) different attributes are applicable to only certain classes of instances, for example, if the entity in a
medical data-base is PATIENTS, it could be categorized by sex because the attribute date-of-last-
pregnancy would not be applicable to all instances in the entity PATIENTS, or

(2) relationships with other entities are only allowed (or are always required) for certain classes of
instances, for example, NOR is a category of document which must always be associated with another
document in the category ECP, but must never be associated with a document in the category
PERIODICAL.

e. Category discriminator. An attribute in an entity, or any ancestor of the entity which determines which
category entity (subtype) contains a specific instance of an entity.

f. Data element code (CODE). A nine-position code, used to identify the DED (also referred to as a field
code). 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 CM AIS. The last three positions of the
code are the table code in which the element first appears. When a key migrates to a new table, thus
becoming a foreign key, it will retain the table code where the key originated, unless the key is required to
assume a "role name" in the new table. (See discussion on categorization limitations in B.4.3.)
Origination of foreign keys which assume role names are defined in the business rules for the data table.

g. Data element definition (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 Element Definitions can be found in Appendix C.

h. Data element string. The concatenation of two or more data element fields to form a new, composite field.

i. 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. It is the intent that these data element
titles conform to the requirements of DoD 8320.1-M-1. There are two types of data element titles:
generic data element titles and standard data element titles.

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

k. Dependent. A constraint between two related entities indicating that no instance of one (child entity) can
exist without being related to an instance of the other (parent entity).

l. Entity. The representation of a set of real or abstract things (people, objects, places, events, ideas,
combination of things, etc.) that are recognized as the same type because they share the same
characteristics and can participate in the same relationships.

m. Field code. See data element code.

n. Foreign key. An element first defined in a higher table in the hierarchy and which is either a key to this
table (shown in the upper portion of the table figure) or is necessary for traversing the table hierarchy, but
not key to this table (shown in the lower portion of the table figure). Values for foreign keys are always
mandatory and cannot be null-valued unless specifically denoted as optional. Foreign keys are denoted by
the letters FK.

B-2
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

o. Identifying. A constraint between two related entities that requires the primary key in one (child entity) to
contain the entire primary key of the other (parent entity).

p. Independent. A condition of a single entity such that the key attributes of the entity are not inherited from
any other entity, or only part of the key attributes of another entity are used as key attributes in the
independent entity.

q. Instance. An instance is a specific set of values assigned to the attributes of an entity. For example, for
the entity EMPLOYEE with attributes name, sex, SSAN, one instance is the values John Doe, M, 123-45-
6789; another instance is the values Mary Kay, F, 987-65-4321.

r. Key data element code (Key). The attribute or combination of attributes that uniquely identify an instance
of the entity (that is, a row of the table) and which is the primary method of ensuring uniqueness of data.
When the table is invoked, values for keys are mandatory and cannot be null-valued.

s. Mandatory. A non-identifying attribute which must be supplied as part of each table entry. (Note: Key,
Alternate Key and Foreign Key attributes are assumed to be mandatory.)

t. Metadata. Data about data; the names and attributes of data entities as stored in the data dictionary.

u. Non-identifying. A specific connection relationship in which some or all of the attributes contained in the
primary key of the parent entity do not participate in the primary key of the child entity.

v. Optional. A foreign key or alternate key attribute which may be omitted as part of a table entry. (Note:
attributes which are not Key, Alternate Key or Foreign Keys are assumed to be optional.)

w. Role name. A uniquely modified standard data element title which describes the use/application of the
data element within a specific relational data table location. This is required when a data element is
inherited by a single table in multiple contexts (for example, a part number in a parts list may be the
assembly part number or a component part number).

x. Table. There are two usages of this term.

(1) In the conceptual-schema in this appendix, it refers to the fully defined list of the contents of an
entity, including the DED Code, DED Title, DED Number and identification of the Key, Alternate
Key, Foreign Key, Optional or Mandatory nature of the element.

(2) In the physical-schema (in this case, the CM AIS database), it refers to the fact that information is
typically stored as a table where the column headings are the entries in the conceptual-schema entity,
and the rows each represent one instance of data.

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

z. Table description. A short statement outlining the contents and associated business rules of the data table.

aa. Table title. A descriptive phrase used to identify the relational table. Sufficient adjectival modifiers are
used with the phrase to ensure unique identification. An abbreviated title is shown in parenthesis and is
used on the figure(s) due to space limitations.

B-3
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.3.3. Definition of symbols.

a. Entity tables. Tables are denoted by rectangles with an internal horizontal dividing line. Each table is
identified by a unique name, unique abbreviated name, and a unique table number.

(1) Independent. A square-cornered table indicates an independent entity, identified solely by its key(s).

(2) Dependent. A round-cornered table indicates a dependent entity, which requires other tables for its
unique identification.

(3) Key/non-key. The data elements which are key to the uniqueness of data instances in a table are
shown in the upper half of the table. Other data elements are shown in the lower half. This
convention is continued by use of a thick horizontal line in the entity content lists in Section B.5.

b. Category discriminator. Category discriminators are denoted by a circle with one or two horizontal
underscores. The attribute used as the discriminator may appear beside the circle.

(1) Complete category discriminator. A category discriminator depicted with a double horizontal
underscore indicates that all possible values of the discriminator are depicted as subtypes within this
document.

(2) Incomplete category discriminator. A category discriminator depicted with a single horizontal
underscore indicates that only some of the possible values of the discriminator are depicted as
subtypes. Incomplete discriminators are usually used when either not all possible values of the
discriminator are known, or when only selected subtypes are of special interest due to additional
attributes or special limited or required relationships.

B.3.4. Definition of relationship lines.

a. Line terminators.

0
(1) Zero, one or more. The ball terminator (—— ) indicates there is zero, one, or more entries in the
table at the terminal end of the connecting line for each entry in the table at the opposite end of the
connecting line.

(2) One or more. The ball terminator with a "P" (positive) (—— 0
P
) indicates that there are one or more
entries in the table at the terminal end of the connecting line for each entry in the table at the opposite
end of the connecting line. If a number appears next to the terminator instead of a "P" (for example:
—— 2
0 ), it means that the specific quantity of entries is required in the table at the terminal end of the
line for each entry in the table at the opposite end of the connecting line.

(3) Zero or one. The ball terminator with a "Z" (zero) (—— Z
0) indicates that pertinent entry in the table
at the terminal end of the relationship must either exist or be null.

(4) Categorization. The lines connecting the parent or generic entity with the categorization symbol and
the categorization symbol with the category entities, or subtypes, are shown without terminators
because the relationship is always one to one; every instance in the parent entity must exist in one,
and only one, of the category entities and vice versa.

B-4
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Lines.

(1) Identifying relation. An identifying relation is indicated by a solid connecting line. The key of the
table at the terminal end of the line includes the key of the other table, which must exist.
Categorizations are always identifying relations.

(2) Non-identifying relation. A non-identifying relation is indicated by a dashed connecting line. The
data of the table at the terminal end of the line includes the key of the table at the other end of the
line; however, this foreign key information is not all part of the key of the dependent entity. The
parent entity must exist.

(3) Optional non-identifying relation. An optional non-identifying relation is indicated by a dashed

connecting line and has a diamond (c— —) at the parent end of the line. The data of the table at the
terminal end of the line includes the key of the table at the other end of the line; however, this foreign
key information is not all part of the key of the dependent entity and the non-key portion may be null-
valued in the dependent entity.

B.4. GENERAL REQUIREMENTS

B.4.1. Standard CSA data elements. Required status accounting information shall be expressed in terms of the
standard CSA DED codes and DED titles listed in the detailed requirements of this Appendix. Substitutes,
alternatives, or variations shall not be used.

B.4.2. Supplemental CSA data elements. Additional CSA data

elements and related features may be added as required and approved by the Government.

B.4.3. Concept. In a relational database system, information is organized 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.
CSA relational tables are two-dimensional matrices of related data. Tables are defined in terms of columns (DED
codes or DED titles) and rows (or multiple instances of the columnar data elements). Information in this format
can be easily visualized and understood. Within each table, certain data may be defined as foreign key, or key.
(Key data is 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-tier data table. The interrelationships and data hierarchy between tables are
only established through common data element keys and data values. The tables listed in this appendix comprise
the total required CSA relational database.

B.4.4. Categorization and assignment of field codes. In general, all documents are identified by a source entity
(for example: a CAGE code: 30003; an organization acronym: ANSI; a company name: Honeywell; an author:
Thomas A. Bruce, etc.), an identifier (for example: a number: 12345, or a title: Designing Quality Databases) and
the type of document (for example: a drawing, specification, report, ECP, etc.). Certain attributes apply to all
documents (for example: the level of security classification). However, some documents have specialized
attributes (for example: an ECP justification code only applies to documents of the type "ECP"). Many documents
have restrictions on how they can be identified (for example: ECPs must be identified by a CAGE code, and a
number; they cannot be primarily identified by an author or title) or on how they relate to other document types
(for example: for a Parts List Drawing to exist, a graphics drawing must also exist). Thus documents in general,
are highly categorized to allow for specification of the various business rules which apply to them. Additionally, a
generic document may be revised; each iteration has the same hierarchical set of categorization as the basic
document. This complexity results in a multi-tier, multi-dimensional decision tree for categorization of any

B-5
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

document. IDEF1x does not lend itself to this problem; it allows multi-tiers, but does not support the multi-
dimensional aspect. However, it can be shown by inspection that if entity "B" is a subtype of "A", and "C" is a
child of "A" with subtype "D" based on the same categorization discriminator as in the "A" to "B" relation, then
any instance in "B" must also exist as an instance in "D". Due to this parallelism, it can be said that "D" is a de
facto child of "B". Where this is the case, the assignment of field codes is based on this observation. Thus, since
CAGNUM003 is assigned to the DED enterprise-defense-logistics--assigned-identification-code in the hierarchy of
entity categorizations (because the entity-type categorization discriminator has the value of "enterprise" and the
enterprise-identification-type-code categorization discriminator has a value of "cage"), CAGNUM003 is also
assigned to the document-source-enterprise-defense-logistics--assigned-identification-code in the hierarchy of
generic document categorization and in the hierarchy of generic document revision categorizations because the
same discriminator values apply. This cannot be modelled in IDEF1x.

B.4.5. Organization. Because of the massiveness and complexity of the business rules of Configuration
Management, the entities are organized into views of various subsets of the overall data requirements. The
relational tables are shown in this appendix by views (functional areas) in the following sequence:

Tables 000-049, Generic document, organization identification and attributes (see B.5.1.)
Tables 050-099, Engineering drawing requirements, including supplementary drawings such as index list,
parts list and data list drawings (see B.5.2.)
Tables 100-149, Program-unique specification requirements (see B.5.3.)
Tables 150-199, Software (both defense and commercial) and related document requirements (see B.5.4.)
Tables 200-249, Part numbers and material identification, parts lists and as-designed (should-build) structure
requirements, and as-built/modified/maintained structure requirements (see B.5.5.)
Tables 250-299, Engineering Change Proposal (ECP) requirements (see B.5.6.)
Tables 300-329, Notice of Revision (NOR) requirements (see B.5.7.)
Tables 330-344, Baselines (see B.5.8.)
Tables 345-349, National Stock Numbers (NSNs) (see B.5.9.)
Tables 350-399, Request for Deviation (RFD) requirements (see B.5.10.)
Tables 400-449, Standardization documents (see B.5.11.)
Tables 450-499, Modification requests, instructions, and kits (see B.5.12.)
Tables 500-549, Serialization and lot control tracking requirements (see B.5.13.)
Tables 550-599, Technical manuals/orders (see B.5.14.)
Tables 600-649, Document supplements (see B.5.15.)
Tables 650-669, Data Item Descriptions (DIDs) (see B.5.16.)
Tables 670-674, Procuring Activity Numbers (PANs) (see B.5.17.)
Tables 675-689, Audit action tracking requirements (see B.5.18.)
Tables 690-709, Configuration item nomenclature, Configuration Control Board (CCB) identification and
CCB directives (see B.5.19.)
Tables 710-799, Reserved
Tables 800-849, Document representations identification and release process (see B.5.20.)
Tables 850-899, Document revision approval/adoption processes (see B.5.21.)
Tables 900-909, Files (see B.5.22.)
Tables 910-939, Commercial documents, part numbers, and materials (see B.5.23.)
Tables 940-949, Addresses (see B.5.24.)
Tables 950-999, Contract and Contract Data Requirements List (CDRL) Frequirements (see B.5.25.)

B.4.6. Functional CSA relational table listing and table relationships. At the beginning of each functional area,
there is a set of figures showing the data table relationships. Each figure depicts the table number and abbreviated
title (for example: for DWGREV/051, "DWGREV" is the abbreviated title, and "051" is the table number).
Starting with independent entities (or dependent entities from another page), table keys are migrated down to each
successive level of related tables shown through the line relationships. The key fields for each table are shown in
the upper portion of the table. Selected attributes (usually those fields which are alternate keys, or which are

B-6
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

inherited foreign keys necessary for climbing back up the hierarchy but which are not key to the particular table)
are included in the lower half of the table. The tables are connected by lines which indicate the relationship of the
information in the connected tables. The tables in the figures represent the CSA data model at the key-based level.
(The corresponding fully attributed tables are included in the accompanying text.)

B.4.7. CSA relational tables. The detailed portion of each view contains each CSA table, a brief description of
the table contents and business rules, an explanation of any functional dependencies, and the content of the table
elements. The CSA tables at this level are "fully-attributed." Each table contains the following entries:

a. Table code

b. Table title (full title and abbreviation)

c. Table description and any pertinent business rules (assertions)

d. Columnar listing of the entity contents

(1) Field code

(2) DED title or role name
(3) DED number
(4) Key indicator

B.5. DETAILED REQUIREMENTS

B.5.1. Generic and miscellaneous. Entity tables numbered in the range of 000 through 049 contain the
identification of a generic entity which issues documents, the identification of a generic document, and the identity
of a generic document revision. Each of these is categorized at several levels. Since the same discriminators are
used in each of the categorization hierarchies, a logical matrix exists between corresponding subtypes of each
hierarchy. Since all other documents addressed elsewhere in this database are subtypes of these generic entities, all
the attributes of the generic entities apply to the specific documents addressed throughout this appendix.
Additionally, this section includes several miscellaneous tables which are applicable to several applications, such
as security classification, Government rights in technical data, etc. The relationships between these various entity
tables are depicted in Figures 01GEN1 through 01GEN6.

B.5.1.1. Table 000, Generic Entity Identification (ENTITY-IDENTIFIER). This is a 'virtual' table; it is included
in the conceptual diagram only to show the concept of an entity identifier. It is not expected that a physical
database would include a similar table. It has two subtypes: AUTHOR/001 and ENTERPRISE/002.

Code Data Element Title DED Key

ENTYID000 entity-identifier 0033 K

ENTTYP000 entity-type-code 0076 M

B.5.1.2. Table 001, Author identification (AUTHOR). This table contains author names and is a subtype of Table
ENTITY-IDENTIFIER/000. Author names are one type of document source.

a. Attribute entity-identifier (ENTYID000) inherited from Table 000 assumes the role author-human-name
(AUTNAM001).

B-7
(see 1GEN2, 4SW1, 4SW3, 21REP1,
ENTITY-IDENTIFIER / 000 21REP2, 21REP3, 22REV4, 23FILE1)
entity-identifier
entity-type-code

entity-type-code

H E

AUTHOR / 001 ENTERPRISE / 002 (see 1GEN2, 5PIN1, 5PIN2, 19CI2, 21REP1, 23FILE1)
author-name.entity-identifier (FK) enterprise-identifier.entity-identifier (FK)
enterprise-identification-type-code

enterprise-identification-type-code

ORG
COM
CAG ORGANIZATION / 004 (DOD EDM*)
(see 1GEN2,6ECP1,10RFD1,23FILE1,24COM2, organization-identifier.enterprise-identifier (FK)
COMPANY / 005
24COM3,24COM4) CAGE / 003 (see 3SPEC1, 13TRK1, 13TRK5)
commercial-name.enterprise-identifier (FK) organization-type-identifier
cage-code.enterprise-identifier (FK)
cage-type-code
organization-type-identifier
may have
DOD INT

B-8
an assigned cage-type-code
DOD-ORGANIZATION / 034 (DOD EDM*) INTERNATIONAL-ORGANIZATION / 039 (DOD EDM*)
C
APPENDIX B

us-dod-organization-code.organization-identifier (FK) international-organization-code.organization-identifier (FK)

MIL-STD-2549

G
COM-CAGE / 006 dod-organization-type-identifier
cage-code (FK) may have an assigned
US-NONGOVT
commercial-name (FK) US-GOV-NONDEF
US-NON-GOVT-ORGANIZATION / 036 (DOD EDM*)
OTHER-US-GOVT-ORGANIZATION / 035 (DOD EDM*)
us-nongovernment-organization-code.organization-identifier (FK)
us-government-nondefense-organization-code.organization-identifier (FK)
GOV-CAGE / 007
cage-code (FK)
NON-US-GOVT NON-US-NONGOVT
us-dod-organization-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FOREIGN-GOVT-ORGANIZATION / 037 (DOD EDM) FOREIGN-NON-GOVT-ORGANIZATION / 038 (DOD EDM)

non-us-government-organization-code.organization-identifier (FK) non-us-nongovernment-organization-code.organization-identifier (FK)
FIGURE 01GEN1
GENERIC DEFINITION (Part 1 of 6)
*Defined in the U.S. DOD Enterprise Data Model (EDM)
GENERIC-DOCUMENT / 010 (see 1GEN3,1GEN5,2DWG4,4SW1,5PIN4,6ECP1,7NOR5,8BL1,21REP1,24COM1)
ENTITY-IDENTIFIER / 000 (from 1GEN1)
may be responsible for identification of document-source-entity-identifier.entity-identifier (FK)
entity-identifier document-identifier
may be originator of
entity-type-code document-type-code
may be change-control authority for
document-current-change-control-authority.(entity-identifier,program-name,enterprise-identifier,ci-identifier,office-symbol,ccb-name) (FK)
document-identification-type-code
may be change-control document-originator.entity-identifier (FK)
authority for document-source-entity-type-code
entity-type-code
may be adopted for
may be change-control
application by has iterations
may be custodian for authority for
E
AA / 033 (see REV3)
ENTERPRISE / 002 (from 1GEN1) is OFFICE / 941 (from 25ADD1) application-activity-identifier.(office-symbol,enterprise-identifier) (FK) CCB-CI / 703 (from 19CI2)
enterprise-identifier.entity-identifier (FK) divided
enterprise-identifier (FK) may adopt document-source-entity-identifier (FK) enterprise-identifier
into
office-symbol for application document-identifier (FK) program-name
enterprise-identification-type-code P document-type-code (FK) ccb-name
glaa-code ci-identifier

may be distribution controlling office for

enterprise-identification-type P
GENERIC-DOCREV / 011 (see 1GEN4,1GEN6,2DWG3,2DWG4,3SPEC2,4SW1,6ECP2,8BL1,10RFD2,

B-9
may be custodian for 15SUP1,15SUP2,18AUD1,
document-source-entity-identifier (FK)
21REP1,22REV1,22REV3,
document-identifier (FK)
COM may claim copyrights to 24COM2,26CON2,26CON4)
document-type-code (FK)
APPENDIX B

document-generic-revision
MIL-STD-2549

COMPANY / 005 (from 1GEN1)

may claim proprietary, or document-custodian.(enterprise-identifier entity-identifier) (FK)
commercial-name.enterprise-identifier (FK) limited/restricted data rights to document-custodian-office.office-symbol (FK)
current-security-classification.security-classification (FK)
downgrade-security-classification.security-classification (FK)
copyright-code (FK)
CONDOC / 950 (from 26CON1) may specify copyright-owning-enterprise-identifier.enterprise-identifier (FK)
technical distribution-controlling-enterprise-identifier.enterprise-identifier (FK)
contract-identifier
data rights distribution-code (FK)
distribution-controlling-office.office-symbol (FK)
export-control-code (FK) ACCESS / 018 (see 23FILE1)
technical-data-rights-code (FK) security-access-restriction-code
CLASS / 012 (see 23FILE1) proprietary-rights-code (FK)
CPYRGT / 013 (see 23FILE1)
security-classification contract-identifier (FK)
copyright-code proprietary-data-rights-commercial-name.commercial-name (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

may apply to
may apply to
may have access
may apply to downgrade of restricted by
may apply to
may apply to
may apply to DOC-ACCESS / 019
may apply to
document-source-entity-identifier (FK)
may apply to
document-identifier (FK)
DISTRB / 014 (see 23FILE1) document-type-code (FK)
FIGURE 01GEN2 EXPORT / 015 (see 23FILE1) DATARGT / 016 (see 23FILE1) PROP / 017 (see 23FILE1)
distribution-code document-generic-revision (FK)
GENERIC DEFINITION (Part 2 of 6) export-control-code technical-data-rights-code proprietary-rights-code security-access-restriction-code (FK)
GENERIC-DOC / 010 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-identification-type-code

document-identification-type-code

N
NUMDOC / 020 (de facto child of 002) (see 3SPEC2,15DID1,26CON1)
document-source-enterprise-identifier.document-source-entity-identifier (FK)
document-alphanumeric-identifier.document-identifier (FK)
document-type-code (FK)

enterprise-identification-type-code (from 002)

CAG COM

B-10
(see 2DWG1, 3SPEC1, 6ECP1,
APPENDIX B

7NOR1, 10RFD1)
MIL-STD-2549

CAGE-NUM-DOC / 022 (de facto child of 003)

COMPANY-NUM-DOC / 026 (de facto child of 005 ) (see 24COM1)
document-source-cage-code.document-source-enterprise-identifier (FK)
document-alphanumeric-identifier (FK) commercial-document-source-name.document-source-enterprise-identifier (FK)
document-type-code (FK) document-alphanumeric-identifier (FK)
document-type-code (FK)

ORG
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

ORG-NUM-DOC / 024 (de facto child of 004) (see 14TM1, 14TM4)

document-source-organization-identifier.document-source-enterprise-identifier (FK)
document-alphanumeric-identifier (FK)
document-type-code (FK)
FIGURE 01GEN3
GENERIC DEFINITION (Part 3 of 6)
GENERIC-DOCREV / 011 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-generic-revision

document-identification-type-code
(from 010)
N

NUMDOCREV / 021 (de facto child of 020)(see 3SPEC2,15DID1,26CON2)

document-source-enterprise-identifier.document-source-entity-identifier (FK)
document-alphanumeric-identifier.document-identifier (FK)
document-type-code (FK)
document-generic-revision (FK)

enterprise-identification-type-code (from 002)

B-11
CAG COM
APPENDIX B

(see 2DWG1, 3SPEC1,

MIL-STD-2549

6ECP1,7NOR1,19CI2) COMPANY-NUM-DOCREV / 027 (de facto child of 026)

CAGE-NUM-DOCREV / 023 (de facto child of 022)
document-source-cage-code.document-source-enterprise-identifier (FK) commercial-document-source-name.document-source-enterprise-identifier (FK)
document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
document-type-code (FK) document-type-code (FK)
document-generic-revision (FK) document-generic-revision (FK)

ORG
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

ORG-NUM-DOCREV / 025 (de facto child of 024) (see 14TM2)

document-source-organization-identifier.document-source-enterprise-identifier (FK)
document-alphanumeric-identifier (FK)
document-type-code (FK)
document-generic-revision (FK)
FIGURE 01GEN4
GENERIC DEFINITION (Part 4 OF 6)
GENERIC-DOC / 010 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-identification-type-code

document-identification-type-code

T
TITLED / 040
document-source-entity-identifier (FK)
document-title.document-identifier (FK)
document-type-code (FK)

entity-type-code
(from 000)
H E

B-12
AUTH-TITL-DOC / 042 (de facto child of 001) ENT-TITL-DOC / 044 (de facto child of 002)
author-name.document-source-entity-identifier (FK) document-source-enterprise-identifier.document-source-entity-identifier (FK)
APPENDIX B
MIL-STD-2549

document-title (FK) document-title (FK)

document-type-code (FK) document-type-code (FK)

enterprise-identification-type-code
(from 002)
ORG COM

ORG-TITL-DOC / 046 (de facto child of 004) COMPANY-TITL-DOC / 048 (de facto child of 005)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-source-organization-identifier.document-source-enterprise-identifier (FK) commercial-document-source-name.document-source-enterprise-identifier (FK)

document-title (FK) document-title (FK)
document-type-code (FK) document-type-code (FK)

FIGURE 01GEN5
GENERIC DEFINITION (Part 5 of 6)
GENERIC-DOCREV / 011 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-generic-revision

document-identification-type-code
(from 010)
T
TITLED-DOCREV / 041 (de facto child of 040)
document-source-entity-identifier (FK)
document-title.document-identifier (FK)
document-type-code (FK)
document-generic-revision (FK)

B-13
entity-type-code
APPENDIX B
MIL-STD-2549

(from 000)
H E

AUTH-TITL-DOCREV / 043 (de facto child of 042) ENT-TITL-DOCREV / 045 (de facto child of 044)
author-name.document-source-entity-identifier (FK) document-source-enterprise-identifier.document-source-entity-identifier (FK)
document-title (FK) document-title (FK)
document-type-code (FK) document-type-code (FK)
document-generic-revision (FK) document-generic-revision (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 01GEN6
GENERIC DEFINITION (Part 6 of 6)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

AUTNAM001 author-human-name 0069 FK

B.5.1.3. Table 002, Enterprise identification (ENTERPRISE). This table is a subtype of Table ENTITY-
IDENTIFIER/001, and contains the identifiers of enterprises such as companies, industry standards organizations,
and Government agencies, etc. It has three subtypes: CAGE/003, ORGANIZATION/004, and COMPANY/005.

a. Attribute entity-identifier (ENTYID000) inherited from Table 000 assumes the role enterprise-identifier
(ENTIDN002).

Code Data Element Title DED Key

ENTIDN002 enterprise-identifier 0052 FK

ENTTYP002 enterprise-identification-type-code 0050 M

B.5.1.4. Table 003, Commercial and Government entity code (CAGE). This table is a subtype of Table
ENTERPRISE/002, and contains valid CAGE codes and NSCM codes as listed in Handbook H4. It has two
subtypes: Tables COM-CAGE/034 and GOV-CAGE/035, which associate a commercial or Government (DoD)
organization name with the CAGE (or NSCM) code.

a. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role enterprise-
defense-logistics--assigned-identification-code (CAGNUM003).

Code Data Element Title DED Key

CAGNUM003 enterprise-defense-logistics--assigned-identification-code 0001 FK

CAGTYP003 enterprise-defense-logistics--assigned-identification-type- 0102 M

code

B.5.1.5. Table 004, Organizations identified by acronym (ORGANIZATION). This table is a subtype of Table
ENTERPRISE/002, and contains the identification and name of recognized Government and non-Government
organizations which are identified by acronyms. This table is part of the DOD Enterprise Data Model. According
to the DOD Enterprise Data Model, an organization is defined as an administrative structure with a mission. This
table has six subtypes: DOD-ORGANIZATION/034, OTHER-US-GOVT-ORGANIZATION/0035, US-NON-
GOVT-ORGANIZATION/036, FOREIGN-GOVT-ORGANIZATION/037, FOREIGN-NON-GOVT-
ORGANIZATION/038, and INTERNATIONAL-ORGANIZATION/039).

a. The organization-type-identifier (ORGTYP004) is inherited from Table ORGANIZATION-TYPE (not

shown in Figure 01GEN1) in the DOD Enterprise Data Model.

b. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role organization-
identifier (ORGIDN004).

Code Data Element Title DED Key

ORGIDN004 organization-identifier 0096 FK

ORGTYP004 organization-type-identifier 0095 FK, O

ENTNAM004 enterprise-name 0170 M

B-14
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.1.6. Table 005, Company identification by name (COMPANY). This table is a subtype of Table
ENTERPRISE/002, and contains the name of companies used in this database.

a. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role commercial-
enterprise-name (COMNAM005).

Code Data Element Title DED Key

COMNAM005 commercial-enterprise-name 0170 FK

B.5.1.7. Table 006, Commercial CAGE code (COM-CAGE). This table is a subtype of Table CAGE/003
consisting of those CAGE codes which identify commercial enterprises. It contains the commercial enterprise
name which is associated with the CAGE code.

Code Data Element Title DED Key

CAGNUM003 enterprise-defense-logistics--assigned-identification-code 0001 FK

COMNAM005 commercial-enterprise-name 0170 FK

B.5.1.8. Table 007, Government CAGE code (GOV-CAGE). This table is a subtype of Table CAGE/003
consisting of those CAGE codes which identify U.S. DOD organizations. It contains the organization identifying
acronym which is associated with the CAGE code.

Code Data Element Title DED Key

CAGNUM003 enterprise-defense-logistics--assigned-identification-code 0001 FK

DODORG034 united-states-defense-department-enterprise-acronym- 0002 FK

identification-code

B.5.1.9. Tables 8 and 9. Reserved.

B.5.1.10. Table 010, Document identification (GENERIC-DOCUMENT). This table is designed to permit the
inclusion of all types of documents. It is strongly sub-typed as depicted in Table B-I and the accompanying entity
relation diagrams.

a. The document-current-change-control-authority-entity-identifier (CCCENT010) is usually the same as

either the document originator (indicated in various subtypes of GENERIC-DOCREV/011), or the
document-source-entity-identifier (SRCIDN010); however, it can be some other entity or a configuration
control board. As a result, the value of this element is a concatenation of various inherited fields. The
first 30 characters are the entity-identifier (ENTYID000) inherited from Table 000, or the enterprise-
identifier (ENTIDN002) inherited from either Table 703 or 941. The next 20 characters are either the
enterprise-division-name (OFFSYM941) inherited from Table 941, or blank. The remaining characters
are either blank or the concatenation of the program-name (PROGNM691), program-configuration-
control-board-name (CCBNAM700), and configuration-item-product-identifier (CIIDEN695), all of
which are inherited from Table 703. If document-type-code (DOCTYP010) has a value of 'ECP', then the
value of CCCENT010 for the ECP must be the same as the value of CCCENT010 for each document
listed in Table ECPREV-DOCREV/266 for this instance of GENERIC-DOC and GENERIC-DOCREV.

B-15
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

TABLE B-I. Types of documents supported.

Document Document Identification Document Source Identification Type Code (See App C, DED
Type Type 0100)
(see App C, DED
0004 for enterprise identifier author
definitions of (A)
codes) CAGE organizational acronym company
code (O) name (M)
(C)
ANALYS NUMBER X X

TITLE X X

BOOK TITLE X X X

CONTRCT NUMBER X X

DID NUMBER X DOD X

DIRECTV NUMBER X X

TITLE X X X

DL NUMBER X

DOCSUP NUMBER X X X

DWG NUMBER X X

ECP NUMBER X

IL NUMBER X

MISC NUMBER X X X X

TITLE X X X X

MODINST NUMBER X X X

TITLE X X

MODREQ NUMBER X X X

TITLE X X

NOR NUMBER X

PERIODL NUMBER X X

TITLE X X X

PL NUMBER X X

PLNPROC NUMBER X X

TITLE X X X

P-SPEC NUMBER X

REPORT NUMBER X X X

TITLE X X X

RFD NUMBER X

B-16
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

TABLE B-I. Types of documents supported.

SVD NUMBER X

SW NUMBER X X

TITLE X

SWDOC NUMBER X X

TITLE X

TECHMAN NUMBER USA, USN, USMC X

TITLE X

TRD NUMBER X X

Note: "X" indicates any valid entry is permissible; "blank" indicates that this combination of document-type, document-identification-type and
source-identifier-type is not supported.

b. The value of interface-control-document-indicator-code (ICDCOD010) must be blank unless the value of

document-type-code (DOCTYP010) is 'ANALYS', 'MISC', 'P-SPEC', 'REPORT', or 'STDDOC'. (See
also: Table 051, Field CONTYP051, and Table 912, Field CONTYP912.)

c. Attribute entity-identifier (ENTYID000) inherited from Table 000 assumes the role document-origination-
entity-identifier (ORIGIN010).

d. Attribute entity-identifier (ENTYID000) inherited from Table 000 assumes the role document-source-
entity-identifier (SRCIDN010).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 K
DOCTYP010 document-type-code 0004 K
SRCIDN010 document-source-entity-identifier 0033 FK

CCCENT010 document-current-change-control-authority-identifier 0239 FK

ORIGIN010 document-origination-entity-identifier 0033 FK
CCCADT010 document-change-control-authority-effective-date 0082 M
ENTTYP010 document-source-identification-type-code 0100 M
ICDCOD010 interface-control-document-indicator-code 0030
IDNTYP010 document-identification-type-code 0101 M

B-17
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.1.11. Table 011, Document revision identification and attributes (GENERIC-DOCREV). This table depicts
the typical document revision information. The various security classification codes shown in Figure 01GEN2 are
typical of all documents and, therefore, are included here rather than on each subentity table.

a. The proprietary-data-rights-commercial-enterprise-name (PRPCOM011) is the name of the company

claiming company proprietary rights and/or rights in technical data or software and, therefore, must be
nonblank if the document-company-proprietary-data-rights-code (PRPCOD017) has a value of 'P' or 'S', or
if the technical-document-government-data-rights-code (RGTCOD016) has any value other than 'U' or
'N'. In all other cases, the value of proprietary-data-rights-commercial-enterprise-name must be blank. If
the technical-document-government-data-rights-code (RGTCOD016) has any value other than 'U' or 'N',
the value of document-company-proprietary-data-rights-code (PRPCOD017) must be 'P'.

b. The contract-document-identifier (CONIDN950) must appear as part of the Government rights in

technical data claim text and, therefore, must be nonblank if the technical-document-government-data-
rights-code is anything other than 'U' or 'N'; in all other cases, it is optional. The technical-document-
government-data-rights-expiration-date (RGTEXP011) also must be blank if the value of RGTCOD016 is
'U' or 'N', and must be nonblank for all other values.

c. The copyright-owner-enterprise-identifier (CPYENT011) is the name of the enterprise which has

copyrighted the data and, therefore, must be blank if the document-copyright-code (CPYCOD013) has a
value of 'N'; and must be nonblank for all other values.

d. The document-distribution-controller-enterprise-identifier (DISENT011) and the document-distribution-

controller-enterprise-office-name (DISOFF011) together identify the distribution controlling office which
appears as part of the distribution statement and, therefore, they both must be blank if the value of
document-distribution-statement-code (DISCOD014) is 'N' or 'A' and must be nonblank for all other
values. The document-distribution-restriction-determination-date (DISDAT011) is the date of
determination that a distribution statement is required and, therefore, must be blank if the value of
DISCOD014 has a value of 'N' or 'A' and nonblank for all other values.

e. If the document-current-security-classification-code (SECCOD011) is any value other than 'U' or 'FOUO',

the document-security-classification-date (SCLSDT011) must be nonblank, either the document-security-
declassification-date (SDCLDT011) or the document-security-declassification-process-event-name
(SDCLEV011) must be nonblank, and the document-security-classification-authority-text (SECAUT011)
must be nonblank. Additionally, if the value of SECCOD011 is anything other than 'U', 'C', 'NC', 'NR' or
'FOUO', the value of document-downgrade-security-classification-code (SDWNCD011) may be nonblank;
otherwise, it must be blank. If SDWNCD011 is nonblank, either the document-security-classification-
downgrade-date (SDWNDT011) or the document-security-classification-downgrade-process-event-name
(SDWNEV011) must be nonblank; otherwise, they must be blank. If the value of SECCOD011 is 'U' or
'FOUO', then, the values of SCLSDT011, SDCLDT011, SDCLEV011, SDWNCD011, SDWNDT011,
SDWNEV011, and SECAUT011 must be blank.

f. If the value of document-identification-type-code in Table 010 is 'T', then the value of document-identifier
(DOCIDN010) and document-name (DOCTIT011) must be the same.

g. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role copyright-owner-
enterprise-identifier (CPYENT011).

h. Attribute enterprise-office-name (OFFSYM941) inherited from Table 941 assumes the role document-
custodial-enterprise-office-name (CUSOFF011).

B-18
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

i. Attribute entity-identifier (ENTYID000) inherited from Table 000 and enterprise-identifier (ENTIDN002)
inherited from Table 941 must have the same value and merge to assume the role document-custodial-
entity-identifier (CUSORG011).

j. Attribute enterprise-identifier (ENTIDN002) inherited from Table 941 assumes the role document-
distribution-controller-enterprise-identifier (DISENT011).

k. Attribute enterprise-office-name (OFFSYM941) inherited from Table 941 assumes the role document-
distribution-controller-enterprise-office-name (DISOFF011).

l. Attribute commercial-enterprise-name (COMNAM005) inherited from Table 005 assumes the role
proprietary-data-rights-commercial-enterprise-name (PRPCOM011).

m. Attribute document-security-classification-code (SECCOD012) inherited from Table 012 assumes the role
document-downgrade-security-classification-code (SDWNCD011).

n. Attribute document-security-classification-code (SECCOD012) inherited from Table 012 assumes the role
document-current-security-classification-code (SECCOD011).

Code Data Element Title DED Key

DOCREV011 document-generic-revision-identifier 0243 K
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

CONIDN950 contract-document-identifier 0015 FK, O

CPYCOD013 document-copyright-code 0012 FK
CPYENT011 copyright-owner-enterprise-identifier 0052 FK, O
CUSOFF011 document-custodial-enterprise-office-name 0044 FK, O
CUSORG011 document-custodial-entity-identifier 0033 FK
DISCOD014 document-distribution-statement-code 0014 FK
DISENT011 document-distribution-controller-enterprise-identifier 0052 FK, O
DISOFF011 document-distribution-controller-enterprise-office-name 0044 FK, O
EXPCOD015 document-export-control-code 0079 FK
PRPCOD017 document-company-proprietary-data-rights-code 0084 FK
PRPCOM011 proprietary-data-rights-commercial-enterprise-name 0170 FK, O
RGTCOD016 technical-document-government-data-rights-code 0022 FK
SDWNCD011 document-downgrade-security-classification-code 0010 FK, O
SECCOD011 document-current-security-classification-code 0010 FK
DISDAT011 document-distribution-restriction-determination-date 0082
DOCTIT011 document-name 0008 M
PREPDT011 document-preparation-date 0082 M
RGTEXP011 technical-document-government-data-rights-expiration-date 0082
SCLSDT011 document-security-classification-date 0082

B-19
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SDCLDT011 document-security-declassification-date 0082

SDCLEV011 document-security-declassification-process-event-name 0156
SDWNDT011 document-security-classification-downgrade-date 0082
SDWNEV011 document-security-classification-downgrade-process-event- 0156
name
SECAUT011 document-security-classification-authority-text 0155

B.5.1.12. Table 012, Security classification (CLASS). This table contains the Government security
classification codes and their meanings. It is used to standardize the full text or meaning of a classification when
extracted for inclusion within a report or on CITIS display transactions.

Code Data Element Title DED Key

SECCOD012 document-security-classification-code 0010 K

SECCLS012 document-security-classification-name 0011 M

B.5.1.13. Table 013, Copyright (CPYRGT). This table contains the copyright codes and their meanings. It is
used to standardize the full text or meaning of a copyright statement when extracted for inclusion within a report
or on CITIS display transactions.

Code Data Element Title DED Key

CPYCOD013 document-copyright-code 0012 K

CPYTXT013 document-copyright-text 0013 M

B.5.1.14. Table 014, Distribution Code (DISTRB). This table contains the Government distribution statement
codes and their long and short form meanings. Some document distribution statements require a reason for
limiting the distribution. A code is assigned to each statement/reason combination and is used to standardize the
full text or meaning of a distribution statement when extracted for inclusion within a report or on CITIS display
transactions.

Code Data Element Title DED Key

DISCOD014 document-distribution-statement-code 0014 K

LNSTMT014 document-long-distribution-statement-text 0016 M

SHSTMT014 document-short-distribution-statement-text 0016 M

B.5.1.15. Table 015, Export Control Warning (EXPORT). This table contains the Government export control
codes and their meanings. It is used to standardize the full text or meaning of the export control statement when
extracted for inclusion within a report or on CITIS display transactions.

B-20
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

EXPCOD015 document-export-control-code 0079 K

EXPTXT015 document-export-control-warning-text 0080 M

B.5.1.16. Table 016, Government rights in technical data and software (DATARGT). This table contains the
Government rights in technical data and software codes and their short and long text meanings. It is used to
standardize the full text or meaning of a technical data rights code when extracted for inclusion within a report or
on CITIS display transactions.

Code Data Element Title DED Key

RGTCOD016 technical-document-government-data-rights-code 0022 K

RGTTXT016 technical-document-government-data-rights-text 0083 M

B.5.1.17. Table 017, Company proprietary rights (PROP). This table contains the company proprietary rights
codes (including competition sensitive) and their meanings. It is used to standardize the full text or meaning of
company proprietary rights when extracted for inclusion within a report or on CITIS display transactions.

Code Data Element Title DED Key

PRPCOD017 document-company-proprietary-data-rights-code 0084 K

PRPTXT017 document-company-proprietary-data-rights-text 0117 M

B.5.1.18. Table 018, Security access restrictions (ACCESS). This table contains the Government security
access restrictions and their meanings. It is used to standardize the full text or meaning of access restriction codes
when extracted for inclusion within a report or on CITIS display transactions.

Code Data Element Title DED Key

ACCCOD018 document-security-access-restriction-code 0085 K

ACCTXT018 document-security-access-restriction-text 0157 M

B.5.1.19. Table 019, Special security access restrictions (DOC-ACCESS). This table correlates special
Government security access restrictions with specific document revisions.

Code Data Element Title DED Key

ACCCOD018 document-security-access-restriction-code 0085 FK
DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B-21
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.1.20. Table 020, Documents identified by number (NUMDOC). This table is a subtype of Table
GENERIC-DOC/010, containing the identifiers of all documents which are primarily identified by a number, as
opposed to a title. For all entries in this table, the value of entity-type-code (ENTTYP000) in Table 000 must be
'E'. Due to parallel categorization, this table is a de facto child of Table ENTERPRISE/002.

a. Attribute document-identifier (DOCIDN010) inherited from Table 010 assumes the role document-
alphanumeric-identifier (DOCNUM020).

b. Because this table is a de facto child of Table 002, the value of document-source-entity-identifier
(SRCIDN010) inherited from Table 010 must exist as a enterprise-identifier (ENTIDN002) in Table 002.
SRCIDN010 assumes the role document-source-enterprise-identifier (SRCENT020).

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCENT020 document-source-enterprise-identifier 0052 FK

B.5.1.21. Table 021, Revisions to numbered documents (NUMDOCREV). This table is a subtype of Table
GENERIC-DOCREV/011, containing the subset of all revised documents which are primarily identified by a
number, as opposed to a document identified only by a title.

a. Due to parallel categorization, this table is a de facto child of Table NUMDOC/020.

b. Attribute document-identifier (DOCIDN010) inherited from Table 011 assumes the role document-
alphanumeric-identifier (DOCNUM020).

c. Because this table is a de facto child of Table 020, document-source-entity-identifier (SRCIDN010)

inherited from Table 011 is really a document-source-enterprise-identifier (SRCENT020) existing in
Table 020. Therefore, SRCIDN010 assumes the identity SRCENT020.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCENT020 document-source-enterprise-identifier 0052 FK

B.5.1.22. Table 022, Documents identified by CAGE code and number (CAGE-NUM-DOC). This table is a
subtype of Table NUMDOC/020 and consists of the subset of documents identified primarily by number (as
opposed to by title) and which are also identified by a CAGE code or NSCM code.

a. Subentities of this table are based on the document-type-code. They are not shown graphically, but can be
determined from Table B-I.

b. Due to parallel categorization, this table is a de facto child of Table CAGE/003.

B-22
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Because this table is a de facto child of Table 003, the value of document-source-enterprise-identifier
(SRCENT020) inherited from Table 020 must exist as a enterprise-defense-logistics--assigned-
identification-code (CAGNUM003) in Table 003. SRCENT020 assumes the role document-source-
enterprise-defense-logistics--assigned-identification-code (SRCCAG022).

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCCAG022 document-source-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B.5.1.23. Table 023, Revisions to documents identified by a CAGE code and number (CAGE-NUM-
DOCREV). This table is a subtype of Table NUMDOCREV/021 and consists of the subset of revised documents
which are identified primarily by number (as opposed to by title) and which are also identified by a CAGE code or
NSCM code.

a. Due to parallel categorization, this table is a de facto child of Table CAGE-NUM-DOC/022.

b. This table has subtypes based on document-type-code (DOCTYP010). Because it is a de facto child of
Table CAGE-NUM-DOC/022, it has the same subtypes as Table CAGE-NUM-DOC/022.

c. Because this table is a de facto child of Table 022, document-source-enterprise-identifier (SRCENT020)

inherited from Table 021 is really a document-source-enterprise-defense-logistics--assigned-identification-
code (SRCCAG022) existing in Table 022. Therefore, SRCENT020 assumes the identity SRCCAG022.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCCAG022 document-source-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B.5.1.24. Table 024, Documents identified by an issuing organization acronym and number (ORG-NUM-
DOC). This table is a subtype of Table NUMDOC/020, consisting of those documents which are identified by a
number and an issuing organization which is identified by an acronym (for example: ANSI Y14-24M, [DOD]
MIL-STD-973, etc.). Due to parallel categorization, this table is a de facto child of Table ORGANIZATION/004.

a. Because it is a de facto child of Table 004, it has the same six subtypes as Table 004; however, only two of
these are shown graphically in Figure 1GEN3.

b. Because this table is a de facto child of Table 004, the value of document-source-enterprise-identifier
(SRCENT020) inherited from Table 020 must exist as a organization-identifier (ORGIDN004) in Table
004. SRCENT020 assumes the role document-source-organization-identifier (SRCORG024).

B-23
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCORG024 document-source-organization-identifier 0096 FK

B.5.1.25. Table 025, Revisions to documents identified by an organization acronym and number (ORG-NUM-
DOCREV). This table is a subtype of Table NUMDOCREV/021, consisting of those revised documents that are
identified by an issuing organization acronym and a number.

a. Due to parallel categorization, this table is a de facto child of Table ORG-NUM-DOC/024.

b. This table has subtypes based on document-type-code (DOCTYP010). Because it is a de facto child of
Table ORG-NUM-DOC/024, it has the same subtypes as ORG-NUM-DOC/024.

c. Because this table is a de facto child of Table 024, document-source-enterprise-identifier (SRCENT020)

inherited from Table 021 is really a document-source-organization-identifier (SRCORG024) existing in
Table 024. Therefore, SRCENT020 assumes the identity SRCORG024.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCORG024 document-source-organization-identifier 0096 FK

B.5.1.26. Table 026, Documents identified by a company name and number (COMPANY-NUM-DOC). This
table is a subtype of Table NUMDOC/020, consisting of those numbered documents whose issuing organization is
identified by a company name. Subtypes of this table are based on document-type-code. They are not shown
graphically, but can be determined from Table B-I. Due to parallel categorization, this table is a de facto child of
Table COMPANY/005.

a. Because this table is a de facto child of Table 005, the value of document-source-enterprise-identifier
(SRCENT020) inherited from Table 020 must exist as a commercial-enterprise-name (COMNAM005) in
Table 005. SRCENT020 assumes the role commercial-document-source-enterprise-name (SRCCOM026).

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM026 commercial-document-source-enterprise-name 0170 FK

B.5.1.27. Table 027, Revisions to documents identified by a document number and company name
(COMPANY-NUM-DOCREV). This table is a subtype of Table NUMDOCREV/021, consisting of those revised
documents which are identified by an issuing company name and a number.

B-24
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Due to parallel categorization, this table is a de facto child of Table COMPANY-NUM-DOC/026.

b. This table has subtypes based on document-type-code (DOCTYP010). Because it is a de facto child of
Table COMPANY-NUM-DOC/026, it has the same subtypes as COMPANY-NUM-DOC/026.

c. Because this table is a de facto child of Table 026, document-source-enterprise-identifier (SRCENT020)

inherited from Table 021 is really a commercial-document-source-enterprise-name (SRCCOM026)
existing in Table 026. Therefore, SRCENT020 assumes the identity SRCCOM026.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM026 commercial-document-source-enterprise-name 0170 FK

B.5.1.28. Tables 28 through 32. Reserved.

B.5.1.29. Table 033, Application Activities (AA). This table identifies the activity(ies) which have adopted a
document for use.

a. The attributes enterprise-identifier (ENTIDN002) and enterprise-office-name (OFFSYM941) inherited

from Table 941 are concatenated and assume the role application-activity-enterprise-division-identifier
(APPACT033). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

APPACT033 application-activity-enterprise-division-identifier 0228 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

GLAACD033 application-activity-program-government-lead-indicator- 0128 M

code

B.5.1.30. Table 034, DOD organizations (DOD-ORGANIZATION). This table is a part of the DOD Enterprise
Data Model and is a subtype of Table ORGANIZATION/004. It contains the identifiers of DOD organizations. It
has five subtypes (not shown): DEFENSE-SECRETARY, DEFENSE-AGENCY, JOINT-MILITARY-STAFF,
MILITARY-SERVICE, and UNIFIED/SPECIFIED-COMMAND. For the purpose of CSA, we are interested in
those organizations which create, have change control authority over, or have custodial responsibility for
documents.

a. The united-states-defense-department-organization-type-identifier (DODTYP006) is inherited from Table

DOD-ORGANIZATION-TYPE (not shown in Figure 01GEN1) in the DOD Enterprise Data Model.

b. Attribute organization-identifier (ORGIDN004) inherited from Table 004 assumes the role united-states-
defense-department-enterprise-acronym-identification-code (DODORG034).

B-25
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DODORG034 united-states-defense-department-enterprise-acronym- 0002 FK
identification-code

DODTYP034 united-states-defense-department-organization-type-identifier 0097 FK

B.5.1.31. Table 035, Other US Government organization identification (OTHER-US-GOVT-

ORGANIZATION). This table is part of the DOD Enterprise Data Model and is a subtype of Table
ORGANIZATION / 004. It contains the identifying acronym of non-defense organizations of the U.S.
Government (for example: DOE, DOT, NASA, OSHA, etc.).

a. Attribute organization-identifier (ORGIDN004) inherited from Table 004 assumes the role united-states-
government-nondefense-enterprise-acronym-identification-code (GOVORG035).

Code Data Element Title DED Key

GOVORG035 united-states-government-nondefense-enterprise-acronym- 0002 FK
identification-code

B.5.1.32. Table 036, US non-Government organization identification (US-NON-GOVT-ORGANIZATION).

This table is part of the DOD Enterprise Data model and is a subtype of Table ORGANIZATION / 004. It contains
the identifying acronym for U.S. industry, professional, and other U.S. non-Government organizations, such as
IEEE, AIA, EIA, ANSI, etc.

a. Attribute organization-identifier (ORGIDN004) inherited from Table 004 assumes the role united-states-
nongovernment-enterprise-acronym-identification-code (INDORG036).

Code Data Element Title DED Key

INDORG036 united-states-nongovernment-enterprise-acronym- 0002 FK
identification-code

B.5.1.33. Table 037, Non-U.S. government organizations (FOREIGN-GOVT-ORGANIZATION). This table is

part of the DOD Enterprise Data Model and is a subtype of Table ORGANIZATION / 004. It contains the
identifying acronym of government organizations of countries other than the U.S. (for example: UK MOD, CSA,
etc.).

a. Attribute organization-identifier (ORGIDN004) inherited from Table 004 assumes the role non--united-
states-government-enterprise-acronym-identification-code (FGOVOR037).

Code Data Element Title DED Key

FGOVOR037 non--united-states-government-enterprise-acronym- 0002 FK
identification-code

B.5.1.34. Table 038, Non-U.S. nongovernment organizations (FOREIGN-NON-GOVT-ORGANIZATION).

This table is part of the DOD Enterprise Data model and is a subtype of Table ORGANIZATION / 004. It contains

B-26
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

the identifying acronym for non-U.S. industry, professional, and other national nongovernment organizations; it
does not include international organizations.

a. Attribute organization-identifier (ORGIDN004) inherited from Table 004 assumes the role non--united-
states-nongovernment-enterprise-acronym-identification-code (FNGVOR038).

Code Data Element Title DED Key

FNGVOR038 non--united-states-nongovernment-enterprise-acronym- 0002 FK
identification-code

B.5.1.35. Table 039, International organizations (INTERNATIONAL-ORGANIZATION). This table is part of

the DOD Enterprise Data Model and is a subtype of Table ORGANIZATION / 004. It contains the identifying
acronym of international organizations, such as ISO, AECMA, and NATO.

a. Attribute organization-identifier (ORGIDN004) inherited from Table 004 assumes the role international-
enterprise-acronym-identification-code (INTORG039).

Code Data Element Title DED Key

INTORG039 international-enterprise-acronym-identification-code 0002 FK

B.5.1.36. Table 040, Documents identified by title in lieu of number (TITLED). This table is a subtype of
Table GENERIC-DOC/010, containing the subset of all documents which are primarily identified by a title, as
opposed to a document identified by a number.

a. Attribute document-identifier (DOCIDN010) inherited from Table 010 assumes the role document-name
(DOCTIT040).

Code Data Element Title DED Key

DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.1.37. Table 041, Revisions to documents which are identified by a title (TITLED-DOCREV). This table is
a subtype of Table GENERIC-DOCREV/011, containing the subset of all revised documents which are identified
primarily by a title, as opposed to a number.

a. Due to parallel categorization, this table is a de facto child of Table TITLED/040.

b. Because this table is a de facto child of Table 040, document-identifier (DOCIDN010) inherited from
Table 011 is really a document-name (DOCTIT040) existing in Table 040. Therefore, DOCIDN010
assumes the identity DOCTIT040.

B-27
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.1.38. Table 042, Documents identified by author name and title (AUTH-TITL-DOC). This table is a
subtype of Table TITLED/040, containing the subset of documents identified primarily by title (as opposed to by
number) and which are also identified by an author's name. Due to parallel categorization, this table is a de facto
child of Table AUTHOR/001.

a. Subtypes of this table are based on document-type. They are not shown graphically, but are as follows:
'BOOK', 'PERIODL'.

b. Because this table is a de facto child of Table 001, document-source-entity-identifier (SRCIDN010)

inherited from Table 040 is really a author-human-name (AUTNAM001) existing in Table 001.
Therefore, SRCIDN010 assumes the identity AUTNAM001.

Code Data Element Title DED Key

AUTNAM001 author-human-name 0069 FK
DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK

B.5.1.39. Table 043, Revisions to documents which are identified by title and author (AUTH-TITL-DOCREV).
This table is a subtype of Table TITLED-DOCREV/041, containing the subset of all documents which have been
revised and which are identified primarily by title (as opposed to by number) and which are also identified by an
author's name.

a. Due to parallel categorization, this table is a de facto child of Table AUTH-TITL-DOC/042.

b. This table has subtypes based on document-type-code (DOCTYP010). Because it is a de facto child of
Table AUTH-TITL-DOC/042, it has the same subtypes as AUTH-TITL-DOC/042.

c. Because this table is a de facto child of Table 042, document-source-entity-identifier (SRCIDN010)

inherited from Table 041 is really a author-human-name (AUTNAM001) existing in Table 042.
Therefore, SRCIDN010 assumes the identity AUTNAM001.

Code Data Element Title DED Key

AUTNAM001 author-human-name 0069 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK

B-28
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.1.40. Table 044, Titled documents issued by an enterprise (ENT-TITL-DOC). This table is a subtype of
Table TITLED/040, containing the subset of documents which are identified by an enterprise identification and a
title. Due to parallel categorization, this table is a de facto child of Table ENTERPRISE/002. Thus, subtypes of
this table depend on the value of the enterprise-identification-type-code in Table ENTERPRISE/002. (Notice that
CAGE is not a valid subtype in this case.)

a. Because this table is a de facto child of Table 002, the value of document-source-entity-identifier
(SRCIDN010) inherited from Table 040 must exist as a enterprise-identifier (ENTIDN002) in Table 002.
SRCIDN010 assumes the role document-source-enterprise-identifier (SRCENT044).

Code Data Element Title DED Key

DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCENT044 document-source-enterprise-identifier 0052 FK

B.5.1.41. Table 045, Revisions to documents identified by issuing organization acronym and title (ENT-TITL-
DOCREV). This table is a subtype of Table TITLED-DOCREV/041, containing the subset of all documents which
have been revised and are identified primarily by a title (as opposed to by number) and by the acronym of the
issuing organization (such as NATO, DOD, DLA, NSA, AIA, ISO, etc.).

a. Due to parallel categorization, this table is a de facto child of Table ENT-TITL-DOC/044.

b. Because this table is a de facto child of Table 044 it has the same subtypes as Table 044.

c. Because this table is a de facto child of Table 044, document-source-entity-identifier (SRCIDN010)

inherited from Table 041 is really a document-source-enterprise-identifier (SRCENT044) existing in
Table 044. Therefore, SRCIDN010 assumes the identity SRCENT044.

Code Data Element Title DED Key

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCENT044 document-source-enterprise-identifier 0052 FK

B.5.1.42. Table 046, Documents identified by an organization acronym and title (ORG-TITL-DOC). This table
is a subtype of Table ENT-TITL-DOC/044, containing the subset of documents which are identified by a title and
the acronym of the issuing organization.

a. Due to parallel categorization, this table is a de facto child of Table ORGANIZATION/004.

b. Subtypes of this table are based on document-type-code (DOCTYP010). They are not shown graphically,
but can be determined from Table B-I.

c. Because this table is a de facto child of Table 004, the value of document-source-enterprise-identifier
(SRCENT044) inherited from Table 044 must exist as a organization-identifier (ORGIDN004) in Table
004. SRCENT044 assumes the role document-source-organization-identifier (SRCORG046).

B-29
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCORG046 document-source-organization-identifier 0096 FK

B.5.1.43. Table 047, Revisions to documents identified by issuing organization acronym and title (ORG-TITL-
DOCREV). This table is a subtype of Table ENT-TITL-DOCREV/045, containing the subset of all documents
which have been revised and are identified primarily by a title (as opposed to by number) and by the acronym of
the issuing organization (such as NATO, DOD, DLA, NSA, AIA, ISO, etc.).

a. Due to parallel categorization, this table is a de facto child of Table ORG-TITL-DOC/046.

b. Because this table is a de facto child of Table 046, it has the same subtypes as Table 046.

c. Because this table is a de facto child of Table 046, document-source-enterprise-identifier (SRCENT044)

inherited from Table 045 is really a document-source-organization-identifier (SRCORG046) existing in
Table 046. Therefore, SRCENT044 assumes the identity SRCORG046.

Code Data Element Title DED Key

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCORG046 document-source-organization-identifier 0096 FK

B.5.1.44. Table 048, Documents identified by company name and title (COMPANY-TITL-DOC). This table is
a subtype of Table ENT-TITL-DOC/044, containing the subset of documents which are identified primarily by
company name and title.

a. Due to parallel categorization, this table is a de facto child of Table COMPANY/005.

b. Subtypes of this table are based on document-type-code (DOCTYP010). They are not shown graphically,
but can be determined from Table B-I.

c. Because this table is a de facto child of Table 005, the value of document-source-enterprise-identifier
(SRCENT044) inherited from Table 044 must exist as a commercial-enterprise-name (COMNAM005) in
Table 005. SRCENT044 assumes the role commercial-document-source-enterprise-name (SRCCOM048).

Code Data Element Title DED Key

DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM048 commercial-document-source-enterprise-name 0170 FK

B-30
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.1.45. Table 049, Revisions to documents which are identified by a company name and document title
(COMPANY-TITL-DOCREV). This table is a subtype of Table ENT-TITL-DOCREV/045, containing the subset
of all documents which have been revised and are identified primarily by a title (as opposed to by number) and by
the name of the issuing company.

a. Due to parallel categorization, this table is a de facto child of Table COMPANY-TITL-DOC/048.

b. Because this table is a de facto child of Table 048, document-source-enterprise-identifier (SRCENT044)

inherited from Table 045 is really a commercial-document-source-enterprise-name (SRCCOM048)
existing in Table 048. Therefore, SRCENT044 assumes the identity SRCCOM048.

Code Data Element Title DED Key

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTIT040 document-name 0008 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM048 commercial-document-source-enterprise-name 0170 FK

B-31
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.2. Drawings and associated lists. Entity tables numbered in the range of 050 through 099 contain the
identification of engineering drawings and associated lists which comply with either military or ANSI standards.
This means that the contents of this section are limited to drawings and lists identified by a CAGE (or NSCM)
code and a drawing number. This series of tables includes all the drawing/list-unique attributes which are
necessary to the configuration management of the documents or the products1. This includes the relationship
between drawings and part definition, and the relationship between drawings and documents and parts referenced
in the notes of a drawing. The relationships between these various entity tables are depicted in Figures 02DWG1
through 02DWG5.

B.5.2.1. Table 050, Drawing Definition (DWG). This table contains the unique identifier of the engineering
drawing or associated list. An engineering drawing or associated list is one of four sub-types of Table CAGE-
NUMDOC/022 for the cases where the document-type-code has the value of 'DWG', 'PL', 'DL', or 'IL'. (Note: Use
of a CAGE code and number for identification of engineering drawings is the industry standard in the U.S. as
defined in ANSI Y14.1 since 1980. Despite this standard, it is recognized that some small business companies still
identify their drawings with a company name instead of a CAGE code; this practice is addressed in Table 912.)

a. In this usage, the document-source-enterprise-defense-logistics--assigned-identification-code is usually

called the Design CAGE Code.

b. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 022 assumes the role design-enterprise-defense-logistics--assigned-identification-
code (DESCAG050).

c. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 022 assumes the role
engineering-drawing-document-alphanumeric-identifier (DWGNUM050).

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

B.5.2.2. Table 051, Drawing Revision Definition (DWGREV). This table is the history of the various revisions to
an engineering drawing or associated list. It is one subtype of Table CAGE-NUM-DOCREV/023 for the same case
as the instances in Table CAGE-NUM-DOC/022, which is a de facto parent. This table also contains
characteristics about the drawing, such as total sheets and sheet size.

a. If the separate-parts-list-document-code (SEPCOD051) has a value of 'S' or 'I', then the administrative-
control-drawing-document-type-code (CONTYP051) must have a value of 'N'.

b. Because this table is a de facto child of Table 050, document-source-enterprise-defense-logistics--

assigned-identification-code (SRCCAG022) inherited from Table 023 is really a design-enterprise-
defense-logistics--assigned-identification-code (DESCAG050) existing in Table 050. Therefore,
SRCCAG022 assumes the identity DESCAG050.

1
exception: parts lists are in tables 200 to 249, see para B.5.5.

B-32
CAGE-NUM-DOC / 022 (from 1GEN3) CAGE-NUM-DOCREV / 023 (from 1GEN4)
document-source-cage-code document-source-cage-code
document-alphanumeric-identifier document-alphanumeric-identifier
document-type-code document-type-code
document-generic-revision

Assertion: relationship between

Assertion: relationship between
Table 022 and Table 050 is 1:1
may be a Table 022 and Table 050 is 1:1
if the value of doucment-type-code
if the value of doucment-type-code
is DL, DWG, IL, or PL, and is 1:0
is DL, DWG, IL, or PL, and is 1:0 may be a for all other cases
for all other cases
Z
Z
DWG / 050 (see 2DWG2)
DWGREV / 051 (de facto child of 050) (see 2DWG2, 2DWG3, 5PIN4, 6ECP2)
design-cage-code.document-source-cage-code (FK)
drawing-alphanumeric-identifier.document-alphanumeric-identifier (FK) design-cage-code.document-source-cage-code (FK)
document-type-code (FK) drawing-alphanumeric-identifier.document-alphanumeric-identifier (FK)
document-type-code (FK)
document-revision.document-generic-revision (FK)
separate-parts-list-code
control-drawing-type-code
document-type-code

DWGSHT / 052
PL
design-cage-code (FK)
Assertion: The only case when has sheets drawing-alphanumeric-identifier (FK)

B-33
a parts list drawing (PL / 062) P document-type-code (FK)
can exist without a corresponding drawing-revision.document-revision (FK)
graphical drawing (PICDWG / 060) is the sheet revision of document-sheet-identifier
APPENDIX B
MIL-STD-2549

is for a Kit Drawing. P drawing-sheet-revison.document-revision (FK)

DWG
PL / 062
IL PICDWG / 060 (see 4SW2, 13TRK1)
design-cage-code (FK)
drawing-alphanumeric-identifier (FK) may have design-cage-code (FK) CINOMEN / 690 (from 19CI1)
separate may be
PL.document-type-code (FK) drawing-alphanumeric-identifier (FK) ci-nomenclature
depicted by
document-type-code (FK)
DWG.document-type-code (FK) Z
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

ci-nomenclature (FK)

may define may define

IL / 065 Z
FIGURE 02DWG1
DRAWING DEFINITION (Part 1 of 3) design-cage-code (FK) DL / 069
drawing-alphanumeric-identifier (FK)
IL.document-type-code (FK) design-cage-code (FK)
Z drawing-alphanumeric-identifier (FK)
DWG.document-type-code (FK) DL.document-type-code (FK)
DWG.document-type-code (FK)
DWGREV / 051 (from 2DWG1)
design-cage-code
CAGEPIN / 212 (from 5PIN2) DWG / 050 (from 2DWG1) drawing-alphanumeric-identifier
design-cage-code design-cage-code document-type-code
part-identifier drawing-alphanumeric-identifier document-revision
document-type-code
document-type-code separate-parts-list-code
control-drawing-type-code

may define
document-type-code
Assertion: The relationship of Table 050 to 053 is 1:0-M
if the document-type-code is 'DWG', it is 1:P if the document-
type-code is 'PL', and it is 1:0 if the document-type-code is
DWG 'DL' or 'IL'.
may define
Assertion: The relationship of Table 051 to 054 is 1:0-M if the document-type-code document-type-code
DWGPIN / 053 (see 4SW2, 5PIN5, 14TM5) is 'DWG', it is 1:P if the document-type-code is 'PL', and it is 1:0 if the document-type-
design-cage-code (FK) code is 'DL' or 'IL'.
part-identifier (FK) DWG PL

drawing-alphanumeric-identifier (FK)
document-type-code (FK) PLREV / 063 (de facto child of 062) (see 2DWG3,2DWG4,2DWG5,7NOR3)
PICDWGREV / 061 (de facto child of 060) (see 2DWG4,2DWG5,7NOR3)
design-cage-code (FK)
design-cage-code (FK) drawing-alphanumeric-identifier (FK)
is defined on drawing-alphanumeric-identifier (FK) document-type-code (FK)
document-type-code (FK) document-revision (FK)
document-revision (FK)

GENERIC-MATID / 200 (from 5PIN1)

design-enterprise-identifier may be graphically
material-generic-identifier described by
material-identification
may have parts listed on Note: The only time the relation

B-34
Assertion: The relation of Table 061 between Tables 063 and 064 is 1:0
to 064 is 1:0 if the separate-parts- (meaning that a parts list drawing
list-code is 'N' or 'I', and is 1:P if the exists without a graphic drawing)
APPENDIX B
MIL-STD-2549

separate-parts-list-code in Table 051 is when the parts list drawing is a

P
is 'S'. Kit drawing or an Identification Cross
DWGREV-PIN / 054 (see 5PIN4) Reference drawing.
design-cage-code (FK) GENERIC-PIN / 210 (from 5PIN2)
part-identifier (FK) design-enterprise-identifier
document-revision (FK) part-identifier
DWGREV-PLREV / 064
drawing-alphanumeric-identifier (FK) design-cage-code (FK)
document-type-code (FK) drawing-alphanumeric-identifier (FK)
may be controlled by PL.document-type-code (FK)
may be DWG.document-type-code (FK)
equivalent to may be equivalent to parts-list-drawing-revision.document-revision (FK)
Assertion: If the control-drawing-type-code is graphic-drawing-revision.document-revision (FK)
may be
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

'P', 'S', 'V', or 'X', the relationships 054 to 055

controlled by and 054 to 056 cannot both be 1:0

ADMIN-MAT / 055 ADMIN-PIN / 056

design-cage-code (FK) design-cage-code (FK)
part-administrative-identifier.part-identifier (FK) part-administrative-identifier.part-identifier (FK)
document-revision (FK) document-revision (FK)
design-enterprise-identifier (FK) design-enterprise-identifier (FK)
FIGURE 02DWG2 vendor--assigned-material-identifier.(material-generic-identifier,material-identification) (FK) vendor--assigned-part-identifier.part-identifier (FK)
DRAWING DEFINITION (Part 2 of 3)
DWGREV / 051 (from 2DWG1)
design-cage-code
drawing-alphanumeric-identifier
document-type-code
document-revision
separate-parts-list-code
GENERIC-DOCREV / 011 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-generic-revision document-type-code

DL IL

DLREV / 070 (de facto child of 069) ILREV / 066 (de facto child of 065)
design-cage-code (FK) design-cage-code (FK) may include
drawing-alphanumeric-identifier (FK) drawing-alphanumeric-identifier (FK)
DL.document-type-code (FK) IL.document-type-code (FK) may be included in
document-revision (FK) document-revision (FK)

may be
included in
ILREV-IL / 067
PLREV / 063 (from 2DWG2) controlling-index-list-cage-code.design-cage-code (FK)
controlling-index-list-drawing-alphanumeric-identifier.drawing-alphanumeric-identifier (FK)
may include design-cage-code IL (FK)

B-35
drawing-alphanumeric-identifier controlling-index-list-revision.document-revision (FK)
document-type-code component-index-list-cage-code.design-cage-code (FK)
document-revision component-index-list-drawing-alphanumeric-identifier.drawing-alphanumeric-identifier (FK)
APPENDIX B
MIL-STD-2549

component-index-list-revision.document-revision (FK)

may include

DLREV-DOC / 071
may be included in
design-cage-code (FK)
drawing-alphanumeric-identifier (FK)
DL (FK)
ILREV-PL / 068
data-list-revision.document-revision (FK)
document-source-entity-identifier (FK) index-list-cage-code.design-cage-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-identifier (FK) index-list-drawing-alphanumeric-identifier.drawing-alphanumeric-identifier (FK)

component-document-type-code.document-type-code (FK) IL (FK)
index-list-revision.document-revision (FK)
document-generic-revision (FK) parts-list-cage-code.design-cage-code (FK)
parts-list-drawing-alphanumeric-identifier.drawing-alphanumeric-identifier (FK)
PL.document-type-code (FK)
parts-list-revision.document-revision (FK)
FIGURE 02DWG3
DRAWING DEFINITION (Part 3 of 3)
PICDWGREV / 061 (from 2DWG2)
design-cage-code GENERIC-DOCUMENT / 010 (from 1GEN2)
drawing-alphanumeric-identifier document-source-entity-identifier
document-type-code document-identifier
document-revision document-type-code

may reference in notes

may be referenced
PLREV / 063 (from 2DWG2) in notes on
design-cage-code
drawing-alphanumeric-identifier
document-type-code GENERIC-DOCREV / 011 (from 1GEN2)
may have document-revision document-source-entity-identifier
Assertion: the relationship of
document-identifier
Table 061 to 082 and of Table
document-type-code
063 to 082 are mutually exclusive.
document-generic-revision
may have may reference in notes
Assertion: the relationship of
Table 061 to 080 and of Table
may be referenced in notes of
063 to 080 are mutually exclusive.
DWGNOTE / 080 (see 2DWG5, 5PIN4)
design-cage-code (FK) DWG-REFDOC / 082

B-36
drawing-alphanumeric-identifier (FK)
design-cage-code (FK)
document-type-code (FK)
drawing-alphanumeric-identifier (FK)
APPENDIX B

document-revision (FK)
MIL-STD-2549

controlling-drawing-document-type-code.document-type-code (FK)
drawing-note-number
controlling-drawing-revision.document-revision (FK)
document-source-entity-identifier (FK)
document-identifier (FK)
referenced-document-type-code.document-type-code (FK)
may have
may reference
referenced-document-generic-revision.document-generic-revision (FK)

SPECIAL-NOTE / 081
design-cage-code (FK) may be referenced in
drawing-alphanumeric-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-type-code (FK)
document-revision (FK)
drawing-note-number (FK) DWGNOTE-DOC / 085
drawing-special-condition-code design-cage-code (FK)
drawing-alphanumeric-identifier (FK)
controlling-drawing-document-type-code.(controlling-drawing-document-type-code,document-type-code) (FK)
controlling-drawing-revision.(document-revision,controlling-drawing-revision) (FK)
drawing-note-number (FK)
FIGURE 02DWG4 document-source-entity-identifier (FK)
DOCUMENTS NOTED ON DRAWINGS document-identifier (FK)
referenced-document-type-code (FK)
GENERIC-MATID / 200 (from 5PIN1) PICDWGREV / 061 (from 2DWG2)
design-enterprise-identifier GENERIC-PIN / 210 (from 5PIN2)
design-cage-code
material-generic-identifier drawing-alphanumeric-identifier design-enterprise-identifier
material-identification document-type-code part-identifier
document-revision

may be referenced may be referenced

in notes of in notes of

may reference in notes may reference in notes

PLREV / 063 (from 2DWG2)

design-cage-code
drawing-alphanumeric-identifier
document-type-code
document-revision

may reference in notes may reference in notes

Assertion: the relationship of Assertion: the relationship of
Table 061 to 083 and of Table Table 061 to 084 and of Table
063 to 083 are mutually exclusive. 063 to 084 are mutually exclusive.

B-37
DWG-REFMAT / 083
DWG-REFPIN / 084
design-cage-code (FK) DWGNOTE / 080 (from 2DWG4)
APPENDIX B

design-cage-code (FK)
MIL-STD-2549

drawing-alphanumeric-identifier (FK)
design-cage-code drawing-alphanumeric-identifier (FK)
document-type-code (FK)
drawing-alphanumeric-identifier document-type-code (FK)
document-revision (FK)
document-type-code document-revision (FK)
design-enterprise-identifier (FK)
document-revision design-enterprise-identifier (FK)
material-generic-identifier (FK)
drawing-note-number part-identifier (FK)
material-identification (FK)

may be referenced in may reference may reference may be referenced in

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

DWGNOTE-MAT / 086
design-cage-code (FK) DWGNOTE-PIN / 087
drawing-alphanumeric-identifier (FK) design-cage-code (FK)
document-type-code (FK) drawing-alphanumeric-identifier (FK)
document-revision (FK) document-type-code (FK)
drawing-note-number (FK) document-revision (FK)
design-enterprise-identifier (FK) drawing-note-number (FK)
FIGURE 02DWG5 material-generic-identifier (FK) design-enterprise-identifier (FK)
PARTS/MATERIALS NOTED ON DRAWINGS material-identification (FK) part-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 023 assumes the role
document-alphanumeric-revision-identifier (DOCREV051).

d. Because this table is a de facto child of Table 050, document-alphanumeric-identifier (DOCNUM020)

inherited from Table 023 is really a engineering-drawing-document-alphanumeric-identifier
(DWGNUM050) existing in Table 050. Therefore, DOCNUM020 assumes the identity DWGNUM050.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

CONTYP051 administrative-control-drawing-document-type-code 0032 M

DWGSHT051 document-sheet-total-quantity 0110
DWGSIZ051 document-sheet-size-code 0112
FRSTRT051 materiel-item-first-article-test-code 0077
SEPCOD051 separate-parts-list-document-code 0025

B.5.2.3. Table 052, Drawing Sheet Revision Correlation (DWGSHT). This table contains the 'status of sheets' for
an engineering drawing or associated list.

a. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 051 assumes

the role engineering-drawing-document-current-alphanumeric-revision-identifier (CURREV052).

b. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 051 assumes

the role engineering-drawing-document-sheet-alphanumeric-revision-identifier (SHTREV052).

Code Data Element Title DED Key

SHTNUM052 document-sheet-identifier 0026 K
CURREV052 engineering-drawing-document-current-alphanumeric- 0009 FK
revision-identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

SHTREV052 engineering-drawing-document-sheet-alphanumeric-revision- 0009 FK

identifier
SHTDAT052 document-revised-sheet-change-incorporation-date 0082

B.5.2.4. Table 053, Part numbers of parts defined by an engineering drawing and CAGE code (DWGPIN). This
table is a subset of Table CAGEPIN/212 consisting of those part numbers which are identified by an engineering
drawing which is identified by a CAGE (or NSCM) code and number. (Note: The value of document-
alphanumeric-identifier [DOCNUM020] is frequently embedded in the first 'n' characters of part identifier.)

B-38
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. The value of document-type-code (DOCTYP010) must be 'DWG' or 'PL'.

b. The value of DOCTYP010 must be the same as the value of document-type-code (DOCTYP212) for the
super-type in Table 212.

c. Fields DESCAG050 inherited from Table 050 and DESCAG212 inherited from Table 212 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG053).

Code Data Element Title DED Key

DESCAG053 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
PARNUM210 part-product-identifier 0024 FK

DOCTYP010 document-type-code 0004 FK

DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

B.5.2.5. Table 054, Correlation of part numbers to drawing revisions on which they are defined (DWGREV-PIN).
This table correlates part numbers which are defined by engineering drawings with the specific revision(s) of the
engineering drawing on which the parts are defined.

a. For each instance in this table, the combination of the values of the engineering-drawing-document-
alphanumeric-identifier (DWGNUM050) and document-type-code (DOCTYP010) must be the same as
the combination of the values of the same fields in the parent instance in Table 053.

b. Fields DESCAG050 inherited from Table 051 and DESCAG053 inherited from Table 053 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG054).

Code Data Element Title DED Key

DESCAG054 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
PARNUM210 part-product-identifier 0024 FK

DOCTYP010 document-type-code 0004 FK

DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
PARSTA054 part-product-status-code 0035 M

B.5.2.6. Table 055, Correlation of control-drawing part numbers to vendor materials (ADMIN-MAT). This table
correlates the part numbers defined on a source control drawing, vendor item drawing, procurement control
drawing, or an identification cross-reference drawing with the equivalent vendor material identifiers.

a. Attribute part-product-identifier (PARNUM210) inherited from Table 054 assumes the role part-product-
administrative-control-identifier (CONPIN055).

B-39
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. The attributes material-product-generic-identifier (MATGID200) and material-product-identifier

(MATIDN200) inherited from Table 200 are concatenated and assume the role material-product-vendor--
assigned-identifier (VMATID055). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

CONPIN055 part-product-administrative-control-identifier 0024 FK
DESCAG054 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT200 design-enterprise-identifier 0052 FK
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
VMATID055 material-product-vendor--assigned-identifier 0048 FK

B.5.2.7. Table 056, Correlation of source controlled part numbers to vendor part numbers (ADMIN-PIN). This
table correlates the part numbers defined on a source control drawing, vendor item drawing, procurement control
drawing, or an identification cross-reference drawing with the equivalent vendor part number(s).

a. The combination of the values of design-enterprise-identifier (DESENT210) and part-product-vendor-

assigned-identifier (VPARNO056) cannot be the same as the combination of the values of design-
enterprise-defense-logistics--assigned identification-code (DESCAG054) and part-product-administrative-
control-identifier (CONPIN056) for the same instance.

b. Attribute part-product-identifier (PARNUM210) inherited from Table 054 assumes the role part-product-
administrative-control-identifier (CONPIN056).

c. Attribute part-product-identifier (PARNUM210) inherited from Table 210 assumes the role part-product-
vendor--assigned-identifier (VPARNO056).

Code Data Element Title DED Key

CONPIN056 part-product-administrative-control-identifier 0024 FK
DESCAG054 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT210 design-enterprise-identifier 0052 FK
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
VPARNO056 part-product-vendor--assigned-identifier 0024 FK

B.5.2.8. Tables 57 through 59. Reserved.

B.5.2.9. Table 060, Graphical drawings, with or without an integral parts list (PICDWG). This table is a subtype
of Table DWG/050 which contains graphical engineering drawings only. Associated lists are specifically
excluded.

a. The value of document-type-code (DOCTYP010) must be 'DWG'.

b. If the value of configuration-item-product-nomenclature-text (CINOMN690) is non-blank, then the value

of configuration-item-product-indicator-code (CIFLAG057) must be 'Y'.

B-40
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

CINOMN690 configuration-item-product-nomenclature-text 0047 FK, O

CIFLAG060 configuration-item-product-indicator-code 0023 M

B.5.2.10. Table 061, Graphical drawing revision, with or without integral parts list (PICDWGREV). This table
is a subtype of Table DWGREV/051 for the case of document-type-code (DOCTYP010) in Table 051 with a value
of 'DWG'. It is a subset of all drawings and associated lists which have revisions. It contains the revision history
of engineering drawings. This table is a de facto child of Table 060.

Code Data Element Title DED Key

B.5.2.11. Table 062, Parts list drawing (PL). This table is a subtype of Table DWG/050 which contains the
subset of all drawings and associated lists which are separate Parts List drawings only.

a. Attribute document-type-code (DOCTYP010) inherited from Table 060 assumes the role engineering-
drawing-document-type-code (DWGTYP062).

b. Attribute document-type-code (DOCTYP010) inherited from Table 050 assumes the role parts-list-
drawing-document-type-code (PLTYPE062).

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
PLTYPE062 parts-list-drawing-document-type-code 0004 FK

DWGTYP062 engineering-drawing-document-type-code 0004 FK

B.5.2.12. Table 063, Parts list drawing revisions (PLREV). This table is a subtype of Table DWGREV/051 for
the case of document-type-code (DOCTYP010) in Table 051 with a value of 'PL'. It contains the revision history of
separate parts list drawings. This table is a de facto child of Table 062.

a. Because this table is a de facto child of Table 062, document-type-code (DOCTYP010) inherited from
Table 051 is really a parts-list-drawing-document-type-code (PLTYPE062) existing in Table 062.

B-41
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

B.5.2.13. Table 064, Correlation of graphical drawing revisions to separate parts list drawing revisions
(DWGREV-PLREV). This table correlates revisions to engineering drawings without an integral parts list to their
associated parts list drawing revision(s).

a. Attribute document-type-code (DOCTYP010) inherited from Table 061 assumes the role engineering-
drawing-document-type-code (DWGTYP064).

b. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 061 assumes

the role graphic-engineering-drawing-document-alphanumeric-revision-identifier (GDWGRV064).

c. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 063 assumes

the role parts-list-drawing-document-alphanumeric-revision-identifier (PLREVN064).

d. Attribute document-type-code (DOCTYP010) inherited from Table 063 assumes the role parts-list-
drawing-document-type-code (PLTYPE064).

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
DWGTYP064 engineering-drawing-document-type-code 0004 FK
GDWGRV064 graphic-engineering-drawing-document-alphanumeric- 0009 FK
revision-identifier
PLREVN064 parts-list-drawing-document-alphanumeric-revision-identifier 0009 FK
PLTYPE064 parts-list-drawing-document-type-code 0004 FK

B.5.2.14. Table 065, Index list drawings (IL). This table is a subtype of DWG/050 which contains the subset of
all drawings and associated lists which are Index List drawings.

a. Attribute document-type-code (DOCTYP010) inherited from Table 060 assumes the role engineering-
drawing-document-type-code (DWGTYP065).

b. Attribute document-type-code (DOCTYP010) inherited from Table 050 assumes the role index-list-
drawing-document-type-code (ILTYPE065).

B-42
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
ILTYPE065 index-list-drawing-document-type-code 0004 FK

DWGTYP065 engineering-drawing-document-type-code 0004 FK

B.5.2.15. Table 066, Index list drawing revision (ILREV). This table is a subtype of Table DWGREV/051 for
the case of document-type-code (DOCTYP010) with a value of 'IL'. It contains the revision history of index list
drawings.

a. This table is a de facto child of Table 065.

b. Because this table is a de facto child of Table 065, document-type-code (DOCTYP010) inherited from
Table 051 is really a index-list-drawing-document-type-code (ILTYPE065) existing in Table 065.
Therefore, DOCTYP010 assumes the identity ILTYPE065.

Code Data Element Title DED Key

B.5.2.16. Table 067, Correlation of index list drawing revisions to their component index list drawings
(ILREV-IL). This table correlates index list drawings to the specific index list revision on which they appear as a
component. The value of the combination of component-index-list-drawing-document-source-enterprise-defense-
logistics--assigned-identification-code (CILCAG067) and component-index-list-drawing-document-alphanumeric-
identifier (CILNUM067) cannot be the same as the value of the combination of controlling-index-list-drawing-
document-source-enterprise-defense-logistics--assigned-identification-code (ILCAGE067) and controlling-index-
list-drawing-document-alphanumeric-identifier (ILNUMB067) for the same instance.

a. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG050) inherited from

Table 066 assumes the role component-index-list-drawing-document-source-enterprise-defense-logistics--
assigned-identification-code (CILCAG067).

b. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

066 assumes the role component-index-list-drawing-document-alphanumeric-identifier (CILNUM067).

c. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 066 assumes

the role component-index-list-drawing-document-alphanumeric-revision-identifier (CILREV067).

d. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG050) inherited from

Table 066 assumes the role controlling-index-list-drawing-document-source-enterprise-defense-logistics--
assigned-identification-code (ILCAGE067).

B-43
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

e. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

066 assumes the role controlling-index-list-drawing-document-alphanumeric-identifier (ILNUMB067).

f. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 066 assumes

the role controlling-index-list-drawing-document-alphanumeric-revision-identifier (ILREVN067).

Code Data Element Title DED Key

CILCAG067 component-index-list-drawing-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
CILNUM067 component-index-list-drawing-document-alphanumeric- 0003 FK
identifier
ILCAGE067 controlling-index-list-drawing-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ILNUMB067 controlling-index-list-drawing-document-alphanumeric- 0003 FK
identifier
ILREVN067 controlling-index-list-drawing-document-alphanumeric- 0009 FK
revision-identifier
ILTYPE065 index-list-drawing-document-type-code 0004 FK

CILREV067 component-index-list-drawing-document-alphanumeric- 0009 FK

revision-identifier

B.5.2.17. Table 068, Correlation of index list drawing revisions to their component parts list drawings (ILREV-
PL). This table correlates separate parts list drawings to the specific index list revision on which they appear as a
component.

a. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG050) inherited from

Table 066 assumes the role index-list-drawing-document-design-enterprise-defense-logistics--assigned-
identification-code (ILCAGE068).

b. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

066 assumes the role index-list-drawing-document-alphanumeric-identifier (ILNUMB068).

c. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 066 assumes

the role index-list-drawing-document-alphanumeric-revision-identifier (ILREVN068).

d. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG050) inherited from

Table 063 assumes the role parts-list-drawing-document-source-enterprise-defense-logistics--assigned-
identification-code (PLCAGE068).

e. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

063 assumes the role parts-list-drawing-document-alphanumeric-identifier (PLNUMB068).

f. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 063 assumes

the role parts-list-drawing-document-alphanumeric-revision-identifier (PLREVN068).

g. Attribute document-type-code (DOCTYP010) inherited from Table 063 assumes the role parts-list-
drawing-document-type-code (PLTYPE068).

B-44
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

ILCAGE068 index-list-drawing-document-design-enterprise-defense- 0001 FK
logistics--assigned-identification-code
ILNUMB068 index-list-drawing-document-alphanumeric-identifier 0003 FK
ILREVN068 index-list-drawing-document-alphanumeric-revision- 0009 FK
identifier
ILTYPE065 index-list-drawing-document-type-code 0004 FK
PLCAGE068 parts-list-drawing-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
PLNUMB068 parts-list-drawing-document-alphanumeric-identifier 0003 FK
PLTYPE068 parts-list-drawing-document-type-code 0004 FK

PLREVN068 parts-list-drawing-document-alphanumeric-revision-identifier 0009 FK

B.5.2.18. Table 069, Data list drawings (DL). This table is a subtype of DWG/050 which contains the subset of
all drawings and associated lists which are Data List drawings.

a. Attribute document-type-code (DOCTYP010) inherited from Table 050 assumes the role data-list-
drawing-document-type-code (DLTYPE069).

b. Attribute document-type-code (DOCTYP010) inherited from Table 060 assumes the role engineering-
drawing-document-type-code (DWGTYP069).

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DLTYPE069 data-list-drawing-document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

DWGTYP069 engineering-drawing-document-type-code 0004 FK

B.5.2.19. Table 070, Data list drawing revisions (DLREV). This table is a subtype of Table DWGREV/051 for
the case of document-type-code (DOCTYP010) with a value of 'DL'. It contains the revision history of data list
drawings.

a. This table is a de facto child of Table 069.

b. Because this table is a de facto child of Table 069, document-type-code (DOCTYP010) inherited from
Table 051 is really a data-list-drawing-document-type-code (DLTYPE069) existing in Table 069.
Therefore, DOCTYP010 assumes the identity DLTYPE069.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DLTYPE069 data-list-drawing-document-type-code 0004 FK
DOCREV051 document-alphanumeric-revision-identifier 0009 FK

B-45
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

B.5.2.20. Table 071, Correlation of data list drawing revisions to their component documents (DLREV-DOC).
This table correlates documents (other than those engineering drawings identified by CAGE code an drawing
identifier) to the specific data list revision on which they appear as a component.

a. The value of component-document-type-code (CDOCTY071) may be any value; however, if it is 'DL',

then the combination of the design-enterprise-defense-logistics--assigned-identification-code
(DESCAG050) and engineering-drawing-document-alphanumeric-identifier (DWGNUM050) cannot be
the same as the combination of the document-source-entity-identifier (SRCIDN010) and document-
identifier (DOCIDN010).

b. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 011 assumes the role
component-document-generic-revision-identifier (CDOCRV071).

c. Attribute document-type-code (DOCTYP010) inherited from Table 011 assumes the role component-
document-type-code (CDOCTY071).

d. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 070 assumes

the role data-list-drawing-document-alphanumeric-revision-identifier (DLREVN071).

Code Data Element Title DED Key

CDOCTY071 component-document-type-code 0004 FK
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DLREVN071 data-list-drawing-document-alphanumeric-revision-identifier 0009 FK
DLTYPE069 data-list-drawing-document-type-code 0004 FK
DOCIDN010 document-identifier 0122 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
SRCIDN010 document-source-entity-identifier 0033 FK

CDOCRV071 component-document-generic-revision-identifier 0243 FK

B.5.2.21. Tables 72 through 79. Reserved.

B.5.2.22. Table 080, Drawing note identification (DWGNOTE). This table identifies the notes on an
engineering drawing. Its primary purpose is to capture documents which are called out in the notes and, therefore,
must be included in Data Lists. It also meets an engineering need to be able to encapsulate and transfer drawing
text in a simple fashion. If desired, it can contain the actual text of the note.

Code Data Element Title DED Key

NOTNUM080 engineering-drawing-document-note-identifier 0251 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK

B-46
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DOCTYP010 document-type-code 0004 FK

DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

NOTTXT080 engineering-drawing-document-note-text 0252

B.5.2.23. Table 081, Special Conditions, Materials and Processes in the notes (SPECIAL-NOTE). This table
identifies the special conditions, materials and processes which are associated with a particular note on a particular
engineering drawing.

Code Data Element Title DED Key

SPNOTE081 engineering-drawing-document-special-condition-code 0257 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
NOTNUM080 engineering-drawing-document-note-identifier 0251 FK

B.5.2.24. Table 082, Documents referenced on a drawing other than in the parts list (DWG-REFDOC). This
table identifies documents which are referenced for information in the notes or elsewhere on the face of a drawing,
other than in the parts list. This information is necessary for the preparation of Data List Drawings and Technical
Data Packages.

a. The fields DESCAG050, DWGNUM050, CDWGTY082, and CDWGRV082 are inherited from either
Table 061 or Table 063 and identify the drawing or parts list drawing which contains the reference. The
fields SRCIDN010, DOCIDN010, RDOCTY082, and the optional field RDOCRV082 identify the
referenced document. The value of the combination of design-enterprise-defense-logistics--assigned-
identification-code (DESCAG050), engineering-drawing-document-alphanumeric-identifier
(DWGNUM050), and controlling-engineering-drawing-document-type-code (CDWGTY082) cannot be
the same as the value of the combination of document-source-entity-identifier (SRCIDN010), document-
identifier (DOCIDN010), and referenced-document-type-code (RDOCTY082) for the same instance.

b. Attribute document-alphanumeric-revision-identifier (DOCREV051) is inherited either from Table 061 or

Table 063. In either case, it assumes the role controlling-engineering-drawing-document-alphanumeric-
revision-identifier (CDWGRV082).

c. Attribute document-type-code (DOCTYP010) is inherited either from Table 061 or Table 063. In either
case, it assumes the role controlling-engineering-drawing-document-type-code (CDWGTY082).

d. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 011 assumes the role
referenced-document-generic-revision-identifier (RDOCRV082).

e. Attribute document-type-code (DOCTYP010) inherited from Table 010 and document-type-code

(DOCTYP010) inherited from Table 011 must have the same value and merge to assume the role
referenced-document-type-code (RDOCTY082).

B-47
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

CDWGRV082 controlling-engineering-drawing-document-alphanumeric- 0009 FK
revision-identifier
CDWGTY082 controlling-engineering-drawing-document-type-code 0004 FK
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCIDN010 document-identifier 0122 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
RDOCTY082 referenced-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

RDOCRV082 referenced-document-generic-revision-identifier 0243 FK, O

B.5.2.25. Table 083, Materials referenced on a drawing other than in the parts list (DWG-REFMAT). The
table identifies materials (not identified by part numbers) which are referenced in the notes of the drawing or
elsewhere on the face of the drawing, excluding the parts list. This information is necessary for preparation of
Data List Drawings.

a. The fields DESCAG050, DWGNUM050, DOCTYP010, and DOCREV011 are inherited from either
Table 061 or Table 063 and identify the drawing or parts list drawing which contains the reference. The
fields DESENT200, MATGID200, and MATIDN200 identify the material.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT200 design-enterprise-identifier 0052 FK
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK

B.5.2.26. Table 084, Part numbers referenced on drawing other than in the parts list (DWG-REFPIN). The
table identifies part numbers which are referenced in the notes of the drawing or elsewhere on the face of the
drawing, excluding the parts list. This information is necessary for preparation of Data List Drawings.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT210 design-enterprise-identifier 0052 FK

B-48
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DOCREV051 document-alphanumeric-revision-identifier 0009 FK

DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
PARNUM210 part-product-identifier 0024 FK

B.5.2.27. Table 085, Miscellaneous documents identified in notes of an engineering drawing (DWGNOTE-
DOC). This table identifies documents which are referenced for information in the notes of a drawing and
correlates them to the note number(s). This information is necessary for support of certain ISO STEP Application
Protocol(s).

a. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 080 assumes

the role controlling-engineering-drawing-document-alphanumeric-revision-identifier (CDWGRV082).

b. Attribute document-type-code (DOCTYP010) inherited from Table 080 assumes the role controlling-
engineering-drawing-document-type-code (CDWGTY082).

Code Data Element Title DED Key

CDWGRV082 controlling-engineering-drawing-document-alphanumeric- 0009 FK
revision-identifier
CDWGTY082 controlling-engineering-drawing-document-type-code 0004 FK
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCIDN010 document-identifier 0122 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
NOTNUM080 engineering-drawing-document-note-identifier 0251 FK
RDOCTY082 referenced-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.2.28. Table 086, Material referenced in notes of an engineering drawing (DWGNOTE-MAT). This table
identifies materials and parts (not identified by part numbers) which are referenced for information in the notes of
a drawing and correlates it to the note number. This information is necessary for support of certain ISO STEP
application protocols.

Code Data Element Title DED Key

B-49
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.2.29. Table 087, Part numbers referenced in drawing notes (DWGNOTE-PIN). This table identifies part
numbers which are referenced for information in the notes of a drawing and correlates it to the drawing note
number. This information is necessary to support certain ISO STEP application protocols.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT210 design-enterprise-identifier 0052 FK
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
NOTNUM080 engineering-drawing-document-note-identifier 0251 FK
PARNUM210 part-product-identifier 0024 FK

B.5.2.30. Tables 88 through 99. Reserved.

B-50
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.3. Program-unique specifications. Entity tables numbered in the range of 100 through 149 contain the
identification of program-unique specifications which comply with either old2 or current military standards3. This
means that the contents of this section are limited to program-unique specifications identified by a CAGE (or
NSCM) code and a document number.4 This series of tables includes all the specification attributes which are
necessary to the configuration management of the documents or the products. This includes the relationship
between specifications and the parts or materials which they define and the relationship between program-unique
specifications and documents and parts referenced in the applicable documents section of a program-unique
specification. The relationships between these various entity tables are depicted in Figures 03SPEC1 through
03SPEC3.

B.5.3.1. Table 100, Program-unique specification definition (PSPEC). This table contains the unique identifier of
the program-unique specification. A program-unique specification is one sub-type of Table CAGE-NUMDOC/020
for the case where the value of document-type-code is 'P-SPEC'. (Note: Some small business companies still
identify their specifications with a company name instead of a CAGE code; this practice is addressed in Table
910.)

a. The value of functional-baseline-top--level-document-indicator-code (FBLFLG100) must be 'N' unless the

value of program--unique-specification-document-subsidiary-type-code (SUBTYP100) is 'SYS'.

b. The value of allocated-baseline-top--level-document-indicator-code (ABLFLG100) must be 'N' unless the

value of program--unique-specification-document-subsidiary-type-code (SUBTYP100) is either 'B1', 'B2',
'B3', 'B4', 'IS', 'SRS', or 'SS'.

c. The values for allocated-baseline-top--level-document-indicator-code (ABLFLG100) and functional-

baseline-top--level-document-indicator-code (FBLFLB100) cannot both be 'Y' for any one instance. The
decision of whether this specification is the top-level FBL or ABL document is from the viewpoint of the
design-enterprise-defense-logistics--assigned-identification-code (DESCAG100).

d. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 022 assumes the role design-enterprise-defense-logistics--assigned-identification-
code (DESCAG100).

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK

CINOMN690 configuration-item-product-nomenclature-text 0047 FK, O

ABLFLG100 allocated-baseline-top--level-document-indicator-code 0137 M
FBLFLG100 functional-baseline-top--level-document-indicator-code 0138 M
FSCCOD100 product-federal-supply-classification-code 0073
PRDTYP100 product-type-code 0034 M
SUBTYP100 program--unique-specification-document-subsidiary-type- 0108 M
code

2
Exception: Specification change notices are supported only in a very limited fashion by this model.
3
There are no industry standards for the preparation or content of program-unique specifications.
4
For program-unique specifications which are commercially prepared and identified by a company name instead of a
CAGE code (or NSCM), see Tables 910 through 924. For standardization documents such as military, industry,
international, foreign, etc., specifications, standards, handbooks, bulletins, etc., see Tables 400 through 450.

B-51
CAGE-NUM-DOC / 022 (from 1GEN3)
document-source-cage-code
document-alphanumeric-identifier
CINOMEN / 690 (from 19CI1)
document-type-code
ci-nomenclature

document-type-code
CAGEPIN / 212 (from 5PIN2) may be depicted by
design-cage-code
part-identifier PSPEC / 100 (see 3SPEC2, 13TRK1) CAGE-MATID / 205 (from 5PIN1)
document-type-code design-cage-code.document-source-cage-code (FK) design-cage-code
document-alphanumeric-identifier (FK) material-generic-identifier
document-type-code (FK) material-identification
ci-nomenclature (FK)
document-type-code product-type-code
abl-top--level-indicator
fbl-indicator

product-type-code
document-type-code

PSPEC-DEFPIN / 102
CAGE-NUM-DOCREV / 023 (from 1GEN4) PSPEC-DEFMAT / 103
design-cage-code (FK)
document-source-cage-code design-cage-code (FK)
document-alphanumeric-identifier (FK)
document-alphanumeric-identifier material-document-identifier.(document-type-code,document-alphanumeric-identifier) (FK)
document-type-code (FK)
document-type-code
document-generic-revision

B-52
defines
defines
APPENDIX B

document-type-code
MIL-STD-2549

P
PSPECPIN / 104 (see 3SPEC2,3SPEC3,6ECP2,7NOR3)
design-cage-code (FK) PSPECREV / 101 (de facto child of 100)
P
part-identifier (FK) design-cage-code.document-source-cage-code (FK)
document-alphanumeric-identifier (FK) PSPEC-MATID / 106
document-alphanumeric-identifier (FK) document-type-code (FK) design-cage-code (FK)
document-type-code (FK) document-revision.document-generic-revision (FK) material-document-identifier.(material-generic-identifier,material-document-identifier) (FK)
material-identification (FK)

may define
is documented by
has status Assertion: The relation of PSPECREV / 101 to may define
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

PSPECREV-PINSTAT / 105 is 1:P if the value

of the product-type-code in PSPEC / 100 is 'P' Assertion: The relation of PSPECREV / 101 to P
(for part), and is 1:0 for all other values of PSPECREV-MATSTAT / 107 is 1:P if the value
product-type-code of the product-type-code in PSPEC / 100 is 'M' PSPECRV-MATSTAT / 107
P
(for material), and is 1:0 for all other values of design-cage-code (FK) (AK1)
PSPECRV-PINSTAT / 105 product-type-code material-document-identifier (FK)
design-cage-code (FK) material-identification (FK) (AK1)
part-identifier (FK) document-revision (FK) (AK1)
document-revision (FK)
document-alphanumeric-identifier (FK) (AK1)
FIGURE 03SPEC1 document-alphanumeric-identifier (FK) document-type-code (FK)
PROGRAM SPECIFICATION DEFINITION document-type-code (FK) material-status-code
part-status-code
PSPECREV / 101 (from 3SPEC1) GENERIC-DOC / 010 (from 1GEN2)
design-cage-code document-source-entity-identifier
document-alphanumeric-identifier document-identifier GENERIC-DOCREV / 011 (from 1GEN2)
document-type-code document-type-code document-source-entity-identifier
document-revision document-identifier
document-type-code
document-generic-revision

GENERIC-PIN / 210 (from 5PIN2)

design-enterprise-identifier
part-identifier may be an applicable
document in
may list as an
applicable document may be an
may list as an applicable
may be referred applicable document document in
to in notes of

B-53
PSPECAPPDOC-PIN / 111 PSPECAPPDOC-OTHER / 110
APPENDIX B
MIL-STD-2549

design-cage-code (FK) design-cage-code (FK)

document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
document-type-code (FK) P-SPEC.document-type-code (FK)
document-revision (FK) specification-revision.document-revision (FK)
design-enterprise-identifier (FK) document-source-entity-identifier (FK)
part-identifier (FK) document-identifier (FK)
referenced-document-type-code.document-type-code (FK)
referenced-document-generic-revision.document-generic-revision (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 03SPEC2
APPLICABLE DOCUMENTS LISTED IN PROGRAM SPECIFICATIONS
PSPECREV / 101 (from 3SPEC1) DOD-SCN / 620 (from 15SUP6)
design-cage-code.document-source-cage-code design-cage-code
document-alphanumeric-identifier revised-program--unique-specification-identifier
document-type-code DOCSUP
document-revision scn-identifier

may be changed by
may be part of

B-54
PSPEC-SCN / 449
design-cage-code (FK)
APPENDIX B
MIL-STD-2549

revised-program--unique-specification-identifier.(revised-program--unique-specification-identifier,document-alphanumeric-identifier,document-revision) (FK)
document-type-code (FK)
DOCSUP (FK)
scn-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 03SPEC3
PROGRAM SPECIFICATION CHANGE NOTICE
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.3.2. Table 101, Program-unique specification revisions (PSPECREV). This table is a subtype of Table CAGE-
NUM-DOCREV/023 for the case of document-type-code (DOCTYP010) having a value of 'P-SPEC'. It contains
the history of the various revisions to a program-unique specification. Due to parallel categorization, Table 023 is
a de facto child of Table PSPEC/100.

a. Because this table is a de facto child of Table 100, document-source-enterprise-defense-logistics--

assigned-identification-code (SRCCAG022) inherited from Table 023 is really a design-enterprise-
defense-logistics--assigned-identification-code (DESCAG100) existing in Table 100. Therefore,
SRCCAG022 assumes the identity DESCAG100.

b. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 023 assumes the role
document-alphanumeric-revision-identifier (DOCREV101).

Code Data Element Title DED Key

FRSTRT101 materiel-item-first-article-test-code 0077 M

SPCCAT101 specification-document-category-code 0105 M

B.5.3.3. Table 102, Specification-defined parts (PSPEC-DEFPIN). This table is a subtype of Table PSPEC/100
containing the subset of program-unique specifications which define part numbered items.

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK

B.5.3.4. Table 103, Specification-defined material (PSPEC-DEFMAT). This table is a subtype of Table PSPEC/
100 which contains the subset of program-unique specifications which define materials which are not identified by
part numbers.

a. The attributes document-alphanumeric-identifier (DOCNUM020) and document-type-code

(DOCTYP010) inherited from Table 100 are concatenated and assume the role material-document-
identifier (MATDOC103). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
MATDOC103 material-document-identifier 0192 FK

B-55
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.3.5. Table 104, Part numbers defined by program-unique specifications (PSPECPIN). This table is a subtype
of Table CAGEPIN/212 containing the subset of generic part numbers which is limited to those part numbers
identified by a program-unique specification identified by a CAGE (or NSCM) code and number. (Note:
frequently, the numbered-document-identifier [DOCNUM020] is embedded in the part-product-identifier
[PARNUM210] as the left-most characters in the string.)

a. The value of DOCTYP010 must be the same as the value of document-type-code (DOCTYP212) for the
super-type in Table 212.

b. Fields DESCAG100 inherited from Table 102 and DESCAG212 inherited from Table 212 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG104).

Code Data Element Title DED Key

DESCAG104 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
PARNUM210 part-product-identifier 0024 FK

DOCNUM020 document-alphanumeric-identifier 0003 FK

DOCTYP010 document-type-code 0004 FK

B.5.3.6. Table 105, Correlation of part numbers to program specification revisions in which they are defined
(PSPECRV-PINSTAT). This table correlates part numbers with the specific revision(s) of the specification in
which they are/were defined.

a. For each instance in this table, the combination of the document-alphanumeric-identifier (DOCNUM020)
and document-type-code (DOCTYP010) must be the same as the combination of the same values in Table
SPECPIN/104 for the parent instance.

b. Fields DESCAG100 inherited from Table 101 and DESCAG104 inherited from Table 104 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG105).

Code Data Element Title DED Key

DESCAG105 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV101 document-alphanumeric-revision-identifier 0009 FK
PARNUM210 part-product-identifier 0024 FK

DOCNUM020 document-alphanumeric-identifier 0003 FK

DOCTYP010 document-type-code 0004 FK
PARSTA105 part-product-status-code 0035 M

B.5.3.7. Table 106, Materials defined by program-unique specifications (PSPEC-MATID). This table is a subtype
of Table CAGE-MATID/205 containing the subset of generic materials which is limited to those materials
identified by a program-unique specification identified by a CAGE (or NSCM) code and number.

B-56
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Fields DESCAG100 inherited from Table 103 and DESCAG205 inherited from Table 205 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG106).

b. Attribute material-document-identifier (MATDOC103) inherited from Table 103 and material-product-

generic-identifier (MATGID200) inherited from Table 205 must both have the same value. Therefore
they merge and assume the identity material-document-identifier (MATDOC103).

Code Data Element Title DED Key

DESCAG106 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
MATDOC103 material-document-identifier 0192 FK
MATIDN200 material-product-identifier 0038 FK

B.5.3.8. Table 107, Program-unique specification-defined material status (PSPECRV-MATSTAT). This table
correlates parts and materials which are not identified by part numbers with the specific revision(s) of the
specification in which they are/were defined.

a. Fields DESCAG100 inherited from Table 101 and DESCAG106 inherited from Table 106 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG107).

Code Data Element Title DED Key

DESCAG107 design-enterprise-defense-logistics--assigned-identification- 0001 FK, AK1
code
DOCREV101 document-alphanumeric-revision-identifier 0009 FK, AK1
MATDOC103 material-document-identifier 0192 FK
MATIDN200 material-product-identifier 0038 FK, AK1

DOCNUM020 document-alphanumeric-identifier 0003 FK, AK1

DOCTYP010 document-type-code 0004 FK, AK1
MATSTA107 material-product-status-code 0035 M

B.5.3.9. Tables 108 and 109. Reserved.

B.5.3.10. Table 110, Documents listed as applicable documents in a program-unique specification (PSPEC-
APPDOC). This table identifies documents which are included as lower-tier references in the applicable document
section of a program-unique specification. This information is required for the creation of Data List drawings.

a. If the value of the referenced-document-type-code (RDOCTY110) is 'P-SPEC', then the combination of

values for design-enterprise-defense-logistics--assigned-identification-code (DESCAG0100) and
document-alphanumeric-identifier (DOCNUM020) (which identify the specification) cannot be the same
as the combination of values for document-source-entity-identifier (SRCIDN010) and document-identifier
(DOCIDN010) (which identify the referenced document).

B-57
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 011 assumes the role
referenced-document-generic-revision-identifier (RDOCRV110).

c. Attribute document-type-code (DOCTYP010) inherited from Table 010 and document-type-code

(DOCTYP010) inherited from Table 011 must have the same value and merge to assume the role
referenced-document-type-code (RDOCTY110).

d. Attribute document-alphanumeric-revision-identifier (DOCREV101) inherited from Table 101 assumes

the role program--unique-specification-document-alphanumeric-revision-identifier (SPECRV110).

e. Attribute document-type-code (DOCTYP010) inherited from Table 101 assumes the role program--
unique-specification-document-type-code (SPECTY110).

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCIDN010 document-identifier 0122 FK
DOCNUM020 document-alphanumeric-identifier 0003 FK
RDOCTY110 referenced-document-type-code 0004 FK
SPECRV110 program--unique-specification-document-alphanumeric- 0009 FK
revision-identifier
SPECTY110 program--unique-specification-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

RDOCRV110 referenced-document-generic-revision-identifier 0243 FK, O

B.5.3.11. Table 111, Part numbers listed as applicable documents in a program-unique specification
(PSPECAPPDOC-PIN). This table identifies part numbers which are included as lower-tier references in the
applicable document section of a program-unique specification. This information is required for the creation of
Data List drawings.

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT210 design-enterprise-identifier 0052 FK
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV101 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
PARNUM210 part-product-identifier 0024 FK

B.5.3.12. Tables 112 through 149. Reserved.

B-58
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.4. Software and software support documents. Entity tables numbered in the range of 150 through 199
contain the identification of software and software support documents (such as user manuals, etc.), including those
which comply with either old or current military standards, or common commercial practices. This means that the
contents of this section includes:

a. software which is identified by a CAGE (or NSCM) code and a drawing-based part number,

b. software which is identified by a CAGE (or NSCM) code and a software number,

c. software which is identified by a basic number and dash number (similar to a drawing-based part number,
but independent of any drawing),

d. software which is identified by a company name and software product name, and

e. software support documents (including software version description documents) which are identified by a
CAGE (or NSCM) code and a document number,

f. software support documents (including software version description documents) which are identified by a
company name and a document number or document title.

This series of tables includes all the software and software support document attributes which are necessary to the
configuration management of the documents or the software products. Because there are no standards in this area,
software is treated both as a document and as a product. This maximizes flexibility in this area while still
providing the necessary configuration controls. By treating it as a document, the general rules which apply to any
document can be applied (such as security markings and document representations, etc.). This approach facilitates
correlation of source and executable code. By treating software as a product, the generic supertype can be used in
parts lists and other references. This section also includes the relationship between software and software
drawings, between software and software support documents, and between software and software version
description documents. This section also addresses those parameters of the U.S. Air Force-assigned Computer
Program Identification Number (CPIN) which can be used for CM. The relationships between these various entity
tables are depicted in Figures 04SW1 through 04SW4.

B.5.4.1. Table 150, Software definition (SW). This table contains the unique identifier of software as a document
(for software treated as a product, see Table 170). It is one subtype of Table GENERIC-DOC/010 for the case
where document-type-code has a value of 'SW'. It includes both defense software (identified by a CAGE code) and
commercial software (identified by an author, company, or organization acronym).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

SWPARA150 software-product-identification-paradigm-type-code 0163 M

B-59
GENERIC-DOC / 010 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code GENERIC-DOCREV / 011 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-generic-revision
document-type-code
SW SWDOC
SVD

SW / 150 SVD / 180 (see 4SW3) SWDOC / 185

document-source-entity-identifier (FK) document-source-entity-identifier (FK) software-support-document-source-entity-identifier.document-source-entity-identifier (FK)
document-identifier (FK) svd-identifier.document-identifier (FK) document-identifier (FK) document-type-code
document-type-code (FK) SVD.document-type-code (FK) document-type-code (FK)
software-paradigm-code software-support-document-subsidiary-type-code

SW SWDOC

ENTITY / 000 (from 1GEN1) SWVER / 151 (de facto child of 150) SWDOCREV / 186 (de facto child of 185) (see 4SW3)
entity-identifier document-source-entity-identifier (FK) (AK1) software-support-document-source-entity-identifier.document-source-entity-identifier (FK)
document-identifier (FK) software-support-document-identifier.document-identifier (FK)
document-type-code (FK) SWDOC.document-type-code (FK)
document-generic-revision (FK) software-support-document-generic-revision.document-generic-revision (FK)
may define

SWROOT / 155
software-source-identifier.entity-identifier (FK) document-identification-type-code (from 010)
software-paradigm-code
software-root-identifier

B-60
(from 150) N
R
SWVER-NUM / 152 (de facto child of 021) (see 4SW2)
APPENDIX B
MIL-STD-2549

has variations software-paradigm-code document-source-entity-identifier (FK)

P document-alphanumeric-identifier.document-identifier (FK)
document-type-code (FK)
SWDASH / 156 R document-generic-revision (FK)
D
software-source-identifier (FK) software-source-enterprise-type-code
software-root-identifier (FK)
software-dash-identifier
SWREL-PARADIGM / 158
document-source-entity-identifier (FK) SWRELEASE / 159 (de facto child of 158) (see 4SW3)
document-identifier (FK) software-source-identifier.document-source-entity-identifier (FK)
is document-type-code (FK) document-identifier (FK)
document-type-code (FK)
software-version.document-generic-revision (FK)

1 P
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

SWDASH-PARADIGM / 157 (see 4SW3)

software-source-identifier.(document-source-entity-identifier,software-source-identifier) (FK) SWDWG-PARADIGM / 160 (see4SW2)
software-alphanumeric-identifier.(document-identifier,software-root-identifier,software-dash-identifier) (FK)
document-type-code (FK) document-source-entity-identifier (FK)
drawing-alphanumeric-identifier.document-identifier (FK)
document-type-code (FK)
software-source-enterprise-type-code

FIGRUE 04SW1
SOFTWARE CODE & DOCUMENTS (Part 1 of 2)
SWDWG-PARADIGM / 160 (from 4SW1)
document-source-entity-identifier
drawing-alphanumeric-identifier
document-type-code
software-source-enterprise-type-code

software-source-enterprise-type-code
CAG COM
PICDWG / 060 (from 2DWG1) SWCAGE / 161
SWCOMM / 162 COMDWG / 912 (from 24COM1)
design-cage-code design-cage-code.document-source-entity-identifier (FK)
design-company-name.document-source-entity-identifier (FK) design-company-name
drawing-alphanumeric-identifier drawing-alphanumeric-identifier (FK)
drawing-alphanumeric-identifier (FK) drawing-alphanumeric-identifier
document-type-code document-type-code (FK)
document-type-code (FK) document-type-code

SWVER-NUM / 152 (from 4SW1)

may document document-source-entity-identifier may be identified by may document
may be identified by
document-alphanumeric-identifier
Z document-type-code
Z
document-generic-revision
SW-DWG / 163 SW-COMDWG / 165
software-source-enterprise-type-code
design-cage-code (FK) design-company-name (FK)
drawing-alphanumeric-identifier (FK) drawing-alphanumeric-identifier (FK)
DWG.document-type-code (FK) DWG.document-type-code (FK)
software-source-enterprise-type-code
SW.document-type-code (FK) SW.document-type-code (FK)
CAG COM
DWGPIN / 053 (from 2DWG2)

B-61
design-cage-code SWVER-CAGE / 153 (de facto child of 022) (see 6ECP2, 10RFD2) SWVER-COMM / 154 (de facto child of 026)
part-identifier
design-cage-code.document-source-entity-identifier (FK) design-company-name.document-source-entity-identifier (FK)
COMPIN / 920 (from 24COM2)
APPENDIX B

drawing-alphanumeric-identifier document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)

MIL-STD-2549

document-type-code document-type-code (FK) document-type-code (FK) design-company-name

document-generic-revision (FK) software-version.document-generic-revision (FK) part-identifier

may be equivalent to
may be equivalent to
documents software iterations documents
Z P Z software
may be iterations
SW-PIN / 164 (see 4SW3)
equivalent to
design-cage-code (FK) (AK1)
part-identifier (FK)
drawing-alphanumeric-identifier.(drawing-alphanumeric-identifier,document-alphanumeric-identifier) (FK) (AK1)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

DWG (FK) may be equivalent to

SW.document-type-code (FK) (AK1)
software-version.document-generic-revision (FK) (AK1)
Z P Z
SW-COMPIN / 166 (see 4SW3)
design-company-name (FK) (AK1)
part-identifier (FK)
FIGURE 04SW2
drawing-alphanumeric-identifier.(document-alphanumeric-identifier,drawing-alphanumeric-identifier) (FK) (AK1)
SOFTWARE CODE & DOCUMENTS (Part 2 of 2)
DWG (FK)
SW.document-type-code (FK) (AK1)
software-version (FK) (AK1)
ENTITY / 000 (from 1GEN1) (see 4SW4,5PIN4,5PIN5,5PIN6,7NOR5,10RFD2,19CI1,23FILE1)
GENERIC-SWPROD / 170
entity-identifier may define
software-source-identifier.(entity-identifier,document-source-entity-identifier) (FK) may be
software-generic-identifier documented/
supported by
svd-identifier (FK)
SVD / 180 (from 4SW1) SVD (FK)
document-source-entity-identifier software-paradigm-code
svd-identifier.document-identifier describes
SVD.document-type-code SW-SWSUPDOC / 187
software-support-document-source-entity-identifier (FK)
software-support-document-identifier (FK)
SWDOC (FK)
SWDASH-PARADIGM / 157 (from 4SW1) software-support-document-revision (FK)
software-source-identifier software-paradigm-code software-source-identifier (FK)
software-alphanumeric-identifier software-generic-identifier (FK)
document-type
R
P
D supports
SWPROD-PIN / 173 SW-COMPIN / 166 (from 4SW2)
SW-PIN / 164 (from 4SW2)
software-source-identifier (FK) design-company-name SWDOCREV / 186 (from 4SW1)
design-cage-code software-generic-identifier (FK) part-identifier
part-identifier software-support-document-source-entity-identifier
software-source-enterprise-type-code software-support-document-identifier
SWDOC
software-source-enterprise-type-code software-support-document-revision
is is

B-62
1 CAG COM
APPENDIX B
MIL-STD-2549

SWPROD-CAGEPIN / 174 is
design-cage-code.(software-source-identifier,design-cage-code) (FK)
part-identifier.(software-generic-identifier,part-identifier) (FK) SWRELEASE / 159 (from 4SW1)
software-source-identifier
1 document-identifier
document-type
SWPROD-COMPIN / 175 software-version
design-company-name.(software-source-identifier,design-company-name) (FK)
software-alphanumeric-identifier.software-generic-identifier (FK)

1 part-identifier.part-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

is
SWPROD-DASH / 171
software-source-identifier (FK)
software-generic-identifier (FK)
1
software-alphanumeric-identifier.software-alphanumeric-identifier (FK)
SWPROD-RELEASE / 172
document-type (FK)
software-source-identifier (FK)
software-identifier.(software-generic-identifier,software-version,document-identifier) (FK)
FIGURE 04SW3
SOFTWARE PRODUCT document-type (FK)
CPIN / 190
cpin

cpin-type-code
(embedded in cpin-designator)

C or D F, S, T, or U

CPIN-TYPECD / 191 CPIN-TYPEFSTU / 192

cpin (FK) cpin (FK)

B-63
is the master of,
or combination of may be part of GENERIC-SWPROD / 170 (from 4SW3)
APPENDIX B

cpin-applicability-code
MIL-STD-2549

software-source-identifier
(embedded in cpin-designator) software-generic-identifier

2
COMBO-CPIN / 193 A
component-cpin.cpin (FK) may be alternately identified by
combination-cpin.cpin (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

CPIN-APPA / 194
cpin (FK)
FIGURE 04SW4 software-source-identifier (FK)
CPIN software-generic-identifier (FK)
media-type
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.4.2. Table 151, Software versions/version description document definition (SWVER). This table is a subtype
of Table GENERIC-DOCREV/011 for the case where the value of document-type-code is 'SW' and identifies
software versions. Due to parallel categorization, this table is a de facto child of Table SW/150. This table has two
subtypes based on the value of document-identification-type-code (IDNTYP010 in Table 010) and three subtypes
based on the value of software-product-identification-paradigm-type-code (SWPARA150 in Table 150).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK, AK1

COMIDN151 computer-software-compiler-asset-identifier 0031

COMVER151 computer-software-compiler-asset-version-identifier 0064
HWNAME151 computer-hardware-asset-nomenclature-identifier 0031
LNKIDN151 computer-software-link-asset-identifier 0031
LNKVER151 computer-software-link-asset-version-identifier 0064
SYSIDN151 computer-operating-system-software-asset-identifier 0031 M
SYSVER151 computer-operating-system-software-asset-version-identifier 0064

B.5.4.3. Table 152, Versions of software identified by an alphanumeric identifier (SWVER-NUM). This table is
one subtype of Table SWVER/151 for the case in which the value of document-identification-type-code in Table
GENERIC-DOC/010 is 'N'. It includes that software which is identified by an alphanumeric identifier rather than
by a name. Due to parallel categorization, this table is a de facto child of Table NUMDOCREV/021.

a. Because this table is a de facto child of Table 021, document-identifier (DOCIDN010) inherited from
Table 151 is really a document-alphanumeric-identifier (DOCNUM020) existing in Table 021. Therefore,
DOCIDN010 assumes the identity DOCNUM020.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

SRCTYP152 software-product-source-enterprise-identification-type-code 0050 M

B.5.4.4. Table 153, Versions of software identified by CAGE code and alphanumeric identifier (SWVER-CAGE).
This table is one subtype of Table SWVER-NUM/152 for the case in which the value of software-product-source-
enterprise-identification-type-code (SRCTYP152) in Table 152 is 'CAG'. It includes that software which is
identified by a CAGE code (rather than by a company name) and an alphanumeric identifier (rather than by a
name). By examination, it can be demonstrated that this table is equally applicable to all three categories of
software (based on the software identification paradigm). Because the software-product-source-enterprise-
identification-type-code has values which are a subset of the source-enterprise-identification-type-code in Table

B-64
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ENTERPRISE/002, it can be shown that due to parallel categorization this table is a de facto child of Table CAGE-
NUM-DOC/022.

a. Because this table is a de facto child of Table 022, the value of document-source-entity-identifier
(SRCIDN010) inherited from Table 152 must exist as a document-source-enterprise-defense-logistics--
assigned-identification-code (SRCCAG022) in Table 022. SRCIDN010 assumes the role design-
enterprise-defense-logistics--assigned-identification-code (DESCAG153).

Code Data Element Title DED Key

B.5.4.5. Table 154, Versions of software identified by a company name and alphanumeric identifier (SWVER-
COMM). This table is one subtype of Table SWVER-NUM/152 for the case in which the value of software-
product-source-enterprise-identification-type-code (SRCTYP152) in Table 152 is 'COM'. It includes that software
which is identified by a company name (rather than by a CAGE code) and an alphanumeric identifier (rather than
by a name). Because the software-product-source-enterprise-identification-type-code has values which are a
subset of the source-enterprise-identification-type-code in Table ENTERPRISE/002, it can be shown that due to
parallel categorization this table is a de facto subtype of Table COMPANY-NUM-DOCREV/027.

a. Because this table is a de facto subtype of Table027, the value of document-source-entity-identifier

(SRCIDN010) inherited from Table 152 must exist as a commercial-document-source-enterprise-name
(SRCCOM026) in Table 027. SRCIDN010 assumes the role design-enterprise-name (DESCOM154).

b. Because this table is a de facto subtype of Table027, the value of document-generic-revision-identifier

(DOCREV011) inherited from Table 152 must exist as a document-generic-revision-identifier
(DOCREV011) in Table 027. DOCREV011 assumes the role software-product-version-identifier
(SWVERS154).

Code Data Element Title DED Key

DESCOM154 design-enterprise-name 0170 FK
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SWVERS154 software-product-version-identifier 0062 FK

B.5.4.6. Table 155, Software root identifier for the software-dash number identification paradigm (SWROOT).
This table identifies the basic (root) software identifiers used for identification of software programs or databases
using the software-dash number paradigm. (See Table 157 for a more in depth discussion of the software-dash
number paradigm.)

a. Attribute entity-identifier (ENTYID000) inherited from Table 000 assumes the role software-product-
source-entity-identifier (SWSORC155).

B-65
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

SWROOT155 software-product-basic-application-alphanumeric-identifier 0190 K
SWSORC155 software-product-source-entity-identifier 0033 FK

B.5.4.7. Table 156, Software dash identifiers for the software-dash number paradigm (SWDASH). This table
identifies the basic (root) software identifiers used for identification of software programs or databases using the
software-dash number paradigm and correlates them with the assigned suffix (dash) numbers.

Code Data Element Title DED Key

SWDASH156 software-product-application-suffix-alphanumeric-identifier 0222 K
SWROOT155 software-product-basic-application-alphanumeric-identifier 0190 FK
SWSORC155 software-product-source-entity-identifier 0033 FK

B.5.4.8. Table 157, Software identifiers using the software-dash number paradigm (SWDASH-PARADIGM).
This table is one category of software identification paradigm. It contains the software identifiers which identify
software programs or databases when the software-dash number paradigm is used. Using this paradigm, each
significant change to software (resulting in the noninterchangeability of releases) is identified by a basic (root)
identifier followed by a hyphen and a suffix. The basic identifier ties all releases of one software program together;
the suffix identifies significant differences between releases. Each release may have multiple versions; however,
all versions in a single release must be interchangeable.

a. Field DOCIDN010 from Table 150 must contain the same value as the concatenation of fields
SWROOT155 and SWDASH156 (both from Table 156); therefore, DOCIDN010 assumes the identity
software-product-alphanumeric-identifier (SWNUMB157).

b. The attributes software-product-application-suffix-alphanumeric-identifier (SWDASH156) and software-

product-basic-application-alphanumeric-identifier (SWROOT155) inherited from Table 156 are
concatenated and assume the role software-product-alphanumeric-identifier (SWNUMB157). (See
Appendix C for concatenation order.)

c. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 150 and software-product-

source-entity-identifier (SWSORC155) inherited from Table 156 must both have the same value.
Therefore they merge and assume the identity software-product-source-entity-identifier (SWSORC155).

Code Data Element Title DED Key

DOCTYP010 document-type-code 0004 FK
SWNUMB157 software-product-alphanumeric-identifier 0088 FK
SWSORC155 software-product-source-entity-identifier 0033 FK

B.5.4.9. Table 158, Software identifiers using the software release paradigm (SWREL-PARADIGM). This table is
one category of software identification paradigm. It contains the software identifiers which identify software
programs or databases when the software release paradigm is used. Using this paradigm, each change to software
is identified by a name or basic identifier followed by a release (or version) identifier. The name/basic identifier
ties all releases of one software program (or database) together; the release (or version) identifies differences

B-66
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

between releases. Although changes in software are identified, no guaranty of interchangeability is expressed or
implied by this method.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.4.10. Table 159, Software releases for the software release paradigm (SWRELEASE). This table contains
the iterations (releases/versions) of software when the software release paradigm is used. Due to parallel
categorization, this table is a de facto child of Table SWREL-PARADIGM/158.

a. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 151 assumes the role
software-product-source-entity-identifier (SWSORC159).

b. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 151 assumes the role
software-product-version-identifier (SWVERS159).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SWSORC159 software-product-source-entity-identifier 0033 FK
SWVERS159 software-product-version-identifier 0062 FK

B.5.4.11. Table 160, Software identifiers for the software drawing paradigm (SWDWG-PARADIGM). This
table is one category of software identification paradigm. It contains the software identifiers which identify
software programs or databases when the software drawing paradigm is used. Using this paradigm, each change to
software is identified by a part identification number (PIN) on an engineering drawing. The engineering drawing
identifier ties all releases of one software program (or database) together; the PIN identifies differences between
releases (or versions). All changes in software are uniquely identified; therefore, noninterchangeability of
sequential releases/versions is implied by this method.

a. Attribute document-identifier (DOCIDN010) inherited from Table 150 assumes the role engineering-
drawing-document-alphanumeric-identifier (DWGNUM160).

Code Data Element Title DED Key

DOCTYP010 document-type-code 0004 FK
DWGNUM160 engineering-drawing-document-alphanumeric-identifier 0003 FK
SRCIDN010 document-source-entity-identifier 0033 FK

SRCTYP160 software-product-source-enterprise-identification-type-code 0050 M

B.5.4.12. Table 161, Software with a source identified by a CAGE code (SWCAGE). This table is one category
of Table SWDWG-PARADIGM/160 for the case when the software-product-source-enterprise-identification-type-

B-67
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

code (SRCTYP160) in Table 160 has a value of 'CAG' indicating that the software source is identified by a CAGE
code. Examination of categorization will prove that the design-enterprise-defense-logistics--assigned-
identification-code (DESCAG161) must exist as an enterprise-defense-logistics--assigned-identification-code
(CAGNUM003) in Table CAGE/003.

a. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 160 assumes the role
design-enterprise-defense-logistics--assigned-identification-code (DESCAG161).

Code Data Element Title DED Key

DESCAG161 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCTYP010 document-type-code 0004 FK
DWGNUM160 engineering-drawing-document-alphanumeric-identifier 0003 FK

B.5.4.13. Table 162, Software with a source identified by a company name (SWCOMM). This table is one
category of Table SWDWG-PARADIGM/160 for the case when the software-product-source-enterprise-
identification-type-code (SRCTYP160) in Table 160 has a value of 'COM' indicating that the software source is
identified by a company name. Examination of categorization will prove that the design-enterprise-name
(DESCOM162) must exist as a commercial-enterprise-name (COMNAM005) in Table COMPANY/005.

a. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 160 assumes the role
design-enterprise-name (DESCOM162).

Code Data Element Title DED Key

DESCOM162 design-enterprise-name 0170 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM160 engineering-drawing-document-alphanumeric-identifier 0003 FK

B.5.4.14. Table 163, Correlation of software to software drawings (SW-DWG). This table correlates software
identifiers to drawing number when there is a requirement to use software drawings.

a. Fields DESCAG050 inherited from Table 060 and DESCAG161 inherited from Table 161 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG163).

b. Fields DWGNUM050 inherited from Table 060 and DWGNUM160 inherited from Table 161 must be the
same; therefore, they assume the identity engineering-drawing-document-alphanumeric-identifier
(DWGNUM163).

c. Attribute document-type-code (DOCTYP010) inherited from Table 060 assumes the role engineering-
drawing-document-type-code (DWGTYP163).

d. Attribute document-type-code (DOCTYP010) inherited from Table 161 assumes the role software-
document-type-code (SWTYPE163).

B-68
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DESCAG163 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM163 engineering-drawing-document-alphanumeric-identifier 0003 FK
DWGTYP163 engineering-drawing-document-type-code 0004 FK

SWTYPE163 software-document-type-code 0004 FK

B.5.4.15. Table 164, Correlation of software to drawing/part number (SW-PIN). This table correlates software
identifiers to part number when there is a requirement to use software drawings.

a. The value of the engineering-drawing-document-alphanumeric-identifier (DWGNUM164) for each

instance in this table must be the same as the value of the engineering-drawing-document-alphanumeric-
identifier (DWGNUM050) in Table DWGPIN/053 for the parent instance.

b. Fields DESCAG053 inherited from Table 053, DESCAG153 inherited from Table 153, and DESCAG163
inherited from Table 163 must be the same. Therefore, they merge and assume the identity design-
enterprise-defense-logistics--assigned-identification-code (DESCAG164).

c. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 153 and engineering-

drawing-document-alphanumeric-identifier (DWGNUM163) inherited from Table 163 must both have the
same value. Therefore they merge and assume the identity engineering-drawing-document-alphanumeric-
identifier (DWGNUM164).

d. Attribute document-type-code (DOCTYP010) inherited from Table 153 assumes the role software-
document-type-code (SWTYPE164).

e. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 153 assumes the role
software-product-version-identifier (SWVERS164).

Code Data Element Title DED Key

DESCAG164 design-enterprise-defense-logistics--assigned-identification- 0001 FK, AK1
code
PARNUM210 part-product-identifier 0024 FK

DWGNUM164 engineering-drawing-document-alphanumeric-identifier 0003 FK, AK1

DWGTYP163 engineering-drawing-document-type-code 0004 FK
SWTYPE164 software-document-type-code 0004 FK, AK1
SWVERS164 software-product-version-identifier 0062 FK, AK1

B.5.4.16. Table 165, Correlation of commercial software to commercial software drawings (SW-COMDWG).
This table correlates commercial software identifiers to the commercial drawing number when the software
drawings paradigm is used for software identification of commercial software.

a. Fields DESCOM162 inherited from Table 162 and DESCOM912 inherited from Table 912 must be the
same; therefore, they assume the identity design-enterprise-name (DESCOM165).

B-69
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Fields DWGNUM160 inherited from Table 162 and DWGNUM912 inherited from Table 912 must be the
same; therefore, they assume the identity engineering-drawing-document-alphanumeric-identifier
(DWGNUM165).

c. Attribute document-type-code (DOCTYP010) inherited from Table 912 assumes the role engineering-
drawing-document-type-code (DWGTYP165).

d. Attribute document-type-code (DOCTYP010) inherited from Table 162 assumes the role software-
document-type-code (SWTYP165).

Code Data Element Title DED Key

DESCOM165 design-enterprise-name 0170 FK
DWGNUM165 engineering-drawing-document-alphanumeric-identifier 0003 FK
DWGTYP165 engineering-drawing-document-type-code 0004 FK

SWTYP165 software-document-type-code 0004 FK

B.5.4.17. Table 166, Correlation of commercial software to a commercial drawing/part number (SW-
COMPIN). This table correlates commercial software identifiers to a commercial part number when the software
drawing paradigm is used.

a. Fields DESCOM154 inherited from Table 154, DESCOM165 inherited from Table 165, and
DESCOM919 inherited from Table 920 must be the same. Therefore, they merge and assume the identity
commercial-enterprise-name (DESCOM166).

b. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 154 and engineering-

drawing-document-alphanumeric-identifier (DWGNUM165) inherited from Table 165 must both have the
same value. Therefore they merge and assume the identity engineering-drawing-document-alphanumeric-
identifier (DWGNUM165).

c. Attribute document-type-code (DOCTYP010) inherited from Table 154 assumes the role software-
document-type-code (SWTYPE166).

Code Data Element Title DED Key

DESCOM166 commercial-enterprise-name 0170 FK, AK1
PARNUM210 part-product-identifier 0024 FK

DWGNUM165 engineering-drawing-document-alphanumeric-identifier 0003 FK, AK1

DWGTYP165 engineering-drawing-document-type-code 0004 FK
SWTYPE166 software-document-type-code 0004 FK, AK1
SWVERS154 software-product-version-identifier 0062 FK, AK1

B.5.4.18. Tables 167 through 169. Reserved.

B.5.4.19. Table 170, Generic identification of software (GENERIC-SWPROD). This table is the generic super-
type of software identification which includes the identification of all software which is by part number, name and

B-70
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

release/version, or other identification. This table has three subtypes: SWPROD-DASH/171, SWPROD-
RELEASE/172, and SWPROD-PIN/173.

a. The entity-identifier (ENTYID000) inherited from Table 000 assumes the identity software-product-
source-entity-identifier (SWSORC170). If there is a related software version description document, the
document-source-entity-identifier (SRCIDN010) must have the same value as SWSORC170.

Code Data Element Title DED Key

SWIDEN170 software-product-generic-identifier 0060 K
SWSORC170 software-product-source-entity-identifier 0033 FK

SVDNUM180 software-version-description-document-alphanumeric- 0003 FK, O

identifier
SVDTYP180 software-version-description-document-type-code 0004 FK, O
SWPARA170 software-product-identification-paradigm-type-code 0163 M

B.5.4.20. Table 171, Software product identified by dash numbers (SWPROD-DASH). This table is one
category of GENERIC-SWPROD/170 for the case when the value of software-product-identification-paradigm-
type-code (SWPARA170) is 'D'. It consists of those software products which are identified using the software-dash
number paradigm. It relates the software product identifier to the software document identifier (which contains the
code or other files).

a. Attribute software-product-alphanumeric-identifier (SWNUMB157) inherited from Table 157 and

software-product-generic-identifier (SWIDEN170) inherited from Table 170 must both have the same
value. Therefore they merge and assume the identity software-product-alphanumeric-identifier
(SWNUMB157).

b. Fields SWSORC155 inherited from Table 157 and SWSORC170 inherited from Table 170 must be the
same; therefore, they assume the identity software-product-source-entity-identifier (SWSORC171).

Code Data Element Title DED Key

SWNUMB157 software-product-alphanumeric-identifier 0088 FK
SWSORC171 software-product-source-entity-identifier 0033 FK

DOCTYP010 document-type-code 0004 FK

B.5.4.21. Table 172, Software products identified by the release or version number (SWPROD-RELEASE).
This table is one category of GENERIC-SWPROD/170 for the case when the value of software-product-
identification-paradigm-type-code (SWPARA170) is 'R'. It consists of those software products which are identified
using the software release (or version) paradigm. It relates the software product identifier to the software
document identifier (which contains the code or other files).

a. The concatenation of the values of document-identifier (DOCIDN010) and software-product-version-

identifier (SWVERS159) inherited from Table SWRELEASE/159 must the same value as the software-
product-generic-identifier (SWIDEN170) inherited from Table 170; therefore, they are merged and
assume the identity software-product-identifier (SWPIDN172).

B-71
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Fields SWSORC159 inherited from Table 159 and SWSORC170 inherited from Table 170 must be the
same; therefore, they assume the identity software-product-source-entity-identifier (SWSORC172).

Code Data Element Title DED Key

SWPIDN172 software-product-identifier 0262 FK
SWSORC172 software-product-source-entity-identifier 0033 FK

DOCTYP010 document-type-code 0004 FK

B.5.4.22. Table 173, Software products identified by a drawing-related part number (SWPROD-PIN). This
table is one category of GENERIC-SWPROD/170 for the case when the value of software-product-identification-
paradigm-type-code (SWPARA170) is 'P'. It consists of those software products which are identified using the
software drawing number paradigm. It has two subtypes: SWPROD-CAGEPIN/174 and SWPROD-COMPIN/
175.

Code Data Element Title DED Key

SWIDEN170 software-product-generic-identifier 0060 FK
SWSORC170 software-product-source-entity-identifier 0033 FK

SRCTYP173 software-product-source-enterprise-identification-type-code 0050 M

B.5.4.23. Table 174, Software products identified by a CAGE code and a drawing-related part number
(SWPROD-CAGEPIN). This table is one category of SWPROD-PIN/173 for the case when the value of software-
product-source-enterprise-identification-type-code (SRCTYP173) is 'CAG'. It consists of those software products
which are identified using the software drawing paradigm with parts/drawings identified by a CAGE code and
alphanumeric identifier. It relates the software product identifier to the software part number and related drawing
(which contains the code or other files).

a. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG164) inherited from

Table 164 and software-product-source-entity-identifier (SWSORC170) inherited from Table 173 must
both have the same value. Therefore they merge and assume the identity design-enterprise-defense-
logistics--assigned-identification-code (DESCAG164).

b. Attribute part-product-identifier (PARNUM210) inherited from Table 164 and software-product-generic-

identifier (SWIDEN170) inherited from Table 170 must both have the same value. Therefore they merge
and assume the identity part-product-identifier (PARNUM210).

Code Data Element Title DED Key

DESCAG164 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
PARNUM210 part-product-identifier 0024 FK

B.5.4.24. Table 175, Software products identified by a company name and a drawing-related part number
(SWPROD-COMPIN). This table is one category of SWPROD-PIN/173 for the case when the value of software-
product-source-enterprise-identification-type-code (SRCTYP173) is 'COM'. It consists of those software products
which are identified using the software drawing paradigm with parts/drawings identified by a company name and

B-72
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

alphanumeric identifier. It relates the software product identifier to the software part number and related
commercial drawing (which contains the code or other files).

a. Attribute commercial-enterprise-name (DESCOM166) inherited from Table 166 and software-product-

source-entity-identifier (SWSORC170) inherited from Table 173 must both have the same value.
Therefore they merge and assume the identity commercial-enterprise-name (DESCOM166).

b. Attribute part-product-identifier (PARNUM210) inherited from Table 166 and software-product-generic-

identifier (SWIDEN170) inherited from Table 173 must both have the same value. Therefore they merge
and assume the identity part-product-identifier (PARNUM210).

Code Data Element Title DED Key

DESCOM166 commercial-enterprise-name 0170 FK
PARNUM210 part-product-identifier 0024 FK

B.5.4.25. Tables 176 through 179. Reserved.

B.5.4.26. Table 180, Software version description definition (SVD). This table contains the unique identifier of
software version description documents. A software version description document is one subtype of a Table
GENERIC-DOC/010 for the case where document-type-code has a value of 'SVD'.

a. Attribute document-identifier (DOCIDN010) inherited from Table 010 assumes the role software-version-
description-document-alphanumeric-identifier (SVDNUM180).

b. Attribute document-type-code (DOCTYP010) inherited from Table 010 assumes the role software-version-
description-document-type-code (SVDTYP180).

Code Data Element Title DED Key

SRCIDN010 document-source-entity-identifier 0033 FK
SVDNUM180 software-version-description-document-alphanumeric- 0003 FK
identifier
SVDTYP180 software-version-description-document-type-code 0004 FK

B.5.4.27. Tables 181 through 184. Reserved.

B.5.4.28. Table 185, Software support document identification (SWDOC). This table contains the unique
identifier of software support documents. Software support documents are one subtype of Table GENERIC-DOC/
010 for the case where document-type-code (DOCTYP010) has a value of 'SWDOC'.

a. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 010 assumes the role
software-support-document-source-entity-identifier (SSDSRC185).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK

B-73
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SSDSRC185 software-support-document-source-entity-identifier 0033 FK

SDOCSB185 software-support-document-subsidiary-type-code 0107 M

B.5.4.29. Table 186, Software support document revisions (SWDOCREV). This table is a subtype of Table
GENERIC-DOCREV/011 and contains the revision history for software support documents. Due to parallel
categorization, this table is a de facto child of Table SWDOC/185.

a. Attribute document-identifier (DOCIDN010) inherited from Table 011 assumes the role software-support-
document-alphanumeric-identifier (SSDIDN186).

b. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 011 assumes the role
software-support-document-generic-revision-identifier (SSDREV186).

c. Because this table is a de facto child of Table 185, document-source-entity-identifier (SRCIDN010)

inherited from Table 011 is really a software-support-document-source-entity-identifier (SSDSRC185)
existing in Table 185. Therefore, SRCIDN010 assumes the identity SSDSRC185.

d. Attribute document-type-code (DOCTYP010) inherited from Table 011 assumes the role software-
support-document-type-code (SSDTYP186).

Code Data Element Title DED Key

B.5.4.30. Table 187, Correlation of software support documentation revisions to the software versions they
support (SWDOCREV-SWVER). This table correlates software versions with the specific software support
document revision(s) which support it.

Code Data Element Title DED Key

SSDIDN186 software-support-document-alphanumeric-identifier 0122 FK
SSDREV186 software-support-document-generic-revision-identifier 0243 FK
SSDSRC185 software-support-document-source-entity-identifier 0033 FK
SSDTYP186 software-support-document-type-code 0004 FK
SWIDEN170 software-product-generic-identifier 0060 FK
SWSORC170 software-product-source-entity-identifier 0033 FK

B.5.4.31. Tables 188 and 189. Reserved.

B.5.4.32. Table 190, USAF Computer Program Identification Numbers (CPINs) (CPIN). This table contains
the USAF CPINs assigned by OC-ALC/MMEDUE to Embedded Computer Software (ECS) and related software as
required by USAF TO 00-15-16.

B-74
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

CPINNO190 software-product-united-states-air-force--assigned- 0237 K
designation-identifier

B.5.4.33. Table 191, CPINs with a software type of 'C' or 'D' (CPIN-TYPECD). This table is a subtype of Table
190 containing the subset of software-product-united-states-air-force--assigned-designation-identifier
(CPINNO190) which consists of those software-product-united-states-air-force--assigned-designation-identifiers
with a value of 'C' or 'D' for the software-product-united-states-air-force--assigned-type-code. (The software-
product-united-states-air-force--assigned-type-code is one of the data elements which comprise the software-
product-united-states-air-force--assigned-designation-identifier.)

Code Data Element Title DED Key

CPINNO190 software-product-united-states-air-force--assigned- 0237 FK
designation-identifier

B.5.4.34. Table 192, CPINs with a software type code of 'F', 'S', 'T', or 'U' (CPIN-TYPEFSTU). This table is a
subtype of Table 190 containing the subset of software-product-united-states-air-force--assigned-designation-
identifier (CPINNO190) which consists of those software-product-united-states-air-force--assigned-designation-
identifiers with a value of 'F', 'S', 'T', or 'U' for the software-product-united-states-air-force--assigned-type-code.
(The software-product-united-states-air-force--assigned-type-code is one of the data elements which comprise the
software-product-united-states-air-force--assigned-designation-identifier.) This table has two subtypes (applicable
to software ['A'] and applicable to software engineering documentation package ['D']). Only the table which is
applicable to software is shown because the software engineering documentation package CPIN is unnecessary to
CM.

Code Data Element Title DED Key

CPINNO190 software-product-united-states-air-force--assigned- 0237 FK
designation-identifier

B.5.4.35. Table 193, Combination and Master CPINs (COMBO-CPIN). This table correlates the combination
and master CPINs with the software (or software engineering data package) CPINs which they combine.

a. Attribute software-product-united-states-air-force--assigned-designation-identifier (CPINNO190)

inherited from Table 191 assumes the role combination-software-product-united-states-air-force--
assigned-designation-identifier (COMBNO193).

b. Attribute software-product-united-states-air-force--assigned-designation-identifier (CPINNO190)

inherited from Table 192 assumes the role component-software-product-united-states-air-force--assigned-
designation-identifier (COMPNO193).

Code Data Element Title DED Key

COMBNO193 combination-software-product-united-states-air-force-- 0237 FK
assigned-designation-identifier
COMPNO193 component-software-product-united-states-air-force-- 0237 FK
assigned-designation-identifier

B-75
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.4.36. Table 194, CPINs assigned to Software (CPIN-APPA). This table is a subtype of Table 192 which
contains the subset of software-product-united-states-air-force--assigned-designation-identifier which is applicable
to software (rather than software engineering documentation packages). The instances in this table all have a
value of 'A' for the software-product-united-states-air-force--assigned-applicability-code. (The software-product-
united-states-air-force--assigned-applicability-code is one of the data elements which is part of the software-
product-united-states-air-force--assigned-designation-identifier.)

Code Data Element Title DED Key

CPINNO190 software-product-united-states-air-force--assigned- 0237 FK
designation-identifier

SWIDEN170 software-product-generic-identifier 0060 FK

SWSORC170 software-product-source-entity-identifier 0033 FK
MEDTYP194 software-product-storage-medium-type-name 0238 M

B.5.4.37. Tables 195 through 199. Reserved.

B-76
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.5. Parts and materials. Entity tables numbered in the range of 200 through 249 contain the identification of
parts and materials, and the effective contents of parts lists (including both integral and separate parts lists), and
the current configuration of products. This section addresses a generic part number which includes parts defined by
engineering drawings (CAGE and part number), military or industry standards (part numbers defined by an
organization acronym) and company internal practices (part numbers defined by companies without a CAGE
code). Similarly, this section addresses a generic material (for materials not identified by a part number) which
includes parts defined by program-unique specifications, military or industry standards, and company internal
practices (material names). The material section is broadly designed to include parts which are identified by
parameters instead of a part number (for example: No. 8, 3/4 in., 24UNC, Hex-head bolt). Both of these sections
also address the concept of substitute (due to temporary non-availability) and replacement (due to permanent
supersession) parts/materials. This section also includes an effective parts list (parts list by drawing revision and
parts list by change effectivity) and a current configuration structure (parts list by part and serial/lot number). The
relationships between these various entity tables are depicted in Figures 04PIN1 through 04PIN8.

Other part/material identification can be found in the applicable section of this appendix. (See B.5.8.4 for
substitute and replacement National Stock Numbers, and B.5.22.5 for company stock numbers.)

B.5.5.1. Table 200, Generic identification of materials (GENERIC-MATID). This table is the generic super-type
of material identification which includes the identification of all materials and parts which are identified by
parameters, classes, types, etc. It specifically excludes materials identified by part number. It has three subtypes:
STD-MATID/201, CAGE-MATID/205, and COM-MATID/915.

a. For each value of product--tracking-base--identifier (BASNUM500) in this table, there must be one (and
only one) instance in this table where the value of BASNUM500 is the same as the value of the
concatenation of design-enterprise-identifier (DISENT200), material-product-generic-identifier
(MATGID200), and material-product-identifier (MATIDN200).

b. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role design-enterprise-
identifier (DESENT200).

c. Attribute part-product-name (PARNAM209) inherited from Table 209 assumes the role material-product-
name (MATNAM200).

Code Data Element Title DED Key

MATGID200 material-product-generic-identifier 0092 K
MATIDN200 material-product-identifier 0038 K
DESENT200 design-enterprise-identifier 0052 FK

BASNUM500 product--tracking-base--identifier 0056 FK, O

MATNAM200 material-product-name 0191 FK, O
NSNNUM345 product-national-stock-identifier 0049 FK, O
HAZMAT200 materiel-item-supply-hazardous-material-code 0078 M
METALS200 materiel-item-supply-precious-metals-indicator-code 0093 M
RELDAT200 material-product-design-release-date 0082
SHLFCD200 supply-item-control-shelf-life-code 0094
SRVCCD200 product-service-life-period-unit-code 0232
SRVCQY200 product-service-life-period-quantity 0086
STATIC200 materiel-item-supply-electrostatic-discharge- 0074 M
electromagnetic-interference-code

B-77
GENERIC-MATID / 200 (see 2DWG4, 5PIN3, 5PIN4, 5PIN5, 5PIN7, 7NOR5, 10RFD3, 13TRK1, 13TRK3, 24COM3)
ENTERPRISE / 002 (from 1GEN1)
design-enterprise-identifier.enterprise-identifier (FK)
enterprise-identifier may define material-generic-identifier may have a substitute of
enterprise-identification-type-code material-identification
can be used as
P product--tracking-base--identifier (FK) a substitute for
nsn (FK)
is assigned to material-name.part-name (FK)
PART-NAME / 209 (from 9NSN1)
may be the P
part-name
national stock
number for MAT-SUBMAT / 206
replaced-material-enterprise-identifier.design-enterprise-identifier (FK)
replaced-material-generic-identifier.material-generic-identifier (FK)
NSN / 325 (from PCTSS) replaced-material-identification.material-identification (FK)
nsn substitute-material-enterprise-identifier.design-enterprise-identifier (FK)
substitute-material-generic-identifier.material-generic-identifier (FK)
substitute-material-identification.material-identification (FK)

BASE-MAT / 506 (from 13TRK1) is the common

product--tracking-base--identifier base number for
enterprise-identification-type-code

B-78
APPENDIX B

ORGSTDDOC-DEFMAT / 421 (from 11STDS4)

MIL-STD-2549

design-organization-code
material-document-identifier ORG CAG

defines
COM
P
STD-MATID / 201 (see 11STDS4, 13TRK1) CAGE-MATID / 205 (de facto child of 003) (see 3SPEC1, 11STDS5)
design-organization-code.(design-enterprise-identifier,design-organization-code) (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

design-cage-code.design-enterprise-identifier (FK)
material-document-identifier.(material-generic-identifier,material-document-identifier) (FK) material-generic-identifier (FK)
material-identification (FK) material-identification (FK)

COM-MATID / 921 (from 24COM3)

design-company-name.design-enterprise-identifier (FK)
FIGURE 05PIN1 material-generic-identifier (FK)
GENERIC MATERIAL DEFINITION material-identification (FK)
ENTERPRISE / 002 (from 1GEN1)
GENERIC-PIN / 210 (see 2DWG5,3SPEC2,5PIN3,5PIN4,5PIN5,5PIN6,7NOR5,10RFD3,
enterprise-identifier may define 13TRK1, 13TRK3, 14TM5, 24COM2)
design-enterprise-identifier.enterprise-identifier (FK)
enterprise-identification-type-code part-identifier

P product--tracking-base--identifier (FK)
nsn (FK)
is assigned to
part-name (FK)
PART-NAME / 209 (from 9NSN1)
part-name may be the P may have a substitute of
national stock
number for can be used as a substitute for

NSN / 325 (from PCTSS) PIN-SUBPIN / 216

nsn replaced-part-enterprise-identifier.design-enterprise-identifier (FK)
replaced-part-identifier.part-identifier (FK)
substitute-part-enterprise-identifier.design-enterprise-identifier (FK)
substitute-part-identifier.part-identifier (FK)
BASE-PIN / 505 (from 13TRK1) is the common
product--tracking-base--identifier base number for

enterprise-identification-type-code

B-79
ORG COM
APPENDIX B

ORGSTDDOC-DEFPIN / 420 (from 11STDS4)

MIL-STD-2549

design-organization-code CAG
document-alphanumeric-identifier
document-type-code (see 2DWG2,3SPEC1,6ECP3,11STDS5)
CAGEPIN / 212 (de facto child of 003)
design-cage-code.design-enterprise-identifier (FK)
part-identifier (FK)
defines document-type-code
P
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

STDPIN / 211 (see 11STDS4) COMPIN / 920 (from 24COM2)

design-organization-code.(design-enterprise-identifier,design-organization-code) (FK) design-company-name.design-enterprise-identifier (FK)
part-identifier (FK) part-identifier (FK)
document-type-code (FK)
document-alphanumeric-identifier (FK)

FIGURE 05PIN2
GENERIC PART NUMBER DEFINITION
MAT-SUBPIN / 207
replaced-material-enterprise-identifier.design-enterprise-identifier (FK)
replaced-material-generic-identifier.material-generic-identifier (FK)
replaced-material-identification.material-identification (FK)
may have a substitute-part-enterprise-identifier.design-enterprise-identifier (FK) can be used as
GENERIC-MATID / 200 (from 5PIN1) substitute of substitute-part-identifier.part-identifier (FK) a substitute for
GENERIC-PIN / 210 (from 5PIN2)
design-enterprise-identifier
design-enterprise-identifier
material-generic-identifier
part-identifier
material-identification

may have a may have

can be used as electronic
substitute of
a substitute for
PIN-SUBMAT / 217
replaced-part-enterprise-identifier.design-enterprise-identifier (FK)
replaced-part-identifier.part-identifier (FK) PARTMODEL / 230 (de facto child of 010)
substitute-material-enterprise-identifier.design-enterprise-identifier (FK) design-enterprise-identifier (FK)
substitute-material-generic-identifier.material-generic-identifier (FK) part-identifier (FK)
substitute-material-identification.material-identification (FK) SW

has iterations
ASSYMODEL / 233 P

B-80
assembly-enterprise-identifier.design-enterprise-identifier (FK) MODELREV / 231 (de facto child of 011)
assembled-part-identifier.part-identifier (FK)
design-enterprise-identifier (FK)
APPENDIX B

assembly-model-generic-revision.part-model-generic-revision (FK) may be an assembly model of

MIL-STD-2549

part-identifier (FK)
component-enterprise-identifier.design-enterprise-identifier (FK)
SW (FK)
component-part-identifier.part-identifier (FK) may be a component model of part-model-generic-revision
component-part-model-generic-revision.part-model-generic-revision (FK)
SW (FK)

is filed as

MODEL-FILE / 232
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

design-enterprise-identifier (FK)
FILE / 900 (from 23FILE1) part-identifier (FK)
file-originator SW (FK)
file-originator-office-address part-model-generic-revision (FK)
file-identifier file-originator (FK)
may be a
file-creation-date file-originator-office-address (FK)
file-creation-time file-identifier (FK)
file-creation-date (FK)
file-creation-time (FK)
FIGURE 05PIN3
GENERIC PART/MATERIAL SUBSTITUTIONS
DWG-NOTE / 080 (from 2DWG4) FIND-NOTE / 226
DWGREV-PIN / 054 (from 2DWG2) design-cage-code design-cage-code (FK)
design-cage-code drawing-alphanumeric-identifier may be called out by assembly-drawing-alphanumeric-identifier.drawing-alphanumeric-identifier (FK)
part-identifier document-type-code document-type-code (FK) may refer to
document-revision document-revision document-revision (FK)
drawing-note-number DWGREV / 051 (from 2DWG1) drawing-note-number (FK)
drawing-alphanumeric-identifier
design-cage-code find-identifier (FK)
document-type-code
drawing-alphanumeric-identifier
document-type-code
may be assembled document-revision may have
or made from Assertions: (1) The relationship of 051 to 219 is 1:P if the value of
may have separate-parts-list-code is 'I' (integral parts list) and the value of
parts/materials list document-type-code is 'DWG'.
composed of (2) The relationship of 051 to 219 is 1:P if the value of separate-parts-
list-code is 'S' (separate parts list) and the document-type-code is 'PL'.
(3) The relationship of 051 to 219 is 1:0 in all other cases.
DASH-PLITEM / 225 DWGREV-PLITEM / 224
identifies the primary DWGREV-FIND / 219
design-cage-code (FK) may be design-cage-code (FK)
or preferred part design-cage-code (FK)
assembly-drawing-alphanumeric-identifier (FK) assembled assembly-drawing-alphanumeric-identifier.drawing-alphanumeric-identifier (FK)
drawing-alphanumeric-identifier (FK)
part-identifier (FK) or made document-revision (FK) Z document-revision (FK)
document-revision (FK) into find-identifier (FK)
may identify an find-identifier
find-identifier (FK) pl-entry-sequence-number
pl-entry-sequence-number (FK) alternate part document-type-code (FK)
document-type-code (FK)
component-quantity component-type-code
unit-of-measure primary-alternate-flag may have assembly
location designated by

component-type-code REFDES / 208

COMPPIN / 220
design-cage-code (FK) ci-nomenclature (FK)
assembly-drawing-alphanumeric-identifier (FK) P CINOMEN / 690 (from 19CI1) reference-designator (AK1)
may have component

B-81
document-revision (FK) ci-nomenclature locations designated by design-cage-code (FK) (AK1)
find-identifier (FK) drawing-alphanumeric-identifier (FK) (AK1)
pl-entry-sequence-number (FK)
APPENDIX B

document-revision (FK) (AK1)

MIL-STD-2549

design-enterprise-identifier (FK) S find-identifier (FK) (AK1)

M
part-identifier (FK)
D

COMPMAT / 221 COMPSW / 222

COMPDOC / 223
design-cage-code (FK) design-cage-code (FK)
design-cage-code (FK)
assembly-drawing-alphanumeric-identifier (FK) assembly-drawing-alphanumeric-identifier (FK) may have
assembly-drawing-alphanumeric-identifier (FK)
document-revision (FK) document-revision (FK)
document-revision (FK)
may be called out by find-identifier (FK) find-identifier (FK)
find-identifier (FK)
pl-entry-sequence-number (FK) pl-entry-sequence-number (FK)
pl-entry-sequence-number (FK)
design-enterprise-identifier (FK) software-source-identifier (FK)
document-source-entity-identifier (FK)
material-generic-identifier (FK) software-generic-identifier (FK)
document-identifier (FK)
material-identification (FK) document-type-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

SPECIAL-ITEM / 227
GENERIC-PIN / 210 (from 5PIN2) may be called out by drawing-special-condition-note
may be called out by may be called out by
design-enterprise-identifier design-cage-code (FK)
part-identifier drawing-alphanumeric-identifier (FK)
GENERIC-MATID / 200 (from 5PIN1) GENERIC-DOCUMENT / 010 (from 1GEN2) document-revision (FK)
GENERIC-SWPROD / 170 (from 4SW3)
design-enterprise-identifier document-source-entity-identifier find-identifier (FK)
document-identifier software-source-identifier
material-generic-identifier drawing-special-condition-code
document-type-code software-generic-identifier
material-identification
FIGURE 05PIN4
ENGINEERING PARTS LIST STRUCTURE
(Part 1 OF 2)
DWGPIN / 053 (from 2DWG2) ASSY-COMPPIN / 234
design-cage-code design-cage-code (FK) GENERIC-PIN / 210 (from 5PIN02)
part-identifier may be assembled assembled-product-identifier.part-identifier (FK) may be assembled design-enterprise-identifier
or made from design-enterprise-identifier (FK) or made into part-identifier
component-part-identifier.part-identifier (FK)

GENERIC-SWPROD / 170 (from 4SW3)

software-source-identifier GENERIC-MATID / 200 (from 5PIN1)
software-generic-identifier may have effectivity
design-enterprise-identifier specified as
material-generic-identifier
material-identification
may be assembled from
or programmed with
COMPPIN-EFF / 237 (see 6ECP4, 10RFD4)
may be blown into, may be assembled or made into design-cage-code (FK)
or installed in may be assembled or made from assembled-product-identifier (FK)
manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK)
ASSY-COMPMAT / 235 starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
design-enterprise-identifier (FK)
design-cage-code (FK) component-part-identifier (FK)
part-identifier (FK)
ASSY-COMPSW / 236 product--tracking-base--identifier (FK)
design-enterprise-identifier (FK)
assembled-product-cage-code.design-cage-code (FK) material-generic-identifier (FK) ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
part-identifier (FK) material-identification (FK)
software-source-identifier (FK)
software-generic-identifier (FK) may be starting effectivity for

B-82
may have effectivity specified as may be ending effectivity for
APPENDIX B
MIL-STD-2549

BASETRACK / 515 (from 13TRK2)

COMPMAT-EFF / 238 (see 6ECP4, 10RFD4) product--tracking-base--identifier
design-cage-code (FK) may be the starting effectivity for manufacturer-cage-code
part-identifier (FK) product-effectivity-tracking-type
manufacturer-cage-code (FK) product-tracking-identifier
product-effectivity-tracking-type (FK) may be ending effectivity for
starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
design-enterprise-identifier (FK)
may be starting effectivity for use of
material-generic-identifier (FK)
material-identification (FK) may be ending effectivity for
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

product--tracking-base--identifier (FK)
ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
COMPSW-EFF / 239 (see 6ECP4, 10RFD4)
assembled-product-cage-code (FK)
part-identifier (FK)
manufacturer-cage-code (FK)
may have
product-effectivity-tracking-type (FK)
effectivity
starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
specified as
software-source-identifier (FK)
software-generic-identifier (FK)

FIGURE 05PIN5 product--tracking-base--identifier (FK)

ENGINEERING PARTS LIST STRUCTURE (Part 2 OF 2) ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
GENERIC-PIN / 210 (from 5PIN2) BASETRACK / 515 (from 13TRK2)
design-enterprise-identifier product-tracking-base-identifier
part-identifier manufacturer-cage-code
product-effectivity-tracking-type
product-tracking-identifier

may be identified by
may identify

TRACK-PIN / 240 (de facto supertype of 521,522,523 & 529) (see 5PIN7)
design-enterprise-identifier (FK)
part-identifier (FK) may consist of
manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK) may be installed in
product-tracking-identifier (FK)
product-tracking-base-identifier (FK)

GENERIC-SWPROD / 170 (from 4SW3) ASCONFIG-PINPIN / 242

B-83
software-source-identifier assembly-design-enterprise-identifier.design-enterprise-identifier (FK)
software-generic-identifier assembled-product-identifier.part-identifier (FK)
APPENDIX B
MIL-STD-2549

assembly-manufacturer-cage-code.manufacturer-cage-code (FK)
assembly-tracking-identifier.(product-tracking-identifier,product-effectivity-tracking-type) (FK)
assembly-status-code
may be loaded into may incorporate assembly-status-date
assembly-status-time
component-part-enterprise-identifier.design-enterprise-identifier (FK)
ASCONFIG-PINSW / 245 component-part-identifier.part-identifier (FK)
component-part-manufacturer-cage-code.manufacturer-cage-code (FK)
design-enterprise-identifier (FK)
component-part-tracking-identifier.(product-tracking-identifier,product-effectivity-tracking-type) (FK)
part-identifier (FK)
manufacturer-cage-code (FK) component-quantity
product-effectivity-tracking-type (FK) unit-of-measure
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

product-tracking-identifier (FK)
assembly-status-code
assembly-status-date
assembly-status-time
software-source-identifier (FK)
software-generic-identifier (FK)

FIGURE 05PIN6
AS-BUILT/MODIFIED/RETROFIT/MAINTAINED (Part 1 OF 3)
BASETRACK / 515 (from 13TRK2) GENERIC-MATID / 200 (from 5PIN1)
product-tracking-base-identifier design-enterprise-identifier
manufacturer-cage-code TRACK-MAT / 241 (de facto supertype of 526 & 530) (see 5PIN8) material-generic-identifier
product-effectivity-tracking-type design-enterprise-identifier (FK) material-identification
product-tracking-identifier material-generic-identifier (FK)
material-identification (FK)
manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK)
may identify product-tracking-identifier (FK) may be identified by

may identify product-tracking-base-identifier (FK)

may be installed in
TRACK-PIN / 240 (from 5PIN6)
design-enterprise-identifier
part-identifier
ASCONFIG-PINMAT / 243
manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK) assembly-design-enterprise-identifier.design-enterprise-identifier (FK)
product-tracking-identifier (FK) assembled-product-identifier.part-identifier (FK)

B-84
assembly-manufacturer-cage-code.manufacturer-cage-code (FK)
product-tracking-base-identifier (FK) assembly-tracking-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
assembly-status-code
APPENDIX B
MIL-STD-2549

assembly-status-date
may consist of assembly-status-time
component-material-enterprise-identifier.design-enterprise-identifier (FK)
component-material-generic-identifier.material-generic-identifier (FK)
component-material-identification.material-identification (FK)
component-material-manufacturer-cage-code.manufacturer-cage-code (FK)
component-material-tracking-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
component-quantity
unit-of-measure
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 05PIN7
AS-BUILT/MODIFIED/RETROFIT/MAINTAINED (Part 2 OF 3)
TRACK-MAT / 241 (from 5PIN7)
design-enterprise-identifier
material-generic-identifier
material-identification
manufacturer-cage-code
product-effectivity-tracking-type
product-tracking-identifier
product-tracking-base-identifier

may incorporate
may be a component of

ASCONFIG-MATMAT / 244
assembly-design-enterprise-identifier.design-enterprise-identifier (FK)
assembled-material-generic-identifier.material-generic-identifier (FK)

B-85
assembled-material-identification.material-identification (FK)
assembly-manufacturer-cage-code.manufacturer-cage-code (FK)
APPENDIX B
MIL-STD-2549

assembly-product-tracking-identifier.(product-tracking-identifier,product-effectivity-tracking-type) (FK)
assembly-status-code
assembly-status-date
assembly-status-time
component-material-enterprise-identifier.design-enterprise-identifier (FK)
component-material-generic-identifier.material-generic-identifier (FK)
component-material-identification.material-identification (FK)
component-material-manufacturer-cage-code.manufacturer-cage-code (FK)
component-material-tracking-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

component-quantity
unit-of-measure

FIGURE 05PIN8
AS-BUILT/MODIFIED/RETROFIT/MAINTAINED (Part 3 OF 3)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.5.2. Table 201, Materials defined by specification or standard (STD-MATID). This table is a subtype of Table
GENERIC-MATID/200 containing the subset of generic material identifiers which is limited to those materials
and parts which are identified by a numbered specification or standard issued by a standardization organization
(such as ISO, NATO, DOD, etc.).

a. Due to parallel categorization, this table is a de facto child of Table ORGANIZATION/004; therefore, the
value of design-enterprise-acronym-identification-code (DESORG421) must exist as an organization-
identifier (ORGIDN004) in Table ORGANIZATION/004.

b. Attribute design-enterprise-identifier (DESENT200) inherited from Table 200 and design-enterprise-

acronym-identification-code (DESORG421) inherited from Table 421 must both have the same value.
Therefore they merge and assume the identity design-enterprise-acronym-identification-code
(DESORG421).

c. Attribute material-product-generic-identifier (MATGID200) inherited from Table 200 and material-

document-identifier (MATDOC421) inherited from Table 421 must both have the same value. Therefore
they merge and assume the identity material-document-identifier (MATDOC421).

Code Data Element Title DED Key

DESORG421 design-enterprise-acronym-identification-code 0002 FK
MATDOC421 material-document-identifier 0192 FK
MATIDN200 material-product-identifier 0038 FK

B.5.5.3. Tables 202 through 204. Reserved.

B.5.5.4. Table 205, Specification-defined material identification (CAGE-MATID). This table is a subtype of Table
GENERIC-MATID/200 containing the subset of generic material identifiers which is limited to those materials
and parts identified by a program-unique specification or standardization document which is identified by a
CAGE code and a number. Due to parallel categorization, this table is a de facto child of Table CAGE/003.

a. Because this table is a de facto child of Table 003, the value of design-enterprise-identifier (DESENT200)
inherited from Table 200 must exist as a enterprise-defense-logistics--assigned-identification-code
(CAGNUM003) in Table 003. DESENT200 assumes the role design-enterprise-defense-logistics--
assigned-identification-code (DESCAG205).

Code Data Element Title DED Key

DESCAG205 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK

B.5.5.5. Table 206, Substitute materials (for materials) (MAT-SUBMAT). This table identifies materials and parts
which are not identified by a part number and which have been identified by competent authority as suitable
substitute parts/materials or permanent replacement parts/materials for parts/materials which have either been
permanently discontinued (and therefore, superseded) or which are temporarily out-of-stock.

B-86
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Attribute design-enterprise-identifier (DESENT200) inherited from Table 200 assumes the role replaced-
material-product-design-enterprise-identifier (RMENID206).

b. Attribute material-product-generic-identifier (MATGID200) inherited from Table 200 assumes the role
replaced-material-product-generic-identifier (RMGNID206).

c. Attribute material-product-identifier (MATIDN200) inherited from Table 200 assumes the role replaced-
material-product-identifier (RMMTID206).

d. Attribute design-enterprise-identifier (DESENT200) inherited from Table 200 assumes the role substitute-
material-product-design-enterprise-identifier (SMENID206).

e. Attribute material-product-generic-identifier (MATGID200) inherited from Table 200 assumes the role
substitute-material-product-generic-identifier (SMGNID206).

f. Attribute material-product-identifier (MATIDN200) inherited from Table 200 assumes the role substitute-
material-product-identifier (SMMTID206).

Code Data Element Title DED Key

RMENID206 replaced-material-product-design-enterprise-identifier 0052 FK
RMGNID206 replaced-material-product-generic-identifier 0092 FK
RMMTID206 replaced-material-product-identifier 0038 FK
SMENID206 substitute-material-product-design-enterprise-identifier 0052 FK
SMGNID206 substitute-material-product-generic-identifier 0092 FK
SMMTID206 substitute-material-product-identifier 0038 FK

ONEWAY206 product-interchangeability-code 0063 M

REPTYP206 product-replacement-type-code 0106 M

B.5.5.6. Table 207, Substitute materials defined by part number (for materials not defined by part number) (MAT-
SUBPIN). This table identifies part numbers which have been identified by competent authority as suitable
substitute part numbers, or permanent replacement part numbers for parts/materials (not identified by part number)
which have either been permanently discontinued (and therefore, superseded) or which are temporarily out-of-
stock.

a. Attribute design-enterprise-identifier (DESENT200) inherited from Table 200 assumes the role replaced-
material-product-design-enterprise-identifier (RMENID207).

b. Attribute material-product-generic-identifier (MATGID200) inherited from Table 200 assumes the role
replaced-material-product-generic-identifier (RMGNID207).

c. Attribute material-product-identifier (MATIDN200) inherited from Table 200 assumes the role replaced-
material-product-identifier (RMMTID207).

d. Attribute part-product-identifier (PARNUM210) inherited from Table 210 assumes the role substitute-
part-product-identifier (SPARNO207).

B-87
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

e. Attribute design-enterprise-identifier (DESENT210) inherited from Table 210 assumes the role substitute-
part-product-design-enterprise-identifier (SPENID207).

Code Data Element Title DED Key

RMENID207 replaced-material-product-design-enterprise-identifier 0052 FK
RMGNID207 replaced-material-product-generic-identifier 0092 FK
RMMTID207 replaced-material-product-identifier 0038 FK
SPARNO207 substitute-part-product-identifier 0024 FK
SPENID207 substitute-part-product-design-enterprise-identifier 0052 FK

ONEWAY207 product-interchangeability-code 0063 M

REPTYP207 product-replacement-type-code 0106 M

B.5.5.7. Table 208, Correlation of reference designators to assembly find numbers (REFDES). This table
correlates the reference designator for a specific CI with the parts-list call-out for the component denoted by the
reference designator.

Code Data Element Title DED Key

REFDES208 place-reference-designator-identifier 0055 K, AK1
CINOMN690 configuration-item-product-nomenclature-text 0047 FK

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK, AK1

code
DOCNUM020 document-alphanumeric-identifier 0003 FK, AK1
DOCREV051 document-alphanumeric-revision-identifier 0009 FK, AK1
FINDID219 parts-list-document-item-identifier 0027 FK, AK1

B.5.5.8. Table 209, Part name (PART-NAME). This table contains the valid part names used by cataloging.

Code Data Element Title DED Key

PARNAM209 part-product-name 0113 K

B.5.5.9. Table 210, Generic identification of parts (GENERIC-PIN). This table is the generic super-type of part
numbers. It specifically excludes materials/parts which are identified by parameter instead of by part number. It
has three subcategories: STDPIN / 211, CAGEPIN/212, and COMPIN/920.

b. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role design-enterprise-
identifier (DESENT210).

B-88
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

PARNUM210 part-product-identifier 0024 K
DESENT210 design-enterprise-identifier 0052 FK

BASNUM500 product--tracking-base--identifier 0056 FK, O

NSNNUM345 product-national-stock-identifier 0049 FK, O
PARNAM209 part-product-name 0113 FK, O
HAZMAT210 materiel-item-supply-hazardous-material-code 0078 M
METALS210 materiel-item-supply-precious-metals-indicator-code 0093 M
PARWGT210 part-product-unit-weight 0114
RELDAT210 part-product-release-date 0082
SHLFCD210 supply-item-control-shelf-life-code 0094
SRVCCD210 product-service-life-period-unit-code 0232
SRVCQY210 product-service-life-period-quantity 0086
STATIC210 materiel-item-supply-electrostatic-discharge- 0074 M
electromagnetic-interference-code
WGTCOD210 part-product-bulk-measurement-unit-code 0054

B.5.5.10. Table 211, Part numbers defined by standardization organizations (STDPIN). This table is a subtype
of Table GENERIC-PIN/210 containing the subset of generic part numbers which are those part numbers identified
by a numbered standardization document (instead of by a drawing) that is issued by a standards-issuing
organization identified by an acronym; this includes U.S., foreign, and international military, industry and
professional organizations.

a. Due to parallel categorization, this table is a de facto child of Table ORGANIZATION/004; therefore the
value of design-enterprise-acronym-identification-code (DESORG420) must exist as an organization-
identifier (ORGIDN004) in Table 004.

b. Attribute design-enterprise-identifier (DESENT210) inherited from Table 210 and design-enterprise-

acronym-identification-code (DESORG420) inherited from Table 420 must both have the same value.
Therefore they merge and assume the identity design-enterprise-acronym-identification-code
(DESORG420).

Code Data Element Title DED Key

DESORG420 design-enterprise-acronym-identification-code 0002 FK
PARNUM210 part-product-identifier 0024 FK

DOCNUM020 document-alphanumeric-identifier 0003 FK

DOCTYP010 document-type-code 0004 FK

B.5.5.11. Table 212, Part numbers defined in conjunction with a CAGE code (CAGEPIN). This table is a
subset of Table GENERIC-PIN/210 containing those part numbers which are identified by a CAGE (or NSCM)
code and part number. This table has three subtypes: DWGPIN/053 (shown in Figure 2DWG2), PSPECPIN/104
(shown in Figure 3SPEC1), and CAGESTDDOC-PIN/436 (shown in Figure 11STDS4).

B-89
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Due to parallel categorization, this table is a de facto child of Table CAGE/003.

b. Because this table is a de facto child of Table 003, the value of design-enterprise-identifier (DESENT210)
inherited from Table 210 must exist as a enterprise-defense-logistics--assigned-identification-code
(CAGNUM003) in Table 003. DESENT210 assumes the role design-enterprise-defense-logistics--
assigned-identification-code (DESCAG212).

Code Data Element Title DED Key

DESCAG212 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
PARNUM210 part-product-identifier 0024 FK

DOCTYP212 document-type-code 0004 M

B.5.5.12. Tables 213 through 215. Reserved.

B.5.5.13. Table 216, Substitute part numbers (for part numbers) (PIN-SUBPIN). This table identifies part
numbers which have been identified by competent authority as suitable substitute part numbers, or permanent
replacement part numbers for part numbers which have either been permanently discontinued (and, therefore,
superseded) or which are temporarily out-of-stock.

a. Attribute design-enterprise-identifier (DESENT210) inherited from Table 210 assumes the role replaced-
part-product-design-enterprise-identifier (RENTID216).

b. Attribute part-product-identifier (PARNUM210) inherited from Table 210 assumes the role replaced-part-
product-identifier (RPARNO216).

c. Attribute design-enterprise-identifier (DESENT210) inherited from Table 210 assumes the role substitute-
part-product-design-enterprise-identifier (SENTID216).

d. Attribute part-product-identifier (PARNUM210) inherited from Table 210 assumes the role substitute-
part-product-identifier (SPARNO216).

Code Data Element Title DED Key

RENTID216 replaced-part-product-design-enterprise-identifier 0052 FK
RPARNO216 replaced-part-product-identifier 0024 FK
SENTID216 substitute-part-product-design-enterprise-identifier 0052 FK
SPARNO216 substitute-part-product-identifier 0024 FK

ONEWAY216 product-interchangeability-code 0063 M

REPTYP216 product-replacement-type-code 0106 M

B.5.5.14. Table 217, Substitute material (for material identified by a part number) (PIN-SUBMAT). This table
identifies parts/material (not identified by part number) which have been identified by competent authority as
suitable substitute parts/materials, or permanent replacement parts/materials for part numbers which have either
been permanently discontinued (and, therefore, superseded) or which are temporarily out-of-stock.

B-90
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Attribute design-enterprise-identifier (DESENT210) inherited from Table 210 assumes the role replaced-
part-product-design-enterprise-identifier (RENTID217).

b. Attribute part-product-identifier (PARNUM210) inherited from Table 210 assumes the role replaced-part-
product-identifier (RPARNO217).

c. Attribute design-enterprise-identifier (DESENT200) inherited from Table 200 assumes the role substitute-
material-product-design-enterprise-identifier (SENTID217).

d. Attribute material-product-generic-identifier (MATGID200) inherited from Table 200 assumes the role
substitute-material-product-generic-identifier (SMGNID217).

e. Attribute material-product-identifier (MATIDN200) inherited from Table 200 assumes the role substitute-
material-product-identifier (SMMTID217).

Code Data Element Title DED Key

RENTID217 replaced-part-product-design-enterprise-identifier 0052 FK
RPARNO217 replaced-part-product-identifier 0024 FK
SENTID217 substitute-material-product-design-enterprise-identifier 0052 FK
SMGNID217 substitute-material-product-generic-identifier 0092 FK
SMMTID217 substitute-material-product-identifier 0038 FK

ONEWAY217 product-interchangeability-code 0063 M

REPTYP217 product-replacement-type-code 0106 M

B.5.5.15. Table 218. Reserved.

B.5.5.16. Table 219, Parts list finds by drawing revision (DWGREV-FIND). This table is the correlation of
drawing finds (parts list items) to the drawing revision(s) on which they appear. Find numbers are applicable only
to assembly drawings with integral parts lists or to parts list drawings. The approach taken in this system assumes
consistent parts lists5 are used on tabulated assembly drawings; the system does not support inconsistent parts lists.6
This information is correlated with the drawing revision on which it appears and the product effectivity expressed
in terms of product serial/lot number(s).

Code Data Element Title DED Key

FINDID219 parts-list-document-item-identifier 0027 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK

5
Consistent parts lists are tabulated parts lists in which a find number is associated with the same
part/material identifier(s) for all dash numbers in the tabulated parts list.
6
Inconsistent parts lists are tabulated parts lists in which the find number may be associated with a
different part/material identifier for each dash number in the tabulated parts list.

B-91
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DOCREV051 document-alphanumeric-revision-identifier 0009 FK

DOCTYP010 document-type-code 0004 FK

B.5.5.17. Table 220, Parts List entries consisting of component part numbers (COMPPIN). This table is a
subtype of the drawing-revision to parts list item correlation table (DWGREV-PLITEM/224) and includes only
those parts list entries which contain a component part number.

a. The combination of the values of enterprise-identifier (ENTIDN002) and part-product-identifier

(PARNUM210) inherited from Table 210 cannot be the same as the combination of the values of design-
enterprise-defense-logistics--assigned-identification-code (DESCAG050) and part-product-identifier
(PARNUM210) in any instance of Table 225 with which it is associated. (This enforces the rule that a
part cannot be made from itself.)

Code Data Element Title DED Key

ASSYNO224 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
FINDID219 parts-list-document-item-identifier 0027 FK
PLSEQN224 document-parts-list-entry-sequence-identifier 0259 FK

DESENT210 design-enterprise-identifier 0052 FK

PARNUM210 part-product-identifier 0024 FK

B.5.5.18. Table 221, Parts List entries consisting of component materials (COMPMAT). This table is a subtype
of the drawing-revision to parts list item correlation table (DWGREV-PLITEM/224) and includes only those parts
list entries which contain a component material not identified by a part number.

Code Data Element Title DED Key

DESENT200 design-enterprise-identifier 0052 FK

MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK

B-92
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.5.19. Table 222, Parts List entries consisting of component software (COMPSW). This table is a subtype of
the drawing-revision to parts list item correlation table (DWGREV-PLITEM/224) and includes only those parts list
entries which contain a component software identifier (which is not a part number).

Code Data Element Title DED Key

SWSORC170 software-product-source-entity-identifier 0033 FK

B.5.5.20. Table 223, Parts List entries consisting of component miscellaneous reference documents
(COMPDOC). This table is a subtype of the drawing-revision to parts list item correlation table (DWGREV-
PLITEM/224) and includes only those parts list entries which contain a component reference document identifier.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK

DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.5.21. Table 224, Parts list line items (DWGREV-PLITEM). This table is an abstract table which represents
a single parts list line entry. This information is correlated with the drawing revision on which it appears.

a. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

051 and document-alphanumeric-identifier (DOCNUM020) inherited from Table 219 must have the same
value and merge to assume the role assembly-engineering-drawing-document-alphanumeric-identifier
(ASSYNO224).

Code Data Element Title DED Key

PLSEQN224 document-parts-list-entry-sequence-identifier 0259 K
ASSYNO224 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK

B-93
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

FINDID219 parts-list-document-item-identifier 0027 FK

DOCTYP010 document-type-code 0004 FK

ALTFLG224 document-parts-list-entry-priority-indicator-code 0258 M
COMPTY224 document-parts-list-entry-component-type-code 0241 M

B.5.5.22. Table 225, Correlation of part numbers (dash numbers) to parts list line item entries. (DASH-
PLITEM). This table correlates an assembly part number to a parts list line item entry.

a. All combinations of design-enterprise-logistics--assigned-identification-code (DESCAG225) and part-

product-identifier (PARNUM210) identifying the assembly in this table and their associated combination
of design-enterprise-identifier (DESENT210) and part-product-identifier (PARNUM210) identifying the
component in Table COMPPIN/220 must form a series of directed acyclic graphs. (This enforces the rule
that a part cannot be a component of itself at any level.)

b. Fields DESCAG054 inherited from Table 054 and DESCAG050 inherited from Table 224 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG225).

Code Data Element Title DED Key

ASSYNO224 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG225 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
FINDID219 parts-list-document-item-identifier 0027 FK
PARNUM210 part-product-identifier 0024 FK
PLSEQN224 document-parts-list-entry-sequence-identifier 0259 FK

QUANTY225 assembly-part-component-quantity 0053 M

UOMCOD225 product-measurement-unit-code 0054 M

B.5.5.23. Table 226, Correlation of parts find numbers with drawing note numbers (FIND-NOTE). This table
correlates parts list find number with the engineering drawing note number(s) to which they are related.

a. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

080 and assembly-engineering-drawing-document-alphanumeric-identifier (ASSYNO224) inherited from
Table 224 must both have the same value. Therefore they merge and assume the identity assembly-
engineering-drawing-document-alphanumeric-identifier (ASSYNO224).

Code Data Element Title DED Key

B-94
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

FINDID219 parts-list-document-item-identifier 0027 FK

NOTNUM080 engineering-drawing-document-note-identifier 0251 FK

B.5.5.24. Table 227, Special Conditions, Materials and Processes on a parts list (SPECIAL-ITEM). This table
identifies the special conditions, materials and processes which are associated with a particular parts list find on a
particular engineering drawing.

Code Data Element Title DED Key

SPNOTE227 engineering-drawing-document-special-condition-code 0257 K
ASSYNO224 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
PLSEQN224 document-parts-list-entry-sequence-identifier 0259 FK

B.5.5.25. Tables 228 and 229. Reserved.

B.5.5.26. Table 230, Part model databases (PARTMODEL). A part may be designed using application
software which creates a model instead of a drawing. This table is the identification of such a model. This table is
a de facto child of GENERIC-DOC/010.

a. Because this table is a de facto child of Table 010, design-enterprise-identifier (DESENT210) inherited
from Table 210 is really a document-source-entity-identifier (SRCIDN010) existing in Table 010.

b. Because this table is a de facto child of Table 010, part-product-identifier (PARNUM210) inherited from
Table 210 is really a document-identifier (DOCIDN010) existing in Table 010.

c. Attribute document-type-code (DOCTYP010) inherited from Table 010 assumes the role software-
document-type-code (SWTYPE230).

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
PARNUM210 part-product-identifier 0024 FK
SWTYPE230 software-document-type-code 0004 FK

B.5.5.27. Table 231, Part model database revisions (MODELREV). This table contains the revision history of
part model databases. It is a de facto child of Table GENERIC-DOCREV/011.

a. Because this table is a de facto child of Table 011, design-enterprise-identifier (DESENT210) inherited
from Table 230 is really a document-source-entity-identifier (SRCIDN010) existing in Table 011.

B-95
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Because this table is a de facto child of Table 011, part-product-identifier (PARNUM210) inherited from
Table 230 is really a document-identifier (DOCIDN010) existing in Table 011.

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 011 assumes the role
part-model-database-document-generic-revision-identifier (PMODRV231).

d. Because this table is a de facto child of Table 011, software-document-type-code (SWTYPE230) inherited
from Table 230 is really a document-type-code (DOCTYP010) existing in Table 011.

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
PARNUM210 part-product-identifier 0024 FK
PMODRV231 part-model-database-document-generic-revision-identifier 0243 FK
SWTYPE230 software-document-type-code 0004 FK

B.5.5.28. Table 232, Correlation of part models to files (MODEL-FILE). This table correlates part model
revisions to the file(s) in which they are stored.

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILDAT900 electronic-document-file-creation-date 0082 FK
FILIDN900 electronic-document-file-identifier 0206 FK
FILORG900 file-originator-human-name 0069 FK
FILTIM900 electronic-document-file-creation-time 0160 FK
PARNUM210 part-product-identifier 0024 FK
PMODRV231 part-model-database-document-generic-revision-identifier 0243 FK
SWTYPE230 software-document-type-code 0004 FK

B.5.5.29. Table 233, Assembly model databases (ASSYMODEL). This table correlates assembly model
databases to the component part model databases which support them.

a. Attribute design-enterprise-identifier (DESENT210) inherited from Table 231 assumes the role assembly-
design-enterprise-identifier (ASYENT233).

b. Attribute part-product-identifier (PARNUM210) inherited from Table 231 assumes the role assembled-
part-product-identifier (ASYIDN233).

c. Attribute part-model-database-document-generic-revision-identifier (PMODRV231) inherited from Table

231 assumes the role assembly-model-database-document-generic-revision-identifier (ASYREV233).

d. Attribute design-enterprise-identifier (DESENT210) inherited from Table 231 assumes the role
component-part-design-enterprise-identifier (PINENT233).

B-96
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

e. Attribute part-product-identifier (PARNUM210) inherited from Table 231 assumes the role component-
part-product-identifier (PINIDN233).

f. Attribute part-model-database-document-generic-revision-identifier (PMODRV231) inherited from Table

231 assumes the role component-part-model-database-document-generic-revision-identifier
(PINREV233).

Code Data Element Title DED Key

ASYENT233 assembly-design-enterprise-identifier 0052 FK
ASYIDN233 assembled-part-product-identifier 0024 FK
ASYREV233 assembly-model-database-document-generic-revision- 0243 FK
identifier
PINENT233 component-part-design-enterprise-identifier 0052 FK
PINIDN233 component-part-product-identifier 0024 FK
PINREV233 component-part-model-database-document-generic-revision- 0243 FK
identifier
SWTYPE230 software-document-type-code 0004 FK

B.5.5.30. Table 234, Correlation of assembly part to component part for Bill of Materials (ASSY-COMPIN).
This table correlates assembly part numbers to component part numbers as part of the bill of materials (BOM).

a. As a validity check for all entries in this table, for each combination of values of design-enterprise-
defense-logistics--assigned-identification-code (DESCAG053) and assembled-part-product-identifier
(APARNO234), the associated combination of values of design-enterprise-identifier (DESENT210) and
component-part-product-identifier (CPARNO234) (inherited from Table 210 as ENTIDN002 and
PARNUM210, respectively) must be able to be reached through the path Table 053 -> Table 054 -> Table
225 -> Table 224 -> Table 220 -> Table 210. This ensures that the BOM does not contain any assembly-
component pairs which do not exist in the engineering design.

b. Attribute part-product-identifier (PARNUM210) inherited from Table 053 assumes the role assembled-
part-product-identifier (APARNO234).

c. Attribute part-product-identifier (PARNUM210) inherited from Table 210 assumes the role component-
part-product-identifier (CPARNO234).

Code Data Element Title DED Key

B-97
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.5.31. Table 235, Correlation of assembly part to component material for Bill of Materials (ASSY-
COMPMAT). This table correlates assembly part numbers to component materials (not identified by part
numbers) as part of the bill of materials (BOM).

a. As a validity check for all entries in this table, for each combination of values of design-enterprise-
defense-logistics--assigned-identification-code (DESCAG053) and part-product-identifier
(PARNUM210), the associated combination of values of design-enterprise-identifier (DESENT200),
material-product-generic-identifier (MATGID200), and material-product-identifier (MATIDN200)
(inherited from Table 200) must be able to be reached through the path Table 053 -> Table 054 -> Table
225 -> Table 224 -> Table 221 -> Table 200. This ensures that the BOM does not contain any assembly-
component pairs which do not exist in the engineering design.

Code Data Element Title DED Key

B.5.5.32. Table 236, Correlation of assembly part to component software for Bill of Materials (ASSY-
COMPSW). This table correlates assembly part numbers to component software as part of the bill of materials
(BOM).

a. As a validity check for all entries in this table, for each combination of values of assembly-design-
commercial-government-enterprise-identification-code (ADESCG236) and part-product-identifier
(PARNUM210) (inherited from Table 053 as DESCAG022 and PARNUM210, respectively), the
associated combination of values of software-product-originator-design-commercial-government-
enterprise-identification-code (SWCAGE236) and software-product-identifier (SWIDEN236) (inherited
from Table 151 as DESCAG022 and the concatenated string of DOCNUM020, DOCTYP010, and
DOCREV011, respectively) must be able to be reached through the path Table 053 -> Table 054 -> Table
225 -> Table 224 -> Table 222 -> Table 170. This ensures that the BOM does not contain any assembly-
component pairs which do not exist in the engineering design.

b. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG053) inherited from

Table 053 assumes the role assembled-product-design-enterprise-defense-logistics--assigned-
identification-code (ADESCG236).

Code Data Element Title DED Key

ADESCG236 assembled-product-design-enterprise-defense-logistics-- 0001 FK
assigned-identification-code
PARNUM210 part-product-identifier 0024 FK
SWIDEN170 software-product-generic-identifier 0060 FK
SWSORC170 software-product-source-entity-identifier 0033 FK

B-98
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.5.33. Table 237, Effectivity of an assembly part number/component part number combination (COMPIN-
EFF). This table documents the required starting, and proposed ending, effectivity of an assembly/component part
combination.

a. The value of the product--tracking-base--identifier (BASNUM500) in this table (inherited from Table
515) must be the same as the value of BASNUM500 found in the inheritance path: Table 237 to Table
234 to Table 053 to Table 060 to Table 050 to either Table 510 or 511, as appropriate.

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF237).

c. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF237).

Code Data Element Title DED Key

APARNO234 assembled-part-product-identifier 0024 FK
CPARNO234 component-part-product-identifier 0024 FK
DESCAG053 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
STREFF237 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF237 product-ending-effectivity-sequential-tracking-identifier 0058 FK, O

B.5.5.34. Table 238, Effectivity of an assembly part number/component material combination (COMPMAT-
EFF). This table documents the required starting, and proposed ending, effectivity of an assembly/component
material (not identified by a part number) combination.

a. The value of the product--tracking-base--identifier (BASNUM500) in this table (inherited from Table
515) must be the same as the value of BASNUM500 found in the inheritance path: Table 238 to Table
235 to Table 053 to Table 050 to Table 60 to either Table 510 or 511, as appropriate.

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF238).

c. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF238).

Code Data Element Title DED Key

DESCAG053 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK

B-99
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

MATIDN200 material-product-identifier 0038 FK

MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
STREFF238 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF238 product-ending-effectivity-sequential-tracking-identifier 0058 FK, O

B.5.5.35. Table 239, Effectivity of an assembly part number/component software combination (COMPSW-
EFF). This table documents the required starting, and proposed ending, effectivity of an assembly/component
software combination.

a. The value of the product--tracking-base--identifier (BASNUM500) in this table (inherited from Table
515) must be the same as the value of BASNUM500 found in the inheritance path: Table 239 to Table
236 to Table 053 to Table 050 to Table 060 to either Table 510 or 511, as appropriate.

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF239).

c. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF239).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF239 product-ending-effectivity-sequential-tracking-identifier 0058 FK, O

B.5.5.36. Table 240, Configuration tracked parts (TRACK-PIN). This table contains the identity of an installed
component part number, or an assembly item part number, and its tracking identifier. It is the basic building block
for the 'As-built'/'As-maintained' configuration record.

a. The product-effectivity-tracking-type-code must have a value of 'D', 'G', 'L', or 'M'. In effect, this table is a
super-type of Tables PIN-MSN/521, PIN-GSN/522, PIN-LOT/523 and PIN-DATECODE/529.

B-100
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
TRKIDN515 product-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.5.37. Table 241, Configuration-tracked material (TRACK-MAT). This table contains the identity of an
installed component material/part identifier (not identified by a part number), or an assembly item material/part
identifier (not identified by a part number), and its tracking identifier. It is the basic building block for the 'As-
built'/'As-maintained' configuration record.

a. The value of the product-effectivity-tracking-type-code must be either 'D' or 'L'. This means that, in
effect, this table is a super-type of Tables MAT-LOT/526 and MAT-DATECODE/530.

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.5.38. Table 242, As-configured assembly with component part (ASCONFIG-PINPIN). This table
correlates an assembly part number and its serial/lot tracking number with a specific component part number and
its serial/lot tracking number in the 'As-built'/'As-maintained' configuration.

a. The combination of component-part-design-enterprise-identifier (CENTID242) and component-part-

identifier (CPARNO242) cannot be the same as the combination of assembly-design-enterprise-identifier
(AENTID242) and assembly-part-identifier (APARNO242), nor can they be cyclic. (For example, if A is
an assembly containing component B, then B can never have a component A at any level.)

b. If the component-part-product-tracking-identifier (CTRKID242) has a product-effectivity-tracking-type-

code has a value of 'G' or 'M', the assembly-part-component-quantity must be 1, the product-measurement-
unit-code must have a value of 'EA', and the component key information cannot appear in any other
record as an installed component on the most current product-assembly-status-date of any other assembly
in the database.

c. If the component-part-product-tracking-identifier has a product-effectivity-tracking-type-code of 'L' or 'D',

the total assembly-part-component-quantity for all most current assemblies with this component installed

B-101
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

must not exceed the quantity in Table PIN-LOT/523 (if the product-effectivity-tracking-type-code has a
value of 'L') or in Table PIN-DATECODE/529 (if the product-effectivity-tracking-type-code has a value of
'D').

d. The first time each combination of assembly-design-enterprise-identifier (AENTID242), assembly-

manufacturer-enterprise-defense-logistics--assigned-identification-code (AMFRCG242), assembly-part-
product-identifier (APARNO242), assembly-product-tracking-identifier (ATRKID242), component-part-
design-enterprise-identifier (CENTID242), component-part-manufacturer-enterprise-defense-logistic--
assigned-identification-code (CMFRCG242), component-part-product-identifier (CPARNO242),
component-part-product-tracking-identifier (CTRKID242) is entered in this table, the value of product-
assembly-status-date (STATDT242) shall default to the value of product-manufacture-date
(MFRDAT515) in Table 515 for the instance which is inherited as the combination of assembly-design-
enterprise-identifier (AENTID242), assembly-manufacturer-enterprise-defense-logistics--assigned-
identification-code (AMFRCG242), assembly-part-product-identifier (APARNO242), and assembly-
product-tracking-identifier (ATRKID242).

e. Attribute design-enterprise-identifier (DESENT210) inherited from Table 240 assumes the role assembly-
design-enterprise-identifier (AENTID242).

f. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 240 assumes the role assembly-manufacturer-enterprise-defense-logistics--assigned-
identification-code (AMFRCG242).

g. Attribute part-product-identifier (PARNUM210) inherited from Table 240 assumes the role assembled-
part-product-identifier (APARNO242).

h. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 240 are concatenated and assume the role
assembly-product-tracking-identifier (ATRKID242). (See Appendix C for concatenation order.)

i. Attribute design-enterprise-identifier (DESENT210) inherited from Table 240 assumes the role
component-part-design-enterprise-identifier (CENTID242).

j. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 240 assumes the role component-part-manufacturer-enterprise-defense-logistics--
assigned-identification-code (CMFRCG242).

k. Attribute part-product-identifier (PARNUM210) inherited from Table 240 assumes the role component-
part-product-identifier (CPARNO242).

l. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 240 are concatenated and assume the role
component-part-product-tracking-identifier (CTRKID242). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

STATCD242 product-assembly-status-code 0174 K
STATDT242 product-assembly-status-date 0082 K
STATTM242 product-assembly-status-time 0160 K
AENTID242 assembly-design-enterprise-identifier 0052 FK

B-102
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

AMFRCG242 assembly-manufacturer-enterprise-defense-logistics-- 0001 FK

assigned-identification-code
APARNO242 assembled-part-product-identifier 0024 FK
ATRKID242 assembly-product-tracking-identifier 0175 FK
CENTID242 component-part-design-enterprise-identifier 0052 FK
CMFRCG242 component-part-manufacturer-enterprise-defense-logistics-- 0001 FK
assigned-identification-code
CPARNO242 component-part-product-identifier 0024 FK
CTRKID242 component-part-product-tracking-identifier 0175 FK

QUANTY242 assembly-part-component-quantity 0053 M

UOMCOD242 product-measurement-unit-code 0054 M

B.5.5.39. Table 243, As-configured assembly with component material (ASCONFIG-PINMAT). This table
correlates an assembly part number and its serial/lot tracking number with a specific component material/part
identifier (not identified by a part number) and its serial/lot tracking number in the 'As-built'/'As-maintained'
configuration.

a. The total quantity for all most current assemblies with this component part installed must not exceed the
quantity in Table MAT-LOT/526 (if the product-effectivity-tracking-type-code = 'D').

b. The first time each combination of assembly-design-enterprise-identifier (AENTID243), assembly-

manufacturer-enterprise-defense-logistics--assigned-identification-code (AMFRCG243), assembly-part-
product-identifier (APARNO243), assembly-product-tracking-identifier (ATRKID243), component-
material-design-enterprise-identifier (CENTID243), component-material-manufacturer-enterprise-
defense-logistics--assigned-identification-code (CMFRCG243), component-material-product-tracking-
identifier (CTRKID243), material-product-generic-identifier (MATGID200), and material-product-
identifier (MATIDN200) is entered in this table, the value of product-assembly-status-date (STATDT243)
shall default to the value of product-manufacture-date (MFRDAT515) in Table 515 for the instance which
is inherited as the combination of assembly-enterprise-identifier (AENTID242), assembly-manufacturer-
commercial-government-enterprise-identification-code (AMFRCG242), assembly-part-product-identifier
(APARNO242), and assembly-product-tracking-identifier (ATRKID242).

c. Attribute design-enterprise-identifier (DESENT210) inherited from Table 240 assumes the role assembly-
design-enterprise-identifier (AENTID243).

d. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 240 assumes the role assembly-manufacturer-enterprise-defense-logistics--assigned-
identification-code (AMFRCG243).

e. Attribute part-product-identifier (PARNUM210) inherited from Table 240 assumes the role assembled-
part-product-identifier (APARNO243).

f. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 240 are concatenated and assume the role
assembly-product-tracking-identifier (ATRKID243). (See Appendix C for concatenation order.)

g. Attribute design-enterprise-identifier (DESENT200) inherited from Table 241 assumes the role
component-material-design-enterprise-identifier (CENTID243).

B-103
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

h. Attribute material-product-generic-identifier (MATGID200) inherited from Table 241 assumes the role
component-material-product-generic-identifier (CMATGI243).

i. Attribute material-product-identifier (MATIDN200) inherited from Table 241 assumes the role
component-material-product-identifier (CMATID243).

j. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 241 assumes the role component-material-manufacturer-enterprise-defense-
logistics--assigned-identification-code (CMFRCG243).

k. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 241 are concatenated and assume the role
component-material-product-tracking-identifier (CTRKID243). (See Appendix C for concatenation
order.)

Code Data Element Title DED Key

STATCD243 product-assembly-status-code 0174 K
STATDT243 product-assembly-status-date 0082 K
STATTM243 product-assembly-status-time 0160 K
AENTID243 assembly-design-enterprise-identifier 0052 FK
AMFRCG243 assembly-manufacturer-enterprise-defense-logistics-- 0001 FK
assigned-identification-code
APARNO243 assembled-part-product-identifier 0024 FK
ATRKID243 assembly-product-tracking-identifier 0175 FK
CENTID243 component-material-design-enterprise-identifier 0052 FK
CMATGI243 component-material-product-generic-identifier 0092 FK
CMATID243 component-material-product-identifier 0038 FK
CMFRCG243 component-material-manufacturer-enterprise-defense- 0001 FK
logistics--assigned-identification-code
CTRKID243 component-material-product-tracking-identifier 0175 FK

QUANTY243 assembly-part-component-quantity 0053 M

UOMCOD243 product-measurement-unit-code 0054 M

B.5.5.40. Table 244, As-configured material with component material (ASCONFIG-MATMAT). This table
correlates an assembly component material/part identifier (not identified by a part number) and its serial/lot
tracking number with a specific component material/part identifier (not identified by a part number) and its serial/
lot tracking number in the 'As-built'/'As-maintained' configuration.

a. The combination of assembly-design-enterprise-identifier (AENTID244), assembly-material-product-

generic-identifier (AMATGI244), and assembly-material-product-identifier (AMATID244) cannot be the
same as the combination of component-material-design-enterprise-identifier (CENTID244), component-
material-product-generic-identifier (CMATGI244), and component-material-product-identifier
(CMATID244), nor can they be cyclic.

B-104
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. The total quantity for all most current assemblies with this component material installed cannot exceed
the quantity in Table MAT-LOT/526 (if the product-effectivity-tracking-type-code = 'L'), or in Table
MAT-DATECODE/530 (if the product-effectivity-tracking-type-code = 'D').

c. The first time each combination of assembly-design-enterprise-identifier (AENTID244), assembly-

material-product-generic-identifier (AMATGI244), assembly-material-product-identifier (AMATID244),
assembly-manufacturer-enterprise-defense-logistics--assigned-identification-code (AMFRCG244),
assembly-product-tracking-identifier (ATRKID244), component-material-design-enterprise-identifier
(CENTID244), component-material-product-generic-identifier (CMATGI244), component-material-
product-identifier (CMATID244), component-material-manufacturer-enterprise-defense-logistics--
assigned-identification-code (CMFRCG244), and component-material-product-tracking-identifier
(CTRKID244) is entered in this table, the value of product-assembly-status-date (STATDT243) shall
default to the value of product-manufacture-date (MFRDAT515) in Table 515 for the instance which is
inherited as the combination of assembly-design-enterprise-identifier (AENTID244), assembly-material-
product-generic-identifier (AMATGI244), assembly-material-product-identifier (AMATID244),
assembly-manufacturer-enterprise-defense-logistics--assigned-identification-code (AMFRCG244), and
assembly-product-tracking-identifier (ATRKID244).

d. Attribute design-enterprise-identifier (DESENT200) inherited from Table 241 assumes the role assembly-
design-enterprise-identifier (AENTID244).

e. Attribute material-product-generic-identifier (MATGID200) inherited from Table 241 assumes the role
assembled-material-product-generic-identifier (AMATGI244).

f. Attribute material-product-identifier (MATIDN200) inherited from Table 241 assumes the role
assembled-material-product-identifier (AMATID244).

g. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 241 assumes the role assembly-manufacturer-enterprise-defense-logistics--assigned-
identification-code (AMFRCG244).

h. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 241 are concatenated and assume the role
assembly-product-tracking-identifier (ATRKID244). (See Appendix C for concatenation order.)

i. Attribute design-enterprise-identifier (DESENT200) inherited from Table 241 assumes the role
component-material-design-enterprise-identifier (CENTID244).

j. Attribute material-product-generic-identifier (MATGID200) inherited from Table 241 assumes the role
component-material-product-generic-identifier (CMATGI244).

k. Attribute material-product-identifier (MATIDN200) inherited from Table 241 assumes the role
component-material-product-identifier (CMATID244).

l. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 241 assumes the role component-material-manufacturer-enterprise-defense-
logistics--assigned-identification-code (CMFRCG244).

m. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 241 are concatenated and assume the role
component-material-product-tracking-identifier (CTRKID244). (See Appendix C for concatenation
order.)

Code Data Element Title DED Key

STATCD244 product-assembly-status-code 0174 K
STATDT244 product-assembly-status-date 0082 K

B-105
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

STATTM244 product-assembly-status-time 0160 K

AENTID244 assembly-design-enterprise-identifier 0052 FK
AMATGI244 assembled-material-product-generic-identifier 0092 FK
AMATID244 assembled-material-product-identifier 0038 FK
AMFRCG244 assembly-manufacturer-enterprise-defense-logistics-- 0001 FK
assigned-identification-code
ATRKID244 assembly-product-tracking-identifier 0175 FK
CENTID244 component-material-design-enterprise-identifier 0052 FK
CMATGI244 component-material-product-generic-identifier 0092 FK
CMATID244 component-material-product-identifier 0038 FK
CMFRCG244 component-material-manufacturer-enterprise-defense- 0001 FK
logistics--assigned-identification-code
CTRKID244 component-material-product-tracking-identifier 0175 FK

QUANTY244 assembly-part-component-quantity 0053 M

UOMCOD244 product-measurement-unit-code 0054 M

B.5.5.41. Table 245, As-configured assembly with installed software (ASCONFIG-PINSW). This table
correlates an assembly part number and its serial/lot tracking number with a specific component (defense) software
identifier in the 'As-built'/'As-maintained' configuration.

a. The first time each combination of software-product-source-entity-identifier (SWSORC170), software-

product-identifier (SWIDEN170), design-enterprise-identifier (DESENT210), manufacturer-enterprise-
defense-logistics--assigned-identification-code (MFRCAG515), part-product-identifier (PARNUM210),
product-sequential-tracking-identifier (TRKIDN515), and product-change-effectivity-tracking-type-code
(TRKTYP515) is entered in this table, the value of product-assembly-status-date (STATDT242) shall
default to the value of product-manufacture-date (MFRDAT515) in Table 515 for the instance which is
inherited as the combination of design-enterprise-identifier (DESENT210), manufacturer-enterprise-
defense-logistics--assigned-identification-code (MFRCAG515), part-product-identifier (PARNUM210),
product-sequential-tracking-identifier (TRKIDN515), and product-change-effectivity-tracking-type-code
(TRKTYP515).

Code Data Element Title DED Key

STATCD245 product-assembly-status-code 0174 K
STATDT245 product-assembly-status-date 0082 K
STATTM245 product-assembly-status-time 0160 K
DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
SWIDEN170 software-product-generic-identifier 0060 FK
SWSORC170 software-product-source-entity-identifier 0033 FK
TRKIDN515 product-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

B.5.5.42. Tables 246 through 249. Reserved.

B-106
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.6. Engineering change proposals. Entity tables numbered in the range of 250 through 299 contain the
identification of engineering change proposals and their associated attributes. ECPs are primarily a military
document used to identify changes which are required to engineering drawings, program-unique or military
specifications, and defense software. However, most companies which contract with the U.S. Department of
Defense either use this same document internally, or have developed a similar internal methodology (contractor
format ECP equivalent documents are typically called Engineering Change Notices [ECNs], Engineering Change
Orders [ECOs], etc.). This section only addresses the military requirement; therefore, it only includes ECPs
identified by a CAGE (or NSCM) code and a number. It recognizes that ECNs and ECOs are used and that they
typically are identified using the same rules; therefore, an interface is provided to use this portion of the database to
access company internal ECP-equivalent documents.

The relationships between these various ECP entity tables and between ECPs and the documents changed by them
are depicted in Figures 06ECP1 through 06ECP5.

B.5.6.1. Table 250, Engineering change proposal definition (ECP). This table includes the unique and primary
identification of an Engineering Change Proposal. An ECP is one subtype of Table CAGE-NUMDOC/022 for the
case where the document-type-code in Table 010 has a value of 'ECP'.

a. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 022 assumes the role engineering-change-proposal-document-source-enterprise-
defense-logistics--assigned-identification-code (ECPCAG250).

b. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 022 assumes the role
engineering-change-proposal-document-alphanumeric-identifier (ECPNUM250).

c. Attribute document-type-code (DOCTYP010) inherited from Table 022 assumes the role engineering-
change-proposal-document-type-code (ECPTYP250).

Code Data Element Title DED Key

B.5.6.2. Table 251, Engineering change proposal revisions (ECPREV). This table is a subtype of Table CAGE-
NUM-DOCREV/023 and contains the revision history of the ECP during its life cycle. There are two subtypes of
this entity, based on the value of engineering-change-proposal-document-change-classification-code (ECP005251):
Tables CLASS1ECP/289 and CLASS2ECP (not shown). There are no special attributes attached to a class II ECP;
however, there are numerous additional special attributes required for a class I ECP. This table also correlates
'related' ECPs with their primary ECP and identifies when unrelated ECPs must be implemented in a particular
sequence. Related ECPs are those ECPs which must be implemented simultaneously.

B-107
CLIN / 959 (from 26CON2) CAGE-NUM-DOCREV / 023 (from 1GEN4) ECP-BLINE / 254
contract-identifier CAGE-NUM-DOC / 022 (from 1GEN3)
document-source-cage-code STAFF / 943 (from 25ADD1) ecp-cage-code (FK)
contract-modification ecp-alphanumeric-identifier (FK) document-source-cage-code
document-alphanumeric-identifier person-name document-alphanumeric-identifier
clin-identifier document-type-code ECP (FK)
office-address document-type-code
document-generic-revision baseline-type-code
ecp-revision (FK)
may be affected by
document-type-code may concur in class of document-type-code
P ECP
ECP-AFFECTED-ITEM / 255 ECP impacts
ecp-cage-code (FK) ECP / 250 (see 7NOR1, 10RFD1, 17PAN1, 18AUD1)
ecp-alphanumeric-identifier (FK) ECPREV / 251 (de facto child of 250) (see 6ECP2, 6ECP3, 7NOR2)
ecp-cage-code.document-source-cage-code (FK)
ECP (FK) ecp-cage-code.document-source-cage-code (FK)
ecp-alphanumeric-identifier.document-alphanumeric-identifier (FK)
contract-identifier (FK) ecp-alphanumeric-identifier.document-alphanumeric-identifier (FK)
may be primary for ECP.document-type-code (FK)
contract-modification (FK) ECP.document-type-code (FK)
clin-identifier (FK) ecp-revision.document-generic-revision (FK)
ecp-revision (FK)
ecp-class-type-code
ecp-format-type-code Assertion: If the value of primary-ecp-indicator-
dcmc-contact-name.person-name (FK) code in ECPREV / 251 is 'P', the relationship
dcmc-address.office-address (FK) of Table 250 to 251 is 1:0 and this is a null
may impact ecp-change-class-concurrence-code GENERIC-DOCUMENT / 010 (from 1GEN02)
parent case. If the value of primary-ecp-
primary-ecp-indicator-code indicator-code is 'R', the relationship is 1:P document-source-entity-identifier
may impact primary-ecp-cage-code.ecp-cage-code (FK) and null parents are not allowed. If the value document-identifier
primary-ecp-alphanumeric-identifier.ecp-alphanumeric-identifier (FK) of primary-ecp-indicator-code is 'S', the document-type-code
ECP-CON / 257 primary-ecp-document-type-code.ECP (FK) relationship is 1:0-M and null parents are not
ecp-cage-code (FK) allowed.
ecp-alphanumeric-identifier (FK)
ECP (FK) has has extended text in
contract-identifier (FK) ecp-class-type-code may be a
contract-modification (FK) may have justification supplemented by supplement to
CLASS 1 (or Major) Z
P

B-108
ecp-revision (FK)
ECP-EXTTXT / 261
ECPREV-STAT / 294 (de facto subtype of 850) may be extended
ecp-cage-code (FK) text file for
APPENDIX B

document-revision-approval-status-code
MIL-STD-2549

ecp-alphanumeric-identifier (FK) ECP-SUPDOC / 253

may be document-revision-approval-status-date
impacted by ECP (FK) ecp-cage-code (FK)
ecp-cage-code (FK) ecp-revision (FK) FILE / 900 (from 23FILE1) ecp-alphanumeric-identifier (FK)
ecp-alphanumeric-identifier (FK) file-originator (FK) file-originator ECP (FK)
CONMOD / 951 (from 26CON2) ECP (FK) file-originator-office-addess (FK) file-originator-office-addess ecp-revision (FK)
ecp-revision (FK) file-identifier (FK)
contract-identifier file-identifier document-source-entity-identifier (FK)
contract-modification file-creation-date (FK) file-creation-date document-identifier (FK)
file-creation-time (FK) file-creation-time document-type-code (FK)
document-revision-approval-status-code
may implement APV
CLASS1ECP / 289 (see 6ECP5)
ecp-cage-code (FK) may be cost spread-sheet for
APPRECP-CONMOD / 292 ecp-alphanumeric-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

contract-identifier (FK) ECP (FK) may have associated cost

contract-modification (FK) ecp-revision (FK) Z
ecp-cage-code (FK) may have unusual impacts
ecp-alphanumeric-identifier (FK) ECPCOST / 252
may be
ECP (FK) implemented ecp-cost-component-code
ecp-revision (FK) by (de facto subtype of 854) ECP-OTHER / 265 ecp-cage-code (FK)
document-revision-approval-status-code (FK) ecp-cage-code (FK) ecp-alphanumeric-identifier (FK)
ECPREV-APP / 295 (see 6ECP2, 6ECP5, 7NOR2, 12RAD1) ECP (FK)
document-revision-approval-status-date (FK) ecp-alphanumeric-identifier (FK)
ecp-cage-code (FK) (AK1) ECP (FK) ecp-revision (FK)
ecp-alphanumeric-identifier (FK) (AK1) ecp-revision (FK) file-originator (FK)
ECP (FK) (AK1) ecp-unusual-effect-title file-originator-office-addess (FK)
FIGURE 06ECP1 document-revision-approval-status-code (FK) file-identifier (FK)
ENGINEERING CHANGE PROPOSAL (ECP) DEFINITION document-revision-approval-status-date (FK) file-creation-date (FK)
ecp-revision (FK) file-creation-time (FK)
ECPREV / 251 (from 6ECP1) ECPREV-DOCREV / 266 (see 6ECP3) ECPREV-APP / 295 (from 6ECP1)
may affect may cause new
ecp-cage-code ecp-cage-code (FK) may be approved, ecp-cage-code
document
ecp-alphanumeric-identifier Assertion: If the value ecp-alphanumeric-identifier (FK) resulting in a new ecp-alphanumeric-identifier
revision(s)
ECP of ecp-format-type in ECP (FK) document revision ECP
ecp-revision Table 251 is not 'M', ecp-revision (FK) ecp-revision
the relation of Table document-source-entity-identifier (FK) Z document-revision-approval-status-code
251 to Table 266 is 1:P document-identifier (FK) document-revision-approval-status-date
APPRECP-DOCREV / 271 (see 6ECP4)
document-type-code (FK)
may be document-current-generic-revision.document-generic-revision (FK) ecp-cage-code (FK)
GENERIC-DOCREV / 011 (from 1GEN2) affected ecp-alphanumeric-identifier (FK)
document-source-entity-identifier by ECP (FK)
document-identifier document-source-entity-identifier (FK) ORGSTDDOCREV / 403 (from 11STDS1)
may be the resulting revision of
document-type-code document-identifier (FK) document-source-organization-identifier
document-generic-revision document-type-code (FK) document-alphanumeric-identifier
SPECREV / 101 (from 3SPEC1)
document-generic-revision (FK) document-type-code
design-cage-code document-generic-revision
document-alphanumeric-identifier document-current-generic-revision (FK)
SWVER-CAGE / 153 (from 4SW2) document-type-code document-revision-approval-status-code (FK)
design-cage-code document-revision document-revision-approval-status-date (FK)
ecp-revision (FK) may be the
document-alphanumeric-identifier
resulting
document-type-code
revision of
document-generic-revision
may be the resulting revision of document-type-code
P-SPEC STDDOC
DWG
APPRECP-SPECREV / 287 (see 7NOR4, 15SUP6)
design-cage-code.(document-source-entity-identifier,design-cage-code) (FK) DWGREV / 051 (from 2DWG1)
may be the document-alphanumeric-identifier.(document-identifier,document-alphanumeric-identifier) (FK) design-cage-code
resulting document-type-code (FK) drawing-alphanumeric-identifier
revision of document-revision.(document-generic-revision,document-revision) (FK) document-type-code
ecp-cage-code (FK) document-revision
ecp-alphanumeric-identifier (FK)

B-109
ECP (FK)
Assertion: The may be the resulting revision of
relationships
APPENDIX B
MIL-STD-2549

SW between Table
PL 051 and 286
APPRECP-SWVER / 270 and between Table 051 and
design-cage-code.(document-source-entity-identifier,design-cage-code) (FK) may be the resulting revision of 285 are mutually exclusive.
document-alphanumeric-identifier.(document-identifier,document-alphanumeric-identifier) (FK)
document-type-code (FK) APPRECP-DWGREV / 285 (see 7NOR4)
document-revision design-cage-code.(document-source-entity-identifier,design-cage-code) (FK)
ecp-cage-code (FK) drawing-alphanumeric-identifier.(document-identifier,drawing-alphanumeric-identifier) (FK)
ecp-alphanumeric-identifier (FK) DWG.document-type-code (FK)
document-generic-revision (FK) document-revision.(document-generic-revision,document-revision) (FK)
ECP (FK) ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
ECP (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

APPRECP-PLREV / 286 (see 7NOR4)

design-cage-code.(document-source-entity-identifier,design-cage-code) (FK)
drawing-alphanumeric-identifier.(document-identifier,drawing-alphanumeric-identifier) (FK) APPRECP-DEFSPECREV / 288 (see 7NOR4)
PL.document-type-code (FK) document-source-entity-identifier (FK)
document-revision.(document-generic-revision,document-revision) (FK) document-alphanumeric-identifier.(document-identifier,document-alphanumeric-identifier) (FK)
ecp-cage-code (FK) document-type-code (FK)
ecp-alphanumeric-identifier (FK) document-generic-revision (FK)
ECP (FK) ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
ECP (FK)
FIGURE 06ECP2 document-source-organization-identifier (FK)
ECP-DOCUMENT CORRELATION (as approved)
ECPREV-DOCREV / 266 (from 6ECP2)
ecp-cage-code ECPREV / 251 (from 6ECP1)
ecp-alphanumeric-identifier ecp-cage-code BASETRACK / 515 (from 13TRK2)
CAGEPIN / 212 (from 5PIN2) ECP ecp-alphanumeric-identifier product--tracking-base--identifier
ecp-revision ECP
design-cage-code manufacturer-cage-code
document-source-entity-identifier ecp-revision
part-identifier product-effectivity-tracking-type
document-identifier
product-tracking-identifier
document-type-code document-type-code
document-current-generic-revision

has proposed
may be effectivity
affected by
affects may be proposed starting effectivity

may be proposed ending effectivity

ECP-PART / 258 (see 6ECP4, 12MOD5)
ECP-RETRO / 290 (from 6ECP5)
ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK) ecp-cage-code
ECP (FK) ecp-alphanumeric-identifier
ecp-revision (FK) ECP
design-cage-code.(design-cage-code,document-source-entity-identifier) (FK) ecp-revision
part-identifier.part-identifier (FK)
document-alphanumeric-identifier.document-identifier (FK)

B-110
document-type-code (FK)
document-current-generic-revision (FK) is effective
APPENDIX B
MIL-STD-2549

ECP-PROPEFF / 259 (see 6ECP4) RETROFIT / 260

ecp-cage-code (FK) ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK) ecp-alphanumeric-identifier (FK)
ECP (FK) may have ECP (FK)
ecp-revision (FK) retrofit ecp-revision (FK)
manufacturer-cage-code (FK) locations manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

product-effectivity-tracking-type (FK)
starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK) starting-effectivity-product-tracking-identifier (FK)
product--tracking-base--identifier (FK) ship-identifier
ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK) vehicle-identifier
product-effectivity-timing-type-code retrofit-completion-date

FIGURE 06ECP3
ENGINEERING CHANGE PROPOSAL EFFECTIVITY
COMPPIN-EFF / 237 (from 5PIN5) APPRECP-DOCREV / 271 (from 6ECP2)
ECP-PART / 258 (from 6ECP3)
design-cage-code ECP-PROPEFF / 259 (from 6ECP3) ecp-cage-code
assembled-product-identifier ecp-cage-code
ecp-alphanumeric-identifier
manufacturer-cage-code ecp-alphanumeric-identifier ecp-cage-code
ECP
product-effectivity-tracking-type ECP ecp-alphanumeric-identifier
document-source-entity-identifier
starting-effectivity-product-tracking-identifier ecp-revision ECP
document-identifier
design-enterprise-identifier design-cage-code ecp-revision
document-type-code
component-part-identifier part-identifier manufacturer-cage-code
document-generic-revision
product-effectivity-tracking-type
ending-effectivity-product-tracking-identifier document-alphanumeric-identifier starting-effectivity-product-tracking-identifier ecp-revision
product-tracking-base-identifier document-type-code
ecp-approved-status-code
component-quantity document-current-revision ending-effectivity-product-tracking-identifier
document-superceded-revision
product--tracking-base--identifier
product-effectivity-timing-type-code

may apply to COMPSW-EFF / 239 (from 5PIN5)

implements
assembly-design-cage-code
part-identifier
may apply to may apply to manufacturer-cage-code
may apply to product-effectivity-tracking-type
may apply to starting-effectivity-product-tracking-identifier
software-source-identifier
may apply to software-generic-identifier
may apply to ending-effectivity-product-tracking-identifier
COMPMAT-EFF / 238 (from 5PIN5) product--tracking-base--identifier
APPRECP-COMPPIN / 256 design-cage-code
part-identifier
ecp-cage-code (FK) manufacturer-cage-code implements
ecp-alphanumeric-identifier (FK) product-effectivity-tracking-type
ECP (FK) starting-effectivity-product-tracking-identifier
design-cage-code.(design-cage-code,document-source-entity-identifier) (FK) design-enterprise-identifier may apply to
assembled-product-identifier.(assembled-product-identifier,part-identifier) (FK) material-generic-identifier
manufacturer-cage-code (FK) material-identification

B-111
product-effectivity-tracking-type (FK)
starting-effectivity-product-tracking-identifier (FK) ending-effectivity-product-tracking-identifier
design-enterprise-identifier (FK) product-tracking-base-identifier
APPENDIX B

component-part-identifier (FK) component-quantity

MIL-STD-2549

document-generic-revision (FK)
document-alphanumeric-identifier.document-identifier (FK) implements
document-type-code (FK) may apply to
ecp-revision (FK)

APPRECP-COMPSW / 293
APPRECP-COMPMAT / 284
ecp-cage-code (FK)
ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
ecp-alphanumeric-identifier (FK)
ECP (FK)
ECP (FK)
assembly-design-cage-code.(assembly-design-cage-code,document-source-entity-identifier,design-cage-code) (FK)
design-cage-code.(document-source-entity-identifier,design-cage-code) (FK)
part-identifier (FK)
part-identifier (FK)
manufacturer-cage-code (FK)
manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

product-effectivity-tracking-type (FK)
starting-effectivity-product-tracking-identifier (FK)
starting-effectivity-product-tracking-identifier (FK)
software-source-identifier (FK)
design-enterprise-identifier (FK)
software-generic-identifier (FK)
material-generic-identifier (FK)
material-identification (FK) document-alphanumeric-identifier.document-identifier (FK)
document-type-code (FK)
document-alphanumeric-identifier.document-identifier (FK)
document-generic-revision (FK)
document-type-code (FK)
ecp-revision (FK)
document-generic-revision (FK)
ecp-revision (FK)

FIGURE 06ECP4
ENGINEERING CHANGE PROPOSAL IMPACT ON ASSEMBLIES
CCB-ECP / 705 (from 19CI2) ECPREV-APP / 295 (from 6ECP1) CLASS1ECP / 289 (from 6ECP1) DODTECHMAN / 552 (from 14TM1)
enterprise-identifier ecp-cage-code ecp-cage-code us-dod-document-source-organization-code
program-name ecp-alphanumeric-identifier ecp-alphanumeric-identifier document-alphanumeric-identifier
ccb-name ECP ECP TECHMAN
ecp-cage-code ecp-revision ecp-revision
ecp-alphanumeric-identifier document-revision-approval-status-code
ECP document-revision-approval-status-date retrofit-requirement-code
ecp-revision
may be impacted by
may impact
retrofit-requirement-code
may direct may require
Y
OFFICE / 941 (from 25ADD1) RETRO-LVL / 263
enterprise-identifier ECP-RETRO / 290 (see 6ECP3, 14TM4) ecp-cage-code (FK)
office-symbol ecp-alphanumeric-identifier (FK)
ecp-cage-code (FK) ECP (FK)
ecp-alphanumeric-identifier (FK) ecp-revision (FK)
ECP (FK) is performed by retrofit-level-of-maintenance
ecp-revision (FK)
P retrofit-kit-installation-time
may be responsible for retrofit-kit-installation-test-time
retrofit-system-test-time
kit-quantity

B-112
ECPACT / 262 (see 14TM3,14TM5,15SUP1,15SUP2,15SUP3,15SUP4,15SUP5)
ccb-enterprise-identifier.enterprise-identifier (FK)
APPENDIX B

program-name (FK) ECP-TECHMAN / 291 (see 14TM4,15SUP1,15SUP2,15SUP3,15SUP4,15SUP5)

MIL-STD-2549

ccb-name (FK)
ecp-cage-code (FK) ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK) ecp-alphanumeric-identifier (FK)
ECP (FK) ECP (FK)
ecp-revision (FK) ecp-revision (FK)
may require us-dod-document-source-organization-code (FK)
ecp-implementation-action-identifier
document-alphanumeric-identifier (FK)
ecp-implementation-action-responsible-enterprise-identifier.enterprise-identifier (FK) TECHMAN (FK)
ecp-implementation-action-responsible-office.office-symbol (FK)
TECHMAN (FK)
us-dod-document-source-organization-code (FK)
document-alphanumeric-identifier (FK)
document-revision-approval-status-code (FK) ECPACTSTAT / 264
document-revision-approval-status-date (FK) ccb-enterprise-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

program-name (FK)
ccb-name (FK)
ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
has life cycle status ECP (FK)
ecp-revision (FK)
P ecp-implementation-action-identifier (FK)
ecp-implementation-action-status-code
FIGURE 06ECP5
ecp-implementation-action-status-date
ENGINEERING CHANGE PROPOSAL IMPLEMENTATION
March 18, 1997
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. For related ECPs, the value of primary-engineering-change-proposal-document-indicator-code

(PECPFG250) must be 'R' and the value of engineering-change-proposal-document-implementation-
sequence-code (ECPSEQ250) must be 'W'.

b. If the value of primary-engineering-change-proposal-document-indicator-code (PECPFG250) is 'R' or 'S',

the values of primary-engineering-change-proposal-document-source-enterprise-defense-logistics--
assigned-identification-code (PECPCG250), primary-engineering-change-proposal-document-
alphanumeric-identifier (PECPNO250), engineering-change-proposal-document-type-code
(PECPTY250), and engineering-change-proposal-document-implementation-sequence-code
(ECPSEQ250) must be non-blank. These four elements must be blank for all other values of
PECPFG250.

c. For ECPs with sequential implementation requirements, the value of PECPFG250 must be 'S'. The
engineering-change-proposal-document-implementation-sequence-code (ECPSEQ250) indicates the
implementation order between this ECP and the primary ECP (identified by fields PECPCG250,
PECPNO250, and PECPTY250. Therefore, it should be read, "This ECP must be implemented _____ the
primary ECP."

d. For each instance in this table, the combination of the values of engineering-change-proposal-document-
source--enterprise-defense-logistics--assigned-identification-code (ECPCAG250), engineering-change-
proposal-document-alphanumeric-identifier (ECPNUM250), and engineering-change-proposal-document-
type-code (ECPTYP250) cannot be the same as the combination of the values of primary-engineering-
change-proposal-document-source--enterprise-defense-logistics--assigned-identification-code
(PECPCG250), primary-engineering-change-proposal-document-alphanumeric-identifier (PECPNO250),
and primary-engineering-change-proposal-document-type-code (PECPTY250).

e. The values of engineering-change-proposal-document-contract-administrator-class-concurrence-date

(ECP27F251), procurement-quality-assurance-contact-human-name (ECP27E251), and engineering-
change-proposal-document-contract-administrator-class-concurrence-process-disposition-action-status-
code (ECP27C251) must all be blank, or all be non-blank.

f. If the value of engineering-change-proposal-document-change-class-code (ECP050251) is '1', the values

of interface-configuration-item-product-affected-code (ECP100251) and engineering-change-proposal-
document-in--production-code (ECP170251) are mandatory.

g. If the value of engineering-change-proposal-document-change-class-code (ECP050251) is '2', then the

value of engineering-change-proposal-document-format-type-code (ECP08E251) must be 'F'.

h. If the value of engineering-change-proposal-document-change-class-code (ECP050251) is '1' and the

value of engineering-change-proposal-document-format-type-code (ECP08E251) is 'F' or 'P', the value of
the change-proposal-document-product-delivery-schedule-effect-text (ECP0220251) is mandatory.

i. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role defense-
contract-management-enterprise-office-address-text (ECP27D251).

j. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role defense-contract-
management-command-contact-human-name (ECP27E251).

k. Because this table is a de facto child of Table 250, the value of document-source-enterprise-defense-
logistics--assigned-identification-code (SRCCAG022) inherited from Table 023 must exist as a
engineering-change-proposal-document-source-enterprise-defense-logistics--assigned-identification-code

B-113
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

(ECPCAG250) in Table 250. SRCCAG022 assumes the role engineering-change-proposal-document-

source-enterprise-defense-logistics--assigned-identification-code (ECPCAG250).

l. Because this table is a de facto child of Table 250, the value of document-alphanumeric-identifier
(DOCNUM020) inherited from Table 023 must exist as a engineering-change-proposal-document-
alphanumeric-identifier (ECPNUM250) in Table 250. DOCNUM020 assumes the role engineering-
change-proposal-document-alphanumeric-identifier (ECPNUM250).

m. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 023 assumes the role
engineering-change-proposal-document-alphanumeric-revision-identifier (ECPREV251).

n. Because this table is a de facto child of Table 250, the value of document-type-code (DOCTYP010)
inherited from Table 023 must exist as a engineering-change-proposal-document-type-code (ECPTYP250)
in Table 250. DOCTYP010 assumes the role engineering-change-proposal-document-type-code
(ECPTYP250).

o. Attribute engineering-change-proposal-document-source-enterprise-defense-logistics--assigned-
identification-code (ECPCAG250) inherited from Table 250 assumes the role primary-engineering-
change-proposal-document-source-enterprise-defense-logistics--assigned-identification-code
(PECPCG251).

p. Attribute engineering-change-proposal-document-alphanumeric-identifier (ECPNUM250) inherited from

Table 250 assumes the role primary-engineering-change-proposal-document-alphanumeric-identifier
(PECPNO251).

q. Attribute engineering-change-proposal-document-type-code (ECPTYP250) inherited from Table 250

assumes the role primary-engineering-change-proposal-document-type-code (PECPTY251).

Code Data Element Title DED Key

ECP27D251 defense-contract-management-enterprise-office-address-text 0081 FK, O

ECP27E251 defense-contract-management-command-contact-human- 0069 FK, O
name
PECPCG251 primary-engineering-change-proposal-document-source- 0001 FK, O
enterprise-defense-logistics--assigned-identification-code
PECPNO251 primary-engineering-change-proposal-document- 0003 FK, O
alphanumeric-identifier
PECPTY251 primary-engineering-change-proposal-document-type-code 0004 FK, O
ECP050251 engineering-change-proposal-document-change-class-code 0164 M
ECP08E251 engineering-change-proposal-document-format-type-code 0194 M
ECP100251 interface-configuration-item-product-affected-code 0129
ECP170251 engineering-change-proposal-document-in--production-code 0223

B-114
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ECP190251 change-proposal-document-change-description-text 0171 M

ECP200251 change-proposal-document-change-justification-text 0171 M
ECP220251 change-proposal-document-production-delivery-schedule- 0171
effect-text
ECP27C251 engineering-change-proposal-document-class-concurrence- 0021
process-disposition-status-code
ECP27F251 engineering-change-proposal-document-contract- 0082
administration-change-class-concurrence-date
ECPSEQ251 engineering-change-proposal-document-implementation- 0119
sequence-code
PECPFG251 primary-engineering-change-proposal-document-indicator- 0187 M
code
SGM190251 standard-generalized-markup-language-document-proposed- 0118
change-long-description-field-identifier
SGM200251 standard-generalized-markup-language-document-proposed- 0118
change-long-need-rationale-field-identifier
SGM20A251 standard-generalized-markup-language-document-change- 0118
proposal-disapproval-consequences-field-identifier

B.5.6.3. Table 252, Engineering change proposal cost information (ECPCOST). This table identifies the service
components (for example: Army, Navy, Air Force, etc.) for which there is a cost impact as a result of this ECP and
contains a pointer to the spreadsheet file containing the cost information associated with this class I ECP. (See
Data Information Packet 4 for required file contents and user interface requirements.)

a. The combination of file-originator-human-name (FILORG900), electronic-document-file-identifier

(FILIDN900) and enterprise-file-origination-office-address-text (FILADD900) can be associated with only
one combination of engineering-change-proposal-document-source-enterprise-defense-logistics--assigned-
identification-code (ECPCAG250), engineering-change-proposal-document-alphanumeric-identifier
(ECPNUM250), and engineering-change-proposal-document-alphanumeric-revision-identifier
(ECPREV251).

Code Data Element Title DED Key

SERVID252 engineering-change-proposal-cost--affected-enterprise- 0002 K
acronym-identification-code
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILIDN900 electronic-document-file-identifier 0206 FK
FILORG900 file-originator-human-name 0069 FK

FILDAT900 electronic-document-file-creation-date 0082 FK

FILTIM900 electronic-document-file-creation-time 0160 FK

B-115
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.6.4. Table 253, Identification of documents which supplement the contents of an ECP (ECP-SUPDOC). This
table correlates various documents with the ECP(s) which they supplement. Usually these documents are analysis,
reports, studies, or marked-up drawings.

a. The value of document-type-code (DOCTYP010) must be 'ANALYS', 'BOOK', 'DWG', 'MISC',

'PERIODL', 'PL', 'PLNPROC', 'P-SPEC', or 'STDDOC'.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.6.5. Table 254, Baseline(s) affected by an engineering change proposal (ECP-BLINE). This table identifies
the baseline(s) impacted by the ECP.

a. The value of 'product-baseline-type' (BLTYPE254) is limited to the values 'A', 'F', or 'P'.

Code Data Element Title DED Key

BLTYPE254 product-baseline-type-code 0098 K
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.6.6. Table 255, Contract line item(s) affected by an engineering change proposal (ECP-AFFECTED-ITEM).
This table correlates the ECP with the affected Contract Line Items. Only the most recent modification for any one
contract needs to be addressed.

Code Data Element Title DED Key

CLINUM959 contract-document-line-item-identifier 0017 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

B-116
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK

defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.6.7. Table 256, Effectivity of an approved ECP on an assembly with component parts (APPRECP-COMPIN).
This table correlates the effectivity of the approved ECP with the assembly-component part combinations which are
impacted by the ECP.

a. The values of document-alphanumeric-identifier (DOCNUM256) and document-type-code (DOCTYP010)

in this table must be the same as the values for the same-named fields in parent Table ECP-PART/258.

b. The value of DOCTYP010 must be either 'DWG' or 'PL'.

c. The value of document-generic-revision-identifier (DOCREV011) must be greater than the value of

document-current-generic-revision-identifier (DOCCRV266) in parent Table ECP-PART/258.

d. Attribute assembled-part-product-identifier (APARNO234) inherited from Table 237 and part-product-

identifier (PARNUM210) inherited from Table 258 must both have the same value. Therefore they merge
and assume the identity assembled-part-product-identifier (APARNO256).

e. Fields DESCAG053 inherited from Table 237, DESCAG258 inherited from Table 258, and SRCIDN010
inherited from Table 271 must be the same. Therefore, they merge and assume the identity design-
enterprise-defense-logistics--assigned-identification-code (DESCAG256).

f. Attribute document-identifier (DOCIDN010) inherited from Table 271 assumes the role document-
alphanumeric-identifier (DOCNUM256).

g. Fields STREFF237 inherited from Table 237 and STREFF259 inherited from Table 259 must be the
same; therefore, they assume the identity product-starting-effectivity-sequential-tracking-identifier
(STREFF256).

Code Data Element Title DED Key

APARNO256 assembled-part-product-identifier 0024 FK
CPARNO234 component-part-product-identifier 0024 FK
DESCAG256 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT210 design-enterprise-identifier 0052 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B-117
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

STREFF256 product-starting-effectivity-sequential-tracking-identifier 0058 FK

TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

DOCNUM256 document-alphanumeric-identifier 0003 FK

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier

B.5.6.8. Table 257, Correlation of engineering change proposal to contract(s) (ECP-CON). This table correlates
ECPs to the contracts which they impact, or under which they are submitted. Only current contracts between the
originator and the approval agency for which a CDRL item exists need to be addressed.

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.6.9. Table 258, Part numbers affected by an engineering change proposal (ECP-PART). This table correlates
ECPs to the part numbers affected. Only part numbers identified by a design CAGE (or NSCM) code and number
are included in this table.

a. The combination of the values of design-enterprise-defense-logistics--assigned-identification-code

(DESCAG258), document-alphanumeric-identifier (DOCNUM258), document-type-code (DOCTYP010),
part-product-identifier (PARNUM210), must exist in either Table 053 or Table 104.

b. Fields DESCAG212 inherited from Table 212 and SRCIDN010 inherited from Table 266 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG258).

c. Attribute document-identifier (DOCIDN010) inherited from Table 266 assumes the role document-
alphanumeric-identifier (DOCNUM258).

Code Data Element Title DED Key

DESCAG258 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier

B-118
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK

revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
PARNUM210 part-product-identifier 0024 FK

DOCCRV266 document-current-generic-revision-identifier 0243 FK

DOCNUM258 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
PARLVL258 engineering-change-proposal-document-part-level-code 0121 M

B.5.6.10. Table 259, ECP effectivity of changes (ECP-PROPEFF). This table correlates the ECP with the
proposed effectivity of the ECP for documents and software identified by a CAGE (or NSCM) code and number.

a. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF259).

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF259).

Code Data Element Title DED Key

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
STREFF259 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF259 product-ending-effectivity-sequential-tracking-identifier 0058 FK, O
EFFTIM259 product-change-effectivity-timing-type-code 0028 M

B.5.6.11. Table 260, Locations of items to be retrofit (RETROFIT). This table contains the locations, identity,
and quantity of the units to be retrofit.

a. As key fields, elements geographic-place-name (RETLOC260), ship-asset-identifier (RETSHP260), and

vehicle-asset-identifier (RETVEH260) must be nonblank. However, any one or two of these fields may
have a dash (-) entered to indicate that they do not apply. The product-quantity (QUANTY260) and
product-measurement-unit-code (LOCUOM260) must be nonblank if geographic-place-name
(RETLOC260) is nonblank/nondash; otherwise QUANTY260 and LOCUOM260 must both be blank.

B-119
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

RETLOC260 geographic-place-name 0029 K
RETSHP260 ship-asset-identifier 0031 K
RETVEH260 vehicle-asset-identifier 0031 K
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
STREFF259 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

LOCUOM260 product-measurement-unit-code 0054

QUANTY260 product-quantity 0019
RETCOM260 product-change-retrofit-completion-date 0082

B.5.6.12. Table 261, ECP text file (ECP-EXTTXT). This table identifies the file which contains the extended
text to which the SGML tags in Tables 251 and 289 refer.

a. The combination of file-originator-human-name (FILORG900), electronic-document-file-identifier

Code Data Element Title DED Key

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
FILADD900 enterprise-file-origination-office-address-text 0081 FK, AK1
FILDAT900 electronic-document-file-creation-date 0082 FK, AK1
FILIDN900 electronic-document-file-identifier 0206 FK, AK1
FILORG900 file-originator-human-name 0069 FK, AK1
FILTIM900 electronic-document-file-creation-time 0160 FK, AK1

B-120
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.6.13. Table 262, Engineering change proposal required implementation action(s) (ECPACT). This table
contains the identification of the CCB-directed action items necessary for implementation of an ECP. This allows
CM to monitor their status until completion.

a. Attribute enterprise-identifier (ENTIDN002) inherited from Table 705 assumes the role configuration-
control-board-convening-enterprise-identifier (CCBENT262).

b. Attribute enterprise-office-name (OFFSYM941) inherited from Table 941 assumes the role engineering-
change-implementation-required-action-responsible-enterprise-office-name (RESOFF262).

c. Attribute enterprise-identifier (ENTIDN002) inherited from Table 941 assumes the role engineering-
change-implementation-process-required-action-responsible-enterprise-identifier (RESPON262).

Code Data Element Title DED Key

ECPACT262 engineering-change-implementation-process-action-identifier 0072 K
CCBENT262 configuration-control-board-convening-enterprise-identifier 0052 FK
CCBNAM700 program-configuration-control-board-name 0151 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
PROGNM691 program-name 0059 FK

DOCNUM552 document-alphanumeric-identifier 0003 FK, O

RESOFF262 engineering-change-implementation-required-action- 0044 FK
responsible-enterprise-office-name
RESPON262 engineering-change-implementation-process-required-action- 0052 FK
responsible-enterprise-identifier
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK, O
enterprise-acronym-identification-code
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK
TMNTYP550 technical-manual-document-type-code 0004 FK, O
ACTCOM262 process-action-comment-text 0066
ACTDES262 engineering-change-implementation-process-action-item- 0185 M
description-text
ACTTTL262 process-action-item-title-name 0136 M

B.5.6.14. Table 263, Retrofit maintenance levels (RETRO-LVL). This table identifies the work hours required
for retrofit by various levels of maintenance. If kits are required for retrofit, this table contains the details
associated with the retrofit kits (such as, level of installation and time for installation) which are anticipated at the
time the ECP is submitted.

B-121
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. The value of 'retrofit-maintenance-process-period-work-hour-quantity' (RNRTIM263) and the value of

'retrofit-kit-installation-process-period-work-hour-quantity' (KITTIM263) cannot both be blank in the
same instance.

Code Data Element Title DED Key

RETLVL263 engineering-change-proposal-document-retrofit-installation- 0195 K
level-code
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

ECP450263 retrofit-system-test-process-period-work-hour-quantity 0087 M

ECP480263 predicted-asset-service-period-downtime-days-quantity 0184 M
KITQTY263 product-quantity 0019
KITTIM263 retrofit-kit-installation-process-period-work-hour-quantity 0087
KITTST263 retrofit-kit-test-process-period-work-hour-quantity 0087
RNRTIM263 retrofit-maintenance-process-period-work-hour-quantity 0087

B.5.6.15. Table 264, Status of engineering change proposal implementation action items (ECPACTSTAT).
This table contains the status of the implementation actions identified in Tables 262.

Code Data Element Title DED Key

STACOD264 engineering-change-implementation-process-action- 0021 K
disposition-status-code
STADAT264 engineering-change-implementation-process-action- 0082 K
disposition-status-date
CCBENT262 configuration-control-board-convening-enterprise-identifier 0052 FK
CCBNAM700 program-configuration-control-board-name 0151 FK
ECPACT262 engineering-change-implementation-process-action-identifier 0072 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
PROGNM691 program-name 0059 FK

ACTCOM264 process-action-comment-text 0066

B-122
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.6.16. Table 265, Other impacts of the ECP (ECP-OTHER). This table is used to identify and describe any
factors which are impacted by the ECP and which are not addressed elsewhere.

Code Data Element Title DED Key

IMPNAM265 engineering-change-proposal-document-unusual-effect-name 0263 K
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

SGMUNU265 standard-generalized-markup-language-document-proposed- 0118 M

change-unusual-effect-description-field-identifier

B.5.6.17. Table 266, Correlation of ECP revisions to the document revisions they impact (ECPREV-DOCREV).
This table correlates the ECP revisions to the document(s) and software which are impacted by the ECP revision.
Only documents and software which are identified by a CAGE (or NSCM) code and number are included in this
table.

a. The only allowable values of document-type-code (DOCTYP010) are 'DWG', 'MISC', 'PL', 'P-SPEC',
'SW', and 'SWDOC'.

b. All documents entered in this table and the ECP with which they are associated must have the same
document-current-change-control-authority-entity-identifier in Table 010 at the time of approval of the
ECP.

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 011 assumes the role
document-current-generic-revision-identifier (DOCCRV266).

Code Data Element Title DED Key

DOCCRV266 document-current-generic-revision-identifier 0243 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

SGM330266 standard-generalized-markup-language-document-specific- 0118

proposed-changes-field-identifier

B-123
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.6.18. Tables 267 through 269. Reserved.

B.5.6.19. Table 270, Approved ECPs impacting software (APPRECP-SWVER). This table is a subtype of
Table APPRECP-DOCREV/271 containing the subset of Table 271 consisting of those entries with a document-
type-code (DOCTYP010) of 'SW'. It contains the correlation of approved ECPs to the software which is changed
as a result of the ECP. This table includes the new software version.

a. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG153) inherited from

Table 153 and document-source-entity-identifier (SRCIDN010) inherited from Table 271 must both have
the same value. Therefore they merge and assume the identity design-enterprise-defense-logistics--
assigned-identification-code (DESCAG153).

b. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 153 and document-

identifier (DOCIDN010) inherited from Table 271 must both have the same value. Therefore they merge
and assume the identity document-alphanumeric-identifier (DOCNUM020).

Code Data Element Title DED Key

DESCAG153 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.6.20. Table 271, Correlation of old and new revision identifiers for approved changes to documents
(APPRECP-DOCREV). This table correlates the ECP to the revision of the engineering drawing, program-unique
specification or software against which the ECP was written. Only documents and software identified by a CAGE
(or NSCM) code and number are included in this table.

a. Attribute document-current-generic-revision-identifier (DOCCRV266) inherited from Table 266 assumes

the role document-superseded-alphanumeric-revision-identifier (OLDREV271).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B-124
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK

revision-identifier
OLDREV271 document-superseded-alphanumeric-revision-identifier 0009 FK
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.6.21. Tables 272 through 283. Reserved.

B.5.6.22. Table 284, Effectivity of an approved ECP on an assembly with component materials (APPRECP-
COMPMAT). This table correlates the effectivity of the approved ECP with the assembly-component material
combinations which are impacted by the ECP.

a. The values of document-alphanumeric-identifier (DOCNUM284) and document-type-code (DOCTYP010)

in this table must be the same as the values for the same-named fields in parent Table ECP-PART/258.

b. The value of DOCTYP010 must be either 'DWG' or 'PL'.

c. The value of document-generic-revision-identifier (DOCREV011) must be greater than the value of

document-current-generic-revision-identifier (DOCCRV266) in parent Table ECP-PART/258.

d. Fields DESCAG053 inherited from Table 238, DESCAG258 inherited from Table 258, and SRCIDN010
inherited from Table 271 must be the same. Therefore, they merge and assume the identity design-
enterprise-defense-logistics--assigned-identification-code (DESCAG284).

e. Attribute document-identifier (DOCIDN010) inherited from Table 271 assumes the role document-
alphanumeric-identifier (DOCNUM284).

f. Fields STREFF238 inherited from Table 238 and STREFF259 inherited from Table 259 must be the
same; therefore, they assume the identity product-starting-effectivity-sequential-tracking-identifier
(STREFF284).

Code Data Element Title DED Key

DESCAG284 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT200 design-enterprise-identifier 0052 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
STREFF284 product-starting-effectivity-sequential-tracking-identifier 0058 FK

B-125
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

DOCNUM284 document-alphanumeric-identifier 0003 FK

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier

B.5.6.23. Table 285, Approved ECPs impacting engineering drawings (APPRECP-DWGREV). This table is a
subtype of Table APPRECP-DOCREV/271 containing the subset of Table 271 consisting of a correlation of
approved ECPs to the engineering drawings which are changed as a result of the ECP. This table includes the new
drawing revision letter.

a. The value of document-type-code (DOCTYP010) must be 'DWG'.

b. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG050) inherited from

Table 051 and document-source-entity-identifier (SRCIDN010) inherited from Table 271 must both have
the same value. Therefore they merge and assume the identity design-enterprise-defense-logistics--
assigned-identification-code (DESCAG050).

c. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 051 and

document-generic-revision-identifier (DOCREV011) inherited from Table 271 must both have the same
value. Therefore they merge and assume the identity document-alphanumeric-revision-identifier
(DOCREV051).

d. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

051 and document-identifier (DOCIDN010) inherited from Table 271 must both have the same value.
Therefore they merge and assume the identity engineering-drawing-document-alphanumeric-identifier
(DWGNUM050).

e. Attribute document-type-code (DOCTYP010) inherited from Table 051 and document-type-code

(DOCTYP010) inherited from Table 271 must have the same value and merge to assume the role
engineering-drawing-document-type-code (DWGTYP285).

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
DWGTYP285 engineering-drawing-document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B-126
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.6.24. Table 286, Approved ECPs impacting parts list drawings (APPRECP-PLREV). This table is a
subtype of Table APPRECP-DOCREV/271 containing the subset of Table 271 consisting of a correlation of
approved ECPs to the parts list drawings which are changed as a result of the ECP. This table includes the new
parts list drawing revision letter.

a. The value of document-type-code (DOCTYP010) must be 'PL'.

b. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG050) inherited from

c. Attribute document-alphanumeric-revision-identifier (DOCREV051) inherited from Table 051 and

d. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

e. Attribute document-type-code (DOCTYP010) inherited from Table 051 and document-type-code

(DOCTYP010) inherited from Table 271 must have the same value and merge to assume the role parts-
list-drawing-document-type-code (PLTYPE286).

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
PLTYPE286 parts-list-drawing-document-type-code 0004 FK

B.5.6.25. Table 287, Approved ECPs impacting program specifications (APPRECP-SPECREV). This table is a
subtype of Table APPROVED-DOCREV/271 containing the subset of Table 271 consisting of a correlation of
approved ECPs to the program-unique specifications which are changed as a result of the ECP. This table includes
the new drawing revision letter.

a. The value of document-type-code (DOCTYP010) must be 'SPEC'.

b. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG100) inherited from

Table 101 and document-source-entity-identifier (SRCIDN010) inherited from Table 271 must both have

B-127
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

the same value. Therefore they merge and assume the identity design-enterprise-defense-logistics--
assigned-identification-code (DESCAG100).

c. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 101 and document-

identifier (DOCIDN010) inherited from Table 271 must both have the same value. Therefore they merge
and assume the identity document-alphanumeric-identifier (DOCNUM020).

d. Attribute document-alphanumeric-revision-identifier (DOCREV101) inherited from Table 101 and

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV101 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.6.26. Table 288, Approved ECPs impacting defense specifications (APPRECP-DEFSPECREV). This table
is a subtype of Table APPRECP-DOCREV/271 containing the subset of Table 271 consisting of a correlation of
approved ECPs to the defense specifications which are changed as a result of the ECP. This table includes the new
specification revision identifier.

a. The value of document-type-code (DOCTYP010) must be 'STDDOC'.

b. The combination of values of document-source-organization-identifier (SRCORG024), document-

alphanumeric-identifier (DOCNUM020), and document-type-code (DOCTYP010) inherited from Table
403 must exist in Table 412.

c. Attribute document-identifier (DOCIDN010) inherited from Table 271 and document-alphanumeric-

identifier (DOCNUM020) inherited from Table 403 must both have the same value. Therefore they
merge and assume the identity document-alphanumeric-identifier (DOCNUM020).

d. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 271 and document-

source-organization-identifier (SRCORG024) inherited from Table 403 must both have the same value.
Therefore they merge and assume the identity document-source-organization-identifier (SRCORG024).

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK

B-128
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK

defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SRCORG024 document-source-organization-identifier 0096 FK

B.5.6.27. Table 289, Class I ECPs (CLASS1ECP). This table is a subtype of Table ECPREV/251 which
contains a subset of the revision history of ECPs. It consists of class I ECPs with all the attribute information
associated with a class I ECP (and therefore, the value of engineering-change-proposal-document-change-
classification-code [ECP050251] in Table 251 must have a value of 'I'). This table has two subtypes: ECP-
RETRO/290 and ECP-NORETRO (not shown); there are no special attributes associated with ECP-NORETRO.

a. The product-royalty-expiration-date (ECPROY289) must be non-blank for all values of engineering-

change-proposal-document-justification-code except 'V'.

b. The value of engineering-change-proposal-document-retrofit-contract-authority-need-date (ECP50B289)

must be blank if the value of engineering-change-proposal-product-retrofit-requirement-code
(ECP001289) is 'N'; and must be non-blank if the value is 'Y'.

c. The value of engineering-change-proposal-document-estimated-research-cost-amount (RDTCOS289)

must be nonblank if the value of engineering-change-proposal-document-format-type-code (ECP08E251
in Table 251) is 'P', and must be blank if the value of ECP08E251 (in Table 251) is 'F'.

d. The value of engineering-change-proposal-document-estimated-production-cost-amount (PRDCOS289)

must be blank if the value of engineering-change-proposal-document-format-type-code (ECP08E251 in
table 251) is 'F', and must be nonblank for all other values of ECP08E251.

e. The value of engineering-change-proposal-document-estimated-under-contract-subtotal-cost-amount

(CONCOS289) and engineering-change-proposal-document-estimated-total-cost-amount (TOTCOS289)
must be nonblank if the value of engineering-change-proposal-document-format-type-code (ECP08E251
in Table 251) is 'F', and must be blank for all other values of ECP08E251.

f. If the value of engineering-change-proposal-document-format-type-code (ECP08E251 in Table 251) is

'M', then the vlaue of engineering-change-proposal-document-priority-code (ECP070289) must be either
'U' or 'E'.
Code Data Element Title DED Key
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

CONCOS289 engineering-change-proposal-document-estimated-under- 0172 M

contract-subtotal-cost-amount
ECP060289 engineering-change-proposal-document-justification-code 0165 M

B-129
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ECP070289 engineering-change-proposal-document-priority-code 0166 M

ECP50A289 engineering-change-proposal-document-production-contract- 0082
authority-need-date
ECPROY289 product-royalty-expiration-date 0082
PRDCOS289 engineering-change-proposal-document-estimated- 0172
production-cost-amount
RDTCOS289 engineering-change-proposal-document-estimated-research- 0172
cost-amount
RTROCD289 product-retrofit-requirement-code 0240 M
SGM32E289 standard-generalized-markup-language-document-proposed- 0118
change-software-effect-field-identifier
SGM341289 standard-generalized-markup-language-document-proposed- 0118
change-alternate-solutions-field-identifier
SGM342289 standard-generalized-markup-language-document-proposed- 0118
change-developmental-program-requirements-field-identifier
SGM37A289 standard-generalized-markup-language-document-proposed- 0118
change-performance-effect-field-identifier
SGM37B289 standard-generalized-markup-language-document-proposed- 0118
change-aircraft-weight-balance-stability-effect-field-
identifier
SGM37C289 standard-generalized-markup-language-document-proposed- 0118
change-weight-moment-inertia-effect-field-identifier
SGM37E289 standard-generalized-markup-language-document-proposed- 0118
change-nomenclature-effect-field-identifier
SGM38A289 standard-generalized-markup-language-document-proposed- 0118
change-logistics-support-plan-effect-field-identifier
SGM38B289 standard-generalized-markup-language-document-proposed- 0118
change-maintenance-concept-effect-field-identifier
SGM38D289 standard-generalized-markup-language-document-proposed- 0118
change-interim-support-programs-effect-field-identifier
SGM38E289 standard-generalized-markup-language-document-proposed- 0118
change-spare-repair-parts-effect-field-identifier
SGM38F289 standard-generalized-markup-language-document-proposed- 0118
change-technical-manual-effect-field-identifier
SGM38G289 standard-generalized-markup-language-document-proposed- 0118
change-facilities-effect-field-identifier
SGM38H289 standard-generalized-markup-language-document-proposed- 0118
change-support-equipment-effect-field-identifier
SGM38I289 standard-generalized-markup-language-document-proposed- 0118
change-operator-training-effect-field-identifier
SGM38J289 standard-generalized-markup-language-document-proposed- 0118
change-personnel-effect-field-identifier
SGM38K289 standard-generalized-markup-language-document-proposed- 0118
change-maintenance-training-effect-field-identifier
SGM38M289 standard-generalized-markup-language-document-proposed- 0118
change-contract-maintenance-effect-field-identifier

B-130
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SGM38N289 standard-generalized-markup-language-document-proposed- 0118

change-packaging-handling-storage-transport-effect-field-
identifier
SGM39A289 standard-generalized-markup-language-document-proposed- 0118
change-safety-effect-field-identifier
SGM39B289 standard-generalized-markup-language-document-proposed- 0118
change-survivability-effect-field-identifier
SGM39C289 standard-generalized-markup-language-document-proposed- 0118
change-reliability-effect-field-identifier
SGM39D289 standard-generalized-markup-language-document-proposed- 0118
change-maintainability-effect-field-identifier
SGM39E289 standard-generalized-markup-language-document-proposed- 0118
change-service-life-effect-field-identifier
SGM39F289 standard-generalized-markup-language-document-proposed- 0118
change-operating-procedure-effect-field-identifier
SGM39G289 standard-generalized-markup-language-document-proposed- 0118
change-electromagnetic-interference-effect-field-identifier
SGM39H289 standard-generalized-markup-language-document-proposed- 0118
change-activation-effect-field-identifier
SGM39I289 standard-generalized-markup-language-document-proposed- 0118
change-critical-single-point-failure-item-effect-field-
identifier
SGM39J289 standard-generalized-markup-language-document-proposed- 0118
change-interoperability-effect-field-identifier
SGM40D289 standard-generalized-markup-language-document-proposed- 0118
change-other-software-effect-field-identifier
SGM40E289 standard-generalized-markup-language-document-proposed- 0118
change-rework-other-equipment-effect-field-identifier
SGM40F289 standard-generalized-markup-language-document-proposed- 0118
change-system-test-procedure-effect-field-identifier
SGM40G289 standard-generalized-markup-language-document-proposed- 0118
change-warranty-effect-field-identifier
SGM40H289 standard-generalized-markup-language-document-proposed- 0118
change-parts-control-effect-field-identifier
SGM40I289 standard-generalized-markup-language-document-proposed- 0118
change-life-cycle-cost-effect-field-identifier
SGM40J289 standard-generalized-markup-language-document-proposed- 0118
change-government-furnished-equipment-effect-field-
identifier
TOTCOS289 engineering-change-proposal-document-estimated-total-cost- 0172
amount

B.5.6.28. Table 290, ECP retrofit recommendation and requirements (ECP-RETRO). This table is a subtype of
Table CLASS1ECP/289 and is applicable only if an ECP recommends retrofit of existing, deployed units (that is,
the value of engineering-change-proposal-product-retrofit-code in Table 289 is 'Y'). It contains the pertinent
information on why retrofit is necessary and the detail of what retrofit will entail.

a. If the value of change-proposal-document-contractor-field-service-effect-code (ECP470290) is 'Y', then

the value of standard-generalized-markup-language-document-proposed-change-contractor-field-service-

B-131
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

effect-field-identifier (SGM470290) must be nonblank; if the value of ECP470290 is 'N', then

SGM470290 must be blank.

Code Data Element Title DED Key

ECP470290 change-proposal-document-contractor-field-service-effect- 0180 M

code
ECP50B290 engineering-change-proposal-document-retrofit-contract- 0082 M
authority-need-date
SGM430290 standard-generalized-markup-language-document-retrofit- 0118 M
recommendations-field-identifier
SGM470290 standard-generalized-markup-language-document-proposed- 0118
change-contractor-field-service-effect-field-identifier

B.5.6.29. Table 291, Correlation of ECP to impacted Technical Manuals/Orders (ECP-TECHMAN). This table
correlates a proposed ECP with the Technical manuals/orders which will be impacted upon its approval.

Code Data Element Title DED Key

DOCNUM552 document-alphanumeric-identifier 0003 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.6.30. Table 292, Correlation of approved ECPs to implementing contract modification(s) (APPRECPREV-
CONMOD). This table correlates approved ECPs to the implementing contract modification(s).

Code Data Element Title DED Key

B-132
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK

identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK

STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.6.31. Table 293, Effectivity of an approved ECP on an assembly with component software (APPRECP-
COMPSW). This table correlates the effectivity of the approved ECP with the assembly-component software
combinations which are impacted by the ECP.

a. The values of document-alphanumeric-identifier (DOCNUM293) and document-type-code (DOCTYP010)

in this table must be the same as the values for the same-named fields in parent Table ECP-PART/258.

b. The value of DOCTYP010 must be either 'DWG' or 'PL'.

c. The value of document-generic-revision-identifier (DOCREV011) must be greater than the value of

document-current-generic-revision-identifier (DOCCRV266) in parent Table ECP-PART/258.

d. Fields ADESCG236 inherited from Table 239, DESCAG258 inherited from Table 258, and SRCIDN010
inherited from Table 271 must be the same. Therefore, they merge and assume the identity assembled-
product-design-enterprise-defense-logistics--assigned-identification-code (ADESCG293).

e. Attribute document-identifier (DOCIDN010) inherited from Table 271 assumes the role document-
alphanumeric-identifier (DOCNUM293).

f. Fields STREFF239 inherited from Table 239 and STREFF259 inherited from Table 259 must be the
same; therefore, they assume the identity product-starting-effectivity-sequential-tracking-identifier
(STREFF293).

Code Data Element Title DED Key

ADESCG293 assembled-product-design-enterprise-defense-logistics-- 0001 FK
assigned-identification-code
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
STREFF293 product-starting-effectivity-sequential-tracking-identifier 0058 FK
SWSORC170 software-product-source-entity-identifier 0033 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

DOCNUM293 document-alphanumeric-identifier 0003 FK

B-133
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DOCREV011 document-generic-revision-identifier 0243 FK

DOCTYP010 document-type-code 0004 FK
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
SWIDEN170 software-product-generic-identifier 0060 FK

B.5.6.32. Table 294, ECP approval process status (ECPREVSTAT). This table contains the status of an ECP
revision as it is processed through the approval process by the current document change authority (CDCA) of the
document(s) impacted by the ECP. Although not shown, it can be proven that the series of subtype relationships
between Table GENERIC-DOCREV/011 and this table also exist between Table DOCREVSTAT/850 and this
table. Therefore, this table is a de facto subtype of Table 850, and all the data elements, rules and relationships of
Table 850 also apply.

a. Because this table is a de facto subtype of Table 850, engineering-change-proposal-document-source-

enterprise-defense-logistics--assigned-identification-code (ECPCAG250) inherited from Table 251 is
really a document-source-entity-identifier (SRCIDN010) existing in Table 850.

b. Because this table is a de facto subtype of Table 850, engineering-change-proposal-document-

alphanumeric-identifier (ECPNUM250) inherited from Table 251 is really a document-identifier
(DOCIDN010) existing in Table 850.

c. Because this table is a de facto subtype of Table 850, engineering-change-proposal-document-

alphanumeric-revision-identifier (ECPREV251) inherited from Table 251 is really a document-generic-
revision-identifier (DOCREV011) existing in Table 850.

d. Because this table is a de facto subtype of Table 850, engineering-change-proposal-document-type-code

(ECPTYP250) inherited from Table 251 is really a document-type-code (DOCTYP010) existing in Table
850.

Code Data Element Title DED Key

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.6.33. Table 295, Approved ECPs (ECPREV-APP). This table is one subtype of Table ECPREVSTAT/294
which contains the subset of the contents of Table 294 consisting of those documents which are approved ECPs;
therefore, the value of document-revision-approval-process-disposition-status-code must be 'APP'. Although not
shown, it can be proven that the series of subtype relationships between Table GENERIC-DOCREV/011 and this
table also exist between Table DOCREV-APP/854 and this table. Therefore, Table 295 is a de facto subtype of
Table 854, and all the data elements, rules and relationships of Table 854 apply. Table 295 is singled out in the
data model due to the unique relationships associated with it.

B-134
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. The value of document-revision-approval-process-disposition-status-code (REVSTA850) cannot be 'APP'

unless the value of engineering-change-proposal-document-format-type-code (ECP08E251) in Table 251
is 'F'.

b. Because this table is a de facto subtype of Table 854, engineering-change-proposal-document-source-

enterprise-defense-logistics--assigned-identification-code (ECPCAG250) inherited from Table 294 is
really a document-source-entity-identifier (SRCIDN010) existing in Table 854.

c. Because this table is a de facto subtype of Table 854, engineering-change-proposal-document-

alphanumeric-identifier (ECPNUM250) inherited from Table 294 is really a document-identifier
(DOCIDN010) existing in Table 854.

d. Because this table is a de facto subtype of Table 854, engineering-change-proposal-document-

alphanumeric-revision-identifier (ECPREV251) inherited from Table 294 is really a document-generic-
revision-identifier (DOCREV011) existing in Table 854.

e. Because this table is a de facto subtype of Table 854, engineering-change-proposal-document-type-code

(ECPTYP250) inherited from Table 294 is really a document-type-code (DOCTYP010) existing in Table
854.

Code Data Element Title DED Key

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK, AK1
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK, AK1
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK, AK1
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK, AK1
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.6.34. Tables 296 through 299. Reserved.

B.5.7. Notice of revision. Entity tables numbered in the range of 300 through 324 contain the identification of
notices of revision, their associated attributes, and their relation to engineering change proposals. A NOR is
primarily a military document used to identify specific changes (for example: "change from... to...") which are
required to an engineering drawing or to a program-unique or defense specification. However, most companies
which contract with the U.S. Department of Defense either use this same document internally, or have developed a
similar internal methodology which is part of their internal ECP-equivalent document(s) (contractor format ECP/
NOR equivalent documents are typically called Engineering Change Notices [ECNs], Engineering Change Orders
[ECOs]). This section only addresses the military requirement; therefore, it only includes NORs which are
identified by a CAGE (or NSCM) code and a number. NORs are always an attachment to one ECP and can only
be approved with the ECP (note: a NOR can be disapproved, even if the ECP is approved, but cannot be approved
if the ECP is disapproved). An approved NOR is always associated with the new revision level of the engineering
drawing, program-unique specification or defense specification which is changed as a result of its approval.

B-135
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

The other major portion of this section allows the capture of ECP-proposed changes to an engineering parts list
(integral or separate). If proposed parts list changes are captured here, automated systems can be developed to
incorporate the approved changes into the effective parts list in Figures 05PIN4 and 05PIN5.

The relationships between these various NOR entity tables, NORs and ECP entity tables, and NORs and the
documents changed by them are depicted in Figures 07NOR1 through 07NOR5.

B.5.7.1. Table 300, Notice of revision definition (NOR). This table includes the unique and primary identification
of a Notice of Revision. A NOR is one subtype of Table CAGE-NUM-DOC/022 for the case where document-type-
code in Table 022 has a value of 'NOR'.

a. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 022 assumes the role revision-notice-document-source-enterprise-defense-logistics--
assigned-identification-code (NORCAG300).

b. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 022 assumes the role
revision-notice-document-alphanumeric-identifier (NORNUM300).

c. Attribute document-type-code (DOCTYP010) inherited from Table 022 assumes the role revision-notice-
document-type-code (NORTYP300).

Code Data Element Title DED Key

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK

defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B-136
CAGE-NUM-DOC / 022 (from 1GEN3)
document-source-cage-code
document-alphanumeric-identifier
document-type-code

ECP / 250 (from 6ECP1)

ecp-cage-code
ecp-alphanumeric-identifier
document-type-code
ECP

may have associated

NOR

B-137
APPENDIX B
MIL-STD-2549

NOR / 300
nor-cage-code.document-source-cage-code (FK)
nor-alphanumeric-identifier.document-alphanumeric-identifier (FK)
NOR.document-type-code (FK)
ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
ECP (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 07NOR1
NOTICE OF REVISION (NOR) DEFINITION
CAGE-NUM-DOCREV / 023 (from 1GEN4)
ECPREV / 251 (from 6ECP1) ECPREV-APP / 295 (from 6ECP1)
document-source-cage-code
document-alphanumeric-identifier ecp-cage-code ecp-cage-code
document-type-code ecp-alphanumeric-identifier ecp-alphanumeric-identifier
document-generic-revision ECP ECP
ecp-revision ecp-revision
document-revision-approval-status-code
FILE / 900 (from 23FILE1) document-revision-approval-status-date
file-originator document-type-code
file-originator-office address may have associated
file-identifier NOR
file-creation-date
file-creation-time NORREV / 301 (de facto child of 300) (see 7NOR3)
NORREV-ECPREV / 303
nor-cage-code.document-source-cage-code (FK)
nor-alphanumeric-identifier.document-alphanumeric-identifier (FK) ecp-cage-code (FK)
NOR.document-type-code (FK) is part of ecp-alphanumeric-identifier (FK)
nor-revision.document-generic-revision (FK) ECP (FK)
P ecp-revision (FK)
affected-document-type nor-cage-code (FK)
nor-alphanumeric-identifier (FK)
may be NOR (FK)
extended may have extended text in has
text file for nor-revision (FK)
P

B-138
NORREV-STAT / 308 (de facto subtype of 850)
nor-cage-code (FK)
nor-alphanumeric-identifier (FK)
APPENDIX B
MIL-STD-2549

Z NOR (FK) validates ECP-NOR

nor-revision (FK) iteration combination
NOR-EXTTXT / 314 document-revision-approval-status-code
nor-cage-code (FK) document-revision-approval-status-date
nor-alphanumeric-identifier (FK)
NOR (FK)
nor-revision (FK)
file-originator (FK) document-revision-approval-status-code may include approval of
file-originator-office address (FK)
file-identifier (FK) APV
Z
file-creation-date (FK)
file-creation-time (FK) NORREV-APP / 309 (de facto subtype of 854)
nor-cage-code (FK) (AK1)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

nor-alphanumeric-identifier (FK) (AK1)

NOR (FK) (AK1)
nor-revision (FK) (AK1)
nor-revision-approved-status-code.document-revision-approval-status-code (FK)
nor-revision-approved-status-date.document-revision-approval-status-date (FK)
nor-implementation-authorization-code
ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
ECP (FK)
ecp-revision (FK)
FIGURE 07NOR2 ecp-revision-approved-status-code.document-revision-approval-status-code (FK)
NOR-ECP-CORRELATION (Part 1 of 3) ecp-revision-approved-status-date.document-revision-approval-status-date (FK)
NORREV / 301 (from NOR2) NORREV-DWGREV / 302 (see 7NOR5)
nor-cage-code nor-cage-code (FK) (AK1)
nor-alphanumeric-identifier may propose changes nor-alphanumeric-identifier (FK) (AK1)
NOR to parts list or notes on NOR (FK) (AK1)
nor-revision
Z nor-revision (FK) (AK1)
affected-document-type design-cage-code (FK)
PSPECREV / 101 (from 3SPEC1) drawing-alphanumeric-identifier (FK)
design-cage-code document-type-code (FK)
document-alphanumeric-identifier document-revision (FK)
document-type-code affected-document-type
document-revision
may have changes to notes may have changes to notes
or parts list proposed by or parts list proposed by

Assertion: the relationships between Table 061 and Table 302

P-SPEC and between Table 063 and Table 302 are mutually exclusive
and are dependent on the affected-document-type in Table 302.

ORGSTDDOCREV / 403 (from 11STDS1)

PICDWGREV / 061 (from 2DWG2)
document-source-organization-identifier
document-alphanumeric-identifier design-cage-code
drawing-alphanumeric-identifier PLREV / 063 (from 2DWG2)
document-type-code
potentially document-generic-revision document-type-code design-cage-code
may be document-revision drawing-alphanumeric-identifier

B-139
affected by document-type-code
document-revision
APPENDIX B
MIL-STD-2549

potentially potentially may

may be STDDOC be affected by
affected by PL may potentially
be affected by
DWG

NORREV-SPECREV / 304 NORREV-DEFSPECREV / 305 NORREV-PICDWGREV / 306 NORREV-PLREV / 307

nor-cage-code (FK) nor-cage-code (FK) nor-cage-code (FK) nor-cage-code (FK)
nor-alphanumeric-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

nor-alphanumeric-identifier (FK) nor-alphanumeric-identifier (FK) nor-alphanumeric-identifier (FK)

NOR (FK) NOR (FK) NOR (FK) NOR (FK)
nor-revision (FK) nor-revision (FK) nor-revision (FK) nor-revision (FK)
design-cage-code (FK) document-source-organization-identifier (FK) design-cage-code (FK) design-cage-code (FK)
document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK) drawing-alphanumeric-identifier (FK) drawing-alphanumeric-identifier (FK)
document-type-code (FK) document-type-code (FK) document-type-code (FK) document-type-code (FK)
document-revision (FK) document-generic-revision (FK) document-revision (FK) document-revision (FK)

FIGURE 07NOR3
NOR-ECP-DOCUMENT CORRELATION (ECP/NOR: as prepared) (Part 2 of 3)
NORREV-APP / 309 (from 7NOR2)
APPRECP-PLREV / 286 (from 6ECP3)
APPRECP-DWGREV / 285 (from 6ECP3) nor-cage-code (AK1)
ecp-cage-code
ecp-cage-code nor-alphanumeric-identifier (AK1)
ecp-alphanumeric-identifier
ecp-alphanumeric-identifier NOR (AK1)
ECP
ECP nor-revision (AK1)
design-cage-code
design-cage-code nor-revision-approved-status-code
drawing-alphanumeric-identifier
drawing-alphanumeric-identifier nor-revision-approved-status-date
PL
DWG
ecp-cage-code document-revision
document-revision
ecp-alphanumeric-identifier
ECP
ecp-revision
ecp-revision-approved-status-code APPRECP-SPECREV / 287 (from 6ECP3)
APPRECP-DEFSPECREV / 288 (from 6ECP2)
ecp-revision-approved-status-date ecp-cage-code
ecp-cage-code ecp-alphanumeric-identifier
ecp-alphanumeric-identifier may have changes
ECP
ECP defined by may have changes design-cage-code
document-source-organization-identifier defined by document-alphanumeric-identifier
document-alphanumeric-identifier document-type-code
document-type document-revision
document-revision affected-document-type
(from Table 301)

may have changes

B-140
defined by
may have changes
defined by STDDOC P-SPEC
APPENDIX B
MIL-STD-2549

DWG PL

APPRNORREV-DEFSPECREV / 310 APPRNORREV-PLREV / 312

APPRNORREV-DWGREV / 311 APPNORREV-SPECREV / 313
nor-cage-code (FK) (AK1) nor-cage-code (FK) (AK1)
nor-cage-code (FK) (AK1) nor-cage-code (FK) (AK1)
nor-alphanumeric-identifier (FK) (AK1) nor-alphanumeric-identifier (FK) (AK1)
nor-alphanumeric-identifier (FK) (AK1) nor-alphanumeric-identifier (FK) (AK1)
NOR (FK) (AK1) NOR (FK) (AK1)
NOR (FK) (AK1) NOR (FK) (AK1)
nor-revision (FK) (AK1) nor-revision (FK) (AK1)
nor-revision (FK) (AK1) nor-revision (FK) (AK1)
nor-revision-approved-status-code (FK) nor-revision-approved-status-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

nor-revision-approved-status-code (FK) nor-revision-approved-status-code (FK)

nor-revision-approved-status-date (FK) nor-revision-approved-status-date (FK)
nor-revision-approved-status-date (FK) nor-revision-approved-status-date (FK)
ecp-cage-code (FK) ecp-cage-code (FK)
ecp-cage-code (FK) ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK) ecp-alphanumeric-identifier (FK)
ecp-alphanumeric-identifier (FK) ecp-alphanumeric-identifier (FK)
ECP (FK) ECP (FK)
ECP (FK) ECP (FK)
document-source-organization-identifier (FK) design-cage-code (FK)
design-cage-code (FK) design-cage-code (FK)
document-alphanumeric-identifier (FK) drawing-alphanumeric-identifier (FK)
drawing-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
document-type (FK) PL (FK)
DWG (FK) document-type-code (FK)
document-revision (FK) document-revision (FK)
document-revision (FK) document-revision (FK)
FIGURE 07NOR4
NOR-ECP-DOCUMENT CORRELATION (Part 3 of 3)
(ECP/NOR: as approved)
NOR-DWGREVPIN / 317 NORREV-DWGREV / 302 (from 7NOR3) NOR-DWGNOTE / 325 NOR-NOTESPECITEM / 327
nor-cage-code (FK) nor-cage-code may add, nor-cage-code (FK) nor-cage-code (FK)
nor-alphanumeric-identifier (FK) nor-alphanumeric-identifier change or delete nor-alphanumeric-identifier (FK) nor-alphanumeric-identifier (FK)
NOR (FK) NOR NOR (FK) NOR (FK)
may
nor-revision (FK) nor-revision may nor-revision (FK) nor-revision (FK)
define may have
design-cage-code (FK) design-cage-code add, design-cage-code (FK) design-cage-code (FK)
part-identifier drawing-alphanumeric-identifier change drawing-alphanumeric-identifier (FK) drawing-alphanumeric-identifier (FK)
or delete drawing-note-number may be drawing-note-number (FK)
drawing-alphanumeric-identifier (FK) document-type-code
called drawing-special-condition-code
document-revision
may be assembled out by
or made from NOR-DWGREVFIND / 315
NOR-DWGPLNOTE / 326
nor-cage-code (FK)
NOR-DWGREVPLITEM / 316 nor-cage-code (FK)
nor-alphanumeric-identifier (FK)
nor-cage-code (FK) identifies the primary NOR (FK) nor-alphanumeric-identifier (FK)
nor-alphanumeric-identifier (FK) or preferred part nor-revision (FK) may refer to NOR (FK)
NOR (FK) design-cage-code (FK) nor-revision (FK)
Z design-cage-code (FK)
nor-revision (FK) drawing-alphanumeric-identifier (FK)
design-cage-code (FK) find-identifier drawing-alphanumeric-identifier (FK)
may identify an
assembly-drawing-alphanumeric-identifier.drawing-alphanumeric-identifier (FK) find-identifier (FK)
alternate part
pl-entry-sequence-number drawing-note-number (FK)
find-identifier (FK) may have assembly may have
CINOMEN / 690 (from 19CI1) location designated by
component-type-code
ci-nomenclature NOR-FINDSPECITEM / 324
primary-alternate-flag
NOR-REFDES / 323 nor-cage-code (FK)
may be assembled or made into nor-alphanumeric-identifier (FK)
nor-cage-code (FK) NOR (FK)
NOR-DASHPLITEM / 318 nor-alphanumeric-identifier (FK) nor-revision (FK)
component-type-code NOR (FK) design-cage-code (FK)
nor-cage-code (FK) nor-revision (FK)
nor-alphanumeric-identifier (FK) drawing-alphanumeric-identifier (FK)
reference-designator (AK1)

B-141
may have component find-identifier (FK)
NOR (FK)
locations designated by ci-nomenclature (FK) drawing-special-condition-code
nor-revision (FK)
APPENDIX B

design-cage-code (FK) design-cage-code (FK) (AK1)

MIL-STD-2549

assembly-drawing-alphanumeric-identifier (FK) P drawing-alphanumeric-identifier (FK) (AK1)

part-identifier (FK) find-identifier (FK) (AK1)
find-identifier (FK) M D
pl-entry-sequence-number (FK)
S
component-quantity
NOR-COMPDOC / 322
unit-of-measure NOR-COMPMAT / 320
NOR-COMPSW / 321 nor-cage-code (FK)
NOR-COMPPIN / 319 nor-cage-code (FK) nor-alphanumeric-identifier (FK)
nor-cage-code (FK)
nor-alphanumeric-identifier (FK) NOR (FK)
nor-cage-code (FK) nor-alphanumeric-identifier (FK)
NOR (FK) nor-revision (FK)
nor-alphanumeric-identifier (FK) NOR (FK)
nor-revision (FK) design-cage-code (FK)
NOR (FK) nor-revision (FK)
design-cage-code (FK) assembly-drawing-alphanumeric-identifier (FK)
nor-revision (FK) design-cage-code (FK)
assembly-drawing-alphanumeric-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

design-cage-code (FK) assembly-drawing-alphanumeric-identifier (FK) find-identifier (FK)

find-identifier (FK) pl-entry-sequence-number (FK)
assembly-drawing-alphanumeric-identifier (FK) find-identifier (FK)
pl-entry-sequence-number (FK)
find-identifier (FK) pl-entry-sequence-number (FK)
document-source-entity-identifier (FK)
pl-entry-sequence-number (FK) design-enterprise-identifier (FK) document-identifier (FK)
software-source-identifier (FK)
material-generic-identifier (FK) document-type-code (FK)
design-enterprise-identifier (FK) software-generic-identifier (FK)
material-identification (FK)
part-identifier (FK) may be called out by
may be called out by may be called out by
may be called out by
GENERIC-DOCUMENT / 010 (from 1GEN2)
GENERIC-MATID / 200 (from 5PIN1)
GENERIC-PIN / 210 (from 5PIN2) GENERIC-SWPROD / 170 (from 4SW3) document-source-entity-identifier
design-enterprise-identifier
software-source-identifier document-identifier
FIGURE 07NOR5 design-enterprise-identifier material-generic-identifier
software-generic-identifier document-type-code
PROPOSED PARTS LIST STRUCTURE part-identifier material-identification
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.7.2. Table 301, Notice of revision revisions (NORREV). This table is one subtype of Table CAGE-NUM-
DOCREV/023 for the case where the value of document-type-code (DOCTYP010) in Table 023 is 'NOR'. It
contains the revision history of the NOR during its life cycle. This table has four subtypes: NORREV-SPECREV/
304, NORREV-MILSPEC/305, NORREV-DWGREV/306, and NORREV-PLREV/307.

a. Due to parallel categorization, this table is a de facto child of Table NOR/300.

b. Because this table is a de facto child of Table 300, document-source-enterprise-defense-logistics--

assigned-identification-code (SRCCAG022) inherited from Table 023 is really a revision-notice-
document-source-enterprise-defense-logistics--assigned-identification-code (NORCAG300) existing in
Table 300. Therefore, SRCCAG022 assumes the identity NORCAG300.

c. Because this table is a de facto child of Table 300, document-alphanumeric-identifier (DOCNUM020)

inherited from Table 023 is really a revision-notice-document-alphanumeric-identifier (NORNUM300)
existing in Table 300. Therefore, DOCNUM020 assumes the identity NORNUM300.

d. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 023 assumes the role
revision-notice-document-alphanumeric-revision-identifier (NORREV301).

e. Because this table is a de facto child of Table 300, document-type-code (DOCTYP010) inherited from
Table 023 is really a revision-notice-document-type-code (NORTYP300) existing in Table 300.
Therefore, DOCTYP010 assumes the identity NORTYP300.

Code Data Element Title DED Key

ADOCTY301 affected-document-type-code 0004 M

SGMCHG301 standard-generalized-markup-language-document-specific- 0118
proposed-changes-field-identifier

B.5.7.3. Table 302, Correlation of NOR to drawing with parts list and/or note changes (NORREV-DWGREV).
This table correlates a NOR revision to either a parts list drawing or a graphical drawing with an integral parts list.
It is used only when the NOR is proposing changes to the notes on the drawing or to the parts list contents and
these changes need to be captured discretely to allow for automated update of the drawing upon approval.

a. The document-type-code (DOCTYP010) inherited from either Table PICDWGREV/061 or PLREV/063

must be either 'DWG' or 'PL' and must be the same as the affected-document-type-code (ADOCTY301) in
Table 301.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

B-142
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK, AK1

logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK, AK1
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK, AK1
NORTYP300 revision-notice-document-type-code 0004 FK, AK1

DOCREV051 document-alphanumeric-revision-identifier 0009 FK

DOCTYP010 document-type-code 0004 FK

B.5.7.4. Table 303, Correlation of notice of revision revisions to engineering change proposal revisions
(NORREV-ECPREV). This table correlates ECP revisions with NOR revisions.

a. For each instance in this table, the values of the combination of the engineering-change-proposal-
document-source-enterprise-defense-logistics--assigned-identification-code (ECPCAG250) and the
engineering-change-proposal-document-alphanumeric-identifier (ECPNUM250) in this table must be the
same as the values of the same-named fields in Table 300 for the parent instance (combination of revision-
notice-document-source-enterprise-defense-logistics--assigned-identification-code [NORCAG300] and
revision-notice-document-alphanumeric-identifier [NORNUM300]).

Code Data Element Title DED Key

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORTYP300 revision-notice-document-type-code 0004 FK

NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK

B.5.7.5. Table 304, Correlation of a NOR revision to the program specification which it impacts (NORREV-
SPECREV). This table is a subtype of Table NORREV/301 which contains the subset of NORs which includes
only those NOR revisions which propose changing program-unique specifications (and, therefore, the value of
affected-document-type-code [ADOCTY301] in Table 301 must be 'SPEC'). It correlates the NOR revision to the
program-unique specification revision which it is proposing to change.

a. There must be at least one common entry in Table 303 for the combination of the values of engineering-
change-proposal-document-source-enterprise-defense--logistics--assigned-identification-code
(ECPCAG250), engineering-change-proposal-document-alphanumeric-identifier (ECPNUM250),
engineering-change-proposal-document-revision-identifier (ECPREV251), revision-notice-document-
source-enterprise-defense-logistics--assigned-identification-code (NORCAG300), revision-notice-
document-alphanumeric-identifier (NORNUM300), and revision-notice-document-revision-identifier

B-143
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

(NORREV301) when traced through the path Table 304 to Table 301 to Table 303 and through the path
Table 304 to Table 101 to Table 266 to Table 251 to Table 303.

b. For each instance in this table, the value of document-current-change-control-authority-identifier

(CCCENT010) in Table 010 must be the same for both the NOR (NORCAG300 + NORNUM300 +
NORTYP300) and the program-unique specification (DESCAG100 + DOCNUM020 + DOCTYP010) it is
proposing to change.

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK

code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV101 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK

B.5.7.6. Table 305, Correlation of NOR revision to the defense specification which it impacts (NORREV-
DEFSPECREV). This table is a subtype of Table NORREV/301 which contains the subset of NORs which
includes only those NOR revisions which propose changing defense specifications (and, therefore, the value of
affected-document-type-code [ADOCTY301] in Table 301 must be 'STDDOC'). It correlates the NOR revision to
the defense specification revision which it is proposing to change.

a. There must be at least one common entry in Table 303 for the combination of the values of engineering-
change-proposal-document-source-enterprise-defense-logistics--assigned-identification-code
(ECPCAG250), engineering-change-proposal-document-alphanumeric-identifier (ECPNUM250),
engineering-change-proposal-document-revision-identifier (ECPREV251), revision-notice-document-
source-enterprise-defense-logistics--assigned-identification-code (NORCAG300), revision-notice-
document-alphanumeric-identifier (NORNUM300), and revision-notice-document-revision-identifier
(NORREV301) when traced through the path Table 307 to Table 301 to Table 303 and through the path
Table 307 to Table 066 to Table 051 to Table 266 to Table 251 to Table 303.

b. The combination of values of document-source-organization-identifier (SRCORG024), document-

alphanumeric-identifier (DOCNUM020), and document-type-code (DOCTYP010) inherited from Table
403 must exist in Table 412.

c. For each instance in this table, the value of document-current-change-control-authority-identifier

(CCCENT010) in Table 010 must be the same for both the NOR (NORCAG300 + NORNUM300 +
NORTYP300) and the defense specification (SRCORG024 + DOCNUM020 + DOCTYP010) it is
proposing to change.

B-144
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCORG024 document-source-organization-identifier 0096 FK

B.5.7.7. Table 306, Correlation of NOR revision to the engineering drawing which it impacts (NORREV-
DWGREV). This table is a subtype of Table NORREV/301 which contains the subset of NORs which includes
only those NOR revisions which propose changing engineering drawings (and, therefore, the value of affected-
document-type-code [ADOCTY301] in Table 301 must be 'DWG'). It correlates the NOR revision to the
engineering drawing revision which it is proposing to change.

a. There must be at least one common entry in Table 303 for the combination of the values of engineering-
change-proposal-document-source-enterprise-defense-logistics--assigned-identification-code
(ECPCAG250), engineering-change-proposal-document-alphanumeric-identifier (ECPNUM250),
engineering-change-proposal-document-revision-identifier (ECPREV251), revision-notice-document-
source-enterprise-defense-logistics--assigned-identification-code (NORCAG300), revision-notice-
document-alphanumeric-identifier (NORNUM300), and revision-notice-document-revision-identifier
(NORREV301) when traced through the path Table 306 to Table 301 to Table 303 and through the path
Table 306 to Table 065 to Table 051 to Table 266 to Table 251 to Table 303.

b. For each instance in this table, the value of document-current-change-control-authority-identifier

(CCCENT010) in Table 010 must be the same for both the NOR (NORCAG300 + NORNUM300 +
NORTYP300) and the engineering drawing (DESCAG050 + DWGNUM050 + DOCTYP010) it is
proposing to change.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK

code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

B-145
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.7.8. Table 307, Correlation of NOR revision to the parts list drawing it impacts (NORREV-PLREV). This
table is a subtype of Table NORREV/301 which contains the subset of NORs which includes only those NOR
revisions which propose changing parts list drawing (and, therefore, the value of affected-document-type-code
[ADOCTY301] in Table 301 must be 'PL'). It correlates the NOR revision to the parts list drawing revision which
it is proposing to change.

b. For each instance in this table, the value of document-current-change-control-authority-identifier

(CCCENT010) in Table 010 must be the same for both the NOR (NORCAG300 + NORNUM300 +
NORTYP300) and the parts list drawing (DESCAG100 + DOCNUM020 + DOCTYP010) it is proposing
to change.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK

code
DOCREV051 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

B.5.7.9. Table 308, NOR approval process status (NORREVSTAT). This table contains the status of a NOR
revision as it is processed through the approval process by the CDCA of the document(s) impacted by the ECP with
which it is associated. Although not shown, it can be proven that the series of subtype relationships between Table
GENERIC-DOCREV/011 and this table also exist between Table DOCREVSTAT/850 and this table. Therefore,
Table 308 is a de facto subtype of Table 850, and all the data elements, rules, and relationships of Table 850 apply.

a. Because this table is a de facto subtype of Table 850, revision-notice-document-source-enterprise-defense-

logistics--assigned-identification-code (NORCAG300) inherited from Table 301 is really a document-
source-entity-identifier (SRCIDN010) existing in Table 850.

b. Because this table is a de facto subtype of Table 850, revision-notice-document-alphanumeric-identifier

(NORNUM300) inherited from Table 301 is really a document-identifier (DOCIDN010) existing in Table
850.

B-146
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Because this table is a de facto subtype of Table 850, revision-notice-document-alphanumeric-revision-

identifier (NORREV301) inherited from Table 301 is really a document-generic-revision-identifier
(DOCREV011) existing in Table 850.

d. Because this table is a de facto subtype of Table 850, revision-notice-document-type-code (NORTYP300)

inherited from Table 301 is really a document-type-code (DOCTYP010) existing in Table 850.

Code Data Element Title DED Key

NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.7.10. Table 309, Approved NORs (NORREV-APP). This table is one subtype of NORREVSTAT/308
which contains the subset of the contents of Table 308 consisting of those documents which are approved NORs;
therefore, the value of revision-notice-document-revision-approval-process-disposition-status-code must be 'APP'.
Although not shown, it can be proven that the series of subtype relationships between Table GENERIC-DOCREV/
011 and this table also exist between Table DOCREV-APP/854 and this table. Therefore, Table 309 is a de facto
subtype of Table 854, and all the data elements, rules and relationships of Table 854 apply (revision-notice-
document-source-enterprise defense-logistics--assigned identification-code [NORCAG300], revision-notice-
document-alphanumeric-identifier [NORNUM300], and revision-notice-document-type-code [NORTYP300]
inherited from Tables 303 and 308, and revision-notice-document-alphanumeric-revision-identifier [NORREV301]
inherited from Table 308 are one case of a document-source-entity-identifier [SRCIDN010], document-identifier
[DOCIDN010], document-type-code [DOCTYP010], and document-generic-revision-identifier [DOCREV011],
respectively, in Table 854). This table is singled out in the data model due to the unique relationships associated
with it.

a. The revision-notice-document-implementation-authorization-code (IMPCOD309) indicates the decision

by the CDCA in its role as a tasking activity as to whether or not its performing activities may use the
NOR prior to incorporation of the NOR into the document (see also, Table 863).

b. Attribute document-revision-approval-process-disposition-status-date (STADAT850) inherited from Table

295 assumes the role engineering-change-proposal-document-revision-approval-process-approval-
disposition-status-date (ECPDAT309).

c. Attribute document-revision-approval-process-disposition-status-code (REVSTA850) inherited from Table

295 assumes the role engineering-change-proposal-document-revision-approval-process-approved-
disposition-status-code (ECPSTA309).

d. Because this table is a de facto subtype of Table 854, the value of document-revision-approval-process-
disposition-status-date (STADAT850) inherited from Table 308 must exist as a document-revision-
approval-process-disposition-status-date (STADAT850) in Table 854. STADAT850 assumes the role
revision-notice-document-revision-approval-process-approved-disposition-status-date (NORDAT309).

B-147
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

e. Because this table is a de facto subtype of Table 854, revision-notice-document-alphanumeric-revision-

identifier (NORREV301) inherited from Table 308 is really a document-generic-revision-identifier
(DOCREV011) existing in Table 854.

f. Because this table is a de facto subtype of Table 854, the value of document-revision-approval-process-
disposition-status-code (REVSTA850) inherited from Table 308 must exist as a document-revision-
approval-process-disposition-status-code (REVSTA850) in Table 854. REVSTA850 assumes the role
revision-notice-document-revision-approval-process-approved-disposition-status-code (NORSTA309).

Code Data Element Title DED Key

NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK, AK1
logistics--assigned-identification-code
NORDAT309 revision-notice-document-revision-approval-process- 0082 FK
approved-disposition-status-date
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK, AK1
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK, AK1
NORSTA309 revision-notice-document-revision-approval-process- 0021 FK
approved-disposition-status-code
NORTYP300 revision-notice-document-type-code 0004 FK, AK1

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK

defense-logistics--assigned-identification-code
ECPDAT309 engineering-change-proposal-document-revision-approval- 0082 FK
process-approval-disposition-status-date
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPSTA309 engineering-change-proposal-document-revision-approval- 0021 FK
process-approved-disposition-status-code
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
IMPCOD309 revision-notice-document-implementation-authorization-code 0176 M

B.5.7.11. Table 310, Correlation of approved NOR with defense specification new revision (APPNORREV-
DEFSPECREV). This table is a subtype of Table NORREV-APP/309 which contains the subset of approved NORs
which includes only those NOR revisions which have been approved, are associated with an approved ECP, and
propose changing defense specifications (and, therefore, the value of affected-document-type-code [ADOCTY301]
in Table 301 must be 'STDDOC'). It correlates the NOR revision to the defense specification revision which is
assigned as a result of this approved change.

a. The combination of values of engineering-change-proposal-document-source-enterprise-defense-logistics--

B.5.7.14. Table 313, Correlation of approved NOR with program specification new revision (APPNORREV-
SPECREV). This table is a subtype of Table NORREV-APP/309 which contains the subset of approved NORs
which includes only those NOR revisions which have been approved, are associated with an approved ECP, and
propose changing program-unique specifications (and therefore, the value of affected-document-type-code
[ADOCTY301] in Table 301 must be 'SPEC'). It correlates the NOR revision to the program-unique specification
revision which is assigned as a result of this approved change.

a. The combination of the values of engineering-change-proposal-document-source-enterprise-defense-

logistics--assigned-identification-code (ECPCAG250), engineering-change-proposal-document-
alphanumeric-identifier (ECPNUM250), and engineering-change-proposal-document-type-code
(ECPTYP251) must be the same as in Table 309.

b. Due to parallel categorization, the combination of the values of design-enterprise-defense-logistics--

assigned-identification-code (DESCAG100), document-alphanumeric-identifier (DOCNUM020), and
document-type-code (DOCTYP010) must be the same as the same fields in Table 304 for this combination
of the values of revision-notice-document-source-enterprise-defense-logistics--assigned-identification
(NORCAG300), revision-notice-document-alphanumeric-identifier (NORNUM300), and revision-notice-
document-type-code (NORTYP300).

B-151
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

former value is the revision level of the program-unique specification as the result of approval of this
ECP/NOR, and the latter value is the revision level of the program-unique specification before the change
is approved.

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK

code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV101 document-alphanumeric-revision-identifier 0009 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.7.15. Table 314, NOR text file (NOR-EXTTXT). This table identifies the file which contains the extended
text to which the SGML tags in Table 301 refer.

a. The combination of file-originator-human-name (FILORG900), electronic-document-file-identifier

(FILIDN900) and enterprise-file-origination-office-address-text (FILADD900) can be associated with only
one combination of revision-notice-document-source-enterprise-defense-logistics--assigned-identification-
code (NORCAG300), revision-notice-proposal-document-alphanumeric-identifier (NORNUM300), and
revision-notice-proposal-document-alphanumeric-revision-identifier (NORREV251).

Code Data Element Title DED Key

FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILIDN900 electronic-document-file-identifier 0206 FK
FILORG900 file-originator-human-name 0069 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK

FILDAT900 electronic-document-file-creation-date 0082 FK

FILTIM900 electronic-document-file-creation-time 0160 FK

B-152
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.7.16. Table 315, Proposed changes to find numbers (NOR-DWGREVFIND). This table identifies additions
deletions of find numbers from an integral or separate parts list.

a. The value of engineering-drawing-document-proposed-entry-change-type (CHGTYPE315) must be 'A',

'D', or 'N'.

b. If the value of the CHGTYP315 is 'D' or 'N', the combination of values of design-enterprise-defense-
logistics--assigned-identification-code (DESCAG050), engineering-drawing-document-alphanumeric-
identifier (DWGNUM050), document-type-code (DOCTYP010 in parent instance in Table 302),
document-alphanumeric-revision-identifier (DOCREV051 in parent instance in Table 302), and parts-list-
document-item-identifier (FINDID315) must exist in the corresponding fields in an instance in Table 219.

Code Data Element Title DED Key

FINDID315 parts-list-document-item-identifier 0027 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK

CHGTYP315 engineering-drawing-document-proposed-entry-change-type- 0260 M

code

B.5.7.17. Table 316, Proposed changes to parts list line items (NOR-DWGREVPLITEM). This table contains
the proposed additions, deletions and changes of part list line items.

a. The value of the engineering-drawing-document-proposed-entry-change-type-code (CHGTYP316) must

be 'A', 'C', or 'D' only. (The value 'C' addresses changes either in this table, or in one of the four
component subtype tables.)

b. If the value of CHGTYP316 is 'C' or 'D', then the combination of values of design-enterprise-defense-
logistics--assigned-identification-code (DESCAG050), assembly-engineering-drawing-document-
identifier (ASSYNO316), document-type-code (DOCTYP010 in parent instance of Table 302), document-
alphanumeric-revision-identifier (DOCREV051 in parent instance of Table 302), parts-list-document-
item-identifier (FINDID315), and document-parts-list-entry-sequence-identifier (PLSEQN316) must exist
in the corresponding fields in an instance in Table 224.

c. Attribute engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table

302 and engineering-drawing-document-alphanumeric-identifier (DWGNUM050) inherited from Table
315 must have the same value and merge to assume the role assembly-engineering-drawing-document-
alphanumeric-identifier (ASSYNO316).

B-153
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

PLSEQN316 document-parts-list-entry-sequence-identifier 0259 K
ASSYNO316 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
FINDID315 parts-list-document-item-identifier 0027 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK

ALTFLG316 document-parts-list-entry-priority-indicator-code 0258 M

CHGTYP316 engineering-drawing-document-proposed-entry-change-type- 0260 M
code
COMPTY316 document-parts-list-entry-component-type-code 0241 M

B.5.7.18. Table 317, Proposed changes to defined parts (NOR-DWGREVPIN). This table identifies the
proposed changes to parts defined by this drawing.

a. The value of engineering-drawing-document-proposed-entry-change-type-code (CHGTYP317) must be

'A', 'D', or 'N'.

b. If the value of CHGTYP317 is 'D' or 'N', then the combination of values of design-commercial-
government-enterprise-identification-code (DESCAG050), part-product-identifier (PARNUM317), and
document-alphanumeric-revision-identifier (DOCREV051 in the parent instance in Table 302) must exist
in the corresponding fields in an instance in Table 054.

Code Data Element Title DED Key

PARNUM317 part-product-identifier 0024 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK

DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

CHGTYP317 engineering-drawing-document-proposed-change-type-code 0261 M

B-154
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.7.19. Table 318, Proposed changes to component quantities (NOR-DASHPLITEM). This table identifies
proposed changes to the part list line item entry quantities and/or units of measure as they apply to a specific part
number (dash number).

a. The value of the engineering-drawing-document-proposed-entry-change-type-code (CHGTYP318) must

be 'A', 'C', or 'D'.

b. If the value of the CHGTYP318 is 'C' or 'D', then the combination of values of design-enterprise-defense-
logistics--assigned-identification-code (DESCAG050), assembly-engineering-drawing-document-
identifier (ASSYNO316), part-product-identifier (PARNUM217), parts-list-document-item-identifier
(FINDID315), document-parts-list-entry-sequence-identifier (PLSEQN316), and document-alphanumeric-
revision-identifier (DOCREV051 in parent instance of Table 302) must exist in the corresponding fields
in an instance in Table 225.

c. For any instance in this table, if the combination of the values of design-enterprise-defense-logistics--
assigned-identification-code (DESCAG050) and part-product-identifier (PARNUM317) is the same as the
combination of values of design-enterprise-identifier (DESENT210) and part-product-identifier
(PARNUM210) in the subtype of the parent instance in Table 319, then the value of the assembly-part-
component-quantity (QUANTY318) must be zero (0). (This rule is necessary to enforce the requirement
that indentured parts lists form directed acyclic graphs.)

d. If the value of document-parts-list-entry-component-type-code (COMPTY316) in Table 316 is 'P' or 'M',

the value of QUANTY318 must be nonblank; if the value of COMPTY316 in Table 316 is 'S' or 'D', the
value of QUANTY318 must be blank.

e. If the value of QUANTY318 is nonblank and non-zero, the value of product-measurement-unit-code

(UOMCOD318) must be nonblank; if the value of QUANTY318 is blank or zero (0), the value of
UOMCOD318 must be blank.

Code Data Element Title DED Key

ASSYNO316 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
FINDID315 parts-list-document-item-identifier 0027 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK
PARNUM317 part-product-identifier 0024 FK
PLSEQN316 document-parts-list-entry-sequence-identifier 0259 FK

CHGTYP318 engineering-drawing-document-proposed-entry-change-type- 0260 M

code
QUANTY318 assembly-part-component-quantity 0053
UOMCOD318 product-measurement-unit-code 0054

B-155
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.7.20. Table 319, Proposed changes of component parts (NOR-COMPPIN). This table is a subtype of Table
NOR-DWGREVPLITEM/316 which proposes a change in the correlation of a parts list line item with a component
part number.

a. If the value of CHGTYP316 in Table 316 is 'D', then the combination of values of design-enterprise-
defense-logistics--assigned-identification-code (DESCAG050), assembly-engineering-drawing-document-
alphanumeric-identifier (ASSYNO316), parts-list-document-item-identifier (FINDID315), and document-
parts-list-entry-sequence-identifier (PLSEQN316) must exist in the corresponding fields in an instance in
Table 220.

Code Data Element Title DED Key

ASSYNO316 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
FINDID315 parts-list-document-item-identifier 0027 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK
PLSEQN316 document-parts-list-entry-sequence-identifier 0259 FK

DESENT210 design-enterprise-identifier 0052 FK

PARNUM210 part-product-identifier 0024 FK

B.5.7.21. Table 320, Proposed changes of component materials (NOR-COMPMAT). This table is a subtype of
Table ECP-DWGREVPLITEM/316 which proposes a change in the correlation of a parts list line item with a
component material (not identified by a part number).

Code Data Element Title DED Key

B-156
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

PLSEQN316 document-parts-list-entry-sequence-identifier 0259 FK

DESENT200 design-enterprise-identifier 0052 FK

MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK

B.5.7.22. Table 321, Proposed changes of component software (NOR-COMPSW). This table is a subtype of
Table ECP-DWGREVPLITEM/316 which proposes a change in the correlation of a parts list line item with a
component software.

Code Data Element Title DED Key

ASSYNO316 assembly-engineering-drawing-document-alphanumeric- 0003 FK
identifier
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
FINDID315 parts-list-document-item-identifier 0027 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK
PLSEQN316 document-parts-list-entry-sequence-identifier 0259 FK

SWIDEN170 software-product-generic-identifier 0060 FK

SWSORC170 software-product-source-entity-identifier 0033 FK

B.5.7.23. Table 322, Proposed changes of component documents (NOR-COMPDOC). This table is a subtype of
Table ECP-DWGREVPLITEM/316 which proposes a change in the correlation of a parts list line item with a
component document number.

b. For any instance in this table, the combination of the values of document-source-entity-identifier
(SRCIDN010), document-identifier (DOCIDN010), and document-type-code (DOCTYP010) cannot be
the same as the combination of the values of design-enterprise-defense-logistics--assigned-identification-
code (DESCAG050), assembly-engineering-drawing-document-alphanumeric-identifier (ASSYNO316),

B-157
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

and document-type-code (DOCTYP010 in the parent instance in Table 302). (This rule is necessary to
enforce the requirement that indentured parts lists form directed acyclic graphs.)

Code Data Element Title DED Key

FINDID315 parts-list-document-item-identifier 0027 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK
PLSEQN316 document-parts-list-entry-sequence-identifier 0259 FK

DOCIDN010 document-identifier 0122 FK

DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.7.24. Table 323, Proposed changes of reference designators (NOR-REFDES). This table identifies
proposed changes to reference designators and correlates them to the parts list find.

a. If the value of the engineering-drawing-document-proposed-change-type-code (CHGTYP323) is 'D', then

the combination of values of configuration-item-product-nomenclature-text (CINOMN690) and part-
location-place-identifier (REFDES323) must exist in the corresponding fields in an instance in Table 208.

Code Data Element Title DED Key

REFDES323 place-reference-designator-identifier 0055 K
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK

CINOMN690 configuration-item-product-nomenclature-text 0047 FK

B.5.7.25. Table 324, Proposed changes of special item indicators in a parts list (NOR-FINDSPECITEM). This
table identifies proposed changes to special item indicators on a part list find.

a. If the value of the engineering-drawing-document-proposed-change-type-code (CHGTYP324) is 'D', the

combination of values of design-enterprise-defense-logistics--assigned-identification-code (DESCAG050),
assembly-engineering-drawing-document-alphanumeric-identifier (ASSYNO316), document-
alphanumeric-revision-identifier (DOCREV051 in the parent instance in Table 302), parts-list-document-

B-158
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

item-identifier (FINDID315), document-parts-list-entry-sequence-identifier (PLSEQN316), and

engineering-drawing-document-special-condition-code (SPNOTE324) must exist in the corresponding
fields in an instance in Table 227.

Code Data Element Title DED Key

SPNOTE324 engineering-drawing-document-special-condition-code 0257 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
FINDID315 parts-list-document-item-identifier 0027 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK

CHGTYP324 engineering-drawing-document-proposed-change-type-code 0261 M

B.5.7.26. Table 325, Proposed changes to drawing notes (NOR-DWGNOTE). This table contains the proposed
changes to notes in a drawing or parts list drawing.

a. If the value of engineering-drawing-document-proposed-entry-change-type-code (CHGTYP325) is 'C', 'D',

or 'N', then the combination of the values of design-enterprise-defense-logistics--assigned-identification-
code (DESCAG050), engineering-drawing-document-alphanumeric-identifier (DWGNUM050),
document-type-code (DOCTYP010 in the parent instance in Table 302), document-alphanumeric-
revision-identifier (DOCREV051 in the parent instance in Table 302), and engineering-drawing-
document-note-identifier (NOTNUM325) must exist in the corresponding fields in an instance in Table
080.

Code Data Element Title DED Key

NOTNUM325 engineering-drawing-document-note-identifier 0251 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK

CHGTYP325 engineering-drawing-document-proposed-entry-change-type- 0260 M

code
NOTTXT325 engineering-drawing-document-note-text 0252

B.5.7.27. Table 326, Proposed changes to the correlation of parts list finds and drawing notes (NOR-
DWGFINDNOTE). This table identifies changes to the note call-outs in parts list finds.

B-159
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. If the value of engineering-drawing-document-proposed-change-type-code (CHGTYP326) is 'D', then the

combination of the values of design-enterprise-defense-logistics--assigned-identification-code
(DESCAG050), assembly-engineering-drawing-document-alphanumeric-identifier (ASSYNO316),
document-type-code (DOCTYP010 in the parent instance in Table 302), document-alphanumeric-
revision-identifier (DOCREV051 in the parent instance in Table 302), engineering-drawing-document-
note-identifier (NOTNUM325), and parts-list-document-item-identifier (FINDID315) must exist in the
corresponding fields in an instance in Table 226.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
FINDID315 parts-list-document-item-identifier 0027 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK
NOTNUM325 engineering-drawing-document-note-identifier 0251 FK

CHGTYP326 engineering-drawing-document-proposed-change-type-code 0261 M

B.5.7.28. Table 327, Proposed changes of special item indicators in drawing notes (NOR-NOTESPECITEM).
This table identifies proposed changes to special item indicators in engineering drawing notes.

a. If the value of the engineering-drawing-document-proposed-change-type-code (CHGTYP327) is 'D', the

combination of values of design-enterprise-defense-logistics--assigned-identification-code (DESCAG050),
assembly-engineering-drawing-document-alphanumeric-identifier (ASSYNO316), document-type-code
(DOCTYP010 in the parent instance in Table 302), document-alphanumeric-revision-identifier
(DOCREV051 in the parent instance in Table 302), engineering-drawing-document-note-identifier
(NOTNUM325), and engineering-drawing-document-special-condition-code (SPNOTE327) must exist in
the corresponding fields in an instance in Table 081.
b.
Code Data Element Title DED Key
SPNOTE327 engineering-drawing-document-special-condition-code 0257 K
DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK
NORCAG300 revision-notice-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
NORNUM300 revision-notice-document-alphanumeric-identifier 0003 FK
NORREV301 revision-notice-document-alphanumeric-revision-identifier 0009 FK
NORTYP300 revision-notice-document-type-code 0004 FK
NOTNUM325 engineering-drawing-document-note-identifier 0251 FK

CHGTYP327 engineering-drawing-document-proposed-change-type-code 0261 M

B.5.7.29. Tables 328 and 329. Reserved.

B-160
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.8. Baselines. Entity tables numbered in the range of 330 through 339 contain the information concerning
program technical-, contractual- and configuration management baseline(s). The relationships between these
various entity tables are depicted in Figure 08BL1.

B.5.8.1. Table 330, Program technical baseline (TECHBL). This table correlates document identifiers with
program/system technical baseline(s). (A technical baseline is the collection of documents which are associated
with a particular project. Generally, they serve to document the analysis and rationales which were used to
authorize the project to proceed past various milestones.)

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
PROGNM691 program-name 0059 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.8.2. Table 331, Product baseline(s) (PBL). This table identifies the document(s) which comprise the product
baseline(s) for a configuration item by associating the top-level product design definition document (product-
baseline-top-level-document-identifier, PBLDOC331) for each design solution (each product baseline) with the
configuration item. All other documents in the product baseline are determined by the database when requested.
To display the entire list of documents in the product baseline: if a specification is given, the system creates a tree
of lower level documents; if a drawing is given, the system finds the part numbers associated with the specified
drawing at the current revision level, creates a part tree, and determines the document numbers (drawing,
specification, or software number) associated with each part number in the tree and all documents which are lower
level to the documents in the tree; the resulting list is the product baseline. If a software number is given, it is the
product baseline. When populating this table, care must be taken to ensure that only one top-level document is
entered for each distinct design solution for the CI. Normally, each different design solution will have a different
value of document-source-entity-identifier (SRCIDN010) inherited from Table 010.

a. The value of document-type-code (DOCTYP010) must be 'DWG', 'SPEC', or 'SW'.

b. The attributes document-identifier (DOCIDN010), document-type-code (DOCTYP010), and document-

source-entity-identifier (SRCIDN010) inherited from Table 010 are concatenated and assume the role
product-baseline-top-level-document-identifier (PBLDOC331). (See Appendix C for concatenation
order.)

Code Data Element Title DED Key

PBLDOC331 product-baseline-top-level-document-identifier 0124 FK

CIIDEN695 configuration-item-product-identifier 0111 FK

B-161
CI / 695 (from 19CI1) GENERIC-DOCUMENT / 010 (from 1GEN2) SYSTEM / 691 (from 19CI2)
ci-identifier document-source-entity-identifier program-name
document-identifier
document-type-code

may include technical data in

may be technical data for

may have established

TECHBL / 330 GENERIC-DOCREV / 011 (from 1GEN2)
may be the highest
level document in program-name (FK) document-source-entity-identifier
document-source-entity-identifier (FK) document-identifier
document-identifier (FK) document-type-code
document-type-code (FK) document-generic-revision

PBL / 331

B-162
CONMOD / 951 (from 26CON2)
pbl-top-level-document.(document-type-code,document-source-entity-identifier,document-identifier) (FK)
contract-identifier
APPENDIX B
MIL-STD-2549

ci-identifier (FK) contract-modification

NOTE: For FBL and ABL, see may establish a

Figure 3SPEC1, Table baseline consisting of
PSPEC / 100.
may be part of a
may be contracted for by contractual baseline
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

CONTRACT-PBL / 332
contract-identifier (FK)
FIGURE 08BL1
contract-modification (FK)
BASELINES
document-source-entity-identifier (FK)
document-identifier (FK)
document-type-code (FK)
document-generic-revision (FK)
pbl-top-level-document (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.8.3. Table 332, Contract (product) baseline (CONTRACT-PBL). This table identifies the document(s) which
comprise the product baseline for a configuration item as specified in a particular contract at a particular contract
modification. All documents in the contractual product baseline are included with the specific revision which is
contractually applicable. Unless a commodity or common use item is being purchased, each document entered in
this table must exist somewhere in the tree of documents which forms the complete PBL listing for the specified
product-baseline-top-level-document-identifier (PBLDOC331).

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

PBLDOC331 product-baseline-top-level-document-identifier 0124 FK, O

B.5.8.4. Tables 333 through 344. Reserved.

B-163
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.9. National stock number. Entity tables numbered in the range of 345 through 349 contain the information
concerning national stock number. This section includes the correlation of NSNs to part numbers or material
identifiers and the identification of substitute (due to temporary non-availability) and replacement (due to
permanent supersession) NSNs. The relationships between these various NSN entity tables are depicted in Figure
09NSN1.

NSN / 345 (from PCTSS) (see 5PIN1, 5PIN2) REPLACEMENT-NSN / 346

nsn may be substituted by replaced-nsn.nsn (FK)
replacement-nsn.nsn (FK)
may be substituted for
replacement-type-code

FIGURE 09NSN1
NATIONAL STOCK NUMBER DEFINITION

B.5.9.1. Table 345, National stock number (NSN). This table is part of the Provisioning/Cataloging Technical
Support System (PCTSS) and contains national stock numbers which are pertinent to the configuration
management process.

Code Data Element Title DED Key

NSNNUM345 product-national-stock-identifier 0049 K

NSNDES345 product-national-stock-description-text 0116 M

PRDTYP345 product-type-code 0034 M

B.5.9.2. Table 346, Correlation of NSN to substitute/replacement NSN(s) (REPACEMENT-NSN). This table
identifies NSNs which have been identified by competent authority as suitable substitute parts/materials or
permanent replacement parts/materials for NSNs which have either been permanently discontinued (and, therefore,
superseded) or which are temporarily out-of-stock.

a. Attribute product-national-stock-identifier (NSNNUM345) inherited from Table 345 assumes the role
replacement-product-national-stock-identifier (NEWNSN346).

b. Attribute product-national-stock-identifier (NSNNUM345) inherited from Table 345 assumes the role
replaced-product-national-stock-identifier (OLDNSN346).

Code Data Element Title DED Key

NEWNSN346 replacement-product-national-stock-identifier 0049 FK
OLDNSN346 replaced-product-national-stock-identifier 0049 FK

REPTYP346 product-replacement-type-code 0106 M

B.5.9.3. Tables 347 through 349. Reserved.

B-164
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.10. Requests for deviation (RFD). Entity tables numbered in the range of 350 through 399 contain the
identification of Requests for Deviation, along with all associated attributes. Requests for Deviation are strictly a
Government form; therefore, this means that the content of this section is limited to RFDs identified by a CAGE
(or NSCM) code and a document number. The relationships between these various entity tables are depicted in
Figures 10RFD1 through 10RFD5.

B.5.10.1. Table 350, Request for deviation document (RFD). This table includes the unique and primary
identification of an RFD document. An RFD is a subtype of CAGE-NUM-DOC/022 for the case where the value
of document-type-code is 'RFD'.

a. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 022 assumes the role deviation-request-document-source-enterprise-defense-
logistics--assigned-identification-code (RFDCAG350).

b. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 022 assumes the role
deviation-request-document-alphanumeric-identifier (RFDNUM350).

c. Attribute document-type-code (DOCTYP010) inherited from Table 022 assumes the role deviation-
request-document-type-code (RFDTYP350).

Code Data Element Title DED Key

B.5.10.2. Table 351, Revisions to request for deviation documents (RFDREV). This table is a subtype of Table
CAGE-NUM-DOCREV/023 for the case where the value of document-type-code in Table 023 is 'RFD'. It contains
the revision history of the RFD during its life cycle.

a. Due to parallel categorization, this table is a de facto child of Table RFD/350.

b. The change-proposal-document-...-effect-code (AFF0xx351) data elements and the standard-generalized-

markup-language-document-...-field-identifier (SGMLxx351) are paired fields. The value of the
SGMLxx351 field must be blank if the value of the AFF0xx351 field is 'N'. For each AFF0xx351 data
element with a value of 'Y', there must be a text explanation discussing this element in the RFD file(s). If
the contract requires that the RFD be compliant with MIL-STD-28001 (SGML), then, the SGML tags
used in the RFD file(s) must be entered in the appropriate SGMLxx351 field.

c. If the contract requires that the RFD be compliant with MIL-STD-28001 (SGML), then, the SGML tags
used in the RFD file(s) for Description of Need for Deviation and RFD Description must be entered in
standard-generalized-markup-language-document-proposed-change-need-field-identifier (SGMNED351),
and standard-generalized-markup-language-document-proposed-change-description-field-identifier
(SGMDES351), respectively.

d. The value of 'product-baseline-type' (BLTYPE351) is limited to the values 'A', 'F', or 'P'.

B-165
CAGE-NUM-DOCREV / 023 (from 1GEN4) CAGE-NUM-DOC / 022 (from 1GEN3)
design-cage-code design-cage-code
document-alphanumeric-identifier document-alphanumeric-identifier ECP / 250 (from 6ECP1)
document-type-code document-type-code ecp-cage-code
document-revision ecp-alphanumeric-identifier
ECP

document-type-code
document-type-code
RFD
RFD

RFDREV / 351 (de facto child of 350) (see 10RFD2, 10RFD3, 22REV2) RFD / 350 (see 17PAN1)
rfd-cage-code.design-cage-code (FK) rfd-cage-code.design-cage-code (FK)
rfd-alphanumeric-identifier.document-alphanumeric-identifier (FK) rfd-alphanumeric-identifier.document-alphanumeric-identifier (FK)
RFD.document-type-code (FK) RFD.document-type-code (FK)
rfd-revision.document-revision (FK)

may recur as
may be a recurrence of
Assertion: The relationships has
of Table 351 to Table 352
and Table 351 to Table 353 CONMOD / 951 (from 26CON2)
cannot both be 1:0. may resolve
contract-identifier
may impact
contract-modification
CLIN / 959 (from 26CON2)

B-166
contract-identifier Z Z
contract-modification P RFD-RECUR / 359
APPENDIX B

clin-identifier
MIL-STD-2549

may be impacted by current-rfd-cage-code.rfd-cage-code (FK)

RFDREV-STAT / 373 (de facto subtype of 850)
current-rfd-alphanumeric-identifier.rfd-alphanumeric-identifier (FK)
rfd-cage-code (FK)
rfd-revision (FK)
rfd-alphanumeric-identifier (FK)
RFD-CON / 354 prior-rfd-cage-code.rfd-cage-code (FK)
RFD (FK)
prior-rfd-alphanumeric-identifier.rfd-alphanumeric-identifier (FK)
contract-identifier (FK) rfd-revision (FK)
RFD (FK)
contract-modification (FK) document-revision-approval-status-code
may be rfd-cage-code (FK) document-revision-approval-status-date ecp-cage-code (FK)
affected by rfd-alphanumeric-identifier (FK) ecp-alphanumeric-identifier (FK)
RFD (FK) ECP (FK)
rfd-revision (FK)
may implement document-revision-approval-status-code
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

RFD-AFFECTED-ITEM / 355 APV

contract-identifier (FK)
contract-modification (FK) APPRFDREV-CONMOD / 356
may impact RFDREV-APP / 374 (de facto subtype of 854) (see 10RFD5,13TRK3)
clin-identifier (FK) contract-identifier (FK)
rfd-cage-code (FK) rfd-cage-code (FK) (AK1)
contract-modification (FK) may be rfd-alphanumeric-identifier (FK) (AK1)
rfd-alphanumeric-identifier (FK) rfd-cage-code (FK)
RFD (FK) implemented RFD (FK) (AK1)
rfd-alphanumeric-identifier (FK) by rfd-revision (FK)
rfd-revision (FK) RFD (FK) document-revision-approval-status-code (FK)
rfd-revision (FK) document-revision-approval-status-date (FK)
document-revision-approval-status-code (FK)
FIGURE 10RFD1 document-revision-approval-status-date (FK)
REQUEST FOR DEVIATION (RFD) DEFINITION (Part 1 of 2)
RFD-SUPDOC / 357
RFDREV / 351 (from 10RFD1) rfd-cage-code (FK)
rfd-alphanumeric-identifier (FK) GENERIC-DOCREV / 011 (from 1GEN2)
rfd-cage-code RFD (FK) may be a document-source-entity-identifier
rfd-alphanumeric-identifier may have justification rfd-revision (FK) supplement document-identifier
RFD supplemented by document-source-entity-identifier (FK) to document-type-code
rfd-revision document-identifier (FK) document-generic-revision
document-type-code (FK)
document-generic-revision (FK)

proposes
deviation from may have requirements
requirements of deviated from by
P
RFDREV-DOCREV / 352
rfd-cage-code (FK) GENERIC-SWPROD / 170 (from 4SW3)
rfd-alphanumeric-identifier (FK) software-source-identifier
RFD (FK) software-generic-identifier
Assertion: The relationships between rfd-revision (FK)
Tables 351 and 353 (shown here), document-source-entity-identifier (FK)
and between Tables 351 and 360 and

B-167
document-identifier (FK)
Tables 351 and 365 (shown on 10RFD3) document-type-code (FK)
APPENDIX B

cannot all be 1:0.

MIL-STD-2549

document-generic-revision (FK)

may affect may be affected by

has extended text in
RFDREV-SW / 353
Z
rfd-cage-code (FK)
RFD-EXTTXT / 358 FILE / 900 (from 1FILE1) rfd-alphanumeric-identifier (FK)
rfd-cage-code (FK) file-originator RFD (FK)
rfd-revision (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

rfd-alphanumeric-identifier (FK) file-originator-address

RFD (FK) may be extended text for file-identifier software-source-identifier (FK)
rfd-revision (FK) file-creation-date software-generic-identifier (FK)
file-originator (FK) file-creation-time
file-originator-address (FK)
file-identifier (FK)
file-creation-date (FK)
file-creation-time (FK)

FIGURE 10RFD2
REQUEST FOR DEVIATION (RFD) DEFINITION (Part 2 OF 2)
RFDREV / 351 / (from 10RFD1) BASETRACK / 515 (from 13TRK2)
GENERIC-PART / 210 (from 5PIN2)
rfd-cage-code RFD-PART / 360 product-tracking-base-identifier
rfd-alphanumeric-identifier may design-enterprise-identifier
rfd-cage-code (FK) may be manufacturer-cage-code
RFD affect part-identifier
rfd-alphanumeric-identifier (FK) affected by product-effectivity-tracking-type
rfd-revision RFD (FK) product-tracking-identifier
rfd-revision (FK)
design-enterprise-identifier (FK)
part-identifier (FK)
may be proposed starting effectivity
may be proposed ending effectivity
Assertion: The relationships
between Tables 351 and 353
(shown on 10RFD2), and RFDPART-PROPEFF / 361 (see 10RFD4)
between Tables 351 and 360 and
rfd-cage-code (FK)
Tables 351 and 365 (shown here)
rfd-alphanumeric-identifier (FK)
cannot all be 1:0.
RFD (FK)
is effective on
rfd-revision (FK)
P design-enterprise-identifier (FK)
part-identifier (FK)
manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK)

B-168
starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
may affect
ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
APPENDIX B
MIL-STD-2549

product-tracking-base-identifier (FK)
GENERIC-MATID / 200 (from 5PIN1)
design-enterprise-identifier
material-generic-identifier may be proposed starting effectivity
material-identification
may be proposed ending effectivity

RFDMAT-PROPEFF / 366
may be affected by
rfd-cage-code (FK)
rfd-alphanumeric-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

RFD-MAT / 365 RFD (FK)

rfd-cage-code (FK) rfd-revision (FK)
rfd-alphanumeric-identifier (FK) design-enterprise-identifier (FK)
RFD (FK) may be effective on material-generic-identifier (FK)
rfd-revision (FK) material-identification (FK)
P manufacturer-cage-code (FK)
design-enterprise-identifier (FK)
material-generic-identifier (FK) product-effectivity-tracking-type (FK)
material-identification (FK) starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
product-tracking-base-identifier (FK)

FIGURE 10RFD3
REQUEST FOR DEVIATION (RFD) EFFECTIVITY
RFDPART-PROPEFF / 361 (from 10RFD3)
rfd-cage-code COMPSW-EFF / 239 (from 5PIN5) COMPMAT-EFF / 238 (from 5PIN5)
rfd-alphanumeric-identifier design-cage-code
RFD assembled-product-cage-code
part-identifier part-identifier
rfd-revision manufacturer-cage-code
design-enterprise-identifier manufacturer-cage-code
product-effectivity-tracking-type product-effectivity-tracking-type
part-identifier starting-effectivity-product-tracking-identifier
manufacturer-cage-code starting-effectivity-product-tracking-identifier
software-source-identifier design-enterprise-identifier
product-effectivity-tracking-type material-generic-identifier
starting-effectivity-product-tracking-identifier software-generic-identifier
material-identification
ending-effectivity-product-tracking-identifier ending-effectivity-product-tracking-identifeir
product-tracking-base-identifier ending-effectivity-product-tracking-identifier
product-tracking-base-identifier product-tracking-base-identifier
component-quantity
may
may apply to implement
COMPPIN-EFF / 237 (from 5PIN5)
design-cage-code
assembled-product-identifier APPRRFD-COMPSW / 364
manufacturer-cage-code
product-effectivity-tracking-type assembled-product-cage-code.(assembled-product-cage-code,design-enterprise-identifier) (FK)
starting-effectivity-product-tracking-identifier part-identifier (FK)
design-enterprise-identifier manufacturer-cage-code (FK)
component-part-identifier product-effectivity-tracking-type (FK)
starting-effectivity-product-tracking-identifier (FK)
ending-effectivity-product-tracking-identifier software-source-identifier (FK)

B-169
product-tracking-base-identifier software-generic-identifier (FK)
component-quantity rfd-cage-code (FK)
APPENDIX B
MIL-STD-2549

rfd-alphanumeric-identifier (FK)
RFD (FK)

may implement rfd-revision (FK)

may apply to

may apply to
may implement
APPRRFD-COMPPIN / 362
design-cage-code.(design-cage-code,design-enterprise-identifier) (FK)
assembled-product-identifier.(assembled-product-identifier,part-identifier) (FK) APPRRFD-COMPMAT / 363
manufacturer-cage-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

design-cage-code.(design-cage-code,design-enterprise-identifier) (FK)
product-effectivity-tracking-type (FK)
part-identifier (FK)
starting-effectivity-product-tracking-identifier (FK)
manufacturer-cage-code (FK)
design-enterprise-identifier (FK)
product-effectivity-tracking-type (FK)
component-part-identifier (FK)
starting-effectivity-product-tracking-identifier (FK)
rfd-cage-code (FK)
design-enterprise-identifier (FK)
rfd-alphanumeric-identifier (FK)
material-generic-identifier (FK)
RFD (FK)
material-identification (FK)
rfd-revision (FK) rfd-cage-code (FK)
rfd-alphanumeric-identifier (FK)
RFD (FK)
FIGURE 10RFD4 rfd-revision (FK)
REQUEST FOR DEVIATION IMPACT ON ASSEMBLIES
CCB-RFD / 706 (from 19CI2)
enterprise-identifier RFDREV-APP / 374 (from 10RFD1)
program-name rfd-cage-code
ccb-name rfd-alphanumeric-identifier
rfd-cage-code RFD
rfd-alphanumeric-identifier rfd-revision
RFD document-revision-approval-status-code
rfd-revision document-revision-approval-status-date

OFFICE / 941 (from 25ADD1)

enterprise-identifier
office-symbol may direct may require

RFDACT / 370
ccb-enterprise-identifier.enterprise-identifier (FK)
program-name (FK)
ccb-name (FK)
rfd-cage-code (FK)
rfd-alphanumeric-identifier (FK)

B-170
may be responsible for RFD (FK)
rfd-revision (FK)
APPENDIX B
MIL-STD-2549

rfd-implementation-action-identifier
rfd-implementation-action-responsible-enterprise-identifier.enterprise-identifier (FK)
rfd-implementation-action-responsible-office.office-symbol (FK)
document-revision-approval-status-code (FK)
document-revision-approval-status-date (FK)

RFDACTSTAT / 372
ccb-enterprise-identifier (FK)
program-name (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

ccb-name (FK)
rfd-cage-code (FK)
rfd-alphanumeric-identifier (FK)
has life cycle status
RFD (FK)
FIGURE 10RFD5 P rfd-revision (FK)
REQUEST FOR DEVIATION IMPLEMENTATION rfd-implementation-action-identifier (FK)
rfd-implementation-disposition-status-code
rfd-implementation-disposition-status-date
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

e. Because this table is a de facto child of Table 350, document-source-enterprise-defense-logistics--

assigned-identification-code (SRCCAG022) inherited from Table 023 is really a deviation-request-
document-source-enterprise-defense-logistics--assigned-identification-code (RFDCAG350) existing in
Table 350. Therefore, SRCCAG022 assumes the identity RFDCAG350.

f. Because this table is a de facto child of Table 350, document-alphanumeric-identifier (DOCNUM020)

inherited from Table 023 is really a deviation-request-document-alphanumeric-identifier (RFDNUM350)
existing in Table 350. Therefore, DOCNUM020 assumes the identity RFDNUM350.

g. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 023 assumes the role
deviation-request-document-alphanumeric-revision-identifier (RFDREV351).

h. Because this table is a de facto child of Table 350, document-type-code (DOCTYP010) inherited from
Table 023 is really a deviation-request-document-type-code (RFDTYP350) existing in Table 350.
Therefore, DOCTYP010 assumes the identity RFDTYP350.

Code Data Element Title DED Key

RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

BLTYPE351 product-baseline-type-code 0098 M

RFD006351 deviation-request-document-defect-severity-classification- 0125 M
code
RFD018351 deviation-request-document-recurring-request-code 0133 M
RFD019351 deviation-request-document-price-effect-estimate-amount 0132 M
RFD020351 deviation-request-document-delivery-schedule-effect-text 0131 M
RFD022351 deviation-request-document-description-text 0126 M
RFD023351 deviation-request-document-justification-text 0127 M
RFD024351 deviation-request-document-corrective-action-taken-text 0130 M
RFD19A351 deviation-request-document-price-adjustment-effect- 0104
rationale-text
SGM021351 standard-generalized-markup-language-document-proposed- 0118
change-logistics-support-effect-field-identifier
SGM022351 standard-generalized-markup-language-document-proposed- 0118
change-long-description-field-identifier
SGM023351 standard-generalized-markup-language-document-proposed- 0118
change-long-need-rationale-field-identifier
SGM024351 standard-generalized-markup-language-document-deviation- 0118
request-corrective-action-taken-field-identifier

B.5.10.3. Table 352, Source of requirements which is basis for deviation (RFDREV-DOCREV). This table
correlates the RFD revision to the revision of the document(s) which include the requirements from which the

B-171
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

deviation is requested. The value of document-type-code (DOCTYP010) inherited from Table 011 must be either
'DWG', 'MISC', 'P-SPEC', 'STDDOC', or 'SWDOC'.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

DOCREV011 document-generic-revision-identifier 0243 FK

SGM22A352 standard-generalized-markup-language-document-specific- 0118 M
proposed-changes-field-identifier

B.5.10.4. Table 353, Software affected by a deviation (RFDREV-SW). This table correlates the RFD revision
to the software product(s) which are affected by the RFD.

Code Data Element Title DED Key

PARLVL353 deviation-request-document-part-level-code 0220 M

B.5.10.5. Table 354, Correlation of request for deviation documents with the contract numbers under which
they are submitted (RFD-CON). This table correlates RFDs to the contracts which they impact, or under which
they are submitted. Only current contracts between the originator and the approval agency for which a CDRL item
exists need to be addressed.

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK

B-172
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

RFDTYP350 deviation-request-document-type-code 0004 FK

B.5.10.6. Table 355, Correlation of contract line items to the request for deviation which affects them (RFD-
AFFECTED-ITEM). This table correlates the RFD with the affected contract line items. Only the most recent
modification for any one contract needs to be addressed.

Code Data Element Title DED Key

CLINUM959 contract-document-line-item-identifier 0017 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

B.5.10.7. Table 356, Correlation of approved RFD to implementing contract modification(s) (APPRFDREV-
CONMOD). This table correlates approved RFDs to their implementing contract modification(s).

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK

RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.10.8. Table 357, Identification of documents which supplement the contents of an RFD (RFD-SUPDOC).
This table correlates various documents with the RFD(s) which they supplement. Usually these documents are
analysis, reports, studies, or marked-up drawings.

a. The value of document-type-code (DOCTYP010) must be 'ANALYS', 'BOOK', 'DWG', 'MISC',

'PERIODL', 'PL', 'PLNPROC', 'P-SPEC', or 'STDDOC'.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code

B-173
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK

RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.10.9. Table 358, RFD text file (RFD-EXTTXT). This table identifies the file which contains the extended
text to which the SGML tags in Table 351 refer.

a. The combination of file-originator-human-name (FILORG900), electronic-document-file-identifier

(FILIDN900) and enterprise-file-origination-office-address-text (FILADD900) can be associated with only
one combination of deviation-request-document-source-enterprise-defense-logistics--assigned-
identification-code (RFDCAG350), deviation-request-proposal-document-alphanumeric-identifier
(RFDNUM350), and deviation-request-proposal-document-alphanumeric-revision-identifier
(RFDREV351).

Code Data Element Title DED Key

FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILIDN900 electronic-document-file-identifier 0206 FK
FILORG900 file-originator-human-name 0069 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

FILDAT900 electronic-document-file-creation-date 0082 FK

FILTIM900 electronic-document-file-creation-time 0160 FK

B.5.10.10. Table 359, Correlation of prior requests for deviation with current recurring deviation request (RFD-
RECUR). This table correlates RFDs which have been submitted by a single company for a recurring problem.

a. The values of engineering-change-proposal-document-source-enterprise-defense-logistics--assigned-

identification-code (ECPCAG250), engineering-change-proposal-document-alphanumeric-identifier
(ECPNUM250), and engineering-change-proposal-document-type-code (ECPTYP250) must be either all
blank, or all non-blank.

b. Attribute deviation-request-document-source-enterprise-defense-logistics--assigned-identification-code
(RFDCAG350) inherited from Table 350 assumes the role current-deviation-request-document-source-
enterprise-defense-logistics--assigned-identification-code (CRFDCG359).

c. Attribute deviation-request-document-alphanumeric-identifier (RFDNUM350) inherited from Table 350

assumes the role current-deviation-request-document-alphanumeric-identifier (CRFDNO359).

d. Attribute deviation-request-document-source-enterprise-defense-logistics--assigned-identification-code
(RFDCAG350) inherited from Table 350 assumes the role prior-deviation-request-document-source-
enterprise-defense-logistics--assigned-identification-code (PRFDCG359).

B-174
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

e. Attribute deviation-request-document-alphanumeric-identifier (RFDNUM350) inherited from Table 350

assumes the role prior-deviation-request-document-alphanumeric-identifier (PRFDNO359).

Code Data Element Title DED Key

CRFDCG359 current-deviation-request-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
CRFDNO359 current-deviation-request-document-alphanumeric-identifier 0003 FK
PRFDCG359 prior-deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
PRFDNO359 prior-deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK

defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SGMRAT359 standard-generalized-markup-language-document-recurring- 0118
deviation-request-corrective-action-taken-field-identifier

B.5.10.11. Table 360, Part numbers affected by deviations (RFD-PART). This table correlates RFDs to the part
numbers affected by the RFD.

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
PARNUM210 part-product-identifier 0024 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

PARLVL360 deviation-request-document-part-level-code 0220 M

B.5.10.12. Table 361, Proposed effectivity of an RFD with respect to impacted parts (RFD-PROPEFF). This
table correlates parts affected by the RFD with the proposed effectivity of the RFD.

a. The combination of values for design-enterprise-identifier (DESENT210) and part-product-identifier

(PARNUM210) must also relate to the product--tracking-base--identifier (BASNUM500) via the hierarchy
of tables subsidiary to Table 500.

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF361).

B-175
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF361).

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
STREFF361 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF361 product-ending-effectivity-sequential-tracking-identifier 0058 FK, O

B.5.10.13. Table 362, Impact of approved RFD on assemblies with component parts (APPRRFD-COMPPIN).
This table correlates the effectivity of the approved RFD with the assembly-component part combinations which
are impacted by the RFD.

a. Attribute assembled-part-product-identifier (APARNO234) inherited from Table 237 and part-product-

identifier (PARNUM210) inherited from Table 361 must both have the same value. Therefore they merge
and assume the identity assembled-part-product-identifier (APARNO234).

b. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG053) inherited from

Table 237 and design-enterprise-identifier (DESENT210) inherited from Table 361 must both have the
same value. Therefore they merge and assume the identity design-enterprise-defense-logistics--assigned-
identification-code (DESCAG053).

c. Fields STREFF237 inherited from Table 237 and STREFF361 inherited from Table 361 must be the
same; therefore, they assume the identity product-starting-effectivity-sequential-tracking-identifier
(STREFF362).

Code Data Element Title DED Key

APARNO234 assembled-part-product-identifier 0024 FK
CPARNO234 component-part-product-identifier 0024 FK
DESCAG053 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK

B-176
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

RFDTYP350 deviation-request-document-type-code 0004 FK

STREFF362 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK

B.5.10.14. Table 363, Impact of approved RFD on assemblies with component materials (APPRRFD-
COMPMAT). This table correlates the effectivity of the approved RFD with the assembly-component material
combinations which are impacted by the RFD.

a. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG053) inherited from

Table 238 and design-enterprise-identifier (DESENT210) inherited from Table 361 must both have the
same value. Therefore they merge and assume the identity design-enterprise-defense-logistics--assigned-
identification-code (DESCAG053).

b. Fields STREFF238 inherited from Table 238 and STREFF361 inherited from Table 361 must be the
same; therefore, they assume the identity product-starting-effectivity-sequential-tracking-identifier
(STREFF363).

Code Data Element Title DED Key

DESCAG053 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
STREFF363 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK

B.5.10.15. Table 364, Impact of approved RFD on assemblies with component software (APPRRFD-COMPSW).
This table correlates the effectivity of the approved RFD with the assembly-component software combinations
which are impacted by the RFD.

a. Attribute assembled-product-design-enterprise-defense-logistics--assigned-identification-code
(ADESCG236) inherited from Table 239 and design-enterprise-identifier (DESENT210) inherited from
Table 361 must both have the same value. Therefore they merge and assume the identity assembled-
product-design-enterprise-defense-logistics--assigned-identification-code (ADESCG236).

B-177
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Fields STREFF239 inherited from Table 239 and STREFF361 inherited from Table 361 must be the
same; therefore, they assume the identity product-starting-effectivity-sequential-tracking-identifier
(STREFF364).

Code Data Element Title DED Key

ADESCG236 assembled-product-design-enterprise-defense-logistics-- 0001 FK
assigned-identification-code
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
STREFF364 product-starting-effectivity-sequential-tracking-identifier 0058 FK
SWIDEN170 software-product-generic-identifier 0060 FK
SWSORC170 software-product-source-entity-identifier 0033 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK

B.5.10.16. Table 365, Materials affected by deviations (RFD-MAT). This table correlates RFDs to the
material(s) (not identified by a part number) affected by the RFD.

Code Data Element Title DED Key

DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

PARLVL365 deviation-request-document-part-level-code 0220 M

B.5.10.17. Table 366, Proposed effectivity of an RFD with respect to impacted materials (RFDMAT-PROPEFF).
This table correlates materials affected by the RFD with the proposed effectivity of the RFD.

a. The combination of values for design-enterprise-identifier (DESENT200), material-product-generic-

identifier (MATGID200), and material-product-identifier (MATIDN200) must also relate to the product--
tracking-base--identifier (BASNUM500) via the hierarchy of tables subsidiary to Table 500.

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF366).

B-178
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF366).

Code Data Element Title DED Key

DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
STREFF366 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF366 product-ending-effectivity-sequential-tracking-identifier 0058 FK, O

B.5.10.18. Tables 367 through 369. Reserved.

B.5.10.19. Table 370, RFD implementation actions (RFDACT). This table identifies the CCB-directed actions
necessary to implement the approved RFD.

a. Attribute enterprise-identifier (ENTIDN002) inherited from Table 706 assumes the role configuration-
control-board-convening-enterprise-identifier (CCBENT370).

b. Attribute enterprise-office-name (OFFSYM941) inherited from Table 941 assumes the role deviation-
implementation-required-action-responsible-enterprise-office-name (RESOFF370).

c. Attribute enterprise-identifier (ENTIDN002) inherited from Table 941 assumes the role deviation-
implementation-process-required-action-responsible-enterprise-identifier (RESPON370).

Code Data Element Title DED Key

RFDACT370 deviation-implementation-process-action-identifier 0072 K
CCBENT370 configuration-control-board-convening-enterprise-identifier 0052 FK
CCBNAM700 program-configuration-control-board-name 0151 FK
PROGNM691 program-name 0059 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK

B-179
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

RFDTYP350 deviation-request-document-type-code 0004 FK

RESOFF370 deviation-implementation-required-action-responsible- 0044 FK

enterprise-office-name
RESPON370 deviation-implementation-process-required-action- 0052 FK
responsible-enterprise-identifier
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK
ACTCOM370 process-action-comment-text 0066
ACTDES370 deviation-implementation-process-action-item-description- 0185 M
text
ACTTTL370 process-action-item-title-name 0136 M

B.5.10.20. Table 371. Reserved.

B.5.10.21. Table 372, RFD Implementation Action Status (RFDACTSTAT). This table contains the status of
each action item necessary to implement the approved RFD.

Code Data Element Title DED Key

STACOD372 deviation-implementation-process-action-disposition-status- 0021 K
code
STADAT372 deviation-implementation-process-action-disposition-status- 0082 K
date
CCBENT370 configuration-control-board-convening-enterprise-identifier 0052 FK
CCBNAM700 program-configuration-control-board-name 0151 FK
PROGNM691 program-name 0059 FK
RFDACT370 deviation-implementation-process-action-identifier 0072 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

ACTCOM372 process-action-comment-text 0066

B.5.10.22. Table 373, RFD approval process status (RFDREVSTAT). This table contains the status of an RFD
revision as it is processed through the approval process by the CDCA of the RFD. Although not shown, it can be
proven that the series of subtype relationships between Table GENERIC-DOCREV/011 and this table also exist
between Table DOCREVSTAT/850 and this table. Therefore, Table 373 is a de facto subtype of Table 850, and all
the data elements, rules and relationships of Table 850 apply.

a. Because this table is a de facto subtype of Table 850, deviation-request-document-source-enterprise-

defense-logistics--assigned-identification-code (RFDCAG350) inherited from Table 351 is really a
document-source-entity-identifier (SRCIDN010) existing in Table 850.

B-180
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Because this table is a de facto subtype of Table 850, deviation-request-document-alphanumeric-identifier

(RFDNUM350) inherited from Table 351 is really a document-identifier (DOCIDN010) existing in Table
850.

c. Because this table is a de facto subtype of Table 850, deviation-request-document-alphanumeric-revision-

identifier (RFDREV351) inherited from Table 351 is really a document-generic-revision-identifier
(DOCREV011) existing in Table 850.

d. Because this table is a de facto subtype of Table 850, deviation-request-document-type-code

(RFDTYP350) inherited from Table 351 is really a document-type-code (DOCTYP010) existing in Table
850.

Code Data Element Title DED Key

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.10.23. Table 374, Approved RFDs (RFDREV-APP). This table is one subtype of RFDREVSTAT/373 which
contains the subset of the contents of Table 373 consisting of those documents which are approved RFDs;
therefore, the value of document-revision-approval-process-disposition-status-code must be 'APP'. Although not
shown, it can be proven that the series of subtype relationships between Table GENERIC-DOCREV/011 and this
table also exist between Table DOCREV-APP/854 and this table. Therefore, Table 374 is a de facto subtype of
Table 854, and all the data elements, rules and relationships of Table 854 apply. This table is singled out in the
data model due to the unique relationships associated with it.

a. Because this table is a de facto subtype of Table 854, deviation-request-document-source-enterprise-

defense-logistics--assigned-identification-code (RFDCAG350) inherited from Table 373 is really a
document-source-entity-identifier (SRCIDN010) existing in Table 854.

b. Because this table is a de facto subtype of Table 854, deviation-request-document-alphanumeric-identifier

(RFDNUM350) inherited from Table 373 is really a document-identifier (DOCIDN010) existing in Table
854.

c. Because this table is a de facto subtype of Table 854, deviation-request-document-alphanumeric-revision-

identifier (RFDREV351) inherited from Table 373 is really a document-generic-revision-identifier
(DOCREV011) existing in Table 854.

d. Because this table is a de facto subtype of Table 854, deviation-request-document-type-code

(RFDTYP350) inherited from Table 373 is really a document-type-code (DOCTYP010) existing in Table
854.

B-181
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK, AK1
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK, AK1
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK, AK1
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.10.24. Tables 375 through 399. Reserved.

B-182
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.11. Standardization documents and standard parts and materials. Entity tables numbered in the range of 400
through 449 contain the identification of standardization documents, along with all associated unique attributes.
Standardization documents include specifications, standards, handbooks, guidebooks, codes, practices, procedures,
protocols, regulations, manuals, etc. which are issued for the purpose of standardizing or codifying practices,
procedures, processes, materials, parts, etc. within a segment of a company, industry, or government. (For
example: Military Standards, Federal Specifications, ISO Application Protocols, EIA Bulletins, AECMA
Documents, SAE Standard Practices, AF Regulations, Code of Federal Regulations [CFR], Standard NATO
Agreements (STANAGs), company Standard Procedures, etc.) This section specifically excludes program-unique
specifications (see B.5.2.30), DOD Technical Manuals/Orders (see B.5.13.36), and Data Item Descriptions (see
B.5.15.15). This section also identifies parts and materials defined by standardization documents. (For example:
MS-parts, NAS-parts, DIN-parts, etc.) The relationships between these various standardization document entity
tables are depicted in Figure 11STDS1 through 11STDS5.

B.5.11.1. Table 400, Standardization documents (STDDOC). This table is a subcategory of Table NUMDOC/
020 for the case where the value of document-type-code is 'STDDOC'. It contains standardization documents
which are identified by an alphanumeric identifier. This table has three subcategories: ORGSTDDOC/402,
CAGSTDDOC/430, and COMSTDNUMDOC/440.

a. For each value of product--tracking-base--identifier (BASNUM500) in this table, there may be one (but
only one) instance in this table where the value of BASNUM500 is the same as the value of the
concatenation of enterprise-identifier (ENTIDN002), document-alphanumeric-identifier (DOCNUM020),
and document-type-code (DOCTYP010).

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCENT020 document-source-enterprise-identifier 0052 FK

BASNUM500 product--tracking-base--identifier 0056 FK, O

PRDTYP400 product-type-code 0034 M

B.5.11.2. Table 401, Revisions to standardization documents (STDDOCREV). This table is a subcategory of
Table NUMDOCREV/021 for the case where the value of document-type-code is 'STDDOC'. It contains revision
history of standardization documents. Due to parallel categorization, this table is a de facto child of Table
STDDOC/400. This table has three subcategories: ORGSTDDOCREV/403, CAGESTDDOCREV/431, and
COMSTDDOCREV/441.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCENT020 document-source-enterprise-identifier 0052 FK

B-183
NUMDOC / 020 (from 1GEN3) NUMDOCREV / 021 (from 1GEN4)
document-source-enterprise-identifier document-source-enterprise-identifier
document-alphanumeric-identifier document-alphanumeric-identifier
document-type-code BASE-STDDOC / 504 (from 13TRK1) document-type-code
product--tracking-base--identifier document-generic-revision

document-type-code
is the common document-type-code
base number for
STDDOC P STDDOC
STDDOC / 400 STDDOCREV / 401 (de facto child of 400)
document-source-enterprise-identifier (FK) document-source-enterprise-identifier (FK)
document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
document-type-code (FK) document-type-code (FK)
document-generic-revision (FK)
product--tracking-base--identifier (FK)
product-type-code

enterprise-identification-type-code (from 002) enterprise-identification-type-code (from 002)

CAG CAG
CAGESTDDOC / 430 (de facto child of 022) (see 11STDS5) CAGESTDDOCREV / 431 (de facto child of 430) (see 11STDS5)
document-source-cage-code.document-source-enterprise-identifier (FK) document-source-cage-code.document-source-enterprise-identifier (FK)
document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
document-type-code (FK) document-type-code (FK)
document-generic-revision (FK)

B-184
APPENDIX B

COM
MIL-STD-2549

COM
COMSTDNUMDOC / 440 (de facto subtype of 914)
commercial-document-source-name.document-source-enterprise-identifier (FK) COMSTDNUMDOCREV / 441 (de facto child of 440)
document-alphanumeric-identifier (FK) comercial-document-source-identifier.document-source-enterprise-identifier (FK)
document-type-code (FK) document-alphanumeric-identifier (FK)
document-type-code (FK)
document-generic-revision (FK)
ORG

ORGSTDDOC / 402 (de facto child of 024) (see 11STDS2,11STDS4) ORG

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-source-organization-identifier.document-source-enterprise-identifier (FK)
document-alphanumeric-identifier (FK) ORGSTDDOCREV / 403 (de facto child of 402)(see 6ECP2, 7NOR3, 11STDS4)
document-type-code (FK) document-source-organization-identifier.document-source-enterprise-identifier (FK)
controlling-document-alphanumeric-identifier.document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
controlling-document-source-organization-identifier.document-source-organization-identifier (FK) document-type-code (FK)
document-generic-revision (FK)

may control alias

FIGURE 11STDS1
STANDARDIZATION DOCUMENTS
ORGSTDDOC / 402 (from 11STDS1)
document-source-organization-identifier
document-alphanumeric-identifier
document-type-code

organization-type-identifier
(from Table 004)
DOD
US-GOV-NONDEF
DOD-STDDOC / 408 (de facto child of 034) (see 11STDS3)
us-dod-document-source-organization-code.document-source-organization-identifier (FK)
document-alphanumeric-identifier (FK)
document-type-code (FK)
standardization-document-series-type-code

US-GOV-NONDEF-STDDOC / 409 (de facto child of 035)

us-government-nondefense-document-source-organization-code.document-source-organization-identifier (FK)
document-alphanumeric-identifier (FK)
document-type-code (FK)
standardization-document-series-type-code

US-NON-GOVT
NON-US-GOVT
US-NONGOV-STDDOC / 407 (de facto child of 036)

B-185
us-nongovernment-document-source-organization-code.document-source-organization-identifier (FK)
document-alphanumeric-identifier (FK)
APPENDIX B
MIL-STD-2549

document-type-code (FK)
standardization-document-series-type-code

NON-US-GOV-STDDOC / 405 (de facto child of 037)

non--us-government-document-source-organization-code.document-source-organization-identifier (FK)
document-alphanumeric-identifier (FK)
document-type-code (FK)
standardization-document-series-type-code

NON-US-NONGOVT
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

INT
NON-US-NONGOV-STDDOC / 406 (de facto child of 038)
non--us-nongovernment-document-source-organization-code.document-source-organization-identifier (FK)
document-alphanumeric-identifier (FK)
document-type-code (FK)
standardization-document-series-type-code

INT-STDDOC / 404 (de facto child of 039)

FIGURE 11STDS2 international-document-source-organization-code.document-source-organization-identifier (FK)
STANDARDIZATION DOCUMENTS document-alphanumeric-identifier (FK)
document-type-code (FK)
standardization-document-series-type-code
DOD-STDDOC / 408 (de facto child of 034) (from 11STDS2)
us-dod-document-source-organization-code
document-alphanumeric-identifier
document-type-code
standardization-document-series-type-code

dod-organization-type-identifier
(from 034)
OSD

DEFSEC-STDDOC / 410
us-defense-secretariate-document-source-organization-code.us-dod-document-source-organization-code (FK)
document-alphanumeric-identifier (FK)
document-type-code (FK)

standardization-document-series-type-code
STD
SPEC USDEFSTD / 411

B-186
us-defense-secretariate-document-source-organization-code (FK)
APPENDIX B

us-defense-standard-document-alphanumeric-identifier.document-alphanumeric-identifier (FK)
MIL-STD-2549

document-type-code (FK)

USDEFSPEC / 412 (see 7NOR3)

us-defense-secretariate-document-source-organization-code (FK)
us-defense-specification-document-alphanumeric-identifier.document-alphanumeric-identifier (FK)
document-type-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

HDBK

USDEFHDBK / 413
us-defense-secretariate-document-source-organization-code (FK)
us-defense-handbook-document-alphanumeric-identifier.document-alphanumeric-identifier (FK)
FIGURE 11STDS3
document-type-code (FK)
STANDARDIZATION DOCUMENTS
ORGSTDDOC / 402 (from 11STDS1)
document-source-organization-identifier
document-alphanumeric-identifier
document-type-code

product-type-code (from 400)

P M
ORGSTDDOC-DEFPIN / 420 (see 5PIN2)
design-organization-code.document-source-organization-identifier (FK) ORGSTDDOC-DEFMAT / 421 (see 05PIN1)
document-alphanumeric-identifier (FK) design-organization-code.document-source-organization-identifier (FK)
document-type-code (FK) material-document-identifier.(document-alphanumeric-identifier,document-type-code) (FK)

STDPIN / 211 (from 05PIN2) ORGSTDDOCREV / 403 (from 11STDS1) STD-MATID / 201 (from 05PIN1)
design-organization-code document-source-organization-identifier design-organization-code
part-identifier document-alphanumeric-identifier material-document-identifier
document-type-code material-identification
document-alphanumeric-identifier document-generic-revision
document-type-code

may define may define

has status
Assertion: The relation of ORGSTDDOCREV/403

B-187
Assertion: The relation of ORGSTDDOCREV/403
to ORGSTDREV-PIN/423 is 1:P if the product- to ORGSTDMATSTAT/422 is 1:P if the product-
APPENDIX B

type-code in ORGSTDDOC/402 is 'P' (for part), type-code in ORGSTDDOC/402 is 'M' (for material),
MIL-STD-2549

P and is 1:0 for all other values of product-type-code.

and is 1:0 for all other values of product-type-code.
ORGSTDDOCRV-PINSTAT / 423
design-organization-code.(design-organization-code,document-source-organization-identifier) (FK)
part-identifier (FK)
part-identifie is documented by
rdocument-generic-revision
document-alphanumeric-identifier (FK)
document-type-code (FK)
document-generic-revision (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

part-status-code
P
ORGSTDDOCRV-MATSTAT / 422
design-organization-code.(design-organization-code,document-source-organization-identifier) (FK)
material-document-identifier (FK)
material-identification (FK) (AK1)
FIGURE 11STDS4 document-generic-revision (FK) (AK1)
STANDARDIZATION DOCUMENTS
document-alphanumeric-identifier (FK) (AK1)
document-type-code (FK)
material-status-code
CAGESTDDOC / 430 (from 11STDS1) CAGE-MATID / 205 (from 5PIN1)
CAGEPIN / 212 (from 5PIN2) document-source-cage-code design-cage-code
document-alphanumeric-identifier material-generic-identifier
design-cage-code material-identification
document-type-code
part-identifier
document-type-code

product-type-code (from 400) document-type-code

document-type-code
P M

CAGESTDDOC-DEFPIN / 432
design-cage-code.document-source-cage-code (FK) CAGESTDDOC-DEFMAT / 433
document-alphanumeric-identifier (FK) design-cage-code.document-source-cage-code (FK)
document-type-code (FK) material-document-identifier.(document-alphanumeric-identifier,document-type-code) (FK)

defines defines
P
P CAGESTDDOCREV / 431 (from 11STDS1)
CAGESTDDOC-MATID / 434
document-source-cage-code
CAGESTDDOC-PIN / 436 design-cage-code (FK)
document-alphanumeric-identifier

B-188
design-cage-code (FK) document-type-code material-document-identifier.(material-generic-identifier,material-document-identifier) (FK)
part-identifier (FK) document-generic-revision material-identification (FK)
APPENDIX B
MIL-STD-2549

document-alphanumeric-identifier (FK)
document-type-code (FK)

may define may define

has status Assertion: The relation of Assertion: The relation of is documented by
CAGESTDDOCREV/ 431 to CAGESTDDOCREV / 431 to
STDDOCREV-PIN / 436 is 1:P CAGESTDMATSTAT / 434 is 1:P
if the product-type-code in if the product-type-code in
CAGESTDDOC / 430 is 'P' (for part), CAGESTDDOC / 430 is 'M' (for material),
and is 1:0 for all other values and is 1:0 for all other values of
P product-type-code.
of product-type-code. P
CAGESTDDOCRV-PINSTAT / 437
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

CAGESTDDOCRV-MATSTAT / 435
design-cage-code.(design-cage-code,document-source-cage-code) (FK)
part-identifier (FK) design-cage-code.(design-cage-code,document-source-cage-code) (FK) (AK1)
document-generic-revision (FK) material-document-identifier (FK)
material-identification (FK) (AK1)
document-alphanumeric-identifier (FK) document-generic-revision (FK) (AK1)
document-type-code (FK)
part-status-code document-alphanumeric-identifier (FK) (AK1)
document-type-code (FK)
material-status-code
FIGURE 11STDS5
STANDARDIZATION DOCUMENTS
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.11.3. Table 402, Standardization documents issued by an organization identified by acronym

(ORGSTDDOC). This table is a subcategory of Table STDDOC/400 for the case where the value of enterprise-
identification-type-code in Table 002 is 'ORG'. It contains the subset of standardization documents which are
issued by organizations identified by an acronym. Due to parallel categorization, this table is a de facto child of
Table ORG-NUM-DOC/024. Because it is a de facto child of Table 024, it has the same six subtypes as Table 024;
thus, the subcategories are: INTSTDDOC/404, FOREIGNGOVSTDDOC/405, FOREIGN-NONGOVSTDDOC/
406, USNONGOVSTDDOC/407, USDODSTDDOC/408, and OTHERUSGOVSTDDOC/409.

a. Sometimes more than one organization will issue the same document by applying an alias identifier. For
example: (1) ANSI's document Y14.24M is an alias for ASTM's document Y14.24M and (2) DNA's
document DNA INST 5010.18 is an alias for Army's document AR 70-37. If this document is an alias for
a document issued by another organization, the controlling document organization and identifier are
entered as the controlling-document-enterprise-acronym-identification-code (CORGID402) and
controlling-document-alphanumeric-identifier (CDOCNO402), respectively.

b. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 402 assumes the role
controlling-document-alphanumeric-identifier (CDOCNO402).

c. Attribute document-source-organization-identifier (SRCORG024) inherited from Table 402 assumes the

role controlling-document-source-enterprise-acronym-identification-code (CORGID402).

d. Because this table is a de facto child of Table 024, document-source-enterprise-identifier (SRCENT020)

inherited from Table 400 is really a document-source-organization-identifier (SRCORG024) existing in
Table 024. Therefore, SRCENT020 assumes the identity SRCORG024.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCORG024 document-source-organization-identifier 0096 FK

CDOCNO402 controlling-document-alphanumeric-identifier 0003 FK, O

CORGID402 controlling-document-source-enterprise-acronym- 0002 FK, O
identification-code

B.5.11.4. Table 403, Revisions to standardization documents issued by an organization identified by acronym
(ORGSTDDOCREV). This table is a subcategory of Table STDDOCREV/401 for the case where the value of
enterprise-identification-type-code in Table 002 is 'ORG'. It contains revisions to the subset of standardization
documents which are issued by organizations identified by an acronym. Due to parallel categorization, this table is
a de facto child of Table ORGSTDDOC/402. Because it is a de facto child of Table 402, it has the same six
subtypes as Table 402; however, these are not shown graphically.

a. Because this table is a de facto child of Table 402, document-source-enterprise-identifier (SRCENT020)

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCGOV409 united-states-government-nondefense-document-source- 0002 FK
enterprise-acronym-identification-code

SERIES409 standardization-document-series-type-code 0242 M

B.5.11.11. Table 410, Standardization documents issued by a U.S. defense secretariate organization (DEFSEC-
STDDOC). This table is a subcategory of Table DOD-STDDOC/408 for the case where the value of united-states-
defense-department-organization-type-identifier (DODTYP034) in Table 034 is 'OSD'. It contains the subset of
standardization documents which are issued by U.S. Office of the Secretary of Defense organizations identified by
an acronym. The three subcategories shown are for the case where the value of OSDORG410 is 'DOD' and are
included as examples because of the specific numbering rules associated with them. Other categories for this case
which are not shown graphically would include 'USDODD' (DOD Directives), 'USDODI' (DOD Instructions),
'USDODP' (DOD Procedures), etc. (For archival purposes, 'BULL' [for military bulletins] could be included.) If it
is desired that specific document identification rules be enforced by the database for other series of documents,
subcategories may be created based on the united-states-defense-secretariate-design-enterprise-acronym-
identification-code (OSDORG410) and standardization-document-series-type-code (SERIES408 in Table 408).

a. Attribute united-states-defense-department-document-source-enterprise-acronym-identification-code
(SRCDOD408) inherited from Table 408 assumes the role united-states-defense-secretariate-document-
source-enterprise-acronym-identification-code (SRCOSD410).

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCOSD410 united-states-defense-secretariate-document-source- 0002 FK
enterprise-acronym-identification-code

B.5.11.12. Table 411, U.S. defense standards (USDEFSTD). This table is a subcategory of Table DEFSEC-
STDDOC/410 for the case where the value of united-states-defense-secretariate-design-enterprise-acronym-
identification-code (SRCOSD410) in Table 410 is 'DOD' and the value of standardization-document-series-type-
code (SERIES408) in Table 408 is 'STD'. It contains the subset of U.S. OSD standardization documents which are
standards.

a. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 410 assumes the role
united-states-defense-standard-document-alphanumeric-identifier (STDNUM411).

Code Data Element Title DED Key

DOCTYP010 document-type-code 0004 FK
SRCOSD410 united-states-defense-secretariate-document-source- 0002 FK
enterprise-acronym-identification-code
STDNUM411 united-states-defense-standard-document-alphanumeric- 0003 FK
identifier

B-193
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.11.13. Table 412, U.S. defense specifications (USDEFSPEC). This table is a subcategory of Table DEFSEC-
STDDOC/410 for the case where the value of united-states-defense-secretariate-design-enterprise-acronym-
identification-code (SRCOSD410) in Table 410 is 'DOD' and the value of standardization-document-series-type-
code (SERIES408) in Table 408 is 'SPEC'. It contains the subset of U.S. OSD standardization documents which
are specifications.

a. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 410 assumes the role
united-states-defense-specification-document-alphanumeric-identifier (SPCNUM412).

Code Data Element Title DED Key

DOCTYP010 document-type-code 0004 FK
SPCNUM412 united-states-defense-specification-document-alphanumeric- 0003 FK
identifier
SRCOSD410 united-states-defense-secretariate-document-source- 0002 FK
enterprise-acronym-identification-code

B.5.11.14. Table 413, U.S. defense handbooks (USDEFHDBK). This table is a subcategory of Table DEFSEC-
STDDOC/410 for the case where the value of united-states-defense-secretariate-design-enterprise-acronym-
identification-code (SRCOSD410) in Table 410 is 'DOD' and the value of standardization-document-series-type-
code (SERIES408) in Table 408 is 'HDBK'. It contains the subset of U.S. OSD standardization documents which
are handbooks. (Note: Do not confuse DOD handbooks with DLA handbooks.)

a. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 410 assumes the role
united-states-defense-handbook-document-alphanumeric-identifier (HBKNUM413).

Code Data Element Title DED Key

DOCTYP010 document-type-code 0004 FK
HBKNUM413 united-states-defense-handbook-document-alphanumeric- 0003 FK
identifier
SRCOSD410 united-states-defense-secretariate-document-source- 0002 FK
enterprise-acronym-identification-code

B.5.11.15. Tables 414 through 419. Reserved.

B.5.11.16. Table 420, Standardization documents which define part numbers (ORSSTDDOC-DEFPIN). This
table is a subcategory of Table ORGSTDDOC/402 for the case where the value of product-type-code (PRDTYP400)
in Table 400 is 'P'. It contains the subset of standardization documents consisting of those documents which are
issued by an organization identified by an acronym and which define parts and identify them by part number.

a. Attribute document-source-organization-identifier (SRCORG024) inherited from Table 402 assumes the

role design-enterprise-acronym-identification-code (DESORG420).

Code Data Element Title DED Key

DESORG420 design-enterprise-acronym-identification-code 0002 FK
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK

B-194
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.11.17. Table 421, Standardization documents which define materials (ORGSTDDOC-DEFMAT). This
table is a subcategory of Table ORGSTDDOC/402 for the case where the value of product-type-code (PRDTYP400)
in Table 400 is 'M'. It contains the subset of standardization documents consisting of those documents which are
issued by a organization identified by an acronym and which define materials and parts not identified by part
number.

a. Attribute document-source-organization-identifier (SRCORG024) inherited from Table 402 assumes the

role design-enterprise-acronym-identification-code (DESORG421).

b. The attributes document-alphanumeric-identifier (DOCNUM020) and document-type-code

(DOCTYP010) inherited from Table 402 are concatenated and assume the role material-document-
identifier (MATDOC421). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

DESORG421 design-enterprise-acronym-identification-code 0002 FK
MATDOC421 material-document-identifier 0192 FK

B.5.11.18. Table 422, Material release status correlated with standardization document revision
(ORGSTDDOCRV-MATSTAT). This table correlates material identifiers (not part numbers) to the specific
standardization document revision(s) in which they are defined and indicates the release status of the material.

a. For each instance in this table, the value of the combination of document-type-code (DOCTYP010) and
document-alphanumeric-identifier (DOCNUM020) must be the same as the value of material-document-
identifier (MATDOC421).

b. Attribute design-enterprise-acronym-identification-code (DESORG421) inherited from Table 201 and

document-source-organization-identifier (SRCORG024) inherited from Table 403 must both have the
same value. Therefore they merge and assume the identity design-enterprise-acronym-identification-code
(DESORG421).

Code Data Element Title DED Key

DESORG421 design-enterprise-acronym-identification-code 0002 FK, AK1
DOCNUM020 document-alphanumeric-identifier 0003 FK, AK1
DOCREV011 document-generic-revision-identifier 0243 FK, AK1
DOCTYP010 document-type-code 0004 FK
MATDOC421 material-document-identifier 0192 FK
MATIDN200 material-product-identifier 0038 FK, AK1

MATSTA422 material-product-status-code 0035 M

B.5.11.19. Table 423, Part release status correlated with standardization document revision (ORGSTDDOCRV-
PINSTAT). This table correlates part identifiers to the specific standardization document revision(s) in which they
are defined and indicates the release status of the part.

B-195
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. For each instance in this table, the combination of the value of document-alphanumeric-identifier
(DOCNUM020) and document-type-code (DOCTYP010) must be the same as the combination of the
values of the same fields for the parent instance in Table STDPIN/211.

b. Attribute design-enterprise-acronym-identification-code (DESORG420) inherited from Table 211 and

Code Data Element Title DED Key

DESORG420 design-enterprise-acronym-identification-code 0002 FK
DOCREV011 document-generic-revision-identifier 0243 FK
PARNUM210 part-product-identifier 0024 FK

DOCNUM020 document-alphanumeric-identifier 0003 FK

DOCTYP010 document-type-code 0004 FK
PARSTA423 part-product-status-code 0035 M

B.5.11.20. Tables 424 through 429. Reserved.

B.5.11.21. Table 430, Standardization documents issued by an organization identified by CAGE code
(CAGESTDDOC). This table is a subcategory of Table STDDOC/400 for the case where the value of enterprise-
identification-type-code in Table 002 is 'CAG'. It contains the subset of standardization documents which are
issued by organizations identified by a CAGE code (or NSCM). Due to parallel categorization, this table is a de
facto child of Table CAGE/022.

a. Because this table is a de facto child of Table 022, document-source-enterprise-identifier (SRCENT020)

inherited from Table 400 is really a document-source-enterprise-defense-logistics--assigned-identification-
code (SRCCAG022) existing in Table 022. Therefore, SRCENT020 assumes the identity SRCCAG022.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCCAG022 document-source-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B.5.11.22. Table 431, Revisions to standardization documents issued by an organization identified by CAGE
code (CAGESTDDOCREV). This table is a subcategory of Table STDDOCREV/401 for the case where the value
of enterprise-identification-type-code in Table 002 is 'CAG'. It contains revisions to the subset of standardization
documents which are issued by organizations identified by a CAGE code (or NSCM).

a. Due to parallel categorization, this table is a de facto child of Table CAGESTDDOC/430.

b. Because this table is a de facto child of Table 430, document-source-enterprise-identifier (SRCENT020)

inherited from Table 401 is really a document-source-enterprise-defense-logistics--assigned-identification-
code (SRCCAG022) existing in Table 430. Therefore, SRCENT020 assumes the identity SRCCAG022.

B-196
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

B.5.11.23. Table 432, Standardization documents which define part numbers (CAGESTDDOC-DEFPIN). This
table is a subcategory of Table CAGESTDDOC/430 for the case where the value of product-type-code
(PRDTYP400) in Table 400 is 'P'. It contains the subset of standardization documents consisting of those
documents which are issued by an organization identified by a CAGE code (or NSCM) and which define parts and
identify them by part number.

a. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 430 assumes the role design-enterprise-defense-logistics--assigned-identification-
code (DESCAG432).

Code Data Element Title DED Key

DESCAG432 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK

B.5.11.24. Table 433, Standardization documents which define materials and are issued by an organization
identified by a CAGE code (CAGESTDDOC-DEFMAT). This table is a subcategory of Table ORGSTDDOC/402
for the case where the value of product-type-code (PRDTYP400) in Table 400 is 'M'. It contains the subset of
standardization documents consisting of those documents which are issued by a organization identified by a CAGE
code (or NSCM) and which define materials and parts not identified by part number.

a. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 430 assumes the role design-enterprise-defense-logistics--assigned-identification-
code (DESCAG433).

b. The attributes document-alphanumeric-identifier (DOCNUM020) and document-type-code

(DOCTYP010) inherited from Table 430 are concatenated and assume the role material-document-
identifier (MATDOC433). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

DESCAG433 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
MATDOC433 material-document-identifier 0192 FK

B.5.11.25. Table 434, Materials defined by standardization document (CAGESTDDOC-MATID). This table is
a subtype of Table CAGE-MATID/205 containing the subset of material identifiers which is limited to those

B-197
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

materials and parts which are identified by a standardization document issued by an organization which is
identified by a CAGE code (or NSCM).

a. Fields DESCAG205 inherited from Table 205 and DESCAG433 inherited from Table 433 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG434).

b. Attribute material-product-generic-identifier (MATGID200) inherited from Table 205 and material-

document-identifier (MATDOC433) inherited from Table 433 must both have the same value. Therefore
they merge and assume the identity material-document-identifier (MATDOC433).

Code Data Element Title DED Key

DESCAG434 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
MATDOC433 material-document-identifier 0192 FK
MATIDN200 material-product-identifier 0038 FK

B.5.11.26. Table 435, Material release status correlated with standardization document revision
(CAGESTDDOCRV-MATSTAT). This table correlates material identifiers (not part numbers) to the specific
standardization document revision(s) in which they are defined and indicates the release status of the material.

b. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 431 and design-enterprise-defense-logistics--assigned-identification-code
(DESCAG434) inherited from Table 434 must both have the same value. Therefore they merge and
assume the identity design-enterprise-defense-logistics--assigned-identification-code (DESCAG434).

Code Data Element Title DED Key

DESCAG434 design-enterprise-defense-logistics--assigned-identification- 0001 FK, AK1
code
DOCNUM020 document-alphanumeric-identifier 0003 FK, AK1
DOCREV011 document-generic-revision-identifier 0243 FK, AK1
DOCTYP010 document-type-code 0004 FK
MATDOC433 material-document-identifier 0192 FK
MATIDN200 material-product-identifier 0038 FK, AK1

MATSTA435 material-product-status-code 0035 M

B.5.11.27. Table 436, Part numbers defined by standardization documents (CAGESTDDOC-PIN). This table is
a subtype of Table CAGEPIN/212 containing the subset of part numbers which are those part numbers identified
by a standardization document (instead of by a drawing or program-unique specification) that is issued by a
standards-issuing organization identified by a CAGE code (or NSCM).

B-198
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. The value of DOCTYP010 must be the same as the value of document-type-code (DOCTYP212) for the
super-type in Table 212.

b. Fields DESCAG212 inherited from Table 212 and DESCAG432 inherited from Table 432 must be the
same; therefore, they assume the identity design-enterprise-defense-logistics--assigned-identification-code
(DESCAG436).

Code Data Element Title DED Key

DESCAG436 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
PARNUM210 part-product-identifier 0024 FK

DOCNUM020 document-alphanumeric-identifier 0003 FK

DOCTYP010 document-type-code 0004 FK

B.5.11.28. Table 437, Part release status correlated with standardization document revision
(CAGESTDDOCRV-PINSTAT). This table correlates part identifiers to the specific standardization document
revision(s) in which they are defined and indicates the release status of the part.

b. Attribute document-source-enterprise-defense-logistics--assigned-identification-code (SRCCAG022)

inherited from Table 431 and design-enterprise-defense-logistics--assigned-identification-code
(DESCAG436) inherited from Table 436 must both have the same value. Therefore they merge and
assume the identity design-enterprise-defense-logistics--assigned-identification-code (DESCAG436).

Code Data Element Title DED Key

DESCAG436 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCREV011 document-generic-revision-identifier 0243 FK
PARNUM210 part-product-identifier 0024 FK

DOCNUM020 document-alphanumeric-identifier 0003 FK

DOCTYP010 document-type-code 0004 FK
PARSTA437 part-product-status-code 0035 M

B.5.11.29. Tables 438 and 439. Reserved.

B.5.11.30. Table 440, Standardization documents issued by a commercial enterprise (COMSTDNUMDOC).

This table is a subcategory of Table STDDOC/400 for the case where the value of enterprise-identification-type-
code in Table 002 is 'COM'. It contains the subset of standardization documents which are issued by commercial
enterprises. Due to parallel categorization, this table is a de facto child of Table COMPANY-NUM-DOC/026. It
is also a de facto subtype of Table COMSTDDOC/914.

B-199
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Because this table is a de facto subtype of Table 914, document-alphanumeric-identifier (DOCNUM020)

inherited from Table 400 is really a document-identifier (DOCIDN010) existing in Table 914.

b. Because this table is a de facto subtype of Table 914, document-source-enterprise-identifier (SRCENT020)

inherited from Table 400 is really a commercial-document-source-enterprise-name (SRCCOM910)
existing in Table 914. Therefore, SRCENT020 assumes the identity SRCCOM910.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM910 commercial-document-source-enterprise-name 0170 FK

B.5.11.31. Table 441, Revisions to standardization documents issued by a commercial enterprise

(COMSTDDOCREV). This table is a subcategory of Table STDDOCREV/401 for the case where the value of
enterprise-identification-type-code in Table 002 is 'COM'. It contains revisions to the subset of standardization
documents which are issued by commercial enterprises. Due to parallel categorization, this table is a de facto child
of Table COMSTDDOC/440.

a. Because this table is a de facto child of Table 401, commercial-document-source-enterprise-name

(SRCCOM910) inherited from Table 440 is really a document-source-enterprise-identifier (SRCENT020)
existing in Table 401. Therefore, SRCCOM910 assumes the identity SRCCOM026.

Code Data Element Title DED Key

B.5.11.32. Tables 442 through 449. Reserved.

B-200
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.12. Modification requests and instructions. The entity tables numbered in the range of 450 through 499
contain the identification of, and information concerning, modification requests (including Proposed Technical
Improvements, Proposed Military Improvements, and Materiel Improvement Program requests, etc.) and
modification instructions (including technical directives, time-compliance technical orders, rapid action change
orders, modification work orders, SHIPALTs, etc.) and modification kit information. Modification requests serve
the same purpose as ECPs in that they initiate a request to change hardware. They differ from ECPs in that they
do not cause a change to existing engineering drawings, unless they result in the initiation of an ECP.
Modification instructions are used to direct that changes be made to fielded hardware or software. The may be the
result of an approved modification request or of an approved ECP. The relationship between these various entity
tables are depicted in Figures 12MOD1 through 12MOD5.

B.5.12.1. Table 450, Modification requests (MODREQ). This table is a subcategory of Table GENERIC-DOC/
010 for the case where the value of document-type-code is 'MODREQ'. It contains the subset of documents which
are used to request permission to modify inventory assets on a permanent or temporary basis. Three of the possible
subcategories are shown: PTIREQ/451, PMIREQ/452, and MIPREQ/453. Other subcategories may be added with
proper authority.

a. Attribute document-type-code (DOCTYP010) inherited from Table 010 assumes the role modification-
request-document-type-code (MRQTYP450).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
MRQTYP450 modification-request-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

MODSUB450 modification-request-document-subsidiary-type-code 0142

B.5.12.2. Table 451, Proposed technical improvement modification requests (PTIREQ). This table is a
subcategory of Table MODREQ/450 for the case where the value of modification-request-document-subsidiary-
type-code is 'PTI'. It contains the subset of documents which are proposed technical improvement requests.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
MRQTYP450 modification-request-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B-201
GENERIC-DOC / 010 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code

TECHMAN / 550 (from 14TM1)

document-type-code document-source-entity-identifier
MODREQ document-identifier
TECHMAN
MODREQ / 450 (see 12MOD2)
MODINST
document-source-entity-identifier (FK)
document-identifier (FK)
MODREQ.document-type-code (FK)
may be changed
as a result of

may result in

MODINST / 460 (see 12MOD3, 12MOD5, 13TRK2)

B-202
modification-instruction-source-identifier.document-source-entity-identifier (FK)
APPENDIX B
MIL-STD-2549

modification-instruction-identifier.document-identifier (FK)
MODINST.document-type-code (FK)
modification-request-source-identifier.document-source-entity-identifier (FK)
modification-request-identifier.document-identifier (FK)
MODREQ (FK)

may direct changes to

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

TM-MODINST / 461
modification-instruction-source-identifier (FK)
modification-instruction-identifier (FK)
MODINST (FK)
document-source-entity-identifier (FK)
document-identifier (FK)
FIGURE 12MOD1 TECHMAN (FK)
MODIFICATION REQUESTS/INSTRUCTIONS
MODREQ / 450 (from 12MOD1)
document-source-entity-identifier
document-identifier
MODREQ
modification-request-type-code

modification-request-type-code
PTI

B-203
PMI
APPENDIX B
MIL-STD-2549

PTIREQ / 451
document-source-entity-identifier (FK)
document-identifier (FK) MIPREQ / 453
MODREQ (FK) document-source-entity-identifier (FK)
PMIREQ / 452 document-identifier (FK)
document-source-entity-identifier (FK) MODREQ (FK)
document-identifier (FK)
MODREQ (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 12MOD2
MODIFICATION REQUESTS
MODINST / 460 (from 12MOD1)
modification-instruction-source-identifier
modification-identifier
MODINST
dod-indicator-code

dod-indicator-code
D C

DOD-MODINST / 462
us-dod-document-source-organization-code.modification-instruction-source-identifier (FK) COM-MODINST / 463
modification-instruction-alphanumeric-identifier.modification-identifier (FK) modification-instruction-source-identifier (FK)
MODINST (FK) modification-identifier (FK)
MODINST (FK)
modification-instruction-type-code

NAVAIRTM / 561 (from 14TM1)

modification-instruction-type-code
us-dod-document-source-organization-code
document-alphanumeric-identifier USATM / 557 (from 14TM1)
TECHMAN us-dod-document-source-organization-code
us-army-technical-manual-identifier
TECHMAN

MWO
TECHDIR
may have associated

B-204
TECHDIR / 465 MWO / 467
APPENDIX B

us-dod-document-source-organization-code (FK)
MIL-STD-2549

us-dod-document-source-organization-code (FK)
technical-directive-alphanumeric-identifier.modification-instruction-alphanumeric-identifier (FK) mwo-alphanumeric-identifier.modification-instruction-alphanumeric-identifier (FK)
MODINST (FK) MODINST (FK)

is associated with
may have RAC TCTO
P
TM-MWO / 468
us-dod-document-source-organization-code (FK)
RAC / 464 mwo-alphanumeric-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

us-dod-document-source-organization-code (FK) TCTO / 466 (see 14TM1) MODINST (FK)

rac-alphanumeric-identifier.modification-instruction-alphanumeric-identifier (FK) us-dod-document-source-organization-code (FK) us-army-technical-manual-identifier (FK)
MODINST (FK) modification-instruction-alphanumeric-identifier (FK) TECHMAN (FK)
MODINST (FK)
TECHMAN (FK)
document-alphanumeric-identifier (FK)

FIGURE 12MOD3
MODIFICATION INSTRUCTIONS (Part 1 of 3)
DOD-MODINST / 462 (from 12MOD3)
us-dod-document-source-organization-code.modification-instruction-source-identifier
modification-alphanumeric-identifier.modification-identifier
MODINST
modification-instruction-type-code

modification-instruction-type-code

ORDALT
NUCALT

ORDALT / 469 MACHALT

us-dod-document-source-organization-code (FK) FLDCHG NUCALT / 472
modification-alphanumeric-identifier (FK) us-dod-document-source-organization-code (FK)
MODINST (FK) modification-alphanumeric-identifier (FK)
MODINST (FK)
SHIPALT

B-205
MACHALT / 470
APPENDIX B
MIL-STD-2549

us-dod-document-source-organization-code (FK) FLDCHG / 473

modification-alphanumeric-identifier (FK) us-dod-document-source-organization-code (FK)
MODINST (FK) modification-alphanumeric-identifier (FK)
MODINST (FK)

SHIPALT / 471
us-dod-document-source-organization-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

modification-alphanumeric-identifier (FK)
MODINST (FK)

FIGURE 12MOD4
MODIFICATION INSTRUCTIONS (Part 2 of 3)
ECP-RETRO / 290 (from 6ECP5)
ecp-cage-code
MODINST / 460 (from 12MOD1)
ecp-alphanumeric-identifier
ECP modification-instruction-source-organization-code may apply to
ecp-revision modification-instruction-identifier
MODINST may apply to
BASETRACK / 515 (from 13TRK2)
product--tracking-base--identifier
results in manufacturer-cage-code
creation of product-effectivity-tracking-type
is a result of product-tracking-identifier
GENERIC-PIN / 210 (from 5PIN2)
design-enterprise-identifier
ECP-MODINST / 493
part-identifier
modification-instruction-source-organization-code (FK)
modification-instruction-identifier (FK) may be starting
MODINST (FK) effectivity for may be starting
effectivity for
ecp-cage-code (FK)
may be modified may be ending
ecp-alphanumeric-identifier (FK)
as required by effectivity for may be ending
ECP (FK)
ecp-revision (FK) effectivity for

may require MOD-PIN / 491

may identify design-enterprise-identifier (FK)
part-identifier (FK)
modification-instruction-source-organization-code (FK)
Z modification-instruction-identifier (FK)
MODKIT / 490 MODINST (FK)
product--tracking-base--identifier (FK)
modification-kit-identifier.(design-enterprise-identifier,part-identifier) (FK)

B-206
manufacturer-cage-code (FK)
modification-instruction-source-organization-code (FK) product-effectivity-tracking-type (FK)
modification-instruction-identifier (FK) starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
APPENDIX B

MODINST (FK)
MIL-STD-2549

ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK)

may be used to modify may require modification by

P
MODKIT-PART / 492 GENERIC-MAT / 200
design-enterprise-identifier MOD-MAT / 494
modification-kit-identifier (FK) modification-instruction-source-organization-code (FK)
modification-instruction-source-organization-code (FK) material-generic-identifier
material-identification modification-instruction-identifier (FK)
modification-instruction-identifier (FK) MODINST (FK)
MODINST (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

design-enterprise-identifier (FK)
design-enterprise-identifier (FK) material-generic-identifier (FK)
part-identifier (FK) material-identification (FK)
product--tracking-base--identifier (FK) may be modified product--tracking-base--identifier (FK)
manufacturer-cage-code (FK) as required by manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK) product-effectivity-tracking-type (FK)
starting-effectivity-product-tracking-identifier (FK) starting-effectivity-product-tracking-identifier.product-tracking-identifier (FK)
ending-effectivity-product-tracking-identifier.product-tracking-identifier (FK)

FIGURE 12MOD5
MODIFICATION INSTRUCTIONS (Part 3 of 3)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.12.3. Table 452, Proposed military improvement modification requests (PMIREQ). This table is a
subcategory of Table MODREQ/450 for the case where the value of modification-request-document-subsidiary-
type-code is 'PMI'. It contains the subset of documents which are proposed military improvement requests.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
MRQTYP450 modification-request-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.12.4. Table 453, Modification requests via the MIP (MIPREQ). This table is a subcategory of Table
MODREQ/450 for the case where the value of modification-request-document-subsidiary-type-code is 'MP'. It
contains the subset of documents which are Modification Proposals (AF Form 1067).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
MRQTYP450 modification-request-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.12.5. Table 454, Correlation of ECPs to modification requests (ECPREQ). This table correlates ECPs with
the modification requests which cause them to be issued.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
MRQTYP450 modification-request-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.12.6. Tables 455 through 459. Reserved.

B.5.12.7. Table 460, Modification Instructions (MODINST). This table is a subcategory of Table GENERIC-
DOC/010 for the case where the value of document-type-code is 'MODINST'. It contains documents which are
used to direct the modification of inventory assets. It has two subcategories: DOD-MODINST/462 and COM-
MODINST/463.

a. Attribute document-identifier (DOCIDN010) inherited from Table 010 assumes the role modification-
instruction-document-identifier (MINIDN460).

b. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 010 assumes the role
modification-instruction-document-source-entity-identifier (MINSRC460).

B-207
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Attribute document-type-code (DOCTYP010) inherited from Table 010 assumes the role modification-
instruction-document-type-code (MINTYP460).

d. Attribute document-identifier (DOCIDN010) inherited from Table 450 assumes the role modification-
request-document-identifier (MRQIDN460).

e. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 450 assumes the role
modification-request-document-source-entity-identifier (MRQSRC460).

Code Data Element Title DED Key

MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK
MINTYP460 modification-instruction-document-type-code 0004 FK

MRQIDN460 modification-request-document-identifier 0122 FK, O

MRQSRC460 modification-request-document-source-entity-identifier 0033 FK, O
MRQTYP450 modification-request-document-type-code 0004 FK, O
CNXDAT460 modification-instruction-document-rescission-date 0082
DODCOD460 document-format-compliance-indicator-code 0143 M
EFFDAT460 modification-instruction-document-effective-date 0082 M
ISSDAT460 modification-instruction-document-issue-date 0082 M
MODDES460 modification-instruction-document-task-description-text 0253
WKHOUR460 equipment-modification-process-period-work-hour-quantity 0087

B.5.12.8. Table 461, Correlation of modification instructions to technical manuals (MODINST-TM). This
table correlates modification instructions to the basic technical manuals (or technical orders) to which they apply.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK
MINTYP460 modification-instruction-document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.12.9. Table 462, DOD modification requests (DOD-MODINST). This table is a subcategory of Table
MODINST/460 for the case where the value of document-defense-department-indicator-code is 'D'. It contains the
subset of modification instructions which are identified by a U.S. DOD acronym (as the source) and an
alphanumeric identifier. Nine of the possible subcategories are shown: RAC/464, TECHDIR/465, TCTO/466,
MWO/467, ORDALT/469, MACHALT/470, SHIPALT/471, NUCALT/472, and FLDCHG/473. Other
subcategories may be added at command discretion.

B-208
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Attribute modification-instruction-document-source-entity-identifier (MINSRC460) inherited from Table

460 assumes the role modification-instruction-document-alphanumeric-identifier (MINNUM462).

b. Attribute modification-instruction-document-source-entity-identifier (MINSRC460) inherited from Table

460 assumes the role united-states-defense-department-document-source-enterprise-acronym-
identification-code (SRCDOD462).

Code Data Element Title DED Key

MINNUM462 modification-instruction-document-alphanumeric-identifier 0003 FK
MINTYP460 modification-instruction-document-type-code 0004 FK
SRCDOD462 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

MINSUB462 modification-instruction-document-subsidiary-type-code 0141 M

B.5.12.10. Table 463, Commercial modification instructions (COM-MODINST). This table is a subcategory of
Table MODINST/460 for the case where the value of document-defense-department-indicator-code is 'C'. It
contains the subset of modification instructions which are identified by commercial best practices. Subcategories
may be added at command discretion.

Code Data Element Title DED Key

B.5.12.11. Table 464, RAC identification (RAC). This table is a subcategory of DOD-MODINST/462 for the
case where the value of the modification-instruction-document-subsidiary-type-code (MINSUB462) in Table 462 is
'RAC'. It contains the unique and primary identification of Navy Rapid Action Change (RAC) orders as defined in
Mil-M-81748. This table also correlates the RAC order with the NAVAIR technical manual which is impacted or
affected by it.

a. Attribute modification-instruction-document-alphanumeric-identifier (MINNUM462) inherited from

Table 462 assumes the role rapid-action-change-order-document-alphanumeric-identifier (RACNUM464).

Code Data Element Title DED Key

MINTYP460 modification-instruction-document-type-code 0004 FK
RACNUM464 rapid-action-change-order-document-alphanumeric-identifier 0003 FK
SRCDOD462 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

DOCNUM020 document-alphanumeric-identifier 0003 FK

TMNTYP550 technical-manual-document-type-code 0004 FK
CHGTYP464 rapid-action-change-order-document-change-type-code 0256 M

B-209
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.12.12. Table 465, Technical directive identification (TECHDIR). This table is a subcategory of DOD-
MODINST/462 for the case where the value of the modification-instruction-document-subsidiary-type-code
(MINSUB462) in Table 462 is 'TECHDIR'. It contains the unique and primary identification of NAVAIR
Technical Directives as defined in Mil-D-81992 and NAVAIR Technical Manual 00-25-300. Technical Directives
are independent of technical manuals.

a. Attribute modification-instruction-document-alphanumeric-identifier (MINNUM462) inherited from

Table 462 assumes the role united-states-naval-air-technical-directive-document-alphanumeric-identifier
(TDIRNO465).

Code Data Element Title DED Key

MINTYP460 modification-instruction-document-type-code 0004 FK
SRCDOD462 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TDIRNO465 united-states-naval-air-technical-directive-document- 0003 FK
alphanumeric-identifier

CATCOD465 technical-directive-document-category-code 0247 M

LVLCOD465 technical-directive-document-maintenance-level-code 0254
TSKTYP465 technical-directive-document-task-type-code 0249 M

B.5.12.13. Table 466, Time-compliance technical order identification (TCTO). This table is a subcategory of
DOD-MODINST/462 for the case where the value of the modification-instruction-document-subsidiary-type-code
(MINSUB462) in Table 462 is 'TCTO'. It contains the unique and primary identification of Air Force time-
compliance technical orders as defined in MIL-T-9885, MIL-T-38804, and USAF TO 00-5-1. An Air Force time-
compliance technical order is a special case of Table USAFTO/560. Because of this, it follows the rules of both
entities.

Code Data Element Title DED Key

LVLCOD466 limited-duration-technical-order-document-maintenance- 0255

level-code
PRICOD466 limited-duration-technical-order-document-priority-code 0248 M

B.5.12.14. Table 467, Modification work order identification (MWO). This table is a subcategory of DOD-
MODINST/462 for the case where the value of the modification-instruction-document-subsidiary-type-code
(MINSUB462) in Table 462 is 'MWO'. It contains the unique and primary identification of Army Modification
Work Orders (MWO) as defined in Army Regulation 25-30.

a. Attribute modification-instruction-document-alphanumeric-identifier (MINNUM462) inherited from

Table 462 assumes the role united-states-army-modification-work-order-document-alphanumeric-
identifier (MWONUM467).

B-210
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

MINTYP460 modification-instruction-document-type-code 0004 FK
MWONUM467 united-states-army-modification-work-order-document- 0003 FK
alphanumeric-identifier
SRCDOD462 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

LVLCOD467 modification-work-order-document-maintenance-level-code 0250

PRICOD467 modification-work-order-document-priority-code 0246 M

B.5.12.15. Table 468, Correlation of MWOs to TMs (TM-MWO). This table contains the correlation of U.S.
Army Technical Manuals with the Modification Work Orders which impact or affect the TM (or the hardware they
describe).

a. Fields SRCDOD462 inherited from Table 462 and SRCDOD552 inherited from Table 557 must be the
same; therefore, they assume the identity united-states-defense-department-document-source-enterprise-
acronym-identification-code (SRCDOD468).

Code Data Element Title DED Key

ATMNUM557 united-states-army-technical-manual-document- 0003 FK
alphanumeric-identifier
MINTYP460 modification-instruction-document-type-code 0004 FK
MWONUM467 united-states-army-modification-work-order-document- 0003 FK
alphanumeric-identifier
SRCDOD468 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.12.16. Table 469, Ordnance alteration instruction identification (ORDALT). This table is a subcategory of
DOD-MODINST/462 for the case where the value of the modification-instruction-document-subsidiary-type-code
(MINSUB462) in Table 462 is 'ORDALT'. It contains the unique and primary identification of Ordnance
Alteration Instructions (ORDALTINST) as defined in MIL-STD-1662.

Code Data Element Title DED Key

B.5.12.17. Table 470, Machinery alteration instruction identification (MACHALT). This table is a subcategory
of DOD-MODINST/462 for the case where the value of the modification-instruction-document-subsidiary-type-
code (MINSUB462) in Table 462 is 'ORDALT'. It contains the unique and primary identification of Machinery
Alteration Instructions (MACHALTINST) as defined in DOD-STD-2140.

B-211
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

B.5.12.18. Table 471, Ship alteration instructions (SHIPALT). This table is a subcategory of DOD-MODINST/
462 for the case where the value of the modification-instruction-document-subsidiary-type-code (MINSUB462) in
Table 462 is 'SHIPALT'. It contains the unique and primary identification of Ship Alteration Instructions
(SHIPALTINST) as defined in OPNAVINST 4720.2.

Code Data Element Title DED Key

B.5.12.19. Table 472, Nuclear alteration instruction identification (NUCALT). This table is a subcategory of
DOD-MODINST/462 for the case where the value of the modification-instruction-document-subsidiary-type-code
(MINSUB462) in Table 462 is 'NUCALT'. It contains the unique and primary identification of Nuclear Alteration
Instructions (NUCALTINST) as defined in OPNAVINST 4720.2.

Code Data Element Title DED Key

B.5.12.20. Tables 473 through 489. Reserved.

B.5.12.21. Table 490, Modification kit identification (MODKIT). This table identifies the modification kit(s)
which are associated with a specific modification instruction and correlates them to the kit drawing(s) or other
design documentation which depicts them.

a. The attributes design-enterprise-identifier (DESENT210) and part-product-identifier (PARNUM210)

inherited from Table 210 are concatenated and assume the role modification-kit-product-identifier
(KITIDN490). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

KITIDN490 modification-kit-product-identifier 0245 FK
MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK

B-212
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

MINTYP460 modification-instruction-document-type-code 0004 FK

B.5.12.22. Table 491, Correlation of modification instructions to affected part numbers (MOD-PIN). This table
correlates the part number(s) affected by a modification instruction to the modification instruction and specifies the
effectivity of the modification.

a. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF491).

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF491).

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK
MINTYP460 modification-instruction-document-type-code 0004 FK
PARNUM210 part-product-identifier 0024 FK
STREFF491 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF491 product-ending-effectivity-sequential-tracking-identifier 0058 FK

B.5.12.23. Table 492, Correlation of modification kits to the parts to be modified (MODKIT-PART). This table
correlates the modification kit with the parts to be modified as directed by the modification instruction or ECP.

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
KITIDN490 modification-kit-product-identifier 0245 FK
MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK
MINTYP460 modification-instruction-document-type-code 0004 FK
PARNUM210 part-product-identifier 0024 FK

B.5.12.24. Table 493, Correlation of ECPs to modification instructions (ECP-MODINST). This table correlates
approved ECPs which require retrofit of fielded assets with the modification instructions which actually direct
depot/field units to perform the modification/retrofit.

B-213
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK
MINTYP460 modification-instruction-document-type-code 0004 FK

B.5.12.25. Table 494, Correlation of modification instructions to affected material (MOD-MAT). This table
correlates the material(s) (which are not identified by part number) that affected by a modification instruction to
the modification instruction and specifies the effectivity of the modification.

a. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-ending-effectivity-sequential-tracking-identifier (ENDEFF494).

b. Attribute product-sequential-tracking-identifier (TRKIDN515) inherited from Table 515 assumes the role
product-starting-effectivity-sequential-tracking-identifier (STREFF494).

Code Data Element Title DED Key

DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK
MINTYP460 modification-instruction-document-type-code 0004 FK
STREFF494 product-starting-effectivity-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

BASNUM500 product--tracking-base--identifier 0056 FK

ENDEFF494 product-ending-effectivity-sequential-tracking-identifier 0058 FK

B.5.12.26. Tables 495 through 499. Reserved.

B-214
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.13. Serial, lot and other tracking numbers. Entity tables numbered in the range of 500 through 549 contain
the information concerning the product-tracking base-identifier (common base number) used for serialization,
serial numbers (both Government and manufacturer), lot numbers, date codes and block numbers. These numbers
are used to state effectivity of changes and to track actual parts and materials in use. This section includes the
correlation of these tracking numbers to part numbers or material identifiers, and the correlation between the
various types of tracking numbers, including the changes in part number resulting from rework/remanufacture, or
the change in lot number resulting from the formation of composite lots. The relationships between these various
tracking number entity tables are depicted in Figures 13TRK1 through 13TRK5.

B.5.13.1. Table 500, Base identifier for serialization and lot numbering (BASE). This table contains the
product-tracking base-identifier for serialization and lot numbering of parts and materials. In order of preference,
the product-tracking base-identifier is:

a. the Type and Model portion (see Table B-II) of the configuration item designation as assigned in
accordance with MIL-STD-196, MIL-STD-787, MIL-STD-1812 or AR 70-50/NAVMATINST
8800.4/AFR 82-1, or

b. the drawing number of tabulated part or assembly drawings, or

c. the drawing number of one of the non-tabulated parts (or assemblies) within the group of like items, or

d. the specification number of parts or materials defined by a program-unique specification or

standardization document, or

e. the part number of standard parts, or

f. the material identifier of any material defined in terms like class, grade, type, etc. (without a part
number).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 K

TRKSCD500 product-tracking--base-source-code 0103 M

B.5.13.2. Table 501, CI designation as product-tracking base-identifier (BASE-CI). This table is a subtype of
BASE/500 which contains the subset of Table 500 consisting of those product-tracking base-identifiers which are
based on CI designations. This is the preferred product-tracking base-identifier (see also: B.5.13.1 and Table B-
II).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

CIDESG693 configuration-item-product-designation-identifier 0045 FK

B-215
BASE / 500 (see 13TRK2)
product--tracking-base--identifier
product-tracking--base-source-code

product-tracking--base-source-code

D M

CI / 693 (from 19CI1) P

C
ci-designation
U S

may be a BASE-STDDOC / 504 (see 11STDS1)

Z BASE-PIN / 505 (see 5PIN2)
product--tracking-base--identifier (FK)
product--tracking-base--identifier (FK)
BASE-CI / 501
product--tracking-base--identifier (FK)
ci-designation (FK) is the common
base number for BASE-MAT / 506 (see 5PIN1)
BASE-DWG / 502 BASE-SPEC / 503 product--tracking-base--identifier (FK)
product--tracking-base--identifier (FK) product--tracking-base--identifier (FK) P
STDDOC / 400 (from 11STDS1)
document-source-enterprise-identifier
document-alphanumeric-identifier

B-216
is the common is the common
is the common document-type-code base number for base number for
base number for
APPENDIX B

product--tracking-base--identifier (FK)
MIL-STD-2549

is the common base number for GENERIC-PIN / 210 (from 5PIN2)

PICDWG / 060 (from 2DWG1)
PSPEC / 100 (from 3SPEC1) design-enterprise-identifier
design-cage-code part-identifier
drawing-alphanumeric-identifier design-cage-code
document-type-code document-alphanumeric-identifier product--tracking-base--identifier (FK)
is the common base number for document-type-code
ci-nomenclature P
is the common ci-nomenclature
base number for GENERIC-MAT / 200 (from 5PIN1)
design-enterprise-identifier
ci-nomenclature ci-nomenclature material-generic-identifier
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

material-identification
[BLANK] [NOT BLANK] [BLANK] [NOT BLANK]
P product--tracking-base--identifier (FK)
P P P
DWG-DWGBASE / 511
DWG-CIBASE / 510 PSPEC-CIBASE / 509 PSPEC-SPECBASE / 508
design-cage-code (FK)
design-cage-code (FK) design-cage-code (FK) design-cage-code (FK)
drawing-alphanumeric-identifier (FK)
drawing-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
document-type-code (FK)
document-type-code (FK) document-type-code (FK) document-type-code (FK)
product--tracking-base--identifier (FK)
product--tracking-base--identifier (FK) product--tracking-base--identifier (FK) product--tracking-base--identifier (FK)
FIGURE 13TRK1
COMMON BASE-NUMBER DEFINTION
is the (see 5PIN5, 5PIN6, 5PIN7, 6ECP3, 10RFD3) may be MODINST / 460 (from 12MOD1)
BASE / 500 (from 13TRK1) BASETRACK / 515 (with 13TRK3)
common incorporated
product--tracking-base--identifier modification-instruction-source-organization-code
base for manufacturer-cage-code.cage-code (FK) in modification-instruction-identifier
product-effectivity-tracking-type
MODINST
product-tracking-identifier
product--tracking-base--identifier (FK)
CAGE / 003 (from 1GEN1) may be the
manufacture-date may INCMODINST / 536
manufacturer of
cage-code manufacture-time incorporate modification-instruction-source-organization-code (FK)
modification-instruction-identifier (FK)
MODINST (FK)
manufacturer-cage-code (FK)
product-effectivity-tracking-type (FK)
product-tracking-identifier (FK)
product-effectivity-tracking-type product--tracking-base--identifier (FK)

B
G M
L
GSN / 517 MSN / 516
manufacturer-cage-code (FK) manufacturer-cage-code (FK)
government-serial-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK) manufacturer-serial-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
product--tracking-base--identifier (FK) product--tracking-base--identifier (FK)

GENERIC-PIN / 210 (from 5PIN2) LOTNUM / 518 (see 13TRK3)

design-enterprise-identifier manufacturer-cage-code (FK)
part-identifier product-lot-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
product--tracking-base--identifier (FK)
PINLOT-BLOCK / 525

B-217
design-enterprise-identifier (FK)
may be tracked by assertion: the relationships part-identifier (FK)
is assigned to
APPENDIX B
MIL-STD-2549

P LOTNUM / 518 to PIN-LOT / 523, manufacturer-cage-code (FK)

and LOTNUM / 518 to MAT-LOT / 526 product-lot-identifier (FK)
PIN-LOT / 523 (see 13TRK4,13TRK5) may be part of are mutually exclusive product-block-identifier (FK)
design-enterprise-identifier (FK)
may be part of product--tracking-base--identifier (FK)
part-identifier (FK)
manufacturer-cage-code (FK) (AK1)
product-lot-identifier (FK) (AK1) is assigned to may include
product--tracking-base--identifier (FK) BLOCKID / 520 (see 13TRK3)
product-quantity
manufacturer-cage-code (FK)
may include product-block-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
product--tracking-base--identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

may include
may be tracked by
P
may be may include PIN-GSN / 522 (see 13TRK5)
design-enterprise-identifier (FK) (AK1) PIN-MSN / 521 (see 13TRK5)
is tracked by
assigned part-identifier (FK) (AK1) design-enterprise-identifier (FK)
to manufacturer-cage-code (FK) (AK1) part-identifier (FK)
government-serial-identifier (FK) may be also manufacturer-cage-code (FK) may include
P be tracked as manufacturer-serial-identifier (FK)
product--tracking-base--identifier (FK)
FIGURE 13TRK2 Z
product-block-identifier (FK) product--tracking-base--identifier (FK)
SERIAL/LOT/BLOCK CORRELATION (PART 1 OF 4) product-lot-identifier (FK) product-block-identifier (FK)
manufacturer-serial-identifier (FK) (AK1) product-lot-identifier (FK)
BASETRACK / 515 (with 13TRK2) (see 5PIN5, 5PIN6, 5PIN7, 6ECP4, INCDEV / 535
6ECP5, 10RFD3) RFDREV-APP / 374 (from 10RFD1)
manufacturer-cage-code manufacturer-cage-code (FK)
product-effectivity-tracking-type product-effectivity-tracking-type (FK) rfd-cage-code (AK1)
product-tracking-identifier product-tracking-identifier (FK) may be rfd-alphanumeric-identifier (AK1)
product--tracking-base--identifier product--tracking-base--identifier (FK) incorporated RFD (AK1)
may incorporate into
rfd-cage-code (FK) rfd-revision
manufacture-date rfd-alphanumeric-identifier (FK) document-revision-approval-status-code
manufacture-time RFD (FK) document-revision-approval-status-date

product-effectivity-tracking-type rfd-revision (FK)

document-revision-approval-status-code (FK)
document-revision-approval-status-date (FK)
D
L
B
DATECODE / 519
product-manufacturing-datecode.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
manufacturer-cage-code (FK)
product--tracking-base--identifier (FK)

GENERIC-MATID / 200 (from 5PIN1) BLOCKID / 520 (from 13TRK2)

may be assigned to design-enterprise-identifier product-block-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
material-generic-identifier manufacturer-cage-code (FK)
may be assigned to product--tracking-base--identifier (FK)
material-identification

GENERIC-PIN / 210 (from 5PIN2)

may be tracked by LOTNUM / 518 (from 13TRK2)
design-enterprise-identifier

B-218
part-identifier may be tracked by product-lot-identifier.(product-effectivity-tracking-type,product-tracking-identifier) (FK)
manufacturer-cage-code (FK)
APPENDIX B
MIL-STD-2549

product--tracking-base--identifier (FK)
MAT-DATECODE / 530
design-enterprise-identifier (FK)
material-generic-identifier (FK) Assertion: the relationships LOTNUM / 518
material-identification (FK) to PIN-LOT / 523 (shown on 13TRK2) and
manufacturer-cage-code (FK) LOTNUM / 518 to MAT-LOT / 526 are
may be tracked by
product-manufacturing-datecode (FK) mutually exclusive.
product--tracking-base--identifier (FK)
product-quantity
may include may be part of
unit-of-measure
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MAT-LOT / 526 (see 13TRK4, 13TRK5) may be

PIN-DATECODE / 529 MATLOT-BLOCK / 528
design-enterprise-identifier (FK) assigned to
design-enterprise-identifier (FK) design-enterprise-identifier (FK)
material-generic-identifier (FK)
part-identifier (FK) Z material-generic-identifier (FK)
material-identification (FK)
manufacturer-cage-code (FK) may be part of material-identification (FK)
manufacturer-cage-code (FK) (AK1)
product-manufacturing-datecode (FK) manufacturer-cage-code (FK)
product-lot-identifier (FK) (AK1)
product-lot-identifier (FK)
product--tracking-base--identifier (FK)
product--tracking-base--identifier (FK) (AK1) product-block-identifier (FK)
product-quantity
product-quantity
unit-of-measure product--tracking-base--identifier (FK)
unit-of-measurement
FIGURE 13TRK3
SERIAL/LOT/BLOCK CORRELATION (PART 2 of 4)
REGROUP-PINLOT / 524
design-enterprise-identifier (FK)
part-identifier (FK)
PIN-LOT / 523 (from 13TRK2)
component-lot-manufacturer-cage-code.manufacturer-cage-code (FK)
design-enterprise-identifier may be part of component-lot-identifier.product-lot-identifier (FK)
part-identifier regrouped-lot-manufacturer-cage-code.manufacturer-cage-code (FK)
manufacturer-cage-code regrouped-lot-identifier.product-lot-identifier (FK)
product-lot-identifier may be a regrouping of
component-lot-quantity
product--tracking-base--identifier unit-of-measure

REGROUP-MATLOT / 527

B-219
MAT-LOT / 526 (from 13TRK3)
design-enterprise-identifier design-enterprise-identifier (FK)
APPENDIX B
MIL-STD-2549

material-generic-identifier material-generic-identifier (FK)

may be part of
material-identification material-identification (FK)
manufacturer-cage-code (AK1) component-lot-manufacturer-cage-code.manufacturer-cage-code (FK)
product-lot-identifier (AK1) component-lot-identifier.product-lot-identifier (FK)
may be a regrouping of regrouped-lot-manufacturer-cage-code.manufacturer-cage-code (FK)
product--tracking-base--identifier (AK1) regrouped-lot-identifier.product-lot-identifier (FK)
product-quantity
unit-of-measure component-lot-quantity
unit-of-measure
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 13TRK4
SERIAL/LOT/BLOCK CORRELATION (PART 3 OF 4)
CAGE / 003 (from 1GEN1)
PIN-MSN / 521 (from 13TRK2) MODIFY-MSNPART / 531
cage-code
design-enterprise-identifier may be modified into original-design-enterprise-identifier.design-enterprise-identifier (FK)
part-identifier original-part-identifier.part-identifier (FK)
manufacturer-cage-code Z manufacturer-cage-code (FK)
may be a modification of
manufacturer-serial-identifier manufacturer-serial-identifier (FK)
Z modified-product-design-enterprise-identifier.design-enterprise-identifier (FK)
product--tracking-base--identifier may
modified-part-identifier.part-identifier (FK) modify
product-block-identifier assertion: in REDO-PINLOT / 531, the
product-lot-identifier product-tracking--base-identifier remanufacturer-cage-code.cage-code (FK)
is the same through all paths of
inheritance

PIN-GSN / 522 (from 13TRK2) MODIFY-GSNPART / 532

design-enterprise-identifier original-design-enterprise-identifier.design-enterprise-identifier (FK)
part-identifier original-part-identifier.part-identifier (FK) may
manufacturer-cage-code may be modified into manufacturer-cage-code (FK) modify
government-serial-identifier
Z government-serial-identifier (FK)
product-tracking--base-identifier may be a modification of modified-product-design-enterprise-identifier.design-enterprise-identifier (FK)
product-block-identifier modified-part-identifier.part-identifier (FK)
product-lot-identifier Z
remanufacturer-cage-code.cage-code (FK)
manufacturer-serial-number assertion: in REDO-PINLOT / 532,
the product-tracking--base-identifier
is the same through all paths of may modify
inheritance

B-220
MODIFY-LOTPART / 533
PIN-LOT / 523 (from 13TRK2) original-design-enterprise-identifier.design-enterprise-identifier (FK)
APPENDIX B

may be modified into

MIL-STD-2549

design-enterprise-identifier original-part-identifier.part-identifier (FK)

part-identifier manufacturer-cage-code (FK)
manufacturer-cage-code product-lot-identifier (FK)
product-lot-identifier may be a modification of modified-product-design-enterprise-identifier.design-enterprise-identifier (FK) may modify
assertion: in REDO-PINLOT / 533, modified-part-identifier.part-identifier (FK)
product--tracking-base--identifier
the product-tracking--base-identifier remanufacturer-cage-code.cage-code (FK)
is the same through all paths of
inheritance

MAT-LOT / 526 (from 13TRK3) MODIFY-LOTMAT / 534

design-enterprise-identifier original-design-enterprise-identifier.design-enterprise-identifier (FK)
material-generic-identifier
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

may be modified into original-material-generic-identifier.material-generic-identifier (FK)

material-identification original-material-idenfication.material-identification (FK)
manufacturer-cage-code (AK1) manufacturer-cage-code (FK)
product-lot-identifier (AK1) product-lot-identifier (FK)
may be a modification of
product--tracking-base--identifier (AK1) modified-product-design-enterprise-identifier.design-enterprise-identifier (FK)
product-quantity assertion: in REDO-PINLOT / 534, modified-material-generic-identifier.material-generic-identifier (FK)
unit-of-measure the product-tracking--base-identifier modified-material-identification.material-identification (FK)
is the same through all paths of remanufacturer-cage-code.cage-code (FK)
inheritance

FIGURE 13TRK5
SERIAL/LOT/BLOCK CORRELATION (PART 4 OF 4)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

TABLE B-II. Portion of nomenclature to be used as common base number

If nomenclature is in and, the item is: then, the common base number is the: which
accordance with1 appears as:

MIL-STD-196 Electronic system "AN/", equipment type indicator, "-", and number AN/VRC-1

Electronic group Group indicator, "-", and model number OJ-301

Electronic unit Unit indicator, "-", and model number PP-50

Battery "BA-" or "BB-", and model number BA-4

BB-552

MIL-STD-787 Optical range "ORI/", series of three indicator letters, "-", and ORI/CBC-4
instrumentation model number

ORI accessories component indicator, "-", and model number TT-45

MIL-STD-1812 Photographic equipment Photographic code, "-", and model number KA-533

Aeronautical & support "A/", installation letter, type of equipment indicator, A/S32P-5
equipment purpose letter, "-", and model number

Aeronautical & support Group indicator, "G-", and model number SVG-7
group

Aeronautical & support Unit indicator, "U-", and model number SVU-555
unit

Ordnance unit Unit indicator, "U-", model number, "/", and purpose BLU-27/B
indicator

Engine or motor Type indicator, "-", and model indicator2 F100-100

SR1-113

AFR 82-1, Aircraft Basic mission indicator, vehicle type indicator (if F-18
AR 70-50, assigned), "-", and design number UH-45
NAVMATINST 8800.4
Missile, probe or rocket Launch environment indicator, mission indicator, AGM-88
vehicle type indicator, "-" and design number3
NOTES:
1. Nomenclatures assigned in accordance with MIL-STD-1464(AR) or MIL-STD-1661(OS) are not included in this table because the
designation portions of these nomenclatures are not unique, and therefore, cannot be used as a common base number.
2. Note that the manufacturer identification letter is not used as part of the common base number.
3. Training versions of mission equipment shall be serialized in the same series as mission equipment even though the mission indicator will
be different. For example, the ATM-88 is a training version of the AGM-88; the common base number for both of these is "AGM-88".

B.5.13.3. Table 502, Drawing identifier as product-tracking base-identifier (BASE-DWG). This table is a
subtype of BASE/500 which contains the subset of Table 500 consisting of those product-tracking base-identifiers
which are engineering drawing identifiers. This is the second choice to use as a product-tracking base-identifier
(see also: B.5.13.1).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.4. Table 503, Program specifications as product-tracking base-identifier (BASE-SPEC). This table is a
subtype of BASE/500 which contains the subset of Table 500 consisting of those product-tracking base-identifiers

B-221
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

which are program-unique specification identifiers. This is the third choice to use as a product-tracking base-
identifier (see also: B.5.13.1).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.5. Table 504, Standardization document as product-tracking base-identifier (BASE-STDDOC). This

table is a subtype of BASE/500 which contains the subset of Table 500 consisting of those product-tracking base-
identifiers which are the identifiers of standardization documents which define part numbers or materials. This is
the fourth choice to use as a product-tracking base-identifier (see also: B.5.13.1 and B.5.11.1).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.6. Table 505, PIN as product-tracking base-identifier (BASE-PIN). This table is a subtype of BASE/500
which contains the subset of Table 500 consisting of those product-tracking base-identifiers which are part
numbers. This is the fifth choice to use as a product-tracking base-identifier (see B.5.13.1 and B.5.5.9).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.7. Table 506, Material definition as product-tracking base-identifier (BASE-MAT). This table is a
subtype of BASE/500 which contains the subset of Table 500 consisting of those product-tracking base-identifiers
which are identifiers of materials (or parts) which are not identified by part numbers. This is the sixth choice to
use as a product-tracking base-identifier (see B.5.13.1 and B.5.5.1).

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.8. Table 507. Reserved.

B.5.13.9. Table 508, Correlation of program-unique specifications to product-tracking base-identifiers (PSPEC-

SPECBASE). This table is a subtype of Table SPEC/100 which contains those specifications which serve as the
product-tracking base-identifier for tracking materials or parts.

a. If the value of configuration-item-product-nomenclature-text (CINOMN690) in Table 100 is blank, then,

this table applies; if the value of CINOMN690 in Table 100 is not blank, then, this table does not apply.

b. For each value of product--tracking-base--identifier (BASNUM500) in this table, there must be one (and
only one) instance in this table where the value of BASNUM500 is the same as the value of the
concatenation of design-enterprise-defense-logistics--assigned-identification-code (DESCAG022),
document-alphanumeric-identifier (DOCNUM020), and document-type-code (DOCTYP010).

B-222
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.10. Table 509, Program specifications which use a CI designation as the product-tracking base-identifier
(SPEC-CIBASE). This table is a subtype of Table SPEC/100 which contains those specifications which use a CI
designation as the product-tracking base-identifier for tracking materials or parts.

a. If the value of configuration-item-product-nomenclature-text (CINOMN100) in Table 100 is not blank,

then, this table applies; if the value of configuration-item-product-nomenclature-text (CINOMN100) in
Table 100 is blank, then, this table does not apply.

b. The value of configuration-item-product-nomenclature-text (CINOMN690) in Table 100 must be the same

as the value of product--tracking-base--identifier (BASNUM500) in this table.

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.11. Table 510, Engineering drawings which use a CI designation as the product-tracking base-identifier
(DWG-CIBASE). This table is a subtype of Table PICDWG/060 which contains those drawings which use a CI
designation as the product-tracking base-identifier for tracking parts.

a. If the value of configuration-item-product-nomenclature-text (CINOMN690) in Table 057 is not blank,

then, this table applies; if the value of CINOMN690 in Table 060 is blank, then, this table does not apply.

b. The value of CINOMN690 in Table 060 must be the same as the value of product--tracking-base--
identifier (BASNUM500) in this table.

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

BASNUM500 product--tracking-base--identifier 0056 FK

B-223
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.13.12. Table 511, Correlation of engineering drawings to product-tracking base-identifier (DWG-

DWGBASE). This table is a subtype of Table PICDWG/060 which contains those drawings which serve as the
product-tracking base-identifier for tracking parts.

a. If the value of configuration-item-product-nomenclature-text (CINOMN690) in Table 060 is blank, then,

this table applies; if the value of CINOMN690 in Table 060 is not blank, then, this table does not apply.

b. For each value of product--tracking-base--identifier (BASNUM500) in this table, there must be one (and
only one) instance in this table where the value of BASNUM500 is the same as the value of the
concatenation of design-enterprise-defense-logistics--assigned-identification-code (DESCAG050),
engineering-drawing-document-alphanumeric-identifier (DWGNUM050), and document-type-code
(DOCTYP010).

Code Data Element Title DED Key

DESCAG050 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DOCTYP010 document-type-code 0004 FK
DWGNUM050 engineering-drawing-document-alphanumeric-identifier 0003 FK

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.13. Tables 512 through 514. Reserved.

B.5.13.14. Table 515, Basis for product tracking (BASETRACK). This table contains the valid combinations of
manufacturer and serial/lot/block/date code numbers for each product-tracking base-identifier (common base
number).

a. Attribute enterprise-defense-logistics--assigned-identification-code (CAGNUM003) inherited from Table

003 assumes the role manufacturer-enterprise-defense-logistics--assigned-identification-code
(MFRCAG515).

Code Data Element Title DED Key

TRKIDN515 product-sequential-tracking-identifier 0058 K
TRKTYP515 product-change-effectivity-tracking-type-code 0057 K
BASNUM500 product--tracking-base--identifier 0056 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

MFRDAT515 product-manufacture-date 0082 M

MFRTIM515 product-manufacture-time 0160 M

B.5.13.15. Table 516, Manufacturer serial number (MSN). This table is a subtype of Table BASETRACK/515
and contains the subset of product tracking identifiers consisting of manufacturer serial (or sequence) numbers.
These numbers are assigned by the manufacturer who has sole responsibility for them.

a. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 515 are concatenated and assume the role

B-224
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

product-manufacturer-serial-tracking-identifier (MSNNUM516). (See Appendix C for concatenation

order.)

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
MSNNUM516 product-manufacturer-serial-tracking-identifier 0175 FK

B.5.13.16. Table 517, Government serial number (GSN). This table is a subtype of Table BASETRACK/515
which contains the subset of product tracking identifiers consisting of Government serial numbers. These
numbers are provided to the manufacturer by the procuring Government agency for assignment to the product,
usually at the completion of final acceptance testing. Use of these numbers is usually limited to CI level units only.

a. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 515 are concatenated and assume the role
product-government-serial-tracking-identifier (GSNNUM517). (See Appendix C for concatenation
order.)

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK
GSNNUM517 product-government-serial-tracking-identifier 0175 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B.5.13.17. Table 518, Lot numbers (LOTNUM). This table is a subtype of Table BASETRACK/515 which
contains the subset of product tracking identifiers consisting of manufacturer lot numbers. These numbers are
assigned by the manufacturer who has sole responsibility for them.

a. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 515 are concatenated and assume the role
product-lot-tracking-identifier (LOTNUM518). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK
LOTNUM518 product-lot-tracking-identifier 0175 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B.5.13.18. Table 519, Date codes (DATECODE). This table is a subtype of Table BASETRACK/515 which
contains the subset of product identifiers consisting of manufacturer date code numbers. This form of lot numbers
is assigned by the manufacturer who has sole responsibility for them.

B-225
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 515 are concatenated and assume the role
product-manufacturing-datecode-tracking-identifier (DATCOD519). (See Appendix C for concatenation
order.)

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK
DATCOD519 product-manufacturing-datecode-tracking-identifier 0175 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B.5.13.19. Table 520, Block numbers (BLOCKID). This table is a subtype of BASETRACK/515 which contains
the subset of product identifiers consisting of engineering configuration block numbers. These numbers are not
actually used for tracking parts, but rather, are used to identify blocks of parts which all incorporate the same group
of ECPs. They are used administratively only.

a. The attributes product-sequential-tracking-identifier (TRKIDN515) and product-change-effectivity-

tracking-type-code (TRKTYP515) inherited from Table 515 are concatenated and assume the role
product-block-tracking-identifier (BLKNUM520). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK
BLKNUM520 product-block-tracking-identifier 0175 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B.5.13.20. Table 521, Correlation of part number to manufacturer serial number (PIN-MSN). This tables
provides a correlation of manufacturer-assigned serial numbers to part number; it is a list of which serial numbers
have been assigned to each part number at any time in the history of the part number.

a. For each instance in this table, the product--tracking-base--identifier (BASNUM500) must have the same
value in all parent instances.

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
MSNNUM516 product-manufacturer-serial-tracking-identifier 0175 FK
PARNUM210 part-product-identifier 0024 FK

BASNUM500 product--tracking-base--identifier 0056 FK

BLKNUM520 product-block-tracking-identifier 0175 FK, O
LOTNUM518 product-lot-tracking-identifier 0175 FK, O

B-226
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.13.21. Table 522, Correlation of part number to government serial number (PIN-GSN). This table provides
a correlation of Government-assigned serial numbers to part number; it is a list of which serial numbers have been
assigned to each part number at any time in the history of the part number.

a. For each instance in this table, the product--tracking-base--identifier (BASNUM500) must have the same
value in all parent instances.

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
GSNNUM517 product-government-serial-tracking-identifier 0175 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK

BASNUM500 product--tracking-base--identifier 0056 FK

BLKNUM520 product-block-tracking-identifier 0175 FK, O
LOTNUM518 product-lot-tracking-identifier 0175 FK, O
MSNNUM516 product-manufacturer-serial-tracking-identifier 0175 FK, O

B.5.13.22. Table 523, Correlation of part number(s) to lot numbers (PIN-LOT). This table provides a correlation
of manufacturer-assigned lot numbers to part number(s); it is a list of which lot numbers have been assigned to
each part number at any time in the history of the part number.

Code Data Element Title DED Key

DESENT210 design-enterprise-identifier 0052 FK
LOTNUM518 product-lot-tracking-identifier 0175 FK, AK1
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK, AK1
identification-code
PARNUM210 part-product-identifier 0024 FK

BASNUM500 product--tracking-base--identifier 0056 FK, AK1

QUANTY523 product-quantity 0019 M
UOMCOD523 product-measurement-unit-code 0054 M

B.5.13.23. Table 524, Regrouped part lots (REGROUP-PINLOT). This table identifies lots of a single part
number which have been formed by the consolidation of small lots (or partial lots) of the same part number. In
this case, the organization performing the work assigns a new lot number, but the part identifier is unchanged.

a. Attribute product-lot-tracking-identifier (LOTNUM518) inherited from Table 523 assumes the role
component-product-lot-tracking-identifier (CLOTNO524).

b. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 523 assumes the role component-part-manufacturer-enterprise-defense-logistics--
assigned-identification-code (CMFRCG524).

B-227
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Attribute product-lot-tracking-identifier (LOTNUM518) inherited from Table 523 assumes the role
regrouped-product-lot-tracking-identifier (RLOTNO524).

d. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 523 assumes the role regrouped-lot-manufacturer-enterprise-defense-logistics--
assigned-identification-code (RMFRCG524).

Code Data Element Title DED Key

CLOTNO524 component-product-lot-tracking-identifier 0175 FK
CMFRCG524 component-part-manufacturer-enterprise-defense-logistics-- 0001 FK
assigned-identification-code
DESENT210 design-enterprise-identifier 0052 FK
PARNUM210 part-product-identifier 0024 FK
RLOTNO524 regrouped-product-lot-tracking-identifier 0175 FK
RMFRCG524 regrouped-lot-manufacturer-enterprise-defense-logistics-- 0001 FK
assigned-identification-code

QUANTY524 component-product-quantity 0019 M

UOMCOD524 product-measurement-unit-code 0054 M

B.5.13.24. Table 525, Correlation of part lot numbers to block numbers (PINLOT-BLOCK). This table
correlates part lot numbers to block numbers.

Code Data Element Title DED Key

BLKNUM520 product-block-tracking-identifier 0175 FK
DESENT210 design-enterprise-identifier 0052 FK
LOTNUM518 product-lot-tracking-identifier 0175 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.25. Table 526, Correlation of material identification and lot number (MAT-LOT). This table correlates
lot numbers with materials (and parts) which are not identified by a part number; it is a list of which lot numbers
have been assigned to each material identifier at any time in the history of the material identifier.

a. For each instance in this table, the value of product-tracking-base-identifier (BASNUM500) must be the
same in all parent instances.

Code Data Element Title DED Key

DESENT200 design-enterprise-identifier 0052 FK
LOTNUM518 product-lot-tracking-identifier 0175 FK, AK1
MATGID200 material-product-generic-identifier 0092 FK

B-228
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

MATIDN200 material-product-identifier 0038 FK

MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK, AK1
identification-code

BASNUM500 product--tracking-base--identifier 0056 FK, AK1

QUANTY526 product-quantity 0019 M
UOMCOD526 product-measurement-unit-code 0054 M

B.5.13.26. Table 527, Regrouped material lots (REGROUP-MATLOT). This table identifies lots of a single
material (not identified by a part number) which have been formed by combining, re-blending, etc. smaller lots (or
partial lots) of the same material. In this case, the organization performing the work assigns a new lot number, but
the material identification is unchanged.

a. Attribute product-lot-tracking-identifier (LOTNUM518) inherited from Table 526 assumes the role
component-product-lot-tracking-identifier (CLOTNO527).

b. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 526 assumes the role component-material-manufacturer-enterprise-defense-
logistics--assigned-identification-code (CMFRCG527).

c. Attribute product-lot-tracking-identifier (LOTNUM518) inherited from Table 526 assumes the role
regrouped-product-lot-tracking-identifier (RLOTNO527).

d. Attribute manufacturer-enterprise-defense-logistics--assigned-identification-code (MFRCAG515)

inherited from Table 526 assumes the role regrouped-lot-manufacturer-enterprise-defense-logistics--
assigned-identification-code (RMFRCG527).

Code Data Element Title DED Key

CLOTNO527 component-product-lot-tracking-identifier 0175 FK
CMFRCG527 component-material-manufacturer-enterprise-defense- 0001 FK
logistics--assigned-identification-code
DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
RLOTNO527 regrouped-product-lot-tracking-identifier 0175 FK
RMFRCG527 regrouped-lot-manufacturer-enterprise-defense-logistics-- 0001 FK
assigned-identification-code

QUANTY527 component-product-quantity 0019 M

UOMCOD527 product-measurement-unit-code 0054 M

B.5.13.27. Table 528, Correlation of material lot numbers to block change numbers (MATLOT-BLOCK). This
table correlates material lot numbers to block numbers.

B-229
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

BLKNUM520 product-block-tracking-identifier 0175 FK
DESENT200 design-enterprise-identifier 0052 FK
LOTNUM518 product-lot-tracking-identifier 0175 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

BASNUM500 product--tracking-base--identifier 0056 FK

B.5.13.28. Table 529, Correlation of part numbers to date codes (PIN-DATECODE). This table correlates part
numbers and date codes; it is a list of which date codes have been assigned to each part number at any time in the
history of the part number.

Code Data Element Title DED Key

DATCOD519 product-manufacturing-datecode-tracking-identifier 0175 FK
DESENT210 design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
PARNUM210 part-product-identifier 0024 FK

BASNUM500 product--tracking-base--identifier 0056 FK

QUANTY529 product-quantity 0019 M
UOMCOD529 product-measurement-unit-code 0054 M

B.5.13.29. Table 530, Correlation of material identifiers to date codes (MAT-DATECODE). This table
correlates material identifiers (not part numbers) to date codes; it is a list of which date codes have been assigned
to each material identifier at any time in the history of the material identifier.

Code Data Element Title DED Key

DATCOD519 product-manufacturing-datecode-tracking-identifier 0175 FK
DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

BASNUM500 product--tracking-base--identifier 0056 FK

QUANTY530 product-quantity 0019 M
UOMCOD530 product-measurement-unit-code 0054 M

B-230
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.13.30. Table 531, Part number change history for item tracked by manufacturer's serial number (MODIFY-
MSNPART). This table identifies part numbers tracked by a manufacturer serial number which have been
modified into a different part number within the same product-tracking base-identifier. In this case, the part
number changes, but the manufacturer serial number does not change. This table also records what organization
performed the modification.

a. The product-tracking-base-identifier must be the same through all inheritance paths for both the new and
original parts.

b. Attribute design-enterprise-identifier (DESENT210) inherited from Table 521 assumes the role modified-
product-design-enterprise-identifier (MDESEN531).

c. Attribute part-product-identifier (PARNUM210) inherited from Table 521 assumes the role modified-part-
product-identifier (MPARNO531).

d. Attribute design-enterprise-identifier (DESENT210) inherited from Table 521 assumes the role original-
design-enterprise-identifier (ODESEN531).

g. Attribute material-product-identifier (MATIDN200) inherited from Table 526 assumes the role original-
material-product-identifier (OMATID534).

h. Attribute enterprise-defense-logistics--assigned-identification-code (CAGNUM003) inherited from Table

003 assumes the role remanufacturer-enterprise-defense-logistics--assigned-identification-code
(RMFRCG534).

Code Data Element Title DED Key

LOTNUM518 product-lot-tracking-identifier 0175 FK
MDESEN534 modified-product-design-enterprise-identifier 0052 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code

B-233
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

MMATGI534 modified-material-product-generic-identifier 0092 FK

MMATID534 modified-material-product-identifier 0038 FK
ODESEN534 original-design-enterprise-identifier 0052 FK
OMATGI534 original-material-product-generic-identifier 0092 FK
OMATID534 original-material-product-identifier 0038 FK

RMFRCG534 remanufacturer-enterprise-defense-logistics--assigned- 0001 FK

identification-code

B.5.13.34. Table 535, Incorporated deviations (INCDEV). This table identifies the approved deviations which
have been incorporated into this part or material which is identified by a product tracking identifier. Entries in this
table must be validated against the contents of Table 361 or 366.

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDTYP350 deviation-request-document-type-code 0004 FK
TRKIDN515 product-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK

RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.13.35. Table 536, Incorporated modification instructions (INCMODINST). This table identifies the
approved modification instructions that have been incorporated into this part or material which is identified by a
product tracking identifier.

Code Data Element Title DED Key

BASNUM500 product--tracking-base--identifier 0056 FK
MFRCAG515 manufacturer-enterprise-defense-logistics--assigned- 0001 FK
identification-code
MINIDN460 modification-instruction-document-identifier 0122 FK
MINSRC460 modification-instruction-document-source-entity-identifier 0033 FK
MINTYP460 modification-instruction-document-type-code 0004 FK
TRKIDN515 product-sequential-tracking-identifier 0058 FK
TRKTYP515 product-change-effectivity-tracking-type-code 0057 FK

B.5.13.36. Tables 537 through 549. Reserved.

B-234
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.14. Technical manuals and orders. The entity tables numbered in the range of 550 through 599 contain the
identification of, and information concerning, both military and commercial technical manuals and technical
orders. Military technical manuals and orders are unusual in that they have three levels of iteration: the basic
technical manual is revised (denoted by the issue date); revisions have changes (identified by either a change
number or letter); and changes have supplements (identified by the supplement type and number). The
relationship between these various entity tables are depicted in Figures 14TM1 through 14TM4.

B.5.14.1. Table 550, Technical manuals (TECHMAN). This table is a category of GENERIC-DOC/010 for the
case where the value of document-type-code (DOCTYP010) is 'TECHMAN'. This table contains the unique and
primary identification of technical manuals.

a. The document-acquiring-activity-indicator-code (ACQCOD550) indicates whether the instance represents

the primary identifier of the technical manual, or if this identifier is an alias assigned by a using activity.

b. Attribute document-type-code (DOCTYP010) inherited from Table 010 assumes the role technical-
manual-document-type-code (TMNTYP550).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
SRCIDN010 document-source-entity-identifier 0033 FK
TMNTYP550 technical-manual-document-type-code 0004 FK

ACQCOD550 document-lead-activity-indicator-code 0006 M

DODCOD550 document-format-compliance-indicator-code 0143 M

B.5.14.2. Table 551, Revisions to technical manuals (TECHMAN-REV). This table is a category of
GENERIC-DOCREV/011 for the case where the value of document-type-code (DOCTYP010) is 'TECHMAN'.
This table contains the unique and primary identification of revisions to technical manuals.

a. Due to parallel categorization this table is a de facto child of Table TECHMAN/550. It therefore has the
same subtypes as Table 550.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
SRCIDN010 document-source-entity-identifier 0033 FK
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.14.3. Table 552, DOD technical manual identification (DODTECHMAN). This table is a category of
Table TECHMAN/550 for the case where the value of the document-defense-department-indicator-code
(DODCOD550) is 'D'. This table contains the unique and primary identification of military service technical
manuals and technical orders as primarily defined in Mil-M-38784.

B-235
GENERIC-DOC / 010 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code

document-type-code
may be using activity alias for TECHMAN

TECHMAN / 550 (see 12MOD1)

document-source-entity-identifier (FK)
document-identifier (FK)
TMALIAS / 556
TECHMAN.document-type-code (FK)
alias-document-source-entity-identifier.document-source-entity-identifier (FK) may have aliases
alias-document-identifier.document-identifier (FK) dod-indicator-code
document-type-code (FK)
TECHMAN (FK)
controlling-technical-manual-source-identifier.document-source-entity-identifier (FK)
controlling-technical-manual-identifier.document-identifier (FK)
D C

TCTO / 466 (from 12MOD3) DODTECHMAN / 552 (see 6ECP5) COMTECHMAN / 553
us-dod-document-source-organization-code us-dod-document-source-organization-code.document-source-entity-identifier (FK) document-source-entity-identifier (FK)
modification-identifier document-alphanumeric-identifier.document-identifier (FK) document-identifier (FK)
MODINST TECHMAN (FK) TECHMAN (FK)
service-acronym

B-236
APPENDIX B
MIL-STD-2549

service-acronym
USAF USN
USA USMC
is a
USATM / 557 (see 12MOD3) USMCTM / 558 USNTM / 559
us-dod-document-source-organization-code (FK) us-dod-document-source-organization-code (FK) us-dod-document-source-organization-code (FK)
document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
TECHMAN (FK) TECHMAN (FK) TECHMAN (FK)
navy-command-identifier
1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

USAFTO / 560
us-dod-document-source-organization-code (FK) navy-command-identifier
af-technical-order-alphanumeric-identifier.(document-alphanumeric-identifier,modification-identifier) (FK)
TECHMAN (FK)
NAVAIR NAVSEA
MODINST (FK)

NAVAIR-TM / 562 (see 12MOD3) NAVSEA-TM / 563

us-dod-document-source-organization-code (FK) us-dod-document-source-organization-code (FK)
FIGURE 14TM1 document-alphanumeric-identifier (FK) document-alphanumeric-identifier (FK)
TECHNICAL MANUALS (Part 1 of 4) TECHMAN (FK) TECHMAN (FK)
GENERIC-DOCREV / 011 (from 1GEN2)
document-source-entity-identifier
docment-identifier
document-type-code
document-generic-revision

document-type-code

TECHMAN-REV / 551 (de facto child of 550)

document-source-entity-identifier (FK)
docment-identifier (FK)
TECHMAN.document-type-code (FK)
document-generic-revision (FK)

B-237
APPENDIX B
MIL-STD-2549

dod-indicator-code (from 550)

D C

COM-TMREV / 555 (de facto child of 553)

DOD-TMREV / 554 (de facto child of 552) (see 14TM3)
document-source-entity-identifier (FK)
us-dod-document-source-organization-code.document-source-entity-identifier (FK) docment-identifier (FK)
document-alphanumeric-identifier.docment-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

TECHMAN (FK)
TECHMAN (FK) document-generic-revision (FK)
document-generic-revision (FK)
document-iteration-type-code

FIGURE 14TM2
TECHNICAL MANUALS (Part 2 of 4)
DOD-TMREV / 554 (from 14TM2)
us-dod-document-source-organization-code
document-alphanumeric-identifier DOD-TMCHG / 610 (from 15SUP2)
TECHMAN us-dod-document-source-organization-code
document-generic-revision revised-tm-identifier
document-type-code
document-iteration-type-code tm-change-identifier

document-iteration-type-code

D may be part of
REVISED-DODTM / 570 (see 15SUP1) S
us-dod-document-source-organization-code (FK)
document-alphanumeric-identifier (FK)
TECHMAN (FK) C
tm-revision-issue-date.document-generic-revision (FK)

CHANGED-DODTM / 571 (see 15SUP2, 15SUP3, 15SUP4, 15SUP5)

us-dod-document-source-organization-code (FK) may be
revised-tm-identifier.(tm-revision-issue-date,revised-tm-identifier,document-alphanumeric-identifier) (FK) supplemented
may be changed by
TECHMAN (FK) by
tm-change-identifier.(document-generic-revision,tm-change-identifier) (FK)

document-type-code (FK)

B-238
DOD-TMSSUP / 611 (from 15SUP2)
APPENDIX B

us-dod-document-source-organization-code
MIL-STD-2549

changed-tm-identifier
document-type-code Z
tm-safety-supplement-identifier
may be part of SUPPLEMENTED-DODTM / 572
us-dod-document-source-organization-code (FK)
changed-tm-identifier.(document-alphanumeric-identifier,tm-change-identifier,changed-tm-identifier,revised-tm-identifier) (FK)
TECHMAN (FK)
DOD-TMOSUP / 612 (from 15SUP3)
tm-supplement-set-date.document-generic-revision (FK)
us-dod-document-source-organization-code
changed-tm-identifier may be part of document-type-code (FK)
document-type-code tm-routine-supplement-identifier (FK)
tm-operational-supplement-identifier tm-operational-supplement-identifier (FK)
tm-safety-supplement-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

may be part of
DOD-TMRSUP / 613 (from 15SUP4) may include
us-dod-document-source-organization-code
changed-tm-identifier DODTMSUPPKG-TOPS / 573
document-type-code DOD-TOPS / 614 (from 15SUP5)
us-dod-document-source-organization-code (FK)
tm-routine-supplement-identifier us-dod-document-source-organization-code changed-tm-identifier (FK)
changed-tm-identifier TECHMAN (FK)
document-type-code may be part of tm-supplement-set-date (FK)
to-page-supplement-identifier to-page-supplement-identifier (FK)
FIGURE 14TM3 document-type-code (FK)
TECHNICAL MANUALS (Part 3 of 4)
ECP-TECHMAN / 291 (from 6ECP5)
ECPACT / 262 (from 6ECP5)
ecp-cage-code
ecp-cage-code ecp-alphanumeric-identifier
ecp-alphanumeric-identifier ECP
ECP ecp-revision
REVISED-DODTM / 570 (from 14TM3)
ecp-revision us-dod-document-source-organization-code
us-dod-document-source-organization-code enterprise-identifier document-alphanumeric-identifier
document-alphanumeric-identifier program-name TECHMAN
TECHMAN ccb-name
tm-revision-issue-date ecp-implementation-action-identifier

may require the issuance of

may direct the
issue of

B-239
may be the result of
APPENDIX B
MIL-STD-2549

ECP-TMREV / 565
ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
ECP (FK)
ecp-revision (FK)
us-dod-document-source-organization-code (FK)
document-alphanumeric-identifier (FK)
TECHMAN (FK)
tm-revision-issue-date (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

ecp-implementation-action-identifier (FK)
enterprise-identifier (FK)
FIGURE 14TM4 program-name (FK)
TECHNICAL MANUALS (Part 4 of 4) ccb-name (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. The value of united-states-defense-department-document-source-enterprise-acronym-identification-code

(SRCDOD552) must exist as a valid entry in Table DOD-ORGANIZATION/034.

b. Attribute document-identifier (DOCIDN010) inherited from Table 550 assumes the role document-
alphanumeric-identifier (DOCNUM552).

c. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 550 assumes the role
united-states-defense-department-document-source-enterprise-acronym-identification-code
(SRCDOD552).

Code Data Element Title DED Key

DOCNUM552 document-alphanumeric-identifier 0003 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

SERVID552 united-states-defense-component-enterprise-acronym- 0002 M

identification-code

B.5.14.4. Table 553, Commercial technical manuals (COMTECHMAN). This table is a category of Table
TECHMAN/550 for the case where the value of the document-defense-department-indicator-code (DODCOD550)
is 'C'. This table contains the unique and primary identification of non-military service technical manuals.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
SRCIDN010 document-source-entity-identifier 0033 FK
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.14.5. Table 554, Iterations of DOD technical manuals (DOD-TMREV). This table is a category of Table
TECHMAN-REV/551 for the case where the value of the document-defense-department-indicator-code
(DODCOD550) in Table 550 is 'D'. This table contains the unique and primary identification of iterations of
military service technical manuals and technical orders as primarily defined in Mil-M-38784. Because DOD
technical manuals use multi-level iterations (for example: changes are issued against revisions of the manual) this
table has three subtypes: REVISED-DODTM/570, CHANGED-DODTM/571, and SUPPLEMENTED-DODTM/
572. Each of these represent the technical manual with the specified iterations incorporated. (See also: Table
DOCSUP/600.)

a. Due to parallel categorization, this table is a de facto child of Table DODTECHMAN/552. Therefore, it
has the same subtypes as Table 552.

Code Data Element Title DED Key

DOCNUM552 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

ITTYPE554 technical-manual-document-iteration-type-code 0196 M

B-240
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.14.6. Table 555, Revisions to commercial technical manuals (COM-TMREV). This table is a category of
Table TECHMAN-REV/551 for the case where the value of the document-defense-department-indicator-code
(DODCOD550) in Table 550 is 'C'. This table contains the unique and primary identification of iterations of non-
military service technical manuals.

a. Due to parallel categorization, this table is a de facto child of Table COMTECHMAN / 553. Therefore, it
has the same subtypes as Table 553.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.14.7. Table 556, Technical manual aliases (TMALIAS). Often, a technical manual will be used by more
than one organization because the equipment is used by more than one service. However, each organization has its
own system of technical manual (or order) identification. These systems use intelligent numbering systems to
facilitate information retrieval and document distribution. (Note: sometimes a document which is a technical
manual (or order) in one organization is published as a standardization document in another organization.) In
each of these cases, there is one organization which is responsible for the information in the technical manual and
maintaining it. There is only one lead for any document which has alias identification number(s) assigned to it;
this activity is tracked in Table 550. The purpose of this table is to correlate the various alias identifier(s) with the
identifier assigned by the lead organization. (Note: according to MIL-M-38784 for U.S. DOD technical manuals,
the lead activity identifier is always listed first on each page of the document with the alias[es] listed in
alphabetical order by using service component.)

a. Attribute document-identifier (DOCIDN010) inherited from Table 010 assumes the role document-alias-
identifier (ADOCID556).

b. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 010 assumes the role
alias-document-source-entity-identifier (ASRCID556).

c. Attribute document-identifier (DOCIDN010) inherited from Table 550 assumes the role controlling-
technical-manual-document-identifier (CTMIDN556).

d. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 550 assumes the role
controlling-technical-manual-document-source-entity-identifier (CTMSRC556).

Code Data Element Title DED Key

ADOCID556 document-alias-identifier 0122 FK
ASRCID556 alias-document-source-entity-identifier 0033 FK
CTMIDN556 controlling-technical-manual-document-identifier 0122 FK
CTMSRC556 controlling-technical-manual-document-source-entity- 0033 FK
identifier
DOCTYP010 document-type-code 0004 FK
TMNTYP550 technical-manual-document-type-code 0004 FK

B-241
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.14.8. Table 557, Army Technical Manuals (ARMY-TM). This table is a category of DODTECHMAN/552
for the case where the value of the united-states-defense-component-enterprise-acronym-identification-code
(SERVID552) in Table 552 is 'USA'. It contains the unique and primary identification of Army technical manuals
as defined in Mil-M-38784.

a. Attribute document-alphanumeric-identifier (DOCNUM552) inherited from Table 552 assumes the role
united-states-army-technical-manual-document-alphanumeric-identifier (ATMNUM557).

Code Data Element Title DED Key

ATMNUM557 united-states-army-technical-manual-document- 0003 FK
alphanumeric-identifier
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.14.9. Table 558, Marine Corps Technical Manual (MARINE-TM). This table is a category of
DODTECHMAN/552 for the case where the value of the united-states-defense-component-enterprise-acronym-
identification-code (SERVID552) in Table 552 is 'USMC'. This table contains the unique and primary
identification of Marine Corps technical manuals as defined in Mil-M-38784.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

B.5.14.10. Table 559, Navy Technical Manuals (USNTM). This table is a category of DODTECHMAN/552 for
the case where the value of the united-states-defense-component-enterprise-acronym-identification-code
(SERVID552) in Table 552 is 'USN'. This table contains the unique and primary identification of Navy technical
manuals and technical orders as defined in Mil-M-38784.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

NAVCOM559 united-states-navy-command-enterprise-acronym- 0002 M

identification-code

B.5.14.11. Table 560, Air Force Technical Orders (USAFTO). This table is a category of DODTECHMAN/552
for the case where the value of the united-states-defense-component-enterprise-acronym-code (SERVID552) in
Table 552 is 'USAF'. This table contains the unique and primary identification of Air Force technical orders (or
manuals) as defined in Mil-M-38784 and USAF TO 00-5-1 including time-compliance technical orders as defined

B-242
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

in Mil-T-9885, Mil-M-38784, Mil-T-38804, and USAF TO 00-5-1. An Air Force technical order (or technical
manual) is a category of Table DOD-TECHMAN/552 for the case where the value of united-states-defense-
component-enterprise-acronym-identification-code (DODCOD552) in Table 552 is 'USAF'. An Air Force time-
compliance technical order is a special case of technical order because it is also a modification instruction (see
MODINST/460). It therefore must follow the rules for both parent entities.

a. The value of modification-instruction-document-alphanumeric-identifier (MINNUM462) inherited from

Table 466 and the value of document-alphanumeric-identifier (DOCNUM552) inherited from Table 552
must be the same. Therefore, they merge into the identity united-states-air-force-technical-order-
document-alphanumeric-identifier (AFTONO560).

b. Attribute united-states-defense-department-document-source-enterprise-acronym-identification-code
(SRCDOD462) inherited from Table 466 and united-states-defense-department-document-source-
enterprise-acronym-identification-code (SRCDOD552) inherited from Table 552 must have the same
value and merge to assume the role united-states-defense-department-document-source-enterprise-
acronym-identification-code (SRCDOD560).

Code Data Element Title DED Key

AFTONO560 united-states-air-force-technical-order-document- 0003 FK
alphanumeric-identifier
SRCDOD560 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

MINTYP460 modification-instruction-document-type-code 0004 FK, O

B.5.14.12. Table 561. Reserved.

B.5.14.13. Table 562, Naval Air Systems Command Technical Manuals (NAVAIR-TM). This table contains the
unique and primary identification of Naval Air (NAVAIR) Systems Command technical manuals as defined in
Mil-M-38784. A NAVAIR technical manual is a special case of Table USNTM/559 for the case where the value
of united-states-navy-command-enterprise-acronym-identification-code (NAVCOM559) is 'NAVAIR'.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

B.5.14.14. Table 563, Naval Sea Systems Command Technical Manuals (NAVSEA-TM). This table contains
the unique and primary identification of Naval Sea (NAVSEA) Systems Command technical manuals as defined in
Mil-M-38784. A NAVSEA technical manual is a special case of Table USNTM/559 for the case where the value
of united-states-navy-command-enterprise-acronym-identification-code (NAVCOM559) is 'NAVSEA'.

B-243
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCTYP010 document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

B.5.14.15. Table 564. Reserved.

B.5.14.16. Table 565, Correlation of ECPs to TM revisions (ECP-TMREV). This table correlates approved
ECPs to the Technical Manual/Order revision which results from the approved ECP.

Code Data Element Title DED Key

DOCNUM020 document-alphanumeric-identifier 0003 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
ISSDAT570 technical-manual-document-revision-issue-date 0082 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

CCBNAM700 program-configuration-control-board-name 0151 FK, O

ECPACT262 engineering-change-implementation-process-action-identifier 0072 FK
ENTIDN002 enterprise-identifier 0052 FK, O
PROGNM691 program-name 0059 FK, O

B.5.14.17. Tables 566 through 569. Reserved.

B.5.14.18. Table 570, Revised technical manuals (REVISED-DODTM). This table is a subtype of Table DOD-
TMREV/554 for the case of document-iteration-type-code (REVTYP010) having a value of 'D'. It contains the
history of the various revisions to a technical order or manual. Initial issue and revisions to technical manuals and
orders are identified by a date.

a. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 554 assumes the role
technical-manual-document-revision-issue-date (ISSDAT570).

Code Data Element Title DED Key

DOCNUM552 document-alphanumeric-identifier 0003 FK
ISSDAT570 technical-manual-document-revision-issue-date 0082 FK

B-244
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SRCDOD552 united-states-defense-department-document-source- 0002 FK

enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.14.19. Table 571, Changed technical manuals (CHANGED-DODTM). This table is a subcategory of Table
DOD-TMREV/554 for the case where document-iteration-type-code (REVTYP554) has a value of 'C'. Changes to
technical manuals are issued against a specific revision of the technical manual. This table contains the history of
the various changes to a given revision of a technical manual or order.

a. Changes to technical manuals are numbered based on the current technical manual revision in effect.
Therefore, the value document-alphanumeric-identifier (DOCNUM552) inherited from Table 554 must be
the same as the concatenation of the values of document-alphanumeric-identifier (DOCNUM552) and
technical-manual-document-revision-issue-date (ISSDAT570) inherited from Table 570. It is also the
same as the revised-technical-manual-document-identifier (RTMIDN610) inherited from Table 610. This
concatenation assumes the identity revised-technical-manual-document-identifier (RTMIDN571).

b. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 554 and technical-

manual-change-document-identifier (CHGNUM610) inherited from Table 610 must both have the same
value. Therefore they merge and assume the identity technical-manual-change-document-identifier
(CHGNUM610).

Code Data Element Title DED Key

CHGNUM610 technical-manual-change-document-identifier 0134 FK
RTMIDN610 revised-technical-manual-document-identifier 0135 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.14.20. Table 572, Supplemented technical manuals (SUPPLEMENTED-DODTM). This table is a subtype
of Table DOD-TMREV/554 for the case where the value of document-iteration-type-code (REVTYP554) in Table
554 is 'S'. It contains the history of the various sets of technical order page supplements (TOPS) to each technical
manual or technical order, (including revision and change).

a. Supplements to technical manuals are numbered based on the current technical manual revision and
change in effect. Therefore, the value of document-alphanumeric-identifier (DOCNUM552) inherited
from Table 554 and the changed-technical-manual-document-identifier optionally inherited from Tables
611, 612, and 613, must be the same as the concatenation of the values of revised-technical-manual-
document-identifier (RTMIDN571) and technical-manual-document-change-identifier (CHGNUM571)
inherited from Table 571. This concatenation assumes the identity changed-technical-manual-document-
identifier (CTMIDN572). The entries in this table represent the technical manual with the revisions,
changes and supplement(s) incorporated. (See also, Table 600.)

b. Supplements to technical manuals are identified by a supplement type and either supplement issue date or
sequence number. This difference exists because only one routine, safety, and operational supplement can
be in effect at any time; however, multiple page supplements can be in effect.

B-245
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 554 assumes the role
technical-manual-document-supplement-set-effective-date (SETDAT572).

Code Data Element Title DED Key

CTMIDN572 changed-technical-manual-document-identifier 0218 FK
SETDAT572 technical-manual-document-supplement-set-effective-date 0082 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK

DOCTYP010 document-type-code 0004 FK, O

OSIDEN612 technical-manual-operational-supplement-document- 0244 FK
sequential-identifier
RSIDEN613 technical-manual-routine-supplement-document-sequential- 0244 FK
identifier
SSIDEN611 technical-manual-safety-supplement-document-sequential- 0244 FK
identifier

B.5.14.21. Table 573, Correlation of technical order page supplements (TOPS) to technical manuals.
(DODTMSUPSET-TOPS). This table correlates multiple TOPS which are simultaneously effective with the
technical order to which they pertain. This entity represents the technical order with TOPS incorporated. (See
also: Table 614.)

a. Attribute changed-technical-manual-document-identifier (CTMIDN572) inherited from Table 572 and

changed-technical-manual-document-identifier (CTMIDN614) inherited from Table 614 must both have
the same value. Therefore they merge and assume the identity changed-technical-manual-document-
identifier (CTMIDN572).

Code Data Element Title DED Key

CTMIDN572 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
SETDAT572 technical-manual-document-supplement-set-effective-date 0082 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TMNTYP550 technical-manual-document-type-code 0004 FK
TOPIDN614 technical-manual-page-supplement-document-sequential- 0244 FK
identifier

B.5.14.22. Tables 574 through 599. Reserved.

B-246
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.15. Document supplements. The entity tables numbered in the range of 600 through 650 contain the
identification of, and information concerning, supplements to documents. Supplements, as used herein, refers to
document changes or modifications which are intended to augment a document and are treated as separate
documents for the purpose of review, approval and distribution, but which are identified by the document they are
to augment. This type of document can be called many different names: change pages, revision sheets, notice,
supplement, amendment, etc. One example is supplements to military technical manuals; these are prepared,
reviewed, approved, and distributed as independent documents, but are identified with the same number as the
technical manual they are to supplement. Another example would be changes to military standards; the change
pages, along with acompanying pen and ink change instructions are prepared, reviewed, approved, and distributed
as independent documents, but are identified with the same number as the military standard they are to change.
The relationship between these various entity tables are depicted in Figures 15SUP1 and 15SUP6.

B.5.15.1. Table 600, Reserved.

B.5.15.2. Table 601, Document supplement identification (DOCSUPREV). This table is a category of
GENERIC-DOCREV/011 for the case where the value of the document type code is 'DOCSUP'. It contains those
supplements, addendums, changes, etc. which are treated as independent documents for the purpose of review and
distribution, but which are identified only as iterations of another document. For example, Operational
Supplements to DOD technical manuals are identified by the technical manual, technical manual revision, and
change to the technical manual revision, as well as their unique identifier. Therefore, entries in this table must
always be associated with another document from which they inherit their primary identification. These are some
times referred to as Pen & Ink changes or slip-sheets. This entity addresses the package of revised pages or
instructions to revise pages only. (See also: DOD-TMREV/554 for contrast.)

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

SUPTYP601 supplement-document-type-code 0162 M

B.5.15.3. Tables 602 through 609. Reserved.

B.5.15.4. Table 610, DOD technical manual change identification (DOD-TMCHG). This table is a category of
Table DOCSUPREV/601 for the case where the value of supplement-document-type-code (SUPTYP601) in Table
601 is 'CHG'. It contains the identification of Department of Defense Technical Manual Change.

a. Changes to DOD technical manuals are numbered (or lettered) based on the current technical manual
revision in effect. Therefore, the value of document-identifier (DOCIDN010) inherited from Table 601
must be the same as the concatenation of the values of document-alphanumeric-identifier (DOCNUM554)
and technical-manual-document-revision-issue-date (ISSDAT570) inherited from Table 570. This
concatenation assumes the identity revised-technical-manual-document-identifier (RTMIDN610). The
entries in this table represent the change (supplement) only. (See also: Table 571.)

B-247
GENERIC-DOCREV / 011 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-generic-revision

REVISED-DODTM / 570 (from 14TM3)

document-type-code
us-dod-document-source-organization-code
document-alphanumeric-identifier TMCHG
TECHMAN
tm-revision-issue-date
DOCSUPREV / 601 (with 15SUP2, 15SUP3, 15SUP4, 15SUP5, 15SUP6))
document-source-entity-identifier (FK)
document-identifier (FK) ECP-TECHMAN / 291 (from 6ECP5)
document-type-code (FK)
ecp-cage-code
document-generic-revision (FK)
ecp-identifier
supplement-document-type-code ECP
ecp-revision
may be basis for us-dod-document-source-organization-code
identification of supplement-document-type-code document-alphanumeric-identifier
TECHMAN

CHG
ECPACT / 262 (from 6ECP5)
ecp-cage-code
ecp-identifier

B-248
ECP DOD-TMCHG / 610 (see 14TM3)
ecp-revision us-dod-document-source-organization-code.(document-source-entity-identifier,us-dod-document-source-organization-code) (FK)
APPENDIX B

enterprise-identifier revised-tm-identifier.(document-identifier,tm-revision-issue-date,document-alphanumeric-identifier) (FK)

MIL-STD-2549

program-name document-type-code (FK)

ccb-name tm-change-identifier.document-generic-revision (FK)
ecp-implementation-action-identifier
TECHMAN (FK)

may be the result of

ECP-TM-CHG / 615
us-dod-document-source-organization-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

may direct the revised-tm-identifier.(revised-tm-identifier,document-alphanumeric-identifier) (FK)

issuance of document-type-code (FK)
tm-change-identifier (FK)
ecp-cage-code (FK) may require the
ecp-identifier (FK) issuance of
ECP (FK)
FIGURE 15SUP1
DOCUMENT SUPPLEMENTS ecp-revision (FK)
enterprise-identifier (FK)
program-name (FK)
ccb-name (FK)
ecp-implementation-action-identifier (FK)
TECHMAN (FK)
CHANGED-DODTM / 571 (from 14TM3)
us-dod-document-source-organization-code
DOCSUPREV / 601 (from 15SUP1)
revised-tm-identifier
document-source-entity-identifier ECP-TECHMAN / 291 (from 6ECP5)
TECHMAN
tm-change-identifier document-identifier ecp-cage-code
document-type-code ecp-identifier
document-generic-revision ECP
ecp-revision
supplement-document-type-code us-dod-document-source-organization-code
may be basis for
identification of document-alphanumeric-identifier
TECHMAN
supplement-document-type-code
S-SUP

ECPACT / 262 (from 6ECP5)

ecp-cage-code DOD-TMSSUP / 611 (see 14TM3)
ecp-identifier us-dod-document-source-organization-code.(document-source-entity-identifier,us-dod-document-source-organization-code) (FK)
ECP changed-tm-identifier.(document-identifier,revised-tm-identifier,tm-change-identifier) (FK)
ecp-revision document-type-code (FK)

B-249
enterprise-identifier tm-safety-supplement-identifier.document-generic-revision (FK)
program-name
APPENDIX B

TECHMAN (FK)
MIL-STD-2549

ccb-name
ecp-implementation-action-identifier

may be the result of

ECP-TM-SSUP / 616
ecp-cage-code (FK)
ecp-identifier (FK)
ECP (FK)
may direct the us-dod-document-source-organization-code (FK)
issuance of changed-tm-identifier.(changed-tm-identifier,document-alphanumeric-identifier) (FK) may require the
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-type-code (FK) issuance of

tm-safety-supplement-identifier (FK)
ecp-revision (FK)
FIGURE 15SUP2 TECHMAN (FK)
DOCUMENT SUPPLEMENTS enterprise-identifier (FK)
program-name (FK)
ccb-name (FK)
ecp-implementation-action-identifier (FK)
CHANGED-DODTM / 571 (from 14TM3) DOCSUPREV / 601 (from 15SUP2)
us-dod-document-source-organization-code document-source-entity-identifier
ECP-TECHMAN / 291 (from 6ECP5)
revised-tm-identifier document-identifier
TECHMAN document-type-code ecp-cage-code
tm-change-identifier document-generic-revision ecp-identifier
ECP
supplement-document-type-code ecp-revision
us-dod-document-source-organization-code
document-alphanumeric-identifier
may be basis for supplement-document-type-code TECHMAN
identification of

O-SUP

ECPACT / 262 (from 6ECP5)

ecp-cage-code DOD-TMOSUP / 612 (see 14TM3)
ecp-identifier us-dod-document-source-organization-code.(document-source-entity-identifier,us-dod-document-source-organization-code) (FK)
ECP changed-tm-identifier.(document-identifier,tm-change-identifier,revised-tm-identifier) (FK)
ecp-revision document-type-code (FK)
enterprise-identifier tm-operational-supplement-identifier.document-generic-revision (FK)
program-name
ccb-name TECHMAN (FK)
ecp-implementation-action-identifier

B-250
may be the result of
APPENDIX B
MIL-STD-2549

ECP-TM-OSUP / 617
ecp-cage-code (FK)
ecp-identifier (FK)
ECP (FK)
may direct the us-dod-document-source-organization-code (FK)
issuance of changed-tm-identifier.(changed-tm-identifier,document-alphanumeric-identifier) (FK) may require the
document-type-code (FK) issuance of
tm-operational-supplement-identifier (FK)
ecp-revision (FK)
TECHMAN (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 15SUP3 enterprise-identifier (FK)

DOCUMENT SUPPLEMENTS program-name (FK)
ccb-name (FK)
ecp-implementation-action-identifier (FK)
CHANGED-DODTM / 571 (from 14TM3) DOCSUPREV / 601 (from 15SUP2)
us-dod-document-source-organization-code document-source-entity-identifier ECP-TECHMAN / 291 (from 6ECP5)
revised-tm-identifier document-identifier ecp-cage-code
TECHMAN document-type-code ecp-identifier
tm-change-identifier document-generic-revision ECP
ecp-revision
supplement-document-type-code us-dod-document-source-organization-code
document-alphanumeric-identifier
TECHMAN
may be basis for supplement-document-type-code
identification of

R-SUP

ECPACT / 262 (from 6ECP5)

ecp-cage-code DOD-TMRSUP / 613 (see 14TM3)
ecp-identifier us-dod-document-source-organization-code.(document-source-entity-identifier,us-dod-document-source-organization-code) (FK)
ECP changed-tm-identifier.(document-identifier,tm-change-identifier,revised-tm-identifier) (FK)
ecp-revision document-type-code (FK)
enterprise-identifier tm-routine-supplement-identifier.document-generic-revision (FK)
program-name
ccb-name TECHMAN (FK)
ecp-implementation-action-identifier

B-251
may be the result of
APPENDIX B
MIL-STD-2549

ECP-TM-RSUP / 618
ecp-cage-code (FK)
ecp-identifier (FK)
ECP (FK)
may direct the us-dod-document-source-organization-code (FK)
issuance of changed-tm-identifier.(changed-tm-identifier,document-alphanumeric-identifier) (FK) may require the
document-type-code (FK) issuance of
tm-routine-supplement-identifier (FK)
ecp-revision (FK)
TECHMAN (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 15SUP4 enterprise-identifier (FK)

DOCUMENT SUPPLEMENTS program-name (FK)
ccb-name (FK)
ecp-implementation-action-identifier (FK)
CHANGED-DODTM / 571 (from 14TM3) DOCSUPREV / 601 (from 15SUP2)
us-dod-document-source-organization-code document-source-entity-identifier ECP-TECHMAN / 291 (from 6ECP5)
revised-tm-identifier document-identifier ecp-cage-code
TECHMAN document-type-code ecp-identifier
tm-change-identifier document-generic-revision ECP
supplement-document-type-code ecp-revision
us-dod-document-source-organization-code
document-alphanumeric-identifier
may be basis for supplement-document-type-code TECHMAN
identification of

TOPS

ECPACT / 262 (from 6ECP5)

ecp-cage-code DOD-TOPS / 614 (see 14TM3)
ecp-identifier
ECP us-dod-document-source-organization-code.(document-source-entity-identifier,us-dod-document-source-organization-code) (FK)
ecp-revision changed-tm-identifier.(document-identifier,tm-change-identifier,revised-tm-identifier) (FK)
enterprise-identifier document-type-code (FK)
program-name to-page-supplement-identifier.document-generic-revision (FK)
ccb-name TECHMAN (FK)
ecp-implementation-action-identifier

B-252
may be the result of
APPENDIX B
MIL-STD-2549

ECP-TOPS / 619
ecp-cage-code (FK)
ecp-identifier (FK)
ECP (FK)
may direct the us-dod-document-source-organization-code (FK)
issuance of changed-tm-identifier.(changed-tm-identifier,document-alphanumeric-identifier) (FK) may require the
document-type-code (FK) issuance of
to-page-supplement-identifier (FK)
ecp-revision (FK)
TECHMAN (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE 15SUP5 enterprise-identifier (FK)

DOCUMENT SUPPLEMENTS program-name (FK)
ccb-name (FK)
ecp-implementation-action-identifier (FK)
APPRECP-SPECREV / 287 (from 6ECP2)
design-cage-code
DOCSUPREV / 601 (from 15SUP1) PSPECREV / 101 (from 3PSPEC1)
document-alphanumeric-identifier
document-type-code document-source-entity-identifier design-cage-code
document-revision document-identifier document-alphanumeric-identifier
ecp-cage-code document-type-code document-type-code
ecp-alphanumeric-identifier document-generic-revision document-alphanumeric-revision
ECP
supplement-document-type-code

supplement-document-type-code
may be the resulting
revision from
may be basis for

B-253
SCN identification of
APPENDIX B
MIL-STD-2549

DOD-SCN / 620 (see 3SPEC3)

design-cage-code.(document-source-entity-identifier,design-cage-code) (FK)
revised-program--unique-specification-identifier.(document-identifier,document-alphanumeric-revision,document-revision,document-alphanumeric-identifier) (FK)
DOCSUP.document-type-code (FK)
scn-identifier.document-generic-revision (FK)
P-SPEC.document-type-code (FK)
ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

ECP (FK)

FIGURE 15SUP6
DOCUMENT SUPPLEMENTS
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Changes to technical manuals are identified by an issue date of the basic manual and the change number
(or letter).

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 601 assumes the role
technical-manual-change-document-identifier (CHGNUM610).

d. Attribute united-states-defense-department-document-source-enterprise-acronym-identification-code
(SRCDOD552) inherited from Table 570 and document-source-entity-identifier (SRCIDN010) inherited
from Table 601 must both have the same value. Therefore they merge and assume the identity united-
states-defense-department-document-source-enterprise-acronym-identification-code (SRCDOD552).

Code Data Element Title DED Key

CHGNUM610 technical-manual-change-document-identifier 0134 FK
DOCTYP010 document-type-code 0004 FK
RTMIDN610 revised-technical-manual-document-identifier 0135 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.15.5. Table 611, DOD technical manual safety supplement identification (DOD-TMSSUP). This table is a
category of Table DOCSUPREV/601 for the case where the value of supplement-document-type-code
(SUPTYP601) in Table 601 is 'SS'. It contains the identification of Department of Defense Technical Manual
Safety Supplements.

a. Safety Supplements to DOD technical manuals are numbered based on the current technical manual
revision and change in effect. Therefore, the value of document-identifier (DOCIDN010) inherited from
Table 601 must be the same as the concatenation of the values of revised-technical-manual-document-
identifier (RTMIDN571) and technical-manual-document-change-identifier (CHGNUM571) inherited
from Table 571. This concatenation assumes the identity changed-technical-manual-document-identifier
(CTMIDN611). The entries in this table represent the safety supplement only. (See also: Table 572.)

b. Safety Supplements to technical manuals are identified by an issue date.

c. Attribute united-states-defense-department-document-source-enterprise-acronym-identification-code
(SRCDOD552) inherited from Table 571 and document-source-entity-identifier (SRCIDN010) inherited
from Table 601 must both have the same value. Therefore they merge and assume the identity united-
states-defense-department-document-source-enterprise-acronym-identification-code (SRCDOD552).

d. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 601 assumes the role
technical-manual-safety-supplement-document-sequential-identifier (SSIDEN611).

Code Data Element Title DED Key

CTMIDN611 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

B-254
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SSIDEN611 technical-manual-safety-supplement-document-sequential- 0244 FK

identifier

TMNTYP550 technical-manual-document-type-code 0004 FK

SISSDT611 technical-manual-safety-supplement-document-issue-date 0082 M

B.5.15.6. Table 612, DOD technical manual operational supplement identification (DOD-TMOSUP). This
table is a category of Table DOCSUPREV/601 for the case where the value of supplement-document-type-code
(SUPTYP601) in Table 601 is 'OS'. It contains the identification of Department of Defense Technical Manual
Operational Supplements.

a. Operational Supplements to DOD technical manuals are numbered based on the current technical manual
revision and change in effect. Therefore, the value of document-identifier (DOCIDN010) inherited from
Table 601 must be the same as the concatenation of the values of revised-technical-manual-document-
identifier (RTMIDN571) and technical-manual-document-change-identifier (CHGNUM571) inherited
from Table 571. This concatenation assumes the identity changed-technical-manual-document-identifier
(CTMIDN612). The entries in this table represent the operational supplement only. (See also: Table
572.)

b. Operational Supplements to technical manuals are identified by an issue date.

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 601 assumes the role
technical-manual-operational-supplement-document-sequential-identifier (OSIDEN612).

d. Attribute united-states-defense-department-document-source-enterprise-acronym-identification-code
(SRCDOD552) inherited from Table 571 and document-source-entity-identifier (SRCIDN010) inherited
from Table 601 must both have the same value. Therefore they merge and assume the identity united-
states-defense-department-document-source-enterprise-acronym-identification-code (SRCDOD552).

Code Data Element Title DED Key

CTMIDN612 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
OSIDEN612 technical-manual-operational-supplement-document- 0244 FK
sequential-identifier
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

TMNTYP550 technical-manual-document-type-code 0004 FK

OISSDT612 technical-manual-operational-supplement-document-issue- 0082 M
date

B.5.15.7. Table 613, DOD technical manual routine supplement identification (DOD-TMRSUP). This table is
a category of Table DOCSUPREV/601 for the case where the value of supplement-document-type-code
(SUPTYP601) in Table 601 is 'SUP'. It contains the identification of Department of Defense Technical Manual
Routine Supplements.

a. Routine Supplements to DOD technical manuals are numbered based on the current technical manual
revision and change in effect. Therefore, the value of document-identifier (DOCIDN010) inherited from
Table 601 must be the same as the concatenation of the values of revised-technical-manual-document-

B-255
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

identifier (RTMIDN571) and technical-manual-document-change-identifier (CHGNUM571) inherited

from Table 571. This concatenation assumes the identity changed-technical-manual-document-identifier
(CTMIDN613). The entries in this table represent the operational supplement only. (See also: Table
572.)

b. Operational Supplements to technical manuals are identified by an issue date.

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 601 assumes the role
technical-manual-routine-supplement-document-sequential-identifier (RSIDEN613).

Code Data Element Title DED Key

CTMIDN613 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
RSIDEN613 technical-manual-routine-supplement-document-sequential- 0244 FK
identifier
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

TMNTYP550 technical-manual-document-type-code 0004 FK

RISSDT613 technical-manual-routine-supplement-document-issue-date 0082 M

B.5.15.8. Table 614, DOD technical order page supplement identification (DOD-TMTPSUP). This table is a
category of Table DOCSUPREV/601 for the case where the value of supplement-document-type-code
(SUPTYP601) in Table 601 is 'TP'. It contains the identification of Department of Defense Technical Order Page
Supplements (TOPS).

a. TOPS to DOD technical manuals are numbered based on the current technical manual revision and
change in effect. Therefore, the value of document-identifier (DOCIDN010) inherited from Table 601
must be the same as the concatenation of the values of revised-technical-manual-document-identifier
(RTMIDN571) and technical-manual-document-change-identifier (CHGNUM571) inherited from Table
571. This concatenation assumes the identity changed-technical-manual-document-identifier
(CTMIDN614). The entries in this table represent the TOPS only. (See also: Table 572.)

b. Attribute united-states-defense-department-document-source-enterprise-acronym-identification-code
(SRCDOD552) inherited from Table 571 and document-source-entity-identifier (SRCIDN010) inherited
from Table 601 must both have the same value. Therefore they merge and assume the identity united-
states-defense-department-document-source-enterprise-acronym-identification-code (SRCDOD552).

c. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 601 assumes the role
technical-manual-page-supplement-document-sequential-identifier (TOPIDN614).

B-256
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

CTMIDN614 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TOPIDN614 technical-manual-page-supplement-document-sequential- 0244 FK
identifier

TMNTYP550 technical-manual-document-type-code 0004 FK

TOPISS614 technical-manual-supplement-document-issue-date 0082 M

B.5.15.9. Table 615, Correlation of ECPs to technical manual changes (ECP-TMCHG). This table correlates
approved ECPs to the Technical Manual/Order change which results from the approved ECP.

a. Attribute document-alphanumeric-identifier (DOCNUM552) inherited from Table 291 and revised-

technical-manual-document-identifier (RTMIDN610) inherited from Table 610 must both have the same
value. Therefore they merge and assume the identity revised-technical-manual-document-identifier
(RTMIDN615).

Code Data Element Title DED Key

CHGNUM610 technical-manual-change-document-identifier 0134 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
RTMIDN615 revised-technical-manual-document-identifier 0135 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

CCBNAM700 program-configuration-control-board-name 0151 FK, O

ECPACT262 engineering-change-implementation-process-action-identifier 0072 FK, O
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ENTIDN002 enterprise-identifier 0052 FK, O
PROGNM691 program-name 0059 FK, O
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.15.10. Table 616, Correlation of ECPs to technical manual safety supplements (ECP-TM-SSUP). This table
correlates approved ECPs with the technical manual safety supplements which are created as a result of their
approval.

B-257
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Attribute document-alphanumeric-identifier (DOCNUM552) inherited from Table 291 and changed-

technical-manual-document-identifier (CTMIDN611) inherited from Table 611 must both have the same
value. Therefore they merge and assume the identity changed-technical-manual-document-identifier
(CTMIDN611).

Code Data Element Title DED Key

CTMIDN611 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
SSIDEN611 technical-manual-safety-supplement-document-sequential- 0244 FK
identifier

CCBNAM700 program-configuration-control-board-name 0151 FK, O

B.5.15.11. Table 617, Correlation of ECPs to technical manual operational supplements (ECP-TM-OSUP). This
table correlates approved ECPs with the technical manual operational supplements which are created as a result of
their approval.

a. Attribute document-alphanumeric-identifier (DOCNUM552) inherited from Table 291 and changed-

technical-manual-document-identifier (CTMIDN612) inherited from Table 612 must both have the same
value. Therefore they merge and assume the identity changed-technical-manual-document-identifier
(CTMIDN612).

Code Data Element Title DED Key

CTMIDN612 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
OSIDEN612 technical-manual-operational-supplement-document- 0244 FK
sequential-identifier

B-258
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SRCDOD552 united-states-defense-department-document-source- 0002 FK

enterprise-acronym-identification-code

CCBNAM700 program-configuration-control-board-name 0151 FK, O

B.5.15.12. Table 618, Correlation of ECPs to technical manual routine supplements (ECP-TM-RSUP). This
table correlates approved ECPs with the technical manual routine supplements which are created as a result of
their approval.

a. Attribute document-alphanumeric-identifier (DOCNUM552) inherited from Table 291 and changed-

technical-manual-document-identifier (CTMIDN613) inherited from Table 613 must both have the same
value. Therefore they merge and assume the identity changed-technical-manual-document-identifier
(CTMIDN613).

Code Data Element Title DED Key

CTMIDN613 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
PROGNM691 program-name 0059 FK
RSIDEN613 technical-manual-routine-supplement-document-sequential- 0244 FK
identifier
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code

CCBNAM700 program-configuration-control-board-name 0151 FK, O

ECPACT262 engineering-change-implementation-process-action-identifier 0072 FK, O
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ENTIDN002 enterprise-identifier 0052 FK, O
TMNTYP550 technical-manual-document-type-code 0004 FK

B.5.15.13. Table 619, Correlation of ECPs to TOPS (ECP-TOPS). This table correlates approved ECPs with the
technical order page supplements which are created as a result of their approval.

a. Attribute document-alphanumeric-identifier (DOCNUM552) inherited from Table 291 and changed-

technical-manual-document-identifier (CTMIDN614) inherited from Table 614 must both have the same

B-259
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

value. Therefore they merge and assume the identity changed-technical-manual-document-identifier

(CTMIDN614).

Code Data Element Title DED Key

CTMIDN614 changed-technical-manual-document-identifier 0218 FK
DOCTYP010 document-type-code 0004 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SRCDOD552 united-states-defense-department-document-source- 0002 FK
enterprise-acronym-identification-code
TOPIDN614 technical-manual-page-supplement-document-sequential- 0244 FK
identifier

CCBNAM700 program-configuration-control-board-name 0151 FK, O

B.5.15.14. Table 620, Program-unique specification change notices (SCN). This table is a category of Table
DOCSUPREV/601 for the case where the value of supplement-document-type-code (SUPTYP601) in Table 601 is
'SCN'. It contains the identification of specification change notices (SCNs) to program-unique specifications. It is
included in this conceptual schema for legacy documents only.

a. SCNs to program-unique specifications are numbered based on the current specification revision in effect.
Therefore, the value of document-identifier (DOCIDN010) inherited from Table 601 must be the same as
the value of document-alphanumeric-identifier (DOCNUM020) inherited from Table 287 and also must
be the same as the concatenation of the values of document-alphanumeric-identifier (DOCNUM020) and
document-alphanumeric-revision-identifier (DOCREV101) inherited from Table 101. This concatenation
assumes the identity revised-program--unique-specification-document-identifier (RSPCID620). The
entries in this table represent the SCN only. (See also: Table 149.)

b. Attribute design-enterprise-defense-logistics--assigned-identification-code (DESCAG100) inherited from

Table 101, design-enterprise-defense-logistics--assigned-identification-code (DESCAG100) inherited
from Table 287, and document-source-entity-identifier (SRCIDN010) inherited from Table 601 must all
be the same. Therefore, they merge and assume the identity design-enterprise-defense-logistics--assigned-
identification-code (DESCAG100).

c. Attribute document-type-code (DOCTYP010) inherited from Table 601 assumes the role supplemental-
document-type-code (DSUPTY620).

d. The value of document-alphanumeric-revision-identifier (DOCREV101) inherited from Table 287 and the
value of document-generic-revision-identifier (DOCREV011) inherited from Table 601 must be the same.

B-260
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Therefore, they merge into the identity program--unique-specification-change-notice-document-

sequential-identifier (SCNIDN620).

e. Attribute document-type-code (DOCTYP010) inherited from Table 101 and document-type-code

(DOCTYP010) inherited from Table 287 must have the same value and merge to assume the role
program--unique-specification-document-type-code (SPCTYP620).

Code Data Element Title DED Key

DESCAG100 design-enterprise-defense-logistics--assigned-identification- 0001 FK
code
DSUPTY620 supplemental-document-type-code 0004 FK
RSPCID620 revised-program--unique-specification-document-identifier 0149 FK
SCNIDN620 program--unique-specification-change-notice-document- 0193 FK
sequential-identifier

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK

defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
SPCTYP620 program--unique-specification-document-type-code 0004 FK

B.5.15.15. Tables 621 through 649. Reserved.

B-261
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.16. Data item descriptions. Entity tables numbered in the range of 650 through 669 contain the identification
of contain the identification of military data item descriptions. (For the U.S. DOD, DIDs are defined in MIL-STD-
963). These documents have been traditionally used primarily by the Department of Defense; however, with the
advent of acquisition reform, many enterprises other than the DOD are finding a need to create them. The
relationships between these various DID document entity tables are depicted in Figure 16DID1.

NUMDOC / 020 (from 1GEN3)

document-source-enterprise-identifier
document-alphanumeric-identifier
document-type-code

NUMDOCREV / 021 (from 1GEN4)

document-type-code document-source-enterprise-identifier
document-alphanumeric-identifier
document-type-code
document-generic-revision

DID / 650
document-type
document-source-enterprise-identifier (FK)
did-alphanumeric-identifier.document-alphanumeric-identifier (FK)
DID.document-type-code (FK)

DIDREV / 651 (de facto child of 630) (see 26CON2)

document-source-enterprise-identifier (FK)
FIGURE 16DID1 did-alphanumeric-identifier.document-alphanumeric-identifier (FK)
DATA ITEM DESCRIPTION (DID) DEFINITION DID.document-type-code (FK)
document-generic-revision (FK)

B.5.16.1. Table 650, Data item description definition (DID). This table includes the unique and primary
identification of data item description (DID) documents. A DID is one subcategory of Table NUMDOC/020 for the
case where the value of document-type-code (DOCTYP010) is 'DID'. Although not shown in Figure 16DID1, this
table may be further subtyped based on the value of enterprise-identification-type-code (ENTTYP002) in Table
002. This further subcategorization (reflecting the entity hierarchy in Figure 1GEN1) allows for the incorporation
of organization-specific identification rules for DIDs.

a. Attribute document-alphanumeric-identifier (DOCNUM020) inherited from Table 020 assumes the role
data-item-description-document-alphanumeric-identifier (DIDNUM650).

b. Attribute document-type-code (DOCTYP010) inherited from Table 020 assumes the role data-item-
description-document-type-code (DIDTYP650).

B-262
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DIDNUM650 data-item-description-document-alphanumeric-identifier 0003 FK
DIDTYP650 data-item-description-document-type-code 0004 FK
SRCENT020 document-source-enterprise-identifier 0052 FK

B.5.16.2. Table 651, Data item description revision definition (DIDREV). This table is a subtype of Table
NUMDOCREV/021 for the case where the value of document-type-code (DOCTYP010) is 'DID'; it contains the
revision history of data item description documents. Due to parallel categorization, Table 651 is a de facto child of
Table 650.

a. Because this table is a de facto child of Table 650, document-alphanumeric-identifier (DOCNUM020)

inherited from Table 021 is really a data-item-description-document-alphanumeric-identifier
(DIDNUM650) existing in Table 650. Therefore, DOCNUM020 assumes the identity DIDNUM650.

b. Because this table is a de facto child of Table 650, document-type-code (DOCTYP010) inherited from
Table 021 is really a data-item-description-document-type-code (DIDTYP650) existing in Table 650.
Therefore, DOCTYP010 assumes the identity DIDTYP650.

Code Data Element Title DED Key

DIDNUM650 data-item-description-document-alphanumeric-identifier 0003 FK
DIDTYP650 data-item-description-document-type-code 0004 FK
DOCREV011 document-generic-revision-identifier 0243 FK
SRCENT020 document-source-enterprise-identifier 0052 FK

B.5.16.3. Tables 652 through 669. Reserved.

B-263
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.17. Procurement Activity Numbers. Entity tables numbered in the range of 670 through 674 contain the
Procurement Activity Numbers. PANs are not documents; they are merely an alternate index to ECPs and RFDs
used by ARDEC. The relationships between the PAN entity tables and the ECP/RFD entity tables are depicted in
Figure 17PAN1.

PAN / 670
pan RFD / 350 (from 10RFD1)
ECP / 250 (from 6ECP1) year
ecp-cage-code rfd-cage-code
document-type-code rfd-alphanumeric-identifier
ecp-alphanumeric-identifier
ECP RFD

document-type-code

may have an alternate identifier

ECP RFD

PAN-ECP / 671 PAN-RFD / 672

pan (FK) pan (FK)
year (FK) year (FK)

ecp-cage-code (FK) rfd-cage-code (FK)

ecp-alphanumeric-identifier (FK) rfd-alphanumeric-identifier (FK)
ECP (FK) RFD (FK)

FIGURE 17PAN1
PROCURING ACTIVITY NUMBER (PAN) CORRELATION

B.5.17.1. Table 670, Procuring activity number definition (PAN). This table includes the unique and primary
identification of a procuring activity [tracking] number. A PAN is not a document, but merely an alternate
identification for ECPs and RFDs. PANs are used exclusively by U.S. Army/ARDEC.

a. The value of document-type-code (DOCTYP670) must be 'ECP' or 'RFD'.

Code Data Element Title DED Key

PANNUM670 document-procuring-activity--assigned-identifier 0178 K
YEARNO670 julian-year-period-identifier 0219 K

DOCTYP670 document-type-code 0004 M

B.5.17.2. Table 671, Correlation of PAN to ECP (PAN-ECP). This table is a subcategory of Table PAN/670 for
the case where the value of document-type-code (DOCTYP670) is 'ECP'. It contains the subset of the contents of
Table 670 and consisting of those PANs which are alternate identifiers for ECPs. It correlates PANs to ECP
identifiers.

B-264
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

PANNUM670 document-procuring-activity--assigned-identifier 0178 FK
YEARNO670 julian-year-period-identifier 0219 FK

ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK, AK1

defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK, AK1
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK, AK1

B.5.17.3. Table 672, Correlation of PAN to RFD (PAN-RFD). This table is a subcategory of Table PAN/670
for the case where the value of document-type-code (DOCTYP670) is 'RFD'. It contains the subset of the contents
of Table 670 and consisting of those PANs which are alternate identifiers for RFDs. It correlates PANs to RFD
identifiers.

Code Data Element Title DED Key

PANNUM670 document-procuring-activity--assigned-identifier 0178 FK
YEARNO670 julian-year-period-identifier 0219 FK

RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK, AK1

logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK, AK1
RFDTYP350 deviation-request-document-type-code 0004 FK, AK1

B.5.17.4. Tables 673 and 674. Reserved.

B-265
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.18. Audit Action Items. Entity tables numbered in the range of 675 through 689 contain the identification
and status of all action items which are the result of a configuration audit of any type. The relationships between
the audit action item entity tables are depicted in Figure 18AUD1.

B.5.18.1. Table 675, Configuration management audits (AUD). This table contains the unique identification of
configuration management audits. It is used to provide the basis for identifying action items and tracking them
until completion. Although designed solely for the configuration management audits (PCA and FCA), its use can
be expanded for all program reviews (for example, SSR, SDR, etc.).

Code Data Element Title DED Key

AUDDAT675 audit-process-date 0082 K
AUDTYP675 audit-process-type-code 0070 K
CIIDEN695 configuration-item-product-identifier 0111 FK
CONIDN950 contract-document-identifier 0015 FK

B.5.18.2. Table 676, Audit actions (AUDACT). This table contains the unique identifier and description of
each major action item which results from a configuration management audit. The enterprise-identifier
(ENTIDN002) and enterprise-office-name (OFFSYM941) inherited from Table 941 reflect the responsibility for
the completion of this action.

Code Data Element Title DED Key

AUDACT676 audit-process-action-identifier 0072 K
AUDDAT675 audit-process-date 0082 FK
AUDTYP675 audit-process-type-code 0070 FK
CIIDEN695 configuration-item-product-identifier 0111 FK
CONIDN950 contract-document-identifier 0015 FK

ENTIDN002 enterprise-identifier 0052 FK

OFFSYM941 enterprise-office-name 0044 FK
ACTCOM676 process-action-comment-text 0066
ACTDES676 audit-process-required-action-description-text 0065 M
ACTTTL676 process-action-item-title-name 0136 M

B.5.18.3. Table 677. Reserved.

B-266
AUD / 675
CONDOC / 950 (from 26CON1) CI / 695 (from 19CI1)
audit-type-code may have design
contract-identifier may require audit-date validated by ci-identifier
performance of ci-identifier (FK)
contract-identifier (FK)

OFFICE / 941 (from 25ADD1)

may result in enterprise-identifier
office-symbol

AUDACT / 676
audit-type-code (FK) AUDAGENSTAT / 678
audit-date (FK) may be responsible for audit-type-code (FK)
CONMOD / 951 (from 26CON2) ci-identifier (FK) audit-date (FK)
contract-identifier contract-identifier (FK) ci-identifier (FK)
contract-modification audit-action-item-identifier has close-out life cycle contract-identifier (FK)
P audit-action-item-identifier (FK)
enterprise-identifier (FK)
audit-action-item-disposition-code
office-symbol (FK)
audit-action-item-disposition-date
may have
unfulfilled may document
requirements violation of may be resolved
by creation of

AUD-CONREF / 679 may AUD-ECP / 682

document

B-267
audit-type-code (FK) may document audit-type-code (FK)
violation of ECP / 250 (from 6ECP1)
audit-date (FK) violation of audit-date (FK)
may correct ecp-cage-code
APPENDIX B

ci-identifier (FK)
MIL-STD-2549

ci-identifier (FK)
contract-identifier (FK) deficiencies ecp-alphanumeric-identifier
audit-action-item-identifier (FK)
audit-action-item-identifier (FK) identified by ECP
contract-identifier (FK)
document-reference-citation ecp-cage-code (FK)
ecp-alphanumeric-identifier (FK)
contract-modification (FK) ECP (FK)

AUD-SOWREF / 680
AUD-DOCREF / 681
audit-type-code (FK)
SOW / 957 (from 26CON2) audit-date (FK) audit-type-code (FK)
may have audit-date (FK)
contract-identifier ci-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

unfulfilled ci-identifier (FK) may have GENERIC-DOCREV / 011 (from 1GEN2)

contract-modification contract-identifier (FK)
requirements contract-identifier (FK) unfulfilled
sow-identifier audit-action-item-identifier (FK) document-source-entity-identifier
audit-action-item-identifier (FK) requirements document-identifier
contract-modification (FK) document-type-code
sow-identifier (FK) document-generic-revision (FK)
document-source-entity-identifier (FK) document-generic-revision
document-reference-citation
document-identifier (FK)
FIGURE 18AUD1 document-type-code (FK)
AUDIT ACTIONS document-reference-citation
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.18.4. Table 678, Audit action subsidiary item status (AUDAGENSTAT). Each major audit action item
may include more than one specific subsidiary action, with suspense dates, which will have to be accomplished to
close out the action item. This table provides the status of each subsidiary action which results from a
configuration management audit.

Code Data Element Title DED Key

STACOD678 audit-process-action-item-disposition-status-code 0021 K
STADAT678 audit-process-action-item-disposition-status-date 0082 K
AUDACT676 audit-process-action-identifier 0072 FK
AUDDAT675 audit-process-date 0082 FK
AUDTYP675 audit-process-type-code 0070 FK
CIIDEN695 configuration-item-product-identifier 0111 FK
CONIDN950 contract-document-identifier 0015 FK

ACTCOM678 process-action-comment-text 0066

B.5.18.5. Table 679, Correlation of audit actions to contract references (AUD-CONREF). This table allows
correlation of audit action items to contract sections, paragraphs or other specific references which are the cause of
the action item.

Code Data Element Title DED Key

CONMOD951 contract-document-revision-identifier 0120 FK

DOCREF679 document-reference-citation-identifier 0075 M

B.5.18.6. Table 680, Correlation of audit actions to statement of work references (AUD-SOWREF). This table
allows correlation of audit action items to contractually specified statement of work sections, paragraphs or other
specific references which are the cause of the action item.

Code Data Element Title DED Key

CONMOD951 contract-document-revision-identifier 0120 FK

SOWIDN957 work-statement-document-identifier 0229 FK

B-268
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DOCREF680 document-reference-citation-identifier 0075 M

B.5.18.7. Table 681, Correlation of audit action items to document references (AUD-DOCREF). This table
allows correlation of audit action items to sections, paragraphs, zones or other specific references in a drawing,
program-unique specification, or other document which is the cause of the action item. Because these must be
requirements documents, the value of document-type-code (DOCTYP010) inherited from Table 011 cannot be
'DOCSUP', 'MODINST', 'MODREQ', 'PLNPROC', 'REPORT', or 'TM'.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK

DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK
DOCREF681 document-reference-citation-identifier 0075 M

B.5.18.8. Table 682, Correlation of audit action items to corrective action ECPs (AUD-ECP). This table allows
correlation of audit action items to the ECP(s) which are created to resolve the action item.

Code Data Element Title DED Key

AUDACT676 audit-process-action-identifier 0072 FK
AUDDAT675 audit-process-date 0082 FK
AUDTYP675 audit-process-type-code 0070 FK
CIIDEN695 configuration-item-product-identifier 0111 FK
CONIDN950 contract-document-identifier 0015 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK

B.5.18.9. Tables 683 through 689. Reserved.

B-269
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.19. Configuration Items and Configuration Control Boards. Entity tables numbered in the range of 690
through 709 contain the identification of configuration items by designation and name as well as associated
attributes. They also contain the identification of Configuration Control Boards (CCBs), CCB directives and
related information. The relationships between the CI and CCB entity tables are depicted in Figures 19CI1 and
19CI2.

B.5.19.1. Table 690, Configuration item nomenclature (CINOMEN). This table contains the approved
configuration item nomenclatures.

a. The attributes part-product-name (PARNAM209) inherited from Table 209 and configuration-item-
product-designation-identifier (CIDESG693) inherited from Table 693 are concatenated and assume the
role configuration-item-product-nomenclature-text (CINOMN690). (See Appendix C for concatenation
order.)

Code Data Element Title DED Key

CINOMN690 configuration-item-product-nomenclature-text 0047 FK

B.5.19.2. Table 691, System/Program name (SYSTEM-PROGRAM). This table contains the program, project,
or system name which identifies a collection of resources and assets bound by a common objective, for example,
HARM, Patriot, F-22, etc.

Code Data Element Title DED Key

PROGNM691 program-name 0059 K

B.5.19.3. Table 692, Correlation of system/programs to the CIs which are used by them (PROGRAM-CI). This
table correlates the system or program name to the nomenclature of the configuration item(s) which are used by
them, and vice versa.

Code Data Element Title DED Key

CIIDEN695 configuration-item-product-identifier 0111 FK
PROGNM691 program-name 0059 FK

B.5.19.4. Table 693, CI designator (CI-DESG). This table contains assigned CI designations.

a. If the value of the configuration-item-product-designation-standard-code (CISTND693) is '1812', '196',

'787', or 'MAV', then the relationship between this table and Table 690 must be 1:1.

Code Data Element Title DED Key

CIDESG693 configuration-item-product-designation-identifier 0045 K

CISTND693 configuration-item-designation--convention-document-code 0051 M

B-270
SUPPORT-CI / 694
CI / 695 (see 8BL1, 18AUD1, 19CI2, 26CON1)
may require support from support-equipment-ci-identifier.ci-identifier (FK)
ci-identifier
primary-equipment-ci-identifier.ci-identifier (FK)
ci-type-code may be support for

PART-NAME / 209 (from PCTSS) CI-DESIG / 693 (see 13TRK1)

part-name ci-designation
ci-standard-code

may be the
official name of is known as

B-271
P
APPENDIX B
MIL-STD-2549

GENERIC-SWPROD / 170 (from 4SW3)

ci-type-code CINOMEN / 690 (see 2DWG1, 3SPEC1, 5PIN4, 7NOR5)
software-source-identifier
ci-nomenclature.(ci-designation,part-name) (FK)
software-generic-identifier

C H

is a is a
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

1
1
CSCI / 696
HWCI / 697
ci-identifier (FK)
ci-identifier (FK)
software-source-identifier (FK) (AK1)
ci-nomenclature (FK) (AK1)
software-generic-identifier (FK) (AK1)

FIGURE 19CI1
CONFIGURATION ITEM
SYS-SYS / 698 ENTERPRISE-PROGRAM / 701
may be comprised of SYSTEM / 691 (see 19BL1)
system-name.program-name (FK) enterprise-identifier (FK)
subsystem-name.program-name (FK) program-name
is managed by program-name (FK) may manage
may be a subsystem of
P
ENTERPRISE / 002 (from 1GEN1)
may be or use enterprise-identifier
STAFF / 943 (from 25ADD1) may be may conduct
may be person-name chairperson of
member of office-address
CI / 695 (from 19CI1)
CCB / 700
ci-identifier CCB-MEMBER / 702
enterprise-identifier (FK)
enterprise-identifier (FK) program-name (FK)
program-name (FK) ccb-name
ccb-name (FK) may be comprised of
person-name (FK) office-address (FK)
is, or is used by office-address (FK) person-name (FK)
ccb-type
higher-level-ccb.(enterprise-identifier,program-name,ccb-name) (FK)
P
PROGRAM-CI / 692 may be responsible for reviewing changes to
program-name (FK) Assertion: The relationship of Table 700 to recommends disposition of
ci-identifier (FK) Table 703 is 1:0 if the value of ccb-type in Assertion: The relation of Table
Table 700 is 'S', and is 1:P for all other 700 to 704 must be 1:0 if the
values of ccb-type. value of higher-level-ccb is not
must have
proposed null-valued.

B-272
change CCB-DIRECTIVE / 704 CAGE-NUM-DOCREV / 023 (from 1GEN4)
reviewed by enterprise-identifier (FK) document-source-cage-code
APPENDIX B
MIL-STD-2549

program-name (FK) document-alphanumeric-identifier

P ccb-name (FK) is reviewed by document-type-code
document-source-cage-code (FK) document-generic-revision
may be next higher
CCB-CI / 703 (see 1GEN2) document-alphanumeric-identifier (FK) level CCB of
enterprise-identifier (FK) document-type-code (FK)
ci-identifier (FK) document-generic-revision (FK)
program-name (FK)
ccb-name (FK) ccb-decision-date
ccb-chairman-disposition
ccb-minutes

document-type-code
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

ECP RFD

CCB-ECP / 705 (de facto child of 251) (see 6ECP5) CCB-RFD / 706 (de facto child of 351) (see 10RFD6)
enterprise-identifier (FK) enterprise-identifier (FK)
program-name (FK) program-name (FK)
ccb-name (FK) ccb-name (FK)
ecp-cage-code.document-source-cage-code (FK) rfd-cage-code.document-source-cage-code (FK)
FIGURE 19CI2 ecp-alphanumeric-identifier.document-alphanumeric-identifier (FK) rfd-alphanumeric-identifier.document-alphanumeric-identifier (FK)
CONFIGURATION CONTROL BOARD ECP.document-type-code (FK) RFD.document-type-code (FK)
ecp-revision.document-generic-revision (FK) rfd-revision.document-generic-revision (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.19.5. Table 694, Correlation of primary and support equipment CIs (SUPPORT-CI). This table correlates
primary equipment CIs (for example, a missile or aircraft) with support equipment CIs (for example, a test
program set [TPS], special inspection equipment [SIE], or program-unique aerospace ground equipment [AGE]).

a. Attribute configuration-item-product-identifier (CIIDEN695) inherited from Table 695 assumes the role
primary-equipment-configuration-item-product-identifier (PCIIDN694).

b. Attribute configuration-item-product-identifier (CIIDEN695) inherited from Table 695 assumes the role
support-equipment-configuration-item-product-identifier (SCIIDN694).

Code Data Element Title DED Key

PCIIDN694 primary-equipment-configuration-item-product-identifier 0111 FK
SCIIDN694 support-equipment-configuration-item-product-identifier 0111 FK

B.5.19.6. Table 695, Configuration item identifiers (CI). This table is a super-type of CI identifiers which
includes both hardware CI (HWCI) nomenclatures and computer software CI (CSCI) design CAGE code and
identifiers.

Code Data Element Title DED Key

CIIDEN695 configuration-item-product-identifier 0111 K

CITYPE695 configuration-item-product-type-code 0115 M

B.5.19.7. Table 696, CSCI identifiers (CSCI). This table is a subtype of Table CI/695 consisting of those CIs
which are computer software CIs (CSCIs). The concatenated value of software-product-source-entity-identifier
(SWSORC170), and software-product-identifier (SWIDEN170) inherited from Table 170 is the CSCI identifier,
and therefore, must be the same as the value of configuration-item-product-identifier (CIIDEN695) for each
instance in this table.

Code Data Element Title DED Key

CIIDEN695 configuration-item-product-identifier 0111 FK

SWIDEN170 software-product-generic-identifier 0060 FK, AK1

SWSORC170 software-product-source-entity-identifier 0033 FK, AK1

B.5.19.8. Table 697, HWCI identifiers (HWCI). This table is a subtype of Table CI/695 consisting of those CIs
which are hardware CIs (HWCIs). The value of the configuration-item-product-nomenclature-text (CINOMN690)
inherited from Table 690 is the HWCI identifier, and therefore, must be the same as the value of configuration-
item-product-identifier (CIIDEN695) for each instance in this table.

Code Data Element Title DED Key

CIIDEN695 configuration-item-product-identifier 0111 FK

CINOMN690 configuration-item-product-nomenclature-text 0047 FK, AK1

B-273
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.19.9. Table 698, System hierarchy (SYS-SYS). This table contains the hierarchy of systems and
subsystems.

a. Attribute program-name (PROGNM691) inherited from Table 691 assumes the role program-subsystem-
name (SUBNAM698).

b. Attribute program-name (PROGNM691) inherited from Table 691 assumes the role program-system-
name (SYSNAM698).

Code Data Element Title DED Key

SUBNAM698 program-subsystem-name 0059 FK
SYSNAM698 program-system-name 0059 FK

B.5.19.10. Table 699. Reserved.

B.5.19.11. Table 700, Configuration Control Board Identification (CCB). This table identifies configuration
control boards (sometimes referred to as configuration change boards or change control boards). CCBs have
responsibility for approving or disapproving the recommended changes to documents which are part of the baseline
for a specific system and/or configuration item under their control. If the CCB is the current document change
authority (CDCA) for the document, it has the final decision as to the disposition of the proposed change. If the
CCB is not the CDCA for the document, then it can recommend a disposition to the CDCA CCB, and it can decide
whether or not to continue use of the document in its baseline, but it cannot direct that the document be changed.
CCBs are often multi-level in responsibility, by area of responsibility (for example, a systems CCB is higher level
than a hardware CCB or software CCB for the same system) within a program (project or system) in an enterprise.
A CCB is always responsible for either a system, one or more CIs, or both.

a. The combination of the human-name (PERNAM943) and the enterprise-office-address-text

(DIVADD942) fields identifies the CCB chairperson.

b. The attributes program-configuration-control-board-name (CCBNAM700) inherited from Table 700,

enterprise-identifier (ENTIDN002) inherited from Table 700, and program-name (PROGNM691)
inherited from Table 700 are concatenated and assume the role program-higher-level-configuration-
control-board-text (TOPCCB700). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

CCBNAM700 program-configuration-control-board-name 0151 K
ENTIDN002 enterprise-identifier 0052 FK
PROGNM691 program-name 0059 FK

DIVADD942 enterprise-office-address-text 0081 FK

PERNAM943 human-name 0069 FK
TOPCCB700 program-higher-level-configuration-control-board-text 0089 FK, O
CCBTYP700 program-configuration-control-board-type-code 0173 M

B-274
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.19.12. Table 701, Project identification by enterprise (ENTERPRISE-PROGRAM). This table identifies the
different programs (projects or systems) for which a particular enterprise has an interest in the requirements and/or
design.

Code Data Element Title DED Key

ENTIDN002 enterprise-identifier 0052 FK
PROGNM691 program-name 0059 FK

B.5.19.13. Table 702, CCB Membership (CCB-MEMBER). This table identifies the members of a specific
CCB.

Code Data Element Title DED Key

CCBNAM700 program-configuration-control-board-name 0151 FK
DIVADD942 enterprise-office-address-text 0081 FK
ENTIDN002 enterprise-identifier 0052 FK
PERNAM943 human-name 0069 FK
PROGNM691 program-name 0059 FK

RESPON702 human-responsibility-description-text 0154

B.5.19.14. Table 703, CCB area of responsibility (CCB-CI). This table identifies the Configuration Item(s) for
which the CCB has cognizance. Note that the CCB cognizance may be as the current document change authority
(CDCA), or as an application activity (AA).

Code Data Element Title DED Key

CCBNAM700 program-configuration-control-board-name 0151 FK
CIIDEN695 configuration-item-product-identifier 0111 FK
ENTIDN002 enterprise-identifier 0052 FK
PROGNM691 program-name 0059 FK

B.5.19.15. Table 704, Results of CCB (CCB-DIRECTIVE). This identifies the results of the CCB
review/disposition of each document brought to the CCB.

a. The value of document-type-code (DOCTYP010) must be either 'ECP' or 'RFD'.

Code Data Element Title DED Key

CCBNAM700 program-configuration-control-board-name 0151 FK
DOCNUM020 document-alphanumeric-identifier 0003 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
ENTIDN002 enterprise-identifier 0052 FK

B-275
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

PROGNM691 program-name 0059 FK

SRCCAG022 document-source-enterprise-defense-logistics--assigned- 0001 FK
identification-code

CCBDAT704 program-configuration-control-board-decision-date 0082 M

CCBMIN704 program-configuration-control-board-discussion-text 0168
CCBSTA704 document-change-process-program-configuration-control- 0021 M
board-chairman-disposition-status-code

B.5.19.16. Table 705, CCB Disposition of ECPs (CCB-ECP). This table is the subset of CCB Directives
(subtype of Table 704) which pertain to the disposition of ECPs. Due to parallel categorization, this table is a de
facto child of Table 251.

a. Because this table is a de facto child of Table 251, document-source-enterprise-defense-logistics--

assigned-identification-code (SRCCAG022) inherited from Table 704 is really a engineering-change-
proposal-document-source-enterprise-defense-logistics--assigned-identification-code (ECPCAG250)
existing in Table 251. Therefore, SRCCAG022 assumes the identity ECPCAG250.

b. Because this table is a de facto child of Table 251, document-alphanumeric-identifier (DOCNUM020)

inherited from Table 704 is really a engineering-change-proposal-document-alphanumeric-identifier
(ECPNUM250) existing in Table 251. Therefore, DOCNUM020 assumes the identity ECPNUM250.

c. Because this table is a de facto child of Table 251, document-generic-revision-identifier (DOCREV011)

inherited from Table 704 is really a engineering-change-proposal-document-alphanumeric-revision-
identifier (ECPREV251) existing in Table 251. Therefore, DOCREV011 assumes the identity
ECPREV251.

d. Because this table is a de facto child of Table 251, document-type-code (DOCTYP010) inherited from
Table 704 is really a engineering-change-proposal-document-type-code (ECPTYP250) existing in Table
251. Therefore, DOCTYP010 assumes the identity ECPTYP250.

Code Data Element Title DED Key

CCBNAM700 program-configuration-control-board-name 0151 FK
ECPCAG250 engineering-change-proposal-document-source-enterprise- 0001 FK
defense-logistics--assigned-identification-code
ECPNUM250 engineering-change-proposal-document-alphanumeric- 0003 FK
identifier
ECPREV251 engineering-change-proposal-document-alphanumeric- 0009 FK
revision-identifier
ECPTYP250 engineering-change-proposal-document-type-code 0004 FK
ENTIDN002 enterprise-identifier 0052 FK
PROGNM691 program-name 0059 FK

B.5.19.17. Table 706, CCB Disposition of RFDs (CCB-RFD). This table is the subset of CCB Directives
(subtype of Table 704) which pertain to the disposition of RFDs. Due to parallel categorization, this table is a de
facto child of Table 351.

B-276
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Because this table is a de facto child of Table 351, document-source-enterprise-defense-logistics--

assigned-identification-code (SRCCAG022) inherited from Table 704 is really a deviation-request-
document-source-enterprise-defense-logistics--assigned-identification-code (RFDCAG350) existing in
Table 351. Therefore, SRCCAG022 assumes the identity RFDCAG350.

b. Because this table is a de facto child of Table 351, document-alphanumeric-identifier (DOCNUM020)

inherited from Table 704 is really a deviation-request-document-alphanumeric-identifier (RFDNUM350)
existing in Table 351. Therefore, DOCNUM020 assumes the identity RFDNUM350.

c. Because this table is a de facto child of Table 351, document-generic-revision-identifier (DOCREV011)

inherited from Table 704 is really a deviation-request-document-alphanumeric-revision-identifier
(RFDREV351) existing in Table 351. Therefore, DOCREV011 assumes the identity RFDREV351.

d. Because this table is a de facto child of Table 351, document-type-code (DOCTYP010) inherited from
Table 704 is really a deviation-request-document-type-code (RFDTYP350) existing in Table 351.
Therefore, DOCTYP010 assumes the identity RFDTYP350.

Code Data Element Title DED Key

CCBNAM700 program-configuration-control-board-name 0151 FK
ENTIDN002 enterprise-identifier 0052 FK
PROGNM691 program-name 0059 FK
RFDCAG350 deviation-request-document-source-enterprise-defense- 0001 FK
logistics--assigned-identification-code
RFDNUM350 deviation-request-document-alphanumeric-identifier 0003 FK
RFDREV351 deviation-request-document-alphanumeric-revision-identifier 0009 FK
RFDTYP350 deviation-request-document-type-code 0004 FK

B.5.19.18. Tables 707 through 799. Reserved.

B-277
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.20. Document representations and release/approval cycles. Entity tables numbered in the range of 800
through 849 contain the identification of document representations, their release cycle and the associations with
document revisions. The relationships between the document representation entity tables are depicted in Figures
21REP1 through 21REP3.

B.5.20.1. Table 800, Document representation definition (DOCREP). This table contains the unique
identification of each representation of a document.

Code Data Element Title DED Key

REPIDN800 document-representation-identifier 0207 K
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.20.2. Table 801, Document representation revision definition (DOCREPREV). This table contains the
unique identification of each revision to each representation of a document revision.

a. Attribute entity-identifier (ENTYID000) inherited from Table 000 assumes the role document-
representation-revision-originator-entity-identifier (REPORG801).

Code Data Element Title DED Key

REPREV801 document-representation-revision-identifier 0208 K
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
REPIDN800 document-representation-identifier 0207 FK
SRCIDN010 document-source-entity-identifier 0033 FK

DOCREV011 document-generic-revision-identifier 0243 FK

REPORG801 document-representation-revision-originator-entity-identifier 0033 FK
REPDAT801 document-representation-creation-date 0082 M

B.5.20.3. Table 802, Correlation of document representation revisions and their associated files (REPREV-
FILE). This table correlates a specific revision of a document representation with the file(s) with which it is
composed.

B-278
DOCREP / 800
GENERIC-DOCUMENT / 010 (from 1GEN2) ENTERPRISE / 002 (from 1GEN1)
is represented by document-source-entity-identifier (FK)
document-source-entity-identifier enterprise-identifier
document-identifier (FK)
document-identifier
document-type-code (FK)
document-type-code Assertion: The relationship
document-representation-identifier
between Tables 010 and 800
and between Tables 011 and 801
can be 1:0 only if either the status
of the document revision in Table
has iterations 850 (see Figure 22REV1) is 'INWK' has iterations may be originator of
or if the value of document-type-code
is either 'ECP' or 'RFD'.
P
P FILE / 900 (from 23FILE1)
GENERIC-DOCREV / 011 (from 1GEN2)
file-originator
document-source-entity-identifier (FK) DOCREPREV / 801
file-originator-office-address
document-identifier (FK) document-source-entity-identifier (FK) file-identifier
document-type-code (FK) has proposed document-identifier (FK) file-creation-date
document-generic-revision representations document-type-code (FK) file-creation-time
document-representation-identifier (FK)
document-representation-revision
document-generic-revision (FK)
STAFF / 943 (from 25ADD1) document-representation-revision-originator.enterprise-identifier (FK)
person-name

B-279
may be part of
office-address may be composed of
APPENDIX B
MIL-STD-2549

has

may disposition
P REPREV-FILE / 802 (see 21REP3, 22REV2, 22REV4, 26CON5)
document-source-entity-identifier (FK)
REPREVSTAT / 803 (see 21REP2) document-identifier (FK)
document-source-entity-identifier (FK) document-type-code (FK)
document-identifier (FK) document-representation-identifier (FK)
document-type-code (FK) document-representation-revision (FK)
document-representation-identifier (FK) file-originator (FK)
document-representation-revision (FK) file-originator-office-address (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-representation-release-status-code file-identifier (FK)

file-creation-date (FK)
document-representation-release-status-date file-creation-time (FK)
document-representation-release-dispositioner-name.person-name (FK)
office-address (FK)

FIGURE 21REP1
DOCUMENT REPRESENTATION RELEASE STATUS (Part 1 of 2)
REPREVSTAT / 803 (from 21REP1)
document-source-entity-identifier
document-identifier
document-type-code
document-representation-identifier
document-representation-revision
document-representation-release-status-code
DOCREV-DISAPP / 855 (from 22REV1)
document-source-entity-identifier
document-identifier
document-type-code
document-representation-release-status-code document-generic-revision
document-revision-approval-status-code
INWK document-revision-approval-status-date
REVW DOCREV-AWC / 853 (from 22REV1)
document-source-entity-identifier
REPREV-INWORK / 804 REPREV-INREVIEW / 805 (see 21REP3) document-identifier
document-source-entity-identifier (FK) document-type-code
document-source-entity-identifier (FK)
document-identifier (FK) document-generic-revision
document-identifier (FK)
document-type-code (FK) document-revision-approval-status-code
document-type-code (FK)
document-representation-identifier (FK) document-revision-approval-status-date
document-representation-identifier (FK)
document-representation-revision (FK) document-representation-revision (FK)
document-representation-release-status-code (FK) document-representation-release-status-code (FK)

results in
RLSE REJ
DOCREV-SUBMIT / 852 (from 22REV1) DOCREV-APP / 854 (from 22REV1)

B-280
document-source-entity-identifier document-source-entity-identifier (AK1) is the conditional
document-identifier document-identifier (AK1) approval of
APPENDIX B

document-type-code document-type-code (AK1)

MIL-STD-2549

is disapproval of
document-generic-revision document-generic-revision (AK1)
document-revision-submit-code Assertion: The relationships results in
document-revision-approval-status-code
document-revision-submit-date document-revision-approval-status-date of Table 853 to 806, Table Assertion: The relationship
854 to 806, and Table 855 to of Table 853 to 807, and
806 are mutually exclusive. Table 855 to 807 are
mutually exclusive.

1 1
Z Z
REPREV-RELEASE / 806 (see 22REV2, 22REV3, 22REV4, 26CON3)
REPREV-REJECT / 807
is approval document-source-entity-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-source-entity-identifier (FK)
date of document-identifier (FK)
document-identifier (FK)
document-type-code (FK)
document-type-code (FK)
1 document-representation-identifier (FK)
document-representation-identifier (FK)
is the submission of document-representation-revision (FK)
document-representation-revision (FK)
document-representation-release-status-code (FK)
1 document-representation-release-status-code (FK)
FIGURE 21REP2 document-generic-revision (FK)
DOCUMENT REPRESENTATION RELEASE STATUS document-generic-revision (FK)
document-revision-submit-code (FK)
(Part 2 of 2) document-revision-approval-status-code (FK)
document-revision-submit-date (FK)
document-revision-approval-status-date (FK)
document-revision-approval-status-code (FK)
document-revision-approval-status-date (FK)
REPREV-INREVIEW / 805 (from 21REP2) REPREV-FILE / 802 (from 21REP1)
document-source-entity-identifier document-source-entity-identifier
document-identifier document-identifier
document-type-code STAFF / 943 (from 25ADD1) document-type-code FILE / 900 (from 23FILE1)
document-representation-identifier document-representation-identifier file-originator
person-name
document-representation-revision document-representation-revision file-originator-office-address
office-address
document-representation-release-status-code file-originator file-identifier
file-originator-office-address file-creation-date
file-identifier file-creation-time
file-creation-date
may be reviewed by file-creation-time
may review

OO-REVIEWER / 811 may be commented on by

document-source-entity-identifier (FK) may contain
document-identifier (FK) comments on
document-type-code (FK)
document-representation-identifier (FK) may record
document-representation-revision (FK) comments on
file-reviewer-person-name.person-name (FK)
file-reviewer-office-address.office-address (FK)

B-281
document-representation-release-status-code (FK) OO-REDLINE / 812
APPENDIX B

technical-disposition-recommendation
MIL-STD-2549

document-source-entity-identifier (FK)
document-identifier (FK)
document-type-code (FK)
document-representation-identifier (FK)
document-representation-revision (FK)
document-representation-file-originator.file-originator (FK)
document-representation-file-originator-office-address.file-originator-office-address (FK)
document-representation-file-identifier.file-identifier (FK)
document-representation-file-creation-date.file-creation-date (FK)
document-representation-file-creation-time.file-creation-time (FK)
comment-file-originator.(file-reviewer-person-name,file-originator) (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

comment-file-originator-office-address.(file-reviewer-office-address,file-originator-office-address) (FK)
comment-file-identifier.file-identifier (FK)
comment-file-creation-date.file-creation-date (FK)
comment-file-creation-time.file-creation-time (FK)

FIGURE 21REP3
DOCUMENT REPRESENTATION ORIGINATING ORGANIZATION REVIEW
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILDAT900 electronic-document-file-creation-date 0082 FK
FILIDN900 electronic-document-file-identifier 0206 FK
FILORG900 file-originator-human-name 0069 FK
FILTIM900 electronic-document-file-creation-time 0160 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.20.4. Table 803, Release status of a document representation revision (REPREVSTAT). This table
contains the release status of the document representation revision by the creator (current change control activity)
of the document representation.

a. If the value of document-representation-release-process-disposition-status-code (REPSTA803) is any value

other than in-work ('INWK'), then the value of document-representation-release-process-dispositioner-
human-name (DISPNM803) must be nonblank.

b. If the value of document-representation-release-process-disposition-status-code (REPSTA803) is release

('RLSE') or reject ('REJ'), then the value of document-representation-release-process-next-status-suspense-
date (NSTATD803) must be blank.

c. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role document-
representation-release-process-dispositioner-human-name (DISPNM803).

Code Data Element Title DED Key

REPSTA803 document-representation-release-process-disposition-status- 0021 K
code
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
SRCIDN010 document-source-entity-identifier 0033 FK

DISPNM803 document-representation-release-process-dispositioner- 0069 FK

human-name
DIVADD942 enterprise-office-address-text 0081 FK
NSTATD803 document-representation-release-process-next-status- 0082
suspense-date
RELDAT803 document-representation-release-process-disposition-status- 0082 M
date

B-282
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.20.5. Table 804, Document representations with a release status of 'in-work' (REPREV-INWORK). This
table is a subtype of Table REPREVSTAT/803. It contains the subset of the contents of Table 803 consisting only
of those document representations which are in the release status of in-work ('INWK') by the originator of the
document representation. This is the default status for newly created document representations.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
REPSTA803 document-representation-release-process-disposition-status- 0021 FK
code
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.20.6. Table 805, Document representation(s) with a release status of 'in-review' (REPREV-INREVIEW).
This table is a subtype of Table REPREVSTAT/803. It contains the subset of the contents of Table 803 consisting
only of those document representations which are in the release status of in-review ('REVW') by the originator of
the document representation.

Code Data Element Title DED Key

B.5.20.7. Table 806, Document representation(s) with a release status of 'release' (REPREV-RELEASE). This
table is a subtype of Table REPREVSTAT/803, It contains the subset of the contents of Table 803 consisting only
of those document representations which are in the release status of released ('RLSE')' by the originator of the
document representation.

Code Data Element Title DED Key

DOCREV011 document-generic-revision-identifier 0243 FK, O

B-283
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK

STADAT850 document-revision-approval-process-disposition-status-date 0082 FK
SUBDAT852 document-revision-approval-process-submission-date 0082 FK, O
SUBSTA852 document-revision-approval-process-submission-disposition- 0021 FK, O
status-code
RELLIM806 document-representation-release-limitations-text 0217
RELTYP806 document-representation-release-type-code 0216 M

B.5.20.8. Table 807, Document representation(s) with a release status of 'reject' (REPREV-REJECT). This
table is a subtype of Table REPREVSTAT/803, It contains the subset of the contents of Table 803 consisting only
of those document representations which are in the release status of reject ('REJ') by the originator of the document
representation.

Code Data Element Title DED Key

DOCREV011 document-generic-revision-identifier 0243 FK, O

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK, O

B.5.20.9. Tables 808 through 810. Reserved.

B.5.20.10. Table 811, Document representation originating activity reviewers (REPREV-OOREVIEWER). This
table contains the names of the originating organization reviewer(s) who have been provided access to the
document representation revision for review as part of the release process.

a. The values of disposition-process-technical-recommendation-date (TECHDT811) and document-

representation-release-process-technical-recommended-disposition-status-code (TECHCD811) must both
be blank, or both be non-blank.

b. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role
enterprise-file-review-office-address-text (FREVAD811).

c. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role file-reviewer-human-
name (FREVNM811).

B-284
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
FREVAD811 enterprise-file-review-office-address-text 0081 FK
FREVNM811 file-reviewer-human-name 0069 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
SRCIDN010 document-source-entity-identifier 0033 FK

REPSTA803 document-representation-release-process-disposition-status- 0021 FK

code
TECHCD811 document-representation-release-process-technical- 0021
recommended-disposition-status-code
TECHDT811 disposition-process-technical-recommendation-completion- 0082
date

B.5.20.11. Table 812, Originating organization reviewer comments on a document representation (REPREV-
OOREDLINE). This table contains the identification of the file(s) containing comments or redline annotations to
the document representation revision being reviewed as part of the release process by the originating organization.
These files are cross-referenced to, but separate and distinct from, the original files being reviewed.

a. For each instance in this table, the same value of document-revision-identifier (DOCREV011) must be in
all parent instances; that is, the same instance must be reached through the inheritance path Table 812 ->
Table 802 -> Table 801, and the path Table 812 -> Table 811 -> Table 805 -> Table 803 -> Table 801.

b. The value of enterprise-file-review-office-address-text (FREVAD811) inherited from Table 811 and the
value of enterprise-file-origination-office-address-text (FILADD900) inherited from Table 900 must be
the same. Therefore, they merge into the identity enterprise-comment-file-origination-office-address-text
(CFILAD812).

c. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-date (CFILDT812).

d. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 900 assumes the role
electronic-document-comment-file-identifier (CFILID812).

e. The value of file-reviewer-human-name (FREVNM811) inherited from Table 811 and the value of file-
originator-human-name (FILORG900) inherited from Table 900 must be the same. Therefore, they merge
into the identity comment-file-originator-human-name (CFILOR812).

f. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-date (CFILTM812).

g. Attribute enterprise-file-origination-office-address-text (FILADD900) inherited from Table 802 assumes

the role enterprise-document-file-origination-office-address-text (RFILAD812).

B-285
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

h. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-date (RFILDT812).

i. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 802 assumes the role
electronic-document-representation-file-identifier (RFILID812).

j. Attribute file-originator-human-name (FILORG900) inherited from Table 802 assumes the role
document-file-originator-human-name (RFILOR812).

k. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-date (RFILTM812).

Code Data Element Title DED Key

CFILAD812 enterprise-comment-file-origination-office-address-text 0081 FK
CFILOR812 comment-file-originator-human-name 0069 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
RFILAD812 enterprise-document-file-origination-office-address-text 0081 FK
RFILDT812 electronic-document-representation-file-creation-date 0082 FK
RFILID812 electronic-document-representation-file-identifier 0206 FK
RFILOR812 document-file-originator-human-name 0069 FK
RFILTM812 electronic-document-representation-file-creation-date 0082 FK
SRCIDN010 document-source-entity-identifier 0033 FK

CFILDT812 electronic-document-comment-file-creation-date 0082 FK

CFILID812 electronic-document-comment-file-identifier 0206 FK, O
CFILTM812 electronic-document-comment-file-creation-date 0082 FK

B.5.20.12. Tables 813 through 849. Reserved.

B-286
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.21. Document revisions and approval cycles. Entity tables numbered in the range of 850 through 899 contain
the approval cycle of generic document revisions, including the initial issue (the no-change revision). The
relationships between the document revision entity tables are depicted in Figures 22REV1 through 22REV4.
There are two major areas depicted in this series of tables.

a. Those tables in the range of 850 through 859 address the approval activities of the current document
change authority (CDCA) for the specific document. The CDCA must be specified in Table 010; it is the
organization or Configuration Control Board which has the sole authority to decide whether or not to
approve a change to the document and to direct the incorporation of the change into the document. The
CDCA is responsible for the informational content of the document; it owns the intellectual property
contained in the document. Each document has only one CDCA at any point in time, however, the CDCA
may be changed at any time by agreement of the current CDCA and the new CDCA. An example of this
would be the change in CDCA as a result of a PCA and consequent establishment of a tasking activity
baseline.7

b. Those tables in the range of 860 through 869 address the adoption activities of an application activity
(AA). An application activity is any enterprise which uses a document in a manner such that they have a
vested interested in the changes occurring to that document.8 For example, if an Army Missile Command
(MICOM) program office adopts the use of a Naval Aviation Command (NAVAIR) drawing by including
it in the MICOM program product baseline, MICOM is an application activity for the drawing. Each
document may have any number of AAs at any time. Although normally referred to as approval, the AA
can really only adopt (or reject) the document because, unlike the CDCA, the AA cannot direct that a
change be incorporated into the document; the document is not controlled by them. The AA can, and
should, review proposed changes before they are approved and make a recommendation to the CDCA;
however, the CDCA does not have to consider the AA recommendation. If the AA disagrees with a
decision made by the CDCA, the AA's only recourse is to cease using the document and to create a new
document which meets their needs.

c. Those tables in the series 870 through 899 are not currently used.

d. Because the relationship of the release of the document representation and the approval/adoption of the
document revision are so complex and closely entwined, IDEF3 process diagrams are included at the end
of this section. Figure B-1 is an explanation of the symbols used in the diagrams and Figures B-2 through
B-7 depict the most common scenarios.

B.5.21.1. Table 850, Document revision approval status (DOCREVSTAT). This table contains the document
revision approval status by the document-current-change-control-authority-entity-identifier (CCCENT010) as
shown in Table 010.

a. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role document-revision-
approval-process-dispositioner-human-name (PERNAM850).

7
The CDCA may be a tasking activity, performing activity, or both. The example is only an example and is not meant to
imply that the CDCA must change as the result of the establishment of a tasking activity PBL. It is very possible for the
Tasking Activity to be an Application Activity while the Performing Activity is the CDCA.

8
An AA can be a Tasking Activity, a Performing Activity, or both.

B-287
GENERIC -DOCREV / 011
document-source-entity-identifier
STAFF / 943 (from 25ADD1)
document-identifier
document-type-code person-name
document-generic-revision office-address

has may disposition

P
DOCREV-STAT / 850
document-source-entity-identifier (FK)
document-identifier (FK)
document-type-code (FK)
document-generic-revision (FK)
document-revision-approval-status-code
document-revision-approval-status-date
document-revision-dispositioner-name.person-name (FK)
office-address (FK)

document-revision-approval-status-code

INWK DISAPV

APV

B-288
SUBMIT AWC DOCREV-DISAPP / 855 (see 21REP2)
DOCREV-INWORK / 851
APPENDIX B
MIL-STD-2549

document-source-entity-identifier (FK)
document-source-entity-identifier (FK) DOCREV-AWC / 853 (see 21REP2) document-identifier (FK)
document-identifier (FK) document-type-code (FK)
document-type-code (FK) document-source-entity-identifier (FK)
document-identifier (FK) document-generic-revision (FK)
document-generic-revision (FK) document-revision-approval-status-code (FK)
document-revision-approval-status-code (FK) document-type-code (FK)
document-generic-revision (FK) document-revision-approval-status-date (FK)
document-revision-approval-status-date (FK)
document-revision-approval-status-code (FK)
document-revision-approval-status-date (FK)

DOCREV-APP / 854 (see 21REP2, 22REV3)

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

DOCREV-SUBMIT / 852 (see 21REP2, 22REV2)

document-source-entity-identifier (FK) (AK1)
document-source-entity-identifier (FK)
document-identifier (FK) (AK1)
document-identifier (FK)
document-type-code (FK) (AK1)
document-type-code (FK)
document-generic-revision (FK) (AK1)
document-generic-revision (FK)
document-revision-approval-status-code (FK)
document-revision-submit-code.document-revision-approval-status-code (FK)
document-revision-approval-status-date (FK)
document-revision-submit-date.document-revision-approval-status-date (FK)

FIGURE 22REV1
DOCUMENT REVISION CDCA APPROVAL STATUS
DOCREV-SUBMIT / 852 (from 22REV1) REPREV-RELEASE / 806 (from 21REP2) REPREV-FILE / 802 (from 21REP1)
document-source-entity-identifier document-source-entity-identifier document-source-entity-identifier
document-identifier document-identifier document-identifier
document-type-code document-type-code document-type-code
document-generic-revision document-representation-identifier document-representation-identifier
document-revision-submit-code document-representation-revision document-representation-revision
document-revision-submit-date document-representation-release-status-code file-originator
file-originator-office-address
file-identifier
file-creation-date
file-creation-time
STAFF / 943 (from 25ADD1)
person-name
office-address may be
commented
FILE / 900 (from 23FILE1)
on by
may be reviewed by may be reviewed by file-originator
may review file-originator-office-address
file-identifier
file-creation-date
DOCREV-REVIEWER / 857
may contain file-creation-time
document-source-entity-identifier (FK)

B-289
comments on
document-identifier (FK)
APPENDIX B

document-type-code (FK)
MIL-STD-2549

document-generic-revision (FK) DOCSUB-CDCAREDLINE / 858

document-revision-submit-code (FK) document-source-entity-identifier (FK)
document-revision-submit-date (FK) document-identifier (FK)
file-reviewer-name.person-name (FK) document-type-code (FK)
file-reviewer-office-address.office-address (FK) document-representation-identifier (FK)
technical-disposition-recommendation document-representation-revision (FK)
document-representation-file-originator.file-originator (FK)
document-representation-file-originator-office-address.file-originator-office-address (FK)
document-representation-file-identifier.file-identifier (FK)
may record document-representation-file-creation-date.file-creation-date (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

comments on document-representation-file-creation-time.file-creation-time (FK)

comment-file-originator.(file-reviewer-name,file-originator) (FK)
comment-file-originator-office-address.(file-reviewer-office-address,file-originator-office-address) (FK)
document-generic-revision (FK)
document-representation-release-status-code (FK)
FIGURE 22REV2 document-revision-submit-code (FK)
DOCUMENT REVISION CDCA REVIEW STATUS document-revision-submit-date (FK)
comment-file-identifier.file-identifier (FK)
comment-file-creation-date.file-creation-date (FK)
comment-file-creation-time.file-creation-time (FK)
REPREV-RELEASE / 806 (from 21REP2) AA / 033 (from 1GEN2)
document-source-entity-identifier application-activity-identifier
document-identifier document-source-entity-identifier GENERIC-DOCREV / 011 (from 1GEN2)
document-type-code document-identifier document-source-entity-identifier
document-representation-identifier document-type-code document-identifier
document-representation-revision document-type-code
document-representation-release-status-code document-generic-revision

may be submitted has

to for adoption may be used by

STAFF / 943 (from 25ADD1) P

person-name DOCREV-APP / 854 (from 22REV1)
office-address AA-DOCSTAT / 861 document-source-entity-identifier
application-activity-identifier (FK) document-identifier
document-source-entity-identifier (FK) document-type-code
document-identifier (FK) document-generic-revision
may disposition document-type-code (FK) document-revision-approval-status-code
document-generic-revision (FK) document-revision-approval-status-date
application-activity-approval-status-code
application-activity-approval-status-date
document-revision-dispositioner-name.person-name (FK)
office-address (FK)

B-290
document-representation-identifier (FK)
document-representation-revision (FK)
APPENDIX B

document-representation-release-status-code (FK)
MIL-STD-2549

may be adopted for use by

application-activity-approval-status-code

DISAPV
SUBMIT
PEND ADOPT
DOCREV-AADISAPP / 864
DOCREV-AASUBMIT / 862 (see 22REV4)
DOCREV-AAPEND / 865 DOCREV-AAADOPT / 863 application-activity-identifier (FK)
application-activity-identifier (FK) document-source-entity-identifier (FK)
document-source-entity-identifier (FK) application-activity-identifier (FK) application-activity-identifier (FK)
document-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-identifier (FK) document-source-entity-identifier (FK) document-source-entity-identifier (FK) (AK1)

document-identifier (FK) (AK1) document-type-code (FK)
document-type-code (FK) document-identifier (FK) document-generic-revision (FK)
document-generic-revision (FK) document-type-code (FK) document-type-code (FK) (AK1)
document-generic-revision (FK) (AK1) application-activity-approval-status-code (FK)
application-activity-approval-status-code (FK) document-generic-revision (FK) application-activity-approval-status-date (FK)
application-activity-approval-status-date (FK) application-activity-approval-status-code (FK) application-activity-approval-status-code (FK)
application-activity-approval-status-date (FK) application-activity-approval-status-date (FK)
document-revision-approval-status-code (FK)
document-revision-approval-status-date (FK)
FIGURE 22REV3 nor-implementation-authorization-code
DOCUMENT REVISION AA APPROVAL STATUS
DOCREV-AASUBMIT / 862 (from 22REV3) REPREV-RELEASE / 806 (from 21REP2) REPREV-FILE / 802 (from 21REP1)
application-activity-identifier document-source-entity-identifier document-source-entity-identifier
document-source-entity-identifier document-identifier document-identifier
document-identifier document-type-code document-type-code
document-type-code document-representation-identifier document-representation-identifier
document-revision FILE / 900 (from 23FILE1)
document-representation-revision document-representation-revision
application-activity-approval-status-code document-representation-release-status-code file-originator file-originator
application-activity-approval-status-date file-originator-office-address file-originator-office-address
file-identifier file-identifier
file-creation-date file-creation-date
file-creation-time file-creation-time
STAFF / 943 (from 25ADD1)
person-name
office-address
may be reviewed by
may be reviewed by
may be
commented may contain comments on
may review on by

AA-REVIEWER / 866
application-activity-identifier (FK)
document-source-entity-identifier (FK)
document-identifier (FK) AA-REDLINE / 867

B-291
document-type-code (FK) document-source-entity-identifier (FK)
document-revision (FK) document-identifier (FK)
APPENDIX B
MIL-STD-2549

application-activity-approval-status-code (FK) document-type-code (FK)

application-activity-approval-status-date (FK) document-representation-identifier (FK)
file-reviewer-person-name.person-name (FK) document-representation-revision (FK)
file-reviewer-office-address.office-address (FK) document-representation-file-originator.file-originator (FK)
document-representation-file-originator-office-address.file-originator-office-address (FK)
technical-disposition-recommendation
document-representation-file-identifier.file-identifier (FK)
document-representation-file-creation-date.file-creation-date (FK)
document-representation-file-creation-time.file-creation-time (FK)
may record
comment-file-originator.(file-reviewer-person-name,file-originator) (FK)
comments on
comment-file-originator-office-address.(file-originator-office-address,file-reviewer-office-address) (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

application-activity-identifier (FK)
document-revision (FK)
document-representation-release-status-code (FK)
application-activity-approval-status-code (FK)
application-activity-approval-status-date (FK)
FIGURE 22REV4 comment-file-identifier.file-identifier (FK)
DOCUMENT REVISION AA REVIEW STATUS comment-file-creation-date.file-creation-date (FK)
comment-file-creation-time.file-creation-time (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

REVSTA850 document-revision-approval-process-disposition-status-code 0021 K
STADAT850 document-revision-approval-process-disposition-status-date 0082 K
DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

DIVADD942 enterprise-office-address-text 0081 FK

PERNAM850 document-revision-approval-process-dispositioner-human- 0069 FK, O
name
NXSTDT850 document-revision-approval-process-next-status-suspense- 0082 M
date

B.5.21.2. Table 851, Document revisions in the approval process with a status of 'In-Work' (DOCREV-
INWORK). This table is a subtype of DOCREVSTAT/850. It contains the subset of the contents of Table 850
consisting of those document revisions which have reached the status of in-work ('INWK'). This is the default
status for new document revisions.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
SRCIDN010 document-source-entity-identifier 0033 FK
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.21.3. Table 852, Document revisions in the approval process with a status of 'SUBMIT' (DOCREV-
SUBMIT). This table is a subtype of Table DOCREVSTAT/850. It contains the subset of the contents of Table
850 consisting of those document revisions which have reached the status of submit ('SUBMIT'), indicating that
one representation of the document revision has been submitted to the current document change authority (CDCA)
for consideration for approval.

a. Attribute document-revision-approval-process-disposition-status-date (STADAT850) inherited from Table

850 assumes the role document-revision-approval-process-submission-date (SUBDAT852).

b. Attribute document-revision-approval-process-disposition-status-code (REVSTA850) inherited from Table

850 assumes the role document-revision-approval-process-submission-disposition-status-code
(SUBSTA852).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK

B-292
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DOCTYP010 document-type-code 0004 FK

SRCIDN010 document-source-entity-identifier 0033 FK
SUBDAT852 document-revision-approval-process-submission-date 0082 FK
SUBSTA852 document-revision-approval-process-submission-disposition- 0021 FK
status-code

B.5.21.4. Table 853, Document revisions with an approval process status of 'AWC' (DOCREV-AWC). This
table is a subtype of Table DOCREVSTAT/850 which contains the subset of the contents of Table 850 consisting
of those document revisions which have reached the status of approved with comment ('AWC') by the CDCA as
shown in Table 010. (Note: this is synonymous with 'conditional approval'.)

Code Data Element Title DED Key

B.5.21.5. Table 854, Document revisions with the approval process status of 'APPROVED' (DOCREV-APP).
This table is a subtype of Table DOCREVSTAT/850. It contains a subset of the contents of Table 850 consisting of
those document revisions which have reached the status of approved ('APV') by the CDCA as shown in Table 010.
Therefore, the value of document-revision-approval-process-disposition-status-code (REVSTA850) must be 'APV'.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK, AK1
DOCREV011 document-generic-revision-identifier 0243 FK, AK1
DOCTYP010 document-type-code 0004 FK, AK1
REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK
SRCIDN010 document-source-entity-identifier 0033 FK, AK1
STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

B.5.21.6. Table 855, Document revisions with the approval process status of 'DISAPPROVED' (DOCREV-
DISAPP). This table is a subtype of Table DOCREVSTAT/850. It contains the subset of the contents of Table 850
consisting of those document revisions which have reached the status of disapproved ('DISAPV') by the CDCA as
shown in Table 010.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK

B-293
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK

STADAT850 document-revision-approval-process-disposition-status-date 0082 FK

SRCIDN010 document-source-entity-identifier 0033 FK

B.5.21.7. Table 856. Reserved.

B.5.21.8. Table 857, Reviewers in the document revision approval process (DOCREV-REVIEWER). This
table contains the names of the CDCA reviewer(s) who have been provided access to the document representation
revision for review as part of the approval process.

a. The values of disposition-process-technical-recommendation-completion-date (TECHDT857) and

document-approval-process-technical-recommended-disposition-status-code (TECHCD857) must both be
blank, or both be nonblank.

b. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role
enterprise-file-review-office-address-text (FREVAD857).

c. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role file-reviewer-human-
name (FREVNM857).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
FREVAD857 enterprise-file-review-office-address-text 0081 FK
FREVNM857 file-reviewer-human-name 0069 FK
SRCIDN010 document-source-entity-identifier 0033 FK
SUBDAT852 document-revision-approval-process-submission-date 0082 FK
SUBSTA852 document-revision-approval-process-submission-disposition- 0021 FK
status-code

TECHCD857 document-approval-process-technical-recommended- 0021

disposition-status-code
TECHDT857 disposition-process-technical-recommendation-completion- 0082
date

B.5.21.9. Table 858, Current change control authority reviewer comments on submitted documents/document
revisions (DOCSUB-CDCAREDLINE). This table contains the identification of the file(s) containing comments
or redline annotations to the document representation revision being reviewed as part of the document revision
approval process by the document-current-change-control-authority-entity-identifier (CCCENT010) as shown in
Table 010. These files are cross-referenced to, but separate and distinct from, the original files being reviewed.

a. The same value of document-revision-identifier must be in all inheritance paths; that is, the same value of
document-revision-identifier must be reached through the path Table 802 to Table 801, and the path Table
858 to Table 857 to Table 856.

B-294
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. The file reviewer is the originator of the comment file.

c. The value of enterprise-file-review-office-address-text (FREVAD857) inherited from Table 857 and the
value of enterprise-file-origination-office-address-text (FILADD900) inherited from Table 900 must be
the same. Therefore, they merge into the identity enterprise-comment-file-origination-office-address-text
(CFILAD858).

d. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-date (CFILDT858).

e. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 900 assumes the role
electronic-document-comment-file-identifier (CFILID858).

f. The value of file-reviewer-human-name (FREVNM857) inherited from Table 857 and the value of file-
originator-human-name (FILORG900) inherited from Table 900 must be the same. Therefore, they merge
into the identity comment-file-originator-human-name (CFILOR858).

g. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-date (CFILTM858).

h. Attribute enterprise-file-origination-office-address-text (FILADD900) inherited from Table 802 assumes

the role enterprise-document-file-origination-office-address-text (RFILAD858).

i. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-date (RFILDT858).

j. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 802 assumes the role
electronic-document-representation-file-identifier (RFILID858).

k. Attribute file-originator-human-name (FILORG900) inherited from Table 802 assumes the role
document-file-originator-human-name (RFILOR858).

l. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-date (RFILTM858).

Code Data Element Title DED Key

CFILAD858 enterprise-comment-file-origination-office-address-text 0081 FK
CFILOR858 comment-file-originator-human-name 0069 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
RFILAD858 enterprise-document-file-origination-office-address-text 0081 FK
RFILDT858 electronic-document-representation-file-creation-date 0082 FK
RFILID858 electronic-document-representation-file-identifier 0206 FK
RFILOR858 document-file-originator-human-name 0069 FK
RFILTM858 electronic-document-representation-file-creation-date 0082 FK

B-295
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SRCIDN010 document-source-entity-identifier 0033 FK

CFILDT858 electronic-document-comment-file-creation-date 0082 FK

CFILID858 electronic-document-comment-file-identifier 0206 FK
CFILTM858 electronic-document-comment-file-creation-date 0082 FK
DOCREV011 document-generic-revision-identifier 0243 FK
REPSTA803 document-representation-release-process-disposition-status- 0021 FK
code
SUBDAT852 document-revision-approval-process-submission-date 0082 FK
SUBSTA852 document-revision-approval-process-submission-disposition- 0021 FK
status-code

B.5.21.10. Tables 859 and 860. Reserved.

B.5.21.11. Table 861, Application activity document revision approval process status (DOCREV-AASTAT).
This table contains the document revision approval status by the application activity.

a. If the value of document-revision-application-activity-approval-process-disposition-status-code

(AREVST861) is adopted ('ADOPT') or disapproved ('DISAPV'), then the document-revision-approval-
process-next-status-suspense-date (NSTATD856) must be blank.

b. The values of human-name (PERNAM039) and enterprise-division-address-text (DIVADD038) inherited

from Table 039 identify the person who puts the document revision in the status indicated in document-
revision-application-activity-approval-process-disposition-action-status-code (AREVST861).

Code Data Element Title DED Key

AREVDT861 document-revision-application-activity-approval-process- 0082 K
disposition-status-date
AREVST861 document-revision-application-activity-approval-process- 0021 K
disposition-status-code
APPACT033 application-activity-enterprise-division-identifier 0228 FK
DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

DIVADD942 enterprise-office-address-text 0081 FK

PERNAM943 human-name 0069 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
REPSTA803 document-representation-release-process-disposition-status- 0021 FK
code
NSTATD861 document-revision-approval-process-next-status-suspense- 0082
date

B-296
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.21.12. Table 862, Document revisions with an application activity approval process status of 'SUBMIT'
(DOCREV-AASUBMIT). This table is a subtype of Table DOCREV-AASTAT/861 which contains the subset of
the contents of Table 861 consisting of those document revisions which have reached the status of submit
('SUBMIT'), indicating that one representation of the document revision has been submitted to the document
application activity for consideration for adoption.

Code Data Element Title DED Key

APPACT033 application-activity-enterprise-division-identifier 0228 FK
AREVDT861 document-revision-application-activity-approval-process- 0082 FK
disposition-status-date
AREVST861 document-revision-application-activity-approval-process- 0021 FK
disposition-status-code
DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK

B.5.21.13. Table 863, Document revisions with an application activity approval process status of 'ADOPT'
(DOCREV-AAAPP). This table is a subtype of Table DOCREV-AASTAT/861. It contains the subset of the
contents of Table 861 consisting of those document revisions which have reached the status of adopted ('ADOPT')
by the document application activity.

a. The revision-notice-document-implementation-authorization-code (IMPCOD863) must be blank unless

the value of document-type-code (DOCTYP010) is 'NOR', in which case, the value must be nonblank.
This field indicates the decision by the Application Activity in its role as a tasking activity as to whether
or not its performing activities may use the NOR prior to incorporation of the NOR into the document (see
also, Table 309).

Code Data Element Title DED Key

APPACT033 application-activity-enterprise-division-identifier 0228 FK
AREVDT861 document-revision-application-activity-approval-process- 0082 FK
disposition-status-date
AREVST861 document-revision-application-activity-approval-process- 0021 FK
disposition-status-code
DOCIDN010 document-identifier 0122 FK, AK1
DOCREV011 document-generic-revision-identifier 0243 FK, AK1
DOCTYP010 document-type-code 0004 FK, AK1
SRCIDN010 document-source-entity-identifier 0033 FK, AK1

REVSTA850 document-revision-approval-process-disposition-status-code 0021 FK

STADAT850 document-revision-approval-process-disposition-status-date 0082 FK
IMPCOD863 revision-notice-document-implementation-authorization-code 0176

B.5.21.14. Table 864, Document revisions with an application activity approval process status of
'DISAPPROVED' (DOCREV-AADISAPP). This table is a subtype of Table DOCREV-AASTAT/861. It contains

B-297
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

the subset of the contents of Table 861 consisting of those document revisions which have reached the status of
disapproved ('DISAPV') by the document application activity.

Code Data Element Title DED Key

B.5.21.15. Table 865, Document revisions with an application activity approval process status of 'PENDING'
(DOCREV-AAPEND). This table is a subtype of Table DOCREV-AASTAT/861. It contains the subset of the
contents of Table 861 consisting of those document revisions which have reached the status of pending ('PEND') by
the document application activity. This status means that the application activity has completed its review of the
document, made a recommendation to the CDCA, and is awaiting the decision of the CDCA as to the disposition
of the proposed change.

Code Data Element Title DED Key

B.5.21.16. Table 866, Reviewers of document revisions in the application activity approval process
(AADOCSUB-AAREVIEWER). This table contains the names of the document application activity reviewer(s)
who have been provided access to the document representation revision for review as part of the application
activity approval process.

a. The values of disposition-process-technical-recommendation-completion-date (TECHDT866) and

document-approval-process-technical-recommended-disposition-status-code (TECHCD866) must both be
blank, or both be non-blank.

b. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role
enterprise-file-review-office-address-text (FREVAD866).

B-298
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role file-reviewer-human-
name (FREVNM866).

Code Data Element Title DED Key

APPACT033 application-activity-enterprise-division-identifier 0228 FK
AREVDT861 document-revision-application-activity-approval-process- 0082 FK
disposition-status-date
AREVST861 document-revision-application-activity-approval-process- 0021 FK
disposition-status-code
DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
FREVAD866 enterprise-file-review-office-address-text 0081 FK
FREVNM866 file-reviewer-human-name 0069 FK
SRCIDN010 document-source-entity-identifier 0033 FK

TECHCD866 document-approval-process-technical-recommended- 0021

disposition-status-code
TECHDT866 disposition-process-technical-recommendation-completion- 0082
date

B.5.21.17. Table 867, Application activity reviewer comments on an application activity submitted document
revision (AADOCSUB-AAREDLINE). This table contains the identification of the file(s) containing comments or
redline annotations to the document representation revision being reviewed as part of the document revision
approval process by the document application activity. These files are cross-referenced to, but separate and distinct
from, the original files being reviewed.

a. The same value of document-revision-identifier must be in all inheritance paths; that is, the same value of
document-revision-identifier must be reached through the path Table 867 to Table 802 to Table 801, and
the path Table 867 to Table 866 to Table 865.

b. The file reviewer is the originator of the comment file.

c. The value of enterprise-file-review-office-address-text (FREVAD866) inherited from Table 866 and the
value of enterprise-file-origination-office-address-text (FILADD900) inherited from Table 900 must be
the same. Therefore, they merge into the identity enterprise-comment-file-origination-office-address-text
(CFILAD867).

d. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-date (CFILDT867).

e. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 900 assumes the role
electronic-document-comment-file-identifier (CFILID867).

f. The value of file-reviewer-human-name (FREVNM866) inherited from Table 866 and the value of file-
originator-human-name (FILORG900) inherited from Table 900 must be the same. Therefore, they merge
into the identity comment-file-originator-human-name (CFILOR867).

B-299
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

g. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-date (CFILTM867).

h. Attribute enterprise-file-origination-office-address-text (FILADD900) inherited from Table 802 assumes

the role enterprise-document-file-origination-office-address-text (RFILAD867).

i. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-date (RFILDT867).

j. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 802 assumes the role
electronic-document-representation-file-identifier (RFILID867).

k. Attribute file-originator-human-name (FILORG900) inherited from Table 802 assumes the role
document-file-originator-human-name (RFILOR867).

l. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-date (RFILTM867).

Code Data Element Title DED Key

CFILAD867 enterprise-comment-file-origination-office-address-text 0081 FK
CFILOR867 comment-file-originator-human-name 0069 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
RFILAD867 enterprise-document-file-origination-office-address-text 0081 FK
RFILDT867 electronic-document-representation-file-creation-date 0082 FK
RFILID867 electronic-document-representation-file-identifier 0206 FK
RFILOR867 document-file-originator-human-name 0069 FK
RFILTM867 electronic-document-representation-file-creation-date 0082 FK
SRCIDN010 document-source-entity-identifier 0033 FK

APPACT033 application-activity-enterprise-division-identifier 0228 FK

AREVDT861 document-revision-application-activity-approval-process- 0082 FK
disposition-status-date
AREVST861 document-revision-application-activity-approval-process- 0021 FK
disposition-status-code
CFILDT867 electronic-document-comment-file-creation-date 0082 FK
CFILID867 electronic-document-comment-file-identifier 0206 FK
CFILTM867 electronic-document-comment-file-creation-date 0082 FK
DOCREV011 document-generic-revision-identifier 0243 FK
REPSTA803 document-representation-release-process-disposition-status- 0021 FK
code

B.5.21.18. Tables 868 through 899. Reserved.

B-300
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Symbol Meaning/Use
______ ___________
UNIT OF BEHAVIOR
Defines a function, Responsible Activity
task description activity, action, Abbreviations:
process, operation, task,
or event.

id. no. resp.

AA: Application Activity
Responsible activity CDCA: Current Document
Change Authority
OO: Originating
REFERENCE Organization
reference
information or Contains supplementary PA: Performing Activity
optional information,
instructions instructions, cross TA: Tasking Activity
reference to steps
performed outside the
cross-ref/go-to process flow depicted,
notes, and Go-To’s.
Junction Symbols Fan-in Junction Meaning Fan-out Junction Meaning
________________ _______________________ ________________________

& ASYNCHRONOUS AND ASYNCHRONOUS AND

J# Process proceeds only All of the following

after all preceding tasks tasks will be initiated;
are completed; expecta- however, they may or may
tion is that they will not be initiated at the
not necessarily be com- same time.
pleted at the same time.

Junction Identifier

& SYNCHRONOUS AND SYNCHRONOUS AND

J# Process proceeds only All of the following

after all preceding tasks tasks will be initiated
are complete; expectation simultaneously.
is that they will be com-
pleted simultaneously.

O ASYNCHRONOUS OR ASYNCHRONOUS OR
J# Process proceeds after One or more of the fol-
any one of the preceding lowing tasks will be
tasks is completed. initiated; they may (or
may not) be initiated at
the same time.

O SYNCHRONOUS OR SYNCHRONOUS OR

J# Process proceeds after One or more of the fol-

any one of the preceding lowing tasks will be
tasks is completed (or initiated, and they will
after more than one are be initiated simultan-
completed simultaneous- eously.
ly.)

X EXCLUSIVE OR EXCLUSIVE OR
J# Process proceeds after Exactly one of the
one, and only one of the following tasks will be
preceding tasks is com- initiated.
pleted; expectation is
that only one of the
preceding tasks will ever
be completed.

EXAMPLE PROCESS:
Evaluate Cost
Proposal

3 TA

Prepare Receive Award contract

proposal Proposal & &

J1 J2
1 PA 2 TA 5 TA

Evaluate
Technical
Proposal
Fan-out junction Fan-in junction
4 TA

FIGURE B-1: IDEF3 Notation

B-301
the files which
comprise the
document are
created or
located
1-3 OO
a document number
a need is is assigned; the
determined for revision is ’-’;
a new document the status is & &
in-work
1J1 1J2
1-1 OO
1-2 CDCA a document
representation
identifier is
assigned with a
version of ’-’ and
a status of inwork

1-4 OO

the corrected files O

which comprise the
document are 1J3
created or located
the document
representation
version is put 1-9 OO
in the status &
of reject
1J5 &
1-8 OO

B-302
1J6
the document the next version
representation letter of the
APPENDIX B

revision is put reviewers may document represen-

MIL-STD-2549

in the status make comments X tation is assigned

of review the document the document with a document
1J4 representation revision is put revision of ’-’ and
1-6 OO 1-7 OO* version is put in the status of a status of inwork
in the status approved
* In CASE 1, OO=CDCA of release 1-10 OO

1-11 OO 1-12 CDCA

the files which

comprise the
document are
attached to the
document
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

representation

1-5 OO

FIGURE B-2: DOCUMENT RELEASE/APPROVAL CASE 1.

An enterprise creates a new document. (The enterprise is both the CDCA and the document representation originator. There are no
other activities involved.)
the files which
comprise the
document revision
are created or
located

2-3 OO

a need is the next document

determined for revision letter is the files which
a revision to assigned; the & a document comprise the document
the document status is in-work representation are attached to the
2J1 identifier is document
2-1 OO assigned with a & O representation at
2-2 CDCA version of ’-’; the the appropriate
status is inwork 2J4 2J5 version
2-6 OO
2-4 OO

O
X
the next version of 2J3
2J2 an existing
document
representation
identifier is
assigned; the
status is in-work the corrected files
which comprise the
2-5 OO document are
created or located

B-303
APPENDIX B

the document 2-10 OO

MIL-STD-2549

representation
version is put
in the status & &
of reject
the document 2J5 2J6
representation reviewers may make 2-9 OO the next version
version is put in comments letter of the
the status of X document represen-
review tation is assigned
2J4 with a document
the document revision of ’-’ and
2-7 OO 2-8 OO* representation the document a status of inwork
version is put revision is put
in the status in the status of 2-11 OO
* In CASE 1, OO=CDCA of release approved
2-12 OO 2-13 CDCA
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE B-3: DOCUMENT RELEASE/APPROVAL CASE 2.

An enterprise decides to revise an existing document for which they are the CDCA. (The enterprise is both the CDCA and the document representation originator. There are no other
activities involved.)
the most current
a need is an existing CDCA-approved
determined for document (under document revision
using an control of a CDCA is put in
existing other than the AA) Application
document is located Activity Adoption
status submit
3-1 AA
3-2 AA 3-3 AA

the document
revision is placed
in application
activity status
NOT-ADOPTED
application activity
reviewers may make
comments to any document 3-5 AA
representation which is

B-304
attached to the document
revision and which have a X
document representation
APPENDIX B
MIL-STD-2549

revision release status 3J1

of released
the document
3-4 AA revision is placed
in application
activity status
ADOPTED

3-6 AA

FIGURE B-4: DOCUMENT RELEASE/APPROVAL CASE 3.

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

An enterprise decides to use an existing document for which they are not the CDCA. (The enterprise is an Application
Activity. There are no other activities involved.)
The document
revision is put in Do CASE 6,
the Application starting with
Activity status of Step 6-1
SUBMIT
(Note
1) 4-3 AA**
4-2 OO*
** In this case, AA
* In this case, OO=CDCA may be PA or TA or
just a user with no
Do steps 1-1 contractual rela-
through 1-11 in tionship with the Do CASE 1, Steps 1-8
CASE 1 (or steps OO/CDCA. through 1-11
2-1 through 2-12 in O O The document
CASE 2) revision is put (or CASE 2, Steps 2-9
4J1 4J2 in the CDCA through 2-12)
status of
4-1 OO DISAPPROVED
4-8 OO
(Note 4-6 CDCA
2)
O &
4J5 4J6
The document revision
Review comments is put in the CDCA
from AA(s) status of
O X APPROVE-WITH-COMMENT The Application
Activity(s) are
4J3 4J4 notified of the
4-4 CDCA O status of the
4-5 CDCA document revision
4J7

B-305
4-7 CDCA
The document
APPENDIX B
MIL-STD-2549

Note 1: Use this path when coordination with a revision is put

TA, PA, or other AA is required or desired prior in the CDCA
to a final disposition by the CDCA. status of APPROVE

Note 2: Use this path when coordination with a 4-11 CDCA

TA, PA or other AA is not required and not desired
prior to the final disposition by the CDCA. Do CASE 6:
Application The contract is
Activity review & modified if
comment necessary.

4-9 AA** 4-10 TA

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

** In this case, AA
may be PA or TA or
just a user with no
contractual rela-
tionship with the
OO/CDCA.

FIGURE B-5: DOCUMENT RELEASE/APPROVAL CASE 4.

The CDCA of a document proposes a change to the document (or proposes a new document). There may be a contractual relationship with one or
more Application Activities. (The OO is the CDCA; it does not matter whether the CDCA is the TA or the PA in the contractual relationship.)
The document
revision is put in Do CASE 6,
the Application starting with
Activity status of Step 6-1
SUBMIT

(Note 5-5 AA**

1) 5-4 CDCA
** In this case, AA
may be PA or TA or
just a user with no
Do steps 1-1 The document revision contractual rela-
through 1-11 in is put in the Current Reviewers may tionship with the
CASE 1 (or steps Document Change make comments CDCA.
2-1 through 2-12 in O Authority status of O
CASE 2) SUBMIT
5J1 5J2
5-3 CDCA
5-1 OO 5-2 OO

Review comments
from AA(s)

5-6 CDCA

B-306
(Note 2)
Note 1: Use this path when coordination with a O
TA, PA, or other AA is required or desired prior
APPENDIX B
MIL-STD-2549

to a final disposition by the CDCA. 5J3

Note 2: Use this path when coordination with a
TA, PA or other AA is not required and not desired
prior to the final disposition by the CDCA.

FIGURE B-6: DOCUMENT RELEASE/APPROVAL CASE 5 (Part 1 of 2).

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

to from
1 An Application Activity (AA) proposes a change to the doucment (or proposes a new document). The Application Activity is the 2
originating organization (OO) and prepares the draft of the change. There may (or may not) be a contractual relationship with the
Current Document Change Authority (CDCA). there may (or may not) be additional AAs involved. (The OO is an AA; it is NOT the CDCA;
it does not matter whether the CDCA is the TA or the PA in the contractual relationship with the OO/AA.)
from to
1 2

The document
revision is put Do CASE 1, Steps 1-8
in the CDCA through 1-11
status of
DISAPPROVED (or CASE 2, Steps 2-9
through 2-12)
5-7 CDCA
5-13 OO

O &
The document revision (Note
is put in the CDCA 3) 5J6 5J7
status of
APPROVE-WITH-COMMENT X
Do CASE 1, Steps The document
X 5J5 (Note 1-8 through 1-11 revision is put
4) (or CASE 2, Steps in the CDCA
5J4 5-8 CDCA 1-9 through 1-12) status of
SUBMIT

5-9 OO 5-10 OO
The Application
Activity(s) are
notified of the

B-307
O status of the
document revision
APPENDIX B

5J9
MIL-STD-2549

The document 5-14 CDCA

revision/
representation is
reviewed for proper
incorporation of
comments
Note 3: Use this path when the
5-11 CDCA OO does not agree with the
comments from the CDCA. (Use of Do CASE 6, The contract is
this path requires a subsequent starting with modified if
full CDCA review cycle.) Step 6-11 necessary.
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

Note 4: Use this path when the 5-15 AA** 5-16 TA

OO concurs with the comments of
The document the CDCA. (This path eliminates
revision is put a subsequent full CDCA review ** In this case, AA
in the CDCA cycle and provides for a minimal may be PA or TA or
X status of APPROVE review instead.) just a user with no
contractual rela-
5J8 tionship with the
5-12 CDCA CDCA.

FIGURE B-6 (continued): DOCUMENT RELEASE/APPROVAL CASE 5 (Part 2 of 2).

(Note 2)
A new revision of a
document (in CDCA Reviewers may
status of SUBMIT) make comments
is put in AA status O
of SUBMIT O
6J2 The document
6-2 AA revision is put Do CASE 6 Receive 6J3
6-1 CDCA in the AA status starting at comments from Review comments
of SUBMIT for Step 6-1 other AA from other AA
(Note another AA(s)
1)
6-5 AA 6-6 ** 6-7 AA 6-8 AA
** Other AA

Note 1: Use this path when coordination with another AA

(either a TA, PA, or other AA) is required or desired The document
X prior to a final disposition by either the CDCA or this revision is put
activity. in the AA
6J1 status of
PENDING
Note 2: Use this path when coordination with another AA AA receives
(either a TA, PA, or other AA) is not required and not 6-9 AA announcement of
desired prior to the final disposition by the CDCA or final disposition
this activity. & & of a change to a
document

B-308
6J4 6J5
A recommendation is
application activity made to the CDCA 6-11 *
the most current reviewers may make (CASE 4 resumes at X
APPENDIX B
MIL-STD-2549

CCCA-approved comments to any document Step 4-4, or CASE 5 * From either CDCA or
document revision representation which is resumes at Step 5-6) another AA 6J6
is put in attached to the document
Application revision and which have a
Activity status document representation 6-10 AA
SUBMIT revision release status
of released
6-3 PA/AA
6-4 AA

to
1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

FIGURE B-7: DOCUMENT RELEASE/APPROVAL CASE 6 (Part 1 of 2).

An Application Activity (AA) receives a change to a document. The change may either be a proposed change under consideration by the Current
Document Change Authority (CDCA) for the document, or may have been approved by the CDCA already. (The AA may be a Tasking Activity [TA],
Performing Activity [PA] or some other AA.)
from
1

O O Note 3: Use this path when coordination with another AA

(either a TA, PA, or other AA) is required or desired
6J7 The document 6J8 prior to a final disposition by this activity.
revision is put Do CASE 6 Receive
in the AA status starting at disposition
of SUBMIT for Step 6-3 from other AA Note 2: Use this path when coordination with another AA
another AA(s) (either a TA, PA, or other AA) is not required and not
desired prior to the final disposition by this activity.
6-12 AA 6-13 ** 6-14 AA

** Other AA

B-309
the document Initiate action
APPENDIX B
MIL-STD-2549

revision is placed to create a

in application document to Notify other AAs
activity status replace the one of disposition, Modify
NOT-ADOPTED previously in use if necessary contracts if
X (CASE 6 resumes necessary
6-16 AA at Step 6-14)
6-15 AA 6J10
6-18 AA 6-19 TA
X

6J9

the document
revision is placed
in application
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

activity status
ADOPTED

6-17 AA

FIGURE B-7 (continued): DOCUMENT RELEASE/APPROVAL CASE 6 (Part 2 of 2).

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.22. Electronic Files. Entity tables numbered in the range of 900 through 909 contain the identification of
electronic files, their associated attributes, physical location and application software launch scripts. The
relationships between the file entity tables are depicted in Figure 23FILE1.

B.5.22.1. Table 900, File definition (FILE). This table contains the unique user-defined name of an electronic
file with the cross reference to its actual (physical) storage location.

a. The proprietary-data-rights-commercial-enterprise-name (PRPCOM900) is the name of the company

b. If the technical-document-government-data-rights-code (RGTCOD016) has any value other than 'U' or

'N', the value of document-company-proprietary-rights-code (PRPCOD017) must be 'P'.

c. The contract-document-identifier (CONIDN950) must appear as part of the Government rights in

technical data claim text and, therefore, must be nonblank if the technical-document-government-data-
rights-code (RGTCOD016) is anything other than 'U' or 'N'; in all other cases, it is optional. The
technical-document-government-data-rights-expiration-date (RGTEXP900) also must be blank if the
value of RGTCOD016 is 'U' or 'N', and must be nonblank for all other values.

d. The copyright-owner-enterprise-identifier (CPYENT900) is the name of the enterprise which has

copyrighted the data and, therefore, must be blank if the document-copyright-code (CPYCOD013) has a
value of 'N' and must be nonblank for all other values.

e. The document-distribution-controller-enterprise-identifier (DISENT900) and the document-distribution-

controller-enterprise-office-name (DISOFF900) together identify the distribution controlling office which
appears as part of the distribution statement; therefore, they both must be blank if the value of document-
distribution-statement-code (DISCOD014) is 'N' or 'A' and must be nonblank for all other values. The
document-distribution-restriction-determination-date (DISDAT900) is the date of determination that a
distribution statement is required and, therefore, must be blank if the value of DISCOD014 has a value of
'N' or 'A' and nonblank for all other values.

f. If the document-current-security-classification-code (SECCOD900) is any value other than 'U' or 'FOUO',

the document-security-classification-date (SCLSDT900) must be nonblank, either the document-security-
declassification-date (SDCLDT900) or the document-security-declassification-process-event-name
(SDCLEV900) must be nonblank, and the document-security-classification-authority-text (SECAUT900)
must be nonblank. Additionally, if the value of SECCOD900 is anything other than 'U', 'C', 'NC', 'NR' or
'FOUO', the value of document-downgrade-security-classification-code (SDWNCD900) may be nonblank;
otherwise, it must be blank. If SDWNCD900 is nonblank, either the document-security-classification-
downgrade-date (SDWNDT900) or the document-security-classification-downgrade-process-event-name
(SDWNEV900) must be nonblank; otherwise, they must be blank. If the value of SECCOD900 is 'U' or
'FOUO', then, the values of SCLSDT900, SDCLDT900, SDCLEV900, SDWNCD900, SDWNDT900,
SDWNEV900 and SECAUT900 must be blank.

g. The value of the document-file-compression-method-code (CMPMTH900) must be blank if the value of

document-file-compression-code (CMPCOD900) is 'N' and must be nonblank if the value of
(CMPCOD900) is 'Y'.

B-310
FILE / 900 (see 6ECP1, 7NOR2,10RFD2, 21REP1, 21REP3, 22REV2, 22REV4, 26CON3)
may specify STAFF / 943
CONDOC / 950 (from 26CON1) file-originator.person-name (FK)
technical data file-originator-office-address.office-address (FK) person-name
contract-identifier
rights file-identifier may originate office-address
file-creation-date
file-creation-time

ENTERPRISE / 002 (from 1GEN1) software-source-identifier (FK)

may claim copyright-code (FK) GENERIC-SWPROD / 170 (from 4SW3)
enterprise-identifier copyrights to software-generic-identifier (FK)
may be used software-source-identifier
file-name software-generic-identifier
to create
file-description-text
file-type-code
is subdivided computer-operating-system-type-code
P current-security-classification-code.security-classification-code (FK) may be stored at
may be d downgrade-security-classification-code.security-classification-code (FK)
OFFICE / 941 (from 25ADD1) istribution proprietary-rights-code (FK)
enterprise-identifier (FK) controlling technical-data-rights-code (FK) COMPAPPLIC / 902
office-symbol office for proprietary-data-company-name.commercial-name (FK) software-source-identifier (FK)
contract-identifier (FK) software-generic-identifier (FK)
export-control-code (FK) application-software-location
distribution-code (FK)
distribution-controlling-enterprise-identifier.enterprise-identifier (FK) application-software-launch-script-location-identifier

may claim distribution-controlling-office-symbol.office-symbol (FK)

COMPANY / 005 (from 1GEN1) proprietary, copyright-owning-enterprise-identifier.enterprise-identifier (FK)
or limit/restrict file-location (AK1)
commercial-name
Gov't data rights file-compression-code may be used to view
file-compression-method-code

B-311
may apply to
may be viewed using
may apply to downgrade of
APPENDIX B
MIL-STD-2549

ACESS / 018 (from 1GEN2)

may apply to
security-access-restriction-code
CLASS / 012 (from 1GEN2)
security-classification-code may apply to
VIEWLAUNCH / 903
may apply to may apply to software-source-identifier (FK)
software-generic-identifier (FK)
may have access application-software-location (FK)
CPYRGT / 013 (from 1GEN2) may apply to restricted by file-originator (FK)
copyright-code file-originator-office-address (FK)
may apply to file-identifier (FK)
file-creation-date (FK)
file-creation-time (FK)
FILE-ACCESS / 901
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

DISTRB / 014 (from 1GEN2)

DATARGT / 016 (from 1GEN2) security-access-restriction-code (FK)
distribution-code
technical-data-rights-code file-originator (FK)
file-originator-office-address (FK)
file-identifier (FK)
file-creation-date (FK)
EXPORT / 015 (from 1GEN2) PROP / 017 (from 1GEN2) file-creation-time (FK)
FIGURE 23FILE1 proprietary-rights-code
export-control-code
FILE DEFINITION
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

h. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role copyright-owner-
enterprise-identifier (CPYENT900).

i. Attribute enterprise-identifier (ENTIDN002) inherited from Table 941 assumes the role document-
distribution-controller-enterprise-identifier (DISENT900).

j. Attribute enterprise-office-name (OFFSYM941) inherited from Table 941 assumes the role document-
distribution-controller-enterprise-office-name (DISOFF900).

k. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role
enterprise-file-origination-office-address-text (FILADD900).

l. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role file-originator-human-
name (FILORG900).

m. Attribute commercial-enterprise-name (COMNAM005) inherited from Table 005 assumes the role
proprietary-data-rights-commercial-enterprise-name (PRPCOM900).

n. Attribute document-security-classification-code (SECCOD012) inherited from Table 012 assumes the role
document-downgrade-security-classification-code (SDWNCD900).

o. Attribute document-security-classification-code (SECCOD012) inherited from Table 012 assumes the role
document-current-security-classification-code (SECCOD900).

Code Data Element Title DED Key

FILDAT900 electronic-document-file-creation-date 0082 K
FILIDN900 electronic-document-file-identifier 0206 K
FILTIM900 electronic-document-file-creation-time 0160 K
FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILORG900 file-originator-human-name 0069 FK
SWIDEN170 software-product-generic-identifier 0060 FK

CONIDN950 contract-document-identifier 0015 FK

CPYCOD013 document-copyright-code 0012 FK
CPYENT900 copyright-owner-enterprise-identifier 0052 FK, O
DISCOD014 document-distribution-statement-code 0014 FK
DISENT900 document-distribution-controller-enterprise-identifier 0052 FK, O
DISOFF900 document-distribution-controller-enterprise-office-name 0044 FK
EXPCOD015 document-export-control-code 0079 FK
PRPCOD017 document-company-proprietary-data-rights-code 0084 FK
PRPCOM900 proprietary-data-rights-commercial-enterprise-name 0170 FK, O
RGTCOD016 technical-document-government-data-rights-code 0022 FK
SDWNCD900 document-downgrade-security-classification-code 0010 FK, O
SECCOD900 document-current-security-classification-code 0010 FK
SWSORC170 software-product-source-entity-identifier 0033 FK, O

B-312
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

CMPCOD900 document-file-compression-code 0215 M

CMPMTH900 document-file-compression-method-code 0214
DISDAT900 document-distribution-restriction-determination-date 0082
FILDES900 document-file-description-text 0212
FILLOC900 document-file-electronic-storage-place-identifier 0209 AK1, M
FILNAM900 document-file-name 0211 M
FILTYP900 document-file-type-code 0210 M
OPSYST900 computer-operating-system-asset-type-code 0213
RGTEXP900 technical-document-government-data-rights-expiration-date 0082
SCLSDT900 document-security-classification-date 0082
SDCLDT900 document-security-declassification-date 0082
SDCLEV900 document-security-declassification-process-event-name 0156
SDWNDT900 document-security-classification-downgrade-date 0082
SDWNEV900 document-security-classification-downgrade-process-event- 0156
name
SECAUT900 document-security-classification-authority-text 0155

B.5.22.2. Table 901, File security access restriction(s) (FILE-ACCESS). This table correlates special
Government security access restrictions with specific files.

Code Data Element Title DED Key

ACCCOD018 document-security-access-restriction-code 0085 FK
FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILIDN900 electronic-document-file-identifier 0206 FK
FILORG900 file-originator-human-name 0069 FK

B.5.22.3. Table 902, Computer application software storage location and usage instructions (COMPAPPLIC).
This table stores the procedures (or pointers to the procedures) for launching the application software required to
view/edit the file.

Code Data Element Title DED Key

APPLOC902 application-software-product-electronic-storage-place- 0209 K
identifier
SWIDEN170 software-product-generic-identifier 0060 FK
SWSORC170 software-product-source-entity-identifier 0033 FK

LAUNCH902 application-software-product-launch-script-electronic- 0209 M

storage-place-identifier

B.5.22.4. Table 903, Software viewers (VIEWLAUNCH). This table associates software applications which
can be used to view a file with the file.

B-313
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

APPLOC902 application-software-product-electronic-storage-place- 0209 FK
identifier
FILADD900 enterprise-file-origination-office-address-text 0081 FK
FILDAT900 electronic-document-file-creation-date 0082 FK
FILIDN900 electronic-document-file-identifier 0206 FK
FILORG900 file-originator-human-name 0069 FK
FILTIM900 electronic-document-file-creation-time 0160 FK
SWIDEN170 software-product-generic-identifier 0060 FK
SWSORC170 software-product-source-entity-identifier 0033 FK

B.5.22.5. Tables 904 through 909. Reserved.

B-314
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.23. Company documents, parts and materials. Entity tables numbered in the range of 910 through 939
contain the identification of company drawings, specifications and other documents, commercial part numbers and
commercial materials issued by individual companies, along with all associated attributes. Commercial
companies, as used herein, do not use a CAGE code as their primary identification, but use their company name
instead. This means that the contents of this section are limited to documents identified by a company name and a
document number or title. Parts are assumed to be identified by a company name and part number, and materials
are assumed to be identified by a company name and a material name. The relationships between these various
company entity tables are depicted in Figures 24COM1 through 24COM4.

B.5.23.1. Table 910, Documents identified by company name (in lieu of CAGE code) (COMPANY-DOC).
This table is a subtype of Table GENERIC-DOC/010 for the case where the value of document-source-
identification-type-code (ENTTYP010) is 'M'. It contains the unique identification of commercial documents
which are identified by company name, a document identifier, and a document type.

a. Attribute document-source-entity-identifier (SRCIDN010) inherited from Table 010 assumes the role
commercial-document-source-enterprise-name (SRCCOM910).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM910 commercial-document-source-enterprise-name 0170 FK

B.5.23.2. Table 911, Company document revisions (for company name used in lieu of CAGE code)
(COMPANY-DOCREV). This table is a subtype of Table GENERIC-DOCREV/011 for the case where the value
of document-source-identification-type-code (ENTTYP010) is 'M'. Due to parallel categorization, it is a de facto
child of Table COMPANY-DOC/910. It contains the revision history for the commercial documents contained in
Table 910.

a. Because this table is a de facto child of Table 910, document-source-entity-identifier (SRCIDN010)

inherited from Table 011 is really a commercial-document-source-enterprise-name (SRCCOM910)
existing in Table 910. Therefore, SRCIDN010 assumes the identity SRCCOM910.

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM910 commercial-document-source-enterprise-name 0170 FK

B.5.23.3. Table 912, Commercial engineering drawings (COMDWG). This table is one category of Table
COMPANY-DOC/910 for the case when the value of the document-type-code in Table 910 is either 'DWG' or 'PL'.
It contains the identification of drawings which are identified by a company name and an alphanumeric identifier.

B-315
GENERIC-DOC / 010 (from 1GEN2)
document-source-entity-identifier
document-identifier
document-type-code
document-identification-type-code
document-source-entity-type-code

document-source-entity-type-code

COMPANY-DOC / 910
commercial-document-source-name.document-source-entity-identifier (FK)
document-identifier (FK)
document-type-code (FK)

document-type-code
STDDOC
DWG or PL P-SPEC

COMDWG / 912 (see 4SW2, 24COM2) COMPSPEC / 913 COMSTDDOC / 914

design-company-name.commercial-document-source-name (FK) design-company-name.commercial-document-source-name (FK) commercial-document-source-name (FK)
drawing-alphanumeric-identifier.document-identifier (FK) document-identifier (FK) document-identifier (FK)

B-316
document-type-code (FK) document-type-code (FK) document-type-code (FK)
APPENDIX B

product-type-code product-type-code
MIL-STD-2549

product-type-code

P M

COMSPEC-PIN / 915 (see 24COM2) product-type-code

COMSPEC-MAT / 916 (see 24COM3)
design-company-name (FK)
design-company-name (FK)
document-identifier (FK)
material-document-identifier.(document-type-code,document-identifier) (FK)
document-type-code (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

P M

COMSTDDOC-PIN / 917 (see 24COM2)

COMSTDDOC-MAT / 918 (see 24COM3)
design-company-name.commercial-document-source-name (FK)
document-identifier (FK) design-company-name.commercial-document-source-name (FK)
FIGURE 24COM1 material-document-identifier.(document-type-code,document-identifier) (FK)
COMPANY DOCUMENTS/PARTS/MATERIALS document-type-code (FK)
COMDWG / 912 (from 24COM1) COMSPEC-PIN / 915 (from 24COM1) COMSTDDOC-PIN / 917 (from 24COM1)
COMPANY / 005 (from 1GEN1)
design-company-name design-company-name design-company-name
commercial-name
drawing-alphanumeric-identifier document-identifier document-identifier
document-type-code document-type-code document-type-code

may define
may design may define
Assertion: the relationship of Table 912
may define
to Table 919 is 1:0-M if the value of
document-type-code is 'DWG'; it is 1:P if Assertion: the relationships 912 to 919,
the value of document-type-code is 'PL'. 915 to 919, and 917 to 919 are
mutually exclusive. GENERIC-DOCREV / 011 (from 1GEN2)
P P
document-source-identifier
COMBASICPART / 919 document-identifier
design-company-name.(commercial-name,design-company-name) (FK) document-type-code
part-basic-identifier document-generic-revision
document-identifier.(drawing-alphanumeric-identifier,document-identifier) (FK)
document-type-code (FK)

GENERIC-PIN / 210 (from 5PIN2) has iterations document-source-entity-type-code

design-enterprise-identifier M (from Table 010)
part-identifier P
COMPARTREV / 925

B-317
COMPANY-DOCREV / 911 (de facto child of COMPANY-DOC)
design-company-name (FK)
commercial-document-source-name.document-source-identifier (FK)
APPENDIX B

part-basic-identifier (FK)
MIL-STD-2549

part-revision document-identifier (FK)

enterprise-identification-type-code document-type-code (FK)
(from Table 002) document-generic-revision (FK)

COM
is

may be defined on, or may have contexts may define, or be a context of

1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

COMPIN / 920 (see 5PIN2) COMDOCREV-COMPINREV / 926

design-company-name.(design-enterprise-identifier,design-company-name) (FK) design-company-name (FK)
part-identifier.(part-identifier,part-revision,part-basic-identifier) (FK) part-basic-identifier (FK)
part-revision (FK)
commercial-document-source-name (FK)
document-identifier (FK)
document-type-code (FK)
FIGURE 24COM2 document-generic-revision (FK)
COMPANY PARTS
GENERIC-MATID / 200 (from 5PIN1)
design-enterprise-identifier
material-generic-identifier
material-identification

COMPANY / 005 (from 1GEN1)

commercial-name
COMSPEC-MAT / 916 (from 24COM1)
design-company-name enterprise-identification-type-code
material-document-identifier
(from Table 002)
may be original
COM design activity of
COMSTDDOC-MAT / 918 (from 24COM1)
design-company-name
material-document-identifier COM-MATID / 921 (see 5PIN1)
design-company-name.design-enterprise-identifier (FK)
material-generic-identifier (FK) COMBASICMAT / 922
material-identification (FK)
commercial-name (FK)
product-identification-type-code material-name
defines

B-318
defines
APPENDIX B

product-identification-type-code
MIL-STD-2549

has
Assertion: The relationships between
Tables 916 and 923, and between NUM NAM
Tables 918 and 923 are mutually
exclusive, but cannot both be null. P P
COM-NUMMAT / 923
design-company-name (FK)
material-document-identifier.(material-generic-identifier,material-document-identifier) (FK)
material-identification (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

P
COM-NAMMAT / 924
design-company-name.(design-company-name,commercial-name) (FK)
material-name.(material-generic-identifier,material-name) (FK)
FIGURE 24COM3 material-identification (FK)
COMPANY MATERIALS
COMPANY / 005 (from 1GEN1)
commercial-name

may assign item

COMSTOCK / 927
GENERIC-PIN / 210 (from 5PIN2)
GENERIC-MATID / 200 (from 5PIN1) commercial-name (FK)
company-stock-number design-enterprise-identifier
design-enterprise-identifier
part-identifier
material-generic-identifier
product-type-code
material-identifier

B-319
may be company may be company may be stocked as
may be stocked as stock number for stock number for
APPENDIX B
MIL-STD-2549

COM-MATSTOCK / 928
commercial-name (FK) COM-PINSTOCK / 929
company-stock-number (FK) commercial-name (FK)
design-enterprise-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

company-stock-number (FK)
material-generic-identifier (FK) design-enterprise-identifier (FK)
material-identifier (FK) part-identifier (FK)

FIGURE 24COM4
COMPANY STOCK NUMBER
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Attribute commercial-document-source-enterprise-name (SRCCOM910) inherited from Table 910

assumes the role design-enterprise-name (DESCOM912).

b. Attribute document-identifier (DOCIDN010) inherited from Table 910 assumes the role engineering-
drawing-document-alphanumeric-identifier (DWGNUM912).

Code Data Element Title DED Key

DESCOM912 design-enterprise-name 0170 FK
DOCTYP010 document-type-code 0004 FK
DWGNUM912 engineering-drawing-document-alphanumeric-identifier 0003 FK

CONTYP912 administrative-control-drawing-document-type-code 0032 M

B.5.23.4. Table 913, Commercial program-unique specifications (identified by company name in lieu of CAGE
code) (COMPSPEC). This table is a subtype of Table COMPANY-DOC/910 and contains a subset of the data in
Table 910 for the case where the value of document-type-code (DOCTYP010) in Table 910 is 'P-SPEC'.

a. Attribute commercial-document-source-enterprise-name (SRCCOM910) inherited from Table 910

assumes the role design-enterprise-name (DESCOM913).

Code Data Element Title DED Key

DESCOM913 design-enterprise-name 0170 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK

PRDTYP913 product-type-code 0034 M

B.5.23.5. Table 914, Company-unique standardization documents (COMSTDDOC). This table is a

subcategory of Table COMPANY-DOC/910 for the case where the value of document-type-code is 'STDDOC'. It
contains the unique identification of company standards. It has three subcategories based on the value of product-
type-code (PRDTYP914); only COMSTDDOC-PIN/917, COMSTDDOC-MAT/918 are shown in Figure 24COM1.
It has two subcategories based on the value of document-identification-type-code (IDNTYP010) in Table 010; only
Table COMSTDNUMDOC/440 is shown (see Figures 11STDS1 and 24COM1).

Code Data Element Title DED Key

DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCCOM910 commercial-document-source-enterprise-name 0170 FK

PRDTYP914 product-type-code 0034 M

B.5.23.6. Table 915, Parts defined by a commercial program-unique specification (COMSPEC-PIN). This table
is a subtype of Table COMPSPEC/913 and contains the subset of the data in Table 913 consisting of those
instances where the value of product-type-code in Table 913 is 'P'. These instances are program-unique
specifications which define parts/part numbers.

B-320
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DESCOM913 design-enterprise-name 0170 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK

B.5.23.7. Table 916, Materials defined by a commercial program-unique specification (COMSPEC-MAT).

This table is a subtype of Table COMPSPEC/913 and contains the subset of the data in Table 913 consisting of
those instances where the value of product-type-code in Table 913 is 'M'. These instances are program-unique
specifications which define materials (or parts) not identified by part numbers.

a. The attributes document-identifier (DOCIDN010) and document-type-code (DOCTYP010) inherited from

Table 913 are concatenated and assume the role material-document-identifier (MATDOC916). (See
Appendix C for concatenation order.)

Code Data Element Title DED Key

DESCOM913 design-enterprise-name 0170 FK
MATDOC916 material-document-identifier 0192 FK

B.5.23.8. Table 917, Parts defined by a commercial standardization document (COMSTDDOC-PIN). This
table is a subtype of Table COMSTDDOC/914 and contains the subset of the data in Table 914 consisting of those
instances where the value of product-type-code in Table 914 is 'P'. These instances are standardization documents
which define parts/part numbers.

a. Attribute commercial-document-source-enterprise-name (SRCCOM910) inherited from Table 914

assumes the role design-enterprise-name (DESCOM917).

Code Data Element Title DED Key

DESCOM917 design-enterprise-name 0170 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK

B.5.23.9. Table 918, Materials defined by a commercial standardization document (COMSTDDOC-MAT).

This table is a subtype of Table COMSTDDOC/914 and contains the subset of the data in Table 914 consisting of
those instances where the value of product-type-code in Table 914 is 'M'. These instances are standardization
documents which define materials (or parts) not identified by part numbers.

a. Attribute commercial-document-source-enterprise-name (SRCCOM910) inherited from Table 914

assumes the role design-enterprise-name (DESCOM918).

b. The attributes document-identifier (DOCIDN010) and document-type-code (DOCTYP010) inherited from

Table 914 are concatenated and assume the role material-document-identifier (MATDOC918). (See
Appendix C for concatenation order.)

B-321
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DESCOM918 design-enterprise-name 0170 FK
MATDOC918 material-document-identifier 0192 FK

B.5.23.10. Table 919, Basic part identified by company name (in lieu of CAGE code) and part number
(COMBASICPART). This table contains the unique identification of commercial parts.

a. The value of design-enterprise-name inherited from Table 912 (DESCOM912), Table 915
(DESCOM913), or Table 917 (DESCOM917) must be the same as the value of the commercial-
enterprise-name (COMNAM005) inherited from Table 005. Therefore these fields are merged and
assume the identity design-enterprise-name (DESCOM919).

b. The document-identifier (DOCIDN919) is inherited either from Table 912 (drawing-alphanumeric-

identifier [DWGNUM912]), Table 915 (document-identifier [DOCIDN010]), or Table 917 (document-
identifier [DOCIDN010]).

Code Data Element Title DED Key

BPINNO919 part-product-basic-identifier 0024 K
DESCOM919 design-enterprise-name 0170 FK

DOCIDN919 document-identifier 0122 FK

DOCTYP010 document-type-code 0004 FK

B.5.23.11. Table 920, Commercial part (identified by company name, part number and revision) (COMPIN).
This table is a subtype of Table GENERIC-PIN/210 and contains a subset of the data in Table 210 and correlates
the commercial part number into the generic part hierarchy.

a. The concatenation of the values of part-product-basic-identifier (BPINNO919) and the part-product-

revision-identifier (PINREV925) inherited from Table COMPARTREV/925 must be the same as the value
of (PARNUM210) in Table GENERIC-PIN/210 therefore the concatenation of BPINNO919 and
PINREV925 is merged with PARNUM210 and assumes the identity PARNUM920.

b. Attribute design-enterprise-identifier (DESENT210) inherited from Table 210 and design-enterprise-

name (DESCOM919) inherited from Table 925 must both have the same value. Therefore they merge
and assume the identity design-enterprise-name (DESCOM919).

Code Data Element Title DED Key

DESCOM919 design-enterprise-name 0170 FK
PARNUM920 part-product-identifier 0024 FK

B.5.23.12. Table 921, Commercial materials (identified by company name in lieu of CAGE code) (COM-
MATID). This table is a subtype of Table GENERIC-MATID/200 and contains a subset of the data in Table 200
for the case where the value of enterprise-identification-type-code (ENTTYP002) in Table 002 is "COM". It
correlates the commercial material into the generic material hierarchy. This table has two subtypes: COM-
NUMMAT/923 and COM-NAMMAT/924.

B-322
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. Attribute design-enterprise-identifier (DESENT200) inherited from Table 200 assumes the role design-
enterprise-name (DESCOM921).

Code Data Element Title DED Key

DESCOM921 design-enterprise-name 0170 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK

PIDTYP921 product-identification-type-code 0123 M

B.5.23.13. Table 922, Commercial material name (COMBASICMAT). This table contains the unique
identification of a commercial material which is identified by a design company name and a material name.

Code Data Element Title DED Key

MATNAM922 material-product-name 0191 K
COMNAM005 commercial-enterprise-name 0170 FK

B.5.23.14. Table 923, Commercial materials identified by document (COM-NUMMAT). This table is a subtype
of Table COM-MATID/921 for the case where the value of product-identification-type-code (PIDTYP921) in Table
921 is 'NUM'. It contains those commercial materials which are identified by the company name and a
alphanumeric document identifier.

a. The design-enterprise-name inherited from either Table 916 (DESCOM913) or Table 918 (DESCOM918)
must be the same as the design-enterprise-name inherited from Table 921 (DESCOM921) and therefore,
the merge and assume the identity DESCOM923.

b. The material-document-identifier inherited from either Table 916 (MATDOC916) or Table 918
(MATDOC918) must be the same as the value of material-product-generic-identifier inherited from Table
921 (MATGID200) and therefore, they merge and assume the identity material-document-identifier
(MATDOC923).

Code Data Element Title DED Key

DESCOM923 design-enterprise-name 0170 FK
MATDOC923 material-document-identifier 0192 FK
MATIDN200 material-product-identifier 0038 FK

B.5.23.15. Table 924, Commercial materials identified by name (COM-NAMMAT). This table is a subcategory
of Table COM-MATID/921 for the case where the value of the product-identification-type-code (PRDTYP921) is
'NAM'. It consists of the subset commercial materials which are identified by a company (design source) name, a
material name, and a list of material parameters.

a. Attribute design-enterprise-name (DESCOM921) inherited from Table 921 and commercial-enterprise-

name (COMNAM005) inherited from Table 922 must both have the same value. Therefore they merge
and assume the identity design-enterprise-name (DESCOM921).

B-323
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

b. Attribute material-product-generic-identifier (MATGID200) inherited from Table 921 and material-

product-name (MATNAM922) inherited from Table 922 must both have the same value. Therefore they
merge and assume the identity material-product-name (MATNAM922).

Code Data Element Title DED Key

DESCOM921 design-enterprise-name 0170 FK
MATIDN200 material-product-identifier 0038 FK
MATNAM922 material-product-name 0191 FK

B.5.23.16. Table 925, Commercial part revisions (COMPARTREV). This table contains part revisions to
commercial parts. Commercial parts are those parts which are identified by a company name rather than a CAGE
code. This table must be used for commercial parts; however, if the company practice is not to assign revisions to
parts, the value of part-product-revision-identifier (PINREV925) can be dash ('-') and system implementations may
display a null for this value.

Code Data Element Title DED Key

PINREV925 part-product-revision-identifier 0181 K
BPINNO919 part-product-basic-identifier 0024 FK
DESCOM919 design-enterprise-name 0170 FK

B.5.23.17. Table 926, Correlation of document revisions to part revisions (COMDOCREV-COMPINREV). This
table contains the correlation of commercial document revisions with commercial part revisions. The commercial
documents may represent the defining document or some other context of the part. This table is necessary to
support the STEP concept of multiple contexts.

Code Data Element Title DED Key

BPINNO919 part-product-basic-identifier 0024 FK
DESCOM919 design-enterprise-name 0170 FK
DOCIDN010 document-identifier 0122 FK
DOCREV011 document-generic-revision-identifier 0243 FK
DOCTYP010 document-type-code 0004 FK
PINREV925 part-product-revision-identifier 0181 FK
SRCCOM910 commercial-document-source-enterprise-name 0170 FK

B.5.23.18. Table 927, Company stock numbers (COMSTOCK). This table contains company stock numbers for
parts and materials. (In some companies, these are depicted by company-equivalent drawings which depict
customer or standard parts, and therefore, are referred to as company part numbers.)

B-324
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

STKNUM927 commercial-product-inventory-stock-identifier 0186 K
COMNAM005 commercial-enterprise-name 0170 FK

B.5.23.19. Table 928, Commercial stock number for material (COM-MATSTOCK). This table contains the
correlation of commercial stock numbers with materials (or parts) not identified by part numbers.

Code Data Element Title DED Key

COMNAM005 commercial-enterprise-name 0170 FK
DESENT200 design-enterprise-identifier 0052 FK
MATGID200 material-product-generic-identifier 0092 FK
MATIDN200 material-product-identifier 0038 FK
STKNUM927 commercial-product-inventory-stock-identifier 0186 FK

B.5.23.20. Table 929, Commercial stock number for parts identified by part number. (COM-PINSTOCK). This
table contains the correlation of commercial stock numbers with part numbers.

Code Data Element Title DED Key

COMNAM005 commercial-enterprise-name 0170 FK
DESENT210 design-enterprise-identifier 0052 FK
PARNUM210 part-product-identifier 0024 FK
STKNUM927 commercial-product-inventory-stock-identifier 0186 FK

B.5.23.21. Tables 930 through 939. Reserved.

B-325
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.24. Address Tables. Entity tables numbered in the range of 940 through 949 are an "address book". They
contain the names, addresses, phone numbers, fax numbers, e-mail addresses, and assignments of the various
points of contact necessary for certain kinds of documents and for file identification. (See also: B.5.22.) This
section could easily be used to contain other personal information (such as security clearance level, etc.) and
administrative access authority. The various tables and their relationships are shown in Figure 25ADD1.

B.5.24.1. Table 940, Address (ADDRESS). This table contains enterprise identifiers and associated addresses.
It is primarily for use in conjunction with data item delivery.

Code Data Element Title DED Key

ADDRES940 enterprise-address-text 0039 K
ENTIDN002 enterprise-identifier 0052 FK

B.5.24.2. Table 941, Office Symbols (OFFICE). This table contains organizational identifiers within an
enterprise. These are often referred to as office symbols, or desk codes. They are included primarily for CDRL
distribution and for CM document change control authority.

Code Data Element Title DED Key

OFFSYM941 enterprise-office-name 0044 K
ENTIDN002 enterprise-identifier 0052 FK

HICLAS941 enterprise-security-classified-document-receipt- 0224

authorization-code

B.5.24.3. Table 942, Division address (DIV-ADDRESS). This table is the correlation of enterprise divisions
(office symbols) with enterprise addresses. It is used primarily for document delivery. It also provides contract
point-of-contact information.

a. The enterprise-identifier (ENTIDN002) inherited from Table 940 and that inherited from Table 941 must
be the same. They are merged and concatenated with the enterprise-address-text (ADDRES940) inherited
from Table 940 and the enterprise-office-name (OFFSYM941) inherited from Table 941 and assume the
identity enterprise-office-address-text (DIVADD942). See Appendix C for concatenation order.

Code Data Element Title DED Key

DIVADD942 enterprise-office-address-text 0081 FK

FAXNUM942 human-facsimile-machine-access-identifier 0225

TELPHN942 human-telephone-access-identifier 0225

B.5.24.4. Table 943, Staffing (STAFF). This table is a telephone/electronic-mail directory of key personnel in
Government and industry. It is used primarily for recording document receipt and source of redline reviews of
documents/files, and Configuration Control Board (CCB) membership. The stored attributes could be expanded to
form the basis for CM AIS access.

B-326
ENTERPRISE / 002 (from 1GEN1)
enterprise-identifier

has may be divided into

ADDRESS / 940
OFFICE / 941 (see 1GEN2, 6ECP5, 10RFD6, 17AUD1, 23FILE1, 26CON1)
enterprise-identifier (FK)
enterprise-identifier (FK)
address
office-symbol

may have can be located at

DIV-ADDRESS / 942 (see 26CON1, 26CON2)

office-address.(office-symbol,address,enterprise-identifier) (FK)

B-327
telephone-number
APPENDIX B
MIL-STD-2549

fax-number

may be staffed by

STAFF / 943 (see 6ECP1, 19CI2, 21REP1, 21REP3, 22REV1,

22REV2, 22REV3, 22REV4, 23FILE1, 26CON1)
person-name
office-address (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

telephone-number
FIGURE 25ADD1
fax-number
ADDRESS
email-address
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

PERNAM943 human-name 0069 K
DIVADD942 enterprise-office-address-text 0081 FK

EMAILX943 human-electronic-mail-access-identifier 0225

FAXNUM943 human-facsimile-machine-access-identifier 0225
TELPHN943 human-telephone-access-identifier 0225

B.5.24.5. Tables 944 through 949. Reserved.

B-328
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.25. Contract and contract data. Entity tables numbered in the range of 950 through 999 contain the
identification of contracts, contract line items, contract exhibits, contract data requirements, contract data
submittals and their approval cycle. Within the DOD Enterprise Data Model, contracts are limited to DoD
contracts and are treated as an entity, but not as a document; however, in this model, contracts are not so limited,
and are treated as one type of document. The relationships between the contract/contract data item entity tables are
depicted in Figures 26CON1 through 26CON6.

B.5.25.1. Table 950, Contract document definition (CONDOC). This table contains the contract identifier. A
contract is one subtype of NUMDOC/020 for the case where the value of document-type-code (DOCTYP010) in
Table 020 is 'CONTRCT'. This table also serves as a link to the DOD EDM CONTRACT entity.

a. The value of field enterprise-identifier (ENTIDN002) inherited from Table 002 as the tasking activity
must be the same as the value of document-source-enterprise-identifier (SRCENT020) inherited from
Table 020 and therefore can be merged with SRCENT020. The value of document-alphanumeric-
identifier (DOCNUM020) inherited from Table 020 must be the same as the value of contract-document-
alphanumeric-identifier (CONNUM977) inherited from Table 977 and therefore can be merged with
CONNUM977. These two pairs of merged fields are concatenated with document-type-code
(DOCTYP010) inherited from Table 020 and assume the identity contract-document-identifier
(CONIDN950).

b. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role
enterprise-administrative-contracting-office-address-text (ACOADD950).

c. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role administrative-
contracting-officer-human-name (ACONAM950).

d. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role
enterprise-procuring-contracting-office-address-text (PCOADD950).

e. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role product-procuring-
contracting-officer-human-name (PCONAM950).

f. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 943 assumes the role
performing-enterprise-contact-office-address-text (SELADD950).

g. Attribute enterprise-identifier (ENTIDN002) inherited from Table 002 assumes the role performing-
enterprise-identifier (SELENT950).

h. Attribute human-name (PERNAM943) inherited from Table 943 assumes the role contractor-human-
name (SELNAM950).

B-329
AGREEMENT TYPE / 975 (DOD EDM*) NUMDOC / 020 (from 1GEN3)
STAFF / 943 (from 25ADD1)
agreement-type-code document-source-enterprise-identifier
document-alphanumeric-identifier person-name
ENTERPRISE / 002 (from 1GEN1) document-type-code office-address
enterprise-identifier
is a type of

AGREEMENT / 976 (DOD EDM*) document-type-code

may be the
agreement-identifier tasking
activity for
agreement-type-code (FK)
may be the
performing may be performing activity
agreement-type-identifier activity for point of contact for

may be ACO for

CONTRACT / 977 (DOD EDM*)
contract-alphanumeric-identifier.agreement-identifier (FK)
may be PCO for

is a
1
CONDOC / 950 (see 18AUD1, 19CI1, 23FILE1, 26CON2)

B-330
contract-identifier.(document-source-enterprise-identifier,document-alphanumeric-identifier,document-type-code,contract-alphanumeric-identifier,enterprise-identifier) (FK)
performing-activity-enterprise-identifier.enterprise-identifier (FK)
APPENDIX B
MIL-STD-2549

performing-activity-poc-name.person-name (FK)
performing-activity-poc-address.office-address (FK)
aco-name.person-name (FK)
aco-address.office-address (FK)
pco-name.person-name (FK)
pco-address.office-address (FK)

DIV-ADDRESS / 942 (from 25ADD1)

office-address
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

is distributed to
may receive copy of

CONDIST / 962
contract-identifier (FK) *Defined in the U.S. DOD Enterprise Data Model (EDM)
FIGURE 26CON1 office-address (FK)
CONTRACT & CDRL DEFINITION (Part 1 of 2)
NUMDOCREV / 021 (from 1GEN4) CONEVENT / 961 (see 26CON3) CONDOC / 950 (from 26CON1)
document-source-enterprise-identifier contract-identifier (FK) may have
contract-identifier
document-alphanumeric-identifier event-code milestones
document-type-code
document-generic-revision
has deliveries
processed via

document-type-code DD250 / 960 (see 26CON3)

CONTRCT contract-identifier (FK)
CONMOD / 951 (de facto child of 950) (see 6ECP1, 8BL1, 10RFD1, 18AUD1, 22REV3) dd250-shipment-identifier
contract-identifier.(document-type-code,document-source-enterprise-identifier,document-alphanumeric-identifier) (FK) contract-modification (FK)
may be
contract-modification.document-generic-revision (FK) clin-identifier (FK)
delivered
and paid
orders for by
Assertion: The relationship
CI / 695 (from 19CI1) CLIN / 959 (see 6ECP1, 10RFD1) between 960 and 953, and the
ci-identifier contract-identifier (FK) relationship between 960 and
clin-identifier 954 (shown in Figure 26CON3)
may have
contract-modification (FK) are mutually exclusive.
P
may be documented by may have may provide payment for

DIDREV / 651 (from 16DID1)

CONEX / 952 document-source-enterprise-identifier
CLIN-CONEX / 958
contract-identifier (FK) is did-alphanumeric-identifier
contract-exhibit-identifier funded contract-identifier (FK) DISTRB / 014 (from 1GEN2) DID
contract-modification (FK) by clin-identifier (FK) document-generic-revision
distribution-code
contract-exhibit-identifier (FK)

B-331
ci-identifier (FK) P contract-modification (FK)
APPENDIX B
MIL-STD-2549

may have attached may apply to OFFICE / 941 (from 25ADD1)

may list enterprise-identifier
may be called
office-symbol
SOW / 957 (see 18AUD1) out for use by
sow-identifier.(document-source-entity-identifier,document-identifier,document-generic-revision,document-type-code) (FK)
contract-identifier (FK)
contract-modification (FK) may require

GENERIC-DOCREV / 011 (from 1GEN2) CDRL / 953 (see 26CON3)

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

document-source-entity-identifier may be contract-identifier (FK)

document-identifier referenced contract-exhibit-identifier (FK)
document-type-code by cdrl-sequence-identifier
document-generic-revision contract-modification (FK)
may be a
did-identifier.(document-generic-revision,DID,document-source-enterprise-identifier,did-alphanumeric-identifier) (FK)
dd250-shipment-identifier (FK)
FIGURE 26CON2 distribution-code (FK)
CONTRACT & CDRL DEFINITION (Part 2 OF 2) technical-office-identifier.(office-symbol,enterprise-identifier) (FK)
sow-identifier (FK)
OFFICE / 941 (from 25ADD1) CDRL / 953 (from 26CON2) CONEVENT / 961 (from 26CON2) DD250 / 960 (from 26CON2)
enterprise-identifier contract-identifier contract-identifier contract-identifier
office-symbol contract-modification event-code dd250-shipment-identifier DIV-ADDRESS / 942 (from 25ADD1)
contract-exhibit-identifier office-address
cdrl-sequence-identifier contract-modification
clin-identifier
clin-subline-identifier
may determine initial due date of
is submitted may determine subsequent due date of Assertion: The relationship
may be customer technical office between 960 and 953 (shown
may determine cut-off date of on Figure 26CON2), and the may receive copy of
may be contractor technical office relationship between 960 and
may provide payment for
954 are mutually exclusive.

DATASUB / 954
contract-identifier (FK)
CDRLSUBDIST / 963 (see 26CON5)
contract-modification (FK)
contract-exhibit-identifier (FK) contract-identifier (FK)
cdrl-sequence-identifier (FK) contract-modification (FK)
has iterations data-submittal-identifier must be contract-exhibit-identifier (FK)
distributed to cdrl-sequence-identifier (FK)
data-submittal-effective-cut--off-event.event-code (FK) data-submittal-identifier (FK)
data-submittal-initial-delivery-due-event.event-code (FK) office-address (FK)
data-submittal-subsequent-delivery-due-event.event-code (FK)
customer-technical-office.(office-symbol,enterprise-identifier) (FK)
P contractor-technical-office.(enterprise-identifier,office-symbol) (FK)
dd250-shipment-identifier (FK)
DATASUBREV / 955 (see 26CON5) receives various

B-332
contract-identifier (FK) P
contract-modification (FK)
contract-exhibit-identifier (FK) CDRLQTY / 964
APPENDIX B

cdrl-sequence-identifier (FK)
MIL-STD-2549

contract-identifier (FK)
data-submittal-identifier (FK) has approval status contract-modification (FK)
data-submittal-revision
contract-exhibit-identifier (FK)
cdrl-sequence-identifier (FK)
data-submittal-identifier (FK)
office-address (FK)
delivery-method-code

CDRLSTAT / 956 (see 26CON4)

contract-identifier (FK)
contract-modification (FK)
contract-exhibit-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

cdrl-sequence-identifier (FK)
data-submittal-identifier (FK)
data-submittal-revision (FK)
data-submittal-revision-disposition-status-code
data-submittal-revision-disposition-status-date
data-submittal-dispositioner-name
data-resubmittal-requirement-source.(contract-identifier,contract-modification,contract-exhibit-identifier,cdrl-sequence-identi fier,data-submittal-identifier,data-submittal-revision) (FK)

may cause a resubmittal identified as

FIGURE 26CON3
CONTRACT DATA SUBMITTAL
CDRLSTAT / 956 (from 26CON3)
contract-identifier
contract-modification
contract-exhibit-identifier
cdrl-sequence-identifier
data-submittal-identifier
data-submittal-revision
data-submittal-revision-disposition-status-code
data-submittal-revision-dispostion-status-date
data-submittal-dispositioner-name

data-submittal-revision-disposition-status-code

INWK
APV
CDRL-INWORK / 969
CDRL-APPR / 971
contract-identifier (FK)
contract-identifier (FK)
contract-modification (FK)

B-333
contract-modification (FK)
contract-exhibit-identifier (FK)
contract-exhibit-identifier (FK)
cdrl-sequence-identifier (FK)
APPENDIX B
MIL-STD-2549

cdrl-sequence-identifier (FK)
data-submittal-identifier (FK)
data-submittal-identifier (FK)
data-submittal-revision (FK)
data-submittal-revision (FK)
data-submittal-revision-disposition-status-code (FK)
data-submittal-revision-disposition-status-code (FK)

SUBMIT DISAPV

CDRL-SUBMIT / 970 (see 26CON5) CDRL-DISAPP / 972

Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

contract-identifier (FK) contract-identifier (FK)

contract-modification (FK) contract-modification (FK)
contract-exhibit-identifier (FK) contract-exhibit-identifier (FK)
cdrl-sequence-identifier (FK) cdrl-sequence-identifier (FK)
data-submittal-identifier (FK) data-submittal-identifier (FK)
data-submittal-revision (FK) data-submittal-revision (FK)
data-submittal-revision-disposition-status-code (FK) data-submittal-revision-disposition-status-code (FK)
FIGURE 26CON4
CDRL STATUS customer-technical-review-compeletion-suspense-date data-resubmittal-code
customer-final-disposition-suspense-date data-resubmittal-due-date
DATASUBREV / 955 (from 26CON3)
GENERIC-DOCREV / 011 (from 1GEN2)
contract-identifier
contract-modification document-source-entity-identifier
contract-exhibit-identifier document-identifier
cdrl-sequence-identifier document-type-code
data-submittal-identifier document-generic-revision
data-submittal-revision

may be submitted
includes under contract cdrl
P
SUBPKG / 965 (see 26CON5)
DOCREV-AAADOPT / 863 (from 22REV3) DOCREV-AAPEND / 865 (from 22REV3)
contract-identifier (FK)
contract-modification (FK) document-source-entity-identifier document-source-entity-identifier
REPREV-RELEASE / 806 (from 21REP2) contract-exhibit-identifier (FK) document-identifier document-identifier
cdrl-sequence-identifier (FK) document-type-code document-type-code
document-source-entity-identifier
data-submittal-identifier (FK) document-revision document-revision
document-identifier
data-submittal-revision (FK) application-activity-identifier application-activity-identifier
document-type-code
document-source-entity-identifier (FK) application-activity-approval-status-code application-activity-approval-status-code
document-representation-identifier
document-identifier (FK) application-activity-approval-status-date application-activity-approval-status-date
document-representation-revision
document-representation-release-status-code document-type-code (FK)
document-generic-revision (FK)

may be submitted may be submitted

B-334
under contract cdrl under contract cdrl
may be submitted may include Originating may include Application
APPENDIX B

under contract cdrl Activity and/or CDCA Activity adopted Assertion: The relationship
MIL-STD-2549

documents documents between Tables 863 and 967,

and between Tables 865 and 967
Assertion: The relationship between Tables 965 and 966, are mutually exclusive and
and between Tables 965 and 967 cannot both be 1:0. cannot both be 1:0.

REP-CCASUBPKG / 966
contract-identifier (FK) REP-AASUBPKG / 967
contract-modification (FK) contract-identifier (FK)
contract-exhibit-identifier (FK) contract-modification (FK)
cdrl-sequence-identifier (FK) contract-exhibit-identifier (FK)
data-submittal-identifier (FK) cdrl-sequence-identifier (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

data-submittal-revision (FK) data-submittal-identifier (FK)

document-source-entity-identifier (FK) data-submittal-revision (FK)
document-identifier (FK) document-source-entity-identifier (FK)
document-type-code (FK) document-identifier (FK)
document-type-code (FK)
document-representation-identifier (FK)
document-representation-revision (FK) document-revision (FK)
document-representation-release-status-code (FK) application-activity-identifier (FK)
application-activity-approval-status-code (FK)
application-activity-approval-status-date (FK)
FIGURE 26CON5
CDRL CONTENTS
SUBPKG / 965 (from 26CON4) CONSUBDIST / 963 (from 26CON3)
CDRL-SUBMIT / 970 (from 26CON4)
contract-identifier contract-identifier
contract-identifier
contract-modification contract-modification FILE / 900 (from 23FILE1)
contract-modification
contract-exhibit-identifier contract-exhibit-identifier
contract-exhibit-identifier file-originator
cdrl-sequence-identifier cdrl-sequence-identifier
cdrl-sequence-identifier file-originator-office-address
data-submittal-identifier data-submittal-identifier
data-submittal-identifier file-identifier
data-submittal-revision data-submittal-revision
data-submittal-revision file-creation-date
document-source-entity-identifier office-address
data-submittal-revision-disposition-status-code file-creation-time
document-identifier
document-type-code
document-revision

may comment on is reviewed by

may be commented on by may contain comments on

P
REPREV-FILE / 802 (from 21REP1)
CDRL-REDLINE / 968
document-source-entity-identifier
document-identifier contract-identifier (FK)
document-type-code contract-modification (FK)
document-representation-identifier contract-exhibit-identifier (FK)
may be
document-representation-revision cdrl-sequence-identifier (FK)
commented

B-335
file-originator data-submittal-identifier (FK)
on by
file-originator-office-address data-submittal-revision (FK)
APPENDIX B
MIL-STD-2549

file-identifier document-source-entity-identifier (FK)

file-creation-date document-identifier (FK)
file-creation-time document-type-code (FK)
document-representation-identifier (FK)
document-representation-revision (FK)
document-representation-originator.file-originator (FK)
document-representation-file-originator-office-address.file-originator-office-address (FK)
document-representation-file-identifier.file-identifier (FK)
document-representation-file-creation-date.file-creation-date (FK)
document-representation-file-creation-time.file-creation-time (FK)
comment-file-originator.file-originator (FK)
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

comment-file-originator-office-address.(office-address,file-originator-office-address) (FK)
comment-file-identifier.file-identifier (FK)
FIGURE 26CON6 comment-file-creation-date.file-creation-date (FK)
CDRL-SUBMITTAL REVIEW comment-file-creation-time.file-creation-time (FK)
data-submittal-revision-disposition-status-code (FK)
technical-disposition-recommendation
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK

ACOADD950 enterprise-administrative-contracting-office-address-text 0081 FK, O

ACONAM950 administrative-contracting-officer-human-name 0069 FK, O
PCOADD950 enterprise-procuring-contracting-office-address-text 0081 FK, O
PCONAM950 product-procuring-contracting-officer-human-name 0069 FK, O
SELADD950 performing-enterprise-contact-office-address-text 0081 FK, O
SELENT950 performing-enterprise-identifier 0052 FK
SELNAM950 contractor-human-name 0069 FK, O
CONNAM950 agreement-name 0071
FEETYP950 contract-document-fee-type-code 0227

B.5.25.2. Table 951, Contract modifications (CONMOD). This table is a subtype of Table NUMDOCREV/021,
consisting of those documents for which the value of document-type-code (DOCTYP010) is 'CONTRCT'. Due to
parallel categorization, this table is a de facto child of Table CONDOC/950. It contains the revision history for a
contract.

a. Because this table is a de facto child of Table 950, the concatenation of ENTIDN002, DOCNUM020, and
DOCTYP010 inherited from Table NUMDOCREV/021, must be a contract-document-identifier existing
in Table 950; therefore, they are concatenated and assume the identity CONIDN950, contract-document-
identifier.

b. Attribute document-generic-revision-identifier (DOCREV011) inherited from Table 021 assumes the role
contract-document-revision-identifier (CONMOD951).

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

CDADAF951 contract-modification-document-address-list-affect-code 0198

CDRLAF951 contract-modification-document-contract-data-requirements- 0198
list-affect-code
CONAFF951 contract-modification-document-delivery-schedule-affect- 0198
code
CONDAT951 agreement-effective-date 0082 M
CONDES951 contract-document-modification-description-text 0140
DISSAF951 contract-modification-document-distribution-statement- 0198
affect-code
OATTAF951 contract-modification-document-other-attachment-affect- 0198
code
OTEXAF951 contract-modification-document-other-exhibit-affect-code 0198
PERIOD951 contract-document-performance-period-months-quantity 0145 M
SCHAAF951 contract-modification-document-schedule-a-affect-code 0198

B-336
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SCHBAF951 contract-modification-document-schedule-b-affect-code 0198

SCHCAF951 contract-modification-document-schedule-c-affect-code 0198
SCHDAF951 contract-modification-document-schedule-d-affect-code 0198
SCHEAF951 contract-modification-document-schedule-e-affect-code 0198
SCHFAF951 contract-modification-document-schedule-f-affect-code 0198
SCHGAF951 contract-modification-document-schedule-g-affect-code 0198
SCHHAF951 contract-modification-document-schedule-h-affect-code 0198
SCHIAF951 contract-modification-document-schedule-i-affect-code 0198
SCHJAF951 contract-modification-document-schedule-j-affect-code 0198
SCHKAF951 contract-modification-document-schedule-k-affect-code 0198
SOWAFF951 contract-modification-document-work-statement-affect-code 0198

B.5.25.3. Table 952, Contract exhibit definition (CONEX). This table contains the unique identification of the
contract exhibits.

Code Data Element Title DED Key

CONEXH952 contract-document-exhibit-identifier 0007 K
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

CIIDEN695 configuration-item-product-identifier 0111 FK, O

APPRDT952 contract-data-requirement-list-document-form-approval- 0082
process-disposition-action-status-date
APPRNM952 contract-data-requirement-list-document-form-approver- 0069
human-name
CDRLCT952 contract-data-requirement-list-document-form-category-code 0201
PREPDT952 contract-data-requirement-list-document-form-preparation- 0082
process-completion-date
PREPNM952 contract-data-requirement-list-document-form-preparer- 0069
human-name

B.5.25.4. Table 953, Contract data requirements list definition (CDRL). This table contains the contract data
requirements list sequence numbers.

a. The value of contract-data-requirement-list-document-item-effective-cut--off-date (CDR11D953) and

contract-data-requirement-list-document-item-effective-cut--off-event-delta-text (CDR11T953) cannot
both be nonblank.

b. The value of contract-data-requirement-list-document-item-initial-delivery-due-code (CDR12C953) and

contract-data-requirement-list-document-item-initial-submittal-due-date (CDR12D953) cannot both be
nonblank.

B-337
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

c. The value of contract-data-requirement-list-document-item-subsequent-delivery-due-code (CDR13C953)

and contract-data-requirement-list-document-item-subsequent-submittal-due-date (CDR13D953) cannot
both be nonblank.

d. If the value of data-item-description-document-identifier (CDR040953) is nonblank, this field must

default to the value of document-name (DOCTIT011) in Table 011 which is associate with the value of
CDR040953.

e. The attributes data-item-description-document-alphanumeric-identifier (DIDNUM650), data-item-

description-document-type-code (DIDTYP650), document-generic-revision-identifier (DOCREV011), and
document-source-enterprise-identifier (SRCENT020) inherited from Table 651 are concatenated and
assume the role data-item-description-document-identifier (CDR040953). (See Appendix C for
concatenation order.)

f. The attributes enterprise-identifier (ENTIDN002) and enterprise-office-name (OFFSYM941) inherited

from Table 941 are concatenated and assume the role tasking-activity-enterprise-technical-monitor-
division-identifier (CDR060953). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 K
identifier
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

CDR040953 data-item-description-document-identifier 0230 FK, O

CDR060953 tasking-activity-enterprise-technical-monitor-division- 0228 FK
identifier
DISCOD014 document-distribution-statement-code 0014 FK
SHPIDN960 shipping-document-alphanumeric-identifier 0003 FK, O
SOWIDN957 work-statement-document-identifier 0229 FK, O
CDR020953 contract-data-requirement-list-document-item-name 0008 M
CDR030953 contract-data-requirement-list-document-item-subsidiary- 0008
name
CDR050953 document-reference-citation-identifier 0075
CDR070953 shipping-document-requirement-code 0202 M
CDR080953 contract-data-requirement-list-document-item-approval- 0203 M
requirement-code
CDR100953 contract-data-requirement-list-document-item-submission- 0197 M
frequency-code
CDR11D953 contract-data-requirement-list-document-item-effective-cut-- 0082
off-date
CDR11T953 contract-data-requirement-list-document-item-effective-cut-- 0161
off-event-delta-text
CDR12C953 contract-data-requirement-list-document-item-initial- 0233
delivery-due-code
CDR12D953 contract-data-requirement-list-document-item-initial- 0082
submittal-due-date

B-338
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

CDR13C953 contract-data-requirement-list-document-item-subsequent- 0233

delivery-due-code
CDR13D953 contract-data-requirement-list-document-item-subsequent- 0082
submittal-due-date
CDR160953 contract-data-requirement-list-document-item-remark-text 0204
CDR170953 contract-data-requirement-list-document-item-price-group- 0199
code
CDR180953 contract-data-requirement-list-document-item-price-amount 0200
SUFXCD953 contract-data-requirement-list-document-item-modification- 0205
symbol-code

B.5.25.5. Table 954, Contract data item submittal identification (DATASUB). This data contains the unique
identification of the CDRL submittals for each CDRL sequence number.

a. The value of contract-data-submittal-document-effective-cut--off-event-delta-text (COFFDL954) and

contract-data-submittal-document-effective-cut--off-date (COFFDT954) cannot both be nonblank.

b. The value of contract-data-submittal-document-initial-delivery-event----delta-text (INDUDL954) and

contract-data-submittal-document-initial-delivery-calendar-due-date (INDUDT954) cannot both be
nonblank.

c. The value of contract-data-submittal-document-subsequent-delivery-event--delta-text (SBDUDL954) and

contract-data-submittal-document-subsequent-delivery-calendar-due-date (SBDUDT954) cannot both be
nonblank.

d. A process-event-code (EVNCOD961) inherited from Table 961 is concatenated with a period-length-

quantity and period-unit-code to form the contract-data-submittal-document-effective-cut--off-event-delta-
text (COFFDL954).

e. A process-event-code (EVNCOD961) inherited from Table 961 is concatenated with a period-length-

quantity and period-unit-code to form the contract-data-submittal-document-initial-delivery-event--delta-
text (INDUDL954).

f. A process-event-code (EVNCOD961) inherited from Table 961 is concatenated with a period-length-

quantity and period-unit-code to form the contract-data-submittal-document-subsequent-delivery-event--
delta-text (SBDUDL954).

g. The value of SBDUDT954 and SBDUDL954 must both be blank if the value of contract-data-submittal-
document-submittal-type-code (SUBTYP954) is 'F'.

h. The attributes enterprise-identifier (ENTIDN002) and enterprise-office-name (OFFSYM941) inherited

from Table 941 are concatenated and assume the role performing-activity-enterprise-technical-monitor-
division-identifier (PRFTEK954). (See Appendix C for concatenation order.)

i. The attributes enterprise-identifier (ENTIDN002) and enterprise-office-name (OFFSYM941) inherited

from Table 941 are concatenated and assume the role tasking-activity-enterprise-technical-monitor-
division-identifier (TSKTEK954). (See Appendix C for concatenation order.)

B-339
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

CDRLSB954 contract-data-submittal-document-identifier 0020 K
CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

COFFDL954 contract-data-submittal-document-effective-cut--off-event- 0161 FK, O

delta-text
INDUDL954 contract-data-submittal-document-initial-delivery-event-- 0234 FK, O
delta-text
PRFTEK954 performing-activity-enterprise-technical-monitor-division- 0228 FK, O
identifier
SBDUDL954 contract-data-submittal-document-subsequent-delivery- 0234 FK, O
event--delta-text
SHPIDN960 shipping-document-alphanumeric-identifier 0003 FK, O
TSKTEK954 tasking-activity-enterprise-technical-monitor-division- 0228 FK
identifier
COFFDT954 contract-data-submittal-document-effective-cut--off-date 0082
INDUDT954 contract-data-submittal-document-initial-delivery-calendar- 0082
due-date
SBDUDT954 contract-data-submittal-document-subsequent-delivery- 0082
calendar-due-date
SUBRMK954 contract-data-submittal-document-remark-text 0153
SUBTIT954 contract-data-submittal-document-name 0008
SUBTYP954 contract-data-submittal-document-submittal-type-code 0150

B.5.25.6. Table 955, Contract data item submittal revision (DATASUBREV). This table contains the CDRL
submittal revision identifiers. (Note: this is distinct from the revisions of the documents being submitted; this
refers to the iterations of the CDRL as a CDRL item in the CDRL approval process.)

Code Data Element Title DED Key

SUBREV955 contract-data-submittal-document-revision-identifier 0099 K
CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

SUBCOM955 contract-data-submittal-document-remark-text 0153

SUBDUE955 contract-data-submittal-document-calendar-due-date 0082

B-340
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.5.25.7. Table 956, Contract data submittal/approval status (CDRLSTAT). This table contains the CDRL
submittal status for each submittal/resubmittal.

a. The contract-data-item-document-resubmittal-requirement-identifier (RSUBSR956) is nonblank only

when the value of contract-data-item-approval-process-disposition-action-status-code (SUBSTA956) in
the REFERENCED instance has a value of 'DISAPP' and the value of contract-data-item-document-
resubmittal-code (RSUBRQ972) in Table 972 is 'Y'.

b. If the value of contract-data-item-approval-process-disposition-action-status-code (SUBSTA956) is not

'INWK', then the value of contract-document-data-item-submittal-dispositioner-human-name
(DISNAM956) must be nonblank.

c. The attributes contract-data-requirement-list-document-item-sequence-identifier (CDRLIN953), contract-

data-submittal-document-identifier (CDRLSB954), contract-document-exhibit-identifier (CONEXH952),
contract-document-identifier (CONIDN950), contract-document-revision-identifier (CONMOD951), and
contract-data-submittal-document-revision-identifier (SUBREV955) inherited from Table 956 are
concatenated and assume the role contract-data-submittal-document-resubmittal-requirement-identifier
(RSUBSR956). (See Appendix C for concatenation order.)

Code Data Element Title DED Key

SUBSTA956 contract-data-submittal-document-approval-process- 0021 K
disposition-status-code
CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK

RSUBSR956 contract-data-submittal-document-resubmittal-requirement- 0235 FK, O

identifier
DISNAM956 contract-data-submittal-document-dispositioner-human-name 0069
STATDT956 contract-data-submittal-document-approval-process- 0082 M
disposition-status-date

B.5.25.8. Table 957, Statement of work definition (SOW). This table contains the contract-unique
identification of the statement of work and cross references to the document identification system.

a. The attributes document-identifier (DOCIDN010), document-generic-revision-identifier (DOCREV011),

document-type-code (DOCTYP010), and document-source-entity-identifier (SRCIDN010) inherited from
Table 019 are concatenated and assume the role work-statement-document-identifier (SOWIDN957).
(See Appendix C for concatenation order.)

B-341
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
SOWIDN957 work-statement-document-identifier 0229 FK

B.5.25.9. Table 958, Contract line item number correlation with contract exhibit(s) (CLIN-CONEX). This
table correlates the contract line items with the contract exhibits.

Code Data Element Title DED Key

CLINUM959 contract-document-line-item-identifier 0017 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

B.5.25.10. Table 959, Contract line item number definition (CLIN). This table identifies the contract line items.

Code Data Element Title DED Key

CLINUM959 contract-document-line-item-identifier 0017 K
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

CLINDS959 contract-document-line-item-description-text 0109

CLINQT959 contract-document-line-item-quantity 0144
UOMCOD959 product-measurement-unit-code 0054

B.5.25.11. Table 960, Contract data item shipping document/payment identification (DD250). This table
contains the identification of each DD Form 250 which is prepared in support of contract deliveries. (Note: if a
letter of transmittal is used, it should be included in the list of documents in the submittal package. See Table
SUBPKG/965.)

Code Data Element Title DED Key

SHPIDN960 shipping-document-alphanumeric-identifier 0003 K
CONIDN950 contract-document-identifier 0015 FK

CLINUM959 contract-document-line-item-identifier 0017 FK

CONMOD951 contract-document-revision-identifier 0120 FK
SHPAMT960 shipping-document-dollar-amount 0146
SHPDAT960 product-shipping-date 0082
SHPDES960 shipping-document-shipped-item-description-text 0147
SHPQTY960 shipping-document-shipped-item-quantity 0148

B-342
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SHPSTA960 shipping-document-process-disposition-status-code 0021

UOMCOD960 product-measurement-unit-code 0054

B.5.25.12. Table 961, Contract events (milestones) (CONEVENT). This table contains user-defined contract
event codes which are used in conjunction with the data item delivery due dates to update the delivery dates as
event dates change.

Code Data Element Title DED Key

EVNCOD961 process-event-code 0018 K
CONIDN950 contract-document-identifier 0015 FK

PRSEDT961 process-event-end-date 0082

PRSNAM961 process-event-name 0156
PRSSDT961 process-event-start-date 0082

B.5.25.13. Table 962, Contract distribution (CONDIST). This table contains the addressees who receive copies
of the contract.

Code Data Element Title DED Key

CONIDN950 contract-document-identifier 0015 FK
DIVADD942 enterprise-office-address-text 0081 FK

DOCQTY962 document-quantity 0158

B.5.25.14. Table 963, Contract data submittal distribution requirements (CDRLSUBDIST). This table contains
the contract data item distribution addressees.

a. Attribute enterprise-office-address-text (DIVADD942) inherited from Table 942 assumes the role
enterprise-file-review-office-address-text (FILADD963).

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
FILADD963 enterprise-file-review-office-address-text 0081 FK

B.5.25.15. Table 964, CDRL distribution format and quantity (CDRLQTY). This table contains the distribution
format and quantity requirements for each addressee for each CDRL submittal.

B-343
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

DELMTH964 data-product-delivery-method-code 0139 K
CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
FILADD963 enterprise-file-review-office-address-text 0081 FK

DOCQTY964 document-quantity 0158 M

B.5.25.16. Table 965, CDRL submittal package (SUBPKG). This table correlates the identity of the actual
document representations delivered as part of the CDRL data item delivery. If a letter of transmittal is used, it is
included in this package.

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK

DOCREV011 document-generic-revision-identifier 0243 FK

B.5.25.17. Table 966, CDCA-released document representations associated with CDRL submittal package (REP-
CDCASUBPKG). This table is a subtype of Table SUBPKG/865 containing the subset of the data in Table 965
consisting of those submittal items which are submitted to, or by, the CDCA.

a. Because this table is a subtype of Table 965, for each instance in this table, the same value for document-
revision-identifier (DOCREV011) must be in the parent instances found in all inheritance paths; that is,
the same value of DOCREV011 must be found through the path Table 966-> Table 965, and through the
path Table 966->Table 806->Table 803-> Table 801.

Code Data Element Title DED Key

B-344
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

CONIDN950 contract-document-identifier 0015 FK

CONMOD951 contract-document-revision-identifier 0120 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK

REPIDN800 document-representation-identifier 0207 FK

REPREV801 document-representation-revision-identifier 0208 FK
REPSTA803 document-representation-release-process-disposition-status- 0021 FK
code

B.5.25.18. Table 967, Application activity released document representations associated with CDRL submittal
package (REP-AASUBPKG). This table is a subtype of Table SUBPKG/965. It contains a subset of the data in
Table 965 consisting of those submittal items which are submitted to a tasking activity by an application activity.

a. Because this table is a subtype of Table 965, for each instance in this table, the same value for document-
revision-identifier (DOCREV011) must be in the parent instances found in all inheritance paths; that is,
the same value of DOCREV011 must be found through the path Table 967 -> Table 965, and through the
path Table 967 -> Table 863 -> Table 861.

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
DOCIDN010 document-identifier 0122 FK
DOCTYP010 document-type-code 0004 FK
SRCIDN010 document-source-entity-identifier 0033 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK

APPACT033 application-activity-enterprise-division-identifier 0228 FK

B.5.25.19. Table 968, Contract-reviewer comments to a CDRL submittal package (CDRL-REDLINE). This
table contains the identification of the file(s) containing comments or redline annotations to the document
representation revision being reviewed as part of the CDRL data item approval process by the CDRL approval
activity . These files are cross-referenced to, but separate and distinct from, the original files being reviewed.

B-345
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

a. For each instance in this table, the same value of document-revision-identifier (DOCREV011) must be in
the parent instances in all inheritance paths; that is, the same value of document-revision-identifier must
be reached through the path Table 968 -> Table 965, and through the path Table 968 -> Table 802 ->
Table 801.

b. The reviewer of the data item submittal is the originator of the comment file.

c. Attribute enterprise-file-origination-office-address-text (FILADD900) inherited from Table 900 and

enterprise-file-review-office-address-text (FILADD963) inherited from Table 963 must have the same
value and merge to assume the role enterprise-comment-file-origination-office-address-text
(CFILAD968).

d. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-date (CFILDT968).

e. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 900 assumes the role
electronic-document-comment-file-identifier (CFILID968).

f. Attribute file-originator-human-name (FILORG900) inherited from Table 900 assumes the role comment-
file-originator-human-name (CFILOR968).

g. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 900 assumes the role
electronic-document-comment-file-creation-time (CFILTM968).

h. Attribute enterprise-file-origination-office-address-text (FILADD900) inherited from Table 802 assumes

the role enterprise-document-file-origination-office-address-text (RFILAD968).

i. Attribute electronic-document-file-creation-date (FILDAT900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-date (RFILDT968).

j. Attribute electronic-document-file-identifier (FILIDN900) inherited from Table 802 assumes the role
electronic-document-representation-file-identifier (RFILID968).

k. Attribute file-originator-human-name (FILORG900) inherited from Table 802 assumes the role
document-file-originator-human-name (RFILOR968).

l. Attribute electronic-document-file-creation-time (FILTIM900) inherited from Table 802 assumes the role
electronic-document-representation-file-creation-time (RFILTM968).

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CFILAD968 enterprise-comment-file-origination-office-address-text 0081 FK
CFILOR968 comment-file-originator-human-name 0069 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK

B-346
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

DOCIDN010 document-identifier 0122 FK

DOCTYP010 document-type-code 0004 FK
REPIDN800 document-representation-identifier 0207 FK
REPREV801 document-representation-revision-identifier 0208 FK
RFILAD968 enterprise-document-file-origination-office-address-text 0081 FK
RFILDT968 electronic-document-representation-file-creation-date 0082 FK
RFILID968 electronic-document-representation-file-identifier 0206 FK
RFILOR968 document-file-originator-human-name 0069 FK
RFILTM968 electronic-document-representation-file-creation-time 0160 FK
SRCIDN010 document-source-entity-identifier 0033 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK

CFILDT968 electronic-document-comment-file-creation-date 0082 FK

CFILID968 electronic-document-comment-file-identifier 0206 FK
CFILTM968 electronic-document-comment-file-creation-time 0160 FK
SUBSTA956 contract-data-submittal-document-approval-process- 0021 FK
disposition-status-code
TECHCD968 document-approval-process-technical-recommended- 0021
disposition-status-code
TECHDT968 disposition-process-technical-recommendation-completion- 0082
date

B.5.25.20. Table 969, CDRL submittals 'in-work' (CDRL-INWORK). This table is a subtype of Table
CDRLSTAT/956. It contains the subset of the data in Table 956 consisting of those CDRL submittals which have
achieved a contractual approval status of in-work ('INWK'). This is the default status.

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK
SUBSTA956 contract-data-submittal-document-approval-process- 0021 FK
disposition-status-code

B.5.25.21. Table 970, CDRL submittals in 'submit' status (CDRL-SUBMIT). This table is a subtype of Table
CDRLSTAT/956 which contains the subset of the data in Table 956 consisting of those CDRL submittals which
have achieved a contractual approval status of submit ('SUBMIT'), indicating that they have been submitted to the
customer for review and disposition.

B-347
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK
SUBSTA956 contract-data-submittal-document-approval-process- 0021 FK
disposition-status-code

FSUSDT970 contract-data-submittal-document-customer-final- 0082 M

disposition-suspense-date
TSUSDT970 contract-data-submittal-document-customer-technical- 0082 M
review-completion-suspense-date

B.5.25.22. Table 971, CDRL submittals in 'approved' status (CDRL-APPR). This table is a subtype of Table
CDRLSTAT/956 which contains the subset of the data in Table 956 consisting of those CDRL submittals which
have achieved a contractual approval status of approve ('APV').

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK
SUBSTA956 contract-data-submittal-document-approval-process- 0021 FK
disposition-status-code

B.5.25.23. Table 972, CDRL submittals in 'disapproved' status (CDRL-DISAPP). This table is a subtype of
Table CDRLSTAT/956. It contains the subset of the data in Table 956 consisting of those CDRL submittals which
have achieved a contractual approval status of disapproved ('DISAPV').

Code Data Element Title DED Key

CDRLIN953 contract-data-requirement-list-document-item-sequence- 0005 FK
identifier
CDRLSB954 contract-data-submittal-document-identifier 0020 FK
CONEXH952 contract-document-exhibit-identifier 0007 FK
CONIDN950 contract-document-identifier 0015 FK
CONMOD951 contract-document-revision-identifier 0120 FK
SUBREV955 contract-data-submittal-document-revision-identifier 0099 FK

B-348
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

SUBSTA956 contract-data-submittal-document-approval-process- 0021 FK

disposition-status-code

RSUBDT972 contract-data-submittal-document-resubmittal-due-date 0082

RSUBRQ972 contract-data-submittal-document-resubmittal-code 0159 M

B.5.25.24. Tables 973 and 974. Reserved.

B.5.25.25. Table 975, Agreement types (AGREEMENT-TYPE). This table is part of the DOD Enterprise Data
Model (EDM). It contains codes for various types of agreements, such as contracts, treaties, memorandums of
understanding, etc.

Code Data Element Title DED Key

AGRTYP975 agreement-type-code 0167 K

B.5.25.26. Table 976, Agreements (AGREEMENT). This table is part of the DOD EDM and contains the
identification of agreements.

Code Data Element Title DED Key

AGRIDN976 agreement-identifier 0152 K

AGRTYP975 agreement-type-code 0167 FK

B.5.25.27. Table 977, Contracts (CONTRACT). This table is a subtype of table AGREEMENT/976 consisting
of those agreements which are contracts.

a. Attribute agreement-identifier (AGRIDN976) inherited from Table 976 assumes the role contract-
document-alphanumeric-identifier (CONNUM977).

Code Data Element Title DED Key

CONNUM977 contract-document-alphanumeric-identifier 0226 FK

B.6. NOTES

(This section contains information of a general or explanatory nature that may be helpful, but is not
mandatory.)

B.6.1. Intended use. This document is intended to define the conceptual database requirements and related
business constraints necessary for the DoD CM AIS. Any organization which provides data to, or extracts data
from the CM AIS must format their data/queries to support this database schema. Implementation of databases
conforming to this conceptual schema may be accomplished using relational databases, object-oriented databases,
or any other approach.

B-349
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

B.6.2. Reference documents. The following documents have been used as references in preparing this appendix
and may provide additional information.

DEPARTMENT OF DEFENSE PUBLICATIONS:

DDRS Department of Defense Data Repository System (Data Element Listing as of
2/28/95)
DoD 4120.3-M Defense Standardization Manual
DoDI 4140.54 Serial Number Tracking of Selected Parts, Components, and End Items
DoD 5010.12-L Acquisition Management Systems and Data Requirements Control List
(AMSDL)
DoDM 5010.12-M Procedures for Acquisition and Management of Technical Data
DoD 5220.22-M Industrial Security Manual for Safeguarding Classified Information
DoD 8320.1-M-1 Data Element Standardization Procedures
MIL-HDBK-59 Department of Defense Computer-aided Acquisition and Logistic Support
(CALS) Program Implementation Guide
MIL-STD-100 Engineering Drawing Practices
MIL-STD-196 Joint Electronics Type Designation System
MIL-STD-787 Joint Optical Range Instrumentation Type Designation System
MIL-STD-498 Software Development and Documentation
MIL-STD-787 Joint Optical range Instrumentation type Designation System
MIL-STD-961 Defense Specifications
MIL-STD-962 Defense Standards and Handbooks
MIL-STD-963 Data Item Descriptions (DIDs), Preparation of
MIL-STD-1168 Ammunition Lot Numbering
MIL-STD-1345(NAVY) Test Requirements Document, Preparation of
MIL-STD-1464(AR) Army Nomenclature System
MIL-STD-1519(USAF) Test Requirements Document, Preparation of
MIL-STD-1661(OS) MARK and MOD Nomenclature System
MIL-STD-1662(OS) Ordnance Alteration (ORDALT) Instructions, Preparation of
DOD-STD-1700 Data Management Program
MIL-STD-1806 Marking Technical Data Prepared by or for the Department of Defense
MIL-STD-1812 Type Designation, Assignment and Method for Obtaining
MIL-STD-2039 Field Changes and Field Change Kits, Preparation of
DOD-STD-2140(SH) Machinery Alteration (MACHALT) Instructions, Preparation of (Metric)
DOD-STD-2167 Defense System Software Development
MIL-T-9885 Time Compliance Technical Orders: for Surface-Launched Missiles, Space
Vehicles and Related Support Equipment, Preparation of
MIL-T-31000 Technical Data Package, General Specification for
MIL-M-38784 Manuals, Technical: General Style and Format Requirements
MIL-T-38804 Time Compliance Technical Orders, Preparation of
MIL-PRF-49506 Logistics Management Information
MIL-M-81748 Manuals, Technical, Rapid Action Changes, Requirements for Preparation of
MIL-D-81992(AS) Directives, Technical; Preparation of
DOD-T-86000(NS) Test Requirements Document, Preparation of

DEPARTMENT OF COMMERCE PUBLICATIONS:

NATIONAL INSTITUTE OF STANDARDS & TECHNOLOGY:
FIPS-PUB-184 Integration Definition for Information Modeling (IDEF1X)

B-350
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

GENERAL SERVICES ADMINISTRATION PUBLICATIONS:

FEDERAL SUPPLY SERVICE:
Federal Standardization Manual

DEFENSE LOGISTICS AGENCY PUBLICATIONS:

DLA Handbook H4/H8 Index of Commercial and Government Entity Codes

DEPARTMENT OF THE ARMY PUBLICATIONS:

AR 25-30 The Army Integrated Publishing and Printing Program
AR 70-50 Military Aerospace Equipment
AR 750-1 Army Materiel Maintenance Policy and Retail Maintenance Operations
DA PAM 738-750 Functional Users Manual for the Army Maintenance Management System
(TAMMS)
DA PAM 738-751 Functional Users Manual for the Army Maintenance Management System--
Aviation (TAMMS-A)

DEPARTMENT OF THE AIR FORCE PUBLICATIONS:

AFR 82-1 Military Aerospace Equipment
TO 00-5-16 Software Managers Manual: USAF Computer Program Identification
Numbering (CPIN) System
TO 00-5-17 Users Manual: USAF Computer Program Identification Numbering (CPIN)
System
TO 00-20-2 Maintenance Data Collection

ARMY ARMAMENT RESEARCH, DEVELOPMENT & ENGINEERING CENTER PUBLICATIONS:

CMPM (Draft) Assignment of Procurement Activity Numbers (PAN)

NAVAL AIR SYSTEMS COMMAND PUBLICATIONS:

AR-41 Aeronautical Requirements: Technical Directive Development and Acquisition
of Integrated Logistic Support for Aeronautical Weapon System Changes
00-25-300 Technical Directive System
NAVAIRINST 4130.1C Naval Air Systems Command Configuration Management Policy
NAVSEAINST 4130.15 Antisubmarine Warfare (ASW) Engineering Change Accomplishment Program
(ECAP) for SONAR and Acoustic Warfare Equipment
OPNAVINST 4720.2E Policy for Fleet Modernization Program (FMP)
NAVAIRINST 5215.8C The NAVAIR Technical Directive System
NAVAIRINST 8800.4D Military Aerospace Equipment

U.S. INDUSTRY STANDARDS:

ANSI/EIA 476-A-1987 Source and Date Code Marking
ANSI Y14.1-1980 Drawing Sheet Size and Forms
ASME Y14.24-1989 Types and Applications of Engineering Drawings
ANSI/ASME Parts Lists, Data Lists and Index Lists
Y14.34M-1989
ASME Y14.35M-1992 Revision of Engineering Drawings and Associated Lists
ANSI Y32.2-1975 Graphic Symbols for Electrical and Electronic Diagrams
ANSI Y32.16-1975 Reference Designations for Electrical and Electronics Parts and Equipments
ANSI/IEEE Std 830-84 IEEE Standard for Software Requirements Specifications
ANSI/IEEE Std 1042-87 IEEE Guide to Software Configuration Management
EIA IS-649 Configuration Management
EIA J-STD-016.0 U.S. implementation of ISO/IEC 12207 International Standard (Standard for
Information Technology --Software life cycle processes

B-351
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX B

INTERNATIONAL STANDARDS:
ISO 10303-203 Product Data Representation and Exchange- Part 203, Application Protocol:
Configuration Controlled Design
ISO 10007 Quality Management--Guidelines for Configuration Management
ISO/IEC 12207 Standard for Information Technology--Software life cycle processes
NATO STANAG 4159 NATO Material Configuration Management Policy and Procedures for
Multinational Joint Projects

B-352
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

CONFIGURATION STATUS ACCOUNTING (CSA) DATA ELEMENT DEFINITIONS

C.1. GENERAL

C.1.1. Scope. This appendix establishes the Configuration Status Accounting (CSA) standard data elements which
constitute the minimum requirements for a Government CM AIS. This appendix prescribes the format of data
elements required by Appendix B. This appendix fulfills the requirement in MIL-STD-974 for a CALS data
dictionary. This appendix is a mandatory part of the standard. The information contained herein is intended for
compliance.

C.2. APPLICABLE DOCUMENTS

C.2.1. There are no sub-tier documents required for implementation of this appendix. The source documents for
the various requirements in this appendix (including those cited for legacy data) are included for information only.

C.3. DEFINITIONS

C.3.1. Acronyms used in this Appendix. The acronyms in Section 3 of this standard apply to this appendix. In
addition, the following acronyms are used in the text of this appendix:

B Bitmap
C Character
D Date
Dec Decimal places
F Full justification
FLPT Floating point decimal number
FXPT Fixed point decimal number
I Integer
Jst Justification
L Left justified
R Right justified
S [Character] String

C.3.2. Definitions used in this Appendix. The definitions in Section 3 of this standard apply to this appendix. In
addition, the following definitions apply to this appendix:

a. Data element domain value. 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 a data record. A code is used
instead of the data item itself, to conserve space on the data records and to facilitate machine processing.
For example, under the data element "Baseline Impact Code", the corresponding Data Items "Functional
Baseline", "Allocated Baseline" and "Product Baseline" are represented by the data codes "F", "A" and "P",
respectively.

b. Field format. A specification for the size, type positional justification, and decimal placement of a data
element field, or sub-field thereof as described below:

C-1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

(1) Type. A specification of the character type, wherein:

"B" specifies that the input is a bit-map

"C" specifies that the input is any combination of ASCII characters (unless otherwise noted in the DED
definition)

"D" specifies that the input is a valid date

"FLPT" specifies that the input is a floating-point real number (for example: 3.25E-5, -4.2625E+8,
5.3x1012, etc.)

"FXPT" specifies that the input is a fixed-point number, or integer (for example: 1.3, -2.59, 0.003, etc.)

"I" specifies that the input is an integer number (for example: 1, 2, 3, -5, etc.)

"S" specifies that the input is a string of separately defined fields which have been concatenated in the
order indicated.

(2) Justification (Jst). 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).

(3) Decimal placement (Dec). Specifies the number of character positions to the right of the assumed
decimal point when the data element is a floating-point or fixed-point number.

(4) Size. The number of character positions in the data element. In the event the length is variable, the
maximum length is specified.

c. Generic element name. A generic element is the part of a data element that establishes a structure
(maximum size/length, data type, etc.) and limits the allowable set of values of a data element. A generic
element has no functional or application context other than to define a general class of data and ensure
consistency in structure and domain. The domain (permissible set of values) of a generic element may be
specific or general. Within this document, generic data element names include a brace-pair ({}) to indicate
the omitted prime word.

d. Role name. See Appendix B.

e. Standard element name. Any data element which does not include braces ({}) in the element name is a
standard data element. In some cases, a standard data element also serves as the basis for establishing the
structure (maximum size/length, data type, etc.) and limits the allowable set of values of a data element for a
collection of standard data elements with unique roles names. Basic Standard Data Elements have a
function or context of their own, and also serve to define a general class of data and ensure consistency in
structure and domain. The domain (permissible set of values) of a basic standard data element may be
specific or general. Each role-named standard data element includes additional modifier(s) in its title and
may be smaller in size or have a domain of values which is a subset of the domain of the basic standard data
element with which it is associated. The size and/or domain of a role-named standard data element are
shown with the role-named standard data element definition only when they are different from the values
shown for the basic standard data element.

C-2
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

C.4. GENERAL REQUIREMENTS

C.4.1. Standard CSA data elements. Required status accounting information shall be expressed in terms of the
standard CSA data elements listed in the detailed requirements of this appendix. Substitutes, alternatives, or
variations shall not be used.

C.4.2. Supplemental CSA data elements. Additional CSA data elements and related features may be added as
required and approved by the Government. All supplemental data elements which are to be submitted to the
Government CM AIS must comply with Government data element standardization procedures.

C.5. DETAILED REQUIREMENTS

DED DED TITLE or ROLE TITLE Type Jst Dec Size

Definition and Domain Values (if any)

0001 enterprise-defense-logistics--assigned-identification-code C F 5
The standard code which represents and/or denotes a commercial or Government entity or enterprise
that manufactures and/or controls the design of items supplied to a Government Agency. United States
and Canadian entities are designated by a commercial and government entity (CAGE) code while North
Atlantic Treaty Organizations (NATO) are designated by an NATO Supply Code for Manufacturing
(NSCM). Codes are listed in the Defense Logistics Agency Handbook H4/H8. This code has formerly
been known as the Code Identification (Code Ident) and the Federal Supply Code for Manufacturers
(FSCM). Must be digits or uppercase letters excluding the letters I and O. (Source of requirements:
DLA Handbook H4/H8.) (This is equivalent to MIL-PRF-49506 DED 0140.) This DED is used in the
following Table(s): 003, 006, 007.

This DED is used as part of the following DED string(s):

DED Title
0245 modification-kit-product-identifier

assembled-product-design-enterprise-defense-logistics--assigned-
identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify the
design of an assembly. This DED is used in the following Table(s): 236, 239, 293, 364.

assembly-manufacturer-enterprise-defense-logistics--assigned-
identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify the
manufacturer of an assembly. This DED is used in the following Table(s): 242, 243, 244.

component-index-list-drawing-document-source-enterprise-defense-
logistics--assigned-identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify an
index list drawing which is a component on a higher level index list drawing. This DED is used in the
following Table(s): 067.

C-3
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

component-material-manufacturer-enterprise-defense-logistics--assigned-
identification-code
The CAGE code which represents and/or denotes a company or organization which is the manufacturer
of a material used as a component in a higher level part or material. This DED is used in the following
Table(s): 243, 244, 527.

component-part-manufacturer-enterprise-defense-logistics--assigned-
identification-code
The CAGE code which represents and/or denotes a manufacturer of a part which is used as a component
of a higher level assembly or in a regrouped lot of parts. This DED is used in the following Table(s):
242, 524.

controlling-index-list-drawing-document-source-enterprise-defense-
logistics--assigned-identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify the
index list drawing which is the primary, or parent, index list drawing in a relationship with lower-tier
index list drawings. This DED is used in the following Table(s): 067.

current-deviation-request-document-source-enterprise-defense-logistics--
assigned-identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify the
Request for Deviation which is the most current request in a list of recurring requests for deviation.
This DED is used in the following Table(s): 359.

design-enterprise-defense-logistics--assigned-identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify the
document, software or part. This DED is used in the following Table(s): 050, 051, 052, 053, 054, 055,
056, 060, 061, 062, 063, 064, 065, 066, 069, 070, 071, 080, 081, 082, 083, 084, 085, 086, 087, 100,
101, 102, 103, 104, 105, 106, 107, 110, 111, 153, 161, 163, 164, 174, 205, 208, 212, 219, 220, 221,
222, 223, 224, 225, 226, 227, 234, 235, 237, 238, 256, 258, 270, 284, 285, 286, 287, 302, 304, 306,
307, 311, 312, 313, 315, 316, 317, 318, 319, 320, 321, 323, 324, 325, 326, 327, 362, 363, 432, 433,
434, 435, 436, 437, 508, 509, 510, 511, 620.

deviation-request-document-source-enterprise-defense-logistics--assigned-
identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify the
Request for Deviation. This DED is used in the following Table(s): 350, 351, 352, 353, 354, 355, 356,
357, 358, 360, 361, 362, 363, 364, 365, 366, 370, 372, 373, 374, 535, 672, 706.

document-source-enterprise-defense-logistics--assigned-identification-
code
The CAGE code which identifies the enterprise whose number is used to identify a document. This
DED is used in the following Table(s): 022, 023, 430, 431, 704.

C-4
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

engineering-change-proposal-document-source-enterprise-defense-
logistics--assigned-identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify an
ECP. This DED is used in the following Table(s): 250, 251, 252, 253, 254, 255, 256, 257, 258, 259,
260, 261, 262, 263, 264, 265, 266, 270, 271, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294,
295, 300, 303, 309, 310, 311, 312, 313, 359, 454, 493, 565, 615, 616, 617, 618, 619, 620, 671, 682,
705.

index-list-drawing-document-design-enterprise-defense-logistics--
assigned-identification-code
The CAGE code which represents and/or denotes the design agency or organization whose number is
used to identify an index list drawing. This DED is used in the following Table(s): 068.

manufacturer-enterprise-defense-logistics--assigned-identification-code
The CAGE code which represents and/or denotes the organization that has manufactured or is
manufacturing the item. This DED is used in the following Table(s): 237, 238, 239, 240, 241, 245,
256, 259, 260, 284, 293, 361, 362, 363, 364, 366, 491, 494, 515, 516, 517, 518, 519, 520, 521, 522,
523, 525, 526, 528, 529, 530, 531, 532, 533, 534, 535, 536.

parts-list-drawing-document-source-enterprise-defense-logistics--
assigned-identification-code
The CAGE code which represents and/or denotes the design organization whose number is used to
identify a parts list drawing. This DED is used in the following Table(s): 068.

primary-engineering-change-proposal-document-source-enterprise-
defense-logistics--assigned-identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify the
ECP which is the primary ECP in a group of related ECPs which must be implemented together. This
DED is used in the following Table(s): 251.

prior-deviation-request-document-source-enterprise-defense-logistics--
assigned-identification-code
The CAGE code which represents and/or denotes the organization or enterprise of a prior approved
Request for Deviation for a recurring problem. This DED is used in the following Table(s): 359.

regrouped-lot-manufacturer-enterprise-defense-logistics--assigned-
identification-code
The CAGE code which represents and/or denotes the manufacturer that has formed a new lot of a part
(or material) by consolidating small lots of the same part (or material). This DED is used in the
following Table(s): 524, 527.

remanufacturer-enterprise-defense-logistics--assigned-identification-code
The CAGE code which represents and/or denotes a manufacturer that re-worked or re-manufactured a
part (or material) into a different part number (or material identifier) from as originally manufactured,

C-5
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

for example: part XYZ-1 re-manufactured into an XYZ-2. Re-manufacture in this context includes the
formation of a new part by forming a composite lot of different part numbers (for example: linking
20mm tracer rounds into 20mm HEI ammunition belts) and formation of a new lot of the same part
number (or material) by consolidation of small lots. This DED is used in the following Table(s): 531,
532, 533, 534.

revision-notice-document-source-enterprise-defense-logistics--assigned-
identification-code
The CAGE code which represents and/or denotes the organization whose number is used to identify a
NOR. This DED is used in the following Table(s): 300, 301, 302, 303, 304, 305, 306, 307, 308, 309,
310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327.

0002 enterprise-acronym-identification-code C L 7
The identifying abbreviation or acronym code which represents and/or denotes an administrative
structure with a mission. This is the standard abbreviation, or other acronym, which represents and/or
denotes an organization or enterprise. Frequently, this is associated with an organization that does not
have a CAGE code. A partial list of values is included below; additional values may be used with prior
approval of the office responsible for this document. Field size for particular role names is dependent
upon the acronyms associated with the role name. (Source of requirements: DODISS, DoD 8320.1-M-
1.)

This DED is used as part of the following DED string(s):

DED Title
0230 data-item-description-document-identifier

The valid domain values for this element are as follows:

Domain
Value Meaning
A2LA American Association for Laboratory Accreditation
AA The Aluminum Association, Inc
AASHTO American Association of State Highway and Transportation Officials
AATCC American Association of Textile Chemists and Colorists
ABMA American Bearing Manufacturers Association
ABS American Bureau of Shipping
ACI American Concrete Institute
ACS American Chemical Society
AECMA Association Europeenne des Construceurs de Materiel Aerospace
AGA American Gas Association
AGMA American Gear Manufacturers Association
AI Asphalt Institute
AIA American Institute of Architects
AIA/NAS Aerospace Industries Association of America
AIAA American Institute of Aeronautics and Astronautics
AICHE American Institute of Chemical Engineers
AIIM Association for Information & Image Management
AISC American Institute of Steel Construction
AISI American Iron and Steel Institute
ANS American Nuclear Society

C-6
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

ANSI American National Standards Institute

API American Petroleum Institute
AREA American Railway Engineering Association
ARI Air-conditioning and Refrigeration Institute
ARINC Aeronautical Radio, Incorporated
ASA Acoustical Society of America
ASAE The American Society of Agricultural Engineers
ASCE American Society of Civil Engineers
ASHRAE American Society of Heating, Refrigerating & Air-Conditioning Engineers Inc.
ASI Italian Space Agency
ASME American Society of Mechanical Engineers
ASNT American Society for Nondestructive Testing
ASQC American Society for Quality Control
ASSE American Society of Sanitary Engineering
ASTM American Society for Testing and Materials
AWS American Welding Society, Inc
AWWA American Water Works Association
BHMA Builders Hardware Manufacturers Association, Inc
CED Civil Engineering Data
CGA Compressed Gas Association, Inc.
CSA Canadian Space Agency
CTI Cooling Tower Institute
DCAA (United States) Defense Contract Audit Agency
DFAS (United States) Defense Finance and Accounting Service
DIA (United States) Defense Intelligence Agency
DIN Deutsche Industrie Numer
DIS (United States) Defense Investigative Agency
DISA (United States) Defense Information Systems Agency
DLA (United States) Defense Logistics Agency
DLSA (United States) Defense Legal Services Agency
DMA (United States) Defense Mapping Agency
DNA (United States) Defense Nuclear Agency
DOC (United States) Department of Commerce
DOD (United States) Department of Defense
DOE (United States) Department of Energy
DOT (United States) Department of Transportation
DRPA (United States) Defense Research Projects Agency
DSAA (United States) Defense Security Assistance Agency
ECMA European Computer Manufacturers Association
EIA Electronics Industries Association
ESA European Space Agency
FAA Federal Aviation Agency
GA Gypsum Association
GPA Gas Processors Association
GSA U.S. General Services Administration
IEC International Electrotechnical Commission
IEEE Institute for Electrical and Electronic Engineering
IESNA Illuminating Engineering Society of North America
IFI Industrial Fasteners Institute
IPC The Institute for Interconnecting and Packaging Electronic Circuits

C-7
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

IRS U.S. Internal Revenue Service

ISA Instrument Society of America
ISHM International Society for Hybrid Microelectronics
ISO International Standards Organization
MSS Manufacturers Standardization Society of the Valve and Fittings Industry, Inc
NACE National Association of Corrosion Engineers
NASA National Aeronautics & Space Administration
NASDA Japanese Space Agency
NATO North Atlantic Treaty Organization
NAVAIR (United States) Naval Air Systems Command
NAVSEA (United States) Naval Sea Systems Command
NEBB National Environmental Balancing Bureau
NEMA National Electrical Manufacturers Association
NFP National Fluid Power Association
NFPA National Fire Protection Association
NISO National Information Standards Organization
NIST National Institute of Standards and Technology
NSA (United States) National Security Agency/Central Security Service
NTIAC Nondestructive Testing Information Analysis Center
OSD (United States) Office of the Secretary of Defense
OSHA (United States) Occupational Safety and Health Agency
PFI Pipe Fabrication Institute
PLASTEC Plastic Technical Evaluation Center
PPI Plastic Pipe Institute
RAC Reliability Analysis Center
RSA Russian Space Agency
RWMA Resistance Welder Manufacturers Association
SAE Society of Automotive Engineers
SDIO (United States) Strategic Defense Initiative Organization
SEMI Semiconductor Equipment and Materials International
SJI Steel Joist Institute
SMACNA Sheet Metal and Air Conditioning Contractors' National Association, Inc
SMPTE Society of Motion Picture & Television Engineers
SSPC Steel Structures Painting Council
UK-MOD United Kingdom, Ministry of Defense
UL Underwriters Laboratories Inc.
USA (United States) Department of the Army
USAF (United States) Department of the Air Force
USCG United States Coast Guard
USMC (United States) Department of the Marine Corps
USN (United States) Department of the Navy

controlling-document-source-enterprise-acronym-identification-code
The identifying abbreviation or acronym code which represents and/or denotes an organization or
enterprise which has issued the controlling document which a different organization or enterprise has
identified by an alias and issued. This DED is used in the following Table(s): 402.

C-8
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

design-enterprise-acronym-identification-code
The acronym which represents and/or denotes the organization which is the design organization for a
part or material. The design organization assigns the number which is used to identify the part or
material. A partial list of values is included below; additional values may be used with prior approval of
the office responsible for this document. This DED is used in the following Table(s): 201, 211, 420,
421, 422, 423.

The valid domain values for this element are as follows: AIA/NAS, ANSI, ASME, CGA, DOD, IFI,
SAE.

engineering-change-proposal-cost--affected-enterprise-acronym-
identification-code
The identifying abbreviation or acronym code which represents and/or denotes a U.S. defense
department service branch affected by the ECP. This DED is used in the following Table(s): 252.

The valid domain values for this element are as follows: USA, USAF, USMC, USN.

international-document-source-enterprise-acronym-identification-code
The acronym which represents and/or denotes the international organization whose number (or other
identifier) is used to identify the document. A partial list of values is included below; additional values
may be used with prior approval of the office responsible for this document. This DED is used in the
following Table(s): 404.

The valid domain values for this element are as follows: AECMA, ECMA, ESA, IEC, ISHM, ISO,
NATO.

international-enterprise-acronym-identification-code
The identifying abbreviation or acronym code which represents and/or denotes an international
organization. A partial list of values is included below; additional values may be used with prior
approval of the office responsible for this document. This DED is used in the following Table(s): 039.

The valid domain values for this element are as follows: AECMA, ECMA, ESA, IEC, ISHM, ISO,
NATO.

non--united-states-government-document-source-enterprise-acronym-
identification-code
The acronym which represents and/or denotes the non-U.S. government organization whose number is
used to identify the document. A partial list of values is included below; additional values may be used
with prior approval of the office responsible for this document. This DED is used in the following
Table(s): 405.

The valid domain values for this element are as follows: ASI, CSA, NASDA, RSA, UK-MOD.

non--united-states-government-enterprise-acronym-identification-code
The identifying abbreviation or acronym code which represents and/or denotes a government
organization other than a U.S. Government organization. A partial list of values is included below;

C-9
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

additional values may be used with prior approval of the office responsible for this document. This
DED is used in the following Table(s): 037.

The valid domain values for this element are as follows: ASI, CSA, NASDA, RSA, UK-MOD.

non--united-states-nongovernment-document-source-enterprise-acronym-
identification-code
The acronym which represents and/or denotes the non-U.S. industry, professional, or other
nongovernment organization whose number is used to identify the document. A partial list of values is
included below; additional values may be used with prior approval of the office responsible for this
document. This DED is used in the following Table(s): 406.

The valid domain values for this element are as follows: DIN.

non--united-states-nongovernment-enterprise-acronym-identification-
code
The identifying abbreviation or acronym code which represents and/or denotes an industry organization
other than a US industry organization. A partial list of values is included below; additional values may
be used with prior approval of the office responsible for this document. This DED is used in the
following Table(s): 038.

The valid domain values for this element are as follows: DIN.

united-states-defense-component-enterprise-acronym-identification-code
A code which denotes or represents the branch of the U.S. military. (This is equivalent to MIL-PRF-
49506 DED 1180.) This DED is used in the following Table(s): 552.

The valid domain values for this element are as follows: USA, USAF, USMC, USN.

united-states-defense-department-document-source-enterprise-acronym-
identification-code
The acronym which represents and/or denotes the U.S. DOD organization whose number is used to
identify the document. A partial list of values is included below; additional values may be used with
prior approval of the office responsible for this document. This DED is used in the following Table(s):
262, 291, 408, 462, 464, 465, 466, 467, 468, 469, 470, 471, 472, 552, 554, 557, 558, 559, 560, 562,
563, 565, 570, 571, 572, 573, 610, 611, 612, 613, 614, 615, 616, 617, 618, 619.

The valid domain values for this element are as follows: DCAA, DFAS, DIA, DIS, DISA, DLA, DLSA,
DMA, DNA, DOD, DRPA, DSAA, USA, USAF, USMC, USN.

united-states-defense-department-enterprise-acronym-identification-code
The identifying abbreviation or acronym code which represents and/or denotes a United States
Department of Defense organization or enterprise. A partial list of values is included below; additional
values may be used with prior approval of the office responsible for this document. This DED is used in
the following Table(s): 007, 034.

C-10
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

The valid domain values for this element are as follows: DCAA, DFAS, DIA, DIS, DISA, DLA, DLSA,
DMA, DNA, DOD, DRPA, DSAA, USA, USAF, USMC, USN.

united-states-defense-secretariate-document-source-enterprise-acronym-
identification-code
The identifying abbreviation or acronym code which represents and/or denotes an organization within
the U.S. Office of the Secretary of Defense which is the source of the identifier of a document. A partial
list of values is included below; additional values may be used with prior approval of the office
responsible for this document. This DED is used in the following Table(s): 410, 411, 412, 413.

The valid domain values for this element are as follows: DOD, OSD, SDIO.

united-states-government-nondefense-document-source-enterprise-
acronym-identification-code
The acronym which represents and/or denotes the nondefense U.S. government organization whose
number is used to identify the document, software or part. A partial list of values is included below;
additional values may be used with prior approval of the office responsible for this document. This
DED is used in the following Table(s): 409.

The valid domain values for this element are as follows: DOC, DOE, DOT, GSA, IRS, NSA, OSHA,
USCG.

united-states-government-nondefense-enterprise-acronym-identification-
code
The identifying abbreviation or acronym code which represents and/or denotes a government
organization or enterprise which is not part of the department of defense. A partial list of values is
included below; additional values may be used with prior approval of the office responsible for this
document. This DED is used in the following Table(s): 035.

The valid domain values for this element are as follows: DOE, DOT, FAA, GSA, IRS, NASA, NIST,
NSA, OSHA, SDIO, USCG.

united-states-navy-command-enterprise-acronym-identification-code
The identifying abbreviation or acronym code which represents and/or denotes a specific Command of
the U.S. Navy. This DED is used in the following Table(s): 559.

The valid domain values for this element are as follows: NAVAIR, NAVSEA.

united-states-nongovernment-document-source-enterprise-acronym-
identification-code
The acronym which represents and/or denotes the U.S. industry, professional, or other nongovernment
organization whose number is used to identify the document. A partial list of values is included below;
additional values may be used with prior approval of the office responsible for this document. This
DED is used in the following Table(s): 407.

C-11
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

The valid domain values for this element are as follows: A2LA, AA, AASHTO, AATCC, ABMA,
ABS, ACI, ACS, AGA, AGMA, AI, AIA, AIA/NAS, AIAA, AICHE, AIIM, AISC, AISI, ANS, ANSI,
API, AREA, ARI, ARINC, ASA, ASAE, ASCE, ASHRAE, ASME, ASNT, ASQC, ASSE, AWS,
AWWA, BHMA, CED, CTI, EIA, GA, GPA, IEEE, IESNA, IFI, IPC, ISA, MSS, NACE, NEBB,
NEMA, NFP, NFPA, NISO, NTIAC, PFI, PLASTEC, PPI, RAC, SAE, SEMI, SJI, SMACNA,
SMPTE, SSPC, UL.

united-states-nongovernment-enterprise-acronym-identification-code
The identifying abbreviation or acronym code which represents and/or denotes an industry standards
organization or enterprise. A partial list of values is included below; additional values may be used with
prior approval of the office responsible for this document. This DED is used in the following Table(s):
036.

0003 document-alphanumeric-identifier C L 32
The document identifier which represents the unique identification number of, and primary reference to,
a document. The field size of this data element has been set to allow for future growth; users should
refer to the appropriate source document to determine the field size currently allowed for a specific role.
(Note: this identifier may have a document series type embedded in it as the leading characters; for
example: AFM 30-30, FIPS 8130.1-M, STANAG 4159, CFR 49, AP 203, MIL-STD-2549, etc.) Only
uppercase letters, numbers, dash -(-), virgule (/), colon (:), decimal (.), parentheses (), and embedded
blank may be used. This DED is used in the following Table(s): 020, 021, 022, 023, 024, 025, 026,
027, 100, 101, 102, 104, 105, 107, 110, 111, 152, 153, 154, 208, 211, 219, 256, 258, 262, 270, 284,
287, 288, 291, 293, 304, 305, 310, 313, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 420,
422, 423, 430, 431, 432, 435, 436, 437, 440, 441, 464, 508, 509, 552, 554, 558, 559, 562, 563, 565,
570, 704.

This DED is used as part of the following DED string(s):

DED Title
0230 data-item-description-document-identifier
0192 material-document-identifier

assembly-engineering-drawing-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
an engineering drawing which is an assembly level engineering drawing reflecting the integrated
configuration of multiple components and materials. Must be uppercase letters (except O), numbers, or
dashes only; no other special characters allowed. This DED is used in the following Table(s): 220, 221,
222, 223, 224, 225, 226, 227, 316, 318, 319, 320, 321.

C-12
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

component-index-list-drawing-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
an index list drawing which is a component part of a higher-level index list drawing. Must be uppercase
letters (except O), numbers or dashes only; no other special characters allowed. This DED is used in
the following Table(s): 067.

controlling-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and controlling reference
to, an industry standard when a joint application exists. For example, the controlling document
identifier for an ANSI-adopted IEEE standard is the IEEE-assigned identifier. This DED is used in the
following Table(s): 402.

controlling-index-list-drawing-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
an index list drawing which is the primary, or parent, index list drawing in a relationship with lower-tier
index list drawings. Uppercase letters (except O), numbers, or dashes only; no other special characters
allowed. This DED is used in the following Table(s): 067.

current-deviation-request-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a Request for Deviation which is the most current request in a list of recurring requests for deviation.
Uppercase letters (except O), numbers, or dashes -(-) only; no other special characters allowed. This
DED is used in the following Table(s): 359.

data-item-description-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a data item description (DID). Must be in the form 'DI-X-#' or 'DI-XXX-#', where X is an alphabetic
character and # is a number between 1 and 99999. This DED is used in the following Table(s): 650,
651.

deviation-request-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a Request for Deviation. Must be uppercase letters (excluding O) or numbers; may include dash -(-);
must include the letter "D". This DED is used in the following Table(s): 350, 351, 352, 353, 354, 355,
356, 357, 358, 360, 361, 362, 363, 364, 365, 366, 370, 372, 373, 374, 535, 672, 706.

engineering-change-proposal-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
an Engineering Change Proposal document. Must be uppercase letters (except O), numbers or dashes -
(-). (This is equivalent to MIL-PRF-49506 DED 0120.) This DED is used in the following Table(s):
250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 270, 271, 284,
285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 300, 303, 309, 310, 311, 312, 313, 359, 454,
493, 565, 615, 616, 617, 618, 619, 620, 671, 682, 705.

C-13
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

engineering-drawing-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
an engineering drawing. Must be uppercase letters (except O), numbers, or dashes -(-); no other special
characters allowed. This DED is used in the following Table(s): 050, 051, 052, 053, 054, 060, 061,
062, 063, 064, 065, 066, 069, 070, 071, 080, 081, 082, 083, 084, 085, 086, 087, 160, 161, 162, 163,
164, 165, 166, 285, 286, 302, 306, 307, 311, 312, 315, 317, 323, 324, 325, 326, 327, 510, 511, 912.

index-list-drawing-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
an index list drawing. Uppercase letters (except O), numbers or dashes only; no other special
characters allowed. This DED is used in the following Table(s): 068.

modification-instruction-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a modification instruction. Must be uppercase letters (except O), numbers, or dashes -(-) only; no other
special characters allowed. This DED is used in the following Table(s): 462, 466, 469, 470, 471, 472.

parts-list-drawing-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a parts list drawing. Must be uppercase letters (except O), numbers, or dashes -(-) only; no other
special characters allowed. This DED is used in the following Table(s): 068.

primary-engineering-change-proposal-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
an ECP which is the primary ECP in a group of related ECPs which must be implemented together.
Must be uppercase letters (except O), numbers, and dashes -(-) only. This DED is used in the following
Table(s): 251.

prior-deviation-request-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a prior approved Request for Deviation for a recurring problem. Must be uppercase letters (except O)
or numbers only; no special characters allowed. This DED is used in the following Table(s): 359.

program--unique-specification-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a program-unique specification. This identifier includes the 'Part 1' or 'Part 2' suffix if applicable. Must
be uppercase letters (except O) or numbers only; no special characters allowed.

This DED is used as part of the following DED string(s):

DED Title
0149 revised-program--unique-specification-document-identifier

C-14
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

rapid-action-change-order-document-alphanumeric-identifier
The identifier which represents the unique identification of, and primary reference to, a Rapid Action
Change (RAC) Order. Must be uppercase letters (except O), numbers, or dashes -(-) only; no other
special characters allowed. This DED is used in the following Table(s): 464.

revision-notice-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a Notice of Revision (NOR). Must be uppercase letters (except O), numbers, dashes -(-), or decimals (.)
only. This DED is used in the following Table(s): 300, 301, 302, 303, 304, 305, 306, 307, 308, 309,
310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327.

shipping-document-alphanumeric-identifier
The document identifier which, in conjunction with the contract number, represents the unique
identification number of, and primary reference to, the DD Form 250 and consequently, each delivery
under a contract. Must be uppercase letters (except I and O) and numbers only. This DED is used in
the following Table(s): 953, 954, 960.

software-version-description-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a software version description document (VDD). Must be uppercase letters (except O), numbers, or
decimals (.) only. This DED is used in the following Table(s): 170, 180.

technical-manual-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a technical manual or technical order. Must be uppercase letters (except O), numbers, dash -(-),
decimal (.), or virgule (/). (This is equivalent to MIL-PRF-49506 DED 1370.)

This DED is used as part of the following DED string(s):

DED Title
0135 revised-technical-manual-document-identifier

united-states-air-force-technical-order-document-alphanumeric-identifier
The identifier which represents the unique identification of, and primary reference to, a U.S. Air Force
Technical Order or Manual, excluding Time-Compliance Technical Orders. Must be uppercase letters
(except O), numbers, virgule (/), dash -(-), and parenthesis (()). This DED is used in the following
Table(s): 560.

united-states-army-modification-work-order-document-alphanumeric-
identifier
The identifier which represents the unique identification of, and primary reference to, a modification
work order. Must be uppercase letters (except O), numbers, ampersand (&), and dash -(-). This DED is
used in the following Table(s): 467, 468.

C-15
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

united-states-army-technical-manual-document-alphanumeric-identifier
The identifier which represents the unique identification of, and primary reference to, a U.S. Army
Technical Manual. Must be uppercase letters (except O), numbers, ampersand (&), and dash -(-). This
DED is used in the following Table(s): 468, 557.

united-states-defense-handbook-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a military handbook issued by the U.S. DOD. Must be in the format 'MIL-HDBK-#####', where # is a
number. This DED is used in the following Table(s): 413.

united-states-defense-specification-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a military specification. Must be uppercase letters, numbers, virgule (/), or dash-(-) in the format 'MIL-
$-#####', 'MIL-$-#####/##', 'MIL-$$$-#####', or 'MIL-$$$-#####/##' where $ is a letter and # is a
number. This DED is used in the following Table(s): 412.

united-states-defense-standard-document-alphanumeric-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a military standard issued by the U.S. DOD. Must be uppercase letters (except O), numbers, virgule and
dash in the format MIL-STD-#####, where # is a number This DED is used in the following Table(s):
411.

united-states-naval-air-technical-directive-document-alphanumeric-
identifier
The identifier which represents the unique identification of, and primary reference to, a Technical
Directive issued by NAVAIR. It consists of a two-digit series identifier as defined in NAVAIR
Technical Manual 00-25-300, followed by a dash, followed by a four-digit number assigned sequentially
within each series identifier. See NAVAIR Technical Manual 00-25-300. This DED is used in the
following Table(s): 465.

0004 document-type-code C L 7
The standard code which represents and/or denotes a category or type of formal papers or records of
similar characteristics known as a document. This DED is used in the following Table(s): 010, 011,
019, 020, 021, 022, 023, 024, 025, 026, 027, 033, 040, 041, 042, 043, 044, 045, 046, 047, 048, 049,
050, 051, 052, 053, 054, 060, 061, 063, 080, 081, 083, 084, 086, 087, 100, 101, 102, 104, 105, 107,
111, 150, 151, 152, 153, 154, 157, 158, 159, 160, 161, 162, 171, 172, 185, 211, 212, 219, 223, 224,
226, 253, 256, 258, 266, 270, 271, 284, 287, 288, 293, 302, 304, 305, 306, 307, 310, 313, 322, 330,
332, 352, 357, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 420, 422, 423,
430, 431, 432, 435, 436, 437, 440, 441, 508, 509, 510, 511, 555, 556, 558, 559, 562, 563, 572, 573,
601, 610, 611, 612, 613, 614, 615, 616, 617, 618, 619, 670, 681, 704, 800, 801, 802, 803, 804, 805,
806, 807, 811, 812, 850, 851, 852, 853, 854, 855, 857, 858, 861, 862, 863, 864, 865, 866, 867, 910,
911, 912, 913, 914, 915, 917, 919, 926, 965, 966, 967, 968.

This DED is used as part of the following DED string(s):

C-16
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

DED Title
0230 data-item-description-document-identifier
0192 material-document-identifier
0124 product-baseline-top-level-document-identifier
0229 work-statement-document-identifier

The valid domain values for this element are as follows:

Domain
Value Meaning
ANALYS Analysis, data and deductive rationale for decisions which may or may not have
been reduced to a report
BOOK A book
CONTRCT Contract, purchase order or other procurement instrument, including delivery
orders under indefinite delivery contracts, orders under basic ordering
agreements, and calls under blanket purchase orders.
DID Data item description as defined in MIL-STD-963 or comparable commercial or
non-U.S. documents
DL Data list (associated with an engineering documentation package) as defined in
MIL-STD-100 or ANSI Y14.34M or comparable non-U.S. documents
DOCSUP Document supplement is any separately issued supplemental pages and/or
corrections to a document which can be used only in conjunction with another
document. (This includes technical manual changes and supplements, U.S. DOD
Defense specification and standard amendments, changes, notices, and
supplements, etc.)
DWG Engineering drawing as defined in MIL-STD-100 or ANSI Y14.24M or
comparable non-U.S. documents
ECP Engineering change proposal as defined herein, in EIA IS-649, ANSI/IEEE Std
6610.12, NATO STANAG 4159, or comparable commercial or non-U.S.
documents
IL Index list (associated with an engineering documentation package) as defined in
MIL-STD-100 or ANSI Y14.34M or comparable non-U.S. documents
MISC Miscellaneous document, not otherwise classified by CM (NOTE: Care must be
exercised to prevent this category from becoming a catch-all.)
MODINST Modification instructions direct that specific changes be made to specified assets
which are already in service. (These include such things as Modification Work
Orders, Time Compliance Technical Orders, Technical Directives, Rapid Action
Change Orders, Ship Alteration Instructions, etc.)
MODREQ Modification requests are used to request that assets already in service be
changed. (These include such things as Proposed Military Improvements,
Proposed Technical Improvements, etc.) (For contrast, see: ECP and RFD)
NOR Notice of revision (to an engineering drawing or program-unique specification)
as defined herein or comparable commercial or non-U.S. documents
P-SPEC Company and program-unique specifications for products, software, processes,
or material (as defined in MIL-STD-490, MIL-STD-961D, DOD-STD-2167,
MIL-STD-498 or comparable commercial or non-U.S. documents). For
contrast, see STDDOC.
PERIODL Periodical; any routinely published document of general information, such as a
newsletter, news bulletin, etc.
PL Parts list (associated with an engineering drawing) as defined in MIL-STD-100
or ANSI Y14.34M or comparable non-U.S. documents

C-17
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

PLNPROC Plans and procedures

REPORT Reports
RFD Request for deviation (or waiver) from the requirements of a design document
(for example: an engineering drawing or program-unique specification) as
defined herein, in EIA IS-649, ANSI/IEEE Std 610.12, NATO STANAG 4159,
or comparable commercial or non-U.S. government standard
STDDOC Specifications, standards, or other documents issued for the purpose of
standardizing, regulating, or codifying practices, procedures, processes, material,
etc. within a segment of a company, industry, or government. For example:
Military Specifications, Federal Standards, ISO Application Protocols, EIA
Bulletins, AECMA Documents, SAE Standard Practices, NATO Standard
NATO Agreements (STANAGs), etc. For contrast, see P-SPEC.
SVD Software version description document as defined in DOD-STD-2167, MIL-
STD-498, or comparable commercial or non-U.S. documents
SW Software code of any type, including source and executable applications and
copies of databases such as the Logistics Support Analysis Database,
Configuration Status Accounting Database, etc.
SWDOC Software documentation including all types of support documentation specified
in MIL-STD-498, DOD-STD-2167 or company equivalent; excludes software
documents which are included in other categories (such as software
specifications in P-SPEC, software test procedures in PLNPROC, etc.)
TECHMAN Army, Navy, Air Force, or Marine Corps technical manuals (or Air Force
Technical Orders) as defined in Mil-M-38784, NAVAIR 00-25-700, or
comparable commercial or non-U.S. documents
TRD Test requirements document as defined in MIL-STD-1345, MIL-STD-1519 or
DOD-T-86000(NS) or comparable commercial or non-U.S. documents

affected-document-type-code
A subset of document type codes which represents and/or denotes the type of document affected by a
NOR. This DED is used in the following Table(s): 301.

The valid domain values for this element are as follows: DWG, P-SPEC, PL, STDDOC.

component-document-type-code
The standard code which represents and/or denotes the type of document of a document listed as a
component of another document. For example a document listed in a data list drawing. This DED is
used in the following Table(s): 071.

The valid domain values for this element are as follows: DL, DWG, IL, MISC, P-SPEC, PL, STDDOC,
SVD, SW, TRD.

C-18
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

contract-document-type-code
A code which denotes that a document is a contract.

This DED is used as part of the following DED string(s):

DED Title
0015 contract-document-identifier

The valid domain values for this element are as follows: CONTRCT.

controlling-engineering-drawing-document-type-code
The code which represents and/or denotes the type of the engineering drawing which is the controlling,
or parent, drawing in a given relationship between an engineering drawings and other documents
referenced on the engineering drawing. This DED is used in the following Table(s): 082, 085.

The valid domain values for this element are as follows: DWG, PL.

data-item-description-document-type-code
The standard code which represents and/or denotes a data item description document. This DED is used
in the following Table(s): 650, 651.

The valid domain values for this element are as follows: DID.

data-list-drawing-document-type-code
The standard code which represents and/or denotes a data list drawing. This DED is used in the
following Table(s): 069, 070, 071.

The valid domain values for this element are as follows: DL.

deviation-request-document-type-code
The standard code which represents and/or denotes a Request for Deviation (RFD). This DED is used
in the following Table(s): 350, 351, 352, 353, 354, 355, 356, 357, 358, 359, 360, 361, 362, 363, 364,
365, 366, 370, 372, 373, 374, 535, 672, 706.

The valid domain values for this element are as follows: RFD.

engineering-change-proposal-document-type-code
The standard code which represents and/or denotes an Engineering Change Proposal (ECP). This DED
is used in the following Table(s): 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263,
264, 265, 266, 270, 271, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 300, 303, 309,
310, 311, 312, 313, 359, 454, 493, 565, 615, 616, 617, 618, 619, 620, 671, 682, 705.

The valid domain values for this element are as follows: ECP.

C-19
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

engineering-drawing-document-type-code
The standard code which represents and/or denotes an engineering drawing. This DED is used in the
following Table(s): 062, 064, 065, 069, 163, 164, 165, 166, 285, 311.

The valid domain values for this element are as follows: DWG.

index-list-drawing-document-type-code
The standard code which represents and/or denotes an index list drawing. This DED is used in the
following Table(s): 065, 066, 067, 068.

The valid domain values for this element are as follows: IL.

modification-instruction-document-type-code
The standard code which represents and/or denotes a modification instruction document. This DED is
used in the following Table(s): 460, 461, 462, 463, 464, 465, 466, 467, 468, 469, 470, 471, 472, 490,
491, 492, 493, 494, 536, 560.

The valid domain values for this element are as follows: MODINST.

modification-request-document-type-code
The standard code which represents and/or denotes a modification request document. This DED is used
in the following Table(s): 450, 451, 452, 453, 454, 460.

The valid domain values for this element are as follows: MODREQ.

parts-list-drawing-document-type-code
The standard code which represents and/or denotes a separate parts list drawing. This DED is used in
the following Table(s): 062, 064, 068, 286, 312.

The valid domain values for this element are as follows: PL.

primary-engineering-change-proposal-document-type-code
The standard code which represents and/or denotes the fact that the document is the primary ECP in a
group of related ECPs which must be implemented together. This DED is used in the following
Table(s): 251.

The valid domain values for this element are as follows: ECP.

program--unique-specification-document-type-code
The standard code which represents and/or denotes a program-unique specification. This DED is used
in the following Table(s): 110, 620.

The valid domain values for this element are as follows: P-SPEC.

C-20
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

referenced-document-type-code
The standard code which represents and/or denotes the type of document which is cited as a reference in
a document. This DED is used in the following Table(s): 082, 085, 110.

The valid domain values for this element are as follows: DID, DL, DWG, IL, P-SPEC, PL, PLNPROC,
REPORT, STDDOC, SW, SWDOC, TRD.

revision-notice-document-type-code
The standard code which represents and/or denotes a Notice of Revision (NOR). This DED is used in
the following Table(s): 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, 315,
316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327.

The valid domain values for this element are as follows: NOR.

software-document-type-code
The standard code which represents and/or denotes a software program or database. This DED is used
in the following Table(s): 163, 164, 165, 166, 230, 231, 232, 233.

The valid domain values for this element are as follows: SW.

software-support-document-type-code
The standard code which represents and/or denotes documents which support software design, testing or
use. Requirements documents are specifically excluded. (See also: program--unique-specification-
document-type-code.) This DED is used in the following Table(s): 186, 187.

The valid domain values for this element are as follows: SWDOC.

software-version-description-document-type-code
The standard code which represents and/or denotes a software version description document (VDD).
This DED is used in the following Table(s): 170, 180.

The valid domain values for this element are as follows: SVD.

supplemental-document-type-code
The standard code which represents and/or denotes a document which is a supplemental document. This
DED is used in the following Table(s): 620.

The valid domain values for this element are as follows: DOCSUP.

technical-manual-document-type-code
A code which represents and/or denotes a technical manual as described in Mil-M-38784 or equivalent.
This DED is used in the following Table(s): 262, 291, 461, 464, 468, 550, 551, 552, 553, 554, 556,
557, 560, 565, 570, 571, 572, 573, 610, 611, 612, 613, 614, 615, 616, 617, 618, 619.

The valid domain values for this element are as follows: TECHMAN.

C-21
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0005 contract-data-requirement-list-document-item-sequence- C L 6
identifier
A unique sequential identifier within a contract exhibit that identifies a single Data Item requirement.
This element can include exhibit subline item identification letters. It consists of an exhibit identifier
followed by sequentially assigned alphanumeric characters. (If an exhibit subline item identification is
used it will immediately follow the sequential numbers as a two character suffix.) Must be uppercase
letters (except I or O) or numbers; the first 1 or 2 characters must be a valid exhibit identifier. The
exhibit subline item identification letters can be blank; however, if nonblank, they must be uppercase
letters (except I or O). (Source of requirements: DFAR 204.7105 (c), DoDM 5010.12-M.) This DED
is used in the following Table(s): 953, 954, 955, 956, 963, 964, 965, 966, 967, 968, 969, 970, 971, 972.

This DED is used as part of the following DED string(s):

DED Title
0235 contract-data-submittal-document-resubmittal-requirement-identifier

0006 document-lead-activity-indicator-code C F 1
A code which denotes whether the document number is assigned by the primary controlling service (lead
activity) for the document, or if the document number is an alias assigned by a using activity. The lead
activity document identifier is always the first one to appear on the top of each page of the document.
(Source of requirements: MIL-M-38784.) This DED is used in the following Table(s): 550.

The valid domain values for this element are as follows:

Domain
Value Meaning
L Lead activity
U Using activity

0007 contract-document-exhibit-identifier C L 2
The unique document identifier that represents an exhibit to a particular contract. Must be uppercase
letters excluding the letters I and O. (Source of requirements: DFAR 204.7105(b).) This DED is used
in the following Table(s): 952, 953, 954, 955, 956, 958, 963, 964, 965, 966, 967, 968, 969, 970, 971,
972.

This DED is used as part of the following DED string(s):

DED Title
0235 contract-data-submittal-document-resubmittal-requirement-identifier

0008 *document-name C L 240

The name (or title) of a document. Must be a printable ASCII character or embedded space. (Source of
requirements: DDRS element 7,125, MIL-STD-100, MIL-STD-961.) This DED is used in the
following Table(s): 011, 040, 041, 042, 043, 044, 045, 046, 047, 048, 049.

C-22
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

contract-data-requirement-list-document-item-name
The title of a specific CDRL line item. This DED is used in the following Table(s): 953.

contract-data-requirement-list-document-item-subsidiary-name
The subtitle of a specific CDRL line item. This DED is used in the following Table(s): 953.

contract-data-submittal-document-name
The text of the title or of a brief description of a particular submittal, for example, June Progress Report,
Preliminary Test Report, etc. This is usually the same as, or very similar to, the CDRL Subtitle in Block
3, DD Form 1423/1423-1/2. This DED is used in the following Table(s): 954.

0009 document-alphanumeric-revision-identifier C R 3
The identifier which represents the specific revision, in a series of revisions, to a document or a portion
of the document (that is, sheet) to indicate that the document has been modified or changed. The
designator will normally be sequentially assigned. The default field size is three characters; however, in
some instances only two characters apply. Must be uppercase letters, numbers or dash. The letter O
shall not be used. (Source of requirements: ANSI Y14-24M, MIL-STD-100, MIL-STD-961, MIL-
STD-962.) (This is equivalent to MIL-PRF-49506 DED 1120.) This DED is used in the following
Table(s): 051, 054, 055, 056, 061, 063, 066, 070, 080, 081, 083, 084, 086, 087, 101, 105, 107, 111,
208, 219, 220, 221, 222, 223, 224, 225, 226, 227, 285, 286, 287, 302, 304, 306, 307, 311, 312, 313.

component-index-list-drawing-document-alphanumeric-revision- Size: 2
identifier
The identifier which represents the specific revision, in a series of revisions, to an index list which is a
component of a higher-level document. Must be uppercase letters (except I, O, Q, X and Z), numbers
or dash. This DED is used in the following Table(s): 067.

controlling-engineering-drawing-document-alphanumeric-revision- Size: 2
identifier
The identifier which represents the specific revision, in a series of revisions, to an engineering drawing
which is the controlling document in a relationship with another document. Must be uppercase letters
(except O), numbers, or dash -(-). This DED is used in the following Table(s): 082, 085.

controlling-index-list-drawing-document-alphanumeric-revision- Size: 2
identifier
The identifier which represents a specific revision, in a series of revisions to, an index list drawing
which is the controlling, or parent, index list drawing in a relationship with lower-tier index list
drawings. Must be uppercase letters (excluding O), numbers, or dash -(-). This DED is used in the
following Table(s): 067.

C-23
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

data-list-drawing-document-alphanumeric-revision-identifier Size: 2
The identifier which represents the specific revision, in a series of revisions, to a data list drawing. Must
be uppercase letters (except O), numbers, or dash -(-). This DED is used in the following Table(s):
071.

deviation-request-document-alphanumeric-revision-identifier
The identifier which represents the specific revision, in a series of revisions, to a Request for Deviation.
Limited to a dash -(-) or an 'R' followed by 01 through 99 (for example: R01, R02, etc.). This DED is
used in the following Table(s): 351, 352, 353, 354, 355, 356, 357, 358, 359, 360, 361, 362, 363, 364,
365, 366, 370, 372, 373, 374, 535, 706.

document-superseded-alphanumeric-revision-identifier
The identifier which represents the specific revision, in a series of revisions, to a document. This
identifier is used in contrast to the new document revision which is assigned as the result of ECP
approval. Must be uppercase letters, numbers or dash -(-). The letter O shall not be used. This DED is
used in the following Table(s): 271.

engineering-change-proposal-document-alphanumeric-revision-identifier
The identifier which represents the specific revision, in a series of revisions, to an ECP. Limited to a
dash -(-) or an 'R' followed by 01 through 99 (for example: R01, R02, etc.). This DED is used in the
following Table(s): 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266,
271, 284, 289, 290, 291, 292, 293, 294, 295, 303, 309, 493, 565, 615, 616, 617, 618, 619, 705.

engineering-drawing-document-current-alphanumeric-revision-identifier Size: 2
The identifier which represents the specific revision, in a series of revisions, to an engineering drawing.
This identifier is used in contrast to the drawing revision which is assigned as a result of ECP approval.
Must be uppercase letters (except O), numbers, or dash -(-). This DED is used in the following
Table(s): 052.

engineering-drawing-document-sheet-alphanumeric-revision-identifier Size: 2
The identifier which represents the specific revision, in a series of revisions, to a specific sheet of a
multi-sheet engineering drawing. Must be uppercase letters (except O), numbers or dash -(-). This
DED is used in the following Table(s): 052.

graphic-engineering-drawing-document-alphanumeric-revision-identifier Size: 2
The identifier which represents the specific revision, in a series of revisions, to a specific sheet of a
multi-sheet graphic drawing (that is, a drawing which does not have an integral part list). Must be
uppercase letters (except O), numbers or dash -(-). This DED is used in the following Table(s): 064.

index-list-drawing-document-alphanumeric-revision-identifier Size: 2
The identifier which represents the specific revision, in a series of revisions, to an index list drawing.
Must be uppercase letters (except O), numbers, or dash -(-). This DED is used in the following
Table(s): 068.

C-24
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

parts-list-drawing-document-alphanumeric-revision-identifier Size: 2
The identifier which represents the specific revision, in a series of revisions, to a parts list drawing.
Must be uppercase letters, numbers, or dash -(-). The letter O shall not be used. This DED is used in
the following Table(s): 064, 068.

program--unique-specification-document-alphanumeric-revision- Size: 2
identifier
The identifier which represents the specific revision, in a series of revisions, to a program-peculiar
specification. Must be uppercase letters (except I, O, Q, X and Z), numbers or dash -(-). This DED is
used in the following Table(s): 110.

This DED is used as part of the following DED string(s):

DED Title
0149 revised-program--unique-specification-document-identifier

revision-notice-document-alphanumeric-revision-identifier
The identifier which represents the specific revision, in a series of revisions, to a Notice of Revision.
Limited to a dash -(-) or an 'R' followed by 01 through 99; as in R01 - R99. This DED is used in the
following Table(s): 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, 315, 316,
317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327.

0010 document-security-classification-code C L 4
The standard security classification code which represents and/or denotes a level of classification of the
contents of media (for example, documents, files, equipment, etc.) in any of its forms. (Source of
requirements: DoD 5120.22-M, DoD 5200.1-R, DoD 8320.1-M-1.) This DED is used in the following
Table(s): 012.

The valid domain values for this element are as follows:

Domain
Value Meaning
C Confidential
FOUO For Official Use Only
NC NATO Confidential
NCA NATO Confidential Atomal
NR NATO Restricted
NS NATO Secret
NSA NATO Secret Atomal
NTS NATO Top Secret
NTSA NATO Top Secret Atomal
S Secret
TS Top Secret
U Unclassified

C-25
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

document-current-security-classification-code
The standard security classification code which represents and/or denotes the current level of
classification of the contents of media (for example, documents, files, equipment, etc.) in any of its
forms. This DED is used in the following Table(s): 011, 900.

document-downgrade-security-classification-code
The standard security classification code which represents and/or denotes the classification level, lower
than the current classification level, to which the classified material is to be reclassified upon occurrence
of a specified event or date. This DED is used in the following Table(s): 011, 900.

0011 document-security-classification-name C L 25
A name, term or phrase which defines the security classification of the contents of a document. (Source
of requirements: DoD 5200.1-R, DoD 5220.22-M, DoD 8320.1-M-1.) This DED is used in the
following Table(s): 012.

The valid domain values for this element are as follows:

Domain
Value Meaning
CONFIDENTIAL The designation indicating that unauthorized disclosure of
information or material could be reasonably expected to cause
damage to the national security
FOR-OFFICIAL-USE-ONLY The designation of unclassified material, the dissemination of
which, should be limited to a 'need to know' basis
NATO-CONFIDENTIAL The designation indicating that unauthorized disclosure of
information or material could be reasonably expected to cause
damage to NATO security
NATO-CONFIDENTIAL-ATOMAL The designation indicating that unauthorized disclosure of
information or material concerning the NATO atomic program
could be reasonably expected to cause damage to NATO security
NATO-RESTRICTED The designation indicating that disclosure of the information or
material should be limited to a 'need to know' basis, but is
otherwise unclassified.
NATO-SECRET The designation indicating that the unauthorized disclosure of
information or material could reasonably be expected to cause
serious damage to NATO security
NATO-SECRET-ATOMAL The designation indicating that the unauthorized disclosure of
information or material concerning the NATO atomic program
could reasonably be expected to cause serious damage to the
NATO security
NATO-TOP-SECRET The designation indicating that the unauthorized disclosure of
information or material could reasonably be expected to cause
grave damage to NATO security
NATO-TOP-SECRET-ATOMAL The designation indicating that the unauthorized disclosure of
information or material concerning the NATO atomic program
could reasonably be expected to cause grave damage to NATO
security

C-26
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

SECRET The designation indicating that the unauthorized disclosure of

information or material could reasonably be expected to cause
serious damage to the national security
TOP-SECRET The designation indicating that the unauthorized disclosure of
information or material could reasonably be expected to cause
grave damage to the national security
UNCLASSIFIED The designation indicating that the disclosure of information or
material will not impact security

0012 document-copyright-code C F 1
A code that denotes the restrictions on the use of delivered items and data which were
manufactured/procured under license from another organization or design activity. (Source of
requirements: DFAR 52.277-7013.) This DED is used in the following Table(s): 011, 013, 900.

The valid domain values for this element are as follows:

Domain
Value Meaning
C Copyrighted
G Copyrighted with United States government use authorized
N Not copyrighted

0013 document-copyright-text C L 160

The narrative text that describes the contractor's copyright statement and use restrictions related to the
document or data as required by DFAR 52.227-7013. Used with document-copyright-code. Must be a
printable ASCII character, space, tab, line feed, and carriage return. (Source of requirements: DFAR
52.277-7013.) This DED is used in the following Table(s): 013.

0014 document-distribution-statement-code C F 3
The standard distribution code which represents and/or denotes the type of distribution statement,
including the reason, that is affixed to the document or viewable file to indicate the authorized
circulation or dissemination of the information contained within the item. (Source of requirements:
DoDD 5230.24, DoDD 5230.25, DoDD 5230.9.) This DED is used in the following Table(s): 011,
014, 900, 953.

The valid domain values for this element are as follows:

Domain
Value Meaning
A00 Statement A, unlimited
B02 Statement B, limited to U.S. Government to prevent Premature Dissemination
B03 Statement B, limited to U.S. Government due to Critical Technology
B04 Statement B, limited to U.S. Government due to Foreign Government
Information
B05 Statement B, limited to U.S. Government due to Proprietary Information
B06 Statement B, limited to U.S. Government due to Test and Evaluation

C-27
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

B07 Statement B, limited to U.S. Government due to Contractor Performance

Evaluation
B08 Statement B, limited to U.S. Government due to Software Documentation
B09 Statement B, limited to DoD due to specific authority
B10 Statement B, limited to U.S. Government due to Administrative or Operational
Use
C03 Statement C, limited to U.S. Government and Contractors due to Critical
Technology
C04 Statement C, limited to U.S. Government and Contractors due to Foreign
Government I Information
C08 Statement C, limited to U.S. Government and Contractors due to Software
Documentation
C09 Statement C, limited to U.S. Government and Contractors due to Specific
Authority
C10 Statement C, limited to U.S. Government and Contractors due to Administrative
or Operational Use
D03 Statement D, limited to DoD and Contractors due to Critical Technology
D04 Statement D, limited to DoD and Contractors due to Foreign Government
Information
D08 Statement D, limited to DoD and Contractors due to Software Documentation
D09 Statement D, limited to DoD and Contractors due to Specific Authority
D10 Statement D, limited to DoD and Contractors due to Administrative or
Operational Use
E01 Statement E, limited to DOD due to Direct Military Support
E02 Statement E, limited to DoD to prevent Premature Dissemination
E03 Statement E, limited to DoD due to Critical Technology
E04 Statement E, limited to DoD due to Foreign Government Information
E05 Statement E, limited to DoD due to Proprietary Information
E06 Statement E, limited to DoD due to Test and Evaluation
E07 Statement E, limited to DoD due to Contractor Performance Evaluation
E08 Statement E, limited to DoD due to Software Documentation
E09 Statement E, limited to DoD due to Specific Authority
E10 Statement E, limited to DoD due to Administrative or Operational Use
F01 Statement F, Request Approval of Controlling Office due to Direct Military
Support
F11 Statement F, request approval of controlling office due to Special Dissemination
and Reproduction
N00 MIL-STD-1806 does not apply
X00 Statement X, Certified Contractors

0015 contract-document-identifier S 58
The document identifier which represents the complete and unique identification of a contract, purchase
order, or other procurement instrument. This includes the source of the contract and the contract
number. (Source of requirements: DFAR 204.7003(b), DFAR 204.7004(d).) This DED is used in the
following Table(s): 011, 255, 257, 292, 332, 354, 355, 356, 675, 676, 678, 679, 680, 681, 682, 900,
950, 951, 952, 953, 954, 955, 956, 957, 958, 959, 960, 961, 962, 963, 964, 965, 966, 967, 968, 969,
970, 971, 972.

C-28
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

This DED is used as part of the following DED string(s):

DED Title
0235 contract-data-submittal-document-resubmittal-requirement-identifier

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0052 document-source-enterprise-identifier
0226 contract-document-alphanumeric-identifier
0004 contract-document-type-code

0016 document-distribution-statement-text C L 480

The narrative text that states in detail the limitations on distribution of a document. Must be a printable
ASCII character, space, tab, line feed, and carriage return. (Source of requirements: DoDD 5230.24,
DoDD 5230.25, DoDD 5230.9.)

document-long-distribution-statement-text Size: 300

The actual text of the full (long) document distribution statement. This DED is used in the following
Table(s): 014.

document-short-distribution-statement-text Size: 37
The actual text of the abbreviated form of Distribution Statement. This DED is used in the following
Table(s): 014.

0017 contract-document-line-item-identifier C L 6
The unique identifier within a contract which identifies the supply being purchased. This element may
include a Contract Sub-line item identification letter. Section B of the contract indicates usage. The first
4 positions must be numeric. The last 2 may be blank; but if nonblank, they must be uppercase letters
AA through ZZ, excluding the letters I and O. (Source of requirements: DFAR 204.7103-2, DFAR
204.7104-2.) This DED is used in the following Table(s): 255, 355, 958, 959, 960.

0018 process-event-code C L 5
A user defined code to identify a unique contractual event, for example, PDR for Preliminary Design
Review, FFT for First Flight Test, etc. A partial list of values included below are standard for the events
shown; however, users may use additional codes of their own choosing for other contract events.
(Source of requirements: MIL-HDBK-61, MIL-STD-1521A.) This DED is used in the following
Table(s): 961.

This DED is used as part of the following DED string(s):

DED Title
0234 contract-data-submittal-document-event--delta-text
0161 document-effective-cut--off-event-delta-text

The valid domain values for this element are as follows:

The valid domain values for this element are as follows: INWK, REJ, REVW, RLSE.

document-representation-release-process-technical-recommended-
disposition-status-code
The code representing and/or denoting the disposition recommended by the technical reviewer. This
DED is used in the following Table(s): 811.

The valid domain values for this element are as follows: REJ, RLSE, SUBMIT.

document-revision-application-activity-approval-process-disposition-
status-code
The status code that represents or denotes the current application activity approval status during the
process of document revision submission, review and approval by the application activity. This DED is
used in the following Table(s): 861, 862, 863, 864, 865, 866, 867, 967.

The valid domain values for this element are as follows: ADOPT, DISAPV, PEND, SUBMIT.

C-32
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

document-revision-approval-process-disposition-status-code
The status code that represents or denotes the current change control authority approval status during the
process of document revision submission, review and approval. This DED is used in the following
Table(s): 262, 271, 292, 294, 295, 308, 356, 370, 373, 374, 535, 806, 807, 850, 851, 853, 854, 855,
863.

The valid domain values for this element are as follows: APV, AWC, DISAPV, INWK, SUBMIT.

document-revision-approval-process-submission-disposition-status-code
The code which identifies or denotes that a document revision has achieved the status of 'submit' in the
document revision approval process. This DED is used in the following Table(s): 806, 852, 857, 858.

The valid domain values for this element are as follows: SUBMIT.

engineering-change-implementation-process-action-disposition-status-
code
The standard status code which represents and/or denotes the status of the disposition action taken on an
ECP implementation action item. This DED is used in the following Table(s): 264.

The valid domain values for this element are as follows: CANC, COMPL, DEFER, DISTR, INWK,
PLACOR.

engineering-change-proposal-document-class-concurrence-process-
disposition-status-code
A status code that indicates the defense contract management office's concurrence or nonconcurrence
with the engineering change proposal classification. This DED is used in the following Table(s): 251.

The valid domain values for this element are as follows: CONCUR, NONCON.

engineering-change-proposal-document-revision-approval-process-
approved-disposition-status-code
The status code that represents and/or denotes that the 'approved' status has been achieved for an ECP in
the approval process. This DED is used in the following Table(s): 309.

The valid domain values for this element are as follows: APV.

revision-notice-document-revision-approval-process-approved-
disposition-status-code
The code that represents and/or denotes that a NOR has achieved the 'approved' status in the approval
process. This DED is used in the following Table(s): 309, 310, 311, 312, 313.

The valid domain values for this element are as follows: APV.

C-33
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

shipping-document-process-disposition-status-code
The status code that indicates the action taken on the DD Form 250. This DED is used in the following
Table(s): 960.

The valid domain values for this element are as follows: APV, PAID, RTN, SUBMIT.

0022 technical-document-government-data-rights-code C L 2
A code that indicates the nature of the government technical rights in data for a document or computer
software. (Source of requirements: DFAR 252.227-7013.) This DED is used in the following Table(s):
011, 016, 900.

The valid domain values for this element are as follows:

Domain
Value Meaning
G Government Purpose License Rights (GPLR); as defined at DFAR 252.277-7013
(c)(2)(iii); applies to non-software documents
G2 Government Purpose License Rights (GPLR) Alternate Text; as defined at
DFAR 252.277-7013 (b)(3)(ii); applies to non-software documentation only
L Limited Rights; as defined at DFAR 252.277-7013 (b)(3)(iii)(C) basic text;
applies to non-software documents
L1 Limited Rights, alternate text 1; as defined at DFAR 252.277-7013
(b)(3)(iii)(C); applies to non-software documentation only
L2 Limited Rights, alternate text 2; as defined at DFAR 252.277-7013 Alternate II
(b)(2)(i)(B); applies to non-software documentation only
N No rights; rights have not been granted to the government
NL Negotiated License rights, as defined at DFARS Part 227.
R Restricted Rights; as defined at DFAR 252.277-7013 (c)(1)(i) and DFAR
252.277-7013 Alternate II (c)(1)(i); applies to software and software-
documentation developed on contract only
RC Restricted Rights for Commercial Software; as defined at DFAR 252.277-7013
(c)(1)(ii) and DFAR 252.277-7013 Alternate II (c)(1)(ii); applies to
commercially available software and supporting documentation only
SB Small Business Innovative Research (SBIR) rights, as defined in DFARS Part
227.
U Unlimited/Unrestricted rights; applies to any documentation or software

0023 configuration-item-product-indicator-code C F 1
A code which denotes whether or not a particular document portrays a configuration item. This DED is
used in the following Table(s): 060.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, the item described by this document is not a configuration item.
Y Yes, the item described by this document is a configuration item.

C-34
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0024 part-product-identifier C L 32
The unique identifier that distinguishes one part from another as defined in a specification or
engineering drawing. A part number may be a string consisting of a drawing-identifier followed by an
optional drawing-suffix-identifier, a specification-identifier followed by an optional specification-suffix-
identifier, or some other number which may or may not have all or part of the controlling design
document identification embedded in it. For commercial parts only, the identifier may also include a
revision letter. (Source of requirements: ISO 10303-203, MIL-STD-100, MIL-STD-961.) This DED is
used in the following Table(s): 053, 054, 084, 087, 104, 105, 111, 164, 166, 174, 175, 210, 211, 212,
220, 225, 230, 231, 232, 235, 236, 238, 239, 240, 245, 258, 284, 293, 317, 318, 319, 360, 361, 363,
364, 423, 436, 437, 491, 492, 521, 522, 523, 524, 525, 529, 920, 929.

This DED is used as part of the following DED string(s):

DED Title
0245 modification-kit-product-identifier

assembled-part-product-identifier
A part identifier for an assembled part/product. This DED is used in the following Table(s): 233, 234,
237, 242, 243, 256, 362.

component-part-product-identifier
A part identifier for a part used as a component part of an assembly. This DED is used in the following
Table(s): 233, 234, 237, 242, 256, 362.

modified-part-product-identifier
A part identifier of a part which has been modified into a different part number from the originally
manufactured part (but with the same product-tracking base-identifier as the originally manufactured
part. For example: part XYZ-1 is modified into an XYZ-2. This DED is used in the following
Table(s): 531, 532, 533.

original-part-product-identifier
The original identifier of a part which has been modified into a different part number or lot. This DED
is used in the following Table(s): 531, 532, 533.

part-product-administrative-control-identifier
The part identifier assigned as the administrative control number of a source-controlled, vendor-item, or
procurement-controlled part or material, or as an identification cross-reference. This DED is used in the
following Table(s): 055, 056.

part-product-basic-identifier Size: 30
The basic identifier for a commercial part, excluding any revision designation. This DED is used in
the following Table(s): 919, 925, 926.

C-35
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

part-product-vendor--assigned-identifier
The unique part identifier that was assigned by the original design agency (as opposed to the part-
product-administrative-control-identifier assigned to it on a source control, vendor item, purchase
control, or cross-reference drawing). This DED is used in the following Table(s): 056.

replaced-part-product-identifier
A identifier of a part for which a substitute or superseding part or material has been identified. This
DED is used in the following Table(s): 216, 217.

substitute-part-product-identifier
An identifier of a part which may be substituted for another part or material without specific approval
because it is 1) authorized as a substitute or superseding part in a military specification or standard, a
non-government standard, or a government or non-government stock list, or 2) is identified as an
interchangeable replacement or superseding part on the engineering drawing for the part being replaced,
or 3) the part replaces a part, the use of which must be discontinued due to public law. This DED is
used in the following Table(s): 207, 216.

0025 separate-parts-list-document-code C F 1
A code to indicate that the engineering drawing parts list is integral to the drawing; is separately
maintained; or that no parts list exists. This DED is used in the following Table(s): 051.

The valid domain values for this element are as follows:

Domain
Value Meaning
I Integral parts list
N No parts list
S Separate parts list

0026 document-sheet-identifier C R 4
The sheet or page number identifier of a multi-sheet or multi-page document. Numeric characters only.
(Source of requirements: ANSI Y14.1-1980, MIL-STD-100.) This DED is used in the following
Table(s): 052.

0027 parts-list-document-item-identifier I R 6
The identifier, as shown on the engineering drawing, that is used to identify the location of the part.
This field is also used for sequence numbers which identify alternate or optional parts to the preferred
part. This number is known as the 'find number'. (Source of requirements: ANSI Y14.34M, MIL-STD-
100.) This DED is used in the following Table(s): 208, 219, 220, 221, 222, 224, 225, 226, 315, 316,
318, 319, 320, 321, 322, 323, 324, 326.

C-36
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0028 product-change-effectivity-timing-type-code C F 1
A code that is used to indicate whether the change effectivity for a part is forward fit or retrofit. This
DED is used in the following Table(s): 259.

The valid domain values for this element are as follows:

Domain
Value Meaning
F Forward fit; incorporate change into future production units
R Retrofit; incorporate change into delivered units

0029 geographic-place-name C L 25
The name of the geographic location (for example: Hill AFB, UT; Fort Sill, OK; Yorktown NWS, VA;
etc.) Must be a printable ASCII character or embedded space. This DED is used in the following
Table(s): 260.

0030 interface-control-document-indicator-code C F 1
A code which denotes or signifies whether or not a document contains interface definitions/requirements
between two configuration items. This DED is used in the following Table(s): 010.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, this is not an interface control document.
Y Yes, this is an interface control document.

0031 asset-identifier C L 60
The unique identifier assigned to a defined asset, such as an aircraft, ship or vehicle.

computer-hardware-asset-nomenclature-identifier
The unique identifier given to development computer hardware that was used by the developing activity
to create the software for the project/system (including modifications and upgrades). This DED is used
in the following Table(s): 151.

computer-operating-system-software-asset-identifier
The unique identifier that denotes a particular software operating system used by the developing activity
to create the project/system software product. This DED is used in the following Table(s): 151.

computer-software-compiler-asset-identifier
The unique identifier that denotes a particular software compiler used to generate object code for the
software product. This DED is used in the following Table(s): 151.

C-37
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

computer-software-link-asset-identifier
The identifier that denotes a specific link editor or linking software, that normally is used in conjunction
with a software compiler to obtain the product object code. This DED is used in the following Table(s):
151.

ship-asset-identifier
The identifier used for ship hull numbers. This DED is used in the following Table(s): 260.

vehicle-asset-identifier
The unique identifier used for vehicle numbers. This DED is used in the following Table(s): 260.

0032 administrative-control-drawing-document-type-code C F 1
A code which indicates or denotes the type of control drawing. (Source of requirements: ANSI
Y14.24M-89.) This DED is used in the following Table(s): 051, 912.

The valid domain values for this element are as follows:

Domain
Value Meaning
D Design control drawing (formerly called an Envelope drawing)
I Interface control drawing
N No, this is not a control drawing
P Procurement control drawing
S Source control drawing
V Vendor item drawing
X Identification cross-reference drawing

0033 entity-identifier C L 36
A generic data element which refers to the identification of an organization or person. See enterprise-
identifier, and author-name data elements. This DED is used in the following Table(s): 000.

This DED is used as part of the following DED string(s):

DED Title
0239 document-current-change-control-authority-identifier

alias-document-source-entity-identifier
The identifier of the author or enterprise which is the source of an alias identifier of a document. This
DED is used in the following Table(s): 556.

controlling-technical-manual-document-source-entity-identifier
The identifying abbreviation or acronym code which represents and/or denotes an organization or
enterprise which is the source of the identifier which is assigned as the controlling, or parent, identifier
in a relationship between a technical manual and aliases of the technical manual. This DED is used in
the following Table(s): 556.

C-38
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

document-custodial-entity-identifier
The name of the organization or enterprise that is responsible for custodial control over a document.
This is the design agency or contractor responsible for the physical security, maintenance, and
modification of the document. This DED is used in the following Table(s): 011.

document-origination-entity-identifier
The identifier of the person or enterprise that was responsible for the original generation of the
document. This is independent of, but usually the same as, the design activity or design source that
becomes part of the document's unique identification when combined with the document identifier. This
DED is used in the following Table(s): 010.

document-representation-revision-originator-entity-identifier
The identifier which represents the person or organization which is responsible for the creation of a
document representation. This DED is used in the following Table(s): 801.

document-source-entity-identifier
The identifier for the person, company, or organization which is the source of the identifier assigned to a
document. This DED is used in the following Table(s): 010, 011, 019, 033, 040, 041, 071, 082, 085,
110, 150, 151, 152, 158, 160, 180, 223, 253, 266, 271, 322, 330, 332, 352, 357, 450, 451, 452, 453,
454, 461, 550, 551, 553, 555, 601, 681, 800, 801, 802, 803, 804, 805, 806, 807, 811, 812, 850, 851,
852, 853, 854, 855, 857, 858, 861, 862, 863, 864, 865, 866, 867, 965, 966, 967, 968.

This DED is used as part of the following DED string(s):

DED Title
0124 product-baseline-top-level-document-identifier

modification-instruction-document-source-entity-identifier
A identification of the organization or person who is the source of the identification assigned to a
modification instruction document. This DED is used in the following Table(s): 460, 461, 463, 490,
491, 492, 493, 494, 536.

modification-request-document-source-entity-identifier
A identification of the organization or person who is the source of the identification assigned to a
modification request document. This DED is used in the following Table(s): 460.

software-product-source-entity-identifier
The identifier for the person, company, or organization which is the source of the identifier assigned to a
software program or database. This DED is used in the following Table(s): 155, 156, 157, 159, 170,
171, 172, 173, 187, 194, 222, 236, 239, 245, 293, 321, 353, 364, 696, 900, 902, 903.

software-support-document-source-entity-identifier
The identifier of the author or enterprise which is the source of the identifier assigned to a software
support document. This DED is used in the following Table(s): 185, 186, 187.

C-39
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0034 product-type-code C L 1
A code that denotes whether the product is a distinct part or a material item. This DED is used in the
following Table(s): 100, 345, 400, 913, 914.

The valid domain values for this element are as follows:

Domain
Value Meaning
M Materials or discrete parts identified by one or more parameters such as type,
class, voltage, thread, head-type, power-output, etc.
N Not applicable
P Materials or discrete parts identified by distinct part-numbers

0035 product-status-code C F 1
A status code used to indicate whether a product is in active use, or has been made inactive by
obsolescence or superseded by another product.

The valid domain values for this element are as follows:

Domain
Value Meaning
A Active
O Obsolete
S Superseded

material-product-status-code
A status code used to indicate whether a material is in active use, or has been inactivated by
obsolescence or superseded by another material. This DED is used in the following Table(s): 107, 422,
435.

part-product-status-code
A status code used to indicate whether a part is in active use, or has been inactive by obsolescence or
superseded by another part. This DED is used in the following Table(s): 054, 105, 423, 437.

0036 material-product-classification-type-code C L 4
A material classification code used to differentiate various classification schemes for materials or
discrete parts controlled by program (or military) specifications. A partial list of valid codes are
provided; others may be added as required. (Also, see material-product-classification-type-name.)
(Source of requirements: MIL-STD-961.)

The valid domain values for this element are as follows:

Domain
Value Meaning
CAT Category
CLS Class
COLR Color

C-40
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

COMP Composition
DUTY Duty
FORM Form
GRAD Grade
SIZE Size
STYL Style
TYPE Type

material-product-fifth-classification-type-code
The fifth parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-first-classification-type-code
The first parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-fourth-classification-type-code
The fourth parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-second-classification-type-code
The second parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-sixth-classification-type-code
The sixth parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-third-classification-type-code
The third parameter in a list of up to six parameters used to identify a material.

C-41
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

0037 material-product-classification-type-name C L 5
The classification name within a particular material type code which differentiates various materials
from each other. For example, if materials are designated as Type I or Type II, "Type" is the material
classification type code, and "I" and "II" are material attribute type names. Must be a printable ASCII
character or embedded space. (Source of requirements: MIL-STD-961.)

material-product-fifth-classification-type-name
The value of the fifth parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-first-classification-type-name
The value of the first parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-fourth-classification-type-name
The value of the fourth parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-second-classification-type-name
The value of the second parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

material-product-sixth-classification-type-name
The value of the sixth parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

C-42
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

material-product-third-classification-type-name
The value of the third parameter in a list of up to six parameters used to identify a material.

This DED is used as part of the following DED string(s):

DED Title
0038 material-product-identifier

0038 material-product-identifier S 54
The identifier for materials or discrete parts which are not identified by a part number. The identifier
consists of a string of six paired material types and material names. This DED is used in the following
Table(s): 083, 086, 106, 107, 200, 201, 205, 221, 235, 238, 241, 284, 320, 363, 365, 366, 422, 434,
435, 494, 526, 527, 528, 530, 921, 923, 924, 928.

This DED is used as part of the following DED string(s):

DED Title
0048 material-product-vendor--assigned-identifier

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0036 material-product-first-classification-type-code
0037 material-product-first-classification-type-name
0036 material-product-second-classification-type-code
0037 material-product-second-classification-type-name
0036 material-product-third-classification-type-code
0037 material-product-third-classification-type-name
0036 material-product-fourth-classification-type-code
0037 material-product-fourth-classification-type-name
0036 material-product-fifth-classification-type-code
0037 material-product-fifth-classification-type-name
0036 material-product-sixth-classification-type-code
0037 material-product-sixth-classification-type-name

assembled-material-product-identifier
The identification of a material (or discrete part) which is not identified by a part number and which is
used as an assembly. This DED is used in the following Table(s): 244.

component-material-product-identifier
The identification of a material (or discrete part) which is not identified by a part number and which is
used as a component of a higher level assembly. This DED is used in the following Table(s): 243, 244.

modified-material-product-identifier
A material identifier of a material which has been modified into a different material from the originally
manufactured material but with the same product-tracking base-identifier as the original material. This
DED is used in the following Table(s): 534.

C-43
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

original-material-product-identifier
The original identifier of a material (not identified by a part number) which has been modified into a
different material. This DED is used in the following Table(s): 534.

replaced-material-product-identifier
A material identifier for which a substitute or superseding part or material has been identified. This
DED is used in the following Table(s): 206, 207.

substitute-material-product-identifier
An identifier of a material which may be substituted for another material or part without specific
approval because it is 1) authorized as a substitute or superseding part in a military specification or
standard, a non-government standard, or a government or non-government stock list, or 2) is identified
as an interchangeable replacement or superseding part on the engineering drawing for the part being
replaced, or 3) the part replaces a part, the use of which must be discontinued due to public law. This
DED is used in the following Table(s): 206, 217.

0039 enterprise-address-text S 142

The text of the string of data elements that constitute a full address for an organization or enterprise.
(Source of requirements: U.S. GPO Style Manual, U.S. Postal Service.) This DED is used in the
following Table(s): 940.

This DED is used as part of the following DED string(s):

DED Title
0081 enterprise-office-address-text

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0090 enterprise-first-line-address-text
0091 enterprise-second-line-address-text
0041 city-place-name
0040 state-place-code
0042 country-place-name
0043 place-postal-zone-code

0040 state-place-code C F 2
A code that is an abbreviation for one of the states or designated provinces that comprise the United
States of America or Canada. (Source of requirements: U.S. Govt Printing Office, U.S. Postal Service.)

This DED is used as part of the following DED string(s):

DED Title
0039 enterprise-address-text

The valid domain values for this element are as follows:

C-44
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
AB Alberta
AK Alaska
AL Alabama
AR Arkansas
AZ Arizona
BC British Columbia
CA California
CO Colorado
CT Connecticut
CZ Canal Zone
DC District of Columbia
DE Delaware
FL Florida
GA Georgia
GU Guam
HI Hawaii
IA Iowa
ID Idaho
IL Illinois
IN Indiana
KS Kansas
KY Kentucky
LA Louisiana
LB Labrador
MA Massachusetts
MB Manitoba
MD Maryland
ME Maine
MI Michigan
MN Minnesota
MO Missouri
MS Mississippi
MT Montana
NB New Brunswick
NC North Carolina
ND North Dakota
NE Nebraska
NF Newfoundland
NH New Hampshire
NJ New Jersey
NS Nova Scotia
NT Northwest Territories
NV Nevada
NY New York
OH Ohio
OK Oklahoma
ON Ontario
OR Oregon

C-45
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

PA Pennsylvania
PE Prince Edward Island
PQ Quebec
PR Puerto Rico
RI Rhode Island
SC South Carolina
SK Saskatchewan
TN Tennessee
TX Texas
UT Utah
VA Virginia
VI Virgin Islands
VT Vermont
WA Washington
WI Wisconsin
WV West Virginia
WY Wyoming

0041 city-place-name C L 20
The name of a city, town, village, or named place; usually associated with a state or country. Must be a
printable ASCII character or embedded space. (Source of requirements: MIL-STD-1388-2B.)

This DED is used as part of the following DED string(s):

DED Title
0039 enterprise-address-text

0042 country-place-name C L 60
The name given to political state or nation or its territory. Must be a printable ASCII character or
embedded space. (Source of requirements: MIL-STD-1388-2B.)

This DED is used as part of the following DED string(s):

DED Title
0039 enterprise-address-text

0043 place-postal-zone-code C L 10
The postal zone code (U.S. ZIP) or other country postal zone code used to facilitate mail delivery.
Must be uppercase letters, digits or dash -(-). (Source of requirements: U.S. Postal Service.)

This DED is used as part of the following DED string(s):

DED Title
0039 enterprise-address-text

C-46
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0044 enterprise-office-name C L 20
The name of a particular agency, activity or division within an organization or enterprise that is
responsible for performing a specific task. Sometimes referred to as an office symbol. Must be a
printable ASCII character or embedded space. This DED is used in the following Table(s): 676, 941.

This DED is used as part of the following DED string(s):

DED Title
0239 document-current-change-control-authority-identifier
0228 enterprise-division-identifier
0081 enterprise-office-address-text

deviation-implementation-required-action-responsible-enterprise-office-
name
The name of the activity, office or organization responsible for assuring implementation of an approved
RFD. This DED is used in the following Table(s): 370.

document-custodial-enterprise-office-name
The name of a particular agency, activity or division within an organization or enterprise that is
responsible for custodial control over a document. This is the division or office of the design agency or
contractor responsible for the physical maintenance and modification of the document. This DED is
used in the following Table(s): 011.

document-distribution-controller-enterprise-office-name
The name of the activity, office or organization that has distribution control for a document, data or
other information. This DED is used in the following Table(s): 011, 900.

engineering-change-implementation-required-action-responsible-
enterprise-office-name
The name of the activity, office or organization responsible for assuring implementation of an approved
ECP. This DED is used in the following Table(s): 262.

0045 configuration-item-product-designation-identifier C L 43
The system or configuration item (CI) designation portion of the nomenclature assigned by the
Government for a configuration item. (Nomenclature consists of a name portion and an identifier (or
designator) portion. For hardware this identifier is the type-model-series designator, or the mission-
design-series for the item. Must be uppercase letters, numbers, dash -(-), or virgule (/). (Source of
requirements: AFR 82-1, AR 70-50, MIL-STD-1464(AR), MIL-STD-1661(OS), MIL-STD-1812, MIL-
STD-196, MIL-STD-787, NAVMATINST 8800.4.) (This is equivalent to MIL-PRF-49506 DED
0470.) This DED is used in the following Table(s): 501, 693.

This DED is used as part of the following DED string(s):

DED Title
0047 configuration-item-product-nomenclature-text

C-47
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0046 configuration-item-product-name C L 60
The configuration item name portion of the nomenclature. (Nomenclature consists of a name portion
and an identifier (or designator) portion.) Must be a printable ASCII character or embedded space.
(Source of requirements: AFR 82-1, AR 70-50, MIL-STD-1464(AR), MIL-STD-1661(OS), MIL-STD-
1812, MIL-STD-196.) (This is equivalent to MIL-PRF-49506 DED 0480.)

This DED is used as part of the following DED string(s):

DED Title
0047 configuration-item-product-nomenclature-text

0047 configuration-item-product-nomenclature-text S 103

The text that describes the nomenclature for a configuration item (CI) that consists of the ci-product-
designation identifier and the ci-product-name. (Source of requirements: AFR 82-1, AR 70-50, MIL-
STD-1464 (AR), MIL-STD-1661(OS), MIL-STD-1812, MIL-STD-196, MIL-STD-787,
NAVMATINST 8800.4.) This DED is used in the following Table(s): 060, 100, 208, 323, 690, 697.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0045 configuration-item-product-designation-identifier
0046 configuration-item-product-name

0048 material-product-vendor--assigned-identifier S 168

The identification of a material as assigned by the original design agency. This DED is used in the
following Table(s): 055.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0092 material-product-generic-identifier
0038 material-product-identifier

0049 product-national-stock-identifier C F 16
The national stock number (NSN) identifier assigned to each item of supply repetitively used,
purchased, stocked, or distributed within the Federal Government. Consists of the federal supply
classification (FCS) and the national item identification number (NIIN). Must be digits and dashes in
pattern 0000-00-000-0000. (Source of requirements: DLA Stock List, MIL-STD-1388-2B.) (This is
equivalent to MIL-PRF-49506 DED 0680.) This DED is used in the following Table(s): 200, 210, 345.

replaced-product-national-stock-identifier Size: 13
The national stock number (NSN) identifier for which a substitute part is available, or which has been
discontinued and replaced by a superseding part. This DED is used in the following Table(s): 346.

C-48
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

replacement-product-national-stock-identifier Size: 13
The national stock number (NSN) identifier for an NSN which has been designated for use as a
replacement for another item which has been superseded, or as a substitute for another item which is
temporarily unavailable. This DED is used in the following Table(s): 346.

0050 enterprise-identification-type-code C F 3
The identification code which represents and/or denotes the method used to identify an organization or
enterprise. This DED is used in the following Table(s): 002.

The valid domain values for this element are as follows:

Domain
Value Meaning
CAG CAGE or NSCM
COM Commercial name
ORG Organization identifying acronym

software-product-source-enterprise-identification-type-code
The identification code which represents and/or denotes the method used to identify an organization or
enterprise associated with a software product. This DED is used in the following Table(s): 152, 160,
173.

The valid domain values for this element are as follows: CAG, COM.

0051 configuration-item-designation--convention-document-code C L 4
A code which represents and/or denotes the military standard upon which the assignment of
configuration item nomenclature is based. This DED is used in the following Table(s): 693.

The valid domain values for this element are as follows:

Domain
Value Meaning
1464 MIL-STD-1464(AR), Army Nomenclature System
1661 MIL-STD-1661(OS), Mark & Mod Nomenclature System
1812 MIL-STD-1812, Type Designation, Assignment and Method for Obtaining
196 MIL-STD-196, Joint Electronics Type Designation System
787 MIL-STD-787, Joint Optical Range Instrumentation Type Designation System
CSCI Computer Software Configuration Item as defined in DOD-STD-2167, Defense
System Software Development; MIL-STD-498, Software Development; or
equivalent.
MAV AFR 82-1/AR 70-50/NAVMATINST 8800.4, Designating and Naming Defense
Equipment -- Military Aerospace Vehicles
OBS Other, obsolete, standard

C-49
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0052 enterprise-identifier C L 30
A generic identifier for an enterprise which refers to either a CAGE/NSCM Code, an acronym for a
standards organization, or a company name. This DED is used in the following Table(s): 002, 565,
615, 616, 617, 618, 619, 676, 700, 701, 702, 703, 704, 705, 706, 940, 941.

This DED is used as part of the following DED string(s):

DED Title
0228 enterprise-division-identifier
0081 enterprise-office-address-text
0089 program-higher-level-configuration-control-board-text

assembly-design-enterprise-identifier
The unique identifier for the design activity of an assembly. This DED is used in the following
Table(s): 233, 242, 243, 244.

component-material-design-enterprise-identifier
The identification of the design enterprise for a material (or discrete part) which is not identified by a
part number and which is used as a component of a higher level assembly. This DED is used in the
following Table(s): 243, 244.

component-part-design-enterprise-identifier
The identification of the design enterprise for a part which is used as a component of a higher level
assembly. This DED is used in the following Table(s): 233, 242.

configuration-control-board-convening-enterprise-identifier
The identifier of the enterprise which sponsors the configuration control board. This DED is used in the
following Table(s): 262, 264, 370, 372.

Definition and Legal Values (if any)

238, 239, 240, 241, 259, 361, 366, 400, 491, 494, 500, 501, 502, 503, 504, 505, 506, 508, 509, 510,
511, 515, 516, 517, 518, 519, 520, 521, 522, 523, 525, 526, 528, 529, 530, 535, 536.

0057 product-change-effectivity-tracking-type-code C F 1
A code which represents or denotes the type of sequential unit identifier which will be used to specify
and track implementation of a change to an item or the timing of the effectivity. This DED is used in the
following Table(s): 237, 238, 239, 240, 241, 245, 256, 259, 260, 284, 293, 361, 362, 363, 364, 366,
491, 494, 515, 535, 536.

This DED is used as part of the following DED string(s):

DED Title
0175 product-tracking-identifier

The valid domain values for this element are as follows:

Domain
Value Meaning
B Block-change number
D Date-code
G Government-assigned serial number
L Lot number
M Manufacturer-assigned serial number

0058 product-sequential-tracking-identifier C L 15
A generic product tracking identifier applied to any sequentially-assigned number/letter combination
that is applied to the product to differentiate units of the product; for example, serial numbers, lot
numbers, etc. This DED is used in the following Table(s): 240, 241, 245, 515, 535, 536.

This DED is used as part of the following DED string(s):

DED Title
0175 product-tracking-identifier

product-ending-effectivity-sequential-tracking-identifier
The ending unit tracking identifier in the range of unit tracking identifiers for which a particular design
change is applicable to the item. For example, serial or block numbers. (This is equivalent to MIL-
PRF-49506 DED 1170.) This DED is used in the following Table(s): 237, 238, 239, 259, 361, 366,
491, 494.

product-starting-effectivity-sequential-tracking-identifier
The starting unit tracking identifier in the range of unit tracking identifiers for which a particular design
change is applicable to the item. For example, serial or block numbers. (This is equivalent to MIL-
PRF-49506 DED 1170.) This DED is used in the following Table(s): 237, 238, 239, 256, 259, 260,
284, 293, 361, 362, 363, 364, 366, 491, 494.

C-54
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0059 program-name C L 30
The name of any definable collection of resources and assets bound by a common objective. This is
sometimes referred to as a system name. Characters are limited to letters, numbers, decimals (.), spaces
( ), virgules (/), hyphens -(-), and parenthesis (). This DED is used in the following Table(s): 262, 264,
330, 370, 372, 565, 615, 616, 617, 618, 619, 691, 692, 700, 701, 702, 703, 704, 705, 706.

This DED is used as part of the following DED string(s):

DED Title
0239 document-current-change-control-authority-identifier
0089 program-higher-level-configuration-control-board-text

program-subsystem-name
The name of a system or program which is subsidiary to another system or program. This DED is used
in the following Table(s): 698.

program-system-name
The name of a system or program. This DED is used in the following Table(s): 698.

0060 software-product-generic-identifier C L 248

The identifier of, and primary reference to, a software application or database product. It may be a part
number, software number, or application/database identifier (name or number) and release number.
This DED is used in the following Table(s): 170, 173, 187, 194, 222, 236, 239, 245, 293, 321, 353,
364, 696, 900, 902, 903.

0061 software-product-united-states-air-force--assigned-identifier S 25
The unique identifier assigned by the U.S. Air Force (OC-ALC/MMEDUE) to a computer software
configuration item (CSCI), group of CSCIs, or CSCI engineering documentation package. This
identifier may be the primary identifier, or an alias to the primary identifier, of software or supporting
engineering documentation for embedded computer systems (ECS). It is used by the USAF for tracking
configurations and authorizing distribution of ECS software. (Note: in addition to the data elements
which are concatenated to form this data element string, there are three (3) embedded dashes -(-); they
are located after the second, third and fifth data elements of the string.) (Source of requirements: USAF
TO 00-5-16, USAF TO 00-5-17.)

This DED is used as part of the following DED string(s):

DED Title
0237 software-product-united-states-air-force--assigned-designation-identifier

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0179 software-product-united-states-air-force--assigned-category-code
0182 software-product-united-states-air-force--assigned-major-function-code
0183 software-product-united-states-air-force--assigned-applicable-system-identifier
0188 software-product-united-states-air-force--assigned-type-code

C-55
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0221 software-product-united-states-air-force--assigned-sequence-identifier
0189 software-product-united-states-air-force--assigned-version-identifier
0236 software-product-united-states-air-force--assigned-applicability-code

0062 software-product-version-identifier C L 8
An identifier that designates the version/revision of the software product. The version number and/or
letter is used to indicate a particular release of the software. Upper and lowercase letters; digits; and
special characters -(-); (.) or (:). This DED is used in the following Table(s): 154, 159, 164, 166.

This DED is used as part of the following DED string(s):

DED Title
0262 software-product-identifier

0063 product-interchangeability-code C F 1
A code which signifies or denotes whether the substitute/replacement part/material is one-way or two-
way interchangeable with the primary part/material. (This is equivalent to MIL-PRF-49506 DED 0430.)
This DED is used in the following Table(s): 206, 207, 216, 217.

The valid domain values for this element are as follows:

Domain
Value Meaning
1 The substitute/replacement part/material can be used in lieu of the primary or
original part/material, but NOT vice versa.
2 The substitute/replacement part/material can be used in lieu of the primary or
original part/material and vice versa.

0064 asset-version-identifier C L 8
The unique identifier which denotes a specific release or revision of an asset. Must be uppercase and
lowercase letters; digits; and special characters dash -(-), decimal(.), or colon (:).

computer-operating-system-software-asset-version-identifier
The unique identifier which denotes a specific release of the software operating system that was used in
developing the software product. This DED is used in the following Table(s): 151.

computer-software-compiler-asset-version-identifier
The unique identifier that denotes a specific release of the software compiler used to generate object
code for the software product. This DED is used in the following Table(s): 151.

computer-software-link-asset-version-identifier
The unique identifier that denotes a specific release of the link software. This DED is used in the
following Table(s): 151.

C-56
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0065 process-required-action-description-text C L 9999

The freeform description of the action item. Must be a printable ASCII character, space, tab, line feed,
page eject, and carriage return.

audit-process-required-action-description-text
The freeform description of a specific action to be accomplished as a result of the audit. This DED is
used in the following Table(s): 676.

0066 process-action-comment-text C L 9999

Freeform text comments concerning a required action. Must be a printable ASCII character, space, tab,
line feed, page eject, and carriage return. This DED is used in the following Table(s): 262, 264, 370,
372, 676, 678.

0067 human-given-name C L 15
The "given" name and/or the initial(s) of the given name of a person. This is commonly referred to as
the "first name and initials". Must be uppercase and lowercase characters, dash -(-), and decimal (.)
only.

This DED is used as part of the following DED string(s):

DED Title
0069 human-name

0068 human-family-name C L 25
The "family" or surname of a person. This is commonly referred to as the "last name". Must be
uppercase and lowercase characters or dash -(-).

This DED is used as part of the following DED string(s):

DED Title
0069 human-name

0069 human-name S 36
The name given to an individual human being. It is a string consisting of a 'given' name, a blank space,
and a 'family' name. This DED is used in the following Table(s): 700, 702, 861, 943.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0067 human-given-name
0068 human-family-name

C-57
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

administrative-contracting-officer-human-name
The name of the administrative contracting officer assigned to a contract. This DED is used in the
following Table(s): 950.

author-human-name
The full name of the person who is considered the author of a document. This DED is used in the
following Table(s): 001, 042, 043.

comment-file-originator-human-name
The name of the person who first created a particular file which contains comments on another file as
part of the review process. This DED is used in the following Table(s): 812, 858, 867, 968.

contract-data-requirement-list-document-form-approver-human-name
The name of the person who approves the CDRL form entry, or modification for use. This DED is used
in the following Table(s): 952.

contract-data-requirement-list-document-form-preparer-human-name
The name of the person who prepared the CDRL form entry, or modification for use. This DED is used
in the following Table(s): 952.

contract-data-submittal-document-dispositioner-human-name
The name of the person who dispositions the contract data item submittal. This DED is used in the
following Table(s): 956.

contractor-human-name
The name of a person who represents the contracted company, agency or organization. This DED is
used in the following Table(s): 950.

defense-contract-management-command-contact-human-name
The name of the Defense Contract Management Command contact on the program. This DED is used
in the following Table(s): 251.

document-file-originator-human-name
The name of the person who first created a particular file which is part of a particular document
representation. This DED is used in the following Table(s): 812, 858, 867, 968.

document-representation-release-process-dispositioner-human-name
The name of the person who dispositions a document representation as part of the document
representation release process. This DED is used in the following Table(s): 803.

C-58
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

document-revision-approval-process-dispositioner-human-name
The name of the person who dispositions a document as part of the document approval process. This
DED is used in the following Table(s): 850.

file-originator-human-name
The name of the person who first created a particular electronic file. This DED is used in the following
Table(s): 232, 252, 261, 314, 358, 802, 900, 901, 903.

file-reviewer-human-name
The name of a person who reviews a particular electronic file. This DED is used in the following
Table(s): 811, 857, 866.

product-procuring-contracting-officer-human-name
The name of the procuring contracting officer as it appears on an Engineering Change Proposal or
Request for Deviation This DED is used in the following Table(s): 950.

0070 audit-process-type-code C F 3
The audit process code which represents and/or denotes the type of configuration audit being performed
on the developed products. Functional requirements are reviewed at the FCA and physical requirements
at the PCA. This DED is used in the following Table(s): 675, 676, 678, 679, 680, 681, 682.

The valid domain values for this element are as follows:

Domain
Value Meaning
FCA Functional configuration audit
PCA Physical configuration audit

0071 *agreement-name C L 100

The name of an agreement. Must be a printable ASCII character or embedded space. (Source of
requirements: DDRS element 12,682.) This DED is used in the following Table(s): 950.

0072 *action-identifier C R 10
An identifier that represents a specific action. Must be the ASCII character set of digits 0-9. (Source of
requirements: DDRS Element 9904.)

audit-process-action-identifier
An audit action identifier used as the unique and primary reference for an audit action item. Must be the
ASCII character set of digits 0-9. This DED is used in the following Table(s): 676, 678, 679, 680, 681,
682.

C-59
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

deviation-implementation-process-action-identifier
The identifier used as a unique and primary reference for an action that is required to implement an
approved RFD. Must be the ASCII character set of digits 0-9. This DED is used in the following
Table(s): 370, 372.

engineering-change-implementation-process-action-identifier
The identifier used as a unique and primary reference for an action that is required to implement an
approved ECP. Must be the ASCII character set of digits 0-9. This DED is used in the following
Table(s): 262, 264, 565, 615, 616, 617, 618, 619.

0073 product-federal-supply-classification-code C F 4
The code which represents the federal supply classification code as defined in Cataloging handbook H2.
Must be ASCII digits 0-9. (Source of requirements: DLA Hdbk H2.) This DED is used in the
following Table(s): 100.

0074 *materiel-item-supply-electrostatic-discharge-electromagnetic- C F 1
interference-code
The code that represents the susceptibility of a materiel-item-supply to electrostatic discharge or
electromagnetic damage. (Source of requirements: DDRS element 10,529, MIL-STD-100.) This DED
is used in the following Table(s): 200, 210.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, item is not susceptible to either electrostatic discharge or electromagnetic
interference.
Y Yes, item is susceptible to either electrostatic discharge or electromagnetic
interference

0075 document-reference-citation-identifier C L 30
Citation identifier to a specific reference within a document, for example, a paragraph number, figure or
table number, appendix number, drawing sheet and/or zone, etc. (Source of requirements: DoDM
5010.12-M.) This DED is used in the following Table(s): 679, 680, 681, 953.

0076 entity-type-code C F 1
The standard code which represents and/or denotes whether the entity-identifier is an organization or
person. This DED is used in the following Table(s): 000.

The valid domain values for this element are as follows:

C-60
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
E Enterprise or organization
H Human individual

0077 *materiel-item-first-article-test-code C F 1
The code that denotes whether the first article of a production series requires testing. (Source of
requirements: DDRS element 10,904.) This DED is used in the following Table(s): 051, 101.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, first article testing is not required.
Y Yes, first article testing is required.

0078 *materiel-item-supply-hazardous-material-code C F 2
The code that represents a materiel item of supply that requires special handling because of
environmental or safety reasons. (Source of requirements: DDRS element 10,534.) (This is equivalent
to MIL-PRF-49506 DED 0360.) This DED is used in the following Table(s): 200, 210.

The valid domain values for this element are as follows:

Domain
Value Meaning
BI Biological hazardous material
EX Explosive hazardous material
NA NOT HAZARDOUS
OT Other hazardous material
RN Radiation or Nuclear hazardous material

0079 document-export-control-code C F 1
The standard export code which represents and/or denotes whether or not an export control warning
notice is required for a document that contains technical data subject to withholding from public release.
(Source of requirements: DoDD 5230.24, DoDD 5230.25, DoDD 5230.9.) This DED is used in the
following Table(s): 011, 015, 900.

The valid domain values for this element are as follows:

Domain
Value Meaning
N Export control warning notice is NOT required
Y Export control warning notice is required. See MIL-STD-1806 for text of
warning notice.

C-61
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0080 document-export-control-warning-text C L 500

The full text of the export control warning which is as follows: "WARNING - This document contains
technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec 2751, et
seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App 2401 et seq.
Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with
provisions of DoD Directive 5230.25." (Source of requirements: DoDD 5230.24, DoDD 5230.25,
DoDD 5230.9.) This DED is used in the following Table(s): 015.

0081 enterprise-office-address-text S 214

A string of text consisting of the concatenation of an enterprise-identifier, an optional enterprise-
division-name, and an enterprise-address-text This DED is used in the following Table(s): 700, 702,
803, 850, 861, 942, 943, 962.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0052 enterprise-identifier
0044 enterprise-office-name
0039 enterprise-address-text

defense-contract-management-enterprise-office-address-text
The address of the defense contract management command This DED is used in the following Table(s):
251.

enterprise-administrative-contracting-office-address-text
The text string defining the address of the administrative contracting officer for a contract. This DED is
used in the following Table(s): 950.

enterprise-comment-file-origination-office-address-text
The address of the originator of a comment file. This DED is used in the following Table(s): 812, 858,
867, 968.

enterprise-document-file-origination-office-address-text
The enterprise and office address of the person who is the originator of a particular electronic file which
is part of a particular document representation. This DED is used in the following Table(s): 812, 858,
867, 968.

enterprise-file-origination-office-address-text
The address of the enterprise division which first created a particular electronic file. This DED is used
in the following Table(s): 232, 252, 261, 314, 358, 802, 900, 901, 903.

enterprise-file-review-office-address-text
The address of the enterprise and office to which a document reviewer is assigned. This DED is used in
the following Table(s): 811, 857, 866, 963, 964.

C-62
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

enterprise-procuring-contracting-office-address-text
The text string defining the address of the procuring contracting officer for a contract. This DED is
used in the following Table(s): 950.

performing-enterprise-contact-office-address-text
The address of the point-of-contact for the performing activity (seller) in a contract. This DED is used
in the following Table(s): 950.

0082 {}-date D F 8
The date of an event, expressed as the year, month, and day of the event, that is, YYYYMMDD, where
YYYY is limited to the range 1776 to 9999, MM is limited to the range 01 to 12, and DD is limited to
the range 01-31 (for MM = 01, 03, 05, 07, 08, 10 or 12), 01-30 (for MM = 04, 06, 09, or 11), 01-28 (for
MM = 02 and either YYYY not evenly divisible by 4, or YYYY evenly divisible by 100), and 01-29
(for MM = 02 and YYYY evenly divisible by 4, but not evenly divisible by 100).

*agreement-effective-date
The modification date of the contract or supplemental agreement. This DED is used in the following
Table(s): 951.

audit-process-date
The date on which an audit took place. Normally associated with the FCA and PCA, but can apply to a
specific software audit date. This DED is used in the following Table(s): 675, 676, 678, 679, 680, 681,
682.

audit-process-action-item-disposition-status-date
The status date on which a disposition action to an audit item was established. The type of action taken
is listed in process-disposition-action-status-code data element. This DED is used in the following
Table(s): 678.

contract-data-requirement-list-document-form-approval-process-
disposition-action-status-date
The approval date on which the CDRL form entry or modification was approved for use. This DED is
used in the following Table(s): 952.

contract-data-requirement-list-document-form-preparation-process-
completion-date
The date the CDRL form entry or modification was prepared for use. This DED is used in the following
Table(s): 952.

contract-data-requirement-list-document-item-effective-cut--off-date
The date prior to submittal of a contract data item, on which data collection for the report is ended. This
DED is used in the following Table(s): 953.

C-63
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

Definition and Legal Values (if any)

engineering-change-implementation-process-action-disposition-status-
date
The date on which action was taken to disposition the ECP implementation action item. This DED is
used in the following Table(s): 264.

engineering-change-proposal-document-contract-administration-change-
class-concurrence-date
The date that DCMC indicates concurrence/non-concurrence in the change classification of an ECP.
This DED is used in the following Table(s): 251.

engineering-change-proposal-document-production-contract-authority-
need-date
The contract need date that the performing activity specifies on the ECP as necessary for contractual
approval to maintain the estimated production effectiveness specified in the ECP. This DED is used in
the following Table(s): 289.

engineering-change-proposal-document-retrofit-contract-authority-need-
date
The need date the performing activity specifies on the ECP form as necessary for contractual approval
to maintain the estimated retrofit effectiveness specified in the ECP. This DED is used in the following
Table(s): 290.

engineering-change-proposal-document-revision-approval-process-
approval-disposition-status-date
The date on which an ECP achieved the status of 'approved' in the document approval process. This
DED is used in the following Table(s): 309.

material-product-design-release-date
The date that the design activity releases the material design for use. This DED is used in the following
Table(s): 200.

modification-instruction-document-effective-date
The date on which the modification instruction becomes effective for use. This DED is used in the
following Table(s): 460.

modification-instruction-document-issue-date
The issue date of a modification instruction such as the Time Compliance Technical Order, the
Technical Directive, the Modification Work Order or a Rapid Action Change document. This DED is
used in the following Table(s): 460.

C-67
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

modification-instruction-document-rescission-date
The date when it is anticipated that the modification instruction will have been completely incorporated,
included in applicable documents, and otherwise served its purpose. This DED is used in the following
Table(s): 460.

part-product-release-date
The date that the design activity releasees the part design for use. This DED is used in the following
Table(s): 210.

process-event-end-date
The end date of a unique contractual event. Particular events are identified in the process-event-code
data element. This DED is used in the following Table(s): 961.

process-event-start-date
The start date of a unique contractual event. Particular events are identified in the process-event-code
data element. This DED is used in the following Table(s): 961.

product-assembly-status-date
The date of assembly (or disassembly) of an item. This DED is used in the following Table(s): 242,
243, 244, 245.

product-change-retrofit-completion-date
The completion date for the retrofit change on the product. This DED is used in the following Table(s):
260.

product-manufacture-date
The date that an item was fabricated, assembled, or remanufactured. This DED is used in the following
Table(s): 515.

product-royalty-expiration-date
The expiration date of the royalty requirement. This DED is used in the following Table(s): 289.

product-shipping-date Size: 7
The date an item was shipped. This DED is used in the following Table(s): 960.

program-configuration-control-board-decision-date
The date on which the CCB decides on the disposition of an ECP or RFD and issues the results and
directions for implementation, if applicable. This DED is used in the following Table(s): 704.

C-68
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

revision-notice-document-revision-approval-process-approved-
disposition-status-date
The date on which the NOR achieved the status of 'approved' in the document approval process. This
DED is used in the following Table(s): 309, 310, 311, 312, 313.

technical-document-government-data-rights-expiration-date
The expiration date on government rights to technical data for a particular document, data or computer
software. This DED is used in the following Table(s): 011, 900.

technical-manual-document-revision-issue-date
The date on which a technical manual, or revised technical manual, was officially issued for use. This is
the document date. This DED is used in the following Table(s): 565, 570.

This DED is used as part of the following DED string(s):

DED Title
0135 revised-technical-manual-document-identifier

technical-manual-document-supplement-set-effective-date
The date that a particular set of supplements to a technical manual are all current. A new set date is
established each time a supplement is issued or cancelled. This DED is used in the following Table(s):
572, 573.

technical-manual-operational-supplement-document-issue-date
The date of issue of an operational supplement to a DOD technical manual. This DED is used in the
following Table(s): 612.

technical-manual-routine-supplement-document-issue-date
The date of issue of a routine supplement to a DOD technical manual. This DED is used in the
following Table(s): 613.

technical-manual-safety-supplement-document-issue-date
The date of issue of a safety supplement to a DOD technical manual. This DED is used in the following
Table(s): 611.

technical-manual-supplement-document-issue-date
The date of issue of a supplement to a technical manual. This DED is used in the following Table(s):
614.

0083 technical-document-government-data-rights-text C L 2000

The actual text of the technical data government rights legend. (Source of requirements: DFAR
252.277-7013.) This DED is used in the following Table(s): 016.

C-69
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0084 document-company-proprietary-data-rights-code C F 1
The proprietary rights code which represents and/or denotes a restriction on the use of a delivered
document or data. This DED is used in the following Table(s): 011, 017, 900.

The valid domain values for this element are as follows:

Domain
Value Meaning
N Proprietary rights are not claimed by any company
P This document contains information which is proprietary to the company
specified
S This document contains information which is competition sensitive to the
company specified.

0085 document-security-access-restriction-code C L 6
The restriction code which represents and/or denotes a security-related restriction to document access
which is in addition to the standard security classification (for example, secret, confidential, etc.).
(Source of requirements: DoD 5200.1-R, DoD 5220.22-M.) This DED is used in the following
Table(s): 018, 019, 901.

The valid domain values for this element are as follows:

Domain
Value Meaning
2MAN Two-man access material
CNWDI Critical Nuclear Weapons Design Information
CRYPTO Cryptographic information
FRD Formerly Restricted Data
NOFORN NOt releasable to FOReign Nationals
RD Restricted Data
SAR Special Access Required
WINTEL Warning: Intelligence methods and sources disclosed

0086 product-service-life-period-quantity FXP R 1 6

T
A number representing the expected service life of an item. This DED is used in the following Table(s):
200, 210.

0087 process-period-work-hour-quantity FXP R 1 5

T
The period of time in work hours and partial work hours required to complete a task. Examples are: the
time to install a retrofit kit or to run the system test.

C-70
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

equipment-modification-process-period-work-hour-quantity
The length of time in work hours associated with performing the work associated with implementing the
modification instruction such as in an MWO, TCTO or Technical Directive. This DED is used in the
following Table(s): 460.

retrofit-kit-installation-process-period-work-hour-quantity
The length of time in hours and tenths required for installation of a retrofit kit by a particular level of
maintenance. This DED is used in the following Table(s): 263.

retrofit-kit-test-process-period-work-hour-quantity
The length of time in hours and tenths that each activity requires to test the retrofit kit. This DED is
used in the following Table(s): 263.

retrofit-maintenance-process-period-work-hour-quantity
The length of time in hours and tenths required by a particular level of maintenance for accomplishing a
retrofit order by removing an obsolete component and replacing with a new component. This DED is
used in the following Table(s): 263.

retrofit-system-test-process-period-work-hour-quantity
The length of time in hours and tenths that each activity requires to test the system after installation of
the engineering change. This DED is used in the following Table(s): 263.

0088 software-product-alphanumeric-identifier S 15
The identifier of a specific software release when the software-dash number paradigm is used for
software identification. It consists of a basic software identifier, a hyphen, and a suffix identifier. This
DED is used in the following Table(s): 157, 171.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0190 software-product-basic-application-alphanumeric-identifier
0222 software-product-application-suffix-alphanumeric-identifier

0089 program-higher-level-configuration-control-board-text S 90
The complete identification of the configuration control board from which a subsidiary configuration
control board derives its authority. This DED is used in the following Table(s): 700.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0052 enterprise-identifier
0059 program-name
0151 program-configuration-control-board-name

C-71
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0090 enterprise-first-line-address-text C L 25
The text part of the address that designates location by street name and number assigned to the location
on the street. It may also be a designated post office box number. Must be a printable ASCII character
or space. (Source of requirements: U.S. Postal Service.)

This DED is used as part of the following DED string(s):

DED Title
0039 enterprise-address-text

0091 enterprise-second-line-address-text C L 25
The text part for an address that allows for information beyond just the street name and number.
Examples are: suite, mail station, building. Must be a printable ASCII character or space. (Source of
requirements: U.S. Postal Service.)

This DED is used as part of the following DED string(s):

DED Title
0039 enterprise-address-text

0092 material-product-generic-identifier C L 120

A material identifier that may be the name or an arbitrary number which identifies a material. Must be a
letter, number, dash -(-), decimal (.), pound (#), or virgule (/). This DED is used in the following
Table(s): 083, 086, 200, 205, 221, 235, 238, 241, 284, 320, 363, 365, 366, 494, 526, 527, 528, 530,
921, 928.

This DED is used as part of the following DED string(s):

DED Title
0048 material-product-vendor--assigned-identifier

assembled-material-product-generic-identifier
The identification of an assembly which is not identified by a part number and which is an assembly of
other materials (or discrete parts). This DED is used in the following Table(s): 244.

component-material-product-generic-identifier
The identification of a material (or discrete part) which is not identified by a part number and which is
used as a component of a higher level assembly. This DED is used in the following Table(s): 243, 244.

modified-material-product-generic-identifier
A material identifier for a material which has been modified into a different material from the originally
manufactured material but which has the same product-tracking base-identifier as the original material.
This DED is used in the following Table(s): 534.

C-72
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

original-material-product-generic-identifier
The original identifier of a material which has been modified into a different material or lot. This DED
is used in the following Table(s): 534.

replaced-material-product-generic-identifier
A identifier of a material for which a substitute or superseding part or material has been identified. This
DED is used in the following Table(s): 206, 207.

substitute-material-product-generic-identifier
An identifier of a material which may be substituted for another material or part without specific
approval because it is 1) authorized as a substitute or superseding part in a military specification or
standard, a non-government standard, or a government or non-government stock list, or 2) is identified
as an interchangeable replacement or superseding part on the engineering drawing for the part being
replaced, or 3) the part replaces a part, the use of which must be discontinued due to public law. This
DED is used in the following Table(s): 206, 217.

0093 *materiel-item-supply-precious-metals-indicator-code C F 1
The code that represents presence of precious metals (silver, gold, platinum) in a materiel-item-supply.
(Source of requirements: DDRS element 10,541.) (This is equivalent to MIL-PRF-49506 DED 0790.)
This DED is used in the following Table(s): 200, 210.

The valid domain values for this element are as follows:

Domain
Value Meaning
A Item does not contain precious metal
C Item contains combination of two or more precious metals
G Item contains gold
P Item contains platinum
S Item contains silver
U Precious metal type is unknown
V Precious metal type varies between manufacturers

0094 *supply-item-control-shelf-life-code C F 1
The code that represents the period of time during which a materiel-item-supply retains usability.
(Source of requirements: DDRS element 11,027, DOD 4100.39-M, Vol 10.) This DED is used in the
following Table(s): 200, 210.

The valid domain values for this element are as follows:

Domain
Value Meaning
0 Non-deteriorative
1 3 Months, extendable
2 6 Months, extendable
3 9 Months, extendable

C-73
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

4 12 Months, extendable
5 18 Months, extendable
6 24 Months, extendable
7 36 Months, extendable
8 48 Months, extendable
9 60 Months, extendable
A 1 Month, non-extendable
B 2 Months, non-extendable
C 3 Months, non-extendable
D 4 Months, non-extendable
E 5 Months, non-extendable
F 6 Months, non-extendable
G 9 Months, non-extendable
H 12 Months, non-extendable
J 15 Months, non-extendable
K 18 Months, non-extendable
L 21 Months, non-extendable
M 24 Months, non-extendable
N 27 Months, non-extendable
P 30 Months, non-extendable
Q 36 Months, non-extendable
R 48 Months, non-extendable
S 60 Months, non-extendable
X Medical items, personnel parachutes, and Individual Repair Part Ordering Data
(IRPOD) items with a shelf-life period of greater than 60 months

0095 *organization-type-identifier C L 17
The identifier of the type of organization. (Source of requirements: DOD Enterprise Data Model.)
This DED is used in the following Table(s): 004.

The valid domain values for this element are as follows:

Domain
Value Meaning
DOD United States DoD Organization
INT International Organization
NON-US-GOVT Non-United States Government organization
NON-US-NONGOVT Non-United States nongovernment organization
US-GOVT-NONDEF United States Government nondefense organization
US-NONGOVT United States nongovernment organization

0096 *organization-identifier C L 15
The identifier which represents an administrative structure with a mission. Must be printable ASCII
characters. (Source of requirements: DDRS element 7,875.) This DED is used in the following
Table(s): 004.

C-74
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

document-source-organization-identifier
The unique and primary identifier of the industry, professional, military or other organization which is
the source of the document and its identification. This DED is used in the following Table(s): 024,
025, 046, 047, 288, 305, 310, 402, 403.

0097 *united-states-defense-department-organization-type-identifier C L 8
The identifier of the type of defense department organization. (Source of requirements: DOD
Enterprise Data Model.) This DED is used in the following Table(s): 034.

The valid domain values for this element are as follows:

Domain
Value Meaning
AGENCY Defense Agency
JSTAFF Joint Military Staff
OSD Defense Secretary
SERVICE Military Service
UNI/SPEC Unified/Specified Command

0098 product-baseline-type-code C F 1
A baseline code which identifies the type of configuration baseline. This DED is used in the following
Table(s): 254, 351.

The valid domain values for this element are as follows:

Domain
Value Meaning
A Allocated Baseline
C Contracted baseline
F Functional Baseline
P Product Baseline
T Technical Baseline

0099 contract-data-submittal-document-revision-identifier C R 2
The unique revision identifier that indicates a change or modification to a delivered data item submittal.
Must be uppercase letters excluding O. (Source of requirements: MIL-STD-1700.) This DED is used
in the following Table(s): 955, 956, 965, 966, 967, 968, 969, 970, 971, 972.

This DED is used as part of the following DED string(s):

0108 program--unique-specification-document-subsidiary-type-code C L 3
A code which identifies a specific type of program-unique specification. . (Source of requirements:
DI-E-30131, DOD-STD-2167, MIL-STD-490, MIL-STD-498, MIL-STD-961D.) This DED is used in
the following Table(s): 100.

The valid domain values for this element are as follows:

Domain
Value Meaning
B1 Prime Item Development Specification as defined in MIL-STD-490, or
comparable commercial or non-U.S. document
B2 Critical Item Development Specification as defined in MIL-STD-490 or
comparable commercial or non-U.S. document
B3 Non-Complex Item Specification as defined in MIL-STD-490, or comparable
commercial or non-U.S. document
B4 Facility or Ship Specification as defined in MIL-STD-490 or comparable
commercial or non-U.S. document
C1A Prime Item Function Specification as defined in MIL-STD-490 or comparable
commercial or non-U.S. document
C1B Prime Item Fabrication Specification as defined in MIL-STD-490 or comparable
commercial or non-U.S. document
C2A Critical Item Function Specification as defined in MIL-STD-490 or comparable
commercial or non-U.S. document
C2B Critical Item Fabrication Specification as defined in MIL-STD-490 or
comparable commercial or non-U.S. document
C3 Non-Complex Item Fabrication Specification as defined in MIL-STD-490 or
comparable commercial or non-U.S. document
C4 Inventory Item Specification as defined in MIL-STD-490 or comparable
commercial or non-U.S. document
IRS Interface Requirements Specification as defined in MIL-STD-498, DOD-STD-
2167, DI-E-30131, or comparable commercial or non-U.S. document
IS Item Specification as defined in MIL-STD-961D or comparable commercial or
non-U.S. document
MFR Manufacturer's Specification as defined by best commercial practices

C-78
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

MS Material Specification as defined in MIL-STD-490 (Type E), MIL-STD-961D or

comparable commercial or non-U.S. document
PS Process Specification as defined in MIL-STD-490 (Type D), MIL-STD-961D or
comparable commercial or non-U.S. document
SPS Software Product Specification as defined in MIL-STD-498, DOD-STD-2167,
MIL-STD-490, or comparable commercial or non-U.S. document
SRS Software Requirements Specification as defined in MIL-STD-498 or DOD-STD-
2167A, or B5 Software Development Specification as defined in MIL-STD-490,
or comparable commercial or non-U.S. document
SS Software Specification as defined in MIL-STD-961D or comparable commercial
or non-U.S. document
SYS System Specification as defined in MIL-STD-961D, or System/Segment
Specification as defined in MIL-STD-490, MIL-STD-498, DOD-STD-2167, or
comparable commercial or non-U.S. document

0109 contract-document-line-item-description-text C L 160

The text of a short narrative description about the contract line item. Must be a printable ASCII
character, space, tab, line feed, and carriage return. This DED is used in the following Table(s): 959.

0110 document-sheet-total-quantity I R 3
The total quantity or number of sheets in the document. (Source of requirements: MIL-STD-100.) This
DED is used in the following Table(s): 051.

0111 configuration-item-product-identifier C L 103

The generic reference to the identifier of an HWCI (nomenclature) or CSCI (software source and
identifier). This DED is used in the following Table(s): 331, 675, 676, 678, 679, 680, 681, 682, 692,
695, 696, 697, 703, 952.

This DED is used as part of the following DED string(s):

DED Title
0239 document-current-change-control-authority-identifier

primary-equipment-configuration-item-product-identifier
The official identifier of a configuration item which is supported by another configuration item(s). An
example is a missile supported by a Test Program Set (TPS). This DED is used in the following
Table(s): 694.

support-equipment-configuration-item-product-identifier
The official identifier of a configuration item which supports another configuration item(s). An
example is the Test Program Set (TPS) which supports a missile. This DED is used in the following
Table(s): 694.

C-79
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0112 document-sheet-size-code C R 1
The sheet size code which represents and/or denotes the particular size of a document when printed or
plotted. (Source of requirements: ANSI Y14.1-1980, MIL-STD-100.) This DED is used in the
following Table(s): 051.

The valid domain values for this element are as follows:

Domain
Value Meaning
A 8.5 X 11.0 or 11.0 x 8.5 in.
B 11.0 x 17.0 in.
C 17.0 x 22.0 in.
D 22.0 x 34.0 in.
E 34.0 x 44.0 in.
F 28.0 x 40.0 in.
G 11.0 x (22.5-90.0) in.
H 28.0 x (44.0-143.0) in.
J 34.0 x (55.0-176.0) in.
K 40.0 x (55.0-143.0) in.

0113 part-product-name C L 60
The name given to a product part, both hardware and software. Must be a printable ASCII character or
embedded space. (This is equivalent to MIL-PRF-49506 DED 0480.) This DED is used in the
following Table(s): 209, 210.

0114 part-product-unit-weight FXP R 1 5

T
The weight of a completed unit or assembly expressed as a whole number. Required only on
Government ship construction drawings. (Source of requirements: ANSI Y14.34M-1989.) (This is
equivalent to MIL-PRF-49506 DED 1550.) This DED is used in the following Table(s): 210.

0115 configuration-item-product-type-code C F 1
A code which designates whether a particular configuration item is a hardware CI or a software CI. This
DED is used in the following Table(s): 695.

The valid domain values for this element are as follows:

Domain
Value Meaning
C Computer Software Configuration Item (CSCI)
H Hardware Configuration Item (HWCI)

C-80
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

standard-generalized-markup-language-document-proposed-change-
survivability-effect-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which discusses the effect of the proposed change on product survivability (including
nuclear survivability) in quantitative terms. This DED is used in the following Table(s): 289.

standard-generalized-markup-language-document-proposed-change-
system-test-procedure-effect-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which discusses the effect of the proposed change on system test procedure(s), including
changes, updates, and new procedures. This DED is used in the following Table(s): 289.

standard-generalized-markup-language-document-proposed-change-
technical-manual-effect-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which discusses the effect of the proposed change on technical manuals, including the
identification of required new manuals. This DED is used in the following Table(s): 289.

standard-generalized-markup-language-document-proposed-change-
unusual-effect-description-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which provides the detailed description of one or more impacts of the engineering change
proposal which are not otherwise addressed within the ECP. This DED is used in the following
Table(s): 265.

standard-generalized-markup-language-document-proposed-change-
warranty-effect-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which discusses the effect of the proposed change on product warranties or guarantees.
This DED is used in the following Table(s): 289.

standard-generalized-markup-language-document-proposed-change-
weight-moment-inertia-effect-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which discusses the effect of the proposed change on equipment weight or moment of
inertia (excluding aircraft). This DED is used in the following Table(s): 289.

standard-generalized-markup-language-document-recurring-deviation-
request-corrective-action-taken-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which provides rationale as to why the recurrence of this problem was not prevented by
the previous corrective action(s). This DED is used in the following Table(s): 359.

C-87
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

standard-generalized-markup-language-document-retrofit-
recommendations-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which discusses the recommendations for retrofit, including a kit requirement and
delivery schedule, and special tooling and test equipment requirements. This DED is used in the
following Table(s): 290.

standard-generalized-markup-language-document-specific-proposed-
changes-field-identifier
The standard generalized markup language character combination (tag) which identifies the start of the
text paragraph which provides the detailed description of changes being proposed to a document.
Typically this is done by means of 'From/To', 'As-is/To be' or similar descriptions, or by use of the
'redline & strike-out' capability of most word processing applications. This DED is used in the
following Table(s): 266, 301, 352.

0119 engineering-change-proposal-document-implementation- C F 1
sequence-code
The standard code which represents and/or denotes the implementation sequence of an engineering
change when other related engineering changes exist. This DED is used in the following Table(s): 251.

The valid domain values for this element are as follows:

Domain
Value Meaning
A This ECP must be implemented after the related ECP.
B This ECP must be implemented before the related ECP.
W This ECP must be implemented simultaneously with the related ECP.

0120 contract-document-revision-identifier C L 6
The revision identifier used to indicate an agreed upon and approved change or modification to the
contract document. This number is a suffix formatted in accordance with DFAR 204.7004. First
character must be 'A' or 'P'; the second character must be 'K', 'L', 'M', 'N', 'P', 'Q', 'S', 'T', 'U', 'V', 'W', 'X',
'Y', or 'Z', followed by 4 digits. (Source of requirements: DFAR 204.7004 (c).) This DED is used in
the following Table(s): 255, 257, 292, 332, 354, 355, 356, 679, 680, 951, 952, 953, 954, 955, 956, 957,
958, 959, 960, 963, 964, 965, 966, 967, 968, 969, 970, 971, 972.

This DED is used as part of the following DED string(s):

DED Title
0235 contract-data-submittal-document-resubmittal-requirement-identifier

0121 engineering-change-proposal-document-part-level-code C F 1
The part level code which represents and/or denotes whether the part number is the "lowest level" part
addressed by the ECP, the effectivity base for the ECP, or both. This DED is used in the following
Table(s): 258.

C-88
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

The valid domain values for this element are as follows:

Domain
Value Meaning
B Both
E Basis for effectivity
L Lowest level part

0122 document-identifier C L 240

The document identifier which represents the unique identification of, and primary reference to, a
document. This could be a title or an arbitrary alphanumeric string. Must be printable ASCII
characters. This DED is used in the following Table(s): 010, 011, 019, 033, 071, 082, 085, 110, 150,
151, 158, 159, 185, 223, 253, 266, 271, 322, 330, 332, 352, 357, 450, 451, 452, 453, 454, 461, 550,
551, 553, 555, 601, 681, 800, 801, 802, 803, 804, 805, 806, 807, 811, 812, 850, 851, 852, 853, 854,
855, 857, 858, 861, 862, 863, 864, 865, 866, 867, 910, 911, 913, 914, 915, 917, 919, 926, 965, 966,
967, 968.

This DED is used as part of the following DED string(s):

DED Title
0124 product-baseline-top-level-document-identifier
0262 software-product-identifier
0229 work-statement-document-identifier

controlling-technical-manual-document-identifier
The document identifier which represents the unique identification number of, and primary reference to,
a technical manual which is the controlling, or parent, manual in a relationship between a technical
manual and alias identifiers of the technical manual. This DED is used in the following Table(s): 556.

document-alias-identifier
The document identifier which represents an alias to the primary unique identification of, and primary
reference to, a document. This could be a title or an arbitrary alphanumeric string. This DED is used in
the following Table(s): 556.

modification-instruction-document-identifier
The document identifier which represents the unique identification of, and primary reference to, a
modification instruction document. This could be a title or an arbitrary alphanumeric string. This DED
is used in the following Table(s): 460, 461, 463, 490, 491, 492, 493, 494, 536.

modification-request-document-identifier
The document identifier which represents the unique identification of, and primary reference to, a
modification request document. This could be a title or an arbitrary alphanumeric string. This DED is
used in the following Table(s): 460.

C-89
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

software-support-document-alphanumeric-identifier
The document identifier which represents the unique title or alphanumeric identifier of, and primary
reference to, a specific document in the set of software documentation that supports a software product.
This DED is used in the following Table(s): 186, 187.

0123 product-identification-type-code C F 3
A code which denotes or represents whether a material product is identified by a name or number. This
DED is used in the following Table(s): 921.

The valid domain values for this element are as follows:

Domain
Value Meaning
NAM Name
NUM Number

0124 product-baseline-top-level-document-identifier S 75
The identifier of the top-level document which defines a product baseline of a configuration item. This
DED is used in the following Table(s): 331, 332.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0033 document-source-entity-identifier
0122 document-identifier
0004 document-type-code

0125 deviation-request-document-defect-severity-classification-code C F 2
A classification code to indicate the severity class and defect classification for the request for deviation.
This DED is used in the following Table(s): 351.

The valid domain values for this element are as follows:

Domain
Value Meaning
CR Critical. A departure from the approved configuration documentation that has
been included in the contract or statement of work by the tasking activity and
which involves safety, or the configuration documentation defining the
requirements for the item classifies defects in requirements and the departure is
from a requirement which is classified as critical.
MA Major. A departure from the approved configuration documentation that has
been included in the contract or statement of work by the tasking activity and
which involves: health, performance, interchangeability, reliability,
survivability, maintainability or durability, of the item or its repair parts;
effective use or operation; weight; or appearance (when a factor); or when the
configuration documentation defining the requirements for the item classifies

C-90
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

defects in requirements and the departure is from a requirement which is

classified as major.
MR Minor. A departure from the approved configuration documentation that has
been included in the contract or statement of work by the tasking activity and
which does not involve the factors listed for major or critical, or when the
configuration documentation defining the requirements for the item classifies
defects in requirements and the departure is from a requirement which is
classified as minor.

0126 deviation-request-document-description-text C L 360

The text description of the proposed departure from the technical requirements of the configuration
documentation that is being requested by the Request for Deviation. Must be a printable ASCII
character, space, tab, line feed, and carriage return. This DED is used in the following Table(s): 351.

0127 deviation-request-document-justification-text C L 360

The text description of the nature of the proposed departure from the technical requirements of the
configuration documentation. Must be a printable ASCII character, space, tab, line feed, and carriage
return. This DED is used in the following Table(s): 351.

0128 application-activity-program-government-lead-indicator-code C F 1
A code that indicates whether a government agency or activity is the lead Government agency for
procurement of an item described by a particular design document, or is the lead agency for Government
discourse with the current document change authority for a document for which the Government is not
the current document change authority. This DED is used in the following Table(s): 033.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No
Y Yes

0129 interface-configuration-item-product-affected-code C F 1
A code to indicate whether there is an interface effect with other systems or configuration items as a
result of the engineering change proposal or request for deviation for the item covered by the ECP or
RFD. This DED is used in the following Table(s): 251.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No interface effect
Y Interface effect

C-91
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0130 deviation-request-document-corrective-action-taken-text C L 360

A summary text description of the action(s) taken to prevent recurrence of the problem which
necessitated the need for the request for deviation. Must be a printable ASCII character, space, tab, line
feed, and carriage return. This DED is used in the following Table(s): 351.

0131 deviation-request-document-delivery-schedule-effect-text C L 360

The text description of the effects on the contract delivery schedule that will result from both approval
and disapproval of the request for deviation. Must be a printable ASCII character, space, tab, line feed,
page eject, and carriage return. This DED is used in the following Table(s): 351.

0132 deviation-request-document-price-effect-estimate-amount FXP R 2 8

T
The dollar amount which is an estimate of the reduction or price adjustment resulting from approval of
the request for deviation. This DED is used in the following Table(s): 351.

0133 deviation-request-document-recurring-request-code C F 1
The code that denotes or represents whether or not a request for deviation addresses a recurring problem
which has been previously addressed by a request for deviation. This DED is used in the following
Table(s): 351.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No prior RFD exists for this problem
Y Yes a prior RFD exists for this problem

0134 technical-manual-change-document-identifier C R 2
The identifier of a specific change in a series of changes to the initial issue or to a revision of a technical
manual or order. Limited to uppercase letters (excluding O), and numbers. (This is equivalent to MIL-
PRF-49506 DED 1350.) This DED is used in the following Table(s): 571, 610, 615.

This DED is used as part of the following DED string(s):

DED Title
0218 changed-technical-manual-document-identifier

0135 revised-technical-manual-document-identifier S 40
The identifier of a specific revision of a specific technical manual or order. This DED is used in the
following Table(s): 571, 610, 615.

This DED is used as part of the following DED string(s):

C-92
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

DED Title
0218 changed-technical-manual-document-identifier

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0003 technical-manual-document-alphanumeric-identifier
0082 technical-manual-document-revision-issue-date

0136 process-action-item-title-name C L 120

The name or title of an audit-, ECP implementation-, or RFD implementation-action item. Must be a
printable ASCII character or embedded space. This DED is used in the following Table(s): 262, 370,
676.

0137 allocated-baseline-top--level-document-indicator-code C F 1
The code which represents or denotes whether the program-unique specification is the top-level
document which defines the allocated baseline of a configuration item. This DED is used in the
following Table(s): 100.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, this is not the top-level-document in the allocated baseline for the CI
indicated
Y Yes, this is the top-level document in the allocated baseline for the CI indicated

0138 functional-baseline-top--level-document-indicator-code C F 1
The code which represents or denotes whether a program-unique specification is the functional baseline
of a configuration item. This DED is used in the following Table(s): 100.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, this is not the top-level document in the functional baseline for the CI
indicated
Y Yes, this is the top-level document in the functional baseline for the CI indicated

0139 data-product-delivery-method-code C F 2
A code which represents and/or denotes the type of medium by which a contract data requirements list
item is delivered to the tasking activity. This DED is used in the following Table(s): 964.

The valid domain values for this element are as follows:

C-93
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
AC Aperture card
AT Audio tape
ET Electronic transmittal
FM Film
HC Paper, hard copy manuscript
IA Interactive host access
MD Magnetic disk, diskette
MF Microfilm
MT Magnetic tape
OS Optical storage device
PT Punch tape
VT Video tape
XX Other

0140 contract-document-modification-description-text C L 240

The text of the contract modification description being issued to the contract. Must be a printable
ASCII character, space, tab, line feed, and carriage return. This DED is used in the following Table(s):
951.

0141 modification-instruction-document-subsidiary-type-code C L 7
A code which denotes the type of modification instruction. This DED is used in the following Table(s):
462.

The valid domain values for this element are as follows:

Domain
Value Meaning
FLDCHG Field Change Bulletin as described in MIL-STD-2039
MACHALT Machinery Alteration Instruction as described in DOD-STD-2140
MWO Modification Work Order
NUCALT Nuclear Alteration Instruction
ORDALT Ordnance Alteration Instruction as described in MIL-STD-1662
RAC Rapid Action Change Order
SHIPALT Ship Alteration Instruction
TCTO Time-compliance Technical Order
TECHDIR Technical Directive

0142 modification-request-document-subsidiary-type-code C L 6
A code which denotes the type of modification request document. This DED is used in the following
Table(s): 450.

The valid domain values for this element are as follows:

C-94
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
MP Materiel Proposal, AF Form 1067 (USAF Modification Improvement Program)
PMI Proposed Military Improvement as described in OPNAVINST 4720.2E
PTI Proposed Technical Improvement as described in OPNAVINST 4720.2E

0143 document-format-compliance-indicator-code C F 1
A code which denotes or indicates whether or not a document is required to comply with U.S. DOD
rules on identification. This DED is used in the following Table(s): 460, 550.

The valid domain values for this element are as follows:

Domain
Value Meaning
C Must comply with best commercial practices
D Must comply with DOD practices

0144 contract-document-line-item-quantity I R 7
The quantity of the item to be delivered under the contract line item. (This is equivalent to MIL-PRF-
49506 DED 0990.) This DED is used in the following Table(s): 959.

0145 contract-document-performance-period-months-quantity I R 2
The length of time agreed to in the contract from contract start date to contract completion, expressed in
months. This DED is used in the following Table(s): 951.

0146 shipping-document-dollar-amount FXP R 2 18

T
The dollar value of the product being delivered in this shipment. (Source of requirements: DD FORM
250.) This DED is used in the following Table(s): 960.

0147 shipping-document-shipped-item-description-text C L 180

The narrative description of the item(s) being shipped via the DD Form 250. Must be a printable ASCII
character, space, tab, line feed, and carriage return. This DED is used in the following Table(s): 960.

0148 shipping-document-shipped-item-quantity I L 3
The quantity of items shipped via the DD Form 250. (This is equivalent to MIL-PRF-49506 DED
1000.) This DED is used in the following Table(s): 960.

C-95
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0149 revised-program--unique-specification-document-identifier S 35
The identifier of a specific revision of a specific program-unique specification. This DED is used in the
following Table(s): 620.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0003 program--unique-specification-document-alphanumeric-identifier
0009 program--unique-specification-document-alphanumeric-revision-identifier

0150 contract-data-submittal-document-submittal-type-code C F 1
The submittal type code which represents and/or denotes whether the contractually required data is
being submitted as a draft or final submittal. (Note: if there is a draft submittal, the final submittal shall
be a higher revision level than the draft.) This DED is used in the following Table(s): 954.

The valid domain values for this element are as follows:

Domain
Value Meaning
D Draft
F Final

0151 program-configuration-control-board-name C L 30
The name which identifies a particular configuration control board (CCB) within a particular program
(project or system) within a particular enterprise. Must be a printable ASCII character. This DED is
used in the following Table(s): 262, 264, 370, 372, 565, 615, 616, 617, 618, 619, 700, 702, 703, 704,
705, 706.

This DED is used as part of the following DED string(s):

DED Title
0239 document-current-change-control-authority-identifier
0089 program-higher-level-configuration-control-board-text

0152 *agreement-identifier C L 25
The identifier that represents an agreement. (Note: This is limited to agreements to which the U.S. DoD
is a party; in case of contracts, the U.S. DoD must be the issuing activity.) (Source of requirements:
DDRS element 12,495.) This DED is used in the following Table(s): 976.

0153 contract-data-submittal-document-remark-text C L 160

The text of the remarks pertaining to the requirements for the specific submittal. Must be a printable
ASCII character, space, tab, line feed, and carriage return. This DED is used in the following Table(s):
954, 955.

C-96
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0154 human-responsibility-description-text C L 160

The freeform text narrative which describes the area of expertise and responsibility of a person. Must
be a printable ASCII character, space, tab, line feed, and carriage return. This DED is used in the
following Table(s): 702.

0155 document-security-classification-authority-text C L 60
The text of the name for the original classification authority, the contract number, classification guide
identification or other authority (including the term 'multiple sources'), which directs that a document be
assigned a classification other than 'Unclassified'. Must be a printable ASCII character, space, tab, line
feed, and carriage return. (Source of requirements: DoD 5120.22-M, DoD 5200.1-R.) This DED is
used in the following Table(s): 011, 900.

0156 process-event-name C L 60
The name of a unique contractual event, for example, Program Design Review, First Flight Test, etc.
Must be a printable ASCII character or embedded space. This DED is used in the following Table(s):
961.

document-security-classification-downgrade-process-event-name
The name of the event which, upon occurrence, will authorize the reclassification of classified material
to a lower classification level; for example, from secret to confidential. This DED is used in the
following Table(s): 011, 900.

document-security-declassification-process-event-name
The name of the event which, upon occurrence, will authorize the declassification of classified material.
This DED is used in the following Table(s): 011, 900.

0157 document-security-access-restriction-text C L 200

The text of the actual security access restriction. In some cases, specific text is required by law. Must
be a printable ASCII character, space, tab, line feed, and carriage return. (Source of requirements: DoD
5120.22-M, DoD 5200.1-R.) This DED is used in the following Table(s): 018.

0158 document-quantity I R 2
The quantity of copies of a document. This DED is used in the following Table(s): 962, 964.

0159 contract-data-submittal-document-resubmittal-code C F 1
A code which represents and/or denotes whether or not a revised submittal of a contract data item is
required. This DED is used in the following Table(s): 972.

The valid domain values for this element are as follows:

C-97
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
N No, a resubmittal is not required.
Y Yes, a resubmittal is required after corrections have been made.

0160 {}-time I F 6
The specific chronological point that designates the occurrence (in the past, present, or future) that a
specific even occurred or will occur. Expressed as HHMMSS using a 24-hour clock where HH is hours,
MM is minutes, and SS is seconds based on Greenwich Mean Time.

electronic-document-comment-file-creation-time
The time that a comment file is created, or revised and replaced. For computer files it is the time
assigned by the system in use. This DED is used in the following Table(s): 968.

electronic-document-file-creation-time
The time that a file is created, or revised and replaced. For computer files it is the time assigned by the
system in use. This DED is used in the following Table(s): 232, 252, 261, 314, 358, 802, 900, 903.

electronic-document-representation-file-creation-time
The time that a file (which is part of a document representation) is created, or revised and replaced. For
computer files it is the time assigned by the system in use. This DED is used in the following Table(s):
968.

product-assembly-status-time
The time that a specific assembly status was achieved. This DED is used in the following Table(s):
242, 243, 244, 245.

product-manufacture-time
The time that an item, or lot of items, was manufactured. This DED is used in the following Table(s):
515.

0161 document-effective-cut--off-event-delta-text S 11
Text indicating the date that data collection for a document is to stop. The date is expressed as a period
of time before or after a specific event.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0231 period-length-quantity
0232 period-unit-code
0018 process-event-code

C-98
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

contract-data-requirement-list-document-item-effective-cut--off-event-
delta-text
Text indicating the date (as specified in the Contracts Data Requirements List) that data collection for a
document is to stop. The date is expressed as a period of time before or after a specific event. This
DED is used in the following Table(s): 953.

contract-data-submittal-document-effective-cut--off-event-delta-text
Text indicating the date that data collection for a document is to stop for a specific data submittal. The
date is expressed as a period of time before or after a specific event. This DED is used in the following
Table(s): 954.

0162 supplement-document-type-code C L 7
A code which denotes or represents the type of a supplemental document. (Source of requirements:
MIL-M-38784, MIL-STD-490, MIL-STD-961, MIL-STD-962.) This DED is used in the following
Table(s): 601.

The valid domain values for this element are as follows:

Domain
Value Meaning
MS-AMD Amendment to a U.S. Defense specification
MS-NOT Notice to a U.S. Defense specification
MS-SUP Supplement to a U.S. Defense specification
O-SUP Operational Supplement
R-SUP Technical manual routine supplement
S-SUP Safety supplement
SCN Specification Change Notice to program-unique specification
STD-NOT Notice to a U.S. Defense standard
TM-CHG Technical manual change
TOP-SUP Technical Order page supplement (TOPS)

0163 software-product-identification-paradigm-type-code C F 1
The code that represents and/or denotes the type of paradigm used for software identification. This
DED is used in the following Table(s): 150, 170.

The valid domain values for this element are as follows:

Domain
Value Meaning
D Dash Number Paradigm. The software is identified by an alphanumeric root
identifier followed by a hyphen and an alphanumeric suffix. All versions of
software with the same root and suffix are interchangeable.
P Part Number Paradigm. Software is identified by an alphanumeric drawing
identifier. Each release of software is identified by a different part identification
number defined on the same drawing. Interchangeability follows hardware part
interchangeability rules.

C-99
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

R Release Paradigm. Software is identified by a name or alphanumeric identifier

and each release is identified by an alphanumeric release identifier. This method
identifies chronological change, but does not address interchangeability. The
determination of interchangeability is left to the user of the software.

0164 engineering-change-proposal-document-change-class-code C R 2
The change classification code which represents and/or denotes whether the change described by the
ECP is classified as a Class I or Class II change. This DED is used in the following Table(s): 251.

The valid domain values for this element are as follows:

Domain
Value Meaning
I Class I. An ECP proposing a change to approved configuration documentation
for which the Government is the CDCA or that has been included in the contract
or statement of work by the tasking activity and either (1) affects any physical or
functional requirement in approved functional or allocated configuration
documentation, or (2) affects any approved functional, allocated, or product
configuration documentation and cost, warranties or contract milestones, or (3)
affects approved product configuration documentation, and one or more of the
following: (a) Government Furnished Equipment, (b) safety, (c) compatibility,
interoperability, or logistics support, (d) delivered technical manuals for which
changes are not funded, (e) will require retrofit of delivered units, (f) preset
adjustments or schedules affecting operating limits or performance to the extent
that a new identification number is required, (g) interchangeability,
substitutability or replaceability of any item down to non-repairable
subassemblies, (h) sources on a source control drawing, (i) skills, manning,
training, biomedical factors or human engineering design.
II Class II. An ECP proposing a change to approved configuration documentation
for which the Government is the CDCA or that has been included in the contract
or statement of work by the tasking activity and which is not Class I.

0165 engineering-change-proposal-document-justification-code C F 1
The justification code which represents and/or denotes the justification or reason for the preparation of
the engineering change described by the ECP. This DED is used in the following Table(s): 289.

The valid domain values for this element are as follows:

Domain
Value Meaning
B Interface. The engineering change proposes to eliminate incompatibility
between interfacing CIs.
C Compatibility. The engineering change proposes to correct a deficiency with the
following characteristics: (1) The need for the change has been discovered
during the system or item functional checks or during installation and checkout
and is necessary to make the system or item work. (2) The effort required to
accomplish the change is considered to be within the scope of the existing
contract except for changes caused by the tasking activity. (3) The contract
change documentation implementing the engineering change will not reflect an

C-100
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

increase in contract price for the corrective action for the items in production
and/or for already delivered items.
D Deficiency. The engineering change is required to eliminate a deficiency for
which there is not a more descriptive code.
O Operational or Logistics Support. The engineering change proposes to make a
significant effectiveness change in operational capabilities or logistics support.
P Production Stoppage. The engineering change is required to prevent slippage in
an approved production schedule. this code applies when production to the
current configuration documentation either is impracticable or cannot be
accomplished without delay.
R Cost Reduction. The engineering change proposes to provide a net total life
cycle cost savings to the Government, but which is not being submitted pursuant
to the Value Engineering clause of the contract. The savings in life cycle cost
should include all effects on cost and price for the effort and requirements
covered by the contract(s) currently in effect for this contractor, plus the costs
resulting from necessary associated changes in delivered items and logistics
support.
S Safety. The engineering change proposes to correct a deficiency and thus, to
eliminate a hazardous condition. When this code is assigned, a system hazard
analysis (per MIL-STD-882 or equivalent) is included with the ECP.
V Value Engineering. The engineering change proposes a change which will result
in a net life cycle cost reduction and which is submitted pursuant to the Value
Engineering clause of the contract.

0166 engineering-change-proposal-document-priority-code C F 1
The priority code which represents and/or denotes the precedence of engineering change processing and
approval. This DED is used in the following Table(s): 289.

The valid domain values for this element are as follows:

Domain
Value Meaning
E Emergency. To preclude serious compromise to national security, serious injury
or costly damage to equipments.
R Routine. Other than emergency or urgent.
U Urgent. Expeditious action to minimize undesirable impact.

0167 *agreement-type-code C F 1
The code that represents a specific kind of agreement. (Source of requirements: DDRS element
12,683.) This DED is used in the following Table(s): 975, 976.

The valid domain values for this element are as follows:

C-101
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
C Contract, including purchase orders, delivery orders under indefinite delivery
contracts, orders under basic ordering agreements, and calls under blanket
purchase orders.
T Treaty
U Understanding, including memorandum of agreement or understanding.

0168 program-configuration-control-board-discussion-text C L 9999

A free-form narrative text which captures the discussion of the CCB concerning a particular document
being considered by the CCB. In essence, this is the minutes of the CCB for a particular agenda item.
Must be a printable ASCII character, space, tab, line feed, page eject, and carriage return. This DED is
used in the following Table(s): 704.

0169 software-product-united-states-air-force--assigned-receiving- C F 2
country-place-code
The code which is assigned to represent the non-U.S. country for which a Computer Software
Configuration Item (CSCI) has been developed or to which a CSCI has been sold. Valid codes are
found in Military Assistance Sales Manual, DoD 5105.38-M, Part I, Appendix A-9. (Source of
requirements: USAF TO 00-15-16, USAF TO 00-5-17.)

This DED is used as part of the following DED string(s):

DED Title
0237 software-product-united-states-air-force--assigned-designation-identifier

0170 enterprise-name C L 30
The name of a company, organization or agency. Must be a printable ASCII character or embedded
space. This DED is used in the following Table(s): 004.

commercial-document-source-enterprise-name
The unique name of the company or other commercial enterprise which is the source of the document
and its identification. This DED is used in the following Table(s): 026, 027, 048, 049, 440, 441, 910,
911, 914, 926.

commercial-enterprise-name
The name of the company or other commercial enterprise that produces products or services. This DED
is used in the following Table(s): 005, 006, 166, 175, 922, 927, 928, 929.

design-enterprise-name
The name of a company which is responsible for design of a part or material. This DED is used in the
following Table(s): 154, 162, 165, 912, 913, 915, 916, 917, 918, 919, 920, 921, 923, 924, 925, 926.

C-102
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

proprietary-data-rights-commercial-enterprise-name
The name of a company which claims proprietary rights to data, documents or information. This DED
is used in the following Table(s): 011, 900.

0171 change-proposal-document-text C L 300

The text description for one particular aspect of an engineering change proposal. Must be a printable
ASCII character, space, tab, line feed, and carriage return.

change-proposal-document-change-description-text
The text of the change description resulting from an engineering change. This DED is used in the
following Table(s): 251.

change-proposal-document-change-justification-text
The text of the detailed explanation that describes the need for change, nature of improvement, defect,
failure, malfunction, etc. This DED is used in the following Table(s): 251.

change-proposal-document-production-delivery-schedule-effect-text
The text description of the effect of the change, if any, on delivery schedule and the estimated new
delivery schedule for the hardware/software incorporating the change. This DED is used in the
following Table(s): 251.

0172 engineering-change-proposal-document-cost-amount FXP R 2 9

T
The dollar cost of approving and implementing the engineering change proposal.

engineering-change-proposal-document-estimated-production-cost-
amount
The bugetary estimate in dollars of the increased/decreased cost of production of the specified units with
the proposed change incorporated. This DED is used in the following Table(s): 289.

engineering-change-proposal-document-estimated-research-cost-amount
The bugetary estimate in dollars of the cost of research, development, test, and evaluation of the
proposed change. This DED is used in the following Table(s): 289.

engineering-change-proposal-document-estimated-total-cost-amount
The estimated total dollar cost of approving and implementing the engineering change proposal. This
DED is used in the following Table(s): 289.

C-103
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

engineering-change-proposal-document-estimated-under-contract-
subtotal-cost-amount
The estimated dollar cost (which is applicable to the current contract) of approving and implementing
the engineering change proposal. This DED is used in the following Table(s): 289.

0173 program-configuration-control-board-type-code C F 1
A code which denotes whether a configuration control board is responsible for a system, one or more
configuration items, or both. This DED is used in the following Table(s): 700.

The valid domain values for this element are as follows:

Domain
Value Meaning
B Responsible for both a System and one or more CIs
C Responsible for one, or more, CIs, only
S Responsible for a System, only

0174 product-assembly-status-code C F 1
The standard code which represents and/or denotes the status of a component part/material relative to
the assembly in which it is or was installed. This DED is used in the following Table(s): 242, 243, 244,
245.

The valid domain values for this element are as follows:

Domain
Value Meaning
I Component is installed
R Component has been removed

0175 product-tracking-identifier S 16
The concatenation of a code indicating the type of sequential tracking identifier and the actual value of
the sequential tracking identifier used to identify a specific item (or batch of items) in a series of like
items. For example: "L123456789012345" where 'L' indicates a lot number and the
'123456789012345' is the specific lot number.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0057 product-change-effectivity-tracking-type-code
0058 product-sequential-tracking-identifier

assembly-product-tracking-identifier
The product tracking identifier sequentially assigned to equipment/parts at the assembly level. This
DED is used in the following Table(s): 242, 243, 244.

C-104
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

component-material-product-tracking-identifier
The product tracking identifier sequentially assigned to a material which is used as a component of a
higher-level assembly. This DED is used in the following Table(s): 243, 244.

component-part-product-tracking-identifier
The product tracking identifier sequentially assigned to a part which is used as a component of a higher-
level assembly. This DED is used in the following Table(s): 242.

component-product-lot-tracking-identifier
A product tracking identifier which is assigned to track a lot of material (or parts) which is a component
of a higher level assembly or of a regrouped lot of the material or part. This DED is used in the
following Table(s): 524, 527.

product-block-tracking-identifier
The product tracking identifier which is used to refer to a block of product serial or lot numbers. Block
numbers may be used for stating effectivity on ECPs and RFDs, but are not identifiers in the sense that
they are marked on parts. Aircraft normally are tracked by block numbers in addition to tail numbers.
This DED is used in the following Table(s): 520, 521, 522, 525, 528.

product-government-serial-tracking-identifier
A product tracking identifier which is assigned by the government tasking activity to an individual part
and is unique and non-duplicating for all items with the same product-tracking base-identifier. This
DED is used in the following Table(s): 517, 522, 532.

product-lot-tracking-identifier
A product tracking identifier assigned to a batch of material or group of like items. This DED is used
in the following Table(s): 518, 521, 522, 523, 525, 526, 528, 533, 534.

product-manufacturer-serial-tracking-identifier
A product tracking identifier which is assigned by the manufacturer to an individual part and is unique
and non-duplicating for all items with the same product-tracking base-identifier. This DED is used in
the following Table(s): 516, 521, 522, 531.

product-manufacturing-datecode-tracking-identifier
The product tracking identifier which is assigned by the manufacturer to a batch of like items based
upon the date of manufacture of the item. This DED is used in the following Table(s): 519, 529, 530.

regrouped-product-lot-tracking-identifier
A product tracking identifier assigned to a lot of parts (or material) which has been formed by the
consolidation of small lots of the same part (or material). This DED is used in the following Table(s):
524, 527.

C-105
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0176 revision-notice-document-implementation-authorization-code C F 1
A code which denotes and/or represents whether authority is granted for implementation of the approved
NOR prior to incorporation into the drawing or specification. This DED is used in the following
Table(s): 309, 863.

The valid domain values for this element are as follows:

Domain
Value Meaning
N NOR shall not be used for manufacture until receipt of revised document.
Document custodian shall incorporate this revision and furnish revised
document.
Y NOR may be used for manufacture in conjunction with the existing document.

0177 software-product-united-states-air-force--assigned-revision- C F 6
identifier
The identifier of the revision of a computer product identification number (CPIN) as assigned by U.S.
Air Force (OC-ALC/MMEC). The first three positions must be the letters 'REV'. The last three
positions are the numbers from 001 to 999. (Source of requirements: USAF TO 00-5-16, USAF TO
00-5-17.)

This DED is used as part of the following DED string(s):

DED Title
0237 software-product-united-states-air-force--assigned-designation-identifier

0178 document-procuring-activity--assigned-identifier C L 9
An identifier used by ARDEC organizations as an alias identifier for ECPs and RFDs. (Source of
requirements: ARDEC.) This DED is used in the following Table(s): 670, 671, 672.

0179 software-product-united-states-air-force--assigned-category-code C F 2
The code which is part of the U.S. Air Force Computer Product Identification Number (CPIN) and
which identifies the category of software to which the CPIN applies. (Source of requirements: USAF
TO 00-15-16, USAF TO 00-15-17.)

This DED is used as part of the following DED string(s):

DED Title
0061 software-product-united-states-air-force--assigned-identifier

The valid domain values for this element are as follows:

Domain
Value Meaning
81 Aircraft
82 Missiles
83 Ground Communications-Electronics
84 Simulators or Trainers

C-106
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

85 Test Stations or Testers

87 General Purpose Computers
88 Other Computer Programs
89 Space and Space Vehicles
91 Command and Control

0180 change-proposal-document-contractor-field-service-effect-code C F 1
The code that denotes whether contractor field service engineering is required to support the proposed
change. This DED is used in the following Table(s): 290.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No
Y Yes

0181 part-product-revision-identifier C R 2
The identifier of the specific revision, in a series of revisions, to a part to indicate that the part design
has been modified or changed. The designator will normally be sequentially assigned. Must be either
uppercase letters or numbers or a dash -(-). This DED is used in the following Table(s): 925, 926.

0182 software-product-united-states-air-force--assigned-major- C F 1
function-code
The code which is part of the U.S. Air Force Computer Product Identification Number (CPIN) and
which identifies the major function of an embedded computer software (ECS) computer software
configuration item (CSCI). (Source of requirements: USAF TO 00-15-16, USAF TO 00-15-17.)

This DED is used as part of the following DED string(s):

DED Title
0061 software-product-united-states-air-force--assigned-identifier

The valid domain values for this element are as follows:

Domain
Value Meaning
A Operational Flight
B Electronic Warfare
C Communications
D Data Processing or Display
E Engines
F Flight Controls
G Guidance
H Navigation
J Weapons Delivery
K Fire Control
L Missile Launch

C-107
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

M Metrology
N Environmental and Egress
P Photography
Q Electronic and Electrical
R Armament and Munitions
S Fuel
T Multiple Major Functions
U Hydraulic, Pneumatic, Pneudraulic, Vacuum
W Surveillance/Tracking/Identify Friend or Foe (IFF)
X Not Used
Y Not Used
Z Other

0183 software-product-united-states-air-force--assigned-applicable- C L 12
system-identifier
The identifier which is part of the U.S. Air Force assigned Computer Product Identification Number
(CPIN) and which identifies the hardware system and/or subsystem in which the software is used. The
content of this field is an abbreviation of the configuration item designation. Characters are restricted to
uppercase letters, numbers and the characters dash -(-), virgule (/), and parenthesis (( )). (Source of
requirements: USAF TO 00-15-16, USAF TO 00-15-17.)

This DED is used as part of the following DED string(s):

DED Title
0061 software-product-united-states-air-force--assigned-identifier

0184 predicted-asset-service-period-downtime-days-quantity FXP R 2 6

T
The length of time in days and hundredths of a day that the system or equipment will be out of service
because of the engineering change. This DED is used in the following Table(s): 263.

0185 implementation-process-action-item-description-text C L 320

The free-form text narrative description of the action necessary to implement a particular aspect of the
engineering change proposal or request for deviation. Must be a printable ASCII character, space, tab,
line feed, and carriage return.

deviation-implementation-process-action-item-description-text
The free-form text narrative description of the action necessary to implement a particular aspect of the
request for deviation. This DED is used in the following Table(s): 370.

engineering-change-implementation-process-action-item-description-text
The free-form text narrative description of the action necessary to implement a particular aspect of the
engineering change proposal. This DED is used in the following Table(s): 262.

C-108
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0186 commercial-product-inventory-stock-identifier C L 32
The identifier assigned by a company to a part, material, or family of parts and/or materials for
warehousing, inventory control, and internal reference of the item. It may also be used for cataloging
and external ordering of parts sold by, but not designed by, the company. Must be printable ASCII
characters. This DED is used in the following Table(s): 927, 928, 929.

0187 primary-engineering-change-proposal-document-indicator-code C F 1
The code which represents or denotes whether an ECP is a primary ECP with related ECPs associated
with it, or is related to a primary ECP. This DED is used in the following Table(s): 251.

The valid domain values for this element are as follows:

Domain
Value Meaning
N Not related to any other ECPs
P Primary ECP
R Related ECP
S Sequential implementation required between otherwise unrelated ECPs

0188 software-product-united-states-air-force--assigned-type-code C F 1
The code which is part of the computer product identification number (CPIN) and which identifies the
application of the CPIN. (Source of requirements: USAF TO 00-15-16, USAF TO 00-15-17.)

This DED is used as part of the following DED string(s):

DED Title
0061 software-product-united-states-air-force--assigned-identifier

The valid domain values for this element are as follows:

Domain
Value Meaning
C Combination of types of software
D Master (denotes a combination of software of a single type)
F Operational Software
S Support Software
T In Place Test Software
U Unit Under Test Software

0189 software-product-united-states-air-force--assigned-version- C F 2
identifier
The identifier which is part of the computer product identification number (CPIN) and which identifies a
particular version of a computer software configuration item (CSCI), group of CSCIs, or CSCI
engineering documentation. Characters are limited to the digits 00 through 99. (00 will always denote
the initial product baseline version.) (Source of requirements: USAF TO 00-15-16, USAF TO 00-15-
17.)

C-109
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

This DED is used as part of the following DED string(s):

DED Title
0061 software-product-united-states-air-force--assigned-identifier

0190 software-product-basic-application-alphanumeric-identifier C L 8
The identifier which represents all releases and versions of a software program or database. Must be
numbers or capital letters (excluding O). This DED is used in the following Table(s): 155, 156.

This DED is used as part of the following DED string(s):

DED Title
0088 software-product-alphanumeric-identifier

0191 material-product-name C L 120

The name which identifies a material, for example, Nylon-66, elastomeric putty, trichloro-ethane,
enamel paint, etc. Must be a printable ASCII character or embedded space. (This is equivalent to MIL-
PRF-49506 DED 0480.) This DED is used in the following Table(s): 200, 922, 924.

0192 material-document-identifier S 39
An identifier of a document which defines a material. This DED is used in the following Table(s): 103,
106, 107, 201, 421, 422, 433, 434, 435, 916, 918, 923.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0004 document-type-code
0003 document-alphanumeric-identifier

0193 program--unique-specification-change-notice-document- C R 2
sequential-identifier
The identifier of a specific change notice in a series of specification change notices to a program-unique
specification at a specific revision Must be the numbers 1 through 99. This DED is used in the
following Table(s): 620.

0194 engineering-change-proposal-document-format-type-code C F 1
A code which denotes and/or indicates the type of Engineering Change Proposal. This DED is used in
the following Table(s): 251.

The valid domain values for this element are as follows:

Domain
Value Meaning
F Final ECP. An ECP which provides engineering information and other data in
sufficient detail to support final change approval and contractual

C-110
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

implementation. (The content will differ depending on the contractual

relationship between the performing and tasking activities, what organization is
proposing the change, and what organization is the current document change
authority for the document addressed by the proposed change.)
M Message ECP. An ECP which, in the originator's judgement, (a) carries a
priority of emergency or urgent, and requires immediate action, or (b) warrants a
justification code of 'compatibility' (all aspects of the compatibility code must
apply. In either case, the ECP may be initiated verbally (by telephone or
personal contact), or in writing (by hard copy or electronic message). When the
initial contact is verbal, a follow-up written confirmation is required, followed by
a class I ECP. With initial favorable reaction, corrective action may be
implemented immediately by the performing activity to resolve incompatibilities,
but only for the specific item(s) situated in the location at which the deficiency
was originally discovered.
P Preliminary ECP. The purpose is: (1) to furnish the tasking activity with very
brief, preliminary information on a routine priority proposed change idea in
order to decide whether to authorize the additional work necessary to generate a
final ECP; or (2) to supplement a message ECP relative to an emergency or
urgent priority ECP when it is impractical to document and submit a final ECP
within 30 calendar days of the message ECP; or (3) during production, for those
instances where the change originator did not develop the prescribed detail
design, and therefore does not know the total impact of the change being
requested, to provide sufficient data on the proposed change to permit the
current document change authority to evaluate the proposal, adding whatever
data is necessary to the change proposal for this purpose; or (4) to permit (a)
analysis and selection of the most attractive of several proposed alternative
concepts; (b) analysis of the proposed hardware or software design prior to the
actual building and testing of the hardware or coding and testing of the software;
or (c) evaluation of preliminary test data documenting the merits of the proposed
design (for example: installation, evaluation, and testing of prototype hardware
or software).

0195 engineering-change-proposal-document-retrofit-installation- C F 1
level-code
A code that identifies the echelon level of maintenance needed to perform the work associated with a
retrofit requirement. This DED is used in the following Table(s): 263.

The valid domain values for this element are as follows:

Domain
Value Meaning
D Depot
I Intermediate
O Operational or field

0196 technical-manual-document-iteration-type-code C F 1
A code which denotes the type of document iteration series, for example: revision, change, supplement,
etc. This DED is used in the following Table(s): 554.

C-111
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

The valid domain values for this element are as follows:

Domain
Value Meaning
C Change number (or letter)
D Revision issue date
S Supplement

0197 contract-data-requirement-list-document-item-submission- C L 5
frequency-code
A code which denotes and/or represents how often an item on the contract data requirements list item
must be submitted. (Source of requirements: DoDM 5010.12-M.) This DED is used in the following
Table(s): 953.

The valid domain values for this element are as follows:

Domain
Value Meaning
ANNLY Annually (on anniversary of first submittal)
ASGEN As generated
ASREQ As required
BI-MO Bi-monthly (on anniversary of first submittal)
BI-YR Bi-ennially (on anniversary of first submittal)
DAILY Daily
DFDEL Deferred delivery
MTHLY Monthly (on anniversary of first submittal)
ONE/P One preliminary
ONE/R One time with revisions
QRTLY Quarterly (on anniversary of first submittal)
R/ASR Revisions as required
RTIME Real Time
SEMIA Every six months (on anniversary of first submittal)
WEKLY Weekly (on anniversary of first submittal)
XTIME Number of times to be submitted where X is a number between 1 and 9

0198 contract-modification-document-affect-code C F 1
A code that denotes and/or represents the affect of a contract modification on a particular section of an
existing contract.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No effect on contract contents
Y Section has been affected

contract-modification-document-address-list-affect-code
A code that indicates the effect of a contract modification on the address list of the contract. This DED
is used in the following Table(s): 951.

C-112
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

contract-modification-document-contract-data-requirements-list-affect-
code
A code that indicates the effect of a contract modification on the contract data requirements list portion
of the contract. This DED is used in the following Table(s): 951.

contract-modification-document-delivery-schedule-affect-code
A code that indicates an effect of a contract modification on the delivery schedule of the contract. This
DED is used in the following Table(s): 951.

contract-modification-document-distribution-statement-affect-code
A code that indicates the effect of a contract modification on the distribution statement applicable to the
contract. This DED is used in the following Table(s): 951.

contract-modification-document-other-attachment-affect-code
A code that indicates the effect of a contract modification on other attachments to the contract. This
DED is used in the following Table(s): 951.

contract-modification-document-other-exhibit-affect-code
A code that indicates the effect of a contract modification on other exhibits of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-a-affect-code
A code that indicates an effect of a contract modification on schedule A of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-b-affect-code
A code that indicates the effect of a contract modification on Schedule B of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-c-affect-code
A code that indicates the effect of a contract modification on Schedule C of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-d-affect-code
A code that indicates the effect of a contract modification on Schedule D of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-e-affect-code
A code that indicates the effect of a contract modification on Schedule E of the contract. This DED is
used in the following Table(s): 951.

C-113
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

contract-modification-document-schedule-f-affect-code
A code that indicates the effect of a contract modification on Schedule F of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-g-affect-code
A code that indicates the effect of a contract modification on Schedule G of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-h-affect-code
A code that indicates the effect of a contract modification on Schedule H of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-i-affect-code
A code that indicates the effect of a contract modification on Schedule I of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-j-affect-code
A code that indicates the effect of a contract modification on Schedule J of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-schedule-k-affect-code
A code that indicates the effect of a contract modification on Schedule K of the contract. This DED is
used in the following Table(s): 951.

contract-modification-document-work-statement-affect-code
A code that indicates the effect of a contract modification on the statement of work as a result of a
change. This DED is used in the following Table(s): 951.

0199 contract-data-requirement-list-document-item-price-group-code C F 1
The code which denotes and/or represents the price group of the contract data item as determined by the
availability of the data. (Source of requirements: DoDM 5010.12-M.) This DED is used in the
following Table(s): 953.

The valid domain values for this element are as follows:

Domain
Value Meaning
1 Group I. Data that the contractor prepares to satisfy the Government's
requirements. The contractor does not need this type of data to perform the rest
of the contract. Price would be based on identifiable direct costs, overhead,
general and administrative (G&A), and profit.
2 Group II. Data essential to contract performance which must be reworked or
amended to conform to Government requirements. The price for data in this

C-114
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

group would be based on the direct cost to convert the original data to meet
Government needs and to deliver it, plus allocable overhead, G&A, and profit.
3 Group III. Data that the contractor must develop for the contractor's use and that
requires no substantial change to conform to Government requirements on depth
of content, format, frequency of submittal, preparation, and quality of data. Only
the costs of reproducing, handling and delivery, plus overhead, G&A, and profit,
are considered in pricing data in this group.
4 Group IV. Data that the contractor has developed as part of the contractor's
commercial business. Not much of this data is required and the cost is
insignificant. The item should normally be coded "no charge." An example is a
brochure or brief manual developed for commercial application which will be
acquired in small quantities, and the added cost is too small to justify the
expense of computing the charge that otherwise would go with the acquisition.

0200 contract-data-requirement-list-document-item-price-amount FXP R 2 7

T
The dollar price of the data item. (Source of requirements: DoDM 5010.12-M.) This DED is used in
the following Table(s): 953.

0201 contract-data-requirement-list-document-form-category-code C L 4
A code that indicates the category of data addressed by a contract data requirements list. (Source of
requirements: DOD 5010.12-L.) This DED is used in the following Table(s): 952.

The valid domain values for this element are as follows:

Domain
Value Meaning
ADMN Administrative
ALSS Acquisition Logistics Standards and Specifications
ATTS Automatic Test Technology Standards
CDNC Computer-aided Design/Numerical Control
CMAN Configuration Management
CMPS Composites Technology
DCPS Data Communications Protocol Standards
DRPR Drawing Practices
EDRS DoD Engineering Data Reproduction Systems
EGDS Engineering Data Systems
EMCS Electromagnetic Compatibility
ENVR Environmental Requirements and Related Test Methods
FACR Facility Construction Design Requirements
FNCL Financial Data
FORG Forgings
GDRQ General Design Requirements
HFAC Human Factors
IPSC Information Processing Standards for
MCCR Mission Critical Computer Resources
MECA Metal Castings
MFFP Metal Finishing & Finishing Processes & Procedures

C-115
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

MGMT Management
MISC Miscellaneous
MNTY Maintainability
NDTI Nondestructive Testing & Inspection
NUOR Nuclear Ordnance
PACK Packing, Packaging. Preservation and Transportability
QCIC Quality Control/Assurance and Inspection
RELI Reliability
SAFT Safety
SDMP Standardization and Data Management
SLHC Long-Haul Communications
SOLD Soldering
TCSP Technical Support
TCTS Tactical Communications Systems Technical Standards
TDP Technical Data Package
THDS Screw Threads
THJM Thermal Joining of Materials
TMSS Technical Manual Specifications and Standards

0202 shipping-document-requirement-code C F 2
A code indicating whether or not a DD Form 250 is required for delivery of the data item and the
location of inspection and acceptance of the data item. (Source of requirements: DoDM 5010.12-M.)
This DED is used in the following Table(s): 953.

The valid domain values for this element are as follows:

Domain
Value Meaning
DD DD Form 250 required, no inspection performed at source, final inspection at
destination; acceptance at destination.
DS DD Form 250 required; no inspection performed at source, final inspection at
destination; acceptance at source.
LT No DD Form 250; letter of transmittal only; inspection and acceptance required
as specified in remarks.
NO No DD Form 250 required; no letter of transmittal required; no inspection or
acceptance required.
SD DD Form 250 required; inspection at source; acceptance at destination.
SS DD Form 250 required; inspection at source; acceptance at source.
XX Inspection and acceptance requirements specified elsewhere in the contract.

0203 contract-data-requirement-list-document-item-approval- C F 1
requirement-code
A code that denotes and/or represents whether government approval is required for the data item.
(Source of requirements: DoDM 5010.12-M.) This DED is used in the following Table(s): 953.

The valid domain values for this element are as follows:

C-116
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
N No, government approval is not required
Y Yes, approval is required

0204 contract-data-requirement-list-document-item-remark-text C L 400

The text description that elaborates upon the requirements for a data item on the contract data
requirements list. Must be a printable ASCII character, space, tab, line feed, and carriage return.
(Source of requirements: DoDM 5010.12-M.) This DED is used in the following Table(s): 953.

0205 contract-data-requirement-list-document-item-modification- C F 1
symbol-code
A code added to the Data Item Number (ELIN) to indicate if the contract data requirements list (CDRL)
item has been added, deleted or revised since the initial issue of the CDRL. Valid characters are plus
(+) meaning added, dash -(-) meaning deleted, and 'R' meaning revised. (Source of requirements:
DoDM 5010.12-M.) This DED is used in the following Table(s): 953.

0206 electronic-document-file-identifier C L 32
The identifier which represents a single unit of information for storage in a computer. This DED is used
in the following Table(s): 232, 252, 261, 314, 358, 802, 900, 901, 903.

electronic-document-comment-file-identifier
The identifier which represents a digital or other electronic file which contains comments about a
document. This DED is used in the following Table(s): 812, 858, 867, 968.

electronic-document-representation-file-identifier
The identifier of a file which is used as part (or all) of a document representation. This DED is used in
the following Table(s): 812, 858, 867, 968.

0207 document-representation-identifier C L 32
The identifier which represents a set of digital (or other) files which, when viewed together, collectively
represent the entire document. (For example, a set of raster files, a set of IGES files, a set of paper
pages. This DED is used in the following Table(s): 800, 801, 802, 803, 804, 805, 806, 807, 811, 812,
858, 861, 867, 966, 968.

0208 document-representation-revision-identifier C L 2
The identifier which represents a specific iteration in a sequential series of iterations of a document
representation. Must be uppercase letters (excluding O), numbers, or dash -(-). This DED is used in the
following Table(s): 801, 802, 803, 804, 805, 806, 807, 811, 812, 858, 861, 867, 966, 968.

C-117
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0209 electronic-storage-place-identifier S 128

The identifier which represents the electronic storage location of a digital or other electronic file. It may
be a directory identifier/path with a file name and extension, or it may be an internal operating system
pointer to the storage location.

application-software-product-electronic-storage-place-identifier
The identifier which represents the electronic storage location of application software. It may be a
directory identifier/path with a file name and extension, or it may be an internal operating system pointer
to the storage location. This DED is used in the following Table(s): 902, 903.

application-software-product-launch-script-electronic-storage-place- Size: 64
identifier
The identifier which represents the electronic storage location of the software instructions necessary for
automatically initiating recall and use of specific application software. It may be a directory
identifier/path with a file name and extension, or it may be an internal operating system pointer to the
storage location. This DED is used in the following Table(s): 902.

document-file-electronic-storage-place-identifier Size: 64
The identifier which represents the electronic storage location of a digital or other electronic file. It may
be a directory identifier/path with a file name and extension, or it may be an internal operating system
pointer to the storage location. This DED is used in the following Table(s): 900.

0210 document-file-type-code C L 6
The code that represents or denotes the general type of an electronic file. This DED is used in the
following Table(s): 900.

The valid domain values for this element are as follows:

Domain
Value Meaning
ASCII American Standard Code for Information Interchange
CGM Computer Graphics Metafile
DSSSL Document Style Semantics Specification Language
EDIF Electronic Design Interchange Format
EPS Encapsulated Post Script page description language
FOSI Formatting Output Specification Instance
HPGL Hewlett-Packard Graphics Language page description language
HTML HyperText Markup Language
HYTIME HYpermedia/TIME-based structuring language
IGES3 Initial Graphics Exchange Specification, Version 3
IGES4 Initial Graphics Exchange Specification, Version 4
IPC Integrated Printed Circuit
MPEG Motion Picture Experts Group
PDF Portable Document File
PLANG Proprietary Language. A file which can only be accessed for view or edit by use
of a specific software application which is proprietary to a particular company.

C-118
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

PS Post Script page description language (registered trademark of Adobe, Inc.)

RAST3 Raster Graphics, Group 3
RAST4 Raster Graphics, Group 4
SGML Standard Generalized Markup Language
SPDL Standard Page Description Language
STEP STandard for the Exchange of Product data
TIFF Tagged Image File Format
VHDL Very High Speed Integrated Circuit (VHSIC) Hardware Description Language

0211 document-file-name C L 32
The name of a digital or other electronic file. Must be a printable ASCII character or embedded space.
This DED is used in the following Table(s): 900.

0212 document-file-description-text C L 120

The text describing the content and/or usage of a digital or other electronic file. Must be a printable
ASCII character, space, tab, line feed, and carriage return. This DED is used in the following Table(s):
900.

0213 computer-operating-system-asset-type-code C L 8
The code which represents or denotes a specific type of computer operating system software. This DED
is used in the following Table(s): 900.

The valid domain values for this element are as follows:

Domain
Value Meaning
APPLE Apple OS
IMS IBM Information Management System
MS-DOS Microsoft Disk Operating System
OS2 IBM Operating System-2
OS2-WARP IBM WARP Operating System
PC-DOS IBM PC Disk Operating System
SUN-OS SUN Operating System
TI-DOS Texas Instruments Disk Operating System
UNIX UNIX Operating System
VMS VAX Virtual Management System
WIN-95 Microsoft Windows Operating System
WIN-NT Microsoft Windows, NT Operating System
WINDOWS Microsoft Windows Operating System

0214 document-file-compression-method-code C F 3
The code which represents or denotes the method or software used to compress the data in a digital file.
This DED is used in the following Table(s): 900.

C-119
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

The valid domain values for this element are as follows:

Domain
Value Meaning
ARC An MS-DOS based file compression method
TAR A UNIX-based file compression method
ZIP An MS-DOS based file compression method

0215 document-file-compression-code C F 1
The code which represents or denotes whether or not a digital file has been compressed for storage.
This DED is used in the following Table(s): 900.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, the file is not compressed for storage
Y Yes, the file is compressed for storage

0216 document-representation-release-type-code C F 3
A code which represents or denotes the type of release action which has been authorized. This DED is
used in the following Table(s): 806.

The valid domain values for this element are as follows:

Domain
Value Meaning
FUL Release allows unrestricted use.
LIM Release is limited to use for specific actions, including submittal to an external
customer for approval.
SUB Release is limited to use as a submittal to an external customer for approval.

0217 document-representation-release-limitations-text C L 500

The text describing the limitations placed on the use of a released document representation. Must be a
printable ASCII character, space, tab, line feed, and carriage return. This DED is used in the following
Table(s): 806.

0218 changed-technical-manual-document-identifier S 42
The identifier of a specific change to a specific revision of a specific technical manual or order. This
DED is used in the following Table(s): 572, 573, 611, 612, 613, 614, 616, 617, 618, 619.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0135 revised-technical-manual-document-identifier
0134 technical-manual-change-document-identifier

C-120
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0219 julian-year-period-identifier C F 4
The unique set of digits assigned using the Julian calendar system to represent a specific 12-month
period of time starting on the first day of January and ending on the last day of December. The
acceptable range of values is 0001 through 9999. This DED is used in the following Table(s): 670,
671, 672.

0220 deviation-request-document-part-level-code C F 1
A code which represents and/or denotes whether the part number is the "lowest level" part addressed by
the RFD, the effectivity base for the RFD, or both. This DED is used in the following Table(s): 353,
360, 365.

The valid domain values for this element are as follows:

Domain
Value Meaning
B Both
E Basis for effectivity
L Lowest level part

0221 software-product-united-states-air-force--assigned-sequence- C F 3
identifier
The identifier which is part of the computer product identification number (CPIN) and which identifies
the sequence number of a series of related computer software configuration items (CSCIs), or different
types of media for storage of the CSCI. The contents are restricted to the digits 000 through 999.
(Source of requirements: USAF TO 00-15-16, USAF TO 00-15-17.)

This DED is used as part of the following DED string(s):

DED Title
0061 software-product-united-states-air-force--assigned-identifier

0222 software-product-application-suffix-alphanumeric-identifier C L 6
The identifier of the specific significant release of a software program or database within a family of
related releases of the software program or database. Must be a number. This DED is used in the
following Table(s): 156.

This DED is used as part of the following DED string(s):

DED Title
0088 software-product-alphanumeric-identifier

0223 engineering-change-proposal-document-in--production-code C F 1
A code that indicates whether the equipment to which the ECP applies is in production. This DED is
used in the following Table(s): 251.

C-121
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

The valid domain values for this element are as follows:

Domain
Value Meaning
N No
Y Yes

0224 enterprise-security-classified-document-receipt-authorization- C L 1
code
A code which represents and/or denotes the highest level of security-classified documents which may be
received. This DED is used in the following Table(s): 941.

The valid domain values for this element are as follows:

Domain
Value Meaning
C Confidential and lower level classifications only.
S Secret and lower level classifications only.
T Top Secret and lower level classifications only.
U Unclassified only.

0225 human-access-identifier C L 60
The identifier of the electronic- or voice-access address which is used to contact a person; for example:
a telephone number or electronic mail (EMail) address.

human-electronic-mail-access-identifier
The identifier which is the electronic mail (EMail) address of a person. Limited to letters, numbers,
decimals (.), dashes -(-), at (@), underscore (_) and percent (%). This DED is used in the following
Table(s): 943.

human-facsimile-machine-access-identifier Size: 15
The identifier of a telephone number which is used for receipt of facsimile transmissions of documents.
This is in the format of country code-number. In the U.S., the number is in the format xxx-yyy-zzzz
where xxx is the area code, yyy is the exchange and zzzz is the local number. Other number formats
may be used with other country codes. The country code is optional for systems which can only be
accessed within a country. Limited to uppercase letters (except Q and Z), numbers, and dashes -(-).
This DED is used in the following Table(s): 942, 943.

human-telephone-access-identifier Size: 20
The telephone number of a person. In the format of country code-number-extension. In the U.S., the
number is in the format xxx-yyy-zzzz where xxx is the area code, yyy is the exchange and zzzz is the
local number. Other number formats may be used with other country codes. The country code is
optional for systems which can only be accessed within a country. The extension is always optional.
Limited to uppercase letters (except Q and Z), numbers, and dashes -(-). This DED is used in the
following Table(s): 942, 943.

C-122
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0226 contract-document-alphanumeric-identifier C L 21
The document identifier which represents the complete and unique identification number of, and
primary reference to, a contract. This includes delivery orders under indefinite delivery contracts,
orders under basic ordering agreements, and calls under blanket purchase orders. This is one type of
agreement-identifier. Must be uppercase letters, numbers and dashes -(-); no other special characters are
allowed. (Source of requirements: DFAR 204.7003(b), DFAR 204.7004(d).) This DED is used in the
following Table(s): 977.

This DED is used as part of the following DED string(s):

DED Title
0015 contract-document-identifier

0227 contract-document-fee-type-code C L 4
A code which represents and/or denotes the type of pricing/fee arrangement agreed to in the contract.
This DED is used in the following Table(s): 950.

The valid domain values for this element are as follows:

Domain
Value Meaning
CPAF Cost Plus Award Fee
CPFF Cost Plus Fixed Fee
CPIF Cost Plus Incentive Fee
FFP Firm Fixed Price
FPIF Fixed Price Incentive Fee

0228 enterprise-division-identifier S 50
The identifier of an enterprise and a specific division or office within that enterprise.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0052 enterprise-identifier
0044 enterprise-office-name

application-activity-enterprise-division-identifier
The identifier of an activity (organization, company, etc. and specific division or office) which is not
the current document change authority designated for configuration control of a document, or document
representation, but which has incorporated the document into one or more of its baselines for use on the
program(s) under its control, or into one or more of its products, or is in the process of reviewing a
document or document representation for suitability for use in one or more of its baselines, programs or
products. Application activities can provide approval for use of a document or a change to a document;
however, this approval is limited to the program(s) for which it is responsible. Application activities
cannot direct incorporation of a change into the document. Application activities cannot approve or
direct implementation of a proposed change which is disapproved by the current document change
authority. This DED is used in the following Table(s): 033, 861, 862, 863, 864, 865, 866, 867, 967.

C-123
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

performing-activity-enterprise-technical-monitor-division-identifier
The identifier of the performing activity enterprise and division, or office, responsible for performing
the role of technical monitor for a contract. This DED is used in the following Table(s): 954.

tasking-activity-enterprise-technical-monitor-division-identifier
The identifier of the tasking activity enterprise and division, or office, responsible for performing the
role of technical monitor over a contract. This DED is used in the following Table(s): 953, 954.

0229 work-statement-document-identifier S 139

The complete identifier of a statement of work document, including the revision level. (Source of
requirements: MIL-HDBK-245.) This DED is used in the following Table(s): 680, 953, 957.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0052 document-source-enterprise-identifier
0122 document-identifier
0004 document-type-code
0243 document-generic-revision-identifier

0230 data-item-description-document-identifier S 13
The identifier which represents the complete and unique identification of, and primary reference to, a
Data Item Description (DID) document that describes the requirements for generating contract data
items. (Source of requirements: DOD 5010.12-L.) This DED is used in the following Table(s): 953.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0002 enterprise-acronym-identification-code
0003 document-alphanumeric-identifier
0004 document-type-code
0243 document-generic-revision-identifier

0231 period-length-quantity I R 4
The quantity of time in a period. Negative numbers indicate the period is measured prior to an event.
Positive numbers which are greater than zero indicate the period is measured after the event.

This DED is used as part of the following DED string(s):

DED Title
0234 contract-data-submittal-document-event--delta-text
0161 document-effective-cut--off-event-delta-text

C-124
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0232 period-unit-code C L 2
A code which represents and/or denotes a unit of time.

This DED is used as part of the following DED string(s):

DED Title
0234 contract-data-submittal-document-event--delta-text
0161 document-effective-cut--off-event-delta-text

The valid domain values for this element are as follows:

Domain
Value Meaning
DA Day
HR Hour
MI Minute
MO Month
WK Week
YR Year

product-service-life-period-unit-code
A code which denotes or signifies the unit of measure of the expected service life of an item. This DED
is used in the following Table(s): 200, 210.

0233 contract-data-requirement-list-document-delivery-due-code C F 5
A code that denotes or represents the contractually required time-frame for delivery of a contract data
item. (Source of requirements: DoDM 5010.12-M.)

The valid domain values for this element are as follows:

Domain
Value Meaning
ASGEN As generated
ASREQ As required
DFDEL Deferred delivery

contract-data-requirement-list-document-item-initial-delivery-due-code
A code which denotes or represents the contractually required time-frame for the first delivery of a
contract data item. This DED is used in the following Table(s): 953.

contract-data-requirement-list-document-item-subsequent-delivery-due-
code
A code which denotes or represents the contractually required time-frame for the second and subsequent
delivery of a contract data item. This DED is used in the following Table(s): 953.

C-125
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0234 contract-data-submittal-document-event--delta-text S 9
A text string which defines a date that a contract data item delivery is due expressed as a period of time
before or after an event.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0231 period-length-quantity
0232 period-unit-code
0018 process-event-code

contract-data-submittal-document-initial-delivery-event--delta-text
A text string which defines a date that the initial delivery of a contract data item is due expressed as a
period of time before or after an event. This DED is used in the following Table(s): 954.

contract-data-submittal-document-subsequent-delivery-event--delta-text
A text string which defines a date that the second or subsequent delivery of a contract data item is due
expressed as a period of time before or after an event. This DED is used in the following Table(s): 954.

0235 contract-data-submittal-document-resubmittal-requirement- S 36
identifier
The complete identifier of the disapproved data item submittal which necessitated the submittal of a
revised data item. This DED is used in the following Table(s): 956.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0015 contract-document-identifier
0120 contract-document-revision-identifier
0007 contract-document-exhibit-identifier
0005 contract-data-requirement-list-document-item-sequence-identifier
0020 contract-data-submittal-document-identifier
0099 contract-data-submittal-document-revision-identifier

0236 software-product-united-states-air-force--assigned-applicability- C F 1
code
The code which is part of the computer product identification number (CPIN) and which denotes
whether the CPIN is applicable to software or a software engineering documentation package. (Source
of requirements: USAF TO 00-15-16, USAF TO 00-15-17.)

This DED is used as part of the following DED string(s):

DED Title
0061 software-product-united-states-air-force--assigned-identifier

The valid domain values for this element are as follows:

C-126
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

Domain
Value Meaning
A CSCI (executable or object code)
D Software Engineering Documentation Package

0237 software-product-united-states-air-force--assigned-designation- S 33
identifier
The identifier which is assigned by the U.S. Air Force (OC-ALC/MMEDUE) to a computer software
configuration item (CSCI) and which uniquely identifies a specific revision and version of a CSCI,
combination of CSCIs, or CSCI engineering documentation package, and, the country for which it was
prepared. (Source of requirements: USAF TO 00-15-16, USAF TO 00-5-17.) This DED is used in the
following Table(s): 190, 191, 192, 194.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0169 software-product-united-states-air-force--assigned-receiving-country-place-code
0061 software-product-united-states-air-force--assigned-identifier
0177 software-product-united-states-air-force--assigned-revision-identifier

combination-software-product-united-states-air-force--assigned-
designation-identifier
The identifier which is assigned by the U.S. Air Force (OC-ALC/MMEDUE) to a computer software
configuration item (CSCI) and which uniquely identifies a specific revision and version of a group of
CSCIs or a multi-use CSCI engineering documentation package, and, the country for which it was
prepared. This DED is used in the following Table(s): 193.

component-software-product-united-states-air-force--assigned-
designation-identifier
The identifier which is assigned by the U.S. Air Force (OC-ALC/MMEDUE) to a computer software
configuration item (CSCI) and which uniquely identifies a specific revision and version of a CSCI, or
CSCI engineering documentation package, and, the country for which it was prepared. This DED is
used in the following Table(s): 193.

0238 software-product-storage-medium-type-name C L 15
The name of the type of medium used to store a particular software product. Must be a printable ASCII
character. This DED is used in the following Table(s): 194.

0239 document-current-change-control-authority-identifier S 203

The identifier which represents the activity (organization, author, company, configuration control board,
etc.) which is currently responsible for the design content of the document and, therefore, is the sole
authority for approval of changes to the document. This DED is used in the following Table(s): 010.

This DED is comprised of the following data elements concatenated in the order listed:

C-127
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

DED Title
0033 entity-identifier
0044 enterprise-office-name
0059 program-name
0151 program-configuration-control-board-name
0111 configuration-item-product-identifier

0240 product-retrofit-requirement-code C F 1
A code which denotes and/or represents whether or not retrofit of existing units is recommended by an
ECP. This DED is used in the following Table(s): 289.

The valid domain values for this element are as follows:

Domain
Value Meaning
N No, retrofit is not necessary or recommended
Y Yes, retrofit is recommended/required

0241 document-parts-list-entry-component-type-code C F 1
A code which denotes and/or represents the type of item primarily associated with a parts list entry line
item. This DED is used in the following Table(s): 224, 316.

The valid domain values for this element are as follows:

Domain
Value Meaning
D Document number for a reference drawing or other miscellaneous document
M Material or part not identified by a part number
P Part number
S Software identifier (not software part number)

0242 standardization-document-series-type-code C L 6
The code which represents or denotes the type of document series issued for the purpose of
standardizing, regulating, or codifying practices, procedures, processes, material, etc. within a segment
of a company, industry, or government. For example: Military Specifications, Federal Standards, ISO
Application Protocols, EIA Bulletins, AECMA Documents, SAE Standard Practices, NATO Standard
NATO Agreements (STANAGs), etc. The list of values below is a partial list; other values may be
used as appropriate. Each organization should identify their own set of values for this code. (Source
of requirements: DoD 4120.3-M, Federal Standardization M, MIL-STD-961, MIL-STD-962.) This
DED is used in the following Table(s): 404, 405, 406, 407, 408, 409.

The valid domain values for this element are as follows:

Domain
Value Meaning
AP Application Protocol
BUL Bulletin
CFR Code of Federal Regulations

C-128
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

CID Commercial Item Description

DOC Document
FIPS Federal Information Processing Standard
GUIDE Guide or Guidebook
HDBK Handbook
INST Instruction
MANUAL Manual
PRACT Practice or Standard Practice
PROC Procedure or Standard Procedure
PUB Publication
QPL Qualified Products List
REG Regulation
SOI Standard Operating (or Operations) Instruction
SOP Standard Operating (or operations) Procedure
SPEC Specification
STANAG Standardized NATO Agreement
STD Standard

0243 document-generic-revision-identifier C L 8
The identifier of the specific revision, in a series of revisions, to a document or a portion of the
document (that is, sheet) to indicate that the document has been modified or changed. The designator
may be a date or may be a sequentially assigned letter or number or similar identifier. Must be
uppercase letters (except O) and/or numbers, a dash -(-), or a date. (Source of requirements: MIL-M-
38784.) This DED is used in the following Table(s): 011, 019, 021, 023, 025, 027, 041, 043, 045, 047,
049, 151, 152, 153, 256, 270, 271, 284, 288, 293, 305, 310, 332, 352, 401, 403, 422, 423, 431, 435,
437, 441, 551, 554, 555, 601, 651, 681, 704, 801, 806, 807, 850, 851, 852, 853, 854, 855, 857, 858,
861, 862, 863, 864, 865, 866, 867, 911, 926, 965, 967.

This DED is used as part of the following DED string(s):

DED Title
0230 data-item-description-document-identifier
0229 work-statement-document-identifier

assembly-model-database-document-generic-revision-identifier
The identifier of the revision/version of a database of an assembly model. This DED is used in the
following Table(s): 233.

component-document-generic-revision-identifier
The identifier of the specific revision, within a series of revisions, of a document which is listed in a
higher level document as a component. For example: a document listed in a data list drawing. This
DED is used in the following Table(s): 071.

component-part-model-database-document-generic-revision-identifier
The identifier of the revision of a database of a component part model. This DED is used in the
following Table(s): 233.

C-129
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

document-current-generic-revision-identifier
The identifier of the current specific revision, in a series of revisions, to a document. This identifier is
used in contrast to the superseded document revision which is replaced as the result of ECP approval.
This DED is used in the following Table(s): 258, 266.

part-model-database-document-generic-revision-identifier
The identifier of the revision/version of a part model. This DED is used in the following Table(s): 231,
232.

referenced-document-generic-revision-identifier
The identifier of a specific revision, in a series of revisions, to a document which is included as a
document. This DED is used in the following Table(s): 082, 110.

software-support-document-generic-revision-identifier
The identifier which represents the specific revision, in a series of revisions, to a software support
document. This DED is used in the following Table(s): 186, 187.

0244 supplement-document-sequential-identifier C R 3
The identifier of a specific supplement in a series of supplements to a document. Limited to the
characters 1 through 999.

technical-manual-operational-supplement-document-sequential-identifier
The identifier of a specific operational supplement in a sequence of operational supplements to a
specific technical manual/order at a specific revision and change. This DED is used in the following
Table(s): 572, 612, 617.

technical-manual-page-supplement-document-sequential-identifier
The identifier of a specific page supplement in a sequence of page supplements to a specific technical
manual/order at a specific revision and change. This DED is used in the following Table(s): 573, 614,
619.

technical-manual-routine-supplement-document-sequential-identifier
The identifier of a specific routine supplement in a sequence of routine supplements to a specific
technical manual/order at a specific revision and change. This DED is used in the following Table(s):
572, 613, 618.

technical-manual-safety-supplement-document-sequential-identifier
The identifier of a specific safety supplement in a sequence of safety supplements to a specific technical
manual/order at a specific revision and change. This DED is used in the following Table(s): 572, 611,
616.

C-130
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0245 modification-kit-product-identifier S 37
The identifier of a kit of materials and/or parts to be used to modify fielded hardware. (Source of
requirements: NAVAIR TM 00-25-300.) This DED is used in the following Table(s): 490, 492.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0001 enterprise-defense-logistics--assigned-identification-code
0024 part-product-identifier

0246 modification-work-order-document-priority-code C F 1
A code that indicates the priority given to a modification work order to indicate the level of urgency that
should be given to accomplishing the task. (Source of requirements: DA PAM 738-750, DA PAM 738-
751.) This DED is used in the following Table(s): 467.

The valid domain values for this element are as follows:

Domain
Value Meaning
L Limited Urgent
N Normal
U Urgent

0247 technical-directive-document-category-code C F 1
A code assigned to a technical directive to indicate the importance and urgency of accomplishing the
work involved. (Source of requirements: MIL-D-81992B, NAVAIRINST 5215.8C.) This DED is used
in the following Table(s): 465.

The valid domain values for this element are as follows:

Domain
Value Meaning
C Record Purpose
I Immediate
R Routine
U Urgent

0248 limited-duration-technical-order-document-priority-code C F 1
A code assigned to a TCTO to indicate the immediacy or importance of accomplishing the task covered
by the TCTO. (Source of requirements: AF TO 00-20-2.) This DED is used in the following Table(s):
466.

The valid domain values for this element are as follows:

Domain
Value Meaning
1 Immediate action
2 Urgent action

C-131
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

3 Routine action or record type

7 Event type

0249 technical-directive-document-task-type-code C F 1
A code used to distinguish the type of technical directive. (Source of requirements: NAVAIR 00-25-
300, NAVAIRINST 5215.8C.) This DED is used in the following Table(s): 465.

The valid domain values for this element are as follows:

Domain
Value Meaning
B Bulletin
C Formal change
I Interim change
R Rapid Actions Minor Engineering Change

0250 modification-work-order-document-maintenance-level-code C F 1
The code that indicates the echelon level of maintenance required to complete the work defined by the
MWO. (Source of requirements: AR 750-1.) This DED is used in the following Table(s): 467.

The valid domain values for this element are as follows:

Domain
Value Meaning
D Depot
F Direct Support
H General Support
O Unit

0251 engineering-drawing-document-note-identifier I R 3
The identifier of a notation in a series of notations on an engineering drawing and provides a cross
reference between the series of notations, the graphical view of the part or assembly being described by
the drawing, and the parts and materials included in the parts list. The number is unique within a single
engineering drawing. (Source of requirements: MIL-STD-100.) This DED is used in the following
Table(s): 080, 081, 085, 086, 087, 226, 325, 326, 327.

0252 engineering-drawing-document-note-text C L 500

The text which is a notation on an engineering drawing. Must be a printable ASCII character, space,
tab, and line feed. (Source of requirements: MIL-STD-100.) This DED is used in the following
Table(s): 080, 325.

C-132
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0253 modification-instruction-document-task-description-text C L 300

A narrative description of the purpose of a specific modification instruction. Must be a printable ASCII
character, space, tab, line feed, and carriage return. This DED is used in the following Table(s): 460.

0254 technical-directive-document-maintenance-level-code C F 1
The code that indicates the echelon level of maintenance associated with the technical directive
implementation. (Source of requirements: MIL-D-81992B.) This DED is used in the following
Table(s): 465.

The valid domain values for this element are as follows:

Domain
Value Meaning
C Contractor
D Depot
I Intermediate
O Organizational

0255 limited-duration-technical-order-document-maintenance-level- C F 1
code
The code that is associated with the echelon level of maintenance required to implement the TCTO.
(Source of requirements: AFMCP 66-16.) This DED is used in the following Table(s): 466.

The valid domain values for this element are as follows:

Domain
Value Meaning
D Depot level
I Intermediate or organizational level

0256 rapid-action-change-order-document-change-type-code C L 2
A code used to distinguish rapid action change documents as interim or formal. (Source of
requirements: MIL-M-81748C.) This DED is used in the following Table(s): 464.

The valid domain values for this element are as follows:

Domain
Value Meaning
IA Interim RAC issued as a message
IB Interim RAC issued as a speedletter
II Formal RAC

C-133
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0257 engineering-drawing-document-special-condition-code C L 4
A code which indicates that a special material or process is applicable. (Source of requirements: MIL-
STD-100, PL 102-484.) (This is equivalent to MIL-PRF-49506 DED 0340.) This DED is used in the
following Table(s): 081, 227, 324, 327.

The valid domain values for this element are as follows:

Domain
Value Meaning
CSI Critical Safety Item (see MIL-STD-882)
CSP Critical Safety Process (see MIL-STD-882)
ENI Environmental Impact item or process
ESD Electrostatic Discharge Sensitive Device (see MIL-STD-1686 and DOD-HDBK-
263)
ESS Environmental Stress Screening (see MIL-STD-2164)
HAZ Hazardous material or process or conditions
HCI Hardness Critical Item
HCP Hardness Critical Process
I/R Interchangeability/Replaceability controlled item (see MIL-I-8500)
INT Interface Control
OCI Observable Critical Item
OCP Observable Critical Process
ODS1 Ozone Depleting Substance Class 1
ODS2 Ozone Depleting Substance Class 2
ODS3 Ozone Depleting Substance Class 3
ODS4 Ozone Depleting Substance Class 4
ODS5 Ozone Depleting Substance Class 5

0258 document-parts-list-entry-priority-indicator-code C F 1
A code which denotes whether the parts list entry depicts a preferred or alternate component. This DED
is used in the following Table(s): 224, 316.

The valid domain values for this element are as follows:

Domain
Value Meaning
A Alternate component
P Preferred component

0259 document-parts-list-entry-sequence-identifier I F 3
The identifier of a particular line item entry for a single find number in a parts list. The identifier
indicates the relative ordering of the parts list line items for presentation. (Source of requirements: ISO
10303-232.) This DED is used in the following Table(s): 220, 221, 222, 224, 225, 227, 316, 318, 319,
320, 321, 322.

C-134
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

DED DED TITLE/ROLE TITLE Type Jst Dec Size

Definition and Legal Values (if any)

0260 engineering-drawing-document-proposed-entry-change-type- C F 1
code
A code which denotes the type of proposed change to an entry in a parts list (either integral or separate)
or note. This DED is used in the following Table(s): 315, 316, 318, 325.

The valid domain values for this element are as follows:

Domain
Value Meaning
A Added entry
C Changed entry (replace current information with new information)
D Deleted entry
N No change

0261 engineering-drawing-document-proposed-change-type-code C F 1
A code which denotes the type of a proposed change to part number defined by a drawing or in the text
associated with a find number which represent its components. This DED is used in the following
Table(s): 317, 323, 324, 326, 327.

The valid domain values for this element are as follows:

Domain
Value Meaning
A Added part number or note
D Deleted part number or note

0262 software-product-identifier S 248

The unique identification of a software product by means of a software name (or number) and a release
level. This DED is used in the following Table(s): 172.

This DED is comprised of the following data elements concatenated in the order listed:
DED Title
0122 document-identifier
0062 software-product-version-identifier

0263 engineering-change-proposal-document-unusual-effect-name C L 30
The name of the unusual factor which is impacted by the proposed ECP. Must be a printable ASCII
character or embedded space. This DED is used in the following Table(s): 265.

C.6. NOTES

This section is not applicable to this standard.

C-135
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX C

(This page intentionally left blank)

C-136
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

DATA ELEMENT DICTIONARY CROSS-REFERENCES

D.1. SCOPE

D.1.1. Scope. This appendix is provided to assist CM AIS developers in locating specific information in the
relational tables and data dictionary. This appendix is included as information. There are no compliance
requirements in this appendix.

D.2. APPLICABLE DOCUMENTS

D.2.1. Not applicable.

D.3. DEFINITIONS

D.3.1. Additional definitions. The acronyms and definitions in Section 3, Appendix B, and Appendix C of this
standard apply to this appendix. In addition, the following definitions apply:

a. Alias. A non-standard name for an attribute. See Nickname.

b. Nickname. An attribute name which does not meet the DoD requirements for data element standardization.
Generally, the nickname is the data element name or abbreviation which is used in the IDEF1x diagrams in
this standard or which is commonly used to describe the element and is used to identify the contents of
specific form blocks, report column headings, or paragraphs.

D.4. GENERAL REQUIREMENTS

D.4.1. Organization of this appendix. This appendix is divided into two sections as follows:

D.4.1.1. Section 1: Index of data element names. This section is an alphabetical list of all data element titles and
nicknames. DED titles are cross-referenced to their DED number, table(s) where used, and DED codes (within the
table[s]). Nicknames are cross-referenced to their DED title.

D.4.1.2. Section 2: Index of DED codes. This section is an alphanumerical list of all DED codes. Each DED
code is cross-referenced to its DED number and DED title.

D.5. DETAILED REQUIREMENTS

D.5.1. Section 1: Index of data element names.

D-1
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

abl-top--level-indicator 0137 alias for: allocated-baseline-top--level-

document-indicator-code

aco-address 0081 alias for: enterprise-administrative-

contracting-office-address-text

aco-name 0069 alias for: administrative-contracting-

officer-human-name

action-identifier 0072 (Basic Standard Data Element--see

applicable role name.)

action-item-title 0136 alias for: process-action-item-title-name

address 0039 alias for: enterprise-address-text

administrative-contracting-officer- 0069 950.ACONAM950

human-name

administrative-control-drawing- 0032 051.CONTYP051, 912.CONTYP912

document-type-code

af-technical-order-identifier 0003 alias for: united-states-air-force-technical-

order-document-alphanumeric-identifier

affected-document-type-code 0004 301.ADOCTY301

agreement-identifier 0152 976.AGRIDN976

agreement-name 0071 950.CONNAM950

agreement-effective-date 0082 951.CONDAT951

agreement-type-code 0167 975.AGRTYP975, 976.AGRTYP975

alias-document-source-entity-identifier 0033 556.ASRCID556

allocated-baseline-top--level-document- 0137 100.ABLFLG100

indicator-code

application-activity-approval-status-code 0021 alias for: document-revision-application-

activity-approval-process-disposition-
status-code

application-activity-approval-status-date 0082 alias for: document-revision-application-

activity-approval-process-disposition-
status-date

D-2
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

application-activity-enterprise-division- 0228 033.APPACT033, 861.APPACT033,

identifier 862.APPACT033, 863.APPACT033,
864.APPACT033, 865.APPACT033,
866.APPACT033, 867.APPACT033,
967.APPACT033

application-activity-identifier 0228 alias for: application-activity-enterprise-

division-identifier

application-activity-program- 0128 033.GLAACD033

government-lead-indicator-code

application-software-launch-script- 0209 alias for: application-software-product-

location-identifier launch-script-electronic-storage-place-
identifier

application-software-location-identifier 0209 alias for: application-software-product-

electronic-storage-place-identifier

application-software-product-electronic- 0209 902.APPLOC902, 903.APPLOC902

storage-place-identifier

application-software-product-launch- 0209 902.LAUNCH902

script-electronic-storage-place-identifier

area-of-responsibility 0154 alias for: human-responsibility-

description-text

army-technical-manual-identifier 0003 alias for: united-states-army-technical-

manual-document-alphanumeric-identifier

assembled-material-generic-identifier 0092 alias for: assembled-material-product-

generic-identifier

assembled-material-identification 0038 alias for: assembled-material-product-

identifier

assembled-material-product-identifier 0038 244.AMATID244

assembled-material-product-generic- 0092 244.AMATGI244

identifier

assembled-part-product-identifier 0024 233.ASYIDN233, 234.APARNO234,

237.APARNO234, 242.APARNO242,
243.APARNO243, 256.APARNO256,
362.APARNO234

assembled-product-design-enterprise- 0001 236.ADESCG236, 239.ADESCG236,

defense-logistics--assigned-identification- 293.ADESCG293, 364.ADESCG236
code

D-3
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

assembled-product-identifier 0024 alias for: assembled-part-product-identifier

assembly-design-cage-code 0001 alias for: assembled-product-design-

enterprise-defense-logistics--assigned-
identification-code

assembly-design-enterprise-identifier 0052 233.ASYENT233, 242.AENTID242,

243.AENTID243, 244.AENTID244

assembly-drawing-alphanumeric- 0003 alias for: assembly-engineering-drawing-

identifier document-alphanumeric-identifier

assembly-engineering-drawing- 0003 220.ASSYNO224, 221.ASSYNO224,

document-alphanumeric-identifier 222.ASSYNO224, 223.ASSYNO224,
224.ASSYNO224, 225.ASSYNO224,
226.ASSYNO224, 227.ASSYNO224,
316.ASSYNO316, 318.ASSYNO316,
319.ASSYNO316, 320.ASSYNO316,
321.ASSYNO316

assembly-manufacturer-cage-code 0001 alias for: assembly-manufacturer-

enterprise-defense-logistics--assigned-
identification-code

assembly-manufacturer-enterprise- 0001 242.AMFRCG242, 243.AMFRCG243,

defense-logistics--assigned-identification- 244.AMFRCG244
code

assembly-model-database-document- 0243 233.ASYREV233

generic-revision-identifier

assembly-model-revision 0243 alias for: assembly-model-database-

document-generic-revision-identifier

assembly-part-component-quantity 0053 225.QUANTY225, 242.QUANTY242,

243.QUANTY243, 244.QUANTY244,
318.QUANTY318

assembly-product-tracking-identifier 0175 242.ATRKID242, 243.ATRKID243,

244.ATRKID244

assembly-status-code 0174 alias for: product-assembly-status-code

assembly-status-date 0082 alias for: product-assembly-status-date

assembly-status-time 0160 alias for: product-assembly-status-time

assembly-tracking-identifier 0175 alias for: assembly-product-tracking-

identifier

D-4
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

asset-identifier 0031 (Basic Standard Data Element--see

applicable role name.)

asset-version-identifier 0064 (Basic Standard Data Element--see

applicable role name.)

audit-action-item-description 0065 alias for: audit-process-required-action-

description-text

audit-action-item-disposition-code 0021 alias for: audit-process-action-item-

disposition-status-code

audit-action-item-disposition-date 0082 alias for: audit-process-action-item-

disposition-status-date

audit-action-item-identifier 0072 alias for: audit-process-action-identifier

audit-date 0082 alias for: audit-process-date

audit-process-date 0082 675.AUDDAT675, 676.AUDDAT675,

678.AUDDAT675, 679.AUDDAT675,
680.AUDDAT675, 681.AUDDAT675,
682.AUDDAT675

audit-process-action-identifier 0072 676.AUDACT676, 678.AUDACT676,

679.AUDACT676, 680.AUDACT676,
681.AUDACT676, 682.AUDACT676

audit-process-action-item-disposition- 0021 678.STACOD678

status-code

audit-process-action-item-disposition- 0082 678.STADAT678

status-date

audit-process-required-action-description- 0065 676.ACTDES676

text

audit-process-type-code 0070 675.AUDTYP675, 676.AUDTYP675,

678.AUDTYP675, 679.AUDTYP675,
680.AUDTYP675, 681.AUDTYP675,
682.AUDTYP675

audit-type-code 0070 alias for: audit-process-type-code

author-human-name 0069 001.AUTNAM001, 042.AUTNAM001,

043.AUTNAM001

author-name 0069 alias for: author-human-name

baseline-type-code 0098 alias for: product-baseline-type-code

D-5
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

bugetary-production-cost-estimate 0172 alias for: engineering-change-proposal-

document-estimated-production-cost-
amount

bugetary-rdt&e-cost-estimate 0172 alias for: engineering-change-proposal-

document-estimated-research-cost-amount

cage-code 0001 alias for: enterprise-defense-logistics--

assigned-identification-code

cage-type-code 0102 alias for: enterprise-defense-logistics--

assigned-identification-type-code

ccb-chairman-disposition-status-code 0021 alias for: document-change-process-

program-configuration-control-board-
chairman-disposition-status-code

ccb-decision-date 0082 alias for: program-configuration-control-

board-decision-date

ccb-enterprise-identifier 0052 alias for: configuration-control-board-

convening-enterprise-identifier

ccb-minutes 0168 alias for: program-configuration-control-

board-discussion-text

ccb-name 0151 alias for: program-configuration-control-

board-name

ccb-type 0173 alias for: program-configuration-control-

board-type-code

cdrl-address-list-affect-code 0198 alias for: contract-modification-document-

address-list-affect-code

cdrl-affect-code 0198 alias for: contract-modification-document-

contract-data-requirements-list-affect-code

cdrl-approval-requirement-code 0203 alias for: contract-data-requirement-list-

document-item-approval-requirement-code

cdrl-category-code 0201 alias for: contract-data-requirement-list-

document-form-category-code

cdrl-delivery-due-code 0233 alias for: contract-data-requirement-list-

document-delivery-due-code

cdrl-document-item-effective-cut--off- 0082 alias for: contract-data-requirement-list-

date document-item-effective-cut--off-date

cdrl-effective-cut--off-date 0082 alias for: contract-data-submittal-

document-effective-cut--off-date

D-6
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

cdrl-effective-cut--off-event-delta 0161 alias for: contract-data-requirement-list-

document-item-effective-cut--off-event-
delta-text

cdrl-form-approval-date 0082 alias for: contract-data-requirement-list-

document-form-approval-process-
disposition-action-status-date

cdrl-form-approver-name 0069 alias for: contract-data-requirement-list-

document-form-approver-human-name

cdrl-form-preparation-date 0082 alias for: contract-data-requirement-list-

document-form-preparation-process-
completion-date

cdrl-form-preparer-name 0069 alias for: contract-data-requirement-list-

document-form-preparer-human-name

cdrl-frequency-code 0197 alias for: contract-data-requirement-list-

document-item-submission-frequency-code

cdrl-initial-delivery-due-code 0233 alias for: contract-data-requirement-list-

document-item-initial-delivery-due-code

cdrl-initial-submittal-due-date 0082 alias for: contract-data-requirement-list-

document-item-initial-submittal-due-date

cdrl-item-subtitle 0008 alias for: contract-data-requirement-list-

document-item-subsidiary-name

cdrl-item-title 0008 alias for: contract-data-requirement-list-

document-item-name

cdrl-modification-symbol-code 0205 alias for: contract-data-requirement-list-

document-item-modification-symbol-code

cdrl-price-amount 0200 alias for: contract-data-requirement-list-

document-item-price-amount

cdrl-price-group-code 0199 alias for: contract-data-requirement-list-

document-item-price-group-code

cdrl-remark-text 0204 alias for: contract-data-requirement-list-

document-item-remark-text

cdrl-sequence-identifier 0005 alias for: contract-data-requirement-list-

document-item-sequence-identifier

cdrl-subsequent-delivery-due 0233 alias for: contract-data-requirement-list-

document-item-subsequent-delivery-due-
code

D-7
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

cdrl-subsequent-submittal-due-date 0082 alias for: contract-data-requirement-list-

document-item-subsequent-submittal-due-
date

change-proposal-document 0171 alias for: change-proposal-document-text

change-proposal-document-text 0171 (Basic Standard Data Element--see

applicable role name.)

change-proposal-document-change- 0171 251.ECP190251

description-text

change-proposal-document-change- 0171 251.ECP200251

justification-text

change-proposal-document-contractor- 0180 290.ECP470290

field-service-effect-code

change-proposal-document-production- 0171 251.ECP220251

delivery-schedule-effect-text

changed-technical-manual-document- 0218 572.CTMIDN572, 573.CTMIDN572,

identifier 611.CTMIDN611, 612.CTMIDN612,
613.CTMIDN613, 614.CTMIDN614,
616.CTMIDN611, 617.CTMIDN612,
618.CTMIDN613, 619.CTMIDN614

changed-tm-identifier 0218 alias for: changed-technical-manual-

document-identifier

ci-designation 0045 alias for: configuration-item-product-

designation-identifier

ci-designation-standard-code 0051 alias for: configuration-item-designation--

convention-document-code

ci-identifier 0111 alias for: configuration-item-product-

identifier

ci-indicator-code 0023 alias for: configuration-item-product-

indicator-code

ci-name 0046 alias for: configuration-item-product-name

ci-nomenclature 0047 alias for: configuration-item-product-

nomenclature-text

ci-type-code 0115 alias for: configuration-item-product-type-

code

city 0041 alias for: city-place-name

D-8
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

city-place-name 0041 Part of data element string: enterprise-

address-text.

classification-downgrade-event 0156 alias for: document-security-classification-

downgrade-process-event-name

classified-document-receipt- 0224 alias for: enterprise-security-classified-

authorization-code document-receipt-authorization-code

clin-description 0109 alias for: contract-document-line-item-

description-text

clin-identifier 0017 alias for: contract-document-line-item-

identifier

clin-quantity 0144 alias for: contract-document-line-item-

quantity

combination-cpin 0237 alias for: combination-software-product-

united-states-air-force--assigned-
designation-identifier

combination-software-product-united- 0237 193.COMBNO193

states-air-force--assigned-designation-
identifier

comment-file-creation-time 0160 alias for: electronic-document-comment-

file-creation-time

comment-file-identifier 0206 alias for: electronic-document-comment-

file-identifier

comment-file-originator 0069 alias for: comment-file-originator-human-

name

comment-file-originator-human-name 0069 812.CFILOR812, 858.CFILOR858,

867.CFILOR867, 968.CFILOR968

comment-file-originator-office-address 0081 alias for: enterprise-comment-file-

origination-office-address-text

commercial-document-source-enterprise- 0170 026.SRCCOM026, 027.SRCCOM026,

name 048.SRCCOM048, 049.SRCCOM048,
440.SRCCOM910, 441.SRCCOM026,
910.SRCCOM910, 911.SRCCOM910,
914.SRCCOM910, 926.SRCCOM910

commercial-document-source-name 0170 alias for: commercial-document-source-

enterprise-name

D-9
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

commercial-enterprise-name 0170 005.COMNAM005, 006.COMNAM005,

166.DESCOM166, 175.DESCOM166,
922.COMNAM005, 927.COMNAM005,
928.COMNAM005, 929.COMNAM005

commercial-name 0170 alias for: commercial-enterprise-name

commercial-product-inventory-stock- 0186 927.STKNUM927, 928.STKNUM927,

identifier 929.STKNUM927

company-stock-number 0186 alias for: commercial-product-inventory-

stock-identifier

component-cpin 0237 alias for: component-software-product-

united-states-air-force--assigned-
designation-identifier

component-document-generic-revision 0243 alias for: component-document-generic-

revision-identifier

component-document-generic-revision- 0243 071.CDOCRV071

identifier

component-document-type-code 0004 071.CDOCTY071

component-index-list-cage-code 0001 alias for: component-index-list-drawing-

document-source-enterprise-defense-
logistics--assigned-identification-code

component-index-list-drawing- 0003 alias for: component-index-list-drawing-

alphanumeric-identifier document-alphanumeric-identifier

component-index-list-drawing-document- 0003 067.CILNUM067

alphanumeric-identifier

component-index-list-drawing-document- 0009 067.CILREV067

alphanumeric-revision-identifier

component-index-list-drawing-document- 0001 067.CILCAG067

source-enterprise-defense-logistics--
assigned-identification-code

component-index-list-revision 0009 alias for: component-index-list-drawing-

document-alphanumeric-revision-identifier

component-lot-identifier 0175 alias for: component-product-lot-tracking-

identifier

component-lot-quantity 0019 alias for: component-product-quantity

component-material-design-enterprise- 0052 243.CENTID243, 244.CENTID244

identifier

D-10
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

component-material-enterprise-identifier 0052 alias for: component-material-design-

enterprise-identifier

component-material-generic-identifier 0092 alias for: component-material-product-

generic-identifier

component-material-identification 0038 alias for: component-material-product-

identifier

component-material-manufacturer-cage- 0001 alias for: component-material-

code manufacturer-enterprise-defense-logistics--
assigned-identification-code

component-material-manufacturer- 0001 243.CMFRCG243, 244.CMFRCG244,

enterprise-defense-logistics--assigned- 527.CMFRCG527
identification-code

document-generic-revision-identifier

component-part-model-generic-revision 0243 alias for: component-part-model-database-

document-generic-revision-identifier

D-11
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

D-12
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

configuration-control-board-convening- 0052 262.CCBENT262, 264.CCBENT262,

enterprise-identifier 370.CCBENT370, 372.CCBENT370

configuration-item-designation-- 0051 693.CISTND693

convention-document-code

configuration-item-product-identifier 0111 331.CIIDEN695, 675.CIIDEN695,

676.CIIDEN695, 678.CIIDEN695,
679.CIIDEN695, 680.CIIDEN695,
681.CIIDEN695, 682.CIIDEN695,
692.CIIDEN695, 695.CIIDEN695,
696.CIIDEN695, 697.CIIDEN695,
703.CIIDEN695, 952.CIIDEN695

configuration-item-product-name 0046 Part of data element string: configuration-

item-product-nomenclature-text.

configuration-item-product-designation- 0045 501.CIDESG693, 693.CIDESG693

identifier

configuration-item-product-indicator- 0023 060.CIFLAG060

code

configuration-item-product- 0047 060.CINOMN690, 100.CINOMN690,

nomenclature-text 208.CINOMN690, 323.CINOMN690,
690.CINOMN690, 697.CINOMN690

configuration-item-product-type-code 0115 695.CITYPE695

contract-alphanumeric-identifier 0226 alias for: contract-document-

alphanumeric-identifier

contract-data-requirement-list-document- 0233 (Basic Standard Data Element--see

delivery-due-code applicable role name.)

contract-data-requirement-list-document- 0082 952.APPRDT952

form-approval-process-disposition-action-
status-date

contract-data-requirement-list-document- 0069 952.APPRNM952

form-approver-human-name

contract-data-requirement-list-document- 0201 952.CDRLCT952

form-category-code

contract-data-requirement-list-document- 0082 952.PREPDT952

form-preparation-process-completion-
date

contract-data-requirement-list-document- 0069 952.PREPNM952

form-preparer-human-name

D-13
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

contract-data-requirement-list-document- 0008 953.CDR020953

item-name

contract-data-requirement-list-document- 0203 953.CDR080953

item-approval-requirement-code

contract-data-requirement-list-document- 0082 953.CDR11D953

item-effective-cut--off-date

contract-data-requirement-list-document- 0161 953.CDR11T953

item-effective-cut--off-event-delta-text

contract-data-requirement-list-document- 0233 953.CDR12C953

item-initial-delivery-due-code

contract-data-requirement-list-document- 0082 953.CDR12D953

item-initial-submittal-due-date

contract-data-requirement-list-document- 0205 953.SUFXCD953

item-modification-symbol-code

contract-data-requirement-list-document- 0200 953.CDR180953

item-price-amount

contract-data-requirement-list-document- 0199 953.CDR170953

item-price-group-code

contract-data-requirement-list-document- 0204 953.CDR160953

item-remark-text

contract-data-requirement-list-document- 0005 953.CDRLIN953, 954.CDRLIN953,

item-sequence-identifier 955.CDRLIN953, 956.CDRLIN953,
963.CDRLIN953, 964.CDRLIN953,
965.CDRLIN953, 966.CDRLIN953,
967.CDRLIN953, 968.CDRLIN953,
969.CDRLIN953, 970.CDRLIN953,
971.CDRLIN953, 972.CDRLIN953

contract-data-requirement-list-document- 0197 953.CDR100953

item-submission-frequency-code

contract-data-requirement-list-document- 0233 953.CDR13C953

item-subsequent-delivery-due-code

contract-data-requirement-list-document- 0082 953.CDR13D953

item-subsequent-submittal-due-date

contract-data-requirement-list-document- 0008 953.CDR030953

item-subsidiary-name

D-14
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

contract-data-submittal-document- 0020 954.CDRLSB954, 955.CDRLSB954,

identifier 956.CDRLSB954, 963.CDRLSB954,
964.CDRLSB954, 965.CDRLSB954,
966.CDRLSB954, 967.CDRLSB954,
968.CDRLSB954, 969.CDRLSB954,
970.CDRLSB954, 971.CDRLSB954,
972.CDRLSB954

contract-data-submittal-document-name 0008 954.SUBTIT954

contract-data-submittal-document- 0021 956.SUBSTA956, 968.SUBSTA956,

approval-process-disposition-status-code 969.SUBSTA956, 970.SUBSTA956,
971.SUBSTA956, 972.SUBSTA956

contract-data-submittal-document- 0082 956.STATDT956

approval-process-disposition-status-date

contract-data-submittal-document- 0082 955.SUBDUE955

calendar-due-date

contract-data-submittal-document- 0082 970.FSUSDT970

customer-final-disposition-suspense-date

contract-data-submittal-document- 0082 970.TSUSDT970

customer-technical-review-completion-
suspense-date

contract-data-submittal-document- 0069 956.DISNAM956

dispositioner-human-name

contract-data-submittal-document- 0082 954.COFFDT954

effective-cut--off-date

contract-data-submittal-document- 0161 954.COFFDL954

effective-cut--off-event-delta-text

contract-data-submittal-document-event-- 0234 (Basic Standard Data Element--see

delta-text applicable role name.)

contract-data-submittal-document-initial- 0082 954.INDUDT954

delivery-calendar-due-date

contract-data-submittal-document-initial- 0234 954.INDUDL954

delivery-event--delta-text

contract-data-submittal-document- 0153 954.SUBRMK954, 955.SUBCOM955

remark-text

contract-data-submittal-document- 0159 972.RSUBRQ972

resubmittal-code

D-15
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

contract-data-submittal-document- 0082 972.RSUBDT972

resubmittal-due-date

contract-data-submittal-document- 0235 956.RSUBSR956

resubmittal-requirement-identifier

contract-data-submittal-document- 0099 955.SUBREV955, 956.SUBREV955,

revision-identifier 965.SUBREV955, 966.SUBREV955,
967.SUBREV955, 968.SUBREV955,
969.SUBREV955, 970.SUBREV955,
971.SUBREV955, 972.SUBREV955

contract-data-submittal-document- 0150 954.SUBTYP954

submittal-type-code

contract-data-submittal-document- 0082 954.SBDUDT954

subsequent-delivery-calendar-due-date

contract-data-submittal-document- 0234 954.SBDUDL954

subsequent-delivery-event--delta-text

contract-data-submittal-initial-delivery- 0082 alias for: contract-data-submittal-

due-date document-initial-delivery-calendar-due-
date

contract-document-identifier 0015 011.CONIDN950, 255.CONIDN950,

257.CONIDN950, 292.CONIDN950,
332.CONIDN950, 354.CONIDN950,
355.CONIDN950, 356.CONIDN950,
675.CONIDN950, 676.CONIDN950,
678.CONIDN950, 679.CONIDN950,
680.CONIDN950, 681.CONIDN950,
682.CONIDN950, 900.CONIDN950,
950.CONIDN950, 951.CONIDN950,
952.CONIDN950, 953.CONIDN950,
954.CONIDN950, 955.CONIDN950,
956.CONIDN950, 957.CONIDN950,
958.CONIDN950, 959.CONIDN950,
960.CONIDN950, 961.CONIDN950,
962.CONIDN950, 963.CONIDN950,
964.CONIDN950, 965.CONIDN950,
966.CONIDN950, 967.CONIDN950,
968.CONIDN950, 969.CONIDN950,
970.CONIDN950, 971.CONIDN950,
972.CONIDN950

contract-document-alphanumeric- 0226 977.CONNUM977

identifier

D-16
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

contract-document-exhibit-identifier 0007 952.CONEXH952, 953.CONEXH952,

954.CONEXH952, 955.CONEXH952,
956.CONEXH952, 958.CONEXH952,
963.CONEXH952, 964.CONEXH952,
965.CONEXH952, 966.CONEXH952,
967.CONEXH952, 968.CONEXH952,
969.CONEXH952, 970.CONEXH952,
971.CONEXH952, 972.CONEXH952

contract-document-fee-type-code 0227 950.FEETYP950

contract-document-line-item-identifier 0017 255.CLINUM959, 355.CLINUM959,

958.CLINUM959, 959.CLINUM959,
960.CLINUM959

contract-document-line-item-quantity 0144 959.CLINQT959

contract-document-line-item-description- 0109 959.CLINDS959

text

contract-document-modification- 0140 951.CONDES951

description-text

contract-document-performance-period- 0145 951.PERIOD951

months-quantity

contract-document-revision-identifier 0120 255.CONMOD951, 257.CONMOD951,

292.CONMOD951, 332.CONMOD951,
354.CONMOD951, 355.CONMOD951,
356.CONMOD951, 679.CONMOD951,
680.CONMOD951, 951.CONMOD951,
952.CONMOD951, 953.CONMOD951,
954.CONMOD951, 955.CONMOD951,
956.CONMOD951, 957.CONMOD951,
958.CONMOD951, 959.CONMOD951,
960.CONMOD951, 963.CONMOD951,
964.CONMOD951, 965.CONMOD951,
966.CONMOD951, 967.CONMOD951,
968.CONMOD951, 969.CONMOD951,
970.CONMOD951, 971.CONMOD951,
972.CONMOD951

contract-document-type-code 0004 Part of data element string: contract-

document-identifier.

contract-exhibit-identifier 0007 alias for: contract-document-exhibit-

identifier

contract-identifier 0015 alias for: contract-document-identifier

D-17
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

contract-mod-affect-code 0198 alias for: contract-modification-document-

affect-code

contract-mod-schedule-affect-code 0198 alias for: contract-modification-document-

delivery-schedule-affect-code

contract-modification 0120 alias for: contract-document-revision-

identifier

contract-modification-date 0082 alias for: agreement-effective-date

contract-modification-description 0140 alias for: contract-document-modification-

description-text

contract-modification-document-address- 0198 951.CDADAF951

list-affect-code

contract-modification-document-affect- 0198 (Basic Standard Data Element--see

code applicable role name.)

contract-modification-document-contract- 0198 951.CDRLAF951

data-requirements-list-affect-code

contract-modification-document-delivery- 0198 951.CONAFF951

schedule-affect-code

contract-modification-document- 0198 951.DISSAF951

distribution-statement-affect-code

contract-modification-document-other- 0198 951.OATTAF951

attachment-affect-code

contract-modification-document-other- 0198 951.OTEXAF951

exhibit-affect-code

contract-modification-document- 0198 951.SCHAAF951

schedule-a-affect-code

contract-modification-document- 0198 951.SCHBAF951

schedule-b-affect-code

contract-modification-document- 0198 951.SCHCAF951

schedule-c-affect-code

contract-modification-document- 0198 951.SCHDAF951

schedule-d-affect-code

contract-modification-document- 0198 951.SCHEAF951

schedule-e-affect-code

contract-modification-document- 0198 951.SCHFAF951

schedule-f-affect-code

D-18
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

contract-modification-document- 0198 951.SCHGAF951

schedule-g-affect-code

contract-modification-document- 0198 951.SCHHAF951

schedule-h-affect-code

contract-modification-document- 0198 951.SCHIAF951

schedule-i-affect-code

contract-modification-document- 0198 951.SCHJAF951

schedule-j-affect-code

contract-modification-document- 0198 951.SCHKAF951

schedule-k-affect-code

contract-modification-document-work- 0198 951.SOWAFF951

statement-affect-code

contract-performance-period-months 0145 alias for: contract-document-performance-

period-months-quantity

contractor-human-name 0069 950.SELNAM950

contractor-technical-monitor-division 0228 alias for: performing-activity-enterprise-

technical-monitor-division-identifier

CONTRCT 0004 alias for: contract-document-type-code

copyright-statement 0013 alias for: document-copyright-text

country 0042 alias for: country-place-name

country-place-name 0042 Part of data element string: enterprise-

address-text.

cpin 0237 alias for: software-product-united-states-

air-force--assigned-designation-identifier

cpin-applicability-code 0236 alias for: software-product-united-states-

air-force--assigned-applicability-code

D-20
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

cpin-category-code 0179 alias for: software-product-united-states-

air-force--assigned-category-code

cpin-designator 0061 alias for: software-product-united-states-

air-force--assigned-identifier

cpin-major-function-code 0182 alias for: software-product-united-states-

air-force--assigned-major-function-code

cpin-prefix 0169 alias for: software-product-united-states-

air-force--assigned-receiving-country-
place-code

cpin-sequence 0221 alias for: software-product-united-states-

air-force--assigned-sequence-identifier

cpin-suffix 0177 alias for: software-product-united-states-

air-force--assigned-revision-identifier

cpin-system-identifier 0183 alias for: software-product-united-states-

air-force--assigned-applicable-system-
identifier

cpin-type-code 0188 alias for: software-product-united-states-

air-force--assigned-type-code

cpin-version 0189 alias for: software-product-united-states-

air-force--assigned-version-identifier

current-deviation-request-document- 0003 359.CRFDNO359

alphanumeric-identifier

current-deviation-request-document- 0001 359.CRFDCG359

source-enterprise-defense-logistics--
assigned-identification-code

current-rfd-alphanumeric-identifier 0003 alias for: current-deviation-request-

document-alphanumeric-identifier

current-rfd-cage-code 0001 alias for: current-deviation-request-

document-source-enterprise-defense-
logistics--assigned-identification-code

current-security-classification 0010 alias for: document-current-security-

classification-code

customer-final-data-disposition-suspense- 0082 alias for: contract-data-submittal-

date document-customer-final-disposition-
suspense-date

D-21
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

customer-technical-data-review- 0082 alias for: contract-data-submittal-

completion-suspense-date document-customer-technical-review-
completion-suspense-date

data-delivery-method-code 0139 alias for: data-product-delivery-method-

code

data-item-description-document-identifier 0230 953.CDR040953

data-item-description-document- 0003 650.DIDNUM650, 651.DIDNUM650

alphanumeric-identifier

data-item-description-document-type- 0004 650.DIDTYP650, 651.DIDTYP650

code

data-list-drawing-document- 0009 071.DLREVN071

alphanumeric-revision-identifier

data-list-drawing-document-type-code 0004 069.DLTYPE069, 070.DLTYPE069,

071.DLTYPE069

data-list-revision 0009 alias for: data-list-drawing-document-

alphanumeric-revision-identifier

data-product-delivery-method-code 0139 964.DELMTH964

data-resubmittal-code 0159 alias for: contract-data-submittal-

document-resubmittal-code

data-resubmittal-due-date 0082 alias for: contract-data-submittal-

document-resubmittal-due-date

data-resubmittal-requirement-source 0235 alias for: contract-data-submittal-

document-resubmittal-requirement-
identifier

data-rights-expiration-date 0082 alias for: technical-document-government-

data-rights-expiration-date

data-submittal-dispositioner-name 0069 alias for: contract-data-submittal-

document-dispositioner-human-name

data-submittal-due-date 0082 alias for: contract-data-submittal-

document-calendar-due-date

data-submittal-effective-cut--off-event 0161 alias for: contract-data-submittal-

document-effective-cut--off-event-delta-
text

data-submittal-event-delta-due-date 0234 alias for: contract-data-submittal-

document-event--delta-text

D-22
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

data-submittal-identifier 0020 alias for: contract-data-submittal-

document-identifier

data-submittal-initial-delivery-event 0234 alias for: contract-data-submittal-

document-initial-delivery-event--delta-text

data-submittal-remarks-text 0153 alias for: contract-data-submittal-

document-remark-text

data-submittal-revision 0099 alias for: contract-data-submittal-

document-revision-identifier

data-submittal-revision-disposition- 0021 alias for: contract-data-submittal-

status-code document-approval-process-disposition-
status-code

data-submittal-revision-disposition- 0082 alias for: contract-data-submittal-

status-date document-approval-process-disposition-
status-date

data-submittal-subsequent-delivery-due- 0082 alias for: contract-data-submittal-

date document-subsequent-delivery-calendar-
due-date

data-submittal-subsequent-delivery-event 0234 alias for: contract-data-submittal-

document-subsequent-delivery-event--
delta-text

data-submittal-title 0008 alias for: contract-data-submittal-

document-name

data-submittal-type-code 0150 alias for: contract-data-submittal-

document-submittal-type-code

date 0082 alias for: {}-date; Generic Data

Element--see applicable Standard Data
Element role name.

dcmc-address 0081 alias for: defense-contract-management-

enterprise-office-address-text

dcmc-concurrence-date 0082 alias for: engineering-change-proposal-

document-contract-administration-change-
class-concurrence-date

dcmc-contact-name 0069 alias for: defense-contract-management-

command-contact-human-name

dd250-dollar-amount 0146 alias for: shipping-document-dollar-

amount

D-23
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

dd250-item-description 0147 alias for: shipping-document-shipped-

item-description-text

dd250-requirement-code 0202 alias for: shipping-document-requirement-

code

dd250-shipment-date 0082 alias for: product-shipping-date

dd250-shipment-identifier 0003 alias for: shipping-document-

alphanumeric-identifier

dd250-shipping-delivery-quantitiy 0148 alias for: shipping-document-shipped-

item-quantity

dd250-status 0021 alias for: shipping-document-process-

disposition-status-code

declassification-event 0156 alias for: document-security-

declassification-process-event-name

defense-contract-management-command- 0069 251.ECP27E251

contact-human-name

defense-contract-management-enterprise- 0081 251.ECP27D251

office-address-text

delta-time-period 0231 alias for: period-length-quantity

design-cage-code 0001 alias for: design-enterprise-defense-

logistics--assigned-identification-code

design-company-name 0170 alias for: design-enterprise-name

design-enterprise-identifier 0052 (List is too long to include here, see

D.5.1.1.)

design-enterprise-name 0170 154.DESCOM154, 162.DESCOM162,

165.DESCOM165, 912.DESCOM912,
913.DESCOM913, 915.DESCOM913,
916.DESCOM913, 917.DESCOM917,
918.DESCOM918, 919.DESCOM919,
920.DESCOM919, 921.DESCOM921,
923.DESCOM923, 924.DESCOM921,
925.DESCOM919, 926.DESCOM919

design-enterprise-acronym-identification- 0002 201.DESORG421, 211.DESORG420,

code 420.DESORG420, 421.DESORG421,
422.DESORG421, 423.DESORG420

design-enterprise-defense-logistics-- 0001 (List is too long to include here, see

assigned-identification-code D.5.1.2.)

D-24
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

design-organization-code 0002 alias for: design-enterprise-acronym-

identification-code

deviation-code 0125 alias for: deviation-request-document-

defect-severity-classification-code

deviation-corrective-action-taken 0130 alias for: deviation-request-document-

corrective-action-taken-text

deviation-cost-price-effect-estimate- 0132 alias for: deviation-request-document-

amount price-effect-estimate-amount

deviation-delivery-schedule-text 0131 alias for: deviation-request-document-

delivery-schedule-effect-text

deviation-description-text 0126 alias for: deviation-request-document-

description-text

deviation-implementation-process-action- 0072 370.RFDACT370, 372.RFDACT370

identifier

deviation-implementation-process-action- 0021 372.STACOD372

disposition-status-code

deviation-implementation-process-action- 0082 372.STADAT372

disposition-status-date

deviation-implementation-process-action- 0185 370.ACTDES370

item-description-text

deviation-implementation-process- 0052 370.RESPON370

required-action-responsible-enterprise-
identifier

deviation-implementation-required- 0044 370.RESOFF370

action-responsible-enterprise-office-name

deviation-need-text 0127 alias for: deviation-request-document-

justification-text

deviation-recurring-request-code 0133 alias for: deviation-request-document-

recurring-request-code

DID 0004 alias for: data-item-description-document-

type-code

D-25
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

deviation-request-document- 0003 350.RFDNUM350, 351.RFDNUM350,

alphanumeric-identifier 352.RFDNUM350, 353.RFDNUM350,
354.RFDNUM350, 355.RFDNUM350,
356.RFDNUM350, 357.RFDNUM350,
358.RFDNUM350, 360.RFDNUM350,
361.RFDNUM350, 362.RFDNUM350,
363.RFDNUM350, 364.RFDNUM350,
365.RFDNUM350, 366.RFDNUM350,
370.RFDNUM350, 372.RFDNUM350,
373.RFDNUM350, 374.RFDNUM350,
535.RFDNUM350, 672.RFDNUM350,
706.RFDNUM350

deviation-request-document- 0009 351.RFDREV351, 352.RFDREV351,

alphanumeric-revision-identifier 353.RFDREV351, 354.RFDREV351,
355.RFDREV351, 356.RFDREV351,
357.RFDREV351, 358.RFDREV351,
359.RFDREV351, 360.RFDREV351,
361.RFDREV351, 362.RFDREV351,
363.RFDREV351, 364.RFDREV351,
365.RFDREV351, 366.RFDREV351,
370.RFDREV351, 372.RFDREV351,
373.RFDREV351, 374.RFDREV351,
535.RFDREV351, 706.RFDREV351

deviation-request-document-corrective- 0130 351.RFD024351

action-taken-text

deviation-request-document-defect- 0125 351.RFD006351

severity-classification-code

deviation-request-document-delivery- 0131 351.RFD020351

schedule-effect-text

deviation-request-document-description- 0126 351.RFD022351

text

deviation-request-document-justification- 0127 351.RFD023351

text

deviation-request-document-part-level- 0220 353.PARLVL353, 360.PARLVL360,

code 365.PARLVL365

deviation-request-document-price- 0104 351.RFD19A351

adjustment-effect-rationale-text

deviation-request-document-price-effect- 0132 351.RFD019351

estimate-amount

D-26
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

deviation-request-document-recurring- 0133 351.RFD018351

request-code

deviation-request-document-source- 0001 350.RFDCAG350, 351.RFDCAG350,

enterprise-defense-logistics--assigned- 352.RFDCAG350, 353.RFDCAG350,
identification-code 354.RFDCAG350, 355.RFDCAG350,
356.RFDCAG350, 357.RFDCAG350,
358.RFDCAG350, 360.RFDCAG350,
361.RFDCAG350, 362.RFDCAG350,
363.RFDCAG350, 364.RFDCAG350,
365.RFDCAG350, 366.RFDCAG350,
370.RFDCAG350, 372.RFDCAG350,
373.RFDCAG350, 374.RFDCAG350,
535.RFDCAG350, 672.RFDCAG350,
706.RFDCAG350

deviation-request-document-type-code 0004 350.RFDTYP350, 351.RFDTYP350,

352.RFDTYP350, 353.RFDTYP350,
354.RFDTYP350, 355.RFDTYP350,
356.RFDTYP350, 357.RFDTYP350,
358.RFDTYP350, 359.RFDTYP350,
360.RFDTYP350, 361.RFDTYP350,
362.RFDTYP350, 363.RFDTYP350,
364.RFDTYP350, 365.RFDTYP350,
366.RFDTYP350, 370.RFDTYP350,
372.RFDTYP350, 373.RFDTYP350,
374.RFDTYP350, 535.RFDTYP350,
672.RFDTYP350, 706.RFDTYP350

did-alphanumeric-identifier 0003 alias for: data-item-description-document-

alphanumeric-identifier

did-identifier 0230 alias for: data-item-description-document-

identifier

disposition-process-technical- 0082 811.TECHDT811, 857.TECHDT857,

recommendation-completion-date 866.TECHDT866, 968.TECHDT968

distribution-code 0014 alias for: document-distribution-statement-

code

distribution-controlling-enterprise 0052 alias for: document-distribution-

controller-enterprise-identifier

distribution-controlling-office 0044 alias for: document-distribution-

controller-enterprise-office-name

distribution-determination-date 0082 alias for: document-distribution-

restriction-determination-date

D-27
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

distribution-statement-affect-code 0198 alias for: contract-modification-document-

distribution-statement-affect-code

distribution-statement-text 0016 alias for: document-distribution-statement-

text

DL 0004 alias for: data-list-drawing-document-

type-code

DOCSUP 0004 alias for: supplemental-document-type-

code

document-alias 0122 alias for: document-alias-identifier

document-change-control-activity- 0082 alias for: document-change-control-

effective authority-effective-date

document-classification-authority 0155 alias for: document-security-classification-

authority-text

document-classification-date 0082 alias for: document-security-classification-

date

document-classification-downgrade-date 0082 alias for: document-security-classification-

downgrade-date

document-comment-file-creation-date 0082 alias for: electronic-document-comment-

file-creation-date

document-current-change-control- 0239 alias for: document-current-change-

authority control-authority-identifier

document-current-generic-revision 0243 alias for: document-current-generic-

revision-identifier

document-custodian 0033 alias for: document-custodial-entity-

identifier

document-custodian-office 0044 alias for: document-custodial-enterprise-

office-name

document-declassification-date 0082 alias for: document-security-

declassification-date

document-disposition-recommendation 0021 alias for: document-representation-release-

process-technical-recommended-
disposition-status-code

document-effective-cut--off-event-delta 0161 alias for: document-effective-cut--off-

event-delta-text

D-28
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-identifier 0122 (List is too long to include here, see

D.5.1.3.)

document-iteration-type-code 0196 alias for: technical-manual-document-

iteration-type-code

document-name 0008 011.DOCTIT011, 040.DOCTIT040,

041.DOCTIT040, 042.DOCTIT040,
043.DOCTIT040, 044.DOCTIT040,
045.DOCTIT040, 046.DOCTIT040,
047.DOCTIT040, 048.DOCTIT040,
049.DOCTIT040

document-originator 0033 alias for: document-origination-entity-

identifier

document-quantity 0158 962.DOCQTY962, 964.DOCQTY964

document-alias-identifier 0122 556.ADOCID556

document-alphanumeric-identifier 0003 (List is too long to include here, see

D.5.1.4.)

document-alphanumeric-revision- 0009 051.DOCREV051, 054.DOCREV051,

identifier 055.DOCREV051, 056.DOCREV051,
061.DOCREV051, 063.DOCREV051,
066.DOCREV051, 070.DOCREV051,
080.DOCREV051, 081.DOCREV051,
083.DOCREV051, 084.DOCREV051,
086.DOCREV051, 087.DOCREV051,
101.DOCREV101, 105.DOCREV101,
107.DOCREV101, 111.DOCREV101,
208.DOCREV051, 219.DOCREV051,
220.DOCREV051, 221.DOCREV051,
222.DOCREV051, 223.DOCREV051,
224.DOCREV051, 225.DOCREV051,
226.DOCREV051, 227.DOCREV051,
285.DOCREV051, 286.DOCREV051,
287.DOCREV101, 302.DOCREV051,
304.DOCREV101, 306.DOCREV051,
307.DOCREV051, 311.DOCREV051,
312.DOCREV051, 313.DOCREV101

document-approval-process-technical- 0021 857.TECHCD857, 866.TECHCD866,

recommended-disposition-status-code 968.TECHCD968

document-change-control-authority- 0082 010.CCCADT010

effective-date

D-29
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-change-process-program- 0021 704.CCBSTA704

configuration-control-board-chairman-
disposition-status-code

document-company-proprietary-data- 0084 011.PRPCOD017, 017.PRPCOD017,

rights-code 900.PRPCOD017

document-company-proprietary-data- 0117 017.PRPTXT017

rights-text

document-copyright-code 0012 011.CPYCOD013, 013.CPYCOD013,

900.CPYCOD013

document-copyright-text 0013 013.CPYTXT013

document-current-change-control- 0239 010.CCCENT010

authority-identifier

document-current-generic-revision- 0243 258.DOCCRV266, 266.DOCCRV266

identifier

document-current-security-classification- 0010 011.SECCOD011, 900.SECCOD900

code

document-custodial-enterprise-office- 0044 011.CUSOFF011

name

document-custodial-entity-identifier 0033 011.CUSORG011

document-distribution-controller- 0052 011.DISENT011, 900.DISENT900

enterprise-identifier

document-distribution-controller- 0044 011.DISOFF011, 900.DISOFF900

enterprise-office-name

document-distribution-restriction- 0082 011.DISDAT011, 900.DISDAT900

determination-date

document-distribution-statement-code 0014 011.DISCOD014, 014.DISCOD014,

900.DISCOD014, 953.DISCOD014

document-distribution-statement-text 0016 (Basic Standard Data Element--see

applicable role name.)

document-downgrade-security- 0010 011.SDWNCD011, 900.SDWNCD900

classification-code

document-effective-cut--off-event-delta- 0161 (Basic Standard Data Element--see

text applicable role name.)

document-export-control-code 0079 011.EXPCOD015, 015.EXPCOD015,

900.EXPCOD015

D-30
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-export-control-warning-text 0080 015.EXPTXT015

document-file-name 0211 900.FILNAM900

document-file-compression-code 0215 900.CMPCOD900

document-file-compression-method-code 0214 900.CMPMTH900

document-file-description-text 0212 900.FILDES900

document-file-electronic-storage-place- 0209 900.FILLOC900

identifier

document-file-originator-human-name 0069 812.RFILOR812, 858.RFILOR858,

867.RFILOR867, 968.RFILOR968

document-file-type-code 0210 900.FILTYP900

document-format-compliance-indicator- 0143 460.DODCOD460, 550.DODCOD550

code

document-generic-revision-identifier 0243 (List is too long to include here, see

D.5.1.5.)

document-identification-type-code 0101 010.IDNTYP010

document-lead-activity-indicator-code 0006 550.ACQCOD550

document-long-distribution-statement- 0016 014.LNSTMT014

text

document-origination-entity-identifier 0033 010.ORIGIN010

document-parts-list-entry-component- 0241 224.COMPTY224, 316.COMPTY316

type-code

document-parts-list-entry-priority- 0258 224.ALTFLG224, 316.ALTFLG316

indicator-code

document-parts-list-entry-sequence- 0259 220.PLSEQN224, 221.PLSEQN224,

identifier 222.PLSEQN224, 224.PLSEQN224,
225.PLSEQN224, 227.PLSEQN224,
316.PLSEQN316, 318.PLSEQN316,
319.PLSEQN316, 320.PLSEQN316,
321.PLSEQN316, 322.PLSEQN316

document-preparation-date 0082 011.PREPDT011

document-procuring-activity--assigned- 0178 670.PANNUM670, 671.PANNUM670,

identifier 672.PANNUM670

D-31
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-reference-citation 0075 alias for: document-reference-citation-

identifier

document-reference-citation-identifier 0075 679.DOCREF679, 680.DOCREF680,

681.DOCREF681, 953.CDR050953

document-representation-file-creation- 0082 alias for: electronic-document-

date representation-file-creation-date

document-representation-file-creation- 0160 alias for: electronic-document-

time representation-file-creation-time

document-representation-file-identifier 0206 alias for: electronic-document-

representation-file-identifier

document-representation-file-originator 0069 alias for: document-file-originator-human-

name

document-representation-file-originator- 0081 alias for: enterprise-document-file-

office-address origination-office-address-text

document-representation-identifier 0207 800.REPIDN800, 801.REPIDN800,

802.REPIDN800, 803.REPIDN800,
804.REPIDN800, 805.REPIDN800,
806.REPIDN800, 807.REPIDN800,
811.REPIDN800, 812.REPIDN800,
858.REPIDN800, 861.REPIDN800,
867.REPIDN800, 966.REPIDN800,
968.REPIDN800

document-representation-creation-date 0082 801.REPDAT801

document-representation-next-release- 0082 alias for: document-representation-release-

status-suspense-date process-next-status-suspense-date

document-representation-release- 0069 alias for: document-representation-release-

dispositioner-name process-dispositioner-human-name

document-representation-release- 0217 alias for: document-representation-release-

limitations limitations-text

document-representation-release- 0217 806.RELLIM806

limitations-text

document-representation-release-process- 0021 803.REPSTA803, 804.REPSTA803,

disposition-status-code 805.REPSTA803, 806.REPSTA803,
807.REPSTA803, 811.REPSTA803,
858.REPSTA803, 861.REPSTA803,
867.REPSTA803, 966.REPSTA803

D-32
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-representation-release-process- 0082 803.RELDAT803

disposition-status-date

document-representation-release-process- 0069 803.DISPNM803

dispositioner-human-name

document-representation-release-process- 0082 803.NSTATD803

next-status-suspense-date

document-representation-release-process- 0021 811.TECHCD811

technical-recommended-disposition-
status-code

document-representation-release-status- 0021 alias for: document-representation-release-

code process-disposition-status-code

document-representation-release-status- 0082 alias for: document-representation-release-

date process-disposition-status-date

document-representation-release-type- 0216 806.RELTYP806

code

document-representation-revision 0208 alias for: document-representation-

revision-identifier

document-representation-revision- 0208 801.REPREV801, 802.REPREV801,

identifier 803.REPREV801, 804.REPREV801,
805.REPREV801, 806.REPREV801,
807.REPREV801, 811.REPREV801,
812.REPREV801, 858.REPREV801,
861.REPREV801, 867.REPREV801,
966.REPREV801, 968.REPREV801

document-representation-revision- 0033 alias for: document-representation-

originator revision-originator-entity-identifier

document-representation-revision- 0033 801.REPORG801

originator-entity-identifier

document-revised-sheet-change- 0082 052.SHTDAT052

incorporation-date

document-revision 0009 alias for: document-alphanumeric-

revision-identifier

document-revision-application-activity- 0021 861.AREVST861, 862.AREVST861,

approval-process-disposition-status-code 863.AREVST861, 864.AREVST861,
865.AREVST861, 866.AREVST861,
867.AREVST861, 967.AREVST861

D-33
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-revision-application-activity- 0082 861.AREVDT861, 862.AREVDT861,

approval-process-disposition-status-date 863.AREVDT861, 864.AREVDT861,
865.AREVDT861, 866.AREVDT861,
867.AREVDT861, 967.AREVDT861

document-revision-approval- 0069 alias for: document-revision-approval-

dispositioner-name process-dispositioner-human-name

document-revision-approval-process- 0021 262.REVSTA850, 271.REVSTA850,

disposition-status-code 292.REVSTA850, 294.REVSTA850,
295.REVSTA850, 308.REVSTA850,
356.REVSTA850, 370.REVSTA850,
373.REVSTA850, 374.REVSTA850,
535.REVSTA850, 806.REVSTA850,
807.REVSTA850, 850.REVSTA850,
851.REVSTA850, 853.REVSTA850,
854.REVSTA850, 855.REVSTA850,
863.REVSTA850

document-revision-approval-process- 0082 262.STADAT850, 271.STADAT850,

disposition-status-date 292.STADAT850, 294.STADAT850,
295.STADAT850, 308.STADAT850,
356.STADAT850, 370.STADAT850,
373.STADAT850, 374.STADAT850,
535.STADAT850, 806.STADAT850,
807.STADAT850, 850.STADAT850,
851.STADAT850, 853.STADAT850,
854.STADAT850, 855.STADAT850,
863.STADAT850

document-revision-approval-process- 0069 850.PERNAM850

dispositioner-human-name

document-revision-approval-process- 0082 850.NXSTDT850, 861.NSTATD861

next-status-suspense-date

document-revision-approval-process- 0082 806.SUBDAT852, 852.SUBDAT852,

submission-date 857.SUBDAT852, 858.SUBDAT852

document-revision-approval-process- 0021 806.SUBSTA852, 852.SUBSTA852,

submission-disposition-status-code 857.SUBSTA852, 858.SUBSTA852

document-revision-approval-status-code 0021 alias for: document-revision-approval-

process-disposition-status-code

document-revision-approval-status-date 0082 alias for: document-revision-approval-

process-disposition-status-date

document-revision-next-approval-status- 0082 alias for: document-revision-approval-

suspense-date process-next-status-suspense-date

D-34
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-revision-submit-code 0021 alias for: document-revision-approval-

process-submission-disposition-status-code

document-revision-submit-date 0082 alias for: document-revision-approval-

process-submission-date

document-security-access-restriction-code 0085 018.ACCCOD018, 019.ACCCOD018,

901.ACCCOD018

document-security-access-restriction- 0157 alias for: document-security-access-

description restriction-text

document-security-access-restriction-text 0157 018.ACCTXT018

document-security-classification-code 0010 012.SECCOD012

document-security-classification-date 0082 011.SCLSDT011, 900.SCLSDT900

document-security-classification-name 0011 012.SECCLS012

document-security-classification- 0155 011.SECAUT011, 900.SECAUT900

authority-text

document-security-classification- 0082 011.SDWNDT011, 900.SDWNDT900

downgrade-date

document-security-classification- 0156 011.SDWNEV011, 900.SDWNEV900

downgrade-process-event-name

document-security-declassification-date 0082 011.SDCLDT011, 900.SDCLDT900

document-security-declassification- 0156 011.SDCLEV011, 900.SDCLEV900

process-event-name

document-sheet-identifier 0026 052.SHTNUM052

document-sheet-size 0112 alias for: document-sheet-size-code

document-sheet-size-code 0112 051.DWGSIZ051

document-sheet-total 0110 alias for: document-sheet-total-quantity

document-sheet-total-quantity 0110 051.DWGSHT051

document-short-distribution-statement- 0016 014.SHSTMT014

text

document-source-cage-code 0001 alias for: document-source-enterprise-

defense-logistics--assigned-identification-
code

D-35
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

document-source-enterprise-identifier 0052 020.SRCENT020, 021.SRCENT020,

044.SRCENT044, 045.SRCENT044,
400.SRCENT020, 401.SRCENT020,
650.SRCENT020, 651.SRCENT020

document-source-enterprise-defense- 0001 022.SRCCAG022, 023.SRCCAG022,

logistics--assigned-identification-code 430.SRCCAG022, 431.SRCCAG022,
704.SRCCAG022

document-source-entity-identifier 0033 (List is too long to include here, see

D.5.1.6.)

document-source-entity-type-code 0100 alias for: document-source-identification-

type-code

document-source-identification-type-code 0100 010.ENTTYP010

document-source-organization-identifier 0096 024.SRCORG024, 025.SRCORG024,

046.SRCORG046, 047.SRCORG046,
288.SRCORG024, 305.SRCORG024,
310.SRCORG024, 402.SRCORG024,
403.SRCORG024

document-superseded-alphanumeric- 0009 271.OLDREV271

revision-identifier

document-superseded-revision 0009 alias for: document-superseded-

alphanumeric-revision-identifier

document-supplement-type-code 0162 alias for: supplement-document-type-code

document-title 0008 alias for: document-name

document-type-code 0004 (List is too long to include here, see

D.5.1.7.)

dod-indicator-code 0143 alias for: document-format-compliance-

indicator-code

dod-organization-type-identifier 0097 alias for: united-states-defense-

department-organization-type-identifier

downgrade-security-classification 0010 alias for: document-downgrade-security-

classification-code

drawing-alphanumeric-identifier 0003 alias for: engineering-drawing-document-

alphanumeric-identifier

drawing-note-number 0251 alias for: engineering-drawing-document-

note-identifier

D-36
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

drawing-note-text 0252 alias for: engineering-drawing-document-

note-text

drawing-revision 0009 alias for: engineering-drawing-document-

current-alphanumeric-revision-identifier

drawing-sheet-revision 0009 alias for: engineering-drawing-document-

sheet-alphanumeric-revision-identifier

drawing-special-condition-code 0257 alias for: engineering-drawing-document-

special-condition-code

DWG 0004 alias for: engineering-drawing-document-

type-code

ECP 0004 alias for: engineering-change-proposal-

document-type-code

ecp-alphanumeric-identifier 0003 alias for: engineering-change-proposal-

document-alphanumeric-identifier

ecp-cage-code 0001 alias for: engineering-change-proposal-

document-source-enterprise-defense-
logistics--assigned-identification-code

ecp-change-class-concurrence-code 0021 alias for: engineering-change-proposal-

document-class-concurrence-process-
disposition-status-code

ecp-change-description-text 0171 alias for: change-proposal-document-

change-description-text

ecp-change-need-text 0171 alias for: change-proposal-document-

change-justification-text

ecp-class-type-code 0164 alias for: engineering-change-proposal-

document-change-class-code

ecp-cost 0172 alias for: engineering-change-proposal-

document-cost-amount

ecp-cost-component-code 0002 alias for: engineering-change-proposal-

cost--affected-enterprise-acronym-
identification-code

ecp-estimated-total-cost 0172 alias for: engineering-change-proposal-

document-estimated-total-cost-amount

ecp-estimated-under-contract-cost 0172 alias for: engineering-change-proposal-

document-estimated-under-contract-
subtotal-cost-amount

D-37
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

ecp-format-type-code 0194 alias for: engineering-change-proposal-

document-format-type-code

ecp-implementation-action-identifier 0072 alias for: engineering-change-

implementation-process-action-identifier

ecp-implementation-action-item- 0185 alias for: engineering-change-

description implementation-process-action-item-
description-text

ecp-implementation-action-responsible- 0052 alias for: engineering-change-

enterprise-identifier implementation-process-required-action-
responsible-enterprise-identifier

ecp-implementation-action-responsible- 0044 alias for: engineering-change-

office implementation-required-action-
responsible-enterprise-office-name

ecp-implementation-action-status-code 0021 alias for: engineering-change-

implementation-process-action-disposition-
status-code

ecp-implementation-action-status-date 0082 alias for: engineering-change-

implementation-process-action-disposition-
status-date

ecp-implementation-sequence-indicator- 0119 alias for: engineering-change-proposal-

code document-implementation-sequence-code

ecp-in--production-code 0223 alias for: engineering-change-proposal-

document-in--production-code

ecp-justification-code 0165 alias for: engineering-change-proposal-

document-justification-code

ecp-part-level-code 0121 alias for: engineering-change-proposal-

document-part-level-code

ecp-priority-code 0166 alias for: engineering-change-proposal-

document-priority-code

ecp-production-authority-need-date 0082 alias for: engineering-change-proposal-

document-production-contract-authority-
need-date

ecp-production-delivery-schedule-text 0171 alias for: change-proposal-document-

production-delivery-schedule-effect-text

ecp-retrofit-authority-need-date 0082 alias for: engineering-change-proposal-

document-retrofit-contract-authority-need-
date

D-38
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

ecp-revision 0009 alias for: engineering-change-proposal-

document-alphanumeric-revision-identifier

ecp-revision-approved-status-code 0021 alias for: engineering-change-proposal-

document-revision-approval-process-
approved-disposition-status-code

ecp-revision-approved-status-date 0082 alias for: engineering-change-proposal-

document-revision-approval-process-
approval-disposition-status-date

ecp-service-downtime 0184 alias for: predicted-asset-service-period-

downtime-days-quantity

ecp-unusual-effect-title 0263 alias for: engineering-change-proposal-

document-unusual-effect-name

electronic-document-comment-file- 0206 812.CFILID812, 858.CFILID858,

identifier 867.CFILID867, 968.CFILID968

electronic-document-comment-file- 0082 812.CFILDT812, 812.CFILTM812,

creation-date 858.CFILDT858, 858.CFILTM858,
867.CFILDT867, 867.CFILTM867,
968.CFILDT968

electronic-document-comment-file- 0160 968.CFILTM968

creation-time

electronic-document-file-identifier 0206 232.FILIDN900, 252.FILIDN900,

261.FILIDN900, 314.FILIDN900,
358.FILIDN900, 802.FILIDN900,
900.FILIDN900, 901.FILIDN900,
903.FILIDN900

electronic-document-file-creation-date 0082 232.FILDAT900, 252.FILDAT900,

261.FILDAT900, 314.FILDAT900,
358.FILDAT900, 802.FILDAT900,
900.FILDAT900, 903.FILDAT900

electronic-document-file-creation-time 0160 232.FILTIM900, 252.FILTIM900,

261.FILTIM900, 314.FILTIM900,
358.FILTIM900, 802.FILTIM900,
900.FILTIM900, 903.FILTIM900

electronic-document-representation-file- 0206 812.RFILID812, 858.RFILID858,

identifier 867.RFILID867, 968.RFILID968

electronic-document-representation-file- 0082 812.RFILDT812, 812.RFILTM812,

creation-date 858.RFILDT858, 858.RFILTM858,
867.RFILDT867, 867.RFILTM867,
968.RFILDT968

D-39
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

electronic-document-representation-file- 0160 968.RFILTM968

creation-time

electronic-storage-place-identifier 0209 (Basic Standard Data Element--see

applicable role name.)

electrostatic/electromagnetic- 0074 alias for: materiel-item-supply-

susceptability-code electrostatic-discharge-electromagnetic-
interference-code

email-address 0225 alias for: human-electronic-mail-access-

identifier

ending-effectivity-product-tracking- 0058 alias for: product-ending-effectivity-

identifier sequential-tracking-identifier

engineering-change-implementation- 0072 262.ECPACT262, 264.ECPACT262,

process-action-identifier 565.ECPACT262, 615.ECPACT262,
616.ECPACT262, 617.ECPACT262,
618.ECPACT262, 619.ECPACT262

engineering-change-implementation- 0021 264.STACOD264

process-action-disposition-status-code

engineering-change-implementation- 0082 264.STADAT264

process-action-disposition-status-date

engineering-change-implementation- 0185 262.ACTDES262

process-action-item-description-text

engineering-change-implementation- 0052 262.RESPON262

process-required-action-responsible-
enterprise-identifier

engineering-change-implementation- 0044 262.RESOFF262

required-action-responsible-enterprise-
office-name

engineering-change-proposal-cost-- 0002 252.SERVID252

affected-enterprise-acronym-
identification-code

engineering-change-proposal-document- 0003 (List is too long to include here, see

alphanumeric-identifier D.5.1.8.)

D-40
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

engineering-change-proposal-document- 0009 251.ECPREV251, 252.ECPREV251,

alphanumeric-revision-identifier 253.ECPREV251, 254.ECPREV251,
255.ECPREV251, 256.ECPREV251,
257.ECPREV251, 258.ECPREV251,
259.ECPREV251, 260.ECPREV251,
261.ECPREV251, 262.ECPREV251,
263.ECPREV251, 264.ECPREV251,
265.ECPREV251, 266.ECPREV251,
271.ECPREV251, 284.ECPREV251,
289.ECPREV251, 290.ECPREV251,
291.ECPREV251, 292.ECPREV251,
293.ECPREV251, 294.ECPREV251,
295.ECPREV251, 303.ECPREV251,
309.ECPREV251, 493.ECPREV251,
565.ECPREV251, 615.ECPREV251,
616.ECPREV251, 617.ECPREV251,
618.ECPREV251, 619.ECPREV251,
705.ECPREV251

engineering-change-proposal-document- 0164 251.ECP050251

change-class-code

engineering-change-proposal-document- 0021 251.ECP27C251

class-concurrence-process-disposition-
status-code

engineering-change-proposal-document- 0082 251.ECP27F251

contract-administration-change-class-
concurrence-date

engineering-change-proposal-document- 0172 (Basic Standard Data Element--see

cost-amount applicable role name.)

engineering-change-proposal-document- 0172 289.PRDCOS289

estimated-production-cost-amount

engineering-change-proposal-document- 0172 289.RDTCOS289

estimated-research-cost-amount

engineering-change-proposal-document- 0172 289.TOTCOS289

estimated-total-cost-amount

engineering-change-proposal-document- 0172 289.CONCOS289

estimated-under-contract-subtotal-cost-
amount

engineering-change-proposal-document- 0194 251.ECP08E251

format-type-code

D-41
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

engineering-change-proposal-document- 0119 251.ECPSEQ251

implementation-sequence-code

engineering-change-proposal-document- 0223 251.ECP170251

in--production-code

engineering-change-proposal-document- 0165 289.ECP060289

justification-code

engineering-change-proposal-document- 0121 258.PARLVL258

part-level-code

engineering-change-proposal-document- 0166 289.ECP070289

priority-code

engineering-change-proposal-document- 0082 289.ECP50A289

production-contract-authority-need-date

engineering-change-proposal-document- 0082 290.ECP50B290

retrofit-contract-authority-need-date

engineering-change-proposal-document- 0195 263.RETLVL263

retrofit-installation-level-code

engineering-change-proposal-document- 0082 309.ECPDAT309

revision-approval-process-approval-
disposition-status-date

engineering-change-proposal-document- 0021 309.ECPSTA309

revision-approval-process-approved-
disposition-status-code

engineering-change-proposal-document- 0001 (List is too long to include here, see

source-enterprise-defense-logistics-- D.5.1.9.)
assigned-identification-code

engineering-change-proposal-document- 0004 (List is too long to include here, see

type-code D.5.1.10.)

engineering-change-proposal-document- 0263 265.IMPNAM265

unusual-effect-name

engineering-drawing-document- 0003 (List is too long to include here, see

alphanumeric-identifier D.5.1.11.)

engineering-drawing-document-current- 0009 052.CURREV052

alphanumeric-revision-identifier

D-42
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

engineering-drawing-document-note- 0251 080.NOTNUM080, 081.NOTNUM080,

identifier 085.NOTNUM080, 086.NOTNUM080,
087.NOTNUM080, 226.NOTNUM080,
325.NOTNUM325, 326.NOTNUM325,
327.NOTNUM325

engineering-drawing-document-note-text 0252 080.NOTTXT080, 325.NOTTXT325

engineering-drawing-document- 0261 317.CHGTYP317, 323.CHGTYP323,

proposed-change-type-code 324.CHGTYP324, 326.CHGTYP326,
327.CHGTYP327

engineering-drawing-document- 0260 315.CHGTYP315, 316.CHGTYP316,

proposed-entry-change-type-code 318.CHGTYP318, 325.CHGTYP325

engineering-drawing-document-sheet- 0009 052.SHTREV052

alphanumeric-revision-identifier

engineering-drawing-document-special- 0257 081.SPNOTE081, 227.SPNOTE227,

condition-code 324.SPNOTE324, 327.SPNOTE327

engineering-drawing-document-type-code 0004 062.DWGTYP062, 064.DWGTYP064,

065.DWGTYP065, 069.DWGTYP069,
163.DWGTYP163, 164.DWGTYP163,
165.DWGTYP165, 166.DWGTYP165,
285.DWGTYP285, 311.DWGTYP285

enterprise-division 0228 alias for: enterprise-division-identifier

enterprise-identifier 0052 002.ENTIDN002, 565.ENTIDN002,

615.ENTIDN002, 616.ENTIDN002,
617.ENTIDN002, 618.ENTIDN002,
619.ENTIDN002, 676.ENTIDN002,
700.ENTIDN002, 701.ENTIDN002,
702.ENTIDN002, 703.ENTIDN002,
704.ENTIDN002, 705.ENTIDN002,
706.ENTIDN002, 940.ENTIDN002,
941.ENTIDN002

enterprise-name 0170 004.ENTNAM004

enterprise-acronym-identification-code 0002 Part of data element string: data-item-

description-document-identifier.

enterprise-address-text 0039 940.ADDRES940

enterprise-administrative-contracting- 0081 950.ACOADD950

office-address-text

enterprise-comment-file-origination- 0081 812.CFILAD812, 858.CFILAD858,

office-address-text 867.CFILAD867, 968.CFILAD968

D-43
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

enterprise-defense-logistics--assigned- 0001 003.CAGNUM003, 006.CAGNUM003,

identification-code 007.CAGNUM003

enterprise-defense-logistics--assigned- 0102 003.CAGTYP003

identification-type-code

enterprise-division-identifier 0228 (Basic Standard Data Element--see

applicable role name.)

enterprise-document-file-origination- 0081 812.RFILAD812, 858.RFILAD858,

office-address-text 867.RFILAD867, 968.RFILAD968

enterprise-file-origination-office-address- 0081 232.FILADD900, 252.FILADD900,

text 261.FILADD900, 314.FILADD900,
358.FILADD900, 802.FILADD900,
900.FILADD900, 901.FILADD900,
903.FILADD900

enterprise-file-review-office-address-text 0081 811.FREVAD811, 857.FREVAD857,

866.FREVAD866, 963.FILADD963,
964.FILADD963

enterprise-first-line-address-text 0090 Part of data element string: enterprise-

address-text.

enterprise-identification-type-code 0050 002.ENTTYP002

enterprise-office-name 0044 676.OFFSYM941, 941.OFFSYM941

enterprise-office-address-text 0081 700.DIVADD942, 702.DIVADD942,

803.DIVADD942, 850.DIVADD942,
861.DIVADD942, 942.DIVADD942,
943.DIVADD942, 962.DIVADD942

enterprise-procuring-contracting-office- 0081 950.PCOADD950

address-text

enterprise-second-line-address 0091 alias for: enterprise-second-line-address-

text

enterprise-second-line-address-text 0091 Part of data element string: enterprise-

address-text.

enterprise-security-classified-document- 0224 941.HICLAS941

receipt-authorization-code

entity-identifier 0033 000.ENTYID000

entity-type-code 0076 000.ENTTYP000

equipment-modification-process-period- 0087 460.WKHOUR460

work-hour-quantity

D-44
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

event-code 0018 alias for: process-event-code

event-name 0156 alias for: process-event-name

export-control-code 0079 alias for: document-export-control-code

export-control-warning-text 0080 alias for: document-export-control-

warning-text

fax-number 0225 alias for: human-facsimile-machine-

access-identifier

fbl-indicator 0138 alias for: functional-baseline-top--level-

document-indicator-code

federal-supply-class 0073 alias for: product-federal-supply-

classification-code

file-compression-code 0215 alias for: document-file-compression-code

file-compression-method-code 0214 alias for: document-file-compression-

method-code

file-creation-date 0082 alias for: electronic-document-file-

creation-date

file-creation-time 0160 alias for: electronic-document-file-

creation-time

file-description 0212 alias for: document-file-description-text

file-identifier 0206 alias for: electronic-document-file-

identifier

file-location 0209 alias for: document-file-electronic-storage-

place-identifier

file-name 0211 alias for: document-file-name

file-originator 0069 alias for: file-originator-human-name

file-originator-human-name 0069 232.FILORG900, 252.FILORG900,

261.FILORG900, 314.FILORG900,
358.FILORG900, 802.FILORG900,
900.FILORG900, 901.FILORG900,
903.FILORG900

file-originator-office-address 0081 alias for: enterprise-file-origination-office-

address-text

file-reviewer-human-name 0069 811.FREVNM811, 857.FREVNM857,

866.FREVNM866

D-45
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

file-reviewer-office-address 0081 alias for: enterprise-file-review-office-

address-text

file-reviewer-person-name 0069 alias for: file-reviewer-human-name

file-type-code 0210 alias for: document-file-type-code

find-identifier 0027 alias for: parts-list-document-item-

identifier

first-article-test-code 0077 alias for: materiel-item-first-article-test-

code

first-line-address 0090 alias for: enterprise-first-line-address-text

first-name 0067 alias for: human-given-name

functional-baseline-top--level-document- 0138 100.FBLFLG100

indicator-code

geographic-location 0029 alias for: geographic-place-name

geographic-place-name 0029 260.RETLOC260

glaa-code 0128 alias for: application-activity-program-

government-lead-indicator-code

government-serial-identifier 0175 alias for: product-government-serial-

tracking-identifier

government-technical-monitor-division 0228 alias for: tasking-activity-enterprise-

technical-monitor-division-identifier

graphic-drawing-revision 0009 alias for: graphic-engineering-drawing-

document-alphanumeric-revision-identifier

graphic-engineering-drawing-document- 0009 064.GDWGRV064

alphanumeric-revision-identifier

hazardous-material-code 0078 alias for: materiel-item-supply-hazardous-

material-code

higher-level-ccb 0089 alias for: program-higher-level-

configuration-control-board-text

IL 0004 alias for: index-list-drawing-document-

type-code

human-name 0069 700.PERNAM943, 702.PERNAM943,

861.PERNAM943, 943.PERNAM943

D-46
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

human-access-identifier 0225 (Basic Standard Data Element--see

applicable role name.)

human-electronic-mail-access-identifier 0225 943.EMAILX943

human-facsimile-machine-access- 0225 942.FAXNUM942, 943.FAXNUM943

identifier

human-family-name 0068 Part of data element string: human-name.

human-given-name 0067 Part of data element string: human-name.

human-responsibility-description-text 0154 702.RESPON702

human-telephone-access-identifier 0225 942.TELPHN942, 943.TELPHN943

implementation-action-item-description- 0185 alias for: implementation-process-action-

text item-description-text

implementation-process-action-item- 0185 (Basic Standard Data Element--see

description-text applicable role name.)

index-list-cage-code 0001 alias for: index-list-drawing-document-

design-enterprise-defense-logistics--
assigned-identification-code

index-list-drawing-document- 0003 068.ILNUMB068

alphanumeric-identifier

index-list-drawing-document- 0009 068.ILREVN068

alphanumeric-revision-identifier

index-list-drawing-document-design- 0001 068.ILCAGE068

enterprise-defense-logistics--assigned-
identification-code

index-list-drawing-document-type-code 0004 065.ILTYPE065, 066.ILTYPE065,

067.ILTYPE065, 068.ILTYPE065

index-list-identifier 0003 alias for: index-list-drawing-document-

alphanumeric-identifier

index-list-revision 0009 alias for: index-list-drawing-document-

alphanumeric-revision-identifier

interface-configuration-item-product- 0129 251.ECP100251

affected-code

interface-control-document-indicator- 0030 010.ICDCOD010

code

D-47
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

international-document-source- 0002 404.SRCINT404

enterprise-acronym-identification-code

international-document-source- 0002 alias for: international-document-source-

enterprise-organization-code enterprise-acronym-identification-code

international-enterprise-acronym- 0002 039.INTORG039

identification-code

international-organization-code 0002 alias for: international-enterprise-

acronym-identification-code

julian-year-period-identifier 0219 670.YEARNO670, 671.YEARNO670,

672.YEARNO670

last-name 0068 alias for: human-family-name

lead-activity-flag 0006 alias for: document-lead-activity-

indicator-code

limited-duration-technical-order- 0255 466.LVLCOD466

document-maintenance-level-code

limited-duration-technical-order- 0248 466.PRICOD466

document-priority-code

long-distribution-statement 0016 alias for: document-long-distribution-

statement-text

manufacture-date 0082 alias for: product-manufacture-date

manufacture-time 0160 alias for: product-manufacture-time

material-product-classification-type-code 0036 (Basic Standard Data Element--see

applicable role name.)

material-product-classification-type-name 0037 (Basic Standard Data Element--see

applicable role name.)

material-product-design-release-date 0082 200.RELDAT200

material-sixth-type-code 0036 alias for: material-product-sixth-

classification-type-code

material-sixth-type-name 0037 alias for: material-product-sixth-

classification-type-name

material-status-code 0035 alias for: material-product-status-code

D-51
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

material-third-type-code 0036 alias for: material-product-third-

classification-type-code

material-third-type-name 0037 alias for: material-product-third-

classification-type-name

material-type-code 0036 alias for: material-product-classification-

type-code

material-type-name 0037 alias for: material-product-classification-

type-name

materiel-item-first-article-test-code 0077 051.FRSTRT051, 101.FRSTRT101

materiel-item-supply-electrostatic- 0074 200.STATIC200, 210.STATIC210

discharge-electromagnetic-interference-
code

materiel-item-supply-hazardous-material- 0078 200.HAZMAT200, 210.HAZMAT210

code

materiel-item-supply-precious-metals- 0093 200.METALS200, 210.METALS210

indicator-code

media-type 0238 alias for: software-product-storage-

medium-type-name

military-specification-alphanumeric- 0003 alias for: united-states-defense-

identifier specification-document-alphanumeric-
identifier

military-standard-document-identifier 0003 alias for: united-states-defense-standard-

document-alphanumeric-identifier

miltary-handbook-alphanumeric- 0003 alias for: united-states-defense-handbook-

identifier document-alphanumeric-identifier

modification-instruction-alphanumeric- 0003 alias for: modification-instruction-

identifier document-alphanumeric-identifier

modification-instruction-description 0253 alias for: modification-instruction-

document-task-description-text

modification-instruction-document- 0122 460.MINIDN460, 461.MINIDN460,

identifier 463.MINIDN460, 490.MINIDN460,
491.MINIDN460, 492.MINIDN460,
493.MINIDN460, 494.MINIDN460,
536.MINIDN460

D-52
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

modification-instruction-document- 0003 462.MINNUM462, 466.MINNUM462,

alphanumeric-identifier 469.MINNUM462, 470.MINNUM462,
471.MINNUM462, 472.MINNUM462

modification-instruction-document- 0082 460.EFFDAT460

effective-date

modification-instruction-document-issue- 0082 460.ISSDAT460

date

modification-instruction-document- 0082 460.CNXDAT460

rescission-date

modification-instruction-document- 0033 460.MINSRC460, 461.MINSRC460,

source-entity-identifier 463.MINSRC460, 490.MINSRC460,
491.MINSRC460, 492.MINSRC460,
493.MINSRC460, 494.MINSRC460,
536.MINSRC460

modification-instruction-document- 0141 462.MINSUB462

subsidiary-type-code

modification-instruction-document-task- 0253 460.MODDES460

description-text

modification-instruction-document-type- 0004 460.MINTYP460, 461.MINTYP460,

code 462.MINTYP460, 463.MINTYP460,
464.MINTYP460, 465.MINTYP460,
466.MINTYP460, 467.MINTYP460,
468.MINTYP460, 469.MINTYP460,
470.MINTYP460, 471.MINTYP460,
472.MINTYP460, 490.MINTYP460,
491.MINTYP460, 492.MINTYP460,
493.MINTYP460, 494.MINTYP460,
536.MINTYP460, 560.MINTYP460

modification-instruction-effective-date 0082 alias for: modification-instruction-

document-effective-date

modification-instruction-identifier 0122 alias for: modification-instruction-

document-identifier

modification-instruction-issue-date 0082 alias for: modification-instruction-

document-issue-date

modification-instruction-rescission-date 0082 alias for: modification-instruction-

document-rescission-date

modification-instruction-source-identifier 0033 alias for: modification-instruction-

document-source-entity-identifier

D-53
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

modification-instruction-type 0141 alias for: modification-instruction-

document-subsidiary-type-code

modification-kit-identifier 0245 alias for: modification-kit-product-

identifier

modification-kit-product-identifier 0245 490.KITIDN490, 492.KITIDN490

modification-process-period-work-hour- 0087 alias for: equipment-modification-process-

quantity period-work-hour-quantity

modification-request-document-identifier 0122 460.MRQIDN460

modification-request-document-source- 0033 460.MRQSRC460

entity-identifier

modification-request-document- 0142 450.MODSUB450

subsidiary-type-code

modification-request-document-type-code 0004 450.MRQTYP450, 451.MRQTYP450,

452.MRQTYP450, 453.MRQTYP450,
454.MRQTYP450, 460.MRQTYP450

modification-request-identifier 0122 alias for: modification-request-document-

identifier

modification-request-source-identifier 0033 alias for: modification-request-document-

source-entity-identifier

modification-request-type-code 0142 alias for: modification-request-document-

subsidiary-type-code

modification-work-order-document- 0250 467.LVLCOD467

maintenance-level-code

modification-work-order-document- 0246 467.PRICOD467

priority-code

modified-material-generic-identifier 0092 alias for: modified-material-product-

generic-identifier

modified-material-identification 0038 alias for: modified-material-product-

identifier

modified-material-product-identifier 0038 534.MMATID534

modified-material-product-generic- 0092 534.MMATGI534

identifier

modified-part-identifier 0024 alias for: modified-part-product-identifier

D-54
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

MODINST 0004 alias for: modification-instruction-

document-type-code

MODREQ 0004 alias for: modification-request-document-

type-code

modified-part-product-identifier 0024 531.MPARNO531, 532.MPARNO532,

533.MPARNO533

modified-product-design-enterprise- 0052 531.MDESEN531, 532.MDESEN532,

identifier 533.MDESEN533, 534.MDESEN534

mwo-identifier 0003 alias for: united-states-army-modification-

work-order-document-alphanumeric-
identifier

mwo-maintenance-level 0250 alias for: modification-work-order-

document-maintenance-level-code

mwo-priority-code 0246 alias for: modification-work-order-

document-priority-code

navy-command-identifier 0002 alias for: united-states-navy-command-

enterprise-acronym-identification-code

non--united-states-government- 0002 405.SRCFGV405

document-source-enterprise-acronym-
identification-code

non--united-states-government- 0002 037.FGOVOR037

enterprise-acronym-identification-code

non--united-states-nongovernment- 0002 406.SRCFNG406

document-source-enterprise-acronym-
identification-code

non--united-states-nongovernment- 0002 038.FNGVOR038

enterprise-acronym-identification-code

non--us-government-enterprise- 0002 alias for: non--united-states-government-

identification-code enterprise-acronym-identification-code

non--us-government-organization-code 0002 alias for: non--united-states-government-

document-source-enterprise-acronym-
identification-code

non--us-nongovernment-enterprise- 0002 alias for: non--united-states-

identification-code nongovernment-enterprise-acronym-
identification-code

D-55
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

non--us-nongovernment-organization- 0002 alias for: non--united-states-

code nongovernment-document-source-
enterprise-acronym-identification-code

NOR 0004 alias for: revision-notice-document-type-

code

nor-alphanumeric-identifier 0003 alias for: revision-notice-document-

alphanumeric-identifier

nor-cage-code 0001 alias for: revision-notice-document-

source-enterprise-defense-logistics--
assigned-identification-code

nor-implementation-authorization-code 0176 alias for: revision-notice-document-

implementation-authorization-code

nor-revision 0009 alias for: revision-notice-document-

alphanumeric-revision-identifier

nor-revision-approved-status-code 0021 alias for: revision-notice-document-

revision-approval-process-approved-
disposition-status-code

nor-revision-approved-status-date 0082 alias for: revision-notice-document-

revision-approval-process-approved-
disposition-status-date

nsn 0049 alias for: product-national-stock-identifier

nsn-description 0116 alias for: product-national-stock-

description-text

office-address 0081 alias for: enterprise-office-address-text

office-symbol 0044 alias for: enterprise-office-name

operating-system-software-identifier 0031 alias for: computer-operating-system-

software-asset-identifier

operating-system-software-version 0064 alias for: computer-operating-system-

software-asset-version-identifier

organization-code 0002 alias for: enterprise-acronym-

identification-code

organization-identifier 0096 004.ORGIDN004

organization-type-identifier 0095 004.ORGTYP004

original-design-enterprise-identifier 0052 531.ODESEN531, 532.ODESEN532,

533.ODESEN533, 534.ODESEN534

D-56
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

original-material-generic-identifier 0092 alias for: original-material-product-

generic-identifier

original-material-identification 0038 alias for: original-material-product-

identifier

original-material-product-identifier 0038 534.OMATID534

original-material-product-generic- 0092 534.OMATGI534

identifier

original-part-identifier 0024 alias for: original-part-product-identifier

original-part-product-identifier 0024 531.OPARNO531, 532.OPARNO532,

533.OPARNO533

other-attachment-affect-code 0198 alias for: contract-modification-document-

other-attachment-affect-code

other-exhibit-affect-code 0198 alias for: contract-modification-document-

other-exhibit-affect-code

other-system-cis-affected-code 0129 alias for: interface-configuration-item-

product-affected-code

P-SPEC 0004 alias for: program--unique-specification-

document-type-code

pan 0178 alias for: document-procuring-activity--

assigned-identifier

part-administrative-identifier 0024 alias for: part-product-administrative-

control-identifier

part-basic-identifier 0024 alias for: part-product-basic-identifier

part-identifier 0024 alias for: part-product-identifier

part-model-database-document-generic- 0243 231.PMODRV231, 232.PMODRV231

revision-identifier

part-model-generic-revision 0243 alias for: part-model-database-document-

generic-revision-identifier

part-name 0113 alias for: part-product-name

part-product-identifier 0024 (List is too long to include here, see

D.5.1.12.)

part-product-name 0113 209.PARNAM209, 210.PARNAM209

D-57
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

part-product-administrative-control- 0024 055.CONPIN055, 056.CONPIN056

identifier

part-product-basic-identifier 0024 919.BPINNO919, 925.BPINNO919,

926.BPINNO919

part-product-bulk-measurement-unit-code 0054 210.WGTCOD210

part-product-release-date 0082 210.RELDAT210

part-product-revision-identifier 0181 925.PINREV925, 926.PINREV925

part-product-status-code 0035 054.PARSTA054, 105.PARSTA105,

423.PARSTA423, 437.PARSTA437

part-product-unit-weight 0114 210.PARWGT210

part-product-vendor--assigned-identifier 0024 056.VPARNO056

part-release-date 0082 alias for: part-product-release-date

part-revision-identifier 0181 alias for: part-product-revision-identifier

part-status-code 0035 alias for: part-product-status-code

part-unit-weight 0114 alias for: part-product-unit-weight

part-weight-code 0054 alias for: part-product-bulk-measurement-

unit-code

parts-list-alphanumeric-identifier 0003 alias for: parts-list-drawing-document-

alphanumeric-identifier

parts-list-cage-code 0001 alias for: parts-list-drawing-document-

source-enterprise-defense-logistics--
assigned-identification-code

parts-list-document-item-identifier 0027 208.FINDID219, 219.FINDID219,

220.FINDID219, 221.FINDID219,
222.FINDID219, 224.FINDID219,
225.FINDID219, 226.FINDID219,
315.FINDID315, 316.FINDID315,
318.FINDID315, 319.FINDID315,
320.FINDID315, 321.FINDID315,
322.FINDID315, 323.FINDID315,
324.FINDID315, 326.FINDID315

parts-list-drawing-document- 0003 068.PLNUMB068

alphanumeric-identifier

parts-list-drawing-document- 0009 064.PLREVN064, 068.PLREVN068

alphanumeric-revision-identifier

D-58
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

parts-list-drawing-document-source- 0001 068.PLCAGE068

enterprise-defense-logistics--assigned-
identification-code

parts-list-drawing-document-type-code 0004 062.PLTYPE062, 064.PLTYPE064,

068.PLTYPE068, 286.PLTYPE286,
312.PLTYPE286

parts-list-drawing-revision 0009 alias for: parts-list-drawing-document-

alphanumeric-revision-identifier

pbl-top-level-document 0124 alias for: product-baseline-top-level-

document-identifier

pco-address 0081 alias for: enterprise-procuring-contracting-

office-address-text

pco-name 0069 alias for: product-procuring-contracting-

officer-human-name

performing-activity-enterprise-identifier 0052 alias for: performing-enterprise-identifier

performing-activity-enterprise-technical- 0228 954.PRFTEK954

monitor-division-identifier

performing-activity-poc-address 0081 alias for: performing-enterprise-contact-

office-address-text

performing-activity-poc-name 0069 alias for: contractor-human-name

performing-enterprise-identifier 0052 950.SELENT950

performing-enterprise-contact-office- 0081 950.SELADD950

address-text

period-length-quantity 0231 Part of data element string: contract-data-

submittal-document-event--delta-text.

period-unit-code 0232 Part of data element string: contract-data-

submittal-document-event--delta-text.

person-name 0069 alias for: human-name

PL 0004 alias for: parts-list-drawing-document-

type-code

pl-entry-sequence-number 0259 alias for: document-parts-list-entry-

sequence-identifier

place-postal-zone-code 0043 Part of data element string: enterprise-

address-text.

D-59
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

place-reference-designator-identifier 0055 208.REFDES208, 323.REFDES323

postal-zone 0043 alias for: place-postal-zone-code

precious-metals-indicator-code 0093 alias for: materiel-item-supply-precious-

metals-indicator-code

predicted-asset-service-period-downtime- 0184 263.ECP480263

days-quantity

preparation-date 0082 alias for: document-preparation-date

primary-alternate-flag 0258 alias for: document-parts-list-entry-

priority-indicator-code

primary-ecp-alphanumeric-identifier 0003 alias for: primary-engineering-change-

proposal-document-alphanumeric-
identifier

primary-ecp-cage-code 0001 alias for: primary-engineering-change-

proposal-document-source-enterprise-
defense-logistics--assigned-identification-
code

primary-ecp-document-type-code 0004 alias for: primary-engineering-change-

proposal-document-type-code

primary-ecp-indicator-code 0187 alias for: primary-engineering-change-

proposal-document-indicator-code

primary-engineering-change-proposal- 0003 251.PECPNO251

document-alphanumeric-identifier

primary-engineering-change-proposal- 0187 251.PECPFG251

document-indicator-code

primary-engineering-change-proposal- 0001 251.PECPCG251

document-source-enterprise-defense-
logistics--assigned-identification-code

primary-engineering-change-proposal- 0004 251.PECPTY251

document-type-code

primary-equipment-ci-identifier 0111 alias for: primary-equipment-

configuration-item-product-identifier

primary-equipment-configuration-item- 0111 694.PCIIDN694

product-identifier

prior-deviation-request-document- 0003 359.PRFDNO359

alphanumeric-identifier

D-60
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

prior-deviation-request-document-source- 0001 359.PRFDCG359

enterprise-defense-logistics--assigned-
identification-code

prior-rfd-alphanumeric-identifier 0003 alias for: prior-deviation-request-

document-alphanumeric-identifier

prior-rfd-cage-code 0001 alias for: prior-deviation-request-

document-source-enterprise-defense-
logistics--assigned-identification-code

process-action-comment-text 0066 262.ACTCOM262, 264.ACTCOM264,

370.ACTCOM370, 372.ACTCOM372,
676.ACTCOM676, 678.ACTCOM678

process-action-item-title-name 0136 262.ACTTTL262, 370.ACTTTL370,

676.ACTTTL676

process-disposition-status-code 0021 (Basic Standard Data Element--see

applicable role name.)

process-event-code 0018 961.EVNCOD961

process-event-name 0156 961.PRSNAM961

process-event-end-date 0082 961.PRSEDT961

process-event-start-date 0082 961.PRSSDT961

process-period-work-hour-quantity 0087 (Basic Standard Data Element--see

applicable role name.)

process-required-action-comment-text 0066 alias for: process-action-comment-text

process-required-action-description-text 0065 (Basic Standard Data Element--see

applicable role name.)

process-work-hours 0087 alias for: process-period-work-hour-

quantity

product-block-identifier 0175 alias for: product-block-tracking-identifier

product-effectivity-timing-type-code 0028 alias for: product-change-effectivity-

timing-type-code

product-effectivity-tracking-type 0057 alias for: product-change-effectivity-

tracking-type-code

product-lot-identifier 0175 alias for: product-lot-tracking-identifier

product-manufacturing-datecode 0175 alias for: product-manufacturing-datecode-

tracking-identifier

D-61
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

product-quantity 0019 260.QUANTY260, 263.KITQTY263,

523.QUANTY523, 526.QUANTY526,
529.QUANTY529, 530.QUANTY530

product--tracking-base--identifier 0056 200.BASNUM500, 210.BASNUM500,

237.BASNUM500, 238.BASNUM500,
239.BASNUM500, 240.BASNUM500,
241.BASNUM500, 259.BASNUM500,
361.BASNUM500, 366.BASNUM500,
400.BASNUM500, 491.BASNUM500,
494.BASNUM500, 500.BASNUM500,
501.BASNUM500, 502.BASNUM500,
503.BASNUM500, 504.BASNUM500,
505.BASNUM500, 506.BASNUM500,
508.BASNUM500, 509.BASNUM500,
510.BASNUM500, 511.BASNUM500,
515.BASNUM500, 516.BASNUM500,
517.BASNUM500, 518.BASNUM500,
519.BASNUM500, 520.BASNUM500,
521.BASNUM500, 522.BASNUM500,
523.BASNUM500, 525.BASNUM500,
526.BASNUM500, 528.BASNUM500,
529.BASNUM500, 530.BASNUM500,
535.BASNUM500, 536.BASNUM500

product-assembly-status-code 0174 242.STATCD242, 243.STATCD243,

244.STATCD244, 245.STATCD245

product-assembly-status-date 0082 242.STATDT242, 243.STATDT243,

244.STATDT244, 245.STATDT245

product-assembly-status-time 0160 242.STATTM242, 243.STATTM243,

244.STATTM244, 245.STATTM245

product-baseline-top-level-document- 0124 331.PBLDOC331, 332.PBLDOC331

identifier

product-baseline-type-code 0098 254.BLTYPE254, 351.BLTYPE351

product-block-tracking-identifier 0175 520.BLKNUM520, 521.BLKNUM520,

522.BLKNUM520, 525.BLKNUM520,
528.BLKNUM520

product-change-effectivity-timing-type- 0028 259.EFFTIM259

code

D-62
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

product-change-effectivity-tracking-type- 0057 237.TRKTYP515, 238.TRKTYP515,

code 239.TRKTYP515, 240.TRKTYP515,
241.TRKTYP515, 245.TRKTYP515,
256.TRKTYP515, 259.TRKTYP515,
260.TRKTYP515, 284.TRKTYP515,
293.TRKTYP515, 361.TRKTYP515,
362.TRKTYP515, 363.TRKTYP515,
364.TRKTYP515, 366.TRKTYP515,
491.TRKTYP515, 494.TRKTYP515,
515.TRKTYP515, 535.TRKTYP515,
536.TRKTYP515

product-change-retrofit-completion-date 0082 260.RETCOM260

product-ending-effectivity-sequential- 0058 237.ENDEFF237, 238.ENDEFF238,

tracking-identifier 239.ENDEFF239, 259.ENDEFF259,
361.ENDEFF361, 366.ENDEFF366,
491.ENDEFF491, 494.ENDEFF494

product-federal-supply-classification-code 0073 100.FSCCOD100

product-government-serial-tracking- 0175 517.GSNNUM517, 522.GSNNUM517,

identifier 532.GSNNUM517

product-identification-type-code 0123 921.PIDTYP921

product-interchangeability-code 0063 206.ONEWAY206, 207.ONEWAY207,

216.ONEWAY216, 217.ONEWAY217

product-lot-tracking-identifier 0175 518.LOTNUM518, 521.LOTNUM518,

522.LOTNUM518, 523.LOTNUM518,
525.LOTNUM518, 526.LOTNUM518,
528.LOTNUM518, 533.LOTNUM518,
534.LOTNUM518

product-manufacture-date 0082 515.MFRDAT515

product-manufacture-time 0160 515.MFRTIM515

product-manufacturer-serial-tracking- 0175 516.MSNNUM516, 521.MSNNUM516,

identifier 522.MSNNUM516, 531.MSNNUM516

product-manufacturing-datecode- 0175 519.DATCOD519, 529.DATCOD519,

tracking-identifier 530.DATCOD519

D-63
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

product-measurement-unit-code 0054 225.UOMCOD225, 242.UOMCOD242,

243.UOMCOD243, 244.UOMCOD244,
260.LOCUOM260, 318.UOMCOD318,
523.UOMCOD523, 524.UOMCOD524,
526.UOMCOD526, 527.UOMCOD527,
529.UOMCOD529, 530.UOMCOD530,
959.UOMCOD959, 960.UOMCOD960

product-national-stock-identifier 0049 200.NSNNUM345, 210.NSNNUM345,

345.NSNNUM345

product-national-stock-description-text 0116 345.NSNDES345

product-procuring-contracting-officer- 0069 950.PCONAM950

human-name

product-replacement-type-code 0106 206.REPTYP206, 207.REPTYP207,

216.REPTYP216, 217.REPTYP217,
346.REPTYP346

product-retrofit-requirement-code 0240 289.RTROCD289

product-royalty-expiration-date 0082 289.ECPROY289

product-sequential-tracking-identifier 0058 240.TRKIDN515, 241.TRKIDN515,

245.TRKIDN515, 515.TRKIDN515,
535.TRKIDN515, 536.TRKIDN515

product-service-life-period-quantity 0086 200.SRVCQY200, 210.SRVCQY210

product-service-life-period-unit-code 0232 200.SRVCCD200, 210.SRVCCD210

product-service-life-quantity 0086 alias for: product-service-life-period-

quantity

product-shipping-date 0082 960.SHPDAT960

product-starting-effectivity-sequential- 0058 237.STREFF237, 238.STREFF238,

tracking-identifier 239.STREFF239, 256.STREFF256,
259.STREFF259, 260.STREFF259,
284.STREFF284, 293.STREFF293,
361.STREFF361, 362.STREFF362,
363.STREFF363, 364.STREFF364,
366.STREFF366, 491.STREFF491,
494.STREFF494

product-status-code 0035 (Basic Standard Data Element--see

applicable role name.)

product-tracking-identifier 0058 alias for: product-sequential-tracking-

identifier

D-64
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

product-tracking-identifier 0175 (Basic Standard Data Element--see

applicable role name.)

product-tracking--base-source-code 0103 500.TRKSCD500

product-type-code 0034 100.PRDTYP100, 345.PRDTYP345,

400.PRDTYP400, 913.PRDTYP913,
914.PRDTYP914

program--unique-specification- 0003 alias for: program--unique-specification-

alphanumeric-identifier document-alphanumeric-identifier

program-name 0059 262.PROGNM691, 264.PROGNM691,

330.PROGNM691, 370.PROGNM691,
372.PROGNM691, 565.PROGNM691,
615.PROGNM691, 616.PROGNM691,
617.PROGNM691, 618.PROGNM691,
619.PROGNM691, 691.PROGNM691,
692.PROGNM691, 700.PROGNM691,
701.PROGNM691, 702.PROGNM691,
703.PROGNM691, 704.PROGNM691,
705.PROGNM691, 706.PROGNM691

program--unique-specification-change- 0193 620.SCNIDN620

notice-document-sequential-identifier

program--unique-specification-document- 0003 Part of data element string: revised-

alphanumeric-identifier program--unique-specification-document-
identifier.

program--unique-specification-document- 0009 110.SPECRV110

alphanumeric-revision-identifier

program--unique-specification-document- 0108 100.SUBTYP100

subsidiary-type-code

program--unique-specification-document- 0004 110.SPECTY110, 620.SPCTYP620

type-code

program-configuration-control-board- 0151 262.CCBNAM700, 264.CCBNAM700,

name 370.CCBNAM700, 372.CCBNAM700,
565.CCBNAM700, 615.CCBNAM700,
616.CCBNAM700, 617.CCBNAM700,
618.CCBNAM700, 619.CCBNAM700,
700.CCBNAM700, 702.CCBNAM700,
703.CCBNAM700, 704.CCBNAM700,
705.CCBNAM700, 706.CCBNAM700

program-configuration-control-board- 0082 704.CCBDAT704

decision-date

D-65
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

program-configuration-control-board- 0168 704.CCBMIN704

discussion-text

program-configuration-control-board- 0173 700.CCBTYP700

type-code

program-higher-level-configuration- 0089 700.TOPCCB700

control-board-text

program-subsystem-name 0059 698.SUBNAM698

program-system-name 0059 698.SYSNAM698

proposed-change-type-code 0261 alias for: engineering-drawing-document-

proposed-change-type-code

proposed-entry-change-type-code 0260 alias for: engineering-drawing-document-

proposed-entry-change-type-code

proprietary-data-rights-commercial- 0170 011.PRPCOM011, 900.PRPCOM900

enterprise-name

proprietary-data-rights-company-name 0170 alias for: proprietary-data-rights-

commercial-enterprise-name

proprietary-rights-code 0084 alias for: document-company-proprietary-

data-rights-code

proprietary-rights-text 0117 alias for: document-company-proprietary-

data-rights-text

rac-identifier 0003 alias for: rapid-action-change-order-

document-alphanumeric-identifier

rac-type-code 0256 alias for: rapid-action-change-order-

document-change-type-code

rapid-action-change-order-document- 0003 464.RACNUM464

alphanumeric-identifier

rapid-action-change-order-document- 0256 464.CHGTYP464

change-type-code

reference-designator 0055 alias for: place-reference-designator-

identifier

referenced-document-generic-revision 0243 alias for: referenced-document-generic-

revision-identifier

referenced-document-generic-revision- 0243 082.RDOCRV082, 110.RDOCRV110

identifier

replaced-part-product-identifier 0024 216.RPARNO216, 217.RPARNO217

replaced-part-product-design-enterprise- 0052 216.RENTID216, 217.RENTID217

identifier

D-67
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

replaced-product-national-stock-identifier 0049 346.OLDNSN346

replacement-nsn 0049 alias for: replacement-product-national-

stock-identifier

replacement-product-national-stock- 0049 346.NEWNSN346

identifier

document-identifier

revised-program--unique-specification- 0149 alias for: revised-program--unique-

identifier specification-document-identifier

revised-technical-manual-document- 0135 571.RTMIDN610, 610.RTMIDN610,

identifier 615.RTMIDN615

D-68
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

revised-tm-identifier 0135 alias for: revised-technical-manual-

document-identifier

revision-notice-document-alphanumeric- 0003 300.NORNUM300, 301.NORNUM300,

identifier 302.NORNUM300, 303.NORNUM300,
304.NORNUM300, 305.NORNUM300,
306.NORNUM300, 307.NORNUM300,
308.NORNUM300, 309.NORNUM300,
310.NORNUM300, 311.NORNUM300,
312.NORNUM300, 313.NORNUM300,
314.NORNUM300, 315.NORNUM300,
316.NORNUM300, 317.NORNUM300,
318.NORNUM300, 319.NORNUM300,
320.NORNUM300, 321.NORNUM300,
322.NORNUM300, 323.NORNUM300,
324.NORNUM300, 325.NORNUM300,
326.NORNUM300, 327.NORNUM300

revision-notice-document-alphanumeric- 0009 301.NORREV301, 302.NORREV301,

revision-identifier 303.NORREV301, 304.NORREV301,
305.NORREV301, 306.NORREV301,
307.NORREV301, 308.NORREV301,
309.NORREV301, 310.NORREV301,
311.NORREV301, 312.NORREV301,
313.NORREV301, 314.NORREV301,
315.NORREV301, 316.NORREV301,
317.NORREV301, 318.NORREV301,
319.NORREV301, 320.NORREV301,
321.NORREV301, 322.NORREV301,
323.NORREV301, 324.NORREV301,
325.NORREV301, 326.NORREV301,
327.NORREV301

revision-notice-document- 0176 309.IMPCOD309, 863.IMPCOD863

implementation-authorization-code

revision-notice-document-revision- 0021 309.NORSTA309, 310.NORSTA309,

approval-process-approved-disposition- 311.NORSTA309, 312.NORSTA309,
status-code 313.NORSTA309

revision-notice-document-revision- 0082 309.NORDAT309, 310.NORDAT309,

approval-process-approved-disposition- 311.NORDAT309, 312.NORDAT309,
status-date 313.NORDAT309

D-69
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

revision-notice-document-source- 0001 300.NORCAG300, 301.NORCAG300,

enterprise-defense-logistics--assigned- 302.NORCAG300, 303.NORCAG300,
identification-code 304.NORCAG300, 305.NORCAG300,
306.NORCAG300, 307.NORCAG300,
308.NORCAG300, 309.NORCAG300,
310.NORCAG300, 311.NORCAG300,
312.NORCAG300, 313.NORCAG300,
314.NORCAG300, 315.NORCAG300,
316.NORCAG300, 317.NORCAG300,
318.NORCAG300, 319.NORCAG300,
320.NORCAG300, 321.NORCAG300,
322.NORCAG300, 323.NORCAG300,
324.NORCAG300, 325.NORCAG300,
326.NORCAG300, 327.NORCAG300

revision-notice-document-type-code 0004 300.NORTYP300, 301.NORTYP300,

302.NORTYP300, 303.NORTYP300,
304.NORTYP300, 305.NORTYP300,
306.NORTYP300, 307.NORTYP300,
308.NORTYP300, 309.NORTYP300,
310.NORTYP300, 311.NORTYP300,
312.NORTYP300, 313.NORTYP300,
314.NORTYP300, 315.NORTYP300,
316.NORTYP300, 317.NORTYP300,
318.NORTYP300, 319.NORTYP300,
320.NORTYP300, 321.NORTYP300,
322.NORTYP300, 323.NORTYP300,
324.NORTYP300, 325.NORTYP300,
326.NORTYP300, 327.NORTYP300

rfd-alphanumeric-identifier 0003 alias for: deviation-request-document-

alphanumeric-identifier

rfd-cage-code 0001 alias for: deviation-request-document-

source-enterprise-defense-logistics--
assigned-identification-code

rfd-cost-rationale 0104 alias for: deviation-request-document-

price-adjustment-effect-rationale-text

rfd-document-type-code 0004 alias for: deviation-request-document-

type-code

rfd-implementation-action-disposition- 0021 alias for: deviation-implementation-

status-code process-action-disposition-status-code

rfd-implementation-action-disposition- 0082 alias for: deviation-implementation-

status-date process-action-disposition-status-date

D-70
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

rfd-implementation-action-identifier 0072 alias for: deviation-implementation-

process-action-identifier

rfd-implementation-action-item- 0185 alias for: deviation-implementation-

description process-action-item-description-text

rfd-implementation-action-responsible- 0052 alias for: deviation-implementation-

enterprise-identifier process-required-action-responsible-
enterprise-identifier

rfd-implementation-action-responsible- 0044 alias for: deviation-implementation-

office required-action-responsible-enterprise-
office-name

rfd-lowest-part-level-code 0220 alias for: deviation-request-document-part-

level-code

rfd-revision 0009 alias for: deviation-request-document-

alphanumeric-revision-identifier

schedule-a-affect-code 0198 alias for: contract-modification-document-

schedule-a-affect-code

schedule-b-affect-code 0198 alias for: contract-modification-document-

schedule-b-affect-code

schedule-c-affect-code 0198 alias for: contract-modification-document-

schedule-c-affect-code

schedule-d-affect-code 0198 alias for: contract-modification-document-

schedule-d-affect-code

schedule-e-affect-code 0198 alias for: contract-modification-document-

schedule-e-affect-code

schedule-f-affect-code 0198 alias for: contract-modification-document-

schedule-f-affect-code

schedule-g-affect-code 0198 alias for: contract-modification-document-

schedule-g-affect-code

schedule-h-affect-code 0198 alias for: contract-modification-document-

schedule-h-affect-code

schedule-i-affect-code 0198 alias for: contract-modification-document-

schedule-i-affect-code

schedule-j-affect-code 0198 alias for: contract-modification-document-

schedule-j-affect-code

schedule-k-affect-code 0198 alias for: contract-modification-document-

schedule-k-affect-code

D-71
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

scn-identifier 0193 alias for: program--unique-specification-

change-notice-document-sequential-
identifier

security-access-restriction-code 0085 alias for: document-security-access-

restriction-code

security-classification-code 0010 alias for: document-security-classification-

code

security-classification-name 0011 alias for: document-security-classification-

name

separate-parts-list-code 0025 alias for: separate-parts-list-document-

code

separate-parts-list-document-code 0025 051.SEPCOD051

service-acronym 0002 alias for: united-states-defense-

component-enterprise-acronym-
identification-code

sgml-activation-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
activation-effect-field-identifier

sgml-aircraft-weight-balance-stability- 0118 alias for: standard-generalized-markup-

effect-tag language-document-proposed-change-
aircraft-weight-balance-stability-effect-
field-identifier

sgml-alternate-solutions-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
alternate-solutions-field-identifier

sgml-change-description-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-long-
description-field-identifier

sgml-contract-maintenance-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
contract-maintenance-effect-field-identifier

sgml-contractor-field-service-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
contractor-field-service-effect-field-
identifier

D-72
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

sgml-critical-single-point-failure-item- 0118 alias for: standard-generalized-markup-

effect-tag language-document-proposed-change-
critical-single-point-failure-item-effect-
field-identifier

sgml-developmental-program- 0118 alias for: standard-generalized-markup-

requirements-tag language-document-proposed-change-
developmental-program-requirements-
field-identifier

sgml-deviation-request-corrective-action- 0118 alias for: standard-generalized-markup-

tag language-document-deviation-request-
corrective-action-taken-field-identifier

sgml-disapproval-consequences-tag 0118 alias for: standard-generalized-markup-

language-document-change-proposal-
disapproval-consequences-field-identifier

sgml-emi-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
electromagnetic-interference-effect-field-
identifier

sgml-facilities-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
facilities-effect-field-identifier

sgml-gfe-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
government-furnished-equipment-effect-
field-identifier

sgml-ils-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
logistics-support-effect-field-identifier

sgml-interim-support-program-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
interim-support-programs-effect-field-
identifier

sgml-interoperability-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
interoperability-effect-field-identifier

sgml-life-cycle-cost-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-life-
cycle-cost-effect-field-identifier

D-73
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

sgml-logistics-support-plan-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
logistics-support-plan-effect-field-identifier

sgml-maintainability-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
maintainability-effect-field-identifier

sgml-maintenance-concept-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
maintenance-concept-effect-field-identifier

sgml-maintenance-training-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
maintenance-training-effect-field-identifier

sgml-need-for-change-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-long-
need-rationale-field-identifier

sgml-nomenclature-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
nomenclature-effect-field-identifier

sgml-operating-procedure-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
operating-procedure-effect-field-identifier

sgml-operator-training-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
operator-training-effect-field-identifier

sgml-other-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
unusual-effect-description-field-identifier

sgml-other-software-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
other-software-effect-field-identifier

sgml-parts-control-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
parts-control-effect-field-identifier

sgml-performance-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
performance-effect-field-identifier

sgml-personnel-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
personnel-effect-field-identifier

D-74
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

sgml-phst-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
packaging-handling-storage-transport-
effect-field-identifier

sgml-recurring-rfd-corrective-action-tag 0118 alias for: standard-generalized-markup-

language-document-recurring-deviation-
request-corrective-action-taken-field-
identifier

sgml-reliability-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
reliability-effect-field-identifier

sgml-retrofit-recommendations-tag 0118 alias for: standard-generalized-markup-

language-document-retrofit-
recommendations-field-identifier

sgml-rework-other-equipment-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
rework-other-equipment-effect-field-
identifier

sgml-safety-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
safety-effect-field-identifier

sgml-service-life-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
service-life-effect-field-identifier

sgml-software-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
software-effect-field-identifier

sgml-spare-repair-part-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
spare-repair-parts-effect-field-identifier

sgml-specific-proposed-document- 0118 alias for: standard-generalized-markup-

changes-tag language-document-specific-proposed-
changes-field-identifier

sgml-support-equipment-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
support-equipment-effect-field-identifier

sgml-survivability-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
survivability-effect-field-identifier

D-75
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

sgml-system-test-procedure-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
system-test-procedure-effect-field-identifier

sgml-tag 0118 alias for: standard-generalized-markup-

language-document-field-identifier

sgml-technical-manual-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
technical-manual-effect-field-identifier

sgml-warranty-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
warranty-effect-field-identifier

sgml-weight-moment-inertia-effect-tag 0118 alias for: standard-generalized-markup-

language-document-proposed-change-
weight-moment-inertia-effect-field-
identifier

sheet-date 0082 alias for: document-revised-sheet-change-

incorporation-date

ship-asset-identifier 0031 260.RETSHP260

ship-identifier 0031 alias for: ship-asset-identifier

shipping-document-alphanumeric- 0003 953.SHPIDN960, 954.SHPIDN960,

identifier 960.SHPIDN960

shipping-document-dollar-amount 0146 960.SHPAMT960

shipping-document-process-disposition- 0021 960.SHPSTA960

status-code

shipping-document-requirement-code 0202 953.CDR070953

shipping-document-shipped-item-quantity 0148 960.SHPQTY960

shipping-document-shipped-item- 0147 960.SHPDES960

description-text

short-distribution-statement 0016 alias for: document-short-distribution-

statement-text

software-alphanumeric-identifier 0088 alias for: software-product-alphanumeric-

identifier

software-compiler-identifier 0031 alias for: computer-software-compiler-

asset-identifier

D-76
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

software-compiler-version 0064 alias for: computer-software-compiler-

asset-version-identifier

software-dash-identifier 0222 alias for: software-product-application-

suffix-alphanumeric-identifier

software-document-type-code 0004 163.SWTYPE163, 164.SWTYPE164,

165.SWTYP165, 166.SWTYPE166,
230.SWTYPE230, 231.SWTYPE230,
232.SWTYPE230, 233.SWTYPE230

software-generic-identifier 0060 alias for: software-product-generic-

identifier

software-link-identifier 0031 alias for: computer-software-link-asset-

identifier

software-link-version 0064 alias for: computer-software-link-asset-

version-identifier

software-product-identifier 0262 172.SWPIDN172, 187.SWIDEN170

software-product-alphanumeric-identifier 0088 157.SWNUMB157, 171.SWNUMB157

software-product-application-suffix- 0222 156.SWDASH156

alphanumeric-identifier

software-product-basic-application- 0190 155.SWROOT155, 156.SWROOT155

alphanumeric-identifier

software-product-generic-identifier 0060 170.SWIDEN170, 173.SWIDEN170,

194.SWIDEN170, 222.SWIDEN170,
236.SWIDEN170, 239.SWIDEN170,
245.SWIDEN170, 293.SWIDEN170,
321.SWIDEN170, 353.SWIDEN170,
364.SWIDEN170, 696.SWIDEN170,
900.SWIDEN170, 902.SWIDEN170,
903.SWIDEN170

software-product-identification-paradigm- 0163 150.SWPARA150, 170.SWPARA170

type-code

software-product-source-enterprise- 0050 152.SRCTYP152, 160.SRCTYP160,

identification-type-code 173.SRCTYP173

D-77
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

software-product-source-entity-identifier 0033 155.SWSORC155, 156.SWSORC155,

157.SWSORC155, 159.SWSORC159,
170.SWSORC170, 171.SWSORC171,
172.SWSORC172, 173.SWSORC170,
187.SWSORC170, 194.SWSORC170,
222.SWSORC170, 236.SWSORC170,
239.SWSORC170, 245.SWSORC170,
293.SWSORC170, 321.SWSORC170,
353.SWSORC170, 364.SWSORC170,
696.SWSORC170, 900.SWSORC170,
902.SWSORC170, 903.SWSORC170

software-product-storage-medium-type- 0238 194.MEDTYP194

name

software-product-united-states-air-force-- 0061 Part of data element string: software-

assigned-identifier product-united-states-air-force--assigned-
designation-identifier.

software-product-united-states-air-force-- 0236 Part of data element string: software-

assigned-applicability-code product-united-states-air-force--assigned-
identifier.

software-product-united-states-air-force-- 0183 Part of data element string: software-

assigned-applicable-system-identifier product-united-states-air-force--assigned-
identifier.

software-product-united-states-air-force-- 0179 Part of data element string: software-

assigned-category-code product-united-states-air-force--assigned-
identifier.

software-product-united-states-air-force-- 0237 190.CPINNO190, 191.CPINNO190,

assigned-designation-identifier 192.CPINNO190, 194.CPINNO190

software-product-united-states-air-force-- 0182 Part of data element string: software-

assigned-major-function-code product-united-states-air-force--assigned-
identifier.

software-product-united-states-air-force-- 0169 Part of data element string: software-

assigned-receiving-country-place-code product-united-states-air-force--assigned-
designation-identifier.

software-product-united-states-air-force-- 0177 Part of data element string: software-

assigned-revision-identifier product-united-states-air-force--assigned-
designation-identifier.

software-product-united-states-air-force-- 0221 Part of data element string: software-

assigned-sequence-identifier product-united-states-air-force--assigned-
identifier.

D-78
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

software-product-united-states-air-force-- 0188 Part of data element string: software-

assigned-type-code product-united-states-air-force--assigned-
identifier.

software-product-united-states-air-force-- 0189 Part of data element string: software-

assigned-version-identifier product-united-states-air-force--assigned-
identifier.

software-product-version-identifier 0062 154.SWVERS154, 159.SWVERS159,

164.SWVERS164, 166.SWVERS154

software-root-identifier 0190 alias for: software-product-basic-

application-alphanumeric-identifier

software-source-enterprise-type-code 0050 alias for: software-product-source-

enterprise-identification-type-code

software-source-identifier 0033 alias for: software-product-source-entity-

identifier

software-support-document- 0122 186.SSDIDN186, 187.SSDIDN186

alphanumeric-identifier

software-support-document-generic- 0243 alias for: software-support-document-

revision generic-revision-identifier

software-support-document-generic- 0243 186.SSDREV186, 187.SSDREV186

revision-identifier

software-support-document-identifier 0122 alias for: software-support-document-

alphanumeric-identifier

software-support-document-source-entity- 0033 185.SSDSRC185, 186.SSDSRC185,

identifier 187.SSDSRC185

software-support-document-sub-type-code 0107 alias for: software-support-document-

subsidiary-type-code

software-support-document-subsidiary- 0107 185.SDOCSB185

type-code

software-support-document-type-code 0004 186.SSDTYP186, 187.SSDTYP186

software-version 0062 alias for: software-product-version-

identifier

software-version-description-document- 0003 170.SVDNUM180, 180.SVDNUM180

alphanumeric-identifier

software-version-description-document- 0004 170.SVDTYP180, 180.SVDTYP180

type-code

D-79
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

sow-affect-code 0198 alias for: contract-modification-document-

work-statement-affect-code

sow-identifier 0229 alias for: work-statement-document-

identifier

specification-category-code 0105 alias for: specification-document-category-

code

specification-document-category-code 0105 101.SPCCAT101

specification-revision 0009 alias for: program--unique-specification-

document-alphanumeric-revision-identifier

specification-sub-type-code 0108 alias for: program--unique-specification-

document-subsidiary-type-code

standard-generalized-markup-language- 0118 251.SGM20A251

document-change-proposal-disapproval-
consequences-field-identifier

standard-generalized-markup-language- 0118 351.SGM024351

document-deviation-request-corrective-
action-taken-field-identifier

standard-generalized-markup-language- 0118 (Basic Standard Data Element--see

document-field-identifier applicable role name.)

standard-generalized-markup-language- 0118 289.SGM39H289

document-proposed-change-activation-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM37B289

document-proposed-change-aircraft-
weight-balance-stability-effect-field-
identifier

standard-generalized-markup-language- 0118 289.SGM341289

document-proposed-change-alternate-
solutions-field-identifier

standard-generalized-markup-language- 0118 289.SGM38M289

document-proposed-change-contract-
maintenance-effect-field-identifier

standard-generalized-markup-language- 0118 290.SGM470290

document-proposed-change-contractor-
field-service-effect-field-identifier

D-80
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

standard-generalized-markup-language- 0118 289.SGM39I289

document-proposed-change-critical-
single-point-failure-item-effect-field-
identifier

standard-generalized-markup-language- 0118 289.SGM342289

document-proposed-change-
developmental-program-requirements-
field-identifier

standard-generalized-markup-language- 0118 289.SGM39G289

document-proposed-change-
electromagnetic-interference-effect-field-
identifier

standard-generalized-markup-language- 0118 289.SGM38G289

document-proposed-change-facilities-
effect-field-identifier

standard-generalized-markup-language- 0118 (Basic Standard Data Element--see

document-proposed-change-government- applicable role name.)
furnished-equipment-effect-field-
identifier

standard-generalized-markup-language- 0118 289.SGM38D289

document-proposed-change-interim-
support-programs-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM39J289

document-proposed-change-
interoperability-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM40I289

document-proposed-change-life-cycle-
cost-effect-field-identifier

standard-generalized-markup-language- 0118 351.SGM021351

document-proposed-change-logistics-
support-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38A289

document-proposed-change-logistics-
support-plan-effect-field-identifier

standard-generalized-markup-language- 0118 251.SGM190251, 351.SGM022351

document-proposed-change-long-
description-field-identifier

D-81
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

standard-generalized-markup-language- 0118 251.SGM200251, 351.SGM023351

document-proposed-change-long-need-
rationale-field-identifier

standard-generalized-markup-language- 0118 289.SGM39D289

document-proposed-change-
maintainability-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38B289

document-proposed-change-maintenance-
concept-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38K289

document-proposed-change-maintenance-
training-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM37E289

document-proposed-change-
nomenclature-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM39F289

document-proposed-change-operating-
procedure-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38I289

document-proposed-change-operator-
training-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM40D289

document-proposed-change-other-
software-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38N289

document-proposed-change-packaging-
handling-storage-transport-effect-field-
identifier

standard-generalized-markup-language- 0118 289.SGM40H289

document-proposed-change-parts-control-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM37A289

document-proposed-change-performance-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38J289

document-proposed-change-personnel-
effect-field-identifier

D-82
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

standard-generalized-markup-language- 0118 289.SGM39C289

document-proposed-change-reliability-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM40E289

document-proposed-change-rework-other-
equipment-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM39A289

document-proposed-change-safety-effect-
field-identifier

standard-generalized-markup-language- 0118 289.SGM39E289

document-proposed-change-service-life-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM32E289

document-proposed-change-software-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38E289

document-proposed-change-spare-repair-
parts-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38H289

document-proposed-change-support-
equipment-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM39B289

document-proposed-change-survivability-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM40F289

document-proposed-change-system-test-
procedure-effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM38F289

document-proposed-change-technical-
manual-effect-field-identifier

standard-generalized-markup-language- 0118 265.SGMUNU265

document-proposed-change-unusual-
effect-description-field-identifier

standard-generalized-markup-language- 0118 289.SGM40G289

document-proposed-change-warranty-
effect-field-identifier

standard-generalized-markup-language- 0118 289.SGM37C289

document-proposed-change-weight-
moment-inertia-effect-field-identifier

D-83
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

standard-generalized-markup-language- 0118 359.SGMRAT359

document-recurring-deviation-request-
corrective-action-taken-field-identifier

standard-generalized-markup-language- 0118 290.SGM430290

document-retrofit-recommendations-
field-identifier

standard-generalized-markup-language- 0118 266.SGM330266, 301.SGMCHG301,

document-specific-proposed-changes- 352.SGM22A352
field-identifier

standardization-document-series-type- 0242 404.SERIES404, 405.SERIES405,

code 406.SERIES406, 407.SERIES407,
408.SERIES408, 409.SERIES409

starting-effectivity-tracking-identifier 0058 alias for: product-starting-effectivity-

sequential-tracking-identifier

state 0040 alias for: state-place-code

state-place-code 0040 Part of data element string: enterprise-

address-text.

substitute-material-enterprise-identifier 0052 alias for: substitute-material-product-

design-enterprise-identifier

substitute-material-generic-identifier 0092 alias for: substitute-material-product-

generic-identifier

substitute-material-identification 0038 alias for: substitute-material-product-

identifier

substitute-material-product-identifier 0038 206.SMMTID206, 217.SMMTID217

substitute-material-product-design- 0052 206.SMENID206, 217.SENTID217

enterprise-identifier

substitute-material-product-generic- 0092 206.SMGNID206, 217.SMGNID217

identifier

substitute-part-enterprise-identifier 0052 alias for: substitute-part-product-design-

enterprise-identifier

substitute-part-identifier 0024 alias for: substitute-part-product-identifier

substitute-part-product-identifier 0024 207.SPARNO207, 216.SPARNO216

substitute-part-product-design-enterprise- 0052 207.SPENID207, 216.SENTID216

identifier

subsystem-name 0059 alias for: program-subsystem-name

D-84
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

supplement-document-sequential- 0244 (Basic Standard Data Element--see

identifier applicable role name.)

supplement-document-type-code 0162 601.SUPTYP601

supplemental-document-type-code 0004 620.DSUPTY620

supply-item-control-shelf-life-code 0094 200.SHLFCD200, 210.SHLFCD210

support-equipment-ci-identifier 0111 alias for: support-equipment-

configuration-item-product-identifier

SVD 0004 alias for: software-version-description-

document-type-code

support-equipment-configuration-item- 0111 694.SCIIDN694

product-identifier

svd-identifier 0003 alias for: software-version-description-

document-alphanumeric-identifier

SW 0004 alias for: software-document-type-code

sw-paradigm-code 0163 alias for: software-product-identification-

paradigm-type-code

SWDOC 0004 alias for: software-support-document-type-

code

system-name 0059 alias for: program-system-name

tasking-activity-enterprise-technical- 0228 953.CDR060953, 954.TSKTEK954

monitor-division-identifier

tcto-maintenance-level-code 0255 alias for: limited-duration-technical-order-

document-maintenance-level-code

tcto-priority-code 0248 alias for: limited-duration-technical-order-

document-priority-code

td-category-code 0247 alias for: technical-directive-document-

category-code

td-maintenance-level-code 0254 alias for: technical-directive-document-

maintenance-level-code

td-task-type-code 0249 alias for: technical-directive-document-

task-type-code

technical-data-rights-code 0022 alias for: technical-document-government-

data-rights-code

D-85
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

technical-data-rights-text 0083 alias for: technical-document-government-

data-rights-text

technical-directive-document-category- 0247 465.CATCOD465

code

technical-directive-document- 0254 465.LVLCOD465

maintenance-level-code

technical-directive-document-task-type- 0249 465.TSKTYP465

code

technical-directive-identifier 0003 alias for: united-states-naval-air-technical-

directive-document-alphanumeric-
identifier

technical-disposition-recommendation 0021 alias for: document-approval-process-

technical-recommended-disposition-status-
code

technical-document-government-data- 0022 011.RGTCOD016, 016.RGTCOD016,

rights-code 900.RGTCOD016

technical-document-government-data- 0083 016.RGTTXT016

rights-text

technical-document-government-data- 0082 011.RGTEXP011, 900.RGTEXP900

rights-expiration-date

technical-manual-change-document- 0134 571.CHGNUM610, 610.CHGNUM610,

identifier 615.CHGNUM610

technical-manual-document- 0003 Part of data element string: revised-

alphanumeric-identifier technical-manual-document-identifier.

technical-manual-document-iteration- 0196 554.ITTYPE554

type-code

technical-manual-document-revision- 0082 565.ISSDAT570, 570.ISSDAT570

issue-date

technical-manual-document-supplement- 0082 572.SETDAT572, 573.SETDAT572

set-effective-date

D-86
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

technical-manual-document-type-code 0004 262.TMNTYP550, 291.TMNTYP550,

461.TMNTYP550, 464.TMNTYP550,
468.TMNTYP550, 550.TMNTYP550,
551.TMNTYP550, 552.TMNTYP550,
553.TMNTYP550, 554.TMNTYP550,
556.TMNTYP550, 557.TMNTYP550,
560.TMNTYP550, 565.TMNTYP550,
570.TMNTYP550, 571.TMNTYP550,
572.TMNTYP550, 573.TMNTYP550,
610.TMNTYP550, 611.TMNTYP550,
612.TMNTYP550, 613.TMNTYP550,
614.TMNTYP550, 615.TMNTYP550,
616.TMNTYP550, 617.TMNTYP550,
618.TMNTYP550, 619.TMNTYP550

technical-manual-operational- 0082 612.OISSDT612

supplement-document-issue-date

technical-manual-operational- 0244 572.OSIDEN612, 612.OSIDEN612,

supplement-document-sequential- 617.OSIDEN612
identifier

technical-manual-page-supplement- 0244 573.TOPIDN614, 614.TOPIDN614,

document-sequential-identifier 619.TOPIDN614

technical-manual-routine-supplement- 0082 613.RISSDT613

document-issue-date

technical-manual-routine-supplement- 0244 572.RSIDEN613, 613.RSIDEN613,

document-sequential-identifier 618.RSIDEN613

technical-manual-safety-supplement- 0082 611.SISSDT611

document-issue-date

technical-manual-safety-supplement- 0244 572.SSIDEN611, 611.SSIDEN611,

document-sequential-identifier 616.SSIDEN611

technical-manual-supplement-document- 0082 614.TOPISS614

issue-date

technical-recommendation-disposition- 0082 alias for: disposition-process-technical-

date recommendation-completion-date

telephone-number 0225 alias for: human-telephone-access-

identifier

time 0160 alias for: {}-time; Generic Data

Element--see applicable Standard Data
Element role name.

time-unit 0232 alias for: period-unit-code

to-page-supplement-identifier 0244 alias for: technical-manual-page-

supplement-document-sequential-identifier

unit-of-measure 0054 alias for: product-measurement-unit-code

united-states-air-force-technical-order- 0003 560.AFTONO560

document-alphanumeric-identifier

united-states-army-modification-work- 0003 467.MWONUM467, 468.MWONUM467

order-document-alphanumeric-identifier

united-states-army-technical-manual- 0003 468.ATMNUM557, 557.ATMNUM557

document-alphanumeric-identifier

D-88
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

united-states-defense-component- 0002 552.SERVID552

enterprise-acronym-identification-code

united-states-defense-department- 0002 262.SRCDOD552, 291.SRCDOD552,

document-source-enterprise-acronym- 408.SRCDOD408, 462.SRCDOD462,
identification-code 464.SRCDOD462, 465.SRCDOD462,
466.SRCDOD462, 467.SRCDOD462,
468.SRCDOD468, 469.SRCDOD462,
470.SRCDOD462, 471.SRCDOD462,
472.SRCDOD462, 552.SRCDOD552,
554.SRCDOD552, 557.SRCDOD552,
558.SRCDOD552, 559.SRCDOD552,
560.SRCDOD560, 562.SRCDOD552,
563.SRCDOD552, 565.SRCDOD552,
570.SRCDOD552, 571.SRCDOD552,
572.SRCDOD552, 573.SRCDOD552,
610.SRCDOD552, 611.SRCDOD552,
612.SRCDOD552, 613.SRCDOD552,
614.SRCDOD552, 615.SRCDOD552,
616.SRCDOD552, 617.SRCDOD552,
618.SRCDOD552, 619.SRCDOD552

united-states-defense-department- 0002 007.DODORG034, 034.DODORG034

enterprise-acronym-identification-code

united-states-defense-department- 0097 034.DODTYP034

organization-type-identifier

united-states-defense-handbook- 0003 413.HBKNUM413

document-alphanumeric-identifier

united-states-defense-secretariate- 0002 410.SRCOSD410, 411.SRCOSD410,

document-source-enterprise-acronym- 412.SRCOSD410, 413.SRCOSD410
identification-code

united-states-defense-specification- 0003 412.SPCNUM412

document-alphanumeric-identifier

united-states-defense-standard-document- 0003 411.STDNUM411

alphanumeric-identifier

united-states-government-nondefense- 0002 409.SRCGOV409

document-source-enterprise-acronym-
identification-code

united-states-government-nondefense- 0002 035.GOVORG035

enterprise-acronym-identification-code

D-89
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

united-states-naval-air-technical- 0003 465.TDIRNO465

directive-document-alphanumeric-
identifier

united-states-navy-command-enterprise- 0002 559.NAVCOM559

acronym-identification-code

united-states-nongovernment-document- 0002 407.SRCIND407

source-enterprise-acronym-identification-
code

united-states-nongovernment-enterprise- 0002 036.INDORG036

acronym-identification-code

us-defense-secretariate-document-source- 0002 alias for: united-states-defense-

organization-code secretariate-document-source-enterprise-
acronym-identification-code

us-dod-document-source-organization- 0002 alias for: united-states-defense-

code department-document-source-enterprise-
acronym-identification-code

us-dod-organization-code 0002 alias for: united-states-defense-

department-enterprise-acronym-
identification-code

us-government-nondefense-organization- 0002 alias for: united-states-government-

code nondefense-document-source-enterprise-
acronym-identification-code

us-government-organization-code 0002 alias for: united-states-government-

nondefense-enterprise-acronym-
identification-code

us-nongovernment-document-source- 0002 alias for: united-states-nongovernment-

organization-code document-source-enterprise-acronym-
identification-code

us-nongovernment-organization-code 0002 alias for: united-states-nongovernment-

enterprise-acronym-identification-code

vehicle-asset-identifier 0031 260.RETVEH260

vehicle-identifier 0031 alias for: vehicle-asset-identifier

vendor--assigned-material-identifier 0048 alias for: material-product-vendor--

assigned-identifier

vendor--assigned-part-identifier 0024 alias for: part-product-vendor--assigned-

identifier

D-90
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

DED Title or Nickname/Alias DED No. Table.Field, or

DED Title

work-statement-document-identifier 0229 680.SOWIDN957, 953.SOWIDN957,

957.SOWIDN957

year 0219 alias for: julian-year-period-identifier

D.5.1.1. The data element design-enterprise-identifier is used in the following locations:

055.DESENT200, 056.DESENT210, 083.DESENT200, 084.DESENT210, 086.DESENT200,

087.DESENT210, 111.DESENT210, 200.DESENT200, 210.DESENT210, 220.DESENT210,
221.DESENT200, 230.DESENT210, 231.DESENT210, 232.DESENT210, 234.DESENT210,
235.DESENT200, 237.DESENT210, 238.DESENT200, 240.DESENT210, 241.DESENT200,
245.DESENT210, 256.DESENT210, 284.DESENT200, 319.DESENT210, 320.DESENT200,
360.DESENT210, 361.DESENT210, 362.DESENT210, 363.DESENT200, 365.DESENT200,
366.DESENT200, 491.DESENT210, 492.DESENT210, 494.DESENT200, 521.DESENT210,
522.DESENT210, 523.DESENT210, 524.DESENT210, 525.DESENT210, 526.DESENT200,
527.DESENT200, 528.DESENT200, 529.DESENT210, 530.DESENT200, 928.DESENT200,
929.DESENT210.

D.5.1.2. The data element design-enterprise-defense-logistics--assigned-identification-code is used in the following

locations:

050.DESCAG050, 051.DESCAG050, 052.DESCAG050, 053.DESCAG053, 054.DESCAG054,

055.DESCAG054, 056.DESCAG054, 060.DESCAG050, 061.DESCAG050, 062.DESCAG050,
063.DESCAG050, 064.DESCAG050, 065.DESCAG050, 066.DESCAG050, 069.DESCAG050,
070.DESCAG050, 071.DESCAG050, 080.DESCAG050, 081.DESCAG050, 082.DESCAG050,
083.DESCAG050, 084.DESCAG050, 085.DESCAG050, 086.DESCAG050, 087.DESCAG050,
100.DESCAG100, 101.DESCAG100, 102.DESCAG100, 103.DESCAG100, 104.DESCAG104,
105.DESCAG105, 106.DESCAG106, 107.DESCAG107, 110.DESCAG100, 111.DESCAG100,
153.DESCAG153, 161.DESCAG161, 163.DESCAG163, 164.DESCAG164, 174.DESCAG164,
205.DESCAG205, 208.DESCAG050, 212.DESCAG212, 219.DESCAG050, 220.DESCAG050,
221.DESCAG050, 222.DESCAG050, 223.DESCAG050, 224.DESCAG050, 225.DESCAG225,
226.DESCAG050, 227.DESCAG050, 234.DESCAG053, 235.DESCAG053, 237.DESCAG053,
238.DESCAG053, 256.DESCAG256, 258.DESCAG258, 270.DESCAG153, 284.DESCAG284,
285.DESCAG050, 286.DESCAG050, 287.DESCAG100, 302.DESCAG050, 304.DESCAG100,
306.DESCAG050, 307.DESCAG050, 311.DESCAG050, 312.DESCAG050, 313.DESCAG100,
315.DESCAG050, 316.DESCAG050, 317.DESCAG050, 318.DESCAG050, 319.DESCAG050,
320.DESCAG050, 321.DESCAG050, 323.DESCAG050, 324.DESCAG050, 325.DESCAG050,
326.DESCAG050, 327.DESCAG050, 362.DESCAG053, 363.DESCAG053, 432.DESCAG432,
433.DESCAG433, 434.DESCAG434, 435.DESCAG434, 436.DESCAG436, 437.DESCAG436,
508.DESCAG100, 509.DESCAG100, 510.DESCAG050, 511.DESCAG050, 620.DESCAG100.

D.5.1.3. The data element document-identifier is used in the following locations:

010.DOCIDN010, 011.DOCIDN010, 019.DOCIDN010, 033.DOCIDN010, 071.DOCIDN010,

082.DOCIDN010, 085.DOCIDN010, 110.DOCIDN010, 150.DOCIDN010, 151.DOCIDN010,
158.DOCIDN010, 159.DOCIDN010, 185.DOCIDN010, 223.DOCIDN010, 253.DOCIDN010,
266.DOCIDN010, 271.DOCIDN010, 322.DOCIDN010, 330.DOCIDN010, 332.DOCIDN010,

D-91
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

352.DOCIDN010, 357.DOCIDN010, 450.DOCIDN010, 451.DOCIDN010, 452.DOCIDN010,

453.DOCIDN010, 454.DOCIDN010, 461.DOCIDN010, 550.DOCIDN010, 551.DOCIDN010,
553.DOCIDN010, 555.DOCIDN010, 601.DOCIDN010, 681.DOCIDN010, 800.DOCIDN010,
801.DOCIDN010, 802.DOCIDN010, 803.DOCIDN010, 804.DOCIDN010, 805.DOCIDN010,
806.DOCIDN010, 807.DOCIDN010, 811.DOCIDN010, 812.DOCIDN010, 850.DOCIDN010,
851.DOCIDN010, 852.DOCIDN010, 853.DOCIDN010, 854.DOCIDN010, 855.DOCIDN010,
857.DOCIDN010, 858.DOCIDN010, 861.DOCIDN010, 862.DOCIDN010, 863.DOCIDN010,
864.DOCIDN010, 865.DOCIDN010, 866.DOCIDN010, 867.DOCIDN010, 910.DOCIDN010,
911.DOCIDN010, 913.DOCIDN010, 914.DOCIDN010, 915.DOCIDN010, 917.DOCIDN010,
919.DOCIDN919, 926.DOCIDN010, 965.DOCIDN010, 966.DOCIDN010, 967.DOCIDN010,
968.DOCIDN010.

D.5.1.4. The data element document-alphanumeric-identifier is used in the following locations:

020.DOCNUM020, 021.DOCNUM020, 022.DOCNUM020, 023.DOCNUM020, 024.DOCNUM020,

025.DOCNUM020, 026.DOCNUM020, 027.DOCNUM020, 100.DOCNUM020, 101.DOCNUM020,
102.DOCNUM020, 104.DOCNUM020, 105.DOCNUM020, 107.DOCNUM020, 110.DOCNUM020,
111.DOCNUM020, 152.DOCNUM020, 153.DOCNUM020, 154.DOCNUM020, 208.DOCNUM020,
211.DOCNUM020, 219.DOCNUM020, 256.DOCNUM256, 258.DOCNUM258, 262.DOCNUM552,
270.DOCNUM020, 284.DOCNUM284, 287.DOCNUM020, 288.DOCNUM020, 291.DOCNUM552,
293.DOCNUM293, 304.DOCNUM020, 305.DOCNUM020, 310.DOCNUM020, 313.DOCNUM020,
400.DOCNUM020, 401.DOCNUM020, 402.DOCNUM020, 403.DOCNUM020, 404.DOCNUM020,
405.DOCNUM020, 406.DOCNUM020, 407.DOCNUM020, 408.DOCNUM020, 409.DOCNUM020,
410.DOCNUM020, 420.DOCNUM020, 422.DOCNUM020, 423.DOCNUM020, 430.DOCNUM020,
431.DOCNUM020, 432.DOCNUM020, 435.DOCNUM020, 436.DOCNUM020, 437.DOCNUM020,
440.DOCNUM020, 441.DOCNUM020, 464.DOCNUM020, 508.DOCNUM020, 509.DOCNUM020,
552.DOCNUM552, 554.DOCNUM552, 558.DOCNUM020, 559.DOCNUM020, 562.DOCNUM020,
563.DOCNUM020, 565.DOCNUM020, 570.DOCNUM552, 704.DOCNUM020.

D.5.1.5. The data element document-generic-revision-identifier is used in the following locations:

011.DOCREV011, 019.DOCREV011, 021.DOCREV011, 023.DOCREV011, 025.DOCREV011,

027.DOCREV011, 041.DOCREV011, 043.DOCREV011, 045.DOCREV011, 047.DOCREV011,
049.DOCREV011, 151.DOCREV011, 152.DOCREV011, 153.DOCREV011, 256.DOCREV011,
270.DOCREV011, 271.DOCREV011, 284.DOCREV011, 288.DOCREV011, 293.DOCREV011,
305.DOCREV011, 310.DOCREV011, 332.DOCREV011, 352.DOCREV011, 401.DOCREV011,
403.DOCREV011, 422.DOCREV011, 423.DOCREV011, 431.DOCREV011, 435.DOCREV011,
437.DOCREV011, 441.DOCREV011, 551.DOCREV011, 554.DOCREV011, 555.DOCREV011,
601.DOCREV011, 651.DOCREV011, 681.DOCREV011, 704.DOCREV011, 801.DOCREV011,
806.DOCREV011, 807.DOCREV011, 850.DOCREV011, 851.DOCREV011, 852.DOCREV011,
853.DOCREV011, 854.DOCREV011, 855.DOCREV011, 857.DOCREV011, 858.DOCREV011,
861.DOCREV011, 862.DOCREV011, 863.DOCREV011, 864.DOCREV011, 865.DOCREV011,
866.DOCREV011, 867.DOCREV011, 911.DOCREV011, 926.DOCREV011, 965.DOCREV011,
967.DOCREV011.

D.5.1.6. The data element document-source-entity-identifier is used in the following locations:

010.SRCIDN010, 011.SRCIDN010, 019.SRCIDN010, 033.SRCIDN010, 040.SRCIDN010, 041.SRCIDN010,

071.SRCIDN010, 082.SRCIDN010, 085.SRCIDN010, 110.SRCIDN010, 150.SRCIDN010, 151.SRCIDN010,
152.SRCIDN010, 158.SRCIDN010, 160.SRCIDN010, 180.SRCIDN010, 223.SRCIDN010, 253.SRCIDN010,
266.SRCIDN010, 271.SRCIDN010, 322.SRCIDN010, 330.SRCIDN010, 332.SRCIDN010, 352.SRCIDN010,

D-92
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

357.SRCIDN010, 450.SRCIDN010, 451.SRCIDN010, 452.SRCIDN010, 453.SRCIDN010, 454.SRCIDN010,

461.SRCIDN010, 550.SRCIDN010, 551.SRCIDN010, 553.SRCIDN010, 555.SRCIDN010, 601.SRCIDN010,
681.SRCIDN010, 800.SRCIDN010, 801.SRCIDN010, 802.SRCIDN010, 803.SRCIDN010, 804.SRCIDN010,
805.SRCIDN010, 806.SRCIDN010, 807.SRCIDN010, 811.SRCIDN010, 812.SRCIDN010, 850.SRCIDN010,
851.SRCIDN010, 852.SRCIDN010, 853.SRCIDN010, 854.SRCIDN010, 855.SRCIDN010, 857.SRCIDN010,
858.SRCIDN010, 861.SRCIDN010, 862.SRCIDN010, 863.SRCIDN010, 864.SRCIDN010, 865.SRCIDN010,
866.SRCIDN010, 867.SRCIDN010, 965.SRCIDN010, 966.SRCIDN010, 967.SRCIDN010, 968.SRCIDN010.

D.5.1.7. The data element document-type-code is used in the following locations:

010.DOCTYP010, 011.DOCTYP010, 019.DOCTYP010, 020.DOCTYP010, 021.DOCTYP010,

022.DOCTYP010, 023.DOCTYP010, 024.DOCTYP010, 025.DOCTYP010, 026.DOCTYP010,
027.DOCTYP010, 033.DOCTYP010, 040.DOCTYP010, 041.DOCTYP010, 042.DOCTYP010,
043.DOCTYP010, 044.DOCTYP010, 045.DOCTYP010, 046.DOCTYP010, 047.DOCTYP010,
048.DOCTYP010, 049.DOCTYP010, 050.DOCTYP010, 051.DOCTYP010, 052.DOCTYP010,
053.DOCTYP010, 054.DOCTYP010, 060.DOCTYP010, 061.DOCTYP010, 063.DOCTYP010,
080.DOCTYP010, 081.DOCTYP010, 083.DOCTYP010, 084.DOCTYP010, 086.DOCTYP010,
087.DOCTYP010, 100.DOCTYP010, 101.DOCTYP010, 102.DOCTYP010, 104.DOCTYP010,
105.DOCTYP010, 107.DOCTYP010, 111.DOCTYP010, 150.DOCTYP010, 151.DOCTYP010,
152.DOCTYP010, 153.DOCTYP010, 154.DOCTYP010, 157.DOCTYP010, 158.DOCTYP010,
159.DOCTYP010, 160.DOCTYP010, 161.DOCTYP010, 162.DOCTYP010, 171.DOCTYP010,
172.DOCTYP010, 185.DOCTYP010, 211.DOCTYP010, 212.DOCTYP212, 219.DOCTYP010,
223.DOCTYP010, 224.DOCTYP010, 226.DOCTYP010, 253.DOCTYP010, 256.DOCTYP010,
258.DOCTYP010, 266.DOCTYP010, 270.DOCTYP010, 271.DOCTYP010, 284.DOCTYP010,
287.DOCTYP010, 288.DOCTYP010, 293.DOCTYP010, 302.DOCTYP010, 304.DOCTYP010,
305.DOCTYP010, 306.DOCTYP010, 307.DOCTYP010, 310.DOCTYP010, 313.DOCTYP010,
322.DOCTYP010, 330.DOCTYP010, 332.DOCTYP010, 352.DOCTYP010, 357.DOCTYP010,
400.DOCTYP010, 401.DOCTYP010, 402.DOCTYP010, 403.DOCTYP010, 404.DOCTYP010,
405.DOCTYP010, 406.DOCTYP010, 407.DOCTYP010, 408.DOCTYP010, 409.DOCTYP010,
410.DOCTYP010, 411.DOCTYP010, 412.DOCTYP010, 413.DOCTYP010, 420.DOCTYP010,
422.DOCTYP010, 423.DOCTYP010, 430.DOCTYP010, 431.DOCTYP010, 432.DOCTYP010,
435.DOCTYP010, 436.DOCTYP010, 437.DOCTYP010, 440.DOCTYP010, 441.DOCTYP010,
508.DOCTYP010, 509.DOCTYP010, 510.DOCTYP010, 511.DOCTYP010, 555.DOCTYP010,
556.DOCTYP010, 558.DOCTYP010, 559.DOCTYP010, 562.DOCTYP010, 563.DOCTYP010,
572.DOCTYP010, 573.DOCTYP010, 601.DOCTYP010, 610.DOCTYP010, 611.DOCTYP010,
612.DOCTYP010, 613.DOCTYP010, 614.DOCTYP010, 615.DOCTYP010, 616.DOCTYP010,
617.DOCTYP010, 618.DOCTYP010, 619.DOCTYP010, 670.DOCTYP670, 681.DOCTYP010,
704.DOCTYP010, 800.DOCTYP010, 801.DOCTYP010, 802.DOCTYP010, 803.DOCTYP010,
804.DOCTYP010, 805.DOCTYP010, 806.DOCTYP010, 807.DOCTYP010, 811.DOCTYP010,
812.DOCTYP010, 850.DOCTYP010, 851.DOCTYP010, 852.DOCTYP010, 853.DOCTYP010,
854.DOCTYP010, 855.DOCTYP010, 857.DOCTYP010, 858.DOCTYP010, 861.DOCTYP010,
862.DOCTYP010, 863.DOCTYP010, 864.DOCTYP010, 865.DOCTYP010, 866.DOCTYP010,
867.DOCTYP010, 910.DOCTYP010, 911.DOCTYP010, 912.DOCTYP010, 913.DOCTYP010,
914.DOCTYP010, 915.DOCTYP010, 917.DOCTYP010, 919.DOCTYP010, 926.DOCTYP010,
965.DOCTYP010, 966.DOCTYP010, 967.DOCTYP010, 968.DOCTYP010.

D.5.1.8. The data element engineering-change-proposal-document-alphanumeric-identifier is used in the following

locations:

250.ECPNUM250, 251.ECPNUM250, 252.ECPNUM250, 253.ECPNUM250, 254.ECPNUM250,

255.ECPNUM250, 256.ECPNUM250, 257.ECPNUM250, 258.ECPNUM250, 259.ECPNUM250,

D-93
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

260.ECPNUM250, 261.ECPNUM250, 262.ECPNUM250, 263.ECPNUM250, 264.ECPNUM250,

265.ECPNUM250, 266.ECPNUM250, 270.ECPNUM250, 271.ECPNUM250, 284.ECPNUM250,
285.ECPNUM250, 286.ECPNUM250, 287.ECPNUM250, 288.ECPNUM250, 289.ECPNUM250,
290.ECPNUM250, 291.ECPNUM250, 292.ECPNUM250, 293.ECPNUM250, 294.ECPNUM250,
295.ECPNUM250, 300.ECPNUM250, 303.ECPNUM250, 309.ECPNUM250, 310.ECPNUM250,
311.ECPNUM250, 312.ECPNUM250, 313.ECPNUM250, 359.ECPNUM250, 454.ECPNUM250,
493.ECPNUM250, 565.ECPNUM250, 615.ECPNUM250, 616.ECPNUM250, 617.ECPNUM250,
618.ECPNUM250, 619.ECPNUM250, 620.ECPNUM250, 671.ECPNUM250, 682.ECPNUM250,
705.ECPNUM250.

D.5.1.9. The data element engineering-change-proposal-document-source-enterprise-defense-logistics--assigned-

identification-code is used in the following locations:

250.ECPCAG250, 251.ECPCAG250, 252.ECPCAG250, 253.ECPCAG250, 254.ECPCAG250,

255.ECPCAG250, 256.ECPCAG250, 257.ECPCAG250, 258.ECPCAG250, 259.ECPCAG250,
260.ECPCAG250, 261.ECPCAG250, 262.ECPCAG250, 263.ECPCAG250, 264.ECPCAG250,
265.ECPCAG250, 266.ECPCAG250, 270.ECPCAG250, 271.ECPCAG250, 284.ECPCAG250,
285.ECPCAG250, 286.ECPCAG250, 287.ECPCAG250, 288.ECPCAG250, 289.ECPCAG250,
290.ECPCAG250, 291.ECPCAG250, 292.ECPCAG250, 293.ECPCAG250, 294.ECPCAG250,
295.ECPCAG250, 300.ECPCAG250, 303.ECPCAG250, 309.ECPCAG250, 310.ECPCAG250,
311.ECPCAG250, 312.ECPCAG250, 313.ECPCAG250, 359.ECPCAG250, 454.ECPCAG250,
493.ECPCAG250, 565.ECPCAG250, 615.ECPCAG250, 616.ECPCAG250, 617.ECPCAG250,
618.ECPCAG250, 619.ECPCAG250, 620.ECPCAG250, 671.ECPCAG250, 682.ECPCAG250,
705.ECPCAG250.

D.5.1.10. The data element engineering-change-proposal-document-type-code is used in the following locations:

250.ECPTYP250, 251.ECPTYP250, 252.ECPTYP250, 253.ECPTYP250, 254.ECPTYP250, 255.ECPTYP250,

256.ECPTYP250, 257.ECPTYP250, 258.ECPTYP250, 259.ECPTYP250, 260.ECPTYP250, 261.ECPTYP250,
262.ECPTYP250, 263.ECPTYP250, 264.ECPTYP250, 265.ECPTYP250, 266.ECPTYP250, 270.ECPTYP250,
271.ECPTYP250, 284.ECPTYP250, 285.ECPTYP250, 286.ECPTYP250, 287.ECPTYP250, 288.ECPTYP250,
289.ECPTYP250, 290.ECPTYP250, 291.ECPTYP250, 292.ECPTYP250, 293.ECPTYP250, 294.ECPTYP250,
295.ECPTYP250, 300.ECPTYP250, 303.ECPTYP250, 309.ECPTYP250, 310.ECPTYP250, 311.ECPTYP250,
312.ECPTYP250, 313.ECPTYP250, 359.ECPTYP250, 454.ECPTYP250, 493.ECPTYP250, 565.ECPTYP250,
615.ECPTYP250, 616.ECPTYP250, 617.ECPTYP250, 618.ECPTYP250, 619.ECPTYP250, 620.ECPTYP250,
671.ECPTYP250, 682.ECPTYP250, 705.ECPTYP250.

D.5.1.11. The data element engineering-drawing-document-alphanumeric-identifier is used in the following

locations:

050.DWGNUM050, 051.DWGNUM050, 052.DWGNUM050, 053.DWGNUM050, 054.DWGNUM050,

060.DWGNUM050, 061.DWGNUM050, 062.DWGNUM050, 063.DWGNUM050, 064.DWGNUM050,
065.DWGNUM050, 066.DWGNUM050, 069.DWGNUM050, 070.DWGNUM050, 071.DWGNUM050,
080.DWGNUM050, 081.DWGNUM050, 082.DWGNUM050, 083.DWGNUM050, 084.DWGNUM050,
085.DWGNUM050, 086.DWGNUM050, 087.DWGNUM050, 160.DWGNUM160, 161.DWGNUM160,
162.DWGNUM160, 163.DWGNUM163, 164.DWGNUM164, 165.DWGNUM165, 166.DWGNUM165,
285.DWGNUM050, 286.DWGNUM050, 302.DWGNUM050, 306.DWGNUM050, 307.DWGNUM050,
311.DWGNUM050, 312.DWGNUM050, 315.DWGNUM050, 317.DWGNUM050, 323.DWGNUM050,
324.DWGNUM050, 325.DWGNUM050, 326.DWGNUM050, 327.DWGNUM050, 510.DWGNUM050,
511.DWGNUM050, 912.DWGNUM912.

D-94
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549
APPENDIX D

D.5.1.12. The data element part-product-identifier is used in the following locations:

053.PARNUM210, 054.PARNUM210, 084.PARNUM210, 087.PARNUM210, 104.PARNUM210,

MIL-STD-2549

CONCLUDING MATERIAL

Custodians: Preparing activity:

Army - AR OSD - DO
Navy -AP (Project: CMAN-0044)
Air Force - 16
NSA - NS

Review activities:
Army - AC, AL, AM, AT, AV, CE, CR, EA, ET, GL, HD, IE, LM, MD, ME, MI, MR, PT, SC, SC2, SM, TE,
TM TM2
Navy - AS, CG, CH, EC, MC, ND, NM, NP, OM, OS, TD, SH, YD
Air Force - 02, 05, 13, 17, 19, 29, 33, 94
DLA - DH
Other Government Activities - DC, DC1, DC5, DI, US, OST

149
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

MIL-STD-2549

(This page intentionally left blank)

150
Downloaded from http://www.everyspec.com on 2011-03-04T18:36:23.

STANDARDIZATION DOCUMENT IMPROVEMENT PROPOSAL

INSTRUCTIONS
1. The preparing activity must complete blocks 1, 2, 3, and 8. In block 1, both the document number and
revision letter should be given.

2. The submitter of this form must complete blocks 4, 5, 6, and 7.

3. The preparing activity must provide a reply within 30 days from receipt of the form.

NOTE: This form may not be used to request copies of documents, nor to request waivers, or clarification of
requirements on current contracts. Comments submitted on this form do not constitute or imply authorization
to waive any portion of the referenced documents(s) or to amend contractual requirements.
1. DOCUMENT NUMBER 2. DOCUMENT DATE (YYMMDD)
I RECOMMEND A CHANGE: MIL-STD-2549 970630
3. DOCUMENT TITLE
Configuration Management Data Interface
4. NATURE OF CHANGE (Identify paragraph number and include proposed rewrite, if possible. Attach extra sheets as needed.)

5. REASON FOR RECOMMENDATION

6. SUBMITTER
a. NAME (Last, First, Middle Initial) b. ORGANIZATION

c. ADDRESS (Include Zip Code) d. TELEPHONE (Include Area Code) 7. DATE SUBMITTED
(1) Commercial (YYMMDD)
(2) AUTOVON
(if applicable)
8. PREPARING ACTIVITY
a. NAME b. TELEPHONE (Include Area Code)
CALS & Electronic Data Interchange (1) Commercial (2) AUTOVON

Policy & Planning Division (703) 681-8475 761-8475

c. ADDRESS (Include Zip Code) IF YOU DO NOT RECEIVE A REPLY WITHIN 45 DAYS, CONTACT:
Defense Quality and Standardization Office
5203 Leesburg Pike, Suite 1403, Falls Church, VA 22041-3466
5203 Leesburg Pike, Suite 1609 Telephone (703) 756-2340 AUTOVON 289-2340
Falls Church, VA 22041-3346
DD Form 1426, OCT 89 Previous editions are obsolete 198-290

POS - Vidarbha Konkan Gramin Bank VIDHARBHA KONKAN
No ratings yet
POS - Vidarbha Konkan Gramin Bank VIDHARBHA KONKAN
67 pages
Sae Eia-649-2-2016
No ratings yet
Sae Eia-649-2-2016
48 pages
Basic Apparel Production 1 Teacher's Guide V2
90% (10)
Basic Apparel Production 1 Teacher's Guide V2
110 pages
Steps in Implementation of SAP PP
100% (1)
Steps in Implementation of SAP PP
12 pages
Mil STD 973
No ratings yet
Mil STD 973
258 pages
Mil STD 3046 PDF
No ratings yet
Mil STD 3046 PDF
94 pages
Mil STD 480B PDF
No ratings yet
Mil STD 480B PDF
104 pages
Mil STD 499b
100% (1)
Mil STD 499b
54 pages
ACMP - 6 - Ed - 1 NATO CONFIGURATION MANAGEMENT TERMS AND DEFINITIONS
100% (1)
ACMP - 6 - Ed - 1 NATO CONFIGURATION MANAGEMENT TERMS AND DEFINITIONS
52 pages
CS-25 Amendment 11 - AMC 25.1309
100% (1)
CS-25 Amendment 11 - AMC 25.1309
30 pages
EIA-632 - Processes For Engineering A System - 7 Jan 99
No ratings yet
EIA-632 - Processes For Engineering A System - 7 Jan 99
137 pages
Mil STD 756b
No ratings yet
Mil STD 756b
85 pages
MIL-HDBK-61A (SE) Configuration Management Guidance
No ratings yet
MIL-HDBK-61A (SE) Configuration Management Guidance
221 pages
Weight Estimating and Margins Manual
100% (3)
Weight Estimating and Margins Manual
65 pages
Audit Check List All Elements ISO TS 16949
88% (16)
Audit Check List All Elements ISO TS 16949
80 pages
2KW and 3KW Singlephase EV Charger
No ratings yet
2KW and 3KW Singlephase EV Charger
14 pages
Mil STD 470b
100% (1)
Mil STD 470b
78 pages
MIL-HDBK-61B (Draft) PDF
100% (2)
MIL-HDBK-61B (Draft) PDF
227 pages
Mil STD 1760D
No ratings yet
Mil STD 1760D
219 pages
Mil STD 490a PDF
No ratings yet
Mil STD 490a PDF
112 pages
Mil STD 973 Notice5
No ratings yet
Mil STD 973 Notice5
1 page
Mil STD 882e
No ratings yet
Mil STD 882e
104 pages
Department of Defense: Standard Practice For System Safety
No ratings yet
Department of Defense: Standard Practice For System Safety
31 pages
Arp4754 Ed-79
No ratings yet
Arp4754 Ed-79
105 pages
Di Sess 81646D
No ratings yet
Di Sess 81646D
5 pages
NASA-5001 Design+Test Factors of Safety
100% (1)
NASA-5001 Design+Test Factors of Safety
14 pages
Mil STD 1568d
No ratings yet
Mil STD 1568d
39 pages
Ansi Eia 649 Revision A Draft and Eia 649 Handbook Status
No ratings yet
Ansi Eia 649 Revision A Draft and Eia 649 Handbook Status
25 pages
Secnav Rme 2022
No ratings yet
Secnav Rme 2022
121 pages
Mil HDBK 516b
No ratings yet
Mil HDBK 516b
208 pages
Mil STD 11991a
No ratings yet
Mil STD 11991a
213 pages
The Systems Thinking Tool Box: Tree Diagram (TD)
100% (1)
The Systems Thinking Tool Box: Tree Diagram (TD)
8 pages
A STD 61 Part1 Issue1
No ratings yet
A STD 61 Part1 Issue1
61 pages
Mil STD 704
No ratings yet
Mil STD 704
25 pages
Mil STD 1474e Final 15apr2015
No ratings yet
Mil STD 1474e Final 15apr2015
123 pages
223.NCATT AAA Standard PDF
No ratings yet
223.NCATT AAA Standard PDF
17 pages
DEF STAN 00-40 Part 1 Issue 4 - Reliabilty and Maintainability
No ratings yet
DEF STAN 00-40 Part 1 Issue 4 - Reliabilty and Maintainability
20 pages
MIl STD 785B
No ratings yet
MIl STD 785B
88 pages
ECSS Trees 15april2016
No ratings yet
ECSS Trees 15april2016
10 pages
MTBF Calculator (Reliability Calculation System)
100% (1)
MTBF Calculator (Reliability Calculation System)
233 pages
DI-SESS-81758-Logistics Product Data
100% (1)
DI-SESS-81758-Logistics Product Data
2 pages
Mil HDBK 781a PDF
No ratings yet
Mil HDBK 781a PDF
411 pages
Di Sess 81121a
No ratings yet
Di Sess 81121a
8 pages
Mil DTL 6162C
No ratings yet
Mil DTL 6162C
32 pages
Mil STD 188 125 1 (2005)
No ratings yet
Mil STD 188 125 1 (2005)
108 pages
A Reliability Engineer's Use of Warranty Cost Information
No ratings yet
A Reliability Engineer's Use of Warranty Cost Information
11 pages
Mil STD 3013
No ratings yet
Mil STD 3013
127 pages
CA Bayonet PDF
No ratings yet
CA Bayonet PDF
56 pages
Ministry of Defence Defence Standard 00-42: Issue 3 Publication Date 14 March 2008
No ratings yet
Ministry of Defence Defence Standard 00-42: Issue 3 Publication Date 14 March 2008
48 pages
Mil STD 3034a
No ratings yet
Mil STD 3034a
115 pages
Data Item Description: H TT P: // A S S Ist - D A P S - D L A. M I L
No ratings yet
Data Item Description: H TT P: // A S S Ist - D A P S - D L A. M I L
2 pages
Mil HDBK 470a PDF
No ratings yet
Mil HDBK 470a PDF
716 pages
Aviation CSIHandbook
No ratings yet
Aviation CSIHandbook
186 pages
MIL System Overview
No ratings yet
MIL System Overview
13 pages
History of Iso9100
100% (1)
History of Iso9100
3 pages
Simcenter T3STER Master 2301 Useref
No ratings yet
Simcenter T3STER Master 2301 Useref
138 pages
Mil Burn in Std883-1015
No ratings yet
Mil Burn in Std883-1015
4 pages
Di Sess 81248B
No ratings yet
Di Sess 81248B
2 pages
FAA HIRF Advisory Circular 20-158
No ratings yet
FAA HIRF Advisory Circular 20-158
42 pages
Ministry of Defence Defence Standard 00-44: Issue 1 Publication Date 31 January 2007
No ratings yet
Ministry of Defence Defence Standard 00-44: Issue 1 Publication Date 31 January 2007
50 pages
FMD-91 1991
100% (1)
FMD-91 1991
365 pages
Ministry of Defence Defence Standard 00-40: Issue 6 Publication Date 13 June 2008
No ratings yet
Ministry of Defence Defence Standard 00-40: Issue 6 Publication Date 13 June 2008
19 pages
Mil STD 3046 (Ar) Draft
No ratings yet
Mil STD 3046 (Ar) Draft
90 pages
MIL-STD-3046 ARMY 11mar13
100% (1)
MIL-STD-3046 ARMY 11mar13
94 pages
Windham, Jeff - DoD Military Standard For Configuration Management
No ratings yet
Windham, Jeff - DoD Military Standard For Configuration Management
26 pages
Unlocking Statistics for the Social Sciences
From Everand
Unlocking Statistics for the Social Sciences
Norma Sinclair
No ratings yet
Naval Ordnance & Gunnery
No ratings yet
Naval Ordnance & Gunnery
375 pages
Glass and Mirrors On: Section 9L
No ratings yet
Glass and Mirrors On: Section 9L
13 pages
Naval Ordnance V1 Part1 PDF
100% (1)
Naval Ordnance V1 Part1 PDF
206 pages
N1996 MS-7061 Version 1.0
No ratings yet
N1996 MS-7061 Version 1.0
102 pages
USMC
No ratings yet
USMC
14 pages
GD01 - Digital Data Specification - V0
No ratings yet
GD01 - Digital Data Specification - V0
9 pages
Designing Scenarios - Rebecca Wirfs-Brock PDF
100% (1)
Designing Scenarios - Rebecca Wirfs-Brock PDF
8 pages
TOR - Printing IEC Materials For Closeout Events
No ratings yet
TOR - Printing IEC Materials For Closeout Events
11 pages
Storage Tank Selection, Sizing and Troubleshooting, Kolmetz Handbook of Process Equipment Design
100% (3)
Storage Tank Selection, Sizing and Troubleshooting, Kolmetz Handbook of Process Equipment Design
39 pages
Risk Factors in Software Development Phases: European Scientific Journal January 2014
No ratings yet
Risk Factors in Software Development Phases: European Scientific Journal January 2014
21 pages
Test Plan
100% (8)
Test Plan
25 pages
25MIS
No ratings yet
25MIS
352 pages
Regulations For Safety Inspection of Hazardous Machines and Equipment
No ratings yet
Regulations For Safety Inspection of Hazardous Machines and Equipment
132 pages
Mil L 0046010e
100% (1)
Mil L 0046010e
21 pages
Specification For Pipe Fabrication Installation
No ratings yet
Specification For Pipe Fabrication Installation
24 pages
S F A M T B T S P T F Ethiopian Electric Utility (Eeu)
No ratings yet
S F A M T B T S P T F Ethiopian Electric Utility (Eeu)
12 pages
Bauxite Export Project, Guinea - CC - 006 Method Statement For Lateral Load Test SP-A8GA-006-FLR-CS-PL-5010 RC
No ratings yet
Bauxite Export Project, Guinea - CC - 006 Method Statement For Lateral Load Test SP-A8GA-006-FLR-CS-PL-5010 RC
10 pages
As 2437-1987 Flusher Sanitizers For Bed Pans and Urine Bottles
No ratings yet
As 2437-1987 Flusher Sanitizers For Bed Pans and Urine Bottles
8 pages
MDTS 116 Rev 6
No ratings yet
MDTS 116 Rev 6
13 pages
Designer Sample Resume
No ratings yet
Designer Sample Resume
12 pages
Installation Qualification For Compressed Air System
100% (2)
Installation Qualification For Compressed Air System
15 pages
NHCX Objectives: Visualization of NHCX Across Multiple Provider or Payer Apps
No ratings yet
NHCX Objectives: Visualization of NHCX Across Multiple Provider or Payer Apps
7 pages
Supply and Installation of Energy Dispersive X-Ray Fluorescence (Edxrf) Spectrometer at Regional Forensic Science Laboratories, Hubli
No ratings yet
Supply and Installation of Energy Dispersive X-Ray Fluorescence (Edxrf) Spectrometer at Regional Forensic Science Laboratories, Hubli
37 pages
Ac145 1
No ratings yet
Ac145 1
47 pages
Method Statement-Ext Pipe Fittings
No ratings yet
Method Statement-Ext Pipe Fittings
13 pages
CQI-11 Proc Table
No ratings yet
CQI-11 Proc Table
28 pages
4ece M18
No ratings yet
4ece M18
5 pages
Review of Indonesia Buidling Regulartion and Standard
No ratings yet
Review of Indonesia Buidling Regulartion and Standard
17 pages
Information Requirements For Ball Valves: January
No ratings yet
Information Requirements For Ball Valves: January
19 pages
Corrosion Resistant Coated Dowel Bars: Standard Specification For
No ratings yet
Corrosion Resistant Coated Dowel Bars: Standard Specification For
2 pages

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.