ECN cycle time down from 11 days to 5, missing process documents under 1%

Every engineering change notice (ECN) meant updating drawings, process sheets, inspection standards, the BOM and supplier notifications across 6 departments. Process engineers spent much of their time comparing versions and chasing signatures, and missed changes caused quality problems every quarter.

The company was preparing to take on platform programs for EV customers, who audit change responsiveness and document consistency far more strictly.

We organized the work around the ECN process. Finding the impact scope, updating documents and checking consistency were handed to Agents; people kept judgment and sign-off.

• Impact analysis Agent: reads the change notice and, from PLM and BOM relationships, lists every affected drawing, process sheet, inspection standard and open order
• Document update Agent: drafts revised process sheets and inspection standards from the change content, marks each edit and hands them to the process engineer for confirmation
• Consistency check: before release, drawing, process sheet and BOM versions are compared automatically, and any gap or conflict is blocked
• Supplier notification drafts are generated automatically and sent with one click once procurement confirms

The integration with PLM and ERP is read plus draft write-back only; formal release still happens inside PLM, so there is a single source of truth. For drawings, only the title block and version number are extracted; the drawing body is never sent to the model.