Design/Change Control Form Example and Advice

D

darrock

#1
Hi all,

I am currently reviewing our company "Design/Change Control" process. Currently, changes to a product or process go through one form - all the orginator of the form needs to do is describe the proposed change and write a validation protocol and QA seem to do the rest!

After some intial consultations with individuals that use the system, I have found that they don't really like the form & they don't understand it.

Has anyone got any examples of design changes for products once they have been transferred into production? I would very much appreciate it!

Thanks
 
Elsmar Forum Sponsor

Crusader

Trusted Information Resource
#2
Re: Design/Change Control Form

Hi all,

I am currently reviewing our company "Design/Change Control" process. Currently, changes to a product or process go through one form - all the orginator of the form needs to do is describe the proposed change and write a validation protocol and QA seem to do the rest!

After some intial consultations with individuals that use the system, I have found that they don't really like the form & they don't understand it.

Has anyone got any examples of design changes for products once they have been transferred into production? I would very much appreciate it!

Thanks

I removed the form - it is not structured for the medical field and migh tbe confusing to some.
 
Last edited:

Ajit Basrur

Staff member
Admin
#3
Re: Design/Change Control Form

Hi all,

I am currently reviewing our company "Design/Change Control" process. Currently, changes to a product or process go through one form - all the orginator of the form needs to do is describe the proposed change and write a validation protocol and QA seem to do the rest!

After some intial consultations with individuals that use the system, I have found that they don't really like the form & they don't understand it.

Has anyone got any examples of design changes for products once they have been transferred into production? I would very much appreciate it!

Thanks
If you would like to share your form, we covers could comment and give you suggestions for improvement :)

Btw, your phrase "QA seem to do the rest" sounds harsh - Quality is everybody's responsibility and everyone should share. All activities relating to Change Proposal should be handled by a team comprising mainly of Engg, Operations and Quality.

Here is our ECR Form. QA has nothing to do with it - Only Engineering can review & approve. Anyone can submit it though.
:bigwave:
Thanks for sharing the form. You probably would like to include Quality approval in the approval process.
 

Crusader

Trusted Information Resource
#4
Re: Design/Change Control Form

Thanks for sharing the form. You probably would like to include Quality approval in the approval process.
Like I said, Quality has no authority on Engineering changes. Only Engineering can approve a change.
Edit: Form removed. Sorry, my form is for the ISO 9001 system, not medical. My mistake.
 
Last edited:
T

Teri - 2011

#5
I am going to try and attach our sample.

We have quality, materials and engineering sign off, that they are aware of the upcoming change, then once all paperwork, ppap, P.O.'s etc...etc.. are completed they must sign off again.

We had to do this, because materials was complaining, "I was never told the material was changing (just an example)".
Of course all this is discussed during APQP, however, the signature holds each department accountable for their requirements.
 

Attachments

D

ddunn

