Read the pump
TwinEdge OS collects the signals at the site, even if the network drops.
Platform overview
See what the pump is doing. Act before it fails.
TwinEdge reads a pump, keeps its history, explains extra power or wear, turns that into a repair job, and helps you decide whether to keep, repair, or replace it. It works with the systems you already have.
- Less surprise downtime. Catch wear early and plan the stop.
- Lower energy cost. Find a pump using more power for the same work.
- Fewer emergency repairs. Give the crew the history, job, and parts.
- Better capital decisions. Compare repair versus replace with real history.
ONE PUMP. THE FULL PRODUCT FAMILY.
START WITHPump readings
TWINEDGE CONNECTSOne record for the machine
MOVE FORWARD WITHA repair or replace decision
THE WORKFLOW
What TwinEdge does for this pump.
Keep the history
Historian stores what this pump has been doing, with time, units, and identity.
Explain the change
Analytics and the digital twin show why it is using more power or wearing faster.
Do the repair
AssetOps and Field turn the finding into a job, parts list, and closeout.
Plan the spend
Capital Planning compares repair versus replace using the same pump record.
Less surprise downtime
See wear early and plan the stop, instead of waiting for a failure.
Lower energy cost
Find a pump that is using more power to do the same work.
Smarter capital spend
Repair or replace with the history, energy, and service cost in one place.
FROM THE PRODUCT
See the work in context.
Select a screen to explore the workflow. Open it for a closer look.
01 / INSIDE TWINEDGE
DataOps Workbench
The DataOps workspace shows source health, asset binding, namespace readiness, recommendations, models, canonical graph, standards, and edge fleet.
BUILT FOR THE OPERATION
The context your team needs.
Industrial DataOps
A workspace for sources, tags, models, physics inputs, instances, pipelines, namespace, graph, catalog, APIs, MCP, and monitoring across operational systems.
Governed agentic analytics
Agents use operational context, physics model outputs, and operating envelopes to prepare evidence-backed recommendations with dry-run plans and approval gates.
Complete execution layer
AssetOps EAM, Field, Water OS, Wastewater OS, TwinEdge Chemical, Water Quality, Capital Planning, ESG, APIs, and MCP use the same trusted context.
GO DEEPER
Details for your operating context.
Every seam between two systems is a place the truth goes missing.
Most plants run separate tools for readings, charts, maintenance, and reporting. People join them by hand. TwinEdge keeps the reading, the analysis, the work, and the capital decision on one asset record, so there is nothing to retype at a handover.
- Nothing to keep in step. Four tools need six connections. One shared record needs none, because the data was never apart.
- Repairs on condition, not on a date. When maintenance can see the machine, it schedules by what the machine is actually doing.
- You can start anywhere. Keep the SCADA, historian, and maintenance system you run today, or replace them a piece at a time. Either way it stays one record.
Industrial teams are drowning in data but still short on operational truth.
SCADA screens, historians, GIS maps, CMMS records, lab results, spreadsheets, PDFs, and operator notes all hold part of the answer. When something goes wrong, teams lose time reconciling systems instead of acting on a trusted view.
- Signals lack context. Raw tags and alarms rarely explain which asset is affected, how critical it is, what changed, or which procedure applies.
- Work is disconnected from evidence. Maintenance, field work, compliance review, and capital planning often depend on screenshots, exports, and manual justification.
- AI cannot help without trust. Generic copilots are risky when they cannot prove source context, role scope, approval state, and what evidence supports a recommendation.
TwinEdge connects the cause, the consequence, and the next best action.
The platform is designed for measurable industrial outcomes: faster investigations, fewer avoidable failures, better maintenance decisions, lower operating waste, and cleaner audit evidence.
- Faster exception response. Operators and engineers see the asset, telemetry, history, recommendations, and evidence trail in one investigation path.
- More reliable work planning. Maintenance teams can prioritize work from condition, criticality, procedures, parts context, approvals, and recurring risk patterns.
- Clearer executive reporting. Leaders can review operating risk, asset health, energy performance, compliance readiness, and capital needs from a consistent model.
Find the reason faster when alarms, work history, and documents point in different directions.
TwinEdge gives teams a shared timeline of readings, events, operating state, recommendations, approvals, and work evidence so troubleshooting does not start from a blank search.
- One timeline for the event. Bring telemetry, alarms, recent work, asset condition, procedures, lab context, field notes, and source evidence into the same review path.
- Recommendations with boundaries. AI-supported findings show the source context, confidence, assumptions, approval state, and next action before work is handed off.
- Replay for learning. Teams can review what happened, why a recommendation was accepted, who approved it, and how the final work was closed out.
CONNECTED BY DESIGN
Fits the systems around it.
Keep source context available as the workflow moves between teams and applications.
One connected record.
Platform overview
- DataOps Workbench creates the physics-aware, AI-ready context.
- Agentic Analytics uses that context to explain, draft, and validate recommendations.
- TwinEdge OS supports cloud-connected, offline, and protocol-rich edge deployments.
- AssetOps EAM and TwinEdge Field close the loop from recommendation to work, guided mobile diagnostics, human-reviewed evidence, and closeout.
- Water OS, Wastewater OS, TwinEdge Chemical, Water Loss OS, Water Quality, Capital Planning, ESG, and Facility OS package industry workflows.
- REST and MCP data products make context available to enterprise applications and AI systems.
BEFORE YOU START
A few useful answers.
What does TwinEdge do?
It connects a piece of equipment to its history, the reason a problem appeared, the maintenance job, and the decision to repair or replace it. The pump example on this page is the same loop for compressors, blowers, chillers, and other machines.
Do we have to replace our current systems?
No. TwinEdge can read from the control system, historian, and maintenance system you already run. You can keep those tools, or switch later. Migration is free if you choose to switch.
What do we get from it?
Earlier warning before a failure, less wasted energy, clearer repair jobs for the crew, and a better basis for repair-or-replace decisions. Every step stays attached to the same equipment record.
Where does it run?
On-premise, in the cloud, or both. TwinEdge OS can keep reading and storing at the site if the network is down. Capacity, usage, and token cost are set after a needs assessment.
Can it change the pump by itself?
No. Recommendations wait for a person to approve. Writeback to equipment is off unless you turn it on for a specific machine.
THE NEXT CONNECTION
Explore the product familyBuild the rest of your loop.
START WITH YOUR OPERATION
Put the next decision in motion.
Discuss your sources, assets, and the outcomes your team wants to improve.