In the field
A phone that does not need the network to do its job.
Most inspection apps degrade politely when the signal goes. This one was built the other way round: the round runs against data already on the device, and the network is only ever needed at the ends.
The lifecycle
Cache, walk out of coverage, work, come back.
This is the whole argument. Everything between step two and step four happens with no network at all, and nothing about the experience changes when it disappears.
Why it matters here
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, under a conveyor, or in a bunded tank farm with steel above you on three sides. Sites that have spent money on coverage still have dead spots, and the dead spots are usually where the equipment is.
An app that needs a round trip per question does not fail loudly in those places. It fails as a tradesperson standing still, waiting, and then writing on their hand instead — which puts you back where you started.
AMS caches master data to the device on sign-in, and the cache is time-gated so it refreshes on its own schedule rather than on every launch. If a crew needs the latest structure before walking out, a force refresh is one tap.
A schematic of an inspection screen. AMS has no public product screenshots, so this is drawn rather than captured.
What the app actually does
A short list, and all of it is real.
Planned rounds
The rounds assigned to the position you hold, on a calendar. Open one, see the summary, start work.
Guided execution
Question by question, with the answer evaluated on the device so a finding can raise its defect without waiting for a server.
Raise a defect anywhere
Create a notification from where you are standing, attach a photo, and let it queue. It does not need to be part of a round.
Find the asset
Search and an equipment picker over the cached register, so the right tag is selected rather than typed from memory.
Photos, annotation, signature
Capture a photo against a specific answer, mark it up in the app, and sign off the completed round on the glass.
Entra ID sign-in
Microsoft identity, with the session cached so a crew that signed in at the gate stays signed in out on the plant.
Two things we are careful about
Where the honest line is.
Tag read and write is in the platform, and there is an NFC-based equipment tracking application running in production — but it was built as a site-specific application, not as a screen in the base mobile app.
If tagging matters to you we will show you the one that exists, and we will be clear that it was built for one site and what it would take to do yours.
The platform can read device location, and some marketing would round that up to “GPS-tagged evidence”. It is not: AMS does not currently store a coordinate against a photo, an answer or a notification.
Traceability comes from the asset, the round and the timestamp instead. If you need coordinates on evidence, say so and we will scope it rather than claim it.
Built where sites have asked for it
Your work orders on the same phone.
At the smelting deployment, the mobile app goes further: a technician sees the SAP work orders assigned to them, opens the operation, and posts a time confirmation back to SAP from the phone. The long text on the order is read and written in place.
That is delivered integration for one customer rather than a switch in the base product, and we describe it that way on purpose — but it is running, and it is the clearest example of what the overlay is for.
When something does go wrong
The app keeps a crash log on the device that a user can open and read. On a shared plant phone with no debugger attached and no cable in sight, that is the difference between a bug report and a shrug.
Put it in a glove, in the rain
The useful demo is not on a desk. Ask us to show the round running with the phone in flight mode, and then watch the queue drain when it comes back.