Performance Work Statement (PWS) (Attachment 1).pdf

PERFORMANCE WORK STATEMENT

Enterprise Sustainment Management System (E-SMS) Universal Cost Assembly Development Contract

27 April 2026

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. The purpose of BUILDER is to recommend facility repair actions across a portfolio of real property assets. It works by taking facility component condition information, projected component condition information, estimated component repair costs, and tailored business rules to create facility-specific work plans. BUILDER's current real estate inventory includes approximately 3 billion square feet of facility assets with a Plant Replacement Value (PRV) of approximately $1.5 trillion. BUILDER’s primary customer has been the Department of Defense for the sustainment of real property on military installations. The system is managed specifically by the Sustainment Management System Technical Center of Expertise (SMS-TCX), located at CERL.

1.2 Over the next several years, customers of BUILDER will migrate to the Enterprise Sustainment Management System (E-SMS). E-SMS consolidates the function of BUILDER with several other stand-alone Sustainment Management System (SMS) applications under a single cloud-based web application. These other applications include PAVER (for paved services), ROOFER (for roofs), RAILER (for rail infrastructure), and FUELER (for fuel facilities). E-SMS will also incorporate several new asset domains to include utilities, waterfront, and civil works structures. As customers are on-boarded to the new system and new domains are incorporated, the remaining legacy SMS applications are planned to sunset.

1.3 To perform the required analyses and generate work plan estimates, E-SMS will rely upon accurate, up-to-date costs for the replacement, repair, and preventive maintenance of thousands of different facility asset components (i.e., windows, doors, boilers, condensers, light fixtures, etc.)

Because such costs fluctuate over time, they will need to be updated annually. As new domains are brought into E-SMS, the need for such cost information will continue to grow.

1.4 To generate the unit price cost estimates that E-SMS uses, cost model assemblies have been developed using the Government’s Micro-Computer Aided Cost Estimating System 2nd Generation (MII). Each assembly models the cost to replace a specific facility component. These assemblies are re-priced annually using labor, material, and equipment cost data from an updated version of the Tri-Service Automated Cost Engineering System (TRACES) MII Cost Book and its associated libraries. Currently, the TRACES MII Cost Book is updated annually, and access is available on a subscription basis (at cost). The website https://www.hnc.usace.army.mil/Media/Fact-Sheets/Fact- Sheet-Article-View/Article/482084/tri-service-automated-cost-engineering-system-traces/ can be viewed for additional details. The TRACES MII Cost Book contains construction tasks and crews found in the nine (9) most common construction cost data cost books. These include their Building Construction, Heavy Construction, Concrete & Masonry, Mechanical, Electrical, Plumbing, Interior, Site Work & Landscape, and Green Book.

Where needed items don’t exist within the TRACES MII Cost Book, custom items were developed and their costs independently researched and included for use in the newly developed assemblies.

Once re-pricing was completed, the lump sum total costs of each project item assembly would be exported from MII and imported as tables in E-SMS for the system to reference.

1.5 Prior to this contract, assemblies have only been developed for component replacement costs for building facilities. Instead of having separate assemblies for each component repair action, repair costs were derived through an equation using the component’s replacement cost and its current condition. Preventive maintenance costs have not yet been incorporated. This contract seeks to develop separate assemblies for not only additional component replacement actions, but also component-specific repairs and component-specific preventive maintenance actions across a much broader set of asset domains.

2.0 DEFNITIONS

a. Domain

A domain is a general categorization of assets in the built environment. E-SMS domains include buildings, utilities, waterfront facilities, pavements, rail assets, fuel facilities, water control structures, bridges, training areas and ranges, and specialized assets. Each asset managed within E-SMS will fall under a specific domain.

b. Asset

An asset is a system of components that work together to serve a specific function. The most common example of an asset is an individual building. Other examples could include a bulk fuel facility, wastewater treatment plant, a rail line, a runway, an earthen dam, etc. In most cases, an asset is identified with its own RPUID (real property unit identification) number.

With systemic domains, the concept of assets can be a bit more flexible. For example, an installation’s stormwater system could be considered a single asset or several related assets organized into sections.

c. Component

A component is a generic term for the items that make up an asset. It is the smallest managed item within SMS where condition is tracked and where repair, replacement, and preventive maintenance actions take place. Examples of components include walls, doors, windows, conduit, foundations, air handlers, chillers, boilers, carpet, light fixtures, ductwork, pumps, pipes, valves, transformers, sidewalks, storage tanks, utility vaults, etc.

