Main site

Manufacturing AI agent · Engineering change

Engineering-Change & Configuration-Integrity AI Agent

Carry a change through review, then check whether the same revision and effectivity are live in the ERP routing, the MES work instruction and the supplier portal — and flag where they are not.

Typical delivery
4–6 weeks
Deployment
Your stack
Authority signs
Pre-effectivity
After launch
Agent Care

What this agent does

Checks across the systems, not inside one

In

  1. 01

    A change is raised, and the parts, documents, routings and open orders it touches are assembled with it.

  2. 02

    A packet arrives thin, and the missing categorisation, justification and implementation plan are named.

Reason

  1. 03

    A change waits on one over-subscribed reviewer, and the queue is chased there, not across the board.

  2. 04

    A change is released in PLM, and the ERP change master, the MES routing and the work instruction are read back.

  3. 05

    An effectivity date passes, and the revision the cell is building is compared with the one the order carries.

Decide

  1. 06

    An effectivity type differs between systems — date here, serial there — and the mismatch is raised, not averaged.

  2. 07

    An open order cites the superseded drawing, and the supplier side is in scope — SAE EIA-649C (2019) puts it there.

Out

  1. 08

    A divergence is found, and it is routed with both records behind it to the named change authority.

  2. 09

    Execute write actions only inside the approval boundaries agreed during implementation.

Product statement

The agent reports where the change stands; ISO 10007:2017 leaves the verification with a dispositioning authority, and a named person dispositions the stock.

Example workflow

One change order, raised to landed

  1. 1Change request raisedPLM change request, supplier request, deviation or customer-driven change
  2. 2Impact assembledAffected parts, documents, routings, work instructions, open orders and stock on hand
  3. 3Systems comparedRevision, effectivity type and date per system, gaps and confidence
  4. 4Controls appliedRevision-string checks, effectivity-type comparison, open-order checks and confidence threshold

No human action required

Stages 1 to 4 run unaided, and nothing is released at any of them — the agent is reconciling, and the authority's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold
High confidence

Goes to the change authority to release.

Low confidence

Adds a configuration-lead read first.

Authority release

The change is held with its status per system, its open gaps and the confidence.

Approve · Hold · Send to board review

Approved — released for implementation

  1. 6Downstream systems updatedOnly where write access and approval policy allow it
  2. 7Outcome evaluatedTime to landed, systems behind at effectivity, and divergence found after build

Holds

Every change the authority holds is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Deciding a change may go ahead.
    • Dispositioning stock built to the old revision.
    • Waiving a customer's approval of a change.
    • Setting the effectivity date a change takes.

  • Automation boundary

    Agent acts unaided

    • ✓Assemble the change packet from the systems of record.
    • ✓Carry each revision forward with the system it was read in for the named owner.
    • ✓Compare revision, effectivity type and date across systems.
    • ✓Mark the gaps the authority should weigh, and hold the change.

    Any write happens inside the boundaries agreed at implementation, never ahead of release.

    • Judging whether a trial run is needed.
    • Closing a change while re-approval is open.
    • Granting or extending a deviation.
  • Changes to effectivity, routing or approval rules.

Example output

One change order, annotated

Everything the agent reports is attached to the system it was read in.

Configuration-status output · single change

Illustrative example
Change
Housing ECO · one plant
Finding
The work instruction still serves the revision this order supersedes
Revision live
Rev A
System of record
MES work instruction
Confidence
84%
Effectivity
Date here, serial in ERP

As received

Read from PLM, ERP and MES as they stand — nothing on this side is inferred by the agent.

Evidence used

  • Released change order
  • ERP change master
  • MES revision in force

Why this is flagged

The revision is released and this system is still serving the old one.

What the score decides

Below the configured threshold the change picks up a configuration-lead read first.

Action

ApproveHoldSend to board review

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

Every change

From the change order

03Reconciling

Compare beyond the PLM

Draw on the released order, the baseline the board agreed, and the systems the PLM does not reach.

01Approved path

Released is not the same as landed

Routine changes arrive with their status per system already assembled.

02Human review

Send review to the divergence

Open gaps and low-confidence comparisons are marked, so the authority's read starts where systems disagree.

04

Build an evidence trail

The change, the system it was checked in and the authority who released it stay on the order.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • PLM and change control

    • Teamcenter
    • Windchill
    • 3DEXPERIENCE
    • Arena

  • ERP and item master

    • SAP S/4HANA
    • Oracle
    • Infor
    • Dynamics 365

  • MES and shop floor

    • Siemens Opcenter
    • Plex
    • Tulip
    • Apriso
    • DELMIA

Agent

Change & configuration integrity

  • Reads each system
  • Compares the revision
  • Holds for release

  • Supplier portal and quality

    • Ariba
    • Coupa
    • SupplyOn
    • PPAP and drawing packages

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the line

Each control holds the one it surrounds, six in all. What no control holds is in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modePull reconciliation back to reporting-only when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, effectivity-rule and connector changes.Track
L4TraceabilityRecord each system read, the revision found, the gaps and the release time.Record
L3Authority releaseHold changes for the named authority; it governs release, not whether the release is right.Gate
L2Policy guardrailsTest comparisons against configured effectivity and baseline rules; a failure returns the change.Restrict
L1Confidence thresholdsRoute low-confidence comparisons to a configuration read before the authority sees them.Require review
Model coreStatus produced — revision and effectivity per system, open gaps and confidence
L1 – L2
Test whether a status may stand
L3
Puts the release in an authority's hands
L4 – L5
Keep the change and the system behind it
L6
Reverts to status reporting when signals degrade

How Nestack evaluates it

Evaluate the reconciliation across systems — not only the change inside the PLM.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the status the board sees

  1. E1Final-output evaluationDid each system's revision match what the order released?
  2. E2Step-level evaluationDid the agent read the right systems, baseline and effectivity rules?
  3. E3Tool evaluationDid it read and write the correct change and the correct system?
  4. E4Confidence calibrationDo low-confidence comparisons actually attract more holds?
  5. E5Slice evaluationHow does performance change across specific system pairs?
  6. E6Business outcomeHow many divergences were found only after parts had been built to the old revision?

Floor — the revision the cell builds

Failure modes

Where each failure originates in the agent

Seven failure modes, set where each one begins.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • NG-03

      Connector-limited view

      Systems outside the connector set go unread.

    Stage gathers

    Change orders, item masters, routings and portals

  2. 02 · Reasoning

    2 modes

    • NG-04

      Effectivity type ignored

      A date rule is read as equal to a serial rule.

    • NG-06

      Closed before it landed

      Workflow closure is taken as implementation.

    Stage proposes

    Revision, effectivity and gaps, with confidence

  3. 03 · Tool / write

    2 modes

    • NG-02

      Old stock left standing

      Superseded stock sits with no named disposition.

    • NG-05

      Supplier kept on the old

      Open orders keep citing the superseded drawing.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • NG-01

      False agreement reported

      Systems are called matched where they differ.

    Stage returns

    The status the authority releases the change from

  5. 05 · Change / Version

    1 mode

    • NG-07

      Silent scope regression

      A rule change narrows which systems are compared.

    Stage tracks

    Model, prompt, effectivity rules and connectors

  • Sev-1 · release recorded outside the boundary
  • Sev-2 · the cell builds a superseded revision
  • Sev-3 · a system is unreadable, change holds
See the complete Manufacturing failure-mode catalogue

Affected slices

One system can be behind while the rest agree

A company-wide agreement rate can look settled while one or two systems carry most of the divergence. Nestack reports the divergence rate by slice, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
MES work instructions6.7%3.5×Review
Supplier portal and open POs4.6%2.4×Review
Inspection and control plans3.3%1.7×Watch
ERP item master and BOM1.8%0.9×Normal

Bar: divergence-rate lift vs. ERP-item-master baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

Each cycle ends in a new case

A cycle closes when the change that never landed is a regression case the next release must pass. That suite is what the next order tracked is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Divergence rate rises in one system.

  2. 02

    Diagnose

    The cell that built to a revision the change board retired in April is read back until one cause is left.

  3. 03

    Improve

    The fix gets a number, and the change orders that raised it are held against it.

  4. 04

    Verify

    No release while a touched effectivity case is outstanding; it reruns until green.

  5. 05

    Learn

    The case stays for good, and the systems it spans are recorded against it.

  6. Learn → Detect

    The return edge. The next order is tracked against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, cross-system reconciliation, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Change workflow discovery and boundaries and boundary definition.Week 1
  2. 02PLM, ERP, MES and portal assessment.Week 1, Week 2
  3. 03Effectivity, baseline and route mapping and rule mapping.Week 1, Week 2
  4. 04Change-order ingest and system mapping.Week 2
  5. 05Cross-system comparison and binding.Week 2, Week 3
  6. 06Confidence scoring and gap routing.Week 3
  7. 07Authority release workflow.Week 3, Week 4
  8. 08ERP, MES and portal integration.Week 5
  9. 09Effectivity and revision cases.Week 4, Week 5
  10. 10Guardrails and release controls.Week 4
  11. 11Change-trail instrumentation.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne change board, one plantProductionProduction PLM, ERP and MESAdvancedMultiple plants / systems
Introduced at Pilot
Reconciliation across your systems✓✓✓
Authority release✓✓✓
Revision-agreement baseline✓✓✓
Introduced at Production
Reporting by system—✓✓
Release workflow in your systems—✓✓
Approved write-back—✓✓
PLM and ERP integration—✓✓
Introduced at Advanced
Multi-customer approval routes——✓
Multi-stage board approvals——✓
High change volume——✓
Multi-system configuration controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your change process and who sits on the board

    Change-order ingestion and system mapping

    Week 1

  2. 02Representative change orders, closed ones included

    Reconciliation baseline, revision and effectivity binding

    Week 2

  3. 03Your effectivity rules and customer approval routes

    Effectivity, baseline and customer-route mapping

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    PLM, ERP, MES and portal assessment, then integration setup

    Week 2

  5. 05Changes you would not want released

    Divergence cases and failure-mode testing

    Week 4

  6. 06What no release may go out without

    Confidence scoring, gap routing, guardrails and release controls

    Week 3

  7. 07A named change authority to release changes

    Authority release workflow, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

The weeks are drawn from the change board, so the fifth carries evaluation and the pilot together.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Change workflow discovery, route mapping and the automation boundary

W2System integration and the reconciliation baseline

W3Cross-system comparison, confidence logic and release controls

W4Evaluation suite, effectivity checks and failure-mode testing

W5Portal and MES integration, pilot changes and targeted corrections

W6One change board run under the configuration lead, then Agent Care handover

Reading the band
A bar runs across the weeks its work is named in and no further. The week 5 overlap is real.
At the end of W6
Validation closes on live orders, and Agent Care picks up monitoring.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Manufacturing AI agent

Build a configuration-integrity agent around your change board.

Show us one released change and where it should have landed. Ask the planner who cut last week's orders which revision his routing gave him — that answer is the one we keep current.

Typical delivery
4–6 weeks
Deployment
Your PLM, ERP and MES
Authority signs
Pre-effectivity
After launch
Agent Care available

Nestack Agents · Engineering change & configuration integrity

AGT-MFG-19 · Agent Care available after launch

Build a configuration-integrity agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your changes

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.