Amendment 0006_Revised Specifications P919.pdf

P-919 BULK TANK FARM IMPROVEMENTS, PHASE 1

NAVSTA ROTA, SPAIN

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 17.00 20

COST-LOADED NETWORK ANALYSIS SCHEDULES (NAS)

05/25

PART 1 GENERAL

1.1 DEFINITIONS

1.2 NAS REQUIREMENTS PRIOR TO THE START OF WORK

1.2.1 Preliminary Scheduling Meeting

1.2.2 Baseline NAS

1.3 WEEKLY LOOK AHEAD SCHEDULE

1.3.1 Quality Control and Production Integration with NAS

1.3.2 Weekly Look Ahead Schedule Requirements

1.4 MONTHLY NETWORK ANALYSIS

1.4.1 Monthly Update Meeting

1.4.2 Monthly NAS Updates

1.4.3 As-Built NAS

1.5 CORRESPONDENCE AND TEST REPORTS

1.6 ADDITIONAL NETWORK ANALYSIS SCHEDULE REQUIREMENTS

1.7 SUBMITTALS

1.8 SOFTWARE

1.9 DESIGNATED PROJECT SCHEDULER

1.9.1 Qualifications

1.9.2 Duties

1.10 NETWORK SYSTEM FORMAT

1.10.1 NAS Activity Properties and Level of Detail

1.10.1.1 Activity Identification and Organization

1.10.1.2 Activity Logic

1.10.1.3 Longest Path Activity Baseline Limitation

1.10.1.4 Assigned Calendars

1.10.1.5 Activity Categories

1.10.1.5.1 Pre-construction Activities

1.10.1.5.2 Procurement Activities

1.10.1.5.3 Government Activities

1.10.1.5.4 Construction Quality Management (CQM) Activities

1.10.1.5.5 Construction Activities

1.10.1.5.6 Turnover and Closeout Activities

1.10.1.6 Contract Milestones and Constraints

1.10.1.6.1 Project Start Date Milestones

1.10.1.6.1.1 Post-Award Kickoff (PAK) meeting Milestone

1.10.1.6.2 Pre-Construction Meeting Milestone

1.10.1.6.3 Preconstruction Submittals Finish Milestone

1.10.1.6.4 Contractor Mobilization Finish Milestone

1.10.1.6.5 NAVFAC Red Zone - Facility Turnover Planning Meeting

Milestones

1.10.1.6.6 Substantial Completion Milestone

1.10.1.6.7 DD-1354 Finish Milestone

1.10.1.6.8 Project Completion Milestone

1.10.1.6.9 Contract Completion Date (CCD) Milestone

1.10.1.6.10 Additional Milestones

ms2226 SECTION 01 32 17.00 20 Page 1 February 02, 2026

1.10.1.7 Work Breakdown Structure & Activity Code

1.10.1.7.1 Work Breakdown Structure (WBS)

1.10.1.7.2 Responsibility Code

1.10.1.7.3 Activity Category Code

1.10.1.7.4 Additional Activity Codes

1.10.1.7.5 Drawing Code

1.10.1.7.6 Construction Specification Institute (CSI)

Masterformat Code

1.10.1.8 Adverse Weather Lost Work Days

1.10.1.9 Anticipated Restricted Delays

1.10.1.10 Cost Loading

1.10.1.10.1 Cost Loading Activities

1.10.1.10.2 Partial Payment

1.10.2 NAS Software Settings and Restrictions

1.10.3 Required Tabular Reports and Native P6 XER Files

1.11 CONTRACT MODIFICATION

1.11.1 Time Impact Analysis (TIA)

1.12 PROJECT FLOAT

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --ms2226 SECTION 01 32 17.00 20 Page 2 February 02, 2026

SECTION 01 32 17.00 20

COST-LOADED NETWORK ANALYSIS SCHEDULES (NAS)

05/25

PART 1 GENERAL

1.1 DEFINITIONS

The cost-loaded Network Analysis Schedule (NAS) is a tool to manage the project, both for Contractor and Government activities. The NAS is also used to report progress, evaluate time extensions, and provide the basis for progress payments.

For consistency, when scheduling software terminology is used in this section, the terms in Oracle Primavera's scheduling programs are used.

1.2 NAS REQUIREMENTS PRIOR TO THE START OF WORK

1.2.1 Preliminary Scheduling Meeting

Before preparation of the Baseline NAS, and prior to the start of work, meet with the Contracting Officer to discuss the proposed NAS and the requirements of this section. Propose projected data dates for monthly update NAS for the project and incorporate each monthly update submittal into the submittal register. Discuss required forms, terminology, and submittal requirements of this section and other requirements related to schedule management for this contract. Use the NAVFAC-provided Preliminary Scheduling Meeting Guideline in the completion of the intended mutual understanding.

1.2.2 Baseline NAS

Submit the Baseline NAS within 30 calendar days after contract award.

Data date must be set to contract award date and no progress recorded for any activity. Only bonds and the required Preliminary Scheduling Meeting may be recorded as complete prior to acceptance of the Baseline NAS. The acceptance of a Baseline NAS is a condition precedent to:

a. The Contractor starting demolition work or construction stage(s) of the contract.

b. Processing Contractor's invoices(s) for any items other than bonds.

c. Review of any NAS updates. The contractor is still required to submit monthly NAS updates. Without an accepted baseline NAS, the Government may return Monthly NAS update as received for record.

Submittal of the Baseline NAS is the Contractor's certification that the submitted NAS meets the requirements of the Contract Documents and represents the Contractor's plan on how the work will be accomplished.

Provide all items listed in paragraph REQUIRED TABULAR REPORTS AND NATIVE P6 XER FILES with baseline NAS submittal.

ms2226 SECTION 01 32 17.00 20 Page 3 February 02, 2026

1.3 WEEKLY LOOK AHEAD SCHEDULE

1.3.1 Quality Control and Production Integration with NAS

Submit the first Look Ahead Schedule 30 days after contract award and continue to submit weekly until contract completion.

Transmit the Weekly Look Ahead Schedule Submittal to the Contracting Officer on the first day of the current week that the Look Ahead Schedule covers and at least one working day prior to any Quality Control meetings. Contractor is required to provide all attendees at meetings with a copy of the Look Ahead Schedule. A Look Ahead Schedule is required to be submitted weekly regardless of whether a meeting is held or not.

1.3.2 Weekly Look Ahead Schedule Requirements

Prepare and issue a Three-Week Look Ahead Schedule to provide a more detailed day-to-day plan of upcoming work identified on the current Network Analysis Schedule. Requirements include:

a. For each Look Ahead Schedule activity, identify parent NAS activity number(s). The parent NAS activity is the activity in the NAS that would incorporate the Look Ahead Schedule activity requirement and scope of work.

b. Update schedule each week to show the planned work for the following three-week period. Also include previous week, as-built work, showing actual start and finish dates.

c. Include upcoming outages, closures, preparatory meetings, and initial meetings, testing and inspections.

d. Identify any offsite fabrication and production activities.

e. Clearly identify Longest Path activities on the Weekly Look Ahead Schedule. Include a key or legend that distinguishes longest path activities. Include all Longest Path activity NAS start/finish dates exceeded and occurring during this period.

f. Identify responsibility for each activity.

g. The detail work plans are to be bar chart type schedules, derived from but maintained separately from the Project NAS on an electronic spreadsheet program and printed on 299 by 432 mm sheets as directed by the Contracting Officer.

h. Activities must not exceed 5 working days in duration and have sufficient level of detail to assign crews, tools and equipment required to complete the work.

i. Look Ahead activities are not limited to only onsite work. Include submittal, offsite fabrication, and procurement activities. Include design activities, meetings, and coordination when part of scope.

j. Upload the Weekly Look Ahead Schedules to eCMS as a submittal by the date and time required.

ms2226 SECTION 01 32 17.00 20 Page 4 February 02, 2026

1.4 MONTHLY NETWORK ANALYSIS

Submittal of Monthly NAS is the Contractor's certification that the submitted NAS meets the requirements of the Contract Documents and represents the Contractor's plan on how the work will be accomplished.

Provide all items listed in paragraph REQUIRED TABULAR REPORTS AND NATIVE P6 XER FILES with the monthly NAS submittal.

1.4.1 Monthly Update Meeting

Meet with Government representative(s) at monthly intervals to review and agree on the information presented in the Monthly NAS Update. The Monthly Update Meeting must be a separate and distinct meeting from other meetings required of the contract. As a minimum, accomplish the following with each meeting held monthly:

a. Prior to the meeting, provide an agenda of proposed topics to be discussed to include but not limited to narrative report and items listed in paragraph REQUIRED TABULAR REPORTS. Document agenda and minutes with Meeting Minutes object in eCMS for each monthly update meeting.

b. The Approved Designated Project Scheduler must present the NAS data using Oracle Primavera P6 software and have baseline NAS, monthly update NAS, and Time Impact Analysis native files available to review as necessary.

c. Review Time Impact Analysis.

d. Document action items in eCMS Meeting Minutes for necessary revisions to Monthly NAS Update and to address any delays and or problem areas in a timely manner.

1.4.2 Monthly NAS Updates

a. The submission of an accepted, updated NAS to the Government is a condition precedent to the processing of the Contractor's invoice.

b. Regardless of whether an invoice is being submitted monthly, or no project progress occurred, an updated NAS (or with new data date) must be submitted monthly to the Government. The Monthly NAS update must be submitted within 5 calendar days of the data date.

c. Regardless of whether a baseline or other NAS is submitted and accepted, an updated NAS must be submitted monthly to the Government.

Monthly updates submitted before the baseline being accepted may be returned as received for record.

d. Provide all items listed in paragraph REQUIRED TABULAR REPORTS AND NATIVE P6 XER FILES, with each monthly NAS update submittal.

e. Activity progress must incorporate as-built events as they occurred and correspond to records including but not limited to submittals and daily production and quality control reports.

f. Software Settings: Handle NAS calculations through Retained Logic, not Progress Override. Out of Sequence progress is not allowed.

Relationships must be changed to reflect as-built relationships. Show all activity durations and float values in days. Show activity ms2226 SECTION 01 32 17.00 20 Page 5 February 02, 2026 progress using Remaining Duration. Set default activity type to "Task Dependent".

g. Updated NAS must reflect current Contract Completion Date and contract value in accordance with all conformed contract modifications issued prior to data date of NAS update.

1.4.3 As-Built NAS

As a condition precedent to the release of retention and making final payment, submit an "As-Built NAS," as the last NAS update showing all activities at 100 percent completion. This NAS must reflect the exact manner in which the project was actually constructed.

1.5 CORRESPONDENCE AND TEST REPORTS

Reference NAS Activity IDs that are being addressed in each correspondence (e.g., letters, Submittals, Requests for Information (RFIs), e-mails, meeting minute items, Production and QC Daily Reports, material delivery tickets, photographs) and test report (e.g., concrete, soil compaction, weld, pressure).

1.6 ADDITIONAL NETWORK ANALYSIS SCHEDULE REQUIREMENTS

Other specification sections may include additional NAS related requirements, including systems to be inspected, tested and commissioned, and submittal procedures. Those requirements must be incorporated into the NAS.

1.7 SUBMITTALS

Government approval/acceptance is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Baseline NAS ; G

Designated Project Scheduler ; G

SD-07 Certificates

Weekly Look Ahead Schedule

Monthly NAS Updates ; G

SD-11 Closeout Submittals

As-Built NAS ; G

1.8 SOFTWARE

Prepare and maintain project NAS using Oracle Primavera P6 software in a version compatible with Government's current version. Submit XER files exported as version 17 or earlier. Importing data into P6 using data conversion techniques or third party software is cause for rejection of the submitted NAS. NAS with Performing Organizational Breakdown Structure ms2226 SECTION 01 32 17.00 20 Page 6 February 02, 2026

(POBS) data in any form other than column is cause for rejection. NAS must be scheduled by using the Schedule command after last entry in Oracle Primavera P6 prior to export for submission to the Government.

1.9 DESIGNATED PROJECT SCHEDULER

Within 30 calendar days of contract award, submit to the Contracting Officer for approval an individual who will serve as the Designated Project Scheduler. Include a copy of the candidate's resume with qualifications. The Designated Project Scheduler is subject to removal by the Contracting Officer for non-compliance with the requirements specified in the Contract. Payment request will not be processed without an approved Designated Project Scheduler.

1.9.1 Qualifications

The Designated Project Scheduler must have served as a scheduler and prepared and maintained at least three previous NAS for projects, at least one within the last 5 years of similar size and complexity to this contract, using Oracle Primavera P6.

1.9.2 Duties

Duties of the Designated Project Scheduler include to be actively involved and be responsible for the following:

a. Prepare Baseline NAS.

b. Prepare monthly NAS updates.

c. Prepare tabular reports.

d. Prepare Time Impact Analysis (TIA) as necessary.

e. Provide certification of contract compliance for each NAS and TIA submittal transmitted to government for review.

f. Participate with the Prime Contractor and Government Representative in a monthly teleconference call, and scheduled with sufficient time to support the Monthly Network Analysis Updates process, to discuss project status, NAS updates, critical activities, potential delays, and contract modifications impacting any project progress. Have a computer with P6 software available during the meeting.

1.10 NETWORK SYSTEM FORMAT

Prepare the NAS in accordance with the following Primavera P6 settings and parameters. Deviation from these settings and parameters, without prior consent of the Contracting Officer, is cause for rejection of NAS submittal.

1.10.1 NAS Activity Properties and Level of Detail

1.10.1.1 Activity Identification and Organization

a. Identify construction activities planned for the project and other activities that could impact project completion if delayed in the NAS.

b. Each activity must have a unique name.

ms2226 SECTION 01 32 17.00 20 Page 7 February 02, 2026

c. Identify administrative type activity/milestones, including all pre-construction submittal and permit requirements prior to demolition or construction stage.

d. Include durations for procurement, Contractor quality control, acceptance testing and training in the NAS.

e. Include the Government approval time required for the submittals that require Government Approval prior to construction, as indicated in Section 01 33 00 SUBMITTAL PROCEDURES.

f. Create separate activities for each Phase, Area, Floor Level and Location the activity is occurring.

g. Do not use activities to represent non-work type reference (e.g., Serial Letter, Request for Information) in NAS. When RFIs need to be included in NAS, identify Non-work reference with use of added Activity codes (e.g, RFI code, Serial Letter Code). Document use of added activity codes in narrative report.

Activity categories included in the NAS are specified below.

1.10.1.2 Activity Logic

a. With the exception of the Contract Award and Contract Completion Date (CCD) milestone activities, activity must not be open-ended; each activity must have at least one predecessor and at least one successor.

b. Activities must not have open start or open finish (dangling) logic.

c. Do not use lead or lag logic without Contracting Officer prior approval. Request for approval must be submitted at the required Preliminary Scheduling Meeting for use in the Baseline NAS and at the required Monthly Network Analysis Update Meeting for use in a monthly updated NAS.

d. Minimize redundant logic ties.

e. Once an activity exists on the NAS it must not be deleted or renamed to change the scope of the activity and must not be removed from the NAS logic without approval from the Contracting Officer. Request for approval must be submitted with the required Monthly NAS Update Narrative.

f. While an activity cannot be deleted, where said activity is no longer applicable to the NAS, but must remain within the logic stream for historical record, change the activity original and remaining duration to zero and clearly label "(NO LONGER REQUIRED)" after the Activity Name.

(1) Document any such change in the activities' "Notebook," including a date and explanation for the change.

(2) The ID number for a "NO LONGER REQUIRED" activity must not be re-used for another activity.

g. No activity can be added to the NAS without the prior approval from the Contracting Officer. Request for approval must be submitted at ms2226 SECTION 01 32 17.00 20 Page 8 February 02, 2026 the required Monthly Network Analysis Update Narrative for use in a monthly updated NAS.

h. Activity Type for all activities except for milestones must be set to "Task Dependent". "Level of Effort" Activity Type is not allowed.

i. Duration Type for all activities except for milestones must be set to "Fixed Duration & Units".

j. Percent Complete Type for all activities including milestones must be set to "Physical".

1.10.1.3 Longest Path Activity Baseline Limitation

For P6 settings, critical activities are defined as being on the Longest Path. Longest Path (Critical) Activities must not make up more than 30 percent of all activity within the Construction Baseline NAS.

1.10.1.4 Assigned Calendars

All NAS activity must be assigned calendars that reflect required and anticipated non-work days.

Total work hours/day for all defined calendars is set to 8.

1.10.1.5 Activity Categories

1.10.1.5.1 Pre-construction Activities

Examples of pre-construction activities include, but are not limited to, bond approval, permits, pre-construction submittals and approvals.

Include pre-construction activities that are required to be completed prior to the Contractor starting the demolition or construction stage of work.

1.10.1.5.2 Procurement Activities

Include activities necessary to manage the ordering, fabrication, and delivery of material and equipment. Procurement activities must not have a duration in excess of 60 calendar days without prior approval by the Contracting Officer. Include within sequence of off-site assembly and fabrication any quality control and testing being performed.

Examples of procurement activities include, but are not limited to:

Material/equipment submittal preparation, submittal and approval of material/equipment; material/equipment fabrication and delivery, and material/equipment on-site. As a minimum, separate procurement activities must be provided for critical items, long lead items, items requiring Government approval and material/equipment procurement for which payment will be requested in advance of installation. Show each delivery with relationship tie to the Construction Activity specifically for the delivery.

1.10.1.5.3 Government Activities

Government and other agency activities that could impact progress must be clearly identified. Government activities include, but are not limited to; Government approved submittal reviews, Government conducted inspections/tests, environmental permit approvals by State regulators, ms2226 SECTION 01 32 17.00 20 Page 9 February 02, 2026 utility outages, and delivery of Government Furnished Material/Equipment.

1.10.1.5.4 Construction Quality Management (CQM) Activities

The Preparatory and Initial Phase meetings for each Definable Feature of Work identified in the Contractor's Quality Control Plan must be included in the Weekly Look Ahead Schedules. Preparatory and Initial phase meetings are not required in the NAS, but can be represented by a start milestone linked to successor parent Construction Activity. The Follow-up Phase must be represented by the Construction Activities themselves in the

NAS.

1.10.1.5.5 Construction Activities

On-site construction activities that are the responsibility of the Contractor or Contractor's subcontractors must not have a duration in excess of 20 working days without prior approval by the Contracting Officer. Contractor activities must be driven by calendars that reflect Saturdays, Sundays and all Federal Holidays as non-work days, unless otherwise defined in this contract. Federal Holidays are as defined in Federal Law 5 USC 6103.

1.10.1.5.6 Turnover and Closeout Activities

Include activities or milestones for items on the NAVFAC Red Zone Checklist/POAM that are applicable to this project. As a minimum, include required Contractor testing, required Government acceptance inspections on equipment, Pre-Final Inspection, Punch List Completion, Final Inspection and Acceptance. Add an unconstrained start milestone for the initial NAVFAC Red Zone - Facility Turnover Planning Meeting at approximately 75 percent construction contract completion or six months prior to Contract Completion Date (CCD), whichever is sooner. Include a separate NAVFAC Red Zone - Facility Turnover Planning Meeting Milestone for each phase if the contract requires construction to be completed in phases.

1.10.1.6 Contract Milestones and Constraints

1.10.1.6.1 Project Start Date Milestones

Include as the first activity on the NAS a start milestone titled, "Contract Award", which must have a Mandatory Start constraint equal to the Contract Award Date.

1.10.1.6.1.1 Post-Award Kickoff (PAK) meeting Milestone

Include an unconstrained finish milestone on the NAS titled, "Post-Award Kickoff Meeting". The Post Award Kickoff Meeting may be a single day, or it may range over several days. The intent is to cover all PAK topics, including Partnering and Concept Design Workshop (if required) in one continuous session.

1.10.1.6.2 Pre-Construction Meeting Milestone

Include an unconstrained finish milestone on the NAS titled, "Pre-Construction Meeting". The Pre-Construction meeting may be a single day, or it may range over several days. The intent to cover all the Pre-Con topics, including Partnering and DD1354.

ms2226 SECTION 01 32 17.00 20 Page 10 February 02, 2026

1.10.1.6.3 Preconstruction Submittals Finish Milestone

Include an unconstrained finish milestone on the NAS titled, "Preconstruction Submittals". This milestone is complete when all required preconstruction submittals have been reviewed and approved by the Government.

1.10.1.6.4 Contractor Mobilization Finish Milestone

Include an unconstrained finish milestone on the NAS titled, "Contractor Mobilization".

1.10.1.6.5 NAVFAC Red Zone - Facility Turnover Planning Meeting Milestones

See paragraph TURNOVER AND CLOSEOUT ACTIVITIES above.

1.10.1.6.6 Substantial Completion Milestone

Include an unconstrained finish milestone on the NAS titled "Substantial Completion." Substantial Completion is defined as the point in time the Government would consider the project ready for beneficial occupancy wherein by mutual agreement of the Government and Contractor, Government use of the facility is allowed while construction access continues in order to complete remaining items (e.g., punch list and other close out submittals). Include a separate Substantial Completion Milestone for each phase if the contract requires construction to be completed in phases.

1.10.1.6.7 DD-1354 Finish Milestone

Add unconstrained finish milestone, titled "DD-1354" and scheduled 30 calendar days prior to Substantial Completion, whenever a Form DD-1354 is required in accordance with Section 01 20 00 PRICE AND PAYMENT PROCEDURES. Include a separate DD-1354 Finish Milestone for each phase if the contract requires construction to be completed in phases.

1.10.1.6.8 Project Completion Milestone

Include an unconstrained finish milestone on the NAS titled "Project Completion." Project Completion is defined as the point in time all contract requirements are complete and verified by the Government with a successful Final Inspection in accordance with Section 01 45 00 QUALITY CONTROL. This milestone must have the Contract Completion Date (CCD) milestone as its only successor.

1.10.1.6.9 Contract Completion Date (CCD) Milestone

Last NAS entry must be an unconstrained finish milestone titled "Contract Completion (CCD: DD-MM-YY)." DD-MM-YYYY is the current contract completion date at data date, day-month-year corresponding to P6 Must Finish By Date. NAS milestone updates of Project Completion finish date for longest path must reflect calculated float as positive or negative based on CCD. Calculation of NAS updates must be such that if the finish of the "Project Completion" milestone falls after the contract completion date, then negative float is calculated on the longest path. If the finish of the "Project Completion" milestone falls before the contract completion date, the float calculation must reflect positive float on the longest path.

ms2226 SECTION 01 32 17.00 20 Page 11 February 02, 2026

1.10.1.6.10 Additional Milestones

Provide up to five additional milestones as required by Contracting Officer.

1.10.1.7 Work Breakdown Structure & Activity Code

At a minimum, establish a Work Breakdown Structure (WBS) and provide activity codes identified as follows:

1.10.1.7.1 Work Breakdown Structure (WBS)

Group all activities and milestones within appropriate WBS elements/levels including, at a minimum, the following:

a. Project Milestones:

(1) Management Milestones

(2) Project Administrative Meetings

(3) Permits

b. Pre-Construction Phase:

(1) Submittals and Reviews

(2) Procurement

(3) Mobilization

c. Construction Phase: Create multiple elements/levels in accordance with project specific definable features of work including in WBS descending order as follows:

(1) General Area

(a) Type of Work Item

1. Location

d. Project Closeout: Include activity items such as, but not limited to, Punchlist, Demobilization, O&M, As-built Drawings, Training, and As-built NAS.

e. Modifications: Create Conformed and Non-Conformed elements/levels under Modification WBS. Create multiple elements/levels as the project progresses identified by issue and Fragnet placed in Conformed for modifications issued prior data date, or Non-Conformed for issues not modified to contract prior data date.

f. Removed Activity: Activity is "removed" by remaining within logic sequence, eliminating duration and adding "(NO LONGER REQUIRED)" after Activity Name in Activity Table.

g. Commissioning & Testing:

(1) Specific area/locations of commissioning ms2226 SECTION 01 32 17.00 20 Page 12 February 02, 2026

(2) Final Testing

(3) Training

1.10.1.7.2 Responsibility Code

Use "RESP" for Activity Code Name. All activities in the project NAS must be identified with the resource, including business name, for completing the task. Activities must not belong to more than one responsible party.

1.10.1.7.3 Activity Category Code

Use "CAT" for Activity Code Name for the following Project Level activity codes:

a. Assign "PROC" value to Procurement type activity

b. Assign "PRE-CON" value to Pre-construction activity

c. Assign "CONS" value to Construction type activity

d. Assign "TEST" value to dedicated testing type activities

e. Assign "CX" value to dedicated Commissioning type activities

f. Assign "CLOS" value to dedicated Close Out type activity

g. Assign "OTHR" to other activity not otherwise designated

1.10.1.7.4 Additional Activity Codes

Provide up to an additional five activity codes as required by the Contracting Officer

1.10.1.7.5 Drawing Code

Identify all activities in the project NAS with its respective Drawing Code. The Drawing Code is the Sheet Number on the primary project drawing which indicates work to be performed. If an activity does not have an applicable Drawing Code (e.g., Mobilize), the code must be "0000".

1.10.1.7.6 Construction Specification Institute (CSI) Masterformat Code

Identify all activities in the project NAS with its respective Specification Section number. Activities must not belong to more than one Section number. If an activity does not have an applicable CSI Code (e.g., Mobilize), the code must be "0000".

1.10.1.8 Adverse Weather Lost Work Days

Use the National Oceanic and Atmospheric Administration's (NOAA) Summary of Monthly Normals report to obtain the historical average number of days each month with precipitation, using a nominal 30-year, greater than 2.5 mm precipitation amount parameter, as indicated on the Station Report for the NOAA location closest to the project site as the basis for establishing a "Weather Calendar" showing the number of anticipated non-workdays for each month due to adverse weather, in addition to Saturdays, Sundays and all Federal Holidays as non-work days.

ms2226 SECTION 01 32 17.00 20 Page 13 February 02, 2026

Use the following schedule of anticipated monthly non-work days due to adverse weather as the basis for establishing a "Weather Calendar" showing the number of anticipated non-workdays for each month due to adverse weather, in addition to Saturdays, Sundays and all Federal Holidays as non-work days.

MONTHLY ANTICIPATED ADVERSE WEATHER LOST WORK DAY

JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC

4 5 5 6 3 1 0 0 1 6 4 5

Assign the Weather Calendar to any activity that could be impacted by adverse weather. The Contracting Officer will issue a modification in accordance with the contract clauses, giving the Contractor a time only extension for the difference of days between the anticipated and actual adverse weather delay if the number of actual adverse weather delay days exceeds the number of days anticipated for the month in which the delay occurs and the adverse weather delayed activities are on the longest path to contract completion in the period when delay occurred. A lost workday due to weather conditions is defined as a day in which the Contractor cannot work at least 50 percent of the day on the impacted activity.

Impacts resulting from adverse weather must be documented in Narrative Report for the month that it occurred.

Make changes to P6 project calendars to reflect as-built conditions where work occurred where originally anticipated as non-work days, and where work did not occur (lost work day).

1.10.1.9 Anticipated Restricted Delays

Use anticipated non-working days as defined in Section 01 14 00 WORK RESTRICTIONS, use Anticipated Restricted Delays as basis for establishing a "Security Calendar" showing the number of anticipated non-workdays for each month due to anticipated restrictions, in addition to anticipated adverse weather, Saturdays, Sundays and all Federal Holidays as non-work days. Assign the Security Calendar to any activity that could be impacted by restriction delays. The Contracting Officer will issue a modification in accordance with the contract clauses, giving the Contractor a time extension for the difference of days between the anticipated and actual lost work days if the number of actual restriction delay days exceeds the number of anticipated for the month in which the delay occurs and the restriction delayed activities are critical to contract completion. A lost workday due to restriction delay is defined as a day in which the Contractor cannot work at least 50 percent of the day on the impacted activity.

