USMA_BLDG_624_Combined_Spec_.pdf

USMA Building 624 HVAC Upgrades

United States Military Academy

West Point, NY

SPECIFICATIONS

BID # W912DS-15-B-0020

5 August 2015

Designed by:

Tetra Tech, Inc.

USMA Building 624 West Point HVAC Renovation

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 01 15 LIST OF DRAWINGS

00 80 00 SPECIAL CONDITIONS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

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

01 62 35 RECYCLED/RECOVERED/BIOBASED MATERIALS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 81 00 TRANSPORTATION AND DISPOSAL OF HAZARDOUS MATERIALS

02 82 14.00 10 ASBESTOS HAZARD CONTROL ACTIVITIES

02 82 16.00 20 ENGINEERING CONTROL OF ASBESTOS CONTAINING MATERIALS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 09 - FINISHES

09 22 00 SUPPORTS FOR GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 65 00 RESILIENT FLOORING

09 90 00 PAINTS AND COATINGS

DIVISION 21 - FIRE SUPPRESSION

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING

23 00 00 AIR SUPPLY, DISTRIBUTION, VENTILATION, AND EXHAUST SYSTEMS

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 08 00.00 10 COMMISSIONING OF HVAC SYSTEMS

PROJECT TABLE OF CONTENTS Page 1

23 09 23 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS

23 21 13.00 20 LOW TEMPERATURE WATER (LTW) HEATING SYSTEM

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 CHILLED, CHILLED-HOT, AND CONDENSER WATER PIPING SYSTEMS

DIVISION 25 - INTEGRATED AUTOMATION

25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END

AND INTEGRATION

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 08 00 APPARATUS INSPECTION AND TESTING

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

DIVISION 27 - COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 74.00 20 INTERIOR FIRE DETECTION AND ALARM SYSTEM

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

SUBMITTAL REGISTER

DOCUMENT 00 01 15

LIST OF DRAWINGS

02/11

PART 1 GENERAL

1.1 SUMMARY

This section lists the drawings for the project pursuant to contract clause "DFARS 252.236-7001, Contract Drawings, Maps and Specifications."

1.2 CONTRACT DRAWINGS

Contract drawings are as follows:

GENERAL

T-001 COVER SHEET, LOCATION MAPS AND SHEET INDEX

G-001 SHEET INDEX

HAZARDOUS MATERIALS ABATEMENT PLAN

H-100 GENERAL NOTES AND SCHEDULE

H-102 DECONTAMINATION UNIT AND ENCLOSURE DETAILS

H-103 BASEMENT PLAN

H-104 PARTIAL 1ST FLOOR PLAN A

H-105 PARTIAL 1ST FLOOR PLAN B

H-106 PARTIAL 1ST FLOOR PLAN C

H-107 PARTIAL 1ST FLOOR PLAN D

H-108 PARTIAL 2ND FLOOR PLAN A

H-109 PARTIAL 2ND FLOOR PLAN B

H-110 PARTIAL 2ND FLOOR PLAN C

H-111 PARTIAL 2ND FLOOR PLAN D

H-112 PARTIAL 3RD FLOOR PLAN A

H-113 PARTIAL 3RD FLOOR PLAN B

ARCHITECTURAL

DOCUMENT 00 01 15 Page 1

GENERAL

A-001 GENERAL ABBREVIATIONS

AD101 FIRST FLOOR DEMOLITION - AREA 'A'

AD102 FIRST FLOOR DEMOLITION - AREA 'B'

AD103 FIRST FLOOR DEMOLITION - AREA 'C'

AD104 FIRST FLOOR DEMOLITION - AREA 'D'

AD105 SECOND FLOOR DEMOLITION - AREA 'A'

AD106 SECOND FLOOR DEMOLITION - AREA 'B'

AD107 SECOND FLOOR DEMOLITION - AREA 'C'

AD108 SECOND FLOOR DEMOLITION - AREA 'D'

A-101 BASEMENT FLOOR PLAN - AREA 'B'

A-102 BASEMENT FLOOR PLAN - AREA 'A'

A-103 FIRST FLOOR - AREA 'B'

A-104 FIRST FLOOR - AREA 'C'

A-105 FIRST FLOOR - AREA 'D'

