36C10B23Q0525 FINAL.docx

VA Police Cloud Record Management System (RMS) Implementation 36C10B23Q0525

PAGE 1 OF

1. REQUISITION NO.

2. CONTRACT NO.

3. AWARD/EFFECTIVE DATE

4. ORDER NO.

5. SOLICITATION NUMBER

6. SOLICITATION ISSUE DATE

a. NAME

b. TELEPHONE NO. (No Collect Calls)

8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY

CODE

10. THIS ACQUISITION IS

UNRESTRICTED OR

SET ASIDE:

% FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ

IFB

RFP

15. DELIVER TO

CODE

16. ADMINISTERED BY

CODE

17a. CONTRACTOR/OFFEROR

CODE

FACILITY CODE

18a. PAYMENT WILL BE MADE BY

CODE

TELEPHONE NO.

DUNS:

DUNS+4:

PHONE:

FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER 18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19.

20.

21.

22.

23.

24.

ITEM NO.

SCHEDULE OF SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA

26. TOTAL AWARD AMOUNT (For Govt. Use Only) 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________

29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DATED ________________________________. YOUR OFFER ON SOLICITATION

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER) 30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

(REV. 2/2012)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

VA-23-00071616

36C10B23Q0525 08-29-2023 Sean McAvoy, Contract Specialist 848-377-5094 08-31-2023

3PM EST

Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way

Eatontown, NJ 07724

541519

150 EMP

N/A

N/A X

See Delivery Schedule

23 Christopher Way

Eatontown NJ 07724

Axon Enterprise, Inc.

17800, North 85TH Street Scottsdale, Arizona 85255, United States

Financial Services Center PO Box 149971 Austin TX 78714-8971

See CONTINUATION Page

Title: VA Police Cloud Record Management System (RMS) Implementation

Type of Contract: Firm Fixed Price (FFP)

Period of Performance: 12 months from date of award, with three (3) 12-month option periods

See Section B.4 for Price Schedule.

Points of Contact:

Sean McAvoy 848-377-5094 / Sean.Mcavoy1@va.gov

Contract Specialist Kathryn Pantages 848-377-5039 / Kathryn.Pantages@va.gov

Contracting Officer

Kathryn Pantages Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto, as permitted by FAR 12.212. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C. § 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

(1). Definitions.

a) Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs (“VA”) and is synonymous with “Government.”

b) Licensor. The term “licensor” shall mean the Contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “Contractor” is the party identified in Block 17a on the SF1449. If the Contractor is a reseller and not the Licensor, the Contractor remains responsible for performance under this Contract/Order.

c) Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.

d) Maintenance. The term “maintenance” is the process of enhancing and optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

e) Technical Support. The term “technical support” refers to the range of services providing assistance for the software via the telephone, email, a website or otherwise.

f) Release or Update. The term “release” or “update” are terms that refer to a revision of software that contains defect corrections, minor enhancements or improvements of the software’s functionality. This is usually designated by a change in the number to the right of the decimal point (e.g., from Version 5.3 to 5.4). An example of an update is the addition of new hardware.

g) Version or Upgrade. The term “version” or “upgrade” are terms that refer to a revision of software that contains new or improved functionality. This is usually designated by a change in the number to the left of the decimal point (e.g., from Version 5.4 to 6).

(2). Software License.

a) Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work Statement or Product Description, the software license provided to the Government is a perpetual, nonexclusive license to use the software.

b) The Government may use the software in a networked environment.

c) Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).

d) All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

(3). Software Maintenance and Technical Support.

a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this Contract/Order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received, the Contractor is neither authorized nor permitted to renew any of the previously furnished services.

b) The Contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the Contractor to its commercial customers so as to cause the software to perform according to its specifications, documentation or demonstrated claims.

c) Any telephone support provided by Contractor shall be at no additional cost.

d) The Contractor shall provide all maintenance services in a timely manner in accordance with the Contractor’s customary practice or as defined in the Performance Work Statement or Product Description. However, prolonged delay (exceeding 2 business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.ppirs.gov).

e) If the Government allows the maintenance and support to lapse and subsequently wishes to reinstate it, any reinstatement fee charged shall not exceed the amounts that would have been charged if the Government had not allowed the subscription to lapse.

(4). Disabling Software Code. The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the Contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the Government. Inability of the Contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5). Manuals and Publications. Upon Government request, the Contractor shall furnish the most current version of the user manual and publications for all products/services provided under this Contract/Order at no cost.

