Getting started
One site, done properly
A pilot here is not a sandbox and not a slide deck. It is your equipment, your people and your work running on Powoflow, small enough to finish, real enough to judge.
Standing up your workspace
All of this happens before anyone books a van. Plenty of pilots prove their value here and add hardware afterwards.
We set up your workspace
We create your tenant, its own isolated identity organisation, and the top-level structure, sites and locations, physical assets, partners, inventory, edge devices. Your first admin gets an invitation by email and can bring the rest of the team in straight away. You deal with the people who built it, not a queue.
Your industry, already modelled
Pick a starting template and it seeds typed asset classes with their field schemas, the rules for what can contain what, ISO 14224 failure coding and preventive-maintenance intervals. Across the nine templates that is 111 asset types, 92 failure modes and 89 maintenance intervals, yours arrives configured, and all of it is yours to edit.
See it working before you commit data
Six templates deploy a complete worked estate in one click. A campus, a plant, a depot, a vehicle fleet, an offshore fleet or an off-grid power system. Click through a populated hierarchy and decide whether the shape fits your operation before anyone exports a spreadsheet.
Bring the register you already keep
Assets load from CSV, name, type, parent, description, status and tags, with a preview that catches problems row by row before anything is written. Most first pilots start from the register you already maintain rather than from new data collection.
Putting a Field Agent on site
For when you want live data off the equipment itself, vibration, power, temperature, cameras, controllers.
We commission the Field Agent
Not a box you unpack and configure. An engineer runs commissioning end to end, imaging, hardening, registration, runtime install and a health check, and hands it over already reporting. Your one step is pasting a claim code into your workspace to bind it to your tenant.
What the site needs
DIN-rail space, power, 9 to 36 V DC or Power over Ethernet, and a network drop with outbound internet. Typical draw is about 5 W, so it goes in an existing cabinet on existing power. Genuinely isolated sites are workable too; tell us early and we plan for it.
It powers your cameras too
Five gigabit ports, three of them supplying Power over Ethernet at 12 W each, so cameras run straight off the Field Agent with no separate injector or second enclosure. Wi-Fi is on board, cellular and LoRaWAN drop into module slots, and serial, CAN and isolated digital I/O are there for equipment older than any of it.
Live in one visit
Commissioning is a single scripted command, so a Field Agent goes from boxed to reporting within one site visit rather than across a scheduled engagement. Add sensors later and they appear against the assets you have already modelled.
What you have at the end
Your site modelled as a hierarchy your engineers recognise, with failure coding and maintenance intervals against every asset class. Work orders running through it carrying parts, hours and signatures on the record. Whatever you chose to instrument arriving against the assets it belongs to and raising the alarms you set. And an audit trail underneath all of it, because it was never a separate feature.
Then a straight answer to the only question that matters: did it catch something you would otherwise have missed, and will your team keep using it once we stop paying attention.
Worth knowing before you start
We are pre-launch, and a pilot runs with us alongside you rather than handed over. We create the workspace, commission the hardware and load the standard report set. Templates bring your asset classes, failure coding and maintenance intervals; alarm rules and checklists you set to match how the site actually runs. Moving off an existing maintenance system is a CSV import and a conversation, not a migration service. And if you need your corporate directory federated on day one, raise it early. Every tenant is built as its own identity organisation ready for it, though we have not connected one yet.
What we need to quote it
Three things: how many sites, roughly how many devices per site, and which optional modules matter. Assets, hierarchy, alarms and telemetry are always included; work orders, projects, inventory and the data explorer are what move the number. The contact form asks for all three, so the first reply can be an actual price rather than three more questions.
The most useful thing you can bring is a job that went wrong. A failure nobody saw coming, an audit that cost a fortnight, a report somebody rebuilds by hand every month. Ten minutes on that tells both of us more than an hour of features.
Start with one site
A pilot that covers one site properly is worth more than a rollout nobody has time to finish.