B08 - Attachment #6 - DEMS Statement of Requirements v.10 (20191008).docx

Enterprise Digital Evidence Management System (DEMS)

Enterprise DEMS Statement of Requirements

CONTROLLED//DISSEM-FEDCON

Enterprise Digital Evidence Management System

STATEMENT OF REQUIREMENTS

TABLE OF CONTENTS

II. Procurement Objective

III. Fee and Payment

IV. Procurement Prerequisites

A. Service Requirements

B. 508 Compliance

C. FedRAMP

D. Software as a Service (SaaS) Model

E. Bid / Price Schedule

F. Project Approach

G. Organization Chart & Staff Qualifications

H. Security Considerations

I. Place of Performance

J. Period of Performance

K. Technical Response / Submission Requirements

I. Introduction

The purpose of this document is to propose a solution to satisfy an organizational need of the Department of the Interior (DOI). Over the past decade, technological advancements and societal perceptions have advanced expectations of citizens that Law Enforcement (LE) officers be able to document with video their interactions with the public. U.S. District Attorneys encourage LE officers to provide video evidence as this type of evidence is incontestable, is influential with juries, and often expedites judicial processes. LE officers’ perceptions of Body-Worn Cameras (BWC) have also increased as officers recognize the value of BWCs to assist with evidence collection and protect officers from fraudulent accusations.

The digital video collected by LE camera systems requires a significant digital storage capacity. The Federal Data Center Consolidation Initiative (FDCCI) restricts federal departments from purchasing additional data infrastructure, which places a significant burden on DOI LE officers to discern their own storage and management solutions. Bureaus operating their own independent platforms and policies puts the Department at greater risk of potential violations of federal IT security and PIA violations.

The Statement of Requirements (SOR) provides contextual background and justification for the procurement of the proposed solution. The SOR also details costs associated with the procurement and outlines technical specifications for the hardware, software, and services requested by the National Park Service (NPS). NPS is the procurement lead for this enterprise DOI solution, and will be seeking a solution which satisfies the needs of each of the law enforcement organizations within DOI. For the remainder of this document, Bureaus will refer to the law enforcement programs within, but not limited to, the following DOI Bureaus: NPS, Bureau of Land Management (BLM), Bureau of Indian Affairs (BIA), and Fish and Wildlife Service (FWS). This document will be used to inform the Request for Proposal (RFP) process by aiding to the clarity of information provided to industry vendors on the products / services requested by NPS. This will help to ensure responses from vendors provide adequate information for the Department to make the best informed decisions in the vendor selection process.

A. Summary The DOI NPS, in conjunction with the Office of Law Enforcement and Security (OLES), has developed requirements for an integrated Digital Evidence Management System (DEMS) comprised of Law Enforcement (LE) Body-Worn Cameras (BWC), in-vehicle cameras, and cloud-based evidence management software. This enterprise DEMS solution will resolve current issues expressed by DOI LE officers with the challenges of storing and managing digital evidence captured on LE camera systems, and will be made available to all bureaus.

NPS will ensure the evidence management software is compatible with the Incident Management, Analysis, and Reporting System (IMARS). In conjunction with IMARS, the cloud-based application shall serve as the System of Record for uploading, managing, and storing all law enforcement related in-vehicle, body-worn, and surveillance camera evidence collected as part of law enforcement investigations and operations. By integrating media management and metadata with an interface to the DOI IMARS application, the Department provides law enforcement agencies a single solution which consolidates IT and governance resources, and aligns with Departmental initiatives, as well as industry standards and best practices. This document represents the collective functional requirements to support the business need for secure, reliable, and consistent collection, storage, management, and modification of videos and other media collected from a variety of electronic devices in use in the DOI’s law enforcement programs.

B. Background DOI has the responsibility to manage federally owned resources, protect the environment, prevent, detect, and investigate criminal activity, and manage visitor use and protection programs. This requires the identification, collection, analysis, management and reporting of information related to incidents, which are defined as any occurrence that requires documentation. Collection, analysis, and management of an increasingly large amount of video footage from body worn cameras is an emerging requirement being addressed by this initiative.

A variety of body worn cameras have been tested and are in use throughout the law enforcement programs in the Department. The Office of Law Enforcement and Security (OLES) has drafted policy on the wear and use of cameras, and is establishing a Department-wide technology program to support the storage and management of video files collected by officers and agents. It is anticipated that Departmental policy and support of the technical solution will encourage increased wear and use of video in law enforcement programs, where feasible and appropriate.

The Incident Management Analysis and Reporting System (IMARS) provides a Department-wide system for information collection on incidents and cases. Incident reporting, investigations, and case building are completed in the DOI IMARS system of record. Evidentiary information related to incidents and cases created in IMARS require retention schedules based on the severity of the crimes involved. Evidence collected as video will be managed on media servers and linked to incidents created in the IMARS system, and will be accessible through the IMARS application.

To meet the DOI’s media management requirements as well as comply with the DOI Inspector General’s 2018 report on BWC policy and practices, it is the intent of NPS and OLES to coordinate a solicitation to procure turnkey, end-to-end DEMS solution. This will include a cloud-based Software as a Service (SaaS) solution that provides a single, integrated platform for fully and seamlessly automating the upload, storage, notifications, and management requirements outlined in this document. A single vendor which provides the turn-key solution for the LE camera systems, cloud services, software, training, technical support, and maintenance package to support the Department-wide program is strongly preferred.

This integrated, enterprise solution should prohibit data tampering, editing, and copying. The data storage system should also include protections against tampering with the data prior to downloading, thereby alleviating any concerns that officers will be able to alter or delete recordings prior to downloading. The storage system should also have a record of who accesses video data, when, and for what purpose, including a built-in audit trail, thus helping to preserve the chain of custody. The data storage system should also have a reliable backup system that preserves recorded data.

II. Procurement Objective

NPS seeks to acquire a turnkey, end-to-end DEMS solution comprised of an integrated system of BWCs, in-vehicle cameras, and cloud-based evidence management software. The successful vendor will provide a FedRAMP* moderate compliant, SaaS model which is scalable and flexible to meet the diverse requirements of the DOI Bureaus. Additionally, the successful vendor will provide the necessary services required to fully deploy and implement all procured products and services in a timely manner. Prospective vendors will be assessed according to the attached Evaluation Criteria.

*Note: The Contractor is responsible for any and all costs associated with achieving a FEDRAMP ATO.

*Note: If and ATO is not obtained within the first year the Government is not likely to exercise any options associated with the contract.

III. Fee and Payment

The national Indefinite Delivery / Indefinite Quantity (IDIQ) contract provides an opt-in for bureaus and units that want to participate. Mandatory body worn camera programs are not required.

IV. Procurement Prerequisites

A. Service Requirements Vendor will be required to provide initial systems training to users, administrators, and internal Department trainers. Additional services required include, but may not be limited to, account management, help desk support, maintenance support, and acquisition support for new, next release, lost, and damaged major end items and components.

The vendor is to provide a project/deployment manager to aid the bureau(s) in designing and implementing the deployment schedule.

B. 508 Compliance Section 508, an amendment to the United States Workforce Rehabilitation Act of 1973, is a federal law mandating that all electronic and information technology developed, procured, maintained, or used by the federal government be accessible to people with disabilities. Successful vendors must conform to the U.S. accessibility standards of 36 CFR 1194. The vendor must provide an Accessibility Conformance Report (ACR) for the evidence management system of this acquisition, and the ACR must be based on the Voluntary Product Accessibility Template Version 2.2 provided by the Information Technology Industry Council (ITI). The VPAT is a reporting format that enables businesses to document product conformance with relevant accessibility standards, and assists government contracting officials and other buyers in identifying commercially available information and communications technology with accessible features.

C. FedRAMP Compliance The Federal Risk and Authorization Management Program (FedRAMP) is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. The solution must be FedRAMP moderate compliant. Vendors must demonstrate FedRAMP ready, in process, or authorized status for both the Infrastructure as a Service (IaaS) and Software as a Service (SaaS). A FedRAMP and DOI compliant Authority to Operate (ATO) are required prior to going into production. Vendors would need to submit a deployment schedule that supports meeting the ATO requirement in advance of BWC/DEMS deployment. FedRAMP statuses are defined as follows:

