Specifications - FE Walter Bridge W912BU25B0007 - 10 Dec 2024.pdf

RFP W912BU25R0019

US Army Corps of Engineers

Philadelphia District

Francis E. Walter Dam Service Bridge Repairs

Francis E. Walter Dam, Lehigh River, Pennsylvania

Construction Solicitation and Specifications

RTA

10 DECEMBER 2024

RTA

10 DECEMBER 2024

INVITATION NO. W912BU25R0019

PHILADELPHIA DISTRICT

CORPS OF ENGINEERS

Request for Proposal

FRANCIS E. WALTER DAM SERVICE BRIDGE REPAIRS

FRANCIS E. WALTER DAM

LEHIGH RIVER, PENNSYLVANIA

I. NOTE THE AFFIRMATIVE ACTION REQUIREMENT OF THE EQUAL OPPORTUNITY CLAUSE

WHICH MAY APPLY TO THE CONTRACT RESULTING FROM THIS SOLICITATION.

II. BIDDERS ARE REQUIRED TO COMPLETE THE REPRESENTATIONS AND CERTIFICATIONS

PORTION OF SECTION 00 45 00 OF THIS SOLICITATION AND SUBMIT THIS WITH THEIR

PROPOSAL.

00 10 00-3

BIDDING SCHEDULE

(To be attached to SF 1442)

Item Estimated Unit Estimated

No. Description Quantity Unit Price Amount_____

1. Bearing Repairs 1 JOB LS $___________

2. Concrete Spall Repairs 96 SF $_______ $___________

3. Epoxy Bridge Deck

Overlay with Aggregate 3823 SF $_______ $___________

TOTAL ESTIMATED BID AMOUNT $______________

NOTE: Offerors must bid on all items.

Francis E. Walter Dam Service Bridge Overlay and Repairs RFP W912BU25R0019

SECTION 00 50 05

PRE-AWARD SURVEY SUBMITTAL REQUIREMENTS

PART 1 GENERAL

1.1 AWARD CRITERIA

Award of this Contract will be made as a whole to the lowest responsive and responsible Bidder whose bid conforms to all requirements of the specifications. Subsequent to the bid opening, the apparent low Bidder shall submit Pre-Award Survey Information that demonstrates compliance with the requirements set forth in this section as a precondition to receiving award.

1.2 GENERAL PRE-AWARD SURVEY INFORMATION

Complete the pre-award survey information sheets attached to this section, and submit to the Contracting Officer within 5 calendar days after bid opening.

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION (Not Applicable)

-- End of Section --

DOCUMENT 00 50 05 Page 1

US ARMY CORPS OF ENGINEERS

PHILADELPHIA DISTRICT

PRE-AWARD SURVEY

A. GENERAL INFORMATION

1) Name of Firm: ___________________________________________________________________

Address: __________________________________________________________________________

Phone: _____________________________________ Fax:__________________________________

Email: ____________________________________________________________________________

CAGE CODE:

If your company has more than one CAGE Code, please list all that apply.

2) Location where accounts are kept (if different than item 1 above): ____________________________

3) Type of Firm (Please check one):

Sole Proprietorship [ ] Partnership [ ] Corporation [ ] Joint Venture [ ] Other

Date Organized: ____________________________________

Date Incorporated: __________________________________

State of Incorporation: _______________________________

4) Attach list of Name of Officers.

Please check "Yes" or "No" for each of the following:

Have current officers of your firm ever been indicted? Yes [ ] No [ ]

Are any of your officers currently under indictment? Yes [ ] No [ ]

If you have answered "Yes" to either of the above, please attach an explanation.

5) Has your firm been terminated for default on any contracts in the past six years? Yes [ ] No [ ] (If yes, please attach an explanation)

00 50 05 Page 2

B. PROPOSED SCHEDULE

Submit a preliminary schedule depicting your project plan from start to final completion. The schedule you submit will be used to determine your ability to successfully perform the project within the time frame stated in the specifications.

IAW FAR 52.236-15, Schedules for Construction Contracts, you will be required to submit a fully loaded schedule within five days after work commences on the awarded contract.

C. PERFORMANCE AND PAYMENT BOND INFORMATION

1) Performance & Payment Bonds will be furnished by:

Name of Company: _______________________________________________________________

Phone No: _____________________________________________________________________

2) Firm's bonding capacity as authorized by your Insurance Company:

Single Project: ___________________________________________________________________

Aggregate Basis: _________________________________________________________________

D. BANKING INFORMATION

Name of Bank: ___________________________________________________________________

Address: ________________________________________________________________________

