Atch_9_Appendix_5a_–_SI_2152_Tracy_Specification.pdf

HVAC COMBINED ASA105

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 00 00 GENERAL REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 16 DESIGN AFTER AWARD

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 QUALITY CONTROL

01 45 00.15 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 91 00.15 TOTAL BUILDING COMMISSIONING

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 82 13 ASBESTOS ABATEMENT

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS

23 21 23 HYDRONIC PUMPS

23 23 00 REFRIGERANT PIPING

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

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

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1 l2ctaas9 Typewritten Text 05/15/2018

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 00 00

GENERAL REQUIREMENTS

05/17

PART 1 GENERAL

1.1 REFERENCES

1.2 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS OF ENGINEERS

CONTRACTS

1.3 SCRAP MATERIAL

1.4 WRITTEN GUARANTEES AND GUARANTOR'S LOCAL REPRESENTATIVE

1.5 PRICING OF CONTRACTOR-FURNISHED PROPERTY

1.6 TEMPORARY ELECTRIC WIRING

1.6.1 Temporary Power and Lighting

1.6.2 Construction Equipment

1.6.3 Circuit Protection

1.7 UTILITIES

1.8 PLANNED UTILITY OUTAGES AND STREET CLOSURES

1.9 EXCAVATION PERMITS

1.10 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER

1.11 SPECIAL CONSTRUCTION PROCEDURES

1.12 HAZARDOUS NOISE AREA

1.13 COLOR SCHEME FOR CONTRACTOR FACILITIES

PART 2 PRODUCTS

2.1 GOVERNMENT FURNISHED MATERIALS

PART 3 EXECUTION

3.1 AFTER AWARD DOCUMENTS

-- End of Section Table of Contents --

01 00 00 - 1

SECTION 01 00 00

GENERAL REQUIREMENTS

05/17

PART 1 GENERAL

1.1 REFERENCES

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

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2017; ERTA 1-2 2017; TIA 17-1; TIA 17-2)

National Electrical Code

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

ER 415-1-15 (1989) Construction Time Extensions for Weather

1.2 VETERANS EMPLOYMENT EMPHASIS FOR U.S. ARMY CORPS OF ENGINEERS CONTRACTS

In addition to complying with the requirements outlined in FAR Part 22.13, FAR Provision 52.222-38, FAR Clause 52.222-35, FAR Clause 52.222-37, DFARS

222.13 and Department of Labor regulations, U.S. Army Corps of Engineers (USACE) contractors and subcontractors at all tiers are encouraged to promote the training and employment of U.S. veterans while performing under a USACE contract. While no set-aside, evaluation preference, or incentive applies to the solicitation or performance under the resultant contract, USACE contractors are encouraged to seek out highly qualified veterans to perform services under this contract. The following resources are available to assist USACE contractors in their outreach efforts:

Federal Veteran employment information at http://www.fedshirevets.gov/index.aspx

Department of Labor Veterans Employment Assistance http://www.dol.gov/vets/

Department of Veterans Affairs-VOW to Hire Heros Act http://benefits.va.gov/vow/

Army Wounded Warrior Program -http://wtc.army.mil/modules/employers/index.html

U.S. Chamber of Commerce Foundation-Hiring Our Heros http://www.hiringourheroes.org/

Guide to Hiring Veterans - Reference Material http://www.whitehouse.gov/sites/default/files/docs/white_house

01 00 00 - 2

_business_council_-_guide_to_hiring_veterans_0.pdf

1.3 SCRAP MATERIAL

Materials specified to be removed and become the property of the Contractor are designated as scrap, and the Contractor, by signing this contract, hereby acknowledges that he has made due allowance for value, if any, of such scrap in the contract price.

1.4 WRITTEN GUARANTEES AND GUARANTOR'S LOCAL REPRESENTATIVE

