Attachment_2_-_Specificaitons.pdf

DEFENSE DISTRIBUTION DEPOT SAN JOAQUIN

RENOVATE BUILDING 101

SPECIFICATIONS

SOURCE SELECTION INFORMATION

SEE FAR 2.101AND 3.104

Attachment 2

PROJECT TABLE OF CONTENT

DIVISION 01 – GENERAL REQUIREMENTS

01 00 00 GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 45 00.00 QUALITY CONTROL

01 50 00 TEMPORARY CONSTRUCTION FACILITIES

01 57 20.00 10 ENVIRONMENTAL PROTECTION

01 62 35 RECYCLED / RECOVERED MATERIALS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

DIVISION 02 – EXISTING CONDITIONS

02 41 00 DEMOLITION AND DECONSTRUCTION

02 42 51 CARPET REMOVAL AND RECLAMATION

02 82 14.00 10 ABESTOS HAZARD CONTROL ACTIVITIES

02 83 13.00 20 LEAD IN CONSTRUCTION

DIVISION 07 – THERMAL AND MOISTURE PROTECTION

07 92 00 JOINT SEALANTS

DIVISION 09 FINISHES

09 51 00 ACOUSTICAL CEILINGS

09 68 00 CARPETS

09 90 00 PAINTS AND COATINGS

DIVISION 26 ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 00.00 40 COMMON WORK RESULTS FOR ELECTRICAL

26 20 00 INTERIOR DISTIRBUTION SYSTEM

26 51 00 INTERIOR LIGHTING

DIVISION 27 COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

SOURCE SELECTION INFORMATION

DEFENSE DISTRIBUTION DEPOT SAN JOAQUIN

DIVISION 01: GENERAL REQUIREMENTS

4/6/2015

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.12 SPECIAL CONSTRUCTION PROCEDURES

1.13 CONTRACTOR SAFETY PERSONNEL REQUIREMENTS

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

GENERAL REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

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

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2011; TIA 08-1) National Electrical Code

U.S. ARMY (DA)

DA FORM 5383 (2009) HOT-WORK PERMIT

DA AR 385-10 (2007; RAR 1 2009) The Army Safety Program

DA PAM 385-64 (1999) Ammunition and Explosives Safety Standards

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2008; Change 1-2010; Change 3-2010;

Errata 1-2010) Safety and Health Requirements Manual

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 1910.135 Head protection

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, the Contractor shall obtain and furnish to the Contracting Officer's representative written guarantees for all the equipment and/or appliances furnished under the contract.

The Contractor shall furnish with each guarantee: The name, address, and telephone number of the guarantor's representative nearest to the location where the equipment and/or appliances are installed, who, upon request of the Using Service's representative, will honor the guarantee during the guaranty period and will provide the services prescribed by the terms of the guarantee.

1.4 PRICING OF CONTRACTOR-FURNISHED PROPERTY

At the request of the Contracting Officer, the Contractor shall 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

The Contractor shall provide construction power facilities in accordance with the safety requirements of the NFPA 70 and EM 385-1-1.

The Contractor, or his delegated subcontractor, shall 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. A testing means shall be provided which will impose a measured fault of 5 milliamperes, plus or minus 1 milliamperes, and result in tripping the GFCI unit.

1.6 UTILITIES

If the Contractor encounters, within the construction limits of the entire project, utilities not shown on the plans and not visible as to the date of this contract and such utilities will interfere with construction operations, he shall immediately notify the Contracting Officer in writing 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, the Contractor shall be entitled to equitable adjustment for any additional pertinent work or delay.

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, 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 Job Hazard Analysis

Based on the construction schedule, submit a job hazard analysis of each major phase of work prior to entering that phase of activity. The analysis shall include major or high risk hazards, as well as commonly recurring deficiencies that might possibly be encountered for that operation, and shall identify proposed methods and techniques of accomplishing each phase in a safe manner. The Prime Contractor's superintendent shall take active participation in the Job Hazard Analysis, including the subcontractors' work. Prior to start of actual work a meeting shall be held with Prime Contractor, Government, and affected subcontractor to review the Job Hazard Analysis. In addition, job site meetings shall be held to indoctrinate foreman and workers on details of this analysis.

1.7.4 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.5 Elevated Work Areas

Workers in elevated work areas in excess of 6 feet above an adjoining surface require special safety attention. In addition to the provisions of EM 385-1-1, the following safety measures are required to be submitted to the Contracting Officer's Representative. Prior to commencement of work in elevated work areas, the Contractor shall submit drawings depicting all provisions of his positive protection system including, but not limited to, all details of guard rails.

1.7.5.1 Protection

Positive protection for workmen engaged in the installation of structural steel and steel joists shall be provided by safety nets, tie-off's, hydraulic man lifts, scaffolds, or other required means. Decking crews must be tied-off or work over nets or platforms not over 6 feet below the work area. Walking on beams and/or girders and the climbing of columns is prohibited without positive protection.

1.7.5.2 Guard Rails

Perimeter guard rails shall be installed at floor, roof, or wall openings more than 6 feet above an adjoining surface and on roof perimeters.

Rails shall be designed to protect all phases of elevated work including, but not limited to, roofing operations and installation of gutters and flashing. Rails around roofs may not be removed until all work on the roof is complete and all traffic on or across the roof ceases. Rails shall be designed by a licensed engineer to provide adequate stability under any anticipated impact loading. As a minimum, the rails shall consist of a top rail at a height of 42 inches, a mid rail and a toe board. Use of tie-offs, hydraulic man lifts, scaffolds, or other means of roof edge protection methods may be utilized on small structures such as family housing, prefabricated metal buildings, etc.

1.7.6 Fire Prevention

Twenty-four hours notice shall be given to the Contracting Officer for coordination with the Facility Fire Department prior to conducting any fire hazardous operation. Cutting or welding will be permitted only in areas that are or have been made fire safe. Where possible, all combustibles shall be located at least 35 feet horizontally from the work site. Where such location is impracticable, combustibles shall be protected with fire blankets and/or protective welding screens to prevent slag from running out of the work area. Edges of covers at the floor shall be tight to prevent sparks from going under them. This precaution is also important at overlaps where several covers are used to protect a large pile. The Contractor shall not allow any welding/cutting or open flame operations in facilities that are protected by a wet pipe fire sprinkler or an automatic detection system, if the system is out of service. First priority of work will be to return the suppression/detection system to operational condition. Return the fire detection and/or suppression system back to an operational status (if possible) during periods that the facility is unoccupied, and at the end of the work day. The Contractor shall post a fire guard for a 24 hour period (or certify to the Fire Department that the facility is safe) after welding, cutting, and open flame operations in a facility when: (a) fire detection and suppression system cannot be returned to service; (b) fire detection or suppression systems do not exist. Other fire prevention precautions shall be in accordance with the latest National Fire Codes.

1.7.6.1 Inspections

All construction sites are subject to fire and safety inspections without notice. Any violation of fire and safety standards may result in a work stoppage at the expense of the Contractor.

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, 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 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 14 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. The Contractor shall strictly observe such schedules and the contractor will be held responsible for any violations.

1.12 SPECIAL CONSTRUCTION PROCEDURES

(A) Contractor - Visitor Badges

(1) A minimum of one week prior to entry and initiation of work on Tracy Facilities, the Prime Contractor shall submit a list of all prime and subcontractor employees including any other personnel required to perform work on the installation during the contract performance period. The list will include the name, driver’s license number, and state of issuance to the Contracting Officer Representative who will request badges at the Security Operations Pass & ID Office located in Building 29A. If personnel are added or changed during the contract performance period, a revised list is to be submitted 72 hours prior to any new employees’ arrival for work at the Tracy Facility.

(2) Badges will be issued for the contract performance period not to exceed 179 day increments. A check will be made periodically by Security on the status of these badges. Normally, on projects longer than 180 days, the COR will submit a request to Pass and ID and request new badges to ensure contract personnel are vetted semi-annually.

(3) The Prime Contractor will be required to escort suppliers, vendors, or other one-time or occasional visitors to the project site. Notification will be given a minimum of 3 working days prior to arrival and include the name of the company, the Prime Contractor Company name responsible for the vendor, and the vendor representative if available. Security may refuse entry without this notification.

(4) The Prime Contractor will ensure that all access control requirements are adhered to per the DLA Defense Distribution Depot San Joaquin Physical Security Plan. Any questions or concerns will be routed through the COR to the Security Services Branch for clarification.

(5) Any additional requirements from Physical Security and Emergency Installation Management will be addressed during the pre-construction meeting conducted by the COR.

1.13 CONTRACTOR SAFETY PERSONNEL REQUIREMENTS

(A) Full-time, on-site, safety coverage by contractors shall be required for the life of the contract.

(B) The following conditions shall be met:

(1) The Contractor shall employ, to cover all hours of work at the project site(s), at least one safety and health person to manage the Contractor's safety program; duties which are not germane to the safety program shall not be assigned to this person(s). The principal safety and health person shall report to and works directly for the Contractor’s top on-site manager, corporate safety office, or other high-level official of equivalent position. The safety and health person(s) shall have the authority to take immediate steps to correct unsafe or unhealthful conditions. The employment of a safety and health person(s) shall not abrogate the safety and health responsibilities of other personnel.

(2) The Safety and Health Person can be the same as the project Superintendent as long as the Superintendent is a competent person and have the required training including but not limited to: OSHA General Industry and OSHA 30 Hour Construction Training.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

-- End of Section --

SECTION 01 11 00

SUMMARY OF WORK

1.1 RENOVATE BUILDING 101 DEFENSE DISTRIBUTION DEPOT SAN JOAQUIN

1.1.1 Project Description

1.1.2 Location

1.2 OCCUPANCY OF PREMISES

1.3 EXISTING WORK

-- End of Section Table of Contents –

SECTION 01 11 00

SUMMARY WORK

1.1 RENOVATE BUILDING 101 DEFENSE DISTRIBUTION DEPOT SAN JOAQUIN

1.1.1 Project Description

The work includes the renovation of Building 101 at Defense Distribution Depot San Joaquin - Tracy California.

1.1.2 Location

The work shall be located at the Tracy, CA, approximately as indicated in Appendix 1.

1.2 OCCUPANCY OF PREMISES

Building 101 is existing and will be partially occupied during and after performance of work under this Contract.

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

1.3 EXISTING WORK

In addition to "FAR 52.236-9, Protection of Existing Vegetation, Structures, Equipment, Utilities, and Improvements":

a. Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.

b. Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work shall be in a condition equal to or better than that which existed before new work started.

Not used.

Not used.

SECTION 01 32 01.00 10

PROJECT SCHEDULE

1.1 REFERENCES

1.2 SUBMITTALS

1.3 QUALITY ASSURANCE

3.1 GENERAL REQUIREMENTS

3.1.1 Approved Project Schedule

3.1.2 Schedule Status Reports

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.3 Procurement Activities

3.3.2.4 Mandatory Tasks

3.3.2.5 Government Activities

3.3.2.6 Activity Responsibility Coding (RESP)

3.3.2.7 Activity Work Area Coding

3.3.2.8 Contract Changes/Requests for Equitable Adjustment

(REA) Coding (MODF)

3.3.2.9 Contract Line Item (CLIN) Coding (BIDI)

3.3.2.10 Phase of Work Coding (PHAS)

3.3.2.11 Category of Work Coding (CATW)

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

3.3.3 Scheduled Project Completion and Activity Calendars

3.3.3.3 Project Start Date

3.3.3.4 Schedule Constraints and Open Ended Logic

3.3.3.5 Early Project Completion

3.3.4 Interim Completion Dates

3.3.4.3 Start Phase

3.3.4.4 End Phase

3.3.4.5 Phase "X" Hammock

3.3.5 Default Progress Data Disallowed

3.3.6 Out-of-Sequence Progress

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.2 Initial Project Schedule Submission

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CD's

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

3.6.1 Update Submission Following Progress Meeting

3.6.2 Status of Activities

3.6.2.3 Start and Finish Dates

3.6.2.4 Remaining Duration

3.6.2.5 Percent Complete

3.6.2.6 Logic Changes

3.6.2.7 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

-- End of Section Table of Contents --

SECTION 01 32 01.00 10

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.

U.S. ARMY CORPS OF ENGINEERS (USACE)

ECB 2005-10 (2005) Scheduling Requirements for

Testing of Mechanical Systems in Construction Contracts

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

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

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

SD-01 Preconstruction Submittals

Project Schedule; G

1.3 QUALITY ASSURANCE

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling have previously developed, created, and maintained at least 2 electronic schedules for 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.

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule. 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 construction design and construction is the responsibility of the Contractor.

Contractor management personnel shall actively participate in its development. Subcontractors and suppliers Designers, Subcontractors and suppliers working on the project shall also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool.

3.1.1 Approved Project Schedule

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

3.1.2 Schedule Status Reports

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

3.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. Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule.

3.3.1 Critical Path Method

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

3.3.2 Level of Detail Required

Develop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer, will result in its disapproval.

The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2.1 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities shall have Original Durations (OD) greater than 20 work days or 30 calendar days.

Procurement activities are defined herein.

3.3.2.3 Procurement Activities

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

3.3.2.4 Mandatory Tasks

The following tasks must be included and properly scheduled:

a. Submission and approval of as-built drawings.

b. Contractor's pre-final inspection.

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

d. Government's pre-final inspection.

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

f. 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/disapprovals, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.2.6 Activity Responsibility Coding (RESP)

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

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 be identified with a single project phase and have only one Phase of Work code.

3.3.2.11 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: design, design submittal, design reviews, review conferences, permits, construction submittals, construction submittal approvals, Acceptance, Procurement, Fabrication, Delivery, Weather Sensitive Installation, Non-Weather Sensitive Installation, and 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 feature of work to which the activity belongs.

Definable Feature of Work is defined in Specification Section 01 45 00.00

10 QUALITY CONTROL. An activity shall not have more than one Definable Feature of Work Code. Not all activities are required to be Definable Feature of Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

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

Original durations must account for anticipated normal adverse weather.

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

3.3.3.1 Project Start Date

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

3.3.3.2 Schedule Constraints and Open Ended Logic

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

3.3.3.3 Early Project Completion

In the event the Preliminary or Initial project schedule calculates an early completion date of the last activity prior to the contract completion date, identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

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

3.3.4.2 End Phase

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

3.3.4.3 Phase "X" Hammock

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

3.3.5 Default Progress Data Disallowed

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

3.3.6 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer. Propose logic corrections to eliminate all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than 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. The data CD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS.

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.

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.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 PDf and original file format. 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.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 handouts to view the proposed schedule update during the meeting. The meeting and resultant approvable schedule update shall be a condition precedent to a formal submission of the update as described in SUBMISSION REQUIREMENTS and to the submission of an invoice for payment. The meeting will be a working interactive exchange which will allow the Government and the Contractor the opportunity to review the updated schedule on a real time and interactive basis. The Contractor's authorized scheduling representative will organize, sort, filter and schedule the update as requested by the Government. The meeting will last no longer than 8 hours. A rough draft of the proposed activity logic corrections and narrative report shall be provided to the Government 48 hours in advance of the meeting. The Contractor's Project Manager and Authorized Scheduler shall attend the meeting with the Authorized Representative of the Contracting Officer.

3.6.1 Update Submission Following Progress Meeting

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

3.6.2 Status of Activities

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

3.6.2.1 Start and Finish Dates

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

3.6.2.2 Remaining Duration

Update the estimated RD for all incomplete activities independent of Percent Complete. Remaining Durations may exceed the activity OD or may exceed the activity's prior update RD if the Government considers the current OD or RD to be understated based on current progress, insufficient work crews actually manning the job, unrealistic OD or deficiencies that must be corrected that restrain successor activities.

3.6.2.3 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value. 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).

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

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. 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, continue to update the schedule with the Contracting Officer's revisions until a mutual agreement in the revisions is reached. If the Contractor fails to submit alternative revisions within 2 weeks of receipt of the Contracting Officer's proposed revisions, the Contractor will be deemed to have concurred with the Contracting Officer's proposed revisions. The proposed revisions will then be the basis for an equitable adjustment for performance of the work.

3.9 WEEKLY PROGRESS MEETINGS

a. Meet weekly with the Government (or as otherwise mutually agreed

to) between the meetings described in paragraph PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. The then current and approved schedule update shall be used for the purposes of this meeting and for the production and review of reports. The Contractor's Project Manager and the Authorized Representative of the Contracting Officer shall attend. The weekly progress meeting will address the status of RFI's, RFP's and Submittals.

b. Provide a bar chart produced by the scheduling software, organized by Total Float and Sorted by Early Start Date, and a two week "look-ahead" schedule by filtering all schedule activities to show only current ongoing activities and activities schedule to start during the upcoming two weeks, organized by Work Area Code (AREA) and sorted by Early Start Date.

c. The Government and the Contractor shall jointly review the reports. If it appears that activities on the longest path(s) which are currently driving the calculated completion date (driving activities), are not progressing satisfactorily and therefore could jeopardize timely project completion, corrective action must be taken immediately. Corrective action includes but is not limited to: increasing the number of work crews; increasing the number of work shifts; increasing the number of hours worked per shift; and determining if Government responsibility coded activities require Government corrective action.

3.10 OWNERSHIP OF FLOAT

Float available in the schedule, at…