63095_Site_Final_Specs.pdf

PDF 2 MB Posted

Attached to
Site work for temporary hospital building Joplin MO
Solicitation number
W912DS-12-R-0002
Issued by

About this file

W912DS-12-R-0002 Specs

View the file

Other files

File Type Posted
St John's Interim Hospital Dv Lay.pdf PDF
W912DS-12-R-0002 0008.pdf PDF
W912DS-12-R-0002 0007.pdf PDF
W912DS-12-R-0002 0006.pdf PDF
W912DS-12-R-0002 0005.pdf PDF
W912DS-12-R-0002 0004.pdf PDF
W912DS-12-R-0002 0003.pdf PDF
Site Visit - Sign-in Sheet - dtd 2011-10-25.pdf PDF
W912DS-12-R-0002 0002.pdf PDF
E505 ELECTRICAL DETAILS.pdf PDF
1980DR_E502.pdf PDF
1980DR_ES101.pdf PDF
1980DR_GI_CVR.pdf PDF
26 20 00.pdf PDF
63095_Site_Add01.pdf PDF
22 00 70.pdf PDF
W912DS-12-R-0002 0001.pdf PDF
00902.pdf PDF
10 14 01.pdf PDF
33 40 00.pdf PDF
00901.pdf PDF
33 70 02.00 10.pdf PDF
63095_Site_Final_Dwgs.pdf PDF
W912DS-12-R-0002.pdf PDF
Show all 24

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

1980DR-MO-COE-NPD-07-TO#6

New York District

St. John’s Temporary Hospital Facility Joplin, MO Contract No. W912DQ-08-D-0063 Task Order No. CE02 Solicitation No. W912DS-12-R-0002

Site Development Design Complete Specifications

September 2011

Submitted by:

Burns and McDonnell

9400 Ward Parkway Kansas City, MO 64114

Tel: 816-333-9400 Certification: 000165

St. John's Interim Hospital Site Design Joplin, MO

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 20 00.00 20 PRICE AND PAYMENT PROCEDURES

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

01 45 00.10 10 QUALITY CONTROL SYSTEM (QCS)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 20.00 10 ENVIRONMENTAL PROTECTION

01 57 23 TEMPORARY STORM WATER POLLUTION CONTROL

01 62 35 RECYCLED / RECOVERED MATERIALS

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

DIVISION 03 - CONCRETE

03 30 53 MISCELLANEOUS CAST-IN-PLACE CONCRETE

03 40 00.00 10 PLANT-PRECAST CONCRETE PRODUCTS FOR BELOW GRADE

CONSTRUCTION

DIVISION 22 - PLUMBING

22 60 70 GAS AND VACUUM SYSTEMS FOR HEALTHCARE FACILITIES

22 66 53.00 40 LABORATORY CHEMICAL-WASTE AND VENT PIPING

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 54 21.00 10 HELIPAD LIGHTING AND VISUAL NAVIGATION AIDS

26 56 00 EXTERIOR LIGHTING

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 32 11 SOIL SURFACE EROSION CONTROL

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 19 FIELD MOLDED SEALANTS FOR SEALING JOINTS IN RIGID

PAVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 11 23 AGGREGATE BASE COURSE

32 12 10 BITUMINOUS TACK COAT

32 12 16 HOT-MIX ASPHALT (HMA) FOR ROADS

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 17 23.00 20 PAVEMENT MARKINGS

32 31 13 CHAIN LINK AND PVC FENCES AND GATES

PROJECT TABLE OF CONTENTS Page 1

32 92 19 SEEDING

DIVISION 33 - UTILITIES

33 11 00 WATER DISTRIBUTION

33 11 23 NATURAL GAS AND LIQUID PETROLEUM PIPING

33 30 00 SANITARY SEWERS

33 40 00 STORM DRAINAGE UTILITIES

33 70 02.00 10 ELECTRICAL DISTRIBUTION SYSTEM, UNDERGROUND

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

SECTION 01 11 00

SUMMARY OF WORK

08/11

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.

ASTM INTERNATIONAL (ASTM)

ASTM E 2114 (2008) Standard Terminology for Sustainability Relative to the Performance of Buildings

1.2 DEFINITIONS

Definitions pertaining to sustainable development are as defined in ASTM E 2114, Section 01 57 20.00 10 ENVIRONMENTAL PROTECTION, and as specified.

a. "Environmentally preferable products" have a lesser or reduced effect on the environment in comparison to conventional products and services. This comparison may consider raw materials acquisition, production, manufacturing, packaging, distribution, reuse, operation, maintenance, or disposal of the product.

b. "Indoor environmental quality" is the physical characteristics of the building interior that impact occupants, including air quality, illumination, acoustics, occupant control, thermal comfort, daylighting, and views.

c. "Operational performance" is the functional behavior of the building as a whole or of the building components.

d. "Sustainability" is the balance of environmental, economic, and societal considerations.

1.3 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. The following shall be submitted in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Upon receipt of Government Furnished Equipment, the Contractor shall submit records in accordance with paragraph entitled, "Government Furnished Property," of this section.

Submit the following items to the Contracting Officer:

Utility Outage Requests

63095SITE SECTION 01 11 00 Page 1

Utility Connection Requests

Borrow Permits

Excavation Permits

Welding Permits

Burning Permits

1.4 WORK COVERED BY CONTRACT DOCUMENTS

1.4.1 Project Description

The work includes site development for the Interim St. John's Hospital Building in Joplin, MO. Sitework includes all excavation, grading, drainage, site utilities, roadways, parking lots, curbs, sidewalks and other miscellaneous site improvements and incidental related work.

1.4.2 Location

The work shall be located at the St. John's Interim Hospital Site located in Joplin, MO, approximately as indicated on the drawings. The exact location will be shown by the Contracting Officer.

1.5 WORK RESCHEDULING

Contractor shall allow for a maximum of [_____] calendar days where construction activity is prohibitive. Further allowance for [_____] calendar days of excavation and subsurface activity abeyance shall be imposed where other construction activities are permitted. Government will provide 24-hour notification each time the restrictions are invoked.

Normal duty hours for work shall be from [_____] a.m. to [_____] p.m., Monday through Friday. Requests for additional work shall require written approval from the Contracting Officer 7 days in advance of the proposed work period.

1.6 PROJECT ENVIRONMENTAL GOALS

Contractor shall distribute copies of the Environmental Goals to each subcontractor and the Contracting Officer. The overall goal for design, construction, and operation is to produce a building that meets the functional program needs and incorporates the principles of sustainability. Specifically:

a. Preserve and restore the site ecosystem and biodiversity; avoid site degradation and erosion. Minimize offsite environmental impact.

b. Use the minimum amount of energy, water, and materials feasible to meet the design intent. Select energy and water efficient equipment and strategies.

c. Use environmentally preferable products and decrease toxicity level of materials used.

d. Use renewable energy and material resources.

63095SITE SECTION 01 11 00 Page 2

e. Optimize operational performance (through commissioning efforts) in order to ensure energy efficient equipment operates as intended.

Consider the durability, maintainability, and flexibility of building systems.

f. Manage construction site and storage of materials to ensure no negative impact on the indoor environmental quality of the building.

g. Reduce construction waste through reuse, recycling, and supplier take-back.

1.7 OCCUPANCY OF PREMISES

Building(s) will 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.8 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.9 ON-SITE PERMITS

1.9.1 Utility Outage Requests and Utility Connection Requests

Notify the Contracting Officer at least 72 hours prior to starting excavation work. Contractor is responsible for marking and verifying all utilities not marked.

The Contractor shall verify the elevations of existing piping, utilities, and any type of underground obstruction not indicated or specified to be removed. But indicated in locations to be transversed by piping, ducts, and other work to be installed. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.

Work shall be scheduled to hold outages to a minimum.

Utility outages and connections required during the prosecution of work that affect existing systems shall be arranged for at the convenience of the Government and shall be scheduled outside the regular working hours or on weekends.

Contractor shall not be entitled to additional payment for utility outages and connections required to be performed outside the regular work hours.

Requests for utility outages and connections shall be made in writing to

63095SITE SECTION 01 11 00 Page 3 the Contracting Officer at least 7 calendar days in advance of the time required. Each request shall state the system involved, area involved, approximate duration of outage, and the nature of work involved.

1.9.2 Borrow, Excavation, Welding, and Burning Permits

ACTIVITY SUBMISSION DATE SUBMISSION FORM

[Borrow Permits [_____] calendar days prior to work [_____]] [Burning Permits [_____] calendar days prior to work [_____]] [Excavation Permits [_____] calendar days prior to work [_____]] [Welding Permits [_____] calendar days prior to work [_____]]

Permits shall be posted at a conspicuous location in the construction area.

Burning of trash or rubbish is not permitted on project site.

1.10 LOCATION OF UNDERGROUND FACILITIES

Obtain digging permits prior to start of excavation by contacting the Contracting Officer 15 calendar days in advance. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.

1.10.1 Notification Prior to Excavation

Notify the Contracting Officer at least 48 hours prior to starting excavation work.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

63095SITE SECTION 01 11 00 Page 4

SECTION 01 20 00.00 20

PRICE AND PAYMENT PROCEDURES

08/11

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)

EP-1110-1-8 (2009) Construction Equipment Ownership and Operating Expense Schedule

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. The following shall be submitted in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Earned Value Report; G

1.3 EARNED VALUE REPORT

1.3.1 Data Required

This contract requires the use of a cost-loaded Network Analysis Schedule (NAS). The information required for the Schedule of Prices will be entered as an integral part of the Network Analysis Schedule. Within 15 calendar days of notice of award, prepare and deliver to the Contracting Officer an Earned Value Report (construction contract) as directed by the Contracting Officer. Provide a detailed breakdown of the contract price, giving quantities for each of the various kinds of work, unit prices, and extended prices. Costs shall be summarized and totals provided for each construction category.

1.3.2 Schedule Instructions

Payments will not be made until the Earned Value Report from the cost-loaded NAS has been submitted to and accepted by the Contracting Officer. Identify the cost for site work, and include incidental work to the 5 ft line. Identify costs for the building(s), and include work out to the 5 ft line. Work out to the 5 ft line shall include construction encompassed within a theoretical line 5 ft from the face of exterior walls and shall include attendant construction, such as pad mounted HVAC cooling equipment, cooling towers, and transformers placed beyond the 5 ft line.

1.4 CONTRACT MODIFICATIONS

In conjunction with the Contract Clause "DFARS 252.236-7000, Modification Proposals-Price Breakdown," and where actual ownership and operating costs

63095SITE SECTION 01 20 00.00 20 Page 1 of construction equipment cannot be determined from Contractor accounting records, equipment use rates shall be based upon the applicable provisions of the EP-1110-1-8.

1.5 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT

1.5.1 Content of Invoice

Requests for payment will be processed in accordance with the Contract Clause FAR 52.232-27, Prompt Payment Construction Contracts and FAR 52.232-5, Payments Under Fixed-Price Construction Contracts. The requests for payment shall include the documents listed below.

a. The Contractor's invoice, on NAVFAC Form 7300/30 furnished by the Government, showing in summary form, the basis for arriving at the amount of the invoice. Form 7300/30 shall include certification by Quality Control (QC) Manager as required by the contract.

b. The Earned Value Report from the cost-loaded NAS, showing in detail:

the estimated cost, percentage of completion, and value of completed performance for each of the construction categories stated in this contract. Use LANTNAVFACENGCOM Form 4-330/110 (New 7/84) on NAVFAC Atlantic contracts when a Monthly Estimate for Voucher is required.

c. Updated Project Schedule and reports required by the contract.

d. Contractor Safety Self Evaluation Checklist.

e. Other supporting documents as requested.

f. Updated copy of submittal register.

g. Invoices not completed in accordance with contract requirements will be returned to the Contractor for correction of the deficiencies.

1.5.2 Submission of Invoices

If NFAS Clause 5252.232-9301 is included in the contract, the documents listed in paragraph "CONTENT OF INVOICE" shall be provided in their entirety as attachments in Wide Area Work Flow (WAWF) for each invoice submitted. The maximum size of each WAWF attachment is two megabytes, but there are no limits on the number of attachments. If a document cannot be attached in WAWF due to system or size restriction it shall be provided as instructed by the Contracting Officer.

1.5.3 Final Invoice

a. A final invoice shall be accompanied by the certification required by DFARS 252.247.7023 TRANSPORTATION OF SUPPLIES BY SEA, and the Contractor's Final Release. If the Contractor is incorporated, the Final Release shall contain the corporate seal. An officer of the corporation shall sign and the corporate secretary shall certify the Final Release.

b. For final invoices being submitted via WAWF, the original Contractor's Final Release Form and required certification of Transportation of Supplies by Sea must be provided directly to the respective Contracting Officer prior to submission of the final invoice. Once receipt of the original Final Release Form and required certification of

63095SITE SECTION 01 20 00.00 20 Page 2

Transportation of Supplies by Sea has been confirmed by the Contracting Officer, the Contractor shall then submit final invoice and attach a copy of the Final Release Form and required certification of Transportation of Supplies by Sea in WAWF.

c. Final invoices not accompanied by the Contractor's Final Release and required certification of Transportation of Supplies by Sea will be considered incomplete and will be returned to the Contractor.

1.6 PAYMENTS TO THE CONTRACTOR

Payments will be made on submission of itemized requests by the Contractor which comply with the requirements of this section, and will be subject to reduction for overpayments or increase for underpayments made on previous payments to the Contractor.

1.6.1 Obligation of Government Payments

The obligation of the Government to make payments required under the provisions of this contract will, at the discretion of the Contracting Officer, be subject to reductions and/or suspensions permitted under the FAR and agency regulations including the following in accordance with "FAR 32.503-6:

a. Reasonable deductions due to defects in material or workmanship;

b. Claims which the Government may have against the Contractor under or in connection with this contract;

c. Unless otherwise adjusted, repayment to the Government upon demand for overpayments made to the Contractor; and

d. Failure to provide up to date record drawings not current as stated in Contract Clause "FAC 5252.236-9310, Record Drawings."

1.6.2 Payment for Onsite and Offsite Materials

Progress payments may be made to the contractor for materials delivered on the site, for materials stored off construction sites, or materials that are in transit to the construction sites under the following conditions:

a. FAR 52.232-5(b) Payments Under Fixed Price Construction Contracts.

b. Materials delivered on the site but not installed, including completed preparatory work, and off-site materials to be considered for progress payment shall be major high cost, long lead, special order, or specialty items, not susceptible to deterioration or physical damage in storage or in transit to the construction site. Examples of materials acceptable for payment consideration include, but are not limited to, structural steel, non-magnetic steel, non-magnetic aggregate, equipment, machinery, large pipe and fittings,precast/prestressed concrete products, plastic lumber (e.g., fender piles/curbs), and high-voltage electrical cable. Materials not acceptable for payment include consumable materials such as nails, fasteners, conduits, gypsum board, glass, insulation, and wall coverings.

c. Materials to be considered for progress payment prior to installation shall be specifically and separately identified in the Contractor's estimates of work submitted for the Contracting Officer's approval in

63095SITE SECTION 01 20 00.00 20 Page 3 accordance with Earned Value Report requirement of this contract.

Requests for progress payment consideration for such items shall be supported by documents establishing their value and that the title requirements of the clause at FAR 52.232-5 have been met.

d. Materials are adequately insured and protected from theft and exposure.

e. Provide a written consent from the surety company with each payment request for offsite materials.

f. Materials to be considered for progress payments prior to installation shall be stored either in Hawaii, Guam, Puerto Rico, or the Continental United States. Other locations are subject to written approval by the Contracting Officer.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

63095SITE SECTION 01 20 00.00 20 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)

ECB 2005-10 (2005) Scheduling Requirements for Testing of Mechanical Systems in Construction Contracts

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, RO

1.3 QUALITY ASSURANCE

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

63095SITE SECTION 01 32 01.00 10 Page 1 design and construction sequences, is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development.

Subcontractors and 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

63095SITE SECTION 01 32 01.00 10 Page 2

Schedule shall be capable of meeting all requirements of this specification. Failure of the Contractor to meet the requirements of this specification 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 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.3 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.

h. Submission and approval of fire protection specialist.

i. Submission and approval of testing and balancing of HVAC plus commissioning plans and data. Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of

63095SITE SECTION 01 32 01.00 10 Page 3 detail consistent with ECB 2005-10.

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.4 Government Activities

Show Government and other agency activities that could impact progress.

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

3.3.2.5 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, Government design reviews, 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: DOR (for the designer of record); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE). Unacceptable code values are abbreviations of the names of subcontractors.

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

63095SITE SECTION 01 32 01.00 10 Page 4

3.3.2.7 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.8 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.9 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. Code activities to a Construction Phase. Code fast track construction phases proposed by the Contractor to allow filtering and organizing the schedule by fast track design and construction packages. 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.10 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: 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 activity shall have only one Category of Work Code.

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

63095SITE SECTION 01 32 01.00 10 Page 5

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

63095SITE SECTION 01 32 01.00 10 Page 6

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

63095SITE SECTION 01 32 01.00 10 Page 7

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 each fast track design package released for construction; design complete;

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 design activities, the 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. Schedule any construction activities planned for the first 90 calendar days after NTP. Constrain planned construction activities by Government acceptance of the associated design package(s) and all other 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 performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer.

63095SITE SECTION 01 32 01.00 10 Page 8

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:

www.rmssupport.com. The SDEF format is as follows:

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 format. Each CD shall also contain all previous update backup files. File medium shall be CD. Label each CD indicating the type of 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

63095SITE SECTION 01 32 01.00 10 Page 9 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 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

63095SITE SECTION 01 32 01.00 10 Page 10 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 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

63095SITE SECTION 01 32 01.00 10 Page 11 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% 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 actually manning the job, unrealistic OD or deficiencies that must be corrected that restrain successor activities.

3.6.2.3 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .