36C10B25Q0519 FINAL.pdf

PAGE 1 of 102 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

VA-25-00065169

36C10B25Q0519 09-10-2025

Allison Fulton, Contract Specialist 512-981-4477 09-10-2025

10:00 CST

36C10B Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

541519

$34 Million

N/A

X

See Delivery Schedule

36C10B

Department of Veterans Affairs Technology Acquisition Center

36C10A

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

877-353-9791

PAR Excellence Weight-Based Inventory Management System (WBIMS) Software, Hardware, and Support Services

Period of Performance (POP):

PoP shall be 12-months from the date of award. Installation shall begin no later than 30 days after contract award date.

In accordance with (IAW) Product Description (PD) Section

2.0 and 2.1.3, installation shall be phased by location and begin at the Primary Location, John D. Dingell VAMC.

Installation and setup to be completed for all locations no later than 180 days after contract award.

Points of Contact Contracting Officer – Evan Schlisserman, evan.schlisserman@va.gov

Contract Specialist – Allison Fulton, Allison.fulton@va.gov x x

Evan Schlisserman

36C10B25Q0519

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW CLAUSE

B.2 SOFTWARE LICENSE, MAINTENANCE, AND TECHNICAL SUPPORT

B.3 CONTRACT ADMINISTRATION DATA

B.4 PRICE SCHEDULE

B.5 PRODUCT DESCRIPTION

SECTION C - CONTRACT CLAUSES

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

C.2 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR

INFORMATION SYSTEMS (NOV 2021)

C3. 52.212-4 CONTRACT TERMS AND CONDITIONS—COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES

C.4 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (JAN 2025) (DEVIATION FEB 2025)

C.5 52.227-19 COMMERCIAL COMPUTER SOFTWARE LICENSE

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

(FEB 2023)

C.7 VAAR 852.239-76 INFORMATION AND COMMUNICATION TECHNOLOGY

ACCESSIBILITY (FEB 2023)

C.8 VAAR 852.242-71 ADMINISTRATIVE CONTRACTING OFFICER (OCT 2020)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB

1998)

E.2 52.204-20 PREDECESSOR OF OFFEROR

E.3 52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS

AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (NOV 2021)

E.4 52.204-29 FEDERAL ACQUISITION SUPPLY CHAIN SECURITY ACT

ORDERS—REPRESENTATION AND DISCLOSURES (DEC 2023)

E.5 52.209-5 CERTIFICATION REGARDING RESPONSIBILITY MATTERS (AUG 2020)

E.6 52.209-11 REPRESENTATION BY CORPORATIONS REGARDING DELINQUENT

TAX LIABILITY OR A FELONY CONVICTION UNDER ANY FEDERAL LAW (FEB 2016)

E.7 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (MAY 2024) (DEVIATION

FEB 2025)

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

E.9 52.233-2 SERVICE OF PROTEST (SEP 2006)

E.10 NOTICE TO OFFEROR(S)

E.11 BASIS FOR AWARD

E.12 QUOTE SUBMISSION INSTRUCTIONS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW CLAUSE

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

Department of Justice (DOJ) in accordance with 28 U.S.C. § 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.2 SOFTWARE LICENSE, MAINTENANCE, AND TECHNICAL SUPPORT

(1). Definitions.

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

b) Licensor. The term “licensor” shall mean the Contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired.

The term “Contractor” is the party identified in Block 17a on the SF1449. If the Contractor is a reseller and not the Licensor, the Contractor remains responsible for performance under this Contract/Order.

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

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

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

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

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

(2). Software License.

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

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

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

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

(3). Software Maintenance and/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.

http://www.cpars.gov/

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

B.3 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: To Be Determined (TBD)

b. GOVERNMENT: Contracting Officer 36C10B Attn: Evan Schlisserman Evan.schlisserman@va.gov

Department of Veterans Affairs Technology Acquisition Center

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 Government Acceptance of Supplies and Services associated with Section B.4

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

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

AMENDMENT NO DATE

