# Engineering Change Management Maturity Assessment > Source: https://netray.co/tools/engineering-change-management-maturity-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten-question self-assessment that scores how controlled your engineering change process is and gives practical next steps for your score band. ## Category engineering-plm ## Audience - Engineering manager - Operations manager - Configuration manager ## Tool **Kind:** assessment **Questions:** #### How are engineering changes requested and recorded? **Help:** Think about the last five changes. **Options:** ##### Email, chat or verbal requests **Score:** 0 ##### A spreadsheet or shared form **Score:** 1 ##### A standard form with numbering, stored centrally **Score:** 2 ##### A workflow tool with numbering, status and audit trail **Score:** 3 #### How is the impact of a change analysed? **Options:** ##### The requester judges it **Score:** 0 ##### Engineering checks the BOM only **Score:** 1 ##### Where-used, stock, orders and suppliers are checked by hand **Score:** 2 ##### Impact is generated from system data and reviewed by a board **Score:** 3 #### How are changes classified and approved? **Options:** ##### No classes, whoever is available signs **Score:** 0 ##### Informal approval by engineering lead **Score:** 1 ##### Defined classes with a signature matrix **Score:** 2 ##### Defined classes, routed approvals and customer approval where required **Score:** 3 #### How is effectivity defined? **Options:** ##### Not stated, people start when they hear **Score:** 0 ##### Stated in text, such as next build **Score:** 1 ##### A date, lot or serial is set on most changes **Score:** 2 ##### Effectivity is mandatory and carried into the ERP structure **Score:** 3 #### How is existing stock dispositioned? **Options:** ##### Handled when someone notices **Score:** 0 ##### Planner decides after release **Score:** 1 ##### Disposition is on the change form **Score:** 2 ##### Disposition with quantity and value is decided before approval **Score:** 3 #### How do changes reach the ERP and the shop floor? **Options:** ##### Manual updates, often late **Score:** 0 ##### Manual updates with a checklist **Score:** 1 ##### Planned updates with a named owner and a notice to the floor **Score:** 2 ##### Integrated PLM to ERP release with verification of results **Score:** 3 #### How are suppliers told about changes? **Options:** ##### They find out from the new drawing or order **Score:** 0 ##### Buyer calls or emails when remembered **Score:** 1 ##### Written notice with revision and effectivity **Score:** 2 ##### Notice with acknowledgement tracked and first article requested **Score:** 3 #### How is the change verified after cut-in? **Options:** ##### It is not **Score:** 0 ##### Operators report problems if they occur **Score:** 1 ##### First units are inspected against the new revision **Score:** 2 ##### Verification, cost versus estimate and closure review are recorded **Score:** 3 #### What do you measure about changes? **Options:** ##### Nothing **Score:** 0 ##### Count of changes **Score:** 1 ##### Cycle time and backlog **Score:** 2 ##### Cycle time, rework of changes, cost and escapes reviewed regularly **Score:** 3 #### How are old revisions kept from use? **Options:** ##### Old files remain accessible everywhere **Score:** 0 ##### Files are moved by hand **Score:** 1 ##### Superseded status is applied and controlled copies are used **Score:** 2 ##### System controls access and the shop floor sees only released revisions **Score:** 3 **Bands:** #### Ad hoc **Min:** 0 **Max:** 34 **Verdict:** Changes are handled by individuals and mistakes are likely to reach production. **Recommendations:** - Create one change form with a number, owner, reason and approver list - Require a where-used check on every change - Add stock disposition and effectivity as mandatory fields - Hold a short weekly change review #### Developing **Min:** 35 **Max:** 59 **Verdict:** A process exists but depends on people remembering steps. **Recommendations:** - Define change classes and a signature matrix - Use a checklist for implementation and closure - Send written notices to suppliers and the shop floor - Start tracking cycle time and open changes #### Controlled **Min:** 60 **Max:** 79 **Verdict:** The process is defined and mostly followed, with room to remove manual steps. **Recommendations:** - Generate impact reports from ERP data instead of by hand - Verify ERP updates after release against the approved change - Track change cost versus estimate - Review change escapes and fix their root causes #### Managed **Min:** 80 **Max:** 100 **Verdict:** Change control is integrated and measured. **Recommendations:** - Keep reviewing metrics and trends each quarter - Audit a sample of closed changes for completeness - Look at lead time reduction through earlier supplier involvement - Share the process with sister sites to align practices ## Content **Intro:** Engineering change is where design, purchasing, planning, quality and the floor all meet. Weak control shows up as scrap, wrong-revision builds and customer escapes. This ten-question self-assessment gives a quick read on where your process is and what to fix first. **Sections:** #### How to use the assessment **Body:** Answer based on how the last several changes were actually handled, not how your procedure says they should be. Ask a planner and a shop supervisor to answer separately, since they often see gaps that engineering does not. Compare the scores. A large spread between roles usually points to a communication gap, not a tool gap. **Bullets:** - Use real examples from recent changes - Score honestly; a low score is useful information - Re-run it after six months to see movement #### What the score means **Body:** The score is the sum of option points as a percentage of the maximum. Bands run from ad hoc to managed. The questions follow the life of a change: request, impact analysis, approval, effectivity, stock disposition, implementation, supplier communication, verification, measurement and control of old revisions. They reflect expectations in quality systems such as ISO 9001 and AS9100 for controlling and verifying changes, but this is a self-assessment, not an audit. #### Common mistakes **Body:** Teams often buy a PLM tool hoping to fix a process problem. Software helps with routing, audit trail and integration, but unclear effectivity, missing stock decisions and absent supplier notice remain problems if no one owns them. Start with the lowest scoring questions, assign owners, and fix the process on paper before automating it. **Cta:** Netray can discuss how ERP data can feed change impact reports and where AI assisted checks may help. We are happy to review your results with you. **Faq:** #### Is this assessment an audit? **Answer:** No. It is a quick self-assessment for internal use. It does not certify compliance with ISO 9001, AS9100 or any other standard, but it points to gaps worth discussing in a management or process review. #### How often should we run it? **Answer:** Once to set a baseline and then every six to twelve months, or after a significant escape or system change. Keep the answers so you can compare trends. #### Do we need PLM software to score well? **Answer:** Not necessarily. A disciplined process with a standard form, a checklist and ERP reports can score well. PLM mainly helps with workflow, audit trail and keeping design and ERP data in step. #### Which question should we fix first? **Answer:** Start with impact analysis and stock disposition, since gaps there lead directly to scrap and wrong-revision use. Then address effectivity, supplier notice and verification. ## Search terms engineering change management assessment, ECO process maturity, engineering change process audit, change control maturity model, PLM change management self assessment, ECN process improvement, configuration management maturity, engineering change KPIs --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json