Central Base Drainage XHZG201601826 Final specs.pdf

PROJECT SPECIFICATIONS

Oklahoma Air National Guard Central Base Drainage Repair Project No. : XHZG201601826

Tulsa, OK

B2 Final Submittal May 15, 2018

ARCHITECT / ENGINEER

Cyntergy AEC 810 South Cincinnati Avenue

Second Floor Tulsa, Oklahoma 74119

918 877 6000

CENTRAL BASE DRAINAGE REPAIR

XHZG201601826

Table of Contents

TULSA OKANG B2 Final Submittal 5/15/18

PROJECT TABLE OF CONTENTS

DIVISION 00 – PROCUREMENT AND CONTRACTING REQUIREMENTS

Notice of Proposed Task Order Proposal Form

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 20 00.00 20 PRICE AND PAYMENT PROCEDURES

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 32 16.00 20 CONSTRUCTION PROGRESS DOCUMENTATION

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 35 40.00 20 ENVIRONMENTAL MANAGEMENT

01 45 00.00 40 QUALITY CONTROL

01 50 00 TEMPORARY CONSTRUCTION FACILITIES

01 57 19.00 20 TEMPORARY ENVIRONMENTAL CONTROLS

01 57 20.00 10 ENVIRONMENTAL PROTECTION

01 57 23 TEMPORARY STORM WATER POLLUTION CONTROL

01 74 19 CONSTRUCTION WASTE MANAGEMENT

01 78.00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 – EXISTING CONDITIONS

02 41 00 DEMOLITION AND DECONSTRUCTION

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 23 00.00 20 EXCAVATION AND FILL

DIVISION 32 – EXTERIOR IMPROVEMENTS

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTER

32 92 23 SODDING

END OF TABLE OF CONTENTS

Type B2 Final Section 00 00 07 05/15/2018

SECTION 00 01 00 - SEALS PAGE

CIVIL ENGINEER OF RECORD

W. Charles Mitchell, PE

Cyntergy

810 S. Cincinnati Ave.

Tulsa, Oklahoma 74119

Civil Engineer Date of Record

END OF DOCUMENT

011100 - 1/2

TULSA OKANG B2 Final Submittal 5/15/18

SECTION 01 11 00

SUMMARY OF WORK

08/11

PART 1

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes the selective demolition of existing sidewalk areas and the construction of new sidewalks and incidental related work as indicated on the documents.

1.1.2 Locations

The work shall be located as indicated. The exact location will be confirmed by the Contracting Officer.

1.2 EXISTING WORK

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

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

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

c. Obtain digging permits prior to start of excavation.

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

1.3 SALVAGE MATERIAL AND EQUIPMENT

Items designated by the Contracting Officer to be salvaged shall remain the property of the Government.

The salvaged property shall be segregated, itemized, delivered, and off-loaded at the Government designated storage area located within 1 miles of the construction site.

Contractor shall maintain property control records for material or equipment designated as salvage. Contractor's system of property control may be used if approved by the Contracting Officer. Contractor shall be responsible for storage and protection of salvaged materials and equipment until disposition by the Contracting Officer.

011100 - 1/2

1.4 BORING LOGS

N/A.

1.5 SUBSURFACE DATA

N/A.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

-- End of Section --

011400 - 1/2

SECTION 01 14 00

WORK RESTRICTIONS

07/07

PART 1 GENERAL

1.1 CONTRACTOR ACCESS AND USE OF PREMISES

1.1.1 Activity Regulations

1.1.1.1 Subcontractors and Personnel Contacts

Furnish 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.1.1.2 Subcontractors and Personnel Contacts

1.1.1.3 Identification Badges

Identification badges, if required, will be furnished without charge.

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/files/form/I-9_IFR_02-02-09.pdf. Immediately report instances of lost or stolen badges to the Contracting Officer.

1.1.1.4 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installations under the cognizance of OKANG except in designated smoking areas. This applies to buildings and site. 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.1.2 Working Hours

Regular working hours shall consist of an 10 hour period beginning at 7:30

AM and running through 5:30PM, Monday through Friday, excluding Government holidays.

1.1.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress

011400 - 2/2

1.1.4 Occupied Buildings

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

Contracting Officer.

1.1.5 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in the paragraph "Work Outside Regular Hours."

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

c. Interruption to electric service shall be considered utility cutovers pursuant to the paragraph entitled "Work Outside Regular

Hours." 1/2

1.2 SECURITY REQUIREMENTS

Contractor shall provide security personnel during working hours, at gate onto site from batch plant. The Government will provide a portable radio for two way communication with Base Security.

Not Used

0120000020 - 1/3

SECTION 01 20 00.00 20

PRICE AND PAYMENT PROCEDURES

02/10

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)

EP-1110-1-8 (2009) Construction Equipment Ownership and

Operating Expense Schedule, Volumes 1 - 12

(Regions I - XII)

1.2 SUBMITTALS

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

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

SD-01 Preconstruction Submittals

Schedule of values; G

1.3 SCHEDULE OF VALUES

1.3.1 Data Required

Within 15 calendar days of notice of award, prepare and deliver to the

Contracting Officer a schedule of values (construction contract) on the forms furnished by the Government. Provide a detailed breakdown of the contract price, giving quantities for each of the various kinds of work, unit prices, and extended prices.

1.3.2 Real Property Assets

The following real property assets apply to work covered by this specification. These assets are broken out by construction categories and are typically found in the DD Form 1391, and the "Category Codes for

Military Real Property", which is service specific and available from the

Contracting Officer. These assets must also be identified in coordination with the Real Property Accounting Officer. (Contact the Contracting Officer for coordination.)

Divide detailed asset breakdown into each construction category, sufficient for completion of the DD Form 1354, Transfer and Acceptance of Military Real

Property. Subcontractors who may be involved in work under more than one of these categories shall be advised of this requirement in order to furnish file://///rams/Projects/OKANG/B403%20Fire%20Station%20ADAL/Specifications/B3%20Final%20Specs/01%2033%2000.DOC

0120000020 - 2/3

TULSA OKANG B2 Final Submittal 5/15/18 such data without delay. Assets and construction categories above may be modified by the Contracting Officer as necessary during course of work.

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

DD Form 1354. Coordinate with section 01 33 10.05 20, DESIGN SUBMITTAL

PROCEDURES paragraph "DD Form 1354".

1.3.3 Schedule Instructions

Payments will not be made until the Schedule of Prices has been submitted to and accepted by the Contracting Officer. Identify the cost for site work, and include incidental work to the 5 foot line. Identify costs for the building(s), and include work out to the 5 foot line. Work out to the 5 foot line shall include construction encompassed within a theoretical line 5 feet from the face of exterior walls and shall include attendant construction, such as cooling towers, placed beyond the 5 foot line.

1.4 CONTRACT MODIFICATIONS

In conjunction with the Contract Clause "DFARS 252.236-7000, Modification

Proposals-Price Breakdown," and where actual ownership and operating costs of construction equipment cannot be determined from Contractor accounting records, equipment use rates shall be based upon the applicable provisions of the EP-1110-1-8.

1.5 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.5.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/or 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.5.2 Payment for Materials Offsite

Payments may be made to the Contractor for materials stored off construction sites under the following conditions:

0120000020 - 3/3

TULSA OKANG B2 Final Submittal 5/15/18

a. Conditions described in the paragraph entitled "Payments to the

Contractor";

b. Material located and stored in the Continental United States;

c. Materials adequately insured and protected from theft and exposure;

d. Materials not susceptible to deterioration or physical damage in storage or in transit to the job site are acceptable for progress payments. Items such as non-magnetic steel, aluminum, non-magnetic aggregate, machinery, pre-cast/pre-stressed concrete products, and plastic lumber ( e.g., fender piles and curbs) are acceptable for progress payments;

e. Conditions specified in FAR 52.232-5(b) PAYMENTS UNDER FIXED PRICE

CONSTRUCTION CONTRACTS; and

f. Payment requests for off-site materials include consent of surety.

013000 - 1/3

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

1.1 SUBMITTALS

used, a designation following the "G" designation identifies the office that will review the submittal for the Government. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

List of contact personnel; G, Progress and completion pictures; G,

1.2 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color 4 megapixel 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 a view location sketch indicating points of view. Submit with the monthly invoice two sets of digital photographs each set on a separate CD-R, cumulative of all photos to date. Indicate photographs demonstrating environmental procedures. Photographs for each month shall be in a separate monthly directory and each file shall be named to indicate its location on the view location sketch. The view location sketch shall also be provided on the CD as digital file. All file names shall include a date designator. Cross reference submittals in the appropriate daily report.

