Breakdowns are reported by phone
A request arrives as a call, gets written on a board, and its history exists only in the memory of whoever took it.
Maintenance
A CMMS that already knows your people and your spares
Reactive requests and preventive plans in one asset register — with parts issued from the warehouse and technicians whose competence the system has already checked.
Eleven tools · Preventive and reactive · Issues spares from Inventory
Illustrative product view with sample data. Request a live walkthrough.
Before Caspian ERP
The maintenance system knows the machine and nothing else
A standalone CMMS has its own asset list, its own people list and its own spares list. Keeping three lists in step is the actual job.
Preventive plans slip quietly
The plan says quarterly. The last one was seven months ago. Nothing raised its hand, because nothing was watching.
Spares come off the shelf uncounted
The technician takes what they need. Stock is wrong, the job cost is wrong, and the next planner works from both.
What it does
Everything the equipment needs, in one register
Reactive work, planned work, calibration and warranty — against the same assets.
An asset register that carries its history
Every piece of equipment as a record: what it is, where it is, and everything that has happened to it.
- Assets with location, criticality and documents
- Full work history against the asset, not against a person’s memory
- Vehicles and production equipment in the same register
- Failure codes so patterns can actually be seen
Requests and work orders
Reactive work raised by anyone, triaged, assigned and closed with what was done.
- Requests raised from the field on a phone
- Triaged into scheduled work with an owner and a priority
- Parts issued from stock as part of closing the job
- The job cost built from labour and material actually used
Preventive plans that raise their own work
Time-based and meter-based plans that generate the work rather than relying on a reminder.
- Preventive plans per asset with interval and scope
- Meter readings driving usage-based servicing
- Maintenance checklists attached to the planned job
- Overdue preventive work visible before it becomes a breakdown
Calibration with certificates
Instruments tracked with their calibration status, due dates and certificates.
- Calibration schedule per instrument
- Certificates stored against the asset
- Out-of-calibration equipment flagged before use
- The evidence a client or auditor asks for, on demand
Warranty claims that get made
Warranty status held with the asset, so claims happen while they are still valid.
- Warranty periods recorded per asset
- Claims raised against the supplier and tracked
- Linked to the failure that triggered them
- Money recovered rather than quietly written off
Meter readings and failure analysis
Usage and failure data captured routinely, so reliability work has something to stand on.
- Meter readings recorded in the field
- Failure codes applied consistently at closure
- Repeat failures visible per asset and per code
- Preventive intervals adjusted from evidence
From a breakdown call to a closed job
And the same register drives the preventive work that stops the call happening.
Request raised
Assigned
Spares issued
Checklist done
Failure code
Closed
Every tool in the module
Eleven tools for keeping equipment running
Reactive, preventive, calibration and warranty in one module.
Assets
The equipment register — location, criticality, documents, warranty and full work history.
Requests
Reactive maintenance raised by anyone in the organization, from a phone, and triaged into work.
Schedule
The forward view of planned and assigned maintenance work across assets and technicians.
Maintenance Dashboard
Backlog, overdue preventive work, breakdown frequency and cost, on one screen.
Meter Readings
Hours, kilometres and cycles recorded in the field to drive usage-based servicing.
Calibration
Calibration schedules, statuses and certificates for instruments that must stay verified.
Warranty Claims
Claims raised against suppliers while the warranty is still live, linked to the failure that caused them.
Failure Codes
A consistent vocabulary for what went wrong, which is what makes reliability analysis possible.
Maintenance Checklists
Standard task lists attached to planned jobs so the work is done the same way every time.
Preventive Plans
Time-based and meter-based plans that generate their own work orders on schedule.
Preventive Actions
The individual actions a plan produces, tracked to completion like any other work.
Connected, not bolted on
The three lists a standalone CMMS has to duplicate
Here they are the same records the rest of the organization uses.
Spares from real stock
Parts issued to a job are stock movements, so the warehouse figure and the job cost stay true to each other.
Technicians with current tickets
Work is assigned to people whose certificates and training the platform already tracks, so competence is checked before dispatch.
Permits and isolations
Maintenance on live plant needs a permit — and the permit, the asset and the technician are all records in the same system.
Who lives in it
For everyone between the breakdown and the fix
Requester, planner and technician on one register.
Maintenance planner
Balances preventive plans against the reactive backlog and sees what is overdue before it becomes a failure.
Technician
Works from a job list on a phone, follows the checklist, issues the spares and records the failure code at closure.
Operations supervisor
Raises a request in seconds and can see where it sits, instead of ringing the workshop for an update.
Yours to shape
Configure maintenance to your equipment strategy
Criticality, intervals and codes are yours — they are the whole reliability strategy.
- Define asset criticality and let it drive priority on requests
- Set preventive intervals by time, by meter reading, or by both
- Build your own failure code list so the analysis matches your equipment
- Attach standard checklists to planned jobs, per asset type
- Decide who may raise a request, who may schedule, and who may close a job
Maintenance · Settings
| Setting | Value |
|---|---|
| Preventive trigger | Time + meter |
| Request raised by | Any member |
| Spares issue | From stock, mandatory |
| Failure code at closure | Required |
| Calibration warning | 30 days |
Maintenance questions we get asked
Do preventive plans create work automatically?
Yes — plans generate preventive actions on their interval, by date or by meter reading, so overdue servicing surfaces on its own rather than depending on someone’s reminder.
Are vehicles maintained here or in Logistics?
Here. A vehicle is an asset, so its servicing, meter readings and preventive plans run through Maintenance. Logistics handles the journeys it makes and the documents it carries.
Can technicians work from a phone in the field?
Yes. Requests, job lists, checklists and meter readings are all designed to be used in a phone browser, which is where most of this work actually happens.
Does issuing a spare part update inventory?
Yes. Parts issued to a work order are real stock movements against the warehouse, which is what keeps stock accurate and gives the job its true material cost.
Can we track calibration certificates for client audits?
Calibration schedules, statuses and certificates are held against the instrument, so producing evidence is a filter rather than a search through folders.