Mobile CMMS: Why Field Teams Need It, and What to Test
Here is how most maintenance records get written. A technician finishes a job in a plant room at 10:40, moves straight to the next one, and three more after that. At 16:30 they sit down at the workshop PC and type up the day from memory. The pump job becomes "replaced seal", the reading they took on the gauge is gone, and the photo of the corroded flange is still on their own phone, if it was ever taken.
That end-of-shift write-up is where most maintenance data quality is lost. A mobile CMMS exists to move the record back to the moment and the place the work happens. Everything else about choosing one follows from that.
This post covers what a mobile CMMS is for, what it has to do to be worth deploying, and how to test one before you commit. If you are earlier in the process, start with how to choose a CMMS.
What a mobile CMMS changes
Strip away the feature lists and a mobile CMMS does three things a desktop system cannot.
It captures the record at the asset. The technician is standing next to the machine with the job open. The reading goes in as they take it, the photo is attached to the work order and not left in a camera roll, and the time is logged by a timer instead of estimated at the end of the day.
It identifies the asset without guesswork. Scanning a QR label on the machine opens the right record. On a site with 14 near-identical pumps, that removes the most common data error in maintenance: work logged against the wrong asset. Our QR asset tagging guide covers label placement and what to encode.
It brings in the people who never touch the desktop. Drivers doing a pre-start check, operators reporting a fault, cleaners noticing a leak. On paper these reports arrive late or not at all. On a phone they arrive with a photo, a timestamp and the asset already attached.
None of this is about convenience for the technician. It is about whether your maintenance history can be trusted when you need it: in an audit, in a warranty claim, or when you are deciding whether to replace a machine.
What belongs on the phone, and what does not
A common mistake is to judge a mobile app by how much of the desktop system it squeezes onto a small screen. That gets it backwards. The phone should do the jobs that happen next to the asset, and do them quickly with one hand.
| Job | Phone | Desktop |
|---|---|---|
| See today's assigned work | Yes | Yes |
| Scan a label to open an asset | Yes | No |
| Record readings, notes, photos and time | Yes | Rarely |
| Run an inspection or pre-start checklist | Yes | No |
| Raise a defect or new work order on the spot | Yes | Yes |
| Build PM schedules | No | Yes |
| Bulk import assets | No | Yes |
| Dashboards and reporting | Glance at most | Yes |
| Users, permissions, integrations | No | Yes |
If a vendor's app tries to do everything in the Desktop column, the jobs marked for the phone usually get worse. Extra tabs and menus mean more taps between the technician and the job.
Offline is the requirement that separates apps
Every CMMS vendor says its app works offline. They do not all mean the same thing, and the difference only shows up in the places where you most need it: basements, plant rooms, rural sites, the back of a steel-framed warehouse.
There are roughly three levels.
- Read-only cache. The app shows whatever you last looked at while you had signal. You can read a work order but cannot change it.
- Partial offline. Open work orders can be edited offline, but asset records, checklists or new work orders need a connection.
- Offline-first. The app runs from a database on the phone. Your assigned work, the assets behind it and the checklists you need are already on the device. Anything you record is saved locally first and sent when the phone is back in range.
Only the third level survives a full shift in a dead zone. Ask the vendor which one they mean, then check it yourself in the trial (see the test plan below).
Two follow-up questions matter just as much.
- What happens when the same record changes in two places? A technician edits a work order offline while the office reassigns it. A good app shows that as a conflict and lets someone choose what to keep. A poor one silently overwrites one version.
- Can the technician see what has not been sent yet? If changes queue silently, nobody knows a record is missing until it is needed. Look for a screen that lists pending changes.
Who pays for the people in the field
Licensing decides how many people use a mobile CMMS, and that decides how good your data is.
Most CMMS products charge per user. That is reasonable for technicians and planners who live in the system. It is a problem for the larger group who only need to report: drivers, operators, cleaners, site staff. Pay full price for each of them and the budget conversation usually ends with "only the technicians get logins". The rest go back to shouting across the workshop, and the defects they would have reported never reach the system.
When you compare vendors, price the whole field team, not just the technicians. A system that looks cheap at five technician seats can look very different once 40 drivers need to log a daily check. We go into the wider version of this in the hidden cost of free CMMS.
A trial test plan for any mobile CMMS
Demos happen on office Wi-Fi with a salesperson driving. A trial should happen where your technicians work, with your technicians holding the phone. Run these tests in the first week.
| Test | How to run it | What a failure looks like |
|---|---|---|
| Dead-zone shift | Put a phone in flight mode, work three real jobs, then reconnect | Jobs missing, photos lost, or the app refusing to open records |
| Cold start in the field | Install fresh, log in once on Wi-Fi, then go somewhere with no signal | Assets or checklists empty until the phone is online again |
| Wrong-asset check | Label two identical machines, scan each, log a reading | Reading lands on the wrong record, or scanning needs a typed search |
| Gloves and daylight | Close a work order outdoors in work gloves | Targets too small to hit, text unreadable in sun |
| Conflict | Edit a work order offline while someone changes it on the desktop | One version silently disappears |
| Reporter path | Have a driver or operator raise a defect with a photo | Needs a paid login, or the report arrives without the asset attached |
| Time to first job | Time a new technician from install to first closed work order | More than one short session of help needed |
Score each test pass or fail. A product that fails the dead-zone shift or the conflict test will fail you in the same way in production, just less visibly.
If you are working out how the mobile app fits into the rest of your maintenance process, moving from chaos to control covers the workflow side.
How to roll it out without losing people
The fastest way to kill a mobile CMMS is to switch everyone on at once with a two-hour training session. Technicians judge the app on their first three jobs. Make those three jobs easy.
- Label the assets first. An app that opens the right record from a scan sells itself. An app that makes people search a list of 600 assets does not.
- Start with one crew and one workflow. Work orders for one team, or daily pre-starts for one depot. Fix what annoys them before widening it.
- Keep the paper fallback for a fortnight. People trust a new system faster when they know there is a safety net.
- Read the data after week one. Look at how many work orders were closed with notes, photos and time. That tells you whether the app is being used properly or just ticked.
Where AssetOS fits
We built the AssetOS app around the jobs above. It shows assigned work orders, opens assets from a QR scan, and, where your workspace has them switched on, runs vehicle pre-start checks and fire extinguisher site visits. It saves everything on the phone first and syncs when you are back in range. It is included on every plan, and people who only report or run checks do not take a paid seat.
You can see the real screens on the mobile app page, or download it from the App Store or Google Play and run the test plan above against it.
Shane Price
Writing about maintenance management, CMMS implementation, and the real challenges operations teams face.