· FedRAMP Authorized means the service has either a Provisional Authorization to Operate (P-ATO) via the Joint Authorization Board (JAB) or an Authorization to Operate (ATO) by an Agency and is available for use by an Agency (by leveraging the existing ATO or P-ATO).

· FedRAMP Ready means the cloud service provider (CSP) has completed a Readiness Assessment Report (RAR) that has been approved by the FedRAMP PMO. This indicates that a CSP is likely to attain a JAB P-ATO an Agency ATO. While not a guarantee that the CSP will become authorized, the government has a clearer understanding of a provider’s technical capabilities before the assessment process begins so there is a greater likelihood of success in the authorization process.

· FedRAMP In- Process means that the service is in the process of being reviewed for a JAB P-ATO or Agency ATO.

D. Software as a Service (SaaS) Model SaaS is a software distribution model in which applications are hosted by a vendor or service provider and made available to customers over a network, typically the Internet. Unlike traditional packaged applications that users install on their computers or servers, the SaaS vendor owns the software and runs it on computers in its data center. The successful vendor will provide a SaaS solution allowing Bureaus to purchase licenses to utilize the software.

E. Bid / Price Schedule A bid schedule template is included in the RFP, and vendors are required to include a completed bid schedule in response to the RFP. The intent of the bid schedule is to provide a comparison of major components. Vendors should also include a comprehensive price list of all other items to include peripherals and/or minor components.

F. Project Approach The project approach provides an introduction and overview of the proposer’s phased implementation plan to include the proposer’s management plan, list of general objectives, work breakdown structure, and a brief explanation of the methodology to be used. The project approach should clearly delineate what work will be performed by the proposer and what will be performed by any subcontractors, if applicable. All responses must be complete and unequivocal. The plan shall identify meeting requirements for DOI related to project implementation, purpose of meetings, and a description of required attendees.

G. Organization Chart & Staff Qualifications The proposal shall detail the organization structure of the project implementation team, and provide resumes and relevant experience of key staff members. These should clearly demonstrate proposer’s qualifications to perform the project activities described in this RFP. Include the names of customers served for any item on the resume where “Project Manager” is listed as a duty.

H. Security considerations

1. Contractors and subcontractors must be U.S. citizens. Contractor personnel are required to have a Federal government-issued personal identification card before being allowed unsupervised access to a DOI facility and/or information system. All contractor and subcontractor personnel who will require physical and/or logical access for performance of work under this contract will need to be identified. The following forms, or their equivalent, may be used to initiate the background and/or credentialing process:

a. OPM Standard Form 85 or 85P

b. OF 306

c. Fingerprint card (local procedures may require the fingerprinting to be done at a police station; in this case, any charges are to be borne by the contractor)

d. Release to Obtain Credit Information

e. PIV card application (web-based)

2. If an individual has already been credentialed by another agency through OPM, and that credential has not yet expired, further investigation may not be necessary.

3. At a minimum, a National Agency Check (NAC) will be conducted to verify the identity of the individual applying for clearance. The DOI will determine the appropriate background (NACI, Tier 3, or MBI).

4. Due to the nature of the contract, contract staff will require access to Bureau networks and hardware. Each Contractors’ staff member will have to accomplish the following to attain access:

a. Annual IT Security Test (if applicable)

b. VPN request form (also identifies level of access)

c. Bureau or DOI Computer User policy (read and sign)

I. Place of performance In general, work will be conducted at the Contractor facility. The SaaS is operated and maintained in a secure, cloud hosted environment in accordance with FedRAMP standards, and therefore will not require a sustained, on-site presence of Contractor personnel at user locations.

The LESES Division of the NPS is located within the Main Interior Building (MIB). MIB address: 1849 C Street, NW, Room 2560, Washington, DC 20240.