A-106 SECOND FLOOR AREA 'A'

A-107 SECOND FLOOR AREA 'B'

A-108 SECOND FLOOR AREA 'C'

A-109 SECOND FLOOR AREA 'D'

A-501 WALL PARTITIONS AND DETAILS

MECHANICAL

M-001 MECHANICAL LEGEND AND NOTES

MD101 BASEMENT MECHANICAL DEMOLITION PLAN

MD102 FIRST FLOOR MECHANICAL DEMOLITION PLAN

MD103 SECOND FLOOR MECHANICAL DEMOLITION PLAN

MD104 THIRD FLOOR MECHANICAL DEMOLITION PLAN

MD105 ENLARGED MECHANICAL ROOM DEMOLITION PLAN

DOCUMENT 00 01 15 Page 2

GENERAL

MD106 ENLARGED MECHANICAL ROOM DEMOLITION PLANS

MD107 ENLARGED ROOM MODULE DEMOLITION PLANS

MD108 ENLARGED ROOM MODULE DEMOLITION PLANS

MD109 ENLARGED MECHANICAL ROOM HW AND CW SYSTEM DEMOLITION

PLAN

M-101 BASEMENT HVAC FLOOR PLAN - AREA 'A'

M-102 BASEMENT HVAC FLOOR PLAN - AREA 'B'

M-103 BASEMENT HVAC FLOOR PLAN - AREA 'C'

M-104 FIRST FLOOR HVAC PLAN - AREA 'A'

M-105 FIRST FLOOR HVAC PLAN - AREA 'B'

M-106 FIRST FLOOR HVAC PLAN - AREA 'C'

M-107 FIRST FLOOR HVAC PLAN - AREA 'D'

M-108 SECOND FLOOR HVAC PLAN - AREA 'A'

M-109 SECOND FLOOR HVAC PLAN - AREA 'B'

M-110 SECOND FLOOR HVAC PLAN - AREA 'C'

M-111 SECOND FLOOR HVAC PLAN - AREA 'D'

M-112 THIRD FLOOR HVAC PLAN - AREA 'A'

M-113 THIRD FLOOR HVAC PLAN - AREA 'B'

M-114 THIRD FLOOR HVAC PLAN - AREA 'C'

M-115 THIRD FLOOR HVAC PLAN - AREA 'D'

M-501 MECHANICAL DETAILS

M-502 MECHANICAL DETAILS

M-503 MECHANICAL DETAILS

M-504 MECHANICAL DETAILS

M-505 MECHANICAL DETAILS

M-506 MECHANICAL DETAILS

M-601 MECHANICAL SCHEDULES

DOCUMENT 00 01 15 Page 3

GENERAL

M-602 MECHANICAL SCHEDULES

ELECTRICAL

E-001 ELECTRICAL LEGEND AND NOTES

E-101 BASEMENT ELECTRICAL FLOOR PLAN - AREA 'A'

E-102 BASEMENT ELECTRICAL FLOOR PLAN - AREA 'B'

E-103 BASEMENT ELECTRICAL FLOOR PLAN - AREA 'C'

E-104 FIRST FLOOR ELECTRICAL PLAN - AREA 'A'

E-105 FIRST FLOOR ELECTRICAL PLAN - AREA 'B'

E-106 FIRST FLOOR ELECTRICAL PLAN - AREA 'C'

E-107 FIRST FLOOR ELECTRICAL PLAN - AREA 'D'

E-108 SECOND FLOOR ELECTRICAL PLAN - AREA 'A'

E-109 SECOND FLOOR ELECTRICAL PLAN - AREA 'B'

E-110 SECOND FLOOR ELECTRICAL PLAN - AREA 'C'

E-111 SECOND FLOOR ELECTRICAL PLAN - AREA 'D'

E-112 THIRD FLOOR ELECTRICAL PLAN - AREA 'A'

E-113 THIRD FLOOR ELECTRICAL PLAN - AREA 'B'

E-114 THIRD FLOOR ELECTRICAL PLAN - AREA 'C'

E-115 THIRD FLOOR ELECTRICAL PLAN - AREA 'D'

E-601 ELECTRICAL ONE-LINE DIAGRAM

1.3 SUPPLEMENTARY DRAWINGS

1.3.1 Reference Drawings

The following reference drawings are intended only to show the original construction. Drawings are the property of the Government and shall not be used for any purpose other than that intended by the contract.

Noresco Controls Drawings

-- End of Document --

DOCUMENT 00 01 15 Page 4

SECTION 01 11 00

SUMMARY OF WORK

08/11

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes removal and replacement of Building 624 water chiller;

demolition of the existing dual temperature heating and cooling piping system and terminal fan coil units; installation of new complete chilled water and heating hot water piping systems; and provision and installation of new fan coil terminal heating and cooling equipment. Existing control systems shall be updated or retained to the extent possible with installation of new equipment and control points where needed. and incidental related work.

1.1.2 Location

The work shall be located at the United States Military Academy, Building 624, approximately as indicated. The exact location will be shown by the Contracting Officer.

1.2 OCCUPANCY OF PREMISES

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

Before work is started, the Contractor shall arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

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

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

1.5 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged shall remain the

SECTION 01 11 00 Page 1 property of the Government.

The salvaged property shall be segregated, itemized, delivered, and off-loaded at the Government designated storage area located within 5 miles of the construction site.

Contractor shall maintain property control records for material or equipment designated as salvage. Contractor's system of property control may be used if approved by the Contracting Officer. Contractor shall be responsible for storage and protection of salvaged materials and equipment until disposition by the Contracting Officer.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

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

View location map; G

Progress and completion pictures; G

1.2 VIEW LOCATION MAP

Submit to the Contracting Officer, 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.3 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 8mp 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 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. Indicate photographs demonstrating environmental procedures. 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. Cross reference submittals in the appropriate daily report. Photographs shall be provided for unrestricted use by the Government.

1.4 MINIMUM INSURANCE REQUIREMENTS

Procure and maintain during the entire period of performance under this contract the following minimum insurance coverage:

a. Comprehensive general liability: $500,000 per occurrence

b. Automobile liability: $200,000 per person, $500,000 per occurrence for bodily injury, $20,000 per occurrence for property damage

c. Workmen's compensation as required by Federal and State workers' compensation and occupational disease laws.

SECTION 01 30 00 Page 1

d. Employer's liability coverage of $100,000, except in States where workers compensation may not be written by private carriers,

e. Others as required by NY law.

1.5 CONTRACTOR SPECIAL REQUIREMENTS

1.5.1 Asbestos Containing Material

All contract requirements of Section 02 82 16.00 20, "Engineering Control of Asbestos Containing Materials" assigned to the Private Qualified Person (PQP) shall be accomplished directly by a first tier subcontractor.

1.5.2 Space Temperature Control, HVAC TAB, and Apparatus Inspection

All contract requirements of Section 23 09 23 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS, Section 23 05 93 TESTING, ADJUSTING AND BALANCING FOR HVAC and Section 26 08 00 APPARATUS INSPECTION AND TESTING shall be accomplished directly by a first tier subcontractor, including the Commissioning Agent. No work required by Section 23 09 23, or 23 05 93 shall be accomplished by a second tier subcontractor.

1.6 SUPERVISION

Have at least one qualified supervisor capable of reading, writing, and conversing fluently in the English language on the job site during working hours. In addition, if a Quality Control (QC) representative is required on the contract, then that individual shall also have fluent English communication skills.

1.7 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 shall also attend.

1.8 FACILITY TURNOVER PLANNING MEETINGS (NAVFAC Red Zone - NRZ)

Key personnel will meet to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start the turnover process at the Pre Construction Conference meeting and convene at the Facility Turnover Meetings once the project has reached approximately 75 percent completion or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first. The Contracting Officer's Representative will lead the meetings and guide discussions based on an agenda provided by the Government. The facility Turnover effort shall include the following:

a. Pre Construction Meeting - Contracting Officer's Technical Representative (COTR) will provide the NRZ Checklist and the Contractor, Client, and NAVFAC Representatives will compare Contractor's schedule to NRZ Checklist items.

SECTION 01 30 00 Page 2

b. Facility Turnover Meetings

1. Fill in the NRZ Checklist including Contractor, Client, and NAVFAC Checklist Items and assign a person responsible for each item and a due date. The Contractor's Representative will facilitate the assignment of responsibilities, fill out the NRZ Checklist, and discuss "Interim DD Form 1354" requirements.

