COMBINED_FINAL_WATER_MAIN_SPECS.pdf

SECTION 01 11 00 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. 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

Utility Outage Requests

Utility Connection Requests

Borrow Permits

Excavation Permits

Welding Permits

Burning Permits

Salvage Plan; G

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes demolition of an existing pipe, pipe fittings, valves, valve cans, and related items; installation of a new pipe including valves;

reconnection of water service lateral and water loop; and related piping, bypass, and incidental related work.

1.2.2 Location

The work is located at the Naval Base San Diego, approximately as indicated. The exact location will be shown by the Contracting Officer.

1.3 CONTRACT DRAWINGS

The following drawings accompany this specification and are a part thereof.

Existing Utility GIS Maps (Area 5 and Area 9)

NAVFAC Utility Standard Drawings (G-1, W-2, W-3, W-4, and W-6)

Reference publications will not be furnished. Immediately check furnished drawings and notify the Government of any discrepancies.

SECTION 01 11 00 Page 2

1.4 OCCUPANCY OF PREMISES

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

Occupancy notifications will be posted in a prominent location in the work area.

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

1.5 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 must be in a condition equal to or better than that which existed before new work started.

1.6 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, pier deck or paved surface where existing underground utilities or utilities encased in pier structures are discovered. Verify the elevations of existing piping, utilities,and any type of underground or encased 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. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.

1.6.1 Notification Prior to Excavation

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

1.7 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged remain the property of the Government. Segregate, itemize, deliver and off-load the salvaged property at the Government designated storage area.

Provide a salvage plan, listing material and equipment to be salvaged, and their storage location. Maintain property control records for material or

SECTION 01 11 00 Page 3 equipment designated as salvage. Use a system of property control that is approved by the Contracting Officer. Store and protect salvaged materials and equipment until disposition by the Contracting Officer.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

-- End of Section --

SECTION 01 20 00.00 20 Page 1

SECTION 01 20 00.00 20

PRICE AND PAYMENT PROCEDURES

11/11

1.1 SUBMITTALS

approval. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING.

Earned Value Report; G

1.2 EARNED VALUE REPORT

1.2.1 Data Required

This contract requires the use of a cost-loaded Network Analysis Schedule

(NAS). The information required for the Schedule of Prices will be entered as an integral part of the Network Analysis Schedule. Within 15 calendar days of notice of award, prepare and deliver to the Contracting Officer an

Earned Value Report (construction contract) as directed by the Contracting

Officer. Provide a detailed breakdown of the contract price, giving quantities for each of the various kinds of work, unit prices, and extended prices. Costs shall be summarized and totals provided for each construction category.

1.2.2 Schedule Instructions

Payments will not be made until the Earned Value Report from the cost-loaded NAS has been submitted to and accepted by the Contracting

Officer. Identify the cost for site work, and include incidental work to the

5 ft line. Identify costs for the building(s), and include work out to the

5 ft line. Work out to the 5 ft line shall include construction encompassed within a theoretical line 5 ft from the face of exterior walls and shall include attendant construction, such as pad mounted HVAC cooling equipment, cooling towers, and transformers placed beyond the 5 ft line.

1.2.3 Real Property Assets

The Government will provide the Draft DD Form 1354, Transfer and Acceptance of Military Real Property filled in with the appropriate Real Property

Unique Identifiers (RPUID) and related construction Category Codes to summarize the designed real property assets that apply to this contract.

The Contractor shall meet with the Contracting Officer and the Real

Property Accounting Officer during the Pre Construction Meeting and the

Project Closeout Meetings to modify and include any necessary changes to the DD Form 1354. The Contractor shall provide the Interim DD Form 1354 that uses the appropriate division of the RPUIDs/ Category Codes to represent the final constructed facility and include all associated cost.

Coordinate the Contractor's Price and Payment structure with the structure

SECTION 01 20 00.00 20 Page 2 of the RPUIDs/ Category Codes.

Divide detailed asset breakdown into the RPUIDs and related construction

Category Codes and populate associated costs which represent all aspects of the work. Where assets diverge into multiple RPUID/ Category Codes, divide the asset and provide the proportion of the assets in each RPUID/ Category

Code. Assets and related RPUID/ Category Codes may be modified by the

Contracting Officer as necessary during course of the work. Coordinate identification and proportion of these assets with the Government Real

Property Accounting Officer.

Cost data accumulated under this section are required in the preparation of

DD Form 1354.

1.3 CONTRACTOR'S INVOICE AND CONTRACT PERFORMANCE STATEMENT

1.3.1 Content of Invoice

Requests for payment will be processed in accordance with the Contract

Clause FAR 52.232-27, Prompt Payment Construction Contracts and FAR

52.232-5, Payments Under Fixed-Price Construction Contracts. The requests for payment shall include the documents listed below.

a. The Contractor's invoice, on NAVFAC Form 7300/30 furnished by the

Government, showing in summary form, the basis for arriving at the amount of the invoice. Form 7300/30 shall include certification by

Contractor and Quality Control (QC) Manager.

b. The Estimate for Voucher/ Contract Performance Statement on NAVFAC Form

4330/54 furnished by the Government Earned Value Report from the cost-loaded NAS, showing in detail: the estimated cost, percentage of completion, and value of completed performance for each of the construction categories stated in this contract. Use NAVFAC Form

43300/54 on NAVFAC contracts when a Monthly Estimate for Voucher is required.

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

d. Contractor Safety Self Evaluation Checklist.

e. Other supporting documents as requested.

f. Updated copy of submittal register.

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

h. Monthly Work-hour report.

i. Solid Waste Disposal Report.

1.3.2 Submission of Invoices

If DFARS Clause 5252.232-7006 is included in the contract, provide the documents listed in paragraph CONTENT OF INVOICE in their entirety as attachments in Wide Area Work Flow (WAWF) for each invoice submitted. The maximum size of each WAWF attachment is two megabytes, but there are no limits on the number of attachments. If a document cannot be attached in

WAWF due to system or size restriction, provide it as instructed by the

SECTION 01 20 00.00 20 Page 3

Contracting Officer.

1.3.3 Final Invoice

a. A final invoice shall be accompanied by the certification required by

DFARS 252.247.7023 TRANSPORTATION OF SUPPLIES BY SEA, and the

Contractor's Final Release. If the Contractor is incorporated, the

Final Release shall contain the corporate seal. An officer of the corporation shall sign and the corporate secretary shall certify the

Final Release.

b. For final invoices being submitted via WAWF, the original Contractor's

Final Release Form and required certification of Transportation of

Supplies by Sea must be provided directly to the respective Contracting

Officer prior to submission of the final invoice. Once receipt of the original Final Release Form and required certification of

Transportation of Supplies by Sea has been confirmed by the Contracting

Officer, the Contractor shall then submit final invoice and attach a copy of the Final Release Form and required certification of

Transportation of Supplies by Sea in WAWF.

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

1.4 PAYMENTS TO THE CONTRACTOR

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

1.4.1 Obligation of Government Payments

The obligation of the Government to make payments required under the provisions of this contract will, at the discretion of the Contracting

Officer, be subject to reductions and suspensions permitted under the FAR and agency regulations including the following in accordance with FAR

32.503-6:

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

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

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

d. Failure to provide up to date record drawings not current as stated in

Contract Clause "FAC 5252.236-9310, Record Drawings."

1.4.2 Payment for Onsite and Offsite Materials

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

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

SECTION 01 20 00.00 20 Page 4

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

c. Materials to be considered for progress payment prior to installation shall be specifically and separately identified in the Contractor's estimates of work submitted for the Contracting Officer's approval in accordance with Earned Value Report requirement of this contract.

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

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

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

f. Materials to be considered for progress payments prior to installation shall be stored either in Hawaii, Guam, Puerto Rico, or the Continental

United States. Other locations are subject to written approval by the

Not Used

SECTION 01 30 00 Page 5

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

08/15

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

EM 385-1-1 (2014) Safety and Health Requirements

Manual

1.2 SUBMITTALS

approval.Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING.

View Location Map; G

Progress and Completion Pictures; G

Insurance; G

1.3 VIEW LOCATION MAP

Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.

1.4 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 true color 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.

SECTION 01 30 00 Page 6

1.4.1 Camera Passes

A Camera Pass will be required to take pictures of the work. Camera passes will be issued for each individual using an official company issued camera.

Camera passes limit pictures to a specific work site and may not be used to take pictures of other areas.

