Specifications_-_B3_100__NPS_4-12-2016.pdf

US Army Corps of Engineers

NEW YORK DISTRICT

GREEN BROOK FLOOD RISK MANAGEMENT PROJECT

GREEN BROOK SUB-BASIN OF THE RARITAN RIVER

SEGMENT B-3

BOROUGH OF MIDDLESEX, NEW JERSEY

Specifications

APRIL 2016

Small Business Set – Aside

IFB NO. W912DS-16-B-0007

Green Brook Flood Risk Management Project Segment B-3

MTOC - 1

MAIN TABLE OF CONTENTS

DIVISION 00 - CONTRACT REQUIREMENTS

00 01 00 SF 1442 AND BIDDING SCHEDULE

00 60 00 REPRESENTATIONS AND CERTIFICATIONS

00 70 00 CONTRACT CLAUSES

00 73 00 SPECIAL CONTRACT REQUIREMENTS

LIST OF DOCUMENTS, EXHIBITS & OTHER ATTACHMENTS

00 90 00 WAGE RATES

00 90 01 FLOOD HAZARD AREA PERMIT AND FRESHWATER WETLANDS

INDIVIDUAL PERMIT

00 90 02 ENGINEER MANUAL

DIVISION 01 – GENERAL REQUIREMENTS

01 12 00.00 18 DESIGN AND RECORD DRAWING REQUIREMENTS

01 32 01.00 18 PROJECT SCHEDULE

01 33 00.00 18 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 02.00 18 QUALITY CONTROL SYSTEM (QCS)

01 45 04.00 18 CONTRACTOR QUALITY CONTROL

01 50 20.00 18 STREAM DIVERSION AND DEWATERING

01 54 00.00 18 MOBILIZATION AND DEMOBILIZATION

01 55 00.00 18 MAINTENANCE AND PROTECTION OF TRAFFIC

01 57 19.00 20 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00.00 18 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 – EXISTING CONDITIONS

02 21 80.00 18 MONITORING OF EXISTING STRUCTURES

02 41 00 DEMOLITION AND DECONSTRUCTION

DIVISION 03 – CONCRETE

03 11 13.00 10 STRUCTURAL CAST-IN-PLACE CONCRETE FORMING

03 11 13.10 10 CONCRETE FORMWORK – FLOODWALL AND MISCELLANEOUS

STRUCTURES

03 15 00.10 10 JOINTS – FLOODWALL AND MISCELLANEOUS STRUCTURES

03 20 00.00 10 CONCRETE REINFORCING

03 20 00.10 10 CONCRETE REINFORCING – FLOODWALL AND MISCELLANEOUS

STRUCTURE

03 30 00 CAST-IN-PLACE CONCRETE

03 31 01.10 10 CAST-IN-PLACE CONCRETE – FLOODWALL AND MISCELLANEOUS

STRUCTURES

03 39 00.00 10 CONCRETE CURING - FLOODWALL AND MISCELLANEOUS

STRUCTURES

MTOC - 2

03 45 00 PRECAST ARCHITECTURAL CONCRETE

DIVISION 05 – METALS

05 05 23.16 STRUCTURAL WELDING

05 12 00 STRUCTURAL STEEL

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 51 00 METAL STAIRS

05 51 33 METAL LADDERS

05 52 00 METAL RAILINGS

DIVISION 09 – FINISHES

09 97 02 PAINTING – FLOODWALL

DIVISION 26 – ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 20 00 INTERIOR DISTRIBUTION SYSTEM

DIVISION 31 – EARTHWORK

31 00 00 EARTHWORK

31 05 22 GEOTEXTILES USED AS FILTERS

31 11 00 CLEARING AND GRUBBING

31 23 00.00 20 EXCAVATION AND FILL

31 32 11 SOIL SURFACE EROSION CONTROL

31 41 16 METAL SHEET PILING

31 63 29 DRILLED MICROPILES

DIVISION 32 – EXTERIOR IMPROVEMENTS

32 11 23 DENSE-GRADED AGGREGATE (DGA) BASE COURSE

32 11 26 BITUMINOUS BASE COURSE

32 12 10 BITUMINOUS TACK AND PRIME COATS

32 12 16 HOT-MIX ASPHALT (HMA) FOR ROADS

32 17 23.00 20 PAVEMENT MARKINGS

32 31 13 CHAIN LINK FENCES AND GATES

32 31 19 DECORATIVE METAL FENCES AND GATES

