Mobile Engineering Access
Read-first, strongly authenticated mobile and tablet views that let on-call engineers triage from anywhere without weakening the control room's authority.
Why mobile is read-first
On-call engineers need to assess a machine at 3 a.m. from outside the control room. The mobile surface gives them the full observability picture — dashboards, alerts, the 3D twin overlay, incident timelines — but grants no hard-real-time control. Actuation authority stays with the L1 Control Plane and physically-present operators. This is a deliberate asymmetry: observability should be ubiquitous; authority should be concentrated and accountable.
What mobile can and cannot do
| Capability | On mobile? |
|---|---|
| View dashboards / KPIs | yes |
| View 3D twin overlay + confidence | yes |
| Acknowledge / triage / annotate alerts | yes |
| Replay an incident | yes |
| Request an advisory setpoint (queued for control room) | yes, with approval |
| Issue hard-real-time actuation | no |
| Override an interlock | no |
A subset of supervisory actions (acknowledging an alert, requesting a non-safety setpoint change) is permitted but always routed as a request that a control-room operator confirms, with both identities logged. Anything touching safety is unavailable off-console by design.
Design for the mobile context
Mobile views assume glare, one hand, and interruption. They lead with a single triage verdict (what is wrong, how confident, how urgent), collapse detail behind progressive disclosure, and keep tap targets large. The 3D overlay degrades gracefully to a 2D cross-section on small screens while preserving the same color grammar and confidence hatching so the mental model does not change between console and phone.
- Strong auth: device attestation plus per-session identity, short-lived
- Least privilege: read by default, request-and-confirm for the narrow write set
- Full audit: every view and action attributed and time-stamped
- Offline-safe: shows last-known state with an explicit staleness badge
Because the mobile view is downstream of the same L2 fabric and L3 twin, its numbers always agree with the control room. See alerting and triage UX for the workflow that drives most mobile sessions, and staleness indicators for how connectivity gaps are shown honestly.