Technical Specifications - Amendment 0002.pdf

McNary Powerhouse Turbine Draft Tube Slot Filler W912EF25BA002 MNTDTSF352071 Amend-0002

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 01.00 28

SUPPLEMENTARY REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 DEFINITIONS

1.4 REQUIRED DELIVERY DATES

1.4.1 Additional Delivery Restrictions

1.5 REGULAR CLEANUP AND DEBRIS DISPOSAL

1.6 EQUIPMENT LIST

1.7 TESTING OF EQUIPMENT

1.8 PROTECTION AND RESTORATION OF EXISTING FACILITIES

1.9 CONTRACTOR RESPONSIBILITY FOR CONTRACT WORK

1.10 PROJECT SUPERINTENDENT

1.11 KEY PERSONNEL SUBSTITUTION

1.12 POST AWARD MEETINGS

1.12.1 Post-Award/Pre-Fabrication

1.12.1.1 Pre-Fabrication

1.12.1.1.1 Minutes

1.12.2 CAD Requirements and Coordination Meeting

1.12.3 Pre-Fabrication Conference

1.12.4 Pre-Painting Meeting

1.12.5 Pre-Delivery Meetings

1.12.6 RMS Orientation Meeting

1.13 BI-WEEKLY PRODUCTION MEETINGS

1.13.1 Production Briefings

1.13.2 Fabrication Progress Photos

1.13.3 Minutes

1.14 ADDITIONAL MEETINGS

1.15 GOVERNMENT QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

PART 2 PRODUCTS (Not Used)

PART 3 EXECUTION (Not Used)

ATTACHMENTS:

Weekly Meeting Agenda three (3) week 'look ahead'

-- End of Section Table of Contents --

SECTION 01 11 01.00 28

G4EDHCMP

Line

THIS PAGE INTENTIONALLY LEFT BLANK

SECTION 01 11 01.00 28

SECTION 01 11 01.00 28

SUPPLEMENTARY REQUIREMENTS

PART 1 GENERAL

The work covered by this section of the specifications consists of work common to more than one section of these TECHNICAL SPECIFICATIONS.

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to in the text by the basic designation only.

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 Safety and Occupational Health Requirements

Comply with the current edition and all changes posted on the web as of the effective date of this solicitation.

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals having an "I" designation are for information only.

Designation following the "G" or "I" designation identifies the office that will review the submittal for the Government. Submit in accordance with SECTION 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Equipment List ; I, C

Project Superintendent ; I, C

CAD Requirements And Coordination Meeting ; G, GS

SD-07 Certificates

Key Personnel Substitution ; G, C

1.3 DEFINITIONS

a. Qualified Person.

As defined in EM 385-1-1 ; "DEFINITIONS", unless otherwise specified.

1.4 REQUIRED DELIVERY DATES

Deliver Line Items by the dates listed below. See SECTION 01 55 29.10 28 CONTRACTOR WORK, ACCESS, AND STAGING AREAS, and SECTION 05 50 14.01 28 STRUCTURAL METAL FABRICATIONS for additional delivery related information:

CLIN DESCRIPTION REQUIRED DELIVERY DATES

No later than dates listed below

0001 One North and One South Draft Tube Slot Filler

12 months after Contract Award

0002 Dogging Beams No later than delivery of

CLIN 0001

0003 One North and One South Draft Tube Slot Filler

24 months after Contract Award

0004 One North and One South Draft Tube Slot Filler

32 months after Contract Award

0005 One North and One South Draft Tube Slot Filler

32 months after Contract Award

0006 One North and One South Draft Tube Slot Filler

32 months after Contract Award

0007 One North and One South Draft Tube Slot Filler

32 months after Contract Award

1.4.1 Additional Delivery Restrictions

a. After CLIN 0001 and 0002 delivery, allow 90 calendar days prior to beginning fabrication on CLINs 0003 - 0007. See Sheet G-002, GENERAL NOTES 3 for additional information . Notify the Contracting Officer (KO) a minimum of 30 calendar days prior to beginning fabrication on CLIN 0003 Draft Tube Slot Fillers.