To obtain a Camera Pass, submit the following information to the Contracting

Officer:

1. Company name

2. Camera serial number and model

3. Name of indivudual using camera

4. Date of birth

5. US Citizen?

1.5 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.6 SUPERVISION

1.6.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.6.2 Superintendent Qualifications

The project superintendent must have a minimum of 10 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

1.6.2.1 Duties

The project superintendent is primarily responsible for managing and coordinating day-to-day production and schedule adherence on the project.

The superintendent is required to attend NAVFAC Red Zone meetings, partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.6.3 Project Manager

1.6.3.1 Project Manager Qualifications

The Project Manager must have a minimum 10 years experience as a Project

Manager or Superintendent on projects of similar size and complexity.

1.6.4 Non-Compliance Actions

SECTION 01 30 00 Page 7

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

After award of the contract but prior to commencement of any work at the

SECTION 01 30 00 Page 8 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, prosecution of the work, and clear expectations of the "Interim DD Form

1354" Submittal. Major subcontractors who will engage in the work must also attend.

1.8 FACILITY TURNOVER PLANNING MEETINGS (NAVFAC Red Zone - NRZ)

Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start the turnover process at the Pre-Construction Conference meeting with a discussion of the NAVFAC Red Zone (NRZ) process and convene at regularly scheduled NRZ Meetings. Include the following in the facility Turnover effort:

1.8.1 NRZ Checklist

a. Contracting Officer's Technical Representative (COTR) will provide the

Contractor a copy of the NRZ Checklist template prior to 75 percent completion.

b. Prior to 75 percent completion add/delete critical activities to the

NRZ Checklist template as necessary to match the project scope, and schedule critical activities and insert planned completion dates in the

NRZ checklist for each critical activity. Present the NRZ Checklist to

COTR and review during a regularly scheduled QC Meeting.

1.8.2 Meetings

a. Upon Government acceptance of the NRZ Checklist, the Project

Superintendent is required to lead regular NRZ Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.

b. The Contracting Officer will determine the frequency of the meetings, which is expected to increase as the project completion draws nearer.

c. Using the NRZ Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.

d. Coordinate with the COTR any upcoming activities that require

Government involvement.

e. Maintain the NRZ Checklist by documenting the actual completion dates as work is completed and update the NRZ Checklist with revised planned completion dates as necessary to match progress. Distribute copies of the current NRZ Checklist to attendees at each NRZ Meeting.

1.9 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, SECTION 01 30 00 Page 9 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.

SECTION 01 32 17.00 20 Page 1

SECTION 01 32 17.00 20

COST-LOADED NETWORK ANALYSIS SCHEDULES (NAS)

02/15

1.1 DESCRIPTION

The Contractor is responsible for scheduling procurement, Contractor quality control and construction, acceptance testing and training. Refer to Specification Section 01 33 00 SUBMITTAL PROCEDURES to determine if any items require Government approval prior to construction; if any are required, include that submittal review time in the schedule.

The schedule is a tool to manage the project, both for Contractor and

Government activities. It will also be used to report progress and evaluate time extensions. The Project NAS must be cost-loaded and will provide the basis for progress payments. Use the Critical Path Method

(CPM) and the Precedence Diagram Method (PDM) to satisfy time and cost applications. For consistency, when scheduling software terminology is used in this specification, the terms in Primavera's scheduling programs are used.

1.2 SUBMITTALS

The use of a "G" following a submittal indicates that a Government approval action is required. Submit the following in accordance with Section

01 33 00 SUBMITTAL PROCEDURES.

Qualifications; G

Baseline Network Analysis Schedule (NAS); G

SD-07 Certificates

Monthly Network Analysis Schedule Update; G

SD-11 Closeout Submittals

As-Built Schedule; G

1.3 SCHEDULE ACCEPTANCE PRIOR TO START OF WORK

Participate with the Contracting Officer in a preliminary meeting(s) to discuss the proposed schedule and requirements of this section prior to the

Contractor preparing the Project Baseline Schedule. Government review comments on the Contractor's schedule(s) do not relieve the Contractor from compliance with requirements of the Contract Documents. Only bonds may be paid prior to acceptance of the Baseline Network Analysis Schedule (NAS)

The acceptance of a Baseline NAS is a condition precedent to:

a. The Contractor starting work on the demolition or construction stage(s) of the contract.

b. Processing Contractor's invoices(s) for construction activities/items

SECTION 01 32 17.00 20 Page 2 of work.

c. Review of any schedule updates.

Submittal of the Baseline Network Analysis Schedule, and subsequent schedule updates, is understood to be the Contractor's certification that the submitted schedule meets all of the requirements of the Contract

Documents, represents the Contractor's plan on how the work will be accomplished, and accurately reflects the work that has been accomplished and how it was sequenced (as-built logic).

1.4 SOFTWARE

Prepare and maintain project schedules using Primavera P6. Importing data into P6 using data conversion techniques or third party software is cause for rejection of the submitted schedule.

A listing of Primavera P6 settings and parameters which must be used in preparing the Schedules are contained later in this specification section.

Deviation from these settings and parameters, without prior consent of the

Contracting Officer, is cause for rejection of schedule submission.

1.5 QUALIFICATIONS

The designated Scheduler for the project must have prepared and maintained at least 3 previous schedules of similar size and complexity of this contract using Primavera P3, Primavera SureTrak, or Primavera P6. At least one of the three must be in Primavera P6. Submit a resume outlining the qualifications of the Scheduler. Payment will not be processed until an acceptable Scheduler is provided.

1.6 NETWORK SYSTEM FORMAT

The system must include time-scaled logic diagrams and specified reports.

1.6.1 Diagrams

Provide Time-scaled Logic Diagram printed in color on ANSI D size sheets.

The diagram must clearly show activities on the critical path. Include the following information for each activity:

a. Activity ID

b. Activity Description

c. Original Duration in Work Days

d. Remaining duration in Work Days

e. Physical Percent Complete

f. Start Date

g. Finish Date

h. Total Float

SECTION 01 32 17.00 20 Page 3

1.6.2 Schedule Activity Properties and Level of Detail

The NAS must identify all Government, Construction Quality Management

(CQM), Construction activities planned for the project and all other activities that could impact project completion if delayed. Create separate activities for each Phase, Area, Floor Level and Location the activity is occurring. Activity categories included in the schedule are specified below.

With the exception of the Contract Award and Contract Completion Date (CCD) milestone activities, no activity shall be open-ended; each activity must have predecessor and successor ties. No activity must have open start or open finish (dangling) logic. Minimize redundant logic ties. Once an activity exists on the schedule it must not be deleted or renamed to change the scope of the activity and must not be removed from the schedule logic without approval from the Contracting Officer. While an activity cannot be deleted, where said activity is no longer applicable to the schedule but must remain within the logic stream for historical record, it can be changed to a milestone. Document any such change in the milestone's

"Notebook", including a date and explanation for the change. The ID number for a deleted activity must not be re-used for another activity. Within the Baseline Schedule no more than 20 percent of the activities shall be critical or near critical. Critical is defined as having zero days of

Total Float. "Near Critical" is defined as having Total Float of 1 to 14 days. Contractor activities must be driven by calendars that reflect

Saturdays, Sundays and all Federal Holidays as non-work days.

1.6.2.1 Activity Categories

1.6.2.1.1 Procurement Activities

Examples of procurement activities include, but are not limited to;

Material/equipment submittal preparation, submittal and approval of material/equipment; material/equipment fabrication and delivery, and material/equipment on-site. As a minimum, separate procurement activities will be provided for critical items, long lead items, items requiring

Government approval and material/equipment procurement for which payment will be requested in advance of installation. Show each delivery with relationship tie to the Construction Activity specifically for the delivery.

1.6.2.1.2 Government Activities

Government and other agency activities that could impact progress must be clearly identified. Government activities include, but are not limited to;

Government approved submittal reviews, Government conducted inspections/tests, environmental permit approvals by State regulators, utility outages, and delivery of Government Furnished Material/Equipment.

1.6.2.1.3 Quality Management (QM) Activities

The Preparatory Phase and Initial Phase for each Definable Feature of Work identified in the Contractor's Quality Control Plan must be added to each

Three-Week Look Ahead Schedule referenced in the paragraph THREE-WEEK LOOK

AHEAD SCHEDULE. The Follow-up Phase will be represented by the

