Maintenance management software (CMMS)
Maintenance management software that starts from your equipment logbooks
A CMMS, or computerized maintenance management system, keeps every machine, repair, spare part, purchase request and planned job in one place your team can search. This one is built for plants whose maintenance records are in logbooks and spreadsheets today, including sites that changed owners and no longer have the group system.
- maintenance roles
- 10maintenance roles
- apps in one launchpad
- 20apps in one launchpad
- in and out
- Excelin and out
- optional, beside it
- SAPoptional, beside it
- Starts from logbooks and spreadsheets
- Works without an ERP
- Replaces the daily Excel files
- Your records, downloadable any time
Does this sound like your plant?
The site changed owners
The old group switched off access to its ERP. The equipment list, the work order history, the spare parts stock and the purchase requests were in it.
Maintenance runs on paper
Each machine has a logbook. An entry says "bearing replaced, machine running" and nothing about which bearing, why it failed or whether the fix was temporary.
The plan lives in a spreadsheet
One person keeps the planned maintenance sheet. Nobody else knows what is overdue until that person says so.
The knowledge is in two heads
The same fault comes back every few months and is diagnosed from the start, unless the technician who fixed it last time is on shift.
Modules
Each one opens that app in the demo. Figures are the demo plant on a fresh start. It is laid out the way enterprise systems are, so it will not feel new: a home screen with the key figures for today and your own apps first, every app opening with its purpose and its key figure, and lists you can sort, filter and open.
Notifications and work orders
Planning and performance
Stores and purchasing
Quality and compliance
Management
Your data
Everything it keeps (26)
- A list of every machine
- Name, area, class (GMP-critical, utility, non-product-contact), qualification status and your own asset tag.
- An equipment maintenance log for every machine
- Each repair as a record: symptom, what changed before it, cause, fix, parts used, downtime, who did it and who reviewed it.
- Where each fact came from
- Every record names its source: the logbook page, the old work order, the manual section or the technician who said it.
- Breakdown requests from operators
- Breakdown maintenance starts with the report: an operator reports a fault from the line and says whether the machine has stopped. Maintenance acknowledges it, and the time it waited is on file.
- Temporary repairs that stay visible
- A repair made with a part that is not the specified one stays at the top of the machine until it is closed.
- Spare parts stock
- The spare parts inventory: what is on the shelf, where it is, the minimum to keep and which machine it fits. A part used on a repair comes off the shelf.
- Purchase requests
- A request for a part that is low or out, who raised it, who approved it (the site head above a set limit), when it was ordered and when it arrived.
- Preventive maintenance and calibration
- Every planned job and calibration with its due date, what is overdue, and how much was done on time.
- Goods received notes and stock counts
- A delivery is recorded against its request with the supplier's delivery note. A stock count shows where the shelf and the figures differ, and keeps the difference on file.
- Contractor jobs
- Each outside job with the firm, the quote, who approved it, the permit it runs under and who signed the work off. An approved quote counts as committed in the budget.
- Permits to work
- Who asked for a lockout, hot work, work at height or confined space permit, who issued it, and whether it was closed at the end of the shift.
- The maintenance budget
- Each budget line with what is spent, what is committed on open purchase requests and what is left, against how much of the year has gone.
- A monthly report
- The month's repairs, downtime, overdue jobs, low stock and budget on a few pages, written from the records and ready to print.
- Repeat faults and downtime
- Which faults came back, on which machine, and how much production time they cost.
- Downtime and OEE by machine
- Downtime tracking without a second system: breakdown time comes from the repair records. Add the planned hours and the units made and passed for each shift, and it works out availability, performance, quality and OEE for each machine.
- Links to quality records
- The deviation, CAPA or change control number that belongs to a repair is kept with it.
- A calibration register
- Every instrument with its range, tolerance, due date and last certificate, and which ones decide product quality, so an overdue one is flagged to QA.
- Utilities maintenance templates
- Starting task lists for HVAC and air handling, purified water, compressed air, boilers and chillers, adapted to your equipment and SOPs.
- Inspection readiness
- The questions a DRAP or PIC/S inspector asks of maintenance, answered from the records: calibration, overdue GMP-critical jobs, temporary repairs, unreviewed records and open permits.
- A workspace for each role
- Each person signs in to their own apps first: the planner to the plan, the stores officer to the shelf, the site head to the decisions waiting for them.
- A weekly review for the three heads
- One agenda for the head of maintenance, the head of engineering and the site head, built from the same records, with each item naming who decides it.
- Handover
- Everything a position holds, from planned jobs and instruments to open permits, requests and approval limits, listed and moved to a successor in one step.
- Facility blocks
- A site with several blocks, such as an oral solid dosage block and a utilities block, filters every list to one block.
- Spreadsheets in and out
- Any list downloads to Excel, and rows pasted from an existing sheet show how they become records.
- A pilot scorecard
- The measures a pilot is judged on, with the figure before go-live, the figure now from the records, and a target the plant sets.
- A trail of who did what
- Each added record, review and download is listed with the time and the person.
Who it is for, and what it says about them
Operator
- Who it is for
- The person running the machine on the line.
- Why it matters to them
- A fault is reported in seconds from the line, and they can see that maintenance has picked it up instead of chasing someone on the phone.
- What it says about them
- That they raised the alarm, and when. If the machine stood waiting, the record shows the wait was not theirs.
Their apps in the demo
For the site head, head of engineering and quality, the Leadership Summary app puts inspection readiness, overdue calibration, planned jobs on time, OEE, budget and breakdown time on one screen, with the decisions waiting on them and the pilot scorecard beside it.
The work each role does by hand today, and what the system takes over
Head of engineering
By hand today
Pieces together repeat faults and temporary repairs from logbooks and memory before deciding what to fix for good.
Done by the system
Repeat faults, open temporary repairs with their change controls, qualification status and OEE losses are listed from the records.
Still a person's job
Deciding the permanent fix and approving the change.
Utilities engineer
By hand today
Keeps HVAC, water, compressed air, boiler and chiller checks in separate sheets and log books.
Done by the system
Utilities have their own plans, readings, breakdowns and permits, on the same records as the production lines.
Still a person's job
Running the utilities and signing off the work.
Maintenance planner
By hand today
Keeps the planned maintenance sheet, chases overdue jobs and works out the weekly on-time figure.
Done by the system
Every planned job has a due date. Overdue jobs and the on-time percentage are worked out without anyone counting.
Still a person's job
Deciding what gets done first when two jobs clash.
Maintenance engineer and technician
By hand today
Writes each repair in the logbook and looks through old pages to find what was done last time.
Done by the system
One search finds every past repair by symptom, part or alarm code. A repeat fault and an open temporary repair are flagged on the machine.
Still a person's job
Diagnosing the fault and doing the repair.
Calibration and instrumentation
By hand today
Tracks calibration due dates in a separate sheet.
Done by the system
Calibrations sit in the same list as planned maintenance, with the overdue ones on GMP-critical equipment counted first.
Still a person's job
Doing the calibration and signing the certificate.
Spare parts stores
By hand today
Keeps bin cards, checks reorder levels and writes purchase requisitions.
Done by the system
A part used on a job comes off the shelf. A part below its minimum is listed with the quantity to request. A delivery gets a goods received note, and a count shows the differences.
Still a person's job
Checking the delivery, counting the shelf and dealing with suppliers.
Head of maintenance
By hand today
Collects figures from four people before an inspection or a monthly review.
Done by the system
Downtime, repeat faults, overdue jobs, low stock and open requests are on one screen, the monthly report writes itself, and each machine history downloads as a file.
Still a person's job
Setting the budget, deciding priorities and answering the inspector.
Where the daily work really happens
Plants often own several large systems, and the day-to-day maintenance work still runs in Excel: the planned maintenance sheet, calibration due dates, the spare parts list, repair notes and the handover file. Those files sit on one person's computer, in versions only they can follow.
It sits beside the systems you already have and takes over the spreadsheets, not them. Where a plant runs SAP, the Connected Systems app shows what would be read from it and written to it.
- The planned maintenance sheet
- Becomes maintenance plans with due dates, owners and an on-time figure nobody has to count.
- The calibration tracker
- Becomes a calibration register with certificates, and a flag when an instrument that affects product quality falls due.
- The breakdown log
- Becomes notifications from the line, with how long each waited and what was done.
- Repair notes and logbooks
- Become searchable records, with the original page kept beside each one.
- The handover folder
- Becomes a handover list of everything a position holds, moved to the successor in one step.
From paper logbooks to a CMMS, one line at a time
1. Pick one line
Five to ten machines, usually the ones that stop production most often.
2. Send what you have
Logbook pages, spreadsheets, manuals, alarm lists, and any export you kept from the old ERP. Photos of pages are fine.
3. We build the records
We turn them into machine files and repair records. Your engineer checks each one before it counts.
4. Your team uses it
Technicians search it at the machine and add each new repair. The head of maintenance reviews what is added.
What it is not
- It is new. The working demo is what exists today, and a pilot on one line is how it becomes yours.
- It is not yet a validated computerized system. Until it has been validated for your site, your signed logbooks remain the GMP record and this is the searchable copy beside them.
- It does not replace finance. It follows a spare part from request to shelf to machine; supplier invoices, payments and accounts stay where your finance team keeps them.
- It gives no safety or quality instruction on its own. Lockout, line clearance and release decisions stay with your procedures and your people.
Questions
Do we have to stop using Excel?
No. Every list downloads to Excel, and rows pasted from the sheets you keep today show how they would become records. Most plants keep a few sheets alongside it.
Does it need SAP or another system to run?
No. It runs on its own. Where a plant already runs SAP, it can sit beside it and exchange equipment, stock and requests; the Connected Systems app in the demo shows what would be read from it and written to it, with a log of every exchange.
We lost access to our ERP when the site was sold. Can we start from nothing?
Yes. A pilot starts from what is still on site: logbooks, spreadsheets, manuals, alarm lists and what your technicians know. If you kept an export of the old equipment list or work orders, we load that too.
Is this a CMMS?
Yes, in what it covers: the machine list, the equipment maintenance log, breakdown requests, preventive maintenance dates, spare parts stock, purchase requests, downtime and OEE. It is new, and it does not handle supplier invoices or payments.
Can it take in our old equipment maintenance logs?
Yes. Paper logbook pages are read into records, with the original words kept and the page shown beside the record. Anything the page does not say is marked as not written, never filled in, and your engineer checks each record before it counts.
Can it be our GMP maintenance record?
Not until it has been validated for your site. Until then your signed logbooks remain the GMP record, and this is the searchable copy that tells a technician what was done last time.
Who types the records in?
We build the first set from your documents and your engineer checks them. After that, the technician who does a repair adds it, and the head of maintenance reviews it.
Can we get our data out?
Yes. Each machine history downloads as a spreadsheet file, and the records are yours.
Tell us what you want to build.
A few lines are enough. We reply in writing with questions.