Bring Industrial Data into Microsoft Fabric
One integration. Every team's questions answered.
Fabric has your business data. It's missing operations.
Your IT team can bring ERP, CMMS and lab data into Microsoft Fabric with standard connectors. The operational data that gives those numbers meaning lives in historians and SCADA systems across your facilities, and it doesn't come along.
Five teams, one data gap
Each question needs operational data sitting next to business data in Fabric.
Operations
"Why did deliveries fall short of nominations last week?"
Maintenance
"Which compressors and pumps should we service before they fail?"
Engineering
"Is every facility running where it should?"
Environmental
"What did we emit, and what did we capture?"
Finance
"What did each product stream actually earn us last month?"
Why the operational half is the hard half
Different questions, same four obstacles.
Locked on the OT network
Historians and control systems sit behind OT firewalls. Fabric can't reach them without gateways, client software and firewall changes.
Spread across many systems
One facility runs PI, another Wonderware, a third a SQL database or OPC UA server. Each needs its own connection and query logic.
Raw readings, not reportable numbers
A volume may be a totalizer or need calculating from a flow rate. Either way it has to be aggregated and time-aligned before it can sit next to a cost or a work order.
Tag names, not meanings
FT-301A.PV means nothing to finance or environmental. Someone has to map tags to assets and keep that mapping current.
How TrendOps closes the gap, once, for every team
TrendOps sits between your operational systems and Fabric. It collects the data, shapes it into reportable numbers and serves it through one secured Web API.
TrendOps Edge
On-premise, next to your historians, SCADA and SQL systems.
AVEVA PI, Wonderware, FactoryTalk, DeltaV, SQL, MQTT, Sparkplug B and OPC UA.
Data leaves the plant over a single outbound connection. Nothing reaches in.
TrendOps Platform
Where raw readings become numbers the business can use.
Totals, averages and time-weighted values on common time intervals, so values from different systems line up with your business data.
Unit conversions, derived values and cleanup live in one place, not in every Fabric pipeline.
Tags become named attributes, such as Facility A › Meter Station 2 › Daily Volume.
Web API to Microsoft Fabric
Fabric pulls the data in next to your ERP, CMMS and lab data.
Access follows the same identity controls as the rest of your Microsoft environment.
All five teams draw from the same model. One set of definitions, one set of numbers.
When a team needs more, add an attribute
The first report is never the last. In TrendOps, the next one is a small change.
- 1Find the tag in each source system
- 2Extend the extraction
- 3Rebuild the aggregation
- 4Update the pipeline and the model
- 5Repeat for every system and every team
- 1Add an attribute to the hierarchy and map it to a tag
- 2Set a formula if it needs one
It's available through the same API. No pipeline changes.
For your IT team
What changes in your environment, and what doesn't.
No inbound ports
Edge makes outbound MQTT connections only. No VPN and no OT firewall exceptions.
No gateway
Fabric calls a cloud API. No on-premises data gateway and no historian client software.
Microsoft Entra
The Web API is secured with Entra and managed with your existing identities.
No data gaps
Checkpointed collection and automatic backfill keep the data contiguous through outages.
Start with one team's question
Pick the question that matters most. We'll show it answered in Fabric with your own operational data. The next team gets theirs through the same integration.
Book a Demo