B.3 CONTRACT ADMINISTRATION DATA

1. Contract Administration: All contract administration matters will be handled by the following individuals:

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor will be made in accordance with:

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X] Upon acceptance of deliverables in accordance with B.5, Price Schedule

4. GOVERNMENT INVOICE ADDRESS: All Invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of Payment Requests.

5. ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

B.4 PRICE SCHEDULE

Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination

BASE PERIOD

Period of performance shall be 12 months from date of award.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.1.

Period of Performance: 12 months

Due within two (2) business days of Kickoff Meeting.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Due weekly throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Due within 3 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.2.

Period of Performance: 12 months

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.3.

Period of Performance: 12 months

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.4.

Period of Performance: 12 months

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.5.

Period of Performance: 12 months

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.6.

Period of Performance: 12 months

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Due within 90 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.7.

Period of Performance: 12 months

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.8.

Period of Performance: 12 months

Due within 90 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Due within 90 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.9.

Period of Performance: 12 months

Due monthly, as required, when Service Outages or Disruptions occur.

Electronic submission to: VA PM, COR, CS.

Due within 60 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after award and shall be updated and maintained throughout the PoP when major function changing released occur.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.10.

Period of Performance: 12 months

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after award and shall be updated and maintained throughout the PoP as new features or functionality are added, delivered 14 days prior to scheduled training Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.11.

Period of Performance: 12 months

Due within 10 business days after award and shall be updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

Seven (7) business days prior to scheduled testing.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after User Acceptance or System Reliability Testing Electronic submission to: VA PM, COR, CS.

OPTION PERIOD ONE

This 12-month option period may be exercised in the sole discretion of the Government in accordance with (IAW) FAR 52.217-9 Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, the 12-month option period is to commence immediately upon expiration of the base period.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.1.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Due weekly throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.2.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.3.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.4.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.5.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.6.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.8.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.9.

Period of Performance: 12 months

Due monthly, as required, when Service Outages or Disruptions occur during the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period when major function changing released occur.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.11.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Seven (7) business days prior to scheduled testing during the Option Period.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after User Acceptance or System Reliability Testing during the Option Period.

Electronic submission to: VA PM, COR, CS.

OPTION PERIOD TWO

This 12-month option period may be exercised in the sole discretion of the Government in accordance with (IAW) FAR 52.217-9 Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, the 12-month option period is to commence immediately upon expiration of the Option Period One.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.1.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Due weekly throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.2.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.3.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.4.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.5.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.6.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.8.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.9.

Period of Performance: 12 months

Due monthly, as required, when Service Outages or Disruptions occur during the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period when major function changing released occur.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.11.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Seven (7) business days prior to scheduled testing during the Option Period.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after User Acceptance or System Reliability Testing during the Option Period.

Electronic submission to: VA PM, COR, CS.

OPTION PERIOD THREE

This 12-month option period may be exercised in the sole discretion of the Government in accordance with (IAW) FAR 52.217-9 Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, the 12-month option period is to commence immediately upon expiration of the Option Period Two.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.1.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Due weekly throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Updated and maintained throughout the PoP.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.2.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.3.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.4.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.5.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.6.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.8.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.9.

Period of Performance: 12 months

Due monthly, as required, when Service Outages or Disruptions occur during the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Shall be updated and maintained throughout the Option Period when major function changing released occur.

Electronic submission to: VA PM, COR, CS.

This FFP CLIN includes all travel, labor and deliverables for the successful completion of services detailed in PWS Section 5.11.

Period of Performance: 12 months

Shall be updated and maintained throughout the Option Period.

Electronic submission to: VA PM, COR, CS.

Seven (7) business days prior to scheduled testing during the Option Period.

Electronic submission to: VA PM, COR, CS.

Due within 10 business days after User Acceptance or System Reliability Testing during the Option Period.

Electronic submission to: VA PM, COR, CS.

B.5 PRODUCT DESCRIPTION

VA Police Cloud Record Management System (RMS) Implementation 36C10B23Q0525

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

VHA Police

VA Police Cloud Record Management System (RMS) Implementation

Date: June 22, 2023

VA-23-00071616

PWS Version Number: 2

1.0 BACKGROUND

