S02_36C10B25Q0535_RTLS Northport_Final.pdf

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. UEI: EFT:

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. NOV 2021)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

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

36C10B25Q0535 09-05-2025

Jennifer Jefferson, Contract Specialist

848-337-5339 09-10-2025 10 am ET

36C10B Department of Veterans Affairs Office of Procurement, Acquisition and Logistics (OPAL) Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

541512

$34 Million

N/A

X

See Schedule of Supplies/Services

36C10B

Department of Veterans Affairs

OPAL

Technology Acquisition Center 23 Christopher Way

74KW9

AgileRank, LLC 21525 Ridgetop Cir Ste 310 Sterling, VA 20166-8518

Y5PTNH8M5GA1

Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971 http://www.fsc.va.gov/einvoice.asp

See CONTINUATION Page

Title: Passive Real Time Location System Asset Tracking Solution – Northport, NY VA Medical Center

Points of Contact:

Contracting Officer: John Vardouniotis;

ioannis.vardouniotis@va.gov Contract Specialist: Jennifer Jefferson;

Jennifer.jefferson@va.gov; 848-377-5339

This is a sole source to AgileRank, LLC via the Veterans First Contracting Program

Delivery shall be completed within six months of award.

See Continuation Pages

See CONTINUATION Page

X X

John Vardouniotis

Request for Quote # 36C10B25Q0535

Table of Contents

SECTION A

A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

B.2 GOVERNING LAW CLAUSE

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

B.4 SCHEDULE OF SUPPLIES/DELIVERABLES

B.5 PERFORMANCE WORK STATEMENT

SECTION C - CONTRACT CLAUSES

C.1 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

C.2 FAR 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR

INFORMATION SYSTEMS (NOV 2021)

C.3 FAR 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO

IMPLEMENT STATUTES OR EXECUTIVE ORDERS—COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES (JAN 2025)(DEVIATION FEB 2025)

C.4 FAR 52.223-23 SUSTAINABLE PRODUCTS AND SERVICES (MAY 2024)

(DEVIATION FEB 2025)

C.5 FAR 52.227-19 COMMERCIAL COMPUTER SOFTWARE LICENSE (DEC 2007) . 87

C.6 VAAR 852.204-71 INFORMATION AND INFORMATION SYSTEMS SECURITY

(FEB 2023)

C.7 VAAR 852.219-73 VA NOTICE OF TOTAL SET-ASIDE FOR VERIFIED SERVICE-

DISABLED VETERAN-OWNED SMALL BUSINESSES (JAN 2023)(DEV)

C.8 VAAR 852.219-75 VA NOTICE OF LIMITATIONS ON SUBCONTRACTING –

CERTIFICATE OF COMPLIANCE FOR SERVICES AND CONSTRUCTION (JAN 2023)

(DEVIATION)

C.9 VAAR 852.239-76 INFORMATION AND COMMUNICATION TECHNOLOGY

ACCESSIBILITY (FEB 2023)

C.10 VAAR 852.247-71 DELIVERY LOCATION (OCT 2018)

C.11 VAAR 852.247-72 MARKING DELIVERABLES (OCT 2018)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 FAR 52.252-1 PROVISIONS INCORPORATED BY REFERENCE

E.2 FAR 52.204-24 REPRESENTATION REGARDING CERTAIN

TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT

(NOV 2021)

E.3 FAR 52.204-29 FEDERAL ACQUISITION SUPPLY CHAIN SECURITY ACT

ORDERS—REPRESENTATION AND DISCLOSURES (DEC 2023)

E.4 FAR 52.212-2 EVALUATION—COMMERCIAL PRODUCTS AND COMMERCIAL

SERVICES (NOV 2021)

E.5 FAR 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS-

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (MAY 2024) (DEVIATION

FEB 2025)

E.6 FAR 52.216-1 TYPE OF CONTRACT (APR 1984)

E.7 FAR 52.233-2 SERVICE OF PROTEST (SEPT 2020)