B.4 PRICE SCHEDULE

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

NOTE: Offerors are instructed to complete Section B.4 and submit with their quote.

Offerors are cautioned that alterations to the line items as specified below will not be accepted and will render quotes unacceptable. All questions shall be directed to the Contract Specialist, Allison Fulton, Allison.fulton@va.gov, prior to the closing date and time specified in the RFQ.

BASE PERIOD

Installation shall begin no later than 30 days after contract award date. In accordance with (IAW) Product Description (PD) Section 2.0 and 2.1.3, installation shall be phased by location and begin at the Primary Location, John D. Dingell VAMC. Installation and setup to be completed for all locations no later than 180 days after contract award. 12-Month

Base Period for support services shall begin 180 days after contract award.

LINE

ITEM DESCRIPTION QTY UNIT UNIT PRICE TOTAL

PRICE

0001 Software Licenses IAW PD Section 2.0 and all subparagraphs 1 LT NSP NSP

0001AA

PAR Secondary Facility License 101-300 Beds

1 EA $ $

Part Number: PX9110

0001AB

PAR Client Unlimited

Part Number: PX9120U

0001AC

PAR Vision Facility License

Part Number: PX9176

0001AD

PAR Bins Replenish License

6 EA $ $

Part Number: PX9186

0002 Interface Development Services IAW PD Section 2.0 and all subparagraphs 1 LT NSP NSP

0002AA

GIP Interface (VA)

Part Number: PX9295-GIP

0002AB

Project Management

12 MO $ $

Part Number: PX9809-PMFR

120 EA $ $

Small & Medium Platform Scales

Controller, Replenish, Ethernet

PAR Bins Scale, Lg Platform 50 Kg

20 EA $ $

Part Number: PX3273

PAR Bins Setup Kit

2 EA $ $

Part Number: PX3950C

PAR Hardware Accessories

0008 Storage Products IAW PD Section 2.0 and all subparagraphs 1 LT NSP NSP

0008AA

Plastic Storage Bins

0008AB

10 EA $ $

Bridge Allocation (unit plus sides/front)

0008AC

26 EA $ $

QS-LR36 qwikSIGHT Mobile Louvered Panel Units, 36"

0008AD

QS-LR18 qwikSIGHT Mobile Louvered Panel Units, 18"

Third Party Services

Onsite Implementation and Training Services IAW PD Section 2.0 and all subparagraphs

TOTAL BASE PERIOD $

B.5 PRODUCT DESCRIPTION

PRODUCT DESCRIPTION (PD)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration

Par Excellence, Phase I

John D. Dingell Veterans Affairs Medical Center Satellite Locations and Community Based Outpatient Clinics

Date: July 10, 2025

VA-25-00065169

PD Version Number: 1.2

1.0 BACKGROUND

Historically, the Detroit VAMC has used a non-weight-based Point-of-Use (POU) system for inventory management. The facility has realized this system is not efficient as it requires staff to continuously scan the inventories to track changes. The facility leadership researched how similar-sized facilities were able to gain better inventory tracking systems, reduce stockouts, and reduce costs. The facilities that have been the most successful in these transitions have moved to weight-based inventory management systems that automatically track the inventory.

2.0 PRODUCT REQUIREMENTS

The Weight-Based Inventory Management System shall produce an accurate real-time reading of quantities on-hand accessible by a web-based program and provide data mining capabilities that shall include at a minimum: current stock levels, recommended order points, average usage levels per item and ability to track medical supply usage per patient treated at the Detroit VAMC, Satellite and its CBOC locations.

The Weight-Based Inventory System shall be interfaced with the Generic Inventory Package (GIP). The primary purpose of the interface is to identify out of balance on-hand quantities and values between GIP and the Weight-Based Inventory System.

The Weight-Based Inventory System shall identify an out of balance on hand quantities and values, accounting for any due outs or due ins. If the out of balance condition is caused by a pending due in or due out, it shall be displayed separately to easily identify.

