System safety analysis process and instruction

• US 20030233245A1
• Filed: 06/17/2002
• Published: 12/18/2003
• Est. Priority Date: 06/17/2002
• Status: Abandoned Application

• Current Assignee: the united states of america as represented by the secretary of the navy
• Original Assignee: the united states of america as represented by the secretary of the navy
• Inventors: Zemore, Michael G.
• Application Number:
  US10/172,229
• Publication Number:
  US 20030233245A1
• Time in Patent Office: Days
• US Class Current: 705/317
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/018 Certifying business or products
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety

Abstract

A safety analysis process and system are disclosed. The safety analysis evolution includes four phases: safety program definition, detailed safety analysis, safety disposition, and sustained safety engineering. In the safety program definition phase, a safety program is thoroughly defined through the generation of system safety plans and the establishment of the safety team. In the detailed safety analysis phase, the system is thoroughly analyzed using a systematic analysis approach while all engineering data is captured in the unified hazard tracking database. In the safety disposition phase, the safety posture is formally disclosed to safety review officials and operational safety precepts are generated. In the sustained safety engineering phase, the safety efforts are maintained, including maintaining the hazard tracking database and assessing the safety impact of reported problems, proposed engineering changes, maintenance changes, and incident reports.

Claims

1. A safety analysis system comprising:

a safety program definition phase in which a safety program is defined;

a detailed safety analysis phase to analyze the safety of the system;

a safety disposition phase to dispose the safety program as has been analyzed; and

,

a sustained system safety engineering phase to sustain the safety program as has been analyzed and disposed.

2. The system of claim 1, wherein the safety program definition phase comprises generation of a system safety management plan.

3. The system of claim 2, wherein the safety program definition phase further comprises definition of a system safety program plan, definition of a software safety program plan, and definition of safety design principles, leading from the generation of the system safety management plan.

4. The system of claim 3, wherein the safety program definition phase further comprises definition of a preliminary hazards list, leading from definition of the system safety program plan.

5. The system of claim 3, wherein the safety program definition phase further comprises definition of a master system safety schedule.

6. The system of claim 1, wherein the detailed safety analysis phase comprises establishment of a system hazard tracking database comprising a plurality of records corresponding to defined system safety critical events based at least in part on causal factors, system safety critical functions also defined.

7. The system of claim 6, wherein the detailed safety analysis phase further comprises establishment of a software hazard tracking database as part of the system hazard tracking database.

8. The system of claim 7, wherein the detailed safety analysis phase further comprises maintenance of the software hazard tracking database.

9. The system of claim 6, wherein the detailed safety analysis phase further comprises maintenance of the system hazard tracking database.

10. The system of claim 6, wherein the detailed safety analysis phase further comprises performance of software analysis and validation based at least in part on maintenance of the system safety critical functions and the system safety critical events, the software analysis and validation including one or more software criticality analyses leading to software trouble reports.

11. The system of claim 10, wherein the detailed safety analysis phase further comprises an assessment of safety impact based on at least the software trouble reports, ultimately leading to modification of the system hazard tracking database.

12. The system of claim 10, wherein the detailed safety analysis phase further comprises requirements and design changes influencing the one or more software criticality analyses and resulting from requirement changes, design and code changes, and procedure changes themselves resulting from review of the system hazard tracking database.

13. The system of claim 10, wherein the safety disposition phase comprises maintenance of the system hazard tracking database, and maintenance of a software hazard tracking database that is part of the system hazard tracking database.

14. The system of claim 13, wherein the safety disposition phase further comprises generation of operational safety precepts and safety assessment reports resulting from analysis results from the detailed safety analysis phase and reporting from the system hazard tracking database.

15. The system of claim 10, wherein the sustained system safety engineering phase comprises maintenance of the system hazard tracking database, and maintenance of a software hazard tracking database that is part of the system hazard tracking database.

16. The system of claim 15, wherein the sustained system safety engineering phase further comprises assessment of safety impact of software trouble reports, and performance a risk assessment based on the assessment of the safety impact and system safety critical events, the risk assessment leading to updating of the system hazard tracking database.

17. The system of claim 15, wherein the sustained system safety engineering phase further comprises generation of requirement changes, software patches, and procedure changes and training.

18. The system of claim 15, wherein the sustained system safety engineering phase further comprises generation of requirement and design changes, safety device designs, and procedure changes and training based on analysis of and resulting in modification of the system hazard tracking database.

19. A method comprising:

defining a safety program, including a system safety program plan and a preliminary hazard lists based on the system safety program plan;

analyzing the safety program using analysis methods including a preliminary hazard analysis, a system hazard analysis, a subsystem hazard analysis, and an operating and support hazard analysis;

establishing and maintaining a system hazard tracking database based at least in part on the preliminary hazards list, the system hazard tracking database comprising a plurality of records corresponding to defined system safety critical events, system safety critical functions also defined;

dispositioning safety of the system being analyzed, including maintaining the system hazard tracking database, generating operational safety precepts and safety assessment reports resulting from analyzing the system hazard tracking database and presenting the analysis results to various safety review boards; and

,

sustaining the safety engineering activities, including maintaining the system hazard tracking database, assessing of a safety impact of software trouble reports, performing a risk assessment based on the assessing of the safety impact and the system safety critical events, and updating the system hazard tracking database based on the risk assessment.

20. The method of claim 19, wherein the system hazard tracking database includes at least a software hazard tracking database.