mlr associates 11-99 1 configuration management based on best practices alan e. lager mlr associates...

MLR Associates 11-99 1

Configuration Management

Based on Best PracticesAlan E. Lager

MLR Associates

Alan E. Lager MLR Associates

2801 Park Center Drive, #A1612, Alexandria, VA 22302, USA

Voice: 1 703 5673280; 1 703 624 8857 Fax: 1 703 567-3279

E-Mail: [email protected]://www.mlrassociates.com

Manchester, UK, FEB 2000Manchester, UK, FEB 2000CMCMEuropeEuropeEuropeEuropeSeminar A1 – Establishing Industry Best Seminar A1 – Establishing Industry Best

PracticesPracticesSeminar A1 – Establishing Industry Best Seminar A1 – Establishing Industry Best

PracticesPractices


Configuration Management Based on Best Practices

What is CM -- Really? What are Best CM Practices? ANSI/EIA-649 Perspective Fundamental CM Principles

– Planning and Management– Configuration Identification– Configuration control– Configuration Status Accounting– Configuration Verification and Audit

Measuring and Benchmarking CM Practices

Configuration Management Based on Best Practices

What is CM -- Really? What are Best CM Practices? ANSI/EIA-649 Perspective Fundamental CM Principles

– Planning and Management– Configuration Identification– Configuration control– Configuration Status Accounting– Configuration Verification and Audit


Agenda


What is Configuration Management

- Really?


What is CM - Really!

Change Requests• Improve design• Increase reliability• Enhance Maintainability• Reduce Cost• Etc.

Known Current Configuration

Updated Configuration

Controlling changes from idea inception to incorporation in all affected items

CMIN OUT

Status


What is CM - Really?

CM makes sure that:–The configuration of a product

is known and reflected in product information

–Product change is beneficial and effected without adverse consequences

–Change is managed from idea inception to incorporation in all items affected

CM makes sure that:–The configuration of a product

is known and reflected in product information

–Product change is beneficial and effected without adverse consequences

–Change is managed from idea inception to incorporation in all items affected


What is CM - Really? CM is an amalgamation of a set

of best industry practices Properly applied, CM

– Serves both the provider (developer, producer, supplier) and the user (customer) of a product

– Facilitates Logistic Support (Product Support) and product maintenance

– Is a Cost Avoider NOT a Cost Driver!!!

CM is an amalgamation of a set of best industry practices

Properly applied, CM – Serves both the provider

(developer, producer, supplier) and the user (customer) of a product

– Facilitates Logistic Support (Product Support) and product maintenance

– Is a Cost Avoider NOT a Cost Driver!!!


What are Best CM Practices?


What are “Best Practices”

Practices that are the benchmark by which similar activities are judged

Methods that– Are effective and efficient – Meet customer requirements– Have rational performance goals– Include performance measurement

standards – Align with corporate business objectives– Position the organization as a leader

Practices that are the benchmark by which similar activities are judged

Methods that– Are effective and efficient – Meet customer requirements– Have rational performance goals– Include performance measurement

standards – Align with corporate business objectives– Position the organization as a leader


What are Best CM Practices?

Applicable CM Principles

Customer Environment

Supplier Environment

BenchmarkAssessMeasure

Documented CM Process

Integrated inOrganizational Process


ANSI/EIA-649 Perspective

ANSI/EIA 649 “National (US) Consensus

Standard on Configuration Management”ANSI American National

Standards Institute

EIA Electronic Industries Alliance


ANSI/EIA-649 Perspective EIA-649 Presents Industry View EIA-649 Presents Industry View

MIL-STD View

Buyer imposed Requirements

649 View

Industry “Best Practices” employing CM principles EIA- 649 Rationale for Performing

CM

– Provides Benefit– Avoids Cost– Best Value


PurposPurposee

Allows common sense application of CM

principles De-fuses the terminology issue using

Aliases Sells CM on its Merits

– Example: Product attributes are defined»Measurable Performance Parameters»Both Buyer & Seller have common basis

