Improvement: fix Management of Safety Anomalies findings #1138
Description
Important
Make sure to link this issue with the PR for your improvement.
Deviation_4: For safety classified issues (problems), it is not defined how affected versions/ released products are identified and potential product recalls are identified. It is imperative to identify the exact moment when the problem occurs. The process of notification of all users needs to be described. The responsibility of the user of the product shall be clarified: the user is responsible for checking for known safety issues (this requires a process of publishing known safety issues (with version information).
Deviation_5: The Safety Manager shall be able to bypass the Technical Lead for escalation of safety anomalies.
Document: https://eclipse-score.github.io/score/main/platform_management_plan/safety_management.html
Action_19: The activities / arguments when a Safety Anomaly can be considered as managed are missing. It might be that the future Problem Resolution Process covers the requirements of a Safety Anomaly process