Ask five systems the same question and you get five answers.
We build the one that settles it. One system that reads across your ERP, your maintenance system, the plant floor, the portals, the drawings and the contracts, reconciles them and names the record every figure came from. Then it does the work that follows: the draft, the pack, the notice, the claim. Built for your company, on your infrastructure, one at a time.
See it as your operation
Built for groups with more than one site, more than one system of record, and a monthly ritual of assembling the numbers by hand. Switch the operation and watch it become a different company’s system.
An illustrative system. Every build is named for your roles, works to your rules and runs on your accounts.
One morning, five systems
This is the work nobody can do at four in the morning, and the reason none of it gets done until somebody complains. Every step names the system it read and the record it read there, because an answer you cannot trace is not one you can act on.
- 04:40Monitoring portal
Pump 3 on site 14 trips offline
Read within the minute, along with every other plant on the fleet. Nobody is awake.
Fault code 4102, third trip in eleven days - 04:41Asset register
It checks what this asset actually is
Not the model on the nameplate – the one in your register, with its history attached.
Warranty lapsed 3 months ago, asset PMP-14-03 - 04:41Maintenance system
And when it was last serviced
Against what the service contract requires, rather than what was scheduled.
Last serviced 14 months ago; the contract says six (work order 88214) - 04:42The O&M contract
It reads what this outage costs you
The availability guarantee is a clause, not a number in somebody’s head. It is read as written.
Guarantee 97%. This outage puts the month at 96.2% (clause 8.3) - 04:43Spares and stores
It finds the part, and where the part is
One impeller on the shelf, and not at the store nearest the site.
1 on hand, Nelspruit store, 4 hours from site (SKU 30-4471) - 04:44Drafted, not sent
Four things are drafted and waiting for you
The technician dispatch. The client notification, worded as the contract requires. The spares transfer. And a claim note against the provider who missed the service interval, while the evidence is still fresh.
- 07:30Your phone
One line, one decision
“Pump 3, site 14 is down and puts you under your availability guarantee this month. The part is in Nelspruit. Approve the dispatch and the client notice?” You reply yes, at a robot, in the car.
Nothing above was sent by a machine. Four things were drafted and one person approved them, which is the only arrangement that survives the day it gets something wrong.
What this is not
You have probably been sold some of these already. If one of them would actually solve this, buy it instead and keep your money.
Answers confidently, and cannot show you why
It will give you a figure. It will not tell you which of your five systems that figure came from, or that two of them disagreed. The test is not whether an answer sounds right – it is whether you would sign something on the strength of it.
Answers only the questions someone predicted
A dashboard is a set of questions frozen when it was built. The question that matters this month – why this site is behind, which claim is about to lapse – was not one of them, and adding it is a change request with a queue.
Eighteen months to make five systems agree
The classic answer is to replace or unify the systems. It takes two years, costs more than it saves, and the plant floor still keeps a spreadsheet. Reading what you already run, and reconciling it with the source named, is faster and changes nobody’s job.
The work is not hard, it is relentless
Assembling the month by hand is a job someone can do. It also stops when they are on leave, leaves nothing behind when they resign and costs more every year. The system takes the part of their week that never needed a person.
Three rules that do not move
Draft, approve, send
The agent drafts. A person approves. Nothing reaches a client, a supplier or a municipality without that tap. Money movement and filing always stay human.
Your accounts, your data
Every account the system runs on is registered in your name. On request and on exit you receive a five-part export: schema, data, configuration, documentation and access list.
Objective acceptance
Twenty real messages classified correctly against a key you agree. If a stage fails its test it is not accepted and not invoiced. The criteria are in the agreement.
Three ways to start
Nobody signs a build off a website, and nobody should. Each of these ends with something worth having whether or not it goes further.
Send us the question nobody can answer
The one that takes three people and a day to assemble. Tell us which systems hold the pieces and we’ll tell you in writing, for nothing, whether it can be answered automatically and what it would take.
Send the questionMap where the operation loses time
Eight minutes. Rank the six places the week goes, describe a bad one in your own words and give four rough numbers. You keep the map, and everything we send afterwards is written from it.
Answer the seven questionsA read-only shadow of your operation
We connect to what you already run, read only, change nothing, and run alongside your month. You get what it found, what it would have drafted and what that was worth. Credited in full against a build.
See what it costsStart with the seven questions.
Eight minutes. Rank where the week goes, describe a bad one and give four rough numbers. You keep the map whether or not we ever work together.