CMMS software: what it does and how to choose one.

What CMMS software does

The full name is computerized maintenance management software, or system. Plants outside the US often write it as computerised maintenance management system, and both spellings appear on vendor sites. The category is the same either way. You will also hear it called a CMMS system, a CMMS program, or CMMS solutions, and those terms are interchangeable in practice. Different CMMS systems vary far more in how they are priced and how fast a technician can use them than in their headline feature lists.

The useful way to think about a CMMS is as a loop. Something breaks or comes due, the job is routed to a person, the person does it and records it, and the record changes what happens next time. Without the record, the loop restarts from memory on every shift. A simple test of whether the loop works: can you say which machine cost you the most downtime last quarter, without asking anyone to remember? The CMMS glossary entry and the longer guide, What Is a CMMS?, cover the definition in more depth.

CMMS for manufacturing versus facilities

Facilities teams maintain buildings: heating and cooling, lifts, lighting, plumbing. Work usually arrives as requests from people who occupy the space, the asset list is long, and most assets are low criticality. A facilities CMMS leans on request portals, space records and vendor contracts.

Manufacturing teams maintain production machines, where a stoppage has a direct cost in output. That shifts what matters. CMMS for manufacturing needs fast breakdown reporting from the people standing at the machine, machine-level history, spare parts tied to specific equipment, shift handovers, and preventive schedules driven by running hours as well as dates. Many products serve both settings, so check which one the product was designed around by looking at what its default screens show.

Core features to expect in CMMS software

Vendors list dozens of features. Five carry the weight, and everything else depends on them being connected to each other.

Work orders

A work order is the record of a job: which machine, who is assigned, what state it is in, what was done, how long it took and what was used. Breakdowns, preventive tasks and inspections should all become work orders so they can be tracked in one place. See the work order guide for how a job should move from request to close out.

Preventive maintenance scheduling

Scheduling rules generate work before failure, either on the calendar (every 90 days) or on a meter (every 5,000 running hours). The test is not whether schedules can be created but whether overdue work is visible and whether completion is measured. Preventive maintenance and PM compliance explain the measures, and What Is Preventive Maintenance? covers building schedules technicians will actually finish.

Asset registry

The asset registry is the list of what you maintain, ideally with a hierarchy of plant, line, machine and component. Every other record attaches to it, so an inconsistent machine list quietly damages every report. It is the dull part of implementation and the part most worth getting right first.

Parts inventory

Stock levels, reorder points and consumption tied to the work order and the machine. Linking use to equipment turns stocking decisions from guesses into a reorder calculation. Look for an approval step between a technician's request and the store keeper's issue, because that is where unrecorded consumption usually starts. See MRO inventory for the vocabulary.

Reporting

Reports should come from the work order records, not from a separate spreadsheet. The core measures are MTTR, MTBF, PM compliance and downtime by machine, plus OEE where production data is available. If a vendor demo shows impressive dashboards but cannot show how a number is derived from a timestamp on a work order, treat the dashboard with caution.

Contractor management, shift handover, training records and safety workflows are common additions. They are worth having if you need them, but they sit on top of the five above.

How CMMS pricing works

CMMS pricing depends on what the vendor chooses to count. The four common models each suit a different plant, and none is better in every case.

Per-user pricing is usually the cheaper route for a small, fixed team looking after a handful of machines. Per-machine pricing tends to win when many operators and supervisors need to report faults and the asset count is moderate, because adding a reporter does not change the bill. Whatever the model, ask about the costs outside the headline rate: annual-only billing, storage charges, paid onboarding and features gated by tier. The post on per-machine versus per-user pricing works through the arithmetic with assumptions you can re-run for your own plant.

Where Firmicore's pricing fits

Firmicore sizes plans by the machines you register. Each tier has a flat monthly price and states its machine limit with inventory, preventive maintenance and user limits alongside it, so the price is not a per-head charge. The current tiers, by machine limit, are Basic (10 machines), Workshop (100 machines), Factory Pro (1,500 machines), Enterprise (unlimited machines). Plans start from $29/mo on Basic, and annual billing is discounted. Some modules, including shift handover and the PM compliance dashboard, start at the Workshop tier. Figures are indicative, so check the pricing page and confirm with sales before you budget. If you have few machines and a very small team, per-user pricing from another vendor may cost less, and it is worth running both numbers.

