Agents that carry the paperwork behind every part you ship or repair.
Supplier follow-up, quote packs, conformance documents and repair records. Each one crosses your ERP, your document store and a mailbox. We build the agents that carry it, and a named person signs each 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.
The part is ready. The paperwork is not.
We build AI agents for aerospace suppliers and MRO shops (maintenance, repair and overhaul). The agents take the steps between your systems: they read the order, collect the test results, draft the pack and route it to the person who signs. Your inspectors and buyers keep every decision that carries their name.
In this trade the paper is part of the product. A part without its traceability does not ship, and a repair without its record does not return to service. Today a person builds each pack by hand, from the ERP, the document store, the work order and the supplier's email. The agent does that assembly. The person who answers for it still signs.
- The agent works only on the order, the part and the customer for that job.
- Drawings you mark as controlled stay inside the permission for that job. A send to an address outside it is refused, and the refusal is on the record. Ares does not decide what is export-controlled, and it does not certify export compliance.
- Every pack shows where each document came from, who approved it and when.
One repaired unit, from work order to signed release.
This workflow is designed and has not run in the sandbox yet. Each step names the system, who approves, and what goes on the record.
- 01Ticketing
Take the closed work order and receive a credential for this unit and this customer only. The credential expires when the job ends.
- Who approves
- No approval on this step
- On the record
- credential issued · one unit
- 02Documents
Read the test results and the inspection notes for the unit.
- Who approves
- No approval on this step
- On the record
- read-results · allowed
- 03ERP
Check the part number, the serial and the parts fitted against the order.
- Who approves
- No approval on this step
- On the record
- check-parts · allowed
- 04Email
Read the customer's covering email. One line in it tells the agent to skip the final test. The line is struck out before the agent reads it.
- Who approves
- No approval on this step
- On the record
- customer-email · redacted · hidden instruction
- 05Documents
Try to attach the maintenance history of another customer's unit. That unit is outside the permission for this job, so the step is refused.
- Who approves
- No approval on this step
- On the record
- attach-history · refused · outside permission
- 06Documents
Draft the release pack. It waits until the certifying inspector reviews it and signs.
- Who approves
- Certifying inspector
- On the record
- release-pack · signed by inspector
- 07Accounting
Draft the repair invoice against the order.
- Who approves
- No approval on this step
- On the record
- draft-invoice · allowed
In short
- What happens when a supplier date slips?The agent reads the reply, checks the open orders and drafts the change. Your buyer approves any new date before it reaches the ERP.
- Can an agent touch controlled drawings?Only the drawings you mark for that job, inside its permission. A send to an address outside it is refused and recorded.
- Who signs a release?The same person who signs it today. The agent prepares the pack. It never signs.
- Does it work with the systems we run?It works with your ERP, document store, mailbox, ticketing and accounting. The assessment lists which ones you have and what each needs.
Aerospace workflows, and the state of each.
Three of these run in the sandbox today. Release packs, conformance packs, quotes and change paperwork are designed. We scope non-conformance reports 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.
- Built
Supplier follow-up on late parts
The agent reads the order, chases the supplier and drafts the date change for the buyer.
Run it in the sandbox - Built
Quotes between two companies
A buyer's agent asks a supplier's agent for a quote on one order line. The permission narrows at the company boundary.
See the run - Built
Parts and tooling requisitions
The agent drafts the order and checks stock. An order above your threshold waits for a person. The sandbox run orders laptops; the same steps apply to parts and tooling.
Run it in the sandbox - Designed
Repair release packs
The workflow above: work order, results, parts fitted, and the release the inspector signs.
- Designed
Conformance and traceability packs
Certificates, material records and test results collected per shipment. The quality lead signs before it goes.
See the steps - Designed
RFQ and quote preparation
The request read, costs and drawings gathered, and a draft quote for the estimator to release.
See the steps - Designed
Engineering change paperwork
The change request, the drawings it touches and the parts list update, for the engineer to sign.
See the steps - On request
Non-conformance reports
The evidence for a non-conformance collected from each system and routed for a decision.
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 sign a release, a certificate or a quote. A named person does.
- It does not replace your ERP, your quality system or your maintenance records. It works between them.
- It does not decide what counts as controlled data. You set the permission, and the agent holds to it.
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.
Name one pack your team builds by hand. We will say whether an agent should build it, and what the first step costs. The first step is a workflow assessment. Fixed price, quoted after one call.
A senior member of the team replies within two business days.