A.1.9 322-1905_Specifications_2022-03_RevG.pdf

March 2022

MK ENGINEERS (USACE)

FY22 – CONTAINERIZED POWER

PLANT AND ELECTRICAL

DISTRIBUTION SYSTEM

Meck Island, Kwajalein Atoll, Republic of The Marshall Islands

US Army Garrison Kwajalein Atoll

Specifications

PROJECT NUMBER:

160075

PROJECT CONTACT:

RYAN MCMURTREY

EMAIL:

RYAN.MCMURTREY@POWERENG.COM

PHONE:

208-288-6492

BOI 0322-1905 160075 (2022-03-21) EYT i

SPECIFICATIONS

PREPARED FOR: MK ENGINEERS (USACE)

PREPARED BY: RYAN MCMURTREY

208-288-6492

RYAN.MCMURTREY@POWERENG.COM

REVISION HISTORY

DATE REVISED BY REVISION

13DEC19 R. McMurtrey A – 65% Design Submittal

22MAY20 R. McMurtrey B – 95% Design Submittal

15JUL20 R. McMurtrey C – 100% Design Submittal

04SEP20 R. McMurtrey D – RTA Submittal

26JAN22 R. McMurtrey E – RTA Submittal Rev 1

04MAR22 R. McMurtrey F – RTA Submittal Rev 2

21MAR22 R. McMurtrey G – RTA Submittal Rev 3

� � ���������������� !"#�!$%&&'�(��)�*�+����� !"#�! ,&&$-��./01232145267.�89:�3;<<�1=>?@A>BCADBE�/=FBC�/G@>?�@>E�0GBH?CAH@G�IAJ?CAKL?A=>�.MJ?BN���.5OP15PO4Q��RST�89UU9VWXY�Z[T\W8W\]̂W9XZ�ZT\̂W9XZ�S]_T�̀TTX�[:T[]:Ta�bXaT:�̂ST�:TZ[9XZẀUT�\S]:YT�98�c9:d�eT̀ ẐT:f�ghih��I2j2.267�kl�m�n070O4Q�O0oP2O0p075.�qr�st�ut�vgicwxy�wzvgicRw{zv������������ � |}~~}~~

������������� !�"#$$#%&'(�)*!+&"&+,-&#')�)!+-&#')� ,.!�/!!'�*0!*,0!1�2'1!0�- !�0!)*#')&/$!�+ ,0(!�#"���3�4�5�67�89�:��;�5��7<��673���675�=>�??�?>�@ABC�BDBE�FG@CB�HIJBD�EG@�DGKL�GIM�F@@BNKCGB@������������ �OPQQ�RSTUVWXPYZV[V\SYY]�̂V[TP_�̀]�OPQQ�RSTUVWXPYZab�cdeUf�gdhPQQijST̂VWXPYklmnPoPT[iWmpf�qdrsqtgu�gT[VTPPôf�vTWrf�cadOPQQ�RSTUVWXPYwmWS\VmTb�xmV̂Pf�vZuPŜmTb�v�Sp�SllomjVT[�\yV̂�_mWzpPT\cmT\SW\�vTQmb�{|}i{}}i~���ZS\Pb�{|{{i|�i{��|}b|}b�}�|~�||�

Jefferson D. VanSickel, P.E.

US Army Corps of Engineers ®

CIVIL

The following specifications sections have been prepared under the responsible charge of W. Keith Waller, P.E.

DIVISION 31 – EARTHWORK

31 00 00 EARTHWORK

03/22/2022

FY22 Meck Containerized Power Plant and Electrical Distribution W9128A19F0065

PROJECT TABLE OF CONTENTS

DI VI SI ON 00 - PROCUREMENT AND CONTRACTI NG REQUI REMENTS

00 22 13.00 20 02/14, CHG 3: 11/18 SUPPLEMENTARY INSTRUCTIONS TO OFFERORS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 32 00 03/17 PROJECT SCHEDULE

01 33 00 03/17 SUBMITTAL PROCEDURES

01 35 26 03/17 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 03/17 RMS3 - CONTRACTOR MODE (RMS3/CM)

01 45 04 03/17 CONTRACTOR QUALITY CONTROL

01 45 35 11/20 SPECIAL INSPECTIONS

01 50 00 05/18 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 78 00 03/17 CLOSEOUT SUBMITTALS

01 78 23 08/15 OPERATION AND MAINTENANCE DATA

01 90 00 01/18 MISCELLANEOUS PROVISIONS

DI VI SI ON 02 - EXI STI NG CONDI TI ONS

02 41 00 05/10, CHG 2: 02/19 DEMOLITION

