# Historian integration — Introduction

Source: https://cumulocity.com/docs/historian-integration/historian-integration-introduction/
Sector: Device management & connectivity
Release: Latest

A process historian is a time-series database that collects and stores operational data from industrial systems such as programmable logic controllers (PLCs), supervisory control and data acquisition (SCADA) systems, and distributed control systems (DCS). Historians often hold years of high-frequency process data, but this data typically stays on the plant floor and is not available to IoT and analytics applications.

With Cumulocity, you can integrate data from your existing historians into the platform. Cumulocity represents the integrated historian tags as assets and measurements, so you can use them in dashboards, alarms, streaming analytics, machine learning, and downstream IT systems without changing your existing operational technology (OT) infrastructure.

Two integration methods are available:

* **OPC UA device gateway**: Connects to any historian that provides an OPC UA server interface. You add the historian to the gateway as a regular OPC UA server and map its data with device protocol definitions. See [Integration via the OPC UA device gateway](https://cumulocity.com/docs/historian-integration/integration-methods/#opcua-device-gateway).
* **AVEVA PI connector**: A dedicated connector for AVEVA PI System (formerly OSIsoft PI System). It reads tag data through the PI Web API and sends it to Cumulocity via thin-edge.io. See [Integration via the AVEVA PI connector](https://cumulocity.com/docs/historian-integration/integration-methods/#aveva-pi-connector).

### Architecture {#historian-integration-architecture}

Both integration methods connect to Cumulocity through thin-edge.io. The OPC UA device gateway and the AVEVA PI connector run as containers managed by thin-edge.io, which sends their data to Cumulocity as devices, measurements, events, and alarms.
Because thin-edge.io manages the containers, you can operate both components remotely from the Device Management application:
* Deploy and upgrade them via [Software Management](https://thin-edge.github.io/thin-edge.io/operate/c8y/software-management/).
* Change their [configuration](https://thin-edge.github.io/thin-edge.io/operate/c8y/configuration-management/).
* Retrieve their [log files](https://thin-edge.github.io/thin-edge.io/operate/c8y/log-management/).
* Monitor their [health status](https://thin-edge.github.io/thin-edge.io/operate/c8y/health-monitoring/) as services of the device.


![Historian integration architecture: both integration methods reach Cumulocity through thin-edge.io](https://cumulocity.com/docs/images/historian-integration/historian-integration-architecture.svg)


> **Info:**
> Both integration methods run in your environment, next to the historian. Only outbound connections from your network to the Cumulocity platform are required.
