Downloaded from http://www.everyspec.

com

MIL-sTD-1456A
11 SEPTSMBER 1989
SUPERSEDING
MIL-STD-1456
25 January 1972

MILITARY STANDARD

,
CONFIGURATION MANAGEMENT PLAN

AREA CMAN
AMSC A4759
..
DISTRIBUTION STATEMENT A. Approved for public release; distribution..isunlimited.
 Downloaded from http://www.everyspec.com

MIL-STO-1456A

I DEPARTMENT OF DRFSNSE
Washington, TIC20362-5101

Configuration Management Plan

!
1. This Mill tary Standard is approved for use by all Departments and
Agenciee of the ~epartment of Defense.

2. Benef iciel comments (recommendations, edditions, deletions) and any

pertinent data which may be of use in improving this document, should be
addraased tot Commander, U.S. Army ARDEC, Al’TN: SMCAR-BAC-S, Ptcatinny
Arsenal, New Jereey 07S06-5000 by using the self-addreesed Standardization
Document Improvement Proposal (DD Form 1426) appearing at the end of this
document or by letter.

ii ●
 Downloaded from http://www.everyspec.com

MIL-sTO-1456A

FOREWORD

1. Configuration Management (CM) Plans are the means by which the Government
and the contractor are to document the details of their respective coordi-
nated CM programs. Initially, CM Plans should provide planning and
procedural Information. As the Configuration Item (CI) progresses through
the various phases of its life cycle, the content of the CM Plans should be
revised to include historic as well as updcted planning and procedural in-
formation. The CM Plan is applicable to a CI throughout its life cycle. A
CM Plan mcy address a systernconsisting of more than one CI or a group of
related CIS provided the purpose and objectives for having CM Plans can be
met.

2. The CM Plans should describe the CI and the procedures for CM applica-
tion, tailoring, tasks, participants and their roles, products, locatione,
scheduled events, related programs (e.g., reliability, maintainability,
quality assurance, Integrated Logistics Support (ILS), systems engineering,
test and evaluation programs, etc.), as well as other CM programs or
allocated and related CIS. Implementing procedures pertinent to each element
of CM should be specified as they affect the CI, its configuration identi-
fication, tbe government and industry.

3. “CM Plans should be tailored to be consistent with total program needs and
the requirements of thfs standard.

4. This standard covers CM plans for botb Hardware Configuration Items

(HCIS) and related Computer Software Configuration Items (CSCIS). Procuring
activities may elect to specify CM Plans in accordance with DI-MCCR-SOO09 for
CSCIS on programs covering Mission Critical Computer Resources (MCCR) only or
on Software Intensive Systems programs. when DI-McCR-80009 is specified for
CSCIS, CM Plans in accordance with this standard should still be applied to
non MC~. HCIS. When CM Plans conforming to both this standard and
DI-MCCR-SOO09 are required on the same contract, the plans should be closely
coordinated and should reference each other. Government CM Plans for all
HCIS and CSCIS should be in accordance with this standard

: “*
iii
 Downloaded from http://www.everyspec.com

MIL-s’TD-1456A

CONTENTS

PABAG8WH PAGE

1. SCOPE .......................................... 1

1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Applicability............................... 1
1.3 Appllcetion guidance ........................ 1
1.3.1 Nondevelopmental item. ..................... 1
1.4 Policy ........o.................o........... 1

2. REFERENCED DOCUMENTS ......i.....o............. 2

2.1 Government document . .................. ... .. 2

2.1.i Specifications, standerds and
Ixandbooks ................................. 2
2.1.2 Other Onvernment documente, drawfnge
end publications. .......................... 2
2.2 Order of precedence ......................... 2

3. DEFINITIONS
. .................................. 3“

4. GENERAL REQUIREMENTS..
........ ................ 4

4.1 Gener,el..................................... 4
4,1.1 Application, ................................ 4
4.1.2 CM plan requirement ......................... 4
4,2 Objectives .................................. 4
4*3 Implementation .............................. 4
4.4 Interface management. ....................... 4

5. DETAILED REQUIREMENTS ......................... 5

5.1 Formet ......................$.$ . . . . . . . . . . . . . 5

5.2 Contractor CM plan content .................. 5
5.2.1 Self-cover .........................o........ 5
5.2.2 Record of reviews and history ............... 5
5.2.3 Contente pege ............................... 5
5.2.4 Section 1 - Introduction .................... 6
5,2.5 Section 2 - Organization .................... 7
5.2.6 Section 3 - Beseline identificatfon ......... g
?5.2.7 Section 4 - Configuration control ........... 10
‘5.2.8 Section 5 - Interface control .............. 11
:5.2.9 Section 6 - Configuration traceability ..... 11
“5.2.1O Section 7 - “Conffguration etetue accounting.12
5.2.11 Section 8 - Confisuratlonnumegement audits. 12
5.2.12 Section 9 - Subcontractorvendor control..., 12

iv
●
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

CONTENTS - CONTINUED

5.3 Government CN plan content.................. 13

5.3.1 Self-cover .................................. 13
5.3.2 Record of reviews and history ............... 13
5.3.3 Contents page ................................ 13
5.3.4 Section 1 - Introduction .................... 13
5.3.5 Section 2 - Organization .................... 14
5.3.6 Section 3 - Baseline identification......... 15
5.3.7 Section 4 - Conf fguration control ........... 16
5.3.8 Section 5 - Interface management ............ 17
5.3.9 Section 6 - Configuration traceability...... 17
5.3.10 section 7 - Configuration status accounting. 18
5.3.11 Section S - Configuration management audits. 18
5.3.12 Section 9 - Subcontractor vendor control .... 18

6. NOTES ......................................... 19

6.1 Intended use ................................ 19

6.2 Data requirements ........................... 19
6.3 Tailoring guidance for contractual
application ................................ 19
6.4 Issue of DoDISS ............................. 19
6.5 Subject term (Key Word) listing. ............ 19
6.6 Changes from previous issue. ................ 19

Appendix A Definitions ................................... 20

:*

b
 Downloaded from http://www.everyspec.com

?iIL-sTD-1456A

1. SCOPE

@’ 1.1 Purpose. This standard establishes uniform requirements for CN

Plans. CM Plans shall encompass the description of methods and procedures
used to manage the functional and physical characteristics of a Configura-
tion Item (CI), its interfaces and identification documents. The term CI as
used herein may be hardware, firmware or other computer software (see 30.14).

1.2 Applicability. It is intended that thLs standard be used by

contractorsand Government activities to prepare CM Plans (hardwareor
hardware and software) for CIS which are designed, developed,produced or
modified for the Department of Defense (DoD).
1.3 Application guidance. This standard describes one task, the
preparation of a CM Plan. The task description shall be tailored as
appropriate to the Particular CI and its life cycle phase. In tailoring the
task, the detail and depth of the CM Plan required is de fined and incor-
porated in the appropriate contractualdocument or tasking order. This
standard shall be used for guidance only durtng Concept Exploration and
Demonstration and Validation Program Phases.

1.3.1 Nondevelopmental item (NDI) . CM Plans for NDIs shall address,

at a minimum, Comfiguration Control interchangeabil Lty and interoperability
(see 30.26).
I
1.4 Policy. “ CM Plans prepared in accordance with this standard
shall be complete and in sufficient depth to not only provide the Government
and industry with needed planning information, but also to serve as a means
● of defining epecific program CM responsibilities, procedures, and practices.