Account Representative: ____________________________________________________________

Phone No: ________________________________ E-mail: _______________________________

Authorized Credit Line: ________________________________________________

If additional banks are utilized, please provide this information for each.

E. INSURANCE INFORMATION

Name of Insurance Company: ______________________________________________________

Type of Insurance Provided: _______________________________________________________

Insurance Agency: _______________________________________________________________

Address: _______________________________________________________________________

Agent: _________________________________________________________________________

Phone No: ______________________________ Email: _________________________________

If more than one insurance company is utilized, please provide this formation for each.

00 50 05 Page 3

F. FINANCIAL DATA

Please provide the last two certified public accountant's financial statements.

G. SAFETYDATA

Please check "Yes" or "No" for each of the following:

1. Does your firm have a Standard Operating Procedure for Safety?

Yes [ ] No [ ] If yes, please provide a copy.

Does your firm have a Policy Letter dealing with Safety?

Yes [ ] No [ ] If yes, please provide a copy.

2. What was your accident rate for last year? _____________________

3. What is your accident rate to date for this year? ____________________

H. QUALITY CONTROL DATA

Please check "Yes" or "No" for each of the following:

1. Does your firm have a Standard Operating Procedure for Quality Control?

Yes [ ] No [ ] If yes, please provide a copy.

2. Does your firm have a Policy Letter dealing with Quality Control?

Yes [ ] No [ ] If yes, please provide a copy.

I. EQUIPMENT DATA

Please provide the following data for each piece of construction equipment (including equipment you will rent or lease), intended to be used on the project. Do not include consumables.

Make Year Mfg.

Description Purchase Price (if equipment is owned) Size Book Value (if equipment is owned) Model Number Unpaid Balance (if equipment is owned)

J. EXPERIENCE DATA

1. Please provide the following data for all major projects in progress or completed with the past three years.

Also, provide the same data for Corps of Engineer projects completed within the last five years. Those projects containing work similar in nature to that involved under this solicitation are to marked with an asterisk (*).

Name and Address of Owner Point of Contact and Telephone Number Project Location Type of Work performed by your firm Indicate whether you performed as a prime or subcontractor Name of Architect/Engineer in charge for Owner Address of Architect/Engineer Contract or Subcontract Amount Approximate date completed or, if not completed provide percent complete

00 50 05 Page 4

Were time extensions necessary? Were penalties imposed? Were liens, claims or stop work orders filed?

2. How many years have you been in business as a contractor? ________________________________

3. How many years experience in the type of work involved in the subject solicitation do you have

a) as prime contractor? ___________________________________

b) as a subcontractor? ___________________________________

K. KEY PROJECT PERSONNEL

Please provide resumes for each of the following key personnel to be assigned to this project:

Project Engineer, Superintendent, Quality Control Manager/Technician, Safety Technician, Office Engineer

(Signature of Person Supplying Data)

(Print or Type Name and Title of Person Supplying Data)

(Phone No.)

(Email Address)

00 50 05 Page 5

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 QUALITY CONTROL

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

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 60 00 WORK ACCESS PLATFORM

01 78 00 CLOSEOUT SUBMITTALS

DIVISION 03 - CONCRETE

03 01 32 CONCRETE REHABILITATION

DIVISION 05 - METALS

05 12 10 BEARING REPAIRS

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 12 36 EPOXY BRIDGE DECK OVERLAY WITH AGGREGATE

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The major items of work to be performed under the Base Bid include, but are not limited to the following; resetting rocker bearings at Pier 2, repairing bearing anchor bolts at Pier 1, lubricating all bearing pins, repairing concrete areas with spalling or delamination, and installing an epoxy overlay on the bridge deck.

1.1.2 Location

The work is located at the Francis E. Walter Dam.

The Francis E. Walter Dam is located on the Lehigh River in White Haven, Pennsylvania.

1.2 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches.

1.3 EXISTING WORK

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

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

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

1.4 DELIVERY OF MATERIAL

1.4.1 Delivery Schedule

Notify the Contracting Officer's Representative (COR) in writing at least 14 calendar days in advance of the date on which the materials and equipment will be delivered to each site.

1.4.2 Delivery Locations

After coordination with the Contracting Officers Representative (COR), when ready for delivery, the Contractor shall pick up, transport, deliver, and

SECTION 01 11 00 Page 1 off-load the fabrications at the following location: Francis E. Walter Dam:

146 Walter Dam Road, White Haven, PA 18661. COR will provide precise locaiton of delivery.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 11 00 Page 2

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

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)