02 81 00 11/18 TRANSPORTATION AND DISPOSAL OF

HAZARDOUS MATERIALS

02 82 00 11/18 ASBESTOS REMEDIATION

02 83 00 11/18 LEAD REMEDIATION

DI VI SI ON 03 - CONCRETE

03 30 00 02/19 CAST-IN-PLACE CONCRETE

DI VI SI ON 09 - FI NI SHES

09 96 00 11/14 HIGH-PERFORMANCE COATINGS

DI VI SI ON 21 - FI RE SUPPRESSI ON

21 13 13.00 10 05/09 WET PIPE SPRINKLER SYSTEM, FIRE

PROTECTION

DI VI SI ON 25 - I NTEGRATED AUTOMATI ON

25 05 11 11/17 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS

25 10 10.01 05/06 SCADA INTEGRATION

25 10 10.02 03/20 MICROGRID CONTROL SYSTEM (MGCS)

INTEGRATION

DI VI SI ON 26 - ELECTRI CAL

26 05 19.10 10 05/16 INSULATED WIRE AND CABLE

26 05 48.00 10 10/07 SEISMIC PROTECTION FOR ELECTRICAL

EQUIPMENT

26 08 00 08/08 APPARATUS INSPECTION AND TESTING

26 11 16 02/10 SHELTERED AISLE POWER DISTRIBUTION

ASSEMBLIES

26 24 13 05/15 SWITCHBOARDS

PROJECT TABLE OF CONTENTS Page 1

REVISED MARCH 2022

* Revised March 2022

26 28 01.00 10 10/07 COORDINATED POWER SYSTEM PROTECTION

26 41 00 11/13 LIGHTNING PROTECTION SYSTEM

26 56 00 05/13 EXTERIOR LIGHTING

DI VI SI ON 28 - ELECTRONI C SAFETY AND SECURI TY

28 31 64.00 10 08/09 FIRE DETECTION AND ALARM SYSTEM,

ADDRESSABLE

DI VI SI ON 31 - EARTHWORK

31 00 00 08/08 EARTHWORK

31 11 00 11/18 CLEARING AND GRUBBING

DI VI SI ON 32 - EXTERI OR I MPROVEMENTS

32 11 20 08/17 BASE COURSE FOR RIGID PAVING

32 13 13.06 05/20 PORTLAND CEMENT CONCRETE PAVEMENT FOR

ROADS AND SITE FACILITIES

DI VI SI ON 33 - UTI LI TI ES

33 11 00 02/18 WATER UTILITY DISTRIBUTION PIPING

33 71 02 02/15 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 04/06 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

REVISED MARCH 2022

* Revised March 2022

SECTION TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

DOCUMENT 00 22 13.00 20

SUPPLEMENTARY INSTRUCTIONS TO OFFERORS

02/ 14, CHG 3: 11/ 18

PART 1 GENERAL

1.1 CONTRACT LINE ITEMS

1.2 GENERAL BID NOTES

PART 2 PRODUCTS

PART 3 EXECUTION

-- End of Section Table of Contents --

DOCUMENT 00 22 13.00 20 Page 1

REVISED MARCH 2022

DOCUMENT 00 22 13.00 20

SUPPLEMENTARY INSTRUCTIONS TO OFFERORS

02/ 14, CHG 3: 11/ 18

PART 1 GENERAL

1.1 CONTRACT LINE ITEMS

The terms Offeror and Bidder and versions thereof (offer/bid) have the same definition as used within this contract.

Provide the Contract Line Item (CLIN) lump sum price for the following items:

CLIN 0001 - BASE PRICE. Price for the entire project Site Work for the replacement of the 4,160 V medium voltage (MV) electrical distribution system located at Meck Island, U.S. Army Garrison – Kwajalein Atoll, Republic of the Marshall Islands, complete in accordance with the drawings and specifications but excluding work described in CLIN 0002. Price includes the following:

DOCUMENT 00 22 13.00 20 Page 2

CLIN DESCRIPTION TOTAL

PRICE

FOR

CLIN

0001 All work required to demolish, remove and provide, test, and commission existing primary and secondary electrical distribution equipment at B5030, B5040, B5041, B5065, B5070, B5080, B5095, B5102, B5128 as indicated in the contract documents.

Procure, deliver, install, test, and commission a new main distribution switchgear system (PDC).

Procure, deliver, install, test, and commission new breakers, enclosures, and supporting equipment to extend the B5030 switchgear bus, adding two breaker sections.

Provide new feeders and supporting infrastructure to connect the B5030 paralleling switchgear lineup to the new PDC as shown in the contract documents.

