35.9.1. Case Study 1: Robotic Arm Collision on Precast Site

• Incident: A robotic arm used in precast panel handling struck a worker due to unexpected trajectory movement.

This part describes a specific incident involving a robotic arm at a construction site. The arm, which is designed to handle precast panels, unexpectedly moved into the space where a worker was located, resulting in a collision. Understanding such incidents is crucial because they highlight the potential risks associated with using automated systems in environments where humans are also present.

Imagine a registered nurse working in a hospital while a robotic arm is moving to pick up supplies. If the robotic arm’s path is not monitored and it unexpectedly changes direction, it could strike the nurse, leading to serious injury. This scenario illustrates the importance of ensuring robots have predictable and safe movement patterns, especially when operating near people.

• Root Cause: Incomplete training and override of safety perimeter sensors.

This section explores the root causes of the collision incident. It indicates that there were two main issues: first, the workers received incomplete training on how to operate around the robotic arm safely. Second, the safety perimeter sensors, which are intended to prevent collisions by detecting human presence, were overridden or not functioning correctly. These factors contributed to the mishap, emphasizing the need for thorough training and proper functioning of safety mechanisms.

Consider a school where teachers are supposed to train students on how to safely interact with a robot that assists in the classroom. If the training is rushed or incomplete, students might not know to stay out of the robot's path, increasing the risk of accidents. Additionally, if the safety barriers in place to keep students safe are disabled or malfunctioning, the situation becomes even riskier, leading to possible injuries.

• Liability Outcome: Shared liability between the contractor (training failure) and OEM (inadequate motion prediction software).

This chunk addresses the legal implications following the incident. It states that liability was shared between two parties: the contractor who failed to provide adequate training for the workers and the Original Equipment Manufacturer (OEM) who produced the robotic arm but did not ensure that the software could adequately predict or manage its motion. This shared liability illustrates how multiple stakeholders can be responsible when incidents occur involving automated systems.

Think of a car accident where both the driver (representing the contractor responsible for training) and the car manufacturer (representing the OEM) share blame. If the driver was untrained and didn’t know how to handle a sudden stop, but the car also lacked proper braking systems to prevent accidents in emergencies, both parties bear responsibility for the accident.

• Lessons Learned: - Enforce motion simulation before deployment. - Use wearable proximity tags for workers.

This part highlights two critical lessons derived from the incident. The first lesson emphasizes the importance of motion simulations, which are tests conducted before actual deployment of robotic systems to help anticipate and manage potential issues. The second lesson suggests the implementation of wearable proximity tags that would alert workers when they are too close to operating machinery, further enhancing their safety around such systems.

In a video game, before launching a new level, creators often run simulations to see how players might navigate the environment and identify potential glitches. Similarly, motion simulation of robotic arms can preemptively uncover risks. Wearable proximity tags for workers can be likened to alarms in a car that beep when the driver gets too close to a wall or barrier, thus enhancing safety.

--