RFP_PN87253_LED_Amendment_3.pdf

Request for

Proposal

ECIP, Post Wide Exterior LED Lighting

PN 87253

FY 2017

Fort Drum, NY

JUNE 2018

TABLE OF CONTENTS

June 2018

REQUEST FOR PROPOSAL

ECIP, Post Wide Exterior LED Lighting PN 87253

Fort Drum, NY

DIVISION 01 - GENERAL REQUIREMENTS

01 10 00 STATEMENT OF WORK

01 32 01.00 18 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 45 00.00 10 QUALITY CONTROL

01 45 00.10 10 QUALITY CONTROL SYSTEM (QCS)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 26 – SPECIFICATIONS

26 56 00 EXTERIOR LIGHING (LED)

APPENDICIES

Appendix A – Lighting Fixture Schedule

Appendix B – Installation and Building Maps

Appendix C – Building Exterior Lighting Detail

Appendix D – Electrical Drawings

Appendix E – Basis of Design

POST WIDE EXTERIOR

LED LIGHTING

SECTION 01 10 00 PAGE 1

SECTION 01 10 00

STATEMENT OF

WORK

PART 1 GENERAL

1.1 PROJECT DESCRIPTION

1.1.1 General

Install approximately 3,077 new light emitting diode exterior lighting (with motion sensor controls) and remove existing twenty-year old high pressure sodium (HPS) vapor parking lot, street, and building fixtures. The new fixtures will last 22 years before requiring a replacement. The project objective is to increase cost efficiency with on-post lighting by reducing electricity by 80%, reduce maintenance costs, and improve light quality.

1.1.2 Project Title

Post Wide LED Exterior Lighting

1.1.3 Project Location

The work for this project will be conducted across Fort Drum, NY to include the Airfield. The site of work is on a military reservation and al rules and regulations issued by the Commanding Officer covering general safety, security, and sanitary requirements, etc. shall be observed by the contractor.

1.1.4 Project Type

The Project delivery type is a Design Build project.

1.2 REFERENCES

Code Standards Reference includes but not limited to:

29 CFR 1910 Occupational Safety and Health Standards AADAG American with Disabilities Act and Architectural Barriers Act

Accessibilities Guidelines, latest edition ANSI/IEEE C2 National Electrical Safety Code EM 385-1-1 (2014) Safety and Health Requirements CEC Title 24 (2008; Effective Jan 2010) California's Energy Efficiency

Standards for Residential and Nonresidential Buildings IESNA (2011) Illuminating Engineering Society Lighting Handbook, 10th Edition ICC IBC (2012) International Building Code NFPA 70 (2014) National Electrical Code NFPA 101 (2015) Life Safety Code

Military Criteria includes but not limited to:

Uniform Federal Guide Specification UFGS Energy Policy Act of 2005

(EPAC05)

SECTION 01 10 00 PAGE 2

ER 1110-3450723 Engineering and Design System Commissioning Procedures UFC 1-200-01 General Building Requirements UFC 3-210--02 POV Site Circulation and Parking UFC 3-400-01 Energy Conservation UFC 3-501-01 Electrical Engineering UFC 3-530-01 Interior and Exterior Lighting Control UFC 4-010-01 DoD Minimum Antiterrorism Standards for Buildings UFC 4-010-02 DoD Minimum Standoff Distances for Buildings

1.4 ADMINISTRATIVE

REQUIREMENTS None specified.

1.5 SUBMITTALS

See Section 01 33 00 SUBMITTAL PROCEDURES.

1.6 OCCUPANCY OF PREMISES

1.6.1 Continued Occupancy

All facilities continue to be occupied and be in operation throughout the duration of this project.

Schedule all work at such time and in such a manner to minimize interference and inconvenience to public, staff and Operations.

Work is carried out in a manner that will not impose avoidable hardship, danger, or inconvenience to the public or staff. Prior to the commencement of work, the Contractor and COR will jointly survey the construction site and surrounding areas, making permanent record of existing damage such as cracks, malfunctioning utility equipment and fixtures, or other similar damage. This record serves as a basis for determination of subsequent damage to these structures and adjacent areas due to Contractor's operations. Any damage of any nature to these structures and adjacent areas not noted in original survey but subsequently noted is reported immediately to the COR.

Occupant safety and comfort should be stressed as important requirements.

