configuration-management-presentation

8/7/2019 Configuration-Management-Presentation

1/91

Company Confidential 1

Configuration ManagementGuidelines

Su pp ly Ch a in Manag em ent H andbook

Rev. Date: 11 June 2010


2/91

For ew or d

The guideline describes Configuration Management

functions and principles and defines ConfigurationManagement terminology for use with Aerospaceand Defense AS&D product line.

It is targeted at Small and Medium size companiesacting as subcontractors/suppliers either in a Buildto Print or a Build to Spec relationship.

The intention of these guidelines is to assistorganizations with understanding the concept andprocess of Configuration Management and is notintended to be a requirement, nor auditable.

2


3/91


4/91

When Configuration Management principles areapplied using effective practices, return oninvestment is maximized, product life cycle costsare reduced and the small investment in resourcesnecessary for effective Configuration Management

is returned many fold in cost avoidance.

These Guidelines provide the reader with the basicideas of the industry needs, the benefits to the

implementing organization and describesConfiguration Management functions andprinciples.

I n t r odu ct i on

4


5/91

Lis t o f Top ics

1. What is Configuration?

2. Why it is important to manage and controlconfiguration in AS&D

3. Applicable Terms and Definitions4. The objectives of Configuration Management

5. Benefits for an enterprise gained through applicationof CM6. CM and Documents control in 9100:20097. The Configuration Continuum8. CM functions

9. CM vs. Engineering Change10. CM Tools11. Summary12. Resources

5


6/91


1 . W h at i s Con f ig u r a t ion ?


7/91

Functional and physical characteristics ofexisting or planned hardware, firmware,software or a combination thereof as setforth in technical documentation and

ultimately achieved in a product.

7


8/91Company Confidential 8

2 . W hy i s i t im po r t an t t o m anage and con t r o l con f i gu r a t i on i n Aerospace & Defense?


9/91

Proper CM implementation can positively impact

Product Quality, On time Product Delivery, anddecrease development and life cycle costs

Product configuration presents a particularlydifficult set of challenges for Aerospace & Defense

resulting from: Large products involving a highly complex set of parts

and systems

Complex set of environmental and safety regulations

Ability to respond effectively to customer demands

9


10/91

Aerospace and Defen se Fu nc t ion a l

Needs Managing massive bid activities requiring

product configuration knowledge

Managing massive design activities requiringproduct configuration knowledge for:

Program and project management

Work Breakdown Structures (WBS)

Managing manufacturing operations Many, many open work orders

Frequent engineering change

10


11/91

Hardware and software CM at all stages of theproduct life-cycle

Configuration identification and change control

Configuration tracking, product traceability andvisibility

Storage, retrieval and transfer of data from acommon data base

The capability to reproduce products/processes Manufacture and testing of products only from

released documents

Aerospace and Defen se Fu nc t ion a l

Needs ( con t )

11


12/91

Aero space an d Defense Spec i f i c

Cons t ra in t s Project oriented activities

Research & Development

Devices Procurement

Complex & Extensive Bills of Material

Constant engineering change process

Long (30+ years) product life cycles

Legacy mind-sets

Both Government/Customers and Contractors

Classification & Security aspects

12


13/91Company Confidential 13

3 . App l i cab le t e rm s and de f in i t i ons


14/91

Configuration Management (CM)

CM is a methodology which provides a technicaland administrative framework for managing thedevelopment, manufacturing and maintenance ofConfiguration Items.

CM is an integral part of the product life-cyclemanagement.

Activity for establishing and maintainingconsistent record of the performance parametersof a product and its functional and physicalcharacteristics compared to the product designand operational requirements.

14


15/91

Configuration Management (CM) ( c o n t d )

This discipline is applicable to hardware,software, processed materials, services, andrelated technical documentation throughout theentire lifecycle of the product (i.e. development,

production, deployment, operation,maintenance and disposal).

15


16/91

Configuration I tem (CI)

An aggregation of hardware, firmware,software or any of its discrete portions, whichsatisfies an end use function and is designatedby the developer or customer for separate

configuration management. Any item requiredfor logistic support and designated for separateprocurement is a CI.

Configuration I tem (CI) selection

