Platform · Deployment scenarios
Where each Proxus server goes.
Seven layouts, from one server next to the machines to a group of plants on one hub. Each has its own page: the drawing, what to install, what happens when a part fails, and the limits. Start with the one closest to your plant.
- Servers
- A hub, and Edge Gateways where the machines are
- Runs on
- Docker, Kubernetes or Siemens Industrial Edge
- Connections
- Gateways connect out; nothing connects into the control network
The parts
Every layout is built from two kinds of server.
The drawing shows the most common layout. Cut the link to see what the gateways do while the hub is out of reach.
- Proxus
- Your systems
- Reads machines
- Values, buffered by the sender
| Server | What it does | Runs on | High availability | Usually at |
|---|---|---|---|---|
| Hub | The web interface, the namespace, the historian, alarms, dashboards, and the configuration of the whole installation. | Docker Compose on Linux, Windows or macOS; Kubernetes; Siemens Industrial Edge | Yes, on Kubernetes | L3, the DMZ or central |
| Edge Gateway | Reads the machines, runs rules and functions, serves MQTT, buffers on disk and delivers to your systems. | Linux with Docker, x86-64 or ARM | Restarted on failure; one instance each | L3, next to the lines |
| SYSTEM gateway | The hub’s own gateway, for machines on the hub’s network. It comes with every installation. | Next to the hub | Restarted with the hub | With the hub |
Seven layouts
Start with the one closest to your plant.
-
A pilot or one plant
Single server
The hub and its built-in gateway on one machine next to the machines.
Open the layout -
Several lines or networks
Hub and edge gateways
Edge Gateways next to the machines, one hub for the plant.
Open the layout -
IT and OT kept apart
Hub in the DMZ or the cloud
The hub where IT wants it; gateways on the control network connect out to it.
Open the layout -
A group of plants
Many sites, one hub
Gateways at every plant, one central hub with one namespace for the group.
Open the layout -
No single server to lose
High availability
On Kubernetes: two hubs, a three-node message cluster, replicated databases.
Open the layout -
No internet at all
Air-gapped
Installed from a package, licensed offline, no path to the internet.
Open the layout -
Siemens Industrial Edge sites
Siemens Industrial Edge
Installed from Industrial Edge Management, running on one Industrial Edge Device.
Open the layout
Not sure?
Answer a few questions.
Layouts combine: an air-gapped plant can run with high availability, and a group can keep its largest plant on its own hub.
Side by side
How the layouts differ.
| Single server | Hub and edge gateways | Hub in the DMZ or the cloud | Many sites, one hub | High availability | Air-gapped | Siemens Industrial Edge | |
|---|---|---|---|---|---|---|---|
| Collection continues while the hub is out of reach | Hub and collection share one machine | Yes, on each gateway | Yes, on each gateway | Yes, at every site | Yes | Yes, on each gateway | Hub and collection share one device |
| The hub survives a server failure | No | No | No | With High availability | Yes, on the hub side | With High availability | No |
| One namespace across several sites | One plant | One plant | One plant | Yes | Possible | Possible | One plant |
| Needs Kubernetes | No | No | No | No | Yes | No | No |
| Needs internet access | No | No | No | No | No | Never | No |
Next step
Draw your plant with an engineer.
Bring a sketch of your networks and the machines you want to connect. In the first call we place the hub and the gateways on it, with the firewall rules your IT team will ask for.
-
Scoping call
Equipment, protocols, sites and the systems the data has to reach.
-
Technical walkthrough
A working demo against a scenario that resembles your plant, not a generic tour.
-
Pilot plan
A defined first line or site, with the deployment and security questions answered up front.
-
Roll-out
The same templates bring the next lines and sites online.