The VA Police is a federal law enforcement organization within the U.S. Department of Veterans Affairs with unique responsibilities dedicated to reducing crime and protecting those assets under the charge and control of the Veterans Health Administration. The VHA Office of the Senior Security Officer (OSSO), Director of Law Enforcement Services has determined that in response to VA Office of Inspector General (VA OIG) Report 19-05798-107 (VA Police Information Management System), that a replacement for the current VA Police reporting system was required to fully implement the recommendations contained in the report. The VA OIG recommended that steps be taken to employ a solution that meets the information management needs of VA Police while providing the highest level of information security processes to prevent unauthorized use of, and proper storage or disposal of records.

In FY2022, VA entered an IDIQ (36C10X22D0024) with Axon Enterprises Inc., with a period of performance consisting of the base year, and 4 option years, to provide a pAMP high assurance cloud storage platform, including user licenses to access the content. Under the terms of the IDIQ, VA Police have access to a Digital Evidence (DEMS), Standards (Internal Affairs), and Records Management (RMS) features, with unlimited storage. The current VA Police RMS contract will end on 9/30/2023. The agency has a mission critical need, to build out the RMS portion of the Axon platform. As part of Contract No. 36C10X22D0024, VA Police Body and Vehicle Cameras and Evidence Cloud Storage, Veterans Affairs Police Services have activated licenses and unlimited storage for Axon Records. Consequently, Axon Records is available to configure and use by Veterans Affairs Police Services at any point during the life of this contract. The configuration and workflow customization are limited to Axon personnel only. The work in this PWS requires access to, and expertise in, the Axon platform.

The 2023 Omnibus Bill amends Section 902 of title 38 requiring the Secretary to track and analyze data regarding arrests, tickets, prosecution, use of weapons and force, and complaints against department police officers. The law requires VA to implement a department-wide data system to carry out the tracking and analysis of the data. The IT services from The contractor shall enable VA to fully implement capabilities that were acquired in IDIQ(36C10X22D0024) in order comply with law. Axon services are the only solution to initiate and support setup, configurations, and provisioning of the RMS portion of the already deployed Axon solution. Axon engineering will allow VA Police to utilize the full capability of our RMS, providing a single point of access for officers to interface with the entire police records system, simplifying and streamlining workflow for use of force, evidence, incident reporting, and data analysis into one system.

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”

2. “Federal Information Security Modernization Act of 2014”

3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements for Cryptographic Modules”

4. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,” August 2013

7. 10 U.S.C. § 2224, "Defense Information Assurance Program"

8. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

9. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters

10. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”

11. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm

12. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm

13. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5, 2019

14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017

15. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

16. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”

17. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008

18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” March 12, 2019

23. VA Handbook 6500.5, “Incorporating Security and Privacy into the System Development Lifecycle,” March 22, 2010

24. VA Handbook 6500.6, “Contract Security,” March 12, 2010

25. VA Handbook 6500.8, “Information System Contingency Planning,” April 6, 2011

26. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018

27. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

28. OIT Process Asset Library (PAL), https://www.va.gov/process/ . Reference Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp

29. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

30. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

31. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015

32. VA Handbook 6510, “VA Identity and Access Management,” January 15, 2016

33. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

34. VA Directive 6300, “Records and Information Management,” September 21, 2018

35. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

36. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

37. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

38. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

39. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014

40. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

41. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

42. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

43. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture (https://arch.idmanagement.gov/#what-is-the-ficam-architecture)

44. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

45. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

46. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

47. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile Devices (Draft),” October 2012

48. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981, “Mobile, PIV, and Authentication,” March 2014

49. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

50. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

51. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

52. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

53. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

54. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

55. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007

56. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005

57. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018

58. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

59. VA Directive 0058, “VA Green Purchasing Program,” July 19, 2013

60. VA Handbook 0058, “VA Green Purchasing Program,” July 19, 2013

61. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

62. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

63. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

64. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

65. “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

66. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

67. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

68. Social Security Number (SSN) Fraud Prevention Act of 2017

69. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

3.0 SCOPE OF WORK

The Contractor shall provide professional services to complete police report form configuration, establish workflow processes, build data analysis reports, and provide ongoing sustainment services. The Contractor shall migrate and configure data from the current VA Police RMS into the Axon platform, fully enabling a complete reporting and data analysis system. The contractor shall complete work in phases to configure, deploy, scale, and sustain a high reliability basic incident reporting system.