When planning a deployment for Factry Historian, companies face different architectural choices depending on business needs, IT strategy, and operational requirements. This article outlines a couple of common architectures Factry has encountered in the field, along with their benefits, challenges, and use cases.

System Architecture

Deployment 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

On-premise local historian

Concepts

Introduction

Central Historian (Hub-and-Spoke) deployment

Multi tier historian deployment

Central broker 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