Impacts resulting from restriction delays must be documented in Narrative Report for the month that it occurred.

Make changes to P6 project calendars to reflect as-built conditions where work occurred where originally anticipated as non-work days, and where work did not occur (lost work day).

1.10.1.10 Cost Loading

The Project Network Analysis Schedule (NAS) must be cost-loaded and will provide the basis for progress payments. Earned Value Reports must be ms2226 SECTION 01 32 17.00 20 Page 14 February 02, 2026 derived from and correspond to cost loaded NAS. Use the Critical Path Method (CPM) and the Precedence Diagram Method (PDM) to satisfy time and cost applications.

Sum of all costs assigned to activities must equal the current contract value as of the data date of the baseline or update NAS. Activity cost loading must be without front-end loading. Provide additional documentation if requested by the Contracting Officer.

1.10.1.10.1 Cost Loading Activities

a. Cost load construction activities. Define construction activities as on-site work activities that can be traced directly to the construction, alteration, demolition, repair of a project facility, infrastructure, or sitework.

b. Assign costs for materials which payment will be requested in advance of installation, including their quantities, to their respective procurement activities that were approved by the Contracting Officer.

Assign labor costs, including their quantities, for material and equipment paid for after installation to their respective construction activities.

c. Costs for mobilization will not be paid as individual pay items with the exception of batch plant set-up, mobilization of dredging equipment or other similar labor-intensive situations. If payment for mobilization costs are approved, assign costs for demobilization activities. The value of demobilization activities must not be less than 40 percent of the total costs for mobilization activities. If not approved as a separate line item, evenly disperse over construction activities the costs for mobilization and demobilization.

d. The value of commissioning, testing, and closeout WBS section may not be less than 10 percent of the total costs for procurement and construction activities.

e. ALL activities assigned Government responsibility will have Zero Cost. No contractor cost should be assigned to an activity designated as a Government responsibility.

f. Do not include field overhead positions as individual cost loaded activities. Evenly disperse non-construction costs (e.g., meetings, presentations, submittals, surveys, haul road or storage yard maintenance, dust control, security) and profit to construction activities assigned to the Construction Phase WBS level.

g. If assigning resources to activities, setting for Calculate costs from units in Resources tab must be unchecked.

1.10.1.10.2 Partial Payment

Breakdown unit of measure and cost must be defined within P6 Activity Detail Expenses for partial payment of any cost loaded activity. Lump sum cost loaded activity will not be partially paid.

1.10.2 NAS Software Settings and Restrictions

a. Activity Constraints: Date/time constraint(s), other than those required by the contract, are not allowed unless accepted by the ms2226 SECTION 01 32 17.00 20 Page 15 February 02, 2026

Contracting Officer. Identify any constraints proposed and provide an explanation for the purpose of the constraint in the Narrative Report as described in paragraph REQUIRED TABULAR REPORTS.

b. Default Progress Data Disallowed: Actual Start is date work begins on activity with intent to pursue work to substantial completion. Actual Finish is date work is substantially complete to point where successor activity can begin. Actual dates on the NAS must correspond with activity dates reported on the Contractor Quality Control and Production Reports.

c. At a minimum, include the following settings and parameters in P6 NAS preparation:

(1) General: Define or establish Calendars and Activity Codes at the "Project" level, not the "Global" level.

(2) Admin Drop-Down Menu, Admin Preferences, Time Periods Tab:

(a) Set time periods for P6 to 8.0 Hours/Day, 40.0 Hours/Week,

172.0 Hours/Month and 2000.0 Hours/Year.

(b) Use assigned calendar to specify the number of work hours for each time period: Must be checked.

(3) Admin Drop-Down Menu, Admin Preferences, Earned Value Tab:

(a) Technique for computing performance percent complete: Use "Activity percent Complete"

(b) Technique for computing Estimate to Complete: Use "PF = 1".

(c) Earned Value Calculation: Use "Budgeted values with current dates".

(4) Project Level, Dates Tab:

(a) Set "Must Finish By" date to "Contract Completion Date", and set "Must Finish By" time to 05:00pm.

(5) Project Level, Defaults Tab:

(a) Duration Type: Set to "Fixed Duration & Units".

(b) Percent Complete Type: Set to "Physical".

(c) Activity Type: Set to "Task Dependent".

(d) Calendar: Set to "Standard 5 Day Workweek". Calendar must reflect Saturday, Sunday and all Federal holidays as non-work days. Alternative calendars may be used with Contracting Officer approval.

(6) Project Level, Calculations Tab:

(a) Default Price/Unit for activities without resource or role Price/Units: Set to "$1/h".

(b) Activity percent complete based on activity steps: Must be ms2226 SECTION 01 32 17.00 20 Page 16 February 02, 2026

Checked.

(c) Link Budget and At Completion for not started activities:

Must be Checked.

(d) Reset Remaining Duration and Units to Original: Must be Selected.

(e) Subtract Actual from At Completion: Must be Selected.

(f) Recalculate Actual units and Cost when duration percent complete changes: Must be Checked.

(g) Update units when costs change on resource assignments:

Must be Unchecked.

(h) Link Actual to Date and Actual This Period Units and Cost:

Must be Checked.

(7) Project Level, Settings Tab:

(a) Define Critical Activities: Check "Longest Path".

(8) Work Breakdown Structure Level, Earned Value Tab:

(a) Technique for Computing Performance Percent Complete:

"Activity percent complete" is selected.

(b) Technique for Computing Estimate to Complete (ETC): "PF = 1" is selected.

