Your ERP holds the work order. AMS holds what actually happened in the plant.
AMS is the inspection, defect and risk layer that runs on top of the maintenance system you already own — and hands the results back to it.
In production in multi-metals smelting in Australia, at a Queensland process plant, and in a commercial explosives business.
The gap
The work order exists. The condition of the asset does not.
Your maintenance system of record is good at planning and costing work. It was never built to hold what a tradesperson saw on a walkway at six in the morning. So that part of the job falls back to paper, spreadsheets and memory.
Inspection rounds live in spreadsheets
A round is authored once, printed, and then drifts. Nobody can tell you which version a crew actually ran last quarter, or what changed between them.
Defects found on paper never reach triage
A finding written on a clipboard has to be retyped by somebody, into something, before it becomes work. Most of the time it is not.
Risk is a matrix reviewed once a year
The scoring lives in a workbook owned by one engineer. It is not connected to anything measured, and it is out of date the week after the review.
How AMS is different
Three things, and we do not claim a fourth.
It sits on top, not in the way
AMS has no database of its own. Every read and write goes out over HTTP, and AMS publishes its own documented REST surface back. It is an overlay on the system of record, which means no migration and no rip-and-replace evaluation.
It works where there is no signal
The native mobile app caches master data to the phone, runs a complete inspection round offline, writes every answer to a local database, and uploads the queue when the network comes back.
Your engineers configure it
Inspection rounds, question catalogues, site variants and risk formulas are authored in the product, not in our source code. A reliability engineer changes a round or a formula the same afternoon.
The part that closes the loop
A finding becomes triaged work without anyone retyping it.
This is the mechanism most inspection tools do not have. In AMS, a question can carry an action. When the answer meets the condition the action is configured for, AMS raises a defect notification automatically — and it arrives already populated.
- The object part and damage code, taken from that equipment’s own catalogue
- The priority the engineer set when the question was authored
- The standing comments that belong with that kind of finding
- The answer, the photo and the round it came from
The inspector taps one answer. A planner sees a properly coded notification. No clipboard, no re-keying, no translation loss in between.
Risk management
Risk scoring is arithmetic your own engineers own.
This is the deepest module in AMS. Risk variables are defined per site and evaluated with real formulas, not picked from a fixed template. Measurements are logged over time against equipment and locations, edited in bulk when a campaign lands, and rolled up into an assessment view.
Because the formula is configuration rather than code, changing how your site scores consequence or likelihood does not require us.
What is in it
Enough to run the work, not so much that nobody configures it.
Risk management
Configurable risk variables with formula evaluation, assessments, and a measurement log with bulk editing and an overview.
MoreInspection authoring
Build questionnaires, a shared question catalogue, per-site variants and the actions that turn an answer into a defect. No code.
MoreWork orders and defects
Notifications, the work order register and detail, search, bulk import, and operations placed on a shared time axis.
MoreEquipment and org register
Equipment and types, the company, area and location hierarchy, employees and org positions.
MoreDashboards and search
Embedded Power BI reports, and one search box across notifications, equipment, locations and work orders.
MoreRoles and access
Users, system roles, system functions and the mapping between them, with Entra ID sign-in where you use it.
MoreWhere it runs
Heavy industry, in the conditions heavy industry actually has.
We describe customer work the way we publish all of it: sector, asset estate and function. No names and no logos on a public page.
Multi-metals smelting
A smelting group operating in Australia. The deepest deployment: inspections and risk alongside a production SAP Plant Maintenance estate, Entra ID sign-in, and a dedicated mobile app for field crews.
Chemical and fertiliser processing
A continuous process plant in Queensland. Acid plant, utilities, water treatment, dosing and bunded areas — an estate where inspection evidence and risk scoring carry regulatory weight.
Mining and quarrying services
A commercial explosives business. Equipment that moves between customer sites, operated by crews who are rarely at a desk and often out of coverage.
On a public page, the sites speak for themselves. If you need a reference conversation during an evaluation, ask and we will tell you what we can arrange.
See it against your own plant
Tell us how your site is structured and we will walk through the parts that fit. The people who build AMS are the people who run the demo.