CIs should be selected with the object ofmaximizing control and minimizing the effortrequired to achieve that control.

16


17/91

Configuration Baseline

Approved status of requirements and design of aproduct at key project milestone that serve asreference for activities throughout the life cycleof the product.

Baselines, plus approved changes, constitute the

current approved configuration.

There are three formal baselines designatedconfiguration baselines in the life cycle of aconfiguration item:

Functional Baseline (system specifications)

Allocated Baseline (subsystem specifications)

Product Baseline (complete technical datapackage for the CI)

17


18/91

Configuration Identification

Coordinated activities to establish rulesor configuration item selection, baseline contentdefinition, and product and document identifiers.Identification is provided in the approved

baseline technical documentation, as shown inspecifications, tests, drawings, associated lists,and reference documents.

18


19/91

Configuration I tem Identification Numbers

For each configuration item you need to knowat any time the technical description of theitem and the identification should be changedwhen the technical characteristics are changedand when the two items are notinterchangeable. Every item which is definedas a CI must be marked as agreed.

19


20/91


21/91

Configuration Control

Coordinated activities for controlling changeto configuration baseline. Configurationcontrol should be applied to establishedbaselines, configuration identifications and allreleased engineering data. Configurationcontrol system should screen, classify andprocess changes in a manner that providesfully coordinated, approved change packagesin compliance with the requirements or

contract.

21


22/91

Configuration Status Accounting (CSA)

A formal process of recording and reporting ofproduct configuration information, the status ofproposed changes and the implementationstatus of approved changes.

Configuration Audits (CA)

Performed before the acceptance of aconfiguration baseline to assure the productcomplies with its specified requirements and to

assure the product is accurately reflected by itsconfiguration documents.

22


23/91

Functional Configuration Audit (FCA)

A formal examination of functionalcharacteristics of a configuration item (finalproduct), to verify that the item has achievedthe performance specified in its configurationidentification.

Physical Configuration Audit (PCA)

A formal examination of the "as-built"configuration of a product or a CI against its

technical documentation, in order to establishconformance between the product and itscurrent configuration identification.

23


24/91


4 . Th e Ob j ect iv es o f CM


25/91

CM represents a discipline which ensures that allparties to the acquisition of a product:

the buyer

the developer/designer

the manufacturer, and

the user (customer)

Have a common understanding about:

how the product looks (physical shape/ software code)

what the product is supposed to do (functionality,performance)

how the product can be operated (missionprofile/capabilities); and

how the product is maintained (supportability)

25


26/91

CM is the process or a set of requirements to be

included in every industrial process for establishingand maintaining a consistent record of a productsfunctional and physical characteristics compared toits design and operational requirements.

Configuration management is applied through-outthe entire life cycle of the product and allows one to:

know at any moment the technical description of asystem and its components, using approved

documentation

record and control effectively and continuouslyevolutions in the technical description and providetraceability of such evolutions throughout the life-cycleof the product

26


27/91

facilitate the consistency of the systems components(control of external interfaces) and the products that

make up these components (control of internalinterfaces)

verify that documentation is and remains the exactimage of the products it describes

identify the current configuration baseline and theas-built configuration of a product, to recorddiscrepancies detected during production, delivery oroperation and dispositioned for further use;

enable any user to know the operational capabilities

and limitations of each product item and, in case ofvariances or non conformances, to know which itemsare affected

CM accomplishes this through control of the productdefining technical data

27


28/91


5 . Bene f i t s f o r an en t e rp r i se ga ined t h r oug h app l i ca t i on o f CM


29/91

Conclusive and current information, knowing at any timewhat the enterprise is;

developing

building

testing

delivering maintaining

Assured product consistency, being enabled to;

deliver identical items

repeat performance

support the delivered product remotely

modify the product without the need of reverseengineering

29


30/91

Control of cost, CM helps a project to stay withinthe authorized budget frame;

Product changes may involve high costconsiderations. The right processing of changes andanalysis of costs can keep expense per change at itslowest rate.

Unauthorized changes will be prevented.

Thorough identification of all affected documentationand product elements reduces cost of search andanalysis of effects.

Approved changes can be immediately

