Amend-0001__TechSpec.pdf

McNary 350 Ton Bridge Crane Skew Correction W912EF-16-R-0026 Amend-0001

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 28

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 QUALIFICATIONS

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.1.1 Approved Project Schedule

3.1.2 Schedule Status Reports

3.2 BASIS FOR PAYMENT AND COST LOADING

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Critical Path Method

3.3.2 Level of Detail Required

3.3.2.1 Activity Durations

3.3.2.2 Procurement Activities

3.3.2.3 Mandatory Tasks

3.3.2.4 Government Activities

3.3.2.5 Activity Responsibility Coding (RESP)

3.3.2.6 Activity Work Area Coding

3.3.2.7 Contract Changes/Requests for Equitable Adjustment (REA)

Coding (MODF)

3.3.2.8 Contract Line Item (CLIN) Coding (BIDI)

3.3.2.9 Phase of Work Coding (PHAS)

3.3.2.10 Category of Work Coding (CATW)

3.3.2.11 Definable Features of Work Coding (FOW)

3.3.3 Scheduled Project Completion and Activity Calendars

3.3.3.1 Project Start Date

3.3.3.2 Schedule Constraints and Open Ended Logic

3.3.3.3 Early Project Completion

3.3.4 Interim Completion Dates

3.3.4.1 Start Phase

3.3.4.2 End Phase

3.3.4.3 Phase "X" Hammock

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

3.3.7 Negative Lags and Start to Finish Relationships

3.3.8 Calculation Mode

3.3.9 Milestones

3.3.10 Activity Codes and Calendars

3.3.11 Program Settings

3.3.12 Lags

SECTION 01 32 01.00 28

G4EDDRJR

Line

3.3.13 Cost Loading

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Design Package Schedule Submission

3.4.4 Periodic Schedule Updates

3.4.5 Standard Activity Coding Dictionary

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CD's

3.5.2 Narrative Report

3.5.3 Approved Changes Verification

3.5.4 Schedule Reports

3.5.4.1 Activity Report

3.5.4.2 Logic Report

3.5.4.3 Total Float Report

3.5.4.4 Earnings Report by CLIN

3.5.5 Network Diagram

3.5.5.1 Continuous Flow

3.5.5.2 Project Milestone Dates

3.5.5.3 Critical Path

3.5.5.4 Banding

3.5.5.5 S-Curves

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

3.6.1 Update Submission Following Progress Meeting

3.6.2 Status of Activities

3.6.2.1 Start and Finish Dates

3.6.2.2 Remaining Duration

3.6.2.3 Percent Complete

3.6.2.4 Logic Changes

3.6.2.5 Other Changes

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.7.2 Submission Requirements

3.7.3 Additional Submission Requirements

3.8 DIRECTED CHANGES

3.9 WEEKLY PRODUCTION MEETINGS

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

-- End of Section Table of Contents --

SECTION 01 32 01.00 28

SECTION 01 32 01.00 28

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this section 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) Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

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

submittals having an "I" designation are for information only. A designation following the "G" or "I" 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

Qualifications ; G C

Initial Project Schedule ; G C

Periodic Schedule Updates ; G C

1.3 QUALIFICATIONS

Designate and submit for approval 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 have previously developed, created, and maintained at least (2) two electronic schedules for projects similar in nature and complexity to this project and shall be experienced in the use of the scheduling software that meets the requirements of this SPECIFICATION.

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

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

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

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

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.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 an inability of the Contracting Officer to evaluate contract earned value for the purposes of payment. Failure of the Contractor to provide all required information will result in the disapproval of the preliminary, initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on The Schedule.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this SPECIFICATION. Failure of the Contractor to meet the requirements of this SPECIFICATION will result in the disapproval of the schedule. Scheduling software that meets the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 are Primavera Project Planner (P6) by Primavera and Open Plan by Deltek.

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 procurement and non-procurement activities to be accurately determined between schedule update periods. Activity durations shall be broken down to a sufficient level of detail to analyze the critical path, prosecute the work and coordinate related, predecessor and/or successor activities.

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

1. Submission and approval of O&M manuals

2. Submission and approval of Shop drawings

3. Submission and approval of As-built drawings.

4. Contractor Preparation and Submission of all Submittals

5. Government Review Period and Acceptance of all Submittals.

b. Inspections

1. Contractor's pre-final inspection

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

3. Government's pre-final inspection

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

5. Contractor's final inspection

6. Correction of punch list from Contractor's final inspection

7. Government's final inspection

8. Correction of punch list from Government's final inspection

c. Material Procurements

d. All Definable Features of Work

e. Testing and Commissioning Activities

f. Training of Government Personnel

g. Completion dates, constraints and limited work windows as described in Clause 52.211-10 COMMENCEMENT, PROSECUTION, AND COMPLETION OF WORK

(APR 1984)

h. Work sequence specified in SECTION 41 01 20.72 26 BRIDGE CRANE MECHANICAL AND STRUCTURAL MODIFICATION paragraph "General Sequence of Work"

i. Mobilization and Demobilization

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.

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 (FOW)

Assign a Definable Feature of Work Code to appropriate activities based on the definable feature of work to which the activity belongs. An activity shall not have more than one Definable Feature of Work Code. Not all activities are required to be Definable Feature of Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is acknowledged by the Contractor. Schedule activities on a calendar to which the activity logically belongs. Activities may be assigned to a seven (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 (7) 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 (0) 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 two (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.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

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

3.3.4.2 End Phase

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

3.3.4.3 Phase "X" Hammock

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

3.3.5 Default Progress Data Disallowed

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

3.3.6 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.

Propose logic corrections to eliminate all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than two (2) update cycles by logic revision, as approved by the Contracting Officer.

3.3.7 Negative Lags and Start to Finish Relationships

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

3.3.8 Calculation Mode

Schedule calculations shall retain the logic between predecessors and successors even when the successor activity starts and the predecessor activity has not finished. Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") will not be allowed.

3.3.9 Milestones

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

foundation/substructure construction complete; superstructure construction complete; building dry-in or enclosure complete to allow the initiation of finish activities; permanent power complete; and building systems commissioning complete. crane frame, end truck and wheel alignment measurements; submission of crane measurements and alignment recommendations of each crane; end-tie modifications and crack repairs complete; re-measurement of crane frame, end truck and wheel alignments complete; wheel/axle replacement and other necessary end truck modifications, as approved, complete; installation of calibration marker monuments and crane alignment targets; final inspections and testing complete.

3.3.10 Activity Codes and Calendars

Activity Codes and Calendars shall be at the Project Level.

3.3.11 Program Settings

a. Duration Types are to be set to Fixed Duration and Units.

b. Percent Complete types are to be set to Physical.

c. Activity Types are to be set to Task Dependent except for milestone activities which shall be set to Start or Finish Milestone.

d. Critical Activities shall be defined as Longest Path.

e. Time Period Preferences shall be set to 8hr/day, 40 hr/week, 172 hr/month, 2000 hr/yr.

3.3.12 Lags

Lags shall not exceed 5 days. Wherever possible, replace lags with an activity.

3.3.13 Cost Loading

Activities will be cost loaded using a Job Labor Resource. Cost loading shall not be front end loaded.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The reports and network diagrams required for each submission are contained in paragraph

SUBMISSION REQUIREMENTS.

3.4.1 Preliminary Project Schedule Submission

At the Pre-work meeting, provide a hardcopy "Preliminary Project Schedule", defining the Contractor's planned operations at a summary level. Provide an electronic PDF version to the COR the day prior to the Pre-work meeting, to allow time for distribution. The Preliminary Project Schedule shall include NTP, major design activities, major preconstruction submittals (to include APP, EPP, and CQC), mobilization, construction/installation, testing/commissioning, demobilization. The

SECTION 01 32 01.00 28

"Preliminary Project Schedule" may be developed in any format as long as the schedule meets the requirements of this paragraph. All other Project Schedules must be developed on software meeting requirements of paragraph

PROJECT SCHEDULE DETAILED REQUIREMENTS.

3.4.2 Initial Project Schedule Submission

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

3.4.3 Design Package Schedule Submission

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

3.4.4 Periodic Schedule Updates

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

3.4.5 Standard Activity Coding Dictionary

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

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

Field Activity Code Length Description

1 WRKP 3 Workers per Day 2 RESP 4 Responsible Party (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 FOW 30 Feature of Work (Max of 30 characters including spaces)

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 (2) sets of data CD's containing the project schedule in the software format developed from, (PDF file is not acceptable). File medium shall be CD. Label each CD indicating the type of schedule (Initial or Update), full contract number, Data Date and file name. Each schedule shall have a unique file name as determined by the Contractor. Contractor shall also e-mail a copy to the Contracting Officer's Representative.

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 two (2) most critical paths where the total float is less than or equal to 20 work days, a description of current and anticipated problem areas or delaying factors and their impact, and an explanation of corrective actions taken or required to be taken. The Narrative Report is expected to communicate to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis. Identify and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

3.5.3 Approved Changes Verification

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

3.5.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report shall be as directed by the Contracting Officer. Typically reports shall contain: Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission.

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 NTPdate 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 shall be required on the initial schedule submission and on monthly schedule update submissions. 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 network diagram shall be submitted on a single sheet or drawing large enough to provide legible print for the activity number, description of activity, duration of activity, and logic flow arrows for the complete network diagram. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.5.1 Continuous Flow

Diagrams shall show a continuous flow from left to right with no arrows from right to left. The activity number, description, duration, and estimated earned value shall be shown 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 (5) work 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 eight (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 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 four (4) working days after the periodic schedule update meeting, reflecting only those changes made during the previous update meeting.

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 Contracting Officer 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 required due to delays in completion of any activity or group of activities include:

a. Delays beyond the Contractor's control, such as strikes and unusual weather.

b. Delays encountered due to submittals, Government Activities, deliveries or work stoppages which make re-planning the work necessary.

c. Changes required to correct a schedule that does not represent the actual or planned prosecution and progress of the work.

3.7 REQUESTS FOR TIME EXTENSIONS

In the event the Contractor believes it is entitled to an extension of the contract performance period, completion date, or any interim milestone date, furnish the following for a determination by the Contracting Officer: justification, project schedule data, and supporting evidence as the Contracting Officer may deem necessary. Submission of proof of excusable delay, based on revised activity logic, duration, and costs (updated to the specific date that the delay occurred) is a condition precedent to any approvals by the Government. In response to each Request For Proposal issued by the Government, submit a schedule impact analysis demonstrating whether or not the change contemplated by the Government impacts the critical path.

3.7.1 Justification of Delay

The project schedule shall clearly display that the Contractor has used, in full, all the float time available for the work involved with this request. The Contracting Officer's determination as to the number of allowable days of contract extension shall be based upon the project schedule updates in effect for the time period in question, and other factual information. 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.7.2 Submission Requirements

Submit a justification for each request for a change in the contract completion date of less than two (2) weeks based upon the most recent schedule update at the time of the NTP or constructive direction issued for the change. Such a request shall be in accordance with the requirements of other appropriate Contract Clauses and shall include, as a minimum:

a. A list of affected activities, with their associated project schedule activity number.

b. A brief explanation of the causes of the change.

c. An analysis of the overall impact of the changes proposed.

d. A sub-network of the affected area.

Identify activities impacted in each justification for change by a unique activity code contained in the required data file.

3.7.3 Additional Submission Requirements

The Contracting Officer may request an interim update with revised activities for any requested time extension of over two (2) weeks.

Provide this disk within four (4) days of the Contracting Officer's request.

3.8 DIRECTED CHANGES

All changes shall be processed in accordance with FAR 52.243-4, Changes.

If a change is required to be implemented prior to settlement of price and/or time, the Contractor shall submit a proposed schedule revision to the Contracting Officer within 14 calendar days of the Government written change order or the Contractor's written notice under paragraph (b) of FAR 52.243-4, Changes. The proposed revision to the schedule will be approved by the Contracting Officer prior to inclusion of those changes within the project schedule. This submission shall not limit the time period for assertion of rights to a final adjustment to time and/or price under paragraph (e) of FAR 52.243-4, Changes.

3.9 WEEKLY PRODUCTION MEETINGS

a. The Government and the Contractor shall meet weekly (or as otherwise mutually agreed to) 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 three (3) weeks.

The then current and approved schedule update shall be used for the purposes of this meeting and for the production and review of reports. The Contractor's Project Manager and the Contracting Officer shall attend. The weekly production meeting will address the status of RFI's, RFP's and Submittals.

b. The Government and the Contractor shall jointly review the reports. If it appears that activities on the longest path(s) which are currently driving the calculated completion date (driving activities), are not progressing satisfactorily and therefore could jeopardize timely project completion, corrective action must be taken immediately. Corrective action includes but is not limited to:

increasing the number of work crews; increasing the number of work shifts; increasing the number of hours worked per shift; and determining if Government responsibility coded activities require Government corrective action.

3.10 OWNERSHIP OF FLOAT

Float available in the schedule, at any time, shall not be considered for the exclusive use of either the Government or the Contractor.

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

Download and upload the schedule data into the Resident Management System (RMS) prior to RMS databases being transferred to the Government and is considered to be additional supporting data in a form and detail required by the Contracting Officer pursuant to FAR 52.232-5 - Payments under Fixed-Price Construction Contracts. The receipt of a proper payment request pursuant to FAR 52.232-27 - Prompt Payment for Construction Contracts is contingent upon the Government receiving both acceptable and approvable hard copies and electronic export from QCS of the application for progress payment.

-- End of Section --

This page intentionally left blank

SECTION TABLE OF CONTENTS

DIVISION 41 - MATERIAL PROCESSING AND HANDLING EQUIPMENT

SECTION 41 01 20.72 26

BRIDGE CRANE MECHANICAL AND STRUCTURAL MODIFICATION

PART 1 GENERAL

1.1 GENERAL INFORMATION

1.2 REFERENCES

1.3 SUBMITTALS

1.4 DESIGN CRITERIA

1.4.1 General

1.4.2 Unit Stresses

1.4.2.1 Walkways, Ladders and Platforms

1.4.2.2 Bolts

1.4.2.3 Welds

1.4.2.4 Detailing Requirements

1.4.2.5 Mechanical Parts of the Bridge Drive Machinery

1.4.2.6 Stress Concentration Factors

1.4.3 Bolted Connections

1.5 QUALITY ASSURANCE

1.5.1 General

1.5.2 Drawing Index

1.5.3 Drawings

1.5.4 Design Calculations

1.5.4.1 Finite Element Analysis (FEA)

1.5.5 Product Data

1.5.6 Final Approved Versions of Contractor Prepared Drawings

1.5.7 Final Calculations

1.6 OPERATIONS AND MAINTENANCE MANUALS

1.7 SPARE PARTS

PART 2 PRODUCTS

2.1 BRIDGE CRANE WALKWAY GUARDRAILS AND STAIRS MODIFICATION

2.1.1 General

2.1.2 Walkway Guardrails and Stairs

2.2 BRIDGE DRIVE

2.3 MACHINERY EFFICIENCIES

2.4 SPEED REDUCERS

2.4.1 Speed Reducer Rating

2.4.2 Speed Reducer Features

2.4.3 Gear Cases

2.4.3.1 Drain Valves, Plugs and Drip Pans

2.4.4 Speed Reducer Seals

2.4.5 Speed Reducer Lubrication

2.4.6 Speed Reducer Nameplate

2.4.7 Speed Reducer Certified Prints

2.5 ANTI-FRICTION BEARINGS

2.5.1 Speed Reducer Anti-Friction Bearings

2.5.2 Bridge Truck Anti-Friction Bearings

2.5.3 Seals

2.6 KEYS AND KEYSEATS

SECTION 41 01 20.72 26

2.7 SHAFT COUPLINGS

2.7.1 General

2.7.2 Flexible Couplings

2.8 BRIDGE TRUCK EQUALIZER PINS AND BUSHINGS

2.9 WHEELS

2.9.1 Wheel Hardness Testing

2.10 AXLES

2.11 LUBRICATION

2.11.1 General

2.11.2 Speed Reducers

2.11.2.1 New Lubricating Oil

2.11.2.2 Speed Reducer Oil Sampling

2.11.2.3 Speed Reducer Oil Testing

2.11.2.4 New Lubricating Oil Cleanliness

2.11.3 Grease

2.12 CALIBRATION MARKER MONUMENTS AND CRANE ALIGNMENT TARGETS

2.13 ANCHORS FOR CALIBRATION MARKER MONUMENTS

PART 3 EXECUTION

3.1 BRIDGE CRANE MODIFICATIONS

3.1.1 General Background

3.1.2 General Sequence of Work

3.2 CRANE ALIGNMENT MEASUREMENTS

3.2.1 General

3.2.2 Crane Frame, End Truck and Wheel Alignment Measuring Procedure

3.2.2.1 Crane Frame Squareness

3.2.2.2 End Truck, Wheel Alignment and Span

3.2.2.3 Wheel Dimensions

3.2.3 Preliminary Alignment Measurements

3.2.4 Crane Measurement Results and Alignment Recommendation

3.2.5 Post-Modification Alignment Measurements

3.3 END-TIE MODIFICATIONS AND CRACK REPAIR

3.4 END TRUCK MODIFICATIONS

3.4.1 Bridge Drive Trucks

3.4.2 Bridge Idler Trucks

3.4.3 Bridge Truck Equalizer Pins and Bushings

3.4.4 Equalizer Pin Line Boring (Optional)

3.4.5 Crane Jacking Procedure For Removal of End Trucks

3.5 CALIBRATION MARKER MONUMENTS AND CRANE ALIGNMENT TARGETS

3.5.1 General

3.5.2 Installation Details

3.5.3 Crane Squaring Procedure

3.6 CRANE END STOPS

3.7 TIGHTENING OF FASTENERS

3.8 CLEANUP

-- End of Section Table of Contents --

SECTION 41 01 20.72 26

SECTION 41 01 20.72 26

BRIDGE CRANE MECHANICAL AND STRUCTURAL MODIFICATION

PART 1 GENERAL

1.1 GENERAL INFORMATION

This SECTION covers the mechanical and structural work for the modifications of the two (2) 350-ton powerhouse bridge cranes at McNary Lock and Dam. The Contractor shall engineer and design modifications and submit computations and drawings as stated in paragraph SUBMITTALS below.

Furnish detailed shop drawings showing all details required to perform the modification work.

1.2 REFERENCES

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

AMERICAN BEARING MANUFACTURERS ASSOCIATION (ABMA)

ABMA 8.2 (1999) Ball and Roller Bearing Mounting Accessories, Inch Design

ABMA 19.1 (1987; R 1999) Tapered Roller Bearings - Radial Metric Design

ABMA 19.2 (1994; R 1999) Tapered Roller Bearings - Radial Inch Design

ABMA 20 (1996) Radial Bearings of Ball, Cylindrical Roller and Spherical Roller Types Metric Design

AMERICAN GEAR MANUFACTURERS ASSOCIATION (AGMA)

AGMA 6001 (2008e; R 2014) Design and Selection of Components for Enclosed Gear Drives

AGMA 6013 (2006a; r 2011) Standard for Industrial Enclosed Gear Drives

AGMA 9005 (2002e; R 2013) Industrial Gear Lubrication

AMERICAN INSTITUTE OF STEEL CONSTRUCTION (AISC)

AISC 316 (1989) ASD Manual of Steel Construction

AMERICAN WELDING SOCIETY (AWS)

AWS D1.1/D1.1M (2010; Errata 2011) Structural Welding Code - Steel

ASME INTERNATIONAL (ASME)

ASME B4.1 (1967; R 2009) Preferred Limits and Fits for Cylindrical Parts

ASME B17.1 (1967; R 2003) Keys and Keyseats

ASTM INTERNATIONAL (ASTM)

ASTM A 504/A 504M (2008) Standard Specification for Wrought Carbon Steel Wheels

ASTM A 307 (2010) Standard Specification for Carbon Steel Bolts and Studs, 60,000 psi Tensile Strength

ASTM A 325 (2010) Standard Specification for Structural Bolts, Steel, Heat Treated, 120/105 ksi Minimum Tensile Strength

ASTM A 434 (2006) Standard Specification for Steel Bars, Alloy, Hot-Wrought or cold-Finished, Quenched and Tempered

ASTM A 490 (2012) Standard Specification for Structural Bolts, Alloy Steel, Heat Treated, 150 ksi Minimum Tensile Strength

ASTM D 445 (2006) Standard Test Method for Kinematic Viscosity of Transparent and Opaque Liquids (and the Calculation of Dynamic Viscosity)

ASTM D 664 (2007) Standard Test Method for Acid Number of Petroleum Products by Potentiometric Titration

ASTM D 2509 (2003; R 2008) Standard Test Method for Measurement of Load-Carrying Capacity of Lubricating Grease (Timken Method)

ASTM D 4057 (2006) Standard Practice for Manual Sampling of Petroleum and Petroleum Products

ASTM D 4950 (2008) Standard Classification and Specification for Automotive Service Greases

ASTM D 5185 Determination of Additive Elements, Wear Metals, and Contaminants in Used Lubricating Oils and Determination of Selected Elements in Base Oils by Inductively Coupled Plasma Atomic Emission Spectrometry (ICP-AES)

ASTM D 6304 (2007) Standard Test Method for Determination of Water in Petroleum Products, Lubricating Oils, and Additives by Coulometric Karl Fischer Titration

ASSOCIATION FOR IRON AND STEEL TECHNOLOGY (AIST)

TR-06 (2005) Specifications for Electric Overhead Traveling Cranes for Steel Mill Service

CRANE MANUFACTURERS ASSOCIATION OF AMERICA (CMAA)

CMAA 70 (2010) Top Running and Bridge and Gantry Type Multiple Girder Electric Overhead Traveling Cranes, No. 70

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO)

ISO 4406 (1999) Hydraulic Fluid Power - Fluids - Method for Coding the Level of Contamination by Solid Particles - Second Edition

ISO 11171 (1999; Corrigendum 1 2001) Hydraulic Fluid Power - Calibration of Automatic Particle Counters for Liquids - First Edition

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.3 SUBMITTALS

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

submittals having an "I" designation are for information only. A designation following the "G" or "I" designation identifies the office that will review the submittal for the Government. The submittals listed in the below Articles shall be submitted within the timeframes specified in this SECTION. The Contractor is responsible for reviewing paragraph

3.1.2 GENERAL SEQUENCE OF WORK and submitting within the specified timeframes. Submit the following in accordance with SECTION 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Crane Frame, End Truck and Wheel Alignment Measuring Procedure ; G

HDC

North Crane Measurement Results and Alignment Recommendation ; G HDC

South Crane Measurement Results and Alignment Recommendation ; G HDC

North Crane Existing Wheel Dimensions (FIO-071) ; I HDC

South Crane Existing Wheel Dimensions (FIO-071) ; I HDC

Crane Jacking Procedure ; G HDC

Speed Reducer Manufacturer Installation Instructions ; I HDC

Speed Reducer Oil Sampling and Test Plan ; I HDC

Crane Wheel Hardness Testing/Reporting Plan ; I HDC

Equalizer Pin Line Boring Procedure ; I HDC

SD-02 Shop Drawings In accordance with paragraph QUALITY ASSURANCE.

North Crane Arrangement Drawings ; G HDC

South Crane Arrangement Drawings ; G HDC

North Crane Detailed Drawings ; G HDC

South Crane Detailed Drawings ; G HDC

SD-03 Product Data In accordance with paragraph PRODUCT DATA.

Anti-Friction Bearings ; G HDC

Seals ; I HDC

Wheels ; G HDC

Shaft Couplings ; I HDC

Bridge Truck Equalizer Pins and Bushings ; G HDC

Lubrication ; I HDC

Speed Reducers ; G HDC

Speed Reducer Certified Prints ; G HDC

Anchors for Calibration Marker Monuments ; G HDC

SD-05 Design Data

Design Calculations ; G HDC

Final Calculations ; G HDC

North Crane Axle and Wheel As-Machined Final Dimensions ; G HDC

South Crane Axle and Wheel As-Machined Final Dimensions ; G HDC

Bolt Tension Chart ; I HDC

SD-06 Test Reports

North Crane Wheel Hardness Test Report ; G HDC

South Crane Wheel Hardness Test Report ; G HDC

North Crane Oil Test Results (New Oil Delivery) ; I HDC

South Crane Oil Test Results (New Oil Delivery) ; I HDC

North Crane Equalizer Pin/Bushing Inspection Report ; G HDC

South Crane Equalizer Pin/Bushing Inspection Report ; G HDC

North Crane Post-Modification Alignment Report ; G HDC

South Crane Post-Modification Alignment Report ; G HDC

SD-07 Certificates

Registered Professional Engineer ; I HDC

Hardness Testing Instrument Calibration Certification ; I HDC

North Crane Wheel Axle Material Certification ; I HDC

South Crane Wheel Axle Material Certification ; I HDC

SD-08 Manufacturer's Instructions

Crane Squaring Procedure ; G HDC

1.4…