b. Do not schedule deliveries between 15 December and 31 March, annually, unless approved otherwise by the KO.

c. Do not deliver more than one pair of Draft Tube Slot Fillers per month. Both Slot Fillers in a given pair, must arrive onsite within 24 hours of each other, unless approved otherwise by the KO.

1.5 REGULAR CLEANUP AND DEBRIS DISPOSAL

With the exception of materials specifically indicated or specified to be salvaged for reuse, or turned over to the Government, all wastes and demolished materials becomes the property of the Contractor and must be removed from the job site daily in accordance with Federal, State, and local regulations. The Contractor shall furnish waste containers. All small waste containers provided by the contractor must be emptied daily, large bin containers must be emptied when full or once a week. Salvaged materials shall not be sold on the project site.

1.6 EQUIPMENT LIST

Furnish a complete list of all equipment to be used on the Project 30 calendar days prior to commencement of on-site work. Submit a revised list in the event of change of equipment. Lists shall include rented equipment as well as lease-purchase or sale-leaseback equipment. The initial list and the revised lists shall indicate dates equipment is assigned to or removed from the Project and adequate identification or description of each item of equipment including manufacturer's name (abbreviated), model number, manufacturer's serial number, year of manufacture, and Contractor's assigned serial or record number.

1.7 TESTING OF EQUIPMENT

Before any machinery or mechanized equipment is put to use on the job, it must be inspected and tested by a qualified person and determined to be in safe operating condition. Cranes or derricks must be tested by the Contractor or a qualified testing agency in accordance with EM 385-1-1 .

Equipment must be large enough to safely handle proposed picks or tasks without exceeding the crane rating established by these tests.

1.8 PROTECTION AND RESTORATION OF EXISTING FACILITIES

Take precautions to prevent damage to existing facilities while performing work under this contract. Upon completion of the work, all existing facilities not included as a portion of the work shall be left in a condition better than or equal to the condition existing at the time of Contractor arrival on site. Repair any damage caused by Contractor activities at no additional cost to the Government.

1.9 CONTRACTOR RESPONSIBILITY FOR CONTRACT WORK

The Contractor is responsible for correcting all damage and defects to work covered by this contract, until final acceptance by the Government.

1.10 PROJECT SUPERINTENDENT

The Contractor's Project Superintendent must be on the worksite at McNary Dam during performance of on-site work on this contract. The Project Superintendent is required on the worksite, at all times work is being performed, until work on this contract is completed and accepted. Submit Superintendent name and contact information prior to start of on-site work.

The Project Superintendent is authorized to serve as both the Contractor Quality Control (CQC) System Manager and the Site Safety and Health Officer (SSHO) providing they meet the qualifications specified for both positions.

1.11 KEY PERSONNEL SUBSTITUTION

If the Contractor plans on replacing any Key personnel (Project Superintendent, CQC System Manager, or CQC staff Members) they must have the approval of the KO. Personnel shall possess the qualifications that meet or exceed those stated in this contract for the position of the individual they are replacing. Submit qualifications of new personnel at least 15 calendar days in advance of date of replacement.

1.12 POST AWARD MEETINGS

1.12.1 Post-Award/Pre-Fabrication

A combined Post-Award/Pre-Fabrication Meeting will be held within fifteen

(15) calendar days after receipt of Notice of Award. Senior level members of the Contractor's staff and the Contractor's Project Superintendent and QC system manager shall attend the Post-Award/ Pre-Fabrication meeting.

The Government will lead the Post-Award part of the meeting and take the meeting minutes for this portion. The Government will discuss the overall contract requirements.

1.12.1.1 Pre-Fabrication

For the Pre-Fabrication part of the meeting, the Project Superintendent shall lead the meeting and discuss the Contractor's plan on executing the work, schedule, and plan for implementing quality control.

