One record for every asset, visit and contract.
A pump station, a substation bay or a fuel storage tank collects years of inspections, repairs and paperwork. We build the business software that keeps that history in one place for the office and the crews in the field.
Picture a maintenance engineer standing beside a transformer that tripped overnight. The last inspection report is in a colleague's inbox, the vendor's warranty letter sits on a shared drive, and the previous repair was logged in a spreadsheet the contractor kept. Before anyone touches the equipment, an hour goes into finding out what has already been done to it.
Energy businesses run into this gap because the work is divided between a control room, maintenance crews, outside contractors, a commercial desk and finance. Each group has its own tool, and each tool names the same piece of equipment a little differently. Our work sits in the administrative layer: asset registers, work orders, inspection records, contracts and customer requests, all keyed to one agreed asset ID.
We do not build or alter control systems. SCADA, protection settings, permit-to-work and anything that can operate equipment stay with your specialist vendors and the engineers accountable for them. If our software needs to read from those systems, we agree what is read, how often, and who on your side signs off the connection.
Where the history goes missing.
The report arrives as a scanned PDF.
An outside crew services a gas compressor and emails its report a week later. Someone in the office has to file it against the right unit and note the parts replaced. An upload page tied to the open work order removes that chore.
The night crew saw something.
An operator notes an oil leak in a paper log. The day shift needs to know whether it became a defect, who owns it, and whether it can wait for the planned outage.
Every inspection since commissioning.
An insurer or internal auditor asks for the complete inspection record of one asset. With an audit trail on each record, answering is a filter on a screen instead of a week of digging through folders.
A customer calls about their supply contract.
Sales wants the contracted volumes, the open invoice dispute and recent service tickets for that site on one screen before returning the call.
Which side of the line is ours?
The split we would propose, before any detail is agreed.
Settle these before any screen is drawn.
A sensible first release is the asset register and field work orders for one site, with commercial records added once the IDs hold up in use.
- Asset IDs. Which numbering wins when the plant tag, the finance asset code and the manufacturer's serial disagree.
- Sites and access. Which staff and contractors may see which locations, set up through roles and permissions from the start.
- Field conditions. Where crews lose signal, whether they work in gloves, and which devices they really carry.
- Evidence rules. Which jobs need photos, readings or a supervisor's approval before they can close.
- Old records. Which spreadsheets and maintenance exports are trustworthy enough to import, and who checks them.
- The interface boundary. Which operational systems we may read from, and who owns that decision on your side.
What energy teams ask us.
Can several plants or depots share one system?
Yes. Each site keeps its own assets and crews, and managers get a combined view across them. Permissions decide who sees which location.
Will this replace our maintenance software?
Not necessarily. If an existing tool handles planned maintenance well, we can connect to it and build only what it lacks, such as contractor uploads or commercial records. Our guide on custom or ready-made software covers that choice.
Who looks after the system once it is live?
We can host, maintain and keep developing it, or hand it to your IT team with documentation. The code and the data belong to you in both cases.
Tell us about one asset that caused trouble.
Walk us through how its history is kept today and we will suggest where software would help first.