C05_-_Attachment_E_-_Specs_5.3.2017.pdf

US Army Corps of Engineers Baltimore District

SPECIFICATIONS

MDA Parking Lot Expansion, Ft. Belvoir, Va

REQUEST FOR PROPOSAL W912DR-17-B-0006

CONTRACT NO.

DATE: May 2017

THIS PAGE LEFT INTENTIONALLY BLANK

MDA Parking Lot Expansion, Ft. Belvoir BELMDAPKNG

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

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 20.00 10 ENVIRONMENTAL PROTECTION

01 58 00 PROJECT IDENTIFICATION

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

DIVISION 03 - CONCRETE

03 30 00.00 10 CAST-IN-PLACE CONCRETE

DIVISION 26 - ELECTRICAL

26 56 00 EXTERIOR LIGHTING

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 11 00 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 11 10 PAVEMENT DRAINAGE LAYER (RDM)

32 11 23 DENSE GRADED AGGREGATE (DGA) BASE COURSE

32 12 17.05 BITUMINOUS PAVING - VIRGINIA (SUPERPAVE)

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 17 24.00 10 PAVEMENT MARKINGS

32 32 23 SEGMENTAL CONCRETE BLOCK RETAINING WALL

32 92 19 SEEDING

32 92 23 SODDING

32 93 00 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 40 00 STORM DRAINAGE UTILITIES

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION 01 11 00

SUMMARY OF WORK

08/15

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes redeveloping Harris Road, converting existing parallel parking spaces to perpendicular spaces. In addition, at the southeast end of the existing MDA parking lot, perpendicular parking spaces will be added to the drive aisle leading to the existing fire lane and incidental related work.

1.1.2 Location

The work is located at the MDA Headquarters parking lot, Ft. Belvoir, VA, approximately as indicated. The exact location will be shown by the Contracting Officer.

1.2 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract.

1.3 EXISTING WORK

In addition to "FAR 52.236-9, Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements":

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

b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.

1.4 LOCATION OF UNDERGROUND UTILITIES

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

Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work and in accordance with Section 01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS.

1.4.1 Notification Prior to Excavation

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

SECTION 01 11 00 Page 1

1.5 AMERICAN WATER (AW)

In 2009, AW was awarded a 50-year contract to privatize the water and wastewater utilities at Fort Belvoir, Virginia. AW's responsibilities include system capital investment, regulatory and environmental compliance, planning, asset recapitalization, and long term operations and maintenance. The water system distributes purchased water from the Fairfax County Water Authority, with standard water distribution system components - mains, pump stations, storage tanks. The sanitary sewer system conveys untreated sewage to the City of Fairfax system, with standard collection system components - mains and lift stations. For this project, the Contractor shall hire AW to provide all water service construction and/or relocation. See Contract Drawings and bid schedule for detailed information.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

11/11

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

List of Contact Personnel; G , AO

Personnel List; G , AO

Vehicle List; G , AO

1.2 SPECIAL SCHEDULING REQUIREMENTS

a. The new parking area under construction must not be left unuseable for parking while asphalt plants are closed. The parking spaces must be in useable condition and the lighting complete by the time the asphalt plants close. Asphalt paving must be completed by November 15th.

b. Plantings must be installed during the appropriate timeframes as specified and shown. Indicate this on the project schedule. See Section 01 32 01.00 10 PROJECT SCHEDIULE, Article 3.2 for more information.

c. The parking lot will remain in operation during the entire construction period. The Contractor must conduct his operations so as to cause the least possible interference with normal operations of the activity.

d. Permission to interrupt any Activity roads, railroads, or utility service must be requested in writing a minimum of 15 calendar days prior to the desired date of interruption.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear hard hats in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Mark Contractor equipment for identification.

1.3.1.1 Subcontractors and Personnel Contacts

Provide a list of contact personnel of the Contractor and subcontractors

SECTION 01 14 00 Page 1 including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.3.1.2 Identification Passes and Installation Access

