Attachment C - 01_32_17.00_20.pdf

USACE / NAVFAC / AFCEC UFGS-01 32 17.00 20 (May 2025)

Preparing Activity: NAVFAC Superseding UFGS-01 32 17.00 20 (November 2023)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

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.2.3 Baseline NAS

1.2.3.1 Baseline NAS

1.2.3.2 Post-Award Kickoff (PAK) Meeting and Baseline NAS

1.2.3.3 Construction 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 Design Activities

1.10.1.5.2 Pre-construction Activities

1.10.1.5.3 Procurement Activities

1.10.1.5.4 Government Activities

1.10.1.5.5 Construction Quality Management (CQM) Activities

SECTION 01 32 17.00 20 Page 1

1.10.1.5.6 Construction Activities

1.10.1.5.7 Turnover and Closeout Activities

1.10.1.5.8 Testing of HVAC - DALT, TAB, and PVT Activities

1.10.1.5.9 Commissioning Activities

1.10.1.6 Contract Milestones and Constraints

1.10.1.6.1 Project Start Date Milestones

1.10.1.6.1.1 Design Phase Completion Milestone

1.10.1.6.1.2 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

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

SECTION 01 32 17.00 20 Page 2

USACE / NAVFAC / AFCEC UFGS-01 32 17.00 20 (May 2025)

Preparing Activity: NAVFAC Superseding UFGS-01 32 17.00 20 (November 2023)

UNIFIED FACILITIES GUIDE SPECIFICATIONS

SECTION 01 32 17.00 20

COST-LOADED NETWORK ANALYSIS SCHEDULES (NAS)

05/25

NOTE: This guide specification applies to Design-Bid-Build and Design-Build projects and covers the preparation and use of Cost-Loaded Network Analysis Schedules (NAS) for construction using Primavera P6.

Confirm with the Administering FEAD/ROICC/OICC that the project schedule should be prepared under the requirements of this section. Provide the proposed NAS Specification for the review and acceptance by the PDC5 Construction Schedule Analyst. Further, this section must be reviewed and approved by the administering FEAD/ROICC/OICC/PDC5 Construction Schedule Analyst prior to completion of the Request for Proposal (RFP). Selected bracketed options [_____] included in this section must be approved by the Administering FEAD/ROICC/OICC.

Coordination is required with Section 01 20 00 PRICE AND PAYMENT PROCEDURES with selection of "Earned Value Report" rather than "Schedule of Prices" in that section.

Adhere to UFS 1-300-02 Unified Facilities Guide Specifications (UFGS) Format Standard when editing this guide specification or preparing new project specification sections. Edit this guide specification for project specific requirements by adding, deleting, or revising text. For bracketed items, choose applicable item(s) or insert appropriate information.

Comments, suggestions and recommended changes for this guide specification are welcome and should be submitted as a Criteria Change Request (CCR) .

NOTE: This section contains tailoring for Design-Build (DB), Design-Bid-Build (DBB), TABS, and Commissioning (CX). Use TABS tailoring when Section

SECTION 01 32 17.00 20 Page 3

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

and Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC are included in the contract specifications.

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

NOTE: This paragraph is tailored for

DESIGN-BID-BUILD.

In the first sentence, select the default of "30" calendar days as the standard. If warranted, the amount of calendar days for projects requiring more time may be tailored based on project size and technical complexity.

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.

SECTION 01 32 17.00 20 Page 4

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.

1.2.3 Baseline NAS

NOTE: This paragraph is tailored for DESIGN-BUILD.

1.2.3.1 Baseline NAS

Submit the Baseline NAS at the Post-Award Kickoff (PAK) Meeting or within 30 calendar days after contract award whichever occurs first. The Baseline NAS must include detailed design activities and a general approach to construction, including summary activities for required phasing and definable areas. Summary Construction activities must not exceed duration of 60 calendar days, unless approved otherwise by Contracting Officer. 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 submitting the first design submittal.

b. Processing Contractor's invoices(s)other than that for the bonds.

1.2.3.2 Post-Award Kickoff (PAK) Meeting and Baseline NAS

Present the Baseline NAS at the PAK Meeting. Be prepared to discuss the NAS logic emphasizing how the NAS satisfies the design package requirements and incorporates the required government review periods for each design submittal.

1.2.3.3 Construction Baseline NAS

Submit the detailed Construction Baseline NAS prior to the pre-final design submittal. The pre-final design submittal will not be reviewed until a Construction Baseline NAS is submitted.

The acceptance of the Construction 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 for demolition or construction activities.

c. Review of any construction phase NAS updates.

Submittal of the Construction Baseline NAS must be 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

SECTION 01 32 17.00 20 Page 5

TABULAR REPORTS AND NATIVE P6 XER FILES with baseline NAS submittal.

1.3 WEEKLY LOOK AHEAD SCHEDULE

1.3.1 Quality Control and Production Integration with NAS

NOTE: Refer to Section 01 45 00 .

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

NOTE: Select the default of "Three-Week" for the number of future weeks to be displayed in the Weekly Look Ahead Schedules. If the Administering FEAD/ROICC/OICC agree, the option "Four-Week" can be selected.

Prepare and issue a [Four-Week][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][or] scope of work.

b. Update schedule each week to show the planned work for the following[ three-week][ four-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][or] 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 11 by 17 inch sheets as directed by the Contracting Officer.

SECTION 01 32 17.00 20 Page 6

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. For design-build: Identify any design production and quality control activities, meetings, and charrettes.

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

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

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][or]

SECTION 01 32 17.00 20 Page 7 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 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

NOTE: Review Submittal Description (SD) definitions in Section 01 33 00 SUBMITTAL PROCEDURES and edit the following list, and corresponding submittal items in the text, to reflect only the submittals required for the project. The Guide Specification technical editors have classified those items that require Government approval, due to their complexity or criticality, with a "G." Generally, other submittal items can be reviewed by the Contractor's Quality Control System. Only add a "G" to an item if the submittal is sufficiently important or complex in context of the project.

SECTION 01 32 17.00 20 Page 8

For Army projects, fill in the empty brackets following the "G" classification, with a code of up to three characters to indicate the approving authority. Codes for Army projects using the Resident Management System (RMS) are: "AE" for Architect-Engineer; "DO" for District Office (Engineering Division or other organization in the District Office); "AO" for Area Office; "RO" for Resident Office; and "PO" for Project Office. Codes following the "G" typically are not used for Navy and Air Force projects.

The "S" classification indicates submittals required as proof of compliance for sustainability Guiding Principles Validation or Third Party Certification and as described in Section 01 33 00 SUBMITTAL

PROCEDURES.

NOTE: For Design-Build projects, delete Section 01 33 00 SUBMITTAL PROCEDURES and replace with UFGS 01 33 00.05 20 CONSTRUCTION SUBMITTAL PROCEDURES and

UFGS 01 33 10.05 20 DESIGN SUBMITTAL PROCEDURES.

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. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Baseline NAS ; G, [_____]

Construction 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

SECTION 01 32 17.00 20 Page 9 the submitted NAS. NAS with Performing Organizational Breakdown Structure (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

NOTE: Select one of two options concerning the meeting between the Designated Scheduler, Prime Contractor, and Government Representative. Select the first option for most projects. Only select the second option if specifically requested by the FEAD/ROICC/OICC Office.

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,][meeting at the job site in-person,] 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.

NOTE: Retain the following list item where justified by project size [and][or] complexity.

SECTION 01 32 17.00 20 Page 10

[ g. Be present on the project site full-time during working hours.

] 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

NOTE: Item a. contains tailoring for DESIGN-BUILD projects, and item e. contains tailoring for sections used in DESIGN-BID-BUILD and DESIGN-BUILD.

a. Identify design and 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.

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 Section 01 33 10.05 20 DESIGN

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

SECTION 01 32 17.00 20 Page 11

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

NOTE: Retain 20 percent threshold baseline in the bracketed item for most projects. However, for horizontal construction, and the more linear a project, (for example, sidewalk, roadway, fence) this threshold may be increased accordingly to as much as 80 percent, depending on the type of project. Consult with FEC scheduler if additional guidance is needed.

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.

SECTION 01 32 17.00 20 Page 12

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

1.10.1.5 Activity Categories

1.10.1.5.1 Design Activities

NOTE: This paragraph is tailored for DESIGN-BUILD projects.

Design activities must include design decision points and design submittal packages, including critical path submittals for Fast Tracked Phases.

Review times for design development packages must be included in the NAS.

Refer to Section 01 33 10.05 20 DESIGN SUBMITTAL PROCEDURES, for specific requirements.

1.10.1.5.2 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.3 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.4 Government Activities

NOTE: The paragraph below includes DESIGN-BUILD tailoring for Design and Construction Start 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, utility outages, Design Start, Construction Start (including Design/Construction Start for each Fast-Track Phase, and delivery of Government Furnished Material/Equipment.

SECTION 01 32 17.00 20 Page 13

1.10.1.5.5 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.6 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.7 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.5.8 Testing of HVAC - DALT, TAB, and PVT Activities

NOTE: Use this paragraph when Section 23 05 93 TESTING, ADJUSTING AND BALANCING FOR HVAC and Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC are included in the contract specifications;

otherwise, delete. This paragraph is tailored for

TABS.

Include in the baseline NAS, activities and milestones associated with Government acceptance of Duct Air Leakage Test (DALT), Testing, Adjusting, and Balancing (TAB) and Performance Verification Test (PVT) as required and in accordance with Section 23 05 93 TESTING, ADJUSTING AND BALANCING FOR HVAC and Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC.

a. Identify the general area or location(s) for Government Acceptance Testing of DALT, TAB and PVT.

b. Incorporate into the baseline NAS, time periods required for advance notification of work, and Government submittal review in accordance with Section 23 05 93 TESTING, ADJUSTING AND BALANCING FOR HVAC, paragraph DALT AND TAB SUBMITTAL AND WORK SCHEDULE.

SECTION 01 32 17.00 20 Page 14

c. Include the following as NAS activities or milestones:

(1) Pre-DALT/TAB/PVT Meeting

(2) TAB Design Review Report, Government review

(3) TAB Pre-Field Engineering Report, Government review

(4) DALT Field Work

(5) DALT Field Acceptance Testing

(6) Certified Final DALT Report, Government review

(7) Control Contractors PVT Plan, Government review

(8) Equipment Suppliers PVT Plan, Government review

(9) Endurance Testing, Government review

(10) PVT Field Work

(11) PVT Report, Government review

NOTE: Insert the following when Season I or II work is included in the Contract.

DM will coordinate with NAVFAC Contracting to ensure that the overall Period of Performance outlined in the RFP aligns with the overall Contract Completion Date (CCD) which includes the durations for Season I, Season II [and][or] Post-Occupancy activities required for Testing, Adjusting, and Balancing for HVAC systems.

Further coordination is required with NAVFAC Contracting to ensure that Liquidated Damage (LD) amounts are identified for both the Substantial Completion Milestone as well as the overall Contract Completion Date (CCD).

d. Include in the baseline schedule, the following cost-loaded activities. These activities will be successors to the Substantial Completion Milestone and predecessors to the Project Completion Milestone as defined in paragraph PROJECT COMPLETION MILESTONE.

(1) Season I TAB Field Work

(2) Season I Certified Final TAB Report, Government review

(3) Season I TAB Field Acceptance Testing

(4) Season II TAB Field Work

(5) Season II Certified Final TAB Report, Government review

(6) Season II TAB Field Acceptance Testing

SECTION 01 32 17.00 20 Page 15

NOTE: Insert the following when required by, and coordinate the post-occupancy endurance testing and post occupancy PVT Field Work with, Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

[ (7) Post-Occupancy Endurance Testing Government review

(8) Post-Occupancy PVT Field Work

] 1.10.1.5.9 Commissioning Activities

NOTE: This paragraph is tailored for Commissioning (CX). Use this paragraph if Section 01 91 00.15 BUILDING COMMISSIONING is included in the contract specifications.

Include in the baseline NAS activities and milestones associated with Commissioning.

a. Identify the general area or location(s) of systems for Commissioning Inspection and Testing

b. Incorporate into the baseline NAS time periods for Government submittal review

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 Design Phase Completion Milestone

NOTE: This paragraph is tailored for DESIGN-BUILD projects.

Include an unconstrained finish milestone on the NAS titled, "Design Phase Completion". Design Phase Completion is defined as the point in time when all design requirements are complete and approved. Duration for Government review and approval must be included as predecessor activities to Design Phase Completion.

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

SECTION 01 32 17.00 20 Page 16

1.10.1.6.2 Pre-Construction Meeting Milestone

NOTE: This paragraph is tailored for DESIGN-BID-BUILD projects.

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.

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

SECTION 01 32 17.00 20 Page 17

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.

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:

NOTE: The following items a.(4) and a.(5) are tailored for DESIGN-BUILD Contracts.

a. Project Milestones:

(1) Management Milestones

(2) Project Administrative Meetings

(3) Permits

(4) Design Phase

(5) Design Submittals and Reviews Milestones

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

SECTION 01 32 17.00 20 Page 18

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.

NOTE: The following item g. is tailored for Commissioning (CX). Use if Section 01 91 00.15 BUILDING COMMISSIONING is included in the contract specifications.

g. Commissioning & Testing:

(1) Specific area/locations of commissioning

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

NOTE: The following item h. is tailored for DESIGN-BUILD Contracts.

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

SECTION 01 32 17.00 20 Page 19

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

h. Assign "DSGN" value to Design type activity

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

NOTE: Retain either or both of the following two paragraphs where justified by project complexity.

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

NOTE: Check with the FEC's Scheduling Subject Matter Expert or with the FEAD/ROICC/OICC for known site-specific Adverse Weather Delays to determine how to edit this paragraph. If historical data is not available, choose the first paragraph using NOAA historical monthly averages as the basis for establishing non-workdays. Note that NOAA historical data may not be available for all OCONUS locations.

If the historical adverse weather data is available, use the second paragraph and table and populate the table with the known data. Insert the data for each month in the blank, bracketed item provided. A bracketed choice of 2 days per month is provided only as an option to remind the Designer to insert the actual data.

[ 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

0.10 inch 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.

SECTION 01 32 17.00 20 Page 20

][ 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

[2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_] [2][_]

] 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

NOTE: Use this paragraph if base access restrictions are anticipated during the project timeframe; otherwise, delete. Revise number of days and period of time as appropriate for project specific requirements. Verify with FEAD/ROICC/OICC before this is incorporated to ensure this is applicable to project site.

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

SECTION 01 32 17.00 20 Page 21

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

NOTE: Choose 10 percent in the brackets below, unless FEC or FEAD/ROICC/OICC scheduler directs otherwise.

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][or] 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, SECTION 01 32 17.00 20 Page 22 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 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:

SECTION 01 32 17.00 20 Page 23

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