..
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

2, RSFERENCRD DOCUMENTS

2.1 Government documente. ●

2.1.1 Specifications, standards, and handbooks. The following
specifications, standards, and handbooks form a part of thie document to the
extent specified herein. Unless otherwfse epecified, the iesues of these
documents are those lieted in the issue of the Department of Defenee Index of
Specification and Standards (DODISS) and supplement thereto, cited in the
solicitation (eee 6.4).

SPECIFICATIONS

MILITARY

DOD-D-1OOO Drawing8, UngineerinS and Aeeocfated

Liste.
MIL-s-83490 Specifications, TYPEISand Forms.

STANDARDS

M2LITARY

DOD-STD-4S0 Configuration Control-Engineering

Changes, Deviations and Waivere.
MIL-STD-481 Configuration Control-l?ngineering
Changes, Deviations, and Waivers

MIL-STD-490
(Short Form).
Specification Precticea. ●
M2L-STD-961 Military Specification end Associated
Documente.
M2L-STI)-1521 Technical Revfewe and Audits for Syeteme
Equipment end Computer Programs.
DOD-STD-2167 Defense Syetem Software Development.

(Copies of apecifications, standerds, handbooks, drewings, and publications

required by contractor in connection with epecific acquisition functione
should be obteined from the contracting activity or as directed by the
contracting officer.)

2.1.2 Othar Government publication. The following other Cevernment

publication forms a part of this stendard to the extent specified herein.

Department of Defense Directive 5010.19 - DOD Configuretion

Management Program.

2.2 Order of precedence. In the event of a conflict between the

taxt of this standard and the raferences cited herein, the text of thie
etandard ehall take precedence.Nothing in this document, however, eupereedes
applicable laws and regulation unlees a specific exemption has been
obtained.

2
● ✎
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

3. DEFINITIONS

● Definitions are contained in APPENDIX A.

3
 Downloaded from http://www.everyspec.com

MIL-STO-1456A

6. GENESAL REQUIREMENTS

4.1 Generel, CM Plane ehall define the methods ueed to manage the
functional end physical characteristics of CIS, including interfecee and
identffication documente, for the full scale development end subsequent
program phases.

4.1.1 Application. The CM Plan reflecte the interpretation and

aPpliC8ti0n of the Department of Defenee Directive 5010.19 - Configuration
Management, for a given program.

4,1.2 CM plan requirement. Unless otherwise epecified, CM Plens or a

detailed outline for CM implementation ehall be prepared following the
requirement contained herein.

4.2 Ob jectivee. A GM Plan ie prepered to provide a document that

shall:

a. Eneure that all required elements of CM are applied in such

a menner tieto provide a comprehensive GM program meeting contractual
requirement.

b. Provide for identifying the means by which continuity of

effort and underetending is achieved among the various activites, primarily
between the responsible Government activity end the other .Government
Agenctee which may be reeponeible for allocated CIS, -integrating, interfacing
or otherwiaa-related CIe; contractor organizations; test and evaluation
activities; end Manegere.
●
c. Eeteblieh internal CM requirement for a total contract.

d. Serve, when approved, es a working document to plan, guide,

and meeeure the CM proceee.

4.3 Implementation. CM Plans shall be initiatedas coon as poseible

in the life cycle of the CI.

4.4 Interfece management. The criticality of maintaining interfaces

❑ ayrequire an inteneive interface management program which may be admin-
istered .geparetelyfrom the CM program. If euch e program ie requited, the
CM Plen ehall describe thet progrem, e.g. , chcrters, working groupe, etc. If
e eeperate interface management program is not required, the .CM Plan
shall detail,how the identification and control of the interfaces will be
accomplished.
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

5. DETAILED REQUIREMENTS

5.1 Format. The format of the plan shall conform to the following
outline. Optionally, sections listed may be further subdivided.

a. Self-cover

b. Record of reviews and history

c. Contente page

d. Section 1. Introduction
1.1 Description of the Configuration Item (CI)
1.2 Program Phasing and Milestones
1.3 Special Features

e. Section 2. Organization
2.1 Structure
2.1.1 Structure (CM)
2.1.2 Configuration control boards
2.2 Authority and responsibility
2.3 Policy directives
2.4 Reference documents

f. Section 3. Baseline identification

3.1 Functional baseline
3.2 Allocated baseline
3.2.1 Specifications
3.2.2 Drawings
3.3 Product baseline
.3.3.1 Specifications
3.3.2 Drawings and associated lists

g. Section 4. Configuration control

4.1 Responsibilities
4.2 Procedures

h. Section 5. Interface management

5.1 Documentalion
5.2 Interface control

i. Section 6. Configuration traceability

6.1 Nomenclature
6.2 Documentation numbering
6.3 Hardware identification
6.3.1 Documentation/hardware correlation
6.4 Software aid ffrmware identification

j. Section 7. Configuration status accounting

7.1 Data bank description
7.2 Data bank content
7.3 Reporting

k. Section S. Configuration management audits

1.. Section 9. Subcontractor/vendor control

5
 Downloaded from http://www.everyspec.com

klIL-STD-1456A

S.2 Contractor CM Plan Content. The informati.ondescribed in the

following paragraphs ehall be included in each plan as applicable.

5.2.1 Self-cover. The eelf-cover shall provide the nomenclature

of tha CI, contractor’s name, addreas and Commercial and Government Entity
(CAGE) coda I contract number, and CDRL Sequence No., contracting agency and
date of issua. l%is page ehall also contain the contractors authorizing
signature and when required, an approval/signature block for the procuring
agenty.

5.2.2 Record of reviews and history. This information shall include

the review and approval dates of plan changes.

5.2.3 Contents page. Self-explanatory.

5.2.4 gection 1 - Introduction. This section shall provide a descrip-

tion of tha materiel to which tha.plan la to be applied, the management
acquisitionphilosophy to which it la tailored, the currant stetua of the
program, and aignificant plans for the future. Special CM problems presented
by the nature of the materiel or the program shall be specified.

5.2.4.1 Paragraph 1.1 - Description of the CI. The”CI, or families

of CI.v,will be briefly deecribed in this paragraph and subparagraph as
required. Sufficient detail will ha presented to permit a basic
undaratanding of the CI and its complexity. Included will be the following:
“(Information will be provided in a manner to avoid security classification of
tha plen, if.possible,)

a. Mission/capability of each CI.

1 b. Description of each CI mission and its relationship to othar

missions and field/unit level peculiar to ite eupport equipment.

c. Supporting Miesion Critical Computer Resources (MCCR)

deacriptfon.

d. Training equipment requirements.

e. Government Furniehed Equipment (GFE). (May be apecifled in

a separate appandix if necessary.)

5.2.4.2 Paragraph 1.2 - Program phaaing and milestones. The current

atatua of the program (conceptaxploration, demonstrationand validation,
full scale development, production and deployment), at the time of
preparation or update of the plan, will be specified. A mfleetone chart
shall be included which depicts the I-34activities and their relationship to
tha major overall projact/program mileatonea. The relationship between
events critical to CM ,,andto the schedule/control of the program, e.g.,
aaquencing of dasign reviews, releaee of engineering documental ion,
production, taat program, logistic support events, audits, etc, ehall bc
apecifically defined.

6
 Downloaded from http://www.everyspec.com

MIL-STD-1456A

5.2.4.3 Paragraph 1.3 - Special features. Abnormal conditions Or

special features of the material or the management program which have a
bearing on ‘the plan, will be described, e.g., major product improvement
programs which wi 11 result in more than one configuration to be supported in
the field with more than one prodtictbaseline, depot rebuild.prOgrams
designed to reduce the clifferences among models of fielded equipment, or
major model differences in systems or weapons designed for varying
applications.Peculiaritiesof the CM program that result from participation
by a large number of organizations,or unique contractingmethods, e.g.,
preproductionevaluation,use of many commercial items, use of existing
drawings and specifications,and employmentof an integratingcontractorwill
be described here. Innovationsintended to increase the effectivenessof the
program will also be described here.
.
5.2.5 Section 2. Organization. This section shall outline the
relationahfp and integration of the contractor’s programfproject management
. to CM and describe the organizational relationship of the individuals and
activities involved in the (X program. Responsibilities shall be defined and
the policy directives that govern the program shall be listed. Procedures
shall not be included in this section.

5.2.5.1 Parasraph 2.1 - Structure. An organizational chart for the

program (or Company, or division of Company) which illustrates the structure
of program/project management shall be used. The chart, supplemented by
narrative description or flow diagrams, shall illustrate the authority/
responsibility of the key organizational elements in the company impactedby
contractualrequirementsfor CM. The integrationof CM activitieswith other
program/project activity shall also be described. This paragraph shall
specify the relationshipsamong the contractor’ssoftware CM organization,
the contractor’shardware CM organization,and the project’s hardware m
organizationwhen the software is only one element of the system being
developed.

5.2.5 .1.1 Paragraph 2.1.1 - Structure (CM). Charts supplemented by

narrative descriptions will define the relationships between activities
directly involved in the ~ program. The charts will include the
Configuration Manager, CM Office or function, interfacing organizations,
procuring and administrative contacting officers, data management, and
subcontractors to the extent employed in the program and any other elements
that may be involved.

5.2.5.1.2 Paragraph 2.1.2 - Configuration Control Boards (CCB). This

paragraph shall delineate the authority and responsibility
y of the CCB in
depth. The following shall be included:

a. Relationship of CCB to change authorization (i.e.,

Recommendation or ActIon).

b. Relationship of CCBS if there are more than one level or

separate software CCBS.

c. Membership of the CCBS.

7
 Downloaded from http://www.everyspec.com
,

MIL-sTD-1456A

5.2.5.2 Paragraph 2.2 - Authority and responsibility. Each activity

or individual shown on the organizationchart(s) shall be the aubflectof a
subparagraphwhich wi11 deteil the authority and responsibility for which CM
ia assigned. Included will be tbe CConfiguration Manager, the Contracting
●
Officar, interfece orgenizatione, and the CCB. Both authority and
rasponeibility shall be covered, and signature authority for Engineering
Changa Proposala (ECPe) and Request for Deviation/Waivers (RFD/RFWS) ehall be
specifically aeeigned.

5.2.5.3 Paragraph 2.3 - P&licY directives. All POlfCY directives

directly ralated to CM shall be listed. Theee directives ehall be
pro ject/program related directives or, if company standards, directly
traceable to a project/programdirective. If cempany standards are to be
tailored for the projectlprogramapplication, this shall be clearly defined
in a cover program directive.

5.2.5.4 Paragraph 2.4 - Reference documents. Tbie paragraph.Shall

list only those documente which are referred to in the CM Plan, with the
excaption of thosa listed in paragraph 2.3.

5.2.6 Bection 3 - Baaeline Identification. Requirements covering

preparation, aulnniaeionfor Government approval and subsequent release of the
Government-approveddocumentationwhich defines each of the required
.baaelinee shall be established in thie section. The contractor’a methods
under which the documentationwill be prepared and released shall ba
described, and the time periods in which that will bc accomplished ehall be’
indicatad.

5.2.6.1 Paragraph 3.1 - Functional baeelirie.The dOcumant@ which

establiah the functional baaeline ehall be listed in this paragraph. The
e
contractor’s plan for proposing modlf ications or expansion of those
documents shall be outlined.

If the Functional baeeline is to be prepared by the contractor, the

document format per MIL-STD-490 or MIL-STD_4B3 Appendix 111 shall be
defined. The procedure for review and release will be outlined, and tha
de8ree of Government control shall be specified.

5.2.6.2 Paragraph 3.2 - Allocated baseline. The contractor!s plan for

propoeing modifications or expenaion of existing development apecificatione
.shnll be outlined. A list of all exieting and required development speci-
fications shall be included in specification tree format and each HCI shall
be designated in accordance with the classification system of MIL-s-B3490.
Allocated baaeline documentation for CSCIa ehall be in accordance with
I)oD-sTD-2167 and ae spacifiad. A list of drawinge, ff applicable, which form
a Part of tha allocated baeeline shall also be provided. If the contractor
ia tu prepare the documente for the allocated baeeline, plana” for
preparation, review and releaea of the allocated documental ion shall be
outlined here. The technique for the application of the baseline
documentation to control the development effort ehall be apecified.

8 ●
 Downloaded from http://www.everyspec.com

MIL-STD-1456A

5.2.6 .2.1 ~s. This paragraph shall

identifY the specification per MIL-STO-490 and MIL-STD-483 that the
“a contractor shall prepare, eiisting specifications for CI, and the use of
these specifications to establish and control the allocated baseline
developed WI thin the contractor’s organization. The alignment of authority
and responsibility of the contractor and the procuring activity with respect
to establishment of the configuration identifications, and changes to the
specifications establishing the configuration identification, including clear
delineation of responsibility for cost and schedule impacts which may result,
shall be included herein. The plans shall identify knowm specifications
below prime CI level that will be prepared; e.g., critical items. The
applicabili tY of appropriate policy and appendixes of MIL-STD-490 to this
program (cantract) shall be stated. Any need for deviation of the content of
thnse appendixes deemed applicable shall be stated. Any “limitations on
delivary to, or use by, the procuring activity of contractor-prepared
specifications shall be stated. The list of specifications s~ll be prepared
in specification tree format. This paragraph shall also identify the
software documentation imposed or to be generated as part of the allocated
baseline. The type of specification/document as prescribed by OOD-STO-2167
shall be specified.

,5.2.6
.2.2 Paragraph 3.2.2.-Drawings. This paragraph shall identify
the drawings and diagrams that are a part of or shall be a part of the
alloceted baseline. A list of interface control drawings fnr both hardware
shall be delineated here or in a separate appendix. If interface control
drawings are not to be a part of the allocated baseline, a justification with
rationale must be provided (See also section 5.Interface Control). Plans for

●
preparation, review, and release shall be outlined. The technique fOr their
~~ application to control the developmenteffort shall bc specified.

5.2.6.3 Paragraph ,3.3 - Product baseline. The details of the tYPe,.

categories, forms and levels of documents to be utilized in establishing this
baseline shalI be listed. Plans for preparation, review, release and control
of the product specifications and drawings and CSCI code standarde
(DOD-STD-2167 ) shall he outlined.

