Attachment_C_-_Construction_Specifications.pdf

US Army Corps of Engineers Baltimore District

CONSTRUCTION

SPECIFICATIONS

PERIMETER SECURITY

FENCE

FORT MYER, VIRGINIA

CONTRACT NO.

DATE. AUG ##, 2018

Perimeter Security Fence MYERFENCE

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.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE(RMS CM)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

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

12 93 00 SITE FURNISHINGS

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 08 00 APPARATUS INSPECTION AND TESTING

26 28 00.00 10 PANELBOARDS

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 10 05 ELECTRONIC SECURITY SYSTEMS (ESS)

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 11 00 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 11 10 PAVEMENT DRAINAGE LAYER (RDM)

32 11 16.16 BASE COURSE FOR RIGID, SUBBASE COURSE FOR FLEXIBLE, AND

PERVIOUS PAVING

32 11 23 DENSE GRADED AGGREGATE (DGA) BASE COURSE

32 12 17.05 BITUMINOUS PAVING - VIRGINIA (SUPERPAVE), POROUS ASPHALT

(JOGGING PATH), AND MILL AND OVERLAY

32 14 43 PERMEABLE CONCRETE PAVER

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 16 15 CONCRETE BLOCK PAVEMENTS

32 17 24.00 10 PAVEMENT MARKINGS

32 31 13 CHAIN LINK FENCES AND GATES

32 31 13.90 SECURITY FENCES

32 32 22 MECHANICALLY STABILIZED EARTH (MSE) WALL

PROJECT TABLE OF CONTENTS Page 1

32 92 19 SEEDING

32 92 23 SODDING

32 93 00 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 40 00 STORM DRAINAGE UTILITIES

33 46 16 SUBDRAINAGE SYSTEM

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

DIVISION 34 - TRANSPORTATION

34 73 13 CANTILEVERED CRASH-RATED SLIDING VEHICLE GATE SYSTEM

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes construction of a security fence of approxamately 10,000 LF with five entry gates and intrusion detection system installation along Joint Base Myer-Henderson Hall's (JBM-HH) shared boundary with Arlington National Cemetery (ANC). Supporting facilities shall include relocation of existing utilities along the fence route as necessary, electrical, paving, walks, curbs, and gutters, storm drainage, and site improvements. Access for individuals with disabilities shall be provided. Cyber Security Measures and Sustainability/Energy measures shall be incorporated into this project.

1.1.2 Location

The work is located along the boundaries of Joint Base Myer-Henderson Hall and Arlington National Cemetery, approximately as indicated.

1.2 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.3 LOCATION OF UNDERGROUND UTILITIES

See Section 01 14 00 for this information.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 1

SECTION 01 14 00

WORK RESTRICTIONS

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

Construction Phasing Plan; G AO

1.2 SPECIAL SCHEDULING REQUIREMENTS

1.2.1 Construction Phasing Plan

Furnish to the Contracting Officer for approval a phasing plan consisting of narrative and drawings as applicable clearly defining proposed sequence of construction, particularly at gates. This plan will be reviewed by and coordinated with personnel of The Old Guard (TOG), Arlington National Cemetery (ANC) and the chaplain officiating at funerals.

1.2.2 Specific Requirements

As applicable the following shall be incorporated into the phasing plan.

a. Work on one gate at a time. Notify the Contracting Officer at least 30 days before proposed work on each gate will begin, except for gates listed below.

b. New parking lot and landscaping at Henderson Hall (HH) shall be completed before existing HH parking spaces are removed for fence construction.

c. Arlington National Cemetery will remain in operation during the entire construction period. The Contractor shall conduct his operations so as to cause the least possible interference with normal operations of the cemetery (ANC Visitor Hours are 08:00 a.m. - 07:00 p.m., April-September; and 08:00 a.m. - 05:00 p.m. October-March; seven days a week).

d. Notify the Contracting Officer at least 60 days before proposed work at Old Post Chapel (OPC), Memorial Chapel (MC), the Millennium Project site and Selfride Gates will begin. This is necessary to allow the Government to relocated functions at OPC and MC, and at reroute Selfridge Gate traffic to other locations.

e. The Government will allow an ample periods (60 - 90 days) of time to complete work at OPC and Selfridge, thereby eliminating the need to cease work when ceremonies will take place at these locations.

SECTION 01 14 00 Page 1

f. Typically members of The Old Guard participating in ceremonies at OPC remain inside OPC during inclement weather. However, MC does not afford this protection so an approved modular shall be provided.

Coordinate with the Contracting Officer for space requirements and locations.

