Detection on the Cameras CompleteView Already Records
No CompleteView connector is prebuilt. The connection would be to the stream, on the RTSP path that already carries Axis, Hanwha and Verkada, and Salient is one of the platforms that path has been exercised against, so an engagement scopes configuration and verification rather than development. CompleteView is a video management platform used in retail, education and municipal deployments, 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 CompleteView, 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 recording servers.
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, CompleteView's own metadata and its user management would stay with Salient. In a school district or a municipal estate the cameras are usually spread across many buildings on one network, so an engagement would settle where the analysis servers sit and which cameras each covers rather than assuming one central server reaches everything.
What you can do together
- Add detection to cameras CompleteView already records, without replacing a camera.
- Keep the clip around an event as evidence under retention and a custody record, which matters when a clip is going to be requested later.
- Configure per camera, so a school entrance and a bus bay differ.
- Run the analysis on site, so an alert reaches whoever is watching in seconds.
A scenario
- ScopingThe engagement would confirm which cameras cover the doors, how streams are reached across the district network, and what counts as propped.
- SetupA server would be placed per campus depending on the network, and the door cameras added and grouped into a folder per building.
- ConfigurationA zone rule with a dwell condition would cover each doorway, active during school hours, with clip length set to show who propped it.
- A morningA propped door would raise an alert, and the clip would be filed in the library under that building's folder.
- A records requestMonths later the clip would be retrievable from the library with its custody record intact, which is the part a request turns on.
What stays where
CompleteView 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.
Evidence lands in the library
Clips around events carry access control, retention and chain of custody, which is what makes one answerable to a later request.
Processing would run on site
Servers on the camera network are what keep alert latency low, and it is the deployment this work is projected for.
Products and solutions
Next step
See it on your own Salient CompleteView 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/salient-completeview