Written by Tsujita — Paddy & Water Inc. / Supply Chain

Engineering Change Management × Supply Chain Management

— A Complete Guide to the Integrated Architecture for Propagating Design Changes Through the Supply Chain —

June 2026

Introduction: The Necessity and Business Value of ECM×SCM Integration

0.1　The “Storm of Design Changes” Facing Manufacturing

Against a backdrop of intensifying global competition, shortening product life cycles, decarbonization regulations, and multi-layered supply chain risk, the number, complexity, and urgency of engineering changes handled by today’s manufacturers continue to increase. The era in which “there were only a few dozen design changes a year, and individual staff could coordinate them one by one” is over. Today, the combination of high-mix low-volume production, modular design, and global supply chains means that a single design change can simultaneously affect hundreds of purchase orders, dozens of suppliers, and multiple production sites.

Changes Surrounding Manufacturing	Impact on ECM×SCM Integration
Shortening product life cycles (consumer goods: 3 years → 1 year; electronics: 6 months → 3 months)	The frequency of model changes and discontinuation changes has doubled. The risk of carrying old-part inventory into the transition to next-generation designs has become the norm
Multi-tiering of global supply chains (Tier1→2→3→4 chains)	It takes several weeks for an engineering change notice to propagate through four tiers. Production of old parts continues before the information reaches end-tier suppliers
Frequent EOL of semiconductors and electronic components (supply chain restructuring since the pandemic)	Part Discontinuation Notices (PDNs) are increasing. ECOs for substitute-part changes now number in the hundreds per year. Quality qualification of substitute parts and updates to procurement plans must be carried out simultaneously
Tightening of regulations such as RoHS/REACH/CFR Part 11 (regulation of specific substances and hazardous chemicals)	Statutory deadlines are set for prohibiting the use of parts containing specific substances, creating an obligation to complete the switchover across the entire SCM within the deadline. Complete retention of change records is required as evidence
Response to carbon neutrality (2030–2050 targets)	Information on CO2 emissions from materials and parts is beginning to be incorporated into SCM, and ECOs for switching to low-carbon parts are rapidly emerging as a new change category
Growing demand for customer customization (engineer-to-order specifications and configuration)	Management of BOM differences per customer is becoming more complex. Cases are increasing in which a single customer-specific change requires redesigning the entire supply chain

0.2　The Cost of a World Without ECM×SCM Integration — Losses Seen in Numbers

This section shows, in numbers, how much is lost when ECM and SCM are not connected. Below is a structured summary of typical costs and losses, based on surveys of manufacturers and industry reports.

Typical Losses Without ECM×SCM Integration (for a Mid-Size Manufacturer with ¥50 Billion in Revenue)

◆ Direct losses from obsolete inventory 　・Without ECM–SCM linkage, ordering and receipt of old parts continues even after a design change has been approved 　・Industry average: annual obsolete inventory losses run 0.5–2% of revenue. For a ¥50 billion company, that is ¥250–1,000 million per year 　・Reduction achieved after integration: numerous cases have reduced obsolete inventory costs by 40–70% ◆ Labor and manual-work costs for change processing 　・Per ECO: design, purchasing, production control, and supplier staff coordinate via Excel/email, averaging 8–15 hours of coordination effort 　・At 500 ECOs per year, that is 4,000–7,500 hours. At an hourly rate of ¥3,000, this is ¥12–22.5 million per year in pure labor cost 　・After integration and automation: coordination effort per ECO can be reduced to 1–2 hours, an 80–85% reduction in effort ◆ Quality costs from mixing of new and old parts 　・Delayed change notices or mistakes in setting effectivity conditions result in products shipping with a mixture of new and old parts 　・Costs of handling claims, rework, and recalls can reach 2–5 times the cost of obsolete inventory ◆ Impact on supplier relationships 　・Repeated “sudden change notices” and “last-minute cancellations” erode supplier trust 　・Risk of losing preferred-customer status with quality suppliers, raising procurement costs

0.3　Concrete Business Benefits Created by ECM×SCM Integration

Business Benefit	Before Integration	After Integration (When Realized)	Basis for the Effect
Reduction of obsolete inventory cost (Obsolete Inventory Reduction)	Procurement and receipt of old parts continues even after a design change. Write-off losses occur chronically	Open POs are cancelled at the same time as ECO approval. Ordering of old parts is automatically stopped. The projected volume to be scrapped is simulated in advance	Obsolete inventory cost reduced by 40–70% (varies by industry and product complexity)
Shortened change lead time (Change Lead Time Reduction)	ECO approval → ERP reflection → shop-floor application takes an average of 2–4 weeks	Automatic linkage across all systems after approval shortens this to a few hours to 1–2 business days	The effect is especially pronounced for emergency safety changes. The scope of a recall can be identified within hours
Reduction of manual change-processing effort (Manual Work Reduction)	8–15 hours of manual coordination effort occur per ECO	Shortened to 1–2 hours per ECO. Manual Excel communication and confirmation work becomes unnecessary	60–85% reduction in effort; staff can focus on higher value-added work
Improved accuracy and speed of supplier notification (Supplier Notification Quality)	Individual emails/faxes sent by staff members; missed notices, content errors, and no way to confirm delivery	Automatic distribution to the supplier portal at the same time as ECO approval, with electronic management through to acknowledgment of receipt	Ensures suppliers switch over correctly, greatly reducing scrap compensation costs
Ensuring traceability of design changes (Traceability Assurance)	It is unclear “which part version is used in which product”	Complete tracking of the part version used, down to the individual manufacturing serial number	Enables precise identification of recall scope; reduces regulatory compliance costs for FDA/IATF and similar bodies
Improved supply chain planning accuracy (Supply Plan Accuracy)	BOM changes do not reach SCM, so plans are drawn up based on outdated information	BOM updates are immediately reflected in SCM (MRP/IBP), and procurement plans for new parts are drawn up accurately	Reduction of inventory shortages and excesses; reduced risk of production stoppages

0.4　Closed Loop Manufacturing — The Closed Loop Between Manufacturing and Design

The ultimate purpose of ECM×SCM integration is to realize a “closed loop from design to manufacturing, and from manufacturing back to design.” Closed Loop Manufacturing is a manufacturing framework in which the flow of information — design (PLM/ECM) → planning (ERP/SCM) → manufacturing execution (MES) → results collection (MES/IoT) → design improvement (PLM/ECM) — circulates without interruption.

Conceptual Diagram of Closed Loop Manufacturing

[Downstream Flow: From Design to Manufacturing] PLM / ECM “Design BOM, ECR/ECO approval, effectivity condition settings” | ▼ ERP / SCM “MBOM update, procurement planning, production planning, inventory switchover planning” | ▼ MES (Manufacturing Execution System) “Update of BOP (process routing), work instructions, and quality inspection plans” | ▼ Shop Floor “Manufacturing execution with new parts and new processes” [Upstream Flow: From Manufacturing Back to Design (Upstream Feedback — Closed Loop)] Shop Floor “Actual yield, actual labor hours, quality inspection results, equipment anomalies” | ▼ MES “Collection of manufacturing results, detection of quality deviations, recording of process parameters” | ▼ ← This is the point of the closed loop ERP / SCM “Recording of actual inventory, cost variances, and scrap results” | ▼ PLM / ECM “ECR raised based on manufacturing results: ‘This part is hard to use in this process’ ‘Yield is poor with this design’ → an ECO for design improvement is raised” → When this closed loop functions, the design intent and the manufacturing reality continue to stay aligned

