AI for Engineering Knowledge Management

How to Automate the Engineering Change Order Process

How to Automate the Engineering Change Order Process

How to Automate the Engineering Change Order Process

Automate the engineering change order process: run a multi-level where-used for impact analysis, pick fast or full track, and test the result on 20 closed ECOs.

·

⏱

6 min read

Michelle Ben-David

Product Specialist, Leo AI

Product Specialist, Leo AI

Mechanical Engineer, B.Sc. · Ex-Officer, Elite Tech Unit · Aerospace & Defence · Medical Devices

Mechanical Engineer, B.Sc. · Ex-Officer, Elite Tech Unit · Aerospace & Defence · Medical Devices

Michelle Ben-David is a mechanical engineer and Technion graduate. She served in an IDF elite technology and intelligence unit, where she developed multidisciplinary systems integrating mechanics, electronics, and advanced algorithms. Her engineering background spans robotics, medical devices, and automotive systems.

Cover image illustrating How to Automate the Engineering Change Order Process: Automate the engineering change order process: run a multi-level where-used for impact analysis, pick

BOTTOM LINE

Automate three steps of the engineering change order process: a multi-level where-used for impact, a fast or full track rule, and the reviewer package. On the 8-item example a single-level search misses 4 items, so test the walk on 20 closed ECOs first. Leo runs that where-used across your PDM and PLM.

Three steps of the engineering change order process can be automated: finding every affected item, choosing the fast or full track, and assembling the reviewer package. Approval stays with a person.

If your team runs ECOs in Windchill, Vault or a similar PLM, the first step is where mistakes start. A part change also changes each assembly above it, and a single-level where-used lists only the first layer.

A change reaches more items than its drawing lists

Changing a part changes every assembly that contains it. Autodesk's Vault documentation gives the Inventor case: changing a part also changes the parent assembly, so the guidance is to add all affected files to the change order. (Vault change order rules)

Vault also limits each file to one active change order at a time. If ECO-2 misses an assembly that open ECO-1 already holds, that assembly cannot join ECO-2 until ECO-1 is closed or cancelled.

Windchill flags the same exposure with a pending change icon on any object that has an unresolved change request or an incomplete change notice against it. (PTC Windchill change management)

The worked example below shows the size of the gap: a single-level where-used finds 4 of the 8 items the change must touch.

IN PRACTICE

It integrates directly with PLM and existing workflows, making past designs, standards, and calculations instantly available. The result is fewer errors, faster decision-making, and a more consistent process across teams.

- Sergey G., Board Member

Seven steps carry a change from problem report to audit

PTC's Windchill help describes this example scenario. NASA's handbook treats configuration change management as one of five configuration management elements, next to identification and verification. (NASA handbook, section 6.5)

  1. A user creates a problem report against an end item.

  2. Change Administrator I reviews the problem report, creates the change request and runs the impact analysis.

  3. The administrator records the track. Fast track changes have low impact and cost, and the cost threshold is set by company policy.

  4. Full track changes go to the Change Review Board, typically design engineering, manufacturing engineering and quality assurance.

  5. Approval produces a change notice. A full track notice needs Change Implementation Board approval before any work starts.

  6. Data creators edit parts and documents as the change tasks direct, and reviewers check each task.

  7. Change Administrator III audits the resulting documentation and approves or rejects the change notice.

Steps 2, 3 and 6 carry the manual lookup work, so automate those first. The fields behind each step are covered in the ECO data model.

Worked example: a 3-level where-used finds 8 items, not 4

The BOM below is an illustrative example built for this post, not customer data. The M8 bolt F-M8-30 is discontinued, and the change must reach every item that contains it.

  1. List the direct parents of F-M8-30: SUB-A, SUB-B, SUB-C and ASM-3. This single-level where-used returns 4 items.

  2. Walk up one level from each parent. SUB-A, SUB-B and SUB-C add ASM-1 and ASM-2.

  3. Walk up again. ASM-1 and ASM-2 add TOP-X and TOP-Y.

  4. Stop when no item has a parent. The result is 8 items across 3 levels, so the single-level search misses 4 of 8 (50%).

  5. Multiply quantities up each path to get bolts per unit.

Affected item

Level

F-M8-30 per unit

SUB-A

1

4

SUB-B

1

2

SUB-C

1

6

ASM-3

1

6

ASM-1

2

6

ASM-2

2

8

TOP-X

3

14

TOP-Y

3

8

The walk is a breadth-first search over the parent-child relations your PDM or PLM already stores. The result is only as complete as those relations: a bolt named in a drawing note instead of a BOM line does not appear.

Test the automation on 20 closed ECOs in one week

Run these tests on your own data before the automation touches a live change.

  1. Pick 20 closed ECOs from the last 12 months. Include 5 that were followed by a second ECO on the same assembly.

  2. Run the multi-level where-used on each changed part as of the ECO date. Pass: every item the original ECO touched appears in the result.

  3. Check the 5 follow-up ECOs. Pass: the first run lists the assembly that needed the second change, 5 of 5.

  4. Classify each extra item in the results as changed or unchanged. Pass: a reviewer decides each one in under 5 minutes.

  5. Time the reviewer package from change request to ready. Pass: the median is at or below your current median with no new misses.