Demolish and dispose of the existing B5020 switchgear and enclosure.

Remove and dispose existing HVPS 1 and HVPS 2 feeders.

Remove existing, dispose, and provide new Tech 1, Tech 2, and Area Utility feeders.

Provide new ductbanks as indicted in the contract documents.

DOCUMENT 00 22 13.00 20 Page 3

PRICE

FOR

CLIN

0001 (continued)

Remove existing and provide new feeders (MICB 1, MICB 2) servicing the existing B5050 SWGR #1.

Provide all labor, materials, and equipment required to remove existing primary feeders from SWGR #1, field determine routing into the existing SWGR #1, and terminate / test / and energize new feeders into existing the B5050 SWGR #1 with feed from the Contractor provided PDC.

Install fiber optic cable and 2 conduit between the PDC and JCI microgrid controller as indicated on TN501, TN504, and TN601.

Modify MGC specification to include serial protocol configuration for the required meters, fiber to serial convertors and MGC configuration changes to map the new meter communications.

Decommission the meter configurations in the MGC for the B5020 switchgear.

Provide the balance of communications conduits connecting to new load substations with pull strings to support future fiber optic cable installation.

Provide the PDC in a with all protective relays and meter connected to the signal marshalling cabinet shown on sheets TN504 and TN505. Communications protocol configurations for the protective relays and meters supporting these IP connections will not be done.

Provide networking equipment as indicated on sheets TN504 and TN505. Network equipment configurations will be default factory settings.

Provide bulk fuel system monitoring, PA, and Dedicated Communications systems as indicated in the contract documents.

The bulk fuel system monitoring will be SCADA ready, but will not communicate with a SCADA system or operator interface.

CLIN 0002 Option Item No. 1 - Price includes the following:

Price for providing all work in connection with the 4,160 V medium voltage (MV) electrical distribution system located at Meck Island, U.S. Army Garrison – Kwajalein Atoll, complete in accordance with the drawings and specifications.

DOCUMENT 00 22 13.00 20 Page 4

PRICE

FOR

CLIN

0002 Remove existing primary and secondary substation and distribution equipment from the B5050 Main Electrical Room as indicated in the contract documents

Procure, deliver, install, test, and commission the replacement B5050 primary and secondary substation equipment as indicated in the contract documents

Connect the replacement B5050 primary substation to the new feeders provided under the base bid as indicated in the contract documents

Integrate the B5050 primary substation into the SCADA system provided under the Option 1

Provide SCADA hardware, communications media, equipment, testing, and commissioning as indicated on sheets EI501, T-101, TN503, TN507, TN508, TN602 and in the design technical specifications as required to deliver a complete and useable SCADA system.

Integrate the existing MGC Ethernet network with the new SCADA Ethernet network providing a MGC gateway to pass information to the SCADA system.

Provide MGC configuration changes to support the new IP meter communications and SCADA gateway.

1.2 GENERAL BID NOTES

a. The Government reserves the unilateral right to award CLIN 0002 to the Contractor at the proposed price within 30 calendar days after the contract award. A firm fixed proposed price is required for CLIN 0001, CLIN 0002. No provision is made for economic price adjustment.

If Options are exercised, the contract completion date remains unchanged after award of the contract.

b. Evaluation of Options (JUL 1990). Except when it is determined in accordance with FAR 17.206(b) Evaluation not to be in the Government's best interest, the Government will evaluate offers for award purposes by adding the price for the Option(s) to the total price for CLIN 0001. In accordance with FAR 52.217-5 Evaluation of Options, evaluation of options will not obligate the Government to exercise the Option(s).

c. The Government may reject an offer as nonresponsive if it is materially unbalanced as to prices for the basic requirement and the optionquantities. An offer is unbalanced when it is based on prices significantly less than cost for some work and prices which are significantly overstated for other work.

DOCUMENT 00 22 13.00 20 Page 5

d. If CLIN 0002 is exercised, additional bonding and consent of surety is required. Consequently, the Performance Bond must reflect 100 percent of the aggregate amount of all Items.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Document --

DOCUMENT 00 22 13.00 20 Page 6

FY22 Containerized Power Plant and Electrical Distribution System

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 00

PROJECT SCHEDULE

03/17

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Primavera

2.1.2.2 Other Than Primavera

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Permit Activities

3.3.4 Procurement Activities

3.3.5 Mandatory Tasks

3.3.6 Government Activities

3.3.7 Standard Activity Coding Dictionary

3.3.7.1 Workers Per Day (WRKP)

3.3.7.2 Responsible Party Coding (RESP)

