BIS_OEE_SOW Body Worn Camera Program _Draft.pdf
PDF 533 KB Posted
- Attached to
- Source - Sought Synopsis - BIS Body Worn Camera Program Federal contract opportunity
- Solicitation number
- EX430600-23-00078
About this file
This statement of work outlines requirements for a body worn camera program for the Bureau of Industry and Security within the Department of Commerce. Key requirements include body worn cameras, electronic control devices, and a digital evidence management system software as a service solution. The statement specifies hardware requirements for approximately 400 body worn cameras and 25-50 electronic control devices to be delivered within 30 days of order, along with related accessories and supplies. It also details requirements for a FedRAMP authorized digital evidence management system to store, manage, and share audiovisual evidence captured by the body worn cameras. The software must support 3,000 users with 500 simultaneous users and include licensing, hosting, maintenance and support, and training for five years. Products must comply with standards for criminal justice information, federal information security, and Section 508 accessibility.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Sources Sought Synposis Notice - BIS Body Worn Camera Program.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DEPARTMENT OF COMMERCE ENTERPRISE SERVICES
STATEMENT OF WORK
STATEMENT OF WORK:
BODY WORN CAMERA PROGRAM
FOR
Bureau of Industry and Security (BIS), Office of Export Enforcement
(OEE)
Table of Contents
1. Project Title:
2. Background/Vision:
3. Hardware:
4. Software as a Service (SaaS) Model, Licensing and Storage:
5. FedRAMP Compliance:
6. General Requirements:
7. DEMS Requirements, Features and Settings:
8. System Standards Compliance:
9. Internet Protocol Version 6:
10. Customer Service & Support:
11.. Legal Authorities and Regulatory Requirements:
Appendix: Key Terms, Acronyms and Definitions
1. Project Title:
Body Worn Camera Program
2. Background/Vision:
The United States Department of the Commerce (DOC) Bureau of Industry and Security (BIS) Office of Export Enforcement (OEE), hereafter referred to as BIS OEE, has a need to enhance its program with integrated products and solutions designed to improve and enhance law enforcement actions, officer safety and public safety.
In May 2022, Presidential Executive Order 14074 was signed mandating all federal law enforcement agencies to adopt and publicly post body-worn camera policies that mandate activation of cameras during activities like arrests and searches, OEE and other DOC federal law enforcement agencies (LEAs) are seeking to acquire body-worn cameras. Additionally, OEE requires the ability to ingest, manage, and share body-worn camera video/audio captured during specific law enforcement operations through a Digital Evidence Management System (DEMS). DEMS, the foundation of this integrated solution, is a cloud-based system.
In sum, to fully comply with Presidential Executive Order 14074, meet federal standards, and comply with DOC IT security and OEE policy, BIS OEE will need Body Worn Camera(s) (BWC), DEMS, and Electronic Control Devices (ECD), along with the appropriate and necessary services and support. See below for a more detailed breakdown:
DEMS is software used to store, manage, secure, share, redact, protect and dispose of digital evidence, most typically in the form of video, photo and audio records. BIS OEE requires a DEMS in the form of Software as a Service (SaaS) which is hosted in a vendor provided cloud environment. The SaaS solution must currently be FedRAMP Authorized with an Authority to Operate (ATO) rated for impact level moderate or high.
Currently authorized means as of the closing date of the Request for Quote (RFQ).
BWC are audio and video recording devices worn by law enforcement officers as part of their uniform to document what they see and hear as they perform their duties. BIS OEE requires approximately 150 BWC’s (DOC law enforcement agencies (LEA) require approximately 400) for its law enforcement program; however, during an initial trial period, BIS OEE will only seek to purchase approximately 25 BWCs (subject to change). BIS OEE requires a variety of accessories for the BWC operations. BIS OEE policy has a strict requirement for BWC’s to have a minimum 30-second pre-event, buffering recording mode. BIS OEE requires access to training and / or training curriculum for BWCs.
ECD’s also known as Electronic Control Weapon (ECW) or Conducted Energy Weapon (CEW) or Conducted Energy Device(s) (CED) are less-lethal devices that uses electricity to override voluntary motor responses or apply pain to gain compliance or overcome resistance from a subject. The ECD allows for a quick recovery time, requires no decontamination, and allows officers to subdue a subject from a greater distance than OC spray, baton, and other short-range less-lethal devices. BIS OEE requires approximately 25-50 (subject to change) ECD’s for its law enforcement less lethal program. BIS OEE requires a variety of cartridges for the ECD’s for operation and training. BIS OEE requires a variety of accessories for the ECD’s for operation and training. BIS OEE requires access to training and / or training curriculums for ECD’s.
3. Hardware:
A. Body Worn Cameras (BWC)
BIS OEE and other DOC LEAs intend to purchase, or will need the ability to purchase, the items and quantities listed in the table below. Please note, this is not an all-inclusive list. Further, quantities identified below are subject to change.
*A full schedule of supplies has been attached as – DOC Schedule of Supplies 6- 8-23
Item# /
SKU
Item Description Year Quantity
100147 Axon Body 4 (AB4) Body Worn Camera Base- Option Year 4
100466 USB-C to USB-A Cable for AB3 Base- Option Year 4
11507, 74020, 74028, etc.
Molle Mount, Magnet Mount, Wing Clip Mount (*other mounts are listed in the attached supply schedule)
Base- Option Year 4
100201 Axon Body 4 (AB4) 1 Bay Dock (*other docks available for purchase listed in the attached supply schedule)
Base- Option Year 4
71104 North American Power Cord for Axon Body 3 (AB3) & T7 1 Bay Dock/Dataport
Base- Option Year 4
85144 Axon Starter Service Base
85014 Axon 1-day Service Base
1. Body Worn Camera (BWC) Requirements
a. 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 up to 400 in the Base year, with potential for additional purchase in subsequent Option years, for all DOC LEAs.
b. 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.
c. 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.
d. Ease of operation: Cameras should be easy to power activate/deactivate, and record activate/deactivate as needed with a single switch/button.
2. Camera Operational Requirements:
a. Must possess a minimum 142-degree field of view.
b. The video image shall be in full color.
c. The camera shall have low light capability.
d. There shall be a minimum of 16 GB internal/integrated memory.
e. Minimum video graphics array (VGA) resolution (640 x 480 pixels).
f. Minimum recording speed of 30 fps.
g. Minimum of 30 second pre-event recording configurable up to 2 minutes.
h. Camera must have auto-activation recording capability.
i. Bluetooth capability is preferred.
j. Camera must have audio recording capability.
k. GPS capability is preferred.
l. Officers must have the capability or option to view, categorize and annotate the recorded video on scene.
m. The camera must have an initial standby battery life of 12 hours without recharging or additional batteries.
n. A minimum 5 hours of record time.
o. Recharge in less than 8-10 hours.
p. Multiple charging capabilities to include docking station and USB cable.
q. Video/audio files shall be tagged with date/time.
r. Camera equipment must have a five (5) – year warranty.
B. Electronic Control Device (ECD)
BIS OEE intends to purchase or will need the ability to purchase the items and quantities listed in the table below. Please note, this is not an all-inclusive list.
Further, quantities identified below are subject to change. *A full schedule of supplies has been attached as – DOC Schedule of Supplies 6-8-23
Item# / SKU Item Description Year QT Y
20008 Taser 7 Handle, Yellow, High Visibility, Green Laser
Base-Option Year
25-
20018 Taser 7/10 Battery Pack – Tactical Base-Option Year
22175 Taser 7 Live Cartridge, Standoff 3.5 Degree Base-Option Year
22176 Taser 7 Live Cartridge, Close Quarters 12 Degree
Base-Option Year
22177 Taser 7 Hook-and-Loop Training Cartridge Standoff
Base-Option Year
22178 Taser 7 Hook-and-Loop Training Cartridge Close Quarters
Base-Option Year
74201 Taser 7 Single Bay Dock + Core Base-Option Year
20160/ 20161
Taser 7 Holster- Safariland RH/LH Base-Option 4 25-
20023 Taser 7, Training Handle, Blue Rubber Base 2
803985 Taser 7 Handle Ext Warranty Base-Option Year
80374 Taser 7/10 Battery Pack Ext Warranty Base-Option Year
80387 Single Bay Dock Ext Warranty Base-Option Year
80087 Taser 7 Target Conductive Professional Base 2
80090 Taser 7 Target Frame Professional Base 2
20050 Hook and Loop Training (HALT) Suit Base 1
85147 CEW Starter Service Base
44729 Taser Instructor Course Voucher Base 4
1. ECD General Requirements:
a. ECD’s shall be yellow in color. Total quantity of 25-50 (subject to change) with potential to purchase additional units in future years.
b. Mounting: ECD’s should have multiple wearing and holster options to accommodate varying uniformed officers, plain-clothed officers, and tactical field situations. Examples include, but are not limited to, right-hand draw, left-hand draw, etc.
c. 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.
d. Ease of operation: ECD’s should be easy to activate/deactivate as needed with a single switch/button.
2. ECD Operational Requirements:
a. Ability to operate in a temperature range of -4 to 122
b. Shall be water resistant to IEC specifications.
c. Shall have a housing made of high impact polymer.
d. Shall have an onboard high efficiency flashlight.
e. Shall have a central Information Display
f. Shall have on board self-diagnostics
g. Total weight no more than 1 LB with the battery
h. Utilize management software that is FEDRAMP authorized.
i. Possess ambidextrous safety lever.
j. Use cartridges that shoot probes between 15’ and 25’.
k. Ability to offer a warning arc without having to fire the probes.
l. Utilize multiple cartridges.
m. Utilize dual aim point lasers.
3. Necessary Life Cycle Support Program Requirements:
BIS OEE requires an equipment support program that cuts down on overall device lifecycle costs which include the following:
a. Comprehensive equipment warranty for a minimum of 3 years
b. Planned CEW modernization program that upgrades current arsenal to the most Technology advanced CEW / ECD weapon, upon certification and when readily available.
c. Supply of training cartridges to support qualification sent annually.
d. Access to online-training content.
e. Hook and Loop Training (HALT) Suit
f. Master Instructor training vouchers.
g. Hosted Master Instructor Course held annually location TBD
h. Enhanced weapons training available.
i. Weapons inventory management system.
C. Accessories (if optioned)
The vendor shall provide a comprehensive, but not exhaustive, list of accessories available for hardware items requested in this Statement. The vendor shall list pricing for all available accessories and indicate any minimum or maximum quantities required for purchasing. Vendor shall indicate if pricing of accessories listed in this Statement will remain available for purchase at the same agreed to pricing for the life of the contract. Accessories and pricing listed on the attached DOC Schedule of Supplies.
D. Warranty
The vendor shall provide information related to all warranties for hardware and accessories, to include warranty terms and conditions.
E. Returns
The vendor shall provide information, instructions, shipping addresses and processes related to hardware returns for service and/or support.
F. Additional Hardware (if optioned)
As an optional task, if exercised, the vendor shall provide the ability for BIS OEE and DOC LEAs to purchase additional hardware at a Firm Fixed Price (FFP). The vendor shall list pricing for all hardware requested in this Statement and indicate any minimum or maximum quantities required for purchasing. BIS OEE and DOC LEAs anticipate the need to purchase additional hardware during this project in the range of 10% to 25% of the initial purchase. The vendor should provide agreed to pricing for the purchase of additional hardware by quantity. Suggested quantities are: 1 unit, 5 units, 10 units, 25 units and 50 units.
G. Spare Devices
Due to the public safety / mission critical nature of this hardware, having spare devices on-hand and immediately accessible is preferred by BIS OEE and DOC LEAs. The vendor shall provide information related to provision of spare hardware and provide associated terms and conditions.
4. Software as a Service (SaaS) Model, Licensing and Storage
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 vendor will provide a SaaS solution allowing BIS OEE and DOC LEAs to purchase licenses to utilize the software.
BIS OEE intends to purchase the items and quantities (subject to change) listed in the table below. *A full schedule of supplies has been attached as – DOC Schedule of Supplies 6-8-23
Item# /
SKU
Item Description Year Quantity
73746 Professional Evidence.Com License All 400
73686 Evidence.Com Unlimited Axon Device Storage
All 400
73683 10 Gigabyte Evidence.Com A-La-Cart Data Storage allowance
All 800
73680 Respond Device Plus All 400
73779 Axon Redaction Assistant User License All 400
73739 Performance License All 400
A. Licensing
The vendor shall provide software and licenses necessary for use and operation of services pursuant to this Statement. The vendor shall provide documentation information related to licensing use and ownership, to include associated terms and conditions.
B. Additional Licensing (if optioned)
As an optional task, if exercised, the vendor shall provide the ability for BIS OEE and DOC LEAs to purchase additional licensing at a Firm Fixed Price (FFP). The vendor shall list pricing for all licenses requested in this Statement and indicate any minimum or maximum quantities required for purchasing. BIS OEE and DOC LEAs anticipate the need to purchase additional licenses during this project in the range of 10% to 25% of the initial purchase. The vendor should provide agreed to pricing for the purchase of additional licenses by quantity. Suggested quantities are: 1 unit, 5 units, 10 units, 25 units and 50 units.
C. Agency Owned Content
BIS OEE and DOC LEAs control and own all right, title, and interest in each individual agency content. Vendor obtains no interest in each agency’s content, and agency’s content are government records. BIS OEE and each DOC LEA is solely responsible for uploading, sharing, managing, retaining, redacting, and deleting agency content. Vendor will have limited access to agency content solely for providing and supporting Cloud Services to agency and agency end users.
D. Storage
The vendor shall provide information regarding best practices for data management and storage on the vendors system, for the purpose of maximizing available storage and preventing additional charges for storage to extent possible.
E. U.S. Government Cloud Services
BIS OEE is a Federal Agency of the United States Government and will be using vendor provided Software as a Service (SaaS) Cloud Services for agency mission. These services are defined in the Federal Acquisition Regulation and Defense Federal Acquisition Regulation Supplement as “commercial item,” “commercial computer software,” “commercial computer software documentation,” and “technical data.”
F. Termination
The vendor shall provide detailed information regarding handling and availability of Agency Owned Content and data upon contract termination. Vendor shall indicate status of licensing, availability of access to systems and data and any pertinent timelines. Vendor shall indicate how long agency data will remain accessible and available upon termination of the contract and/or agreement.
Vendor shall provide information on any associated fees for bulk data extraction, transfer or egress.
5. 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 DEMS solution must be FedRAMP moderate compliant. Vendors must demonstrate FedRAMP ready, in process, or authorized status for Software as a Service (SaaS). A FedRAMP and DOC compliant Authority to Operate (ATO) are required by BIS and DOC LEAs prior to going into production. FedRAMP authorized is defined as follows:
FedRAMP Authorized means the service has a Provisional Authorization to Operate (P-ATO) via the Joint Authorization Board (JAB).
6. General Requirements:
A. Period of Performance:
1. Hardware and Software – all hardware and software for delivery 30 days after receipt of order (ARO) as required within the Statement. Hardware items shall include support and maintenance, including vendor standard warranties and any enhanced warranties, if offered.
2. Licenses and Support: one (1) base period of coverage, and Four (4) additional option periods for Licenses and Software Support (Purchased as a Commercial Products)
Periods of Coverage for licenses and maintenance:
Base Period - From Contract Award for 365 calendar days
Option Period 1 - if exercised, period of performance of 365 calendar days
Option Period 2 - if exercised, period of performance of 365 calendar days
Option Period 3 - if exercised, period of performance of 365 calendar days
Option Period 4 - if exercised, period of performance of 365 calendar days
B. Bid / Requirements Pricing Sheet / Schedule
A bid / requirements pricing sheet / schedule template is included as an attachment to the Statement, and vendors are requested to submit a completed requirements pricing sheet/Schedule of Supplies in response to this Statement.
The intent of the requirements pricing sheet/Schedule of Supplies is to provide a comprehensive listing of all BIS OEE requirements. Vendors should also include a comprehensive price list of all other items to include accessories, peripherals and/or minor components which may be purchased by the government as options under this contract.
C. The Vendor shall, at all times, comply with the following (access to directives, regulations, statutes, ordinances, laws, and codes shall be provided prior to or at award):
1. All applicable directives of the DOC.
2. All DOC Security regulations.
3. All applicable regulations.
4. All applicable Federal, DOC and local statutes, ordinances, laws, regulations, codes, directives, and/or orders.
D. The Vendor shall:
1. Provide a list of key personnel, key contacts and decision makers, indicating position and role for each.
2. All vendor personnel and alternates must be able to read, write, speak, and understand the English language.
3. Participate in meetings with government identified POC’s and/or Project Team, as directed by the Contracting Officer’s Representative (COR) or designee.
4. Promptly communicate the delivery schedules of all hardware and software with the COR to allow DOC to track deliveries and coordinate arrivals.
5. Support all system-related software to include: operating system(s), database, application and application-related. The Vendor shall be responsible for upgrading and supporting system-related software.
6. Coordinate all software through the COR to ensure compliance prior to acceptance.
7. The Vendor’s solution must be cloud ready and must be currently FedRAMP
Authorized with an Authority to Operate (ATO) rated for impact level moderate or high. Currently authorized means as of the closing date of the Request for Quote (RFQ). (see section on FedRAMP Requirements)
8. Consistent vendor communications regarding requirements and expectations through this coordinating effort is expected.
E. Disclosure of Information
Information made available to the vendor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the Contracting Officer.
The vendor agrees to assume responsibility for protecting the confidentiality of Government records which are not public information. Each vendor or employee of the vendor to whom information may be made available or disclosed shall be notified in writing by the vendor that such information may be disclosed only for a purpose and to the extent authorized herein.
F. Limited Use of Data
Performance of this effort may require the vendor to access and use data and information sensitive and proprietary to a Government agency or Government vendor which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others.
Vendor and/or vendor personnel shall not divulge or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorized Government personnel or upon written approval of the Contracting Officer (CO). The vendor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein shall preclude the use of any data independently acquired by the vendor without such limitations or prohibit an agreement at no cost to the Government between the vendor and the data owner which provides for greater rights to the vendor.
7. DEMS Requirements, Features and Settings:
A. System 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 BIS OEE and other DOC LEAs and increasing number of 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. Provide account-based, unique user, two-factor authentication.
14. Provide separate and secure backup of all data stored in the operational system.
15. 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.
16. Provide for disaster recovery, disaster recovery planning, and annual disaster recovery testing; provide proof and/or certification of annual disaster recovery test with evidentiary documentation to the COR.
17. Provide for secure long-term or permanent archival of specific files which retains file integrity and all-important metadata associated with the file.
18. Provide for 24-48-hour retrieval of files, if archived off-site.
19. Ability to restore archived files into the active database.
20. Support up to 3,000 current users and 500 simultaneous users.
21. Supportable by local IT staff, as required to provide administrative functions for system and user support.
22. Operational/Active Files
23. Data requiring upload is estimated at ~1.5TB/officer/year
24. Data requiring storage beyond a 30-90-day retention period is ~10%
25. Backup Files
26. Mirror Operational Files
27. File Archival and Retrieval
28. May be a limited requirement, based on the ability to archive files in the
IMARS environment.
29. Upload of video to the System should require minimal User interaction (e.g.
dock, plug-in device or wireless and files are uploaded).
30. Ability to upload a minimum of 800 videos simultaneously.
31. Ability to put files for upload in queue.
32. Provide for secured wireless or wired upload from any plug-in device, (vendor should provide recommendations for device integration).
33. Enable use of standardized docking stations for automatic and unattended upload of files.
34. 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.
35. Provide for holding or parsing of packages before or in transmission to enable bandwidth-sensitive upload of large media files.
36. Ability to securely upload a file from any connected device, in any common file format (nonproprietary), without alteration.
37. Ability to package and export any file in its original format, as well as a standard format.
38. 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.
39. Automated time/date stamping of video and automated or manual tagging of associated:
a. Officer/Agent
b. Unit/Badge#
c. Incident number
d. Evidence
e. Sensitive/Secure
40. Ability to quickly bulk load and tag files with common metadata.
41. Ability to select and drag and to copy and paste files from a computer or other device into the system upload queue.
42. Ability to work on and share a copy of the record in the system, without touching or risking integrity of the original file.
43. 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
44. Ability to print photos and reports to a local printer.
45. Vendor will work with BIS OEE and DOC LEAs to accommodate the upload of digital data from legacy cameras of competing brands into the vendor’s evidence management software.
46. Access to the system will be role-and permissions-based, as well as unit-or group-based.
47. 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.
48. Roles, permissions, and units are pre-defined, and easily assigned by system
(or other appropriate level) administrators.
49. Users can have multiple roles and units within the system, with the ability to switch between roles.
50. Access to individual folders, files, or parts of files can be further secured
(hidden) by users using access control features.
51. Ability to share or secure specific files to specific users of the system, for a specific or unlimited period of time.
52. 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 Gmail, Outlook, others)
53. System shall provide 99.5% availability or higher, and limited disruption to all
DOC users with an acceptable applied service credit or cost recovery schedule including OEM license provider and partner defined contract responsibilities.
54. Ability to stream video for viewing without download.
55. Ability to download a watermarked, read-only copy to an encrypted drive
(according to user’s permissions).
56. Ability for non-technical users to upload, tag, view and share files in the system with limited or no training.
57. 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/Badge #
h. Officer/Agent
i. Device
j. Archival/deletion date or date range
k. Review date or date range
58. Ability to tag, categorize, annotate, and mark for later any file.
59. Ability to conduct simple and detailed searches across the database.
60. Ability to limit searches to only the user’s own videos (by role).
61. 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.
62. Ability for users to contact points of contact through the system to request permission to view.
63. Ability for supervisors to review files.
64. Provide for tracking and notifications of tasks through standard and customized workflows.
65. Ability to quickly collect media files in a case, or temporary collection, for the purpose of investigation and analysis, sharing and export.
66. Provide standardized and customizable reports, to include:
a. Chain of Custody
b. Evidence Log
c. Case File
d. Property inventory
B. 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. Configure and activate a fully functional DEMS solution with functionally that meets the DOC and BIS OEE requirements.
2. Include licensing for time identified within this Statement.
3. Provide phone and email support during company business hours, (M-F, 9AM-5PM), based on the time zone of the company headquarters in Scottsdale, AZ.
4. Provide after-hours support for troubleshooting service and support for outages and critical issue resolution. Provide documentation on the SLA and response times.
5. During large planned operations support by DOC prior notification will be coordinated via the COR to request 24 hours per day troubleshooting service and support for outages and critical issue resolution
6. Provide an 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.
7. Provide necessary training materials and user manuals.
8. 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.
9. Vendor shall assign a project manager responsible for the overall execution of the vendor's specific tasks.
C. 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.
D. Records Management
1. Metadata Requirements
a. Date/Time stamp
b. Agent
c. Field Office
d. Badge #
e. Incident/Case number
f. Subject Name(s)
2. Ability to implement DOC 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.
E. 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. Automatically track faces, license plates, and other objects in video so as not to perform manual frame-by-frame redaction
f. Track moving objects from a moving camera
g. Export files to Adobe, Photoshop, and Premier
2. Legal and FOIA release of records:
Alterations must be captured within the system’s action or audit records and be able to be provided to the requesting Court entity.
F. Additional Requirements
1. 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.
2. 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.
3. Customer Service and Support. (See section customer service and support requirements)
G. Policy Notes
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.
H. Legal release
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.)
Alterations must be captured within the system’s action or audit records and be able to be provided to the requesting Court entity.
I. FOIA release
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.)
8. System Standards Compliance:
Each DOC LEA Bureau will conduct an Assessment & Authorization (A&A) of the DEMS system before the OCIO of each participating DOC Bureau issues an Authority to Operate (ATO) on their respective DOC network. When this assessment is conducted, the vendor may be required to answer questions, to participate in the A&A process and potentially implement any information security changes necessary to facilitate receiving an ATO for this system. The system is required to meet or exceed specific and relevant security requirements identified and detailed in the Security and Privacy Requirements documentation.
The system shall be fully compliant with the most recent U.S Department of Justice (USDOJ), Federal Bureau of Investigation (FBI) Criminal Justice Information Services CJIS) Security Policy.
The system and any/all electronic and information technology procured through this effort must be compliant with 29 U.S.C § 794d - Electronic and information technology (Section 508 Compliance Amendment to the Rehabilitation Act of 1973) the applicable accessibility standards at 36 CFR 1194. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov. Standards applicable to this requirement include:
Functional Performance Criteria 1194.31 and Information, Documentation, and Support 1194.41.
9.Internet Protocol Version 6:
Any system hardware, software, firmware and/or networked component (voice, video or data) developed, procured, or acquired in support and/or performance of this contract shall be capable of transmitting, receiving, processing, forwarding and storing digital information across system boundaries utilizing system packets that are formatted in accordance with commercial standards of Internet Protocol (IP) version 6 (IPv6) as set forth in the USGv6 Profile (NIST Special Publication 500-
267) and corresponding declarations of conformance defined in the USGv6 Test Program.
http://www.section508.gov./
Systems and Services shall be accessible from the Internet and DOC's computer network using Internet Protocol version 6. Services accessible via IPv6 shall be equivalent to services provided via IPv4; Systems and services must interoperate with both IPv6 and IPv4 systems and products.
In addition, this system shall maintain interoperability with IPv4 systems and provide at least the same level of performance and reliability capabilities of IPv4 products.
The system shall be fully compliant with National Institute of Standards and Technology (NIST), Federal Information Processing Standard (FIPS) Publication 140-2, Security Requirements for Cryptographic Modules.
The system shall be fully compliant with National Institute of Standards and Technology (NIST), Federal Information Processing Standard (FIPS) Publication 197, Advanced Encryption Standard (AES) 256-bit cypher.
The system shall be fully compliant with National Institute of Standards and Technology (NIST), Special Publication 800-82, Guide to Industrial Control Systems (ICS) Security (Revision 2 Initial Public Draft).
National Institute of Standards and Technology (NIST) Special Publication 500-267, A Profile for IPv6 in the U.S. Government – Version 1.0. Reference: NIST Link:
http://www.nist.gov/information-technology-portal.cfm
10. Customer Service & Support:
Support shall include technical assistance to the Government DEMS system designated administrator(s) available during normal business hours with a 24-hour maximum response time to inquiries and questions.
The standard technical support shall include support for all supplied software and any updates, such as patches and/or bug fixes or broadly distributed feature updates. The vendor shall also provide technical support for the installed DEMS system version. Standard technical support may not include any customization and/or feature updates requested by the government.
Licensing should be structured to be flexible and dynamic allowing for all licenses to be used concurrently on appropriate devices at any time and any location desired by the government throughout the base and option years.
11. Legal Authorities and Regulatory Requirements:
The design, construction and operation of the system, network and transmission of all data must comply with all commonly accepted commercial network standards http://www.nist.gov/information-technology-portal.cfm and regulations and with the following legal and regulatory requirements:
A. 44 U.S.C. § 3501 - Federal Information Security Management Act (FISMA) of
B. 44 U.S.C. § 3501 - Federal Information Security Modernization Act (FISMA) of 2014
C. 16 U.S.C. § 470 – National Historic Preservation Act D. 29 U.S.C § 794d - Electronic and Information Technology (Section 508
Compliance Amendment to the Rehabilitation Act of 1973) E. 28 C.F.R. § 20 - Criminal Justice Information Systems F. 43 C.F.R. Public Lands: Commerce G. FBI CJIS Security Policy H. Department of the Commerce Acquisition Policy Release (DIAPR) 2012-09 –
IPv6
All work shall be performed in accordance with NIST SP 800-37, 800-18, 800-30, 800-60, 800-53, 800-53A, Federal Information Processing Standard (FIPS) 199 & 200, DOC guides & templates, and the DOC Privacy Impact Assessment.*Guides and templates shall be provided at time of award by the COR
The quoted solution will undergo Assessment & Authorization activities by the government, and the quoted solution will undergo continuous monitoring as set forth in NIST SP 800-37. The vendor will take appropriate and timely action to correct or mitigate any weaknesses discovered during such activities, at no additional cost to the government.
https://www.fbi.gov/about-us/cjis/cjis-security-policy-resource-center
Appendix: Key Terms, Acronyms and Definitions The following are definitions and explanations for terms and acronyms relevant to the content presented within this document and terms which may be used during the period of performance. Not all terms listed below may be found in this document.
AES: Advanced Encryption Standard A&A: FISMA Assessment and Authorization API: Application Programming Interface AR: Administrative Resources ATO: Authority to Operate BIS: Bureau of Industry and Security CFR: Code of Federal Regulations CJIS: Criminal Justice Information Services Division of the Federal Bureau of Investigation CLIN: Contract Line Item Number COR: Contracting Officer’s Representative DOC: United States Department of the Commerce ESN: Enterprise Services Network FAR: Federal Acquisition Regulations FAX: Facsimile FIPS: Federal Information Processing Standard FISMA: Federal Information Security Management Act of 2002 or FISMA: Federal Information Security Management Act of 2014 or ID: Identification IMARS: Incident Management, Analysis and Reporting System IP: Internet Protocol ISA: Interconnection Security Agreement LEA: Law Enforcement Agency LEO: Law Enforcement Officer LEN: Law Enforcement Network LOB: Line of Business NIJ: National Institute of Justice NIST: National Institute of Standards and Technology PC: Project Coordinator PI: Project Inspector PM: Project Manager POA&M: Plan of Action & Milestones RFP: Request for Proposal RFQ: Request for Quote RMS: Records Management System SOP: Standard Operating Procedures VRF: Virtual Routing and Forwarding XML: Extensible Markup Language
File details come from the government source that posted it. Updated .