If You Don't Know Exactly What Happens in Your System, You Are Leaving a lot of Safety Improvement Potential on the Table
How to Make Your Mission Critical System Safer by Knowing What Happens in a Key Component of Your System
The definition of a mission critical system is that a failure can have disastrous consequences, including death, destruction, bankrupting entire big companies, economic crisis, ...
Examples for such mission critical systems are:
- Air traffic control,
- Industrial processes, e.g. in chemical industry,
- Atomic power plants,
- Railway interlocking systems,
- Maritime control,
- Big stock traders.
Of course, such systems are usually designed in a redundant way, such that one mistake should not cause a failure of the whole system.
One of the Most Critical Components of such a System Is Human-Machine-Interaction.
Why is this component so critical?
Due to the critical role of humans in mission critical systems, good training of these humans is of vital importance.
Among others, the following learning methods are very effective for that:
I think you'll agree that these are very effective learning methods that should be part of any training.
Below we show how recording human computer interaction can help with these methods
Reproducing human-computer-interaction is important for making mission critical systems safer.
We can provide the recording technology for that: With DisplayRecorder, we offer a field-proven software which records human-computer-interaction of mission critical systems. Continuously, 24x7.
"DemoRecorder is an integral part of the successful operation of Airways' air-traffic control systems.
Chris has a strong work ethic and customer focus, and I've enjoyed working with him as he's enhanced DemoRecorder suitably for our needs.
The system is performing well - it just works."
When there was a malfunction in a complex mission critical system, it is important to localize the subsystem where the cause of that malfunction was located.
Once you know the subsystem,
- You can concentrate your efforts on a much smaller area,
- You know which vendor to consult for further analysis. And you can prove to this vendor that something in their subsystem has caused the problem. So you'll avoid finger-pointing across multiple vendors.