Professional Documents
Culture Documents
Storage Body Cam
Storage Body Cam
1. DESIGN
As with other revolutionary products and technologies, many vendors have jumped
into the market, hoping to tap some of the billions of dollars that are already being
spent on BWCs. (Photo/iStock)
RELATED ARTICLES
8 body camera concerns police and the public need to know
How to deploy a smart, successful BWC program
4 concerns your BWC policy must address
RELATED FEATURE
This free PDF will educate police how to stay atop the evolving policies, training and technology
shaping law enforcement.
The earliest BWCs were typically “lipstick” cameras that were tethered to a
recorder/battery module by a cable. Better engineering and the understanding that
cops already have enough gear dangling off of them meant that the devices evolved
into a single unit, with some variations and options between brands.
The typical design today is a small device about the size of a deck of cards with a
camera facing outward in the upper corner or in the middle of the device. The
opposite face of the device may have an LCD display for reviewing the video, a clip
to hold it in place on the officer’s body, and/or controls to operate the recorder.
Some vendors may also place the LCD display on the outward-facing side, so
anyone being recorded can see exactly what is being recorded at all times.
The LCD display can be a nice feature, but it can also add cost, a slight amount of
bulk, and can decrease battery life. Some models have the option of sending video
to a synced smartphone via a wireless Bluetooth connection. Unless your officers
often have a need to review video immediately, choosing a model with no LCD
display may be a way to save money and battery.
2. CAMERA PLACEMENT
Some models have provisions for attaching a camera to the officer’s head or
shoulder, via an eyeglass frame, helmet, or ball cap clip, or an attachment to the
uniform epaulet. A camera coaxially mounted on the officer’s head can provide
more information than one on his chest, as it will show where the officer is looking,
and may give a better perspective on the environment. It also requires a tethering
cable.
Because we tend to move our heads more than our torsos, video from a head-
mounted camera can be shaky and disorienting. Testing and review of videos from
both body and head-mounted cameras makes it clearer which is best suited for
your application.
How the BWC attaches to the officer might have the least amount of technology
involved, but remains a very important factor. If the attachment isn’t secure
enough, cameras will be lost and possibly broken frequently. Spring-loaded clips
work well on belts, but not so much on shirt fronts. Every vendor seems to
approach this problem differently. One employs a vest tailored to look like a
sleeveless uniform shirt that is worn over the regular uniform, and also acts as a
body armor carrier. The BWC slips into a custom-made pocket under the placket,
with a plastic-reinforced hole for the lens. This is a novel and very secure way of
carrying the BWC, but also ties you to a single uniform vendor and may require a
costly new issue of carrier for every officer who will carry a BWC.
As with uniform fittings and choices, the method of mounting the BWC can be an
individual preference. If possible, field test proposed devices and get feedback from
the troops to ensure they will work as well as the vendor says they will.
4. BATTERY LIFE
Most BWC models have internal, rechargeable batteries that will power the
recorder for three to six hours.
This amount of battery capacity is necessary because the devices are usually
powered up for the entire duration of the duty tour, even if they’re not in record
mode. As with most modern in-car camera systems, BWCs usually have a “pre-
event” recording mode, where the last 30-120 seconds of video are saved in buffer
memory. When the officer activates the recorder, the contents of that buffer are
automatically appended to the front of the recording, though absent sound. Sound
is usually not captured by the pre-event buffer for privacy reasons, but some
vendors offer the option to record sound at all times.
No battery is 100 percent efficient, and all of them have service lives, usually
measured in charge-discharge cycles. For example, after 500 charge-discharge
cycles, the battery might have 80 percent of its original storage capacity. The
original battery capacity exceeds the time the BWC is likely to run so as to make the
battery still usable when its capacity declines.
Most devices recharge their batteries when they are placed into a charging dock,
which often also downloads the recorded video into an archive and erases the
recordings on the camera, so it’s ready for the next shift. A few may use a micro-
USB cable, such as is common in many consumer electronics. A full charge can take
anywhere between one and six hours.
5. STORAGE CAPACITY
Most BWCs have internal storage capacities of 16 or 32 gigabytes (GB). Like with all
other electronics, the ability to store a lot of data in a very small space has
improved dramatically. Most BWC recordings come in around 1 GB per hour,
although that can increase substantially if a higher resolution is selected. Standard
resolution is what you get on a non-HD TV screen, around 800 MB (0.78 GB) per
hour. A 720p resolution quadruples that size, while HD-level 1020p resolution is
sixteen times as much information. For most agencies, the standard or mid-level
resolution is enough for their needs.
The only time internal storage is likely to be an issue is if you have a situation where
an officer has to use the same BWC for multiple shifts without offloading the
recorded video to a server. This doesn’t happen often, but if it’s a possibility, you’ll
want to choose the largest internal storage capacity you can get.
6. ACTIVATION METHODS
When choosing a BWC, keep in mind that the user may be wearing gloves when
they need to activate the recorder, or they may be under intense stress, where fine
motor skills deteriorate. The activation switch needs to be something the user can
hit reliably under adverse conditions.
Some vendors have a provision for voice activation, so the officer can trigger the
BWC into record mode just by speaking a command. The voice activation software
is “trained” to the user’s voice, so the same command spoken by someone nearby
won’t activate the camera. If that voice system is operating, it also draws power
from the battery.
Newer BWC models are increasingly aware of their environment. Some will link to
an in-car recorder system, activating when the car system does (or activating the
car system when the BWC is triggered), or will power up when the car door opens.
Obviously, the in-car and BWC systems need to be compatible to make this work.
Some will start recording if internal accelerometers sense the officer running, if
there are violent movements (as would be the case if the officer was struggling with
someone) or if he or she goes flat on the ground. It isn’t a big reach to expect future
generations of BWC will be linked to a fitness bracelet or other device that monitors
the user’s heart rate or other stress indicator.
7. CREATING A NETWORK
Another innovation is the formation of a network with the patrol car and/or or
other BWCs in the vicinity. A network and the appropriate infrastructure (such as a
strong wide-area data network) allow recordings to be broadcast to the patrol car
and streamed to another car or to an operations center in real time. The operations
center might also be able to trigger the recorder remotely. If other BWCs are
included in the network, activation of one BWC could trigger activation of all the
others within a defined perimeter, giving multiple perspectives on the same
incident.
8. UPLOADING DATA
There has to be a way of getting the video recordings off of the BWC and into long-
term storage. Most vendors use a combination dock and charger where the BWC
resides when it isn’t in use. On being placed into the dock, a connected server
downloads the recorded video and any other data and transfers it to a local server,
or the cloud. When the data is downloaded and verified for integrity, the recordings
are deleted from the BWC. At the same time, the battery is recharged and the
device is made ready for the next user or next shift.
When an officer begins his or her shift, most systems have them log in to a
computer connected to the dock. The system assigns a BWC to that officer for the
shift, and encodes the officer’s name, badge number, and other data onto the
internal memory. This “tags” every recording with that officer’s ID.
Another method, not often used, is to transfer the video wirelessly via any Wi-Fi
connection the system has approved. This could be an opening for a security
problem, but the larger issue is the time it takes for a large video file to move over a
wireless connection. Hardwired connections are usually a better choice, but your
situation may make the wireless option better.
Because of the size of the video files that will accumulate, most vendors have a
system that stores the video in the cloud. The cloud is likely one or more servers
located at huge server/data “farms” owned by companies like Google and Amazon.
Unless your agency is one in a high-tech locale or some other place with very high-
speed internet connections, uploading that video is likely to create a logjam
between your agency and the internet. Most of the U.S. makes do with internet
connections averaging 11.4 Mbps, or megabits per second. If you have one of those
11.4 Mbps connections, uploading 1 GB of video will take about 14 minutes (there is
a useful transfer time calculator available here, and that assumes no other online
traffic during that time. Multiply that by however many cops will be using a BWC
every day. Keep in mind that your download and upload speeds can be very
different. To get an idea of what you’re dealing with, visit SpeedTest.org.
If you’re adopting a BWC system that uses the cloud, take into account this
bandwidth problem. Your internet service provider may be able to suggest some
solutions, including a bigger data pipe — for a fee, of course.
One possible alternative is to have officers take the BWCs home with them and use
their own internet connections to transfer the video while recharging the devices.
This method invites questions of security, as a user could conceivably delete video
that was unfavorable to him, and copy it for another use (such as posting it on
YouTube). Most of the BWC vendors incorporate safeguards to ensure against this,
but it still invites an additional risk.
9. UNDERSTANDING METADATA
Metadata is “data about data.” Most of us are familiar with digital photography, but
you might not know that nearly all digital cameras encode a significant amount of
metadata with each photo file. The metadata can include the model and serial
number of the camera, the exposure data, the time and date, and if the camera has
a GPS function, the location where the photo was taken.
Video metadata can include all of this information, and much more. As mentioned
above, most systems will tag each recording with the officer’s name or other
identifier. The system might also be able to capture direction of travel, speed, and
location sufficient to plot the physical path of the BWC on a moving map. If the BWC
is networked with other recorders, it could include what other cameras were in the
vicinity and whether they were recording.
Storage and management of video is the elephant in the room for any discussion of
a BWC program. Unless you have a very small agency with a short retention policy
on recordings, local storage is probably out of the question. Hard drive storage is
cheaper than ever before, but a 10-cop department will still fill up a one-terabyte (1
TB) hard drive ($30-$50, plus the computer it’s connected to) in a bit over six
months.
Your retention policy will have a huge impact on your storage requirements. If you
decide you need to keep everything indefinitely, multiply the scenario above to fit
the size of your operation. Know that buying new drives will be an infinitely
recurring cost, doubled by the need to have backup copies of everything.
Most departments decide eventually to use the cloud. It’s usually preferable to use
the BWC vendor’s video management solution, as opposed to trying a homegrown
method. The vendor is going to have a front-end user interface that will be easier to
use with more features than you can create locally. It will make the best use of
whatever features the vendor has built into its products, and it’s probably going to
be cheaper than other solutions.
The user interface is the indexing and viewing software you will be using to review
videos. It’s critically important that this software is something you’re comfortable
with and that it offers the features you need. If the software is difficult for you to
use, you’re going to be wrestling with it every time you need to see or copy a video.
Search options. How many parameters can you use to locate relevant video clips?
These might include an officer’s name, ID number, day, time, geo-coordinates,
incident or case number, type of incident (field interview, traffic stop, crime report,
etc.), length of clip, and others unique to your operation.
Chain of evidence. Security should also track every action by every user, so that
any change or copying can be tied to the person who did it. Users must be careful
about signing in to the software and then walking away from the computer to do
other things.
Viewing options. By default, videos usually play in a small viewing window, with
the perimeter surrounded by metadata. There should be an option to view the
video full screen.
Selective overlays. Most viewing software allows the user to overlay text on the
screen that provides time and date, officer’s name, speed, whether emergency
lights are on, etc. You should have the option to include or remove all of that
information with every video.
A retention policy governs how long you will keep each video recording before it’s
deleted to save space and storage costs. The vendor will likely have a suggested
retention policy, but this is something you will want to discuss with your
prosecutor’s office and risk manager. If you have a pay-as-you-go storage contract,
every retention decision is a compromise between cost and the risk of deleting a
record you might need later.
Some vendors offer an “all you can eat” storage plan, often folded into a
maintenance and service agreement. The vendor will charge you a fixed fee per
month per user, no matter how much video that user might create.
Deciding which option is best will depend heavily on your agency size, your
situation and needs, and on your retention policy. Most vendors estimate that each
officer/user will generate about 1 GB of video per day, on average. Multiply the
number of officer workdays in a month to get an idea of how much video data you
will be generating.
For example, say you have a small agency where you field three officers on day
shifts, three on evening shifts, and two on the overnight shift. That’s eight officer
workdays each day, or 240 in a month. It will take you a little over four months to
generate 1 TB (1024 GB) of video, assuming a 100 percent retention policy.
Amazon Web Services is the leader in online storage, and serves everyone from
Netflix to the U.S. Government. Their standard storage rate is $0.03 per GB/month,
with small price breaks as you start accumulating more video. At four months,
storage will cost you about $30 per month, increasing by around $7.00 each month.
A big advantage in using a massive service like Amazon is that your data is
guaranteed to be backed up, with the redundant copies probably existing on
different parts of the planet.
Storage is not the only cost associated with online video. You will also pay for
bandwidth, which varies by how much you transfer from storage to your local
computer. Expect to pay about $0.09 per GB downloaded.
Facebook
LinkedIn
Twitter
Print
Email
Editor's note: This is part two of a three-part series in which Government Technology
looks at the technology considerations for body worn cameras. Read part one here.
When the Chula Vista, Calif., Police Department started giving body worn cameras to
a handful of police officers, they quickly learned that a 30-minute video took about
800 MB of storage space. The department crunched the numbers and realized that if it
equipped every one of its 200 sworn officers with cameras, they could potentially
generate 33 terabytes of data every year, according to Police Chief Magazine.
When it comes to BWCs, data storage is the 800-pound gorilla in the room. Video, as
every CIO knows, is a data hog. And BWC systems can produce vast amounts of
video data, as well as the metadata to track and manage the video clips for retention
and chain of custody purposes. Data storage is a technology issue and it’s one that
CIOs try to address in the most cost-effective manner.
But in the case of BWCs, policy is inextricably linked to the question of storage.
Retention policies can play havoc with the portion of a BWC budget that’s dedicated
to storage. Some jurisdictions say non-evidentiary video should only be kept for 60 to
90 days. Some departments say it should be longer, others say less. The Oakland,
Calif., Police Department, which currently has 600 BWCs deployed, retains video for
a remarkable five years. As a result, storage needs have grown significantly over the
past couple of years and the department now captures on average almost 7 TB of
video data per month, according to Officer Dave Burke. And if a video becomes
evidence in a court case, the retention requirements can be even longer. “What if
there’s an appeal in the case 10 years down the road?” asked a CIO. “What are the
requirements and policies for handling those scenarios?”
Many cities, under pressure to implement BWCs, have found data storage and related
costs to be a major stumbling block. Last year, Baltimore Mayor Stephanie Rawlings-
Blake vetoed a BWC proposal after concluding that data storage costs and other
details were not sufficiently taken into account. Baltimore city officials estimated
video storage costs at as much as $2.6 million annually.
Experts agree that issues concerning privacy must be balanced with storage capacity,
transparency and state laws. The Police Executive Research Foundation (PERF)
released a report on BWCs in 2014 (Implementing a Body-Worn Camera Program)
that looked at existing BWC programs around the country and developed a list of key
lessons learned when it comes to data storage:
For the final point, PERF reported that police departments, legal advisers and
prosecutors were comfortable using third-party storage solutions, but to consider the
vendor’s technical capabilities and whether the system includes protections, such as
audit trails and backup.
The National Institute of Justice points out that as video becomes more important to a
police department, storage adjustments will need to be made. “The length of storage
time can cost numerous man hours in addition to the actual costs of the storage
device.” It goes on to say that advanced data storage systems can provide end-to-end
data management that includes safeguards to control data handling and assist in chain-
of-custody control.
Facebook
LinkedIn
Twitter
Print
Email
BODY WORN VIDEO AND RECORDS RETENTION
With the popularity and affordability of Body Worn Video (BWV) equipment, many OMAG members are
purchasing devices for their police officers. Members learn quickly that the expense of the equipment
purchase doesn’t compare to the cost of storing the video or data. OMAG Legal receives regular inquiries
regarding storage/retention requirements and issues when it comes to BWV. As a service to our members,
OMAG’s Legal and Risk Management Departments have developed this article addressing the most frequently
asked questions regarding BWV retention.
As of this writing, there is no legal obligation to store body (or dash) camera videos for any length of time. As
such, the decision to store or not store is left to the municipality subject to the requirements of State law. The
municipality should consider adopting a retention policy that takes into account the legal factors outlined in the
statutes discussed below. In particular, if there is video of a use of deadly force (whether it causes death or just
injuries or even where no one is actually hurt), those videos should be preserved (OMAG recommendation)
and should be sent to OMAG Legal for review. Videos depicting a use of force incident causing significant
bodily injury should also be preserved (OMAG recommendation). The Statute of Limitations for Civil Rights
claims is 2 years and there is a 6 month grace period to serve a Civil Rights suit after it is filed. For video
capturing incidents which may lead to a Civil Rights claim, a 3 year retention would be ideal and a best
practice.
The following Statutes are implicated when determining whether BWV videos should be preserved.
OMAG recommends that each municipality adopt policies on retention that take into account whether the
record is needed for current business transactions and, if not, whether the record has administrative, legal,
fiscal, research and historical value of records and then provide for their retention based on those factors.
OMAG’s opinion is that this Act applies to municipalities and would apply to body cam video, but imposes no
affirmative requirements on retention.
BWV CATEGORIES
Police Officers utilizing BWV devices must adhere to a department policy that not only governs the initiation
and termination of recording, but also the categorizing of the recording. At the end of recording, or end of
shift, the officer must choose if the video segments are critical, non-critical, or would be considered evidence.
For the purposes of BWV categories, a few examples of critical, non-critical, and evidence are listed below:
I. Critical
a. Vehicle stop where seizure and/or arrest is made
b. Injury to an officer or suspect
c. Use of force
d. Formal or administrative complaint/investigation
e. Or as determined by policy
II. Non-critical
a. Warnings
b. Tickets
c. Routine interactions with public
III. Evidence
a. Any images or video captured that an officer reasonably believes constitutes evidence in a criminal case
OMAG recommends a 3 year retention for a critical category and a 180 day retention for non-critical category.
Evidence should be maintained for the amount of time required by statute, until the case is adjudicated, or all
appeals have been exhausted.
Body Worn Video and Records Retention was written by Matthew Love and Kevin McCullough. You may
contact the authors at mlove@omag.org or kmccullough@omag.org . The information in this bulletin is
intended solely for general informational purposes and should not be construed as or used as a substitute for
legal advice or legal opinion with respect to specific situations, since such advice requires an evaluation of
precise factual circumstances by an attorney.
If you’re like many people involved in the criminal justice system, the police
who arrested you were wearing body cameras at the time of your arrest. Is
that possible for the police to turn that footage over to the prosecutor in your
case, and if so, can the prosecutor use body cam footage against you in
court? Here’s what you need to know.
State and federal courts have acknowledged that this type of footage can be
useful in verifying a police officer’s version of events. Therefore, it is
admissible in court and the prosecutor in your case can use it against you.
In some cases, body camera footage can be used to show that a police officer
acted improperly during your arrest. In a situation like that, your criminal
defense attorney will request to see the footage and may ask that it be
entered as evidence in your case.
By
TechTarget Contributor
Body cams generally include an HD camera with a microphone. Most body cams
have an on/off button for the camera and a separate button for the microphone to
accommodate differing state laws on audio recordings. Some designs feature
lights for dark environments and onboard storage or streaming video.
Related Terms
Microsoft Assessment and Planning (MAP) Toolkit
Microsoft Assessment and Planning (MAP) Toolkit is a free utility IT can use to determine
whether its infrastructure is prepared ... See complete definition
mobile app
A mobile app (or mobile application) is a software application developed specifically for use
on small, wireless computing ... See complete definition
Wien's constant
Wien's constant is a physical constant that is used in defining the relationship between the
thermodynamic temperature of a black... See complete definition
How College of Policing Guidance
Enables Body Worn Camera Abuse
Kevin Donoghue, solicitor, reviews the College of Policing guidelines on body worn cameras in light of a recent
court case.
By Kevin Donoghue, solicitor
For many years I have said that the College of Policing’s body worn camera (BWC) guidance is
not fit for purpose. In particular, I have railed against the idea that the police can be trusted to
use their cameras properly. A recent court report highlights the inevitable consequences.
Last week I read a shocking story by Neil Docking of the Liverpool Echo: “Bent coppers
covered up officer battering man in his home.”
The story is worth reading in full by clicking on the link above. (It opens in a new tab so you can
come back here afterwards.) It could be used as a case-study for police corruption and reflects
very poorly on Merseyside Police.
Darren McIntyre
Laura Grant
Lauren Buchanan-Lloyd
Garrie Burke
lied and lied after the victim was repeatedly punched and left pouring with blood.
His story includes details of:
Seven years I wrote this blog post: Why the Police Should Change Their Body Camera Policy
In it, I explained how the Metropolitan Police were trialling the use of body worn cameras. I
noted that:
It is expected that the body cameras will only be used when the police respond to incidents and
during stop & search operations, rather than during day-to-day interactions. The Commissioner
says this is because leaving the cameras on all the time would be ‘too intrusive’.
I urged the Met, then led by former Merseyside Police Chief Constable Sir Bernard Hogan-
Howe, to set a policy of recording every interaction with the public:
to counter suspicions that officers would deliberately not turn their body cameras on
noting that:
Other forces are watching with interest and are expected to adopt body cameras if the test is
successful.
That force applies the College of Policing’s 2014 guidance on body worn video. (It has its own
Body Worn Video policy which you can read here.)
We connect everyone working in the police and law enforcement to understand their
challenges.
We use evidence-based knowledge in everything we develop.
We help police officers and staff; researchers, academics and learning providers; the
international policing community; and the public.
We give a voice to professional policing on standards, skills and capabilities.
Here I refer to the College of Policing’s body worn video guidance instead of Merseyside
Police’s policy. This is because the College issues best-practice guidance for all national police
forces, including Merseyside Police.
Principle 4 – The operational use of body-worn video must be proportionate, legitimate and
necessary.
Principle 5 –Use of body-worn video will be incident specific. Officers will use common sense
and sound judgment when using body-worn video, in support of the principles of best evidence.
Operational considerations
Recording an incident – basic principles and techniques
The decision to record or not to record an incident rests with the user. However, users should
record incidents whenever they invoke a police power.
Under normal circumstances, all BWV users present at an evidential encounter, regardless of
the fact that other BWV users may be present, should record the incident. Users should always
take into account the circumstances and the people involved, for example, vulnerable persons.
Failing to record an incident may require explanation in court, although in some instances it is
not appropriate to make a video recording. In such cases users should record the fact in their
pocket notebook.
Users may not indiscriminately record entire duties or patrols. Recordings must be incident
specific (whether or not the recording is ultimately required for use as evidence).
All recordings can be used in evidence, even if it appears to the user at the time of the incident
that this is unlikely (eg, a stop and search with a negative result). All recordings should be
treated as evidential until it is confirmed otherwise. If it becomes obvious that the recording
will not be evidential, unless there are other extenuating circumstances, users should stop
recording immediately.
Users should capture as much evidence as possible (including the context of the encounter)
and should always try to record as much of an incident as possible. Users should begin
recording at the start of an incident or at the earliest opportunity thereafter, for example:
In order to comply with the DPA and HRA, wherever practicable, users should restrict
recording to the areas and persons necessary in order to obtain evidence and intelligence
relevant to the incident. Users should always attempt to minimise collateral intrusion on those
not involved.
And note this section:
Selective capture
The BWV user should record entire encounters from beginning to end without interrupting
the recording. There will, however, be occasions when the user may wish to consider
interrupting the recording of an incident. In such circumstances the user may decide to start
and stop recording at any point during an encounter. This practice is referred to as selective
capture.
For example, it may be necessary to stop recording an incident in cases of a sensitive nature or
if the incident has concluded prior to the arrival of the BWV user. In all cases the user should
exercise their professional judgement in deciding whether or not to record all or part of an
incident.
If the user chooses to interrupt or cease recording at an ongoing incident, they should record
their decision and rationale (if practicable in the circumstances) by making a suitable verbal
statement on the BWV material and also in a pocket notebook or other log.
Selective capture can also be used to describe the process of temporarily stopping and restarting
recording in order to bookmark (see bookmarking) the recorded material.
Selective capture never involves deleting images. There are no circumstances in which the user
can justify unauthorised deletion of any images that have already been recorded.
1. police officers have absolute and total discretion when to use their body worn cameras, subject to
certain requirements (like invoking a police power)
2. they should not leave cameras running and, instead, must target their use to specific events and
people
3. recordings must be treated as evidence (which means that they must be preserved unmolested)
4. police officers should capture as much of the incident as possible, ie. Start recording when
deployed or as soon as necessary to capture evidence. But this is open to interpretation, and
officers can start or stop recordings during incidents as they see fit.
The practical effects of some of this guidance can be seen in Neil Docking’s Liverpool Echo
report. Evidently, the officers used some of their training (described below in bold) before going
rogue:
The jury was told McIntyre, Grant and Buchanan-Lloyd all switched their cameras on at the
start of the incident, which they were trained to keep on, as it is key evidence.
However, Grant and Buchanan-Lloyd both turned off their cameras when things became violent,
which Mr Barton [the Prosecutor in the case] said was a deliberate attempt to prevent
independent evidence being recorded.
The court heard Grant hesitated then turned away from the violence to turn off her camera and
Buchanan-Lloyd did the same.
Buchanan-Lloyd later said in an interview that she and Grant discussed turning their cameras
off and whether they would say their batteries died, but decided this would be too suspicious.
In September 2020, a report by Cynthia Lum et al was published on the College of Policing’s
own website.
(This is the same site where police officers can read the body worn camera guidance used by UK
forces outlined above.)
The report described a meta-analysis of 30 studies considering the effects of body worn cameras
on policing. Most of the studies were based on police in the USA, but some focused in whole or
part on UK police forces.
Today, BWCs are likely the most rapidly diffusing technologies in modern police history.
Although it is difficult to determine how many BWCs are in circulation today, there have been
some estimates. In the United Kingdom, one assessment by a privacy watchdog group found that
over 70% of police forces had acquired cameras by 2019 and were rapidly moving toward full
adoption.
It found that in most forces where body worn cameras were issued officers had to use them:
a large portion of the agencies (83%) had official policies that requi
Body-worn cameras (BWC) have become a necessity in law enforcement agencies of
the present day. Rise in several incidents has brought forward a greater need for better
mechanisms to support the accountability of officers and assist in evidence collection.
In November 2018, a report by the Bureau of Justice Statistics (BJS), based off
metrics from 2016, over 47% of general-purpose law enforcement agencies had
acquired body-worn cameras; a number that rose to 80% for large police departments.
Besides enhancing evidence collection, body cams serve as a great tool to assist police
officers. They also improve the chain of custody by recording footage of physical
handling of evidence (or potential evidence items) at a crime scene.
With each device recording for entire shifts without delays or breaks, several terabytes
of body camera video storage are required.
This blog talks about the challenges faced when working with body cameras when it
comes to video storage as well as practical solutions for them.
Challenges faced
by Law Enforcement Agencies
(LEAs)
1. Expenses When Working With Body Camera
Video Storage
Incorporating body cameras calls for a big budget. Knowing a department may have
hundreds or even thousands of officers on the field, to have the gear dispatched to
each of them is definitely a challenge.
According to the official website of the City of New York, NYPD rolled out over
6000 body worn cameras during its body-worn camera program that started in April
2017 and spanned over the next two years.
Dispatching body cameras to officers isn’t the end of costs. With each officer that
using bodycams, there will be several terabytes of video data incoming daily. Each
officer’s shift will be recorded and saved. Hence, a tremendous amount of storage is
required for each video file.
However, in a list compiled by the Government of the City of Fort Collins, Colorado,
entailing facts on body worn cameras, a statement getting a foremost mention takes
the spotlight.
There are numerous reasons to choose either, but we will get to it later.
So, does your choice of video storage and management platform offer that level of
security?
Two of these are by the California Rules of Court and the Criminal Justice
Information Services (CJIS) Security Policy.
You would have to compliant with GDPR based off your region, and FedRAMP
based off your industry and prospects.
With all these compliance needs being a necessity, the question being raised is
whether your video storage platform meets these compliance standards?
Storing footage from these body cameras in their proprietary codecs results in
playback issues, especially when shared with prosecutors, defense attorneys, the court,
or other scenarios.
Therefore, the need to generalize all codecs and make them compatible with all video
players is a necessity.
With several hours of footage coming from each officer daily, a manual video-to-
video search is an impractical idea.
Not only should your body cam videos be more optimized for searches, but the search
itself should have advanced features to provide better accessibility and accurate
results.
The standard process is to store video on a certain platform, which acts as a storage
medium. Then, the video is exported to a platform with a redaction tool, gets
processed, and then saved it back to storage.
As apparent, this process is both lengthy and time-consuming; something which turns
out to cut down efficiency for law enforcers.
We need a platform that offers us video storage with a built-in video redaction
software that makes the job easier and less time-consuming.
However, body cam video recording transcriptions play a key role in several cases,
and act as valuable data itself.
A good example is the missing people and murder case of Brian Laundrie and Gabby
Petito from Utah in the later part of 2021.
The audio quality becomes a huge hurdle when the audio must be transcribed. The
task becomes even more difficult when the audio carries multiple languages, jargon,
unrecognizable terms, or other factors.
The transcription process can be made easier and more accurate, but the audio file
needs to be passed through a few processes that require different tools.
Things would be much simpler if the entire task could be performed on a single
platform.
The solution to this issue it to make a conversion to Apple’s HLS (HTTP Live
Streaming) protocol. This is extremely necessary, as it makes the video file
compatible with all existing browsers and video streaming players.
But what can be possible solutions for these problems? Let us investigate these.
Cloud Storage
Video is a medium of data known for excessive amounts of data consumption. With
video qualities forever increasing, such as better resolutions thanks to camera
technology with greater megapixels and HDTV, the demand for greater storage has
followed.
Adding additional storage media has its limitations. Moreover, there are several risks
in terms of security and data loss.
This option is more feasible as it eliminates several negative factors when working
with disparate, local storage systems.
Cloud storage also enhances accessibility. The video content is stored on the cloud
can be remotely accessed by officers anywhere.
By utilizing cloud storage, we cut down the costs of locating evidence data on local
storage and physically transporting video evidence from one location to the next.
A third solution is to go for a mix of both – a hybrid model. Local storage holds
frequently accessed video content while the rest is stored on the cloud.
Security
Data security is also one of the primary concerns when working with body camera
video storage. The storage medium or service provider chosen must enforce measures
to keep data secure.
Bodycam videos could hold crucial evidence and confidential data. Any form of
cybersecurity attack could prove to be chaotic.
You also need to ensure that the videos stored on a storage medium are secure when
in transit, during playback or retrieval. Therefore, the service must incorporate
a secure video streaming platform with SSL/TLS encryption to protect video from
“man-in-the-middle” attacks and similar threats.
Transcoding
There is also an issue of compatibility or playback for any video file with bodycam
video storage.
The best solution at hand is to transcode it into a generalized codec with varying
bitrate frequencies to allow them to be playable on all mediums and under all
conditions.
Generalized codecs will be device and software agnostic, hence making it easier to
stream evidence on the organization’s own systems, or those with the legal bodies it is
shared with, such as courts.
Read more on what other practices should you consider with our 5 Tips On How
To Present Video Evidence In Court
The platform could provide access to cloud storage, be it their own or through a
partner’s integration, with added measures for security. Moreover, a system such as
that would have built-in mechanisms to assist you in automatically transcoding and
tagging video content.
A DEM system would not be limited to that, however. It will provide you with exactly
what you need when it comes down to handling your stored video content.
1. Bulk Ingestion: Bulk ingest digital evidence from any source such as Bodycams,
Dashcams, and CCTV Cameras, enabling evidence collection and segregation
through multiple, autonomous portals.
2. Integration: VIDIZMO’s device agnosticism allows massive possibilities for
integrations and ingestions. Integrate with your existing IT applications, such as
CAD, RMS, and CMS systems. Integrate with SSO for authenticated access and
interoperability and much more.
3. Accessibility: The use of a web app makes evidence viewable and accessible through
all devices.
4. Secure Evidence Sharing: Leverage a broad range of controls for end-to-end
evidence security and privacy. Ensure the highest level of protection for your digital
evidence using a robust set of security features and functions.
5. Artificial Intelligence: Make the use of AI to automate processes such as redaction,
transcription, translation, analytics generation and more.
6. Translate & Transcribe: Automatically transcribe audio and video evidence
simultaneously in 4 languages, or one out of around 40 in a single iteration.
Similarly, translations are available in over 50 languages.
7. Integrity of Evidence: Verify the originality and integrity of your evidence files
with the standard SHA-3 cryptographic hash function. This detects the presence of
any tampering and alerts the system and individual that evidence is assigned to.
8. Flexible Deployment: Deploy the solution as SaaS in Azure or AWS Cloud
(Government or Commercial), in an on-premises data center or in a hybrid
infrastructure.
9. Meeting Compliance Policies: Meet compliance requirements, such as CJIS,
FedRAMP, GDPR, HIPAA, ADA, DoD, CRoC, FOIA and more, through a wide
variety of features as well as through project hosts and partners.
VIDIZMO DEMS’ set of diverse features are not limited to what we have mentioned
above, however. There is a lot more that you can explore by paying a visit to our
website or directly exploring the features of the Digital Evidence Management
System.
WE OFFER MUCH MORE
SEE ALL FEATURES!
CONTACT US
Or test out the product yourself with a free trial!
Table Of Contents
1. Then Why Are Body Worn Cameras Not Incorporated Statewide?
2. Challenges faced by Law Enforcement Agencies (LEAs)
3. What Can Be Done To Solve These Problems?
4. A Complete Solution – A Digital Evidence Management System
5. VIDIZMO Digital Evidence Management System
Related Articles
VIDIZMO Whitepapers
←
→
1
2
3
4
Post a comment
First Name
Last Name
Email Address
Comment
VIDIZMO is committed to protecting and respecting your privacy, and we’ll only use your personal information to administer
your account and to provide the products and services you requested from us. From time to time, we would like to contact you
about our products and services, as well as other content that may be of interest to you. If you consent to us contacting you for
this purpose, please tick below to say how you would like us to contact you:
You can unsubscribe from these communications at any time. For more information on how to unsubscribe, our privacy
practices, and how we are committed to protecting and respecting your privacy, please review our Privacy Policy.
By clicking submit below, you consent to allow VIDIZMO to store and process the personal information submitted above to
provide you the content requested.
Submit Comment
About
VIDIZMO offers two products, a Gartner-Recognized YouTube-like platform
EnterpriseTube, and the IDC-Recognized Digital Evidence Management Solution for
law enforcement, along with other standalone video solutions like Redaction.
VIDIZMO solutions fully utilize and integrate with customer’s IT investments such as
SSO, Hyper-V, VMWARE, Cloud, Wowza Steaming Engines, Wowza Cloud, ECDN,
SharePoint, or other Content Management Systems, to provide end-to-end
enterprise video, digital media asset & evidence management solutions.
LEGAL
Privacy Policy
Terms of Use
Security & Privacy
Compliance
Agreement and Terms
Subscription Service Agreement
Request Subscription Change
Resources
About Us
Case Studies
Blog
Write For VIDIZMO
Videos
Support
Whitepapers
Press Releases
Careers
Helpdesk
Service Status
All Resources