Deployment scenarios · Siemens Industrial Edge sites
Proxus as an app on Siemens Industrial Edge.
On sites that run Siemens Industrial Edge, Proxus installs from Industrial Edge Management like any other app. The whole platform runs on one Industrial Edge Device, behind the device’s own address and certificate.
- Where
- An Industrial Edge Device next to the machines
- Install
- The app package, imported into Industrial Edge Management
- Fits
- Plants standardised on Siemens Industrial Edge
The layout
Where everything sits.
- Proxus
- Your systems
- Reads machines
- Values, buffered by the sender
- Installs and updates
What you install
- The app
- One package per device architecture, x86-64 or arm64, with the hub, the SYSTEM gateway, the message server, the configuration database and the historian.
- Memory
- The services reserve about 1.5 GB together and may use up to about 11 GB, most of it for the historian.
- Backups
- The device’s own backup keeps the configuration and the database.
How it connects
- Users
- Open Proxus under the device’s address, with the device’s certificate.
- Machines
- Read in their own protocols from the device’s network.
- Your systems
- Proxus delivers to them from the device.
When something fails
- A service stops
- It restarts on its own.
- The device stops
- Collection, history and screens stop until it is back; the machines keep running.
The limits
- One device
- Hub and gateway share the device; there is no standby.
- Memory
- Choose a device with room for the historian at your data rate.
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.
- 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.
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.