1.12.1.1.1 Minutes

Contractor is responsible for taking the meeting minutes for this portion of the meeting and shall send them electronically within 48 hours after the meeting to the Government's KO, Project Engineer, Quality Assurance Representative, and Resident Engineer. Include project name and meeting topic in e-mail subject line.

1.12.2 CAD Requirements and Coordination Meeting

a. After Notice of Award, and prior to the Contractor starting CAD files for design work on this contract , coordinate a CAD Requirements and Coordination Meeting with the Contracting Officer. All Lead CAD staff shall attend the meeting. The purpose of the meeting is to explain CAD design and submittal requirements throughout the contract, specify which version of Autodesk must be used for CAD drawing submittals, and establish Points of Contact. Provide a record of the meeting within 7 calendar days.

b. Assume Contractor use of Autodesk version 2023 for all CAD files and drawing submittals, unless approved otherwise by the Contracting Officer .

bc. The meeting may be held in conjunction with another Post Award Meeting, but must be prior to beginning CAD related work.

1.12.3 Pre-Fabrication Conference

See SECTION 05 50 14.01 28 STRUCTURAL METAL FABRICATIONS, paragraph PRE-FABRICATION CONFERENCE for additional information.

1.12.4 Pre-Painting Meeting

Coordinate with the KO and establish the date of the Pre-Painting Meeting.

The meeting shall be held at the Contractor's facility at least one (1) week prior to start of Certification Tests for paint applicators. See SECTION 09 97 02.01 28 PAINTING: HYDRAULIC STRUCTURES, paragraph "Qualified Coating Applicator" and related paragraphs for additional information. The Contractor shall lead the Pre-Painting Meeting discussing the Contractor's plan on executing the work on and off the Project site, schedule, and plan for implementing safety and quality control. Key members of the contractor staff shall attend this meeting including the Quality Control (QC) System Manager, Site Safety and Health Officer (SSHO) and any other members determined by the Government to be required.

1.12.5 Pre-Delivery Meetings

a. Coordinate with the KO and establish the dates of the Pre-Delivery Meetings. The meetings will be held at the Project site at least 21 calendar days prior to anticipated delivery date of each pair of Draft

SECTION 01 11 01.00 28

Tube Slot Fillers , unless approved otherwise by the KO. The Contractor shall lead the Pre-Delivery Meetings discussing the Contractor's plan on executing the work at the project site including delivery of Draft Tube Slot Fillers, repair of damage that occurred during shipping (including coating repair), schedule, and plan for implementing safety and quality control.

b. The Government will have key members from the Project staff to discuss environmental and clearance issues. Key members of the contractor staff shall attend these meetings including the Quality Control (QC) System Manager, Site Safety and Health Officer (SSHO) and any other members determined by the Government to be required.

1.12.6 RMS Orientation Meeting

a. Upon the Contractor's request, an RMS (Resident Management System) Orientation Meeting will be held within fifteen (15) calendar days after receipt of Notice of Award. See SECTION 01 45 01.00 28 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM) for additional information.

The Orientation Meeting will be held at NWW District Headquarters, and may occur in conjunction with, but not at the same time as, the Post-Award Meeting. The Orientation Meeting can also occur via video conference. Coordinate meeting date and time with the KO a minimum of 7 calendar days prior to the meeting.

b. At a minimum, the Contractor's RMS-CM Administrator and QC system manager shall attend the RMS Orientation meeting. A Government Representative will lead the orientation. Anticipate the following at the meeting:

1. Allow for a maximum 4 hour duration.

2. Cover the following topics, at a minimum, in RMS Contractor Mode (CM):

i. Contractor use of RMS (CM) system.

ii. Contractor Data.

iii. Quality Control Reports.

iv. Submittals.

v. RFIs.

vi. Payment.

3. Receive a follow-up handout/guide for reference on the above items.

c. Contractor employees shall bring a computer with Wi-Fi capability (to gain access to the Internet), with RMS pre-loaded.

