I.A.02.10_Attachment_A_-_Specifications.pdf

US Army Corps of Engineers Baltimore District

RTA SPECIFICATIONS

SPILLWAY ELECTRICAL

UPGRADE

JENNINGS RANDOLPH LAKE, GARRETT

COUNTY, MARYLAND AND MINERAL

COUNTY, WEST VIRGINIA

OCTOBER 2018

Jennings Randolph Spillway Electrical Upgrade JENSPWYELEC

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 05 00 JOB CONDITIONS

01 14 00 WORK RESTRICTIONS

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

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

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19.00 25 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23.00 25 OPERATION AND MAINTENANCE DATA

DIVISION 09 - FINISHES

09 97 03.00 25 PAINTING: MECHANICAL EQUIPMENT

DIVISION 13 - SPECIAL CONSTRUCTION

13 48 00.00 25 SEISMIC PROTECTION FOR MECHANICAL EQUIPMENT

13 48 00.10 25 SEISMIC PROTECTION FOR MISCELLANEOUS EQUIPMENT

DIVISION 26 - ELECTRICAL

26 05 00.00 25 COMMON WORK RESULTS FOR ELECTRICAL

26 05 19.00 25 INSULATED WIRE AND CABLE

26 05 48.00 25 SEISMIC PROTECTION FOR ELECTRICAL EQUIPMENT

26 08 00.00 25 APPARATUS INSPECTION AND TESTING

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 01 41.00 25 ELECTROMECHANICAL OPERATING MACHINERY FOR LOCKS AND DAMS

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION 01 05 00

JOB CONDITIONS

PART 1 GENERAL

1.1 PHYSICAL DATA: (APR 1984)

Data and information furnished or referred to below is for the Contractor's information. The Government shall not be responsible for any interpretation or conclusion drawn from the data or information by the Contractor. (CENAB)

1.1.1 Transportation Facilities

JENNINGS RANDOLPH LAKE

