Motorola Watchguard Videomanager EX - Device Profile Management Reference Guide

WHAT ARE DEVICE PROFILES?

Device profiles are the mechanism which dictates how your body-worn cameras record footage and behave in the field. Before
you assign cameras and start recording, you must ensure that you have created device profiles which fit the unique needs of
your organization.
You can create as many profiles as necessary - for example, you may want to create one profile for high-resolution recordings,
one for use with Yardarm™ HolsterAware™ Peripherals, and one for use with Peer-Assisted Recording.
Once you have created these profiles, you can control which body-worn cameras receive them, based on the body-worn
cameras’ operators. This ensures that your workers only have access to the profiles which are relevant to their workflow.

 

HOW DO I CREATE A DEVICE PROFILE?

To create a new device profile:
1. Open VideoManager EX.
2. Navigate to the Admin tab.
3. Select the Devices pane.
4. Click the Device Profiles section.

5. Click Create Profile.
6. In the Name field, enter the name of the profile.
7. From the Device Family dropdown, select VB400.

You can configure the following settings:

NOTIFICATIONS AND ALARMS
● SOUND ALARM WHEN STORAGE NEARLY FULL
If the body-worn camera’s storage is running low, an alarm will sound.
● SOUND ALARM WHEN BATTERY LEVEL CRITICAL
If the body-worn camera’s battery is running low (< 10 minutes remaining), an alarm will sound.
● BLINK LED IN STANDBY
If the VB400 is idle (assigned and undocked, but not recording), its top LED will blink green at short intervals.
● CUSTOMIZE LED PATTERNS
If enabled, you can select how the VB400’s LEDs will behave when the body-worn camera is recording.
● WHEN IN NORMAL MODE AND WHEN IN HUSH MODE
Enable or disable LEDs, beeps and vibrate for both modes.
● RECORDING ALARM
If enabled, the VB400 will beep and vibrate periodically while it is recording. You can also configure the interval at
which the beeps and vibrations will occur.
● ALARM WHILE MUTED
If enabled, the VB400 will beep and vibrate periodically while its audio is muted. You can also configure the interval
at which the beeps and vibrations will occur.

POWER MANAGEMENT
● BEHAVIOR WHEN IDLE
Select how the VB400 will behave when it has been undocked and assigned, but not recording.
○ DEVICE ENTERS STANDBY MODE
The VB400 will enter standby mode. It will leave standby mode as soon as it is prompted to record again.
○ DEVICE SHUTS DOWN
The VB400 will shut down. This means its battery will last longer in the field. It will turn on again a few
seconds after being prompted to record.
● ENTER SAFETY MODE IF IDLE AFTER UNDOCKING
If enabled, the VB400 will enter safety mode (i.e. will be completely inert and unable to record footage) if it is not
prompted to start recording within 10 seconds after undocking.

RECORDING BEHAVIOR
● SHOW VIDEO METADATA OVERLAY
If enabled, the metadata overlay will be burned in for all videos recorded on a VB400 with this profile.
● OVERWRITE OLDEST FOOTAGE WHEN FULL
If enabled, the VB400 will start overwriting its oldest footage when its storage is full. If disabled, the VB400 will
stop recording once its storage is full.
● PRE-RECORD
If enabled, the VB400 will capture a period of time immediately before it is prompted to start recording. You can
also configure:
○ The length of the pre-record period (between 1 and 120 seconds)
○ Whether the VB400 pre-records automatically, or must be manually prompted to start pre-recording. The
button and gesture which prompts pre-recording can be configured in the Controls section.
○ Whether the VB400 also has a post-record period, which is captured immediately after it is prompted to
stop recording.

● RECORD AUDIO

Select whether the VB400 will record audio. The options are as follows:
○ Yes
○ Yes, except during pre-record - this option is only available if pre-record has been enabled.
○ No
You can also configure whether audio is initially muted when the VB400 is undocked (and must therefore be
manually unmuted using a pre-configured gesture).
● ENABLE GPS
If enabled, the VB400 will capture location information for its videos. This information can be reviewed alongside
the video on VideoManager.
● VIDEO LENGTH
The length of time for which a VB400 can record, after which the recording is split into multiple, shorter recordings
for ease of review.
● SUPPRESS RECORDING ON UNDOCK
If enabled, the VB400 will be prevented from recording for a pre-configured amount of time after it has been
undocked. This means it will ignore any gestures which would normally prompt it to record.

