Guide · Choosing software
CMMS vs field service management vs OEM customer portal: how to decide
Short answer: a CMMS runs a plant’s own maintenance — work orders, preventive maintenance, spare-parts stock. Field service management (FSM) software plans and dispatches a service organisation’s technicians. An OEM customer portal serves the machines a manufacturer has shipped: the operator scans the plate on the machine, finds the released documents and troubleshooting, and sends a structured fault report to the manufacturer.
Updated October 20, 2026
At a glance: CMMS, field service management and an OEM customer portal
Machine builders who want to serve their installed base better are usually offered all three. They overlap in marketing and differ in who they are built for. Four questions below settle most decisions.
| CMMS | Field service management (FSM) | OEM customer portal (e.g. Servotag Pro) | |
|---|---|---|---|
| Built for | The plant’s maintenance team | The service organisation’s dispatchers and technicians | The manufacturer and the operators of its machines |
| Whose machines | The plant’s own equipment, any brand | The machines the service organisation is sent to | The manufacturer’s machines in its customers’ plants |
| Record level | Per asset, created by the plant | Per job or visit | Per serial number, created by the manufacturer |
| Fault report to the manufacturer | Usually internal to the plant | A job once it has been created | Built in, structured, with photo or video |
| Work orders, PM scheduling, stock | Core function | Scheduling and dispatch of technicians | Not included |
| Login to scan | Usually required | For the service organisation’s own staff | Not required for operators |
| Typical fit | Plants maintaining their own assets | Service organisations with technicians in the field | OEMs serving an installed base |
The three are not mutually exclusive: a fault report from a customer portal can land in the same inbox or ticket system your field service team already works from.
Four questions that separate the categories
| Question | Manufacturer’s customer portal | Maintenance software (CMMS) | Field service software (FSM) |
|---|---|---|---|
| Whose machine data is it? | The manufacturer’s, for every machine it has shipped | The plant’s, for the equipment it operates | The service company’s, for the jobs it carries out |
| Who writes the content? | The manufacturer: manuals, troubleshooting, spare parts per machine type | The plant’s maintenance team: work instructions and plans | Dispatchers and technicians: job notes and reports |
| Who uses it at the machine? | Any operator with a phone, without an account | Maintenance staff with an account | The service company’s own technicians |
| What happens to a fault? | A structured report goes to the manufacturer’s existing workflow | A work order in the plant’s own system | A job is scheduled and dispatched |
These are the typical roles, not rules: many products stretch into a neighbouring category. The questions still tell you which problem you are buying for.
When a customer portal is the right first step
- You ship many machines of a few types, and the same questions reach your hotline again and again.
- The operators at your customers’ sites have no account in any of your systems — and should not need one.
- You want better fault reports before you change how your technicians are dispatched.
- You do not want to run a software project in every customer’s plant.
When you need CMMS or field service software instead — or as well
If you plan preventive maintenance for equipment in your own plant, that is a maintenance system’s job. If you schedule technicians, manage van stock and invoice service visits, that is field service software. A customer portal does not replace either; it can feed them — a fault report can arrive in the same inbox or ticket system your field service team already works from.
Where Servotag Pro sits
- The manufacturer’s after-sales layer: the QR plate ships with the machine, and the plant needs no project of its own.
- Content per machine type, inherited by every machine of that type, in several languages.
- Release levels: operator topics for everyone, technician procedures behind a revocable service code.
- Fault reports into email or a signed webhook, with the machine identity attached.
- Three request statuses — New, Sent, Closed — and a one-click entry into the machine’s service history. No dispatch, scheduling or work orders.
- Maintenance plans on the machine type; due dates are recalculated whenever a plan or a service entry changes.
- Everything exportable as spreadsheets, and never machine control.
How an equipment service history by QR code builds up over the life of a machine is shown step by step in its own guide.
Questions to ask any vendor
- Does the operator need an app or an account to use it?
- Can content be released per level, so an operator never sees a technician-only procedure?
- Does a fault report carry the machine’s identity without anybody typing a serial number?
- Where does the report go — into the inbox or ticket system you already use?
- Can you export all of it, at any time?
- Does it connect to machine control — and do you want it to?