Agents for the work orders, permits and invoices around the field crew.
Inspection reports become work orders. Work orders need parts, permits and contractor packs. Field tickets become invoices. We build agents that carry each step across your business systems. Your planner approves spend above your threshold, and your crew lead signs off the field ticket.
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 crew finishes the job. The office finishes the paperwork.
We build AI agents for energy and utility operations: the business work around the field, not the control systems that run the network. An inspection report arrives as a document. Someone types it into the maintenance system, orders the part, chases the contractor and matches the invoice to the field ticket. Each step sits in a different system.
The agent takes those steps. It reads the report, opens the work order, drafts the requisition and checks the contractor invoice against what the crew recorded. Your planner, your supervisor and your controller approve the steps that carry their names.
- We do not connect agents to operational technology or the control room. The workflows on this page run in the business systems around them, and the access policy keeps control systems outside the permission.
- Customer addresses and account details stay inside the permission. Anything that leaves for a contractor is checked first.
- It can run on a machine in your own building, with the record kept on site.
One inspection finding, from report to closed work order.
This workflow is designed. The steps are how we build it in a pilot. It has not run in the sandbox yet.
- 01Documents
Take the inspection report and receive a credential for this asset and this job only.
- Who approves
- No approval on this step
- On the record
- credential issued · one asset
- 02Documents
Read the finding, the photos and the asset reference in the report.
- Who approves
- No approval on this step
- On the record
- read-report · allowed
- 03Ticketing
Open the work order in the maintenance system and link the report to it.
- Who approves
- No approval on this step
- On the record
- open-work-order · allowed
- 04ERP
Request a replacement part above the spend threshold. The order waits until the maintenance planner approves it.
- Who approves
- Maintenance planner
- On the record
- requisition · approved by planner
- 05Email
Send the job pack to the contractor. Customer names and account numbers are taken out on the way out.
- Who approves
- No approval on this step
- On the record
- job-pack · redacted · customer data
- 06Ticketing
Try to close the work order before the crew lead signs the field ticket. The step is outside the permission, so it is refused.
- Who approves
- No approval on this step
- On the record
- close-work-order · refused · no field sign-off
- 07Accounting
Match the contractor invoice to the signed field ticket and flag each difference for the controller.
- Who approves
- No approval on this step
- On the record
- match-invoice · allowed
In short
- Does the agent touch the control systems?No. It works in documents, maintenance, purchasing, email and accounting. Operational technology stays outside its permission.
- Who approves a spend on spares?The person who approves it today, above the threshold you set. Below it, the agent drafts and routes the order.
- What leaves for a contractor?Only the job pack for that job. Customer data is taken out before it leaves, and the record shows what was removed.
- Can an auditor or a regulator check the record?Yes. Every decision, approval and refusal is on a record an outside party can check with the open verifier, without us.
Energy and utility workflows, and the state of each.
A built item links to its run in the sandbox. A designed item has its steps written. An on-request item is scoped in the assessment.
- 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
Spare parts 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 spares.
Run it in the sandbox - Built
Reports that leave with customer data
The sandbox run sends a contract summary out with client identifiers taken out. The record names each one removed.
See the redaction - Designed
Inspection findings to work orders
The workflow above, from the report to the closed work order.
See the steps - Designed
Contractor invoice matching
Each invoice line checked against the field ticket and the agreed rate. Differences go to the controller.
See the steps - Designed
Permit and outage paperwork
The permit request assembled from the work order and the asset record, for the supervisor to sign.
- On request
Notices for planned work
Letters to affected customers drafted from the outage plan, and released by a person.
- On request
Evidence for a filing
The documents behind a regulatory filing, collected from each system with their source.
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 operate control systems, and we do not connect it to them. It works in your business systems only.
- It does not decide which spends or closures need a person. Your supervisors set the thresholds.
- It does not replace your maintenance system or your ERP. It carries the work between them.
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.
Pick one process the office repeats after each field job. We will say whether an agent should take 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.