Four Values Realized by Closed Loop Manufacturing

• ① Continuous improvement of design quality: Yield losses, rework, and scrap occurring on the shop floor are fed back to the design department, giving rise to ECOs that improve the design itself. “Why is this hard to manufacture” is reflected back into the design stage

• ② Real-time improvement of planning accuracy: Manufacturing results (actual yield, labor hours, throughput) are reflected in SCM plans in real time, narrowing the gap between plan and actual. “Why we cannot build to plan” is automatically incorporated into SCM’s calculation parameters

• ③ Reduction of engineering-change cost: Design problems that would otherwise be discovered after manufacturing can be caught before manufacturing (at the design stage). The cost of a design change grows exponentially — “design stage: 1,” “prototype stage: 10,” “mass-production stage: 100” — so the benefit of early detection is enormous

• ④ Realization of the Digital Thread: A state in which a product’s design, manufacturing, quality, and service information are all connected by a single digital thread. For part number X, it becomes possible to consistently trace “who designed it, when it was changed, which lot it was manufactured in, which customer it was shipped to, what claims arose, and what was reflected in the next design change”

[External Case Study: Cytiva (Rockwell Automation, 2020)]Closed Loop Manufacturing is not a theoretical concept. In Cytiva’s official case study, a digital foundation including MES, electronic batch records, and cloud analytics (KUBio) compressed factory construction to under 18 months, improved production throughput, availability, and floor efficiency by 10–20%, and is reported to shorten customer time-to-market from “7 years to 3–4 years.” Standardizing design, automation, and quality documentation ahead of time is what determines the propagation speed of change. (Officially published by Rockwell Automation/Cytiva)

0.5　Closed Loop Quality — The Closed Loop Between Quality and Design Change

Closed Loop Quality is the quality-focused version of Closed Loop Manufacturing. It realizes a closed loop in which “problems detected through quality automatically drive design changes (ECM), and the effect of the design change is then verified through quality results.” It is the architecture that contributes most directly to reducing the Cost of Quality in manufacturing.

Conceptual Diagram of Closed Loop Quality

[Occurrence and Detection of Quality Problems] Market / Customer “Product claims, field defects, safety incidents” | ▼ Quality Management System (SAP QM / Customer Claim Management) “Claim intake, root-cause analysis, corrective action (CAPA) management” | Shop Floor / Incoming Inspection “Quality deviations during manufacturing, incoming inspection rejects, process defects” | Supplier Quality “Supplier-caused part quality problems, SCAR (Supplier Corrective Action Request)” [Feedback from Quality to Design (The Core of the Closed Loop)] The quality system determines: “Is this quality problem caused by design? By the part? By the process?” | ▼ Design-caused → an ECR is automatically raised in PLM “Design change request based on quality issue number #QN-2025-0412” “Root cause: the tolerance setting of Part A exceeds the capability of the manufacturing process” | Part-caused → an ECR (substitute part change) is automatically linked with an SCAR (supplier corrective action request) | Process-caused → BOP change instruction (process parameter adjustment) in MES [Verification of Effect After the Design Change (Closing the Loop)] ECO approval, BOM change, adoption of new part | ▼ Quality results are collected from the production lots made after the change “Did the claim rate improve? Did the defect rate decrease?” | ▼ Quality improvement effect confirmed → ECO is closed (change complete) If improvement is insufficient → an additional ECR is raised → When this closed loop functions, quality problems continue to lead to design improvements

The Five Components of Closed Loop Quality

Component	Overview	SAP Implementation	Linkage with ECM
Quality Notification	Customer claims, internal defects, and supplier problems are managed as quality notifications. Root-cause analysis, corrective actions, and effectiveness confirmation are managed centrally	SAP QM01 (Quality Notification), QM10 (Quality Notification List)	When the cause of a quality notification is determined to be “design-caused,” it is automatically escalated to an ECR in PLM. The notification number is linked as the supporting document for the ECR
SPC (Statistical Process Control) — Process Capability Monitoring	Manufacturing process parameters (temperature, pressure, dimensions, etc.) are monitored in real time. An automatic alert fires if process capability (Cp/Cpk) falls below the standard value	SAP QM (SPC function), quality modules of MES (Opcenter/SAP DM)	When a decline in process capability is caused by “a design tolerance issue,” an ECR is automatically raised to the design department. This creates a flow that proposes “a design change to relax the tolerance”
FMEA (Failure Mode and Effects Analysis) Linked with ECM	If a risk identified in the design FMEA actually materializes, the FMEA is updated and an ECR is automatically raised	SAP PLM FMEA module or integration with a dedicated FMEA tool (e.g., ReliaSoft)	If the severity, occurrence, or detection rating in the FMEA worsens, a high-priority ECR is automatically generated. Consistent management from design FMEA → manufacturing FMEA → actual results data
CAPA (Corrective and Preventive Action) Management	Corrective actions and preventive actions for the root cause of quality problems are managed as documents	SAP QM CAPA / dedicated CAPA management system	If a CAPA requires a design change, an ECR is automatically generated from the CAPA. The CAPA’s effectiveness check is linked as a precondition for closing the ECO
Supplier Corrective Action Requests (SCAR/8D)	Corrective action requests for supplier-caused quality problems. Manages the submission, confirmation, and approval of 8D reports	SAP Ariba Quality Management or the SCAR function of the supplier portal	If a supplier’s corrective action includes “a part specification change,” a substitute-part ECR is automatically raised to the design department. SCAR completion is linked as a precondition for ECO approval

[External Case Study: Catena-X Quality Management (BMW/Bosch/DENSO and others)]When field data on market defects held by an OEM is connected — in a standardized, sovereignty-preserving form — to a supplier’s manufacturing results, root-cause analysis and change-necessity decisions can be pulled forward by months. Officially published results report detecting errors an average of 4 months earlier, connecting new suppliers in 5 weeks, and narrowing camera-related suspects from 1.4 million units to 14 units. This substantiates the practicality of “reverse-direction feedback” and “multi-tier linkage.” (Officially published by Catena-X)

0.6　Digital Thread — All Data Connected Around Design Changes

The higher-level concept that integrates Closed Loop Manufacturing and Closed Loop Quality is the “Digital Thread.” It refers to a state in which all data related to a product’s design, manufacturing, quality, and service is connected by a single “digital thread.” ECM (engineering change management) is the system that manages “when the thread switches over” within this Digital Thread, and SCM is the mechanism that ensures “the thread matches the actual flow of physical goods.”