The Weight-Based Inventory System due-ins and due-outs shall automatically be removed when GIP due-ins and due-outs are “cleared”.

The Weight-Based Inventory Management System shall have color-coded stickers for item identification based on standard color-coding system shown in Attachment A.

Installed equipment shall have a one-year full equipment replacement for defects or damage not caused by VA personnel. Install does not include disassembly of existing storage devices.

Tasks under this PD shall be performed at the following VA facilities:

Primary Location:

1. John D. Dingell VAMC (Comp/Pen, IE 136), 4646 John R St, Detroit, MI 48201

Secondary Locations:

2. Detroit VAMC – Valor Center (IE 323), 3245 E Jefferson Ave, Detroit, MI 48207

3. Veterans Community Resource and Referral Center (VCRRC) (IE 197), 301

Piquette Ave, Detroit, MI 48202

4. Pontiac VA Clinic (IE 208), 44200 Woodward Ave, Ste 208 Pontiac, MI 48341

5. Pontiac VA Clinic (IE 425), 44200 Woodward Ave, Ste 208 Pontiac, MI 48341

6. Downriver VA Clinic (IE 422), 1640 Fort Street, Ste D, Trenton, MI 48183

Travel for this effort shall be built into the Contractor’s firm fixed price. Work May be performed at remote locations with prior concurrence from the Contracting Officer’s Representative.

The Contractor shall supply and install the following items at the specified locations, including any ancillary components that may be required for the system to be fully operational:

PAR Software Licenses

Software License (required for each period of performance)

UOM Est.

Qty

Location(s)

PX9110_101-300 PAR

Secondary Facility License 101-300 Beds

EA 1 N/A

PX9120U PAR Client Unlimited

EA 1 N/A

PX9176 PAR Vision Facility License

EA 1 N/A

PX9186 PAR Bins Replenish License

EA 6 John D. Dingell VAMC (1), Detroit VAMC

– Valor Center (1), Veterans Community Resource and Referral Center (VCRRC) (1), Pontiac VA Clinic (IE 208) (1), Pontiac VA Clinic (IE 425) (1), Downriver VA Clinic (1)

Interface Development and Services

Interface Development UOM Est.

Qty Location(s)

PX9295-GIP GIP Interface

(VA)

EA 1 N/A

Services PX9809-PMFR Project Management Flat Rate

1 N/A

PAR Scale Products

PAR Scale Products UOM Est.

Qty Location(s)

Small & Medium Platform Scales

EA 120 John D. Dingell VAMC (4), Detroit VAMC

– Valor Center (10), Veterans Community Resource and Referral Center (VCRRC) (66), Pontiac VA Clinic (IE 208) (17), Pontiac VA Clinic (IE 425) (9), Downriver VA Clinic (14)

Controller, Replenish, Ethernet

6 John D. Dingell VAMC (1), Detroit VAMC

– Valor Center (1), Veterans Community Resource and Referral Center (VCRRC) (1), Pontiac VA Clinic (IE 208) (1), Pontiac VA Clinic (IE 425) (1), Downriver VA Clinic (1)

PX3273 PAR Bins Scale, Lg Platform 50 Kg (CA = 4)

20 Pontiac VA Clinic (IE 208) (20)

PX3950C PAR Bins Setup Kit

2 Pontiac VA Clinic (IE 208) (2)

Storage Products

Third Party Storage Products

UOM Est.

Qty

Location(s)

Plastic Storage Bins LOT All Bridge Allocation (unit plus sides/front)

10 John D. Dingell VAMC (1), Detroit VAMC

– Valor Center (1), Veterans Community Resource and Referral Center (VCRRC) (5), Pontiac VA Clinic (IE 208) (1), Pontiac VA Clinic (IE 425) (1), Downriver VA Clinic (1)

QS-LR36 qwikSIGHT Mobile Louvered Panel Units, 36"

EA 26 John D. Dingell VAMC (2), Detroit VAMC

