Factry Historian is built from a small set of components that collect, contextualize and store industrial process data. This section covers what those components are and how a deployment is shaped around them.

 covers the components and how data moves between them.

 covers the common deployment patterns, and the trade-offs of each.

Introduction

Architecture

DCOM

ItemID

ProgID

SparkplugB

HTTPS

HTTP

gRPC

sudo

Representational State Transfer Application Programming Interface

REST_API

An RRULE is a recurrence rule which defines a pattern to generate a set of timestamps to setup new events.

RRULE

UUID

VNet

LDAP

Lightweight Directory Access Protocol (LDAP) with TLS/SSL encryption

LDAPS

Entra_DS

FQDN

SCADA

TSDB

JSON

System Architecture

concepts

Concepts

On-premise local historian

Central Historian (Hub-and-Spoke) deployment

Multi tier historian deployment

Central broker deployment

Deployment Architecture

Collector state

Collector failover

Collectors

Tags & Labels

Measurements

Calculations

Asset Properties

Asset Metadata

Asset Prototypes

Assets

Events

Manual Entry Forms

Sinks

Forwarders

Sinks & Forwarders

Time-series databases

Organizations

Users and Groups

OPC-UA

OPC-DA

MQTT

REST API

Siemens S7

Protocols & Formats

Historian Portal

architecture

forwarder

mqtt

sinks

forms

prototypes

metadata

asset properties

calculations

tags & labels

measurements

assets

collectors

opcua

events