All Contractor personnel assigned and billed to the SOR shall be subject to the Personnel Security Requirements, Personnel Qualification Requirements, and Conflict of Interest/Procurement Integrity Requirements set forth in the SOR.

The day-to-day supervision and direct control over the work performed by on-site Contractor personnel will be the sole responsibility of the Contractor.

J. Period of Performance The qualified selected vendor shall provide a Service Level Agreement (SLA) which includes service on equipment, hardware and software for a base year plus four (4) option years.

V. BWC Requirements A. General Requirements

1. Body worn cameras shall be black in color and capable of recording digital colored video/audio from an officer's point of view. Total quantity of 35 initially with potential to purchase additional units in future years.

2. Mounting: Cameras should have multiple mounting options to accommodate varying uniformed officers, plain-clothed officers, and tactical field situations. Examples include, but are not limited to, lapel, shoulder, eyeglasses, cap, helmet, holster, button shirt, zipper shirt, utility belt, etc.

3. Environmentally Durable: Devices shall be rain, wind, fluid resistance. Able to operate in temperatures ranging from -10 F to 120 F, be dust and dirt resistant, lens scratch resistant and the device must meet a 6-foot drop test requirement. In addition, the device shall be conducted energy device resistant.

4. Ease of operation: Cameras should be easy to power activate/deactivate and record activate/deactivate as needed with a single switch/button.

B. Camera Operational Requirements

1. Must possess a minimum 142-degree field of view.

2. The video image shall be in full color.

3. The camera shall have low light capability of <= .I lux.

4. There shall be a minimum of 16 GB internal/integrated memory.

5. Minimum video graphics array (VGA) resolution (640 x 480 pixels).

6. Minimum recording speed of 30 fps.

7. Minimum of 30 second pre-event recording configurable up to 2 minutes.

8. Camera must have auto-activation recording capability.

9. Bluetooth capability is preferred.

10. Camera must have audio recording capability.

11. GPS capability is preferred.

12. Officers must have the capability or option to view, categorize and annotate the recorded video on scene.

13. The camera must have an initial standby battery life of 12 hours without recharging or additional batteries.

14. A minimum 5 hours of record time.

15. Recharge in less than 8-10 hours.

16. Multiple charging capabilities to include docking station and USB cable.

17. Video/audio files shall be tagged with date/time.

18. Camera equipment must have a five (5) – year warranty.

19. Camera equipment shall come with upgrades at 30 months and at 60 months, (or other identified periods) at no extra cost to DOI.

VI. In-Vehicle Camera Requirements A. General Requirements

1. In-vehicle cameras be of high quality, durable, and be equipped with automatic activation triggers, to include light-bar or siren activation as well as reaching a specified vehicle speed. Automatic activation of BWC triggered by in-vehicle camera activation is a preferred capability. Camera system should be capable of recording high resolution digital colored video, be equipped with internal microphone, and capture video image to the vehicle front and rear.

2. Mounting: All accessories required for in-vehicle camera installation will be provided by vendor. Vendor will provide necessary instructions for vehicle mounting and installation assistance as required.

3. Environmentally Durable: In-vehicle camera systems, to include battery and power units, should be capable of operating and being stored safely in extreme temperatures ranging from 0 F to 110 F. Systems should also be resistant to dust, dirt, and moisture.

4. Ease of operation: Cameras should be easily activated, both manually and automatically, and allow for easy download of digital video by non-technical users.

B. Camera Operational Requirements

1. Must possess a minimum 120-degree field of view with both front and rear cameras.

2. The video image shall be in full color.

3. The camera shall have low light capability of <= .1 lux.

4. Night recording capability is preferred. Infrared capability is preferred.

5. Must possess audio recording capability. Internal microphone is preferred.

6. Minimum recording speed of 30 fps.

7. Video resolution: 1080P

8. Minimum 12 hours recording capacity.

9. Minimum 18 hours of recording time under default resolution setting.

10. Ability to capture still photos.

11. Possess a minimum 30 second pre-event recording feature (preferred).

12. Possess Wi-Fi capability.