3.3.7.3 Area of Work Coding (AREA)

3.3.7.4 Modification Number (MODF)

3.3.7.5 Bid Item Coding (BIDI)

3.3.7.6 Phase of Work Coding (PHAS)

3.3.7.7 Category of Work Coding (CATW)

3.3.7.8 Feature of Work Coding (FOW)

3.3.8 Contract Milestones and Constraints

3.3.8.1 Project Start Date Milestone and Constraint

3.3.8.2 End Project Finish Milestone and Constraint

3.3.8.3 Interim Completion Dates and Constraints

3.3.8.3.1 Start Phase

3.3.8.3.2 End Phase

3.3.9 Calendars

3.3.10 Open Ended Logic

3.3.11 Default Progress Data Disallowed

3.3.12 Out-of-Sequence Progress

SECTION 01 32 00 Page 1

3.3.13 Added and Deleted Activities

3.3.14 Original Durations

3.3.15 Leads, Lags, and Start to Finish Relationships

3.3.16 Retained Logic

3.3.17 Percent Complete

3.3.18 Remaining Duration

3.3.19 Cost Loading of Closeout Activities

3.3.19.1 Final Record (As-Built) Drawings

3.3.19.2 O & M Manuals

3.3.20 Anticipated Adverse Weather

3.3.21 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Preliminary Project Schedule Submission

3.4.2 Initial Project Schedule Submission

3.4.3 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Data CD/DVDs

3.5.2 Narrative Report

3.5.3 Schedule Reports

3.5.3.1 Activity Report

3.5.3.2 Logic Report

3.5.3.3 Total Float Report

3.5.3.4 Earnings Report by CLIN

3.5.3.5 Schedule Log

3.5.4 Network Diagram

3.5.4.1 Continuous Flow

3.5.4.2 Project Milestone Dates

3.5.4.3 Critical Path

3.5.4.4 Banding

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

3.6.2 Update Submission Following Progress Meeting

3.7 WEEKLY PROGRESS MEETINGS

3.8 REQUESTS FOR TIME EXTENSIONS

3.8.1 Justification of Delay

3.8.2 Time Impact Analysis (Prospective Analysis)

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

3.8.4 Fragmentary Network (Fragnet)

3.8.5 Time Extension

3.8.6 Impact to Early Completion Schedule

3.9 FAILURE TO ACHIEVE PROGRESS

3.9.1 Artificially Improving Progress

3.9.2 Failure to Perform

3.9.3 Recovery Schedule

3.10 OWNERSHIP OF FLOAT

3.11 TRANSFER OF SCHEDULE DATA INTO RMS3/CM

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

-- End of Section Table of Contents --

SECTION 01 32 00 Page 2

SECTION 01 32 00

PROJECT SCHEDULE

03/17

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G Preliminary Project Schedule; G Initial Project Schedule; G

SD-06 Test Reports

Narrative Report Schedule Reports Periodic Schedule Updates

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

SECTION 01 32 00 Page 3

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 intends to 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 native schedule file (or 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 that is compliant with this specification but is other than Primavera P6, the software must be capable of generating a data file in the Standard Data Exchange Format (SDEF) as described in paragraph STANDARD ACTIVITY CODING DICTIONARY.

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

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

Provide additional documentation to demonstrate reasonableness if requested

SECTION 01 32 00 Page 4 by the Contracting Officer.

3.2.2 Withholdings / Payment Rejection

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

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

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

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

3.3.2 Activity Durations

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

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

3.3.3 Permit Activities

Include permit activities with the necessary conferences and follow-up actions and design package submission dates.

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.

3.3.5 Mandatory Tasks

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

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

b. Submission, review and acceptance of features require design completion

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

d. Long procurement activities

SECTION 01 32 00 Page 5

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

g. Submission and approval of installed equipment lists.

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

i. Submission of TAB specialist design review report.

j. Submission and approval of fire protection specialist.

k. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

l. Air and water balancing.

m. Building commissioning - Functional Performance Testing.

n. Controls testing plan submission.

o. Controls testing.

p. Performance Verification testing.

q. 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, environmental permit approvals by State regulators, inspections, utility tie-ins, road closures, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.7 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. Additional information is available on the RMS web site:

http://rms.usace.army.mil/QCS/Guides.

SECTION 01 32 00 Page 6

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

8 FOW 30 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 for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

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, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE). Unacceptable code values are abbreviations of the the names of subcontractors.

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

SECTION 01 32 00 Page 7 different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings.

Activities cannot have more than one Work Area Code.

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.

3.3.7.4 Modification Number (MODF)

Assign a Modification Number Code 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.

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.

