PURPOSE
|
The purpose of Task 102 is to develop a System Safety Program Plan (SSPP). It describes in detail tasks and activities of system safety engineering required to identify, evaluate, and eliminate/control hazards, or reduce the associated risk to a level acceptable to the MA throughout the system life cycle. The approved plan provides a formal basis of understanding between the contractor and MA on how the system safety program will be executed to meet contractual requirements, including general and specific provisions
| |
TASK DESCRIPTION
|
PROGRAM SCOPE AND OBJECTIVES
|
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,
| |
Appropriate commitment of resources (both manning and funding) to assure tasks are completed.
| |
Define a program to satisfy the system safety requirements imposed by the contract.
| |
Describe the scope of the overall program and the related system safety program.
| |
List the tasks and activities of system safety management and engineering.
| |
Describe the interrelationships between system safety and other functional elements of the program.
| |
List the other program requirements and tasks applicable to system safety identify where they are specified or described.
| |
Account for all contractually required safety tasks and responsibilities.
| |
Provide matrix to correlate the requirements of the contract to the location in the SSPP where the requirement is addressed.
| |
SYSTEM SAFETY ORGANIZATION
|
Describe the system safety organization or function within the organization of the total program using charts to show the organizational and functional relationships, and lines of communication.
| |
Describe the organizational relationship between other functional elements having responsibility for tasks with system safety impacts and the system safety management and engineering organization shall be shown.
| |
Describe review and approval authority of applicable tasks by system safety.
| |
Describe the responsibility and authority of system safety personnel, other contractor organizational elements involved in the system safety effort, subcontractors, and system safety groups.
| |
Describe the methods by which safety personnel may raise issues of concern directly to the program manager or the program manager's supervisor within the corporation.
| |
Identify the organizational unit responsible for executing each task.
| |
Identify the authority in regard to resolution of all identified hazards.
| |
Describe the staffing of the system safety organization for the duration of the contract to include manpower loading, control of resources and a summary of the qualifications of key system safety personnel assigned to the effort, including those who possess coordination/approval authority for contractor prepared documentation.
| |
Describe the procedures by which the contractor will integrate and coordinate the system safety efforts including assignment of the system safety requirements to action organizations and subcontractors, coordination of subcontractor system safety programs, integration of hazard analyses, program and design reviews, program status reporting, and system safety groups.
| |
Describe the process through which contractor management decisions will be made including timely notification of unacceptable risks, necessary action, incidents or malfunctions, waivers to safety requirements, program deviations, etc.
| |
Describe details of how resolution and action relative to system safety will be effected at the program management level possessing resolution authority.
| |
SYSTEM SAFETY PROGRAM MILESTONES
|
Define system safety program milestones.
| |
Relate the milestones to major program milestones, program element responsibility, and required inputs and outputs
| |
Provide a program schedule of safety tasks including start and completion dates, reports, and reviews.
| |
Identify subsystem, component, software safety activities as well as integrated system level activities (i.e., design analyses, tests, and demonstrations) applicable to the system safety program but specified in other engineering studies and development efforts to preclude duplication
| |
Provide the estimated manpower loading required to complete each task.
| |
GENERAL SYSTEM SAFETY REQUIREMENTS AND CRITERIA
|
Describe general engineering requirements and design criteria for safety..
| |
Describe safety requirements for support equipment and operational safety requirements for all appropriate phases of the life cycle up to, and including, disposal.
| |
List the safety standards and system specifications containing safety requirements that shall be complied with by the contractor. Include titles, dates, and where applicable, paragraph numbers
| |
Describe the risk assessment procedures.
| |
The hazard severity categories, hazard probability levels, and the system safety precedence that shall be followed to satisfy the safety requirements of the program.
| |
State any qualitative or quantitative measures of safety to be used for risk assessment including a description of the acceptable/unacceptable risk levels. Include system safety definitions which modify, deviate from or are in addition to those in this standard.
| |
Describe closed-loop procedures for taking action to resolve identified unacceptable risk including those involving nondevelopmental items.
| |
HAZARD ANALYSIS
|
Describe the analysis techniques and formats to be used in qualitative or quantitative analysis to identify hazards, their causes and effects, hazard elimination, or risk reduction requirements and how those requirements are met
| |
Describe the depth within the system to which each technique is used including hazard identification associated with the system, subsystem, components, software, hazardous materials, personnel, ground support equipment, nondevelopmental items, facilities, and their interrelationship in the logistic support, training, maintenance, operational and disposal (including render safe and emergency disposal) environments.
| |
Describe the integration of subcontractor hazard analyses with overall system hazard analyses.
| |
Efforts to identify and control hazards associated with materials used during the system's life cycle.
| |
SYSTEM SAFETY DATA.
|
Describe the approach for collecting and processing pertinent historical hazard, mishap, and safety lessons learned, data
| |
Identify deliverable data by title and number, and means of delivery (e.g. hard copy, electronically, etc.).
| |
Identify non-deliverable system safety data and describe the procedures for accessibility by the MA and retention of data of historical value.
| |
SAFETY VERIFICATION
|
Describe the verification (test, analysis, inspection, etc.) requirements for making sure that safety is adequately demonstrated.
| |
Identify any certification requirements for software, safety devices or other special safety features (e.g., render safe and emergency disposal procedures
| |
Describe procedures for making sure safety-related verification information is transmitted to the MA for review and analysis.
| |
Describe procedure for ensuring the safe conduct of all tests.
| |
AUDIT PROGRAM
|
Describe the techniques and procedures to be employed by the contractor to make sure the objectives and requirements of the system safety program are being accomplished.
| |
TRAINING
|
Describe the safety training for engineering, technician, operating and maintenance personnel
| |
INCIDENT REPORTING
|
Describe in the SSPP the mishap/incident alerting/notification, investigation and reporting process including notification of the MA
| |
SYSTEM SAFETY INTERFACES
|
Identify the interface between system safety and all other applicable safety disciplines such as: nuclear safety, range safety, explosive and ordnance safety, chemical and biological safety, laser safety and any others
| |
Identify the interface between system safety, systems engineering, and all other support disciplines such as: maintainability, quality control, reliability, software development, human factors engineering, medical support (health hazard assessments), and any others.
| |
Identify The interface between system safety and all system integration and test disciplines.
| |
The contractor will provide a plan which complies with the requirements in paragraph 102.2 above in their reply to the solicitation as part of their proposal or integrated master plan and will be made a part of the contract.
| |
DETAILS TO BE SPECIFIED IN THE SOLICITATION
|
Imposition of Tasks 101 and 102.
| |
Identification of additional information to be provided.
| |