How to choose CMMS software: a checklist

Feature tables mislead because most products tick the same boxes. These questions separate systems that get used from systems that get abandoned.

1. Can an operator report a breakdown from the machine in under a minute, on a shared device, without hunting for an asset number?
2. Is preventive maintenance scheduling, calendar and meter based, included in the tier you would actually buy?
3. Does a work order capture parts, time, root cause and sign-off, with timestamps created by the system rather than typed in?
4. Can you import your existing machine list from a spreadsheet instead of retyping it?
5. What does the pricing model count, and what happens to the bill if you add twenty reporters or thirty machines?
6. Do reports show MTTR, MTBF, PM compliance and downtime per machine without an export to a spreadsheet?
7. What does it need from your IT team: hosting, single sign-on, a VPN, an on-site database?
8. Who does the setup, how long does it take, and is onboarding charged separately?
9. Can you export all of your data if you leave?

Then test the shortlist where it will really be used. Try it in the worst-covered corner of the plant, with the person who has the least patience for software. Pilot on one line before committing the whole site. Our guide to CMMS for small manufacturers applies this checklist to plants without an IT team, and the MaintainX comparison sets out where a per-user product is the better fit and where a per-machine one is.

CMMS implementation steps

Most failed rollouts fail on scope, not software. A plant tries to load every machine, every checklist and every user in week one. A smaller sequence works better.

1. Clean the machine list. One name per machine, a consistent hierarchy, and a decision about whether components are tracked separately.
2. Choose a pilot line. Pick one with enough breakdowns to generate real records within weeks.
3. Load preventive schedules for critical machines only. A short schedule that gets completed beats a complete one that does not.
4. Set roles and access before go-live, so supervisors, technicians and store keepers each see their own work.
5. Put identifiers on the machines and retire the paper log on the pilot line the same day. Running both in parallel teaches people that the software is optional.
6. Review the first month of records weekly with the supervisors, and fix the data problems you find.
7. Extend line by line once the pilot line's reports are being used in daily meetings.

For the floor-level side of this, including shared tablets and operators who do not have accounts, see the rollout section of the maintenance management software guide and the post on how to report a machine breakdown.

When you need EAM instead of a CMMS

EAM, or enterprise asset management, covers the whole asset lifecycle: purchase, depreciation, capital planning, maintenance and disposal, often across many sites. Maintenance is one module inside it. A CMMS is narrower and goes deeper on the maintenance work itself.

A CMMS is the right tool when the question is how to keep machines running and prove what was done. EAM becomes the better answer when the question is lifecycle cost and capital replacement across a large asset base, or when asset financials must live in the same system as maintenance. Very large multi-site enterprises that have already standardized on an ERP such as SAP often use that suite's maintenance module, and for them that is frequently the sensible choice. The SAP Plant Maintenance comparison sets out the trade-offs, and the maintenance management software guide compares spreadsheets, ERP modules and dedicated systems side by side.

How Firmicore handles this

Firmicore is a CMMS for manufacturing and process plants. Every machine in the registry carries a QR code, and scanning it opens breakdown reporting for that specific machine, so floor staff can report without logging in to a desktop and without typing an asset number. Operators can also work through guided triage while they wait for a technician.

Work orders run from Draft to Closed with multi-technician checklists, time tracking, parts requests and a supervisor sign-off queue. Preventive maintenance runs on calendar or meter schedules with a compliance dashboard. Parts requests go through an approval workflow that includes the store keeper, and shift handover reports are compiled from open work orders and breakdowns. Email and in-app notifications keep people informed, and role-based access gives each of the nine role workspaces only what it needs.

Pricing is sized by machine count, as described above. See every module on the features page, compare tiers on the pricing page, or read how QR reporting compares with paper logs.

Frequently asked questions