#7
The review and approval of an ECO should not be a technical review of the change (that's an engineering function) but should be an implementation review. Proper planning of change implementation is where most companies fall down. Attached is the ECO form and CCB process is use.
 

Attachments

T

Teri - 2011

#8
Our Engineering does all of that. That's why QA is not included and is not applicable in our case. There is extensive research prior to a change.
Then I am confused to what you are looking for. You said what you have doesn't appear to be working. But if your engineering does everything, why do you need a new form? Does your engineering change all the necessary paperwork (operator instructions, specs, PPAP, etc)?
Does engineering order the material, if the change is a material change?

I agree, changes START in engineering and probably get final approval there, however, the implementation process into production is usually when things get messed up, someone, somewhere drops the ball, or doesn't get informed of the change.
 
T

Teri - 2011

#9
Sorry crusader,,, yes confused you with orginial poster:truce:. But it is a Monday afterall:notme:!
 

Jim Wynne

Staff member
Admin
#10
The review and approval of an ECO should not be a technical review of the change (that's an engineering function) but should be an implementation review. Proper planning of change implementation is where most companies fall down. Attached is the ECO form and CCB process
It depends on what is considered the purpose of the ECO form, not the process. Engineering changes usually follow this path:
  1. There is a perceived need for a change, perhaps to add functionality, improve existing functions, or to correct design errors.
  2. The rationale for the change is documented or otherwise made known.
  3. The idea is reviewed, and a decision is made as to whether or not the change should be implemented.
  4. If a decision is made to implement the change, its implications are considered, including any necessary tooling and other process changes, disposition of existing stock, updating of process and user documentation, the timing of implementation, etc.
  5. Formal documentation, including information regarding all of the first four steps, is drafted. Note that the documentation should begin with step 1, and is updated as the ensuing steps occur.
At this point, there needs to be some formal notification of the change to the affected parties. That's what we generally think of as an ECO, or ECN. In some companies, there are three documents: The initial request for a change (ECR), the official approval of implementation (ECO) and notice to affected parties (ECN). What matters in all of this is that (A) the impetus and rationale for the change is documented; (B) the implications of the change are understood and documented and properly implemented and (C) affected parties are duly notified of what's going on. There should be a clear trail from the initial idea to the actual implementation of the change, but how it's documented is a matter of choice and preference.
 
Thread starter Similar threads Forum Replies Date
A UDI and Design Controls - Labeling change via the Design Control process 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
A Design/Change Control Procedure - How to cope with Changes during Development? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 26
T Design and Development: 7.1.4 - Change Control - What is a good change control system Design and Development of Products and Processes 7
J Significant change related to design and intended use EU Medical Device Regulations 3
U NOC - What is considered a "design change" EU Medical Device Regulations 5
S Requirement to Conduct New Shelf-life Testing? (re-do testing for design change) EU Medical Device Regulations 3
S MDR Delay - MDD design Change? (before new MDR DOA) EU Medical Device Regulations 8
H New 510K VS Documents about design change. Other US Medical Device Regulations 1
R Explain what "design change" is to people new to the industry ISO 13485:2016 - Medical Device Quality Management Systems 9
T Closing out CAR while waiting for design change Nonconformance and Corrective Action 12
L Managing design projects: New Medical Device Project or Change Design and Development of Products and Processes 1
T How to Document Risk Effects on Design Change(s) ISO 14971 - Medical Device Risk Management 3
I Another design change or new product? IVD device ISO 13485:2016 - Medical Device Quality Management Systems 6
S Engineering change order versus a design change request ISO 13485:2016 - Medical Device Quality Management Systems 1
Q PPAP - How to determine the "Design Record Change Level" APQP and PPAP 2
S Verification and Validation of Post Market Design Change Design and Development of Products and Processes 2
A Reporting of Design Changes (Color Change Only) EU Medical Device Regulations 5
Q 510K Checklist that considers every Design Change 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 8
A Medical Device DHF (Design History File) - One per Design Change? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 17
V Product Evaluation Requirements for Change in Manufacturing Facility/Change in Design 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 12
S Design Change vs. Intellectual Property Design and Development of Products and Processes 9
J What should be included in the Design Change Document 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
S External or Internal Design Change and Responsibilities Document Control Systems, Procedures, Forms and Templates 3
C Design Change needed for Changing an Angle in existing Product from 15-25 degrees? ISO 13485:2016 - Medical Device Quality Management Systems 11
S Design Change Drawing Reviews and Customer Approval Process Document Control Systems, Procedures, Forms and Templates 5
A Design Review OR Design Change - Software development company ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 9
R Procedure for "Customer Acceptance of a design or process change" Design and Development of Products and Processes 12
B Severity Reduction by Product or Process Design Change? Seeking Good Example Design and Development of Products and Processes 2
S FMEA Severity Rating - Will a Process Design Change also Change the Severity Rating? FMEA and Control Plans 21
L Outsourced Design with Internal Design Change Design and Development of Products and Processes 2
J When does an engineering change become a design change? Design and Development of Products and Processes 7
A Engineering change validation - Companies that have no design responsibility Design and Development of Products and Processes 5
R Is design change applicable (7.3.7)? Design and Development of Products and Processes 2
M Reducing both Detection and Occurance in a Design FMEA WITHOUT a Design Change FMEA and Control Plans 8
N What are the VDA requirements for Design change? VDA Standards - Germany's Automotive Standards 2
K FMEA - Reduce Occurance of a Failure (or its cause) by Design Change FMEA and Control Plans 6
DuncanGibbons Section 8.3 relevant for design organisations AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 2
P DFMEA - Machinery Design Best Practices FMEA and Control Plans 0
R Is a FAIR required on parts that we design? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
U API Spec Q1 - 5.6.1.2 C (3) - Design software Oil and Gas Industry Standards and Regulations 3
N Example for design and development planning,input,output,review,verification,validation and transfer Misc. Quality Assurance and Business Systems Related Topics 4
A 8.6 Release of products and services, 8.3 Design and development - evidence required ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 9
C Stress / Challenge Conditions for Design Verification Testing to Reduce Sample Size 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 11
S Traceability of requirements to design and risk Design and Development of Products and Processes 3
Q PPT used as Design Review ISO 13485:2016 - Medical Device Quality Management Systems 3
D Design Verification Sample Size vs Repeats Statistical Analysis Tools, Techniques and SPC 9
A Design and development procedure for API Spec Q2 Oil and Gas Industry Standards and Regulations 6
D Design controls - Inputs, outputs, V&V, DHF, DMR ISO 13485:2016 - Medical Device Quality Management Systems 10
LostLouie Manufacturer divorced from Design process, is he justified in design process deficiencies? ISO 13485:2016 - Medical Device Quality Management Systems 9
R DFA & DFM - Examples for Design for assembly and design for manufacturability Lean in Manufacturing and Service Industries 2

Similar threads

Top Bottom