VMS PWS v06092023 RFQ.pdf

Department of Justice (DOJ) Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF)

Special Operations Division (SOD)

Performance Work Statement (PWS)

Law Enforcement Surveillance Camera Airship Brand Name or Equal

Video Management System (VMS) June 9, 2023

1.0 General

1.1 Background: ATF is a law enforcement organization. ATF’s unique responsibilities consist of reducing violent crime, collecting revenue, and protecting the public. ATF enforces Federal laws and regulations relating to alcohol, tobacco, firearms, explosives, and arson by working directly and in cooperation with other government agencies.

1.2 Objective: ATF requires 400 Airship brand name or equal Enterprise Sensor Device Licenses and 400 Airship brand name or equal Advantage Platinum Support licenses to add to ATF’s existing Cloud-Based Airship Video Management System (VMS).

1.3 Scope: The contractor shall provide all products and services to support the VMS as a turnkey solution. A turnkey solution means a type of system built end-to-end for ATF that can be easily implemented into the current ATF process. The solution shall be immediately ready to use upon delivery and vendor implementation. Customization shall be minimal and approved by ATF prior to implementation.

Vendor shall only provide the actual number of licenses requested by ATF at the time of award or by future modifications. The Government reserves the right to order additional licenses under this requirement. The VMS system shall meet or exceed the following technical specifications:

• Must be capable of integrating with our existing Airship VMS that we are currently utilizing.

• Enterprise Licenses shall include brand name or equal Airship Acropolis and Command viewing software suite with unlimited installs.

• Capable of hosting up to 1,000 simultaneous video streams.

• Supporting multi-factor authentication in accordance with Executive Order 14028

