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 drift once they are printed, and nobody can say which version a crew actually ran last quarter. Defects written on a clipboard have to be retyped by somebody, into something, before they become work — and most of the time they are not. Risk lives in a workbook owned by one engineer, reviewed once a year, connected to nothing that was measured.
A finding becomes triaged work without anyone retyping it
This is the part that closes the loop. In AMS a question can carry an action, and when the answer meets the condition the action is configured for, a defect notification is raised automatically. 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, and no translation loss in between.
Risk scoring is arithmetic your own engineers own
Risk variables are defined per site and evaluated with real formulas rather than 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 and not code, changing how your site scores consequence or likelihood does not require us.
It works where there is no signal
Coverage inside heavy industry is not a solved problem. A cell tower does not help you inside a furnace building, behind a bank of transformers, or in a bunded tank farm with steel above you on three sides, and the dead spots are usually where the equipment is.
The mobile app was built the other way round from most: it caches master data to the device on sign-in, runs the whole round against what is already there, evaluates each answer on the phone so a finding can raise its defect without waiting for a server, and uploads the queue when the network comes back. Nothing about the experience changes when the signal disappears.
It sits on top, not in the way
AMS has no database of its own. Every read and write leaves the process over HTTP, no component holds a database credential, and AMS publishes its own documented REST surface back — the same one the mobile app uses. There is no schema of ours for you to migrate, version or reconcile against yours, and the blast radius of an AMS outage is AMS, not your plant database.
Entra ID sign-in, Power BI Embedded reporting, the REST hub and Excel import and export ship with the product. The SAP Plant Maintenance integration, SSRS rendering and the read-only MCP server were each scoped and built for a specific site against that customer's systems; we can repeat them, and we will not imply they are a switch.
Where it runs
We describe customer work the way we publish all of it: sector, asset estate and function, with no names and no logos on a public page.
- Multi-metals smelting. A smelting group operating in Australia, and the deepest deployment by a distance: inspections and risk alongside a production SAP Plant Maintenance estate, Entra ID sign-in, a dedicated mobile app for field crews, and technicians posting time confirmations back to SAP from the phone.
- Chemical and fertiliser processing. A continuous process plant in Queensland — acid plant, utilities, water treatment, dosing and bunded areas — where inspection evidence and risk scoring carry regulatory weight. The risk module is configured most heavily here.
- Mining and quarrying services. A commercial explosives business whose equipment moves between customer sites, operated by crews who are rarely at a desk and often out of coverage.
Find out more
The full product site, with the capabilities, field, platform, integrations and deployment detail, is at dbsams.com. If you would rather talk it through, tell us how your site is structured and we will reply within one working day.