Appendix_3v8-PEWS_001-General_Requirements.pdf

Fort Drum Public Works Effective: 30 May 2012 Repair, Rehabilitation, and Construction (RRC) Revision No.: 3 (14 January 2013) Multiple Award Task Order Contract (MATOC)

PEWS 001 – General Requirements Page 1 of 18

Fort Drum RRC Page 1 of 18

FORT DRUM PUBLIC WORKS ENGINEERING

PW Engineering Work Statement

Fred Stone, P.E.

12/3/2012

PEWS 001 – General Requirements Page 2 of 18

Fort Drum RRC Page 2 of 18

Contents

PEWS 001 GENERAL REQUIREMENTS

1.0 General Requirements

1.1 General

1.2 Extent of Work:

1.3 Unified Facility Criteria

1.4 Construction Specifications

1.5 As‐built Record Drawings and Historical Information

1.6 Surface and Subsurface Soil Conditions

1.7 Fort Drum PW Engineering General Requirements

1.7.1 Preconstruction Conference:

1.7.2 Draft Price‐Loaded Progress Schedule:

1.7.3 Task Order Price‐Loaded Progress Schedule

1.7.4 Pre‐construction Meeting Minutes:

1.7.5 Quality Control Acceptance Testing and Commissioning

1.7.6 Field Verification

1.7.7 Existing Tracer Wires and Marking Tape

1.7.8 Equipment and Material Staging/Parking Areas

1.7.9 Notifications for Performance of Work

1.7.10 Maintenance & Protection of Traffic

1.7.11 Government Furnished Materials

1.7.12 Government Furnished Utilities

1.7.13 Government Furnished Property

2.0 Submittals

PEWS 001 – General Requirements Page 3 of 18

Fort Drum RRC Page 3 of 18

2.1 Pre‐construction Submittals

2.2 Construction Submittals

2.3 Post‐construction Submittals

PEWS 001 – General Requirements Page 4 of 18

Fort Drum RRC Page 4 of 18

PEWS 001 GENERAL REQUIREMENTS

1.0 General Requirements

1.1 General

This PEWS sets forth some general requirements that PW Engineering considers necessary for successful project completion. The general requirements presented herein are not inclusive of all general requirements that the Contractor may require. From time‐to‐time, PW Engineering will require more stringent requirements than those presented herein.

When this is the case, these more stringent standards will be specifically stated in the task order statement of work or in associated PEWSs.

1.2 Extent of Work:

The contractor shall confine all work within the proposed limits of construction as shown on the Government concept plans. Any work beyond the limits of construction, by the contractor or subcontractor at any tier, will be restored to conditions equal to or better than existing prior to being affected.

1.3 Unified Facility Criteria

Unified Facility Criteria (UFC) documents provide planning, design, construction, sustainment, restoration, and modernization criteria for construction of Military projects.

PW Engineering shall require compliance with applicable UFCs in construction of the project.

UFC can be obtained at the following URL:

http://www.wbdg.org/ccb/browse_cat.php?o=29&c=4

1.4 Construction Specifications

PW Engineering shall require all work completed under this task order to be completed in accordance with the technical and quality control requirements of the applicable Unified

Facility Guide Specifications (UFGS).

PEWS 001 – General Requirements Page 5 of 18

Fort Drum RRC Page 5 of 18

UFGS are updated quarterly in February, May, August, and November. UFGS can be obtained at the following URL:

http://www.wbdg.org/ccb/browse_cat.php?c=3

Unless specifically requested by the Government, the Contractor will not be required to prepared construction specifications for this task order. When the contractor is required to prepare construction specifications, construction specifications shall be identified by the

Government as a definable feature of work in Statement of Work.

1.5 As‐built Record Drawings and Historical Information

As‐built record drawings and historical information regarding existing facilities, utilities, and infrastructure at the project site, if any, that were used to prepare this statement of work are provided in Appendix B to this statement of work.

1.6 Surface and Subsurface Soil Conditions

General information pertaining to soil conditions, engineering properties, and other related soil properties that may affect construction may be obtained from the United States

