W912DS-15-R-0012_Specifications.pdf

NEW YORK DISTRICT

Re-Procurment of the Explosive Research and Development Laboratory Facility

(ERDLF)

Picatinny Arsenal, New Jersey

W912DS-15-R-0012

Specifications

ERDL Facility 012104

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 31 10.00 18 PROJECT SCHEDULE: BAR CHART

01 32 01.00 18 PROJECT SCHEDULE

01 33 00.00 18 SUBMITTAL PROCEDURES

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 02.00 18 QUALITY CONTROL SYSTEM (QCS)

01 45 04.00 18 CONTRACTOR QUALITY CONTROL

01 45 20.00 18 TESTING FOR MECHANICAL AND ELECTRICAL SYSTEMS

01 52 60.00 18 CONSTRUCTION INDOOR AIR QUALITY (IAQ) MANAGEMENT

01 57 20.00 10 ENVIRONMENTAL PROTECTION

01 57 23 TEMPORARY STORM WATER POLLUTION CONTROL

01 78 00.00 18 CLOSEOUT SUBMITTALS

01 78 23.00 18 OPERATION AND MAINTENANCE DATA

DIVISION 03 - CONCRETE

03 11 13.00 10 STRUCTURAL CAST-IN-PLACE CONCRETE FORMING

03 15 00.00 10 CONCRETE ACCESSORIES

03 20 00.00 10 CONCRETE REINFORCING

03 30 00 CAST-IN-PLACE CONCRETE

03 33 00 CAST-IN-PLACE ARCHITECTURAL CONCRETE

03 35 00.00 10 CONCRETE FINISHING

DIVISION 05 - METALS

05 12 00 STRUCTURAL STEEL

05 30 00 STEEL DECKS

05 40 00 COLD-FORMED METAL FRAMING

05 51 33 METAL LADDERS

05 52 00 METAL RAILINGS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 41 16.00 10 LAMINATE CLAD ARCHITECTURAL CASEWORK

06 61 16 SOLID POLYMER (SOLID SURFACING) FABRICATIONS

06 73 01 FIBERGLASS REINFORCED PLASTIC (FRP) GRATING

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 22 00 ROOF AND DECK INSULATION

07 24 00 EXTERIOR INSULATION AND FINISH SYSTEMS

07 41 13 METAL ROOF PANELS

07 53 23 ETHYLENE-PROPYLENE-DIENE-MONOMER ROOFING

07 60 00 FLASHING AND SHEET METAL

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 14 00 WOOD DOORS

08 51 13 ALUMINUM WINDOWS

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

PROJECT TABLE OF CONTENTS Page 1

08 91 00 METAL WALL LOUVERS

DIVISION 09 - FINISHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 13 CERAMIC TILING

09 51 00 ACOUSTICAL CEILINGS

09 65 00 RESILIENT FLOORING

09 90 00 PAINTS AND COATINGS

09 97 23 METALLIC TYPE CONDUCTIVE/SPARK RESISTANT CONCRETE FLOOR

FINISH

DIVISION 10 - SPECIALTIES

10 10 00 VISUAL COMMUNICATIONS SPECIALTIES

10 14 00.20 INTERIOR SIGNAGE

10 14 01 EXTERIOR SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 26 13 WALL AND CORNER GUARDS

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS

10 51 13 METAL LOCKERS

DIVISION 11 - EQUIPMENT

11 13 10 DOCK LEVELERS

DIVISION 12 - FURNISHINGS

12 21 00 WINDOW BLINDS

DIVISION 21 - FIRE SUPPRESSION

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

21 13 17.00 10 DRY PIPE SPRINKLER SYSTEM, FIRE PROTECTION

21 13 18.00 10 PREACTION AND DELUGE SPRINKLER SYSTEMS, FIRE PROTECTION

21 30 00 FIRE PUMPS

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

22 15 14.00 40 GENERAL SERVICE COMPRESSED-AIR SYSTEMS, LOW PRESSURE

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING

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

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 08 00.00 10 COMMISSIONING OF HVAC SYSTEMS

23 09 23.13 20 BACnet DIRECT DIGITAL CONTROL SYSTEMS FOR HVAC

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

23 22 26.00 20 STEAM SYSTEM AND TERMINAL UNITS

23 23 00 REFRIGERANT PIPING

23 81 00.00 20 UNITARY AIR CONDITIONING EQUIPMENT

23 82 46.00 40 ELECTRIC UNIT HEATERS

DIVISION 26 - ELECTRICAL

PROJECT TABLE OF CONTENTS Page 2

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 23 00 SWITCHBOARDS AND SWITCHGEAR

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

27 51 16 RADIO AND PUBLIC ADDRESS SYSTEMS

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 11 00 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 11 23 AGGREGATE AND/OR GRADED-CRUSHED AGGREGATE BASE COURSE

32 12 17 HOT MIX BITUMINOUS PAVEMENT

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 31 13 CHAIN LINK FENCES AND GATES

32 92 19 SEEDING

DIVISION 33 - UTILITIES

33 11 00 WATER DISTRIBUTION

33 30 00 SANITARY SEWERS

33 40 00 STORM DRAINAGE UTILITIES

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

DIVISION 40 - PROCESS INTEGRATION

40 18 00.00 40 VACUUM SYSTEMS PROCESS PIPING

DIVISION 41 - MATERIAL PROCESSING AND HANDLING EQUIPMENT

41 22 13.14 CRANES AND HOISTS

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 3

SECTION 01 31 10.00 18

PROJECT SCHEDULE: BAR CHART

NYD EDITION 08/05

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. The following shall be submitted in accordance with Section 01 33 00.00 18 SUBMITTAL PROCEDURES:

SD-12 Schedules

Initial Project Schedules; G, RO

Revised Project Schedule; G, RO

Periodic Schedule Update; G, RO

Progress Curve Report Format; G, RO

Narrative report with schedule updates-Format; G, RO

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL

Pursuant to the Contract Clause, SCHEDULES FOR CONSTRUCTION CONTRACTS, and Special Contract Requirements SCHEDULING AND DETERMINATION OF PROGRESS the Contractor shall prepare and submit for approval a practicable project schedule. The schedule will be submitted within fifteen (15) calender days after receipt of Notice to Proceed or as otherwise determined by the Contracting Officer.

3.1.1 BASIS FOR PAYMENT

The approved Project Schedule shall be used to measure the progress of the work, to aid in evaluating time extensions, and to provide the basis of all progress payments.

3.1.2 PROJECT SCHEDULE

The Project Schedule shall be in the form of a chart consisting of a series of bars graphically indicating the sequence proposed to accomplish each work feature or operation. Each bar will represent a work features, system or series of activities within the construction project. The chart shall be prepared to show the starting and completion dates of all work features on a linear horizontal time scale beginning with date of Notice to Proceed and indicating calendar days to completion. Interdependence of status of activities shall be shown. Horizontal time scale shall allow identifica-tion of the first work day of each week, which shall be identified. Space

SECTION 01 31 10.00 18 Page 1 between bars shall be allowed for future revisions and notations. Initial Project Schedule shall be submitted for approval within fifteen (15) calendar days after Notice to Proceed. The schedule shall provide a reasonable sequence of activities which represent work through the entire project and shall be at a reasonable level of detail. The initial schedule shall be reviewed by the Government to determine compliance with contract requirements and realistic completion of the project in the period indicated. A revised project schedule shall be submitted based on Government review, if required.

3.1.2.1 PROGRESS CURVE

With the Project Schedule the Contractor shall also submit for approval a progress curve which reflects the intended schedule for completing the work. The progress curve (S-Curve) will be plotted to reflect Cumulative Progress (Percent) based on placement along the y-axis and Time along the x-axis.

