Attachment 9 Travis AFB Fire Suppression Building 54 Final Specifications.pdf

Renovate Wet Fire Suppression To Dry, Server Room, B54

XDAT 15-1124

Final Specifications – September 27, 2019

Prepared For:

Travis Air Force Base, California

Prepared By:

2020 E. 1st Street Suite 525 Santa Ana, CA 92705

714.689.0298 Ι www.DevelopmentOne.net

Renovate Wet Fire Suppression Building 54 XDAT 15-1124 Final Specifications 09.27.2019

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 31 23.13 20 ELECTRONIC CONSTRUCTION AND FACILITY SUPPORT CONTRACT

MANAGEMENT SYSTEM

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.10 20 QUALITY CONTROL FOR MINOR CONSTRUCTION

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 56 00 ENVIRONMENTAL GENERAL REQUIREMENTS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 83 00 LEAD REMEDIATION

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 71 00 DOOR HARDWARE

DIVISION 21 - FIRE SUPPRESSION

21 22 00.00 40 CLEAN AGENT FIRE EXTINGUISHING SYSTEMS

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

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

23 03 00.00 20 BASIC MECHANICAL MATERIALS AND METHODS

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 20 00 INTERIOR DISTRIBUTION SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 00.00 10 FIRE DETECTION AND ALARM SYSTEM, DIRECT CURRENT LOOP

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION 01 11 00

SUMMARY OF WORK

08/15

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval.

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

Renovate the Fire Suppression System in Building 54 (switch room) to comply with the Unified Facilities Criteria (UFC) 3-600-01 and Air Force Engineering Technical Letter (ETL) 01-18. Theses design features include:

a. Demolition Plan for applicable / existing Fire Detection and Suppression System

b. Design to construct a clean agent Fire Suppression System to include, but not limited to:

1. Provide stand-alone (not dependent upon the building Fire Alarm System for operation) control panels that are listed for releasing device service and monitored by the building Fire Alarm system.

2. The system shall include a manually activated exhaust system to facilitate the extraction of any remaining clean agent after the required hold time of the total flooding Clean Agent System.

3. A very early warning smoke detection system must be used to activate a Clean Agent Fire Extinguishing System.

1.2.2 Location

The work is located at Travis Air Force Base, approximately as indicated.

The exact location will be shown by the Contracting Officer.

1.3 OCCUPANCY OF PREMISES

Adjacent building(s) will be occupied during performance of work under this Contract.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, area for storage of materials and equipment, and use of parking areas and easements.

1.4 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

SECTION 01 11 00 Page 1 damage to any portions of the existing work which remain.

1.5 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.

Contact local utility locating service a minimum of 48 hours prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.

Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities are discovered. Verify the elevations of existing piping, utilities,and any type of underground obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed.

1.5.1 Notification Prior to Excavation

Notify the Contracting Officer at least 15 days prior to starting excavation work.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

11/11

PART 1 GENERAL

1.1 SUBMITTALS

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

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

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Contact Personnel; G

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.1 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear hard hats in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Mark Contractor equipment for identification.

1.2.1.1 Subcontractors and Personnel Contacts

Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.2.1.2 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

1.2.2 Working Hours

Regular working hours must consist of a period established by the Contractor Officer, between 7 a.m. and 5:00 p.m., Monday through Friday, excluding Government holidays.

1.2.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, the

SECTION 01 14 00 Page 1

Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

1.2.4 Occupied Buildings

The Contractor shall be working around existing buildings which are occupied. Do not enter the buildings without prior approval of the Contracting Officer.

The existing buildings and their contents must be kept secure at all times. Provide temporary closures as required to maintain security as directed by the Contracting Officer.

1.2.5 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required paragraph WORK OUTSIDE REGULAR HOURS.

b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.

c. Operation of Utilities: The Contractor must not operate nor disturb the setting of control devices in the base utilities system, including water, sewer, electrical, and steam services. The Government will operate the control devices as required for normal conduct of the work. The Contractor must notify the Contracting Officer giving reasonable advance notice when such operation is required.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 2

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

