Integration Guides

Practical guides for connecting industrial data sources to modern reporting and analytics tools.

Filter by:

Product Overview TrendOps Edge

TrendOps Edge: On-Premise Industrial Data Gateway

How TrendOps Edge collects time-series data from industrial historians and SCADA systems — gap-free, across firewalled networks — and delivers it to the TrendOps cloud platform.

Read overview →

SQL Database Power BI OT/IT Integration

Get Industrial SQL Data into Power BI

Power BI has a native SQL connector — but industrial SQL databases live on restricted networks, use shared credentials, carry schemas that need context to be meaningful, and add load to production servers when analysts query them directly. How TrendOps changes the picture.

SQL Database Excel TrendOps Link

Get Industrial SQL Data into Excel

Excel can query SQL — but industrial SQL servers are on restricted networks, credentials are shared, raw schemas need context, and every analyst refresh adds load to the production server. How TrendOps Link removes all of it from the analyst's path.

MQTT Power BI OT/IT Integration

Get MQTT Data into Power BI

Your devices already speak MQTT — but Power BI can't subscribe to a broker. The data needs somewhere to land first. Broker deployment, network traversal, payload parsing, topic routing, and persistence: why building the bridge is harder than it looks, and how TrendOps Edge handles it.

MQTT Excel TrendOps Link

Get MQTT Data into Excel

Excel has no MQTT connector — before a workbook can show device data, the messages need to land somewhere, be parsed, and be stored. Why building that infrastructure is a bigger project than it sounds, and how TrendOps Edge and TrendOps Link replace the whole stack.

AVEVA PI Power BI OT/IT Integration

Connect AVEVA PI to Power BI

Why connecting AVEVA PI to Power BI is harder than it looks — proprietary data model, no native connector, OT network isolation, and raw time-series volume — and how TrendOps solves it without the complexity.

Wonderware Power BI OT/IT Integration

Connect AVEVA Wonderware to Power BI

Why IndustrialSQL looks like a path Power BI can walk — and why it usually isn't. Retrieval modes, ODBC client dependencies, OT network isolation, and how TrendOps removes all of it from the equation.

Wonderware Excel TrendOps Link

Connect AVEVA Wonderware to Excel

AVEVA Historian ships an Excel add-in — but it comes bundled with the full desktop client stack. Why the native tool falls short for most teams, and how TrendOps Link gets Wonderware data into any Excel workbook without the client software.

FactoryTalk Historian Power BI OT/IT Integration

Connect FactoryTalk Historian to Power BI

FactoryTalk Historian runs on the same PI engine as AVEVA PI — which means all the same barriers apply. No native Power BI connector, PI AF SDK on every machine, on-premises gateway required for the Service. How TrendOps removes every layer.

FactoryTalk Historian Excel TrendOps Link

Connect FactoryTalk Historian to Excel

The native Excel path for FactoryTalk Historian is PI DataLink — but most users don't know that because the search results point the wrong way. PI DataLink per machine, AF SDK required, breaks in Excel for the Web. How TrendOps Link skips all of it.

FactoryTalk Data Logger Power BI OT/IT Integration

Connect FactoryTalk Data Logger to Power BI

Data Logger writes to SQL Express on the HMI workstation — a 10 GB cap, a two-table schema, and a direct OT connection requirement between them and Power BI. Why it's harder than it looks, and how TrendOps removes every layer.

FactoryTalk Data Logger Excel TrendOps Link

Connect FactoryTalk Data Logger to Excel

SQL Express on the HMI workstation, a two-table schema, high row counts that lock up Excel, and no path for Excel for the Web. How TrendOps Link gets Data Logger data into any workbook without touching the OT network.

DeltaV Historian Power BI OT/IT Integration

Connect DeltaV Continuous Historian to Power BI

No native Power BI connector, a closed OT network, OPC bridging required, and a gateway on top. Why the multi-layer stack between Emerson DeltaV and Power BI breaks teams — and how TrendOps collapses it to one connection.

DeltaV Historian Excel TrendOps Link

Connect DeltaV Continuous Historian to Excel

DeltaV has an Excel add-in — but it only works when you're connected to the OT network. A desktop-only COM add-in, DCS team deployment required, and no Excel for the Web support. How TrendOps Link removes the OT network requirement entirely.

AVEVA PI Copilot Studio AI Agent

Connect AVEVA PI to a Microsoft Copilot Agent

Copilot Studio agents call HTTP endpoints — not OT protocols. PI lives on the OT network; Microsoft's cloud doesn't reach it. Why the connectivity, context, and payload barriers are harder than they look, and how TrendOps gives your agent a clean API without touching the plant network.

AVEVA PI OpenAI AI Agent