Components of the Digital Thread	Information Managed	Role in ECM×SCM Integration
Design Thread	CAD/EBOM, specifications, FMEA, test data, ECR/ECO history	Every design change is stored in a form traceable by change number (ECO number). A data foundation that completely shows “what changes this product went through during design”
Manufacturing Thread	MBOM, process routing (BOP), work instructions, manufacturing results, serial number history	Records, for every manufactured product, “which design version (ECO version) it was made with.” A complete link between serial numbers and ECO versions
Quality Thread	Quality inspection records, SPC results, claims, SCARs, CAPAs, defective lots	Immediately identifies “which design version, which supplier part, and which manufacturing lot” from the serial number of a product with a quality problem. Quality information also automatically generates feedback to ECRs
Service Thread	Field defects, repair history, spare-part usage records, customer feedback	Problems occurring after shipment are recorded as the basis for design changes. “What broke in the field” becomes input information for the next ECO
Supply Chain Thread	Part traceability, lot tracking, supplier change history, procurement contracts	Complete tracing of “which supplier and which lot this part came from.” Ensures that the effectivity conditions of an ECO (part change) precisely match the actual switchover point in procurement

[External Case Study: NIST Digital Thread / Siemens Amberg / Rolls-Royce DIREKT]The Digital Thread is not a buzzword — it is the subject of published standards (STEP, QIF, MTConnect). NIST reports in pilot studies that adopting model-based product definitions contributes to shortening design–manufacturing lead time and improving final quality. Siemens Amberg demonstrates the use of roughly 50 million data points, 99.9990% quality, and cycle-time improvements via digital twins, while Rolls-Royce’s DIREKT uses a full-lifecycle digital thread to “instantly recalculate design changes at the model stage.” (Officially published by NIST/Siemens/Rolls-Royce)

0.7　Intended Readers of This Guide and How to Use It

This guide is written with the following readers primarily in mind. A recommended reading path is shown for each purpose.

• Design department / PLM staff at manufacturers: to understand “how the ECRs we raise affect the supply chain” and to create ECOs that are more grounded in reality. → Focus on Chapters 1, 2, and 3

• Procurement, purchasing, and supply chain staff: to understand “what is needed to receive design changes faster and more accurately, and reduce write-off losses.” → Focus on Chapters 3, 5, and 8

• Production control and shop-floor managers: to clarify “when and how a design change reaches the shop floor, and what needs to change.” → Focus on Chapters 5, 6, and 7

• ERP system architects and SAP implementation consultants: for the technical design of “how to implement ECM×SCM integration in SAP S/4HANA.” → Focus on Chapters 6, 7, and 9

• Executives and DX leaders: to understand “why ECM×SCM integration is a management priority” and to use it as a basis for investment decisions. → The Introduction (this chapter) alone provides sufficient grounds for an investment decision

Chapter 1: Why ECM×SCM Integration Is Difficult — The Essence of the Problem

1.1　Design Changes That Stop the Supply Chain

In manufacturing, “engineering changes” occur on a daily basis. The reasons vary widely: responses to quality problems, switching to cost-reducing parts, regulatory compliance, responding to customer requirements, performance improvements, and more. The problem is the integration gap in which “even once a design change is approved, it does not propagate accurately and in a timely manner across the entire supply chain.”

Typical Confusion Caused by Design Changes in SCM

[What Commonly Happens on the Ground] ① A BOM change is approved in the design department 　→ But purchasing has already placed a large order for the old part 　→ Excess inventory and obsolescence loss (obsolete inventory) of the old part occur ② The effective date of the design change is set as “starting the 1st of next month” 　→ But on the shop floor, the rule for “which production lots completed today still use the old part” is ambiguous 　→ Products with a mix of new and old parts are shipped, leading to quality problems ③ An emergency safety modification (Safety ECO) is issued 　→ It is not immediately clear which suppliers hold how much of the old part in stock 　→ It takes three days to identify the affected scope, during which products using the old part continue to be shipped ④ The design department has closed the change as “complete” 　→ But the service department continues to procure the old part as a spare for three years 　→ The state in which “the part is discontinued in design but still alive in procurement” persists for a long time

1.2　The Structural Disconnect Created by the “Division of Labor” Between ECM and SCM

Manufacturing information systems have historically been managed with “design and development” (PLM/ECM) and “procurement, manufacturing, and logistics” (ERP/SCM) as separate systems. This “division of labor” itself is rational as a functional division, but in many cases the information linkage across that boundary relies on “manual, email, and Excel-based communication,” which is the single biggest barrier to ECM×SCM integration.

System Layer	Area of Responsibility	Change Information Managed	Means of Linkage to SCM (Current Problems)
PLM (Teamcenter/ENOVIA/Windchill/SAP PLM)	Design, development, and change management (ECM)	EBOM, drawings, specifications, ECR/ECO, part qualification status	No automatic linkage from PLM to ERP/SCM; the design department communicates change content via Excel or email
ERP (SAP S/4HANA, etc.)	Purchasing, inventory, production planning, cost	MBOM, production orders, purchase orders, inventory	Changes from PLM are manually reflected on the ERP side. Time lag, errors, and omissions occur
SCM/APS (SAP IBP/APO, etc.)	Demand planning, supply planning, inventory optimization	Production plans, supply plans, inventory targets	BOM change and part-switchover information does not reach SCM, degrading plan accuracy
MES (Opcenter/DELMIA, etc.)	Manufacturing execution, work instructions, quality	BOP, work instructions, quality standards	It takes time for the new BOP/work instructions after a design change to reach the shop floor, creating a risk of mixing old and new
External Supplier Systems	Parts procurement, outsourced manufacturing	Trading-partner part master, open orders, inventory	Change notices arrive by paper, fax, or email, delaying the supplier’s response

1.3　Five Questions ECM×SCM Integration Must Answer

• Question ① (Timing): At what point in the supply chain should a design change take effect? (After existing inventory is used up? From a specific lot number? From a specific date?)

• Question ② (Scope of Impact): Where does this change affect purchasing, inventory, production, shipping, and service? Can the full scope of impact be identified automatically before the change is approved?

• Question ③ (Propagation Speed): How many hours or days does it take for an approved change to reach a supplier’s factory floor or our own production line? Is that fast enough?

• Question ④ (Traceability): Can it be tracked, even after manufacturing and shipment, which product used the new part and which used the old part?

• Question ⑤ (Reverse-Flow Information): Can quality and procurement problems discovered in SCM or MES be quickly fed back as ECRs to the design department?

Chapter 2: The Full Picture of Engineering Change Management

2.1　Basic ECM Terminology

Term	Abbreviation	Definition	Corresponding SAP Object
Engineering Change Request	ECR (Change Request)	A document raising the need for a change. Includes the reason for the change, the anticipated scope, and an initial assessment of impact. Promoted to an ECO once approved	ECR classification in CC01 (Change Master) / Change Request in SAP PLM
Engineering Change Order	ECO (Change Order)	A document that formally approves the implementation of a change. Finalizes the target BOM, drawings, specifications, effective date, and responsible parties	CC01/CC02 (Change Master) / CS01 links an effectivity period to a BOM change
Engineering Change Notice	ECN (Change Notice)	A document notifying relevant departments and suppliers of the change content. Issued at the same time as, or immediately after, ECO implementation	SAP Document Management (DMS) / supplier portal notification
Engineering Change Implementation	ECI (Change Implementation)	The process of actually changing the BOM, drawings, and work instructions based on the ECO, and confirming application to manufacturing and procurement	Implementation of BOM change (CS02) and routing change (CA02)
Effectivity	—	The condition under which a change becomes effective. Includes date effectivity, serial-number effectivity, and lot-number effectivity	Effectivity parameter settings in CC01 (lower/upper date bounds, serial range)
Phase-In / Phase-Out	Phase-In/Out	Supply chain planning that gradually discontinues an old part (Phase-Out) while gradually introducing a new part (Phase-In)	Phase-in/out settings in MRP/MRP Live, substitute-part master
Red-Line Change	Emergency Change	An immediate response to a serious safety or quality issue. The normal approval flow is shortened to implement the change as fast as possible	Priority setting in SAP ECM, emergency release flow

