Bring devices into service through readiness, training, and handover

A device should not become operational just because it exists in the registry. Ovahol tracks readiness checks, training completion, handover acknowledgement, and commissioning separately so the go-live decision is explicit and governed.

By the end of this stage: Teams can see whether a device is actually ready for use instead of assuming the asset is safe because it was received.

Modules involved: Device Record Lifecycle, Commissioning, Training Records, Handover Records

What to do

1. Capture readiness evidence

Record site readiness, safety checks, calibration, and any pre-use conditions required by governance. These are visible on the device record before commissioning can close.

2. Document training

Log operator or maintainer training so competency is visible before use begins. Governance rules can require training evidence before commissioning proceeds.

3. Record handover

Capture custody acknowledgement and any documents that must move with the device at the point it changes hands.

4. Commission deliberately

Close commissioning only when the required readiness evidence is in place. The governance model controls what is required and who can approve it.

5. Run training as sessions

Individual records answer "was this person trained on this device". Sessions answer "what training did we run, for whom, and against which objectives" — useful when a batch of devices arrives together. A device's roster shows who attended, and a session can be recorded from either the session list or the device record.