Routine Hazard Analysis

Employees can be helpful in analyzing jobs, processes, or activities for hidden hazards and in helping to design improved hazard controls. Employees and supervisors frequently are teamed up to accomplish these activities. For complicated processes, an engineer probably will lead the team [7]. 

Employees are more likely to accept the changes that result from these analyses if they are involved in the decisions that revise practices and processes. For more information on routine hazard analysis and job hazard analysis in particular, refer to Chapter 15. 

---

Job Hazard Analysis (4) Employees involved in the development of current hazard analysis on their jobs. (3) Hazard analysis program exists for some jobs/processes and understood by affected employees. (2) Hazard analysis program exists for a few jobs/processes and understood by affected employees. (1) Hazard analysis program exists, but few employees involved and most not aware of results. (0) No routine hazard analysis process in place at facility. 

Checking documentation is a standard andit techniqne. It is particularly useful for understanding whether the tracking of hazards to correction is effective. It can also be used to determine the quality of certain activities, such as self-inspections or routine hazard analysis. 

Job hazard analysis. Routine hazard analysis, such as job hazard analysis, process hazard analysis, or task hazard analysis [2] refer to Chapter 15... 

To combat this issue, a routine hazard analysis should be conducted. One of the most common reasons for injuries are tasks that are performed over and over many times daily, weekly, monthly, year after year, etc. These become a hazard because we get used to doing the same task over and over. It becomes a natural routine. We loose the ability to think of the consequences. For example, driving a car becomes second nature to us. How many times have you passed a landmark and do not remember passing it This is the same as an employee doing a specific task over and over without thinking. 

Change analysis prevents expensive problems before they occur. Individuals who are knowledgeable in employee safety can help to design and plan for changes at the worksite. Change analysis uses elements of routine hazard analysis appropriate to the type of change being contemplated. 

Routine hazard analysis also adds hazards to your inventory. It will help you to control hazards that develop in work procedures or in processes, or that occur because of changes in the phases of the operation. 

Pre-use Analysis Comprehensive Surveys Self Inspections Routine Hazard Analysis Employee Reports of Hazards Accident Investigations Pattern Analysis... 

There is no routine hazard analysis system in place... 

Do a hazard analysis on all procedures, including routine ones, for failure modes where releases of materials, contamination, or exposures could occur. 

Software hazard analysis (SWHA) is a system safety analytical technique whose primary function is to systematically evaluate any potential faults in operating system and applications software requirements, codes, and programs as they may affect overall system operation. The purpose of the SWHA is to ensure that safety specifications and related operational requirements are accurately and consistently translated into computer software programs. In this regard, the analysis will verify that specific operational safety criteria, such as failsafe or fail-passive, have been properly assimilated into operational software. The SWHA will also identify and analyze those computer software programs, routines, or functions that may have direct control over or indirect influence on the safe operation of a given system. Also, in the operation of the computer software command function, there is a potential that the actual coded software may cause identified hazardous conditions to occur or inhibit a desired function, thereby creating additional hazard potential. 

Software Preliminary Hazard Analysis This type of analysis is used to identify software program routines that are considered to be safety-critical, and thus is conducted prior to software program coding. To perform the analysis, the analyst should make reference to any available system specifications, interface documentation, functional flow diagrams, software flowcharts, storage and file allocation specifications, and any other program descriptive information. 

Cl. Is there at least a minimally effective hazard analysis system in place for routine operations and activities ... 

C3. What hazard analysis technique(s) are employed for routine operations and activities (e.g., job hazard analysis, HAZOPs, fault trees) Are they adequate ... 

C4. Are the results of the hazard analysis of routine activities adequately documented ... 

FI. Does the hazard-tracking system address hazards found by employees, hazard analysis of routine and nonroutine activities, inspections, and accident or incident investigations ... 

If a non-routine or new task is eventually to be done on a routine basis, then a hazard analysis of this routine task should subsequently be developed. 

Examples of system safety analyses include routine hazard spotting job safety analysis hazard and operability studies design safety analysis fault-tree analysis and simulation exercises using a computer. 

Watch the movements that employees make in performing their tasks to see if there are existing or potential cumulative trauma disorders (CTDs) or other ergonomic issues Suggest processes for routine process hazard analysis... 

You will be able to determine if one or more hazard analysis systems designed to address routine job, process, or phase hazards are in place at the facility. 

The standard does not specify a specific time period for routine procedure review. It suggests that one of the roles of the hazards analysis team is to help define this schedule. 

---