1.10.3 Required Tabular Reports and Native P6 XER Files

Include the following reports with the Baseline, Monthly Update and any other required NAS submittals:

a. Time Scaled Logic NAS

Provide formatted 11 by 17-inch Time-scaled Logic NAS in color and landscape-oriented with each NAS submittal. Clearly show activities on the longest path setting Gantt chart longest path activity bars to red. Group activities by WBS and sort by finish date in ascending order. Include the following information in column form for each activity and include accompanying Gantt chart:

(1) Activity ID

(2) Activity Name

(3) Original Duration

(4) Remaining duration

(5) Physical Percent Complete

(6) Start Date

(7) Finish Date ms2226 SECTION 01 32 17.00 20 Page 17 February 02, 2026

(8) Total Float

(9) Project-level Calendar

b. Previous Monthly Update Comparison Time Scaled Logic NAS (Submit with all Monthly NAS Update Submittals.)

Provide formatted 11 by 17-inch Time-scaled Logic NAS in color and landscape-oriented with each monthly NAS update submittal. Clearly show activities on the current month longest path setting Gantt chart longest path activities bars to red. Show previous month activities as yellow bars and previous month milestones in yellow within Gantt chart. Sort by finish date in ascending order. Filter activities for longest path. Maintain and assign the accepted previous monthly NAS update or the accepted baseline NAS for the first update submittal as the baseline and primary baseline in P6 before printing the NAS.

Include the following information in column form for each activity and include accompanying Gantt chart:

(1) Activity ID

(2) Activity Name

(3) Original Duration

(4) Current Month Remaining Duration

(5) Current Month Start Date

(6) Previous Month Update Start Date (BL Project Start)

(7) Start Date Delta between Current Month and Previous Month (Variance - BL Project Start Date)

(8) Current Month Finish Date

(9) Previous Month Finish Date (BL Project Finish)

(10) Finish Date Delta between Current Month and Previous Month (Variance - BL Project Start Date)

(11) Current Month Total Float

c. P6 native XER file: Include the back-up native .xer program file compatible with the current Government version of Primavera P6. Each native NAS file must have a unique file name to include project name and data date using (yyyy-mm-dd) convention. Each native NAS must have a unique Project ID and Project Name.

d. Log Report: P6 Scheduling/Leveling Report.

e. Narrative Report: Identify and justify:

Each entry in the Narrative Report must cite the respective Activity ID and Activity Name, the date and reason for any changes, and description of the change.

(1) Provide Project Summary Data in format below:

ms2226 SECTION 01 32 17.00 20 Page 18 February 02, 2026

(a) Data Date ______

(b) Award Date: _______

(c) Original Project Duration: _____ days post Award Date

(d) Current Project Duration: ______ days post Award Date

(e) Time percent elapsed: ______ percent at data date

(f) Original CCD: _______

(g) Current CCD: _______ (thru MOD _______)

(h) Anticipated CCD: _____ (___ calendar days early/late)

(i) Original Contract Value: $____________

(j) Current Contract Value: $_________

(k) Invoiced Amount: $_________ (____ percent)

(l) Cost Growth: ____ percent

(m) NAS Growth: ____ percent

(n) There are a total of ______ activities, ______ activities complete (____ percent), ____ activities in progress (____ percent), _____ activities not started (____ percent). Of the in progress and not started activities; ____ (____ percent) are on the longest path. The longest path has duration of _____ calendar days from data-date to anticipated project completion.

(2) Progress made in each area of the project;

(3) Longest Path;

(4) Date/time constraint(s), other than those required by the contract

(5) Listing of all changes made between the previous monthly NAS update and current monthly NAS update include as a minimum:

added or deleted activities, original and remaining durations for activities that have not started, logic (sequence constraint lag/lead), milestones, planned sequence of operations, longest path, calendars or calendar assignments, and cost loading.

Identify any other changes that relate to calculations within Oracle Primavera P6;

(6) Any decrease in previously reported activity Earned Amount;

(7) Pending items and status thereof, including permits, changes orders, and time extensions;

(8) Status of Contract Completion Date and interim milestones;

(9) Status of Projected Completion Milestone and account of difference in calendar days between previous update Projected ms2226 SECTION 01 32 17.00 20 Page 19 February 02, 2026

Completion Milestone

(10) Current and anticipated delays listing Activity Names and IDs for impacted activities(describe cause of delay and corrective actions(s) and mitigation measures to minimize);

(11) Description of current and potential future NAS problem areas.

(12) Identification of any weather and restricted lost time as compared to anticipated weather for the month and anticipated restricted days for which the update is submitted. Impacts resulting from adverse weather must be documented in tabular form showing the calendar month (or billing period) with the days on which construction activity incurred Lost Work Days due to adverse weather. In narrative form, describe the adverse weather cause such as precipitation measurement, temperature, wind or other influencing factors, and why work was impacted. Identify the construction activity(s) by ID and Name that was (were) scheduled, impacted.

f. Earned Value Report: Derive from and correspond to P6 cost loaded Monthly NAS Update. List all activities having a budget amount cost loaded. Compile total earnings on the project from notice to proceed to current progress payment request. Show on the report for each activity:

(1) Current budget;

(2) Previous Physical Percent Complete;

(3) To-Date Physical Percent Complete;

(4) Previous Earned Value;

(5) To-Date Earned Value;

(6) Cost This Period;

(7) Cost to Complete.

g. Schedule Variance Control (SVC) Diagram: With each NAS submission, provide a SVC diagram representing only the current file showing 1) A Cash Flow Curve indicating planned project cost based on each of projected early and projected late activity finish dates and 2) one curve for Earned Value to-date. Revise Cash Flow Curves when the contract is modified, or as directed by the Contracting Officer Include a legend on report clearly indication 3 curves: early finish, late finish, and earned-value to date.