VIDEO SETTINGS
● VIDEO RESOLUTION
Select the quality of videos recorded on VB400s in this profile.
● FRAME RATE
Select the frame rate of videos recorded on VB400s in this profile.
AUDIO SETTINGS
● AUDIO PROFILE
Select the audio profile for videos recorded on VB400s in this profile, depending on whether they are primarily
recording indoors or outdoors.
● AUDIO CODEC
Select the audio codec for videos recorded on VB400s in this profile.

BLUETOOTH SETTINGS
● YARDARMTM HOLSTER AWARETM PERIPHERALS
Select the number of sensors associated with VB400s in this profile. You must also pair these sensors with the
user who will be operating the VB400.
● PEER-ASSISTED RECORDING
If enabled, when a VB400 starts recording, it advertises the recording state to nearby VB400s. Depending on the
device policy of those VB400s, they may also start recording as well.

CONTROLS
In this section, you can configure how long an operator must hold a button or how quickly they must double-click a button
for the VB400 to register the gesture. You can also configure how various VB400 buttons (Front button, Function button A,
Function Button B, Function Button C, and Slide) are mapped onto gestures (Press, Hold, Double click, Slide up, Slide down)
and actions. The actions are as follows:
● NO ACTION
Nothing happens.
● START/STOP RECORDING
The VB400’s recording state will change. If it was recording, it will stop recording. If it was not recording, it will
start recording.
● START RECORDING
The VB400 will start recording.
● STOP RECORDING
The VB400 will stop recording.
● SHUTDOWN
The VB400 will shut down.
● RECORD BOOKMARK
If the VB400 is recording, it will place a bookmark in the footage. This bookmark will be visible on VideoManager
when reviewing the footage.
● ENTER HUSH MODE
The VB400 will enter hush mode.
● EXIT HUSH MODE
The VB400 will leave hush mode.
● TOGGLE HUSH MODE
The VB400’s state will change. If it was in hush mode, it will leave hush mode. If it was not in hush mode, it will
enter hush mode.

MUTE AUDIO
The VB400 will stop recording audio.
● UNMUTE AUDIO
The VB400 will start recording audio.
● TOGGLE MUTE AUDIO
The VB400’s state will change. If its audio was muted, it will unmute. If its audio was unmuted, it will mute.
● ENTER SAFETY MODE
The VB400 will enter safety mode.
PLEASE NOTE: While in safety mode, the VB400 will be completely inert until the operator performs the pre-configured
gesture which will prompt it to leave safety mode.
● EXIT SAFETY MODE
The VB400 will exit safety mode.
● TOGGLE SAFETY MODE
The VB400’s state will change. If it was in safety mode, it will leave safety mode. If it was not in safety mode, it will
enter safety mode.

SHOW BATTERY STATUS
The VB400’s bottom LED will show the battery status of the body-worn camera. If it is green, the VB400 has a high
battery level. If it is yellow, the VB400 is running low on charge. If it is red, the VB400 is about to shut down due to
low battery.
The following actions are only visible if pre-record has been configured to start and stop manually, from the Recording
Behavior section:
● START PRE-RECORD
The VB400 will start pre-recording. The length of the pre-record period depends on the configuration in the
Recording Behavior section.
● STOP PRE-RECORD
The VB400 will stop pre-recording, and the pre-recorded footage will be discarded.
● TOGGLE PRE-RECORD
The VB400’s pre-recording state will change. If it was pre-recording, it will stop. If it was not pre-recording, it will
start.

The following actions are only visible if Manual has been selected from the Wi-Fi Connection dropdown:
● CONNECT TO WI-FI
The VB400 will attempt to connect to Wi-Fi.
● DISCONNECT FROM WI-FI
The VB400 will disconnect from Wi-Fi.
● TOGGLE WI-FI CONNECTION
The VB400’s Wi-Fi state will change. If it was connected to Wi-Fi, it will disconnect. If it was not connected to Wi-Fi,
it will attempt to connect.

The following actions are only visible if pre-record has been configured to start and stop manually, from the Recording
Behavior section:
● START PRE-RECORD
The VB400 will start pre-recording. The length of the pre-record period depends on the configuration in the
Recording Behavior section.
● STOP PRE-RECORD
The VB400 will stop pre-recording, and the pre-recorded footage will be discarded.
● TOGGLE PRE-RECORD
The VB400’s pre-recording state will change. If it was pre-recording, it will stop. If it was not pre-recording, it will
start.
Click Save Settings.

ONCE I’VE CREATED A DEVICE PROFILE, HOW DO I
APPLY IT TO A BODY-WORN CAMERA?

There are three ways to apply a device profile to a body-worn camera, depending on how your instance of VideoManager EX
has been configured.
SET THE DEVICE PROFILE AS A SYSTEM DEFAULT
You can set a device profile as the system default for all users on VideoManager. Only users with the correct permissions
(Assign device and Select device profile when assigning) can override this default. To do so:
1. Navigate to the Admin tab.
2. Select the Devices pane.
3. Click the Device Profiles section.

4. In the top right-hand corner, click Reorder Profiles.
5. Using the arrows, reorder the profiles until the requisite device profile is at the top of the list. This will make it the default.
6. Click Confirm new order.

When assigning body-worn cameras, this device profile will now be presented as the default. If a VB400 is assigned to an
operator with Single Issue with RFID or Permanent Allocation, and the operator is not part of a role with a different device
profile, their VB400 will receive the default device profile.
APPLY DEVICE PROFILES TO ROLES
Device profiles can also be applied to entire roles, which are then in turn applied to groups of users. This is useful if workers
in a particular division of your organization (e.g. security guards) need one device profile, while workers in another (e.g.
retail workers) should have a different one.
This process is necessary if you will be assigning body-worn cameras to operators using the Single Issue with RFID or
Permanent Allocation method - otherwise, those operators will always receive the system default device profile.
To apply a device profile to a role:
1. Navigate to the Admin tab.
2. Select the People pane.
3. Click the Roles section.
4. Click Go to Role next to the relevant role.

5. In the Default Device Profiles field, click +, and select the device profile.
6. Click Save Role.

 

APPLY A DEVICE PROFILE WHILE ASSIGNING A BODY-WORN CAMERA
Finally, if you are an administrator assigning the body-worn camera to an operator manually, or if you are the operator and
have the permissions to assign yourself a body-worn camera (Assign device and Select device profile when assigning), you
can apply the device profile at the same time as you assign the body-worn camera.
PLEASE NOTE: This method is only applicable if you will be assigning body-worn cameras with Single or Permanent Issue. If
you will be assigning body-worn cameras with Single Issue with RFID or Permanent Allocation, please see the two previous
sections.
To apply a device profile when you assign a body-worn camera:
1. Navigate to the Devices tab.
2. In the Search Devices pane, filter the body-worn cameras as necessary, and click Find Devices.
3. Click Assign Device.

4. In the Operator Name field, enter the name of the operator who will be using this body-worn camera.
5. From the Assignment Mode dropdown, select one of the following options:
● Single issue - the body-worn camera will be assigned to the operator for one trip. Once it has been docked,
it will become unassigned again.
● Permanent issue - the body-worn camera will be permanently assigned to the operator, even when it is
docked.
6. From the Device Profile dropdown, select the previously-created device profile.
7. Click Assign Device.

 

HOW DO I REPLICATE DEVICE PROFILES ACROSS
MULTIPLE INSTANCES OF VIDEOMANAGER EX?

If you have multiple instances of VideoManager EX, you can copy the device profiles from one instance to another. This is
useful if you have a Central VideoManager EX with multiple Sites (e.g. for satellite offices or remote workers), or a test
server.
MANUALLY EXPORT AND IMPORT ALL DEVICE PROFILES
If you would like to export all of your device profiles from one instance of VideoManager EX (e.g. a test system) into another
instance (e.g. a live system):
1. In the original instance of VideoManager EX, navigate to the Admin tab.
2. Select the System pane.
3. Click the Import / Export system config section.

4. In the Merge this configuration with target system section, click + and select Device Profiles from the dropdown.
5. Click Save Settings.
6. Click Export System Config in the top right-hand corner. The configuration will be downloaded to your PC’s default
downloads location as an XML file.
7. On the other instance of VideoManager EX, navigate to the Admin tab.
8. Select the System pane.
9. Click the Import / Export system config section.
10. Click Import System Config.
11. Select the previously-exported XML file and click Confirm.
PLEASE NOTE: Any device profiles on VideoManager EX which have the same names as the imported device profiles will be
overwritten.

 

MANUALLY EXPORT AND IMPORT INDIVIDUAL WI-FI PROFILES
If you would like to export one of your device profiles from one instance of VideoManager EX (e.g. a test system) into another
instance (e.g. a live system):
1. In the original instance of VideoManager EX, navigate to the Admin tab.
2. Select the Devices pane.
3. Click the Device Profiles section.
4. Click Export Profile next to the relevant device profile. It will be automatically downloaded to your PC as a JSON file.
5. In the other instance of VideoManager EX, navigate to the Admin tab.
6. Select the Devices pane.
7. Click the Device Profiles section.
8. Click Import Profile.

9. Select the previously-exported profile.
10. Click Import