– Valor Center (6), Veterans Community Resource and Referral Center (VCRRC) (4), Pontiac VA Clinic (IE 208) (5), Pontiac VA Clinic (IE 425) (3), Downriver VA Clinic (6)

QS-LR18 qwikSIGHT Mobile Louvered Panel Units, 18"

EA 6 John D. Dingell VAMC (1), Detroit VAMC

– Valor Center (1), Veterans Community Resource and Referral Center (VCRRC) (1), Pontiac VA Clinic (IE 208) (1), Pontiac VA Clinic (IE 425) (1), Downriver VA Clinic (1)

2.1 WEIGHT-BASED INVENTORY MANAGEMENT SYSTEM

2.1.1 SALIENT CHARACTERISTICS

The Weight-Based Inventory Management System shall have the following physical, functional and performance characteristics:

1. Shall be weight based

2. Easily calibrated and accurate

3. Provide real-time visibility to our Secondary Inventory locations

4. Shall be able to interface with GIP package in IFCAP

5. Shall be capable of tracking, adjusting, and reporting comprehensive real time information pertaining to the inventory of a secondary location

6. It is imperative that depletion of stock triggers “pick” tickets based on Periodic Automatic Replacement (PAR) levels, Re-order points, and Emergency Stock Levels

7. Software shall be intuitive and easy to train on

8. Software shall be able to utilize multiple users with different levels of permissions

9. Reports generated by software shall be relevant to APICS Principles of Inventory

Management

10. Shall be able to handle a wide range of products based on size, thickness, and weight.

11. Complete generic identification: Weight-based inventory Supply Chain Solution

12. Applicable model/make/catalog number: PAR Express weight-based automation by PAR Excellence

13. Communication about system status including system failures

14. Materials Management Status –

a. Open Orders

b. Emergency/Critical Item Levels

c. Negative Quantities on-Hand

15. Item Locator

16. Customer Item Requisition

17. PAR Level Analysis

18. Current Levels –

a. Level recommendations by cost and usage demand SKU reduction recommendations

b. Items over par level

c. Stock outs and critical hits Par level value over time

19. Consumption

a. Average monthly usage

b. Consumption analysis including time

c. Consumption deviation

d. Consumption over time

20. Reports

a. Activity detail (sales, receipts, adjustments, etc.) to include time inventory on hand changed

b. Quantity on-hand Value on-hand

c. Department transactions

d. Cycle count sheet

e. Out of balance with GIP – on hand Due-ins

f. Due outs

g. Issue multiple discrepancy between GIP and Par Bin

h. Emergency levels

21. Orders

a. Existing orders

b. Order preview

22. Items

a. Item master Item history

b. Item classification Reconciliation history

c. Most recent reconciliation per item

2.1.2 LICENSING

One-year license agreement for use of Weight-Based Inventory Management System and related support. Automatic software upgrades of the installed program and software. Web-based program shall be available on any computer and/or mobile device for reporting purposes and evaluation of inventory levels for an unlimited number of users.

2.1.3 INSTALLATION

Installation shall occur during normal business hours, 7:30AM to 4:30PM local time.

The Contractor shall provide notification to the VA Project Team 10 days prior to starting on-site activities. The Contractor shall coordinate with site escorts for installation.

Install on two (2) VA owned laptops software package used for system set-up, installation, and management. This includes adding, deleting, and editing items stored in the bins/platforms to manage inventory and levels at each designated facility. Install and prepare VA owned server for transmission of information between Contractor and VA for maintenance and monitoring of equipment in use.

Installation shall begin no later than 30 days after contract award date. Installation shall be phased by location and begin at the Primary Location, John D. Dingell VAMC.

Installation and setup to be completed no later than 180 days after contract award.

2.1.4 ACCESS

The Contractor shall ensure that VA staff are able to access the weight-based inventory management system, and that VA staff are able to provision additional users themselves.

2.2 SUPPORT

Support to include continuous monitoring by means of a minimum of four remote checks of equipment functionality by Contractor personnel every 24 hours. Notification and maintenance support from Contractor personnel in the event of a problem with equipment or software. Contractor personnel shall respond to service calls no later than 24 hours after being notified of a problem with either equipment or installed software.

