S02 - 36C10B26R0017 - Automated Asset Management.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

36C10B26R0017 07-16-2026

Juan C Perez 512-981-4467 08-17-2026

14:00 EDT

Department of Veterans Affairs Technology Acquisition Center Procurement Services G 23 Christopher Way Eatontown NJ 07724

X

541519

150 Employee

N/A

X

See Delivery Schedule

Procurement Services G

Financial Services Center PO Box 149971 Austin TX 78714-8971

Automated Asset Management Using Passive Radiofrequency Identification and Bluetooth Low Energy

See Continuation Page

X X

Edgar Alonso-Bernal

Contract Number: TBD

Request for Proposal: 36C10B26R0017

B.1 Schedule of Supplies/Services

Item # Description/Part Number Unit Quantity Price Total

1. Specific requirements are detailed in Section B.4, Performance Work Statement (PWS) titled “Automated Asset Management Using Passive Radiofrequency Identification and Bluetooth Low Energy”, dated February 9, 2026.

2. ARM Number: 201323

3. Inspection/Acceptance/FOB: Destination.

4. Address/Point of Contact: See B.4 Product Description.

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

6. Pricing shall be placed in accordance with Attachment A.

CLIN Description Qty Unit Unit Price Total Price

Automated Asset Management Using Passive Radiofrequency Identification and Bluetooth Low Energy

Total Contract Ceiling $TBD

Governing Law Clause

Federal law and regulations, including the Revolutionary Federal Acquisition Regulation (FAR) Overhaul (RFO), 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 RFO 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), Source Code Harmonization and Reuse in Information Technology Act “SHARE IT Act” (P.L. 118-187), and RFO clauses 52.212-4, 52.227- 14 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 RFO 52.227-14, this includes any custom code developed for the purpose of performing under this contract. 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.

SOFTWARE LICENSE, SOFTWARE MAINTENANCE AND SOFTWARE 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) All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

d) The commercial computer software delivered under this contract may not be used, reproduced, or disclosed by the Government except as provided below or as expressly stated otherwise in this contract. The commercial computer software may be-

i. Used or copied for use with the computer(s) for which it was acquired, including use at any Government installation or agency to which the computer(s) may be transferred;

ii. Used or copied for use with a backup computer if any computer for which it was acquired is inoperative;

iii. Reproduced for safekeeping (archives) or backup purposes;

iv. Modified, adapted, or combined with other computer software;

v. Disclosed to and reproduced for use by support service Contractors or their subcontractors, subject to the same restrictions set forth in this contract; and

vi. Used or copied for use with a replacement computer.

e) Unauthorized Obligations.

i. Except as stated in paragraph (ii), when any supply or service acquired under this contract is subject to any commercial supplier agreement (as defined in 502.101) that includes any language, provision, or clause requiring the Government to pay any future fees, penalties, interest, legal costs or to indemnify the Contractor or any person or entity for damages, costs, fees, or any other loss or liability that would create an Anti-Deficiency Act violation ( 31 U.S.C.

1341), the following shall govern:

1) Any such language, provision, or clause is unenforceable against the Government.

2) Neither the Government nor any Government authorized end user shall be deemed to have agreed to such clause by virtue of it appearing in the commercial supplier agreement. If the commercial supplier agreement is invoked through an “I agree” click box or other comparable mechanism (e.g., “click-wrap” or “browse-wrap” agreements), execution does not bind the Government or any Government authorized end user to such clause.

3) Any such language, provision, or clause is deemed to be stricken from the commercial supplier agreement.

ii. Paragraph (u)(1) of this clause does not apply to indemnification or any other payment by the Government that is expressly authorized by statute and specifically authorized under applicable agency regulations and procedures.

f) Commercial supplier agreements unenforceable clauses.

i. This agreement is a part of a contract between the commercial supplier and the U.S. Government for the acquisition of the supply or service that necessitates a license or other similar legal instrument (including all contracts, task orders, and delivery orders under RFO 12).

ii. End user. This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.

iii. Law and disputes. This agreement is governed by Federal law. Any language purporting to subject the U.S.

Government to the laws of a U.S. state, U.S. territory, district, or municipality, or a foreign nation, except where Federal law expressly provides for the application of such laws, is hereby deleted.

1) Any language requiring dispute resolution in a specific forum or venue that is different from that prescribed by applicable Federal law is hereby deleted. Any dispute https://www.acquisition.gov/gsam/part-502#GSAM_502_101 http://uscode.house.gov/browse.xhtml;jsessionid=114A3287C7B3359E597506A31FC855B3 regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in RFO 52.212-4(e).

2) Any language prescribing a different time period for bringing an action than that prescribed by applicable Federal law in relation to a dispute is hereby deleted.

3) Continued performance. The supplier or licensor shall not unilaterally revoke, terminate or suspend any rights granted to the Government except as allowed by this contract. If the supplier or licensor believes the ordering activity to be in breach of the agreement, it shall pursue its rights under the Contract Disputes Act or other applicable Federal statute while continuing.

4) Arbitration; equitable or injunctive relief. In the event of a claim or dispute arising under or relating to this agreement, a binding arbitration shall not be used unless specifically authorized by agency guidance, and equitable or injunctive relief, including the award of attorney fees, costs or interest, may be awarded against the U.S. Government only when explicitly provided by statute (e.g., Prompt Payment Act or Equal Access to Justice Act).

iv. Updating terms. After award, the contractor may unilaterally revise commercial supplier agreement terms if they are not material. A material change is defined as:

1) Terms that change Government rights or obligations;

2) Terms that increase Government prices;

3) Terms that decrease overall level of service; or

4) Terms that limit any other Government right addressed elsewhere in this contract.

5) For revisions that will materially change the terms of the contract, the revised commercial supplier agreement must be incorporated into the contract using a bilateral modification.

6) Any agreement license terms or conditions unilaterally revised subsequent to award that are inconsistent with any material term or provision of this contract shall not be enforceable against the Government, and the Government shall not be deemed to have consented to them.

v. No automatic renewals. If any license or service tied to periodic payment is provided under this agreement (e.g., annual software maintenance or annual lease term), such license or service shall not renew automatically upon expiration of its current term without prior express consent by an authorized Government representative.

vi. Indemnification. Any clause of this agreement requiring the commercial supplier or licensor to defend or indemnify the end user is hereby amended to provide that the U.S.

Department of Justice has the sole right to represent the United States in any such action, in accordance with 28 U.S.C. 516.

vii. Audits. Any clause of this agreement permitting the commercial supplier or licensor to audit the end user's compliance with this agreement is hereby amended as follows:

1) Discrepancies found in an audit may result in a charge by the commercial supplier or licensor to the ordering activity. Any resulting invoice must comply with the proper invoicing requirements specified in the underlying Government contract or order.

2) This charge, if disputed by the ordering activity, will be resolved in accordance with RFO 52.212-4(e); no payment obligation shall arise on the part of the ordering activity until the conclusion of the dispute process.

3) Any audit requested by the contractor will be performed at the contractor's expense, without reimbursement by the Government.

(3). Software Maintenance and/or 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 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 two business days) in resolving software problems will be noted in the Government’s various past performance records on the

Contractor (e.g., www.cpars.gov).

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

(4). Disabling Software Code.

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

(5). Manuals and Publications.

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

http://www.cpars.gov/

B.2 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: See Block 17a

b. GOVERNMENT: Contracting Officer - See Block 31b

Department of Veterans Affairs Technology Acquisition Center-Austin

Eatontown, NJ 07724

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

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

Management, or [] 52.232-36, Payment by Third Party

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X – Upon acceptance]

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

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

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

B.4 PRODUCT DESCRIPTION

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veteran Health Administration