A component may be unitary (such as a door, window, or equipment item) or area (such as walls, flooring, or roofing) or it can be described in terms of length (such as length of pipe, wire, or conduit). To measure its quantity, each component is assigned a specific unit of measure (UOM). The UOM for unitary components is “each” (EA). The UOM for components quantified by area is square feet (SF). The UOM for components quantified by length is linear feet (LF).

Some of the more complex components whose maintenance can be further broken down to the sub-component level (for example, a compressor on a heat pump condensing unit would be a sub-component).

d. Component Type

A component type is a component whose attributes are roughly defined to Uniformat level 4- 5 (or equivalent). Examples could include: “interior doors”, “fixed interior partitions”, and “rooftop HVAC unit”.

e. Component Specification

A component specification (or spec) is a component whose attributes are roughly defined to Uniformat level 6 or equivalent. This would include the component’s specific size, material, capacity, or method of the component. Example would include “Water pipe, cast iron, 8” diameter”.

f. Building System

A building system is a group of components which work together to serve a specific function for an asset. Systems are often installed and replaced together. Examples of systems include HVAC systems (which would include the condensing unit(s), air handler(s), ductwork, and control system), built-up roof systems (which would include the base sheet, bitumen layers, reinforcing fabric, and a surfacing layer). Other systems could include building automation control systems, security systems, etc. Entire systems may be replaced in lieu of individual components when it’s more economical to do so.

3.0 PURPOSE AND SCOPE

3.1 The purpose of this contract is to provide the SMS-TCX a flexible contract mechanism for the development of MII project item assemblies and associated data artifacts. The SMS-TCX will use the contractor developed assemblies to assess and model the cost of a variety of component repair, replacement, and preventive maintenance service actions that E-SMS needs to perform cost calculations and facility sustainment estimates.

3.2 Project item assemblies shall be either built from construction tasks in the TRACES MII Cost Book, modified, or with custom-built construction items developed by the contractor when construction tasks are not found in the cost book. For assemblies which require special materials not available in the MII Cost Book, the contractor shall survey revised costs for those materials.

3.3 Assemblies developed and accepted under this contract will become the property of the SMS- TCX for perpetual use and maintenance. The Government will use these assemblies for re-pricing component replacement costs in BUILDER and E-SMS as updated versions of the MII Cost Book become available.

3.4 The eleven (11) asset domains for which assemblies be requested will include:

a. Building facilities. Examples include administrative, training, maintenance, lodging, barracks, medical, hangars, schools, retail, industrial, commissary, storage, public safety, fitness, recreation, chapels, childcare facilities, etc. and their associated structural, roofing, envelope, architectural, mechanical, and electrical systems and components.

b. Utilities. Examples include electrical transmission and distribution, water distribution, gas distribution, stormwater systems (e.g., reservoir systems, retention basins, gates and channels), wastewater systems, boilers, chillers, thermal distribution, etc.

c. Waterfront facilities. Examples include piers, docks, shore utilities, decks, piles, seawalls, mooring equipment, gangways, fuel equipment, compressed air, etc.

d. Pavements. Examples include roads, parking lots, runways, taxiways, aprons, etc.

e. Rail assets. Examples include rails, ties, ballast, spikes, clips, joints (fishplates), turnouts, frogs, switches, signals, etc.

f. Fuel facilities. Examples include bulk fuel storage, fuel distribution systems, pipes, pumps, valves, meters, gauges, controls, strainers, filtration, product recovery, spill containment, dispensing/receiving equipment, etc.

g. Water control structures. Examples include dams (concrete or earthen), dikes, levees, weirs, gates, etc.

h. Bridges. Examples include vehicular, pedestrian, beam, metal truss, etc.

i. Training areas & ranges. Examples include live fire ranges, maneuver ranges, demolition ranges, urban warfare training areas, etc. and associated facilities and equipment.

j. Specialized assets. Examples include fences, security walls, barriers, blast walls, contingency assets, etc.—any non-memorial asset that could be found on a military installation that is not covered under another domain.

k. Memorial assets. Examples might include memorials, statues, fountains, cemetery assets, etc.

4.0 TASK TYPES

This paragraph describes the different tasks that can be ordered on an indefinite quantity-indefinite delivery basis under this contract. They include:

