Overview · for Engineers, Administrators, Developers

Concepts

How Proxus is built and how its parts work together, from the edge gateway next to a machine to the historian, the namespace and automation.

The pages in this section explain Proxus rather than tell you what to click. Read them when you want to know why a screen asks for something, where a value is at a given moment, or which tool fits a job. The how-to guides link here for background.

The building blocks in one picture

A machine is read by an edge gateway. The gateway publishes every value in the Unified Namespace, sends it to the outbound targets you chose, and passes it to the hub, which keeps its history and shows it. Pipelines, rules and functions act on the values on their way.

The main parts of Proxus

Machines PLCs, CNCs, robots, meters

Edge gateway reads, buffers, publishes

Hub configuration, historian, screens

Users and systems trends, reports, alarms

Pages in this section

Architecture The hub, the edge gateways, how they talk to each other, and where data is kept. Open How data flows The path of one value: read, buffer, publish, store, route. Open Devices, profiles and tags What a device, a device profile and a tag are, with data types and quality. Open Unified Namespace The place of a device, the topic structure and the messages Proxus publishes. Open Pipelines, rules and functions Which tool to use to shape data, raise alarms or run your own code. Open

The glossary defines every term in a sentence or two.

Was this page helpful?

← Previous

Tour

Architecture

Evaluating Proxus? See it on your own machines in a 30-minute technical session.