S06 36C24826R0094 0001 5.1.26.pdf

5. PROJECT NUMBER (if applicable)

CODE 7. ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER 3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO. 1. CONTRACT ID CODE

FACILITY CODE CODE

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office. is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

15C. DATE SIGNED

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED STATES OF AMERICA

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER 16A. NAME AND TITLE OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30 PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243

(Type or print) (Type or print)

(Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code)

(If other than Item 6)

(Specify type of modification and authority)

(such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer)

1 9

0001 05-01-2026

548-26-104

36C248

Department of Veterans Affairs Network Contracting Office 8 (NCO 8)

8875 Hidden River Pkwy Ste 160A Tampa FL 33637

36C248

Department of Veterans Affairs Network Contracting Office 8 (NCO 8)

8875 Hidden River Pkwy Tampa FL 33637

To all Offerors/Bidders

36C24826R0094

X

X X

X 1

This amendment provides RFI responses for those RFIs received by the deadline posted in the solicitation.

Phase 1 Proposals are due 05/11/2026 at 10:00 AM.

Stacy Figlinski Contracting Officer

FY26: NRM (PROJ: 548-26-104) DB - Remove and Replace Nurse Call System Solicitation 36C24826R0094 Phase 1 RFIs

RFI 1: Please confirm Nurse call system must include a native interface via 37 pin connector (out of box, which must not require any additional middleware, servers, from current Hillrom Beds to connect) to the existing Hill-Rom smart beds for bed status to provide the following data points:

a. Near real-time visual dashboard providing actionable information:

i. Patient room number

ii. Patient name or corresponding HIPAA compliant naming convention.

iii. Patient notes (ex. Hard of hearing, NPO, etc.)

iv. Risk Status, based on EMR assessment (Falls, Skin, Pulmonary) or manual entry

v. Assigned staff

vi. Active calls

vii. Call wait times

viii. Rounding reminders automatically reset based on caregiver presence

(optional)

ix. Caregiver presence in room displays on Status Board, Dome Light illumination, graphical stations (with optional Real time Locating)

x. Patient presence in bed

xi. Bed exit armed

xii. Brakes set

xiii. Bed in low position

xiv. Individual Side rails up/down

xv. Head of bed angle

xvi. Patient weight

• The Contractor shall provide a nurse call system that meets the requirements of the SOW, including 37-pin wall plates/receptacles where identified and integration with patient beds as required by the SOW. It is confirmed no additional middleware, servers, for connection to Hillrom Beds. The proposed system shall satisfy the SOW performance, integration, cybersecurity, code, and VA approval requirements Refer to SOW: Section 2, 4, and all applicable SOW sections.

RFI 2: Please confirm Nurse Call System must have the option using the 37 pin connecter cable to automate bed exit alarm on the Hillrom Beds and customer defined data elements to be displayed on the status board.

• Refer to RFI 1

RFI 3: Please confirm Nurse Call System to pull bed data from 37 pin connector to provide a “bed exit history report” for clinical users to review the following from the Hillrom Beds.

• Refer to RFI 1.

RFI 4: Please confirm the nurse call system must have an ADT HL7 Admit, Discharge, Transfer (ADT) live at a VA site with CPRS/Vista to allow for the following desired workflows:

ADT must be able to Time stamp patient admission, discharge and transfer within the nurse call system.

Patient name is automatically updated/displayed on master console, status board and reporting; provides the ability to better acknowledge patient by name at the time of call to improve patient perception with nurse communication

Reporting Improves data accuracy in the following reports:

• call summary, call detail, bedside shift handoff & Event Chronology.

Provides current and accurate patient context information, eliminating need to verify correct patients in room/bed against patient bed placement in VISTA

Enables clinicians to make informed decisions based on accurate data for Root Cause Analysis

• This is not necessary.

RFI 5: Project Dependencies to start Implementation and provide 365/7/24 Support “Must Have” Requests in ensure start on day 1, and ensure support for life of ownership. Please confirm at time of bid the Nurse Call System must have the following (copies to be submitted with bid):