incorporated in the technical documentation, butreleased for implementation into the product inaccordance with an authorized budget schedule.

Proper identification and change control reduced costof maintenance and reuse.

30


31/91

Visibility in planning, CM helps project planning byensuring that;

any schedule effect of a proposed change isreviewed prior to disposition of the change

interface requirements are assessed for effect of thechange on other design organizations schedules

Compliance with requirements, CM ensures theintended configuration by;

supporting internal and formal design reviews

performing the functional and physical configurationverifications (audits)

maintaining traceability of software configurationsto functional requirements

controlling changes to the approved documentation

communicating change status to all involved parties

31


32/91


6 . CM an d Docum en t Con t r o l in I AQG 9 1 0 0


33/91

FOREWORD

REVISION SUMMARY/RATIONALE

0 INTRODUCTION

1 QUALITY MANAGEMENT SYSTEMS REQUIREMENTS

2 NORMATIVE REFERENCES

3 TERMS AND DEFINITIONS

4 QUALITY MANAGEMENT SYSTEM4.2.3 Control of Documents4.2.4 Control of Records

5 MANAGEMENT RESPONSIBILITY

6 RESOURCE MANAGEMENT

33

A documented procedure shall beestablished to:

a) to approve documents foradequacy prior to issue,b) to review and update as necessaryand re-approvec) to ensure that changes and thecurrent revision status of documentsare identified,

d) to ensure that relevant versions ofapplicable documents are available atpoints of use,e) to ensure that documents remainlegible and readily identifiable,f) to ensure that documents ofexternal origin determined by theorganization to be necessary for the

planning and operation of the qualitymanagement system are identifiedand their distribution controlled, andg) to prevent the unintended use ofobsolete documents, and to applysuitable identification to them if theyare retained for any purpose.


34/91

7 PRODUCT REALIZATION7.1 Planning of Product Realization7.1.2 Risk Management7.1.3 Configuration Management7.1.4 Control of Work Transfers7.2 Customer-related processes7.2.1 Determination of Requirements Related to the

Product

7.2.2 Review of Requirements Related to the Product7.2.3 Customer Communication7.3 Design and Development7.3.1 Design and Development Planning7.3.2 Design and Development Inputs7.3.3 Design and Development Outputs

34

The organization shall define the data required to

allow the product to be identified, manufactured,inspected, used and maintained; including forexample

the drawings, part lists and specificationsnecessary to define the configuration and the designfeatures of the product, and

the material, process, manufacturing and assemblydata needed to ensure conformity of the product.

The organization shall establish, implement and

maintain a configuration management process thatincludes, as appropriate to the producta) configuration management planning,b) configuration identification,c) change control,d) configuration status accounting, ande) configuration audit.NOTE: See ISO 10007 for guidance.

The organization shall plan and develop theprocesses needed for product realization

In planning product realization, the organizationshall determine the following, as appropriate:.e) configuration management appropriate to theproduct;f) resources to support the use and maintenanceof the product


35/91

7.3.4 Design and Development Review7.3.5 Design and Development Verification7.3.6 Design and Development Validation7.3.6.1 Design and Development Verification and

Validation Testing7.3.6.2 Design and Development Verification and

Validation Documentation7.3.7 Control of Design and Development

Changes

35

Where tests are necessary for

verification and validation, thesetests shall be planned, controlled,reviewed and documented to ensureand prove the following:..c) the correct configuration of theproduct is submitted for the test,

Design and development changes shallbe identified and records maintained.The changes shall be reviewed, verifiedand validated, as appropriate, andapproved before implementation. Thereview of design and developmentchanges shall include evaluation of theeffect of the changes on constituent

parts and product already delivered.Records of the results of the review ofchanges and any necessary actions shallbe maintained (see 4.2.4).

Design and development changes shallbe controlled in accordance with theconfiguration management process (see7.1.3).


36/91


37/91


7 . The Con f ig u r a t ion Con t inu u m


38/91

ContractReview/Planning

DesignProduction

38

Request forInformation/Proposal

Proposal ContractAward

As Quoted

Configuration

As Accepted

Configuration

As Planned

Configuration

As Designed

Configuration

As Built

Configuration

As Documented

Configuration

As Maintained

Configuration

