RailCommand Ops Readiness
Ops Readiness is the pre-session checklist for RailCommand. It checks whether the selected layout has enough data and system health to support the operating session you want to run.
When to Run It
Run Ops Readiness:
- After selecting or switching layouts.
- Before starting a live operating session.
- After importing layout, roster, JMRI, TrainController, or OperationsPro data.
- After changing hardware mappings.
- After recovering from an offline or emergency-stopped state.
What It Checks
Ops Readiness can call out missing or incomplete setup in areas such as:
- Industries and operating locations.
- Staging yards and track capacity.
- Trains, locomotives, cars, and consists.
- Routes, schedules, and timetables.
- Hardware mappings for sensors, turnouts, signals, and accessories.
- Crew assignments and role readiness.
How to Use the Report
- Read required items first.
- Use each fix link to open the web or desktop screen that owns the missing setup.
- Resolve required blockers before physical movement.
- Review recommendations if you want a richer session.
- Re-run readiness after changes.
If the report says the layout is not ready for live operation, use practice or simulated mode only when that matches the app state and your operating plan.