36C26026R0025 0004.docx

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) 05-11-2026 653-25-103 36C260 Network Contracting Office 20

ATTN: V4CONT

1601 E. Fourth Plain Blvd Bldg.17, Suite B428 Vancouver

WA

98661 36C260 Network Contracting Office 20

ATTN: V4CONT

1601 E. Fourth Plain Blvd Bldg.17, Suite B428 Vancouver

WA

98661 To all Offerors/Bidders

36C26026R0025 04-14-2026

X X X ** HOUR & DATE for Receipt of Offers is EXTENDED to: 05-21-2026 12PM PDT X The purpose of Amendment 0004 is to:

1. Publish revised RFI responses from Amendment 0002 that was published on May 5, 2026

2. Extend the proposal submission date from May 14, 2026 at 10AM PDT to May 21, 2026 at 12 Noon PDT. See Block 11 for additional information.

All terms and conditions remain the same.

SANDRA K SNEDIKER

CONTRACT OFFICER

Please confirm the total number of Security Operations Centers (SOC) and monitoring locations. Is it correct that there are three (3) rooms total: one (1) primary SOC at the Roseburg campus, one (1) at Brookings, and one (1) at North Bend?

· Two main SOCs at Roseburg campus; One at Building 57 - Police Station, One at Building 1 – Dispatch Center Room,

· Include 10 sub SOCs viewing selected cameras only – One at Building 1AC – Authority on Duty Station (AOD), Building 81, Building 85 and Building 88. Reminder of buildings locations to be provided as they become available.

· One at North Bend

· One at Brookings Regarding remote capabilities, will VA IT be responsible for opening and configuring the required network ports to allow for multi-site remote viewing?

· No, that is the responsibility of the contractors on this project.

Please confirm that all SOC hardware (servers, displays, workstations, and cabling) will be provided by the VA as GFE.

· Computers/laptops will be provided by the VA however the Awarded Contractor will provide all other hardware.

Is it the government’s intent for the SOC that the contractor provides no hardware for this installation, or are there specific components the contractor is expected to procure?

· Computers/laptops will be provided by the VA however the Awarded Contractor will provide all other hardware.

Will the VA Medical Center IT department provide all necessary rack space, dedicated power, and environmental cooling for the new server infrastructure at all sites?

· Racks will need to be provided by the contractor, however space, power and cooling will be provided by the facility.

Please confirm the requirement for new Avigilon servers and full system programming at the Roseburg location.

· Yes, this is a requirement.

Should the new server capacity be scaled to account for future camera expansions? If so, please provide the projected camera count for these future additions.

· Yes, account for all the future cameras noted on the drawings, then add a 15% expansion capacity.

Please confirm if the scope for Brookings includes the installation of new Avigilon cameras, cabling, and servers.

· Yes Please confirm the requirement for new Avigilon servers and system programming at North Bend.

· Just programming Please confirm that VA IT will maintain sole responsibility for network management, including firewall rules and port access control.

· Yes Can the VA provide current "as-built" mapping and precise physical locations for all existing cameras at Roseburg and North Bend to assist in the programming phase?

· See attached “CUI” drawings Are all existing cameras to be replaced on a "like-for-like" basis with Avigilon hardware based on the provided Camera Capability Summary Matrix, or is there a specific quantity of new-location cameras required?

· See attached “CUI” drawings. All cameras need to be interchangeable/compatible with Avigilon.

Please clarify the significance of "dark" vs. "greyed-out" camera icons in the provided drawings. Do these represent existing-to-remain, future, or decommissioned units?

· Refer to the project drawings E-RB-001, LINE TYPES Legend and COMMUNICATIONS SYMBOLS LEGEND for specific details. See below for a high-level overview of the symbology.

· In Brookings CBOC

· Dark Replace existing cameras with new.

· In North Bend CBOC

· Gray = Existing to remain to be incorporated in new system

· Dark = Future cameras provisions provided under this contract to include memory space on servers, program interfaces, licenses and any other needed software/hardware.

· In Roseburg VA

· Site cameras: Existing cameras to remain and be integrated into the new system.

· Floor plan gray cameras= Existing to remain to be incorporated in new system

· Floor plan dark cameras = Future cameras provisions provided under this contract to include memory space on servers, program interfaces, licenses and any other needed software/hardware.

· For purposes of memory server sizing for the future cameras, assume the use of 3 Mega Pixels (MP) fixed dome cameras in corridor areas; 8 MP 360° cameras in lobbies and other open interior spaces; and 14 MP 360° cameras for exterior locations. All cameras shall support a minimum resolution of 1080p and frame per second (FPS) rates suitable for future AI-enabled functionality, including but not limited to multi-camera search and behavioral analytics.

Does the VA have a preferred mounting matrix or standard detail package for various environments (e.g., indoor recessed vs. outdoor parapet/pole mounts)? If not, should the contractor include all necessary mounting hardware (wall arms, pendant brackets, etc.) based on field verification?

· Include all necessary mounting hardware based on field verification.

For LPR-designated cameras, does the VA intend for these to be mounted on existing light poles, or is the contractor required to provide and install new dedicated poles, including the necessary trenching and power/data pathways?

· Intent is to add a future LPR at this location. Future provisions provided under this contract shall include memory space on servers, program interfaces, licenses and any other needed software/hardware. LPR resolution, MP and FPS provisions shall be suitable for this task.

To ensure the system meets the VA NVR storage requirements, please provide the required recording parameters:

Required frames per second (FPS) and retention period (days)?

· See specification 282300 for minimum requirements.

Estimated motion-detection percentage per day for storage calculations?

· During active time (generally Monday through Friday from 7:00 a.m. to 7:00 p.m) use 60% for interiors areas and parking/exterior areas. Use 15% during off times. See specification 282300 for minimum requirements.

Will the VA accept Avigilon "Object Detection" in lieu of standard motion detection for storage optimization?

· Not at this time Are the POE switches shown in the drawings to be Government Furnished Equipment (GFE), or is the contractor responsible for furnishing and installing all network switching hardware?

· No, they are contractor furnished.

The drawings specify an Avigilon AiNVR. Given the "High security impact" classification, please confirm if the VA requires FIPS-compliant servers, as standard AiNVR units may not carry that specific designation.

· Yes, they need FIPS-compliance. Avigilon and other manufacturers have Pre-hardened FIPS compliant Network Video Recorders available. Refer to specification 282300 2.11.D.1 for additional details.

What is the expectation for the North Bend and Brookings CBOCs? Is the contractor required to furnish new NVRs and licenses for these sites, and do they need to be integrated into the centralized Roseburg VAMC management system?

· Yes they need to be centralized.

· NVRs and cameras and licenses need to be purchased for Brookings

· Licenses need to be renewed/purchased for North Bend

· NVRs and cameras and licenses need to be purchased for Roseburg Is the VA standardizing on Avigilon Unity software? If so, are "Enterprise" level licenses required for all new cameras?

· We are using enterprise level software. There is a push for unity level software, however we are not there yet.

If the VA intends to re-use any non-Avigilon cameras, please confirm if those units will also require Enterprise-level licenses for integration into the new NVR environment.

· Yes The SOW mentions a phased removal of existing NVRs. To assist with bid accuracy, can the VA provide a schedule of existing camera licenses currently assigned to each NVR?

· Currently not required to have licenses on existing cameras.

To allow for a comprehensive engineering review of bandwidth, storage requirements, and UPS loads following the response to these RFIs, we respectfully request a 5-day extension to the proposal due date following the release of responses to these questions. This will ensure all offerors can provide a well-engineered, turnkey solution that minimizes risk to the Government.

· Proposal responses are due May 21, 2026 at noon PDT. This is an extension from May 14th to May 21st We request approval to substitute the specified Avigilon Network Video Recorders (NVRs) with BCD NVRs. BCD Network Video Recorders meet the basis of design. Please let us know if we need to submit a product sheet.

We request approval to substitute the specified cameras with Hanwha cameras. Hanwha cameras meet basis of design (see remarks below).

We are requesting consideration to push the proposal due date to allow sufficient time for OEM partners to provide adequate quotes that reflect all RFI answers and appropriate BOMs.

· A brand equal to the basis of design is acceptable if it meets the specifications, Enterprise Risk Analysis approval, and is compatible with existing previously installed Pelco and Avigilon hardware and software.

· Refer to specification 280500.1.4.A, B, & D for product quality assurance, and requirements for substitutions for the basis of design.

Hanwha Cameras NDAA Compliance: Hanwha Vision produces NDAA-compliant surveillance systems.

