qAI agent for MRO release paperwork
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.
4 min readRunning it, Agent design
by Grisha Pertaia
- session
- credential
- notify · refused· outside permission
- score
- lookup
- lookup · redacted· client identifiers
- lookup
- route
- draft · human review· sent for review
A repaired unit goes back to its owner when two things are true: the paperwork is complete, and a certifying inspector has signed the release. An AI agent for MRO release paperwork can take most of the assembly behind that signature. It cannot give the signature, and the workflow is built so that it never tries.
This post answers one operations question: which parts of a repair release pack can an agent prepare, and which stay with a person?
The workflow is designed. It has not run in the sandbox yet, and the steps below are how we build it in a pilot. The aerospace page lists it beside the other aerospace workflows, with the state of each.
Where the pack comes from
The pack draws on four places. The closed work order sits in your maintenance or ticketing tool. The test results and inspection notes sit in your document store. The part number, the serial and the parts fitted sit in your ERP. The customer's covering note arrives by email.
Today a person opens each one, checks that they agree, and builds the pack by hand. The agent does that collection and that cross-check. It drafts the pack, routes it to the inspector, and drafts the repair invoice against the order.
Where a wrong action costs money
Each of these costs time, rework or a customer's confidence.
- A serial that does not match the order. The pack comes back, the unit waits, and someone rebuilds the pack.
- A document from the wrong unit. A history attached from another customer's unit is a disclosure to one customer and a records error for the other.
- An instruction that should not be followed. A covering note can carry a line that asks for a step to be skipped. A person ignores it. An agent that acts on text must be stopped from acting on it.
The workflow, step by step
- Step 1
A credential for one unit
The agent takes the closed work order and receives a credential for this unit and this customer only. It expires when the job ends.
- Step 2
Results read
It reads the test results and the inspection notes for the unit.
- Step 3
Parts checked
It checks the part number, the serial and the parts fitted against the order in the ERP.
- Step 4
The note read at the door
The customer's covering note is read before the agent sees it. A line that tells the agent to skip the final test is struck out.
- Step 5
Another unit refused
The agent tries to attach the history of another customer's unit. That unit is outside the permission, so the step is refused.
- Step 6
The inspector signs
The draft pack waits until the certifying inspector reviews it and signs.
- Step 7
Invoice drafted
The repair invoice is drafted against the order.
The refusal in step 5 does not depend on the agent's judgement. The credential for this job names one unit and one customer. Records for any other unit were never in it, so the step fails whatever reason the agent had for it. The refusal and its reason go on the record.
The step the inspector keeps
The certifying inspector signs the release, as today. The agent prepares the pack and stops. If a check fails, the agent names the mismatch and the pack waits. The inspector decides what happens next.
You decide which other steps wait for a person, such as the note back to the customer. The record shows who approved each one.
- allowed
Reads the work order, the results and the inspection notes
- allowed
Checks the part number, the serial and the parts fitted against the order
- redacted
Strikes out a hidden instruction in the customer's note
- session
Drafts the release pack and the repair invoice
- human review
Reviews the pack against the unit
- human review
Decides what happens when a check fails
- human review
Signs the release and answers for it
What gets refused
Two kinds of step are refused. The first kind is outside the permission for the job: another customer's records, or a controlled drawing sent to an address the job does not allow. The second kind is a statement only a person can make, such as a signature.
You mark the drawings that are controlled, and the permission holds to what you marked. Ares does not decide what is export-controlled, and it does not certify export compliance.
The same rule runs through the quality document pack workflow. There, the agent tries to copy an earlier certificate onto a lot that has none on file, and the step is refused. In both workflows the agent collects documents. It never writes one.
What you can check
Every step above leaves a line on the record, including the struck-out line and the refused attachment, each with its reason, and the inspector's signature with a name. Your customer or your auditor can check that record with the open verifier, without us. The guarantees page says what the record holds and where it stops: it shows what the agent did, not whether a business rule was wise.
What it does not do
- It does not sign a release, a certificate or a quote.
- It does not replace your maintenance records, your ERP or your quality system. It works between them.
- Inspection covers stated patterns and languages. A covering note in an unlisted language can carry an instruction past it. The credential for one unit still limits what the agent can reach.
- It has not run in the sandbox. The closest run today is supplier follow-up.
Related notes
- illustration
- session
- credential
- write
- notify
- file · human review
- write
6 min read
Evidence, not logs: what an auditor can actually verify
A log is a file the operator controls. A trace adds structure, not independence. Evidence is a record more than one party confirmed before it was written, that an auditor can check against another copy without trusting the vendor.
- illustration
- session
- credential
- notify
- file
- route
- file
6 min read
Verify an AI agent audit trail yourself: our replay pack verifier is open source
The replay pack and the open-source verifier we said were planned have shipped. One zip per job, checked offline with code you can read: what it checks, what a pass does not prove, and how to run it.