Lab Safety and Physical Risk Engineering — Operating Quantum Computers

Quantum computing software often hides the physical risk profile of the machine. A cloud API may sit on top of cryogens, vacuum systems, lasers, high-frequency electronics, high currents, magnetic fields, compressed gases, and mechanical lifting. A mature quantum operation treats physical safety as part of system reliability.

OSHA materials identify hazards associated with cryogens and dry ice, including skin and eye injury, pressure buildup, oxygen displacement, and the need for appropriate handling precautions. OSHA also highlights laser hazards to eyes and skin, with higher-class lasers requiring significant controls [R137]. These are not peripheral concerns for quantum facilities. They shape access, maintenance, incident response, and commissioning.

77.1 Safety envelope

Diagram loads as you read

77.1 Safety envelope · Figure 1

View diagram source

flowchart TB
    Safety[Quantum facility safety envelope] --> Cryogens[Cryogens]
    Safety --> Lasers[Lasers]
    Safety --> Vacuum[Vacuum systems]
    Safety --> Electrical[Electrical and RF power]
    Safety --> Magnetic[Magnetic fields]
    Safety --> Mechanical[Mechanical lifts]
    Safety --> Chemical[Cleaning and fabrication chemicals]
    Safety --> Software[Software interlocks]

The safety envelope is the set of conditions under which a system may be operated, serviced, or modified. It is as important as the computational envelope.

77.2 Hazard registry

Diagram loads as you read

77.2 Hazard registry · Figure 2

View diagram source

flowchart LR
    Hazard[Hazard] --> Inventory[Inventory]
    Inventory --> Control[Control]
    Control --> Inspection[Inspection]
    Inspection --> Training[Training]
    Training --> Evidence[Evidence record]
    Evidence --> Review[Periodic review]

A hazard registry should include source, affected rooms and equipment, PPE, training, interlocks, emergency shutdown path, inspection cadence, owner, and last review date.

77.3 Cryogenic workflow

Diagram loads as you read

77.3 Cryogenic workflow · Figure 3

View diagram source

sequenceDiagram
    participant Tech as Technician
    participant Permit as Work permit
    participant Room as Lab room
    participant Dewar as Cryogen container
    participant Monitor as O2 monitor
    participant Log as Safety log
    Tech->>Permit: request cryogen operation
    Permit->>Room: verify ventilation and access
    Room->>Monitor: verify oxygen monitoring
    Tech->>Dewar: transfer or connect
    Monitor-->>Tech: alarm if oxygen unsafe
    Tech->>Log: record completion and anomalies

Cryogen risk is often a volume and ventilation problem. The danger can be invisible until an oxygen monitor, alarm, or procedural control catches it.

77.4 Laser workflow

Diagram loads as you read

77.4 Laser workflow · Figure 4

View diagram source

flowchart TB
    LaserUse[Laser operation] --> Classification[Class and wavelength]
    Classification --> Access[Controlled area]
    Classification --> Eyewear[Correct eyewear]
    Access --> Interlocks[Interlocks and signage]
    Eyewear --> Alignment[Alignment procedure]
    Alignment --> Log[Use log]

Laser controls should be specific to class, wavelength, power, beam path, alignment mode, and enclosure state. “Wear goggles” is not a sufficient control.

77.5 Maintenance mode is a different system

Diagram loads as you read

77.5 Maintenance mode is a different system · Figure 5

View diagram source

stateDiagram-v2
    [*] --> NormalOperation
    NormalOperation --> Maintenance: work permit opened
    Maintenance --> Lockout: hazardous energy isolated
    Lockout --> Test: controlled verification
    Test --> NormalOperation: permit closed
    Maintenance --> Emergency: unsafe condition
    Emergency --> NormalOperation: incident closed and reviewed

Maintenance can expose hazards that normal operation contains, including unexpected startup and release of stored energy. Maintenance mode needs task-specific hazard controls, qualified staffing, and a verified return-to-service procedure. [R137]

77.6 Safety interlocks and software

Diagram loads as you read

77.6 Safety interlocks and software · Figure 6

View diagram source

flowchart LR
    Sensor[Sensor or alarm] --> Interlock[Interlock controller]
    Interlock --> Runtime[Runtime admission]
    Interlock --> Facility[Facility action]
    Runtime --> Block[Block or drain jobs]
    Facility --> Shutdown[Safe shutdown]
    Block --> Incident[Incident record]

Software must not bypass physical safety. The runtime can help by refusing jobs when facility state is unsafe, but it should not be the only safety layer.

77.7 Incident response

Diagram loads as you read

77.7 Incident response · Figure 7

View diagram source

flowchart TB
    Alarm[Alarm or unsafe condition] --> Evacuate[Evacuate or isolate]
    Evacuate --> Notify[Notify safety owner]
    Notify --> Stabilize[Stabilize equipment]
    Stabilize --> Preserve[Preserve evidence]
    Preserve --> Review[Incident review]
    Review --> Correct[Corrective action]

Quantum safety incidents should feed both the safety program and the reliability program. A cryogen alarm may reveal a facility issue, a maintenance-procedure issue, or a scheduling issue.

77.8 Operating rule

A quantum platform is not production-ready if it can schedule a job on a device whose physical safety state is unknown.

Diagram loads as you read

77.8 Operating rule · Figure 8

View diagram source

flowchart LR
    FacilityState[Facility state] --> Admission[Runtime admission]
    Admission --> Execute[Execute workload]
    FacilityState --> Maintenance[Maintenance plan]
    Maintenance --> Evidence[Safety evidence]