Detection on a MAXPRO Estate Without Replacing It
No MAXPRO connector is prebuilt. The connection would be to the stream, on the RTSP path that already carries Axis, Hanwha and Verkada, and Honeywell MAXPRO is one of the platforms that path has been exercised against, so an engagement scopes configuration and verification rather than development. MAXPRO is a video management system deployed in commercial buildings and critical infrastructure, and it would stay in place. AI Live Insight would read streams alongside it.
How it connects
Streams would be consumed over RTSP, from the cameras or republished by MAXPRO, each source added by address, port, stream path and credentials. Encoding would stay where it is: the existing H.264 or H.265 bitstream read as emitted with the codec detected per source, so nothing is re-encoded and no encoder load is added to the recorders.
The flow would be inbound only. Detections would become a timed metadata track beside each recorded segment, and the clip around an event would be filed in the library under one Recording Folder organized by camera, carrying access control, retention and chain of custody. Classes, thresholds, severity, zone rules and clip length would be set per camera in the portal.
Nothing would flow back. Camera control, device management, MAXPRO's own metadata and its user management would stay with Honeywell. In a critical infrastructure setting the network is usually the constraint rather than the software, so an engagement would establish how streams are reached across whatever segmentation is in place before anything is committed. Because analysis reads the live stream, it would run on a GPU server inside that network.
What you can do together
- Add detection to a MAXPRO estate without replacing cameras or changing how recording works.
- Keep the clip around an event as evidence under retention and a custody record.
- Configure per camera, so a plant room and a lobby are not held to one rule.
- Run the analysis inside your own network, with no stream leaving it.
A scenario
- ScopingThe engagement would confirm which cameras cover the aisle doors, how streams cross the segmented network, and what counts as held open.
- SetupA GPU server would be placed inside the operations network, and the aisle cameras added.
- ConfigurationA zone rule with a dwell condition would cover each doorway, with clip length set to show who opened it.
- A shiftA door held past the threshold would raise an alert on the dashboard, and the clip would be filed in the library under the hall's folder.
- AuditThe compliance team would pull the quarter's clips from the library for its access review, while MAXPRO holds the continuous recording.
What stays where
MAXPRO remains the video management system
Cameras, recording, device management and its users stay there.
The stream is the whole of the connection
Inbound only, with nothing written back, and no stream leaving the network.
Evidence lands in the library
Clips around events carry access control, retention and chain of custody.
Processing would run inside your network
A GPU server on the same segment 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 Honeywell MAXPRO 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/honeywell-maxpro