5.2.6 .3.1 Paragraph 3.3.1 - Specifications. This paragraph shall

identify the hardware and software specifications which the contractor shall
prepare and the format to which they will be prepared (MIL-STD-961 or
MIL-STD-490) . Any’ limitations on procuring activity approval of content and
at what stage in the program that these shove specifications will be
available to the procuring activity shall also be identified. The
applicability Of appropriate policy and appendixes of MIL-STD-961 or
MIL-STD-490 to this program (contract) shall be stated. Any need for
leviation of the content of thoee appendixes granted for this program shall
be stated. Any limitations on delivery to, or uee by, the procuring activity
of contractor-prepared specifications shall be stated.

9
 Downloaded from http://www.everyspec.com

MIL-STD-1456A

‘-5.
2.6.3.2 Paragraph 3.3.2 - Drawings and associatedlists. This para-
graph”shall defina the drawings practices for application to tha CI, and the
OPPlicatiOn Of DOD-D-1OOO, and standards referenced therein. Any limitation
on delivery to, or use by the procuring activity, of contractor-prepared
●
drawings shall he stated. The use of interface control drawinge/interface
identification of parameter shall be addreaaed.

5.2.7 .Section4 - Configurationcontrol. Thie eection shall defi.ne

the responsibilitiesand procedures used within the contractor 1e organfzation
For control to established hardware and eoftware CI, and for proceeding
changee to these established CIS. Configuration control of the interfaces
between the procuring activities and the contractor shall be stated. This
section shall be specific in Its treetment of the subject of control of
technical interfaces both between the contractor and the procuring activity
and, when appropriate,the contractorand other contractorsinvolved in the
program. Plana for specific application of DOD-STD-480 or MIL-STO-481 shall
ba stated. .

5.2.7.1 Paregraph 4.1 - Reeponeibility for deeign release.

a. If design responsibility rests with the contractor for

pare of the’program, thie paragraph shall define the contractors authority
and responsibility. It ehall also delineate the contractor’ e internal
procedures after the Governmentassumes control. ,

b. Where tha Government aesumes design responsibility, this

EeCtiOn will outline the procedures for processing ECPS and RFD/RFWs. If
Value Engineering Deeign Release Change Proposals (VECPS) follow a different
routing or level of approval, those differences will be described. Procedures ●
and responsibilityiee for approval of deviat ione and waivere be specified,
including those involving a Materiel Review Board (MRB).and reporting of
daviatione and waivers into the,etatue accounting system.

5.2.7.2 Paragraph 4.2 - Procedures. This paragraph shall addrees:

a. A separate chart shall be prepared for the proceedingof

I
contractor changee if change authority reste with the contractor for a period
of time. Copies of the contractorsfonus as exhibfte shall be included along
with tbe narrative for the chart.

b. The proceeding of “ECPe”,VECPe, RFD/RFWs (to include all

claesee, priorities end types) and Software Trouble Reports (STRS) will .be
described in chart form, supported by narrative as required. .Information
shall be included for each elawent involved from the original proposer through
tha contracting officer responsible for the contractual inplementin8 action.

c. Procedure for ensuring implementatfon of approved changee

into production, repair parta, retrofit and technicelpublicationsprograms
and feedbacka to the procuringactivity shall be described.

10
a
 Downloaded from http://www.everyspec.com

MIL-STD-1456A

d. If during the program (contract), different requirements for

processing changes are necessary, those requirements shall be clearly defined
● by separate charts supported by narrative.

e. The inputs to the status accounting system will be clearly

defined and keyed to the change process. Capabilitiesfor the monitoring of
changes shall be described in detail.

5.2.S Paragraph 5.2 - Interface Control. This parasraph ehall

delineate the authority, responsibilities and procedures for releasing and
revising the Interface Control Documents and all aspects of the interface
program, e.g. , GYE/GFP, Governmentfcontractor, contractorfcontractor.

5.2.9 Section 6 - Configuration traceability. Tbis section shall

describa the plan for establishing the methods to be used for +dentifyfng
documents and physical items in order to achieve configuration traceability
, from reauirementa to eauirnnent,subassemblies, pfecc-parts, facility sites
and spares, and the proper relationship between engineering/manufacturing
deta and manufactured CIS o Identification of software shall be addressed and
include the following:

a. Locatfons or plan for the development of a software support

library.

b. Reconciling deliverable software to its approved

documentation.

●
c. Assuring that the software, descriptive documentation,,and
program materials are properly identified.

5.2.9.1 Paragraph 6.1 - Nomenclature. This paragraph shall address

the procese of nomenclature assignment and the requirement for titling
specifications and drawings.

5.2.9.2 Paragraph 6.2 Documentalion numberin~ If tbe procuring

activity has specified requirements (assignment of numbers) for documents,
those requirements shall be stated here. If contractor numbers are to bc
used, this paragraph shall delineate in detail the numbering syetem to be used
for drawings and specifications.

5.2.9.3 Paragraph 6.3 - Hardware identification. The contractor shall

identify the plan and ,procedures for part identification, serializatiorb and
lotting including tbe criteria to be used for part reidentification. The
paragraph shall list the criteria used in applying serial numbers and lot
numbers and shall identify, where possible by document number, the items that
shall be subjected to eerial/lot control.

5.2.9.3.1 Paragraph 6.3.1 - Documentation/hardware correlation’. This

paragraph shall present the contractor~s plans and identify the procedures,
and capability of generating and maintaining a record which describes the
relationship between ,the “as designed,” “as built,” and “as modified”
configurations.

11
 Downloaded from http://www.everyspec.com

?41L-STD-1456A

‘“””””
5.2.9.4 Paragraph 6.4 - ,Software and firmware identification. This
paragraph shall delineate the contractor’a plana and identify the procedure,
and methods for identification of software and firmware including correlation
to its documentation. Plans for reconciling the eoftware status reports and
the status of the eoftwara, descriptive documentation, and program ntcteriale
wf th the approvad baselines and its approved changes ehall be addresaed.

5.2.10 Section 7 - Configurationstatue accounting. Contractors shall

state thair plans for statua accounting for this program (contract).This
eection shall also outline plans for collecting,storing, handling,
verifying, validating and preeenting of configuration status information to
management. Technique to be applied to provide an information system
responsive to cuetower and internal needa ehall be epecified. The content
and format of pariodic summary reporte to reflect 8tatue of ECJ?S,RFD/RFWa
and STRa, etc., as appropriate, shall ale.obe delineated.

5.2.10.1 Paragraph 7.1 - Data bank description. Plans for

astabliahment of the configuration etatus accounting date bank shall be
daacribad in this paragraph. The plan muet”indicata whether the data bank
will be manual or autamated, and how inputs.and outputs of participating
(Subcontractora /Government) activities will be handled.

5.2.10.2 Paragraph 7.2 - Data bank content. The type of information

that will be stored:in the data bank shall ba indicated in this paragraph,
with a short description of the eourcee, and the technique by which the
information will be incorporated. Means must ba provided for collecting data
on documentation release and revieion, on deliverable -tools, inspection, teet
equipment and repair parte affected by changes, on publication etatus, and on
implementation of changes to hardware in production and in the field (to
include eoftware and firmware, as applicable).

5.2.10.3 Paragraph 7.3 - ReportIn&. The methods by which