2.2　The Standard ECM Process Flow

The ECM process proceeds through multiple stages, from “discovery of the change” to “verification of the change.” The decisions made at each stage and the assessment of impact on SCM are at the core of integrated design.

Stage	Key Activities	Decision Maker	Impact on SCM
Stage 1 Discovery and Raising of the Change	An ECR is raised, triggered by a quality defect, cost improvement, regulatory change, customer request, etc. The reason for the change, an initial estimate of impact scope, and urgency are described	Designer, quality staff, sales	A preliminary notice to SCM is needed at this stage (especially for urgent changes). Cross-checking with current inventory, open orders, and production plans begins
Stage 2 Impact Analysis	The affected BOM, drawings, and specifications are identified. Impact on items being purchased, inventory, production orders, and already-shipped products is assessed from every angle. Projected write-offs, switchover cost, and schedule impact are calculated	A cross-functional team of design, purchasing, manufacturing engineering, quality, and logistics	The most important stage. Value comes from integration with the SCM system that can automatically enumerate the “affected purchase orders, inventory, and production lots”
Stage 3 Change Approval (ECO Approval)	Implementation of the change is approved based on the results of the impact analysis. The effectivity condition (date/lot number) and transition method (immediate/phased) are decided	Design lead, head of procurement, head of production control, head of quality assurance	The decision on the effectivity condition and transition method governs how SCM moves. Ideally, this is automatically reflected in the SCM system at the same time as approval
Stage 4 Change Implementation (ECI)	The BOM, routing, and work instructions are changed. The switchover schedule for old and new parts is executed. ECN issuance to suppliers and inventory switchover instructions are given	Design, purchasing, production control, MES staff	Change propagation from PLM → ERP → MES. Whether each system’s update is automatically linked or manual is the crux of the integration design
Stage 5 Change Verification	Manufacturing results with the new part and new process are confirmed. Quality inspection results and cost results are evaluated. The ECO is closed and completion of the change is recorded	Quality assurance, design, production control	Result data fed back from MES and QM to the ECM system completes verification of the change’s effect

Chapter 3: The Impact Map of Design Changes on SCM

3.1　Scope of Impact by Change Type

The scope and urgency of impact on SCM varies greatly depending on the “type” of design change. The main change types and their impacts are organized below.

Change Type	Main Reasons for Occurrence	Scope of Impact on SCM	Urgency	Typical Problem
① Safety/quality modification change (Safety/Quality ECO)	Product safety issue, serious quality defect, recall response	・Recall/repair of already-shipped products ・Immediate quarantine of the old part in inventory ・Decision on whether to stop production lots in progress ・Immediate notification to suppliers	Highest (hour-level)	It takes time to identify the scope of inventory and shipped products that should be quarantined. If SCM traceability is incomplete, the scope of impact cannot be determined
② Part substitution / procurement change (Material Substitution ECO)	End-of-life (EOL) of an old part, unit-price spike, supplier change, procurement risk avoidance	・Switching purchase orders ・Plan to use up old-part inventory ・New-part qualification and order lead time ・Managing coexisting inventory of old and new parts	High to medium (week-level)	Write-off losses occur when switching to the new part while old inventory remains. Or the switch to the new part is delayed while trying to use up the old part, stopping the production line
③ Performance/feature improvement change (Performance/Feature ECO)	Improving product competitiveness, customer feedback, cost reduction	・BOM change (adding/removing new parts) ・Manufacturing process change ・Updating work instructions ・Impact on cost	Medium (month-level)	Ambiguous effective-date settings result in products with a mix of new and old parts reaching the market. Missed updates to management codes
④ Regulatory compliance change (Regulatory ECO)	Regulatory changes such as RoHS, REACH, CE, FDA	・Prohibition on using inventory containing specific substances ・Switching to certified parts ・Updating CoC (Certificate of Conformance)	High (based on the regulation’s effective date)	Risk of being unable to confirm that switchover of all inventory, including supplier inventory, is complete by the regulation’s effective date
⑤ Obsolescence change (Obsolescence ECO)	End of production of a product, model change	・Securing final inventory of spare parts ・Confirming the final production lot number ・Planning service inventory	Low to medium (quarter-level)	Even after obsolescence, suppliers may unknowingly continue to hold inventory, leading to continued surplus inventory and unnecessary procurement

3.2　The Structure of Write-Off Losses (Obsolete Inventory) from Design Changes

Write-off losses accompanying design changes chronically occur in manufacturing as a “hard-to-see cost.” Understanding this structure is the starting point for ECM×SCM integration design.

Where Write-Off Losses Occur	Mechanism of Occurrence	What Integration Can Prevent
Old-part inventory in the company’s own warehouse	Ordered inventory continues to arrive even after change approval. The inventory is written off as “unusable after the change”	MRP’s open orders and expected receipts are automatically cross-checked at the impact-analysis stage. Open POs for the old part are cancelled and the supplier notified at the same time as change approval
Work in process (WIP)	The old part is already built into a product partway through the manufacturing process. After the change, it is scrapped or reworked as an “incomplete product”	Integration with MES identifies, in real time and before change approval, which production lots have the old part built in. Precisely sets the switchover point of “use the new part from this production lot onward”
Supplier inventory	While the change notice is delayed, the supplier continues manufacturing and holding inventory of the old part. After the change, it is written off as “non-returnable”	The ECN (change notice) is automatically sent via the supplier portal/EDI at the same time as approval. The supplier’s old-part inventory volume is confirmed in advance to minimize write-off compensation
After-sales service inventory	A part that is discontinued in design continues to be procured by the service department as a long-term spare	ECO information is automatically propagated to the service BOM and spare-parts catalog. A “substitute part code” is linked to the discontinued part, and the service department automatically switches to the new part

Chapter 4: The Overall ECM×SCM Integration Architecture Blueprint

4.1　The Overall Picture of Integration

The ideal form of ECM×SCM integration is an architecture in which “the single event of a design-change approval propagates automatically, instantly, and accurately across the entire supply chain.” The concept of the overall integration blueprint is shown below.

Conceptual Diagram of the ECM×SCM Integration Architecture