Automated Asset Management Using Passive Radiofrequency Identification and Bluetooth Low Energy

Date: 02/09/2026

TAC- VA-26-00044895

PWS Version Number: 1.0

Purchaser Order Number: TBD

1.0 BACKGROUND

The mission of the Department of Veterans Affairs (VA) is to deliver benefits and services to United States Veterans. In fulfilling this mission, the VA is committed to providing high-quality, effective, and efficient operational support to those responsible for caring for Veterans—both at the point of care and across every stage of their healthcare journey—in a timely, compassionate, and impactful manner. To support this mission, the VA Health Care Systems (HCS) currently utilize the following combination of proprietary technologies:

1. CenTrak® Real Time Locating Systems (RTLS) – Provides real-time location information for medical equipment.

2. Zebra® Passive Radio Frequency Identification (RFID) – Supports Non- Expendable (NX) asset management.

3. Infor Location Based Intelligence (LBI®) – Aggregates location data from both CenTrak® RTLS and Zebra® passive RFID, enabling integration with Computerized Maintenance Management Systems (CMMS) and Enterprise Asset Management (EAM) platforms.

4. AgileRank aRTLS mobile application – Supports asset tag management

These solutions work together as an integrated operational system designed to provide goal-based intelligence on assets, patients, and staff in real time with a zonal, room-level, and within-room-level accuracy.

The purpose of this requirement is to maintain, expand, and enhance existing automated asset management platform (AAMP), extend its capabilities, and integrate Bluetooth® Low Energy (BLE) technologies to bridge the gap between active RTLS and passive RFID solutions.

2.0 APPLICABLE DOCUMENTS

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

1. “Federal Information Security Modernization Act of 2014”

2. Federal Information Processing Standards (FIPS) Publication 140-3, “Security

Requirements for Cryptographic Modules”, March 22, 2019

3. FIPS Pub 199. “Standards for Security Categorization of Federal Information and

Information Systems,” February 2004

4. FIPS Pub 200, “Minimum Security Requirements for Federal Information and

Information Systems,” March 2006

5. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and

Contractors,” January 2022

6. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended

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

8. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and

Information Technology Act of 2006, as amended, Title IX, Information Security Matters

9. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended

10. VA Directive 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm

11. VA Handbook 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm

12. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019

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

Guidelines,” as amended

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

Information as a Strategic Resource,” July 28, 2016

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

Services (CHAMPUS)”, as amended

16. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and

Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024

17. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended

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

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

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

NOTICE 24-18, dated September 27, 2024, “Update to VA Directive 6500 Cybersecurity Program”, and VA Notice 25-07, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, and VA Notice 25- 06, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”, VA Notice 25-16, dated September 15, 2025, “Amending VA Handbook 6500 to Replace Enterprise Mission Assurance Support Services Tool With Office of Information Technology Governance Risk Compliance Tool, and VA Notice 25-17, dated September 22, 2025, “Rescission Of Office Of Information Security (OIS) Deputy Assistant Secretary (DAS) Memorandum – Requirements of Proper Plan of Action and Milestones (POA&M) Completion)

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023

23. VA Handbook 6500.6, “Contract Security,” March 12, 2010 (see VA Notice 24-12, dated April 22, 2024, “Update to VA Handbook 6500.6, Contract Security, Appendix C VA Information and Information System Security/Privacy Language For Inclusion Into Contracts, As Appropriate”)

24. VA Handbook 6500.8, “Information System Contingency Planning,” March 25,

25. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018 (see VA NOTICE 25-10, dated June 9, 2025, “Use of Personally Owned Mobile Devices Policy Amendment of Department of Veterans Affairs Handbook 6500.10”, and VA Notice 25-15, dated August 22, 2025, “Update to VA Handbook 6500.10 Mobile Device Security Policy”)

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

27. OIT Process Asset Library (PAL), OIT Process Asset Library.

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

29. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy

Impact Assessment,” October 15, 2014

