am_01.pdf

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of theoffer 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 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.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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)

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

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

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE PAGE OF PAGES

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

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

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBE

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

J 1 3

0001 22 JUN 2026 572918

W9126G

W076 ENDIST FT WORTH

KO CONTRACTING DIVISION, 819 TAYLOR ST BOX 17300

FORT WORTH, TX 76102-6124

UNITED STATES

CHRISTINE NORIEGA, EMAIL: CHRISTINE.NORIEGA@USACE.ARMY.MIL

TELEPHONE: (817) 886-1104

SCD: PAS:

W9126G26RA087

17 JUN 2026

SEE SECTION G - CONTRACT ADMINISTRATION DATA

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

Project: B90176 Hangar Door Expansion (HADES)

See SF 30 Continuation Page

Proposal due date remains unchanged: July 17, 2026., 2:00pm, CT

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.

W9126G26RA087

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

CHANGES TO SOLICITATION W9126G26RA087

CHANGES TO THE SPECIFICATIONS

1. Replacement Sections: Replace the following section with the accompanying new section of the same number and title bearing the notation W9126G26RA087-0001.

00 21 16 INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFEROS

End of Summary of Changes

W9126G26RA087-0001

SECTION 00 21 16

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

AMENDMENT# 0001

1. GENERAL DESCRIPTION OF WORK

This construction project is for the expansion of hangar doors at Facility B90176, Fort Hood, Texas, to support the HADES mission and accommodate the ME-11B (Bombardier Global 6500) aircraft. The project includes replacing two existing hangar doors each with a single 120-foot-wide rolling sectional door of equal height vertical fabric door with two sections of increased height, requiring structural modifications to the pre-engineered metal building (PEMB).

Exterior improvements involve extending the trench drain and adjusting adjacent man-doors and wall mounted utility lines. Interior work consists of installing higher-capacity motors for the new door, refinishing and restriping affected areas of the hangar floor, making minor partitions and finish modifications to support new flight group requirements

2. OFFEROR'S QUESTIONS AND COMMENTS

a. All questions and/or comments are to be submitted via ProjNet at http://www.projnet.org/projnet. To submit and review bid inquiry items, bidders will need to be a current registered user or self-register into system. To self-register go to web page, enter email and bidder inquiry key, click Quick Add link, select agency USAGE, enter Key for this solicitation listed below, and your e-mail address, click Continue. Fill in all required information and click Add User. Verify that information on next screen is correct and click continue. From this page you may view all bidder inquiries or add inquiry. Bidders will receive an acknowledgement of their question via email, followed by an answer to their question after it has been processed by our technical team.

b. The Solicitation Number is: W9126G26RA087

The Bidder Inquiry Key is: 95NKA6-GDCFPI

c. Last day to submit ProjNet questions is seven calendar days prior to bid closure date in order to ensure adequate time is allotted to form an appropriate response and amend the solicitation, if necessary. If the system is not closed in a timely manner, an inquiry posted within seven calendar days of the receipt of proposals will still be regarded as untimely and may not be afforded a substantive response.

d. Offerors are requested to ask only one question per inquiry. If multiple questions are included, only the first one will be answered.

e. Oral explanations or instructions are not binding. Any information given to an offeror, whether oral or through ProjNet, that impacts the solicitation and/or offer http://www.projnet.org/projnet will not be binding unless given in the form of a written amendment to the solicitation.

f. Offerors are requested to review the specification in its entirety, review the Bidder Inquiry System for answers to questions prior to submission of a new inquiry.

The call center operates weekdays from 8AM to 5PM U.S. Central Standard Time Zone (Chicago). The telephone number for the Call Center is 833-389-1097 and 217-367- 3273.

3. PROPOSAL EXPENSES AND PRE-CONTRACT COSTS

This solicitation does not commit the Government to pay as a direct charge any costs incurred by the Offeror in the preparation and submission of its proposal or revisions. A stipend is not authorized.

4. NEGOTIATIONS

The Government intends to evaluate proposals and award a contract without negotiations with offerors (except clarifications as described in RFO 15.202(a)(2)).

Therefore, the offeror's initial proposal should contain the offeror's best terms from a cost or price and technical standpoint. The concept of a simultaneous competitive range and a common cut-off date for Final Proposal Revisions does not apply to this acquisition methodology.

5. HIGHEST TECHNICALLY RATED WITH A FAIR AND REASONABLE PRICE

(HTR-FRP) APPROACH

Award will be made to the responsible Offeror with the highest technically rated proposal found to have a fair and reasonable price. The HTR-FRP approach prioritizes technical merit and forbids the tradeoff between non-price factors and price. This approach prioritizes the best possible performance, provided the price is determined to be fair and reasonable. Here, all proposals are initially evaluated based solely on the non-price factors specified in the RFP. Only the price of the highest-ranked technical proposal is then evaluated to ensure it is fair and reasonable. Price is not an evaluation factor for the purpose of ranking proposals; it will be evaluated for fairness and reasonableness for the highest technically rated proposal in accordance with RFO 15.103-3.

6. SITE VISIT

Pursuant to Contract Clause "RFO 52.236-3, Site Investigation and Conditions Affecting the Work," prospective offerors will be permitted to inspect the site where services are to be performed and to satisfy themselves as to all general and local conditions that may affect the cost of performance of the Contract to the extent such information is reasonably obtainable. Offerors are urged and expected to inspect the site where the work will be performed. See the site visit information below:

Date: 22 June 2026

Time: 10:00am, CST Location: Central Texas Area Office (CTAO) at Fort Hood Bldg. 4617 72nd St and Sante Fe Avenue Ft. Hood, TX 76544 POC: Brad D. Butts EMAIL: brad.d.butts@usace.army.mil Phone: (254)220-2126

<AM#0001>Second Site Visit

Date: 07 July 2026 Time: 10:00am, CST Location: Central Texas Area Office (CTAO) at Fort Hood Bldg. 4617 72nd St and Sante Fe Avenue Ft. Hood, TX 76544 POC: Brad D. Butts EMAIL: brad.d.butts@usace.army.mil Phone: (254)220-2126 </AM#0001>

Note: Offerors and subcontractors wishing to participate must submit a complete listing of all personnel to attend the preproposal site visit, via encrypted email, to the referenced Base Access POC, a minimum of five (5) business days prior to the preproposal site visit.

7. PROPOSAL SUBMISSION

a. GUIDING PRINCIPLES FOR PROPOSAL SUBMISSION & REVIEW

This section outlines the foundational principles governing the submission and evaluation of all proposals. Adherence to these principles is mandatory.

(1) Completeness and Accuracy: Proposals must be submitted with all required information. Assumptions made by an offeror in place of required data may render the proposal non-compliant. If specific information is unavailable, this must be explicitly stated and explained.

(2) Regulatory Adherence and Citation: All submissions are reviewed for strict adherence to the current Revolutionary Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), Army Federal Acquisition Regulation Supplement (AFARS), USACE Acquisition Instructions (UAI), and all related policies, including all changes from the Revolutionary FAR Overhaul (RFO).

(3) Currency of Information: Offerors are solely responsible for ensuring their proposals comply with all regulations and amendments in effect at the time of solicitation.

(4) Mandatory Submission Requirements: Failure to provide the following documentation with the proposal may eliminate it from further consideration.

b. PROPOSAL SUBMISSION REQUIREMENTS

(1) Each volume shall be submitted electronically via the Procurement Integrated Enterprise Environment (PIEE) Solicitation module; no hard copies will be accepted. Any portion of the proposal that is changed (as a result of negotiations or proposal revisions) should be annotated and dated. Each volume shall be clearly labeled with its Title and Volume number. Each paragraph should be single spaced and shall be separated by at least one blank line. All narratives shall be in Adobe PDF format and shall be on 8 ½ x 11 size pages and a standard, 12-point minimum font size applies. Schedule Diagram, Drawings shall be in Adobe PDF format and shall be on 11 x 17 size pages. Where page limitations are specified, 11 x 17 size pages will be considered as one (1) page. Arial or New Times Roman fonts are required.

Page limitations, where specified in the RFP, shall be considered a maximum.

Pages that exceed the required page limitations will not be evaluated. Additional pages over the maximum allowed will be removed or not read and will not be evaluated by the Government. Tables and illustrations may use a reduced font size no less than 8-point and may be produced in landscape mode. All volumes of the proposal must be received by the closing date and time set for receipt of proposals.

Offerors may use compressions utility software such as WinZip or PKZip to reduce file size and facilitate transmission.

Offerors are advised to follow the PIEE instructions for uploading files. Additional instructions/guidance can be found at https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf

Interested parties shall submit responses no later than the date specified on the solicitation document. The time & date of proposal receipt will be the delivery time & date recorded within PIEE suite at https://piee.eb.mil/. Do not assume that electronic submission will occur instantaneously. Large files may take some time to upload.

Offerors should time their upload effort with prudence by not waiting until the last few minutes—this will allow for unexpected delays in the transmittal process and troubleshooting. It is the offeror’s responsibility to obtain written confirmation of receipt of all electronic files of the full proposal by the Fort Worth District Contracting office. In the event that the Solicitation Module is down, an alternate method for proposal submission will be provided only after obtaining approval from the Contracting Officer shayla.j.lucas@usace.army.mil to use an alternate submission method. Offerors are responsible for ensuring electronic copies are virus-free and shall run an anti-virus scan before submission.

