Skip to main content

Terminology

Common abbreviations and terms used in the Axis body worn documentation and the body worn content destination API.

AbbreviationMeaning
BWCBody Worn Camera
BWMAXIS Body Worn Manager — web-based administration interface for the body worn system (BWS)
BWSBody Worn System — the complete system of cameras, docking stations, system controller, and BWM
CDContent Destination — the third-party application (your integration) that receives recordings
EMSEvidence Management System
SCUSystem Controller Unit (AXIS W800)
VMSVideo Management System

Additional terms​

TermDefinition
Connection fileA JSON file that configures how the BWS connects to the content destination. Created by the CD and imported into BWM.
ContainerIn the Swift API model, a top-level directory. Each recording creates one container.
ObjectIn the Swift API model, a file within a container. Clips, key files, bookmarks, and GNSS trails are objects.
CapabilityA feature that the content destination declares support for via System/Capabilities.json. Controls which features the BWS enables.
RecordingA set of one or more video clips captured during a single trigger event, stored in one container.
ClipA single video file within a recording. Long recordings are split into multiple clips.
BookmarkAn annotation attached to a recording at a specific time, optionally with a category and free-text description.
TriggerThe event that starts a recording (button press, fall detection, always-record, wireless broadcast, or unholster).
GNSS trailGNSS location data captured during a recording, stored as a JSON object in the recording container.
Signed videoEmbedded cryptographic signatures in video frames (SEI NAL units) that prove authenticity and integrity from camera to client.