Connected Operations
Everything in the field. One home for it all.
Powoflow puts your equipment, robots, sensors and field data at the centre of your operations. Everything else attaches to it: the work, the parts, the costs, live video and photos, compliance and sign-off.
Powoflow is pre-launch. We are working with a small number of selected customers rather than opening sign-ups, because at this stage each deployment teaches us something and we would rather do a few properly than many badly.
Powoflow is genuinely built and running. This site describes what exists, not what is planned, and says plainly which certifications we do not hold. If you are considering it, the honest first step is one site and one question you cannot currently answer.
The asset has a home
Everything in Powoflow hangs off one structure: a graph of the things you actually operate. Not a folder tree bolted onto a maintenance database. A model with typed relationships, inherited properties and rules about what can contain what.
Containment is only part of how a plant is wired. A pump sits in a room, belongs to a system, and is fed by a switchboard three levels away. Those are different relationships, and keeping them apart is what lets you ask what is downstream of this and get an answer rather than an opinion.
Reference designations follow ISO 81346. The location, function and product aspects resolved across the graph into one designation. Engineers who already work this way do not have to translate. Everyone else never has to see it.
How the graph works“What’s the condition of that engine, who signed off on it, and what has it cost this year?”
Simple question. No fast answer. The truth is scattered across multiple systems and none of them talk to each other.
Automation & sensors
No memory of what was done about it.
The maintenance system
What was planned. Not what happened.
ERP & purchasing
What was bought. Not what it went into.
Email, PDFs, paper
Someone approved it. Finding proof is archaeology.
A person's memory
Your best record. Also the one that walks off.
Multiple systems. Multiple owners. No shared model of the equipment itself: it exists in all of the systems, and in none of them.
What runs on top
Four things Powoflow does with that structure.
Sense
Get the readings, and keep getting them when the link drops.
Decide
Turn a stream of numbers into the few that need a person.
Work
Do the job, and have the record at the end without writing it.
Govern
Know who did what, and keep tenants genuinely apart.
Works when the link is up, and when it is down
Anything can forward messages while the network is good. What matters is the hour it is not. Field Agents at the site run their own time-series database, do their own inference, and replay what the cloud missed once the link returns.
A satellite outage should cost you latency, not data, and a vibration event at 3200 Hz should be processed beside the sensor rather than shipped across the world to be averaged.
Inside a Field AgentDashboard
Last updated: 2 min agoPump Station Alpha returned to service
2 min ago
Bearing temp alarm acknowledged
15 min ago
WO-2026-0042 task completed
1h ago
Scheduled backup completed
3h ago
Built to the standards your people already use
Implemented in the product, not referenced in a slide. None of these is a certification, and we say so on the security page.
Alarm management
Full alarm state machine, normal, unacknowledged, acknowledged, cleared, with shelving, out-of-service, flood protection and chatter suppression.
Reliability & maintenance data
Four-level failure coding on every work order: detection method, failure mode, mechanism, cause. The vocabulary is enforced server-side. An out-of-vocabulary code is rejected, not stored.
Reference designation
Location, function and product aspect chains resolved across the asset graph into a single designation such as =K1+B2.R3-A1.
Manufacturing hierarchy
Site, area, production line, work cell, equipment, shipped as a domain template, not a diagram in a slide deck.
Facilities information
Structures the facilities-management domain template.
Field Agent baseline
Every Field Agent is commissioned to one fixed baseline: host firewall closed by default, remote access locked down, mandatory access control, intrusion detection and file integrity monitoring, and its own identity and credentials per device. Not a checklist someone runs afterwards, a scripted step that has to pass before the device is handed over.
Industries
9 domain templates ship. A ready-made hierarchy, asset types and failure taxonomy to start from rather than build. Industries below that map to one are marked; a few share a template. The unmarked ones we address without a pre-built starting point.
We sit above your systems. We do not replace them.
Powoflow reads, correlates and presents. It never sits inside a control loop and never actuates a safety function. That boundary is deliberate, and it is why this can be added to a plant without re-qualifying one.
What it runs on
Bring a question you cannot currently answer
The useful first conversation is about one piece of equipment and one question about it that today takes five minutes and three phone calls.