20-R-0025 Attachment 1 - Civil Works MATOC Specs.pdf

Solicitation No. W912BV20R????

US Army Corps of Engineers Tulsa District Arkansas & Red River Watersheds Kansas, Oklahoma, and Texas

MULTIPLE AWARD TASK

ORDER CONTRACT (MATOC)

FOR MAINTENANCE, REPAIR,

AND RESTORATION (MRR) –

FY20

Specifications

April 14, 2020

RSL

FY20

Civil Works MATOC General Repairs FY20 CIVILMATOCFY20

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 00 00 SUMMARY OF WORK

01 30 00 ADDITIONAL ADMINISTRATIVE REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 45 00 QUALITY CONTROL

01 46 00 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00 BULLETIN BOARD, PROJECT SIGN, AND SAFETY SIGN

DIVISION 03 - CONCRETE

03 30 53 MISCELLANEOUS CAST-IN-PLACE CONCRETE

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 05 19 GEOTEXTILE (FILTER CLOTH)

31 11 00 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 00 00 WORK COVERED UNDER OKLAHOMA DEPARTMENT OF TRANSPORTATION

2009 STANDARD SPECIFICATIONS FOR HIGHWAY CONSTRUCTION

32 20 00 TRAFFIC STRIPING

32 92 19 HYDROSEEDING

32 92 23 BERMUDA SOD

32 92 26 BERMUDA SPRIGGING

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 31 19 STONE PROTECTION

35 31 20 ARTICULATING CONCRETE BLOCK REVETMENTS

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION 01 00 00

SUMMARY OF WORK

08/15

PART 1 GENERAL

1.1 SCOPE OF WORK

The scope of this acquisition includes a wide range of Design-Bid-Build (DBB) civil, structural, mechanical and, electrical engineering, new utilities, relocation of existing utilities, and heavy construction activities for maintenance, repair, and rehabilitation of roads and other paved surfaces, small inhabitable structures, revetment and shoreline protection, small to medium sized concrete outlet works and control structures, foundation drainage systems, and other ancillary features that support flood control and navigation infrastructures. The Contractor shall provide all plant, materials, equipment, labor, instruments tools, subcontractors, supervision, management, and travel necessary to complete all work in accordance with this summary of work, the drawings, the base MATOC and task order specifications, and all other contract documents and requirements. When in conflict the task order specifications and drawings must supercede the base MATOC specifications. Where contract documents and criteria appear to be in conflict, the Contractor shall consult the Contracting Officer (CO) or Administrative Contracting Officer (ACO), as applicable, for clarification before beginning any work. The Contractor shall maintain the capability to provide quick response for this work.

Work requirements will vary from site to site as stated in each task order. The Government will provide no materials, equipment, or labor unless explicitly stated.

1.2 EXPLANATION OF CONTRACT AUTHORITY AND RELATIONSHIPS

The U. S. Army Corps of Engineers (USACE), Tulsa District will award and administer this contract and shall be the sole authority to interact contractually with, direct, and provide oversight to the Contractor.

References to any other organization or entity directing, authorizing, approving, or in any other way contractually interacting with the Contractor shall denote such action by the designated representative(s) of the Contracting Officer, USACE, Tulsa District.

1.3 LOCATION

The location of work is primarily inside the U. S. Army Corps of Engineers USACE), Tulsa District (SWT) civil works boundaries, which covers a portion of southern Kansas, the entire state of Oklahoma, and a small portion of northern Texas. However, work may be required in any portion of the area included inside the Southwest Division (SWD) of USACE. See drawings for maps of SWT and SWD.

1.4 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract. Occupancy notifications must be posted in a prominent location in the work area.

Before work is started, arrange with the Contracting Officer (CO) or Administrative Contracting Officer (ACO) a sequence of procedure, means of

SECTION 01 00 00 Page 1 access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

1.5 EXISTING WORK

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

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

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

1.6 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Government Installation and/or other Government property requirements for locating and marking underground utilities. Contact a local utility locating service a minimum of 72 hours prior to excavating to mark utilities, and within sufficient time required if work occurs on a Monday or after an official Federal Government holiday. Verify existing utility locations indicated on contract drawings, within area of work.

Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities or utilities encased in pier structures are discovered. Verify the elevations of existing piping, utilities, and any type of underground or encased obstruction, not indicated or specified to be removed, that is indicated or discovered during scanning in locations to be traversed by piping, ducts, and other work to be conducted or installed. Verify elevations before installing new work closer than the nearest manhole or other structure at which an adjustment in grade can be made.

Notify the ACO at least 96 hours before starting excavation work.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 00 00 Page 2

SECTION 01 30 00

ADDITIONAL ADMINISTRATIVE REQUIREMENTS

07/18

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.

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

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. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Superintendent; G

View Location Map; G

Verification of Site Conditions; G, DO

Progress and Completion Pictures; G

1.3 PROJECT SUPERINTENDENT

1.3.1 Qualifications

Identify as Superintendent an individual within the onsite work organization that is responsible for overall management of all construction and related activities and has the authority to act in all on-site construction matters for the Contractor. The Superintendent shall have 10 years of documented superintendent experience with a minimum of five years documented construction experience on work similar to this contract. The Superintendent shall be assigned no other duties unless stated otherwise in each individual task order. The project superintendent shall maintain a physical presence at the site at all times and is responsible for all construction and related activities at the site, including safety and quality control.

The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent.

The Contracting Officer (CO) or Administrative Contracting Officer (ACO)

SECTION 01 30 00 Page 1 may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

1.3.2 Duties

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

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

1.3.3 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to insure timely completion. Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.4 VIEW LOCATION MAP

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

1.5 VERIFICATION OF SITE CONDITIONS

Before starting any work on each task order, the Contractor shall be responsible for verifying the accuracy of all data and information provided by the Government. The Contractor shall obtain all required measurements, dimensions, etc. and determine the existing conditions of the facilities, structures, and work site. If data and information provided by the Government are inaccurate or existing conditions appear different and affect the proposed construction, the Contractor shall inform the CO or ACO in writing before proceeding with any construction processes, including ordering materials. Work outside the original scope shall be accomplished only at the direction of the CO or ACO through future contract modifications.

For each individual task order the Contractor shall photograph the site(s) and structure(s), including the storage and staging areas, field office areas, and roads in connection with the project to document the pre-construction conditions. One digital copy of all photographs taken shall be furnished to the ACO with the verification of site conditions.

Digital photographs shall be minimum of 9MB (approximately 3500 pixels (horizontal) x 2500 pixels (vertical) for landscape orientation. Color bit depth shall be 24 true color minimum (8 red, 8 green, 8 blue). Resolution shall provide clear digital printed photographs on 8-1/2" x 11" photograph paper stock. If requested by the Contractor and approved by the ACO, digital video documentation may substitute for certain digital still photographs where video provides better documentation. Video will be limited to ACO approved areas and will be on a case-by-case basis only.

1.6 PROGRESS AND COMPLETION PICTURES

Provide monthly, and within one month of the completion of work on each

SECTION 01 30 00 Page 2 task order, digital photographs, quality as stated above. Take a minimum of 20 digital photographs each week throughout each individual task order from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

1.7 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after each task order award, provide the Contracting Officer a single (only one) e-mail address for electronic communications from the Contracting Officer related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The Contracting Officer may also use email to notify the Contractor of site access conditions when emergency conditions warrant, such as tornados or terrorist threats. Multiple email addresses are not allowed.

It is the Contractor's responsibility to make timely distribution of all Contracting Officer initiated e-mail with its own organization including field office(s). Promptly notify the Contracting Officer, in writing, of any changes to this email address.

1.8 ADDITIONAL ADMINISTRATIVE REQUIREMENTS

In addition to all other administrative requirements in both the base MATOC contract and each task order contract, the requirements and conditions listed below shall apply.

1.8.1 Contractor Supply and Use of Electronic Software for Processing Construction Wage Rate Requirements Statute Certified Labor Payrolls

a. The contractor shall use a commercially-available electronic system to process and submit certified payrolls electronically to the Government.

The requirements for preparing, processing and providing certified labor payrolls are established by the Construction Wage Rate Requirements statute.

b. The contractor shall be responsible for obtaining and providing for all access, licenses, and other services required to provide for receipt, processing, certifying, electronically transmitting to the Government, and storing weekly payrolls and other data required for the contractor to comply with the Construction Wage Rate Requirements statute. When the contractor uses an electronic payroll system, the electronic payroll service shall be used by the contractor to prepare, process, and maintain the relevant payrolls and basic records during all work under this construction contract and the electronic payroll service shall be capable of preserving these payrolls and related basic records for the required 3 years after contract completion. The contractor shall obtain and provide electronic system access to the Government, as required to comply with the Construction Wage Rate Requirements over

SECTION 01 30 00 Page 3 the duration of this construction contract. The access shall include electronic review access by the Government contract administration office to the electronic payroll processing system used by the contractor.

c. (c) The contractor's provision and use of an electronic payroll processing system shall meet the following basic functional criteria:

(1) Commercially available;

(2) Compliant with appropriate Construction Wage Rate Requirements statute payroll provisions in the Federal Acquisition Regulation

(FAR);

(3) Able to accommodate the required numbers of employees and subcontractors planned to be employed under the contract

(4) No payroll data shall be entered in RMS 3.0 CM;

(5) demonstrated security of data and data entry rights;

(6) ability to produce contractor-certified electronic versions of weekly payroll data;

(7) ability to identify erroneous entries and track the date/time of all versions of the certified Construction Wage Rate Requirements statute payrolls submitted to the government over the life of the contract;

(8) capable of generating a durable record copy, that is, a CD or DVD and PDF file record of data from the system database at end of the contract closeout. This durable record copy of data from the electronic payroll processing system shall be provided to the Government during contract closeout.

d. All contractor-incurred costs related to the contractor's provision and use of an electronic payroll processing service shall be included in the contractor's price for the overall work under the contract. The costs for compliance with the Construction Wage Rate Requirements statute by using electronic payroll processing services shall not be a separately bid or reimbursed item under this contract.

1.8.2 Equipment Ownership and Operating Expense Schedule

a. This requirement does not apply to terminations. See UAI 5152.249-9000, Basis for Settlement of Proposals, and Federal Acquisition Regulation (FAR) part 49.

b. Allowable costs for construction and marine plant and equipment in sound workable condition owned or controlled and furnished by a contractor or subcontractor at any tier shall be based on actual cost data for each piece of equipment or groups of similar serial and series for which the Government can determine both ownership and operating costs from the contractor's accounting records. When both ownership and operating costs cannot be determined for any piece of equipment or groups of similar serial or series equipment from the contractor's accounting records, costs for that equipment shall be based upon the applicable provisions of Engineer Pamphlet (EP) 1110-1-8, Construction Equipment Ownership and Operating Expense Schedule, Region VI. Working

SECTION 01 30 00 Page 4 conditions shall be considered to be average for determining equipment rates using the schedule unless specified otherwise by the contracting officer. For equipment not included in the schedule, rates for comparable pieces of equipment may be used or a rate may be developed using the formula provided in the schedule. For forward pricing, the schedule in effect at the time of negotiations shall apply. For retroactive pricing, the schedule in effect at the time the work was performed shall apply.

c. Equipment rental costs are allowable, subject to the provisions of FAR 31.105(d)(ii) and FAR 31.205-36. Rates for equipment rented from an organization under common control, lease-purchase arrangements, and sale-leaseback arrangements, will be determined using the schedule, except that actual rates will be used for equipment leased from an organization under common control that has an established practice of leasing the same or similar equipment to unaffiliated lessees.

d. When actual equipment costs are proposed and the total amount of the pricing action exceeds the simplified acquisition threshold (SAT), the contracting officer shall request the contractor to submit either certified cost or pricing data, or partial/limited data, as appropriate. The data shall be submitted on Standard Form 1411, Contract Pricing Proposal Cover Sheet.

1.8.3 Payment for Materials Delivered Off-Site

a. Pursuant to Federal Acquisition Regulation (FAR) 52.232-5, Payments Under Fixed Price Construction Contracts, materials delivered to the contractor at locations other than the site of the work may be taken into consideration in making payments if included in payment estimates and if all the conditions of the General Provisions are fulfilled.

Payment for items delivered to locations other than the work site shall be limited to:

(1) Materials required by the technical provisions; or

(2) Materials that have been fabricated to the point where they are identifiable to an item of work required under this contract; or

(3) Items specifically listed below.

b. Payment for materials delivered off-site shall be made only after receipt of paid invoices listing the value of material and labor incorporated in the items along with a canceled check showing the prime contractor's title to the items delivered off site. Payment for materials delivered off-site shall be limited to the following items:

AS AUTHORIZED BY THE CONTRACTING OFFICER.

1.8.4 Required Insurance (FAR 28.307-2)

The Contractor shall procure and maintain during the entire period of his performance under this contract the following minimum insurance:

a. Workmen's Compensation and Employer's Liability Insurance in compliance with applicable state statutes, with a minimum liability coverage of $100,000.

b. Comprehensive General Liability Insurance for bodily injury in the minimum limits of $500,000 per occurrence. No property damage liability

SECTION 01 30 00 Page 5 insurance is required.

c. Comprehensive Automobile Liability Insurance covering the operation of all automobiles used in connection with the performance of the contract in the minimum limits of $200,000 per person and $500,000 per occurrence for bodily injury and $25,000 per occurrence for property damage.

The Contractor agrees to insert the substance of this clause, including this paragraph, in all subcontracts hereunder.

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION (NOT USED)

SECTION 01 30 00 Page 6

SECTION 01 32 01

PROJECT SCHEDULE

02/15

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. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Periodic Schedule Update; G

Initial Project Schedule; G

Weekly Progress Meeting Minutes

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 01 Page 1

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 "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, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules 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.

SECTION 01 32 01 Page 2

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 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 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 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.4 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. Road closure/opening dates.

d. Dates for floating bulkhead placement/movement by the Government.

c. Initial UHPC mix/mock-up dates.

d. Dates for temporary outages of tainter gates.

SECTION 01 32 01 Page 3

e. Dates for transfer from permanent power to temporary power.

f. Dates for transfer from temporary power to permanent power.

g. Submission, review, and acceptance of features that require design completion.

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

i. Witness Points identified in technical specifications.

j. Start of bridge girder fabrication.

k. Start of deck panel fabrication.

l. Start of crack/spall repair.

m. Start of demolition of piers.

n. Submission and approval of O & M manuals.

o. Submission and approval of as-built drawings.

p. Submission and approval of DD1354 data and installed equipment lists.

q. Equipment testing plan submission.

r. Equipment testing.

s. Performance Verification testing.

t. Other systems testing, if required.

u. UHPC/grout mock-up preparatory meeting.

v. UHPC/grout mock-up completion.

w. Contractor's pre-final inspection.

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

y. Government's pre-final inspection.

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

aa. Final inspection.

3.3.5 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, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

SECTION 01 32 01 Page 4

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

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.6.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.6.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, 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: DOR (for the designer of record);

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

SECTION 01 32 01 Page 5

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

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

a. Code proposed fast track design and construction phases proposed to allow filtering and organizing the schedule by fast track design and 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.6.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 can have no more than one Category of Work Code.

3.3.6.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 00 QUALITY CONTROL.

An activity can have only one Feature of Work Code.

SECTION 01 32 01 Page 6

3.3.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

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

3.3.7.1 Project Start Date Milestone and Constraint

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

3.3.7.2 End Project Finish Milestone and Constraint

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

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

3.3.7.3 Interim Completion Dates and Constraints

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

3.3.7.3.1 Start Phase

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

3.3.7.3.2 End Phase

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

3.3.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs.

Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop Seasonal Calendar(s) and assign to seasonally affected activities as applicable.

If an activity is weather sensitive it should be assigned to a calendar

SECTION 01 32 01 Page 7 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 adverse weather delay work days provided in the Special Contract Requirements.

Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends.

3.3.9 Open Ended Logic

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

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

3.3.10 Default Progress Data Disallowed

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

3.3.11 Out-of-Sequence Progress

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

3.3.12 Added and Deleted Activities

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

3.3.13 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.14 Leads, Lags, and Start to Finish Relationships

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

a. Leads (negative lags) are prohibited.

SECTION 01 32 01 Page 8

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

3.3.15 Retained Logic

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

3.3.16 Percent Complete

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

3.3.17 Remaining Duration

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

3.3.18 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.18.1 As-Built Drawings

If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than 1.5% of the present contract value, up to $300,000. Activity will be declared 100 percent complete upon the Government's approval.

3.3.18.2 O & M Manuals

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

3.3.19 Early Completion Schedule and the Right to Finish Early

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

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

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

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

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 Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. 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 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

SECTION 01 32 01 Page 10

Quality Control Report for an activity start or finish.

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, 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 and file name. Each schedule must have a unique 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. Provide two set(s) of hardcopy reports. The following lists typical reports that will be requested:

SECTION 01 32 01 Page 11

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 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 dates, and contract completion dates.

3.5.4.3 Critical Path

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

SECTION 01 32 01 Page 12

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.

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.