Engineering gets a brilliant idea: substitute Component A with Component B—better performance, lower cost, faster supplier lead time. Win-win-win. The engineer updates the CAD file and sends an email to Production: "Use Component B going forward."
What could possibly go wrong?
Purchasing has 500 units of Component A in stock and 1,000 more on order (didn't receive the email). Estimating is quoting new jobs using Component A pricing (doesn't know about the change). Quality has inspection criteria for Component A (Component B requires different checks). Finance's standard cost reflects Component A (costing now systematically wrong). The production supervisor who received the email is on holiday (replacement doesn't know about the change).
One engineering change, six departments confused, countless opportunities for error. This scenario plays out in New Zealand manufacturing businesses daily, because engineering changes are treated as simple notifications rather than coordinated processes requiring systematic management.
Engineering change is inevitable—products improve, suppliers change, regulations update, costs optimise. The question isn't whether to make changes, but how to manage them without creating production chaos, quality risk, and cost confusion.
Why Engineering Changes Happen (and Will Continue)
Understanding why changes occur helps design effective management processes. Engineering changes aren't failures—they're essential to continuous improvement and market competitiveness.
Product Improvement
Engineering's job is continuous improvement. Field feedback reveals opportunities to enhance reliability. Testing identifies components that could be upgraded. Design reviews find efficiency gains. These improvements make products better—refusing them means stagnation.
One Taranaki agricultural equipment manufacturer averages 15-20 engineering changes monthly across their product range. Not because original designs were wrong, but because continuous improvement is a cultural commitment. Their products are meaningfully better than five years ago because engineering never stops iterating and responding to real-world performance data.
Supply Chain Dynamics
Supplier discontinues a component. Original specification no longer available. New supplier offers better pricing but slightly different form factor. Import tariffs make current component uneconomical. Supply chain volatility necessitates engineering changes regardless of original design quality.
The COVID pandemic and subsequent supply disruptions taught manufacturers that supply chain resilience requires engineering flexibility. Component substitution capability isn't nice-to-have—it's business continuity requirement. Manufacturers who could rapidly qualify alternative components maintained production whilst competitors faced lengthy shutdowns.
Regulatory and Standards Updates
Safety standards evolve. Environmental regulations change. Industry certifications require specific materials or processes. Compliance mandates engineering changes on existing designs even when current products are performing well in the field.
Medical device and industrial equipment manufacturers face ongoing regulatory change. Engineering change control becomes compliance documentation requirement, not just internal process improvement. Auditors expect complete traceability showing what changed, when, why, and how the change was validated.
Cost Optimisation
Finance identifies high-cost components. Engineering investigates alternatives. Sourcing finds lower-cost suppliers with equivalent specifications. Design-for-manufacturability reviews identify simplification opportunities. Cost pressures drive engineering changes that improve profitability without sacrificing quality or performance.
Lean manufacturing philosophy emphasises continuous incremental improvement. Engineering changes are the vehicle for delivering these improvements—reducing material waste, simplifying assembly processes, eliminating non-value-adding steps.
The Chaos of Informal Change Management
Without systematic change control, even well-intentioned changes create serious operational problems that compound across departments and time.
Version Ambiguity
Customer returns product for warranty repair. Technician needs replacement parts. Critical question: Which BOM version was used in original manufacturing? Without formal versioning and effective dating:
- Production might have mixed old and new components during inventory transition
- Documentation shows one version, actual build used another
- Can't definitively identify what was built when
- Warranty claim becomes archaeological excavation requiring days of investigation
Traceability requires knowing exactly what was built. Informal change management makes this impossible. One Wellington medical device manufacturer discovered a component defect three months post-production. Without formal BOM versioning and change tracking, they couldn't reliably identify which units contained the suspect component, forcing a broader recall than necessary.
Cross-Department Misalignment
Engineering changes a BOM. Who needs to know? Everyone:
- Purchasing: Stop ordering old component, start ordering new one (avoid obsolete inventory)
- Estimating: Update quotes to reflect new costs (maintain margin accuracy)
- Production: Update work instructions and tooling (prevent confusion on shop floor)
- Quality: Modify inspection criteria (ensure appropriate testing)
- Finance: Adjust standard costs (accurate job costing)
- Service: Update spare parts lists and repair procedures (support installed base)
Email notification isn't sufficient. Some people miss it. Others read it but forget to act. Information doesn't automatically translate to systematic action across all affected functions. The coordination burden becomes overwhelming as change frequency increases.
MYOB Acumatica's ECN (Engineering Change Notice) workflow routes changes to every affected role, requires acknowledgment, tracks implementation completion. Engineering proposes the change, the system ensures coordinated implementation across all departments.
Inventory Management Confusion
Switching from Component A to Component B creates immediate inventory challenges:
- 500 units of Component A currently in stock
- 1,000 units on inbound purchase order
- Do we consume old inventory first? (minimise waste and write-offs)
- Do we switch immediately? (benefit from improvement now)
- Do we allow mixed builds? (some products with A, some with B)
- What happens with obsolete inventory? (scrap, return to supplier, find alternative use)
Without formal policy tied to the change control process, each supervisor makes ad-hoc decisions. Consistency disappears, traceability suffers, cost impact becomes unclear. Finance discovers $45,000 in obsolete inventory three months later, but can't determine which engineering changes caused the obsolescence.
Cost Impact Blindness
Engineering changes a component, intending to reduce cost. But total cost impact involves multiple factors often overlooked in informal processes:
- New component unit price (might be lower on paper)
- Inventory obsolescence (old stock now unusable, must be written off)
- Tooling or fixture modification (new component has different form factor)
- Supplier change costs (new qualification, sample testing, setup fees)
- Learning curve (operators unfamiliar with new component, initial efficiency loss)
Engineering sees component cost reduction. Finance sees total cost increase. Without cross-functional review during the change process, good intentions create bad outcomes. One Auckland electronics manufacturer implemented a "cost-saving" component change that reduced piece price by $2.40 but created $18,000 in obsolete inventory and $6,500 in fixture modifications—net cost increase of $22,100.
Regulatory and Quality Implications
For manufacturers in regulated industries or with ISO certification, informal change control creates significant compliance risk that can result in audit findings, customer issues, or regulatory consequences.
Traceability Requirements
Medical device regulations (TGA in Australia/NZ, FDA globally, MDR in Europe) require complete traceability: which components, which suppliers, which lots were used in each manufactured device. This enables field corrective actions when component defects are discovered months or years after production.
Engineering change without formal documentation breaks traceability. You can't prove what was built with which BOM version. Regulatory audit findings result. Potential product recalls expand because you can't reliably identify affected serial numbers. Customer confidence erodes when you can't answer basic questions about product composition.
Design History File Integrity
Regulated manufacturers maintain Design History Files (DHF) documenting product evolution. Every change must be documented with:
- Clear description and reason for change
- Change implementation date and effective serial/lot numbers
- Affected products and assemblies
- Verification and validation testing results demonstrating change doesn't create new risks
- Formal approval signatures from appropriate stakeholders
Spreadsheet-based change tracking creates DHF gaps that auditors increasingly flag. Auditors expect electronic change control systems with complete audit trails—not manual logs vulnerable to omission and human error.
Supplier Change Notifications
Suppliers make component changes—material composition, manufacturing process, facility location. Even if the part number remains unchanged, the change might affect your product performance, compliance status, or regulatory approvals.
Formal ECN processes capture supplier-initiated changes, trigger impact review, ensure appropriate response (qualification testing, customer notification, regulatory submission if required). Informal processes miss supplier notifications that arrive via email, creating compliance gaps.
Best Practice Engineering Change Control
Effective ECN isn't bureaucracy—it's systematic coordination that prevents chaos whilst enabling continuous improvement. Leading manufacturers implement structured processes that balance agility with control.
Formal Change Request Process
Anyone can propose changes—engineers, production supervisors, quality managers, customer service representatives. But proposals enter formal workflow rather than ad-hoc email:
- Change request created describing proposed modification and affected items
- Justification documented (cost savings, performance improvement, compliance requirement)
- Affected products and assemblies identified (full where-used analysis)
- Initial impact assessment (inventory implications, tooling requirements, cost analysis)
This creates visibility before implementation. Changes are evaluated against consistent criteria (ROI, risk, urgency) and prioritised systematically rather than first-come-first-served.
MYOB Acumatica's ECN module provides structured change request forms directly linked to affected BOMs. The requester describes the change, attaches supporting documents (revised drawings, supplier quotes, test results), and submits for cross-functional review.
Cross-Functional Review
Engineering changes affect multiple departments. Review workflow ensures all stakeholders evaluate impact to their functional area:
- Engineering: Technical feasibility, testing requirements, design validation
- Operations: Manufacturing process changes, tooling requirements, operator training needs
- Purchasing: Supplier availability, lead times, pricing, contract implications
- Quality: Inspection criteria updates, regulatory implications, customer notification requirements
- Finance: Total cost impact including implementation costs, standard cost updates
- Sales/Service: Customer communication needs, spare parts implications, field service impact
Each reviewer sees the change request, assesses impact to their area, approves or raises concerns that must be addressed. The system tracks all reviews, escalates delays, ensures complete evaluation before approval. No change proceeds until all affected stakeholders have reviewed and approved.
This cross-functional review often identifies issues the original requester didn't consider. One Christchurch metal fabricator's "simple" material change required fixture modifications that Operations identified during review, adding three weeks to implementation timeline but preventing shop floor disruption.
Effective Dating and Phasing
Not all changes should implement immediately. Effective-dating controls precisely when changes become active:
- Immediate: Use new component starting now (critical safety fix or urgent quality issue)
- Date-based: Effective from specific date (planned transition, coordinated with supplier)
- Serial/lot number-based: Effective starting with specific unit number (serial-controlled products)
- Inventory depletion: Use old component until existing stock exhausted, then switch (minimise waste)
MYOB Acumatica's BOM versioning supports all effective-dating methods. Estimating, production planning, and costing automatically use the correct BOM version based on the order date or serial number, eliminating manual coordination.
Effective dating also supports phased implementation across product families. A component might be proven in Product A (immediate implementation) but require additional testing for Product B (delayed implementation), allowing risk management whilst capturing benefits where validated.
Implementation Tracking
Change approved—now what? Implementation requires coordinated actions across multiple departments:
- Purchase orders placed for new components
- Obsolete inventory disposition (scrap, return, alternative use identified)
- Work instruction updates published and distributed
- Operator training completed and documented
- Quality procedure revisions approved and implemented
- Standard costs updated in financial system
- Customer notifications sent where contractually required
ECN workflow includes implementation task lists assigned to specific roles with due dates and dependencies. Quality manager updates inspection procedures. Purchasing expedites new component orders and processes obsolete inventory returns. Finance adjusts standard costs system-wide. The system tracks task completion, preventing incomplete implementation that creates the very confusion change control is designed to prevent.
One Waikato industrial equipment manufacturer tracks average implementation time from approval to complete deployment. This metric helps them understand change management efficiency and identify process bottlenecks requiring improvement.
Documentation and Audit Trail
Every change must be completely documented for traceability, compliance, and institutional knowledge:
- Who requested the change and when
- Business justification (why was this change necessary)
- What changed (detailed before/after comparison)
- When effective (date, serial number, or other trigger)
- Who reviewed and approved (complete approval chain)
- Implementation completion confirmation
- Any issues encountered during implementation
Electronic audit trails satisfy regulatory requirements, support internal quality reviews, and enable continuous improvement analysis. Patterns emerge: Why are changes occurring? Which products have highest change frequency? What categories of changes are most common? This intelligence informs product development, supplier management, and quality improvement initiatives.
Managing Change in Multi-Product Environments
Where components are shared across multiple product lines, change complexity multiplies significantly. Manufacturers need sophisticated tools to manage this complexity without slowing improvement velocity.
Where-Used Analysis
Component X is used in 15 different products. Engineering proposes a change. Critical question: Does this change affect all 15 products, or only some based on their specific application requirements?
Where-used inquiry shows every BOM that includes Component X. Engineering reviews each product, determines change applicability. Some products benefit from the change immediately, others don't (different operating environments, different load conditions, different customer requirements). The ECN can specify precisely which products adopt the change and which remain on the current specification.
Without comprehensive where-used visibility, change impact assessment becomes incomplete guesswork. You might apply changes globally when they're only appropriate for specific products—or worse, miss products that should adopt the change, creating field failures from known issues.
Phased Implementation Across Product Lines
Changes might benefit some products immediately but require additional validation on others due to different regulatory status, operating conditions, or customer specifications:
- Product A: Immediate implementation (field-tested in similar application, proven benefit)
- Product B: Pending validation (qualification testing in progress, different operating environment)
- Product C: Future consideration (lower priority, evaluate after field experience with A and B)
MYOB Acumatica allows BOM-specific effective dates and implementation status. The same component change can have different implementation timing across the product range, enabling risk management whilst capturing benefits where proven.
Customer-Specific Constraints
Some customers specify exact component sources, material grades, or supplier qualifications in their purchase contracts. Engineering changes affecting these specifications require customer approval before implementation on their orders—even if the change is beneficial.
ECN workflow can include customer notification and approval steps for affected customers. The system tracks which customers have approved, which are pending, and which orders can proceed with the change. This prevents contractual violations whilst enabling change implementation for other customers.
One Canterbury aerospace components manufacturer serves both commercial and defence customers. Defence contracts often have stricter change approval requirements. Their ECN system manages different approval workflows based on customer type, ensuring compliance whilst avoiding unnecessary delays for commercial customers.
Configuration Management
Complex products with multiple options and variants create configuration management challenges. Engineering changes might affect:
- Base model only (common platform component)
- Specific options only (unique to certain configurations)
- All configurations (universal component or material)
- Customer-specific configurations (bespoke variants)
Formal change control with configuration visibility ensures changes apply correctly across the variant landscape. One Wellington industrial controls manufacturer offers products with 50+ configuration options. Their ECN system links changes to specific configurations, preventing errors where changes are applied too broadly or too narrowly.
Reporting and Analytics
ECN data reveals patterns that inform strategic decisions:
- Which products have highest change frequency? (design instability requiring review? Complex customer requirements?)
- What drives changes? (cost reduction, quality improvement, supplier issues, regulatory compliance)
- How long from request to implementation? (process efficiency metric, identifies bottlenecks)
- What's the total cost impact of changes? (obsolescence, rework, expediting—often hidden costs)
- Which suppliers generate most changes? (quality issues or proactive improvements?)
Analytics turn change management from administrative task to strategic insight source. One Waikato manufacturer discovered that 60% of their engineering changes were supplier-driven substitutions. This insight led to improved supplier qualification processes and contract terms requiring advance notification.
Change as Competitive Advantage
Engineering change is inevitable in competitive manufacturing. Products must evolve to remain relevant. Suppliers change. Regulations update. Costs must be optimised. Manufacturers who resist change stagnate and lose market position.
Those who embrace change but manage it poorly create operational chaos—production confusion, cost surprises, quality risks, compliance gaps. The middle ground between resistance and chaos is systematic change control that enables rapid, confident improvement.
Formal engineering change control isn't bureaucracy that slows innovation—it's coordination infrastructure that enables rapid improvement without creating problems. You're not impeding engineering creativity; you're ensuring improvements translate to production reality without quality risk, cost confusion, or traceability gaps.
MYOB Acumatica Manufacturing Edition provides the change control capabilities New Zealand manufacturers need: BOM versioning with effective dating, ECN workflows with cross-functional review, implementation tracking and complete audit trails. Changes happen systematically, visibility is complete, compliance is automatic.
The question isn't whether your products will change—they will, and should, to remain competitive. The question is whether you'll manage those changes confidently with systematic processes, or cope with them reactively through firefighting and workarounds.
Leading manufacturers have made their choice. They've implemented formal change control and transformed it from administrative burden to competitive advantage—enabling innovation whilst maintaining control, quality, and compliance.
Take the Next Step: Manufacturing ERP Selection Made Simple
Wondering what manufacturing ERP capabilities matter most for your operations? We've created a practical resource to help New Zealand manufacturers evaluate options and make confident decisions.
Download our Manufacturing ERP Selection Checklist—a comprehensive guide covering:
- Engineering change control capabilities and BOM management requirements
- Production scheduling and material planning functionality
- Quality management and traceability features critical for compliance
- Integration capabilities with CAD, PLM, and other design systems
- Implementation considerations specific to mid-market manufacturers
- Questions to ask vendors during evaluation and demonstrations
- ROI calculation frameworks to build your business case
This checklist cuts through vendor marketing claims to focus on the capabilities, questions, and evaluation criteria that actually matter for operational success.
Download the Manufacturing ERP Checklist →
Already dealing with engineering change chaos? Calculate the true cost of informal processes and the ROI of systematic change control with our Manufacturing ROI Calculator. Model scenarios, quantify impacts, and build your business case with confidence.
Access the Manufacturing ROI Calculator →
Your products need to evolve. The question is whether your processes enable that evolution systematically—or fight it at every step.