a. Type Ia: Replacement Model for Component Type (see para. 4.1)

b. Type Ib: Replacement Model for Component Spec (see para. 4.2)

c. Type IIa: Repair Model for Component Type (see para. 4.3)

d. Type IIb: Repair Model for Component Spec (see para. 4.4)

e. Type IIIa: Preventive Maintenance Model for Component Type (see para. 4.5)

f. Type IIIb: Preventive Maintenance Model for Component Spec (see para. 4.6)

g. Type IV: Material Item Re-Price & Assembly Update (see para. 4.7)

Requirements for each task type are described in the sub-paragraphs below. General requirements that apply to all tasks are provided in para. 5.0.

4.1 Replacement Model for Component Type (Type Ia)

4.1.1 Each Type Ia task includes all work to develop and deliver one (1) project item assembly for modeling the cost of replacing (1) unit (each (EA), square feet (SF), linear feet (LF), etc.) of a specified component type. The assembly may use construction items that are available in the

TRACES MII Cost Book, however, items which are not available in the TRACES MII Cost Book shall be custom developed by the contractor. The contractor shall assume the component type being replaced is already part of a constructed asset currently in use.

4.1.2 Because this model is based on a component type (rather than a component spec), it will need to represent a variety of component specifications. To develop an assembly for a component type, the contractor shall assume any details necessary to provide a complete model that: (1) accurately represents the variety of component specifications according to what is most common, and (2) is developed in such a way that it can easily be converted later to a component specification by changing out spec-level details.

4.1.3 Type Ia assemblies should not necessarily model “in kind” replacement of materials or equipment that industry generally considers obsolete. Rather, it should model replacing obsolete materials or equipment with materials or equipment with contemporary use items. For example, vitreous clay pipe would likely be replaced with PVC pipe.

4.1.4 The effort to survey material costs for a newly developed custom construction item is included in the initial assembly development effort. When assigning material costs for custom construction items, use the procedure identified in para. 4.7.3.

4.1.5 Example Type Ia Task

Assume the task order requested a project item assembly for the replacement of one (1) SF of Uniformat Level 4 interior wall partition.

To create this assembly, the contractor shall model the replacement action into subordinate construction tasks. This could include equivalent proportions of (1) the selective removal of the old partition (drywall and studwork), (2) new studs, (3) in-wall utilities, (4) new drywall, (5) priming and painting both sides of the drywall, (6) clean-up, and (7) associated debris removal.

Once the appropriate construction items were selected from the TRACES MII Cost Book, an assembly formula shall be used to link the various components to ensure the cost is modeled for one (1) SF of interior partition replacement.

4.2 Replacement Model for Component Spec (Type Ib)

4.2.1 This task is identical to the requirements of para. 4.1 except that the assembly is developed for a component specification rather than a component type. The task order will define which specifications to model. The idea is that the developer would merely copy and modify the existing component type assembly as the basis for the assembly and then merely add or modify construction items that make the component type specific to the specification.

4.2.2 This task will only be ordered (a) after the task for its parent component type has already been developed or (b) along with its parent component on the same task order. (There would never be an instance where a Type Ib task is ordered before or without a corresponding Type Ia task.) This will allow the component type model to be used as the basis for developing related component specifications.

4.2.3 This task may also be used to modify one (1) assembly (either a Type I component type or Type I specification) as directed in the task order. Assembly modifications are not expected to be complete re-developments but rather adding, deleting, or adjusting construction items in the assembly which less than half of the assembly’s composition.

4.3 Repair Model for Component Type (Type IIa)

4.3.1 Each Type IIa task includes all work to develop and deliver one (1) project item assembly for modeling the cost of (1) unit (EA, SF, LF, etc.) of a specified repair for a specified component type. The defect whose repair is to be modeled (and its UOM) will be specified in the task order. The contractor shall assume the component type being repaired is part of a constructed asset that is currently in use.

4.3.2 Because this model is based on a component type (rather than a component spec), it will need to represent a variety of component specifications. To develop an assembly for a component type, the contractor shall assume any details necessary to provide a complete model that: (1) accurately represents the variety of component specifications according to what is most common, and (2) is developed in such a way that it can easily be converted later to a component specification by changing out spec-level details.

