36C10B22R0016.docx

36C10B22R0016

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

36C10B22R0016 8/22/2022 Laura Startek 848-377-5089 09-6-2022 3:00pm

EDT

36C10B Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

541614 $16.5 Million

N/A

36C10B Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

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

TITLE: Automated Inventory Management Using Passive Radiofrequency Identification

Type of Order: Firm-Fixed Price

Contracting Officer: Matthew J. Truex, Matthew.Truex1@va.gov

Contract Specialist: Laura Startek, Laura.Startek@va.gov

Matthew J. Truex Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: TBD

b. GOVERNMENT: Contracting Officer Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

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:

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.

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

B.2 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. 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. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ). 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 effected by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

1. Definitions.

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

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

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

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

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

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

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

1. Software License

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

1. The Government may use the software in a networked environment.

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

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

1. Software Maintenance and Technical Support

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

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.

B.4 PRICE SCHEDULE

All deliverables will be destination inspection and acceptance and due 30 days after award unless otherwise specified. Deliverables with due dates falling on a weekend or holiday shall be submitted the following Government workday after the weekend or holiday. All deliverables will be electronically submitted to the VA PM, COR, and CS. All deliverables will be destination inspection and acceptance.

NOTE: Vendors are instructed to complete Attachment A – Price Schedule.

Vendors are cautioned that alterations to the line items as specified below may render quotes unacceptable. All questions shall be directed to the Contract Specialist Laura.Startek@va.gov to the closing date and time specified in the Request for Quote (RFQ) on Page 1, Block 8.

Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination Ordering Period is 36 months.

In accordance with (IAW) PWS Section 5.1 through 5.1.2 Pricing shall include SLINS 1001AA-0001AB

Deliverable: Contractor Project Management Plan One Per Task Order, Updated Throughout Period of Performance Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.1.1

Deliverable: Monthly Progress Report Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.1.2

IAW PWS Section 5.2 through 5.2.1

Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.2.1

Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.2.1

IAW PWS Section 5.3

0003AA

Deliverable: Site Assessment Report One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.3

IAW PWS Section 5.4 through 5.4.3 Pricing shall include SLIN 1004A

IAW PWS Section 5.4.1

IAW PWS Section 5.4.2

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.4.3

IAW PWS Section 5.5

Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov Inspection: Destination Acceptance: Destination IAW PWS Section 5.5

IAW PWS Section 5.5.1

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.5.1

IAW PWS Section 5.6

IAW PWS Section 5.6.1

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.6.1

IAW PWS Section 5.6.2

IAW PWS Section 5.6.3

IAW PWS Section 5.7

IAW PWS Section 5.7.1

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS 5.7.1

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS 5.7.1

IAW PWS Section 5.7.2

IAW PWS Section 5.7.3

IAW PWS Section 5.8 through 5.8.2

Draft due 60 days after contract award, final due within 90 days, and updated as required thereafter.

Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.8

IAW PWS Section 5.8.1

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.8.1

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.8.1

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination IAW PWS Section 5.8.1

IAW PWS Section 5.8.2

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.8.2

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.8.2

IAW PWS Section 5.9

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.9

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.9

IAW PWS Section 5.10

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.10

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.10

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.10

Support for one (1) year following each site acceptance by VA.

IAW PWS Section 5.11

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 5.11

IAW PWS Section 6.1 through 6.7 and Addendums

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 6.2.2

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 6.7

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section 6.7

One Per Task Order Electronic Submission to: Phuc.Nguyen@va.gov

Inspection: Destination Acceptance: Destination

IAW PWS Section A3.4

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veteran Health Administration Veteran Integrated Service Network 21 (VISN 21)

Automated Inventory Management Using Passive Radiofrequency Identification

Date: 3/29/2022

TAC VA-22-00058687

PWS Version Number: 1.0

1.0 BACKGROUND

The mission of the Department of Veterans Affairs (VA), Veteran Integrated Service Network 21 (VISN 21) is to provide benefits and services to Veterans of the United States. In meeting these goals, VISN 21 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.

VISN 21 currently uses CenTrak® proprietary active radiofrequency identification (active RFID) real time locating systems (RTLS) to track asset, staff, and patient locations. CenTrak® Active Asset Tracking (AT) deployed at VISN 21 Health Care Systems (HCS) is supplemented with the Infor® Location Based Intelligence (LBI) user interface (UI). The hardware and software are designed for locating assets in real time at a zonal, room-level, and within-room level accuracy.

Currently, however, active (i.e., battery powered) CenTrak® asset tracking (AT) only provides coverage for a portion of VISN 21’s assets due to the trade-off between tag size, maintenance cost (e.g., battery management), and the ability to locate assets in real time. However, it is not necessary to locate in real time the majority of non-expendable (NX) equipment at medical centers. Therefore, VISN 21 is seeking a passive (i.e., non-powered) RFID solution to complement CenTrak® active AT in locating non-expendable equipment not suitable for use with active RFID tags.

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

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

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

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

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

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

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

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 professional services, hardware, and software required by individual Task Orders (TOs) for the implementation of a radiofrequency-based asset tagging system at VISN 21 Health Care Systems.

