One change request, carried from the ticket to the new revision.
The agent finds what the change touches, drafts the notice and lines up the update in each system. The change board approves the notice and its effectivity. A released revision is never written over.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for engineering change requests does the paperwork around a change, not the engineering. The impact list, the notice, the stock and open orders at the old revision, the bill of materials in the ERP: each sits in a different system, and each is a place where a part gets built to the wrong drawing.
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.
What a person still decides
- Whether the change goes ahead, and from which order or serial it applies.
- What happens to stock and work in progress at the old revision.
- Which steps, if any, stop needing approval later.
The engineering page shows the other engineering workflows. The rest of the library is on the workflows page, and the guarantees say what each control covers and where it stops.
One change request, five systems, one board approval.
The part, its revisions and the board are examples. Each step names the system, who approves and the line written to the record.
- 01Ticketing
Take the change request from the engineering queue and receive a credential for this change only. It expires when the change closes.
- Who approves
- No approval on this step
- On the record
- credential issued · one change
- 02Source control
Read the released drawing and model files for the part at revision B.
- Who approves
- No approval on this step
- On the record
- read-revision-b · allowed
- 03ERP
Run the where-used check: assemblies, open orders, work in progress and stock at revision B.
- Who approves
- No approval on this step
- On the record
- where-used · allowed
- 04Documents
Draft the change notice with the impact list and a proposed effectivity: use the stock at revision B, switch at the next order.
- Who approves
- No approval on this step
- On the record
- draft-notice · allowed
- 05Source control
Try to write the new files over revision B. Released revisions are read-only for this job, so the step is refused. The new files are staged as draft revision C for the board.
- Who approves
- No approval on this step
- On the record
- overwrite-revision-b · refused · released revision is read-only
- 06Ticketing
The change notice and its effectivity. The step waits until the change board lead approves it.
- Who approves
- Change board lead
- On the record
- approve-notice · approved by change board lead
- 07ERP
Update the bill of materials and the item revision in the ERP to match the notice.
- Who approves
- No approval on this step
- On the record
- update-bom · allowed
- 08Email
Draft the notice to each buyer who holds an open order at revision B.
- Who approves
- No approval on this step
- On the record
- draft-buyer-notice · allowed
The systems, by type
We name systems by type. Yours are named in the assessment.
Ticketing
Holds the change request and the board decision. The agent reads the request and posts the notice for approval.
Source control
Holds the released drawings and models. The agent reads them and adds a new revision. It cannot change a released one.
ERP
Answers the where-used question, and holds the bill of materials the agent updates after the approval.
Documents
Holds the change notice and the impact list the board reviews.
Carries the drafted notice to the buyers with open orders at the old revision.
The approval, the refusal, the record
- A person approves: The change notice and its effectivity. The step waits until the change board lead approves it.Whether a change goes ahead, and when, decides which parts are built to which drawing, so the board approves it and the agent waits.
- Refused: Try to write the new files over revision B. Released revisions are read-only for this job, so the step is refused. The new files are staged as draft revision C for the board.A released revision is the evidence of what was built, so the job may add revision C but never write over revision B.
- On the recordThe request, each file and order read, the notice, the refused overwrite with its reason, the approval with a name, and each ERP update. You can check it without us.
What goes on the record
- credential issued · one change
- read-revision-b · allowed
- where-used · allowed
- draft-notice · allowed
- approve-notice · approved by change board lead
- update-bom · allowed
- draft-buyer-notice · allowed
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not judge whether a change is right. Your engineers and the board do.
- It does not read or change the geometry inside a model. It works with files, revisions and metadata.
- It does not set the effectivity. It proposes one from the where-used list, and the board decides.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.