SF33 - 15BPCC26R00000004.pdf
PDF 405 KB Posted
- Attached to
- Body-Worn Camera Solution
- Solicitation number
- 15BPCC26R00000004
- Issued by
-
Department of Justice Bureau of Prisons
About this file
Solicitation Summary: Body-Worn Cameras for Federal Bureau of Prisons
This is a Request for Proposal (RFP) issued by the Federal Bureau of Prisons (FBOP) for the acquisition of body-worn cameras (BWCs) and associated hardware, software, cloud services, and support. The solicitation number is 15BPCC26R00000004, issued on August 14, 2026, with proposals due by 5:00 PM ET on September 3, 2026. This is a negotiated procurement using commercial item acquisition procedures under FAR Part 12.
The Government seeks a firm-fixed-price, indefinite-delivery/requirements contract with one twelve-month base year and seven one-year option periods, plus a potential six-month extension. The contractor must provide commercially available, Trade Agreements Act (TAA)-compliant BWC devices rated for IP67 dust/water resistance, operating temperatures of -4°F to 120°F, 16GB minimum internal storage, 12-hour continuous battery life with less than 8-hour recharge time, 120-degree field of view, 720p resolution at 30 FPS, and support for multiple mounting options. The solution must include unlimited cloud storage via a FedRAMP Moderate Authorized system with Authority to Operate (ATO) capability, comprehensive warranty coverage with 10-business-day repair/replacement timelines, unlimited firmware updates, technical support with 99.5% system availability, and training including Train-the-Trainer programs. The contractor shall implement a four-year phased deployment across FBOP facilities nationwide, with estimated quantities provided in Attachment J.1, representing approximately 75-150 cameras in active use during peak shifts across three operational shifts. Pricing must be all-inclusive, accounting for hardware, accessories, software licenses, cloud services, unlimited digital evidence storage for up to 10 years, minimum warranty, shipping, technical support, training, and technology refresh. Proposals shall consist of three separate volumes: Technical (describing the solution and FedRAMP authorization evidence), Past Performance (contracts performed in the preceding three years), and Price. Award will be based on best-value tradeoff with Technical Capability evaluated as significantly more important than Price using Good/Acceptable/Unacceptable ratings, Past Performance evaluated on Pass/Fail/Neutral basis as an eligibility factor, and Price not receiving adjectival ratings. The solicitation requires small business subcontracting plans for non-small business offerors and includes special requirements for personnel security clearances, DOJ information security compliance, and Large Language Model disclosures if applicable.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
15BPCC26R00000004 Page 1 of 68
SOLICITATION, OFFER, AND AWARD 1. This Contract is a Rated Order under the Defense Priorities and Allocations
System (DPAS) - Code of Federal Regulations - at 15 CFR 700.
RATING
2. CONTRACT NUMBER 3. SOLICITATION NUMBER
15BPCC26R00000004
SEALED BID (IFB) INVITATION FOR BID
X NEGOTIATED (RFP) REQUEST FOR
PROPOSAL
4. TYPE OF SOLICITATION 5. DATE
ISSUED
08/14/2026
6. REQUISITION/PURCHASE
NUMBER
CODE 15BPCC
Federal Bureau of Prisons Privatized Corrections Contracting 320 First Street NW Suite 524 Washington, DC 20534
7. ISSUED BY 8. ADDRESS OFFER TO (If other than item 7)
NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".
SOLICITATION
17:00 ET 09/03/2026
(Hour) (Date)
CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision Number 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.
9. Sealed offers in original and ____________ copies for furnishing the supplies or services in the Schedule will be received at the place specified in item 8, or if hand carried, in the depository located in ______________________________________________________ until ________________ local time _________________
10. FOR
INFORMATION
CALL:
A. NAME
AREA CODE NUMBER EXTENSION
B. TELEPHONE (NO COLLECT CALLS) C. EMAIL ADDRESS
11. TABLE OF CONTENTS
(X) SECTION DESCRIPTION PAGE(S) (X) SECTION DESCRIPTION PAGE(S)
PART I - THE SCHEDULE PART II - CONTRACT CLAUSES
X A SOLICITATION/CONTRACT FORM 1 X I CONTRACT CLAUSES 35-54
X B SUPPLIES OR SERVICES AND PRICES/COSTS 5-6 PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
X C DESCRIPTION/SPECIFICATIONS/WORK STATEMENT 7-17 X J LIST OF ATTACHMENTS 55
X D PACKAGING AND MARKING 18 PART IV - REPRESENTATIONS AND INSTRUCTIONS
X E INSPECTION AND ACCEPTANCE 19
X K REPRESENTATIONS, CERTIFICATIONS AND OTHER
STATEMENTS OF OFFERORS
56-59
X F DELIVERIES OR PERFORMANCE 20-21
X L INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS 60-64X G CONTRACT ADMINISTRATION DATA 22-23
X M EVALUATION FACTORS FOR AWARD 65-68X H SPECIAL CONTRACT REQUIREMENTS 24-34
OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.
In compliance with the above, the undersigned agrees, if this offer is accepted within _______________________ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.
12.
13. DISCOUNT FOR PROMPT PAYMENT
(See Section I, Clause Number 52.232-8)
10 CALENDAR DAYS (%)
0.00 %
20 CALENDAR DAYS (%)
0.00 %
30 CALENDAR DAYS (%)
0.00 %
0 CALENDAR DAYS (%)
0.00 %
14. ACKNOWLEDGEMENT OF AMENDMENTS
(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):
AMENDMENT NUMBER DATE AMENDMENT NUMBER DATE
15A. NAME AND
ADDRESS
OF
OFFEROR
CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN
OFFER (Type or Print)
15B. TELEPHONE NUMBER
AREA CODE NUMBER EXTENSION
15C. CHECK IF REMITTANCE ADDRESS IS
DIFFERENT FROM ABOVE - ENTER
SUCH ADDRESS IN SCHEDULE.
17. SIGNATURE 18. OFFER DATE
AWARD (To be completed by Government)
19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION
10 U.S.C. 3204(a) ( ) 41 U.S.C. 3304(a) ( )
22. AUTHORITY FOR USING OTHER THAN FULL OPEN COMPETITION
UNDER THE UNITED STATES CODE AT:
23. SUBMIT INVOICES TO ADDRESS SHOWN IN
(4 copies unless otherwise specified)
ITEM
CODE24. ADMINISTERED BY (if other than Item 7)
CODE25. PAYMENT WILL BE MADE BY
26. NAME OF CONTRACTING OFFICER (Type or print) Mason Lacy
(Signature of Contracting Officer)
27. UNITED STATES OF AMERICA 28. AWARD DATE
IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.
AUTHORIZED FOR LOCAL REPRODUCTION
Previous edition is unusable
STANDARD FORM 33 (REV. 12/2022)
Prescribed by GSA - FAR (48 CFR) 53.214(c)
15BPCC26R00000004 Page 2 of 68
Table of Contents
Section Description Page Number
A Solicitation/Contract Form B Supplies or Services and Prices/Costs
B.1 Description of Supplies or Services B.2 Type of Contract B.3 Pricing B.4 Estimated Quantities
C Description/Specifications/Statement of Work C.1 Statement of Work
D Packaging and Marking D.1 Packaging and Marking Requirements
E Inspection and Acceptance E.1 Quality Assurance / Testing Requirements E.2 Firmware Updates / Patches E.3 Warranties
F Deliveries and Performance F.1 Period of Performance F.2 Delivery Schedule Timeline F.3 Notice to the Government of Delays F.4 Place of Delivery
G Contract Administration Data 2852.201-70 Contracting Officer's Representative (COR) (NOV 2020) G.1 Contract Administrative Notice G.2 Contracting Officer's Representative (COR) G.3 Invoicing Requirements
H Special Contract Requirements 2852.222-70 Domestic Violence, Sexual Assault, and Stalking (DEC 2014) 2852.223-70 Unsafe Conditions Due to the Presence of Hazardous Material (NOV 2020) DOJ-05 Security of Department Information and Systems (APR 2026) DOJ-07 Prohibition On Access By Non-U.S. Citizens To DOJ IT Systems (MAR 2002) H.1 Special Security and Clearance Requirements H.2 Legal Authorities and Regulatory Requirements H.3 Internet Protocol Version 6 (IPv6) Requirements H.4 System Standards Compliance H.5 Legal Release Requirements H.6 Disclosure of Information H.7 Limited Use of Data H.8 Disclosure of Data under the Freedom of Information Act (FOIA) H.9 Government Rights in Data and Copyrights
I Contract Clauses 52.203-6 Alt I Restrictions on Subcontractor Sales to the Government (Jun 2020) - Alternate I (Nov 2021) 52.203-13 Contractor Code of Business Ethics and Conduct (Nov 2021) 52.203-17 Contractor Employee Whistleblower Rights (Nov 2023) 52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (Jan 2017) 52.204-9 Personal Identity Verification of Contractor Personnel (Jan 2011) 52.204-13 (DEV) System for Award Management-Maintenance (Oct 2018) (DEVIATION NOV 2025) 52.209-6 (DEV) Protecting the Government's Interest When Subcontracting with Contractors Debarred, Suspended, Proposed for Debarment, or Voluntarily Excluded (Jan 2025)
(DEVIATION NOV 2025)
52.209-9 (DEV) Updates of Publicly Available Information Regarding Responsibility Matters (Oct 2018) (DEVIATION NOV 2025) 52.209-10 (DEV) Prohibition on Contracting With Inverted Domestic Corporations (Nov 2015)
(DEVIATION NOV 2025)
15BPCC26R00000004 Page 3 of 68
52.212-4 (DEV) Terms and Conditions-Commercial Products and Commercial Services (Nov
2023) (DEVIATION NOV 2025)
52.219-8 (DEV) Utilization of Small Business Concerns (Jan 2025) (DEVIATION DEC 2025) 52.219-9 Alt II (DEV) Small Business Subcontracting Plan (Jan 2025) - Alternate II (Nov 2016)
(DEVIATION DEC 2025)
52.219-16 (DEV) Liquidated Damages-Subcontracting Plan (Sep 2021) (DEVIATION DEC 2025) 52.222-3 (DEV) Convict Labor (June 2003) (DEVIATION DEC 2025) 52.222-19 (DEV) Child Labor-Cooperation with Authorities and Remedies (Jan 2025)
(DEVIATION MAR 2026)
52.222-35 (DEV) Equal Opportunity for Veterans (Jun 2020) (DEVIATION DEC 2025) 52.222-36 (DEV) Equal Opportunity for Workers with Disabilities (Jun 2020) (DEVIATION
DEC 2025)
52.222-37 (DEV) Employment Reports on Veterans (Jun 2020) (DEVIATION DEC 2025) 52.222-40 (DEV) Notification of Employee Rights Under the National Labor Relations Act (Dec
2010) (DEVIATION DEC 2025)
52.222-50 (DEV) Combating Trafficking in Persons (Oct 2025) (DEVIATION DEC 2025) 52.222-90 Addressing DEI Discrimination by Federal Contractors (APR 2026) 52.224-3 Alt I Privacy Training (Jan 2017) - Alternate I (Jan 2017) 52.225-5 Trade Agreements (Nov 2023) 52.226-8 Encouraging Contractor Policies To Ban Text Messaging While Driving (May 2024) 52.227-14 Rights in Data-General (May 2014) 52.229-12 (DEV) Tax on Certain Foreign Procurements (Feb 2021) (DEVIATION AUG 2025) 52.232-33 Payment by Electronic Funds Transfer-System for Award Management (Oct 2018) 52.232-40 Providing Accelerated Payments to Small Business Subcontractors (Mar 2023) 52.233-3 (DEV) Protest after Award (Aug 1996) (DEVIATION NOV 2025) 52.233-4 (DEV) Applicable Law for Breach of Contract Claim (Oct 2004) (DEVIATION NOV 2025) 52.240-91 (DEV) Security Prohibitions and Exclusions (DEVIATION NOV 2025) 52.240-93 (DEV) Basic Safeguarding of Covered Contractor Information Systems
(DEVIATION NOV 2025)
52.244-6 (DEV) Subcontracts for Commercial Products and Commercial Services (Jan 2025)
(DEVIATION APR 2026)
52.216-21 (DEV) Requirements (Oct 1995) (DEVIATION DEC 2025) 52.217-8 Option to Extend Services (Nov 1999) 52.217-9 Option to Extend the Term of the Contract (Mar 2000) 52.252-6 Authorized Deviations in Clauses (Nov 2020) 2852.212-4 Contract Terms and Conditions, Commercial Items (FAR Deviation) (NOV 2020)
508 COMPLIANCE WITH SECTION 508 OF THE REHABILITATION ACT OF 1973, 1998
AMENDMENTS
DOJ-01 Whistleblower Information Distribution (Oct 2021) DOJ-02 Contractor Privacy Requirements (JAN 2022) DOJ-03 Personnel Security Requirements For Contractor Employees (Nov 2021) DOJ-08 Continuing Contract Performance During a Pandemic Influenza or other National Emergency (OCT 2007) DOJ-09 Large Language Models (MAR 2026)
J List of Attachments K Representations, Certifications and Other Statements of Offerors
52.203-11 Certification And Disclosure Regarding Payments to Influence Certain Federal Transactions (Sept 2024) 52.203-18 Prohibition on Contracting with Entities that Require Certain Internal Confidentiality Agreements or Statements--Representation (Jan 2017) 52.240-90 (DEV) Security Prohibitions and Exclusions Representations and Certifications
(DEVIATION NOV 2025)
15BPCC26R00000004 Page 4 of 68
52.209-12 Certification Regarding Tax Matters (Oct 2025) 52.222-18 Certification Regarding Knowledge of Child Labor for Listed End Products (Feb 2021) 52.225-6 Trade Agreements Certificate (Feb 2021) 52.229-11 (DEV) Tax on Certain Foreign Procurements--Notice and Representation (Jun
2020) (DEVIATION AUG 2025)
L Instructions, Conditions and Notices to Offerors 52.204-7 (DEV) System for Award Management-Registration (Nov 2024) (DEVIATION NOV 2025) 52.212-1 (DEV) Instructions to Offerors-Commercial Products and Commercial Services (Sep
2023) (DEVIATION NOV 2025)
52.216-1 (DEV) Type of Contract (Apr 1984) (DEVIATION DEC 2025) 52.219-4 (DEV) Notice of Price Evaluation Preference for HUBZone Small Business Concerns (Oct 2022) (DEVIATION DEC 2025) 52.252-5 Authorized Deviations in Provisions (Nov 2020) 2852.233-70 Protests Filed Directly with the Department of Justice (NOV 2020) L.1 General Instructions for Preparing Proposals L.2 Proposal Preparation Instructions: Volume 1 – Technical Proposal L.3 Proposal Preparation Instructions: Volume 2 - Past Performance L.4 Proposal Preparation Instructions: Volume 3 – Price Proposal L.5 Small Business Subcontracting Plan L.6 Instructions for Submission of Proposals L.7 Submission of Questions L.8 Proposal Submission Deadline
M Evaluation Factors for Award 52.217-5 (DEV) Evaluation of Options (July 1990) (DEVIATION AUG 2025) M.1 Basis for Award M.2 Evaluation Criteria M.3 Technical Capability M.4 Past Performance M.5 Price
15BPCC26R00000004 Page 5 of 68
Section B - Supplies or Services and Prices/Costs
Body-Worn Cameras (BWC)
Firm Fixed Price
SCHEDULE OF SUPPLIES/SERVICES
CONTINUATION SHEET
ITEM NO. SUPPLIES/SERVICES EST.
QUANTITY
UNIT UNIT PRICE AMOUNT
0001 See instructions in:
* L.4 Proposal Preparation Instructions: Volume 3 – Price Proposal
* M.5 Factor 3 - Price
PSC: 5836
0 EA $________ $_________________
Clauses By Full Text
B.1 Description of Supplies or Services
Under the policies and procedures prescribed in the Revolutionary Federal Acquisition Regulation Overhaul (RFO) Part 12
(Acquisition of Commercial Products and Commercial Services) and RFO Part 15 (Contracting by Negotiation), the Contractor shall provide Body-Worn Cameras (BWCs) and all associated hardware, accessories, software, cloud services, licensing, warranties, updates, training, technical refresh, and support required to fully implement and operate the Federal Bureau of Prisons’ (FBOP) nationwide Body-Worn Camera program.
The Contractor shall furnish commercially available, Trade Agreements Act (TAA) compliant BWC hardware meeting all technical, durability, recording, storage, battery, activation, and integration requirements identified in Section C (Statement of Work). Supplies and services include, but are not limited to:
• BWC devices;
• Magnetic mounts, cables, docking stations, chargers, and related accessories;
• Required software licenses and cloud solution access for evidence upload, storage, retention, redaction, chain of custody, administrative controls, and reporting;
• Unlimited cloud storage meeting, at minimum, FedRAMP Moderate Authorization requirements and suitable for obtaining an agency Authority to Operate (ATO);
• Comprehensive warranty coverage for hardware, software, accessories, and components, to include no cost firmware/ software updates during the support period;
• Training (including Train the Trainer), implementation, maintenance, and technical support services;
• Technology refresh.
All supplies and services shall meet or exceed the specifications and operational requirements described in Section C. Offerors proposing non-OEM items shall provide documentation demonstrating OEM authorization.
B.2 Type of Contract
The Government intends to award a Firm Fixed-Price (FFP), Indefinite-Delivery/Requirements contract with one (1) base year and up to seven (7) one-year option periods. At the Government’s discretion, an additional six-month extension may be exercised in accordance with FAR 52.217-8.
15BPCC26R00000004 Page 6 of 68
B.3 Pricing
Offerors shall provide firm-fixed unit prices for BWC hardware, accessories, cloud services, software licenses, warranty coverage, support services, implementation, and technology refresh.
Pricing must account for:
• Hardware meeting SOW specifications.
• Mounts, cables, necessary accessories, chargers, and docking stations.
• All software and cloud licenses necessary for full operational capability.
• Unlimited digital evidence storage and retention per SOW requirements.
• Minimum warranty coverage.
• Shipping included in unit pricing.
• Technical support obligations.
• Training, Train-the-Trainer programs, and administrative/supervisory training.
• Technology Refresh
Offerors shall provide a pricing schedule accounting for all items included in Section B.4.
B.4 Estimated Quantities
Estimated quantities of BWC devices and associated products are in Attachment J.1 – FBOP Facility Implementation Schedule V.1.
These quantities reflect anticipated needs for deployment across the FBOP’s four-year rollout but do not represent a guaranteed purchase amount. Actual quantities will depend on funding availability, operational need, and institutional deployment timelines.
Orders will be issued and funded via individual delivery orders.
END OF SECTION B
15BPCC26R00000004 Page 7 of 68
Section C - Description/Specifications/Statement of Work
Clauses By Full Text
C.1 Statement of Work
1. Background
The Federal Bureau of Prisons (FBOP) is responsible for the custody and care of approximately 154,000 federal offenders.
Approximately 91 percent of these inmates are housed within FBOP-operated facilities, with the remainder placed in community-based locations. Additional information about the FBOP mission and operations is available at www.bop.gov.
2. Pupose and Scope
The purpose of this Statement of Work (SOW) is to establish all requirements for the acquisition, deployment, configuration, integration, training, maintenance, support, and lifecycle management of Body#Worn Cameras (BWCs) and the associated digital evidence software at Federal Bureau of Prisons institutions nationwide.
The BWC Program will enhance agency ability to:
• Document staff–inmate interactions;
• Improve accountability and transparency;
• Support investigations of inmate allegations and administrative matters;
• Strengthen compliance with FBOP policies and operational directives;
• Provide valuable media for incident review and training.
This initiative will be implemented through a structured four-year phased rollout. The contractor shall provide all hardware, accessories, software, licenses, cloud services, technical expertise, logistical planning, integration support, training, and warranty/ maintenance services necessary to successfully deploy BWCs and digital evidence systems at the institutions, which includes hardware deployment, software configuration, cloud service integration, training, and operational support requirements. The deployment schedule is in Attachment J.1 - FBOP Facility Implementation Schedule V.1.
3. Body-Worn Camera Requirments
BWCs will be used as audio and video recording devices equipped to users as part of their uniform to document what they see and hear in the performance of their duties when interacting with federal inmates. The solution licensure will be based upon a shared use model with an estimated 75-150 cameras in use during peak shifts. The cameras will be required (24) hours a day, spanning (3) shifts.
3.1 Hardware Functionality Requirements
3.1.1 Design and Durability
• The BWC hardware shall be black in color; constructed with IP67 or higher dust and water-resistant protection; capable of operating in temperatures ranging from #4°F to 120°F; equipped with a scratch resistant lens; and capable of continued operation after a six-foot drop.
• The solution shall include multiple mounting options (lapel, shoulder, belt, uniform button, zipper jacket, helmet, etc.) and provide simple single switch activation/deactivation for power and recording.
• The device shall include a minimum of 16GB internal/integrated storage.
15BPCC26R00000004 Page 8 of 68
3.1.2 Video and Audio Recording
• The device shall provide a minimum 120-degree field of view; record full color video at 720p resolution using the H.264 codec; record at 30 FPS or greater; include built-in microphone; support lowlight recording with auto white balance and auto exposure; and provide at least 30 seconds of pre-event buffering, configurable up to two minutes.
3.1.3 Battery Performance
• The device shall provide a minimum of 12 hours of continuous recording time per full charge.
• The battery shall fully recharge in less than 8 hours.
3.1.4 Assignment, Alerts, Notifications, and Activations
• The BWC devices shall be assignable using the individual’s agency issued Personal Identity Verification (PIV) card that will be scanned to register and check out the device.
• The system shall provide the capability for collocated BWCs to be alerted when a single device begins recording, with an option for collocated devices to autoactivate.
• Designated personnel shall be able to activate all BWCs in the event of an emergency.
• The solution shall support integration with agency issued radios (manufacturer agnostic, where technically feasible) to trigger automatic BWC activation during body alarm/man down events.
3.1.5 Hardware Technical Requirements
• Vendor shall provide free firmware and software updates throughout the support period.
• Vendor shall ensure availability of replacement parts and repairs during the support period.
• Vendor shall provide technical support sufficient to resolve system integration issues, bugs, performance deficiencies, and configuration challenges.
• Hardware must be Trade Agreement Act (TAA) compliant.
3.2 Warranty Coverage
3.2.1 Warranty
Vendor shall provide a warranty covering all hardware, software, accessories, and components from date of purchase until the equipment is refreshed. All exclusions must be clearly identified in proposal submissions.
3.2.2 Hardware Warranty Coverage
Vendor shall provide no cost repair or replacement (including shipping) for defective cameras, batteries, and docking/charging equipment within the warranty period.
3.2.3 Accessories Warranty Coverage
Vendor shall provide no-cost repair or replacement (including shipping) of defective clips, mounts, cables, and related accessories within the warranty period.
3.2.4 Repair/Replacement Timeline
Defective products must be repaired or replaced within 10 business days of receipt within the warranty period.
Products not repairable within 10 days shall be replaced with a model equal to or better and compatible with existing infrastructure.
15BPCC26R00000004 Page 9 of 68
3.3 Technology Refresh
The Contractor shall propose a technology refresh approach as part of its offer. The Government intends to understand the
Contractor’s recommended methods, timelines, and cost structures for refreshing body-worn camera equipment during the period of performance. The refresh is intended to maintain operational effectiveness, ensure continuity of service, and leverage advancements in the Contractor’s product line.
At a minimum, the Contractor’s proposed technology refresh approach shall address:
• Availability and Conditions: The Contractor shall identify when a technology refresh will be made available during the contract period and describe any conditions or limitations associated.
• Scope of Refresh: The Contractor shall define what equipment, components, or services would be included in a potential technology refresh. Examples may include updated camera hardware, batteries, mounts, or other elements necessary to maintain system operability. The Contractor may recommend additional refresh elements based on industry best practices.
Pricing Method: The Contractor shall provide a clear, structured pricing methodology for a technology refresh.
• Compatibility and Integration: The Contractor shall explain how its proposed refresh would remain compatible with, software, evidence management systems, accessories, and other infrastructure provided under this contract.
• Delivery and Execution: The Contractor shall propose timelines and processes for implementing the technology refresh.
4. Solution Licensing and Cloud Storage Requirements
4.1 Cloud Solution
The FBOP requires a cloud-based solution (SaaS preferred) for storage, management, redaction, sharing, protection, and disposal of digital evidence. Any proposed system shall be at a minimum Federal Risk and Authorization Management
Program (FedRAMP) Moderate Authorized and capable of obtaining an agency issued Authority to Operate (ATO).
4.2 Licensing
Vendor shall provide all necessary software licenses and documentation for full operational use, including terms and conditions. Any required licensing must 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 and any expanded use.
4.3 Data Ownership
All BWC content is FBOP-owned. Vendor shall have no rights, title, or interest in agency content which is the government’s records. The FBOP is solely responsible for sharing, managing, retaining, redacting, and deleting agency content. The vendor will have limited access to agency content and said access that is granted is solely for providing and supporting any cloud services to the agency and agency end-users. Agency-owned content includes, but is not limited to, video and/or audio taken with any device procured through this contract.
4.4 Storage
15BPCC26R00000004 Page 10 of 68
The system shall support unlimited cloud storage capacity.
Vendor shall support data retention up to 10 years and provide best practices for storage and cost management.
4.5 Termination Requirements
Agency data must remain accessible for at least 90 days after contract termination, during which vendor shall provide complete data export prior to deletion.
4.6 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 proposed solution, shall at the minimum, have a FedRAMP Moderate Authorization and be compliant as a cloud service provider (CSP). The contractor shall include their FedRAMP Package ID for verification in their proposal. A FedRAMP and FBOP-compliant ATO is required by the agency prior to the solution going into production.
FedRAMP Authorized is defined as follows: The service has a Provisional Authorization to Operate (P-ATO) via the Joint Authorization Board (JAB). Further information about the FedRAMP certification process is available at www.fedramp.gov.
4.7 Disaster Recovery and Failover
• The solution shall include a secondary hosting facility with automatic failover. If the alternate interface differs from the primary interface, restoration to full operations must occur within 12 hours.
• Vendor shall perform annual disaster recovery tests and provide evidence of successful testing to the COR.
• The system shall maintain redundant backups separate from the operational environment.
• Archived files shall be retrievable within 24–48 hours and restorable into the active environment.
4.8 Access Requirements
• The system shall be accessible via web browser on any web-enabled device without client software installation.
• The solution shall support secure transfer of large media files even under low-bandwidth conditions. No browser plugins shall be required, and non#proprietary codecs are preferred.
• The system shall encrypt and validate integrity of media starting at device upload, preserving raw unaltered originals throughout the lifecycle.
• The system shall support uploading of at least 800 videos simultaneously and support queued upload operations.
• The system shall support 3,000 total users and 500 concurrent users, scalable to 20,000 or more concurrent users.
• System availability shall be no less than 99.5%. Failure shall result in contractual service credits.
• The system shall enable Okta-based Single Sign-On for all web-based and cloud services associated with the BWC.
• Integration of BWC management software with Active Directory. The integration will enable centralized identity and access control for all users involved in camera deployment, review, and administration. Features include role assignments (such as administrators, supervisors, and reviewers), device assignment for issued cameras, and alignment with existing director structures.
5. System Functionality Requirements
• The system shall maintain evidentiary recording quality sufficient for authentication and admissibility in federal court, with complete chain of custody tracking.
• The system shall securely capture, ingest, and organize all BWC media and related metadata.
• Users shall upload media with minimal interaction using docking stations, plug#in devices, or wireless upload.
• The system shall support upload from any connected device in any non#proprietary file format.
• Users shall be able to export media in original or standard formats.
15BPCC26R00000004 Page 11 of 68
• The system shall provide automated time/date stamping and metadata fields including:
• Post
• Location/Badge #
• Incident number
• Evidence designation
• Secure/Sensitive flag
• The system shall support bulk upload and bulk metadata tagging operations.
• The system shall support drag and drop and copy/paste upload interfaces.
• The system shall allow users to work from or share copies of files without modifying originals.
• The system shall include basic file manipulation features including:
• Cut-and-paste
• Crop
• Zoom in/out
• 360° rotation
• 3D rotation
• Filters
• Enhancement tools
• Light adjustment
• Opacity adjustment
• Black-and-white conversion
• The system shall support printing of photos and reports.
• System access shall be role based, permission based, and unit/group based.
• Roles, permissions, and units shall be predefined and easily assignable by administrators.
• Users may hold multiple roles but cannot operate in conflicting roles simultaneously.
• The system shall support access#control functions that allow files or file segments to be hidden from unauthorized users.
• The system shall recognize assigned devices, associate them with specific users, and track metrics on uploads, downloads, and data quantities.
• The solution shall allow secure sharing of files with authorized users for defined or indefinite periods.
• The system shall allow secure sharing with non#users via time#limited links integrated with Outlook.
• The system shall support streaming playback without requiring downloads.
• The system shall support downloading watermarked read#only media to encrypted devices.
• The system shall support both simple and advanced searching, including:
• Name or partial name
• Date/time or range
• Incident number
• Incident type
• Location
• Unit/Badge #
• User
• Device
• Archival/deletion date or range
• Review date or range
• Authorized users shall be able to tag, categorize, annotate, and mark files for later review.
• The system shall allow users to limit searches to their own recordings.
• Supervisors shall have the capability to review subordinate personnel’s recordings.
• The system shall support workflow task tracking and automated notifications.
• The system shall support creation of case collections for investigation, analysis, sharing, and export.
• The system shall provide standardized and customizable reports including:
• Chain of Custody
• Evidence Log
• Case File
• Property Inventory
6. Privacy Act and Freedom of Information Act (FOIA) Requirements
15BPCC26R00000004 Page 12 of 68
The solution shall include integrated tools for editing and redacting media files (audio/video) in accordance with Privacy Act and
FOIA requirements.
Redaction tools must allow authorized personnel to:
• Delete specific portions of audio or video content.
• Blur selected video portions and tag FOIA exemptions.
• Crop audio or video segments.
• Scramble or redact audio content.
• Automatically detect, track, and redact faces or objects.
• Export raw files in standard H.264 format compatible with tools such as Adobe Photoshop and Adobe Premiere.
All alterations must be logged in the system’s audit trail and must be accessible for legal or administrative review.
The solution shall preserve evidentiary integrity such that original and edited files remain admissible in federal court. Solutions with proven evidentiary reliability will be considered favorably.
Vendor personnel may not alter or redact, release, or delete any recording, in part or in whole, without legal (Court/U.S.
Attorney’s Office) or administrative authority (valid FOIA request through the FOIA office) to do so.
7. Service Level Agreement (SLA)
The vendor shall provide technical support and system assistance consistently with a Service Level Agreement (SLA) that ensures reliable and timely support for FBOP personnel.
The vendor shall provide telephone and email technical support Monday through Friday, from 7:30 a.m. to 8:00 p.m. Eastern
Standard Time.
The vendor shall provide after#hours emergency support for critical outages and urgent operational issues, including immediate triage and escalation in accordance with SLA protocols.
The vendor shall adhere to the following response times:
• Critical incidents: immediate acknowledgement; continuous work until resolved.
• High#priority issues: acknowledgement within one hour.
• Routine technical issues: acknowledgement within 24 hours.
The vendor shall maintain documented SLA procedures detailing escalation paths, severity classifications, communication expectations, and resolution targets.
The vendor shall provide all patches, bug fixes, updates, and security enhancements for supplied software and shall coordinate update scheduling with the COR.
The vendor shall maintain minimum system availability of 99.5%. Failure to meet this standard shall result in service credits.
The vendor shall continuously monitor system performance, including upload success, file integrity, encryption processes, metadata accuracy, access controls, and authentication mechanisms.
The vendor shall submit SLA compliance reports, as requested by the COR, including ticket counts, response times, resolution summaries, outage reports, performance metrics, and deviations.
Vendor support personnel shall be trained to protect sensitive information.
15BPCC26R00000004 Page 13 of 68
8. Administrative and Records Management Requirements
8.1 Administrative Controls
The system shall:
• Allow system administration accounts to manage the FBOP’s files and data.
• Support a hierarchy of administration accounts enabling headquarters, regional, and institution-level management.
• Permit assignment of roles, permissions, and unit/group level access as defined by FBOP administrators.
• Prevent users from operating in conflicting roles simultaneously.
• Recognize assigned devices, associate them with specific users, and track upload/download activity and data quantities.
8.2 Records Management Requirements
8.2.1 Metadata Capture
Store at a minimum, the following metadata for each file:
• Date/Time stamp
• User
• Location/Department/Post
• Badge number
• Incident/Case number
• Subject name(s) involved
• Subject register number
8.2.2 Retention and Disposition
• Support implementation of FBOP Records Schedules and retention periods of up to 10 years.
• Allow permissions-based control to set and modify retention periods by role and unit.
• Allow standard and special retention requirements per file or per group of files.
• Support schedules for automatic purge dates, archival, and deletion, with notifications prior to action.
• Automatically purge video based on defined business rules while preserving a review period before deletion.
• Allow users to review files scheduled for deletion based on the retention schedule and notifications.
9. Implementation and Deployment Requirements
The vendor shall provide all labor, planning, coordination, materials, tools, and technical expertise necessary to support the implementation and deployment of the FBOP’s Body-Worn Camera (BWC) Program across all institutions identified in
Attachment J.1 - FBOP Facility Implementation Schedule V.1.
The vendor shall develop and deliver a comprehensive Implementation and Deployment Plan that outlines all activities required to achieve full operational capability at each institution. The plan shall include detailed methodologies for hardware installation, software configuration, data integration, training, scheduling, logistics, and coordination with FBOP personnel.
The vendor shall provide a detailed rollout timeline aligned with the four-year phased deployment schedule. The timeline shall identify all tasks, required resources, sequencing, interdependencies, risks, and milestones for each institution.
15BPCC26R00000004 Page 14 of 68
The vendor shall perform all site-specific assessments necessary to ensure readiness for BWC deployment. These assessments shall identify networking, power, mounting, and docking requirements at each location.
The vendor shall install, configure, and activate all hardware components required for BWC operation, including cameras, docking stations, chargers, mounts, accessories, and any supporting infrastructure.
The vendor shall configure the Digital Evidence Management System (DEMS) and cloud-based digital evidence platform to meet
FBOP technical and operational requirements. This includes user provisioning, role and permission setup, integration with Active
Directory and Single Sign-On (SSO), configuration of metadata fields, retention policies, workflows, and tagging schemes.
The vendor shall ensure all integration points function correctly, including:
• Camera-to-docking station upload.
• Cloud ingestion and file encryption.
• Automated time/date stamping.
• Metadata tagging.
• Role-based access control.
• Administrative and supervisory tools.
• Reporting functions.
• Integration with agency-issued radios (where feasible).
• System notifications and automated alerts.
Prior to activation at each institution, the vendor shall conduct on-site Testing and Validation to confirm full system functionality. Validation shall include hardware performance, battery endurance, upload accuracy, cloud storage functionality, role-based permissions, search capabilities, and media playback.
The vendor shall provide on-site training prior to system activation. Training shall include device operation, docking procedures, daily care, upload workflows, evidence management, storage and retention procedures, redaction tools, and basic system navigation.
The vendor shall provide a Train-the-Trainer Program at each institution. A minimum of five (5) FBOP institution staff at each location shall be certified as trainers capable of delivering ongoing instruction to new and existing users.
The vendor shall provide administrative, investigative, and supervisory training for personnel responsible for system configuration, digital evidence management, oversight, reporting, and workflow operations. This training shall support up to thirty (30) staff per institution.
The vendor shall provide all training materials, including manuals, quick-start guides, lesson plans, course outlines, and digital documents necessary for continued training after deployment.
The vendor shall assign a Project Manager responsible for oversight, coordination, scheduling, communication, documentation, and full execution of all vendor responsibilities under this section.
10. Project Management Requirements
The vendor shall provide all planning, direction, coordination, oversight, and control necessary for project execution. The vendor’s Project Manager shall serve as the primary liaison with the FBOP.
• Kick-Off Meeting - Vendor shall attend a kickoff meeting with FBOP personnel to discuss approach, policies, procedures, and deliver an overview of the technical strategy.
15BPCC26R00000004 Page 15 of 68
• Project Plan - The contractor shall provide a Project Plan that describes the technical approach, project personnel roles, organizational structure, available resources and management controls to be employed to meet the), performance, schedule and milestones, communications, and quality requirements throughout the contract execution.
The contractor must periodically update this Project Plan if there are any major changes in the work and/or schedule as bilaterally agreed to by the contractor and FBOP.
• A draft project plan is due within five (5) days after the kick-off meeting.
• The final Project Plan shall be due within ten (10) days after FBOP review and comments.
• Project Schedule - Within the Project Plan, the contractor shall provide a Project Schedule for all tasks assigned under this contract. The contractor Project Manager shall ensure that the Project Schedule is developed and presented to the FBOP Project Manager/Contracting Officer Representative (COR) as part of the Project Plan. The Project Schedule shall identify all tasks, resources, and schedule. The Project Schedule shall become the schedule for the task and shall be maintained and updated weekly by the contractor for the duration of the contract/task to show progress completed. Tasks must have a short enough duration to update the project schedule on a weekly basis.
• Progress Reports - The contractor shall provide written progress reports on a weekly and monthly basis for the duration of the project. These reports will be emailed to the COR and FBOP Project Manager. The Weekly Progress Report shall cover all work completed during the previous week and shall present the work to be accomplished during the subsequent week.
The Weekly Progress Report shall be between one (1) and three (3) pages in length. The Monthly Progress Report shall be a summary of the prior 30 days’ work and the subsequent 30 days’ work to be accomplished. The Monthly Progress Report shall be no longer than ten (10) pages in length. These reports shall also identify any problems that arose and a statement explaining how the problem was resolved. These reports shall also identify any problems that have arisen but have not been completely resolved and provide an explanation. Additionally, status updates shall be provided during bi-weekly project status meetings.
• Meeting Minutes - Vendor shall support meetings by preparing agendas, minutes, briefing materials, and managing scheduling. All virtual meetings shall be hosted on FBOP collaboration platforms.
10. Deliverables
Deliverable Format Due Acceptable
Project Kick-Off Meeting Microsoft Teams Project Start Meeting between FBOP designated staff and contract team to discuss approach, policies and procedures. The contractor shall provide a briefing on their technical approach for accomplishing results that meet the objectives of Project Stakeholders.
Project Plan Microsoft Word 5 days after kick-off Describes the technical approach, project personnel roles, organizational structure, available resources and management controls to be employed to meet the cost, performance, schedule and milestones, communications, and quality requirements throughout the contract execution.
Project Schedule Microsoft Word/Excel/MS
Project (or other scheduling tool)
10 days after kick-off Within the Project Plan, the contractor shall provide a
15BPCC26R00000004 Page 16 of 68
Project Schedule for all tasks assigned under this contract.
The contractor Project Manager shall ensure that the Project
Schedule is developed and presented to the FBOP Project
Manager/Contracting Officer
Representative (COR) as part of the Project Plan. This shall identify all tasks, resources, and schedule. The Project Schedule shall become the schedule for the task and shall be maintained and updated weekly by the contractor for the duration of the contract/ task to show progress completed.
RACI Chart Microsoft Word/Excel 30 days after award Outlines Customer vs FBOP responsibilities, including but not limited to project milestone tracking, UAT testing, meeting coordination, etc.
Progress Reports Microsoft Word Ongoing (weekly & monthly) Written progress reports on a weekly and monthly basis for the duration of the project.
These reports will be emailed to the COR and FBOP Project
Manager.
Risk Management Plan
(data loss)
Microsoft Word 45 days after award Correct format, free of grammatical/clerical errors, on time.
Change Management Plan
(organizational communication)
Microsoft Word 45 days after award Correct format, free of grammatical/clerical errors, on time.
Training Plan Microsoft Word 90 days after award Correct format, free of grammatical/clerical errors, on time.
Master Data Management Plan Microsoft Word/Excel 90 days after award, continuously updated
Correct format, free of grammatical/clerical errors, on time.
User Roles, Access, Permissions, and Security Plan, to include
Security Information Assurance
Package for Authority-to-
Operate (ATO) to comply with
NIST 800-53 security control assessment and authorization
Microsoft Word/Excel
+ standard NIST 800-53 format
120 days after award, continuously updated
Correct format, free of grammatical/clerical errors, on time.
Training Library
(how-to guides)
Multiple 120 days after award, continuously updated
Correct format, free of grammatical/clerical errors, on time.
15BPCC26R00000004 Page 17 of 68
END OF SECTION C
15BPCC26R00000004 Page 18 of 68
Section D - Packaging and Marking
Clauses By Full Text
D.1 Packaging and Marking Requirements
All BWC hardware, accessories, mounts, docking stations, chargers, cables, and related components shall be packaged in accordance with normal commercial practices to ensure safe shipment, handling, storage, and protection from environmental conditions.
The Contractor shall place the contract and delivery order number on or adjacent to the exterior shipping label. Packages shall clearly identify the products contained, including the delivery order number(s), product number(s), and quantity. This information may be placed on the bill of lading.
The Contractor shall replace any products damaged or lost prior to Government acceptance at no additional cost to the Government.
The Contractor shall maintain the capability to track items sold and shipped under this contract in the event a recall becomes necessary for warranty replacement and shall provide such information to the Contracting Officer upon request.
The Contractor shall meet delivery schedules with the entire quantity of products ordered via delivery order. Equipment shall be shipped as complete shipments only. No partial shipments shall be accepted without prior approval from the CO or COR.
END OF SECTION D
15BPCC26R00000004 Page 19 of 68
Section E - Inspection and Acceptance
Clauses By Full Text
E.1 Quality Assurance / Testing Requirements
The Contractor shall utilize its existing commercial quality assurance system to inspect or test commercial products before presenting them to the Government for acceptance in accordance with RFO 12.105(a). The Government reserves the right to inspect or test any supplies or services tendered for acceptance in accordance with RFO 52.212#4(b) (DEVIATION NOV 2025). Failure to maintain the standards established at award may constitute grounds for initiation of contract termination proceedings.
E.2 Firmware Updates / Patches
The Contractor shall ensure that all firmware updates, patches, or revisions provided during the period of performance maintain or exceed performance and security standards established at award.
• Testing and Validation: Prior to release, the Contractor shall conduct internal QA testing to ensure updates do not adversely impact system stability, interoperability, or mission functionality. Documentation of testing shall be made available to the COR upon request.
• Security Assurance: The Contractor is responsible for ensuring updates are free of known vulnerabilities and malware, and for securing delivery mechanisms against unauthorized modification during transmission or installation.
• Notification and Documentation: The Contractor shall provide written notification to the COR at least ten (10) business days prior to release of any non#emergency firmware update, accompanied by detailed Release Notes (changes, fixes, limitations).
• Regression and Corrective Action: If an update results in degradation or failure to meet contract specifications (a “regression”), the Contractor shall, at no cost to the Government, provide a corrective patch or stable rollback version within five (5) business days of Government notification.
E.3 Warranties
E.3.1 Minimum Warranty: The Contractor shall warranty all products (hardware, software, accessories, and components) purchased under this contract to be free of manufacturing defects from time of purchase through technology refresh. All warranty exclusions must be clearly identified in proposal submissions.
E.3.2 Hardware Coverage: The Contractor shall provide no cost repair or replacement (including shipping) for defective cameras, batteries, and docking/charging equipment within the warranty period.
E.3.3 Accessories Coverage: The Contractor shall provide no cost repair or replacement (including shipping) of defective mounts, cables, and related accessories within the warranty period.
E.3.4 Repair / Replacement Timeline: Defective products must be repaired or replaced within ten (10) business days of receipt within the warranty period. Products not repairable within ten (10) business days shall be replaced with a model equal to or better, and compatible with existing infrastructure.
END OF SECTION E
15BPCC26R00000004 Page 20 of 68
Section F - Deliveries and Performance
Clauses By Full Text
F.1 Period of Performance
The anticipated period of performance shall be a twelve (12) month base period, beginning on the date of award, with seven (7) possible one-year option periods and a six (6) month option to extend.
F.2 Delivery Schedule Timeline
The Contractor shall deliver within sixty (60) days after receipt of an individual delivery order. In the event of delay, see Section F.3.
F.3 Notice to the Government of Delays
If the Contractor encounters difficulty meeting delivery schedules or completion dates, or has knowledge of circumstances that may delay performance, the Contractor shall notify the CO and COR in writing within five (5) business days, providing:
(1) a detailed justification for the delay, and
(2) a realistic delivery timeline.
F.4 Place of Delivery
Products shall be shipped to all FBOP locations CONUS and OCONUS (Hawaii and Puerto Rico). Shipping addresses will be specified at the time of order. Delivery shall be “FOB Destination.”
RFO 52.24734 F.o.b. Destination (Jan 1991)
(a) The term “f.o.b. destination,” as used in this clause, means:
(1) Free of expense to the Government, on board the carrier’s conveyance, at a specified delivery point where the consignee’s facility is located; and
(2) Supplies shall be delivered to the destination consignee’s wharf (if destination is a port city and supplies are for export), warehouse unloading platform, or receiving dock, at the expense of the Contractor. The Government shall not be liable for any delivery, storage, demurrage, accessorial, or other charges involved before actual delivery (or “constructive placement” per carrier tariffs) to the destination, unless such charges are caused by an act or order of the Government acting in its contractual capacity. If rail carrier is used, supplies shall be delivered to the specified unloading platform. If motor carrier (including “piggyback”) is used, supplies shall be delivered to truck tailgate at the unloading platform, except when supplies meet the requirements of Item 568 of the National Motor Freight Classification for “heavy or bulky freight.” When supplies meeting Item 568 are delivered, unloading
(including movement to tailgate) shall be performed by the consignee, with assistance from the truck driver, if requested. If the contractor uses rail carrier or freight forwarder for less#than#carload shipments, the contractor shall ensure the carrier furnishes tailgate delivery, when required, if transfer to truck is needed to complete delivery.
(b) The Contractor shall:
(1)(i) Pack and mark the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .