A coordination layer for systems, people, and decisions.
Railixa is conceived as an operational layer around existing TMS, maintenance, and roster systems—not a replacement for their authoritative records.
Six design principles for a calmer operational layer.
Event-linked workflow
The demo models incidents, asset events, acknowledgements, and handovers as one connected operational timeline.
Shared operational context
Product surfaces reuse the same service, location, asset, and response context instead of creating isolated records.
Traceability by design
The intended workflow keeps actions time-stamped and reviewable. Compliance requirements would still need formal validation.
Integration-ready direction
The concept is designed to sit around TMS, CMMS, rostering, and identity systems through scoped interfaces.
EU-first data direction
Data location, subprocessors, retention, and transfer safeguards would be documented before any production procurement.
Role-aware access concept
The product direction includes role, line, and depot context without claiming a production identity implementation.
Requirements to validate
These are procurement workstreams, not certifications or completed assessments.
- Rail safetyApplicability assessment
- SecurityControls and evidence
- Data protectionRoles and safeguards
- AccessibilityOperator workflows
- AvailabilityService objectives
- InteroperabilityScoped interfaces