2. Review the Contractor's updated schedule. The Contractor shall develop a POAM for the completion of all Contractor, Client, and NAVFAC Checklist items.

3. Confirm that all NRZ Checklist items will be completed on time for the scheduled Facility Turnover.

1.9 AVAILABILITY OF CADD DRAWING FILES

After award and upon request, the electronic "Computer-Aided Drafting and Design (CADD)" drawing files will only be made available to the Contractor for use in preparation of construction drawings and data related to the referenced contract subject to the following terms and conditions.

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

These electronic CADD drawing files are not construction documents.

Differences may exist between the CADD files and the corresponding construction documents. The Government makes no representation regarding the accuracy or completeness of the electronic CADD files, nor does it make representation to the compatibility of these files with the Contractors hardware or software. In the event that a conflict arises between the signed and sealed construction documents prepared by the Government and the furnished CADD files, the signed and sealed construction documents shall govern. The Contractor is responsible for determining if any conflict exists. Use of these CADD files does not relieve the Contractor of duty to fully comply with the contract documents, including and without limitation, the need to check, confirm and coordinate the work of all contractors for the project.

If the Contractor uses, duplicates and/or modifies these electronic CADD files for use in producing construction drawings and data related to this contract, all previous indicia of ownership (seals, logos, signatures, initials and dates) shall be removed.

1.10 ELECTRONIC MAIL (E-MAIL) ADDRESS

The Contractor shall establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments

SECTION 01 30 00 Page 3 in Microsoft, Adobe Acrobat, and other similar formats. Within 10 days after contract award, the Contractor shall 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, terrorist threats, etc. Multiple email address will not be 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). The Contractor shall 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 4

SECTION 01 32 01.00 10

PROJECT SCHEDULE

08/08

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

ER 1-1-11 (1995) 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 Schedule; G

1.3 SCHEDULE PREPARER

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling and have previously developed, created, and maintained at least 2 electronic schedules for projects similar in nature and complexity to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the design and construction sequences, is required. The scheduling of constructiondesign and construction is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development. Subcontractors and suppliersDesigners, Subcontractors and

SECTION 01 32 01.00 10 Page 1 suppliers working on the project shall 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.

3.1.1 Approved Project Schedule

Use the approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions. Make the schedule cost loaded and activity coded. The schedule will provide the basis for all progress payments. If the Contractor fails to submit any schedule within the time prescribed, the Contracting Officer may withhold approval of progress payments until the Contractor submits the required schedule.

3.1.2 Schedule Status Reports

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

3.1.3 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting Officer shall be grounds for a determination, by the Contracting Officer, that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract. Upon making this determination, the Contracting Officer may terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.

3.2 BASIS FOR PAYMENT AND COST LOADING

Use the schedule as the basis for determining contract earnings during each update period and therefore the amount of each progress payment. Lack of an approved schedule update, or qualified scheduling personnel, will result in the inability of the Contracting Officer to evaluate contract earned value for the purposes of payment. Failure of the Contractor to provide all required information will result in the disapproval of the preliminary, initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on the Schedule.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this specification. Comply with PRIMAVERA P6 - USACE MANDATORY REQUIREMENTS.

Failure of the Contractor to meet the requirements of this specification

SECTION 01 32 01.00 10 Page 2 will result in the disapproval of the schedule.

3.3.1 Critical Path Method

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

3.3.2 Level of Detail Required

Develop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer, 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.1 Activity Durations

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

3.3.2.2 Permit Activities

Include permit activities with the necessary conferences and follow-up actions and submission dates. This shall be at a detailed level of scheduling sufficient to identify all major tasks, including those that control the flow of work. The schedule shall include review and correction periods associated with each item.

3.3.2.3 Procurement Activities

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

3.3.2.4 Mandatory Tasks

The following tasks must be included and properly scheduled:

a. Submission, review and acceptance of design packages.

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

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

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

f. Submission and approval of testing and air balance (TAB).

g. Submission of TAB specialist design review report.

SECTION 01 32 01.00 10 Page 3

h. Submission and approval of fire protection specialist.

i. Submission and approval of HVAC testing and balancing and Building Commissioning Plan, test data and reports: Prepare a schedule with integrated logic associated for testing and commissioning of building systems. The schedule shall be at a level of detail which identifies activities and integrates specific activity durations and interdependencies of tasks related to all building testing and commissioning of systems. The logic shall be tied to the overall project schedule and it shall be shown that all tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion. Refer to Figures 1 and 2 as an example of level of detail and associated schedule logic.

j. Air and water balancing.

k. HVAC commissioning.

l. Controls testing plan submission.

m. Controls testing.

n. Performance Verification testing.

o. Other systems testing, if required.

p. Contractor's pre-final inspection.

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

r. Government's pre-final inspection.

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

t. Final inspection.

3.3.2.5 Government Activities

Show Government and other agency activities that could impact progress.

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

3.3.2.6 Activity Responsibility Coding (RESP)

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

SECTION 01 32 01.00 10 Page 4

3.3.2.7 Activity Work Area Coding

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

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

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

(MODF)

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

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

3.3.2.9 Contract Line Item (CLIN) Coding (BIDI)

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

3.3.2.10 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. If the contract specifies construction phasing with separately defined performance periods, identify a Construction Phase Code to allow filtering and organizing the schedule accordingly. Each activity shall be identified with a single project phase and have only one Phase of Work code.

3.3.2.11 Category of Work Coding (CATW)

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

SECTION 01 32 01.00 10 Page 5 activity shall have only one Category of Work Code.

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

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

3.3.3 Scheduled Project Completion and Activity Calendars

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

Original durations must account for anticipated normal adverse weather.

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

3.3.3.1 Project Start Date

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

3.3.3.2 Schedule Constraints and Open Ended Logic

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

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

3.3.3.3 Early Project Completion

In the event the Preliminary or Initial project schedule calculates an early completion date of the last activity prior to the contract completion

SECTION 01 32 01.00 10 Page 6 date, identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

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

3.3.4.2 End Phase

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

3.3.4.3 Phase "X" Hammock

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

3.3.5 Default Progress Data Disallowed

Do not automatically update Actual Start and Finish dates with default mechanisms that may be included in the scheduling software. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the AS and AF dates on the Daily Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's updated schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

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

3.3.6 Out-of-Sequence Progress

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

SECTION 01 32 01.00 10 Page 7 two update cycles by logic revision, as approved by the Contracting Officer.

3.3.7 Negative Lags and Start to Finish Relationships

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

3.3.8 Calculation Mode

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

3.3.9 Milestones

The schedule must include milestone activities for each significant project event including but not limited to: milestone activities for foundation/substructure construction complete; superstructure construction complete; building dry-in or enclosure complete to allow the initiation of finish activities; permanent power complete; and building systems commissioning complete.

3.4 PROJECT SCHEDULE SUBMISSIONS

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

SUBMISSION REQUIREMENTS.

3.4.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 15 calendar days after the NTP is acknowledged. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. Detail it for the first 90 calendar days. It may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as previously specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified 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 permitting activities, and other non-construction activities intended to occur within the first 90 calendar days. Schedule any construction activities planned for the first 90 calendar days after NTP. Constrain planned construction activities and all specified Program and Plan approvals. Activity code any activities that are summary in nature after the first 90 calendar days with Responsibility Code (RESP) and Feature of Work code (FOW1, FOW2, FOW3).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract

SECTION 01 32 01.00 10 Page 8 performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer.

3.4.3 Periodic Schedule Updates

Based on the result of the meeting, specified in PERIODIC SCHEDULE UPDATE MEETINGS, submit periodic schedule updates. These submissions will enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgment of the Contracting Officer or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made.

3.4.4 Standard Activity Coding Dictionary

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

http://rms.usace.army.mil/. The SDEF format is as follows:

SDEF Format

Field Activity Code Length Description

1 WRKP 3 Workers per Day

2 RESP 4 Responsible Party (e.g. GC, subcontractor, USACE)

3 AREA 4 Area of Work

4 MODF 6 Modification or REA number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of Work

7 CATW 1 Category of Work

8 FOW1 10 Feature of Work (used up to 10 characters in length)

9 FOW2 10 Feature of Work (used up to 20 characters in length)

10 FOW3 10 Feature of Work (used up to 30 characters in length)

3.5 SUBMISSION REQUIREMENTS

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

3.5.1 Data CD's

Provide two sets of data CD's containing the project schedule in the backup Primavera P6 format. Each CD shall also contain all previous update backup files. File medium shall be CD. Label each CD indicating the type of

SECTION 01 32 01.00 10 Page 9 schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule shall have a unique file name as determined by the Contractor.

3.5.2 Narrative Report

Provide a Narrative Report with the Preliminary, Initial, and each Periodic Update of the project schedule, as the basis of the progress payment request. The Narrative Report shall include: a description of activities along the 2 most critical paths where the total float is less than or equal to 20 work days, 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. The narrative report is expected to communicate to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis. Identify and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

3.5.3 Approved Changes Verification

Include only those project schedule changes in the schedule submission that have been previously approved by the Contracting Officer. The Narrative Report shall specifically reference, on an activity by activity basis, all changes made since the previous period and relate each change to documented, approved schedule changes.

3.5.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report shall be as directed by the Contracting Officer. Typically reports shall 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. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission.

3.5.4.1 Activity Report

A list of all activities sorted according to activity number.

3.5.4.2 Logic Report

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

3.5.4.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.5.4.4 Earnings Report by CLIN

A compilation of the Contractor's Total Earnings on the project from the NTP to the data date. This report shall reflect the earnings of specific activities based on the agreements made in the schedule update meeting

SECTION 01 32 01.00 10 Page 10 defined herein. Provided that the Contractor has furnished a complete schedule update, this report shall serve as the basis of determining progress payments. Group activities by CLIN item number and sort by activity number. This report shall: sum all activities coded to a particular CLIN and provide a CLIN item percent earned value; and complete and sum CLIN items to provide a total project percent complete. The printed report shall contain, for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), and Earnings to Date.

3.5.5 Network Diagram

The network diagram is required for the Preliminary, Initial and Periodic Updates. The network diagram shall 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.5.5.1 Continuous Flow

Diagrams shall 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.5.5.2 Project Milestone Dates

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

3.5.5.3 Critical Path

Clearly show the critical path.

3.5.5.4 Banding

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

3.5.5.5 S-Curves

Earnings curves showing projected early and late earnings and earnings to date.

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

Conduct periodic schedule update meetings for the purposes of reviewing the Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. Meetings shall occur at least monthly within five days of the proposed schedule data date and after the Contractor has updated the schedule with Government concurrence respecting actual start dates, actual finish dates, remaining durations and percent complete for each activity it intend to status. Provide a computer with the scheduling software loaded and a projector during the meeting which allows all meeting participants to view the proposed schedule update during the meeting. The meeting and resultant approvable schedule update shall be a condition precedent to a formal submission of the update as described in SUBMISSION REQUIREMENTS and to the submission of an invoice for payment. The meeting will be a working

SECTION 01 32 01.00 10 Page 11 interactive exchange which will allow the Government and the Contractor the opportunity to review the updated schedule on a real time and interactive basis. The Contractor's authorized scheduling representative will organize, sort, filter and schedule the update as requested by the Government. The meeting will last no longer than 8 hours. A rough draft of the proposed activity logic corrections and narrative report shall be provided to the Government 48 hours in advance of the meeting. The Contractor's Project Manager and Authorized Scheduler shall attend the meeting with the Authorized Representative of the Contracting Officer.

3.6.1 Update Submission Following Progress Meeting

Submit a complete update of the project schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 working days after the periodic schedule update meeting, reflecting only those changes made during the previous update meeting.

3.6.2 Status of Activities

Update information, including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete shall be subject to the approval of the Government prior to the meeting. As a minimum, address the following items on an activity by activity basis during each progress meeting.

3.6.2.1 Start and Finish Dates

Accurately show the status of the AS and/or AF dates for each activity currently in-progress or completed since the last update. The Government may allow an AF date to be assigned with the percent complete less than 100 percent to account for the value of work remaining but not restraining successor activities. Only assign AS dates when actual progress occurs on an activity.

3.6.2.2 Remaining Duration

Update the estimated RD for all incomplete activities independent of Percent Complete. Remaining Durations may exceed the activity OD or may exceed the activity's prior update RD if the Government considers the current OD or RD to be understated based on current progress, insufficient work crews…