Department of Agriculture, Natural Resources Conservation Service (NRCS) Web Soil Survey at the following link:

http://websoilsurvey.nrcs.usda.gov/app/HomePage.htm

It shall be the contractor’s responsibility to complete review of soil conditions at the project site that affect construction. Information from subsurface soil investigations, if any, at the project site and/or surrounding that the Government relied upon when preparing this task order statement of work are presented in the appendices.

1.7 Fort Drum PW Engineering General Requirements

The intent of these general requirements is to establish standards for the Government as well as the Contractor’s for performance of work under task orders.

1.7.1 Preconstruction Conference:

PEWS 001 – General Requirements Page 6 of 18

Fort Drum RRC Page 6 of 18

After award of the task order, at the direction of the Contracting Officer, but prior to commencement of any work at the site, a preconstruction conference will be held. The Contractor and key members will meet with the Contracting

Officer (or Contract Administrator) and Contracting Officer’s Representative

(COR) to review task order statement of work and project coordination. Major subcontractors who will perform work under the task order may also attend.

Unless notified otherwise, the Preconstruction conference is scheduled to be held on the 10‐business day after task order award. The actual date, time, and location will be announced by email. At the Contracting Officers discretion, the task order Notice to Proceed (NTP) maybe issued at the conclusion of the preconstruction conference.

1.7.2 Draft Price‐Loaded Progress Schedule:

The Contractor shall provide at the preconstruction conference a draft price‐ loaded progress schedule that reflects performance of work based on the performance period specified in the task order (from task order award date or from the NTP). If the task order specifies a performance period beginning from the NTP, for purposes of preparing the draft price‐loaded progress schedule, the

Contractor shall assume that the NTP date shall be the date of the pre‐ construction conference.

1.7.3 Task Order Price‐Loaded Progress Schedule

Within 5 business days following receipt of the Notice to Proceed, the

Contractor shall submit a final price‐load progress schedule for Government review and approval. The final price‐loaded progress schedule shall be submitted electronically in Adobe® PDF format via email or on a CD/DVD to the

PW Engineering Construction Representative (ConRep) for the task order. The price‐loaded progress schedule will be routed by the PW Engineering ConRep through the PW Engineering Project Manager to the COR. The COR will review and recommended acceptance/disapproval of the price‐loaded progress schedule to the Contracting Officer. Progress schedules disapproved at the COR review level will be returned to the Contractor with comments. The contractor will have 2‐business days to submit a corrected price‐loaded progress schedule.

PEWS 001 – General Requirements Page 7 of 18

Fort Drum RRC Page 7 of 18

The Contracting Officer will approve the final price‐loaded progress schedule and forward the approved schedule to the Contractor.

1.7.4 Pre‐construction Meeting Minutes:

The PW Engineering PM shall prepare the pre‐construction meeting minutes.

The preconstruction meeting minutes, to include the attendance register, will be provided to the contractor. The contractor will have 5‐business days to respond with any clarification/changes to the preconstruction meeting minute

1.7.5 Quality Control Acceptance Testing and Commissioning

Where used in the Task Order Statement of Work and associated PEWSs, when quality control testing is required to be submitted to the Government for review and approval it shall be understood that these testing requirements are QC acceptance tests that the government will rely upon when completing the final inspection and acceptance of work upon task order completion.

The Contractor shall notify the PW Engineering ConRep a minimum of 2‐ business days in advance of QC acceptance testing. This notification is required for afford the Government an opportunity to whiteness the QC acceptance testing as required to implement the Government’s Quality Assurance planning.

The Contractor shall notify the PW Engineering ConRep a minimum of 5‐ business days in advance of commissioning system installations. This notification is required for afford the Government opportunity to whiteness the startup, shutdown, and commissioning as required to implement the

Government’s Quality Assurance planning.

