RailCommand Offline, Degraded, and Practice Operation
RailCommand can support cloud-backed setup, local desktop operation, offline packages, and simulated practice. The safe operator action depends on which part is unavailable.
State Meanings
| State | Operator meaning |
|---|---|
| Online | Cloud, local runtime, and required hardware are ready for the selected workflow. |
| Degraded | Some capability is impaired. Avoid movement that depends on the missing capability. |
| Offline package | A trusted local .rspkg can be opened for supported offline workflows. |
| Simulated or practice | Use for learning and rehearsal. Do not describe it as physical layout control. |
| Emergency stopped | Keep operators from issuing new movement commands until recovery is complete. |
Decide What To Do
- Identify whether the cloud, local runtime, command station, sensors, turnouts, signals, or session sync is affected.
- Decide whether the session can continue, must switch to practice-only, needs repair, or must stop.
- Tell crews which state the railroad is in.
- After recovery, verify session, hardware, throttle, route, and train state before movement.
- Run Ops Readiness again when configuration or session state changed.
Good Practice
- Do not treat simulated state as physical state.
- Do not continue live movement when authority, turnout, signal, sensor, or throttle state is uncertain.
- Keep emergency stop available during every live session.
- If the desktop app blocks an action, follow the reason shown by the app.