Application for and use of passes will be as directed. Each employee must enter Tulley Gate and go to the Visitor Control Center to get a pass. They will need a valid driver's license, passport, state issued identification card, employment authorization document, or permanent resident card. This pass will only allow access to Fort Belvoir thru Tulley Gate. The Contracting Officer will not sponsor the contractor employees to get a long term pass. Immediately report instances of lost or stolen passes to the Contracting Officer.

1.3.1.3 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

1.3.2 Working Hours

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

1.3.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer.

1.3.4 Occupied Buildings

The Contractor shall be working around existing buildings which are occupied. Do not enter the buildings without prior approval of the Contracting Officer.

1.3.5 Utility Cutovers and Interruptions

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

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

c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, and compressed air are considered utility cutovers pursuant to the paragraph WORK OUTSIDE REGULAR HOURS.

SECTION 01 14 00 Page 2

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 3

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

08/15

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2014) Safety and Health Requirements Manual

1.2 SUBMITTALS

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

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

SD-01 Preconstruction Submittals

View Location Map; G , AO

Progress and Completion Pictures; G , AO

SD-11 Closeout Submittals

Stormwater Management As-Built Certification Package; G , DO

1.3 VIEW LOCATION MAP

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

1.4 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs

SECTION 01 30 00 Page 1 provided are for unrestricted use by the Government.

1.5 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 LIABILITY, during the entire period of performance under this contract.

Provide other insurance coverage as required by State law.

1.6 PERMITS

The permits listed below have been obtained by the Government, or are in the approval process, or may require action by the Contractor to obtain or become complete. For permits being obtained by the Government, the Government will furnish approval letters and/or permits to the Contracting Officer who will furnish the Contractor all such permits before or during construction. The Contractor shall abide by all permit requirements.

a. Erosion and Sediment (E&S) Control Plan: The E&S control plans were submitted by the Government to the Ft Belvoir Environmental Office (DPW-ENRD) and the Virginia Department of Environmental Quality (VA-DEQ) for review and approval. The permit will be provided to the Contractor with the Notice to Proceed.

b. Stormwater Management (SWM) Plan: The SWM Plans were submitted by the Government to the Ft Belvoir Environmental Office (DPW-ENRD) for review and approval. The permit will be provided to the Contractor with the Notice to Proceed. Contractor is responsible for ensuring the SWM facilities are constructed per plans and specs, and the Contractor shall record the as-built data required on the drawings during construction. Upon SWM facility construction completion, the Contractor is responsible for preparing and submitting the Stormwater Management As-Built Certification Package. The package shall include an as-built topographic survey, as-built drawings, and the as-built data of the SWM facilities. The Stormwater Management As-Built Certification Package shall be signed and sealed by a Professional Engineer registered in the State of Virginia. Two hard copies and electronic versions shall be included in the submittal for DPW-ENRD and USACE COR records.

c. Stormwater Pollution and Prevention Plan (SWPPP): The Contractor shall prepare and submit a SWPPP for approval in accordance with VA DEQ and Ft. Belvoir DPW-ENRD requirements. For SWPPP guidelines, see the EPA template here:

http://www.epa.gov/npdes/pubs/sw_swppp_guide.pdf. The SWPPP shall be submitted to DPW-ENRD along with a completed DPW-ENRD SWPPP checklist for review and approval prior to construction project commencement.

d. Construction General Permit for construction activities in accordance with EPA's National Pollution Discharge Elimination System (NPDES) program: This does not pertain to this project because the total limit of disturbance is less than 1 acre. No additional action is required.

e. Fort Belvoir Land Disturber Letter: The Contractor shall provide the Ft Belvoir DPW-ENRD Stormwater POC with the Contractor POC responsible for insuring that SWM and ESC plans are executed. This POC should be a VADEQ certified Responsible Land Disturber (RLD), and record of certification shall also be provided to DPW-ENRD at this time. Information on what an RLD is and certification can be found