information will ba nraaanted to management will hc indicated here. Both
inquiry capability aid periodic miles tone reporting will be covered.
(Under moat circumatancas, emphaeie ehould be placed on the ability of the
ayatam to produce conciee anawera tn epacific inquiriee by management
elamenta; bulky pariodic reports should ha minimized. ) The plan must
indicate the type of data that will be evailable on call, as well ae the
purpoea for which it is intended. Planned periodic reports will ha listed.

5.2.11 gectionfl - Configuration management audits. This section shall

deecribe (a) .plana, procedures,.and documentation, for the Functional and
Physical Configuration Audits in accordance with MIL-sTD-1521 and (b) the
format and reporting results of in-proceea configuration audits.

5.2.12 SectInn 9 - Subcontractor/vendorcontrol. Tbe contractor ehall

indicata hiarproposedmethods for control over subcontractorsand ,vendors,
insofar aa it impacts on hia CM conunitmantsto the procuring activity. The
mathode used to detemnine their capability and monitor their ability to
support the requirementa of CM ehall be explained.

12
●
 Downloaded from http://www.everyspec.com

?4tL-sTTI-1456A

5.3 Government CM Plan content. The information described in the

following paragraphs shall” be included in each plan as applicable.

5.3.1 Self-cover sheet. The self-cover sheet shall provide the

nomenclature of the System or CI; preparing and approving Government
Activit y‘s organization and signature, and date of signature(s).

5.3.2 Record of reviews and history. This page shall show dates of
reviews and approvals of plan changes. .

5.3.3 Contents page. Self-explanatory ~,

5.3.4 Section 1 - Introduction. This section shall provide a

describtlon of the materiel to which the plan is to be applied, the
management/acquisition philosophy to which it is tailored, the current status
of the program, and significant plans for the future. Special CM problem
presented by the nature of the nwteriel, or the program shall be specified.

5.3.4.1 Paragraph 1.1 - Description of the CI. The CI, or families of

CIS, shall be briefly described in this paragraph and subparagraphs as
required. Sufficient detail shall be presented to permit a basic
understanding of the CI and fts complexity. Included shall be the following:
(Information shall be provided in a manner that will preclude security
classification of the plan, if possible.)

a. Mission/capability of the CI.

● the CI. b“ Description of each prime item showing its relationship to

c. Supporting software description.

d. Training equtpment requirements.

e. Government Furnished Equipment/Property. (May be specified

in a separate appendix if necessary. )

f. Description of the software capability as related to mission

and to.each prime item within the CI.

5.3.4.2 Paragraph 1.2 - Program phasing and milestones. ‘f.he current

status of the program (concept exploration, demonstrate
ion and validation,
full scale engineering development,,production and deplO~ent) at the time Of
preparation or update of the plan, will be specified. A mi let?tonechart
shall be included which depicts the (34activities and their relationship to
the major overall project/program milestones. The relationship betwean
events critical to Q4 and to the schedule/control of the program, e.g.,
sequencing of design reviews, release of engineering documentalion,
production, test programs, logistic support events, audits, etc., shall be
specifically defined.

13
 Downloaded from http://www.everyspec.com

MIL-STD-1456A

5.3.4.3 Paragraph 1.3 Special featurea. Abnormal conditions or

special features of tha material or the management program which have bearing
on tha plan will be deecribed, e.g., mejor product improvementprograms which
will raeult in more than one configuration to ba supportad in the field with
more than one product baeeline, depot rebuild programs designed to reduce the
differences among modala of field equipment, major model differences in
systems or weapons dasigned for varying applications. Peculiarities of tha
CM program that result from participation by a large number of organization,
uriiqua contracting methode, a.g., praproduction eveluation; use of many
commercial iteme, uae of exieting drawings and speclfications, and employment
of an intagratfng contractor, shall be described hera, Innovation intanded
to incraase the effectiveneee of the program ehall alao be describad here.

5.3.5 Section 2 - Organization. Thie eection ehall outline the

relntionahip end integration of tba Government ia program/project management
to CM and :describe the organizational ralationsbiu of the Dositions and
activities involvad in the CM program. Responaibilitiea shall be defined and .
-the policy directivee that govern the program shall ba Iieted. Procedures
shall not ha included in this section.

5.3.5.1 “Paragraph2.1 - Structure. A organizationalchart which

illustrates tha structure of programfprojactmanagement shall be ueed. The
chart, supplemented by narrative description or flow diagrams, shall
illue crate tha authority/responsibility of tha key organizational elements
:impacted by CM requirements. The integration of CM activities with other
program/project activity ehall alao be deacrfbed.

.5.3.5.1.1 Paragraph 2.1.1 - Structure (CM). charts, supplamantadby

narrative descriptions,shall define the relationshipsof activities Involved a
in the program. The charte ehall Sncluda tha configuration manager, CM
office or function, interfacing organization, procuring and administrateive
contracting.officare, CCB and contractors to the extent employed in the
progrnma, and any other elements that are involved.

5.3.5.1.2 Paragraph 2.1,2 Configuration Control Board (CCB). ‘fbie

paragraph shall dalineate the operation of the CCB. Tha following shall be
:includedt

a. Ralat ionahip of CCB to change autborization (e.g.,

Racommandation or Action),

b. Ralationehip of CCBS if there are more than one level or

eeparata software CCBa.

c. Membership of the Cf.2BS.

d. Activation (effective time or event at which the CCB

becomes or waa made operational).

-,
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

● 5.3.5.2 Paragraph 2:2 - Authority and responsibility. Each actiVitY

or individual shown on the organization chart(s) shall be the subject of a
subparagraph which wi 11 detai 1 the authority and responsibllity for which CM
is assigned. Among those included will be the Conf igiration Manager, the
Centratting ‘officer, interface organizations, and the cm. Both authority
and responsibility shall be covered, and signature authority for ECP’s and
RFO/RPWS shall be specifically assigned.,

5.3.5.3 Paragraph 2.3 - Policy directives. All POliCY directives

(e.g., SOPS , office instructions) directly related to configuration
management, except those published by higher authority, shall be listed and
copies shell be appended to the configuration management plan.

5.3.5.4 Paragraph 2.4 - Reference documente. This paragraph shall

list all documents which are referred to In the CM Plan except those listed
in para 2.3.

5.3.6 Section 3 - Baseline identification. ‘fhlssection shall identify

and conta Ln ulans for development of the documentalIon that will define each
of the requl~ed baselines. Contractual or in-house programs under which the
documentationwill be prepared and released shall bc described.

5.3.6.1 Paragraph 3.1 - Functional baseline. The dOc~ment Or

documents which establish the functional baseline shall be listed in this
uaragrauh. The urocedure for review and release must bc outlined, and the
degr~e if Govertient control must be spec lfied.

● 5.3.6.2 Paragraph 3.2 - Allocated baseline. ‘L’he doc~efits which

establish the allocated baseline shall be listed. Plans for preP~ratiOn,
review, ahd release of the alloccted documentalion must be.outlined. The
technique for their application to centrol the development effort (e .e.,
contractual provisions, in-house procedures, etc.), must b epecified.

5.3.6.2.1 Paragraph 3.2.1 - Specifications. This paragraph shall

talent
ify the specifications (MIL-STO-490, Type B) that wi 11 be prepared,
existing specificattons, and the use of these specification to establish and
control the Allocated Baseline. Any known support documentation, (e.g.,
handbooks, user manuals, test plans) that is iequired shall be identified.

5.3.6 .2.2 Paragraph 3.2.2 - Drawings. This paragraph shall identify

the drawings and diagrams that are a part of or will be a part of the
allocated bcseline. A list of interface control drawings for both hardware
and software shall bc delineated here. Plans for preparation, review, and
release shall bc outlined. ,

5.3.6.3 Paragraph 3.3 - Product baseline. The details Of the tYPe,

categories and forms of documents to be utilized in establishing this
baseline shall be listed. Plans for preparation, review, release and control
of the product specifications and drawings must be outIined.

5.3.6 .3.1 Paragraph 3.3.1 - Specifications. This paragraph shall

identify the hardware and software specifications (MIL-sTD-961 or
MIL-sTD-490 ) that will be prepared, and any existfng sP’ecificatiOne.
a

15

.
 Downloaded from http://www.everyspec.com

Mm-pm-l 456A

5.3.6 .3.2 Paragraph 3.3.2 Drawings and associated llsts. This

paragraph shall define the drawing practices for application to the CI, and
the application of DOTI-D-1OOO,and etandarda referenced therein. The use of
interface conttol drawings/interface identification of parameters shall be
addreased. This paragraph shall aleo specify in detail all software related
drawings, including interface with hardware, which are required for the
product baaeline.

5.3.7 Section 4 - Configuration control. Thie section shall define the

re.eponeibilitiesand procedures used wt thtn the procuring activity’s organi-
zation for control .to the hardware and software CI end for processing changes
to theee CIa. This section shall be specific as it treata the subject of
Interface within fbetween Government agencies and Government egencieaf
contractor. Plana for specific application of DoD-sTD-480 or )41L-STD-481
ehall be etated.

