Specifications.pdf

INVITATION FOR BID (IFB)

PL 84-99 LEVEE REHABILITATION REPAIRS

CY 2007 ORDERS 3-4 SITES

RECLAMATION DISTRICT 150

Yolo County, California

IFB NO.

SPECIFICATION NO. RD150

US Army Corps of Engineers Sacramento District

DISTRIBUTION STATEMENT A

Approved for public release; distribution is unlimited

ATTENTION TO OFFERORS:

1. SECURITY REQUIREMENTS

YOUR ATTENTION IS DIRECTED TO THE SECURITY REQUIREMENTS FOR THIS

CONTRACT LOCATED IN SECTION 00800, SPECIAL CONTRACT REQUIREMENTS.

2. FACTS ABOUT THE USE OF INDIVIDUAL SURETIES

The Federal Acquisition Regulation (FAR) permits the use of individual sureties for bid, payment and performance bonds. However, the conditions that must be met are strict, and they may not be waived. Further, the FAR imposes limits with respect to the type of property interest individual sureties may utilize.

Individual sureties have been occasionally and successfully used in accordance with FAR requirements within the Sacramento District, when real property interests have not been provided as the security interest. On at least one occasion, an individual surety was made acceptable when an individual personally known to a bidder provided a business property for the security interest, and legal counsel was engaged to navigate and implement the FAR requirements.

Bidders or proposers considering utilizing individuals or firms providing “brokerage” or “insurance” services to obtain bonds from individual sureties are advised to carefully research their backgrounds. The Government is not responsible for and will not reimburse any bidder for advance payments made to such firms in the event that the bonds are unacceptable to the contracting officer.

The Sacramento District strictly follows the FAR 28.203 “Acceptability of individual sureties.” Frequently, an individual surety’s bid bond raises questions about the real property security interest being offered. Also, individual sureties may use “altered” Standard Form 28 affidavits, which are unacceptable. Documentation containing such flaws will result in rejection of the bonds, and, if it is a bid bond, rejection of the bid.

Some “brokers” apparently represent that “their bonds” are accepted by federal government entities. Yet, be aware that not all federal agencies implement the FAR in a uniform manner. Insufficiencies that go unnoticed by one agency may be perceived as fatal by another. The risk of such results rests with the bidder offering the bid bond.

Know your broker, and ensure that all bonding documents comply with FAR requirements before you submit them. It is important to remember that the contracting officer is vested with a wide degree of discretion and business judgment in determining the acceptability of an individual surety, and the Comptroller General has stated that he will not question such a determination so long as it is reasonable.

So, please make certain that if you intend to use an individual surety you are familiar with the regulations and specific requirements that apply to this form of bonding.

PL 84-99 Levee Rehabilitation Repairs for RD150 RD150

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 GENERAL REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 01 CONTRACTOR QUALITY CONTROL

01 45 01.10 QUALITY CONTROL SYSTEM (QCS)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES

01 57 20 ENVIRONMENTAL PROTECTION

01 57 23 TEMPORARY STORM WATER POLLUTION CONTROL

01 71 13 MOBILIZATION AND DEMOBILIZATION

01 78 00 CLOSEOUT SUBMITTALS

DIVISION 31 - EARTHWORK

31 23 19 DEWATERING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 92 19.26 EROSION CONTROL SEEDING

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 31 19 STONE PROTECTION

35 41 00 LEVEE CONSTRUCTION FOR EMERGENCY REPAIR

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 11 00

GENERAL REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 GENERAL

1.3.1 The Contractor's Superintendent

1.3.2 Job Hazard Analysis

1.3.3 Violations

1.3.4 Fire Prevention

1.3.5 Recordkeeping/Reporting Requirements

1.3.6 Accident Reporting

1.4 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER

1.5 EQUIPMENT DATA FORM

1.6 BID ITEM OVERRUN

1.7 NON CONTRACT WORK

1.8 DAMAGE TO ROADS

1.9 SPECIAL SURVEY PROCEDURES

1.9.1 Survey Services

1.9.2 Survey Supervision and Scheduling

1.10 SPECIAL CONSTRUCTION CONDITIONS

1.10.1 Commencement, Prosecution And Completion Of Work

1.10.1.1 Complete construction by October 31, 2009

