Use this checklist to verify your integration before release. Items are categorized as Mandatory (must have) or Good to have (recommended).
HTTPS support
| Requirement | Explanation | Importance |
|---|
| HTTPS communication supported when communicating with the body worn system (BWS)? | | Mandatory |
| HTTPS certificate can be renewed when the server IP changes? | | Mandatory |
Connection file
| Requirement | Explanation | Importance |
|---|
| Same connection file usable for multiple BWS connected to one server? | Don't tie the file to a specific system controller serial number. Simplifies large installations. | Good to have |
Import data from BWS
| Requirement | Explanation | Importance |
|---|
| Default minimum retention period long enough (for example, 90 days)? | Prevents recordings from being deleted immediately after upload when cameras aren't docked frequently. | Mandatory |
| Retention time adjusted automatically based on recording category? | Requires ReadCategories capability. | Good to have |
| Users notified of offloading problems? | | Good to have |
| Users notified about newly arrived recordings of a certain category? | Requires ReadCategories capability. | Good to have |
| Application can import and decrypt a USB-exported file? | Stuck recordings can be offloaded from AXIS W800 to USB. | Good to have |
| Signed video used? | Provides end-to-end authentication from camera to client. | Good to have |
Present BWS data
| Requirement | Explanation | Importance |
|---|
| Recordings organized by camera user, not physical camera? | Cameras may be reassigned between users (self-assign mode). | Mandatory |
| Camera user name combined with unique user ID as identifier? | Display as "Name (UserID)". Requires StoreUserIDKey capability. | Mandatory |
| Recording metadata presented in a user-friendly manner (for example, bookmarks)? | | Mandatory |
| Search for recordings by metadata (category, location, trigger method)? | | Good to have |
| Recordings longer than one clip displayed as a single recording? | | Mandatory |
| Location data used sensibly (map display, search by location, copy/paste coordinates)? | | Good to have |
| Operator directed to playback view when opening a body worn camera's live view? | Display a friendly message or camera image since live view is separate. | Good to have |
| Trigger time used as default playback start point? | Pre-buffer content is less relevant at first sight. Use bookmarks or thumbnails at trigger time. | Good to have |
| GNSS trails shown on a map during recording playback? | Available since AXIS OS 11.1. | Good to have |
System maintenance
| Requirement | Explanation | Importance |
|---|
| Measure taken to prevent removing a camera in the application before removing it from BWM? | Prevents license and upload issues from mismatched configurations. | Mandatory |
| BWS configurations backed up regularly? | Helps restore the BWS connection after reinstalling the application. Prevents stuck content on AXIS W800. | Good to have |
| BWM accessible in a built-in browser? | Avoids switching between BWM and the application. | Good to have |
| Users notified when BWS licenses run out? | Licenses based on camera users may run out when new users are created. | Good to have |
| BWS events logged in the application? | For example, "recordings from BWC have arrived." | Mandatory |
| Requirement | Explanation | Importance |
|---|
| Performance tested on a system as large as planned to support? | Recordings must be offloaded in time or system controllers and cameras fill up. | Mandatory |
Documentation
| Requirement | Explanation | Importance |
|---|
| User documentation explaining how to integrate the BWS? | Provide a PDF copy to Axis. | Mandatory |
| Webpage showing the integration exists? | Provide a link to Axis. | Good to have |
| Documented from which BWS firmware version the application has support? | | Mandatory |
| Users informed: system is locked to one CD instance after setup (system reset required to change)? | The BWS works only with the application instance matching its SystemID. | Mandatory |
| Users informed: BWS administration is done in BWM, not in the application? | | Mandatory |
Upload speed considerations
The maximum transfer speed of an AXIS W800 is 1 Gbit/s. Plan capacity for your deployment:
Example: 100 cameras per shift, 2 hours of recording per camera at 1080p high bitrate (~5 GB/hour) = 1 TB per shift. At 500 Mbit/s throughput, offload takes ~5 hours. Ensure offload completes before the next shift starts.
Connection file importance
The same connection file is required for a content destination to continue operating. Users cannot move a system controller to a different CD instance without a system reset. Implementing StoreReadSystemID enforces this automatically.