E.8 BASIS OF AWARD

E.9 QUOTE SUBMISSION

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: AgileRank, LLC

21525 Ridgetop Circle, Suite 310 Sterling, VA 20166-8518

b. GOVERNMENT: Contracting Officer 36C10B

Technology Acquisition Center 23 Christopher Way

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

[X] 52.232-33, Payment by Electronic Funds Transfer—System For Award

Management, or

[] 52.232-36, Payment by Third Party

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X – In accordance with Schedule of Supplies/Services]

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.

See website at: http://www.fsc.va.gov/einvoice.asp

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

AMENDMENT NO DATE

http://www.fsc.va.gov/einvoice.asp

B.2 GOVERNING LAW CLAUSE

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.3 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.cpars.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.

http://www.cpars.gov/

B.4 SCHEDULE OF SUPPLIES/DELIVERABLES

Any resulting contract will be awarded on a firm-fixed-price basis as defined by Federal Acquisition Regulation Subpart 16.202. Accordingly, the Contractor shall ensure that any and all costs associated with the Contractor’s proposed application(s), software products, software solution, and/or system, shall be included in the Contractor’s proposed firm-fixed price, and shall serve as the Contractor’s firm-fixed price for the life of any resulting contract. No additional costs or fees relative to the Contractor’s proposed application(s), software products, software solution, and/or system including, but not limited to, licensing costs and any associated licensing maintenance required for the development, delivery, integration, operation, and/or maintenance of the Contractor’s proposed solution will be allowed, accepted, and/or paid by the Government.

NOTE: Respondents are instructed to complete Section B.4 below and submit with its quote. Respondents are cautioned that alterations to the line items specified below will not be accepted and may render its quote unacceptable.

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

Base Period

All delivery, installation, configuration, and approvals shall be complete, and a fully functional RTLS AT solution shall be in place within six months of award. Sustainment services for 12 months shall be provided upon successful deployment/go-live of the RTLS AT solution.

All products/services shall be in accordance with (IAW) the Performance Work Statement (PWS), entitled, “Passive Real Time Locating System (RTLS) Asset Tracking (AT) Solution – Northport, NY VA Medical Center“, dated September 2, 2025, as set forth in section B.5 of this solicitation.

Applicable Product Service Codes (PSC) are noted in each Contract Line-Item Number

(CLIN)

CLIN Description Quantity Unit Unit Price Total Price

Project Management IAW PWS section 5.1 and all subparagraphs.

This CLIN includes all labor, supplies, travel, associated reports and program management required for the successful and timely completion of the services/deliverables detailed in the

PWS.

The price of this CLIN shall be included in the priced CLINs.

1 Lot

(LT)

Not Separately

Priced

(NSP)

NSP

0001AA

Deliverable Monthly Progress Report IAW PWS section 5.1.2

Due 30 days after award and monthly thereafter.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0001AB

Deliverable Final Technical Kickoff Meeting Presentation IAW PWS section 5.1.3

Due within three days of the Technical Kickoff Meeting.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0001AC

Deliverable Technical Kickoff Meeting Minutes IAW PWS section 5.1.2

Due within three days of the Technical Kickoff Meeting.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

Hardware IAW PWS sections 5.2, 5.3, and all subparagraphs.

This CLIN includes all supplies, travel, hardware, and any other items required for the successful and functional passive RTLS AT solution.

PSC: 7E20

1 LT $ $

0002AA

Deliverable Signed Facility Receiving Report IAW PWS section 5.3.1

Due on day of any hardware delivery.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0002AB

Deliverable Rendered Maps of Installed Infrastructure Device Locations IAW PWS section 5.3.2

1 LT NSP NSP

Due within 30 days after implementation

Electronic submission to: VA PM, COR, CO, CS

Software IAW PWS section 5.2, 5.4 and all subparagraphs.

This CLIN includes all software, travel, and any other items required for the successful and functional passive RTLS AT solution.

PSC: DA01

1 LT $ $

0003AA

Deliverable Software Installation Report IAW PWS section 5.4.1

Due within 30 days after implementation.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0003AB

Deliverable Configuration Changes Document IAW PWS section 5.4.2

Due within 30 days after implementation.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

Services IAW PWS section 5.2, 5.5, 5.6, 5.7, 5.9, 5.11, 6.2, and all subparagraphs.

This CLIN includes all supplies, software, travel, and any other items required for the successful and functional passive RTLS AT solution.

PSC: DA01

1 EA $ $

0004AA

Deliverable Tagging and Commissioning Plan IAW PWS section 5.5

Due 30 days prior to delivery.

Electronic submission to: VA PM, COR, CO, CS

0004AB

Deliverable System Administration Dashboard IAW PWS section 5.6

Due on the same day as delivery.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0004AC

Deliverable Acceptance Test Plan IAW PWS section 5.7

Due seven days before date of implementation.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0004AD

Deliverable Performance Test Plan Methodology IAW PWS section 5.7.1

Due 15 days before date of implementation.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0004AE

Deliverable Performance Test Results IAW PWS section 5.7.1

Due within 30 days following test completion.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0004AF

Deliverable Warranty Status Report IAW PWS section 5.9

Due seven days prior to implementation.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0004AG

Deliverable Continuous Monitoring Security Artifacts IAW PWS section 5.11

Due as outlined by FedRAMP requirements.

Electronic submission to: VA PM, COR, CO, CS

0004AH

Deliverable Continuous Monitoring Scans IAW PWS section 5.11

Due as outlined by FedRAMP requirements.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0004AJ

Deliverable Plan of Action and Milestones Reports IAW PWS section 5.11

Due as outlined by FedRAMP requirements.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0004AK

Deliverable Contractor Staff Roster IAW PWS section 6.2.2

Due within three business days after award

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

Training IAW PWS sections 5.8 and all subparagraphs.

This CLIN shall include all supplies, services, travel, and any other items for the successful completion of this

CLIN.

PSC: DA01

1 LT NSP NSP

0005AA

Deliverable Training Plan IAW PWS section 5.8

Due at least 30 days prior to implementation.

Electronic submission to: VA PM, COR, CO, CS

0005AB

Deliverable Training Materials and Schedules IAW PWS section 5.8

Due at least seven days prior to any scheduled training.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

0005AC

Deliverable Completed Training Report IAW PWS section 5.8

Due within seven days after any completed training.

Electronic submission to: VA PM, COR, CO, CS

1 LT NSP NSP

Sustainment – Ongoing Maintenance & Technical Support IAW PWS sections 5.2 – 5.11 and all subparagraphs.

This CLIN shall include all supplies, services, travel, and any other items for the successful sustainment of the functional passive RTLS AT solution.

Sustainment shall be 12 months from time of deployment/-go live.

PSC: DA01

1 LT $ $

Task Order Total $

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration (VHA)

Veterans Integration Services Network (VISN) 2 Northport VA Medical Center (VAMC)

Passive Real Time Locating System (RTLS) Asset Tracking (AT) Solution

Date: September 2, 2025

VA-25-00090173

PWS Version Number: 1.1

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Veterans Health Administration (VHA), Veteran Integrated Services Network (VISN) 2 - Northport VA Medical Center (VAMC) has a requirement for installation of a new Passive Real Time Location System (RTLS) Asset Tracking System solution. The solution shall cover strategic areas of the VAMC as checkpoints: Warehouse, Community Living Centers (CLC) 1, 2, 3, 4, and Building 200 (main hospital) entrance. The Northport VAMC currently relies on legacy technology for asset management, resulting in significant operational and clinical challenges related to asset tracking and inventory control. Presently, assets are identified via barcode labels, which provide limited data primarily for identification purposes. Implementing an advanced asset tracking solution would enable real-time tracking of asset location and status, thereby enhancing process efficiency and operational accuracy. This capability can lead to improved clinical workflows, reduced staff time spent on locating equipment and performing maintenance and eventually optimized inventory levels to reduce costs. Adoption of a modern asset tracking system is essential for healthcare facilities seeking to improve operational efficiency and support high-quality patient care. VHA, VISN 2 – Northport VAMC seeks to implement the following Passive RTLS application based on the same platforms at other VISN 2 facilities

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 2016

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. Carnegie Mellon Software Engineering Institute, Capability Maturity Model®

Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Acquisition (CMMI-ACQ), Version 1.3 November 2010

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

