A.03.09 Amendment Package 0002 Specifications and Drawings.pdf

Phase II Redevelopment Site - Martin, KY Amendment No. 0002

RTA SOLICITATION NO.: W9123720B0002

SECTION TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

SECTION 00 80 00

SPECIAL CONTRACT REQUIREMENTS

PART 1 GENERAL

1.1 COMMENCEMENT, PROSECUTION, AND COMPLETION OF WORK

1.2 SUBMITTALS

1.3 LIQUIDATED DAMAGES--CONSTRUCTION

1.4 DOCUMENT SECURITY

1.4.1 For Official Use Only (FOUO)

1.5 SECURITY REQUIREMENTS

1.6 AT/OPSEC REQUIREMENTS

1.7 RECORDKEEPING AND REPORTING

1.8 CONTRACT DRAWINGS AND SPECIFICATIONS

1.9 LAYOUT OF WORK

1.10 WAGE RATES

1.11 CONTRACTOR SUPPLY AND USE OF ELECTRONIC SOFTWARE FOR PROCESSING

WAGE RATE REQUIREMENTS STATUTE CERTIFIED LABOR PAYROLLS

1.12 PERFORMANCE OF WORK BY CONTRACTOR

1.13 REQUIRED INSURANCE

1.14 QUANTITY SURVEYS

1.15 PERFORMANCE EVALUATION OF CONTRACTOR

1.16 EQUIPMENT OWNERSHIP AND OPERATING EXPENSE SCHEDULE

1.17 AVAILABILITY AND USE OF UTILITY SERVICES

1.17.1 Government Furnished Utility Services

1.17.2 Contractor Installation of Utility Service

1.18 PROGRESS SCHEDULE

1.18.1 Schedule Preparation

1.19 PAYMENT

PART 2 PRODUCTS (NOT APPLICABLE)

PART 3 EXECUTION (NOT APPLICABLE)

-- End of Section Table of Contents --

Enclosure No. DOCUMENT 00 80 00 Page 1

Enclosure No. 2 brian.polak Text Box

THIS PAGE INTENTIONALLY LEFT BLANK

Enclosure No. DOCUMENT 00 80 00 Page 2 brian.polak

SECTION 00 80 00

SPECIAL CONTRACT REQUIREMENTS

PART 1 GENERAL

1.1 COMMENCEMENT, PROSECUTION, AND COMPLETION OF WORK

Comply with the Contract Clause FAR 52.211-10.

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only or as otherwise designated. The following shall be submitted in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Employees ; G|SM

Investigation Package for Contractor and Subcontractor Employees ;

G|SM

1.3 LIQUIDATED DAMAGES--CONSTRUCTION

Comply with the Contract Clause FAR 52.211-12. These liquidated damages are in addition to excess costs of repurchase under the Termination clause

FAR 52.249-10 DEFAULT (FIXED-PRICE CONSTRUCTION).

1.4 DOCUMENT SECURITY

Contractors working for and on USACE projects shall provide the appropriate physical security for all related items as detailed/prescribed in AR 380-5, dated 29 September 2000.

1.4.1 For Official Use Only (FOUO)

For Official Use Only (FOUO): The unauthorized disclosure of the information contained in the attached documents is forbidden to protect the Government's interest in compliance with program effectiveness under AR 380-5 and as follows:

a. During working hours, reasonable steps shall be taken to minimize risk of access by unauthorized personnel. After working hours, FOUO information can be stored in unlocked containers, desks or cabinets if U.S. Government or U.S. Government-contract building security is provided. If U.S. Government-contract building security is not zprovided, FOUO information must be stored in locked desks, file cabinets, bookcases, or similar locked containers.

b. FOUO documents and material can be transmitted via first class mail, parcel post, or, for bulk shipments, fourth class mail.

Electronic transmission of FOUO information by voice, data, facsimile or similar means, shall be by approved secure communications systems whenever possible. (AR 380-5 (dated 29 September 2000))

c. Record copies of FOUO documents shall be disposed of in accordance

Enclosure No. DOCUMENT 00 80 00 Page 3 brian.polak with AR 25-400-2. Non-record FOUO documents shall be destroyed by shredding or tearing into pieces and discarding the pieces in regular trash containers.

1.5 SECURITY REQUIREMENTS

All Contractors and subcontractor employee(s) working on this contract who require access in and/or around any Huntington District facilities shall receive authorization to be on site at these facilities based upon a favorable background investigation in accordance with "Homeland Security Presidential Directive 12: Policy for a Common Identification Standard for Federal Employees and Contractors" (HSPD 12). The Huntington District Security Management Office shall submit contractor(s) personal information (List of Employees) to complete the basic background investigation in order to make a recommendation to the Contracting Officer of an employee's suitability for work on Government property. The Procuring Contracting Officer (PCO) has the right to deny any contractor or subcontractor employee from working on the contract based upon the results of the background investigation provided by the Huntington District Security Management Office. The Government, Contractor, and subcontractors shall not permit any employee(s) access to drawings, blueprints, records, photos, sites, or projects until the Huntington District Security Management Office has completed an Operations Security (OPSEC) review of such items and determined they can be released.

For Contracts In Excess Of 1 Year Duration The Documents Listed Below Are Required:

The documents listed below are required (Investigation Package for Contractor and Subcontractor Employees):

SF 85, Questionnaire for Non-Sensitive Positions (see http://www.opm.gov/forms/ to print form). FD 258, Contractor Fingerprint Card (one card for digital prints, two for ink prints) (NOTE: a trained/qualified individual must take prints, ORI block on the FD 258 must be USOPM000Z) (Contractor Fingerprint Cards (FD-258) may be obtained by Contracting Division by contacting the Huntington District Security Management Office).

Contractor shall report any changes in personnel, or at any time conditions change at least 5 working days prior to individual(s) need to have access to the site. The Contractor shall provide the same information as listed above for all new employees.

Following submission of paperwork, the Huntington District Security Management Office will conduct an initial criminal check based upon the information provided. If there are no issues, the Huntington District Security Management Office will make recommendations to the PCO or their Designated Representative. The Huntington District Security Management Office cannot give approval due to unfavorable report(s). The Huntington District Security Management Office shall coordinate with Office of Counsel and will jointly make recommendations to the PCO and/or the Designated Representative should a background investigation come back with derogatory information. The PCO will make the determination whether to allow the Contractor personnel to work on the site based on Security and Office of Counsel recommendations, and the PCO will advise the Contractor of the decision.

Foreign Nationals: The Contractor shall provide the package listed above, Enclosure No. DOCUMENT 00 80 00 Page 4 brian.polak as well as, additional materials noted below for all Foreign Nationals.

In accordance with Engineering Regulation 380-1-18, "Technology Transfer, Disclosure of Information and Contacts with Foreign Representatives" dated 1 August 1996, Section 4, all foreign nationals who work on Corps of Engineers' contracts shall be approved by the Headquarters US Army Corps of Engineers (HQ USACE) Foreign Disclosure Officer before beginning work on this contract; this regulation includes subcontractor employees. The Contractor shall submit to the Security Management Office, the names of all foreign nationals proposed for performance under this contract, along with documentation to verify legal admittance into the United States. Such documentation shall include at least one of the following: a U.S.

passport, Certificate of U.S. Citizenship (INS Form N-560 or N-561), Certificate of Naturalization (INS Form N-550 or N-570), Alien Registration Card with photograph (INS Form I-151 or I-551), Employment Authorization Card (INS Form I-688A), etc.

In order to assure forms are properly completed, and to minimize time delays, the Contractor is encouraged to work closely with the Huntington District Security Management Office. The Government will return for correction incomplete forms, illegible forms, etc., which will delay the contractor/subcontractor from beginning work.

Security requirements are subject to change in accordance with HSPD-12, Office of Personnel Management, regulation or policy changes, etc. The Government will add any changes to security requirements by modification to the contract.

The Contractor shall contact the Huntington District Security Management Office by phone, letter, or e-mail at the following numbers/addresses:

CELRH-SM

502 Eighth Street Huntington, WV 25701

Scott E. Grandon, phone (304) 399-5661;

email scott.e.grandon@usace.army.mil

Stephen R. Curry, phone (304) 399-5695;

e-mail stephen.r.curry@usace.army.mil

Matthew D. Green, phone (304) 399-5294;

e-mail matthew.d.green@usace.army.mil

Sandra L. Hardwick, Phone (304) 399-5612;

e-mail Sandra.L.Hardwick@usace.army.mil

1.6 AT/OPSEC REQUIREMENTS

Contractors are required to comply with the following: Pre-screen candidates using E-Verify Program. The Contractor must pre-screen candidates using the E-verify Program (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Vendor must ensure that the candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible candidates must be provided to the Contracting Officer's Representative no later than three business days after the initial

Enclosure No. DOCUMENT 00 80 00 Page 5 brian.polak contract award. When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, with the designated Government representative. This Form will be provided to the Contracting Officer and shall become part of the official contract file.

1.7 RECORDKEEPING AND REPORTING

The Contractor shall maintain a roster of all background investigation requests. The roster shall be maintained and available for inspection by the Contracting Officer upon request. A copy will also be provided to the Contracting Officer on a monthly basis. At a minimum, the roster shall include the following information:

Full Name of Employee Employer Date Phase I Background Check Requested Date of Phase I Approval/Disapproval Date Phase II Background Investigation Requested Date of Phase II Approval/Disapproval Date Foreign National/Recent U.S. Citizen Check Requested Date Foreign National/Recent U.S. Citizen Check Approval/Disapproval

Other information may also be included on the roster. However, the Contractor is responsible for protecting all sensitive personal information such as social security numbers, birth dates, etc.

1.8 CONTRACT DRAWINGS AND SPECIFICATIONS

Comply with Contract Clause DFARS 252.236-7001. Contractor shall field verify all dimensions on drawings prior to commencing design and layout of the work.

1.9 LAYOUT OF WORK

See FAR Clause 52.236-17.

1.10 WAGE RATES

Wage rates shall be in accordance with Contract Clause, WAGE RATE

REQUIREMENTS (CONSTRUCTION) (FAR 52.222-6).

1.11 CONTRACTOR SUPPLY AND USE OF ELECTRONIC SOFTWARE FOR PROCESSING WAGE

RATE REQUIREMENTS STATUTE CERTIFIED LABOR PAYROLLS

The Contractor is encouraged to 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 Wage Rate Requirements statute.

If the Contractor elects to use an electronic payroll processing system, then 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 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

Enclosure No. DOCUMENT 00 80 00 Page 6 brian.polak 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 three years after contract completion. If the Contractor chooses to use an electronic payroll system, then the contractor shall obtain and provide electronic system access to the Government, as required to comply with the Wage Rate Requirements over 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.

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 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) capable of producing an Excel spreadsheet-compatible electronic output of weekly payroll records for export in an Excel spreadsheet to be imported into the contractor's Quality Control System (QCS) version of Resident Management System (RMS), that in turn shall export payroll data to the Government's RMS;

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

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 Wage Rate Requirements statute by using electronic payroll processing services shall not be a separately bid or reimbursed item under this contract.

1.12 PERFORMANCE OF WORK BY CONTRACTOR

The Contractor shall perform on the site, and with its own organization, work equivalent to at least 15 percent of the total amount of work to be performed under the contract. This percentage may be reduced by a supplemental agreement to this contract if, during performing the work, the Contractor requests a reduction and the Contracting Officer determines that the reduction would be to the advantage of the Government.

Enclosure No. DOCUMENT 00 80 00 Page 7 brian.polak

1.13 REQUIRED INSURANCE

In reference to Contract Clause, INSURANCE--WORK ON A GOVERNMENT INSTALLATION, FAR 52.228-5, the Contractor shall procure and maintain, during the entire period of his performance under this contract, the following minimum insurance:

a. Workmen's Compensation. Workmen's Compensation and Occupational Disease Coverage, as legally required by the State wherein the work is being performed.

b. Comprehensive Automobile Liability Insurance. Bodily injury coverage with minimum limits of $200,000 per person and $500,000 per occurrence, and $100,000 per occurrence for property damage shall be required.

c. Comprehensive General Liability Insurance. Bodily injury coverage with minimum limit of $500,000 per occurrence shall be required.

Property damage coverage with a minimum limit of $100,000 per occurrence shall be required.

d. Before commencing work under this contract, the Contractor shall certify to the Contracting Officer, in writing, that the required insurance has been obtained. The policies evidencing the required insurance shall contain an endorsement to the effect that any cancellation or any material change adversely affecting the Government's interest shall not be effective (1) for such period as the laws of the State in which this contract is to be performed prescribe or (2) until 30 calendar days after the insurer or the Contractor gives written notice to the Contracting Officer, whichever period is longer.

1.14 QUANTITY SURVEYS

a. Quantity surveys shall be conducted, and the data derived from these surveys shall be used in computing the quantities of work performed and the actual construction completed and in place.

b. The Contractor shall conduct an initial baseline field survey of existing conditions and field surveys for Excavation, Rock Excavation, and Fill Placement for any periods for which progress payments are being requested. All of these surveys shall be conducted under the direction of a representative of the Contracting Officer, unless the Contracting Officer waives this requirement in a specific instance.

Using these surveys, the Government shall make such computations as are necessary to determine the quantities of work performed for which progress payments are requested. The computations used for payment shall be made as follows:

For use in tracking the progress of Construction and for estimating/verifying the quantities submitted for the Contractor's request for Progress Pavements, the Contractor shall provide a MicroStation drawing model file with Cross Sections taken at 20 foot intervals along the proposed roadway alignments and other areas that proposed Excavation, Rock Excavation, and Fill Placement is to occur including but not limited to the Green Space and Mayo Hollow areas. Promptly upon completing each survey, the Contractor shall show the current limits of construction as surveyed in the Cross Section Model File depicting the surveyed

Enclosure No. DOCUMENT 00 80 00 Page 8 brian.polak areas. With each new survey, a MicroStation Level shall be created and named in a way to describe the survey, i.e. "Request for Progress Payment - October 2020". This level shall then be used to depict the line work for the surveyed ground conditions as well as for any text labels for the measured areas and computed volumes.

Starting with the line work from the baseline survey or from the previous pay request survey's line work, each subsequent survey end area volumes in cubic yards shall be computed from the cross sections at 20 foot intervals. These volumes will be used as the basis of payment for the work as constructed for each progress payment.

Survey Deliverables: For each subsequent survey and/or payment request, the Contractor shall provide to the Government the updated Cross Section Model file and all of the data used to generate the new line work. This survey data is not limited to, but shall include copies of all field notes, all surveyed point files in PNEZD ASCII format, any breakline data used for surface creation, and any surfaces (DTM's), used to generate the line work for each request for payment.

All survey data to be provided in horizontal coordinates based on Kentucky Coordinate System South Zone NAD83 and vertical datum based on NAVD88 and with a unit definition of US Survey Feet with a tenth of a foot minimum accuracy and meeting state jurisdictional standards, whichever is more stringent. .

c. Survey personnel. All quantity surveys required by the Contractor shall be made by personnel of a professional engineering and/or surveying firm experienced in the practice of such work. The survey personnel shall have the following minimum qualifications.

(1) Party Chief shall be proficient in survey operations and methodologies and provide supervision of all survey crew activities.

( 12) Instrument person shall be proficient in the operation of precise and semi-precise instruments including total stations, levels, and automated data collectors , and GPS units . If applicable instrument person shall prepare all survey notes in a firm and legible manner.

(2) Rodman and/or chainman. At least one rodman and/or one chainman, with a minimum of six months prior experience each, shall be assigned to each survey party.

d. The Contractor shall maintain complete and accurate field notes, sketches, recordings and computations required in establishing the necessary horizontal and vertical control. All survey data shall be recorded in accordance with accepted standards and as approved by the Contracting Officer. All the above data shall be available at all times during the progress of the work for ready examination and use by the Contracting Officer. Upon request of the Contracting Officer, the Contractor shall furnish a copy of above survey data.

Enclosure No. DOCUMENT 00 80 00 Page 9 brian.polak

1.15 PERFORMANCE EVALUATION OF CONTRACTOR

It is the Corps' standard operating procedure that the Contracting Officer evaluate the Contractor's performance and prepare a performance report using the web-based application CPARS (Contractor Performance Assessment Reporting System) for construction contracts of 700,000 or more. After an evaluation (interim or final) is written by the Corps, the Contractor has a 60-day period to access, review and comment on the evaluation.

Accessing and using CPARS requires having specific software, called PKI certification, installed on the user's computer. The certification, a Department of Defense requirement, was implemented to provide security in electronic transactions. The certification software could cost approximately $100-$125 per certificate, per year and is purchased from an External Certificate Authorities (ECA) vendor. Current information about the PKI certification process and for contacting vendors can be found on the web site: http://www.cpars.gov. The Contractor is encouraged to participate in the performance evaluation process, access to CPARS and PKI certification is the sole responsibility of the Contractor.

1.16 EQUIPMENT OWNERSHIP AND OPERATING EXPENSE SCHEDULE

This section does not apply to terminations. See Federal Acquisition Regulation (FAR) part 49.

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 II. Working 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.

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.

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.

Enclosure No. DOCUMENT 00 80 00 Page 10 brian.polak

1.17 AVAILABILITY AND USE OF UTILITY SERVICES

1.17.1 Government Furnished Utility Services

The Government will not provide any utilities under this contract.

1.17.2 Contractor Installation of Utility Service

The Contractor, at its expense and in a workman-like manner satisfactory to the Contracting Officer, shall install and maintain all necessary temporary connections and distribution lines, and all meters required to measure the amount of each utility used for the purpose of determining charges. Before final acceptance of the work by the Government, the Contractor shall remove all the temporary connections, distribution lines, meters, and associated paraphernalia.

1.18 PROGRESS SCHEDULE

1.18.1 Schedule Preparation

Prepare schedules in accordance with Section 01 32 01.00 10 PROJECT

SCHEDULE.

1.19 PAYMENT

No separate payment will be made for the work covered under this section and all costs in connection therewith shall be included in the applicable contract price to which the work pertains.

PART 2 PRODUCTS (NOT APPLICABLE)

PART 3 EXECUTION (NOT APPLICABLE)

-- End of Section --

Enclosure No. DOCUMENT 00 80 00 Page 11 brian.polak

THIS PAGE INTENTIONALLY LEFT BLANK

Enclosure No. DOCUMENT 00 80 00 Page 12 brian.polak

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

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 Procurement Activities

3.3.4 Mandatory Tasks

3.3.5 Government Activities

3.3.6 Standard Activity Coding Dictionary

3.3.6.1 Workers Per Day (WRKP)

3.3.6.2 Responsible Party Coding (RESP)

3.3.6.3 Area of Work Coding (AREA)

3.3.6.4 Modification Number (MODF)

3.3.6.5 Bid Item Coding (BIDI)

3.3.6.6 Phase of Work Coding (PHAS)

3.3.6.7 Category of Work Coding (CATW)

3.3.6.8 Feature of Work Coding (FOW)

3.3.7 Contract Milestones and Constraints

3.3.7.1 Project Start Date Milestone and Constraint

3.3.7.2 End Project Finish Milestone and Constraint

3.3.7.3 Interim Completion Dates and Constraints

3.3.7.3.1 Start Phase

3.3.7.3.2 End Phase

3.3.8 Calendars

3.3.9 Open Ended Logic

3.3.10 Default Progress Data Disallowed

3.3.11 Out-of-Sequence Progress

3.3.12 Added and Deleted Activities

3.3.13 Original Durations

3.3.14 Leads, Lags, and Start to Finish Relationships

Enclosure No. SECTION 01 32 01.00 10 Page 1

Enclosure No 3 brian.polak

3.3.15 Retained Logic

3.3.16 Percent Complete

3.3.17 Remaining Duration

3.3.18 Cost Loading of Closeout Activities

3.3.18.1 As-Built Drawings

3.3.18.2 O & M Manuals

3.3.19 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.5.1 Weather

3.8.5.2 Unusually Severe Weather

3.8.6 Anticipated Adverse Weather Days

3.8.7 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 RMS/QCS

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

3.13 PAYMENT

-- End of Section Table of Contents --

Enclosure No. SECTION 01 32 01.00 10 Page 2 brian.polak

SECTION 01 32 01.00 10

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

PART 2 PRODUCTS

2.1 SOFTWARE

The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.

Enclosure No. SECTION 01 32 01.00 10 Page 3 brian.polak

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.

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 or Contracting Officer's Representative (COR).

Enclosure No. SECTION 01 32 01.00 10 Page 4 brian.polak

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 or Contracting Officer's Representative (COR) directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer or Contracting Officer's Representative (COR) 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 or Contracting Officer's Representative (COR) 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. Submission, review and acceptance of design packages.

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

d. Long procurement activities

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

Enclosure No. SECTION 01 32 01.00 10 Page 5 brian.polak

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

h. Contractor's pre-final inspection.

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

j. Government's pre-final inspection.

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

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

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

Enclosure No. SECTION 01 32 01.00 10 Page 6 brian.polak 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).

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.

Enclosure No. SECTION 01 32 01.00 10 Page 7 brian.polak

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

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.

Enclosure No. SECTION 01 32 01.00 10 Page 8 brian.polak

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 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 Paragraph ANTICIPATED ADVERSE WEATHER DAYS. 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.

Enclosure No. SECTION 01 32 01.00 10 Page 9 brian.polak

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.

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, Enclosure No. SECTION 01 32 01.00 10 Page 10 brian.polak cost load the "Submission and approval of 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 approval.

3.3.18.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less than $50,000 $10,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 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.