Construction Activities in the Baseline Schedule and in the schedule updates.

SECTION 01 32 17.00 20 Page 4

1.6.2.1.4 Construction Activities

No on-site construction activity may have a duration in excess of 20 working days. Contractor activities must be driven by calendars that reflect Saturdays, Sundays and all Federal Holidays as non-work days, unless otherwise defined in this contract.

1.6.2.1.5 Turnover and Closeout Activities

Include activities with all items on the NAVFAC Red Zone Checklist/POAM that are applicable to this project. As a minimum, include all testing, specialized inspection activities, Pre-Final Inspection, Punch List

Completion, Final Inspection and Acceptance. Add a milestone for the

Facility Turnover Planning Meeting at approximately 75 percent construction contract completion or three to six months prior to Contract Completion

Date (CCD), whichever is sooner.

1.6.2.2 Contract Milestones and Constraints

1.6.2.2.1 Project Start Date Milestones

Include as the first activity on the schedule a start milestone titled

"Contract Award", which must have a Mandatory Start constraint equal to the

Contract Award Date.

1.6.2.2.2 Facility Turnover Planning Meeting Milestones

See paragraph ACTIVITY CATEGORIES above.

1.6.2.2.3 Substantial Completion Milestone

Include an unconstrained finish milestone on the schedule titled

"Substantial Completion". Substantial Completion is defined as the point in time the Government would consider the project ready for beneficial occupancy wherein by mutual agreement of the Government and Contractor, Government use of the facility is allowed while construction access continues in order to complete remaining items (e.g. punch list and other close out submittals).

1.6.2.2.4 Projected Completion Milestone

Include an unconstrained finish milestone on the schedule titled "Projected

Completion". Projected Completion is defined as the point in time the

Government would consider the project complete. This milestone must have the Contract Completion (CCD) milestone as its only successor.

1.6.2.2.5 Contract Completion Date (CCD) Milestone

Include as the last activity on the schedule a finish milestone titled

"Contract Completion (CCD)". Calculation of schedule updates must be such that if the finish of the "Projected Completion" milestone falls after the contract completion date, then negative float will be calculated on the longest path and if the finish of the "Projected Completion" milestone falls before the contract completion date, the float calculation must reflect positive float on the longest path.

1.6.2.3 Work Breakdown Structure & Activity Code

At a minimum, the Contractor must establish a Work Breakdown Structure

SECTION 01 32 17.00 20 Page 5

(WBS) and provide activity codes identified as follows:

1.6.2.3.1 Work Breakdown Structure (WBS)

Group all activities and milestones within appropriate WBS categories including, at a minimum, the following:

a. Project Milestones:

(1) Management Milestones

(2) Project Administrative Meetings

b. Pre-Construction Phase:

(1) Submittals and Reviews

(2) Procurement

c. Construction Phase; Create multiple sub-sections in accordance with project specific categories of work including in WBS descending order as follows:

(1) General Area

(a) Type of Work Item

1. Location

d. Commissioning & Testing:

(1) Specific area/locations of commissioning

(2) Final Testing

(3) Training

e. Project Closeout: Include activity items such as Punchlist, Demobilization, O&M, As-built Drawings, and As-built NAS.

f. Modifications: Create multiple sub-sections as the project progresses identified by modifications issued.

1.6.2.3.2 Responsibility Code

All activities in the project schedule must be identified with the party responsible for completing the task. Activities must not belong to more than one responsible party.

1.6.2.3.3 Construction Specification Institute (CSI) Masterformat Code

Identify all activities in the project schedule with its respective

Specification Section number. Activities must not belong to more than one

Section number. If an activity does not have an applicable CSI Code (e.g.

Mobilize), the code must be "0000".

1.6.2.4 Anticipated Weather Lost Work Days

Use the National Oceanic and Atmospheric Administration's (NOAA) historical

SECTION 01 32 17.00 20 Page 6 monthly averages for days with precipitation, using a nominal 30-year, greater than 0.10 inch amount parameter, as indicated on the Station Report for the NOAA location closest to the project site as the basis for establishing a "Weather Calendar" showing the number of anticipated non-workdays for each month due to adverse weather, in addition to

Saturdays, Sundays and all Federal Holidays as non-work days.

Assign the Weather Calendar to any activity that could be impacted by adverse weather. The Contracting Officer will issue a modification in accordance with the contract clauses, giving the Contractor a time extension for the difference of days between the anticipated and actual adverse weather delay if the number of actual adverse weather delay days exceeds the number of days anticipated for the month in which the delay occurs and the adverse weather delayed activities are critical to contract completion. A lost workday due to weather conditions is defined as a day in which the Contractor cannot work at least 50 percent of the day on the impacted activity.

1.6.2.5 Anticipated Restricted Delays

Allow in the schedule a total of 5 lost workdays per calendar year for instances where base access is not permitted due to a restriction or closure which causes a delay in the work. A lost workday is defined as a day which the Contractor cannot work at least 50 percent of the day on the closed installation. If the installation is closed for a period longer than 5 lost workdays per calendar year, the Contracting Officer will issue a no cost contract modification as applicable in accordance with the contract clauses extending the contract completion date where the critical path has been impacted.

1.6.2.6 Cost Loading

1.6.2.6.1 Cost Loading Activities

Assign Material and Equipment Costs, for which payment will be requested in advance of installation, to their respective procurement activity (i.e., the material/equipment on-site activity). Assign cost for material/equipment, paid for after installation; labor; and construction equipment to their respective Construction Activities. The value of commissioning, testing and closeout WBS section may not be less than 10 percent of the total costs for Procurement and Construction Activities.

Evenly disperse overhead and profit to each activity over the duration of the project.

1.6.2.6.2 Quantities and Units of Measure

Each cost loaded activity must have a detailed quantity breakdown and unit of measure. Lump sum costing is not acceptable.

1.6.3 Schedule Software Settings and Restrictions

a. Activity Constraints: Date/time constraint(s), other than those required by the contract, are not allowed unless accepted by the

Contracting Officer. Identify any constraints proposed and provide an explanation for the purpose of the constraint in the Narrative Report as described in paragraph REQUIRED TABULAR REPORTS.

b. Default Progress Data Disallowed: Actual Start and Actual Finish dates on the CPM schedule must match the dates on the Contractor Quality

SECTION 01 32 17.00 20 Page 7

Control and Production Reports.

c. Software Settings: Handle schedule calculations and Out-of-Sequence progress (if applicable) through Retained Logic, not Progress

Override. Show all activity durations and float values in days. Show activity progress using Remaining Duration. Set default activity type to "Task Dependent".

d. At a minimum, include the following settings and parameters in Baseline

Schedule preparation:

(1) General: Define or establish Calendars and Activity Codes at the "Project" level, not the "Global" level.

(2) Admin Drop-Down Menu, Admin Preferences, Time Periods Tab:

(a) Set time periods for P6 to 8.0 Hours/Day, 40.0 Hours/Week,

172.0 Hours/Month and 2000.0 Hours/Year.

(b) Use assigned calendar to specify the number of work hours for each time period: Must be checked.

(3) Admin Drop-Down Menu, Admin Preferences, Earned Value Tab:

(a) Earned Value Calculation: Use "Budgeted values with current dates".

(4) Project Level, Dates Tab:

(a) Set "Must Finish By" date to "Contract Completion Date".

(5) Project Level, Defaults Tab:

(a) Duration Type: Set to "Fixed Duration & Units".

(b) Percent Complete Type: Set to "Physical".

(c) Activity Type: Set to "Task Dependent".

(d) Calendar: Set to "Standard 5 Day Workweek". Calendar must reflect Saturday, Sunday and all Federal holidays as non-work days. Alternative calendars may be used with Contracting Officer approval.

(6) Project Level, Calculations Tab:

(a) Activity percent complete based on activity steps: Must be Checked.

(b) Reset Remaining Duration and Units to Original: Must be Checked.

(c) Subtract Actual from At Completion: Must be Checked.

(d) Recalculate Actual units and Cost when duration percent(%) complete changes: Must be Checked.

(e) Link Actual to Date and Actual This Period Units and Cost:

Must be Checked.

SECTION 01 32 17.00 20 Page 8

(f) Price/Unit: Set to "$1/h".

(g) Update units when costs change on resource assignments: Must be Unchecked.

(7) Project Level, Settings Tab:

(a) Define Critical Activities: Check "Total Float is less than or equal to" and add "0d".

(8) Work Breakdown Structure Level, Earned Value Tab:

(a) Technique for Computing Performance Percent Complete:

"Activity percent complete" is selected.

(b) Technique for Computing Estimate to Complete (ETC): "PF = 1" is selected.

1.6.4 Required Tabular Reports

Include the following reports with the Baseline, Monthly Update and any other required schedule submittals:

a. Log Report: Listing of all changes made between the previous schedule and current updated schedule.

b. Narrative Report: Identify and justify:

(1) Progress made in each area of the project;

(2) Critical Path;

(3) Date/time constraint(s), other than those required by the contract

(4) Changes in the following; added or deleted activities, original and remaining durations for activities that have not started, logic, milestones, planned sequence of operations, critical path, and cost loading;

(5) Any decrease in previously reported activity Earned Amount;

(6) Pending items and status thereof, including permits, changes orders, and time extensions;

(7) Status of Contract Completion Date and interim milestones;

(8) Current and anticipated delays (describe cause of delay and corrective actions(s) and mitigation measures to minimize);

(9) Description of current and future schedule problem areas.

Each entry in the narrative report must cite the respective Activity ID and Activity Description, the date and reason for the change, and description of the change.

c. Earned Value Report: List all activities having a budget amount cost loaded. Compile total earnings on the project from notice to proceed to current progress payment request. Show current budget, previous

SECTION 01 32 17.00 20 Page 9 physical percent complete, to-date physical percent complete, previous earned value, to-date earned value and cost to complete on the report for each activity.

d. Schedule Variance Control (SVC) Diagram: With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates and 2) Earned Value to-date. Revise Cash Flow

S-Curves when the contract is modified, or as directed by the

1.7 SUBMISSION AND ACCEPTANCE

1.7.1 Monthly Network Analysis Updates

Meet with Government representatives at monthly intervals to review and agree on the information presented in the updated project schedule. The submission of an acceptable, updated schedule to the Government is a condition precedent to the processing of the Contractor's invoice. Submit an acceptable, updated schedule to the Government regardless of whether a

Contractor's invoice is submitted for the given period. The Contractor and

Government must consent to agree on percentage of payment for each activity progressed during the update period. Monthly update schedules must incorporate as-built events as they occurred and provide ongoing status of anticipated finish dates. As-built events must correspond to contemporaneous records including but not limited to submittals, daily production reports and quality control reports.

Provide the following with each Schedule submittal:

a. Time-Scaled Logic Diagram.

b. Reports listed in paragraph entitled "REQUIRED TABULAR REPORTS."

c. Data disks containing the project schedule. Include the back-up native .xer program files.

1.7.2 As-Built Schedule

As a condition precedent to the release of retention and making final payment, submit an "As-Built Schedule," as the last schedule update showing all activities at 100 percent completion. This schedule must reflect the exact manner in which the project was actually constructed.

1.8 CONTRACT MODIFICATION

Submit a Time Impact Analysis (TIA) with each cost and time proposal for a proposed change. TIA must illustrate the influence of each change or delay on the Contract Completion Date or milestones. No time extensions will be granted nor delay damages paid unless a delay occurs which consumes all available Project Float, and extends the Projected Finish beyond the

Contract Completion Date.

a. Each TIA must be in both narrative and schedule form. The narrative must define the scope and conditions of the change; provide start and finish dates of impact, successor and predecessor activity to impact period, responsible party; describe how it originated, and how it impacts the schedule. The schedule submission must consist of three native files:

SECTION 01 32 17.00 20 Page 10

(1) Fragnet used to define the scope of the changed condition

(2) Most recent accepted schedule update as of the time of the proposal or claim submission that has been updated to show all activity progress as of the time of the impact start date.

(3) The impacted schedule that has the fragnet inserted in the updated schedule and the schedule “run” so that the new completion date is determined.

b. For claimed as-built project delay, the inserted fragnet TIA method must be modified to account for as-built events known to occur after the data date of schedule update used.

c. All TIAs must include any mitigation, and must determine the apportionment of the overall delay assignable to each individual delay. The associated narrative must clearly describe the findings in a chronological listing beginning with the earliest delay event.

(1) Identify types of delays as follows:

(a) Excusable Delay: Force-Majeure (e.g. weather) - Contractor may receive time extension, but time will not be compensable.