10. Public Law 109-461, Veterans Benefits, Health Care, and Information

Technology Act of 2006, Title IX, Information Security Matters

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

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

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

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

15. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and

Guidelines,” January 18, 2017

16. Office of Management and Budget (OMB) Circular A-130, “Managing Federal

Information as a Strategic Resource,” July 28, 2016

17. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed

Services (CHAMPUS)”

18. NIST SP 800-66 Rev. 1, An Introductory Resource Guide for Implementing the

Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008

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

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

21. VA Directive 6500, “VA Cybersecurity Program,” January 24, 2019

22. VA Handbook 6500, “Risk Management Framework for VA Information Systems

– Tier 3: VA Information Security Program,” March 10, 2015

23. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal

Information (SPI)”, July 28, 2016

24. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring of

VA Information Systems,” February 3, 2014

25. VA Handbook 6500.5, “Incorporating Security and Privacy into the System

Development Lifecycle”, March 22, 2010

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

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

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

29. OI&T 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

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

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

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

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

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

35. VA Directive 6300, Records and Information Management, September 21, 2018

36. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010

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

38. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015

39. OMB Memorandum, “Transition to IPv6”, September 28, 2010

40. VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, October 26, 2015 https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx

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

42. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006

43. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003

44. 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

45. OMB memorandum M-11-11, “Continued Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, February 3, 2011

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

47. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011

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

49. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007

50. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, December 2017

51. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014

52. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices

(Draft), October 2012

53. Draft National Institute of Standards and Technology Interagency Report

(NISTIR) 7981 Mobile, PIV, and Authentication, March 2014

54. 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)

55. 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)

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

57. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.2, Federal Interagency Technical Reference Architectures, Department of Homeland Security, June 19, 2017 https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf

58. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007

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

60. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552) https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552

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

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

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

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

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

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

67. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote

Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

69. “Veteran Focused Integration Process (VIP) Guide 3.2”, December 2018, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

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

71. RTLS Enterprise Data Architecture (EDA) Standards Workbook

72. RTLS Requirements Specification Document

3.0 SCOPE OF WORK

The Contractor shall install a new passive RTLS AT solution at the Northport VAMC campus. This project will cover strategic areas of the medical center as checkpoints:

Warehouse, CLC 1, 2 ,3, 4, and building 200 (main hospital) entrance. These checkpoints were selected as the locations where movement between mobile beds and stretchers can be tracked. The first phase of the project will be focused on tracking bed and stretcher movement throughout the hospital and CLCs. The solution shall provide the Northport VAMC the ability to monitor critical assets such as hospital beds and stretchers through a centralized interface and reporting platform. The solution shall provide precise location tracking to minimize the operational costs associated with manual inventory counts. The solution shall capture comprehensive inventory data in real-time as they move through checkpoints, automatically reconciling this information daily with the existing Automated Engineering Management System/Medical Equipment Reporting (AEMS/MERS) Vista databases, ensuring data accuracy and operational consistency.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

All delivery, installation, configuration, and approvals shall be complete, and a fully functional RTLS AT solution shall be in place within six months of award. Sustainment services for 12 months shall be provided upon successful deployment/go-live of the RTLS AT solution.

Any work at a Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

There are 11 Federal holidays set by law (USC Title 5 Section 6103) that VA follows.

Under current definitions, five are set by date:

New Year's Day January 1 Juneteenth June 19 Independence Day July 4 Veterans Day November 11 Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday.

Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February Memorial Day Last Monday in May Labor Day First Monday in September Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November

