Air Force System Safety Handbook - System Safety Society

More documents

Recommendations

Info

Hazard Assessment. A safety assessment (Task 301) or safety compliance assessment (Task 402) report may be all that is necessary or available to gather detailed hazard information concerning an NDI program. If the selected system must be modified to meet mission requirements, other hazard analyses may be required, especially if the modifications are not otherwise covered. The full analysis uses Task 202, 204 or 205, and possibly 206 or 207. <strong>System</strong> <strong>Safety</strong> Groups. Requiring a system safety group meeting early in the program will help clarify system characteristics versus mission requirements and allow time to address issues. An additional SSG can be used to assure satisfactory closure of issues and smooth fielding of the system. Periodic SSGs through the remainder of the life cycle can be used to address on going concerns and special issues. 39
5.1 SSPP--Task 102. (Note: Task numbers came from MIL-STD-882C and are continued in the DoD Deskbook acquisition tool) The SSPP is a basic tool used by the MA to assist in managing an effective system safety program. It can be used to evaluate the various contractors’ approaches to, understanding of, and execution of their system safety tasks, their depth of planning to make sure their procedures for implementing and controlling system safety tasks are adequate, and their organizational structure to make sure appropriate attention will be focused on system safety activities. (30:A-8) The purpose of the Task 102 is to develop an SSPP. MIL- STD-882D does not mention a specific SSPP. Instead, it requires documentation of an overall approach to achieving system safety objectives. Task 102 is no longer called out in the standard, but has been placed in the DOD Deskbook reference tool as a guide. Its principles still apply to current system safety efforts, so it is covered in this handbook. The task describes in detail the tasks and activities of system safety management and system safety engineering required to identify, evaluate, and eliminate hazards, or reduce the associated risk to a level acceptable to the MA throughout the system life cycle. An SSPP provides a basis of understanding between the contractor and the MA as to how the system safety program will be accomplished to meet contractual safety requirements included in the general and special provisions of the contract. (30:102-1) Proper preparation of an SSPP requires coming to grips with the hard realities of program execution. It involves the examination and reexamination of anticipated problems and establishing a management system which will ensure effective solutions. The program offices specifies the system safety planning requirements by the inclusion of MIL-STD-882 in contracts. The plan can be either developed by the program managing activity or as a contractor requirement. The contractor-prepared plan, submitted normally with the proposal, describes the contractor’s approach to implementation of the requirements specified on the contract.. The plan is prepared to reflect an integrated program management and engineering effort. It includes details of those methods the contractor uses to implement each system safety task described by the statement of work and by those documents listed for compliance. The plan defines all requirements to perform the system safety task, including all appropriate related tasks and complete breakdown of all system safety tasks, subtasks, and resource allocations for each program element through the term of the contract. A basic plan is required at program initiation (prior to milestone 0) to identify system safety mission element needs for existing or projected capability. This will aid in identifying opportunities to improve mission capability and reduction of life-cycle costs. The plan will be updated at the beginning of each subsequent program phase to describe the tasks and responsibilities for the following phase. (37:3-9) Never apply a plan prepared by one contractor to the contract of another. Each plan is unique to the corporate personality and management system. The plan is prepared so that it CHAPTER 5 SYSTEM SAFETY PROGRAM PLAN (SSPP) 40 describes a system safety approach and involves system safety in all appropriate program activities. It also describes the contractor’s approach in defining the critical tasks leading to system safety certification. The plan describes methods by which critical safety problems are brought to the attention of program management and for management approval of closeout action. (37:3-9) The plan should describe an organization with a system safety manager who is directly accountable to the program manager as his agent for system safety. This agent must not be organizationally inhibited from assigning action to any level of program management. The plan describes methods by which critical safety problems are brought to the attention of program management and for management approval of close-out action. Organizations which show accountability through lower management levels are ineffective, therefore, are unacceptable. (37:3-9) This chapter discusses the significant information necessary for an effective SSPP. Specific contractual direction for the system safety program is contained in MIL-STD-882, while the format for presenting that program is directed by Data Item Descriptions (DI-SAFT-80102 to DI-SAFT-80106). It is important to understand that each data item explains the minimum level of information to be delivered to the government and describes the format for presenting it. The MIL-Standard levies the minimum performance requirements on the contractor. The discussions that follow are meant to give an understanding of the importance of required information, not to describe the specific information. (37:3-10) The SSPP is normally valid for a specific period of time. This time period is associated with a particular phase of the system life cycle because separate contracts are awarded as development of equipment proceeds through each phase of the life cycle. For example, a contract is awarded to develop a prototype during the validation phase, another contract is awarded to develop hardware and software during full-scale engineering development, and still another contract is awarded when the equipment enters the production phase. Progressing from one phase of the life cycle to the next, the new contract may specify that the SSPP prepared from the former contract simply be revised to meet the requirements of the new contract. (32:44) 5.2 Program Scope. Each SSPP shall describe, as a minimum, the four elements of an effective system safety program: a planned approach for task accomplishment, qualified people to accomplish tasks, authority to implement tasks through all levels of management, and appropriate resources, both manning and funding, to assure tasks are completed. The SSPP should define a program to satisfy the system safety requirements imposed by the contract. (30:1) Each plan should contain a systematic, detailed description of the scope and magnitude of the overall system safety task. This includes a breakdown of the project by organizational component, safety tasks, subtasks, events, and responsibilities of each organizational element, including resource allocations and the contractor’s estimate of the level
Page 1 and 2: “designing the safest possible sy
Page 3 and 4: Chapter Page Forward ..............
Page 5 and 6: Fig # Title Page 1-1 System Safety
Page 7 and 8: Acceptable Risk. That part of ident
Page 9 and 10: Articles/Papers REFERENCES 1. Cleme
Page 11 and 12: 1.3 Need for System Safety. Why is
Page 13 and 14: integrated with other factors that
Page 15 and 16: Figure 1-4 SYSTEM SAFETY OBJECTIVES
Page 17 and 18: 9. Nature and severity of hazards u
Page 19 and 20: CONCEPT EXPLORATION • Evaluate sy
Page 21 and 22: CONSTRUCTION (facilities) • Ensur
Page 23 and 24: existing levels of system safety an
Page 25 and 26: (a) Provides risk assessments to SA
Page 27 and 28: Block 5--Increased Safety Awareness
Page 29 and 30: 3.1 Definitions. System safety is a
Page 31 and 32: 3.4 Mishap Severity Categories and
Page 33 and 34: FREQUENCY OF OCCURRENCE Figure 3-5
Page 35 and 36: j. To point out to a designer how h
Page 37 and 38: g. Ensure that the appropriate syst
Page 39 and 40: Figure 4-1 FUNCTIONS OF SAFETY ORGA
Page 41 and 42: An explosive safety program encompa
Page 43 and 44: Quality assurance establishes polic
Page 45 and 46: safety requirements have been impos
Page 47: instead uses the tailoring process
Page 51 and 52: This section of the plan contains t
Page 53 and 54: program tasking should be sufficien
Page 55 and 56: h. Develop a method of exchanging s
Page 57 and 58: 7.1 Analyses. (28:39-40) Role of An
Page 59 and 60: d. Any other events, that considera
Page 61 and 62: CONCEPT STUDIES (PHL) SYSTEM SAFETY
Page 63 and 64: design specifications. In addition,
Page 65 and 66: a. Of the modes of failure, includi
Page 67 and 68: . Potential material substitutions
Page 69 and 70: are identified, monitored, and comp
Page 71 and 72: 9.1 Fault Hazard Analysis. (33:47-4
Page 73 and 74: The SCA of military systems has inc
Page 75 and 76: doors, sunglasses, machine guards,
Page 77 and 78: Checklists)? There are others, such
Page 79 and 80: not directly provide useful informa
Page 81 and 82: c. Procedures, manuals, etc. These
Page 83 and 84: shutdown. This is a relatively smal
Page 85 and 86: c. Perform or update the PHA done d
Page 87 and 88: (2) Adequate safety provisions are
Page 89 and 90: 11.1 Program Office Description. A
Page 91 and 92: management officer (DMO) is usually
Page 93 and 94: Once the details of these tasks are
Page 95 and 96: arrangements, an assessment of the
Page 97 and 98: f. Assist the contractors in making
Page 99 and 100:
12.1 Contracting Principles. (34:6-
Page 101 and 102:
A SOO is attached to an RFP to spec
Page 103 and 104:
Type E - Material Specifications Ty
Page 105 and 106:
Type A--System/Segment Specificatio
Page 107 and 108:
13.1 Process. CHAPTER 13 EVALUATING
Page 109 and 110:
ascertain if the safety requirement
Page 111 and 112:
Develop and prepare program plans a
Page 113 and 114:
The contractor SSPP will be updated
Page 115 and 116:
Facility safety design criteria is
Page 117 and 118:
10. Skill in written and oral commu
Page 119 and 120:
eflect the local concern for operat
Page 121 and 122:
c. Review equipment installation, o
Page 123 and 124:
15.1 Acceptable/Unacceptable Risk.
Page 125 and 126:
FACILITIES SYSTEM SAFETY INDUSTRIAL
Page 127 and 128:
15.3 Biomedical Safety. (37:Chapter
Page 129 and 130:
• Mishap Class/system identificat
Page 131 and 132:
c. A Nuclear Safety Cross-check Ana
Page 133 and 134:
17.1 General. There are many variat
Page 135 and 136:
characteristics are under configura
Page 137 and 138:
The AFMC supplement to AFI-91-202 p
Page 139 and 140:
TRB DEFICIENCY REPORTS MISHAP REPOR
Page 141 and 142:
these elements should be investigat
Page 143 and 144:
The modification risk-assessment su
Page 145 and 146:
20.1 General. Test and Evaluation (
Page 147 and 148:
Development of these scenarios crea
Page 149 and 150:
isk, or to stop the test until the
Page 151 and 152:
Figure A-1. Mission Requirements/El
Page 153 and 154:
• Capability (task loading) • O
Page 155 and 156:
preliminary hazard list. The major
Page 157 and 158:
• System Hazard Analysis • Oper
Page 159 and 160:
sensitivity analysis. Here, an asse
Page 161:
(5) Revising Maintenance Requiremen
show all

Air Force System Safety Handbook - System Safety Society

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?