A CMMS mobile app built to run a work order from the floor, not just view one.
SMMS (Smart Maintenance Management System) gives technicians a mobile app for creating, updating, and closing work orders; scanning a QR code or using GPS to find an asset; logging downtime with photo evidence; and asking Elisa for parts availability, LOTO steps, or a repair sequence — while connected.
What does a technician actually need from a mobile CMMS app?
A technician standing next to a piece of equipment needs to find the right asset record fast, see or create the work order for it, close it out with the failure data that actually matters later, and get an answer to a field question without walking back to a shared terminal. That's the app SMMS ships: work-order execution, asset lookup by scan or proximity, downtime logging, and an AI assistant scoped to real, checkable answers rather than a generic chatbot.
Four capabilities, all in the field app
Create, update, and close work orders from the mobile app
A stepped work-order wizard (problem, type, details) and a full work-order detail/edit screen run in the mobile app — a technician can open, update, and close out a job without going back to a desk, with photo attachment through the device camera or photo library.
QR/barcode scanning and GPS-based nearby-asset search
The mobile QR scanner resolves a scanned code directly to an asset or spare part record. A separate "Nearby Assets" screen uses the device GPS to list assets within a chosen radius, closest-first, so a technician standing in front of unfamiliar equipment can find its record without knowing the asset tag by heart.
How assets are classified (ISO 14224)Coded failure data and downtime logging in the field
Work-order closeout on a governed asset type requires the same ISO-coded failure mode, mechanism, and cause the database enforces everywhere else in SMMS — not a separate, looser mobile-only path. Downtime events can be logged directly from the mobile app, with photo evidence attached.
How failure coding worksAsk Elisa for parts availability, LOTO steps, or a repair sequence
The mobile Elisa chat screen supports asking for parts availability, the lockout/tagout sequence for an asset, or a generated repair walk-through — each backed by a real, database-checked lookup that refuses to fabricate an answer when nothing is on file, rather than a generic chatbot guess.
What Elisa does and does not doA repair, start to closeout
A technician at Meridian Fabrication Works (a synthetic demo tenant) gets a corrective work order assigned for a conveyor. They scan the asset's QR code to pull up its record instead of searching by name, then ask Elisa for the LOTO sequence before starting — Elisa returns the posted procedure for that asset type. Partway through, they ask Elisa to check whether a replacement bearing is in stock; it is, at a nearby storeroom. On closeout, the work order requires a coded failure mode, mechanism, and cause — the technician selects "Bearing Failure" from the seeded vocabulary, attaches a photo of the worn part, and closes the job. Nothing about that closeout required a separate desktop session.
Limitations
SMMS is pre-revenue with no deployed customer sites — every capability claim on this page is about what the mobile app does today while connected, not about adoption numbers or field-hardware compatibility claims that aren't independently verified.
- This page describes online mobile-app functionality only; it makes no claim about behavior without network connectivity.
- Elisa's field lookups (parts, LOTO, repair sequence) are read-only, real, database-checked answers — they fail closed to "not on file" rather than fabricating a response when the underlying data doesn't exist.
Frequently asked questions
Can I do my whole job from the mobile app, or do I still need a desktop?
Work-order creation, updates, and closeout; asset lookup by QR/barcode scan or GPS proximity; downtime logging with photo evidence; and asking Elisa for parts availability, LOTO procedures, or a repair sequence are all available in the mobile app while online. This page describes shipped, online mobile functionality only.
Does the mobile app work without a network connection?
This page describes shipped functionality with an active connection only and makes no claim either way about behavior without one. If that scenario is a requirement for your site, confirm the current state directly with your implementation contact before assuming an answer.
Can I scan a QR code to find an asset instead of searching for it?
Yes — the mobile QR scanner resolves a scanned code directly to an asset or spare-part record. There is also a GPS-based "Nearby Assets" screen that lists assets within a chosen radius when you don’t have a code to scan.
Does the app tell me the LOTO steps for an asset, or do I have to look them up separately?
You can ask Elisa in the mobile app for the lockout/tagout sequence for a named asset. If no procedure is on file for that asset, Elisa is designed to say so plainly and direct you to the posted instructions or your site safety officer — not to invent a substitute sequence.
Do I have to fill out a failure code, or can I just write a note?
On a governed work-order type, closeout requires selecting a real coded failure mode, mechanism, and cause from the seeded vocabulary — the same enforcement as the desktop app, not a looser mobile shortcut. This is by design: it is what keeps failure history usable for MTBF/RCFA analysis later.
See the field app on your own asset list.
Request a demo and we'll walk through work-order execution, asset lookup, and field AI assistance on a tenant shaped like your fleet — or take the free RMI QuickScan first to see where your program stands today.