Attachment_1_Specifications_20_July_2016.pdf

S P E C I F I C A T I O N

FOR PROJECT

QJVF14-0027

CONSTRUCT SGT PAD

AT

MINOT AIR FORCE BASE, NORTH DAKOTA

PREPARED BY:

5 CES, ENGINEERING FLIGHT

MINOT AIR FORCE BASE, NORTH DAKOTA

27 April 2016

I HEREBY CERTIFY THAT THIS ENGINEERING

DOCUMENT WAS PREPARED BY ME OR UNDER MY

DIRECT PERSONAL SUPERVISION AND THAT I AM A

DULY LICENSED PROFESSIONAL ENGINEER UNDER

THE LAWS OF THE STATE OF NORTH DAKOTA

0, 1, 2

SPECIFICATION DIVISIONS COVERED BY THIS SEAL:

STEPHEN R. SMITH, AIA

ARCHITECT DATE

I HEREBY CERTIFY THAT THIS ENGINEERING

DOCUMENT WAS PREPARED BY ME OR UNDER MY

DIRECT PERSONAL SUPERVISION AND THAT I AM A

DULY LICENSED PROFESSIONAL ENGINEER UNDER

THE LAWS OF THE STATE OF NEBRASKA

31, 32, 33

SPECIFICATION DIVISIONS COVERED BY THIS SEAL:

CHRISTOPHER J. LANGAN, PE

CIVIL ENGINEER DATE

I HEREBY CERTIFY THAT THIS ENGINEERING

DOCUMENT WAS PREPARED BY ME OR UNDER MY

DIRECT PERSONAL SUPERVISION AND THAT I AM A

DULY LICENSED PROFESSIONAL ENGINEER UNDER

THE LAWS OF THE STATE OF NEBRASKA

26, 33

SPECIFICATION DIVISIONS COVERED BY THIS SEAL:

MICHAEL D. WALLACE, PE

ELECTRICAL ENGINEER DATE

18 MARCH 2016

18 MARCH 2016

18 MARCH 2016

R

C

H

I

T

E

C

T

A

D

E

C

I

L

N

S

E

T

S

M

S

R

N

E

H

P

E

T

S

(2625)

T

I

H

A

T

E

O

F

N

RO

T

H

D

A

K

O

T

A

3/18/16

PROJECT TABLE OF CONTENTS Page 2

{Construct SGT Pad, Minot AFB, ND}

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING

REQUIREMENTS

00 01 15 LIST OF DRAWINGS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 29 SUSTAINABILITY REPORTING

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.10 20 QUALITY CONTROL FOR MINOR CONSTRUCTION

01 57 20.00 10 ENVIRONMENTAL PROTECTION

{QJVF 14-0027}

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 78 39 AS-BUILT DRAWINGS

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

DIVISION 26 - ELECTRICAL

26 08 00 APPARATUS INSPECTION AND TESTING

26 12 21 SINGLE-PHASE PAD-MOUNTED TRANSFORMERS

26 20 00 ELECTRICAL DISTRIBUTION SYSTEM

26 41 00 LIGHTNING PROTECTION SYSTEM

26 56 00 EXTERIOR LIGHTING

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 05 19 GEOTEXTILE

31 11 00 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 19 FIELD MOLDED SEALANTS FOR SEALING JOINTS IN RIGID

PAVEMENTS

32 11 10 DRAINAGE LAYER

32 12 17 HOT MIX BITUMINOUS PAVEMENT

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 17 23.00 20 PAVEMENT MARKINGS

32 92 19 SEEDING

PROJECT TABLE OF CONTENTS Page 2

DIVISION 33 - UTILITIES

33 40 00 STORM DRAINAGE UTILITIES

33 46 16 SUBDRAINAGE SYSTEM

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

APPENDIX A – GEOTECHNICAL ENGINEERING REPORT

-- End of Project Table of Contents --

{Construct SGT Pad, Minot AFB, ND} {QJVF 14-0027}

DOCUMENT 00 01 15

LIST OF DRAWINGS

PART 1 GENERAL

1.1 SUMMARY

This section lists the drawings for the project pursuant to contract clause "DFARS 252.236-7001, Contract Drawings, Maps and Specifications."

1.2 CONTRACT DRAWINGS

Contract drawings are as follows:

GENERAL

G-001 COVER SHEET

G-002 INDEX OF DRAWINGS, LEGENDS AND GENERAL NOTES

G-003 ABBREVIATIONS

CIVIL

V-001 TOPOGRAPHIC SURVEY

C-101 GRADING PLAN

C-102 PAVING PLAN

C-103 COORDINATION PLAN

C-104 JOINTING PLAN

C-105 CIVIL DETAILS

ELECTRICAL

EG101 GENERAL ELECTRICAL NOTES AND SYMBOLS LEGEND

ES101 ELECTRICAL SITE PLAN

E-501 ELECTRICAL DETAILS

E-502 ELECTRICAL DETAILS

E-601 POWER RISER DIAGRAMS & ELECTRICAL SCHEDULES

-- End of Document --

DOCUMENT 00 01 15 Page 1

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The purpose of this project is to design a Safeguard Transport (SGT) parking pad, exterior electrical lighting for the parking pad, sub-grade, storm water drainage system, lightning protection system, curbside power supply, vehicle plug-in stations, a road to connect the parking pad to Building 1119, and other incidental features to meet user parking needs and force protection requirements.

The SGT Pad will be located within the Weapon Storage Area (WSA) and will provide a parking place that meets all Air Force Quantity Distance (QD) arcs and Air Force Instructions requirements. Currently the SGTs are parked on an existing road in the WSA, blocking off traffic to the entire road. Support vehicles are parked in random locations within the WSA which requires some of the vehicle armory items to be off-loaded and stored in separate locations in order to satisfy QD requirements. The construction of the SGT Pad and road will eliminate waivers that are in place for the current parking situation.

When assets are moved from the storage igloos to Building 1119, traffic at the ECP is stopped during the transit. The construction of a road connecting the parking pad will provide a more direct route from the igloos to B1119, eliminating the need to stop traffic.

1.1.2 Location

The work is located in the Weapons Storage Area (WSA), as shown on the cover sheet of the Contract Drawings.

1.2 WORK RESCHEDULING

Allow for a maximum of 15 calendar days in the construction schedule where construction activity is prohibited due to military operations.

Government will provide 24 hour notification each time the restrictions are invoked.

Normal duty hours for work are from 7:30 a.m. to 4:00 p.m., Monday through Friday. Requests for additional work requires written approval from the Contracting Officer 7 days in advance of the proposed work period.

1.3 OCCUPANCY OF PREMISES

The Weapons Storage area must be completely accessible throughout construction activities.

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 roads and parking areas.

SECTION 01 11 00 Page 1

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 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.5 ON-SITE PERMITS

1.5.1 Utility Outage Requests and Utility Connection Requests

Schedule work to minimize outages. For utility outages and connections required during the execution of work that affect existing systems, schedule outside the regular working hours or on weekends, as approved by the Contracting Officer. Schedule utility outages and connections to minimize disruptions to the Government. No additional payment will be provided for utility outages and connections required to be performed outside the regular work hours.

Submit requests for utility outages and connections in writing to the Contracting Officer for approval at least 7 calendar days in advance of the time required. In each request, state the system involved, area involved, approximate duration of outage, and the nature of work involved.

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 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 constructed 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 48 hours prior to starting excavation work.

1.7 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged remain the

SECTION 01 11 00 Page 2 property of the Government. Segregate, itemize, deliver and off-load the salvaged property at the Government designated storage area located within 3 miles of the construction site.

Provide a salvage plan, listing material and equipment to be salvaged, and their storage location. Maintain property control records for material or 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

Not used.

-- End of Section --

SECTION 01 11 00 Page 3

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.1 SUBMITTALS

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

Preconstruction Submittals

List of Contact Personnel

Personnel List

Vehicle List

1.2 SPECIAL SCHEDULING REQUIREMENTS

a. Permission to interrupt any Activity roads, railroads, or utility service must be requested in writing a minimum of 7 calendar days prior to the desired date of interruption.

b. The work under this contract requires special attention to the scheduling conduct of the work in connection with existing operations.

Identify on the construction schedule each factor which constitutes a potential interuption to operations.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.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.3.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.3.1.2 Identification Badges and Installation Access

Application for and use of badges will be as directed. Furnish a completed EMPLOYMENT ELIGIBILITY VERIFICATION (DHS FORM I-9) form for all personnel requesting badges. This form is available at http://www.uscis.gov/portal/site/uscis by searching or selecting Employment

SECTION 01 14 00 Page 1

Verification (Form I-9) [____ ]. Immediately report instances of lost or stolen badges to the Contracting Officer.

1.3.1.3 Employee List

The Contractor must provide to the Contracting officer, in writing, the names of two designated representatives authorized to request personnel and vehicle passes for employees and subcontractor's employees prior to commencement of work under this contract.

1.3.1.4 Personnel Entry Approval

Failure to obtain entry approval will not affect the contract price or time of completion.

1.3.1.5 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.3.5 Working Hours

Regular working hours must consist of an 8 1/2 hour period, between 7:30 a.m. and 4:00 p.m., Monday through Friday, excluding Government holidays.

1.3.6 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 7 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 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.3.7 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. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, and compressed air, are considered utility cutovers pursuant to the paragraph WORK

OUTSIDE REGULAR HOURS.

1.4 SECURITY REQUIREMENTS

SECTION 01 14 00 Page 2

Contract Clause "FAR 52.204-2, Security Requirements and Alternate II," "FAC 5252.236-9301, Special Working Conditions and Entry to Work Area," and the Minot Air Force Base Integrated Defense Plan 31 apply.

1.4.11 Personnel List

Submit for approval, at least 15 days prior to the desired date of entry, an original alphabetical list of personnel who require entry into Government property to perform work on the project. Furnish for each person:

a. Name

b. Date and place of birth

c. Citizenship

d. Home address

e. Social security number

f. Current pass expiration date

g. Naturalization number

The request for personnel passes must be accompanied with the following certification:

"I hereby certify that all personnel on this list are either born U.S.

citizens, naturalized U.S. citizens with the naturalization number shown."

Signature/Firm Name

1.4.11.1 Personnel EAL Submital

When work is in a secure location, a second personnel list in the form of an EAL will be required to be submitted by the contractor. The EAL Format will be provided by the government.

1.4.11.2 Citizenship Requirements

Aliens will not be admitted to the work site.

1.4.11.3 Documents Acceptable for Proof of Citizenship

a. Birth registration card

b. Certificate of live birth, birth certificate

c. Certificate of Naturalization

d. Certificate of registration

e. DD-214 (Must Cite Birthplace)

SECTION 01 14 00 Page 3

f. DD Form 4 (Contract for Enlistment and Must Cite Birthplace)

g. DD 1966 (Application for Enlistment)

h. Military discharge papers (must cite birthplace)

i. Delayed birth certificate

j. Hawaii certificate of foreign birth

k. Hospital birth certificate

l. Marriage license certificate

m. Merchant marine certificate

n. Military officer ID card

o. Notification of birth registration

p. USA passport

1.4.12 Vehicle List

Submit an original list of vehicles to be utilized at the work site with the following information for each vehicle:

a. Make

b. Year

c. Model

d. License number

e. Registered owner

1.4.12.1 Vehicle EAL Submittal

When work is in a secure location, a second vehicle list in the form of an EAL will be required to be submitted by the contractor. The EAL Format will be provided by the government.

1.4.13 Passes

Submit request for personnel and vehicle passes together. Include the Certificate of Insurance for Contractor and Subcontractor(s) and the Statement of Acknowledgement Form SF 1413 with the submittal. Passes will normally be issued within 21 days.

1.4.13.1 Control

Maintain strict accountability over passes. Immediately report to the

SECTION 01 14 00 Page 4 source of issue, passes missing or lost and the circumstances. If the Contractor has another active contract or one commencing immediately, employees' names may be transferred from one contract to the other. Final payment will not be effected until employees are transferred to another contract or the records are cleared. Furnish a signed letter, countersigned by the source of issue, stating that passes have been turned in.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

-- End of Section --

SECTION 01 14 00 Page 5

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

Preconstruction Submittals

Preliminary Project Schedule;

Initial Project Schedule;

Periodic Schedule Update;

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this project with scheduling software that meets the requirements of this specification. Representative must have a comprehensive knowledge of CPM scheduling principles and application.

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.

{Construct SGT Pad, Minot AFB, ND} {QJVF 14-0027}

SECTION 01 32 01. Page 100 10

1515678723C Cross-Out

2.1.1 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

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 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.2.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. A Gantt chart is sufficent for the level of detail necessary for the project schedule.

3.2.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.2.3 Design and Permit Activities

Include design and permit activities with the necessary conferences and follow-up actions and design package submission dates. Include the design schedule in the project schedule, showing the sequence of events involved in carrying out the project design tasks within the specific contract period. Provide at a detailed level of scheduling sufficient to identify all major design tasks, including those that control the flow of work.

Also include review and correction periods associated with each item.

3.2.4 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, {Construct SGT Pad, Minot AFB, ND} {QJVF 14-0027}

Page 2SECTION 01 32 01.00 10

1515678723C Cross-Out equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.2.5 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 DD1354 data and installed equipment lists.

g. Submission and approval of testing and air balance (TAB).

h. Submission of TAB specialist design review report.

i. Submission and approval of fire protection specialist.

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

k. Air and water balancing.

l. Building commissioning - Functional Performance Testing.

m. Controls testing plan submission.

n. Controls testing.

o. Performance Verification testing.

p. Other systems testing, if required.

q. Contractor's pre-final inspection.

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

s. Government's pre-final inspection.

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

Page 3SECTION 01 32 01.00 10

u. Final inspection.

3.2.6 Government Activities

Show Government and other agency activities that could impact progress.

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

3.2.7 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.2.7.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.2.7.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.2.7.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 phase is later than the specified interim completion date.

3.2.7.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.2.7.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.

Page 4SECTION 01 32 01.00 10

3.2.8 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.2.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.

Predecessor open ended logic may be allowed in a time impact analyses upon the Contracting Officer's approval.

3.2.10 Default Progress Data Disallowed

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

3.2.11 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer. Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.2.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

3.2.13 Original Durations

Page 5SECTION 01 32 01.00 10

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

3.2.14 Leads, Lags, and Start to Finish Relationships

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb float, or to replace proper schedule logic.

a. Leads (negative lags) are prohibited.

b. Start to Finish (SF) relationships are prohibited.

3.2.15 Retained Logic

Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity(s) starts and the predecessor activity(s) has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed.

3.2.16 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.2.17 Remaining Duration

Update the remaining duration for each activity based on the number of estimated work days it will take to complete the activity. Remaining duration may not mathematically correlate with percentage found under paragraph entitled Percent Complete.

3.2.18 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.2.19 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it

Page 6SECTION 01 32 01.00 10 responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.3 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.3.1 Preliminary Project Schedule Submission

Within 10 calendar days after the NTP is acknowledged submit the AF 3064 defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code

(FOW).

3.3.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 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.

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

Update the schedule to include detailed construction activities as the design progresses, but not later than the submission of the final un-reviewed design submission for each separate design package. The Contracting Officer may require submission of detailed schedule activities for any distinct construction that is started prior to submission of a final design submission if such activity is authorized.

Page 7SECTION 01 32 01.00 10

a. Update information including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete is subject to the approval of the Government at the meeting.

b. AS and AF dates must match the date(s) reported on the Contractor's Quality Control Report for an activity start or finish.

3.4 SUBMISSION REQUIREMENTS

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

3.4.1 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.4.1.1 Activity Report

List of all activities sorted according to activity number.

3.4.1.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

3.4.1.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.4.1.4 Schedule Log

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

3.4.2 Network Diagram

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

3.4.2.1 Continuous Flow

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

Page 8SECTION 01 32 01.00 10

3.4.2.2 Project Milestone Dates

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

3.4.2.3 Critical Path

Show all activities on the critical path. The critical path is defined as the longest path.

3.5 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.6 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.6.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 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.6.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer based on industry standard AACE 52R-06. Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis. If Contracting Officer determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. Unless approved by the Contracting Officer, no other changes may be incorporated into the schedule being used to justify the time impact.

3.6.3 Forensic Schedule Analysis (Retrospective Analysis)

Prepare an analysis for approval by the Contracting Officer based on industry standard AACE 29R-03.

Page 9SECTION 01 32 01.00 10

3.6.4 Fragmentary Network (Fragnet)

Prepare a proposed fragnet for time impact analysis consisting of a sequence of new activities that are proposed to be added to the project schedule to demonstrate the influence of the delay or impact to the project's contractual dates. Clearly show how the proposed fragnet is to be tied into the project schedule including all predecessors and successors to the fragnet activities. The proposed fragnet must be approved by the Contracting Officer prior to incorporation into the project schedule.

3.6.5 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.7 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.7.1 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.7.2 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.7.3 Recovery Schedule

Should the Contracting Officer find it necessary, submit a recovery

Page 10SECTION 01 32 01.00 10 schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.

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

-- End of Section --

Page 11SECTION 01 32 01.00 10

SECTION 01 33 00

SUBMITTAL PROCEDURES

PART 1 GENERAL

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.

Data type submittals shall be provided in electronic format either on disk or posted on a cloud service followed by an email confirmation for retrival by the government.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions

Submittals requirements are specified in the technical sections.

Submittals are identified by submittal description titles as follows:

Preconstruction Submittals

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 1

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

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.

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.

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 which the work can be judged.

Color samples from the manufacturer's standard line (or custom color samples if specified) to be used in selecting or approving colors for the project.

Field samples and mock-ups constructed on the project site establish standards by which the ensuring work can be judged. Includes

SECTION 01 33 00 Page 2 assemblies or portions of assemblies which are to be incorporated into the project and those which will be removed at conclusion of the work.

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.

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.

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.

Manufacturer's Instructions

Preprinted material describing installation of a product, system or material, including special notices and (MSDS)concerning impedances, hazards and safety precautions.

SECTION 01 33 00 Page 3

Manufacturer's Field Reports

Documentation of the testing and verification actions taken by manufacturer's representative at the job site, in the vicinity of the job site, or on a sample taken from the job site, on a portion of the work, during or after installation, to confirm compliance with manufacturer's standards or instructions. The documentation must be signed by an authorized official of a testing laboratory or agency and state the test results; and indicate whether the material, product, or system has passed or failed the test.

Factory test reports.

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.

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.2.2 Approving Authority

Office or designated person authorized to approve submittal.

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

Submit the following in accordance with this section.

Preconstruction Submittals

Submittal Register

SECTION 01 33 00 Page 4

1.4 SUBMITTAL CLASSIFICATION

Submittals are classified as follows:

1.4.1 Government Approved

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

1.5 FORWARDING SUBMITTALS REQUIRING GOVERNMENT APPROVAL

1.5.1 Submittals Required from the Contractor

As soon as practicable after award of contract, and before procurement of fabrication, forward to the government, submittals required in the technical sections of this specification, including shop drawings, product data and samples. Forward electronic transmittal form for all submittals to the contracting officer.

1.5.1.1 O&M Data

The government will review and approve O&M Data to verify the submittals comply with the contract requirements; submit data specified for a given item within 30 calendar days after the item is…