1.10.1.2 August 1 , 2010 – September 30, 2010

1.10.2 Stream Flow Conditions

1.10.3 River Gaging Stations

1.10.4 Project Security and Public Safety

1.10.5 Special Encroachment Requirements

1.11 PAYMENT

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

01 11 00 - 1

SECTION 01 11 00

GENERAL REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

The current issues of the publications listed below, but referenced to hereafter by basic designation only, form a part of this specification to the extent indicated by the references thereto:

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2008) Safety and Health Requirements Manual

ER 415-1-15 (1989) Construction Time Extensions for Weather

U.S. ARMY CORPS OF ENGINEERS, SACRAMENTO DISTRICT (CESPK)

DM 4-805-10 (1991) Survey Manual

U.S. NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

29 CFR 1904.5 Determination of work-relatedness

29 CFR 1910 Occupational Safety and Health Standards

29 CFR 1926 Safety and Health Regulations for Construction

1.2 SUBMITTALS

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

submittals not having a designation are for information only. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Job Hazard Analysis; G

Written summary identifying hazards of each aspect of construction and proposed methods and techniques of accomplishing each aspect in a safe manner.

1.3 GENERAL

EM 385-1-1, 29 CFR 1926, as revised from time to time, 29 CFR 1910, as revised from time to time, and the National Fire Protection Association Codes are applicable to this contract. In case of conflict the most stringent requirement of the standards is applicable.

01 11 00 - 2

1.3.1 The Contractor's Superintendent

The Contractor's superintendent shall take an active role in enforcing the safety requirements by participation in safety conferences, hazard analysis (see below), tool box meetings, walk-through inspections, correction of violations, etc., and including that of the subcontractor's work.

1.3.2 Job Hazard Analysis

Based on the construction schedule, the Contractor shall submit to the Contracting Officer a Job Hazard Analysis of each aspect of construction prior to the start of construction. The analysis shall include major or high risk hazards, as well as commonly recurring deficiencies that might possibly be encountered, and shall identify proposed methods and techniques of accomplishing each aspect in a safe manner. The Contractor's superintendent shall take active participation in the Job Hazard Analysis, including the subcontractors' work. Prior to the start of actual work, a meeting shall be held with the Contractor, the Contracting Officer, and affected subcontractors to review the Job Hazard Analysis. In addition, job site meetings shall be held to indoctrinate the foreman and workers on details of this analysis.

1.3.3 Violations

If recurring violations and/or a gross violation indicate that the safety performance is unsatisfactory, corrective action shall be taken as directed, and at the discretion of the Contracting Officer the retention or some part thereof will be withheld from the progress payment until corrective action has been completed.

1.3.4 Fire Prevention

Cutting or welding will be permitted only in areas that are or have been made fire safe. Where possible, all combustibles shall be located at least 40 feet horizontally from the work site. Where such location is impracticable, combustibles shall be protected with fire blankets and/or protective welding screens to prevent slag from running out of the work area. Other fire prevention precautions shall be in accordance with the latest National Fire Codes.

1.3.5 Recordkeeping/Reporting Requirements

On all contract operations, the Contractor shall be responsible for recording and reporting all accident exposure and experience incident work (this includes exposure and experience of the Contractor and his subcontractors). As a minimum these records shall include exposure work-hours and a log of occupational injuries and illnesses. (OSHA Form 200 or state equivalent as prescribed by 29 CFR 1904.5) Reference

EM 385-1-1.

1.3.6 Accident Reporting

In addition to the requirements for reporting accidents in accordance with EM 385-1-1, Section 1, the Contractor shall submit to the Contracting Officer at the 100% of project completion, a written summary report of worker's compensation claims filed by workers on the project. The report shall include all subcontractors. The report shall be certified as "correct and true" by the Contractor's and the subcontractors' compensation insurance carrier. The same certification will be required for

01 11 00 - 3 subcontractor reports.

1.4 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER

This provision specifies the procedure for the determination of time extensions for unusually severe weather. In order for the Contracting Officer to award a time extension under this clause, the following conditions must be satisfied:

The weather experienced at the project site during the contract period must be found to be unusually severe, that is, more severe than the adverse weather anticipated for the project location during any given month.

The unusually severe weather must actually cause a delay to the completion of the project. The delay must be beyond the control and without the fault or negligence of the Contractor.

The following schedule of monthly anticipated adverse weather delays is based on National Oceanic and Atmospheric Administration (NOAA) or similar data for the project location and will constitute the base line for monthly weather time evaluations. The Contractor's progress schedule must reflect these anticipated adverse weather delays in all weather dependent activities.

Monthly Anticipated Adverse Weather Delay Work Days Based On Five Day Work Week

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

7 6 5 4 1 0 0 0 1 2 5 7

Upon acknowledgment of the Notice to Proceed (NTP) and continuing throughout the contract, the Contractor will record on the daily CQC report, the occurrence of adverse weather and resultant impact to normally scheduled work. Actual adverse weather delay days must prevent work on critical activities for 50 percent or more of the Contractor's scheduled work day.(ER 415-1-15)

Flow conditions in the Sacramento River will not be considered as adverse or unusually severe weather and no time extension to the contract will be granted to the Contractor for this circumstance.

1.5 EQUIPMENT DATA FORM

The Contractor shall furnish SPK Form 450 for all necessary equipment to perform work requiring adjustment of contract price and shall submit these forms with the modification proposals.

1.6 BID ITEM OVERRUN

Throughout the contract, (at a minimum, every 5 calendar days) the Contractor shall be responsible to monitor placement or installation of unit price items with respect to the original estimated quantities shown in the contract. If placement or installation indicates a possible overrun with respect to the original estimated quantities shown in the contract, the Contractor shall immediately provide, within one day, written notification to the Contracting Officer with revised total estimated quantities.

01 11 00 - 4

1.7 NON CONTRACT WORK

The Contractor and/or his subcontractors shall not perform any work or erect any structure for third parties, landowners or otherwise, within the limits of the rights-of-way without prior approval of the Contracting Officer.

1.8 DAMAGE TO ROADS

The Contractor shall preserve and protect all public, private, and project access or right-of-way roads. At the completion of work or a Contracting Officer's discretion and prior to the Contractor leaving the project, he shall restore to pre-project conditions all such roads. Repairs shall include replacement of base rock and/or surface treatment as required to meet pre-project conditions. Refer also to paragraph "PROTECTION AND MAINTENANCE OF TRAFFIC" in section 01 50 00, "TEMPORARY CONSTRUCTION

FACILITIES".

1.9 SPECIAL SURVEY PROCEDURES

1.9.1 Survey Services

All survey services shall be performed in accordance with DM 4-805-10, copies of which are available in the office of the Contracting Officer.

1.9.2 Survey Supervision and Scheduling

All survey services shall be performed by or under the direct supervision of a person licensed to practice surveying in the State of California.

Field notes shall be kept in accordance with DM 4-805-10. The accuracy of the survey shall be third order or better.

1.10 SPECIAL CONSTRUCTION CONDITIONS

1.10.1 Commencement, Prosecution And Completion Of Work

1.10.1.1 Complete construction by October 31, 2009

6 Order 2 Sites: 2005130-006-010; 20051230-006-013; 20051230-006-014;

20051230-006-015; 20051230-006-018; 20051230-006-019. Work can be done through the weekends as needed to fulfill the schedule of this first work window.

1.10.1.2 August 1 , 2010 – September 30, 2010

11 Order 3-5 Sites: 20051230-006-002; 20051230-006-003; 20051230-006-004;

20051230-006-005; 20051230-006-006; 20051230-006-007; 20051230-006-008;

20051230-006-011; 20051230-006-012; 20051230-006-016; 20051230-006-017

1.10.2 Stream Flow Conditions

The Contractor shall be aware and prepared to address rapidly changing site conditions based on forecast weather conditions and the subsequent affects to the water level in the river, stream, bypass, or slough adjacent to the project site. In addition to the requirements established in paragraph 1.4, the Contractor shall not park equipment in any area that may be inundated by increased flows. Furthermore, the Contractor shall be capable of completing a repair site within 24 hours if directed by the Contracting officer as a result of flood or severe weather conditions.

01 11 00 - 5

1.10.3 River Gaging Stations

Water surface elevation data is available for the stream gages operated by the Department of Water Resources. Data can be obtained from the Internet at the web site operated by the California Department of Water Resources, California Data Exchange Center (CDEC). River forecasts available on the CDEC Website. The Internet address is:

http://cdec.water.ca.gov or:

http://cdec.water.ca.gov/queryGroup.html

The Government does not guarantee the reliability or accuracy of the hydrographs and will assume no responsibility for any deductions, conclusions, or interpretations that may be made from them. The Contractor shall undertake any such studies that are deemed necessary to assess the reliability and accuracy of the information presented in the hydrographs.

1.10.4 Project Security and Public Safety

The contractor shall require all visitors to abide by all construction site safety requirements. The construction contractor shall notify the Corps Contracting Officer 48 hours before the commencement of any physical activities on the site.

1.10.5 Special Encroachment Requirements

Provide a ten foot buffer with temporary orange construction fencing with metal t-posts around all identified encroachments. Comply with the special encroachment requirements listed here:

PL84-99 Repair Sites; Summary of observed encroachments

Site Encroachment Coordinates

Impacts Repair

Notes

5 38.34480 121.55751

Yes

10A 38.37582 121.52525

Yes Pipe cut off/capped approx 4' from WS levee slope.

10B 38.37820 121.52547

Yes Abandoned.

12 38.38110 121.52415

Yes

13 Yes Abandoned metal stairs/debris.

14 38.39966 121.51486

Yes Stairs at DS limit of repair site; stairs undermined and unstable.

15 38.40599 121.51736

Yes Abandoned.

18 Yes

01 11 00 - 6

PL84-99 Repair Sites; Summary of observed encroachments

Site Encroachment Coordinates

Impacts Repair

Notes

Note: Inspect the project sites and verify the extent of damage. Additional encroachments may be found during construction that are not noted here.

1.11 PAYMENT

No separate payment will be made for the work covered under this section and all costs in connection therewith will be considered a subsidiary obligation of the Contractor.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

01 11 00 - 7

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 CONTRACTOR SCHEDULING REPRESENTATIVE QUALIFICATIONS

PART 2 PRODUCTS

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.1.1 Approved Poject Schedule

3.1.2 Schedule Status Reports

3.1.3 Default Terms

3.2 BASIS FOR PAYMENT AND COST LOADING

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Critical Path Method

3.3.2 Level of Detail Required

3.3.2.1 Activity Durations

3.3.2.2 Procurement Activities

3.3.2.3 Mandatory Tasks

3.3.2.4 Government Activities

3.3.2.5 Contracts with multiple buildings/facilities

3.3.2.6 Activity Responsibility Coding (RESP)

3.3.2.7 Activity Work Area Coding

3.3.2.8 Contract Changes/Requests for Equitable Adjustment (REA)

Coding (MODF)

3.3.2.9 Contract Line Item (CLIN) Coding (BIDI)

3.3.2.10 Phase of Work Coding (PHAS)

3.3.2.11 Category of Work Coding (CATW)

3.3.2.12 Definable Features of Work Coding (FOW1, FOW2, FOW3)

3.3.3 Scheduled Project Completion and Activity Calendars

3.3.3.1 Project Start Date

3.3.3.2 Schedule Constraints and Open Ended Logic

3.3.3.3 Early Project Completion

3.3.4 Interim Completion Dates

3.3.4.1 Start Phase

3.3.4.2 End Phase

3.3.4.3 Phase "X" Hammock

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

3.3.7 Negative Lags and Start to Finish Relationships

3.3.8 Calculation Mode

3.3.9 Milestones

3.4 PROJECT SCHEDULE SUBMISSIONS

01 32 01 - 1

3.4.1 Preliminary NAS Project Schedule Submission

3.4.2 Initial NAS Project Schedule Submission

3.4.3 Design Package Schedule Submission

3.4.4 Periodic Schedule Updates

3.4.5 Standard Activity Coding Dictionary

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CDs

3.5.2 Narrative Report

3.5.3 Approved Changes Verification

3.5.4 Schedule Reports

3.5.4.1 Activity Report

3.5.4.2 Logic Report

3.5.4.3 Total Float Report

3.5.4.4 Earnings Report by CLIN

3.5.5 Network Diagram

3.5.5.1 Continuous Flow

3.5.5.2 Project Milestone Dates

3.5.5.3 Critical Path

3.5.5.4 Banding

3.5.5.5 S-Curves

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

3.6.1 Update Submission Following Progress Meeting

3.6.2 Status of Activities

3.6.2.1 Start and Finish Dates

3.6.2.2 Remaining Duration

3.6.2.3 Percent Complete

3.6.2.4 Logic Changes

3.6.2.5 Other Changes

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.7.2 Submission Requirements

3.7.3 Additional Submission Requirements

3.8 DIRECTED CHANGES

3.9 WEEKLY PROGRESS MEETINGS

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

01 32 01 - 2

SECTION 01 32 01

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.

U.S. ARMY CORPS OF ENGINEERS (USACE)

ECB 2005-10 (2005) Scheduling Requirements for Testing of Mechanical Systems in Construction

ER 1-1-11 (1995) 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. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Schedule; G bar chart schedule Schedule Status Report Preliminary NAS Project Schedule Initial NAS Project Schedule Design Package Schedule Periodic Schedule Updates Data CDs Justification of Delay Proposed Schedule Revisions

1.3 CONTRACTOR SCHEDULING REPRESENTATIVE QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation and submittal of the entire Network Analysis Systems (NAS) project schedule including all items specified below and revisions to the schedule or supplemental completion schedules, and all required updating (activity status) and preparation of reports, as applicable or directed by the Contracting Officer. The authorized scheduling representative shall be approved by the Contracting Officer based on a resume indicating as a minimum, formal training from software vendor or 5 years experience in working with NAS schedules.

01 32 01 - 3

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the design and construction sequences, is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development.

Subcontractors and suppliers working on the project shall also contribute in developing and maintaining an accurate Project Schedule. The schedule must be a forward planning as well as a project monitoring tool.

3.1.1 Approved Poject Schedule

Use the approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions. Make the schedule cost loaded and activity coded. The schedule will provide the basis for all progress payments. If the Contractor fails to submit any schedule within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

3.1.2 Schedule Status Reports

Provide a Schedule Status Report on at least a monthly basis. The Government will use the NAS Project Schedule to evaluate the contractor's progress for timely completion, plan for Quality Assurance verification of the work and evaluate the effects of a proposed modification on the contract duration (critical path activities). If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor shall take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.3 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting Officer shall be grounds for a determination by the Contracting Officer that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract.

Upon making this determination, the Contracting Officer may terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.

3.2 BASIS FOR PAYMENT AND COST LOADING

Use the schedule as the basis for determining contract earnings during each

01 32 01 - 4 update period and therefore the amount of each progress payment. Lack of an approved schedule update or qualified scheduling personnel will result in an inability of the Contracting Officer to evaluate contract earned value for the purposes of payment. Failure of the Contractor to provide all required information will result in the disapproval of the preliminary, initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on the Schedule.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the NAS Project Schedule shall be capable of meeting all requirements of this specification. Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule. Scheduling software that meets the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 are Primavera Project Planner (P3) by Primavera, and Open Plan by Deltek. The Contractor shall provide to the Government a complete input listing for the selected software. Manual methods used to produce any required information shall require prior approval by the Contracting Officer. The Contracting Officer intends to use P3.

Should the contractor utilize software that is different than that utilized by the Contracting Officer, based on the software utilized by the contractor for the preparation of the NAS schedule, the contractor shall provide a copy of the software and a license to the Administrative Contracting Officer at the Government field office until final payment.

The software and license shall be returned to the contractor. The Contractor shall submit a copy of the user's manual outlining the selected CPM computer program's mathematical analysis capabilities, details, functions and operation.

3.3.1 Critical Path Method

Use the Critical Path Method (CPM) of network calculation to generate the Project Schedule. Prepare the Project Schedule using the Precedence Diagram Method (PDM).

3.3.2 Level of Detail Required

Develop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer, 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.1 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 shall have Original Durations (OD) greater than 20 work days or 30 calendar days. Durations shall be in workdays. Procurement activities are defined herein.

01 32 01 - 5

3.3.2.2 Procurement Activities

The schedule must include activities associated with the submittal, approval, 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. A typical procurement sequence includes the string of activities: submit, approve, procure, fabricate, and deliver.

3.3.2.3 Mandatory Tasks

Include and properly schedule the following mandatory tasks:

a. Submission, review and acceptance of design packages.

b. Submission of mechanical/electrical/information systems layout drawings.

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

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

f. Submission and approval of testing and air balance (TAB).

g. Submission of TAB specialist design review report.

h. Submission and approval of fire protection specialist.

i. Submission and approval of testing and balancing of HVAC plus commissioning plans and data. Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with ECB 2005-10.

j. Air and water balancing.

k. HVAC commissioning.

l. Controls testing plan submission.

m. Controls testing.

n. Performance Verification testing.

o. Other systems testing, if required.

p. Contractor's pre-final inspection.

q. Correction of punchlist from Contractor's pre-final inspection.

r. Government's pre-final inspection.

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

t. Final inspection.

01 32 01 - 6

3.3.2.4 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements. Government approval of shop drawings activities should be shown with the duration at least the minimum allowed by the contract. The contractor's failure to provide reasonable durations in its schedule for Government activities does not establish or change the Government's review or approval path periods and the durations established for Government's activities are subject to approval by the Contracting Officer.

Allow 30 calendar days total duration prior to current contract completion date for the following activities. Refer to specification Section 01 45 01 USACE QUALITY CONTROL. Include and properly schedule the following critical tasks:

a. Submission of Contractor Quality Control (CQC) for all mechanical/electrical/information systems tests.

b. Government QA for all mechanical systems acceptance/operational tests.

b. Government QA for all electrical systems acceptance/operational tests.

c. CQC completion inspection of the entire project.

d. Contractor works off CQC punchlist.

e. Prefinal inspection performed when the facility is completed such that it can be used for it intended function, as determined by the Contracting Officer.

f. Contractor works off prefinal punchlist.

g. Final/acceptance inspection of the entire project.

h. Contractor works off final punchlist.

3.3.2.5 Contracts with multiple buildings/facilities

Prepare a separate detailed NAS schedule for each building/facility indicating its critical path for specified interim completion dates or critical milestone date. The master NAS schedule shall indicate the interface/lag/link between buildings/facilities to maximize/level the labor and other resources. The master schedule critical path must be indicated through the various buildings/facilities and total duration equal to the contract duration.

3.3.2.6 Activity Responsibility Coding (RESP)

Assign responsibility Code for all activities to the Prime Contractor, Subcontractor or Government agency responsible for performing the activity. 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 Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements. Code all activities not coded with a Government Responsibility Code to the Prime Contractor or Subcontractor responsible to perform the work. Activities

01 32 01 - 7 shall not 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). Unacceptable code values are abbreviations of the names of subcontractors.

3.3.2.7 Activity Work Area Coding

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 shall not have more than one Work Area Code. Not all activities are required to be Work Area coded. A lack of Work Area coding will indicate the activity is not resource or space constrained.

3.3.2.8 Contract Changes/Requests for Equitable Adjustment (REA) Coding

(MODF)

Assign Activity code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by the Contracting Officer, with a Contract Changes/REA Code. Key all Code values to the Government's modification numbering system. Any activity or sequence of activities added to the schedule as a result of alleged constructive changes made by the Government may be added to a copy of the current schedule, subject to the approval of the Contracting Officer.

Assign Activity codes for these activities with a Contract Changes/REA Code. Key the code values to the Contractor's numbering system. Approval to add these activities does not necessarily mean the Government accepts responsibility and therefore liability for such activities and any associated impacts to the schedule, but rather the Government recognizes such activities are appropriately added to the schedule for the purposes of maintaining a realistic and meaningful schedule. Such activities shall not be Responsibility Coded to the Government unless approved. An activity shall not have more than one Contract Changes/REA Code.

3.3.2.9 Contract Line Item (CLIN) Coding (BIDI)

Code all activities to the CLIN on the Contract Line Item Schedule to which the activity belongs. An activity shall not contain more than one CLIN Item Code. CLIN Item code all activities, even when an activity is not cost loaded.

3.3.2.10 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. Code activities to a Construction Phase. Code fast track construction phases proposed by the Contractor to allow filtering and organizing the schedule by fast track design and construction packages. If the contract specifies construction phasing with separately defined performance periods, identify a Construction Phase Code to allow filtering and organizing the schedule accordingly. Each activity shall be identified with a single project phase and have only one Phase of Work code.

01 32 01 - 8

