qAI agent for drawing release
AI agent for drawing release: who signs and who receives it
An AI agent for drawing release prepares the new revision and its paperwork. Your engineer signs it, and only approved suppliers receive it.
4 min readRunning it, Evidence
by Grisha Pertaia
- session
- credential
- draft
- notify
- notify
- route
- intake
- write
- draft · refused· outside permission
A drawing release has two moments that matter. One is the signature: a responsible engineer says this revision is the one to build to. The other is the send: the new revision reaches the people who will build to it, and nobody else. An AI agent for drawing release can do most of the work between those moments. It should do neither of them alone.
This post explains the release part of the engineering change workflow on our engineering page. It covers what the agent prepares, where a mistake costs money, which steps your people keep, what the agent is refused, and what you can check afterwards. The workflow is designed. It has not run in the sandbox yet, and the steps are how we would build it with you in a pilot.
The paperwork around one change
A change request lands in the engineering queue. Before anyone can sign, someone has to assemble the pack. The pack draws on several systems at once:
- the drawings and models the change touches, at their current released revision, from your vault or source control;
- the assemblies, open orders and stock that use the affected part, from the ERP;
- the change notice and the new revision of the bill of materials, drafted in your document system;
- the list of suppliers who hold the old revision and are approved for the part.
The agent collects these for one change, under a credential for that change only. It drafts the notice and the bill of materials revision, and it lists every document and supplier the change touches. That list is what your engineer reviews.
Where a wrong step costs money
The costly mistakes in this workflow sit in the paperwork that follows the engineering, not in the engineering itself.
A drawing left off the pack. A supplier who never hears about the change builds to the old revision. The parts arrive, fail inspection, and the cost is the batch, the delay and the second order.
A bill of materials that does not match the release. Purchasing orders against the ERP, not against the drawing. If the two disagree, the wrong part is bought with a correct purchase order.
A drawing sent to the wrong place. Drawings and models are data that would hurt if they leaked. A send to a supplier who is not approved for the part is a disclosure, whatever the intent.
The two steps your people keep
The release. The new revision waits until the responsible engineer approves it. The agent prepares the pack and stops. The approval goes on the record with the engineer's name, not a role. If the engineer rejects the pack, that decision is recorded too.
The register. Where your document controller keeps the register, the issue waits for that person as well. The document control workflow checks that each revision names its reviewer and approver before it reaches the controller, and marks the superseded copy instead of deleting it.
You decide which other steps wait for a person. A send to a new supplier, a change to a part used in many assemblies, an update to a controlled drawing: each can be made a step that pauses. Ares does not decide which steps are sensitive. You do.
What the agent is refused
- allowed
Read the affected drawings at their released revision
- allowed
List where the part is used, with open orders and stock
- allowed
Draft the change notice and the new bill of materials
- allowed
Send the released drawing to a supplier approved for the part
- refused
Send the drawing to a supplier not approved for the part
- refused
Write the new revision over the released one
- refused
Release the revision without the engineer's approval
- redacted
A hidden instruction in a supplier note, struck out at the door
The approved-supplier list for the part is part of the credential for this change. A send to any other address fails at that list, whoever asked for it. That includes a supplier's note with a hidden line that asks for the drawing to go elsewhere: the line is struck out before the agent reads it, and the send would fail anyway.
What you can check afterwards
The record holds each step: the credential, each document read, the where-used list, the draft notice, the release with the engineer's name, each send with the supplier who received which revision, and each refusal with its reason. When a customer asks which revision you built to, you answer from that record.
You can export it and check it offline with the open verifier. The guarantees page says where the record stops: it shows what the agent did, not whether the change was the right one.
What it does not do
- Whether a change is right is for your engineers. The agent carries the paperwork, not the design decision.
- It reads documents, file names and metadata. It does not read or change the geometry in a model.
- Your PLM, CAD vault and document system stay. The agent works between them and the ERP.
- The engineering change workflow is designed, not yet run in the sandbox. The closest run today is supplier follow-up, where a drawing send to a new address is refused.
Related notes
- illustration
- session
- credential
- write
- lookup
- write · refused
- lookup
4 min read
Non-conformance evidence with AI agents: who signs it
Non-conformance evidence with AI agents: what the agent gathers, why test results stay read-only, who signs the disposition, and how an auditor checks it.
- illustration
- session
- credential
- notify · refused
- score
- lookup
- lookup · redacted
4 min read
AI agent for MRO release paperwork: what the inspector signs
An AI agent for MRO release paperwork can assemble the pack for a repaired unit. The inspector still signs. The steps, the refusals and the record.