Delivery Service

Pr o j ect Li fe Cyc le Con f ig ur a t ion Prog r ess

As Specified - Customer

Requirement Baseline


39/91

As Speci f i ed / Requ i r em ent Base l in e ( Requ est fo r I n f o r m a t ion / Pr oposa l

RFI / RFP)

As Specified/Requirement Baseline is thecustomer baseline. It is specified in the RFI/RFPand includes any allocated requirements,specifications, structure, configurationmanagement requirements, etc.

The customer expects to receive information/proposal from the supplier including supplier

attitude to the Requirement Baseline.

39


40/91

As Quo t ed Con f igu r a t i on ( by t he supp l i er )

Following the RFI/RFP from the customer, thesupplier prepares his response.

In the response the supplier presents hisattitude toward the implementation of customerrequirements.

The supplier proposes a configurationmanagement plan in response to the customer'sconfiguration management requirements.

In some cases the proposed/quotedconfiguration differs from the As Specifiedconfiguration and thus it is the As Quotedbaseline.

40


41/91

As Accept ed Conf igu r a t ion ( Con f ig u r a t ion a t Con t rac t Aw a rd )

This configuration includes the systemrequirements specification & the systeminterface specification as finally agreed by thecustomer and the supplier.

The method to manage configuration baselinesand changes is established at this stage.

The As Accepted configuration serves as a basisfor the next (planning/review) phase.

41


42/91

Proper management and control of customerdocuments is a condition essential to themaintenance of a well regulated productionprocess. The management and control of thecustomer's documents and drawings should bedone as specified by the contract.

The customer defines the configurationmanagement requirements for the project. Theserequirements are applicable to all the actors of theproject.

The purpose of the CM plan is to define theprocess & resources for managing theconfiguration of the product in a controlled &traceable manner throughout the project life cycle.

42


43/91

As Plann ed Conf igu r a t ion ( Con t r ac t / Rev iew P lann ing )

The As Accepted configuration is reviewed duringinitial stages of contract implementation.

Mutually acceptable revisions to the configurationare included.

As part of the allocated baseline the sub-systems requirements & interface specifications

are frozen towards the Preliminary DesignReview phase (As Planned).

43


44/91

As Des ign ed ( By Eng ineer ing )

The As Designed configuration may be accomplished

in a few stages (as applicable to the contractedproduct):

System Requirements Review and System Design Review(SRR & SDR)

Preliminary Design Review (PDR)

Critical Design Review (CDR)

The configuration at each stage should include blockdrawings, schematic drawings, design documents,design interfaces documents and Validation &

Verification V&V documents. At each stage theconfiguration should be frozen and change controlimplemented.

At As Designed configuration (after CDR) thosedocuments are frozen.

44


45/91

As Bu i l t ( By P roduc t i on )

The manufacturer must enable tracking fromthe finished product to the components andmaterials comprising it, in accordance with thetype of the product and the contractrequirements.

During procurement, storage, production,assembly, and test, details & identificationmarking will enable the follow-up of the historyof the item in all its stages.

The level of traceability shall be specified andupdated in accordance with contractualrequirements.

45


46/91

As Bu i l t ( By Pro d u c t i o n ) - ( co n t d )

The traceability process shall allow, whenrequired, the identification of all productsmanufactured from the same batch of rawmaterial or from the same production batch aswell as the delivery destination of all products

from that batch. In addition, the process shallallow identification of all parts and componentsof products/assemblies defined as requiringtracking.

46


47/91

As Docum en t ed ( in Del i ve ry Docum en t a t ion )

An individual file will be issued for each itemfor which all the conditions specified belowhave been met, unless otherwise specified bycontractual requirements:

Item have been tested according to their individualtest procedures.

Item have been identified by individual serialnumbers.

Item have been awarded a Serviceable tag uponcompletion of test.

47


48/91

As Ma in t a ined ( Serv ice Docum en t a t ion )

The maintenance contract should define themaintenance levels, and the infrastructure to beprepared.

Involvement in product maintenance is set

according to customer demands, which aredecided upon receiving the customers order.

In certain cases, the demand will be to apply aspecific maintenance policy in manufacturing andthe design of the product, including the definitionof needs in training, accompanying technicaldocumentation, maintenance contract with thecustomer and suggestion of spare parts for initialprovisioning.

48


49/91


8 . Con f ig u r a t ion Managem ent Func t ions

CM P Fl


50/91

ConfigurationManagement

Hardware,software,

documentsnumberingmethods

Definition of

configuration

items

ConfigurationIdentification

ConfigurationReport

BaselineConfiguration

Producttrees

Document status

Hardwareproduction

Changemanagement

ConfigurationControl

SystemSpecification

Specifications + CD

Production Drawings+

Version DescriptionDocuments *

Changestatus

FunctionalBaseline

AllocatedBaseline

ProductBaseline

Waivers

MRB activity

CDR

PDR

ContractSRR

* Including assemblydraw ings, test and

integration documents

CM Pr ocess Flow

50


51/91

Conf igu r a t ion I den t i f i cat ion / Con f igu r a t ion Docum en t a t ion

Product File:

Provides the engineering documentation neededto build and test the product:

Hardware Software

Drawings and associated lists

Electronic media

Diagrams

Version Description Document (VDD)

Unique processes

Printed circuit card design

Acceptance test

51


52/91

Manufacturing File

Consists of the Product File, to which is addedmanufacturing operation sequences andprocesses.

Data File

Contractor Data Requirement List (CDRL)documentation required in addition to theproduct or manufacturing file includesspecifications, plans, analyses, tests, manuals,etc.

52


53/91

Con f ig ur a t ion Manag er s Task

Establishment of Configuration policy. Release and submittal of configuration

documentation in relation to program events.

Establishment of internal developmental

configuration and contractual baselines.

Establishment of configuration control boards.

Implementation of a status accounting

information and provision of reports.

53


54/91

Conf igu r a t ion Manager s Task ( con t d )

Account for and deliver Contractor DataRequirement List (CDRL) items.

Prevent duplication of data.

Apply change control.

Identify and maintain status of data received &submitted.

54


55/91

Conf igu r a t ion Con t ro l Board

Configuration Control Board (CCB) is a groupof technical and administrative experts withthe assigned authority and responsibility tomake decisions on the configuration and itsmanagement.

All proposed changes should be reviewed bythe CCB to evaluate the change against thecriteria and/or include as an alternate, notmaking the change.

In addition, it should evaluate all aspects of

the change to include design, performance,cost, schedule, operational effectiveness, andlogistics considerations.

55


56/91

Conf igu r a t ion Con t ro l

To maintain product control, no change may beimplemented without an approved change orderor approved deviation/waiver request.

The Configuration Manager and the CCB

members are responsible for the change controlprocess.

Configuration control is applied to establishedbaselines, identifications and releasedengineering data.

56


57/91

Con f igu r a t i on Con t ro l ( con t d )

Configuration control system should beestablished to provide for screening,classification and processes changes thatprovide fully coordinated, approved changepackages.

Configuration control should be applied toestablished baselines, identifications andreleased engineering data.

Configuration control should be implemented instages corresponding to the product life-cycle.

Before reviews and establishment of baselines,control may be maintained manually by thedevelopment engineer or by use of automatedtools as they are developed.

57


58/91

Upon freezing of the Bill Of Material (BOM) andthe order to procure components, changesshould be controlled by CCB.

Manufacturing release should includeimplementation of all approved internal

changes into the drawings.

Formal change control will commence withsuccessful completion of the production auditor with first delivery.

58

Con f igu r a t i on Con t ro l ( con t d )


59/91

Conf ig u r a t ion Repor t / Con f ig u r a t ion St a t us Accoun t ing

Upon initiation of component procurement,changes will be tracked in the database for eachdocument/drawing/list.

Each hardware delivery will generate an As

Planned/As Built Report reflecting the build ofeach unit.

Configuration Status Accounting Reports (CSAR):

The configuration manager maintains CSAR for the purposes ofinternal control to assure compatibility of the product and itsdocumentation, and producing the status accounting reportsnecessary for configuration visibility and traceability.

Feed-back from the As Planned/As Built Report providesconfirmation of the implementation of changes, deviations, etc.

59


60/91