4.3.3 It’s anticipated that very few construction items for repair actions are available in the TRACES MII Cost Book and the majority will need to be developed by the contractor as custom construction items. The effort to survey material costs for a newly developed custom construction item is included in the initial assembly development effort. When assigning material costs for custom construction items, use the procedure identified in para. 4.7.3.

4.3.4 Before modeling the repair, the contractor must consult operation and maintenance manuals for the component, common industry practice, and knowledgeable technicians in the pertinent discipline(s). The models must reflect the appropriate labor type, crews, and productivity rate to perform the work. The contractor will be responsible for performing this research.

4.3.5 Example Type IIa Task

Assume the task order requested a project item assembly for the repair of one (1) square foot (SF) of asphalt road.

To create this assembly, the contractor would model the replacement action into subordinate construction tasks for one (1) SF of the defect. For example, the assembly might include: One

(1) SF of saw cutting; 1 (SF) of asphalt patch replacement, 1 (SF) of rolling, and the removal and disposal of debris associated with one (1) SF of road surface.

Proportions would be set in the model to allow cost accuracy when multiple quantities of defect are repaired at a time.

4.4 Repair Model for Component Spec (Type IIb)

4.4.1 This task is identical to the requirements of para. 4.3 except that the assembly is developed for a component specification rather than a component type. The task order will define which specifications to model. The idea is that the developer would merely copy and modify the existing component type assembly as the basis for the assembly and then merely add or modify construction items that make the component type specific to the specification.

4.4.2 This task will only be ordered (a) after the task for its parent component type has already been developed or (b) along with its parent component on the same task order. (There would never be an instance where a Type IIb task is ordered before or without a corresponding Type IIa task.) This will allow the component type model to be used as the basis for developing related component specifications.

4.4.3 This task may also be used to modify one (1) assembly (either a Type II component type or Type II specification) as directed in the task order. Assembly modifications are not expected to be complete re-developments but rather adding, deleting, or adjusting construction items in the assembly which less than half of the assembly’s composition.

4.5 Preventive Maintenance Models for Component Type (Type IIIa)

4.5.1 Preventive maintenance is defined as maintenance activities aimed at preventing premature failures and prolonging component life or function. Preventive maintenance mostly applies to mechanical or electrical components but can include actions such as painting, re-coating, or re-sealing surfaces.

4.5.2 Each Type IIIa task includes all work to develop and deliver:

One (1) project item assembly for modeling the cost of performing all preventive maintenance work over a one-year period for a specified component type. This would include PMs performed weekly (x52), monthly (x12), quarterly (x4), semi-annually (x2), and annually and

One (1) project item assembly for modeling the cost of all preventive maintenance work to be performed every nth year for a specified component type. One (1) assembly would be developed for each nth year PM routine.

4.5.3 Because this model is based on a component type (rather than a component spec), it will need to represent a variety of component specifications. To develop an assembly for a component type, the contractor will assume any details necessary to provide a complete model that: (1) accurately represents the variety of component specifications according to what is most common, and (2) is developed in such a way that it can easily be converted later to a component specification by changing out spec-level details.

4.5.4 It’s anticipated that very few construction items for preventive maintenance actions are available in the TRACES MII Cost Book and the majority will need to be developed by the contractor as custom construction items. The effort to survey material costs for a newly developed custom construction item is included in the initial assembly development effort. When assigning material costs for custom construction items, use the procedure identified in para.

4.7.3.

4.5.5 The preventive maintenance actions and their frequencies must be obtained from component operation and maintenance manuals as informed by competent and knowledgeable technicians in the pertinent discipline(s). The models must reflect the appropriate labor type, crews, and productivity rate to perform the work. The contractor shall be responsible for collecting and reviewing all information and documentation needed to perform this work.

4.5.6 When developing an assembly for annual preventive maintenance, each preventive maintenance action to be performed during a specific frequency (weekly, monthly, etc.) should be clearly segregated and identified in the assembly. A multiplier must be used for each section of the assembly to bring that portion to an annualized cost. For example, the total cost of a PM action to be performed quarterly would be linked and multiplied by a quantity of four (4) to model the annual cost.

4.5.7 Example Type IIIa Task

Assume the task order requires development of preventive maintenance assemblies for a component type (air handler).

First, the contractor would research the operation and maintenance manual(s) of comparable equipment and speak with qualified technicians regarding proper preventive maintenance practices for that type of unit. After this research, PMs were found to be performed on a quarterly basis and every five (5) years. Therefore, the task will require two assemblies: One (1) to model all annual PM actions and one (1) to model all PM actions that should be performed every 5 years.