d. The RMS Orientation Meeting is required for Contractors with no prior RMS experience. The RMS Orientation Meeting, is optional, but may be requested, for all other Contractors.

e. The purpose of the RMS Orientation Meeting is to facilitate Contractor's use of RMS (CM). It does not relieve the Contractor of the requirement to use RMS (CM) in accordance with the Contract. See

SECTION 01 45 01.00 28 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE

(RMS CM), paragraph RMS SOFTWARE for information related to required download and installation deadlines.

1.13 BI-WEEKLY PRODUCTION MEETINGS

1.13.1 Production Briefings

During all fabrication and onsite work, hold a bi-weekly production meeting to brief the Government on the status of the project.

a. Use the attached "Weekly Meeting Agenda" and discuss all elements of this agenda.

b. Provide a three (3) week 'look ahead'. Example attached. Other formats are permissible as long as information is clearly conveyed.

1. Describe all planned fabrication activities, on-site and off-site over the next three (3) weeks.

2. ENSURE these activities align to the overall Project SCHEDULE submitted under SECTION 01 32 01.00 28 PROJECT SCHEDULE.

3. RECORD any changes to the Project Schedule AND INCLUDE IN the next scheduled update.

c. Key members of the Contractor's staff including the Quality Control System Manager and the SITE SAFETY AND HEALTH OFFICER shall attend.

d. The Quality Control System Manager shall discuss all QC aspects outlined in SECTION 01 45 00.01 28 CONTRACTOR QUALITY CONTROL.

e. The Government reserves the right to require any person from the Contractor's staff such as the Project Manager, Engineer, Scheduler or Key Subcontractor Personnel to attend the meeting.

1.13.2 Fabrication Progress Photos

a. During all fabrication activities (including work onsite at McNary Dam) record fabrication progress using bi-weekly progress photographs.

Submit digital photographs bi-weekly for use at the BI-WEEKLY PRODUCTION MEETING. Photographs provided are for unrestricted use by the Government.

1. Submit photos at the end of each 2 week work period.

2. Furnish digital photographs, Utilize JPEG file format for all photograph and image files.

3. Provide full-color photos with photo resolution of not less than 4 megapixels and not more than 12 megapixels. Photos shall show the sequence and progress of work.

4. Take a minimum of 20 digital photographs each week throughout the entire project.

b. Ensure that the photographs are digitally dated. A log must be furnished for each photograph that records the following information:

1. Photograph number (the specific format should be tied to the filename of the digital photograph).

2. Date the photograph was taken.

3. A brief description of the location, what the photograph depicts, and the orientation of the view.

1.13.3 Minutes

The Contractor is responsible for taking the meeting minutes and shall send them electronically within 24 hours of the meeting to the Government's Project Engineer, Quality Assurance Representative, and Resident Engineer. Include project name and meeting topic in e-mail subject line.

1.14 ADDITIONAL MEETINGS

Record the minutes of all meetings, including all conference calls, that occur between the Contractor and Government. Send minutes electronically within 24 hours of the meeting to the KO for concurrence. E-mail subject line shall include project name and meeting topic.

1.15 GOVERNMENT QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

1. The Government will monitor the Contractor's performance under this contract using quality assurance procedures developed by the Government. Typical procedures might include random sampling, checklists, customer complaints, and observations.

2. The Government reserves the right to inspect and test all services called for by the contract, to the extent practicable at all times and places during the term of the contract. The Government will perform inspections and tests in a manner that will not unduly delay the work.

3. If any of the services do not conform to contract requirements, the Government will request the Contractor to perform the services again, where appropriate, in conformity with contract requirements, at no increase in contract amount. When the defects in services cannot be corrected by re-performance, the Government may (1) require the Contractor to take necessary action to ensure future performance conforms to contract requirements and (2) reduce the contract price to reflect the reduced value of the services performed.

