VMS integration

FI Tech + Bosch BVMS: AI Vision on Your Existing CCTV

FI Tech is camera-agnostic and integrates with Bosch BVMS via ONVIF Profile S/T, RTSP and the Bosch VMS SDK — no rip-and-replace. We pull streams from the Video Streaming Gateway, run PPE, intrusion, fall, fire, license-plate and occupancy models, then post detections back as BVMS alarms or generic events. Typical pilot deploys in 2–4 weeks on a Riyadh-hosted, PDPL-aligned data path.

Talk to integrations teamRead setup guide

Compatibility matrix

Supported product linesBosch BVMS 11.x and newer (BVMS Lite, Plus, Pro), Bosch DIVAR IP appliances, Bosch IP cameras (Flexidome, Dinion, Autodome, Inteox)
Required ONVIF profileProfile S minimum, Profile T recommended for H.265 and event metadata. Bosch IP cameras are widely ONVIF S/T conformant.
AuthenticationBosch service account (BVMS Operator), camera-side digest user, optional certificate-based device auth (Escrypt)
Streaming protocolsRTSP/RTP (H.264, H.265, MJPEG), Bosch Video Streaming Gateway, RCP+ for legacy cameras
Event channelBosch SDK alarm injection, ONVIF metadata, BVMS Generic Event Source, webhook, syslog
FI Tech deployment topologyFI Tech inference server peers with the BVMS Management Server on the LAN. Detections post back as alarms via the Bosch SDK or Generic Event Source.

Setup guide

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

  1. 01

    Verify ONVIF profile and Bosch firmware

    Confirm cameras run a recent firmware (CPP6/7/13/14, recommended 8.x or newer) with ONVIF Profile S/T enabled in the camera Configuration Manager.

  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 each camera and to the Video Streaming Gateway / Management Server.

  3. 03

    Provision Bosch users

    Create a dedicated camera-side ONVIF Operator user (Configuration Manager). In BVMS, create a service account with View Live and Generic Event privileges.

  4. 04

    Install the FI Tech connector

    Deploy the FI Tech connector container on Ubuntu 22.04 LTS or Windows Server 2022. Point it at the BVMS Management Server and authenticate with the SDK credentials.

  5. 05

    Map cameras and AI models

    Select Bosch cameras in the FI Tech console and assign AI models per stream — PPE, intrusion, fall, fire, license plate, occupancy. Save the mapping.

  6. 06

    Configure alarm routing

    Choose how detections appear: BVMS alarm with workflow (Operator Acknowledge), generic event triggering Command Scripts, alarm-image popup, or webhook to your SOC.

  7. 07

    Test the end-to-end alert path

    Stage a controlled scene. Verify the alarm reaches the BVMS Operator Client within ~1.5 s and that the configured workflow fires.

AI models supported on Bosch BVMS

  • PPE compliance

    Hard hat, vest, gloves, boots, harness — strong on Bosch Flexidome / Dinion 4K streams.

  • Intrusion / perimeter

    Polygon zones, loitering, tailgating; complements Bosch Intelligent Video Analytics where present.

  • Fall detection

    Slip and from-height events for transport, industrial and rail.

  • Fire and smoke

    Early-stage detection, day and night IR; fuses with Bosch AVIOTEC where present.

  • License plate (LPR)

    Saudi + GCC plates on Bosch Autodome PTZ and bullet streams.

  • Occupancy and people-counting

    Per-zone counts, queue length, dwell time. Useful for transit and retail.

Sample latency and accuracy

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

Saudi-specific deployment

For KSA customers, FI Tech offers a PDPL-aligned data path: raw video stays on your Bosch VRM / DIVAR IP, inference runs 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 Bosch cameras to use FI Tech?

No. FI Tech is camera-agnostic and integrates with Bosch BVMS via ONVIF and RTSP plus the Bosch VMS SDK. Cameras already on your BVMS are eligible — no firmware swap.

Is FI Tech a Bosch Integration Partner?

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

How do detections show in BVMS Operator Client?

Detections raise BVMS alarms with the configured workflow — alarm-image popup, Command Script, audio file, or operator acknowledgement. They can also flow as generic events that drive PTZ presets or relay outputs.

Can FI Tech run alongside Bosch IVA / AVIOTEC?

Yes. We treat IVA and AVIOTEC events as additional inputs and fuse them with our analytics — useful for raising precision or adding analytics IVA does not cover.

How does data residency work in KSA?

Raw video stays on the customer Video Recording Manager / DIVAR IP. 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 Bosch BVMS deployment?

We will scope cameras, models and alarm workflows on a 30-minute call.

Contact FI Tech