32 32 23 SEGMENTAL CONCRETE BLOCK RETAINING WALL

32 92 19 SEEDING

32 93 00 EXTERIOR PLANTS

DIVISION 33 – UTILITIES

33 30 00 SANITARY SEWERS

33 40 00 STORM DRAINAGE UTILITIES

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

DIVISION 35 – WATERWAY AND MARINE CONSTRUCTION

35 31 19 STONE AND RIPRAP PROTECTION

MTOC - 3

35 41 00 LEVEE CONSTRUCTION

DIVISION 40 – PROCESS INTEGRATION

40 05 13 PIPELINES, LIQUID PROCESS PIPING

-- End of Project Table of Contents --

Construction Project Identification Sign

16-2

EP 310-1-6a 01 Jun 06

Below are two samples of the Construc-tion Project Identification sign showing how this panel is adaptable for use to identify either military (top) or civil works projects (bottom). The graphic format for this 4’x 6' sign panel follows the legend guidelines and layout as specified below.

The large 4’x 4' section of the panel on the right is to be white with black legend.

The 2’x 4' section of the sign on the left with the full Corps Signature (reverse version) is to be screen-printed Commu-nication Red on the white background The designation of a sponsor in the area indicated is optional with Military or Civil Works construction signs. Signs may list one sponsoring entity. If agreement on a sponsor designation cannot be achieved, the area should be left blank.

This sign is to be placed with the Safety Performance sign shown on the following page. Mounting and fabrication details are provided on page 16-4.

Special applications or situations not covered in these guidelines should be referred to the district Sign Program Manager.

Legend Group 1: One- to two-line description of Corps relationship to project.

Color: White Typeface: 1.25" Helvetica Regular Maximum line length: 19”

Legend Group 2: Division or District Name (optional). Placed below 10.5” reverse Signature (6” Castle).

Color: White Typeface: 1.25" Helvetica Regular

Legend Group 2a: One- to three-line identifica-tion of Military or Civil Works sponsor (optional). Place below Corps Signature to cross-align with Group 5a-b.

Color: White Typeface: 1.25" Helvetica Regular Maximum line length: 19"

Legend Group 3: One- to three-line project title legend describes the work being done under this contract.

Color: Black Typeface: 3" Helvetica Bold Maximum line length: 42"

Legend Group 4: One- to two-line identification of project or facility (civil works) or name of sponsoring department (military).

Color: Black Typeface: 1.5" Helvetica Regular Maximum line length: 42"

Cross-align the first line of Legend Group 4 with the first line of the Corps Signature (US Army Corps) as shown.

Legend Groups 5a-b: One- to five-line identification of prime contractors including:

type (architect, general contractor, etc.), corporate or firm name, city, state. Use of Legend Group 5 is optional.

Color: Black Typeface: 1.25" Helvetica Regular Maximum line length: 21"

All typography is flush left and rag right, upper and lower case with initial capitals only as shown. Letter- and word-spacing to follow Corps standards as specified in Appendix D.

Sign Legend Panel Post Specification Mounting Color Type Size (A) Size Size Code Height Bkg/Lgd

CID-01 various 4’x6’ 4”x4” HDO-3 48” WH-RD/BK

4.5” 2”

6.25”

10.5”

2.5”

3” 3” 42” 3”

6”

4.5”

4.5”

6”

2.25”

9.5”

1.875” 1.875” 1.875” 1.875”

7.75”

3” 21” 1” 21” 2” staudegm Text Box

Segment B-3 Floodwall, Levee and Pump Station staudegm Text Box Green Brook Flood Risk Management Project staudegm Text Box

Contractor:

Text Box New York District staudegm Text Box Local Sponsor:

New Jersey Department of Environmental Protection staudegm Text Box staudegm Text Box staudegm Placed Image staudegm Text Box The graphic format for this 4'x6' sign panel follows the legend guidelines and layout as specified below. The large 4'x4' section of the panel on the right is to be white with black legend. The 2'x4' section of the sign on the left with the full Corps Signature (reverse version) is to be screen-printed Communication Red on the white background. Always use the exact color values listed. Do not use screens or tints of any of the colors for any part of the logos. The CMYK values should be used for print applications. The RGB and HEX# values should be used for on-screen applications.

staudegm Text Box

PROJECT IDENTIFICATION SIGN

CIVIL WORKS PROJECT

staudegm Text Box SECTION 00 73 00 Page 27 staudegm Text Box 21" staudegm Text Box Green Brook Flood Risk Management Project staudegm

Segment B-3

Safety Performance Sign EP 310-1-6a 01 Jun 06

16-3

Each contractor’s safety record is to be posted on Corps managed or supervised construction projects and mounted with the Construction Project Identification sign specified on page 16-2.

The graphic format, color, size and type-faces used on the sign are to be repro-duced exactly as specified below. The title with First Aid logo in the top section of the sign, and the performance record captions are standard for all signs of this type. Legend groups 2 and 3 below identify the project and the contractor and are to be placed on the sign as shown.

Safety record numbers are mounted on individual metal plates and are screw-mounted to the background to allow for daily revisions to posted safety perfor-mance record.

Special applications or situations not covered in these guidelines should be referred to the district Sign Program Manager.

Legend Group 1: Standard two-line title “Safety is a Job Requirement” with 8” (outside diameter) Safety Green first aid logo.

Color: To match Pantone system 347 Typeface: 3" Helvetica Bold Color: Black

Legend Group 2: One- to two-line project title legend describes the work being done under this contract and name of host project.

Color: Black Typeface: 1.5" Helvetica Regular Maximum line length: 42"

Legend Group 3: One- to two-line identifica-tion: name of prime contractor and city, state address. Color: Black Typeface: 1.5" Helvetica Regular Maximum line length: 42"

Legend Group 4: Standard safety record captions as shown.

Color: Black Typeface: 1.25” Helvetica Regular

Replaceable numbers are to be mounted on white .060 aluminum plates and screw-mounted to background.

Color: Black Typeface: 3" Helvetica Regular Plate size: 2.5" x 4.5"

All typography is flush left and rag right, upper and lower case with initial capitals only as shown. Letter- and word-spacing to follow Corps standards as specified in Appendix D.

3” 33.030” eq. 8” eq.

6”

4.5”

10.5”

2.25” 3”

2.25” 3”

4.875”

4.875”

6.75”

4.875” .75” 4.875”

4.5”

3”

3” 42” 3”

2.25” 2.25” 2.25” 2.25”

.75”

3”

.75”

Sign Legend Panel Post Specification Mounting Color Type Size (A) Size Size Code Height Bkg/Lgd

CID-02 various 4’x4’ 4”x4” HDO-3 48” WH/BK-SG

SAFETY PERFORMANCE SIGN

The graphic format, color, size and type-faces used on the sign are to be reproduced exactly as specified below. The title with the First Aid logo in the top section of the sign, and the performance record captions are standard for all signs of this type. Legend Group 2 and 3 below identify the project and the contractor and are to be placed on the sign as shown. Safety record numbers are mounted on individual metal plates and are screw-mounted to the background to allow for daily revisions to posted safety performance record.

staudegm Text Box staudegm Text Box SECTION 00 73 00 Page 28 staudegm Text Box Green Brook Flood Risk Management Project Segment B-3 Floodwall, Levee and Pump Station

Borough of Middlesex Middlesex County, New Jersey staudegm Text Box Green Brook Flood Risk Management Project staudegm

SECTION 00 08 00 Page 35

US ARMY

CORPS OF ENGINEERS, NEW YORK DISTRICT

Green Brook Flood Damage Reduction Project Segment B1

Sebrings Mills Road Bridge Reconstruction, Floodwall, Levee and Pump Station

CONTRACTOR:

FUNDED BY:

COMPLETION DATE:

FOR YOUR SAFETY

1. DO NOT ENTER DESIGNATED WORK AREAS

2. OBEY ALL LOCAL REQUIREMENTS CONCERNING PROHIBITED ACTIVITIES

DISTRICT ENGINEER: COLONEL JOHN R BOULE’

PUBLIC SAFETY SIGN

staudegm Text Box Green Brook Flood Risk Management Project Segment B-3 Floodwall, Levee and Pump Station staudegm Text Box SECTION 00 73 00 Page 29 staudegm Text Box

DISTRICT ENGINEER: COLONEL DAVID A. CALDWELL

staudegm Text Box staudegm Placed Image staudegm Text Box

US ARMY

CORPS OF ENGINEER, NEW YORK DISTRICT

staudegm Text Box Green Brook Flood Risk Management Project staudegm

Fabrication and Mounting GuidelinesEP 310-1-6a 01 Jun 06

16-4

All Construction Project Identification signs and Safety Performance signs are to be fabricated and installed as de-scribed below. The signs are to be erected at a location designated by the contracting officer representative and shall conform to the size, format, and typographic standards shown on pages16-2 and 16-3. Detailed specifica-tions for HDO plywood panel preparation are provided in Appendix B.

Shown below the mounting diagram is a panel layout grid with spaces provided for project information. Photocopy this page and use as a worksheet when preparing sign legend orders.

For additional information on the proper method to prepare sign panel graphics, contact the district Sign Program Manager.

The sign panels are to be fabricated from .75" High Density Overlay Plywood. Panel preparation to follow HDO specifications provided in Appendix B.

Sign graphics to be prepared on a white nonreflective vinyl film with positionable adhesive backing.

All graphics except for the Communication Red background with Corps Signature on the project sign are to be die-cut or computer-cut nonreflective vinyl, prespaced legends prepared in the sizes and typefaces specified and applied to the background panel following the graphic formats shown on pages 16-2 and 16-3.

The 2’x 4’ Communication Red panel (to match Pantone system 032) with full Corps Signa-ture (reverse version) is to be screen-printed on the white background. Identification of the district or division may be applied under the signature with white cut vinyl letters prepared to Corps standards.

Drill and insert six (6) .375" T-nuts from the front face of the HDO sign panel. Position holes as shown. Flange of T-nut to be flush with sign face.

Apply graphic panel to prepared HDO plywood panel following manufacturers’ instructions.

Sign uprights to be structural grade 4" x 4" treated Douglas Fir or Southern Yellow Pine, No.1 or better. Post to be 12' long. Drill six (6) .375" mounting holes in uprights to align with T-nuts in sign panel. Countersink (.5") back of hole to accept socket head cap screw (4" x .375").

Assemble sign panel and uprights. Imbed assembled sign panel and uprights in 4' hole.

Local soil conditions and/or wind loading may require bolting additional 2" x 4" struts on inside face of uprights to reinforce installation as shown.

48”

48”

18”

Construction Project Identification Sign Legend Group 1: Corps Relationship 1.

2.

Legend Group 2: Division/District Name 1.

2.

Legend Group 3: Project Title 1.

2.

3.

Legend Group 4: Facility Name 1.

2.

Legend Group 5: Contractor/A&E 1.

2.

3.

4.

5.

Safety Performance Sign Legend Group 2: Project Title 1.

2.

Legend Group 3: Contractor/A&E 1.

2.

Legend Group 2a: Military/Civil Works Sponsor 1.

2.

Legend Group 5b: Contractor/A&E 1.

2.

3.

4.

5.

staudegm Text Box

Fabrication and Mounting Guidelines staudegm Text Box staudegm Text Box -- End of Section --

SECTION 00 73 00 Page 30

SECTION 00 90 00 Page 1

SECTION 00 90 00

WAGE RATES

SECTION 00 90 01 Page 1

SECTION 00 90 01

FLOOD HAZARD AREA PERMIT AND FRESHWATER WETLANDS INDIVIDUAL PERMIT

SECTION 00 90 00 Page 1

SECTION 00 90 02

ENGINEER MANUAL

Engineer Manual EM 1110-2-6056 Standards and Procedures for Referencing Project Elevation Grades to Nationwide Vertical Datums is included as part of this solicitation W912DS-16-B-0007 Plans and Specification and is posted in the FBO with the Plans and Specification, as an attachment.

SECTION 01 12 00.00 18

DESIGN AND RECORD DRAWING REQUIREMENTS

PART 1 GENERAL

1.1 GENERAL

All RECORD DRAWINGS (or "as-builts") to be provided under this contract shall be accomplished and developed using computer-aided design and drafting (CADD) software and procedures conforming to the following criteria.

1.2 GRAPHIC FORMAT

All CADD data shall be supplied in Bentley Systems, three-dimensional, MicroStation V8, native electronic digital format (i.e., .dgn, .cel). The contractor shall ensure that all digital files and data (e.g., model files, sheet files, reference files, cell libraries) are compatible with the Government's target CADD system (i.e., basic and advanced CADD software, platform, database software), and adhere to the standards and requirements specified herein. The term "compatible" means that data can be accessed directly by the target CADD system without translation, preprocessing, or postprocessing of the electronic digital data files. It is the responsibility of the contractor to ensure this level of compatibility.

1.3 CADD STANDARDS

CADD drawings shall be prepared in accordance with the Department of Defense Architectural/Engineering/Construction (A/E/C) Computer-Aided Design and Drafting (CADD) Standard, Release 5. Standard drawing size shall be ANSI-D CADD drawings shall be prepared using inch-pound units.

