System safety program requirements generally

The plan developed by the contractor to meet the system safety program requirement of the government (as specified in the contract) is generally called the system safety program plan (SSPP). 

Section 4, General Requirements, in 882E delineates the minimum mandatory requirements for an acceptable system safety program. Section 4.1.4, as follows, gives the steps to be taken in reducing risk, in an order of precedence. ... 

Military Handbook (MIL-HDBK)-516B, Airworthiness Certification, DoD Handbook, delineates the U.S. military aircraft airworthiness certification process. It also contains a list of the typical certification data required for airworthiness certification, which leads to a flight clearance. It includes a section on system safety, a system safety program (SSP), and a software safety program (SwSP). System safety generally provides the safety evaluation of hardware and software for airworthiness flight clearance recommendations. System safety is involved in ensuring that the Aircraft Airworthiness Authority s standards are satisfied for the airworthiness authority involved. 

As a primer. Standard Practice for System Safety, 882-D, Department of Defense. General system safety concepts and program requirements are set forth. 

The system safety requirements paragraph discusses program objectives, general design requirements, the system safety precedence (safety precedence sequence), and risk assessment descriptions of both severity and probability categories (Tables 3-1 and 3-2). 

Nevada adopts federal OSHA standards by reference and enforces OSHA standards contained within 29 CFR, parts 1910 (General Industry), 1926 (Construction) and 1928 (Agriculture). In addition, Nevada has adopted additional requirements to include safety programs, cranes, steel erection, construction projects, asbestos, explosives, ammonium perchlorate and photovoltaic system projects. 

The actual noise levels produced by HVAC systems can var) considerably, and it is not possible to generalize the problems that may be encountered. From a safety point of view, it is advisable to start hearing conservation programs for workers. Permanent hearing damage will result when the noise levels exceed 80 dB(A) for a given time period. Whenever possible, it is desirable to control noise pressure levels to meet the requirements of speech communication in this case noise should not exceed 65-70 dB(A). 

FIFRA23 imposes a system of pesticide product registrations. Such requirements include premarket review of potential health and environmental effects before a pesticide can be introduced in the United States, reregistration of products introduced prior to the enactment of FIFRA to assess their safety in light of current standards, and classification of pesticides for restricted or general use. Restricted products can be used only by those whose competence has been certified by a state program. 

Nevertheless in the context of the licensing procedure hardwired activation of safety functions is demanded in addition to PES activation, since it is still difficult to assess the reliability of computer programs. However, in [6] aspects are presented which have to be accounted for if electric/electronic/programmable electronic systems (E/E/PES) are used to realize safety functions. Below some general remarks are made following [7]. The corresponding mathematical and technical treatment is presented in Chap. 11. Since the requirements of [6] can be applied as well to other control systems than (E/E/PES) we speak in what follows of PCE equipment with the understanding that any of the above types of process control is meant. 

For fires, in particular, every regulatory system has issued guide criteria and requirements which, in general, necessitate the implementation of a complete fire protection program. This includes provisions for the separation of redundant safety systems, other prevention measures, anti-fire equipment and operating procedures. 

Safety management systems are largely nonprescriptive that is, the regulations and standards in this field generally provide very little specific detail as to what has to be done. This lack of detail explains why the technical section of the SEMS rule is so short. The regulation merely requires that programs be in place, that they be adhered to, and that they work. 

The safety requirements must correctly reflect the critical properties of the environment in which the software is to operate. This is of importance since the software system may react differently in different environments and it is imperative to exercise the programs with representative inputs. In practice, general user requirements will change over a period of time and a necessary feature of the safety specification will provide for maintainabihty of the safety systems so that the achieved safety level is not compromised by future alterations. 

---