Prior to completion of the contract, obtain and furnish to the Contracting Officer's representative written guarantees for all the equipment and/or appliances furnished under the contract. Furnish with each guarantee: The name, address, and telephone number of the guarantor's representative nearest to the location where the equipment and/or appliances are installed, who, upon request of the Using Service's representative, will honor the guarantee during the guaranty period and will provide the services prescribed by the terms of the guarantee.

1.5 PRICING OF CONTRACTOR-FURNISHED PROPERTY

At the request of the Contracting Officer, promptly furnish and must cause any subcontractors to furnish, in like manner, unit prices and descriptive data required by the Government for property record purposes of fixtures and equipment furnished and installed by the Contractor.

1.6 TEMPORARY ELECTRIC WIRING

1.6.1 Temporary Power and Lighting

Provide construction power facilities in accordance with the safety requirements of the NFPA 70 and EM 385-1-1. Enforce all the safety requirements of electrical extensions for the work of all subcontractors.

All work must be accomplished by skilled electrical tradesmen in a workmanlike manner, as approved by the Contracting Officer.

1.6.2 Construction Equipment

In addition to the requirements of EM 385-1-1, all temporary wiring conductors installed for operation of construction tools and equipment must be either Type TW or THW contained in metal raceways, or may be multiconductor cord. Temporary wiring must be secured above the ground or floor in a workmanlike manner and must not present an obstacle to persons or equipment. Open wiring may only be used outside of buildings, and then only in strict accordance with the provisions of the National Electrical Code.

1.6.3 Circuit Protection

In addition to the present requirements in EM 385-1-1 and NFPA 70, all 15 and 20-ampere receptacle outlets used for obtaining power during construction must have ground fault circuit interrupters (GFCI) for personnel protection. Block and brick saws must also be equipped with GFCI. The Contracting Officer may allow an exception to this requirement for circuits for concrete vibrators or circuits operating at other than 60 Hertz normal (in both cases an assured grounding program as described in the NFPA 70, except utilizing the daily inspection frequency of the grounding means of such equipment, may be permitted). The assured

01 00 00 - 3 grounding program will not be permitted as a substitute for usage of GFCI'S except as described above. All generator-powered 15- and 20-ampere, 60 Hertz receptacle outlets must have GFCI'S, and must be properly grounded.

Provide a testing means which will impose a measured fault of 5 milliamperes, plus or minus 1 milliamperes, and result in tripping the GFCI unit.

1.7 UTILITIES

Immediately notify the Contracting Officer in writing if utilities not shown on the plans and not visible as to the date of this contract are encountered within the construction limits of the entire project, and such utilities will interfere with construction operations, to enable a determination by the Contracting Officer as to the necessity for removal or relocation. If such utilities are removed or relocated as directed by the Contracting Officer, an equitable adjustment in the contract price must be made pursuant to the Contract Clause CHANGES to cover the cost of any additional pertinent work or delay.

1.8 PLANNED UTILITY OUTAGES AND STREET CLOSURES

Power outages must be restricted to off-duty hours and weekends. Other utilities may be connected and streets closed during normal working hours with the outage duration and street closure as short as possible. All outages and street closures must be scheduled as far in advance as possible with the Contracting Officer and in no case less than 7 days before the outage or closure. Obtain in writing from the Contracting Officer a statement or schedule giving the permissible times of utility outages or road closures for particular installations and the maximum time allowed for such outage. Strictly observe such schedules and will be held responsible for any violations.

1.9 EXCAVATION PERMITS

All excavation permits will be issued to the Contractor from the Directorate of Engineering and Housing (DEH), through the Contracting Officer. The appropriate form, for this request, may be obtained from the Contracting Officer. Processing time required is 14 calendar days.

Questions concerning the excavation permit should be directed to the Contracting Officer.

1.10 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER

a.This provision specifies the procedure for the determination of time extensions for unusually severe weather. In order for the Contracting Officer to award a time extension under this clause, the following conditions must be satisfied:

1. The weather experienced at the project site during the contract period must be found to be unusually severe, that is, more severe than the adverse weather anticipated for the project location during any given month.

2. The unusually severe weather must actually cause a delay to the completion of the project. The delay must be beyond the control and without the fault or negligence of the Contractor.

b. The following schedule of monthly anticipated adverse weather delays is

01 00 00 - 4 based on National Oceanic and Atmospheric Administration (NOAA) or similar data for the project location and will constitute the base line for monthly weather time evaluations. The Contractor's progress schedule must reflect these anticipated adverse weather delays in all weather dependent activities.

MONTHLY ANTICIPATED ADVERSE WEATHER DELAY

WORK DAYS BASED ON (5) DAY WORK WEEK

TRACY DEFENSE DEPOT/TRACY CARBONA

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

c. Upon execution of the Notice to Proceed (NTP) and continuing throughout the contract, the Contractor will record on the daily CQC report, the occurrence of adverse weather and resultant impact to normally scheduled work. Actual adverse weather delay days must prevent work on critical activities for 50 percent or more of the Contractor's scheduled work day. Refer to ER 415-1-15.

1.11 SPECIAL CONSTRUCTION PROCEDURES

a. Contractor - Visitor Badges

(1) Contractors will apply for badges at the Security Operations Pass & ID Office, Tracy Facility. Contractors may be required to submit Security Form DD 3988-2, National Agency Questionnaire (NAQ), for all proposed superintendents and/or foremen, at least one week prior to initiation of work and prior to badges being issued. This form may be obtained at the Pass & ID Office. When applying for a badge, contractor and subcontractor, personnel must present a drivers license or another identification card with a photograph, and a copy of the contract. Badges will be issued to and worn by supervisors and/or foreman who will be responsible for the conduct of their crew while on DDRW San Joaquin Facilities (Sharpe and Tracy).

(2) A minimum of one week prior to entry and initiation of work on San Joaquin Facilities, the Prime Contractor must submit a list of all prime and subcontractor employees including any other personnel required to perform work on San Joaquin Facilities during the contract performance period. The list is to be submitted to both the Contracting Officer Representative (COR), and to the Security Office, Building 1A, for construction at the Tracy Facility. If personnel are added or changed during the contract performance period, a revised list is to be submitted prior to any new employees' arrival for work at San Joaquin Facilities, Security may refuse entry to employees not on the employee list.

(3) Badges will be issued for the contract performance period. A check will be made periodically by Security on the status of these badges. Normally, on projects longer than one month, a badge will be issued to the Prime Contractor's superintendents or foreman.

Normally, on projects of one month or less, a badge will be issued only to the Prime Contractor's superintendent. The Security Office may approve additional badges on service contracts and on particularly large or complex construction projects.

(4) All Prime Contractor and subcontractor employees will be required

01 00 00 - 5 to sign in the first day at Pass & ID Office (Building 1A at Tracy). During the contract performance period, a contractor employee with a badge will be required to escort employees without badges between the gate and the project site.

(5) Suppliers, vendors, or other one-time or occasional visitors do not need to be escorted to the project site; however, a contractor employee with a badge must notify the Security Officer at the gate. Notification will be done on the day of the visit, and include the name of the company and the nature of the visit.

Security may refuse entry without this notification.

(6) All expired or unnecessary badges will be returned to the issuing office. The Contractor agrees to pay a replacement fee of $22.00 for each badge not returned.

1.12 HAZARDOUS NOISE AREA

Work area for this contract is located within a high noise area and can be hazardous to the human ear. The Contractor is responsible for providing adequate ear protection as may be required for Contractor's personnel at the job site.

1.13 COLOR SCHEME FOR CONTRACTOR FACILITIES

a. All Contractor storage and operational facilities including temporary structures, signs and fencing, that remain at the site must be compatible with the color scheme used on the project signs as directed by the Contracting Officer.