All model files and sheet files shall include the following project code in their A/E/C CADD Standard file-name: Green Brook Flood Risk Damage Project Segment B-2 Contract, Borough of Middlesex and Green Brook Township, New Jersey

The Contractor shall submit a written request for approval of any deviations from the Government's established A/E/C CADD standard. No deviations from the Government's established A/E/C CADD standard will be permitted unless prior written approval of such deviation has been received from the Government.

1.4 DELIVERY MEDIA AND FORMAT

All CADD data and files developed under this contract shall be delivered to the Government on electronic digital media at project completion, with each submittal as required in the Schedule of Work. The electronic digital data and files shall be provided on optical media (CD-ROM or DVD-R), referred to as a "disc." Each disc shall be delivered to the Government in a separate container, commonly referred to as a "jewel box." The electronic digital media shall be in a format that can be read and processed by the Government's target CADD system.

SECTION 01 12 00.00 18 Page 1

Model files, sheet files, and other associated files shall not be device-dependent, nor shall the directory structure of the disc require any reconfiguration or other manipulation on the Government's part to view, print, and plot the files directly from the disc. The directory structure of the disc shall be configured such that a complete download of the disc's contents to an electronic folder on a Government computer's hard drive will not require any reconfiguration or other manipulation on the Government's part to view, print, and plot the files.

A tagged portable document format (.pdf) file containing the set of full-sized plotted Sheet Files shall be also included on each disc. This .pdf set shall contain active bookmarks linking to each drawing in the set. The initial view of this set shall conform to the following settings: Layout and Magnification/Navigation Tab set to Bookmarks Panel and Page. Layout and Magnification/Page Layout set to Single Page. Layout and Magnification/Magnification set to Fit Page. (For further information on tagged .pdf documents refer to this website:

http://blogs.adobe.com/acrolaw/2006/01/understanding_t_1.html.)

Each disc shall be labeled with a printed label and each printed disc label shall contain, as a minimum, the following information:

(1) The Project's Name, Contract Number (and Delivery Order Number if applicable), date, and version and/or submission number.

(2) The name of the preparer's firm and the name and phone number of the preparer's Point-of-Contact for the project.

(3) The sequence number of the digital media for multiple-disc submittals.

(4) A description of the contents of the disc (e.g., "Architectural Plans," etc.).

Note: it is acceptable, storage permitting, to include specifications, design analyses and other data on the disc as space permits. These items shall be included in the disc label in accordance with paragraph above.

1.5 HARD COPY TRANSMITTALS

A transmittal letter shall accompany each electronic digital media submittal to the Government. The transmittal letter shall be dated and signed by the appropriate Contractor's representative. The transmittal letter shall be provided to the Government on 8-1/2-inch by 11-inch paper.

An electronic copy of the transmittal letter in .pdf format shall also be provided on the electronic digital media submitted to the Government. The transmittal letter shall contain, as a minimum, the following information:

(1) The information included on the external label of each CD-ROM, along with the total number being delivered, and a list of the names and descriptions of the files on each media unit.

(2) List of all new symbol cells created for the project, which were not provided to the Contractor with the Government-furnished materials. List of all new figures, symbols, tables, schedules, details, and other cells created for the project, which were not provided to the Contractor with the Government-furnished materials, and any associated properties. List of all database files associated with each drawing, as well as a description and documentation of the database format and schema design. Recommended

SECTION 01 12 00.00 18 Page 2 modifications which will be necessary to make the data available for GIS use.

(3) Certification that all delivery media are free of known computer viruses. A statement including the name(s) and release date(s) of the virus-scanning software used to analyze the delivery media, the date the virus scan was performed, and the operator's name shall also be included with the certification. The release or version date of the virus-scanning software shall be the current version which has detected the latest known viruses at the time of delivery of the digital media.

(4) A statement indicating that the A-E will retain a copy of all delivered electronic digital media (with all files included) for at least one year and, during this period of time, will provide up to 2 additional copies of each to the Government, if requested, at no additional cost.

(5) List of any deviations from the Government's standard level scheme and file-naming conventions and a copy of the Government's signed and dated approval letter allowing these exact deviations from the DoD A/E/C CADD Standard.

1.6 OWNERSHIP

The Government, for itself and such others as it deems appropriate, will have unlimited rights under this contract to all information and materials developed under this contract and furnished to the Government and documentation thereof, reports, and listings, and all other items pertaining to the work and services pursuant to this agreement including any copyright. Unlimited rights under this contract are rights to use, duplicate, or disclose text, data, drawings, and information, in whole or in part in any manner and for any purpose whatsoever without compensation to or approval from the Contractor. The Government will at all reasonable times have the right to inspect the work and will have access to and the right to make copies of the above-mentioned items. All text, electronic digital files, data, and other products generated under this contract shall become the property of the Government. By reference, the following DFAR clauses are included in this contract as a part of the requirements herein:

a. DFAR 252.227-7013, "Rights in Technical Data - Noncommercial Items."

b. DFAR 252.227-7017, "Identification and Assertion of Use, Release, or Disclosure Restrictions."

c. DFAR 252.227-7020, "Rights in Special Works."

d. DFAR 252.227-7028, "Technical Data or Computer Software Previously Delivered to the Government."

e. DFAR 252.227-7037, "Validation of Restrictive Markings on Technical Data."

f. DFAR 252.227-7025, "Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends."

g. DFAR 252.227-7014, "Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation."

SECTION 01 12 00.00 18 Page 3

1.7 GOVERNMENT-FURNISHED MATERIALS

The DoD A/E/C CADD Standard, Cover and Border sheet model files shall be downloaded from this website:

https://cadbim.usace.army.mil/CAD.

1.8 RETAINAGE

Failure of the contractor to provide the associated design or construction documents in compliance with the DoD A/E/C CADD Standard, will result in withholding of the progress payment.

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

SECTION 01 12 00.00 18 Page 4

SECTION 01 32 01.00 18

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) 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. The following shall be submitted in accordance with Section 01 33 00.00 18 SUBMITTAL PROCEDURES:

SD-12 Schedules

Initial Project Schedule; G, RO

Preliminary Project Schedule; G, RO

Periodic Project Schedule; G, RO

Narrative Report; G, RO

Four copies of the schedules showing codes, values, categories, numbers, and other items, etc., as required.

SD-07 Certificates

Qualifications Statement;

Documentation showing the qualifications of personnel preparing the reports.

1.3 QUALIFICATIONS

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

SECTION 01 32 01.00 18 Page 1

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the design (if design-build projects) and construction sequences, is required.

The scheduling of constructiondesign and construction is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development. SubContractors (and Designers if Design-Build Projects) and suppliers working on the project shall also contribute in developing and maintaining an accurate Project Schedule. The schedule must be a forward planning as well as a project monitoring tool.

3.1.1 Approved Poject Schedule

Use the approved 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 cost loaded and activity coded. The schedule will provide the basis for all progress payments. If the Contractor fails to submit any schedule within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

3.1.2 Schedule Status Reports

Provide a Schedule Status Report on at least a monthly basis. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor shall take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.3 Default Terms

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

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

3.2 BASIS FOR PAYMENT AND COST LOADING

Use the schedule as the basis for determining contract earnings during each update period and therefore the amount of each progress payment. Lack of an approved schedule update or qualified scheduling personnel will result in an inability of the Contracting Officer to evaluate contract earned value for the purposes of payment. Failure of the Contractor to provide

SECTION 01 32 01.00 18 Page 2 all required information will result in the disapproval of the preliminary, initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on the Schedule.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this specification and shall be capable of producing the Standard Data Exchange Format (SDEF) file discussed in ER 1-1-11. Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule. Scheduling software that meets the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 are Primavera Project Planner (P3) or Primavera Project Management (P5) by Primavera, and Open Plan by Deltek. Manual methods shall not be utilized to produce any required information. The contractor shall be required to furnish to the Gov't the software scheduling program with one software license for the duration of this contract.

3.3.1 Critical Path Method

Use the Critical Path Method (CPM) of network calculation to generate the Project Schedule. Prepare the Project Schedule using the Precedence Diagram Method (PDM).

3.3.2 Level of Detail Required

With the exception of the initial and preliminary schedule submission, the Project Schedule shall include an appropriate level of detail. Failure to develop or update the Project Schedule or provide data to the Contracting Officer at the appropriate level of detail, as specified by the Contracting Officer, shall result in the disapproval of the schedule. The Contracting Officer will use, but is not limited to, the following conditions to determine the appropriate level of detail to be used in the Project Schedule:

3.3.2.1 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Less than 2 percent of all non-procurement activities shall have Original Durations (OD) greater than 20 work days or 30 calendar days. Procurement activities are defined herein.

3.3.2.2 Design and Permit Activities

Include design (for design-build projects) and permit activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period. This shall be at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work. The schedule shall include review and

SECTION 01 32 01.00 18 Page 3 correction periods associated with each item.

3.3.2.3 Procurement Activities

The schedule must include activities associated with the submittal, approval, procurement, fabrication and delivery of long lead materials, equipment, fabricated assemblies and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days. A typical procurement sequence includes the string of activities: submit, approve, procure, fabricate, deliver, installation and testing.

3.3.2.4 Mandatory Tasks

In addition to other activities as required to complete the project, the Progress Schedule shall include the following as separate line activities:

a. Submission, review and acceptance of design packages.

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

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

e. Submission and approval of 1354 data and installed equipment lists.

f. Warranty/Closeout Actions.

g. Contractor's pre-final inspection.

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

i. Government's pre-final inspection.

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

k. Final inspection.

3.3.2.5 Government Activities

Show Government and other agency activities that could impact progress.

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

3.3.2.6 Workers Per Day

All activities shall have an estimate of the average number of workers per day that are expected to be used during the execution of the activity to produce the expected completion date. If no workers are required for an activity, in the case of activities related to procurement, for example, then the activitity shall be identified as using zero workers per day. The workers per day information for each activity shall be identified by the Workers Per Day Code.

SECTION 01 32 01.00 18 Page 4

3.3.2.7 Activity Responsibility Coding (RESP)

Assign responsibility Code for all activities to the Prime Contractor, Subcontractor or Government agency responsible for performing the activity. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements. Code all activities not coded with a Government Responsibility Code to the Prime Contractor or Subcontractor responsible to perform the work. Activities shall not have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE). Unacceptable code values are abbreviations of the names of subcontractors.

3.3.2.8 Activity Work Area Coding

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

Activities shall not have more than one Work Area Code. Not all activities are required to be Work Area coded. A lack of Work Area coding will indicate the activity is not resource or space constrained.

3.3.2.9 Contract Changes/Requests for Equitable Adjustment (REA) Coding

(MODF)

Assign Activity code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by the Contracting Officer, with a Contract Changes/REA Code. Key all Code values to the Government's modification numbering system. Any activity or sequence of activities added to the schedule as a result of alleged constructive changes made by the Government may be added to a copy of the current schedule, subject to the approval of the Contracting Officer.

Assign Activity codes for these activities with a Contract Changes/REA Code. Key the code values to the Contractor's numbering system. Approval to add these activities does not necessarily mean the Government accepts responsibility and therefore liability for such activities and any associated impacts to the schedule, but rather the Government recognizes such activities are appropriately added to the schedule for the purposes of maintaining a realistic and meaningful schedule. Such activities shall not be Responsibility Coded to the Government unless approved. An activity shall not have more than one Contract Changes/REA Code.

3.3.2.10 Contract Line Item (CLIN) Coding (BIDI)

Code all activities to the CLIN on the Contract Line Item Schedule to which the activity belongs. An activity shall not contain more than one CLIN Item Code. CLIN Item code all activities, even when an activity is not cost loaded.

3.3.2.11 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in

SECTION 01 32 01.00 18 Page 5 which the activity occurs. Code activities to either a Design Phase or a Construction Phase. Code fast track design and construction phases proposed by the Contractor to allow filtering and organizing the schedule by fast track design and construction packages. If the contract specifies construction phasing with separately defined performance periods, identify a Construction Phase Code to allow filtering and organizing the schedule accordingly. Each activity shall have only one Phase of Work code.

3.3.2.12 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: Design, Design Submittal, design reviews, review conferences, permits, submittals,Construction Submittal approvals, Acceptance, Procurement, Fabrication, Delivery, Weather Sensitive Installation, Non-Weather Sensitive Installation, Start-Up, Test and Turnover. Assign a Category of Work Code to each activity. Each activity shall have only one Category of Work Code.

3.3.2.13 Definable Features of Work Coding (FOW1, FOW2, FOW3)

Assign a Definable Feature of Work Code to appropriate activities based on the definable ture of work to which the activity belongs. Definable Feature of Work is defined in Specification Section 01 45 04.00 18 CONTRACTOR QUALITY CONTROL. An activity shall not have more than one Definable Feature of Work Code. Not all activities are required to be Definable Feature of Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is acknowledged by the Contractor. Schedule activities on a calendar to which the activity logically belongs. Activities may be assigned to a 7 day calendar when the contract assigns calendar day durations for the activity such as a Government Acceptance activity. If the Contractor intends to perform physical work less than seven days per week, schedule the associated activities on a calendar with non-work periods identified including weekends and holidays. Assign the Category of Work Code - Weather Sensitive Installation to those activities that are weather sensitive.

Original durations must account for anticipated normal adverse weather.

The Government will interpret all work periods not identified as non-work periods on each calendar as meaning the Contractor intends to perform work during those periods.

3.3.3.1 Project Start Date

The schedule shall start no earlier than the date on which the NTP was acknowledged. Include as the first activity in the project schedule an activity called "Start Project"( or NTP). The "Start Project" activity shall have an "ES" constraint date equal to the date that the NTP was acknowledged, and a zero day duration.

3.3.3.2 Schedule Constraints and Open Ended Logic

Constrain completion of the last activity in the schedule by the contract

SECTION 01 32 01.00 18 Page 6 completion date. Schedule calculations shall result in a negative float when the calculated early finish date of the last activity is later than the contract completion date. Include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall have an "LF" constraint date equal to the contract completion date for the project, and with a zero day duration or by using the "project must finish by" date in the scheduling software. The schedule shall have no constrained dates other than those specified in the contract. The use of artificial float constraints such as "zero fee float" or "zero total float" are typically prohibited. There shall only be 2 open ended activities:

Start Project (or NTP) with no predecessor logic and End Project with no successor logic.

3.3.3.3 Early Project Completion

In the event the Preliminary or Initial project schedule calculates an early completion date of the last activity prior to the contract completion date, the Contractor shall identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

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

3.3.4.2 End Phase

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

3.3.4.3 Phase "X" Hammock

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

3.3.5 Default Progress Data Disallowed

Do not automatically update Actual Start and Finish dates with default mechanisms that may be included in the scheduling software. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the AS and AF dates on the

SECTION 01 32 01.00 18 Page 7

Daily Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's updated schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

Updating of the percent complete and the remaining duration of any activity shall be independent functions. Disable program features which calculate one of these parameters from the other.

3.3.6 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer. Propose logic corrections to eliminate all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than two update cycles by logic revision, as approved by the Contracting Officer.

3.3.7 Negative Lags and Start to Finish Relationships

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

3.3.8 Calculation Mode

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

3.3.9 Milestones

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

foundation/substructure construction complete; superstructure construction complete.

3.4 PROJECT SCHEDULE SUBMISSIONS

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

SUBMISSION REQUIREMENTS.

3.4.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 15 calendar days after the NTP is acknowledged. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. Detail it for the first 90 calendar days. It may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as previously specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified

SECTION 01 32 01.00 18 Page 8 herein and must include all of the required Plan and Program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, the planned submissions of all early design packages, permitting activities, design review conference activities and other non-construction activities intended to occur within the first 90 calendar days. Schedule aAny construction activities planned for the first 90 calendar days after NTP. Constrain planned construction activities by Government acceptance of the associated design package(s) and all other specified Program and Plan approvals. Activity code any activities that are summary in nature after the first 90 calendar days with Responsibility Code (RESP) and Feature of Work code (FOW1, FOW2, FOW3).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer. If a design build project, include in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews and conferences;

permit submissions and any required Government actions; and long lead item acquisition prior to design completion. Also cover in the preliminary design-build schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone,including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. As the design proceeds and design packages are developed, fully detail the remaining construction activities concurrent with the monthly schedule updating process. Constrain construction activities by Government acceptance of associated designs. When the design is complete, incorporate into the then approved schedule update all remaining detailed construction activities that are planned to occur after the dry-in milestone.

3.4.3 Design Package Schedule Submission

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

3.4.4 Periodic Schedule Updates

Based on the result of the meeting, specified in PERIODIC SCHEDULE UPDATE MEETINGS, submit Periodic Project Schedule updates. These submissions will enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgement of the Contracting Officer or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made. For design-build projects, update the schedule to include detailed, lower WBS level construction activities as the design progresses, but not later than the submission of the final, un-reviewed design submission for each separate design package. The

SECTION 01 32 01.00 18 Page 9

Contracting Officer may require submission of detailed schedule activities for any distinct construction that is started prior to submission of a final design submission, if such activity is authorized.

3.4.5 Standard Activity Coding Dictionary

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

The SDEF format is as follows:

Field Activity Code…