VMS integration

FI Tech + Milestone XProtect: AI Vision on Your Existing CCTV

FI Tech is camera-agnostic and integrates with Milestone XProtect via ONVIF Profile S/T and RTSP — no rip-and-replace, no firmware swap. We pull streams from your Recording Server, run PPE, intrusion, fall, fire, license-plate and occupancy models, then push detections back as XProtect alarms, bookmarks, generic events or webhooks. Typical pilot deploys in 2–4 weeks on a Riyadh-hosted, PDPL-aligned data path.

Talk to integrations team Read setup guide

Compatibility matrix

Supported product lines XProtect Essential+, Express+, Professional+, Expert and Corporate (2020 R1 and newer recommended)
Required ONVIF profile Profile S (live streaming) — Profile T recommended for H.265 and event metadata
Authentication ONVIF user (digest), Windows / Active Directory accounts, or HTTPS basic auth on the camera
Streaming protocols RTSP/RTP (H.264, H.265), MJPEG over HTTP, Milestone Recording Server pull or direct camera pull
Event channel ONVIF metadata, XProtect Generic Events (TCP/UDP), MIP SDK plugin, webhook, syslog
FI Tech deployment topology Sidecar inference server pulls RTSP from the Recording Server or directly from cameras; alerts pushed back to XProtect Smart Client as bookmarks and alarms

Setup guide

Seven steps from "verify ONVIF" to "test alert". Scoped for a network-accessible XProtect deployment.

  1. 01

    Verify ONVIF profile and credentials

    Confirm each camera is ONVIF Profile S or T conformant and that an ONVIF user exists with at least Operator rights. Note the RTSP port (default 554) and HTTPS port.

  2. 02

    Allow-list the FI Tech inference server

    Open the camera or Recording Server to a dedicated FI Tech VM on the LAN. Required ports: RTSP 554/TCP, ONVIF 80 or 443/TCP. No outbound internet is needed for on-prem mode.

  3. 03

    Provision a service account in XProtect

    Create a Milestone user (e.g. fi-tech-inference) with View Live, Read Bookmarks and Trigger Generic Events rights. Bind it to the FI Tech connector.

  4. 04

    Install the FI Tech VMS connector

    Deploy the FI Tech connector container on a Linux host (Ubuntu 22.04 LTS or RHEL 9). Point it at the XProtect Management Server or Recording Server endpoint and authenticate.

  5. 05

    Map cameras and AI models

    In the FI Tech console, select XProtect cameras and assign AI models per stream — PPE, intrusion, fall, fire, license plate or occupancy. Save the mapping.

  6. 06

    Configure alert routing

    Choose how detections appear in XProtect: Generic Event + alarm, bookmark on the live timeline, MIP plugin overlay, or external webhook to your SOC. Test with a tripwire event.

  7. 07

    Test the end-to-end alert path

    Stage a controlled scene (e.g. person without hard-hat). Verify the bounding box appears in Smart Client within 1.5 s and that the alarm triggers the configured workflow.

AI models supported on Milestone XProtect

  • PPE compliance

    Hard hat, safety vest, gloves, safety boots, harness — typical 92–96% mAP on construction footage.

  • Intrusion / perimeter

    Person and vehicle in restricted polygon, with loitering timers.

  • Fall detection

    From-height and slip-and-fall on indoor and scaffold scenes.

  • Fire and smoke

    Early-stage smoke plume and open flame, day and night IR.

  • License plate (LPR)

    Saudi and GCC plates; Arabic + Latin glyphs; gate and parking flows.

  • Occupancy and people-counting

    Per-zone headcount, queue length, dwell time.

Sample latency and accuracy

End-to-end latency
1.0 – 1.8 s end-to-end (camera → inference → XProtect alarm)
Throughput
10 – 25 FPS per stream depending on model and GPU class
Model accuracy
PPE 92–96% mAP, intrusion 96%+ recall, LPR 94%+ on Saudi plates

Typical figures — depend on camera resolution, codec, lighting, GPU (NVIDIA T4 / L4 / RTX A2000) and network jitter.

Saudi-specific deployment

For customers operating in the Kingdom, FI Tech offers a PDPL-aligned data path: raw video stays on the customer Recording Server, inference runs on a sidecar appliance on your LAN or in our Riyadh region, and only structured detections (event metadata, thumbnails on opt-in) leave the camera network. Alert routing is hosted in Riyadh with a documented residency boundary, and audit logs are exportable for NCA / SDAIA review.

Frequently asked questions

Do we need to replace our Milestone XProtect cameras to add FI Tech AI?

No. FI Tech is camera-agnostic and integrates with XProtect via ONVIF/RTSP. Any camera already streaming into your Recording Server is eligible — there is no rip-and-replace and no firmware change on the cameras.

Is FI Tech a Milestone Solution Partner?

FI Tech is camera-agnostic and integrates with Milestone XProtect through the publicly documented ONVIF, RTSP and Generic Events interfaces, plus an optional MIP SDK plugin. Formal Milestone partner status is tracked separately on our partners page.

How are alerts displayed inside XProtect Smart Client?

Detections can appear as alarms in the Alarm Manager, as bookmarks on the live timeline, or as a custom MIP plugin overlay with bounding boxes. Operators can also receive parallel notifications by webhook, email or Telegram.

Where does video data live — does footage leave Saudi Arabia?

By default video stays on-prem on the customer Recording Server. FI Tech inference runs on a sidecar VM on your LAN or in our Riyadh region. PDPL-aligned data residency means raw frames never cross the border unless you explicitly opt in.

How long does a typical Milestone + FI Tech pilot take?

Two to four weeks for up to 32 cameras: one week of network and credentials setup, one to two weeks of model calibration on your scenes, then go-live. Larger sites scale linearly with one extra inference node per ~32 streams.

Ready to add AI to your Milestone XProtect deployment?

We will scope cameras, models and alert routing on a 30-minute call.

Contact FI Tech