1.6.2 Disruption of Existing Services

Disruption of utility service is not permitted outside of the construction work area without prior approval of the Facility Manager.

Work is be planned so as to minimize shutdown time of any service or operations ----- Request approval of a utility or equipment shutdown in writing to the COR not less than (14) calendar days before time shutdown is desired. Provide the COR with an estimate of the duration of shutdown and how the facility is going to be affected.

a. Coordinate and submit request for disruption of existing services with COR. Coordinate with

COR, Public Works & facility staff in advance of any shut down.

b. Begin work only after COR, Public Works & facility staff is fully informed and has agreed to the schedule of shut offs.

c. Do not cut into existing services without first verifying with the COR that service has been correctly identified and shut off.

SECTION 01 10 00 PAGE 3

d. Operation of existing valves, switches, etc., to affect service shutdown will be completed by

Government, unless arranged otherwise.

e. Limit duration of each such disruption of service to maximum of 4 hours or as approved by the COR. Fabricate and install interconnecting portions of these systems prior to shut down for final connections.

f. Maintain utilities or other service, indicated to be abandoned, in service or provide alternate means of service until new facilities are provided, tested, and put in operation.

g. Maintain fire protection and fire alarm systems at all times within existing facilities.

h. Review all existing conditions, drawings and other documents for proper coordination between new and existing construction.

i. Active utilities whose locations are unknown to the Government are suspected to exist.

Contractor is cautious of their existence. If they are encountered, immediately report to the COR for direction.

j. Damages to existing structures, utilities and other items which are caused by Contractor's operations are repaired or replaced to their original conditions.

1.6.3 Use of Project Site

Conform to all laws, ordinances, permits and regulations affecting Work on site.

Existing roads, streets, drives, parking lots, entrances and required fire exit ways are kept clear and available at all times for their intended use. Do not use these areas for parking, staging or storage without COR's written approval. Coordinate with COR, and provide alternate routes for public and COR access if normal routes are affected.

Do not unreasonably encumber site with equipment, materials or vehicles.

Return all conditions on or about site and adjacent property which are not shown to be altered, removed or otherwise changed; to conditions which existed previous to starting performance under Task Order.

Construction personnel will not park at any time in any officially marked parking lot; on Government's property without Government's consent, and will not park on adjacent residential streets.

1.6.4 Use of Facilities

Limit use and operation within existing facilities to areas indicated for construction Work and as required to perform Work. Other areas within facility are not to be disturbed or disrupted.

Perform Work so as not to interfere or inconvenience public, staff and training operations.

Maintain and keep clear all required fire exit ways throughout facility within and in vicinity of construction areas: Coordinate alternate temporary egress routes with COR and local fire authority.

Audio devices and radios are prohibited. Two-way radios needed for Contractor's operations are approved by the Facility manager prior to use. Use of two-way radios within occupied facilities is limited, so as not to disrupt occupants.

SECTION 01 10 00 PAGE 4

Use of toilet facilities, washrooms, and telephones within existing facility or occupied areas is not allowed without the COR's consent.

Cafeteria and dining areas may not be used by construction personnel without the COR's consent.

Coordinate construction operations to assure that operations are carried out with consideration given to conservation of energy, water, and materials.

Maintain existing building in a weather-tight condition throughout the construction period. Repair damage and leaks caused by construction operations. Take all precautions necessary to protect building and its occupants during construction period.

PART 2 PRODUCTS

2.1 GENERAL

None.

2.1.1 Facility Inventory Record

None.

2.2 CONTRACT DOCUMENTS

Provided herein

2.2.1 Design Documents

Drawings, diagrams and information provided in the attached Appendixes are to assist the contractor with the completion of this project.

PART 3 EXECUTION

3.1 ELECTRICAL REQUIREMENTS

3.1.1 GENERAL: Select electrical characteristics of the power system to provide a safe, efficient, and economical distribution of power based upon the size and types of loads to be served. Use distribution and utilization voltages of the highest level that is practical for the load to be served.

Voltage drop shall not exceed the maximum allowed per ASHRAE 90.1.

3.1.1.1 All design and construction work shall comply with the latest edition of the National

Electric Code (NEC), National Electrical Safety Code (NESC), UFC 3-501-01 for electrical design criteria, and Fort Drum Exterior Utilities Design Standards.