3.1 ISSUANCE OF TOS

The CO shall issue a TO to the Contractor. Contractor work shall commence only after issuance of the TO by the CO.

3.1.1 Request for Post Award Action

Upon identification of the need for a modification to a TO, the Government shall issue a Request for Post Award Action, designated by an action number, to the Contractor. The CO shall designate individuals authorized to issue such requests upon TO award, in writing. The Contractor shall respond to requests from these authorized individuals only. All Contractor correspondence shall reference the Government designated action number. The Government’s Request for Post Award Action does NOT constitute an authorization to start work. A Request for Post Award action may include, but not limited to cost and no cost changes, period of performance extensions, within scope changes, shipping or inspections changes.

4.0 PERFORMANCE DETAILS

This is an Indefinite Delivery/Indefinite Quantity (IDIQ) contract. Individual TOs shall be issued on a Firm Fixed Price (FFP) basis.

The Contractor shall provide and/or acquire the services, hardware, and software required by individual TOs pursuant to the general requirements specified below.

4.1 PERFORMANCE PERIOD

The ordering period shall be three (3) years from the date of award. The period of performance (PoP) for any task order may go up to 16 months beyond the last day of the ordering period. Each TO will have its own PoP.

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

The place of performance shall be identified in individual Task Orders within VISN 21. The list of current VISN 21 Health Care Systems and their addresses are given in Table 1.

Table 1: VISN 21 Health Care Systems

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort. 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 will be dependent on each Task Order.

5.0 SPECIFIC TASKS AND DELIVERABLES

Individual TO(s) may encompass more than one functional area listed below. Functional area details are described to provide greater insight into the complexity and uniqueness of some potential TO requirements covered by this Performance Work Statement (PWS). Functional area requirements are not mutually exclusive, and an individual TO requirements may fall within multiple functional areas.

5.1 PROJECT MANAGEMENT

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 the contract. 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 requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated with approval from the Government. The Contractor shall update and maintain the CPMP throughout the period of performance.

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR with Monthly Progress Reports (MPR) in electronic format. The MPR 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 monitor performance against the CPMP and report all deviations. The Contractor shall communicate with the Government any potential issues that may arise. The MPR reports shall reflect progress as of the last day of the preceding month.

The deliverables defined below are required for the basic contract and each resulting TO, unless otherwise specified, and shall be forwarded electronically to the Government. The basic contract report shall be a rollup of each TO. Each individual TO report shall be delivered to the COR for that TO. Any differences between the requirements for the overall basic contract report versus the TO report are noted below. For monthly reports, the reporting period shall be from the first day of each month (or the date of TO award) through the last day of that month; each deliverable for that period shall then be submitted by the 15th day of each the following months. Deliverables with due dates falling on a weekend or holiday shall be submitted the following Government work day after the weekend or holiday.

The Contractor shall provide a Monthly Progress Report at the basic contract level that provides a roll up of each TO.

Deliverable:

A. Monthly Progress Report

5.2 IMPLEMENTATION AND EXPANSION

5.2.1 COMPATIBILITY REQUIREMENTS

Due to the existing implementation of CenTrak® active RTLS and Infor® LBI at VISN 21 Medical Centers and CBOCs, the following requirements apply to all specific tasks and deliverables in this PWS:

· The Contractor shall propose a hardware solution that is compatible with Infor® LBI. Location and asset data from the proposed passive RFID system must be transmissible to Infor LBI® and conform to the CenTrak® and Infor® Data Standards.

· The Contractor shall propose a software interface that is compatible with CenTrak® hardware and software for asset tracking. The proposed software and user interfaces must be able to accept CenTrak® location data.

· The Contractor shall propose a solution that is compatible with CenTrak® and Infor® data architecture.

The requirements above ensure that there is possible cross-talks between the passive and active asset management systems at VISN 21. In addition, VA VISN 21 requires that:

· The Contractor shall provide proof as an authorized reseller or distributor for the original equipment manufacturer (OEM) and remain an authorized reseller or distributor for the duration of the POP.

· The Contractor shall provide proof as an authorized reseller or distributor for the original software manufacturer of the user interfaces.

Deliverables:

A. Authorized Reseller or Distributor for the (OEM) Documentation B. Authorized Reseller or Distributor for the Original Software Manufacturer of the User Interfaces Documentation

5.3 SITE ASSESSMENT

The Contractor shall perform a detailed site assessment at the site(s) identified in individual TOs to provide a full scope of requirements for site needs. A VAMC or CBOC in a different city shall be considered a different site for site assessment purposes. The Contractor shall coordinate with the COR and site POCs to schedule site assessments. The Contractor shall conduct a pre-assessment conference call at least two (2) 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).

The Contractor shall provide a Site Assessment Report that outlines all requirements and line items per site to include hardware, software and services. 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

Milestones may be based on TO award date. 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.

Deliverables A. Site Assessment Report