3.1.2.2 PERIODIC SCHEDULE UPDATE AND PROGRESS CURVE UPDATE

Approved Schedule and Progress Curve will be updated monthly during the entire duration of construction. Not later than four days after the Monthly Progress Meeting the Contractor shall submit updated Project Schedule and Progress Curve. The updated versions shall include all approved contract revisions, progress of each activity to date of submission, and adjustments. Contractor shall also provide a very brief narrative report as required to indicate any problem areas, anticipated delays, impact on schedule, and corrective action.

3.1.2.3 NARRATIVE REPORT

A Narrative Report shall be provided with each upgrade of the project schedule. This report shall be provided as the basis of the Contractor's progress payment request. The Narrative Report shall include general description of current progress and a description of current and anticipated problem areas of delaying factors (relating to project activities) and their impact, and an explanation of corrective action taken.

3.1.2.3 PERIODIC PROGRESS MEETINGS

Progress meetings to discuss payment shall include a monthly on-site meeting or other regular intervals mutually agreed to at the preconstruc-tion conference. During this meeting the Contractor will describe, on an activity by activity basis, all proposed revisions and adjustments to the project schedule required to reflect the current status of the project.

The Contracting Officer will approve activity progress, proposed revisions, and adjustments as appropriate.

-- End of Section --

SECTION 01 31 10.00 18 Page 2

SECTION 01 32 01.00 18

PROJECT SCHEDULE

NYD Version 03/07 (UFGS 01/07)

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

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

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. The following shall be submitted in accordance with Section 01 33 00.00 18 SUBMITTAL PROCEDURES:

SD-12 Schedules

Initial Project Schedule; G, RO

Preliminary Project Schedule; G, RO

Periodic Project Schedule; G, RO

Narrative Report; G, RO

Four copies of the schedules showing codes, values, categories, numbers, and other items, etc., as required.

SD-07 Certificates

Qualifications Statement;

Documentation showing the qualifications of personnel preparing the reports.

1.3 QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling projects similar in nature to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

SECTION 01 32 01.00 18 Page 1

PART 2 PRODUCTS (Not Applicable)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the design (if design-build projects) 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. The schedule must be a forward planning as well as a project monitoring tool.

3.1.1 Approved Poject Schedule

Use the approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions, and to provide the basis of all progress payments. 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, 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 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

SECTION 01 32 01.00 18 Page 2 value for the purposes of payment. Failure of the Contractor to provide all required information will result in the disapproval of the preliminary, initial and subsequent schedule updates. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made. Activity cost loading shall be reasonable, as determined by the Contracting Officer. The aggregate value of all activities coded to a contract CLIN shall equal the value of the CLIN on the Schedule.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this specification and shall be capable of producing the Standard Data Exchange Format (SDEF) file discussed in ER 1-1-11. 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 (P3) or Primavera Project Management (P5) by Primavera, and Open Plan by Deltek. Manual methods shall not be utilized to produce any required information. The contractor shall be required to furnish to the Gov't the software scheduling program with one software license for the duration of this contract.

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

With the exception of the initial and preliminary schedule submission, the Project Schedule shall include an appropriate level of detail. Failure to develop or update the Project Schedule or provide data to the Contracting Officer at the appropriate level of detail, as specified by the Contracting Officer, shall result in the disapproval of the schedule. The Contracting Officer will use, but is not limited to, the following conditions to determine the appropriate level of detail to be used in the Project Schedule:

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, deliver, installation and

SECTION 01 32 01.00 18 Page 3 testing.

3.3.2.3 Mandatory Tasks

In addition to other activities as required to complete the project, the Progress Schedule shall include the following as separate line activities:

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 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, as required.

p. Warranty/Closeout Actions.

q. Contractor's pre-final inspection.

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

s. Government's pre-final inspection.

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

u. Final inspection.

3.3.2.4 Government Activities

