How to mitigate storage troubles of body worn cameras?

Body worn cameras are mainly being used by federal security agencies to record their day to day activities, experiences and interactions with common populace. On seeing the success of their implementation, US Government is planning to deploy them in all 50 states of America.

However, the difficulty with body worn cameras implementation is striking the balance between privacy rights, cost of operations, and the collection of acceptable video evidence. Legislators, police departments, police officer unions and other interested groups all try to draft policy that strikes this balance. The result is a long list of rules dictating when the officer needs to record the evidence and when to avoid it.

Then there is the issue of retention, which generally keeps all recorded video for a minimum of 30-60 days, with incident relevant videos kept for longer periods, say for 1 year to forever.

Keeping aside the policy variants, let’s do some calculations for storing video recorded by body worn cameras.

Suppose 2 hours of video per officer per 10 hour shift is recorded. Say the video is being recorded at 720P resolution and 30 frames per second. Then the resulting video file will record 2.472 GB per hour or 4.944 Gigabytes per shift.

Generally, all videos are saved for 30 days. And out of that 6% of those videos is deemed to be potential evidence and so is retained for 1 year. 2% of video becomes part of a case file and must be retained for 5 years.

Then imagine how much video storage will be required for storing evidence gathered by mid size agency with 60 officers who work in 3 shifts per day with 20 officers per shift.

Around 297GB of data will be generated by the officers on daily basis. So, to store the data recorded for 30 days over 8.7 terabytes of video storage capacity will be needed per month.

Once, all this video is recorded, agencies have to store it, protect it as evidence following a chain of rules, make it search recipient, and provide it to various constituencies in either raw or encrypted form to protect privacy.

Regardless of how you store your video, you will need to purchase the cameras, which cost from $400 to $1,000, depending on the supplier. Then you will need a docking station, which can cost an additional $50 to $200 per port. These costs are fixed for both local storage and cloud storage architectures.

Hence, how to mitigate storage costs in body camera deployments?

You can opt for either a local storage appliance or a hybrid appliance which keeps hot data on premises and moves cold or infrequently accessed data to cloud.

DNF Security is one such company which offers integration of cloud services in its Falcon series of video storage appliances. So, security agencies using Falcon series of recording and storage appliances can use on-premises storage for recording all the hot data. For archival purposes, they can use Cloud Connection which is a secure cloud storage platform offered by DNF Security.

By choosing DNF Solution for recoding video evidence from body worn cameras, security agencies can mitigate costs associated with increasing storage costs.

The agencies can buy a single fault tolerant and highly redundant DNF Falcon Video storage appliance and then integrate it to DNF Cloud Connection. All frequently accessed data can be stored on the appliance and the cold data can be moved to cloud. Users can pay for the cloud capacity as per their usage.

Remember, DNF video storage solutions are available in a minimum 2TB storage capacity and a maximum of 288TB capacity. So, capacity issues will never trouble you and your agency in body worn cameras implementation.

To know more click on DNF Security solutions web link

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s