SMS - Hazards and mitigations - Common register?
Hi,
Now when SMS are being introduced, all of our design organisations are most likely going to have a continuous findings regarding hazard description and mitigations needed, when the DOA team leaders will start requesting more and more risks and mitigations to be implemented. (even more prescriptive than before)
=> I thought it could perhaps be of interest of having a shared database of "handled" hazards, where we as DOAs could copy the work form each other. This will in a way minimise the work effort needed for all organisations, and also create a standard what is an acceptable hazard. If a hazard and its mitigation has been accepted by one DOA team leader, why should it not been accepted by another? thus we can stop EASA making unfair findings....
=> Of course, no one will share IP without a benefit. those organisations willing to participate get access, those who don't....
What say you all?
SMS - Hazards and mitigations - Common register?
Hi,
Now when SMS are being introduced, all of our design organisations are most likely going to have a continuous findings regarding hazard description and mitigations needed, when the DOA team leaders will start requesting more and more risks and mitigations to be implemented. (even more prescriptive than before)
=> I thought it could perhaps be of interest of having a shared database of "handled" hazards, where we as DOAs could copy the work form each other. This will in a way minimise the work effort needed for all organisations, and also create a standard what is an acceptable hazard. If a hazard and its mitigation has been accepted by one DOA team leader, why should it not been accepted by another? thus we can stop EASA making unfair findings....
=> Of course, no one will share IP without a benefit. those organisations willing to participate get access, those who don't....
What say you all?
English
Arabic
French
Spanish
Portuguese
Deutsch
Turkish
Dutch
Italiano
Russian
Romaian
Greek