for acquisition & use of the product

Allows common sense application of CM principles

De-fuses the terminology issue using Aliases

Sells CM on its Merits– Example: Product attributes are

defined»Measurable Performance Parameters»Both Buyer & Seller have common basis

for acquisition & use of the product

ANSI/EIA-649 Perspective

BenefitBenefitss


Fundamental CM Principles

CM Planning & Management



To assure that the appropriate CM processes and activities are applied

To establish CM organizational responsibilities

To determine the necessary resources and facilities

To provide a basis for continuous improvement

To enhance the maturity of the enterprises process

To assure that the appropriate CM processes and activities are applied

To establish CM organizational responsibilities

To determine the necessary resources and facilities

To provide a basis for continuous improvement

To enhance the maturity of the enterprises process

Purpose and benefits


Configuration Management Processes (ANSI/EIA 649)

CONFIGURATION CHANGE

MANAGEMENT

Manage changes

CM PLANNING & MANAGEMENT

Selection, tailoring, guidance, oversight

Attributes, identifiers, baselines

CONFIGURATION

IDENTIFICATION

CM information & status

CONFIGURATION

STATUS ACCOUNTING

CONFIGURATION

VERIFICATION/AUDIT

Verify performance & consistency

Assure data integrity

CM OF

DIGITAL DATA


EIA 649 - CM Principle #1

Plan CM processes for the context and environment in which they are to be performed and manage in accordance with the planning:– Assign Responsibilities/Document

procedures – Train personnel– Measure Performance; and– Assess measurements/trends to

effect process improvements

Plan CM processes for the context and environment in which they are to be performed and manage in accordance with the planning:– Assign Responsibilities/Document

procedures – Train personnel– Measure Performance; and– Assess measurements/trends to

effect process improvements

Be Prepared!



Consistent with ISO10007 - CM Plan 7.7 Configuration

Management Plan– A CMP provides the CM

procedures that are to be used and states who will undertake these and when

8. Configuration Management System Audit– Determine conformity of

the applied CM practice to the procedures described in the CM plan

7.7 Configuration Management Plan– A CMP provides the CM

procedures that are to be used and states who will undertake these and when

8. Configuration Management System Audit– Determine conformity of

the applied CM practice to the procedures described in the CM plan

1. Plan2. Document

Procedures3. Do what you plan




Configuration IdentificationConfiguration Identification


Configuration Identification

Configuration identification is the basis from which the configuration of products are defined and verified; products and documents are labeled; changes are managed; and accountability is maintained.

Benefits are realized only if there is consistency between the product and the information about the product

Product attributes are – Defined in configuration documentation– Achieved in the product– Verified for consistency between product

and documentation

Configuration identification is the basis from which the configuration of products are defined and verified; products and documents are labeled; changes are managed; and accountability is maintained.

Benefits are realized only if there is consistency between the product and the information about the product

Product attributes are – Defined in configuration documentation– Achieved in the product– Verified for consistency between product

and documentation



Purpose and Benefits of Configuration Identification

Determines structure of the product & documentation

Defines performance, interface & other attributes

Provides unique identity to product, components and documentation

Prescribes identification marking Modifies product and document

identifiers to reflect incorporation of major changes

Determines structure of the product & documentation

Defines performance, interface & other attributes

Provides unique identity to product, components and documentation

Prescribes identification marking Modifies product and document

identifiers to reflect incorporation of major changes


Purpose/Benefits, continued

Maintains release control and baseline definition

Provides reference for changes & corrective actions

Correlates document revision level to product configuration – Enables user to distinguish between

product versions– Enables service person to correlate

product to instructions– Correlates units to warranty/service

life

Maintains release control and baseline definition

Provides reference for changes & corrective actions

Correlates document revision level to product configuration – Enables user to distinguish between

product versions– Enables service person to correlate

product to instructions– Correlates units to warranty/service

life


Product Structure

Determine CIs

Select Config. DocTypes/Baselines

Identify Documents &

Items

