70RFPW26QW8000006 Amend 1.pdf

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:

(a) By completing items 8 and 15, and returning 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 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.

E. IMPORTANT: is not is required copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7.ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

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

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

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

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

D. OTHER (Specify type of modification and authority)

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.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

PAGESOF

Contractor

The hour and date specified for receipt of Offers to sign this document and return

Jennifer J. Moore

See continuation page

FPS WEST CCG (70RFPW)

U.S. Dept. of Homeland Security Office of Procurement Operations Federal Protective Service Acq. Division 1102 15th Street SW, Suite 105 Auburn WA 98001

DHS/FPS/West CCG/Region 8 U.S. Dept. of Homeland Security Ofc of Procurement Operations - FPS Federal Ctr, Bldg 44, PO Box 25266 Attn: <<Enter Contract Specialist>> Denver CO 80225

70RFPW OPO/FPS/WEST CCG/R8D

70RFPW26QW8000006

04/30/2026

04/06/2026

1 2

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGES

NAME OF OFFEROR OR CONTRACTOR

SUPPLIES/SERVICES

(B)

UNIT

(D)

UNIT PRICE

(E)

AMOUNT

(F)

OPTIONAL FORM 336 (4-86)

Sponsored by GSA FAR (48 CFR) 53.110

ITEM NO.

(A)

QUANTITY

(C)

NSN 7540-01-152-8067

70RFPW26QW8000006/0001

Requisition # 192126R08PRJP0043

COR: Jacob Rensel

CO: Jennifer Moore

CS: Katelin Davis, Katelin.b.davis@fps.dhs.gov

Intrusion Detection System (IDS) Installation at the Aberdeen Federal Building in Aberdeen, South Dakota.

A. The purpose of this Amendment is to post the

Questions and Answers (see the PDF paperclipped within this amendment). The answers are provided for informational purposes and do not amend or change the terms of the solicitation.

If there is a conflict between the solicitation and the information provided in the answers to the questions, the solicitation governs.

B. There are no other changes as a result of this amendment; all other terms and conditions shall remain the same.

**** OFFERORS ARE ENCOURAGED TO REVIEW THE RFQ

PACKAGE IN ITS ENTIRETY. ANY SUBMISSIONS WHICH

DOES NOT MEET THE REQUIREMENTS OF THIS RFQ WILL

BE REMOVED FROM AWARD CONSIDERATION. ATTACHMENT

F IS PROVIDED FOR YOUR CONVENIENCE AND OUTLINES

THE REQUIREMENTS OF THIS RFQ PACKAGE. ****

Sponsored by GSA FAR (48 CFR) 53.110

RFQ 70RFPW26QW8000006

Questions and Answers

1) Question: Can you please confirm what the existing access control system is (manufacturer, model, and current configuration)?

Answer: Yes, the GSA EPACS is installed at the site. Integration will be required between the EPACs and IDS panel.

2) Question: Is the GSA EPACS currently installed onsite, or is integration required with a remote/enterprise system?

Answer: The GSA EPACS system specifics are not provided or needed for us to be the trigger to the IDS for the doors with our readers on them. They utilize Gallagher as their PAC’s. Specifically onsite we have at minimum the High Sec Controller 6000 and are utilizing 8 In 2 Out Door Modules C300660.

3) Question: What level of integration is expected between the new IDS and the existing access control system (e.g., full integration, monitoring only, or data sharing)?

Answer: The triggers for the 6 points are all mounted near the respective door on a module. The vehicle entry door does not currently have a request to exit (REX) device installed. If this door is intended to serve as both an entry and exit point, a REX will need to be added, wired into the GSA EPACS, and properly configured to prevent false alarms when occupants exit the facility. If the door is "entry only" then no change is needed.

4) Question: Are there any existing network or infrastructure constraints we should be aware of for system integration?

Answer: The IDS installers would only need to wire to the provided termination/whip for the card reader doors. No "integration" beyond that is needed, as all triggering is handled from within the GSA EPACS for an alarm condition. The "zone" would just need to be able to differentiate between open, closed and short/trouble. Things are presently set up with 1k EOL resistance for the IDS trigger.

5) Question: Will the Government provide any existing system documentation, drawings, or configurations to assist with integration planning?

Answer: Yes, the Government has provided drawings. You can find it paperclipped within the RFQ.