13. Bluetooth capability is preferred.

14. Camera must have a minimum of 2 hour backup battery time.

15. Full battery recharge time must be 12 hours or less.

16. There shall be a minimum of 16 GB internal/integrated memory.

17. Camera should have GPS capability with the ability to embed GPS coordinates in recorded video.

18. Must operate under internal vehicle power.

19. Video/audio files shall be tagged with date/time.

20. Integration capability with officer BWC is preferred. Preferred BWC - in-vehicle camera interaction range is 50 feet or greater.

21. Manual activation capability is required. Alternative preferred methods of activation include:

a. BWC activation

b. Emergency lights

c. Speed setting

d. G-force reading

22. In-vehicle camera must have a 1 year warranty.

VII. Digital Storage Requirements A. Infrastructure Requirements

1. The System’s video must be of evidentiary quality for court and to be tactically useful for investigative purposes.

2. Create a fully secure Digital Evidence Management System for BWC video, in-vehicle video, crime scene photos, audio interviews, 3rd party video, smartphone video/audio, etc.

3. A cloud-based, SaaS solution is required.

4. The System must be compliant with Criminal Justice Information Services (CJIS) requirements.

5. Vendor must have at least one secondary hosting facility, with failover, in the event that the primary hosting facility fails or is not operational via the internet.

6. All primary servers and / or failover sites shall be located in the United States.

7. Web-based and accessible from any web-enabled computer, laptop, or handheld device.

8. Provide mobile app technology for upload, tagging, and basic operational functions.

9. Provides locally installed software, browser plug-in, or other technology to facilitate the file transfer of large files sites with poor connectivity; software that can be installed on any machine or device is preferred.

10. Does not require a client installation for the upload, download, access, copy, or share of media.

11. Scalable to increasing demands by bureau, and increasing number of bureaus and offices.

12. Configurable software, flexible to enable both standardized requirements across the Department, and unique requirements within the Department’s various bureaus and programs.

13. Through an Application Program Interface (API), interoperable to interface and automatically sync with the DOI’s IMARS and allow linking from the Department’s law enforcement records system into the media management system.

14. Provide account-based, unique user, two-factor authentication.

15. Provide separate and secure backup of all data stored in the operational system.

16. Backup redundancy must be immediately accessible by the same user interface as the operational system; if this is not the case, restoration to an active database must be achievable within 24 hours.

17. Provide for disaster recovery, disaster recovery planning, and disaster recovery testing.

18. Provide for secure long-term or permanent archival of specific files which retains file integrity and all important metadata associated with the file.

19. Provide for 24-48 hour retrieval of files, if archived off-site.

20. Ability to restore archived files into the active database.

21. Support up to 3,000 current users and 500 simultaneous users.

22. Supportable by local IT staff, as required.

B. Digital Storage Capacity Estimates

1. Operational/Active Files

a. Data requiring upload is estimated at ~1.5TB/officer/year

i. BIA ~650

ii. BLM ~250

iii. BOR ~30

iv. FWS ~700 (RLE only has shown interest, ~350)

v. NPS ~2000

vi. USPP ~650

b. Data requiring storage beyond a 30-90 day retention period is ~10%

c. Backup Files

i. Mirror Operational Files

ii. File Archival and Retrieval

a. May be a limited requirement, based on the ability to archive files in the IMARS environment.

C. Upload and Transmission Requirements Comment by Michael Reimers: I am not sure I am seeing anything about legacy systems needing to be integrated into the upload and transmission requirement Comment by Scott Schroeder: Added legacy user para./line C.17.

1. Upload of video to the System should require minimal User interaction (e.g. dock, plug-in device or wireless and files are uploaded).

2. Ability to upload a minimum of 800 videos simultaneously.

3. Ability to put files for upload in queue.

4. Provide for secured wireless or wired upload from any plug-in device, (vendor should provide recommendations for device integration).

5. Enable use of standardized docking stations for automatic and unattended upload of files.

6. Provide secured docking stations and/or devices to manage the seamless upload of files to the database during the officer’s off-duty hours between shifts.

