Attachment 1 - Specifications.6.8.2020.pdf

U.S. Army Corps of Engineers Sacramento District

REPAIR BARGE PIER AND CONSTRUCT SMALL

CRAFT BERTHING FACILITY

MILITARY OCEAN TERMINAL CONCORD

(MOTCO)

CONCORD, CALIFORNIA

SPECIFICATION NO. 2187

8 June, 2020

Submitted By

2185 N. California Blvd., Suite 500 Walnut Creek, CA 94596

REPAIR BARGE PIER AND CONSTRUCT SMALL CRAFT BERTHING FACILITY 2187

MOTCO CONCORD, CALIFORNIA

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 10.00 28 DIVING

01 35 20 MEC CLEARANCE OPERATIONS

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 QUALITY CONTROL

01 45 00.15 41 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 20.00 10 ENVIRONMENTAL PROTECTION

01 57 25 TURBIDITY MONITORING

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DI VI SI ON 02 - EXI STI NG CONDI TI ONS

02 41 00 DECONSTRUCTION

DI VI SI ON 03 - CONCRETE

03 30 53 MISCELLANEOUS CAST-IN-PLACE CONCRETE

DI VI SI ON 05 - METALS

05 50 14 STRUCTURAL METAL FABRICATIONS

DI VI SI ON 06 - WOOD, PLASTI CS, AND COMPOSI TES

06 13 33 PIER TIMBERWORK

DI VI SI ON 26 - ELECTRI CAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 19.10 10 INSULATED WIRE AND CABLE

26 24 16.00 40 PANELBOARDS

DI VI SI ON 31 - EARTHWORK

31 62 13.20 PRECAST/PRESTRESSED CONCRETE PILES

31 62 19.13 TIMBER MARINE PILES

31 62 19.14 TIMBER PILE WRAP SYSTEM

DI VI SI ON 35 - WATERWAY AND MARI NE CONSTRUCTI ON

35 31 19 STONE, PROTECTION FOR STRUCTURES

35 51 13.00 20 CONCRETE FLOATING DOCKS AND ATTENUATOR

35 51 14.00 10 ALUMUINUM GANGWAY SYSTEM

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

PROJECT TABLE OF CONTENTS (Continuation Page)

ATTACHMENTS:

A. MOTCO Barge Pier Routine Inspection Report Facility Number: 00126, Military Ocean Terminal, Concord, California by KCI Technologies, Inc. Report Date: November 2016.

B. Determination of Categorical Exclusion, MOTCO – Barge Pier and Boat

Ramp Upgrade, Contra Costa County, CA, U.S. Army Corps of Engineers, Sacramento District.

C. Memorandum for Director, Defense Ammunition Center DDESB Approval of

Explosives Safety Submission (ESS), Munitions and Explosives of Concern (MEC) Removal Action, Military Ocean Terminal Concord (MOTCO), Concord, CA, located at the Former Naval Weapons Station, Concord, CA, 7 August 2013.

D. Munitions and Explosives of Concern (MEC) Support during Hazardous

Toxic, and Radioactive Waste (HTRW) and Construction Activities U.S.

Army Corps of Engineers, Engineering Pamphlet EP 75-1-2 dated 01 August 2004.

E. Final Work Plan for Munitions and Explosives of Concern Construction

Support for Concord Barge Pier Renovation, Military Ocean Terminal, Concord, CA. Contract W91238-10-D-0036, June 2014.

F. “HS20 Pier Analysis” December 18, 2013 prepared by B.C. Gerwick.

-- End of Table of Contents -

PROJECT TABLE OF CONTENTS Page 2

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 SUBMITTALS

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

1.2.2 Location

1.3 EXISTING WORK

1.4 ON-SITE PERMITS

1.4.1 Utility Outage Requests and Utility Connection Requests

1.5 LOCATION OF UNDERGROUND UTILITIES

1.5.1 Notification Prior to Excavation

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

