Evidence
TwinEdge proof, benchmarks, and evaluation evidence
Buyers and AI agents should be able to distinguish measured benchmarks, modeled projections, evaluation methods, and product control claims. This page keeps those categories explicit.
Competitive local benchmark
TwinEdge OS edge throughput benchmark
At a 20,000-tag tier, TwinEdge measured 20,333.3 stored readings/s with 100 ms p95 source-to-ingest, 1.000 store ratio, zero sequence gaps, and zero replay lag in a local lab-style probe.
- •Competitive local benchmark, not a vendor device certification.
- •Compares TwinEdge p95 source-to-ingest plus storage acceptance against publicly referenced Siemens IIH Semantics processing figures used as a baseline reference.
- •Rerun gates on target ARM64 or x86 industrial hardware with soak and power-loss recovery before production sizing.
Modeled projection — not a customer case study
Modeled water/wastewater impact ranges
Homepage modeled ranges include fewer sanitary sewer overflows, lower energy spend, and fewer manual inspections under defined hydraulic and condition-assessment assumptions.
- •Modeled outcomes are labeled as modeled and are not customer case studies.
- •Results depend on site hydraulics, asset condition, operating policy, and data quality.
Evaluation method
Closed-loop AssetOps evaluation path
TwinEdge recommends a narrow pilot: one source, one asset class, one governed recommendation or work workflow, then expand. This is the productized path used in starter packages such as AssetOps Field Starter and Water Twin Starter.
- •Pilot outcomes are customer-specific and should be measured against an agreed baseline.
- •No universal downtime or energy reduction percentage is claimed for all sites.
Product control evidence
Governance and safety posture
Agents are recommendation-first and read-only by default, with dry-run, approval, audit, and replay controls. Field mobile diagnostics are screening evidence, not certified scientific measurement or safety clearance.
- •Customer policy can tighten or expand operational handoff only under governed configuration.
- •Safety PLC and SIS remain authoritative.
Pilot scorecard template (blank)
Use this checklist in discovery. Do not fill with invented results — measure against a customer baseline.
- • Baseline period and sites/assets in scope
- • Source systems connected (protocols, historians, CMMS, GIS)
- • Deployment topology (edge / hybrid / cloud) and network constraints
- • One primary workflow (recommendation → approval → work → closeout)
- • Metrics agreed in advance (alarms, work lag, energy, truck rolls, etc.)
- • Safety and writeback policy confirmed (approval-first by default)
- • Commercial scope drivers logged (integrations, compute, support)
Entry commercial reference: enterprise pricing from $1,000/month, final quote deployment-dependent.