Connect and model your whole fleet.
Fabric is the industrial data ops layer: one runtime per site connects your equipment, digital twins in the cloud model it, and every reading streams into tiered history you query as one.
Asset connectors
Connect any equipment. Manage it from the cloud.
A single lightweight runtime acquires data at the site over four native protocols, buffers it locally, and stays configured and current from the cloud.
One runtime per site
One small piece of software runs at the site. No stack to assemble, no per-protocol services to wire together.
Built-in industrial drivers
OPC UA with subscriptions, plus Modbus TCP, MQTT, and REST. Four native protocols, no plugins to install.
Store-and-forward buffer
A dual hot and cold buffer keeps recording at the site through restarts and through a lost connection, and streams what it holds once the link returns. A gateway that cannot reach the cloud is still collecting.
Cloud-managed configuration
Set up connectors and signal mappings in the cloud; the site picks the change up on its own in about 30 seconds. No manual edits at the site.
Automatic updates
Gateways keep themselves current. New runtime versions roll out automatically, so the fleet stays on a known-good build without a site visit.
A private, isolated network per tenant
Every gateway connects out over an encrypted, per-tenant private link. No inbound ports, no firewall holes, and nothing at the site exposed to the public internet.
Larkspur Wind Farm · GW-01
Edge deployment
Digital twins
A living model of your fleet.
Raw signals become named, typed variables on real assets. The twin is what makes everything downstream fleet-wide instead of per-device, from dashboards to alerts to analytics: one definition on the asset type follows every current and future asset.
Sites, assets, sub-assets
Model your operation the way it actually is: sites contain assets, assets contain sub-assets. Every reading lands on the exact piece of equipment it came from.
Templates with typed variables
Define an asset type once, with its variables, units, and structure, then stamp it across the fleet. Every instance stays consistent, and fleet-wide queries stay possible.
AI-assisted signal mapping
Point Fleetera at an OPC UA server and it suggests how each raw signal maps to your variables. You check the matches before they take effect, and you can always browse and map by hand.
Industry-agnostic categories
Wind turbines, battery racks, pumps, air handlers: categories describe any equipment in any industry, so the same model works across your whole portfolio.
| Variable | Address | Enabled | Source |
|---|---|---|---|
| active_powerTurbine A07 | OPC UAns=2;s=ActivePower | AI | |
| rotor_speedTurbine A07 | OPC UAns=2;s=RotorSpeed | AI | |
| blade_pitchTurbine A07 | OPC UAns=2;s=BladePitch | Manual | |
| nacelle_tempTurbine A12 | OPC UAns=2;s=NacelleTemp | AI | |
| socBESS Rack 3 | Modbus40 001 / holding | Manual |
Streams
From raw readings to a queryable history.
Telemetry is validated and kept in per-asset order on the way in, stored across hot and cold tiers, and served back through a single query that spans your entire history.
Validated ingestion
Every reading arrives tagged with its tenant, site, asset, and variable. The pipeline preserves order per asset.
Hot time-series tier
Recent data lands in storage built for industrial time series, giving fast point lookups and quick range scans across millions of readings at full resolution.
Automatic rollups
Hourly and daily aggregates are computed continuously, so historical trends come back instantly without scanning raw data.
Long-horizon cold archive
Older data rolls into a cost-efficient cold archive that keeps your history queryable for the long term, not only the recent past.
One query across all history
Ask for any asset, variable, and time range in one query. Fleetera picks the right storage automatically and returns recent and long-term data as one result.
CSV and JSON export
Pull any query window out as CSV or JSON to feed reporting, notebooks, or downstream systems.
Retention
Hot and cold, queried as one.
Recent data stays at full resolution for live work; older data rolls into hourly and daily aggregates. Retention is a query window, not a delete: queries beyond the window narrow gracefully to the resolution you have, rather than erroring.
Talk to us about retentionKeep exploring
Get your first site online.
Stand up the runtime, point it at your equipment, and watch modeled telemetry land in the cloud.