Quality control acceptance testing and commissioning shall be completed by qualified firms and personnel certified or trained to perform the required QC acceptance testing and commissioning as required by the SOW/PEWSs and contract requirements. QC acceptance testing and commission shall by a qualified testing/Commissioning firm that is financially independent from the material/system installer. For example, a subcontractor completes asphalt paving for the RRC Contractor under a task order; the QC acceptance testing firm cannot be an employee of or hired by the subcontractor that completed

PEWS 001 – General Requirements Page 8 of 18

Fort Drum RRC Page 8 of 18 the asphalt paving. The QC testing firm must be hired by the RRC Contractor and an RRC Contractor employee cannot perform the QC acceptance testing

(since the employee is financially dependent on the RRC Contractor).

The RRC Contractor can hire the QC acceptance testing/commissioning firm to complete QC acceptance testing/commissioning for work that the RRC

Contractor self‐performed. This is the only instance where QC acceptance testing is acceptable to the Government when the qualified firm completing the

QC testing/commissioning is financial depended to the material/system installer.

This requirement shall not limit the RRC contractor from performing QC testing for purposes of verify and checking the quality of work that is self‐ performed/subcontracted or for self‐verification of work performed by subcontractors. It shall also be understood that these requirements shall not prevent the RRC Contractor from affectively implanting their Contract Quality

Control (CQC) Plan. It shall be understood that these QC tests performed by financial dependent firm/personnel, if performed, are not QC acceptance tests the Government will recognize and approve for final acceptance of the work.

1.7.6 Field Verification

Project that require utility connections, earth work, or like operations the contractor shall field verify the horizontal and vertical location of all underground utilities within the project footprint prior to construction.

Verification of utilities shall include invert elevations for sanitary sewer (gravity) and stormwater systems. Upon completion of field verifying the location all site utilities, the contractor shall notify the Contracting Officer that the utility verification is completed and report the location of any utilities that are not within the allowable variances defined by this SOW which may materially affect performance of work under this task order.

Where the scope of work involves construction of new buildings or the maintenance, repair, or renovation of existing buildings or structures the contractor shall, prior to construction, complete a thorough inspection of existing site and facility conditions. Where existing site or facility conditions exist that materially affect performance of work under this task order that were

PEWS 001 – General Requirements Page 9 of 18

Fort Drum RRC Page 9 of 18 not readily apparent at the time of the Request for Task Order Proposal (RTOP) site visit shall be documented in writing and by photographs to the Contracting

Officer.

1.7.7 Existing Tracer Wires and Marking Tape

Existing utilities may or may not have marking/warning tape or tracer wires installed for identifying/locating the service. Where marking tape and tracer wires exist, if damaged/broken during construction, it shall be the contractor’s responsibility to repair/replace the broke tracer wire/marking tape and ancillary equipment. Tracer wires that are repaired, the contractor will be responsible for completing continuity and grounding testing to verify the integrity of the repair. Tracer wire testing shall be completed between the two closest tracer wire vaults on either side of the repair. Tracer wire testing shall be completed prior to backfilling the excavation. If the tracer wire test fails, visual inspection of the repair must be completed by PW Engineering to verify that the repair was adequately completed. The Government does not maintain records of past of tracer wires testing. Therefore, it is not possible to establish if existing damage exists. It shall be the contractor’s responsibility to verify the continuity of tracer wires that maybe affected during construction. The contractor will not be responsible for repairs to correct tracer wire failures, or failures outside the limits of construction where the damage occurred due to construction activities.

1.7.8 Equipment and Material Staging/Parking Areas

Contractors and subcontractors shall not stage or park equipment or stage materials on or near roadways or intersections that impair motorist and pedestrian lines of sight or that present a hazard to motorist or pedestrians.

Contractors and subcontractors shall not park or stage equipment and materials near a known water line, sewer line, or other underground or aboveground utility that poses a threat of damage to the equipment/material if the utility were to fail.

1.7.9 Notifications for Performance of Work

The contractor shall provide notification to the Contracting Officer and

Contracting Officer’s Representative (COR), PW Engineering Project Manager

PEWS 001 – General Requirements Page 10 of 18

Fort Drum RRC Page 10 of 18

(PM), and PW Engineering Construction Representative (ConRep) a minimum of

2‐buisness days prior to any work being performed on weekends, holidays, or other times outside of the normal duty day. No work shall be completed on weekends, holidays, or other times outside of the normal duty day without prior approval of the Contracting Officer.

1.7.9.1 Road Closures:

Unless specified otherwise in the Task Order Task Order Statement of

Work, roads maybe closed to facilitate construction of the project. For purposes of RRC construction projects, road closures are defined as

Short‐Term and Long‐Term. Short‐Term road closures are those road closures that will begin and end on the same day and the road is open to traffic prior to close of business the same day. Long‐Term road closures are all other closures that will extend beyond the close of business the day the road is closed.

Short‐Term Closures: The Contractor shall notify PW Engineering a minimum of 5‐business days prior to the requested date for a short‐ term road closure. The Contractor is responsible for providing

Maintenance and Protection of Traffic (MPT) in accordance with the latest edition of the Manual for Uniform Traffic Control Devices

(MUTCD) and New York State Department of Transportation (NYSDOT) standards. A formal MTP Plan is not required, however, a map showing the location of the detour route and proposed signage is required to be submitted to PW Engineering. The road closure must be approved by the Contracting Officer prior to closing the road.

Long‐Term Closures: The Contractor shall notify PW Engineering a minimum of 10‐business days prior to the requested date for Long‐Term closures. Prior to closing of a road, the Contractor must submit a formal

MPT Plan that details the location of traffic control devices as well as the proposed detour route(s). The MPT shall be in accordance with the latest edition of the MUTCD and NYSDOT standards. The MPT Plan and road closure must be approved by the Contracting Officer a minimum of

5‐business days prior to the requested date.

PEWS 001 – General Requirements Page 11 of 18

Fort Drum RRC Page 11 of 18

1.7.9.2 Lane Closures:

Unless specified otherwise in the Task Order statement of work, roadway travel lanes maybe closed to facilitate construction of the project. For purposes of RRC Projects, lane closures are categorized as wither Short‐Term or Long Term. Short‐Term lane closures are those lane closures that will begin and end on the same day and the lane is open to traffic prior to close of business the same day. Long‐Term lane closures are all other closures that will extend beyond the close of business the day the lane is closed.

Short‐Term Lane Closures: Generally, there is no requirement for the contractor to notify PW engineering for routine lane closures that will last for less than 4 hours. PW Engineering shall be notified 1‐business day prior to a lane closure that will last more than 4 hours. Unless specified otherwise, Short‐Term lane closures do not require the approval of the Contractor Officer. The contractor shall be responsible for implementing MTP in accordance with the MUTCD and NYSDOT standards. A formal NTP Plan is not required.

Long‐Term Lane Closures: The Contractor shall notify PW Engineering a minimum of 10‐business days prior to the requested date for Long‐Term lane closures. Prior to closing of a travel lane, the Contractor must submit a formal MPT Plan that details the location of traffic control devices as well as the proposed detour route(s). The MPT shall be in accordance with the latest edition of the MUTCD and NYSDOT standards. The MPT Plan and lane closure must be approved by the

Contracting Officer a minimum of 5‐business days prior to the requested date.

1.7.9.3 Utilities:

1.7.9.3.1 Electrical:

Procedures for requesting electrical outages are addressed in Exhibit C of the base contract. The Contractor shall notify

PW Engineering a minimum of 15‐business days prior to the

PEWS 001 – General Requirements Page 12 of 18

Fort Drum RRC Page 12 of 18 date requested to electrical outage. Electrical outages must be approved by the Contracting Officer prior to the date requested.

The contractor shall notify PW Engineering a minim of 2‐ business days prior to completing QC acceptance testing of electrical utilities and services. This notification is required to allow the Government opportunity to witness the QC acceptance testing.

1.7.9.3.2 Natural Gas:

The contractor shall notify PW Engineering a minimum of 5‐ buisness days prior to any work that requires natural gas services service to be shut off to buildings or emergency/backup generators. Natural gas outages must be approved by the Contracting Officer prior to the date requested.