08/15

PART 1 GENERAL

1.1 SUBMITTALS

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

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

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Progress and Completion Pictures; G

1.2 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures.

Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file.

Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

1.3 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 LIABILITY, during the entire period of performance under this contract. Provide other insurance coverage as required by State law.

1.4 SUPERVISION

1.4.1 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of contract work. In addition, if a Quality Control (QC) representative is required on the contract, then that individual must also have fluent English communication skills.

1.4.2 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to insure timely completion. Furthermore, SECTION 01 30 00 Page 1 the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.5 PRECONSTRUCTION

After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule of prices or earned value report, shop drawings, and other submittals, scheduling programming,and prosecution of the work. Major subcontractors who will engage in the work must also attend.

1.6 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after contract award, provide the Contracting Officer a single (only one) e-mail address for electronic communications from the Contracting Officer related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes or terrorist threats.

Multiple email addresses are not allowed.

It is the Contractor's responsibility to make timely distribution of all Contracting Officer initiated e-mail with its own organization including field office(s). Promptly notify the Contracting Officer, in writing, of any changes to this email address.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00 Page 2

SECTION 01 31 23.13 20

ELECTRONIC CONSTRUCTION AND FACILITY SUPPORT CONTRACT MANAGEMENT SYSTEM

05/17

PART 1 GENERAL

1.1 CONTRACT ADMINISTRATION

Utilize the Naval Facilities Engineering Command's (NAVFAC's) Electronic Construction and Facility Support Contract Management System (eCMS) for the transfer, sharing and management of electronic technical submittals and documents. The web-based eCMS is the designated means of transferring technical documents between the Contractor and the Government. Paper media or e-mail submission, including originals or copies, of the documents identified in Table 1 are not permitted, except where eCMS is unavailable, non-functional or specifically requested in addition to electronic submission. Contact the Contracting Officer's Representative (COR) regarding availability of eCMS training and reference materials.

1.2 USER PRIVILEGES

The Contractor will be provided access to eCMS. All technical submittals and documents must be transmitted to the Government via the COR. Project roles and system roles will be established to control each user's menu, application, and software privileges, including the ability to create, edit, or delete objects.

1.3 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. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Contractor's Personnel; G

1.4 SYSTEM REQUIREMENTS AND CONNECTIVITY

1.4.1 General

The eCMS requires a web-browser (platform-neutral) and Internet connection. Obtain from an approved vendor an External Certification Authority (ECA), Primary Key Infrastructure (PKI) certificate, or other similar digital identification to support two-factor authentication and access to eCMS. Provide and maintain computer hardware and software for the eCMS access throughout the duration of the contract for all Contractor-designated users. Provide connectivity, speed, bandwidth, and access to the Internet to ensure adequate functionality. Neither upgrading of the Contractor's computer system nor delays associated from the usage of the eCMS will be justification or grounds for a time extension or cost adjustment to the Contract.

SECTION 01 31 23.13 20 Page 1

1.4.2 Contractor Personnel List

Within 20 calendar days of contract award, provide to the Contracting Officer a list of Contractor's personnel who will have the responsibility for the transfer, sharing and management of electronic design, technical submittals and documents and will require access to the eCMS. Project personnel roles to be filled in the eCMS include the Contractor's Project Manager, Designer of Record, Superintendent, Quality Control (QC) Manager, and Site Safety and Health Officer (SSHO). Personnel must be capable of electronic document management. Notify the COR immediately of any personnel changes to the project. The Contracting Officer reserves the right to perform a security check on all potential users. Provide the following information:

First Name Last Name E-mail Address Office Address Project Role (e.g. Project Manager, QC Manager, Superintendent)

1.4.3 Field Administration

Within 30 days of Contract Award, provide a tablet computer with a Common Access Card (CAC) reader at the job site for Government use only. The tablet computer must have a web-browser, built-in camera, and cellular data connectivity. Provide tablet computer with a rugged case suitable for use in a construction environment. The tablet computer must be fully charged and made available at all times for Government use to facilitate the input of construction data at the job site. After completion of the work, reset the tablet computer to factory default settings. The tablet computer remains the property of the Contractor and must be removed from the site.

