VMS Integration

Milestone XProtect AI analytics integration.

DHI connects edge safety detection to Milestone XProtect by reading approved camera streams locally and pushing incident events into XProtect alarm and Smart Client workflows.

Integration proof

Milestone XProtect needs a clear path from camera stream to operator action.

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

Milestone XProtect

DHI connects edge safety detection to Milestone XProtect by reading approved camera streams locally and pushing incident events into XProtect alarm and Smart Client workflows.

Camera workflow

Existing streams

The integration is designed for teams that already rely on XProtect for video review and alarm handling. DHI adds local detection and sends structured events back to the VMS rather than replacing the VMS.

Event routing

Structured alerts

DHI reads the selected stream locally and leaves the XProtect recording path intact.

Deployment check

Pilot-ready scope

Start with the cameras that see the highest-risk zone, not every camera in the estate.

Security posture

On-premise video

Raw video stays on the site network while DHI routes safety metadata into the existing operator workflow.

Fit

Keep XProtect as the operator workspace.

The integration is designed for teams that already rely on XProtect for video review and alarm handling. DHI adds local detection and sends structured events back to the VMS rather than replacing the VMS.

  • Use existing XProtect camera streams and recording infrastructure.
  • Map each DHI incident class to an alarm, camera, priority, and operator response.
  • Keep event review inside Smart Client and existing operational process.

RTSP stream health

Confirm the pilot cameras expose stable streams under normal warehouse, station, or facility load.

Analytics event mapping

Create a clear mapping between DHI incident classes and XProtect alarm definitions.

Operator workflow

Decide which alarms interrupt the operator, which are logged for review, and which require supervisor escalation.

Event flow

From camera signal to VMS alarm.

These pages should make the data path simple enough for IT, security operations, and safety leadership to review together.

1

Ingest the camera

DHI reads the selected stream locally and leaves the XProtect recording path intact.

2

Detect the incident

The edge node classifies the event, adds metadata, and applies the pilot threshold.

3

Send to XProtect

The VMS receives the event so the operator can open the right camera and review the right timestamp.

Pilot checklist

What has to be true before go-live.

A strong integration page should help the buyer self-qualify before the first technical call.

List target cameras

Start with the cameras that see the highest-risk zone, not every camera in the estate.

Name each alarm plainly

Operators should see direct labels like forklift conflict, person down, smoke visible, or restricted entry.

Test the Smart Client path

The pilot should prove that the event appears where operators already work, not in a separate dashboard.