Equipment and related hardware shall be replaced within 48 hours of notification of a problem if user is not at fault for damage or defect.

2.3 TRAINING

The Contractor shall conduct two (2) in person training sessions for five (5) VA staff members on the Weight-Based Inventory Management System. The Contractor shall train the VA employees for the web-based program that shall have unlimited user access and provide reports and data mining capability of current inventory including but not limited to current stock levels, recommended order levels, and average usage levels. The system shall be capable of producing reports in Excel or text delimited format using commercially available software. Training shall include but is not limited to:

1. Adding items

2. Removing items

3. Assigning items

4. Weighing items

5. Editing items

6. Troubleshooting

7. Reporting functions

8. Par Vision

9. Process definition

2.4 PERFORMANCE MONITORING

Completion of the install will be verified by POC or designated personnel. Functionality and accuracy of the installed equipment will be continuously monitored by Logistics staff to ensure equipment is functioning properly and providing accurate and timely information for inventory and reordering purposes. Installed equipment and software is monitored by Contractor employees by daily check-ins that shall occur remotely at least four (4) times every 24 hours. Contractor support to be provided for any defects or functionality problems by contacting Contractor via email or telephone within time frames designated in Section 2.2 of this PD. The Contractor will meet (e.g. in person, telephone, etc.) with the POC monthly to address any unresolved issues. Any unresolved and/or continuous issues will be addressed to the Contracting Officer for corrective action.

2.5 PROJECT MANAGEMENT

2.5.1 DELIVERY ORDER KICKOFF MEETING

The Contractor shall conduct a virtual Delivery Order (DO) Kickoff Meeting with the VA Program Team, Contracting Officer (CO), Contract Specialist (CS) within five (5) business days of contract award. The Contractor shall provide a DO Kickoff Meeting Agenda no later than (NLT) two (2) business days prior to the DO Kickoff Meeting to the VA PM, COR, and Contract Specialist. The agenda shall include all topics to be discussed for successful contract execution. The Contractor shall provide DO Kickoff Meeting Minutes NLT three (3) business days after the DO Kickoff Meeting that summarizes the meeting and includes the primary contact information of all parties in attendance.

The VA Project Team will provide the VA Project Team email distribution list to the Contractor at the DO Kickoff Meeting.

Deliverables:

A. DO Kickoff Meeting Agenda B. DO Kickoff Meeting Minutes

3.0 SECURITY REQUIREMENTS

Vendor owned software and/or program (PAR Excellence) to be installed on VA owned server, laptop and desktop computer. Other access to vendor website and programs

(PAR Vision) will be permitted by vendor from any desktop computer using the World Wide Web.

Contractor personnel performing installation may be required to complete the Department of Veterans Affairs security screening. General Contractor’s employees shall not enter the work area without the appropriate badge. The Contractor shall wear a Contractor’s badge during the set-up of the system and any other on-site work. They may be subject to inspection of their personal effects when entering or leaving the work area.

4.0 GOVERNMENT FURNISHED EQUIPMENT (GFE)

The VAMC will furnish one (1) server and two (2) laptops for installation of vendor owned software and related programs needed to make the installed equipment operational.

5.0 RISK CONTROL

Employees of contractors responsible for installation and setup will have background check completed or show proof of background check completed no longer than one (1) year ago, from date of award including fingerprint analysis. Contractor employees shall always obtain VA badge and wear on their person above their waist and visible.

The Contractor may be installing a supply storage and tracking system in an area under construction. The Contractor will need to be cognizant of staff movements, equipment and a plethora of activity during certain periods of the workday. The Contractor shall be accompanied by an escort during on-site activities. Installation staff shall have no patient contact or access to sensitive patient information. COR will be available for risk intervention should the need arise.

6.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION

AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508)

On January 18, 2017, the Access Board issued a final rule that updated accessibility requirements covered by Section 508 and refreshed guidelines for telecommunications equipment subject to Section 255 of the Communications Act. The final rule went into effect on January 18, 2018. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

6.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT.

These standards are found in their entirety at: Revised 508 Standards and 255 Guidelines (access-board.gov). A single PDF file version of the Revised Section 508 Standards and 255 Guidelines will be supplied upon request or can be obtained from https://www.access-board.gov/ict/ https://www.access-board.gov/ict/ the Access Board website. Federal agencies must comply with the Rehabilitation Act of 1973, as amended.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

☒ E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA Guidelines)

☒ E204 Functional Performance Criteria ☒ E206 Hardware Requirements ☒ E207 Software Requirements ☒ E208 Support Documentation and Services Requirements

6.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

6.3 ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery.

The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

7.0 INFORMATION TECHNOLOGY USING SUSTAINABLE PRODUCTS AND SERVICES

Not Applicable.

8.0 SHIPMENT OF HARDWARE OR EQUIPMENT

All hardware shall be shipped to the Primary Location, John D. Dingell VAMC, and then distributed to the Secondary Locations as identified in Section 2.0 of this PD.

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

Ship To and Mark For:

Primary Alternate Name: John D Dingell VAMC Name: John D Dingell VAMC Address: 4646 John R St, Detroit, MI

48201 Address: 4646 John R St, Detroit, MI

48201

Primary Alternate Voice: 313-576-3358 Voice: 313-576-1675 Email: Timothy.Scheidsr@va.gov Email: Matoka.Johnson@va.gov

8.1 SPECIAL SHIPPING INSTRUCTIONS

Prior to shipping, Contractor shall notify Site POCs, by phone followed by email, of all incoming deliveries including line-by-line details for review of requirements. The Contractor shall not make any changes to the delivery schedule at the request of Site

POC.

Contractors shall coordinate deliveries with Site POCs before shipment of hardware to ensure sites have adequate storage space.

All shipments, either single or multiple container deliveries, shall bear the VA IFCAP Purchase Order number (if applicable) on external shipping labels and associated manifests or packing lists. In the case of multiple container deliveries, a statement readable near the VA IFCAP PO or Contract number shall indicate total number of containers for the complete shipment (e.g. “Package 1 of 2”), clearly readable on manifests and external shipping labels.

Packing Slips/Labels and Lists shall also include the following:

IFCAP PO # or Contract No.: ____________ (e.g., 166-E11234 (the IFCAP PO number is in block #20 of the SF 1449)) Project Description: (e.g. Tier I Lifecycle Refresh)

Total number of Containers: Package ___ of ___. (e.g., Package 1 of 3)

9.0 GENERAL REQUIREMENTS

9.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM).

Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

9.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

9.3 SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the Integrated Control Number (ICN) in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (MPI) for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.

9.4 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support IPv6-Only based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices, applications, and systems shall support all applicable functionality on native IPv6-Only as well as dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g., web, email, DNS, ISP services, etc.) shall support native IPv6-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.

https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119

9.5 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

9.6 TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents.)

9.7 POSITION/TASK RISK DESIGNATION LEVEL(S)

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

Position Sensitivity and Background Investigation Requirements by Service Task/Item Number

Service Task / Item Number

Tier1 / Low Risk Tier 2 / Moderate Risk

Tier 4 / High Risk

2.0 ☒ ☐ ☐

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

https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf https://www.cisa.gov/publication/tic-30-core-guidance-documents

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/ PRIVACY

LANGUAGE

NOTE: In the event of a conflict, VAAR Security Clauses take precedence over the language in this Addendum B.

APPLICABLE SECTIONS FROM: VA NOTICE 24-12, 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

B.1 GENERAL

This entire section applies to all acquisitions requiring any Information Security and Privacy language. Contractors, contractor personnel, Subcontractors and subcontractor personnel will be subject to the same federal laws, regulations, standards, VA directives and handbooks, as VA personnel regarding information and information system security and privacy.

B.2 VA INFORMATION CUSTODIAL LANGUAGE

a. The Government shall receive unlimited rights to data/intellectual property first produced and delivered in the performance of this contract or order (hereinafter “contract”) unless expressly stated otherwise in this contract. This includes all rights to source code and all documentation created in support thereof. The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data – General. The primary clause used to define computer software license (not data/intellectual property first produced under this Contractor or order) is FAR 52.227-19, Commercial Computer Software License.

b. Information made available to the Contractor by VA for the performance or administration of this contract will be used only for the purposes specified in the service agreement, SOW, PWS, PD, and/or contract. The Contractor shall not use VA information in any other manner without prior written approval from a VA Contracting Officer (CO). The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data – General.

c. VA information will not be co-mingled with any other data on the Contractor’s information systems or media storage systems. The Contractor shall ensure compliance with Federal and VA requirements related to data protection, data encryption, physical data segregation, logical data segregation, classification requirements and media sanitization.

d. VA reserves the right to conduct scheduled or unscheduled audits, assessments, or investigations of Contractor Information Technology (IT) resources to ensure information security is compliant with Federal and VA requirements. The Contractor shall provide all necessary access to records (including electronic and documentary materials related to the contracts and subcontracts) and support

(including access to Contractor and Subcontractor staff associated with the contract) to VA, VA's Office Inspector General (OIG), and/or Government Accountability Office (GAO) staff during periodic control assessments, audits, or investigations.

e. The Contractor may only use VA information within the terms of the contract and applicable Federal law, regulations, and VA policies. If new Federal information security laws, regulations or VA policies become applicable after execution of the contract, the parties agree to negotiate contract modification and adjustment necessary to implement the new laws, regulations, and/or policies.

f. The Contractor shall not make copies of VA information except as specifically authorized and necessary to perform the terms of the contract. If copies are made for restoration purposes, after the restoration is complete, the copies shall be destroyed in accordance with VA Directive 6500, VA Cybersecurity Program and VA Information Security Knowledge Service.

g. If a Veterans Health Administration (VHA) contract is terminated for default or cause with a business associate, the related local Business Associate Agreement (BAA) shall also be terminated and actions taken in accordance with VHA Directive 1605.05, Business Associate Agreements. If there is an executed national BAA associated with the contract, VA will determine what actions are appropriate and notify the contractor.

h. The Contractor shall store and transmit VA sensitive information in an encrypted form, using VA-approved encryption tools which are, at a minimum, Federal Information Processing Standards (FIPS) 140-2, Security Requirements for Cryptographic Modules (or its successor) validated and in conformance with VA Information Security Knowledge Service requirements. The Contractor shall transmit VA sensitive information using VA approved Transport Layer Security (TLS) configured with FIPS based cipher suites in conformance with National Institute of Standards and Technology (NIST) 800-52, Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations.

i. The Contractor’s firewall and web services security controls, as applicable, shall meet or exceed VA’s minimum requirements.

j. Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the Contractor may use and disclose VA information only in two situations: (i) in response to a qualifying order of a court of competent jurisdiction after notification to VA CO (ii) with written approval from the VA CO.

The Contractor shall refer all requests for, demands for production of or inquiries about, VA information and information systems to the VA CO for response.

k. Notwithstanding the provision above, the Contractor shall not release VA records protected by Title 38 U.S.C. § 5705, Confidentiality of medical quality-assurance records and/or Title 38 U.S.C. § 7332, Confidentiality of certain medical records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse or infection with Human Immunodeficiency Virus (HIV). If the Contractor is in receipt of a court order or other requests for the above-mentioned information, the Contractor shall immediately refer such court order or other requests to the VA CO for response.

l. Information made available to the Contractor by VA for the performance or administration of this contract or information developed by the Contractor in performance or administration of the contract will be protected and secured in accordance with VA Directive 6500 and Identity and Access Management (IAM) Security processes specified in the VA Information Security Knowledge Service.

m. Any data destruction done on behalf of VA by a Contractor shall be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management, VA Handbook 6300.1, Records…