Jennings Randolph Lake is located in Garrett County, Maryland, and Mineral County, West Virginia, northeast of Kitzmiller, Maryland. Major access routes are I-68, MD State Routes 495, 135, 38, and US Highway 50 (directions from various locations are available at http://www.nab.usace.army.mil/Missions/Dams-Recreation/Jennings-Randolph-Lake/).

1.2 AVAILABILITY OF UTILITIES INCLUDING LAVATORY FACILITIES

It shall be the responsibility of the Contractor to provide all utilities he may require during the entire life of the contract. He shall make his own investigation and determinations as to the availability and adequacy of utilities for his use for construction purposes and domestic consumption. He shall install and maintain all necessary supply lines, connections, piping, and meters if required, but only at such locations and in such manner as approved by the Contracting Officer. Before final acceptance of work under this contract, all temporary supply lines, connections and piping installed by the Contractor shall be removed by him in a manner satisfactory to the Contracting Officer.

1.3 DISPOSAL OF EXISTING MATERIAL AND EQUIPMENT: (DEC 1975)

All removed, dismantled or demolished material and/or equipment including rubble, scrap and debris not specified or indicated to be Government salvaged, reinstalled under this contract or otherwise retained for disposal on Government land will become the property of the Contractor and shall be promptly removed from the site and disposed of by the Contractor at his own expense and responsibility. (CENAB)

1.4 COMPLIANCE WITH POST/BASE REGULATIONS: (JUL 1980)

The site of the work is at a Government lake and all rules and regulations issued by the manager covering general safety, security, sanitary requirements, pollution control, traffic regulations and parking, shall be observed by the Contractor. Information regarding these requirements may be obtained by contacting the Contracting Officer, who will provide such information or assist in obtaining same from appropriate authorities.

(MEMO)

SECTION 01 05 00 Page 1

1.5 PROTECTION OF GOVERNMENT PROPERTY AND PERSONNEL: (DEC 1975)

The Contractor shall protect lake personnel and visitors by installing safety rails and/or barricades as applicable to prevent injury from unauthorized entry into work areas. Warning signs shall be erected as necessary to indicate Construction areas or hazardous zones. Work shall proceed in such manner as to prevent the undue spread of dust and flying particles.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 05 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for information only. 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

Temporary Electrical Wiring Primary and Backup Power Plan; G, DO

A plan defining provisions for temporary wiring and power to the gates.

1.2 SPECIAL PROJECT REQUIREMENTS

1.2.1 Mobilization Date Restriction

Mobilization to the project site shall not begin prior to 1 July 2019.

This restriction is imposed to allow work at the project site under a separate contract to be completed.

1.2.2 Maintaining Gate Operability

A minimum of 3 of the 5 tainter gates shall be operable at all times. The Corps dam operators can also limit which two gates are inoperable at the same time (because certain gates at the spillway are intended to be operated in tandem during a high water event). The Contractor shall assume that any inoperable gates must remain in the fully closed position.

Prior to the start of work, a meeting shall be held to discuss anticipated gate inoperability. This meeting shall include the Contractor, Contracting Officer's Representative (COR), dam operator and Baltimore District Water Control Office. Anticipated periods of gate inoperability shall be identified on the project schedule along with the anticipated duration. A minimum of 7 days prior to any gate being made inoperable, the Contractor shall notify the COR and receive approval from the Baltimore District Water Control Office.

1.2.3 Gate Power Supply

The Contractor shall ensure that primary and backup power is provided for the gates throughout the work. Government-furnished electrical power 480V main feed to the spillway may be used for primary power. Install all temporary electrical wiring in accordance with EM 385-1-1 and as approved by the COR. The Contractor shall also supply a temporary generator throughout the work that can power the gates in the event of primary power failure. The temporary generator shall be capable of supporting the simultaneous operation of 3 gates. The Contractor shall ensure the generator is hardwired into the system so that it can provide immediate

SECTION 01 14 00 Page 1 backup in the event of primary power failure.

The Contractor shall design and submit a temporary electrical wiring primary and backup power plan for temporary connections to the gate for Government approval a minimum of 30 days prior to the start of work.

The plans shall provide information on all details of the work (routing, cabling, equipment and materials, etc). The Contractor shall be responsible to fully implement the approved plan to include providing all materials, equipment, and labor for the temporary connections to the gates. All temporary electrical equipment and wiring must be removed prior to completion of the contract.

1.2.4 Lake Elevation and Work Impacts

The normal elevation of the lake is approximate elevation 1466.0' in the summer and at lower elevations in the winter. The crest of the spillway is elevation 1468.0'. The lake level is therefore below the level of the gates at normal pool.

The Contractor is advised that the level of the lake can vary during high inflows at times the water will rise above the bottom of the gates. During normal low level fluctuations in lake elevation, the Contractor shall be permitted to continue work while water is against the gates, except that gates will not be allowed to open during these periods (as that would result in spillway flows).

Very high water events are infrequent but possible. During any very large increases in lake elevation that may require the Government to activate the spillway for releases, the contractor will be required to cease construction operations and remove material and equipment from the spillway area. The Contracting Officer will attempt to provide notification for such removal as early as possible but the Contractor must be aware of the inconsistencies of weather forecasting and should be prepared to perform removal within 24 hours. Costs for such removal shall be covered in accordance with the CHANGES clause of the contract. The Contractor shall provide the Contracting Officer with contact phone numbers that can be used to ensure rapid notification during such events (see subparagraph "Subcontractors and Personnel Contacts" below).

1.2.5 Government Access Across Spillway Bridge

The Government will require vehicular access across the spillway bridge on a regular basis throughout the work. At the end of each day the Contractor shall leave the bridge unblocked to allow vehicular access across the bridge. The Government will work with the Contractor for special circumstances where it is necessary to leave equipment on the bridge overnight, and related requests should be coordinated through the COR. The Government will at times also require access across the bridge during the day and will coordinate with the Contractor to minimize disruption of work.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Government Lake Regulations

Ensure that Contractor personnel employed at the lake become familiar with and obey regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear hard hats in designated areas. Do not enter any non-work areas unless required to do so and until cleared for such entry. Mark

SECTION 01 14 00 Page 2

Contractor equipment for identification.

1.3.1.1 Subcontractors and Personnel Contacts

Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. These personnel shall be available for 24 hour emergency contact/notification. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.3.1.2 Identification Badges and Lake Access

All Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and local security policies and procedures (provided by government representative). The Contractor shall also provide all information required for background checks to meet installation access requirements. Contractor workforce must comply with all personal identity verification requirements. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes. The Contractor must pre-screen employees using the E-verify Program (http://www.dhs.gov/E-Verify) website to meet the established employment eligibility requirements. The Contractor shall ensure that the employee has two valid forms of Government issued identification prior to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible employees must be provided to the Contracting Officer no later than 3 business days after the initial contract award.

1.3.1.3 Personnel Entry Approval

Failure to obtain entry approval will not affect the contract price or time of completion.

1.3.2 Working Hours

Regular working hours must be between the hours of 0700 and 1530 Monday through Friday excluding Government holidays.

1.3.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress

1.3.4 Occupied Buildings

The Contractor shall be working around existing buildings which are occupied. Do not enter the buildings without prior approval of the Contracting Officer.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 3

SECTION 01 14 00 Page 4

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for information only. 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

Photographs

Photographs and, as applicable, negatives showing construction progress.

1.2 SUPERVISION

Have at least one qualified supervisor capable of reading, writing, and conversing fluently in the English language on the job site during working hours. In addition, if a Quality Control (QC) representative is required on the contract, then that individual shall also have fluent English communication skills.

1.3 PRECONSTRUCTION CONFERENCE

After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule prices, shop drawings, and other submittals, scheduling programming, and prosecution of the work.

Major subcontractors who will engage in the work shall also attend.

1.4 AVAILABILITY OF CADD DRAWING FILES

After award and upon request, the electronic "Computer-Aided Drafting and Design (CADD)" drawing files will only be made available to the Contractor for use in preparation of construction data related to the referenced contract subject to the following terms and conditions.

Data contained on these electronic files shall not be used for any purpose other than as a convenience in the preparation of construction data for the referenced project. Any other use or reuse shall be at the sole risk of the Contractor and without liability or legal exposure to the Government. The Contractor shall make no claim and waives to the fullest extent permitted by law, any claim or cause of action of any nature against the Government, its agents or sub consultants that may arise out of or in connection with the use of these electronic files. The Contractor shall, to the fullest extent permitted by law, indemnify and hold the Government harmless against all damages, liabilities or costs, including reasonable attorney's fees and defense costs, arising out of or resulting from the use of these electronic files.

SECTION 01 30 00 Page 1

These electronic CADD drawing files are not construction documents.

Differences may exist between the CADD files and the corresponding construction documents. The Government makes no representation regarding the accuracy or completeness of the electronic CADD files, nor does it make representation to the compatibility of these files with the Contractors hardware or software. In the event that a conflict arises between the signed and sealed construction documents prepared by the Government and the furnished CADD files, the signed and sealed construction documents shall govern. The Contractor is responsible for determining if any conflict exists. Use of these CADD files does not relieve the Contractor of duty to fully comply with the contract documents, including and without limitation, the need to check, confirm and coordinate the work of all contractors for the project.

If the Contractor uses, duplicates and/or modifies these electronic CADD files for use in producing construction drawings and data related to this contract, all previous indicia of ownership (seals, logos, signatures, initials and dates) shall be removed.

1.5 PERMITS

Applying for and obtaining any and all permits that are or may be required for this project is the sole responsibility, and at the expense of, the Contractor.

1.6 PHOTOGRAPHS

Provide monthly, and within one month of the completion of work, digital photographs in JPEG file format showing the sequence and progress of work. Take a minimum of ten digital photographs prior to the seventh day of each month of views and points designated after award by the Contracting Officer. Submit a view location sketch indicating points of view. Submit with the monthly invoice two sets of digital photographs each set on a separate CD-R, cumulative of all photos to date. Photographs for each month shall be in a separate monthly directory and each file shall be named to indicate its location on the view location sketch. The view location sketch shall also be provided on the CD as digital file.

All file names shall include a date designator. (CENAB-EN)

1.7 ELECTRONIC MAIL (E-MAIL) ADDRESS

The Contractor shall establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments in Microsoft, Adobe Acrobat, and other similar formats.

Within 10 days after contract award, the Contractor shall provide the Contracting Officer a single (only one) e-mail address for electronic communications from the Contracting Officer related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes, terrorist threats, etc.

Multiple email address will not allowed.

It is the Contractor's responsibility to make timely distribution of all Contracting Officer initiated e-mail with its own organization including field office(s). The Contractor shall promptly notify the Contracting Officer, in writing, of any changes to this email address.

SECTION 01 30 00 Page 2

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00 Page 3

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only. 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 Schedule; G, DO

1.3 SCHEDULE PREPARER

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling projects similar in nature to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

PART 2 PRODUCTS

2.1 SOFTWARE

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

2.1.1 Government Default Software

The Government intends to use Primavera P6.

2.1.2 Contractor Software

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

SECTION 01 32 01.00 10 Page 1

2.1.2.1 Primavera

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

2.1.2.2 Other Than Primavera

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

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to 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. Provide a schedule that is a forward planning as well as a project monitoring tool.

3.1.1 Approved Project 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. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, 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

SECTION 01 32 01.00 10 Page 2 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 update period and therefore the amount of each progress payment.

Lack of an approved schedule update, or qualified scheduling personnel, will result in the 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 Project Schedule shall be capable of meeting all requirements of this specification. Comply with PRIMAVERA P6 - USACE MANDATORY REQUIREMENTS.

Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule.

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. Procurement activities are defined herein.

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

SECTION 01 32 01.00 10 Page 3 calendar days. A typical procurement sequence includes the string of activities: submit, approve, procure, fabricate, and deliver.

3.3.2.3 Mandatory Tasks

The following tasks must be included and properly scheduled:

a. Submission and approval of as-built drawings.

b. Performance Verification testing.

c. Other systems testing, if required.

d. Contractor's pre-final inspection.

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

f. Government's pre-final inspection.

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

h. Final inspection.

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.

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

SECTION 01 32 01.00 10 Page 4

3.3.2.7 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.8 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.9 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.

3.3.2.10 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.11 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 00.00 10 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.

SECTION 01 32 01.00 10 Page 5

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 received 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" 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 project schedule calculates an early completion date of the last activity prior to the contract completion date, 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 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.

SECTION 01 32 01.00 10 Page 6

3.3.4 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. 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.5 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.6 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.7 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.8 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. The data CD, reports, and network diagrams required for each submission are contained in paragraph

SUBMISSION REQUIREMENTS.

SECTION 01 32 01.00 10 Page 7

3.4.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 15 calendar days after the NTP is acknowledged. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. 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 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, 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 Project Schedule Submission

Submit the Initial 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 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 judgment 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.4 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:

http://rms.usace.army.mil/ . The SDEF format is as follows:

SECTION 01 32 01.00 10 Page 8

SDEF Format

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

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 Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

3.5.1 Data CD's

Provide two sets of data CD's containing the project schedule in the backup Primavera P6 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.

SECTION 01 32 01.00 10 Page 9

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.

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. This report shall: sum all activities coded to a particular CLIN and provide a CLIN item percent earned value; and complete and sum CLIN items to provide a total project percent complete. The printed report shall contain, for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), and Earnings to Date.

3.5.5 Network Diagram

The network diagram is required for the Preliminary, Initial and Periodic Updates. The network diagram shall depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

SECTION 01 32 01.00 10 Page 10

3.5.5.1 Continuous Flow

Diagrams shall 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.5.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.5.3 Critical Path

Clearly show the critical path.

3.5.5.4 Banding

Organize activities as directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by category of work, work area and/or responsibility.

3.5.5.5 S-Curves

Earnings curves showing projected early and late earnings and earnings to date.

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

Conduct periodic schedule update meetings for the purposes of reviewing the Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. Meetings shall occur at least monthly within five days of the proposed schedule data date and after the Contractor has updated the schedule with Government concurrence respecting actual start dates, actual finish dates, remaining durations and percent complete for each activity it intend to status. Provide a computer with the scheduling software loaded and a projector during the meeting which allows all meeting participants to view the proposed schedule update during the meeting.

The meeting and resultant approvable schedule update shall be a condition precedent to a formal submission of the update as described in SUBMISSION REQUIREMENTS and to the submission of an invoice for payment. The meeting will be a working interactive exchange which will allow the Government and the Contractor the opportunity to review the updated schedule on a real time and interactive basis. The Contractor's authorized scheduling representative will organize, sort, filter and schedule the update as requested by the Government. The meeting will last no longer than 8 hours. A rough draft of the proposed activity logic corrections and narrative report shall be provided to the Government 48 hours in advance of the meeting. The Contractor's Project Manager and Authorized Scheduler shall attend the meeting with the Authorized Representative of the Contracting Officer.

3.6.1 Update Submission Following Progress Meeting

Submit a complete update of the project schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 working days after the periodic schedule update meeting, reflecting only those changes made during the previous update meeting.

SECTION 01 32 01.00 10 Page 11

3.6.2 Status of Activities

Update information, including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete shall be subject to the approval of the Government prior to the meeting. As a minimum, address the following items on an activity by activity basis during each progress meeting.

3.6.2.1 Start and Finish Dates

Accurately show the status of the AS and/or AF dates for each activity currently in-progress or completed since the last update. The Government may allow an AF date to be assigned with the percent complete less than 100 percent to account for the value of work remaining but not restraining successor activities. Only assign AS dates when actual progress occurs on an activity.

3.6.2.2 Remaining Duration

Update the estimated RD for all incomplete activities independent of Percent Complete. Remaining Durations may exceed the activity OD or may exceed the activity's prior update RD if the Government considers the current OD or RD to be understated based on current progress, insufficient work crews actually manning the job, unrealistic OD or deficiencies that must be corrected that restrain successor activities.

3.6.2.3 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, cost load the correction of punch list from Government pre-final inspection activity(ies) not less than 1 percent of the total contract value, which activity(ies) may be declared 100 percent complete upon completion and correction of all punch list work identified during Government pre-final inspection(s).

3.6.2.4 Logic Changes

Specifically identify and discuss all logic changes pertaining to NTP on change orders, change orders to be incorporated into the schedule, Contractor proposed changes in work sequence, corrections to schedule logic for out-of-sequence progress, and other changes that have been made pursuant to contract provisions. The Government will only approve logic revisions for the purpose of keeping the schedule valid in terms of its usefulness in calculating a realistic completion date, correcting erroneous logic ties, and accurately sequencing the work.

3.6.2.5 Other Changes

Other changes…