Camera view
Use one approved view and operating schedule.
Start with a condition that is visible enough to measure without changing the customer’s camera infrastructure.
How continuous operations become a Safety Control Scan
From continuous monitoring to a completed Safety Control Scan.
Edgentik monitors one defined condition, creates alerts, sends configured notifications and organizes confirmed events as reviewed episodes. The Scan workflow then reveals recurrence, records the site response and checks the same condition again.
Operational foundation
Continuous monitoring generates the events and evidence that feed the Scan workflow.
- 01 Confirm the camera view Can this camera reliably observe the condition?
- 02 Find where it repeats Where and when does it keep happening?
- 03 Record the site response What action did the customer select?
- 04 Check again What was observed when the area was reviewed again?
Clear responsibility at each layer
Each layer has one defined job.
The camera supplies the approved view. Local processing applies the selected condition. The review application organizes detected events into findings, actions and follow-up. Safety decisions remain with the site team.
Local policy processing
Apply the selected condition close to the source.
The on-site edge box processes the configured camera stream and produces only the configured event records and selected clips.
Reviewable evidence
Organize alerts, reviewed episodes, clips and observation coverage.
Named users review the evidence supporting confirmed events and the resulting pattern.
Completed customer output
Deliver the finding, action record and follow-up plan.
The report preserves what was measured, the observation basis and the site’s recorded next decision.
What runs where
Use existing cameras while keeping processing close to the site.
Edgentik manages the infrastructure behind the Safety Control Scan. The diagram shows the path from camera input and on-site processing to reviewable evidence, the completed Scan and the operating response.
Camera and local processing
- Existing camera connection
- Local processing and buffering
- Chosen condition observed
- Detections become alerts; confirmed events become reviewed episodes
Review, evidence and completed Scan
- Camera and measurement review
- Recurring-pattern analysis
- Action record and implementation evidence
- Completed Safety Control Scan
Hazard assessment and control decision
- Hazard and control assessment
- Control selection and approval
- Connection to the customer’s process
- The next-step decision
Before the first camera
Clear answers for Safety, Operations and IT.
Before connection, Edgentik and the customer agree on the camera, condition, users, data path, retention and responsibility boundary.
| Question | What Edgentik provides | What we confirm together |
|---|---|---|
| What runs on site? | Edgentik provides and manages the on-site edge box and software required for the pilot. | Device location, camera scope, connectivity and recovery responsibilities. |
| Which camera is used? | A suitable existing RTSP camera view can be connected. | Feed access, view suitability, lighting, occlusion and operating schedule. |
| What leaves the site? | Only the evidence agreed with the customer is sent to Edgentik for review and reporting. | Exact payload, outbound endpoints, expected volume and retention. |
| Who can review it? | Only approved users for the organization and site can review evidence, actions and completed reports. | Users, roles, hosting region, export rights and pilot-close treatment. |
| Who owns the safety decision? | Edgentik provides the observation result, recurring finding and follow-up evidence. | The employer assesses the hazard, selects the control and decides what happens next. |
Start with one priority condition
Put a recurring operating concern under continuous observation.
Name the area and condition. Edgentik will configure the existing camera view, monitoring rule and evidence workflow for the first Safety Control Scan.