Engineering change, from the request to the released drawing.
A change touches drawings, the bill of materials, open orders, suppliers and the document register. We build agents that carry the paperwork through each system. The engineer still signs the release.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
AI agents for engineering change do the paperwork around a change, not the engineering. A change request arrives. Someone finds every drawing and model it touches, checks where the part is used, lists the open orders and the stock at risk, drafts the change notice, updates the bill of materials and tells the suppliers who hold the old revision. Each step lives in a different system. A missed one means a part built to the wrong revision.
We build that path with you as one workflow. The agent gathers, drafts and updates. Your engineer reviews and signs the release. Document control keeps one answer to the question "which revision is current, and who released it".
What changes for your engineers
- Engineers review a prepared change pack instead of assembling it.
- Document control sees each release with its signature and its reason.
- A drawing reaches only the suppliers approved for that part. Any other send is refused and recorded.
Drawings and models are data that would hurt if they leaked. The workflow can run in your building, on one small machine, and nothing leaves unless you allow it. The quality page covers the inspection and evidence side of the same part.
One change request, from the ticket to the released revision.
This workflow is designed and has not run in the sandbox yet. One change touches five systems and one supplier. The part and the supplier are examples.
- 01Ticketing
Take the change request from the engineering queue. Receive a credential for this change only.
- Who approves
- No approval on this step
- On the record
- credential issued · one change
- 02Source control
Find the drawings and models the change touches, at their released revision.
- Who approves
- No approval on this step
- On the record
- read-revisions · allowed
- 03ERP
List the assemblies, open orders and stock that use the affected part.
- Who approves
- No approval on this step
- On the record
- where-used · allowed
- 04Documents
Draft the change notice and the new revision of the bill of materials.
- Who approves
- No approval on this step
- On the record
- draft-change-notice · allowed
- 05Documents
Release the new revision. The step waits until the responsible engineer approves it.
- Who approves
- Responsible engineer
- On the record
- release-revision · approved by engineer
- 06Email
Try to send the new drawing to a supplier not approved for this part. The step is refused.
- Who approves
- No approval on this step
- On the record
- send-drawing · refused · supplier not approved
- 07ERP
Update the bill of materials in the ERP to match the release.
- Who approves
- No approval on this step
- On the record
- update-bom · allowed
In short
- What does a missed drawing cost?A supplier builds to the old revision. The agent lists every document and supplier the change touches before the engineer signs.
- Can an agent release a drawing?No. It prepares the release. The responsible engineer approves it, and the approval is on the record with a name.
- Can a drawing leave for the wrong supplier?Not within the permission for the job. A send to an address outside the approved list is refused, and the reason is recorded.
- Can we show a customer which revision we built to?Yes. The record shows each release, who approved it, and which supplier received which revision. An outside party can check it without us.
Engineering workflows we build, and the state of each.
Two of these run in the sandbox today, both on the supplier side. The change notice, document release, drawing transfer and bill of materials sync are designed. We scope deviations and software release notes with you.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Designed
Engineering change notice
Request, affected documents, where-used check, change notice, signed release and the ERP update. The steps are shown above.
See the steps - Designed
Document release and revision control
The agent checks that each document in a release names a reviewer and an approver. Document control approves the register entry.
See the steps - Designed
Drawing transfer to suppliers
The agent sends a drawing only to suppliers approved for that part and revision. Any other address is refused, and the refusal is recorded.
- Designed
Bill of materials sync with the ERP
After a release, the agent updates the ERP bill of materials and lists each difference it could not resolve.
- Built
A supplier quote on one order line
A supplier's agent prices one line and reaches for your full bill of materials. That read is refused at your company boundary.
Run it in the sandbox - Built
A late part with a drawing request
The supplier follow-up run includes a drawing sent to a new address. The send is refused.
Run it in the sandbox - On request
Deviations and concessions
- On request
Release notes for software changes
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not make engineering decisions. Whether a change is right is for your engineers.
- It does not replace your PLM, your CAD vault or your document system. It works between them and the ERP.
- It reads documents, file names and metadata. It does not read or change the geometry in a model.
- The engineering change workflow is designed, not yet run in the sandbox.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Questions and answers
Tell us about one workflow.
Bring one recent engineering change and the systems it crossed. We will say whether an agent should carry it, and what the first step costs. Fixed price, quoted after one call.
A senior member of the team replies within two business days.