Deployment scenarios · A pilot or one plant
Everything on one server.
The hub and its built-in SYSTEM gateway run on one machine on the plant network. It is the quickest way to start, and for a plant whose machines share one network it can be all you need.
- Where
- One server at L3, on the machines’ network
- Install
- Docker Compose on Linux, Windows or macOS
- Fits
- A pilot, a demo, one plant on one network
The layout
Where everything sits.
- Proxus
- Your systems
- Reads machines
- Values, buffered by the sender
What you install
- The hub
- The web interface, the namespace, the historian, alarms, dashboards and reports.
- The SYSTEM gateway
- Reads the machines on the server’s network, runs rules and functions, and serves the MQTT broker.
- How
- The installer sets up the whole stack with one command. A package for servers without internet access is available too.
How it connects
- Users
- The web interface over HTTPS on port 8443. Nothing is installed on their computers.
- Machines
- Read in their own protocols across the plant network.
- MQTT devices
- Publish to the server on 1883, or 8883 with TLS.
- Your systems
- Proxus delivers to them; none of them needs to reach into the plant.
When something fails
- The server stops
- Collection, history and screens stop until it is back. Every service restarts on its own after a crash.
- The machines
- Keep running: their control does not depend on Proxus.
The limits
- One machine
- There is no standby server. For a hub that survives a server failure, see High availability.
- Other networks
- Machines on another network or at another site need an Edge Gateway near them: see Hub and edge gateways.
- Capacity
- Set by the licence, as a data rate per gateway. The disk the historian needs grows with that rate and with how long you keep the data.
Other layouts
Layouts combine. These are the other six.
- Hub and edge gateways Edge Gateways next to the machines, one hub for the plant.
- Hub in the DMZ or the cloud The hub where IT wants it; gateways on the control network connect out to it.
- Many sites, one hub Gateways at every plant, one central hub with one namespace for the group.
- High availability On Kubernetes: two hubs, a three-node message cluster, replicated databases.
- Air-gapped Installed from a package, licensed offline, no path to the internet.
- Siemens Industrial Edge Installed from Industrial Edge Management, running on one Industrial Edge Device.
Next step
Place it on your own plant.
Bring a sketch of your networks and the machines you want to connect. An engineer places the hub and the gateways on it with you, 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.