VMS integration

FI Tech + Genetec Security Center: AI Vision on Your Existing CCTV

FI Tech is camera-agnostic and integrates with Genetec Security Center via ONVIF Profile S/T, RTSP and the Genetec SDK — no rip-and-replace. We pull streams from your Archiver, run PPE, intrusion, fall, fire, license-plate and occupancy models, then post Custom Events back into Security Desk and Event-to-Action. Typical pilot deploys in 2–4 weeks on a Riyadh-hosted, PDPL-aligned data path.

Compatibility matrix

Supported product linesSecurity Center 5.10 and newer (Omnicast video, Synergis access). On-prem and Genetec Cloud Link / SaaS Edition.
Required ONVIF profileProfile S minimum, Profile T recommended for H.265 and event metadata. Profile M used where the camera publishes analytics objects.
AuthenticationGenetec service account (Server Admin), camera-side ONVIF user with digest auth, optional TLS client certs
Streaming protocolsRTSP/RTP (H.264, H.265, MJPEG). Archiver pulls camera; FI Tech connector pulls from Archiver or directly from camera URI.
Event channelGenetec Software Development Kit (SDK) custom events, ONVIF metadata, webhook bridge, syslog forwarder
FI Tech deployment topologyFI Tech inference VM peers with the Archiver on the LAN. Detections post back as Genetec custom events that drive the Event-to-Action engine.

Setup guide

Seven steps from "verify ONVIF" to "test alert".

  1. 01

    Verify ONVIF profile and camera firmware

    Confirm Profile S/T conformance for each unit (Genetec Camera Compatibility List or the unit's web UI). Note RTSP and ONVIF ports.

  2. 02

    Open the LAN path to FI Tech

    Allow RTSP 554/TCP and ONVIF 80 or 443/TCP from the FI Tech inference host to the Archiver and to each camera. No outbound internet required for on-prem mode.

  3. 03

    Create a Security Center service account

    Add a user (e.g. fi_tech_inference) in Config Tool with the Live video and Custom events privileges. Generate an SDK certificate or token for the connector.

  4. 04

    Install the FI Tech Genetec connector

    Deploy the connector container on Ubuntu 22.04 LTS or Windows Server 2022. Point it at the Directory server and authenticate with the SDK certificate.

  5. 05

    Map cameras to AI models

    From the FI Tech console, pick Genetec entities and assign models — PPE, intrusion, fall, fire, LPR, occupancy. Save and start the pipeline.

  6. 06

    Wire detections to Event-to-Action

    In Config Tool, route the FI Tech custom event to actions: pop-up live tile, alarm, archive bookmark, send email, trigger Synergis door, or external webhook.

  7. 07

    Test the end-to-end alert path

    Stage a controlled scene. Verify the bounding box overlay reaches the Security Desk operator within ~1.5 s and that the configured action fires.

AI models supported on Genetec Security Center

  • PPE compliance

    Hard hat, vest, gloves, boots, harness — calibrated per site.

  • Intrusion / perimeter

    Polygon zones with loitering and crossing rules, fused with Synergis access events.

  • Fall detection

    Slip and from-height events for industrial and retail environments.

  • Fire and smoke

    Early-stage detection with thermal-camera fusion when present.

  • License plate (AutoVu-friendly)

    Saudi + GCC plates, runs alongside or in place of AutoVu Sharp cameras.

  • Occupancy and people-counting

    Per-zone counts feeding Genetec maps and dashboards.

Sample latency and accuracy

End-to-end latency
1.0 – 2.0 s end-to-end (camera → inference → Security Desk)
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 resolution, codec, lighting, GPU (T4 / L4 / A2000) and Archiver load.

Saudi-specific deployment

For KSA customers, FI Tech runs a PDPL-aligned data path: raw video stays on the Genetec Archiver, inference happens on a sidecar appliance on your LAN or in our Riyadh region, and only structured detections 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 swap our cameras to use FI Tech with Genetec Security Center?

No. FI Tech is camera-agnostic and integrates with Genetec via ONVIF and RTSP plus the Genetec SDK. Any camera already on your Archiver is eligible.

Is FI Tech a Genetec Technology Partner?

FI Tech connects via the publicly documented Genetec SDK, ONVIF and RTSP interfaces. Formal partner status is tracked separately on our partners page.

How are detections shown in the Security Desk?

Detections raise Custom Events that the Event-to-Action engine renders as alarms, pop-up tiles, bookmarks or door triggers. Bounding-box overlays can be drawn on live tiles via the SDK.

Does this work with Genetec SaaS / Cloud Link?

Yes. The FI Tech connector also supports Cloud Link via the Genetec REST API, with the same custom-event surface. Inference can run on a Riyadh-region host or on a customer LAN appliance.

How does data residency work in KSA?

Raw video stays on the customer Archiver. Inference runs on-prem or in our Riyadh region; only structured detections cross the network. Audit logs are exportable for NCA / SDAIA review.

Ready to add AI to your Genetec Security Center deployment?

We will scope cameras, models and Event-to-Action wiring on a 30-minute call.

Contact FI Tech