(b) Inexcusable Delay: Contractor Responsibility – Contractor will not receive time extension.

(c) Compensable Delay: Government Responsibility – Contractor may receive compensable time extension.

(2) If a combination of any of the delay types outlined above occurs, it is considered Concurrent Delay, which will require an analysis of the facts to determine compensability and entitlement to any time extension under the applicable contract clauses.

d. Submit Data disks containing the narrative and native schedule files.

e. Unless the Contracting Officer requests otherwise, only add conformed contract modifications into the Project NAS.

1.8.1 No Reservation of Rights

All direct costs, indirect cost, and time extensions will be negotiated and made full, equitable and final at the time of modification issuance.

1.9 PROJECT FLOAT

Project Float is the length of time between the Contractor's Projected

Completion Milestone and the Contract Completion Date Milestone. Project

Float available in the schedule will not be for the exclusive use of either the Government or the Contractor.

The use of Resource Leveling or other techniques used for the purpose of artificially adjusting activity durations to consume float and influence critical path is prohibited.

SECTION 01 32 17.00 20 Page 11

1.10 THREE-WEEK LOOK AHEAD SCHEDULE

Prepare and issue a 3-Week Look Ahead schedule to provide a more detailed day-to-day plan of upcoming work identified on the Project Network Analysis

Schedule. Key the work plans to NAS activity numbers and update each week to show the planned work for the current and following two-week period.

Additionally, include upcoming outages, closures, field evaluation tests, preparatory meetings, and initial meetings. Identify critical path activities on the Three-Week Look Ahead Schedule. The detail work plans are to be bar chart type schedules, derived from but maintained separately from the Project NAS on an electronic spreadsheet program and printed on

8-1/2 by 11 inch sheets as directed by the Contracting Officer. Activities must not exceed 5 working days in duration and have sufficient level of detail to assign crews, tools and equipment required to complete the work.

Deliver three hard copies and one electronic file of the 3-Week Look Ahead

Schedule to the Contracting Officer no later than 8 a.m. each Monday and review during the weekly CQC Coordination or Production Meeting.

1.11 CORRESPONDENCE AND TEST REPORTS

All correspondence (e.g., letters, Requests for Information (RFIs), e-mails, meeting minute items, Production and QC Daily Reports, material delivery tickets, photographs) must reference Schedule activity IDs that are being addressed. All test reports (e.g., concrete, soil compaction, weld, pressure) must reference schedule activity IDs that are being addressed.

1.12 ADDITIONAL SCHEDULING REQUIREMENTS

Any references to additional scheduling requirements, including systems to be inspected, tested and commissioned, that are located throughout the remainder of the Contract Documents, are subject to all requirements of this section.

SECTION 01 33 00 Page 1

SECTION 01 33 00

SUBMITTAL PROCEDURES

05/11

1.1 SUMMARY

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections.

Units of weights and measures used on all submittals are to be the same as those used in the contract drawings.

Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Contractor's Quality Control (CQC) System Manager and the Designer of

Record, if applicable, to check and approve all items prior to submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals items such as: Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited

to) catalog cuts, diagrams, operating charts or curves; test reports; test cylinders; samples; O&M manuals (including parts list); certifications;

warranties; and other such required submittals.

Submittals requiring Government approval are to be scheduled and made prior to the acquisition of the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Material Safety Data Sheets (MSDS) and in compliance with existing laws and regulations.

A submittal register showing items of equipment and materials for when submittals are required by the specifications is provided as "Appendix A -

Submittal Register".

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittals requirements are specified in the technical sections.

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

Submittals which are required prior to start of construction

(work).issuance of contract notice to proceed.or commencing work on site.or the start of the next major phase of the construction on a multi-phase contract, includes schedules, tabular list of data, or tabular list including location, features, or other pertinent information regarding products, materials, equipment, or components to be used in the work.

Certificates of insurance

SECTION 01 33 00 Page 2

Surety bonds

List of proposed Subcontractors

List of proposed products

Construction progress schedule

Network Analysis Schedule (NAS)

Submittal register

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, 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-04 Samples

Fabricated or unfabricated physical examples of materials, equipment or workmanship that illustrate functional and aesthetic characteristics of a material or product and establish standards by…