REV Part 1 - BCD Bulkhead_RTA DB RFP 25NOV2025.pdf

US Army Corps of Engineers New York District

National Park Service (NPS) Bulkhead

Repair

Jacob Riis Park

Queens, New York

Part 2 – General Requirements

Design Build

Amendment # 02

Final DB RFP – November 2025

THIS PAGE INTENTIONALLY LEFT BLANK

NPS Beach Channel Drive (BCD) Bulkhead NPSBCDBULKHEAD Amendment 01 11/19/25

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 02/24 SUMMARY OF WORK

01 14 00 11/22, CHG 2: 05/24 WORK RESTRICTIONS

01 30 00 11/20, CHG 3: 08/23 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 08/23 PROJECT SCHEDULE

01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES

01 33 10.00 18 03/25 ENGINEERING CONSIDERATIONS AND

INSTRUCTIONS FOR FIELD PERSONNEL

(ECIFP)

01 33 16.00 10 05/16 DESIGN DATA (DESIGN AFTER AWARD)

01 35 26 05/24 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 05/24 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 08/23, CHG 1: 05/24 QUALITY CONTROL

01 45 00.15 10 11/23 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 50 00 11/20, CHG 2: 08/22 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 08/22 TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00 08/19, CHG 5: 08/22 PROJECT IDENTIFICATION

01 74 19 02/19, CHG 3: 11/21 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

01 78 00 05/19, CHG 1: 08/21 CLOSEOUT SUBMITTALS

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION 01 11 00

SUMMARY OF WORK

02/24

PART 1 GENERAL

1.1 FAR 52.211-10, COMMENCEMENT, PROSECUTION AND COMPLETION OF WORK

a. The Contractor must be required to (i) commence work under this contract within five (5) calendar days after the date the Contractor receives the Notice to Proceed, (ii) prosecute the work diligently, and (iii) complete the entire work ready for use, before 1600 calendar days. The date stated for completion must include final cleanup of the premises. (FAR 52.212-3)

b. The Contractor must furnish all labor, materials, equipment, and services for the following work as described in the construction documents.

c. All work must be in accordance with the drawings and specifications or instructions attached hereto and made a part thereof, or to be furnished hereafter by the Contracting Officer and subject, in every detail, to his supervision, direction, and instructions.

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes bulkhead replacement, repaving, repair and replace exisiting reinforced concrete storm drain pipes and any additional work as indicated in the DB RFP.

1.2.2 Location

The work is located at the Gateway National Recreation Area, Queens, NY, approximately as indicated in DB RFP. The exact location will be shown by the Contracting Officer.

1.2.2.1 DFARS 236.204, DISCLOSURE OF THE MAGNITUDE OF CONSTRUCTION PROJECTS

This project is estimated between $25,000,000.00 and $100,000,000.00

1.3 EXISTING WORK

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

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.

At Contractor's own expense, immediately restore to service and repair any damage caused by Contractor's workmen to the existing piping and conduits, wires, cables, etc., of utility services or of fire protection systems and

SECTION 01 11 00 Page 1 communications systems (including telephone). Provide immediate notification to the Contracting Officer and verbalize the planned procedures to restore the damaged system. Immediately assemble personnel, equipment and material necessary to restore. Compliance with Contract Documents for quality installation must be included. The work must proceed at 24-hours per day until satisfactorily restored service is achieved.

The approval to perform repairs during normal working hours requires the contractor to request this in writing. The contractor's request shall include the specific procedures that will be needed to make the repair.

The request to perform repairs during normal working hours requires Contractor's written approval. The write up of procedures to repair must be submitted to Contracting Officer.

Repair any damage to those facilities, including those that are the property of a third party, resulting from failure to comply with the requirements of this contract or failure to exercise reasonable care in performing the work. If the Contractor fails or refuses to repair the damage promptly, the Contracting Officer may have the necessary work performed and charge the cost to the Contractor.

1.4 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.

Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.

Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities are discovered. Verify the elevations of existing piping, utilities,and any type of underground or encased obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.

1.4.1 Notification Prior to Excavation

Notify the Contracting Officer at least 15 days prior to starting excavation work.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

11/22, CHG 2: 05/24

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" 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

List of Contact Personnel

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear appropriate personal protective equipment (PPE) in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Ensure all Contractor equipment, include delivery vehicles, are clearly identified with their company name.

