Configuration Management Non Government Std: EIA Standard-649 “A management process for establishing and maintaining consistency of a product’s performance,

Configuration ManagementNon Government Std: EIA Standard-649

Configuration ManagementNon Government Std: EIA Standard-649

“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.”

• Identify and document the functional and physical characteristics of configuration items.

• Control changes to configuration items and their related documentation.

• Record (or Status Accounting in DoD terms) and report information needed to manage configuration items effectively, including the status of proposed changes and implementation status of approved changes.

• Audit configuration items to verify conformance to specifications, drawings, interface control documents, and other contract requirements.

- Adopted by DoD, 22 Nov 96

Configuration ItemsConfiguration Items

• CONFIGURATION ITEM (CI) - An aggregation of hardware or software that satisfies an end use function and is designated by the Government for separate configuration management.

• CIs will be directly traceable to WBS.

• Any item required for logistics support and designated for separate procurement is also a CI.

• Computer hardware & software will be treated equally as CIs.

• High risk or safety concern?

• Readily identifiable physically ?

• Newly developed?

• Use new technologies?

• Interface with item developed under another contract?

• Interface with other CI’s whose configuration is controlled by someone else?

• Requirement to know exact configuration during life?

Why Designate it as a Configuration Item?Why Designate it as a Configuration Item?

Impact of CI DesignationImpact of CI Designation

• Separate specifications.

• Put under configuration control.

Documentation

Formal approval of changes

Status accounting

Configuration Audits

• Individual design reviews.

• Separate qualification tests.

• Separate operating and user manuals.

Configuration BaselinesConfiguration Baselines

• Used to ensure an orderly transition from one major commitment point to the next.

• Three distinct evolutionary increasing levels of detail:

• Functional configuration documentation.

• Allocated configuration documentation.

• Product configuration documentation

• A baseline plus approved changes from that baseline constitutes the current approved configuration documentation.

ECP

Baseline

ECP+ + Approved

Configuration=

APPROVED APPROVED

IOCBA

Single Step orEvolution to Full

Capability

Concept &Technology

DevelopmentSystem Development

& Demonstration

Production &Deployment

Pre-SystemsAcquisition

Systems Acquisition(Engineering and Manufacturing

Development, Demonstration, LRIP &Production)

Operations &

Support

C

Technology Opportunities &User Needs

Post-SystemsAcquisition

Process entry at MilestonesA, B, or C (or within phases)

Program outyear fundingwhen it makes sense, but nolater than Milestone B(unless entering at C)

Relationship to Requirements Process

MNS ORD

All validated byRequirements Authority

or PSA

FRPDecisionReview

BLOCK II

BLOCK III

FOC

IOT&E

DESIG

N

FAB

, IN

TEG

RAT

E &

TEST

SFR

PDR

CDR

TRR

SVRSRR

Specification Evolution Across the Life Cycle

Specifications - - - - - - - - - - - - -----------------------------------------------------------------------------------------

System Spec

- - - - - - - - - - - - - -------------------------------------------------------------------------Item Performance Spec

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ------------------------------------------------Item Detail, Process, Material Specs

SFR

PDR

PCA

FCACDR

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ------------------------------------------------

- - - - - - - - - - - - - -------------------------------------------------------------------------

Functional (system)

Allocated (design to)

Product (build to)

Configuration Baselines - - - - - - - - - -----------------------------------------------------------------------------------------

Configuration Management PlanningConfiguration Management Planning

• The decision as to

• Which baselines the government should eventually control

• The data needed

• When that control should be established

are strategic management decisions that involve

• Acquisition strategies - sources, competition, etc.

• Logistics support plans - repair levels, data needs, open systems, etc.

• Technology insertion - stable vs rapidly moving technologies, etc.

Configuration Management StrategyConfiguration Management Strategy

• Government should control the Functional Baseline (documents system level requirements)

• DoD PMO’s increasingly choose to leave Allocated Baselines under contractor control until late in development. (Documents the CI level design requirements.) • Promotes contractor design flexibility

• Relieves PMO from administrative burdens of managing design ECPs

• Requires effective implementation of IPPD

• When and if to control baselines is dependent on support philosophy and acquisition management strategy.

Configuration IdentificationConfiguration Identification

• The selection of the documents to comprise the technical baseline for the system and configuration items involved.

• Selection of the numbers and other identifiers affixed to the items and documents.

• Basis for configuration audits, configuration control, and configuration status accounting.

s/n xxxxxx

s/n yyyyyy

ECPDWG

Spec’n

Dwg no xxx

Configuration ControlConfiguration Control

• Purpose of configuration control:

• Provide management visibility.

• Prevent unnecessary or marginal changes.

• Establish change priorities.

• Assure prompt action:

• Control the change.

• Document the change.

• Control the release system.

• A configuration control board is established to review

proposed changes and advise the program manager.

CONTRACTING

OFFICER

Configuration Control BoardConfiguration Control Board

OTHER

IMPLEMENTING

ACTIVITIES

ENGINEERING CHANGE

PROPOSAL (ECP)

Alteration in approved

CM Doc’s CI (possibly

with a spec change)

CONFIGURATION

CONTROL BOARD

DIRECTIVE

CCB SECRETARIAT (CONFIG MGR)

CHAIRMAN (PM)

USING COMMAND

TNG COMMAND

LOG COMMAND

ENGINEERING

PROCUREMENT

PROGRAM CONTROL

TEST

CONFIG MGT

SAFETY

FLT SURGEON

MAINTENANCE

CONTRACTOR

Begins & Ends

Configuration Status AccountingConfiguration Status Accounting

• Provides a track of configuration identification changes.

• Documents the configuration of items.

• Helps ensure on time shipments of change kits.

• Helps provide proper training.

• Helps ensure installation of correct items.

Configuration AuditsConfiguration Audits

• Verify and document that the configuration item and its configuration documentation:

• Agree.

• Are complete and accurate.

• Satisfy program requirements.

• Two types:

• Functional Configuration Audit

• Physical Configuration Audit

Functional Configuration AuditFunctional Configuration Audit

“ASBUILT”RECORDS

TEST

PROCEDURES

CONFIGURATIONIDENTIFICATION

CONFIG

ITEM

SPEC

QUALIFICATIONTEST REPORTS

COMPAREDWITH

RELEASEDENGINEERING

CONFIGURATION

QUALIFICATIONTESTING

INITIAL UNIT OF PRODUCTIONHARDWARE

AUTHORIZEDCHANGES

Physical Configuration AuditPhysical Configuration Audit

ACCEPTANCE TESTDATA

INTEGRATEDRECORDSSYSTEMFORMS

INPUT FOR CONFIGURATION

STATUS ACCOUNTING

REPORT

ACCEPTANCETEST

PROCEDURESRELEASE

ENGINEERINGDATA

PHYSICALLY(size, type, dimensions)

COMPARED WITH

ITEM DETAILSPECIFI-CATION

CONFIGURATIONIDENTIFICATION

INDEX

INITIALUNIT OF

PRODUCTIONHARDWARE

AUTHORIZEDCHANGES

COMPLIANCE REPORTED

VERIFY

SummarySummary

• Configuration management is essential to control the system design throughout the life cycle. The issue is not whether or not to have a configuration management program, but, rather, how it shall be managed.

• Configuration management impacts across the technical and business spectrum and requires an integrated (IPPD) approach to ensure that decisions made are well founded and that surprises do not occur.