36C10B23R0031.docx

36C10B23R0031

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

09-14-2023 Brandon Caltabilota 848-377-5177 09-20-2023

3:00PM

EDT

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

541519 $34 Million

N/A

See Delivery Schedule

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

Department of Veterans Affairs Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971

See CONTINUATION Page Real Time Location Systems (RTLS) Asset Tracking (VA Long Beach)

See Section B.4 Price Schedule and Section B.5 Performance Work Statement

This procurement is set aside to Service-Disabled Veteran- Owned Small Businesses (SDVOSB).

This RFP will result in a Firm-Fixed-Price Contract.

The period of performance shall be 12 months from date of award, with one 12-mo Option Period, and one Optional Task.

Xx

Jessica Bieberbach Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

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

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

(1). Definitions.

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

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

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

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

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

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

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

(2). Software License.

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

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

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

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

(3). Software Maintenance and Technical Support.

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

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

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

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

B.3 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: TBD

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

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly [ ]

b. Semi-Annually [ ]

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

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

B.4 PRICE SCHEDULE

Offerors are instructed to complete Section B.4 Price Schedule and submit with their proposal. Offerors are cautioned that alterations to the line items as specified below may render proposals unacceptable. All questions shall be directed to the Contract Specialist, Brandon Caltabilota, Brandon.Caltabilota@va.gov, and Contracting Officer, Jessica Bieberbach, Jessica.Bieberbach@va.gov prior to the closing date and time specified in the Request for Proposal (RFP).

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.

All deliverables shall be destination inspection and acceptance. Days used below refer to calendar days unless otherwise stated. Deliverables with due dates falling on a weekend or holiday shall be submitted the following Government workday after the weekend or holiday.

All deliverables shall be electronically submitted to: VA Program Manager (PM), Contracting Officer’s Representative (COR), Contracting Officer (CO), and Contract Specialist (CS).

Base Period

The Base Period of Performance (PoP) shall be 12 months from date of award.

This Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, project management, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.1, inclusive of all subparagraphs.

The PoP shall be 12 months from date of award.

The cost of this CLIN shall be included in and allocated to CLINs 0002 through 0009, and 2001, if exercised.

(NSP)

NSP

Due 30 days after receipt of contract and updated monthly thereafter.

Due five (5) days prior to the kickoff meeting.

Due three (3) business days after technical kickoff meeting.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.2, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

PoP shall be 12 months from date of award.

Due 20 business days after completion of site assessment for VA Long Beach Healthcare System.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.3, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months from date of award.

Due 5 business days after delivery of hardware component(s).

Due 20 business days after completion of site assessment for VA Long Beach Healthcare System.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.4, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months from date of award.

Due 20 business days after completion of site assessment for VA Long Beach Healthcare System.

Due 20 business days after completion of site assessment for VA Long Beach Healthcare System.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.5, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months from date of award.

Due 15 business days prior to start of tagging operations

Due five (5) business days after start of tagging operations and every Friday thereafter.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.6, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months from date of award.

Due five (5) business days after completion of installation and updated every Monday thereafter.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.7, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months from date of award.

Due 90 business days after completion of site assessment for VA Long Beach Healthcare System.

Due 90 business days after completion of site assessment for VA Long Beach Healthcare System.

Due five (5) business days after completion of testing.

Due five (5) business days after completion of testing.

Due 10 days after approval of all VA Long Beach Healthcare System test reports.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.8, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months from date of award.

Due 60 days prior to training events.

Due 10 days prior to training events.

This FFP CLIN includes all labor, materials, project management, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.9, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months from date of award.

Due five (5) business days prior to start of each warranty period.

Option Period One

This 12-month Option Period may be exercised IAW FAR 52.217-9, Option to Extend the Term of the Contract. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, this option shall commence immediately after expiration of the Base Period.

This Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, project management, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.1, inclusive of all subparagraphs.

The PoP shall be 12 months commencing immediately upon expiration of the Base Period.

The Deliverable(s) identified under Base Period SLIN(s) 0001AA shall be required.

The cost of CLIN 1001 shall be included in and allocated to CLINs 1002, 1003, and 2001, if exercised.

This FFP CLIN includes all labor, materials, project management, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.6, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

PoP shall be 12 months commencing immediately upon expiration of the Base Period.

The Deliverable(s) identified under Base Period SLIN(s) 0006AA shall be required.

This FFP CLIN includes all labor, materials, project management, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.9, inclusive of all subparagraphs.

Government approval of invoices for payment shall be subject to Contractor’s successful completion of task requirements and associated deliverables required by the PWS.

The PoP shall be 12 months commencing immediately upon expiration of the Base Period.

The Deliverable(s) identified under Base Period SLIN(s) 0009AA shall be required.

Optional Task – Transition Out

IAW FAR 52.217-7, Option for Increased Quantity-Separately Priced Line Item (MAR 1989), this Optional Task may be exercised one time, at any time, at the Government’s discretion during the base or option period. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

This FFP CLIN includes all labor, material, project management, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.12.

Government approval of invoices for payment shall be subject to contractor’s successful completion of task requirements and associated deliverables required by the PWS.

If exercised, the PoP shall be 60 days and may not exceed beyond the period in which it is exercised.

Due 60 days after commencement of optional task.

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration (VHA) VA Long Beach Healthcare System

Real Time Location Systems (RTLS) Asset Tracking (VA Long Beach)

Date: August 21, 2023

VA-23-00092110

PWS Version Number: 1.5

BACKGROUND