30. VA Directive 6510, “VA Identity, Credential and Access Management,” September

3, 2024

31. VA Handbook 6510, “VA Identity, Credential and Access Management,”

September 27, 2024

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

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

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

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

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

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

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

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

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

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

42. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))

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

44. NIST SP 800-63 Rev 4, 800-63A-4, 800-63B-4, 800-63C-4, “Digital Identity Guidelines,” August 1, 2025

45. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 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. 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)

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

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

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

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

52. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L.

110–140), December 19, 2007

53. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005

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

55. Executive Order 14148, “Initial Rescissions of Harmful Executive Orders and

Actions,” dated January 20, 2025

56. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022

57. OIS VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

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

60. VA Memorandum “Proper Use of Email and Other Messaging Services,” January

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

61. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

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

63. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol

Version 6 (IPv6),” November 19, 2020

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

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

66. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended

67. Executive Order 14028, “Executive Order on Improving the Nation's

Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/

68. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

69. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

70. OMB M-26-05, “Adopting a Risk-based Approach to Software and Hardware Security,” January 23, 2026

71. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021

72. NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization,” December 2014

73. CISA Binding Operational Directive (BOD) 19-02: “Vulnerability Remediation

Requirements of Internet-Accessible Systems,” April 29, 2019, BOD 19-02:

Vulnerability Remediation Requirements for Internet-Accessible Systems | CISA

74. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA

75. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks.” Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01:

Improving Asset Visibility and Vulnerability Detection on Federal Networks | CISA

76. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019

77. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

78. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the Federal Government,” December 3, 2020

79. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025

80. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 3, 2025

81. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025

82. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI)

Through Unbiased AI Principles,” December 11, 2025

3.0 SCOPE OF WORK

The Contractor shall provide all professional services, hardware, and software required by individual Task Orders (TOs) to maintain and expand the AAMP across participating HCS. The scope includes the following:

• Technology and Project Management: Master project planning, stakeholder engagement, reporting, and key performance indicators (KPIs).

• Requirements and System Design: Workflow discovery, solution architecture for CenTrak RTLS/RFID/BLE integration, coverage maps, and unified asset data model.

• Delivering and Staging: Hardware/software staging, pre-configuration, and interoperability validation.

• Installation and Deployment: Site readiness activities, hardware installation of hardware such as readers, gateways, BLE beacons; asset tagging, and zone configuration.

• Integration with Enterprise Systems: Configuration of Infor LBI®/CenTrak ConnectCore®/Zebra MotionWorks® integration with CMMS/EAM, event-driven alerts, and secure access controls.

• BLE Enablement: beacon placement strategy, calibration to ensure accuracy, gateway integration, and mobile app enablement.

• Data Governance and Cybersecurity: Compliance with HIPAA, data encryption, adherence to VA security standards, and support for VA Authority to Operate (ATO) and Enterprise Risk Analysis (ERA).

• Testing and Validation: Conduct factory/site acceptance tests, verify accuracy and performance; perform failover testing and data quality checks.

• Training and Change Management: Provide role-based training, standard operating procedures (SOPs), job aids, adoption strategies, and Section 508-compliant materials.

• Operations and Sustainment: Deliver a tiered support model with service level agreement (SLAs), perform preventive/corrective maintenance, monitor system health, and conduct optimization reviews.

• Documentation and Deliverables: Produce design diagrams, configuration baselines, test reports, operational manuals, and disaster recovery plans.

• System Health and Analytics: Develop real-time dashboards for device uptime, tag battery status, location accuracy, utilization metrics, and predictive analytics for asset demand and workflow optimization.

3.1 TECHNOLOGY COMPATIBILITY REQUIREMENTS

Due to the existing implementation of CenTrak® Active RTLS, Zebra® RFID, Infor® LBI, and AgileRank aRTLS® at VA HCSs, the following requirements apply to all tasks and deliverables under this Performance Work Statement (PWS):

