Stay Awake with the OG-66 Radio

Stay Awake is an Onguard guard alertness-monitoring function available on the OG-66 Patrol Radio. At configured times, the guard is prompted to respond, and a missed acknowledgement can generate an alert for operational follow-up.

Onguard also offers Stay Awake as a standalone alertness-monitoring device. Whether it is used as a standalone device or as OG-66 functionality, it provides a structured acknowledgement process rather than proof that a guard remained awake or attentive throughout an entire shift.

What is Onguard Stay Awake?

Stay Awake uses scheduled prompts, guard acknowledgement and missed-response alerts to support guard-monitoring procedures. It can be used where a security operation wants a recorded response to a configured prompt during a shift.

The function addresses alertness monitoring. It is not the same as cellular push-to-talk communication, and it does not replace patrol verification, staffing plans or the operating procedure a site uses for responding to alerts.

How scheduled guard acknowledgements work

Prompts run at configured times and require acknowledgement from the guard. A successful acknowledgement records a response to that prompt. It can support a structured process for checking whether a required response was recorded, but it does not establish every aspect of a guard's activity or performance during the shift.

The relevant prompt schedule and acknowledgement process should fit the work being carried out at the site. Security companies should consider when prompts are appropriate, who reviews a missed response, and how the procedure fits normal patrol and communication duties.

Stay Awake supports remote configuration. The current product information does not establish specific menu names, screen labels or configuration fields, so those should be confirmed with Onguard when setting up a deployment.

What happens when a guard does not respond?

If a Stay Awake prompt times out, a configured notification can be sent to a supervisor or control room. The notification creates an opportunity for operational follow-up; it does not prescribe what the receiving team must do or guarantee a particular response time.

Each security operation should define how it handles missed responses. That may include checking the circumstances, using the available communication method, recording the outcome and deciding whether further action is needed under the site's own procedures.

Stay Awake and one-point patrol operation

Stay Awake can be configured for one-point patrol operation. This provides a specific use case for a guard acknowledgement process, but it should not be confused with a full route-verification workflow.

For patrol verification on the OG-66, named NFC checkpoints can be placed along a configured route. When the radio scans a checkpoint, the patrol event can record the device, checkpoint, date and time. That is a separate type of operational record from an acknowledgement to a Stay Awake prompt.

The distinction is important when planning a site: Stay Awake can support scheduled acknowledgements and missed-response alerts, while NFC patrol points can support records of configured checkpoint scans.

What supervisors can review

Stay Awake supports reporting, remote configuration and one-point patrol operation. Its activity can be included in reporting for operational review. The specific reports and information available depend on the chosen setup and should be confirmed before the operation relies on them for a particular process.

Supervisors should decide what information is useful after a shift, who needs access to it and how a missed acknowledgement will be reviewed. Good guard-monitoring procedures use available records as context for follow-up rather than treating a single acknowledgement as a complete account of a shift.

Stay Awake is one part of guard monitoring

Stay Awake addresses scheduled acknowledgement and alertness-monitoring requirements. It is separate from the OG-66's cellular push-to-talk communication, which depends on supported network connectivity, and separate from NFC patrol verification, which records checkpoint scans on configured routes.

For a broader view of how communication, patrol verification, alertness monitoring, scheduling and reporting can fit together, read the Patrol Management Software South Africa guide. The real-time guard monitoring guide also explains the difference between current operational information, patrol records and response procedures.

When should a security operation consider Stay Awake?

Stay Awake may be relevant where a site wants a scheduled acknowledgement process and a way to surface missed responses for operational follow-up. Before choosing a setup, consider the guard's duties, prompt timing, communication method, patrol-verification requirements, supervisor workflow and the reporting needed after a shift.

Talk to Onguard if you want to understand how Stay Awake and OG-66 can fit into your guard-monitoring procedures.