VA’s Normal Working Hours are 7:00 am to 4:30 p.m., Monday through Friday. Several departments are always operational. The Contractor may work earlier or later in the day and on weekends or federal holidays with the COR’s approval at no additional cost to the VA. Noise disturbances and utility shutdowns/tie-ins shall be coordinated with the COR and not interfere with VA daily operations.

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at the location below. Work may be performed at remote locations with prior concurrence from the COR.

Department of Veterans Affairs VA Medical Center - Northport NY 79 Middleville Rd., Buildings 200, 92 and 8.

Northport, NY 11768

The Contractor, their personnel, and their subcontractors shall be subject to the Federal laws, regulations, standards, and VA Directives and Handbooks regarding information and information system security as delineated in this contract.

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort throughout the PoP. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 STAFFING REQUIREMENTS

The Contractor shall provide a single Contract Implementation Manager, and one standby Backup Manager, as the sole points of contact to coordinate and manage all interactions, engagement, and services provided to the Government under this contract.

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR with Monthly Progress Reports in electronic form in Microsoft (MS) Word, MS PowerPoint, or MS Project formats for this contract. The report shall include detailed instructions/explanations for each required data element to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding month.

The Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including a plan and timeframe for resolving the issue. The Contractor shall maintain communication with VA, so issues that arise are quickly identified and visible to both parties to prevent unnecessary escalation of outstanding issues. The Monthly Progress Report is due 30 days after award then monthly afterwards.

The Contractor shall hold a status meeting with the COR and technical Point of Contacts (POC), as specified by the COR, to discuss all items identified in the Monthly Progress Reports and other issues as identified by the COR.

Deliverable:

A. Monthly Progress Reports

5.1.3 TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 10 days after contract award. The Contractor shall coordinate the date, time, and location (can be virtual) with at minimum the CO, VA Program Manager (PM), the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO, CS, PM and COR at least five calendar days before the meeting. Upon Government approval of a final agenda, the Contractor shall distribute to all meeting attendees.

During the kickoff-meeting, the Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort via a MS PowerPoint presentation.

At the conclusion of the meeting, the Contractor shall update the presentation with a final slide entitled “Summary Report,” which shall include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting. The Contractor shall submit the final updated Final Technical Kickoff Meeting Presentation to the CO, PM, and COR within three calendar days after the meeting. The Contractor shall also work with the CS, the Government’s designated notetaker, to prepare, finalize, and distribute CS-approved meeting minutes of the kickoff meeting to the CO, COR, and all attendees within three calendar days after the meeting. The Contractor shall obtain concurrence from the CS on the content of the meeting minutes prior to distribution of the document and distribute the Technical Kickoff Meeting Minutes to all attendees.

Deliverables:

A. Final Technical Kickoff Meeting Presentation B. Technical Kickoff Meeting Minutes

5.2 RTLS DESIGN

5.2.1 RTLS TIME STAMP

The Contractor shall ensure all applications synchronize with internal VA site time standards. The synchronization of time on this network is critical to every aspect of managing, securing, planning, and debugging as it identifies when an event occurred.

5.2.1 WIRELESS TECHNOLOGY

The Contractor shall utilize the existing Wi-Fi infrastructure at each facility, where possible, to meet standards of location accuracy or shall implement clinical grade location hardware where requirements cannot be met using the existing Wi-Fi.

5.3 RTLS HARDWARE

5.3.1 HARDWARE PROVISIONING

The Contractor shall provide all necessary hardware components specified in the HDDD delivered to the applicable site. Hardware components shall include all infrastructure components, tags, and batteries necessary for asset tracking. The Contractor shall coordinate with the COR and site POCs to schedule delivery and secure required written COR concurrence prior to shipping hardware.

The Contractor shall provide, but not limited to, the following:

• Hardware o 11 each Fixed RF Readers o 20 each Antennas o Two Each - Handheld Scanners o 600 Passive Tags (on metal, 1 roll) o One each Printer (on-metal) o One Printer Cart o Necessary cables, wiring, cords, chargers, power supplies, all associated material.

• Cabling/Networking o All hardware shall have a Windows Operating System (OS) of Windows 11 (or newer), 64 Bit or newer, unless embedded OS. All Windows Server must run on Windows Server 2019 or newer.

o Interface shall be compliant with VA Enterprise Facility IT Support Infrastructure Standard.

o Any offsite server or network maintenance or support provided by the Contractor shall only be done via VPN access after the Contractor has obtained the VPN access from the VA.

o Contractor must possess a nationally approved Memorandum of Understanding-Interconnection Service Agreement (MOU/ISA) or ATO (Authority to Operate) within 30 days of award.

o Contractor must provide VA form 6550 Appendix A, MDS2 (if applicable) and draft network topology at the time of submission for each component that touches the IT network (application server, database server, reporting server, etc). Network topology diagram or supplement must include which ports and communication protocols are used. Each server and component will require its own 6550 and MDS2 form. Those with identical security profiles may be combined on the same form. A single nursing unit can be used to pictorialize any components (hubs, switches, master stations, domes, consoles, terminals, etc) downstream of servers. Submission must include an export of services running on each operating system (TXT file, tab delimited) and port/protocol requirements for functionality.

o All cabling and accessories to provide a complete and functional system.

o Cabling shall be CAT 6 certified or higher.

The Contractor shall submit to the COR a copy of the Signed Facility Receiving Report confirming delivery of components at each site. The Signed Facility Receiving Report shall be due day of delivery. The Signed Facility Receiving Report shall contain:

1. Confirmation of the order and delivery of the components.

2. Reconciliation (if any) of planned versus actual delivery items.

3. Details shall include location of delivered items, time of delivery, and from whom the Government received them.

A. Signed Facility Receiving Report

5.3.2 INFRASTRUCTURE INSTALLATION AND CONFIGURATION

The Contractor shall install all necessary RTLS hardware components delivered to the sites listed in Section 4.2. The Contractor shall coordinate with the COR and site POCs to schedule and complete installation.

The Contractor shall install RTLS supporting hardware and components to blend in (or not be visible) with the general surface treatments of the facility. The Contractor shall install RTLS components to have minimal impact on the business operations of the facility and meet applicable infection control and health and safety requirements such as: The Joint Commission and local Infection Control Risk Assessment findings and standards. Hardware installation shall occur during normal business hours. The Contractor shall use containment units for any above the ceiling work in required areas.

When installation of an infrastructure device requires a data connection, the Contractor shall use existing data connections whenever possible. If a new data connection and cabling is required, the Contractor shall provide the cabling and the cabling services.

The Contractor and the site POC shall coordinate with VA OIT regarding the network connections.

Per hardware design changes or VA reconfiguration requirements, the Contractor shall update rendered maps in the software. Where applicable, naming shall conform to data standards as outlined in the RTLS Asset Tracking Enterprise Data Architecture (EDA) Standards Workbook.

The Contractor shall provide Current Rendered Maps of Installed Infrastructure Device Locations (i.e., “as-built drawings”). The Rendered Maps of Installed Infrastructure Device Locations shall be due 30 days after implementation.

A. Rendered Maps of Installed Infrastructure Device Locations

5.4 RTLS SOFTWARE

5.4.1 SOFTWARE PROVISIONING AND INSTALLATION

The Contractor shall provide perpetual license(s) for all software needed to support

RTLS.

The Contractor shall provide and install all necessary software for each RTLS application as designated by VA.

The software shall be compatible with the existing CenTrak and Infor software currently in use. VA will provide a virtual server platform on which software may reside.

The Contractor shall provide, but not limited to, the following:

• Software:

o Mobile interfaces – FedRAMP ATO approval needed o All associated licenses o Enterprise middleware site license o AEMS/MERS interface o SSOi/Active Directory