(2) The following volumes of material shall be submitted:

Volume Title Digital Copies

Maximum Pages

I TECHNICAL PROPOSAL 1

20 Pages

II PRICE PROPOSAL 1

No page limitation

(3) Proposal Formats/Sections:

(a) The first page of the proposal for each volume must include the elements found at 52.215-1(c)(2).

(b) Table of Contents. Each volume of the proposal shall contain a detailed table of contents and must be bookmarked. If more than one Adobe PDF file is used for a volume, the complete table of contents shall be included in each. The offerors shall not submit any materials not required by this solicitation.

(c) Do not cross-reference similar material in the Past Performance/Technical Proposal with the Price Proposal. No dollar amounts from Volume II shall be included in Volume I.

(d) As this is a competitive negotiation acquisition, there is no public bid opening, and no information will be given out as to the number of offerors or the results of the competition until all awards are made.

(e) Bonds Format: Offerors shall submit bid bonds (Standard Form 24) in electronic format. Electronic copies of bid bonds shall be included in Volume II:

Offerors Certifications and Price. Hard copies of bid bonds with the raised seal are no longer required to be mailed in at this time and are not to be sent to the contracting office. Verification of Bid Bonds with sureties will be completed during the evaluation process and before award. Bid bond submissions shall be due by the proposal due date and time. Offerors are responsible for the accurate submission of the Bid Bonds with all signatures and seals applied.

(4) Joint Venture and LLC Proposal Requirements:

(a) For Joint Ventures:

• Joint Venture Agreement: A complete copy of the JV agreement and any addendum must be submitted with the proposal. For 8(a), HUBZone, or Mentor-Protege JVs, the agreement must comply with 13 CFR Part 124, 13 CFR Part 126, and 13 CFR Part 125, respectively.

• Representations and Certifications: A small business JV offeror must submit the representation required in Section 00 45 00 and RFO solicitation provision 52.219-1, Small Business Program Representations, for all applicable small business categories (Small, SDVOSB, WOSB, EDWOSB, HUBZone).

(b) Limited Liability Companies (LLCs):

• Proof of Signature Authority: The offeror must submit a copy of the operating agreement or other documentation that clearly demonstrates the authority of the signatory to bind the LLC to the contract.

(c) Core Joint Venture (JV) Agreement Provisions:

The submitted JV Agreement should, at a minimum, contain the following provisions to be considered compliant. If the JV Agreement is general and does not address the resources and responsibilities specific to the proposed work, this must be addressed in an addendum.

• Purpose & Management: The agreement must state the specific purpose of the JV and designate the small business partner as the "managing venturer."

• Ownership & Profit: For a separate legal entity JV, the small business must own at least 51%. It must also state that profits will be distributed commensurately with the work performed by each partner.

• Bank Account: The agreement must provide for a special bank account in the name of the JV, requiring consent from all parties for any withdrawals.

• Resources & Responsibilities: The agreement must itemize the resources to be provided by each partner and specify each party's responsibilities for contract performance. For Mentor-Protégé JVs, reference 13 CFR 125.8(b)(vi) and (vii), for 8(a), reference 13 CFR 124.513(c)(6) and (7), and for HUBZone, reference 13 CFR 126.616(c)(6) and (7).

• Performance & Records: This agreement binds all parties, jointly and severally, to uphold the terms and guarantee the full performance of all contractual duties. All official records pertaining to this agreement shall be securely maintained at the designated office of the managing venturer.

(d) Performance of Work Requirements:

• JV Work Share: The joint venture as a whole must perform the applicable percentage of work required by the prime contract's limitation on subcontracting clause.

• Small Business Work Share: The small business partner(s) must perform at least 40% of the work done by the joint venture itself. This work must be substantive and not just administrative in nature. If the small business partner is not expected to exceed the 40% workshare on this project individually, the JV must submit the workshare (in dollars) between each partner on all other projects to support that the workshare for this contract will result in compliance with the 40% requirement for the aggregate workshare across all contracts.

c. PROPOSAL FILES

(1) Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer.

(2) File Naming Convention:

Files submitted to PIEE shall be named as follows:

W9126G26RA087_COMPANY_NAME_VOLUME I

W9126G26RA087_COMPANY_NAME_VOLUME II

(3) Content Requirement.

(a) Each offeror must submit a TECHNICAL PROPOSAL (Volume I), OFFEROR’S CERTIFICATIONS AND PRICE PROPOSAL (Volume II). All volumes of the proposal must be submitted as separate volumes/files as outlined in paragraph 2 above. Do not cross-reference similar material between volumes.