• Hardware Compatibility: The Contractor shall ensure delivery of a combination of passive RFID and BLE hardware that is fully compatible with Infor® LBI and Zebra® MotionWorks®. Location and asset data from the delivered hardware and software solution shall be capable of transmission to Infor® LBI and AgileRank aRTLS.

• Software Interface Compatibility: The Contractor shall ensure delivery of a software interface that integrates seamlessly with CenTrak® RTLS and Zebra® MotionWorks® solutions for asset tracking. The delivered software and user interfaces shall accept and process location data from CenTrak® and Zebra® systems without loss of fidelity or functionality.

• Bluetooth® Low Energy (BLE): The Contractor shall ensure that the delivered BLE software platform integrates fully with the existing CenTrak® RTLS, Zebra MotionWorks®, and AgileRank aRTLS for asset management. BLE-generated location and asset data shall be transmittable to Infor® LBI and AgileRank aRTLS, and harmonized with CenTrak® and Zebra® data standards to support unified reporting, analytics, and operational workflows.

• Data Architecture Compatibility: The Contractor shall ensure that delivered solutions align with the existing CenTrak®, Zebra®, Infor® and aRTLS® data architecture to enable interoperability and data integrity across all systems.

• UI Integration with Inventory Systems: The Contractor shall ensure that at least User Interface includes a fully functional interface with VA’s current inventory management systems, AEMS/MERS and IBM Maximo, to enable bidirectional data exchange. In addition, data shall be transmissible to the VA Corporate Data Warehouse (CDW). Additionally, the UI shall integrate with our CMMS (Nuvolo©) for facilities and asset lifecycle management and provide reporting capabilities through Microsoft Power BI, enabling customizable dashboards, analytics, and exportable reports for operational and strategic decision-making.

These requirements ensure full interoperability and effective data exchange (“cross-talk”) between active RTLS, passive RFID, and BLE asset management systems within VA health care systems.

3.2 TEAMING AND RESELLER REQUIREMENTS

The Contractor shall maintain formal teaming agreements or authorized reseller/distributor status with the Original Equipment Manufacturers (OEMs) for all proposed hardware, software, and professional services throughout the all Ordering Periods. Documentation of these agreements shall be provided to the Government during the contract kickoff meeting and updated upon any change in status. The Contractor shall ensure that all OEM partnerships grant full rights to procure, configure, install, integrate, and support the proposed solutions, including access to OEM technical resources, firmware updates, and warranty services. Failure to maintain OEM authorization or teaming agreements during the Ordering Periods may result in termination for cause.

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, consistent with the general requirements of this PWS.

4.1.1 Performance Period

The Ordering Period shall be four (4) years from the date of award. The Period of Performance (PoP) for any TO may go up to 12 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, five are set by date:

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

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

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

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

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

4.1.2 Place Of Performance

The place of performance shall be identified in individual TOs within our HCS(s). The list of current Health Care Systems supported by this requirement, and their addresses, are given in Table 1.

ID Name Address

570 Central California Health Care System (CCHCS) 2615 E. Clinton Ave. Fresno, CA 93703-2286

612 Northern California Health Care System

(NNHCS)

10535 Hospital Way Mather, CA 95655

640 Palo Alto Health Care System (PAHCS) 3801 Miranda Ave. Palo Alto, CA 94304

654 Sierra Nevada Health Care System (SNHCS) 975 Kirman Avenue Reno, NV 89502

662 San Francisco Health Care System (SFHCS) 4150 Clement St. San Francisco, CA 94121

593 North Las Vegas Health Care System

(NLVHCS)

6900 N. Pecos Road North Las Vegas, NV 89086

459 Pacific Islands Health Care System (PIHCS) 459 Patterson Road Honolulu, HI 96819

623 Eastern Oklahoma VA Healthcare System

(EOHCS)

1011 Honor Heights Dr, Muskogee, OK 74401

