Previous: Summary of CM Knowledge Areas
Next: Other Resources

---

Configuration Management Body of Knowledge
Definitions and Terminology

Table of Contents - (Generated automatically from contents below)

---

1. DEFINITIONS AND TERMINOLOGY

Since a major goal of acquisition streamlining is to use commercial and industry practices to the greatest extent possible, there is no single correct set of CM terminology that must be rigidly adhered to. This section contains many aliases that are commonly used in different environments. It is appropriate to allow the use of common (local) terms to a given industry when dealing with that industry. The following acronyms and definitions are provided for reference.

Can "acquisition streamlining" be explained or reworded? -- NealFreeman^? 20 Feb 2003

1.1. Acronyms

AA	Application Activity
ABL	Allocated Baseline
ACD	Allocated Configuration Documentation
ACSN	Advance Change Study Notice
ACO	Administrative Contract Officer
AECMA	Association Europeene des Constructeurs de Materiel Aerospatial
AIS	Automated Information System
AMSDL	Acquisition Management Systems and Data Requirements Control List
ANSI	American National Standards Institute
CAGE	Commercial and Government Entity
CAO	Contract Administration Office
CCB	Configuration Control Board
CCBD	Configuration Control Board Directive
CCC	Configuration Control Classes
CDCA	Current Document Change Authority
CDR	Critical Design Review
CDRL	Contract Data Requirements List
CI	Configuration Item
CITIS	Contractor Integrated Technical Information Service
CLIN	Contract Line Item Number
CM	Configuration Management
CMDB	Configuration Management Database
CMIS	Configuration Management Information System
CMP	Configuration Management Plan
CMO	Contract Management Office
CSA	Configuration Status Accounting
CSAR	Configuration Status Accounting Report
CSCI	Computer Software Configuration Item
DID	Data Item Description
DSL	Definitive Software Library
DUI	Data Use Identifier
ECN	Engineering Change Notice
ECO	Engineering Change Order
ECP	Engineering Change Proposal
EMD	Engineering and Manufacturing Development
FBL	Functional Baseline
FCA	Functional Configuration Audit
FCD	Functional Configuration Documentation
GFD	Purchaser Furnished Data
GFE	Purchaser Furnished Equipment
HWCI	Hardware Configuration Item
ICD	Interface Control Drawing
ICWG	Interface Control Working Group
IDD	Interface Design Document
ILS	Integrated Logistics Support
IPT	Integrated Project Team
IRS	Interface Requirements Specification
ISO	International Organization for Standardization
LSA	Logistics Support Analysis
MIL-STD	Military Standard
MRB	Material Review Board
MWO	Modification Work Order
NDI	Non-Developmental Item
NOR	Notice of Revision
OPEVAL	Operational Evaluation
PBL	Product Baseline
PCA	Physical Configuration Audit
PCD	Product Configuration Documentation
PCO	Procurement Contracting Officer
PDI	Privately Developed Item
PDM	Product Data Management [System]
PDR	Preliminary Design Review
PIN	Part or Identification Number
PLAA	Purchaser Lead Application Activity
PPSL	Program Parts Selection List
RAC	Rapid Action Change [order]
RFD/W	Request For Deviation
RFP	Request for Proposal
RFW	Request For Waiver
SPS	Software Product Specification
SDL	Software Development Library
SCN	Specification Change Notice
SOW	Statement of Work
SRR	System Requirements Review
SSR	Software Specification Review
TCTO	Time Compliance Technical Order
TM	Technical Manual
TRR	Test Readiness Review
VDD	Version Description Document
VE	Value Engineering
VECP	Value Engineering Change Proposal
WBS	Work Breakdown Structure

1.2. Definitions

Advance Change Study Notice (ACSN)

A document which may be used, instead of a preliminary Engineering Change Proposal (Appendix ?), 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 documentation describing a CI's functional, performance, interoperability, and interface requirements that are allocated from those of a system or higher level configuration item; interface requirements with interfacing configuration items; and the verifications required to confirm the achievement of those specified requirements.