Photographs shall be provided for unrestricted use by the Government.

1.3 MINIMUM INSURANCE REQUIREMENTS

Procure and maintain during the entire period of performance under this contract the following minimum insurance coverage:

a. Comprehensive general liability: $500,000 per occurrence

b. Automobile liability: $200,000 per person, $500,000 per occurrence for bodily injury, $20,000 per occurrence for property damage

c. Workmen's compensation as required by Federal and State workers' compensation and occupational disease laws.

d. Employer's liability coverage of $100,000, except in States where workers compensation may not be written by private carriers, file://///rams/Projects/OKANG/B403%20Fire%20Station%20ADAL/Specifications/B3%20Final%20Specs/01%2033%2000.DOC

013000 - 2/3

e. Others as required by State of Oklahoma.

1.4 CONTRACTOR PERSONNEL REQUIREMENTS

1.4.1 Subcontractors and Personnel

1.4.2 Identification Badges

Identification badges, if required, will be furnished without charge.

Application for and use of badges will be as directed. Immediately report instances of lost or stolen badges to the Contracting Officer.

1.4.3 Contractor Personnel Requirements

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

1.5 SUPERVISION

Have at least one qualified supervisor capable of reading, writing, and conversing fluently in the English language on the job site during working hours. In addition, if a Quality Control (QC) representative is required on the contract, then that individual shall also have fluent English communication skills.

1.6 PRECONSTRUCTION CONFERENCE

After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule prices, 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 shall also attend.

1.7 AVAILABILITY OF CADD DRAWING FILES

CAD drawings will be available to the contractor upon request.

1.8 ELECTRONIC MAIL (E-MAIL) ADDRESS

The Contractor shall establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments in Microsoft, Adobe Acrobat, and other similar formats. Within 10 days after contract award, the Contractor shall provide the Contracting Officer a single (only one) e-mail address for electronic communications from the

Contracting Officer related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the

Contractor of base access conditions when emergency conditions warrant, such as hurricanes, terrorist threats, etc. Multiple email addresses will not allowed.

013000 - 3/3

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). The Contractor shall promptly notify the Contracting

Officer, in writing, of any changes to this email address.

0132010010 - 1/14

SECTION 01 32 01.00 10

PROJECT SCHEDULE

08/08

ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

Project Schedule; G

1.3 QUALITY ASSURANCE

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling having previously developed, created, and maintained at least 2 electronic schedules for projects similar in nature and complexity to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the design and construction sequences, is required. The scheduling of construction is the responsibility of the Contractor. Contractor management file://///rams/Projects/OKANG/B403%20Fire%20Station%20ADAL/Specifications/B3%20Final%20Specs/01%2033%2000.DOC

0132010010 - 2/14

TULSA OKANG B2 Final Submittal 5/15/18 personnel shall actively participate in its development. Subcontractors and suppliers working on the project shall also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool.

3.1.1 Approved Project Schedule

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

3.1.2 Schedule Status Reports

Provide a Schedule Status Report on at least a monthly basis. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor shall take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting

Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the

Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.3 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting

Officer shall be grounds for a determination, by the Contracting Officer, that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract. Upon making this determination, the Contracting Officer may terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.

3.2 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project

Schedule shall be capable of meeting all requirements of this specification.

Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule.

3.2.1 Critical Path Method

Use the Critical Path Method (CPM) of network calculation to generate the

Project Schedule. Prepare the Project Schedule using the Precedence Diagram

Method (PDM).

3.2.2 Level of Detail Required

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

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

0132010010 - 3/14

3.2.2.1 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Less than 2 percent of all non-procurement activities shall have Original Durations (OD) greater than 20 work days or 30 calendar days. Procurement activities are defined herein.

3.2.2.2 Procurement Activities

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

3.2.2.3 Mandatory Tasks

The following tasks must be included and properly scheduled:

a. Submission, review and acceptance of design packages.

b. Submission of electrical systems layout drawings.

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

e. Submission and approval of 1354 data and installed equipment lists.

f. Contractor's pre-final inspection.

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

h. Government's pre-final inspection.

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

j. Final inspection.

3.2.2.4 Government Activities

Show Government and other agency activities that could impact progress.

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

(NTP) for phasing requirements.

3.2.2.5 Activity Responsibility Coding (RESP)

Assign responsibility Code for all activities to the Prime Contractor, Subcontractor or Government agency responsible for performing the activity.

Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements. Code all activities

0132010010 - 4/14

TULSA OKANG B2 Final Submittal 5/15/18 not coded with a Government Responsibility Code to the Prime Contractor or

Subcontractor responsible to perform the work. Activities shall not have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for

USACE). Unacceptable code values are abbreviations of the names of subcontractors.

3.2.2.6 Activity Work Area Coding

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew, from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings. Activities shall not have more than one Work Area Code. Not all activities are required to be Work Area coded. A lack of Work Area coding will indicate the activity is not resource or space constrained.

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

(MODF)

Assign Activity code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by the

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

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

Responsibility Coded to the Government unless approved. An activity shall not have more than one Contract Changes/REA Code.

3.2.2.8 Contract Line Item (CLIN) Coding (BIDI)

Code all activities to the CLIN on the Contract Line Item Schedule to which the activity belongs. An activity shall not contain more than one CLIN Item

Code. CLIN Item code all activities, even when an activity is not cost loaded.

3.2.2.9 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities based upon the phase of work in which the activity occurs. Code fast track construction phases proposed by the Contractor to allow filtering and organizing the schedule by fast track design and construction packages. If the contract specifies construction phasing with separately defined performance periods, identify a

Construction Phase Code to allow filtering and organizing the schedule

0132010010 - 5/14

TULSA OKANG B2 Final Submittal 5/15/18 accordingly. Each activity shall be identified with a single project phase and have only one Phase of Work code.

3.2.2.10 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: construction submittal approvals, Acceptance, Procurement, Fabrication, Delivery, Weather Sensitive Installation, Non-

Weather Sensitive Installation, Start-Up, Test and Turnover. Assign a

Category of Work Code to each activity. Each activity shall have only one

Category of Work Code.

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

Assign a Definable Feature of Work Code to appropriate activities based on the definable feature of work to which the activity belongs. Definable

Feature of Work is defined in Specification Section 01 45 00.00 40 QUALITY

CONTROL. An activity shall not have more than one Definable Feature of Work

Code. Not all activities are required to be Definable Feature of Work

Coded.

3.2.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is received by the

Contractor. Schedule activities on a calendar to which the activity logically belongs. Activities may be assigned to a 7 day calendar when the contract assigns calendar day durations for the activity such as a

Government Acceptance activity. If the Contractor intends to perform physical work less than seven days per week, schedule the associated activities on a calendar with non-work periods identified including weekends and holidays. Assign the Category of Work Code - Weather Sensitive

Installation to those activities that are weather sensitive. Original durations must account for anticipated normal adverse weather. The

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

3.2.3.1 Project Start Date

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

3.2.3.2 Schedule Constraints and Open Ended Logic

Constrain completion of the last activity in the schedule by the contract completion date. Schedule calculations shall result in a negative float when the calculated early finish date of the last activity is later than the contract completion date. Include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall file://///rams/Projects/OKANG/B403%20Fire%20Station%20ADAL/Specifications/B3%20Final%20Specs/01%2045%2000.00%2040.DOC

0132010010 - 6/14

TULSA OKANG B2 Final Submittal 5/15/18 have an "LF" constraint date equal to the contract completion date for the project, and with a zero day duration or by using the "project must finish by" date in the scheduling software. The schedule shall have no constrained dates other than those specified in the contract. The use of artificial float constraints such as "zero fee float" or "zero total float" are typically prohibited. There shall only be 2 open ended activities: Start

Project (or NTP) with no predecessor logic and End Project with no successor logic.

3.2.3.3 Early Project Completion

In the event the Preliminary or Initial project schedule calculates an early completion date of the last activity prior to the contract completion date, the Contractor shall identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the

Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.2.4 Interim Completion Dates

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

3.2.4.1 Start Phase

Include as the first activity for a project phase an activity called "Start

Phase X" where "X" refers to the phase of work. The "Start Phase X" activity shall have an "ES" constraint date equal to the date on which the

NTP was acknowledged, and a zero day duration.

3.2.4.2 End Phase

Include as the last activity for a project phase an activity called "End

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