SECTION 01 30 00 Page 2 here:

http://www.deq.virginia.gov/ConnectWithDEQ/TrainingCertification/RLDGeneralInformation.aspx.

Earth disturbance may not begin until the Contractor receives the Land Disturbance Letter from DPW-ENRD and a pre-construction meeting is held with both DPW-ENRD and COR present.

f. Fort Belvoir Excavation Permit: The Contractor shall complete and submit a Fort Belvoir Excavation Permit Application (Dig Permit) for processing to Janet Lower at DPW-ENRD. A blank Excavation Permit Application can be picked up from Building 1442. Seven (7) copies of a to-scale map or plans are necessary for submittal with the Application.

g. Water/Sewerage Construction Permit: Water construction will be accomplished by the utility owner, American Water. All permits will be handled by American Water.

h. Joint Permit Application for Construction in any Floodplain, Waterway or Wetland: Not applicable to this project.

i. Forest Conservation (FC) Plan: A Forest Conservation Plan has been submitted to the Ft Belvoir Environmental Office, DPW-ENRD for review and approval by the Government. The Contractor shall abide by the requirements contained on the Landscape plan drawings.

Applying for and obtaining any and all other permits not listed above that are or may be required for this project is the sole responsibility, and at the expense of, the Contractor.

1.7 SUPERVISION

1.7.1 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of contract work. In addition, if a Quality Control (QC) representative is required on the contract, then that individual must also have fluent English communication skills.

1.7.2 Superintendent Qualifications

The project superintendent must have a minimum of 10 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

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

SECTION 01 30 00 Page 3

1.7.2.1 Duties

The project superintendent is primarily responsible for managing and coordinating day-to-day production and schedule adherence on the project.

The superintendent is required to attend partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.7.3 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to insure timely completion.

Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.8 PRECONSTRUCTION CONFERENCE

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

1.9 PARTNERING

To most effectively accomplish this contract, the Government requires the formation of a cohesive partnership within the Project Team whose members are from the Government, the Contractor and their Subcontractors. Key personnel from the Supported Command, the End User (who will occupy the facility), the Government Design and Construction team and Subject Matter Experts, the Installation, the Contractor and Subcontractors, and the Designer of Record will be invited to participate in the Partnering process. The Partnership will draw on the strength of each organization in an effort to achieve a project that is without any safety mishaps, conforms to the Contract, and stays within budget and on schedule.

The Contracting Officer will provide Information on the Partnering Process and a list of key and optional personnel who should attend the Partnering meeting.

1.9.1 Informal Partnering

The Contracting Officer will organize the Partnering Sessions with key personnel of the project team, including Contractor personnel and Government personnel.

The Initial Partnering session should be a part of the Pre-Construction Meeting. Partnering sessions will be held at a location agreed to by the Contracting Officer and the Contractor (typically a conference room provided by the Resident Engineer office or the Contractor). The Initial Informal Partnering Session will be conducted and facilitated using

SECTION 01 30 00 Page 4 electronic media (a video and accompanying forms) provided by the Contracting Officer. The Partners will determine the frequency of the follow-on sessions, at no more than 3 to six month intervals.

1.10 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after contract award, provide the Contracting Officer a single (only one) e-mail address for electronic communications from the Contracting Officer related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes or terrorist threats. Multiple email addresses are not allowed.

It is the Contractor's responsibility to make timely distribution of all Contracting Officer initiated e-mail with its own organization including field office(s). Promptly notify the Contracting Officer, in writing, of any changes to this email address.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00 Page 5

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

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

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

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G , AO Preliminary Project Schedule; G , AO Initial Project Schedule; G , AO Periodic Schedule Update; G , AO

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

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

SECTION 01 32 01.00 10 Page 1

2.1.1 Government Default Software

The Government intends to use Primavera P6.

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.

Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 PROJECT SPECIFIC REQUIREMENTS

Work activities such as planting and seeding have special constraints.