Use the following settings in Activity Usage Profile Options:

(1) In the Data section, under Display, the radio box for Cost must be selected.

(2) In the Data section, under Filter for Bars/Graphs, the checkbox for Total must be checked.

(3) In the Show Bars/Curves section:

ms2226 SECTION 01 32 17.00 20 Page 20 February 02, 2026

(a) Under the By Date column, the checkboxes for Baseline, Actual and Remaining Late must be checked. The checkboxes for Budgeted and Remaining Early must be unchecked.

(b) Under the Cumulative column, the checkboxes for Baseline, Actual and Remaining Late must be checked. The checkboxes for Budgeted and Remaining Early must be unchecked.

(c) Set the color for Baseline to green.

(d) Set the color for Actual to blue.

(e) Set the color for Remaining Late to red.

(4) In the Show Earned Value Curves section, the checkboxes for Planned Value Cost, Earned Value Cost and Estimate at Completion must be unchecked.

h. Logic Diagram showing timescale from data date to 60 days after data date with filter for longest path. Leave Group By selection blank and sort by finish date in ascending order.

i. Logic Diagram showing timescale from data date to contract completion date with filter for longest path. Leave Group By selection blank and sort by finish date in ascending order.

j. Baseline or Monthly Update Checklist as applicable completed and certified by Qualified Scheduler. Contractor Baseline Project Schedule Review, Contractor Monthly Update Schedule Review, and Contractor Baseline Project Schedule, and General Commissioning/HVAC Review Checklist. Checklists can be found on the Whole Building Design Guide website as Related Materials to UFGS 01 32 17.00 20.

k. Screen shot PDF of Primavera P6 Time Periods Settings referenced in paragraph NAS SOFTWARE SETTINGS AND RESTRICTIONS, list item c.(2):

ADMIN DROP-DOWN MENU, ADMIN PREFERENCES, TIME PERIODS TAB

l. Screen shot PDF of Primavera P6 Earned Value Settings referenced in paragraph NAS SOFTWARE SETTINGS AND RESTRICTIONS, list item c.(3):

ADMIN DROP-DOWN MENU, ADMIN PREFERENCES, EARNED VALUE TAB

m. Daily Reported Production Activity: Submit on a monthly basis, in electronic spreadsheet, summary of daily reported production activity for the reporting month in the update NAS. Use the following columns for reporting:

(1) Date

(2) Activity ID

(3) Work Description

(4) Contractor

(5) Billable Hours ms2226 SECTION 01 32 17.00 20 Page 21 February 02, 2026

1.11 CONTRACT MODIFICATION

1.11.1 Time Impact Analysis (TIA)

Submit a Time Impact Analysis with each cost and time proposal for a proposed change. TIA must illustrate the influence of each change or delay on the Contract Completion Date or milestones. No time extensions will be granted nor delay damages paid unless a delay occurs which consumes all available Project Float, impacts the longest path, and extends the Projected Completion beyond the Contract Completion Date.

a. Each TIA must be in both narrative and NAS form. The narrative must:

(1) Define the scope and conditions of the change;

(2) Provide start and finish dates of impact to longest path;

(3) Identify and include any accepted NAS referenced in TIA and any changes made to accepted NAS to prepare additional NAS included in the TIA;

(4) Successor(s) and predecessor(s) activities to impact period;

(5) Responsible party;

(6) Describe how the impact originated;

b. The TIA submission must consist of at least three native XER files:

(1) Fragnet used to define the scope of the changed condition

(2) Most recent accepted baseline NAS or monthly NAS update as of the time of the impact start date. If the data date of this NAS is different than the start date of impact, update this NAS to show all activity progress as of the time of the impact start. The impact start date is identified as the time when an existing activity is impeded for either starting or finishing. This NAS must have a data date that is the same as the identified start date of impact in "a.(2)". Identify any changes made to most recent accepted NAS.

(3) The impacted NAS that has the Fragnet inserted in the updated NAS from "b.(2)" and the NAS scheduled using the Schedule command in Oracle Primavera P6 so that the new completion date is determined.

c. For claimed as-built project delay, the inserted Fragnet TIA method must be modified to account for as-built events known to occur after the data date of NAS update used. Updated NAS for periods following the impact start date will be used and included in submittal to evaluate how the project progressed (as-built) through the finish of impact. Impact to longest path must be determined for each following update period.

d. All TIAs must include any mitigation, and must determine the apportionment of the overall delay assignable to each individual delay. Apportionment must provide identification of delay type and classification of delay by compensable and non-compensable events.

The associated narrative must clearly describe analysis methodology used, and the findings in a chronological listing beginning with the ms2226 SECTION 01 32 17.00 20 Page 22 February 02, 2026 earliest delay event.

(1) Identify and classify types of delay defined as follows:

(a) Force majeure delay (e.g., weather delay): Any delay event caused by something or someone other than the Government or the Contractor, or the risk of which has not been assigned solely to the Government or the Contractor. If the force majeure delay is on the longest path, in absence of other types of concurrent delays, the Contractor is granted an extension of contract time, classified as a non-compensable event.

(b) A Contractor-delay: Any delay event caused by the Contractor, or the risk of which has been assigned solely to the Contractor. If the contractor-delay is on the longest path, in absence of other types of concurrent delays, Contractor is not granted extension of contract time, and classified as a non-compensable event. Where absent other types of delays, and having impact to project completion, Contractor must provide to Contracting Officer a Corrective Action Plan identifying plan to mitigate delay.

(c) A Government-delay: Any delay event caused by the Government, or the risk of which has been assigned solely to the Government.