Allocated Configuration Identification (ACI)

Allocated configuration identification (allocated baseline and approved changes) consists of all specifications defining the requirements including functional, for each major configuration item. -- SmKershaw^? - 18 Feb 2003 {From Mil-STD 490A}

Application Activity (AA)

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

Approval/contractual implementation

The acceptance by the Purchaser 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 Purchaser's configuration control procedures.

Assembly

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

Authentication.

Determination by the primary customer that specification content is acceptable. -- SmKershaw^? - 12 Mar 2003

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 Purchaser 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 Series.

Computer data base

A collection of data in a form capable of being processed by a computer.

Computer data definition

A statement of the characteristics of the basic elements of information operated upon by hardware in responding to computer instructions. These characteristics may include, but are not limited to, type, range, structure and value. {from DoD^?-STD-2167} -- SmKershaw^? - 12 Mar 2003

Computer software

A combination of associated computer instructions and computer data definitions required to enable the computer hardware to perform computational on control functions. {from DoD^?-STD-2167}-- SmKershaw^? - 12 Mar 2003

Computer Software Component (CSC)

A distinct part of a computer software configuration item (CSCI). CSCs may be further decomposed into other CSCs and Computer Software Units (CSUs). {from DOD-STD-2167}-- SmKershaw^? - 12 Mar 2003

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)

An element specified in the design of a Computer Software Component (CSC) that is separately testable. {from DoD^?-STD-2167} -- SmKershaw^? - 12 Mar 2003

Configuration

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 audit".

Configuration baseline

1. An agreed-to description of the attributes of a product, at a point in time, which serves as a basis for defining change.
2. An approved and released document, or a set of documents, each of a specific revision; the purpose of which is to provide a defined basis for managing change.
3. The currently approved and released configuration documentation.
4. A released set of files comprising a software version and associated configuration documentation.

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

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 documentation.

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. {Can we work this in, or is it redundant.. "Configuration Identification is established by baseline configuration identificationi documents and all effected changes. Configuration identification documents include all those necessary to provide a full technical description of the characteristics of the configuration item that require control at the time that the baseline is established." from Mil-Std 490A -- SmKershaw^? - 18 Feb 2003 }

Configuration Item (CI)

A configuration item is an aggregation of hardware or software that satisfies an end use function and is designated by the Purchaser 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 changes.
4. Audit configuration items to verify conformance to specifications, drawings, interface control documents, and other contract requirements.

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, submitted, approved).
2. 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 project.

Configuration Status Accounting (CSA)

The recording and reporting of information needed to manage configuration items effectively, including:

a. A record of the approved configuration documentation and identification numbers.

b. The status of proposed changes, deviations, and waivers to the configuration.

c. The implementation status of approved changes.

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 Purchaser for the design, development, manufacture, maintenance, modification, or supply of items under the terms of a contract. A Purchaser activity performing any or all of the above functions is considered to be a contractor for Configuration Management purposes.

Control Point (Project Control Point)

A project agreed on point in time or times when specified agreements or controls are applied to the configuration items being developed, e.g., an approved baseline or release of a specified document/code. -- SmKershaw^? - 18 Feb 2003 {From IEEE Std 828-1990}

Critical item

A Critical Item is a configuration item which is below the level of complexity of a prime item but which is engineering critical or logistics critical.

a. A critical item is engineering critical where one or more of the following applies:

1. The technical complexity warrants an individual specification.
2. Reliability of the critical item significantly affects the ability of the system or prime item to perform its overall function, or safety is a consideration.
3. The prime item cannot be adequately evaluated without separate evaluation and application suitability testing of the critical item.

b. A critical item is logistics critical where the following apply:

1. Repair parts will be provisioned for the item.
2. The contracting agency has designated the item for multiple source reprocurement.

Current Document Change Authority (CDCA)

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

Data

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

Defect

Any nonconformance of a characteristic with specified requirements.

Deficiencies

Deficiencies consist of two types;

a. Conditions or characteristics in any item which are not in accordance with the item's current approved configuration documentation; or

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

Design change

See "Engineering change".

Developmental configuration

The contractor's design and associated technical documentation that defines the evolving configuration of a configuration item during development. It is under the developing contractor's configuration control and describes the design definition and implementation. The developmental configuration for a configuration item consists of the contractor's internally released hardware and software designs and associated technical documentation until establishment of the formal product baseline.

Deviation

A specific written authorization, granted prior to the manufacture of an item, to depart from a particular requirement(s) of an item's current approved configuration documentation for a specific number of units or a specified period of time. (A deviation differs from an engineering change in that an approved engineering change requires corresponding revision of the item's current approved configuration documentation, whereas a deviation does not.)

Distribution Statement

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

Document

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

Document custodian activity

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

Engineering change.

A change to the current approved configuration documentation of a configuration item at any point in the life cycle of the item.

Engineering Change Directive (ECD)

An internal performing activity document that indicates the approval of, and direction to incorporate or implement engineering change.

Engineering change justification code.

A code which indicates the reason for a Class I engineering change.

Engineering change priorities

The priority (emergency, urgent, routine) assigned to a Class I engineering change which determines the relative speed at which the Engineering Change Proposal is to be reviewed, evaluated, and, if approved, ordered and implemented.

Engineering Change Proposal (ECP)

A proposed engineering change and the documentation by which the change is described, justified, and submitted to the Purchaser for approval or disapproval.

Engineering Change Proposal types

A term covering the subdivision of Class I Engineering Change Proposals on the basis of the completeness of the available information delineating and defining the engineering change. They will be identified as preliminary or formal.

Engineering release

An action whereby configuration documentation or an item is officially made available for its intended use.

Engineering Release Record (ERR)

A record used to release configuration documentation.

Evaluation

The process of determining whether an item or activity meets specified criteria. {from DoD^?-STD-2168} -- SmKershaw^? - 12 Mar 2003

Exchangeability of items

See Interchangeable item, Replacement item, and Substitute item.

First Article Inspection and Configuration Review (FAICR)

The first article Inspection and Configuration Review is the operation or set of operations by which the first item produced in a series is verified for conformity to the contractual requirements applicable, in concurrence with a thorough review of all the documents defining the configuration to be considered.

FAR Clause

The FAR clause specifies that the Purchaser normally should accept "non-conforming material" only when it is in the Purchaser's best interests, and there is appropriate consideration.

Firmware

The combination of a hardware device of a hardware devices and computer instructions or computer data that reside as read-only memory software on the hardware device. The software cannot be readily modified under program control. {From DoD^?-STD-2167} -- SmKershaw^? - 12 Mar 2003

Fit

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

Form

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

Function

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

Functional area.

A distinct group of system performance requirements which, together with all other such groupings, forms the next lower-level breakdown of the system on the basis of function.

Functional Baseline (FBL)

The initially approved documentation describing a system's or item's functional, interoperability, and interface characteristics and the verification required to demonstrate the achievement of those specified characteristics.

Functional characteristics

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

Functional Configuration Audit (FCA)

The formal examination of functional characteristics of a configuration item, prior to acceptance, to verify that the item has achieved the requirements specified in its functional and allocated configuration documentation.

Functional Configuration Documentation (FCD)

The approved functional baseline plus approved changes.

Functional Configuration Identification (FCI)

Functional configuration identification (functional baseline and approved changes) will include all specifications necessary to specify 1) all essential system functional characteristics; 2) necessary interface characteristics; 3) specific designation of the functional characteristics of key configuration items; and 4) all of the tests required to demonstrate achievement of each specified characteristic. -- SmKershaw^? - 18 Feb 2003 {From Mil-Std 490A}

Hardware

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

Hardware Configuration Item (HWCI)

A configuration item that is hardware.

Integrated Logistics Support (ILS)

See MIL STD 1388 1.

Interchangeable item

