One data model, from the first drawing to the operator screen.
Track editing and layout definition, railway object design and management, trackside data preparation, Interlocking logic generation with GRAIL, interoperability with third-party applications, simulation environment, testing facilities and debug instruments.
NEAT / TECHNICAL ENGINEERING
THE PROCESS
The sequence.
- LibraryManager CAD creates the object library: object properties and shapes, zones, layers, rail sets, cabinet I/O mapping and the rules that identify routes
- TrackPlanner CAD loads that library at start-up and draws or imports the equipped layout, then identifies paths and routes
- Plugins export the configuration in railML and in project-specific formats
- GRAIL compiles the interlocking rules against the topology
- SmartViewer consumes the same files for verification, with no additional configuration
- Terminal Operator presents the same library to the operator in service
AUDIENCES
Who buys which part.
The suite has two distinct buyers, and treating them as one is why tool sales stall.
E
Engineering
Design offices and application engineers buy TrackPlanner CAD, LibraryManager CAD, the SDK and, increasingly, GRAIL. They are measured on hours per station and on review findings.
O
Operations
Dispatchers and traffic management buy Terminal Operator, on a different budget and a different cycle. The page for it carries its own call to action.