[Upstream: Design and Change Management Layer] PLM (Teamcenter / ENOVIA / Windchill / SAP PLM) ├─ EBOM (Engineering Bill of Materials) ├─ ECR/ECO management (change request → change order) ├─ Drawing/specification/CoC management └─ [Change approval event fires] │ ▼ [Integration Interface Layer] API / BTP (SAP) / ESB (integration platform) ・EBOM→MBOM conversion logic ・Conversion of effectivity conditions ・Automatic impact-scope calculation engine │ ┌──────┼──────────┐ ▼ ▼ ▼ [ERP Layer] [SCM/APS Layer] [Supplier Layer] SAP S/4HANA SAP IBP / APS Supplier Portal ・MBOM update ・Demand-plan recalculation ・Automatic ECN notification ・Purchase order ・Supply-plan adjustment ・Old-part inventory confirmation cancellation ・Inventory switchover plan ・New-part rollout ・Production order update instruction ・Effectivity period setting │ ▼ [Manufacturing Execution Layer] MES (Opcenter / SAP DM) ・BOP (process routing) update ・Automatic distribution of new work instructions ・Control of the “new part starts here” switchover point │ ▼ [Traceability Layer] ・Complete record of “which manufacturing lot used the new/old part” ・Realization of forward/backward tracking

4.2　Integration Design for EBOM→MBOM Conversion

One of the most important integration points in ECM×SCM integration is the “conversion from EBOM (Engineering Bill of Materials) to MBOM (Manufacturing Bill of Materials).” This conversion is not a simple data copy — it includes business logic that translates design intent into manufacturing reality.

Conversion Item	EBOM (Design Side)	MBOM (Manufacturing Side)	Example of Conversion Logic
Part number	Design drawing number / part number (design department rules)	Purchasing/manufacturing item code (ERP item master)	Converted via a mapping table between design numbers and ERP item codes. Manages cases where one design number corresponds to multiple procurement part numbers
Quantity/unit	Design usage quantity (theoretical value, no yield)	Manufacturing required quantity (accounting for yield/scrap rate)	Yield and scrap rates are appended to the MBOM. Example: 1 unit used in design → 1.05 units in the MBOM (95% yield)
Substitute parts	Only “recommended parts” in design	Includes “first substitute, second substitute” in manufacturing	Supplier-qualified substitute parts are automatically added to the MBOM. Substitution priority is set according to procurement risk
Effectivity condition	The design-side effective date of the change	The manufacturing-side switchover point (after inventory depletion / from a specific lot)	Starting from the design’s effective date, the SCM system calculates the “actual switchover lot number/date” from SCM’s inventory volume and production plan
Phantom BOM	A subassembly in design	Whether it is manufactured (Make) or purchased (Buy) as an intermediate item	A Make/Buy decision logic is applied during MBOM conversion

4.3　The Three Methods of Effectivity and Selection Criteria

The “effectivity condition,” which determines when a design change is applied, is the most delicate design point in ECM×SCM integration design. Choosing incorrectly results in write-off losses, quality mixing, and a lack of traceability.

Type of Effectivity	Overview	Suitable Cases	Notes for SCM Implementation
① Date effectivity (Date Effectivity)	The new BOM is applied to items manufactured/procured on or after a specified date. Example: “Production orders from September 1, 2026 onward use the new BOM”	・Switching to cost-improvement parts ・Regulatory compliance (based on the enforcement date) ・Planned performance-improvement changes	Clarify how to handle production orders and purchase orders issued before the date. Establish a rule for whether an old part arriving as expected on September 1 should be used or discarded
② Serial/lot number effectivity (Serial / Lot Effectivity)	The new BOM is applied from a specific serial number or production lot number onward. Example: “The new part is used from serial #5001 onward”	・Safety modifications (clarifying “recall applies before this number”) ・Industries such as automotive and aerospace with strict traceability requirements	The serial-numbering rules must be aligned with the SCM system. MES linkage is used to associate serial numbers with production orders
③ Use-Up effectivity (Use-Up / Exhaust-Then-Change)	The new part is switched to only after the old part’s inventory is used up. Example: “The new part B is used from the production order following depletion of old part A’s warehouse inventory”	・Part substitution changes where write-off loss should be minimized ・When full compatibility between both parts is guaranteed	MRP must calculate the old and new parts simultaneously and be configured to automatically switch to ordering the new part once old inventory is depleted. Inventory levels must be monitored systematically

Chapter 5: Detailed Integration Flows by Change Type

5.1　Integration Flow for Emergency Changes (Safety ECO)

Emergency changes for serious safety and quality issues must shorten the normal approval flow while still identifying and addressing the scope of impact on SCM as fast as possible. Balancing “speed” and “accuracy” is the core of the integration design.

Step	Action	Responsible	System Integration	Target Time
S1: Problem Detection	A quality defect or safety issue is detected, and an emergency ECR is immediately raised. The affected part code and a summary of the problem are recorded	Quality staff, design staff	QM (Quality Notification QM01) → automatically escalated to a PLM ECR, or MES quality alert → PLM linkage	0–2 hours
S2: Immediate Identification of the Impact Scope	① Immediately identify and quarantine the old part in inventory ② Identify which WIP lots have the old part built in ③ Immediately extract the scope of impact on shipped products via the traceability system ④ Confirm the supplier’s old-part inventory volume	Purchasing, logistics, quality, design	MES/WM traceability: reverse-tracks lots using the old part. SAP inventory management: immediately queries lot-level inventory of the old part. Supplier portal: automatically sends inventory inquiries	2–8 hours
S3: Emergency ECO Approval	Based on the impact information, the change is approved via a simplified approval flow (a shortened version of the normal flow). The effectivity condition and transition method are finalized	Design lead, CQO (Chief Quality Officer)	ECO approval triggers automatic propagation of the change to SCM systems. SAP PLM: the Change Master is approved with an emergency status	4–24 hours
S4: Execution of Stop/Quarantine Instructions	① Apply a “Quality Hold” status to old-part inventory ② Temporarily halt shipment of production lots using the old part ③ Issue an emergency ECN to suppliers	Logistics, manufacturing, purchasing	SAP WM: changes inventory status to Q-stock (under inspection). MES: turns off the shipping-permission flag. Supplier portal: automatically sends the emergency ECN	1–4 hours
S5: Implementation of Corrective Measures	Resume production with the new or reworked part. Repair, re-inspect, and resume shipment of products that were held	Manufacturing, quality	MES: distributes the new BOP and new work instructions to the shop floor. SAP PP: re-orders production orders with the new BOM	Depends on the change (days to weeks)
S6: Post-Change Verification and Closure	Confirm manufacturing results and quality inspection results with the new part. Close the ECO and archive all records. Finalize the scope of any recall	Quality, design, legal (as needed)	SAP QM: records the usage decision (QA11). PLM: closes the ECO and archives all records. Issues a traceability report	1–4 weeks

5.2　Integration Flow for Planned Changes (Planned ECO)

For planned design changes aimed at cost improvement or performance enhancement, a phase-in/phase-out plan that both minimizes write-off loss and maximizes the effect of the change is the key.

