TwinEdge product family

One physics-grounded operating layer, modular products for industrial action.

TwinEdge gives industrial and utility teams one governed path from source systems to physics-based asset and process context, agents, API/MCP products, edge resilience, AssetOps EAM and EOM, Water Quality and Regulatory, Chemical OS, self-service BI, reporting, field evidence, and industry operating products.

AI-native product familySource data becomes governed context, agents, productized access, BI, reports, and operational execution.GovernedModularNo-cloudEXISTING SYSTEMSAGENTIC OPERATING LAYEROPERATING PRODUCTSConnectsource systemsSCADAPLCsHistoriansMQTTGISCMMSLIMSERPCollectorOT Bridge + OSdry-run, approval gates, audit, and replay by defaultDataOps15 surfacesAsset graph23 facetsTwinsmodelsAgents10 skillsAPI/MCPproductsGovernancereplayWater OSutility operationsWastewater OSevent preventionChemical OSdose + inventoryQuality + LIMSsamples + signoffAssetOps EAMasset executionEOMmanuals + evidenceFieldmobile proofBI + Reportsself-serviceCapital + ESGplans + reportsENTERPRISE STARTER PATHSAnalytics pilotone source + asset classWater startertwin or utility workflowOS analytics kitedge and no-cloud sitesEAM + Fieldrecommendation to workBUSINESS OUTCOMESFaster activationprove one workflow firstTrusted AIdry-run, approval, replayEdge resiliencelocal intelligence stays onClosed-loop workrecommendations to work

Implementation-backed facts

The AI-native product-family claim is grounded in platform objects, agent contracts, and governance controls.

15

DataOps surfaces

Sources, tags, models, pipelines, graph, standards, AI, APIs/MCP, catalog, edge fleet, and monitor.

23

AI context facets

Source, tag, graph, model, namespace, tool, product, recommendation, action, and trace context.

10

Agent skills

Draft, validate, explain, diff, test, and replay workflows bounded by approval gates.

0

Default writeback

Agent-generated changes stay dry-run, diffed, approval-required, audited, and replayable.

4

Deployment paths

Cloud, Collector, OT Bridge, and TwinEdge OS options support enterprise rollout constraints.

1

Shared model

The same physics-aware operational context feeds agents, REST APIs, MCP tools, BI, dashboards, reports, work, and evidence.

Physics-grounded operating layer

Products fit together because they share the same operational model.

TwinEdge puts AI inside the same operating model used by enterprise teams: source health, asset identity, physics model bindings, operating envelopes, approvals, work, field proof, API products, and replay history stay connected.

Source health
Asset identity
Physics context
Approved action
1operating record
7shared layers
0blind handoffs

Data and edge layer

Connectors, collectors, OT Bridge, TwinEdge OS, protocol access, local telemetry, store-forward, inference, and cloud sync.

Context and twin layer

Asset models, semantic mappings, canonical graph, physics equations, operating envelopes, process context, digital twins, and standard profiles.

Agentic recommendation layer

Activation state, pack binding, physics anomaly context, readiness briefs, explainable recommendations, traces, and decision history.

BI and reporting layer

Self-service BI, dashboards, executive reports, regulatory packages, operational KPIs, disclosure support, and evidence-backed exports.

API and MCP layer

Tenant-scoped, audited, contract-tested REST products and read-only MCP tools for approved applications and copilots.

Execution layer

AssetOps EAM, Electronic O&M/EOM, Field, inspections, inventory, safety gates, mobile workflows, compliance evidence, and work handoff.

Governance layer

Credential redaction, source evidence, dry runs, approval gates, display-safe outputs, audit trails, and replay.

Platform in action

One platform story across several products, features, and operating modules.

The screenshots below are a curated path through TwinEdge: connect data, run the edge, bind context to a digital twin, govern agent recommendations, execute work in AssetOps, preserve quality evidence, and plan capital from the same operational record.

Datasource layer
Twincontext layer
Workexecution layer
Proofevidence layer

Enterprise starter paths

Start with one measurable workflow, then expand across the family without rebuilding context.

The brochure makes the adoption motion clear: prove a focused operational outcome first, then carry the same governed physics-aware model into twins, WaterOS, WastewaterOS, Chemical OS, Water Quality and Regulatory/LIMS, TwinEdge OS, AssetOps EAM/EOM, Field, API/MCP products, BI, and reporting.

One asset class

Analytics Activation Pilot

Connect one source, map one asset class, activate one analytics pack, publish governed outputs, and prove one measurable outcome.

Risk and what-if

Water Twin Starter

Activate a focused twin for a pump station, lift station, treatment process, network zone, DMA, or chemical dosing process.

Utility operations

Water OS Starter

Create an operating layer for one utility tenant, one site, or one focused water utility workflow.

Event prevention

Wastewater OS Starter

Focus on lift station reliability, SSO prevention, collection intelligence, or treatment process visibility.

Edge and no-cloud

TwinEdge OS Analytics Kit

Deploy TwinEdge OS with protocol setup, store-forward, local dashboard, local inference option, cloud sync, and one analytics workflow.

Work execution

AssetOps EAM and Field Starter

Connect enterprise asset hierarchy, physics-based condition, work orders, PM tasks, mobile execution, evidence capture, and recommendation handoff.

Chemical operations

Chemical Optimization Starter

Connect chemical inventory, dosing, residuals, SDS and safety context, reorder recommendations, dose optimization, and compliance evidence.

Quality evidence

Water Quality and Regulatory Starter

Connect sample schedules, field collection, custody, instrument records, LIMS-style result ingestion, QC review, exceedance workflows, and compliance reporting.

Enterprise reporting

BI and Reporting Activation

Publish governed dashboards, self-service datasets, executive reports, regulatory packages, and evidence-backed operational metrics.

Business outcomes

Start with one source, one asset class, and one governed recommendation workflow.

Enterprise teams can evaluate TwinEdge in a focused scope, then expand into edge deployments, physics-based digital twins, API/MCP products, AssetOps EAM/EOM, Field, Chemical OS, Water Quality and Regulatory/LIMS, self-service BI, compliance evidence, reporting, and industry operating products as the operating model proves itself.