EM 385-1-1 (2024) Safety -- Safety and Occupational Health (SOH) Requirements

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

Progress and Completion Pictures; G Evidence Of Insurance

1.3 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

1.4 SUPERVISION

1.4.1 Superintendent Qualifications

Provide project superintendent with a minimum of 10 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as

SECTION 01 30 00 Page 1 for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

1.4.2 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of Contract work.In addition, if a Quality Control (QC) representative is required on the Contract, then that individual must also have fluent English communication skills.

1.4.3 Duties

The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.4.4 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion. Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.5 PRECONSTRUCTION CONFERENCE

Immediately 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 of prices or earned value report, shop drawings, and other submittals, scheduling programming, prosecution of the work, clear expectations of the "Interim DD Form 1354" Submittal, and the processes for joint risk management between the Contractor and Government. Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

1.6 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 of or conclusion drawn from the data or information by the Contractor. (FAR 52.236-4)

a. The indications of physical conditions on the drawings and in the specifications are based on as-built record drawings and field inspections.

b. Weather Conditions. The climate of the area is referred to as "continental" by climatologists, characterized by cold winters and moderately hot summers. Complete weather records and reports may be obtained from the local U.S. Weather Bureau Office nearest to the work

SECTION 01 30 00 Page 2 site. The Contractor shall satisfy himself as to the hazards likely to arise from weather conditions during the construction period.

c. Transportation Facilities.

(1) The Francis E. Walter Dam is located on the Lehigh River in White Haven, Pennsylvania. The main access to the project is located off of Pennsylvania State Route 940, approximately 1 mile east of the Pocono Interchange (Exit 95) on the Northeast Extension of the Pennsylvania Turnpike.

(2) The Contractor is responsible for all investigations of load carrying capacities of bridges and roadways. Contractor is responsible for the repair of damage to roads caused by construction operations.

d. The Contractor will be permitted to work between 0630 and 1530 daily, Monday through Friday, excluding federal legal holidays as outlined by Public Law Number 98-144. Federal holidays that fall within the work week will not be considered as work days. Prior to performing any work during hours other than those specified, the Contractor shall submit an overtime request to the Contracting Officer for review and approval. Overtime requests shall be submitted not less than 24 hours prior to the time the Contractor desires to perform the overtime work. The Contractor shall provide at least a 24 hour advanced notification to establish when on-site work will commence and prior to restarting on-site work following any stoppage of work lasting longer than five normal workdays. Notification shall be provided by phone, or person, or in writing, and shall be given directly to the Contracting Officer.

e. Magnitude of the Contract Work. The estimated value of the contract work is between $500,000 and $1,000,000.

1.7 CERTIFICATES OF COMPLIANCE

Any certificates required for demonstrating proof of compliance of materials with specifications requirements shall be executed in triplicate copies. Each certificate shall be signed by an official authorized to certify on behalf of the manufacturing company and shall contain the name and address of the Contractor, the project name and location, and the quantity and date or dates of shipment or delivery to which the certificates apply. Copies of laboratory test reports submitted with certificates shall contain the name and address of the testing laboratory and the date or dates of the tests to which the report applies.

Certification shall not be construed as relieving the Contractor from furnishing satisfactory material, if, after tests are performed on selected samples, the material is found not to meet the specific requirements.

(CENAP)

1.8 PERFORMANCE EVALUATION OF CONTRACTOR (MAR 2014)

a. As a minimum, the Contractor's performance will be evaluated upon final acceptance of the work for contracts less than one year in duration.

Contracts in excess of one year will receive at a minimum, an annual interim evaluation in addition to the final evaluation. However, interim evaluation may be prepared at any time during contract performance when determined to be in the best interest of the Government. The evaluation will be entered into the Contractor Performance Assessment Reporting System

(CPARS).

SECTION 01 30 00 Page 3

b. CPARS is a web-enabled application that supports the completion, distribution, and retrieval of construction contract performance evaluations. CPARS is for UNCLASSIFIED use only. An evaluation assesses Contractor performance and provides a record, both positive and negative, on a given contract. Each evaluation is based on objective facts and supported by contract management data, such as contract performance elements that evaluate quality, timely performance, effectiveness of management, and compliance with contract terms, labor standards, and safety requirements. The Contractor will be rated either outstanding, above average, satisfactory, marginal, or unsatisfactory in the areas of Contractor Quality Control, Timely Performance, Effectiveness of Management, Compliance with Labor Standards, and Compliance with Safety Standards. The Contractor will be advised of any unsatisfactory rating, either in an individual element or in the overall rating, prior to completing the evaluation, and all Contractor comments will be made a part of the official record. Performance Evaluation Reports will be available to all DOD Contracting offices for their future use in determining Contractor responsibility, in compliance with ER 415-1-17.

