Eye365 investigations: from an event to a controlled export
An investigation method to validate against your deployed version.
Updated
Principle and limits
Begin with a question, time window and camera group. Establish time zone and any clock offset before correlating events. Search can use only the video and metadata actually recorded and supported by the deployed version. Missing results can mean absent metadata, retention expiry, permissions or a narrow query; they do not prove nothing happened.
Worked example
For a reported entrance incident at 14:00, begin with an agreed surrounding interval, locate the arrival and inspect adjacent cameras where available. Preserve preceding and following context. A search match is a candidate for review, not a finding of responsibility. This sequence describes an investigation method, not a promise that every installation has identical search controls.
Installation and acceptance
Confirm camera support, metadata, firmware and licenses on the Eye365 deployment. Export with appropriate authorization, retain the original and document time range, operator and recipient. Reopen the export independently. A cryptographic hash can show that bytes have not changed relative to a recorded hash; it does not prove the scene is authentic or its interpretation correct.