Show Government and other agency activities that could impact progress.

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

SECTION 01 32 01.00 18 Page 4

3.3.2.5 Workers Per Day

All activities shall have an estimate of the average number of workers per day that are expected to be used during the execution of the activity to produce the expected completion date. If no workers are required for an activity, in the case of activities related to procurement, for example, then the activitity shall be identified as using zero workers per day. The workers per day information for each activity shall be identified by the Workers Per Day Code.

3.3.2.6 Activity Responsibility Coding (RESP)

Assign responsibility Code for all activities to the Prime Contractor, Subcontractor or Government agency responsible for performing the activity. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, 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.7 Activity Work Area Coding

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

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

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

(MODF)

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

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

SECTION 01 32 01.00 18 Page 5

3.3.2.9 Contract Line Item (CLIN) Coding (BIDI)

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

3.3.2.10 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. 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 have only one Phase of Work code.

3.3.2.11 Category of Work Coding (CATW)

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

Assign a Definable Feature of Work Code to appropriate activities based on the definable ture of work to which the activity belongs. Definable Feature of Work is defined in Specification Section 01 45 04.00 18 CONTRACTOR 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.2.13 HVAC Testing, Balancing and Commissioning

If this contract contains requirements for Heating, Ventilation and Air Conditioning Testing and Balancing and Commissioning, these activities must be allocated sufficient time and personnel resources by the Contractor so that they can be accomplished within time allowed for project completion.

These activities are necessary to assure detection of any deficiencies in the HVAC Systems and avoid warranty callbacks. Included for guidance at the end of this section is a flow chart (Figures 1 and 2) showing major activities and their chronological relationship to each other and to the Notice to Proceed and Contract Completion points. They are for guidance only - the Contractor shall refer to applicable specification sections for actual requirements for these activities.

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

SECTION 01 32 01.00 18 Page 6 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, 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 early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

Include as the first activity for a project phase an activity called "Start Phase X" where "X" refers to the phase of work. The "Start Phase X"

SECTION 01 32 01.00 18 Page 7 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.

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.

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

SECTION 01 32 01.00 18 Page 8 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 aAny 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. If a design build project, 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.

SECTION 01 32 01.00 18 Page 9

3.4.3 Design Package Schedule Submission

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

3.4.4 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 judgement 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.5 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

SECTION 01 32 01.00 18 Page 10

Update of the project schedule, as the basis of the progress payment request. The Narrative Report shall include: a description of activities along the 2 most critical paths where the total float is less than or equal to 20 work days, a description of current and anticipated problem areas or delaying factors and their impact, and an explanation of corrective actions taken or required to be taken. The narrative report is expected to communicate to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis. Identify and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

3.5.3 Approved Changes Verification

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

3.5.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report shall be as directed by the Contracting Officer. Typically reports shall contain: Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission.

3.5.4.1 Activity Report

A list of all activities sorted according to activity number.

3.5.4.2 Logic Report

A list of detailed predecessor and successor activities for every activity in ascending order by activity number and then sorted according to Early Start Date.

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

SECTION 01 32 01.00 18 Page 11 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 Labor Loading

For each activity shown on the logic report list the total amount of work required for the activity in man-hours, the number of workers assigned to the activity, the expected production rate for a worker, and the length of time (in work days) required to render the expected completion date for the activity. Completion dates on this report must agree with those on the logic report.

3.5.5 Network Diagram

The network diagram is required for the Preliminary, Initial and Periodic Updates. The network diagram shall depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.5.1 Continuous Flow

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

3.5.5.2 Project Milestone Dates

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

3.5.5.3 Critical Path

Clearly show the critical path.

3.5.5.4 Banding

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

3.5.5.5 S-Curves

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

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

Conduct periodic schedule update meetings for the purposes of reviewing the Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. Meetings shall occur at least monthly within five days of the proposed schedule data date and after the Contractor has updated the schedule with Government concurrence respecting actual start dates, actual finish dates, remaining durations and percent complete for each activity it intend to status. Provide a computer with the scheduling software loaded and a projector during the meeting which allows all meeting participants to

SECTION 01 32 01.00 18 Page 12 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 imvoice 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 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

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

To allow for proper schedule management, cost load the correction of punch list from Government pre-final inspection activity(ies) not less than 1 percent of the total contract value, which activity(ies) may be declared 100 percent complete upon completion and correction of all punch list work identified during Government pre-final inspection(s). A portion of the

SECTION 01 32 01.00 18 Page 13 overall project amount may be retained based on delays of activities.

3.6.2.4 Logic Changes

Specifically identify and discuss all logic changes pertaining to NTP on change orders, change orders to be incorporated into the schedule, Contractor proposed changes in work sequence, corrections to schedule logic for out-of-sequence progress, and other changes that have been made pursuant to contract provisions. The Government will only approve logic revisions for the purpose of keeping the schedule valid in terms of its usefulness in calculating a realistic completion date, correcting erroneous logic ties, and accurately sequencing the work.

3.6.2.5 Other Changes

Other changes required due to delays in completion of any activity or group of activities include: 1) delays beyond the Contractor's control, such as strikes and unusual weather. 2) delays encountered due to submittals, Government Activities, deliveries or work stoppages which make re-planning the work necessary. 3) Changes required to correct a schedule that does not represent the actual or planned prosecution and progress of the work.

3.7 REQUESTS FOR TIME EXTENSIONS

In the event the Contractor believes it is entitled to an extension of the contract performance period, completion date, or any interim milestone date, furnish the following for a determination by the Contracting Officer: justification, project schedule data, and supporting evidence as the Contracting Officer may deem necessary. Submission of proof of excusable delay, based on revised activity logic, duration, and costs (updated to the specific date that the delay occurred) is a condition precedent to any approvals by the Government. In response to each Request For Proposal issued by the Government, the Contractor shall submit a schedule impact analysis demonstrating whether or not the change contemplated by the Government impacts the critical path.

3.7.1 Justification of Delay

The project schedule shall clearly display that the Contractor has used, in full, all the float time available for the work involved with this request. The Contracting Officer's determination as to the number of allowable days of contract extension shall be based upon the project schedule updates in effect for the time period in question, and other factual information. Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay, will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.7.2 Submission Requirements

Submit a justification for each request for a change in the contract completion date of less than 2 weeks based upon the most recent schedule update at the time of the NTP or constructive direction issued for the change. Such a request shall be in accordance with the requirements of other appropriate Contract Clauses and shall include, as a minimum:

a. A list of affected activities, with their associated project schedule activity number.

SECTION 01 32 01.00 18 Page 14

b. A brief explanation of the causes of the change.

c. An analysis of the overall impact of the changes proposed.

d. A sub-network of the affected area.

Identify activities impacted in each justification for change by a unique activity code contained in the required data file.

3.7.3 Additional Submission Requirements

The Contracting Officer may request an interim update with revised activities for any requested time extension of over 2 weeks. Provide this disk within 4 days of the Contracting Officer's request.

3.8 DIRECTED CHANGES

If the NTP is issued for changes prior to settlement of price and/or time, submit proposed schedule revisions to the Contracting Officer within 2 weeks of the NTP being issued. The Contracting Officer will approve proposed revisions to the schedule prior to inclusion of those changes within the project schedule. If the Contractor fails to submit the proposed revisions, the Contracting Officer may furnish the Contractor with suggested revisions to the project schedule. The Contractor shall include these revisions in the project schedule until revisions are submitted, and final changes and impacts have been negotiated. If the Contractor has any objections to the revisions furnished by the Contracting Officer, advise the Contracting Officer within 2 weeks of receipt of the revisions.

Regardless of the objections, the Contractor shall continue to update the schedule with the Contracting Officer's revisions until a…