Post Midterm Lecture configuration management

7/27/2019 Post Midterm Lecture configuration management

1/47

CONFIGURATION

MANAGEMENT

Configuration Change Control

Post-Midterm Lectures

Ms. Arlenie R. Salamat


2/47

Recap

What are Configuration Items (CIs)

Choosing the CIs to be taken in the

Configuration Management

Configuration change control for each CI Baseline

Authority

Backward and Forward traces

Etc.


3/47

Configuration Change Control

Configuration management shouldprovide visibility of the products

configuration through recording

specific data in order to establish andmaintain integrity of the product

described by the configuration

throughout its complete life cycle


4/47


5/47

Class Objectives:

Understand the purpose of the configurationcontrol function

Recall the difference between engineeringchanges and configuration departures

Understand and differentiate ConfigurationControl Board (CCB) and Change Review Board(CRB)

Know and understand the classification andcategorization of engineering changes andconfiguration departures

Recall the processes in engineering changes andconfiguration departures


6/47

Purpose and benefit of the

Configuration Control Function

Enable change decisions to be based onknowledge of complete change impact

Limit changes to those which are necessaryor offer significant benefit

Facilitate evaluation of cost, savings, andtrade-offs

Ensure customer interests are considered

Provide orderly communication of change

information


7/47

Purpose cont

Preserve configuration control at productinterfaces

Maintain and control a current configurationbaseline

Maintain consistency between product anddocumentation

Document and limit variances (what arevariances again???)

Facilitate continued supportability of the productafter change


8/47

The primary objective of configuration controlis to establish and maintain a systematicchange management process that regulateslife-cycle cost, and:

Allows optimum design and development latitudewith the appropriate degree and depth ofconfiguration change control procedures duringthe life-cycle of a system / CI

Provides efficient processing and implementationof configuration changes that maintain orenhance operational readiness, supportability,and interchangeability


9/47

Ensures complete, accurate and timelychanges to configuration documentation

maintained under appropriate

configuration control authority

Eliminates unnecessary change

proliferation


10/47

CHANGE AUTHORITIES

Configuration Control Board(CCB)and Change Review Board (CRB)


11/47

Configuration Control Board

The CCB is the sole authority for dispositionof the project configuration documentation

The CCB is chaired by the project manager

or his designated representative

The CCB authenticates configurationdocumentation, establishes baselines,approves or disapproves engineering changeproposals, deviations and waivers andauthorizes the minutes of completedtechnical and configuration reviews


12/47

Change Review Board

The CRB is usually preceding theCCB in order to limit boarding time of

the CCB while reviewing a change or

departure for its technical effects onthe entire product

The CRB recommends the CCBapproval or disapproval of a change

proposal or departure request on the

grounds of a technical review report


13/47


Participation

Beside configuration management, engineeringand quality assurance as permanent CCBparticipants, all other project disciplines assignrepresentatives as called for by the CCB

chairman. They may be assigned from:

Manufacturing

Test Engineering

Purchasing

Logistics Finance

Contracts

Disciplined specialists (as required)

Supplier(s)


14/47


Activities Change effects analysis

Technical feasibility

Effects on CI / higher level CI(s)

Implementation schedule

Cost Production resources

Change categorization Final concurrence in the classification of change

Reviewing the type of change (product evolution,enhancement, or document update)

Agreement in the priority of change (emergency,urgent, or routine)


15/47

CCB Activities cont

Change implementation effectivity(cut-in point planning) and change

correlation with third parties (e.g.,

other projects)

The CCB is usually not a voting body -

the chairman makes final decision


16/47

ENGINEERING CHANGES

VS. CONFIGURATION

DEPARTURES


17/47

Engineering Changes

Engineering changes are the processof changing configuration

documentation for functional

(specifications) and physical(drawings) attributes, including all

associated ancillary documentation


18/47

Reasons for Engineering

Changes to provide new capabilities desired by the

customer

to enhance product support

to insert new technology

to effect product improvements

to correct product defects or deficiencies

to correct problems and prevent recurrence

to eliminate safety hazard conditions

to implement preplanned product improvements

