W912BV-15-D-0093-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04 EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

PXMG Plating Shop Renovation, B3001, Tinker Air Force Base, Oklahoma City, OK.

1. See page 2 for full details of changes. The due date is not extended and clarified as 6 Jan 2016, 2PM CST.

2. All potential offerors must acknowledge this amendment by completing blocks 15A, 15B and 15C of the this page.

Return the completed first page of this amendment with your proposal.

3. POC for this amendment is Pun Chittchang, punnie.chittchang@usace.army.mil, 918-669-7544.

4. ALL OTHER TERMS AND CONDITIONS REMAIN UNCHANGED BY THIS AMENDMENT

1. CONTRACT ID CODE PAGE OF PAGES

1 405

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY

16B. UNITED STATES OF AMERICA 15C. DATE SIGNED 15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer) (Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W912BV-15-R-0093

X 9B. DATED (SEE ITEM 11)

30 Oct 2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

24-Nov-2015

CODE

CONTRACTING DIV

USACE, TULSA 1645 S 101 E AVE

TULSA OK 74128-4609

W912BV 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODE CODE

EMAIL: TEL:

X

X 1

AMENDMENT 0002

W912BV-15-R-0093

PMXG PLATING SHOP RENOVATION, B3001

TINKER AIR FORCE BASE, OKLAHOMA

1. The revised/appendices/pages listed below are hereby added to or revised and made a part of the solicitation.

Revised or added/deleted information can be located in the specifications by searching for an asterisk and amendment number (i.e., *AM2).

00 11 00 PRICING SCHEDULE

01 32 01.00 10 PROJECT SCHEDULE

40 95 00 PROCESS CONTROL (Added attachments to end of the specification.)

2. Delete the following drawings and replace with the attached revised drawings of the same number.

LS-011 LIFE SAFETY PLAN - BASEMENT

LS-012 LIFE SAFETY PLAN – OPERATING FLOOR

LS-013 LIFE SAFETY PLAN - MEZZANINE

00 11 00 1 W912BV-15-R-0093

B3001 Plating Shop Renovation *AM2 REPLACED IN ITS ENTIRELY Tinker AFB, OK

PRICING SCHEDULE

CLIN Estimated Unit No. Description Quantity Unit Price Amount

BASE PROPOSAL

0001 Phase 1 and Phase 2 Plating Shop 1 Job XXX $_____________

0002 Phase 3 to Phase 6 Plating Shop 1 Job XXX $_____________

0003 Real Property 1 Job XXX $_____________

0004 As-Built Drawings 1 Job XXX $_____________

0005 O&M Manuals 1 Job XXX $_____________

TOTAL BASE PROPOSAL

(CLIN 0001 – 0005 INCLUSIVE) $___________________

OPTIONS

0006 Option 1 – Access Door from Area A to Area B (See note 8a) 1 Job XXX $_____________

0007 Option 2 – Roof Replacement (See note 8b) 1 Job XXX $_____________

0008 Option 3 – Wax/DeWax Renovation (See note 8c) 1 Job XXX $_____________

0009 Option 4 – Contaminated Soil Removal and Disposal (See note 8d) 20 CY $_____ $_____________

Sub-Total Options 1 – 4 (CLINS 0006 – 0009 Inclusive) $______________

TOTAL BASE PROPOSAL & OPTIONS

(CLINS 0001 – 0009 INCLUSIVE) $______________

Contract Duration (See Note 6): ______________

00 11 00 2 W912BV-15-R-0093

Tinker AFB, OK

PRICING SCHEDULE NOTES

1. The Offeror shall submit pricing data on the latest Pricing Schedule as published in the solicitation or the latest amendment thereto. In lieu of indicating additions/deductions to line items, all Offerors should state their revised prices for each item.

2. Offerors must insert a price on all numbered items of the Pricing Schedule. Failure to do so will disqualify the Offer.

3. All quantities are estimated except where the unit is given as Lump Sum (LS).

4. If a modification to a proposal is submitted and provides for a lump-sum adjustment to the total estimated cost, the application of the lump-sum adjustment to each unit price and/or lump-sum price, in the Pricing Schedule must be stated or, if it is not stated, the Offeror agrees that the lump-sum adjustment shall be applied on the prorated basis to every litem in the Bidding Schedule.

5. All the extensions of the unit prices shown will be subject to verification by the Government. In case of variation between the unit price and the extension, the unit price will be considered to be the offer.

6. The Offeror shall propose total contract duration in number of calendar days after the notice to Proceed (NTP) is received by the Contractor, whether via electronic means or hard copy, whichever is the earliest method of delivery. The total number of proposed calendar days for construction through completion, ready for turnover shall not exceed the days shown at, SCR: 5.211-10 COMMENCEMENT, PROSECUTION AND COMPLETION OF WORK. The proposed duration shall become the required contract duration. The Government may issue the NTP via e-mail or Facsimile (FAX) or by other means. Day number 1 is the day after the date of the receipt of the NTP.

7. BASE PROPOSAL ITEM DESCRIPTIONS

a. The following item costs shall be excluded from CLINS 0001 and 0002. Include the following item costs in CLIN 0003:

(1) Fire Alarm & Mass Notification Systems

(2) Lighting within the Basement (Below bottom of tank level)

(3) Sprinkler System

8. DESCRIPTION OF OPTIONS

a. Option 1: Access Door from Area A to Area B – this option shall provide double door access between Area A and Area B. This option will include adjustment/relocation of associated structural steel, mezzanine, equipment, and piping as required for installation of the doors. See drawings and specifications for further definition.

b. Option 2: Roof Replacement – this option shall provide a new roof system over the entire plating shop. This option shall include the removal of the existing roof, deck replacement as required, new expansion joints and all new flashing around all roof penetrations. This option includes all associated work required to replace the roofing system. See drawings and specifications for further definition.

c. Option 3: Wax/DeWax Renovation – this option shall include removal and installation of new equipment, replacement of hoists, and other items as shown within the drawings and specifications.

d. Option 4: Contaminated Soil Removal and Disposal: The work shall include removal and disposal of contaminated soil associated with construction on this project. Costs for this item shall include excavation, laboratory analytical testing, characterization, manifesting, confirmation sampling, 00 11 00 3 W912BV-15-R-0093

Tinker AFB, OK containerization, transportation, and off-site disposal. For estimating purposes any waste encountered would be classified as industrial waste and not Hazardous waste.

9. SITE WORK

a. All site work shall be included within CLIN Line Items 0001 and 0002.

10. COST BREAKDOWN INFORMATION

The Contractor shall provide cost or pricing data with this proposal as required by FAR Part 15. This information shall be provided in the format specified by Table 15-2 of FAR 15.408 or in the Contractor’s own format provided that format includes the appropriate information.

11. AWARD OF OPTIONAL PROPOSAL ITEMS

CLINS 0006 and 0008 (Options 1 and 3) may, at the option of the Government, be awarded at the time of contract award or may be exercised at any time from the date of contract award until 90 days after award.

CLINS 0007 (Options 2) may, at the option of the Government, be awarded at the time of contract award or may be exercised at any time from the date of contract award until 270 days after award.

CLINS 0009 (Option 4) may, at the discretion of the Government, be exercised at any time from the date of Contract Award to the completion of the contract.

Any and all optional line items may be exercised solely at the discretion of the Government.

SECTION 01 32 01.00 10 Page 1

Tinker AFB, OK B3001 Plating Shop Renovation

SECTION 01 32 01.00 10

PROJECT SCHEDULE

COAO FULL DBB 01 NOV 2015

PART 1 GENERAL

1.1 REFERENCES

The publications listed below form a part of this specification.

U.S. ARMY CORPS OF ENGINEERS (USACE)

ECB 2005-10 (2005) Scheduling Requirements for Testing of Mechanical Systems in Construction

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

1.1.1 Related Sections

Section 01 33 29 SUSTAINABILITY REPORTING.

Section 01 33 00.10 10 DIGITAL SUBMITTAL PROCEDURES AND CORRESPONDENCE Section 01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS Section 01 45 00.00 10 QUALITY CONTROL

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. Submittals with an "S" are for inclusion in the Sustainability Notebook, in conformance to Section 01 33 29 SUSTAINABILITY REPORTING, when included in the project. Submit the following in accordance with Section 01 33 00.10 10 DIGITAL SUBMITTAL

PROCEDURES AND CORRESPONDENCE:

SD-01 Preconstruction - Construction Schedule Submittals

Project Scheduler/DAR Qualifications; G Preliminary Project Schedule; G Project/Initial Schedule; G Recovery Schedule; G Periodic Schedule Update; G

SD-07 Certificates

Designated Authorized Representative (DAR) Project Scheduler Qualifications; G

Documentation listing, not limited to:

a. Detailed documentation of experience in scheduling (school, training, software, years scheduling, etc.).

b. Minimum of 3 previously developed, created, and maintained projects similar in nature and complexity to the project, detailing name and location of projects.

*AM2 ENTIRE SECTION REVISED

SECTION 01 32 01.00 10 Page 2

c. Qualifications to meet or exceed requirements under Section 01 32 01.00 10, paragraph 1.3 PROJECT SCHEDULER QUALIFICATIONS.

Submittals SD-01 and SD-07 shall be submitted as separate 4025’s for approval.

1.3 PROJECT SCHEDULER QUALIFICATIONS – DESIGNATED AUTHORIZED REPRESENTATIVE

(DAR)

Designate an authorized representative (DAR) to be responsible for the preparation of the schedule and all required updating and production of reports. The authorized representative (DAR) 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. DAR shall be same person or employee of a company approved under Section 01 32 01.00 10, paragraph

1.2 SUBMITTALS SD-07. A DAR change shall be submitted and approved, per Section 01 32 01.00 10, paragraph 1.2 SUBMITTALS, before new authorized representative takes over responsibilities from previous authorized representative. DAR to be responsible for the preparation of the schedule, all required updating, preparing of reports, and all requirements of these specifications. DAR shall have experience in the use of the scheduling software that meets the requirements of this specification.

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.

2.1.1 Government Default Software

The Government will use Primavera P6.

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

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the Contractor chooses software other than Primavera P6, the software shall be compliant with this specification. In addition, the Contractor shall provide for the Government's use two licenses, two computers, and software training for two Government employees. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned to the Contractor at project completion.

SECTION 01 32 01.00 10 Page 3

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 is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.

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

3.2 BASIS FOR PAYMENT AND COST LOADING

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

3.2.1 Activity Cost Loading

Contractor shall meet or provide to USACE cost loading before submission of Preliminary or Initial schedules to evaluate the cost loading to determine if cost loading is reasonable. Non-compliance with this requirement will result in an automatic rejection of preliminary or initial schedules submittals. Cost loading shall be done within the time frame required for submission of schedule per paragraph 3.4 PROJECT SCHEDULE SUBMISSIONS.

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

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer. See additional cost loading requirements under paragraph 3.3.19 COST LOADING OF CLOSEOUT ACTIVITIES.

3.2.2 Withholdings / Payment Rejection

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

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

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval.

SECTION 01 32 01.00 10 Page 4

Contractor shall provide a submittal activity for each administrative, construction, or close-out activity that requires a submittal (even if submittal is for information only) broken down into the following three (3) descriptions: Submit, Government Review, and Approval, unless activity is for procurement. Then follow direct in Section 01 32 01.00 10, paragraph

3.3.4 PROCUREMENT ACTIVITIES. Contractor can establish a cost for the Approval activity only if approval is given per Section 01 32 01.00 10, paragraph 3.2 BASIS FOR PAYMENT AND COST LOADING. Original duration for Submit and Approval activity shall be at a minimum of one (1) day.

Government Review shall be based on contract requirements.

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

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Less than 2 percent of all non-procurement activities shall have Original Durations (OD) greater than 10 work days or 14 calendar days. Once the schedule (Preliminary, Initial, Recovery, or Update) is approved, no changes to original activity durations shall be made without prior approval of the Government.

3.3.3 Permit Activities

Include permit activities with the necessary conferences and follow-up actions. Include in the project schedule, showing the sequence of events involved in carrying out the project permit tasks within the specific contract period. Provide at a detailed level of scheduling sufficient to identify all major permit tasks, including those that control the flow of work. Also include review and correction periods associated with each item.

3.3.4 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days. A typical procurement sequence includes the string of activities: Submit, Government Review, Approve, Procure, Fabricate, and Deliver.

3.3.5 Mandatory Tasks

Include the following activities/tasks in the Preliminary (as applicable), Initial, and Recovery Project Schedule and all updates.

a. Submission, review, and acceptance/approval of SD-01 Preconstruction

Submittals (individual activity for each).

b. Submission, review, and acceptance/approval of features require permit completion.

c. Submission, review, and acceptance/approval of mechanical/ electrical/information systems layout drawings.

d. Long procurement activities

SECTION 01 32 01.00 10 Page 5

e. Submission, review, and acceptance/approval of O & M manuals.

f. Submission, review, and acceptance/approval approval of as-built drawings.

g. Submission, review, and acceptance/approval of DD1354 data and installed equipment lists.

h. Submission, review, and acceptance/approval of testing and air balance

(TAB) report.

i. Submission, review, and acceptance/approval of TAB specialist design review report.

j. Submission, review, and acceptance/approval of fire protection specialist.

k. Submission, review, and acceptance/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. Provide activities and comply with Section 01 32

01.00 10, paragraph 3.3.7.9 COMMISSIONING CODING (MCOM).

l. Air and water balancing.

m. Building commissioning - Functional Performance Testing.

n. Submission, review, and acceptance/approval Controls testing plan submission.

o. Submission, review, and acceptance/approval Controls testing.

p. Performance Verification testing.

q. Submission, review, and acceptance/approval other systems testing, if required.

r. Contractor's pre-final inspection.

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

t. Government's pre-final inspection.

u. Correction of punch list from Government’s pre-final inspection.

v. Final Inspection.

3.3.6 Government Activities

Show Government and other agency activities that could impact progress. These activities include, but are not limited to: approvals, acceptance, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.7 Standard Activity Coding Dictionary

SECTION 01 32 01.00 10 Page 6

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. Contractor shall create the schedule using the following codes for each individual project. Contractor shall define each activity code as a PROJECT activity code. This exact structure is mandatory.

All Activity Codes shall be developed and assigned to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil.

The SDEF format is as follows:

Field Activity Code Length Description

1 WRKP 3 Workers per day

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work (per paragraph 3.3.7.7)

8 FOW 20 Feature of work*

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.3.7.1 Workers Per Day (WRKP)

Assign Workers per Day (WRKP) for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day shall be the average number of workers expected each day to perform a task for the duration of that activity. This code shall be used when Contractor is required to provide a resource loaded schedule. Activities may have more than one WRKP code so as to document different number of resources assigned to that activity. Using RESP or any other activity code and/or resource/expenses to provide number of resources assign to an activity is prohibited. WRKP codes shall be numeric-alpha. Example would be Code Value 3M, 3=CREW SIZE, M=Mason. Activity Workers Per Day Codes shall be imported through the SDEF conversion of the schedule into QCS/RMS. Manual inputting of Activity Workers Per Day Codes into QCS/RMS is prohibited.

3.3.7.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency (ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, http://rms.usace.army.mil/

SECTION 01 32 01.00 10 Page 7 environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements. Government shall not be used for any activity that has costs associated with it. For activities that require Government approval and must have cost associated with them, the Contractor shall use “PRIM” for those activities.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values for (RESP) are: DOR (for the designer of record); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE). Assign Responsibility Code for all activities to the Prime Contractor or Subcontractor. Unacceptable code values are abbreviations of the names of prime contractors or subcontractors. RESP codes shall be alpha; numeric is not allowed for RESP codes. Activity Responsibility Codes shall be imported through the SDEF conversion of the schedule into QCS/RMS. Manual inputting of Activity Responsibility Codes into QCS/RMS is prohibited.

3.3.7.3 Area of Work Coding (AREA)

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. Not all activities are required to be Work Area coded. A lack of Work Area coding indicates the activity is not resource or space constrained. Each activity using a Work Area code shall be identified within a single project area and have only one Work Area code. AREA codes shall be alpha and/or numeric or a combination of both. Activity Work Area Codes shall be imported through the SDEF conversion of the schedule into QCS/RMS. Manual inputting of Activity Work Area Codes into QCS/RMS is prohibited.

3.3.7.4 Modification Number (MODF)

Assign a Modification Number Code (MODF) to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code. Modification Number Code (MODF) shall be imported through the SDEF conversion of the schedule into QCS/RMS. Manual inputting of Modification Number Code (MODF) into QCS/RMS is prohibited.

3.3.7.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code. Contract Line Item Codes (BIDI) shall be imported through the SDEF conversion of the schedule into QCS/RMS. Manual inputting of Contract Line Item Codes into QCS/RMS is prohibited.

3.3.7.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are design phase, procurement phase, and construction phase. Each activity can have only one Phase of Work code. Phase of Work Codes shall be imported

SECTION 01 32 01.00 10 Page 8 through the SDEF conversion of the schedule into QCS/RMS. Manual inputting of Phase of Work Codes into QCS/RMS is prohibited.

a. Code proposed fast track construction phases proposed to allow filtering and organizing the schedule by fast track construction packages.

b. If the contract specifies phasing with separately defined performance periods, identify a Phase Code to allow filtering and organizing the schedule accordingly.

3.3.7.7 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the predetermined codes and descriptions in QCS/RMS dependant on District Library. Each activity shall have only one Category of Work Code. Category of Work Codes shall be imported through the SDEF conversion of the schedule into QCS/RMS.

Manual inputting of Category of Work Codes into QCS/RMS is prohibited. The codes are as follows:

Tulsa District CATW Codes

Field Category Code Length Description

1 1 1 GENERAL

2 A 1 ARCHITECTURAL

3 B 1 PAINTING

4 C 1 CIVIL

5 D 1 DESIGN

6 E 1 ELECTRICAL

7 F 1 FIRE EXTINGUISH

8 G 1 GENERAL CONTRACTOR

9 H 1 HAZARDOUS/TOXIC

10 I 1 DRYWALL/STUDS

11 J 1 FLOORING

12 L 1 LANDSCAPE

13 M 1 MECHANICAL

14 P 1 PLUMBING

15 Q 1 DIRTWORK, ASPHALT

16 R 1 ROOFING

17 S 1 STRUCTURAL

18 T 1 SAFETY

19 X 1 ADMINISTRATIVE

3.3.7.8 Feature of Work Coding (FOW)

Contractor shall use the features of work created as part of the QC Plan.

Contractor shall provide feature of work report as part of schedule submittals.

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan. Definable Feature of Work is defined in Section 01 45 00.00 10 QUALITY CONTROL. An activity can have only one Feature of Work Code. Every activity shall have a Feature of Work code. Feature of Work Codes shall be created as part of the QC Plan and inserted into the schedule. Manual inputting of Features of Work Codes into QCS/RMS shall not be done after QC Plan is approved. If additional Features of Work are to be added or deleted, Contractor shall have Government review and acceptance before proceeding.

SECTION 01 32 01.00 10 Page 9

3.3.7.9 Commissioning Coding (MCOM)

A Commissioning Code shall be assign to every activity that part of the Commissioning Scope of Work whether it is a submittal, report, or construction. Each activity shall have only one Commissioning Code. Manual inputting of Commissioning Codes into QCS/RMS is prohibited. As applicable and/or as a minimum, the Contractor shall provide in the schedule the following activities:

ACTIVITY DESCRIPTIONS

Submit Commissioning Firm Gov’t Review Commissioning Firm Approval Commissioning Firm Submit Commissioning Agent Gov’t Review Commissioning Agent Approval Commissioning Agent Submit Commissioning Plan Gov’t Review Commissioning Plan Approval Commissioning Plan Submit TAB Firm Gov’t Review TAB Firm Approval TAB Firm Submit TAB Specialist Gov’t Review TAB Specialist Approval TAB Specialist Submit TAB Procedures Gov’t Review TAB Procedures Approval TAB Procedures Submit TAB Schematic Drawings-Forms Gov’t Review TAB Schematic Drawings-Forms Approval TAB Schematic Drawings-Forms Submit Design Review Report Gov’t Review Design Review Report Approval Design Review Report Pre FPT Checks Equipment Start-Up

TAB

Submit TAB Report Gov’t Review TAB Report Approval TAB Report TAB Verification Submit TAB Verification Report Gov’t Review TAB Verification Report Approval TAB Verification Report Control Start-Up Test Submit Control Start-Up Test Report Gov’t Review Control Start-Up Test Report Approval Control Start-Up Test Report

PVT (CONTROLS)

Submit PVT Report Gov’t Review PVT Report Approval PVT Report LNS Development UMCS Integration Contractor Front End Test Submit UMCS Start-Up Report

SECTION 01 32 01.00 10 Page 10

Gov’t Review UMCS Start-Up Report Approval UMCS Start-Up Report

PVT (FRONT END)

FPT

Submit FPT Report Gov’t Review FPT Report Approval FPT Report Submit Commissioning Report Gov’t Review Commissioning Report Approval Commissioning Report

Contractor shall include the activities and logic to show a complete trail from start to final completion of commissioning, including LEED requirements. Schedule shall incorporate the above list, along with other activities required to provide a complete logic trail. Activities related to building construction that effect Commissioning (example: Building dry-in) shall have a Commission code assign. Commissioning activities shall be part of Construction logic and be completed on or before Contract Required Completion date.

3.3.8 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 schedule must include milestone activities for each significant project event including but not limited to: milestone activities for each fast track construction; 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. If milestone is ahead of NTP, then Contractor shall use NTP date for start and finish date with a one-day duration. The schedule shall include (as applicable) the following milestones along with any additional milestones requested:

CERTIFICATES OF INSURANCE TURNED IN

SURETY BONDS

NOI COMPLETED

NOT COMPLETED

SWPPP APPROVED (SUBMITTED 15 DAYS AFTER CONTACT AWARD OR 30DAYS

AFTER NTP SEE RFP TO DETERMINE)

ENVIRONMENTAL PROTECTION PLAN (15 DAYS AFTER NTP : 7 DAYS PRIOR TO

PRECONSTRUCTION CONFERENCE)

WASTE MANAGEMENT PLAN (15 DAYS AFTER CONTRACT AWARD)

ASBESTOS SUBMITTAL

NESHAP SUBMITTED

SITE PLAN SUBMITTED (21 DAYS AFTER NTP)

HEALTH AND SAFETY PLAN SUBMITTED

WORK PLAN

QUALITY CONTROL PLAN SUBMITTED (QCQ PLAN DUE 30 DAYS AFTER NTP)

SUBMITTAL REGISTER SUBMITTED (15 DAYS AFTER NTP)

COMMISSIONING AGENT SUBMISSION (PRIOR TO 1ST BUILDING DESIGN

MEETING/SUBMITTAL)

COLOR BOARDS (75 CALENDAR DAYS AFTER NTP)

PRECONSTRUCTION CONFERENCE

COMMISSIONING PLAN SUBMISSION

SECTION 01 32 01.00 10 Page 11

COMMISSIONING START

COMMISSIONING END

PERFORMANCE VERIFICATION TESTING (PVT) START

PERFORMANCE VERIFICATION TESTING (PVT) END

FIRE CODE/LIFE SAFETY CODE REVIEW ANALYSIS

QA-QC MEETING OF UNDERSTANDING

SUBMITTAL REGISTER COMPLETED

CONSTRUCTION SCHEDULE SUBMITTED

FOUNDATION/SUBSTRUCTURE STARTED

FOUNDATION/SUBSTRUCTURE COMPLETED

STEEL ERECTION COMPLETED

BUILDING DRY-IN

START MATERIAL PROCUREMENT (LONG LEAD ITEMS)

PERMANENT POWER TO BUILDING

HVAC START-UP

ELEVATOR START-UP

FIRE ALARM SYSTEM TESTING

72 HOUR FIRE ALARM TEST

FIRE SPRINKLER SYSTEM TESTING

NFPA 13 FORMS SUBMITTED

KITCHEN EQUIPMENT DELIVERY: START-UP: OPERATIONAL

CONTRACTOR PROVIDED EQUIPMENT/FURNITURE INSTALLATION

KEY BITTING CONFERENCE (LOCKS AND KEY PLAN)

WARRANTY MEETING

90% RED ZONE MEETING

The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Using a SS, FF, or FS relationship in unison as a predecessor or successor to an activity is prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein.

3.3.8.1 Project Start Date Milestone and Constraint

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

3.3.8.2 End Project Finish Milestone and Constraint

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

The project schedule must be constrained 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 "End Project” activity shall have a constraint (preferred method) by using the "project must finish by" date in the scheduling software and

SECTION 01 32 01.00 10 Page 12 the date to be inserted into "project must finish by" shall be the contract completion date. The Government is under no obligation to accelerate Government activities to support a Contractor's early completion.

3.3.8.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.3.8.3.1 Start Phase

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

3.3.8.3.2 End Phase

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

3.3.9 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 Seasonal 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. The assignment of the non-work days should be over a seven-day week since weather records are compiled on seven-day weeks, which will cause some of the weather related non-work days to fall on weekends.

Contractor shall not use default/template “Global” calendars in software.

Contractor shall create specific “Project” calendars.

3.3.10 Open Ended Logic

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

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

3.3.11 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

SECTION 01 32 01.00 10 Page 13 in the Daily Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating will result in disapproval of the Contractor's schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

3.3.12 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 (MPM) meetings.

3.3.13 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.3.14 Original Durations

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. Less than 2 percent of all non-procurement activities shall have Original Durations (OD) greater than 10 work days or 14 calendar days. Once the schedule (Preliminary, Initial, Recovery, or Update) is approved, no changes to original activity durations shall be made without prior approval of the Government.

3.3.15 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. Lags shall not be more than 5 working days or 7 calendar days.

a. Leads (negative lags) are prohibited.

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

3.3.16 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 to be allowed.

3.3.17 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

SECTION 01 32 01.00 10 Page 14 management. Remaining costs shall be remain for future placement. Creating or updating percent complete and remaining duration of any activity shall be independent functions. Disable program features, which calculate one of these parameters from the other.

3.3.18 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. Creating or updating percent complete and remaining duration of any activity shall be independent functions. Disable program features, which calculate one of these parameters from the other.

3.3.19 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity (ies) total not less than $35,000 or 1 percent of the present contract value, whichever is greater, up to $200,000. Activity (ies) may be declared 100 percent complete upon the Government's verification of completion and corrections of all punch list work identified during Government pre-final inspection(s).

3.3.19.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, whichever is greater, up to $200,000.

Activity will be declared 100 percent complete upon the Government's approval.

3.3.19.2 O & M Manuals

If there is no separate contract line item (CLIN) for O & M manuals, cost load the "Approval of O & M manuals" activity not less than $35,000 or 1 percent of the present contract value, whichever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

3.3.20 Anticipated Adverse Weather

Refer to contract 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.3.21 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 responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

SECTION 01 32 01.00 10 Page 15

3.4 PROJECT SCHEDULE SUBMISSIONS

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

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

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule 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 or Recovery 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, permitting activities and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the all other specified Program and Plan approvals must occur prior to any planned construction activities. All activities shall have activity codes whether they are for the first 90 calendar days or are summary in nature after the first 90 calendar days. All paragraphs of this specification shall be included with this submission.

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities, which represent all work through the entire contract performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer. Include in the Initial schedule detailed permitting activities, including but not limited to identification permit submissions and any required Government actions, and long lead item acquisitions. Also cover in the Initial schedule the entire construction effort with as much detail as is known at the time but, as a minimum, include all construction start and completion milestones, and detailed construction activities, including all activity coding and cost loading. All paragraphs of this specification shall be included with this submission. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Recovery Project Schedule Submission

If the Contractor falls behind his approved schedule (behind the LS/LF cash flow curve of more than 20 calendar days of negative float), or performs the work in such a manner that the network diagram and mathematical analysis no longer indicate reasonable logic and duration for completion of the work by

SECTION 01 32 01.00 10 Page 16 the current contract completion date, as determined by the Contracting Officer, the Contractor shall promptly provide a supplemental recovery or completion schedule to regain the original schedule, or a supplemental completion schedule to complete by the current completion date, as approved by the Contracting Officer. Recovery schedule shall be submitted via 4025 with all documentation required per specifications. The recovery schedule shall be resource loaded, utilizing the WRKP activity code as listed in Section 01 32 01.00 10, paragraph 3.4.5 STANDARD ACTIVITY CODING DICTIONARY and Section 01 32 01.00 10, paragraph 3.3.2.6 ACTIVITY RESPONSIBILITY CODING (WRKP), with crew size and productivity for each remaining activity, and indicating overtime, weekend work, and/or double shifts needed to regain the schedule, in accordance with FAR 52.236-15, without additional cost to the Government. The recovery schedule shall not replace the original approved schedule as the official contract schedule until submitted and approved. If required by Contracting Officer, the original approved schedule shall be updated monthly (in addition to the supplemental schedule) and monitored by the Contractor and Contracting Officer to determine the effect of the supplemental schedule progress has on the contract progress to regain the rate of progress for timely completion.

The Contractor shall not artificially improve his progress by revising the schedule logic restraints or shortening future work activity durations. The Contractor may improve his progress by performing sequential work activities concurrently or by performing activities more quickly than planned, but such improvements shall be indicated on the supplement schedule and shall not be recorded on the official schedule until they have actually been achieved by the Contractor. The additional resources required to improve the progress must be evident on the work site.

Failure of the Contractor to perform work and maintain progress in accordance with the supplemental recovery or completion schedule may result in an interim and final unsatisfactory performance rating and/or may result in corrective action by the Contracting Officer in accordance with FAR 52.236-15.

3.4.4 Periodic Schedule Updates

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