(https://www.nist.gov/itl/executive-order-14028-improving-nations-cybersecurity).

• Capable of authentication via Active Directory/Azure, DUO, or OKTA for multi-factor authentication.

• Comply with NIST guidance for the security of data at rest and in transit as outlined in Pub

199/ FIPS 140-2.

• Comply with DOJ 0904 Cybersecurity Program Policy (Sept 16, 2016).

• Capable of being hosted in an AWS Cloud Environment.

• Integrate with AXON’s Evidence.com evidence management system for the export/transfer of ATF video evidence.

• Capable of integrating "Edge Analytics" and recording compression to leverage available bandwidth to stream a lower bit rate video, while locally recording full framerate/low compression HD video at the edge.

• All data must be hashed to verify the integrity of the recorded data.

• Shall be able to support the redaction of video.

• Provide Audit Log Reports for All Activities on System

• Shall support commercial-off-the-shelf (COTS) cameras to record audio and video in an open ONVIF format.

• Recorded evidence should comply with all federal rules of evidence.

• Shall support H.264 and H.265.

• Shall be able to support or provide "High Availability", redundant, and/or failover design/architecture.

• Shall provide a mobile app solution to simplify camera view and manipulation while on iPhone and Android phones.

• The VMS must allow for multiple administrator and user connections simultaneously.

• The VMS must be NDAA, and TAA certified.

• The VMS must have a web-based user review capability and a thick/thin client for high-resolution video review capable of multiple case/camera monitoring/review at the same time.

• The VMS must support LPR (License Plate Recorder) technology.

• The VMS must be able to process GPS geolocation information from Edge devices.

• The VMS must support "Evidence discovery" to allow the sharing of video to external parties via remote connection as required by Federal Law or Court orders.

• The VMS must support the GUI integration of Janteq and Silvus Systems Microwave Radio

/ Mesh Radio networks.

1.3.1 Support Services: The contractor shall make available 24/7 support dedicated to the ATF project equivalent to Airship brand name or equal Platinum Support. Vendor shall have technical staff on hand with the ability to gain security clearance to the Top-Secret level. Support shall include access to a Support Center (knowledge base and community forums) and access to product documentation/literature. Support shall provide comprehensive online support services to customer inquiries via email, an online knowledge base, a community help forum and online documentation.

Support shall include live telephone support. Support shall provide Priority Case Routing, Four Named Support Contacts and support hours M-F 1am – 6pm PT/PST Sat-Sun 6am – 6pm PT/PST.

Support response times shall meet or exceed the following:

Severity 1: Critical – Initial Response Time – 30 min, 24x7 Severity 2: Major – Initial Response Time – 1 business hour Severity 3: Minor – Initial Response Time – 2 business hours Severity 4: Enhancement – Initial Response Time – 1 business day

Priority definitions shall be as follows:

Severity 1: Critical – Critical production issue affecting all customers, including system unavailability and data integrity issues, with no workaround available.

Severity 2: Major – Production issue impacting a majority of customers, loss of functionality and/or significantly degraded performance, issue is persistent with no workaround available.

Severity 3: Minor – Any system issue that affects functionality or impacts performance, workaround may be possible but not sustainable.

Severity 4: Enhancement – Any request for desired functionality, information request for application capability, implementation assistance, or system issue that impacts a small number of users with an acceptable workaround available.

1.4 Required Delivery Date/Period of Performance: The required delivery date for software licenses and initial implementation of the VMS solution shall be eight weeks after receipt of contract. The period of performance for the software licenses shall be for one year after implementation and acceptance by the Government.

1.5 Delivery: Delivery shall be Free-On-Board (FOB) Destination. The place of delivery shall be the ATF Tech Shop, Nova Stokes, 5825 N. Sam Houston Parkway, Suite 300, Houston, TX 77086.

1.6 Security: In accordance with (IAW) Clause #ATF-04, ‘Background Investigations (BI) Requirements’, the nature and specific degree of background investigation or facility review will be determined by ATF’s Personnel Security Division (PSD) as required, depending upon the nature and degree of risk associated with the requirement and the position. Individuals may require access to ATF- sensitive information, IT systems, or unescorted access to ATF facilities.

However, if the contractor’s employee will require escorted access to a government facility to fix a problem, a criminal police check shall be conducted by the local field office or ATF Headquarters Physical Security Programs Branch as required. ATF Form 8620.5 shall be provided for completion prior to escorted access to ATF facilities. The contractor shall follow any other facility requirements provided by the Physical Security Branch or other authorized ATF facilities point of contract.

1.7 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this requirement may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications, or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The contractor shall notify the CO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the CO to avoid or mitigate any such OCI. The contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the CO and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as he or she deems necessary, including prohibiting the contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.8 Inspection and Acceptance:

1.8.1 Inspection and Acceptance:

1.8.1.1 Supplies or services delivered under this requirement shall be inspected and accepted by the respective COR. The Contractor shall only tender for acceptance those items that conform to the requirements of this requirement. The Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance IAW the appropriate inspection and acceptance clause.

1.8.1.2 The basis for acceptance shall be compliance with the requirements, objectives and other terms and conditions set forth in this PWS.

1.8.1.3 Deliverable items rejected shall be corrected IAW the applicable clause(s) or PWS specifications.

1.8.2 Acceptance Criteria

1.8.2.1 The respective COR will review all draft and final deliverables to ensure accuracy, functionality, completeness, professional quality, and overall compliance within the guidelines/requirements of the PWS. The Contractor shall ensure the accuracy and completeness of all deliverables. Errors, misleading or unclear statements, incomplete or irrelevant information, and or excessive rhetoric, repetition, and “padding”, shall be considered deficiencies and shall be subject to correction by the Contractor, at no additional cost to the Government.

1.8.2.2 Unless otherwise indicated, the government will require seven (7) business days to review and comment on deliverables. If the deliverable does not meet the noted criteria, the Government will return it for correction.

1.8.3 Rejection Procedures

1.8.3.1 If the respective COR rejects any deliverable, that rejected document will be handled in the manner described in this Section and the PWS.

1.8.3.2 After notification that the deliverable did not meet the acceptance criteria, unless otherwise agreed to between the Government and the Contractor, the Contractor shall resubmit an updated/corrected version within five (5) calendar days after receipt of Government comments.”.

1.8.3.3 Upon re-submission by the Contractor, the Government will reapply the same acceptance criteria. If the deliverable does not meet the acceptance criteria a second time, the Government might consider the Contractor as having deficient performance with respect to the subject PWS. In such an event, the Government may elect to procure the deliverables from another source. Here, the Contractor may be liable for any difference in the purchase price from the other source and the agreed upon to price between the Government and the Contractor.

1.8.3.4 Any rework of rejected deliverables will be completed at no additional cost to the Government - no payments will be issued against rejected deliverables, until they are corrected and accepted by the Government.

1.9 Mandatory Use of Government-to-Government Electronic Mail: Unless exempted by the CO, in writing, communication after contract award with Government agencies shall ordinarily be transmitted via electronic mail (e- mail).

1.10 General Government and Contractor Roles and Responsibilities:

1.10.1 The roles of a federal CO, a COR, other key government representatives and the Contractor Representative (CR) are explained below.

1.10.1.1 The CO ensures performance of all necessary actions for effective contracting, compliance with the contract terms, and safeguards the interests of the U.S. in the contractual relationship. The CO also ensures that the Contractor receives impartial, fair, and equitable treatment under this PWS. The CO is ultimately responsible for the final determination of the adequacy of the Contractor’s performance and authorization of pertinent remedies based on input from the COR.

1.10.1.2 The COR is responsible for technical administration of the PWS and for assuring proper government surveillance and assessment of the Contractor’s performance. The COR is the primary point of contact for the CR and shall be alerted of any changes or events that could adversely impact the Contractor’s ability to effectively perform the requirements of the PWS.

Based on a monthly analysis of the Contractor’s performance, the COR will recommend the application of remedies to the CO.

1.10.1.3 The CR serves as the single point of contact for the Contractor for collecting, reviewing, and submitting performance data and information to the CORs, engaging in discussions, and resolving issues with the COR. The CR is responsible for notifying the respective COR via email of any requested changes in the established delivery schedule for any deliverable. If this notification does not occur, the original delivery date will be used in calculating on-time delivery.

The CR shall email all deliverables to the respective COR.

1.10.1.4 The Project Leads (PL) have the primary responsibility for monitoring and reporting the Contractor performance in the areas of timely delivery and deliverable quality to the CORs.

1.11 ATF Policies, Procedures and Standards:

1.11.1 The contractor shall conform to all ATF guidelines, security requirements, and federal regulation and legislation throughout the life of the contract. ATF reserves the right to amend/upgrade these standards and internal guidelines, processes, and procedures. The following guidelines are applicable to this requirement:

a. Minimum Database Security Requirements as prescribed by the ATF Information Systems Security Office (ATF ISSO)

b. NIST Special Publication 800-53

c. ATF Minimum Security Requirements for Contractor Off Site Labs

d. ATF Publication, 7500.1 Rules of Behavior and Customer Agreement for ATF Workstation Users

e. Section 508 of the Rehabilitation Act (29 U.S.C. 794d), Subpart B – Technical Standards, 1194.21, Software Applications and Operating Systems, and 1194.22, Web-based Intranet and Internet Information and Applications, as it applies to this requirement.

1.12 System for Award Management (SAM): The selected contractor shall have an active registration in the SAM database prior to award and closing date of any solicitation in accordance with Federal Acquisition Regulation 52.204-7.

1.13 Access to Records, Data and Facilities: The contractor shall permit the CO or designated representative(s) access to all records, data, and facilities used in performance for the services covered in this PWS.

2.0 Attachments/Technical Exhibit List

2.1 Technical Exhibit 1 – Performance Requirements Summary

TECHNICAL EXHIBIT 1

Performance Requirements Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Task Objective/Result to be achieved Acceptable Level of

Performance Surveillance

Method Tasks

1.3 All licenses working simultaneously as

a VMS solution meeting all requirements defined in PWS 1.3.

Project deliverables completed that are accepted by the COR as being a turnkey solution as defined in this PWS meeting all requirements of PWS 1.3 with no required corrections.

100% Inspection

1.3.1 Support Services Support Services meeting

the response times and requirements of PWS 1.3.1 with no required corrections or delays.

100% Inspection