ERP for industrial and technical services

Assets, maintenance, work orders, spare parts and billing in one system – with no interface to maintain.


Built for companies that sell service, not units

If your revenue comes from keeping equipment running rather than shipping it once, your ERP has a different job to do.


Facility and building services

Planned maintenance and reactive call-outs across a portfolio of customer sites, with one contract, one asset register and one invoice run behind them.

Industrial maintenance contractors

Corrective and preventive work on customer plant, where the skills, tools and spare parts are settled before the technician leaves the depot rather than discovered on site.

Machinery and equipment service arms

Manufacturers servicing their own installed base: warranty, service contracts, spare parts and the aftermarket revenue that is often half the margin.

Energy and technical services

Inspection, testing and maintenance regimes on distributed assets, scheduled by date, meter reading or operating hours rather than by memory.

Fewer second visits to the same site

A return trip costs a day of margin, and most of them are booked the moment a job is assigned to somebody without the right part or the right ticket.


The Onfinity scheduling and dispatching board: open tasks on the left showing the customer, the site and the skills each job requires, dragged onto named technicians across the top for a chosen day

The skills, the tooling and the parts are settled before anyone leaves the depot. Open tasks carry the customer, the site and the qualification the job needs, and are assigned onto named technicians for the day.

Open service requests by type – breakdown, adhoc and corrective maintenance – each with a Convert action that raises the work order, beside an aging analysis of open work orders by age band

Nothing quietly ages past its response commitment. Requests arrive typed – breakdown, ad-hoc, corrective – and convert straight into a work order against the same asset, with the aging view standing in as the escalation list.

One system. One data model.


A dedicated field service tool has to be integrated with whatever ERP you already run. That integration is the project cost, the go-live risk and a maintenance burden that never ends – and it is where the numbers start to disagree.

In Onfinity the service order, the spare part, the asset, the service contract and the invoice are the same records. Not synchronised copies in two systems. Nothing to reconcile, nothing to re-key, and one place to ask what a job actually cost.


What you get out of the box

Service and maintenance is one of the deepest parts of the platform – and it is standard, not a custom build.


Assets and functional locations

A structured register of what you maintain — equipment, its location in the plant, its history and the parts installed in it. The same model the large maintenance systems use.

Maintenance by date, counter or running hours

Preventive schedules triggered by calendar, meter reading or operating hours, carrying their own task lists, checklists, tools and expected spare parts.

Work orders and dispatch

Plan by qualification, availability and required tooling. Fewer second visits because the right technician arrives with the right part.

Spare parts and stock

Parts reserved against the job and consumed from real stock, so the warehouse and the service order never disagree.

Service contracts and SLAs

Contract-linked work orders, so entitlement and response commitments are checked when the job is raised, not argued about when it is invoiced.

Margin per order, asset and contract

Labour, parts and travel land directly in the order and the invoice — so profitability is reportable per job, per asset and per contract without a spreadsheet.

Service the machine, not the calendar

Time-based schedules service healthy machines and miss failing ones. Both cost money.


An Onfinity asset record for a 50 MVA transformer cooling system: substation, rated power, voltage ratio, vector group, impedance and RTU, with live high- and low-voltage measurements read over IEC 61850, each carrying its source signal path, quality flag, timestamp and age

Trigger on condition, not on a date

Equipment in Onfinity is not just a row with a serial number. Where a plant has instrumentation, the asset record carries its live condition – here a 50 MVA transformer reporting HV and LV measurements over IEC 61850, each value stamped with its source signal path, quality flag and age.

That is what turns a maintenance schedule from a calendar into a decision: trigger on a meter reading or a running-hour count, not on a date somebody picked.

The Schedule Service dialogue in Onfinity offering two routes from an asset: raise a reactive, on-demand service or repair request, or set up a recurring planned maintenance schedule

Both routes start from the asset itself – a reactive repair request, or a recurring preventive schedule. Planned and unplanned work, on the same record.