HyperQ AI Safety deploys in 1 hour on existing cameras and generates a timestamped event record for every pedestrian intrusion into the envelope under a suspended load. That 1-hour figure matters not as a marketing claim but as a comparison point: the typical crane-safety upgrade cycle in SG and MY fabrication facilities runs six to eighteen months of committee reviews, DOSH submissions, and contractor scoping — during which the hazard exists from the first shift, not the last approval.
Fixed exclusion zones and warning lamps do not protect the zone that moves with the load. The exclusion zone that works is directly under the hook at every point in the travel cycle. Warning lights assume the pedestrian sees the hook. Cameras do not.
Why "keep the bay clear" is not a system
A lift plan requires a cleared exclusion zone before the first hoist. That clearance addresses a moment in time. A bridge crane on a 30-meter span moves a load across the full bay in 40 to 90 seconds of active transit, at 0.3 to 0.8 m/s travel speed. During that transit, a maintenance technician entering from a side door, a forklift operator crossing the bay, or a contractor following a site manager can enter the load path with a legitimate reason and no knowledge that the lift is in progress.
The crane operator's attention during transit is on the hook position relative to the set-down point, not on the full bay floor. A rotating amber lamp at the bay entry and an intermittent buzzer are the only active warning reaching a person entering from a side corridor. Neither the lamp nor the buzzer tracks where the load is in the travel cycle. Neither stops the crane.
The painted floor boundary and the perimeter lamp are static answers to a moving hazard.
SG WSH / MY DOSH regulatory context
Singapore. The Workplace Safety and Health (Operation of Cranes) Regulations 2011 require the crane operator to take all reasonably practicable steps to ensure no person is in the path of the moving load or hook throughout the lift. MOM's Safe Lifting Operations framework lists crane exclusion zone management as a required element of the lift plan for loads over 1 tonne. In a post-incident investigation, an employer who can produce an AI-generated event log (timestamped, showing the exact zone boundary at the time of each intrusion, camera ID, and frame reference) is in a different evidentiary position than one whose documentation is the operator's verbal account and a paper sign-off from the start of the shift.
MOM's incident data consistently shows struck-by events from crane loads occurring mid-bay, not at the perimeter. The perimeter is where the existing warning systems are installed. Mid-bay is where the load travels.
Malaysia. DOSH Factories and Machinery (Operations of Cranes) Regulations 1978, updated under OSHA 1994 and the 2022 OSHA amendment, require crane operators to ensure the lift area is clear before each hoist cycle and during travel. The 2022 amendment increased the employer's burden to demonstrate active hazard controls. In a contested incident investigation, "we have floor markings and a rotating lamp" no longer satisfies "all reasonably practicable steps" when an AI monitoring system that logs zone intrusions installs in 1 hour and costs less than one day of crane downtime to commission.
Neither regulator mandates AI monitoring by name. Both require documented active controls. The compliance question in 2026 is whether passive visual warnings alone constitute a demonstrable active control when camera-based enforcement is available at this cost and deployment time.
Warning lights assume the pedestrian sees them
A 85-dB fabrication floor renders a crane buzzer inaudible at 15 meters without direct line of sight. A worker with mandated hearing protection cannot hear the tone regardless of proximity. A contractor on their first site visit does not know what a rotating amber lamp indicates in the context of your crane cycle. A line manager escorting a visitor is watching the visitor, not the lamp rotation sequence.
Warning systems whose outcome depends on the pedestrian's attention, knowledge, and reaction time are passive systems. Detection by camera is independent of what the person under the hook hears, sees, or decides to do. The stop command does not wait for the pedestrian to notice the warning. This removes human attention from the detection chain. That is the structural reason camera-based enforcement produces a different safety outcome than any improvement to the warning lamp or buzzer system.
Why crane zones are harder to guard than fixed-machine perimeters
A robot cell or press brake has a predictable, fixed hazard boundary. The machine stays in one place; a presence sensor, light curtain, or safety gate guards a fixed perimeter. That approach works because the perimeter does not move.
A bridge crane's hazard boundary moves in two dimensions during every lift cycle, with a third dimension of swing variability on long chains. Retrofitting a crane bay with floor-level laser curtains across the full travel envelope would require dozens of sensor pairs and would still not track the load's actual position when it swings off-center.
Camera-based load tracking does not need a perimeter sensor network because it monitors the load directly, not the boundary. The exclusion zone follows the hook center, not a fixed floor coordinate. Most fixed-sensor approaches also omit load-swing compensation entirely — the sensor boundary is the nominal hook position, not where the load actually is when the chain swings. That gap is consequential for chains longer than 4m carrying asymmetric loads, which describes a large share of fabrication and materials-handling lifts.
For facilities that have already deployed near-miss detection and video analytics for forklift-pedestrian interaction, the crane overhead-load application extends the same camera infrastructure; the load-tracking function is additive. Incremental commissioning for an existing HyperQ AI Safety installation is a fraction of a standalone deployment.
How HyperQ AI Safety tracks the load envelope
HyperQ AI Safety runs on the camera network already present in most fabrication and warehousing bays. For a standard single-bay bridge crane, 2 to 3 cameras mounted at fixed overhead positions covering the full travel span provide complete zone coverage from floor-level lift height to maximum hoist position. No new camera poles or additional infrastructure are needed in a typical installation.
The system tracks the hook and load center frame by frame. It renders a configurable exclusion zone around that center, with radius set at commissioning based on load dimensions, chain length, and travel speed. When a person enters the slow-zone radius, it activates an alert at the operator station and a floor-level alarm. When a person enters the stop-zone radius, it sends a relay output to the crane PLC that trips both the travel drive and hoist. In commissioning sessions, the most common tuning step in the first 30 days is adjusting the slow-zone radius down from the default starting value once real load dimensions and swing behavior are observed. The defaults are deliberately conservative, which means more false alerts initially, not fewer.
PLC integration uses the crane's existing emergency-stop input. No rewiring of the crane controls is required. Single-bay bridge crane setup — camera configuration, zone radius definition, relay wiring, test trigger — completes in 1 hour.
The $250 smartband provides a secondary personal-alarm path in bays with camera shadow zones: a column-dense warehouse, or a bay with a fixed overhead obstacle that blocks one camera's line of sight to part of the travel path. The band receives zone-proximity coordinates from the same camera system and activates wrist vibration and a local audio alert independently of the overhead alarm. It does not replace the camera-based stop-zone relay; it adds a wearable redundancy layer for workers who regularly cycle through high-risk zones as part of their normal work.
Zone-design checklist
Each item below is a configuration decision that determines alert behavior, PLC integration scope, or compliance documentation completeness. Resolve all 10 before commissioning begins.
| # | Item | Specification required |
|---|---|---|
| 1 | Crane travel path mapping | Full X–Y envelope across all bay positions, including end-of-travel buffer positions |
| 2 | Slow-zone radius | Horizontal distance from hook center; typical starting value: 3m for loads <10t, 4m for ≥10t |
| 3 | Stop-zone radius | Horizontal distance from hook center; typical: 1.5m; adjust for load width and swing history |
| 4 | Camera coverage at all heights | Verify field of view covers load center from floor-level lift (0.5m) to maximum hoist height |
| 5 | Detection-to-alert latency — slow zone | Maximum 300ms from zone entry to operator console alarm and floor speaker activation |
| 6 | Detection-to-relay latency — stop zone | Maximum 200ms from zone entry to relay output at crane PLC |
| 7 | PLC relay scope | Relay must trip both travel drive and hoist — hoist-only trip does not stop lateral load movement |
| 8 | Load-swing buffer | For chain lengths >4m, add a swing-radius buffer proportional to chain length and load weight |
| 9 | Re-entry protocol | Zone must be clear for 5 continuous seconds before manual-release is available at the operator station |
| 10 | Audit log format | Log must include timestamp, zone type triggered, camera ID, and frame reference for WSH/DOSH compliance files |
Slow-zone and stop-zone latency specification
The latency figure is a physics constraint, not a target to optimize later. At typical indoor walking speed (1.4 m/s), a person crosses 1.5m — the standard stop-zone radius — in 1.07 seconds from zone entry. If detection-to-relay-output latency is 200ms, that leaves 0.87 seconds for the crane to achieve a full stop before the person reaches the load's fall radius. Most industrial bridge cranes in normal brake condition stop travel in 0.5 to 0.8 seconds from a hard relay command, depending on load weight and brake wear. At 200ms system latency, the margin is met. At 250ms, it begins to fail for a 0.5 m/s travel-speed crane. At 1 m/s travel speed, 200ms requires review regardless of brake condition, and a pre-deceleration trigger on slow-zone approach rather than stop-zone entry may be required.
| Zone | Trigger condition | Max detection-to-action latency | Action | Integration requirement |
|---|---|---|---|---|
| Slow zone | Person within 3m of hook center (load <10t) or 4m (≥10t) | 300ms | Audio/visual at operator console; floor speaker activates; crane speed limited to 0.5 m/s | Camera feed |
| Stop zone | Person within 1.5m of hook center | 200ms | Hard relay trips travel drive and hoist; full stop | Camera feed + PLC relay output |
| Load-swing buffer | Load displacement >0.5m from nominal hook center | 150ms | Slow-zone protocol activates at extended radius to cover actual swing arc, not nominal hook position | Camera load-tracking; requires live load-center tracking, not a fixed perimeter |
| Re-entry | Zone clear ≥5 continuous seconds | N/A | Manual-release available at operator station | Camera feed + operator confirm |
These values apply to a 15–25t bridge crane at travel speed ≤0.5 m/s in a standard indoor fabrication or materials-handling bay. For cranes running above 1 m/s travel speed, loads above 30t, or span above 25m, a site-specific latency review is required before finalizing the relay specification.
Contractor and shift-change risk
Crane struck-by incidents in Singapore and Malaysia consistently involve three worker categories: maintenance personnel entering an active bay, contractors who are new to the site and unfamiliar with the crane cycle, and workers crossing during shift changeover when the incoming crane operator has taken over but the departing team's cleared-zone awareness has lapsed. Each is a person with a legitimate reason to be in the facility who was not part of the original lift-plan clearance.
Camera-based monitoring does not require those workers to know the crane cycle, interpret floor markings, or hear warning tones. Detection runs continuously during operational hours, not only during the specific lift cycles listed in the day's lift plans.
This matters for multi-employer worksites — a common configuration in Malaysian fabrication and assembly operations where production staff and contractor maintenance teams share bays on overlapping schedules. The system does not distinguish between employees and contractors; it monitors the load envelope for all persons in the frame. For compliance under the OSHA 2022 amendment's multi-employer duty provisions, continuous documented coverage across all persons in the bay is a stronger basis for the employer's duty-of-care file than a contractor-induction record and a signed entry log.
Cross-industry evidence
Hypernology has no publicly cited crane-vertical deployment. The relevant architectural reference is the same camera-based zone-boundary and PLC relay-output system that operates in a Tier-1 automotive-parts deployment, processing 11,520 units per day across 6 production lines at 99% detection accuracy. That deployment monitors fixed conveyor exclusion zones; the crane application extends the zone center from a fixed production-line coordinate to a tracked moving load center. The detection, latency, and relay-output architecture is the same system class. The load-tracking function is additive, not a different product.
That cross-industry basis means first-deployment risk is real for the crane configuration: the fixed-zone deployment has more production hours behind it than the load-tracking application. The appropriate mitigation is the 30-day commissioning review: examining false-positive events weekly to tune the zone radius for actual load dimensions and bay traffic. The installation is not considered production-qualified until that review period is complete.
A broader framework for how zone-intrusion event logs from safety monitoring systems feed into proactive leading-indicator analysis is covered in leading safety indicators and video analytics for manufacturing environments. The full specification for HyperQ AI Safety — hardware, camera compatibility, and PLC integration options for overhead-load and pedestrian-machine applications — is at /solutions/hyperq-ai-safety.
Where camera-based monitoring has limits
The following failure modes should be assessed before committing to a deployment specification:
Camera shadow zones. A wide load (>4m horizontal span) or a tandem two-crane lift can place part of the exclusion zone outside any single camera's coverage. Multi-camera triangulation resolves this but adds commissioning time and camera mounting complexity. Sites with wide-load or tandem-lift configurations must confirm camera placement before specifying the stop-zone radius.
Outdoor and covered-outdoor cranes. Yard gantry applications exposed to rain, direct sun, or heavy dust have variable image quality that reduces detection confidence. HyperQ AI Safety is rated for indoor and covered-outdoor environments. Open-yard crane applications require a site-specific camera and exposure configuration reviewed before deployment.
Very high crane travel speed. For cranes running above 2 m/s, the time-to-stop margin at 200ms relay latency is insufficient for loads above 10t without a pre-deceleration trigger on slow-zone approach rather than stop-zone entry. High-speed applications need engineering sign-off on the relay specification before go-live. This is not a workaround — it is a different trigger logic that requires PLC programming, not only relay wiring.
Practical starting point for SG/MY facilities
A standard indoor bridge crane installation: 2 cameras, 1-hour setup, relay connected to the crane's existing emergency-stop input, 30-day false-positive review to tune zone radii for your specific load dimensions and bay traffic pattern.
Before accepting the installation, confirm the event-log format: timestamp, zone type triggered, camera ID, and frame reference. That format is directly usable in a MOM incident report (SG) or a DOSH investigation file (MY). It eliminates the evidentiary gap between "all reasonably practicable steps were taken" and documentation that actually demonstrates it.
Send a bay layout showing crane span, travel speed, and maximum load capacity to apac.hypernology.net/contact. We return a camera-placement recommendation and a no-contract zone-latency specification within 2 working days — no purchase decision required.