Detection on the Bosch Cameras Already Installed
No Bosch-specific connector is prebuilt. The connection would be to the stream, on the standard RTSP and ONVIF path that already carries Axis, Hanwha and Verkada, and Bosch is one of the vendors that path has been exercised against, so an engagement scopes configuration and verification rather than development. Bosch supplies IP cameras and recorders across transport, industrial and public sector sites, and all of it would stay in place. AI Live Insight would read the streams.
How it connects
Each camera or recorder would be added by pointing the portal at the existing feed: domain or IP, port, stream name, and credentials where the device requires them. ONVIF profiles S and T cover discovery, stream URL retrieval and PTZ. Encoding would stay on the device, the existing H.264 or H.265 bitstream read as emitted with the codec detected per source, so a mixed fleet of Bosch and other makes runs in one service without re-encoding anything.
Each camera would stand on its own, with its own connection details, detection settings and recordings, appearing in the library as a tile that can be watched, organized into folders, searched and sorted. Detections would become a timed metadata track beside each recorded segment, and the clip around an event would be filed under one Recording Folder organized by camera, carrying the library's access control, retention and chain of custody.
Two limits are worth stating. The connection is to the stream, so camera control and device management would stay with Bosch or whatever recorder is in place. And although Bosch carries ONVIF Profile M conformance on its side, the platform's ONVIF support today is profiles S and T, so a Bosch camera's own on-device analytics events would not be consumed; detection would run on the stream instead.
What you can do together
- Add detection to Bosch cameras already installed, with no device replaced and no encoder added.
- Organize cameras into folders that match how a site is laid out, which matters beyond a handful of them.
- Keep the clip around an event as evidence under retention and a custody record.
- Set classes, thresholds and zone rules per camera, so a perimeter and a plant room differ.
A scenario
- ScopingThe engagement would confirm which cameras cover the platform edge, how each is reached, and what counts as a crossing rather than a lean.
- SetupA GPU server would be placed in the operator's own network, and the platform cameras added with their stream details and grouped into a folder per station.
- ConfigurationA zone rule would cover the track side of the yellow line on each camera, with the seconds kept either side of a detection set to show the approach.
- An eveningA crossing would raise an alert on the operator dashboard, with the clip filed in the library under that station's folder.
- AfterwardsThe safety team would pull the month's clips for a report. The recorders would go on holding the continuous footage.
What stays where
Bosch keeps the cameras and the recording
Device settings, camera control and any recorder already in place stay exactly as they are.
The stream is the whole of the connection
It flows inbound only, and nothing is written back to a camera or a recorder.
On-device analytics stay on the device
Platform ONVIF support is profiles S and T, so a camera's own analytics events are not consumed; detection runs on the stream.
Processing would run on site
A GPU server on the same network is what keeps alert latency low, and it is the deployment this work is projected for.
Products and solutions
Next step
See it on your own Bosch instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/bosch