4. If the Contractor fails to promptly re-perform the services or to take the necessary action to ensure future performance in conformity with contract requirements, the Government may by contract, or otherwise (1) perform the services and charge to the Contractor any cost incurred by the Government that is directly related to the performance of such service or (2) terminate the contract in whole or in part.

PART 2 PRODUCTS (Not Used)

PART 3 EXECUTION (Not Used)

-- End of Section --

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 28

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.2.1 Submittal Activity Durations

3.3.3 Procurement Activities

3.3.4 Mandatory Activities

3.3.5 Government Activities

3.3.6 Standard Activity Coding Dictionary

3.3.6.1 Workers Per Day (WRKP)

3.3.6.2 Responsible Party Coding (RESP)

3.3.6.3 Area of Work Coding (AREA)

3.3.6.4 Modification Number (MODF)

3.3.6.5 Bid Item Coding (BIDI)

3.3.6.6 Phase of Work Coding (PHAS)

3.3.6.7 Category of Work Coding (CATW)

3.3.6.8 Feature of Work Coding (FOW)

3.3.7 Contract Milestones and Constraints

3.3.7.1 Project Start Date Milestone and Constraint

3.3.7.2 End Project Finish Milestone and Constraint

3.3.7.3 Interim Completion Dates and Constraints

3.3.7.3.1 Start Phase

3.3.7.3.2 End Phase

3.3.8 Calendars

3.3.9 Open Ended Logic

3.3.10 Default Progress Data Disallowed

3.3.11 Out-of-Sequence Progress

SECTION 01 32 01.00 28

3.3.12 Added and Deleted Activities

3.3.13 Original Durations

3.3.14 Leads, Lags, and Start to Finish Relationships

3.3.15 Retained Logic

3.3.16 Percent Complete

3.3.17 Remaining Duration

3.3.18 Cost Loading of Closeout Activities

3.3.19 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Electronic Scheduling Data

3.5.2 Narrative Report

3.5.3 Schedule Reports

3.5.3.1 Activity Report

3.5.3.2 Logic Report

3.5.3.3 Total Float Report

3.5.3.4 Earnings Report by CLIN

3.5.3.5 Scheduling and Leveling Report

3.5.4 Network Diagram

3.5.4.1 Continuous Flow

3.5.4.2 Project Milestone Dates

3.5.4.3 Critical Path

3.5.4.4 Grouping and Sorting

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

3.6.2 Update Submission Following Progress Meeting

3.7 WEEKLY PROGRESS MEETINGS

3.8 REQUESTS FOR TIME EXTENSIONS

3.8.1 Justification of Delay

3.8.2 Changes That Do Not Cause Delay

3.8.3 Time Impact Analysis (Prospective Analysis)

3.8.4 Forensic Schedule Analysis (Retrospective Analysis)

3.8.5 Fragmentary Network (Fragnet)

3.8.6 Time Extension

3.8.7 Impact to Early Completion Schedule

3.9 FAILURE TO ACHIEVE PROGRESS

3.9.1 Artificially Improving Progress

3.9.2 Failure to Perform

3.9.3 Recovery Schedule

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RESIDENT MANAGEMENT SYSTEM

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

-- End of Section Table of Contents --

SECTION 01 32 01.00 28

SECTION 01 32 01.00 28

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction

AACE 84R-13 (2015) Planning and Accounting for Adverse Weather

AMERICAN SOCIETY OF CIVIL ENGINEERS (ASCE)

ASCE 67-17 (2017) Schedule Delay Analysis

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (2017) Administration -- Project Schedules

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals having an "I" designation are for information only.

Designation following the "G" or "I" designation identifies the office that will review the submittal for the Government. Submit in accordance with SECTION 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications ; G, C

Preliminary Project Schedule ; G, C

Initial Project Schedule ; G, C

Periodic Schedule Update ; G, C

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The Designated Project Scheduler must have prepared and maintained at least three previous fabrication schedules for projects of similar size and complexity to this contract, using Primavera P6.

Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.

2.1.1 Government Default Software

The Government uses Primavera P6. Ensure exported schedule files are compatible with the version of P6 used by the Government.

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the Contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of fabrication is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors, and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.

Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract progress. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN. Progress shall not be forecasted. Submit progress to the Contracting Officer (KO) for review and vetting.

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Activities with a negative cost loading is not allowed. Provide additional documentation to demonstrate reasonableness if requested by the

KO.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial, or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the KO directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the KO may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The KO will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Non-procurement activities Original Durations (OD) are not to exceed 10 workdays or 15 calendar days.

3.3.2.1 Submittal Activity Durations

Activity durations for Government review of Submittals, and return to Contractor, shall comply with SECTION 01 33 00 SUBMITTAL PROCEDURES, paragraph SCHEDULING.

3.3.3 Procurement Activities

Include in the schedule activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.4 Mandatory Activities

Include the following activities in the initial project schedule and all updates.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

b. Submission, review and acceptance of features requiring design completion.

c. Material Procurements.

d. Long procurement activities.

e. All Definable Features of Work.

f. Completion dates, constraints, and limited work windows.

g. Submission and approval of as-built shop drawings.

h. Contractor's pre-final inspection.

i. Correction of punch list from Contractor's pre-final inspection.

j. Government's pre-final inspection.

k. Correction of punch list from Government's pre-final inspection.

l. Final inspection.

3.3.5 Government Activities

Show in schedule, Government and other agency activities that could impact progress. These activities include, but are not limited to approvals, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice of Award (NOA) for phasing requirements.

3.3.6 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein.

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

SECTION 01 32 01.00 28

Field Activity Code Length Description

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.3.6.1 Workers Per Day (WRKP)

Assign Workers per Day for all fabrication or direct work activities, if directed by the KO. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.6.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice of Award (NOA) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

3.3.6.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

3.3.6.4 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by KO. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code. Base contract activities shall not have MODF codes assigned.

3.3.6.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Number (CLIN) to which the activity belongs, even when an activity is not cost loaded. Bid Item Code shall have a CLIN number, and a CLIN Title.

An activity can have only one BIDI Code.

3.3.6.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and fabrication phase. Each activity can have only one Phase of Work code.

a. Code proposed fast track design and fabrication phases proposed to allow filtering and organizing the schedule by fast track design and fabrication packages.

b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.3.6.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to fabrication submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.3.6.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 00.01 28 CONTRACTOR QUALITY CONTROL. An activity can have only one Feature of Work Code.

3.3.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the KO for approval on a case by case basis.

3.3.7.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NOA Acknowledged," which must have a "Start On" constraint date equal to the date that the NOA is acknowledged.

3.3.7.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project", which must have a "Finish on or Before" constraint in compliance with SECTION 01 11 01.00 28 SUPPLEMENTARY REQUIREMENTS, paragraph

REQUIRED DELIVERY DATES.

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.7.3 Interim Completion Dates and Constraints

Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date.

3.3.7.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.3.7.3.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.

3.3.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop Seasonal Calendar(s) and assign to seasonally affected or work restricted activities as applicable.

If a weather calendar is used its implementation and execution is to be in accordance with AACE 84R-13 .

3.3.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NOA Acknowledged" is to have no predecessor logic, and the last activity -"End Project" is to have no successor logic. Except as noted above all activities are to have at least a start-to-start or finish-to-start relationship with its predecessor(s) and a finish-to-finish or finish-to-start relationship with its successor(s).

Predecessor open ended logic may be allowed in a time impact analyses upon the KO's approval.

3.3.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.3.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the KO. Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the KO. Activity ID and description changes are considered new activities and cannot be changed without KO approval. Do not add activities representing delays or changed work until such time as the delay/change has been approved by contract modification, and in accordance with paragraph REQUESTS FOR TIME EXTENSIONS in this

SECTION.

3.3.13 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the KO.

3.3.14 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb or create float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

b. Start to Finish (SF) relationships are prohibited.

3.3.15 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.3.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management. Budgeted cost of activity is to be reduced by the amount needed to correct deficiency. The activity referenced in paragraph COST LOADING of CLOSEOUT ACTIVITIES must have its budgeted cost increased by this amount.

3.3.17 Remaining Duration

Update the remaining duration for each activity based on the number of estimated workdays it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete. The remaining duration for unstarted activities are not to be less than its original duration.

3.3.18 Cost Loading of Closeout Activities

a. Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the awarded contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

b. Cost load all Closeout Submittals specified in the contract documents, including, but not limited to those found in SECTION 01 78 00.00 28 CLOSEOUT SUBMITTALS, and SECTION 05 50 14.01 28

STRUCTURAL METAL FABRICATIONS.

3.3.19 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data reports and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, the Contractor will be deemed not to have provided an estimate upon which payment can be made.

Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents.

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NOA is acknowledged, or a minimum of 7 calendar days prior to the Post-Award Meeting (whichever comes first), submit the Preliminary Project Schedule , in both pdf and xer formats, defining the planned operations detailed for the first 90 calendar days for approval. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-fabrication activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned fabrication activities.

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after Notice of Award is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum.

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete. Updated information is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

3.5.1 Electronic Scheduling Data

Provide electronic scheduling data containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include the Narrative Report and all required Schedule Reports. The electronic file is to identify the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and schedule file name. Each schedule must have a unique file name and use project specific settings. In addition, e-mail a copy of the electronic file to the KO.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Schedule Narrative Report is a "stand alone" report in PDF or Word format. Title the report "Schedule Narrative Report". Show the Report date, schedule name, and contract number on the first page. Indicate who is responsible for the schedule update and narrative report. Provide a brief description of the Project Scope. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for problems, either current or potential, which are revealed through that analysis. Include the following information at a minimum in the Narrative Report:

a. Identify and discuss the work scheduled to start in the next update period.

b. Describe activities along the critical path in addition to activities on the next float path after the critical path.

c. Describe current and anticipated problem areas, delaying factors and their impact, and an explanation of corrective actions taken or required to be taken. Identify the party responsible for delay, if applicable.

d. Identify and explain why activities, based on their calculated late dates, should have either started or finished during the update period but did not.

e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

f. Identify and discuss out-of-sequence work.

g. If the longest path changes from a monthly update to the next, provide an explanation of the factors driving the change.

h. Respond to USACE Schedule Review Comments from the previous update(s).

3.5.3 Schedule Reports

The format, filtering, organizing, and sorting for each schedule report will be as directed by the KO. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete.

Provide the reports electronically in .pdf format. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

3.5.3.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

3.5.3.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.5.3.4 Earnings Report by CLIN

A compilation of the Total Cost Loading on the project is required at the IPS submission. Group activities by CLIN number and sort by activity number. The report must contain the following for each activity: the Activity Number, Activity Description, and Original Budgeted Amount.

3.5.3.5 Scheduling and Leveling Report

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

3.5.4 Network Diagram

The Network Diagram is required for the Preliminary, Initial and Periodic Updates. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The KO will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.4.1 Continuous Flow

Show a continuous flow from left to right with no arrows from right to left. Show the activity number, description, duration, and estimated earned value on the diagram.

3.5.4.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.5.4.3 Critical Path

Show all activities on the critical path. The critical path is defined as the longest path.

3.5.4.4 Grouping and Sorting

Group and sort activities as directed to assist in the understanding of the activity sequence. Organize activities using a Work Breakdown Structure. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress review. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The Contractor scheduler must attend in person unless virtual attendance is approved by KO. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Submit schedule file and narrative to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager must attend the meeting with the authorized KO. Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work. Following the schedule update meeting, make corrections to the schedule and resubmit, following the required schedule naming convention.

Include only those changes approved by the Government in the schedule review meeting. Only approved schedules may be used to generate invoices for payment.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 workdays after the periodic schedule update meeting.

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two…