The Department of Veterans Affairs (VA)’s Real Time Location System (RTLS) Program affects areas of clinical and administrative workflows by providing process improvement and automation efficiency. Significant potential uses and benefits of this technology throughout VA are numerous and include improved quality of patient care and satisfaction, reduced health care asset management costs, improved capacity/resource planning, improved employee, and patient safety, and improved general asset management and inventory. The RTLS solution is comprised of multiple applications impacting the logistics supply chain, inventory accountability, Biomedical Engineering, Office of Information and Technology (OIT), Sterile Processing, Dental and Surgical Services, Cardiac Catheterization Labs, and a host of other clinical departments.

RTLS is a System of Systems that integrates location data from multiple applications. The RTLS applications are deployed to more than 225 VA medical centers and Community-Based Outpatient Clinics. Current installations use proprietary CenTrak and Infor Location-Based Intelligence (LBI) software for tagging, tracking, and integration into a single database. CenTrak® proprietary active Radio Frequency Identification (RFID) hardware and software provide zonal, room-level, and within-room level accuracy regarding asset location, staff location, patient location, as well as environmental variables.

VHA now seeks to implement the following RTLS application based on the same platforms at VA Long Beach Healthcare System:

1. Asset Tracking (AT) to monitor the location of assets within a facility.

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

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, 2017

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

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)

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, 2005

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

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

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

SCOPE OF WORK

This PWS establishes the requirements for Information Technology (IT) services, hardware, and software to implement CenTrak and Infor LBI-based Asset Tracking (AT) at the VA Long Beach Healthcare System. The Contractor shall provide RTLS hardware, software, documentation, and services to authorized users in VHA. Services include installation, end user acceptance testing, training, warranty services, engineering, and professional services. The scope of this order shall include completion of implementation already started and expansion of current inactive system at VA Long Beach Healthcare System. Facility specifications for the areas in scope are included in Attachment 1 (RTLS In Scope Buildings) and Attachment 2 (Floor Plans) for RTLS.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 12 months from date of award, with one 12-month option period, and one optional task. The overall PoP shall not exceed 26 months including the award, all option years, and optional task.

Any work at a 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, four are set by date:

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:

PLACE OF PERFORMANCE

Tasks under this PWS shall be performed in the VA facilities located in Table 1 below (primarily for hardware installation and tagging). Project management tasks shall be performed remotely.

Table 1: Task Order Place of Performance

Long Beach, CA 90822-5201

Villages at Cabrillo, Bldg. 28 Long Beach, CA 90806-3622

Suite 100 Gardena, CA 90248-4321

Laguna Hills, CA 92653-5422

Placentia, CA 92870-6832

Suite 100 Santa Ana, CA 92705-5405

Suite 180 Santa Fe Springs, CA 90670-6012

TRAVEL

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 PoP. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of the program related meetings for this effort is three (3). Anticipated locations include the following, estimated at two (2) to three (3) weeks in duration:

1. Two (2) trips, each one for two (2) to three (3) weeks in duration to the Tibor Rubin VA Medical Center, 5901 E 7th Street, Long Beach, CA 90822-5201.

2. One (1) trip, for two (2) to three (3) weeks in duration to include each of the six (6) clinics listed above. (Cabrillo VA Clinic; Gardena VA Clinic; Laguna Hills VA Clinic, Placentia VA Clinic; Santa Ana VA Clinic; and the Santa Fe Springs VA Clinics).

SPECIFIC TASKS AND DELIVERABLES

PROJECT MANAGEMENT

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.

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 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 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 Contractor shall hold a monthly 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 Report

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 the Contracting Officer (CO), as the Post-Award Conference Chairperson, the VA lead(s), as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA lead(s) 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 Microsoft 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 Real Time Location Systems (RTLS) Asset Tracking (VA Long Beach) contract.”

The Contractor shall submit the final updated Final Technical Kickoff Meeting Presentation to the CO for review and signature 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

RTLS DESIGN

RTLS TIME STAMP

The Contractor shall ensure all applications synchronize with internal VA site time standard. 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.

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.

HARDWARE DESIGN DOCUMENT

The Contractor shall ensure there is a valid Hardware Deployment Design Document (HDDD) for the facility. The Contractor shall review the existing HDDD (Attachment 3) and provide a Preliminary HDDD. The preliminary HDDD shall indicate the planned design for asset tracking at VA Long Beach Healthcare System.

The Contractor shall update the HDDD throughout the implementation period so that it remains current with the existing design. The final HDDD shall include:

1. The preliminary design that included proposed quantity and location of supplemental Wi-Fi infrastructure to include hardware locations and type, as well as a survey of network closets, the availability/need of closets, Power Over Ethernet (POE) switches for providing power to hardware, hardware, and wiring plan for hardware to achieve the goals of the RTLS applications and room coverage requirements.

2. Changes, corrections and/or updates to Attachments 1 and 2.

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

4. RTLS Database Infrastructure: as part of the HDDD, the Contractor shall provide documentation of the server configuration and architecture configured and optimized to meet the needs of the facility. The HDDD shall include a diagram that lays out the server requirements at each location along with expected bandwidth utilization for the Wide Area Network (WAN) links, expected application latency, server specification (including power, Basic Transmission Units (BTU), and network connections). In addition, the Contractor shall specify the number of tags each server will support.

Deliverable:

A. Preliminary HDDD

RTLS HARDWARE

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 submit to the COR a copy of the Signed Facility Receiving Report confirming delivery of components at each site. The 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.

Deliverable:

A. Signed Facility Receiving Report

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.

Where CenTrak hardware is already installed, the Contractor shall be responsible for identifying and installing any “added” devices, whether they come from VA stocks or are purchased. The Contractor shall evaluate batteries in existing infrastructure devices.