Chip lifecycle / Change and decision flows / Engineering change request and impact assessment

Engineering change request and impact assessment

The common front door for any change to something that has been baselined: a specification, a design database, a test program, a package drawing, a process recipe or a released document. A change request records what is to change and why, the owners of every affected area assess the impact, and a change board approves, rejects or defers it before anyone edits the baseline. It starts as soon as a frozen item needs to change, whoever spots the need.

Engineering change request

A request is raised and screened, every affected owner assesses impact, the change board decides, and an approved change is made, verified and closed against the baseline.

Phase

Raise and screenAssess impactDecideImplement and close

Requester

Change coordination

Affected owners

Change board

Raise the change request

RequesterChange request

?Complete and in scope?

Log, classify and assign owners

Change coordinatorChange log entry

Assess impact in each area

Area ownersImpact assessment

Propose options and a plan

Lead engineerImplementation plan

Review at the change board

Board chairBoard agenda

?Approve the change?

Record rejection or deferral

Change coordinatorDecision record

Implement and verify

Area ownersVerification evidence

Close and update the baseline

Configuration managerUpdated baselineClosed change record

Show this chart as a list

Raise the change request (Requester) by Requester, producing Change request. Next: Complete and in scope?
Complete and in scope? (Change coordination). Next: if yes, Log, classify and assign owners; if no, Raise the change request
Log, classify and assign owners (Change coordination) by Change coordinator, producing Change log entry. Next: Assess impact in each area
Assess impact in each area (Affected owners) by Area owners, producing Impact assessment. Next: Propose options and a plan
Propose options and a plan (Affected owners) by Lead engineer, producing Implementation plan. Next: Review at the change board
Review at the change board (Change board) by Board chair, producing Board agenda. Next: Approve the change?
Approve the change? (Change board). Next: if yes, Implement and verify; if no, Record rejection or deferral
Record rejection or deferral (Change coordination) by Change coordinator, producing Decision record
Implement and verify (Affected owners) by Area owners, producing Verification evidence. Next: Close and update the baseline
Close and update the baseline (Change coordination) by Configuration manager, producing Updated baseline, Closed change record

Register or sign in to read on

The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.