Connect DeltaV Continuous Historian to Copilot
You're building a Copilot agent that should answer questions about process conditions — and the data lives in DeltaV Continuous Historian, running deep inside an Emerson DeltaV DCS on a closed OT network. Unlike an IT-connected historian, DeltaV Continuous Historian was designed for DCS-internal access using OPC and Emerson-proprietary protocols. Getting a Copilot agent to query live process data from there requires solving problems that Copilot Studio documentation doesn't address.
The barriers below are what makes this integration harder than it looks.
Why it's hard
Seven reasons connecting a Copilot agent to DeltaV Continuous Historian is harder than expected.
Copilot agents call HTTP — DeltaV Continuous Historian speaks OPC, not REST
Copilot Studio agents retrieve data through Custom Connectors making HTTP calls. DeltaV Continuous Historian does not expose a REST API. Data access goes through OPC DA and OPC HDA, or through Emerson's proprietary interfaces — all of which require OPC clients running on the OT network. Reaching that data from a Copilot agent requires an intermediary that bridges OPC to an HTTP endpoint accessible from Microsoft's cloud.
DeltaV systems sit on closed OT networks — Microsoft's cloud can't reach them
DeltaV DCS networks are typically air-gapped or separated from IT and the internet by strict firewall policy. Microsoft's Power Platform makes outbound HTTP calls from cloud infrastructure — it has no path to a DeltaV node on a production OT network. Creating that path would require opening inbound network access to DCS infrastructure, which Emerson and most OT security frameworks explicitly advise against.
OPC bridge required — OPC Classic uses DCOM, which doesn't cross networks cleanly
OPC Classic (DA and HDA) relies on Microsoft DCOM, which requires Windows domain trust relationships and specific port configurations to work across network boundaries. Even getting an OPC client to talk reliably to DeltaV Continuous Historian from a machine on a different subnet is a non-trivial IT and OT coordination exercise before any Copilot integration work can begin.
DeltaV tag addressing uses module:parameter notation — opaque to an agent
DeltaV tags follow Emerson's module:parameter convention — identifiers like FIC-101/PV.CV or TIC-204/SP.CV. These are meaningful inside the DCS but opaque when presented directly to an AI agent or end user. Without a mapping layer that translates DeltaV module:parameter paths into human-readable descriptions, the agent can't surface query results in a way that a process engineer or operator can interpret.
Raw historian time-series overflows Copilot action response limits
DeltaV Continuous Historian logs at high resolution. A history query for a process variable over even a short time window returns thousands of timestamped records. Action responses in Copilot Studio have payload size limits — a raw historian dump will exceed them. The endpoint serving the agent must aggregate data before responding, which requires logic the historian's OPC interface doesn't provide natively.
DeltaV Continuous Historian is tightly integrated with DCS — access is restricted
The DeltaV Continuous Historian runs as part of the DCS infrastructure. Access to historian data is controlled by Emerson's security model — connecting external systems requires DeltaV administrator involvement and often a change management process. This is not a self-service integration and typically involves the control system vendor and the site's DCS support team.
Power Platform Custom Connectors require admin approval
Any Copilot Studio agent accessing external data needs a Custom Connector with an approved OpenAPI spec. In enterprise Microsoft 365 environments, connectors that touch OT-adjacent endpoints go through Power Platform admin review, security assessment, and sometimes change management. The approval timeline regularly runs to weeks before a connector reaches production use.
What teams usually try
OPC-to-REST bridge on the OT network
Build a service on a DeltaV-accessible machine that reads historian data via OPC HDA and exposes a REST API. Define a Custom Connector against this endpoint. The service handles OPC DCOM connections and response aggregation.
The catch: The service runs inside the OT network and requires an outbound path to Microsoft's cloud — a security change on DCS infrastructure. OPC DCOM configuration is fragile across network boundaries. DeltaV administrator approval is required for any new OPC connection. Maintaining the bridge adds ongoing infrastructure burden.
Emerson DeltaV Cloud Connect or third-party historian bridge
Use Emerson's own cloud connectivity product or a third-party industrial data bridge to replicate DeltaV historian data to a cloud database. Point the Custom Connector at the cloud endpoint.
The catch: Adds a vendor license and cloud replication pipeline on top of the Copilot integration. Replication introduces latency — the agent answers about replicated history, not live process values. Data residency and replication configuration may add compliance scope depending on the plant and process.
DeltaV Operate export to SharePoint
Export historian trend data from DeltaV Operate as CSV files and upload to SharePoint. Configure the Copilot agent to read these files as its knowledge source for process questions.
The catch: The agent answers questions about the last export — not current process state. Manual export steps add operational burden. High-resolution historian data produces large files that SharePoint-based agent search handles poorly for time-range queries.
How TrendOps solves it
TrendOps Edge connects to DeltaV Continuous Historian on the OT network — reading via OPC, translating module:parameter addresses into human-readable context, and aggregating high-resolution history — then forwards structured data to TrendOps Platform in the cloud over a single outbound MQTT connection. Your Copilot Studio agent calls TrendOps Web API through a single Custom Connector. No OPC from Microsoft's cloud, no inbound path to DCS infrastructure, no raw historian dumps overflowing action payloads.
The agent calls TrendOps Web API — a cloud-accessible HTTPS endpoint. No OPC client, no DCOM configuration, no inbound path to DeltaV infrastructure from Microsoft's Power Platform.
TrendOps maps DeltaV module:parameter identifiers to human-readable tag descriptions. Action responses include context the agent can use to answer questions — not raw DCS addressing that means nothing outside the control room.
TrendOps handles historian aggregation server-side. Action responses return interval summaries — not thousands of high-resolution raw records that overflow Copilot Studio payload limits.
TrendOps Edge reads DeltaV continuously. The agent returns current process values — not a snapshot from an export or a replication pipeline with built-in latency.
TrendOps Edge pushes data out over a single outbound MQTT connection. No inbound path from Microsoft's cloud to DeltaV infrastructure. The Copilot agent's calls never reach the DCS network.
TrendOps normalises DeltaV data alongside AVEVA PI, FactoryTalk, SQL, and MQTT sources. One connector gives the agent a unified view — not a separate integration per historian.
What you end up with
No OPC client or DCOM configuration on the cloud side — the agent calls a plain HTTPS endpoint.
Current process values — the agent knows what's happening right now.
DCS network stays closed — outbound MQTT only, no inbound path from Microsoft's cloud.
One connector, every OT source — not limited to DeltaV.
Don't want to build your own AI agent integration?
TrendGuru — TrendOps's built-in AI agent — already has access to your plant data. Ask questions about your DeltaV process in plain language and get answers instantly, deployed directly in Microsoft Teams. No Custom Connector to configure, no OpenAPI spec to write, no Power Platform admin approval to wait for.
Learn about TrendGuru →Your Copilot agent shouldn't need OPC access to a DCS network to answer a question about process data
TrendOps gives your Copilot agent a clean, cloud-accessible API for DeltaV Continuous Historian — translated, aggregated, and available without touching the DCS network.
Book a Demo