5.3.7.1 Paragraph 4.1 - Responsibilities. This paragraph shall

addrees ~
e

a. Level and dagree of configuration control to be applied.

b. Conf i.gurat
ion control process and partlc ipants. ,

c. Configuration control Board (CCB) charter, including

aeprOval/diaapprOvel authOrity, members and their responsibilities, limits of
CCllauthority, and requirements for coordinating/interfacing with other CCBs.

d. Uae and euthority 6f Materiel Review Boards.

5.3.7.2 Paragraph 4.2 - Procedures. This paragraph shall address:

e. Approval/disapprovalproceae end procedures for Engineering

Change Proposale (ECPa), Value Engineering Change Propoaala (VECPS) and
requeata for Deviation (RPDa) and Waivera (RPWa).

b. Process end procedure for changing the CI and ite

configuration identification documents after the BCP/VSCP/RFD/RPW ia approved,
including provisioning, spares, test, training end operational items. Also,
include the engineering release syetama shall be included.,

c. Procaas and procedures for ensuring that the approved

ECP/RFD/RFW ie incorporated on schadule end that :the incorporated change
satisfiee ita intended purpose.

d. Procedures covering WRB activity.

e. Special criteria for uae of preliminary RCPS /VBCPs.

f. Claaa 11 ECP.processing procedura.

.
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

g. When required, provisions for maintaining a library of

● ECPs/VECPs /SYDs/RPWs, including location, custodian, length of time to retain

,n an active file statua, and turnover or archiva requirements. Also ,
includes requirements for manual or automated data processing of these
documents.

h. Process and procedures for fncorporating approved

ECPa/VECPs/RYDa/RFWs in follOw-On cO~tract requ~rementa.

S.3.8 Section 5 - Interface management. This section shall describe

the documentation and control of all physical and functional interfaces of
systems, equipment, software, facilities and Installation requiremente.

. 5.3.8.1 Paragraph 5.1 - Documentation. l%is paragraph shall s:~ify

the documentation to be generated as part of the interface program.
documents shall be Iistealby type, e.g., drawinga and specifications with
. titles and dates. Also plans to identify interface parameters on the
production documentation shall be specified.

5.3.8.2 Paragraph 5.2 - Interface control. This paragraph shall

delineate the authority,responsibilities,and procedures for releasing and
revising the interface control documents. Also all aspects of the interface
program, e.g., GFEIGPP, Government/contractor, cOntractOrlcontrnctor ShFIllbe
addressed.

5.3.9 Section 6 - .Configuration traceability. This sectiOn shcll

describe the methods to be used for Identifying docomenti and physical items

● in order to achieve configuration traceability for equipment, subassemblies,

p iece-parts, facility sites, and spares and the proper relationship between
engineering/manufacturing CIS. Identification of software shall be addressed
and the following shall be included:

a. Location or plan for development of a software support

library.

b. Reconciling deliverable software to its approved

documentation.

c. Assuring that the software, descriptive documentalion, and’

program materials are properly identified.

5.-3.9.1 Paragraph 6.1 - Nomenclature. ‘PMs paragraph Shall address

the process for official nomenclature assignment and the requirements for
titling of specifications and drawings.

5.3.9.2 Paragraph 6.2 - Documentalion numbering. This paragraph shall

address the numbering system to be used for documentalion.

5.3.9.3 Paragraph 6.3 - Ifardware identification. l?hisparagraph shall

delineate the requirements, where known, for part identificatIon, Iotting, or
serialization.

17
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

5.3.9.3.1 Paragraph 6.3.1 - Documentation/hardwarecorrelatIon. This

paragraph ahal.1delineate the Government’srequirementsfor generatingand
maintaining tha records for “as designed,” “as built,” and “aS mOdified”
configura’tiona.
●
5.3.9.4 Paragraph 6.4 - Software and firmware identification. ‘fhis
paragraph shall specify the methnde to be uaad in the ident ificatton of
firmwara and software.

5.3.10 Section 7 - Configurationstatus accounting. This section shall

outlina plans for collecting, storing, handling, verifying, validating and
presenting of configuration statue information to management. Technlquea tO J
ba epplied to provide an information system responsive to the needs of the
entire managamant team will be atated.

5.3.10.1 Paragraph 7.1 - Data bank description. plana fOr

establishment of the configuration status accounting data bank shall be
daacribed in this paragraph. The plan must indicate whether the data bank
will be manual or automated, whether it will be located at a contractor!s
plant or at an in-house site, and how inputs and outputs of participating
activities.will be hendled.

5.3.10.2 Paragraph 7.2 - Data bank cOfitent. The iflfo~ation that will
be atorad in the data bank ehall be indicated in this paragraph, with a short
daacription of the sources. Means must ba provided for collecting data on
documentation ralenae and revieion, on coets of changea, tools, inspection,
teet equipment and repair parte affacted by changee, on publication status;
and on implementation of changee to software/firmware and hardware in
,production and in the fteld. ●
5.3.10.3 Paragraph 7.3 - Reporting. The methods by which information
will be preeented to management shall be indicated here. Both on-line
inquiry capability and periodic milestone reporting shall be covered.

5.3.11 Saction 8 - Configuration management audits. Tbia section

shall deacriba plana, procedure, and documentation for the functional
and physical configuration audits in accordance with MIL-STD-1521 and the
in-process configuration aydite and technical reviews. All items required by
MIL-STD-1521 shall be addresaed here.

5.3.12 Section 9 - gubcontractorivendor control. The procuring

activity shall deacriba tba methods to ba ueed in establishing requirements
and assuring subcontractor/vendor compliance with configuration management
requirements.

.lB
 Downloaded from http://www.everyspec.com

MIL-STD-1456A

6. NOTES

● 6.1 Intended use. CM Plans conforming to the requirements of this

standard are intended to provide the detailed means by which the requirements
of the DOD Directive 5010.19 are implementedfor a CI. The CM Plan provides
in one document all policies, procedures, organizational descriptions, and
scheduled evente relating to cu. The application of CM principles can be
monitored through this plan.

6.2 Data Requirements. The following Data Item Descriptions (DIDs)

must be listed, as applicable, on the Contract Data Requirement List (DD Form
1423) when this Standard is applied on a contract, in order to obtain the
data, except where DoD FAR Supplement 27.475-1 exempts the requirement for a
. DD Form 1423.

Reference DID DID

s Paragraph Number Title

4.1.2, 5.2 DI-CMAN-80858 Configuration

Management Plan

The above DIDs were those cleared as of the date of this standard. The
current issue of DOD 501O.12-L, Acquisition Management Systems and Data
Requirements Control List (AMSDL), must be researched to ensure that only
current, cleared DIDs are cited on the DD 1423.

6.3 Tailoring guidance for contractual application.

● See Paragraph 1.3.

6.4 Issue of DODISS. When this standard is used in acquisition, the

applicable issue of the DODISS must be cited in the solicitation (see 2.1.1
and 2.2).

6.5 Subject term (key word) listing

Baseline
Configuration
ConfiSurstion audits
Configuration baselines
Configuration control
Configuration identification
Configuration item
Configuration management
Configuration status
Management plan

6.6 Changes from previous issue. Vertical lines or asterisks are

not used In this revision to identify changes with respect to tha previous
1ssue due to the extensiveness of the changes.

19
 Downloaded from http://www.everyspec.com

MIL-STD-1456A

Custodians Prepating activity

I Army - AR Army - AR
Navy - EC
Air Force - 19
DLA - DH
NSA - NS

Review activities
Army - AT, AV; ER, MI
Navy - AS, MC, S% OM, OS, SA, ’20,YD
Air Force -,1, 10, 20

Uaar activitiasl
Army - GL, MS .
Navy - SH
Air Force - 11, 13, 14, 17, 18

(Projact CMAN-0002)

20
 Downloaded from http://www.everyspec.com

MIL-sTD-1456A

APPENDIX A

DEFINITIONS

10. sCOPE

10.1 w. This appendix provides definition of those key terms in

this standard which require specific definitions for use in conjunction with
this document.

20. SSFSSENCEDDOCOMENTS

Not applicable.

30. DEFINITIONS

t 30.1 Acquisition cycle. That part of the life-cycle of a

configuration item for which acquisition is in process. The acquisition
cycle consists of a series of milestone decisions and acquisition phases.

30.2 Baseline. A configuration identification document or a set of

such documents formally designated by the Government at a specific time
during a CIS life cycle. Baselines, plus approved changes from those
baselines, constitute the current configuration identification. For CM there
are three baselines, which are established sequentially. as fOllOws:

a. Functional baseline. The initially approved documentation

describing a system or item’s functional characteristics and the verification
tests required to demonstrate the achievement of those specified functIonal
characteristics.

i b. Allocated baseline. The initially approved documentation

describing an itcm’s interface characteristics that are alloceted from those
of the higher level CI or those to a lower level, interface requirements with
interfacing configuration itcme, additional deeign constraints end the
verification tests required to demonstrate the achievement of those specified
functional and interface characteristics.

c. Product baeeline. The initielly epproved documentation

describing all the necessary physical and functional characteristics of
the CI, including manufacturing processee and procedures, materials, any
required joint and combined operations interoperability characteristics of a
CI (including a complete summary of other Service and allied interfacing CIS
or systermsend equipments); the eelected physical chsracteristics designated
for production acceptance testing and tests neceesary for production and
support of the CI.

21

lL-
 Downloaded from http://www.everyspec.com

MIL-sTIh1456A

30.3 Computet date baees. A collection of data in a form capable of

being processed and operated on by a computer.

30.4 Computer firmware. An aasembly compoeed of a hardware unit and

a computer program integration to form a functional entity whose
configurdtion cannot he easily altered during normel operation.

30.5 Computer program. A series of instructions or statement in a

form acceptable to a computer, deetgned to cause the cmaputer to execute an
operation.

30.6 Computer software. A combination of aeeoctated compster

instructions and cemputer data definitions required to enable the ccmputer
.
hardware to parform computational or control functione.

1 30.7 Computer software documentation. Technical data, including

computer listings and printoute, in human readable form which documents
the design or datails of computer software, explains the capabilities of
.

tha software, or provides operating instructions for ueing the software

I to obtain desirad reeults from a computer.

30.8 Concept exploration phase. That part of the acquisition

life-cycle when alternative concepts are explored and evaluatad.

30.9 Configuration. The functional and/or phyeical characteristics

of hardware[firmware end other software as set forth in technical
documentation and achieved in a product.

30.10 Configuration audits. The verfficatfon of the CIS conformance ●

to specifications end other contract requirements.

a. Functional Configuration Audit (FCA). The formal

examination of ~unctionel characteristic of a CI, prior to acceptance, to
verify that the item has achieved the performance specified in its functional
and/,orallocated configuration identification.

b. ~. The formal examination

of the “ae-built” configuratien of e r,21
against its technical documentalion
to aatablish the CIa initial product configuration identification (PCI).

30.11 C~. The systematic proposal, justification,

evaluation, coordination, approval or disapproval of propoe$d changeg, and
implementation of all approved changee in the configuration of a CI after
formal establishment of the baseline.

30.12 ~. A board cnmpoeed of

technical and adminietrative representatives who approve or disapprove
propoeed enginaeriug changes to an approvad baaeline.

“o
22
 Downloaded from http://www.everyspec.com
I

MIL-STO-1456A

30.13 Configuration identification. The selection of the documents

which will comDrise the baselines for the svstans and CIS involved, the
t
documents them~elves, the information in th~ documents, and the nurnhersand
other identifiers affixed to the items and documents. Tbe documents identify
and define the item’s functional and physical characteristics in the form of
specifications, drawings, associated lists, logic,diagrams, flow charts,
interface control documents, evaluation plans, and documents referenced
therein. The configuration identification is developed and nraintainad
I through three separate, evolutionary, increasing levels of detail, each used
1 for establishing a specific baseline. The three levels of configuration
tdentification are as follows:
I
a. Functional Configuration Identification (FCI). The
approved functional baseline plus approved changea.
~
b. Allocated Configuration Identification (AcI). The apprnved
) allocated baseline Plus approved changes.
I c. Product Cnnfiguration Identification (PCI). The approved
1 product baseline plus approved changes.

30.14 Configuration Item (CI). An aggregation of hardware, firmware,