g Contractor is responsible to ensure that no work interferes with or delays any funeral, ceremony, procession, or visitation in such a way that the dignity or security of the event is compromised. The Contractor's site manager shall be responsible for staying abreast of all such upcoming events. A list of scheduled ceremonies will be provided each week prior to the event, and a list of scheduled funerals will be provided the day prior to the service. Generally work, especially with power equipment, within 1,000 feet of the funeral or ceremony will not be permitted.

g. All hand work within 300 feet of a scheduled ceremony shall be discontinued prior to commencement of the ceremony. This shall include the removal of all equipment, tools, materials, and debris, so that the area will be left in a clean, neat condition, affording a presentable appearance. During ceremonies, equipment operations within 900 feet of the ceremony shall be discontinued.

1.2.3 Coordination with Other Contractors

Other Contractors may be in the work areas repairing the historic wall between ANC and JBM-HH. If so, after award of this contract a meeting will be held with all contractor representatives and the Contracting Officer to develop a plan of work coordination. In case of disagreement regarding use of an area and priorities, the decision of the Contracting Officer will control.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 Activity Regulations

Ensure that Contractor personnel employed on Joint-Base Myer-Henderson Hall (JBM-HH) become familiar with and obey JBM-HH 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 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 Facility Security

1.3.1.2.1 1.9.1 General

Contractor and contractor personnel working at JBM-HH shall be required to comply with provisions below. Any questions related to such requirements shall be addressed to JBM-HH security and Department of Public Works (DPW) through the Contracting Officer.

SECTION 01 14 00 Page 2

1.3.1.2.2 1.9.2 Background Checks

See paragraph "Access And General Protection/Security Policy And Procedures" below.

1.3.1.2.3 1.9.3 Badges

Personnel permitted to work on post based on background checks will receive badges and vehicles identification. Badges and vehicle identification shall be returned to Fort Myer at completion of project.

1.3.1.2.4 1.9.4 Parking

Parking on post will be restricted to Contractor vehicles only. No privately owned vehicles will be allowed on post. Personnel may park off-post and arrange for vans or buses for transportation to the construction site, or walk in (walk-in's enter via Hatfield Gate only).

Vans, buses and drivers will be subject to the same security requirements as construction personnel.

1.3.1.2.5 1.9.5 Parking and Staging

Parking for official Contractor vehicles identified by company placards or logos, construction trailers, private vehicles, and staging will be located at designated areas as directed by the Contracting Officer.

1.3.1.2.6 1.9.6 Foreign Personnel

No illegal aliens are permitted on post. Contractor personnel may include foreign nationals with valid work visa.

1.3.1.2.7 1.9.7 VDOT Vehicle Compliance

All contractor vehicles shall comply with Virginia Department of Transportation (VDOT) requirements, including tags, vehicle registration, vehicle safety, etc. Vehicles not meeting VDOT requirements will be denied entry to JBM-HH.

1.3.1.2.8 1.9.8 Driving Right-of-Ways

All contractor vehicles shall stop, slow down, or give right-of-way for troop traffic on post roads.

1.3.1.2.9 1.9.9 Deliveries

Contractor deliveries shall be schedule with the Contracting Officer with at least one week's notice especially if delivery involves multiple trucks.

1.3.1.2.10 1.9.10 Post Threat Levels

If post threat level is elevated to DELTA, Contractor must vacate the post, and may not resume construction for as long as 48 hours or as otherwise directed.

1.3.1.2.11 Memorandum

See attached JBM-HH Regulation 190-16, "Installation Access Control," for guidance in obtaining passes.

SECTION 01 14 00 Page 3

1.3.1.2.12 AT Level I Training

1.3.1.2.12.1 General

All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 10 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the Contracting Officer's Representative (COR) or to the Contracting Officer, if a COR is not assigned, within 5 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://jkodirect.jten.mil/Atlas2/faces/page/login/Login.seam

1.3.1.2.12.2 iWATCH Training

The Contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 10 calendar days of contract award and within 2 calendar days of new employees commencing performance with the results reported to the COR Contractor no later than 12 calendar days after contract award.

1.3.1.2.12.3 OPSEC Training

Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 10 calendar days of their reporting for duty and annually thereafter. Level I OPSEC training is available at the following website:

http://cdse.edu/catalog/elearning/GS130.html (Duration: 45 minutes).

1.3.1.2.12.4 Access And General Protection/Security Policy And Procedures

Contractor and all associated sub-contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

1.3.1.2.12.5 Contractors That Do Not Require CAC, But Require Access to a Dod Facility or Installation

Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government

SECTION 01 14 00 Page 4 representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

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 at JBM-HH are 7 a.m. to 4:00 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. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

Funerals ceremonies are conducted between 8:00 a.m and 4:00 p.m.

Therefore depending on where work is being done, such work at Old Post Chapel or Memorial Chapel will only be permitted after 4:00 p.m. unless otherwise 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 UTILITIES

1.3.5.1 1.4.4 Utility Markings

The Contractor shall contact the installation/DPW and the One-Call Service, a minimum of 14 days and 48 hours, respectively, prior to any excavation requesting utility location markings. The Contractor shall not proceed with any excavation until all utilities, including abandoned utilities, have been marked to the satisfaction of the Contracting Officer. Prior to requesting the marking of utilities, the Contractor shall stake out proposed excavations and limits of work with white lines ("White Lining"). It is the Contractor's responsibility to ensure that all permits (excavation or otherwise, including DPW permits) are current and up-to-date without expiration. In addition to the above requirements the Contractor shall:

a) Visually survey and verify that all utility markings are consistent with existing appurtenances such as manholes, valve

SECTION 01 14 00 Page 5 boxes, poles, pedestals, pad-mounted devices, gas meters, etc.

prior to any excavation.

b) Hand dig test holes to verify the depth and location of all utilities prior to any mechanical excavation within the limits of work. Other non-damaging methods for utility verification, as indicated in (d) below, may be considered subject to approval by the Contracting Officer. Also, verify that any abandoned utilities are not active.

c) Preserve all utility markings for the duration of the project to the furthest extent possible.

d) When excavation is performed within 2 feet of any utility line, a non-damaging method of excavation shall be used. The non-damaging method shall be hand digging. Other non-damaging methods, such as, soft digging, vacuum excavation, pneumatic hand tools, may be considered subject to approval by the Contracting Officer.

e) Regardless of the type of excavation, the Contractor shall notify the Contracting Officer a minimum of 72 hours prior to any excavation activity. Failure to notify the Contracting Officer can result in the issuance of a "Stop Work" order, which shall not be justification for contract delay or time extension. The Government reserves the right to have personnel present on site during any type of excavation.

f) The Contractor's Quality Control System Manager shall ensure that all excavation requirements herein are met at the time of the preparatory phase of quality control, and that the excavation procedures are reviewed during the preparatory phase meeting.

This preparatory phase of control shall also establish and document contingency plans and actions to be followed in the event that existing utilities are damaged or interrupted. Locations of shut off or isolation devices along with other safety features shall be established and their operation reviewed.

g) Any work other than excavation in the vicinity of a utility, that could damage or interrupt a utility, such as, exterior or interior work near transformers, power lines, poles, above ground gas lines, gas meters, etc., shall be done with extreme care. The Contractor shall specifically note during the preparatory phase of quality control, the construction techniques to be used to preclude damaging or interrupting any utility. This preparatory phase of control shall also establish and document contingency plans and actions to be followed in the event that existing utilities are damaged or interrupted. Locations of shut off or isolation devices along with other safety features shall be established and their operation reviewed.

h) The Contractor shall complete a risk assessment, using the attached checklist, at least one week prior to the start of any excavation or other work in the vicinity of a utility. The risk assessment shall be submitted for government approval prior to any excavation or other work in the vicinity of a utility. A risk assessment shall be completed for each definable feature of work encountering utilities and shall include all utilities anticipated to be encountered.

SECTION 01 14 00 Page 6

i) See also Sheet GC001 for additional information.

1.3.5.2 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 subparagraph WORK OUTSIDE REGULAR HOURS.

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 7

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

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-11 Closeout Submittals

SWM As-Built Certification Package; G DO

1.2 PROGRESS AND COMPLETION PICTURES

Provide monthly, and within one month of the completion of work, digital photographs in JPEG file format showing the sequence and progress of work. Take a minimum of ten digital photographs prior to the seventh day of each month of views and points located by the Contracting Officer.

Submit a view location sketch indicating points of view. Submit with the monthly invoice two sets of digital photographs each set on a separate CD-R, cumulative of all photos to date. Photographs for each month shall be in a separate monthly directory and each file shall be named to indicate its location on the view location sketch. The view location sketch shall also be provided on the CD as digital file. All file names shall include a date designator.

1.3 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.4 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

SECTION 01 30 00 Page 1 and a list of key and optional personnel who should attend the Partnering meeting.

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

1.6 1.17 PERMITS