5.4 DESIGN

5.4.1 Time Stamp

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

The Contractor shall utilize the existing Wi-Fi infrastructure at each facility for the implementation of the technology. 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.

5.4.3 Hardware and Server Design Document

The Contractor shall ensure there is a Hardware and Server Design Document (HSDD) for every site. The Contractor shall update the HSDD throughout the remaining implementation so that it remains current with the existing design. The HSDD shall include:

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

2. Proposed location for installation of hardware.

3. The Contractor shall provide a draft 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).

4. The Contractor shall provide the specification for the number of tags that can be supported per server.

Deliverables

A. Hardware and Server Design Document (HSDD)

5.5 HARDWARE PROVISIONING AND CONFIGURATION

The Contractor shall provide all necessary hardware components delivered to sites as specified in the Hardware and Server Design Document (HSDD) and ordered at the task order level. The hardware provided shall be compatible with VISN 21’s existing interface software and additional proposed interface software. Hardware components shall include, but not limited to, handheld RFID scanners, passive RFID tags, infrastructure components. Wireless hardware proposed shall be FIPS-compliant.

The Contractor shall coordinate with the COR and site POCs to schedule delivery and receive written or e-mail COR concurrence is required to ship hardware. 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 site. 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 A. Facility Receiving Report

5.5.1 Installation and Configuration

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

The Contractor shall ensure that hardware installed and configured do not interfere with other wireless technologies in the same environment. In the event of interference, the Contractor shall propose a plan for resolution of interference to the Government.

The Contractor shall install 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 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. Hardware installation shall occur during normal business hours. This may include use of containment units for any above the ceiling work.

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 shall provide rendered maps of installed infrastructure device locations (i.e., “as-built drawings”).

Deliverable A. Infrastructure Device Maps

5.6 SOFTWARE PROVISIONING AND CONFIGURATION

5.6.1 Hardware-Specific Software

The Contractor shall provide and install all necessary software compatible with the proposed hardware (i.e., middleware). The Government will provide virtual servers. If a virtual server platform is not feasible, the Contractor shall provision compatible physical servers for software installation. The Contractor shall provide a Software Installation Report. This Report shall include:

1) A list of all servers configured

2) Software and licenses that are installed on each server

3) Software validations

4) Server data architecture diagram

Deliverable A. Software Installation Report

5.6.2 User Interface Provisioning and Configuration

The User Interface (UI) shall be a web-based UI and include at minimum the following capabilities:

1. Web-based UI

2. Display individual item information to allow users to uniquely identify individual assets

3. Displays facility assets in a list view; assets may be searched by asset number (identifier), asset type, asset model, asset manufacturer, or tag ID

4. Display facility assets in a map view; asset location shall be displayed on a facility floorplan in a pictographic method

5. Asset information may be exported from the system in an excel format

6. Access past year of asset location history (capability may be developed)

7. Fully customizable business rules

8. Asset egress alerts (capability may be developed as designated by VA)

9. Report generation and integration with Microsoft® Power BI

The UI shall be capable of interfacing with the following automated inventory management system / computerized inventory and maintenance management systems (CMMS):

1. VA Automated Engineering Management System/Medical Equipment Reporting System (AEMS-MERS)

2. IBM Maximo® Enterprise Asset Management System (Maximo EAM)

3. Nuvolo©

The interface for data exchange between the UI and VA AEMS-MERS/Maximo®/Nuvolo© shall at least be bidirectional and have at least the following capabilities:

1. Provide the UI and VA-AEMS/MERS and Maximo AEM the ability to identify a unique asset using a combination of unique asset ID and facility number.

2. Update the UI at least once every 24 hours.

3. Allow the UI shall display individual asset information from VA-AEMS/MERS and Maximo AEM to allow user to unique identify individual assets.

4. Provide designated users the capability to adjust the periodicity of bidirectional updates.

5. Post inventory date and time to VA-AEMS/MERS and Maximo AEM

6. Have the option to be run on demand

7. Update the UI with space creation from VA-AEMS/MERS and Maximo AEM

8. Update the UI when an asset has been decommissioned in VA-AEMS/MERS and Maximo AEM

9. Stop sending location/inventory date updates to VA-AEMS/MERS and Maximo AEM when assets are marked as decommissioned in the UI.

5.6.3 Infor® LBI Software Configuration

VISN 21 currently uses Infor® LBI as a UI for active RFID-based asset tracking. To streamline clinical and operational workflow, compatibility with Infor® LBI is required for all proposed hardware, software, and user interfaces. Therefore, if the proposed UI is not Infor® LBI, the Contractor shall provide configuration services for integrating the proposed passive RFDI system interfaces with Infor LBI®. The Contractor must maintain a current Reseller Agreement with Infor® for all tasks requiring Infor® LBI software installation, configuration, and maintenance.

Per hardware design changes and/or VA reconfiguration requirements, the Contractor shall update rendered maps in Infor® LBI 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.

5.7 PROFESSIONAL SERVICES

5.7.1 Asset Tagging

The…