Hospitals and clinics
Infusion pumps, ventilators, sterilisers, monitors. Every device carries its own procedure, its own interval and its whole service history — on one ward, or across every site at once.
CMMS for industrial maintenance
Every inspection done on the day it was due, with a name against it.
Ncore turns your maintenance procedures into a day’s work orders, puts them on the tablet the operator already has, and keeps what was signed — so when an inspector asks what was done to a machine last March, the answer takes seconds.
Every account approved by a personSet up in minutesCroatian and English
Proof, not recollection
Every step an operator ticks carries who did it, when, and on which machine.
Nobody retypes the schedule
The day’s work orders appear each morning out of procedures you wrote once.
Several facilities, one set of procedures
Write a procedure once and give each facility the variant it needs.
Runs on the tablet you already own
A browser is enough. Nothing to install, and no licence counted per head.
Regulated equipment
Where a missed check is not just downtime.
An infusion pump, a dental autoclave, a laboratory freezer and a compressor in a plant room are one problem to this system: a piece of equipment with a written procedure attached, an interval it has to be done on, and somebody who has to be able to show that it was. The protocols are yours and the rules are whichever ones apply to you — what Ncore does is run them on time and keep the signed record they ask for.
Dental practices
Autoclaves, chairs, compressors, imaging. The daily and weekly checks a surgery runs on, ticked off chairside on the tablet that is already there.
Laboratories and pharmacies
Fridge and freezer temperatures, incubators, calibrated instruments. Readings are kept against the instrument itself, and the ones outside their limits surface without being asked for.
Industry and facilities
Boilers, pumps, presses, lifts. The plant maintenance the system was built for, working exactly as it did before.
Ncore keeps the record. It does not certify anything, and it does not know what you are required to do — which checks you owe, how often, and how long the evidence has to be kept are set by your own protocols and by the rules that apply to you. You write those in, and the system runs them on schedule and keeps what was signed.
The book of procedures
Every machine gets its book, and the book knows when it is due.
A procedure is written once, as a template: the steps in the order they are done, the readings to take, the checks to tick, and the piece of equipment each one is about. From then on the system holds it the way the binder used to — except it also knows whose job it is this morning, and what was signed the last time round.
- Steps, readings, checks and photographs, in the order the work happens.
- Every step bound to the part of the plant it is about.
- One template, and the variant each site actually needs.
Where the numbers come from
Everything that measures reports into the same record.
An operator ticking a step on a tablet, a SCADA system or historian pushing readings over the API, a figure typed in by hand at a desk — they all arrive against the same machine, in the same units, on one timeline. What the plant already measures does not have to be measured a second time to get in here.
Nobody types the same number twice.
What it gives back
The state of the company at a glance, while there is still time to act.
Collected readings stop being rows in a log and become a picture: what is drifting towards its limit, what is late, what is standing still, and which machine is going to need somebody this week. That is the difference between a measure taken in advance and a phone call at three in the morning.
- A reading read against its limit and its trend, not just its last value.
- Overdue work and out-of-spec readings surface without being asked for.
- One plant, or every plant at once, in the same view.
Template library
Nobody starts from a blank page
Hundreds of ready-made procedures across multiple industries, written the way the trade writes them — not a checklist with your logo on it. Pick one, and it opens in the editor as yours to change.
- Grouped by trade, so a dental practice and a haulier each find their own shelf rather than a generic one.
- Real procedures with the readings, tolerances and sign-offs in them, written against the standards the inspection is actually held to.
- Nothing is locked. Rename it, cut half of it, bind it to your own machines — from the moment you pick one it is your document, and ours never changes it again.
The library is part of the Multi edition and up, and four sample procedures are open to every trial. On Single you write your own — as many as the edition holds. Compare all editions →
See the libraryTriggers
Some work cannot wait for a calendar
A calendar knows what day it is. It does not know that a pump has run five hundred hours since its last service, or that the control system raised an alarm at three in the morning. A trigger knows — and it opens the work order while the shift that needs it is still on.
- Every 500 running hours, not every 90 days. A pump that ran flat out in January and idled through February is not due on the same day as one that did the opposite.
- An alarm at 03:14 becomes a job on the 06:00 handover — machine already named, procedure already attached, nobody woken up.
- One order per machine, however often the alarm repeats. A fault that stands for a week does not become three hundred tickets.
Every rule can be tried before it is switched on: it shows you which machines it watches and what it would do to each of them right now, without creating anything.
Features
What the system actually does
This is a list of what the application does today, not what it is planned to do.
Work orders that generate themselves
Templates carry their own schedule — daily, weekly, monthly, yearly. Every morning the day’s work orders exist, at the plant’s own midnight. If a day is missed, catch-up fills it in.
A procedure editor that draws
Build a procedure as a flow of steps, readings and checks on a canvas, and bind each step to the equipment it belongs to.
A passport for every machine
Identity, documents, readings, faults and service history in one place — so a machine’s history outlives the person who remembers it.
The inspection register
Statutory periodic inspections recorded with finding, evidence and dates, ready for whoever asks to see them.
Numbers that answer questions
Done on time, still open, how late, downtime, MTBF — per machine, per site, or across the whole company.
It talks to your other systems
A REST API and keyed ingest for readings a PLC or historian already holds, so nobody types the same number twice.
How it works
Three steps, and then it runs
From a procedure in a binder to a signature on a tablet.
Write the procedure once
The SOP that lives in a binder becomes a template: the steps, the readings to take, the equipment it applies to and how often it comes round.
The morning takes care of itself
At the plant’s own midnight the day’s work orders are generated and put in front of the right group.
The operator signs it off
On a tablet in the plant, step by step, with readings and photographs where they matter. What is signed is kept.
Pricing
One price per plant. Not per person.
Every edition does everything the product does. What separates them is size — how many facilities, machines and procedures the edition is built for, and how much work goes through it in a month.
Single
For one facility that writes its own procedures and keeps its records straight.
Request offer
priced per plant
- Work orders / month
- 250Metered
- Facilities
- 1
- Machines
- 150
- Procedures
- 25
- Procedure library
- Bulk import and export
- Email support
Most chosen
Multi
For a plant that also has to prove it — to an inspector, an insurer or head office.
Request offer
priced per plant
- Work orders / month
- 1,000Metered
- Facilities
- 4
- Machines
- 750
- Procedures
- 150
- Procedure library
- Bulk import and export
- Email support
- Priority support
Group
For several facilities reporting into one office, with systems either side that need feeding.
Request offer
priced per plant
- Work orders / month
- 4,000Metered
- Facilities
- 15
- Machines
- 3,000
- Procedures
- 500
- Procedure library
- Bulk import and export
- Email support
- Priority support
- Assisted setup and data import
- Response-time commitment
On-premise & Custom
For an estate that has to run it on its own servers, or on terms the three editions above do not cover.
Let’s talk
quoted per estate
- Work orders / month
- As agreed
- Facilities
- As agreed
- Machines
- As agreed
- Procedures
- As agreed
- Procedure library
- Bulk import and export
- Email support
- Priority support
- Assisted setup and data import
- Response-time commitment
- Runs on your own servers
- Volume, contract and invoicing terms
- A named engineer who knows your plant
Nothing stops at three in the morning. Work orders are counted, never refused — a round is never blocked because a month was busy, and sustained growth is a conversation at renewal. The ceilings that are enforced are all things an administrator creates at a desk. Prices exclude VAT, and you cancel from inside the app. Compare all editions →
Start with one procedure.
Tell us what you run and who runs it. Every request is read by a person and answered the same working day — and the 3 days start when we say yes, not when you fill the form in.
Request a trial