3.3.2.11 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: construction submittal approvals, Acceptance, Procurement, Fabrication, Delivery, Weather Sensitive Installation, Non-Weather Sensitive Installation, Start-Up, Test and Turnover. Assign a Category of Work Code to each activity. Each activity shall have only one Category of Work Code.

3.3.2.12 Definable Features of Work Coding (FOW1, FOW2, FOW3)

Assign a Definable Feature of Work Code to appropriate activities based on the definable feature of work to which the activity belongs. Definable Feature of Work is defined in Specification Section 01 45 01 USACE QUALITY CONTROL. An activity shall not have more than one Definable Feature of Work Code. Not all activities are required to be Definable Feature of Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is acknowledged by the Contractor. Schedule activities on a calendar to which the activity logically belongs. Activities may be assigned to a 7 day calendar when the contract assigns calendar day durations for the activity such as a Government Acceptance activity. If the Contractor intends to perform physical work less than seven days per week, schedule the associated activities on a calendar with non-work periods identified including weekends and holidays. Assign the Category of Work Code - Weather Sensitive Installation to those activities that are weather sensitive.

Original durations must account for anticipated normal adverse weather.

The Government will interpret all work periods not identified as non-work periods on each calendar as meaning the Contractor intends to perform work during those periods.

3.3.3.1 Project Start Date

The schedule shall start no earlier than the date on which the NTP was acknowledged. Include as the first activity in the project schedule an activity called "Start Project"( or NTP). The "Start Project" activity shall have an "ES" constraint date equal to the date that the NTP was acknowledged, and a zero day duration.

3.3.3.2 Schedule Constraints and Open Ended Logic

Constrain completion of the last activity in the schedule by the contract completion date. Schedule calculations shall result in a negative float when the calculated early finish date of the last activity is later than the contract completion date. Include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall have an "LF" constraint date equal to the contract completion date for the project, and with a zero day duration or by using the "project must finish by" date in the scheduling software. The schedule shall have no constrained dates other than those specified in the contract. The use of artificial float constraints such as "zero fee float" or "zero total float"

01 32 01 - 9 are typically prohibited. There shall only be 2 open ended activities:

Start Project (or NTP) with no predecessor logic and End Project with no successor logic.

3.3.3.3 Early Project Completion

In the event the Preliminary or Initial NAS Project Schedule calculates an early completion date of the last activity prior to the contract completion date, the Contractor shall identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Contractor shall include an activity named "contingency" with no cost and a duration equal to the number of calendar days from the date all the contract work is planned to be completed, to the official contract completion date as awarded. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

Include as the first activity for a project phase an activity called "Start Phase X" where "X" refers to the phase of work. The "Start Phase X" activity shall have an "ES" constraint date equal to the date on which the NTP was acknowledged, and a zero day duration.

3.3.4.2 End Phase

Include as the last activity for a project phase an activity called "End Phase X" where "X" refers to the phase of work. The "End Phase X" activity shall have an "LF" constraint date equal to the specified completion date for that phase and a zero day duration.

3.3.4.3 Phase "X" Hammock

Include a hammock type activity for each project phase called "Phase X" where "X" refers to the phase of work. The "Phase X" hammock activity shall be logically tied to the earliest and latest activities in the phase.

3.3.5 Default Progress Data Disallowed

Do not automatically update Actual Start and Finish dates with default mechanisms that may be included in the scheduling software. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the AS and AF dates on the Daily Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's updated schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

01 32 01 - 10

Updating of the percent complete and the remaining duration of any activity shall be independent functions. Disable program features which calculate one of these parameters from the other.

3.3.6 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 all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than two update cycles by logic revision, as approved by the Contracting Officer.

3.3.7 Negative Lags and Start to Finish Relationships

Lag durations contained in the project schedule shall not have a negative value. Do not use Start to Finish (SF) relationships.

3.3.8 Calculation Mode

Schedule calculations shall retain the logic between predecessors and successors even when the successor activity starts and the predecessor activity has not finished. 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") will not be allowed.

3.3.9 Milestones

The schedule must include milestone activities for each significant project event including but not limited to: milestone activities for each fast track design package released for construction; design complete;

foundation/substructure construction complete; superstructure construction complete; building dry-in or enclosure complete to allow the initiation of finish activities; permanent power complete; and building systems commissioning complete.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. Provide a bar chart schedule for the first 30 calendar days of the contract at the Pre-construction conference. The data CD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS.