c. Upon successful award of the contract, the Contractor will be notified by CPARS via email that access has been granted to a contract within the system. The email will contain instructions of how to log into the system.

(CENAP)

1.9 INSURANCE REQUIREMENTS

Evidence of Insurance: Evidence of the following insurance shall be submitted to the Contracting Officer prior to commencement of work.

Insurance shall be maintained throughout the period of performance:

a. General Liability Insurance (Comprehensive form of policy): Bodily Injury Liability - $500,000 per occurrence.

b. Automobile Liability Insurance (Comprehensive form of policy): Bodily Injury Liability - $200,000 per person and $500,000 per accident. Property Damage Liability - $20,000 per accident.

c. Workmen's Compensation and Employer's Liability Insurance: Compliance with applicable workmen's compensation and occupational disease statutes is required. Employer's liability coverage in the minimum amount of $100,000 is also required."

1.10 PARTNERING

To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.

1.10.1 Team-Led (Informal) Partnering

a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be

SECTION 01 30 00 Page 4 co-led by the Government Construction Manager and Contractor's Project Manager.

b. The Initial Team-led Partnering session may be held concurrently with the Pre-Construction meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.

c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.

d. The Partners will determine the frequency of the follow-on sessions.

e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.

1.11 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after contract award, 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 or terrorist threats.

Multiple email addresses are 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). Promptly notify the Contracting Officer, in writing, of any changes to this email address.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.1 MEASUREMENT AND PAYMENT

No separate measurement or payment will be made for the work specified in this section and all costs in connection therewith shall be included in the costs of all the bid items.

SECTION 01 30 00 Page 5

SECTION 01 32 01

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (2017) Administration -- Project Schedules

1.2 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G,DO Preliminary Project Schedule; G,DO Initial Project Schedule; G,DO Periodic Schedule Update; G,DO

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

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

SECTION 01 32 01 Page 1

2.1.1 Government Default Software

The Government intends to use Primavera P6.

2.1.2 Contractor Software

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

2.1.2.1 Primavera

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

2.1.2.2 Other Than Primavera

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

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of work is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

3.2.1 Activity Cost Loading

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

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

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and

SECTION 01 32 01 Page 2 subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

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

3.3.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.4 Mandatory Tasks

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

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

b. Contractor's pre-final inspection.

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

d. Government's pre-final inspection.

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

f. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

SECTION 01 32 01 Page 3

3.3.6 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site:

http://rms.usace.army.mil.

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.3.6.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.6.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot 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

SECTION 01 32 01 Page 4 subcontractor); and GOVT (for USACE).

3.3.6.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

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

3.3.6.4 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.6.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

3.3.6.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and construction phase. Each activity can have only one Phase of Work code.

a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.

b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.3.6.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.3.6.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 00 QUALITY CONTROL.

SECTION 01 32 01 Page 5

An activity can have only one Feature of Work Code.

3.3.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

3.3.7.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

3.3.7.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project."

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.7.3 Interim Completion Dates and Constraints

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

3.3.7.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.3.7.3.2 End Phase

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

3.3.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs.

Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop Seasonal Calendar(s) and assign to seasonally affected activities as applicable.

SECTION 01 32 01 Page 6

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

3.3.9 Open Ended Logic

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

Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's approval.

3.3.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.3.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer. Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.3.13 Original Durations

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

3.3.14 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

SECTION 01 32 01 Page 7

b. Start to Finish (SF) relationships are prohibited.

3.3.15 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.3.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.

3.3.17 Remaining Duration

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

3.3.18 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

3.3.18.1 As-Built Drawings

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

3.3.19 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

SECTION 01 32 01 Page 8

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

Review comments made by the Government on the schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents.

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval at the preconstruction meeting. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

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

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

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

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

SECTION 01 32 01 Page 9

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 Electronic Scheduling Data

Provide electronic scheduling data containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include the Narrative Report and all required Schedule Reports. The electronic file must identify the type of schedule (Preliminary, Initial, Update), full contract number, Data Date, and file name. Each schedule must have a unique file name and use project specific settings.

3.5.2 Narrative Report

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

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

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

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

d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.

e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

f. Identify and discuss out-of-sequence work.

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format. Provide 2 set(s) of hardcopy reports. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

SECTION 01 32 01 Page 10

3.5.3.2 Logic Report

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

3.5.3.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.5.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

Provide a Scheduling/Leveling…