Advance Change Study Notice (ACSN). A document which may be used, instead
of a preliminary Engineering Change Proposal (DD Form 1692), to identify an
idea or problem in order to obtain authorization to submit a formal routine
Engineering Change Proposal.
Allocated Baseline (ABL). The initially approved documentation describing
an item's functional, interoperability, and interface characteristics that are
allocated from those of a system or a higher level configuration item, interface
requirements with interfacing configuration items, additional design
constraints, and the verification required to demonstrate the achievement of
those specified characteristics.
Allocated Configuration Documentation
(ACD). The approved allocated
baseline plus approved changes.
Approval/contractual implementation. The acceptance by the Government of
a document as complete and suitable for its intended use. Approval/contractual
implementation of configuration documentation means that the approved
documentation is subject to the Government's configuration control procedures.
Block change concept. For hardware configuration items, an engineering
change implementation concept that designates a number (i.e., a block) of
consecutive production units of the configuration item to have an identical
configuration on delivery and in operation. (Using this concept, the production
run is divided into "blocks" of units. The production line incorporation point
for a proposed ECP is delayed to coincide with the first unit of the next block,
or retrofit is required at least for all already-delivered units of the current
block.) For computer software configuration items, once the product baseline has
been established, the concept requires the accumulation and the simultaneous
implementation of a number of routine software changes to minimize the number of
interim versions and related documentation.
Classification of defects. See MIL-STD-109.
Commercial and Government Entity (CAGE)
Code . A five position
alphanumeric code with a numeric in the first and last positions (e.g., 27340,
2A345, 2AA45, 2AAA5), assigned to United States and Canadian organizations which
manufacture and/or control the design of items supplied to a Government Military
or Civil Agency or assigned to United States and foreign organizations,
primarily for identifying contractors in the mechanical interchange of data
required by MILSCAP and the Service/Agency Automated Data Processing (ADP)
systems. The CAGE data provides the data base for the Cataloging Handbook H4/H8
Computer data base. A collection of data in a form capable of being
processed by a computer.
Computer data definition. See DoD-STD-2167.
Computer software. See DoD-STD-2167.
Computer Software Component (CSC).
Computer Software Configuration Item
(CSCI). A configuration item that
is computer software.
Computer software documentation. Technical data or information,
including computer listings, regardless of media, which documents the
requirements, design, or details of computer software explains the capabilities
and limitations of the software; or provides operating instructions for using or
supporting computer software during the software's operational life cycle.
Computer Software Unit (CSU). See DoD-STD-2167.
Configuration. For purposes of this standard, the functional and
physical characteristics of existing or planned hardware, firmware, software or
a combination thereof as set forth in technical documentation and ultimately
achieved in a product.
Configuration audit. See "Functional configuration audit" and "Physical
Configuration baseline. Configuration documentation formally designated
by the Government at a specific time during a CI's life cycle. Configuration
baselines, plus approved changes from those baselines, constitute the current
approved configuration documentation. There are three formally designated
configuration baselines in the life cycle of a configuration item, namely the
functional, allocated, and product baselines.
Configuration control. The systematic proposal, Justification,
evaluation, coordination, approval or disapproval of proposed changes, and the
implementation of all approved changes, in the configuration of a CI after
establishment of the configuration baseline(s) for the CI.
Configuration Control Board (CCB). A board composed of technical and
administrative representatives who recommend approval or disapproval of proposed
engineering changes to a CI's current approved configuration documentation. The
board also recommends approval or disapproval of proposed waivers and deviations
from a CI's current approved configuration documentation.
Configuration documentation. The technical documentation that identifies
and defines the item's functional and physical characteristics. The
configuration documentation is developed, approved, and maintained through three
distinct evolutionary increasing levels of detail. The three levels of
configuration documentation are the functional configuration documentation, the
allocated configuration documentation, and the product configuration
Configuration identification. Configuration identification includes the
selection of CIs; the determination of the types of configuration documentation
required for each CI; the issuance of numbers and other identifiers affixed to
the CIs and to the technical documentation that defines the CI's configuration,
including internal and external interfaces; the release of CIs and their
associated configuration documentation; and the establishment of configuration
baselines for CIs.
Configuration Item (CI). A configuration item is an
aggregation of hardware or software that satisfies an end use function and is
designated by the Government for separate configuration management.
Configuration Management (CM).
a. As applied to configuration items, a
discipline applying technical and administrative direction and surveillance over
the life cycle of items to:
(1) Identify and document the functional and
physical characteristics of configuration items.
(2) Control changes to
configuration items and their related documentation.
(3) Record and
report information needed to manage configuration items effectively, including
the status of proposed changes and implementation status of approved
(4) Audit configuration items to verify conformance to
specifications, drawings, interface control documents, and other contract
b. As applied to digital data files (See MIL-HDBK-59), the
application of selected configuration identification and configuration status
accounting principles to:
(1) Uniquely identify the digital data files,
including versions of the files and their status (e.g., working, released,
Record and report information needed to manage the data files effectively, including the status
of updated versions of files.
Configuration Management Plan (CMP). The document
defining how configuration management will be implemented (including policies
and procedures) for a particular acquisition or program.
The recording and reporting of
information needed to manage configuration items effectively,
a. A record of the approved configuration documentation and
b. The status of proposed changes, deviations,
and waivers to the configuration.
c. The implementation status of
d. The configuration of all units of the
configuration item in the operational inventory.
Contractor. An individual, partnership, company, corporation,
association or other service, having a contract with the Government for the
design, development, manufacture, maintenance, modification, or supply of items
under the terms of a contract. A Government activity performing any or all of
the above functions is considered to be a contractor for configuration
Critical item. See MIL-STD-490.