There are restrictions on use of WIFI on military bases. Cellular data connectivity and availability, and use of WIFI requires coordination with and approval by the Contracting Officer.

1.5 SECURITY CLASSIFICATION

In accordance with Department of Navy guidance, all military construction contract data are unclassified, unless specified otherwise by a properly designated Original Classification Authority (OCA) and in accordance with an established Security Classification Guide (SCG). Refer to the project's OCA when questions arise about the proper classification of information.

The eCMS and tablet computer must only be used for the transaction of unclassified information associated with construction projects. In conformance with the Freedom of Information Act (FOIA), Department of Defense Manual 5200.01-V4: DoD Information Security Program: Controlled Unclassified Information (CUI), and DoD requirements, any unclassified project documentation uploaded into the eCMS must be designated either "U - UNCLASSIFIED" (U) or "FOUO - UNCLASSIFIED-FOR OFFICIAL USE ONLY" (FOUO).

1.6 ECMS UTILIZATION

Establish, maintain, and update data and documentation in the eCMS throughout the duration of the contract.

Personally Identifiable Information (PII) transmittal is not permitted in the eCMS.

SECTION 01 31 23.13 20 Page 2

1.6.1 Information Security Classification/Identification

The eCMS must be used for the transmittal of the following documents. This requirement supersedes conflicting requirements in other sections, however, submittal review times in Section 01 33 00 SUBMITTAL PROCEDURES remain applicable. Table 1 - Project Documentation Types provides the appropriate U and FOUO designations for various types of project documents.

Construction documents requiring FOUO status must be marked accordingly.

Apply the appropriate markings before any document is uploaded into eCMS.

Markings are not required on U documents.

Table 1 also identifies which eCMS application is to be used in the transmittal of data (these are subject to change based on the latest software configuration). If a designated application is not functional within 4 hours of initial attempt, defer to the Submittal application and submit the required data as an uploaded portable document (e.g. PDF), word processor, spreadsheet, drawing, or other appropriate format. Hard copy or e-mail submission of these items is acceptable only if eCMS is documented to be not available or not functional. After uploading documents to the Submittal application, transmit the submittals and attachments to the COR via the Transmittal application. For Submittals, select the following:

Preparation by = Contractor personnel assigned to prepare the submittal Approval by = Contracting Officer Representative (COR) Returned by = Design Lead/Manager Forwarded to = Contractor project manager

Table 1 - Project Documentation Types

SUBJECT/NAME CLASS REMARKS ECMS

APPLICATION

As-Built Drawings U Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

Submittals and Transmittals

Building Information Modeling (BIM)

U 1. Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

2. Design reviews will be performed in existing "Dr Checks"

Submittals and Transmittals

Construction Permits

U Refer to rules of the issuing activity, state or jurisdiction

Submittals and Transmittals

SECTION 01 31 23.13 20 Page 3

SUBJECT/NAME CLASS REMARKS ECMS

APPLICATION

Construction Schedules (Activities and Milestones)

U After the schedule submittal is approved by the COR, import the schedule file into the scheduling application, and select "Approve" to establish a new schedule baseline

Submittals, Transmittals and Scheduling App

Construction Schedules (Cost-Loaded)

FOUO After the schedule submittal is approved by the COR, import the schedule file into the scheduling application, and select "Approve" to establish a new schedule baseline

Submittals, Transmittals and Scheduling App

Construction Schedules (3-Week Lookahead)

U Import the schedule file into the scheduling application, and select "Approve" to establish a new schedule baseline

Scheduling App

DD 1354 Transfer of Real Property

U Submittals and Transmittals

Daily Production Reports

FOUO Provide weather conditions, crew size, man-hours, equipment, and materials information

Daily Report

Daily Quality Control (QC) Reports

FOUO Provide QC Phase, Definable Features of Work Identify visitors

Daily Report

Designs and Specifications

U 1. Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

2. Design reviews will be performed in existing "Dr Checks"