635 Oklahoma City VA Healthcare System (OKL) 921 NE 13th St, Oklahoma City, OK 73104

436 Montana VA Healthcare System (FHM) 3687 Veterans Dr, Fort Harrison, MT 59636

Table 1: Health Care Systems covered under the scope of this contract

4.1.3 Travel

The Government anticipates travel under this effort to perform the tasks associated with the effort. Travel costs are included in the 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 TO.

5.0 SPECIFIC TASKS AND DELIVERABLES

Individual TOs may cover multiple functional areas outlined below. These functional area descriptions are provided to offer greater insight into the complexity and uniqueness of potential TO requirements addressed in this Performance Work Statement (PWS). Functional areas are not mutually exclusive; a single TO may include requirements spanning several areas.

5.0.1 Technology And Project Management

The Contractor shall implement comprehensive technology and project management practices across all TOs. Responsibilities include developing and maintaining a Master Project Plan (MPP) covering scope, schedule, cost, quality, resources, communications, risks, and delivery, as well as coordinating multi-disciplinary stakeholders (Nursing, HTM, OIT, SCM, Engineering, etc.). The Contractor shall administer formal governance routines (steering committee, change control board) and maintain artifacts (risk/issue/change logs) in a VA-approved repository. The Contractor shall assist with defining, tracking, and continuously refining KPIs aligned to VA objectives including location accuracy, system uptime, and integration success rate, with variance analysis and corrective action plans. Project controls shall include dependency tracking and critical path analysis.

Deliverables:

• Master Project Plan (MPP) — MS PowerPoint or PDF, baseline within 30 days of TO award; updated monthly; includes milestones, dependencies, resource plan, and critical path; accepted when dates/logic are consistent and achievable.

• Stakeholder Engagement Plan — PDF; due within 30 days; meeting cadences, roles/RACI, communications channels, escalation paths; accepted when all VA stakeholder groups are identified and engagement commitments scheduled.

• Risk, Issue, and Change Logs — Living spreadsheet or IT Service Agreement tool export; updated weekly; include probability/impact, owners, target dates, and mitigations; accepted when items have owners and dated actions.

• Status Reports (Monthly) — PDF, MS PowerPoint, or dashboard; schedule performance index (SPI), KPIs, accomplishments/next steps, risks/issues;

accepted when variances >±10% include corrective actions.

• KPI Dashboard —Power BI; refreshed at least weekly; displays system uptime, accuracy, retrieval time, interface error rates; accepted when data sources are validated and thresholds codified.

5.0.2 System Design

The Contractor shall lead structured discovery (interviews, workshops, site assessment) to capture clinical workflows, asset classes, patient/staff movement requirements, and compliance constraints. Using these inputs, the Contractor shall produce an end-to-end architecture integrating CenTrak® Active RTLS, Zebra® Passive RFID, BLE, and user interfaces (UI), including coverage designs (zonal, room-level, within-room), capacity plans, and data models (tag schemas, location hierarchies, status states). Designs shall specify accuracy levels (Building, Zonal, Room Level), redundancy, network/security baselines, and interoperability across CMMS/EAM. The Contractor shall conduct design reviews with VA stakeholders and document resolutions.

The Contractor shall develop and maintain hardware and server design document for each site, updating it throughout implementation to reflect current design. The design documents shall include proposed changes to VA-provided maps and Engineering Space Files, hardware installation locations, and a draft server configuration and architecture optimized for facility needs. This draft shall include diagrams detailing server requirements, expected WAN bandwidth utilization, application latency, server specifications (power, BTUs, network connections), and the number of tags supported per server.

The Contractor shall leverage the existing Wi-Fi infrastructure at each facility for technology implementation. If the existing Wi-Fi is unavailable or insufficient to meet application resolution objectives, the Contractor shall promptly notify the Government and propose supplemental technologies to ensure full functionality.

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.

• Requirements Specification — PDF; due within 45 days; use-case narratives, NFRs (accuracy, latency), constraints; accepted when traced to design and test cases.

