How to Implement a Free CMMS Without a Rollout Project
A practical, step-by-step way to stand up a free CMMS and OEE habit this week: add your assets, set PM schedules, log each shift, read the Pareto, and raise work orders. No project plan, no budget approval, and no account needed to start.
The short answer
- You do not need a rollout project. A free CMMS can go live in an afternoon: build a small asset register, add a few PM schedules, and start logging each shift.
- Work the loop daily. Log the shift (about two minutes), let the tool calculate OEE with availability, performance, and quality, then read the downtime Pareto to find your biggest loss.
- Turn the top loss into action by raising a work order on the board, and keep the habit small: one line, one device, real numbers your team actually trusts.
- When manual entry, self-run cause-hunting, and one-device scope start costing more than they save, that is the signal to graduate to Fabrico for automatic PLC capture and a closed loss-to-fix loop.
Most CMMS failures are not tool failures, they are rollout failures: a six-month project, a data-migration marathon, and a launch nobody adopts. You can skip all of it. This guide shows how to implement a free CMMS as a daily habit instead of a project, using OEE Lab's free tracker to log shifts and run maintenance from your browser, with the same steps that apply to any free CMMS.
The whole setup is four short steps you can finish in an afternoon: build a small asset register, add a handful of preventive-maintenance schedules, log your first shift, and read your first OEE number. No account, no server, and no budget line. Everything stays in your browser on one device.
Once the habit sticks, the tool earns its keep by turning your biggest downtime loss into a work order every day. Keep it deliberately small (one line, one device, one team), and when manual logging and single-plant scope start to pinch, the honest next step is laid out in when to upgrade from a free CMMS.
What you get, free
Step 1: build a lightweight asset register
Start by listing the machines and lines you actually run, not every bolt in the plant. The free asset register lets you add each asset with a name and a few details in minutes, so you have something concrete to log downtime and schedule maintenance against. Ten assets is a perfectly good day-one scope.
Step 2: set a few PM schedules
Add preventive-maintenance schedules for the tasks you already know matter: the weekly greasing, the monthly inspection, the filter change. The tracker keeps the recurring PM plan in one place so nothing quietly slips, and you can add more schedules as the habit sticks. There is no need to model every task on day one.
Step 3: log each shift and get OEE
This is the core habit. At handover, someone logs planned time, output, rejects, and stops in about two minutes. The tracker instantly returns OEE broken into availability, performance, and quality, with a comparison to the 85% world-class OEE benchmark so you know exactly where the line stands.
Step 4: read the downtime Pareto
Every logged shift feeds a downtime Pareto that ranks your loss reasons biggest-first, plus a per-machine breakdown so you can see which asset is dragging the line. This is where implementation pays off: you stop guessing and see the one loss worth fixing this week.
Close the loop with a work order
Turn the top Pareto reason into an action by raising a work order on the board and assigning it. The board tracks open and done work orders alongside your PM schedule, so the whole reactive-plus-planned picture lives in one place instead of on a whiteboard that gets wiped at shift change.
Export, back up, and print the numbers
Because everything is browser-local, the tracker gives you CSV and JSON export plus a full backup and restore, so your history is never trapped on one machine. You can also print a PDF report and a scorecard for a supervisor, and reload your saved data any time on the same device.
Log one shift and the free tracker shows your OEE, your loss Pareto and how you compare to world-class. Add work orders and preventive-maintenance reminders in the same place.
Where free stops, and Fabrico begins
The free tracker is built for getting started fast and for one plant on one device. When a site gets serious about its losses, the manual steps start to cost more than they save. This is exactly where Fabrico takes over.
| Capability | Free OEE Lab tracker | Fabrico |
|---|---|---|
| Data capture | Manual shift logging, about two minutes per shift, entered by hand | Automatic OEE read straight from your PLCs, no manual entry |
| Loss-to-fix loop | You spot the top Pareto loss and raise the work order yourself | Closed loop: a detected loss auto-routes into an assigned work order |
| Micro-stop cause | You investigate micro-stops and assign the reason from experience | Computer vision pinpoints the true cause of micro-stops |
| Scope and multi-site | One plant on one device and browser | Scales across lines and sites through live PLC, MES, and ERP integration |
| Integrations | CSV and JSON export you wire up yourself, no live connections | Live integrations with PLCs, MES, and ERP |
| Access and roles | People and roles on that one device with local sign-in | Role-based access backed by ISO 27001-aligned controls |
| Data residency | Data stays in your own browser on your device | EU-built with EU data residency |
| Reporting | Printable PDF report, printable scorecard, and benchmark comparison | Continuous dashboards plus an audit trail that supports audit-readiness against ISO 27001, 20000-1, and 9001 |
| Setup and rollout effort | No project: register a few assets, set PM schedules, and start logging today | Guided onboarding to connect PLCs and configure sites, then it runs unattended |
Frequently asked questions
How long does it take to implement a free CMMS?
An afternoon is enough. With OEE Lab's free tracker there is nothing to install and no account to create, so the real work is four steps: add a handful of assets, set a few PM schedules, log your first shift, and read your first OEE and Pareto. You can be running real work orders the same day.
What do I need ready before I start?
Very little. A list of the machines or lines you run, the recurring maintenance tasks you already know about, and a rough sense of how a shift breaks down into planned time, output, rejects, and stops. You do not need clean historical data or an IT project to begin, because the tracker builds history from the day you start logging.
How much should I set up on day one?
Keep it deliberately small. Around ten assets and a handful of PM schedules is plenty to prove the habit on one line. Trying to load every asset and every task up front is the classic way rollouts stall, so start narrow, get a week of clean shift logs, and expand only once the daily logging habit sticks.
Who should do the shift logging?
The person closest to the line, usually the operator or shift lead. Logging a shift takes about two minutes at handover: planned time, output, rejects, and the stops that happened. Because it is fast and browser-local, it fits into the end-of-shift routine without a separate system to log into.
Do I have to migrate my old spreadsheet first?
No. The fastest path is to start logging fresh and let the tracker build your OEE and downtime history going forward. Your spreadsheets stay as a reference, and since the free tracker exports CSV and JSON with full backup and restore, your new data is never locked in either. Migrating old records is optional, not a prerequisite.
When do I need more than a free CMMS?
When the manual side starts costing more than it saves. The clear signals are needing OEE captured automatically instead of typed in each shift, needing one number across more than one line or site, needing live links to your PLCs, MES, or ERP, or needing an audit trail and EU data residency. That is the point to book a Fabrico demo, where OEE is read straight from your PLCs, computer vision pinpoints the true cause of micro-stops, and a detected loss auto-routes into a work order.
When free is not enough, Fabrico is the upgrade
A free CMMS habit is the right way to start, and for a single line it can run happily for a long time. The moment it stops scaling is usually the moment manual logging, self-run cause-hunting, and one-device scope turn into real engineer-hours every week. Fabrico is the honest paid step up: it reads OEE straight off your PLCs so nothing is typed in by hand, uses computer vision to pinpoint the true cause of micro-stops, and closes the loop by auto-routing a detected loss into an assigned work order. It is EU-built with EU data residency and certified to ISO 27001, 20000-1, and 9001, with a full audit trail that supports audit-readiness. Once your afternoon setup has proven the value and you need it to run unattended across more lines and sites, book a Fabrico demo and see it on your own equipment.
Book a Fabrico demoMore free software: All free software · When to Upgrade From a Free CMMS · Do I need a CMMS? An honest self-assessment for your maintenance team · Free asset management software for manufacturing · Free CMMS vs an ERP maintenance module: how to choose
Open the free OEE tracker · Free preventive maintenance software · Free work order software · Free asset management software · When to upgrade from a free CMMS · Free manufacturing software directory