3.1.1.2 All materials, equipment, fixtures, and appurtenances shall be listed or labeled by

Underwriters Laboratories, Inc., or a similar organization acceptable to the Government.

3.1.1.3 Reference USACE Technical Instructions, UFC 3-501-01 for associated General Electrical Design Criteria.

3.1.1.4 Label all electrical equipment (such as panelboards, disconnect switches, motor starters, contactors, etc.) and circuits. Label each end of spare conduits and cables with the location of the opposite end. Provide wire markers for each conductor at panelboards, gutters, pull boxes, outlet and junction boxes, and each load connection.

SECTION 01 10 00 PAGE 5

3.1.1.5 Size electrical service, feeders and branch circuits per NEC requirements, apply demand factors as applicable and permitted by NEC. Provide 20% spare-future capacity.

3.1.1.6 Maintain dedicated electrical clearances per NEC Article 110. Communicate and coordinate with other trades to maintain clearances after equipment has been installed. Apply adhesive stickers to all equipment requiring dedicated clearances that lists the minimum required access/clearance requirements in front of the equipment.

3.1.1.7 All plywood backboards shall be Fire rated or painted with two coats of UL listed fire- retardant paint. Plywood is required to be AC grade. Do not paint over the plywood fire rating label.

3.2 BUILDING LIGHTING LEVELS, FIXTURES & CONTROLS:

3.2.1 Lighting shall be provided as specified in accordance with UFC 3-530-01. Where certain spaces are not covered by UFC 3-530-01 or this RFP, follow Illuminating Engineering Society (IES) standards.

3.2.2 Conform to the minimum illumination requirements as specified in NFPA 101, Life Safety

Code.

3.2.3 Utilize lighting fixture requirements provided in the lighting specifications portion of this contract.

3.2.4 All lamp colors shall be selected during design – reference the attached appendix displaying what the required light colors are in specific areas of the installation.

3.2.5 Egress and Emergency Lighting shall be provided as required by NFPA 101.

3.2.5.1 Provide emergency egress illumination to either a public way or a distance away from the building that is considered safe (Minimum 10 Feet), whichever is closer.

3.2.6 Where possible emergency lighting shall be achieved thru the use of emergency battery ballasts located inside general illumination fixtures. Centralized lighting inverters which handle several fixtures are also desirable, due to decreased maintenance requirements.

3.2.6.1 Circuit all emergency and exit lighting fixtures to local area light circuit, ahead of local switching device.

3.2.6.2 Provide point by point photometric design calculations which prove compliance with NFPA 101 minimum egress levels.

3.2.6.3 For all exterior lighting, comply with ASHRAE 90.1, ASHRAE 189 requirements and Fort Drum Utility Standards.

3.2.6.4 Reference all applicable UFC’s, including but not necessarily limited to: UFC 4- 211-01N, UFC 3-260-01 and UFC 3-530-01.

3.2.7 Coordinate and verify the areas which are to be illuminated with the Ft. Drum end user.

The actual number and locations of luminaries shall be determined by the Engineer of Record. Exterior lighting plan shall require approval by Fort Drum Public Works.

SECTION 01 10 00 PAGE 6

3.2.7.1 Exterior lighting shall be designed to minimize light trespass. Refer Fort Drum Exterior Utilities Design Standards for additional information. This shall override any UFC reference(s) to HID exterior lighting sources.

3.2.7.2 Outdoor Lighting Minimization guidance can be found under the Environmental section.

SECTION 01 32 01.00 10 Page 1

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 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

Design Drawings; G

Construction Schedule; G

1.2 ACCEPTANCE

Prior to the start of work, prepare and submit to the Contracting Officer for acceptance a construction schedule in the form of either a Network Analysis Schedule (NAS) or Bar Chart Schedule in accordance with the terms in Contract Clause "FAR 52.236-15, Schedules for Construction Contracts," except as modified in this contract.

The acceptance of a Baseline Construction Schedule is a condition precedent to:

a. The Contractor starting work on the demolition or construction stage(s) of the contract.

b. Processing Contractor's invoice(s) for construction activities/items of work.

c. Review of any schedule updates.

Submittal of the Baseline Schedule, and subsequent schedule updates, is understood to be the Contractor's certification that the submitted schedule meets all of the requirements of the Contract Documents, represents the Contractor's plan on how the work will be accomplished, and accurately reflects the work that has been accomplished and how it was sequenced (as-built logic).

1.3 SCHEDULE FORMAT

1.3.1 Network Analysis Schedule (NAS)

Use the critical path method (CPM) to schedule and control project activities. Prepare and maintain project schedules using Primavera P6or Microsoft Project 2010. Importing data into the scheduling program using data conversion techniques or third party software is cause for rejection of the submitted schedule. Build the schedule as follows:

a. The Project Schedule must show submittals, Government review periods, material/equipment delivery, utility outages, all on-site construction, inspection, testing, and closeout activities.

Government and Contractor on-site work activities must be driven by calendars that reflect Saturdays, Sundays and all Federal Holidays as non-work days.

SECTION 01 32 01.00 10 Page 2

b. With the exception of the Contract Award and End Contract milestone activities, no activities shall be open-ended;

Each activity must have predecessor and successor ties.

No activity must have open start or open finish (dangling) logic.

Minimize redundant logic ties.

Once an activity exists on the schedule it must not be deleted or renamed to change the scope of the activity and must not be removed from the schedule logic without approval from the Contracting Officer.

While an activity cannot be deleted, where said activity is no longer applicable to the schedule but must remain within the logic stream for historical record, it can be changed to a milestone.

Document any such change in the milestone's "Notebook", including a date and explanation for the change.

The ID number for a deleted activity must not be re-used for another activity.

c. Each activity must be assigned its appropriate Responsibility Code indicating responsibility to accomplish the work indicated by the activity, Phase Code and Work Location Code.

d. Date/time constraint(s) and/or lags, other than those required by the contract, are not allowed unless accepted by the Contracting Officer. Include as the last activity in the contract schedule, a milestone activity named "Contract Completion Date".

1.3.1.1 Primavera P6 Settings and Parameters

Use the following Primavera P6 settings and parameters in preparing the Baseline Schedule. Deviation from these settings and parameters, without prior consent of the Contracting Officer, is cause for rejection of schedule submission.

a. General: Define or establish Calendars and Activity Codes at the "Project" level, not the "Global" level.

b. Admin Drop-Down Menu, Admin Preferences, Time Periods Tab:

(1) Set time periods for P6 to 8.0 Hours/Day, 40.0 Hours/Week, 172.0 Hours/Month and 2000.0 Hours/Year.

(2) Use assigned calendar to specify the number of work hours for each time period: Must be checked.

c. Project Level, Dates Tab:

(1) Set "Must Finish By" date to "Contract Completion Date".

d. Project Level, Defaults Tab:

(1) Duration Type: Set to "Fixed Duration & Units".

(2) Percent Complete Type: Set to "Physical".

(3) Activity Type: Set to "Task Dependent".

(4) Calendar: Set to "Standard 5 Day Workweek". Calendar must reflect Saturday, Sunday and all Federal holidays as non-work days. Alternative calendars may be used with Contracting Officer approval.

e. Project Level, Calculations Tab:

(1) Activity percent complete based on activity steps: Must be Checked.

SECTION 01 32 01.00 10 Page 3

(2) Reset Remaining Duration and Units to Original: Must be Checked.

(3) Subtract Actual from At Completion: Must be Checked.

(4) Recalculate Actual units and Cost when duration percent(%) complete changes: Must be

Checked.

(5) Link Actual to Date and Actual This Period Units and Cost: Must be Checked.

f. Project Level, Settings Tab:

(1) Define Critical Activities: Check "Total Float is less than or equal to" and add "0d".

g. No on-site construction activity may have durations in excess of 20 working days.

1.3.1.2 Microsoft Project 2010 Settings and Parameters

The Network must have a minimum of 30 construction activities. No on-site construction activity may have durations in excess of 20 working days.

1.3.1.3 Cost Loading Microsoft Project 2010 Schedules

Assign material, labor and equipment costs to their respective Construction Activities. Material and equipment costs for which payment will be requested in advance of installation must be assigned to their respective procurement activity (i.e. the material/equipment on-site activity). Evenly disperse overhead and profit to each activity over the duration of the project. Cost loading must total to 100 percent of the value of the contract.

a. Submit an Earned Value Report with each schedule update showing activity budget, cost percent complete, earned amount and cost to complete as directed by the Contracting Officer.

b. With each schedule submission, provide a Schedule Variance control (SVC) diagram showing:

(1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates.

(2) Earned Value to-date. Revise Cash Flow S-Curves when the contract is modified, or as directed by the Contracting Officer.

1.3.2 Bar Chart Schedule

The Bar Chart must, as a minimum, show work activities, submittals, Government review periods, material/equipment delivery, utility outages, on-site construction, inspection, testing, and closeout activities. The Bar Chart must be time scaled and generated using an electronic spreadsheet program.

1.3.3 Schedule Submittals and Procedures

Submit [Network Analysis Schedules (NAS)][Bar Chart Schedules] and updates in hard copy and on electronic media that is acceptable to the Contracting Officer. Submit an electronic back-up of the project schedule in an import format compatible with the Government's scheduling program.

1.4 SCHEDULE MONTHLY UPDATES

Update the Construction Schedule when the schedule has been revised. The updated schedule must be kept current, reflecting actual activity progress and plan for completing the remaining work. Submit copies of purchase orders and confirmation of delivery dates as directed by the Contracting Officer.

SECTION 01 32 01.00 10 Page 4

a. Narrative Report: Provide with schedule updates. Identify and justify;

(1) Progress made in each area of the project

(2) Critical Path

(3) Date/time constraint(s), other than those required by the contract

(4) Changes in the following; added or deleted activities, original and remaining durations for activities that have not started, logic, milestones, planned sequence of operations, and critical path

(5) Status of Contract Completion Date and interim milestones;

(6) Current and anticipated delays (describe cause of delay and corrective actions(s) and mitigation measures to minimize);

(7) Description of current and future schedule problem areas.

Each entry in the narrative report must cite the respective Activity ID and Activity Description, the date and reason for the change, and description of the change.

1.5 CONTRACT MODIFICATION

Submit a Time Impact Analysis (TIA) with each cost and time proposal for a proposed change. TIA must illustrate the influence of each change or delay on the Contract Completion Date or milestones. No time extensions will be granted nor delay damages paid unless a delay occurs which consumes all available Project Float, and extends the Projected Finish beyond the Contract Completion Date.

a. Each TIA must be in both narrative and schedule form. The narrative must define the scope and conditions of the change; provide start and finish dates of impact, successor and predecessor activity to impact period, responsible party, describe how it originated, and how it impacts the schedule. The schedule submission must consist of three native files:

(1) Fragnet used to define the scope of the changed condition

(2) Most recent accepted schedule update as of the time of the proposal or claim submission that has been updated to show all activity progress as of the time of the impact start date.

(3) The impacted schedule that has the fragnet inserted in the updated schedule and the schedule "run" so that the new completion date is determined.

b. For claimed as-built project delay, the inserted fragnet TIA method must be modified to account for as-built events known to occur after the data date of schedule update used.

c. All TIAs must include any mitigation, and must determine the apportionment of the overall delay assignable to each individual delay. The associated narrative must clearly describe the findings in a chronological listing beginning with the earliest delay event.

(1) Identify types of delays as follows:

(a) Excusable Delay: Force-Majeure (e.g. weather) - Contractor may receive time extension, but time will not be compensable.

(b) Inexcusable Delay: Contractor Responsibility - Contractor will not receive time extension.

SECTION 01 32 01.00 10 Page 5

(c) Compensable Delay: Government Responsibility - Contractor may receive compensable time extension.

(2) If a combination of delay types occurs, it is considered Concurrent Delay, which is defined in the following combinations:

(a) Excusable Delay and Compensable Delay results in Excusable Delay

(b) Excusable Delay and Inexcusable Delay results in Inexcusable Delay

(c) Compensable Delay and Inexcusable Delay results in Excusable Delay

d. Submit Data disks containing the narrative and native schedule files.

e. Unless the Contracting Officer requests otherwise, only add conformed contract modifications into the

Project NAS.

1.6 3-WEEK LOOK AHEAD SCHEDULE

Prepare and issue a 3-Week Look Ahead schedule to provide a more detailed day-to-day plan of upcoming work identified on the Construction Schedule. Key the work plans to activity numbers when a NAS is required and update each week to show the planned work for the current and following two-week period Additionally, include upcoming outages, closures, preparatory meetings, and initial meetings.

Identify critical path activities on the Three-Week Look Ahead Schedule. The detail work plans are to be bar chart type schedules, maintained separately from the Construction Schedule on an electronic spreadsheet program and printed on 8-1/2 by 11 inch sheets as directed by the Contracting Officer.

Activities must not exceed 5 working days in duration and have sufficient level of detail to assign crews, tools and equipment required to complete the work. Deliver three hard copies and one electronic file of the 3-Week Look Ahead Schedule to the Contracting Officer no later than 8 a.m. each Monday, and review during the weekly CQC Coordination or Production Meeting.

1.7 CORRESPONDENCE AND TEST REPORTS:

All correspondence (e.g., letters, Requests for Information (RFIs), e-mails, meeting minute items, Production and QC Daily Reports, material delivery tickets, photographs) must reference Schedule Activities that are being addressed. All test reports (e.g., concrete, soil compaction, weld, pressure) must reference Schedule Activities that are being addressed.

1.8 ADDITIONAL SCHEDULING REQUIREMENTS

Any references to additional scheduling requirements, including systems to be inspected, tested and commissioned, that are located throughout the remainder of the Contract Documents, are subject to all requirements of this section.

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

3.1 BASIS FOR PAYMENT AND COST LOADING

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

SECTION 01 32 01.00 10 Page 6

3.1.1 Withholdings / Payment Rejection

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

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

3.2 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.2.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.2.2 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays.

3.2.3 Original Durations

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

3.2.4 Remaining Duration

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

3.2.5 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled 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 PROJECT SCHEDULE SUBMISSIONS

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

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

3.3.1 Preliminary Project Schedule Submission

SECTION 01 32 01.00 10 Page 7

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

3.3.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued.

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

3.3.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum. Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress.

3.4 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 BI-WEEKLY PROGRESS MEETINGS

Conduct a bi-weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.6 REQUESTS FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.

3.6.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any

SECTION 01 32 01.00 10 Page 8 concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.6.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer based on industry standard AACE 52R-06. Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis. If Contracting Officer determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. Unless approved by the Contracting Officer, no other changes may be incorporated into the schedule being used to justify the time impact.

3.6.3 Time Extension

The Contracting Officer must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.7 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer may require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.

3.7.1 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.7.2 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the Contracting Officer pursuant to FAR 52.236-15 Schedules for Construction Contracts.

SECTION 01 33 00 PAGE 1

SECTION 01 33 00

SUBMITTAL PROCEDURES

05/11

PART 1 GENERAL

1.1 SUMMARY

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections.

Units of weights and measures used on all submittals are to be the same as those used in the contract drawings.

Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Contractor’s to check and approve all items prior to submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals items such as: Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited to) catalog cuts, diagrams, operating charts or curves; test reports;

test cylinders; samples; O&M manuals (including parts list); certifications; warranties; and other such required submittals.

Submittals requiring Government approval are to be scheduled and made prior to the acquisition of the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Material Safety Data Sheets (MSDS) and in compliance with existing laws and regulations.

A submittal register showing items of equipment and materials for when submittals are required by the specifications is provided as "Appendix A - Submittal Register".

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections. Submittals are identified by

Submittal Description (SD) numbers and titles as follows: SD-01 Preconstruction Submittals

Submittals which are required prior to or the start of the next major phase of the construction on a multi-phase contract, includes schedules, tabular list of data, or tabular list including location, features, or other pertinent information regarding products, materials, equipment, or components to be used in the work. Certificates of insurance

Surety bonds

List of proposed Subcontractors

List of proposed products

Construction progress schedule Network Analysis

Schedule (NAS)

Submittal register Schedule of prices or Earned Value

Report Health and safety plan

SECTION 01 33 00 PAGE 2

Work plan

Quality Control (QC) plan

Environmental protection plan

SD-02 Shop Drawings

Drawings, diagrams and schedules specifically prepared to illustrate some portion of the work.

Diagrams and instructions from a manufacturer or fabricator for use in producing the product and as aids to the Contractor for integrating the product or system into the project.

Drawings prepared by or for the Contractor to show how multiple systems and interdisciplinary work will be coordinated.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, instructions and brochures illustrating size, physical appearance and other characteristics of materials, systems or equipment for some portion of the work.

Samples of warranty language when the contract requires extended product warranties.

SD-04 Samples

Fabricated or fabricated physical examples of materials, equipment or workmanship that illustrate functional and aesthetic characteristics of a material or product and establish standards by which the work can be judged.

Color samples from the manufacturer's standard line (or custom color samples if specified) to be used in selecting or approving colors for the project.

Field samples and mock-ups constructed on the project site establish standards by which the ensuring work can be judged. Includes assemblies or portions of assemblies which are to be incorporated into the project and those which will be removed at conclusion of the work.

SD-05 Design Data

Design calculations, mix designs, analyses or other data pertaining to a part of work.

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product or system identical to the material, product or system to be provided has been tested in accord with specified requirements. Unless specified in another section, testing must have been within three years of date of contract award for the project.

Report which includes findings of a test required to be performed by the Contractor on an actual portion of the work or prototype prepared for the project before shipment to job site.

Report which includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports.

Daily logs and checklists.

SECTION 01 33 00 PAGE 3

Final acceptance test and operational test procedure.

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that product, system or material meets specification requirements. Must be dated after award of project contract and clearly name the project.

Document required of Contractor, or of a manufacturer, supplier, installer or Subcontractor through Contractor. The document purpose is to further promote the orderly progression of a portion of the work by documenting procedures, acceptability of methods or personnel qualifications.

Confined space entry permits.

Text of posted operating instructions.

SD-08 Manufacturer's Instructions

Preprinted material describing installation of a product, system or material, including special notices and (MSDS) concerning impedances, hazards and safety precautions.

SD-09 Manufacturer's Field Reports

Documentation of the testing and verification actions taken by manufacturer's representative at the job site, in the vicinity of the job site, or on a sample taken from the job site, on a portion of the work, during or after installation, to confirm compliance with manufacturer's standards or instructions. The documentation must be signed by an authorized official of a testing laboratory or agency and state the test results; and indicate whether the material, product, or system has passed or failed the test.

Factory test reports.

SD-10 Operation and Maintenance Data

Data that is furnished by the manufacturer, or the system provider, to the equipment operating and maintenance personnel, including manufacturer's help and product line documentation necessary to maintain and install equipment. This data is needed by operating and maintenance personnel for the safe and efficient operation, maintenance and repair of the item.

This data is intended to be incorporated in an operations and maintenance manual or control system.

SD-11 Closeout Submittals

Documentation to record compliance with technical or administrative requirements or to establish an administrative mechanism.

Submittals required for Guiding Principle Validation (GPV) or Third Party Certification (TPC).

Special requirements necessary to properly close out a construction contract. For example, Record Drawings and as-built drawings. Also, submittal requirements necessary to properly close out a major phase of construction on a multi-phase contract.

SECTION 01 33 00 PAGE 4

1.2.2 Approving Authority

Office or designated person authorized to approve submittal.

1.2.3 Work

As used in this section, on- and off-site construction required by contract documents, including labor necessary to produce submittals, except those SD-01 Pre-Construction Submittals noted above, construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction.

1.3 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 this section.

SD-01 Preconstruction Submittals Submittal Register; G, RO

1.4 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

1.4.1 Designer of Record Approved (DA)

Designer of Record (DOR) approval is required for extensions of design, critical materials, any deviations from the solicitation, the accepted proposal, or the completed design, equipment whose compatibility with the entire system must be checked, and other items as designated by the Contracting Officer. Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, they are considered to be "shop drawings." Contractor to provide the Government with the number of copies designated hereinafter of all DOR approved submittals. The Government may review any or all Designer of Record approved submittals for conformance to the Solicitation, Accepted Proposal and the completed design. The Government will review all submittals designated as deviating from the Solicitation or Accepted Proposal, as described below. Design submittals to be in accordance with Section 01 33 16 DESIGN AFTER AWARD. Generally, design submittals should be identified as SD-05 Design Data submittals.

1.4.2 Government Approved (G)

Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, they are considered to be "shop drawings."

1.4.3 For Information Only

They are not considered to be "shop drawings" within the terms of the Contract Clause referred to above.

1.5 PREPARATION

1.5.1 Transmittal Form

Use the attached sample transmittal form in Appendix B ENG Form 4025-R for submitting both Government approved and information only submittals in accordance with the instructions on the reverse side of the form. These forms are included in the QCS software that the Contractor is