SECTION 01 11 00 Page 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for information only. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Utility Outage Requests

Utility Connection Requests

Excavation Permits

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

This work includes the furnishing of all labor, materials, equipment, and incidental related work to complete the Barge Pier Repair and to construct the Small Craft Berthing Facility at Military Ocean Terminal Concord (MOTCO) Concord, California.

The scope of work involves:

- Removal of timber fender (at the gangway platform)

- Fabrication and installation of offshore piles

- Fabrication and installation of wave attenuator and finger dock floats

- Construction of cast-in-place concrete gangway platform on piles

- Fabrication and installation of aluminum gangway between the platform and the floating dock

- Installation of utility pedestals

- Installation of power, communications, water and sewer lines

- Replacement of timber fender piles.

- Providing protective pile wrap system.

- Providing structural pile jacket.

- Replacement of timber bracing below the pier deck.

- Replacement of timber curbing.

SECTION 01 11 00 Page 2

- Replacement of timber firewall below the pier deck.

- Repair of pile splits using metal collar.

- Repair of timber wingwall.

- Miscellaneous structural repairs.

- Discover and remove Munitions and Explosives of Concerns (MEC) from the construction footprint of the Barge Pier and Small Craft Berthing Facility and provide MEC Construction Support.

- Construct electrical and communications upgrades to the existing systems.

1.2.2 Location

The work is located at the Barge Pier, Military Ocean Military Concord (MOTCO) Concord, California, approximately as indicated.

1.3 EXISTING WORK

In addition to FAR 52.236-9 Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements:

a. Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.

b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.

1.4 ON-SITE PERMITS

1.4.1 Utility Outage Requests and Utility Connection Requests

Schedule work to minimize outages. For utility outages and connections required during the execution of work that affect existing systems, schedule outside the regular working hours or on weekends, as approved by the Contracting Officer. Schedule utility outages and connections to minimize disruptions to the Government. No additional payment will be provided for utility outages and connections required to be performed outside the regular work hours.

Submit requests for utility outages and connections in writing to the Contracting Officer for approval at least 15 calendar days in advance of the time required. In each request, state the system involved, area involved, approximate duration of outage, and the nature of work involved.

1.5 LOCATION OF UNDERGROUND UTILITIES

Obtain excavation permits from MOTCO Department of Public Works (DPW) prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities. Verify existing utility locations indicated on contract drawings, within area of work.

SECTION 01 11 00 Page 3

Verify the elevations of existing piping, utilities,and any type of obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed.

1.5.1 Notification Prior to Excavation

Notify the Contracting Officer and MOTCO DPW at least 15 days prior to starting excavation work.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 4

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.1 SPECIAL SCHEDULING REQUIREMENTS

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.1 Activity Regulations

1.2.1.1 Subcontractors and Personnel Contacts

1.2.1.2 Identification Badges and Installation Access

1.2.1.3 Employee List

1.2.1.4 No Smoking Policy

1.2.2 Working Hours

1.2.3 Work Outside Regular Hours

1.2.4 Utility Cutovers and Interruptions

1.3 SECURITY REQUIREMENTS

1.3.1 Employment Restrictions

1.3.1.1 Personnel List

1.4 OTHER REQUIREMENTS

1.4.1 Vehicle Searches

1.4.2 Photographs

1.4.3 Personnel Restrictions

1.5 WORK SUSPENSION DUE TO MISSION REQUIREMENTS

1.6 ENVIRONMENTAL RESTRICTIONS AND REQUIREMENTS

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 14 00 Page 1

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.1 SPECIAL SCHEDULING REQUIREMENTS

a. The Barge Pier will remain in operation during the entire construction period. The Contractor shall conduct his operations so as to cause the least possible interference with normal operations of the activity.

b. Permission to interrupt any Activity roads, railroads, and/or utility service shall be requested in writing a minimum of 15 calendar days prior to the desired date of interruption.

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear hard hats in designated areas. Do not enter any restricted areas unless required to do so and not until cleared for such entry. The Contractor's equipment shall be conspicuously marked for identification.

1.2.1.1 Subcontractors and Personnel Contacts

Furnish a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.2.1.2 Identification Badges and Installation Access

Application for and use of badges will be as directed.

1.2.1.3 Employee List

The Contractor shall provide to the Contracting officer, in writing, the names of employees and subcontractor's employees prior to commencement of work who will work and will require identification badges and installation access under this contract.

1.2.1.4 No Smoking Policy

No smoking except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation.

Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

SECTION 01 14 00 Page 2

1.2.2 Working Hours

Regular working hours shall consist of an 8 1/2 hour period established by the Contracting Officer Monday through Friday, and limited to daylight hours .

1.2.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress , giving the specific dates, hours, location, type of work to be performed, contract number and project title.

1.2.4 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in the paragraph "Work Outside Regular Hours."

b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.

c. Interruption to water, sanitary sewer, telephone service, electric service, fire alarm, and security service shall be considered utility cutovers pursuant to the paragraph entitled "Work Outside Regular Hours."

d. Operation of Station Utilities: The Contractor shall not operate nor disturb the setting of control devices in the station utilities system, including water, sewer, and electrical. The Government will operate the control devices as required for normal conduct of the work. The Contractor shall notify the Contracting Officer giving reasonable advance notice when such operation is required.

1.3 SECURITY REQUIREMENTS

All contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in contractor security matters or processes.

1.3.1 Employment Restrictions

MOTCO Is designated as a restricted area in accordance with Army Regulation 190-13,"The Army Physical Security Program" (AR 190-13). As required by paragraph 6-2 of AR 190-13, as well as Homeland Security Presidential Directive (HSPD)-12, Directive-Type Memorandum 09-012, and Army Execution Order (EXORD) 033-15, the MOTCO Installation Commander has

SECTION 01 14 00 Page 3 restricted MOTCO Access to U.S. citizens conducting official business at MOTCO. Consequently, any employee or invitee of the Contractor and any employee or Invitee of each subcontractor who is not a United States citizen shall be denied access to the MOTCO installation. A State issued REAL ID is required for all employees entering MOTCO.

1.3.1.1 Personnel List

Submit for approval, at least 15 days prior to the desired date of entry, an original alphabetical list of personnel who require entry into Government property to perform work on the project. Furnish for each person:

a. Name

b. Date and place of birth

c. Citizenship

d. Home address

e. Social security number

f. Naturalization or Alien Registration number

g. Passport number, place of issue, and expiration date

The request for personnel passes shall be accompanied with the following certification:

"I hereby certify that all personnel on this list are either born U.S.

citizens, naturalized U.S. citizens with the naturalization number shown."

Signature/Firm Name

1.4 OTHER REQUIREMENTS

The Contract Clause entitled "Identification of Employees" and the following apply:

1.4.1 Vehicle Searches

All contractor's vehicles including privately-owned employee's vehicles and construction vehicles will be subject to search by the Facility Security.

1.4.2 Photographs

Photographs are prohibited in and around the Facility unless a written request containing specific justification and details is approved by the security officer via the Contracting Officer. Four days' advance notice is required. Photographs, when approved, shall be taken in the presence of an activity escort.

1.4.3 Personnel Restrictions

Due to sensitivity of Facility operations, the following apply:

a. Restrict personnel to the designated work site.

SECTION 01 14 00 Page 4

b. Contractor's movements within the MOTCO will be restricted.

Contractor personnel will be escorted to and from designated work areas. Contractor personnel shall not be permitted outside of designated work areas without being escorted by authorized personnel.

1.5 WORK SUSPENSION DUE TO MISSION REQUIREMENTS

The work and contractor's activity on site may be suspended upon notice by the Contracting Officer given to the Contractor. Normally such suspensions are the result of scheduled mission requirements and the Contractor is advised to communicate with the MOTCO DPW in order to plan for such suspensions.

1.6 ENVIRONMENTAL RESTRICTIONS AND REQUIREMENTS

Refer to Specification Section 01 57 20.00 10 ENVIRONMENTAL PROTECTION for additional requirements which will affect construction schedule and work activities.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 5

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

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.3 Procurement Activities

3.3.4 Mandatory Tasks

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

3.3.12 Added and Deleted Activities

3.3.13 Original Durations

3.3.14 Leads, Lags, and Start to Finish Relationships

SECTION 01 32 01.00 10 Page 1

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.18.1 As-Built Drawings

3.3.18.2 O & M Manuals

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 Data CD/DVDs

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

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 Banding

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 Time Impact Analysis (Prospective Analysis)

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

3.8.4 Fragmentary Network (Fragnet)

3.8.5 Time Extension

3.8.6 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 RMS/QCS

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.00 10 Page 2

SECTION 01 32 01.00 10

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Periodic Schedule Update; G

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 authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. 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

SECTION 01 32 01.00 10 Page 3 specification.

2.1.1 Government Default Software

The Government intends to use Primavera P6.

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, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. 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. 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 earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

3.2.1 Activity Cost Loading

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

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the

SECTION 01 32 01.00 10 Page 4 disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer 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 Contracting Officer 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.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Procurement Activities

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

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

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

b. Long procurement activities

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

e. Submission and approval of DD1354 data and installed equipment lists.

f. Contractor's pre-final inspection.

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

h. Government's pre-final inspection.

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

SECTION 01 32 01.00 10 Page 5

j. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, acceptance, environmental permit approvals by State regulators, inspections, utility tie-in, and Notice to Proceed (NTP) 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. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil .

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*

*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 field construction or direct work activities, if directed by the Contracting Officer. 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, environmental permit

SECTION 01 32 01.00 10 Page 6 approvals by State regulators, and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: 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.

Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.

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 Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.6.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. 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 construction phase. Each activity can have only one Phase of Work code.

a. Code proposed fast track construction phases proposed to allow filtering and organizing the schedule by fast track construction 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 construction 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.

SECTION 01 32 01.00 10 Page 7

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 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 Contracting Officer 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 "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP 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."

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.

SECTION 01 32 01.00 10 Page 8

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 sSeasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse weather delay work days provided in the Special Contract Clauses. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .

3.3.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.

Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer'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 Contracting Officer.

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 Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.3.13 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work

SECTION 01 32 01.00 10 Page 9 item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

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

3.3.17 Remaining Duration

Update the remaining duration for each activity based on the number of estimated work days it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.

3.3.18 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present 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).

3.3.18.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.

3.3.18.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

SECTION 01 32 01.00 10 Page 10

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 CD/DVD, 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, then the Contractor will be deemed not to have provided an estimate upon which a progress 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 NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. 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 other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of all other specified Program approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. Include long lead item acquisition. Also cover in the initial schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed

SECTION 01 32 01.00 10 Page 11 construction activities through the dry-in milestone, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. Fully detail the remaining construction activities concurrent with the monthly schedule updating process. 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. Update the schedule to include detailed construction activities.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete 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 Data CD/DVDs

Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings.

3.5.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis.

Include the following information as minimum in the Narrative Report:

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

b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.

c. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.

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.

SECTION 01 32 01.00 10 Page 12

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.

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. 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 Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

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 Contracting Officer will use, but is not limited to, the following conditions to

SECTION 01 32 01.00 10 Page 13 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 Banding

Organize activities using the WBS or as otherwise directed to assist in the understanding of the activity sequence. 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 payment. 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 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. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer. Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work.

Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule

SECTION 01 32 01.00 10 Page 14 containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days 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 weeks. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.8 REQUESTS FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.

3.8.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.8.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer based on industry standard AACE 52R-06 . Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis.