TSpecs_W912P519B0013_2July2019.pdf

Solicitation No. W912P519B0013

US Army Corps Of Engineers Nashville District

NRS Substation Upgrade

Old Hickory Lock Davidson County Old Hickory, Tennessee

Technical Specifications

RTA

July 2019

THIS PAGE INTENTIONALLY LEFT BLANK

FOR DUPLEX PRINTING

NRS Substation Upgrade Old Hickory Lock W912P519B0013 Old Hickory, Tennessee

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 00 00 GENERAL REQUIREMENTS

01 22 00 PRICE AND PAYMENT PROCEDURES

01 32 01.10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 35 50 PROJECT SITE SECURITY AND AT/OPSEC PROCEDURES

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 QUALITY CONTROL

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

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 95 00 FORMS AND ATTACHMENTS

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 82 13 ASBESTOS ABATEMENT

02 82 33.13 REMOVAL/CONTROL AND DISPOSAL OF PAINT WITH LEAD

DIVISION 03 - CONCRETE

03 30 53 MISCELLANEOUS CAST-IN-PLACE CONCRETE

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 19.10 10 INSULATED WIRE AND CABLE

26 08 00 APPARATUS INSPECTION AND TESTING

26 12 19 PAD-MOUNTED, LIQUID-FILLED, MEDIUM-VOLTAGE TRANSFORMERS

26 23 00 LOW-VOLTAGE SWITCHGEAR

DIVISION 33 - UTILITIES

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 00 00

GENERAL REQUIREMENTS

PART 1 GENERAL

1.1 GENERAL

1.2 COORDINATION CONFERENCES

1.3 PARTNERING

1.4 REFERENCES

1.5 PROJECT SIGNS

1.5.1 General

1.5.2 Materials

1.5.3 Painting

1.5.4 Erection and Maintenance

1.6 CONTRACTOR'S STAGING AREA

1.7 DAILY CLEANUP AND DISPOSAL

1.8 PROTECTION AND RESTORATION OF EXISTING FACILITIES

1.9 EVALUATION OF CONTRACTOR PERFORMANCE

1.10 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS OF ENGINEERS

CONTRACTS

1.11 MEASUREMENT AND PAYMENT

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION

3.1 AVAILABILITY AND USE OF UTILITY SERVICES

3.1.1 Contractor Responsibilities

3.1.2 Interruptions of Utilities

3.2 Cable Protection

-- End of Section Table of Contents --

SECTION 01 00 00 Page 1

SECTION 01 00 00

GENERAL REQUIREMENTS

PART 1 GENERAL

1.1 GENERAL

This section comprises an explanation of the general contract requirements needed to accomplish the work. All work specified herein shall be accomplished in accordance with the procedures prescribed in the specifications and drawings.

1.2 COORDINATION CONFERENCES

Routine coordination conferences will be scheduled by the Contracting Officer throughout the life of this project. Coordination conferences will be held to discuss contract administration, Contractor quality control, phasing, scheduling, and other aspects relating to this construction. The Corps of Engineers and the Contractor will be represented at each of these meetings. Coordination conferences will be scheduled to occur when notified by the Contracting Officer.

1.3 PARTNERING

In order to most effectively accomplish this contract, the Government urges the contractor to join the Government in establishing a cohesive and professional project management team. Through this "partnering" relationship both entities would strive to draw on the strengths of each organization for the ultimate goal of assuring that the project’s intended results are achieved, within budget and on schedule. This endeavor seeks an environment that nurtures team building, cooperation and trust between the Government and the Contractor. The partnering relationship would be bilateral in make-up, and participation will be totally voluntary.

The first step in initiating the concept would be a joint project management team "partnering" conference attended by multiple officers from each organization representing management and the key jobsite staff of each entity. The initial conference would be held on the same day as the preconstruction conference. The Resident Engineer would chair the conference, establish its agenda and distribute minutes of the meeting. The Contracting Officer's Representative or Administrative Contracting Officer would lead the participants of the session, through the steps of team building and the formation of a problem solving mechanism within the group. The conference duration would be no more than one hour. Location of the conference would be the same as the preconstruction conference.

1.4 REFERENCES

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

SECTION 01 00 00 Page 2

U.S. ARMY CORPS OF ENGINEERS (USACE)

EP 310-1-6a (2006) Sign Standards Manual, VOL 1

EP 310-1-6b (2006) Sign Standards Manual, VOL 2, Appendices

1.5 PROJECT SIGNS

1.5.1 General

Furnish and erect, within 15 days after issuance of the Notice to Proceed, a PROJECT IDENTIFICATION SIGN and a SAFETY PERFORMANCE SIGN at the location directed by the Contracting Officer. Letter signs on one side only and conform to EP 310-1-6a (Section 16), EP 310-1-6b, and to the details and colors shown on the sketches attached at the end of Section 01 95 00 FORMS AND ATTACHMENTS. Name the project as follows:

N.R.S. SUBSTATION REPLACEMENT AND RELOCATION

1.5.2 Materials

Construct the sign with a face sheet of 3/4 inch exterior grade plywood mounted on a substantial framework of treated 4-inch by 4-inch material.

Screws shall be commercial quality and of sizes shown.

1.5.3 Painting

Apply one prime coat and two finish coats of exterior oil paint to signs and post before lettering. Apply letters and trim to one side only using one coat of enamel of color, style, and size shown.

1.5.4 Erection and Maintenance

Erect signs at the locations designated by the Contracting Officer. Signs shall be plumb and backfill of post holes shall be well tamped to properly support the signs throughout the life of the contract. Maintain signs in good condition until completion of the contract. Remove signs from the site upon final acceptance of the contract work.

1.6 CONTRACTOR'S STAGING AREA

The Contractor will be assigned an area within or near the project site for use as a staging area. The building of structures, the erection of tents or other forms of protection will be permitted only at such places as the Government shall approve, and the sanitary conditions of the grounds in or about such structures shall at all times be maintained in a satisfactory manner. Temporary Contractor facilities provided during Construction shall be removed prior to final acceptance from the Government. As a minimum the area shall be left looking "broom clean" and at least as clean as before the structure placement.

1.7 DAILY CLEANUP AND DISPOSAL

Work areas shall be kept reasonably neat on a daily basis. Debris resulting from the work, such as empty paint cans, packing cases, scrap lumber, oil and grease spills, and other debris shall be collected, removed, and disposed of off-site at least once per week. Government trash cans, dump boxes and other containers shall not be used. Liquid waste

SECTION 01 00 00 Page 3 shall not be disposed of in existing drains.

1.8 PROTECTION AND RESTORATION OF EXISTING FACILITIES

Existing facilities shall be protected whether or not shown on the drawings. Upon completion of the work, existing facilities, not included as a portion of the work, shall be left in a condition equal to the original condition prior to the contract. Costs for repair and restoration of any facilities shall be considered to be incidental to and included in the contract price.

1.9 EVALUATION OF CONTRACTOR PERFORMANCE

The Contractor's performance will be evaluated in accordance with FAR Part

42.15 in the areas of quality, schedule, cost control, management, utilization of small businesses, and regulatory compliance at minimum. The evaluation will include a written narrative and rating of either exceptional, very good, satisfactory, marginal, or unsatisfactory for each. The format for the evaluation is attached at the end of Section

01 95 00 FORMS AND ATTACHMENTS.

The Contractor's review of the evaluation shall be completed electronically at the CPARS, http://www.cpars.gov. This website also includes guidance and the user's manual.

Upon contract award, the Contractor shall provide the Contracting Officer with the name and e-mail address of the Contractor's Representative to be registered into the system. Following initial completion by the Government, the Contractor will have sixty (60) calendar days to review, comment, and return the evaluation.

1.10 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS OF ENGINEERS CONTRACTS

In addition to complying with the requirements outlined in FAR Part 22.13, FAR Provision 52.222-38, FAR Clause 52.222-35, FAR Clause 52.222-37, DFARS

222.13 and Department of Labor regulations, U.S. Army Corps of Engineers (USACE) contractors and subcontractors at all tiers are encouraged to promote the training and employment of U.S. veterans while performing under a USACE contract. While no set-aside, evaluation preference, or incentive applies to the solicitation or performance under the resultant contract, USACE contractors are encouraged to seek out highly qualified veterans to perform services under this contract. The following resources are available to assist USACE contractors in their outreach efforts:

a. U.S. Department of Labor Veterans employment: www.vets.gov/

b. Federal veteran employment information: www.fedshirevets.gov/index.aspx

c. Veterans’ Employment and Training Service (VETS):

http://www.dol.gov/vets/

d. Veterans Opportunity to Work (VOW) Program: http://benefits.va.gov/vow/

e. U.S. Army Warrior Transition Command Employment Index:

http://www.wct.army.mil/modules/employers/index.html

f. Hiring Our Heroes initiative:

www.uschamberfoundation.org/hiring-our-heroes

SECTION 01 00 00 Page 4

1.11 MEASUREMENT AND PAYMENT

No separate payment will be made for the work covered under this section.

The costs thereof shall be included in the item to which the work pertains.

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION

3.1 AVAILABILITY AND USE OF UTILITY SERVICES

3.1.1 Contractor Responsibilities

a. The Contractor shall be responsible for the availability of utilities for use on the project. Raw water is available with no charge at the site. The contractor shall supply any other utilities needed at his cost. The Contractor shall carefully conserve any utilities furnished without charge.

b. The Contractor, at its expense and in a workmanlike manner satisfactory to the Contracting Officer, shall install and maintain all necessary temporary connections and distribution lines. Before final acceptance of the work by the Government, the Contractor shall remove all the temporary connections, distribution lines, and associated paraphernalia.

c. The Contractor is responsible for providing drinking water facilities for all personnel associated with this contract.

3.1.2 Interruptions of Utilities

a. No utility services shall be interrupted by the Contractor to make connections, to relocate, or for any purpose without approval of the Contracting Officer.

b. Request for Permission to shut down services shall be submitted in writing to the Contracting Officer not less than seventeen (17) days prior to date of proposed interruption. The request shall give the following information:

(1) Nature of Utility (Gas, L.P. or H.P., Water, etc.)

(2) Size of line and location of shutoff.

(3) Buildings and services affected.

(4) Hours and date of shutoff.

(5) Estimated length of time services will be interrupted.

c. Services shall not be shutoff until receipt of approval of the proposed hours and date from the Contracting Officer.

d. Shutoffs which will cause interruption of Government work operations as determined by the Contracting Officer shall be accomplished during regular non-work hours or on non-work days of the Using Agency.

e. Operation of valves on water mains will be by Government personnel.

Where shutoff of water lines interrupts service to fire hydrants or fire sprinkler systems, the Contractor shall arrange his operations and have sufficient material and personnel available to complete the work without undue delay or to restore service without delay in event of

SECTION 01 00 00 Page 5 emergency.

3.2 Cable Protection

There are areas in the cable tunnels where the existing cable trays have been covered to be protect from falling water. It is the contractors responsibility to maintain this protection during the removal of the existing cable tray and the installation of the new cable tray.

-- End of Section --

SECTION 01 00 00 Page 6

THIS PAGE INTENTIONALLY LEFT BLANK

FOR DUPLEX PRINTING

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 22 00

PRICE AND PAYMENT PROCEDURES

PART 1 GENERAL

1.1 GENERAL INFORMATION

1.2 PAYMENT ITEMS

1.2.1 Performance and Payment Bonds

1.2.1.1 Payment

1.2.1.2 Unit of Measure

1.2.2 Demolition

1.2.2.1 Payment

1.2.2.2 Unit of Measure

1.2.3 Install Integrated Power Assembly

1.2.3.1 Payment

1.2.3.2 Unit of Measure

1.2.4 Install NRS Transformers

1.2.4.1 Payment

1.2.4.2 Unit of Measure

1.2.5 Inspection and Testing

1.2.5.1 Payment

1.2.5.2 Unit of Measure

1.2.6 Concrete

1.2.6.1 Payment

1.2.6.2 Unit of Measure

1.2.7 Cable and Conduit

1.2.7.1 Payment

1.2.7.2 Unit of Measure

1.2.8 Dewater Pump Disconnect and Feeders -Option 1

1.2.8.1 Payment

1.2.8.2 Unit of Measure

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 22 00 Page 1

SECTION 01 22 00

PRICE AND PAYMENT PROCEDURES

PART 1 GENERAL

1.1 GENERAL INFORMATION

Payment items for the work of this contract are listed in the BIDDING SCHEDULE and described below. All costs for items of work, which are not specifically mentioned to be included in a particular job or unit price payment item, are included in the listed payment item most closely associated with the work involved. The price and payment made for each payment item listed constitutes full compensation for furnishing all plant, labor, materials, and equipment, and performing any associated Contractor quality control, environmental protection, meeting safety requirements, tests and reports, and for performing all work required for which separate payment is not otherwise provided.

1.2 PAYMENT ITEMS

1.2.1 Performance and Payment Bonds

1.2.1.1 Payment

Payment will be made for costs associated with performance and payment bonds at each site. In accordance with Contract Clause 52.232-5 PAYMENTS UNDER FIXED-PRICE CONSTRUCTION CONTRACTS, the premiums for performance and payment bonds shall be included in the contract price. Payment for the premiums for performance and payment bonds will be made at the contract price per Job for "Performance and Payment Bonds." Payments made under this provision shall not exceed the amount included for "Performance and Payment Bonds," which payment shall take into consideration any discounts or rebates to the Contractor from the Surety. The Contractor is advised that the pay item "Performance and Payment Bonds" is only for the cost of bonds. Other costs should be allocated to the appropriate bid items.

1.2.1.2 Unit of Measure

Unit of measure: Job.

1.2.2 Demolition

1.2.2.1 Payment

Payment will be made for costs associated with demolition activities as shown in the drawings and as specified in Section 02 41 00 DEMOLITION.

This cost includes considerartion for offsite transportation and disposal.

Payment will be made at the contract price per Job for "Demolition".

1.2.2.2 Unit of Measure

Unit of measure: Job.

SECTION 01 22 00 Page 2

1.2.3 Install Integrated Power Assembly

1.2.3.1 Payment

Payment will be made for costs associated with installing Integrated Power Assembly as shown in the drawings and as specified in Section 26 23 00 LOW-VOLTAGE SWITCHGEAR. Payment will be made at the contract price per Job for "Install Integrated Power Assembly".

1.2.3.2 Unit of Measure

Unit of measure: Job.

1.2.4 Install NRS Transformers

1.2.4.1 Payment

Payment will be made for costs associated with installing NRS Transformers as shown in the drawings and as specified in Section 26 12 19 PAD-MOUNTED, LIQUID-FILLED, MEDIUM-VOLTAGE TRANSFORMERS. Payment will be made at the contract price per Job for "Install NRS Transformers".

1.2.4.2 Unit of Measure

Unit of measure: Job.

1.2.5 Inspection and Testing

1.2.5.1 Payment

Payment will be made for costs associated with Inspection and Testing activities as shown in the drawings and as specified in Section 26 08 00 Apparatus Inspection and Testing. Payment will be made at the contract price per Job for "Inspection and Testing".

1.2.5.2 Unit of Measure

Unit of measure: Job.

1.2.6 Concrete

1.2.6.1 Payment

Payment will cover all costs associated with manufacturing, furnishing, delivering, placing, finishing, and curing of concrete for the various items of the schedule, including the cost of all formwork, as shown in the drawings and as specified in Section 03 30 53 MISCELLANEOUS CAST-IN-PLACE CONCRETE. Payment will be made at the contract price per Job for "Concrete". Payment for grout, preformed expansion joints, field-molded sealants, waterstops, reinforcing steel bars or wire reinforcement is to be included in this payment item.

1.2.6.2 Unit of Measure

Unit of measure: JOB.

SECTION 01 22 00 Page 3

1.2.7 Cable and Conduit

1.2.7.1 Payment

Payment will be made for costs associated with providing and installing cable and conduit as shown in the drawings and as specified in Sections 26 05 19 INSULATED WIRE AND CABLE, and 33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION. Payment will be made at the contract price per Job for "Cable and Conduit".

1.2.7.2 Unit of Measure

Unit of measure: Job.

1.2.8 Dewater Pump Disconnect and Feeders -Option 1

1.2.8.1 Payment

Payment will be made for costs associated with providing and installing Dewater Pump Disconnect and Feeders as shown in the drawings and as specified in Sections 26 05 19 INSULATED WIRE AND CABLE, and 26 23 00 LOW-VOLTAGE SWITCHGEAR. Payment will be made at the contract price (for Option 1) per Job for "Dewater Pump Disconnect and Feeders".

1.2.8.2 Unit of Measure

Unit of measure: Job.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 22 00 Page 4

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.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 Contractor Software

2.1.1.1 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 Contract Milestones and Constraints

3.3.6.1 Project Start Date Milestone

3.3.6.2 End Project Finish Milestone

3.3.6.3 Interim Completion Dates and Constraints

3.3.6.3.1 Start Phase

3.3.6.3.2 End Phase

3.3.7 Calendars

3.3.8 Open Ended Logic

3.3.9 Default Progress Data Disallowed

3.3.10 Out-of-Sequence Progress

3.3.11 Added and Deleted Activities

3.3.12 Original Durations

3.3.13 Leads, Lags, and Start to Finish Relationships

3.3.14 Retained Logic

3.3.15 Percent Complete

3.3.16 Remaining Duration

3.3.17 Cost Loading of Closeout Activities

3.3.17.1 As-Built Drawings

3.3.18 Anticipated Adverse Weather

3.3.19 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

SECTION 01 32 01.10 Page 1

3.4.2 Initial Project Schedule Submission

3.4.3 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Narrative Report

3.5.2 Schedule Reports

3.5.2.1 Activity Report

3.5.2.2 Logic Report

3.5.2.3 Total Float Report

3.5.2.4 Earnings Report by CLIN

3.5.3 Network Diagram

3.5.3.1 Continuous Flow

3.5.3.2 Project Milestone Dates

3.5.3.3 Critical Path

3.5.3.4 Banding

3.5.3.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 PRIMAVERA P6 MANDATORY REQUIREMENTS

SECTION 01 32 01.10 Page 2

SECTION 01 32 01.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

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

2.1.1 Contractor Software

Scheduling software used by the contractor must be capable of meeting all

SECTION 01 32 01.10 Page 3 requirements of this specification.

2.1.1.1 Primavera

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

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE 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. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.

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

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract 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 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:

SECTION 01 32 01.10 Page 4

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. Submission, review and acceptance of features require design completion

c. Long procurement activities

d. Submission and approval of as-built drawings.

e. Contractor's pre-final inspection.

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

g. Government's pre-final inspection.

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

i. 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, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

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

3.3.6.1 Project Start Date Milestone

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged,"

SECTION 01 32 01.10 Page 5

3.3.6.2 End Project Finish Milestone

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.6.3 Interim Completion Dates and Constraints

3.3.6.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.6.3.2 End Phase

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

3.3.7 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 days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. 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.8 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.9 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

SECTION 01 32 01.10 Page 6 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.10 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.11 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.12 Original Durations

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

3.3.13 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.14 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.15 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.16 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

SECTION 01 32 01.10 Page 7 duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.

3.3.17 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.17.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 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

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

SECTION 01 32 01.10 Page 8 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 design activities, 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. Government acceptance of the associated design package(s) and all other specified Program and Plan 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. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

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

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS.

These updates will enable the Government to assess Contractor's progress.

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

SECTION 01 32 01.10 Page 9

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.

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.2 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.2.1 Activity Report

List of all activities sorted according to activity number.

3.5.2.2 Logic Report

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

3.5.2.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.2.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 Network Diagram

The Network Diagram is required for the Preliminary, Initial and Periodic Updates. Depict and display the order and interdependence of activities

SECTION 01 32 01.10 Page 10 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 review compliance with this paragraph:

3.5.3.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.3.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.3.3 Critical Path

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

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

SECTION 01 32 01.10 Page 11

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 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. If Contracting Officer determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. Unless approved by the Contracting Officer, no other changes may be incorporated into the schedule being used to justify the time impact.

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

Prepare an analysis for approval by the Contracting Officer based on industry standard AACE 29R-03.

3.8.4 Fragmentary Network (Fragnet)

Prepare a proposed fragnet for time impact analysis consisting of a sequence of new activities that are proposed to be added to the project schedule to demonstrate the influence of the delay or impact to the

SECTION 01 32 01.10 Page 12 project's contractual dates. Clearly show how the proposed fragnet is to be tied into the project schedule including all predecessors and successors to the fragnet activities. The proposed fragnet must be approved by the Contracting Officer prior to incorporation into the project schedule.

3.8.5 Time Extension

The Contracting Officer must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.8.6 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The Contractor must show that an early completion was achievable had it not been for the impact.

3.9 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer may require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.

3.9.1 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.9.2 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the Contracting Officer pursuant to FAR 52.236-15 Schedules for Construction Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.

SECTION 01 32 01.10 Page 13

3.9.3 Recovery Schedule

Should the Contracting Officer find it necessary, submit a recovery schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.

3.10 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, float available in the schedule, at any time, may not be considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.

3.11 PRIMAVERA P6 MANDATORY REQUIREMENTS

If Primavera P6 is being used, request a backup file template (.xer) from the Government, if one is available, prior to building the schedule. The following settings are mandatory and required in all schedule submissions to the Government:

a. Activity Codes must be Project Level, not Global or EPS level.

b. Calendars must be Project Level, not Global or Resource level.

c. Activity Duration Types must be set to "Fixed Duration & Units".

d. Percent Complete Types must be set to "Physical".

e. Time Period Admin Preferences must remain the default "8.0 hr/day, 40 hr/week, 172 hr/month, 2000 hr/year". Set Calendar Work Hours/Day to