Manufacturing Origin: Products are made in South Korea and Vietnam, avoiding Chinese manufacturing restrictions.

Security Standards: Many products feature UL CAP certification, indicating high cybersecurity standards. These cameras meet the US security regulations for government and defense use, while Chinese brands like Hikvision and Dahua are banned.

Company Rebranding: Formerly Samsung Techwin, Hanwha Vision is a reputable non-Chinese alternative.

· A brand equal to the basis of design is acceptable if it meets the specifications, Enterprise Risk Analysis approval, and is compatible with existing previously installed Pelco and Avigilon hardware and software.

· Refer to specification 280500.1.4.A, B, & D for product quality assurance, and requirements for substitutions for the basis of design.

RFI 1 – Network Video Recorder (NVR) Product Substitution Request: The proposer respectfully requests approval to substitute the specified Avigilon Network Video Recorders (NVRs) with Vigilant NVRs.

Basis: The proposed Vigilant NVRs are equal to or exceed the basis of design, meeting or surpassing the required technical specifications, performance capabilities, scalability, and compatibility with VA security and IT standards.

Question: Will the VA approve the substitution of Vigilant NVRs in lieu of Avigilon NVRs, provided all functional, performance, and compliance requirements are met or exceeded?

· A brand equal to the basis of design is acceptable if it meets the specifications, Enterprise Risk Analysis approval, and is compatible with existing previously installed Pelco and Avigilon hardware and software.

· Refer to specification 280500.1.4.A, B, & D for product quality assurance, and requirements for substitutions for the basis of design.

RFI 2 – Camera Product Substitution Request: The Proposer respectfully requests approval to substitute the specified cameras with Hanwha cameras.

Basis: Hanwha cameras are equal to or exceed the basis of design, offering comparable or superior image quality, cybersecurity compliance, analytics capabilities, durability, and integration with the proposed Video Management System.

Question: Will the VA approve the substitution of Hanwha cameras as an acceptable equal to the specified cameras?

· A brand equal to the basis of design is acceptable if it meets the specifications, Enterprise Risk Analysis approval, and is compatible with existing previously installed Pelco and Avigilon hardware and software.

· Refer to specification 280500.1.4.A, B, & D for product quality assurance, and requirements for substitutions for the basis of design.

RFI 3 – Video Management System (VMS) Substitution Request: The Proposer respectfully requests approval to substitute the specified VMS with SiVeillance VMS.

Basis: SiVeillance VMS is equal to or exceeds the basis of design and is already installed and operational at the VA facility in Marion, Illinois, providing demonstrated compatibility with VA environments and operational requirements.

Question: Will the VA approve the substitution of SiVeillance VMS based on its existing deployment at a VA facility and its ability to meet or exceed all solicitation requirements?

· A brand equal to the basis of design is acceptable if it meets the specifications, Enterprise Risk Analysis approval, and is compatible with existing previously installed Pelco and Avigilon hardware and software.

· Refer to specification 280500.1.4.A, B, & D for product quality assurance, and requirements for substitutions for the basis of design.

RFI 4 – Security Clearance and Escort / Chaperone Requirements Request for Clarification: Please clarify the security requirements for contractor personnel performing installation, testing, programming, and commissioning activities.

Questions:

1. Are any additional security clearances beyond standard VA background investigations required for on‑site work?

· No, VA escort will be required for IT room access, or to qualify for unescorted - all individuals on the unescorted list have to undergo the appropriate background screening, which should typically align with a T-2 background check requirement. They will also need a PIV which can be obtained through the PIV office.

1. Will contractor personnel require a VA‑provided escort or chaperone while on‑site?

· Yes, when working in IT/Data rooms.

1. If escorts are required, will they be provided by the VA, or should contractors include escort labor and coordination in their proposals?

· To qualify for unescorted - all individuals on the unescorted list have to undergo the appropriate background screening, which should typically align with a T-2 background check requirement. They will also need a PIV which can be obtained through the PIV office.

RFI 5 – Proposal Due Date Extension Request: The Proposer respectfully requests consideration of a proposal due date extension to allow adequate time for manufacturers to provide formal compliance documentation for the proposed substitutions and to incorporate Government responses to RFIs.

· One week with Contracting’s concurrence Question: Will the VA consider extending the proposal submission deadline to accommodate resolution of RFIs and ensure Offerors can submit fully compliant proposals?

· One week with Contracting’s concurrence