Approve, Release & Baseline

Document-ation

CM Planning Documented CM Process

Contract Provisions

Configuration Documentation Approved, Released and

Baselined for Change Control by the appropriate Configuration Control Authority

Configuration Identification Process Activity Model

Configuration Items selected and Requirements allocated

Document and Item Identifiers assigned

Appropriate Configuration Document Types and Baselines selected

Configuration Documentation

Systems Engineering

-Reqmts/Functional Analysis

-Allocation & Synthesis

Logistics Maintenance Plan

Approved Engineering Changes



Configuration documentation defines the performance, functional and physical attributes of a product. Other product information is derived from configuration documentation.

Two major sets of product information are:– Configuration documentation– Operational Information

Configuration documentation is the product-defining documentation from which operational information and other product information is derived

Configuration documentation defines the performance, functional and physical attributes of a product. Other product information is derived from configuration documentation.

Two major sets of product information are:– Configuration documentation– Operational Information

Configuration documentation is the product-defining documentation from which operational information and other product information is derived



The Product Information Universe

Product Information

Operational Operational InformationInformation

Operate Maintain

Configuration Configuration DocumentationDocumentation

Reqmts Design

Build & Test

Sales

Distribution



All documents reflecting product performance, functional, or physical requirements and other product information are uniquely identified so that they can be correctly associated with the applicable configuration of the product.

Document identification enables retrieval Common identifiers include:

– Date– Assigned alpha numeric – Revision – Type of document– Title/subject– Originator/Organization– Customer’s contract or PO (if applicable)

All documents reflecting product performance, functional, or physical requirements and other product information are uniquely identified so that they can be correctly associated with the applicable configuration of the product.

Document identification enables retrieval Common identifiers include:

– Date– Assigned alpha numeric – Revision – Type of document– Title/subject– Originator/Organization– Customer’s contract or PO (if applicable)




All products are assigned unique identifiers so that – One product can be distinguished from

other products– One configuration of a product can be

distinguished from another– The source of the product can be

determined– The correct product information can be

retrieved.

All products are assigned unique identifiers so that – One product can be distinguished from

other products– One configuration of a product can be

distinguished from another– The source of the product can be

determined– The correct product information can be

retrieved.




Individual units of a product are assigned a product unit identifier when there is a need to distinguish one unit of the product from another unit of the product.

Typically by Serial Number Units serialized, e.g., when:

– Customer options– Warranties– Individual testing or screening

Individual units of a product are assigned a product unit identifier when there is a need to distinguish one unit of the product from another unit of the product.

Typically by Serial Number Units serialized, e.g., when:

– Customer options– Warranties– Individual testing or screening




When a product is modified, it retains its original unit identifier even though it’s part identifying number is altered to reflect a new configuration.

It is essential that serialization take place using a non-changing identifier as a base

Nothing degrades CM as much as two products with the identical part numbers and identical serial numbers!!

When a product is modified, it retains its original unit identifier even though it’s part identifying number is altered to reflect a new configuration.

It is essential that serialization take place using a non-changing identifier as a base

Nothing degrades CM as much as two products with the identical part numbers and identical serial numbers!!


P/N XYZ, S/N 1???



A series of like units of a product are assigned a product group identifier when it is unnecessary or impractical to identify individual units but nonetheless necessary to correlate units to a process, date, event or test.

Typically, by batch or lot number; In high production, a date code Enables unit to be correlated to

test or process records for the group Also non-changing base

A series of like units of a product are assigned a product group identifier when it is unnecessary or impractical to identify individual units but nonetheless necessary to correlate units to a process, date, event or test.

Typically, by batch or lot number; In high production, a date code Enables unit to be correlated to

test or process records for the group Also non-changing base




A baseline identifies an agreed-to description of the attributes of a product at a point in time and provides a known configuration to which changes are addressed.

EIA 649 Principle #17: Baselines are established by agreeing to the

stated definition of a product’s attributes. Baselines provide

–Assurance of stability & consistency–Common communication of product

definition–Ability to transfer authority

A baseline identifies an agreed-to description of the attributes of a product at a point in time and provides a known configuration to which changes are addressed.

EIA 649 Principle #17: Baselines are established by agreeing to the

stated definition of a product’s attributes. Baselines provide

–Assurance of stability & consistency–Common communication of product

definition–Ability to transfer authority

EIA 649 Principle #16:

N

S

W E



The configuration of any product, or any document, plus the approved changes to be incorporated is the current baseline.

The configuration of any product, or any document, plus the approved changes to be incorporated is the current baseline.


Product Configuration Baseline

Requirements

Requirements Baseline (Multi-Level)

Requirements Implemented in Design Design

Release Baseline

VerifiedProductConfiguration



For product interfaces external to the enterprise, establish an interface agreement and a mutually agreed-to documentation of common attributes.

In Buyer/Seller relationship, interface definition is part of purchase agreement

If no direct relationship exists, an interface agreement is negotiated

Documentation = ICD Procedures may include an ICWG

For product interfaces external to the enterprise, establish an interface agreement and a mutually agreed-to documentation of common attributes.

In Buyer/Seller relationship, interface definition is part of purchase agreement

If no direct relationship exists, an interface agreement is negotiated

Documentation = ICD Procedures may include an ICWG


Let’s interface


Understanding the Levels of Interface

SYSTEM B

A-B Same Contract

SYSTEM C

A-C Same CustomerDifferent Contract

SYSTEM D A-D Different Customer Different Contract

SYSTEM ACI a

CI b

CI c

Assembly Part 12

P4P4P3P2P1

Interfaces within CIs

Interfaces Between CIs

System Interfaces

CI c

P4

Part from

SupplierCI from Supplier

Supplier Interfaces



Configuration Control(Configuration Change

Management)

Configuration Control(Configuration Change

Management)


Configuration Change Management

Changes to a product are accomplished using a systematic, measurable change process.

Process includes– Identifying need for change– Documenting impact– Evaluation & Coordination– Incorporation of approved change– Verification

Also encompasses management of variances

EIA 649 Principle # 21


EIA 649Configuration Change Management Purpose and Benefits

– Enable change decisions to be based on knowledge of complete change impact

– Limit changes to those which are necessary or offer significant benefit

– Facilitate evaluation of cost, savings & trade-offs– Ensure customer interests are considered– Provide orderly communication of change information– Preserve configuration control at product interfaces– Maintain and control a current configuration baseline– Maintain consistency between product and

documentation– Document and limit variances– Facilitate continued supportability of the product

after change


Change Identification

Evaluation & Coordination

Implementation & Verification

New Current Baseline

Need for Change

Documented Change Request

Approved Change

Current Baseline

EIA 649 Change Management Process Model



Configuration Control Process Activity Model

GovernmentConfiguration Control

Initiation

ContractorConfiguration

Control

ECPs, RFDs

ContractorNeed forChange

ContractualProvisions

ApprovedECPs, RFDs

&Implementing

Direction/Authorization

DocumentedCM Process

C

C

C

CM MgmtCommunication

Requestfor ECP

CurrentConfigurationControlAuthority

Status &ConfigurationInformation

GovernmentConfiguration Control

Evaluation &Disposition (Fig. 4-4)

Need forChange toGovernmentBaseline

Contractor-ResponsibleChange Ident,Documentation& Disposition

Govt.Need forChange

ApprovedConfigurationDocumentation(CurrentBaselines)

C



Each change is uniquely identified

Objectives of change identification– Description and impact sufficient for

evaluation– Choose appropriate format– Provide unique identifier for the change

1 23 4

EIA 649 Principle #22




Changes represent opportunities for improvement

Changes initiated to:– Provide new capabilities– Enhance product support– Insert technology– Effect improvements– Correct defects or deficiencies– Reduce cost, improve efficiency

Changes represent opportunities for improvement

Changes initiated to:– Provide new capabilities– Enhance product support– Insert technology– Effect improvements– Correct defects or deficiencies– Reduce cost, improve efficiency



