Industries
Requirements, hazards and verification for rail systems
A rail team can keep its requirements, the hazards they answer and the tests that verify them in OpenV, traced in both directions and frozen at each lifecycle phase with a baseline. Sub-systems and suppliers work in child projects whose results roll up. OpenV provides no evidence for its own tool class under EN 50128, so a project that needs that evidence produces it from its own evaluation.
Updated by Desktop Machine Shop, the makers of OpenV.
What these teams keep
EN 50126 sets a lifecycle with requirements, hazard identification and verification at each phase. EN 50128 asks for software requirements that trace to system requirements and to tests, and EN 50129 for a safety case built on that evidence. A hazard record ties each hazard to its mitigation and to the proof the mitigation is in place.
Where it goes in OpenV
- Requirements in a tree, each with a stable reference that survives edits and moves.
- Hazards linked to the design items that mitigate them, with an open hazard on the gap list.
- A safety integrity level as an attribute on each requirement, defined once for the project.
- A baseline at the end of each phase, and a document from it for the phase review.
- Child projects for sub-systems, with a supplier limited to its own.
- An activity log that names who changed what and when.
A first project
Enter one sub-system: its requirements, the hazards from the hazard record that apply to it, and their mitigations. Add the test cases and record a run. Then download the baseline as a document and check it against what your assessor asked for at the last phase review.
What OpenV does not do
- No certification, no tool qualification kit and no claim of compliance with any standard named on this page. OpenV holds the record; your process and your assessor decide whether it is enough.
- No hazard record fields such as tolerable hazard rate built in; they are attributes you define.
- No evidence for the tool’s own classification or validation under EN 50128.
- Audit-log export and retention settings are not built yet.
- No electronic signatures, and no separate approver role: any project editor can approve, including their own change.
- OpenV is in alpha: screens still change between releases, though data, exports and the API stay compatible across stable releases.
