B08.03 Solicitation Amendment W9132T25RA0020002 SF 30.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 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 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.

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

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 (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 NUMBER

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

Continuation of Description

Miscellaneous text in this section has been modified to:

PERFORMANCE WORK STATEMENT

Sustainment Management System (SMS) Assembly Development

Revision 13 August 2025

1.0 BACKGROUND

1.1 BUILDER was developed by the U. S. Army Corps of Engineers (USACE) Construction Engineering Research Laboratory (CERL), Champaign, IL as a government-owned, data-driven decision support application which recommends repair, sustainment, and replacement actions for real property assets. BUILDER works by taking facility component condition information, projected component condition information, estimated component repair costs, and tailored business rules to create work plans for a portfolio of facilities. BUILDER's real estate inventory includes approximately 3 billion square feet of facility assets with a Plant Replacement Value (PRV) of approximately $1.5 trillion.

1.2 To perform the required analyses and generate work plan estimates, the system relies on accurate replacement costs of thousands of different asset components. Because costs fluctuate over time, they need to be updated annually.

Prior to FY26, updates to these component replacement costs, and the underlying data rights were provided through a single contract. However, beginning in FY26, the program will transition to acquiring these items separately, with one contract providing the cost data rights and a separate contract to develop the models for the component replacement and repair actions. (This contract intends to fulfill the requirements of the second contract).

1.3 The initial phase of this transition is to use the Government's Micro-Computer Aided Cost Estimating System 2nd Generation (MII) cost estimating software to "convert" the current list of component replacement actions into project item assemblies. Once developed, these assemblies would be re-priced by the Government on an annual basis using updated cost information provided in the MII Cost Book and labor and equipment libraries. Once re-pricing is complete, the lump sum total bare costs of each project item assembly would be exported from MII and imported as tables into BUILDER.

1.4 Over the next few years, customers of BUILDER will migrate to the Enterprise Sustainment Management System (ESMS). ESMS consolidates asset data from several stand-alone Sustainment Management System (SMS)

W9132T25RA0020002

applications under a single cloud-based application. These applications include data from several new asset "domains" such as utilities, rail transportation, fuels, waterfront, and civil works structures. As these domains are brought into ESMS, there will be a need to develop new component repair/replacement assemblies to support them.

2.0 PURPOSE OF CONTRACT

2.1 The purpose of this contract is for the contractor to use the MII application to develop (from scratch) project item assemblies associated with each asset component replacement action. These assemblies will be built from construction tasks in the MII Cost Book (or with custom-built user items developed by the contractor when necessary). Once an assembly is accepted by the Government, it will become the property of the Government for future maintenance and adjustment. The Government will use these assemblies for re-pricing component replacement costs in BUILDER and ESMS when updates to the MII Cost Book become available.

2.2 The scope of this contract requires the contract to develop the 4,202 component replacement actions that the system currently uses. The details of these component replacement actions are listed in Appendix A of this contract.

They primarily consist of components used in building-type facility assets.

2.3 All requirements of this contract must be fully met with all deliverables accepted within 285 calendar days from contract award.

3.0 REQUIREMENTS

3.1 Post-Award Coordination Meeting

Within 15 calendar days of award, the Government and contractor will have a meeting to meet the team and discuss the initial work to convert the existing CMC descriptions to assemblies under the base scope of the contract. This will involve a review of processes, expectations, and to answer any detailed questions related to coordination. The meeting will be virtual using MS Teams or other collaboration platform accessible to both parties. The meeting should be expected to last 1-2 hours.

3.2 Component Replacement Project Item Assembly Development

3.2.1 Using the MII software, the Contractor shall develop one (1) project item assembly per each (1) component replacement/repair action listed in Appendix A. Development must be done in accordance with the procedures provided in Appendix B - Section I. (The content found in Appendix B - Sections II and III will be the responsibility of the Government and NOT the contractor. However, the additional sections are being included for contractor awareness to show how the data will be maintained by the Government.) Where there is a conflict between Section I procedures and the body of this performance work statement (PWS), the PWS will take precedence.

3.2.2 Appendix A provides a listing of all component replacement tasks with relevant information to include: (a) a unique identifier numbers (CMC ID); (b) Uniformat II system description (level 2); (c) Uniformat II component description (level 3); (d) Uniformat II material category description (level 4); (e) the component type description (the specific item being replaced); (f) an imperial (detailed)description of the replacement component; and (g) the replacement unit of measure (UOM).

3.2.3 In Progress Clarifications. During execution of the work, the contractor must check for clarity in the descriptions and intent of each component replacement action. In most cases, the descriptions of the component replacement actions will be very broad and generic. The contractor must make (and document) assumptions as described below. However, for descriptions that lack sufficient clarity to develop an assembly, the contractor may contact the COR for guidance.

3.2.4 The project item assemblies must be developed as accurately as possible relative to the component repair /replacement action description. The project item assemblies must include all relevant construction tasks (including any incidental construction items) necessary to model a complete component replacement action. The quantities of each construction item must be proportionally accurate relative to the component replacement action being modeled.

Examples of incidental activities might include significant mobilization, selective demolition, component removal, component replacement, service re-connection, incidental repairs, testing, hauling, disposal, tipping fee, and significant demobilization/clean-up. The component repair/replacement actions modeled by each project item assembly must be complete, constructable, and code compliant as could be determined by a competent licensed engineer in the pertinent discipline(s).

3.2.5 When selecting construction tasks for developing the project item assemblies, the contractor must use the following order of precedence:

(1) First, use (to the maximum extent practical) the construction tasks available in the most current version of the Government-published MII Cost Book (or among those previously developed by the contractor as a custom user construction item).

(2) Second, if the proper construction task is not available in the MII Cost Book, the contractor must use a sufficiently analogous construction task that is available in the MII Cost Book. Crews and production rates may need to be modified within the project item assembly to ensure accuracy of the model. An explanation must be included in the Note field of the replacement construction item to fully explain the developer's logic and intent.

(3) Third, if one or more sufficiently analogous construction tasks are NOT available in the MII Cost Book, the contractor must develop custom user construction items to use in the project item assembly. When this is done, an explanation must be included in the Note field of the replacement construction item fully explaining the development of that item to include the logic in how the crew was selected, any adjustments in production rate, etc.

--enough information so that the Government can understand the model's logic. A current material unit cost must be researched and included for this item. The source(s) for the material cost must also be provided for the government to manually perform future updates to those construction tasks (company, contact, phone number, website, etc.).

3.2.6 When creating project item assemblies, any details or assumptions related to material selection, capacity selection, component location, configuration, repair methodology, and work task composition must be clearly and sufficiently documented (unless obvious from the task description). For example, the description of some component replacement actions may be generic and vague (e.g., "Window Replacement"). The description may also be agnostic to "in situ" details. For example, an "air handler replacement" task may not specify whether the air handler is located on a roof, in a mechanical room, or on a pad adjacent to the facility. In these cases, the Contractor must develop the assembly based on (in their professional judgement) the "most common" situation (with bias toward a conservative cost estimate given equal probabilities of occurrence).

3.2.7 Assembly-level assumptions must be documented in the Notes field of the project item folder. Construction item-level assumptions must be documented in the Notes field of the project item task. Global assumptions (e.g., "a 50-mile haul distance") must be applied consistently to all assemblies developed. Documenting assumptions will aid the Government in understanding the source of possible price variation.

3.2.8 For each project item assembly created, the contractor must create and include a unique Source Tag made up of the Unifomat II Level 4 prefix of the major component item being repaired/replaced followed by a period (.) and then followed by the assembly's CMC number provided by the Government. For example, "D201004.44016" for sink replacement. Uniformat II /WBS 3/21/07 Revision 3 must be used, available at: https://www.wbdg.org /navy/ndbm/uniformat-structure.

3.2.9 Each submittal must include all assemblies and any custom developed construction items within one or more MII (.mlp) files. The final submittal must be contained within a single (merged) .mlp file.

3.3 Progress Reporting

The Contractor shall submit monthly progress reports. There is no required format for the progress report except that it sufficiently provides evidence and demonstrates progress toward completion of the work. The report shall include a detailed narrative of the work accomplished in the reporting period, including quality control efforts. The report would benefit from including screen shots or other evidence to demonstrate progress.

Invoices shall be submitted in accordance with DFARS Clause 252.232-7006, Wide Area WorkFlow Payment Instructions. The frequency shall be at the contractor's discretion, but the values must coincide with the monthly progress reporting so that the total amount invoiced at any given time throughout the period of service is commensurate with the total portion of the effort reflected as complete within the corresponding progress reporting.

3.4 Quality Control Requirements.

https://www.wbdg.org/navy/ndbm/uniformat-structure.

https://www.wbdg.org/navy/ndbm/uniformat-structure.

Prior to each submission (draft and final), the Contractor must perform quality control on the assemblies they develop in accordance with their proposed QMP. This would include (but not be limited to):

a. Ensuring completeness of the work (ensuring all assemblies in the requirement are developed).

b. Ensuring the assemblies developed are complete, logical, constructable, code-compliant, and meet the intent of the task description.

c. Ensuring assumptions of each assembly are properly and sufficiently documented in the construction item and assembly level Notes section (as appropriate).

d. Performing independent technical review of the models by others who are experienced and credentialed to ensure the completeness, logic, code compliance, and buildability of the component replacement activities in the project item assembly model (and any custom construction user items that have been developed).

e. Ensuring the task assemblies will work properly when re-priced in MII using labor and equipment rate libraries.

f. Any custom construction items created have been documented (assumptions, source of researched material price, etc.)

g. Ensuring the applicable elements of Section I - Quality Control of the Performance Work Statement Appendix B are met.

h. Any assemblies developed must include a statement certifying that have been checked prior to submission to the Government in accordance with the QMP.

3.5 Controlled Unclassified Information (CUI):

This acquisition is for other than Commercial Off the Shelf (COTS) items; therefore, DFARS 252.204-7012 and -7020 are required per the prescriptions and will be included, but no CUI will be provided to the contractor, is anticipated to be created by the contractor, or is otherwise anticipated to be involved in the contract effort.

3.6 Submittal Schedule & Review

3.6.1 Schedule. Below is the required schedule for major milestones, delivery and review of submittals:

Activity Calendar Days from Award

Contract Award 0

Monthly Progress Report Submittals Every month of performance

In-Progress Review When 15% complete

Draft Submittal of Assemblies 210

Government Review of Draft Assemblies Complete (comments provided) 240

Review Meeting Between Government and Contractor to discuss comments 225 - 240

Final Submittal of Assemblies 270

Final Government Acceptance of Submittal (back-check) 285

3.6.2 In-Progress Review. Once approximately 15% of the assemblies are developed, the Contractor must submit a merged MII file of the assemblies created up to that point for Government review. This will not be a formal review but will allow the Government an opportunity to check to ensure there are no significant concerns with the procedures, completeness, or quality of the assembly development. If concerns are noted, the Government may request a meeting with the Contractor to discuss the concerns, clarify intent, and ensure the Contractor proceeds with an accurate understanding of the requirements.

3.6.3 Submittal Review Coordination. The Contractor must submit one review copy of the completed draft submittal project item assembly file to the Government. The Government requires 30 calendar days for review and to comment on the submittal. Within 15 days prior to the completion of Government review, the Government and Contractor will schedule a review meeting to discuss Government comments. The Contractor will then have approximately 30 calendar days to make necessary corrections and submit their final corrected assemblies to the Government. Lastly, the Government will perform a back-check of prior comments before fully accepting the assemblies.

3.7 Antiterrorism (AT)/Operations Security (OPSEC) Requirements

3.7.1 General security requirements and guidance: The security requirements described below apply to all contract personnel (including employees of the prime Contractor ("Contractor") and all subcontractor employees) supporting the performance requirements of this contract. The Contractor is responsible for compliance with these security requirements. Questions regarding security matters shall be addressed to the designated Government representative (e.g., Contracting Officer Representative (COR), Requiring Activity (RA) representative, or Contracting Officer (if a COR or other RA representative is not appointed)). Contract personnel are critical to the overall security and safety of US Army Corps of Engineers (USACE) installations, facilities and activities, and security awareness training contributes to those efforts. The Department of Defense (DoD) and Army security training requirements specified below, if applicable, are performance requirements; all applicable contract personnel shall complete initial training within 30 days of contract award or the date new contract personnel begin performance on the contract.

Within five business days from the completion of training, the Contractor shall provide written documentation (e.g., email or memorandum) to the Government representative. The documentation shall include the names of contract personnel trained and which training they completed; the Contractor shall maintain training records as part of their contract files and be prepared to provide copies of training certificates to the Government representative. Contractor personnel and vehicles are subject to search when entering federal installations. Additionally, all contract personnel shall comply with Force Protection Condition (FPCON) measures, Random Antiterrorism Measures (commonly referred to as "RAMs"), and Health Protection Condition (HPCON) measures. The Contractor is responsible for meeting performance requirements during elevated FPCON and/or HPCON levels in accordance with applicable RA plans and procedures --this includes identifying mission essential and non-mission essential personnel. In addition to the changes otherwise authorized by the changes clause of this contract, should the FPCON or HPCON levels at any individual facility or installation change, the Government may implement security changes that affect contract personnel. The Contractor shall ensure all contract personnel are aware of their security responsibilities, including any site-specific requirements identified in local policies or procedures.

3.7.2 Pre-screen candidates using E-Verify Program: Contractors shall comply with the requirements set forth in FAR clause52.222-54 Employment Eligibility Verification and FAR Subpart 22.18 in using the E-Verify Program at (https://www.e-verify.gov/) (website subject to change) to meet the contract employment eligibility requirements.

Contractors are encouraged to cooperate with Federal and State agencies responsible for enforcing labor requirements to include eligibility for employment under United States immigration laws in accordance with FAR 22.102-1(i). An initial list of verified/eligible candidates shall be provided to the COR no later than three business days after the initial contract award. When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, and submit it to the Contracting Officer to become part of the official contract file.

See PRS table attachment.3.8 Performance Requirement Summary (PRS):

Continuation of Deliveries or Performance

The delivery information for the following CLIN(s) / SLIN(s) / ELIN(s) were modified:

INFORMATION FROM TO

Period of Performance 30 Sep 2025 to 14 May 2026 30 Sep 2025 to 12 Jun 2026

Place of Performance - W52EU2 - W2R2 CONST ENGRG LAB

INFORMATION FROM TO

Delivery QuantityValue = 1. UnitOfMeasure = Job.

FrequencyOfDelivery = Monthly.7 Months, 0 Expected Shipment(s)

QuantityValue = 1. UnitOfMeasure = Job.

FrequencyOfDelivery = Monthly.8 Months, 0 Expected Shipment(s)

Addendum to Evaluation - Commercial Product and Commercial Services

Miscellaneous text in this section has been modified to:

Continuation of FAR 52.212-2

Evaluation Confidence Rating(s):

High C onfide nce

The Government will rate an Offeror with High Confidence if their proposal indicates they:

- fully understand the requirement,

- will use a team with experienced cost engineers who are familiar with the MII/MCACES application (as evidenced from having developed project item assemblies and detailed construction cost estimates using MII/MCACES),

- will apply thorough management processes that will mitigate most project risks, or

- will be successful in performing the contract with little or no Government intervention.

Some Confid ence

The Government will rate an Offeror with Some Confidence if their proposal indicates they:

- broadly understand the requirement,

- will use a team of experienced cost estimators who have used and are somewhat familiar with the MII/MCACES application (as evidenced from having generated detailed construction cost estimates using MII/MCACES),

- will apply management processes that mitigate key project risks, or

- will be successful in performing the contract will occasional Government intervention.

Low C onfide nce

The Government will rate an Offeror with Low Confidence if their proposal indicates they:

- lack understanding of the requirement,

- will use a team of cost estimators who appear to lack familiarity with the MII/MCACES application,

- will apply management processes that are either ill-defined or would not appear to manage project risk, or

- will appear to require regular Government intervention.

(iv) Price: Price will be evaluated for reasonableness; however, the lowest price may not be the best value for the Government.

The Government's determination of what represents the best value for this requirement will be based on our confidence that the services being offered will meet the needs detailed in Section C of this solicitation at a reasonable price.

KO CONTRACTING DIVISION, 2902 FARBER DRIVE PO BOX 9005

CHAMPAIGN, IL 61822-1072

UNITED STATES

BOOKER JORDAN, EMAIL: BOOKER.L.JORDAN@USACE.ARMY.MIL TELEPHONE: (217) 373-3344

AdminBy:

SCD: PAS: