B.08 - Solicitation - W912HN22B4010 - Specifications-AMD2.pdf

Hunter Army Airfield, Georgia

Solicitation Number

W912HN-22-B-4010

Repair Airfield Infrastructure, Airfield Stormy Sewer System Volume 1 of 1: Specification Divisions 01 - 33

PN95667

September 2022 Amendment 0002

U.S. ARMY ENGINEER DISTRICT, SAVANNAH

CORPS OF ENGINEERS

100 WEST OGLETHORPE AVENUE

SAVANNAH, GEORGIA 31401-3640

US Army Corps Of Engineers Savannah District

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 08/15, CHG 1: 05/21 SUMMARY OF WORK

01 11 00 APPENDIX A CTR SURVEY REQUIREMENTS

01 14 00 11/11, CHG 14: 02/22 WORK RESTRICTIONS

01 30 00 08/15 ADMINISTRATIVE REQUIREMENTS

01 32 01 02/15 PROJECT SCHEDULE

01 33 00 08/18 SUBMITTAL PROCEDURES

01 33 00 APPENDIX A SUBMITTAL REGISTER

01 35 26 11/15 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 11/16 QUALITY CONTROL

01 45 00.15 11/16 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 45 35 02/15 SPECIAL INSPECTIONS

*2 01 50 00 11/20, CHG 1: 08/21 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 11/15 TEMPORARY ENVIRONMENTAL CONTROLS

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

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

DISPOSAL

01 78 00 05/19 CLOSEOUT SUBMITTALS

01 78 23 08/15 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 05/10 DEMOLITION

DIVISION 31 - EARTHWORK

31 00 00 08/08 EARTHWORK

31 11 00 11/18 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 11.51 05/16 PAINT REMOVAL FROM AIRFIELD PAVEMENTS

32 01 13.63 02/16 GILSONITE MODIFIED ASPHALT EMULSION

SEAL COATS

32 01 16.71 02/17 COLD MILLING ASPHALT PAVING

32 01 17.61 05/17 SEALING CRACKS IN ASPHALT PAVING

32 01 18.71 05/17 GROOVING OF AIRFIELD PAVING

32 01 19 08/08 FIELD MOLDED SEALANTS FOR SEALING

JOINTS IN RIGID PAVEMENTS

32 01 29.61 05/17 PARTIAL DEPTH PATCHING OF RIGID PAVING

32 01 29.61 APPENDIX A PAVEMENT REPAIR MATERIAL CERTIFICATION

PROGRAM

32 11 23 08/17 AGGREGATE BASE COURSES

32 12 13 05/17 BITUMINOUS TACK AND PRIME COATS

32 12 15.13 11/17 ASPHALT PAVING FOR AIRFIELDS

32 12 17.19 11/19 FUEL RESISTANT ASPHALT PAVING FOR

AIRFIELDS - SURFACE COURSE

32 13 14.13 11/17 CONCRETE PAVING FOR AIRFIELDS AND

OTHER HEAVY DUTY PAVEMENTS

32 17 23 08/16 PAVEMENT MARKINGS

DIVISION 33 - UTILITIES

*2 33 01 30.16 08/16 TV INSPECTION OF SEWER PIPELINES

*2 33 01 30.72 05/16 RELINING SEWERS

33 40 00 02/10 STORM DRAINAGE UTILITIES

APPENDIX A STANDARD FORMS

-- End of Project Table of Contents --

Repair Airfield Infrastructure, W91HN-22-B-4010 Runway Airfield Repairs Hunter Army Airfield, Georgia

SECTION 01 11 00

SUMMARY OF WORK

08/ 15, CHG 1: 05/ 21

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.

When used, the "RO" designation following the "G" identifies that the Resident Office will review the submittal for the Government. When used, the "AE" designation following the "G" identifies that the Architect-Engineer will review the submittal for the Government.

Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 - SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Salvage Plan ; G, RO

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes repairs to the Hunter Army Airfield infrastructure. Each pavement distress will be repaired using a methodology consistent with standard UFC details for airfield pavements and will include slab replacement, joint and crack seal, patching, mill and resurface, or other repair by replacement.

1.2.2 Location

The work is located at the Hunter Army Airfield, GA.

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

SECTION 01 11 00 Page 1 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.

1.4.1 Notification Prior to Excavation

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

1.5 GOVERNMENT-FURNISHED MATERIAL AND EQUIPMENT

Pursuant to Contract Clause FAR 52.245-1 Government Property, the Government will furnish materials and equipment for installation by the Contractor. None.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

The contractor shall perform the Preconstruction Survey and Profiles and Cross Sections work as specified in Appendix A.

-- End of Section --

SECTION 01 11 00 Page 2

Appendix A

Preconstruction Survey and Profiles and Cross Sections