natural gas utilities and services. This notification is required to allow the Government opportunity to witness the QC acceptance testing.

1.7.9.3.3 Water:

buisness days prior to any work that requires water service to be shut off to buildings. Water service outages must be approved by the Contracting Officer prior to the date requested.

water utilities and services. This notification is required to

PEWS 001 – General Requirements Page 13 of 18

Fort Drum RRC Page 13 of 18 allow the Government opportunity to witness the QC acceptance testing.

1.7.9.3.4 Communications:

business days prior to any work that involves existing telecommunications facilities that will not involve interruption of communications. This includes both outside and inside plant facilities. The notification must detail the nature of the proposed work, when the work will begin and when the work is anticipated to be completed. PW

Engineering is required to notify Ft. Drum’s Network

Enterprise Command (NEC) of all work that might affect telecommunications.

The contractor shall notify PW Engineering a minimum of

10‐business days prior to any work that involves existing telecommunications faculties that will cause, or have the potential to cause, an interruption of commutations.

The contractor shall notify PW Engineering a minim of 5‐ telecommunications utilities and services. This notification is required to allow the Government opportunity to witness the QC acceptance testing.

1.7.10 Maintenance & Protection of Traffic

The contractor is responsible for preparing and implementing maintenance and protection of traffic planning for the construction project to include ingress and egress of construction and employee vehicles to/from the project work areas.

Unless specifically required by the task order statement of work, a formal

Maintenance and Protection of Traffic (MPT) is not required to be submitted to

PW Engineering. MPT shall be in accordance with the MUTCD and NYSDOT

Standard

PEWS 001 – General Requirements Page 14 of 18

Fort Drum RRC Page 14 of 18

1.7.11 Government Furnished Materials

None, unless specified otherwise.

1.7.12 Government Furnished Utilities

1.7.13 Government Furnished Property

2.0 Submittals

Submittals to be provided under this task order are categorized as pre‐construction, construction, and post‐construction submittals. All submittals will be provided in electronic Adobe® PDF format via email or on a CD/DVD, unless samples are required. When sample are required, the sample shall annotated on the electric submittal and the physical sample shall be delivered to PW Engineering.

UFGS define eleven submittal descriptions (SD) the numbers and titles are as follows:

SD‐01 Preconstruction Submittals

SD‐02 Shop Drawings

SD‐03 Product Data

SD‐04 Samples

SD‐05 Design Data

SD‐06 Test Reports

SD‐07 Certificates

SD‐08 Manufacturer’s Instructions

SD‐09 Manufacturer’s Field Reports

SD‐10 Operations and Maintenance Data

SD‐11 Closeout Submittals

Guidance with respect to requirements for the above‐defined SDs that shall be provided for the task order is as follows:

2.1 Pre‐construction Submittals

PEWS 001 – General Requirements Page 15 of 18

Fort Drum RRC Page 15 of 18

SD‐01: Submittal Register: Contractor’s shall prepare a submittal register for the task order. The submittal resister shall be provided to PW Engineering a For

Information Only (FIO) submittal. PW Engineering will utilize this register to track submittals for the task order.

Inspection & Testing Schedule: The Contractor shall submit a task order specific construction & testing schedule that clearly outlines the quality control requirements for task order statement of work. This submittal shall be provided as a FOI submittal.

SD‐02 Construction Plans: When required by the task order statement of work, the contractor shall submit to PW Engineering for review and approval construction plans that show how the contractor intends to construct the project to meet task order requirements.

SD‐03 The contractor shall submit to PW Engineering product data for long‐lead items.

These maybe submitted as either FIO or for Government review and approval.

SD‐04 Unless specified otherwise, samples are not required. Color samples for long‐ lead items shall be provided for Government review and approval.

SD‐05 The contractor when required to provide construction plans for a task order, shall provide to PW Engineering reports as necessary to document that the construction plans meet required task order statement of work requirements.

SD‐06 Testing data is not required for pre‐construction submittals.

SD‐07 Unless specifically required by the task order statement of work, Certificates are not required for pre‐construction submission.