PART 2 PRODUCTS

2.1 GOVERNMENT FURNISHED MATERIALS

The Government will provide an optical disc at the preconstruction conference that contains the materials specifed in SECTION 01 78 00

CLOSEOUT SUBMITTALS

PART 3 EXECUTION

3.1 AFTER AWARD DOCUMENTS

Provide hard copy sets in the quantities identified in Scope of Work reproduced from the PDF Contract Documents provided by the Contracting Officer at the time of award. The hard copy drawings must be sets of ANSI D (22" x 34")and sets of half size (11" x 17") 3-hole punched and bound with metal posts. The sets of specifications must be standard letter (8-1/2" x 11") 3-hole punched and bound with metal posts. Submit these documents within 5 work days after the Government releases the Contractor's design for construction.

Provide the Resident Engineer a copy ("hard" and "PDF") of the signed Bond and Notice to Proceed within 5 working days after receipt from the Contracting Officer.

-- End of Section --

01 00 00 - 6

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.1.1 Schedule Status Reports

3.1.2 Default Terms

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Design and Permit Activities

3.3.4 Procurement Activities

3.3.5 Mandatory Tasks

3.3.6 Government Activities

3.3.7 Standard Activity Coding Dictionary

3.3.7.1 Workers Per Day (WRKP)

3.3.7.2 Responsible Party Coding (RESP)

3.3.7.3 Area of Work Coding (AREA)

3.3.7.4 Modification Number (MODF)

3.3.7.5 Bid Item Coding (BIDI)

3.3.7.6 Phase of Work Coding (PHAS)

3.3.7.7 Category of Work Coding (CATW)

3.3.7.8 Feature of Work Coding (FOW)

3.3.8 Contract Milestones and Constraints

3.3.8.1 Project Start Date Milestone and Constraint

3.3.8.2 End Project Finish Milestone and Constraint

3.3.8.3 Interim Completion Dates and Constraints

3.3.8.3.1 Start Phase

3.3.8.3.2 Design phase

3.3.8.3.3 End Phase

3.3.9 Calendars

01 32 01 - 1

3.3.10 Open Ended Logic

3.3.11 Default Progress Data Disallowed

3.3.12 Out-of-Sequence Progress

3.3.13 Added and Deleted Activities

3.3.14 Original Durations

3.3.15 Leads, Lags, and Start to Finish Relationships

3.3.16 Retained Logic

3.3.17 Percent Complete

3.3.18 Remaining Duration

3.3.19 Cost Loading of Closeout Activities

3.3.19.1 As-Built Drawings

3.3.19.2 O & M Manuals

3.3.20 Anticipated Adverse Weather

3.3.21 Early Completion Schedule and the Right to Finish Early

3.4 CONTRACTS WITH MULTIPLE BUILDINGS/FACILITIES

3.5 PROJECT SCHEDULE SUBMISSIONS

3.5.1 Preliminary Project Schedule Submission

3.5.2 Initial Project Schedule Submission

3.5.2.1 Design Package Schedule Submission

3.5.3 Periodic Schedule Updates

3.6 SUBMISSION REQUIREMENTS

3.6.1 Data Optical Discs

3.6.2 Narrative Report

3.6.3 Schedule Reports

3.6.3.1 Activity Report

3.6.3.2 Logic Report

3.6.3.3 Total Float Report

3.6.3.4 Earnings Report by CLIN

3.6.3.5 Schedule Log

3.6.4 Network Diagram

3.6.4.1 Continuous Flow

3.6.4.2 Project Milestone Dates

3.6.4.3 Critical Path

3.6.4.4 Banding

3.6.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

3.7 PERIODIC SCHEDULE UPDATE

3.7.1 Periodic Schedule Update Meetings

3.7.2 Update Submission Following Progress Meeting

3.8 WEEKLY PROGRESS MEETINGS

3.9 REQUESTS FOR TIME EXTENSIONS

3.9.1 Justification of Delay

3.9.2 Submission Requirements

3.9.3 Time Impact Analysis (Prospective Analysis)

3.9.4 Forensic Schedule Analysis (Retrospective Analysis)

3.9.5 Fragmentary Network (Fragnet)

3.9.6 Time Extension

3.9.7 Impact to Early Completion Schedule

3.10 FAILURE TO ACHIEVE PROGRESS

3.10.1 Artificially Improving Progress

3.10.2 Failure to Perform

3.10.3 Recovery Schedule

3.11 OWNERSHIP OF FLOAT

3.12 TRANSFER OF SCHEDULE DATA INTO RMS CM

3.13 PRIMAVERA P6 MANDATORY REQUIREMENTS

01 32 01 - 2

SECTION 01 32 01

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Bar Chart Schedule

Project Schedule; G

Design Package Schedule; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Data Optical Discs

Periodic Schedule Update; G

Justification of Delay; G

Time Impact Analysis; G

Forensic Schedule Analysis; G

01 32 01 - 3

Schedule Status Report; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

PART 2 PRODUCTS

2.1 SOFTWARE

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

2.1.1 Government Default Software

The Government intends to use Primavera P6, Release 7.0. Save all files in the Primavera PM XER format.

2.1.2 Contractor Software

Use commercially available scheduling software 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 design and construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Designers, 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

01 32 01 - 4

Path Method (CPM) of network calculation to generate all Project Schedules. Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.1.1 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.2 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting Officer must 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

The approved Project Schedule is 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 to provide all required information will result in the disapproval of the preliminary, initial and subsequent schedule updates. The aggregate value of all activities coded to a contract Contract Line Item Schedule (CLIN) must equal the value of the CLIN.

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.

01 32 01 - 5

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 must have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Design and Permit Activities

Include design and permit activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period. Provide at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work.

Also include review and correction periods associated with each item.

3.3.4 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.5 Mandatory Tasks

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

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

b. Submission, review and acceptance of design packages.

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

d. Long procurement activities

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

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

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

i. Submission of TAB specialist design review report.

01 32 01 - 6

j. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

k. Air and water balancing.

l. Building commissioning - Functional Performance Testing.

m. Controls testing plan submission.

n. Controls testing.

o. Performance Verification testing.

p. Other systems testing, if required.

q. Contractor's pre-final inspection.

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

s. Government's pre-final inspection.

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

u. Final inspection.

3.3.6 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: acceptance, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements. Show Government approval of shop drawings activities with at least the minimum duration allowed by the contract.

Failure to provide reasonable durations in the schedule for Government activities does not establish or change the Government's review or approval path periods and the durations established for Government's activities are subject to approval by the Contracting Officer.

Allow 30 calendar days total duration prior to current contract completion date for the following activities. Refer to specification Section 01 45 00 QUALITY CONTROL. Include and properly schedule the following critical tasks:

a. Submission of Contractor Quality Control (CQC) for all mechanical/electrical/information systems tests.

b. Government QA for all mechanical systems acceptance/operational tests.

c. Government QA for all electrical systems acceptance/operational tests.

d. CQC completion inspection of the entire project.

e. Contractor works off CQC punchlist.

01 32 01 - 7

f. Prefinal inspection performed when the facility is completed such that it can be used for it intended function, as determined by the Contracting Officer.

g. Contractor works off prefinal punchlist.

h. Final/acceptance inspection of the entire project.

i. Contractor works off final punchlist.

3.3.7 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 must activities as detailed herein. A template SDEF compatible schedule backup file is available on the RMS CM web site: http://rms.usace.army.mil.

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

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

01 32 01 - 8

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.7.3 Area of Work Coding (AREA)

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

Activities cannot have more than one Work Area Code.

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

3.3.7.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.7.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.7.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are design phase, 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.7.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 design, design submittal, design reviews, review conferences, permits, construction submittals, procurement, 01 32 01 - 9 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.7.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 QUALITY CONTROL.

An activity can have only one Feature of Work Code.

3.3.8 Contract Milestones and Constraints

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

Mandatory constraints that ignore or effect network logic are prohibited.

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

3.3.8.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Executed," which must have a "Start On" constraint date equal to the date that the NTP is executed by the Contracting Officer.

3.3.8.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.3 Interim Completion Dates and Constraints

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

3.3.8.3.1 Start Phase

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

3.3.8.3.2 Design phase

Include the following design phase activities in the composite design and construction Project schedule. The duration of each of these activities

01 32 01 - 10 must be the duration as included in the contract award.

Prework conference within 5 days after NTP

Design Charrette (Preliminary Design) within 7 days after NTP

Submittal of Final design (95 percent)

Design review conference of Final design

Submittal of Corrected Final design (100 percent)

Design review conference of Corrected Final design

Design Complete

3.3.8.3.3 End Phase

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

3.3.9 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 seasonal Calendar(s) and assign to seasonally affected activities as applicable.

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

3.3.10 Open Ended Logic

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

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

3.3.11 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 disapproval of the Contractor's schedule.

01 32 01 - 11

3.3.12 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.13 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.14 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.15 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.16 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.17 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.18 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.

01 32 01 - 12

3.3.19 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.19.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.19.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.20 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.3.21 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 CONTRACTS WITH MULTIPLE BUILDINGS/FACILITIES

Prepare a separate detailed schedule for each building/facility indicating its critical path for specified interim completion dates or critical milestone date. The master schedule must indicate the interface/lag/link between buildings/facilities to maximize/level the labor and other resources. The master schedule critical path must be indicated through the various buildings/facilities and total duration equal to the contract duration.

3.5 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. Submit a bar chart schedule for the first 30 calendar days of the contract at the Preconstruction conference. The data Optical Disc, reports, and network diagrams required

01 32 01 - 13 for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

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

3.5.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule within 15 calendar days after the NTP is executed defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP.

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

Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.5.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. Include in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews and conferences; permit submissions and any required Government actions; and long lead item acquisition prior to design completion. Also cover in the preliminary design-build schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. As the design proceeds and design packages are developed, fully detail the remaining construction activities concurrent with the monthly schedule updating process. Constrain construction activities by Government acceptance of associated designs. When the design is complete, incorporate into the then approved schedule update all remaining detailed construction activities that are planned to occur after the dry-in milestone. If applicable, include in the design-build schedule detailed design and permitting activities, including but not limited to identification of individual design packages, design submission, reviews and conferences, permit submissions and any required Government actions, and long lead item acquisition prior to design completion. Also cover in the preliminary

01 32 01 - 14 design-build schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities through the dry-in milestone, including all activity coding and cost loading. Include the remaining construction, including cost loading, but it may be scheduled summary in nature. As the design proceeds and design packages are developed, fully detail the remaining construction activities. No payment will be made for work items not fully detailed in the Project Schedule.

3.5.2.1 Design Package Schedule Submission

With each design package submitted to the Government, submit a fragnet schedule extracted from the then current Preliminary, Initial or Updated schedule which covers the activities associated with that Design Package including construction, procurement and permitting activities.

3.5.3 Periodic Schedule Updates

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

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS.

These updates will enable the Government to assess Contractor's progress.

Update the schedule to include detailed construction activities as the design progresses, but not later than the submission of the final un-reviewed design submission for each separate design package. The Contracting Officer may require submission of detailed schedule activities for any distinct construction that is started prior to submission of a final design submission if such activity is authorized.

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

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

3.6 SUBMISSION REQUIREMENTS

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

3.6.1 Data Optical Discs

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

3.6.2 Narrative Report

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

01 32 01 - 15

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

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

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

d. Identify and explain why activities based on their calculated late dates…