to reduce production costs / improve productionefficiency

to prevent schedule slippage, or just

administrative changes to the drawing /

document

C fi ti D t


19/47

Configuration Departures

(Variances) - Deviations and

Waivers Deviations

a written authorization, granted prior to

the manufacture of an item, to depart fromparticular requirements or the design ofan items approved configurationdocumentation for a declared number ofunits or a scheduled period of time.

Deviations do not cause a correspondingrevision of the configuration

documentation governing the departingattribute.


20/47

Waivers a written authorization to accept an item,

which, during manufacture, test or quality

inspection, or having been submitted for

customer inspection or acceptance, is found

to depart from design or manufacturing

process requirements, but nevertheless is

considered suitable for use-as-is or after

repair by an approved method. Waiver do not

cause a corresponding revision of the

configuration documentation governing the

departing attribute.


21/47

Classifying Engineering

Changes


22/47

Prioritizing Engineering

Changes Urgent

To effect a change which, if not accomplishedexpeditiously, may seriously compromise the missioneffectiveness of deployed equipment or software

To correct a potentially hazardous condition, theuncorrected existence of which could result in injuryto personnel or damage to equipment. (A potentiallyhazardous condition compromises safety andembodies risk, but within reasonable limits, permitscontinued use of the affected item, provided theoperator has been informed of the hazard andappropriate precautions have been defined anddistributed to the user)


23/47

Prioritizing cont (URGENT)

To meet significant contractual requirements(for example, when lead time will necessitateslipping approved production or deploymentschedules if the change was not

incorporated)

To effect an interface change which, ifdelayed, would cause a schedule slippage orincrease cost

To effect a significant net life-cycle costsavings to the tasking activity, as defined inthe contract, where expedited processing ofthe change will be a major factor in realizing


24/47

Prioritizing cont (URGENT)

To correct a condition causing unusableoutput information that is critical to mission

accomplishment.

To correct critical CI files that are being

degraded

To effect a change in operationalcharacteristics to implement a new or

changed regulatory requirement with

stringent completion date requirements

issued by an authority higher than that of the


25/47

Prioritizing cont

RoutineA routine priority is assigned to an

ECP/SCP when emergency or urgent

implementation is not applicable,required, or justifiable.


26/47

Prioritizing cont

Emergency To effect a change in operational

characteristics which, if not accomplishedwithout delay, may seriously compromiseproject security

To correct a hazardous condition which mayresult in fatal or serious injury to personnel orin extensive damage or destruction of

equipment. (A hazardous condition usuallywill require withdrawing the item from servicetemporarily, or suspension of the itemoperation, or discontinuance of further testingor development pending resolution of the

condition); or


27/47

Prioritizing

cont(EMERGENCY) To correct a system halt (abnormal termination) in

the production environment such that mission

accomplishment is prohibited.


28/47

Designating Waiver

Product nonconformance for which a waiverrequests permission to use are distinguishedby defect of the product

Minor defect; a departure from establishedengineering and production standards havinglittle or no effect on the product usability

Major defect; a defect that is likely to result initem failure or materially reduces product

usability

Critical defect; a defect that, judgment andexperience indicate, is likely to result in unsafeconditions for individuals using, maintaining, ordepending upon the product


29/47

Initiating an engineering change

problem by reporting


30/47

Engineering/ Software Change

Cycle Issuing a change request (with or without problemreport)

Determination for the need of the requestedchange by analysis of the total impact

Preparation of the engineering / software change

proposal Disposition by the CRB and CCB

Customer approval / disapproval

CCB orders the change for incorporation /implementation

Incorporation in configuration documentation

Incorporation in product / software changeimplementation and incorporation

Verification of change accomplishment


31/47

Typical Change Documentation

in Engineering Change Process


32/47

The Change Implementation

Process Formal involvement of CM in tracking and recording the

change implementation is a relatively new CMresponsibility

A controlled process is required because complexchanges require many individual actions involvingdifferent organizations and thus, require scheduling,coordination, tracking and reporting

CM does not direct the implementation of a change.The direction is provided by the CCB through anengineering (or software) change order

