Deployment scenarios · A group of plants
One hub for every site.
Each plant gets its own Edge Gateways; one central hub holds the model, the history and the screens for all of them. Enterprise, site, area and line are part of the namespace, so one dashboard or report can span plants.
- Where
- The hub in your data centre or private cloud, gateways at each site
- Install
- The hub once; the gateways of each site from the hub
- Fits
- Groups that want one namespace and one historian across plants
The layout
Where everything sits.
- Proxus
- Your systems
- Reads machines
- Values, buffered by the sender
What you install
- The hub
- Once, in your data centre or a private cloud, with Docker or Kubernetes.
- Each site
- One or more Edge Gateways, installed with the command the hub generates.
- The model
- Devices carry their enterprise, site, area and line, so every plant has its place in one namespace.
How it connects
- Site to hub
- Each gateway connects out over your WAN or VPN to port 7422, over TLS. Nothing at the centre connects into a site.
- Users
- Everyone signs in to the central hub; roles and namespace paths decide who sees which plant.
- Group systems
- Receive the data of every site from one place.
When something fails
- One site loses its WAN
- That site’s gateways keep collecting and buffering; the other sites are not affected.
- The central hub stops
- Every site keeps collecting and buffering. Screens and history are unavailable until the hub is back; run it with High availability if that is too long.
- A gateway stops
- Docker starts it again. Its machines are not read in the meantime; the other gateways are not affected.
The limits
- Screens during a WAN outage
- A cut-off site keeps its data, but its people see the central screens again only when the link returns. A site that needs its own screens through an outage runs its own hub, as a separate installation.
- One installation
- One hub, one licence and one configuration for the group. Hubs do not link to each other.
- A restart during a hub outage
- A running gateway rides out a hub outage. A gateway that is restarted while the hub is out of reach starts processing when the hub answers again.
- Disk on the gateway
- The buffer needs disk for its retention time at the gateway’s data rate: 48 hours by default, up to 30 days.
Other layouts
Layouts combine. These are the other six.
- Single server The hub and its built-in gateway on one machine next to the machines.
- 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.
- 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.