For a replacement part, also check it against your approved vendor list before the change notice names it.

Leo runs the where-used and links the sources

Leo connects to your PDM and PLM as an intelligence layer, so the change request stays where it is. You give Leo the part number, for example F-M8-30, and ask which items contain it.

Leo reads the parent-child relations in your PDM or PLM, plus the network drives and ERP records you connect. It returns the multi-level list with quantities per unit, as in the table above, with a link to the source file for each line.

It also finds earlier changes to the same part, so a reviewer sees precedent next to impact. For a substitute, geometric search finds standard parts by shape. The impact discovery post shows what an agent reads.

Leo does not approve or release a change. The Change Review Board still signs, and the list is only as complete as the relations stored in your PDM or PLM. Data handling is on the security page.

FAQ

It records a change request, lists the affected items, routes approvals and tracks the tasks that implement the change. Windchill ships change requests, change notices and change tasks as out-of-the-box change objects, and Vault provides change orders.

Record the change as a request, run the impact analysis and decide the track by your company's cost threshold. Implement through the tasks on a change notice, then audit the documentation before closing it.

It removes the lookup work: the multi-level where-used, the track decision and the reviewer package. The sign-off stays with the Change Review Board.

In Windchill, the change request records the formal analysis, proposed solutions, cost and justification used to decide whether to proceed. The change notice is the work authorization that lists the tasks to implement the change.

Run the where-used up to the top-level item of every line, as TOP-X and TOP-Y show in the example. Send full track changes to a board that includes design, manufacturing and quality, and in Vault confirm no affected file sits on another active change order.

Leo takes a part number, reads the parent-child relations in your connected PDM and PLM, and returns the multi-level list with quantities and source links. Approval and release stay in your PLM.

  1. About Change Management, PTC Windchill Help Center, accessed 2026-11-03

  2. Request Change, PTC Windchill Help Center, accessed 2026-11-03

  3. Rules and Best Practices for Using Change Orders with Files, Autodesk Vault Help, accessed 2026-11-03

  4. 6.5 Configuration Management, NASA Systems Engineering Handbook, accessed 2026-11-03

Test it on your own CAD files

See a multi-level where-used for one of your own parts.

Ask an applications engineer how Leo reads your PDM or PLM, or try a part number from your last ECO and compare the result with what that change touched.

#1 New AI Software Globally - G2 2026

Enterprise-grade security

Trusted by world-class engineering teams

Recommended

Leo AI logo

Subscribe to our engineering newsletter

Be the first to know about Leo's newest capabilities and get practical tips to boost your engineering.

Need help? Join the Leo AI Community

Connect with other engineers, get answers from our team, and request features.

Gartner logo
G2 badges: Top 25 AI Products, 2026; Users Love Us; Top 25 Rookies of the Year, 2026
CB Insights logo
#1 New Software

Globally

All Industries

#12 AI Tool

Worldwide

G2 2026

Contact us

50 Milk Street

Boston, MA 02109

United States

Leo AI on LinkedIn
Leo AI on YouTube
Leo AI on Reddit
Leo AI logo

Subscribe to our newsletter

Be the first to know about Leo's newest capabilities and get practical tips to boost your engineering.

Need help? Join the Community

Connect with other engineers, get answers from our team, and request features.

Gartner logo
G2 badges: Top 25 AI Products, 2026; Users Love Us; Top 25 Rookies of the Year, 2026
CB Insights logo
#1 New Software

Globally

All Industries

#12 AI Tool

Worldwide

G2 2026

Contact us

50 Milk Street

Boston, MA 02109

United States

Leo AI on LinkedIn
Leo AI on YouTube
Leo AI on Reddit
Leo AI logo

Subscribe to our engineering newsletter

Be the first to know about Leo's newest capabilities and get practical tips to boost your engineering.

Need help? Join the Leo AI Community

Connect with other engineers, get answers from our team, and request features.

Gartner logo
G2 badges: Top 25 AI Products, 2026; Users Love Us; Top 25 Rookies of the Year, 2026
CB Insights logo
#1 New Software

Globally

All Industries

#12 AI Tool

Worldwide

G2 2026

Contact us

50 Milk Street

Boston, MA 02109

United States

Leo AI on LinkedIn
Leo AI on YouTube
Leo AI on Reddit
Leo AI logo

Subscribe to our engineering newsletter

Be the first to know about Leo's newest capabilities and get practical tips to boost your engineering.

Need help? Join the Leo AI Community

Connect with other engineers, get answers from our team, and request features.

Gartner logo
G2 badges: Top 25 AI Products, 2026; Users Love Us; Top 25 Rookies of the Year, 2026
CB Insights logo
#1 New Software

Globally

All Industries

#12 AI Tool

Worldwide

G2 2026

Contact us

50 Milk Street

Boston, MA 02109

United States

Leo AI on LinkedIn
Leo AI on YouTube
Leo AI on Reddit

© 2026 Leo AI, Inc.