Classify changes to aid in determining the appropriate levels of review and approval.

Tabulated “best practice”factors differentiate between:– Major & Minor changes– Requirement for external customer

review in addition to internal review




Consider technical, support, schedule, and cost impacts of a requested change before making a judgment as to whether a change should be approved for implementation and incorporation in the product and its documentation.

Change evaluation and coordination process – Reviewing the preliminary impact assessments– Determining change effectivity– Establishing the cost/price– Dispositioning the change


I thought I knew it all !



Determine all potential effects of a change and coordinate potential impacts with the impacted areas of responsibility.

Impact Assessment– Details what is affected– Ensures that all potential effects are

known– Is essential to determine effectivity




Change Boards are a common means of achieving coordination necessary for impact assessment and change evaluation

Change Board characteristics:– Chaired by someone with authority to commit the

resources of the enterprise to implementing the change– Members represent functional activities or product

development teams... and have authority to commit the group they represent

– Agendas & documents ....distributed in advance– Board direction & decisions ...documented and

disseminated Board actions commonly accomplished electronically



Change documentation delineates which unit(s) of the product are to be changed. Change effectivity includes production break-in and retrofit/recall, as applicable.

A changed product should not be

distributed until its support and service areas are able to support it.

Effectivity determination requires– Knowledge of lead times– Balancing of many factors

EIA 649 Principle #28I like this date, it’s my birthday.

Where’s the instructions?




Effectivity delineates which units are to be changed

Effectivity is commonly expressed by– Product unit identifying number

(e.g., serial number)– Production date– Product group identifier

(e.g., lot, batch)– Model Year– Model Designation– Version number



The decision maker is aware of all cost factors in making the decision.

Prerequisites:– Impact assessment– Effectivity

CM process identifies– Immediate cost of change– Expected cost/savings in future

All cost factors are considered




Change approval decisions are made at an appropriate organizational level with the authority to commit necessary resources to implement the change.

Approval authority delegated to different levels, based on classification

As the life cycle progresses, authority typically transitions toward higher fiscal responsibility

Each organization establishes its own change authority levels



Implement an approved change in accordance with documented direction approved by the appropriate level of authority.

Planning for change implementation is– Initiated during change evaluation– Detailed after change is approved

Implementation involves– Release of new or revised configuration

documentation and other affected product information

– Change incorporation into product – Update of operation and support elements




Product

Product Information



Verify implementation of a change to assure consistency between the product, its documentation and its support elements.

Verification may be means of:– Detailed audit of product to documentation– Validation of installation or modification

instructions– Validation of operation and maintenance

instructions– Testing– or, a simple inspection

Verify implementation of a change to assure consistency between the product, its documentation and its support elements.

Verification may be means of:– Detailed audit of product to documentation– Validation of installation or modification

instructions– Validation of operation and maintenance

instructions– Testing– or, a simple inspection



Who sez I’m different?


If it is considered necessary to temporarily depart from specified baseline requirements, a variance is documented and authorized by appropriate level of authority.

Products that incorporate a known departure from requirements should not be delivered to a customer unless a request for variance has been documented and authorized.

Authorized variances do not constitute a change to configuration documentation

If it is considered necessary to temporarily depart from specified baseline requirements, a variance is documented and authorized by appropriate level of authority.

Products that incorporate a known departure from requirements should not be delivered to a customer unless a request for variance has been documented and authorized.

Authorized variances do not constitute a change to configuration documentation


ANSI/EIA-649 Request for Variance

The term “variance” is the alias for what is commonly referred to as– Deviation– Waiver

Variances are requested– Prior to manufacture– During manufacture– After manufacture

The term “variance” is the alias for what is commonly referred to as– Deviation– Waiver

Variances are requested– Prior to manufacture– During manufacture– After manufacture

Deviation!!

Waiver...

Deviation, I think!

Poor Form

NO FORM!!!



Configuration Status Accounting