The permits listed below have been obtained by the Government or are in the approval process and may require additional action by the Contractor to become complete. After final approvals by the respective state agencies are received, the Government will furnish approval letters and permits to the Contracting Officer who will furnish the Contractor all such permits. 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 VA DEQ for 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 VA DEQ for approval. The permit will be provided the Contractor with the Notice to Proceed. During SWM facility construction, the Contractor is responsible for performing inspections and documenting SWM as-built data. Upon SWM facility construction completion, the Contractor is responsible for certifying, submitting to and obtaining SWM As-Built Certification Approval from VA DEQ. The Contractor shall comply with all VA DEQ as-built certification requirements, including but not limited to as-built redline drawings including an as-built topographic survey which compare the approved stormwater management plan with what was constructed, as-built data tables of all SWM facilities, responding to DEQ comments, and making all necessary revised submittals. The SWM As-Built Certification Package shall be signed and sealed by a Professional Engineer or Professional Land Surveyor registered in the State of Virginia. At VA DEQ's request, the Contractor's hired Professional Engineer is also responsible for revising the stormwater calculations based on as-built data that differs from the design data. The Government can provide the approved SWM Report but will not assist the Contractor. VA DEQ may require additional information; if so, the Contractor shall provide required information at no additional cost to the government. The Contractor shall first submit as-built certification package to the Government for review and approval;

SECTION 01 30 00 Page 2 only after Government approval shall the Contractor submit the certification package to VA DEQ. The Contractor shall not submit VPDES Notice of Termination until stormwater management as-built approval from VA DEQ is received.

c. Virginia Pollutant Discharge Elimination System (VPDES) Application for General Permit to Discharge Stormwater Associated with Construction Activities: The VPDES application will be completed by the Government and submitted to VA DEQ. The VPDES permit will be provided to the Contractor with the Notice to Proceed. Upon the issuance of the Notice to Proceed to the Contractor, the Contractor shall request a Transfer of Authority from Fort Myer DPW through the Contracting Officer. The Government will transfer authority to the Contractor. At completion of the construction contract, the Contractor shall complete a Notice of Termination (NOT), notifying VA DEQ of the end of construction.

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

http://www.epa.gov/npdes/pubs/sw_swppp_guide.pdf.

e. Nontidal Wetlands and Waterways Permit: For the impacts to nontidal wetlands and their buffer, the Government will obtain permit. The permit will be provided to the Contractor upon receipt. The Contractor shall not perform the associated work items covered by the permit until directed by the Contracting Officer.

Applying for and obtaining any and all other permits not above listed, construction or otherwise, shall be the responsibility of, and paid for by, the Contractor.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00 Page 3

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

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.

SECTION 01 32 01.00 10 Page 1

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.

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

3.2.1 Activity Cost Loading

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

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this 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.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

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

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

3.3.3 Procurement Activities

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

3.3.4 Mandatory Tasks

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

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

b. OMITTED

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

d. Long procurement activities

SECTION 01 32 01.00 10 Page 3

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

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

h. OMITTED

i. OMITTED

j. OMITTED

k. OMITTED

l. OMITTED

m. OMITTED

n. OMITTED

o. OMITTED

p. OMITTED

q. OMITTED

r. Contractor's pre-final inspection.

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

t. Government's pre-final inspection.

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

v. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

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

3.3.6 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11 . This exact structure is mandatory. Develop and assign 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:

SECTION 01 32 01.00 10 Page 4

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

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

3.3.6.1 Workers Per Day (WRKP)

Assign Workers per Day for 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.3.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.3.6.3 Area of Work Coding (AREA)

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

Activities cannot have more than one Work Area Code.

SECTION 01 32 01.00 10 Page 5

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.3.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.3.6.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

3.3.6.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are 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.3.6.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to permits, 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.3.6.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved 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.3.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

SECTION 01 32 01.00 10 Page 6 specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

3.3.7.1 Project Start Date Milestone and Constraint

The first activity in the project schedule 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.3.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 way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.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 paragraph Time Extensions for Unusually Severe Weather below.

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.3.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.3.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 the AS and AF dates in the Daily Quality Control report will result in

SECTION 01 32 01.00 10 Page 7 disapproval of the Contractor's schedule.

3.3.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.3.12 Added and Deleted Activities

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

3.3.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.3.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.3.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.3.16 Percent Complete

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

3.3.17 Remaining Duration

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

SECTION 01 32 01.00 10 Page 8

3.3.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.3.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.3.18.2 O & M Manuals

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

3.3.19 Anticipated Adverse Weather

Paragraph applicable to contracts with paragraph Time Extensions for Unusually Severe Weather. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.3.20 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates 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.4 PROJECT SCHEDULE SUBMISSIONS

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

SECTION 01 32 01.00 10 Page 9

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the 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.4.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.4.3 Periodic Schedule Updates

Update the Project Schedule on a regular basis, monthly at a minimum.

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in 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.5 SUBMISSION…