The purpose of the Configuration audit is toverify that the configuration identification for aconfigured item is accurate, complete, and willmeet specified program needs.

There are two types of configuration audits:

Functional Configuration Audit (FCA) and

Physical Configuration Audit (PCA).

Both audits must be satisfactorily completed by

the project team members and the contractor asa prerequisite to establishing the productbaseline.

Con f igu r a t i on Aud i t

60


61/91

The results of the functional and physicalconfiguration audits should be documented,reviewed and verified.

Technical documentation and functionaldeficiencies detected during the audits will becorrected by change order.

Con f igu r a t i on Aud i t ( con t d )

61


62/91

Company Confidential

9 . CM v s . En g i n eer in g Ch an geCont ro l

62


63/91

63


64/91

I n t r odu ct i on

The aerospace and defense industries rely on thedevelopment and manufacture of complexproducts comprised of multiple systems,subsystems, and components each designed byindividual designers (design activities) at variouslevels within the supply chain (by the customer

or by any of the suppliers)

Each design activity controls various aspects ofthe configuration and specifications related to theproduct

64


65/91

I n t r od uc t i on ( con t d )

When a change to design information isrequested or required, the change has to beevaluated against the impacts to the higher levelsystem, as detailed in Notice of ChangeRequirements (AS9016).

A change request can be initiated by any of thestakeholders: customer, prime contractor,supplier, etc.

65


66/91

Ch an ge Con t r o l

Pr ocess Flo w

Change influence (retrofit,

Products in process, field)

Effectivity date

Additional tests

Initiating the ECP

(By any stakeholder)

Analyzing

(by initiator's management)

Initiation

Evaluation

by system engineer

CCB EvaluationRecording and

Submitting to additional

experts

Approval by

CCB

Change

Implementation

(Documents & Products)

Documents

Distribution

Rejecting

Change classification (I, II, III)

(Customer approval for class 1)

Cost

Rejecting

Approved

Work center A

Work center B

Subcontractor

/J.V'S

66


67/91

Design activities must meet the Quality System

Requirements and Customer Agreements beforeimplementation of changes as follows:

Changes that Require Customer AcceptancePrior to Implementation

Changes that May Require Acceptance Prior toImplementation

Changes Implemented Concurrent withNotification for Customer Acceptance

Non-Configuration changes

67


68/91

Design activities shall create a Notice of Change

(NoC) or Engineering Change Notice (ECN) andimplement the change. The design activity shalleither submit the NoC to the customer or makeall NoC records available for review, dependingon customer requirements.

The activities required are:

Approval of Design Activity to PerformChange Impact Assessments

Requirements for Data Submission of NoC

Record Retention

68


69/91

Changing the Product Structure (Bill Of Materials) Adding a part Deleting a part Changing the quantity per assembly

Changing the Part Itself Changing specifications New Part Number Changing approved sources?

Changing the Routing Changing the Process Changing the process sequence

W hat i s an En g in eer in g Chan ge?

69


70/91

The Engineering process have three mainmilestones to start an engineering change controlprocess:

Functional Baseline (FBL)

As part of the FBL, the following engineeringdocuments are released;

System Specification

System Requirements

System Interface Definition/Specification

Following the SDR & SRR, these documents are

frozen.

70


71/91

Allocated Baseline (ABL)

As part of the ABL, the following engineeringdocuments are released;

Sub-Systems Specifications

Sub-Systems Interface Specifications

Following the PDR, these documents are frozen

Product Baseline (PBL)

As part of the PBL, all engineering documentsare released;

Following the CDR, these documents are frozen

71


72/91

After all engineering documents are released &frozen (per the Baselines), changes need to bedone due to the following items:

Design

Performance

Reliability

Safety

Production

Drawings errors

As results of operation, maintenance

Change or new configurations (marketing)

As a result of a failure requiring Engineering Change

72


73/91

The Change Control Process is performed by a

Change Control Board (CCB). Engineering, Production, Purchasing, Customer,

Subcontractors are permitted to ask CCB to handleany change request

The Change Control Process includes two types ofchanges:

Major Change (Class 1 change)

Minor Change (Class 2 change)

73


74/91


75/91

W h at m u st an En g in eer in g Chan gePr opo sa l do? Tell us WHAT to change

Show us HOW to make the change

Tell us WHEN

Applicability (implementation) Tell us WHO

Define tasks and assign responsibilities

Show us WHERE

What documents, parts, purchasing

Tell us WHY

Really explain the reasons

75


76/91

The Engineering Change Proposal (ECP) should

present to the stake-holders all the data neededto approve or disapprove an Engineering Change

The approval procedure needs to refer to thefollowing:

Is the change justified?

Is the change a must ?

Can it be implemented ?

What could be the results if the ECP is notapproved?

76


77/91


78/91

Change Cost

Cost in engineering departments (design and drawingrevision)

Cost in production engineering (Route Cards, tools)

Purchasing & Manufacturing Cost

Cost of change implementing at the customer

Cost includes working hours and materials Change Validity

From which point in time a S/N change is implemented, andwhere (production line, storage, maintenance, ILS)

Change Priority

Change Priority is determined by Project Manager orCustomer

78


79/91


80/91

By Revision Letter Engineerings preference

By Dates

Do not use before, do not use after

Other methods (needs)

Use to depletion of old part

Lot (batch) Number

Project (contract) Number

Customer Number Purchase Order Number

Serial Number

Ef fec t i v i t y o f Chan ge

80


81/91

How should the ECN timing be dealt with?

If high priority: Stop work and fix The sun will not set before preliminary action is taken

Otherwise:

Define Effectivity and schedule into the manufacturing,

planning and execution process: Plan for least disruption and part obsolescence

No more than 2-3 working days until preliminaryrelease

Aggregate and hold for product upgrade

Batch release no less often than quarterly

81


82/91


1 0 . Con f ig u r a t ion Man agem en t Tools

CM Systems Relationship


83/91

Ecad

PLM/PDM

SystemsItems

BOM

ECO'S

Logistic System

ERPInventory

Orders

Finance

Mcad

Docs

Software

PLM Product Lifecycle ManagementPDM Product Data ManagementERP- Enterprise Resources Plann ingEcad Electronics Computer Aided DesignMcad Mechanics Computer Aided Design

y p

83


84/91

Implementation of Configuration Management

requires use of a computerized system which canbe simple or comprehensive depending on the typeand size of organization.

Usually the CM should be accomplished usinginformation management systems.

Many organizations use ERP & PDM systems:

The ERP system manages logistic objects: stock,orders, human resources, finance... (examples:

Oracle Applications, SAP, Priority) The PDM system manages engineering objects:

Items, BOM, ECOs... (examples: Teamcenter, Agile,Enovia)

84


85/91

Ecad & Mcad systems usually have someconfiguration tools but in most of the organizations

the configuration management is managed in thePDM.

Usually there are interfaces between the systems.The ERP system has interfaces with the PDM in order

to transfer items & BOM. Ecad & Mcad systems have interfaces with the PDM

in order to transfer the documentation files.

Software configuration systems usually don't have

interfaces with other systems. Softwareconfiguration is managed using tools like Clearcase &Clearquest. The software files which are needed forproduction are transferred to the PDM system.

85


86/91


1 1 . Su m m ar y


87/91


88/91

A disciplined CM process ensures that productsconform to their requirements and are identified and

documented in sufficient detail to support the productlife cycle.

CM assures accurate product configuration informationand enables product interchangeability and safeproduct operation and maintenance to be achieved.

CM implementation requires a balanced and consistentimplementation of CM functions, principles, andpractices throughout the product life cycle. CMfacilitates orderly identification of product attributes

and provides control of product information andproduct changes used to improve capabilities; correctdeficiencies; improve performance, reliability, ormaintainability; extend product life; or reduce cost,risk or liability.

88


89/91


90/91


1 2 . Resou r ces


91/91

AAQG AS9016

Notice of Change (NOC) Requirements

ANSI/EAI 649

National Consensus Standard for Configuration Management

ECSS-M-ST-40

Space Project Management Configuration Management

IAQG 9100

Quality Management System

ISO 10007

Quality Management Guidelines for Configuration Management

MIL HDBK-61A

Configuration Management Guidance MIL-STD-973 (obsolete/but available)

Configuration Management