VA Directive 6550 Medical Enterprise Risk Assessment (MDERA).

Memorandums of Understanding and Interconnection Agreements (MOU-

ISA) which detail what data types are shared, who has access, and the appropriate level of security controls for all systems connected to VA networks.

• The MOU-ISA allows for remote access for faster installation.

• MOU-ISA allows for remote access faster response time, since no one is required to come onsite to fix the issue.

• Time to value is increased

• Contractor shall comply with all applicable VA information security, privacy, cybersecurity, TRM, network, and system-connection requirements required by the SOW and applicable VA policy. The Government does not confirm that all items listed in the RFI are required to be submitted at time of bid unless expressly required by the solicitation. Remote access, if proposed, shall be subject to VA review and approval and shall not be assumed. Refer to SOW: Section 13 and all applicable SOW sections.

RFI 6: Please confirm nurse call system should have a dedicated line to the IDF Closet from each room to avoid daisy chains.

• The SOW requires cabling, labeling, and system installation in accordance with the approved design, applicable codes, VA standards, and manufacturer requirements. Daisy-chaining is prohibited. Contractor shall provide a code-compliant and SOW-compliant design for Government review and acceptance. Refer to SOW: Section 4, 13 and all applicable SOW sections.

RFI 7: Please confirm if MEDERA can be used to use the network infrastructure to align EHRM Modernization in VA.

• This item is not specifically addressed in the SOW as written. Use of VA network infrastructure, MDERA documentation, EHRM modernization alignment, or related IT/security approvals shall be coordinated with the appropriate VA IT, Biomedical/HTM, Information Security, and Contracting stakeholders. Contractors shall not assume approval to use VA network infrastructure unless formally authorized. Refer to SOW: Section 4, 13 and all applicable SOW sections.

RFI 8: Please confirm the manufacturer, model family, software revision, and subsystem architecture of the existing nurse call system.

• The Government will provide available existing information to the extent it is available.

However, the Contractor/Design-Build A/E is responsible for field verification of existing conditions and shall not rely solely on existing documentation. Existing as-built information, if provided, is not guaranteed for accuracy. Refer to SOW: Section 2, 8, 12 and all applicable SOW sections.

RFI 9: Please confirm whether the existing system is TekTone, Rauland, Hill-Rom, Ascom, Jeron, or another platform.

• Contractor/Design-Build A/E shall field verify existing conditions, existing system components, interfaces, cabling, pathways, and architecture as part of the design-build scope. Refer to SOW: Section 2, 12 and all applicable SOW sections.

RFI 10: Please provide any available as-builts, risers, device schedules, or legacy submittals.

• Available existing as-built drawings and relevant information will be provided to the

Contractor/Design-Build A/E as required and to the extent available. The Government does not guarantee the accuracy or completeness of existing documents. Contractor/Design-Build A/E remains responsible for field verification and development of complete design documents. Refer to SOW: Section 8, 12 and all applicable SOW sections.

RFI 11: Please confirm whether any existing cabling, raceway, or pathways must be reused or replaced.

• Contractors shall not use existing cabling. Contractor shall evaluate existing conditions during design and field verification. Existing infrastructure may only be reused if code-compliant, using direct path to location, compatible with the proposed system, acceptable to the manufacturer, and approved through the Government’s design/submittal review process.

Otherwise, Contractor shall provide new infrastructure as required for a complete and functional SOW-compliant system Refer to SOW: Section 2, 4, 5, 8, 9 and all applicable

RFI 12: Please confirm whether the TekTone Tek-CARE 400 GEN3 platform is acceptable as a compliant or superior replacement system.

• Any proposed system, including TekTone TekCARE 400 GEN3 or any other platform, must meet the SOW, applicable VA standards, code requirements, cybersecurity/IT requirements, integration requirements, and solicitation requirements. Acceptability will be determined through proposal evaluation and/or submittal review, as applicable. Compatible with SOW and features. Refer to SOW: Section 2, 3, 4, 5, 13 and all applicable SOW sections.