Phase	Approximate Duration	Action	SCM Integration Points
Pre-Assessment (Pre-ECO)	1–3 months before approval	・Confirm current inventory, open orders, and safety stock of the old part ・Simulate use-up (when will inventory reach zero) ・Confirm supplier qualification and lead time for the new part ・Calculate switchover cost (projected write-off amount, qualification costs)	Simulation via MRP inventory and open-order inquiries. Begin qualification testing of the new part with the supplier
ECO Approval and Effectivity Setting	Approval date	・Decide the effectivity condition (use-up method / date method) ・Finalize the final order date and final receipt date for the old part ・Calculate the first order date and required lead time for the new part	Set the effectivity condition on the MBOM in SAP CC01. Set the old-part phase-out date and new-part phase-in date in the MRP parameters
Transition Execution	1–4 weeks before/after the switchover date	・Place the final order for the old part (order stops after this) ・Confirm the first order and receipt of the new part ・Distribute new work instructions and provide training to shop-floor workers ・Set “the new part is used from this production lot onward” in MES work instructions	MES: registers the switchover lot number; once the lot number passes the switchover point, the new BOM is automatically referenced. Supplier portal: notifies that old-part orders have stopped and new-part orders have begun
Monitoring (Post-ECO)	1–3 months after the switchover	・Confirm quality results with the new part ・Confirm that old-part inventory has reached zero ・Measure cost-reduction and quality effects ・Confirm no unexpected write-off losses have occurred	SAP QM: confirms quality records for new-part lots. SAP Material Ledger: analyzes cost variance between old and new parts. SAP ECO closure processing

Chapter 6: Integration Design for SAP Implementation

6.1　Key ECM Transactions in SAP

Transaction	Function	Role in ECM×SCM Integration
CC01 / CC02	Creation/change of the Change Master (Engineering Change Master)	Centrally manages changes to all BOMs, routings, and material masters under a “change number.” Effectivity conditions (date, parameters) are set here. The change number is the linkage key between ECM and SCM
CS01 / CS02	Creation/change of the Bill of Materials (BOM)	Executes BOM changes linked to a change number and effective date. CS02 references the change number set in CC01, achieving history management in which pre- and post-change BOMs coexist
CA01 / CA02	Creation/change of Routing (manufacturing process)	Manufacturing process changes are also managed by change number. This allows a setting such as “the process under this change number uses the new part in a new process”
CC60	Effectivity Check of the Change Master	A report confirming “whether this change number has been applied correctly.” Confirms the status of change application to the BOM and routing
PMEVC	Change linkage between PLM and ERP (SAP PLM integration)	An interface that automatically links ECRs/ECOs managed in SAP PLM to BOM and routing changes in SAP ERP (S/4HANA)
CS15	Where-Used list for the BOM	Immediately identifies “which product BOMs” the affected part is used in. Used to automate impact-scope analysis
MB52 / MB56	Warehouse inventory inquiry / batch inventory inquiry	Confirms current inventory volume and batch-level inventory of the affected part. Used to project write-off losses
ME2M / ME2L	Purchase order inquiry (by item / by vendor)	Identifies open orders and undelivered orders for the affected part. Extracts cancellation targets at the same time as change approval
CO40 / CO41	Batch release/inquiry of production orders	Identifies production orders using the affected part. Manages the switchover point of “the old BOM applies up to this production order, the new BOM from then on”

6.2　BOM Effectivity-Period Management Design with SAP ECM

BOM effectivity-period management in SAP S/4HANA is realized through the combination of the “Change Master (CC01)” and the “BOM (CS01/CS02).” Without correct design, confusion arises over “which BOM is correct at a given point in time.”

Design Principle ①: Every BOM change must always be assigned a change number

Changing a BOM directly without a change number leaves no change history, making it impossible to trace “when, by whom, and why it was changed.” In S/4HANA, it is recommended to enable the setting that requires a change number (the Change Number Required flag on the material master).

Design Principle ②: Standardize whether the effective-date basis is the “production order date” or the “production start date”

SAP S/4HANA lets you configure “which date determines the version of the BOM.” Options include “production order creation date,” “planned start date,” and “production completion date,” and the appropriate choice differs by industry and product characteristics. Without a consistent setting, it becomes unclear “which BOM was used to manufacture the product.”

Design Principle ③: For the use-up method, leverage the Alternative Item Master

When switching from an old part to a new part via the use-up method, SAP’s BOM Alternative Item feature can be used to configure “prioritize the old part while inventory remains, then automatically switch to the new part once it runs out.” MRP automatically factors this rule into planning.

6.3　Integration Design for Automatic PLM→S/4HANA Linkage (SAP Integration Scenarios)

Integration Scenario	PLM Side	S/4HANA Side	Integration Method	Implementation Notes
EBOM→MBOM conversion	EBOM managed in Teamcenter/ENOVIA/Windchill	MBOM managed in S/4HANA CS01	API integration (REST/SAP BTP Integration) or the SAP LO-ECH API; SAP Teamcenter Integration (TCI) is the most native option	The mapping between design part numbers and ERP item codes must be prepared in advance. Automatic conversion is not possible without this mapping
ECO approval → automatic BOM change application	An ECO reaches approved status in PLM	CC01+CS02 in S/4HANA are automatically updated	PLM ECO approval event → webhook or batch linkage → creation of CC01 and update of CS02 in S/4HANA	Align the lag between approval and application (batch interval) with business requirements. Determine whether real-time or near-real-time linkage is needed
Change notice → automatic supplier notification	PLM ECO approval	ECN automatically sent via SAP Ariba / supplier portal	API from S/4HANA MM → Ariba Connectivity, or a dedicated supplier portal	Notification methods (EDI/email/portal) differ by supplier. A mechanism for confirming receipt (acknowledgment) is also needed
BOP integration	BOP defined from PLM MBOM + process design	Routing updated in S/4HANA CA01, or BOP delivered directly to MES (SAP DM)	Direct integration from PLM BOP → SAP DM (MES), or via S/4HANA CA (routing)	Beware of the difference in granularity between BOP and routing. PLM’s BOP is at the plant-design level, while SAP routing is at the production-planning level — they differ slightly

Chapter 7: Industry-Specific ECM×SCM Integration Patterns

7.1　Automotive and Motorcycle (the Most Complex ECM×SCM)

The automotive industry is one of the most advanced industries for ECM×SCM integration, given the frequency of design changes, the multiple tiers of the supply chain, and IATF 16949 quality requirements.

• Characteristics of design changes: A single vehicle model generates hundreds to thousands of ECOs per year. A “change cascade” propagates through multiple tiers, from OEM to Tier 1 and from Tier 1 to Tier 2

• Characteristics of effectivity: Serial-number effectivity is the mainstream (“the new part from this chassis number onward”). The date the production line “cuts over the model number” is the switchover point

• Main integration challenge: Change notices to Tier 1–Tier 2 arrive as paper or PDF, and the switchover timing at Tier 2 is inaccurate. The risk of old/new part mixing carries different meanings for “design quality” versus “mass-production quality”

• Key point of integration design: EDI linkage from the OEM’s PLM (Teamcenter or ENOVIA) to Tier 1’s ERP is the key. It is necessary to establish a change-notice format that complies with “automotive industry standard formats” (ODETTE/VDA, etc.) for design changes

[External Case Study: Catena-X (Automotive OEM–Supplier Quality Linkage)]The multi-tier quality and change linkage that is the hardest part of automotive ECM×SCM is being implemented through a standardized data platform. Catena-X’s Quality Management is reported to connect an OEM’s market data with a supplier’s production data, detecting defects an average of 4 months earlier and shortening new-supplier go-live to 5 weeks. The form of multi-tier change linkage described in Section 7.1 is already established externally. (Officially published by Catena-X)

