RLX-SP — Operator runtime
The runtime is a browser tab.
Spectrum is what operators actually use. Nexus serves it as a web page, so there is nothing to install, patch or license on the machines that run it — any machine on the plant network can open it.
Specifications
Pre-release. Describes Spectrum as built.
| Client | Value |
|---|---|
| Install | None. It is a web page |
| Requirement | A browser and a route to Nexus |
| Reach | 8080 HTTP, 8443 HTTPS |
| Per-seat licensing | None |
| Phone / tablet | Any browser with a route to Nexus |
| Native mobile apps | Planned — not yet available |
| Data | Value |
|---|---|
| Transport | WebSocket, pushed from the tag engine |
| Screens | Published from Studio |
| Navigation | Authored views, like any other screen |
| Docks | Written once, shared by every page |
How it works
Nothing to deploy
The operator machine needs a browser and a route to Nexus. There is no client to install, no version to keep in step with the server, and nothing per-seat to roll out.
A machine that can reach Nexus can run the HMI — the panel PC, the laptop in the office, the tablet someone is holding out in the plant.
Fed by Nexus
Values arrive over the same WebSocket the configuration console uses, so a screen reflects what the tag engine actually has, rather than polling on its own schedule and drifting away from it.
Screens come from Studio
Operators see what an engineer published. Screens, alarm configuration and reports are all authored in Studio and pushed to Nexus, so the runtime has no separate configuration of its own to drift out of step.
The plant HMI and the phone are the same runtime
A screen is authored at whatever size it needs to be, so a phone-sized view can be built alongside the 1920×1080 plant screen and served from the same Nexus. Both are ordinary Spectrum views; there is no second product to buy or configure.
Because it is a web page, an operator opens it on a phone or a tablet the same way they open it on a panel — a browser and a route to Nexus is the whole requirement.
Native iOS and Android clients are planned, taking the role Lens plays on a panel PC. They are not available yet, and the browser is the mobile story until they are.
What the operator sees