For each assembly, the contractor would create custom construction items that model their respective PM actions. PMs may consist of actions associated with the component type while others may be developed by the contractor based on organizational practices common to all equipment. In the annual PM assembly, the quarterly PM actions will be multiplied by (4) to provide the annualized cost.

Once developed, the construction tasks associated with EACH schedule shall be used to develop an assembly which models each schedule’s overall preventive maintenance regimen for that unit.

These two example tasks might be conceptualized as follows:

Component Type

Preventive Maintenance

Schedule Preventive Maintenance Actions

(each a custom construction item) Assembly

Air Handling Unit

Weekly actions None

Annual Preventive Maintenance for Air

Handling Unit

Monthly actions None

Quarterly actions

Check record for problems (x 4) Check controls for operation (x 4) Check for noise and vibration (x 4) Clean the coils, drain pan, and blowers (x 4) Lubricate shaft and bearings (x 4) Check belts for wear (x 4) Check & tighten connections (x 4) Check operation & clean dampers, louvers, and shutters (x 4) Lubricate pivot points and linkages (x 4) Replace filters (x 4)

Clean area around equipment (x 4) Fill out maintenance check sheet & report deficiencies (x 4)

Semi-annual actions None

Annual actions None and…

Component Preventive

Maintenance Schedule

Preventive Maintenance Actions (each a custom construction item) Assembly

Air Handling Unit Every 5 years

Deep cleaning of coils (every 5 yrs)

5-Year Preventive Maintenance for Air

Handling Unit

Inspect ductwork (every 5 years) Replace broken dampers (every 5 years) Upgrade filters (every 5 years) Calibrate thermostat (every 5 years) Check refrigerant level (every 5 years) Assess electrical connectors (every 5 years) Assess motor fan (every 5 years)

4.6 Preventive Maintenance Models for Component Spec (Type IIIb)

4.6.1 This task is identical to the requirements of para. 4.5 except that the set of assemblies is developed for a component specification rather than a component type. The task order will define which specifications to model. The idea is that the developer would merely copy and modify the existing component type assembly as the basis for the assembly and then merely add or modify construction items that make the component type specific to the specification.

4.6.2 This task will only be ordered (a) after the task for its parent component type has already been developed or (b) along with its parent component on the same task order. (There would never be an instance where a Type IIIb task is ordered before or without a corresponding Type IIIa task.) This will allow the component type model to be used as the basis for developing related component specifications.

4.6.3 This task may also be used to modify one (1) set of assemblies (either a Type III component type or Type III specification) as directed in the task order. Assembly modifications are not expected to be complete re-developments but rather adding, deleting, or adjusting construction items in the assembly which less than half of the assembly’s composition.

4.7 Material Item Re-Price (Type IV) & Assembly Update Task

4.7.1 In the course of this contract the contractor may be required to create custom construction items for tasks that do not exist in the TRACES MII Cost Book. These custom construction items may require custom-developed material costs which will require occasional material cost updates.

4.7.2 Each Type IV task includes all work to re-survey and update the material unit cost of one

(1) custom construction item within a project item assembly. The material cost to be re-surveyed will be identified on the task order and the Government will provide a file with the most current version of the project item assembly to be updated.

4.7.3 Surveying Material Costs. The contractor shall use the following process to derive the cost of a material:

a. Identify three (3) sources for the material cost. (Including a narrative justification if fewer than three sources are used). Previous sources may be re-used if they are still available.

b. Prices must be based on the retail unit cost of the specified UOM. Local sales tax shall

NOT be included.

c. Adjust the material price of each source to the Seattle, WA area using the RS Means City Cost Index (for materials) against the surveyed material supplier’s nearest available source location.

d. After adjusting the price to Seattle, WA, average the location-adjusted unit costs from the three (3) sources to derive the material unit cost to be used in the custom construction item.

e. In the notes field of the custom construction item, provide the source(s) of the material costs (company, contact, phone number, website, etc. as applicable). Enough information must be provided to allow someone else to manually perform future updates to those construction tasks in the future.

f. The deliverables shall include:

A file with all updated project item assemblies.

A spreadsheet with the updated unit cost for each material, by assembly source tag, affected custom construction item(s). It shall include the required calculations and supplementary information used for each survey.