or other canputer software or any of their dfscrete portions, which satiafiea
an end use fnnction and is designated by the Government for separate CM. CIS
may vary widely in complexity, size, and type, from an aircraft, electronic,
or ship system to a test meter or round of ammunition. During development
and mamuf acture of the initial (prototype) production configuration, CIS are
those items whose performance parameters and physical characters tics must be
separately specified defined, and controlled to provide management insight
I
needed to achieve the overall end uee function and performance. Any item
I required for logistic support and designated for separate procurement is’a
CI.
I 30.15 Configuration Management (CM). A discipline applying technical
I and administrative direction and surveiIlance for the following purposes:
,
a. Identify ad document the functional and physical
I characteristics of a CI.

b. Control changes ro the CI and its documentation.

c. Record and report change processing and implementation

status.

30.16 Configuration Status Accounting (CSA) . The recording and

reporting of information that is needed to manage configuration
effectively, including a listing of the approved configuration
identificatibn, the status of proposed changes, deviations and waivers to
configuration, and the implementation at8tua of approved changes.

; *

I 23
I
 Downloaded from http://www.everyspec.com

MlL-STD-l456A

,,30.17 Deviation. A specific written authorization,granted prior to

the manufacture of an item, to depart ‘from’
a’particular perfonnanca or design
requirement of a speeificatl~, drawing ‘or othar document for a specific -.. e
number of!unite or a specific period of time. A deviation differs from tin
engineering change in that en approved engineering change orequires
corraeponding revitiionof the documentation defining tha effected item,
whereas a deviation does not contemplate :teviaion of the applicable
specification or drawing. (DOD-STO-480) , “
,.
.30.18 .E~fact~vit~ A method of specifying items on”which
configurationidentificatfon ia”applicable. Effectivity of confIguration
identification ia expressed In te~s of the serial number’, lnt ~urnbar,
raviaion, vareion, module, etc., of the configuration item to which the
,, .
configuration identification appliea. ,
,, ,,,.
.
so. 19 Bwinaarins change. An alteratfon in the configtwation of a .
configuration itam or item daliverad, to ba delivered, or under development,
after formel establishment of ita configuretion fdentificetiOn.
(DOD-STD-480)

30. 21) Engineering Change.Propoeal (?ICP). A ‘termwhich includes Mth

a proposed engineering change and the documentation by which the change is
described and :suggeated. (DOD-STD-4SO)

30.20. I m class.’ (see DoD-sTD480).’

30.20.2 ..ECPType,
.,. .
o
a. Preliminary ECP (Typa P). A type P ECP ‘may be submitted to”
the Government, for reviaw prior to.tbe ava+ lability of the informatir.n
necassary. to support a formal ~ce. (DOD-STD4s0 )

b. Formal ECP (Type P). A type F ECP provides engineering

information and other data in sufficient detail to support formal change
aPPrOval end contractual authorization,end which may follow the submittal of
a preliminary ECP or VECP. (DOD-S~-480)

30.21 Integretad Logistic Support “(ILS). A compaaite of the

elemante necessary to ensure the effective and economical support of a s.ysbe’m
Ot equipment. at .+1 levels of mctntenance for its programmed, life cycle. Tha
e lernantainclude all resources necessary to maintain and operate an equipment
or weapons system, and are categorized as.followe t (a) planned maintenance,
“(b) losiatic eupport personnel, (c) technical logistic data and information,
(d) support equipment, (e) epares and repair parts, (f) facilities,and‘(g)
contrac~ maintenance. (DoD-STO-480),

30.22 ‘Interface. The epecifIcally dafined physical or functional ~”

junctufa betwaan two or more conf$uration itams.

30.23 Interface a.qreement. A document thet describes’ the mutually

nEreeable CM practices and procedures for a given systam or CI when more than
one agency is designated dasign r.r%ponsibi
lity to perform management
functione for items that interface with tha configuration item.
*

24
 Downloaded from http://www.everyspec.com

~“-sTD-1456A

30.24 Interface control. The delineation of the procedures and

documentation. botb administrative and technical, necessary for
● f.tffi..tf.~ ..d management of f“nctiona~and physical characteristics
tween two or more syeteas or CIS.

30.25 Life-cycle. The life span of a system or CI. The life-cycle

begins with tbs documenting of the mission elsment needs statsment or
equivalent, followsd by the acquisition cycle, the operations and support
phase, and is rejuvenated by a modernization program or ends with the
disposal of the item. Configuration management continuee for as long ae the
configuration identification of the item is maintained.

30.26 Nondevelopmental item. A procured or procurable item that is or

will be available on the commercial market place requiring only minor
c
mod ification in order to resetthe requirements of the contracting activity.

30.27 Spares and repair parts. Spares are components or assemblies

●
used for maintenance replacement purposes in major end items of equipment.
Repair parts are those “bits and pieces,” e.g., individual parts Or
nonreparable assemblies required for the repair of spares or major end
items. (DOD-STD-480)

30.28 Specification. A document intended primarily for use in

procurement which clearly and accurately describes the essential technical
requirements for items, materials or services including the procedures by
which it will be determined that the requirements have been met.
(DOD-STD-480)

● 30.29 Specification Change Notice (SCN). A document used to

propose, transmit and record changes to a specification. In proposed form,
prior to approval, the SCN (P) supplies proposed changes in the text of each
page affected.

30.31 Support Equipment (SE). That equipment required to maintain an

item, systsm, or facility in its operational status, including computer
programs related thereto.

30.32 System. A composite of subsystems, assemblies (or sets),

skills, and techniques capable of performing and/or supporting an operational
or nonoperational role. A complete system includes related facilities,
itsms, material, servi’ces,and personnel required for its operation to tbe
degree that it can be considered a self-sufficient item in its intended
operstiotialor nonoperational andfor support environment. (DoD-S’IW480)

30.33 Tailorin~ The process by which specific requirements

(sections, paragraphs, or sentences) of the selected specifications,
stsndards, and related documents are evaluated to determine the extent to
which each requirementis most suitable for a specificmaterial acquisition
and the modificationof these requirements,where necessary,to ensure that
each tailored document invoked states only the minimum needs of the
Government (DOD 4120.3-M).

25
 Downloaded from http://www.everyspec.com

30.34 Technical reviews. ~A series of system engineeringactivities

by which the technical progress on a project IS aesessed relative to its
technical andfor coatractuel requirements. The reviews are conductedat
logical transition points in tha developmenteffort to identify and correct
problems raaulting from the work completed thus far before the problems can
disrupt or delay the techncial progress. The reviews provide a method for
tha contractor end Government to determine that the development of a CI and
ita idantificatlon have met contract milestone requirements (MIL-STD-1521).

30.35 Total program needs. A genetal term used for the life-cycle
1“ , raquiramenta and considerations given to the development, production, {
oparationa, and support of e CI. Total progi%m naada include, but are not
limited to quality aaaurance, reliability, maintainability, producibility,
teat and evaluation, acceptance, epproval for production, integrated logistic ‘
aupporc, personnel, training, aveilability, interoperability,
interchangaabili ty, transportability, survivability, nuclear biolOgic=l “end ~
chamical hardening, operational readiness, aecurity, eafety, schedulee,
competitive reprocurament, and total life-cycle costs.

30.36 Waiver. A written euthorization to accept a configuration item

I or othar designated ftams, whfch, during production or after having been
submitted for inspection, are found to depart from specified requirements,
but nevertheless are considered suitable for use “as is” or after repair by
an approved method. (DOD-STD-4SO)
I

e
26