7.2　Electrical and Electronics (Part EOL and Short Life Cycles)

In the electrical/electronics industry, “substitute-part changes” triggered by the end-of-life (EOL) of chips and electronic components occur frequently. Because product life cycles are short, the speed of responding to changes directly affects competitiveness.

• Characteristics of design changes: Procurement-led ECOs triggered by a Product Discontinuation Notice (PDN) for a semiconductor part are common. The design and purchasing departments often jointly raise the ECO

• Characteristics of impact on SCM: Since substitute-part qualification takes 3–6 months, an inventory build-up (“Last Time Buy”) is needed from PDN receipt until effective ECO approval. Calculating the LTB quantity is critical

• Main integration challenge: How to support the decision of selecting the optimal option, considering cost, lead time, and quality, among multiple candidate substitute parts. Also, traceability to compare post-substitution quality results with those of the original part

• Key point of integration design: Integrate a parts-information database such as IHS Markit with PLM/ERP to automate “automatic ingestion of part EOL information → advance alert → substitute-part search”

7.3　Pharmaceuticals and Medical Devices (Regulatory Compliance Dominates)

In pharmaceuticals and medical devices, some design changes require filing with or approval from a regulatory authority (FDA, PMDA, etc.), and the constraint that “a change cannot be implemented until approval is obtained” complicates integration design.

• Characteristics of design changes: Under GMP (Good Manufacturing Practice) regulations, documenting, approving, and recording every change is mandatory. Changes are classified as “minor changes (notification only)” or “major changes (approval required)”

• Characteristics of impact on SCM: Because production must continue while awaiting regulatory approval, “securing inventory of the old formulation” and “the switchover plan after regulatory approval” must be managed simultaneously

• Main integration challenge: The switchover timing in SCM changes depending on the regulatory category of the change (notification/approval). Integration is needed that can dynamically simulate the impact on SCM if regulatory approval is delayed

• Key point of integration design: Integrate PLM’s ECM with a quality system (such as Veeva Vault) to guarantee consistency between regulatory submission documents and the manufacturing BOM. Electronic approval and audit trails compliant with FDA 21 CFR Part 11 are mandatory

[External Case Study: Eli Lilly / Zyno Medical (FDA)]The goal of change linkage in regulated industries is not mere BOM synchronization. Eli Lilly built IT/OT integration spanning vision systems, high-speed control, event management, and ERP for serialization at the finished-product level. Zyno Medical, on the other hand, released an unverified (V&V-incomplete) software version to the market, resulting in an FDA Class I recall that required stopping use, returning, and locating devices at the individual serial-number level. This is a stark counter-example showing why linkage between effectivity management and “verified change” is necessary. (Officially published by Rockwell/Eli Lilly, FDA)

7.4　Chemicals and Process Manufacturing (Recipe Changes and Batch Management)

In chemical and process manufacturing, changes to the “product recipe (Formula/Recipe)” are at the center of ECM, and the characteristics of batch manufacturing combined with supply chain integration create a unique complexity.

• Characteristics of design changes: Changes to raw-material quality specifications, mixing ratios, manufacturing temperature, and time parameters are managed as recipe ECOs

• Characteristics of impact on SCM: Batch size and yield variation directly affect inventory planning. Actual yield after a recipe change can deviate from the planned value, making inventory shortages or excesses more likely

• Key point of integration design: Integrate SAP PP-PI (process orders) with PLM’s Recipe management. Design a flow where recipe changes are automatically applied to the master recipe in PP-PI

Chapter 8: Supplier Integration Design — Change Notification to External SCM

8.1　Design of Supplier Change Notification (ECN)

Notifying suppliers of a design change (ECN: Engineering Change Notice) is, in ECM×SCM integration, just as important as — if not more important than — internal system linkage. If a supplier notification is delayed or inaccurate, it results in excess manufacturing of the old part, disputes over write-off compensation, and mixing of quality.

Notification Content	Why It Is Needed	Notification Timing	Recommended Notification Method
Detailed change content (drawings/specifications)	The supplier cannot respond without accurately understanding “what changed and how”	At the same time as ECO approval	Automatic distribution from the PLM DMS (document management) to the supplier portal, providing direct access to the latest drawings and specifications
Effective date and switchover lot	Without accurately communicating “when the new part should be delivered,” new/old mixing occurs	At the same time as ECO approval	Notify with a clear numeric date and lot number. Avoid ambiguous instructions such as “as soon as possible”
Final delivery deadline for the old part	Clarifies when the supplier should stop manufacturing the old part	Advance notice 1–2 weeks before ECO approval	Clearly state the final order date and the last acceptable receipt date. Agree in advance that old-part deliveries after that date will not be accepted
Policy for handling old-part inventory	Whether write-off compensation, return acceptance, or Last Time Buy applies for the old part	Negotiated before ECO approval, finalized at the same time as ECO approval	Ideally, change-notice clauses and write-off compensation clauses are built into the procurement contract (supplier agreement) in advance
Qualification/quality confirmation requirements	Clarifies the quality-testing and supplier-qualification requirements for the new part/specification	Before ECO approval (early, to secure time for qualification)	Send PPAP (Production Part Approval Process) or ISIR requirements together with the change notice

8.2　Supplier Portal Integration Design

In large-scale manufacturing, electronic ECN distribution via a supplier portal (SAP Business Network / Ariba Supply Chain, etc.) is becoming standard. The design points for portal integration are organized below.

• Automatic ECN distribution: When an ECO is approved in PLM or SAP S/4HANA, the ECN is automatically distributed to the affected suppliers (vendor masters linked to items on the BOM)

• Acknowledgment: Electronically confirms whether the supplier has reviewed and accepted the change content. An automatic reminder is sent to suppliers who have not yet confirmed

• Automatic inquiry of old-part inventory: At the time of ECO approval, a request is automatically sent via the supplier portal for a report on “the current volume of old-part inventory.” The volume is aggregated to project write-off loss in advance

• Change queries: A portal feature that lets suppliers ask questions about the change content. Q&A is managed linked to the change record

[External Case Study: Koller Kunststofftechnik (Catena-X/BMW Connection)]The value of a supplier portal is not limited to digitizing communication. Koller, a mid-size supplier, launched Catena-X-compliant software in 3 days, accelerated OEE calculation by 51%, reduced energy loss by 15%, achieved 100% visibility of production energy use, and even reached a proof of concept for exchanging traceability data with BMW. The change-notification infrastructure should be designed not as a “notification box” but as the gateway to standardized data exchange that includes quality, energy, and manufacturing results. (Officially published by Catena-X)

Chapter 9: Pitfalls and Principles for Success in Integration Design

9.1　Typical Failure Patterns in ECM×SCM Integration