5.0 GENERAL REQUIREMENTS COVERING ORDERED TASKS

The following requirements apply to all tasks described in para. 4.0 above (as applicable).

5.1 Process for Developing Assemblies in MII

Project item assemblies must be developed in accordance with the procedures provided in Appendix A - Section I of this performance work statement.

Note: The content found in Appendix A - Sections II and III will be the responsibility of the Government (NOT the contractor). However, the additional sections are being included for contractor awareness to show how the data will be maintained by the Government.

5.2 Order of Precedence for Cost Sources

When selecting construction tasks for developing the project item assemblies or estimates in MII, the contractor shall source costs using the following order of precedence:

(1) First, to the maximum extent practical, use the construction tasks available in the most current version of the TRACES 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 TRACES MII Cost Book, the contractor shall use a sufficiently analogous construction task that is available in the TRACES 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 TRACES MII Cost Book, the contractor shall develop custom user construction items for use in the project item assembly. This may require the development of unique labor crews, productivity rates, materials cost, and equipment items. This will require an intimate awareness of the work being modeled. 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. Material costs used in such construction items must be developed in accordance with para. 4.7.3.

5.3 Accuracy, Detail, and Scope

5.3.1 The unit costs derived from the assembly, when multiplied by the quantity of units of the repair (e.g., EA, SF, LF, etc.), shall represent the total bare of the entire project. When the Government prices the assemblies using the TRACES MII Cost Book, project markups will include Home Office Overhead (HOOH), Job Office Overhead (JOOH), and profit to account to those costs (these markups will be the same for all assemblies across all domains). The extended cost (unit cost x quantity) from each project item assembly is intended model the bare cost of one (1) complete maintenance project. Each assembly should therefore be assumed that every project is independent of any other project and should be considered “self-sufficient”.

5.3.2 Project item assemblies must be developed as accurately as possible relative to the maintenance actions being modeled. They must include all relevant direct and incidental construction tasks necessary to model a complete and independent project. The quantities of each construction item must be proportionally accurate relative to the project item assemblies being developed. Crew productivity rates may require adjustment to ensure accuracy. The maintenance actions modeled by each project item assembly must be complete, constructable, and code compliant as could be determined by an experienced and competent authority in the pertinent discipline(s) or trade(s).

5.3.3 The models will not include technician travel time to the site, installation gate delays, etc.

The models will assume that the technicians are already at the location of the maintenance requirement and have the necessary access to the facilities.

5.3.4 Incidental construction tasks. Incidental construction tasks must be accounted for in the project item assembly to the extent that they provide enhanced accuracy and cost precision for the maintenance action being modeled. Examples of incidental construction tasks can include scalable items such as selective demolition, excavation, component removal, component replacement, incidental repairs, interim dust containment, hauling, disposal, and tipping fees (as applicable). They can also include non-scalable one-time costs such as mobilization, safety precautions, de-energization, lock-out/tag-out, service isolation/disconnection and re-connection, re-energization, component operation testing, demobilization, and project clean-up (as applicable).

Whether scalable or non-scalable, these costs must be included in the unit cost of the project items assembly such that their proportion of the extended cost is relatively accurate for a typical-sized maintenance project. The logic, assumptions, and rationale used to incorporate these costs must be documented in the project item assembly in accordance with para. 5.4.

5.4 Documenting Assumptions and Rationale

5.4.1 Component or work descriptions provided by the Government may be generic or vague.

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).

5.4.2 When creating project item assemblies, any details or assumptions related to material selection, capacity selection, component location, configuration, repair methodology, work task composition, and incidental work costs must be clearly and sufficiently documented (except where obvious from the task description).

These assumptions, logic, and rationale 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.

5.4.3 For each task (as applicable), provide an electronic file (referenced by assembly or task) that includes copies of operations & maintenance instructions, user manuals, reference documentation, research and validation source documents, or explanatory narratives that were used to develop the assembly. This could include anything that could not be easily included in the Project Item Assembly notes field.

5.5 Data Rights

For data taken from closed sources or commercial sources outside of the TRACES MII Cost Book, it is the responsibility of the contractor to coordinate and obtain any necessary use rights for the Government to make full use of this contract and its products.

5.6 Creating Source Tags

For each project item assembly created, the contractor shall 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.

The contractor shall propose and use MII-compatible Source Tag suffixes to numerically differentiate assembly type for the same component.

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

5.7 Submittal Files

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

6.0 TASK ORDER PLACEMENT PROCEDURES

Solicitations for task orders issued under this IDIQ will include a list of components to be modeled (or updated) by task type in an .xlsx file. The solicitation will also include the Government’s expected period of performance (POP) for completion of all tasks on the list.

The solicitation period will involve the contractor performing a review of the requirement listing. The contractor will check specifically for: (a) whether they agree with the task type categorization being requested of each component per the choices defined in Section 4 of this PWS and; (b) sufficient clarity in the component descriptions; and (c) whether the expected period of performance of the task order is sufficient relative to the volume of work. For Type II tasks, the contractor will also check whether the component can only be repaired by replacement (Type I).

In most cases, the descriptions of the component replacement actions will be very broad and generic (requiring the contractor to make informed assumptions).

After review, the contractor may respond with:

(1) Confirmation of their agreement with items a, b, and c above;

(2) A request for additional clarification or detail on component descriptions if necessary, and/or

(3) A counterproposal which may include:

(1) suggested changes in the type categorization of tasks being requested for one or more components, or

(2) a suggested change to the period of performance

The government will review any re-categorization proposal or POP counter proposal, and negotiate with the contractor as necessary. Once agreement is reached the task order will be issued, priced according to the fully burdened task unit price schedule established for the IDIQ. The general intention is for there to be just one task order active at a time, but there may be circumstances where there is more than one with overlap in the POP. Each task order will have an appointed Contracting Officer’s Representative (COR) to provide surveillance of the contractor’s performance in accordance with the specifics of that task order’s scope.

The solicitation will include the following information for each component (according to the type of task being ordered for that component):

6.1 Type I Tasks (a & b)

a. A unique identifier number for the component

b. Uniformat II system description (level 2) for the component

c. Uniformat II component description (level 3) for the component

d. Uniformat II material category description (level 4) for the component

e. A description of the component type (or associated component type)

f. (Type Ib only) A detailed description or specification of the component (which may include size, material, configuration, etc.)

g. The unit of measure (UOM) of the component used to be used for the project item assembly.

6.2 Type II Tasks (a & b)

a. A unique identifier number for the component

b. Uniformat II system description (level 2) for the component

c. Uniformat II component description (level 3) for the component

d. Uniformat II material category description (level 4) for the component

e. A description of the component type (or associated component type)

f. (Type Ib only) A detailed description or specification of the component (which may include size, material, configuration, etc.)

g. The specific defect for which the repair should be modeled

h. The unit of measure (UOM) of the of the defect (EA, LF, SF, etc.) to be used for the project item assembly.

6.3 Type III Tasks (a & b)

a. A unique identifier number for the component

b. Uniformat II system description (level 2) for the component

c. Uniformat II component description (level 3) for the component

d. Uniformat II material category description (level 4) for the component

e. A description of the component type (or associated component type)

f. (Type Ib only) A detailed description or specification of the component (which may include size, material, configuration, etc.)

6.4 Type IV Tasks

a. A file containing the assemblies and construction items with material costs that require re-surveying.

7.0 Progress Reporting

The Contractor shall submit progress reports on a monthly basis throughout the duration of each task order’s POP. 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 POP is commensurate with the total portion of the effort reflected as complete within the corresponding progress reporting.

8.0 Quality Control Requirements

Prior to the submission of each task order deliverable, the Contractor must perform quality control in accordance with their proposed Quality Management Plan (QMP). This would include (but not be limited to):

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

b. Ensuring assemblies and estimates are 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, sources of researched material prices, etc.)

g. Ensuring the applicable elements of Appendix A - Section I - Quality Control of the Performance Work Statement 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.

9.0 Controlled Unclassified Information (CUI):

In reference to DFARS clauses 252.204-7012 & 252.240-7997 there is no Controlled Unclassified Information (CUI) or Federal Contract Information (FCI) involved in the performance of this contract.

10.0 Government Ownership of Product

Once accepted, any estimates or project item assemblies developed under this contract will become the unrestricted intellectual property of the Government.

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

11.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.

11.2 Pre-screen candidates using E-Verify Program: Contractors shall comply with the requirements set forth in FAR clause 52.222-54 Employment Eligibility Verification and RFO 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 RFO 22.1802-

1. 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.