Overview#
At the end of a shift, an officer returns to the station and docks their camera. Within seconds, footage uploads automatically, attaches to the relevant incident record, and enters the evidence retention lifecycle without anyone touching a keyboard. That is the operational baseline this module delivers. For agencies managing thousands of officers across multiple jurisdictions, manual upload processes and inconsistent metadata create gaps that defence counsel can exploit. Automated ingestion closes those gaps from the moment the camera docks.
The module supports body-worn camera fleets from multiple manufacturers and is designed for policing, border security, corrections, and any operational context where officer-worn video is captured as evidence. It also reaches into third-party vendor systems: offline ingestion jobs pull recordings out of external archives, including vendor platforms with no live connection to the platform, verify their integrity, de-duplicate them, and register them as evidence with a full chain-of-custody record.
Key Features#
- Automated BWC footage upload with support for cameras from multiple manufacturers
- Metadata extraction covering GPS coordinates, timestamps, officer ID, and device serial
- Automatic categorisation based on incident type, CAD linkage, and extracted metadata
- Retention policy enforcement aligned to evidence category and jurisdiction
- Chain of custody initialisation from the docking station upload event
- Video indexing for rapid search and retrieval by officer, date, location, or incident
- Integration with CAD and incident management systems for automatic case linking
- Officer assignment tracking and shift-based evidence organisation
- Offline vendor ingestion jobs that download each recording, verify it with cryptographic hash checks, apply content-based de-duplication, store it in the appropriate deployment tier, and register it with a chain-of-custody intake record
- Ingestion job management through a strongly-typed API, with the ability to list jobs and to start or retry them
- American Dynamics connector that retrieves recordings through the ONVIF Profile G recording interface
- Audax DEMS connector with configuration-driven access to the vendor interface and true offline download of held footage
- Connector credentials encrypted at rest for each connection, with downloads guarded against server-side request forgery
- Automatic hand-off to the analytics pipeline once ingested footage is registered as evidence
Use Cases#
- Automating end-of-shift footage upload with immediate categorisation and case linking, removing manual steps that introduce error
- Enforcing jurisdiction-specific retention schedules across BWC evidence categories without manual policy application
- Searching BWC footage by officer, date, GPS polygon, or incident type to support rapid investigation review
- Maintaining a complete chain of custody for BWC evidence from the moment of recording through court presentation
- Supporting oversight and compliance audits with full upload logs and metadata provenance
- Migrating historical body-camera footage from a legacy vendor archive into unified evidence management without losing integrity or custody records
- Running nightly ingestion jobs that bring newly dock-uploaded recordings from vendor systems into the relevant cases automatically, with failed jobs retried on demand
Integration#
The module connects with evidence management, incident management, and CAD systems. Chain of custody records are written to the audit trail at every stage. Footage is stored in secure object storage with cryptographic integrity verification to ensure court-admissible evidence packaging. Vendor connectors extend this reach into third-party camera platforms: an American Dynamics connector ingests recordings over the ONVIF Profile G recording interface, and an Audax DEMS connector performs true offline download from that vendor's evidence system. Credentials for each vendor connection are encrypted at rest, and once a recording is registered it is handed off automatically to the analytics pipeline for downstream processing.
Open Standards#
- OAuth 2.0 (RFC 6749): Camera vendor connectors (including Axon Evidence.com) authenticate using the client credentials grant flow defined by OAuth 2.0, with Bearer token transport on all subsequent integration requests.
- ONVIF Profile G (Recording and Storage): The American Dynamics connector retrieves recordings through the ONVIF Profile G recording interface, allowing footage held on standards-compliant recorders to be ingested without vendor-specific export tooling.
- W3C Verifiable Credentials Data Model v2.0: Signed Verifiable Credentials are issued for each evidence item at the point of ingestion, binding the SHA-256 file digest to a DID-based issuer to provide cryptographically verifiable provenance.
- SHA-256 (FIPS PUB 180-4): Integrity hashes of footage files and chain-of-custody payloads are computed using SHA-256 at every stage, from docking-station upload through court-ready export.
- RFC 3161 (Internet X.509 PKI Time-Stamp Protocol): Trusted timestamps are embedded in court-grade evidence exports, with RFC 3161 TSA tokens used to prove that footage existed in its recorded form at a specific point in time.
- ISO 19005 PDF/A (parts 1 to 4): Court-ready evidence packages are exported as PDF/A-3B by default, with support for ISO 19005-1 through ISO 19005-4 variants to meet jurisdiction-specific archival requirements.
- PKCS#7 (RFC 2315) Digital Signatures: Court-ready export bundles include PKCS#7 digital signatures over the evidence package content, providing non-repudiation for prosecutorial use.
- ISO 8601 (Date and Time Representation): All timestamps across recording metadata, chain-of-custody entries, retention schedules, and audit log events are serialised in ISO 8601 format for unambiguous interchange.
- EXIF / JEITA CP-3451C (Exchangeable Image File Format): GPS coordinates, capture timestamps, and device identifiers are extracted from EXIF metadata embedded in footage files during ingestion to populate incident linkage and location fields.
Last Reviewed: 2026-07-16 Last Updated: 2026-07-16