All organizations contributing to the changeincorporation / implementation effort are tasked toprovide cooperative schedules at the CCB

Verifying the Incorporation of


33/47

Verifying the Incorporation of

Engineering Changes and

Deviations Production planning receives the

approved change documentation ordeviation under cover of an engineering

change order

Quality Control verifies the incorporationand issues an as-built record

CM compares the as-built record with theengineering change and closes the

change action


34/47

A Generic Engineering Change

or Deviation Process


35/47

Requesting Deviations and

Waivers To deliver a product with a known configurationdeparture, defect or parts shortage, customer

authorization is usually required. A request fordeviation or waiver is utilized for obtainingapproval

Deviations and waivers are not engineering orsoftware changes and do not alter engineeringdrawings or software documentation Deviation: A planned nonconformance to

performance, design, or verification requirements, orthe products physical attributes

Waiver: An unplanned nonconformance to theproduct design or its manufacturing processrequirements


36/47

Requesting cont

Deviations and waivers are usuallydesignated minor, major and critical in

respect to their effects. In space projects,

critical deviations and waivers are generally

not permitted since they do affect safety

factors by their definition

Deviations and waivers are occasionally

also referred to as variances,derogation, concessions, or production

permits (in the UK for deviations)


37/47

Processing a Request for

Deviation Except for deviations requested during

the development phase, themanufacturing planner is one of thefirst to be aware of the need todeviate; e.g., when scheduled receipt of material or parts is in

delay

an in-line process such as for coating orheat treatment is out-of-service

inoperable or unavailable test equipmentprevents the conduct of required tests


38/47

Processing (DEVIATION) cont

An alternative material, part or process isselected and a deviation is proposed fortemporary application Engineering and manufacturing normally

have instant access to acceptablealternatives

The CRB / CCB evaluates the proposed

deviation to investigate its suitability of the substitution

a scheduled return to the as-required oras-designed condition


39/47

Processing (DEVIATION) cont

The CRB / CCB evaluates theproposed deviation to investigate

its suitability of the substitution

a scheduled return to the as-required oras-designed condition

the specific identity, such as the serial

number of each affected CI, and the first

unit scheduled for return to normal

proceeding

the appropriate designation as minor,

major (or critical)


40/47

Cont

Note: Commercial producers should notallow major or critical deviations since

their effects on logistics support,

increased risk of product failure, or riskof hazard to the user is unacceptable.

Military customers accept under certain

circumstances major deviations, and

may tolerate the greater risk of a criticaldeviation when strategic conditions

demand the immediate use of the

product (e.g., wartime)


41/47

Cont

After CCB acceptance, the deviation issent to CM. CM obtains deviation

authorization, distributes the deviation

to manufacturing planning orpurchasing, and records the deviation


42/47

Processing a Request for

Waivers In most productions, items receive an in-process quality inspection for early detection

of a nonconformance prior to quality buy-offfor next step integration or delivery

Nonconformances to the products physicalattributes or its manufacturing processes areidentified during manufacture, or as a resultof test failure assessment

Manufacturing / receiving inspectionpersonnel or test technicians use often theproblem report to document briefly a possiblediscrepancy or anomaly


43/47


44/47

Processing (WAIVER) cont

The MRB decision may result in return tosupplier, scrap, rework, repair, or use-as-is

Final disposition of minor defects can be

determined by the MRB and be recorded as aminor waiver

There is a significant difference between reworkand repair

After rework, the product complies with theapproved product design as disclosed by thegoverning engineering drawing


45/47

Processing (WAIVER) cont

A repaired item is functionally satisfactorily,but will never conform exactly to the drawing

Afterrepair, no other defect than minorshould be accepted

MRB decisions for use-as-is concerningmaterial with a major defect need to beelevated to CM for preparation of a request

for major waiver

According CRB / CCB processing for gainingcustomer permission granted is the usualcase


46/47

A Generic Waiver Process


47/47

Date post:	14-Apr-2018
Category:	Documents
Upload:	aidan-cervantes
View:	223 times
Download:	0 times

Post Midterm Lecture configuration management

Documents