Mil STD 1388 2B - Notice 1 PDF

Downloaded from http://www.everyspec.
com
MILITARY STANDARD
MIL-STD-1388-2B
Notice 1
21 Jan 93
DOD REQUIREMENTS FOR A LOGISTIC SUPPORT ANALYSIS RECORD
TO ALL HOLDERS OF MIL-STD-1388-2B
1. THE FOLLOWING PAGES OF MIL-STD-1388-2B HAVE BEEN REVISED AND SUPERSEDE THE
PAGES LISTED:
NEW PAGE(S) DATE SUPERSEDED PAGE(S) DATE
v 28 March 1991 v REPRINTED WITHOUT CHANGE
vi and vii 21 January 1993 vi and vii 28 March 1991
viii 28 March 1991 viii REPRINTED WITHOUT CHANGE
ix/x 21 January 1993 ix/x 28 March 1991
7 and 8 21 January 1993 7 and 8 28 March 1991
9 28 March 1991 9 REPRINTED WITHOUT CHANGE
10 thru 14 21 January 1993 10 thru 14 28 March 1991
18 and 19/20 21 January 1993 18 and 19/20 28 March 1991
26 21 January 1993 26 28 March 1991
29 21 January 1993 29 28 March 1991
40 and 41 28 March 1991 40 and 41 REPRINTED WITHOUT CHANGE
42 21 January 1993 42 28 March 1991
44 21 January 1993 44 28 March 1991
72 21 January 1993 72 28 March 1991
95 21 January 1993 95 28 March 1991
95a 21 January 1993 NEW
96 21 January 1993 96 28 March 1991
102 21 January 1993 102 28 March 1991
AMSC NO A6045 FSC ILSS
DISTRIBUTION STATEMENT A. Approved for public release: distribution is
unlimited.
l of 3
Downloaded from http://www.everyspec.com
MIL-STD-1388-2B
NOTICE 1
MILITARY STANDARD
129 28 March 1991
129 21 January 1993 REPRINTED WITHOUT CHANGE
28 March 1991 130 and 131
130 and 131 132 and 133 28 March 1991
132 and 133 21 January 1993 REPRINTED WITHOUT CHANGE
28 March 1991 134
134 135 28 March 1991
28 March 1991 136
136 137 28 March 1991
28 March 1991 138
138 139 28 March 1991
28 March 1991 140
140 143 28 March 1991
28 March 1991 144
144 149 28 March 1991
149 21 January 1993 28 March 1991
21 January 1993 150 thru 155
150 thru 155 156 REPRINTED WITHOUT CHANGE
156 28 March 1991 28 March 1991
21 January 1993 159 thru 162
163 28 March 1991 28 March 1991
21 January 1993 164 thru 168
173 28 March 1991 174 and 175 28 March 1991
174 and 175 21 January 1993 REPRINTED WITHOUT CHANGE
28 March 1991 176
176 177 28 March 1991
28 March 1991 178 and 179
178 and 179 180 thru 186 28 March 1991
180 thru 186 21 January 1993 REPRINTED WITHOUT CHANGE
28 March 1991 187
187 188 28 March 1991
28 March 1991 193
193 194 28 March 1991
28 March 1991 219
219 220 thru 225 28 March 1991
220 thru 225 21 January 1993 226 and 227 REPRINTED WITHOUT CHANGE
226 and 227 28 March 1991 28 March 1991
21 January 1993 228
228 251 REPRINTED WITHOUT CHANGE
251 28 March 1991 28 March 1991
21 January 1993 252
255 28 March 1991 28 March 1991
21 January 1993 256
257 28 March 1991 28 March 1991
21 January 1993 258
261 28 March 1991 28 March 1991
21 January 1993 262
271 28 March 1991 28 March 1991
21 January 1993 272
272 273 thru 275 28 March 1991
273 thru 275 21 January 1993 REPRINTED WITHOUT CHANGE
28 March 1991 276
276 281 28 March 1991
28 March 1991 282
303 28 March 1991 28 March 1991
21 January 1993 304
319 28 March 1991 28 March 1991
21 January 1993 320
320 335 28 March 1991
28 March 1991 336 and 337
336 and 337 338 thru 340 28 March 1991
338 thru 340 21 January 1993
2of3
MIL-STD-1388-2B
NOTICE 1
MILITARY STANDARD
356 21 January 1993 356 28 March 1991
401a thru 401e 21 January 1993 NEW
420 21 January 1993 420 28 March 1991
439 21 January 1993 439 28 March 1991
451 21 January 1993 451 28 March 1991
472 21 January 1993 472 28 March 1991
484 21 January 1993 484 28 March 1991
486 21 January 1993 486 28 March 1991
492 21 January 1993 492 28 March 1991
513 21 January 1993 513 28 March 1991
513a thru 513f 21 January 1993 NEW
515 21 January 1993 515 28 March 1991
557 21 January 1993 557 28 March 1991
571 thru 599/600 21 January 1993 571 thru 599/600 28 March 1991
2. RETAIN THIS NOTICE AND INSERT BEFORE TABLE OF CONTENTS.
3. Holders of MIL-STD-1388-2B will verify that the page change indicated
herein have been entered. This notice will be retained as a check sheet.
This issuance is a separate publication. Each notice is to be retained by
stocking points until the Military Standard is completely revised or
cancelled.
Custodians: Preparing Activity

Army - TM Army - TM
Navy - AS
Air Force - 95 (Project No. ILSS-0003)
Reviewing Activities:
Army - ME, MI, AV, AT, CR
Navy - SH, YD, OS, MC
Air Force - 11, 13, 15, 16, 17
Miscellaneous DOD/NASA - NS, NA, DC, DH, DS
3 of 3
MIL-STD-1388-2B
CONTENTS
Paragraph Page
1. SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Purpose .. . . . . . . . . . . ... . . . . . . . .. .. . . 1
1.2 Application of standard . . . . . . . . . . . . . . . . . . . . . . . 1
1.2.1 Content of appendices .. . . . . . . . . . . . . . . . . . . . . . . 1
1.2.2 Tailoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2.3 LSA data documentation process . . . . . . . . . . . . . . . . . . 1
2. REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4. GENERAL REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1 LSAR data selection sheets . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 LSAR data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2.1 Manual LSAR data. . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2.1.1 Manual LSAR report generation . . . . . . . . . . . . . . . . . . 12
4.2.2 Automated LSAR data . . . . . . . . . . . . . . . . . . . . . . 12
4.2.2.1 Performing activity LSAR ADP system . . . . . . . . . . . . 12
4.2.2.2 LSAR ADP system criteria . . . . . . . . . . . . . . . . . . . . . . . 12
5. DETAILED INSTRUCTIONS FOR MANUAL/AUTOMATED
PREPARATION OF LSAR RELATIONAL TABLES . . . . . . . . . . . . . 13
5.1 Requiring authority data tables . . . . . . . . . . . . . . . . . . 13
5.1.1 Cross functional requirement . . . . . . . . . . . . . . . . . . . . 13
5.1.2 Operations and maintenance requirements . . . . . . . . . 13
5.2 Performing activity data tables . . . . . . . . . . . . . . . . . . 13
5.2.1 Reliability, availability, maintainability;
Failure modes, effects and criticality
analysis; maintainability analysis . . . . . . . . . . .
5.2.2 Task analysis and personnel and support
requirements . . . . . . . . . . . . . . . . . . . . 14
5.2.3 Support equipment and training material
requirements . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.2.4 Unit under test requirements and justification . . 15
5.2.5 Facilities considerations . . . . . . . . . . . . . . . . . . 15
5.2.6 Personnel skill considerations . . . . . . . . . . . . . . . . . . 15
5.2.7 Packaging and provisioning requirement . . . . . . . . . . 16
5.2.8 Transportability engineering analysis . . . . . . . . . . . 16
5.3 LCN assignment and structure . . . . . . . . . . . . . . . . . . . . 16
5.4 LSA/LSAR guidance conference . . . . . . . . . . . . . . . . . . . . 16
6. NOTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1 Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2 Issue of DODISS . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.3 Consideration of data requirements . . . . . . . . . . . . . . . 17
6.4 Subject term (key word) listing . . . . . . . . . . . . . . . . . . 19
6.5 Suppression data . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.6 Changes from previous issue . . . . . . . . . . . . . . . . . 19
v REPRINTED WITHOUT CHANGE

MIL-STD-1388-2B
APPENDICES
APPENDIX A. LSAR RELATIONAL TABLES . . . . . . . . . . . . . . . . . . . . . . 21
10. SCOPE . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . 21
20. CONCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
30. RELATIONAL DATA TABLE FORMAT . . . . . . . . . . . . . . . . 21
30.1 Functional LSAR relational table listing
and table relationships . . . . . . . . . . . . . . . . . . . . 21
30.2 LSAR relational tables . . .. . . . . . . . . . . . . . . . 22
30.3 LSAR Data Table Exchange/Delivery . . . . . . . . . . . . . . 24
40. CROSS FUNCTIONAL REQUIREMENT . . . . . . . . . . . . . . . . . 26
50. OPERATIONS AND MAINTENANCE REQUIREMENT . . . . . . . . . 32
60. RELIABILITY, AVAILABILITY, AND MAINTAINABILITY;
FAILURE MODES, EFFECTS, AND CRITICALITY ANALYSIS;
AND MAINTAINABILITY ANALYSIS . . . . . . . . . . . . . . . . 40
70. TASK ANALYSIS AND PERSONNEL AND SUPPORT
REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . 53
80. SUPPORT EQUIPMENT AND TWINING MATERIEL
REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . 62
90. UNIT UNDER TEST REQUIREMENTS AND DESCRIPTION . . . . . . 72
100. FACILITIES CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . 81
110 PERSONNEL SKILL CONSIDERATIONS . . . . . . . . . . . . . . . 86
120 PACKAGING AND PROVISIONING REQUIREMENT . . . . . . . . . . . . 90
130 TRANSPORTABILITY ENGINEERING ANALYSIS . . . . . . . . . . . . . 105
APPENDIX B. LSAR REPORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

10. PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
20. CONCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
20.1 LSARdata table to report matrix . . . . . . . . . . . . . . . . . 115
20.2 General report selection criteria . . . . . . . . . . . . . . . . 115
30. LSAR REPORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
30.1 LSA-001, Annual Man-Hours by Skill Specialty Code
and Level of Maintenance . . . . . . . . . . . . . . . . . . . . 116
30.2 LSA-003, Maintenance Summary . . . . . . . . . . . . . . . 117
30.3 LSA-004, Maintenance Allocation Chart . . . . . . . . . . . . 118
30.4 LSA-005, Support Items Utilization Summary . . . . . . . 120
30.5 LSA-006, Critical Maintenance Task Summary . . . . . . . 121
30.6 LSA-007, Support Equipment Requirements . . . . . . . . . . 121
30.7 LSA-008, Support Items Validation Summary . . . . . . . . 121
30.8 LSA-009, Support Items List 122
30.9 LSA-010, Parts Standardization Summary . . . . . . . . . . . 122
30.10 LSA-011, Special Training Equipment/Device
Summary . . . . . . . . . . . . . . . . . . . . . . . . 122
30.11 LSA-012, Facility Requirement . . . . . . . . . . . . . . 122
30.12 LSA-013, Support Equipment Grouping Number
Utilization Summary. . . . . . . . . . . . . . . . . . . . . . 123
30.13 LSA-014, Training Task List . . . . . . . . . . . . . . . 123
30.14 LSA-016, Preliminary Maintenance Allocation
Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
30.15 LSA-018, Task Inventory Report . . . . . . . . . . . . . . . . . . . 124
30.16 LSA-019, Task Analysis Summary . .. . . . . . . . . . . . . . 124
30.17 LSA-023, Maintenance Plan Summary . . . . . . . . . . . . . . . . 125
30.18 LSA-024, Maintenance Plan .. . . . . . . . . . . . . . . . . . 126
30.19 LsA-025, Packaging Requirements Data . . . . . . . . . . . . . 129
Supersedes page vi of 28 March 91 vi

MIL-STD-1388-2B
30.20 LSA-026, Packaging Developmental Data . . . . . . . . . . . . 129
30.21 LSA-027, Failure/Maintenance Rate Summary . . . . . . . . 129
30.22 LSA-030, Indentured Parts List . . . . . . . . . . . . . . . . . . . 130
30.23 LSA-032, Defense Logistics Services Center
(DLSC) Submittals . .. . . . . . . . . . . . . . . . . . . . 133
30.24 LSA-033, Preventive Maintenance Checks and
Services (PMCS) . . . . . . . . . . . . . . . . . . . . . . . . 135
30.25 LSA-036, Provisioning Requirements . . . . . . . . . . . . . . . 135
30.26 LSA-037, Spares and Support Equipment
Identification List .. . . . . . . . . . . . . . . . . . . . 141
30.27 LSA-039, Critical and Strategic Item Summary . . . . . 141
30.28 LSA-040, Authorization List Items Summary . . . . . . . . 141
30.29 LSA-046, Nuclear Hardness Critical Item
Summary . . . . . . . . . . . . . . . . . . . . . . . . . 142
30.30 LSA-050, Reliability Centered Maintenance
Summary . . . . . . . . . . . . . . . . . . . . . . 142
30.31 LSA-056, Failure Modes, Effects and Criticality
Analysis (FMECA) Report . . . . . . . . . . . . . . . . . . . 143
30.32 LSA-058, Reliability and Maintainability Analysis
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
30.33 LSA-065, Manpower Requirements Criteria . . . . . . . . . . 144
30.34 LSA-070, Support Equipment Recommendation
Data (SERD) . . . . . . . . . . . . . . . . . . . . . . . 144
30.35 LSA-071, Support Equipment Candidate List . . . . . . . . 145
30.36 LSA-072, Test Measurement and Diagnostic
Equipment (TMDE) Requirements Summary . . . . . . . 145
30.37 LSA-074, Support Equipment Tool List. . . . . . . . . 145
30.38 LSA-075, Consolidated Manpower, Personnel and
Training Report . . . . . . . . . . . . . . . . . . . . . . 146
30.39 LSA-076, Calibration and Measurement Require-
ments Summary . . . . . . . . . . . . . . . . . . . . 146
30.40 LSA-077, Depot Maintenance Interservice
Data Summary . .. . . . . . . . . . . . . . . . . 147
30.41 LSA-078, Hazardous Materials Summary . . . . . . . . . . . . . 147
30.42 LSA-080, Bill of Materials . . . . . . . . . . . . . . . . . 147
30.43 LSA-085, Transportability Summary . . . . . . . . . . . . 149
30.44 LSA-126, Hardware Generation Breakdown Tree . . . . . . 149
30.45 LSA-151, Provisioning Parts List Index . . . . . . . . . . . 149
30.46 LSA-152, PLISN Assignment/Reassignment . . . . . . . . . 149
30.47 LSA-154, Provisioning Parts Breakout Summary . . . . . 152
30.48 LSA-155, Recommended Spare Parts List for
Spares Acquisition Integrated with Production
(SAIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
APPENDIX C. GUIDANCE FOR ASSIGNMENT OF LOGISTIC SUPPORT
ANALYSIS CONTROL NUMBER (LCN), ALTERNATE LCN
CODE, LCN TYPE AND USABLE ON CODE (UOC) . . . . . . . . . . . . 323
10. PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
10.1 Traditional LCN assignments . . . . . . . . . . . . . . . . 323
10.2 Functional and physical LCN assignments:
anew perspective . . . . . . . . . . . . . . . . . . . . . . . . 323
20. LCN ASSIGNMENT . . . . . . . . . . . . . . . . . . . . . 323
20.1 Classical LCN assignment method . . . . . . . . . . . . . . . . . . . 324
20.2 Modified classical assignment method . . . . . . . . . . . . . 324
20.3 Sequential assignment method . . . . . . . . . . . . . . . 324
vii Supersedes page vii of 28 March 91

MIL-STD-1388-2B
328
30. ALTE~ATE LCNCODE(ALC) . . . . . . . . . . . . . . . . . . 328
30.1 ALC usage for a single configuration/model . . . . . . . 330
30.2 ALC usage for LSAR reports . . . . . . . . . . . . . . . . . 330
30.3 Lower tiered LCN/ALC selections . . . . . . . . . . . . .
40. LOGISTIC SUPPORT ANALYSIS CONTROL NUMBER 330
TYPE (LCN-TYPE). . . . . . . . . . . . . . . . . . . . . . . 330
50. USABLE EN CODE . . . . . . . . . . . . . . . . . . . . . . . . . . 332
50.1 ALC And UOC relationship . . . . . . . . . . . . . . . . . . . 332
50.2 UOC and ALC usage for LSW reports . . . . . . . . . . . . .
60. SERIAL NUMBER CONTROL AS AN ALTERNATIVE FOR 332
CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . 334
70. SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX D. APPLICATION AND TAILORING GUIDANCE FOR THE 335

LOGISTIC SUPPORT ANALYSIS RECORD (LSAR) . . . . . . . . . . . . 335
10. GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
10.1 Purpose
— . . . . . . . . . . . . . . . . . . . . . . . . . 335
10.2 How to use this appendix . . . . . . . . . . . . . . . . 335
20. LSAR APPLICATION AND USE BY LIFE CYCLE PHASE . . . . . . 335
20.1 LSA process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
20.2 Pre-concept and concept exploration (CE) phase . . . 336
20.3 Demonstration and validation phase . . . . . . . . . . . . . 337
20.4 Full scale development (FSD) phase . . . . . . . . . . . . . . . 337
20.5 Production and Deployment Phase .. . . . . . . . . . . . . . 337
30. TAILORING LSAR REQUIREMENTS . . . . . . . . . . . . . . . 337
30.1 LSA task selection . . . . . . . . . . . . . . . . . . . . . . . . .
30.2 Interfacing and coordination with other 338
program elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
40. SCHEDULING OF LSAR DATA . . . . . . . . . . . . . . . . . . . . 340
50. ALTERNATIVES FOR DATA DELIVERY . . . . . . . . . . . . . . .
355
APPENDIX E. DATA ELEMENT DICTIONARY. . . . . . . . . . . . . . . . . . . 355
10. PURPOSE . . . . . . . . . . . . . . . .. . . . . . 355
20. SECTIONS .. . . . . . . . . . . . . . . . . . . . . . . . . 355
20.1 Section 1: Index of data element titles . . . . . . . . . 355
20.2 Section 2: Table of codes and titles . . . . . . . . . . . . 355
20.3 Section 3: Data element definitions . . . . . . . . . . . . .
APPENDIX F. LIST OF LOGISTIC SUPPORT ANALYSIS RECORD ACRONYMS 563

10. PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
20. ACRONYMS . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURES
Page
Figure
2
1 LSA data documentation process . . . . . . . . . . . . . . . . . . . 3
2 LSAR data flow and system engineering interface . . 4
3 LSAR R&M parameter interface . . . . . . . . . . . . . . . . . . . . . 27
4 X table relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5 A table relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6 B table relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7 C table relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8 E table relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
9 U table relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
10 F table relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
BEPRINTED WITHOUT CHANGE
MIL-STD-l388-2B
11 G table relationships. . . . . . . . . . . . . . . . . . . . . . 87
12 H table relationships . . . . . . . . . . . . . . . . . . . . . 91
13 J table relationships . . . . . . . . . . . . . . . . . . . . . . . 106
14 LSAR data tables to report matrix . . . . . . . . . . . . . 153
15 thru 62 Standard LSAR reports . . . . . . . . . . . . . . . . . . . . 193
63 Classical LCN assignment method .. . . . . . . . . . . . . . . 325
64 Modified classical LCN assignment method . . . . . . . . . 326
65 Sequential LCN assignment method . . . . . . . . . . . . . . . . . 327
66 Alternate LCN code usage . . . . . . . . . . . . . . . . . . . . . 329
67 Functional versus physical LCN assignment . . . . . . . . . 331
68 Usable on code and alternate LCN code usage . . . . . . 333
69 LSAR data table utilization by hardware
breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
70 Preconcert and concept exploration phase LSAR . . . . 344
71 Example of DD Form 1949-3 . . . . . . . . . . . . . . . . . . . 571
TABLES
Table Page
I LSA-036 report format . . . . . . . . . . . . . . . . . . . . . . 136

II LSAR data tables related to MIL-STD-1388-1
tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
III Data item description relationships to
the LSAR . . . . . . . . . . . . . . . . . . . . . . . . . 346
ix/x Supersedes page ix/x of 28 March 91

THIS PAGE INTENTIONALLY LEPT BLANK

MIL-STD-1388-2B
MIL-STD-879 Designation of Aircraft Propulsion Gas Turbine Engines

MIL-STD-882 System Safety Program Requirements
MIL-STD-965 Parts Control Program

MIL-STD-1388-1 Logistic Support Analysis
MIL-STD-1390 Level of Repair Analysis
MIL-STD-1478 Task Performance Analysis

MIL-STD-1519 Test Requirements Documents, Preparation of
MIL-STD-1629 Procedures for Performing a Failure Mode, Effects
and Criticality Analysis
.
MIL-STD-1839 Calibration and Measurement Requirements
MIL-STD-1843 Reliability Centered Maintenance for Aircraft, Engines,

and Equipment
MIL-STD-2073-1 DOD Materiel, .Procedures for Development and Application

of Packaging Requirements
MIL-STD-2073-2 Packaging Requirement Codes
MIL-STD-2097 Acquisition of Support Equipment and Associated Integrated
Logistics Support
MIL-STD-2173 Reliability Centered Maintenance Requirements for Naval

Aircraft, Weapon Systems, and Support Equipment
DOD-STD-2121(Navy) Determination of Electronic Test Equipment Parameters
Military Handbooks.
MIL-HDBK-59 Computer-Aided Acquisition and Logistic Support (CALS)
Program Implementation Guide
MIL-HDBK-217 Reliability Prediction of Electronic Equipment
Military Specifications.
MIL-T-31000 Technical Data Packages, General Specifications for
MIL-C-7024 Calibrating Fluid, Aircraft Fuel System Components
MIL-M-63036 Manuals, Technical: Operator’s, Preparation of (Army)
-7- Supersedes page 7 of 28 March 91

MIL-STD-1388-2B
MIL-M-63038 Manuals, Technical: Unit or Aviation Unit Direct Support,
Aviation Intermediate, and General Support Maintenance,
Requirements for
MIL-M-83495 Manuals, Technical: On-Equipment Set, Organizational

Maintenance Manuals; Detailed Requirements for
Preparation of (For USAF Equipment)
Federal Manuals and Catalogs.

H4/H8 Commercial and Government Entity Code
H6-1 Federal Item Name Directory for Supply Cataloging
(Unless otherwise indicated, copies of federal and military specifications,

standards, and handbooks are available from the Standardization Documents
Order Desk, Building 4D, 700 Robbins Avenue, Philadelphia, PA, 19111-5094.)
Bulletins.
ANA Bulletin 306 Engines, Aircraft Turbine and Jet, Designation of
ANA Bulletin 395 Engines, Aircraft Reciprocating, Designation of
Other Documents.
DOD 41OO.38-M DOD Provisioning and Other Preprocurement Screening

Manual
DOD 5000.12-M DOD Manual for Standard Data Elements
DODD 5000.2 Acquisition Management Policies and Procedures
AR 70-50 Designating and Naming Defense Equipment

NAVMATINST 8800.3 Military Aerospace Vehicles
AFR 82-5
AR 700-26
NAVAIRINST 13100.1 Designating and Naming Military Aircraft
AFR 66-11
AR 700-82
OPNAVINST 4410.2 Joint Regulation Governing the Use and Application
AFR 66-45 of Uniform Source Maintenance and Recoverability Codes
MCO 4400.120
DSAR 4100.6
NAVFAC P-72 Category Codes for Real Property, Navy
NAVPERS 15839 Manual of Navy Officer Classifications
NAVPERS 18068 Manual of Navy Enlisted Manpower and Personnel

Classifications and Occupational Standards
MCO P 1200.7 Military Occupational Specialties
Supersedes page 8 of 28 March 91 -8-

MIL-STD-1388-2B
AR 415-28 Department of the Army Facility Classes and Construction
Categories
AR 611-101 Manual of Commissioned Officer Military Occupational

Specialties
AR 611-112 Manual of Warrant Officer Military Occupational
Specialties
AR 611-201 Enlisted Military Occupational Specialties
AFR 36-1 Officer Classification Manual
AFR 39-1 Airman Classification Manual

AFM 86-2 Standard Facility Requirements
FPM Supplement Civil Service Commission, Job Grading Standard
512-1
SB 700-20 Army Adopted/Other Items Selected for Authorization/
List of Reportable Items
JCS PUB 1 Dictionary of United States Military Terms for Joint

Usage
DA CPR 502 Department of Army - Civilian Personnel Regulations,
Standardized Job Descriptions
DA PAM 700-20 Department of Army - Test, Measurement, and Diagnostic
Equipment Register
Industry Documents.
ANSI Y32.16 Reference Designations for Electrical and Electronics
Parts and Equipments
(Non-Government standards and other publications are normally available from
the organizations that prepare or distribute the documents. These documents
also may be available in or through libraries or other informational
services.)
3. DEFINITIONS. The LSAR data elements are defined in the description of the
LSAR reports contained in appendix B and in the LSAR data element dictionary
comprising appendix E of this standard. In addition, for the purposes of this
standard, the following definitions shall apply:
3.1 Assembly. A number of parts or subassemblies, or any combination
thereof, joined together to perform a specific function and capable of
disassembly (e.g., power shovel-front, fan assembly, audio frequency
amplifier). NOTE: The distinction between an assembly and subassembly is
determined by the individual application. An assembly, in one instance, may
be a subassembly in another where it forms a portion of an assembly.
3.2 Attaching part. An item used to attach assemblies or parts to the
equipment or to each other,.
-9- PRINTED WITHOUT CHANGE
MIL-STD-1388-2B
3.3 Component. An assembly or any combination of parts, subassemblies, and

assemblies mounted together normally capable of independent operation in a
variety of situations.
3.4, Desire Change. An approved engineering change incorporated into the end
item which modifies, adds to, deletes, or supersedes parts in the end item.
3.5 End Article/Product. A component, assembly or subassembly being procured

as the top item on the contract.
3.6 End Item. A final combination of end products, component parts/materials
which is ready for its intended use, e.g. , ship, tank, mobile machine shop,
aircraft, receiver, rifle, or recorder.
3.7 LSA Candidate. A component, subassembly, assembly, software, or end
item/article on which maintenance action is considered feasible as a result of
a preliminary or detailed tradeoff analysis.
3.8 LSA Documentation. All data resulting from performance of LSA tasks,
conducted under MIL-STD-1388-1, to include LSAR, pertaining to an acquisition
program.
3.9 Manufacturers Part Number. See reference number.
3.10 Part. One, two or more pieces, joined together which are not normally
subject to disassembly without destruction or impairment of designed use.
3.11 Part Number. See reference number.
3.12 Reference Number. Any number, other than a government activity stock
number, used to identify an item of production, or used by itself or in
conjunction with other reference numbers to identify an item of supply.
Reference numbers include: manufacturer’s part, drawing, model, type, or
source controlling numbers; manufacturer’s trade name; specification or
standard numbers; and, specification or standard part, drawing, or type
numbers. See appendix E, Data Element Definition 337.
3.13 Repair Part. Material capable of separate supply and replacement which
is required for the maintenance, overhaul, or repair of a system, equipment or
end item. This definition does not include Support Equipment, but does include
repair parts for support equipment.
3.14 Spares. Articles identical to or interchangeable with the end articles
on contract which are procured over and above the quantity needed for initial
installation for support of a system.
3.15 Subassembly. Two or more parts which form a portion of an assembly or a

component replaceable as a whole, but having a part or parts which are
individually replaceable (e.g., gun mount stand, window recoil mechanism,
floating piston, telephone dial, mounting board with mounted parts, power
shovel dipper stick).
3.16 Support Equipment. “Support Equipment” is that equipment required to

make an item, system, or facility operational in its intended environment.
This includes all equipment required to maintain and operate the item, system,
or facility including aerospace ground equipment and ground equipment.

MIL-STD-1388-2B
3.17 Support Items. Items subordinate to or associated with an end item,

i.e., spares, repair parts, and support equipment.
3.18 Topdown. A breakdown accomplished by sequencing all parts comprising
the end item in a lateral and descending “family tree/generation breakdown”.
This breakdown shall consist of the end-item, including all components,
listing every assembly, subassembly, and parts which can be disassembled,
reassembled/replaced. All parts are listed in their relation to the end item,
component, assembly, or installation system in which they are contained and to
their own further sub-subassemblies and parts. This relationship is shown by
means of an indenture code.
4. GENERAL REQUIREMENTS. LSA documentation, including LSAR data, is
generated as a result of the analysis tasks specified in MIL-STD-1388-1. As
such, the LSAR data shall serve as the Integrated Logistic Support (ILS)
technical database applicable to all materiel acquisition programs to satisfy
the support acquisition. The DEDs, data field lengths, and data formats
described in appendices A and E shall be adhered to by the performing activity
in establishing the LSAR database. The specific data entry media, storage,
and maintenance procedures are left to the performing activity. Validated
LSAR ADP systems are available for automated storage of the LSAR data. A list
of these LSAR ADP systems may be obtained from the USAMC Materiel Readiness
Support Activity, ATTN: AMXMD-EL i Lexington, KY 40511-5101. The LSAR data
forms a database to:
a. Determine the impact of design features on logistics support.
b. Determine the impact of the proposed logistics support system on the
system/equipment availability and maintainability goals.
c. Provide data for tradeoff studies, life cycle costing, and logistic
support modeling.
d. Exchange valid data among functional organizations.
e. Influence the system/equipment design.
f. Provide data for the preparation of logistics products specified by
DIDs.
g. Provide the means to assess supportability of the fielded item.

h. Provide the means to evaluate the impact of engineering change,
product improvement, major modification or alternative proposals.
4.1 LSAR data requirements form. The LSAR data requirements form
(DD Form 1949-3, figure 71) provides a vehicle for identifying the required
LSAR data elements to be completed and, when applicable, the media of delivery
(e.g., floppy disk, magnetic tape, etc.). Preparation of the LSAR data
requirements form should be a result of the LSAR tailoring process discussed in
appendix D. The data requirements form are used to identify the specific data
elements that are required and identified on the relational data tables. In
addition, the form will be used to specify the data elements required for
each Provisioning Technical Documentation (PTD) list or packaging
categorization of items required. Generation of the PTD lists (format shown

MIL-STD-1388-2B
as table I, LSA-036 report) may be accomplished manually or via automation
techniques. When more than one option of entry for a data element is
possible, the options are spelled out as part of the data element dictionary.
In a similar manner, the LSAR data requirements form list the options for data
elements that have more than one option for entry. Only one option will be
specified for a data element with multiple entry options. The LSAR data
requirements form will be attached to the contract SOW and attached to the
Contract Data Requirements List (CDRL), DD Form 1423, for the applicable DIDs.
Detailed instructions for completing DD Form 1949-3 are provided in appendix B,
paragraph 20.1 and figure 14.
4.2 LSAR data. The preparation and maintenance of LSAR data is directly
related to the hardware and software design of an end item. The requiring
authority is responsible for specifying the equipment indenture level and the
level(s) of maintenance for which LSAR data will be prepared and maintained.
The LSAR data may be prepared and maintained manually, using the LSAR data
tables displayed in appendix A, or equivalent formats approved by the
requiring authority. It may also be prepared and maintained automatically
through use of current computer technology. The decision to automate the LSAR
data versus a manual LSAR must take into account the following factors:
a. Costs and schedules of preparation.
b. Availability of an ADP system.
c. Hardware complexity.
d. Acquisition/life cycle phase.
e. Requiring authority’s schedule requirements.

f. Design stability.
g. Compatibility with other LSAR preparers, as well as the requiring

authority’s ADP system.
h. Requiring authority involvement.

4.2.1 Manual LSAR data. While not preferred, the LSAR data may be prepared
and maintained in hard copy format by using the LSAR data tables displayed in
appendix A as guidelines for data groupings. When the LSAR data is prepared
and maintained manually, the data displayed on the LSAR tables shall be
grouped into LSAR data packages documenting individual reparable assemblies,
embedded computer software, and support/test equipment. The LSAR data
packages shall be sequenced by LCN. The data displayed on support equipment,
facilities, and new or modified skill requirements shall be included in the
applicable system/end item LSAR packages, or as directed by the requiring
authority. LSAR data displayed on the support item identification and
application data shall be sequenced by reference number and LCN within each
reference number.
4.2.1.1 Manual LSAR report generation. When required, any or all of the LSAR
reports contained in appendix B can be produced in a nonautomated environment.
When the LSAR reports are produced by nonautomated means, the reports shall be
in accordance with (IAW) the content, format, sequence, and computational
requirements contained in paragraph 30 of appendix B.

MIL-STD-1388-2B
4.2.2 Automated LSAR data. The LSAR data may be automated and, as such, a
validated LSAR ADP system shall be used as follows.
4.2.2.1 Performing activity LSAR ADP system. The performing activity shall
use a validated LSAR ADP system. Validation will be accomplished by the USAMC
Materiel: Readiness Support Activity (MRSA). The systems shall be capable of
fulfilling the basic criteria defined in paragraph 4.2.2.2 of this standard.
These systems shall be validated by exhibiting processing capability to input,
edit, and build LSAR relational tables and output the relational tables and
standard LSAR reports. Detailed validation procedures will be provide on
4.2.2.2 LSAR ADP system criteria. The independently developed LSAR ADP
system will be validated based on the following design criteria:
a. Shall be capable of automatically accepting relational table data in
the formats displayed in appendix A, using the data elements, definitions,
data element edits, data field lengths, and data relationships contained in
appendices A and E.
b. Shall be capable of producing LSAR reports as displayed in appendix B.
c. Shall be capable, as a minimum, of satisfying all appendix E data
elements.
d. Shall be capable of outputting LSAR ADP relational tables as displayed
in appendix A.
e. Shall be capable of outputting change only data from last delivery of
LSAR data.
f. Shall provide automated user comment capability.
These minimum design criteria are required to secure system validation.
Additional system automation is strongly encouraged.
5. DETAILED INSTRUCTIONS FOR AUTOMATED OR MANUAL PREPARATION OF LSAR
RELATIONAL TABLES. These instructions are applicable for either the automated
or manual preparation of the LSAR data. Each data table contained in
appendix A is identified by a three-position code. The first position of this
code identifies the functional area most directly associated with the
information contained within the data table. These codes are consistent with
the data record letter identifications used in the previous version of this
standard, e.g., support item identification is identified by an “H” in the
first position of the table code. The second position uniquely identifies the
table within a functional area. The third position may be used to insert
additional data tables at a later date.
5.1 Requiring authority data tables. Information in the “A” and portions of.
the “X” tables will be provided by the requiring authority and may be
incorporated with the solicitation, or addressed at the LSA\LSAR guidance
conference. This information will also be documented on the DD form 1949-3,
Figure 71.
5.1.1 Cross functional requirements. These data tables have attributes which
cross multiple functional areas or are used as a link to various functional

MIL-STD-1388-2B
data tables. The tables are used by the requiring authority to document
supply, maintenance and personnel data in support of tradeoff analysis. The
individual data elements may be used in conjunction with other LSA data in
several LSA models with only minor adjustment, if any, for compatibility of
units.
5.1.2 Operations and maintenance requirements. These tables are structured
to consolidate the pertinent information related to the anticipated operation
of the system, environment in which the system will be operated and
maintained, and the system maintenance requirements which must be met. This
information is prepared for the system, and for each subsystem for which
maintenance requirements are to be imposed, and will also be prepared for
government furnished equipment (GFE). When separate operational/maintenance
requirements are established for wartime and peacetime scenarios, each set of
requirements will be documented as separate table rows. The number of rows of
information that will be prepared shall be based on the tasks contained in
MIL-STD-1388-1, or as specified by the requiring authority. The performing
activity shall incorporate this information into the LSAR and shall complete
the appropriate key fields, unless the field has been completed by the
requiring authority. Detailed instructions for completion of this information
are contained in appendices A and E.
5.2 Performing activity data tables. The performing activity shall complete
the required fields of data tables “B”, “C”, and “E”, “F”, “G”, “H”, “J”, “U”
and portions of the “X” IAW the information contained in appendices A and E
and to the extent specified by DD Form 1949-3. When DEDs state that specific
information will be provided by the requiring authority, the information may
be included in the solicitation or not later than the LSA/LSAR guidance
conference.
5.2.1 Reliability, availability, maintainability; failure modes, effects, and

criticality analysis; and maintainability analysis. The “B” data tables
provide a description of the function of each item within the system; outline
the maintenance concept to be utilized for design and support planning
purposes; and, identify any design conditions such as fail-safe requirements/
environmental or nuclear hardness considerations imposed upon the system.
The tables summarize the reliability, maintainability, and related
availability characteristics of the item resulting from the failure modes and
effects, criticality, and maintainability analyses, and accommodates a
narrative description of any analysis related to the potential redesign of an
item. A separate row of information is prepared for the system, for each
subsystem contained in the system, and for each level of breakdown for that
subsystem until the lowest reparable item has been documented. The degree of
breakdown shall be specified by the requiring authority. Additional “B” data
tables are designed to accommodate the Failure Modes and Effects Analysis
(FMEA), as described by task 101 of MIL-STD-1629. These tables will also
accommodate the Damage Mode and Effects Analysis, to be utilized for
survivability and vulnerability assessments, as described in task 104 of
MIL-STD-1629, and accommodates the criticality and maintainability analyses,
as described in tasks 102 and 103 of MIL-STD-1629. The purpose of the
criticality analysis is to rank each identified failure according to the
combined influence of severity classification and failure probability of
occurrence. The relative ranking of the calculated item criticality numbers
highlights system high risk items. The maintainability analysis serves as the
starting point for maintenance task analysis. The FMEA documents the effects

MIL-STD-1388-2B
contractual and does not establish requirements. However, the guidance in

appendix C should be followed to ensure proper assignment of LCNs for a given
system/equipment, as this is critical for successful configuration management
and ILS product development.
5.4 LSA\LSAR guidance conference. The purpose of this conference is to
ensure the performing activity and requiring authority have a firm
understanding of the relationship of the LSA tasks to the LSA documentation,
task milestones, and funding levels contractually required. When a guidance
conference is not contractually specified and the performing activity desires
a conference, the performing activity shall propose a date and place. The
proposal shall be submitted within thirty (30) days after contract award. The
specific date and place for the guidance conference will be determined by-the
requiring authority and performing activity. The guidance provided to the
performing activity by the requiring authority may include, but shall not be
limited to, the following:
a. Performing activity inquiries relative to contractual LSAR
requirements.
b. Operational and maintenance concepts, i.e., program data.
c. Baseline logistics data, i.e., available skills, training programs,
tools , test equipment, and facilities.
d. Requirement for joint service validation of the performing activity
developed LSAR ADP system, when applicable.
e. Guidance relative to the use and application of LSAR data elements.
f. Review of the LSA candidate list.
6. NOTES. (This section contains information of a general or explanatory
nature that is helpful, but is not mandatory.)
6.1 Intended use. This standard contains requirements which are applicable
to the acquisition of military systems and equipment.
6.2 Issue of DODISS. When this standard is used in acquisition, the issue of
the DODISS to be applicable to this solicitation must be cited in this
solicitation (see 2.1).
6.3 Consideration of data requirements. The following should be considered
when this standard is applied on a contract. The applicable DIDs should be
reviewed in conjunction with the specific acquisition to ensure that only
essential data are requested/provided and that the DIDs are tailored to
reflect the requirements of the specific acquisition. To ensure correct
contractual application of the data requirements, a CDRL (DD Form 1423) must
be prepared to obtain the data, except where DOD FAR Supplement 27.475-1
exempts the requirement for a DD Form 1423. Refer to appendix D of this
standard for suggested tailoring guidance.
-17- REPRINTED WITHOUT CHANGE

MIL-STD-1388-2B
Paragraph Number DID Number DID Title
5.2 DI-ILSS-81173 Logistic Support Analysis Record (LSAR)

Data
Appendix B, 30.1 DI-ILSS-81138A LSA-001, Annual Man-Hours by Skill
Specialty Code and Level of Maintenance
Appendix B, 30.2 DI-ILSS-81139A LSA-003, Maintenance Summary
Appendix B, 30.3 DI-ILSS-81140A LSA-004, Maintenance Allocation Chart
Appendix B, 30.4 DI-ILSS-81141A LSA-005, Support Item Utilization Summary
Appendix B, 30.5 DI-ILSS-81142A LSA-006, Critical Maintenance Task Summary
Appendix B, 30.6 DI-ILSS-81143A LSA-007, Support Equipment Requirements
Appendix B, 30.7 DI-ILSS-81144A LSA-008, Support Items Validation Summary
Appendix B, 30.8 DI-ILSS-81145A LSA-009, Support Items List
Appendix B, 30.9 DI-ILSS-81146A LSA-010, Parts Standardization Summary
Appendix B, 30.10 DI-ILSS-81147A LSA-011, Requirements for Special Training
Device
Appendix B, 30.11 DI-ILSS-81148A LSA-012, Facility Requirements
Appendix B, 30.12 DI-ILSS-81149A LSA-013, Support Equipment Grouping Number
Utilization Summary
Appendix B, 30.13 DI-ILSS-81150A LSA-014, Training Task List
Appendix B, 30.14 DI-ILSS-81151A LSA-016, Preliminary Maintenance
Allocation Chart
Appendix B, 30.15 DI-ILSS-81152 LSA-018, Task Inventory Report
Appendix B, 30.16 DI-ILSS-81153A LSA-019, Task Analysis Summary
Appendix B, 30.17 DI-ILSS-81183A LSA-023, Maintenance Plan Summary
Appendix B, 30.18 DI-ILSS-80119C LSA-024, Maintenance Plan
Appendix B, 30.19 DI-PACK-80120 Preservation and Packing Data
Appendix B, 30.20 DI-ILSS-81154A LSA-026, Packaging Developmental Data
Appendix B, 30.21 DI-ILSS-81155A LSA-027, Failure/Maintenance Rate Summary
Appendix B, 30.22 DI-ILSS-81156A LSA-030, Indentured Parts Lists
Appendix B, 30.23 DI-ILSS-81286 Provisioning and other Preprocurement
Screening Data
Appendix B, 30.24 DI-ILSS-81157A LSA-033, Preventive Maintenance Checks
and Services (PMCS)
Appendix B, 30.25 DI-ILSS-81285 Provisioning Technical Documentation
Provisioning Parts List
Short Form Provisioning Parts List
Long Lead Time Items List
Repairable Items List
Interim Support Items List
Tools and Test Equipment List
Common and Bulk Items List
Design Change Notices
Post Conference List
System Configuration Provisioning List
Appendix B, 30.26 DI-ILSS-81158A LSA-037 Spares and Support Equipment
Identification List
Appendix B, 30.27 DI-ILSS-81159A LSA-039, Critical and Strategic Item
Summary
Appendix B, 30.28 DI-ILSS-81160A LSA-040, Authorization List Items Summary
Appendix B, 30.29 DI-ILSS-81161A LSA-046, Nuclear Hardness Critical Item
Summary
Appendix B, 30.30 DI-ILSS-81162A LSA-050, Reliability Centered Maintenance
Summary

MIL-STD-1388-2B
Appendix B, 30.31 DI-ILSS-81163A LSA-056, Failure Modes, Effects and
Criticality Analysis (FMECA) Report
Appendix B, 30.32 DI-ILSS-81164A LSA-058, Reliability and Maintainability
Analysis Summary
Appendix B, 30.33 DI-ILSS-81165A LSA-065, Manpower Requirements Criteria
Appendix B, 30.34 DI-ILSS-80118C LSA-070, Support Equipment Recommendation
Data (SERD)
Appendix B, 30.35 DI-ILSS-81166A LSA-071, Support Equipment Candidate List
Appendix B, 30.36 DI-ILSS-80288B LSA-072, Test, Measurement, and Diagnostic
Equipment (TMDE) Requirements Summary
Appendix B, 30.37 DI-ILSS-80289B LSA-074, Support Equipment Tool List
Appendix B, 30.38 DI-ILSS-80290B LSA-075, Consolidated Manpower, Personnel
and Training Report
Appendix B, 30.39 DI-ILSS-81167A LSA-076, Calibration and Measurement
Requirements Summary
Appendix B, 30.40 DI-ILSS-80291B LSA-077, Depot Maintenance Interservice
Data Summary
Appendix B, 30.41 DI-ILSS-81168A LSA-078, Hazardous Materials Summary
Appendix B, 30.42 DI-ILSS-81169A LSA-080, Bill of Materials
Appendix B, 30.43 DI-ILSS-81170A LSA-085, Transportability Summary
Appendix B, 30.44 DI-ILSS-81171A LSA-126, Hardware Generation Breakdown
Tree
Appendix B, 30.45 DI-ILSS-81287 LSA-151, Provisioning Parts List Index
Appendix B, 30.46 DI-ILSS-81172 LSA-152, PLISN Assignment/Reassignment
Appendix B, 30.47 DI-ILSS-80292B LSA-154, Provisioning Parts Breakout
Summary
Appendix B, 30.48 DI-ILSS-80293B LSA-155, Recommended Spare Parts List for
Spares Acquisition Integrated with
Production (SAIP)
The above DIDs were those cleared as of the date of this standard. The
current issue of DOD 5010.12-L, Acquisition Management Systems and Data
Requirements Control List (AMSDL), must be researched to ensure that only
current, cleared DIDs are cited on DD Form 1423.
6.4 Subject term (key word) listing.
Provisioning
CALS
Support equipment
Task analysis
Training
Transportability
6.5 Supersession data. This standard includes the requirements of

MIL-STD-1388-2A, dated 20 Jul 84.
6.6 Changes from previous issue. Marginal notations are used in this
revision to identify changes with respect to the previous issue.
-19/20 - Supersedes page 19/20 of 28 March 91

THIS PAGE INTENTIONALLY LEFT BLANK

MIL-STD-1388-2B
APPENDIX A
30.2.2.4 Data Element Code (CODE). A nine-position code, left-justified,
used to identify the DED. Each DED Code is unique within the table in which
the DED is listed. The DED Code cannot be changed or modified when
independently developing a relational LSAR ADP System. The last three
positions of the code are the table code. When a key migrates to a new table,
thus becoming a foreign key, it will retain the table code where the key
originated, unless the key is required to assume a “roll name” in the new
table. Origination of foreign keys which assume roll names are defined in the
business rules for the data table.
30.2.2.5 Data Element Title. The noun phrase used to identify the data
element. Sufficient modifiers are used with the noun name to ensure title
uniqueness for a specific data element definition.
30.2.2.6 Field Format. A specification for the length, type, positional
justification, and decimal placement of a data element field, or subfield
thereof, as described below:
a. Length. The number of character positions in the data element. In
the event the length is variable, the maximum length is specified.
b. Type. A specification of the character type, wherein:
“A” specifies that all characters of the data field, except narrative
fields, are upper case alphabetical.
“N” specifies that all characters of the data field are numerical.
“X” specifies that characters of the data field are upper case
alphabetical (except narrative fields), numerical, special, or any
combination thereof.
“D” specifies that characters of the data field are numerical with
floating decimal. Decimals may be entered as required or
exponentially, e.g., “0.0000325” or “3.25E-5”.
c. Justification. Specifies from which side of the field the characters
of the data element are entered. Those starting at the left are left
justified (L), those starting at the right are right justified (R); and, those
which always occupy the entire field are fixed (F). A dash (-) is used if
this column is not applicable.
d. Decimal Placement. Specifies the number of character positions to the

right of the assumed decimal point when the data element is numeric in all
character positions with a fixed decimal location. A dash (-) is used if this
column is not applicable. AS means “AS Specified” and the detailed
instructions will indicate the location of decimal points.
e. Field formats for extended narrative data fields are capable of
accepting a maximum of 99,999, 65-character lines, of information by means of
a text sequencing code.
30.2.2.7 DED Number. A sequentially assigned number to each data element in
the dictionary for use in locating and referencing it throughout the
dictionary and the relational data tables.

MIL-STD-1388-2B
APPENDIX A
30.2.2.8 Key Data Element Code (KEY). An indicator that identifies key and
mandatory data within a data table. The indicators are “F”, foreign key, “K”,
key, or “M”, mandatory, nonidentifying data element. Key data cannot have a
null value (unless specified in the business rules) when attempting to
establish a data row in a given data table.
30.2.2.9 Role Name. A unique modifier of a data element title which
describes the use/application of the data element within a specific relational
data table location.
30.3 LSAR Data Table Exchange/Delivery. Depending upon contractual language,

exchange/delivery of the LSAR data may take the form of full file replacement
or “change only” data (changes to the MIL-STD-1388-2B data tables since the
previous submittal of the LSAR data) . Both capabilities are required of
validated MIL-STD-1388-2B LSAR systems. Validated LSAR systems may employ
table upload edits differently; therefore, each system shall be responsible
for sorting tables of imported LSAR files as necessary to pass their table
upload edits. Also, LSAR data tables shall be exchanged/delivered via
variable length ASCII file formats. All data elements shall be positioned at
their respective offsets in the table row field. The following paragraphs
define the requirements to insure that automated LSAR systems will produce and
load standard outputs not only for all data tables (full file replacement),
but also standard outputs for “change only” data. Each type of transaction
shall be identified by the use of an update code (UC); multiple transactions
are possible for “change only” data delivery. The UC is not a data element
within each relational table; instead, the UC appends the appropriate table
row(s) identifying the transactions which have occurred.
30.3.1 Full file replacement. When providing an initial LSAR file delivery
or a full file replacement, a UC = * must be present for the appropriate row
of Table XA. The file structure for full file replacement is as follows:
The UC (*) identifies the type of transaction as being full file replacement
or initial delivery. The Table ID is XA in this case and the Table Row only
needs the key data element (EIAC) input. Each element of the transaction
shall be contiguous and without the vertical lines shown above.
30.3.2 Change only data delivery. “Change only” data delivery requires
multiple types of change transactions. Each type of change transaction is
listed below with its definition and appropriate UC.
a. Add Transaction - UC = A. The Add Transaction Code identifies that
the record to be loaded is a new record to be added to the respective table.
The appearance of an add implies that the key data elements do not already
exist in the table being accessed. However, those key data elements must
already exist in the prerequisite tables. The add record shall contain
required key fields and shall invoke a full record insert to specified table.
b. Delete Transaction - UC = D. The Delete Transaction Code identifies
the transaction record as a delete of an existing record pertaining to the
identified key data elements. If the table is prerequisite to another table
and there is data in the other table matching on the identified keys, this
transaction shall not delete the data in the specified table. A global delete
transaction (identified below) shall delete table records and associated
-24-
Supersedes page 24 of 28 March 91
MIL-STD-1388-2B
APPENDIX A
subordinate table records with respect to identified key data elements,
c. Element Change Transaction - UC - C. The appearance of an Element
Change Transaction Code for a given table and keys implies that data already
exists and: is being modified. An Element Change Transaction shall only
contain data in the key fields and the fields which are being modified. The
Element Change Transaction shall update only the specified data element(s).
d. Element Delete Transaction - UC - X. If deletion of one or more data
elements from a table is desired, each element will contain a “D” in the first
position of its respective table position. An Element Delete Transaction
shall also contain the appropriate key data for the specified data table. The
Element Delete Transaction shall delete only the specified data element(s).
e. Global Delete Transaction - UC - R. In the Global Delete Transaction,
the identified key data shall be deleted from the specified table as well as
from all tables which are subordinate to the specified table.
f. File Structure for Change Transactions A, D, C, X, and R. The
following file structure shall be used for the subject change transactions:
The UC (A, D, C, X, or R) identifies, the type of transaction. The Table ID is

the data table identification (i.e., XB, CA, etc.). The Table Row is self
explanatory for each type of transaction. Each element of the transaction
g. Key Field Change Transaction - UC -- K. In the Key Field Change

Transaction, the identified key data shall be changed in the specified table
as well as in all tables which are subordinate to the specified table. If a
key data element in the specified table has a foreign key identification, the
“Change To” key data element (see file structure in next paragraph) must be
established in the foreign key file (and other prerequisite files) before the
change can be implemented (e.g. , changing an existing LCN to a new LCN can
only be accomplished in Table XB, where LCN is first introduced as a key data
element) .
h. File Structure for Change Transaction K. The following file structure
shall be used for Key Field Change Transactions:
The UC (K) identifies the transaction as a Key Field Change Transaction. The
Table ID is the data table identification. The Table Row “Change From” Key
Values are the identified table key values which exist in the table and are to
be changed. The Table Row “Change To” Key Values are values to which all
applicable table keys are being changed. Each element of the transaction
30.3.2.1 Update code sort order. The order for the incorporation of change
transactions into a database is critical and shall be dependent upon the UC.
The UC sort order is R, K, D, X, A, and C,

MIL-STD-1388-2B
APPENDIX A
40. CROSS FUNCTIONAL REQUIREMENT. The following “X” data tables have
attributes which cross multiple functional areas or are used as a link to
various functional data tables. Included under these tables are the
functional and physical breakdown LCN, assignment and” application of UOCs,
technical manual numbers, and government provided level of repair analysis
(LORA) modeling information. Figure 4 depicts the key relationships for
these tables.
TABLE CODE TABLE TITLE
XA End Item Acronym Code
XB LCN Indentured Item

XC System/End Item
XD System/End Item Serial Number
XE LCN to Serial Number Usable On Code
XF LCN to System/End Item Usable On Code
XG Functional/Physical LCN Mapping
XH Commercial and Government Entity
XI Technical Manual Code and Number Index
40.1 Table XA, End Item Acronym Code. This table contains the EIAC
(EIACODXA) used to define the LSAR system documented in the relational
database. Also included in this table are LORA modeling parameters provided
by the requiring authority. When the classical or modified classical LCN
assignment is used (see Appendix C), then an entry is required in LCN
structure (LCNSTRXA).
CODE DATA ELEMENT TITLE FORMAT DED KEY
EIACODXA END ITEM ACRONYM CODE 10XL- 096 K

LCNSTRXA LCN STRUCTURE 18NL- 202
ADDLTMXA ADMINISTRATIVE LEAD TIME 2NR- 014
CTDLTMXA CONTACT TEAM DELAY TIME 3NR- 052
CONTNOXA CONTRACT NUMBER 19XL- 055
CSREORXA COST PER REORDER ACTION 4NR2 061
CSPRRQXA COST PER REQUISITION 4NR2 062
DEMILCXA DEMILITARIZATION COST 2NR- 077
DIS CNTXA DISCOUNT RATE 3NR2 083
ESSALVXA ESTIMATED SALVAGE VALUE 2NR- 102
HLCSPCXA HOLDING COST PERCENTAGE 2NR- 160
INTBINXA INITIAL BIN COST 4NR- 166
INCATCXA INITIAL CATALOGING COST 4NR- 167
INTWTXA INTEREST RATE 3NR2 173
INVSTGXA INVENTORY STORAGE SPACE COST 4NR2 176
LODFACXA LOADING FACTOR 3NR2 195
WSOPLVXA OPERATION LEVEL 2NR- 271

MIL-STD-1388-2B
APPENDIX A
a. The System/EI Identifier (SYSIDNXB) of “S” or “E” identifies LCNs as
representing System/EIs from table XB for entry into this table.
b. For identical PCCNS (PCCNUMXC), the UOCS (UOCSEIXC) must be
different.
c. All alternate assemblies of the same LCN must have the same PCCN.
I
CODE DATA ELEMENT TITLE FORMAT DED ~
EIACODXA END ITEM ACRONYM CODE IOXL- E F
LSACONXB LSA CONTROL NUMBER (LCN) 18XL- 199 F
ALTLCNXB ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXB LCN TYPE 1AF- 203 F
UOCSEIXC USABLE ON CODE 3XL- 501 M
PCCNUMXC SYSTEM/EI PROVISIONING CONTRACT 6XF- 307 M
CONTROL NUMBER
ITMDESXC SYSTEM/EI ITEM DESIGNATOR CODE 26XL- 179
PLISNOXC SYSTEM/EI PROVISIONING LIST ITEM 5XL- 309
SEQUENCE NUMBER
TOCCODXC SYSTEM/EI TYPE OF CHANGE CODE 1AF- 481
QTYASYXC SYSTEM/EI QUANTITY PER ASSEMBLY 4X-- 316
QTYPEIXC SYSTEM/EI QUANTITY PER END ITEM 5X-- 317
TIUJSEIXC TRANSPORTATION END ITEM 1AF- 467
INDICATOR
40.4 Table XD, System/End Item Serial Number. This table is only used when
parts configuration control is managed by serial numbers (S/N) of a system/EI.
It contains Serial Numbers applicable to a System/End Item, and if required,
Serial Number UOC assignments, e.g., for model V1O, identified in table XC,
applicable serial numbers may be 110 through 118, 121 and 125-130, while for
model V1OA, also identified in table XC, the applicable serial numbers may be
119, 122-124, and 131-150. For these serial number(s) specific serial number
UOCs may be assigned as follows:
Model Serial Number UOC Serial Number(s)
(ITMDESXC) ( SNUUOCXD) (FRSNUMXD) (TOSNUMXD)
V10 A 110 - 118
V10 B 121 - 121
V10 C 125 - 130
V1OA D 119 - 119
V1OA E 122 - 124
V1OA F 131 - 150
a. S/N From (FRSNUMXD) must be less than or equal to S/N To (TOSNUMXD).
b. S/N UOCs must be different for all EIAC, LCN, ALC and LCN Type
combinations within the same PCCN (pulled from table XC for subject
keys) .
EIACODXA END ITEM ACRONYM CODE 10XL- 096 F
MIL-STD-1388-2B
APPENDIX A
FRSNUMXD SERIAL NUMBER FROM 10XL- 373 K

TOSNUMXD SERIAL NUMBER TO 10XL- 373 K
SNUUOCXD SERIAL NUMBER USABLE ON CODE 3AL- 375 M
40.5 Table XE, LCN to Serial Number Usable On Code. This table contains LCN
and system/EI S/N LCNs in order to determine the associated S/N and SN UOCs
for the LCN. Table keys include all columns.
a. Table keys LSACONXE, ALTLCNXE, and LCNTYPXE migrate from table XB.
Table keys LCNSEIXE, ALCSEIXE, and LTYSEIXE migrate from table XD. EIACODXA
is identical for keys from tables XB and XD for a given row of data.
b. Rows of information from this table with LCNTYPXE and LTYSEIXE of “P”
must match entries in table HN, when this table is established.
LSACONXE S/N ITEM LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXE S/N ITEM ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXE S/N ITEM LCN TYPE 1AF- 203 F
LCNSEIXE S/N SYSTEM/EI LCN 18XL- 199 F
ALCSEIXE S/N SYSTEM/EI ALC 2NF- 019 F
LTSEIXE S/N SYSTEM/EI LCN TYPE 1AF- 203 F
FRSNUMXE S/N SERIAL NUMBER FROM 10XL- 373 F
TOSNUMXE S/N SERIAL NUMBER TO 10XL- 373 F
40.6 Table XF. LCN to System/End Item Usable On Code. This table contains
LCNs and System/EI LCNs in order to determine the associated UOC for the LCN.
This table and table HO (for provisioning) are critical to qualify an LCN for
report requests when a specific UOC is required for report selection. Table
keys include all columns.
a. Table keys LSACONXF, ALTLCNXF, and LCNTYPXF originate in table XB.
Table keys LCNSEIXF, ALCSEIXF, and LTYSEIXF migrate from table XC. EIACODXA
is identical for keys from tables XB and XC for a given row of data.
b. Rows of information from this table with LCNTYPXF and LTYSEIXF of “P”
must match entries in table HO, when this table is established.
EIACODM END ITEM ACRONYM CODE 10XL- 096 F
LSACONXF UOC ITEM LSA CONTROL NUMBER (LCN) 18 X L - 199 F
ALTLCNXF UOC ITEM ALTERNATE LCN CODE 2NF- 019 F
LCNTYPXF UOC ITEM LCN TYPE 1AF- 203 F
LCNSEIXF UOC SYSTEM/EI LCN 18XL- 199 F
ALCSEIXF UOC SYSTEM/EI ALC 2NF- 019 F
LTYSEIXF Uoc SYSTEM/EI LCN TYPE 1AF- 203 F
40.7 Table XG, Functional/Physical LCN Mapping. This table contains a cross-
listing of functional/physical LCNs. All data, except EIACODIM, originate in
REPRINTED WITHOUT CHANGE -30-

MIL-STD-1388-2B
APPENDIX A
measurement base (MB). There can be multiple tables depending upon the annual
operating requirements (AOR) MB. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and AOR (MEASBSAG). For a
given row of information, the following cross-element edits apply to table AG:
. a. AOR (ANOPREAG) and AOR MB (MEASBSAG) must either both be blank, or
have entries.
b. Reliability Operational Requirements Indicator (OPRQINAG) must match
Operational Requirements Indicator (OPRQINAB) in Table AB for the given keys.
The keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), and LCN
Type (LCNTYPXB).
EIACODXA END ITEM ACRONYM CODE 10XL- E Y
MEASBSAG ANNUAL OPERATING REQUIREMENT lAF- 238 K
MEASUREMENT BASE
ANOPREAG ANNUAL OPERATING REQUIREMENT 6NR- 023 M
OPRQINAG RELIABILITY 0PERATIONAL 1AF- 275 M
REQUIREMENTS INDICATOR
OPMTBFAG REQUIRED OPERATIONAL MEAN TIME 10D-- 229
BETWEEN FAILURES
TEMTBFAG REQUIRED TECHNICAL MEAN TIME 10D-- 229
BETWEEN FAILURES
OPMRBMAG REQUIRED OPERATIONAL MEAN TIME 10D-- 230
BETWEEN MAINTENANCE ACTIONS
TMTBMAAG REQUIRED TECHNICAL MEAN TIME 10D-- 230
MTBRXXAG REQUIRED MEAN TIME BETWEEN 10D-- 235
REMOVALS
50.8 Table AH, InteroperabilitY Requirement. This table identifies item

name, national stock number (NSN), and the TM of the system/equipment with
which the new system/equipment must be able to be transported by/interoperate
with. Table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB),
LCN Type (LCNTYPXB), Interoperable Item Name (IONAMEAH), and Interoperable
Item Number Type (IOINTYAH). For a given row of information, the following
cross-element edits apply to table AH:
a. Interoperable CAGE Number (IOCAGEAH) and Interoperable Reference
Number (IOREFNAH) must either both be blank, or both have entries.
b. Interoperable Item National Item Identification Number (IONIINAH) and
Interoperable Item NSN Federal Supply Classification (IONFSCAH) must either
both be blank, or both have entries.
EIACODXA END ITEM ACRONYM CODE 10XF- K T
MIL-STD-1388-2B
APPENDIX A
IONAMEAH INTEROPERABLE ITEM NAME 19XL- 182 K
IOINTYAH INTEROPERABLE ITEM NUMBER TYPE 1AF- 266 K
IOCAGEAH INTEROPERABLE CAGE CODE 5XF- 046
IOREFNAH INTEROPERABLE REFERENCE NUMBER 32XL- 337
IONIINAH INTEROPERABLE ITEM NATIONAL 9NF- 253
ITEM IDENTIFICATION NUMBER
IONFSCAH INTEROPERABLE ITEM NATIONAL 4NF- 253
STOCK NUMBER FEDERAL SUPPLY
CLASSIFICATION
IOITNMAH INTEROPERABLE ITEM TECHNICAL 30XL- 440
MANUAL NUMBER
50.9 Table AI, Modeling Data. This table documents maintenance level
specific information, for a given service designator code, to be used for LSA
modeling. Table keys consist of EIAC (EIACODXA), Modeling Service Designator
Code (SERDESAA), and Modeling O/M Level Code (OMLVLAI).
EIACODXA END ITEM ACRONYM CODE 10XF- G T
SERDESAI MODELING SERVICE DESIGNATOR 1AF- 376 K
CODE
OMLVLCAI MODELING OPERATIONS AND 1AF- 277 K
MAINTENANCE LEVEL CODE
LABRATAI LABOR RATE 4NR2 189
NOSHPSAI NUMBER OF SHOPS 2NR- 263
RPWSCSAI REPAIR WORK SPACE COST 4NR2 352
RQDSTKAI REQUIRED DAYS OF STOCK 3NR- 357
50.10 Table AJ, Operations and Maintenance Shipping Requirement. This table
identifies the O/M level from which a spare/repair part is shipped and the
O/M level which receives the part. Table keys consist of EIAC (EIACODXA),
LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), O/M Level From
(OMLVLFAJ), O/M Level To (OMLVLTAJ).
EIACODXA END ITEM ACRONYM CODE 10XL- K T
LSACONXB LSA CONTROL NUMBER (LCN) 18xL- 199 F
OMLVLFAJ OPERATIONS AND MAINTENANCE 1AF- 277 K
LEVEL FROM
OMLVLTAJ OPERATIONS AND MAINTENANCE 1AF- 277 K
LEVEL TO
SHPDISAJ SHIP DISTANCE 4NR- 085
TIMESHAJ SHIP TIME 3NR- 379
50.11 Table AK, System/End Item Narrative. This table may be used to
identify Additional Supportability Considerations, Additional Supportability
Parameters, and Operational Mission Failure Definition. Table keys consist of
EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB),
System/EI Narrative Code (SEINCDAK), and System/EI Narrative Text Sequencing
Code (TEXSEQAK).

MIL-STD-1388-2B
APPENDIX A
a. If the System/EI Narrative Code (SEINCDAK) is (B), then this
table provides a narrative description of additional supportability
considerations for the item under analysis (Additional Supportability
Considerations, DED 010).
b. If the System/EI Narrative Code (SEINCDAK) is (A), then this table
describes additional supportability parameters which will specify data
elements and associated data when discrete fields are not provided (Additional
Supportability Parameters, DED 011).
c. If the System/EI Narrative Code (SEINCDAK) is (C), then this table

provides a narrative of the guidelines to be followed when defining
operational mission failures (Operational Mission Failure Definition, DED 274).

EIACODXA END ITEM ACRONYM CODE 10XF- E T
SEINCDAK SYSTEM END ITEM NARRATIVE CODE 1AF- 424 K
TEXSEQAK SYSTEM END ITEM NARRATIVE TEXT 5NR- 450 K
SEQUENCING CODE
SEINAMK SYSTEM END ITEM NARRATIVE 65X-- ---

MIL-STD-1388-2B
APPENDIX A
60. ITEM RELIABILITY, AVAILABILITY, AND MAINTAINABILITY CHARACTERISTICS;
FAILURE MODES EFFECTS AND CRITICALITY ANALYSIS; AND, MAINTAINABILITY ANALYSIS.
Data tables beginning with “B” in the first position of the table code are
structured to provide a description of the function of-each item of the end
item; outline the maintenance concept to be utilized for design and support
planning purposes; and, identify any design conditions such as fail safe
requirements/environmental or nuclear hardness considerations imposed upon the
system. The tables summarize the item reliability, maintainability, and
related availability characteristics of the item resulting from the failure
modes and effects, criticality, and maintainability analyses, and accommodate
a narrative description of any analysis related to- the potential redesign or
an item. Figure 6 depicts the relational hierarchy of these tables/entities.
BA Reliability, Availability, and Maintainability Characteristics
BB Reliability, Availability, and Maintainability Characteristics
Narrative
BC Reliability, Availability, and Maintainability Logistics
Considerations
BD Reliability, Availability, and Maintainability Indicator
Characteristics
BE War/Peace Reliability, Availability, and Maintainability
Indicator Characteristics
BF Failure Mode and Reliability Centered Maintenance Analysis
BG Failure Mode and Reliability Centered Maintenance Narrative
BH Failure Mode Task
BI Failure Mode Indicator Mission Phase Code Characteristics
M Failure Mode Indicator Mission Phase Code Characteristics
Narrative
BK Reliability, Availability, and Maintainability Criticality
BL Mission Phase Operational Mode
60.1 Table BA, Reliability, Availability and Maintainability

Characteristics. This table contains logistics considerations, maintenance,
and reliability characteristics of the item under analysis. Table keys
consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), and LCN Type
(LCNTYPXB). For a given row of information, the following cross-element edits
apply to table BA:
The RAM area can only be used if a (Y) is entered in the RAM Indicator
(RAMINDXB) Table XB.

MIL-STD-1388-2B
APPENDIX A
FIGURE 6. B table relationships.
41 REPRINTED WITHOUT CHANCE

MIL-STD-1388-2B
APPENDIX A
b. Fault Isolation Percent Failure Group 1 (FIPFGABA) is not allowed
without Fault Isolation Ambiguity Group 1 (FIAMBABA).
c. The combination in (b) is not allowed without Built in Test (BIT)
Detection Level Percent group 1 (BDLPGABA).
d. That which applies for the combinations in Group 1 (b, c) also applies
to the combination in group 2.
e. Wearout Life (WEOULIBA) and Wearout Life MB (WOLIMBBA) must either
both be blank, or have entries.
EIACODXA END ITEM ACRONYM CODE 10XL- E T
MEQLINBA MINIMUM EQUIPMENT LIST 1AF- 243
INDICATOR
CONVFABA CONVERSION FACTOR 5N-- 059
FIAMBABA FAULT ISOLATION AMBIGUITY 2NR- 143
GROUP 1
FIPFGABA FAULT ISOLATION PERCENT FAILURE 3NR1 143
GROUP 1
BDLPGABA BUILT IN TEST DETECTABILITY 2NR- 032
LEVEL PERCENTAGE PER GROUP 1
FIAMBBBA FAULT ISOLATION AMBIGUITY 2NR- 143
GROUP 2
FIPFGBBA FAULT ISOLATION PERCENT FAILURE 3NR1 143
GROUP 2
BDLPGBBA BUILT IN TEST DETECTABILITY 2NR- 032
LEVEL PERCENTAGE PER GROUP 2
BITNDPBA BUILT IN TEST CANNOT DUPLICATE 2NR- 031
PERCENTAGE
BITROPBA BUILT IN TEST RETEST OK PERCENT 2NR- 033
FRDATABA FAILURE RATE DATA SOURCE 32X-- 141
PREOVCBA PILOT REWORK OVERHAUL 1AF- 292
CANDIDATE
SECCLEBA SECURITY CLEARANCE 1NF- 369
SUPCONBA SUPPORT CONCEPT 1AF- 410
WEOULIBA WEAROUT LIFE 6NR- 505
WOLIMBBA WEAROUT LIFE MEASUREMENT BASE 1AF- 238
LOGSTABA LOGISTIC CONSIDERATIONS 1AF- 196
STANDARDIZATION
LOGACCBA LOGISTIC CONSIDERATIONS 1AF- 196
ACCESSIBILITY
LOGMAIBA LOGISTIC CONSIDERATIONS 1AF- 196
MAINTENANCE EASE
LOGSAFBA LOGISTIC CONSIDERATIONS SAFETY 1AF- 196
LOGTEPBA LOGISTIC CONSIDERATIONS TEST 1AF- 196
POINTS
LOGSKIBA LOGISTIC CONSIDERATIONS SKILLS 1AF- 196
LOGTRABA LOGISTIC CONSIDERATIONS 1AF- 196
TRAINING
LOGCONBA LOGISTIC CONSIDERATIONS 1AF- 196
-42-
MIL-STD-1388-2B
APPENDIX A
CONNECTORS
LOGPATBA LOGISTIC CONSIDERATIONS 1AF- 196
PACKAGING AND TRANSPORTATION
LOGFLOBA LOGISTIC CONSIDRATION FAULT 1 AF - 196
LOCATION
LOGLABBA LOGISTIC CONSIDERATIONS 1AF- 196
LABELING
LOGDSPBA LOGISTIC CONSIDERATIONS DESIGN 1AF- 196
FOR SELF PROTECTION
LOGCRCBA LOGISTIC CONSIDERATIONS 1AF- 196
CORROSION/RUST CONTROL
60.2 Table BB, Reliability, Availability, and Maintainability Characteristics

Narrative. This table may be used to identify RAM Item Functions, RAM
Maintenance Concepts, RAM Minimum Equipment List, and RAM Qualitative and
Quantitative Maintainability Requirements. Table keys consist of EIAC
(EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), RAM
Characteristics Narrative Code (RAMCNABB), and RAM Narrative Text Sequencing
Code (TEXSEQBB). For a given row of information, the following cross-element
edits apply to table BE:
a. If the RAM Characteristics Narrative Code (RAMCNABB) is (A), then this
table identifies the function, specification, and tolerances of the item under
analysis (RAM Item Function, DED 180).
b. If the RAM Characteristics Narrative Code (RAMCNABB) is (B), then this
table describes the broad, planned approach to be employed in sustaining the
system/equipment at a defined level of readiness, or in a specified condition
in support of the operational requirement (RAM Maintenance Concept, DED 207).
c. If the RAM Characteristics Narrative Code (RAMCNABB) is (C), then this
table specifies any limitations on the end item when dispatched on its
assigned mission with the item under analysis inoperative (RAM Minimum
Equipment List Narrative, DED 244). RAM Minimum Equipment List Narrative
(MEQIJWIBB) is not allowed without a (y) selected in table BA for the attribute
RAM Minimum Equipment List Indicator (MEQLINBA).
d. If the RAM Characteristics Narrative Code (RAMCNABB) is (D), then this
table describes the maintainability design constraints and characteristics
that must be considered during the design process, to include fail safe
requirements, environmental considerations, and nuclear hardened
characteristics (RAM Qualitative and Quantitative Maintainability
Requirements, DED 315).
e. If the RAM Characteristics Narrative Code (RAMCNABB) is (E), then this
table describes the support data and analysis used in preparation of the
maintenance plan (Maintenance Plan Rationale, DED 210).
EIACODXA END ITEM ACRONYM CODE 10XL- K T

MIL-STD-1388-2B
APPENDIX A
RAMCNABB RELIABILITY AVAILABILITY AND 1AF- 341 K

MAINTAINABILITY (RAM)
CHARACTERISTICS NARRATIVE
CODE
TEXSEQBB RAM CHARACTERISTICS NARRATIVE 5NR- 450 K
TEXT SEQUENCING CODE .
RAMNARBB RAM CHARACTERISTICS NARRATIVE 65 X -- ---
60.3 Table BC, Reliability, Availability, and Maintainability Logistics

Considerations. This table contains narrative information associated with
logistics considerations. Table keys consist of EIAC (EIACODXA), LCN
(LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), Logistics Consideration Code
(IXICOCOBC), and RAM Logistics Considerations Text Sequencing Code (TEXSEQBC).
EIACODXA END ITEM ACRONYM CODE 10XL- 096 T
LOCOCOBC LOGISTICS CONSIDERATION CODE 1XF- 425 K
TEXSEQBC RELIABILITY AVAILABILITY AND 5NR- 450 K
MAINTAINABILITY (RAM)
LOGISTICS CONSIDERATIONS TEXT
SEQUENCING CODE
IDGNARBC RAM LOGISTICS CONSIDERATIONS 65X-- 426
60.4 Table BD, Reliability, Availability, and Maintainability Indicator

Characteristics. This table contains reliability and maintainability
characteristics of the item under analysis categorized by comparative
analysis, allocated, predicted, or measured values. Table keys consist of
EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type (LCNTYPXB), and
RAM Indicator Code (RAMINDBD). For a given LCN, ALC, and LCN Type
combination, each different measurement base must remain constant for all RAM
Indicator Codes (RAMINDBD). For a given row of information, the following
cross-element edits apply to table BD:
a. Failure Rate (FAILRTBD) and Failure Rate MB (FARAMBBD) must either
b. Percentile (PERCENBD) is not allowed without a Maximum Time to Repair
(MAXTTRBD).
c. Mean Time Between Failures Operational (OPMTBFBD) and Mean Time
Between Failures Operational MB (OM’SBF!4BD) must either both be blank, or have
entries.
d. Mean Time Between Failures Technical (TEMTBFBD) and Mean Time Between
Failures Technical MB (TMTBFMBD) must either both be blank, or have entries.
e. Mean Time Between Maintenance Actions Operational (OMTBMABD) and Mean

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

MIL-STD-1388-2B
APPENDIX A
b. Unscheduled task codes, task interval codes of “F”, “G”, or “J” (2d
position of the task code), must have an MB entered which corresponds to the
MB for the AOR. For this reason, the AOR LCN (AORLCNCA), AOR ALC (AORALCCA),
AOR LCN Type (AORTYPCA), and the AOR MB (AORMSBCA) must match with a set of
by values already established in Table AG.
c. Every Task Code (TASKCDCA) must have a Task ID (TASKIDCA).
d. Secondary Means of Detection (SMDTECCA) is not allowed without Primary
Means of Detection (PMDTECCA).
e. Up to three Performance Standards (PRSTDACA, PRSTDBCA, PRSTDCCA) and
Task Conditions (TCONDACA, TCONDBCA, TCONDCCA) can be entered for a given
record.
f. Every task code requires a corresponding task frequency.
g. If the Facility Requirement Code (FTRNRQCA) is “Y”, the Facility

tables (F tables) should be addressed.
h. Up to four Training Location Rationale (TRNLOCCA) codes may be entered
for each unique combination of LCN, EIAC, ALC, LCN Type, and task code (codes
must be entered in a continuous string).
i. Up to four Training Rationale (TRNRATCA) codes may be entered for each
unique combination of LCN, EIAC, ALC, LCN Type and task code (codes must be
entered in a continuous string).
j. Measured Mean Man-Hours (MSDMMHCA) are calculated by summing the Mean

Man-Minutes (SUBMMMCD) per Person ID for the given task (see DED 225) and
dividing by 60.
k. Measured Mean Elapsed Time (MSDMETCA) is calculated by summing the
Mean Minute Elapsed Times (SBMMETCB) for all subtasks of a task (see DED 225)
and dividing by 60.
l. Task Frequency (corrective) shall be calculated based on Failure Mode
Ratio (Table BF), Failure Rate (Table BD), Mean Time Between Maintenance
Induced (Table BD), Mean Time Between Maintenance No Defect (Table BD),
Conversion Factor (Table BA), and Annual Operating Requirements (Table AG).
Task Frequency (preventive) shall be calculated based on Annual Operating
Requirements (Table AG), Conversion Factor (Table BA), Maintenance Interval
(Table BH), or Task Interval Code (Table CA). A change in any of these
variables shall result in an update of Task Frequency (Table CA).
TASKCDCA TASK CODE 7XF- 427 K
REFEIACA REFERENCED END ITEM ACRONYM CODE 10 X L - 096

MIL-STD-1388-2B
APPENDIX A
REFLCNCA REFERENCED LCN 18XL- 199
REFALCCA REFERENCED ALTERNATE LCN CODE 2XL- 019
REFTYPCA REFERENCED LCN TYPE 1AF- 203
REFTSKCA REFERENCED TASK CODE 7XF- 427
AORLCNCA ANNUAL OPERATING REQUIREMENT 18XL- 199
(AOR) LCN
AORALCCA AOR ALC 2NF- 019
AORTYPCA AOR LCN TYPE 1AF- 203
AORMSBCA TASK AOR MEASUREMENT BASE 1AF- 238
TASKIDCA TASK IDENTIFICATION 36XL- 431
TSKFRQCA TASK FREQUENCY 7NR4 430
TSKCRCCA TASK CRITICALITY CODE 1AF- 429
HRDCPCCA HARDNESS CRITICAL PROCEDURE CODE 1AF- 152
HAZMPCCA HAZARDOUS MAINTENANCE 1AF- 155
PROCEDURES CODE
PMCSIDCA PREVENTIVE MAINTENANCE CHECKS 1AF- 296
AND SERVICES INDICATOR CODE
MSDMETCA MEASURED MEAN ELAPSED TIME 5NR2 224
PRDMETCA PREDICTED MEAN ELAPSED TIME 5NR2 224
MSDMMHCA MEASURED MEAN MAN HOURS 5NR2 225
PRDMMHCA PREDICTED MEAN MAN HOURS 5NR2 225
PMDTECCA PRIMARY MEANS OF DETECTION 1AF- 237
SMDTECCA SECONDARY MEANS OF DETECTION 1AF- 237
FTRNRQCA FACILITY REQUIREMENT CODE 1AF- 358
TRNRQCCA TRAINING EQUIPMENT REQUIREMENT 1AF- 358
CODE
TRNRECCA TRAINING RECOMMENDATION TYPE 1AF- 463
TRNLOCCA TRAINING LOCATION RATIONALE 4AL- 461
TRNWTCA TRAINING RATIONALE 4AL- 462
TSEREQCA TOOL/SUPPORT EQUIPMENT 1AF- 358
REQUIREMENT CODE
PRSTDACA TASK PERFORMANCE STANDARD A 1AF- 287
PRSTDBCA TASK PERFORMANCE STANDARD B 1AF- 287
PRSTDCCA TASK PERFORMANCE STANDARD C IAF- 287
TCONDACA TASK CONDITION A IAF- 428
TCONDBCA TASK CONDITION B IAF- 428
TCONDCCA TASK CONDITION C IAF- 428
70.2 Table CB, Subtask Requirement. This table contains data related to the
subtask level such as Work Area Code and Mean Minute Elapsed Time. All task
narrative will be written at the subtask level, then rolled into the task
level. It is possible to reference subtask descriptions within this table.
Table keys consist of LCN (LSACONXB), LCN Type (LCNTYPXB), ALC (ALTLCNXB),
EIAC (EIACODXA), Task Code (TASKCDCA), and Subtask Number (SUBNUMCB).
For referencing purposes, Referenced Subtask Number (RFDSUBCB),

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

MIL-STD-1388-2B
APPENDIX A
NOTE: Every Task Remark Reference Code and Task Remark combination is unique
across all rows of information for a given EIAC. In other words, for the same
EIAC, a given Task Remark Reference Code can only correspond to one Task
Remark statement throughout the file structure.
TSKRRCCE TASK REMARK REFERENCE CODE 2XF- 349 K
TSKREMCE TASK REMARK 240 X - 432
70.6 Table CF, Task Remark Reference. This table serves as a tie-in table
between the TASK REQUIREMENT table (CA) and the TASK REMARK table (CE). Table
keys consist of LCN (LSACONXB), LCN Type (LCNTYPXB), ALC (ALTLCNXB), EIAC
(EIACODXA), and Task Code (TASKCDCA), which are migrated from table CA and the
Task Remark Reference Code (TSKRRCCE), which migrates from table CE. EIACODXA
from tables CA and CE must always be identical, therefore, duplication of that
key in this table is not needed.
TASKCDCA TASK CODE 7XF- 427 F
TSKRRCCE TASK REMARK REFERENCE CODE 2XF- 349 F
70.7 Table CG, Task Support Equipment. This table contains information which
relates data needed for the task under analysis to the Support Equipment (SE)
tables . This table serves as the tie-in between Task Analysis and SE areas
for data which is to be incorporated into the LSA-070 series of reports (e.g.,
LSA-070, 072, 074, etc.). Table keys consist of LCN (LSACONXB), LCN Type
(LCNTYPXB), ALC (ALTLCNXB), EIAC (EIACODXA), Task Code (TASKCDCA), Task
Support Reference Number (TSFEFNCG), and Task Support CAGE Code (TSCAGECG).
a. In a given row, Quantity Per Task and Quantity Per Task Unit of
Measure must either both be blank, or both have entries.
b, Based on the definitions for Item Category Codes (ICC) (DED 177), it
is recommended that only items which fall under the following ICCs (identified
in table EA by SEICCDEA) be entered in this table: 7, 8, M, D, 1, H, 4, 5, 6,
2, G, N, P, R, 3, S, T, E, F, J, U, V, AC, AD, and AF.
c. If the Training Equipment Requirement Code (TRNRQCCA) in table CA is
“Y” for the subject LCN, ALC, and Task Code, at least one item of support
equipment identified by the Task Support Reference Number (TSREFNCG) must have
an ICC (SEICCDW) of “S”, “T”, or “AF” entered against it in the EA table
(match TSREFNCG and TSCAGECG with SEREFNEA and SECAGEEA, then check ICC).

-59-
MIL-STD-1388-2B
APPENDIX A

TSCAGECG TASK SUPPORT CAGE CODE 5XF- 046 F
TSREFNCG TASK SUPPORT REFERENCE NUMBER 32XL- 337 F
SQTYTKCG SUPPORT ITEM QUANTITY PER TASK 5NR2 319
SQTKUMCG SUPPORT ITEM QUANTITY PER TASK 2AF- 491
UNIT OF ME4SURE
70.8 Table CH, Task Manual. This table ties in the narrative for the task
under analysis to the corresponding Technical Manual (TM) which will contain
the narrative. Table keys consist of LCN (LSACONXB), LCN Type (LCNTYPXB), ALC
(ALTLCNXB), EIAC (EIACODXA), Task Code (TASKCDCA), and TM Code (TMCODEXI).
CODE DATA ELEMENT TITLE Format DED KEY

TMCODEXI TECHNICAL MANUAL CODE 3XF- 437 F
70.9 Table CI, Task Provisioned Item. This table will be used to obtain data
from the Task Analysis area, which will be used in determining provisioning
technical factors. In other words, this table links the provisioning area
directly to the task area. This table should be used for documenting spares
and repair parts needed in support of the subject task. Table keys consist of
Task LCN (TSKLCNCI), Task LCN Type (TSKLTYCI), Task ALC (TSKALCCI), and Task
Provison Task Code (TSKTCDCI), which are migrated from table CA and Task
Provision LCN (PROLCNCI), Task Provision ALC (PROALCCI), Task Provision LCN
Type (PROLTYCI), Task Provision CAGE Code (PROCAGCI), and Task Provision
Reference Number (PROREFCI), which migrate from table HG. The EIACS
(EIACODXA), which are resident in tables CA and HG, must be identical.
a. In a given row, Quantity Per Task and Quantity Per Task Unit of
Measure must either both be blank, or both have entries.
b. For task code functions (lst position of Task Code) of H, there must
be one Task Provision LCN that matches the Task LCN for all items required to
support subject task (i.e., remove/replace of that LCN).
c. Based on definitions for ICCS (DED 177), it is recommended that only

items which fall under the following ICCS be entered in this table (identified
in table HG by ITMCATHG): Q, W, X, Y, Z, 9, K, L, M, AB, AD, and AE.
EIACODXA END ITEM ACRONYM CODE 10XL 096 F

TSKLCNCI TASK LSA CONTROL NUMBER (LCN) 18XL 199 F
TSKALCCI TASK ALTERNATE LCN CODE (ALC) 2NF 019 P

MIL-STD-1388-2B
APPENDIX A
TSKLTYCI TASK LCN TYPE 1AF 203 F

TSKTCDCI TASK PROVISION TASK CODE 7XF 427 F
PROCAGCI TASK PROVISION CAGE CODE 5XF 046 F
PROREFCI TASK PROVISION REFERENCE NUMBER 32 X L 337 F
PROLdNCI TASK PROVISION LCN 18XL 199 F
PROALCCI TASK PROVISION ALC 2NF 019 F
PROLTYCI TASK PROVISION LCN TYPE 1AF 203
PQTYTKCI PROVISION QUANTITY PER TASK 5NR2 319 F
PQTKUMCI PROVISION QUANTITY PER TASK 2AF 491
UNIT OF MEASURE
70.10 Table CJ, Job and Duty Assignments. This table should be used to
document jobs and duties personnel perform in a system. Documentation in this
table is required if the Task Inventory report (LSA-018) is to be processed.
Key data elements are Job Code (JOBCODCJ) and Duty Code (DUTYCDCJ).
JOBCODCJ JOB CODE 2XL- 186 K

DUTYCDCJ DUTY CODE 4XL- 091 K
JOBDESCJ JOB 40XL- 185
DUTIESCJ DUTY 240XL- 090
70.11 Table CK, Task Inventory. This table is used as a cross reference
to produce the Task Inventory report (LSA-018). Tables CC, CD, and CJ are
combined in this cross reference table to identify the tasks, subtasks, and
elements that are required for a given Job and Duty. Table keys include all
columns. EIACODXA, LSACONXB, ALTLCNXB, LCNTYPXB, TASKCDCA, and SUBNUMCB must
be identical for tables CC and CD, migrating SUBPIDCD. Text Sequence Code
From (TSFROMCK) and Text Sequence Code To (TEXTTOCK) migrate from TEXSEQCC,
and therefore, each must match with a TEXSEQCC value for the given subtask.
a. JOBCODCJ and DUTYCDCJ must exist in table CJ prior to table CK.
b. For a given task, Job Code (JOBCODCJ) must have a unique Person ID
(SUBPIDCD).
JOBCODCJ JOB CODE 2XL- 186 F

DUTYCDCJ DUTY CODE 4XL- 091 F
SUBNUMCB SUBTASK NUMBER 3NF- 407 F
TSFROMCK SEQUENTIAL SUBTASK DESCRIPTION 5NR 450 F
TEXT SEQUENCING CODE FROM
TEXTTOCK SEQUENTIAL SUBTASK DESCRIPTION 5NR 450 F
TEXT SEQUENCING CODE TO
SUBPIDCD SUBTASK PERSON IDENTIFIER 3XL- 288 F

MIL-STD-1388-2B
APPENDIX A
80. SUPPORT EQUIPMENT AND TRAINING MATERIEL REQUIREMENTS. Data tables
identified, by an “E” in the first position of the table code are structured to
consolidate the pertinent information related to existing or new support/test
equipment; or training equipment. These tables contain most of the data that
was captured on the old “E and El” records. Much of this information series
as administrative type data for the Support Equipment Recommendation Data
(SERD) report. This information also series as identification of hardware and
software elements required to conduct off-line tests. Figure 8 provides an
entity diagram of these tables.
EA Support Equipment
EB Allocation Data
EC Support Equipment Parameters
ED Support Equipment Authorization
EE Support Equipment Narrative

EF Support Equipment Recommendation Data
EG Support Equipment Recommendation Data Revision Remarks
EH Alternate National Stock Numbers

EI Input Power Source
EJ Support Equipment Design Data
EK Supersedure Data
EL Support Equipment Integrated Logistic Support

Requirement Category Code
EM System Equipment
80.1 Table EA, Support Equipment. This table captures a large portion of
data which occurs one time per support/training equipment item. This table is
used as the foundation for support/training equipment documentation as a
whole. Table keys are Support Equipment (SE) Reference Number (SEREFNEA) and
SE CAGE Code (SECAGEEA).
a. If Adapter/Interconnection Device Required (AIDRQDEA) is “Y”, tables
UI and UJ must be completed.
b. If entries exist for Operating Dimensions or Weight, Storage
Dimensions or Weight, or Support Equipment Shipping Dimensions or Weight,
their respective units of measure must have entries also.
c. Up to eight Using Service Designator Codes (USESEREA) can be entered

at one time in a continuous string. This capability allows for all possible

MIL-STD-1388-2B
APPENDIX A
FIGURE 8. E table relationships.
63 REPRINTED WITHOUT CHANGE

MIL-STD-1388-2B
APPENDIX A
combinations of using services to be entered.

SECAGEEA SUPPORT EQUIPMENT CAGE CODE 5XF 046 F

SEREFNEA SUPPORT EQUIPMENT REFERENCE 32XL 337 F
NUMBER
FLITNMEA SUPPORT EQUIPMENT FULL ITEM 42XL 412
NAME
SEICCDEA SUPPORT EQUIPMENT ITEM CATEGORY 2XL 177
CODE
AQDCOFEA ACQUISITION DECISION OFFICE 15XL 002
ENDARTEA END ARTICLE ITEM DESIGNATOR 26X- 179
AIDRQDEA ADAPTOR/INTERCONNECTION DEVICE 1AF 005
REQUIRED
DATFADEA DATE OF FIRST ARTICLE DELIVERY 6NF 071
CALINTEA CALIBRATION INTERVAL 2NR 037
CALITMEA CALIBRATION ITEM 1AF 038
CALRQDEA CALIBRATION REQUIRED 1AF 040
CALSTDEA CALIBRATION STANDARD 1AF 041
CALTIMEA CALIBRATION TIME 5NR1 042
CMRSRCEA CALIBRATION MEASURMENT 1AF 035
REQUIREMENT SUMMARY RECOMMEND
CNTRNOEA SUPPORT EQUIPMENT CONTRACT 19XL 055
NUMBER
CFEGFEEA CONTRACTOR FURNISHED EQUIPMENT/ 1AF 056
GOVERNMENT FURNISH EQUIPMENT
CUSTCDEA CUSTODY CODE 1AF 069
DRWCLSEA DRAWING CLASSIFICATION 3X-- 088
ECOANLEA ECONOMIC ANALYSIS 1AF 093
FAMGRPEA FAMILY GROUP 10XL 142
GENECDEA GENERIC CODE 5XL 148
GOVDESEA GOVERNMENT DESIGNATOR 20XL 149
HDWRPREA HARDWARE DEVELOPMENT PRICE 8NR- 153
ILSPRCEA INTEGRATED LOGISTIC SUPPORT 8NR- 170
PRICE
DSNPRCEA DESIGN DATA PRICE 8NR- 080
EXUNPREA EXTENDED UNIT PRICE 8NR- 103
PASTHREA PASS THRU PRICE 8NR- 285
OSCOSTEA OPERATING AND SUPPORT COST 8NR- 267
RCURCSEA RECURRING COST 8NR- 332
LICYSTEA LIFE CYCLE STATUS 1AF 190
LIFSPNEA LIFE SPAN 2NR 191
UCTCDEA LOGISTIC CONTROL CODE 1AF 197
LGDCOFEA LOGISTICS DECISION OFFICE 15XL 198
LSARCDEA LSA RECOMMENDATION CODE 1AF 204
MGTPLNEA MANAGEMENT PLAN 1AF 216
MGCOATEA MANAGING COMMAND/AGENCY 10XL 217
SEMTBFEA SUPPORT EQUIPMENT MEAN TIME 10D-- 229
-
BETWEEN FAILURES
SMTBMAEA SUPPORT EQUIPMENT MEAN TIME 10D-- 230
SEMTTREA SUPPORT EQUIPMENT MEAN TIME 5NR2 236
TO REPAIR
-64-
MIL-STD-1388-2B
APPENDIX A
MOBFACEA MOBILE FACILITY CODE 1AF 248

MODCHGEA MODIFICATION OR CHANGE 1AF 252
OPRHGTEA OPERATING HEIGHT 4NR1 268
OPLENGEA OPERATING LENGTH 4NR1 268
OPWIDTEA OPERATING WIDTH 4NR1 268
OPRWGTEA OPERATING WEIGHT 6NR1 270
LWHOUMEA OPERATING DIMENSIONS UNIT OF 2AF- 491
MEASURE
WGTOUMEA OPERATING WEIGHT UNIT OF 2AF- 491
MEASURE
PCBLVLEA PRINTED CIRCUIT BOARD REPAIR 1AF 277
OPERATIONS/MAINTENANCE LEVEL
CALLVLEA SUPPORT EQUIPMENT CALIBRATION 1AF 277
RPRLVLEA SUPPORT EQUIPMENT (SE) REPAIR 1AF 277
SMRCSEEA SE SOURCE, MAINTENANCE AND 6XL- 389
RECOVERABILITY CODE
TMRQCDEA TECHNICAL MANUAL REQUIRED CODE 17XL 441
OPRMANEA OPERATORS MANUAL 16XL 278
SSCOPREA SKILL SPECIALTY CODE FOR SUPPORT 7XL 387
EQUIPMENT OPERATOR
PREATYEA PREPARING ACTIVITY 25XL 294
PROELEEA PROGRAM ELEMENT 3XL 301
PSICPOEA PROGRAM SUPPORT INVENTORY 2XF 303
CONTROL POINT
SERICCIZA REPORTABLE ITEM CONTROL CODE 1NF 356
REVASSEA REVOLVING ASSETS 4XF 361
SLFTSTEA SELF TEST CODE 1AF 370
SENTRAEA SENSORS OR TRANSDUCERS 1AF 371
SERDESEA SE SERVICE DESIGNATOR 1AF 376
USESEREA USING SERVICE DESIGNATOR CODE 8AL 376
SKETCHEA SKETCH 1AF 383
SPRFACEA SPARE FACTOR 4XF 390
SPMGNTEA SPECIAL MANAGMENT CODE 1AF 393
SIASCNEA STANDARD INTERSERVICE AGENCY 7XF 401
SERIAL CONTROL NUMBER
STOHGTEA STORAGE HEIGHT 4NR1 405
STOLENEA STORAGE LENGTH 4NR1 405
STOWDTEA STORAGE WIDTH 4NR1 405
STOWGTEA STORAGE WEIGHT 6NR1 406
LWHSUMEA STORAGE DIMENSIONS UNIT OF 2AF- 491
MEASURE
WGTSUMEA STORAGE WEIGHT UNIT OF MEASURE 2AF- 491
SESHPHEA SUPPORT EQUIPMENT SHIPPING 4NR1 419
HEIGHT
SESHPLEA SUPPORT EQUIPMENT SHIPPING 4NR1 419
LENGTH
SESHPWEA SUPPORT EQUIPMENT SHIPPING 4NR1 419
WIDTH
SESHWTEA SUPPORT EQUIPMENT SHIPPING 6NR1 420
WEIGHT
UMSHIPEA SUPPORT EQUIPMENT SHIPPING 2AF- 491
DIMENSIONS UNIT OF MEASURE

MIL-STD-1388-2B
APPENDIX A
UMSEWTEA SUPPORT EQUIPMENT SHIPPING 2AF- 491
WEIGHT UNIT OF MEASURE
$EGRCDEA SUPPORT EQUIPMENT GROUPING 3NF 413
SEREQDEA SUPPORT EQUIPMENT REQUIRED 1AF 418
TECEVLEA TECHNICAL EVALUATION PRIORITY 3XF 435
CODE
TSTLNGEA TEST LANGUAGE 6AL 443
TSTPTSEA TEST POINTS 1AF 446
TMDERCEA TEST MEASUREMENT AND DIAGNOSTIC 1AF 444
EQUIPMENT REGISTER CODE
TMDERIEA TEST MEASUREMENT AND DIAGNOSTIC 7XF 445
EQUIPMENT REGISTER INDEX
NUMBER
TYPCLSEA TYPE CLASSIFICATION 1AF 479
TYPEEQEA TYPE EQUIPMENT CODE 4XL 480
YRFLDGEA YEAR OF FIELDING 2NF 518
80.2 Table EB, Allocation Data. This table allows documenting of specific
information relating allocation documents to discrete facility types and
maintenance levels. Ten allowance ranges can be documented to describe the
quantity of SE or Automatic Test Equipment (ATE) items necessary to support
the number of end articles related to each discrete range of supported end
item density. DED 015 dictates the value of each range for the number of
pieces of: (a) end items; (b) ATE items; or, (c) depot overhaul requirements
that the entered quantity of SE can support. Table keys are SE Reference
Number (SEREFNEA), SE CAGE Code (SECAGEEA), and Allowance Document Number
(ALDCNMEB).
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5XF 046 F
SEREFNEA SE REFERENCE NUMBER 32XL 337 F
ALDCNMEB ALLOWANCE DOCUMENT NUMBER 10XL 016 K
ALORG1EB ALLOWABLE RANGE 1 3NR- 015
ALRG10EB ALLOWABLE RANGE 10 3NR- 015
ALDNDSEB ALLOCATION DESIGNATION 9XL 015
DESCRIPTION
ALEXRNEB ALLOCATION EXTENDED RANGE 3XR 015
ALLVCDEB ALLOCATION LAND VESSEL CODE 1AF 015
ALMLVLEB ALLOCATION MAINTENANCE LEVEL 2XL 015
FUNCTION
ALSTIDEB ALLOCATION STATION 5XL 015
IDENTIFICATION CODE
80.3 Table EC, Support Equipment Parameters. This table allows documenting

MIL-STD-1388-2B
APPENDIX A
SUSRNOEK SUPERSEDURE SUPPORT EQUIPMENT 10XF 416

RECOMMENDATION DATA NUMBER
REASUPEK REASON FOR SUPERCEDURE/DELETION 2 X F - 327
ICCODEEK SUPERSEDURE INTERCHANGEABILITY 2XL- 172
CODE
80.12 Table EL, Support Equipment Integrated Logistic Support Requirement

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

NUMBER
IRCCODEL INTEGRATED LOGISTIC SUPPORT 1AF 171 K
REQUIREMENT CATEGORY CODE
(IRCC)
CONRECEL IRCC CONTRACTOR RECOMMENDED 1AF 057
ESTPRCEL IRCC ESTIMATED PRICE 8NR 101
GOVRQDEL IRCC GOVERNMENT REQUIRED 1AF 150
IRCSCOEL IRCC SCOPE 40XL 365
80.13 Table EM, System Equipment. This table allows documenting items which
are components of the system/equipment and are necessary to be used in
conjunction with the SE item to perform its intended function. For example, a
wiring harness with the same part number as the one used on the
system/equipment might be required at test bench in order to fault isolate a
line replaceable unit (LRU). This wiring harness would be considered a
required piece of system equipment. Table Keys include System CAGE (SCAGECEM)
and System Reference Number (SREFNOEM) (both migrate from table HA, but are
given “System” role name), and SE CAGE Code (SECAGEEA) and SE Reference
Number (SEREFNEA) (migrate from table Eli).
SECAGEEA SUPPORT EQUIPMENT (SE) CAGE CODE 5 X F - 046 F

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

MIL-STD-1388-2B
APPENDIX A
90. UNIT UNDER TEST REQUIREMENTS AND DESCRIPTION. Data tables beginning with
“U” in the first positon of the table code are structured to identify the UUT
and those hardware and software elements required to test the UUT with off-
line support/test equipment. The unique combination of these elements
required for a specific UUT and support/test equipment configuration is a Test
Program Set (TPS). In addition to defining the TPS elements, this information
provides the configuration identification of the UUT (i.e., the UUT and the
support/test equipment to be used in the test). This information is
established for each UUT which has a requirement to be tested by the
support/test equipment documented. Additionally, Calibration and Measurement
Requirement Summary (CMRS) information is captured in these tables. Figure 9
depicts the relational hierarchy of these tables/entities.
UA Article Requiring Support/Unit Under Test
UB Unit Under Test Support Equipment
UC Operational Test Program
UD Unit Under Test Support Equipment Operational Test
Program ‘
UE Test Program Instruction
UF Unit Under Test Explanation
UG Unit Under Test Parameter Group
UH Unit Under Test Fault Isolated Replaceable Unit
UI Adapter-Interconnector Device
UJ Unit Under Test Support Equipment Adapter-
Interconnector Device
UK Automatic Test Equipment Test Station

UL Unit Under Test Support Equipment Automatic Test
Equipment
UM Support Equipment Item Unit Under Test
UN Support Equipment Unit Under Test Parameter Group
90.1 Table UA, Article Requiring Support/Unit Under Test. This table
identifies the UUT which is a component of weapon system breakdown structure.
A UUT can be either a component of the system/equipment or a piece of complex
SE itself which must be documented under the end article (weapon system) for
contractual or provisioning purposes. Table keys are migrated from table XB,
but are given the role name “UUT” to distinguish them (WTLCNUA, WTALCUA, and
UTLCNTUA). The EIAC must be the same as in table XB, therefore it, is not
role named.

MIL-STD-1388-2B
APPENDIX A
OTPCTPUC OTP COORDINATED TEST PLAN 1XF 060
OTPSFCUC OTP STANDARDS FOR COMPARISON 1XF 402
OTPSRDUC OTP SUPPORT EQUIPMENT 10XF 416
90.4 Table UD, Unit Under Test Support Equipment Operational Test Program.
This table ties together the relationship between the SE, UUT, and the OTP to
maintain the specific application of the OTP. Table keys are EIAC (EIACODXA),
UUT LCN (UUTLCNUA), UUT ALC (UUTALCUA), UUT LCN Type (UTLCNTUA), SE Reference
Number (SEREFNEA), SE CAGE Code (SECAGEEA) (these migrate from the UB table),
and OTP Reference Number (OTPREFUC) and OTP CAGE Code (OTPCAGUC), which
migrate from the UC table.
CODE SHORT NAME FORMAT
UUTLCNUA UUT LSA CONTROL NUMBER (LCN) 18XL- 199 F
UUTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UUT LCN TYPE 1AF- 203 F
SEREFNEA SUPPORT EQUIPMENT REFERENCE 3 2 XL 337 F
NUMBER
OTPCAGUC OPERATIONAL TEST PROGRAM CAGE 5XF 046 F
CODE
OTPREFUC OPERATIONAL TEST PROGRAM 32XL 337 F
. REFERENCE NUMBER
90.5 Table UE, Test Program Instruction. This table allows documenting basic
identification and cost information pertaining to a test program instruction
(TPI) . The TPI is used as an aid in the use of an OTP. Table keys are
migrated from the HA table and given the role name “TPI” to form the following
keys : TPI Reference Number (TPIREFUE) and TPI CAGE Code (TPICAGUE). Also, -
the keys from table UC (OTP CAGE and Reference Number) are migrated in as
foreign keys.
CODE SHORT NAME FORMAT DED KEY
OTPCAGUC OPERATIONAL TEST PROGRAM CAGE 5XF 046 F
CODE
OTPREFUC OPERATIONAL TEST PROGRAM 32XL 337 F
REFERENCE NUMBER
TPICAGUE TEST PROGRAM INSTRUCTION (TPI) 5XF 046 F
CAGE CODE
TPIREFUE TPI REFERENCE NUMBER 32XL 337 F
TPAUCRUE TPI APPORTIONED UNIT COST 8NR 025
RECURRING
TPAUCNUE TPI APPORTIONED UNIT COST 8NR 025
NONRECURRING
TPISTSUE TPI SELF TEST 1AF 370
TPITDPUE TPI TECHNICAL DATA PACKAGE 1AF 434
-75-
MIL-STD-1388-2B
APPENDIX A
TPISRDUE TPI SUPPORT EQUIPMENT 10XF 416

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

WTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA WT LCN TYPE 1AF- 203 F
TEXSEQUF UUT EXPLANATION TEXT 5NR- 450 K
SEQUENCING CODE
UTEXPLUF UUT EXPLANATION 65X-- 498
90.7 Table UG, Unit Under Test Parameter Group. This table allows
documenting specific information about individual parameters which the unit
under test requires to have measured, generated, etc. by the support
equipment. This table is used when the WT is a subelement of the
system/equipment (CMRS category I item), as opposed to being another piece of
support equipment, with one exception. This table can be used to document
parameters for a piece of complex SE which is an LSA candidate, thereby,
making it the WT. Table keys are EIAC (EIACODXA), UJT LCN (WTLCWA), UUT
ALC (WTALCUA), UUT LCN Type (UTLCNTUA), SE Reference Number (SEREFNEA), and
NOTE: The WT Parameter Grouping Code (WTPGCUG) and the SE Parameter

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

WTLCNUA UUT LSA CONTROL NUMBER (LCN) 18XL- 199 F
WTALCUA UUT ALTERNATE LCN CODE 2NF- 019 F
UTLCNTUA UTT LCN TYPE 1AF- 203 F
NUMBER
WTPGCUG UUT PARAMETER GROUP CODE 2AF- 284 K
WTPPCUG UUT CALIBRATION MEASUREMENT 1AF 034
REQUIREMENT SUMMARY PARAMETER
CODE
WTPACUG UUT PARAMETER ACCURACY 26XL 284
WTPIOUG UUT PARAMETER INPUT/OUTPUT CODE 1AF 284

MIL-STD-1388-2B
APPENDIX A
WTPSOUG UUT PARAMETER OPERATIONAL/ 1AF 284

SPECIFICATION CODE
WTPARUG UUT PARAMETER 12XL 284
WTPRFUG UUT PARAMETER RANGE FROM 10 D --- 284
WTPRTUG UUT PARAMETER RANGE TO 10D-- 284
WTPRWG UUT PARAMETER RANGE/VALUE CODE 1AF 284
WTPTAUG UUT PARAMETER TEST ACCURACY 1XF 442
RATIO (TAR) ACTUAL
WTPTDUG UUT PARAMETER TAR DESIRED 1XF 442
90.8 Table UH, Unit Under Test Fault Isolated Replaceable Unit. This table
allows documenting the relationship between SE, UUT, task provisioned items,
and Fault Isolated Replaceable Units (FIRU). The FIRU is an item which is
subordinate to the UUT LCN (WTLCNUA) and the Task LCN (TSKLCNCI) in hardware
breakdown. In fact, the UUT LCN and the Task LCN are one in the same and
therefore, must be identical to each other. This table also allows
documenting the percentage of faults which can be isolated to a given
ambiguity group (up to two groups) and its respective number of items per
ambiguity group. Table keys include those which originate in table CI
(EIACODXA, TSKLCNCI, TSKALCCI, TSKLTYCI, TSKTCDCI, PROLCNCI, PROALCCI,
PROLTYCI, PROCAGCI, and PROREFCI) and are migrated to table UH. Keys from
table EA migrate down as nonidentifying.
a. PROLCNCI must be subordinate to TSKLCNCI.
b. PROLCNCI identifies the FIRU item.
c. To qualify as an FIRU, the PROLCNCI must have an ICC of X, Y, 9, M1,

or AB (identified in table HG) and must be identifiable through fault
isolation procedures for the TSKLCNCI.

EIACODXA END ITEM ACRONYM CODE 10XL 096 F
TSKLCNCI TASK LSA CONTROL NUMBER (LCN) 18XL- 199 F
TSKALCCI TASK ALTERNATE LCN CODE (ALC) 2NF 019 F
TSKLTYCI TASK LCN TYPE 1AF- 203 F
TSKTCDCI TASK PROVISION TASK CODE 7XF- 427 F
PROLCNCI TASK PROVISION LCN 18XL- 199 F
PROALCCI TASK PROVISION ALC 2NF- 019 F
PROLTYCI TASK PROVISION LCN TYPE 1AF- 203 F
PROCAGCI TASK PROVISION CAGE CODE 5XF- 046 F
PROREFCI TASK PROVISION REFERENCE NUMBER 32XL- 337 F
SECAGEEA SUPPORT EQUIPMENT CAGE CODE 5XF 046
SEREFNEA SUPPORT EQUIPMENT REFERENCE 32XL 337
NUMBER
WTFAIUH UUT FIRU AMBIGUITY GROUP 1 2 NR 143
UUTFA2UH UUT FIRU AMBIGUITY GROUP 2 2 NR 143
UUTFP1UH UUT FIRU PERCENT FAILURE 1 3 NR1 143
UUTFP2UH UUT FIRU PERCENT FAILURE 2 3 NR1 143
UUTFTDUH UUT FIRU TEST REQUIREMENTS 1 AF 447
DOCUMENT INDICATOR

MIL-STD-1388-2B
APPENDIX A
90.9 Table UI, Adapter Interconnector Device. This table contains pricing
and identification information about items which are utilized to interface the
UUT with the SE. The table keys are migrated from table HA and given the role
names Adapter Interconnector Device (AID) Reference Number (AIDREFUI) and AID
CAGE Code (AIDCAGUI).
AIDCAGUI ADAPTER INTERCONNECTOR DEVICE 5XF 046 F

(AID) CAGE CODE
AIDREFUI AID REFERENCE NUMBER 32XL 337 F
AIDUCNUI AID APPORTIONED UNIT COST 8NR 025
NONRECURRING
AIDUCRUI AID APPORTIONED UNIT COST 8NR 025
RECURRING
AIDSRDUI AID SUPPORT EQUIPMENT 10XF 416
AIDCUTUI AID COMMON UNIT UNDER TEST 2NR 048
90.10 Table UJ, Unit Under Test Support Equipment Adapter Interconnector
Device. This table cross-references data pertaining to the relationship
between the SE, AID, and the UUT. Table keys include the CAGE and Reference
Number for the AID (AIDCAGUI and AIDREFUI, respectively) from table UI and the
keys migrated from table UB which are EIAC (EIACODXA), UUT LCN (WTLCWA), UUT
ALC (UUTALCUA), UUT LCN Type (UTLCNTUA), SE Reference Number (SEREFNEA), and

NUMBER
AIDCAGUI ADAPTER INTERCONNECTOR DEVICE 5XF 046 F
(AID) CAGE CODE
AIDREFUI AID REFERENCE NUMBER 32XL 337 F
90.11 Table UK, Automatic Test Equipment Test Station. This table is used to
document identification and government designator information concerning the
Automatic Test Equipment (ATE) Test Station required on a SERD summary. Table
keys are migrated from table HA and given role names of ATE Reference Number
(ATEREFUK) and ATE CAGE Code (ATECAGUK).
ATECAGUK ATE CAGE CODE 5XF- 046 F

ATEREFUK AUTOMATIC TEST EQUIPMENT (ATE) 32XL 337 F
REFERENCE NUMBER
ATEGDSUK ATE GOVERNMENT DESIGNATOR 20XL- 149

MIL-STD-1388-2B
APPENDIX A
90.12 Table UL, Unit Under Test Support Equipment Automatic Test Equipment.
This table cross-references the ATE Test Station (table UK) data with the UUT
SE (table UB). Table keys are ATE Reference Number (ATEREFUK) and ATE CAGE
Code (ATECAGUK) migrated from table UK and the keys migrated from table UB
which are EIAC (EIACODXA), UUT LCN (UUTLCNUA), UUT ALC (WTALCUA), UUT LCN
Type (UTLCNTUA), SE Reference Number (SEREFNEA), and SE CAGE Code (SECAGEEA).

NUMBER
ATECAGUK ATE CAGE CODE 5XF- 046 F
ATEREFUK AUTOMATIC TEST EQUIPMENT (ATE) 32XL 337 F
REFERENCE NUMBER
90.13 Table UM, Support Equipment Item Unit Under Test. This table
identifies pieces of SE (Calibration and Measurement Requirement Summary
(CMRS) category II items) that are linked with CMRS category III items (SE in
support of the category II SE). Normally, Tables UM and UN are only used if
a CMRS (LSA-076) is required on contract. Table keys are migrated down from
the EA table (Support Equipment) and given a role name of Support Equipment
Unit Under Test to distinguish them (SUTCAGUM and SUTREFUM).
SUTCAGUM SUPPORT EQUIPMENT UNIT UNDER 5XF 046 F

TEST (SE UUT) CAGE CODE
SUTREFUM SE UUT REFERENCE NUMBER 32XL 337 F
SUTALLUM SE UUT ALLOWANCE 10XL 016
SUTSTCUM SE UUT CMRS STATUS 1AF 036
MNTPLNUM SE UUT MAINTENANCE PLAN NUMBER 23XL 209
TRDNUMUM SE UUT TEST REQUIREMENTS 15XL 448
DOCUMENT NUMBER
WKPKRFUM SE UUT WORK PACKAGE REFERENCE 6XL 515
90.14 Table UN, Support Equipment Unit Under Test Parameter Group. This
table allows documenting specific information about individual parameters
which a piece of support equipment (SE) (CMRS category II) requires to have
calibrated, measured, etc. by another piece of SE (CMRS category 111 item).
Data from this table will be used on the CMRS report (LSA-076). Table keys
include the SE UUT Parameter Group Code (SEUPGCUN), keys migrated from table
EA and given role names of “Testing” (TGSCAGUN and TGSREFUN), and keys from
table UM are also migrated into this table (SUTREFUM and SUTCAGUM).
NOTE: The SE UUT Parameter Grouping Code (SEUPGCUN) and the SE Parameter
Grouping Code (PARGPCEC) (table EC) provide the link between the parameters of
CMRS category III items and category II items, respectively. Therefore,

MIL-STD-1388-2B
APPENDIX A
the values for PARGPCEC and SEUPGCUN must be identical to link the SE UUT to
the,corresponding piece of testing SE.
TGSCAGUN TESTING SUPPORT EQUIPMENT (SE) 5XF- 046 F

CAGE CODE
TGSREFUN TESTING SE REFERENCE NUMBER 32XL- 337 F
SUTCAGUM SE UNIT UNDER TEST (UUT) CAGE 5XF- 046 F
CODE
SUTREFUM SE UUT REFERENCE NUMBER 32XL- 337 F
SEUPGCUN SE UUT PARAMETER GROUP CODE 2AF- 284 K
UTPACMUN SE UUT CALIBRATION MEASUREMENT 1AF 034
REQUIREMENTS SUMMARY (CMRS)
PARAMETER CODE
UTPAACUN SE UUT PARAMETER ACCURACY 26XL 284
UTPAIOUN SE UUT PARAMETER INPUT/OUTPUT 1AF 284
CODE
UTPAPAUN SE UUT PARAMETER 12XL 284
UTRGFRUN SE UUT PARAMETER RANGE FROM 10D-- 284
UTPRRTUN SE UUT PARAMETER RANGE TO 10D-- 284
UTPARVUN SE UUT PARAMETER RANGE/VALUE 1AF 284
CODE
UTPATAUN SE UUT PARAMETER TEST ACCURACY 1XF 442
RATIO (TAR) ACTUAL
UTPATDUN SE UUT PAIUMETER TAR DESIRED 1XF 442
Supersedes page 80 of 28 March 91 - 80 -

MIL-STD-1388-2B
APPENDIX A
100. FACILITIES CONSIDERATIONS. Data tables beginning with “F” in the first
position of the table code are structured to describe and justify all proposed
special and additional facilities requirements, which are indicated as a
result of the operational/maintenance task analysis. Figure 10 depicts the
relational hierarchy of these tables/entities.
FA Facility
FB Facility Narrative
FC Baseline Facility Narrative
FD New or Modified Facility Narrative
FE Operations and Maintenance Task Facility Requirement
100.1 Table FA, Facility. This table identifies the facility by name,
category code, and type that the system/equipment under analysis requires.
The table keys are Facility Name (FACNAMFA), Facility Category Code
(FACCCDFA), and Facility Type (FACTYPFA). For a given row of information, the
following cross-element edits apply to table FB:
a. Facility Area (FAAREAFA) and Facility Area UM (FAARUMFA) must either

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

Unit of Measure (CONUOMFA) must either both be blank, or both have entries.

FACNAMFA FACILITY NAME 32XL- 118 K
FACCCDFA FACILITY CATEGORY CODE 6NL- 115 K
FACTYPFA FACILITY TYPE 1AF- 483 K
FACCLAFA FACILITY CLASS 19XL- 116
DRCLASFA FACILITY DRAWING CLASSIFICATION 3X-- 088
FADNUMFA FACILITY DRAWING NUMBER 32XL- 089
FADREVFA FACILITY DRAWING REVISION 2AR- 360
FAAREAFA FACILITY AREA 6NR- 112
FAARUMFA FACILITY AREA UNIT OF MEASURE 2AF- 491
FACNCOFA FACILITY CONSTRUCTION UNIT OF 10NR2- 492
MEASURE PRICE
CONUOMFA CONSTRUCTION UNIT OF MEASURE 2AF- 491
100.2 Table FB, Facility Narrative. This table may be used to identify
Facility Capability, and Facility Location of either the baseline facility or
the new or modified facility. The table keys consist of Facility Name
(FACNAMFA), Facility Category Code (FACCCDFA), Facility Type (FACTYPFA),
Facility Narrative Code (FNCODEFB), and Facility Narrative Text Sequencing
Code (TEXSEQFB). For a given row of information, the following cross-element
edits apply to table FB:
a. If the Facility Narrative Code (FNCODEFB) is (A), then this table

identifies the capacity impact on the work load of the facility (Facility

MIL-STD-1388-2B
APPENDIX A
FIGURE 10. F table relationships.
REPRINTED WITHOUT CHANGE 82

MIL-STD-1388-2B
APPENDIX A
b. For identical Reference Number and CAGE keys, only one row of
information can be established with a “Y” Provisioning UM Price Code
(PROUMPHD).
c. Lot Quantity From (LOTQFMHE) must be less than or equal to Lot

Quantity To (LOTQTOHE) in any row.
CAGECDXH CAGE CODE 5XF- 046 F

REFNUMHA REFERENCE NUMBER 32XL- 337 F
UMPRICHE UNIT OF MEASURE (UM) PRICE 10NR2 492 K
LOTQFMHE UM PRICE LOT QUANTITY FROM 6NR- 205
LOTQTOHE UM PRICE LOT QUANTITY TO 6NR- 205
CURPRCHE UM PRICE CONCURRENT PRODUCTION 1AF- 051
CODE
TUMPRCHE UM PRICE TYPE OF PRICE CODE 1AF- 485
PROUMPHE UM PRICE PROVISIONING 1AF- 314
FISCYRHE UM PRICE FISCAL YEAR 2NF- 145
120.6 Table HF, Item Packaging Requirement. This table contains packaging
data, as specified by MIL-STD-2073-1 and MIL-STD-2073-2. Table keys are:
Reference Number (REFNUMHA); CAGE (CAGECDXH); and, Degree of Protection
(DEGPROHF).
a. Unit Pack Length (LENUPWF), Width (WIDUPKHF), and Depth (DEPUPKHF)

.. must either all be blank or all have entries for a row of information.
b. Unit Pack entries must be greater than or equal to Unit Size entries
in table HA (LENUPKHF greater than or equal to ULENGTHA; WIDUPKHF greater than
or equal to UWIDTHHA; and, DEPUPKHF greater than or equal to UHEIGHHA).
For numeric entry, Unit Pack Weight (UNPKWTHF) must be greater than or
equal to Unit Weight (UWEIGHHA).
d. Packaging data preparer CAGE (PKCAGEHF) is a nonidentifying key

migrating from table XH.
e. When packaging in accordance with special packaging instruction (SPI)

enter code ZZ in the Method of Preservation Code (MEPRESHF) and omit entries
in the following fields: Cleaning and Drying Procedures (CDPROCHF),
Preservation Material Code (PRSMATHF), Wrapping Material (WRAPMTHF),
Cushioning and Dunnage Material (CUSHMAHF), Cushioning Thickness (CUSTHIHF),
and Unit Container (UNICONHF).
f. The Container National Stock Number (CONNSNHF) is only the 4th - 16th
positions of DED 253, National Stock Number and Related Data.

DEGPROHF DEGREE OF PROTECTION CODE IAF- 074 K
UNICONHF UNIT CONTAINER CODE 2XF- 486
UCLEVLHF UNIT CONTAINER LEVEL lXF- 487
- 95 - Supersedes page 95 of 28 March 91

MIL-STD-1388-2B
APPENDIX A
PKGCODHF PACKING CODE 3XF- 283
PACCATHF PACKAGING CATEGORY CODE 4XF- 282
MEPRESHF METHOD OF PRESERVATION CODE 2XF- 239
CDPROCHF CLEANING AND DRYING PROCEDURES 1XF- 045
PRSMATHF PRESERVATION MATERIAL CODE 2 X F - 295
WRAPMTHF WRAPPING MATERIAL 2XF- 517
CUSHMAHF CUSHIONING AND DUNNAGE MATERIAL 2XF- 067
CUSTHIHF CUSHIONING THICKNESS 1XF- 068
QTYUPKHF QUANTITY PER UNIT PACK 3X-- 321
INTCONHF INTERMEDIATE CONTAINER CODE 2XF- 174
NEW PAGE - 95a -


MIL-STD-1388-2B
APPENDIX A
INCQTYHF INTERMEDIATE CONTAINER QUANTITY 3X-- 175

SPEMRKHF SPECIAL MARKING CODE 2XF- 394
UNPKWTHF UNIT PACK WEIGHT 5X-- 495
LENUPKHF UNIT PACK LENGTH 4NR1 494
WIDUPKHF UNIT PACK WIDTH 4NR1 494
DEPUPKHF UNIT PACK DEPTH 4NR1 494
UNPKCUHF UNIT PACK CUBE 7NR3 493
OPTPRIHF OPTIONAL PROCEDURES INDICATOR 1XF- 279
SPINUMHF SPECIAL PACKAGING INSTRUCTION 10XL- 396
(SPI) NUMBER
SPIREVHF SPI NUMBER REVISION 1AF- 397
SPDATEHF SPI NUMBER JULIAN DATE 5NL- 187
CONNSNHF CONTAINER NATIONAL STOCK NUMBER 20 X -- 253
SUPPKDHF SUPPLEMENTAL PACKAGING DATA 59 X L - 409
PKCAGEHF PACKAGING DATA PREPARER CAGE 5XF- 046
120.7 Table HG, Part Application Provisioning. This table contains parts
related information to the part in a specific hardware application. Table
keys include: Reference Number (REFNUMHA); CAGE (CAGECDXH); EIAC (EIACODXA);
LCN (LSACONXB); ALC (ALTLCNXB); and, LCN Type (LCNTYPXB).
a. LCN Type must always be “P” (Physical).
b. Maintenance Action Code (MAIACTHG) is not allowed without Maximum

Allowable Operating Time (MAOTIMHG).
c. Maintenance Task Distribution subfields (OMTDOOHG, FMTDFFHG, HMTDHHHG,

LMTDLLHG, DMTDDDHG, CBDMTDHG, and CADMTDHG) must always total to 100 percent.
d. Replacement Task Distribution subfields (ORTDOOHG, FRTDFFHG, HRTDHHHG,

LRTDLLHG, and DRTDDDHG) must always total to 100 percent.
c. PCCN (PCCNUMXC) and Provisioning List Item Sequence Number (PLISN)

(PLI~NOHG) combinations must be unique across all rows of information
(PLISNS are mapped to respective PCCNs in Table XC through Table HO).
f. Same as PLISN (SAPLISHG) must be contained in this table as a PLISN
(PLISNOHG) having an identical PCCN. The same as PLISN must be the lowest
(EBCDIC value) PLISN in the table for the same Reference Number, CAGE, and
PCCN combinations (without an associated “D” TOCC).
g. Repair Cycle Time (ORCTOOHG, FRCTFFHG, HRCTHHHG, LRCTLLHG, DRCTDDHG

and CONRCTHG) for each Operations/Maintenance (0/M) Level (identified by the
first position of the short name) must be either blank or greater for each
higher O/M level. The O/M levels in ascending order are O, F, H, L, D, and
CON (contractor).
h. When numeric, the Quantity Per End Item (QTYPEIHG) must be greater
than or equal to the Quantity Per Assembly (QTYASYHG).
i. Maintenance Task Distribution and Replacement Task Distribution.
(1) OMTDOOHG must be less than or equal to ORTDOOHG.

MIL-STD-1388-2B
APPENDIX A
ORCTOOHG ORGANIZATIONAL REPAIR CYCLE 3NR- 350

TIME (RCT)
FWTFFHG INTERMEDIATE\DIRECT SUPPORT RCT 3NR- 350
HRCTHHHG INTERMEDIATE/GENEIUL SUPPORT RCT 3NR- 350
LRCTLLHG SPECIAL REPAIR ACTIVITY RCT 3NR- 350
DRCTDDHG DEPOT/SHIPYARD RCT 3NR- 350
CONRCTHG CONTRACTOR RCT 3NR- 350
NORETSHG NOT REPAIRABLE THIS STATION 3NR- 261
REPSURHG REPAIR SURVIVAL RATE 3NR- 351
DRPONEHG DESIGNATED REWORK POINT ONE 6XL- 081
DRPTWOHG DESIGNATED REWORK POINT TWO 6XL- 081
WRKUCDHG WORK UNIT CODE 7XL- 516
ALLOWCHG ALLOWANCE ITEM CODE 2XF- 017
ALIQTYHG ALLOWANCE ITEM QUANTITY 3NR- 018
120.8 Table HH, Overhaul-Kit Next Higher Assembly PLISN. This table contains
all Next Higher Assembly (NHA), kit or overhaul PLISNs, any associated NHA
PLISN Indicators, and Overhaul Replacement Rates. Table keys include:
Reference Number (REFNUMHA); CAGE (CAGECDXH); EIAC (EIACODXA); LCN (LSACONXB);
ALC (ALTLCNXB); LCN type (LCNTYPXB); and NHA PLISN (NHAPLIHH). NHA PLISN must
be a PLISN contained in table XC (PLISNOXC) or table HG (PLISNOHG) with an
identical PCCN (PCCNUMXC).

NHAPLIHH NEXT HIGHER ASSEMBLY (NHA) 5XL- 258 K
PROVISIONING LIST ITEM SEQUENCE
NUMBER (PLISN)
NHAINDHH NHA PLISN INDICATOR 1XF- 259
OVHREPHH OVERHAUL REPLACEMENT RATE 3NR2 281
120.9 Table HI, Provisioning Remark. This table contains text remarks
associated with a part application for provisioning. Table keys include:
Reference Number (REFNUMHA ); CAGE (CAGECDXH); EIAC (EIACODXA); LCN (LSACONXB);
ALC (ALTLCNXB); LCN Type (LCNTYPXB); and, Text Sequencing Code (TEXSEQHI).

TEXSEQHI PROVISIONING TEXT SEQUENCING CODE 5 N R - 450 K
REMARKHI PROVISIONING REMARKS 65X-- 311

MIL-STD-1388-2B
APPENDIX A
120.10 Table HJ, Provisioning Reference Designation. This table contains

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

REFDESHJ REFERENCE DESIGNATION 64XL- 335 K
RDCODEHJ REFERENCE DESIGNATION CODE 1AF- 336
TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437
FIGNUMHK FIGURE NUMBER 4XR- 144
ITEMNOHK ITEM NUMBER 4XR- 184
120.11 Table HK, Parts Manual Description. This table contains Repair Parts
Manual data associated with a part application for provisioning. Table keys
include: Reference Number (REFNUMHA); CAGE (CAGECDXH); EIAC (EIACODXA); LCN
(LSACONXB); ALC (ALTLCNXB), LCN Type (LCNTYPXB); TM Code (TMCODEXI);
Figure Number (FIGNUMHK); and Item Number (ITEMNOHK).

TMCODEXI TECHNICAL MANUAL (TM) CODE 3XF- 437 F
FIGNUMHK FIGURE NUMBER 4XR- 144 K
ITEMNOHK ITEM NUMBER 4XR- 184 K
TMFGCDHK TM FUNCTIONAL GROUP CODE 11 X L- 438
(REPAIR PARTS MANUAL)
TMINDCHK TM INDENTURE CODE 1NF- 439
QTYFIGHK QUANTITY PER FIGURE 3NR- 318
TMCHGNHK TM CHANGE NUMBER 2NR- 436
120.12 Table HL, Parts Manual Provisioning Nomenclature. This table contains
text for repair parts manual data associated with a part application for
provisioning. Table keys include: Reference number (REFNUMHA ); CAGE
(CAGECDXH); EIAC (EIACODXA); LCN (LSACONXB); ALC (ALTLCNXB), LCN Type
(LCNTYPXB); TM Code (TMCODEXI); Figure Number (FIGNUMHK); Item Number
(ITEMNOHK); and, Text Text Sequencing Code (TEXSEQHL).

MIL-STD-1388-2B
APPENDIX A
ALTLCNHN S/N PROVISIONING ALTERNATE LCN 2NF- 019 F

CODE (ALC)
LCNSEIHN S/N PROVISIONING SYSTEM/EI LCN 18XL- 199 F
ALCSEIHN S/N PROVISIONING SYSTEM/EI ALC 2NF- 019 F
FRSNUMHN S/N PROVISIONING SERIAL NUMBER 10XL- 373 F
FROM
TOSNUMHN S/N PROVISIONING SERIAL NUMBER TO 10 X L - 373 F
120.15 Table HO, Provisioning System/End Item Usable On Code. This table
relates a part application to the applicable System/End Item UOCs and
Provisioning Contract Control Number (PCCN) associated with the part
application. Table keys include all columns. Table keys CAGEDHO, REFNUMHO,
LSACONHO, and ALTLCNHO migrate from table HG. Table keys LCNSEIHO and
ALCSEIHO migrate from table XC, from which UOCs and the PCCN are extracted.
EIACODXA and LCNTYPXB are identical in both tables XC and HG.
NOTE: Part application LCNS (LSACONHO) are mapped to their respective

system/end items by matching on EIAC, LCN Type, LCN, and ALC between tables HO
and XC to extract applicable UOCS and the PCCN. A part application can have
multiple UOCs, but only one PCCN, with the exception of separately provisioned
end items.

CAGECDHO UOC PROVISIONING CAGE CODE 5XF- 046 F
REFNUMHO UOC PROVISIONING REFERENCE NUMBER 32 X L - 337 F
LSACONHO UOC PROVISIONING LSA CONTROL 18XL- 199 F
NUMBER (LCN)
ALTLCNHO UOC PROVISIONING ALTERNATE LCN 2NF- 019 F
CODE (ALC)
LCNSEIHO UOC PROVISIONING SYSTEM/EI LCN 18XL- 199 F
ALCSEIHO UOC PROVISIONING SYSTEM/EI ALC 2NF- 019 F
120.16 Table HP, Desire Change Information. This table contains information
about the parts application item affected by a design change. Table keys
include: Reference Number (REFNUMHA ); CAGE (CAGECDXH); EIAC (EIACODXA); LCN
(LSACONXB); ALC (ALTLCNXB); LCN Type (LCNTYPXB); and, Change Authority Number
(CANUMBHP).
a. Replaced or Superseding PLISN (RSPLISHP) must be established in either

table HG or XC matching the PCCN of the HP table keys (less CANUMBHO). A
Replaced or Superseded PLISN Indicator (RSPLINDHP) cannot be entered without
a Replaced or Superseded PLISN (RSPLISHP).
b. Quantity Procured (QTYPROHP) must be entered if there is an entry in

Quanity Shipped (QTYSHPHP). The QTYPROHP must be greater than or equal to the
QTYSHPHP.
c. Prorated Exhibit Line Item (PROELIHP) must be entered if there is an

entry in Prorated ELIN Quantity (PROQTYHP).

MIL-STD-1388-2B
APPENDIX A

ALTLCNXB ALTERNATE LCN CODE (ALC) 2NF- 019 F
CANUMBHP CHANGE AUTHORITY NUMBER 15XL- 043 K
RSPLISHP REPLACED OR SUPERSEDING (R-S) 5XL- 353
PROVISIONING LIST ITEM SEQUENCE
NUMBER (PLISN)
RSPINDHP R-S PLISN INDICATOR 1AF- 354
INTCHCHP INTERCHANGEABILITY CODE 2AF- 172
TOTICHHP TOTAL ITEM CHANGES 2NR- 452
QTYSHPHP QUANTITY SHIPPED 6NR- 323
QTYPROHP QUANTITY PROCURED 6NR- 322
PROELIHP PRORATED EXHIBIT LINE ITEM 6X-- 305
NUMBER (ELIN)
PROQTYHP PRORATED QUANTITY 6NR- 306
120.17 Table HQ, Serial Number Effectivity. This table contains the serial
number effectivity ranges which are affected by the design change. Table keys
include all columns.

CANUMBHP CHANGE AUTHORITY NUMBER 15XL- 043 F
FMSRNOHQ FROM SERIAL NUMBER EFFECTIVITY 10XL- 374 K
TOSRNOHQ TO SERIAL NUMBER EFFECTIVITY 10XL- 374 K
120.18 Table HR, Design Change Usable On Code. This table references to the
UOC affected by a design change. Table keys include all columns. Design
change UOC is extracted from table XC through table HO for the key of UOC
system/EI (LCNSEIHO and ALCSEIHO) and UOC provisioning LCN/ALC (LSACONHO and
ALTLCNHO). REFNUMHO, CAGECDHO, LSACONHO, and ALTLCNHO must be identical with
REFNUMHA, CAGECDXH, LSACONXB, and ALTLCNXB from table HP migrating CANUMBHP
into this table. EIACODXA and LCNTYPXB must be identical in Tables XC, HO,
and HR.

CAGECDHO UOC PROVISIONING CAGE CODE 5XF- 046 F
REFNUMHO UOC PROVISIONING REFERENCE NUMBER 32 X L - 337 F
REPRINTED WITHOUT CHANGE - 103 -
MIL-STD-1388-2B
APPENDIX A
TRCHRDJA REVISION DATE 6NF- 071
TRCHTHJA THEATER OF OPERATION 5AL- 451
NOPRFFJA NONOPERATIONAL FRAGILITY 2NR- 260
FACTOR
NETEXWJA NET EXPLOSIVE WEIGHT 10NR- 254
130.2 Table JB, Transportation Shipping Modes. This table identifies the
different possible transportation shipping modes for the system/equipment
under analysis. This table can identify the different types of aircraft and
whether the aircraft will transport the item under analysis externally or
internally. This table can identify the different type of helicopters, their
mission capabilities, and whether the helicopter will transport the item under
analysis externally or internally. This table can identify the highway prime
and alternate model types and what type of payload capacity the transporter
has. This table can identify the type of lighterages and whether the item
under analysis can be stowed on deck. This table can identify the type of
rail system that will be used and which countries the rail system will run
through for the item under analysis. This table can identify the type of
ships and whether the item under analysis can be stowed on deck. The table
keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN Type
(LCNTYPXB), Transportation Characteristic Number (TRANCNJB), and
Transportation Mode Type (TRCHMTJB). For a given row of information, the
following cross-element edits apply to table JB:
a. This table can only be used if an (S or B) has been entered in the

Transportation Indicator (TRNINDJA) table JA.
b. Transportation Item Designator (TRITDRJB) and External or Internal

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

Designator (TRITDRJB) for an aircraft must either both be blank, or have
entries.
d. Transportation Item Designator (TRITDRJB), Helicopter Mission Altitude

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

Designator (TRITDRJB) for a helicopter must either both be blank, or have
entries.
f. Highway Prime Load (HIPRMLJB), Highway Prime Model Type (HIPRMTJB),

Highway Alternate Load (HALTMLJB), and Highway Alternate Model Type (HALTMTJB)
should only be filled out when the Transportation Character Mode Type
(TRCHMTJB) of (C) is entered.
g. Highway Prime Model Load (HIPRMLJB) and Highway Prime Model Type
(HIPRMTJB) must either both be blank, or have entries.
- 107 - REkRINTED WITHOUT CHANGE

MIL-STD-1388-2B
APPENDIX A
h. Highway Alternate Model Load (HALTMLJB) and Highway Alternate Model

Type (HALTMTJB) must either both be blank, or have entries.
i. Sea Deck Stowage (SDECKSJB) and Transportation Item Designator

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

(TRITDRJB) must either both be blank, or have entries.
k. Transportation Item Designator (TRITDRJB), Rail Use (RAILUSJB) and

Rail Transportation Country (RAILTCJB) should only be filled out when the
Transportation Character Mode Type (TRCHMTJB) of (E) is entered.
l. Rail Use (RAILUSJB) and Rail Transportation Country (RAILTCJB) must

either both be blank, or have entries.
m. Sea Deck Stowage (SDECKSJB) and Transportation Item Designator

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

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


EIACODXA END ITEM ACRONYM CODE 10 X L - 096 F
LSACONXB LSA CONTROL NUMBER (LCN) 18 X L- 199 F
ALTLCNXB ALTERNATE LCN CODE 2 N F - 019 F
LCNTYPXB LCN TYPE 1 A F- 203 F
TRANCNJB TRANSPORTATION CHARACTER NUMBER 2 N R - 465 K
TRCHMTJB TRANSPORTATION CHARACTER MODE 1 A F - 464 K
TYPE
TRITDRJB TRANSPORTATION ITEM DESIGNATOR 26 X L - 469
SHPCONJB SHIPPING CONFIGURATION 2 A L- 380
CONLENJB CONTAINER LENGTH 2 N R - 053
CONTYPJB CONTAINER TYPE 36 X L - 054
FRCLASJB FREIGHT CLASSIFICATION 7 X L - 146
EOILINJB EXTERNAL OR INTERNAL LOAD 1 A F - 104
INDICATOR
HMATLRJB HELICOPTER MISSION ALTITUDE 5 N R - 159
HMDISRJB HELICOPTER MISSION DISTANCE 3 N R - 159
HMPAYRJB HELICOPTER MISSION PAYLOAD 5 N R - 159
HMTMPRJB HELICOPTER MISSION TEMPERATURE 3 N R - 159
HMTIMRJB HELICOPTER MISSION TIME 3NR1 159
HIPRMIJB HIGHWAY PRIME MODEL LOAD l A F - 250
HIPRMTJB HIGHWAY PRIME MODEL TYPE 19 X L - 251
HALTMLJB HIGHWAY ALTERNATE MODEL LOAD 1 A F - 250
HALTMTJB HIGHWAY ALTERNATE MODEL TYPE 19 X L - 251
WILUSJB RAIL USE 5 A L - 326
RAILTCJB RAIL TRANSPORTATION COUNTRY 240 X -- 325
SDECKSJB SEA DECK STOWAGE 1 A F - 072

MIL-STD-1388-2B
APPENDIX A
130.3 Table JC, Transported End Item. This table provides information
pertaining to a System/EI that is to be transported. The table keys consist
of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCl@3), LCN Type (LCNTYPXB),
Transported Configuration Number (TRANCNJC), and Mobility Type (MOBTYPJC).
For a given row of information, the following cross-element edits apply to
table JC:
a. This table can only be used if an (E or B) has been entered in the

Transportation Indicator (TRNINDJA) table JA.
b. Operational Weight Empty (OPWEEMJC) and Military Load Classification

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

Loaded (HICLNLJC) must either both be blank, or have entries.
d. Skid Number of Skids (SNUMSKJC), Skid Area (SDSICGJC), and Skid Area
UM (SKADUMJC) should only be used when the Mobility Type (MOBTYPJC) of (A) is
entered.
e. Skid Area (SDSICGJC) and Skid Area UM (SKADUMJC) must either both be
blank, or have entries.
f. Tracked Ground Pressure (TRGRPRJC), Tracked Road Wheel Weight

(TRRWWTJC), Tracked Pads Touching (TRNUPTJC), Tracked Pad Shoe Area
(TRPSARJC), and Tracked Pad Shoe Area UM (TPSAUMJC) should only be used when
the Mobility Type (MOBTYPJC) of (B) is entered. Wheeled Inflation Pressure
(WHINPRJC), Wheeled Number of Tires (WHNUTIJC), Wheeled Tire Load Ratings
(WHTLDRJC), Wheeled Tire Size (WHTIFTJC), and Wheeled Weight Ratings
(WHWERAJC) may also apply to tracked vehicles.
g. Tracked Pad Shoe Area (TRPSARJC) and Tracked Pad Shoe Area UM
(TPSAUMJC) must either both be blank, or have entries.
h. Wheeled Inflation Pressure (WHINPRJC), Wheeled Number of Tires

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

TRCONMJC TRANSPORTED CONFIGURATION 2NR- 473 K
NUMBER
MOBTYPJC MOBILITY TYPE 1AF- 249 K
OPWEEMJC OPERATIONAL WEIGHT EMPTY 4NR1 276
HICLNEJC MILITARY LOAD CLASSIFICATION 2NR- 241
EMPTY
OPWELDJC OPERATIONAL WEIGHT LOADED 4NR1 276
HICLNLJC MILITARY LOAD CLASSIFICATION 2NR- 241
LOADED
SHWEEMJC SHIPPING WEIGHT EMPTY 4NR1 381
SHWELDJC SHIPPING WEIGHT LOADED 4NR1 381
MIL-STD-1388-2B
APPENDIX A
CREANGJC CREST ANGLE 2 NR- 063

TRGRPRJC TRACKED GROUND PRESSURE 7 NR- 456
TRRWWTJC TRACKED ROAD WHEEL WEIGHT 6 NR1 459
TRNUPTJC TRACKED PADS TOUCHING 2 N R - 458
TRPSARJC TRACKED PAD SHOE AREA 6 NR1 457
TPSAUMJC TRACKED PAD SHOE AREA 2 AF- 491
UNIT OF MEASURE
WHINPRJC WHEELED INFLATION PRESSURE 3NR- 507
WHNUPLJC WHEELED NUMBER OF PLIES 2NR- 508
WHNUTIJC WHEELED NUMBER TIRES 2NR- 509
WHTLDRJC WHEELED TIRE LOAD RATINGS 10XL- 510
WHTIFTJC WHEELED TIRE SIZE 10XL- 512
WHWEWJC WHEELED WEIGHT RATINGS 10XL- 513
TWALFIJC LENGTH FRONT INSIDE 4NR1 029
TWALFOJC LENGTH FRONT OUTSIDE 4NR1 029
TWALRIJC LENGTH REAR INSIDE 4NR1 029
TWALROJC LENGTH REAR OUTSIDE 4NR1 029
SNUMSKJC SKID NUMBER OF SKIDS 2NR- 264
SDSICGJC SKID AREA 6NR1 384
SKADUMJC SKID AREA UNIT OF MEASURE 2AF- 491
130.4 Table JD, Transported End Item Narrative. This table may be used to
identify Tire Requirements, Skid Remarks, Tracked Wheeled Remarks, Turning
Information, Axle and Suspension Remarks, and Other Transported Equipment.
The table keys consist of EIAC (EIACODXA), LCN (LSACONXB), ALC (ALTLCNXB), LCN
Type (LCNTYPXB), Transported Configuration Number (TRANCNJC), and Mobility
Type (MOBTYPJC), Transported End Item Narrative Code (TREINCJD), and
Transported End Item Narrative Text Sequencing Code (TEXSEQJD). For a given
row of information, the following cross-element edits apply to table JD:
a. If the Transported End Item Narrative Code (TREINCJD) is (A), then

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

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

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

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

this table captures all other information pertaining to a item that is being
transported which is not tracked, wheeled, or skid mounted (Transported Other
Equipment, DED 475).

EIACODXA END ITEM ACRONYM CODE 10XL- Z F

MIL-STD-1388-2B
APPENDIX B
option selected); Part II is ascending LCN, then ascending reference number;

and, Part III is sequenced by ascending LCN, then maintenance type (in the
order of P, C, T, and U).
30.19 LSA-025, Packaging Requirements Data. A report of the basic data

requirements for preservation and packing for common, selective, and special
group items. This report consists of four 80-character card record formats of
packaging information as specified by MIL-STD-2073. The report should be used
to provide adequate packaging instructions for DOD users. It is selectable by
either LCN range, a specified reference number and CAGE combination, or by a
specified degree of protection (DOP). An optional 80-card column magnetic
tape output is also available, The report is sequenced in ascending reference
number and CAGE, and DOP. The format is contained on figure 33.
30.19.1 The Supplemental Card Indicator (SCI) is generated on the LSA-025

summary based on the following:
If only an “A” card is used, the SCI is “1”.

If an “A” and “B” card are used, the SCI is “2”.
If an “A”, “B”, and “C” card are used, the SCI is “3”.
If an “A”, “B”, and “D” card are used, the SCI is “4”.
30.20 LSA-026, Packaging Developmental Data. A report of the basic item

identification data required for packing and preservation. The report can be
requested by a single or multiple LCN, specific reference number or UOC, or
SMR source code. The report can be used as a stand-alone or in conjunction
with LSA-025 to provide packaging information for DOD users. It is sequenced
in ascending reference number and CAGE; within each reference number. The UI
prices are listed in descending order; application information is sorted in
ascending LCN sequence. The format is contained on figure 34. Spacing
between rows and columns is not critical on this report.
30.21 LSA-027, Failure\Maintenance Rate Summary. A report identifying an

item and annual operating requirements by LCN and task code. Only tasks with
a task function of “H” or “J” are included in this report. The report should
be used to provide information necessary to monitor failure rates, failure
modes , task frequencies, and MRRs. The format is contained on figure 35.
Spacing between rows and columns is not critical on this report.
30.21.1 The user has the option of selecting this report based on the
Operating Program, Operating Measurement Base, and the MRRI/MRRII Ratio. When
option 1 of the MRRI/MRRII ratio is selected, the user should enter the
required operating program and it’s associated measurement base (MB). The
operating MB should correspond to the MB of the AOR of the item under
analysis. If the MRRII is to be calculated, enter the required MRRI/MRRII
ratio. If left blank, then MRRII cannot be calculated.
30.21.2 The report provides both the table value and the calculated value of
task frequency and MRRs I and II. The task frequency is calculated as
described in DED 430, appendix E. The MRRI is calculated using the following
formula:
MRRI - Task Frequency X Qty/Task X Operating Program (selected)

AOR

MIL-STD-1388-2B
APPENDIX B
The MRRII is calculated using the following formula:
MRRII = MRRI X MRRI/MRRII ratio (selected).
30.21.3 When failure rate, mean time between maintenance (MTBM)-induced, and
MTBM-no defect are reported, each value is preceded by (M), (P), (A), or (C)
to indicate measured, predicted, allocated, and comparative analysis values,
respectively. Where a measured value has not been entered, the report will
default to the predicted, then allocated, and finally comparative analysis.
30.21.4 The report is sequenced by ascending values of LCN for a given task
code, then ascending task codes. This holds true for the assembly LCN, repair
part LCN, and task LCN. For the reliability, availability, and
maintainability (RAM) LCNs, they are sequenced in ascending value, then by
failure mode indicators (FMI).
30.22 LSA-030, Indentured Parts List. This report consists of four options:
a. Option 1 - Draft Repair Parts and Special Tools List (RPSTL)
b. Option 2 - Proof RPSTL
c. Option 3 - Illustrated Parts Breakdown (IPB)
d. Option 4 - Stockage List Type Four
The format for each option is contained on figure 36.
30.22.1 The draft/proof RPSTL consists of four sections prepared IAW

MIL-STD-335(TM) or MIL-M-49502(TM) (Reference MIL-M-49502(TM), paragraph 6.4,
for applicable document):
a. Section I, Introduction
b. Section II, Repair Parts List
c. Section III, Special Tools List
d. Section IV, Cross-Reference Indexes
Sections II, III and IV listings are produced as separate sections of this
report. The lists may be printed on plain bond paper or may be output to a
word processor file to be used as source information for final RPSTL
preparation. The format contained on figure 34 represents MIL-STD-335(TM).
Reference MIL-M-49502(TM) for the correct format if that document is to be
used in lieu of MIL-STD-335(TM).
30.22.2 Documentation of kits for RPSTL. In order to produce kit/kit

component listings for the RPSTL, a kit record first must be established and a
Provisioning List Item Sequence Number (PLISN) assigned to this item. In the
data table, Overhaul-Kit NHA PLISN, against the application of the kit
component record, an NHA PLISN entry of the Kit PLISN with an NHA PLISN
Indicator of “*” is required. Where the kit component appears in the RPSTL
hardware breakout, the phrase “PART OF KIT P/N” (automatically generated),
followed by the reference number of the kit, will be displayed following the

MIL-STD-1388-2B
APPENDIX B
provisioning nomenclature in the description column. The kit components are

automatically generated beneath the kit. The component listing contains the
applicable figure number, item number and quantity per assembly/figure
duplicated from the hardware breakout information.
30.22.3 FGC Header. A maximum of 9 lines of 36-position FGC or illustration

header information may be entered for each RPSTL figure listing. These
headers are not stored in the LSAR.
30.22.4 The report is selectable by technical manual (TM) code and number and
TM FGC range. Sections II and III are sequenced by ascending TM FGC, then
item number, and PLISN. Section IV, Part Number Index, is sorted in ascending
reference number and CAGE; Stock Number Index in ascending NSN national item
identification number, Reference Designation Index in ascending reference
designation; and, Figure and Item Number Index in ascending figure and item
number.
30.22.5 Specific RPSTL processing (draft and proof).
a. The FGC headers are placed in the description column preceding the
first row of data matching on FGC with the FGC header key.
b. The PART NUMBER column contains 16-positions of the reference number.

If the reference number exceeds 16 positions, the remainder is printed
immediately beneath the first 16 on the next line.
c. For the description column, the item name will first appear, then two
spaces followed by the provisioning nomenclature, if applicable. The
provisioning nomenclature is wrapped in the 36-positions allocated for the
description with “breaks” occurring only at spaces. Trailing periods are
placed following the last position of the item name/provisioning nomenclature
to the end of the description column. If there is an associated TM indenture
code, then leading periods are placed prior to the item name, equal to the
number in the TM indenture code field.
d. If there is a nuclear hardness critical item code of “Y” against the

item, the symbol “(HCI)” will appear following the item name and preceding the
provisioning nomenclature.
e. Following the provisioning nomenclature on a separate line, applicable

UOCs of the item are entered, preceded by “UOC: “. For the proof RPSTL, if
the item has full effectivity, no UOCs are displayed. Full effectivity is
determined by comparison of the item’s associated UOCs with all the associated
UOCs to the PCCN of the item. For the draft RPSTL, applicable UOCs are always
shown regardless of full effectivity.
f. Also extracted for kit entries are information of kit NHAs, which are
handled as described in paragraph 30.22.2. The Kit Reference Number is
determined by a match of the Kit NHA PLISN to a PLISN under the same PCCN in
the parts application provisioning data table. One item may be used in
multiple “kits” by multiple kit NHA PLISN HH entries. Beneath each kit, the
rows that make up the kit are displayed using by item name, and in parenthesis
the quantity per assembly or quantity per figure, the figure number, a dash,
then the item number.
- 131 - REPRINTED WITHOUT CHANGE

MIL-STD-1388-2B
APPENDIX B
g. Under the QTY column, the quantity per figure is displayed, unless
blank. If quantity per figure is blank, then quantity per assembly is used.
h. Under the NSN column, a “Y” is displayed if both the federal supply
classification (FSC) and National Item Identification Number (NIIN) are not
blank and the NIIN does not contain alpha characters for the associated item.
Otherwise “N” is displayed.
i. Under the Provisioning List Category Code (PLCC) column, only entries
in Tools and Test Equipment PLCC or “D”s are shown.
j. After all information following a FGC header is displayed, and before

the next FGC header the phrase “END OF FIGURE” is printed. The information is
printed with no line skips between rows. At the end of a page, a page number
is assigned using the figure number from the first record following the FGC
header, followed by dash then “1”. Multiple pages of the same figure follow
the same pattern, e.g., 3-1, 3-2, 3-3, etc. A page break occurs with each new
FGC Header set under a different FGC. If no FGC header is provided, the
report “page breaks” each time the figure number changes.
k. The section III description column is similar to the section II

description with the addition of the interpreted basis of issue (BOI). Each
BOI is displayed by “BOI: “ quantity, then either level or end item. The
level is interpreted (see DED 030). The end item is preceded by “PER” and
followed by “END ITEMS”. The BOI is inserted between the provisioning
nomenclature and the UOC lines.
l. Section IV cross-reference indexes are produced as optional outputs,

as specified by the requester. The reference designations for the reference
designation index will either include those items having a nonidentifying
migrating key of the appropriate figure and item number, if these keys are
present, or will include all related figure and item numbers, if these keys
are not in the reference designation table. Overflows of reference numbers or
reference designations exceeding 16 or 32 positions, respectively, are printed
on the next line immediately below the first portion of the element.
30.22.6 The IPB consists of four sections prepared IAW MIL-M-38807(USAF):
a. Section I, Front Matter
b. Section II, Maintenance Parts List
c. Section III, Numerical Index
d. Section IV, Reference Designation Index
Sections II, III and IV (each section is optional) listings are produced as
separate sections of this report. The lists may be printed on plain bond
paper or may be output to a word processor file to be used as source
information for final IPB preparation.
30.22.7 Documentation of kits for IPB. Extracted for the IPB are any entries
in table HH for qualified rows matching on PLISNs which have an NHA PLISN with
an NHA PLISN indicator of asterisk (*). Where the row of information is
sorted in the report, the phrase “PART OF KIT P/N” will be displayed followed

MIL-STD-1388-2B
APPENDIX B
by the Reference Number of the Kit. The Kit Reference Number is determined by
a match of the table HH NHA PLISN to a table HG PLISN under the same PCCN as
the kit component. One row of data may be used for a kit with multiple
table HH row entries (kit components). Beneath each kit, the components that
make up the kit are displayed by item name, and in parentheses, the Quantity
per Figure (QTYFIGHK) or Quantity per Assembly (QTYASYHG), Figure Number
(FIGNUMHK), a dash, then Item Number (ITEMNOHK).
30.22.8 The IPB report is selectable by technical manual/technical order (TM)

code and number. Section 11 is sequenced by ascending figure number, then
index number and Section III by ascending Reference Number. Section IV,
Reference Designation Index, is sorted in ascending reference designation.
30.22.9 Stockage List Type Four. This option provides a listing of support
items required for a system/equipment. The listing is used as source
information for preparation of stockage list type four parts manuals.
30.22.10 The following data headers appearing on the LSA-030 are modified
DED, or are in addition to the data element dictionary definitions.
a. Reference Designation (Figure Key) (REF DESIG FIG-KEY). Reference

Designation with an associated Reference Designation Code of “F” (first eight
positions only).
b. Special Stockage Indicator (SS1). Assigned by the requiring

authority, the SSI is left blank by the preparing activity.
c. Replacement Factor (REPL FACTOR). MRRI, fourth through seventh posi-

tions only.
d. Quantity per Application and Equipment. These entries are the Quanti-
ty per Assembly and Quantity per End Item, respectively.
e. Item No. Item Number is a numeric entry assigned to each item in the
report beginning with “l”.
30.22.11 The report is selected by LCN range and is sequenced in ascending

Reference Designation.
30.23 LSA-032, Defense Logistics Information System (DLIS) Submittals. This

summary provides a cross-reference between reference numbers selected for
provisioning screening and the submitter’s control number. DLIS screening is
specified by MIL-STD-1388-lA. This summary provides a valuable tool once the
items have been screened through DLSC files, and the screening results are
received as the DLIS results are sequenced by submitter’s control number. The
format is contained on figure 37.
30.23.1. The following definitions are related to terms located on the LSA-032
summary, but not contained in the LSAR:
a. Document Identifier Code (DIC). A three-position alphanumeric code

which is used for identifying interservice agency or intraservice agency.
logistic transactions. Reference number and CAGE screening requests are
identified by DIC “LSR”. Items may be excluded from DLIS screening, if an

MIL-STD-1388-2B
APPENDIX B
entry showing a screening result, is already contained in the DIC field for
the reference number and CAGE.
b. Priority Indicator Code (PIC). A single numeric code used to

designate the required priority to be applied to processing transactions (see
DOD 41OO.38-M).
c. Activity Code. A two-position alpha code identifying a DOD activity,
Federal agency or other authorized government agency for cataloging,
standardization or other management purposes (see DOD 41OO.38-M).
d. Destination Code. A five-position alphanumeric code used in
conjunction with the activity code to register the address data for recipients
of the results of provisioning screening (see DOD 41OO.38-M).
e. Output Data Request Code (ODRC). A numeric series of established sets
of data (Defense Integrated Data System output segments) identified by
specific ODRCs and available for extraction from DLSC files for provisioning
and preprocurement screening purposes (see DOD 41OO.38-M).
f. Single/Multiple Output Code. A numeric code used by the submitter to
indicate whether the results of screening are to be furnished to one or all of
the recipients as registered under the applicable activity code and
destination code (see DOD 41OO.38-M).
g. Submitter’s Control Number. A 17-position computer assigned

alphanumeric field peculiar to provisioning and preprocurement screening
transactions which is used to control and reference the transactions. The
number consists of a four position julian date (YDDD), and a unique sequential
13 position number assigned for each reference number and additional reference
number package which is to be screened.
h. Statistical Indicator Code. A code designating whether data submitted
for screening is required for provisioning or other services (see
DOD 41OO.38-M).
30.23.2 Report processing.
a. Items may be excluded from the report by already having a screening
result displayed in the DIC field, or by DLIS Screening Result Code. The TAPE
option results in an 80-column file of part II information. The report is
sequenced in ascending submitter control number.
b. The submitter control number is constructed from the PCCN/PLISN of the

qualified record. The PLISN used is the lowest valued PLISN for the item
within the selected PCCN/LCN range (the Same As PLISN field is blank). If no
PCCN/PLISN is recorded for an item, then a Type “1” error is displayed. No
rows of data for the item are placed on part II.
c. If Additional Reference Number Select (ARN SEL) is “YES” and if the
item has more than 24 additional reference numbers, then error Type “2” is
displayed. The first 24 ARNs in ascending reference number sequence are.
placed on part 11 of the report.
d. If a specific SOURCE CODE is selected and the SMR is not contained
REPRINTED WITHOUT CHANGE - 134

MIL-STD-1388-2B
APPENDIX B
against an item, at its first appearance, then error Type “3” is shown and the
item is disqualified from part II.
e. If TYPE SCREEN CODE is “F” or “S”, and if ARN SEL is “YES” and if an
Additional Reference Number matches the prime Reference Number, then error
type “4” is displayed. Only the duplicate ARN is disqualified from part II.
In part 11 of the report, columns 41 and 42 are always left blank for “F” or
“S” type screen.
f. If TYPE SCREEN CODE is “P”, and if either the reference number

category code (RNCC) or reference number variation code (RNVC) is missing for
the reference number/CAGE (in HA) or if ARN SEL is “YES” and any additional
reference number and CAGE (in HB), then error Type “5” is displayed. If the
RNCC/RNVC is an ARN, only the ARN is disqualified from part II. If the RNCC/
RNVC is the prime reference number, then the entire item is disqualified from
Part II.
30.24 LSA-033, Preventive Maintenance Checks and Services (PMCS). This
summary provides operator/crew and organizational level preventive maintenance
task identification and description and equipment availability results. The
PMCS are required for the operator and organizational level TMs and are based
on the results of the reliability centered maintenance analysis. The report
is selectable by either LCN range or TM code and number. The format is
contained on figure 38. Spacing between rows and columns is not critical on
this report.
30.24.1 Task interval values are interpreted as follows; “A”, BEFORE; “D”,
DURING; “H”, AFTER; “C”, DAILY; “L”, WEEKLY; “P”, MONTHLY; “M”, QUARTERLY;
“N”, SEMIANNUALLY; and “Q”, YEARLY. If the interval is “B”, then the
maintenance interval (DED 208) and measurement base (DED 238) are displayed
under the interval column. The measurement base is interpreted on the report,
e.g., “S” is ROUNDS. If the report is selected by TM Code, tasks are
qualified to the PMCS report by an associated PMCS indicator (Table CA). If
the report is selected by LCN range, tasks are further qualified by
maintenance level (Task Code, third position) of Crew or Organizational.
30.24.2 The report is sequenced in ascending Task Code Interval in the order
contained in paragraph 30.24.1, then by ascending LCN. Each LCN is assigned a
numeric item number beginning with “0001”. An alphabetic sequence code
beginning with “A” is assigned to each task against the same LCN with the same
Task Code Interval. If the report is selected by LCN range, a page break is
required between output of Operator/Crew level PMCS tasks and Organizational
level PMCS tasks.
30.25 LSA-036, Provisioning Requirements. This report is a summary of those
data recorded on the data tables identified for provisioning requirements.
The summary contains that data required for review at various provisioning
conferences (e.g., long-lead time items conference, provisioning conference,
etc.) and is used in the selection procedures to identify repair parts
requirements in support of the equipment to be fielded. The summary will
satisfy the deliverables cited in MIL-STD-1388-1A. Format contained in table
I and sample report on figure 39.
30.25.1 The following “header” data required to identify the specified
list(s) are not a part of the LSAR, but are contained in the LSA-036 summary:

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B
a. Procurement Instrument Identification (PII). A 19-position

alphanumeric entry used to identify a specific, contractual document. The PII
includes the PII number (PIIN) (13 positions), ‘and the supplementary PII
number (SPIIN) (6 positions).
b. Nomenclature of model or type number. A 21-position alphanumeric
entry used to specify the name, model, or type of equipment being provisioned.
c. Control Data. A 10-position alphanumeric entry used for control
information as specified by the requiring authority. This information may
consist of such items as identification of provisioning data in MIL-STD-1388-2
format or a Weapons System Code.
d. Prime Contractor's CAGE. A five-position alphanumeric entry which
identifies the prime contractor for the equipment being provisioned.
e. Submission Control Code. A five-position numeric entry used to
control the submission of provisioning data. The first submission will be
00001, and each subsequent submission is to be numbered sequentially, one
greater than the prior submission.
f. Date list submitted. A six-position numeric entry used to identify
the date of submission. The first two positions will identify the year, the
next two will identify the month, and the last two will identify the day.
30.25.2 DEDs for those data contained on the LSA-036 summary are contained in
appendix E. The first card appearing on an LSA-036 list is the header record.
Following this record, the LSA-036 report is sequenced by ascending PLISN in
Binary-Coded-Decimal (BCD), or Extended BCD Interchange Code (EBCDIC)
collating sequence. The PLISNs are then sequenced by ascending Card Format
Indicator (CFI). Multiple CFIs are sequenced by Type of Change Code (TOCC) in
the following order: blank, D, G, L, Q, and M. Finally, within the TOCC,
items are sorted by ascending Card Sequence Number (CSN).
30.25.3 The report will display the following provisioning report control
data:
a. CSN. A two-position numeric code which is used to sequence multiple
data input cards for a specific card format indicator. The initial card entry
is coded 01. Subsequent cards are coded 02-99.
b. CFI. A one-position alphabetic code: A-H, J-L used to identify a
card format and content.
c. Reference Designation Overflow Code (RDOC) (Card/Block, D/45, on the

LSA-036 summary). A one-position alphabetic code: A and B used to link a
long Reference Designation which exceeds 32 characters. Code “A” is entered
against the first 32 characters, and code “B” is entered against the last 32
character-s.
d. Multiple-Configuration UOC. A one, two or three-position alphanumeric
code that indicates the configuration(s) of a system/equipment on which the
item under analysis is used based on the UOC (DED 501) assignments. The UOC
is alphabetic in the sequence A-Z, followed by AA-ZZ (less Is and Os). A
blank UOC indicates that the assembly/part is used in all configurations. For

MIL-STD-1388-2B
APPENDIX B
example:
If there were three different model designations (in

. table XC) for a
given PCCN as shown below:
Model UOC (DED 501)
(V)l A
(V)2 B
(V)3 c
A single UOC is assigned to each item’s application based on the number

of model configurations that the LCN is used on (table HO). (The
combination model UOCs (D, E, and F) are automatically generated. )
LCN UOC System/End Item
lA1 (blank) (Used in all configurations)

1A2 A (Used in (V)l configuration only)
1A21 B (Used in (V)2 configuration only)
1A3 C (Used in (V)3 configuration only)
1A31 D (Used in (V)l and (V)2 configurations)
1A312 E (Used in (V)l and (V)3 configurations)
1A318 F (Used in (V)2 and (V)3 configurations)
e. Quantity per End Item (QPEI) (DED 317). The QPEI (three options) may
be computed during the LSA-036 report preparation using the formulas provided
in the data definitions.
f. NHA PLISN (DED 258) and Overhaul Replacement Rate (ORR) (DED 281)
Assignment. The NHA PLISNs may be assigned during the LSA-036 report
preparation based on the item having a P- source code, an ORR entry, and a
higher assembly PLISN having an SMR Code of P--D-. The base ORR of the item
is multiplied by the Quantity per Assembly (QPA) for each succeeding indenture
level. For example:
PLISN IND CD SMR QPA NHA PLISN NHA-IND ORR
CFFF F PADZZ 0002 CEAA N 005

CEAA E PAHDD 0002 CDEE N 001
CDEE D PAHDD 0003 CCDD N
CCDD c PAFHH 0001 CB12 N 002
CB12 B PAODD 0002 AAAA E 001
AAAA A PAODD 0001
For PLISN CFFF, the Overhaul PLISNs and associated ORRs are:
OVERHAUL PLISN ORR
CDEE 015
CB12 030
AAAA 030
NOTE: PLISN CEAA is the item’s immediate NHA PLISN. PLISN CCDD is
disqualified because it is SMR Coded PAOHH.
MIL-STD-1388-2B
APPENDIX B
g. Same as PLISN (DED 364). The Same as PLISN may be assigned during the
LSA-036 summary preparation.
h. Indenture Code (DED 162). The “A” indenture code (for the XB table
system/end item) is assigned by the LSA-036 process.
30.25.4 LSA-036 Update and Design Change Notices. There are five basic types
of LSA-036 updates which can result when LSAR data is added, changed, or
deleted affecting provisioning lists (PL) previously delivered. These
transactions can be automatically generated using a validated LSAR ADP system
by establishing baseline records upon initial submission of the LSA-036.
These transactions are based upon a comparison of the current LSAR
provisioning oriented data tables and provisioning data baselined by a
previous LSA-036 submittal.
a. Standard Data Update. For each LSA-036 card affected by data which
has been added or changed since the previous PL delivery or LSA-036 update,
mandatory data, i.e., PCCN, PLISN, CSN, and CFI, an “M” TOCC and the added/
changed data only are entered. If data has been deleted, a “G” is entered in
the TOCC and in the left most position of each field deleted on the
appropriate LSA-036 card. Data deletions and changes/additions occurring on
the same LSA-036 card will require both a change and deletion card for the
appropriate data.
(1) If all data on an LSA-036 CFI is deleted, a delete transaction

will be generated consisting of the PCCN, PLISN, CSN “01”, CFI (except A), the
key data associated with that CFI, and a “G” TOCC.
(2) When an entire PLISN record is deleted, a delete transaction will

be generated consisting of the appropriate PCCN, PLISN, CAGE, Reference
Number, and a “D” TOCC on the OIA card. Also , if the reference designation
exists, it is displayed with the PCCN and PLISN on the OID card with a “G”
TOCC. In addition, if any change authority related information is changed,
CFIS “F”, “G”, and “H” update transactions are also processed.
b. Quantity Data Update. If a quantity field is updated, mandatory data,

a “Q” TOCC, and the updated quantity data field(s) are entered. This will
only apply to the following data: QPA, QPEI, Total Quantity Recommended,
Allowance Item Code Quantity, Minimum Replacement Unit, Recommended Initial
System Stock Buy, Recommended Minimum System Stock Level, Recommended Tender
Load List Quantity, Quantity Shipped, Quantity Procured and Prorated Quantity.
If additional data displayed on the same LSA-036 card also changes during the
update, only one change card is entered with TOCC “Q”. If quantity data is
deleted, a change card is entered with a zero filled quantity and TOCC “Q”.
c. Key Data Update. Certain provisioning data are considered key and
associated data elements and are listed below. Changes to key data requires
the submission of both a delete and change card for the appropriate key data.
The deletion card should contain a “G” TOCC and the original key data. The
change card should contain an “M” TOCC with new key data and applicable
associated data. Deletion of key data will result in deletion of the
corresponding associated data.
KEY DATA ASSOCIATED DATA
(1) CAGE and Additional RNCC and RNVC
Reference Number
- 139 - supersedes page 139 of 28 March 91

MIL-STD-1388-2B
APPENDIX B
(2) NHA PLISN ORR, NHA IND.
(3) UOC None
(4) Reference Designation RDOC

RDC
(5) PLCC None
(6) Change Authority Number Serial Number Effectivity

Prorated Exhibit Line Item Number
Prorated Quantity
IC, Replaced or
Superseding PLISN,
R/S Indicator, Design Change Notice
(DCN) UOC, Total Item Changes
Quantity Shipped
Quantity Procured
(7) Serial Number Effectivity None
(8) DCN UOC None

(9) TM Code Figure Number
Item Number
(10) TM Code, Basis of Issue (BOI)

Figure Number TM Change Number, TM Indenture Code
Item Number Quantity per Figure
TM FGC
(11) TM Code Provisioning Nomenclature

Figure Number
Item number
(12) BOI-Control BOI-Quantity Authorized

BOI-End Item, BOI-Level
d. Associated Data Update. Changes to associated data require the

submission of a change card consisting of an “M” TOCC with the changed data
and entry of the applicable key data. Deletion of associated data requires
the submission of a deletion card with a “G” TOCC, a “G” in the left most
position of the associated data field and entry of the key data.
e. DCN. DCN information is not distinguished from other updated data for
a particular LSA-036 update using a validated LSAR ADP system. DCNs can be
processed as a separate and distinguishable report by specifying that DCN
affected data must be processed as an exclusive update, i.e., by performing an
LSA-036 update, entering the DCN information into the LSAR, and again running
an LSA-036 update. An option to obtain an LSA-036 report for updated data
pertaining to a specific Change Authority Number is provided on the LSA-036
report options. DCN information updates are similar to other update
transactions with the following exception: When a Change Authority Number and
Serial Number effectivity are entered, an “L” TOCC is entered for the replaced
item. If a quantity change occurs on a limited effectivity item, an “L” TOCC
is entered in lieu of a “Q”.

MIL-STD-1388-2B
APPENDIX B
30.30.2 When elapsed time and man-hours are reported, each number is preceded
by (M) or (P) to designate either measured or predicted values, respectively.
Where a measured value has not been input into the LSAR, the report will
default to the predicted value.
30.30.3 When the failure rate is reported, it is preceded by (M), (P), (A),
or (C) to indicate measured, predicted, allocated, and comparative analysis
values , respectively. Where a measured value has not been entered, the report
will default to the predicted, allocated, and finally comparative analysis.
30.31 LSA-056, Failure Modes, Effects and Criticality Analysis (FMECA)

Report. This summary consists of three parts. The first part contains FMECA,
criticality analysis, maintainability information, damage mode and effects
analysis, and minimum equipment listing information, as specified by
MIL-STD-1629. The second part is the criticality analysis information which
is a listing in descending order of each item’s computed criticality or
failure mode criticality number by SHSC. This part is selectable by SHSC(s)
and failure mode criticality numbers greater than a selected value. This part
should be used to identify candidates for RCM analysis or design reviews. The
third part is the failure mode analysis summary which consists of the failure
modes and failure rates of each repairable item. The report should be used to
identify failure modes which impact item criticality number and SHSC
assignment. The format is contained on figure 45. Spacing between rows and
columns is not critical on this report.
30.31.1 If part 1 of this report is selected, enter the SHSC (1, 2, 3, 4) of

he failure modes which are of interest. If the SHSC field is left blank,
then only SHSCs 1 and 2 will be considered. A selection must be made for
either minimum Failure Probability Level or minimum Failure Mode Criticality
Number. If both are selected, Failure Probability Level will be disregarded.
30.31.2 Parts 1 and 3, Item Criticality Number (Cr) is calculated using

formulas contained in DEDs 178 and 133 (Failure Mode Criticality Number).
30.31.3 In Part 3, an edit check is made on this report to ensure that the
sum of the failure mode ratios never exceeds 1.00 for a given LCN. If this
occurs, an “***” will be printed out under the Failure Mode Ratio header.
30.31.4 When failure rate is reported, it is preceded by (M), (P), (A), or

(C) to indicate measured, predicted, allocated, and comparative analysis
values , respectively. Where a measured value has not been entered, the report
will default to the predicted, then allocated, and finally comparative
analysis. In part II, overflows of Reference Number exceeding 16 positions
are printed on the next line immediately below the first position of the
Reference Number.
30.31.5 Part 1 of the report is sequenced by ascending LCNs, FMIs, MPCs, then
SHSCS. Part 2 is sequenced by ascending values of Failure Probability Level,
then LCN. Part 3 is sequenced by ascending LCNs.
30.32 LSA-058, Reliability Availability and Maintainability Summary. This

summary consists of two parts. The first part is the reliability summary
redesign which provides a narrative description for an item on which a
redesign is proposed. This part should be used to review potential candidates
for redesign. The second part details the level of repair to be performed on

MIL-STD-1388-2B
APPENDIX B
an item for all maintenance levels. This part is used to review the
reliability and maintainability factors for the’ repair time of an item. The
format is contained on figure 46. Spacing between rows and columns is not
critical on this report.
30.32.1 In part 1 of the report, Failure Mode Criticality Number or Failure

Probability Level may be used. However, Failure Mode Criticality Number
should be used whenever possible. Also, if the LCN type of subject LCN is
functional, then the reference number and CAGE may not appear. In part 2, the
(P) or (M) preceding the elapsed time values represent predicted and measured,
respectively. Measured values take precedence.
30.32.2 Part 1 of the report is sequenced by ascending LCNs, then FMIs. Part
2 is sequenced by maintenance level, then ascending LCNs and FMIs within each
maintenance level.
30.33 LSA-065, Manpower Requirements Criteria. This summary provides

manhour summary information by each task. The format is contained on figure
47. Spacing between rows and columns is not critical on this report.
30.33.1 The following formula applies for Mean Time Between Task Maintenance
Actions (MTBTMA) and Man-Hours per’ Person Identifier (M-HRS PER PERS ID):
Annual Operating Requirements

a. MTBTMAi - (Task Frequency)i
Where: i - task codei
b. M-HRS PER PERS ID is computed by summing all subtask mean man-minutes

per person identifier for each entry matching an identical person identifier
and SSC and then dividing this value by 60.
30.33.2 The report displays the system/component reference number. Within

each reference number, tasks are displayed by unscheduled/on equipment (task
interval codes F, G, and J; and task operability codes A, B, C, D, and E);
unscheduled/off equipment (task interval codes F, G, and J; and task
operability Code G); and, scheduled (all task interval codes except F, G, J,
and Y).
30.34 LSA-070, Support Equipment Recommendation Data (SERD). A report

describing requirements for and of one piece of support equipment. This
report will include administrative data, description of equipment, allocation
data, design data, and Integrated Logistic Support (ILS) requirements as
specified by MIL-STD-2097. Format contained in figure 48. Spacing between
rows and columns is not critical on this report.
30.34.1 The E-CAGE/PN (Equivalent CAGE and Part Number) code in section 2 is
generated based on whether or not the support equipment reference number and
CAGE has equivalent part numbers and CAGES. This is determined by searching
the HB table additional reference numbers and CAGES, and if any are found, a
“Y” code is produced for this field; otherwise, an “N” code is produced. If
any matches are found in table HB, they are output in section 2 (following the
Articles Requiring Support section) under the heading of Equivalent CAGE/PN(S)
(page 6 of the LSA-070 example).

MIL-STD-1388-2B
APPENDIX B
based on the repair code:
If position 4 (repair) is: position 5 (recoverability) must

be:
Z Z, A
O (2, 3, 4, 5, 6) Navy only O, F, H, G, D, L, A
F F, H, G, D, L, A
H H, G, D, L, A
G G, D, L, A
D D, L, A
L D, L, A
B Z, A
g. An assembly is SMR coded repairable (e.g., SMR-4 is not Z or B) but

has no parts breakout beneath it.
h. Items having the error codes 2 and 3 with PCCN selection are listed on
the LSA-080, part II only. Other errors are flagged with “**” to the right of
the line the error appears in part I and also displayed in part II. The error
messages are displayed on part II.
30.42.4 The report is sequenced in either ascending assembly reference number

and CAGE, or in ascending assembly PLISN and then components of assembly
PLISNs based on the selection option specified.
30.43 LSA-085, Transportability Summary. This report provides information

critical to the shipping and transport of major end items of equipment. It
includes environmental and hazardous material information necessary for safe
transport of an item by air, highway, rail, and sea. The format is contained
on figure 57. Spacing between rows and columns is not critical on this
report.
30.43.1 If the LCN type of subject LCN is functional, NSN and related data,
reference number, and CAGE may not be available. Overflows of Reference
Number exceeding 16 positions are printed on the next line immediately below
the first position of the Reference Number. This report is sequenced by
ascending LCNs.
30.44 LSA-126, Hardware Generation Breakdown Tree. This summary provides a

concise summary of information pertaining to a system/equipment breakdown.
Each item is blocked in and indented to the proper level in the hardware
family tree and displayed by line relationship beneath the appropriate
assembly in which the item is contained. The format is contained on figure
58. Spacing between rows and columns is not critical on this report.
30.45 LSA-151, Provisioning Parts List Index (PPLI). This summary provides a
cross reference between reference numbers and the applicable PLISN of the
provisioning list as required by MIL-STD-1388-1A. It provides a ready
reference of usage and location within the provisioning list for a given
reference number. The report can be generated in reference number, LCN, or
PLISN sequence. Additional data which further describes the item at its usage
level(s) are provided for the user’s information (i.e., item name, quantities,
SMR, etc.). The format is contained on figure 59. Spacing between rows and
columns is not critical on this report.

MIL-STD-1388-2B
APPENDIX B
30.46 LSA-152, PLISN Assignment/Reassignment . This summary provides a
listing, by reference number, of PLISN, Indenture Code (IC), NHA PLISN, and
PRIOR ITEM PLISN, assigned by the LSAR system based on parameters of the
assignment select card. The summary will depict the file content before and
after the assignments or reassignments are made (PLISNs are assigned using the
EBCDIC collating sequence). As an option, this report can be used to assign
provisioning related control and reference data to the LSAR Parts Master File.
The format is contained on figure 60. Spacing between rows and columns is not
critical on this report.
30.46.1 It is necessary that the LSAR be properly structured using either a

uniform (nonbroken) LCN structure when applying either a classical or modified
classical LCN assignment technique; or an LCN-IC (Table XB) assignment without
missing or unlinked indenture levels, when LCNs are assigned using the
sequential method. Using the LSA-080 report, the analyst can review the file
for correct structure, or by using the LSA-152 report detect error conditions
in file structure.
30.46.2 The LSA-152 report consists of two parts. Part I will only be output
when an error in file structure is encountered, or when the PLISN assignment
(with selected PLISN spacing) exceeds the limit of 9999 for the proposed
assigned PMF candidates. When these occur, the error location in the file is
depicted on the report with a display of the unlinked or remaining file
segment. If an error condition does occur, the LSA-152 process will not
assign any PLISNs, but will continue processing to determine whether
additional error conditions exist in the file. Validated LSAR systems will be
required to have the capability to produce an error listing for the LSA-152
report. However, the format, messages and explanation of those messages for
the error listing is vendor dependent. Part II of the report reflects the
results of the PLISN assignment/reassignment ; only a Part I or a Part II will
be produced in a processing cycle. Also, PLISN assignment must occur as an
exclusive cycle .
30.46.3 The report selection for PLISN assignment occurs within a PCCN and
optionally a Start and Stop LCN range. ALC is not a selection option.
Alternate LCNS (ALCs other than basic - 00) must be considered when assigning
the basic LCN PLISNs because alternates may have basic items as NHAs. A row
in table HO creates the end item (XC) to part application (HG) relationship.
One HG row cannot be related to multiple PCCNs except when the item is a
subordinate end item. When the item is a subordinate end item, HO would have
one row depicting the end item relationship (end item and item LCN-ALCs are
the same), and one or more rows showing the relationship to the system.
Having the end items located in the XC table, and the fact that no item except
subordinate end items can be linked to more than one PCCN through table HO,
makes the Suppression Indicator Code obsolete.
30.46.4 Since there are unlimited “correct” structuring techniques using the
ALC, there is no system edit to detect errors in file structure when the ALC
is utilized, other than missing an indenture level when the ALC is being
sequenced to the “basic” LCN structure. ALC assignment errors, therefore, can
only be detected by a manual review of the LSA-152 or LSA-080 reports.

MIL-STD-1388-2B
APPENDIX B
30.46.5 There is a wide range of options when using the PLISN assignment
routine:
a. NHA PLISNs and/or ICs may be assigned to the PMF, if this option is
selected on the 152 report.
(1) If the file is constructed using the classical/modified

classical LCN assignment technique, the IC may be assigned, provided the LCN
structure exists in the XA table. Asterisk ICs may be assigned to the parts
file based on the ICC of “9” representing kit components being previously
assigned (Table HG). An option is also available to assign a constant NHA
PLISN indicator of “N” against each NHA PLISN assigned to the HH table.
(2) When a sequential LCN assignment method is utilized, the LCN
structure field may be left blank in the XA table, and the LCN-ICs must be
entered in the XB table in order to assign NHA PLISNs. The IC (Table HG)
should be that of the provisioned end item, while the LCN-IC should be related
to the system level in the LSAR.
b. When assigning PLISNs for a subordinate end item, the IC is not

assigned to the HG table. For example, a separately provisioned end item at
the “C” indenture to the system (LCN-IC, table XB) will have an IC of “A” come
out on the LSA-152 and LSA-036 reports, but will keep its IC of “C” assigned
under the system end item assignment. All components to the subordinate end
item will still have their IC assigned as before. For example, a “D”
indenture item item under the “C” indenture subordinate end item will have a
“B” IC assigned when PLISN assignment is run against the “C” indenture
subordinate end item.
c. PLISNs may be assigned only to items that qualify by PTD Selection

Code for a specified Provisioning List (PL) or lists (Table HG).
d. PLISNs may be assigned in either topdown (LCN) or Reference Number

sequence. When PLISNs are assigned in Reference Number sequence, the system
will lock out the option to assign NHA PLISNs/ICs.
e. PLISNS may be assigned as either all alphabetic, alphanumeric,

numeric, or, first position alphabetic, then second through fourth position
numeric,
f. A starting PLISN value may be specified on the report selection card.
g. PLISN values of “W” through “AMHZ” may be reserved for the system
level and separately provisioned end items (Model Reserve). If this option is
selected, a starting model PLISN value may be specified (within the given
range). If none is selected, the first model PLISN assignment will be “AAM”.
h. PLISNs may be assigned to overlay old PLISN values established in the

file; to overlay PLISNs and to move the old PLISN value to the Prior Item
PLISN field; or to assign PLISNs only to items that do not have a PLISN value
already established (insert) (Insert/Overlay selection on report). If the
insert option is chosen, PLISNs already assigned to the file must match with
the LCN structure or LCN-ICs of the selected LCN range.
i. It is possible to skip PLISN values between the assigned PLISNs for

MIL-STD-1388-2B
APPENDIX B
future use, when the item is impacted by Design Change Notice or Engineering
Change Proposals, or for when the item having PLISNs assigned is not fully
broken down to piece part level. This option cannot be utilized if the insert
option (paragraph h) is in use. PLISN gaps may be as great as 1,121.
j. PLISNs may be assigned to items based upon the Data Status Code (Table
HG) contained against the qualified item. This can be useful when performing
incremental provisioning on an LSAR that is not fully mature.
30.47 LSA-154, Provisioning Parts Breakout Summary. This report provides a

two-part summary of each reference number and can be utilized to assist in
performance of the DOD Replenishment Parts Breakout Program. Included in
part I of the report are critical pricing and breakout program information.
It is sequenced in ascending reference number and CAGE. Part II contains
selected parts application data and is sequenced in ascending LCN. If both
parts are selected, a separate page of the report for each reference number
and CAGE is prepared. If only part I is required, there is no page break
between reference numbers. The report may be selected by contractor technical
information codes, source codes, reference number or report parts. The format
is contained on figure 61. Spacing between rows and columns is not critical
on this report.
30.48 LSA-155, Recommended Spare Parts List for Spares Acquisition Integrated
with Production (SAIP). This summary provides the data required for SAIP
list, as specified by MIL-STD-1388-1A. Either the unit of measure or issue
prices may be displayed and are presented by ascending reference number and
CAGE. Items are qualified for the SAIP List based on entry of “Y” in the SAIP
code (DED 391). The format is contained on figure 62. Spacing between rows
and columns is not critical on this report.

MIL-STD-1388-2B
APPFNDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MXL-STD- 1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

+MIL-STD-1388-2B
APPENDIX B
Ln
ii
- 165 - Supersedes page 165 of 28 ) March 91

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B
- 193 - * REPRINTED WITHOUT CHANGE

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B
Supersedes oage 262 of March 91 - 262 -

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX B

MIL-STD-1388-2B
APPENDIX D
APPENDIX D
APPLICATION AND TAILORING GUIDANCE

FOR THE LOGISTIC SUPPORT ANALYSIS (LSA) RECORD (LSAR)
10. GENERAL.
10.1 Purpose. The LSA process associated with a materiel acquisition program
is iterative in nature. The LSAR provides a structured, standardized, yet
flexible approach to the documentation and use of the data required to
effectively accomplish contractually invoked LSA tasks. To be effective, LSA
documentation must be initiated early in the acquisition life cycle, must be
updated to reflect changes in the hardware design and support concept, and
must be tailored to be commensurate with individual program requirements,
constraints, and characteristics. The LSAR data is generated as a result of
the performance of LSA tasks. Tailoring of both the LSA tasks to be
performed, and the resultant LSAR data produced as a part of LSA task
documentation, is mandatory. Limitations on system development funding make
it imperative that LSA be applied judiciously to improve hardware design and
support concepts, not merely to collect LSAR data. This appendix provides
guidance for appropriate application of the LSAR during each phase of a
system’s life cycle and the procedures for tailoring of the LSAR data records,
elements, and standard reports to satisfy program requirements at minimum
cost . This appendix does not contain any requirements and is not to be
implemented in contractual documents. The user of this appendix may be a
Department of Defense contracting activity, government in-house activity,
prime contractor, or subcontractor wishing to impose LSAR requirements.
10.2 How to Use this appendix. Tailoring of the LSAR requirement begins with
the identification of the life cycle phase of the system/equipment acquisition
effort. Paragraph 20 of this appendix addresses the applicability of the LSAR
for each of the life cycle phases. Figure 69 depicts general applicability of
the LSAR data tables to the system/hardware breakdown. Once the life cycle
phase has been established, tailoring of the LSAR requirement can be
performed. Paragraph 30 provides a stepwise procedure for tailoring the LSAR,
based upon MIL-STD-1388-1 tasks and subtasks, related engineering and
Integrated Logistic Support (ILS) element analysis efforts which result in
LSAR data, and deliverable logistic products specified by data item
descriptions (DID) to be included in the contract. The result of this
tailoring process is a completed DD Form 1949-3, LSAR data requirements form,
identifying the LSAR data table and data element requirements for the specific
phase of the acquisition effort (see figure 71). Guidance for determining
LSAR completion schedules is contained in paragraph 40. The final step in
tailoring the LSAR effort involves contractual delivery of the LSAR data
itself. Paragraph 50 discusses alternatives for delivery of the LSAR data.
20. LSAR APPLICATION AND USE BY LIFE CYCLE PHASE.
20.1 LSA process. The LSA process is applicable to all phases of the life
cycle and all types of acquisition efforts. Tailoring of the LSA tasks, and
additionally, tailoring of the LSAR documentation requirements are dependent
upon the life cycle phase, type of acquisition, and degree of program control
desired. In relation to the acquisition life cycle, the LSA process can be
divided into two basic categories: (a) LSA encompassing laboratory research

MIL-STD-1388-2B
APPENDIX D
and development (R&D), preconceptual and conceptual studies, and development

of conceptual designs; and, (b) LSA for Design Development (DD) to include
late R&D and the demonstration/validation through deployment phases. Both
categories of LSA have as a primary objective:
a. Influence of design concepts and hardware design to reduce operating

and support costs and increase readiness and sustainability.
b. Identification of support resource requirements progressively and

concurrently with the hardware design.
20.2 Concept exploration and definition (CE) Phase. LSA is initiated in the
earliest studies and design efforts and continued during all phases of the
materiel development and acquisition program. Initially, the LSA is primarily
directed toward establishing support related factors and constraints, which
must be used in developing design guidelines and trade study plans. Initial
LSA is also directed toward identifying targets of improvement; of objectives
or goals for reliability, availability, maintainability, and life cycle cost
(LCC); potential logistics problems, constraints and risks; and, the
projection of logistics resource requirements and costs. During this effort,
the LSA program continually interfaces with other system engineering programs
through historical data reviews, tradeoff analyses, use studies, design
projections, and other LSA tasks to arrive at the most cost-effective materiel
design concept(s) and acquisition plan(s) for further examination, study, and
development. In fact, LSA task 301 accomplishment produces a task inventory
that can be used by all engineering specialties. The results of the LSA
effort are embodied in the program documents and supplemental technical
reports. These are required in the materiel acquisition decision process
prior to entry into the demonstration and validation phase. The limited
volume of LSAR data is usually produced by the requiring authority to define
and document system level requirements. Figure 70 suggests the LSAR data
which might be generated at this time. However, tailoring LSAR data
requirements is mandatory, and not all of these elements may be required to
support LSA objectives.
20.3 Demonstration and validation (DVAL) phase. For most development

programs, the second category of the LSA effort begins with this phase. The
data elements completed within each table are dependent upon the analysis
tasks specified and the DIDs placed on contract (these aspects are covered in
paragraph 30 of this appendix). Because of the LSA efforts in the earlier
phase, the requiring authority is more aware of system requirements and
possible shortfalls and can better monitor subsequent performing activity
system development. With this awareness of the system, the requiring
authority can require the performing activity to justify any deviations or
changes in the original concept. To more fully utilize the LSAR documentation
previously developed, contracts should specify that repair and support
requirements be documented for all maintenance levels down to major
subsystems. This data can be used to verify data derived for lower
assemblies/parts, and conversely, for the system and major subsystems.
20.3.1 During the DVAL phase, the LSA is directed toward: (a) influencing
the materiel design by refining and updating support related design.
guidelines, and by challenging design characteristics which impose unnecessary
or costly support requirements; and, (b) updating and refining logistics
support planning data developed during the preconcert and concept phase. LSA

MIL-STD-1388-2B
APPENDIX D
documentation during this phase should provide the data to help further define
support concepts, cost estimates, potential logistics problem areas,
technological advances, or additional design improvements and test
requirements.
20.4 Engineering and manufacturing deployment phase. During this phase, the
LSAR effort is a continuation of the effort conducted during the DVAL phase.
The LSAR data tables are completed to the hardware indenture level identified
on figure 69, and the resulting data is used to develop logistics support
requirements for testing, deployment, and operation.
20.5 Production and deployment phase. The LSAR data established during the
development phases is retained during this phase to support the logistics
analyses that occur as a result of engineering design changes. In addition,
the data is used to evaluate the system’s performance after it is deployed to
determine the impact of future equipment modifications or support
requirements. The LSAR data would be used to establish design changes, goals,
and requirements for succeeding generations of matetiel acquisitions.
30. TAILORING LSAR REQUIREMENTS. The extent, and consequently the cost, of
LSAR inputs and outputs required to document and support the analyses of LSA
tasks will vary from program to program. These variations are attributable to
such factors as: the degree of LSA program visibility and control desired by
the requiring authority; life cycle phase; hardware complexity; and, the
specific acquisition program characteristics (e.g. , new development, major
modification, nondevelopmental). In addition, the data requirements
identified in this standard have been designed to accommodate the
documentation and data manipulation to support Army, Air Force, Navy, and
Marine Corps requirements. Each service has expressed requirements for unique
capabilities not generally applicable to the other services. For the above
reasons, the blanket purchase of the LSAR data elements and reports is an
ineffective and costly approach to the utilization of the LSAR. To realize
maximum benefit from the application of the LSAR, it is imperative that
extreme care be exercised in the contractual imposition of the LSAR
requirements is not only concerned with the exclusion of unnecessary data
requirements, but also, and just as important, with the identification of all
requirements which will eventually be needed to support a specific LSA program
effort. Failure to adequately identify data requirements can be just as
costly as the over purchase of data. To that end, each functional and
engineering specialty area must play in the tailoring of the LSAR, including
manpower and human factors engineering personnel. The guidance contained in
the following sections of this appendix have been arranged in a logical,
stepwise sequence to assist in the optimum selection of LSAR features.
30.1 LSA task selection. The initial step in tailoring of the LSA data
requirements involves selection of the analyses tasks described in
MIL-STD-1388-1, which are to be accomplished. Detailed guidance for task and
subtask selection, with respect to acquisition program characteristics,
program phase, and information requirements associated with primary system
developmental milestones, is provided in appendix A of MIL-STD-1388-1.
Selection of some LSA tasks will result in data which is documented directly
into the LSAR. Output from other tasks becomes the input to follow-on
analyses, and as such, relates only indirectly to the LSAR documentation.
Table 11 provides a list of the LSA tasks and subtasks which relate directly
to the LSAR data tables. A review of each data table is mandatory to ensure

MIL-STD-1388-2B
APPENDIX D
that only those data elements required to document the tasks are procured.
Once established, the specific data elements required to document the tasks
should be recorded on DD Form 1949-3 (see figure 71).
30.2 Interfacing and coordination with other program elements. Data required
to conduct an effective LSA program may also be developed as a result of
analyses conducted in support of associated program elements such as:
a. System/equipment design program
b. System/equipment reliability program
c. System/equipment maintainability program
d. Human engineering program
e. Standardization program
f. Parts control program
g. System safety program
h. Packaging, handling, storage, and transportability program
i. Initial provisioning program
j. System/equipment testability program
k. Survivability program
l. Technical publications program
m. Training and training equipment program
n. Facilities program
o. Support equipment program
p. Test and evaluation program
q. LCC program
It is essential that coordination and interfacing of engineering disciplines

and ILS functional elements be affected to maximize the usage of data
developed by each program element, thereby, realizing analysis economics and
avoiding the generation of incompatible ILS products. Effective coordination
with related program elements can produce benefits by eliminating costly
duplications of effort.
30.2.1 Identification of the engineering and ILS functional element

requirements which interface with the LSA process, and which generate LSAR
data, is the next consideration in the tailoring process. Results of analyses
from other program elements can be used as source data for LSA tasks and vice
versa. For example, inputs from the design, reliability, maintainability,
human engineering, safety, and other program elements may be required to

MIL-STD-1388-2B
APPENDIX D
satisfy the requirements of task 401, Task Analysis, as described in

MIL-STD-1388-1. Benefits of effective interfacing and coordination may also
be achieved by utilizing the features of the LSAR to record, store, and
manipulate data in support of requirements levied by other program elements.
As an example, the LSAR data tables can be used to produce the LSA-018, Task
Inventory report. This report is used and reviewed by human systems
integration specialists, as well as the LSA program.
30,2.2 Once the related program elements have been established, the next step
in the tailoring process is the identification of the logistics DIDs
associated with each element of ILS that will be placed on contract. A
detailed review of the DIDs is required to determine the specific data element
requirements of each. Table III provides a listing of the commonly cited
DID’s associated with each element of ILS that can be satisfied by the LSAR
data. This listing is not intended to be inclusive of all logistic related
DIDs and the user is encouraged to apply the same logic in table III to other
DID’s not listed which may be partially satisfied using the LSAR. The,
objectives and use of each DID are summarized in table III, along wit-h a
description of the extent of interface with the LSAR data tables and LSAR
reports. The user of this appendix should use table III to determine the
extent to which the LSAR data can be used to satisfy the logistics DIDs that
will be placed on contract. If LSAR reports can be used to satisfy a DID,
then the specific LSAR data elements can be established by using appendix B,
figure 14, LSAR Input to Report Matrix. This matrix identifies all of the
LSAR reports and the input data elements required to generate each
(e.g., DI-ILSS-81140A, Maintenance Allocation Chart (MAC), can be satisfied by
using the LSA-004 report). Finding this report across the top of figure 14
and then reading down the column will provide the user with the specific data
elements and LSAR data tables required to produce the report. This process
would be repeated for each DID identified. This information would then be
input on DD Form 1949-3, in order to establish the total LSAR data
requirements from both an analysis and a logistics data product standpoint.
40. SCHEDULING OF THE LSAR DATA. This paragraph addresses scheduling the
development of the LSAR data, so that it can be used in a timely manner as
source data for the development of the contractually cited logistics products
discussed in paragraph 30. This guidance is applicable to any type of
development effort and any phase of the life cycle. To establish timely
completion of the LSAR data, the user must first establish the scheduled
completion dates for the data products that utilize LSAR data. Required
delivery dates for the products specified by DIDs should be established in
conjunction with preparation of the solicitation package, and should take into
account the significant milestones of the development effort.
40.1 Once the scheduled completion dates for all chosen DIDs have been
established, the user can determine the required completion scheduled for the
LSAR. Figure 14 provides a cross-reference list of the LSAR data elements and
the reports that use the data elements on a given data table for product
development. Since the table is sequenced by data table, the completion date
of each data table can be established by listing the delivery dates on the
DIDs and then choosing the earliest date as the scheduled completion date for
that LSAR data table. This approach must be tempered by the range of data
elements on a data table that are required as source data for development of a
DID product. For example., the scheduled delivery date for DI-ILSS-81285, Long
Lead Time Items List, may be 120 days after contract award, while the delivery

MIL-STD-1388-2B
APPENDIX D
date of DI-ILS-81285, Provisioning Parts List, is 24 months after contract
award. This does not mean that all data tables related to support item
identification and application are to be completed 120 days after contract
award, but rather, specific data elements for parts with certain production
lead times would be completed on data tables of support items to satisfy
DI-ILSS-81285, Long Lead Times Item List.
40.2 Completion dates for the LSAR reports can be established by using the
required delivery dates of the DIDs that use the given report for product
development. Additionally, the scheduled completion date for the LSAR data
tables, to include the specific data elements required to produce an LSAR
report, can be established by using figure 14. For example, if
DI-ILSS-81140A, MAC, had a required delivery date of 18 months after award of
contract, then the LSAR output report, LSA-004, must be available at that
point for product development. Additionally, by using figure 14, it can be
established that specific data elements on the listed data tables must be
completed for product development of DI-ILSS-81140A (and report LSA-004).
40.3 This approach to scheduling completion of the LSAR data must take into
account interim product delivery dates, final product delivery dates, and
scheduled updates to final products, Each of these dates will impact the
range of LSAR data required, depth of data required (i.e., the hardware
indenture levels and maintenance levels specified), and the number of updates
to the LSAR data required. The LSAR completion schedule must then be
coordinated with related program schedules (i.e. , drawing release) to ensure
availability of data for LSAR development. Finally, by establishing an LSAR
completion schedule which is timely for DID product development, the user now
has the additional option of not requiring delivery of LSAR data as a separate
data item. In effect, completion of a deliverable product is intimately tied
to the LSAR data and quality.
50. ALTERNATIVES FOR DATA DELIVERY. The last step in the LSAR data tailoring
process involves delivery of the LSAR data itself. LSAR data can be delivered
in q anual form, LSAR reports, LSAR data table files, or through interactive
access to a contractor LSA database. The use of a manual LSAR data file is
generally applicable to simple hardware systems, limited report requirements,
infrequent use of the data, and uncomplicated reports. Implementation of an
automated LSAR is generally applicable to a complex hardware system, multiple
and varied applications, ability to produce tailored reports, on demand use
with short response time, and the ability to manipulate the LSAR data for
specialized reports.
50.1 An automated LSAR presents the additional decision option of who will be
made responsible for Automated Data Processing (ADP) of the LSAR data.
Normally, the performing activity would be responsible for data processing,
using a validated independently developed LSAR software system. The
alternative to this is to use the in-house ADP capabilities of the requiring
authority, thus requiring only a data entry effort by the performing activity.
Once the decision is made who will be responsible for automated processing of
LSAR data, the media for delivery can be established.
50.2 Delivery of the LSAR reports contained in appendix B is one option for
delivery of data in an automated LSAR environment. The LSAR reports are
intended to satisfy the delivery requirements of specific logistics products
(e.g., MAC, Maintenance Plan, Support Equipment Recommendation Data, etc.).

MIL-STD-1388-2B
APPENDIX D
As such, the LSAR reports are static presentations of LSAR data and cannot be
updated or processed further after delivery. They offer the least flexibility
for LSAR data use from an automated standpoint. Requiring LSAR reports as
deliverables is appropriate for final product delivery, or when no further
processing capability is available or necessary.
50.3 Delivery of the LSAR relational tables via magnetic tape/disc/drum is
another option for delivery of data in an automated environment. This option
also includes the delivery of LSAR data files that require processing from the
LSAR relational tables (such as input files for provisioning, Defense
Logistics Information Systems screening, or packaging system data). An
internal processing capability is required for each LSAR data file procured by
the requiring authority. Delivery of the LSAR relational tables provides the
capability to subsequently produce any of the LSAR reports, other data files,
and to produce ad hoc reports via the query capability of a validated LSAR
Relational ADP system. Separate delivery of the LSAR data files places the
responsibility for their generation with the performing activity rather than
the requiring authority. Because of the flexibility provided by these
processable data files, they can be used to satisfy both interim and final
LSAR delivery requirements. Periodic delivery can reduce time spent for
onsite data reviews by providing a vehicle for advanced review of the data.
Final contract deliverables can be consolidated and reduced by internal
processing of LSAR data files, in-part or in total. In addition, validated
LSAR systems are required to have the capability to produce and load standard
outputs not only for all data tables, but also standard outputs for “change
only” data (changes to the data tables since the previous submittal of the
LSAR data).
50.4 The third LSAR deliverables option is interactive access to a performing
activity’s LSA database by using a validated LSAR Relational software system.
Interactive access includes the ability to selectively retrieve, review and
print, and process performing activity LSA source data. Interactive access
for faster requiring authority review of LSAR information represents more of a
performing activity service capability than a specific deliverable
requirement. This capability makes the most current authorized data available
to the requiring authority and eliminates the time required for preparation
and submission of deliverable products. It can also significantly reduce the
time requirement for onsite reviews, while supporting internal analyses and
planning that requires up-to-date supportability information. Interactive
access provides the greatest flexibility for using LSAR data, either by
utilizing the performing activity’s automated LSAR capabilities, or by
electronically transferring the data for further internal processing. Since
interactive access can support interim and final delivery of both LSAR reports
and data files, it may entirely eliminate the need to bring the LSAR data in-
house. (However, it is advisable to have the LSAR relational table files
delivered at contract completion.) The interactive access service can be very
effective for satisfying LSAR deliverable requirements during the early life
cycle phases when the volume of LSAR data is low. In latter phases,
interactive access may be more appropriate as a contract compliance, “change
only” data review, and internal analysis tool rather than for bulk transfers
of complete LSAR master or data files.

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX D
DATA TABLE DED DATA ELEMENT
AA 001 Achieved Availability
064 Crew Size
164 Inherent Availability
222 Maximum Time To Repair
223 Operational Mean Active Maintenance Downtime
236 Operational Mean Time To Repair
454 Total Systems Supported
AB 021 Annual Number of Missions
022 Annual Operating Days
024 Annual Operating Time
228 Mean Mission Duration
273 Operational Availability
BB 180 Item Function
207 Maintenance Concept
315 Qualitative and Quantitative Maintainability
Requirements
CA 427 Task Code
430 Task Frequency
431 Task Identification
358 Facility Requirement Code
358 Tool/Support Equipment Requirement Code
358 Training Equipment Requirement Code
EE 078 Description and Function of Support Equipment
188 Justification
FA 118 Facility Name
FC 107 Facilities Maintenance Requirement
GC 007 New or Modified Skill Additional Requirements
012 Additional Training Requirements
094 Educational Qualifications
188 Skill Justification
FIGURE 70. Concept exploration and definition phase LSAR.
- 344 -
MIL-STD-1388-2B
APPENDIX D
TABLE II. LSAR Data Tables Related to MIL-STD-1388-1 Tasks.
MIL-STD-1388-1
TASK/SUBTASK APPLICABLE LSAR DATA TABLES
201.2.2 AE, AF, AH, BB, BL
203.2.3 BD, BE, FA, FB, FC
205.2.2 AA, AB, AC, AD, AE, AG, AH, AI, AJ, GA
301.2.4 BA, BB, BC, BD, BE, BF, BG, BH, BI, BJ, BK, BL, CA,
CB, CC, CD, CE, CF, CG, CH, CI, CJ, CK, GA, XI
301.2.5 AA, AB, AC, AD, AE, AG, CA, CB, CC, CD, CE, CF, CG,
CH, CI, XI
303.2.7 AI, XA, HG
401.2.1 CA, CB, CC, CD, CE, CF, CG, CH, CI, XI
401.2.2 CA, CB, CC, CD, CE, CF, CG, CH, CI, XI
401.2.3 EA, EB, EC, ED, EE, EF, EG, EH, EI, EJ, EK, EL, EM,
FD, GB, GC, GD, UA, UB, UC, UD, UE, UF, UG, UH, UI,
UJ, UK, UL, UM, UN
401.2.4 EE, GA, GB, GC, GD
401.2.5 CA, CB, CC, CD, CE, CF, CG, CH, CI, FA, FB, FC, FD,
FE, XI
401.2.7 JA, JB, JC, JD, JE, JF
401.2.8 HA, HB, HC, HD, HE, HF, HG, HH, HI, HJ, HK, HL, HM,
HN, HO, HP, HQ, HR, XB, XC, XD, XE, XF, XG
401.2.9 All tables as applicable, except the “A” tables
401.2.10 All tables as applicable
401.2.12 HA, HB, HG

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPEPNDIX D

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX D

MIL-STD-l388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX D

MIL-STD-1388-2B
APPENDIX E
APPENDIX E
DATA ELEMENT DICTIONARY
10 PURPOSE. This appendix provides the Data Element Dictionary for the
Logistic Support (LSA) Analysis Record (LSAR) and information for interpreting
and using it. The dictionary contains all the data elements and names that
appear on the LSAR data relationship tables.
20 SECTIONS. The dictionary is divided into three sections.
20.1 Section 1: Index of data element titles. This section contains listing
of data element definition (DED) numbers and titles. For each DED, the rela-
tional table location(s) in which the data element appears, by table and ele-
ment codes, are depicted.
20.2 Section 2: Listing of data element codes. This section is an al-
phabetical listing of the data element codes used on the LSAR data relational
tables with cross-references to the data element roll names they represent.
Also listed are the applicable DED numbers.
20.3 Section 3: DEDs. This section contains definitions for all data ele-
ments that appear on the LSAR data relationship tables. The DED contains some
or all of the following entries. When a standard data element acronym ap-
plies, this is also listed in this section.
a. DED number
b. Data element title with acronym
c. Field format
d. DED
e. Data item(s)
f. Data code(s)
g. Role name(s)
20.3.1 Format. The general format for the DED is as follows:
DED # DATA ELEMENT TITLE FIELD FORMAT

(ACRONYM)
DATA ELEMENT DEFINITION
DATA ITEM(S) DATA CODE(S)
ROLE NAME(S)
Example of actual DED entry:
MIL-STD-1388-2B
APPENDIX E
339 RELIABILITY/MAINTAINABILITY 1AF-

INDICATOR CODE
A code used to indicate whether the reliability and maintainability

parameters entered on the card are allocated, predicted, measured, or
comparability analysis values.
Comparability analysis C
Allocated A
Predicted P
Measured M
20.3.2 Definition of terms.
20.3.2.1 DED number. A sequentially assigned number to each data element in

the dictionary for use in locating and referencing it throughout the dictio-
nary and data entry instructions (appendix A).
20.3.2.2 Data element title. The noun phrase name used to identify the data
element. Sufficient adjectival modifiers are used with the noun name to en-
sure title uniqueness.
20.3.2.3 Field format. A specification for the length, type, positional jus-
tification, and decimal placement of a data element field, or subfield there-
of, as described below:
a. Length. The number of character positions in the data element. In

the event the length is variable, the maximum length is specified.
b. Type. A specification of the character type, wherein:
“A” specifies that all characters of the data entry are upper case
alphabetical.
“N” specifies that all characters of the data entry are numerical.
“X” specifies that characters of the data entry are upper case
alphabetical, numerical, special, or any combination thereof.
“D” specifies that characters of the data entry are numerical with
floating decimal. Decimals may be entered as required or
exponentially, e.g., “0.0000325” or “3.25E-5”.
c. Justification. Specifies from which side of the field the characters

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

MIL-STD-1388-2B
APPENDIX E
DED DATA ELEMENT TITLE TABLE LOCATIO&
503 Utilization Ratio AE. UTRATIAE
504 Venting and Protective Clothing JF.TRANARJF, JF.TRANCDF(L)

Requirements
505 Wearout Life BA.WEOULIBA
506 Wheeled Axle and Suspension JD.WHTRLOJD, JD.TREINCJD(D)

Requirements
507 Wheeled Inflation Pressure JC.WHINPRJC
508 Wheeled Number of Plies JC.WHNUPLJC
509 Wheeled Number of Tires JC.WHNUTIJC
510 Wheeled Tire Load Rating JC.WHTLDILJC
511 Wheeled Tire Requirements JD.WHTRLOJD, JD.TREINCJD(A)
512 Wheeled Tire Size JC.WHTIFTJC
513 Wheeled Weight Ratings JC.WHWERAJC
514 Work Area Code CB.SUBWACCB
515 Work Package Reference UA.UTWPRFUA, UM.WKPKRFUM
516 Work Unit Code HG.WRKUCDHG
517 Wrapping Material HF.WRAPMTHF
518 Year EA. YRFLDGEA

MIL-STD-1388-2B
APPENDIX E
APPENDIX E - SECTION 2
LISTING OF DATA ELEMENT CODES
CODE DED DATA ELEMENT TITLE (ROLE NAMED)
-A-
AAEERHGD 026 ASVAB APTITUDE ELEMENT EXPECTED RANGE HIGH

AAEERLGD 026 ASVAB APTITUDE ELEMENT EXPECTED RANGE LOW
AAELPHGD 026 ASVAB APTITUDE ELEMENT LOWEST PERCENT HIGH
AAELPLGD 026 ASVAB APTITUDE ELEMENT LOWEST PERCENT LOW
AAEXRHGB 026 ASVAB AFQT EXPECTED RANGE HIGH
AAEXRLGB 026 ASVAB AFQT EXPECTED RANGE LOW
AALPRHGB 026 ASVAB AFQT LOWEST PERCENT HIGH
AALPRLGB 026 ASVAB AFQT LOWEST PERCENT LOW
AAPLCCHA 308 GOVERNMENT FURNISHED PROVISIONING LIST CATEGORY CODE
ABAFQTGB 026 ASVAB AFQT SCORE
ACHAVABD 001 ACHIEVED AVAILABILITY
ACQMETHA 003 ACQUISITION METHOD CODE
ACTNAMED 399 ACTIVITY NAME LOCATION
ACTNSNHA 253 NSN ACTIVITY CODE
ADCAGEHB 046 ARN CAGE CODE
ADDLTMXA 014 ADMINISTRATIVE LEAD TIME
ADDREFHB 006 ADDITIONAL REFERENCE NUMBER
ADPEQPHA 027 AUTOMATIC DATA PROCESSING EQUIPMENT CODE
ADQCOFEA 002 ACQUISITION DECISION OFFICE
ADRNCCHB 338 ARN REFERENCE NUMBER CATEGORY CODE
ADRNVCHB 339 ARN REFERENCE NUMBER VARIATION CODE
AIDCAGUI 046 ADAPTER INTERCONNECTOR DEVICE (AID) CAGE CODE
AIDCUTUI 048 COMMON UNIT UNDER TEST
AIDREFUI 337 AID REFERENCE NUMBER
AIDRQDEA 005 ADAPTER/INTERCONNECTION DEVICE REQUIRED
AIDSRDUI 416 AID SUPPORT EQUIPMENT RECOMMENDATION DATA NUMBER
AIDUCNUI 025 AID APPORTIONED UNIT COST RECURRING
AIDUCRUI 025 AID APPORTIONED UNIT COST NONRECURRING
ALCSEIHN 019 S/N PROVISIONING SYSTEM/EI ALC
ALCSEIHO 019 UOC PROVISIONING SYSTEM/EI ALC
ALCSEIXE 019 S/N SYSTEM/EI ALTERNATE LCN CODE
ALCSEIXF 019 UOC SYSTEM/EI ALC
ALDCNMEB 016 ALLOWANCE DOCUMENT NUMBER
ALDNDSEB 015 ALLOCATION DESIGN DESCRIPTION
ALDTXXBE 013 ADMINISTRATIVE AND LOGISTICS DELAY TIME
ALEXRNEB 015 ALLOCATION EXTENDED RANGE
ALIQTYHG 018 ALLOWANCE ITEM QUANTITY
ALLOWCHG 017 ALLOWANCE ITEM CODE
ALLVCDEB 015 ALLOCATION LAND OR VESSEL CODE
ALMLVLEB 015 ALLOCATION MAINTENANCE LEVEL FUNCTION
ALORG1EB 015 ALLOWABLE RANGE 1

MIL-STD-1388-2B
APPENDIX E

ALRG1OEB 015 ALLOWABLE RANGE 10
ALSTIDEB 015 ALLOCATION STATION IDENTIFICATION CODE
ALTFSCEH 253 ALTERNATE NATIONAL STOCK NUMBER (NSN) FEDERAL SUPPLY CLASSIFICATION
ALTLCNBH 019 FMT ALTERNATE LCN CODE
ALTLCNHN 019 S/N PROVISIONING ITEM ALTERNATE LCN CODE (ALC)
ALTLCNHO 019 UOC PROVISIONING ALTERNATE LCN CODE (ALC)
ALTLCNXB 019 ALTERNATE LCN CODE
ALTLCNXE 019 S/N ITEM ALTERNATE LCN CODE
ALTLCNXF 019 UOC ITEM ALC
ALTNIIEH 253 ALTERNATE NSN NATIONAL ITEM IDENTIFICATION NUMBER
AMSUFCHA 004 ACQUISITION METHOD SUFFIX CODE
ANNOMIAB 021 ANNUAL NUMBER OF MISSIONS
ANOPDAAB 022 ANNUAL OPERATING DAYS
ANOPREAG 023 ANNUAL OPERATING REQUIREMENTS
ANOPTIAB 024 ANNUAL OPERATING TIME
AORALCCA 019 AOR ALC
AORLCNCA 199 ANNUAL OPERATING REQUIREMENT (AOR) LCN
AORMSBCA 238 AOR MEASUREMENT BASE
AORTYPCA 203 AOR LCN TYPE
ARAPTDHG 313 AS REQUIRED LIST A (PTD)
ARBPTDHG 313 AS REQUIRED LIST B (PTD)
ASVAPEGD 026 ASVAB APTITUDE ELEMENT
ATECAGUK 046 ATE CAGE CODE
ATEGDSUK 149 ATE GOVERNMENT DESIGNATOR
ATEREFUK 337 AUTOMATIC TEST EQUIPMENT (ATE) REFERENCE NUMBER
AVAIMHAE 028 AVAILABLE MAN-HOUR
-B-
BBPLCCHA 308 INTERIM SUPPORT ITEMS PLCC

BDLPGABA 032 BUILT IN TEST DETECTABILITY LEVEL PERCENTAGE PER GROUP 1
BDLPGBBA 032 BUILT IN TEST DETECTABILITY LEVEL PERCENTAGE PER GROUP 2
BITNDPBA 031 BUILT IN TEST CANNOT DUPLICATE PERCENTAGE
BITROPBA 033 BUILT IN TEST RETEST OK PERCENT
BOICTRHM 030 BASIS OF ISSUE CONTROL
-C-
CACITYXH 047 CAGE CITY

CADMTDHG 214 CONDEMNED AT DEPOT MTD
CAGECDHB 046 ARN ITEM CAGE CODE
CAGECDHC 046 ITEM CAGE CODE
CAGECDHN 046 S/N PROVISIONING CAGE CODE
CAGECDHO 046 UOC PROVISIONING CAGE CODE
CAGECDXH 046 COMMERICAL AND GOVERNMENRT ENTITY (CAGE) CODE
CALINTEA 037 CALIBRATION INTERVAL
CALITMEA 038 CALIBRATION ITEM
CALPROEC 039 CALIBRATION PROCEDURE
CALRQDEA 040 CALIBRATION REQUIRED
CALSTDEA 041 CALIBRATION STANDARD
CALTIMEA 042 CALIBRATION TIME

MIL-STD-1388-2B
APPENDIX E
CANAMEXH 047 CAGE NAME
CANATNXH 047 CAGE NATION
CANUMBHP 043 CHANGE AUTHORITY NUMBER
CAPOZOXH 047 CAGE POSTAL ZONE
CASTATXH 047 CAGE STATE
CASTREXH 047 CAGE STREET
CBDMTDHG 214 CONDEMNED BELOW DEPOT MTD
CBLPTDHG 313 COMMON AND BULK ITEMS LIST (PTD)
CCPLCCHA 308 LONG LEAD ITEM PLCC
CDPROCHF 045 CLEANING AND DRYING PROCEDURES
CFEGFEEA 056 CONTRACTOR FURNISHED EQUIPMENT/GOVERNMENT FURNISHED EQUIPMENT
CMRSRCEA 035 CALIBRATION MEASUREMENT REQUIREMENT SUMMARY RECOMMENDED
CNTRECEJ 057 DDCC CONTRACTOR RECOMMENDED
CNTRNOEA 055 SUPPORT EQUIPMENT CONTRACT NUMBER
COGNSNHA 253 NSN COGNIZANCE CODE
CONLENJB 053 CONTAINER LENGTH
CONNSNHF 253 CONTAINER NATIONAL STOCK NUMBER
CONNUMJA 055 CONTRACT NUMBER
CONRCTHG 350 CONTRACTOR RCT
CONRECEL 057 IRCC CONTRACTOR RECOMMENDED
CONTNOXA 055 SYSTEM END ITEM CONTRACT NUMBER
CONTYPJB 054 CONTAINER TYPE
CONUOMFA 491 CONSTRUCTION UNIT OF MEASURE
CONVFABA 059 CONVERSION FACTOR
CREANGJC 063 CREST ANGLE
CREWSW 064 CREW SIZE
CRITCDHA 066 CRITICALITY CODE
CRITITHA 065 CRITICAL ITEM CODE
CSPRRQXA 062 COST PER REQUISITION
CSREORXA 061 COST PER REORDER
CTCAGEHC 046 CTIC CAGE CODE
CTDLTMXA 052 CONTRACT TEAM DELAY TIME
CTICODHA 058 CONTRACTOR TECHNICAL INFORMATION CODE
CURPRCHD 051 UI PRICE CONCURRENT PRODUCTION CODE
CURPRCHE 051 UM PRICE CONCURRENT PRODUCTION CODE
CUSHMAHF 067 CUSHIONING AND DUNNAGE MATERIAL
CUSTCDEA 069 CUSTODY CODE
CUSTHIHF 068 CUSHIONING THICKNESS
-D-
DATASCHG 070 DATA STATUS CODE
DATFADEA 071 DATE OF FIRST ARTICLE DELIVERY
DDCCSCEJ 365 DDCC SCOPE
DDPLCCHA 308 TOOLS AND TEST EQUIPMENT PLCC
DEGPROHF 074 DEGREE OF PROTECTION CODE
DELSCHJA 075 DELIVERY SCHEDULE
DEMILCXA 077 DEMILITARIZATION COST
DEMILIHA 076 DEMILITARIZATION CODE
DEPUPKHF 494 UNIT PACK DEPTH
DINMETAD 280 DAILY INSPECTION MEAN ELAPSED TIME
DINMMHAD 280 DAILY INSPECTION MEAN MAN-HOURS
DISCNTXA 083 DISCOUNT RATE

MIL-STD-1388-2B
APPENDIX E
DLSCRCHA 073 DEFENSE LOGISTICS SERVICES CENTER SCREENING REQUIREMENT CODE

DMTDDDHG 214 DEPOT/SHIPYARD MTD
DOCAVCHA 086 DOCUMENT AVAILABILITY CODE
DOCIDCHA 087 DOCUMENT IDENTIFIER CODE
DPRNRSGB 092 DUTY POSITION REQUIRING A NEW OR REVISED SKILL
DRCLASFA 088 FACILITY DRAWING CLASSIFICATION
DRCTDDHG 350 DEPOT/SHIPYARD RCT
DRPONEHG 081 DESIGNATED REWORK POINT ONE
DRPTWOHG 081 DESIGNATED REWORK POINT TWO
DRTDDDHG 355 DEPOT SHIPYARD RTD
DRWCLSEA 088 SUPPORT EQUIPMENT DRAWING CLASSIFICATION
DSNDATEJ 079 DESIGN DATA CATEGORY CODE
DSNPRCEA 080 DESIGN DATA PRICE
DTGVDSEF 071 SERD DATE OF GOVERNMENT DISPOSITION
DTRVSBEF 071 SERD DATE OF REVISION SUBMISSION
DUTIESCJ 090 DUTY
DUTYCDCJ 091 DUTY CODE
-E-
ECOANLEA 093 ECONOMIC ANALYSIS

EEPLCCHA 308 COMMON AND BULK ITEM PLCC
EFMMMBBF 238 ENGINEERING FAILURE MODE MEAN TIME BETWEEN FAILURE MEASUREMENT BASE
EFMTBFBF 097 ENGINEERING FAILURE MODE MEAN TIME BETWEEN FAILURE
EIACODXA 096 END ITEM ACRONYM CODE
ELEMNTCC 095 ELEMENT INDICATOR
ENDARTEA 179 END ARTICLE ITEM DESIGNATOR
ENHATCJA 098 ENVIRONMENTAL HANDLING AND TRANSPORTATION INDICATOR
EOILINJB 104 EXTERNAL OR INTERNAL LOAD INDICATOR
ESSALVXA 102 ESTIMATED SALVAGE VALUE
ESSCODHG 100 ESSENTIALITY CODE
ESTPRCEJ 101 DDCC ESTIMATED PRICE
ESTPRCEL 101 IRCC ESTIMATED PRICE
EXUNPREA 103 EXTENDED UNIT PRICE
-F-
FAAREAFA 026 FACILITY AREA

FAARUMFA 491 FACILITY AREA UNIT OF MEASURE
FABNARFC --- BASELINE FACILITY NARRATIVE
FACCCDFA 115 FACILITY CATEGORY CODE
FACCCDFC 115 BASELINE FACILITY CATEGORY CODE
FACCCDFD 115 NEW OR MODIFIED FACILITY CATEGORY CODE
FACCLAFA 116 FACILITY CLASS
FACNAMFA 118 FACILITY NAME
FACNAMFC 118 BASELINE FACILITY NAME
FACNAMFD 118 NEW OR MODIFIED FACILITY NAME
FACNARFB --- FACILITY NARRATIVE
FACTYPFA 483 FACILITY TYPE
FACTYPFC 483 BASELINE FACILITY TYPE
FACTYPFD 483 NEW OR MODIFIED FACILITY TYPE
FACRNUBI 133 FAILURE MODE CRITICALITY NUMBER
FADNUMFA 089 FACILITY DRAWING NUMBER
FADREVFA 360 FACILITY DRAWING REVISION

MIL-STD-1388-2B
APPENDIX E
FAILRTBD 140 FAILURE RATE
FALCNCXG 019 FUNCTIONAL EI ALC
FAMGRPEA 142 FAMILY GROUP
FAMOINBF 134 FAILURE MODE INDICATOR
FARAMBBD 238 FAILURE RATE MEASUREMENT BASE
FBNACDFC 113 BASELINE FACILITY NARRATIVE CODE
FEPROBBI 130 FAILURE EFFECT PROBABILITY
FFPLCCHA 308 REPAIRABLE ITEMS PLCC
FIAMBABA 143 FAULT ISOLATION AMBIGUITY GROUP 1
FIAMBBBA 143 FAULT ISOLATION AMBIGUITY GROUP 2
FIGNUMHK 144 FIGURE NUMBER
FIPFGABA 143 FAULT ISOLATION PERCENT FAILURE GROUP 1
FIPFGBBA 143 FAULT ISOLATION PERCENT FAILURE GROUP 2
FIQPQTJE 298 FIRST QUARTER PROCUREMENT QUANTITY
FISCYRHD 145 UI PRICE FISCAL YEAR
FISCYRHE 145 UM PRICE FISCAL YEAR
FLCNTYXG 203 FUNCTIONAL SYSTEM/EI LCN TYPE
FLITNMEA 412 SUPPORT EQUIPMENT FULL ITEM NAME
FLSACNXG 199 FUNCTIONAL SYSTEM/EI LCN
FMCLASBF 132 FAILURE MODE CLASSIFICATION
FMCNARBJ --- FAILURE MODE INDICATOR MISSION PHASE CHARACTERISTICS NARRATIVE
FMMPCNBJ 135 FAILURE MODE INDICATOR MISSION PHASE CHARACTERISTICS NARRATIVE CODE
FMNCNABG 131 FAILURE MODE AND RCM NARRATIVE CODE
FMNNARBG --- FAILURE MODE NARRATIVE
FMOPTIBI 269 OPERATING TIME
FMOTMBBI 238 OPERATING TIME MEASUREMENT BASE
FMIUiTOBF 136 FAILURE MODE RATIO
FMSHSCBI 362 SAFETY HAZARD SEVERITY CODE
FMSHSCBK 362 M SAFETY HAZARD SEVERITY CODE
FMSRNOHQ 374 SERIAL NUMBER EFFECTIVITY FROM
FMTDFFHG 214 INTERMEDIATE/DIRECT SUPPORT MTD
FNCODEFB 119 FACILITY NARRATIVE CODE
FPROBLBI 139 FAILURE PROBABILITY LEVEL
FQPQTYJE 298 FOURTH QUARTER PROCUREMENT QUANTITY
FRCLASJB 146 FREIGHT CLASSIFICATION
FRCTFFHG 350 INTERMEDIATE/DIRECT SUPPORT RCT
FRDATABA 141 FAILURE RATE DATA SOURCE
FRSNUMHN 373 S/N PROVISIONING SERIAL NUMBER FROM
FRSNUMXD 373 SERIAL NUMBER FROM
FRSNUMXE 373 S/N SERIAL NUMBER FROM
FRTDFFHG 355 INTERMEDIATE/DIRECT SUPPORT RTD
FSCNSNHA 253 NSN FEDERAL SUPPLY CLASSIFICATION
FTRNRQCA 358 FACILITY REQUIREMENT CODE
-G-
GENECDEA 148 GENERIC CODE
GFAEIDEM 179 SYSTEM EQUIPMENT ITEM DESIGNATOR
GGPLCCHA 308 INTERIM RELEASED ITEM PLCC
GOVDESEA 149 GOVERNMENT DESIGNATOR
GOVRQDEJ 150 DDCC GOVERNMENT REQUIRED
GOVRQDEL 150 IRCC GOVERNMENT REQUIRED

MIL-STD-1388-2B
APPENDIX E

-H-
HALTMLJB 250 HIGHWAY ALTERNATE MODEL LOAD

HALTMTJB 251 HIGHWAY ALTERNATE MODEL TYPE
HARDCIHG 151 HARDNESS CRITICAL ITEM
HAZCODHA 154 HAZARDOUS CODE
HAZMPCCA 155 HAZARDOUS MAINTENANCE PROCEDURES CODE
HDWRPREA 153 HARDWARE DEVELOPMENT PRICE
HHPLCCHA 308 INSTALLATION AND CHECKOUT ITEM PLCC
HICLNEJC 241 MILITARY LOAD CLASSIFICATION EMPTY
HICLNLJC 241 MILITARY LOAD CLASSIFICATION LOADED
HIPRMLJB 250 HIGHWAY PRIME MODEL LOAD
HIPRMTJB 251 HIGHWAY PRIME MODEL TYPE
HLCSPCXA 160 HOLDING COST PERCENTAGE
HMATLRJB 159 HELICOPTER MISSION ALTITUDE
HMDISRJB 159 HELICOPTER MISSION DISTANCE
HMPAYRJB 159 HELICOPTER MISSION PAYLOAD
HMSCOSHA 156 HAZARDOUS MATERIALS STORAGE COST
HMTDHHHG 214 INTERMEDIATE/GENERAL SUPPORT MTD
HMTIMRJB 159 HELICOPTER MISSION TIME
HMTMPRJB 159 HELICOPTER MISSION TEMPERATURE
HRCTHHHG 350 INTERMEDIATE/GENERAL SUPPORT RCT
HRDCPCCA 152 HARDNESS CRITICAL PROCEDURE CODE
HRLARTGA 161 HOUR LABOR RATE
HRTDHHHG 355 INTERMEDIATE/GENERAL SUPPORT RTD
HWDCOSHA 157 HAZARDOUS WASTE DISPOSAL COST
HWSCODHA 158 HAZARDOUS WASTE STORAGE COST
-I-
ICCODEEK 172 SUPERCEDURE INTERCHANGEABILITY CODE

ILSPRCEA 170 INTEGEUiTED LOGISTIC SUPPORT PRICE
IMTBMMBD 238 MEAN TIME BETWEEN MAINTENANCE INDUCED MEASUREMENT BASE
INAMECHA 183 ITEM NAME CODE
INCATCXA 167 INITIAL CATALOG COST
INCQTYHF 175 INTERMEDIATE CONTAINER QUANTITY
INDCODHG 162 INDENTURE CODE
INDMATHA 163 INDUSTRIAL MATERIALS ANALYSIS OF CAPACITY
INHAVAM 164 REQUIRED INHERENT AVAILABILITY
INHAVABD 164 INHERENT AVAILABILITY
INHMAFBD 165 INHERENT MAINTENANCE FACTOR
INHMTBBD 232 MEAN TIME BETWEEN MAINTENANCE INHERENT
INHMTMBD 238 MEAN TIME BETWEEN MAINTENANCE INHERENT MEASUREMENT BASE
INMTBMBD 231 MEAN TIME BETWEEN MAINTENANCE INDUCED
INTBINXA 166 INITIAL BIN COST
INTCHCHP 172 INTERCHANGEABILITY CODE
INTCONHF 174 INTERMEDIATE CONTAINER CODE
INTIUTXA 173 INTEREST RATE
INTSUBEF 071 SERD DATE OF INITIAL SUBMISSION
INVSTGXA 176 INVENTORY STORAGE SPACE
IOCAGEAH 046 INTEROPERABLE CAGE CODE
IOINTYAH 266 NUMBER TYPE
IOITNMAH 440 INTEROPERABLE ITEM TECHNICAL MANUAL NUMBER

MIL-STD-1388-2B
APPENDIX E
CODE DATA ELEMENT TITLE (ROLE NAMED)
IONANEAH 182 INTEROPERABLE ITEM NAME

IONFSCAH 253 INTEROPERABLE ITEM NSN FSC
IONIINAH 253 INTEROPERABLE ITEM IDENTIFICATION NUMBER
IOREFNAH 337 INTEROPERABLE REFERENCE NUMBER
IPACDCEI 168 INPUT POWER SOURCE ALTERNATING CURRENT DIRECT CURRENT
IPFRMXEI 168 INPUT POWER SOURCE FREQUENCY RANGE MAXIMUM
IPMXRPEI 168 INPUT POWER SOURCE PERCENT MAX RIP
IPOPRGEI 168 INPUT POWER SOURCE OPERATING RANGE MINIMUM
IPPHASEI 168 INPUT POWER SOURCE PHASE
IPPOWREI 168 INPUT POWER SOURCE WATTS
IPRGMXEI 168 INPUT POWER SOURCE FREQUENCY RANGE MINIMUM
IPSOPNEI 168 SOURCE OPTION NUMBER
IPSRGMEI 168 INPUT POWER SOURCE OPERATING RANGE MAXIMUM
IRCCODEL 171 INTERATED LOGISTIC SUPPORT REQUIREMENT CATEGORY CODE
IRCSCOEL 365 IRCC SCOPE
ISLPTDHG 313 INTERIM SUPPORT ITEMS LIST(PTD)
ITEMNOHK 184 ITEM NUMBER
ITMCATHG 177 ITEM CATEGORY CODE
ITMDESXC 179 SYSTEM/EI ITEM DESIGNATOR CODE
ITMMGCHA 181 ITEM MANAGEMENT CODE
ITNAMEHA 182 ITEM NAME
-J-
JJPLCCHA 308 AUTHORIZATION STOCK LIST ITEM PLCC

JOBCODCJ 186 JOB CODE
JOBDESCJ 185 JOB
-K-
KKPLCCHA 308 RECOMMENDED BUY LIST ITEM PLCC

-L-
LABRATAI 189 LABOR RATE

LCNAMEXB 201 LCN NOMENCLATURE
LCNINDXB 200 LCN INDENTURE
LCNSEIHN 199 S/N PROVISIONING SYSTEM/EI LCN
LCNSEIHO 199 UOC PROVISIONING SYSTEM/EI LCN
LCNSEIXE 199 S/N SYSTEM/EI LCN
LCNSEIXF 199 UOC SYSTEM/EI LCN
LCNSTRXA 202 LCN STRUCTURE
LCNTYPBH 203 FMT LCN TYPE
LCNTYPXB 203 LCN TYPE
LCNTYPXE 203 S/N ITEM LCN TYPE
LCNTYPXF 203 UOC ITEM LCN TYPE
LENUPKHF 494 UNIT PACK LENGTH
LGCTCDEA 197 LOGISTICS CONTROL CODE
LGDCOFEA 198 LOGISTICS DECISION OFFICE
LICYSTEA 190 LIFE CYCLE STATUS
LIFSPNEA 191 LIFE SPAN
LINNUMHA 193 LINE ITEM NUMBER
LLIPTDHG 313 LONG LEAD TIME ITEMS LIST PROVISIONING TECHNICAL DOCUMENTATION

MIL-STD-1388-2B
APPENDIX E
LLPLCCHA 308 PRESCRIBED LOAD LIST ITEM PLCC

LMTDLLHG 214 SPECIAL REPAIR ACTIVITY MTD
LOCOCOBC 425 LOGISTICS CONSIDERATION CODE
LODFACXA 195 LOADING FACTOR
LOGACCBA 196 LOGISTIC CONSIDERATIONS ACCESSIBILITY
LOGCONBA 196 LOGISTIC CONSIDERATIONS CONNECTORS
LOGCRCBA 196 LOGISTIC CONSIDERATIONS CORROSION/RUST CONTROL
LOGDSPBA 196 LOGISTIC CONSIDERATIONS DESIGN FOR SELF PROTECTION
LOGFLOBA 196 LOGISTIC CONSIDERATIONS FAULT LOCATION
LOGLABBA 196 LOGISTIC CONSIDERATIONS LABELING
LOGMAIBA 196 LOGISTIC CONSIDERATIONS MAINTENANCE BASE
LOGNARBC 426 RAM LOGISTIC CONSIDERATIONS
LOGPATBA 196 LOGISTIC CONSIDERATIONS PACKAGING AND TRANSPORTATION
LOGSAFBA 196 LOGISTIC CONSIDERATIONS SAFETY
LOGSKIBA 196 LOGISTIC CONSIDERAITIONS SKILLS
LOGSTABA 196 LOGISTIC CONSIDERATIONS STANDARDIZATION
LOGTEPBA 196 LOGISTIC CONSIDERATIONS TEST POINTS
LOGTMBA 196 LOGISTIC CONSIDERATIONS TWINING
LOTQFMHD 205 UI PRICE LOT QUANTITY FROM
LOTQFMHE 205 UM PRICE LOT QUANTITY FROM
LOTQTOHD 205 UI PRICE LOT QUANTITY TO
LOTQTOHE 205 UM PRICE LOT QUANTITY TO
LRCTLLHG 350 SPECIAL REPAIR ACTIVITY RCT
LRTDLLHG 355 SPECIAL REPAIR ACTIVITY RTD
LRUNITHG 194 LINE REPLACEABLE UNIT
LSACONHN 199 S/N PROVISIONING SYSTEM LSA CONTROL NUMBER (LCN)
LSACONHO 199 UOC PROVISIONING LSA CONTROL NUMBER (LCN)
LSACONXB 199 LSA CONTROL NUMBER (LCN)
LSACONXE 199 S/N ITEM LSA CONTROL NUMBER
LSACONXF 199 UOC ITEM LCN
LSARCDEA 204 LSA RECOMMENDATION CODE
LTYSEIXE 203 LCN S/N UOC SYSTEM/EI LCN TYPE
LTYSEIXF 203 UOC SYSTEM/EI LCN TYPE
LVLBOIHM 030 BASIS OF ISSUE LEVEL
LWHOUMEA 491 OPERATING DIMENSIONS UNIT OF MEASURE
LWHSUMEA 491 STORAGE DIMENSIONS UNIT OF MEASURE
-M-
MAIACTHG 206 MAINTENANCE ACTION CODE

MAININBH 208 MAINTENANCE INTERVAL
MAINMBBH 238 MAINTENANCE INTERVAL MEASUREMENT BASE
MAOTIMHG 221 MAXIMUM ALLOWABLE OPERATING TIME
MATERLHA 218 MATERIAL
MATNSNHA 253 NSN MATERIEL CONTROL CODE
MAXTTRAA 222 REQUIRED MAXIMUM TIME TO REPAIR
MAXTTRBD 222 MAXIMUM TIME TO REPAIR
MDCSSCGB 257 NEW OR MODIFIED SKILL SPECIALTY CODE
MDSCLCGB 386 NEW MODIFIED SKILL LEVEL CODE
MEASBSAG 238 ANNUAL OPERATING REQUIREMENT MEASUREMENT BASE
MEPRESHF 239 METHOD OF PRESERVATION CODE
MEQLINBA 243 MINIMUM EQUIPMENT LIST INDICATOR
MGCOATEA 217 MANAGING COMMAND/AGENCY

MIL-STD-1388-2B
APPENDIX E

MGTPLNEA 216 MANAGEMENT PLAN
MILUNTJA 242 MILITARY UNIT TYPE
MINREUHG 245 MINIMUM REPLACEMENT UNIT
MISSPCBL 246 MISSION PHASE CODE
MLMTTWC 222 MAINTENANCE LEVEL MAXIMUM TIME TO REPAIR
MLNSSUAC 265 NUMBER OF SYSTEMS SUPPORTED
MLSMHOAC 215 SCHEDULED MAN-HOUR PER OPERATING HOUR
MLUMHOAC 215 UNSCHEDULED MAN-HOUR PER OPERATING HOUR
MLPERCAC 286 MAINTENANCE LEVEL PERCENTILE
MLSAMHAC 020 MAINTENANCE LEVEL SCHEDULED ANNUAL MAN-HOURS
MLUAMHAC 020 MAINTENANCE LEVEL UNSCHEDULED ANNUAL MAN-HOURS
MLUMETAC 499 UNSCHEDULED MAINTENANCE MEAN ELAPSED TIME
MLUMMHAC 499 UNSCHEDULED MAINTENANCE MEAN MAN-HOURS
MMISDMAB 238 MEAN MISSION DURATION MEASUREMENT BASE
MMISDUAB 228 MEAN MISSION DURATION
MMPLCCHA 308 SYSTEM SUPPORT PACKAGE COMPONENT LIST PLCC
MNTPLNUM 209 SE UUT MAINTENANCE PLAN NUMBER
MOBTYPJC 249 MOBILITY TYPE
MODCHGEA 252 MODIFICATION OR CHANGE
MPCMETAD 280 MISSION PROFILE CHANGE MEAN ELAPSED TIME
MPCMMHAD 280 MISSION PROFILE CHANGE MEAN MAN-HOURS
MPOPLDBL 247 MISSION PHASE OPERATIONAL MODE
MRRMODHG 213 MAINTENANCE REPLACEMENT RATE MODIFIER
MRRONEHG 211 MAINTENANCE REPLACEMENT RATE I
MRRTWOHG 212 MAINTENANCE REPLACEMENT RATE II
MSDMETCA 224 MEASURED MEAN ELAPSE TIME
MSDMMHCA 225 MEASURED MEAN MAN-HOURS
MTBMPMBD 238 MEAN TIME BETWEEN PREVENTIVE MAINTENANCE MEASUREMENT BASE
MTBMPVBD 234 MEAN TIME BETWEEN PREVENTIVE MAINTENANCE
MTBRMBBD 238 MEAN TIME BETWEEN REMOVALS MEASUREMENT BASE
MTBRXXAG 235 REQUIRED MEAN TIME BETWEEN REMOVALS
MTBRXXBD 235 MEAN TIME BETWEEN REMOVALS
MTLEADHA 219 MATERIAL LEADTIME
MTLWGTHA 220 MATERIAL WEIGHT
MTTROPBD 236 MEAN TIME TO REPAIR OPERATIONAL
MTTRTHBD 236 MEAN TIME TO REPAIR TECHNICAL
-N-
NETEXWJA 254 NET EXPLOSIVE WEIGHT
NHAINDHH 259 NHA PLISN INDICATOR
NHAPLIHH 258 NEXT HIGHER ASSEMBLY NHA PROVISIONING LIST ITEM SEQUENCE NUMBER
NIINSNHA 253 NSN NATIONAL ITEM IDENTIFICATION NUMBER
NMFNARFD --- NEW OR MODIFIED FACILITY NARRATIVE
NMFNCDFD 255 NEW OR MODIFIED FACILITY NARRATIVE CODE
NMSNARGC --- NEW OR MODIFIED SKILL NARRATIVE
NMSNCDGC 256 NEW OR MODIFIED SKILL NARRATIVE CODE
NMTBMMBD 238 MEAN TIME BETWEEN MAINTENANCE NO DEFECT MEASUREMENT BASE
NOMTBMBD 233 MEAN TIME BETWEEN MAINTENANCE NO DEFECT
NOPRFFJA 260 NON-OPERABILITY FRAGILITY FACTOR
NORETSHG 261 NOT REPARABLE THIS STATION
NOSHPSAI 263 NUMBER OF SHOPS
NUMACTED 399 NUMBER OF ACTIVITIES

MIL-STD-1388-2B
APPENDIX E
NUOPLOAA 262 NUMBER OF OPERATING LOCATIONS
-O-
OMAMDTAA 223 OPERATIONAL MEAN ACTIVE MAINTENANCE DOWNTIME
OMLVLCAC 277 OPERATIONS AND MAINTENANCE LEVEL CODE
OMLVLCAI 277 MODELING OPERATIONS AND MAINTENANCE LEVEL CODE
OMLVLFAJ 277 OPERATIONS AND MAINTENANCE LEVEL FROM
OMLVLTAJ 277 OPERATIONS AND MAINTENANCE LEVEL TO
OMTBFMBD 238 MEAN TIME BETWEEN FAILURES OPERATIONAL MEASUREMENT BASE
OMTBMABD 230 MEAN TIME BETWEEN MAINTENANCE ACTIONS OPERATIONAL
OMTBMMBD 238 MEAN TIME BETWEEN MAINTENANCE ACTIONS OPERATIONAL MEASUREMENT BASE
OMTDOOHG 214 ORGANIZATIONAL MAINTENANCE TASK DISTRIBUTION (MTD)
OPAVAIAB 273 REQUIRED OPERATIONAL AVAILABILITY
OPAVAIBE 273 OPERATIONAL AVAILABILITY
OPLENGEA 268 OPERATING LENGTH
OPMTBFBD 229 MEAN TIME BETWEEN FAILURES OPERATIONAL
OPMRBMAG 230 REQUIRED OPEATIONAL MEAN TIME BETWEEN MAINTENANCE ACTIONS
OPMTBFAG 229 REQUIRED OPERATIONAL MEAN TIME BETWEEN FAILURES
OPMTTRAA 236 REQUIRED OPERATIONAL MEAN TIME TO REPAIR
OPRHGTEA 268 OPERATING HEIGHT
OPRLIFXA 272 OPERATION LIFE
OPRMANEA 278 OPERATOR’S MANUAL
OPRQINAB 275 OPERATIONAL REQUIREMENT INDICATOR
OPRQINBE 275 RAM OPERATIONAL REQUIREMENT INDICATOR
OPRWGTEA 270 OPERATING WEIGHT
OPTPRIHF 279 OPTIONAL PROCEDURES INDICATOR
OPWIDTEA 268 OPERATING WIDTH
ORCTOOHG 350 ORGANIZATIONAL REPAIR CYCLE TIME (RCT)
ORTDOOHG 355 ORGANIZATIONAL REPLACEMENT TASK DISTRIBUTION (RTD)
OSCOSTEA 267 OPERATING AND SUPPORT COST
OSTBTIAB 403 REQUIRED STANDBY TIME
OTPACNUC 025 OTP APPORTIONED UNIT COST NONRECURRING
OTPACRUC 025 OTP APPORTIONED UNIT COST RECURRING
OTPCAGUC 046 OPERATIONAL TEST PROGRAM (OTP) CAGE CODE
OTPCTPUC 060 OTP COORDINATED TEST PLAN
OTPREFUC 337 OPERATIONAL TEST PROGRAM (OTP) REFERENCE NUMBER
OTPSFCUC 402 OTP STANDARDS FOR COMPARISON
OTPSRDUC 416 OTP SUPPORT EQUIPMENT RECOMMENDATION DATA NUMBER
OPWEEMJC 276 OPERATIONAL WEIGHT EMPTY
OPWELOJC 276 OPERATIONAL WEIGHT LOADED
OVHREPHH 281 OVERHAUL REPLACEMENT RATE
-P-
PACCATHF 282 PACKAGING CATEGORY CODE
PALCNCXG 019 PHYSICAL ALC
PAMENRGE 290 PHYSICAL AND MENTAL REQUIREMENTS NARRATIVE
PARACCEC 284 SUPPORT EQUIPMENT PARAMETER ACCURACY
PARGPCEC 284 PARAMETER GROUP CODE
PARPAREC 284 SUPPORT EQUIPMENT PARAMETER
PARRVCEC 284 SUPPORT EQUIPMENT PARAMETER RANGE-VALUE CODE
PASTHREA 285 PASS THROUGH PRICE

MIL-STD-1388-2B
APPENDIX E
PCCNUMXC 307 SYSTEM/EI PROVISIONING CONTRACT CONTROL NUMBER

PCLPTDHG 313 POST CONFERENCE LIST (PTD)
PERCENAA 286 REQUIRED PERCENTILE
PERCENBD 286 PERCENTILE
PHYSECHA 291 PHYSICAL SECURITY/PILFERAGE CODE
PINMETAD 280 PERIODIC INSP MEAN ELAPSED TIME
PINMMHAD 280 PERIODIC INSP MEAN MAN-HOURS
PIPLISHG 297 PRIOR ITEM PLISN
PKCAGEHF 046 PACKAGING DATA PREPARER CAGE
PKGCODHF 283 PACKING CODE
PLCNTYXG 203 PHYSICAL LCN TYPE
PLISNOXC 309 SYSTEM/EI PROVISIONING LIST ITEM SEQUENCE NUMBER (PLISN)
PLISNOHG 309 PROVISIONING LIST ITEM SEQUENCE NUMBER (PLISN)
PLSACNXG 199 PHYSICAL LCN
PMCSIDCA 296 PREVENTIVE MAINTENANCE CHECKS AND SERVICES INDICATOR CODE
PMDTECCA 237 PRIMARY MEANS DETECTION
PMICODHA 293 PRECIOUS METAL INDICATOR CODE
POIMETAD 280 POSTOPERATIVE INSPECTION MEAN ELAPSED TIME
POIMMHAD 280 POSTOPERATIVE INSPECTION MEAN MAN-HOURS
PPLPTDHG 313 PROVISIONING PARTS LIST (PTD)
PPSLSTHA 302 PROGRAM PARTS SELECTION LIST
PQTKUMCI 491 PROVISION QUANTITY PER TASK UNIT OF MEASURE
PQTYTKCI 319 PROVISION QUANTITY PER TASK
PRDLDTHA 299 PRODUCTION LEADTIME
PRDMETCA 224 PREDICTED MEAN ELAPSE TIME
PRDMMHCA 225 PREDICTED MEAN MAN-HOURS
PREATYEA 294 PREPARING ACTIVITY
PREMETAD 280 PREOPERATIVE INSPECTION MEAN ELAPSED TIME
PREMMHAD 280 PREOPERATIVE INSPECTION MEAN MAN-HOURS
PREOVCBA 292 PILOT REWORK OVERHAUL CANDIDATE
PROALCCI 019 TASK PROVISION ALC
PROCAGCI 046 TASK PROVISION CAGE CODE
PROELEEA 301 PROGRAM ELEMENT
PROELIHP 305 PRORATED EXHIBIT LINE ITEM NUMBER (ELIN)
PROFACXA 300 PRODUCTIVITY FACTOR
PROLCNCI 199 TASK PROVISION LCN
PROLTYCI 203 TASK PROVISION LCN TYPE
PROPSNJA 304 PROPER SHIPPING NAME
PROQTYHP 306 PRORATED QUANTITY
PROREFCI 337 TASK PROVISION REFERENCE NUMBER
PROSICHG 312 PROVISIONING SYSTEM IDENTIFIER CODE
PROUIPHD 314 UI PRICE PROVISIONING
PROUMPHE 314 UM PRICE PROVISIONING
PROVNOHL 310 PROVISIONING NOMENCLATURE
PRSMATHF 295 PRESERVATION MATERIAL CODE
PRSTDACA 287 TASK PERFORMANCE STANDARD A
PRSTDBCA 287 TASK PERFORMANCE STANDARD B
PRSTDCCA 287 TASK PERFORMANCE STANDARD C
PRSTOMXA 289 PERSONNEL TURNOVER RATE/MILITARY
PRSTOVXA 289 PERSONNEL TURNOVER RATE/CIVILIAN
PSICPOEA 303 PROGRAM SUPPORT INVENTORY CONTROL POINT
PSYSIDHG 423 PROVISIONING SYSTEM/END ITEM IDENTIFIER

MIL-STD-1388-2B
APPENDIX E

-Q-
QTYASYXC 316 SYSTEM/EI QUANTITY PER ASSEMBLY

QTYASYHG 316 QUANTITY PER ASSEMBLY
QTYAVAAE 324 AVAILABLE QUANTITY
QTYBOIHM 030 BASIS OF ISSUE QUANTITY
QTYFIGHK 318 QUANTITY PER FIGURE
QTYPEIXC 317 SYSTEM/END ITEM QUANTITY PER END ITEM
QTYPEIHG 317 QUANTITY PER END ITEM
QTYPROHP 322 QUANTITY PROCURED
QTYSHPHP 323 QUANTITY SHIPPED
QTYTSTEM 320 SYSTEM EQUIPMENT QUANTITY PER TEST
QTYUPKHF 321 QUANTITY PER UNIT PACK
-R-
RAILTCJB 325 RAIL TRANSPORTATION COUNTRY

RAILUSJB 326 RAIL USE
RAMCNABB 341 RAM CHARACTERISTICS NARRATIVE CODE
RAMINDBD 347 RAM INDICATOR CODE
RAMINDXB 342 RAM INDICATOR
RAMNARBB --- RAM CHARACTERISTICS ‘NARRATIVE
RATIOBHM 030 BASIS OF ISSUE END ITEM
RCBINCXA 333 RECURRING BIN COST
RCCATCXA 334 RECURRING CATALOG COST
RCMDSABF 084 RCM DISPOSITION A
RCMDSBBF 084 RCM DISPOSITION B
RCMDSCBF 084 RCM DISPOSITION C
RCMDSDBF 084 RCM DISPOSITION D
RCMDSEBF 084 RCM DISPOSITION E
RCMDSFBF 084 RCM DISPOSITION F
RCMDSGBF 084 RCM DISPOSITION G
RCMDSHBF 084 RCM DISPOSITION H
RCMDSIBF 084 RCM DISPOSITION I
RCMDSJBF 084 RCM DISPOSITION J
RCMLOGAA 345 RELIABILITY CENTERED MAINTENANCE LOGIC UTILIZED
RCMRO1BF 344 RELIABILITY CENTERED MAINTENANCE (RCM) LOGIC RESULTS 01
RCMR02BF 344 RCM LOGIC RESULTS 02
RCM.R09BF 344 RCM LOGIC RESULTS 09
RCMR1lBF 341 RCM LOGIC RESULTS 11

MIL-STD-1388-2B
APPENDIX E
RcMR23BF 344 RCM LOGIC RESULTS 23
RCURCSEA 332 RECURRING
RDCODEHJ 336 REFERENCE DESIGNATION CODE
REASUPEK 327 REASON FOR SUPERSEDURE DELETION
REFALCCA 019 REFERENCED ALTERNATE LCN CODE
REFDESHJ 335 REFERENCE DESIGNATION
REFEIACA 096 REFERENCED END ITEM ACRONYM CODE
REFLCNCA 199 REFERENCED LCN
REFNCCHA 338 REFERENCE NUMBER CATEGORY CODE
REFNUMHA 337 REFERENCE NUMBER
REFNUMHB 337 ARN ITEM REFERENCE NUMBER
REFNUMHC 337 ITEM REFERENCE NUMBER
REFNUMHN 337 S/N PROVISIONING REFERENCE NUMBER
REFNUMHO 337 UOC PROVISIONING REFERENCE NUMBER
REFNVCHA 339 REFERENCE NUMBER VARIATION CODE
REFTSKCA 427 REFERENCED TASK CODE
REFTYPCA 203 REFERENCED LCN TYPE
REMARKHI 311 PROVISIONING REMARKS
REMIPIHG 348 REMAIN IN PLACE INDICATOR
REPSURHG 351 REPAIR SURVIVAL RATE
RESTCRXA 359 RETAIL STOCKAGE CRITERIA
REVASSEA 361 REVOLVING ASSETS
REVREMEG 417 SERD REVISION REMARKS
RFDALCCB 019 REFERENCED SUBTASK ALTERNATE LCN CODE
RFDEIACB 096 REFERENCED SUBTASK END ITEM ACRONYM CODE
RFDLCNCB 199 REFERENCED SUBTASK LCN
RFDSUBCB 407 REFERENCED SUBTASK NUMBER
RFDTCDCB 427 REFERENCED SUBTASK TASK CODE
RFDTYPCB 203 REFERENCED SUBTASK LCN TYPE
RICRITBK 178 CRITICALITY NUMBER
RILPTDHG 313 REPAIRABLE ITEMS LIST (PTD)
RISSBUHG 328 RECOMMENDED INITIAL SYSTEM STOCK BUY
RMSSLIHG 329 RECOMMENDED MINIMUM SYSTEM STOCK LEVEL
RNGFRMEC 284 SUPPORT EQUIPMENT PARAMETER RANGE FROM
RNGTOCEC 284 SUPPORT EQUIPMENT PARAMETER RANGE TO
RPPCIVGB 330 RECOMMENDED CIVILIAN GRADE
RPPMILGB 330 RECOMMENDED MILITARY RANK RATE
RPWSCSAI 352 REPAIR WORK SPACE COST
RQDSTKAI 357 REQUIRED DAYS OF STOCK
RSPLISHP 353 REPLACED OR SUPERSEDING (R/S) PLISN
RTLLQTHG 331 RECOMMENDED TENDER LOAD LIST QUANTITY
-S-
SAIPCDHA 391 SPARES ACQUISITION INTEGRATED WITH PRODUCTIONS
SAFLVLXA 363 SAFETY LEVEL

MIL-STD-1388-2B
APPENDIX E
SAPLISHG 364 SAME AS PLISN

SBMMETCB 227 SUBTASK MEAN MINUTE ELASPSE TIME
SCAGECEM 046 SYSTEM EQUIPMENT CAGE CODE
SCPPTDHG 313 SYSTEM CONFIGURATION PROVISIONING PARTS LIST (PTD)
SCRSSCGB 369 SECURITY CLEARANCE
SDECKSJB 072 SEA DECK STOWAGE
SDSICGJC 384 SKID AREA
SECAGEEA 046 SUPPORT EQUIPMENT (SE) CAGE CODE
SECCLEBA 369 SECURITY CLEARANCE
SECITMXB 367 SECTIONALIZED ITEM TRANSPORTATION INDICATOR
SECSFCXA 421 SUPPORT OF EQUIP COST FACTOR
SECTIDJA 366 SECTIONALIZED IDENTIFICATION
SEGRCDEA 413 SUPPORT EQUIPMENT GROUPING
SEICCDEA 177 SUPPORT EQUIPMENT ITEM CATEGORY CODE
SEINAMK --- SYSTEM/END ITEM NARRATIVE
SEINCDAK 424 SYSTEM/END ITEM NARRATIVE CODE
SEMTBFEA 229 SUPPORT EQUIPMENT MEAN TIME BETWEEN FAILURE
SEMTTREA 236 SUPPORT EQUIPMENT MEAN TIME TO REPAIR
SENARCEE 414 SUPPORT EQUIPMENT NARRATIVE CODE
SENTRAEA 371 SENSORS OR TRANSDUCERS
SEQNAREE --- SUPPORT EQUIPMENT NARRATIVE
SEQTYAED 399 SUPPORT EQUIPMENT QUANTITY PER ACTIVITY
SERDESAA 376 SERVICE DESIGNATOR CODE
SERDESAI 376 MODELING SERVICE DESIGNATOR CODE
SERDNOEF 416 SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD) NUMBER
SEREFNEA 337 SUPPORT EQUIPMENT REFERENCE NUMBER
SEREQDEA 418 SUPPORT EQUIPMENT REQUIRED
SERICCEA 356 REPORTABLE ITEM CONTROL CODE
SESHPHEA 419 SUPPORT EQUIPMENT SHIPPING HEIGHT
SESHPLEA 419 SUPPORT EQUIPMENT SHIPPING LENGTH
SESHPWEA 419 SUPPORT EQUIPMENT SHIPPING WIDTH
SESHWTEA 420 SUPPORT EQUIPMENT SHIPPING WEIGHT
SEUPGCUN 284 SUPPORT EQUIPMENT UNIT UNDER TEST PARAMETER GROUP CODE
SFPPTDHG 313 SHORT FORM PROVISIONING PARTS LIST (PTD)
SHLIFEHA 377 SHELF LIFE
SHPCONJB 380 SHIPPING CONFIGURATION
SHPDISAJ 085 SHIP DISTANCE
SHWEEMJC 381 SHIPPING WEIGHT EMPTY
SHWELDJC 381 SHIPPING WEIGHT LOADED
SIASCNEA 401 STANDARD INTERSERVICE AGENCY SERIAL CONTROL NUMBER
SKADUMJC 491 SKID AREA UNIT OF MEASURE
SKETCHEA 383 SKETCH
SKLVCDGA 386 SKILL LEVEL CODE
SKSPCDGA 387SKILL SPECIALTY CODE
SLACTNHA 378SHELF LIFE ACTION CODE
SLFTSTEA 370SELF TEST CODE
SMAINCHA 392SPECIAL MAINTENANCE ITEM CODE
SMDTECCA 237 SECONDARY MEANS DETECTION
SMMNSNHA 253 NSN SPECIAL MATERIAL IDENTIFICATION CODE/MATERIAL MANAGEMENT
AGGREGATION CODE
SMRCODHG 389 SOURCE, MAINTENANCE, AND RECOVERABILITY CODE
SMRCSEEA 389 SE SOURCE, MAINTENANCE, AND RECOVERABILITY CODE
SMTBMAEA 230 SUPPORT EQUIPMENT MEAN TIME BETWEEN MAINTENANCE ACTIONS

MIL-STD-1388-2B
APPENDIX E
SNUMSKJC 264 NUMBER OF SKIDS
SNUUOCXD 375 SERIAL NUMBER USABLE ON CODE
SPARIOEC 284 SUPPORT EQUIPMENT PARAMETER INPUT OUTPUT CODE
SPDATEHF 187 SPI NUMBER JULIAN DATE
SPEMRKHF 394 SPECIAL MARKING CODE
SPINUMHF 396 SPECIAL PACKAGING INSTRUCTION (SPI) NUMBER
SPIREVHF 397 SPI NUMBER REVISION
SPMACCHA 395 SPECIAL MATERIAL CONTENT CODE
SPMGNTEA 393 SPECIAL MANAGEMENT
SPRCAGEK 046 SUPERSEDURE CAGE CODE
SPRFACEA 390 SPARE FACTOR
SPRREFEK 337 SUPERSEDURE REFERENCE NUMBER
SPSPEDJA 400 SPEED
SQPQTYJE 298 SECOND QUARTER PROCUREMENT QUANTITY
SQTKUMCG 491 QUANTITY PER TASK UNIT OF MEASURE
SQTYTKCG 319 QUANTITY PER TASK
SRDREVEF 360 SERD REVISION
SREFNOEM 337 SYSTEM EQUIPMENT REFERENCE NUMBER
SSCOPREA 387 SKILL SPECIALTY CODE FOR SUPPORT EQUIPMENT OPERATOR
SSCTESGB 449 TEST SCORE
SSECDECD 388 SKILL SPECIALTY EVALUATION CODE
STABYTBE 403 STANDBY TIME
STATUSEF 404 SERD STATUS
STOHGTEA 405 STORAGE HEIGHT
STOLENEA 405 STORAGE LENGTH
STOWDTEA 405 STORAGE WIDTH
STOWGTEA 406 STORAGE WEIGHT
SUBMMMCD 226 SUBTASK MEAN MAN-MINUTES
SUBNARCC 372 SEQUENTIAL SUBTASK DESCRIPTION
SUBNUMCB 407 SUBTASK NUMBER
SUBPIDCD 288 SUBTASK PERSON IDENTIFIER
SUBTIDCB 431 SUBTASK IDENTIFICATION
SUBWACCB 514 SUBTASK WORK AREA CODE
SUPCONBA 410 SUPPORT CONCEPT
SUPINDHG 422 SUPPRESSION INDICATOR
SUPITNEK 182 SUPERSEDURE ITEM NAME
SUPPKDHF 409 SUPPLEMENTAL PACKAGING DATA
SUSRNOEK 416 SUPERSEDURE SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD) NUMBER
SUTALLUM 016 SE UUT ALLOWANCE
SUTCAGUM 046 SUPPORT EQUIPMENT UNIT UNDER TEST (SE UUT) CAGE CODE
SUTREFUM 337 SE UNIT UNDER TEST (UUT) REFERENCE NUMBER
SUTSTCUM 036 SE UUT CMRS STATUS
SUTYPEEK 408 SUPERSEDURE TYPE
SYSINDXB 423 SYSTEM/END ITEM IDENTIFIER
-T-
TALCNCBH 019 TASK REQUIREMENT ALTERNATE LCN CODE
TASKCDCA 427 TASK CODE
TASKIDCA 431 TASK IDENTIFICATION
TATYPEBH 433 TASK TYPE
TCONDACA 428 TASK CONDITION A
TCONDBCA 428 TASK CONDITION B
NEW PAGE - 401a -

MIL-STD-1388-2B
APPENDIX E
TCONDCCA 428 TASK CONDITION C

TECEVLEA 435 TECHNICAL EVALUATION PRIORITY CODE
TEMTBFAG 229 REQUIRED TECHNICAL MEAN TIME BETWEEN FAILURE
TEMTBFBD 229 MEAN TIME BETWEEN FAILURES TECHNICAL
TEMTTRAA 236 REQUIRED TECHNICAL MEAN TIME TO REPAIR
TEXSEQAF 450 ADDITIONAL REQUIREMENTS TEXT SEQUENCING CODE
TEXSEQAK 450 SYSTEM END ITEM NARRATIVE TEXT SEQUENCING CODE
TEXSEQBB 450 RAM CHARACTERISTICS NARMTIVE TEXT SEQUENCING CODE
TEXSEQBC 450 RAM LOGISTICS CONSIDERATIONS TEXT SEQUENCING CODE
TEXSEQBG 450 FAILURE MODE NARRATIVE TEXT SEQUENCING CODE
TEXSEQBJ 450 FAILURE MODE INDICATOR MISSION PHASE CHARACTERISTICS NARRATIVE
TEXT SEQUENCING CODE
TEXSEQCC 450 SEQUENTIAL SUBTASK DESCRIPTION TEXT SEQUENCING CODE
TEXSEQEE 450 SUPPORT EQUIPMENT NARRATIVE TEXT SEQUENCING CODE
TEXSEQEG 450 SERD REVISION TEXT SEQUENCING CODE
TEXSEQFB 450 FACILITY NARRATIVE TEXT SEQUENCING CODE
TEXSEQFC 450 BASELINE FACILITY NARRATIVE TEXT SEQUENCING CODE
TEXSEQFD 450 NEW OR MODIFIED FACILITY NARRATIVE TEXT SEQUENCING CODE
TEXSEQGC 450” NEW OR MODIFIED SKILL NARRATIVE TEXT SEQUENCING CODE
TEXSEQGE 450 PHYSICAL AND MENTAL REQUIREMENTS TEXT SEQUENCING CODE
TEXSEQHI 450 PROVISIONING TEXT SEQUENCING CODE
TEXSEQHL 450 PARTS MANUAL TEXT SEQUENCING CODE
TEXSEQJD 450 TRANSPORTED END ITEM NARRATIVE TEXT SEQUENCING CODE
TEXSEQJF 450 TRANSPORTATION NARRATIVE TEXT SEQUENCING CODE
TEXSEQUF 450 UUT EXPLANATION TEXT SEQUENCING CODE
TEXTTOCK 450 SEQUENTIAL SUBTASK DESCRIPTION TEXT SEQUENCING CODE TO
TGSCAGUN 046 TESTING SUPPORT EQUIPMENT (SE) CAGE CODE
TGSREFUN 337 TESTING SE REFERENCE NUMBER
TIMESHAJ 379 SHIP TIME
TINMETAD 280 TURNAROUND INSPECTION MEAN ELAPSED TIME
TINMMHAD 280 TURNAROUND INSPECTION MEAN MAN-HOURS
TLCNTYBH 203 TASK REQUIREMENT LCN TYPE
TLSACNBH 199 TASK REQUIREMENT LCN
TMAMDTAA 223 TECHNICAL MEAN ACTIVE MAINTENANCE DOWNTIME
TMCHGNHK 436 TM CHANGE NUMBER
TMCODEXI 437 TECHNICAL MANUAL (TM) CODE
TMDERCEA 444 TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT REGISTER CODE
TMDERIEA 445 TEST MEASUREMENT AND DIAGNOSTIC EQUIPMENT REGISTER INDEX NUMBER
TMFGCDHK 438 TM FUNCTIONAL GROUP CODE
TMFGCDXB 438 TECHNICAL MANUAL FUNCTIONAL GROUP CODE
TMINDCHK 439 TM INDENTURE CODE
TMNUMBXI 440 TECHNICAL MANUAL NUMBER
TMRQCDEA 441 TECHNICAL MANUAL REQUIRED CODE(S)
TMTBFMBD 238 MEAN TIME BETWEEN FAILURES TECHNICAL MEASUREMENT BASE
TMTBMAAG 230 REQUIRED TECHNICAL MEAN TIME BETWEEN MAINTENANCE ACTIONS
TMTBMABD 230 MEAN TIME BETWEEN MAINTENANCE ACTIONS TECHNICAL
TMTBMMBD 238 MEAN TIME BETWEEN MAINTENANCE ACTIONS TECHNICAL MEASUREMENT BASE
TOCCODXC 481 SYSTEM/EI TYPE OF CHANGE CODE
TOCCODHG 481 TYPE OF CHANGE CODE
TOSNUMHN 373 S/N PROVISIONING SERIAL NUMBER TO
TOSNUMXD 373 SERIAL NUMBER TO
TOSNUMXE 373 S/N SERIAL NUMBER TO
TOSRNOHQ 374 SERIAL NUMBER EFFECTIVITY TO
- 401b - NEW PAGE

MIL-STD-1388-2B
APPENDIX E
CODE pEQ DATA ELEMENT TITLE (ROLE NAMED)
TOSYSUAA 454 TOTAL SYSTEMS SUPPORTED

TOTICHHP 452 TOTAL ITEM CHANGES
TOTQTYHG 453 TOTAL QUANTITY RECOMMENDED
TPAUCNUE 025 TPI APPORTIONED UNIT COST NONRECURRING
TPAUCRUE 025 TPI APPORTIONED UNIT COST RECURRING
TPICAGUE 046 TEST PROGRAM INSTRUCTION (TPI) CAGE CODE
TPIREFUE 337 TPI REFERENCE NUMBER
TPISRDUE 416 TPI SUPPORT EQUIPMENT RECOMMENDATION DATA NUMBER
TPISTSUE 370 TPI SELF TEST
TPITDPUE 434 TPI TECHNICAL DATA PACKAGE
TPSAUMJC 491 TRACKED PAD SHOE AREA UNIT OF MEASURE
TQPQTYJE 298 THIRD QUARTER PROCUREMENT QUANTITY
TRAFYRJE 145 TRANSPORT FISCAL YEAR
TRANARJF --- TRANSPORTATION NARRATIVE
TRANCDJF 470 TRANSPORTATION NARRATIVE CODE
TRANCNJB 465 TRANSPORTATION CHARACTERISTIC NUMBER
TRASEIXC 467 TRANSPORTATION END ITEM INDICATOR
TRCHMTJB 464 TRANSPORTATION CHARACTERISTIC MODE TYPE
TRCHRDJA 071 REVISION DATE
TRCHTHJA 451 THEATER OF OPERATION
TRCONMJC 473 TRANSPORTED CONFIGURATION NUMBER
TRDNUMUM 448 SE UUT TEST REQUIREMENTS DOCUMENT NUMBER
TREINCJD 474 TRANSPORTED END ITEM NARRATIVE CODE
TRGRPRJC 456 TRACKED GROUND CONTACT PRESSURE
TRITDRJB 469 TRANSPORTATION ITEM DESIGNATOR
TRNCOSGA 460 TRAINING COST
TRNCSTXA 466 TRANSPORTATION COST
TRNINDJA 468 TRANSPORTATION INDICATOR
TRNLOCCA 461 TRAINING LOCATION RATIONALE CODE
TRNRATCA 462 TRAINING RATIONALE
TRNRECCA 463 TRAINING RECOMMENDATION TYPE
TRNRQCCA 358 TRAINING EQUIPMENT REQUIREMENT CODE
TRNUPTJC 458 TRACKED PADS TOUCHING
TRPSARJC 457 TRACKED PAD SHOE AREA
TRRWWTJC 459 TRACKED ROAD WHEEL WEIGHT
TSCAGECG 046 TASK SUPPORT CAGE CODE
TSEREQCA 358 TOOL/SUPPORT EQUIPMENT REQUIREMENT CODE
TSFROMCK 450 SEQUENTIAL SUBTASK DESCRIPTION TEXT SEQUENCING CODE FROM
TSKALCCI 019 TASK ALTERNATE LCN CODE (ALC)
TSKCRCCA 429 TASK CRITICALITY CODE
TSKFRQCA 430 TASK FREQUENCY
TSKLCNCI 199 TASK LSA CONTROL NUMBER (LCN)
TSKLTYCI 203 TASK LCN TYPE
TSKREMCE 432 TASK REMARK
TSKRRCCE 349 TASK REMARK REFERENCE CODE
TSKTCDCI 427 TASK PROVISION TASK CODE
TSREFNCG 337 TASK SUPPORT REFERENCE NUMBER
TSSCODXA 484 TYPE OF SUPPLY SYSTEM CODE
TSTPTSEA 446 TEST POINTS
TSTLNGEA 443 TEST LANGUAGE
TTASKCBH 427 TASK CODE
TTLPTDHG 313 TOOL AND TEST EQUIPMENT LIST (PTD)
TUIPRCHD 485 UI PRICE TYPE OF PRICE CODE
NEW PAGE - 401c -

MIL-STD-1388-2B
APPENDIX E
TUMPRCHE 485 UM PRICE TYPE OF PRICE CODE

TWALFIJC 029 FRONT INSIDE AXLE LENGTH
TWALFOJC 029 FRONT OUTSIDE AXLE LENGTH
TWALRIJC 029 REAR INSIDE AXLE LENGTH
TWALROJC 029 REAR OUTSIDE AXLE LENGTH
TWSPEDJA 455 TOWING SPEED
TYPACTED 399 TYPE OF ACTIVITY
TYPCLSEA 479 TYPE CLASSIFICATION
TYPEEQEA 480 TYPE EQUIPMENT CODE
-U-
UCLEVLHF 487 UNIT CONTAINER LEVEL

UHEIGHHA 496 UNIT SIZE HEIGHT
UICONVHA 489 UNIT OF ISSUE CONVERSION FACTOR
UIPRICHD 490 UNIT OF ISSUE (UI) PRICE
ULENGTHA 496 UNIT SIZE LENGTH
UMNTPLUA 209 UUT MAINTENANCE PLAN NUMBER
UMPRICHE 492 UNIT OF MEASURE (UM) PRICE
UMSEWTEA 491 SE SHIPPING WEIGHT UNIT OF MEASURE
UMSHIPEA 491 SE SHIPPING DIMENSIONS UNIT OF MEASURE
UNICONHF 486 UNIT CONTAINER CODE
UNITISHA 488 UNIT OF ISSUE
UNITMSHA 491 UNIT OF MEASURE
UNPKCUHF 493 UNIT PACK CUBE
UNPKWTHF 495 UNIT PACK WEIGHT
UOCSEIXC 501 USABLE ON CODE
USESEREA 376 USING SERVICE DESIGNATOR CODE
UTALLOUA 016 UUT ALLOWANCE
UTCMRSUB 035 UUT CALIBRATION MEASUREMENT REQUIREMENTS SUMMARY RECOMMENDED CODE
UTEXPLUF 498 UUT EXPLANATION
UTLCNTUA 203 UUT LCN TYPE
UTPWCUN 284 SE UUT PARAMETER ACCURACY
UTPACMUN 034 SE UUT CALIBRATION MEASUREMENT REQUIREMENTS SUMMARY PARAMETER CODE
UTPAIOUN 284 SE UUT PARAMETER INPUT/OUTPUT CODE
UTPAPAUN 284 SE UUT PARAMETER
UTPARVUN 284 SE UUT PARAMETER RANGE/VALUE CODE
UTPATAUN 442 SE UUT PARAMETER TEST ACCURACY RATIO (TAR) ACTUAL
UTPATDUN 442 SE UUT PARAMETER TAR DESIRED
UTPRRTUN 284 SE UUT PARAMETER RANGE TO
UTRATIAE 503 UTILIZATION RATIO
UTRGFRUN 284 UUT PARAMETER RANGE FROM
UTSTCDUB 036 UUT CALIBRATION MEASUREMENT REQUIREMENT SUMMARY STATUS
UTTRDNUA 448 UUT TEST REQUIREMENTS DOCUMENT NUMBER
UTWPRFUA 515 UUT WORK PACKAGE REFERENCE
UUTALCUA 019 UUT ALTERNATE LCN CODE
UUTFA1UH 143 UUT FIRU AMBIGUITY GROUP 1
UUTFA2UH 143 UUT FIRU AMBIGUITY GROUP 2
UUTFP1UH 143 UUT FIRU PERCENT FAILURE 1
UUTFP2UH 143 UUT FIRU PERCENT FAILURE 2
UUTFTDUH 447 UUT FIRU TEST REQUIREMENTS DOCUMENT INDICATOR
UUTLCNUA 199 UUT LSA CONTROL NUMBER (LCN)
UUTPACUG 284 UUT PARAMETER ACCURACY
- 401d - NEW PAGE

MIL-STD-1358-2B
APPENDIX E
UUTPARUG 284 UUT PARAMETER
UUTPGCUG 284 UUT PARMMETER GROUP CODE
UUTPIOUG 284 UUT PARAMETER INPUT/OUTPUT CODE
UUTPPCUG 034 UUT CALIBRATION MEASUREMENT REQUIREMENT SUMMARY PARAMETER CODE
UUTPRFUG 284 UUT PARAMETER RANGE FROM
UUTPRTUG 284 UUT PARAMETER RANGE TO
UUTPRVUG 284 UUT PARAMETER RANGE/VALUE CODE
UUTPSOUG 284 UUT PARAMETER OPERATIONAL SPECIFICATION CODE
UUTPTAUG 442 UUT PARAMETER TEST ACCURACY RATIO (TAR) ACTUAL
UUTPTDUG 442 UUT PARAMETER TAR DESIRED
UWEIGHHA 497 UNIT WEIGHT
UWIDTHHA 496 UNIT SIZE WIDTH
-W-
WEOULIBA 505 WEAROUT LIFE
WGTOUMEA 491 OPERATING WEIGHT UNIT OF MEASURE
WGTSUMEA 491 STORAGE WEIGHT UNIT OF MEASURE
WHINPRJC 507 WHEELED INFLATION PRESSURE
WHNUPLJC 508 WHEELED NUMBER OF PLIES
WHNUTIJC 509 WHEELED NUMBER OF TIRES
WHTIFTJC 512 WHEELED TIRE SIZE
WHTLDRJC 510 WHEELED TIRE LOAD RATING
WHTRLOJD --- TRANSPORTED END ITEM NARRATIVE
WHWEMJC 513 WHEELED WEIGHT RATINGS
WIDUPKHF 494 UNIT PACK WIDTH
WKPKRFUM 515 SE UUT WORK PACKAGE REFERENCE
WOLIMBBA 238 WEAROUT LIFE MEASUREMENT BASE
WPADDRAF 009 ADDITIONAL REQUIREMENTS
WRAPMTHF 517 WRAPPING MATERIAL
WRKUCDHG 516 WORK UNIT CODE
WSOPLVXA 271 OPERATION LEVEL
WSTYAQXA 478 TYPE ACQUISITION
-Y-
YRFLDGEA 518 YEAR OF FIELDING
NEW PAGE - 401e -


MIL-STD-1388-2B
APPENDIX E
APPENDIX E - SECTION 3
DATA ELEMENT DEFINITIONS
001 ACHIEVED AVAILABILITY (Aa) 8NR6
The probability that, when used under stated conditions in an ideal sup-
port environment, a system will operate satisfactorily at any time. This
differs from Inherent Availability only in its inclusion of consideration
for preventive action. Aa excludes supply downtime and administrative
downtime. The measurement bases for MTBM and M must be consistent when
calculating Aa.
Aa may be expressed by the following formula:
MTBM
Aa = MTBM + M
(1 1 1)-1
MTBF + MTBM-ND + MTBPM
N
E (ETi) (TFi)
i-l
M - N
E TFi
i-1
M = Mean active maintenance downtime (where corrective and preventive

actions are considered)
ETi = Elapsed time for task i
TFi = Task frequency for task i
N - Total number of tasks performed
Note: The measurement bases for MTBF, MTBM-ND, and MTBPM must be
consistent when calculating the MTBM parameter.
REQUIRED ACHIEVED AVAILABILITY. An Aa representing the requirement/
specification Aa.
002 ACQUISITION DECISION OFFICE 15XL-
Identifies the activity name and code or office symbol responsible for
technical and acquisition management decisions.
003 ACQUISITION METHOD CODE (AMC) 1NF-
A code assigned by Department of Defense (DOD) activities to describe the

results of screening reviews of parts, defining either a single souzce or

MIL-STD-1388-2B
APPENDIX E
d. CAGE state 2AF-

e. CAGE nation 20 X L-
f. CAGE postal zone 10 X L-
048 COMMON UNIT UNDER TEST 2NR-

The number of UUTs with which the adapter, interconnection device or
signal conditioning circuitry can be used.
049 COMPENSATING DESIGN PROVISIONS 65X--
A narrative description identifying design provisions which circumvent or
mitigate the effects of the failure. A record of the true behavior of
the item in the presence of an internal malfunction or failure. Features
of the design at any indenture level that will nullify the effects of a
malfunction or failure, control or deactivation system items to halt
generation or propagation of failure effects, or activate backup or
standby items or systems. Redesign compensating provisions include:
a. Redundant items that allow continued and safe operation.
b, Safety or relief devices such as monitoring or alarm provisions
which permit effective operation or limit damage.
c. Alternate models of operation such as backup or standby items or
systems.
050 COMPENSATING OPERATOR ACTION PROVISIONS 65XL-
A narrative description describing operator actions to circumvent or
mitigate the effect of the postulated failure. Describes the
compensating provision that best satisfies the indication(s) observed by
an operator when the failure occurs, and the consequences of any
probable incorrect action(s) by the operator in response to an abnormal
indication,
051 CONCURRENT PRODUCTION CODE (CPC) 1AF-
A code to indicate if the unit of measure or issue price and lot quantity
are based on concurrent production of the spare item with the weapon
system/end item production.
Based on concurrent production Y
Not based on concurrent production N
UI PRICE CONCURRENT PRODUCTION CODE. The CPC associated with the UI
price.
UM PRICE CONCURRENT PRODUCTION CODE. The CPC associated with the UM
price.
052 CONTACT TEAM DELAY TIME 3NR-

MIL-STD-1388-2B
APPENDIX E
The time (in hours) required for a contact team to travel from the
intermediate maintenance location to the organizational location.
053 CONTAINER LENGTH 2NR-
The smallest standard container, in feet, that can be used to transport

the system/equipment.
054 CONTAINER TYPE 36XL-
The designation
— of the standard container used to transport the system/
equipment, e.g., ANSI/ISO, European.
055 CONTRACT NUMBER 19XL-
The unique number assigned to the contract in question, by which it can

be specifically identified.
SUPPORT EQUIPMENT CONTRACT NUMBER. The contract number of the SE
development/procurement.
TRANSPORTATION CONTACT NUMBER. The contract number for shipping.
056 CONTRACTOR FURNISHED EQUIPMENT/ 1AF-

GOVERNMENT FURNISHED EQUIPMENT (CFE/GFE)
A single-position code indicating the contractor’s recommendation for
supply action.
Contractor Furnished C
Government Furnished G
057 CONTRACTOR RECOMMENDED 1AF-
A code to signify whether or not the corresponding requirements are

contractor recommended. Codes are as follows:
“Y”
YES “N”
NO
058 CONTRACTOR TECHNICAL INFORMATION CODE 2A--

(CTIC)
A code which indicates specific information regarding the technical
process/data required to procure or produce the support item.
a. The first position of the CTIC contains a Breakout Recommenda-
tion Code. For a Navy acquisition program the only applicable code is
“C”, which does not relate to first position code “C” of this DED.
Recommended for Breakout A

Not Recommended for Breakout - Safety B
Not Recommended for Breakout - Warranty C
Not Recommended for Breakout - Unstable Design D
- 420 -
MIL-STD-1388-2B
APPENDIX E
Technical
Operational
133 FAILURE MODE CRITICALITY NUMBER 10 D --
(Cm)
Cm is that portion of the criticality number for an item, which ac-
counts for a specific one of its failure modes under a particular
severity classification. For a particular severity classification
and operational phase, the Cm for a failure mode may be calculated
with the following formula:
Cm = (B a F t) (1,000,000)
Where:
C m = Criticality Number for Failure Mode
B = Failure Effect Probability, DED 130
a = Failure Mode Ratio, DED 136
F = Part Failure Rate, DED 140
t = Operating Time, DED 269
134 FAILURE MODE INDICATOR 4XF-
The first position of the code describes whether the indicator is a

failure mode (F) or damage mode (D). The next three positions of the
code are alphanumeric, but not special characters. This four-position
code links information on a table to a particular failure or damage mode.
FMT FAILURE MODE INDICATOR. A failure mode indicator against which

either a corrective or preventive task is documented.
135 FAILURE MODE INDICATOR MISSION PHASE 1AF-
CHARACTERISTICS NARRATIVE CODE
A code that indicates the failure mode indicator mission phase
characteristics narrative.
Compensating design provisions, DED 049 A
Compensating operator actions provisions, DED 050 B
136 FAILURE MODE RATIO (a) 4NR3

The fraction of the failure rate of the part, related to the particular
failure mode under consideration. The failure mode ratio is the
probability expressed as a decimal fraction that the part or item will
fail in the identified mode. If all potential failure modes of a
particular part or item are listed, the sum of the “a” values for the
part or item will equal one. Individual failure mode multipliers may
be derived from failure rate source data or from test and operational
data. If failure mode data are not available, the “a” values represent
the analyst’s judgment based upon an analysis of the item’s functions.
137 FAILURE MODE REMARKS 65X--
MIL-STD-1388-2B
APPENDIX E
Narrative clarification of data pertaining to failure modes.

138 FAILURE PREDICTABILITY 65X--
Information on known incipient failure indicators (e.g. , operational per-

formance variations), which are peculiar to the item failure trends and
permit predicting failures in advance.
139 FAILURE PROBABILITY LEVEL 1AF-
A single-position code identifying the qualitative level assigned to the

failure probability of occurrence. The levels are as follows:
Level A - Frequent. A high probability of occurrences A
during the item operating time interval. High
probability may be defined as a single failure mode
probability of occurrence equal to or greater than
0.20 of the overall probability of failure during the
item operating time interval.
Level B - Reasonably Probable. A moderate B
probability of occurrence during the item
operating time interval. Reasonably probable
may be defined as a single failure mode
probability of occurrence which is 0.10 or more,
but less than 0.20 of the overall probability
of failure during the item operating time interval.
Level C - Occasional. An occasional probability c
of occurrence during item operating time interval.
Occasional probability may be defined as a single
failure mode probability of occurrence which is
0.01 or more, but less than 0.10 of the overall
probability of failure during the item operating time.
Level D - Remote. An unlikely probability of D
occurrence during item operating time interval.
Remote probability may be defined as a single failure
mode probability of occurrence which is 0.001 or more,
but less than 0.01 of the overall probability
of failure during the item operating time.
Level E - Extremely Unlikely. A failure whose E
probability of occurrence is essentially zero during
item operating time interval. Extremely unlikely
may be defined as a single failure mode probability
of occurrence, which is less than 0.001 of the overall
probability of failure during the item
operating time.
140 FAILURE RATE 10D--

MIL-STD-1388-2B
APPENDIX E
Option 3. Indentured with a “Z” and listed as a bulk item at the end of
the provisioning list.
Option 4. All parts indicated on drawing will be listed in the breakdown
in proper indenture without specific identification that the parts are
utilized as “attaching parts”.
Option 5. Attaching hardware need not be listed.
b. Indenture for kits. Whether or not kits will be included in the
provisioning parts list (PPL) will be indicated on the LSAR Data
Requirements Form (DD Form 1949-3). When maintenance plans/
practices require that a group of parts be replaced in one maintenance
or overhaul operation, these items shall be listed as a kit IAW with one
of the following options:
Option 1. Kits shall be assigned an indenture lower than the
subassembly/assembly/component/end item for which it is used and parts
of the kit shall be identified by entering an asterisk.
Option 2. The kit reference number shall be listed at the end of the
subassembly/assembly/component/end item breakdown.
Option 3. All kit parts shall be listed in the PPL in proper indenture
without specific identification that the parts are kit components. The
kit part number is to be listed as the last item of the applicable next
higher assembly, end item/assembly/subassembly breakdown.
163 INDUSTRIAL MATERIALS ANALYSIS OF CAPACITY 19 X L-
(IMAC)
A series of codes, per MIL-STD-295, applied to identify and track se-
lected forms and parts which are critical due to material content or
other industrial planning impacts. The IMAC Code contains three sub-
fields, i.e., item category (form, mechanical part, electrical part,
etc.), item characteristics, and the strategic/critical materials con-
tained in the item.
a. IMAC Category 1AF-
b. IMAC Characteristics 12XL-
C. IMAC Materials 6XL-
164 INHERENT AVAILABILITY (Ai) 8NR6
The probability that, when used under stated conditions in an ideal
support environment without consideration for preventive action, a system
will operate satisfactorily at any time. The “ideal support environment”
referred to, exists when the stipulated tools, parts, skilled manpower,
manuals, SE and other support items required are available. Ai excludes
whatever ready time, preventive maintenance downtime, supply downtime,
and administrative downtime may require. Ai may be expressed by the fol-
lowing formula:
- 445 - Supersedes page 445 of 28 March
MIL-STD-1388-2B
APPENDIX E
Ai = MTBF
MTBF+MTTR
where MTBF - Mean Time Between Failures, DED 229
MTTR - Mean Time To Repair, DED 236
NOTE: The measurement bases for MTBF and MTTR must be consistent when
calculating Ai.
REQUIRED INHERENT AVAILABILITY. An Ai representing the requirement/
specification Ai.
165 INHERENT MAINTENANCE FACTOR 2NR1
A factor derived from historical information, that identifies the percent

of No Defect maintenance actions that have been included in the MTBM
Inherent parameter. This factor is used to relate the MTBM Inherent
parameter to the MTBF parameter. The IMF may be calculated using the
following formula:
IMF = ((MTBF-MTBM INHERENT)/MTBF)100
where:
MTBF = Mean Time Between Failures, DED 229
MTBM Inherent - Mean Time Between Maintenance Inherent, DED 232
66 INITIAL BIN COST 4NR-
The initial cost in, whole dollars, of entering an item into the retail
supply system. This includes the administrative cost of setting up a bin
for the item at the wholesale supply point.
167 INITIAL CATALOGING COST 4NR-
The initial cost of in, whole dollars, of entering a new item into the
wholesale supply system. This is generally considered to be the cost of
screening the item and assigning an NSN.
168 INPUT POWER SOURCE 25X-AS
The operating power requirements necessary for the TMDE to function and
operate properly. Consists of the following subfields.
a. Operating Range, 6N--
The voltage range which the Test Measurement and Diagnostic Equipment
(TMDE) requires to function properly. Subfields are:
(1) Minimum 3NR-
The minimum voltage which the TMDE requires

to function properly.
(2) Maximun 3NR-

MIL-STD-1388-2B
APPENDIX E
Electromagnetic sensitive item L

Facilities U
System peculiar spare part AA
Maintenance significant consumable AB
Modified hand tool AC
Maintenance assist module AD
Attaching hardware AE
Training Equipment AF
178 ITEM CRITICALITY NUMBER (Cr) 10 D --
The sum of the Failure Mode Criticality Numbers related to the failure
modes of an item within specific severity classifications and mission
phases . The following formula may be used to calculate Item Cr:
j
C r= E (Cm)n n=l,2,3 . . . ..j
n=1
where
Cr = Criticality number for the item
C m = Failure mode criticality number, DED 133
n = The failure modes in the items that fall under a particular
severity classification/mission phase combination
j = Last failure mode in the item under the severity
classification/mission phase combination
179 ITEM DESIGNATOR CODE 26X--
A part of nomenclature which provides a method for identifying equipment,

usually by broad performance and use characteristics and general con-
figuration. It is a data chain consisting of all or part of the data
elements type, model, and series designators, in that order. A suffix
may be added for use with the Joint Electronics Type Designation System,
Instructions for coding the type, model, and series designators are con-
tained in MIL-STD-482, appendix II, CM51 and consists of the following
subfields:
a. Type designator 7XL-
A broad categorization of equipment based upon function or use.
b. Model designator IOXL-
Identifies equipment within a particular type designator having

essentially the same performance characteristics.
c. Series designator 2XL-
Identifies equipment within a particular model designator having the same
basic design, but not necessarily the same configuration.
d. Suffix designator 7XL-

MIL-STD-1388-2B
APPENDIX E
supplemental information used with type, model series designators for

items using the Joint Electronics Type Designation Systems, Instructions
for coding suffix designator can be found in the following publications:
MIL-STD-155 Joint Photographic Type Designation
System
MIL-STD-196 Joint Electronics Type Designations
System
MIL-STD-815 Designation System for Liquid, Solid

and Liquid-solid (Hybrid) Propellant
Rocket Engines and Motor
MIL-STD-875 Type Designation System for
Aeronautical and Support Equipment
MIL-STD-879 Designation for Aircraft Propulsion
Gas Turbine Engines
AR 700-26 Designating and Naming Military Aircraft
NAVAIRINST 13100.3
AFR 66-11
AR 70-50 Designating and Naming Defense Equipment,
NAVMATINST 8800.4 Rockets, and Guided Missiles
AFR 82-5
ANA Bulletin 306 Engines, Aircraft Reciprocating,
Designation of
ANA Bulletin 395 Naval Ordnance Requirements, Mark

and Mod Nomenclature System
END ARTICLE ITEM DESIGNATOR. The item designator code of the end article
used in the 070 Report.
SYSTEM EQUIPMENT ITEM DESIGNATOR. The item designator code of the system
equipment item,
SYSTEM/EI ITEM DESIGNATOR CODE. The item designator code of the system/
end item.
180 ITEM FUNCTION 65X--
A narrative description identifying the function, specifications, and
tolerances of the-item under analysis (e.g., supply 10 gallons per minute
of hydraulic fluid at 3,000 psi for normal activation of pilot’s canopy,
hose , main landing gear extension, wheel brakes, and flap extension).
181 ITEM MANAGEMENT CODE (IMC) 1AF-
A single character indicating whether an item of supply shall be subject

to integrated management or shall be retained by the individual military

MIL-STD-1388-2B
APPENDIX E
Narrative specifying any limitations on the end item when dispatched on

its assigned mission with the analysis item inoperative.
245 MINIMUM REPLACEMENT UNIT (MRU) 3NR-
A minimum replacement unit quantity indicating the minimum quantity of an
item that is normally replaced/installed upon failure or scheduled
replacement.
246 MISSION PHASE CODE (MPC) 1XF-

A one-position code developed by the performing activity that uniquely
identifies a Mission Phase/Operational Mode, DED 247. Codes are A-Z,
O-9 and *. The asterisk indicates that the information contained for a
particular item is applicable to all mission phases.
247 MISSION PHASE/OPERATIONAL MODE 65X--
A concise statement of the mission phase/operational mode in which the
failure occurs. Where subphase, event, or time can be defined from
the system definition and mission profiles, the most definitive
timing information should also be described for the assumed time of
failure occurrence.
248 MOBILE FACILITY CODE 1AF-
A code which expresses the applicability of the SE to mobile facilities.
The following codes may be used:
SE required for mobile facility only V

SE not suitable for mobile facilities X
Support not restricted to mobile facilities or other N
site categories
249 MOBILITY TYPE 1AF-
A code which indicates the system/equipment type of mobility.
Skid A
Tracked B
Wheeled C
250 MODEL LOAD (HIGHWAY) 1AF-

The payload capacity of the transporter (truck, trailer, etc.)
Less than 5-ton payload capacity A

Five-ton to 10-ton payload capacity B
Greater than 10-ton payload capacity C
251 MODEL TYPE (HIGHWAY) 19XL-

The model type and number of the transporter.

MIL-STD-1388-2B
APPENDIX E
Supervision required - A YorN

Precision required - B YorN
Time standard - C YorN
288 PERSON IDENTIFIER 3XL-
A three-position code identifying each person required to perform the

subtask (codes “A” through “999”). Within a task, a given Person ID re-
lates to a specific “Job” and a specific Skill Specialty Code.
289 PERSONNEL TURNOVER RATE 4 N - AS
The portion of personnel, expressed in percent per year, leaving their

SSC which will be replaced by new personnel requiring training.
a. Military 2NR-
The military turnover rate.
b. Civilian 2NR-
The civilian turnover rate.
290 PHYSICAL AND MENTAL REQUIREMENTS 65X--
A narrative description identifying any unique physical or mental

personnel attributes required or recommended as prerequisites to full
qualification in the applicable task.
291 PHYSICAL SECURITY/PILFERAGE CODE 1XF-
A code which indicates the security classification or pilferage control

for physical assets. For applicable codes, see DOD 41OO.38-M.
292 PILOT REWORK/OVERHAUL CANDIDATE 1AF-
A code indicating selection status of certain complex assemblies/
components considered for pilot rework/overhaul (PR/0) as part of the
preoperational support program.
Item is nominated for PR/O program Y
Item is not nominated for PR/O program N
Item is approved as an PR/O candidate by the A
requiring authority
Items nominated are those which require additional skills, training,
support and test equipment, facilities, and technical data to ensure a
rework/overhaul capacity concurrent with government support of the end
item. Consideration shall be given to both intermediate rework and depot
level overhaul items.
293 PRECIOUS METAL INDICATOR CODE 1XF-

(PMIC)

MIL-STD-1388-2B
APPENDIX E
Supervision required - A YorN

Precision required - B YorN
Time standard - C YorN
288 PERSON IDENTIFIER 3XL-
A three-position code identifying each person required to perform the

subtask (codes “A” through “999”). Within a task, a given Person ID re-
lates to a specific “Job” and a specific Skill Specialty Code.
289 PERSONNEL TURNOVER RATE 4 N - AS
The portion of personnel, expressed in percent per year, leaving their

SSC which will be replaced by new personnel requiring training.
a. Military 2NR-
The military turnover rate.
b. Civilian 2NR-
The civilian turnover rate.
290 PHYSICAL AND MENTAL REQUIREMENTS 65X--
A narrative description identifying any unique physical or mental

personnel attributes required or recommended as prerequisites to full
qualification in the applicable task.
291 PHYSICAL SECURITY/PILFERAGE CODE 1XF-
A code which indicates the security classification or pilferage control

for physical assets. For applicable codes, see DOD 41OO.38-M.
292 PILOT REWORK/OVERHAUL CANDIDATE 1AF-
A code indicating selection status of certain complex assemblies/
components considered for pilot rework/overhaul (PR/0) as part of the
preoperational support program.
Item is nominated for PR/O program Y
Item is not nominated for PR/O program N
Item is approved as an PR/O candidate by the A
requiring authority
Items nominated are those which require additional skills, training,
support and test equipment, facilities, and technical data to ensure a
rework/overhaul capacity concurrent with government support of the end
item. Consideration shall be given to both intermediate rework and depot
level overhaul items.
293 PRECIOUS METAL INDICATOR CODE 1XF-

(PMIC)
Supersedes Da~e
L u 484 of 28 March 91 - 484 -
MIL-STD-1388-2B
APPENDIX E
A code which indicates the amount and type of precious metal contained in
a specific reference numbered item. For applicable codes, see DOD
41OO.38-M.
294 PREPARING ACTIVITY 25XL-
The name of the activity preparing SE data.

295 PRESERVATION MATERIAL CODE 2XF-
A code which indicates the material used to prevent or inhibit corrosion

or deterioration of an item. For applicable codes, see MIL-STD-2073
series.
296 PREVENTIVE MAINTENANCE CHECKS AND 1AF-
SERVICES (PMCS) INDICATOR CODE
A code which indicates whether or not the task code is applicable to the
PMCS tables.
Task is applicable to PMCS table Y
Task is not applicable to PMCS table N
297 PRIOR ITEM PROVISIONING LIST ITEM 5XL-

SEQUENCE NUMBER
(PRIOR ITEM PLISN)
The PLISN which appeared on the Interim Support Items List, the Long
Lead Times Items List, or first appearance of item in incremental pro
visioing submittals.
298 PROCUREMENT QUANTITY 3NR-
The number of systems/equipment being procured.
299 PRODUCTION LEAD TIME 2NR-
(PLT)
The computed or expected time interval in months between placement of a
new contract and shipment of the first deliverable quantity.
300 PRODUCTIVITY FACTOR 3NR2
This factor is used to account for nonproductive time and has the effect
of increasing manpower requirements for performing maintenance. For
instance, if the soldier’s scheduled work day is 8 hours, he may only be
available for 6 hours to do maintenance due to other duty assignments,
in this case, the productivity factor is ((8-6)/8) + 1 - 1.25.
301 PROGRAM ELEMENT 3XL-
A code consisting of up to three alphanumeric characters identifying
the applicable SE program element specified by the requiring authority.

MIL-STD-1388-2B
APPENDIX E
302 PROGRAM PARTS SELECTION LIST 1AF-

(PPS-L)
A code indicating whether the part is included within contractually

controlled Federal Supply Classes (FSC), as outlined in MIL-STD-965,
Parts Control Program. Codes assigned are as follows:
Part is included in contractually controlled A

FSCs and approved for use in PPSL
Part is included in contractually controlled N

FSCs and not approved for use in PPSL
303 PROGRAM SUPPORT INVENTORY CONTROL 2XF-

POINT
A government code to identify the service supporting Inventory Control

Point (ICP) where the using SE weapon/inventory manager is located.
Codes are as follows:
Service/Agency ICP Code
Marine Corps Marine Corps Logistics Base, Albany, GA PA
USAF Sacramento ALC, CA TA

Warner Robins ALC, Robins AFB, GA TG
San Antonio ALC, Kelly AFB, TX SE
Ogden ALC, Hill AFB, UT SU
Oklahoma City ALC, Tinker AFB, OK SX
AF Cryptologic Support Center (ESC), SJ
San Antonio, TX
Army Communications and Electronics Materiel CL

Readiness Command, Fort Monmouth, NJ
Tank Automotive Command, Warren, MI AZ
Missile Command, Redstone Arsenal, AL BD
Armament Munitions & Chemical Command BF
Rock Island, IL
Aviations Systems Command, St. Louis, MO CT
Troop Support Command, St. Louis, MO AJ
COMSEC Logistics Activity, Fort Huachuca, AZ CM
Navy Ships Parts Control Center, Mechanicsburg, PA HD

Aviation Supply Office, Philadelphia, PA KE
FAA Mike Monroney Aeronautical Center 48

Oklahoma City, OK
304 PROPER SHIPPING NAME 60 X L -
The proper shipping name of the item to be transported, if this name is

categorized as a hazardous material (e.g., CFR 49, UNTDF).

MIL-STD-1388-2B
APPENDIX E
1A1 ABC 0003 0003

1A1 R1 PDQ 0003 0006
1A1 R2 PDQ 0003 REF
1A1 MP2 XYZ 0006 0006
1A2 ABC 0000 REFX
1A3 ABC 0000 REFX
2. For nonreference designation oriented equipment:
Indenture Code Reference No. QTY-ASSY QTY-EI

B ABC 0001 0003
C PDQ 0003 0006
C PDQ 0003 REF
C XYZ 0006 0006
B ABC 0001 REFX
B ABC 0001 REFX
The following formula applies to option 2:
QTY/EI = E QTY/ASSYi
i-1
Where:
N - Number of applications for unique part
i = Application of unique part
Option 3. The QTY/EI shall be entered only on the first appearance of

the line item on the list for system/equipment for which the list is
prepared, and should equal the total number of appearances of the item in
that system/equipment (all appearances of an item may not appear on the
list) . Subsequent appearances of the same assembly or subassembly should
be indicated by printing “REFX” in positions 1-4. Subsequent appearances
of the same repair part (i.e., a part which has no lower indentured
parts) should be indicated by printing the letters “REF” in positions
1-3. This option can only be used with option 3 of the QTY/ASSY.
The following formula applies to option 3:
N M P-1 Q
QTY/EI = E[[ TT QTY/ASSY j ] i + E [ TT QTY/ASSY 1 ] k ] i
i=1 j=1 k=l 1=1
Where:
N = Number of applications of unique part (first appearance of NHA
only)
i = Application of unique part
M = Number of indenture levels
j = Indenture level of application at first appearance
P = Number of applications of unique assembly containing unique part

MIL-STD-1388-2B
APPENDIX E
Officer AR 611-101 NAVPERS AFR 36-1 MCO P 1200.7

15839
Warrant AR 611-112 NAVPERS --- MCO P 1200.7

Officer 15839
Enlisted AR 611-201 NAVPERS AFR 39-1 MCO P 1200.7

18068D
Civilian: DA CPR 502, AFR 36-1, AFR 39-1

FPM Supplement 512-1, Civil Service
Commission, Job Grading Standard
SKILL SPECIALTY CODE FOR SUPPORT EQUIPMENT OPERATOR. The SSC required to
operate the SE under analysis.
388 SKILL SPECIALTY EVALUATION CODE 1AF-
A single-position code denoting the adequacy of the identified SSC with

regard to the specific skills and knowledge required to accomplish the
identical task. Used as a flag to indicate the requirement for
additional training.
SSC is adequate A
SSC needs modification (additional training) M
New SSC should be established E
389 SOURCE, MAINTENANCE AND 6XL-

RECOVERABILITY CODE (SMR)
SMR codes are a series of alpha or alphanumeric symbols used at the time
of provisioning to indicate the source of supply of an item, its main-
tenance implications, and recoverability characteristics. The provision-
ing activity may require the contractor to recommend these codes.
a. Source Codes. These codes are assigned to support items to

indicate the manner of acquiring support items for maintenance, repair,
or overhaul of end items. Source codes are entered in the first and
second position of the Uniform SMR Code. Applicable codes are as
follows:
Definition Code
Item procured and stocked for anticipated or PA
known usage.
Item procured and stocked for insurance purposes PB

because essentiality dictates that a minimum
quantity be available in the supply systems.
Item procured and stocked and which otherwise PC

would be coded PA except that it is deteriorative
in nature.
Support item, excluding support equipment, PD

MIL-STD-1388-2B
APPENDIX E
procured for initial issue or outfitting and

stocked only for subsequent or additional initial
issues or outfittings. Not subject to automatic
replenishment.
Support equipment procured and stocked for initial PE

issue or outfitting to specified maintenance repair
activities.
Support equipment which will not be stocked but PF

which will be centrally procured on demand.
Item procured and stocked to provide for sustained PG

support for the life of the equipment. It is
applied to an item peculiar to the equipment which
because of probable discontinuance or shutdown of
production facilities would prove uneconomical to
reproduce at a later time.
An item of depot overhaul/repair kit and not KD

purchased separately. Depot kit defined as a kit
that provides items required at the time of
overhaul or repair.
An item of a maintenance kit and not purchased KF

separately. Maintenance kit defined as a kit that
provides an item that can be replaced at
organizational or intermediate levels of maintenance.
Item included in both a depot overhaul/repair kit

and a maintenance kit.
Item to be manufactured or fabricated at MO

organizational level.
Item to be manufactured or fabricated at MF

intermediate maintenance levels.
Air Force-Intermediate(*) Marine Corps-3rd Echelon
Army-Direct Support(*) Navy-Afloat
Item to be manufactured or fabricated at MH

intermediate maintenance levels.
Air Force-Intermediate(*) Marine Corps-4th Echelon
Army-General Support(*) Navy-Ashore
Item to be manufactured or fabricated at both MG

afloat and ashore intermediate maintenance
levels-Navy use only.
Item to be manufactured or fabricated at depot MD

maintenance level.
Item to be assembled at organizational level. AO
NEW PAGE - 513a -

MIL-STD-1388-2B
APPENDIX E
Item to be assembled at intermediate maintenance AF

levels.
Air Force-Intermediate(*) Marine Corps-3rd Echelon
Army-Direct Support(*) Navy-Afloat
Item to be assembled at intermediate maintenance AH

levels.
Air Force-Intermediate(*) Marine Corps-4th Echelon
Army-General Support(*) Navy-Ashore
Item to be assembled at both afloat and ashore AG

intermediate maintenance level-Navy use only.
Item to be assembled at depot maintenance levels AD
Item is not procured or stocked becuase the XA

requirements for the item will result in the
replacement of the next higher assembly.
Item is not procured or stocked. If not available XB

through salvage, requisition.
Installation drawing, diagram, instruction sheet, xc

field service drawing, that is identified by
manufacturer’ s part number.
(*) NOTE: For USAF and the USA Safeguard Program, only Code “F” will be
used to denote intermediate maintenance. On joint programs,
use of either code “F” or “H” by the joining service will
denote intermediate maintenance to USAF and the USA Safeguard
Program.
b. Maintenance codes. These codes are assigned to indicate the

levels of maintenance authorized to USE and REPAIR support items. The
maintenance codes are entered in the third and fourth position of the
Uniform SMR Code. Applicable codes are as follows:
USE (Third Position): The maintenance code entered in the third position
will indicate the LOWEST maintenance level authorized to remove, replace,
and use the support item. The decision to code the item for removal and
replacement at the indicated maintenance level will require that all
capabilities necessary to install and ensure proper operation after
installation of a replacement item (i.e., preinstallation inspection,
testing, and post-installation checkout) are provided. The maintenance
code, entered in the third position, will indicate one of the following
levels of maintenance.
Application/Explanation Code
Support item is removed, replaced, used at the O
organizational level of maintenance.
Note (l): To distinguish between the organizational

maintenance capabilities on different classes of
ships, the following codes may be used intra-Navy
513b - NEW PAGE

MIL-STD-1388-2B
APPENDIX E
only. On joint programs, Navy will receive and

transmit an O to indicate organizational maintenance
level.
2-Minesweeper, Yardcraft, Patrol Boat
3-Submarines
4-Auxiliary/Amphibious Ships
5-Major Combatant (Destroyer, Frigate)
6-Major Combatant (Cruiser, Carrier)
Note (2): On Army programs, a code of “C” may be

used in the third position to denote crew or
operator maintenance performed within organizational
maintenance. On joint programs, the Army will
receive or transmit an O to indicate organizational
level .
Support item is removed, replaced, used at the F

following intermediate levels.
USAF-Intermediate (*)
USA-Direct Support (*)
USN-Afloat
USMC-Third Echelon
Support item is removed, replaced, used at both G

afloat and ashore intermediate levels:
Navy only
Support item is removed, replaced, used at the H

following intermediate levels:
USA-General Support (*)
USN-Ashore (only)
USMC-Fourth Echelon
* Note: For the USAF program and USA Safeguard

program, Code F will be used to denote intermediate
maintenance. On joint programs, use of either
Code F or H by the joining service will denote
intermediate maintenance to USAF and the USA
Safeguard program.
Support Items that are removed, replaced, used at

Depot only:
USAF-Depot, Mobile Depot, and Specialized Repair
Activity
USA-Depot, Mobile Depot, Specialized Repair Activity
USN-Aviation Rework, Avionics and Ordnance Facilities,
Shipyards
USMC-Depot
REPAIR (Fourth Position): The maintenance code entered in the fourth

position indicates whether the item is to be repaired and identifies the
lowest maintenance level with the capability to perform complete repair
(i.e., all authorized maintenance functions). The decision to code the
support item for repair at the indicated maintenance levels requires that
NEW PAGE - 513c -

MIL-STD-1388-2B
APPENDIX E
all maintenance capability (remove, replace, repair, assemble, and test)

for the support items be provided to that level. This does not preclude
some repair which may be accomplished at a lower level of maintenance.
However, because of service differences in communicating maintenance
repair level information, a maintenance code entry fn this position is
not required by all services. When a maintenance code is not used, a
dash (-) sign will be entered. For multi-semice equipment/systems, or
when a code is entered, this position will contain one of the following
maintenance codes as assigned by the service(s) that require the code:
Application/Explanation Code
The lowest maintenance level capable of complete 0
repair of the support item is the organizational
level.
Note: To distinguish between the organizational

maintenance capabilities on different classes
of ships, the following codes may be used intra-Navy
only. On joint programs, Navy will receive and
transmit an O to indicate organizational
maintenance level.
2-Minesweeper, Yardcraft, Patrol Boat
3-Submarines
4-Auxiliary/Amphibious Ships
5-Major Combatant (Destroyer, Frigate)
6-Major Combatant (Cruiser, Carrier)
The lowest maintenance level capable of complete F

repair of the support item is the following
intermediate level:
USN-Afloat
USMC-Third Echelon
The lowest maintenance level capable of complete H

repair of the support item is the following
intermediate level:
USN-Ashore (Only)
USMC-Fourth Echelon
* Note: For USAF program and the USA safeguard

Codes F or H by the joining service will denote
Safeguard program.
Both afloat and ashore intermediate levels are G

capable of complete repair of support item: Navy
only.
- 513d - NEW PAGE

MIL-STD-1388-2B
APPENDIX E
The lowest maintenance level capable of complete D

repair of the support item is the depot level:
USAF-Depot, Mobile Depot, and Specialized Repair
Activity
USA-Depot, Mobile Depot, Specialized Repair Activity
USN-Aviation Rework, Avionics, and Ordnance
Facilities, Shipyards
USMC-Depot
Repair restricted to designated Specialized Repair L

Activity.
Nonreparable. No repair is authorized. Z
No repair is authorized. The item may be B

reconditioned by adjusting, lubricating, etc. , at
the user level. No parts or special tools are
procured for the maintenance of this item.
c. Recoverability Codes. These codes are assigned to support items

to indicate the disposition action on unserviceable items. The
recoverability code is entered in the fifth position of the Uniform SMR
Code. Applicable codes are as follows:
Definition Code
Nonreparable item. When unserviceable, condemn Z
and dispose at the level indicated in column 3.
Reparable item. When uneconomically repairable, O

Condemn and dispose at organizational level.
Reparable item. When uneconomically repairable, F

condemn and dispose at the following intermediate
levels:
USN-Afloat
USMC-Third Echelon
Reparable item. When uneconomically repairable, H

condemn and dispose at the following intermediate
levels:
USN-Ashore
USMC-Forth Echelon
* Note: For USAF program and the USA safeguard

Codes F or H by the joining service will denote
Safeguard program.
NEW PAGE - 513e -

MIL-STD-1388-2B
APPENDIX E
Reparable item. When beyond lower-level repair D

capability, return to depot. Condemnation and
disposal not authorized below depot level.
Reparable item. Repair, condemnation, and disposal L

not authorized below depot/Specialized Repair
Activity level.
Item requires special handling or condemnation A

procedures because of specific reasons (i.e.,
precious metal content, high-dollar value,
critical material, or hazardous material). Refer
to appropriate manuals/directives for specific
instructions.
d. Service Peculiar Codes. These codes are peculiar to each

service/program and are assigned accordingly. These codes are entered in
the sixth position of the Uniform SMR Code.
SE SOURCE, MAINTENANCE AND RECOVERABILIY CODE. The SMR of the support

equipment under analysis.
390 SPARE FACTOR 4XF-
A specific quantity or percentage developed to guide the government’s

determination of requirements (procurement of end items over and above
operational quantities) to provide replacement for an item(s) subject to
damage, survey/disposal. An example follows:
A specific quantity QXXX

Percentage of operational assets PXXX
quantity (for consumables only)
No spares required QOOO
391 SPARES ACQUISITION INTEGRATED WITH 1AF-

PRODUCTION (SAIP)
NEW PAGE - 513f -

MIL-STD-1388-2B
APPENDIX E
An alphabetic code indicating that the item is a candidate for an SAIP

list.
Item is an SAIP list candidate Y

Item is not an SAIP list candidate blank
392 SPECIAL MAINTENANCE ITEM CODE (SMIC) 1AF-
A code which indicates any special maintenance category applicable to the
line item. Codes assigned are as follows:
Nonrepairable A
Factory repairable B
Matched set C
Select at test D
MAMS (Maintenance Assistance Modules). An item F
authorized or recommended by the government/
contractor for procurement and location with
the end item as the sole means of fault
isolation in the event of failure. Contractor
recommendations shall be IAW the maintenance
philosophy approved by the government.
(e.g., modules employed in diagnostic circuitry
used for “built-in” fault isolation).
Remain in Place. A repairable item which, upon

removal without an immediate replacement,
would: a. Destroy structural integrity;
b. Endanger operating or maintenance personnel;
or, c. If partially degraded, cause total &grad-
ation of an essential function of the end item.
Safety. An item which, upon failure, would H
jeopardize the direct safety of operating or
maintenance personnel.
393 SPECIAL MANAGEMENT 1AF-

A code to flag an SE end item for special management attention. Codes
are as follows:
Management Concern Code Criteria

Time T SE end item will not be available
concurrently with end article, SE
ILS, or the development lead time
is excessive.
Price P SERD identified development prices
or recurring unit price are sub-

MIL-STD-1388-2B
APPENDIX E
tantially above the average

SE end item.
State of the art A SE end item is state-of-the-art

and required the development of
an end item specification/
requires reliability qualification.
Safety S SE end item is proposed to correct a

safety defect.
Mission essentiality M SE end item is essential to conduct

of the end article’s mission.
N Not applicable
394 SPECIAL MARKING CODE 2XF-
A code which identifies special markings which are required as an

integral part of the total pack to protect the contained item during
preservation, packing, storage, transit, and removal from the pack.
For applicable codes, see MIL-STD-2073-1 and MIL-STD-2073-2.
395 SPECIAL MATERIAL CONTENT CODE 1XF-

(SMCC)
A cede indicating that an item represents or contains peculiar material

requiring special treatment, precautions, or management control of the
item (see DOD 4100.38-M for applicable codes).
396 SPECIAL PACKAGING INSTRUCTION 10XL-

NUMBER
A number which identifies a specific special packaging instruction

prepared IAW MIL-STD-2073-1 and MIL-STD-2073-2.
397 SPECIAL PACKAGING INSTRUCTION (SPI) 1AF-

NUMBER REVISION
A code which identifies the SPI revision.
Codes A through Z
398 SPECIALIZED SERVICE AND EQUIPMENT 65X--

REQUIREMENTS
Narrative information concerning the requirements for special rail cars,

highway vehicles, or material handling equipment such as spreader bars or
Slings.
399 SPECIFIC AUTHORIZATION 71X--
Identifies the type of activity, number of type activities, and the

quantity of support/test equipment or training material which is to be

MIL-STD-1388-2B
APPENDIX E
supported at each activity. Unless otherwise advised by the requiring

authority, the support period shall be for one year beginning with the
scheduled delivery of the first end item. This shall be confirmed or
changed by the government. Consists of the following subfields:
a. Number of activities 3NR-
The specific number of activities of a type (e.g., 6 depots,

2 squadrons).
b. Type of activity 15XL-
The activities by type. Examples of these activities are: training,

specialized repair activity, depot, etc. , including preoperational ac-
tivities whose allowances are not derived from the Basis of Issue.
c. Name/location of activity 50XL-
The name and location of the activity to be allocated support equipment

to include the activity address indicator.
d. Quantity per activity 3NR-
The quantity of support/test equipment or training materiel to be

provided to each activity.
400 SPEED 3NR-
The maximum speed of the system/equipment in miles per hour.
401 STANDARD INTERSERVICE AGENCY SERIAL 7XF-

CONTROL NUMBER (SIASCN)
A seven-position alphanumeric code assigned to executive service managed

items in support of provisioning of multiservice systems and equipment.
The SIASCN is assigned to all items which require NSN assignment/
supported service(s) user registration. The SIASCN is composed of a
specific alphabetic prefix designating the executive service Inventory
Control Point (ICP) followed by six numeric characters as specified by
the requiring authority. Alphabetic prefixes have been assigned to
specific ICPs as follows:
Service/Agency ICP Managing Activity Prefix
Marine Corps Marine Corps Logistics Base, A

Albany, GA
U.S. Air Force Sacramento ALC, CA B

Warner Robins ALC, Robins AFB, GA C
San Antonio ALC, Kelly AFB, TX D
Ogden ALC, Hill AFB, UT E
Oklahoma City ALC, Tinker AFB, OK F
AF Cryptologic Support Center (ESC), J
San Antonio, TX
MIL-STD-1388-2B
APPENDIX E
Partial Mission Capable. Performance of the maintenance task degrades

the mission capability of the system. To be in Partial Mission Capable
status the system must have the capability to perform at least one war
time mission. Systems with no wartime mission must be able to perform
any one mission to be in this status.
Partial Mission Capable D
Svstem Inoperable During Equipment Maintenance. During the performance

of the maintenance task the system is not available to perform all normal
operations .
System Inoperable during Equipment Maintenance A
System Operable During Equipment Maintenance. During performance of the

maintenance task the system is available to perform normal operations.
System Operable during Equipment Maintenance B
Not Mission Capable. During performance of the maintenance task the sys-
tem cannot perform any wartime mission. Systems which have no wartime
mission must not be capable of performing any mission in order to be in
the Not Mission Capable status.
Not Mission Capable E
Off Equipment Maintenance. Maintenance task is performed after the item

under analysis has been removed from the system.
Off Equipment Maintenance G
Turnaround. Performance of the maintenance task occurs during normal

turnaround operations and does not affect the operability of the system.
Turnaround F
f. Task Sequence Code 2XF-
A two-position code assigned to each task. If the combination of the

previous task code fields (task function, task interval, service designa-
tor, O/M level, and Operability Code) are unique, the entry will be “AA”.
If the first five fields are duplicated, within an LCN/ALC combination,
the follow-on task sequence codes will be AB through 99 to differentiate
the tasks.
REFERENCED TASK CODE. A task code that contains referenced task

information.
REFERENCED SUBTASK TASK CODE. A task code that contains referenced

subtask information.
TASK PROVISION TASK CODE. A task code of the item under analysis.
428 TASK CONDITION 3AL-

MIL-STD-1388-2B
APPENDIX E
Indicator that special considerations must be taken into account during

analysis of the task.
TM/Technical Order use not feasible (inadequate

lighting, space constraints, or time constraints) - A Y or N
TMDE/ATE/BIT/BITE required - B Y or N
Special tools required - C Y or N
429 TASK CRITICALITY 1AF-
A single-position code keyed to task level entries in sequential
descriptions and used to indicate whether or not the task is critical. A
task is critical if failure to accomplish it IAW system requirements
would result in adverse effects on system reliability, efficiency, effec-
tiveness, safety, or cost. A task will also be designated as critical
whenever system design characteristics approach human limitations, and
thereby, significantly increase the likelihood of degraded, delayed, or
otherwise impaired mission performance.
Critical Y
Not critical N
430 TASK FREQUENCY 7NR4
The frequency of performance or occurrence of the task identified by the
task code and expressed as the number of annual occurrences. For
corrective tasks the following formula applies:
M N
1 1
TF = [ E [ E FM Ratioi (FR + MTMB-IN + MTMB-ND)X CON FAC ]] X AOR
j=l i-l
Where: TF = Task frequency

FM Ratio = Failure mode ratio, DED 136
FR = Failure rate, DED 140
MTBM -IN = Mean time between Maintenance (induced), DED 231
MTBM -ND = Mean time between maintenance (no defect), DED 233
i = Failure mode referencing task under analysis
N = Number of failure modes referencing task under
analysis
j = Unique LCN/ALC referencing task under analysis
M = Number of LCN/ALCs referencing task under analysis
CON FAC = Conversion factor against each LCN/ALC referencing the
task under analysis, DED 059
AOR = Annual operating requirement, DED 023
For preventive tasks, one of the following procedures applies:
Method 1. Annual Operating Requirement X Conversion Factor

TF = Maintenance Interval
- 530 -
MIL-STD-1388-2B
APPENDIX E
Note: Measurement bases for AOR and maintenance interval (DED 208) must
be identical. The task frequency calculation is performed for the task
reference associated with the maintenance interval.
Method 2. When the frequency of performance of a preventive task is

based on calendar time, the task frequency is a numeric expression of the
task code, task interval code (DED 427), established as a result of RCM
analysis.
Example: Interval Task Frequency

Daily (C) 365.0000
Weekly (L) 52.0000
431 TASK IDENTIFICATION 36XL-
A task is a composite of related activities (perceptions, decisions, and

responses) performed for an immediate purpose, written in operator/
maintainer language. Task identification requires a brief narrative
entry consisting of: (a) an action verb which identifies what is to be
accomplished in the task or subtask; (b) an object which identifies what
is to be acted upon in the task/subtask; and, (c) qualifying phrases
needed to distinguish the task from related or similar tasks. Recommen-
ded action verbs to be used in preparing task or subtask identifications
may be drawn from following list. Some specialized verbs, not listed
below may be needed for a particular system/equipment. Many verbs are
synonymous. The preparing activity should select one verb which ap-
pears closest to the intended meaning for the system/equipment under
analysis, and use that verb consistently throughout the analysis. Some
verbs are more appropriate for writing statements of tasks, while some
verbs are exclusive to subtask elements.
Access. (a) To gain visibility of or the ability to manipulate.

(b) To cause to be displayed, as with a computer menu.
Accomplish. To do, carry out, or bring about; to reach an objective.
Achieve. To carry out successfully.
Acknowledge. To make known the receipt or existence of.
Actuate. To put into mechanical motion or action; to move to action.
Adjust. (a) To bring to a specified position or state. (b) To bring to

a more satisfactory state; to manipulate controls, levers, linkages,
etc., to return equipment from an out of tolerance condition to an in
tolerance condition.
Administer. To manage or supervise the execution, use, or conduct of.
Advance. To move forward; to move ahead.

MIL-STD-1388-2B
APPENDIX E
Advise. To give information or notice to.
Alert. To warn; to call to a state of readiness or watchfulness; to

notify (a person) of an impending action.
Align. To bring into line; to line UP; to bring into precise adjustment,
correct relative position; or coincidence.
Allocate. To apportion for a specific purpose or to particular persons

or things.
Allow. (a) To permit; to give opportunity to. (b) To allot or provide

for. (c) To carry out a procedure.
Analyze. To examine and interpret information.
Annotate. To append explanatory information to a text or” graphic summary

of information.
Announce. To make known,
Apply. (a) To lay or spread on. (b) To energize.
Approve. To give offical sanction.
Archive. To make an archival copy of.
Arrange. To group according to quality, value, or other characteristics;

to put in proper order.
Assault. Close combat phase of an attack.
Assemble. To fit and secure together the several parts of; to make or
form by combining parts.
Assess. To determine the importance, size, or value of; to evaluate.

Assign. To apportion to for a specific purpose or to particular persons
or things; to appoint to a duty.
Assist. To give support or help; to aid.
Attach. To join or fasten to.
Authenticate. To prove or serve to prove the authenticity of.
Balance. To equalize in weight, height, number, or proportion.
Breach. (a) To break through. (b) To secure passage through.

Brief. To give final precise instructions; to coach thoroughly in
advance; to give essential information to.
- 532 -
REPRINTED WITHOUT CHANGE
MIL-STD-1388-2B
APPENDIX E
SKID AREA UNIT OF MEASURE. A UM associated with the skid area.

-
STORAGE DIMENSIONS UNIT OF MEASURE. A UM associated with the length,
width, and height of the SE in the storage mode.
STORAGE WEIGHT UNIT OF MEASURE. A UM associated with the weight of the

SE in the storage mode.
SUPPORT EQUIPMENT SHIPPING DIMENSIONS UNIT OF MEASURE. A UM associated

with the length, width, and height of the SE in the shipping mode.
SUPPORT EQUIPMENT SHIPPING WEIGHT UNIT OF MEASURE. A UM associated with

the weight of the SE in the shipping mode.
SUPPORT ITEM QUANTITY PER TASK UNIT OF MEASURE. A UM used in conjunction

with the support item quantity per task.
TRACKED PAD SHOE AREA UNIT OF MEASURE. A UM associated with tracked pad
shoe area.
492 UNIT OF MEASURE PRICE 10NR2

(UM PRICE)
The best estimated price per UM. The last two positions of the field
represent cents, and the decimal is understood.
FACILITY CONSTRUCTION UNIT OF MEASURE PRICE. The best estimated price

for facility construction per UM.
493 UNIT PACK CUBE 7NR3

The length times width times depth (or cubic dimensions) of the unit
container expressed in feet.
494 UNIT PACK SIZE 12N--

The length, width, and depth of the unit container or package expressed
in inches. Subfields are:
a. Length 4NR1
b. Width 4NR1
c. Depth 4NR1
495 UNIT PACK WEIGHT 5X--
The gross weight of the unit pack expressed in pounds. The field is
structured as follows.
a. For weights up to 9,999.9 pounds 5NR1

b. For weights over 9,999.9 pounds 5 X - -

MIL-STD-1388-2B
APPENDIX E
First subfield. 1AF-
Multiplier code indicates that the number entered in the second subfield
should be multiplied by 10, 100 or 1000 in order-to. correctly represent
the unit pack weight, Codes are as follow:
10 X weight A
100 X weight B
1000 X weight C
Second subfield. 4NRAS
Numerical value of the weight expressed in pounds.

496 UNIT SIZE 12N--
The length, width, and height of the item, as configured for packaging,
expressed in inches. Subfields are as follow:
a. Length 4NR1
b. Width 4NR1
c. Height 4NR1
497 UNIT WEIGHT 5X--
The unpackaged weight of the item expressed in pounds. The field is

structured as follows:
a. For weights up to 9,999.9 5NR1
b. For weights over 9,999.9 5X--
First subfield. 1AF-

Multiplier code indicates that the number entered in the second subfield
should be multiplied by 10, 100 or 1000 in order to correctly represent
the unit weight. Codes are as follow:
10 X weight A
100 X weight B
1000 X weight c
Second subfield. 4NRAS
Numerical values ‘of the weight expressed in pounds.
498 UNIT UNDER TEST EXPLANATION 65X--
Narrative statements which further explain, justify, or substantiate any

data entry concerning unit WT related data (U) tables.
499 UNSCHEDULED MAINTENANCE 1ON-AS

MIL-STD-1388-2B
LSAR DATA REQUIREMENTS FORM

GENERAL INFORMATION
Selection of a data element shall constitute the selection of all data keys
or data dependencies required to document the element in the LSAR. Where
more than one data element code applies to a data selection, the Code column
contains dashes (-). For narrative data, where each data element definition
is separately selectable to a common data table, the code column is blank.
This Form consists of two sections. The first section consists of government
furnished data. The second section consists of the LSAR Data Requirements
Form and is divided into three parts. Part I is LSAR data selected by an
entry in the required column. Part II is LSAR provisioning data selected by
an entry in the type of provisioning list. Part III is packaging data
selected by an entry under a packing categorization.
Explanation of codes appearing under the KEY column are provided below:
KEY KEY EXPLANATION
K Data table key. It is required when any data element of the

table is selected.
F Foreign key. It originates in another data table and is required

prior to a data element of the table being documented. Foreign keys
appear only once on the data requirements form within a major area,
e.g., Task Analysis and Personnel and Support Requirement.
M Mandatory data. It is a nonidentifying data element that is

required when entering information in the data table.
G Data element provided by the requiring authority.
B Data element that is both a key/foreign key and is provided by the

requiring authority.
A Army peculiar data element.
N Navy peculiar data element.
R Air Force peculiar data element.
C Marine Corps peculiar data element.
PART II Provisioning Requirements
MEDIA
7-Track Even Parity BCD Coded

9-Track Odd Parity EBCDIC Coded
800 BPI 1600 BPI 6250 BPI
Number of records per block is:
FIGURE 71. Example of DD-Form 1949-3.

DD FORM 1949-3, AUG 92 Page 1 of 29
MIL-STD-1388-2B
GENERAL INFORMATION
The appropriate code(s) for the header data and sequence should be entered in
The appropriate spaces for the Type Provisioning Lists. .
HEADER DATA
Procurement Instrument Identification (PIIN/SPIIN) P

Nomenclature or Model or Type Number N
Control Data C
Prime Commercial and Government Entity E
Submission Control Code S
Date (YYMMDD) Y
Sequence (Provisioning List Item Sequence Number assignment):

Logistic Support Analysis Control Number Topdown
-
T
Disassembly D
Reference Designation X
Reference Number R
Conference
Type Provisioning Lists: Required Required
Specify (T,D,X,R) (P,N,C,E,S,Y) (Y,N)
Long Lead Time Items List (LLTIL)

Provisioning Parts List (PPL)
Short Form PPL (SFPPL)
Common and Bulk Items List (CBIL)
Repairable Items List (RIL)
Interim Support Items List (ISIL)
Post Conference List (PCL)
Tools and Test Equipment List (TTEL)
System Configuration PPL (SCPPL)
Design Change Notices (DCN)
As Required (ARA) and specified in the SOW
As Required (ARB) and specified in the SOW
Required(Y,N) Time Date (YYMMDD)
Provisioning Guidance Conference
Location
Provisioning Conference
Location
Provisioning Preparedness Review Conference
PART III, Packaging Requirements

Common, MIL-STD-2073-1B, paragraph 3.3.1
Selective, MIL-STD-2073-1B, paragraph 3.3.2
Special, MIL-STD-2073-1B, paragraph 3.3.3
Other Instructions
FIGURE 71. Example of DD-Form 19.49-3.

- 572 -
MIL-STD-1388-2B
GENERAL INFORMATION
Header Data should be documented for each type provisioning list identified.
Type Provisioning List
HEADER DATA
Procurement Instrument Identification (PIIN/SPIIN)
Nomenclature or Model or Type Number
Control Data
Prime Commercial and Government Entity
Submission Control Code
Date (YYMMDD)
Provisioning Activity (Address and Zip Code)
Contractor Name (Address and Zip Code)
Answer these question as yes or no. (Y or N)
Interim Support Items (Required)

Incremental Submission (Authorized)
Resident Provisioning Team (Established)
Interim Release (Authorized)
Provisioning Performance Schedule (Required)
Repair Kits and Repair Part Sets (Included)
Military Service/Agency Addendum (Attached)
Common and Bulk Items List (Options 1-5, Select 1)
Delivery of Support Items Will Be (Concurrent, Scheduled, Not Scheduled, Select 1)
Engineering Data for Provisioning (Microfilm, Hard Copy, Aperture Cards,

Digital/CALS)
Engineering Data for Provisioning (Will be sequenced by Reference Designation,

PLISN, Reference Number, Other, Select 1)

-573 - Supersedes page 573 of 28 March 91
MIL-STD-1388-2B
SECTION 1 GOVERNMENT FURNISHED DATA
This information should be filled out by the requiring authority and should
pertain to the End Item only.
Table XA
End Item Acronym Code, DED 096
Administrative Lead Time, DED 014
Contact Team Delay Time, DED 052
Contract Number, DED 055
Cost Per Reorder Action, DED 061
Cost Per Requisition, DED 062
Demilitarization Cost, DED 077
Discount Rate, DED 083
Estimated Salvage Value, DED 102
Holding Cost Percentage, DED 160
Intial Bin Cost, DED 166
Inital Cataloging Cost, DED 167
Interest Rate, DED 173
Inventory Storage Space Cost, DED 176
Loading Factor, DED 195
Operation Level, DED 271
Operation Life, DED 272
Personnel Turnover Rate Civ, DED 289
Personnel Turnover Rate Mil, DED 289
Productivity Factor, DED 300
Recurring Bin Cost, DED 333
Recurring Cataloging Cost, DED 334
Retail Stockage Criteria, DED 359
Safety Level, DED 363
Support of Support Equipment, DED 421
Transportation Cost, DED 466
Type Acquisition, DED 478
Type of Supply System Code, 484
Table AI
Modeling Service Des. Code, DED 376
Modeling O/M Level Code, DED 277
Labor Rate, DED 189
Number of Shops, DED 263
Repair Work Space Cost, DED 352
Required Days of Stock, DED 357
Table AJ
O/M Level From, DED 277
O/M Level To, DED 277
Ship Distance, DED 085
Ship Time, DED 379
Table AK
Add. Supportability Consids, DED 010
Add. Supportability Parameters, DED 011
Oper. Mission Failure Def., DED 274

MIL-STD-1388-2B
pertain to the Item (LSA Control Number) under analysis.,
Table XB
LSA Control Number, DED 199
Table XC
Usable On Code, DED 501
System/End Item PCCN, DED 307
Table AA
Service Desginator Code, DED 376
Required MTTR, DED 222
Required Percentile, DED 286
Required Ach. Availability, DED 001
Required Inh. Availability, DED 164
Operational MAMDT, DED 223
Technical MAMDT, DED 223
Required Operational MTTR, DED 236
Required Technical MTTR, DED 236
Number of Operating Locations, DED
Crew Size, DED 064
Total Systems Supported, DED 454
RCM Logic Utilized, DED 345
Table AB
Operational Reqt Indicator, DED 275
Annual Number of Missions, DED 021
Annual Operating Days, DED 022
Annual Operating Time, DED 024
Mean Mission Duration, DED 228
Mean Mission Duration MB, DED 238
Required Op. Availability, DED 273
Required ALDT, DED 013
Required Standby Time, DED 403
Table AC
O/M Level, DED 277
Maintenance Level MaxTTR, DED 222
Maintenance Level Percentile, DED 286
Number of Systems Supported, DED 265
Maint. Level Scheduled AMH, DED 020
Maint. Level Unscheduled AMH, DED 020
Scheduled MH/Operating Hour, DED 215
Unscheduled MH/Operating Hour, DED 215
Unscheduled Maintenance MET, DED 499
Unscheduled Maintenance MMH, DED 499
Table AD
Daily Inspection MET, DED 280
Daily Inspection MMH, DED 280
Preoperative Inspection MET, DED 280
Preoperative Inspection MMH, DED 280
DD FORM 1949-3, AUG 92 FIGURE 71. Example of DD-Form 1949-3. Page 5 of 29
MIL-STD-1388-2B
Post Operative Inspection MET, DED 280

Post Operative Inspection MMH, DED 280
Periodic Inspection MET, DED 280
Periodic Inspection MMH, DED 280
Mission Profile Inspection MET, DED 280
Mission Profile Inspection MMH. DED 280
-.
Turnaround Inspection MET, DED 280
Turnaround Inspection MMH, DED 280
Table AE
Available Man Hour, DED 028
Available Quantity, DED 324
Utilization Ratio, DED 503
Table AF
Additional Requirements, DED 009
Table AG
AOR MB, DED 238
Annual Operating Requirement, DED 023
Required Operational MTBF, DED 229
Required Technical MTBF, DED 229
Required Operational MTBMA, DED 230
Required Technical MTBMA, DED 230
Required MTBR, DED 235
Table AH
Interoperable Item Name, DED 182
Interoperable Number Type, DED 266
Interoperable CAGE Code, DED 046
Interoperable Reference Number, DED 337
-.
Interoperable Item NIIN, DED 253
Interoperable Item NSN FSC, DED 253
Interoperable Item TM Number, DED 440

MIL-STD-1388-2B
pertain to a piece of Support Equipment that is supporting the item under
analysis.
Table EA and EB
Support Equipment Cage, DED 046
SE Reference Number, DED 337
Table EA
Acquisition Decision Office, DED 002
Logistics Decision Office, DED 198
Management Plan, DED 216
SMR Code, DED 389
Program Element, DED 301
Program Sup. Inv. Control Pt., DED 303
Revolving Assests, DED 361
Spare Factor, DED 390
Special Management Code, DED 393
SIASC Number, DED 401
SE Shipping Height, DED 419
SE Shipping Length, DED 419
SE Shipping Width, DED 419
SE Shipping Weight, DED 420
Type of Equipment Code, DED 480
Table EB
Allowance Document Number, DED 016
Allowance Range 1, DED 015
Allocation Designation Descr., DED 015
Allocation Extended Range, DED 015
Allocation Land Vessal Code, DED 015
Allocation Manit. Lvl Function, DED 015
Allocation Station ID Code, DED 015

MIL-STD-1388-2B
pertain to the item under analysis.
Table UA
UUT LSA Control Number, DED 199
UUT Maintenance Plan Number, DED 209
Table HA
CAGE Code, DED 046
Reference Number, 337
Acquisition Method Code, DED 003
Acquisition Method Suffix Code, DED 004
Table HG and HP
Cage Code, DED 046
Reference Number, DED 337
Table HG
Provisioning Sys ID Code, DED 312
Table HP
Change Authority Number, DED 043

HIL-STD-1388-2B
SECTION1 GOVERNMENT FURNISHED DATA
Post Operative Inspection MET, DED 280
Post Operative Inspection MMH, DED 280
Periodic Inspection MET, DED 280
Periodic Inspection MMH, DED 280
Mission Profile Inspection MET, DED 280
Mission Profile Inspection MMH, DED 280
Turnaround Inspection MET, DED 280
Turnaround Inspection MMH, DED 280
Table AE
Available Man Hour, DED 028
Available Quantity, DED 324
Utilization Ratio, DED 503
Table AF
Additional Requirements, DED .
Table AG
AOR MB, DED 238
Annual Operating Requirement, DED 023
Required Operational MTBF, DED 229
Required Technical MTBF, DED 229
Required Operational MTBMA, DED 230
Required Technical MTBMA, DED 230
Required MTBR, DED 235
Table AH
Interoperable Item Name, DED 182
Interoperable Number Type, DED 266
Interoperable CAGE Code, DED 046
Interoperable Reference Number, DED 337
Interoperable Item NIIN, DED 253
Interoperable Item NSN FSC, DED 253
Interoperable Item TM Number, DED 440

MIL-STD-1388-2B
pertain to a piece of Support Equipment that is supporting the item under
analysis.
Table EA and EB
Support Equipment Cage, DED 046
SE Reference Number, DED 337
Table EA
Acquisition Decision Office, DED 002
Logistics Decision Office, DED 198
Management Plan, DED 216
SMR Code, DED 389
Program Element, DED 301
Program Sup. Inv. Control Pt., DED 303
Revolving Assests, DED 361
Spare Factor, DED 390
Special Management Code, DED 393
SIASC Number, DED 401
SE Shipping Height, DED 419
SE Shipping Length, DED 419
SE Shipping Width, DED 419
SE Shipping Weight, DED 420
Type of Equipment Code, DED 480
Table EB
Allowance Document Number, DED 016
Allocation Designation Descr., DED 015
Allocation Extended Range, DED 015
Allocation Land Vessal Code, DED 015
Allocation Manit. Lvl Function, DED 015
Allocation Station ID Code, DED 015

MIL-STD-1388-2B
pertain to the item under analysis.
Table UA
UUT LSA Control Number, DED 199
UUT Maintenance Plan Number, DED 209
Table HA
CAGE Code, DED 046
Reference Number, 337
Acquisition Method Code, DED 003
Acquisition Method Suffix Code, DED 004
Table HG and HP
Cage Code, DED 046
Reference Number, DED 337
Table HG
Provisioning Sys ID Code, DED 312
Table HP
Change Authority Number, DED 043

MIL-STD-1338-2B
FIGURE 71. Example of DD-Form 1949-3

MIL-STD-1338-2B

Page 10 of 29
DD FORM 1949-3, AUG 92 - 580 -
MIL-STD-1338-2B
FIGURE 71. Example of DD-FORM 1949-3.
Page 11 of 28
DD FORM 1949-3, AUG 92

MIL-STD-1388-2B

Page 14 of 29
MIL-STD-1388-2B

MIL-STD-1338-2B

MIL-STD-1338-2B


MIL-STD-1338-2B


MIL-STD-1338-2B
FIGURE 71. Example of DD-FORM 1949-3.


MIL-STD-1338-2B

Page 22 of 29
DD FORM 1949-3, AUG, 92
MIL-STD-1338-2B

MIL-STD-1338-2B


MIL-STD-1388-2B


MIL-STD-1338-2B



Page 28 of 29
MIL-STD-1338-2B

Page 29 of 29
- 599/600 - Supersedes page 599/600 of 28 March 91
THIS PAGE INTENTIONALLY LEPT BLANK

Mil STD 1388 2B - Notice 1 PDF

Uploaded by

Copyright:

Available Formats

Mil STD 1388 2B - Notice 1 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mil STD 1388 2B - Notice 1 PDF

Uploaded by

Copyright:

Available Formats

Downloaded from http://www.everyspec.

Custodians: Preparing Activity

v REPRINTED WITHOUT CHANGE

APPENDIX A. LSAR RELATIONAL TABLES . . . . . . . . . . . . . . . . . . . . . . 21

APPENDIX B. LSAR REPORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Supersedes page vi of 28 March 91 vi

vii Supersedes page vii of 28 March 91

APPENDIX D. APPLICATION AND TAILORING GUIDANCE FOR THE 335

APPENDIX F. LIST OF LOGISTIC SUPPORT ANALYSIS RECORD ACRONYMS 563

I LSA-036 report format . . . . . . . . . . . . . . . . . . . . . . 136

ix/x Supersedes page ix/x of 28 March 91

THIS PAGE INTENTIONALLY LEPT BLANK

MIL-STD-879 Designation of Aircraft Propulsion Gas Turbine Engines

MIL-STD-965 Parts Control Program

MIL-STD-1390 Level of Repair Analysis

MIL-STD-1478 Task Performance Analysis

MIL-STD-1843 Reliability Centered Maintenance for Aircraft, Engines,

MIL-STD-2073-1 DOD Materiel, .Procedures for Development and Application

MIL-STD-2173 Reliability Centered Maintenance Requirements for Naval

MIL-M-63036 Manuals, Technical: Operator’s, Preparation of (Army)

-7- Supersedes page 7 of 28 March 91

MIL-M-83495 Manuals, Technical: On-Equipment Set, Organizational

Federal Manuals and Catalogs.

H6-1 Federal Item Name Directory for Supply Cataloging

(Unless otherwise indicated, copies of federal and military specifications,

DOD 41OO.38-M DOD Provisioning and Other Preprocurement Screening

DODD 5000.2 Acquisition Management Policies and Procedures

AR 70-50 Designating and Naming Defense Equipment

NAVPERS 18068 Manual of Navy Enlisted Manpower and Personnel

Supersedes page 8 of 28 March 91 -8-

AR 611-101 Manual of Commissioned Officer Military Occupational

AFR 39-1 Airman Classification Manual

JCS PUB 1 Dictionary of United States Military Terms for Joint

3.3 Component. An assembly or any combination of parts, subassemblies, and

3.5 End Article/Product. A component, assembly or subassembly being procured

3.11 Part Number. See reference number.

3.15 Subassembly. Two or more parts which form a portion of an assembly or a

3.16 Support Equipment. “Support Equipment” is that equipment required to

Supersedes page 10 of 28 March 91 -10-

3.17 Support Items. Items subordinate to or associated with an end item,

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

-11- Supersedes page 11 of 28 March 91

e. Requiring authority’s schedule requirements.

g. Compatibility with other LSAR preparers, as well as the requiring

h. Requiring authority involvement.

Supersedes page 12 of 28 March 91 -12-

-13- Supersedes page 13 of 28 March 91

5.2.1 Reliability, availability, maintainability; failure modes, effects, and

Supersedes page 14 of 28 March 91 -14-

contractual and does not establish requirements. However, the guidance in

-17- REPRINTED WITHOUT CHANGE

Paragraph Number DID Number DID Title

5.2 DI-ILSS-81173 Logistic Support Analysis Record (LSAR)

Supersedes page 18 of 28 March 91 -18-

6.5 Supersession data. This standard includes the requirements of

-19/20 - Supersedes page 19/20 of 28 March 91

THIS PAGE INTENTIONALLY LEFT BLANK

d. Decimal Placement. Specifies the number of character positions to the

-23- Supersedes page 23 of 28 March 91