An accurate, timely information base concerning a product and its associated product information is required throughout the product life cycle.

CM effectiveness is linked to information flow– Information collected while performing CM

activities– CSA correlates, stores, & maintains an

organized collection of information– CSA provides readily available views



Configuration Status Accounting TasksApproved

Configuration Documentation

Change Identification,Documentation, Disposition

Configuration Verification

Change Verification & Validation

Action Items

Status

Configuration Information

Performance Measurement

Record the current approved configuration documentation and configuration identifiers associated with each System/CI(s).

Record and report the status of proposed engineering changes from initiation to final approval to contractual implementation

Record and report the status of all critical and major requests for deviation which affect the configuration of a system/CI(s).

Record and report the results of configuration audits to include the status and final disposition of identified discrepancies and action items

Record and report implementation status of authorized changes Provide the traceability of all changes from the original released

configuration documentation of each System/CI(s) Report the effectivity and installation status of configuration

changes to all system/CI(s) at all locations, including design, production, modification, retrofit and maintenance changes

Record the digital data file(s)identifiers and document representations of all revisions/versions of each document and software which has been delivered, or made accessible electronically, in support of the contract.

Contractual Provisions

CSA Activity Model

Communication

Automated CM System based on CM Data Model & Data Element Dictionary

Documented CM process

CM Planning



Purposes and benefits– Enables retrieval of information concerning change decisions– Supports inquiries concerning future planning of design

changes, investigation of design problems, warranties, shelf and operating life calculations, etc.

– Access to complete configuration information on a product, any individual product unit, or group of product units

– Access to accurate identification of each delivered product unit

– Improves capability to identify, produce, inspect, deliver, operate, maintain, repair, and refurbish products

– Enhances availability of accurate information on spare parts and maintenance support

– Source for configuration history

EIA 649


Configuration Status Accounting over a System Life Cycle

CSA evolves over the product life cycle capturing more detailedinformation and enhancing its value as an information resource

Supporting

Physical

Design

Performance Definition

Solution

Configuration

Element Configuration

Concepts

0I

STATUS

STATUS ACCOUNTING

CAPABILITY

IIIII

Concept Studies Prog. Def

& RiskReduct. Eng &

Mfg Dev

Prod, Field/Deploy& Op Support

SYSTEM/CI LIFECYCLE

ACCOUNTING OBJECTS

MissionNeed



Configuration Verification and Audit

Configuration Verification and Audit


Configuration Verification & Audit

Verification that a product’s requirement attributes have been met and the product design meeting those attributes has been adequately documented is required to baseline the product configuration.

Configuration verification and audit establishes that:– The performance requirements have

been achieved by the design, and– The design has been accurately

documented in configuration documentation


We did it!



Purpose and Benefits– Ensure the product design provides the agreed to

performance capabilities– Validate the integrity of the configuration documentation– Verify the consistency between a product and its

configuration documentation– Determine that an adequate process is in place to

provide continuing control of the configuration– Provide confidence in establishing a product baseline– Ensure a known configuration as a basis for operation

and maintenance instructions, training, spares and repair parts.


VERIFICATION &AUDIT PLANNING*

CONFIGURATIONVERIFICATION

PROCESS

PRE- AUDIT

AUDIT Audit ReportVerification,Validation,Action Items

POST-AUDIT

• Verification Reqd• Audit Schedule

ApprovedConfigDoc.

Status &Config Info(From CSA)

Physical CI /CSCITest Results

Mfg. & Engrg. ToolsDocumentation

DocumentedCM Process

C

Confidence;Verified Product& Validated Process

Contractual Provisions

Verification,Validation,Action Items

(To CSA)

Status(viaCSA)

• Verified Configuration• Verified Changes• Open Items (Action Items)

(ToCSA)

• Agenda• Facilities, Tools• Personnel• Documentation• Availability of

Audit Objects• Certifications

Configuration Verification and Audit Activity Model


Accomplish &Verify Change

Update ConfigDocumentation

ReviseMfg/Prod/TestInstructions

