Safety Test Reporting with Low-Integrity Viewer Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
High integrity safety systems face challenges in efficiently displaying and interacting with safety test results due to the need for high integrity viewers, which increases complexity and cost, particularly in rail infrastructure projects where complex software is used to ensure data accuracy and prevent safety-critical events.
Innovation Solution
A safety testing system that integrates a high integrity safety test reporting system with a low integrity report viewer, where safety test results are pre-filtered and displayed in a log file, allowing operators to interact with a less complex viewer that does not require the same high integrity level.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a high integrity report viewer is used to display safety test results, then data integrity and safety are ensured, but system complexity and cost increase
Solution Approach 1:
The system separates the reporting functionality into two distinct components: a high integrity safety test reporting system that generates and validates reports, and a low integrity report viewer that displays pre-validated information. This segmentation allows each component to have appropriate integrity requirements, reducing overall system complexity while maintaining data integrity through the reporting system's validation processes
Solution Approach 2:
The high integrity safety test reporting system acts as an intermediary between the safety testing processes and the low integrity report viewer. It pre-processes, validates, and formats safety test results before presenting them to the viewer, ensuring data integrity is maintained throughout the chain while allowing the viewer to operate at lower integrity levels
2Measurement precision
If a high integrity report viewer is used to display safety test results, then data accuracy is maintained, but development cost increases
Solution Approach 1:
The system divides the reporting architecture into two parts with different integrity requirements: the safety test reporting system that ensures data accuracy through high integrity processes, and the report viewer that can be developed at lower cost with reduced integrity requirements. This segmentation reduces overall development cost while maintaining data accuracy in the critical reporting functions
Solution Approach 2:
The report viewer is designed as a lower-cost, simpler component that does not require the same high integrity certification as traditional systems. By offloading the critical integrity functions to the reporting system, the viewer can be implemented more economically while still ensuring data accuracy through the pre-validated information it receives
3Ease of operation
If safety test results are displayed with detailed filtering options, then operator control is improved, but software complexity increases
Solution Approach 1:
The high integrity safety test reporting system performs preliminary filtering, sorting, and organization of safety test results before presenting them to the report viewer. Critical information is pre-processed and highlighted, reducing the need for complex filtering operations in the viewer while maintaining operator control over the displayed information
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A safety testing system and method are described. The safety testing system provides a combination of a high integrity safety test reporting system that generates a log file of test results, and low integrity report viewer. The use of the system and method in the context of rail infrastructure systems is also described.