APPENDIX_3_-_Division_1_GENERAL_REQUIREMENTS_Dugway.pdf

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

-- End of Project Table of Contents -

01 00 00 GENERAL REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 29 SUSTAINABILITY REPORTING

01 35 26 GOVERNMENT SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 QUALITY CONTROL

01 45 00.10 QUALITY CONTROL SYSTEM (QCS)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 20 ENVIRONMENTAL PROTECTION

01 57 23 TEMPORARY STORM WATER POLLUTION CONTROL

01 62 35 RECYCLED/RECOVERED/BIOBASED MATERIALS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 00 00 - 1

SECTION TABLE OF CONTENTS DIVISION

01 - GENERAL REQUIREMENTS SECTION

01 00 00

GENERAL REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

1.2 SCRAP MATERIAL

1.3 WRITTEN GUARANTEES AND GUARANTOR'S LOCAL REPRESENTATIVE

1.4 PRICING OF CONTRACTOR-FURNISHED PROPERTY

1.5 TEMPORARY ELECTRIC WIRING

1.5.1 Temporary Power and Lighting

1.5.2 Construction Equipment

1.5.3 Circuit Protection

1.6 UTILITIES

1.7 GENERAL SAFETY REQUIREMENTS

1.7.1 General

1.7.2 The Prime Contractor's Superintendent

1.7.3 Job Hazard Analysis

1.7.4 Violations

1.7.5 Elevated Work Areas

1.7.5.1 Protection

1.7.5.2 Guard Rails

1.7.6 Fire Prevention

1.7.6.1 Inspections

1.7.7 Recordkeeping/Reporting Requirements

1.7.8 Accident Reporting

1.8 PLANNED UTILITY OUTAGES AND STREET CLOSURES

1.9 EXCAVATION PERMITS

1.10 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER

1.11 EQUIPMENT DATA FORM

1.12 SPECIAL CONSTRUCTION PROCEDURES

1.13 CONTRACTOR SAFETY PERSONNEL REQUIREMENTS

1.14 AREAS OF RADAR RADIATION HAZARD

1.15 HAZARDOUS NOISE AREA

1.16 COLOR SCHEME FOR CONTRACTOR FACILITIES

1.17 AFTER AWARD DOCUMENTS

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

01 00 00 - 2

SECTION 01 00 00

GENERAL REQUIREMENTS

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 (2014; AMD 1 2013; Errata 2013; AMD 2

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

U.S. NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)

29 CFR 1904 Recording and Reporting Occupational

Injuries and Illnesses

29 CFR 1910 Occupational Safety and Health Standards

29 CFR 1926 Safety and Health Regulations for

Construction

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

01 00 00 - 3

1.4 PRICING OF CONTRACTOR-FURNISHED PROPERTY

At the request of the Contracting Officer, promptly furnish and shall 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.5 TEMPORARY ELECTRIC WIRING

1.5.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 shall be accomplished by skilled electrical tradesmen in a workmanlike manner, as approved by the Contracting Officer.

1.5.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 shall be either Type TW or THW contained in metal raceways, or may be multiconductor cord. Temporary wiring shall be secured above the ground or floor in a workmanlike manner and shall 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.5.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 shall have ground fault circuit interrupters (GFCI) for personnel protection. Block and brick saws shall 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 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 shall have GFCI'S, and shall 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.6 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 shall be made pursuant to the Contract Clause CHANGES to cover the cost of any additional pertinent work or delay.

It is anticipated that pole lines, signs, pipelines and private

01 00 00 - 4 improvements that would interfere with or are to be replaced by new construction will be removed to new locations by the owners (or by the

State of Utah or its agents) in advance of construction operations. Notify the Contracting Officer at least 30 days in advance of the date on which work will be started requiring the removal of such utilities or private improvements. Care shall be taken to preserve and protect any such improvements from injury or damage during construction operations. Assume full responsibility for reimbursing the owners for any damage to their properties, utilities, or improvements, or interference with their services caused through construction operations. Should such damage be found to have been caused without the Contractor's fault or negligence, an equitable adjustment in the amount due under the contract will be made under the applicable CONTRACT CLAUSES contained within the basic MATOC.

1.7 GENERAL SAFETY REQUIREMENTS

1.7.1 General

For information regarding specific Safety Requirements see Section 01 35 26

GOVERNMENTAL SAFETY REQUIREMENTS. Refer to EM 385-1-1, (see Contract

Clauses, Basic MATOC, ACCIDENT PREVENTION) and the Occupational Safety and

Health Act (OSHA) Standards for Construction 29 CFR 1926; General Industry

Standards 29 CFR 1910; and the National Fire Protection Association Codes are applicable to this contract. In case of conflict the most stringent requirement of the standards is applicable.

1.7.2 The Prime Contractor's Superintendent

The Prime Contractor's superintendent shall take an active role in enforcing the safety requirements by participation in safety conferences, hazard analysis (see below), tool box meetings, walk-through inspections, correction of violations, etc., and including that of the subcontractor's work.

1.7.3 Violations

If recurring violations and/or gross violation indicate that the safety performance is unsatisfactory, corrective action shall be taken as directed, and at the discretion of the Contracting Officer the retention or some part thereof will be withheld from the progress payment until corrective action has been completed.

1.7.7 Recordkeeping/Reporting Requirements

On all contract operations, record and report all accident exposure and experience incident work. [This includes exposure and experience of the prime contractor and sub-contractor(s)]. As a minimum these records shall include exposure work-hours and a log of occupational injuries and illnesses. (OSHA Form 300 or State equivalent as prescribed by 29 CFR

1904). Refer to EM 385-1-1, Paragraph 01.D.04.

1.7.8 Accident Reporting

In addition to the requirements for reporting accidents in accordance with

EM 385-1-1, Section 1, submit at the 50% point and 100% of project completion, a written summary of worker's compensation claims filed by workers on the project. The report will include all subcontractors. The main report covering the Prime Contractor claims will be certified as

"correct and true" by the Contractor's compensation insurance carrier. The

01 00 00 - 5 same certification will be required for subcontractor reports.

1.8 PLANNED UTILITY OUTAGES AND STREET CLOSURES

All utility outages and street closures shall be of as short a duration as possible and shall be scheduled as far in advance as possible with the

Contracting Officer, in no case less than 30 days before the outage or closure. Obtain from the Contracting Officer in writing a statement or schedule giving the permissible times of outages or closures for particular installations and the maximum time allowed for each. Strictly observe such schedules and the contractor will be held responsible for any violations.

Power outages shall 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 shall be scheduled as far in advance as possible with the Contracting Officer and in no case less than 30days 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 Director of Public Works (DPW), through the Contracting Officer. Processing time required is 30 calendar days. Questions concerning the excavation permit should be directed to the Contracting Officer.

(A) General:

Reference is made to the article of the contract entitled "Permits and

Responsibilities," which obligates the Contractor to obtain all required licenses and permits.

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 accordance with the CONTRACT

CLAUSE, Basic MATOC, entitled "DEFAULT (FIXED-PRICE CONSTRUCTION)".

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

01 00 00 - 6

WORK DAYS BASED ON (5) DAY WORK WEEK

STATE UTAH- DUGWAY PROVING GROUND/TOOELE

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

(20) (16) (14) (08) (05) (03) (02) (02) (02) (05) (13) (21)

(C) Upon acknowledgement 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 CONTRACTOR SAFETY PERSONNEL REQUIREMENTS

See Section 01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS for all safety requirements.

Not Used

-- End of Section --

CESPK FORM 450 1 SEP 92 (Edition of Apr 84 will be used) FormFlow 2.2, ver 1

DATE

CONTRACTOR EQUIPMENT DATA SHEET

(Data to be furnished by Contractor for all equipment to be used on modifications as required under the Special Provisions of the Contract.)

CONTRACTOR CONTRACTNUMBER

1. EQUIPMENT DESCRIPTION

2. MODELAND SERIES

3. YEAR PURCHASED

4. PURCHASEPRICEAT YEAR PURCHASED

5. LIST PRICE,YEAR OF MANUFACTURE

6. YEAR MANUFACTURED

7. EQUIPMENT HORSEPOWER

8. CARRIERHORSEPOWER

9. FUELTYPE

10. SHIPPINGWEIGHT

11. TIRESIZE: FRONT-

DRIVE- TRAI

LING-

REMARKS:

01 32 01 - 1

01 32 01

PROJECT SCHEDULE

1.2 SUBMITTALS

1.3 CONTRACTOR SCHEDULING REPRESENTATIVE QUALIFICATIONS

3.1 GENERAL REQUIREMENTS

3.1.1 Approved Project Schedule

3.1.2 Schedule Status Reports

3.1.3 Default Terms

3.2 BASIS FOR PAYMENT AND COST LOADING

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Critical Path Method

3.3.2 Level of Detail Required

3.3.2.1 Activity Durations

3.3.2.2 Design and Permit Activities

3.3.2.3 Procurement Activities

3.3.2.4 Mandatory Tasks

3.3.2.5 Government Activities

3.3.2.6 Contracts with multiple buildings/facilities

3.3.2.7 Activity Responsibility Coding (RESP)

3.3.2.8 Activity Work Area Coding

3.3.2.9 Contract Changes/Requests for Equitable Adjustment (REA)

Coding (MODF)

3.3.2.10 Contract Line Item (CLIN) Coding (BIDI)

3.3.2.11 Phase of Work Coding (PHAS)

3.3.2.12 Category of Work Coding (CATW)

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

3.3.3 Scheduled Project Completion and Activity Calendars

3.3.3.1 Project Start Date

3.3.3.2 Schedule Constraints and Open Ended Logic

3.3.3.3 Early Project Completion

3.3.4 Interim Completion Dates

3.3.4.1 Design phase

3.3.4.2 Start Phase

3.3.4.3 End Phase

3.3.4.4 Phase "X" Hammock

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

01 32 01 - 2

3.3.7 Negative Lags and Start to Finish Relationships

3.3.8 Calculation Mode

3.3.9 Milestones

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary NAS Project Schedule Submission

3.4.2 Initial NAS Project Schedule Submission

3.4.3 Design Package Schedule Submission

3.4.4 Periodic Schedule Updates

3.4.5 Standard Activity Coding Dictionary

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CDs

3.5.2 Narrative Report

3.5.3 Approved Changes Verification

3.5.4 Schedule Reports

3.5.4.1 Activity Report

3.5.4.2 Logic Report

3.5.4.3 Total Float Report

3.5.4.4 Earnings Report by CLIN

3.5.4.5 Activity Resource Loading

3.5.5 Network Diagram

3.5.5.1 Continuous Flow

3.5.5.2 Project Milestone Dates

3.5.5.3 Critical Path

3.5.5.4 Banding

3.5.5.5 S-Curves

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

3.6.1 Update Submission Following Progress Meeting

3.6.2 Status of Activities

3.6.2.1 Start and Finish Dates

3.6.2.2 Remaining Duration

3.6.2.3 Percent Complete

3.6.2.4 Logic Changes

3.6.2.5 Other Changes

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.7.2 Submission Requirements

3.7.3 Additional Submission Requirements

3.8 DIRECTED CHANGES

3.9 WEEKLY PROGRESS MEETINGS

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

01 32 01 - 3

SECTION 01 32 01

PROJECT SCHEDULE

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.

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

The following shall be submitted in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Initial NAS Project Schedule

Preliminary NAS Project Schedule; G

Periodic Schedule Updates; G

Proposed Schedule Revisions; G

1.3 CONTRACTOR SCHEDULING REPRESENTATIVE QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation and submittal of the entire Network Analysis Systems (NAS) project schedule including all items specified below and revisions to the schedule or supplemental completion schedules, and all required updating

(activity status) and preparation of reports, as applicable or directed by the Contracting Officer. The authorized scheduling representative shall be approved by the Contracting Officer based on a resume indicating as a minimum, formal training from a software vendor or 5 years’ experience in working with NAS schedules.

01 32 01 - 4

3.1 GENERAL REQUIREMENTS

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

Designers, Subcontractors and suppliers working on the project shall also contribute in developing and maintaining an accurate Project Schedule. The schedule must be 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. The government will use the NAS Project Schedule to evaluate the contractor's progress for timely completion, plan for Quality Assurance verification of the work and evaluate the effects of a proposed modification on the contract duration (critical path activities). If, in the opinion of the

Contracting Officer, the Contractor falls behind the approved schedule, the

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

01 32 01 - 5 update period and therefore the amount of each progress payment. Lack of an approved schedule update or qualified scheduling personnel will result in an 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 NAS Project

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. Scheduling software that meets the activity coding structure defined in the Standard

Data Exchange Format (SDEF) in ER 1-1-11 are Primavera Project Planner (P6) by Primavera, and Open Plan by Deltek. The Contractor shall provide to the

Government a complete input listing for the selected software. Manual methods used to produce any required information shall require prior approval by the Contracting Officer. The Contracting Officer intends to use P6, which is compatible with RMS.

Should the contractor utilize software that is different than that utilized by the Contracting Officer, based on the software utilized by the contractor for the preparation of the NAS schedule, the contractor shall provide a copy of the software and a license to the Administrative

Contracting Officer at the government field office until final payment.

The software and license shall be returned to the contractor. The

Contractor shall submit a copy of the user's manual outlining the selected

CPM computer program's mathematical analysis capabilities, details, functions and operation.

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. Durations shall be in workdays. Procurement activities are defined herein.

01 32 01 - 6

3.3.2.2 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. This shall be at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work. The schedule shall include review and correction periods associated with each item.

3.3.2.3 Procurement Activities

The schedule must include activities associated with the submittal, approval, procurement, fabrication and delivery of long lead materials, equipment, fabricated assemblies and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over

90 calendar days. A typical procurement sequence includes the string of activities: submit, approve, procure, fabricate, and deliver.

3.3.2.4 Mandatory Tasks

Include and properly schedule the following mandatory tasks:

a. Submission, review and acceptance of design packages.

b. Submission and approval of as-built drawings.

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

d. Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with ECB 2005-10.

e. Air and water balancing.

f. Controls testing.

g. Performance Verification testing.

h. LEED Processes & Certification

i. Other systems testing, as required.

j. Contractor's Punchout inspection.

k. Correction of punchlist from Contractor's punchout inspection.

l. Government's pre-final inspection.

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

n. Final inspection.

3.3.2.5 Government Activities

Show government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, review and verification that design submittals are in accordance with the RFP

01 32 01 - 7 inspections, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment

(GFE) and Notice to Proceed (NTP) for phasing requirements. Government approval of shop drawings activities should be shown with the duration at least the minimum allowed by the contract. The contractor's failure to provide reasonable durations in its 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.

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.

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

c. CQC completion inspection of the entire project.

d. Contractor works off CQC punchlist.

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

Contracting Officer.

f. Contractor works off prefinal punchlist.

g. Final/acceptance inspection of the entire project.

h. Contractor works off final punchlist.

3.3.2.6 Contracts with multiple buildings/facilities

Prepare a separate detailed NAS schedule for each building/facility indicating its critical path for specified interim completion dates or critical milestone date. The master NAS schedule shall 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.3.2.7 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).

3.3.2.8 Activity Work Area Coding

Assign Work Area code to activities based upon the work area in which the

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

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

3.3.2.9 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.10 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.11 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 either a Design Phase or a

Construction Phase. Code fast track design and 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.12 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: design, design submittal, design reviews, review conferences, permits, construction 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.13 Definable Features of Work Coding (FOW1, FOW2, FOW3)

01 32 01 - 9

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 QUALITY

CONTROL. An activity shall not have more than one Definable Feature of

Work Code. Not all activities are required to be Definable Feature of

Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is acknowledged 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 NAS Project Schedule calculates an early completion date of the last activity prior to the contract completion date, the Contractor shall 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

01 32 01 - 10 early completion schedule with zero float on the longest path. The

Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Design phase

The contractor shall include design phase activities in the composite design and construction NAS Project schedule. The duration of each of these activities must be the duration as included in the contract award.

Reference Section 01 33 16 Design After Award.

3.3.4.2 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.3 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.4 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

01 32 01 - 11 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.

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.

3.4.1 Preliminary NAS Project Schedule Submission

Submit for approval, the Preliminary NAS Project Schedule, defining the

Contractor's planned design phase activities within 30 calendar days after the NTP is acknowledged. The approved Preliminary NAS Project Schedule will be used for design deliverable payment purposes. Payment for each design deliverable will be made following Government acceptance of the deliverable.

ompletely cost load the Preliminary NAS Project Schedule to balance the contract award CLINS shown on the Price Schedule. 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 NAS Project Schedule forms the basis for the Initial NAS

Project Schedule specified herein and must include design activities, the planned submissions of all early design packages, permitting activities, design review conference activities and other non-construction activities intended to occur prior to construction. 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 with Responsibility Code (RESP) and

Feature of Work code (FOW1, FOW2, FOW3).

3.4.2 Initial NAS Project Schedule Submission

Submit the Initial NAS Project Schedule for approval at a minimum of 42 calendar days prior to start of any Construction activities. The schedule shall demonstrate a reasonable and realistic sequence of activities which

01 32 01 - 12 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. 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.

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. Update the schedule to include detailed, lower WBS level 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.

3.4.4 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange

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

http://rms.usace.army.mil. The SDEF format is as follows (next page):

http://rms.usace.army.mil/

01 32 01 - 13

SDEF Format

Field Activity

Code

Length Description

1 WRKP 3 Workers per Day

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

3 AREA 4 Area of Work

4 MODF 6 Modification or REA number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of Work

7 CATW 1 Category of Work

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

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

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

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary NAS Schedule, Initial NAS

Schedule, and every Periodic NAS Schedule Update throughout the life of the project. Provide one hard copy of diagrams and three hard copies of all reports.

3.5.1 Data CDs

Provide two sets of data CDs 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 and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

01 32 01 - 14

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.4.5 Activity Resource Loading

This report shall identify and report the units of resource loading or manpower associated with each activity identified in the schedule.

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

01 32 01 - 15 interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.5.1 Continuous Flow

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

3.5.5.2 Project Milestone Dates

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

3.5.5.3 Critical Path

Clearly show the critical path.

3.5.5.4 Banding

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

3.5.5.5 S-Curves

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

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

Conduct periodic schedule update meetings for the purposes of reviewing the

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