Connect AVEVA PI to an OpenAI Agent

OpenAI function calls need a cloud-accessible endpoint — not a PI server on a private OT network. Raw tag names, context-window costs, and schema design all affect how well the agent performs. How TrendOps gives your OpenAI agent a clean, LLM-ready API for live plant data.

AVEVA Wonderware Copilot Studio AI Agent

Connect AVEVA Wonderware to a Microsoft Copilot Agent

Wonderware IndustrialSQL has no REST API and sits on the OT network — neither of which Copilot Studio can reach. Why the ODBC-only interface and retrieval modes make this integration harder than expected, and how TrendOps gives your agent a clean API.

AVEVA Wonderware OpenAI AI Agent

Connect AVEVA Wonderware to an OpenAI Agent

OpenAI function calls need a cloud-accessible HTTPS endpoint — Wonderware IndustrialSQL doesn't have one. ODBC-only access, OT network isolation, and raw time-series volume all compound the problem. How TrendOps solves each barrier.

FactoryTalk Historian Copilot Studio AI Agent

Connect FactoryTalk Historian to a Microsoft Copilot Agent

FactoryTalk Historian runs on the PI engine — which means the same PI AF SDK, OT network, and raw time-series barriers as AVEVA PI, now with Copilot Studio custom connector approval on top. How TrendOps removes the whole stack.

FactoryTalk Historian OpenAI AI Agent

Connect FactoryTalk Historian to an OpenAI Agent

FactoryTalk Historian uses the PI engine — which means PI AF SDK, OT isolation, and cryptic tag names block every path from OpenAI function calling. Raw historian dumps fill the context window. How TrendOps handles each barrier.

FactoryTalk Data Logger Copilot Studio AI Agent

Connect FactoryTalk Data Logger to a Microsoft Copilot Agent

Data Logger writes to SQL Express on HMI workstations — no REST API, OT isolation, a two-table schema, and a 10 GB cap. Why each barrier compounds the next, and how TrendOps turns scattered SQL Express instances into a single agent-ready API.

FactoryTalk Data Logger OpenAI AI Agent

Connect FactoryTalk Data Logger to an OpenAI Agent

OpenAI function calls need an HTTPS endpoint — Data Logger writes to SQL Express with no REST interface. HMI workstations on the OT network, a two-table schema, and high-frequency rows that fill the context window. How TrendOps solves all of it.

DeltaV Historian Copilot Studio AI Agent

Connect DeltaV Continuous Historian to a Microsoft Copilot Agent

DeltaV Continuous Historian speaks OPC on a closed DCS network — not HTTPS from Microsoft's cloud. DCOM bridging, Emerson-specific tag addressing, and DCS change management make this integration a multi-team project before it's an AI one.

DeltaV Historian OpenAI AI Agent

Connect DeltaV Continuous Historian to an OpenAI Agent

OpenAI function calls need HTTPS — DeltaV Continuous Historian speaks OPC on a closed DCS network. DCOM bridging, opaque module:parameter tag addressing, and high-resolution historian dumps that fill the context window. How TrendOps handles each.

SQL Database Copilot Studio AI Agent

Connect an Industrial SQL Database to a Microsoft Copilot Agent

SQL Server doesn't expose HTTP endpoints — and production SQL databases live on restricted networks. Shared credentials, opaque schemas, and analyst query load all compound the problem. How TrendOps gives your Copilot agent a contextualised, cloud-accessible API.

SQL Database OpenAI AI Agent

Connect an Industrial SQL Database to an OpenAI Agent

OpenAI function calls need an HTTPS endpoint — SQL Server doesn't expose one. Restricted networks, shared credentials, cryptic production schemas, and raw row dumps that fill the context window. How TrendOps solves each layer.

MQTT Copilot Studio AI Agent

Connect MQTT Data to a Microsoft Copilot Agent

MQTT is push-based pub/sub — Copilot agents pull HTTP. No REST interface, no history store, raw encoded payloads, and an OT broker you can't expose to the internet. How TrendOps bridges the protocol gap without touching the broker's network perimeter.

MQTT OpenAI AI Agent

Connect MQTT Data to an OpenAI Agent

MQTT is push-based — OpenAI function calls pull HTTPS. No query interface, no history store, raw payloads, and an OT broker that can't be internet-exposed. How TrendOps turns a real-time pub/sub stream into a queryable, LLM-ready endpoint.

AVEVA PI Excel TrendOps Link

Get AVEVA PI Data into Excel

Why PI DataLink falls short for most teams — SDK installs on every machine, broken SharePoint files, PI-only coverage — and how TrendOps Link brings historian data into any Excel workbook, on any device, without the overhead.