7. Provide for holding or parsing of packages before or in transmission to enable bandwidth-sensitive upload of large media files.

8. Ability to securely upload a file from any connected device, in any common file format (nonproprietary), without alteration.

9. Ability to package and export any file in its original format, as well as a standard format.

10. Ability to encrypt and validate the integrity of the media file from the device at the time of upload, and retain the raw, unaltered media throughout the transmission and storage of the file.

11. Automated time/date stamping of video and automated or manual tagging of associated:

a. Officer

b. Unit

c. Incident number

d. Evidence

e. Sensitive/Secure

12. Ability to quickly bulk load and tag files with common metadata.

13. Ability to select and drag and to copy and paste files from a computer or other device into the system upload queue.

14. Ability to work on and share a copy of the record in the system, without touching or risking integrity of the original file.

15. Ability for basic file manipulation and saving of copies, to include:

a. Cut and paste

b. Crop

c. Zoom in/ Zoom Out

d. 360 degree rotation

e. 3D rotation

f. Filter

g. Enhance

h. Light

i. Opacity

j. Black and White

16. Ability to print photos and reports to a local printer.

17. Vendor will work with DOI to accommodate the upload of digital data from legacy cameras of competing brands into the vendor’s evidence management software.

D. Availability and Access Requirements

1. Access to the system will be role-and permissions-based, as well as unit-or group-based.

2. System software must recognize a device and associate the device with the officers assigned to the device. Metrics on officer uploads, downloads, GB of data, etc. must be tracked and available.

3. Roles, permissions, and units are pre-defined, and easily assigned by system (or other appropriate level) administrators.

4. Users can have multiple roles and units within the system, with the ability to switch between roles.

5. Access to individual folders, files, or parts of files can be further secured (hidden) by users using access control features.

6. Ability to share or secure specific files to specific users of the system, for a specific or unlimited period of time.

7. Ability to securely email or share via internet a link to non-users for viewing specific files, for a specific period of time (must integrate with BisonConnect, Gmail, Outlook, others)

8. System availability must be 24 hours a day, 7 days a week, 365 days a year with a minimum of 97.9% up time.

E. Usage Requirements

1. Ability to stream video for viewing without download.

2. Ability to download a watermarked, read-only copy to an encrypted drive (according to user’s permissions).

3. Ability for non-technical users to upload, tag, view and share files in the system with limited or no training.

4. Ability for non-technical users to conduct simple and detailed searches across the system with limited or no training, to include:

a. Name or partial name

b. Date/time or date/time range

c. Incident number

d. Incident type

e. Crime type

f. Location

g. Unit

h. Officer

i. Device

j. Archival/deletion date or date range

k. Review date or date range

5. Ability to tag, categorize, annotate, and mark for later any file.

6. Ability to conduct simple and detailed searches across the database.

7. Ability to limit searches to only the user’s own videos (by role).

8. Ability to provide a notification and point of contact for files available in the database, for which the user does not have permission to view.

9. Ability for users to contact points of contact through the system to request permission to view.

10. Ability for supervisors to review files.

11. Provide for tracking and notifications of tasks through standard and customized workflows.

12. Ability to quickly collect media files in a case, or temporary collection, for the purpose of investigation and analysis, sharing and export.

13. Provide standardized and customizable reports, to include:

a. Chain of Custody

b. Evidence Log

c. Case File

d. Property inventory F. Requirements and Service Level Agreement (SLA) Selected vendors shall provide additional services as agreed by a Service Level Agreement to include, but is not limited to:

1. Install and configure a fully functional body camera system/storage solution with functionally that meets the DOI requirements.

2. Include licensing for time identified within this RFP.

3. Provide phone support during business hours.

4. Provide a one day on-site training relating to the device operation and maintenance of daily care for police officers. Within this training include documentation and training to support video storage/management, processing and redaction.

5. Provide necessary training materials and user manuals.

6. The vendor shall warrant the operation of all equipment, software and hardware products for a period of no less than 12 months from the date of acceptance at no additional cost.