Prior to full mobilization for construction repairs of runway and taxiways, the contractor is to conduct and provide for Government approval, a topographic survey of the existing runway and associated pavement profiles and cross sections in accordance with: EM 1110-1-1005

(Engineering and Design: Control and Topographic Surveying – 01 Jan 07); EM1110-1-1002

(Survey Markers and Monuments – 01 Mar 2012); and the Savannah District Design Manual, Volume II, Chapter A-1, Para 1.10.1 Surveys.

The Contractor shall provide ground topographical surveying services, including furnishing of all personnel, transportation, equipment and materials required in connection with the services described in the scope that follows. These services shall be performed in accordance with the technical provisions contained herein. Services not specifically described herein are nevertheless required if they can be identified as an item commonly a part of professional grade work of a comparable nature.

• Survey area includes: the runway and all overruns; all taxiways; and areas of ramps and aprons that are receiving a repair as shown on CP101. Other areas of the ramps and aprons need not be surveyed.

• Include a 25’ offset from the edge of pavement.

• At taxiway intersections, ensure that survey extends from the edge of the intersection to 50' into the taxiway to ensure sufficient data is collected.

• Survey shall be provided on the Georgia State plane coordinate system, and contain sufficient detail such that cross-sections can be developed at 50-foot stations along the length of the runway.

• Survey shall be oriented to State Plane North (Grid North) but shall be drawn to actual ground horizontal scale (not grid scale). The surveyor shall provide the necessary conversion information needed to scale the drawings from ground to grid and to translate drawings from project coordinates to state plane coordinates.

• The units of measurement shall be U.S. Survey Feet, on NAD 83 GA (East Zone) State

Plane coordinates, and using NAVD 88 vertical datum.

• Ground shots (points) shall be obtained not more than 20 feet on center (20’ grid).

• Contractor shall add control points (TBM) at a grid of no more than 500 feet in each direction.

• Vertical accuracy must be within .25 inch.

• Survey all elevations associated with each longitudinal and transverse joint. Tie-in elevations are required.

• Survey all connections to concrete. Survey covers runway, shoulders and tie-ins.

• Develop a longitudinal runway profile at centerline, edge of runway marking, and edge of pavement (5 profiles total).

• Develop cross sections at 100’ stations.

• Drawings shall be based on a scale of 1” = 30’.

• Survey shall also include Subsurface Utility Exploration (SUE) Quality Level B (QLB) to identify utilities in the project area proposed, inclusive of, but not limited to the runway lights. The Contractor will coordinate with the local utility companies to confirm the general location of their utilities based upon records research and 811 design ticket notifications, and coordinate research with HAAF to include available utility maps and drawings in utility research.

The Contractor shall submit the topographic survey information in the following formats:

• Microstation 3-D (version v8i) file that complies with the CADD/GID Technology

Center, A/E/C CADD Standard, Release 6.0. The web site is https://www.wbdg.org/ffc/army-coe/cadd-bim-technology-center. The file shall include all survey data.

• Also provide a Bentley Digital Terrain Model (DTM) for the site.

• The Contractor shall also provide a Civil 3-D Model (DTM) for the site.

• The Contractor will provide one (1) bound hardcopy and the Adobe pdf files of the following: Field Sketches, ESRI map document, ESRI geodatabase, Field Data

Access database, photographs, and MicroStation Design File in their appropriate electronic formats. The Contractor will also provide electronic copies of the U-

SMART datasheets for all survey control established under this contract.

http://www.wbdg.org/ffc/army-coe/cadd-bim-technology-center

SECTION 01 14 00

WORK RESTRICTIONS

11/ 11, CHG 14: 02/ 22

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 Contractor Quality Control approval.][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 SPECIAL SCHEDULING REQUIREMENTS

a. Prior to closing runway for construction, contractor shall demonstrate to the government their plan to execute the work within the allowable time frame is complete and ready for execution. At a minimum, material and equipment submittal approvals shall be completed and required materials shall be on-hand or ordered and scheduled for delivery at the appropriate time(s).

] 1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.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.3.1.1 Subcontractors and Personnel Contacts

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

1.3.1.2 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. 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.

SECTION 01 14 00 Page 1

1.3.2 Working Hours

Regular working hours will consist of an 8 1/2 hour, between 7 a.m. and 3:30 p.m.,Monday through Friday excluding Government holidays. However, Contractor work hours for this project are anticipated to be as much as 7 days per week and 24 hours per day during certain activities. Contractor shall notify COR of anticipated weekly work schedule at least 15 calendar days in advance for approval.

1.3.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, 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.3.4 Batch Plant

Setup and operation of a batch plant for paving or related operations is not authorized on the installation. The contractor shall transport materials onto the installation from off government premises.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 2

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

08/15

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 (2014) Safety and Health Requirements Manual

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

View Location Map ; G, RO

Existing Site Conditions

Superintendent Qualifications ; G, RO

SD-07 Certificates

Progress And Completion Pictures ; G, RO

1.3 PHOTOGRAPHIC DOCUMENTATION

1.3.1 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.3.2 Photo Documentation

a. Photography: Photographs shall not include military personnel, training or equipment. No identifying data shall appear on the face of the prints or in the viewing area of the electronic files. Failure to follow the started requirements is grounds for remove from the government installation and confiscation of any unapproved items. No progress photos shall be posed on the internet.

b. The use of construction site web cameras is not authorized for this project. In addition, it is a crime under 18 USC 795 to photograph or video defense installations without first obtaining the permission of the Commanding Officer of the military installation. It is a crime under 18

SECTION 01 30 00 Page 1

USC 797 to reproduce publish, sell or give away any photograph, picture or graphic reproduction of a defense installation without first obtaining permission of the Commanding Officer of the military installation. Failure to follow the stated requirements is grounds for removal form the installation and confiscation of unapproved or prohibited items.

1.3.3 Existing Site Conditions

In coordination with the Government, photographically document site conditions prior to start of construction operations.

1.3.4 Progress And Completion Pictures (Monthly)

Submit monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color, 300 dpi 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 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 Georgia State law.

1.5 SUPERVISION

1.5.1 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.5.2 Superintendent Qualifications

The project superintendent must have 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. Submit the superintendent's qualifications, in resume format, prior to the pre-qualification meeting.

SECTION 01 30 00 Page 2

1.5.2.1 Duties

The project superintendent is primarily responsible for managing 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.5.3 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 insure 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.6 PRECONSTRUCTION CONFERENCE

After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule of prices or earned value report, shop drawings, and other submittals, scheduling programming, prosecution of the work, and clear expectations of the "Interim DD Form 1354" Submittal. Major subcontractors who will engage in the work must also attend.

1.7 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

Not used.

SECTION 01 30 00 Page 3

SECTION 01 30 00 Page 4

SECTION 01 32 01

PROJECT SCHEDULE

02/15

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 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

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

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

SD-01 Preconstruction Submittals

Preliminary Project Schedule ; G, RO Initial Project Schedule ; G, RO Periodic Schedule Update ; G, RO

1.3 SCHEDULE PREPARER

Authorize a representative to prepare the schedule and update and produce reports. The authorized representative shall have at least 2 years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this Section. Representative shall have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

The software used to produce and update the required schedules shall meet the requirements of this Section.

2.1.1 Government Default Software

The Government intends to use Primavera P6.

SECTION 01 32 01 Page 1

2.1.2 Contractor Software

Scheduling software used by the contractor shall 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 shall be created and supported by the software manufacturer.

2.1.2.1 Primavera

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

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

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

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

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

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

8.0 Hour days.

f. Set Schedule Option for defining Critical Activities to "Longest Path".

g. Set Schedule Option for defining progressed activities to "Retained Logic".

h. Set up cost loading using a single lump sum resource. The Price/Unit shall be $1/hr, Default Units/Time shall be "8h/d", and settings "Auto Compute Actuals" and "Calculate costs from units" selected.

i. Activity ID's shall not exceed 10 characters.

j. Activity Names shall have the most defining and detailed description within the first 30 characters.

2.1.2.2 Other Than Primavera

If the Contractor chooses software, other than Primavera P6, that is compliant with this Section, provide for the Government's use 2 licenses, 2 computers, and training for 2 Government employees in the use of the software. These computers shall 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, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing the schedule activities. The scheduling of the entire project, including construction sequences, is required.

Contractor management personnel shall actively participate in its

SECTION 01 32 01 Page 2 development. working on the project shall also contribute in developing and maintaining an accurate project schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. 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 the activities coded to a Contract Line Item Number (CLIN) shall equal the value of the CLIN.

3.2.1 Activity Cost Loading

Activity cost loading shall 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 Section may result in the disapproval of the schedules or updates and subsequent rejection of payment requests until requirements are met.

If 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 for 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 shall 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.

SECTION 01 32 01 Page 3

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.

c. Submission of mechanical/electrical/information systems layout drawings.

d. Long procurement activities

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

g. Submission and approval of DD1354 data and installed equipment lists.

h. Submission and approval of testing and air balance (TAB).

i. Submission of TAB specialist design review report.

j. Submission and approval of fire protection specialist.

k. Submission and approval of Building Commissioning Plan, test data, and reports. Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the Contract commissioning requirements. Building testing and commissioning tasks shall be completed prior to submission of building commissioning report and subsequent Contract completion.

l. Air and water balancing.

m. Building commissioning - Functional Performance Testing.

n. Controls testing plan submission.

o. Controls testing.

p. Performance Verification testing.

q. Other systems testing, if required.

r. Contractor's pre-final inspection.

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

t. Government's pre-final inspection.

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

v. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

SECTION 01 32 01 Page 4

These activities include, but are not limited to: 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 the 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 the field construction and direct work activities, if directed by the Contracting Officer. Workers per day shall be 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 activities to the Prime Contractor, subcontractor, or Government agency 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 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 5 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 flors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

Some activities do nto require a Work Area code. 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 an activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key the 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 the activities, using the 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 Each activity can have only one Phase of Work code.

a. Code 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 submittals, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have only 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 quality control plan.

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

An activity can have only one Feature of Work Code.

SECTION 01 32 01 Page 6

3.3.7 Contract Milestones and Constraints

Milestone activities shall be used for significant project events including, but not limited to, project phasing, project start and end activities, and 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 affect 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 shall be a start milestone titled "NTP Acknowledged," which shall 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 shall be a finish milestone titled "End Project".

The project schedule shall be constrained 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. The start milestone shall be called "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 Contract-defined work periods, 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 and assign seasonal calendars to seasonally affected activities.

SECTION 01 32 01 Page 7

If an activity is weather-sensitive, assign it to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated days provided in Contract Clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER.

The assignment of the non-work days should be over a 7-day week since weather records are compiled on 7-day weeks, which will cause some of the weather related non-work days to fall on weekends .

3.3.9 Open Ended Logic

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

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

3.3.10 Default Progress Data Disallowed

Actual Start and Finish dates shall not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of an activity shall 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 shall 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 the preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis, subject to Government approval. 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 and 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 shall not be changed without Contracting Officer approval.

3.3.13 Original Durations

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

3.3.14 Leads, Lags, and Start to Finish Relationships

Lags shall be reasonable as determined by the Government and not used in place of realistic original durations, shall not be in place to artificially absorb float, or to replace proper schedule logic. Leads (negative lags) and Start to Finish (SF) relationships are prohibited.

SECTION 01 32 01 Page 8

3.3.15 Retained Logic

Schedule calculations shall retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity starts and the predecessor activity 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") shall 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 necessary to complete the activity. Remaining duration may not mathematically correlate with percentage found under Paragraph "Percent Complete", above.

3.3.18 Cost Loading of Closeout Activities

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

3.3.18.1 As-Built Drawings

If there is no separate 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, whichever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.

3.3.18.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

3.3.19 Anticipated Adverse Weather

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

3.3.20 Early Completion Schedule and the Right to Finish Early

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

SECTION 01 32 01 Page 9

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 its own work items to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the Contractor's accelerated work.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in Paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth, 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 schedules do not relieve the Contractor from compliance with the Contract.

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 CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It shall 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 shall 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 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 packages and other specified Program and Plan approvals shall occur prior to planned construction activities.

Activity code activities that are summary in nature after the first 90 calendar days with Bid Item code (BIDI), Responsibility Code (RESP), and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after NTP is issued. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent the 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 Paragraph PERIODIC SCHEDULE UPDATE MEETINGS, below. These updates will enable the Government to assess Contractor's

SECTION 01 32 01 Page 10 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 date shall match the dates reported on the Contractor's Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

3.5.1 Data CD/DVDs

Provide 2 sets of data CD/DVDs containing the current project schedule, previously submitted schedules in the format of the scheduling software (e.g. .xer), the Narrative Report, and the required Schedule Reports.

Label each CD/DVD with the type of schedule (Preliminary, Initial, Update), full Contract number, data date, and file name. Each schedule shall 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 problems, either current or potential, which are revealed through that analysis. At a minimum:

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

b. Describe activities along the 2 most critical paths where the total float is less than or equal to 20 work days.

c. Describe current and anticipated problem areas, delaying factors, 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 the schedule changes by activity ID and activity name, including what specifically was changed and why the change was needed. At a minimum, include 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

Formatting, filtering, organizing, and sorting each schedule report shall be as directed by the Contracting Officer. Typically, reports shall contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, SECTION 01 32 01 Page 11

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. Typical reports that will be requested include:

3.5.3.1 Activity Report

List of the activities sorted according to activity number.

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 the 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. This report shall reflect the earnings of activities based on the agreements made in the schedule update meeting. If 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. This report shall also provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report shall 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 Report generated from the current project schedule being submitted.

3.5.4 Network Diagram

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

3.5.4.1 Continuous Flow

Show a continuous flow from left to right with no arrows from right to left. Show the activity number, description, duration, and estimated earned value on the diagram.

3.5.4.2 Project Milestone Dates

Show dates on the diagram for start of project, Contract-required interim completion dates, and Contract completion dates.

SECTION 01 32 01 Page 12

3.5.4.3 Critical Path

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

3.5.4.4 Banding

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

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing:

a. Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and

b. Earned Value to-date

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings, to review the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly, within 5 days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows the meeting participants to view the proposed schedule during the meeting.