SECTION 01 33 00 PAGE 5

required to use for this contract. Properly complete this form by filling out all the heading blank spaces and identifying each item submitted. Exercise special care to ensure proper listing of the specification paragraph and sheet number of the contract drawings pertinent to the data submitted for each item.

1.5.2 Source Drawings for Shop Drawings

The entire set of Source Drawing files (DWG) will not be provided to the Contractor. Only those requested by the Contractor to prepare shop drawings may be provided. Request the specific Drawing Number only for the preparation of Shop Drawings. These drawings may only be provided after award.

1.5.2.1 Terms and Conditions

Data contained on these electronic files must not be used for any purpose other than as a convenience in the preparation of construction data for the referenced project. Any other use or reuse shall be at the sole risk of the Contractor and without liability or legal exposure to the Government. The Contractor must make no claim and waives to the fullest extent permitted by law, any claim or cause of action of any nature against the Government, its agents or sub consultants that may arise out of or in connection with the use of these electronic files. The Contractor must, to the fullest extent permitted by law, indemnify and hold the Government harmless against all damages, liabilities or costs, including reasonable attorney's fees and defense costs, arising out of or resulting from the use of these electronic files.

These electronic Source Drawing files are not construction documents. Differences may exist between the Source Drawing files and the corresponding construction documents. The Government makes no representation regarding the accuracy or completeness of the electronic Source Drawing files, nor does it make representation to the compatibility of these files with the Contractor hardware or software. In the event that a conflict arises between the signed and sealed construction documents prepared by the Government and the furnished Source Drawing files, the signed and sealed construction documents govern. The Contractor is responsible for determining if any conflict exists. Use of these Source Drawing files does not relieve the Contractor of duty to fully comply with the contract documents, including and without limitation, the need to check, confirm and coordinate the work of all contractors for the project. If the Contractor uses, duplicates or modifies these electronic Source Drawing files for use in producing construction data related to this contract, remove all previous indicia of ownership (seals, logos, signatures, initials and dates).

1.5.3 Electronic File Format

Provide submittals in electronic format, with the exception of material samples required for SD-04 Samples items. In addition to the electronic submittal, provide three hard copies of the submittals.

Compile the submittal file as a single, complete document, to include the Transmittal Form described within. Name the electronic submittal file specifically according to its contents, coordinate the file naming convention with the Contracting Officer. Electronic files must be of sufficient quality that all information is legible. Electronic format shall be in PDF, unless otherwise specified or directed by the Contracting Officer. Generate PDF files from original documents with bookmarks so that the text included in the PDF file is both searchable and can be copied. If documents are scanned, Optical Character Resolution (OCR) routines are required. Index and bookmark files exceeding 30 pages to allow efficient navigation of the file. When required, the electronic file must include a valid electronic signature, or scan of a signature.

Email electronic submittal documents fewer than 10MB to an email address as directed by the Contracting Officer. Provide electronic documents over 10MB on an optical disc, or through an electronic file sharing system such as the AMRDEC SAFE Web Application located at the following website: https://safe.amrdec.army.mil/safe/.

SECTION 01 33 00 PAGE 6

Provide hard copies of submittals when requested by the Contracting Officer. Up to two additional hard copies of any submittal may be requested at the discretion of the Contracting Officer, at no additional cost to the Government.

1.6 QUANTITY OF SUBMITTALS

1.6.1 Number of Copies of SD-02 Shop Drawings

Submit six copies of submittals of shop drawings requiring review and approval only by QC organization and seven copies of shop drawings requiring review and approval by Contracting Officer.

1.6.2 Number of Copies of SD-03 Product Data and SD-08 Manufacturer's Instructions

Submit in compliance with quantity requirements specified for shop drawings.

1.6.3 Number of Samples SD-04 Samples

a. Submit two samples, or two sets of samples showing range of variation, of each required item.

One approved sample or set of samples will be retained by approving authority and one will be returned to Contractor.

b. Submit one sample panel or provide one sample installation where directed. Include components listed in technical section or as directed.

c. Submit one sample installation, where directed.

d. Submit one sample of non-solid materials.

1.6.4 Number of Copies SD-05 Design Data and SD-07 Certificates

Submit…