Authorization toimplementapproved change

UpdateOrderingData**Orders for

• Supportequipment

• Trainers• Training• Spares• Tech. Manuals

Change Implementation and Verification

ProductMfg & Retrofit

Other AffectedSupportElements

Operating &MaintenanceInstructions



Verification that a design achieves its goals is accomplished by a systematic comparison of requirements with the results of tests, analysis or inspection.


• Incremental• Systematic• Incorporate in process flow• Requirements flow-down tools• Matrix (Results vs Requirement)



Documentation of a product’s definition must be complete and accurate enough to permit reproduction of the product without further design effort.

The design output must be captured and documented adequately

Documentation content and formality influenced by future procurement and maintenance needs

Verifying the documentation assures that it is adequate for its intended purpose




Where necessary, verification is accomplished by formal configuration audit.

Resources and material to perform functional and physical audit include:– Audit plan and agenda– Adequate facilities and unencumbered access– Availability of personnel– Applicable documentation, schedules, test results,

inspection records, etc.– Tools and inspection equipment– Isolation of the product and parts to be reviewed




Periodic reviews verify continued achievement of requirements, identify and document changes in performance, and ensure consistency with documentation.

Ongoing production and processes, are reviewed periodically to determine continued suitability

Operation of products or facilities are reviewed to identify and monitor changes or degradation of performance

Methods range from manual inspection to statistical process control and trend analysis




Process AssessmentProcess Assessment


Process Assessment Why Process Assessment?

– Quantify process as baseline for measuring improvements/Benchmarking

– Competitiveness; Product Quality; Process Improvement

Options to evaluate the effectiveness of CM Process

– Established Assessment Framework»SEI SW-CMM»EIA-731»Capability Maturity Model Integration (CMMI)

– Develop Internal Assessment


Process Assessment Capability Maturity Model (CMM)

– Yardstick for judging maturity of an organization’s process

– Identify Areas for Process Improvement CMM Components

– Model (Based on Documented Standard) »Framework for Process Definition »Process requirements (“What” not “How”)»Key elements of an effective process

– Assessment Process - - “How we measure it”»Process Elements - - “What you do” »Maturity Elements - - “How well you do it”


Internal Assessments

More focused and detailed than CMM’s Detailed Internal Assessment Model

– EIA Process Analysis Tool (PAT) Ver 1.4– Questionnaires and Scoring Sheets– Assessment Plan / Schedule– Training Material (Team & Participants)– Briefing material (Opening & Findings)– Final Report

Internal or Subcontractor Assessment Checklists


Product Structure Evaluation Checklist

Is the product (System/CIs) structured into a rational hierarchy?

Can the composition of each System/CI be determined from the configuration documentation?

Are subordinate CIs identified at a reasonable level for: – Specification of and measurement of

performance? – Management of the effectivity of changes?– Obtaining spare parts using performance or

design documents?

Is the product (System/CIs) structured into a rational hierarchy?

Can the composition of each System/CI be determined from the configuration documentation?

Are subordinate CIs identified at a reasonable level for: – Specification of and measurement of

performance? – Management of the effectivity of changes?– Obtaining spare parts using performance or

design documents?



BenchmarkingBenchmarking


Benchmarking Process Plan

– Establish Team– Identify What is to be Benchmarked– Identify Comparative Companies– Determine Data Collection Method

Collect Data Analyze

– Determine/quantify Performance Difference Set Improvement Goals

– Project future performance level and timeframe

– Establish Functional Goals– Develop Action Plans (including metrics)

Gain Acceptance Implement and Monitor Progress Re-assess

Plan– Establish Team– Identify What is to be Benchmarked– Identify Comparative Companies– Determine Data Collection Method

Collect Data Analyze

– Determine/quantify Performance Difference Set Improvement Goals

– Project future performance level and timeframe

– Establish Functional Goals– Develop Action Plans (including metrics)

Gain Acceptance Implement and Monitor Progress Re-assess

Does someone do

it better?

Does someone do

it better?