A product which possesses such functional and physical attributes as to be equivalent in performance to another product of similar or identical purposes. It is capable of being exchanged for the other product without selection for fit or performance, and without alteration of the products themselves or of adjoining products, except for adjustment.

Interface

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

Interface control

The process of identifying, documenting, and controlling all functional and physical characteristics relevant to the interfacing of two or more items provided by one or more organizations.

Interface Control Documentation (ICD)

Interface control drawing or other documentation which depicts physical and functional interfaces of related or co-functioning items.

Interface Control Working Group (ICWG)

For projects which encompass a system, configuration item, or a computer software configuration item design cycle, an ICWG is established to control interface activity among the Purchaser, contractors, or other agencies, including resolution of interface problems and documentation of interface agreements.

Interoperability

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

Should a general term like interoperability be defined by specifically mentioning "defense services and agencies"? -- NealFreeman^? - 05 Mar 2003 {- modified according-- SmKershaw^? - 12 Mar 2003}

Item

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

Life cycle

A generic term covering all phases of acquisition, operation, and logistics support of an item, beginning with concept definition and continuing through disposal of the item.

Life cycle cost

The total cost of acquisition and ownership of a system over its life cycle to the purchaser of that system. The life cycle cost includes the cost of development, acquisition, support and where applicable, disposal.

Lot number

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

"Product-Tracking Base-Identifier" anyone? -- NealFreeman^? - 05 Mar 2003

Manufacturer's code

See "Commercial and Purchaser Entity (CAGE) code".

Material

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

Nomenclature

1. The combination of a Purchaser-assigned designation and an approved item name. In certain cases, the designation root serves as the basis for assignment of serial and/or lot numbers.
2. Names assigned to kinds and groups of products.
3. Formal designations assigned to products by customer or supplier (such as model number, or model type, design differentiation, specific design series or configuration.)

Non-conformance

The failure of a unit or product to conform to specified requirements.

Non developmental Item (NDI)

Non-developmental item is a broad generic term that covers material available from a wide variety of sources with little or no development effort required by the Purchaser. NDIs include:

a. Items obtained from a domestic or foreign commercial marketplace.

b. Items already developed and in use by the Services, other Defense activities, and Purchaser agencies.

c. Items already developed by foreign Purchasers which can be supplied.

Non-recurring costs

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

Nonrepairable Item

Any part or assembly for which user-maintenance is limited to replenishment of consumables and replacement of the part or assembly upon failure or malfunction.

Notice of Revision (NOR)

A document used to define revisions to drawings, associated lists, or other referenced documents which require revision after Engineering Change Proposal approval.

Original

The current design activity document or digital data file(s) of record.

Performing activity

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

Physical characteristics

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

Physical Configuration Audit (PCA)

The formal examination of the "as built" configuration of a configuration item against its technical documentation to establish or verify the configuration item's product baseline.

Prime Item

A Prime Item is a complex item such as an aircraft, missile, launcher equipment, fire control equipment, radar set, training equipment, etc.

Product Baseline (PBL)

The initially approved documentation describing all of the necessary functional and physical characteristics of the configuration item and the selected functional and physical characteristics designated for production acceptance testing and tests necessary for support of the configuration item. In addition to this documentation, the product baseline of a configuration item may consist of the actual equipment and software.

Product Configuration Documentation (PCD)

The approved product baseline plus approved changes.

Product Configuration Identification (PCI)

The product configuration identification (product baseline and approved changes) will include all specifications, engineering drawings and related data, as necessary, to provide a set of documents adequate for the procurement, production, test, evaluation, and acceptance of a configuration item without requireing further development work. This set of documents provides that technical description which describes the required physical characteristics of a configuration item; the functional characteristics designated for production acceptance testing; and required acceptance tests. -- SmKershaw^? - 18 Feb 2003 {From Mil-Std 490A}

Recurring costs

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

Release

The designation by the contractor that a document is complete and suitable for use. Release means that the document is subject to the contractor's configuration control procedures. The formal notification and distribution of an approved version. {partially from IEEE Std 828-1990. -- SmKershaw^? - 18 Feb 2003 }

Repair

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

Repairable Item

Any part or assembly which, upon failure or malfunction, is intended to be repaired or reworked.

Replacement item

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

Retrofit

The incorporation of new design parts resulting from an approved engineering change to an item's current approved product configuration documentation into already accepted and/or operational items.

Retrofit Instruction

The document that provides specific, step-by-step instructions about the installation of the replacement parts to be installed in delivered units to bring their configuration up to that approved by an ECP. (Sometimes referred to Alteration Instruction, Modification Work Order, Technical Directive, or Time Compliance Technical Order.)

Rework

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

Serial number

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

Software

Computer programs and computer databases.

Specification

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

Specification Change Notice (SCN)

A document used to propose, transmit, and record changes to a specification.

Substitute item

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

Support equipment

Equipment and computer software required to maintain, test, or operate an item or facility in its intended environment.

Survivability

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

System

A self-sufficient unit in its intended operational environment, which includes all equipment, related facilities, material, software, services, and personnel required for its operation and support.

Systems Development Life Cycle

The activities in developing a computer systems project beginning with perception of a need for the project. Next a feasibility study is performed. If a project is accepted, the analysis, logical and physical design, and testing stages occur. When the system has been tested and errors corrected, it is implemented. During use, the system is evaluated, possible leading to maintenance changes. -- SmKershaw^? - 18 Feb 2003 {From Information Systems Management, by James A. Senn}

Technical data

Technical data is recorded information (regardless of the form or method of recording) of a scientific or technical nature (including computer software documentation) relating to supplies procured by an agency. Technical data does not include computer software or financial, administrative, cost or pricing, or management data or other information incidental to contract administration.

a. Technical data is required to define and document an engineering design or product configuration (sufficient to allow duplication of the original items) and is used to support production, engineering, and logistics activities.

b. A technical data package should include all engineering drawings, associated lists, process descriptions, and other documents which define the physical geometry, material composition, performance characteristics, manufacture, assembly, and acceptance test procedures.

c. Technical data which provides instructions for the installation, operation, maintenance, training, and support of a system or equipment can be formatted into a technical manual.

1. 1. A technical manual normally includes operation and maintenance instructions, parts lists or parts breakdown, and related technical information or procedures exclusive of administrative procedures.
   2. This data may be presented in any form (e.g., hard copy, audio and visual displays, magnetic tape, disks, or other electronic devices).
   3. Technical orders that meet the criteria of this definition may also be classified as technical manuals. (Title 10, United States Code, Section 2302, "Definitions")

Technical data package

See "Technical data".

Technical documentation

See "Technical data".

Technical reviews

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

Training equipment

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

a. Are used to train maintenance and operator personnel by depicting, simulating, or portraying the operational or maintenance characteristics of an item or facility.

b. Are kept consistent in design, construction, and configuration with such items in order to provide required training capability.

Unit

See MIL-STD-280.

Version

An identified and documented body of software. Modifications to a version of software (resulting in a new version) require configuration management actions by either the contractor, the Purchaser, or both.

Waiver

A written authorization to accept an item, which during manufacture, or after having been submitted for Purchaser inspection or acceptance, is found to depart from specified requirements, but nevertheless is considered suitable for use "as is" or after repair by an approved method.

Work Breakdown Structure (WBS)

A work breakdown structure is a product-oriented family tree composed of hardware, software, services, data and facilities which results from engineering efforts during the acquisition of a material item. A workbreakdown structure displays and defines ther product(s) to be developed and/or produced and relates the elements of work to be accomplished to each other and to the end product(s).

Work breakdown structure element

A work breakdown structure element is a discrete portion of a work breakdown structure. A work breakdown structure element may be an identifiable item of hardware, sorftware, service, data or facilities.

---

-- DirkWessel^? - 09 Feb 2003

---

Previous: Summary of CM Knowledge Areas
Next: Other Resources

---