1.

Configuration Management Principles Operational Product/Enabling Products: Enabling RIDs analyzed by review board; documentation
parts of the system considered in the product tree updated.
Why Configuration Management? and CI selection. Related documentation includes Baseline established.
Enables rebuilding the same product. configuration definition documents, specifications,
drawings, manuals, test procedures, and change As-Designed Configuration: Last approved baseline
Masters complex system development. assessments. plus approved departures (changes and deviations).
Ensures compliance with customer requirements.
Correctly shares project data among stakeholders.
Definitions:
Configuration: Set of functional and physical
characteristics defined by technical documents
and achieved by the product.
Configuration Management: Activity for
establishing and maintaining consistent records of Configuration Baselines: Change: Agreed evolution of a configuration baseline
product performance parameters and attributes. (anomaly fix, need evolution, etc.). Permanent once
Subdivided into configuration identification, Approved status of requirements and design at notified; applied to all product items; can be applied
control, status accounting, and verification. project milestones. to already produced items (retrofit).
Configuration Item (CI): Serves as a reference for lifecycle activities. Deviation: Permission to depart from specified
Product specifically designed for the project. Approved and frozen following design review. requirements before realization. Becomes part of as-
Has its own documentation (URD, design files, test Defined according to predefined content. designed configuration.
manuals). Life Cycle Models: Waterfall, V-lifecycle, Agile, Change vs. Deviation:
Has specific reviews (PDR, CDR, QR). incremental, SIS, moving baselines (CMII). Change: Applies to current baseline; modifies
CI Selection Criteria: Configuration management is defined for each baseline requirements.
Product specific to the project (no COTS). model, specifying phases, inputs/outputs, baseline Deviation: Applies to customer requirements;
content, and change processes. addresses unmet requirements.
Requires new design or significant modification. Typical Space Project Lifecycle: SRR, PDR, CDR, As-Built Configuration: Configuration of one
Sub-assembly that may be reused. QR, AR. Baselines are established at each review product item; identifies gaps of conformity with as-
Technical and contractual homogeneity. (functional, design, product). designed configuration. Starting point for "in-use
Baseline Establishment: configuration".
Knowledge from similar projects. Waiver (Concession): Permission to use/release a
Review data package sent to customer/review non-conforming product. Usually time or quantity
team. limited.
RIDs (Review Item Discrepancies) formalized. Deviation vs. Waiver:
 Deviation: Permission to depart from requirements Configuration Status Accounting (CSA): Configuration Management Tool Functionalities: CI
before realization; compliant. Formalized recording and reporting of product identification, documentation management, tree
Waiver: Permission to use a non-conforming characteristics, change status, and implementation management, document applicability, status
product; non-compliant. status. Ensures all project members work with the management, access control, baseline management,
right information. reporting, change/deviation/waiver management, as-
Change Process: CSA Procedures: Defining documentation designed/as-built configuration.
1. Need for change. distribution means; producing/distributing Reference Documents: ISO 10007, RG Aéro 000 23,
2. Modified design description. configuration status reports; using software tools for EIA-649 A, ECSS-M-ST-40C, CMII.
3. Impact analysis (technical and programmatic). direct data access. ISO 10007: International standard; general
4. CCB decision. CIDL (Configuration Item Data List): Shows as- configuration management principles.
5. Change implementation. designed configuration status (document versions, RG Aéro 000 23: BNAE standard; additional
Failed Impact Analysis Examples: New Spanish changes, deviations, physical configuration). information for complex programs.
submarine (weight exceeded, impact on base ABCL (As-Built Configuration List): Shows product EIA-649 A: ANSI standard; configuration
access); Berlin airport (floor addition, impact on item references (including serial numbers) and management process; mainly used in military domain.
electrical and water systems). accepted waivers.
Configuration Control Board (CCB): Regular Putting in Place Configuration Management: ECSS-M-ST-40C: ECSS standard; configuration
meeting for change/departure decisions. Chaired by Quality system, responsibilities, tasks, interfaces, management requirements for space projects;
project manager; includes representatives from all process definition. applies to European space projects.
project disciplines. Configuration Management Plan (CMP): Document CMII: ICM standard; process model (requirements-
Identification Marking: Unique identification code presenting configuration management rules, driven, moving baselines); people and tool
for each item (HW and SW). Enables traceability responsibilities, and processes. Delivered to the certifications.
throughout the lifecycle. customer with a compliance matrix. Annex 1: ECSS-M-40 project phases and baseline
Identification Rules: Reference, major index, minor Configuration Manager Responsibilities: Defining definition.
index. Major and minor indexes manage internal processes, writing CMP, interfacing with Annex 2: Definitions (product, product tree,
interchangeability. customer/subcontractors, operating configuration configuration item, configuration).
Interchangeability: Capability of two configurations management (identification, CCB secretary,
to be replaced. Criteria may vary depending on reporting).
application domain. Information System: Configuration management
Configuration Verification: Determines conformity functionalities integrated into the information system.
of configuration item to its documents. Verifies as- Ensures unique information and clearly identified
built status against as-designed configuration data owners/access rights.
(functional and physical). Establishes product
configuration baseline.