Identify the seasonal constraints as a lag within the network schedule.

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

3.3.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Provide additional documentation to demonstrate reasonableness if

SECTION 01 32 01.00 10 Page 2 requested by the Contracting Officer.

3.3.2 Withholdings / Payment Rejection

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

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.4 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.4.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.4.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.4.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.4.4 Mandatory Tasks

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

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

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

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

d. Long procurement activities

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

SECTION 01 32 01.00 10 Page 3

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

h. Controls testing plan submission.

i. Controls testing.

j. Performance Verification testing.

k. Other systems testing, if required.

l. Contractor's pre-final inspection.

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

n. Government's pre-final inspection.

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

p. Final inspection.

3.4.5 Government Activities

Show Government and other agency activities that could impact progress.

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

3.4.6 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil .

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

SECTION 01 32 01.00 10 Page 4

Field Activity Code Length Description

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.4.6.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.4.6.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

3.4.6.3 Area of Work Coding (AREA)

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

Activities cannot have more than one Work Area Code.

Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained.

3.4.6.4 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.4.6.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item

SECTION 01 32 01.00 10 Page 5

Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

3.4.6.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and construction phase. Each activity can have only one Phase of Work code.

a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and construction packages.

b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.4.6.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.4.6.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 00.00 10 QUALITY CONTROL. An activity can have only one Feature of Work Code.

3.4.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

3.4.7.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

3.4.7.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project."

Constrain the project schedule to the Contract Completion Date in such a

SECTION 01 32 01.00 10 Page 6 way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.4.7.3 Interim Completion Dates and Constraints

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

3.4.7.3.1 Start Phase

Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work.

3.4.7.3.2 End Phase

Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.

3.4.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop sSeasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .

3.4.9 Open Ended Logic

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

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

3.4.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document

SECTION 01 32 01.00 10 Page 7 the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.4.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.

Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.4.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.4.13 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.4.14 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

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

3.4.15 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.4.16 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.

3.4.17 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

SECTION 01 32 01.00 10 Page 8 paragraph entitled Percent Complete.

3.4.18 Cost Loading of Closeout Activities

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

3.4.18.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval.

3.4.18.2 O & M Manuals

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

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

MONTHLY ANTICIPATED ADVERSE WEATHER DELAY

WORK DAYS BASED ON (5) DAY WORK WEEK

JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC

6 6 6 8 6 6 7 5 3 5 5 5

3.4.20 Early Completion Schedule and the Right to Finish Early

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

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.5 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

SECTION 01 32 01.00 10 Page 9

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.5.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the 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. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.5.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.5.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.

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

3.6 SUBMISSION REQUIREMENTS

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

SECTION 01 32 01.00 10 Page 10

3.6.1 Data CD/DVDs

Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .xer). Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule must have a unique file name and use project specific settings.

3.6.2 Narrative Report

Provide a Narrative Report with each schedule submission. The Narrative Report is expected to communicate to the Government the thorough analysis of the schedule output and the plans to compensate for any problems, either current or potential, which are revealed through that analysis.

Include the following information as minimum in the Narrative Report:

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

b. A description of activities along the two most critical paths where the total float is less than or equal to 20 work days.

c. A description of current and anticipated problem areas or delaying factors and their impact and an explanation of corrective actions taken or required to be taken.

d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.

e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

f. Identify and discuss out-of-sequence work.

3.6.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format.

Provide two set(s) of hardcopy reports. The following lists typical reports that will be requested:

3.6.3.1 Activity Report

List of all activities sorted according to activity number.

3.6.3.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

SECTION 01 32 01.00 10 Page 11

3.6.3.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.6.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.6.3.5 Schedule Log

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

3.6.4 Network Diagram

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

3.6.4.1 Continuous Flow

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

3.6.4.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

3.6.4.3 Critical Path

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

3.6.4.4 Banding

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

SECTION 01 32 01.00 10 Page 12

3.6.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2)…