A deployment needs an understandable data path: where video comes from, where the analysis runs, what the operator receives and which records are kept.
ResQVision’s SAIL work included on-premises server build and setup. For another site, the architecture, network access and data-handling arrangements are documented against its requirements.
Define the purpose and coverage
Start with the operational task, monitored area and video required for it. Limit the view and retained material to the agreed purpose; consider adjacent areas and operating hours when planning coverage.
The initial footage assessment uses authorised material for the stated evaluation. Validation, calibration and model training are distinct uses; training use requires a separate agreement.
Map the data path
Camera → analysis → operator review → agreed records. Document the source camera, processing location, receiving team and stored outputs at each step.
Customer-site example: authorised cameras connect to an on-premises processing server; configured events are delivered to the receiving operation. Exact interfaces and connectivity depend on the deployment.
Confirm what leaves the site, which hosting or delivery services are involved and who retains original footage. Offline or air-gapped requirements are assessed against the proposed configuration.
Specify retention and access
Separate full video, event clips, tracks and metadata. The retention period, location, access roles and deletion process are agreed for the implemented system; there is no universal retention period asserted here.
Include the camera system, analysis, event delivery and operator records. Record who can review, export and change the material, and what audit information is available.
Identify responsibilities
ResQVision supplies the agreed analysis, configuration and technical delivery. The customer provides authorised video access, the operating purpose and the people responsible for reviewing and responding.
Where an integrator is involved, identify installation, network, system-interface, maintenance and support responsibilities. The agreement should explain how an outage or change is handled.
Separate safety analytics from identity recognition
People detection, counts and movement tracks describe observed subjects and activity. They do not need to establish a person’s name to support a coastal monitoring task.
Record the information required for the use case and assess any identity-related requirement separately. Camera footage can contain personal information even when the analysis does not identify people by name.
A practical evaluation record
Use a data-flow diagram, retention table, access list and named receiving team. The record should describe the chosen setup and the decisions needed before live operation.
The first conversation can stay at site and task level. We agree a transfer method before receiving video.