Submittals and Transmittals

Environmental Notice of Violation (NOV), Corrective Action Plan

U Refer to rules of the issuing activity, state or jurisdiction

Submittals and Transmittals

Environmental Protection Plan

(EPP)

FOUO Submittals and

SECTION 01 31 23.13 20 Page 4

SUBJECT/NAME CLASS REMARKS ECMS

APPLICATION

Invoice (Supporting Documentation)

FOUO Applies to supporting documentation only. Invoices are submitted in Wide-Area Workflow (WAWF)

Submittals and Transmittals

Jobsite Documentation, Bulletin Board, Labor Laws, SDS

U Submittals and Transmittals

Meeting Minutes FOUO Meeting Minutes

Operations & Maintenance Support Information (OMSI/eOMSI), Facility Data Worksheet

U 1. Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

2. Design reviews will be performed in existing "Dr Checks"

Submittals and Transmittals

Photographs U Subject to base/installation restrictions

Submittals and Transmittals

QCM Initial Phase Checklists

FOUO Checklists (Site Management)

QCM Preparatory Phase Checklists

FOUO Checklists (Site Management)

Quality Control Plans

FOUO Submittals and Transmittals

QC Certifications U Submittals and Transmittals

QC Punch List U Punch Lists (Testing Logs)

Red-Zone Checklist U Checklists (Site Management)

Rework Items List FOUO Punch Lists (Testing Logs)

Request for Information (RFI) Post-Award

FOUO RFIs

SECTION 01 31 23.13 20 Page 5

SUBJECT/NAME CLASS REMARKS ECMS

APPLICATION

Safety Plan FOUO Daily Report

Safety - Activity Hazard Analyses

(AHA)

FOUO Daily Report

Safety - Mishap Reports

FOUO Daily Report

SCIF/SAPF

Accreditation Support Documents

FOUO Note: Some Construction Security plans may be classified as Secret.

Classified information must not be uploaded into eCMS. Refer to the Site Security Manager, as applicable.

Submittals and Transmittals

Shop Drawings U Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager

Submittals and Transmittals

Storm Water Pollution Prevention (Notice of Intent

- Notice of Termination)

U Refer to rules of the issuing activity, state or jurisdiction

Submittals and Transmittals

Submittals and Submittal Log

U Submittals and Transmittals

Testing Plans, Logs, and Reports

FOUO Submittals and Transmittals

Training/Reference Materials

U Submittals and Transmittals

Training Records (Personnel)

FOUO Submittals and Transmittals

Utility Outage/Tie-In Request/Approval

FOUO Submittals and Transmittals

Warranties/BOD Letter

FOUO Submittals and

SECTION 01 31 23.13 20 Page 6

SUBJECT/NAME CLASS REMARKS ECMS

APPLICATION

Quality Assurance Reports

FOUO Checklists (Government initiated)

Non-Compliance Notices

FOUO Non-Compliance Notices (Government initiated)

Other Government-prepared documents

FOUO GOV ONLY

All Othere Documents

FOUO Refer to FOIA guidelines and contact the FOIA official to determine whether exemptions exist

As applicable

1.6.2 Markings on FOUO documents

a. Only FOUO documents being electronically uploaded into the eCMS (.docx, .xlsx, .pptx and others as appropriate), and associated paper documents described in the paragraph CONTRACT ADMINISTRATION require FOUO markings as indicated in the subparagraphs below.

b. FOUO documents that are originally created within the eCMS application using the web-based forms (RFIs, Daily Reports, and others as appropriate) will be automatically watermarked by the eCMS software, and these do not require additional markings.

c. FOUO documents must be marked "UNCLASSIFIED//FOR OFFICIAL USE ONLY" at the bottom of the outside of the front cover (if there is one), the title page, the first page, and the outside of the back cover (if there is one).

d. FOUO documents must be marked on the internal pages of the document as "UNCLASSIFIED//FOR OFFICIAL USE ONLY"' at top and bottom.

e. Where Installations require digital photographs to be designated FOUO, place the markings on the face of the photograph.

