RR Trace reads your EPC contract, builds the CRS, decomposes it to sub-system SRS, and assigns V&V against the applicable CENELEC and TSI clauses. Then it closes the evidence and rolls hazards up to a verdict — every result reviewable by your engineers.
HAZ-014 · roll-up
2 of 3 SRs closed
Grounded in the standards auditors expect
The Workflow
Following the rail V-cycle. Seven steps, each one reviewable by your engineers — see any of them in full below.
Any layout, any page count.
Obligations, atomised and attributed.
Sub-system requirements, per element.
Stage, method, evidence — per clause.
Every child back to its parent.
Your documents, judged per stage.
A status per hazard, rolled up.
Traceable, evidenced, audit-ready — end to end.
Platform Functions
Every one of them a real screen, run on a synthetic contract. Nothing redrawn, nothing mocked up.
Screen capture coming
Hazard Closure runs in the platform today — this screen just has not been captured for the site yet. Everything described here is live.
› Every screen here runs on an independent demonstration project. No client data appears anywhere.
› Columns are yours to show or hide — these screens are trimmed, not cropped.
› Every view here is export-ready: CSV, Excel, or your audit pack.
Safety, end to end
The safety-related flag is set once and carried consistently from CRS through SRS to V&V — cautious by design, and always justified. Hazards from your log link to their safety requirements, so closure isn't a guess: a hazard closes only when every one of its requirements is genuinely closed.
Consistent & cautious
A three-layer merge eliminates CRS/V&V safety contradictions and catches safety-action items the classifier might miss.
No false closures
A hazard with an un-assessed or unmatched SR can never read CLOSED — it stays OPEN with an explicit reason.
Enterprise Trust & Architecture
Rail contracts are among the most sensitive documents you hold. RR Trace runs on Microsoft Azure with EU data residency — documents segregated per project, deleted on request, and never used to train shared models.
Single sign-on through Microsoft Entra External ID, with multi-factor authentication enforced via Security Defaults.
PostgreSQL row-level security enforces strict per-client isolation at the database — verified in production.
Secrets live in Azure Key Vault and are reached through Managed Identity — nothing hard-coded, nothing shared.
All AI reasoning and indexing run on Azure. Your prompts and documents stay in our Azure environment and never train shared models.
Contract PDFs are parsed by Azure Document Intelligence — robust extraction, without files ever leaving Azure.
Per-IP rate limiting, backups with blob soft-delete & versioning, and a disaster-recovery plan with a tested restore.
Bring a real EPC contract and a hazard log. We'll show you the CRS, the V&V, and a live closure roll-up — in minutes.