Failure Pattern	Why It Happens	Resulting Cost/Impact	Preventive Measure
Mismatch between “design is complete” and “the shop floor still uses the old part”	Even when an ECO is approved in PLM, propagation to ERP/MES/suppliers is manual, causing a time lag	Shipment of products mixing new and old parts → risk of quality claims and recalls	Automate the entire chain of ECO approval → ERP BOM update → MES BOP update → supplier notification. Eliminate all manual steps
Change approval without impact analysis	The change is judged to be “simple from a design standpoint” and impact analysis is skipped	After approval, it turns out that “100 purchase orders were actually already placed for the old part” → additional cost is incurred	Make “impact analysis” a mandatory step in the design process for every ECO. Instantly list affected targets with automated tools
Incorrect effectivity setting	Set as “new BOM from September 1, 2026,” but a large amount of old-part inventory remained as of September 1	Old-part write-off loss occurs, or the old part is needed but cannot be used for manufacturing because “the system shows the new BOM”	Run an inventory-depletion simulation before setting the effectivity condition. Set the effective date to the day after the predicted date when inventory is nearly zero
Delayed notification to suppliers	ECNs are manually sent by email/PDF, causing a time lag as staff work through their queue	Write-off compensation is claimed by suppliers who continued manufacturing the old part after the change	Build system integration that automatically distributes the ECN to suppliers at the same time as ECO approval
Change not communicated to the spare-parts team	ECM updates only the EBOM and MBOM; propagation to the service BOM is not included in the design	The discontinued part remains listed in the service catalog, and customers/service staff continue to order it	Include updating the service BOM and spare-parts catalog as a mandatory checklist item within the scope of every ECO

[External Case Study (Counter-Example): Zyno Medical Class I Recall (FDA, 2025)]Change linkage is not dangerous only when notification is slow. When an unverified (V&V-incomplete) change reaches the market together with its effectivity condition, a recall goes straight to stopping use, returning, locating, and arranging replacement at the individual serial-number level. The FDA classified this incident as the most severe recall category (Class I). It stands as a concrete example, within the failure patterns, of the consequences of failing to link “verified” status with “effectivity.” (Officially published by the FDA)

9.2　Five Principles for Successful ECM×SCM Integration

Principle ①: Make the “Change Number” the Linkage Key for All Change Information

Design so that the “change number” functions as the single identifying key across PLM, ERP, MES, and the supplier portal. Enforcing the organization-wide rule that “a change without a change number is not a change (direct edits are prohibited)” is the foundation of traceability.

Principle ②: Make Impact Analysis “Automatic”

Build a mechanism that, when an ECR/ECO is raised, automatically lists the “BOMs, purchase orders, production orders, inventory, and suppliers” affected by that part without manual effort. As long as impact analysis remains a process that “staff investigate by hand,” it is impossible to achieve both speed and accuracy.

Principle ③: Set Effectivity Conditions in Coordination with Inventory and Planning

The effectivity condition (switchover date/switchover lot number) should not be decided by the design department alone, but calculated and set together with “the current inventory volume, open orders, and production plan at that point in time.” A structure is needed in which SCM staff participate in the ECO approval flow and agree on effectivity conditions grounded in reality.

Principle ④: Make Change Propagation “Automatic and Instant”

The event of ECO approval should automatically cascade, like dominoes, to updates in ERP (BOM update), MES (BOP/work-instruction update), the supplier portal (ECN issuance), and the service BOM. A process in which “someone manually updates each system after approval” is the point where the linkage breaks down.

Principle ⑤: Build Reverse-Direction Feedback (SCM→ECM) into the Design

ECM is not a one-way street from “design → SCM”; the feedback loop from “SCM → design” is equally important. Design a mechanism that quickly captures feedback as ECRs, such as “this part is being discontinued by the supplier, so a design change is needed (purchasing → design),” “this part is hard to use in this process (manufacturing → design),” and “this spare part can no longer be procured (service → design).”

9.3　The Maturity Model for ECM×SCM Integration

Maturity	Level Definition	Typical State	Next Step
Level 1 (Disconnected)	ECM and SCM are managed completely separately	Change notices are by email, paper, or word of mouth. BOM changes are managed in Excel. Supplier notification is by phone	Start by standardizing the ECM process (defining ECR/ECO and the approval flow)
Level 2 (Basic Linkage)	Changes are managed in ECM, then manually reflected in the ERP BOM	BOM changes are managed with change numbers in SAP CC01/CS02, but ERP reflection is manual, done in a weekly batch	Automate ERP BOM updates. Automatically list the scope of impact (leveraging CS15)
Level 3 (Automatic Propagation)	ECO approval is automatically reflected in ERP and MES	Automatic BOM update from PLM → ERP. Automatic distribution of the new BOP to MES. Automatic ECN issuance to suppliers	Automatically set effectivity conditions in coordination with the SCM plan. Automate write-off loss projection
Level 4 (Prediction and Optimization)	Impact analysis and switchover optimization are linked with SCM data	When a change is requested, an SCM simulation runs automatically, automatically presenting “the optimal switchover date and a plan to minimize write-off loss”	Leverage AI/ML: improve the accuracy of predicting change impact based on historical ECO patterns
Level 5 (Digital Thread)	Design changes are linked with a digital twin of the entire supply chain	Design changes are reflected in the product’s Digital Twin, and the impact across the entire supply chain is visualized through real-time simulation	Realize the Digital Thread: design → manufacturing → procurement → service connected by a single data stream

End

9.4　Overview of External Evidence-Based Case Studies (Primary-Source Basis)

This section provides an overview of external, primary-source-based case studies that substantiate the design principles in this guide. All are qualified with “per official disclosure” or similar, and are offered as evidence for reading each chapter of this guide not as “theory,” but as “designs already established externally.”

Case Study / Entity	Domain / Relevance	Key Results (as Published)
Catena-X Quality Mgmt (BMW/Bosch/DENSO and others)	Supplier quality, reverse-direction linkage (Chapters 7, 8, 9)	Defect detection an average of 4 months earlier / new connections in 5 weeks / suspects narrowed from 1.4 million units to 14
Koller Kunststofftechnik (Catena-X/BMW)	Supplier portal, visibility (Chapter 8)	Implemented in 3 days / OEE calculation 51% faster / energy loss reduced 15%
Cytiva (Rockwell)	Closed-loop manufacturing, factory start-up (Sections 0.4/6)	Factory construction under 18 months / efficiency improved 10–20% / time-to-market 7 years → 3–4 years
NIST Digital Thread	Standards-based digital thread (Sections 0.6/9)	Shortened design–manufacturing lead time and improved final quality (pilot)
Eli Lilly (Rockwell)	Regulatory, IT/OT, serialization (Section 7.3)	Finished-product traceability via integration of vision/high-speed control/events/ERP
Siemens Amberg	Highly mature factory, horizontal/vertical integration (Sections 0.4/0.6)	50 million data points leveraged / 99.9990% quality / cycle-time improvement via digital twin
Rolls-Royce DIREKT	Lifecycle digital thread (Sections 0.6/7)	Instant reflection of design changes / major lead-time reduction targets
Zyno Medical (Counter-Example, FDA)	Failure = market release of an unverified change (Section 9.1)	Class I recall / stop-use, return, and location confirmation at the serial-number level

* These case studies show four points: ① supplier integration is not about digitizing notifications but about “the round-trip of standardized data” (Catena-X/Koller); ② closed-loop manufacturing shows up not as a shortened approval process but as “factory performance” (Cytiva/Siemens); ③ the Digital Thread is the subject of “open standards” (NIST/Rolls-Royce); ④ in regulated industries, the linkage of “verified change × effectivity” is what separates out recall risk (Eli Lilly/Zyno).