
GITNUXSOFTWARE REVIEW
Transportation & LogisticsTop 9 Best Rail Planning Software of 2026
Compare rail planning software options for scheduling, demand modeling, and network design, including tools like PTV Visum, for rail teams.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy
Viriato is the best overall pick for planning teams that need validated timetable graph outputs because its constraint-driven path validation catches inconsistencies before downstream handoffs, while PTV Visum is a strong alternative for scenario-heavy capacity and routing studies thanks to repeatable graph-based modeling with batch-run scripting.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Viriato
Constraint-driven validation during train path construction that checks consistency before downstream planning handoffs.
Best for: Fits when planning teams need validated timetable graph outputs with consistent constraints across multiple handoff steps.
PTV Visum
Editor pickStudy scripting that batch-runs large model parameter sets for repeatable scenario comparison and regression-style checks.
Best for: Fits when planning teams need repeatable, graph-based capacity and routing studies across many scenarios.
HASTUS
Editor pickIntegrated timetable-driven planning that revalidates feasibility across resources for crew and rolling stock after edits.
Best for: Fits when rail operators need tightly linked scheduling, resources, and constraints with controlled propagation.
Comparison Table
Viriato
vertical specialistModular timetabling tool for strategic and annual railway schedule planning with over 60 active customers worldwide.
Constraint-driven validation during train path construction that checks consistency before downstream planning handoffs.
Viriato supports rail network modeling and timetable planning by centering workflows on train path construction and constraint checking.
The tool emphasizes operational rule configuration so minimum running times and dwell-related restrictions can be enforced during schedule creation.
Rail operators and planners use it to reduce schedule inconsistency across planning roles by reusing modeled network and timetable data across steps.
- +Strong train path validation against operational constraints
- +Configurable rule handling for running and stopping behavior
- +Works well for end-to-end schedule creation and consistency checks
- +Supports integration of network and timetable data for planning handoffs
- –Planning configuration needs careful governance to avoid rule drift
- –Less suited to ad hoc scenario exploration without model discipline
- –Workflow depth can require domain tuning for each rollout
- –Integration breadth depends on the chosen data exchange approach
Rail network planners
Construct train paths with constraint checks
Constraint-checked schedules
Timetable coordinators
Enforce minimum running and dwell restrictions
More consistent timetables
Show 1 more scenario
Rail operators and schedulers
Reuse network and timetable data
Shared planning data
Reuse modeled network and timetable data across planning roles to reduce inconsistencies between steps.
Best for: Fits when planning teams need validated timetable graph outputs with consistent constraints across multiple handoff steps.
PTV Visum
enterprisePTV Visum models multimodal transport demand, public transport networks, and rail scenarios.
Study scripting that batch-runs large model parameter sets for repeatable scenario comparison and regression-style checks.
PTV Visum is used to build and test rail network models for capacity, routing, and timetable-related analyses. The workflow centers on graph-based infrastructure representation, demand and movement assignment, and scenario comparison across operating assumptions.
Model setup supports automation via scripting and repeatable study configurations, which helps when the same network must be evaluated under many constraints. Integration is typically handled through PTV ecosystems and data import export for interchange between infrastructure, timetable planning inputs, and downstream evaluation datasets.
- +Graph-based network modeling supports detailed routing and capacity checks
- +Scenario management enables repeatable comparisons across operating assumptions
- +Automation via study scripting reduces manual rebuilds for large experiments
- +Interfaces with other PTV planning workflows to move analysis toward operations
- –Building and maintaining large network models requires specialist data setup
- –UI workflows can feel dense when studies include many interacting parameters
- –Automation is strong, but deep API-driven provisioning needs partner alignment
- –Change governance for shared models can be hard without disciplined study versioning
Rail planners and agencies
Test service concepts network-wide
Network-level comparisons
Traffic engineers
Model detours and work zone phasing
Traffic effect inputs
Show 2 more scenarios
Transport modelers
Run repeatable infrastructure scenarios
Comparable flow forecasts
Create comparable planning scenarios for roads and network changes and produce forecasts of flows and travel times.
Policy analysts
Calibrate and test policy alternatives
Consistent iteration outcomes
Run calibration loops and policy alternatives using controlled network and demand assumptions for consistent outcome comparisons.
Best for: Fits when planning teams need repeatable, graph-based capacity and routing studies across many scenarios.
HASTUS
enterpriseHASTUS provides public transport scheduling, crew management, and rail planning capabilities.
Integrated timetable-driven planning that revalidates feasibility across resources for crew and rolling stock after edits.
HASTUS is a rail planning system used for timetable planning, train path construction, and downstream schedule tasks across rail operations. Its workflow ties vehicle assignment and crew rostering to a shared schedule base so changes propagate consistently. Giro.ca also supports configuration of operator policies, including connection constraints, dwell time rules, and engineering work windows that feed feasibility checks and conflict detection.
The system is designed to keep operational rule handling close to the schedule build, so planners can test whether a proposed timetable remains workable under configured constraints. A key tradeoff is that tightly linked planning steps can raise the cost of keeping large rule sets and assumptions up to date across many scenarios. It fits best when schedule changes must stay consistent across train paths, vehicle plans, and crew diagrams.
Use it for iterative operational planning where routing decisions and timing rules must remain aligned, not for disconnected analytics. Another tradeoff is that planning complexity increases when many constraint types, such as dwell and work-window effects, must be modeled together. It is a strong fit for organizations running frequent timetable revisions that must produce consistent operational artifacts for multiple planning roles.
- +Strong end-to-end timetable to crew and rolling stock workflow coupling
- +Detailed conflict detection tied to operational rules and constraints
- +Configuration supports engineering work windows and operational feasibility checks
- +Works well for scenario comparison focused on operational impact
- –Automation depth can require specialist configuration for complex rule sets
- –Integration breadth depends on available interfaces for signaling or real-time data
Railway timetable planners
Build timetable-linked operational assignments
Rule-checked operational plan
Transit service planners
Compare baseline and proposed timetables
Clear service change impact
Show 2 more scenarios
Transit roster planners
Create crew duties under constraints
Aligned duties and assignments
Crew duties are planned and revised and then linked to service patterns with applicable constraints enforced.
School transportation planners
Plan routes with timed stop sequences
Repeatable route manifests
School routing plans include stop sequences, timed trips, and driver assignments constrained by routing rules.
Best for: Fits when rail operators need tightly linked scheduling, resources, and constraints with controlled propagation.
SISCOG ONTIME
vertical specialistSISCOG ONTIME supports railway timetable planning, rolling stock allocation, and crew scheduling.
Rule-driven constraint checking that ties feasibility feedback directly to generated train movements during timetable iterations.
SISCOG ONTIME is built around planning workflows that generate train movements from an infrastructure description and then validate them against operational constraints. It supports timetable graph style reasoning through track and routing logic and then flags inconsistencies tied to feasibility and ordering. Scenario comparison is practical when the planning team needs to compare candidate schedules under the same constraint set and then decide which paths to carry forward.
- +Constraint-driven schedule validation reduces feasibility surprises late in planning
- +Scenario comparison supports structured iteration between timetable alternatives
- +Generates train path proposals from infrastructure routing inputs
- +Configurable operational rules fit multiple timetable planning conventions
- –Advanced results require disciplined upstream data completeness
- –Complex projects can increase configuration effort and planning operator training time
- –Integration depth depends heavily on how external formats map into planning inputs
- –Iterative tuning can slow teams when rules must be revised often
Timetable planning teams
Iterate schedules under hard constraints
Faster convergence on feasible timetables
Capacity analysts
Test capacity impacts of changes
Clearer capacity utilization decisions
Show 2 more scenarios
Operations planning coordinators
Plan engineering work windows
Fewer downstream operational conflicts
Apply work window constraints and validate adjusted movements for ordering and operational feasibility.
Rail data and integration teams
Maintain automated planning data feeds
Reduced manual data rework
Use integration and exchange to keep infrastructure and planning inputs current across iterations.
Best for: Fits when planning teams need repeatable rule checks and scenario comparisons for timetable iterations.
TRACS-RS
vertical specialistTRACS-RS supports railway timetable planning, infrastructure capacity analysis, and operational studies.
Scenario comparison and constraint-driven path checks work together to keep alternatives auditable through iterative timetable planning.
TRACS-RS fits teams running structured timetable planning where every change must trace back to operational constraints and resulting movement patterns. The workflow supports conflict detection for running and stopping behavior and helps teams enforce minimum running times and dwell time rules during train path construction. Scenario comparison is used to evaluate alternatives and reduce rework when operational assumptions shift mid-cycle. Documented planning outputs are intended to align with infrastructure manager workflows so teams can hand off validated plans to downstream processes.
- +Constraint-driven train path construction reduces manual conflict hunting
- +Scenario comparison supports structured iteration across planning alternatives
- +Conflict detection flags rule breaches during planning rather than after export
- +Planning workflow aligns with infrastructure handoffs
- –Advanced rule enforcement requires careful configuration of reference data
- –Less effective when infrastructure inputs arrive late or incomplete
- –Scenario iteration can slow down when planners modify many upstream assumptions
- –Integration depends on agreed exchange formats and operational data mapping
Timetable planning analysts
Validate alternative train path options
Fewer late-stage plan changes
Infrastructure manager workflow teams
Produce handoff-ready operational plans
Faster downstream validation
Show 2 more scenarios
Control and operations planners
Test operational rules under scenarios
Lower disruption planning effort
Update assumptions and rerun planning iterations to test rule effects on movement patterns.
Network capacity analysts
Stress-test feasibility of schedules
Clear bottleneck identification
Compare scenarios to identify where operational rules block feasible train paths.
Best for: Fits when rail planning teams need constraint-checked timetable artifacts and repeatable scenario comparisons under governance.
Signature Rail TrainPlan
vertical specialistBespoke rail scheduling software for timetable creation, fleet management, and crew resource planning.
Scenario comparison that highlights feasibility differences between timetable plan versions during constraint validation.
Signature Rail TrainPlan is built around timetable graph style planning and train path construction with constraint checks during plan build, which reduces late-stage rework. Scenario comparison helps teams iterate plan versions and measure the impact of changes across multiple runs. Capacity checks and occupation-aware planning support platform-related feasibility analysis and conflict detection during planning.
- +Constraint-driven train path construction with built-in conflict detection
- +Scenario comparison supports controlled iteration across timetable plan versions
- +Occupation-aware planning supports platform feasibility checks
- +Rail-specific configuration helps enforce timing and operational rules
- –High-quality input infrastructure data is required for accurate feasibility checks
- –Advanced rule modeling takes more configuration than basic timetable planners
- –Integration work can be heavier when existing workflows use different exchange formats
- –Complex plan views require training to navigate large timetable graphs
Timetable planning teams
Iterate daily plans with constraints
Faster plan convergence
Capacity analysis staff
Test platform occupation limits
Reduced operational conflicts
Show 1 more scenario
Infrastructure engineering planners
Assess timing impacts of work windows
Clear impact assessment
Rebuild paths under updated timing rules and compare resulting feasibility.
Best for: Fits when planning teams need constraint checks and repeatable scenario revisions for timetable feasibility.
ROMAN
enterpriseWorldline's timetable planning and path allocation system supporting long-term to short-term scheduling with conflict detection.
Infrastructure-centric constraint validation during train path construction, with results structured to support planning checkpoints.
ROMAN from Worldline centers on rail timetable planning with path-building and capacity checking in infrastructure-focused workflows.
- +Train path construction and validation under timetable constraints
- +Constraint checks tied to infrastructure occupation logic
- +Planning workflows aligned to operator and infrastructure checkpoints
- +Scenario testing support for iterative timetable changes
- –Workflow setup requires disciplined configuration of constraints
- –Limited visibility into deep dispatching simulation versus specialized tools
- –Integration into existing enterprise systems can require dedicated engineering
- –Data preparation effort can be high for complex network topologies
Infrastructure-oriented planners
Build train paths with capacity validation
Validated train paths
Operations and station planners
Model station and signaling occupation logic
Occupation-aware plans
Show 1 more scenario
Operator workflow teams
Checkpoint outputs for operations processes
Workflow-aligned checkpoints
Map planning outputs into operator and infrastructure-manager style workflow checkpoints to support handoffs.
Best for: Fits when rail operators need timetable planning with validated train paths and network occupation constraints under shared workflows.
OSRD
API-firstOpen source web application for railway infrastructure design, capacity analysis, and timetabling.
OSRD computes train running using a constraint-aware simulation engine that ties infrastructure rules to timetable feasibility reports.
OSRD is a rail planning and train path construction tool that centers constraint-based simulation with a track and signal aware routing engine. It generates and compares train runs using a structured infrastructure model and selectable operating rules, then reports measurable timing outcomes like travel time, headway impact, and conflict points.
- +Constraint-driven train run simulation that outputs timing and conflict evidence
- +Scenario comparisons for capacity and timetable tradeoffs on the same infrastructure model
- +API-centric workflow support for repeatable planning runs and integrations
- +Detailed handling of signaling and speed limits in computed paths
- –Infrastructure data modeling and validation require strong domain governance discipline
- –Limited coverage for operational tasks like live dispatching and real-time replanning
Infrastructure manager planners
Run constraint-based capacity checks
Conflict-aware capacity results
Timetable scenario teams
Compare timetable scenario train runs
Measurable scenario differences
Show 1 more scenario
Planning automation engineers
Repeat planning runs via API workflows
Automated repeatable runs
Execute repeatable rail planning runs with an API-driven workflow model for operator and infrastructure-manager contexts.
Best for: Fits when planning teams need repeatable, constraint-based train path construction with scenario comparison and API automation.
TPS.plan
enterpriseSiemens Mobility's timetable creation software for conflict-free schedule planning across strategic and operational horizons.
Constraint-driven timetable construction that preserves running-time and dwell-time rules across train diagram iterations.
TPS.plan from Siemens mobility targets rail planning workflows that connect constrained timetable planning inputs to publishable train path outputs.
- +Strong constraint handling for minimum running times and dwell time rules
- +Supports scenario comparison for capacity utilization analysis across alternatives
- +Workflow depth aligned to infrastructure manager planning and engineering processes
- +Integration focus for signaling-related planning handoffs
- –Configuration discipline is required to keep rules consistent across plans
- –User workflows can feel engineering-heavy for non-planning roles
Infrastructure planners
Derive train paths from rule constraints
Feasible train paths
Capacity analysts
Run platform occupation what-if studies
Headway and occupation impact
Show 1 more scenario
Signaling integration teams
Reduce rework between planning stages
Lower integration rework
Use integration steps aligned to infrastructure manager and signaling system workflows to limit inconsistencies.
Best for: Fits when rail planning teams need engineering-grade constraints and scenario iteration tied to infrastructure manager workflows.
Conclusion
After evaluating 9 rail planning software, Viriato stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Frequently Asked Questions About Rail Planning Software
How does SISCOG ONTIME turn an infrastructure model into scheduled train movements during timetable planning?
When do TRACS-RS scenario comparisons become auditable for iterative timetable planning?
How does Signature Rail TrainPlan prevent late-stage conflicts between platform use and other timetable constraints?
What tradeoff appears when HASTUS propagates changes across rolling stock assignment, crew rostering, and crew diagramming?
Which tool handles graph-based infrastructure modeling and batch study scripting for repeatable capacity and routing scenarios?
Where does ROMAN focus constraint validation during train path construction compared with infrastructure-manager style checkpoints?
How does TPS.plan keep running-time and dwell-time rules consistent across train diagram iterations?
What breaks if the planning workflow needs automation through an API instead of file-based exchange?
How do Siemens TPS.plan and OSRD differ when signaling system integration affects timetable feasibility?
How does Viriato reduce integration work between planning roles without relying on manual exports?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
How to Choose the Right Rail Planning Software
We separate rail planning software by how well it turns rail data into usable plan outputs and then keeps those outputs consistent when you change assumptions. Look hardest at the combination of data model integration, automation and API surface, and admin and governance controls, because that determines whether planning stays repeatable or becomes manual work.
Plan change traceability
Why it matters
Plan change traceability matters because rail planning decisions get revised often, and teams need to see what changed and why. If you cannot trace edits across versions, you will struggle to trust the plan output.
How to check
During a demo, ask to revise one assumption (e.g., a constraint or parameter) and then show how the software records the specific differences in the resulting plan artifacts. Export or screenshot a version history view and confirm you can identify the author, timestamp, and changed settings.
Rail data import compatibility
Why it matters
Rail data import compatibility matters because most teams start from existing network and timetable-related sources, not from scratch. When imports map cleanly, planning time shifts from cleanup to actual scenario work.
How to check
Request an example import of a small rail infrastructure dataset and confirm the tool flags mapping gaps in plain terms. Ask whether the software accepts your typical file formats and whether it supports import validation checks before you run a plan.
API and automation surface
Why it matters
API and automation surface matters because repeat planning runs are where throughput and consistency pay off. If you cannot script or trigger workflows, every update becomes a manual operation.
How to check
Ask for an endpoint list or an automation demo that creates a plan run, sets inputs, and retrieves results. Try a sample request or an export call in the demo environment, and confirm you can run the same job twice with different parameters.
Results visualization for planners
Why it matters
Results visualization for planners matters because rail planning output is complex, and users need to inspect outputs quickly to validate feasibility. If the tool only produces files, planners lose the fast feedback loop.
How to check
Ask to view the same plan in at least two formats (e.g., interactive views and an export). Confirm you can filter by the planning elements that matter to your workflow and that you can highlight where constraints or assumptions affected the outcome.
Scenario configuration controls
Why it matters
Scenario configuration controls matter because rail planning is comparison-heavy, and you need clean, reusable configurations. Good controls reduce accidental mix-ups and help teams rerun prior baselines safely.
How to check
In the demo, set up a baseline scenario and then duplicate it while changing a single parameter. Verify the software keeps a clear record of which inputs differ and prevents saving results under ambiguous scenario names.
Admin and audit governance controls
Why it matters
Admin and audit governance controls matter because planning work often touches multiple teams and requires accountability. RBAC and audit logs help you manage access and review changes without chasing spreadsheets.
How to check
Ask how roles are assigned for planners vs viewers, and whether access can be limited by project or workspace. Confirm the audit log captures planning runs and edits, and request an example export of an audit trail for a scenario change.
Red flags
- Edits and plan outputs are hard to trace back to inputs and authors.
- Imports succeed but silently map wrong fields without validation.
- Admin controls and audit logs are missing or do not cover plan runs.
Fit by situation
- If we regularly rerun plans after changing assumptions, prioritize Plan change traceability.
- If our team spends time cleaning files before planning, prioritize Rail data import compatibility.
- If multiple roles collaborate and we must prove who changed what, prioritize Admin and audit governance controls.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Transportation & Logistics alternatives
See side-by-side comparisons of transportation & logistics tools and pick the right one for your stack.
Compare transportation & logistics tools→