SD‐08 Unless specifically required by the task order statement of work, manufacture instructions are not required for pre‐construction submission.

SD‐09 Manufacture’s field reports are not applicable to pre‐construction submittals.

SD‐10 Unless specifically required by the task order statement of work, operations and maintenance data is not required as preconstruction submission.

PEWS 001 – General Requirements Page 16 of 18

Fort Drum RRC Page 16 of 18

SD‐11 Project closeout submittals are not applicable for pre‐construction submission.

2.2 Construction Submittals

SD‐02 When construction level plans are not specifically required by the task order statement of work, the contractor shall provide shop drawings illustrating typical installation and construction methods. Unless specified otherwise, these submittals shall be provided as FIO submissions.

SD‐03 Contractors shall provide product data as required by the task order statement of work. When specified in the task order statement work, project data shall be provided for Government review and approval; otherwise, product data shall be submitted as FIO.

SD‐04 Unless specifically requested in the task order statement of work, product samples are not required. When required by the task order statement work, product samples will be provided as a FIO submission or if specified for

Government review and approval.

SD‐05 Concrete and asphalt design mix shall always be submitted to PW Engineering for review and approval. Where compaction performance testing is required by the task order statement of work, the material supplier’s proctor test results must be provided to PW Engineering for review and approval. When site materials are permitted to be used as backfill and compaction requirements are specified, it shall be contractor’s responsibility to have material samples collected and proctor testing complete. Proctor test data must be submitted to

PW Engineering for review and approval.

SD‐06 All testing reports are to be provided to PW Engineering for review and approval, if the test results are to be used to document compliance with task order requirements and for reliance by the Government for acceptance of the work. QC testing results, not specifically requested by the task order statement of work shall be submitted to PW Engineering as a FIO submission.

SD‐07 Unless specifically required by the task order statement of work, Certificates are not required for construction submission.

PEWS 001 – General Requirements Page 17 of 18

Fort Drum RRC Page 17 of 18

SD‐08 Unless specifically required by the task order statement of work, Manufacturer’s

Instructions are not required submittals for Government review and approval.

The Contractor shall provide to PW Engineering Manufacturer’s instruction for major products or when product installations must be completed in a specified manner. Manufacturer’s instruction shall be submitted to PW Engineering as

FIO.

SD‐09 When a manufacturer inspection of the installed system is required for warranty purposes (i.e., roofing), the manufactures inspection and field reports shall be provided to PW Engineering for review and approval. Where a manufacturer requires inspection, other than for warranty, the manufacture’s reports shall be submitted to PW Engineering as a FIO submission.

SD‐10 Operations and maintenance data shall not be provided as a construction submittal.

SD‐11 Closeout information shall not be provided as a construction submittal.

2.3 Post‐construction Submittals

SD‐02 When construction level plans are required by the task order statement of work, As‐built record drawings shall always be submitted to PW Engineering for review and approval. When construction drawings are not required by the task order statement work, a complete set of red‐line shop drawings shall be provided that accurately depict the installed conditions. These shop drawings shall be provided as a FIO submission.

SD‐03 Prior to final inspection by the Government, the Contractor shall provide to PW

Engineering all outstanding submittals as required by the submittal register.

SD‐04 Not applicable to post‐construction submittals

SD‐05 Not applicable for post‐construction submittals

SD‐06 Not applicable for post‐construction submittals

PEWS 001 – General Requirements Page 18 of 18

Fort Drum RRC Page 18 of 18

SD‐07 Not applicable for post‐construction submittals

SD‐08 Not applicable for post‐construction submittals

SD‐09 Not applicable for post‐construction submittals

SD‐10 The contractor shall provided to PW Engineering a complete package of

Operations and Maintenance data, manuals, warranty information, and like documentation for systems installed under the task order statement of work.

These closeout documents shall be provided to PW Engineering as a FIO submission.

SD‐11 The Contractor shall provided a completed DD Form 1354 with cost breakout for all real property assets installed/constructed under the task order statement of work