DHI reads the same approved RTSP streams Security Center reads, runs detection on the site, and emits structured events over webhook. Mapping those events onto your Security Center alarm definitions is integration work we scope with your team. DHI does not ship a Genetec connector.
Integration proof
The integration page should answer what connects, what data moves, what the operator sees, and what has to be validated before pilot launch.
Integration target
DHI reads the same approved RTSP streams Security Center reads, runs detection on the site, and emits structured events over webhook. Mapping those events onto your Security Center alarm definitions is integration work we scope with your team. DHI does not ship a Genetec connector.
Camera workflow
Security Center remains the operator workspace and system of record. DHI performs local inference on approved streams, then sends structured safety events that can be mapped to alarms, bookmarks, and response workflows.
Event routing
DHI reads the approved camera stream on site without changing the recording path.
Deployment check
The pilot should start with a short camera list and clear zone labels that match how operators talk about the site.
Security posture
Raw video stays on the site network while DHI routes safety metadata into the existing operator workflow.
Fit
Security Center remains the operator workspace and system of record. DHI performs local inference on approved streams, then sends structured safety events that can be mapped to alarms, bookmarks, and response workflows.
DHI needs approved access to the camera streams selected for the pilot, usually through RTSP or ONVIF paths already available to the VMS.
Each incident class should map to a Security Center alarm name, priority, camera, and response owner before the pilot begins.
The edge node should sit near the camera and VMS network path so inference remains local and predictable.
Event flow
These pages should make the data path simple enough for IT, security operations, and safety leadership to review together.
DHI reads the approved camera stream on site without changing the recording path.
The edge node detects the safety event locally and attaches camera, time, zone, and confidence metadata.
Security Center receives the structured event so operators can act inside their existing alarm workflow.
Pilot checklist
A strong integration page should help the buyer self-qualify before the first technical call.
The pilot should start with a short camera list and clear zone labels that match how operators talk about the site.
Forklift conflict, track trespass, person-down, smoke, and intrusion events should not all carry the same urgency.
A clean test proves that the right camera appears, the timestamp is useful, and the event is easy to review later.
The detailed guide for event mapping and Security Center alarm routing.
Compare the same DHI event model in a Milestone environment.
Review camera ingest, edge inference, and privacy boundaries.
Bring your camera list, VMS version, alarm workflow, and pilot zones. We will map where DHI fits and what has to be tested first.
No raw video has to leave your site for an integration review.
See the flow on a real operating scenario and scope a pilot around one facility or corridor.
Review camera ingest, edge inference, alert routing, and what stays on-premises.
Download the deployment checklist buyers use before green-lighting an industrial AI pilot.
Bring camera count, VMS constraints, latency expectations, and privacy requirements to a technical review.