S02- RFP 36C10A24R0002 .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

TAC

36C10A24R0002 11-14-2023

Jermell Upton; jermell.upton@va.gov

512-981-4400 12-01-2023

15:00 EST

36C10A

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

X 100

X

541519

$34 Million

N/A

See Schedule

Y

Technology Acquisition Center

Eatontown NJ 07724

Y

See website at:

Real Time Location System (RTLS) Hardware, Software, and Professional Services

See Section B.1 for Schedule of Supplies and Services

Edgar Alonso-Bernal https//www.fsc.va.gov/einvoice.asp

Solicitation: 36C10A24R0002

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 Price Schedule of Supplies/Services

Specific requirements are detailed in Section B.4, Performance Work Statement (PWS) titled "Veterans Integrated Service Network (VISN) 21 Real Time Location System (RTLS) Hardware, Software, and Professional Services" dated October 31, 2023.

Ordering shall be conducted through the process described in B.6, “Ordering Procedures” and payment shall be made in accordance with Section B.3, Paragraph “Accounting and Appropriation Data.”

Pricing shall be placed in accordance with Attachment B.

CLIN Description Qty Unit Unit Price

Total Price

0001 -

RTLS hardware, software, and services

Total Contract Ceiling $TBD

Governing Law (continuation of Schedule of Supplies and Services above):

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 contract/order 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.

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 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 or 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/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 or order at no cost.

http://www.ppirs.gov/

B.2 CONTRACT ADMINISTRATION DATA

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

(4) CONTRACTOR: See Block 17a

(5) GOVERNMENT: Contracting Officer - See Block 31b

Technology Acquisition Center

Eatontown, NJ 07724

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

b. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X, After delivery, installation, inspection, and acceptance.]

c. 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. Instructions are provided in VA's Electronic Invoice

Presentment and Payment System (see website at http://www.fsc.va.gov/einvoice.asp).

B.3 ACCOUNTING AND APPROPRIATION DATA

Funding will be identified on the individual task orders executed against this contract.

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

B.4 PRODUCT DESCRIPTION

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veteran’s Health Administration (VHA)

Veterans Integrated Service Network (VISN) 21 Real Time Location System (RTLS) Hardware, Software, and Professional Services

Date: October 31, 2023

VA-23-00060898

PWS Version Number: 1.4

1.0 BACKGROUND

The mission of the Department of Veterans Affairs (VA), Veterans Health Administration (VHA) is to provide benefits and services to Veterans of the United States. In meeting these goals, VHA strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of the Veterans’ health care in an effective, timely and compassionate manner. Real Time Location System (RTLS) technology combines a variety of signaling and wireless communication methods to determine the location of tagged assets to speed up annual inventory, locate equipment, reduce theft/loss, and improve clinical workflow. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals.

1.1 VISN 21 REAL TIME LOCATING TECHNOLOGY

VISN 21 currently uses CenTrak® proprietary active radiofrequency identification (active RFID) hardware and software to provide real time information of asset location, staff locations, and patient locations. CenTrak® Active Asset Tracking (AT) deployed at VA Medical Centers is supplemented with the Infor® Location-Based Intelligence (LBI) user interface (UI): a platform that maps location data to provide end users with 1) a real-time graphical user interface (GUI) displaying location status for individual assets and 2) a set business intelligence reports and dashboards. These hardware and software are designed for locating assets in real time at a zonal, room-level, and within-room level accuracy.

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, “Federal Information Security Management Act (FISMA) of 2002”

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

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

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

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

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

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

8. VA Directive 0710, “Personnel Suitability and Security Program,” June 4, 2010, http://www.va.gov/vapubs/

9. VA Handbook 0710, Personnel Suitability and Security Program, September

10, 2004, http://www.va.gov/vapubs

10. VA Directive and Handbook 6102, “Internet/Intranet Services,” July 15, 2008 http://www.va.gov/vapubs/ http://www.va.gov/vapubs http://www.va.gov/vapubs

11. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility Standards,” July 1, 2003

12. Office of Management and Budget (OMB) Circular A-130, “Management of Federal Information Resources,” November 28, 2000

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

14. An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008

15. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7,

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

17. VA Directive 6500, “Managing Information Security Risk: VA Information

Security Program,” September 20, 2012

18. VA Handbook 6500, “Risk Management Framework for VA Information

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

19. VA Handbook 6500.1, “Electronic Media Sanitization,” November 03, 2008

20. VA Handbook 6500.2, “Management of Data Breaches Involving Sensitive

Personal Information (SPI)”, January 6, 2012

21. VA Handbook 6500.3, “Assessment, Authorization, And Continuous

Monitoring Of VA Information Systems,” February 3, 2014

22. VA Handbook 6500.5, “Incorporating Security and Privacy in System

Development Lifecycle” March 22, 2010

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

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

25. Project Management Accountability System (PMAS) portal (reference https://www.voa.va.gov/pmas/)

26. OI&T ProPath Process Methodology (reference process maps at http://www.va.gov/PROPATH/Maps.asp and templates at http://www.va.gov/PROPATH/Templates.asp NOTE: In the event of a conflict, OI&T ProPath takes precedence over other processes or methodologies.

27. One-VA Technical Reference Model (TRM) (reference at http://www.va.gov/trm/TRMHomePage.asp)

28. National Institute Standards and Technology (NIST) Special Publications

(SP)

29. VA Directive 6508, VA Privacy Impact Assessment, October 3, 2008

30. VA Directive 6300, Records and Information Management, February 26,

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

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

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

Program, February 17, 2011

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

Program, March 20, 2014

35. OMB Memorandum M-06-18, Acquisition of Products and Services for

Implementation of HSPD-12, June 30, 2006 https://www.voa.va.gov/pmas/ http://www.va.gov/PROPATH/Maps.asp http://www.va.gov/PROPATH/Templates.asp http://www.va.gov/trm/TRMHomePage.asp

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

37. 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,

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

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

40. NIST SP 800-116, A Recommendation for the Use of Personal Identity Verification (PIV) Credentials in Physical Access Control Systems, November 20, 2008

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

42. NIST SP 800-63-2, Electronic Authentication Guideline, August 2013

43. Draft NIST Special Publication 800-157, Guidelines for Derived PIV

Credentials, March 2014

44. NIST Special Publication 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012

45. Draft National Institute of Standards and Technology Interagency Report

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

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

47. VA Memorandum, VAIQ # 7011145, VA Identity Management Policy, June 28, 2010 (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

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

49. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.0, Federal Interagency Technical Reference Architectures, Department of Homeland Security, October 1, 2013, https://www.fedramp.gov/files/2015/04/TIC_Ref_Arch_v2-0_2013.pdf

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

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

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

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

54. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.fedramp.gov/files/2015/04/TIC_Ref_Arch_v2-0_2013.pdf https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552

55. Executive Order 13514, “Federal Leadership in Environmental, Energy, and Economic Performance,” October 5, 2009

56. Executive Order 13423, “Strengthening Federal Environmental, Energy, and Transportation Management,” January 24, 2007

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

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

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

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

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

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

62. VA Directive 6071, Project Management Accountability System (PMAS), February 20, 2013

63. VA Memorandum, “Implementation of Federal Personal Identity Verification

(PIV) Credentials for Federal and Contractor Access to VA IT Systems”, (VAIQ# 7614373) July 9, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

64. VA Memorandum “Mandatory Use of PIV Multifactor Authentication to VA Information System” (VAIQ# 7613595), June 30, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

65. VA Memorandum “Mandatory Use of PIV Multifactor Authentication for Users with Elevated Privileges” (VAIQ# 7613597), June 30, 2015;

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

3.0 SCOPE OF WORK

The Contractor shall provide the services, hardware, and software required by individual Task Orders to enable VHA to procure solutions and technical expertise across the suite of CenTrak® RFID/RTLS enabling technologies to support the needs at individual VA medical facilities (VAMC) and community-based outpatient clinics (CBOCS) within

VISN 21.

Contracts awarded will be task orders (TO) applied to this Indefinite-Delivery-Indefinite- Quantity (IDIQ) contract that will provide RTLS hardware, software, documentation and incidental services to authorized users in VHA. Incidental services include end user acceptance testing, training, warranty and maintenance services, and technical engineering services. Hardware and software delivery and installation, as well as performance of associated acceptance testing, training and warranty and maintenance services, will be required at the VISN 21 sites.

The scope of this contract shall include seven health care systems (HCS) within VISN 21, including up to one HCS that have no implementation. Work can include expansion of current sites, completion of implementation already started, and new implementations.

3.1 CONTRACT TYPE

This is an IDIQ contract. Individual Task Orders shall be issued on a performance-based Firm Fixed Price (FFP) basis.

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

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The ordering period shall be three years from the date of award. Individual orders will identify the period of performance applicable to the order. The period of performance for any task order may go up to 12 months beyond the last day of the ordering period.

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

There are eleven (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

• Independence Day July 4

• Veterans Day November 11

• Christmas Day December 25

• Juneteenth June 19

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

4.2 PLACE OF PERFORMANCE

The place of performance shall be identified in individual Task Orders. Locations will be VISN 21 medical facilities detailed below along with ancillary space such as logistics and engineering functions supporting hospital operations. The Table 4-1 lists the major RTLS sites in VISN 21 with their current status.

Facility ID Medical Centers Address

570 Fresno VA Medical Center 2615 E. Clinton Ave.

Fresno, CA 93703-2286

Northern California Health Care System, Valley Division – Sacramento VA Medical Center

10535 Hospital Way Mather, CA 95655

Northern California Health Care System, Valley Division – Martinez Outpatient Clinic

150 Muir Road Martinez, CA 94553

Facility ID Medical Centers Address

Palo Alto Health Care System, Palo Alto Division

3801 Miranda Ave.

Palo Alto, CA 94304

Palo Alto Health Care System, Palo Alto Division

4951 Arroyo Road Livermore, CA 94550-9650

Palo Alto Health Care System, Menlo Park Division

795 Willow Road Menlo Park, CA 94025-2539

654 Sierra Nevada VA Medical Center 975 Kirman Avenue Reno, NV 89502-2597

662 San Francisco VA Medical Center 4150 Clement St.

San Francisco, CA 94121

593 North Las Vegas VA Medical Center 6900 N. Pecos Road North Las Vegas, NV 89086

459 Honolulu VA Medical Center 459 Patterson Road Honolulu, HI 96819-1522

VHA

SimLearn

VHA SimLearn National Simulation Center

13800 Veterans Way, Orlando, FL 32827

Table 4-1. VISN 21 Medical Centers

Expansion of RTLS Asset Tracking in VISN 21 may include expansion to OPCs and CBOCs with the exception for the Manila Health Care System. The fully list of VISN 21 CBOCs can be found here: https://www.va.gov/directory/guide/region.asp?ID=1021

4.3 TRAVEL OR SPECIAL REQUIREMENTS

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the

Period of Performance (PoP) at any of the locations in table 4-2.

All travel will be firm-fixed price. Each travel unit shall be calculated for one individual for a period of 5 business days. The contractor shall use the Federal Travel Regulation to calculate their proposed travel price.

Proposed pricing will need to be calculated on the “Travel” tab of Attachment B. The number of units for the travel CLIN(s) needed for travel will be determined at the individual Task-Order and based on the work required per location.

4.4 GOVERNMENT FURNISHED PROPERTY

The Government has multiple remote access solutions available to include Citrix Access Gateway (CAG), Site-to-Site Virtual Private Network (VPN), and RESCUE VPN.

The Government’s issuance of Government Furnished Equipment (GFE) is limited to Contractor personnel requiring direct access to the network to: development environments; install, configure and run Technical Reference Model (TRM) approved software and tools (e.g., Oracle, Fortify, Eclipse, SoapUI, WebLogic, LoadRunner);

upload/download/ manipulate code, run scripts, and apply patches; configure and change system settings; check logs, troubleshoot/debug, and test/QA.

When necessary, the Government will furnish desktops or laptops, for use by the Contractor to access VA networks, systems, or applications to meet the requirements of this PWS. The overarching goal is to determine the most cost-effective approach to providing needed access to the VA environment coupled with the need to ensure proper Change Management principles are followed. Contractor personnel shall adhere to all VA system access requirements for on-site and remote users in accordance with VA standards, local security regulations, policies and rules of behavior. GFE shall be approved by the COR and Program Manager on a case-by-case basis prior to issuance.

Based upon the Government assessment of remote access solutions and requirements of this TO, the Government estimates that the following GFE will be required by this TO:

1. Three (3) laptops

The Government will not provide IT accessories including but not limited to Mobile Wi-Fi hotspots/wireless access points, additional or specialized keyboards or mice, laptop bags, extra charging cables, extra Personal Identity Verification card readers, peripheral devices, or additional Random-Access Memory (RAM). The Contractor is responsible for providing these types of IT accessories in support of the TO as necessary and any VA installation required for these IT accessories shall be coordinated with the COR.

4.5 SECURITY AND PRIVACY

All requirements in Section 6.0 of the PWS apply to this effort. In addition, the contractor shall:

1. Notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system).

Such issues shall be remediated as quickly as is practical, but in no event longer than three (3) days.

2. When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the contractor shall provide written notice to VA that the patch has been validated as not affecting the Systems within 10 working days. When the contractor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within 10 days.

4.5.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

In accordance with VA Handbook 0710, Personnel Security and Suitability Program, the position sensitivity and the level of background investigation commensurate with the required level of access for the following tasks within the PWS are:

Position Sensitivity and Background Investigation Requirements by Task

Task Number Tier1 / Low Risk Tier 2 / Moderate Risk

Tier 4 / High Risk

5.1

5.2

5.3

5.4

5.5

5.6

5.7

5.8

5.9

5.10

5.11

5.12

For VA Tier 1 Low Risk Position Sensitivity, the following is applicable:

A VA low risk position sensitivity requires a National Agency Check with Written Inquiries (NACI). A NACI is conducted by OPM and covers a 5-year period. It consists of a review of records contained in the OPM Security Investigations Index (SII) and the DOD Defense Central Investigations Index (DCII), FBI name check, FBI fingerprint check, and written inquiries to previous employers and references listed on the application for employment. In VA it is used for Non-sensitive or Low Risk positions.

The Tasks identified above, and the resulting Position Sensitivity and Background Investigation requirements identify, in effect, the Background Investigation requirements for Contractor individuals, based upon the tasks the particular Contractor individual will be working. The submitted Contractor Staff Roster must indicate the required Background Investigation Level for each Contractor individual based upon the tasks the Contractor individual will be working, in accordance with their submitted proposal.

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

The Contractor shall identify a Single Point of Contact (POC) to oversee the project.

The Contractor POC shall be responsible for:

• Effectively communicating and providing timely project status to VA and Contractor team members using the Monthly Activity Report.

• Ensuring the submission of contract deliverables.

• Coordinating, escalating, and resolving Contractor-related issues.

• Representing the Contractor in status meetings.

• Complying with VA’s change management process.

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline, and tools to be used in execution of this TO effort. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the TO.

The Contractor shall update and maintain the VA Program Manager (PM) approved CPMP throughout the PoP.

Deliverables:

Contractor Project Management Plan.

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide Monthly Progress Reports in electronic form in Microsoft Word and Project formats. 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 Week.

The Monthly 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 their plan and timeframe for resolving the issue. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

The Monthly Progress Report shall be required during active Task Orders.

Deliverable:

Monthly Progress Report, Due the 15th day of each month throughout the PoP of the task order.

5.1.3 TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 10 days after TO award. The Contractor shall coordinate the date, time, and location with the Contracting Officer (CO), as the Post-Award Conference Chairperson, the Contracting Officer Representative (COR), as the Co-Chairperson, and the Contract Specialist (CS).

The Contractor shall provide an agenda to the COR at least five (5) calendar days prior to the meeting. Upon Government approval of a final agenda, the Contractor shall distribute to all meeting attendees. During the kick-off 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 Microsoft (MS) Office 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 and the following statement “As the Post-Award Conference Chairperson, I have reviewed the entirety of this presentation and assert that it is an accurate representation and summary of the discussions held during the Technical Kickoff Meeting for the VISN 21 RTLS Asset Tracking Hardware, Software, and Professional Services.”

The Contractor shall submit the final MS Office PowerPoint Presentation to the CO for review and signature within three (5) calendar days after the meeting. The Contractor shall prepare and distribute the Technical Kickoff Meeting Minutes of the kickoff meeting to COR and all attendees within three (3) 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.

Deliverables A. Technical Kickoff Meeting Presentation B. Technical Kickoff Meeting Agenda C. Technical Kickoff Meeting Minutes

5.1.4 SITE ASSESSMENT

The Contractor shall perform a detailed site assessment. The Contractor shall coordinate with the COR and site POCs to schedule site assessments. The Contractor shall a conduct a pre-assessment conference call at least two weeks in advance of the site assessment. The Contractor shall coordinate the call with the COR to ensure attendance by facility stakeholders and subcontractor(s). Coordination for site assessments shall start by within 10 days after Task Order award.

The Contractor shall provide an RTLS Site Assessment Report that outlines all requirements and line items per site to include hardware, software and service. Line items shall be listed in the format of the price cost schedule with the description of the item, quantity, cost per unit, and CLIN number. The Assessment Report shall include narrative and diagrams where appropriate to demonstrate understanding of the project goals. The assessment shall include a timeline for the entire project lifecycle with the following milestones defined as a minimum.

1. Equipment installation schedule

2. Limited installation capability demonstration

3. Equipment installation completion

4. User acceptance testing

5. User training

The limited installation capability demonstration is defined to be a technical feasibility report in which the steps required for complete equipment installation is detailed for each task order. The Contractor shall provide multiple offerings (i.e., alternate designs) for the assessment to include a site assessment with CenTrak® representation and a site assessment with CenTrak® and Infor® representation.

RTLS Site Assessment Report.

5.1.5 RTLS TIME STAMP

The Contractor shall ensure all applications synchronize with internal VISN Facility time standard. The synchronization of time on this network is critical in every aspect of managing, securing, planning and debugging as it involves determining when an event occurred.

5.1.6 WIRELESS TECHNOLOGY

The Contractor shall utilize the existing Wi-Fi infrastructure at each facility as the core active tag ranging and distance measurement (communication between tag and reader). The Contractor shall notify the Government when known existing Wi-Fi infrastructure at each facility is not available or is insufficient and supplemental technologies will be required where Wi-Fi is not available or insufficient to achieve the resolution objectives of the applications. Alternate solutions shall be identified if cheaper or more efficient than the use of VA wireless technology or in areas where there is not enough Wi-Fi Coverage e.g., supplemental clinical grade location hardware.

5.2 HARDWARE DESIGN

The Contractor shall provide and install all RTLS supporting hardware and components to blend in (or not be visible at all), 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 Joint Commission and local Infection Control Risk Assessment (ICRA) findings and standards. This installation shall occur during normal business hours. This may include use of containment units for any above the ceiling work.

The Contractor shall ensure there is a Hardware Deployment Design Document (HDDD) for every site. The Contractor shall update the HDDD throughout the Task Order Period of Performance so that it remains current with the existing design. The Preliminary HDDD shall include:

1. Proposed quantity and location of supplemental Wi-Fi infrastructure to achieve the goals of the RTLS applications and room coverage requirements.

2. Proposed changes, corrections and/or updates to the VA-provided maps and Engineering Space Files as noted during the Contractor’s site validation.

3. Any other tools and templates that help to define the design (e.g., configuration, components, business rules, etc.) of the VISN RTLS to aid the VISN facility in making design decisions to achieve the goals of the proposed RTLS applications.

4. RTLS Database Infrastructure – As designated by VA, as part of the Preliminary HDDD, the Contractor shall provide draft documentation of the Server configuration and architecture that shall be configured and optimized to meet the needs of the facility. This draft documentation shall include a diagram that lays out the server requirements at each location along with expected bandwidth utilization for the WAN links, expected application latency requirements, server specification (including power, BTUs, and network connections), provide the specification for the number of tags that can be supported per server.

Hardware Deployment Design Document (HDDD).

5.3 HARDWARE

The Contractor shall provide all necessary RTLS hardware components to support CenTrak® AT, PEW, and HHC. Hardware shall be ordered at the Task Order level.

Hardware components shall include infrastructure components, tags and batteries. The Contractor shall coordinate with the COR and site POCs to schedule delivery and receive written, or e-mail COR concurrence as required to ship hardware. Anticipated required hardware is identified in Attachment A, however, if additional hardware within scope of this PWS is needed, additional products may be added to the contract via modification.

The Contractor shall provide a copy of the signed Facility Receiving Report to the COR once components are delivered. The Contractor shall submit a copy of the signed Facility Receiving Reports for each facility. The Facility Receiving Report shall contain:

1. Confirmation of the order and delivery of the components

2. Reconciliation (if any) of what was planned to be delivered versus what was delivered. Details of where items were delivered, what time they were delivered, and who from the Government received them.

Deliverable

Facility Receiving Report.

5.4 INSTALL AND TAGGING

5.4.1. Infrastructure Installation

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

The Contractor shall install RTLS supporting hardware and components to blend in (or not be visible at all) 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

Joint Commission and local Infection Control Risk Assessment (ICRA) findings and standards. This installation shall occur during normal business hours. This may include use of containment units for any above the ceiling work.

Installation of stars requires a data connection. The Contractor shall use available data connections whenever possible. If a new data connection and cabling is required, the Contractor will provide the cabling and the cabling services.

For sites with a status of ‘Implementation in Progress’, the Contractor shall evaluate if batteries need to be changed in existing infrastructure devices. If batteries need to be changed, the Contractor shall provide and replace batteries in infrastructure devices.

5.4.2 Asset Tagging

The Contractor shall create and provide a Facility Tagging and Commissioning Plan for sites with a status of ‘Implementation in progress’ and ‘No implementation’ prior to beginning the tagging process for review and approval by the COR. Once approved, this plan shall be integrated into the CPMP. This Plan shall include:

1. Identification of all Asset Groups and Assets to be tagged in accordance with the VA National Tagging Standard (see Attachment A - Minimum List of Hardware and Software).

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 to allow the Government to perform the tagging and commissioning process.

Upon COR approval of the Facility Tagging and Commissioning Plan, the Contractor shall execute and report on tagging and commissioning operations weekly with the COR either through email or status calls, and in the Monthly Progress Reports (Section 5.1.2).

Facility Tagging and Commissioning Plan.

5.4.3 Fingerprinting

The Contractor shall implement RTLS Fingerprinting Technology at the facility as designated by VA. The Contractor shall work with VA staff to gain access to all rooms and minimize disruption of patient care. Fingerprinting Technology is utilized to determine location in Wi-Fi covered areas. Fingerprinting technology captures signal strength from multiple RTLS Active tags received by the Access Points. Data is collected throughout the facility and utilized by CenTrak® to determine the location of an asset.

A. Software Installation Report

5.5 SOFTWARE CONFIGURATION & MAINTENANCE

5.5.1 Software

The Contractor shall provide and install all necessary software for the AT, HHC, and PEW application as designated by VA. The Contractor shall also provide and install the Infor® LBI and CenTrak user interfaces. VA will provide a virtual server platform on which software may reside. The Contractor shall provide a Software Installation Report.

This Report shall include a list of all software and licenses that are installed at the facility.

5.5.2 CenTrak® Software Configuration

Per hardware design changes and/or VA reconfiguration requirements, the Contractor shall update rendered maps in CenTrak® ConnectPulse and/or CenTrak Asset Viewer.

When applicable, naming shall conform to data standards as outlined in the RTLS Enterprise Data Architecture (EDA) Standards Workbook. Further, the Contractor shall provide configuration updates for existing hardware. Configuration changes shall be scoped during the site assessment at each facility.

5.5.3 Infor® Software Configuration

Per hardware design changes and/or VA reconfiguration requirements, the Contractor shall update rendered maps in Intelligent InSites application. Naming shall conform to data standards as outlined in the RTLS Enterprise Data Architecture (EDA) Standards Workbook. Configuration changes shall be scoped during the site assessment at each facility.

The Contractor shall provide service hours as requested by the VHA for all Infor Tasks associated with system and software configuration and administration, as well as workflow solutions.

5.6 FACILITY ACCEPTANCE TESTING

The Contractor shall create and provide an Acceptance Test Plan that includes two phases. A single Acceptance Test Plan is required to define testing methodology for all TOs. The Contractor shall not execute testing on any TO until the COR approves the

Acceptance Test Plan. The VA shall provide test scripts; the Contractor may redact test scripts to meet the scope of the requirement.

Phase 1: Performance Testing:

The Contractor shall perform testing on the system and/or system enhancements to certify Proof of Performance to include Clinical Grade Location Accuracy of 100%.

Active tags in non-clinical grade location areas shall accurately report the vertical (floor) location 97% of the time and horizontal location within 10 meters with an accuracy of 90%. The Contractor shall test and verify that all system functions and specification requirements are met and operational, and no unwanted effects, such as signal distortion or interference with other facility devices are present. The Contractor shall provide VA with a copy of the performance test plan methodology and test results.

If the system does not meet requirements and additional remediation hardware is required, the Contractor shall provide a list that outlines additional requirements per site to include hardware, software and service in the Facility Remediation Hardware Report.

Line items shall be listed in the format of the price cost schedule with the description of the item, quantity, cost per unit, and CLIN #.

Phase 2: User Acceptance Testing:

The Contractor shall schedule an acceptance test date and provide VA 30 days written notice prior to the date the acceptance test is…