1.2.1.1 Subcontractors and Personnel Contacts

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

1.2.1.2 No Smoking Policy

Smoking is prohibited within the project site, except in designated smoking areas. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

1.2.2 Working Hours

Regular working hours will consist of an 8 1/2 hour period , between 7 a.m. and 3:30 p.m., Monday through Friday, excluding Government holidays.

1.2.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, SECTION 01 14 00 Page 1 the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

1.2.4 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in paragraph WORK OUTSIDE REGULAR HOURS.

b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.

c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, are considered utility cutovers pursuant to the paragraph WORK OUTSIDE REGULAR HOURS. Such interruptions are further limited to 4 hours. This time limit includes time for deactivation and reactivation.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 2

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/20, CHG 3: 08/23

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 Health Requirements

1.2 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" 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

View Location Map

Progress and Completion Pictures

1.3 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.4 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 different viewpoints selected by the Contractor unless otherwise directed by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, cumulative of all photos to date electronically. 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 as a digital file.

Include a date designator in file names. Photographs provided are for unrestricted use by the Government.

Refer to section 01 33 00 SUBMITTAL PROCEDURES, Electronic File Format paragraph for information on electronic file format for submission.

SECTION 01 30 00 Page 1

1.5 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by New York State law.

a. Procure and maintain during the entire period of project performance under this contract the following insurance policies:

(1) Commercial General Liability Insurance as required by FAR 28.307-2

(2) The policies must be endorsed (i) to include National Park Service (NPS),the New York State Department of Environmental Conservation (NYSDEC), Queens County and the United States of America as additional insured and (ii) to provide that notice of an occurrence to the insurance company from any insured will serve as notice from all insured.

(3) Comprehensive Automobile Liability Insurance as required by FAR 28.307-2

(4) Certificates of Insurance evidencing the issuance of all insurance required hereby, and guaranteeing at least thirty (30) days prior notice to the Government of cancellation or non-renewal, must be delivered to the Contracting Officer, NPS and NYSDEC prior to entry of the Government's Contractors upon the project area, or, in the case of new or renewal policies replacing any policies expiring during the period, no later than thirty (30) days before the expiration dates of such expiring policies.

b. Prior to the commencement of work hereunder, provide to the Contracting Officer a certificate or statement of the above required insurance. The policies evidencing required insurance must contain an endorsement to the effect that cancellation or any material change in the policies adversely affecting the interests of the Government in such insurance must not be effective for such a period as may be prescribed by the laws of the State in which this contract is to be performed and in no event less than thirty (30) days after written notice thereof to the Contracting Officer.

c. This insurance will be included at no additional cost to the government.

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

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

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

The following resources are available to assist USACE Contractors in their outreach efforts:

SECTION 01 30 00 Page 2

Federal Veteran employment information at http://www.fedshirevets.gov/index.aspx Department of Labor Veterans Employment Assistance https://www.dol.gov/vets/ Department of Veterans Affairs-VOW to Hire Heroes Act http://benefits.va.gov/vow/ Army Wounded Warrior Program-http://wtc.army.mil/modules/employers/index.html U.S. Chamber of Commerce Foundation-Hiring Our Heroes http://www.hiringourheroes.org /

1.7 SUPERVISION

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

For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

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

SECTION 01 30 00 Page 3

1.8 PRECONSTRUCTION CONFERENCE

Immediately after award , prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction Conference . The conference must take place within 35 calendar days after award of the contract, but prior to commencement of any work at the site. The purpose of this conference is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to: daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out.

Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

The Contractor must provide at this conference the following items as indicated:

a. Initial Project Schedule; Section 01 32 01.00 10 PROJECT SCHEDULE.

b. Accident Prevention Plan (APP); Section 01 35 26 GOVERNMENTAL SAFETY

REQUIREMENTS.

c. Contractor Quality Control (CQC) Plan; Section 01 45 00 QUALITY

CONTROL.

d. List of Contact Personnel; Section 01 14 00 WORK RESTRICTIONS.

e. Letter appointing Superintendent.

1.8.1 Attendees

Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

1.9 SUBMISSION OF CLAIMS

The following must be submitted to the Contracting Officer at the following address: U.S. Army Corps of Engineers, Room 16-300, New York District, 26 Federal Plaza, New York, New York 10278-0090:

a. Claims referencing or mentioning the Contracting Disputes Act of 1978.

b. Requests for a written decision by the Contracting Officer.

c. Claims certified in accordance with the Contract Disputes Act of 1978.

No other Government representative is authorized to accept such requests.

A copy must also be provided to the Authorized Representative of the Contracting Officer.

Provide the Contracting Officer with a copy of any requests for additional time, money or interpretation of contract requirements which were provided to the Authorized Representative of the Contracting Officer and which have not been resolved after 90 days.

SECTION 01 30 00 Page 4

1.10 (S-102) CONTRACTOR SUPPLY and USE OF ELECTRONIC SOFTWARE FOR PROCESSING DAVIS-BACON ACT CERTIFIED LABOR PAYROLLS (April 2011)

The Contractor is encouraged to use a commercially-available electronic system to process and submit certified payrolls electronically to the Government. The requirements for preparing, processing and providing certified labor payrolls are established by the Davis-Bacon Act as stated in FAR 52.222-8, PAYROLLS AND BASIC RECORDS and FAR 52.222-13, COMPLIANCE

WITH DAVIS-BACON AND RELATED ACT REGULATIONS.

If the Contractor elects to use an electronic Davis-Bacon payroll processing system, then the Contractor must be responsible for obtaining and providing for all access, licenses, and other services required to provide for receipt, processing, certifying, electronically transmitting to the Government, and storing weekly payrolls and other data required for the Contractor to comply with Davis-Bacon and related Act regulations.

When the Contractor uses an electronic Davis-Bacon payroll system, the electronic payroll service shall be used by the Contractor to prepare, process, and maintain the relevant payrolls and basic records during all work under this construction contract and the electronic payroll service must be capable of preserving these payrolls and related basic records for the required three years after contract completion. If the Contractor chooses to use an electronic Davis-Bacon payroll system, then the Contractor must obtain and provide electronic system access to the Government, as required to comply with the Davis-Bacon and related Act regulations over the duration of this construction contract. The access must include electronic review access by the Government contract administration office to the electronic payroll processing system used by the Contractor.

The Contractor's provision and use of an electronic payroll processing system must meet the following basic functional criteria: Commercially available; compliant with appropriate Davis Bacon Act payroll provisions in the FAR; able to accommodate the required numbers of employees and subcontractors planned to be employed under the contract; demonstrated security of data and data entry rights; ability to produce Contractor-certified electronic versions of weekly payroll data; ability to identify erroneous entries and track the data/time of all versions of the certified Davis Bacon payrolls submitted to the Government over the life of the contract; capable of generating a durable record copy, that is, a CD or DVD and PDF file record of data from the system database at end of the contract closeout. This durable record copy of data from the electronic Davis-Bacon payroll processing system must be provided to the Government during contract closeout.

All Contractor-incurred costs related to the Contractor's provision and use of an electronic payroll processing service must be included in the Contractor's price for the overall work under the contract. The costs for Davis-Bacon Act compliance using electronic payroll processing services must not be a separately bid/proposed or reimbursed item under this contract.

1.11 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

SECTION 01 30 00 Page 5 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.11.1 Facilitated (Formal) Partnering

a. Within 35 calendar days after award and prior to the start of work, host a Formal Partnering session with key personnel from the project team including both Contractor and Government personnel. All costs associated with the Partnering session including the third-party independent Facilitator Consultant, meeting room and other incidental items are the responsibility of the Contractor.

b. Before the Facilitated (Formal) Partnering session, coordinate with the Facilitator all requirements for incidental items (such as audio-visual equipment, easels, flipchart paper, colored markers, note pads, pens/pencils, colored flash cards) and have these items available at the Partnering session. Provide copies of any documents required for distribution to all attendees. Participants will bear their own costs for meals, lodging and transportation associated with Partnering .

c. The Initial Partnering Session must be a duration of one day and be held at a location off base as agreed to by the Contracting Officer.

Partnering session may take place concurrently with the Pre-Construction Meeting.

d. Facilitator must be experienced in conducting corporate Partnering sessions and must be a third-party independent facilitating consultant

- not an employee of the Contractor. The Facilitator is responsible for leading all aspects of the Partnering session necessary to achieve the Partnering goal.

e. An outcome of the Partnering session must be an escalation matrix agreed upon by both the Government and Contractor, which identifies key Government and Contractor decision makers by name and anticipated decision durations.

f. Host follow-on Partnering Sessions at three- to six-month intervals or more frequently if needed and lasting generally a half day or less.

Attendees need only be those required to resolve current issues. The same Facilitator used in the Initial Partnering session must lead the follow-on sessions unless an alternative is permitted by the Contractor Officer. All costs associated with follow-on Partnering sessions are the responsibility of the Contractor.

g. Provide a completed partnering agreement to all participants within 30 days of partnering session.

1.12 COORDINATION PERIOD

In addition to contract clause titled PRECONSTRUCTION CONFERENCE, the Contractor must reserve a two-workday period no later than one month following the contract preconstruction conference for coordination. The Contractor's project management team responsible for this project must participate. During the two-day coordination period the Contractor and the Government will exchange information related to the government regulations and procedures, points of contact, relevant design information

SECTION 01 30 00 Page 6 and general discussion about the execution and coordination of the project. The Contractor must dedicate his management team for this two-day coordination period.

1.13 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 NTP, provide the Contracting Officer the email addresses required 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 GENERAL MEETING REQUIREMENTS

3.1.1 Preparatory and Initial Phase meeting checklists

See Section 01 45 00 QUALITY CONTROL for Preparatory and Initial Phase meeting checklists. Contractor is responsible for phase and progress meetings to include:

a. Meeting notification to participants

b. Prepare agenda for meetings

c. Use phase checklists for Preparatory and Initial Phase meetings

d. Physical arrangements for meetings

e. Preside at meetings

f. Record minutes recording proceedings and decisions

g. Copy and send minutes to:

(1) Meeting participants

(2) Project parties affected by decisions

(3) Contracting Officer (No later than 3 working days)

SECTION 01 30 00 Page 7

3.1.2 Weekly Progress Meetings Agenda

See section 01 32 01.00 10 PROJECT SCHEDULE. for the weekly progress meeting. Modify agenda as needed for on-going work.

a. Review minutes from previous progress meetings

b. Review RMS CM Contractor Action Item Report

c. Review work progress since previous meeting

d. Review current definable features of work:

-- Identify phases of current features of work

-- Identify pending phase changes

-- Identify features for discussion in next scheduled meeting

e. Discuss problem prevention:

(1) Field observations

(2) Deficiencies and tracking

(3) Procedures working well

(4) Problems, conflicts

(5) Methods to improve

f. Review construction schedule:

(1) Identify delays

(2) Discuss proposed corrective actions to regain schedule

g. Submittals and Requests for Information (design interpretation):

(1) Review submittal register

(2) Identify submittals to expedite as required

h. Review off-site activities:

(1) Fabrications

(2) Material and equipment delivery schedule

i. Review Testing:

(1) Type, Schedule

(2) Received Results

j. Review changes to construction schedule:

(1) Planned progress during succeeding work period

SECTION 01 30 00 Page 8

(2) Coordination of various schedules

(3) Effect of changes on construction and completion date

k. Review site safety

l. Discuss maintaining contract quality for materials and workmanship

m. Discuss pending modifications, changes and substitutions

n. Discuss other business, as appropriate

SECTION 01 30 00 Page 9

SECTION 01 32 01.00 10

PROJECT SCHEDULE

08/23

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

AACE 84R-13 (2015) Planning and Accounting for Adverse Weather

AMERICAN SOCIETY OF CIVIL ENGINEERS (ASCE)

ASCE 67-17 (2017) Schedule Delay Analysis

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" or "S" classification. Submittals not having a "G" or "S" 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, RO

Preliminary Project Schedule ; G, RO

Initial Project Schedule ; G, RO

Periodic Schedule Update ; G, RO

Narrative Report ; G, RO

1.3 PROJECT SCHEDULER QUALIFICATIONS

Submit Contractor's scheduler qualifications for requires Government approval. Designate an authorized representative to be responsible for the preparation of the schedule and all required updating,status and production of reports. The Designated Project Scheduler must have

SECTION 01 32 01.00 10 Page 1 prepared and maintained at least three previous construction schedules for projects of similar size, 5 years of field experience and complexity to this contract, using Primavera P6. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

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

2.1.1 Government Default Software

The Government uses Primavera P6. Ensure exported schedule files are compatible with the version of P6 used by the Government.

2.1.2 Contractor Software

Scheduling software version of Primavera P6 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

Utilizing Primavera P6, provide the "xer" export file in a version of P6 importable by the Government system. Verify at the SEKO meeting which version of P6 is in use by the Government. Export the schedule in a version of P6 no newer than that used by the Government.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a detailed 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 detailed scheduling of the entire project is required. The scheduling status, updates, maintenance and schedule health of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors, and suppliers working on the project must also contribute in developing and maintaining an accurate detailed Project Schedule. Provide a detail 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.1.1 Approved Project Schedule

Use the approved baseline and current Project Schedule to measure the progress of the work and to aid in evaluating time extensions, and to provide the basis of all progress payments. Make the schedule reasonably cost loaded and activity coded. Front end loading of any form is prohibited. The schedule will provide the basis for all progress

SECTION 01 32 01.00 10 Page 2 payments. If the Contractor fails to submit any schedule within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

3.1.2 Schedule Status Reports

Provide a fully detailed Schedule Status Report on Monday mornings and a tthe first of each month, throughout the entire project duration. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor must take steps necessary to improve its progress including those that will be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.3 Default Terms

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

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

3.1.4 Scheduling Expectations Kickoff Meeting(SEKO)

In conjunction with the post award conference or pre construction conference the Government and the Contractor will hold a separate and distinct Scheduling Expectations Kickoff Meeting(SEKO). The intent of this meeting is for the Government to review with the contractor the requirements of the scheduling specification and, communicate the Government’s expectations regarding schedule development and management, and answer any questions the Contractor may have regarding the schedule requirements.

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. Match the progress payment "Pay Period Thru" date in RMS to the schedule data date.

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without any type of front-end loading. Activities with a negative cost loading is not allowed. Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer. Government does not pay for submittals.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial, or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

SECTION 01 32 01.00 10 Page 3

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 will 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, accurate and achievable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days. Activity Original duration as consecutive work days. Start and stop (random or sporadic) activity durations are prohibited.

3.3.3 Procurement Activities

Include in the schedule 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 Activities

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

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

b. Submission, review and acceptance of features requiring design completion

c. Submission and approval of as-built drawings.

d. Contractor's pre-final inspection.

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

f. Government's pre-final inspection.

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

h. Final inspection.

SECTION 01 32 01.00 10 Page 4

i. Sub Contractor Buy-outs.

3.3.5 Government Activities

Show in schedule, Government and other agency activities that could impact progress. These activities include, but are not limited to approvals, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

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

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

SECTION 01 32 01.00 10 Page 5 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 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.

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 Number (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.

SECTION 01 32 01.00 10 Page 6

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.

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." Must have "Finish On" constraint date equal to the current Contractual completion Date.

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.

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.

SECTION 01 32 01.00 10 Page 7

3.3.8 Adverse Weather

Ensure anticipated adverse weather is accounted for in the Project Schedule. AACE 84R-13 provides methodologies for techniques in planning for adverse weather. The preferred methodology is the use of a weather calendar. If a method other than a weather calendar is proposed the discuss the reason during the SEKO meeting.

3.3.9 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, weather 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. Include in calendars holidays and special event days.

Minimal three calendars: 5 workdays with holidays, 5 workdays with holidays and weather days, 7 day without holidays and weather days.

If a weather calendar is used its implementation and execution is to be in accordance with AACE 84R-13

3.3.10 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" is to have no predecessor logic, and the last activity -"End Project" is to have no successor logic. Except as noted above all activities are to have at least a start-to-start or finish-to-start relationship with its predecessor(s) and a finish-to-finish or finish-to-start relationship with its successor(s).

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

3.3.11 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.12 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.

SECTION 01 32 01.00 10 Page 8

3.3.13 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.14 Original Durations (OD)

Original Durations are consecutive days. ODs are prohibited from start and stop (random or sporadic). Activity Original Durations (ODs) must be reasonable, accurate and achievable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

3.3.15 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 or create float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

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

c. START milestones must have a START TO START relationship with successors).

d. FINISH milestones must have a FINISH TO FINISH relationship with predecessor(s).

3.3.16 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.17 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.