3.4.1 Preliminary NAS Project Schedule Submission

Submit the Preliminary NAS Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 30 calendar days after the NTP is acknowledged. the Preliminary NAS Project ScheduleThe approved Preliminary NAS Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary NAS Project Schedule to balance the contract award CLINS shown on the Price Schedule. Detail it for the first 90 calendar days. It may be summary in nature for the remaining performance period.

It must be early start and late finish constrained and logically tied as previously specified. The Preliminary NAS Project Schedule forms the basis for the Initial NAS Project Schedule specified herein and must include all of the required Plan and Program preparations, submissions and approvals

01 32 01 - 11 identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, the planned submissions of all early design packages, permitting activities, design review conference activities and other non-construction activities intended to occur within the first 90 calendar days. Schedule any construction activities planned for the first 90 calendar days after NTP.

Constrain planned construction activities by Government acceptance of the associated design package(s) and all other specified Program and Plan approvals. Activity code any activities that are summary in nature after the first 90 calendar days with Responsibility Code (RESP) and Feature of Work code (FOW1, FOW2, FOW3).

3.4.2 Initial NAS Project Schedule Submission

Submit the Initial NAS Project Schedule for approval within 42 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer.

3.4.3 Design Package Schedule Submission

With each design package submitted to the Government, submit a frag-net schedule extracted from the then current Preliminary, Initial or Updated schedule which covers the activities associated with that Design Package including construction, procurement and permitting activities.

3.4.4 Periodic Schedule Updates

Based on the result of the meeting, specified in PERIODIC SCHEDULE UPDATE MEETINGS, submit periodic schedule updates. These submissions will enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgement of the Contracting Officer or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made.

3.4.5 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11, Appendix A. This exact structure is mandatory, even if some fields are not used. A template SDEF compatible schedule backup file (sdef.prx) is available on the QCS website: www.rmssupport.com.

The SDEF format is as follows:

Field Activity Code

Length Description

1 WRKP 3 Workers per Day

2 RESP 4 Responsible Party (e.g. GC, subcontractor, USACE)

3 AREA 4 Area of Work

4 MODF 6 Modification or REA number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of Work

7 CATW 1 Category of Work

01 32 01 - 12

Field Activity Code

Length Description

8 FOW1 10 Feature of Work (used up to 10 characters in length)

9 FOW2 10 Feature of Work (used up to 20 characters in length)

10 FOW3 10 Feature of Work (used up to 30 characters in length)

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary NAS Schedule, Initial NAS Schedule, and every Periodic NAS Schedule Update throughout the life of the project. Provide one hard copy of diagrams and three hard copies of all reports.

3.5.1 Data CDs

Provide two sets of data CDs containing the project schedule in the backup format. Each CD shall also contain all previous update backup files. File medium shall be CD. Label each CD indicating the type of schedule (Preliminary, Initial, Update), full contract number, data date and file name. Each schedule shall have a unique file name as determined by the Contractor.

3.5.2 Narrative Report

Provide a Narrative Report with the Preliminary, Initial, and each Periodic Update of the project schedule, as the basis of the progress payment request. The Narrative Report shall include: a description of activities along the 2 most critical paths where the total float is less than or equal to 20 work days, 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. The narrative report is expected to communicate to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis. Identify and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

3.5.3 Approved Changes Verification

Include only those project schedule changes in the schedule submission that have been previously approved by the Contracting Officer. The Narrative Report shall specifically reference, on an activity by activity basis, all changes made since the previous period and relate each change to documented, approved schedule changes.

3.5.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report shall be as directed by the Contracting Officer. Typically reports shall 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. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission.

01 32 01 - 13

3.5.4.1 Activity Report

A list of all activities sorted according to activity number.

3.5.4.2 Logic Report

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

3.5.4.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.4.4 Earnings Report by CLIN

A compilation of the Contractor's Total Earnings on the project from the NTP to the data date. This report shall reflect the earnings of specific activities based on the agreements made in the schedule update meeting defined herein. Provided that the Contractor has furnished a complete schedule update, this report shall serve as the basis of determining progress payments. Group activities by CLIN item number and sort by activity number.