RFI 13: Please confirm that equivalency determinations will be based solely on published TekTone documentation (UL listings, wiring, device specs, etc.).

• Equivalency or acceptability will not be based solely on one manufacturer’s published documentation. Product/system acceptability shall be based on full compliance with the SOW, solicitation, applicable codes, VA standards, cybersecurity/IT requirements, integration requirements, manufacturer documentation, and Government review/acceptance. Refer to SOW: Section 2, 3, 5, 8, 9, 13 and all applicable SOW sections.

RFI 14: If not acceptable, please identify required platforms or minimum criteria.

• The Government is not identifying or approving a specific platform through this RFI response. Minimum requirements are those stated in the SOW, solicitation documents, applicable VA standards, code requirements, IT/cybersecurity requirements, and integration requirements. Contractor shall propose a complete nurse call system that satisfies those requirements. Refer to SOW: Section 2, 3, 4, 5, 8, 9 and all applicable SOW sections.

RFI 15: Please confirm whether full system replacement is required (headend, stations, cabling, power, network, etc.).

• The project is for the remove and replace of the nurse call system. Contractors shall provide all design, labor, storage of materials, tools, equipment, and associated components necessary for a complete, functional, and SOW-compliant system. Contractor shall verify existing conditions and include all work required for complete system installation and delivery. Refer to SOW: Section 2 and all applicable SOW sections.

RFI 16: Please confirm whether all existing nurse call cabling must be replaced.

• New cabling shall be provided to deliver a complete SOW-compliant system. Refer to SOW:

Section 2, 4, 5, 8,9 and all applicable SOW sections.

RFI 17: Please confirm whether conduit and raceway may be reused.

• Refer to RFI 11

RFI 18: Please confirm whether the new system must be fully IP-based.

• The SOW identifies VoIP nurse consoles and includes requirements for system integration and device/cable labeling. Contractor shall provide a complete system meeting the SOW, code, manufacturer, VA IT/cybersecurity, and integration requirements. Refer to SOW:

Section 2, 4 and applicable SOW sections.

RFI 19: Please confirm required formats for as-builts (AutoCAD, Revit, PDF).

• Contractor shall provide as-built/record documents in the formats required by the SOW, VA standards, PG-18 requirements, and final Government direction. At minimum, Contractor shall provide complete record documentation acceptable to the Government. Final format requirements shall be coordinated with the CO/COR and confirmed during design/submittal review. Refer to SOW: Section 8, 9, 12 and all applicable related SOW sections.

RFI 20: Please confirm required compliance with PG-18-15 Volume C, VA TIL, VA Master Specs, NFPA 99, NFPA 101, and TJC.

• Contractor shall comply with the SOW, applicable VA TIL requirements, PG-18-15 Volume C where applicable, VA Master Specifications, NFPA 99, NFPA 101 and any applicable NFPA codes and standards, TJC requirements, and all other applicable federal, state, local, VA, and healthcare construction requirements. Refer to SOW: Section 5, 13, Appendix B and all applicable related SOW sections.

RFI 21: Please confirm whether facility-specific standards exist.

• Contractor shall comply with applicable VA Medical Center policies, facility-specific requirements, IT/network requirements, and operational coordination requirements as directed by the Government. In addition, full administrative rights will be granted to the facility without 3rd party tools and involvement. Any facility-specific requirements impacting the work shall be coordinated through the CO/COR. Refer to SOW: Section 3, 5, 13 and all applicable related SOW sections.

RFI 22: Please confirm whether integration with RTLS, wireless phones, paging, or EMR/EHR is required.

• The SOW requires integration with wireless, patient beds, Vocera/clinical phone system, RTLS, paging, EMR/HER and other systems as required by the VA. Any proposed integration with VA clinical, IT, or network systems shall be subject to VA review and approval. Refer to SOW: Section 4 Promote Uniformity and all applicable related SOW sections

RFI 23: Please confirm whether full device schedules, risers, floor plans, network diagrams, and phasing plans are required.

• Contractor shall provide complete design and construction documents required by the SOW and applicable VA design-submission requirements, including floor plans, network diagrams, full device schedules, risers where applicable, network diagrams where applicable, and phasing plans necessary to construct and deliver a complete SOW-compliant system. Refer to SOW: Section 2, 6, 9 and all applicable related SOW sections.

RFI 24: Please confirm whether sample submittals or mock-ups are required.

• Submittals or mock-ups are required in accordance with the SOW, specifications, and VA review process: Refer to SOW: Section 13 Resources, Appendix B and all applicable related SOW sections.

RFI 25: Please confirm whether factory certification documentation is required for installers.

• Installer qualification shall comply with the SOW, manufacturer requirements, applicable codes, VA requirements, and approved specifications. Nurse call manufacturer and installer requires certification, Contractor shall provide documentation demonstrating compliance in addition to any safety and training requirements. Refer to SOW: Section 5 General, Section 13 Resources and all applicable related SOW sections.

RFI 26: Please confirm whether clinical schedules will be provided for phasing coordination.

• Clinical and operational coordination will be performed with the VA through the CO/COR.

Contractor shall develop and submit a phasing plan and schedule for review and shall coordinate work to minimize disruption to patient care and facility operations. Refer to SOW:

Section 6 : Scheduling, Phasing, and Working Hours and all applicable related SOW sections.

RFI 27: Please confirm whether after-hours or weekend work is required.

• Contractor is responsible to schedule accordingly so that the hospital may maintain 24/7 operations. Refer to SOW: Section 6: Scheduling, Phasing, and Working Hours and all applicable related SOW sections.

RFI 28: Please confirm whether temporary nurse call coverage is required during cutover.

• Contractor shall maintain patient safety and continuity of required nurse call functionality during cutover, outages, shutdowns, and phasing. Refer to SOW: Section 6 : Scheduling, Phasing, and Working Hours and all applicable related SOW sections.

RFI 29: Please confirm whether infection control barriers, negative air, or HEPA filtration are required.

• Contractor shall comply with the SOW infection control and safety measures, including barriers, negative air, HEPA filtration, containment, cleaning, and work-area controls. Refer to SOW: Section 7: Infection Control and Safety Measures and all applicable related

RFI 30: Page 7 of 58 of the solicitation state that we are to provide a completed “Attachment 02

- Safety or Environmental Violations and Experience Modification Rate (EMR) Form” . Assuming this is referencing Attachment 19 EMR 1 Page, is it acceptable to include Attachment 19 after Factor 3?

• The solicitation should read:

15. SAFETY AND ENVIRONMENTAL RECORD: (SUBMIT WITH PHASE TWO PRICE

PROPOSAL) Offerors shall submit with their proposal a completed Attachment 19 - Safety or Environmental Violations and Experience Modification Rate (EMR) Form, which supplies the Government information pertaining to your firm’s past Safety and Environmental record.

A submitted form represents a certification of your firm’s past Safety and Environmental record identifying serious, willful, or repeat violations from OSHA or any EPA violations within the last 3 years. Please attach explanation for any violations.

RFI 31: Page 8 of 58 of the solicitation states that we are to provide a total of three (3) work experience projects on the “Specialized Experience Information Form”. Assuming this is referencing Attachment 16 Experience Information Sheet 4 Pages, this PDF states we must have a total of four (4) projects. Can you please confirm that we are only required to provide a total of 3 projects?

• Three projects are required. The form has been corrected and is attached to this amendment.

RFI 32: In accordance with FAR 215.305 Proposal Evaluation (Jan 2025), the agency shall consider relevant past performance of affiliates of the Offeror. For two companies that are wholly-owned subsidiaries controlled by the same parent company, will past performance of one subsidiary (not the Offeror) be deemed relevant for the Offeror's use for this solicitation?

• 215.305 is from DFARS, those regulations are not used in our solicitations.

RFI 33: Please confirm for joint venture offerors that projects presented under Factor 2 Specialized experience may be performed by either JV member.

• Yes.

RFI 34: Page 6 of 58, Part 8 – SDVOSB Verification references verification via both System for Award Management (SAM): https://www.sam.gov and SBA Veteran Small Business Certification (VetCert): https://veterans.certify.sba.gov. VetCert currently states “Certified Veteran firms can be verified through Small Business Search (https://search.certifications.sba.gov/).” Upon proceeding to the Small Business Search (SBS), the top banner states “Effective August 1, 2025, VOSB and SDVOSB joint venture designations will no longer be reflected in SBS. Click here to learn more (https://sbaone.atlassian.net/wiki/external/MzY1YTczZGM3NGM0NGNlZDg1Y2I2YTU1YTY1NT diZTA).” After clicking “Click here to learn more” bullet three (3) states “Can my joint venture still bid on VOSB and SDVOSB contracts if it’s not listed in SBS? Yes! According to 13 CFR 128.402(a), to be eligible to submit an offer on a VOSB or SDVOSB contract, 1. The joint venture should be designated as a VOSB or SDVOSB joint venture in SAM with the VOSB or SDVOSB-certified joint venture partner identified, and 2. The VOSB or SDVOSB joint venture partner must be certified. There is no regulatory requirement for the joint venture to be certified or designated by SBA. In fact, the regulation referenced above specifically states: “SBA does not certify VOSB or SDVOSB joint ventures…” Please review the regulation for additional eligibility criteria.” Pursuant to the above, it appears SDVOSB Joint Ventures cannot be verified via VetCert, but RFP Section 8 requires SDVOSB Verification via SAM and VetCert. Verification via VetCert is not possible at this time, based upon VA website statements referenced above.

Will the Government please revise RFP Section 8 to allow for SDVOSB JV verification via means other than VetCert?

• This will not be changed in the solicitation. The SDVOSB of the JV will be verified as an

SDVOSB through VetCert.

RFI 35: Please confirm the evaluation criteria for determining “equal or better.” Please confirm whether a feature by feature comparison matrix is required. Please confirm whether manufacturer letters of compliance are acceptable. Please confirm whether equivalency must include UL/ETL listings, audio quality, dome light logic, network architecture, and workflow features.

• There is no Equal or Better requirement in this solicitation.

RFI 36: Please provide the evaluation and scoring methodology for selecting the Design Build provider. Please confirm whether weighted scoring will include technical approach, system compliance, past performance, schedule, price, risk mitigation, infection control, and phasing strategy. Please confirm whether the system platform will be scored separately from team qualifications. Please confirm whether a live demonstration or mock up is required. Please confirm whether the VA intends to use Best Value Trade Off or LPTA.

• The technical proposal should address the evaluation factors for Phase 1 as stated in the solicitation. The Offeror’s response to those factors will be evaluated. Separate information such as a live demonstration is not requested and will not be considered.

RFI 37: Please confirm whether A/E firms will be evaluated on healthcare low voltage experience, nurse call design, VA DB experience, ICRA, and phased construction expertise.

Please confirm whether A/E scoring includes ability to produce coordinated construction documents, accurate device schedules, and integrated low voltage/electrical/architectural designs. Please confirm whether the VA considers UL listed nurse call design expertise and VA standards proficiency as evaluation strengths. Please confirm whether the VA allows proposing an A/E firm with proven healthcare communications engineering experience and VA project history.

• The technical proposal should address the evaluation factors for Phase 1 as stated in the solicitation. The Offeror’s response to those factors will be evaluated.

RFI 38: Please confirm whether DB teams will be evaluated on experience performing nurse call replacements in active VA hospitals. Please confirm whether experience with full facility device takeoffs, accurate BOMs, phased cutovers, and clinical coordination will be scored.

Please confirm whether the VA considers turnkey capability, procurement accuracy, and multi floor deployment experience as evaluation strengths. Please confirm whether factory certified technicians, 24/7 support capability, rapid warranty response, and lifecycle support will be evaluated.

• The technical proposal should address the evaluation factors for Phase 1 as stated in the solicitation. The Offeror’s response to those factors will be evaluated.

See attached document: Attachment 16 Experience Information Sheet 4 Pages.