The Contractor shall provide a Software Installation Report; it shall include a list of all software and licenses installed at the site. The Software Installation Report shall be due 30 days after implementation.

A. Software Installation Report

5.4.2 USER INTERFACE PROVISIONING AND CONFIGURATION

The Contractor shall use VA ATO-approved or pilot approved user interfaces per hardware design changes and/or VA reconfiguration requirements. The Contractor shall provide rendered maps that are compatible with Infor LBI application. Naming shall conform to data standards as outlined in the RTLS Asset Tracking EDA Standards Workbook. The Contractor shall determine configuration changes needed during the facility site visit(s) and shall provide a Configuration Changes Document for each facility. The Configuration Changes Documents are due 30 days after implementation.

Per hardware design changes or VA reconfiguration requirements, the Contractor shall develop, or update rendered maps in Infor software. Where applicable, naming shall conform to data standards as outlined in the RTLS EDA Standards Workbook.

Deliverable:

A. Configuration Changes Document

5.4.2.1 INTERFACES WITH VA INVENTORY, MAINTENANCE MANAGEMENT, AND

CLINICAL SYSTEMS

The Contractor shall provide VA ATO-approved system interfaces, to include AEMS/MERS, Maximo, Personal Identity Verification/ Single Sign-On Integration, and Vocera, as well as Electronic Health Records Modernization as needed. The Contractor shall provide, implement, and test all interfaces provided.

5.5 PLANNING AND DEPLOYING ASSET TAGS

The Contractor shall create and provide a Tagging and Commissioning Plan (TCP) for sites to be reviewed and approved by the COR prior to beginning the tagging process.

The TCP shall be due 30 days prior to delivery and include:

1. Identification of all assets to be tagged (to include non-expendable equipment, environmental assets, hand hygiene assets, and staff/patient tags).

2. A schedule during normal business hours (not to interrupt business operations) to tag and commission all assets.

3. Guidance and instructions on tag placement (unless provided by the Government).

4. Method for quality control of tag placement and commissioned data.

5. Method for taking corrective actions on misplaced tags, defective tags, assets that cannot be located, incorrect information in the RTLS database, and other errors that can occur during the tagging and commissioning process.

6. Documentation that would allow Government personnel to perform the tagging and commissioning process.

The Contractor shall provide the COR with the TCP within 15 days of receiving request from the COR. Upon COR approval of the TCP, the COR will provide the Contractor with the number of items to be tagged.

A. Tagging and Commissioning Plan

5.6 SYSTEM ADMINISTRATION

The Contractor shall provide Database and System Administration services during the implementation and warranty period. The System Administration services shall include:

1. Perform daily system health checks on servers and databases, including monitoring application logs.

2. Provide security compliance and remediation of application related vulnerabilities.

3. Apply Monthly Operating System security patches provided by VA OIT.

4. Troubleshoot connectivity issues.

5. Troubleshoot startup/shutdown server and application issues.

6. Implement software upgrades provided by Original Equipment Manufacturer.

In addition to tasks listed above, the Contractor shall provide the following additional Database and System Maintenance and Administration services during the implementation and warranty period:

1. Perform all tagging of new equipment and any re-tagging that is necessary.

2. Provide training to VA staff as needed.

The Contractor shall provide a System Administration Dashboard. The System Administration Dashboard shall be due same day as delivery, and provide user access and control database and location.

A. System Administration Dashboard

5.7 ACCEPTANCE TESTING

The Contractor shall create and provide an Acceptance Test Plan that complies with Section 5.7.1, Phase 1: Performance Testing, and Section 5.7.2, Phase 2: User Acceptance Testing. The Acceptance Test Plan shall define testing methodology consistent with this implementation. The Contractor shall not conduct testing until the

COR approves the Acceptance Test Plan. The Acceptance Test Plan is due seven day before date of implementation.

A. Acceptance Test Plan

5.7.1 PERFORMANCE TESTING

The Contractor shall perform testing on the system and/or system enhancements to certify Proof of Performance.