Motorola Solutions

Working with Adobe and Motorola Solutions as lead architect, I defined how police departments register video-capture devices and manage recorded evidence in CommandCentral — the administration and Vault systems used by agencies such as the Atlanta Police Department.

The work centered on Freedom of Information Act requirements: registering mobile capture devices, configuring recording profiles, and giving departments controlled access to video with chain of custody, transcription, redaction, and purge handling.

The boards document two competing approaches for the mobile capture device profile. Option 1 — the preferred path — follows the existing Admin layout as closely as possible: a single-row table for the one supported profile, with the full schema of settings in a right-hand scrolling panel. This minimizes future updates when multiple profiles arrive.

Option 2 places the profile configuration directly on the page. It might be marginally faster, but it breaks Admin display rules — and the annotations ask the hard question of how much faster it would actually be.

Every board carries a red annotation layer recording what exists at MVP and what is deferred: no search, new, or delete options on the profile table; the profile name is not editable since only one profile can exist; the existing Vault device list loads in an iframe under the Devices tab; and logout returns the administrator to the Mobile capture devices screen with its selection preserved.

Device registration itself is a three-step flow — Login, Configure Parameters, Create QR Code — reusing the existing registration site inside the page frame rather than rebuilding it.

On the Vault side, the media view pairs the video player with a location map, speaker-attributed transcription, and the controls FOIA work demands: chain-of-custody verification, transcription verification, redaction, restriction to internal-affairs personnel, a purge date, and download or export.