Amendment 06.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04 EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

The Solicitation for Air Traffic Control Tower Kelly Field; Lackland Air Force Base, Texas is amended as follows.

See SF30 Continuation Sheet(s)

NOTE: Proposal Receipt date is 17 February 2022 at to 2:00 p.m., CT, as previously announced.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 2

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

16C. DATE SIGNED

BY

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

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X 9A. AMENDMENT OF SOLICITATION NO.

W9126G22R0002

X 9B. DATED (SEE ITEM 11)

17-Dec-2021

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

3 -Feb- 2022

CODE

US ARMY ENGINEER DISTRICT, FORT WORTH

ATTN: CESWF-CT

819 TAYLOR ST, ROOM 2A19

P.O. BOX 17300

FORT WORTH TX 76102-0300

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODE CODE

EMAIL: TEL:

W9126G22R0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

CHANGES TO SOLICITATION W9126G22R0002

CHANGES TO THE SPECIFICATIONS

1. Replacement Sections - Replace the following sections with the accompanying new sections of the same number and title, bearing the notation W9126G22R0002-0006.

01 00 00.00 44 CONSTRUCTION SCHEDULE

01 11 00 SUMMARY OF WORK

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

End of Summary of Changes

Kelly Airfield Air Traffic Control Tower KA22ATCT

SECTION 01 00 00.00 44

CONSTRUCTION SCHEDULE

AMENDMENT 0006

PART 1 GENERAL

1.1 SCHEDULE

Commence, prosecute, and complete the work under this contract in accordance with the following schedule and Section 00 73 00 SPECIAL

CONTRACT REQUIREMENTS; CLAUSES, COMMENCEMENT, PROSECUTION AND COMPLETION

OF WORK and LIQUIDATED DAMAGES:

<AM#0006>

Item of Work Commencement of

Work (Calendar days)

Completion of Work

(Calendar days)

Liquidated Damages per calendar days

(1) PHASE I

CONSTRUCTION

All work, including O&M Manuals and Final Record Drawings,to construct Air Traffic Control Tower (ATCT).

Upon Contractor receipt of Notice to Proceed (NTP)

540 600 $1,298.54 $1,168.69

(2) PHASE II

DEMOLITION All work to demolish and dispose of B1160 Existing Control Tower.

Within 90 calendar days after Government acceptance of Phase I (construction).

120 $356.25

</AM#0006>

Liquidated Damages:

a. Liquidated damages for individual items of work will not be combined.

Only the rate of the affected item of work will be assessed.

b. Liquidated damages are not accumulative for multiple phases of work.

Operation and Maintenance Manuals

a. See Section 01 78 00 CLOSEOUT SUBMITTALS, paragraph OPERATION AND MAINTENANCE MANUALS for requirements and withholding amount to ensure completion of O&M Manuals.

SECTION 01 00 00.00 44 Page 1

W9126G22R0002-0006

Record Drawings

a. See Section 01 78 00 CLOSEOUT SUBMITTALS, paragraph titled RECORD DRAWINGS for requirements and for withholding amount to ensure completion of record drawings.

1.1.1 Testing of Heating and Air-Conditioning Systems

The times stated for completion of this project includes all required testing specified in appropriate specification sections of heating, air conditioning and ventilation systems including HVAC Commissioning.

Exception: boiler combustion efficiency test, boiler full load tests, cooling tower performance tests, and refrigeration equipment full load tests, when specified in the applicable specifications, shall be performed in the appropriate heating/cooling season as determined by the Contracting Officer.

1.2 TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER (OCT 1989)

(ER 415-1-15)(52.0001-4038 1/96)

a. This provision specifies the procedure for determination of time extensions for unusually severe weather in accordance with the contract clause FAR 52.249-10 entitled "DEFAULT: (FIXED PRICE CONSTRUCTION)."

In order for the Contracting Officer to award a time extension under this clause, the following conditions must be satisfied:

(1) The weather experienced at the project site during the contract period must be found to be unusually severe, that is, more severe than the adverse weather anticipated for the project location during any given month.

(2) The unusually severe weather must actually cause a delay to the completion of the project. The delay must be beyond the control and without the fault or negligence of the contractor.

b. The following schedule of monthly anticipated adverse weather delays due to precipitation and temperature is based on National Oceanic and Atmospheric Administration (NOAA) or similar data for the project location and will constitute the base line for monthly weather time evaluations. The contractor's progress schedule must reflect these anticipated adverse weather delays in all weather dependent activities. Wind is not considered in the Monthly Anticipated Adverse Weather Calendar Day Schedule.

MONTHLY ANTICIPATED ADVERSE WEATHER DELAY

WORK DAYS BASED ON (5) DAY WORK WEEK

SAN ANTONIO, TX AREA (FORT SAM HOUSTON, KELLY, LACKLAND,

BROOKS, AND RANDOLPH AFB'S AND RESERVE CTRS AT SAN ANTONIO)

JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC

2 3 4 3 4 6 3 4 5 5 5 3

c. Upon receipt of the Notice to Proceed (NTP) and continuing throughout the contract, the contractor will record on the daily CQC report, the occurrence of adverse weather and resultant impact to normally

SECTION 01 00 00.00 44 Page 2 scheduled work. Actual adverse weather delay days must prevent work on critical activities for 50 percent or more of the contractor's scheduled work day.

d. The number of actual adverse weather delay days shall include days impacted by actual adverse weather (even if adverse weather occurred in previous month), be calculated chronologically from the first to the last day of each month, and be recorded as full days. If the number of actual adverse weather delay days exceeds the number of days anticipated in paragraph "b", above, the Contracting Officer will convert any qualifying delays to calendar days, giving full consideration for equivalent fair weather work days, and issue a modification in accordance with the contract clause entitled "Default (Fixed Price Construction)."

1.3 CONSTRUCTION PHASING

1.3.1 Phasing Requirements

To maintain a fully operational ATCT at JBSA-Lackland, this project requires construction activities to be performed in 2 phases. Phase 1 will include site development activities and construction of the new ATCT;

Phase 2 will be the demolition of the existing ATCT.

Phase 1: Following receipt of NTP, this phase includes all work required to construct the new ACTC. Refer to Sheet C-0001 for additional phasing notes.

Phase 2: Following a 90 calendar day transition period after Government acceptance of the new ACTC, contingent on the new ACTC being fully operational, the Government will turn over the existing ATCT (Building 1160) to the contractor for demolition and abatement. Contractor shall be responsible for the disposal of all furniture and other items remaining in building 1160 upon turnover, as part of the demolition effort.

1.4 WORK RESTRICTIONS

Refer to Section 01 14 00 Work Restrictions for additional restrictions.

1.4.1 Working Hours

Normal working hours are Monday through Friday, 0630 to 1700 hours, unless otherwise indicated at the preconstruction conference. Requests to work at times other than the stated working hours, including scheduled utility outages discussed below, shall be submitted to the Contracting Officer for approval. Contractor shall not work outside of the above stated working hours without prior written approval of the Contracting Officer.

1.4.2 Security Requirements

1.4.2.1 Installation Entrance Requirements

Entrance requirements to the Installation are specified in Section 01 35

17.00 44 SPECIAL PROJECT PROCEDURES FOR LACKLAND AIR FORCE BASE.

For the duration of this Contract, the Contractor shall anticipate a delay of 30 minutes or more to access Lackland AFB. These delays are due to increased security precautions, including the checking of vehicle

SECTION 01 00 00.00 44 Page 3 occupants' IDs, vehicle manifests, and the searching of all vehicles. Any general or specific threat to the safety of those working or living at the Installation could result in longer waiting times at the access points to the Installation.

The following are the minimum requirements for contractor employees entering Lackland AFB:

a. One form of picture ID.

b. A memo from the construction company on their letterhead stating the reason for entry, contract number, and the location at Lackland AFB where the jobsite is located.

c. All delivery trucks must have a bill of lading and delivery truck drivers must have a picture ID.

1.4.3 Identification of Employees

The Contractor shall be responsible for furnishing to each employee, and for requiring each employee engaged on the work to display, identification as approved and directed by the Contracting Officer. Badging of all employees and subcontract employees shall be in accordance with the badging process requirements specified in Section 01 35 17.00 44 SPECIAL PROJECT PROCEDURES FOR LACKLAND AFB. Prescribed identification shall immediately be delivered to the Contracting Officer for cancellation upon release of any employee. When required, the Contractor shall obtain and provide fingerprints of persons employed on the project. Contractor and subcontractor personnel shall wear identifying markings on hard hats clearly identifying the company for whom the employee works.

Contractor personnel shall wear visible Contractor-furnished employee identification badges while physically on the Installation. Each badge shall include, as a minimum, the company name, employee name, photograph, Contract Title, Contract Number, and the expiration date of the badge.

1.5 UTILITIES

1.5.1 Payment for Utility Services

Utilitiy availability and Payment For Utility Services are specified in Section 01 50 00.17 44 TEMPORARY CONSTRUCTION FACILITIES FOR LACKLAND AFB.

1.5.2 Coordination

For Contractor Telephone And Internet Service, the Contractor shall coordinate with local phone company for contractor telephone and internet service during construction.

1.5.3 Outages

The Contractor shall coordinate all requests for utility outages with the Contracting Officer and local utility provider (where applicable) in writing 14 days prior to date of requested outage:

a. Water, gas, steam, and sewer outages shall be held to a maximum duration of 4 hours unless otherwise approved in writing.

b. Electrical outages shall have a maximum duration of 4 hours.

SECTION 01 00 00.00 44 Page 4

c. All utility outages shall be scheduled only on Saturdays, Sundays, or holidays unless specific approval is otherwise received.

See Section 01 35 17.00 44 - SPECIAL PROJECT PROCEDURES FOR LACKLAND AIR FORCE BASE for additional information regarding UTILITIES.

1.6 PAPERLESS CONTRACT SUBMISSION

a. GENERAL INFORMATION ON PAPERLESS CONTRACT SUBMISSION

The goal is to reduce waste, decrease time, decrease associated costs, and to streamline most file transmission procedures.

b. METHODS OF DIGITAL SUBMISSION

This contract shall use digital submission methods to the greatest extent practicable. Acceptable methods are as follows, in order of precedence:

(1) RMS - will be used to the greatest extent practicable. Some items may not be submittable via RMS due to program constraints. Those items shall use an alternate method. All ENGR 4025’s shall be generated and submitted in RMS.

(2) Secure, Password Protected Web-Based System Access must be allowed and approved by the Government Representative. Access must be allowed and approved by the Government Representative.

This method shall not be used for security sensitive documents.

(3) E-mail – Items not submitted via RMS, as discussed above, shall be submitted via e-mail, if possible. E-mail limitations for file size must be considered prior to submission.

(4) CD/DVD – Will be accepted if no other method is possible and upon prior approval.

c. ITEMS TO BE SUBMITTED VIA HARDCOPY

Product samples, color boards, and any other item not feasible to submit digitally, shall be submitted hard copy. ENGR 4025 shall be submitted digitally always. The Government reserves the right to request hard copy submission on any item, if deemed necessary.

Contractor shall be prepared to provide requested hard copy at any time.

1.7 CONTRACTOR PERFORMANCE EVALUATIONS

In accordance with the provisions of Subpart 36.201 (Evaluation of Contractor Performance) of the Federal Acquisition Regulation (FAR), construction contractor’s performance shall be evaluated throughout the performance of the contract. The United States Army Corps of Engineers (USACE) follows the procedures outlined in Engineering Regulation 415-1-17 to fulfill this FAR requirement. For construction contracts awarded at or above $750,000.00, the USACE will evaluate contractor’s performance and prepare a performance report using the Contractor Performance Assessment Reporting System (CPARS), which is now a web-based system. After an evaluation (interim or final) is written up by the USACE, the contractor will have the ability to access, review and comment on the evaluation for

SECTION 01 00 00.00 44 Page 5 a period of 60 days. Accessing and using CPARS requires specific software, called PKI certification, which is installed on the user’s computer. The certification is a Department of Defense requirement and was implemented to provide security in electronic transactions. The certification software could cost approximately $110 - $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.csd.disa.mil/

If the Contractor wishes to participate in the performance evaluation process, access to CPARS and PKI certification is the sole responsibility of the Contractor.

1.8 CONTRACTOR PAYROLL RECORD

Contractor shall be required to log payrolls for all their own employees and subcontractors utilizing ENG Form 3180. Each subcontractor requires a separate ENG 3180 for their payrolls. The Contractor shall maintain the ENG 3180, along with the payrolls, on site and available for review by the Contracting Officer's Representative. The ENG 3180's shall be updated weekly as payrolls are submitted. After making copies for their files, the Contractor is required to submit the originals of each week’s payrolls to the Resident Office. Before final payment, the Contractor shall provide the completed ENG 3180’s to the Contracting Officer's Representatives.

1.9 CONTRACTOR SUPPLY and USE OF ELECTRONIC SOFTWARE FOR PROCESSING WAGE

RATE REQUIREMENTS CERTIFIED LABOR PAYROLLS

a. The contractor is required 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.

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

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 Wage Rate Requirements statute payroll provisions in the Federal Acquisition Regulation (FAR);

SECTION 01 00 00.00 44 Page 6

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

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

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

1.10 ADDITIONAL CONTRACTOR PAYROLL RECORD

The Fort Worth District requires the contractor and all sub-contractors to use an electronic payroll system meeting the requirements the above referenced requirements and the following.

a. The Certified Labor Payrolls must be tracked electronically via WEB-based software and all data must be submitted via WEB. Payroll guidelines,"Instructions to Contractors on Contract Labor Requirements, published as "Appendix A, SWFP 1185-1-1" (also known as the Green book), will be provided to advise/inform contractors how these labor provisions will be administered and enforced.

b. The WEB-based software must be capable of downloading data directly from existing electronic payrolls, track workers to ensure that overtime is being paid when overtime status is reached on Government contracts whether on one or multiple contracts or different sub-contractors. The software must track apprentices and journeyman ratios, create and track SF-1444 "Request for Authorization of Additional Classification and Rate", track workers by name/address/with or without Social Security Numbers, allow automated redaction of information appearing on payroll statements for agency response to Freedom of Information Act (FOIA requests), and provide free online training by the software provider to any user of the software.

c. The software must allow fringe benefit statement to track fringe benefits "whether cash or into an approved plan, fund, or program. If the fringe benefits are paid into a plan, fund, or program the company's name (receiving benefits), phone number, and address shall be listed on the Statement of Compliance Form (DD Form 879 or WH-347).

SECTION 01 00 00.00 44 Page 7

d. Software must provide a method of tracking standard and non-standard deductions such as restitution, alimony, child support, and allow for custom entries. Method of tracking must list the deductions on the statement of compliance or be listed as an attachment.

e. The Contractor is required to provide the updated 3180's and notify the Contracting Officer's Representatives weekly by email when the current payrolls are complete and ready for inspection/review on the WEB.

Before final payment, the Contractor shall provide the completed ENG For 3180's and 3 disks (CD/DVD) which include complete copies of the Contractor and sub-contractor's payrolls/attachments, to the Contracting Officer's Representatives.

f. Electronic copies of electronically/manually signed forms/memos/letters such as SF 1413 Statement of Acknowledgement (sub-contractor agreement), SF-1444 "Request for Authorization of Additional Classification and Rate", employee deduction authorization, certification of apprentices and trainees shall be provided to the Contracting Officer's Representative as required by FAR.

1.11 STREET CLOSINGS

The Contractor shall coordinate all requests for street closings with the Contracting Officer in writing 21 days prior to date of requested outage:

a. One lane traffic shall be maintained at all times (except that a total closing may be allowed for specific 8-hour periods).

b. The final street repair shall be completed within 21 calendar days after the start of any street crossing. Any part of the street returned to service prior to final repair shall be maintained smooth with hot-mix cold-lay surface course.

c. Open cuts across paved roads and streets for utility crossings will not be allowed. Utility crossings will be accomplished by boring or jacking procedures only.

1.12 Veterans Employment Emphasis for U.S. Army Corps of Engineers Contracts

In addition to complying with the requirements outlined in FAR Part 22.13, FAR Provision 52.222-38, FAR Clause 52.222-35, FAR Clause 52.222-37, DFARS 222.13 and Department of Labor regulations, U.S. Army Corps of Engineers (USACE) contractors and subcontractors at all tiers are encouraged to promote the training and employment of U.S. veterans while performing under a USACE contract. While no set-aside, evaluation preference, or incentive applies to the solicitation or performance under the resultant contract, USACE contractors are encouraged to seek out highly qualified veterans to perform services under this contract. The following resources are available to assist USACE contractors in their outreach efforts:

U.S. Department of Labor Veterans' Emplyments and Training Service (VETS):

www.dol.gov.vets

Federal Veteran Employment Information:

https://www.fedshirevets.gov/

Veterans Opportunity to Work (VOW) Program:

https://www.benefits.va.gov/vow/

SECTION 01 00 00.00 44 Page 8

U.S> Army Warrior Transition Command Employments Index:

https://wct.army.mil/modules/employers/index.html

Hiring Our Heros:

https://www.uschamberfoundation.org/hiring-our-heroes

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION (NOT USED)

-- End of Section --

SECTION 01 00 00.00 44 Page 9

SECTION 01 11 00

SUMMARY OF WORK

AMENDMENT 0006

PART 1 GENERAL

1.1 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submittals with an "S" are for inclusion in the Sustainability Notebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals Salvage Plan ; G

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

<AM#0006> The work includes construction of a new Air Traffic Control Tower with reinforced concrete pile foundation and slab floor and masonry walls at the lower level. This project also includes an elevator, a catwalk surrounding the tower cab as well as utilities, site improvements, pavements, special foundations, a backup power generator and all other work necessary to provide a complete and usable facility. Associated demolition will include two facilities, includes the existing ATCT Building #1160 , and Building #1161 . </AM#0006>

1.2.2 Location

The work is located on Kelly Annex at Lackland Air Force Base, Joint Base San Antonio, Texas.

1.3 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.

Contact 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 a 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 are discovered. Verify the elevations of existing piping, utilities,and any type of underground 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 nearest manhole

SECTION 01 11 00 Page 1 or other structure at which an adjustment in grade can be made.

1.3.1 Notification Prior to Excavation

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

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

AMENDMENT 0006

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. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance to Section 01 33 29 SUSTAINABILITY REPORTING. 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.

SECTION 01 32 01.00 10 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.00 10 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. Submission, review and acceptance of features require design completion

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

d. Long procurement activities

SECTION 01 32 01.00 10 Page 3

e. Submission and approval of O & M manuals.

f. Submission and approval of as-built drawings.

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

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

i. Submission of TAB specialist design review report.

j. Submission and approval of fire protection specialist.

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

l. Air and water balancing.

m. Building commissioning - Functional Performance Testing.

n. Controls testing plan submission.

o. Controls testing.

p. Performance Verification testing.

q. Other systems testing, if required.

r. Contractor's pre-final inspection.

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

t. Government's pre-final inspection.

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

v. Final inspection.

3.3.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-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:

SECTION 01 32 01.00 10 Page 4

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

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.

SECTION 01 32 01.00 10 Page 5

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.00 10 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.

SECTION 01 32 01.00 10 Page 6

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 Received," which must have a "Start On" constraint date equal to the date that the NTP is received.

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 sSeasonal 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 section 01 00 00.00 44. 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 .

SECTION 01 32 01.00 10 Page 7

3.3.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Received" 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.

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

SECTION 01 32 01.00 10 Page 8 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 $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 $20,000 or 1 percent of the present contract value, whichever is the greater, up to $200,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.

SECTION 01 32 01.00 10 Page 9

3.4 USE OF PRIMAVERA P6

If P6 is being used, the following are Mandatory Requirements:

The following settings are mandatory and required in the Preliminary Project Schedule, Initial Project Schedule and all schedule submissions to the Government.

1) Activity Codes shall be Project Level not Global or EPS level.

2) Calendars shall be Project Level not Global or Resource level.

3) Activity Duration Types must be set to "Fixed Duration & Units".

4) Percent Complete Types must be set to "Physical".

5) Time Period Admin Preferences must remain the default "8.0 hr/day, 40 hr/week, 172 hr/month, 2000 hr/year". Calendar Work Hours/Day must be set to 8.0 Hour days.

6) Schedule Option for defining Critical Activities shall be set to "Longest Path".

7) Schedule Option for defining progressed activities shall be set to "Retained Logic".

8) Cost loading shall be set up using a single lump sum Resource. The Price/Unit shall be $1/hr, Default Units/Time shall be "8h/d", and settings "Auto Compute Actuals" and "Calculate costs from units" selected.

9) Activity ID's shall not exceed 10 characters.

10) Activity Names shall have the most defining and detailed description within the first 30 characters.

Note: USACE P6 Mandatory Requirements are located in the Contract Adminstration Manual, and can be obtained from the Field Office.

3.5 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.5.1 Preliminary Project Schedule Submission

Within 15 calendar days…