3.3.7.6 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and construction phase. Each activity can have only one Phase of Work code.

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 a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittal,procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity canhave no more than one Category of Work Code.

3.3.7.8 Feature of Work Coding (FOW)

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 04 CONTRACTOR QUALITY CONTROL. An activity can have only one Feature of Work Code.

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 use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or affect network logic are prohibited.

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

SECTION 01 32 00 Page 8

3.3.8.1 Project Start Date Milestone and Constraint

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

3.3.8.2 End Project Finish Milestone and Constraint

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

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

3.3.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. Call the start milestone "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.

3.3.10 Open Ended Logic

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

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

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

SECTION 01 32 00 Page 9 complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other. Activity Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process must match those dates provided in the Contractor Quality Control Reports. Failure to document the AS and AF dates in the Daily Quality Control report will result in disapproval of the Contractor's schedule.

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

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.

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

SECTION 01 32 00 Page 10

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.

3.3.19 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

3.3.19.1 Final Record (As-Built) Drawings

If there is no separate contract line item (CLIN) for final record (as-built ) drawings, cost load the "Submission and approval of final record (as-built ) drawings" activity not less than $35,000 or 1 percent of the present contract value, which ever is greater, up to $200,000. Activity will be declared 100 percent complete upon the Government's acceptance of the completed final record (as-built drawings).

3.3.19.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's acceptance of all O & M manuals.

3.3.20 Anticipated Adverse Weather

Paragraph applicable to contracts with clause S-36.5 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER (Section 00 73 00). Original durations must account for anticipated adverse weather. All work periods not identified as non-work periods on each calendar will be interpreted as a Contractor-intended work period.

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.

c. The Government shall be exempt from liability for early completion delay damages. No claim shall be made by or allowed to the Contractor for any damages which may arise out of any delay to early completion.

SECTION 01 32 00 Page 11

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 acceptance. The accepted Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule.

The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as permitting activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for acceptance within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. No payment will be made for work items not fully detailed in the Project Schedule.

3.4.3 Periodic Schedule Updates

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

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

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

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

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

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, SECTION 01 32 00 Page 12 and every Periodic Schedule Update throughout the life of the project:

3.5.1 Data CD/DVDs

Provide two sets of data CD/DVDs containing the current project schedule and all previously submitted schedules in the format of the scheduling software (e.g. .XER). Also include on the data CD/DVDs the Narrative Report and all required Schedule Reports. Label each CD/DVD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date, Contract ID, and file name. Each schedule must have a unique Contract ID and file name and use project specific settings.

3.5.2 Narrative Report

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

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

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

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

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

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

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

3.5.3 Schedule Reports

The format, filtering, organizing and sorting for each schedule report will be as directed by the Contracting Officer. Typically, reports contain Activity Numbers, Activity Description, Original Duration, Remaining Duration, Early Start Date, Early Finish Date, Late Start Date, Late Finish Date, Total Float, Actual Start Date, Actual Finish Date, and Percent Complete. Provide the reports electronically in .pdf format. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

3.5.3.2 Logic Report

List of detailed predecessor and successor activities for every activity in

SECTION 01 32 00 Page 13 ascending order by activity number.

3.5.3.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.5.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

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

3.5.4 Network Diagram

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

3.5.4.1 Continuous Flow

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

3.5.4.2 Project Milestone Dates

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

3.5.4.3 Critical Path

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

3.5.4.4 Banding

Organize activities using the WBS or as otherwise directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by major elements of work, category of work, work area and/or responsibility.

SECTION 01 32 00 Page 14

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

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

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

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

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

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Updates of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS together with the monthly progress payment request.

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.8 REQUESTS FOR TIME EXTENSIONS

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

3.8.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact

SECTION 01 32 00 Page 15 to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.8.2 Time Impact Analysis (Prospective Analysis)

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

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

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

3.8.4 Fragmentary Network (Fragnet)

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

3.8.5 Time Extension

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

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

3.8.6 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The Contractor must show that an early completion was achievable had it not been for the impact.

SECTION 01 32 00 Page 16

3.9 FAILURE TO ACHIEVE PROGRESS

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

3.9.1 Artificially Improving Progress

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

3.9.2 Failure to Perform

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

3.9.3 Recovery Schedule

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

3.10 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, float available in the schedule, at any time, may not be considered for the exclusive use of either the Government or the Contractor including activity and/or project float. However, in accordance with paragraph EARLY COMPLETION SCHEDULE AND THE RIGHT TO FINISH EARLY, the Government is specifically and expressly exempt from liability for early completion delay damages. Activity float (or Free Float) is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone.