Separately they are products. Together they are most of an Interlocking.
The reference architecture, the division of responsibility, and the route from a station schematic to an approved installation.
NEAT / SYSTEM / END TO ENDHero image: a composite showing the design office screen, the equipment rack and the field element, connected as one chain. Or an isometric illustration of the same.
The reference architecture.
One diagram, five components, and no ambiguity about which is whose.
NEAT / SIGNALLING SYSTEM / REFERENCE ARCHITECTUREDiagram: GeminiX as the vital computer, GRIO at the field interface, PVS or RaSTA as the safe protocol, the RBC Generic Product or GRAIL-generated Interlocking logic as two alternative applications on the same platform, not linked to each other, and the Suite for data preparation and testing. Colour-code NEAT, customer and third-party elements.
Who supplies what.
The boundary is drawn explicitly.
NEAT supplies
The certified computing platform, the remote I/O platform, the protocol libraries, the tools, and the evidence package that goes with each.
The customer supplies
The Generic Application and its backplane, the signalling rules, the site data, the safety case, site acceptance and approval.
Third parties supply
Field elements, cabling and installation, and in some projects the operational control system above the interlocking.
From schematic to approved installation.
Each step produces an artefact the next step consumes. That is the whole argument.
- 1. The station is drawn in TrackPlanner CAD, with topological constraints preventing the classes of error that a general-purpose CAD allows
- 2. LibraryManager CAD has already encoded the national and operator signalling rules, so the objects and their properties are the customer’s own standard
- 3. Paths and routes are identified automatically, feeding the Table of Controls
- 4. GRAIL compiles the interlocking rules against that topology into C code for nodes A and B, plus the field wiring map, the VDU numbering and the viewer message layout
- 5. The application runs on GMX-CS_2026A or on your own GeminiX-based hardware, with GRIO at the field interface over PVS or RaSTA
- 6. SmartViewer consumes the same files for verification, so the test bench shows the layout the engineers designed rather than one rebuilt for the occasion
- 7. Terminal Operator presents the same object library to the operator in service
Effort and timeline against a conventional approach belong on this page only if the evidence exists. Until a project has been measured, the page says so.
Maturity, without the marketing.
- In service: GeminiX-OS and GRIO-SW certified, GRIO 1.0 certified, tramway Interlockings running since 2012, KAVACH in production
- In certification: GMX-CS_2026A, GRIO 2.0
- Under development: GRAIL, whose reference manual is at its first issue
- On the roadmap: T3 tool qualification for the Railway Tools