• System Architecture Diagram —PDF; due within 60 days; logical/physical views, interfaces, data flows, security zones; accepted after VA review sign-off.

• Coverage Maps & Accuracy Models — Floor plans with reader/beacon placements; propagation models; accepted when modeled accuracy meets targets by area.

• Data Dictionary & Tagging Standards — Spreadsheet/PDF; tag ID format, asset classes, states (clean/dirty/in-use), location hierarchy; accepted when aligned with CMMS/EAM fields.

• Design Review Report — PDF; per review; comments, decisions, action items;

accepted when all critical actions have owners and due dates.

5.0.3 Hardware Provisioning

The Contractor shall provide all required hardware components as specified and ordered at the TO level. All hardware shall be fully compatible with our existing AAMP and any additional proposed interface software, including CenTrak® Active RTLS, Zebra® Passive RFID and MotionWorks®, BLE technologies. Wireless hardware shall meet FIPS compliance standards.

The Contractor shall coordinate delivery schedules with VA stakeholders and obtain written or email concurrence from the Contracting Officer’s Representative (COR) prior to shipment. Upon delivery, the Contractor shall provide the COR with a signed Facility Receiving Report for each site, confirming the order and delivery of components, reconciling any discrepancies, and detailing delivery time, location, and the Government representative who received the shipment.

Categories of Hardware to be Provided:

• CenTrak® Components: Active RFID tags, exciters, readers, gateways, and supporting infrastructure.

• Zebra® Components: Passive RFID tags, handheld RFID scanners, Zebra MotionWorks® readers, and antennas.

• BLE Components: BLE tags, beacons, gateways, and associated mounting hardware.

• Networking and Infrastructure: Switches, cabling, PoE injectors, and any supplemental wireless hardware (FIPS-compliant).

• Server and Storage Hardware: As specified in the HSDD for local or centralized processing.

5.0.4 Software Provisioning

The Contractor shall provide all required software components for each site as specified and ordered at the TO level. All software shall be fully compatible with our AAMP, including CenTrak® RTLS software, Zebra MotionWorks®, Infor LBI®, and any BLE management applications. The Contractor shall ensure that all software licenses are valid for the entire PoP and include rights for installation, configuration, integration, and ongoing support. Software shall meet VA cybersecurity requirements, including FIPS-compliant encryption and adherence to VA Handbook 6500 standards.

The Contractor shall coordinate with VA stakeholders to schedule software delivery and installation and obtain written or email concurrence from the COR prior to deployment.

Upon installation, the Contractor shall provide the COR with a signed Software Provisioning Report for each site, confirming delivery, installation, and configuration details, as well as reconciliation of any discrepancies between planned and actual deployment.

Categories of Software to be Provided:

• CenTrak® Software: RTLS Asset Management platform, location engine, and device management tools.

• Zebra® Software: MotionWorks® asset tracking platform, RFID middleware, and handheld scanner applications.

• Infor® Software: LBI® for data aggregation and integration with CMMS/EAM.

• BLE Software: Beacon management platform, user interfaces, calibration tools, and mobile application integration.

• Supporting Software: Database components, APIs, and integration connectors for interoperability.

5.0.5 Staging

The Contractor shall manage delivery of approved hardware/software (CenTrak®, Zebra®, BLE beacons/gateways, Infor LBI® licenses) and accessories, preparing a detailed Bill of Materials (BoM) and delivery schedule aligned to installation waves.

Staging shall include firmware standardization, configuration pre-loads, and quality checks. Interoperability validation (firmware compatibility, protocol settings) shall be performed prior to shipment to sites. The Contractor shall document serials, MACs, tag IDs, and association procedures to enable traceability.

• Delivery Schedule — PDF or PowerPoint view; delivery windows, critical dependencies; accepted when aligned to installation plan.

• Pre-Configuration Checklist — PDF; per batch; firmware versions, network…