DHI reads the same approved RTSP streams XProtect reads, runs detection on the site, and emits structured events over webhook. Wiring those events into XProtect alarm definitions is integration work we scope with your team, not a shipped 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 XProtect reads, runs detection on the site, and emits structured events over webhook. Wiring those events into XProtect alarm definitions is integration work we scope with your team, not a shipped connector.
Camera workflow
This pattern is designed for teams that already rely on XProtect for video review and alarm handling. DHI adds local detection and emits structured events back toward the VMS rather than replacing the VMS.
Event routing
DHI reads the selected stream locally and leaves the XProtect recording path intact.
Deployment check
Start with the cameras that see the highest-risk zone, not every camera in the estate.
Security posture
Raw video stays on the site network while DHI routes safety metadata into the existing operator workflow.
Fit
This pattern is designed for teams that already rely on XProtect for video review and alarm handling. DHI adds local detection and emits structured events back toward the VMS rather than replacing the VMS.
Confirm the pilot cameras expose stable streams under normal warehouse, station, or facility load.
Create a clear mapping between DHI incident classes and XProtect alarm definitions.
Decide which alarms interrupt the operator, which are logged for review, and which require supervisor escalation.
Event flow
These pages should make the data path simple enough for IT, security operations, and safety leadership to review together.
DHI reads the selected stream locally and leaves the XProtect recording path intact.
The edge node classifies the event, adds metadata, and applies the pilot threshold.
The VMS receives the event so the operator can open the right camera and review the right timestamp.
Pilot checklist
A strong integration page should help the buyer self-qualify before the first technical call.
Start with the cameras that see the highest-risk zone, not every camera in the estate.
Operators should see direct labels like forklift conflict, person down, smoke visible, or restricted entry.
The pilot should prove that the event appears where operators already work, not in a separate dashboard.
The detailed guide for XProtect alarm and Smart Client workflow planning.
Review the same edge event model in Security Center.
See how XProtect event routing supports warehouse safety workflows.
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.