Draw the station once. Use it everywhere after that.
Desktop tools covering the signalling project life-cycle: modelling, visualisation, data preparation, validation and run-time interaction. The unifying argument is reuse, not features.
NEAT / TRACKPLANNER CAD / STATIONEffort spent on the layout is not spent again.
In most design offices the station is drawn for the design, rebuilt for the test bench and rebuilt again for the operator display. The suite exists to stop that.
NEAT / HORIZON / DESIGN PROCESSThe components.
TrackPlanner CAD
A purpose-built railway schematic editor. Topological constraints and automatic object connections prevent the classes of error a general-purpose CAD allows.
Explore →LibraryManager
Where the object types, symbols and attributes used by TrackPlanner CAD are defined, so the suite adapts to a new signalling practice without code changes.
Explore →SmartViewer
Simulation and test visualisation, consuming the files the design already produced.
Explore →Terminal Operator
Command and control in service, on the same object library the engineers designed with.
Explore →GRAIL
Interlocking logic compiled from rules and topology. Part of this toolchain; its page lives in Railway Software Solutions.
Explore →SDK and plugins
The TrackPlanner CAD SDK: access to all project data, so a customer can build what we have not.
Explore →Design principles.
- User-friendly and lightweight
- Modular and expandable through plug-ins
- Customisable to the customer signalling context
- Multilanguage
- Interoperable, with railML as the backbone
- OS-independent by design
And one honest qualification.
The tools are developed cross-platform in Qt, but the binaries delivered today are Windows executables, tested on Windows 10 and 11. "OS-independent by design, delivered today as Windows binaries" is the accurate form of the claim, and an evaluator who checks will find it holds.