BNL NSLS-II Accident Investigation
ACCIDENT INVESTIGATION COMMITTEE REPORT ON THE LEG INJURY AT THE BNL NSLS‐II CONSTRUCTION SITE THAT OCCURRED ON SEPTEMBER 30, 2009
DRAFT December 4, 2009
BROOKHAVEN NATIONAL LABORATORY
Draft
1
December 4, 2009
BNL NSLS-II Accident Investigation
This page has been left blank intentionally.
Draft
2
December 4, 2009
BNL NSLS-II Accident Investigation
TABLE OF CONTENTS Tables and Figures.......................................................................................................................................... 6 Acronyms......................................................................................................................................................... 7
Executive Summary ........................................................................................................................................ 9 1.0 Introduction.............................................................................................................................................. 13 1.1 Background ..................................................................................................................................... 13 1.2 Facility Description .......................................................................................................................... 14 1.3 Project Management ....................................................................................................................... 15 1.3.1 Contractual Responsibilities ................................................................................................ 17 1.4 Scope, Purpose, and Methodology ................................................................................................. 19 1.4.1 Accident Investigation Terminology ..................................................................................... 20
2.0 Facts ........................................................................................................................................................ 21 2.1. Accident .......................................................................................................................................... 21 2.1.1 Description of the Accident Site........................................................................................... 21 2.1.2 Description of the Accident .................................................................................................. 22 2.2 Emergency Response ..................................................................................................................... 25 2.3 Chronology ...................................................................................................................................... 26 2.4 Environmental Conditions ............................................................................................................... 27 2.5 Operator Training and Qualifications .............................................................................................. 28 2.6 Laborer Training and Qualifications ................................................................................................ 28 2.7 Forklift Specifications ...................................................................................................................... 29
3.0 Analysis ................................................................................................................................................... 30 3.1 Analysis of Conflicting Statements ................................................................................................. 30 3.1.1 Spotter and Hand Signals .................................................................................................... 30 3.1.2 Mud ...................................................................................................................................... 33 3.2 Barrier Analysis ............................................................................................................................... 34 3.3 TapRooT® Analysis ......................................................................................................................... 34 3.4 Event & Causal Factors Analysis .................................................................................................... 35 Draft
3
December 4, 2009
BNL NSLS-II Accident Investigation
3.5 Project Oversight............................................................................................................................. 35 3.5.1 Analysis of Contract Attachment A, Article 43 ..................................................................... 35 3.5.2 Analysis of Contract Attachment A, Article 16 ..................................................................... 44 3.5.3 Analysis of BSA and NSLS-II Oversight .............................................................................. 45 3.6 Integrated Safety Management....................................................................................................... 47 3.6.1 Guiding Principles ................................................................................................................ 49 3.6.2 Define Work ......................................................................................................................... 50 3.6.3 Analyze the Hazards............................................................................................................ 51 3.6.4 Develop and Implement Controls ........................................................................................ 52 3.6.5 Perform Work Safely............................................................................................................ 54 3.6.6 Feedback and Improvement ................................................................................................ 55 3.7 Analysis of Emergency Response .................................................................................................. 60
4.0 Conclusions and Judgments of Need ..................................................................................................... 61 4.1 Direct, Root, and Contributing Causes ........................................................................................... 62 4.2 Judgments of Need ......................................................................................................................... 68
5.0 Other Analyses Required by Team Charter ............................................................................................ 71 5.1 Immediate Response to the Accident ............................................................................................. 71 5.1.1 Discussion/Recommendations ............................................................................................ 72 5.2 Safety Incentive Program ............................................................................................................... 72 5.2.1 Discussion/Recommendations ........................................................................................... 75 5.3 Review of Construction Safety Program Implementation ............................................................... 76 5.3.1 Field Observations ............................................................................................................... 76 5.3.2 Adequacy of Torcon’s Safety Plan Implementation and Flowdown to Subcontractors ....... 76 5.3.3 Adequacy of BNL Oversight of Torcon’s Safety Program ................................................... 76 5.3.4 Recommendations to Improve Overall Construction Site Safety ........................................ 77 5.4 Non-Accident Investigation Judgment of Need – HIPAA ................................................................ 78
6.0 Accident Investigation Committee Signatures ........................................................................................ 79
Draft
4
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDICES Appendix A – Accident Investigation Committee Charter ............................................................................... 80 Appendix B – Waiver ....................................................................................................................................... 82 Appendix C – Summary of Interview Statements ........................................................................................... 83 Appendix D – Footnotes .................................................................................................................................. 85 Appendix E – Barrier Analysis of the Accident (Physical and Administrative) ................................................ 92 Appendix F – TapRooT® Analysis ................................................................................................................... 99 Appendix G – Events and Causal Factors Analysis ........................................................................................ 105 Appendix H – Accident Scene Survey ........................................................................................................... 113 Appendix I – BNL Meteorological Summaries for September and October 2009 .......................................... 114 Appendix J – Description of Radio Transmissions .......................................................................................... 118 Appendix K – Description of Call to BNL Emergency Reporting Number ....................................................... 120 Appendix L – Letter from Rebar Steel Corp. Detailing Laborer’s Experience................................................. 121 Appendix M – Reference Documents ............................................................................................................. 122 Appendix N – Accident Investigation Committee Members ............................................................................ 126
Draft
5
December 4, 2009
BNL NSLS-II Accident Investigation
TABLES Table 1. Chronology of the Accident and Response ............................................................................................. 26 Table 2. Summary of Causes Identified and the Corresponding ISM Core Functions and Guiding Principles. ... 57 Table 3. Event causes, summaries, sources, and associated JONs. ................................................................... 62 Table 4. Contributing causes to program weaknesses, summaries, sources, and associated JONs. ................. 64 Table 5. Judgments of Need. ................................................................................................................................ 68
FIGURES Figure 1. Conceptual view of the NSLS-II when completed.................................................................................. 14 Figure 2. NSLS-II Construction Project Chart as of June 3, 2009. ....................................................................... 15 Figure 3. BSA, Torcon, and subcontractor relationships with respect to this accident. ....................................... 16 Figure 4. BSA/NSLS-II, Torcon, and subcontractor key ES&H requirements and their flowdown with respect to this accident. ......................................................................................................................................................... 18 Figure 5. Aerial view of the NSLS-II construction site taken from the BNL HFBR Stack facing southeast, September 30, 2009, at 0800 hours. ..................................................................................................................... 21 Figure 6. Aerial view taken prior to the accident on September 30, 2009, facing southwest. .............................. 22 Figure 7. Shows the accident site facing northeast. ............................................................................................. 23 Figure 8. Operator’s view facing east, looking out of the Lull at the accident area. ............................................. 24 Figure 9. Photo taken on September 30, 2009, at approximately 0940 hours. ................................................... 34 Figure 10. Tire marks and impression in the ground visible in the center, above the bundle of rebar. ................ 85 Figure 11. Staging area (accident location). ......................................................................................................... 86 Figure 12. Staging area (accident location), including the Lull. ............................................................................ 86 Figure 13. Rebar storage locations. ...................................................................................................................... 87 Figure 14. Operator’s view. ................................................................................................................................... 88 Figure 15. Load chart for Lull. ............................................................................................................................... 88 Figure 16. The spoil pile is visible at the back of the photo. ................................................................................. 89 Figure 17. Broken cribbing. ................................................................................................................................... 90 Figure 18. Broken center wire tie visible in bundle on the right-hand side. .......................................................... 91 Figure 19. Broken center wire tie visible in bundle in front of photograph. ........................................................... 91 Draft
6
December 4, 2009
BNL NSLS-II Accident Investigation
ACRONYMS ANSI
American National Standards Institute
BLS
Bureau of Labor Statistics
BNL
Brookhaven National Laboratory
BSA
Brookhaven Science Associates
BHSO
U.S. Department of Energy Brookhaven Site Office
CAIRS
Computerized Accident, Incident Reporting System
CFR
Code of Federal Regulations
DART
Days away, restricted, or transferred
DEAR
Department of Energy Acquisition Regulation
DOE
Department of Energy
E&CFC
Events and Causal Factors Charting
EMT
Emergency Medical Technician
EMS
Emergency Management System
ES&H
Environment, Safety, and Health
ESH&Q
Environment, Safety, Health and Quality
ETA
Estimated time of arrival
HASP
Health and Safety Program
HFBR
High Flux Beam Reactor
ISM
Integrated Safety Management
ISMS
Integrated Safety Management System
ISO
International Organization for Standardization
IO
Internal Audit and Oversight
JON
Judgment of Need
JRA
Job Risk Assessment
LIE
Long Island Expressway
Draft
7
December 4, 2009
BNL NSLS-II Accident Investigation
NSLS
National Synchrotron Light Source
NSLS-II
National Synchrotron Light Source II
OHSAS
Occupational Health & Safety Advisory Services
OSHA
Occupational Safety and Health Administration
PDHQ
Police Department Head Quarters
PHA
Phase Hazard Analysis
PTI
Project Technologies International, LLC
RTV
Rough Terrain Vehicle
SBMS
Standards-Based Management System
SHE
Safety, Health, and Environment
SHSD
Safety and Health Services Division
Draft
8
December 4, 2009
BNL NSLS-II Accident Investigation
EXECUTIVE SUMMARY On September 30, 2009, at 0840 hours, a Laborer at the National Synchrotron Light Source II (NSLS-II) construction site at Brookhaven National Laboratory (BNL) was injured when a bundle of rebar struck his leg. He was directing the Operator of the rough-terrain forklift (Lull) to place bundles of rebar on cribbing in preparation for pickup by crane, when the rebar struck his right leg and fractured it. The rebar was immediately removed from his leg by the Operator using the Lull. At 0845 hours, BNL’s Laboratory Protection Division’s emergency reporting number, extension 2222, received a call from Torcon’s Safety Manager advising of the injury and requesting an ambulance. In parallel, Torcon’s site EMT was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing medical care. At 0848 hours, the BNL Fire Captain arrived at the scene and assumed the role of Incident Commander. Upon arrival of the BNL Ambulance at 0848 hours, BNL Fire Rescue personnel assumed responsibility for the injured worker and prepared him to be transported to Stony Brook University Medical Center (Hospital) via BNL Ambulance. The injured arrived at the Hospital Emergency Room at 0936 hours, and the BNL Ambulance returned to BNL at approximately 1030 hours. On October 1, 2009, Dr. Steven Dierker, NSLS-II Project Director, charged an independent Accident Investigation Committee to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. On October 6, 2009, six days after the accident, the Laborer was released from the Hospital. He had undergone surgery to repair the fracture and rehabilitation to allow him to move with crutches. Five continuous calendar days in a hospital requires a Type B investigation per DOE O 225.1A, Accident Investigations. However, on October 7, 2009, Michael D. Holland, Manager, Office of Science Brookhaven Site Office (BHSO), received a Memorandum from Glenn S. Podonsky, Chief Health, Safety and Security Officer, Office of Health, Safety and Security, granting a request by BHSO to allow BSA’s Accident Investigation Committee to complete the investigation with DOE oversight. The Accident Investigation Committee began its activities on October 1, 2009 and submitted the final report to the NSLS-II Project Director on December 4, 2009. The charge of the Committee was to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. The Accident Investigation Committee applied several analytical techniques to determine the causal factors of the event. They included Barrier Analysis (BA), Events and Causal Factors Charting (E&CFC), and TapRooT® (TR). Facts were also analyzed using the Core Functions and Guiding Principles of Integrated Safety Management (ISM). In addition, ES&H oversight was evaluated against contract requirements. A Human Factors Scientist reviewed the accident description and these analyses to ensure Human Performance Improvement was incorporated in the results. The Accident Investigation Committee also analyzed the adequacy of the Contractor’s safety program implementation and flow down to subcontractors, as well as the adequacy of BSA’s NSLS-II oversight of the Contractor (as per its charter) using the above results. The Committee limited this analysis to those processes and systems viewed during the performance of the accident investigation, therefore this should not be interpreted as a full analysis. Draft
9
December 4, 2009
BNL NSLS-II Accident Investigation
The Accident Investigation Committee has concluded that this accident was preventable. There is one direct cause and two root causes to this event, which are summarized in the following table.
DCE No. 1 RCE No.
Direct Cause of the Event Laborer struck by rebar
JON 1, 2, 5 & 7
Root Cause of the Event
JON
1
Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities.
1, 5 & 7
2
Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety.
2, 5 & 7
The Accident Investigation Committee identified four causes that did not contribute to this event but contributed to weakening the NSLS-II ES&H Program at the construction site, which are summarized in the following table.
CCW No.
Contributing Cause (Program Weakness)
JON
1
Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels.
3, 5 & 7
2
Torcon and its subcontractors failed to ensure implementation of the NSLS‐II ES&H Program and therefore contributed to its weakness.
4, 5 & 7
3
Torcon and its subcontractors failed to implement an effective suspect/counterfeit program for rigging.
5, 6 & 7
4
NSLS‐II failed to ensure that the NSLS‐II ES&H Program was performing as designed.
5 & 7
Draft
10
December 4, 2009
BNL NSLS-II Accident Investigation
Judgments of Needs were developed to address each Cause and are as follows:
No.
Draft
Judgment of Need
Cause Codes
1
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure workers are qualified and possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities in compliance with (1) Contract Attachment A, Article 43, (2) ES&H program and (3) ISM.
DCE‐1 RCE‐1
2
DCE‐1 There is a need for Torcon and all its subcontractors, at all levels, on RCE‐2 the NSLS‐II construction site, to ensure workers are aware of foreseeable hazards and protective measures for their safety. This includes, but is not limited to defining “major phases” of work to determine when hazard analyses are required, establishing the criteria for acceptance of hazard analyses, discussing hazards and their controls during pre‐job briefings, and ensuring compliance with (1) Contract Attachment A, Article 43 (d)(1), Establishment of Safety Protocols, and (2) Torcon’s SHE Program Section 11, PHAs.
3
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to establish clear and unambiguous lines of authority and responsibility for the implementation the (1) Contract, (2) Torcon’s SHE Program, and (3) other ES&H requirements.
CCW‐1
4
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure all ES&H requirements of the Contract and Torcon’s SHE Program are being adequately implemented. This includes, but is not limited to, the following requirements: • Contract, Attachment A o Article 16, Suspect/Counterfeit Items o Article 43 subsections (d)(1) Establishment of Safety Protocols (d)(2) Frequent and Regular Inspections of the Work Site (f) Immediate Notification to BSA’s Contractual Representative of Recordable Injuries (k) Subcontractor’s Compliance with ES&H
CCW‐2
11
December 4, 2009
BNL NSLS-II Accident Investigation
No.
Judgment of Need
Cause Codes
Requirements of the Contract • Torcon’s SHE Program o Section 11, PHAs o Section 14, Daily Inspections of Heavy Equipment o Section 19, Procedures for Injuries and Near Misses o Section 23, Job Site Inspections o Section 38, Rigging Procedures and Inspections • NFPA 10, Standard for Portable Fire Extinguishers DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
5
There is a need for the NSLS‐II project to provide adequate oversight to ensure that BSA ES&H Contract requirements and the NSLS‐II ES&H programs are being fully implemented. This includes, but is not limited to: • Compliance with Contract, Attachment A, Article 43 (g), Written Notification to Contractor of Non‐compliances • Compliance with BSA’s Construction Safety Subject Area • Compliance with NSLS‐II ES&H Management Plan, paragraph 3.3.1.1, Safety Responsibilities • Compliance with NSLS‐II Project Procedure LT‐ESH_P‐00013, Safety Inspections.
6
CCW‐3 There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to implement an effective suspect/counterfeit program for rigging. This includes, but is not limited to, revising Torcon’s SHE program to reflect inspection of rigging equipment for suspect/counterfeit items prior to use and ensuring there are no unknown suspect/counterfeit items currently in use on the NSLS‐II construction site. There is a further need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure that Contract, Attachment A, Article 16, is being met.
7
There is a need for the NSLS‐II project to establish and implement a well structured assessment program to complement field inspections. The assessment program should be designed to ensure all elements of the ES&H program required by the Contract and ES&H Plans are functioning properly. The schedule should be established to ensure elements that support or monitor life protection programs (e.g., LOTO, confined spaces, excavation, electrical safety) are given priority.
DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
Draft
12
December 4, 2009
BNL NSLS-II Accident Investigation
1.0
INTRODUCTION
1.1
BACKGROUND
On September 30, 2009, at 0840 hours, a Laborer at the National Synchrotron Light Source II (NSLS-II) construction site at Brookhaven National Laboratory (BNL) was injured when a bundle of rebar struck his leg. He was directing the Operator of the rough-terrain forklift (Lull) to place bundles of rebar on cribbing in preparation for pickup by crane, when the rebar struck his right leg and fractured it. The rebar was immediately removed by the Operator using the Lull. At 0845 hours, BNL’s Laboratory Protection Division’s emergency reporting number, extension 2222, received a call from Torcon’s Safety Manager advising of the injury and requesting an ambulance. In parallel, Torcon’s site EMT was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing medical care. At 0848 hours, the BNL Fire Captain arrived at the scene and assumed the role of Incident Commander. Upon arrival of the BNL Ambulance at 0848 hours, BNL Fire Rescue personnel assumed responsibility for the injured worker and prepared him to be transported to Stony Brook University Medical Center (Hospital) via BNL Ambulance. The injured arrived at the Hospital Emergency Room at 0936 hours, and the BNL Ambulance returned to BNL at approximately 1030 hours. On October 1, 2009, Dr. Steven Dierker, NSLS-II Project Director, charged an independent Accident Investigation Committee to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. This report responds to that charge. On October 6, 2009, six days after the accident, the Laborer was released from the Hospital. He had undergone surgery to repair the fracture and rehabilitation to allow him to move with crutches. Five continuous calendar days in a hospital requires a Type B investigation per DOE O 225.1A, Accident Investigations. However, on October 7, 2009, Michael D. Holland, Manager, Office of Science Brookhaven Site Office (BHSO), received a Memorandum from Glenn S. Podonsky, Chief Health, Safety and Security Officer, Office of Health, Safety and Security, granting a request by BHSO to allow BSA’s Accident Investigation Committee to complete the investigation with DOE oversight (see Appendix B).
Draft
13
December 4, 2009
BNL NSLS-II Accident Investigation
1.2 FACILITY DESCRIPTION NSLS-II will be a new state-of-the-art, medium-energy electron storage ring designed to deliver world-leading intensity and brightness, and will produce x-rays more than 10,000 times brighter than the current NSLS located at BNL. The conventional facilities required for the NSLS-II will include a Ring Building of approximately 392,000 square feet. The Ring Building will serve as the centerpiece of the NSLS-II and will house offices for the visiting user community, laboratory space, the main accelerator ring, experimental beamlines, experimental floor area, and supporting facilities.
Figure 1. Conceptual view of the NSLS-II when completed.
The construction type for the Ring Building will be reinforced slab on grade with perimeter footing, structural steel frame with composite reinforced concrete slab on metal deck for the upper floors, and insulated metal panel exterior. Although the building design will generally involve standard commercial design and construction techniques, there are some additional considerations due to the specific requirements of the accelerator, experimental beamlines, and types of research that will take place in laboratory spaces. Placement of the floor slab will involve an estimated 35,000 cubic yards of concrete, with special consideration given to minimization of differential settlement to assure alignment integrity of the installed accelerator and beamlines. Draft
14
December 4, 2009
BNL NSLS-II Accident Investigation
The NSLS-II Ring Building has been designed to minimize sources of vibration and transmission of vibration that would impact beam stability in the accelerator and experimental beamline areas and laboratory spaces. Construction started in April 2009, is currently in progress, and is scheduled for completion in April 2012.
1.3 PROJECT MANAGEMENT Brookhaven National Laboratory is operated by Brookhaven Science Associates, LLC, (BSA) who is under contract to the United States of America’s Department of Energy. Figure 2 provides an organizational chart for the NSLS-II Construction Project.
Figure 2. NSLS-II Construction Project Chart as of June 3, 2009.
Draft
15
December 4, 2009
BNL NSLS-II Accident Investigation
BSA has contracted the construction of the NSLS-II Ring Building to Torcon Incorporated (Torcon). The Operator of the Lull was employed by Macedos Construction, LLC (Macedos), who is under direct contract to Torcon. The Laborer, who was injured, was employed by Rebar Steel Corporation (Rebar Steel), who is under contract to Macedos. Figure 3 illustrates these contractual relationships.
Department of Energy
Brookhaven Science Associates (BSA) Contract for construction of the NSLS-II Ring Building
Torcon, Inc.
Other Subcontractors
Macedos Construction LLC
Operator of the Lull
Laborer who was injured
Rebar Steel Corp. Figure 3. BSA, Torcon, and subcontractor relationships with respect to this accident.
Draft
16
December 4, 2009
BNL NSLS-II Accident Investigation
1.3.1 CONTRACTUAL RESPONSIBILITIES Brookhaven Science Associates (BSA) manages the operations of Brookhaven National Laboratory (BNL) for the United States Department of Energy (DOE). Pertinent to the accident investigation are the environmental, safety, and health (ES&H) roles and responsibilities established by BSA and DOE under Contract DE-AC0298CH10886. BSA implements these roles and responsibilities through its Standards-Based Management System (SBMS). The NSLS-II team has taken these roles and responsibilities described in SBMS as they apply to their entire project and documented them in the Environmental, Safety, and Health Plan for the National Synchrotron Light Source-II; Doc #LT-ESH-002-CD-REV02 (NSLS-II ES&H Plan). To clearly communicate the construction ES&H requirements, the project team created the Environment, Safety, and Health Management Plan for the Construction of the NSLS-II Conventional Facilities, DOC #LT-ESH-0009-Rev1 (NSLS-II ES&H Management Plan). In addition, the project team created the National Synchrotron Light Source II Construction Environment, Safety and Health Plan for Conventional Construction of the Ring Building; Doc #LT-EHS-0006/rev1 (NSLS-II Construction HASP) specifically for the construction activities being conducted by Torcon. BSA contracted Torcon (Contract 7700000004) to perform the construction of the conventional facilities for the NSLS-II Ring Building. Included in the Contract is the NSLS-II Construction HASP. Also included in the contract is Torcon’s responsibility to ensure these requirements are imposed on all of their contractors at all levels and tiers. To demonstrate understanding of these requirements, Torcon was required to submit a health and safety plan that meets the requirements of the NSLS-II Construction HASP prior to the start of work. Torcon’s Project Safety, Health and Environmental Program was reviewed by NSLS-II, BSA, and DOE-BHSO safety and health professionals and approved on March 17, 2009. A notice to proceed was transmitted by BSA to Torcon on March 25, 2009. Figure 4 provides an illustration of the flowdown of pertinent ES&H requirements as it relates to this accident investigation.
Draft
17
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 4. BSA/NSLS‐II, Torcon, and subcontractor key ES&H requirements and their flowdown with respect to this accident.
Draft
18
December 4, 2009
BNL NSLS-II Accident Investigation
1.4 SCOPE, PURPOSE, AND METHODOLOGY The Accident Investigation Committee began its activities on October 1, 2009 and submitted the final report to the NSLS-II Project Director on December 4, 2009. The charge of the Committee was to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. The Committee identified relevant facts; analyzed the facts to determine the direct, contributing, and root causes of the incident; developed conclusions; and determined Judgments of Need that, when addressed, should prevent recurrence of a similar accident. Charge (1) addresses the accident investigation. Charges (2) and (3) expand the scope of the investigation beyond DOE O 225.1A. The accident investigation was performed consistent with DOE O 225.1A, Accident Investigations. The Laborer was in the Hospital for six days, which requires a DOE Type B investigation. However, on October 7, 2009, Michael D. Holland, Manager, Office of Science Brookhaven Site Office (BHSO), received a Memorandum from Glenn S. Podonsky, Chief Health, Safety and Security Officer, Office of Health, Safety and Security, granting a request by BHSO to allow BSA’s Accident Investigation Committee to complete the investigation with DOE oversight (see Appendix B). The investigation conducted by BSA meets the intent of the Order. The following methodology was used: •
Facts relevant to the accident were gathered through reviews of photographs, measurements of the scene and equipment, obtaining interview statements, and a fact finding meeting held on the day of the accident. Following the first day of the accident additional and follow up interviews, measurements and photographs were performed, as well as the review of additional documents and logs.
•
Facts relevant to the adequacy of the contractual safety requirements, the safety incentive program, and the implementation of the construction safety program, were gathered through interviews, the review of documents, and field observations.
•
Facts were analyzed to identify causal factors using Event and Causal Factors Charting (E&CF), Barrier Analysis and TapRooT®. Facts were also analyzed using the Core Functions and Guiding Principles of Integrated Safety Management (ISM). In addition, ES&H oversight was evaluated against contract requirements.
•
The emergency response was evaluated against procedures and effectiveness in performance.
•
Judgments of Need (JONs) for corrective actions to prevent recurrence of the accident and to improve program weaknesses identified were developed.
Draft
19
December 4, 2009
BNL NSLS-II Accident Investigation
1.4.1
ACCIDENT INVESTIGATION TERMINOLOGY
A causal factor is an event or condition in the accident sequence that contributes to the unwanted result. There are three types of causal factors: direct, which is the immediate event(s) or condition(s) that caused the accident; root cause(s), which is the causal factor that, if corrected, would prevent recurrence of the accident; and the contributing causal factors, which are the causal factors that collectively with the other causes increase the likelihood of an accident but which did not cause the accident. The causal factors related to weaknesses in the five Core Functions of Integrated Safety Management (ISM) are analyzed. Event and causal factors analysis includes charting, which depicts the logical sequence of events and conditions (causal factors that allowed the event to occur), and the use of deductive reasoning to determine the events or conditions that contributed to the accident. Barrier analysis reviews the hazards, the targets (people or objects) of the hazards, and the controls or barriers that Management Systems put in place to separate the hazards from the targets. Barriers may be physical or administrative. TapRooT® is a proven tool used to evaluate causal factors that resulted in equipment and human performance problems. The focus is on the system (the way that the work is performed), not the individual. TapRooT® defines causal factors as any problem associated with the incident that, if corrected, would have prevented the incident from occurring or would have significantly mitigated its consequences.
Draft
20
December 4, 2009
BNL NSLS-II Accident Investigation
2.0 FACTS
2.1 ACCIDENT 2.1.1 DESCRIPTION OF THE ACCIDENT SITE On September 30, 2009, the primary construction activities underway on the NSLS-II site were concrete, site work and utility installation. In the accident area, concrete work being conducted included placing forms and rebar for the vehicle tunnel east retaining wall footings, storage ring tunnel floor slab and storage ring tunnel walls. Site work in progress included grading of the north portion of the site to prepare the entrance drive and parking area near the Lobby, additional pouring of concrete to the east, and earthwork required to support installation of drainage utilities on the north and east sides of the site. Utility installations included extension of water mains to the future fire control room, installation of underground sanitary piping under the Ring Building, and installation of electrical grounding for the footings at the Ring Building column line. Figures 5 and 6 show the site on the day of the accident.
Vehicle Tunnel Accident Site SR Tunnel Wall Forms SR Tunnel Slab
Figure 5. Aerial view of the NSLS-II construction site taken from the BNL HFBR Stack facing southeast, September 30, 2009, at 0800 hours.
Draft
21
December 4, 2009
BNL NSLS-II Accident Investigation
Accident area
Original rebar staging area
Form area
Location of Worker 2 at time of accident
Figure 6. Aerial view taken prior to the accident on September 30, 2009, facing southwest.
2.1.2 DESCRIPTION OF THE ACCIDENT The Accident Investigation Committee has reconstructed the accident as they believe it occurred using interview statements, response logs, reports, physical evidence, and fact finding minutes. Photographs were taken by project, BNL Safety & Health Services Division (SHSD) personnel, as well as members of the Accident Investigation Committee. Physical measurements were taken by SHSD and the Accident Investigation Committee. A survey of the accident site was conducted and documented in a scale drawing (see Appendix H). See Appendix D for an explanation of the footnotes and the reasons why the Accident Investigation Committee concluded the event occurred as described. On September 30, 2009, a rough-terrain forklift (Lull) Operator employed by Macedos started work at approximately 0645 hours by performing his daily inspection and testing of the equipment. The Lull was in good working condition and the Operator had no problem with it.1* At 0700 hours, he began working with carpenters to move material. A Laborer employed by Rebar Steel was directed by the Rebar Steel foreman that morning to prepare some rebar for hoisting by a crane into the form work area. At approximately 0815 hours, the Laborer asked the Operator to move some rebar from a laydown area to a staging area where it could be hoisted by crane. The Laborer, acting as a spotter, was directing the placement of the rebar load by directing the Lull. The Operator and the Laborer moved 6 to 7 loads of rebar to another area before starting to work in the area where the accident occurred. The Laborer identified the rebar bundles to be moved by marking them with orange paint. The Operator and the Laborer indicated that they were not under any unusual pressure to get the job done.
*
See Appendix D for all Footnotes
Draft
22
December 4, 2009
BNL NSLS-II Accident Investigation
The Laborer arranged cribbing in the accident area to support the bundles of rebar.2 The Operator, directed by the Laborer, then moved two bundles of rebar into the area, one with a bend and one bundle of ½ inch rebar.3 The Operator, again directed by the Laborer, moved two bundles of 1 ¼ inch rebar into the area.4 Figure 7 shows the staging of the rebar.
Approximate location of Laborer’s head after the accident
Cribbing placed over rebar
First two bundles placed; one with bend and one ½ inch rebar
This was placed after the accident
Approximate location of Laborer’s leg after the accident
Figure 7. Shows the accident site facing northeast. Note the placement of the cribbing, the two bundles laying on it, and the lack of area to move freely while directing the Lull.
At approximately 0835 hours, a second worker (Worker 2) saw the Operator and Laborer preparing to place a load of rebar onto the ground as he was walking behind a spoil pile to his work area. The Laborer was standing in front of the first two bundles of rebar that were placed in the accident staging area, directing the Operator to position the load.5 The Operator was able to clearly see the Laborer giving hand signals, but the load obscured the Operator’s visibility of the Laborer’s feet and lower legs.6 Figure 8 provides a sketch of how the Accident Investigation Committee believes the Operator’s view was obstructed. Although the Laborer is clearly visible, the location of his lower legs is obscured by the load and the location of the rebar behind his feet cannot be seen. The boom extension was 14 to 18 feet.7
Draft
23
December 4, 2009
BNL NSLS-II Accident Investigation
The Laborer’s lower legs and feet are hidden from view.
Two bundles of rebar, one struck the Laborer’s leg. This sketch shows the load just before the accident while it was being moved.
Figure 8. Operator’s view facing east, looking out of the Lull at the accident area. The Laborer’s location is approximate.
The Laborer was directing the Operator while the load was moving toward him, and signaling the Operator to place the load while walking backwards out of the way. 8 The Laborer’s foot contacted the rebar behind him as he was backing up. He was able to get his left leg out of the way, but tripped over the rebar that was behind him and fell backward.9 At approximately 0840 hours, the load was being placed by tilting the forks downward.10 The bundles were sliding off the forks and one of the bundles struck and laid on the Laborer’s leg while the other remained on the forks.11 The Operator saw the Laborer fall and heard screaming. In an effort to remove the bundle of rebar from the Laborer’s leg, the Operator speared the bundle and tilted the forks up, causing the center wire tie of the bundle to break.12 After the load was lifted, the Laborer rolled onto his stomach. The Operator then exited the cab to see if the Laborer was alright. Worker 2 also heard screaming and ran over to see the Laborer on the ground face down and the rebar above him, part on the forks of the Lull and part off the forks, hanging several inches above the Laborer’s legs.13 After Worker 2 arrived on the scene, the Operator moved the load back further by retracting the boom and by moving the vehicle backwards. He then dropped both bundles of rebar to the ground.14
Draft
24
December 4, 2009
BNL NSLS-II Accident Investigation
2.2
EMERGENCY RESPONSE
At 0845 hours, BNL’s Laboratory Protection Division received a phone call via BNL’s emergency reporting number, extension 2222, from Torcon’s Safety Manager advising of an injured worker with an “injury to leg perhaps serious” at the NSLS-II construction work site and the need for an ambulance. At 0846 hours, BNL Fire Rescue’s Car 1, Heavy Rescue Truck, and the Kubota RTV (equipped for patient transport from remote locations), were dispatched to the accident location given. BNL Security also responded to the call. The BNL Ambulance was at the BNL Motor Pool for routine servicing when the call was received. The Motor Pool was notified and the Ambulance was prepared and waiting for the responding crew, who picked up the Ambulance and proceeded to the scene. In parallel, Torcon’s site Emergency Medical Technician (EMT) was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing emergency treatment. A site worker was waiting at the entrance gate to guide the BNL responding vehicles onto the site to where the injured Laborer was located. Upon arrival at the scene, the Fire Captain in Car 1 took control of the accident as the Incident Commander. The Incident Commander notified Suffolk County Police Department (SCPD) aviation in case a helicopter was needed to transport the injured worker. The BNL EMT’s were at the scene within four minutes of the initial call. Upon arrival, they relieved Torcon’s EMT and took custody and control of the injured worker. The BNL Ambulance arrived shortly afterwards. The Injured was evaluated and then prepared for transport. At that time, the Incident Commander and the EMTs who were treating the patient determined that the estimated arrival time of the SCPD helicopter was too long and they would transport the injured worker to Stony Brook University Medical Center (Hospital) via the BNL Ambulance. BNL Ambulance is New York State (NYS) Certified and operates as a basic life support (BLS) unit. Qualifications for a BLS provider include: training to the level of EMT, Defibrillation (EMT-D), and a current NYS Department of Health Certification as an EMT. The NYS Department of Health Bureau of Emergency Medical Services Policy Statement No 98-09, dated 09/01/98, establishes a policy for Advanced Life Support (ALS) intercepts. An Intercept is a staffed unit (person and equipment) that is picked up by the BLS unit while it is en route to the nearest appropriate hospital. If the Intercept is not at the designated point when the BLS unit arrives, the BLS continues on to the hospital without the Intercept, the BLS will not wait for the Intercept. For this accident, the BNL Fire Rescue transport crew initiated the ALS protocol with Suffolk County via radio. Suffolk County dispatched a certified ALS provider to meet the BNL Ambulance on the service road of the Long Island Expressway on route to the Hospital. Pick-up of the ALS provider took less than 20 seconds, as stated by the Chief of Fire Rescue. The Ambulance then continued on to the Hospital. If the ALS provider had not been available, or had not been at the designated area when the Ambulance arrived, the Ambulance would not have stopped and would have continued to the Hospital without the ALS. Per the Chief of Fire Rescue, the actual care the ALS provided falls under the Health Insurance Portability and Accountability Act (HIPAA) and could not be disclosed to the Accident Investigation Committee without the injured worker’s permission, which the Committee was not given. Draft 25 December 4, 2009
BNL NSLS-II Accident Investigation
The Ambulance arrived at the Hospital Emergency Room at 0936 hours and the Injured was transferred to Hospital emergency room staff. After leaving the Hospital, the BNL Ambulance crew returned the ALS provider to his station and returned to BNL at approximately 1030 hours.
2.3 CHRONOLOGY Table 1. Chronology of the Accident and Response
Time
Event
(if it was possible to determine)
Laborer arrives at site and attends orientations. Operator arrives at site and attends orientations. Sept. 16, 2009 Sept. 30, 2009 The remainder of this event takes place on September 30, 2009 0645 hours Operator starts work by performing his daily inspection and testing of equipment. 0700 hours Operator begins to move material for carpenter. Rebar Steel Foreman directs Laborer to prepare rebar for movement by crane into form area. Laborer marks rebar bundles to be moved by spraying them with orange paint. 0815 hours Laborer asks Operator to move rebar with Lull. Laborer, acting as a spotter, directs placement of six to seven loads moved. Laborer places cribbing for rebar to be placed onto. Laborer directs placement of two bundles moved into the incident area. Laborer directs placement of two additional bundles (2,467 lbs. 23 pieces, 24’10” long). 0835 hours As Worker 2 walks by, he sees Operator and Laborer working to lay down rebar. Lull stopped. Boom of the Lull extended to permit load to be placed. Laborer stands in front of two bundles of rebar, in front of the Lull. Laborer signals Operator to place load. Operator tilts forks to place load while Laborer steps backwards to move out of the way. Load slides off the forks of the Lull while the back of Laborer’s foot contacts rebar behind him. Laborer trips over rebar. 0840 hours Rebar strikes lower right leg of the Laborer. 0840 hours Laborer’s right lower leg is fractured. Operator, in response to screams, picks up rebar bundle with the Lull. Sept. 1, 2009
Draft
26
December 4, 2009
BNL NSLS-II Accident Investigation
Time
Event
(if it was possible to determine)
0845 hours 0848 hours 0848 hours 0901 hours 0915 hours Approx. 0915 hours 0936 hours 0944 hours 0946 hours Approx. 1030 hours Approx. 1200 hours
Laborer rolls onto stomach. Operator exits Lull to see if the Laborer is alright. Worker 2, hearing scream, arrives at scene. Operator enters Lull to further retract boom and backs up Lull 6 to 9 feet. BNL Emergency number x 2222 called for Ambulance. BNL Fire Rescue responds. Local (Pembrooke) EMT arrives at scene. Fire Rescue and Security arrive at scene. BNL Ambulance arrives. Ambulance leaves accident site with injured Laborer. Ambulance picks up Advanced Life Support (ALS) provider en route to Hospital. BNL Security secures accident site. Operator leaves BNL. Ambulance arrives at Hospital. Event declared reportable to DOE. Operator returns to BNL for the day. BNL Ambulance returns to BNL. Operator leaves BNL.
2.4
ENVIRONMENTAL CONDITIONS
The recorded temperature for September 30, 2009 at 0900 hours was approximately 55 degrees Fahrenheit, with a wind speed of approximately seven miles per hour from the northwest. There was no recorded precipitation for the day (see Appendix I). The incident area possessed a one percent grade towards the northeast. The soil was composed of sand and clay, was moist and compacted. No water accumulation was observed in the incident area on the day of the accident.
Draft
27
December 4, 2009
BNL NSLS-II Accident Investigation
2.5
OPERATOR TRAINING AND QUALIFICATIONS
The Operator of the Lull was a Journeyman in the International Union of Operating Engineers, Local 138 (Farmingdale, NY), and had over thirty-five years of experience as an Operator of cranes and powered industrial trucks. A summary of his training and qualifications is as follows: • • • • •
New York State Crane Operator – Class A; Expiration August 31, 2012; New York City Department of Buildings Hoist Machine Operator – Class A; Expiration February 28, 2012; International Union of Operating Engineers, Local 138 – 138A – 138B Powered Industrial Trucks; dated 4/02, Refresher Expiration April 2011; International Union of Operating Engineers OSHA 10-Hour Construction Safety & Health Training; dated 5/21/2008; International Union of Operating Engineers OSHA 29CFR1910.120 40-Hour Hazardous Waste Training; Refresher Expiration March 2010.
A review of the training curriculum provided by Local 138 contains the following as it applies to this incident: • •
•
Operator must read and understand the Operator’s Manual for each truck they operate, including warning decals. Instructions for operating around other personnel, including the use of a spotter. In addition, if you use a spotter and you can’t see him or a clear path of travel does not exist, don’t move the truck. From the practical driving test, the following skills are assessed: o Were the loads handled without bumping? o Were the loads centered on the forks? o Were the loads kept low to the ground? o Ability to judge proper clearance all-around when turning.
In addition, the Operator attended BSA’s Contractor Vendor Orientation (CVO) and Torcon’s Project Safety Orientation classes, which are not skill based.
2.6 LABORER TRAINING AND QUALIFICATIONS The Laborer was a member of Laborers’ Local 66, International Union of Operating Engineers, as a Journeyman since September 2009. He was employed by Rebar Steel for the NSLS-II project since September 2, 2009. Rebar Steel provided the following experience and qualifications for the Laborer (see Appendix L): Yardman • • • • • Draft
Moved and disbursed reinforcing steel to different locations. Construction, dismantling and knockdown of shanties on both hi-rises and infrastructures. Mechanic for small engines. Operated forklift - Lifting of materials in the shop yard. Operate and maintain diesel powered stud welding machine. 28 December 4, 2009
BNL NSLS-II Accident Investigation
• • • •
Shoots metal shear studs into Q decking of superstructures. Taught hand signals by job super. OSHA 10 hour Certificate. Weekly Tool Box Talk.
The Union Hall stated that the Laborer was not with them long enough to start any of their training. The Laborer attended BSA’s Contractor Vendor Orientation (CVO) and Torcon’s Project Safety Orientation classes, which are not skill-based. Discussions held by a member of the Accident Investigation Committee and the Long Island Business Agent for Local 66 revealed an employer can request by letter that the Union accept a person the employer wants to sponsor as a full Journeyman. The employer advises the Union that the candidate has all the necessary training to be a Journeyman (approximately 4,000 hours of experience). The employer may have to document time worked for the person by providing “pay stubs” for the previous 4 years worked. A Journeyman is capable of independent work. The Business Agent indicated that Rebar Steel made such a request for the Laborer, which was granted by the Union.
2.7 FORKLIFT SPECIFICATIONS
The power fork lift that was used to move the rebar was a JLG Industries Lull Telehandler Model 1044C54, serial number 0160033803, manufactured in 2008, with 1391 hours on its meter. The rated capacity of this vehicle at 24 inches load center is 10,000 pounds. Its maximum reach is 45 feet with a capacity of 1,500 pounds. Following the accident, the equipment was inspected by BNL’s Hoisting & Rigging Inspector and then by an authorized representative of the manufacturer, both found the equipment and its forks to meet all requirements for the applications. The boom length after the accident was approximately 13 feet. The load capacity for this boom length is 6,000 pounds. At 18 feet, the capacity limit for the Lull is 5,000 pounds. A load of 2,467 pounds for one bundle, or a load of 4,934 pounds for two bundles, was well within this rated capacity.
Draft
29
December 4, 2009
BNL NSLS-II Accident Investigation
3.0
ANALYSIS
The Accident Investigation Committee applied several analytical techniques to determine the causal factors of the event. They included Barrier Analysis (BA), Events and Causal Factors Charting (E&CFC), TapRooT (TR) and were analyzed using the Guiding Principles and Core Functions of (ISM). Causal factors from each technique were grouped under one common causal statement with supporting information following. Each cause is keyed to Tables 3 and 4 in Section 4.0 (see p. 62), which summarize the event causes, provide the analytical technique that was used to establish the cause, and identify the associated Judgment of Need. In addition, a Human Factors Scientist reviewed the accident description and these analyses to ensure Human Performance Improvement was incorporated in the results. The Accident Investigation Committee also analyzed the adequacy of Torcon’s safety plan implementation and flow down to subcontractors, as well as the adequacy of BSA’s oversight of Torcon (as per its charter) using the above results. The Committee limited this analysis to those processes and systems that were reviewed during the performance of the accident investigation. Therefore this report should not be interpreted as a full analysis of the entire Management System. There are two specific areas that warrant further discussion due to their significance in how the Accident Investigation Committee determined the events leading to the accident occurred: the use of a spotter and hand signals, and the Laborer’s statement about getting stuck in the mud. These two topics are discussed in detail in Section 3.1. A summary of the interview statements submitted by the Laborer, Operator, and Worker 2, arranged chronologically, is provided as Appendix C.
3.1
ANALYSIS OF CONFLICTING STATEMENTS
3.1.1 SPOTTER AND HAND SIGNALS This section is an analysis of the events immediately preceding the accident. In this event, the operator of the Lull, a rough terrain forklift, was being guided or directed by a “spotter” or signal person. A spotter or signal person is used in material handling industries whenever an equipment operator’s visibility for the placement of a load may be impaired or obscured. Neither OSHA standards nor ANSI standards address requirements for spotters and only provide the following with respect to visibility for operating a forklift near personnel: •
Do not drive a truck up to anyone standing in front of an object.
•
If the load being carried obstructs forward view, travel with the load trailing.
In this case, neither requirement was applicable to the accident. However, both the manufacturer’s Lull Operator & Safety Manual (1) and the Association of Equipment Manufacturer’s Rough Terrain Forklift Safety Manual (2) retrieved from the cab of the incident forklift provided the following regarding use of a spotter:
Draft
30
December 4, 2009
BNL NSLS-II Accident Investigation
(1) Lull Operator & Safety Manual •
Before Operating the Machine o
o
Plan your work
Before you operate, know how and where you will travel, turn and pickup, lift and place loads.
If you will be placing loads at high elevations, remember your depth perception is decreased because of distance. Use a signal person near the point where the load is to be landed. [emphasis added]
Know the Rules
Make sure you understand all hand, flag, whistle, siren, or bell signals.
(2) Association of Equipment Manufacturers Rough Terrain Forklift Safety Manual •
Know the Rules of Operation o
Make sure you know and understand:
•
•
Hand, flag, whistle, siren or bell signals.
Plan Your Work o
Know the weights of all loads you may be expected to transport before attempting to lift them. Avoid loads of loose material if possible. Check that loads are properly banded or strapped together.
o
If you will be placing loads in landing areas where visibility is a problem, use a signal person near the point where the load is to be landed.
Operate Safely o
Transporting the Load
Carrying the load as low as possible and fully retracted will: •
o
Watch clearances carefully when handling loads that are long, tall or wide. Load end-swing can be deceiving and could cause injury to personnel or damage to objects nearby.
Lifting and Placing the Load
Now that the load has been transported to the location where it is to be placed, remember: •
Draft
Allow for better visibility over the load.
While lifting or lowering always make sure the path of the forks or load is clear of obstacles. 31
December 4, 2009
BNL NSLS-II Accident Investigation
The very reason a spotter is used in material handling evolutions is to assist the equipment operator in situations where visibility may be impaired. Visibility could be impaired by elevation and/or distance, other objects, or the load itself. Other reasons for a spotter could be precision, in that the location requires placement within inches or fractions thereof, which is not possible to accomplish from the operator’s position. In this accident, the Laborer was serving as the spotter and directing the Operator of the forklift to place loads in a position where they could be later hoisted with a crane. This required placement within reach by the crane, and proximity to the other bundles to be hoisted. The incident bundles also were very long - over 24 feet – so clearance was an issue along the path of travel. Through analysis of this accident, the Accident Investigation Committee determined that only the Laborer was responsible for placing the load where it was because he was performing the duties of the spotter or signal person. It is incontrovertible that the Laborer was performing this function because it appears in the statements of both the Operator and the Laborer. Figure 8 (page 24) shows that the load would partially obscure the Operator’s visibility forward of the load on the forks, and particularly the placement of the load. Therefore, the Operator had to rely upon the Laborer’s signals to place the load in the desired location. Figure 8 also clearly shows that the Laborer was visible to the Operator, and the Operator could see the hand signals being given by the Laborer. In fact, the Operator, in both of his statements indicated he was following the signals of the Laborer, and in one statement said he had no problems with visibility (Operator Statement #2). Therefore, there is no evidence that the Operator was moving the load without being able to see the Laborer. The Operator also stated in both statements that the Laborer was standing approximately 5 feet in front of the forks (Operator Statement #1) or 5 feet from where the load was to be dropped (Operator Statement #2). At least this was his perception of the location of the Laborer. His perception that the Laborer was 5 feet away from the forks or the intended placement of the load indicates that the Operator believed the Laborer was a safe distance away from the travel path of the load. Therefore the Operator did not knowingly begin placement of the load with the Laborer in the intended or perceived path of the load. There is some disparity between the Operator’s statements regarding the actions of the Laborer and the Laborer’s statement regarding his actions. In both statements, the Operator indicated the Laborer was standing on bundles of rebar just prior to being struck by the load, and in the first statement he indicated the Laborer backed up to move out of the way of the rebar. This correlates with the Laborer’s statement that he was in the process of “backing up out of the way.” As discussed in footnote 8 to the Accident Description, Section 2.1.2 (pages 22 and 88), the Accident Investigation Committee believes that the Laborer gave a “down” or “tilt down” signal to the Operator in anticipation that he would be out of the way of the load in a couple of steps while he was walking backward. Again, the Laborer, performing the duties of a spotter or signal person, is in the best location to determine where he would be with respect to the load, because the Operator’s visibility is partially obscured. The Laborer’s proximity to the load is consistent with good and accepted safe practice as the Lull Operator’s Manual states to “Use a signal person near the point where the load is to be landed.” It would not be reasonable for the Operator to question the Laborer’s hand signal to place the load if 1) he has a spotter or signal person directing his actions, and 2) the Operator perceived the Laborer was 5 feet from the path of the load. There is no other evidence to the contrary. This is where the Accident Investigation Committee attributes causation to the Laborer because he gave a “down” or “tilt down” signal to the Operator in anticipation that he would be out of the way of the load in a couple of steps while he was walking backward. Therefore, based upon the evidence available, the Accident Investigation Committee can only conclude that the Laborer imprudently gave a “down” or “tilt down” signal to the Operator while he was in the way or path of the load, with the Operator lacking the visual clarity necessary to determine that the Laborer was not a safe distance away – which is why he was using a spotter or signal person. It is possible, and in fact likely, that the Laborer would have been out of the path of the load but for the rebar that he tripped over. Since the Laborer had Draft
32
December 4, 2009
BNL NSLS-II Accident Investigation
placed that rebar at that location within minutes of the accident, the Accident Investigation Committee found the work area organization a contributing cause to the accident, one that is also attributable to the Laborer, primarily due to his lack of training and qualification. Also discussed in footnote 8 to the Accident Description, Section 2.1.2, the Accident Investigation Committee believes that the Laborer gave a “down” or “tilt down” signal to the Operator, and that inconsistent use of hand signals at the construction site is not a possible contributing cause to this accident. The Accident Investigation Committee reached these conclusions considering several facts or the lack thereof. The Operator has several operating engineer licenses and training certificates, as well as many years of construction site experience. The Laborer, however, has mostly yard experience and nonmaterial handling construction experience, and no licenses or operating engineer training, as evidenced by the letter of “experience” provided by Rebar Steel Corporation. The Laborer’s statement regarding the Operator’s previous unexpected response to hand signals is not evidenced by other means. The Laborer did not tell anyone else of these experiences, and construction site management has no record or recollection of this issue. The Operator states he had previously worked with the Laborer and others before the day of the accident and had no trouble understanding the Laborer’s signals. The Operator indicated there are several hand signal methods used on site and he had no problem with any of them. As a crane operator as well as a forklift operator, the Operator would have had training and experience with different signals. The Accident Investigation Committee also evaluated the crane and forklift hand signals and does not believe that a crane stop signal could be misinterpreted as a tilt hand signal. Members of the Accident Investigation Committee have seen the crane stop signal used on the construction site with equipment other than cranes with no indication of misunderstanding between operators and spotters.
3.1.2 MUD The Laborer stated that, immediately prior to the accident, his foot became stuck in mud as he was backing up. The members of the Accident Investigation Committee that responded to the accident site within an hour of the accident did not find mud at the accident site. Figure 9 shows there were no footprints (indents in mud) at all in the area, even from emergency responders. The precipitation report for the month of September shows that there were 1.39 inches of precipitation on September 27, 2009 and 0.12 inches of precipitation on September 28, 2009 (see Appendix I). The area of the accident has been significantly excavated and reshaped, and the normal soil for the entire Long Island area as well as the site is Class C, or sandy soil. In addition, there were 0.74 inches of precipitation on October 3, 2009, and the Accident Investigation Committee on that day did not find any evidence of viscous mud that would trap an individual’s footwear. The rebar was slightly elevated and narrow in diameter, and its contact with the Laborer’s footwear might feel like the foot was stuck, but lateral motion would still be possible, which is consistent with the Laborer’s statement that he was able to get his left foot out of the way. (See also Figures 11 and 16.) For these reasons the Accident Investigation Committee concludes that the Laborer tripped over the rebar and his foot was not stuck in mud.
Draft
33
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 9. Photo taken on September 30, 2009, at approximately 0940 hours. The oval shows the approximate area where the Laborer was standing at the time of the accident. Note that the area is clear of mud and there are no signs of footprints even after emergency response efforts.
3.2
BARRIER ANALYSIS
Barrier Analysis is based on the premise that hazards are associated with all tasks. Barriers are any management or physical means used to control, prevent, or impede the hazard from reaching the target (person or object that a hazard may damage). For an accident or event to occur, there must be a hazard that comes into contact with a target because the barriers or controls were not in place, not used, or failed. The results of the Barrier Analysis are used to support the development of causal factors. Appendix E contains the analysis of the physical and administrative barriers that could have had an impact on this accident and how they performed.
3.3
TAPROOT ANALYSIS
TapRooT® System is a systematic tool used to determine causal factors contributing to equipment and human performance problems. The focus is on the system (the way that the work is performed), not the individual. An analyst, with a small team (for this event, the Accident Investigation Committee) objectively looks at the facts, identifies the problem, and goes through a systematic process to find causes. Software is utilized that documents and assists in the causal analysis process. In this accident investigation, causal factors were identified using E&CFC. TapRooT was then used to analyze each causal factor to determine contributing and root causes. The results of the TapRooT Analysis are provided as Appendix F.
Draft
34
December 4, 2009
BNL NSLS-II Accident Investigation
3.4
EVENT AND CAUSAL FACTORS ANALYSIS
The E&CFC process produces a cause and effects diagram that describes the time sequence of events and the surrounding conditions leading to an event. The purpose of the E&CFC is to identify causal factors. 'A Causal Factor is any problem associated with an event that, if corrected, would have prevented the event from occurring or would have significantly mitigated its consequences' (Taproot, by M. Paradies and L. Unger, 2000). For this accident, the E&CFC created by the Accident Investigation Committee begins with work commencement on the day of the accident and ends shortly after the BNL Ambulance returned to the Laboratory. See Appendix G for the Events and Causal Factors Chart.
3.5
PROJECT OVERSIGHT
The Accident Investigation Committee was tasked to evaluate the ES&H systems and processes in place leading up to the incident to determine if Torcon and NSLS-II oversight was adequate to identify deviations or weaknesses in implementation of the ES&H Program and correct them in a proactive manner. This was accomplished by evaluating the requirements in Attachment A of the Contract, which is entitled Brookhaven Science Associates, LLC General Terms and Conditions for NSLS-II Conventional Construction at Brookhaven National Laboratory, as they pertain to this accident investigation. Two specific Articles in Attachment A provided key requirements for evaluating the performance of the NSLS-II ES&H program implementation. The first was Article 43, Compliance with 10 CFR 851 and Brookhaven Science Associates’ Worker Safety and Health Program by Integration of Environmental, Safety, and Health into Work Planning and Execution. The second was Article 16, Suspect/Counterfeit Items. Although Attachment A contains other Articles that involve ES&H, Articles 16 and 43 are most pertinent to understanding the root and contributing causes to this accident and/or weaknesses to the ES&H Program. Figure 4 provides an illustration of the flowdown of these ES&H requirements. The following sections are organized to provide a review of the pertinent requirement, followed by an analysis of its implementation and the results of that review.
3.5.1 ANALYSIS OF CONTRACT ATTACHMENT A, ARTICLE 43 Review of Requirement Article 43, Compliance with 10 CFR 851 and Brookhaven Science Associates’ Worker Safety and Health Program by Integration of Environmental, Safety, and Health into Work Planning and Execution, requires the contractor to comply with 10 CFR 851 and BSA’s (the Laboratory’s) Worker Safety and Health Program by integrating environmental, safety, and health into work planning and execution. It requires Torcon and all of its subcontractors at all levels to comply with all federal, state, and local environmental, safety, and health laws and regulations applicable to work at the NSLS-II site. The general contractor and all of its subcontractors at all levels are also required to comply with 10 CFR 851 (DOE Worker Safety and Health Program), the Laboratory's Worker Safety and Health Program, and Draft 35 December 4, 2009
BNL NSLS-II Accident Investigation
DEAR 970.5223-1, entitled Integration of Environmental, Safety and Health into Work Planning and Execution, dated December 2000. Specifically, Article 43 (b) states that the contractor shall perform work safely, in a manner that ensures adequate protection for employees, the public, and the environment, and will be held accountable for the safe performance of work. It further states that the contractor is to exercise a 'degree of care' commensurate with the work and the associated hazards and ensure that management of ES&H functions and activities becomes an integral and visible part of the work planning and execution processes. The contractor is to submit a Construction ES&H Plan before work commencement that conforms to the NSLS-II Construction ES&H Plan (i.e., the NSLS-II Construction HASP). The Plan must ensure the following during the performance of work: (1) Personnel possess the experience, knowledge, skills and abilities that are necessary to discharge their responsibilities, and will retain records respecting such competency and qualifications, making them available upon request. (2) Prior to work performance, the associated hazards will be evaluated and a set of ES&H standards and requirements will be established and implemented to provide assurance that employees, the public, and the environment are protected from adverse consequences. (3) Line management is responsible for the protection of employees, the public, and the environment. Line management includes those contractor and subcontractor employees managing or supervising employees performing work. (4) Clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance will be established and maintained at all organizational levels.
Analysis of Requirement Torcon was required to submit an ES&H plan that meets the requirements of the NSLS-II Construction HASP prior to the start of work. Torcon submitted their Project Safety, Health, and Environmental Program (Torcon’s SHE Program) to satisfy this requirement. It was reviewed by NSLS-II, BSA, and DOE-BHSO safety and health professionals and approved on March 17, 2009. A notice to proceed was transmitted by BSA to Torcon on March 25, 2009. Highlights of Torcon’s SHE Program include: •
• •
Draft
A written Project-Specific Safety Plan that includes a statement from the subcontractor regarding the scope of work on the NSLS-II project, and Phase Hazard Analyses for all major tasks involved in the scope of work for the project, and the name(s) of the responsible supervisor(s) for safety issues. A copy of the subcontractor’s Corporate Safety Program. A letter from all Torcon’s subcontractors, on the subcontractor’s company letterhead, including the following statements: o That all of their workers have received all required safety training for their jobs. o Name of subcontractor’s representative to the Labor/Management Safety Committee for the project. o Name of subcontractor’s competent supervisor(s) for safety issues on the NSLS-II site. This supervisor must possess the OSHA 30-Hour Course. The subcontractor is also required to provide the name and telephone number of the subcontractor’s Safety Director or chief safety officer. 36
December 4, 2009
BNL NSLS-II Accident Investigation
• •
•
Documentation that the subcontractor’s competent supervisor for safety issues on the site has completed the OSHA 30-Hour Course in Construction Safety. After the subcontractor submits the Project-Specific Safety Plan with PHA’s to the Torcon Safety Manager, a pre-construction meeting is held. At this meeting, safety requirements for the subcontractor’s scope of work are discussed and guidance provided for any changes needed in the PHA’s. Any questions regarding safety or administrative aspects of the job are clarified. Every worker and supervisor on the project is required to attend the BNL Contractor Vendor Orientation (CVO) and the Torcon Project Safety orientation on his/her first day on the project. No one is permitted on the project site before completing both orientations, except for approved and escorted visitors.
The Accident Investigation Committee also reviewed Macedos’ (Torcon’s subcontractor) site specific construction safety plan. Highlights of the plan include: •
• • • • • • •
Macedos’ commitment to provide adequate training to employees, and employees’ responsibility to ask a qualified person for assistance if the employee is in doubt about how to do a job or task safely. Senior management’s responsibility to support and monitor the safety, health, and risk management process. All employees must comply with safety, health, and risk management requirements. Identification of personnel having the authority for implementing the provisions of the safety plan. The responsibility of all supervisors for implementing and maintaining the safety plan in their work areas and for answering worker questions about the safety plan. Major safety hazards/risks and exposures must be assessed and documented in the PHA’s. Daily inspections are required. Macedos’ system for ensuring that all workers comply with the rules and maintain a safe work environment includes: o Informing workers of the provisions of the safety plan. o Evaluating the safety performance of all workers. o Recognizing employees who perform safe and healthful practices. o Providing training to workers whose safety performance is deficient. o Disciplining workers for failure to comply with the safety and healthful practices.
Result of Analysis The Accident Investigation Committee determined that Torcon and its subcontractors failed to implement the contractual requirement to ensure personnel possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities. Based on the work experience provided by Rebar Steel for the Laborer and the layout of the staging area, the Accident Investigation Committee determined, supervision failed to ensure the Laborer was qualified to perform the work safely. The Accident Investigation Committee has determined the following root cause to this accident: Root Cause Statement (RCE-1): Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities. •
Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.
Draft
37
December 4, 2009
BNL NSLS-II Accident Investigation
The Accident Investigation Committee further determined that Torcon failed to meet the contractual requirement for “clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance will be established and maintained at all organizational levels” for the following reasons: •
Torcon was not able to produce an organizational chart or documented roles and responsibilities that were in effect at the time of the accident.
•
Interviews conducted by members of the Accident Investigation Committee with subcontractor supervisors revealed that supervisors believe investigations and toolbox training to be the responsibility of the safety staff and not theirs, though responsibility is clearly stated in the Torcon SHE Program.
•
Interviews conducted by the Accident Investigation Committee with Torcon and its subcontractors did not identify the individual responsible for requesting drug and alcohol screening after an accident. After this accident the Operator was not requested to undergo screening until after he had left the site, over 3 hours after the accident.
•
Torcon was not able to provide documented roles and responsibilities for their Safety Manager.
As a result of this analysis, the Accident Investigation Committee has determined the following is a contributing cause to weaknesses in the implementation of the ES&H Program: Contributing Cause Statement (CCW-1): Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels. •
Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site.
•
Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations.
•
Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager.
Review of Requirement Attachment A, Article 43 (c) states the contractor, must perform and manage work in accordance with BSA’s DOE-approved Integrated Safety Management (ISM) Program and demonstrate through documentation and work practices that its performance of work under the contract: 1) fulfills the scope of work as outlined in the contract; 2) identifies and analyzes specific, task-level hazards associated with the work; 3) develops and implements hazard controls related to the hazards; 4) allows the performance of work within the controls; and 5) provides feedback on the adequacy of hazard controls and continues improvement in safety management as detailed in their ES&H Plan. Section 4 of Torcon’s SHE Program provides their commitment to integrate safety into every phase of the project, from concept through completion of construction. Torcon states they will achieve this by using the ISM System set forth in BNL’s Construction Safety Plan, National Synchrotron Light Source II Draft
38
December 4, 2009
BNL NSLS-II Accident Investigation
Construction Environment, Safety and Health Plan for Conventional Construction of the Ring Building; Doc #LT-EHS-0006/Rev 1. Torcon’s SHE Program describes the five core functions of ISM. It also puts into place the requirements and processes to ensure contractors and their subcontractors have received all the required safety training for their jobs to perform work on the NSLS-II site, but does not provide criteria for said training Attachment A, Article 43 (d)(1) requires the contractor to demonstrate safety protocols applicable to the scope of work that are well-established and consistent with the requirements of the Laboratory's ISM program, prior to the initiation of work. Prior to commencement of work on any major separately definable activity, Torcon must (1) submit a Phase Hazard Analysis (PHA) of the affected work, (2) ensure workers are aware of foreseeable hazards and protective measures described within the PHA, and (3) require that the workers acknowledge being informed of the hazards and protective measures associated with the work activity. NSLS-II Construction HASP, Section 7.1, Job-Specific Work Requirements, states that PHAs shall be developed for each major phase of the Project to be performed on site, but does not define “major”. The PHA shall identify the task and the steps necessary to complete the task, the hazards associated with each step of the task, and the means to protect the workers performing the task from those hazards. It goes on to say that supervisors and employees are responsible for developing the PHA of their work activities. The supervisor is also responsible for ensuring that hazard analyses are developed and reviewed by the employee before work begins. Torcon is required to submit all PHAs to the NSLS-II ES&H Manager, or designee, for review and approval. The completed and approved PHA shall be reviewed with all personnel involved in the task. Torcon’s Project Orientation and General Safety & Health Rules pamphlet is reviewed with each employee during their orientation on the first day on the site. This pamphlet includes discussions on General Safety Rules, Ten Top Tips for Safety, Phase Hazard Analysis, Personal Protective Equipment, and much more. Each employee signs an acknowledgment that states “I have reviewed Torcon’s Project Orientation and General Safety Rules for the Brookhaven National Laboratory NSLS-II Project. I agree that a safe jobsite makes good sense for everyone and will act accordingly. I agree to report any accident in which I am involved to the superintendent/foreman of my employing subcontractor immediately after the incident. I also agree to report any unsafe condition or “near miss” potential injuries which are a result of unsafe conditions or circumstances. I will be responsible for strict observance of Department of Energy, OHSA and Torcon Rules & Regulations.” Torcon’s SHE Program, Section 11, Pre-Planning of All Construction Work (PHA’s), requires that each of their subcontractors break the scope of their work down into major jobs to be performed by their workers and write a PHA for each job. Once the PHAs have been reviewed and approved by Torcon and NSLS-II ES&H, the PHA must be reviewed by the foremen with their workers in the field. Each worker is required to sign off on the PHA form indicating that he has reviewed the requirements and will abide by them during the work. If job conditions change during the work, requiring deviation from the original PHA, the Torcon Superintendent or Safety Manager requires an addendum to the PHA or a new PHA be completed, reviewed, and signed before work can continue.
Draft
39
December 4, 2009
BNL NSLS-II Accident Investigation
Analysis of Requirement The Accident Investigation Committee determined that the Torcon’s Project Orientation and General Safety & Health Rules provides an adequate safety orientation for the project. In addition, Torcon was able to provide signed acknowledgements of review and agreement with the pamphlet for the Laborer and Operator. The Accident Investigation Committee requested a PHA for the work performed by the Laborer and Operator on the day of the injury and was provided with a Macedos’ PHA entitled “All Footings, revised 6/29/09.” This PHA included a job step entitled “Materials pick up w/forklift” and identified one potential hazard, “Dropping/Misplacement Pinchpoints”. The “Preventive or Protective Measures to Be Used” column of the PHA identified the following: 1) flagman direction/horn warning, 2) cordoned off area with caution tape, and 3) spotter will work with forklift. This was the only PHA provided by Torcon that analyzed hazards associated with forklifts. The copy reviewed was not signed by Torcon. There was no place for NSLS-II ES&H to sign the form. However, NSLS-II ES&H indicated that they review all PHAs they receive and usually there are several iterations before they are accepted. The Field Supervisor (employed by Macedos) signed the PHA on July 15, 2009. Nine workers signed the PHA (undated). However, neither the Laborer nor the Operator had signed it.
Results of Analysis The Committee also determined that the PHA lacked specificity in that it was less-than-adequate to identify hazards associated with moving rebar and is a root cause of the accident. Root Cause Statement (RCE-2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Hazard analyses are required for major phases of the project. However, major phases were not defined.
•
Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”.
The Accident Investigation Committee determined that Torcon and its subcontractors failed to fully implement Article 43 (d)(1) of the Contract by not making workers aware and acknowledge hazards and associated measures for their safety and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
•
Draft
Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers. Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11.
40
December 4, 2009
BNL NSLS-II Accident Investigation
Review of Requirement Attachment A, Article 43 (d)(2) requires the contractor to employ a designated ES&H representative with no collateral duties on the worksite. The ES&H representative is to be knowledgeable of the project’s hazards and has authority to act on behalf of the contractor. The ES&H representative must have appropriate training and qualification to perform this function. This person must, as a minimum, have completed the 30-hour OSHA Construction Safety Course and be a Certified Safety Professional, Certified Industrial Hygienist, or have equivalent documented education and experience in construction safety. This section requires the designated ES&H representative to make frequent and regular inspections of the worksite to identify and correct any instances of noncompliance with the project safety and health requirements.
Analysis of Requirement Torcon has assigned a full time Safety Manager to the project. A review of the Safety Manager’s resume indicated that he possesses a Masters Degree in Safety Management, completed the 40-hour OSHA Construction Safety Course, and has the necessary experience in compliance with Article 43 (d) (2). Though the Accident Investigation Committee did not identify any collateral duties for the Safety Manager, we were unable to obtain his roles and responsibilities to fully evaluate his duties. The Accident Investigation Committee reviewed Torcon’s Project Safety Evaluation records documenting Torcon’s daily safety inspections. Some Project Safety Evaluation forms were completed, while others were not, and some work periods were missing altogether. Objective evidence was not available to indicate whether these inspections had actually taken place daily as required by Article 43 (d)(2).
Results of Analysis The Accident Investigation Committee therefore determined that Torcon failed to ensure Section 23 of Torcon’s SHE Program was being adequately implemented and therefore did not fully meet the requirements of Article 43 (d)(2) and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Torcon’s Project Safety Evaluation forms were not completed correctly and some work periods were missing altogether. Objective evidence was not available to indicate whether these inspections had actually taken place daily as required by the contract.
Review of Requirement Attachment A, Article 43 (d)(3) requires workers be instructed to report any hazard not previously identified or evaluated to the Project Superintendent or the Contractor’s Safety Manager. If immediate corrective action is not possible or the hazard falls outside the project’s scope, the contractor must immediately notify affected workers, post appropriate warning signs, implement needed interim control measures, and notify the NSLS-II ES&H Manager of the action(s) taken. The contractor or its designated ES&H representative must stop work in the affected area until appropriate protective measures are established. The contractor’s ES&H representative is required to document the condition and the corrective action in their inspection report. Draft
41
December 4, 2009
BNL NSLS-II Accident Investigation
Analysis of Requirement Torcon’s Project Orientation and General Safety & Health Rules pamphlet, General Safety Rules, 2, states that employees are to report all unsafe practices or conditions to their Foreman and/or Torcon immediately. In addition, this pamphlet provides a section that discusses PHAs and employees’ responsibility to review and sign them. Each employee signs a copy of this pamphlet acknowledging receipt; signed copies of this pamphlet were provided for the Laborer and Operator.
Results of Analysis The Accident Investigation Committee has determined that this is in compliance with Attachment A, Article 43 (d)(3).
Review of Requirement Attachment A, Article 43 (f) requires the contractor to immediately notify the Laboratory's Contractual Representative of any OSHA-recordable injuries/illnesses and any “off-normal occurrences” or government owned property damage that the Contractor has determined to have occurred during the project. As defined in this section, an “off-normal occurrence” is any unplanned or unexpected event, including near misses, or the discovery of a deficiency in a procedure, plan, or system that has real or potentially undesirable consequences to personnel, equipment, facilities, the environment, and/or programs. This section also requires the contractor to ensure compliance with 10 CFR 851.26, Recordkeeping and Reporting. Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses, and Fires, states that all injuries and near misses, and other incidents, such as fires or vehicle accidents, must be reported to Torcon immediately. The first priority will be to ensure that any needed first aid or medical treatment is administered and the scene is secured. Torcon will report the incident to the NSLS-II Construction Safety Engineer. The Accident Investigation Committee performed a comparison of the NSLS-II site EMT Incident Reports and Torcon’s investigations. This revealed that there were several more incidents than investigations. The list of missing reports was provided to Torcon who stated that they were unaware of the injuries and did not investigate them. They also stated that they believed the injuries to be minor or not work related.
Results of Analysis The Accident Investigation Committee determined that Torcon’s response to this accident met their contractual and ES&H program responsibility. The Accident Investigation Committee determined Torcon’s failed to ensure all injuries were being reported in accordance with their Program SHE and therefore did not fully comply with Attachment A, Article 43 (f) and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Draft
Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met. 42
December 4, 2009
BNL NSLS-II Accident Investigation
Review of Requirement Attachment A, Article 43 (k) requires the contractor to be responsible for its subcontractors’ compliance with the ES&H requirements of this contract. The contractor is required to include NSLS-II site ES&H requirements in all agreements with its subcontractors. Torcon’s SHE Program, Section 23, Job Site Inspections, requires documented daily safety inspections to be performed and documented by Torcon and the subcontractors. Section 23 further states that these inspections are to be carried out to ensure compliance with all safety procedures and PHAs. Torcon’s safety inspections are performed by the Safety Manager, Superintendents, Project Manager and Project Executive. Each active subcontractor company is also required to perform a daily safety inspection of their work areas, done by a supervisor, using the form provided in Article 9 of the Program. This form must be completed each day that the subcontractor is active on the site. The completed form is to be submitted to the Torcon Safety Manager on a weekly basis. Any deficiencies found in the safety inspections are to be corrected, with the date of correction noted on the form. The Torcon Safety Manager is required to review these forms daily to identify trends or problem areas so they can be addressed by training or other action.
Analysis of Requirement A review of the records provided to the Accident Investigation Committee indicated that daily safety inspections were not being completed daily by all subcontractors and they were not being filled out correctly in most cases. For example, the records provide a code for indicating whether the inspection results were acceptable or correction is needed. Numerous records were marked in a manner that was incomprehensible and made the feedback unusable. Other records had comments that appeared to need corrective actions, but there was no indication that action was taken. Objective evidence was not available to indicate whether these inspections were actually taking place daily.
Results of Analysis Torcon’s SHE Program is an ES&H contractual requirement (reference Contract Attachment A, Article 43 (d)), the Accident Investigation Committee determined that Torcon failed to ensure Section 23 of Torcon’s SHE Program was being implemented and did not meet the requirements of Article 43(k) to ensure subcontractors’ compliance with ES&H requirements of the contract. Therefore this is a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Draft
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
43
December 4, 2009
BNL NSLS-II Accident Investigation
3.5.2 ANALYSIS OF CONTRACT ATTACHMENT A, ARTICLE 16 Review of Requirement Attachment A, Article 16 describes the prohibition of counterfeit or suspect items on the BNL site and the actions the Laboratory will implement when these items are found. As defined in this article, suspect items are 'items for which there is an indication by visual inspection, testing, or other information that it may not conform to established government or industry-accepted specifications or national consensus standards'. Counterfeit or suspect items include lifting materials, such as slings, hooks, cables, and shackles. Furthermore, this article directs the contractor to the Suspect/Counterfeit Items Subject Area within the Laboratory's Standards-Based Management System.
Analysis of Requirement Suspect shackles and wire clips (no manufacturer's name or stamp) were found on the NSLS-II site several times over several days by members of the Accident Investigation Committee conducting site observations. The suspect shackles and wire clips were impounded and reported to the NSLS-II ES&H Manager. A review of Torcon’s SHE Program, Section 38 Rigging Procedures and Inspections, and its associated Daily Rigging Inspection form, did not indicate a requirement or discussion of the need to inspect for suspect/counterfeit items prior to rigging.
Results of Analysis The Accident Investigation Committee determined that Torcon and its subcontractors failed to implement the requirement of Article 16 to prevent the use of suspect/counterfeit items during rigging operations and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Torcon failed to detect and correct the use of suspect/counterfeit items used during rigging operations.
Contributing Cause Statement (CCW-3): Torcon and its subcontractors failed to implement an effective suspect/counterfeit program for rigging. • •
Draft
Suspect shackles and wire clips (no manufacturer's name or stamp) were found several times over several days by members of the Accident Investigation Committee. Torcon’s SHE Program, Section 38, Rigging Procedures and Inspections, and its associated Daily Rigging Inspection form outlined in Article 38, did not address inspection for suspect/counterfeit items prior to rigging.
44
December 4, 2009
BNL NSLS-II Accident Investigation
3.5.3 ANALYSIS OF BSA AND NSLS‐II OVERSIGHT Review of Requirement The organizational structure and responsibilities for the NSLS-II team is documented in their Environmental, Safety, and Health Plan for the National Synchrotron Light Source-II; Doc #LT-ES&H-002CD-REV02 (NSLS-II ES&H Plan) and is further defined for this phase of construction in the Environment, Safety, and Health Management Plan for the Construction of NSLS-II Conventional Facilities; DOC LTESH-009-Rev1 (NSLS-II ES&H Management Plan). The NSLS-II ES&H Management Plan identifies the requirements for ES&H Project oversight. It states that the Environmental, Safety, and Health Manager (ES&HM) is responsible for implementing the BNL ISM program for the NSLS-II Project to ensure that environmental, safety, and health issues are addressed in the design, construction, and ultimate operations of NSLS-II. In this capacity, the ES&HM’s responsibilities include: •
Utilizing appropriate BNL ES&H subject matter experts (SMEs) to prepare hazard analyses, review design documents, and oversee construction activity to ensure compliance with ES&H standards.
•
Oversee implementation of the construction safety program to ensure compliance with BNL and OSHA regulations, and monitor progress toward “Best in Class” performance.
•
Be responsible for internal oversight and evaluations of the implementation of the NSLS-II construction safety program. The evaluations shall address consistency with defined expectations (i.e., conformance to internal procedures) and shall identify hazards not effectively addressed by the program.
•
Support the implementation of a construction ES&H program consistent with BNL expectations by (1) identifying expectations and (2) developing the construction ES&H Management Plan for implementing those expectations.
•
Communicate concerns and offer constructive guidance directly to other NSLS-II Project personnel.
Analysis of Requirement Both NSLS-II and Torcon’s insurance carriers have performed field observations of this construction site and have provided feedback to improve operations on the site. It appears these recommendations have been implemented. BSA’s Internal Audit and Oversight Office has conducted two assessments on elements of the NSLS-II ES&H program to date: Report IO 09-97 Phase 1, dated August 26, 2009, and IO 09-97 Phase 2 (in draft, the assessment was completed on August 25, 2009). The scope of Phase 1 included a document review of the NSLS-II and Torcon Safety documents. There were no findings or areas for improvements identified. The Phase 2 scope included training provided to all Project personnel. There were no findings, but three areas for improvement were identified. The scope of the assessment of Phase 3 will consist of field observations of work in progress. BSA’s Safety & Health Services (SHSD) Construction Safety Engineer performs NSLS-II site observations on an average of twice a week. These observations are conducted jointly with NSLS-II Draft
45
December 4, 2009
BNL NSLS-II Accident Investigation
personnel, Torcon personnel, and subcontractor personnel. When findings are developed, they are documented by NSLS-II Personnel. NSLS-II conducted one assessment to date, lead by BNL’s Training Coordinator for NSLS-II. The report is entitled Assessment of Brookhaven National Laboratory, National Synchrotron Light Source II Project Training Requirement, dated September 2, 2009, and was scoped to assess project training requirements. One minor non-compliance and one opportunity for improvement were noted. NSLS-II has scheduled four assessments for calendar year 2010. They will cover safety inspections, equipment inspections, phase hazard analyses, and permits NSLS-II Construction Safety Inspectors are conducting daily safety inspections in accordance with paragraph 3.3.1.1 of the NSLS-II ES&H Management Plan, NSLS-II Project Procedure LT-ESH_P-00013, Safety Inspections, and BSA’s Construction Safety Subject Area. Construction Safety Inspection (CSI) reports are being generated. However, not all findings are being documented on the CSI; some are being verbally transmitted to Torcon, while others are being communicated via e-mail. In addition, the BSA Contractual Representative was not notified of the findings and thus did not issue a Notice of NonCompliance to Torcon as required by Attachment A, Article 43 (g) of the Contract. As a result, CSI’s generated by the NSLS-II staff were not properly processed or completed as required by BSA’s Construction Safety Subject Area and the Contract.
Results of Analysis Considering the number of elements in the NSLS-II ES&H Program and the scheduled completion of this contract in April 2012, the Accident Investigation Committee determined that the current assessment schedule is inadequate to review all program elements in a timely manner to proactively identify and correct deviations. The Accident Investigation Committee has also determined that NSLS-II failed to ensure full implementation of the NSLS-II ES&H Program by not identifying Torcon’s deviations from NSLS-II ES&H Program requirements as explained in section 3.5.1. Though this failure is not a cause for this accident it does weaken the ES&H Program and can lead to missed opportunities to proactively identify and correct minor problems before they become severe. Contributing Cause Statement (CCW-4): NSLS-II failed to ensure that the NSLS-II ES&H Program was performing as designed. •
•
• • •
Draft
NSLS-II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract. NSLS-II’s oversight of Torcon’s implementation of Section 7.1 of the NSLS-II Construction HASP and Section 11 of Torcon’s SHE Program did not identify and correct shortcomings in PHA implementation, such as the lack of specificity, not adequately identifying hazards, and new workers not reviewing and signing PHA’s. NSLS-II’s oversight did not reveal that daily and frequent inspections by Torcon and its subcontractors were not being performed. NSLS-II’s oversight did not identify and correct the use of suspect shackles and wire clips (no manufacturer's name or stamp) found several times over several days on the site. The NSLS-II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations. 46
December 4, 2009
BNL NSLS-II Accident Investigation
3.6
INTEGRATED SAFETY MANAGEMENT
The Accident Investigation Committee examined Management Systems as potential contributing and root causes of the event and the overall NSLS-II ES&H program in terms of Integrated Safety Management (ISM). At BNL, the ISM Program Description describes BNL’s approach to integrating Environment, Safety, Health, and Quality (ESH&Q) requirements into the processes for planning and conducting work at the Laboratory. It also describes BNL's programs for accomplishing work safely and provides a road map of the systems and processes that make up the BNL Integrated Safety Management System (ISMS). The ISMS Program is accomplished by employing an integrated set of non-overlapping Management Systems that embody the requirements defined in the DOE ISMS Manual. These systems collectively form the Standards-Based Management System (SBMS) Management Systems, BNL's highest level of operating and business processes that define how work is conducted at the Laboratory. These Management Systems are defined via Management System Descriptions that identify each system's processes, standards of performance, external requirements, and the set of Laboratory procedures and guidelines (Subject Areas and other Laboratory-wide procedures) to carry-out the elements of each system. Management Systems, Program Descriptions, and Subject Areas operate in an integrated fashion by providing programs and procedures that implement the Plan, Do, Check, Act framework. The Core Functions and Guiding Principles of ISM are the primary focus for BNL and its contractors in conducting work efficiently and in a manner that ensures the protection of workers, the public, and the environment. Properly implemented, ISM is a standards-based approach to safety, requiring rigor and formality in the identification, analysis, and controls of hazards. The five Core Functions of ISM are defining the work, analyzing the hazards, developing and implementing controls, performing work safely, and feedback and improvement. How failure of these core functions apply to the accident is discussed in detail in the following sections. Using ISM’s Core Functions and Guiding Principles, each phase of the work related to the accident was analyzed. In addition, ISM’s Core Functions and Guiding Principles were also used to examine the ES&H program and evaluate its performance. Attachment A, Article 43 (c) of the BSA/Torcon Contract requires Torcon to perform and manage work in accordance with BSA’s DOE-approved Integrated Safety Management (ISM) Program and to demonstrate through documentation and work practices that its performance of work under the contract: (1) fulfills the scope of work as outlined in the contract; (2) identifies and analyzes specific, task-level hazards associated with the work; (3) develops and implements hazard controls related to the hazards; (4) allows the performance of work within the controls; and (5) provides feedback on the adequacy of hazard controls and continuous improvement in safety management as detailed in their ES&H Plan. Section 4 of Torcon’s SHE Program provides their commitment to integrate safety into every phase of the project, from concept through completion of construction. They plan to achieve this by using the ISM System set forth in the NSLS-II Construction HASP. The following sections are organized using the five Core Functions (CF) and seven Guiding Principles (GP), followed by a brief description of the function and/or principle, and the Accident Investigation Committee’s analysis of Torcon’s and its subcontractor’s performance. While each section below lists only the supporting statements that belong to this particular CF or GP, Table 2 summarizes all the connections between the causes identified and the ISM Core Functions and Guiding Principles.
Draft
47
December 4, 2009
BNL NSLS-II Accident Investigation
The five Core Functions, as defined by DOE P 450.4, Safety Management System Policy, are the following: Core Function 1:
Define the scope of work: Missions are translated into work, expectations are set, tasks are identified and prioritized, and resources are allocated.
Core Function 2:
Identify and analyze hazards associated with the work: Hazards associated with the work are identified, analyzed, and categorized.
Core Function 3:
Develop and implement hazard controls: Applicable standards and requirements are identified and agreed-upon, controls to prevent/mitigate hazards are identified, the safety envelope is established, and controls are implemented.
Core Function 4:
Perform work within controls: Readiness is confirmed and work is performed safely.
Core Function 5:
Provide feedback on adequacy of controls and continue to improve safety management: Feedback information on the adequacy of controls is gathered , opportunities for improving the definition and planning of work are identified and implemented, line and independent oversight is conducted, and, if necessary, regulatory enforcement actions occur.
The seven Guiding Principles, as defined by DOE Manual 450.4-1, Integrated Safety Management System Manual, are as follows: Guiding Principle 1:
Line manager clearly responsible for ES&H: Line management is directly responsible for the protection of the public, the workers, and the environment.
Guiding Principle 2:
Clear ES&H roles and responsibilities: Clear and unambiguous lines of authority and responsibility for ensuring safety shall be established and maintained at all organizational levels within the Department and its contractors.
Guiding Principle 3:
Competence commensurate with responsibilities: Personnel shall possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities.
Guiding Principle 4:
Balanced priorities: Resources shall be effectively allocated to address safety, programmatic, and operational considerations. Protecting the public, the workers, and the environment shall be a priority whenever activities are planned and performed.
Guiding Principle 5:
Identify ES&H standards and requirements: Before work is performed, the associated hazards shall be evaluated and an agreed-upon set of safety standards and requirements shall be established which, if properly implemented, will provide adequate assurance that the public, the workers, and the environment are protected from adverse consequences.
Draft
48
December 4, 2009
BNL NSLS-II Accident Investigation
Guiding Principle 6:
Hazard controls tailored to work: Administrative and engineering controls to prevent and mitigate hazards shall be tailored to the work being performed and associated hazards.
Guiding Principle 7:
Operations authorization: The conditions and requirements to be satisfied for operations to be initiated and conducted shall be clearly established and agreedupon.
3.6.1 GUIDING PRINCIPLES The following three Guiding Principles of ISM cover all five core functions. They are followed by the Accident Investigation Committee’s analysis of their implementation at the NSLS-II construction site. GP 1:
Line management is directly responsible for the protection of the public, the workers, and the environment. Torcon’s SHE Program clearly identifies line management is directly responsible for the protection of the public, the workers and environment. During the course of the investigation, the Accident Investigation Committee observed many good practices that demonstrated NSLS-II, Torcon, and its subcontractors were proactively protecting the public, workers and the environment, and these are noted in Section 5.3.1 of this report. However, it is indisputable that this accident occurred and is therefore an example of failure to fully implementation of GP 1. Table 2 identifies the causes impacted by GP 1.
GP 2:
Clear and unambiguous lines of authority and responsibility for ensuring safety shall be established and maintained at all organizational levels within the organization and its contractors. Interviews conducted by members of the Accident Investigation Committee with subcontractor supervisors revealed that supervisors believe investigations and toolbox training to be the responsibility of the safety staff and not theirs. Additional interviews conducted by the Accident Investigation Committee with Torcon and its subcontractors found that the individual responsible for requesting the Operator submit to a drug and alcohol screening following this accident was not clearly defined.. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. Torcon was not able to produce an organization chart that was in effect at the time of the accident; only copies of their organization chart that were included with their bid-proposal and copies dated after the accident were provided. In addition, a description of the roles and responsibilities for the Torcon Safety Manager was requested and could not be provided. The Accident Investigation Committee also determined that the lack of clear roles and responsibilities is a contributing cause to weaknesses in the implementation of the ES&H Program.
Draft
49
December 4, 2009
BNL NSLS-II Accident Investigation
Contributing Cause Statement (CCW-1): Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels. Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations. Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager. GP 3:
Personnel shall posses the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities. The Accident Investigation Committee determined that the Laborer’s experience and skills were not adequately assessed or validated to ensure they were adequate to perform the work he was assigned. In directing the staging of the rebar at the accident location, the Laborer did not allow himself adequate space to move about the area. This resulted in him tripping over the rebar. Torcon and its subcontractors failed to ensure the Laborer possessed the experience, knowledge, skills and abilities necessary to discharge his responsibilities and therefore implementation of GP 3 was not met; this is a Root Cause of this event.
Root Cause Statement (RCE-1): Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities. Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.
GP 7: The conditions and requirements to be satisfied for operations to be initiated and conducted shall be clearly established and agreed-upon. This GP does not apply until operations are authorized at NSLS-II and therefore does not apply to this investigation.
Draft
50
December 4, 2009
BNL NSLS-II Accident Investigation
3.6.2 DEFINE WORK CF 1:
Laboratory missions are translated into work, expectations are set, tasks are identified and prioritized, and resources are allocated.
GP 4:
Resources shall be effectively allocated to address safety, programmatic and operations considerations. To clearly communicate the construction ES&H requirements, the NSLS-II project team created the NSLS-II Construction HASP, which is included in the contract signed with Torcon. Also included in this contract is Torcon’s responsibility to ensure these requirements are imposed on all of its subcontractors at all levels and tiers. Torcon was required to submit a health and safety plan that meets the requirements of the NSLSII Construction HASP prior to the start of work. Torcon’s Project Safety, Health and Environmental Program (Torcon’s SHE Program) was reviewed by NSLS-II, BSA, and DOE-BHSO safety and health professionals and approved on March 17, 2009. A notice to proceed was transmitted by BSA to Torcon on March 25, 2009. The Accident Investigation Committee determined that CF 1 and GP 4 were clearly defined by BSA and NSLS-II and communicated to Torcon, and that Torcon clearly communicated these to their subcontractors.
3.6.3 ANALYZE THE HAZARDS CF 2:
Hazards associated with work are identified, analyzed, and categorized.
GP 5:
Before work is performed, the associated hazards shall be evaluated and an agreed-upon set of safety standards and requirements shall be established which, if properly implemented, will provide adequate assurance that the public, the workers and the environment are protected from adverse consequences. As previously stated in section 3.5.1 of this report, the Accident Investigation Committee determined PHA’s did not adequately identify the hazards for material handling of rebar due to the lack of specificity
Root Cause Statement (RCE-2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Hazard analyses are required for major phases of the project. However, major phases were not defined.
•
Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”.
Draft
51
December 4, 2009
BNL NSLS-II Accident Investigation
•
Torcon and its subcontractors failed to establish that personnel were ready to perform work by ensuring they were aware and prepared to protect themselves from hazards associated with their work. The Laborer created a staging area for the rebar which was unacceptable.
•
Pre-job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
3.6.4 DEVELOP AND IMPLEMENT CONTROLS CF 3:
Applicable standards and requirements are identified and agreed-upon, controls to prevent/mitigate hazards are identified, the safety envelope is established, and controls are implemented.
GP 5:
Before work is performed, the associated hazards shall be evaluated and an agreed-upon set of safety standards and requirements shall be established which, if properly implemented, will provide adequate assurance that the public, the workers and the environment are protected from adverse consequences.
As previously stated in section 3.5.1, the PHA for the work performed by the Laborer and Operator on the day of the injury was requested, and the Accident Investigation Committee was provided with a Macedos PHA entitled All Footings, revised 6/29/09. This PHA did not include the signatures of the Laborer and the Operator, as required by Torcon’s SHE Program. Pre-job briefings witnessed by members of the Accident Investigation Committee during the course of the investigation did not include a discussion of the hazards of the work to be performed. These briefings primarily concentrated on what work needed to be performed and not how to perform the work or identify the associated hazards. There was no evidence that the Laborer and Operator took part in a pre-job brief that identified specific job hazards. In addition, these observations are supported by Macedos’ Safety Manager, who stated that PHAs are used during pre-job reviews conducted by Supervisors with their workers to identify and mitigate/reduce hazards. This is usually not repeated for routine, ongoing tasks, such as moving rebar. Communication between equipment operators and laborers was observed to be effective throughout the site, and there was no sign of miscommunication. However, members of the Accident Investigation Committee observed the following: no evidence of uniform use of standard hand signals on site, even within the same craft of workers; and no discussion or coordination of hand signals between work crew members. This included crew members from different employers who work together on the same job task. Although the Accident Investigation Committee determined that hand signals did not contribute to this accident, the coordination of hand signals posses a potential error trap. Reliable and consistent hand signal communication is critical to safe operations. The equipment manufacturer provides hand signals to be used and these should be incorporated into operations. Therefore, the Accident Investigation Committee determined that this control was not adequately implemented. Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses, and Fires, states that anyone involved in a near miss or injury situation may be required to be tested for substance-abuse at the discretion of Torcon or the NSLS-II Project Management. Section 6, Drug-Free Workplace Policy, states the same. In addition, Torcon’s Project Orientation and General Safety & Health Rules, not dated, state under the Principles of the Program, 2 No alcohol or drugs, that post-incident or injury drug and alcohol Draft
52
December 4, 2009
BNL NSLS-II Accident Investigation
testing are performed. Section 10 of Torcon’s Project Safety Orientation Outline, Revision 6: September 2009, also includes the same requirement. As stated in the Accident Description section of this report (see Section 2.1, page 21), the Operator left the site for approximately 30 minutes and then returned for 1.5 hours before leaving for the day at approximately 1200 hours. The Operator had indicated that he was not asked to submit to an alcohol or drug test before he left the site for the day. Torcon’s Project Manager stated that it was after the Operator had left that they realized they wanted to administer a drug test. Macedos then attempted to reach the Operator but were not able to speak to him until later that day. The Operator did return the following day as requested by Torcon to undergo the drug test. The results of the test were negative. Further conversations with Torcon’s Safety Manager revealed that drug and alcohol testing had not been performed as a result of any injury or incident on the NSLS-II site. The Accident Investigation Committee concluded that Torcon failed to fully implement their alcohol and drug testing requirements. The Accident Investigation Committee determined CF 3 and GP 5 was not adequately implemented. Failure to include hazards as part of pre-job briefings is a root cause of this event. Supervision’s failure to review PHAs with workers, use uniform hand signals, and fully implement their alcohol and drug testing requirements is a contributing cause to weaknesses in the implementation of the ES&H Program.
Root Cause Statement (RCE-2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Pre-job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11.
•
Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met.
•
Hand signal usage was not uniform and relied upon the skill-of-the-workers.
•
Torcon failed to fully implement their alcohol and drug testing requirements.
Draft
53
December 4, 2009
BNL NSLS-II Accident Investigation
3.6.5 PERFORM WORK SAFELY CF 4:
Readiness is confirmed and work is performed safely
GP 6:
Administrative and engineering controls to prevent and mitigate hazards shall be tailored to the work being performed and associated hazards. As previously stated in Section 3.6.4., the Laborer failed to verify his readiness to perform the work safely. The Laborer, standing where he did, had not left himself an escape route. As a result, the Laborer put himself in close proximity to the load, which set the scene for the accident. The Accident Investigation Committee determined that the following are examples of failure by Torcon and its subcontractors to implement administrative controls and confirm readiness to work and are therefore contributing causes to weaknesses in the implementation of the ES&H Program: •
The maintenance log in the Lull, which was boldly marked in red “DO NOT REMOVE FROM VEHICLE!!!” was different from the one provided by Macedos’ Risk and Compliance Director. The copy provided contained more information than the one in the vehicle and should therefore have been in the Lull.
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. However, its gauge indicated full.
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, is different from what is actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of less than full implementation of administrative controls.
•
Torcon Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
The maintenance log in the Lull was different from the one provided by Macedos.
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10.
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of failure to implement administrative controls.
•
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Draft
54
December 4, 2009
BNL NSLS-II Accident Investigation
3.6.6 FEEDBACK AND IMPROVEMENT CF 5:
Feedback information on the adequacy of controls is gathered, opportunities for improving the definition and planning of work are identified and implemented, line and independent oversight is conducted, and if necessary, regulatory enforcement actions occur. The NSLS-II ES&H Monthly Meeting is conducted by NSLS-II ES&H staff and is attended by BSA ES&H staff, DOE-BHSO, as well as Torcon to discuss ES&H-related tasks, issues, and solutions. Torcon’s Labor/Management Safety Committee is described in Torcon’s SHE Program, Section 15, Labor/Management Safety Committee. The Safety Committee meets weekly and is attended by a field supervisor or shop steward. The purpose of the Safety Committee is to create two-way communication on safety issues between Torcon and its subcontractors, including inspection findings, near misses or injuries, suggestions for improvement of safety on the job, and any BNL safety concerns. Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses, and Fires, states that injury and incident investigation will be conducted by Torcon’s Safety Manager, the NSLS-II Construction Safety Engineer, and the subcontractor supervisor to identify causes, contributing factors and lessons learned from the incident. Torcon’s SHE Program, Section16, Weekly Tool Box Safety Meetings, states that each week, at the Labor/Management Safety Committee meeting, Torcon’s Safety Manager distributes the topic of the weekly Tool Box Safety Meeting. Each Torcon supervisor is to hold a brief meeting with his workers. The subcontractor supervisor is free to use a different safety topic for the meeting if desired, in order to keep the topics relevant to the work. Documentation of this meeting, including worker signatures, is to be submitted to the Torcon Safety Manager by the end of each week. Torcon had no assessment schedule for the project and relies on job site inspections and walkthroughs, including those with their insurance carrier. Though this process has a value in ensuring that work activities are being adequately performed in the field, the lack of a systematic approach to assessing the health of the implementation of a safety program, or any other program or process, lessens the effectiveness of that program by not providing feedback to ensure all program expectations are being met. As previously stated, Torcon’s Job Site Daily Inspection Records, required per Torcon’s SHE Program, Section 23, Job Site Inspections, were not being completed daily and not completed correctly in most cases. There are many good practices occurring across the site that focus on field operations, as is stated above, and the result is a site that is in good condition, as described in section 5.3.1 and demonstrates that feedback and improvement is partially working. However, though there are many feedback loops that exist and are being executed, the lack of feedback on the performance of the Project’s ES&H programs has lead the Accident Investigation Committee to determine that the implementation of CF 5 is less-than-adequate and is a contributing cause to weaknesses in the implementation of the ES&H Program.
Draft
55
December 4, 2009
BNL NSLS-II Accident Investigation
Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Torcon had no assessment schedule for the project and relied on job site inspections and walkthroughs, including those with their insurance carrier.
•
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Contributing Cause Statement (CCW-4): NSLS-II failed to ensure that the NSLS-II ES&H Program was performing as designed. •
NSLS-II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract.
•
The NSLS-II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations.
Draft
56
December 4, 2009
BNL NSLS-II Accident Investigation
Table 2. Summary of Causes Identified and the Corresponding ISM Core Functions and Guiding Principles.
Cause Root Cause Statement (RCE‐1): Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities.
Affected Core Function (CF) / Guiding Principle (GP)
Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned.
GP‐1 / GP‐3
•
Supervision failed to ensure the Laborer was qualified to perform the work safely.
GP‐1 / GP‐3
Root Cause Statement (RCE‐2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Hazard analyses are required for major phases of the project. However, major phases were not defined.
•
Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”. Torcon and its subcontractors failed to establish that personnel were ready to perform work by ensuring they were aware and prepared to protect themselves from hazards associated with their work. The Laborer created a staging area for the rebar which was unacceptable.
•
•
Pre‐job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
CF‐2 / GP‐5 CF‐2 / GP‐1 / GP‐5
CF‐2 / GP‐5 CF‐3 / GP‐5
Draft
57
December 4, 2009
BNL NSLS-II Accident Investigation
Cause Contributing Cause Statement (CCW‐1): Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels. •
Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site.
GP‐1 / GP‐2
•
Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations.
GP‐1 / GP‐2
•
Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager.
GP‐1 / GP‐2
Contributing Cause Statement (CCW‐2): Torcon and its subcontractors failed to ensure implementation of the NSLS‐II ES&H Program and therefore contributed to its weakness.
•
Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers.
CF‐3 / GP‐5
•
Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11. Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met.
CF‐3 / GP‐1 / GP‐5
•
•
Draft
Hand signal usage was not uniform and relied upon the skill‐of‐the‐ workers.
58
Affected Core Function (CF) / Guiding Principle (GP)
CF‐3 / GP‐1 / GP‐5
CF‐3 / GP‐5
December 4, 2009
BNL NSLS-II Accident Investigation
Cause •
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. The maintenance log in the Lull was different from the one provided by Macedos.
•
•
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of failure to implement administrative controls. Torcon had no assessment schedule for the project and relied on job site inspections and walkthroughs, including those with their insurance carrier.
Contributing Cause Statement (CCW‐4): NSLS‐II failed to ensure that the NSLS‐II ES&H Program was performing as designed.
Affected Core Function (CF) / Guiding Principle (GP) CF‐4 / CF‐5 / GP‐6
CF‐4 / GP‐6
CF‐4 / GP‐6
CF‐4 / GP‐6
CF‐5
•
NSLS‐II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract.
CF‐5
•
The NSLS‐II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations.
CF‐5
Draft
59
December 4, 2009
BNL NSLS-II Accident Investigation
3.7
ANALYSIS OF EMERGENCY RESPONSE
Notifications to BNL emergency responders and the NSLS-II Project were made in accordance with NSLS-II Project procedure LT-ESH-P-00012, Reporting Events. When the ambulance crew returned to the Firehouse, the Fire Captains conducted a critique of the NSLS-II emergency response. The results are as follows: •
Fire Rescue personnel, including the EMT, responded directly to the accident site and arrived within 4 minutes of notification.
•
Fire Rescue personnel needed to go to the Motor Pool to pick up the ambulance because it was being serviced. The Motor Pool was notified and had the ambulance out and ready by the time Fire Rescue arrived.
•
The Suffolk County Police Medevac was placed on standby because of the report of a serious injury, but released when it was determined by Fire Rescue that there wouldn’t be a delay in transporting the patient.
•
When Fire Rescue personnel arrived at the NSLS-II site, personnel from Torcon directed them directly to the accident scene; they were highly visible and accurate.
•
The Torcon EMT was already on scene and had initiated patient care.
•
The scene was secure and there was ample room for responding apparatus.
•
Fire Rescue personnel stabilized the patient and prepared him for transportation to the hospital.
•
A notification was sent to the hospital apprising them of the incoming patient and his condition. They had a team ready that met the ambulance when it arrived.
•
A request for an ALS intercept was made and provided to the patient without delay in transportation.
•
The entire operation was conducted very smoothly, quickly, efficiently, and safely.
As indicated above, the ambulance was at the Motor Pool for maintenance. If it had not been available to respond to the accident, Suffolk County Police Medevac or mutual aid could have been utilized to transport the injured to the hospital. Feedback received from the hospital indicated that the emergency response team did an excellent job in stabilizing the fracture and keeping it clean. Torcon’s and BSA’s Fire Rescue response time to the accident site and the subsequent transport of the injured worker to the Hospital was acceptable. The Accident Investigation Committee has determined that the emergency response for this event was acceptable.
Draft
60
December 4, 2009
BNL NSLS-II Accident Investigation
4.0
CONCLUSIONS AND JUDGMENTS OF NEED
The Accident Investigation Committee has concluded that this accident was preventable. The Laborer, standing where he did, had not left himself an escape route. It is less important whether the Laborer signaled correctly, whether the Operator misinterpreted the Laborer’s intentions, or whether it was rebar or mud that impeded the Laborer’s movement. In this regard, the Accident Investigation Committee determined that there was no need to think that any of the people involved were being less than truthful in recounting the events. Memory, especially in the wake of a traumatic event, is “reconstructive,” that is, people try their best to make sense of an impossible series of occurrences. The significant point is that the margin for error was reduced by the Laborer standing in the trajectory of the rebar. Therefore any coincidental mishap would be more likely to result in an injury. It seems reasonable to assume that, as the load was being moved toward him and being positioned over the place where it was to be placed, the Laborer’s attention was entirely on what was in front of him, not on what was at his feet or immediately behind him, and that his focus remained so even as he began to move away from where the load would be placed. There are two root causes to this event. The first is that Torcon and its subcontractors failed to ensure employees were qualified and possessed the experience, knowledge, skills and abilities that were necessary to discharge his responsibilities. The Laborer was assigned work by his supervisor who failed to ensure the Laborer was qualified to perform it. In addition, pre-job briefings did not adequately address the hazards associated with the work being performed. Briefings primarily concentrated on what work needs to be performed, not on the associated hazards. The second root cause was that Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. Hazard analyses are required for major phases of the project. However, major phases were not defined. Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”. In addition, pre-job briefings did not adequately address the hazards associated with the work being performed. Briefings primarily concentrated on what work needs to be performed, not on the associated hazards. Four causes were identified that did not contribute to this event but contributed to weaknesses in the NSLS-II ES&H Program at the construction site. NSLS-II has the potential to achieve best in class if their ES&H Program is fully implemented. The first contributing cause to program weakness was due to poorly defined lines of authority and responsibilities for ensuring ES&H compliance. No one was assigned by Torcon or its subcontractors to determine if drug and alcohol screening needed to be performed after an accident. Line supervisors were not aware of their responsibility to conduct injury investigations and toolbox training, but believed these were the responsibility of the safety staff in contradiction to the Torcon SHE Program. The second contributing cause to program weakness was due to poor oversight by Torcon to ensure their ES&H program was being properly implemented. Examples include not detecting and correcting that (1) new workers were reviewing and signing PHA’s, (2) that not all injuries were being investigated, and (3) that daily job site inspections were not being correctly performed if performed at all.
Draft
61
December 4, 2009
BNL NSLS-II Accident Investigation
The third contributing cause to program weakness was due to a lack of effective suspect/counterfeit program for rigging. Suspect shackles and wire clips were found on the NSLS-II construction site several times over several days by members of the Accident Investigation Committee. In addition, the daily rigging inspection forms provided by Torcon failed to address the inspection of suspect/counterfeit items. The fourth and final contributing cause to program weakness was due to the lack of oversight by the NSLS-II project to ensure their ES&H program was being properly implemented. This included not detecting and correcting that: (1) NSLS-II Construction Safety Inspectors were documenting all findings, (2) PHAs were adequate for the work being performed and were being reviewed by new workers, and (3) daily inspections by Torcon and their subcontractors were not being performed.
4.1
DIRECT, ROOT, AND CONTRIBUTING CAUSES
Based upon the results of the analytical methods described above, the Accident Investigation Committee has identified one direct cause to the event (DCE) and two Root Causes to the event (RCE). In addition, the Accident Investigation Committee, as part of its charter, has identified four causes that contributed to weakening the BSA, NSLS-II, and Torcon ES&H Programs (CCW). For each cause, the analytical method that is its source is identified, using the following codes: Barrier Analysis (BA), Event & Causal Charting (E&CFC), ISM Analysis (ISM), and TapRooT (TR). In addition, a reference to the requirements that the cause applies to is also provided. Table 3. Event causes, summaries, sources, and associated JONs.
DCE No.
Direct Cause of the Event
1
Laborer struck by rebar
RCE No.
Root Cause of the Event
1
Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities.
Summary and Source
JON
Rebar strikes the Laborer’s lower right leg and fractures it. (E&CFC)
1, 2, 5 & 7
Draft
Summary and Source •
Torcon, Macedos, and Rebar Steel supervision failed to 1, 5 & 7 ensure the Laborer was qualified to perform the assigned work safely. (BA, TR, OS, ISM, E&CF)) (Reference: Contract Attachment A, Article 43 (b))
62
JON
December 4, 2009
BNL NSLS-II Accident Investigation
RCE No. 2
Root Cause of the Event
Summary and Source
JON
Torcon and its • Hazard analyses are required for major phases of the subcontractors project. However, major phases were not defined. (OS, failed to ensure ISM) workers were • Hazard analyses failed to identify hazards and lacked aware of detail for the movement and placement of rebar. The foreseeable hazard analysis for materials pick up with a forklift only hazards and addressed “dropping/misplacement pinch points” as a protective hazard and provided the following controls: “flagman measures needed direction/horn warning”, “cordoned off area with caution for their safety. tape”, and “spotter will work with forklift”. (BA, OS, ISM)
2, 5 & 7
• Torcon and its subcontractors failed to establish that personnel were ready to perform work by ensuring they were aware and prepared to protect themselves from hazards associated with their work. The Laborer created a staging area for the rebar which was unacceptable. (ISM, TR) •
Pre‐job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards. (BA, ISM, E&CF)
(References: Contract Attachment A, Article 43 (d)(1), and Torcon’s SHE Program Section 11)
Draft
63
December 4, 2009
BNL NSLS-II Accident Investigation
Table 4. Contributing causes to program weaknesses, summaries, sources, and associated JONs.
CCW No. 1
Contributing Cause (Program Weakness) Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels.
Summary and Source
JON
•
Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. (BA, OS, ISM)
•
Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations. (BA, OS, ISM)
•
Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager. (OS, ISM)
3, 5 & 7
(Reference: Contract Attachment A, Article 43 (b)) 2
Draft
Torcon and its subcontractors failed to ensure implementation of the NSLS‐II ES&H Program and therefore contributed to its weakness.
•
Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers. (BA, ISM, OS)
•
Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11. (OS, ISM)
•
Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met. (BA, OS, ISM)
•
Torcon’s Job Site Daily Inspection Records were not 64
4, 5 & 7
December 4, 2009
BNL NSLS-II Accident Investigation
CCW No.
Contributing Cause (Program Weakness)
Summary and Source
JON
being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases. (BA, OS, ISM)
Draft
•
Torcon’s Project Safety Evaluation forms were not completed correctly and some work periods were missing altogether. Objective evidence was not available to indicate whether these inspections had actually taken place daily as required by the contract. (OS)
•
Torcon failed to detect and correct the use of suspect/counterfeit items used during rigging operations. (OS)
•
Hand signal usage was not uniform and relied upon the skill‐of‐the‐workers. (ISM)
•
Torcon failed to fully implement its alcohol and drug testing requirements. (ISM)
•
The maintenance log in the Lull was different from the one provided by Macedos. (BA, ISM)
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. (BA, ISM)
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of failure to implement administrative controls. (BA, ISM)
•
Torcon had no assessment schedule for the project and relied on job site inspections and walkthroughs, including those with their insurance carrier. (ISM)
•
Toolbox meetings topics were not always germane to the work hazards being encountered in the field. The continuing training program was inadequate. The 65
December 4, 2009
BNL NSLS-II Accident Investigation
CCW No.
Contributing Cause (Program Weakness)
Summary and Source
JON
toolbox training provided was not specific to tasks being performed. (BA, TR) (References: Contract Attachment A: Article 16, Article 43 subsections (d)(1), (d)(2), (f), (k), Torcon’s SHE Program Sections 11, 14, 19, 23, and 38, and NFPA 10) 3
Torcon and its subcontractors failed to implement an effective suspect/counterf eit program for rigging.
•
Suspect shackles and wire clips (no manufacturer's name or stamp) were found several times over several days by members of the Accident Investigation Committee. (OS)
•
Torcon’s SHE Program, Section 38, Rigging Procedures and Inspections, and its associated Daily Rigging Inspection form outlined in Article 38, did not address inspection for suspect/counterfeit items prior to rigging. (OS)
5, 6 & 7
(References: Contract Attachment A, Article 16 and Torcon’s SHE Program Section 38)
Draft
66
December 4, 2009
BNL NSLS-II Accident Investigation
CCW No. 4
Contributing Cause (Program Weakness) NSLS‐II failed to ensure that the NSLS‐II ES&H Program was performing as designed.
Summary and Source
JON
•
NSLS‐II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract. (BA, OS. ISM)
•
NSLS‐II’s oversight of Torcon’s implementation of Section 7.1 of the NSLS‐II Construction HASP and Section 11 of Torcon’s SHE Program did not identify and correct shortcomings in PHA implementation, such as the lack of specificity, not adequately identifying hazards, and new workers not reviewing and signing PHA’s. (OS)
•
NSLS‐II’s oversight did not reveal that daily and frequent inspections by Torcon and its subcontractors were not being performed. (OS)
•
NSLS‐II’s oversight did not identify and correct the use of suspect shackles and wire clips (no manufacturer's name or stamp) found several times over several days on the site. (OS)
•
The NSLS‐II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations. (OS, ISM)
5 & 7
(References: Contract Attachment A, Article 43 (g), BSA’s Construction Safety Subject Area, NSLS‐II ES&H Management Plan paragraph 3.3.1.1, and NSLS‐II Project Procedure LT‐ESH_P‐00013, Safety Inspections)
Draft
67
December 4, 2009
BNL NSLS-II Accident Investigation
4.2
JUDGMENTS OF NEED
Judgments of Need are managerial controls and safety measures believed necessary to prevent or minimize the probability of recurrence. They flow from the causal factors and are directed at guiding managers in developing corrective actions. The Judgments of Need and associated Cause Codes are shown in Table 5.
Table 5. Judgments of Need.
No.
Draft
Judgment of Need
Cause Codes
1
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure workers are qualified and possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities in compliance with (1) Contract Attachment A, Article 43, (2) ES&H program and (3) ISM.
DCE‐1 RCE‐1
2
DCE‐1 There is a need for Torcon and all its subcontractors, at all levels, on RCE‐2 the NSLS‐II construction site, to ensure workers are aware of foreseeable hazards and protective measures for their safety. This includes, but is not limited to defining “major phases” of work to determine when hazard analyses are required, establishing the criteria for acceptance of hazard analyses, discussing hazards and their controls during pre‐job briefings, and ensuring compliance with (1) Contract Attachment A, Article 43 (d)(1), Establishment of Safety Protocols, and (2) Torcon’s SHE Program Section 11, PHAs.
3
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to establish clear and unambiguous lines of authority and responsibility for the implementation the (1) Contract, (2) Torcon’s SHE Program, and (3) other ES&H requirements.
CCW‐1
4
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure all ES&H requirements of the Contract and Torcon’s SHE Program are being adequately implemented. This includes, but is not limited to, the following requirements: • Contract, Attachment A o Article 16, Suspect/Counterfeit Items o Article 43 subsections (d)(1) Establishment of Safety Protocols
CCW‐2
68
December 4, 2009
BNL NSLS-II Accident Investigation
No.
Judgment of Need
Cause Codes
(d)(2) Frequent and Regular Inspections of the Work Site (f) Immediate Notification to BSA’s Contractual Representative of Recordable Injuries (k) Subcontractor’s Compliance with ES&H Requirements of the Contract • Torcon’s SHE Program o Section 11, PHAs o Section 14, Daily Inspections of Heavy Equipment o Section 19, Procedures for Injuries and Near Misses o Section 23, Job Site Inspections o Section 38, Rigging Procedures and Inspections • NFPA 10, Standard for Portable Fire Extinguishers
Draft
There is a need for the NSLS‐II project to provide adequate oversight to ensure that BSA ES&H Contract requirements and the NSLS‐II ES&H programs are being fully implemented. This includes, but is not limited to: • Compliance with Contract, Attachment A, Article 43 (g), Written Notification to Contractor of Non‐compliances • Compliance with BSA’s Construction Safety Subject Area • Compliance with NSLS‐II ES&H Management Plan, paragraph 3.3.1.1, Safety Responsibilities • Compliance with NSLS‐II Project Procedure LT‐ESH_P‐00013, Safety Inspections.
6
CCW‐3 There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to implement an effective suspect/counterfeit program for rigging. This includes, but is not limited to, revising Torcon’s SHE program to reflect inspection of rigging equipment for suspect/counterfeit items prior to use and ensuring there are no unknown suspect/counterfeit items currently in use on the NSLS‐II construction site. There is a further need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure that Contract, Attachment A, Article 16, is being met.
69
DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
5
December 4, 2009
BNL NSLS-II Accident Investigation
No. 7
Judgment of Need
Cause Codes
There is a need for the NSLS‐II project to establish and implement a well structured assessment program to complement field inspections. The assessment program should be designed to ensure all elements of the ES&H program required by the Contract and ES&H Plans are functioning properly. The schedule should be established to ensure elements that support or monitor life protection programs (e.g., LOTO, confined spaces, excavation, electrical safety) are given priority.
DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
Draft
70
December 4, 2009
BNL NSLS-II Accident Investigation
5.0
OTHER ANALYSES REQUIRED BY TEAM CHARTER
5.1
IMMEDIATE RESPONSE TO THE ACCIDENT
This section reviews the response actions taken by NSLS-II and Torcon immediately following the accident. The emergency response to the accident is analyzed in section 3.7. At 0845 hours, in accordance with NSLS-II Project Procedure LT-ESH-P-00012 Reporting Events, Torcon’s Safety Manager called BNL’s emergency number advising of an injury and requesting an ambulance. In parallel, Torcon’s site EMT was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing medical care. When Fire Rescue arrived at NSLS-II, Torcon employees directed Fire Rescue personnel directly to the accident scene where they assumed responsibility for the emergency. Fire Rescue commented that Torcon personnel were highly visible and accurate in their directions. After the injured was placed in the ambulance, Laboratory Protection personnel took control of the scene and secured it. Safety and Health Services personnel started to gather information, i.e., take pictures, measurements and statements. NSLS-II and Torcon personnel took the following actions the day of the accident: •
NSLS-II held a fact finding meeting with Torcon, Macedos Rebar Steel, and S&HSD. The Laborer was at the hospital and did not attend, the Operator had left for the day prior to the fact finding meeting. However, he returned the following day and S&HSD personnel obtained his statement.
•
A standdown was held the day of the accident to inform all workers of the event.
•
All rebar mechanical material handling activities were suspended and were not allowed to re-start without the approval of the NSLS-II Project Director.
NSLS-II and Torcon Personnel took the following actions the first several days following the accident: •
Torcon developed toolbox training on material handling and hazards associated with rebar.
•
NSLS-II and Torcon started holding daily ES&H meetings to discuss activities planned for the day as well as safety issues and responses by Torcon.
•
Torcon’s Corporate Safety Manager increased his weekly presence at the NSLS-II site.
•
Torcon started working with the subcontractor (Macedos, employer of the injured) on training topics.
•
BSA and Torcon started developing PHA’s for off-loading and moving rebar on site.
•
Torcon developed and started implementing a preliminary version of their corrective action plan prior to the completion of this report.
Draft
71
December 4, 2009
BNL NSLS-II Accident Investigation
5.1.1 DISCUSSION/RECOMMENDATIONS The procedures established in BSA’s Contractor Vendor Orientation and Torcon’s site orientation were followed and notifications were made swiftly. Within minutes of the injured being removed from the incident site, the scene was promptly secured by BNL Laboratory Protection and data collection was started, including statements from those in the area, photographs, measurements, and a fact finding meeting. These data provided the baseline for this investigation. Sr. Project Management’s walk down of the site and calling for a stand down to inform workers of the event and the implementation of immediate corrective actions, even before the investigation was completed, demonstrated their concern for the safety of all workers on site. The Accident Investigation Committee determined that NSLS-II and Torcon’s response to this event was acceptable.
5.2
SAFETY INCENTIVE PROGRAM
Though the Safety Incentive Program did not have any impact on this accident, it is part of the Accident Investigation Team’s Charter to review the adequacy of contractual safety requirements and the safety incentive program. BSA has designed a safety incentive to motivate Torcon to strive for continuous improvement and perform at a best-in-class level. This is reflected in Article 44, Safety Incentive, of the Contract. The safety incentive is based on three factors: 1. Accident/Injury Rates (Days Away, Restricted, Transferred (DART) Rate and Lost Work Day (LWD) case rates; 2. Serious violations of OSHA requirements; 3. Responsiveness to less serious OSHA violations. The DOE construction average for DART and LWD case rates are used to determine the award. The DART rate will be based on the rates for the most recent full year as presented in the DOE Computerized Accident, Incident Reporting System (CAIRS) database. The value of the safety incentive for the term of the Contract is set at two million Dollars. This earned incentive is to be paid by BSA to Torcon for superior safety performance over and above the contract price and is to be awarded as follows: • •
Up to five hundred thousand Dollars to be awarded annually 3 times, on the anniversary date of BSA’s Notice to Proceed, over the length of the contract; A final incentive of up to five hundred thousand Dollars when the contract is completed.
Work related illness and injuries are defined in 29CFR 1904, Final rule, the OSHA record keeping guidelines for Occupational Injuries and Illnesses, effective January 1, 2002.
Draft
72
December 4, 2009
BNL NSLS-II Accident Investigation
The basis for the award is as follows: •
• •
•
The first award will be made on the basis of DART and LWD case rates at the end of the first year following BSA’s Notice to Proceed. An additional award will be made each succeeding year for a maximum of three annual awards. Annual awards are not cumulative. No award will be made if the DART rate or LWD rate for the combined Contractor and subcontractor (working on site) rate is greater than the construction average from DOE’s CAIRS. Fifty percent of the maximum award will be granted if the DART rate and LWD rate for the combined Contractor and subcontractors at the site is less than or equal to the DOE construction annual average from CAIRS for the DART rate and three year rolling average for the LWD rate. Additional award is earned based on the percentage difference below the DOE average LWD rate only, reaching 100% at 50% of the DOE average LWD rate.
There will be a five thousand Dollar reduction of the earned annual award for each significant instance of OSHA violations, including but not limited to: • • • • • • • •
Any worker not properly using appropriate fall protection systems. Entry into a confined space without a required confined space permit or violation of permit requirements. Failure to use, when required, the Lock-out Tag-out procedures, as approved in Torcon’s Safety Plan. Any work on or near energized parts without a required Energized Electrical Work Permit or violation of permit requirements. Failure to report a recordable work related injury or illness to NSLS-II ES&H. Any fire caused by insufficient or inadequate fire protection measures. Excavation without required Dig/Penetration permit or violation of the requirements of a Dig Penetration permit. Failure to protect all excavation from cave-ins by adequate protection systems designed in accordance with 29CFR 1926.652.
In addition, there will be a five thousand Dollar reduction of the earned annual award for lack of responsiveness to less significant issues called to the attention of Torcon, including but not limited to: • • • • •
Repeated violations of any worker not wearing personal protective equipment, as required in Torcons’ safety plan. Repeated housekeeping issues at the job site, Repeated use of defective hand tools, power tools, extension cords, etc. Smoking in violation of the no-smoking policy, Repeated traffic violations issued on the BNL site.
There will be no annual award regardless of rates if there is a fatality, loss of limb, or an injury to the head resulting in permanent disability, at the work site. Determination of incentive award reductions will be made by the NSLS-II ES&H Manager. The final award will be made on the basis of cumulative injury rates over the time period of the conventional construction.
Draft
73
December 4, 2009
BNL NSLS-II Accident Investigation
There will be no award if the average DART Rate or LWD rate for Torcon including all subcontractors working at the site over the duration of the project is greater than CAIRS construction average for DART and LWD rates for the same period. Fifty percent of the final award will be granted if the DART Rate and LWD rate for Torcon and all subcontractors working at the site over the duration of the project is less than or equal to DOE construction average for DART and LWD rates for the same time period. Torcon’s SHE Program, Section 26, Safety Incentive Programs for the Project, Revision 3, dated June 9, 2009, outlines the potential distribution of any earned incentive as follows: 50% to the Union tradesmen, apportioned to the workers based on their man hours worked during the incentive period; 20% to the subcontractor company; and 5% to Torcon’s field supervision. The remaining 25% will be distributed to Torcon. Any workers or subcontractor companies receiving a violation during the incentive period will be disqualified from receiving the safety incentive payment. Torcon has also implemented short-term incentives or rewards programs for outstanding safety leadership or compliance. Torcon’s Labor/Management Safety Committee provides input into what programs are to be offered. Torcon uses these programs to reward workers and supervisors for showing the extra diligence and professionalism it takes to achieve high levels of safety. Torcon’s Project Orientation and General Safety & Health Rules pamphlet that is reviewed with all new employees does not mention the safety incentive program. However, Torcon’s Project Safety Orientating Outline includes a flyer called “Safety Pays”. This document briefly describes the safety incentive agreement with BSA and informs the workers that it is conceivable that a 100% incentive award earned with no workers being disqualified, could result in an average award of six thousand Dollars per tradesman, with some awards being much higher for tradesmen that are on the Project for the full three year duration. It further states that, even if you are no longer on the job, Torcon will pay any earned bonus Dollars directly to you, not your employer. Field workers were interviewed on their knowledge of the Safety Incentive Program. Many workers were aware of Torcon’s $50 gift card incentive, which is separate from the safety incentive program in the Contract. However, this too was not mentioned in Torcon’s Project Orientation, pamphlet, or SHE Program. Workers interviewed were not aware of the NSLS-II Safety Incentive Program. The NSLS-II construction workforce is partly made up of transient local Union trade workers, who, at the end of their particular phase of the work, will move on to other projects. The Accident Investigation Committee determined that the transient nature of the workers creates a situation where long-term buy-in is difficult to achieve. Short-term incentives can produce the desired results, if properly applied, promoted, and effectively delivered to the worker.
Draft
74
December 4, 2009
BNL NSLS-II Accident Investigation
5.2.1 DISCUSSION/RECOMMENDATIONS The Safety Incentive Program had no impact on this accident. It is extremely difficult for the Accident Investigation Committee to determine if the Safety Incentive Program, as stated in the Contract, has had an influence in improving safety considering the injuries that have occurred on the NSLS-II site to date. The Safety Incentive Program, as stated in the Contract, only indicates what awards will be paid out by BSA to Torcon. It is up to Torcon to determine how best to distribute the award to achieve the desired outcome. The Program is results oriented with only punitive actions for behavior, i.e. the loss of award monies as stated above. Torcon has indicated in their SHE Program how the award will be disbursed to workers. However, workers’ awareness of this program is low. Torcon has an incentive program of their own, used on this and other sites they manage, that rewards workers on the spot when observed working safely. It can be stated that the BSA Safety Incentive encourages this program on site. It is recommended that more emphasis be placed on informing workers of the safety incentive program, from the time when they start working on site and continuing throughout the project. Information concerning safety incentives could be added to Torcon’s Project Orientation and General Safety & Health Rules pamphlet, orientation outline, and as a toolbox topic. There were many discussions with the NSLS-II Safety team with respect to slow and sometimes nonresponsiveness from safety individuals working for Torcon. This was also witnessed by the Accident Investigation Committee. The Contract states that lack of responsiveness to less significant issues brought to Torcon’s attention will result in a five thousand Dollar reduction in the annual award per event. Torcon should be reminded of this and BSA should consider raising this amount for repeat occurrences and providing immediate feedback of any award reduction that will be taken. The use of gift cards, state lottery tickets, or theater tickets may allow the monetary incentive to effectively reach the field worker who will be on site for a short time. These incentives could be given to all employees on site during a particular week, or other short period of time, where no accident occurs.
Draft
75
December 4, 2009
BNL NSLS-II Accident Investigation
5.3
REVIEW OF CONSTRUCTION SAFETY PROGRAM IMPLEMENTATION
5.3.1 FIELD OBSERVATIONS During the course of this investigation, Accident Investigation Committee members who are professional construction safety inspectors, conducted site observations and interviewed workers. While conducting approximately 500 observations over seven days they did not observe any human performance safety deficiencies. In addition to the other findings identified previously in this report they made the following determination with respect to the implementation of the NSLS-II Construction Safety Program on the construction site:
there was a high degree of PPE compliance;
housekeeping was good;
environmental controls were effective;
all hardhats carried the BNL emergency number;
discussions with field workers indicated a positive attitude towards participating in efforts to make the site safe;
material staging and storage areas were well organized;
construction equipment appeared to be in good operating condition;
paths of travel for equipment were well established;
scaffolding was erected properly;
excavation practices were adequate.
5.3.2 ADEQUACY OF TORCON’S SAFETY PLAN IMPLEMENTATION AND FLOWDOWN TO SUBCONTRACTORS The Accident Investigation Team has determined that Torcon has adequately flowed down the requirements of its safety plan to subcontractors. However, Torcon failed to implement their SHE Program plan. The causes identified in Table 4 under Contributing Causes (Program Weakness) provide the basis for this determination.
5.3.3 ADEQUACY OF BNL OVERSIGHT OF TORCON’S SAFETY PROGRAM The Accident Investigation Team has determined that NSLS-II’s oversight failed to identify and correct all weaknesses in Torcon’s SHE Program plan. The causes identified in Table 4 under Contributing Causes (Program Weakness) provide the basis for this determination.
Draft
76
December 4, 2009
BNL NSLS-II Accident Investigation
5.3.4 RECOMMENDATIONS TO IMPROVE OVERALL CONSTRUCTION SITE SAFETY The ES&H requirements established by the NSLS-II Project, the Contract, and Torcon, provide a program that has the potential to produce a best-in-class performance.
Each element of this program plays an important and integral part in achieving the desired results and can be compared to a cable used for structural support. Each program element is like a strand within the cable. Taken together, each strand contributes to a cable’s functional design. The impact of a broken or weakened strand may not be evident at the beginning of cable use. However, as factors such as time, wind, sun, and structural load, start to impact the cable, the importance of each wire becomes more evident. As a result, detailed inspections and tests of the cable are conducted, using both visual means to evaluate the surface layers, and other means to ensure the internal layers are to specification. These inspections and tests are periodically repeated through the lift of the cable to ensure it maintains its integrity. Failure of the cable can cause significant results.
Likewise, when an ES&H program is designed, each element plays a part in the overall desired performance of that program. When one of those elements is not fully implemented as designed, or not implemented at all, the program fails to perform as intended. Impact to the program may not be immediately noticed, if noticed at all. However, as time goes on and events occur, these weaknesses may materialize in significant ways that cannot always be predicted. To prevent this from occurring, structured audits are required. Field inspections play an important part in ensuring the surface results, i.e., behavioral performance, is as expected, but they fall short in identifying internal elemental performance that is not as easily identified. This is why the Accident Investigation Committee recommends a well structured assessment program to complement the field inspections. The assessment program should be designed to ensure all elements of the ES&H program required by the Contract and ES&H Plans are functioning properly. The schedule should be established to ensure elements that support or monitor life protection programs (e.g., LOTO, confined spaces, excavation, electrical safety) are given priority. Finally, adequate resources must be provided to support the schedule.
Draft
77
December 4, 2009
BNL NSLS-II Accident Investigation
5.4
NON‐ACCIDENT INVESTIGATION JUDGMENT OF NEED ‐ HIPAA
The Accident Investigation Committee identified an additional need concerning the Health Insurance Portability and Accountability Act (HIPAA). HIPAA was enacted by the U.S. Congress in 1996. Title II of HIPAA, known as the Administrative Simplification (AS) provisions, defines numerous offenses relating to health care and sets civil and criminal penalties for them. It also creates several programs to control fraud and abuse within the health care system. On several occasions, the Accident Investigation Committee came in contact with BSA employees who stated they could not talk to the Committee about the incident due to HIPAA requirements and their fear of violating them. The Committee asked questions regarding the type of fracture, its location, and general medical care provided. At one point, members of the Committee were informed by a BSA employee that we could not ask the injured any questions about his injury due to HIPAA. Although this point was clarified by BNL’s legal department (yes, the Injured can talk about his injury), and HIPAA did not prevent us from completing our investigation, it did identify a need for BSA to develop and provide training on HIPAA as it applies to injuries and investigations on site. This would aid future investigations by providing clear instructions to all involved and ensure the HIPAA requirements are properly executed across the site.
Draft
78
December 4, 2009
BNL NSLS-II Accident Investigation
6.0
ACCIDENT INVESTIGATION COMMITTEE SIGNATURES
Draft
79
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX A
Draft
ACCIDENT INVESTIGATION COMMITTEE CHARTER
80
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
81
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX B WAIVER
Draft
82
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX C SUMMARY OF INTERVIEW STATEMENTS The following is a compilation of the statements obtained about the accident from the Laborer, Operator, and Worker 2, arranged in chronological order. Similar statements are combined for brevity. Dissimilar statements are both included and appropriately annotated. The Accident Investigation Committee’s reconstruction of the accident is provided in Section 2.1.2, Description of the Accident, page 25. On September 30, 2009, the Lull Operator employed by Macedos started work at approximately 0700 hours by working with carpenters to move material. At approximately 0815 hours, the Laborer, employed by Rebar Steel, asked the Operator to move some rebar, as directed by the Rebar Steel foreman that morning. The Laborer was directing the placement of the rebar load. The Operator and Laborer were moving bundles of rebar from the laydown area to an area where they could be hoisted with the crane. The Operator stated that he and the Laborer moved 6 to 7 loads of rebar before moving to the area where the incident occurred. The Laborer marked the rebar bundles to be moved by spraying them with orange paint. The Operator had previously worked with this Laborer and others before this day. The Laborer stated that on several previous occasions (not on the day of the accident) the Operator misread the Laborer’s hand signals and operated the Lull in a manner not expected by the Laborer. The Operator indicated there are several hand signal methods used on site and he had no problem with any of them. The Operator did not have any problem understanding the Laborer’s signals. The Laborer had never complained to the Operator about not following his signals. The Operator indicated to the Accident Investigation Committee that the Lull was in good working condition and he had no problem with it. The Operator also indicated to the Accident Investigation Committee that there was no unusual pressure placed upon him to get the job done. The Operator stated that the incident occurred with the first rebar bundle moved to the incident area, but the Laborer stated that it was the third bundle moved to the incident area. Both Operator and Laborer stated they were moving one bundle at a time. The responsible supervisor and Worker 2 indicated to the investigation team that there were two bundles being moved. At approximately 0835 hours, Worker 2 saw the Operator and Laborer placing a load of rebar onto the ground between two other loads of rebar already on the ground. The Operator stated that the Laborer was standing on several bundles of rebar approximately 5 feet in front of the forks of the Lull. The Operator stated that he was being guided by the Laborer who signaled the Operator to land the load. The Operator stated that the Lull was stopped prior to the load being placed. The Operator stated the Laborer directed him to drive over a bundle of rebar that was located at the incident area. The Operator stated that he had no problems with visibility; he was able to clearly see the Laborer at all times. The Laborer stated that he was facing the Lull and had indicated, using hand signals, for the Operator to stop movement, but the Operator stated that the Laborer had indicated for him to lay down the load while the Laborer was standing on a stack of rebar approximately 5 feet from where the load was to be dropped. Worker 2 stated that he saw the Laborer turn away as if he was going to get out of the way so the load could be placed, but also later stated to the investigation team that he did not see the incident. Draft
83
December 4, 2009
BNL NSLS-II Accident Investigation
The Operator stated that the Laborer, facing the Lull, backed up to move out of the way of the rebar, at the same time the Operator was in the process of placing the load. The Operator stated that the boom of the Lull was extended to permit the load to be placed in the area indicated by the Laborer. The Laborer stated that he was in the process of backing up out of the way when his right foot got stuck in the mud. As he was trying to move his foot, the Operator continued to move and lower the bundle of rebar. The Laborer was able to get his left foot out of the way, but the bundle of rebar rolled off the forks of the Lull and struck his right leg, resulting in the injury. The Laborer was facing the Operator when the load was placed. Per the Operator, as the load started to slide off the forks, the Laborer slipped off the bundles of rebar he was standing on into a sitting position and the load came down on his right lower leg. The Laborer stated that the bundle of rebar was not completely off of the Lull forks, some of the rebar was still supported by the forks. The Operator, responding to the Laborer’s screams, removed the rebar from his leg. The Operator stated that he did not remember if he speared or cradled the load off the Laborer’s leg. The Laborer rolled onto his stomach after the load was lifted. The Operator stated that he then exited the Lull and went to the injured. Worker 2 heard screaming and ran over to see the Laborer on the ground face down and the rebar above him, half on the forks of the Lull and the other half off the forks hanging several inches above Laborer’s legs. Worker 2 stated he did not see the incident occur; he was located behind a spoil pile at the time of the incident. When he arrived, the Operator was out of the Lull near the Laborer. At this time, the Operator saw the rebar on the forks and believed them not to be at a safe distance from the Laborer and moved the rebar back further by retracting the boom and by moving the vehicle backwards. After Worker 2 arrived at the scene, the Operator moved the load back further and dropped it to the ground. The Operator stated that he thought the bundle of rebar was still on the forks of the Lull when he moved the Lull back, but the first responding investigators did not find any rebar on the forks. The Laborer stated to Worker 2 while awaiting medical assistance that his foot got stuck in mud as he went to get out of the way of the load, and the rebar hit him.
Draft
84
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX D FOOTNOTES The statements of the people involved in the accident and some witnesses conflict with each other or with physical evidence. The following is the analysis of the statements and evidence that explains the conclusion of the Accident Investigation Committee for the sequence of events. 1 – After the incident the Lull was inspected by both the BNL Hoisting & Rigging Inspector and an equipment technician, and both found the Lull was sound and operating correctly. 2 - The Laborer arranged cribbing in the accident area, including moving a 2 x 4 inch piece of wood approximately 10 feet north to the incident location. There was an impression in the ground in the shape of a 2 x 4 inch piece of wood between the forks of the Lull, where it was located after the accident (Figure 10).
Figure 10. Tire marks and impression in the ground visible in the center, above the bundle of rebar.
3 - The Accident Investigation Committee believes the Operator and the Laborer moved two bundles of rebar, one with a bend and another bundle of ½ inch rebar before the incident bundles were moved. There was one statement by the Laborer that the incident bundle was the third bundle to be moved, and this fits with the placement of two different bundles already in the staging area. There is a bundle of rebar with a bend and a bundle of ½ inch rebar set on cribbing in the staging area (Figures 11 and 12). These would have come from different areas when they were unloaded, as was found in the piles of rebar around the area (Figure 13).
Draft
85
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 11. Staging area (accident location).
Figure 12. Staging area (accident location), including the Lull.
Draft
86
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 13. Rebar storage locations.
4 - There are two bundles of 1 ¼ inch rebar south of the other two bundles in the staging area. They are both marked with orange paint, and nearest to the forks of the Lull as it was found after the accident. The Laborer and Worker 2 both state that the rebar was partly on the forks of the Lull after it struck the Laborer. Two bundles would have that same appearance. The combined weight of the two bundles, 4,934 pounds, would still be within the capacity of the Lull at 18 feet of boom extension. 5 - The Laborer was found lying over and between two piles of rebar. The Laborer was reportedly 6 feet 2 inches tall (74 inches), and the distance between the rebar pile on which the laborer’s head was located post-accident, and the bundles of rebar in the staging area measured 59 inches. The two bundles of rebar in the staging area measured 24 inches wide. The Laborer also stated that his foot was stuck in mud. He could only make this statement if he knew he was standing on ground as opposed to standing on rebar immediately before the accident, as stated by the Operator. 6 - This conclusion is based upon Figures 8 and 14. One may easily see that an elevated load would block the view of the Laborer’s lower body while standing in the location in front of the staged rebar. 7 - The boom of the Lull was found at approximately 13 feet after the accident (see Figures 12 and 15). The Operator stated that he moved the load by retracting the boom and backing the vehicle. The capacity limit for the Lull is 5,000 pounds at approximately 18 feet. A load of 2,467 pounds for one bundle, or a load of 4,934 pounds for two bundles, was well within this rated capacity.
Draft
87
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 14. Operator’s view.
Figure 15. Load chart for Lull.
8 - This conclusion is drawn from the Operator’s and Laborer’s statements that the Laborer was facing the Lull at the time of the accident, and the Operator’s and Laborer’s statements that the Laborer was in the process of backing up at the time of the accident. During the second interview with Worker 2 he Draft
88
December 4, 2009
BNL NSLS-II Accident Investigation
stated that he did not see the accident occur. His observations were before the accident occurred and afterwards. Worker 2 stated he was behind the spoil pile at the time the Laborer was screaming. The spoil pile is the large mound of dirt visible in Figure 16. The crane is visible behind the spoil pile. Finally, the Accident Investigation Committee believes that the Laborer gave a “down” or “tilt down” signal to the Operator in anticipation that he would be out of the way of the load in a couple of steps. The Laborer, however, tripped or was otherwise stopped in his retreat by the rebar behind him. The Accident Investigation Committee reached this conclusion considering several facts or the lack thereof. The Operator has several operating engineer licenses and training certificates, as well as many years of construction site experience. The Laborer, however, has mostly yard experience and non-material handling construction experience, and no licenses or operating engineer training, as evidenced by the letter of “experience” provided by Rebar Steel Corporation. The Laborer’s statement regarding the Operator’s previous unexpected response to hand signals is not evidenced by other means. The Laborer did not tell anyone else of these experiences, and construction site management has no record or recollection of this issue. The Operator states he had previously worked with the Laborer and others before the day of the accident and had no trouble understanding the Laborer’s signals. The Operator indicated there are several hand signal methods used on site and he had no problem with any of them. As a crane operator as well as a forklift operator, the Operator would have had training and experience with different signals. The Accident Investigation Committee also evaluated the crane and forklift hand signals and does not believe that a crane stop signal could be misinterpreted as a tilt hand signal. Members of the Accident Investigation Committee have seen the crane stop signal used on the construction site.
Figure 16. The spoil pile is visible at the back of the photo.
9 - The Laborer states his foot became stuck in mud as he was backing. The members of the Accident Investigation Committee that responded to the accident site within an hour of the accident did not find mud at the accident site (see Figure 9). The precipitation report for the month of September shows that there were 1.39 inches of precipitation on September 27, 2009 and 0.12 inches of precipitation on September 28, 2009 (see Appendix I). The area of the accident has been significantly excavated and reshaped, and the normal soil for the entire Long Island area as well as the site is Class C or sandy soil. In addition, there was 0.74 inches of precipitation on October 3, 2009, and the Accident Investigation Draft
89
December 4, 2009
BNL NSLS-II Accident Investigation
Committee did not find any evidence of viscous mud that would trap an individual’s footwear. The rebar was slightly elevated and narrow in diameter, and its contact with the Laborer’s footwear might feel like the foot was stuck, but lateral motion would still be possible, hence the statement by the Laborer that he was able to get his left foot out of the way. (See also Figures 11 and 16.) 10 - This is evidenced by the broken cribbing at the accident site (see Figure 17), the position of the forks post-accident, the fact that the Operator could not immediately stop the load when he saw the Laborer slip, and the Operator’s statement that the load was sliding off the forks.
Figure 17. Broken cribbing.
11 - The Accident Investigation Committee came to this conclusion in order to explain the statement by the Laborer that the rebar was partly on the forks of the Lull after it struck him. This the Laborer would have seen before the Operator lifted the rebar from his leg. The Laborer also rolled onto his stomach after the rebar was lifted off his leg, therefore he might not have seen the rebar partially on the forks and partially off the forks when it was suspended above him, as the Operator and Worker 2 had seen. 12 - See Figures 10, 18, and 19. The bundles are identical, and the remnants of the wire tie are visible in the photographs. 13 - This is the statement by Worker 2, and is consistent with the statement by the Operator. 14 – The photographs show the Lull in a location after the accident that is away from the accident site. (The photographs show neither the load nor the Lull in a location that would contact the Laborer, who was located north of the Lull at the location of the staged rebar bundles.) Fresh tire marks are found in the soil leading from the incident rebar bundles to the Lull in its as-found location (see Figure 10).
Draft
90
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 18. Broken center wire tie visible in bundle on the right-hand side.
Figure 19. Broken center wire tie visible in bundle in front of photograph.
Draft
91
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX E BARRIER ANALYSIS OF THE ACCIDENT (PHYSICAL AND ADMINISTRATIVE) Each barrier failure is keyed to Tables 3 and 4 in Section 4.0 (see p. 62), which summarize the event causes, provide the analytical technique that was used to establish the cause, and identify the associated Judgment of Need. The codes used are as follows: Direct Cause (DC), Root Cause (RC) and Contributing Cause to Program Weakness (CCW). Numbers following the codes indicate the specific causal factor.
Part 1: Physical Hazard: Mechanical Impact
Target: Laborer
How did the barrier perform?
Why did the barrier fail?
How did the barrier affect the accident?
Functioned as designed
Did not fail
Had no effect on accident
Functioned
Did not fail
Had no effect on accident
Appropriate soil (type & condition)
Functioned
Did not fail
Had no effect on accident
Appropriate grade
Functioned
Did not fail
Had no effect on accident
Appropriate weather conditions
Functioned
Did not fail
Had no effect on accident
Good housekeeping
Functioned
Did not fail
Had no effect on accident
Failed
Inadequate area for safest movement by Laborer
Created tripping hazard (RCE-2)
What were the barriers? Tools & Equipment Design/operation of Lull Maintenance of Lull Environment
Area staging
Draft
92
December 4, 2009
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact
What were the barriers?
Target: Laborer How did the barrier affect the accident?
How did the barrier perform?
Why did the barrier fail?
Pre-job brief / Job planning
Failed
Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
Missed opportunity to identify and address hazards (RCE-2)
Qualifications
Failed
Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned.
Enabled creation of hazardous condition (RCE-1)
Skills (ability to do job as intended)
Failed
Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned.
The Laborer put himself in close proximity to the load, which resulted in the accident. (RCE-1)
PPE
Functioned
Did not fail
Had no effect on accident
Communication (e.g., hand signals, language skills) †
Functioned
Did not fail
Had no effect on accident
Worker - Laborer
†
See discussion on the use of hand signals in section 3.1.1.
Draft
93
December 4, 2009
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact
What were the barriers?
Target: Laborer How did the barrier affect the accident?
How did the barrier perform?
Why did the barrier fail?
Pre-job brief
Failed
Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
Missed opportunity to identify and address hazards (RCE-2)
Qualifications
Functioned
Did not fail
Had no effect on accident
Skills (ability to do job as intended)
Functioned
Did not fail
Had no effect on accident
PPE
Functioned
Did not fail
Had no effect on accident
Communication (e.g., hand signals, language skills)
Functioned
Did not fail
Had no effect on accident
Worker - Operator
Draft
94
December 4, 2009
BNL NSLS-II Accident Investigation
Part 2: Administrative Hazard: Mechanical Impact What were the barriers?
Proof of Maintenance: Maintenance Log of Lull Proof of Inspection: Fire extinguisher inspection label (I.A.W. NFPA 10)
Torcon Safety Program: Subcontractor Project-Specific Safety Plan
Torcon Safety Program: PHA
Draft
Target: Laborer
How did the barrier perform?
Why did the barrier fail?
Failed
The maintenance log in the Lull was different from the one provided by Macedos.
Failed
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases. Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers.
Failed
Failed
95
December 4, 2009
How did the barrier affect the accident? Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2) Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2)
Had no effect on accident. However, weakens the ES&H program by less than full implementation (CCW-2)
Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2)
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact What were the barriers?
Torcon Safety Program: Hazard Analyses
Torcon Safety Program: Heavy Equipment Inspection Records
Torcon Safety Program: Injury/Incident Investigations
Draft
Target: Laborer
How did the barrier perform?
Why did the barrier fail? Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”. Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used.
Failed
Failed
Torcon’s failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires
Failed
96
December 4, 2009
How did the barrier affect the accident?
Hazard analysis did not specifically address material handling of rebar (i.e., material handling by Lull for concrete work on foundation), which is a major phase of this project. (RCE-2)
Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2) Had no effect on accident, however weakens the ES&H Program by less than full implementation and missing opportunities for improvement (CCW-2)
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact What were the barriers?
Torcon Safety Program: Post Drug and Alcohol Screening
Torcon Safety Program: Injury/Incident Investigations
Torcon Safety Program: Training
Draft
Target: Laborer
How did the barrier perform?
Why did the barrier fail? Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit for a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. Supervisors not participating in investigations and believe the investigations are the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for participating in injury investigations. Supervisors believe toolbox training to the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes.
Failed
Failed
Failed
97
December 4, 2009
How did the barrier affect the accident?
Had no effect on accident. However, weakens the ES&H Program by less than full implementation. (CCW-1)
Had no effect on accident, however weakens the ES&H Program by Line abdicating safety responsibilities to safety staff (CCW-1)
Had no effect on accident, however weakens the ES&H Program by Line abdicating safety responsibilities to safety staff (CCW-1)
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact What were the barriers?
Target: Laborer How did the barrier affect the accident? Had no effect on accident, however weakens the ES&H Program by less than full implementation, loss of trending data to measure performance of program, and possibly less than adequate corrective actions and follow up. (CCW-2)
How did the barrier perform?
Why did the barrier fail?
Torcon Safety Program: Daily Job Site Inspections
Failed
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Training on unintentional contact with mobile equipment and personnel
Functioned
Did not fail
Failed
NSLS-II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area, the Contract.
Functioned
Did not fail
Had no effect on accident
Functioned
Did not fail
Had no effect on accident
Failed
Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.
NSLS-II ES&H Management Plan: Construction Safety Inspections
Fitness for duty (as required by contract) capability to do task (prearrival drug screening) General, across site: high visibility garments Laborer supervision
Draft
98
December 4, 2009
Had no effect on accident Had no effect on accident, however weakens the ES&H Program by less than full implementation, loss of trending data to measure performance of program, and possibly less than adequate corrective actions and follow up. (CCW-4)
Staging crowded resulting in a trip hazard (RCE-1)
BNL NSLS-II Accident Investigation
APPENDIX F TAPROOT® ANALYSIS
Two Causal Factors were identified from the TapRooT® Analysis: •
Laborer in close proximity to load, and
•
Rebar Layout (staging) Less Than Adequate.
TapRooT defines Causal Factors as any problem associated with the incident that, if corrected, would have prevented the incident from occurring or would have significantly mitigated its consequences. Each TapRooT cause that was identified for the Causal Factor analyzed is keyed to the causal table found in section 4.0. The codes used are as follows: Direct Cause (DC), Root Cause (RC), and Contributing Cause to Program Weakness (CCW). Numbers following the codes indicate the specific causal factor found in Tables 3 and 4. This Appendix contains the Root Cause Trees that resulted from the analysis.
TAPROOT RESULT SUMMARY Causal Factor: Laborer in close proximity to load Training Understanding Needs Improvement (NI) Instruction NI - Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned. (RCE-1) Testing NI - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. The Laborer had a skill and knowledge deficiency that should have been caught by verification and corrected before allowing him to perform this work. Lack of verification failed to ensure mastery of required skills, knowledge, and abilities to necessary perform the work. (RCE-1) Continuing Training NI - Toolbox meetings topics were not always germane to the work hazards being encountered in the field. The continuing training program was inadequate. The toolbox training provided was not specific to tasks being performed. (CCW-2) Management System Oversight/Employee Relations Audits & Evaluations (A&E) lack depth - Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned. (RCE-1)
Draft
99
December 4, 2009
BNL NSLS-II Accident Investigation
Human Engineering Work Environment Housekeeping NI - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. The Laborer prepared an inadequate rebar staging area, which resulted in a trip and fall hazard. (RCE-1) Work Direction Selection of Worker Not Qualified Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. The Laborer prepared an inadequate rebar staging area, which resulted in a trip and fall hazard. (RCE-1) Causal Factor: Rebar Layout (staging) Less Than Adequate Training Understanding NI Continuing training NI - Toolbox meetings topics were not always germane to the work hazards being encountered in the field. The continuing training program was inadequate. The toolbox training provided was not specific to tasks being performed. (CCW-2) Management System Oversight/Employee Relations Audits & Evaluations (A&E) lack depth - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. (RCE-1) Work Direction Selection of Worker Not Qualified - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.The Laborer prepared an inadequate rebar staging area, which resulted in a trip and fall hazard. (RCE-1)
Draft
100
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
101
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
102
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
103
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
104
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX G EVENTS AND CAUSAL FACTORS ANALYSIS
Draft
105
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
106
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
107
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
108
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
109
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
110
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
111
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
112
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX H ACCIDENT SCENE SURVEY
Draft
113
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX I BNL METEOROLOGICAL SUMMARIES FOR SEPTEMBER AND OCTOBER 2009 BROOKHAVEN NATIONAL LABORATORY METEOROLOGICAL SUMMARY MONTH SUMMARY FOR SEPTEMBER, 2009 Run: 2009,10,01,14,24,45 Day Precip(in) MinT(F) MaxT(F) Rad(W/m^2) MaxWind88(mph) 1 0.00 48.20 72.50 999 24.8 2 0.00 44.96 74.84 999 14.8 3 0.00 45.86 76.10 999 15.9 4 0.00 50.00 81.86 999 19.5 5 0.00 60.08 82.76 999 12.5 6 0.00 54.86 71.78 999 28.2 7 0.00 51.44 73.04 999 16.1 8 0.00 54.86 74.66 999 11.2 9 0.04 59.54 75.38 999 29.1 10 0.00 59.18 69.26 999 41.6 11 1.20 59.00 66.20 999 42.7 12 0.26 64.22 67.64 999 18.1 13 0.04 61.16 77.72 999 22.4 14 0.01 55.76 71.24 999 20.6 15 0.00 56.30 83.30 999 20.6 16 0.06 59.72 66.02 999 29.3 17 0.00 46.40 64.58 999 29.8 18 0.00 44.96 73.04 999 26.8 19 0.00 42.80 67.10 999 31.5 Draft
MxMnAvT(F) MeanT(F) HeatDD 60.35
60.02
4.6
0.0
-
59.90
59.51
5.1
0.0
-
60.98
60.78
4.0
0.0
-
65.93
65.47
0.0
0.9
-
71.42
70.25
0.0
6.4
-
63.32
65.36
1.7
0.0
-
62.24
61.04
2.8
0.0
-
64.76
63.88
0.2
0.0
-
67.46
65.56
0.0
2.5
-
64.22
62.89
0.8
0.0
-
62.60
62.97
2.4
0.0
-
65.93
65.86
0.0
0.9
-
69.44
68.63
0.0
4.4
-
63.50
63.59
1.5
0.0
-
69.80
68.34
0.0
4.8
-
62.87
62.85
2.1
0.0
-
55.49
56.96
9.5
0.0
-
59.00
60.23
6.0
0.0
-
54.95
56.35
10.0
0.0
-
114
CoolDD
December 4, 2009
BNL NSLS-II Accident Investigation
20 999 21 999 22 999 23 999 24 999 25 999 26 999 27 999 28 999 29 999 30 999
0.00 17.4 0.00 19.0 0.00 15.4 0.01 23.9 0.04 21.3 0.00 28.9 0.01 21.0 1.39 28.4 0.12 38.9 0.00 33.8 0.00 28.6
38.66
72.68
55.67
55.34
9.3
0.0
-
43.70
73.94
58.82
58.82
6.2
0.0
-
52.70
75.74
64.22
65.17
0.8
0.0
-
60.98
76.28
68.63
69.03
0.0
3.6
-
58.64
82.04
70.34
71.84
0.0
5.3
-
47.30
68.00
57.65
59.94
7.4
0.0
-
40.46
64.04
52.25
53.41
12.8
0.0
-
55.22
67.28
61.25
63.76
3.8
0.0
-
56.30
71.96
64.13
63.52
0.9
0.0
-
47.84
68.72
58.28
58.96
6.7
0.0
-
42.62
61.88
52.25
54.40
12.8
0.0
-
Mean Daily minimum temp = 52.1, Extreme minimum temp = Mean Daily maximum temp = 72.4, Extreme maximum temp = Month mean temp = 62.5 degF Monthly maximum wind speed (90 m) = 42.7 mph Monthly total precipitation = 3.18 inches Month total Heat DDs (F) = 111.3 (F) Month total Cool DDs (F) = 29.0 F Month mean insolation = -999.0 W/m^2
38.66 degF 83.30 degF
$$$NOTE$$$ After a calibration on the 85 meter temperature sensor a -2.2 degree offset was added to the Campbell program and the new program was installed at 1420 on 09/23/09. Definition: Heat degree day = MxMnAv - 65 (degF). Cool deg day = 65 MxMnAv (degF). If deg day < 0, set deg day to 0.0. 65 degF = 18.3 degC Ref: 'The Urban Climate' by Helmut E. Landsberg Temperature min/max based on 1-min averages Wind gust based on 1-min extreme data
Draft
115
December 4, 2009
BNL NSLS-II Accident Investigation
BROOKHAVEN NATIONAL LABORATORY METEOROLOGICAL SUMMARY MONTH SUMMARY FOR OCTOBER, 2009 Run: 2009,10,22,13,56,55 Day Precip(in) MinT(F) MaxT(F) Rad(W/m^2) MaxWind88(mph) 1 0.00 39.38 58.82 999 22.6 2 0.00 35.24 74.48 999 28.9 3 0.74 63.68 69.62 999 27.7 4 0.00 55.76 75.56 999 21.9 5 0.00 46.40 65.66 999 28.0 6 0.01 43.70 66.38 999 24.8 7 0.44 56.66 71.42 999 51.7 8 0.00 48.92 62.06 999 36.9 9 0.01 50.18 67.64 999 37.6 10 0.00 41.36 67.10 999 32.4 11 0.00 34.16 63.32 999 24.8 12 0.00 37.58 53.06 999 26.2 13 0.00 37.58 62.96 165 40.7 14 0.00 36.14 52.52 169 21.5 15 0.81 40.82 44.96 181 39.4 16 0.07 39.74 46.22 169 36.9 17 0.00 43.70 51.80 999 31.3 18 0.91 39.92 47.30 999 45.2 19 0.00 31.10 53.96 999 24.6 20 0.00 30.20 65.66 999 20.8
Draft
MxMnAvT(F) MeanT(F) HeatDD 49.10
49.12
15.9
0.0
-
54.86
54.69
10.1
0.0
-
66.65
65.87
0.0
1.7
-
65.66
63.79
0.0
0.7
-
56.03
56.19
9.0
0.0
-
55.04
55.55
10.0
0.0
-
64.04
63.21
1.0
0.0
-
55.49
55.37
9.5
0.0
-
58.91
60.81
6.1
0.0
-
54.23
59.68
10.8
0.0
-
48.74
49.27
16.3
0.0
-
45.32
45.86
19.7
0.0
-
50.27
52.59
14.7
0.0
44.33
44.93
20.7
0.0
42.89
42.68
22.1
0.0
42.98
42.65
22.0
0.0
47.75
47.23
17.3
0.0
-
43.61
43.54
21.4
0.0
-
42.53
42.61
22.5
0.0
-
47.93
46.75
17.1
0.0
-
116
CoolDD
December 4, 2009
BNL NSLS-II Accident Investigation
21 999 22 999 23 999 24 999 25 999 26 999 27 999 28 999 29 999 30 999 31 999
0.00 14.1 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999
40.46
69.08
54.77
51.73
-999
-999
-999
-999
-999
-999
-999
-999
-999
-999
10.2
0.0
-
-999
-999
-
-999
-999
-999
-
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
Mean Daily minimum temp = 42.5, Extreme minimum temp = Mean Daily maximum temp = 61.4, Extreme maximum temp = Month mean temp = 52.1 degF Monthly maximum wind speed (90 m) = 51.7 mph Monthly total precipitation = 2.99 inches Month total Heat DDs (F) = 276.2 (F) Month total Cool DDs (F) = 2.3 F Month mean insolation = 42.7 W/m^2
30.20 degF 75.56 degF
Definition: Heat degree day = MxMnAv - 65 (degF). Cool deg day = 65 MxMnAv (degF). If deg day < 0, set deg day to 0.0. 65 degF = 18.3 degC Ref: 'The Urban Climate' by Helmut E. Landsberg Temperature min/max based on 1-min averages Wind gust based on 1-min extreme data Missing data = $missing, signifies > $
Draft
117
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX J DESCRIPTION OF RADIO TRANSMISSIONS Radio Transmissions at BNL on September 30, 2009 that concern the NSLS-II Accident (Note: there is approx. a two-minute difference in the time logged by the system and the actual time.) Time logged Description of Call 8:45:21
Leg injury, possible serious injury at NSLS-II
8:46:17
Rescue 4 on route to NSLS-II; fire captain contacted fire rescue to request Motor Pool expedite Ambulance and get it back to fire rescue as soon as possible
8:47:09
Fire Captain speaking...[cannot understand]
8:47:21
Captain ‡ is at the entrance to NSLS-II
8:47:59
Captain is looking for confirmation of exact location; fire rescue confirmed it’s on the west side by Princeton
8:48:31
Captain said he is on scene at 8:46.
8:48:43
Ambulance on route and Rescue 4 on scene [general area]
8:49:03
Captain contacted Rescue 4; specific directions
8:49:33
Captain called Fire Rescue; standby
8:49:51
Captain transmits what kind of injury the patient has: male with compound fracture to right leg; fire rescue repeats “all units be advised compound fracture...”; tells fire dispatcher that he needs aviation; fire dispatcher asks if captain wants him to handle it or if he will; Captain replies that he will handle it [contact Fire Rescue and Suffolk for helicopter]
8:51:21
Captain calling police headquarters [PDHQ]
8:51:31
Captain calling police headquarters [PDHQ]
8:51:42
Captain calling police headquarters [PDHQ]
8:52:08
PDHQ responds
8:52:36
Fire Rescue to Captain: asks if he wanted an engine to stand by at the landing zone; Captain says yes and to notify police that this will leave the base unmanned; Captain says that he will call Fire Rescue [& Emergency Services, Suffolk County, Yaphank] to get an ETA of the bird.
8:53:17
Fire House calls Captain to say that he has two firefighters in quarters, would he like him to stay on radio [indicating that base is not unmanned]; staying on radio
8:53:55
PDHQ calls Captain
8:54:12
PDHQ requests confirmation that Captain is calling for helicopter so he does not have to
‡
“Captain” in this document refers to Fire Captain.
Draft
118
December 4, 2009
BNL NSLS-II Accident Investigation
8:54:36
Captain asks PDHQ that an ORPS Coordinator respond to the scene
8:54:53
Confirmed 8:53; Engine 2 going to PDHQ [for helicopter landing]
8:56:29
Engine 2 on scene [at the landing zone]
8:58:46
Police asks Fire if they got the page; says standby
9:00:32
Police says “go ahead Fire” (phone rings)
9:00:51
OK Fire, thanks
9:01:01
Ambulance [Unit 16] signaled to Stony Brook [this means they are on route to Stony Brook University Medical Center (Stony Brook)]
9:01:21
Fire calling Ambulance [no response]
9:01:35
Fire Rescue asks Captain if they are transporting patient via ground; Captain replies “yes”.
9:02:52
Fire to Engine 2
9:03:09
Fire to Engine 2
9:03:18
Engine 2 responds he read [the transmission] direct and he is returning to quarters
9:04:43
Captain: ES 2 and Rescue ok to return to quarters; Ambulance signal 18 [this means”on route”] to Stony Brook; Captain will wait on scene for the ORPS categorizer; Fire says OK; 34 later [phone call]
9:06:11
Rescue is returning to quarters
9:09:07
Captain informs Ambulance that it was 2,400 pounds of steel [that caused the injury]
9:14:08
Fire calling Ambulance asking for crew [names]
9:14:25
Ambulance provides names
9:14:48
[More about crew]
9:15:25
Ambulance picked up a first responder [from Farmingville Fire House]
9:27:55
[not related to this investigation]
9:28:32
[not related to this investigation]
9:36:21
Confirmed 9:34: Ambulance arrived at Stony Brook
9:52:11
Captain tells Fire Rescue that he is leaving the scene
10:04:43
Ambulance calling BNL Fire Rescue; leaving Hospital, on route back to BNL; needs to drop off first responder where he was picked up
10:29:32
At exit 68 of LIE; should be there in a couple of minutes; have somebody with a broom stand by to clean the Ambulance because it needs to get back to the Motor Pool right away
10:43:31
Dropping off Ambulance at Motor Pool
Draft
119
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX K DESCRIPTION OF CALL TO BNL EMERGENCY REPORTING NUMBER
Date September 30, 2009
Time logged 8:44:13
Description of Call The Safety Manager for Torcon reports an injury that needs an ambulance; injury to leg, perhaps seriously, of one of our workers. He also reports the location: Vehicle tunnel, NSLS-II, west side of project; Princeton Avenue; at entrance in gate, take road to the left. Responder replies: We’re on our way.
Draft
120
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX L LETTER FROM REBAR STEEL CORP. DETAILING LABORER’S EXPERIENCE
Draft
121
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX M • • •
REFERENCE DOCUMENTS
Investigation Team Charge Memo Memo, G.S. Podonsky to M. Holland, October 7, 2009, Waiver of Type B Accident Investigation Occurrence Notification Report. SC-BSHO-BNL-BNL-2009-0019
Section 1: Contracts and Procedures BNL/NSLS-II • • • • • • • • •
Final Hazard Analysis Report for NSLS-II ES&H Management Plan for the Conventional Construction of NSLS-II Facilities (LT-ESH-0009, Rev. 1, February 2009) Management Plan for Construction of NSLS-II Conventional Facilities Rev. 1 (LT-CFD-002-CD-Rev 01, June 2009) NSLS-II ES&H Procedures BNL/Torcon Contract Final Report – Assessment of BNL NSLS-II Project Training Requirement NSLS-II ESH Monthly Meeting Minutes Environment, Safety, and Health Plan for the NSLS-II NSLS-II Construction Environment, Safety and Health Plan for Conventional Construction of the Ring Building (LT-ESH-0006/rev 1, April 2009)
Torcon • • • • • • • • • •
•
Torcon Safety Violation Log Torcon Labor/Management Safety Committee Meeting Minutes (meetings #20, 9/10/09; #21, 9/17/09; #22, 9/24/09) Torcon Organization Chart for the NSLS-II Ring Building Construction Torcon Master Badge List (Names in red indicate those who have been disciplined or discharged for cause) Torcon NSLS-II Project Safety Orientation, Rev. 6, September, 2009 (Section 10 describes preemployment drug testing) Torcon Project Orientation and General Safety and Health Rules (page 6 describes drug testing for cause). Each employee must sign an acknowledgement following training. BSA’s Torcon Assessment Schedule Resume of Tom Moon, Torcon Site Safety Manager Torcon Safety Incentive Program Torcon Corporate Policy, Drug-free Workplace Policy; Excerpt from Torcon Project SH & E Program regarding Drug-free Workplace Policy; and Procedures regarding Drug Collection Torcon Project Safety, Health and Enviornment Program (Original, Rev. 2 and Rev. 3)
Macedos • • Draft
Various Tool-Box training sessions conducted by Macedos Macedos Construction Lull Service Records 122
December 4, 2009
BNL NSLS-II Accident Investigation
• • •
Lull Safety Manual and Operating Manual Lull Technical Brochure and Specification Sheet Daily Inspection Service Log for Lull
Other •
NY State Dept. of Health, Bureau of Emergency Medical Services, Policy Statement (Advanced Life Support) and F&O SOP Emergency Medical Services (EMS) Program, FR-EMS-3.00, Rev. 5, effective 12/12/07
Section 2: Reports prior to the Accident • • •
•
• • • • Draft
Internal Audit and Oversight Report, IO 09-07 Phase I, NSLS-II Construction Safety Program Review, Phase 1, 8/26/09 Various e-mails between Torcon and BNL involving safety observations Various Phase Hazard Analyses o Rebar Steel – installing rebar and wire welded mesh o Macedos – Crane Operations o Macedos – DOCA Formwork using lifting clamps o Macedos – Installing Monuments o Macedos – Ring Tunnel Footings o Macedos – Project: All Footings o G.E. Modular – Install. of Project Office Trailers o Vollers Ex. & Const. – Silt Fence Installation o Vollers/Advanced Env. Services – Removal of Underground Transite Pipe (pre-existing) o Rebar Steel – Fabrication of Rebar o GLS Elec.- cad Welding Footings o Macedos – Heat Exposure o Macedos – Formwork Mockups o Macedos – “Other Contractor” Exposure o Macedos – Crane Operations: Vehicle Tunnel Formwork o Macddos – Pre Mobilization/New Hires Reports of Accidental Injury or Occupational Disease o 9/30/09: Lather, Rebar Steel, right leg (Torcon, Rebar Steel, and Pembrooke reports) o 9/28/09: Carpenter, Macedos, right calf muscle (Torcon report only) o 9/21/09: Laborer, Macedos, left ankle (Pembrooke report only) o 9/2/09: Lather, Rebar Steel, left elbow (Torcon and Pembrooke reports) o 8/13/09: Manager, Torcon, right calf muscle (Pembrooke report only) o 8/13/09: Concrete, Macedos, left arm (Pembrooke report only) o 8/10/09: Laborer, Vollers, nosebleed (Pembrooke report only) o 8/7/09: Inspector, BNL, left and right knee (Pembrooke report only) o 8/5/09: Lather, Pratt Brothers, left forearm (Torcon and Pembrooke reports) o 7/27/09: Eng., Vollers, right elbow (Pembrooke report only) o 7/16/09: Electrician, Hinck Electric, chipped tooth (Torcon and Pembrooke reports) o 4/16/09: Trailer Installer, Modular Dimensions, right heel (Torcon report only) E-mail dated 4/16/09 from M. Fallier to various re: heel injury E-mail dated 4/22/09 from M. Fallier to various re: Torcon Safety Concerns Notice to proceed with Ring Building construction – 3/25/09 Series of e-mails regarding Work Observations at NSLS-II site on 4/20 & 4/21/09 123
December 4, 2009
BNL NSLS-II Accident Investigation
• • • • • • •
Report from PTI to Leon Baukh, dated 9/9/09 , BNL NSLS-II Ring Building General Loss Control Service Visit on 9/3/09 Daily Inspection Reports, conducted by BNL, January – August 2009 Liberty Mutual Report, dated, 9/2/09, of visit to NSLS-II Construction Site on 8/19/09 Liberty Mutual Report, dated, 9/29/09, of visit to NSLS-II Construction Site on 9/10/09 Allied North America, site visit conducted July 24, 2009 Torcon Dairly Jobsite Safety Inspections Project Safety Evaluations
Section 3: The Accident • • • • • • • • • • • • • • • • • • • • • • •
BNL weather summaries for September 30, 2009 Fact finding meeting notes taken by NSLS-II Construction Safety Inspectors – September 30, 2009 BNL Fire/Rescue Report Torcon (Pembrooke) Incident Report Torcon Report of Accidental Injury, preliminary Statement of Laborer (injured party) Letter from Rebar Steel dated 10/9/09 – Experience of Laborer Laborer Training History Results of Drug Test for Laborer and Operator Witness statement by Operator, including training records and list of persons in attendance during his statement Forklift Training Program and Certification for Operator Witness statement by Laboer2, Macedos Construction Witness Statement by Laboer3, Macedos Construction Witness statement by Pembroke EMT Witness statement by BNL Fire/Rescue Captial Statement by BNL EMT Response Team Response from BNL Fire/Rescue – Statement of Medical Response Personnel Photo Log Photographs of scene – post accident Photographs taken from the HFBR stack at 8:30, 8:45, and 9:00 A.M. Photographs taken 10/5/09 at scene of accident Topographical survey – Lull and rebar site (site of accident of 9/30/09), dated 10/7/09 Rebar Steel Accident Report
Section 4: Post-Accident Data • • • • • • • • • Draft
Torcon Safety Stand-down memo (including attendance sheet) Letter dated 10/2/09 – Torcon Measures in Response to 9/30/09 Accident Torcon Safety Stand-down meeting, 10/2/09 Corrective Action and Restart Plan dated 10/7/09 Minutes of Morning Safety Meeting, 10/9/09 Hand Signals Tool Box, 10/14/09 Phase Hazard Analyses for rebar handling with a forklift and for unloading rebar from trucks (including attendance sheet) Signed PHAs (2) for movement of rebar, Rev. 7, 10/7/09 Photos of rebar demonstration using approved PHAs 124
December 4, 2009
BNL NSLS-II Accident Investigation
• • • • • • • • • • •
Draft
Authorization to restart mechanical rebar operations Two lift plans: (1) DOCA Formwork using crane; (2) installation of steel columns at vehicle and utility tunnels Interview with Macedos Construction on 10/7/09 Interview with Torcon Construction on 10/8/09 Interview with Rebar Steel Supervision on 10/13/09 Safety Observations, LSII Project, Accident Investigation Committee Member, 10/12/09 Field Observations Summary, Accident Investigation Committee Member, 10/15/09 Memo dated 10/15/09, requesting additional information, and answers provided Torcon, Inc. Safety Status Report #1, 10/16/09 Internal Audit and Oversight Report, 10 09-07 Phase 2, NSLS-II Construction Safety Program Review, Phase 2, 10/21/09 Draft Copy of Worker Safety and Health Management System Description, SBMS, printed 10/21/09
125
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX N ACCIDENT INVESTIGATION COMMITTEE MEMBERS
Lead Raymond Costa Facilities & Operations Brookhaven National Laboratory 631-344-8227 [email protected]
Member David Fuller SNS-ES&H Oak Ridge National Laboratory 865-241-9095 [email protected]
Member Edward Sierra Quality Management Office Brookhaven National Laboratory 631-344-4080 [email protected]
Member Steven Kane Safety & Health Services Division Brookhaven National Laboratory 631-344-7236 [email protected]
Member Tom Conrad Safety & Health Services Division Brookhaven National Laboratory 631-344-5789 [email protected]
Consultant Brad Tullis Dade Moeller & Associates Richland, WA 541-619-1126 [email protected]
Observer Chris Seniuk BHSO-DOE 631-344-2034 [email protected]
Consultant William Brown, PhD Quality Management Office Brookhaven National Laboratory 631-344-7230 [email protected]
Member - Documentation Sabine Kessler Quality Management Office Brookhaven National Laboratory 631-344-4340 [email protected]
Draft
126
December 4, 2009
ACCIDENT INVESTIGATION COMMITTEE REPORT ON THE LEG INJURY AT THE BNL NSLS‐II CONSTRUCTION SITE THAT OCCURRED ON SEPTEMBER 30, 2009
DRAFT December 4, 2009
BROOKHAVEN NATIONAL LABORATORY
Draft
1
December 4, 2009
BNL NSLS-II Accident Investigation
This page has been left blank intentionally.
Draft
2
December 4, 2009
BNL NSLS-II Accident Investigation
TABLE OF CONTENTS Tables and Figures.......................................................................................................................................... 6 Acronyms......................................................................................................................................................... 7
Executive Summary ........................................................................................................................................ 9 1.0 Introduction.............................................................................................................................................. 13 1.1 Background ..................................................................................................................................... 13 1.2 Facility Description .......................................................................................................................... 14 1.3 Project Management ....................................................................................................................... 15 1.3.1 Contractual Responsibilities ................................................................................................ 17 1.4 Scope, Purpose, and Methodology ................................................................................................. 19 1.4.1 Accident Investigation Terminology ..................................................................................... 20
2.0 Facts ........................................................................................................................................................ 21 2.1. Accident .......................................................................................................................................... 21 2.1.1 Description of the Accident Site........................................................................................... 21 2.1.2 Description of the Accident .................................................................................................. 22 2.2 Emergency Response ..................................................................................................................... 25 2.3 Chronology ...................................................................................................................................... 26 2.4 Environmental Conditions ............................................................................................................... 27 2.5 Operator Training and Qualifications .............................................................................................. 28 2.6 Laborer Training and Qualifications ................................................................................................ 28 2.7 Forklift Specifications ...................................................................................................................... 29
3.0 Analysis ................................................................................................................................................... 30 3.1 Analysis of Conflicting Statements ................................................................................................. 30 3.1.1 Spotter and Hand Signals .................................................................................................... 30 3.1.2 Mud ...................................................................................................................................... 33 3.2 Barrier Analysis ............................................................................................................................... 34 3.3 TapRooT® Analysis ......................................................................................................................... 34 3.4 Event & Causal Factors Analysis .................................................................................................... 35 Draft
3
December 4, 2009
BNL NSLS-II Accident Investigation
3.5 Project Oversight............................................................................................................................. 35 3.5.1 Analysis of Contract Attachment A, Article 43 ..................................................................... 35 3.5.2 Analysis of Contract Attachment A, Article 16 ..................................................................... 44 3.5.3 Analysis of BSA and NSLS-II Oversight .............................................................................. 45 3.6 Integrated Safety Management....................................................................................................... 47 3.6.1 Guiding Principles ................................................................................................................ 49 3.6.2 Define Work ......................................................................................................................... 50 3.6.3 Analyze the Hazards............................................................................................................ 51 3.6.4 Develop and Implement Controls ........................................................................................ 52 3.6.5 Perform Work Safely............................................................................................................ 54 3.6.6 Feedback and Improvement ................................................................................................ 55 3.7 Analysis of Emergency Response .................................................................................................. 60
4.0 Conclusions and Judgments of Need ..................................................................................................... 61 4.1 Direct, Root, and Contributing Causes ........................................................................................... 62 4.2 Judgments of Need ......................................................................................................................... 68
5.0 Other Analyses Required by Team Charter ............................................................................................ 71 5.1 Immediate Response to the Accident ............................................................................................. 71 5.1.1 Discussion/Recommendations ............................................................................................ 72 5.2 Safety Incentive Program ............................................................................................................... 72 5.2.1 Discussion/Recommendations ........................................................................................... 75 5.3 Review of Construction Safety Program Implementation ............................................................... 76 5.3.1 Field Observations ............................................................................................................... 76 5.3.2 Adequacy of Torcon’s Safety Plan Implementation and Flowdown to Subcontractors ....... 76 5.3.3 Adequacy of BNL Oversight of Torcon’s Safety Program ................................................... 76 5.3.4 Recommendations to Improve Overall Construction Site Safety ........................................ 77 5.4 Non-Accident Investigation Judgment of Need – HIPAA ................................................................ 78
6.0 Accident Investigation Committee Signatures ........................................................................................ 79
Draft
4
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDICES Appendix A – Accident Investigation Committee Charter ............................................................................... 80 Appendix B – Waiver ....................................................................................................................................... 82 Appendix C – Summary of Interview Statements ........................................................................................... 83 Appendix D – Footnotes .................................................................................................................................. 85 Appendix E – Barrier Analysis of the Accident (Physical and Administrative) ................................................ 92 Appendix F – TapRooT® Analysis ................................................................................................................... 99 Appendix G – Events and Causal Factors Analysis ........................................................................................ 105 Appendix H – Accident Scene Survey ........................................................................................................... 113 Appendix I – BNL Meteorological Summaries for September and October 2009 .......................................... 114 Appendix J – Description of Radio Transmissions .......................................................................................... 118 Appendix K – Description of Call to BNL Emergency Reporting Number ....................................................... 120 Appendix L – Letter from Rebar Steel Corp. Detailing Laborer’s Experience................................................. 121 Appendix M – Reference Documents ............................................................................................................. 122 Appendix N – Accident Investigation Committee Members ............................................................................ 126
Draft
5
December 4, 2009
BNL NSLS-II Accident Investigation
TABLES Table 1. Chronology of the Accident and Response ............................................................................................. 26 Table 2. Summary of Causes Identified and the Corresponding ISM Core Functions and Guiding Principles. ... 57 Table 3. Event causes, summaries, sources, and associated JONs. ................................................................... 62 Table 4. Contributing causes to program weaknesses, summaries, sources, and associated JONs. ................. 64 Table 5. Judgments of Need. ................................................................................................................................ 68
FIGURES Figure 1. Conceptual view of the NSLS-II when completed.................................................................................. 14 Figure 2. NSLS-II Construction Project Chart as of June 3, 2009. ....................................................................... 15 Figure 3. BSA, Torcon, and subcontractor relationships with respect to this accident. ....................................... 16 Figure 4. BSA/NSLS-II, Torcon, and subcontractor key ES&H requirements and their flowdown with respect to this accident. ......................................................................................................................................................... 18 Figure 5. Aerial view of the NSLS-II construction site taken from the BNL HFBR Stack facing southeast, September 30, 2009, at 0800 hours. ..................................................................................................................... 21 Figure 6. Aerial view taken prior to the accident on September 30, 2009, facing southwest. .............................. 22 Figure 7. Shows the accident site facing northeast. ............................................................................................. 23 Figure 8. Operator’s view facing east, looking out of the Lull at the accident area. ............................................. 24 Figure 9. Photo taken on September 30, 2009, at approximately 0940 hours. ................................................... 34 Figure 10. Tire marks and impression in the ground visible in the center, above the bundle of rebar. ................ 85 Figure 11. Staging area (accident location). ......................................................................................................... 86 Figure 12. Staging area (accident location), including the Lull. ............................................................................ 86 Figure 13. Rebar storage locations. ...................................................................................................................... 87 Figure 14. Operator’s view. ................................................................................................................................... 88 Figure 15. Load chart for Lull. ............................................................................................................................... 88 Figure 16. The spoil pile is visible at the back of the photo. ................................................................................. 89 Figure 17. Broken cribbing. ................................................................................................................................... 90 Figure 18. Broken center wire tie visible in bundle on the right-hand side. .......................................................... 91 Figure 19. Broken center wire tie visible in bundle in front of photograph. ........................................................... 91 Draft
6
December 4, 2009
BNL NSLS-II Accident Investigation
ACRONYMS ANSI
American National Standards Institute
BLS
Bureau of Labor Statistics
BNL
Brookhaven National Laboratory
BSA
Brookhaven Science Associates
BHSO
U.S. Department of Energy Brookhaven Site Office
CAIRS
Computerized Accident, Incident Reporting System
CFR
Code of Federal Regulations
DART
Days away, restricted, or transferred
DEAR
Department of Energy Acquisition Regulation
DOE
Department of Energy
E&CFC
Events and Causal Factors Charting
EMT
Emergency Medical Technician
EMS
Emergency Management System
ES&H
Environment, Safety, and Health
ESH&Q
Environment, Safety, Health and Quality
ETA
Estimated time of arrival
HASP
Health and Safety Program
HFBR
High Flux Beam Reactor
ISM
Integrated Safety Management
ISMS
Integrated Safety Management System
ISO
International Organization for Standardization
IO
Internal Audit and Oversight
JON
Judgment of Need
JRA
Job Risk Assessment
LIE
Long Island Expressway
Draft
7
December 4, 2009
BNL NSLS-II Accident Investigation
NSLS
National Synchrotron Light Source
NSLS-II
National Synchrotron Light Source II
OHSAS
Occupational Health & Safety Advisory Services
OSHA
Occupational Safety and Health Administration
PDHQ
Police Department Head Quarters
PHA
Phase Hazard Analysis
PTI
Project Technologies International, LLC
RTV
Rough Terrain Vehicle
SBMS
Standards-Based Management System
SHE
Safety, Health, and Environment
SHSD
Safety and Health Services Division
Draft
8
December 4, 2009
BNL NSLS-II Accident Investigation
EXECUTIVE SUMMARY On September 30, 2009, at 0840 hours, a Laborer at the National Synchrotron Light Source II (NSLS-II) construction site at Brookhaven National Laboratory (BNL) was injured when a bundle of rebar struck his leg. He was directing the Operator of the rough-terrain forklift (Lull) to place bundles of rebar on cribbing in preparation for pickup by crane, when the rebar struck his right leg and fractured it. The rebar was immediately removed from his leg by the Operator using the Lull. At 0845 hours, BNL’s Laboratory Protection Division’s emergency reporting number, extension 2222, received a call from Torcon’s Safety Manager advising of the injury and requesting an ambulance. In parallel, Torcon’s site EMT was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing medical care. At 0848 hours, the BNL Fire Captain arrived at the scene and assumed the role of Incident Commander. Upon arrival of the BNL Ambulance at 0848 hours, BNL Fire Rescue personnel assumed responsibility for the injured worker and prepared him to be transported to Stony Brook University Medical Center (Hospital) via BNL Ambulance. The injured arrived at the Hospital Emergency Room at 0936 hours, and the BNL Ambulance returned to BNL at approximately 1030 hours. On October 1, 2009, Dr. Steven Dierker, NSLS-II Project Director, charged an independent Accident Investigation Committee to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. On October 6, 2009, six days after the accident, the Laborer was released from the Hospital. He had undergone surgery to repair the fracture and rehabilitation to allow him to move with crutches. Five continuous calendar days in a hospital requires a Type B investigation per DOE O 225.1A, Accident Investigations. However, on October 7, 2009, Michael D. Holland, Manager, Office of Science Brookhaven Site Office (BHSO), received a Memorandum from Glenn S. Podonsky, Chief Health, Safety and Security Officer, Office of Health, Safety and Security, granting a request by BHSO to allow BSA’s Accident Investigation Committee to complete the investigation with DOE oversight. The Accident Investigation Committee began its activities on October 1, 2009 and submitted the final report to the NSLS-II Project Director on December 4, 2009. The charge of the Committee was to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. The Accident Investigation Committee applied several analytical techniques to determine the causal factors of the event. They included Barrier Analysis (BA), Events and Causal Factors Charting (E&CFC), and TapRooT® (TR). Facts were also analyzed using the Core Functions and Guiding Principles of Integrated Safety Management (ISM). In addition, ES&H oversight was evaluated against contract requirements. A Human Factors Scientist reviewed the accident description and these analyses to ensure Human Performance Improvement was incorporated in the results. The Accident Investigation Committee also analyzed the adequacy of the Contractor’s safety program implementation and flow down to subcontractors, as well as the adequacy of BSA’s NSLS-II oversight of the Contractor (as per its charter) using the above results. The Committee limited this analysis to those processes and systems viewed during the performance of the accident investigation, therefore this should not be interpreted as a full analysis. Draft
9
December 4, 2009
BNL NSLS-II Accident Investigation
The Accident Investigation Committee has concluded that this accident was preventable. There is one direct cause and two root causes to this event, which are summarized in the following table.
DCE No. 1 RCE No.
Direct Cause of the Event Laborer struck by rebar
JON 1, 2, 5 & 7
Root Cause of the Event
JON
1
Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities.
1, 5 & 7
2
Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety.
2, 5 & 7
The Accident Investigation Committee identified four causes that did not contribute to this event but contributed to weakening the NSLS-II ES&H Program at the construction site, which are summarized in the following table.
CCW No.
Contributing Cause (Program Weakness)
JON
1
Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels.
3, 5 & 7
2
Torcon and its subcontractors failed to ensure implementation of the NSLS‐II ES&H Program and therefore contributed to its weakness.
4, 5 & 7
3
Torcon and its subcontractors failed to implement an effective suspect/counterfeit program for rigging.
5, 6 & 7
4
NSLS‐II failed to ensure that the NSLS‐II ES&H Program was performing as designed.
5 & 7
Draft
10
December 4, 2009
BNL NSLS-II Accident Investigation
Judgments of Needs were developed to address each Cause and are as follows:
No.
Draft
Judgment of Need
Cause Codes
1
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure workers are qualified and possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities in compliance with (1) Contract Attachment A, Article 43, (2) ES&H program and (3) ISM.
DCE‐1 RCE‐1
2
DCE‐1 There is a need for Torcon and all its subcontractors, at all levels, on RCE‐2 the NSLS‐II construction site, to ensure workers are aware of foreseeable hazards and protective measures for their safety. This includes, but is not limited to defining “major phases” of work to determine when hazard analyses are required, establishing the criteria for acceptance of hazard analyses, discussing hazards and their controls during pre‐job briefings, and ensuring compliance with (1) Contract Attachment A, Article 43 (d)(1), Establishment of Safety Protocols, and (2) Torcon’s SHE Program Section 11, PHAs.
3
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to establish clear and unambiguous lines of authority and responsibility for the implementation the (1) Contract, (2) Torcon’s SHE Program, and (3) other ES&H requirements.
CCW‐1
4
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure all ES&H requirements of the Contract and Torcon’s SHE Program are being adequately implemented. This includes, but is not limited to, the following requirements: • Contract, Attachment A o Article 16, Suspect/Counterfeit Items o Article 43 subsections (d)(1) Establishment of Safety Protocols (d)(2) Frequent and Regular Inspections of the Work Site (f) Immediate Notification to BSA’s Contractual Representative of Recordable Injuries (k) Subcontractor’s Compliance with ES&H
CCW‐2
11
December 4, 2009
BNL NSLS-II Accident Investigation
No.
Judgment of Need
Cause Codes
Requirements of the Contract • Torcon’s SHE Program o Section 11, PHAs o Section 14, Daily Inspections of Heavy Equipment o Section 19, Procedures for Injuries and Near Misses o Section 23, Job Site Inspections o Section 38, Rigging Procedures and Inspections • NFPA 10, Standard for Portable Fire Extinguishers DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
5
There is a need for the NSLS‐II project to provide adequate oversight to ensure that BSA ES&H Contract requirements and the NSLS‐II ES&H programs are being fully implemented. This includes, but is not limited to: • Compliance with Contract, Attachment A, Article 43 (g), Written Notification to Contractor of Non‐compliances • Compliance with BSA’s Construction Safety Subject Area • Compliance with NSLS‐II ES&H Management Plan, paragraph 3.3.1.1, Safety Responsibilities • Compliance with NSLS‐II Project Procedure LT‐ESH_P‐00013, Safety Inspections.
6
CCW‐3 There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to implement an effective suspect/counterfeit program for rigging. This includes, but is not limited to, revising Torcon’s SHE program to reflect inspection of rigging equipment for suspect/counterfeit items prior to use and ensuring there are no unknown suspect/counterfeit items currently in use on the NSLS‐II construction site. There is a further need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure that Contract, Attachment A, Article 16, is being met.
7
There is a need for the NSLS‐II project to establish and implement a well structured assessment program to complement field inspections. The assessment program should be designed to ensure all elements of the ES&H program required by the Contract and ES&H Plans are functioning properly. The schedule should be established to ensure elements that support or monitor life protection programs (e.g., LOTO, confined spaces, excavation, electrical safety) are given priority.
DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
Draft
12
December 4, 2009
BNL NSLS-II Accident Investigation
1.0
INTRODUCTION
1.1
BACKGROUND
On September 30, 2009, at 0840 hours, a Laborer at the National Synchrotron Light Source II (NSLS-II) construction site at Brookhaven National Laboratory (BNL) was injured when a bundle of rebar struck his leg. He was directing the Operator of the rough-terrain forklift (Lull) to place bundles of rebar on cribbing in preparation for pickup by crane, when the rebar struck his right leg and fractured it. The rebar was immediately removed by the Operator using the Lull. At 0845 hours, BNL’s Laboratory Protection Division’s emergency reporting number, extension 2222, received a call from Torcon’s Safety Manager advising of the injury and requesting an ambulance. In parallel, Torcon’s site EMT was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing medical care. At 0848 hours, the BNL Fire Captain arrived at the scene and assumed the role of Incident Commander. Upon arrival of the BNL Ambulance at 0848 hours, BNL Fire Rescue personnel assumed responsibility for the injured worker and prepared him to be transported to Stony Brook University Medical Center (Hospital) via BNL Ambulance. The injured arrived at the Hospital Emergency Room at 0936 hours, and the BNL Ambulance returned to BNL at approximately 1030 hours. On October 1, 2009, Dr. Steven Dierker, NSLS-II Project Director, charged an independent Accident Investigation Committee to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. This report responds to that charge. On October 6, 2009, six days after the accident, the Laborer was released from the Hospital. He had undergone surgery to repair the fracture and rehabilitation to allow him to move with crutches. Five continuous calendar days in a hospital requires a Type B investigation per DOE O 225.1A, Accident Investigations. However, on October 7, 2009, Michael D. Holland, Manager, Office of Science Brookhaven Site Office (BHSO), received a Memorandum from Glenn S. Podonsky, Chief Health, Safety and Security Officer, Office of Health, Safety and Security, granting a request by BHSO to allow BSA’s Accident Investigation Committee to complete the investigation with DOE oversight (see Appendix B).
Draft
13
December 4, 2009
BNL NSLS-II Accident Investigation
1.2 FACILITY DESCRIPTION NSLS-II will be a new state-of-the-art, medium-energy electron storage ring designed to deliver world-leading intensity and brightness, and will produce x-rays more than 10,000 times brighter than the current NSLS located at BNL. The conventional facilities required for the NSLS-II will include a Ring Building of approximately 392,000 square feet. The Ring Building will serve as the centerpiece of the NSLS-II and will house offices for the visiting user community, laboratory space, the main accelerator ring, experimental beamlines, experimental floor area, and supporting facilities.
Figure 1. Conceptual view of the NSLS-II when completed.
The construction type for the Ring Building will be reinforced slab on grade with perimeter footing, structural steel frame with composite reinforced concrete slab on metal deck for the upper floors, and insulated metal panel exterior. Although the building design will generally involve standard commercial design and construction techniques, there are some additional considerations due to the specific requirements of the accelerator, experimental beamlines, and types of research that will take place in laboratory spaces. Placement of the floor slab will involve an estimated 35,000 cubic yards of concrete, with special consideration given to minimization of differential settlement to assure alignment integrity of the installed accelerator and beamlines. Draft
14
December 4, 2009
BNL NSLS-II Accident Investigation
The NSLS-II Ring Building has been designed to minimize sources of vibration and transmission of vibration that would impact beam stability in the accelerator and experimental beamline areas and laboratory spaces. Construction started in April 2009, is currently in progress, and is scheduled for completion in April 2012.
1.3 PROJECT MANAGEMENT Brookhaven National Laboratory is operated by Brookhaven Science Associates, LLC, (BSA) who is under contract to the United States of America’s Department of Energy. Figure 2 provides an organizational chart for the NSLS-II Construction Project.
Figure 2. NSLS-II Construction Project Chart as of June 3, 2009.
Draft
15
December 4, 2009
BNL NSLS-II Accident Investigation
BSA has contracted the construction of the NSLS-II Ring Building to Torcon Incorporated (Torcon). The Operator of the Lull was employed by Macedos Construction, LLC (Macedos), who is under direct contract to Torcon. The Laborer, who was injured, was employed by Rebar Steel Corporation (Rebar Steel), who is under contract to Macedos. Figure 3 illustrates these contractual relationships.
Department of Energy
Brookhaven Science Associates (BSA) Contract for construction of the NSLS-II Ring Building
Torcon, Inc.
Other Subcontractors
Macedos Construction LLC
Operator of the Lull
Laborer who was injured
Rebar Steel Corp. Figure 3. BSA, Torcon, and subcontractor relationships with respect to this accident.
Draft
16
December 4, 2009
BNL NSLS-II Accident Investigation
1.3.1 CONTRACTUAL RESPONSIBILITIES Brookhaven Science Associates (BSA) manages the operations of Brookhaven National Laboratory (BNL) for the United States Department of Energy (DOE). Pertinent to the accident investigation are the environmental, safety, and health (ES&H) roles and responsibilities established by BSA and DOE under Contract DE-AC0298CH10886. BSA implements these roles and responsibilities through its Standards-Based Management System (SBMS). The NSLS-II team has taken these roles and responsibilities described in SBMS as they apply to their entire project and documented them in the Environmental, Safety, and Health Plan for the National Synchrotron Light Source-II; Doc #LT-ESH-002-CD-REV02 (NSLS-II ES&H Plan). To clearly communicate the construction ES&H requirements, the project team created the Environment, Safety, and Health Management Plan for the Construction of the NSLS-II Conventional Facilities, DOC #LT-ESH-0009-Rev1 (NSLS-II ES&H Management Plan). In addition, the project team created the National Synchrotron Light Source II Construction Environment, Safety and Health Plan for Conventional Construction of the Ring Building; Doc #LT-EHS-0006/rev1 (NSLS-II Construction HASP) specifically for the construction activities being conducted by Torcon. BSA contracted Torcon (Contract 7700000004) to perform the construction of the conventional facilities for the NSLS-II Ring Building. Included in the Contract is the NSLS-II Construction HASP. Also included in the contract is Torcon’s responsibility to ensure these requirements are imposed on all of their contractors at all levels and tiers. To demonstrate understanding of these requirements, Torcon was required to submit a health and safety plan that meets the requirements of the NSLS-II Construction HASP prior to the start of work. Torcon’s Project Safety, Health and Environmental Program was reviewed by NSLS-II, BSA, and DOE-BHSO safety and health professionals and approved on March 17, 2009. A notice to proceed was transmitted by BSA to Torcon on March 25, 2009. Figure 4 provides an illustration of the flowdown of pertinent ES&H requirements as it relates to this accident investigation.
Draft
17
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 4. BSA/NSLS‐II, Torcon, and subcontractor key ES&H requirements and their flowdown with respect to this accident.
Draft
18
December 4, 2009
BNL NSLS-II Accident Investigation
1.4 SCOPE, PURPOSE, AND METHODOLOGY The Accident Investigation Committee began its activities on October 1, 2009 and submitted the final report to the NSLS-II Project Director on December 4, 2009. The charge of the Committee was to: (1) investigate the leg injury incident; (2) review the adequacy of contractual safety requirements and the safety incentive program; and (3) review the implementation of the construction safety program. The Committee identified relevant facts; analyzed the facts to determine the direct, contributing, and root causes of the incident; developed conclusions; and determined Judgments of Need that, when addressed, should prevent recurrence of a similar accident. Charge (1) addresses the accident investigation. Charges (2) and (3) expand the scope of the investigation beyond DOE O 225.1A. The accident investigation was performed consistent with DOE O 225.1A, Accident Investigations. The Laborer was in the Hospital for six days, which requires a DOE Type B investigation. However, on October 7, 2009, Michael D. Holland, Manager, Office of Science Brookhaven Site Office (BHSO), received a Memorandum from Glenn S. Podonsky, Chief Health, Safety and Security Officer, Office of Health, Safety and Security, granting a request by BHSO to allow BSA’s Accident Investigation Committee to complete the investigation with DOE oversight (see Appendix B). The investigation conducted by BSA meets the intent of the Order. The following methodology was used: •
Facts relevant to the accident were gathered through reviews of photographs, measurements of the scene and equipment, obtaining interview statements, and a fact finding meeting held on the day of the accident. Following the first day of the accident additional and follow up interviews, measurements and photographs were performed, as well as the review of additional documents and logs.
•
Facts relevant to the adequacy of the contractual safety requirements, the safety incentive program, and the implementation of the construction safety program, were gathered through interviews, the review of documents, and field observations.
•
Facts were analyzed to identify causal factors using Event and Causal Factors Charting (E&CF), Barrier Analysis and TapRooT®. Facts were also analyzed using the Core Functions and Guiding Principles of Integrated Safety Management (ISM). In addition, ES&H oversight was evaluated against contract requirements.
•
The emergency response was evaluated against procedures and effectiveness in performance.
•
Judgments of Need (JONs) for corrective actions to prevent recurrence of the accident and to improve program weaknesses identified were developed.
Draft
19
December 4, 2009
BNL NSLS-II Accident Investigation
1.4.1
ACCIDENT INVESTIGATION TERMINOLOGY
A causal factor is an event or condition in the accident sequence that contributes to the unwanted result. There are three types of causal factors: direct, which is the immediate event(s) or condition(s) that caused the accident; root cause(s), which is the causal factor that, if corrected, would prevent recurrence of the accident; and the contributing causal factors, which are the causal factors that collectively with the other causes increase the likelihood of an accident but which did not cause the accident. The causal factors related to weaknesses in the five Core Functions of Integrated Safety Management (ISM) are analyzed. Event and causal factors analysis includes charting, which depicts the logical sequence of events and conditions (causal factors that allowed the event to occur), and the use of deductive reasoning to determine the events or conditions that contributed to the accident. Barrier analysis reviews the hazards, the targets (people or objects) of the hazards, and the controls or barriers that Management Systems put in place to separate the hazards from the targets. Barriers may be physical or administrative. TapRooT® is a proven tool used to evaluate causal factors that resulted in equipment and human performance problems. The focus is on the system (the way that the work is performed), not the individual. TapRooT® defines causal factors as any problem associated with the incident that, if corrected, would have prevented the incident from occurring or would have significantly mitigated its consequences.
Draft
20
December 4, 2009
BNL NSLS-II Accident Investigation
2.0 FACTS
2.1 ACCIDENT 2.1.1 DESCRIPTION OF THE ACCIDENT SITE On September 30, 2009, the primary construction activities underway on the NSLS-II site were concrete, site work and utility installation. In the accident area, concrete work being conducted included placing forms and rebar for the vehicle tunnel east retaining wall footings, storage ring tunnel floor slab and storage ring tunnel walls. Site work in progress included grading of the north portion of the site to prepare the entrance drive and parking area near the Lobby, additional pouring of concrete to the east, and earthwork required to support installation of drainage utilities on the north and east sides of the site. Utility installations included extension of water mains to the future fire control room, installation of underground sanitary piping under the Ring Building, and installation of electrical grounding for the footings at the Ring Building column line. Figures 5 and 6 show the site on the day of the accident.
Vehicle Tunnel Accident Site SR Tunnel Wall Forms SR Tunnel Slab
Figure 5. Aerial view of the NSLS-II construction site taken from the BNL HFBR Stack facing southeast, September 30, 2009, at 0800 hours.
Draft
21
December 4, 2009
BNL NSLS-II Accident Investigation
Accident area
Original rebar staging area
Form area
Location of Worker 2 at time of accident
Figure 6. Aerial view taken prior to the accident on September 30, 2009, facing southwest.
2.1.2 DESCRIPTION OF THE ACCIDENT The Accident Investigation Committee has reconstructed the accident as they believe it occurred using interview statements, response logs, reports, physical evidence, and fact finding minutes. Photographs were taken by project, BNL Safety & Health Services Division (SHSD) personnel, as well as members of the Accident Investigation Committee. Physical measurements were taken by SHSD and the Accident Investigation Committee. A survey of the accident site was conducted and documented in a scale drawing (see Appendix H). See Appendix D for an explanation of the footnotes and the reasons why the Accident Investigation Committee concluded the event occurred as described. On September 30, 2009, a rough-terrain forklift (Lull) Operator employed by Macedos started work at approximately 0645 hours by performing his daily inspection and testing of the equipment. The Lull was in good working condition and the Operator had no problem with it.1* At 0700 hours, he began working with carpenters to move material. A Laborer employed by Rebar Steel was directed by the Rebar Steel foreman that morning to prepare some rebar for hoisting by a crane into the form work area. At approximately 0815 hours, the Laborer asked the Operator to move some rebar from a laydown area to a staging area where it could be hoisted by crane. The Laborer, acting as a spotter, was directing the placement of the rebar load by directing the Lull. The Operator and the Laborer moved 6 to 7 loads of rebar to another area before starting to work in the area where the accident occurred. The Laborer identified the rebar bundles to be moved by marking them with orange paint. The Operator and the Laborer indicated that they were not under any unusual pressure to get the job done.
*
See Appendix D for all Footnotes
Draft
22
December 4, 2009
BNL NSLS-II Accident Investigation
The Laborer arranged cribbing in the accident area to support the bundles of rebar.2 The Operator, directed by the Laborer, then moved two bundles of rebar into the area, one with a bend and one bundle of ½ inch rebar.3 The Operator, again directed by the Laborer, moved two bundles of 1 ¼ inch rebar into the area.4 Figure 7 shows the staging of the rebar.
Approximate location of Laborer’s head after the accident
Cribbing placed over rebar
First two bundles placed; one with bend and one ½ inch rebar
This was placed after the accident
Approximate location of Laborer’s leg after the accident
Figure 7. Shows the accident site facing northeast. Note the placement of the cribbing, the two bundles laying on it, and the lack of area to move freely while directing the Lull.
At approximately 0835 hours, a second worker (Worker 2) saw the Operator and Laborer preparing to place a load of rebar onto the ground as he was walking behind a spoil pile to his work area. The Laborer was standing in front of the first two bundles of rebar that were placed in the accident staging area, directing the Operator to position the load.5 The Operator was able to clearly see the Laborer giving hand signals, but the load obscured the Operator’s visibility of the Laborer’s feet and lower legs.6 Figure 8 provides a sketch of how the Accident Investigation Committee believes the Operator’s view was obstructed. Although the Laborer is clearly visible, the location of his lower legs is obscured by the load and the location of the rebar behind his feet cannot be seen. The boom extension was 14 to 18 feet.7
Draft
23
December 4, 2009
BNL NSLS-II Accident Investigation
The Laborer’s lower legs and feet are hidden from view.
Two bundles of rebar, one struck the Laborer’s leg. This sketch shows the load just before the accident while it was being moved.
Figure 8. Operator’s view facing east, looking out of the Lull at the accident area. The Laborer’s location is approximate.
The Laborer was directing the Operator while the load was moving toward him, and signaling the Operator to place the load while walking backwards out of the way. 8 The Laborer’s foot contacted the rebar behind him as he was backing up. He was able to get his left leg out of the way, but tripped over the rebar that was behind him and fell backward.9 At approximately 0840 hours, the load was being placed by tilting the forks downward.10 The bundles were sliding off the forks and one of the bundles struck and laid on the Laborer’s leg while the other remained on the forks.11 The Operator saw the Laborer fall and heard screaming. In an effort to remove the bundle of rebar from the Laborer’s leg, the Operator speared the bundle and tilted the forks up, causing the center wire tie of the bundle to break.12 After the load was lifted, the Laborer rolled onto his stomach. The Operator then exited the cab to see if the Laborer was alright. Worker 2 also heard screaming and ran over to see the Laborer on the ground face down and the rebar above him, part on the forks of the Lull and part off the forks, hanging several inches above the Laborer’s legs.13 After Worker 2 arrived on the scene, the Operator moved the load back further by retracting the boom and by moving the vehicle backwards. He then dropped both bundles of rebar to the ground.14
Draft
24
December 4, 2009
BNL NSLS-II Accident Investigation
2.2
EMERGENCY RESPONSE
At 0845 hours, BNL’s Laboratory Protection Division received a phone call via BNL’s emergency reporting number, extension 2222, from Torcon’s Safety Manager advising of an injured worker with an “injury to leg perhaps serious” at the NSLS-II construction work site and the need for an ambulance. At 0846 hours, BNL Fire Rescue’s Car 1, Heavy Rescue Truck, and the Kubota RTV (equipped for patient transport from remote locations), were dispatched to the accident location given. BNL Security also responded to the call. The BNL Ambulance was at the BNL Motor Pool for routine servicing when the call was received. The Motor Pool was notified and the Ambulance was prepared and waiting for the responding crew, who picked up the Ambulance and proceeded to the scene. In parallel, Torcon’s site Emergency Medical Technician (EMT) was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing emergency treatment. A site worker was waiting at the entrance gate to guide the BNL responding vehicles onto the site to where the injured Laborer was located. Upon arrival at the scene, the Fire Captain in Car 1 took control of the accident as the Incident Commander. The Incident Commander notified Suffolk County Police Department (SCPD) aviation in case a helicopter was needed to transport the injured worker. The BNL EMT’s were at the scene within four minutes of the initial call. Upon arrival, they relieved Torcon’s EMT and took custody and control of the injured worker. The BNL Ambulance arrived shortly afterwards. The Injured was evaluated and then prepared for transport. At that time, the Incident Commander and the EMTs who were treating the patient determined that the estimated arrival time of the SCPD helicopter was too long and they would transport the injured worker to Stony Brook University Medical Center (Hospital) via the BNL Ambulance. BNL Ambulance is New York State (NYS) Certified and operates as a basic life support (BLS) unit. Qualifications for a BLS provider include: training to the level of EMT, Defibrillation (EMT-D), and a current NYS Department of Health Certification as an EMT. The NYS Department of Health Bureau of Emergency Medical Services Policy Statement No 98-09, dated 09/01/98, establishes a policy for Advanced Life Support (ALS) intercepts. An Intercept is a staffed unit (person and equipment) that is picked up by the BLS unit while it is en route to the nearest appropriate hospital. If the Intercept is not at the designated point when the BLS unit arrives, the BLS continues on to the hospital without the Intercept, the BLS will not wait for the Intercept. For this accident, the BNL Fire Rescue transport crew initiated the ALS protocol with Suffolk County via radio. Suffolk County dispatched a certified ALS provider to meet the BNL Ambulance on the service road of the Long Island Expressway on route to the Hospital. Pick-up of the ALS provider took less than 20 seconds, as stated by the Chief of Fire Rescue. The Ambulance then continued on to the Hospital. If the ALS provider had not been available, or had not been at the designated area when the Ambulance arrived, the Ambulance would not have stopped and would have continued to the Hospital without the ALS. Per the Chief of Fire Rescue, the actual care the ALS provided falls under the Health Insurance Portability and Accountability Act (HIPAA) and could not be disclosed to the Accident Investigation Committee without the injured worker’s permission, which the Committee was not given. Draft 25 December 4, 2009
BNL NSLS-II Accident Investigation
The Ambulance arrived at the Hospital Emergency Room at 0936 hours and the Injured was transferred to Hospital emergency room staff. After leaving the Hospital, the BNL Ambulance crew returned the ALS provider to his station and returned to BNL at approximately 1030 hours.
2.3 CHRONOLOGY Table 1. Chronology of the Accident and Response
Time
Event
(if it was possible to determine)
Laborer arrives at site and attends orientations. Operator arrives at site and attends orientations. Sept. 16, 2009 Sept. 30, 2009 The remainder of this event takes place on September 30, 2009 0645 hours Operator starts work by performing his daily inspection and testing of equipment. 0700 hours Operator begins to move material for carpenter. Rebar Steel Foreman directs Laborer to prepare rebar for movement by crane into form area. Laborer marks rebar bundles to be moved by spraying them with orange paint. 0815 hours Laborer asks Operator to move rebar with Lull. Laborer, acting as a spotter, directs placement of six to seven loads moved. Laborer places cribbing for rebar to be placed onto. Laborer directs placement of two bundles moved into the incident area. Laborer directs placement of two additional bundles (2,467 lbs. 23 pieces, 24’10” long). 0835 hours As Worker 2 walks by, he sees Operator and Laborer working to lay down rebar. Lull stopped. Boom of the Lull extended to permit load to be placed. Laborer stands in front of two bundles of rebar, in front of the Lull. Laborer signals Operator to place load. Operator tilts forks to place load while Laborer steps backwards to move out of the way. Load slides off the forks of the Lull while the back of Laborer’s foot contacts rebar behind him. Laborer trips over rebar. 0840 hours Rebar strikes lower right leg of the Laborer. 0840 hours Laborer’s right lower leg is fractured. Operator, in response to screams, picks up rebar bundle with the Lull. Sept. 1, 2009
Draft
26
December 4, 2009
BNL NSLS-II Accident Investigation
Time
Event
(if it was possible to determine)
0845 hours 0848 hours 0848 hours 0901 hours 0915 hours Approx. 0915 hours 0936 hours 0944 hours 0946 hours Approx. 1030 hours Approx. 1200 hours
Laborer rolls onto stomach. Operator exits Lull to see if the Laborer is alright. Worker 2, hearing scream, arrives at scene. Operator enters Lull to further retract boom and backs up Lull 6 to 9 feet. BNL Emergency number x 2222 called for Ambulance. BNL Fire Rescue responds. Local (Pembrooke) EMT arrives at scene. Fire Rescue and Security arrive at scene. BNL Ambulance arrives. Ambulance leaves accident site with injured Laborer. Ambulance picks up Advanced Life Support (ALS) provider en route to Hospital. BNL Security secures accident site. Operator leaves BNL. Ambulance arrives at Hospital. Event declared reportable to DOE. Operator returns to BNL for the day. BNL Ambulance returns to BNL. Operator leaves BNL.
2.4
ENVIRONMENTAL CONDITIONS
The recorded temperature for September 30, 2009 at 0900 hours was approximately 55 degrees Fahrenheit, with a wind speed of approximately seven miles per hour from the northwest. There was no recorded precipitation for the day (see Appendix I). The incident area possessed a one percent grade towards the northeast. The soil was composed of sand and clay, was moist and compacted. No water accumulation was observed in the incident area on the day of the accident.
Draft
27
December 4, 2009
BNL NSLS-II Accident Investigation
2.5
OPERATOR TRAINING AND QUALIFICATIONS
The Operator of the Lull was a Journeyman in the International Union of Operating Engineers, Local 138 (Farmingdale, NY), and had over thirty-five years of experience as an Operator of cranes and powered industrial trucks. A summary of his training and qualifications is as follows: • • • • •
New York State Crane Operator – Class A; Expiration August 31, 2012; New York City Department of Buildings Hoist Machine Operator – Class A; Expiration February 28, 2012; International Union of Operating Engineers, Local 138 – 138A – 138B Powered Industrial Trucks; dated 4/02, Refresher Expiration April 2011; International Union of Operating Engineers OSHA 10-Hour Construction Safety & Health Training; dated 5/21/2008; International Union of Operating Engineers OSHA 29CFR1910.120 40-Hour Hazardous Waste Training; Refresher Expiration March 2010.
A review of the training curriculum provided by Local 138 contains the following as it applies to this incident: • •
•
Operator must read and understand the Operator’s Manual for each truck they operate, including warning decals. Instructions for operating around other personnel, including the use of a spotter. In addition, if you use a spotter and you can’t see him or a clear path of travel does not exist, don’t move the truck. From the practical driving test, the following skills are assessed: o Were the loads handled without bumping? o Were the loads centered on the forks? o Were the loads kept low to the ground? o Ability to judge proper clearance all-around when turning.
In addition, the Operator attended BSA’s Contractor Vendor Orientation (CVO) and Torcon’s Project Safety Orientation classes, which are not skill based.
2.6 LABORER TRAINING AND QUALIFICATIONS The Laborer was a member of Laborers’ Local 66, International Union of Operating Engineers, as a Journeyman since September 2009. He was employed by Rebar Steel for the NSLS-II project since September 2, 2009. Rebar Steel provided the following experience and qualifications for the Laborer (see Appendix L): Yardman • • • • • Draft
Moved and disbursed reinforcing steel to different locations. Construction, dismantling and knockdown of shanties on both hi-rises and infrastructures. Mechanic for small engines. Operated forklift - Lifting of materials in the shop yard. Operate and maintain diesel powered stud welding machine. 28 December 4, 2009
BNL NSLS-II Accident Investigation
• • • •
Shoots metal shear studs into Q decking of superstructures. Taught hand signals by job super. OSHA 10 hour Certificate. Weekly Tool Box Talk.
The Union Hall stated that the Laborer was not with them long enough to start any of their training. The Laborer attended BSA’s Contractor Vendor Orientation (CVO) and Torcon’s Project Safety Orientation classes, which are not skill-based. Discussions held by a member of the Accident Investigation Committee and the Long Island Business Agent for Local 66 revealed an employer can request by letter that the Union accept a person the employer wants to sponsor as a full Journeyman. The employer advises the Union that the candidate has all the necessary training to be a Journeyman (approximately 4,000 hours of experience). The employer may have to document time worked for the person by providing “pay stubs” for the previous 4 years worked. A Journeyman is capable of independent work. The Business Agent indicated that Rebar Steel made such a request for the Laborer, which was granted by the Union.
2.7 FORKLIFT SPECIFICATIONS
The power fork lift that was used to move the rebar was a JLG Industries Lull Telehandler Model 1044C54, serial number 0160033803, manufactured in 2008, with 1391 hours on its meter. The rated capacity of this vehicle at 24 inches load center is 10,000 pounds. Its maximum reach is 45 feet with a capacity of 1,500 pounds. Following the accident, the equipment was inspected by BNL’s Hoisting & Rigging Inspector and then by an authorized representative of the manufacturer, both found the equipment and its forks to meet all requirements for the applications. The boom length after the accident was approximately 13 feet. The load capacity for this boom length is 6,000 pounds. At 18 feet, the capacity limit for the Lull is 5,000 pounds. A load of 2,467 pounds for one bundle, or a load of 4,934 pounds for two bundles, was well within this rated capacity.
Draft
29
December 4, 2009
BNL NSLS-II Accident Investigation
3.0
ANALYSIS
The Accident Investigation Committee applied several analytical techniques to determine the causal factors of the event. They included Barrier Analysis (BA), Events and Causal Factors Charting (E&CFC), TapRooT (TR) and were analyzed using the Guiding Principles and Core Functions of (ISM). Causal factors from each technique were grouped under one common causal statement with supporting information following. Each cause is keyed to Tables 3 and 4 in Section 4.0 (see p. 62), which summarize the event causes, provide the analytical technique that was used to establish the cause, and identify the associated Judgment of Need. In addition, a Human Factors Scientist reviewed the accident description and these analyses to ensure Human Performance Improvement was incorporated in the results. The Accident Investigation Committee also analyzed the adequacy of Torcon’s safety plan implementation and flow down to subcontractors, as well as the adequacy of BSA’s oversight of Torcon (as per its charter) using the above results. The Committee limited this analysis to those processes and systems that were reviewed during the performance of the accident investigation. Therefore this report should not be interpreted as a full analysis of the entire Management System. There are two specific areas that warrant further discussion due to their significance in how the Accident Investigation Committee determined the events leading to the accident occurred: the use of a spotter and hand signals, and the Laborer’s statement about getting stuck in the mud. These two topics are discussed in detail in Section 3.1. A summary of the interview statements submitted by the Laborer, Operator, and Worker 2, arranged chronologically, is provided as Appendix C.
3.1
ANALYSIS OF CONFLICTING STATEMENTS
3.1.1 SPOTTER AND HAND SIGNALS This section is an analysis of the events immediately preceding the accident. In this event, the operator of the Lull, a rough terrain forklift, was being guided or directed by a “spotter” or signal person. A spotter or signal person is used in material handling industries whenever an equipment operator’s visibility for the placement of a load may be impaired or obscured. Neither OSHA standards nor ANSI standards address requirements for spotters and only provide the following with respect to visibility for operating a forklift near personnel: •
Do not drive a truck up to anyone standing in front of an object.
•
If the load being carried obstructs forward view, travel with the load trailing.
In this case, neither requirement was applicable to the accident. However, both the manufacturer’s Lull Operator & Safety Manual (1) and the Association of Equipment Manufacturer’s Rough Terrain Forklift Safety Manual (2) retrieved from the cab of the incident forklift provided the following regarding use of a spotter:
Draft
30
December 4, 2009
BNL NSLS-II Accident Investigation
(1) Lull Operator & Safety Manual •
Before Operating the Machine o
o
Plan your work
Before you operate, know how and where you will travel, turn and pickup, lift and place loads.
If you will be placing loads at high elevations, remember your depth perception is decreased because of distance. Use a signal person near the point where the load is to be landed. [emphasis added]
Know the Rules
Make sure you understand all hand, flag, whistle, siren, or bell signals.
(2) Association of Equipment Manufacturers Rough Terrain Forklift Safety Manual •
Know the Rules of Operation o
Make sure you know and understand:
•
•
Hand, flag, whistle, siren or bell signals.
Plan Your Work o
Know the weights of all loads you may be expected to transport before attempting to lift them. Avoid loads of loose material if possible. Check that loads are properly banded or strapped together.
o
If you will be placing loads in landing areas where visibility is a problem, use a signal person near the point where the load is to be landed.
Operate Safely o
Transporting the Load
Carrying the load as low as possible and fully retracted will: •
o
Watch clearances carefully when handling loads that are long, tall or wide. Load end-swing can be deceiving and could cause injury to personnel or damage to objects nearby.
Lifting and Placing the Load
Now that the load has been transported to the location where it is to be placed, remember: •
Draft
Allow for better visibility over the load.
While lifting or lowering always make sure the path of the forks or load is clear of obstacles. 31
December 4, 2009
BNL NSLS-II Accident Investigation
The very reason a spotter is used in material handling evolutions is to assist the equipment operator in situations where visibility may be impaired. Visibility could be impaired by elevation and/or distance, other objects, or the load itself. Other reasons for a spotter could be precision, in that the location requires placement within inches or fractions thereof, which is not possible to accomplish from the operator’s position. In this accident, the Laborer was serving as the spotter and directing the Operator of the forklift to place loads in a position where they could be later hoisted with a crane. This required placement within reach by the crane, and proximity to the other bundles to be hoisted. The incident bundles also were very long - over 24 feet – so clearance was an issue along the path of travel. Through analysis of this accident, the Accident Investigation Committee determined that only the Laborer was responsible for placing the load where it was because he was performing the duties of the spotter or signal person. It is incontrovertible that the Laborer was performing this function because it appears in the statements of both the Operator and the Laborer. Figure 8 (page 24) shows that the load would partially obscure the Operator’s visibility forward of the load on the forks, and particularly the placement of the load. Therefore, the Operator had to rely upon the Laborer’s signals to place the load in the desired location. Figure 8 also clearly shows that the Laborer was visible to the Operator, and the Operator could see the hand signals being given by the Laborer. In fact, the Operator, in both of his statements indicated he was following the signals of the Laborer, and in one statement said he had no problems with visibility (Operator Statement #2). Therefore, there is no evidence that the Operator was moving the load without being able to see the Laborer. The Operator also stated in both statements that the Laborer was standing approximately 5 feet in front of the forks (Operator Statement #1) or 5 feet from where the load was to be dropped (Operator Statement #2). At least this was his perception of the location of the Laborer. His perception that the Laborer was 5 feet away from the forks or the intended placement of the load indicates that the Operator believed the Laborer was a safe distance away from the travel path of the load. Therefore the Operator did not knowingly begin placement of the load with the Laborer in the intended or perceived path of the load. There is some disparity between the Operator’s statements regarding the actions of the Laborer and the Laborer’s statement regarding his actions. In both statements, the Operator indicated the Laborer was standing on bundles of rebar just prior to being struck by the load, and in the first statement he indicated the Laborer backed up to move out of the way of the rebar. This correlates with the Laborer’s statement that he was in the process of “backing up out of the way.” As discussed in footnote 8 to the Accident Description, Section 2.1.2 (pages 22 and 88), the Accident Investigation Committee believes that the Laborer gave a “down” or “tilt down” signal to the Operator in anticipation that he would be out of the way of the load in a couple of steps while he was walking backward. Again, the Laborer, performing the duties of a spotter or signal person, is in the best location to determine where he would be with respect to the load, because the Operator’s visibility is partially obscured. The Laborer’s proximity to the load is consistent with good and accepted safe practice as the Lull Operator’s Manual states to “Use a signal person near the point where the load is to be landed.” It would not be reasonable for the Operator to question the Laborer’s hand signal to place the load if 1) he has a spotter or signal person directing his actions, and 2) the Operator perceived the Laborer was 5 feet from the path of the load. There is no other evidence to the contrary. This is where the Accident Investigation Committee attributes causation to the Laborer because he gave a “down” or “tilt down” signal to the Operator in anticipation that he would be out of the way of the load in a couple of steps while he was walking backward. Therefore, based upon the evidence available, the Accident Investigation Committee can only conclude that the Laborer imprudently gave a “down” or “tilt down” signal to the Operator while he was in the way or path of the load, with the Operator lacking the visual clarity necessary to determine that the Laborer was not a safe distance away – which is why he was using a spotter or signal person. It is possible, and in fact likely, that the Laborer would have been out of the path of the load but for the rebar that he tripped over. Since the Laborer had Draft
32
December 4, 2009
BNL NSLS-II Accident Investigation
placed that rebar at that location within minutes of the accident, the Accident Investigation Committee found the work area organization a contributing cause to the accident, one that is also attributable to the Laborer, primarily due to his lack of training and qualification. Also discussed in footnote 8 to the Accident Description, Section 2.1.2, the Accident Investigation Committee believes that the Laborer gave a “down” or “tilt down” signal to the Operator, and that inconsistent use of hand signals at the construction site is not a possible contributing cause to this accident. The Accident Investigation Committee reached these conclusions considering several facts or the lack thereof. The Operator has several operating engineer licenses and training certificates, as well as many years of construction site experience. The Laborer, however, has mostly yard experience and nonmaterial handling construction experience, and no licenses or operating engineer training, as evidenced by the letter of “experience” provided by Rebar Steel Corporation. The Laborer’s statement regarding the Operator’s previous unexpected response to hand signals is not evidenced by other means. The Laborer did not tell anyone else of these experiences, and construction site management has no record or recollection of this issue. The Operator states he had previously worked with the Laborer and others before the day of the accident and had no trouble understanding the Laborer’s signals. The Operator indicated there are several hand signal methods used on site and he had no problem with any of them. As a crane operator as well as a forklift operator, the Operator would have had training and experience with different signals. The Accident Investigation Committee also evaluated the crane and forklift hand signals and does not believe that a crane stop signal could be misinterpreted as a tilt hand signal. Members of the Accident Investigation Committee have seen the crane stop signal used on the construction site with equipment other than cranes with no indication of misunderstanding between operators and spotters.
3.1.2 MUD The Laborer stated that, immediately prior to the accident, his foot became stuck in mud as he was backing up. The members of the Accident Investigation Committee that responded to the accident site within an hour of the accident did not find mud at the accident site. Figure 9 shows there were no footprints (indents in mud) at all in the area, even from emergency responders. The precipitation report for the month of September shows that there were 1.39 inches of precipitation on September 27, 2009 and 0.12 inches of precipitation on September 28, 2009 (see Appendix I). The area of the accident has been significantly excavated and reshaped, and the normal soil for the entire Long Island area as well as the site is Class C, or sandy soil. In addition, there were 0.74 inches of precipitation on October 3, 2009, and the Accident Investigation Committee on that day did not find any evidence of viscous mud that would trap an individual’s footwear. The rebar was slightly elevated and narrow in diameter, and its contact with the Laborer’s footwear might feel like the foot was stuck, but lateral motion would still be possible, which is consistent with the Laborer’s statement that he was able to get his left foot out of the way. (See also Figures 11 and 16.) For these reasons the Accident Investigation Committee concludes that the Laborer tripped over the rebar and his foot was not stuck in mud.
Draft
33
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 9. Photo taken on September 30, 2009, at approximately 0940 hours. The oval shows the approximate area where the Laborer was standing at the time of the accident. Note that the area is clear of mud and there are no signs of footprints even after emergency response efforts.
3.2
BARRIER ANALYSIS
Barrier Analysis is based on the premise that hazards are associated with all tasks. Barriers are any management or physical means used to control, prevent, or impede the hazard from reaching the target (person or object that a hazard may damage). For an accident or event to occur, there must be a hazard that comes into contact with a target because the barriers or controls were not in place, not used, or failed. The results of the Barrier Analysis are used to support the development of causal factors. Appendix E contains the analysis of the physical and administrative barriers that could have had an impact on this accident and how they performed.
3.3
TAPROOT ANALYSIS
TapRooT® System is a systematic tool used to determine causal factors contributing to equipment and human performance problems. The focus is on the system (the way that the work is performed), not the individual. An analyst, with a small team (for this event, the Accident Investigation Committee) objectively looks at the facts, identifies the problem, and goes through a systematic process to find causes. Software is utilized that documents and assists in the causal analysis process. In this accident investigation, causal factors were identified using E&CFC. TapRooT was then used to analyze each causal factor to determine contributing and root causes. The results of the TapRooT Analysis are provided as Appendix F.
Draft
34
December 4, 2009
BNL NSLS-II Accident Investigation
3.4
EVENT AND CAUSAL FACTORS ANALYSIS
The E&CFC process produces a cause and effects diagram that describes the time sequence of events and the surrounding conditions leading to an event. The purpose of the E&CFC is to identify causal factors. 'A Causal Factor is any problem associated with an event that, if corrected, would have prevented the event from occurring or would have significantly mitigated its consequences' (Taproot, by M. Paradies and L. Unger, 2000). For this accident, the E&CFC created by the Accident Investigation Committee begins with work commencement on the day of the accident and ends shortly after the BNL Ambulance returned to the Laboratory. See Appendix G for the Events and Causal Factors Chart.
3.5
PROJECT OVERSIGHT
The Accident Investigation Committee was tasked to evaluate the ES&H systems and processes in place leading up to the incident to determine if Torcon and NSLS-II oversight was adequate to identify deviations or weaknesses in implementation of the ES&H Program and correct them in a proactive manner. This was accomplished by evaluating the requirements in Attachment A of the Contract, which is entitled Brookhaven Science Associates, LLC General Terms and Conditions for NSLS-II Conventional Construction at Brookhaven National Laboratory, as they pertain to this accident investigation. Two specific Articles in Attachment A provided key requirements for evaluating the performance of the NSLS-II ES&H program implementation. The first was Article 43, Compliance with 10 CFR 851 and Brookhaven Science Associates’ Worker Safety and Health Program by Integration of Environmental, Safety, and Health into Work Planning and Execution. The second was Article 16, Suspect/Counterfeit Items. Although Attachment A contains other Articles that involve ES&H, Articles 16 and 43 are most pertinent to understanding the root and contributing causes to this accident and/or weaknesses to the ES&H Program. Figure 4 provides an illustration of the flowdown of these ES&H requirements. The following sections are organized to provide a review of the pertinent requirement, followed by an analysis of its implementation and the results of that review.
3.5.1 ANALYSIS OF CONTRACT ATTACHMENT A, ARTICLE 43 Review of Requirement Article 43, Compliance with 10 CFR 851 and Brookhaven Science Associates’ Worker Safety and Health Program by Integration of Environmental, Safety, and Health into Work Planning and Execution, requires the contractor to comply with 10 CFR 851 and BSA’s (the Laboratory’s) Worker Safety and Health Program by integrating environmental, safety, and health into work planning and execution. It requires Torcon and all of its subcontractors at all levels to comply with all federal, state, and local environmental, safety, and health laws and regulations applicable to work at the NSLS-II site. The general contractor and all of its subcontractors at all levels are also required to comply with 10 CFR 851 (DOE Worker Safety and Health Program), the Laboratory's Worker Safety and Health Program, and Draft 35 December 4, 2009
BNL NSLS-II Accident Investigation
DEAR 970.5223-1, entitled Integration of Environmental, Safety and Health into Work Planning and Execution, dated December 2000. Specifically, Article 43 (b) states that the contractor shall perform work safely, in a manner that ensures adequate protection for employees, the public, and the environment, and will be held accountable for the safe performance of work. It further states that the contractor is to exercise a 'degree of care' commensurate with the work and the associated hazards and ensure that management of ES&H functions and activities becomes an integral and visible part of the work planning and execution processes. The contractor is to submit a Construction ES&H Plan before work commencement that conforms to the NSLS-II Construction ES&H Plan (i.e., the NSLS-II Construction HASP). The Plan must ensure the following during the performance of work: (1) Personnel possess the experience, knowledge, skills and abilities that are necessary to discharge their responsibilities, and will retain records respecting such competency and qualifications, making them available upon request. (2) Prior to work performance, the associated hazards will be evaluated and a set of ES&H standards and requirements will be established and implemented to provide assurance that employees, the public, and the environment are protected from adverse consequences. (3) Line management is responsible for the protection of employees, the public, and the environment. Line management includes those contractor and subcontractor employees managing or supervising employees performing work. (4) Clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance will be established and maintained at all organizational levels.
Analysis of Requirement Torcon was required to submit an ES&H plan that meets the requirements of the NSLS-II Construction HASP prior to the start of work. Torcon submitted their Project Safety, Health, and Environmental Program (Torcon’s SHE Program) to satisfy this requirement. It was reviewed by NSLS-II, BSA, and DOE-BHSO safety and health professionals and approved on March 17, 2009. A notice to proceed was transmitted by BSA to Torcon on March 25, 2009. Highlights of Torcon’s SHE Program include: •
• •
Draft
A written Project-Specific Safety Plan that includes a statement from the subcontractor regarding the scope of work on the NSLS-II project, and Phase Hazard Analyses for all major tasks involved in the scope of work for the project, and the name(s) of the responsible supervisor(s) for safety issues. A copy of the subcontractor’s Corporate Safety Program. A letter from all Torcon’s subcontractors, on the subcontractor’s company letterhead, including the following statements: o That all of their workers have received all required safety training for their jobs. o Name of subcontractor’s representative to the Labor/Management Safety Committee for the project. o Name of subcontractor’s competent supervisor(s) for safety issues on the NSLS-II site. This supervisor must possess the OSHA 30-Hour Course. The subcontractor is also required to provide the name and telephone number of the subcontractor’s Safety Director or chief safety officer. 36
December 4, 2009
BNL NSLS-II Accident Investigation
• •
•
Documentation that the subcontractor’s competent supervisor for safety issues on the site has completed the OSHA 30-Hour Course in Construction Safety. After the subcontractor submits the Project-Specific Safety Plan with PHA’s to the Torcon Safety Manager, a pre-construction meeting is held. At this meeting, safety requirements for the subcontractor’s scope of work are discussed and guidance provided for any changes needed in the PHA’s. Any questions regarding safety or administrative aspects of the job are clarified. Every worker and supervisor on the project is required to attend the BNL Contractor Vendor Orientation (CVO) and the Torcon Project Safety orientation on his/her first day on the project. No one is permitted on the project site before completing both orientations, except for approved and escorted visitors.
The Accident Investigation Committee also reviewed Macedos’ (Torcon’s subcontractor) site specific construction safety plan. Highlights of the plan include: •
• • • • • • •
Macedos’ commitment to provide adequate training to employees, and employees’ responsibility to ask a qualified person for assistance if the employee is in doubt about how to do a job or task safely. Senior management’s responsibility to support and monitor the safety, health, and risk management process. All employees must comply with safety, health, and risk management requirements. Identification of personnel having the authority for implementing the provisions of the safety plan. The responsibility of all supervisors for implementing and maintaining the safety plan in their work areas and for answering worker questions about the safety plan. Major safety hazards/risks and exposures must be assessed and documented in the PHA’s. Daily inspections are required. Macedos’ system for ensuring that all workers comply with the rules and maintain a safe work environment includes: o Informing workers of the provisions of the safety plan. o Evaluating the safety performance of all workers. o Recognizing employees who perform safe and healthful practices. o Providing training to workers whose safety performance is deficient. o Disciplining workers for failure to comply with the safety and healthful practices.
Result of Analysis The Accident Investigation Committee determined that Torcon and its subcontractors failed to implement the contractual requirement to ensure personnel possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities. Based on the work experience provided by Rebar Steel for the Laborer and the layout of the staging area, the Accident Investigation Committee determined, supervision failed to ensure the Laborer was qualified to perform the work safely. The Accident Investigation Committee has determined the following root cause to this accident: Root Cause Statement (RCE-1): Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities. •
Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.
Draft
37
December 4, 2009
BNL NSLS-II Accident Investigation
The Accident Investigation Committee further determined that Torcon failed to meet the contractual requirement for “clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance will be established and maintained at all organizational levels” for the following reasons: •
Torcon was not able to produce an organizational chart or documented roles and responsibilities that were in effect at the time of the accident.
•
Interviews conducted by members of the Accident Investigation Committee with subcontractor supervisors revealed that supervisors believe investigations and toolbox training to be the responsibility of the safety staff and not theirs, though responsibility is clearly stated in the Torcon SHE Program.
•
Interviews conducted by the Accident Investigation Committee with Torcon and its subcontractors did not identify the individual responsible for requesting drug and alcohol screening after an accident. After this accident the Operator was not requested to undergo screening until after he had left the site, over 3 hours after the accident.
•
Torcon was not able to provide documented roles and responsibilities for their Safety Manager.
As a result of this analysis, the Accident Investigation Committee has determined the following is a contributing cause to weaknesses in the implementation of the ES&H Program: Contributing Cause Statement (CCW-1): Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels. •
Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site.
•
Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations.
•
Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager.
Review of Requirement Attachment A, Article 43 (c) states the contractor, must perform and manage work in accordance with BSA’s DOE-approved Integrated Safety Management (ISM) Program and demonstrate through documentation and work practices that its performance of work under the contract: 1) fulfills the scope of work as outlined in the contract; 2) identifies and analyzes specific, task-level hazards associated with the work; 3) develops and implements hazard controls related to the hazards; 4) allows the performance of work within the controls; and 5) provides feedback on the adequacy of hazard controls and continues improvement in safety management as detailed in their ES&H Plan. Section 4 of Torcon’s SHE Program provides their commitment to integrate safety into every phase of the project, from concept through completion of construction. Torcon states they will achieve this by using the ISM System set forth in BNL’s Construction Safety Plan, National Synchrotron Light Source II Draft
38
December 4, 2009
BNL NSLS-II Accident Investigation
Construction Environment, Safety and Health Plan for Conventional Construction of the Ring Building; Doc #LT-EHS-0006/Rev 1. Torcon’s SHE Program describes the five core functions of ISM. It also puts into place the requirements and processes to ensure contractors and their subcontractors have received all the required safety training for their jobs to perform work on the NSLS-II site, but does not provide criteria for said training Attachment A, Article 43 (d)(1) requires the contractor to demonstrate safety protocols applicable to the scope of work that are well-established and consistent with the requirements of the Laboratory's ISM program, prior to the initiation of work. Prior to commencement of work on any major separately definable activity, Torcon must (1) submit a Phase Hazard Analysis (PHA) of the affected work, (2) ensure workers are aware of foreseeable hazards and protective measures described within the PHA, and (3) require that the workers acknowledge being informed of the hazards and protective measures associated with the work activity. NSLS-II Construction HASP, Section 7.1, Job-Specific Work Requirements, states that PHAs shall be developed for each major phase of the Project to be performed on site, but does not define “major”. The PHA shall identify the task and the steps necessary to complete the task, the hazards associated with each step of the task, and the means to protect the workers performing the task from those hazards. It goes on to say that supervisors and employees are responsible for developing the PHA of their work activities. The supervisor is also responsible for ensuring that hazard analyses are developed and reviewed by the employee before work begins. Torcon is required to submit all PHAs to the NSLS-II ES&H Manager, or designee, for review and approval. The completed and approved PHA shall be reviewed with all personnel involved in the task. Torcon’s Project Orientation and General Safety & Health Rules pamphlet is reviewed with each employee during their orientation on the first day on the site. This pamphlet includes discussions on General Safety Rules, Ten Top Tips for Safety, Phase Hazard Analysis, Personal Protective Equipment, and much more. Each employee signs an acknowledgment that states “I have reviewed Torcon’s Project Orientation and General Safety Rules for the Brookhaven National Laboratory NSLS-II Project. I agree that a safe jobsite makes good sense for everyone and will act accordingly. I agree to report any accident in which I am involved to the superintendent/foreman of my employing subcontractor immediately after the incident. I also agree to report any unsafe condition or “near miss” potential injuries which are a result of unsafe conditions or circumstances. I will be responsible for strict observance of Department of Energy, OHSA and Torcon Rules & Regulations.” Torcon’s SHE Program, Section 11, Pre-Planning of All Construction Work (PHA’s), requires that each of their subcontractors break the scope of their work down into major jobs to be performed by their workers and write a PHA for each job. Once the PHAs have been reviewed and approved by Torcon and NSLS-II ES&H, the PHA must be reviewed by the foremen with their workers in the field. Each worker is required to sign off on the PHA form indicating that he has reviewed the requirements and will abide by them during the work. If job conditions change during the work, requiring deviation from the original PHA, the Torcon Superintendent or Safety Manager requires an addendum to the PHA or a new PHA be completed, reviewed, and signed before work can continue.
Draft
39
December 4, 2009
BNL NSLS-II Accident Investigation
Analysis of Requirement The Accident Investigation Committee determined that the Torcon’s Project Orientation and General Safety & Health Rules provides an adequate safety orientation for the project. In addition, Torcon was able to provide signed acknowledgements of review and agreement with the pamphlet for the Laborer and Operator. The Accident Investigation Committee requested a PHA for the work performed by the Laborer and Operator on the day of the injury and was provided with a Macedos’ PHA entitled “All Footings, revised 6/29/09.” This PHA included a job step entitled “Materials pick up w/forklift” and identified one potential hazard, “Dropping/Misplacement Pinchpoints”. The “Preventive or Protective Measures to Be Used” column of the PHA identified the following: 1) flagman direction/horn warning, 2) cordoned off area with caution tape, and 3) spotter will work with forklift. This was the only PHA provided by Torcon that analyzed hazards associated with forklifts. The copy reviewed was not signed by Torcon. There was no place for NSLS-II ES&H to sign the form. However, NSLS-II ES&H indicated that they review all PHAs they receive and usually there are several iterations before they are accepted. The Field Supervisor (employed by Macedos) signed the PHA on July 15, 2009. Nine workers signed the PHA (undated). However, neither the Laborer nor the Operator had signed it.
Results of Analysis The Committee also determined that the PHA lacked specificity in that it was less-than-adequate to identify hazards associated with moving rebar and is a root cause of the accident. Root Cause Statement (RCE-2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Hazard analyses are required for major phases of the project. However, major phases were not defined.
•
Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”.
The Accident Investigation Committee determined that Torcon and its subcontractors failed to fully implement Article 43 (d)(1) of the Contract by not making workers aware and acknowledge hazards and associated measures for their safety and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
•
Draft
Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers. Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11.
40
December 4, 2009
BNL NSLS-II Accident Investigation
Review of Requirement Attachment A, Article 43 (d)(2) requires the contractor to employ a designated ES&H representative with no collateral duties on the worksite. The ES&H representative is to be knowledgeable of the project’s hazards and has authority to act on behalf of the contractor. The ES&H representative must have appropriate training and qualification to perform this function. This person must, as a minimum, have completed the 30-hour OSHA Construction Safety Course and be a Certified Safety Professional, Certified Industrial Hygienist, or have equivalent documented education and experience in construction safety. This section requires the designated ES&H representative to make frequent and regular inspections of the worksite to identify and correct any instances of noncompliance with the project safety and health requirements.
Analysis of Requirement Torcon has assigned a full time Safety Manager to the project. A review of the Safety Manager’s resume indicated that he possesses a Masters Degree in Safety Management, completed the 40-hour OSHA Construction Safety Course, and has the necessary experience in compliance with Article 43 (d) (2). Though the Accident Investigation Committee did not identify any collateral duties for the Safety Manager, we were unable to obtain his roles and responsibilities to fully evaluate his duties. The Accident Investigation Committee reviewed Torcon’s Project Safety Evaluation records documenting Torcon’s daily safety inspections. Some Project Safety Evaluation forms were completed, while others were not, and some work periods were missing altogether. Objective evidence was not available to indicate whether these inspections had actually taken place daily as required by Article 43 (d)(2).
Results of Analysis The Accident Investigation Committee therefore determined that Torcon failed to ensure Section 23 of Torcon’s SHE Program was being adequately implemented and therefore did not fully meet the requirements of Article 43 (d)(2) and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Torcon’s Project Safety Evaluation forms were not completed correctly and some work periods were missing altogether. Objective evidence was not available to indicate whether these inspections had actually taken place daily as required by the contract.
Review of Requirement Attachment A, Article 43 (d)(3) requires workers be instructed to report any hazard not previously identified or evaluated to the Project Superintendent or the Contractor’s Safety Manager. If immediate corrective action is not possible or the hazard falls outside the project’s scope, the contractor must immediately notify affected workers, post appropriate warning signs, implement needed interim control measures, and notify the NSLS-II ES&H Manager of the action(s) taken. The contractor or its designated ES&H representative must stop work in the affected area until appropriate protective measures are established. The contractor’s ES&H representative is required to document the condition and the corrective action in their inspection report. Draft
41
December 4, 2009
BNL NSLS-II Accident Investigation
Analysis of Requirement Torcon’s Project Orientation and General Safety & Health Rules pamphlet, General Safety Rules, 2, states that employees are to report all unsafe practices or conditions to their Foreman and/or Torcon immediately. In addition, this pamphlet provides a section that discusses PHAs and employees’ responsibility to review and sign them. Each employee signs a copy of this pamphlet acknowledging receipt; signed copies of this pamphlet were provided for the Laborer and Operator.
Results of Analysis The Accident Investigation Committee has determined that this is in compliance with Attachment A, Article 43 (d)(3).
Review of Requirement Attachment A, Article 43 (f) requires the contractor to immediately notify the Laboratory's Contractual Representative of any OSHA-recordable injuries/illnesses and any “off-normal occurrences” or government owned property damage that the Contractor has determined to have occurred during the project. As defined in this section, an “off-normal occurrence” is any unplanned or unexpected event, including near misses, or the discovery of a deficiency in a procedure, plan, or system that has real or potentially undesirable consequences to personnel, equipment, facilities, the environment, and/or programs. This section also requires the contractor to ensure compliance with 10 CFR 851.26, Recordkeeping and Reporting. Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses, and Fires, states that all injuries and near misses, and other incidents, such as fires or vehicle accidents, must be reported to Torcon immediately. The first priority will be to ensure that any needed first aid or medical treatment is administered and the scene is secured. Torcon will report the incident to the NSLS-II Construction Safety Engineer. The Accident Investigation Committee performed a comparison of the NSLS-II site EMT Incident Reports and Torcon’s investigations. This revealed that there were several more incidents than investigations. The list of missing reports was provided to Torcon who stated that they were unaware of the injuries and did not investigate them. They also stated that they believed the injuries to be minor or not work related.
Results of Analysis The Accident Investigation Committee determined that Torcon’s response to this accident met their contractual and ES&H program responsibility. The Accident Investigation Committee determined Torcon’s failed to ensure all injuries were being reported in accordance with their Program SHE and therefore did not fully comply with Attachment A, Article 43 (f) and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Draft
Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met. 42
December 4, 2009
BNL NSLS-II Accident Investigation
Review of Requirement Attachment A, Article 43 (k) requires the contractor to be responsible for its subcontractors’ compliance with the ES&H requirements of this contract. The contractor is required to include NSLS-II site ES&H requirements in all agreements with its subcontractors. Torcon’s SHE Program, Section 23, Job Site Inspections, requires documented daily safety inspections to be performed and documented by Torcon and the subcontractors. Section 23 further states that these inspections are to be carried out to ensure compliance with all safety procedures and PHAs. Torcon’s safety inspections are performed by the Safety Manager, Superintendents, Project Manager and Project Executive. Each active subcontractor company is also required to perform a daily safety inspection of their work areas, done by a supervisor, using the form provided in Article 9 of the Program. This form must be completed each day that the subcontractor is active on the site. The completed form is to be submitted to the Torcon Safety Manager on a weekly basis. Any deficiencies found in the safety inspections are to be corrected, with the date of correction noted on the form. The Torcon Safety Manager is required to review these forms daily to identify trends or problem areas so they can be addressed by training or other action.
Analysis of Requirement A review of the records provided to the Accident Investigation Committee indicated that daily safety inspections were not being completed daily by all subcontractors and they were not being filled out correctly in most cases. For example, the records provide a code for indicating whether the inspection results were acceptable or correction is needed. Numerous records were marked in a manner that was incomprehensible and made the feedback unusable. Other records had comments that appeared to need corrective actions, but there was no indication that action was taken. Objective evidence was not available to indicate whether these inspections were actually taking place daily.
Results of Analysis Torcon’s SHE Program is an ES&H contractual requirement (reference Contract Attachment A, Article 43 (d)), the Accident Investigation Committee determined that Torcon failed to ensure Section 23 of Torcon’s SHE Program was being implemented and did not meet the requirements of Article 43(k) to ensure subcontractors’ compliance with ES&H requirements of the contract. Therefore this is a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Draft
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
43
December 4, 2009
BNL NSLS-II Accident Investigation
3.5.2 ANALYSIS OF CONTRACT ATTACHMENT A, ARTICLE 16 Review of Requirement Attachment A, Article 16 describes the prohibition of counterfeit or suspect items on the BNL site and the actions the Laboratory will implement when these items are found. As defined in this article, suspect items are 'items for which there is an indication by visual inspection, testing, or other information that it may not conform to established government or industry-accepted specifications or national consensus standards'. Counterfeit or suspect items include lifting materials, such as slings, hooks, cables, and shackles. Furthermore, this article directs the contractor to the Suspect/Counterfeit Items Subject Area within the Laboratory's Standards-Based Management System.
Analysis of Requirement Suspect shackles and wire clips (no manufacturer's name or stamp) were found on the NSLS-II site several times over several days by members of the Accident Investigation Committee conducting site observations. The suspect shackles and wire clips were impounded and reported to the NSLS-II ES&H Manager. A review of Torcon’s SHE Program, Section 38 Rigging Procedures and Inspections, and its associated Daily Rigging Inspection form, did not indicate a requirement or discussion of the need to inspect for suspect/counterfeit items prior to rigging.
Results of Analysis The Accident Investigation Committee determined that Torcon and its subcontractors failed to implement the requirement of Article 16 to prevent the use of suspect/counterfeit items during rigging operations and is therefore a contributing cause to weaknesses in the implementation of the ES&H Program. Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Torcon failed to detect and correct the use of suspect/counterfeit items used during rigging operations.
Contributing Cause Statement (CCW-3): Torcon and its subcontractors failed to implement an effective suspect/counterfeit program for rigging. • •
Draft
Suspect shackles and wire clips (no manufacturer's name or stamp) were found several times over several days by members of the Accident Investigation Committee. Torcon’s SHE Program, Section 38, Rigging Procedures and Inspections, and its associated Daily Rigging Inspection form outlined in Article 38, did not address inspection for suspect/counterfeit items prior to rigging.
44
December 4, 2009
BNL NSLS-II Accident Investigation
3.5.3 ANALYSIS OF BSA AND NSLS‐II OVERSIGHT Review of Requirement The organizational structure and responsibilities for the NSLS-II team is documented in their Environmental, Safety, and Health Plan for the National Synchrotron Light Source-II; Doc #LT-ES&H-002CD-REV02 (NSLS-II ES&H Plan) and is further defined for this phase of construction in the Environment, Safety, and Health Management Plan for the Construction of NSLS-II Conventional Facilities; DOC LTESH-009-Rev1 (NSLS-II ES&H Management Plan). The NSLS-II ES&H Management Plan identifies the requirements for ES&H Project oversight. It states that the Environmental, Safety, and Health Manager (ES&HM) is responsible for implementing the BNL ISM program for the NSLS-II Project to ensure that environmental, safety, and health issues are addressed in the design, construction, and ultimate operations of NSLS-II. In this capacity, the ES&HM’s responsibilities include: •
Utilizing appropriate BNL ES&H subject matter experts (SMEs) to prepare hazard analyses, review design documents, and oversee construction activity to ensure compliance with ES&H standards.
•
Oversee implementation of the construction safety program to ensure compliance with BNL and OSHA regulations, and monitor progress toward “Best in Class” performance.
•
Be responsible for internal oversight and evaluations of the implementation of the NSLS-II construction safety program. The evaluations shall address consistency with defined expectations (i.e., conformance to internal procedures) and shall identify hazards not effectively addressed by the program.
•
Support the implementation of a construction ES&H program consistent with BNL expectations by (1) identifying expectations and (2) developing the construction ES&H Management Plan for implementing those expectations.
•
Communicate concerns and offer constructive guidance directly to other NSLS-II Project personnel.
Analysis of Requirement Both NSLS-II and Torcon’s insurance carriers have performed field observations of this construction site and have provided feedback to improve operations on the site. It appears these recommendations have been implemented. BSA’s Internal Audit and Oversight Office has conducted two assessments on elements of the NSLS-II ES&H program to date: Report IO 09-97 Phase 1, dated August 26, 2009, and IO 09-97 Phase 2 (in draft, the assessment was completed on August 25, 2009). The scope of Phase 1 included a document review of the NSLS-II and Torcon Safety documents. There were no findings or areas for improvements identified. The Phase 2 scope included training provided to all Project personnel. There were no findings, but three areas for improvement were identified. The scope of the assessment of Phase 3 will consist of field observations of work in progress. BSA’s Safety & Health Services (SHSD) Construction Safety Engineer performs NSLS-II site observations on an average of twice a week. These observations are conducted jointly with NSLS-II Draft
45
December 4, 2009
BNL NSLS-II Accident Investigation
personnel, Torcon personnel, and subcontractor personnel. When findings are developed, they are documented by NSLS-II Personnel. NSLS-II conducted one assessment to date, lead by BNL’s Training Coordinator for NSLS-II. The report is entitled Assessment of Brookhaven National Laboratory, National Synchrotron Light Source II Project Training Requirement, dated September 2, 2009, and was scoped to assess project training requirements. One minor non-compliance and one opportunity for improvement were noted. NSLS-II has scheduled four assessments for calendar year 2010. They will cover safety inspections, equipment inspections, phase hazard analyses, and permits NSLS-II Construction Safety Inspectors are conducting daily safety inspections in accordance with paragraph 3.3.1.1 of the NSLS-II ES&H Management Plan, NSLS-II Project Procedure LT-ESH_P-00013, Safety Inspections, and BSA’s Construction Safety Subject Area. Construction Safety Inspection (CSI) reports are being generated. However, not all findings are being documented on the CSI; some are being verbally transmitted to Torcon, while others are being communicated via e-mail. In addition, the BSA Contractual Representative was not notified of the findings and thus did not issue a Notice of NonCompliance to Torcon as required by Attachment A, Article 43 (g) of the Contract. As a result, CSI’s generated by the NSLS-II staff were not properly processed or completed as required by BSA’s Construction Safety Subject Area and the Contract.
Results of Analysis Considering the number of elements in the NSLS-II ES&H Program and the scheduled completion of this contract in April 2012, the Accident Investigation Committee determined that the current assessment schedule is inadequate to review all program elements in a timely manner to proactively identify and correct deviations. The Accident Investigation Committee has also determined that NSLS-II failed to ensure full implementation of the NSLS-II ES&H Program by not identifying Torcon’s deviations from NSLS-II ES&H Program requirements as explained in section 3.5.1. Though this failure is not a cause for this accident it does weaken the ES&H Program and can lead to missed opportunities to proactively identify and correct minor problems before they become severe. Contributing Cause Statement (CCW-4): NSLS-II failed to ensure that the NSLS-II ES&H Program was performing as designed. •
•
• • •
Draft
NSLS-II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract. NSLS-II’s oversight of Torcon’s implementation of Section 7.1 of the NSLS-II Construction HASP and Section 11 of Torcon’s SHE Program did not identify and correct shortcomings in PHA implementation, such as the lack of specificity, not adequately identifying hazards, and new workers not reviewing and signing PHA’s. NSLS-II’s oversight did not reveal that daily and frequent inspections by Torcon and its subcontractors were not being performed. NSLS-II’s oversight did not identify and correct the use of suspect shackles and wire clips (no manufacturer's name or stamp) found several times over several days on the site. The NSLS-II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations. 46
December 4, 2009
BNL NSLS-II Accident Investigation
3.6
INTEGRATED SAFETY MANAGEMENT
The Accident Investigation Committee examined Management Systems as potential contributing and root causes of the event and the overall NSLS-II ES&H program in terms of Integrated Safety Management (ISM). At BNL, the ISM Program Description describes BNL’s approach to integrating Environment, Safety, Health, and Quality (ESH&Q) requirements into the processes for planning and conducting work at the Laboratory. It also describes BNL's programs for accomplishing work safely and provides a road map of the systems and processes that make up the BNL Integrated Safety Management System (ISMS). The ISMS Program is accomplished by employing an integrated set of non-overlapping Management Systems that embody the requirements defined in the DOE ISMS Manual. These systems collectively form the Standards-Based Management System (SBMS) Management Systems, BNL's highest level of operating and business processes that define how work is conducted at the Laboratory. These Management Systems are defined via Management System Descriptions that identify each system's processes, standards of performance, external requirements, and the set of Laboratory procedures and guidelines (Subject Areas and other Laboratory-wide procedures) to carry-out the elements of each system. Management Systems, Program Descriptions, and Subject Areas operate in an integrated fashion by providing programs and procedures that implement the Plan, Do, Check, Act framework. The Core Functions and Guiding Principles of ISM are the primary focus for BNL and its contractors in conducting work efficiently and in a manner that ensures the protection of workers, the public, and the environment. Properly implemented, ISM is a standards-based approach to safety, requiring rigor and formality in the identification, analysis, and controls of hazards. The five Core Functions of ISM are defining the work, analyzing the hazards, developing and implementing controls, performing work safely, and feedback and improvement. How failure of these core functions apply to the accident is discussed in detail in the following sections. Using ISM’s Core Functions and Guiding Principles, each phase of the work related to the accident was analyzed. In addition, ISM’s Core Functions and Guiding Principles were also used to examine the ES&H program and evaluate its performance. Attachment A, Article 43 (c) of the BSA/Torcon Contract requires Torcon to perform and manage work in accordance with BSA’s DOE-approved Integrated Safety Management (ISM) Program and to demonstrate through documentation and work practices that its performance of work under the contract: (1) fulfills the scope of work as outlined in the contract; (2) identifies and analyzes specific, task-level hazards associated with the work; (3) develops and implements hazard controls related to the hazards; (4) allows the performance of work within the controls; and (5) provides feedback on the adequacy of hazard controls and continuous improvement in safety management as detailed in their ES&H Plan. Section 4 of Torcon’s SHE Program provides their commitment to integrate safety into every phase of the project, from concept through completion of construction. They plan to achieve this by using the ISM System set forth in the NSLS-II Construction HASP. The following sections are organized using the five Core Functions (CF) and seven Guiding Principles (GP), followed by a brief description of the function and/or principle, and the Accident Investigation Committee’s analysis of Torcon’s and its subcontractor’s performance. While each section below lists only the supporting statements that belong to this particular CF or GP, Table 2 summarizes all the connections between the causes identified and the ISM Core Functions and Guiding Principles.
Draft
47
December 4, 2009
BNL NSLS-II Accident Investigation
The five Core Functions, as defined by DOE P 450.4, Safety Management System Policy, are the following: Core Function 1:
Define the scope of work: Missions are translated into work, expectations are set, tasks are identified and prioritized, and resources are allocated.
Core Function 2:
Identify and analyze hazards associated with the work: Hazards associated with the work are identified, analyzed, and categorized.
Core Function 3:
Develop and implement hazard controls: Applicable standards and requirements are identified and agreed-upon, controls to prevent/mitigate hazards are identified, the safety envelope is established, and controls are implemented.
Core Function 4:
Perform work within controls: Readiness is confirmed and work is performed safely.
Core Function 5:
Provide feedback on adequacy of controls and continue to improve safety management: Feedback information on the adequacy of controls is gathered , opportunities for improving the definition and planning of work are identified and implemented, line and independent oversight is conducted, and, if necessary, regulatory enforcement actions occur.
The seven Guiding Principles, as defined by DOE Manual 450.4-1, Integrated Safety Management System Manual, are as follows: Guiding Principle 1:
Line manager clearly responsible for ES&H: Line management is directly responsible for the protection of the public, the workers, and the environment.
Guiding Principle 2:
Clear ES&H roles and responsibilities: Clear and unambiguous lines of authority and responsibility for ensuring safety shall be established and maintained at all organizational levels within the Department and its contractors.
Guiding Principle 3:
Competence commensurate with responsibilities: Personnel shall possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities.
Guiding Principle 4:
Balanced priorities: Resources shall be effectively allocated to address safety, programmatic, and operational considerations. Protecting the public, the workers, and the environment shall be a priority whenever activities are planned and performed.
Guiding Principle 5:
Identify ES&H standards and requirements: Before work is performed, the associated hazards shall be evaluated and an agreed-upon set of safety standards and requirements shall be established which, if properly implemented, will provide adequate assurance that the public, the workers, and the environment are protected from adverse consequences.
Draft
48
December 4, 2009
BNL NSLS-II Accident Investigation
Guiding Principle 6:
Hazard controls tailored to work: Administrative and engineering controls to prevent and mitigate hazards shall be tailored to the work being performed and associated hazards.
Guiding Principle 7:
Operations authorization: The conditions and requirements to be satisfied for operations to be initiated and conducted shall be clearly established and agreedupon.
3.6.1 GUIDING PRINCIPLES The following three Guiding Principles of ISM cover all five core functions. They are followed by the Accident Investigation Committee’s analysis of their implementation at the NSLS-II construction site. GP 1:
Line management is directly responsible for the protection of the public, the workers, and the environment. Torcon’s SHE Program clearly identifies line management is directly responsible for the protection of the public, the workers and environment. During the course of the investigation, the Accident Investigation Committee observed many good practices that demonstrated NSLS-II, Torcon, and its subcontractors were proactively protecting the public, workers and the environment, and these are noted in Section 5.3.1 of this report. However, it is indisputable that this accident occurred and is therefore an example of failure to fully implementation of GP 1. Table 2 identifies the causes impacted by GP 1.
GP 2:
Clear and unambiguous lines of authority and responsibility for ensuring safety shall be established and maintained at all organizational levels within the organization and its contractors. Interviews conducted by members of the Accident Investigation Committee with subcontractor supervisors revealed that supervisors believe investigations and toolbox training to be the responsibility of the safety staff and not theirs. Additional interviews conducted by the Accident Investigation Committee with Torcon and its subcontractors found that the individual responsible for requesting the Operator submit to a drug and alcohol screening following this accident was not clearly defined.. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. Torcon was not able to produce an organization chart that was in effect at the time of the accident; only copies of their organization chart that were included with their bid-proposal and copies dated after the accident were provided. In addition, a description of the roles and responsibilities for the Torcon Safety Manager was requested and could not be provided. The Accident Investigation Committee also determined that the lack of clear roles and responsibilities is a contributing cause to weaknesses in the implementation of the ES&H Program.
Draft
49
December 4, 2009
BNL NSLS-II Accident Investigation
Contributing Cause Statement (CCW-1): Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels. Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations. Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager. GP 3:
Personnel shall posses the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities. The Accident Investigation Committee determined that the Laborer’s experience and skills were not adequately assessed or validated to ensure they were adequate to perform the work he was assigned. In directing the staging of the rebar at the accident location, the Laborer did not allow himself adequate space to move about the area. This resulted in him tripping over the rebar. Torcon and its subcontractors failed to ensure the Laborer possessed the experience, knowledge, skills and abilities necessary to discharge his responsibilities and therefore implementation of GP 3 was not met; this is a Root Cause of this event.
Root Cause Statement (RCE-1): Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities. Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.
GP 7: The conditions and requirements to be satisfied for operations to be initiated and conducted shall be clearly established and agreed-upon. This GP does not apply until operations are authorized at NSLS-II and therefore does not apply to this investigation.
Draft
50
December 4, 2009
BNL NSLS-II Accident Investigation
3.6.2 DEFINE WORK CF 1:
Laboratory missions are translated into work, expectations are set, tasks are identified and prioritized, and resources are allocated.
GP 4:
Resources shall be effectively allocated to address safety, programmatic and operations considerations. To clearly communicate the construction ES&H requirements, the NSLS-II project team created the NSLS-II Construction HASP, which is included in the contract signed with Torcon. Also included in this contract is Torcon’s responsibility to ensure these requirements are imposed on all of its subcontractors at all levels and tiers. Torcon was required to submit a health and safety plan that meets the requirements of the NSLSII Construction HASP prior to the start of work. Torcon’s Project Safety, Health and Environmental Program (Torcon’s SHE Program) was reviewed by NSLS-II, BSA, and DOE-BHSO safety and health professionals and approved on March 17, 2009. A notice to proceed was transmitted by BSA to Torcon on March 25, 2009. The Accident Investigation Committee determined that CF 1 and GP 4 were clearly defined by BSA and NSLS-II and communicated to Torcon, and that Torcon clearly communicated these to their subcontractors.
3.6.3 ANALYZE THE HAZARDS CF 2:
Hazards associated with work are identified, analyzed, and categorized.
GP 5:
Before work is performed, the associated hazards shall be evaluated and an agreed-upon set of safety standards and requirements shall be established which, if properly implemented, will provide adequate assurance that the public, the workers and the environment are protected from adverse consequences. As previously stated in section 3.5.1 of this report, the Accident Investigation Committee determined PHA’s did not adequately identify the hazards for material handling of rebar due to the lack of specificity
Root Cause Statement (RCE-2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Hazard analyses are required for major phases of the project. However, major phases were not defined.
•
Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”.
Draft
51
December 4, 2009
BNL NSLS-II Accident Investigation
•
Torcon and its subcontractors failed to establish that personnel were ready to perform work by ensuring they were aware and prepared to protect themselves from hazards associated with their work. The Laborer created a staging area for the rebar which was unacceptable.
•
Pre-job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
3.6.4 DEVELOP AND IMPLEMENT CONTROLS CF 3:
Applicable standards and requirements are identified and agreed-upon, controls to prevent/mitigate hazards are identified, the safety envelope is established, and controls are implemented.
GP 5:
Before work is performed, the associated hazards shall be evaluated and an agreed-upon set of safety standards and requirements shall be established which, if properly implemented, will provide adequate assurance that the public, the workers and the environment are protected from adverse consequences.
As previously stated in section 3.5.1, the PHA for the work performed by the Laborer and Operator on the day of the injury was requested, and the Accident Investigation Committee was provided with a Macedos PHA entitled All Footings, revised 6/29/09. This PHA did not include the signatures of the Laborer and the Operator, as required by Torcon’s SHE Program. Pre-job briefings witnessed by members of the Accident Investigation Committee during the course of the investigation did not include a discussion of the hazards of the work to be performed. These briefings primarily concentrated on what work needed to be performed and not how to perform the work or identify the associated hazards. There was no evidence that the Laborer and Operator took part in a pre-job brief that identified specific job hazards. In addition, these observations are supported by Macedos’ Safety Manager, who stated that PHAs are used during pre-job reviews conducted by Supervisors with their workers to identify and mitigate/reduce hazards. This is usually not repeated for routine, ongoing tasks, such as moving rebar. Communication between equipment operators and laborers was observed to be effective throughout the site, and there was no sign of miscommunication. However, members of the Accident Investigation Committee observed the following: no evidence of uniform use of standard hand signals on site, even within the same craft of workers; and no discussion or coordination of hand signals between work crew members. This included crew members from different employers who work together on the same job task. Although the Accident Investigation Committee determined that hand signals did not contribute to this accident, the coordination of hand signals posses a potential error trap. Reliable and consistent hand signal communication is critical to safe operations. The equipment manufacturer provides hand signals to be used and these should be incorporated into operations. Therefore, the Accident Investigation Committee determined that this control was not adequately implemented. Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses, and Fires, states that anyone involved in a near miss or injury situation may be required to be tested for substance-abuse at the discretion of Torcon or the NSLS-II Project Management. Section 6, Drug-Free Workplace Policy, states the same. In addition, Torcon’s Project Orientation and General Safety & Health Rules, not dated, state under the Principles of the Program, 2 No alcohol or drugs, that post-incident or injury drug and alcohol Draft
52
December 4, 2009
BNL NSLS-II Accident Investigation
testing are performed. Section 10 of Torcon’s Project Safety Orientation Outline, Revision 6: September 2009, also includes the same requirement. As stated in the Accident Description section of this report (see Section 2.1, page 21), the Operator left the site for approximately 30 minutes and then returned for 1.5 hours before leaving for the day at approximately 1200 hours. The Operator had indicated that he was not asked to submit to an alcohol or drug test before he left the site for the day. Torcon’s Project Manager stated that it was after the Operator had left that they realized they wanted to administer a drug test. Macedos then attempted to reach the Operator but were not able to speak to him until later that day. The Operator did return the following day as requested by Torcon to undergo the drug test. The results of the test were negative. Further conversations with Torcon’s Safety Manager revealed that drug and alcohol testing had not been performed as a result of any injury or incident on the NSLS-II site. The Accident Investigation Committee concluded that Torcon failed to fully implement their alcohol and drug testing requirements. The Accident Investigation Committee determined CF 3 and GP 5 was not adequately implemented. Failure to include hazards as part of pre-job briefings is a root cause of this event. Supervision’s failure to review PHAs with workers, use uniform hand signals, and fully implement their alcohol and drug testing requirements is a contributing cause to weaknesses in the implementation of the ES&H Program.
Root Cause Statement (RCE-2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Pre-job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11.
•
Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met.
•
Hand signal usage was not uniform and relied upon the skill-of-the-workers.
•
Torcon failed to fully implement their alcohol and drug testing requirements.
Draft
53
December 4, 2009
BNL NSLS-II Accident Investigation
3.6.5 PERFORM WORK SAFELY CF 4:
Readiness is confirmed and work is performed safely
GP 6:
Administrative and engineering controls to prevent and mitigate hazards shall be tailored to the work being performed and associated hazards. As previously stated in Section 3.6.4., the Laborer failed to verify his readiness to perform the work safely. The Laborer, standing where he did, had not left himself an escape route. As a result, the Laborer put himself in close proximity to the load, which set the scene for the accident. The Accident Investigation Committee determined that the following are examples of failure by Torcon and its subcontractors to implement administrative controls and confirm readiness to work and are therefore contributing causes to weaknesses in the implementation of the ES&H Program: •
The maintenance log in the Lull, which was boldly marked in red “DO NOT REMOVE FROM VEHICLE!!!” was different from the one provided by Macedos’ Risk and Compliance Director. The copy provided contained more information than the one in the vehicle and should therefore have been in the Lull.
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. However, its gauge indicated full.
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, is different from what is actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of less than full implementation of administrative controls.
•
Torcon Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
The maintenance log in the Lull was different from the one provided by Macedos.
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10.
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of failure to implement administrative controls.
•
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Draft
54
December 4, 2009
BNL NSLS-II Accident Investigation
3.6.6 FEEDBACK AND IMPROVEMENT CF 5:
Feedback information on the adequacy of controls is gathered, opportunities for improving the definition and planning of work are identified and implemented, line and independent oversight is conducted, and if necessary, regulatory enforcement actions occur. The NSLS-II ES&H Monthly Meeting is conducted by NSLS-II ES&H staff and is attended by BSA ES&H staff, DOE-BHSO, as well as Torcon to discuss ES&H-related tasks, issues, and solutions. Torcon’s Labor/Management Safety Committee is described in Torcon’s SHE Program, Section 15, Labor/Management Safety Committee. The Safety Committee meets weekly and is attended by a field supervisor or shop steward. The purpose of the Safety Committee is to create two-way communication on safety issues between Torcon and its subcontractors, including inspection findings, near misses or injuries, suggestions for improvement of safety on the job, and any BNL safety concerns. Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses, and Fires, states that injury and incident investigation will be conducted by Torcon’s Safety Manager, the NSLS-II Construction Safety Engineer, and the subcontractor supervisor to identify causes, contributing factors and lessons learned from the incident. Torcon’s SHE Program, Section16, Weekly Tool Box Safety Meetings, states that each week, at the Labor/Management Safety Committee meeting, Torcon’s Safety Manager distributes the topic of the weekly Tool Box Safety Meeting. Each Torcon supervisor is to hold a brief meeting with his workers. The subcontractor supervisor is free to use a different safety topic for the meeting if desired, in order to keep the topics relevant to the work. Documentation of this meeting, including worker signatures, is to be submitted to the Torcon Safety Manager by the end of each week. Torcon had no assessment schedule for the project and relies on job site inspections and walkthroughs, including those with their insurance carrier. Though this process has a value in ensuring that work activities are being adequately performed in the field, the lack of a systematic approach to assessing the health of the implementation of a safety program, or any other program or process, lessens the effectiveness of that program by not providing feedback to ensure all program expectations are being met. As previously stated, Torcon’s Job Site Daily Inspection Records, required per Torcon’s SHE Program, Section 23, Job Site Inspections, were not being completed daily and not completed correctly in most cases. There are many good practices occurring across the site that focus on field operations, as is stated above, and the result is a site that is in good condition, as described in section 5.3.1 and demonstrates that feedback and improvement is partially working. However, though there are many feedback loops that exist and are being executed, the lack of feedback on the performance of the Project’s ES&H programs has lead the Accident Investigation Committee to determine that the implementation of CF 5 is less-than-adequate and is a contributing cause to weaknesses in the implementation of the ES&H Program.
Draft
55
December 4, 2009
BNL NSLS-II Accident Investigation
Contributing Cause Statement (CCW-2): Torcon and its subcontractors failed to ensure implementation of the NSLS-II ES&H Program and therefore contributed to its weakness. •
Torcon had no assessment schedule for the project and relied on job site inspections and walkthroughs, including those with their insurance carrier.
•
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Contributing Cause Statement (CCW-4): NSLS-II failed to ensure that the NSLS-II ES&H Program was performing as designed. •
NSLS-II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract.
•
The NSLS-II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations.
Draft
56
December 4, 2009
BNL NSLS-II Accident Investigation
Table 2. Summary of Causes Identified and the Corresponding ISM Core Functions and Guiding Principles.
Cause Root Cause Statement (RCE‐1): Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities.
Affected Core Function (CF) / Guiding Principle (GP)
Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned.
GP‐1 / GP‐3
•
Supervision failed to ensure the Laborer was qualified to perform the work safely.
GP‐1 / GP‐3
Root Cause Statement (RCE‐2): Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. •
Hazard analyses are required for major phases of the project. However, major phases were not defined.
•
Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”. Torcon and its subcontractors failed to establish that personnel were ready to perform work by ensuring they were aware and prepared to protect themselves from hazards associated with their work. The Laborer created a staging area for the rebar which was unacceptable.
•
•
Pre‐job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
CF‐2 / GP‐5 CF‐2 / GP‐1 / GP‐5
CF‐2 / GP‐5 CF‐3 / GP‐5
Draft
57
December 4, 2009
BNL NSLS-II Accident Investigation
Cause Contributing Cause Statement (CCW‐1): Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels. •
Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site.
GP‐1 / GP‐2
•
Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations.
GP‐1 / GP‐2
•
Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager.
GP‐1 / GP‐2
Contributing Cause Statement (CCW‐2): Torcon and its subcontractors failed to ensure implementation of the NSLS‐II ES&H Program and therefore contributed to its weakness.
•
Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers.
CF‐3 / GP‐5
•
Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11. Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met.
CF‐3 / GP‐1 / GP‐5
•
•
Draft
Hand signal usage was not uniform and relied upon the skill‐of‐the‐ workers.
58
Affected Core Function (CF) / Guiding Principle (GP)
CF‐3 / GP‐1 / GP‐5
CF‐3 / GP‐5
December 4, 2009
BNL NSLS-II Accident Investigation
Cause •
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. The maintenance log in the Lull was different from the one provided by Macedos.
•
•
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of failure to implement administrative controls. Torcon had no assessment schedule for the project and relied on job site inspections and walkthroughs, including those with their insurance carrier.
Contributing Cause Statement (CCW‐4): NSLS‐II failed to ensure that the NSLS‐II ES&H Program was performing as designed.
Affected Core Function (CF) / Guiding Principle (GP) CF‐4 / CF‐5 / GP‐6
CF‐4 / GP‐6
CF‐4 / GP‐6
CF‐4 / GP‐6
CF‐5
•
NSLS‐II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract.
CF‐5
•
The NSLS‐II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations.
CF‐5
Draft
59
December 4, 2009
BNL NSLS-II Accident Investigation
3.7
ANALYSIS OF EMERGENCY RESPONSE
Notifications to BNL emergency responders and the NSLS-II Project were made in accordance with NSLS-II Project procedure LT-ESH-P-00012, Reporting Events. When the ambulance crew returned to the Firehouse, the Fire Captains conducted a critique of the NSLS-II emergency response. The results are as follows: •
Fire Rescue personnel, including the EMT, responded directly to the accident site and arrived within 4 minutes of notification.
•
Fire Rescue personnel needed to go to the Motor Pool to pick up the ambulance because it was being serviced. The Motor Pool was notified and had the ambulance out and ready by the time Fire Rescue arrived.
•
The Suffolk County Police Medevac was placed on standby because of the report of a serious injury, but released when it was determined by Fire Rescue that there wouldn’t be a delay in transporting the patient.
•
When Fire Rescue personnel arrived at the NSLS-II site, personnel from Torcon directed them directly to the accident scene; they were highly visible and accurate.
•
The Torcon EMT was already on scene and had initiated patient care.
•
The scene was secure and there was ample room for responding apparatus.
•
Fire Rescue personnel stabilized the patient and prepared him for transportation to the hospital.
•
A notification was sent to the hospital apprising them of the incoming patient and his condition. They had a team ready that met the ambulance when it arrived.
•
A request for an ALS intercept was made and provided to the patient without delay in transportation.
•
The entire operation was conducted very smoothly, quickly, efficiently, and safely.
As indicated above, the ambulance was at the Motor Pool for maintenance. If it had not been available to respond to the accident, Suffolk County Police Medevac or mutual aid could have been utilized to transport the injured to the hospital. Feedback received from the hospital indicated that the emergency response team did an excellent job in stabilizing the fracture and keeping it clean. Torcon’s and BSA’s Fire Rescue response time to the accident site and the subsequent transport of the injured worker to the Hospital was acceptable. The Accident Investigation Committee has determined that the emergency response for this event was acceptable.
Draft
60
December 4, 2009
BNL NSLS-II Accident Investigation
4.0
CONCLUSIONS AND JUDGMENTS OF NEED
The Accident Investigation Committee has concluded that this accident was preventable. The Laborer, standing where he did, had not left himself an escape route. It is less important whether the Laborer signaled correctly, whether the Operator misinterpreted the Laborer’s intentions, or whether it was rebar or mud that impeded the Laborer’s movement. In this regard, the Accident Investigation Committee determined that there was no need to think that any of the people involved were being less than truthful in recounting the events. Memory, especially in the wake of a traumatic event, is “reconstructive,” that is, people try their best to make sense of an impossible series of occurrences. The significant point is that the margin for error was reduced by the Laborer standing in the trajectory of the rebar. Therefore any coincidental mishap would be more likely to result in an injury. It seems reasonable to assume that, as the load was being moved toward him and being positioned over the place where it was to be placed, the Laborer’s attention was entirely on what was in front of him, not on what was at his feet or immediately behind him, and that his focus remained so even as he began to move away from where the load would be placed. There are two root causes to this event. The first is that Torcon and its subcontractors failed to ensure employees were qualified and possessed the experience, knowledge, skills and abilities that were necessary to discharge his responsibilities. The Laborer was assigned work by his supervisor who failed to ensure the Laborer was qualified to perform it. In addition, pre-job briefings did not adequately address the hazards associated with the work being performed. Briefings primarily concentrated on what work needs to be performed, not on the associated hazards. The second root cause was that Torcon and its subcontractors failed to ensure workers were aware of foreseeable hazards and protective measures needed for their safety. Hazard analyses are required for major phases of the project. However, major phases were not defined. Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”. In addition, pre-job briefings did not adequately address the hazards associated with the work being performed. Briefings primarily concentrated on what work needs to be performed, not on the associated hazards. Four causes were identified that did not contribute to this event but contributed to weaknesses in the NSLS-II ES&H Program at the construction site. NSLS-II has the potential to achieve best in class if their ES&H Program is fully implemented. The first contributing cause to program weakness was due to poorly defined lines of authority and responsibilities for ensuring ES&H compliance. No one was assigned by Torcon or its subcontractors to determine if drug and alcohol screening needed to be performed after an accident. Line supervisors were not aware of their responsibility to conduct injury investigations and toolbox training, but believed these were the responsibility of the safety staff in contradiction to the Torcon SHE Program. The second contributing cause to program weakness was due to poor oversight by Torcon to ensure their ES&H program was being properly implemented. Examples include not detecting and correcting that (1) new workers were reviewing and signing PHA’s, (2) that not all injuries were being investigated, and (3) that daily job site inspections were not being correctly performed if performed at all.
Draft
61
December 4, 2009
BNL NSLS-II Accident Investigation
The third contributing cause to program weakness was due to a lack of effective suspect/counterfeit program for rigging. Suspect shackles and wire clips were found on the NSLS-II construction site several times over several days by members of the Accident Investigation Committee. In addition, the daily rigging inspection forms provided by Torcon failed to address the inspection of suspect/counterfeit items. The fourth and final contributing cause to program weakness was due to the lack of oversight by the NSLS-II project to ensure their ES&H program was being properly implemented. This included not detecting and correcting that: (1) NSLS-II Construction Safety Inspectors were documenting all findings, (2) PHAs were adequate for the work being performed and were being reviewed by new workers, and (3) daily inspections by Torcon and their subcontractors were not being performed.
4.1
DIRECT, ROOT, AND CONTRIBUTING CAUSES
Based upon the results of the analytical methods described above, the Accident Investigation Committee has identified one direct cause to the event (DCE) and two Root Causes to the event (RCE). In addition, the Accident Investigation Committee, as part of its charter, has identified four causes that contributed to weakening the BSA, NSLS-II, and Torcon ES&H Programs (CCW). For each cause, the analytical method that is its source is identified, using the following codes: Barrier Analysis (BA), Event & Causal Charting (E&CFC), ISM Analysis (ISM), and TapRooT (TR). In addition, a reference to the requirements that the cause applies to is also provided. Table 3. Event causes, summaries, sources, and associated JONs.
DCE No.
Direct Cause of the Event
1
Laborer struck by rebar
RCE No.
Root Cause of the Event
1
Torcon and its subcontractors failed to ensure employees possessed the experience, knowledge, skills, and abilities that were necessary to discharge their responsibilities.
Summary and Source
JON
Rebar strikes the Laborer’s lower right leg and fractures it. (E&CFC)
1, 2, 5 & 7
Draft
Summary and Source •
Torcon, Macedos, and Rebar Steel supervision failed to 1, 5 & 7 ensure the Laborer was qualified to perform the assigned work safely. (BA, TR, OS, ISM, E&CF)) (Reference: Contract Attachment A, Article 43 (b))
62
JON
December 4, 2009
BNL NSLS-II Accident Investigation
RCE No. 2
Root Cause of the Event
Summary and Source
JON
Torcon and its • Hazard analyses are required for major phases of the subcontractors project. However, major phases were not defined. (OS, failed to ensure ISM) workers were • Hazard analyses failed to identify hazards and lacked aware of detail for the movement and placement of rebar. The foreseeable hazard analysis for materials pick up with a forklift only hazards and addressed “dropping/misplacement pinch points” as a protective hazard and provided the following controls: “flagman measures needed direction/horn warning”, “cordoned off area with caution for their safety. tape”, and “spotter will work with forklift”. (BA, OS, ISM)
2, 5 & 7
• Torcon and its subcontractors failed to establish that personnel were ready to perform work by ensuring they were aware and prepared to protect themselves from hazards associated with their work. The Laborer created a staging area for the rebar which was unacceptable. (ISM, TR) •
Pre‐job briefings failed to address the hazards associated with the work being performed. Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards. (BA, ISM, E&CF)
(References: Contract Attachment A, Article 43 (d)(1), and Torcon’s SHE Program Section 11)
Draft
63
December 4, 2009
BNL NSLS-II Accident Investigation
Table 4. Contributing causes to program weaknesses, summaries, sources, and associated JONs.
CCW No. 1
Contributing Cause (Program Weakness) Torcon and its subcontractors failed to establish clear and unambiguous lines of authority and responsibility for ensuring ES&H compliance was established and maintained at all organizational levels.
Summary and Source
JON
•
Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit to a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. (BA, OS, ISM)
•
Torcon’s supervisors and its subcontractor’s supervisors had abdicated safety responsibilities to safety staff. Supervisors believed investigations and toolbox training to be the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes and participating in injury investigations. (BA, OS, ISM)
•
Torcon was not able to provide a document defining roles and responsibilities for their Safety Manager. (OS, ISM)
3, 5 & 7
(Reference: Contract Attachment A, Article 43 (b)) 2
Draft
Torcon and its subcontractors failed to ensure implementation of the NSLS‐II ES&H Program and therefore contributed to its weakness.
•
Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers. (BA, ISM, OS)
•
Supervision failed to ensure the Laborer and Operator had reviewed and signed the PHA for the work they were performing in accordance with Torcon’s SHE Program, Section 11. (OS, ISM)
•
Torcon failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires, and the requirements of Contract Attachment A, Article 43 (f) were not met. (BA, OS, ISM)
•
Torcon’s Job Site Daily Inspection Records were not 64
4, 5 & 7
December 4, 2009
BNL NSLS-II Accident Investigation
CCW No.
Contributing Cause (Program Weakness)
Summary and Source
JON
being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases. (BA, OS, ISM)
Draft
•
Torcon’s Project Safety Evaluation forms were not completed correctly and some work periods were missing altogether. Objective evidence was not available to indicate whether these inspections had actually taken place daily as required by the contract. (OS)
•
Torcon failed to detect and correct the use of suspect/counterfeit items used during rigging operations. (OS)
•
Hand signal usage was not uniform and relied upon the skill‐of‐the‐workers. (ISM)
•
Torcon failed to fully implement its alcohol and drug testing requirements. (ISM)
•
The maintenance log in the Lull was different from the one provided by Macedos. (BA, ISM)
•
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. (BA, ISM)
•
Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used. Although the Accident Investigation Committee considers these two forms as nearly equivalent, it is another example of failure to implement administrative controls. (BA, ISM)
•
Torcon had no assessment schedule for the project and relied on job site inspections and walkthroughs, including those with their insurance carrier. (ISM)
•
Toolbox meetings topics were not always germane to the work hazards being encountered in the field. The continuing training program was inadequate. The 65
December 4, 2009
BNL NSLS-II Accident Investigation
CCW No.
Contributing Cause (Program Weakness)
Summary and Source
JON
toolbox training provided was not specific to tasks being performed. (BA, TR) (References: Contract Attachment A: Article 16, Article 43 subsections (d)(1), (d)(2), (f), (k), Torcon’s SHE Program Sections 11, 14, 19, 23, and 38, and NFPA 10) 3
Torcon and its subcontractors failed to implement an effective suspect/counterf eit program for rigging.
•
Suspect shackles and wire clips (no manufacturer's name or stamp) were found several times over several days by members of the Accident Investigation Committee. (OS)
•
Torcon’s SHE Program, Section 38, Rigging Procedures and Inspections, and its associated Daily Rigging Inspection form outlined in Article 38, did not address inspection for suspect/counterfeit items prior to rigging. (OS)
5, 6 & 7
(References: Contract Attachment A, Article 16 and Torcon’s SHE Program Section 38)
Draft
66
December 4, 2009
BNL NSLS-II Accident Investigation
CCW No. 4
Contributing Cause (Program Weakness) NSLS‐II failed to ensure that the NSLS‐II ES&H Program was performing as designed.
Summary and Source
JON
•
NSLS‐II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area and the Contract. (BA, OS. ISM)
•
NSLS‐II’s oversight of Torcon’s implementation of Section 7.1 of the NSLS‐II Construction HASP and Section 11 of Torcon’s SHE Program did not identify and correct shortcomings in PHA implementation, such as the lack of specificity, not adequately identifying hazards, and new workers not reviewing and signing PHA’s. (OS)
•
NSLS‐II’s oversight did not reveal that daily and frequent inspections by Torcon and its subcontractors were not being performed. (OS)
•
NSLS‐II’s oversight did not identify and correct the use of suspect shackles and wire clips (no manufacturer's name or stamp) found several times over several days on the site. (OS)
•
The NSLS‐II assessment schedule was inadequate to review all program elements in a timely manner to proactively identify and correct deviations. (OS, ISM)
5 & 7
(References: Contract Attachment A, Article 43 (g), BSA’s Construction Safety Subject Area, NSLS‐II ES&H Management Plan paragraph 3.3.1.1, and NSLS‐II Project Procedure LT‐ESH_P‐00013, Safety Inspections)
Draft
67
December 4, 2009
BNL NSLS-II Accident Investigation
4.2
JUDGMENTS OF NEED
Judgments of Need are managerial controls and safety measures believed necessary to prevent or minimize the probability of recurrence. They flow from the causal factors and are directed at guiding managers in developing corrective actions. The Judgments of Need and associated Cause Codes are shown in Table 5.
Table 5. Judgments of Need.
No.
Draft
Judgment of Need
Cause Codes
1
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure workers are qualified and possess the experience, knowledge, skills, and abilities that are necessary to discharge their responsibilities in compliance with (1) Contract Attachment A, Article 43, (2) ES&H program and (3) ISM.
DCE‐1 RCE‐1
2
DCE‐1 There is a need for Torcon and all its subcontractors, at all levels, on RCE‐2 the NSLS‐II construction site, to ensure workers are aware of foreseeable hazards and protective measures for their safety. This includes, but is not limited to defining “major phases” of work to determine when hazard analyses are required, establishing the criteria for acceptance of hazard analyses, discussing hazards and their controls during pre‐job briefings, and ensuring compliance with (1) Contract Attachment A, Article 43 (d)(1), Establishment of Safety Protocols, and (2) Torcon’s SHE Program Section 11, PHAs.
3
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to establish clear and unambiguous lines of authority and responsibility for the implementation the (1) Contract, (2) Torcon’s SHE Program, and (3) other ES&H requirements.
CCW‐1
4
There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure all ES&H requirements of the Contract and Torcon’s SHE Program are being adequately implemented. This includes, but is not limited to, the following requirements: • Contract, Attachment A o Article 16, Suspect/Counterfeit Items o Article 43 subsections (d)(1) Establishment of Safety Protocols
CCW‐2
68
December 4, 2009
BNL NSLS-II Accident Investigation
No.
Judgment of Need
Cause Codes
(d)(2) Frequent and Regular Inspections of the Work Site (f) Immediate Notification to BSA’s Contractual Representative of Recordable Injuries (k) Subcontractor’s Compliance with ES&H Requirements of the Contract • Torcon’s SHE Program o Section 11, PHAs o Section 14, Daily Inspections of Heavy Equipment o Section 19, Procedures for Injuries and Near Misses o Section 23, Job Site Inspections o Section 38, Rigging Procedures and Inspections • NFPA 10, Standard for Portable Fire Extinguishers
Draft
There is a need for the NSLS‐II project to provide adequate oversight to ensure that BSA ES&H Contract requirements and the NSLS‐II ES&H programs are being fully implemented. This includes, but is not limited to: • Compliance with Contract, Attachment A, Article 43 (g), Written Notification to Contractor of Non‐compliances • Compliance with BSA’s Construction Safety Subject Area • Compliance with NSLS‐II ES&H Management Plan, paragraph 3.3.1.1, Safety Responsibilities • Compliance with NSLS‐II Project Procedure LT‐ESH_P‐00013, Safety Inspections.
6
CCW‐3 There is a need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to implement an effective suspect/counterfeit program for rigging. This includes, but is not limited to, revising Torcon’s SHE program to reflect inspection of rigging equipment for suspect/counterfeit items prior to use and ensuring there are no unknown suspect/counterfeit items currently in use on the NSLS‐II construction site. There is a further need for Torcon and all its subcontractors, at all levels, on the NSLS‐II construction site, to ensure that Contract, Attachment A, Article 16, is being met.
69
DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
5
December 4, 2009
BNL NSLS-II Accident Investigation
No. 7
Judgment of Need
Cause Codes
There is a need for the NSLS‐II project to establish and implement a well structured assessment program to complement field inspections. The assessment program should be designed to ensure all elements of the ES&H program required by the Contract and ES&H Plans are functioning properly. The schedule should be established to ensure elements that support or monitor life protection programs (e.g., LOTO, confined spaces, excavation, electrical safety) are given priority.
DCE‐1 RCE‐1 RCE‐2 CCW‐1 CCW‐2 CCW‐3 CCW‐4
Draft
70
December 4, 2009
BNL NSLS-II Accident Investigation
5.0
OTHER ANALYSES REQUIRED BY TEAM CHARTER
5.1
IMMEDIATE RESPONSE TO THE ACCIDENT
This section reviews the response actions taken by NSLS-II and Torcon immediately following the accident. The emergency response to the accident is analyzed in section 3.7. At 0845 hours, in accordance with NSLS-II Project Procedure LT-ESH-P-00012 Reporting Events, Torcon’s Safety Manager called BNL’s emergency number advising of an injury and requesting an ambulance. In parallel, Torcon’s site EMT was alerted of the injury and proceeded from Torcon’s Project Trailer to the accident location. Upon her arrival, she immediately started providing medical care. When Fire Rescue arrived at NSLS-II, Torcon employees directed Fire Rescue personnel directly to the accident scene where they assumed responsibility for the emergency. Fire Rescue commented that Torcon personnel were highly visible and accurate in their directions. After the injured was placed in the ambulance, Laboratory Protection personnel took control of the scene and secured it. Safety and Health Services personnel started to gather information, i.e., take pictures, measurements and statements. NSLS-II and Torcon personnel took the following actions the day of the accident: •
NSLS-II held a fact finding meeting with Torcon, Macedos Rebar Steel, and S&HSD. The Laborer was at the hospital and did not attend, the Operator had left for the day prior to the fact finding meeting. However, he returned the following day and S&HSD personnel obtained his statement.
•
A standdown was held the day of the accident to inform all workers of the event.
•
All rebar mechanical material handling activities were suspended and were not allowed to re-start without the approval of the NSLS-II Project Director.
NSLS-II and Torcon Personnel took the following actions the first several days following the accident: •
Torcon developed toolbox training on material handling and hazards associated with rebar.
•
NSLS-II and Torcon started holding daily ES&H meetings to discuss activities planned for the day as well as safety issues and responses by Torcon.
•
Torcon’s Corporate Safety Manager increased his weekly presence at the NSLS-II site.
•
Torcon started working with the subcontractor (Macedos, employer of the injured) on training topics.
•
BSA and Torcon started developing PHA’s for off-loading and moving rebar on site.
•
Torcon developed and started implementing a preliminary version of their corrective action plan prior to the completion of this report.
Draft
71
December 4, 2009
BNL NSLS-II Accident Investigation
5.1.1 DISCUSSION/RECOMMENDATIONS The procedures established in BSA’s Contractor Vendor Orientation and Torcon’s site orientation were followed and notifications were made swiftly. Within minutes of the injured being removed from the incident site, the scene was promptly secured by BNL Laboratory Protection and data collection was started, including statements from those in the area, photographs, measurements, and a fact finding meeting. These data provided the baseline for this investigation. Sr. Project Management’s walk down of the site and calling for a stand down to inform workers of the event and the implementation of immediate corrective actions, even before the investigation was completed, demonstrated their concern for the safety of all workers on site. The Accident Investigation Committee determined that NSLS-II and Torcon’s response to this event was acceptable.
5.2
SAFETY INCENTIVE PROGRAM
Though the Safety Incentive Program did not have any impact on this accident, it is part of the Accident Investigation Team’s Charter to review the adequacy of contractual safety requirements and the safety incentive program. BSA has designed a safety incentive to motivate Torcon to strive for continuous improvement and perform at a best-in-class level. This is reflected in Article 44, Safety Incentive, of the Contract. The safety incentive is based on three factors: 1. Accident/Injury Rates (Days Away, Restricted, Transferred (DART) Rate and Lost Work Day (LWD) case rates; 2. Serious violations of OSHA requirements; 3. Responsiveness to less serious OSHA violations. The DOE construction average for DART and LWD case rates are used to determine the award. The DART rate will be based on the rates for the most recent full year as presented in the DOE Computerized Accident, Incident Reporting System (CAIRS) database. The value of the safety incentive for the term of the Contract is set at two million Dollars. This earned incentive is to be paid by BSA to Torcon for superior safety performance over and above the contract price and is to be awarded as follows: • •
Up to five hundred thousand Dollars to be awarded annually 3 times, on the anniversary date of BSA’s Notice to Proceed, over the length of the contract; A final incentive of up to five hundred thousand Dollars when the contract is completed.
Work related illness and injuries are defined in 29CFR 1904, Final rule, the OSHA record keeping guidelines for Occupational Injuries and Illnesses, effective January 1, 2002.
Draft
72
December 4, 2009
BNL NSLS-II Accident Investigation
The basis for the award is as follows: •
• •
•
The first award will be made on the basis of DART and LWD case rates at the end of the first year following BSA’s Notice to Proceed. An additional award will be made each succeeding year for a maximum of three annual awards. Annual awards are not cumulative. No award will be made if the DART rate or LWD rate for the combined Contractor and subcontractor (working on site) rate is greater than the construction average from DOE’s CAIRS. Fifty percent of the maximum award will be granted if the DART rate and LWD rate for the combined Contractor and subcontractors at the site is less than or equal to the DOE construction annual average from CAIRS for the DART rate and three year rolling average for the LWD rate. Additional award is earned based on the percentage difference below the DOE average LWD rate only, reaching 100% at 50% of the DOE average LWD rate.
There will be a five thousand Dollar reduction of the earned annual award for each significant instance of OSHA violations, including but not limited to: • • • • • • • •
Any worker not properly using appropriate fall protection systems. Entry into a confined space without a required confined space permit or violation of permit requirements. Failure to use, when required, the Lock-out Tag-out procedures, as approved in Torcon’s Safety Plan. Any work on or near energized parts without a required Energized Electrical Work Permit or violation of permit requirements. Failure to report a recordable work related injury or illness to NSLS-II ES&H. Any fire caused by insufficient or inadequate fire protection measures. Excavation without required Dig/Penetration permit or violation of the requirements of a Dig Penetration permit. Failure to protect all excavation from cave-ins by adequate protection systems designed in accordance with 29CFR 1926.652.
In addition, there will be a five thousand Dollar reduction of the earned annual award for lack of responsiveness to less significant issues called to the attention of Torcon, including but not limited to: • • • • •
Repeated violations of any worker not wearing personal protective equipment, as required in Torcons’ safety plan. Repeated housekeeping issues at the job site, Repeated use of defective hand tools, power tools, extension cords, etc. Smoking in violation of the no-smoking policy, Repeated traffic violations issued on the BNL site.
There will be no annual award regardless of rates if there is a fatality, loss of limb, or an injury to the head resulting in permanent disability, at the work site. Determination of incentive award reductions will be made by the NSLS-II ES&H Manager. The final award will be made on the basis of cumulative injury rates over the time period of the conventional construction.
Draft
73
December 4, 2009
BNL NSLS-II Accident Investigation
There will be no award if the average DART Rate or LWD rate for Torcon including all subcontractors working at the site over the duration of the project is greater than CAIRS construction average for DART and LWD rates for the same period. Fifty percent of the final award will be granted if the DART Rate and LWD rate for Torcon and all subcontractors working at the site over the duration of the project is less than or equal to DOE construction average for DART and LWD rates for the same time period. Torcon’s SHE Program, Section 26, Safety Incentive Programs for the Project, Revision 3, dated June 9, 2009, outlines the potential distribution of any earned incentive as follows: 50% to the Union tradesmen, apportioned to the workers based on their man hours worked during the incentive period; 20% to the subcontractor company; and 5% to Torcon’s field supervision. The remaining 25% will be distributed to Torcon. Any workers or subcontractor companies receiving a violation during the incentive period will be disqualified from receiving the safety incentive payment. Torcon has also implemented short-term incentives or rewards programs for outstanding safety leadership or compliance. Torcon’s Labor/Management Safety Committee provides input into what programs are to be offered. Torcon uses these programs to reward workers and supervisors for showing the extra diligence and professionalism it takes to achieve high levels of safety. Torcon’s Project Orientation and General Safety & Health Rules pamphlet that is reviewed with all new employees does not mention the safety incentive program. However, Torcon’s Project Safety Orientating Outline includes a flyer called “Safety Pays”. This document briefly describes the safety incentive agreement with BSA and informs the workers that it is conceivable that a 100% incentive award earned with no workers being disqualified, could result in an average award of six thousand Dollars per tradesman, with some awards being much higher for tradesmen that are on the Project for the full three year duration. It further states that, even if you are no longer on the job, Torcon will pay any earned bonus Dollars directly to you, not your employer. Field workers were interviewed on their knowledge of the Safety Incentive Program. Many workers were aware of Torcon’s $50 gift card incentive, which is separate from the safety incentive program in the Contract. However, this too was not mentioned in Torcon’s Project Orientation, pamphlet, or SHE Program. Workers interviewed were not aware of the NSLS-II Safety Incentive Program. The NSLS-II construction workforce is partly made up of transient local Union trade workers, who, at the end of their particular phase of the work, will move on to other projects. The Accident Investigation Committee determined that the transient nature of the workers creates a situation where long-term buy-in is difficult to achieve. Short-term incentives can produce the desired results, if properly applied, promoted, and effectively delivered to the worker.
Draft
74
December 4, 2009
BNL NSLS-II Accident Investigation
5.2.1 DISCUSSION/RECOMMENDATIONS The Safety Incentive Program had no impact on this accident. It is extremely difficult for the Accident Investigation Committee to determine if the Safety Incentive Program, as stated in the Contract, has had an influence in improving safety considering the injuries that have occurred on the NSLS-II site to date. The Safety Incentive Program, as stated in the Contract, only indicates what awards will be paid out by BSA to Torcon. It is up to Torcon to determine how best to distribute the award to achieve the desired outcome. The Program is results oriented with only punitive actions for behavior, i.e. the loss of award monies as stated above. Torcon has indicated in their SHE Program how the award will be disbursed to workers. However, workers’ awareness of this program is low. Torcon has an incentive program of their own, used on this and other sites they manage, that rewards workers on the spot when observed working safely. It can be stated that the BSA Safety Incentive encourages this program on site. It is recommended that more emphasis be placed on informing workers of the safety incentive program, from the time when they start working on site and continuing throughout the project. Information concerning safety incentives could be added to Torcon’s Project Orientation and General Safety & Health Rules pamphlet, orientation outline, and as a toolbox topic. There were many discussions with the NSLS-II Safety team with respect to slow and sometimes nonresponsiveness from safety individuals working for Torcon. This was also witnessed by the Accident Investigation Committee. The Contract states that lack of responsiveness to less significant issues brought to Torcon’s attention will result in a five thousand Dollar reduction in the annual award per event. Torcon should be reminded of this and BSA should consider raising this amount for repeat occurrences and providing immediate feedback of any award reduction that will be taken. The use of gift cards, state lottery tickets, or theater tickets may allow the monetary incentive to effectively reach the field worker who will be on site for a short time. These incentives could be given to all employees on site during a particular week, or other short period of time, where no accident occurs.
Draft
75
December 4, 2009
BNL NSLS-II Accident Investigation
5.3
REVIEW OF CONSTRUCTION SAFETY PROGRAM IMPLEMENTATION
5.3.1 FIELD OBSERVATIONS During the course of this investigation, Accident Investigation Committee members who are professional construction safety inspectors, conducted site observations and interviewed workers. While conducting approximately 500 observations over seven days they did not observe any human performance safety deficiencies. In addition to the other findings identified previously in this report they made the following determination with respect to the implementation of the NSLS-II Construction Safety Program on the construction site:
there was a high degree of PPE compliance;
housekeeping was good;
environmental controls were effective;
all hardhats carried the BNL emergency number;
discussions with field workers indicated a positive attitude towards participating in efforts to make the site safe;
material staging and storage areas were well organized;
construction equipment appeared to be in good operating condition;
paths of travel for equipment were well established;
scaffolding was erected properly;
excavation practices were adequate.
5.3.2 ADEQUACY OF TORCON’S SAFETY PLAN IMPLEMENTATION AND FLOWDOWN TO SUBCONTRACTORS The Accident Investigation Team has determined that Torcon has adequately flowed down the requirements of its safety plan to subcontractors. However, Torcon failed to implement their SHE Program plan. The causes identified in Table 4 under Contributing Causes (Program Weakness) provide the basis for this determination.
5.3.3 ADEQUACY OF BNL OVERSIGHT OF TORCON’S SAFETY PROGRAM The Accident Investigation Team has determined that NSLS-II’s oversight failed to identify and correct all weaknesses in Torcon’s SHE Program plan. The causes identified in Table 4 under Contributing Causes (Program Weakness) provide the basis for this determination.
Draft
76
December 4, 2009
BNL NSLS-II Accident Investigation
5.3.4 RECOMMENDATIONS TO IMPROVE OVERALL CONSTRUCTION SITE SAFETY The ES&H requirements established by the NSLS-II Project, the Contract, and Torcon, provide a program that has the potential to produce a best-in-class performance.
Each element of this program plays an important and integral part in achieving the desired results and can be compared to a cable used for structural support. Each program element is like a strand within the cable. Taken together, each strand contributes to a cable’s functional design. The impact of a broken or weakened strand may not be evident at the beginning of cable use. However, as factors such as time, wind, sun, and structural load, start to impact the cable, the importance of each wire becomes more evident. As a result, detailed inspections and tests of the cable are conducted, using both visual means to evaluate the surface layers, and other means to ensure the internal layers are to specification. These inspections and tests are periodically repeated through the lift of the cable to ensure it maintains its integrity. Failure of the cable can cause significant results.
Likewise, when an ES&H program is designed, each element plays a part in the overall desired performance of that program. When one of those elements is not fully implemented as designed, or not implemented at all, the program fails to perform as intended. Impact to the program may not be immediately noticed, if noticed at all. However, as time goes on and events occur, these weaknesses may materialize in significant ways that cannot always be predicted. To prevent this from occurring, structured audits are required. Field inspections play an important part in ensuring the surface results, i.e., behavioral performance, is as expected, but they fall short in identifying internal elemental performance that is not as easily identified. This is why the Accident Investigation Committee recommends a well structured assessment program to complement the field inspections. The assessment program should be designed to ensure all elements of the ES&H program required by the Contract and ES&H Plans are functioning properly. The schedule should be established to ensure elements that support or monitor life protection programs (e.g., LOTO, confined spaces, excavation, electrical safety) are given priority. Finally, adequate resources must be provided to support the schedule.
Draft
77
December 4, 2009
BNL NSLS-II Accident Investigation
5.4
NON‐ACCIDENT INVESTIGATION JUDGMENT OF NEED ‐ HIPAA
The Accident Investigation Committee identified an additional need concerning the Health Insurance Portability and Accountability Act (HIPAA). HIPAA was enacted by the U.S. Congress in 1996. Title II of HIPAA, known as the Administrative Simplification (AS) provisions, defines numerous offenses relating to health care and sets civil and criminal penalties for them. It also creates several programs to control fraud and abuse within the health care system. On several occasions, the Accident Investigation Committee came in contact with BSA employees who stated they could not talk to the Committee about the incident due to HIPAA requirements and their fear of violating them. The Committee asked questions regarding the type of fracture, its location, and general medical care provided. At one point, members of the Committee were informed by a BSA employee that we could not ask the injured any questions about his injury due to HIPAA. Although this point was clarified by BNL’s legal department (yes, the Injured can talk about his injury), and HIPAA did not prevent us from completing our investigation, it did identify a need for BSA to develop and provide training on HIPAA as it applies to injuries and investigations on site. This would aid future investigations by providing clear instructions to all involved and ensure the HIPAA requirements are properly executed across the site.
Draft
78
December 4, 2009
BNL NSLS-II Accident Investigation
6.0
ACCIDENT INVESTIGATION COMMITTEE SIGNATURES
Draft
79
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX A
Draft
ACCIDENT INVESTIGATION COMMITTEE CHARTER
80
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
81
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX B WAIVER
Draft
82
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX C SUMMARY OF INTERVIEW STATEMENTS The following is a compilation of the statements obtained about the accident from the Laborer, Operator, and Worker 2, arranged in chronological order. Similar statements are combined for brevity. Dissimilar statements are both included and appropriately annotated. The Accident Investigation Committee’s reconstruction of the accident is provided in Section 2.1.2, Description of the Accident, page 25. On September 30, 2009, the Lull Operator employed by Macedos started work at approximately 0700 hours by working with carpenters to move material. At approximately 0815 hours, the Laborer, employed by Rebar Steel, asked the Operator to move some rebar, as directed by the Rebar Steel foreman that morning. The Laborer was directing the placement of the rebar load. The Operator and Laborer were moving bundles of rebar from the laydown area to an area where they could be hoisted with the crane. The Operator stated that he and the Laborer moved 6 to 7 loads of rebar before moving to the area where the incident occurred. The Laborer marked the rebar bundles to be moved by spraying them with orange paint. The Operator had previously worked with this Laborer and others before this day. The Laborer stated that on several previous occasions (not on the day of the accident) the Operator misread the Laborer’s hand signals and operated the Lull in a manner not expected by the Laborer. The Operator indicated there are several hand signal methods used on site and he had no problem with any of them. The Operator did not have any problem understanding the Laborer’s signals. The Laborer had never complained to the Operator about not following his signals. The Operator indicated to the Accident Investigation Committee that the Lull was in good working condition and he had no problem with it. The Operator also indicated to the Accident Investigation Committee that there was no unusual pressure placed upon him to get the job done. The Operator stated that the incident occurred with the first rebar bundle moved to the incident area, but the Laborer stated that it was the third bundle moved to the incident area. Both Operator and Laborer stated they were moving one bundle at a time. The responsible supervisor and Worker 2 indicated to the investigation team that there were two bundles being moved. At approximately 0835 hours, Worker 2 saw the Operator and Laborer placing a load of rebar onto the ground between two other loads of rebar already on the ground. The Operator stated that the Laborer was standing on several bundles of rebar approximately 5 feet in front of the forks of the Lull. The Operator stated that he was being guided by the Laborer who signaled the Operator to land the load. The Operator stated that the Lull was stopped prior to the load being placed. The Operator stated the Laborer directed him to drive over a bundle of rebar that was located at the incident area. The Operator stated that he had no problems with visibility; he was able to clearly see the Laborer at all times. The Laborer stated that he was facing the Lull and had indicated, using hand signals, for the Operator to stop movement, but the Operator stated that the Laborer had indicated for him to lay down the load while the Laborer was standing on a stack of rebar approximately 5 feet from where the load was to be dropped. Worker 2 stated that he saw the Laborer turn away as if he was going to get out of the way so the load could be placed, but also later stated to the investigation team that he did not see the incident. Draft
83
December 4, 2009
BNL NSLS-II Accident Investigation
The Operator stated that the Laborer, facing the Lull, backed up to move out of the way of the rebar, at the same time the Operator was in the process of placing the load. The Operator stated that the boom of the Lull was extended to permit the load to be placed in the area indicated by the Laborer. The Laborer stated that he was in the process of backing up out of the way when his right foot got stuck in the mud. As he was trying to move his foot, the Operator continued to move and lower the bundle of rebar. The Laborer was able to get his left foot out of the way, but the bundle of rebar rolled off the forks of the Lull and struck his right leg, resulting in the injury. The Laborer was facing the Operator when the load was placed. Per the Operator, as the load started to slide off the forks, the Laborer slipped off the bundles of rebar he was standing on into a sitting position and the load came down on his right lower leg. The Laborer stated that the bundle of rebar was not completely off of the Lull forks, some of the rebar was still supported by the forks. The Operator, responding to the Laborer’s screams, removed the rebar from his leg. The Operator stated that he did not remember if he speared or cradled the load off the Laborer’s leg. The Laborer rolled onto his stomach after the load was lifted. The Operator stated that he then exited the Lull and went to the injured. Worker 2 heard screaming and ran over to see the Laborer on the ground face down and the rebar above him, half on the forks of the Lull and the other half off the forks hanging several inches above Laborer’s legs. Worker 2 stated he did not see the incident occur; he was located behind a spoil pile at the time of the incident. When he arrived, the Operator was out of the Lull near the Laborer. At this time, the Operator saw the rebar on the forks and believed them not to be at a safe distance from the Laborer and moved the rebar back further by retracting the boom and by moving the vehicle backwards. After Worker 2 arrived at the scene, the Operator moved the load back further and dropped it to the ground. The Operator stated that he thought the bundle of rebar was still on the forks of the Lull when he moved the Lull back, but the first responding investigators did not find any rebar on the forks. The Laborer stated to Worker 2 while awaiting medical assistance that his foot got stuck in mud as he went to get out of the way of the load, and the rebar hit him.
Draft
84
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX D FOOTNOTES The statements of the people involved in the accident and some witnesses conflict with each other or with physical evidence. The following is the analysis of the statements and evidence that explains the conclusion of the Accident Investigation Committee for the sequence of events. 1 – After the incident the Lull was inspected by both the BNL Hoisting & Rigging Inspector and an equipment technician, and both found the Lull was sound and operating correctly. 2 - The Laborer arranged cribbing in the accident area, including moving a 2 x 4 inch piece of wood approximately 10 feet north to the incident location. There was an impression in the ground in the shape of a 2 x 4 inch piece of wood between the forks of the Lull, where it was located after the accident (Figure 10).
Figure 10. Tire marks and impression in the ground visible in the center, above the bundle of rebar.
3 - The Accident Investigation Committee believes the Operator and the Laborer moved two bundles of rebar, one with a bend and another bundle of ½ inch rebar before the incident bundles were moved. There was one statement by the Laborer that the incident bundle was the third bundle to be moved, and this fits with the placement of two different bundles already in the staging area. There is a bundle of rebar with a bend and a bundle of ½ inch rebar set on cribbing in the staging area (Figures 11 and 12). These would have come from different areas when they were unloaded, as was found in the piles of rebar around the area (Figure 13).
Draft
85
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 11. Staging area (accident location).
Figure 12. Staging area (accident location), including the Lull.
Draft
86
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 13. Rebar storage locations.
4 - There are two bundles of 1 ¼ inch rebar south of the other two bundles in the staging area. They are both marked with orange paint, and nearest to the forks of the Lull as it was found after the accident. The Laborer and Worker 2 both state that the rebar was partly on the forks of the Lull after it struck the Laborer. Two bundles would have that same appearance. The combined weight of the two bundles, 4,934 pounds, would still be within the capacity of the Lull at 18 feet of boom extension. 5 - The Laborer was found lying over and between two piles of rebar. The Laborer was reportedly 6 feet 2 inches tall (74 inches), and the distance between the rebar pile on which the laborer’s head was located post-accident, and the bundles of rebar in the staging area measured 59 inches. The two bundles of rebar in the staging area measured 24 inches wide. The Laborer also stated that his foot was stuck in mud. He could only make this statement if he knew he was standing on ground as opposed to standing on rebar immediately before the accident, as stated by the Operator. 6 - This conclusion is based upon Figures 8 and 14. One may easily see that an elevated load would block the view of the Laborer’s lower body while standing in the location in front of the staged rebar. 7 - The boom of the Lull was found at approximately 13 feet after the accident (see Figures 12 and 15). The Operator stated that he moved the load by retracting the boom and backing the vehicle. The capacity limit for the Lull is 5,000 pounds at approximately 18 feet. A load of 2,467 pounds for one bundle, or a load of 4,934 pounds for two bundles, was well within this rated capacity.
Draft
87
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 14. Operator’s view.
Figure 15. Load chart for Lull.
8 - This conclusion is drawn from the Operator’s and Laborer’s statements that the Laborer was facing the Lull at the time of the accident, and the Operator’s and Laborer’s statements that the Laborer was in the process of backing up at the time of the accident. During the second interview with Worker 2 he Draft
88
December 4, 2009
BNL NSLS-II Accident Investigation
stated that he did not see the accident occur. His observations were before the accident occurred and afterwards. Worker 2 stated he was behind the spoil pile at the time the Laborer was screaming. The spoil pile is the large mound of dirt visible in Figure 16. The crane is visible behind the spoil pile. Finally, the Accident Investigation Committee believes that the Laborer gave a “down” or “tilt down” signal to the Operator in anticipation that he would be out of the way of the load in a couple of steps. The Laborer, however, tripped or was otherwise stopped in his retreat by the rebar behind him. The Accident Investigation Committee reached this conclusion considering several facts or the lack thereof. The Operator has several operating engineer licenses and training certificates, as well as many years of construction site experience. The Laborer, however, has mostly yard experience and non-material handling construction experience, and no licenses or operating engineer training, as evidenced by the letter of “experience” provided by Rebar Steel Corporation. The Laborer’s statement regarding the Operator’s previous unexpected response to hand signals is not evidenced by other means. The Laborer did not tell anyone else of these experiences, and construction site management has no record or recollection of this issue. The Operator states he had previously worked with the Laborer and others before the day of the accident and had no trouble understanding the Laborer’s signals. The Operator indicated there are several hand signal methods used on site and he had no problem with any of them. As a crane operator as well as a forklift operator, the Operator would have had training and experience with different signals. The Accident Investigation Committee also evaluated the crane and forklift hand signals and does not believe that a crane stop signal could be misinterpreted as a tilt hand signal. Members of the Accident Investigation Committee have seen the crane stop signal used on the construction site.
Figure 16. The spoil pile is visible at the back of the photo.
9 - The Laborer states his foot became stuck in mud as he was backing. The members of the Accident Investigation Committee that responded to the accident site within an hour of the accident did not find mud at the accident site (see Figure 9). The precipitation report for the month of September shows that there were 1.39 inches of precipitation on September 27, 2009 and 0.12 inches of precipitation on September 28, 2009 (see Appendix I). The area of the accident has been significantly excavated and reshaped, and the normal soil for the entire Long Island area as well as the site is Class C or sandy soil. In addition, there was 0.74 inches of precipitation on October 3, 2009, and the Accident Investigation Draft
89
December 4, 2009
BNL NSLS-II Accident Investigation
Committee did not find any evidence of viscous mud that would trap an individual’s footwear. The rebar was slightly elevated and narrow in diameter, and its contact with the Laborer’s footwear might feel like the foot was stuck, but lateral motion would still be possible, hence the statement by the Laborer that he was able to get his left foot out of the way. (See also Figures 11 and 16.) 10 - This is evidenced by the broken cribbing at the accident site (see Figure 17), the position of the forks post-accident, the fact that the Operator could not immediately stop the load when he saw the Laborer slip, and the Operator’s statement that the load was sliding off the forks.
Figure 17. Broken cribbing.
11 - The Accident Investigation Committee came to this conclusion in order to explain the statement by the Laborer that the rebar was partly on the forks of the Lull after it struck him. This the Laborer would have seen before the Operator lifted the rebar from his leg. The Laborer also rolled onto his stomach after the rebar was lifted off his leg, therefore he might not have seen the rebar partially on the forks and partially off the forks when it was suspended above him, as the Operator and Worker 2 had seen. 12 - See Figures 10, 18, and 19. The bundles are identical, and the remnants of the wire tie are visible in the photographs. 13 - This is the statement by Worker 2, and is consistent with the statement by the Operator. 14 – The photographs show the Lull in a location after the accident that is away from the accident site. (The photographs show neither the load nor the Lull in a location that would contact the Laborer, who was located north of the Lull at the location of the staged rebar bundles.) Fresh tire marks are found in the soil leading from the incident rebar bundles to the Lull in its as-found location (see Figure 10).
Draft
90
December 4, 2009
BNL NSLS-II Accident Investigation
Figure 18. Broken center wire tie visible in bundle on the right-hand side.
Figure 19. Broken center wire tie visible in bundle in front of photograph.
Draft
91
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX E BARRIER ANALYSIS OF THE ACCIDENT (PHYSICAL AND ADMINISTRATIVE) Each barrier failure is keyed to Tables 3 and 4 in Section 4.0 (see p. 62), which summarize the event causes, provide the analytical technique that was used to establish the cause, and identify the associated Judgment of Need. The codes used are as follows: Direct Cause (DC), Root Cause (RC) and Contributing Cause to Program Weakness (CCW). Numbers following the codes indicate the specific causal factor.
Part 1: Physical Hazard: Mechanical Impact
Target: Laborer
How did the barrier perform?
Why did the barrier fail?
How did the barrier affect the accident?
Functioned as designed
Did not fail
Had no effect on accident
Functioned
Did not fail
Had no effect on accident
Appropriate soil (type & condition)
Functioned
Did not fail
Had no effect on accident
Appropriate grade
Functioned
Did not fail
Had no effect on accident
Appropriate weather conditions
Functioned
Did not fail
Had no effect on accident
Good housekeeping
Functioned
Did not fail
Had no effect on accident
Failed
Inadequate area for safest movement by Laborer
Created tripping hazard (RCE-2)
What were the barriers? Tools & Equipment Design/operation of Lull Maintenance of Lull Environment
Area staging
Draft
92
December 4, 2009
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact
What were the barriers?
Target: Laborer How did the barrier affect the accident?
How did the barrier perform?
Why did the barrier fail?
Pre-job brief / Job planning
Failed
Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
Missed opportunity to identify and address hazards (RCE-2)
Qualifications
Failed
Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned.
Enabled creation of hazardous condition (RCE-1)
Skills (ability to do job as intended)
Failed
Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned.
The Laborer put himself in close proximity to the load, which resulted in the accident. (RCE-1)
PPE
Functioned
Did not fail
Had no effect on accident
Communication (e.g., hand signals, language skills) †
Functioned
Did not fail
Had no effect on accident
Worker - Laborer
†
See discussion on the use of hand signals in section 3.1.1.
Draft
93
December 4, 2009
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact
What were the barriers?
Target: Laborer How did the barrier affect the accident?
How did the barrier perform?
Why did the barrier fail?
Pre-job brief
Failed
Briefings were primarily concentrated on what work needed to be performed and did not address the associated hazards.
Missed opportunity to identify and address hazards (RCE-2)
Qualifications
Functioned
Did not fail
Had no effect on accident
Skills (ability to do job as intended)
Functioned
Did not fail
Had no effect on accident
PPE
Functioned
Did not fail
Had no effect on accident
Communication (e.g., hand signals, language skills)
Functioned
Did not fail
Had no effect on accident
Worker - Operator
Draft
94
December 4, 2009
BNL NSLS-II Accident Investigation
Part 2: Administrative Hazard: Mechanical Impact What were the barriers?
Proof of Maintenance: Maintenance Log of Lull Proof of Inspection: Fire extinguisher inspection label (I.A.W. NFPA 10)
Torcon Safety Program: Subcontractor Project-Specific Safety Plan
Torcon Safety Program: PHA
Draft
Target: Laborer
How did the barrier perform?
Why did the barrier fail?
Failed
The maintenance log in the Lull was different from the one provided by Macedos.
Failed
The fire extinguisher located in the Lull did not have an inspection tag as required by NFPA 10. Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases. Implementation of Section 11 of Torcon’s SHE Program failed to identify and correct (1) the inadequate hazard analysis for material handling (the movement or directing the movement of materials is a major portion of Rebar Steel’s activities) and (2) the lack of review of PHA’s by new workers.
Failed
Failed
95
December 4, 2009
How did the barrier affect the accident? Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2) Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2)
Had no effect on accident. However, weakens the ES&H program by less than full implementation (CCW-2)
Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2)
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact What were the barriers?
Torcon Safety Program: Hazard Analyses
Torcon Safety Program: Heavy Equipment Inspection Records
Torcon Safety Program: Injury/Incident Investigations
Draft
Target: Laborer
How did the barrier perform?
Why did the barrier fail? Hazard analyses failed to identify hazards and lacked detail for the movement and placement of rebar. The hazard analysis for materials pick up with a forklift only addressed “dropping/misplacement pinch points” as a hazard and provided the following controls: “flagman direction/horn warning”, “cordoned off area with caution tape”, and “spotter will work with forklift”. Inspection records identified for use in Torcon’s SHE Program Section 14, Initial and Daily Inspections of Heavy Equipment, were different from what was actually being used.
Failed
Failed
Torcon’s failed to ensure all injuries were being reported in accordance with Torcon’s SHE Program, Section 19, Procedures for Injuries, Near Misses and Fires
Failed
96
December 4, 2009
How did the barrier affect the accident?
Hazard analysis did not specifically address material handling of rebar (i.e., material handling by Lull for concrete work on foundation), which is a major phase of this project. (RCE-2)
Had no effect on accident, however weakens the ES&H Program by less than full implementation (CCW-2) Had no effect on accident, however weakens the ES&H Program by less than full implementation and missing opportunities for improvement (CCW-2)
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact What were the barriers?
Torcon Safety Program: Post Drug and Alcohol Screening
Torcon Safety Program: Injury/Incident Investigations
Torcon Safety Program: Training
Draft
Target: Laborer
How did the barrier perform?
Why did the barrier fail? Torcon and its subcontractors did not indicate a clear responsibility for requesting drug and alcohol screening after an accident or injury. The Operator was not requested to submit for a drug and alcohol screening following the accident until 3 hours had passed and he had left the site. Supervisors not participating in investigations and believe the investigations are the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for participating in injury investigations. Supervisors believe toolbox training to the responsibility of the safety staff and not theirs, even though Torcon’s SHE Program clearly states that the supervisors are responsible for conducting toolboxes.
Failed
Failed
Failed
97
December 4, 2009
How did the barrier affect the accident?
Had no effect on accident. However, weakens the ES&H Program by less than full implementation. (CCW-1)
Had no effect on accident, however weakens the ES&H Program by Line abdicating safety responsibilities to safety staff (CCW-1)
Had no effect on accident, however weakens the ES&H Program by Line abdicating safety responsibilities to safety staff (CCW-1)
BNL NSLS-II Accident Investigation
Hazard: Mechanical Impact What were the barriers?
Target: Laborer How did the barrier affect the accident? Had no effect on accident, however weakens the ES&H Program by less than full implementation, loss of trending data to measure performance of program, and possibly less than adequate corrective actions and follow up. (CCW-2)
How did the barrier perform?
Why did the barrier fail?
Torcon Safety Program: Daily Job Site Inspections
Failed
Torcon’s Job Site Daily Inspection Records were not being completed daily by all subcontractors as required in Section 23 of Torcon’s SHE Program. In addition, those records were being improperly completed in most cases.
Training on unintentional contact with mobile equipment and personnel
Functioned
Did not fail
Failed
NSLS-II Construction Safety Inspectors did not document all findings, and reports were not properly processed or completed as required in BSA’s Construction Safety Subject Area, the Contract.
Functioned
Did not fail
Had no effect on accident
Functioned
Did not fail
Had no effect on accident
Failed
Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.
NSLS-II ES&H Management Plan: Construction Safety Inspections
Fitness for duty (as required by contract) capability to do task (prearrival drug screening) General, across site: high visibility garments Laborer supervision
Draft
98
December 4, 2009
Had no effect on accident Had no effect on accident, however weakens the ES&H Program by less than full implementation, loss of trending data to measure performance of program, and possibly less than adequate corrective actions and follow up. (CCW-4)
Staging crowded resulting in a trip hazard (RCE-1)
BNL NSLS-II Accident Investigation
APPENDIX F TAPROOT® ANALYSIS
Two Causal Factors were identified from the TapRooT® Analysis: •
Laborer in close proximity to load, and
•
Rebar Layout (staging) Less Than Adequate.
TapRooT defines Causal Factors as any problem associated with the incident that, if corrected, would have prevented the incident from occurring or would have significantly mitigated its consequences. Each TapRooT cause that was identified for the Causal Factor analyzed is keyed to the causal table found in section 4.0. The codes used are as follows: Direct Cause (DC), Root Cause (RC), and Contributing Cause to Program Weakness (CCW). Numbers following the codes indicate the specific causal factor found in Tables 3 and 4. This Appendix contains the Root Cause Trees that resulted from the analysis.
TAPROOT RESULT SUMMARY Causal Factor: Laborer in close proximity to load Training Understanding Needs Improvement (NI) Instruction NI - Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned. (RCE-1) Testing NI - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. The Laborer had a skill and knowledge deficiency that should have been caught by verification and corrected before allowing him to perform this work. Lack of verification failed to ensure mastery of required skills, knowledge, and abilities to necessary perform the work. (RCE-1) Continuing Training NI - Toolbox meetings topics were not always germane to the work hazards being encountered in the field. The continuing training program was inadequate. The toolbox training provided was not specific to tasks being performed. (CCW-2) Management System Oversight/Employee Relations Audits & Evaluations (A&E) lack depth - Torcon and its subcontractors failed to ensure their personnel were qualified for the work they were assigned. (RCE-1)
Draft
99
December 4, 2009
BNL NSLS-II Accident Investigation
Human Engineering Work Environment Housekeeping NI - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. The Laborer prepared an inadequate rebar staging area, which resulted in a trip and fall hazard. (RCE-1) Work Direction Selection of Worker Not Qualified Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. The Laborer prepared an inadequate rebar staging area, which resulted in a trip and fall hazard. (RCE-1) Causal Factor: Rebar Layout (staging) Less Than Adequate Training Understanding NI Continuing training NI - Toolbox meetings topics were not always germane to the work hazards being encountered in the field. The continuing training program was inadequate. The toolbox training provided was not specific to tasks being performed. (CCW-2) Management System Oversight/Employee Relations Audits & Evaluations (A&E) lack depth - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely. (RCE-1) Work Direction Selection of Worker Not Qualified - Torcon, Macedos, and Rebar Steel supervision failed to ensure the Laborer was qualified to perform the assigned work safely.The Laborer prepared an inadequate rebar staging area, which resulted in a trip and fall hazard. (RCE-1)
Draft
100
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
101
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
102
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
103
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
104
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX G EVENTS AND CAUSAL FACTORS ANALYSIS
Draft
105
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
106
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
107
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
108
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
109
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
110
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
111
December 4, 2009
BNL NSLS-II Accident Investigation
Draft
112
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX H ACCIDENT SCENE SURVEY
Draft
113
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX I BNL METEOROLOGICAL SUMMARIES FOR SEPTEMBER AND OCTOBER 2009 BROOKHAVEN NATIONAL LABORATORY METEOROLOGICAL SUMMARY MONTH SUMMARY FOR SEPTEMBER, 2009 Run: 2009,10,01,14,24,45 Day Precip(in) MinT(F) MaxT(F) Rad(W/m^2) MaxWind88(mph) 1 0.00 48.20 72.50 999 24.8 2 0.00 44.96 74.84 999 14.8 3 0.00 45.86 76.10 999 15.9 4 0.00 50.00 81.86 999 19.5 5 0.00 60.08 82.76 999 12.5 6 0.00 54.86 71.78 999 28.2 7 0.00 51.44 73.04 999 16.1 8 0.00 54.86 74.66 999 11.2 9 0.04 59.54 75.38 999 29.1 10 0.00 59.18 69.26 999 41.6 11 1.20 59.00 66.20 999 42.7 12 0.26 64.22 67.64 999 18.1 13 0.04 61.16 77.72 999 22.4 14 0.01 55.76 71.24 999 20.6 15 0.00 56.30 83.30 999 20.6 16 0.06 59.72 66.02 999 29.3 17 0.00 46.40 64.58 999 29.8 18 0.00 44.96 73.04 999 26.8 19 0.00 42.80 67.10 999 31.5 Draft
MxMnAvT(F) MeanT(F) HeatDD 60.35
60.02
4.6
0.0
-
59.90
59.51
5.1
0.0
-
60.98
60.78
4.0
0.0
-
65.93
65.47
0.0
0.9
-
71.42
70.25
0.0
6.4
-
63.32
65.36
1.7
0.0
-
62.24
61.04
2.8
0.0
-
64.76
63.88
0.2
0.0
-
67.46
65.56
0.0
2.5
-
64.22
62.89
0.8
0.0
-
62.60
62.97
2.4
0.0
-
65.93
65.86
0.0
0.9
-
69.44
68.63
0.0
4.4
-
63.50
63.59
1.5
0.0
-
69.80
68.34
0.0
4.8
-
62.87
62.85
2.1
0.0
-
55.49
56.96
9.5
0.0
-
59.00
60.23
6.0
0.0
-
54.95
56.35
10.0
0.0
-
114
CoolDD
December 4, 2009
BNL NSLS-II Accident Investigation
20 999 21 999 22 999 23 999 24 999 25 999 26 999 27 999 28 999 29 999 30 999
0.00 17.4 0.00 19.0 0.00 15.4 0.01 23.9 0.04 21.3 0.00 28.9 0.01 21.0 1.39 28.4 0.12 38.9 0.00 33.8 0.00 28.6
38.66
72.68
55.67
55.34
9.3
0.0
-
43.70
73.94
58.82
58.82
6.2
0.0
-
52.70
75.74
64.22
65.17
0.8
0.0
-
60.98
76.28
68.63
69.03
0.0
3.6
-
58.64
82.04
70.34
71.84
0.0
5.3
-
47.30
68.00
57.65
59.94
7.4
0.0
-
40.46
64.04
52.25
53.41
12.8
0.0
-
55.22
67.28
61.25
63.76
3.8
0.0
-
56.30
71.96
64.13
63.52
0.9
0.0
-
47.84
68.72
58.28
58.96
6.7
0.0
-
42.62
61.88
52.25
54.40
12.8
0.0
-
Mean Daily minimum temp = 52.1, Extreme minimum temp = Mean Daily maximum temp = 72.4, Extreme maximum temp = Month mean temp = 62.5 degF Monthly maximum wind speed (90 m) = 42.7 mph Monthly total precipitation = 3.18 inches Month total Heat DDs (F) = 111.3 (F) Month total Cool DDs (F) = 29.0 F Month mean insolation = -999.0 W/m^2
38.66 degF 83.30 degF
$$$NOTE$$$ After a calibration on the 85 meter temperature sensor a -2.2 degree offset was added to the Campbell program and the new program was installed at 1420 on 09/23/09. Definition: Heat degree day = MxMnAv - 65 (degF). Cool deg day = 65 MxMnAv (degF). If deg day < 0, set deg day to 0.0. 65 degF = 18.3 degC Ref: 'The Urban Climate' by Helmut E. Landsberg Temperature min/max based on 1-min averages Wind gust based on 1-min extreme data
Draft
115
December 4, 2009
BNL NSLS-II Accident Investigation
BROOKHAVEN NATIONAL LABORATORY METEOROLOGICAL SUMMARY MONTH SUMMARY FOR OCTOBER, 2009 Run: 2009,10,22,13,56,55 Day Precip(in) MinT(F) MaxT(F) Rad(W/m^2) MaxWind88(mph) 1 0.00 39.38 58.82 999 22.6 2 0.00 35.24 74.48 999 28.9 3 0.74 63.68 69.62 999 27.7 4 0.00 55.76 75.56 999 21.9 5 0.00 46.40 65.66 999 28.0 6 0.01 43.70 66.38 999 24.8 7 0.44 56.66 71.42 999 51.7 8 0.00 48.92 62.06 999 36.9 9 0.01 50.18 67.64 999 37.6 10 0.00 41.36 67.10 999 32.4 11 0.00 34.16 63.32 999 24.8 12 0.00 37.58 53.06 999 26.2 13 0.00 37.58 62.96 165 40.7 14 0.00 36.14 52.52 169 21.5 15 0.81 40.82 44.96 181 39.4 16 0.07 39.74 46.22 169 36.9 17 0.00 43.70 51.80 999 31.3 18 0.91 39.92 47.30 999 45.2 19 0.00 31.10 53.96 999 24.6 20 0.00 30.20 65.66 999 20.8
Draft
MxMnAvT(F) MeanT(F) HeatDD 49.10
49.12
15.9
0.0
-
54.86
54.69
10.1
0.0
-
66.65
65.87
0.0
1.7
-
65.66
63.79
0.0
0.7
-
56.03
56.19
9.0
0.0
-
55.04
55.55
10.0
0.0
-
64.04
63.21
1.0
0.0
-
55.49
55.37
9.5
0.0
-
58.91
60.81
6.1
0.0
-
54.23
59.68
10.8
0.0
-
48.74
49.27
16.3
0.0
-
45.32
45.86
19.7
0.0
-
50.27
52.59
14.7
0.0
44.33
44.93
20.7
0.0
42.89
42.68
22.1
0.0
42.98
42.65
22.0
0.0
47.75
47.23
17.3
0.0
-
43.61
43.54
21.4
0.0
-
42.53
42.61
22.5
0.0
-
47.93
46.75
17.1
0.0
-
116
CoolDD
December 4, 2009
BNL NSLS-II Accident Investigation
21 999 22 999 23 999 24 999 25 999 26 999 27 999 28 999 29 999 30 999 31 999
0.00 14.1 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999 -999
40.46
69.08
54.77
51.73
-999
-999
-999
-999
-999
-999
-999
-999
-999
-999
10.2
0.0
-
-999
-999
-
-999
-999
-999
-
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
-999
-999
-999
-999
-999
-999
-
Mean Daily minimum temp = 42.5, Extreme minimum temp = Mean Daily maximum temp = 61.4, Extreme maximum temp = Month mean temp = 52.1 degF Monthly maximum wind speed (90 m) = 51.7 mph Monthly total precipitation = 2.99 inches Month total Heat DDs (F) = 276.2 (F) Month total Cool DDs (F) = 2.3 F Month mean insolation = 42.7 W/m^2
30.20 degF 75.56 degF
Definition: Heat degree day = MxMnAv - 65 (degF). Cool deg day = 65 MxMnAv (degF). If deg day < 0, set deg day to 0.0. 65 degF = 18.3 degC Ref: 'The Urban Climate' by Helmut E. Landsberg Temperature min/max based on 1-min averages Wind gust based on 1-min extreme data Missing data = $missing, signifies > $
Draft
117
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX J DESCRIPTION OF RADIO TRANSMISSIONS Radio Transmissions at BNL on September 30, 2009 that concern the NSLS-II Accident (Note: there is approx. a two-minute difference in the time logged by the system and the actual time.) Time logged Description of Call 8:45:21
Leg injury, possible serious injury at NSLS-II
8:46:17
Rescue 4 on route to NSLS-II; fire captain contacted fire rescue to request Motor Pool expedite Ambulance and get it back to fire rescue as soon as possible
8:47:09
Fire Captain speaking...[cannot understand]
8:47:21
Captain ‡ is at the entrance to NSLS-II
8:47:59
Captain is looking for confirmation of exact location; fire rescue confirmed it’s on the west side by Princeton
8:48:31
Captain said he is on scene at 8:46.
8:48:43
Ambulance on route and Rescue 4 on scene [general area]
8:49:03
Captain contacted Rescue 4; specific directions
8:49:33
Captain called Fire Rescue; standby
8:49:51
Captain transmits what kind of injury the patient has: male with compound fracture to right leg; fire rescue repeats “all units be advised compound fracture...”; tells fire dispatcher that he needs aviation; fire dispatcher asks if captain wants him to handle it or if he will; Captain replies that he will handle it [contact Fire Rescue and Suffolk for helicopter]
8:51:21
Captain calling police headquarters [PDHQ]
8:51:31
Captain calling police headquarters [PDHQ]
8:51:42
Captain calling police headquarters [PDHQ]
8:52:08
PDHQ responds
8:52:36
Fire Rescue to Captain: asks if he wanted an engine to stand by at the landing zone; Captain says yes and to notify police that this will leave the base unmanned; Captain says that he will call Fire Rescue [& Emergency Services, Suffolk County, Yaphank] to get an ETA of the bird.
8:53:17
Fire House calls Captain to say that he has two firefighters in quarters, would he like him to stay on radio [indicating that base is not unmanned]; staying on radio
8:53:55
PDHQ calls Captain
8:54:12
PDHQ requests confirmation that Captain is calling for helicopter so he does not have to
‡
“Captain” in this document refers to Fire Captain.
Draft
118
December 4, 2009
BNL NSLS-II Accident Investigation
8:54:36
Captain asks PDHQ that an ORPS Coordinator respond to the scene
8:54:53
Confirmed 8:53; Engine 2 going to PDHQ [for helicopter landing]
8:56:29
Engine 2 on scene [at the landing zone]
8:58:46
Police asks Fire if they got the page; says standby
9:00:32
Police says “go ahead Fire” (phone rings)
9:00:51
OK Fire, thanks
9:01:01
Ambulance [Unit 16] signaled to Stony Brook [this means they are on route to Stony Brook University Medical Center (Stony Brook)]
9:01:21
Fire calling Ambulance [no response]
9:01:35
Fire Rescue asks Captain if they are transporting patient via ground; Captain replies “yes”.
9:02:52
Fire to Engine 2
9:03:09
Fire to Engine 2
9:03:18
Engine 2 responds he read [the transmission] direct and he is returning to quarters
9:04:43
Captain: ES 2 and Rescue ok to return to quarters; Ambulance signal 18 [this means”on route”] to Stony Brook; Captain will wait on scene for the ORPS categorizer; Fire says OK; 34 later [phone call]
9:06:11
Rescue is returning to quarters
9:09:07
Captain informs Ambulance that it was 2,400 pounds of steel [that caused the injury]
9:14:08
Fire calling Ambulance asking for crew [names]
9:14:25
Ambulance provides names
9:14:48
[More about crew]
9:15:25
Ambulance picked up a first responder [from Farmingville Fire House]
9:27:55
[not related to this investigation]
9:28:32
[not related to this investigation]
9:36:21
Confirmed 9:34: Ambulance arrived at Stony Brook
9:52:11
Captain tells Fire Rescue that he is leaving the scene
10:04:43
Ambulance calling BNL Fire Rescue; leaving Hospital, on route back to BNL; needs to drop off first responder where he was picked up
10:29:32
At exit 68 of LIE; should be there in a couple of minutes; have somebody with a broom stand by to clean the Ambulance because it needs to get back to the Motor Pool right away
10:43:31
Dropping off Ambulance at Motor Pool
Draft
119
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX K DESCRIPTION OF CALL TO BNL EMERGENCY REPORTING NUMBER
Date September 30, 2009
Time logged 8:44:13
Description of Call The Safety Manager for Torcon reports an injury that needs an ambulance; injury to leg, perhaps seriously, of one of our workers. He also reports the location: Vehicle tunnel, NSLS-II, west side of project; Princeton Avenue; at entrance in gate, take road to the left. Responder replies: We’re on our way.
Draft
120
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX L LETTER FROM REBAR STEEL CORP. DETAILING LABORER’S EXPERIENCE
Draft
121
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX M • • •
REFERENCE DOCUMENTS
Investigation Team Charge Memo Memo, G.S. Podonsky to M. Holland, October 7, 2009, Waiver of Type B Accident Investigation Occurrence Notification Report. SC-BSHO-BNL-BNL-2009-0019
Section 1: Contracts and Procedures BNL/NSLS-II • • • • • • • • •
Final Hazard Analysis Report for NSLS-II ES&H Management Plan for the Conventional Construction of NSLS-II Facilities (LT-ESH-0009, Rev. 1, February 2009) Management Plan for Construction of NSLS-II Conventional Facilities Rev. 1 (LT-CFD-002-CD-Rev 01, June 2009) NSLS-II ES&H Procedures BNL/Torcon Contract Final Report – Assessment of BNL NSLS-II Project Training Requirement NSLS-II ESH Monthly Meeting Minutes Environment, Safety, and Health Plan for the NSLS-II NSLS-II Construction Environment, Safety and Health Plan for Conventional Construction of the Ring Building (LT-ESH-0006/rev 1, April 2009)
Torcon • • • • • • • • • •
•
Torcon Safety Violation Log Torcon Labor/Management Safety Committee Meeting Minutes (meetings #20, 9/10/09; #21, 9/17/09; #22, 9/24/09) Torcon Organization Chart for the NSLS-II Ring Building Construction Torcon Master Badge List (Names in red indicate those who have been disciplined or discharged for cause) Torcon NSLS-II Project Safety Orientation, Rev. 6, September, 2009 (Section 10 describes preemployment drug testing) Torcon Project Orientation and General Safety and Health Rules (page 6 describes drug testing for cause). Each employee must sign an acknowledgement following training. BSA’s Torcon Assessment Schedule Resume of Tom Moon, Torcon Site Safety Manager Torcon Safety Incentive Program Torcon Corporate Policy, Drug-free Workplace Policy; Excerpt from Torcon Project SH & E Program regarding Drug-free Workplace Policy; and Procedures regarding Drug Collection Torcon Project Safety, Health and Enviornment Program (Original, Rev. 2 and Rev. 3)
Macedos • • Draft
Various Tool-Box training sessions conducted by Macedos Macedos Construction Lull Service Records 122
December 4, 2009
BNL NSLS-II Accident Investigation
• • •
Lull Safety Manual and Operating Manual Lull Technical Brochure and Specification Sheet Daily Inspection Service Log for Lull
Other •
NY State Dept. of Health, Bureau of Emergency Medical Services, Policy Statement (Advanced Life Support) and F&O SOP Emergency Medical Services (EMS) Program, FR-EMS-3.00, Rev. 5, effective 12/12/07
Section 2: Reports prior to the Accident • • •
•
• • • • Draft
Internal Audit and Oversight Report, IO 09-07 Phase I, NSLS-II Construction Safety Program Review, Phase 1, 8/26/09 Various e-mails between Torcon and BNL involving safety observations Various Phase Hazard Analyses o Rebar Steel – installing rebar and wire welded mesh o Macedos – Crane Operations o Macedos – DOCA Formwork using lifting clamps o Macedos – Installing Monuments o Macedos – Ring Tunnel Footings o Macedos – Project: All Footings o G.E. Modular – Install. of Project Office Trailers o Vollers Ex. & Const. – Silt Fence Installation o Vollers/Advanced Env. Services – Removal of Underground Transite Pipe (pre-existing) o Rebar Steel – Fabrication of Rebar o GLS Elec.- cad Welding Footings o Macedos – Heat Exposure o Macedos – Formwork Mockups o Macedos – “Other Contractor” Exposure o Macedos – Crane Operations: Vehicle Tunnel Formwork o Macddos – Pre Mobilization/New Hires Reports of Accidental Injury or Occupational Disease o 9/30/09: Lather, Rebar Steel, right leg (Torcon, Rebar Steel, and Pembrooke reports) o 9/28/09: Carpenter, Macedos, right calf muscle (Torcon report only) o 9/21/09: Laborer, Macedos, left ankle (Pembrooke report only) o 9/2/09: Lather, Rebar Steel, left elbow (Torcon and Pembrooke reports) o 8/13/09: Manager, Torcon, right calf muscle (Pembrooke report only) o 8/13/09: Concrete, Macedos, left arm (Pembrooke report only) o 8/10/09: Laborer, Vollers, nosebleed (Pembrooke report only) o 8/7/09: Inspector, BNL, left and right knee (Pembrooke report only) o 8/5/09: Lather, Pratt Brothers, left forearm (Torcon and Pembrooke reports) o 7/27/09: Eng., Vollers, right elbow (Pembrooke report only) o 7/16/09: Electrician, Hinck Electric, chipped tooth (Torcon and Pembrooke reports) o 4/16/09: Trailer Installer, Modular Dimensions, right heel (Torcon report only) E-mail dated 4/16/09 from M. Fallier to various re: heel injury E-mail dated 4/22/09 from M. Fallier to various re: Torcon Safety Concerns Notice to proceed with Ring Building construction – 3/25/09 Series of e-mails regarding Work Observations at NSLS-II site on 4/20 & 4/21/09 123
December 4, 2009
BNL NSLS-II Accident Investigation
• • • • • • •
Report from PTI to Leon Baukh, dated 9/9/09 , BNL NSLS-II Ring Building General Loss Control Service Visit on 9/3/09 Daily Inspection Reports, conducted by BNL, January – August 2009 Liberty Mutual Report, dated, 9/2/09, of visit to NSLS-II Construction Site on 8/19/09 Liberty Mutual Report, dated, 9/29/09, of visit to NSLS-II Construction Site on 9/10/09 Allied North America, site visit conducted July 24, 2009 Torcon Dairly Jobsite Safety Inspections Project Safety Evaluations
Section 3: The Accident • • • • • • • • • • • • • • • • • • • • • • •
BNL weather summaries for September 30, 2009 Fact finding meeting notes taken by NSLS-II Construction Safety Inspectors – September 30, 2009 BNL Fire/Rescue Report Torcon (Pembrooke) Incident Report Torcon Report of Accidental Injury, preliminary Statement of Laborer (injured party) Letter from Rebar Steel dated 10/9/09 – Experience of Laborer Laborer Training History Results of Drug Test for Laborer and Operator Witness statement by Operator, including training records and list of persons in attendance during his statement Forklift Training Program and Certification for Operator Witness statement by Laboer2, Macedos Construction Witness Statement by Laboer3, Macedos Construction Witness statement by Pembroke EMT Witness statement by BNL Fire/Rescue Captial Statement by BNL EMT Response Team Response from BNL Fire/Rescue – Statement of Medical Response Personnel Photo Log Photographs of scene – post accident Photographs taken from the HFBR stack at 8:30, 8:45, and 9:00 A.M. Photographs taken 10/5/09 at scene of accident Topographical survey – Lull and rebar site (site of accident of 9/30/09), dated 10/7/09 Rebar Steel Accident Report
Section 4: Post-Accident Data • • • • • • • • • Draft
Torcon Safety Stand-down memo (including attendance sheet) Letter dated 10/2/09 – Torcon Measures in Response to 9/30/09 Accident Torcon Safety Stand-down meeting, 10/2/09 Corrective Action and Restart Plan dated 10/7/09 Minutes of Morning Safety Meeting, 10/9/09 Hand Signals Tool Box, 10/14/09 Phase Hazard Analyses for rebar handling with a forklift and for unloading rebar from trucks (including attendance sheet) Signed PHAs (2) for movement of rebar, Rev. 7, 10/7/09 Photos of rebar demonstration using approved PHAs 124
December 4, 2009
BNL NSLS-II Accident Investigation
• • • • • • • • • • •
Draft
Authorization to restart mechanical rebar operations Two lift plans: (1) DOCA Formwork using crane; (2) installation of steel columns at vehicle and utility tunnels Interview with Macedos Construction on 10/7/09 Interview with Torcon Construction on 10/8/09 Interview with Rebar Steel Supervision on 10/13/09 Safety Observations, LSII Project, Accident Investigation Committee Member, 10/12/09 Field Observations Summary, Accident Investigation Committee Member, 10/15/09 Memo dated 10/15/09, requesting additional information, and answers provided Torcon, Inc. Safety Status Report #1, 10/16/09 Internal Audit and Oversight Report, 10 09-07 Phase 2, NSLS-II Construction Safety Program Review, Phase 2, 10/21/09 Draft Copy of Worker Safety and Health Management System Description, SBMS, printed 10/21/09
125
December 4, 2009
BNL NSLS-II Accident Investigation
APPENDIX N ACCIDENT INVESTIGATION COMMITTEE MEMBERS
Lead Raymond Costa Facilities & Operations Brookhaven National Laboratory 631-344-8227 [email protected]
Member David Fuller SNS-ES&H Oak Ridge National Laboratory 865-241-9095 [email protected]
Member Edward Sierra Quality Management Office Brookhaven National Laboratory 631-344-4080 [email protected]
Member Steven Kane Safety & Health Services Division Brookhaven National Laboratory 631-344-7236 [email protected]
Member Tom Conrad Safety & Health Services Division Brookhaven National Laboratory 631-344-5789 [email protected]
Consultant Brad Tullis Dade Moeller & Associates Richland, WA 541-619-1126 [email protected]
Observer Chris Seniuk BHSO-DOE 631-344-2034 [email protected]
Consultant William Brown, PhD Quality Management Office Brookhaven National Laboratory 631-344-7230 [email protected]
Member - Documentation Sabine Kessler Quality Management Office Brookhaven National Laboratory 631-344-4340 [email protected]
Draft
126
December 4, 2009
Reliability Prediction Procedure for Electronic Equipment, Telcordia SR-332, Issue 01, May 2001 (telecom-info.telcordia.com), Bellcore TR-332, Issue 06 [53] EPRD, Electronic Parts Reliability Data (RAC-STD-6100), Reliability Analysis Centre, 201 Mill Street, Rome, NY 13440 [54]. Income Tax Case laws decided in March 2016. Download Preview. Description: Income Tax Caselaws #pdf Submitted By: Raju S Narayanan on 04. In 2000, Telcordia and Verisign committed themselves to Telephone Number Mapping or Electronic NUMbering (ENUM). [255] By coincidence, Lucent, which continued to see itself as an AT&T lab, also saw ENUM as their solution for internet telephony problems. Sometimes it seemed as if AT&T and SAIC/Telcordia were two faces of a same strategy. 2 SR-332, Issue 1, Reliability Prediction Procedure for Electronic Equipment, Telcordia, May 2001. 3 SR-332, Issue 2, Reliability Prediction Procedure for Electronic Equipment, Telcordia, September 2006. 4 ITEM Software and ReliaSoft Corporation, RS 490 Course Notes: Introduction to Standards Based Reliability Prediction and Lambda Predict, 2006. Mixing Reliability Prediction Models Maximizes Accuracy Overcome Component Limitations, Better Reflect Past Experiences, and Achieve Superior. The Military Handbook for the Reliability Prediction of Electronic Equipment Military. Telcordia Technologies Special Report SR-332) Commercial, United States Offers analysis ranging from.
definition - Reliability engineering
definition of Wikipedia
Wikipedia
Reliability engineering is an engineering field that deals with the study, evaluation, and life-cycle management of reliability: the ability of a system or component to perform its required functions under stated conditions for a specified period of time.[1] Reliability engineering is a sub-discipline within systems engineering. Reliability is often measured as probability of failure, frequency of failures, or in terms of availability, a probability derived from reliability and maintainability. Maintainability and maintenance are often important parts of reliability engineering.
Reliability engineering is closely related to safety engineering, in that they use common methods for their analysis and may require input from each other. Reliability engineering focuses on costs of failure caused by system downtime, cost of spares, repair equipment, personnel and cost of warranty claims. The focus of safety engineering is normally not on cost, but on preserving life and nature, and therefore deals only with particular dangerous system failure modes.
Reliability engineering for complex systems requires a different, more elaborate systems approach than reliability for non-complex systems. Reliability analysis has important links with function analysis, requirements specification, systems design, hardware design, software design, manufacturing, testing, maintenance, transport, storage, spare parts, operations research, human factors, technical documentation, training and more. Effective reliability engineering requires experience, broad engineering skills and knowledge from many different fields of engineering.
|
Overview
A reliability block diagram showing a 1oo3 (1 out of 3)redundant designed subsystem
Reliability may be defined in several ways.
- The idea that something is fit for a purpose with respect to time.
- The capacity of a device or system to perform as designed.
- The resistance to failure of a device or system.
- The ability of a device or system to perform a required function under stated conditions for a specified period of time.
- The probability that a functional unit will perform its required function for a specified interval under stated conditions.
- The ability of something to fail well.
Reliability engineering is a special discipline within Systems engineering. Reliability engineers rely heavily on statistics, probability theory, and reliability theory to set requirements, measure or predict reliability and give advice on improvements for reliability performance. Many engineering techniques are used in reliability engineering, such as Reliability Hazard analysis, Failure mode and effects analysis (FMEA), Fault tree analysis, Reliability Prediction, Weibull distribution analysis, thermal management, reliability testing and accelerated life testing. Because of the large number of reliability techniques, their expense, and the varying degrees of reliability required for different situations, most projects develop a reliability program plan to specify the reliability tasks that will be performed for that specific system.
The function of reliability engineering is to:
- develop the reliability requirements for the product
- establish an adequate life-cycle reliability program
- show that corrective measures (reliability risk mitigation) produce reliability improvements
- perform appropriate analyses and tasks to ensure that
- the product will meet its requirements
- the unreliability risk is controlled and brought to an acceptable level.
In line with the creation of safety cases for safety, it needs to provide a robust set of (statistical) evidence and justification material to verify if the top reliability or availability requirements can or have been met. The goal is to first identify the reliability hazards, assess the risk associated with them and to control the risk to an acceptable level. What is acceptable is determined by the managing authority or customers. These tasks are normally managed by a reliability engineer or manager, who may hold an accredited engineering degree and has additional reliability-specific education and training.
Reliability engineering is closely associated with maintainability engineering and logistics engineering, e.g. Integrated Logistics Support (ILS). Many problems from other fields, such as security engineering and safety engineering, can also be approached using common reliability engineering techniques.
Many types of engineering employ reliability engineers and use the tools and methodology of reliability engineering. Reliability engineering is performed throughout the entire life cycle of a system, including development, test, production and operation.
Reliability theory
Main articles: Reliability theory and Failure rate
Reliability theory is the foundation of reliability engineering. For engineering purposes, reliability is defined as the probability that a device will perform its intended function during a specified period of time under stated conditions. Mathematically, this may be expressed as,
- ,
- where is the failure probability density function and is the length of the period of time (which is assumed to start from time zero).
Reliability engineering is concerned with four key elements of this definition:
![Handbook Handbook](/uploads/1/2/4/7/124782683/469263125.jpg)
- Reliability is a probability. This means that failure is regarded as a random phenomenon: it is a recurring event, and we do not express any information on individual failures, the causes of failures, or relationships between failures, except that the likelihood for failures to occur varies over time according to the given probability function. Reliability engineering is concerned with meeting the specified probability of success, at a specified statistical confidence level.
- Reliability is predicated on 'intended function:' Generally, this is taken to mean operation without failure. However, even if no individual part of the system fails, but the system as a whole does not do what was intended, then it is still charged against the system reliability. The system requirements specification is the criterion against which reliability is measured.
- Reliability applies to a specified period of time. In practical terms, this means that a system has a specified chance that it will operate without failure before time . Reliability engineering ensures that components and materials will meet the requirements during the specified time. Units other than time may sometimes be used. The automotive industry might specify reliability in terms of miles, the military might specify reliability of a gun for a certain number of rounds fired. A piece of mechanical equipment may have a reliability rating value in terms of cycles of use.
- Reliability is restricted to operation under stated (or explicitly defined) conditions. This constraint is necessary because it is impossible to design a system for unlimited conditions. A Mars Rover will have different specified conditions than a family car. The operating environment must be addressed during design and testing. Also, that same rover may be required to operate in varying conditions requiring additional scrutiny.
Reliability program plan
Many tasks, methods and tools can be used to achieve reliability. Every system requires a different level of reliability. A commercial airliner must operate under a wide range of conditions. The consequences of failure are grave, but there is a correspondingly higher budget. A pencil sharpener may be more reliable than an airliner, but has a much different set of operational conditions, insignificant consequences of failure and a much lower budget.
A reliability program plan (RPP) is used to document exactly what 'best practices' (tasks, methods, tools, analyses and tests) are required for a particular (sub)system, as well as clarify customer requirements for reliability assessment. For large scale, complex systems, the Reliability Program Plan is a distinctive document.
For simple systems, it may be combined with the systems engineering management plan or an integrated logistics support management plan. A reliability program plan is essential for a successful reliability, availability and maintainability (RAM) program and is developed early during system development and refined over the systems life-cycle. It specifies not only what the reliability engineer does, but also the tasks performed by other stakeholders. A reliability program plan is approved by top program management, which is responsible for identifying resources for its implementation.
Technically, often, the main objective of a Reliability Program Plan is to evaluate and improve availability of a system and not reliability. Reliability needs to be evaluated and improved related to both availability and the cost of ownership (due to cost of spar parts, maintenance man-hours, transport costs etc.). Often a trade-off is needed between the two. There might be a maximum ratio between availability and cost of ownership.
Whether availability or Cost of Ownership is more important depends on the use of the system. For example, a system that is a critical link in a production system – for example a big oil platform – is normally allowed to have a very high cost of ownership if this translates to even a minor increase in availability, as the unavailability of the platform directly results in a massive loss of revenue which can easily exceed the basic cost of ownership.
Testability of a system should also be addressed in the plan as this is the link between reliability and maintainability. The maintenance (the maintenance concept / strategy) can influence the reliability of a system (e.g. by preventive maintenance), although it can never bring it above the inherent reliability. Maintainability influences the availability of a system – in theory this can be almost unlimited if one would be able to repair a fault in a very short time.
A proper reliability plan should normally always address RAMT analysis in its total context. RAMT stands in this case for Reliability, Availability, Maintainability/Maintenance and Testability in context to users needs with regard to the technical requirements (as translated from the needs).
Reliability requirements
For any system, one of the first tasks of reliability engineering is to adequately specify the reliability and maintainability requirements as defined by the stakeholders in terms of their overall availability needs. Reliability requirements address the system itself, including test and assessment requirements, and associated tasks and documentation. Reliability requirements are included in the appropriate system/subsystem requirements specifications, test plans and contract statements. Maintainability requirements address system issue of costs as well as repair time. Evaluation of the effectiveness of corrective measures is part of a FRACAS process that is usually part of a good RPP.
Reliability prediction and improvement
Reliability prediction is the combination of the creation of a proper reliability model together with estimating (and justifying) the input parameters for this model (like failure rates for a particular failure mode or event and the mean time to repair the system for a particular failure) and finally to provide a system (or part) level estimate for the output reliability parameters (system availability or a particular functional failure frequency).
Some recognized authors on reliability – e.g. Patrick O'Conner, R. Barnard and others – have argued that too much emphasis is often given to the prediction of reliability parameters and more effort should be devoted to prevention of failure (reliability improvement). The reason for this is that prediction of reliability based on historic data can be very misleading, as a comparison is only valid for exactly the same designs, products under exactly the same loads / context. Even a minor change in detail in any of these could have major effects on reliability. Furthermore, normally the most unreliable and important items (most interesting candidates for a reliability investigation) are most often subjected to many modifications and changes. Also, to perform a proper quantitative reliability prediction for systems is extremely difficult and expensive if done by testing. On part level, results can be obtained often with higher confidence as many samples might be used for the available testing financial budget, however unfortunately these tests might lack validity on system level due to the assumptions that had to be made for part level testing.
Testing for reliability should be done to create failures, learn from them and to improve the system / part. The general conclusion is drawn that an accurate and an absolute prediction – by field data comparison or testing – of reliability is in most cases not possible. A exception might be failures due to wear-out problems like fatigue failures. In the introduction of Mil. Std. 785 it is written that reliability prediction should be used with great caution if not only used for comparison in trade-off studies.
Furthermore, based on the latest insights in Reliability centered maintenance (RCM), most (complex) system failures do no occur due to wear-out issues (e.g. a number of 4% has been provided, refer to RCM page). The failures are often a result of combinations of more and multi-type events or failures. The results of these studies have shown that the majority of failures follow a constant failure rate model, for which prediction of the value of the parameters is often problematic and very time consuming (for a high level reliability – part level). Testing these constant failure rates at system level, by for example mil. handbook 781 type of testing[clarification needed], is not practical and can be extremely misleading.
Despite all the concerns, there will always be a need for the prediction of reliability.[says who?] These numbers can be used as a Key performance indicator (KPI) or to estimate the need for spares, man-power, availability of systems etc.
Reliability predictions:
- help assess the effect of product reliability on maintenance activity and the quantity of spare units required for acceptable field performance of any particular system. For example, predictions of the frequency of unit level maintenance actions can be obtained. Reliability prediction can be used to size spare populations.
- provide necessary input to system-level reliability models. System-level reliability models can subsequently be used to predict, for example, frequency of system outages in steady-state, frequency of system outages during early life, expected downtime per year, and system availability.
- provide necessary input to unit and system-level Life Cycle Cost Analyses. Life cycle cost studies determine the cost of a product over its entire life. Therefore, how often a unit will have to be replaced needs to be known. Inputs to this process include unit and system failure rates. This includes how often units and systems fail during the first year of operation as well as in later years.
- assist in deciding which product to purchase from a list of competing products. As a result, it is essential that reliability predictions be based upon a common procedure.
- can be used to set factory test standards for products requiring a reliability test. Reliability predictions help determine how often the system should fail.
- are needed as input to the analysis of complex systems such as switching systems and digital cross-connect systems. It is necessary to know how often different parts of the system are going to fail even for redundant components.
- can be used in design trade-off studies. For example, a supplier could look at a design with many simple devices and compare it to a design with fewer devices that are newer but more complex. The unit with fewer devices is usually more reliable.
- can be used to set achievable in-service performance standards against which to judge actual performance and stimulate action.
The telecommunications industry has devoted much time over the years to concentrate on developing reliability models for electronic equipment. One such tool is the Automated Reliability Prediction Procedure (ARPP), which is an Excel-spreadsheet software tool that automates the reliability prediction procedures in 'SR-332, Reliability Prediction Procedure for Electronic Equipment'[2] provides suppliers and manufacturers with a tool for making Reliability Prediction Procedure (RPP) calculations. It also provides a means for understanding RPP calculations through the capability of interactive examples provided by the user.
The RPP views electronic systems as hierarchical assemblies. Systems are constructed from units that, in turn, are constructed from devices. The methods presented predict reliability at these three hierarchical levels:
- Device: A basic component (or part)
- Unit: Any assembly of devices. This may include, but is not limited to, circuit packs, modules, plug-in units, racks, power supplies and ancillary equipment. Unless otherwise dictated by maintenance considerations, a unit will usually be the lowest level of replaceable assemblies/devices. The RPP is aimed primarily at reliability prediction of units.
- Serial System: Any assembly of units for which the failure of any single unit will cause a failure of the system or overall mission.
System reliability parameters
Requirements are specified using reliability parameters. The most common reliability parameter is the mean time to failure (MTTF), which can also be specified as the failure rate (this is expressed as a frequency or Conditional Probability Density Function (PDF)) or the number of failures during a given period. These parameters are very useful for systems that are operated frequently, such as most vehicles, machinery, and electronic equipment. Reliability increases as the MTTF increases. The MTTF is usually specified in hours, but can also be used with other units of measurement, such as miles or cycles.
In other cases, reliability is specified as the probability of mission success. For example, reliability of a scheduled aircraft flight can be specified as a dimensionless probability or a percentage, as in system safety engineering.
A special case of mission success is the single-shot device or system. These are devices or systems that remain relatively dormant and only operate once. Examples include automobile airbags, thermal batteries and missiles. Single-shot reliability is specified as a probability of one-time success, or is subsumed into a related parameter. Single-shot missile reliability may be specified as a requirement for the probability of a hit. For such systems, the probability of failure on demand (PFD) is the reliability measure – which actually is a unavailability number. This PFD is derived from failure rate (a frequency of occurrence) and mission time for non-repairable systems.
For repairable systems, it is obtained from failure rate and mean-time-to-repair (MTTR) and test interval. This measure may not be unique for a given system as this measure depends on the kind of demand. In addition to system level requirements, reliability requirements may be specified for critical subsystems. In most cases, reliability parameters are specified with appropriate statistical confidence intervals.
Reliability modelling
Reliability modelling is the process of predicting or understanding the reliability of a component or system prior to its implementation. Two types of analysis that are often used to model a system reliability behavior are Fault Tree Analysis and Reliability Block diagrams. On component level the same analysis can be used together with others. The input for the models can come from many sources: Testing, Earlier operational experience field data or Data Handbooks from the same or mixed industries can be used. In all cases, the data must be used with great caution as predictions are only valid in case the same product in the same context is used. Often predictions are only made to compare alternatives.
For part level predictions, two separate fields of investigation are common:
- The physics of failure approach uses an understanding of physical failure mechanisms involved, such as mechanical crack propagation or chemical corrosion degradation or failure;
- The parts stress modelling approach is an empirical method for prediction based on counting the number and type of components of the system, and the stress they undergo during operation.
Software reliability is a more challenging area that must be considered when it is a considerable component to system functionality.
For systems with a clearly defined failure time (which is sometimes not given for systems with a drifting parameter), the empirical distribution function of these failure times can be determined. This is done in general in an experiment with increased (or accelerated) stress. These experiments can be divided into two main categories:
- Early failure rate studies determine the distribution with a decreasing failure rate over the first part of the bathtub curve. (The bathtub curve only holds for hardware failures, not software.) Here in general only moderate stress is necessary. The stress is applied for a limited period of time in what is called a censored test. Therefore, only the part of the distribution with early failures can be determined.
- In so-called zero defect experiments, only limited information about the failure distribution is acquired. Here the stress, stress time or the sample size is so low that not a single failure occurs. Due to the insufficient sample size, only an upper limit of the early failure rate can be determined. At any rate, it looks good for the customer if there are no failures.
In a study of the intrinsic failure distribution, which is often a material property, higher (material) stresses are necessary to get failure in a reasonable period of time. Several degrees of stress have to be applied to determine an acceleration model. The empirical failure distribution is often parametrized with a Weibull or a log-normal model.
It is a general praxis to model the early (hardware) failure rate with an exponential distribution. This less complex model for the failure distribution has only one parameter: the constant failure rate. In such cases, the Chi-squared distribution can be used to find the goodness of fit for the estimated failure rate. Compared to a model with a decreasing failure rate, this is quite pessimistic (important remark: this is not the case if less hours / load cycles are tested than service life in a wear-out type of test, in this case the opposite is true and assuming a more constant failure rate than there is in reality can be dangerous). Sensitivity analysis should be conducted in this case.
Reliability test requirements
Reliability test requirements can follow from any analysis for which the first estimate of failure probability, failure mode or effect needs to be justified. Evidence can be generated with some level of confidence by testing. With software-based systems, the probability is a mix of software and hardware-based failures. Testing reliability requirements is problematic for several reasons. A single test is in most cases insufficient to generate enough statistical data. Multiple tests or long-duration tests are usually very expensive. Some tests are simply impractical, and environmental conditions can be hard to predict over a systems life-cycle.
Reliability engineering is used to design a realistic and affordable test program that provides empirical evidence that the system meets its reliability requirements. Statistical confidence levels are used to address some of these concerns. A certain parameter is expressed along with a corresponding confidence level: for example, an MTBF of 1000 hours at 90% confidence level. From this specification, the reliability engineer can, for example, design a test with explicit criteria for the number of hours and number of failures until the requirement is met or failed. Other type tests are also possible, including at 95% and 99%.
The combination of reliability parameter value and confidence level greatly affects the development cost and the risk to both the customer and producer. Care is needed to select the best combination of requirements – e.g. cost-effectiveness. Reliability testing may be performed at various levels, such as component, subsystem and system. Also, many factors must be addressed during testing and operation, such as extreme temperature and humidity, shock, vibration, or other environmental factors (like loss of signal, cooling or power; or other catastrophes such as fire, floods, excessive heat, physical or security violations or other myriad forms of damage or degradation).
Reliability engineering must assess the root cause of failures and devise corrective actions. Reliability engineering determines an effective test strategy so that all parts are exercised in relevant environments in order to assure the best possible reliability under understood conditions. For systems that must last many years, reliability engineering may be used to design accelerated life tests.
Requirements for reliability tasks
Reliability engineering must also address requirements for various reliability tasks and documentation during system development, test, production, and operation. These requirements are generally specified in the contract statement of work and depend on how much leeway the customer wishes to provide to the contractor. Reliability tasks include various analyses, planning, and failure reporting. Task selection depends on the criticality of the system as well as cost. A critical system may require a formal failure reporting and review process throughout development, whereas a non-critical system may rely on final test reports. The most common reliability program tasks are documented in reliability program standards, such as MIL-STD-785 and IEEE 1332. Failure reporting analysis and corrective action systems are a common approach for product/process reliability monitoring.
Design for reliability
Design For Reliability (DFR), is an emerging discipline that refers to the process of designing reliability into designs. This process encompasses several tools and practices and describes the order of their deployment that an organization needs to have in place to drive reliability and improve maintainability in products, towards a objective of improved availability, lower sustainment costs, and maximum product utilization or lifetime. Typically, the first step in the DFR process is to establish the system’s availability requirements. Reliability must be 'designed in' to the system. During system design, the top-level reliability requirements are then allocated to subsystems by design engineers, maintainers, and reliability engineers working together.
Reliability design begins with the development of a (system) model. Reliability models use block diagrams and fault trees to provide a graphical means of evaluating the relationships between different parts of the system. These models may incorporate predictions based on failure rates taken from historical data. While the (input data) predictions are often not accurate in an absolute sense, they are valuable to assess relative differences in design alternatives.
One of the most important design techniques is redundancy. This means that if one part of the system fails, there is an alternate success path, such as a backup system. The reason why this is the ultimate design choice is related to the fact that to provide absolute high confidence reliability evidence for new parts / items is often not possible or extremely expensive. By creating redundancy, together with a high level of failure monitoring and the avoidance of common cause failures, even a system with relative bad single channel (part) reliability, can be made highly reliable (mission reliability) on system level. No testing of reliability has to be required for this. Furthermore, by using redundancy and the use of dissimilar design and manufacturing processes (different suppliers) for the single independent channels, less sensitivity for quality issues (early childhood failures) is created and very high levels of reliability can be achieved at all moments of the development cycles (early life times and long term).
An automobile brake light might use two light bulbs. If one bulb fails, the brake light still operates using the other bulb. Redundancy significantly increases system reliability, and is often the only viable means of doing so. However, building redundancy on higher (complex) system level may be very difficult and expensive, and is therefore limited to critical parts of the system (e.g. multi engine aircraft). On lower levels, redundancy is often rather simple and straight forward (e.g. use of redundant bolt connections).
Another design technique, physics of failure, relies on understanding the physical processes of stress, strength and failure at a very detailed level. Then the material or component can be re-designed to reduce the probability of failure. Another common design technique is component derating: Selecting components whose tolerance significantly exceeds the expected stress, as using a heavier gauge wire that exceeds the normal specification for the expected electrical current. Another effective way to deal with unreliability issues is to perform analysis to be able to predict degradation and being able to prevent unscheduled down events / failures from occurring. RCM (Reliability Centered Maintenance) programs can be used for this.
Many tasks, techniques and analyses are specific to particular industries and applications. Commonly these include:
- Built-in test (BIT) (Testability analysis)
- Failure mode and effects analysis (FMEA)
- Reliability simulation modeling
- Reliability Hazard analysis
- Reliability Block Diagram analysis
- Sneak circuit analysis
- Accelerated Testing
- Reliability Growth analysis
- Weibull analysis
- Thermal analysis by Finite Element Analysis (FEA) and / or Measurement
- Thermal induced, shock and vibration fatigue analysis by FEA and / or Measurement
- Electromagnetic analysis
- Avoid Single Point of Failure
- Functional Analysis (like Function FMEA)
- Predictive and preventive maintenance: Reliability Centered Maintenance (RCM) analysis
- Testability analysis
- Failure diagnostics analysis (normally also incorporated in FMEA)
- Human error analysis
- Operational Hazard analysis /
- Manual screening
Results are presented during the system design reviews and logistics reviews. Reliability is just one requirement among many system requirements. Engineering trade studies are used to determine the optimum balance between reliability and other requirements and constraints.
Reliability testing
The purpose of reliability testing is to discover potential problems with the design as early as possible and, ultimately, provide confidence that the system meets its reliability requirements.
Reliability testing may be performed at several levels. Complex systems may be tested at component, circuit board, unit, assembly, subsystem and system levels. (The test level nomenclature varies among applications.) For example, performing environmental stress screening tests at lower levels, such as piece parts or small assemblies, catches problems before they cause failures at higher levels. Testing proceeds during each level of integration through full-up system testing, developmental testing, and operational testing, thereby reducing program risk. System reliability is calculated at each test level. Reliability growth techniques and failure reporting, analysis and corrective active systems (FRACAS) are often employed to improve reliability as testing progresses. The drawbacks to such extensive testing are time and expense. Customers may choose to accept more risk by eliminating some or all lower levels of testing.
Another type of tests are called Sequential Probability Ratio type of tests. These tests use both a statistical type 1 and type 2 error, combined with a discrimination ratio as main input (together with the R requirement). This test (see for examples mil. std. 781) sets – independently – before the start of the test both the risk of incorrectly accepting a bad design (type 2 error) and the risk of incorrectly rejecting a good design (type 1 error) together with the discrimination ratio and the required minimum reliability parameter. The test is therefore more controllable and provides more information from a quality and business point of view. The number of test samples is not fixed, but it is said[citation needed] that this test is in general more efficient (requires less samples) and provides more information than for example zero failure testing.
It is not always feasible to test all system requirements. Some systems are prohibitively expensive to test; some failure modes may take years to observe; some complex interactions result in a huge number of possible test cases; and some tests require the use of limited test ranges or other resources. In such cases, different approaches to testing can be used, such as accelerated life testing, design of experiments, and simulations.
The desired level of statistical confidence also plays an important role in reliability testing. Statistical confidence is increased by increasing either the test time or the number of items tested. Reliability test plans are designed to achieve the specified reliability at the specified confidence level with the minimum number of test units and test time. Different test plans result in different levels of risk to the producer and consumer. The desired reliability, statistical confidence, and risk levels for each side influence the ultimate test plan. Good test requirements ensure that the customer and developer agree in advance on how reliability requirements will be tested.
A key aspect of reliability testing is to define 'failure'. Although this may seem obvious, there are many situations where it is not clear whether a failure is really the fault of the system. Variations in test conditions, operator differences, weather and unexpected situations create differences between the customer and the system developer. One strategy to address this issue is to use a scoring conference process. A scoring conference includes representatives from the customer, the developer, the test organization, the reliability organization, and sometimes independent observers. The scoring conference process is defined in the statement of work. Each test case is considered by the group and 'scored' as a success or failure. This scoring is the official result used by the reliability engineer.
As part of the requirements phase, the reliability engineer develops a test strategy with the customer. The test strategy makes trade-offs between the needs of the reliability organization, which wants as much data as possible, and constraints such as cost, schedule and available resources. Test plans and procedures are developed for each reliability test, and results are documented in official reports.
Accelerated testing
The purpose of accelerated life testing is to induce field failure in the laboratory at a much faster rate by providing a harsher, but nonetheless representative, environment. In such a test, the product is expected to fail in the lab just as it would have failed in the field—but in much less time. The main objective of an accelerated test is either of the following:
- To discover failure modes
- To predict the normal field life from the high stress lab life
An Accelerated testing program can be broken down into the following steps:
- Define objective and scope of the test
- Collect required information about the product
- Identify the stress(es)
- Determine level of stress(es)
- Conduct the accelerated test and analyze the collected data.
Common way to determine a life stress relationship are
- Arrhenius Model
- Eyring Model
- Inverse Power Law Model
- Temperature-Humidity Model
- Temperature Non-thermal Model
Software reliability
![Telcordia sr 332 handbook for employers 2017 Telcordia sr 332 handbook for employers 2017](/uploads/1/2/4/7/124782683/252176994.gif)
Software reliability is a special aspect of reliability engineering. System reliability, by definition, includes all parts of the system, including hardware, software, supporting infrastructure (including critical external interfaces), operators and procedures. Traditionally, reliability engineering focuses on critical hardware parts of the system. Since the widespread use of digital integrated circuit technology, software has become an increasingly critical part of most electronics and, hence, nearly all present day systems.
There are significant differences, however, in how software and hardware behave. Most hardware unreliability is the result of a component or material failure that results in the system not performing its intended function. Repairing or replacing the hardware component restores the system to its original operating state. However, software does not fail in the same sense that hardware fails. Instead, software unreliability is the result of unanticipated results of software operations. Even relatively small software programs can have astronomically large combinations of inputs and states that are infeasible to exhaustively test. Restoring software to its original state only works until the same combination of inputs and states results in the same unintended result. Software reliability engineering must take this into account.
Despite this difference in the source of failure between software and hardware — software does not wear out — some in the software reliability engineering community believe statistical models used in hardware reliability are nevertheless useful as a measure of software reliability, describing what we experience with software: the longer software is run, the higher the probability that it will eventually be used in an untested manner and exhibit a latent defect that results in a failure (Shooman 1987), (Musa 2005), (Denney 2005). (Of course, that assumes software is a constant, which it seldom is.)
As with hardware, software reliability depends on good requirements, design and implementation. Software reliability engineering relies heavily on a disciplined software engineering process to anticipate and design against unintended consequences. There is more overlap between software quality engineering and software reliability engineering than between hardware quality and reliability. A good software development plan is a key aspect of the software reliability program. The software development plan describes the design and coding standards, peer reviews, unit tests, configuration management, software metrics and software models to be used during software development.
A common reliability metric is the number of software faults, usually expressed as faults per thousand lines of code. This metric, along with software execution time, is key to most software reliability models and estimates. The theory is that the software reliability increases as the number of faults (or fault density) goes down. Establishing a direct connection between fault density and mean-time-between-failure is difficult, however, because of the way software faults are distributed in the code, their severity, and the probability of the combination of inputs necessary to encounter the fault. Nevertheless, fault density serves as a useful indicator for the reliability engineer. Other software metrics, such as complexity, are also used. This metric remains controversial, since changes in software development and verification practices can have dramatic impact on overall defect rates.
Testing is even more important for software than hardware. Even the best software development process results in some software faults that are nearly undetectable until tested. As with hardware, software is tested at several levels, starting with individual units, through integration and full-up system testing. Unlike hardware, it is inadvisable to skip levels of software testing. During all phases of testing, software faults are discovered, corrected, and re-tested. Reliability estimates are updated based on the fault density and other metrics. At a system level, mean-time-between-failure data can be collected and used to estimate reliability. Unlike hardware, performing exactly the same test on exactly the same software configuration does not provide increased statistical confidence. Instead, software reliability uses different metrics, such as code coverage.
Eventually, the software is integrated with the hardware in the top-level system, and software reliability is subsumed by system reliability. The Software Engineering Institute's Capability Maturity Model is a common means of assessing the overall software development process for reliability and quality purposes.
Reliability engineering vs safety engineering
Reliability engineering differs from safety engineering with respect to the kind of hazards that are considered. Reliability engineering is in the end only concerned with cost. It relates to all Reliability hazards that could transform into incidents with a particular level of loss of revenue for the company or the customer. These can be cost due to loss of production due to system unavailability, unexpected high or low demands for spares, repair costs, man hours, (multiple) re-designs, interruptions on normal production (e.g. due to high repair times or due to unexpected demands for non-stocked spares) and many other indirect costs.
Safety engineering, on the other hand, is more specific and regulated. It relates to only very specific and system Safety Hazards that could potentially lead to severe accidents. The related functional reliability requirements are sometimes extremely high. It deals with unwanted dangerous events (for life and environment) in the same sense as reliability engineering, but does normally not directly look at cost and is not concerned with repair actions after failure / accidents (on system level). Another difference is the level of impact of failures on society and the control of governments. Safety engineering is often strictly controlled by governments (e.g. Nuclear, Aerospace, Defense, Rail and Oil industries).
Furthermore, safety engineering and reliability engineering may even have contradicting requirements. This relates to system level architecture choices[citation needed]. For example, in train signal control systems it is common practice to use a fail-safe system design concept. In this concept the so called 'wrong side failures' need to be fully controlled to a extreme low failure rate. These failures are related to possible severe effects, like frontal collisions (2* GREEN lights). Systems are designed in a way that the far majority of failures will simply result in a temporary or total loss of signals or open contacts of relays and generate RED lights for all trains. This is the safe state. All trains are stopped immediately. This fail-safe logic might unfortunately lower the reliability of the system. The reason for this is the higher risk of false tripping as any full or temporary, intermittent failure is quickly latched in a shut-down (safe)state. Different solutions are available for this issue. See chapter Fault Tolerance below.
Fault Tolerance
Reliability can be increased here by using a 2oo2 (2 out of 2) redundancy on part or system level, but this does in turn lower the safety levels (more possibilities for Wrong Side and undetected dangerous Failures). Fault tolerant voting systems (e.g. 2oo3 voting logic) can increase both reliability and safety on a system level. In this case the so called 'operational' or 'mission' reliability as well as the safety of a system can be increased. This is also common practice in Aerospace systems that need continued availability and do not have a fail safe mode (e.g. flight computers and related electrical and / or mechanical and / or hydraulic steering functions need always to be working. There are no safe fixed positions for rudder or other steering parts when the aircraft is flying).
Basic Reliability and Mission (Operational) Reliability
The above example of a 2oo3 fault tolerant system increases both mission reliability as well as safety. However, the 'basic' reliability of the system will in this case still be lower than a non redundant (1oo1) or 2oo2 system! Basic reliability refers to all failures, including those that might not result in system failure, but do result in maintenance repair actions, logistic cost, use of spares, etc. For example, the replacement or repair of 1 channel in a 2oo3 voting system that is still operating with one failed channel (which in this state actually has become a 1oo2 system) is contributing to basic unreliability but not mission unreliability. Also, for example, the failure of the taillight of a aircraft is not considered as a mission loss failure, but does contribute to the basic unreliability.
Detectability and Common Cause Failures
When using fault tolerant (redundant architectures) systems or systems that are equipped with protection functions, detectability of failures and avoidance of common cause failures become paramount for safe functioning and/or mission reliability.
Reliability operational assessment
After a system is produced, reliability engineering monitors, assesses and corrects deficiencies. Monitoring includes electronic and visual surveillance of critical parameters identified during the fault tree analysis design stage. The data are constantly analyzed using statistical techniques, such as Weibull analysis and linear regression, to ensure the system reliability meets requirements. Reliability data and estimates are also key inputs for system logistics. Data collection is highly dependent on the nature of the system. Most large organizations have quality control groups that collect failure data on vehicles, equipment and machinery. Consumer product failures are often tracked by the number of returns. For systems in dormant storage or on standby, it is necessary to establish a formal surveillance program to inspect and test random samples. Any changes to the system, such as field upgrades or recall repairs, require additional reliability testing to ensure the reliability of the modification. Since it is not possible to anticipate all the failure modes of a given system, especially ones with a human element, failures will occur. The reliability program also includes a systematic root cause analysis that identifies the causal relationships involved in the failure such that effective corrective actions may be implemented. When possible, system failures and corrective actions are reported to the reliability engineering organization.
One of the most common methods to apply to a reliability operational assessment are Failure Reporting, Analysis and Corrective Action Systems (FRACAS). This systematic approach develops a reliability, safety and logistics assessment based on Failure / Incident reporting, management, analysis and corrective/preventive actions. Organizations today are adopting this method and utilize commercial systems such as a Web based FRACAS application enabling an organization to create a failure/incident data repository from which statistics can be derived to view accurate and genuine reliability, safety and quality performances.
It is extremely important to have one common source FRACAS system for all end items. Also, test results should be able to be captured here in a practical way. Failure to adopt one easy to handle (easy data entry for field engineers and repair shop engineers)and maintain integrated system is likely to result in a FRACAS program failure.
Some of the common outputs from a FRACAS system includes: Field MTBF, MTTR, Spares Consumption, Reliability Growth, Failure/Incidents distribution by type, location, part no., serial no, symptom etc.
The use of past data to predict the reliability of new comparable systems/items can be misleading as reliability is a function of the context of use and can be affected by small changes in the designs/manufacturing.
Reliability organizations
Systems of any significant complexity are developed by organizations of people, such as a commercial company or a government agency. The reliability engineering organization must be consistent with the company's organizational structure. For small, non-critical systems, reliability engineering may be informal. As complexity grows, the need arises for a formal reliability function. Because reliability is important to the customer, the customer may even specify certain aspects of the reliability organization.
There are several common types of reliability organizations. The project manager or chief engineer may employ one or more reliability engineers directly. In larger organizations, there is usually a product assurance or specialty engineering organization, which may include reliability, maintainability, quality, safety, human factors, logistics, etc. In such case, the reliability engineer reports to the product assurance manager or specialty engineering manager.
In some cases, a company may wish to establish an independent reliability organization. This is desirable to ensure that the system reliability, which is often expensive and time consuming, is not unduly slighted due to budget and schedule pressures. In such cases, the reliability engineer works for the project day-to-day, but is actually employed and paid by a separate organization within the company.
Because reliability engineering is critical to early system design, it has become common for reliability engineers, however the organization is structured, to work as part of an integrated product team.
Certification
The American Society for Quality has a program to become a Certified Reliability Engineer, CRE. Certification is based on education, experience, and a certification test: periodic re-certification is required. The body of knowledge for the test includes: reliability management, design evaluation, product safety, statistical tools, design and development, modeling, reliability testing, collecting and using data, etc.
Another highly respected certification program is the CRP (Certified Reliability Professional). To achieve certification, candidates must complete a series of courses focused on important Reliability Engineering topics, successfully apply the learned body of knowledge in the workplace and publicly present this expertise in an industry conference or journal.
Reliability engineering education
Some universities offer graduate degrees in reliability engineering. Other reliability engineers typically have an engineering degree, which can be in any field of engineering, from an accrediteduniversity or college program. Many engineering programs offer reliability courses, and some universities have entire reliability engineering programs. A reliability engineer may be registered as a Professional Engineer by the state, but this is not required by most employers. There are many professional conferences and industry training programs available for reliability engineers. Several professional organizations exist for reliability engineers, including the IEEE Reliability Society, the American Society for Quality (ASQ), and the Society of Reliability Engineers (SRE).
See also
Engineering portal |
- Single point of failure (SPOF)
References
- ^Institute of Electrical and Electronics Engineers (1990) IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY ISBN 1-55937-079-3
- ^SR-332, Reliability Prediction Procedure for Electronic Equipment., FD-ARPP-01 telecom-info.telcordia.com
Further reading
- Blanchard, Benjamin S. (1992), Logistics Engineering and Management (Fourth Ed.), Prentice-Hall, Inc., Englewood Cliffs, New Jersey.
- Breitler, Alan L. and Sloan, C. (2005), Proceedings of the American Institute of Aeronautics and Astronautics (AIAA) Air Force T&E Days Conference, Nashville, TN, December, 2005: System Reliability Prediction: towards a General Approach Using a Neural Network.
- Ebeling, Charles E., (1997), An Introduction to Reliability and Maintainability Engineering, McGraw-Hill Companies, Inc., Boston.
- Denney, Richard (2005) Succeeding with Use Cases: Working Smart to Deliver Quality. Addison-Wesley Professional Publishing. ISBN . Discusses the use of software reliability engineering in use case driven software development.
- Gano, Dean L. (2007), 'Apollo Root Cause Analysis' (Third Edition), Apollonian Publications, LLC., Richland, Washington
- Holmes, Oliver Wendell, Sr. The Deacon's Masterpiece
- Kapur, K.C., and Lamberson, L.R., (1977), Reliability in Engineering Design, John Wiley & Sons, New York.
- Kececioglu, Dimitri, (1991) 'Reliability Engineering Handbook', Prentice-Hall, Englewood Cliffs, New Jersey
- Trevor Kletz (1998) Process Plants: A Handbook for Inherently Safer Design CRC ISBN 1-56032-619-0
- Leemis, Lawrence, (1995) Reliability: Probabilistic Models and Statistical Methods, 1995, Prentice-Hall. ISBN 0-13-720517-1
- Frank Lees (2005). Loss Prevention in the Process Industries (3rdEdition ed.). Elsevier. ISBN978-0-7506-7555-0.
- MacDiarmid, Preston; Morris, Seymour; et al., (1995), Reliability Toolkit: Commercial Practices Edition, Reliability Analysis Center and Rome Laboratory, Rome, New York.
- Modarres, Mohammad; Kaminskiy, Mark; Krivtsov, Vasiliy (1999), 'Reliability Engineering and Risk Analysis: A Practical Guide, CRC Press, ISBN 0-8247-2000-8.
- Musa, John (2005) Software Reliability Engineering: More Reliable Software Faster and Cheaper, 2nd. Edition, AuthorHouse. ISBN
- Neubeck, Ken (2004) 'Practical Reliability Analysis', Prentice Hall, New Jersey
- Neufelder, Ann Marie, (1993), Ensuring Software Reliability, Marcel Dekker, Inc., New York.
- O'Connor, Patrick D. T. (2002), Practical Reliability Engineering (Fourth Ed.), John Wiley & Sons, New York.
- Shooman, Martin, (1987), Software Engineering: Design, Reliability, and Management, McGraw-Hill, New York.
- Tobias, Trindade, (1995), Applied Reliability, Chapman & Hall/CRC, ISBN 0-442-00469-9
- Nelson, Wayne B., (2004), Accelerated Testing – Statistical Models, Test Plans, and Data Analysis, John Wiley & Sons, New York, ISBN 0-471-69736-2
- Bagdonavicius, V., Nikulin, M., (2002), 'Accelerated Life Models. Modeling and Statistical analysis', CHAPMAN&HALL/CRC, Boca Raton, ISBN 1-58488-186-0
US standards, specifications, and handbooks
- Aerospace Report Number: TOR-2007(8583)-6889Reliability Program Requirements for Space Systems, The Aerospace Corporation (10 Jul 2007)
- DoD 3235.1-H (3rd Ed)Test and Evaluation of System Reliability, Availability, and Maintainability (A Primer), U.S. Department of Defense (March 1982) .
- NASA GSFC 431-REF-000370Flight Assurance Procedure: Performing a Failure Mode and Effects Analysis, National Aeronautics and Space AdministrationGoddard Space Flight Center (10 Aug 1996).
- IEEE 1332–1998IEEE Standard Reliability Program for the Development and Production of Electronic Systems and Equipment, Institute of Electrical and Electronics Engineers (1998).
- JPL D-5703Reliability Analysis Handbook, National Aeronautics and Space AdministrationJet Propulsion Laboratory (July 1990).
- MIL-STD-785BReliability Program for Systems and Equipment Development and Production, U.S. Department of Defense (15 Sep 1980). (*Obsolete, superseded by ANSI/GEIA-STD-0009-2008 titled Reliability Program Standard for Systems Design, Development, and Manufacturing, 13 Nov 2008)
- MIL-HDBK-217FReliability Prediction of Electronic Equipment, U.S. Department of Defense (2 Dec 1991).
- MIL-HDBK-217F (Notice 1)Reliability Prediction of Electronic Equipment, U.S. Department of Defense (10 Jul 1992).
- MIL-HDBK-217F (Notice 2)Reliability Prediction of Electronic Equipment, U.S. Department of Defense (28 Feb 1995).
- MIL-STD-690DFailure Rate Sampling Plans and Procedures, U.S. Department of Defense (10 Jun 2005).
- MIL-HDBK-338BElectronic Reliability Design Handbook, U.S. Department of Defense (1 Oct 1998).
- MIL-HDBK-2173Reliability-Centered Maintenance (RCM) Requirements for Naval Aircraft, Weapon Systems, and Support Equipment, U.S. Department of Defense (30 JAN 1998); (superseded by NAVAIR 00-25-403).
- MIL-STD-1543BReliability Program Requirements for Space and Launch Vehicles, U.S. Department of Defense (25 Oct 1988).
- MIL-STD-1629AProcedures for Performing a Failure Mode Effects and Criticality Analysis, U.S. Department of Defense (24 Nov 1980).
- MIL-HDBK-781AReliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production, U.S. Department of Defense (1 Apr 1996).
- NSWC-06 (Part A & B)Handbook of Reliability Prediction Procedures for Mechanical Equipment, Naval Surface Warfare Center (10 Jan 2006).
UK standards
Telcordia Sr 332 Handbook For Employers (m-274)
In the UK, there are more up to date standards maintained under the sponsorship of UK MOD as Defence Standards. The relevant Standards include:
DEF STAN 00-40 Reliability and Maintainability (R&M)
- PART 1: Issue 5: Management Responsibilities and Requirements for Programmes and Plans
- PART 4: (ARMP-4)Issue 2: Guidance for Writing NATO R&M Requirements Documents
- PART 6: Issue 1: IN-SERVICE R & M
- PART 7 (ARMP-7) Issue 1: NATO R&M Terminology Applicable to ARMP’s
DEF STAN 00-42 RELIABILITY AND MAINTAINABILITY ASSURANCE GUIDES
- PART 1: Issue 1: ONE-SHOT DEVICES/SYSTEMS
- PART 2: Issue 1: SOFTWARE
- PART 3: Issue 2: R&M CASE
- PART 4: Issue 1: Testability
- PART 5: Issue 1: IN-SERVICE RELIABILITY DEMONSTRATIONS
DEF STAN 00-43 RELIABILITY AND MAINTAINABILITY ASSURANCE ACTIVITY
- PART 2: Issue 1: IN-SERVICE MAINTAINABILITY DEMONSTRATIONS
DEF STAN 00-44 RELIABILITY AND MAINTAINABILITY DATA COLLECTION AND CLASSIFICATION
- PART 1: Issue 2: MAINTENANCE DATA & DEFECT REPORTING IN THE ROYAL NAVY, THE ARMY AND THE ROYAL AIR FORCE
- PART 2: Issue 1: DATA CLASSIFICATION AND INCIDENT SENTENCING – GENERAL
- PART 3: Issue 1: INCIDENT SENTENCING – SEA
- PART 4: Issue 1: INCIDENT SENTENCING – LAND
DEF STAN 00-45 Issue 1: RELIABILITY CENTERED MAINTENANCE
DEF STAN 00-49 Issue 1: RELIABILITY AND MAINTAINABILITY MOD GUIDE TO TERMINOLOGY DEFINITIONS
These can be obtained from DSTAN. There are also many commercial standards, produced by many organisations including the SAE, MSG, ARP, and IEE.
French standards
- FIDES [1]. The FIDES methodology (UTE-C 80-811) is based on the physics of failures and supported by the analysis of test data, field returns and existing modelling.
- UTE-C 80–810 or RDF2000 [2]. The RDF2000 methodology is based on the French telecom experience.
International standards
External links
- NIST/SEMATECH, 'Engineering Statistics Handbook', [3]
|
|
|
Retrieved from 'http://en.wikipedia.org/w/index.php?title=Reliability_engineering&oldid=503314406'
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)