f. For visual documentation, other than photographs and audio documentation, mark with either visual or audio statements as appropriate at both the beginning and end of the file.

1.7 QUALITY ASSURANCE

Requested Government response dates on Transmittals and Submittals must be in accordance with the terms and conditions of the Contract. Requesting response dates earlier than the required review and response time, without concurrence by the Government COR, may be cause for rejection.

Incomplete submittals will be rejected without further review and must be resubmitted. Required Government response dates for resubmittals must reflect the date of resubmittal, not the original submittal date.

SECTION 01 31 23.13 20 Page 7

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

Not Used.

SECTION 01 31 23.13 20 Page 8

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 SUBMITTALS

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

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

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Initial Project Schedule; G Periodic Schedule Update; G

PART 2 PRODUCTS

2.1 SOFTWARE

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

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction design and construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development.

Subcontractors and suppliers Designers, Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.

Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

SECTION 01 32 01.00 10 Page 1

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

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

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

3.3.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.4 Mandatory Tasks

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

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

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

c. Long procurement activities

d. Submission and approval of O & M manuals.

e. Submission and approval of as-built drawings.

f. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent

SECTION 01 32 01.00 10 Page 2 with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

g. Performance Verification testing.

h. Contractor's pre-final inspection.

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

j. Government's pre-final inspection.

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

l. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: approvals, acceptance, environmental permit approvals by State regulators, inspections, utility tie-in, and Notice to Proceed (NTP) for phasing requirements.

3.3.6 Contract Milestones and Constraints

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

Mandatory constraints that ignore or effect network logic are prohibited.

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

3.3.6.1 Project Start Date Milestone and Constraint

The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged.

3.3.6.2 End Project Finish Milestone and Constraint

The last activity in the schedule must be a finish milestone titled "End Project."

Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.6.3 Interim Completion Dates and Constraints

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

SECTION 01 32 01.00 10 Page 3 phase is later than the specified interim completion date.

3.3.6.3.1 Start Phase

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

3.3.6.3.2 End Phase

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

3.3.7 Calendars

Schedule activities on a Calendar to which the activity logically belongs.

Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop sSeasonal Calendar(s) and assign to seasonally affected activities as applicable.

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

3.3.8 Percent Complete

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

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

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

3.4.1 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 15 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period.

SECTION 01 32 01.00 10 Page 4

3.4.2 Periodic Schedule Updates

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

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

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

3.5 SUBMISSION REQUIREMENTS

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

3.5.1 Narrative Report

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

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

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

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

d. Identify and explain why activities based on their calculated late dates should have either started or finished during the update period but did not.

e. Identify and discuss all schedule changes by activity ID and activity name including what specifically was changed and why the change was needed. Include at a minimum new and deleted activities, logic changes, duration changes, calendar changes, lag changes, resource changes, and actual start and finish date changes.

f. Identify and discuss out-of-sequence work.

3.5.2 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports 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. Provide the reports electronically in .pdf format. The following lists typical reports that will be requested:

3.5.2.1 Activity Report

List of all activities sorted according to activity number.

3.5.2.2 Schedule Log

Provide a Scheduling/Leveling Report generated from the current project

SECTION 01 32 01.00 10 Page 5 schedule being submitted.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer.

Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work. Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days after the periodic schedule update meeting.

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled 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. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.8 REQUESTS FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.

3.8.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion

SECTION 01 32 01.00 10 Page 6 date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.8.2 Time Extension

The Contracting Officer must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

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.9 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer may require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.

3.9.1 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and/or may result in corrective action directed by the Contracting Officer pursuant to FAR 52.236-15 Schedules for Construction Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.

3.9.2 Recovery Schedule

Should the Contracting Officer find it necessary, submit a recovery schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.

3.10 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, float available in the schedule, at any time, may not be considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.

SECTION 01 32 01.00 10 Page 7

SECTION 01 33 00

SUBMITTAL PROCEDURES

05/11

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections.

Submittals are identified by Submittal Description (SD) numbers and titles as follows:

SD-01 Preconstruction Submittals

Submittals which are required prior to start of construction (work).

Certificates of insurance

Surety bonds

List of proposed Subcontractors

List of proposed products

Construction progress schedule

Network Analysis Schedule (NAS)

Submittal register

Schedule of prices or Earned Value Report

Health and safety plan

Work plan

Quality Control(QC) plan

Environmental protection plan

SD-02 Shop Drawings

Drawings, diagrams and schedules specifically prepared to illustrate some portion of the work.

Diagrams and instructions from a manufacturer or fabricator for use in producing the product and as aids to the Contractor for integrating the product or system into the project.

Drawings prepared by or for the Contractor to show how multiple systems and interdisciplinary work will be coordinated.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, SECTION 01 33 00 Page 1 instructions and brochures illustrating size, physical appearance and other characteristics of materials, systems or equipment for some portion of the work.

Samples of warranty language when the contract requires extended product warranties.

SD-05 Design Data

Design calculations, mix designs, analyses or other data pertaining to a part of work.

Design submittals, design substantiation submittals and extensions of design submittals.

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product or system identical to the material, product or system to be provided has been tested in accord with specified requirements. Unless specified in another section, testing must have been within three years of date of contract award for the project.

Report which includes findings of a test required to be performed by the Contractor on an actual portion of the work or prototype prepared for the project before shipment to job site.

Report which includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports.

Daily logs and checklists.

Final acceptance test and operational test procedure.

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that the product, system, or material meets specification requirements. Must be dated after award of project contract and clearly name the project.

Document required of Contractor, or of a manufacturer, supplier, installer or Subcontractor through Contractor. The document purpose is to further promote the orderly progression of a portion of the work by documenting procedures, acceptability of methods, or personnel qualifications.

Confined space entry permits.

Text of posted operating instructions.

SD-08 Manufacturer's Instructions

Preprinted material describing installation of a product, system or material, including special notices and (MSDS)concerning impedances, SECTION 01 33 00 Page 2 hazards and safety precautions.

SD-10 Operation and Maintenance Data

Data that is furnished by the manufacturer, or the system provider, to the equipment operating and maintenance personnel, including manufacturer's help and product line documentation necessary to maintain and install equipment. This data is needed by operating and maintenance personnel for the safe and efficient operation, maintenance and repair of the item.

This data is intended to be incorporated in an operations and maintenance manual or control system.

SD-11 Closeout Submittals

Documentation to record compliance with technical or administrative requirements or to establish an administrative mechanism.

Submittals required for Guiding Principle Validation (GPV) or Third Party Certification (TPC).

Special requirements necessary to properly close out a construction contract. For example, Record Drawings and as-built drawings. Also, submittal requirements necessary to properly close out a major phase of construction on a multi-phase contract.

1.1.2 Approving Authority

Office or designated person authorized to approve submittal.

1.1.3 Work

As used in this section, on- and off-site construction required by contract documents, including labor necessary to produce submittals, construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction.

1.2 SUBMITTALS

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

submittals not having a "G" designation are for Contractor QC approval.

Submit the following in accordance with this section.

SD-01 Preconstruction Submittals

Submittal Register; G

1.3 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

1.3.1 Government Approved (G)

Government approval is required for extensions of design, critical materials, deviations, equipment whose compatibility with the entire system must be checked, and other items as designated by the Contracting Officer.

Government approval is required for any deviations from the Solicitation or Accepted Proposal and other items as designated by the Contracting

SECTION 01 33 00 Page 3

Officer. Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, they are considered to be "shop drawings."

1.4 PREPARATION

1.4.1 Transmittal Form

1.4.2 Source Drawings for Shop Drawings

The entire set of Source Drawing files (DWG) will not be provided to the Contractor. Only those requested by the Contractor to prepare shop drawings may be provided. Request the specific Drawing Number only for the preparation of Shop Drawings. These drawings may only be provided after award.

1.4.2.1 Terms and Conditions

Data contained on these electronic files must not be used for any purpose other than as a convenience in the preparation of construction data for the referenced project.