(b) Proposals shall be received by the closing date and time set for receipt of proposals.

(c) Do not include exceptions to the terms and conditions of the solicitation in your proposal. Should the offer include any standard company terms and conditions that conflict with the terms and conditions of the solicitation, the offer may be determined “unacceptable” and thus ineligible for award. Should the offeror have any questions related to specific terms and conditions, these should be resolved prior to the submission of the offer.

(d) The data criteria specified for each factor identified in Section 00 22 16, shall be submitted as part of the proposal.

8. TARGET PRICE RANGE

The target price range for this project is between $6,500,000.00 and $8,500,000.00.

9. DEFINITIONS AND RATINGS

Significant Strength. An aspect of an Offeror’s proposal with appreciable merit or will exceed specified performance or capability requirements to the considerable advantage of the Government during contract performance.

Strength. An aspect of an offeror's proposal with merit or will exceed specified performance or capability requirements to the advantage of the Government during contract performance.

Weakness. A flaw in the proposal that increases the risk of unsuccessful contract performance. See RFO 15.001.

Significant Weakness. A flaw in the proposal that appreciably increases the risk of unsuccessful contract performance. See RFO 15.001.

Deficiency. Is any part of an offer that does not conform to a material requirement of a RFP. A material requirement is one that affects price, quantity, quality, or delivery, or that the RFP requires to be met at the time of proposal submission. See RFO 15.001.

Uncertainty. Any aspect of a non-cost/price factor proposal for which the intent of the offer is unclear (e.g., more than one way to interpret the offer or inconsistencies in the proposal indicating that there may have been an error, omission, or mistake).

In accordance with the DOD Source Selection Guide, Section 3.1, the Army methodology for evaluating Technical Approach and Related Risk is the Combined Technical/Risk Rating (see Table below). This methodology considers risk, in conjunction with the strengths, weaknesses, significant weaknesses, uncertainties, and deficiencies in determining technical ratings.

Note: Risk will not be rated separately; the Adjective Risk Ratings table is

Combined Technical/Risk Rating Method

Rating Description

Outstanding Proposal demonstrates an exceptional approach and understanding of the requirements and contains multiple strengths and/or at least one significant strength, and risk of unsuccessful performance is low.

Good Proposal indicates a thorough approach and understanding of the requirements and contains at least one strength or significant strength, and risk of unsuccessful performance is low to moderate.

Acceptable Proposal meets requirements and indicates an adequate approach and understanding of the requirements, and risk of unsuccessful performance is no worse than moderate.

Marginal Proposal has not demonstrated an adequate approach and understanding of the requirements, and/or risk of unsuccessful performance is high.

Unacceptable Proposal does not meet requirements of the solicitation and, thus, contains one or more deficiencies and is unawardable, and/or risk of performance is unacceptably high.

provided to define risk that is included in the combined technical/risk ratings.

Adjectival Risk Rating Description

Low

Proposal may contain weakness/weaknesses which have low potential to cause disruption of schedule, increased cost, or degradation of performance.

Normal contractor emphasis and normal Government monitoring will likely be able to overcome any difficulties.

Moderate

Proposal contains a significant weakness or combination of weaknesses which may have a moderate potential to cause disruption of schedule, increased cost, or degradation of performance. Special contractor emphasis and close Government monitoring will likely be able to overcome any difficulties.

High

Proposal contains a significant weakness or combination of weaknesses which is likely to have high potential to cause significant disruption of schedule, increased cost, or degradation of performance. Special contractor emphasis and close Government monitoring will unlikely be able to overcome any difficulties.

Unacceptable Proposal contains a deficiency or a combination of significant weaknesses that causes an unacceptable level of risk of unsuccessful performance.

Past Performance Relevancy Ratings

Rating Description

Very Relevant Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Relevant Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

Not Relevant Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

Past Performance Confidence Assessments

Rating Description

Substantial Confidence Based on the offeror’s recent/relevant performance record, the Government has a high expectation that the offeror will successfully perform the required effort.

Satisfactory Confidence Based on the offeror’s recent/relevant performance record, the Government has a reasonable expectation that the offeror will successfully perform the required effort.

Neutral Confidence No recent/relevant performance record is available or the offeror’s performance record is so sparse that no meaningful confidence assessment rating can be reasonably assigned. The Offeror may not be evaluated favorably or unfavorably on the factor of past performance.

Limited Confidence Based on the offeror’s recent/relevant performance record, the Government has a low expectation that the offeror will successfully perform the required effort.

No Confidence Based on the offeror’s recent/relevant performance record, the Government has no expectation that the offeror will be able to successfully perform the required effort.