MIL-HDBK-61A: Definitions

< Previous | Contents | Next >

3.3 Definitions

Definitions for configuration management terms used in this standard are consistent with ANSI/EIA 649.

Allocated Baseline (ABL).: The approved allocated configuration documentation.
Allocated Configuration Documentation (ACD).: The documentation describing a CI's functional, performance, interoperability, and interface requirements that are allocated from those of a system or higher level configuration item; interface requirements with interfacing configuration items; and the verifications required to confirm the achievement of those specified requirements.
Application Activity (AA).: An activity that has selected an item or a document for use on programs under its control. However, it is not the current document change authority for the document(s).
Approval.: The agreement that an item is complete and suitable for its intended use.
Approved Document (or Data).: Document that has been approved by an appropriate authority and is the official (identified) version of the document until replaced by another approved version.
Archived Document (or Data).: Released or approved Document that is to be retained for historical purposes
Assembly.: A number of basic parts or subassemblies, or any combination thereof, joined together to perform a specific function. Typical examples are: electric generator, audio-frequency amplifier, power supply.
Computer database.: See Database.
Computer software.: See Software.
Computer Software Configuration Item (CSCI).: A configuration item that is computer software.
Computer software documentation.: Technical data or information, including computer listings, regardless of media, which document the requirements, design, or details of computer software; explain the capabilities and limitations of the software; or provide operating instructions for using or supporting computer software.
Configuration.: The performance, functional, and physical attributes of an existing or planned product, or a combination of products.
Configuration audit.: See: Functional Configuration Audit (FCA), and Physical Configuration Audit (PCA).
Configuration baseline (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.: (1) A systematic process that ensures that changes to released configuration documentation are properly identified, documented, evaluated for impact, approved by an appropriate level of authority, incorporated, and verified. (2) The configuration management activity concerning: the systematic proposal, justification, evaluation, coordination, and disposition of proposed changes; and the implementation of all approved and released changes into (a) the applicable configurations of a product, (b) associated product information, and (c) supporting and interfacing products and their associated product information.
Configuration Control Board (CCB).: A board composed of technical and administrative representatives who recommend approval or disapproval of proposed engineering changes to, and proposed deviations from, a CI's current approved configuration documentation.
Configuration Control Board Directive (CCBD).: The document that records the Engineering Change Proposal (ECP) approval (or disapproval) decision of the CCB and that provides the direction to the contracting activity either to incorporate the ECP into the contract for performing activity implementation or to communicate the disapproval to the performing activity.
Configuration documentation.: Technical documentation, the primary purpose of which is to identify and define a product's performance, functional, and physical attributes (e.g., specifications, drawings). (See also: Allocated Configuration Documentation [ACD], Functional Configuration Documentation [FCD], and Product Configuration Documentation [PCD].)
Configuration identification.: (1) The systematic process of selecting the product attributes, organizing associated information about the attributes, and stating the attributes. (2) Unique identifiers for a product and its configuration documents. (3) The configuration management activity that encompasses the selection of CIs; the determination of the types of configuration documentation required for each CI; the issuance of numbers and other identifiers affixed to the CIs and to the technical documentation that defines the CI's configuration; the release of CIs and their associated configuration documentation; and the establishment of configuration baselines for CIs.
Configuration Item (CI).: A Configuration Item is any hardware, software, or combination of both that satisfies an end use function and is designated for separate configuration management. Configuration items are typically referred to by an alphanumeric identifier which also serves as the unchanging base for the assignment of serial numbers to uniquely identify individual units of the CI. (See also: Product-Tracking Base-Identifier.)
Configuration Management (CM).: A management process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design and operational information throughout its life.
Configuration Management Plan (CMP).: The document defining how configuration management will be implemented (including policies and procedures) for a particular acquisition or program.
Configuration Status Accounting (CSA).: The configuration management activity concerning capture and storage of, and access to, configuration information needed to manage products and product information effectively.
Contract.: As used herein, denotes the document (for example, contract, memorandum of agreement/understanding, purchase order) used to implement an agreement between a tasking activity (e.g., buyer) and a performing activity (e.g., seller).
Contractual acceptance of data.: The action taken by the tasking activity signifying that an item submitted or delivered by the performing activity complies with the requirements of the contract.
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.)
Customer Repair (CR) Item.: Any part or assembly which, upon failure or malfunction, is intended to be repaired or reworked by Government personnel (including contract personnel other than the original manufacturer.)
Data.: Recorded information of any nature (including administrative, managerial, financial, and technical) regardless of medium or characteristics. (See also: Data item, Document.)
Database.: A collection of related data stored in one or more computerized files in a manner that can be accessed by users or computer programs via a database management system.
Data item.: A document or collection of documents that must be submitted by the performing activity to the procuring or tasking activity to fulfill a contract or tasking directive requirement for the delivery of information.
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) 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.
Deviation.: A specific written authorization to depart from a particular requirement(s) of an item's current approved configuration documentation for a specific number of units or a specified period of time, and to accept an item which is found to depart from specified requirements, but nevertheless is considered suitable for use "as is" or after repair by an approved method. (A deviation differs from an engineering change in that an approved engineering change requires corresponding revision of the item's current approved configuration documentation, whereas a deviation does not.)
Distribution Statement.: A statement used in marking a technical document to denote the extent of its availability for distribution, release, and disclosure without need for additional approvals and authorizations from the controlling DoD office.
Document.: A self-contained body of information or data 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.
Document representation.: (1) A set of digital files which, when viewed or printed together, collectively represent the entire document. (For example: a set of raster files or a set of IGES files.) A document may have more than one document representation. (2) A document in a non-digital form. (For example: paper, punched card set, or stable-base drawing.)
Engineering change.: (1) A change to the current approved configuration documentation of a configuration item. (2) Any alteration to a product or its released configuration documentation. Effecting an engineering change may involve modification of the product, product information and associated interfacing products.
Engineering Change Directive (ECD).: An internal performing activity document that indicates the approval of, and direction to incorporate or implement engineering change.
Engineering Change Proposal (ECP).: The documentation by which a proposed engineering change is described, justified, and submitted to (a) the current document change authority for approval or disapproval of the design change in the documentation and (b) to the procuring activity for approval or disapproval of implementing the design change in units to be delivered or retrofit into assets already delivered.
Exchangeability of items.: See Interchangeable item, Replacement item, and Substitute item.
Firmware.: The combination of a hardware device and computer instructions or computer data that reside as read only software on the hardware device.
Fit.: The ability of an item to physically interface or interconnect with or become an integral part of another item.
Form.: The shape, size, dimensions, mass, weight, and other physical parameters that uniquely characterize an item. For software, form denotes the language and media.
Function.: The action or actions that an item is designed to perform.
Functional Baseline (FBL).: The approved functional configuration documentation.
Functional characteristics.: Quantitative performance parameters and design constraints, including operational and logistic parameters and their respective tolerances. Functional characteristics include all performance parameters, such as range, speed, lethality, reliability, maintainability, and safety.
Functional Configuration Audit (FCA).: The formal examination of functional characteristics of a configuration item, or system to verify that the item has achieved the requirements specified in its functional and/or allocated configuration documentation.
Functional Configuration Documentation (FCD).: The documentation describing the system's functional, performance, interoperability, and interface requirements and the verifications required to demonstrate the achievement of those specified requirements.
Hardware.: Products made of material and their components (mechanical, electrical, electronic, hydraulic, pneumatic). Computer software and technical documentation are excluded.
Hardware Configuration Item (HWCI).: See Configuration Item (CI).
Interchangeable item.: A product which possess such functional and physical attributes as to be equivalent in performance to another product of similar or identical purposes; and 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 performance, functional, and physical characteristics required to exist at a common boundary.
Interface control.: The process of identifying, documenting, and controlling all performance, functional and physical attributes relevant to the interfacing of two or more products provided by one or more organizations.
Interface Control Documentation (ICD).: Interface control drawing or other documentation that depicts physical, functional, performance, and test interfaces of related or co-functioning products.
Interface Control Working Group (ICWG).: For programs that encompass a system, configuration item, or a computer software configuration item design cycle, an ICWG is established to control interface activity among the tasking activity, performing activities, or other agencies, including resolution of interface problems and documentation of interface agreements.
Interoperability.: The ability to exchange information and operate effectively together.
Item.: A nonspecific term used to denote any product, including systems, materiel, parts, subassemblies, sets, accessories, etc.
Life cycle cost.: The total cost to the tasking activity of acquisition and ownership of an item over its life cycle. As applicable, it includes the cost of development, acquisition, support, and, 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.
Manufacturer Repair (MR) Item.: Any part or assembly for which user-maintenance is limited to replacement of consumables and that, upon failure or malfunction, is returned to the original manufacturer for repair.
Materiel.: A generic term covering systems, equipment, stores, supplies, and spares, including related documentation, manuals, computer hardware, and software.
Modification Directive.: The documentation that indicates the approval of, and direction to implement, a modification request.
Modification Request.: The documentation by which a proposed modification of an asset is described, justified, and submitted to the asset owner (who is not the Current Document Change Authority for the asset design documentation) for approval or disapproval of implementing the modification in one or more units. A modification request may result in modification or installation drawings being created to describe the new configuration, but does not result in a revision of the existing design documentation for which an Engineering Change Proposal would be required.
Nomenclature.: (1) The combination of a Government-assigned designation and an approved item name. In certain cases, the designation root serves as the basis for assignment of serial and/or lot numbers. (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.)
Nonconformance.: The failure of a unit or product to meet a specified requirement.
Nonrecurring costs.: As applied an ECP, one-time costs that will be incurred if an engineering change is approved and which are independent of the quantity of items changed, such as cost of redesign or development 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 configuration documentation which require revision after Engineering Change Proposal approval. (See also Engineering Change Proposal [ECP].)
Original.: The current design activity's documents or digital document representation and associated source data file(s) of record.
Performing activity.: Denotes an activity performing any of the requirements contained in a contract or tasking directive. A "Performing Activity" can be either a contractor or Government activity.
Physical characteristics (attributes).: Quantitative and qualitative expressions of material features, such as composition, dimensions, finishes, form, fit, and their respective tolerances.
Physical Configuration Audit (PCA).: The formal examination of the "as-built" configuration of a configuration item against its technical documentation to establish or verify the configuration item's product baseline.
Product Baseline (PBL).: The approved product configuration documentation.
Product Configuration Documentation (PCD).: A CI's detail design documentation including those verifications necessary for accepting product deliveries (first article and acceptance inspections.) Based on program production/procurement strategies, the design information contained in the PCD can be as simple as identifying a specific part number or as complex as full design disclosure.
Product-tracking base-identifier.: An unchanging identifier used as a base for the assignment of serial numbers to uniquely identify individual units of an item or lot numbers to uniquely identify groups of units of an item. The product-tracking identifier is used rather than the Part or Identifying Number (PIN) because the PIN is altered to reflect a new configuration when the item it identifies is modified. The same product-tracking base-identifier may be used for several similar items (usually defined by a common document) and requires that each such item is assigned serial or lot numbers distinct from each other such item.
Product Tracking Identifier.: A generic term that refers to the sequentially assigned alphanumeric identifier applied to a product to differentiate units of the product or groups of the product. This may be a Government serial (or hull) number, manufacturer's serial number, lot number or date code.
Recurring costs.: Costs that are incurred on a per-unit basis for each item changed or for each service or document ordered.
Release.: The designation by the originating activity that a document representation or software version is approved by the appropriate authority and is subject to configuration change management procedures.
Released Document (Data): : (1) Document that has been released after review and internal approvals. (2) Document that has been provided to others outside the originating group or team for use (as opposed to for comment).
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.: One which is interchangeable with another item, but which differs physically from the original item in that the installation of the replacement item requires operations such as drilling, reaming, cutting, filing, shimming, etc., in addition to the normal application and methods of attachment.
Retrofit.: The incorporation of new design parts or software code, resulting from an approved engineering change, to a product's current approved product configuration documentation and into products already delivered to and accepted by customers.
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).: See Engineering Change Proposal (ECP).
Submitted Document (Data).: Released document that has been made available to customers.
Substitute item.: An item that possesses such functional and physical characteristics as to be capable of being exchanged for another item only under specified conditions or in particular applications and without alteration of the items themselves or of adjoining items.
Support equipment.: Equipment and computer software required to maintain, test, or operate a product or facility in its intended environment.
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.
Tasking activity.: An organization that imposes the requirements contained in a contract or tasking directive on a performing activity, (for example, a Government Contracting Activity that awards a contract to a contractor, a Government Program Management Office that tasks another Government activity, or a contractor that tasks a subcontractor.)
Technical data.: Technical data is recorded information (regardless of the form or method of recording) of a scientific or technical nature (including computer software documentation.)
Technical data package.: A technical description of an item adequate for supporting an acquisition strategy, production, engineering, and logistics support. The description defines the required design configuration and procedures required to ensure adequacy of item performance. It consists of all applicable technical data such as drawings and associated lists, specifications, standards, performance requirements, quality assurance provisions, and packaging details.
Technical documentation.: See Technical data.
Technical reviews.: A series of system engineering activities by which the technical progress on a project is assessed relative to its technical or contractual requirements. The reviews are conducted at logical transition points in the development effort to identify and correct problems resulting from the work completed thus far before the problems can disrupt or delay the technical progress. The reviews provide a method for the performing activity and tasking activity to determine that the development of a configuration item and its documentation have a high probability of meeting contract requirements.
Training equipment.: All types of maintenance and operator training hardware, devices, audio-visual training aids, and related software which:; 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.
Version.: (1) One of several sequentially created configurations of a data product. (2) A supplementary identifier used to distinguish a changed body or set of computer-based data (software) from the previous configuration with the same primary identifier. Version identifiers are usually associated with data (such as files, databases and software) used by, or maintained in, computers.
Waiver.: See Deviation.
Working Document (Data).: Document that has not been released; any document that is currently controlled solely by the originator including new versions of the document that were previously released, submitted, or approved.

For correct application of this information, see NOTE on Contents page