7. Vendor shall assign a project manager responsible for the overall execution of the contractor's specific tasks. Submit a resume of the Project manager who will be assigned to the project. Project manager must be approved by the DOI. The DOI reserves the right to choose, at any time and for any reason, another project manager.

8. Vendor shall provide quarterly reports to the DEMS Contracting Officer / Contracting Specialist summarizing the status of all current and pending task orders. This quarterly status report will include details of all task orders completed and pending by ordering site, totals of equipment and services purchased, and total of all expenditures to date.

G. Administrative Requirements

1. Allow for a limited number of system administration accounts to manage the Department’s files and data.

2. Allow for a hierarchy of administration accounts to enable bureau- and office- level management of files and data.

H. Records Management

1. Metadata Requirements

a. Date/Time stamp

b. Officer

c. Unit

d. Bureau

e. Incident number

f. External File Number (Docket or Case #)

g. Subject Name(s)

2. Ability to implement DOI and Bureau Records Schedules and retention periods.

3. Permissions to set and modify retention periods by role and unit designation.

4. Ability to set standard and special retention requirements per file or group of files.

5. Ability to set schedules for automatic purge dates, archival and deletion, with notifications prior to action taken.

6. Automatic retention periods are set based on the classification of the video. Officers should be able to review video scheduled for deletion based on automatic retention schedules and notifications to the officers. Video should be automatically purged based on defined business rules.

I. Privacy Act and FOIA Requirements

1. Provide an integrated module (or functionality) for specified personnel to manipulate media files for editing or redaction purposes, with the ability to:

a. Delete portions or periods of audio or video content

b. Blur portions or periods of video content

c. Clip audio or video

d. Scramble portions of audio content

e. Alter or disguise voice in audio or video content

f. Automatically track faces, license plates, and other objects in video so as not to perform manual frame-by-frame redaction Track moving objects from a moving camera

g. Export files to Adobe, Photoshop, and Premier

h. Includes redaction reports that detail where blurs or audio redactions take place

2. Legal and FOIA release of records:

a. Alterations must be captured within the system’s action or audit records and be able to be provided to the requesting Court entity.

VIII. Additional Requirements A. Can quickly be deployed to multiple bureaus and programs, across multiple time zones, with both common and unique requirements, and using a variety of media capture devices.

B. Original and altered files from the solution must have evidentiary value in the court of law. A solution that has historically proven the ability to adequately secure video files for inclusion as reliable evidence in court will be given strong preference.

C. Customer Service and Support.

D. Training.

IX. Technical Requirements Notes A. Accreditation at a FEDRAMP moderate impact level.

B. Provide complete audit logs tracking all activities and actors on files including the hit, view, access, edit, download, and share actions by device and system time stamping.

C. Ability to maintain and export audit trails per file. An audit trail will be generated for every file and track all user activity. Provide Litigation support (documentation and testimony in court if needed) to support transport/chain of custody, and storage system.

X. Policy Notes A. Personnel accessing any recordings may not delete, alter, release, or redact, in part or in whole, any recording without legal (Court/U.S. Attorney’s Office) or administrative authority (valid Freedom of Information Act (FOIA) request through the FOIA office) to do so.

B. Legal release

1. All recordings may be altered, redacted and released with the guidance and constraints of the Court entity. (NOTE: steps must be taken to ensure the integrity of the original recording.)

2. Alterations must be captured within the system’s action or audit records and be able to be provided to the requesting Court entity.

C. FOIA release

1. All recordings may be altered, redacted and released with the guidance and constraints of the FOIA request and FOIA Office. (NOTE: steps must be taken to ensure the integrity of the original recording.)

2. Care should be taken to ensure the release images of individuals or other identifying objects captured within the recording are handled within the FOIA and Privacy Act regulations.

3. Alterations must be captured within the system’s action or audit records and be able to be provided to the requesting Court entity.

Sensitive but Unclassified – For Official Use Only

Sensitive but Unclassified – For Official Use Only Page

Sensitive but Unclassified – For Official Use Only Page 18 image1.png image2.png image4.png image3.png image5.png image20.png