3.2.4.3 Phase "X" Hammock

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

3.2.5 Default Progress Data Disallowed

Do not automatically update Actual Start and Finish dates with default mechanisms that may be included in the scheduling software. Activity Actual

Start (AS) and Actual Finish (AF) dates assigned during the updating process shall match those dates provided from Contractor Quality Control Reports.

Failure of the Contractor to document the AS and AF dates on the Daily

Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control

0132010010 - 7/14

TULSA OKANG B2 Final Submittal 5/15/18 reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's updated schedule and the inability of the

Contracting Officer to evaluate Contractor progress for payment purposes.

3.2.6 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer. Propose logic corrections to eliminate all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than two update cycles by logic revision, as approved by the Contracting Officer.

3.2.7 Negative Lags and Start to Finish Relationships

Lag durations contained in the project schedule shall not have a negative value. Do not use Start to Finish (SF) relationships.

3.2.8 Calculation Mode

Schedule calculations shall retain the logic between predecessors and successors even when the successor activity starts and the predecessor activity has not finished. Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") will not be allowed.

3.2.9 Milestones

The schedule must include milestone activities for each significant project event including but not limited to: milestone activities for each fast track design package released for construction; design complete;

foundation/substructure construction complete; superstructure construction complete; building dry-in or enclosure complete to allow the initiation of finish activities; permanent power complete; and building systems commissioning complete.

3.3 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD, reports, and network diagrams required for each submission are contained in paragraph

SUBMISSION REQUIREMENTS.

3.3.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 15 calendar days after the NTP is acknowledged. The approved Preliminary Project

Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. Detail it for the first 90 calendar days. It may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as previously specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required Plan and Program preparations, submissions and

0132010010 - 8/14

TULSA OKANG B2 Final Submittal 5/15/18 approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, the planned submissions of all early design packages, permitting activities, design review conference activities and other non-construction activities intended to occur within the first 90 calendar days. Schedule any construction activities planned for the first 90 calendar days after NTP.

Constrain planned construction activities by Government acceptance of the associated design package(s) and all other specified Program and Plan approvals. Activity code any activities that are summary in nature after the first 90 calendar days with Responsibility Code (RESP) and Feature of

Work code (FOW1, FOW2, FOW3).

3.3.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer.

3.3.3 Design Package Schedule Submission

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

3.3.4 Periodic Schedule Updates

Based on the result of the meeting, specified in PERIODIC SCHEDULE UPDATE

MEETINGS, submit periodic schedule updates. These submissions will enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgement of the Contracting Officer or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made.

3.3.5 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange

Format (SDEF) in ER 1-1-11, Appendix A. This exact structure is mandatory, even if some fields are not used. A template SDEF compatible schedule backup file (sdef.prx) is available on the QCS website: www.rmssupport.com.

The SDEF format is as follows:

Field Activity

Code Length Description

1 WRKP 3 Workers per Day

2 RESP 4 Responsible Party (e.g. GC, subcontractor, USACE)

3 AREA 4 Area of Work

4 MODF 6 Modification or REA number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of Work

7 CATW 1 Category of Work

8 FOW1 10 Feature of Work (used up to 10 characters in length)

0132010010 - 9/14

TULSA OKANG B2 Final Submittal 5/15/18

9 FOW2 10 Feature of Work (used up to 20 characters in length)

10 FOW3 10 Feature of Work (used up to 30 characters in length)

3.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 Data CD's

Provide two sets of data CD's containing the project schedule in the backup format. Each CD shall also contain all previous update backup files. File medium shall be CD. Label each CD indicating the type of schedule

(Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule shall have a unique file name as determined by the

Contractor.

3.4.2 Narrative Report

Provide a Narrative Report with the Preliminary, Initial, and each Periodic

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

3.4.3 Approved Changes Verification

Include only those project schedule changes in the schedule submission that have been previously approved by the Contracting Officer. The Narrative

Report shall specifically reference, on an activity by activity basis, all changes made since the previous period and relate each change to documented, approved schedule changes.

3.4.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report shall be as directed by the Contracting Officer. Typically reports shall contain:

Activity Numbers, Activity Description, Original Duration, Remaining

Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish

Date, Total Float, Actual Start Date, Actual Finish Date, and Percent

Complete. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission.

3.4.4.1 Activity Report

A list of all activities sorted according to activity number.

0132010010 - 10/14

3.4.4.2 Logic Report

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

3.4.4.3 Total Float Report

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

3.4.4.4 Earnings Report by CLIN

A compilation of the Contractor's Total Earnings on the project from the NTP to the data date. This report shall reflect the earnings of specific activities based on the agreements made in the schedule update meeting defined herein. Provided that the Contractor has furnished a complete schedule update, this report shall serve as the basis of determining progress payments. Group activities by CLIN item number and sort by activity number. This report shall: sum all activities coded to a particular CLIN and provide a CLIN item percent earned value; and complete and sum CLIN items to provide a total project percent complete. The printed report shall contain, for each activity: the Activity Number, Activity

Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), and Earnings to Date.

3.5 PERIODIC SCHEDULE UPDATE MEETINGS

Conduct periodic schedule update meetings for the purposes of reviewing the

Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. Meetings shall occur at least monthly within five days of the proposed schedule data date and after the Contractor has updated the schedule with Government concurrence respecting actual start dates, actual finish dates, remaining durations and percent complete for each activity it intend to status. Provide a computer with the scheduling software loaded and a projector during the meeting which allows all meeting participants to view the proposed schedule update during the meeting. The meeting and resultant approvable schedule update shall be a condition precedent to a formal submission of the update as described in SUBMISSION REQUIREMENTS and to the submission of an imvoice for payment. The meeting will be a working interactive exchange which will allow the Government and the Contractor the opportunity to review the updated schedule on a real time and interactive basis. The Contractor's authorized scheduling representative will organize, sort, filter and schedule the update as requested by the Government. The meeting will last no longer than 8 hours. A rough draft of the proposed activity logic corrections and narrative report shall be provided to the

Government 48 hours in advance of the meeting. The Contractor's Project

Manager and Authorized Scheduler shall attend the meeting with the

Authorized Representative of the Contracting Officer.

3.5.1 Update Submission Following Progress Meeting

Submit a complete update of the project schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION

REQUIREMENTS not later than 4 working days after the periodic schedule

0132010010 - 11/14

TULSA OKANG B2 Final Submittal 5/15/18 update meeting, reflecting only those changes made during the previous update meeting.

3.5.2 Status of Activities

Update information, including Actual Start Dates (AS), Actual Finish Dates

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

3.5.2.1 Start and Finish Dates

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

3.5.2.2 Remaining Duration

Update the estimated RD for all incomplete activities independent of Percent

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

3.5.2.3 Percent Complete

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

Government pre-final inspection activity(ies) not less than 1 percent of the total contract value, which activity(ies) may be declared 100 percent complete upon completion and correction of all punch list work identified during Government pre-final inspection(s).

3.5.2.4 Logic Changes

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

0132010010 - 12/14

3.5.2.5 Other Changes

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

3.6 REQUESTS FOR TIME EXTENSIONS

In the event the Contractor believes it is entitled to an extension of the contract performance period, completion date, or any interim milestone date, furnish the following for a determination by the Contracting Officer:

justification, project schedule data, and supporting evidence as the

Contracting Officer may deem necessary. Submission of proof of excusable delay, based on revised activity logic, duration, and costs (updated to the specific date that the delay occurred) is a condition precedent to any approvals by the Government. In response to each Request For Proposal issued by the Government, the Contractor shall submit a schedule impact analysis demonstrating whether or not the change contemplated by the

Government impacts the critical path.

3.6.1 Justification of Delay

The project schedule shall clearly display that the Contractor has used, in full, all the float time available for the work involved with this request.

The Contracting Officer's determination as to the number of allowable days of contract extension shall be based upon the project schedule updates in effect for the time period in question, and other factual information.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay, will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.6.2 Submission Requirements

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

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

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

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

d. A sub-network of the affected area.

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

0132010010 - 13/14

3.6.3 Additional Submission Requirements

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

3.7 DIRECTED CHANGES

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

Officer within 2 weeks of receipt of the revisions. Regardless of the objections, the Contractor shall continue to update the schedule with the

Contracting Officer's revisions until a mutual agreement in the revisions is reached. If the Contractor fails to submit alternative revisions within 2 weeks of receipt of the Contracting Officer's proposed revisions, the

Contractor will be deemed to have concurred with the Contracting Officer's…