W912HN-22-B-BRA1340_SPECS_VOL1.pdf

Fort Bragg, North Carolina

Draft IFB (Not For Construction) W912HN-22-Bra1340 Repair Enlisted UPH Barracks H4445 Volume 1 of 3: Specification Divisions 01 – 12

PN 97302

August 2022

U.S. ARMY ENGINEER DISTRICT, SAVANNAH

CORPS OF ENGINEERS

100 WEST OGLETHORPE AVENUE

SAVANNAH, GEORGIA 31401-3640

US Army Corps Of Engineers Savannah District

Repair Enlisted UPH Barracks H4445 BR97302 Fort Bragg, North Carolina

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 29 SUSTAINABILITY REPORTING

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 QUALITY CONTROL

01 45 00.15 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 45 35 SPECIAL INSPECTIONS

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 57 19.37 INDOOR AIR QUALITY (IAQ) MANAGEMENT

01 74 19 CONSTRUCTION WASTE MANAGEMENT AND DISPOSAL

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 91 00.15 10 TOTAL BUILDING COMMISSIONING

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 81 00 TRANSPORTATION AND DISPOSAL OF HAZARDOUS MATERIALS

02 82 00 ASBESTOS REMEDIATION

02 83 00 LEAD REMEDIATION

02 84 16 HANDLING OF LIGHTING BALLASTS AND LAMPS CONTAINING PCBs

AND MERCURY

02 85 00 MOLD REMEDIATION

DIVISION 03 - CONCRETE

03 30 00 CAST-IN-PLACE CONCRETE

DIVISION 04 - MASONRY

04 20 00 UNIT MASONRY

DIVISION 05 - METALS

05 05 23.16 STRUCTURAL WELDING

05 12 00 STRUCTURAL STEEL

05 30 00 STEEL DECKS

05 40 00 COLD-FORMED METAL FRAMING

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 51 33 METAL LADDERS

05 52 00 METAL RAILINGS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 20 00 FINISH CARPENTRY

06 61 16 SOLID SURFACING FABRICATIONS

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

PROJECT TABLE OF CONTENTS Page 1

07 21 13 BOARD AND BLOCK INSULATION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 22 00 ROOF AND DECK INSULATION

07 27 19.01 SELF-ADHERING AIR BARRIERS

07 27 26 FLUID-APPLIED MEMBRANE AIR BARRIERS

07 41 13 METAL ROOF PANELS

07 42 63 FABRICATED WALL PANEL ASSEMBLIES

07 60 00 FLASHING AND SHEET METAL

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 11 16 ALUMINUM DOORS AND FRAMES

08 14 00 WOOD DOORS

08 31 00 ACCESS DOORS AND PANELS

08 34 73 SOUND CONTROL DOOR ASSEMBLIES

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL WALL AND DOOR LOUVERS

DIVISION 09 - FINISHES

09 06 00 SCHEDULES FOR FINISHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC, QUARRY, AND GLASS TILING

09 62 38 STATIC-CONTROL FLOORING

09 65 00 RESILIENT FLOORING

09 90 00 PAINTS AND COATINGS

DIVISION 10 - SPECIALTIES

10 14 00.20 INTERIOR SIGNAGE

10 26 00 WALL AND DOOR PROTECTION

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS

10 56 13 STEEL SHELVING

DIVISION 11 - EQUIPMENT

11 31 13 ELECTRIC KITCHEN EQUIPMENT

DIVISION 12 - FURNISHINGS

12 21 00 WINDOW BLINDS

12 32 00 MANUFACTURED WOOD CASEWORK

DIVISION 21 - FIRE SUPPRESSION

21 13 13 WET PIPE SPRINKLER SYSTEMS, FIRE PROTECTION

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)

PROJECT TABLE OF CONTENTS Page 2

23 05 48.19 BRACING FOR HVAC

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC

23 09 23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS

23 11 20 FACILITY GAS PIPING

23 23 00 REFRIGERANT PIPING

23 25 00 CHEMICAL TREATMENT OF WATER FOR MECHANICAL SYSTEMS

23 30 00 HVAC AIR DISTRIBUTION

23 52 00 HEATING BOILERS

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 CHILLED, CHILLED-HOT, AND CONDENSER WATER PIPING SYSTEMS

23 81 00 DECENTRALIZED UNITARY HVAC EQUIPMENT

DIVISION 25 - INTEGRATED AUTOMATION

25 05 11 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS

25 05 11.21 CYBERSECURITY FOR FIRE ALARM CONTROL SYSTEMS

25 05 11.23 CYBERSECURITY FOR HVAC CONTROL SYSTEMS

25 08 10 UTILITY MONITORING AND CONTROL SYSTEM TESTING

DIVISION 26 - ELECTRICAL

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 13 SWITCHBOARDS

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 23 ADJUSTABLE SPEED DRIVE (ASD) SYSTEMS UNDER 600 VOLTS

26 41 00 LIGHTNING PROTECTION SYSTEM

26 42 13 GALVANIC(SACRIFICIAL) ANODE CATHODIC PROTECTION (GACP)

SYSTEM

26 51 00 INTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 05 13.43 TELEVISION DISTRIBUTION SYSTEM

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM,

ADDRESSABLE

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 11 00 CLEARING AND GRUBBING

31 31 16.13 CHEMICAL TERMITE CONTROL

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 11 23 AGGREGATE BASE COURSES

32 12 13 BITUMINOUS TACK AND PRIME COATS

32 12 16.16 ROAD-MIX ASPHALT PAVING

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

PROJECT TABLE OF CONTENTS Page 3

32 13 73.19 COMPRESSION CONCRETE PAVING JOINT SEALANT

32 16 19 CONCRETE CURBS, GUTTERS AND SIDEWALKS

32 92 19 SEEDING

32 92 23 SODDING

32 93 00 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 51 15 NATURAL-GAS / LIQUEFIED PETROLEUM GAS DISTRIBUTION

PIPELINES

33 61 13.13 PREFABRICATED UNDERGROUND HYDRONIC ENERGY DISTRIBUTION

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

APPENDICIES

APPENDIX A STANDARD FORMS

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 4

SECTION 01 11 00

SUMMARY OF WORK

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes Repair Barracks Building 315 and incidental related work.

1.1.2 Location

The work is located at the northeast area of Fort Gordon, off East Hospital Road, approximately as indicated. The exact location will be shown by the Contracting Officer.

1.2 EXISTING WORK

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

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

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

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

1.3.1 Notification Prior to Excavation

Notify the Contracting Officer at least 48 hours prior to starting excavation work.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 1

SECTION 01 14 00

WORK RESTRICTIONS

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification 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

List of Contact Personnel

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.1 Installation Regulations

Ensure that Contractor personnel employed on the Installation become familiar with and obey Installation regulations including safety, fire, traffic, and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear appropriate personal protective equipment (PPE) in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Mark Contractor equipment for identification.

1.2.1.1 Subcontractors and Personnel Contacts

Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.

1.2.1.2 No Smoking Policy

Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.

1.2.2 Working Hours

*2

Regular working hours will consist of an 8 1/2 hour period, between 7 a.m.

and 5 p.m. , Monday through Friday, excluding Government holidays.

1.2.3 Work Outside Regular Hours

Work outside regular working hours requires Contracting Officer approval.

Make application 15 calendar days prior to such work to allow arrangements to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, SECTION 01 14 00 Page 1 contract number and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 14 00 Page 2

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY (DA)

DA AR 25-2 (2019) Army Cybersecurity

DA AR 190-13 (2019) The Army Physical Security Program

DA AR 381-12 (2016) Threat Awareness And Reporting Program

DA AR 525-13 (2019) Antiterrorism

DA AR 530-1 (2014) Operations Security (OPSEC)

U.S. DEPARTMENT OF DEFENSE (DOD)

DOD 5220.22-M (2006; Change 1-2013; Change 2-2016) National Industrial Security Program Operating Manual (NISPOM)

DoD 8570.01-M (2005; Change 4-2015) Information Assurance Workforce Improvment Program

1.2 DESIGNATED BILLING OFFICE

Reference Contract Clause titled "PROMPT PAYMENT FOR CONSTRUCTION CONTRACTS" located in the CONTRACT CLAUSES. The "designated billing office" will be the Resident Office (RO) where the Contracting Officer Representative (COR) for this Contract is located. The address for the "designated billing office" is as follows:

Fort Gordon Resident Office USACE, Savannah District Attn: COR {Solicitation #}{W912HN-XX-X-XXXX} 1236 Lane Avenue, Bldg 11303 Fort Gordon, GA 30905

1.3 FORT GORDON AT-OPSEC REQUIREMENTS

1.3.1 Installation Access

Contractor employees, including subcontractors, must comply with applicable Installation and facility access security policies and procedures at work and TDY locations. Contractors and subcontractors will be issued a Common Access Card (CAC) or an Installation Pass through the Automated Installation Entry (AIE) Security System to access the Installation. The Fort Gordon military installation is a limited-access

SECTION 01 30 00 Page 1 post. Unscheduled gate closures by the military police may occur at any time.

In accordance with DA AR 525-13 , paragraph 5-19, prospective Contractors will undergo a verification process by the Installation Provost Marshal Office, Director of Emergency Services to determine the trustworthiness and suitability prior to being granted access to federal property. This will be accomplished using the National Crime Information Center (NCIC) Interstate Identification Index (III). This is the minimum baseline background check for entrance onto Army Installations for non-CAC holders to include entrance of visitors (Ref DA AR 190-13 , paragraph 8-2).

Personnel entering or exiting the installation may experience a delay due to vehicle inspections, registration checks, verification of seat belt use, etc. Vehicles and personnel are subject to search and seizure. The search and seizure provisions apply to Contractor personnel while within Fort Gordon's area of jurisdiction. Contractor personnel must comply with the entry control requirements and security policies/procedures in effect. Security procedures may change without notice.

1.3.2 Antiterrorism (AT) Level I Training

Contractor employees, including subcontractors, assigned to this Contract will receive an initial Antiterrorism Level I Brief by a certified ATO Level II Officer within 30 days of reporting for duty. (Monthly briefings will be offered by the Garrison Antiterrorism Officer.) Annual refresher Antiterrorism Level I Training shall be completed on-line at https://atlevel1.dtic.mil/at/ or they may attend the monthly training offered by the Garrison ATO. The Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee to the COR and unit/activity security manager. (Ref Department of the Army, US Army Contracting Agency, SFCA-CO, 5 Sep 07, subject:

Incorporation of Measures into the Contracting Process and DA AR 525-13 ).

1.3.3 iWATCH

Contractor employees, including subcontractors, assigned to this Contract shall receive a brief on the local iWATCH program (provided in conjunction with the AT Level I Training). This training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 days of reporting to duty and annual refresher training with the results reported to the COR.

1.3.4 Operation Security (OPSEC) Training

Contractor employees, including subcontractors, assigned to this Contract shall complete Level I OPSEC training within 30 days of reporting for duty and then annually thereafter. Initial Level 1 OPSEC training will be conducted monthly by the Garrison OPSEC Officer or a Level II certified OPSEC Officer. ( DA AR 530-1 ). Annual refresher training shall be completed on-line: Go to Internet Explorer, Fort Gordon website, select Fort Gordon and click on Dir, Plans Training and Mobilization, select Security/Intelligence, and click on Contractor OPSEC Awareness Training.

A record on completion will be provided to the COR and unit/activity security manager.

1.3.5 Threat Awareness and Reporting Program (TARP) Training

Contractor employees, including subcontractors, assigned to this Contract

SECTION 01 30 00 Page 2 shall complete TARP training within 30 days of reporting for duty and then annually thereafter. TARP training will be conducted monthly by the 902nd MI Group. The COR will ensure Contractors are notified of available training. Completion of training shall be reported to the COR and the unit/activity security manager. ( DA AR 381-12 ).

1.3.6 Information Assurance (IA)/Information Technology (IT) Training

Contractor employees and associated subcontractors must complete the DoD Cyber Awareness Challenge Training (https://ia.signal.army.mil/DoDIAA) before issuance of network access and annually thereafter. Certificates of successful completion, for both initial awareness training and annual refresher training shall be provided to the COR. All Contractor employees will successfully complete all required IA training as specified in DA AR 25-2 and as directed by the Government. All Contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoD 8570.01-M and DA AR 25-2 .

Contractors, to include subcontractors, requiring access to information systems to fulfill their duties must possess the required favorable security investigation. Contractors that require access to the Fort Gordon network shall have a minimum of a National Agency Check with Inquiries (NACI) investigation initiated and favorable review before issuance of network access. The IASO/IANO from the activity that the Contractor is assigned to, will submit an electronic DD 2875, System Authorization Access Request (SAAR) to Security and Intelligence Division for verification that the Contractor meets the requirements of DA AR 25-2 for accessing the Fort Gordon network.

1.3.7 Information Assurance (IA)/Information Technology (IT) Certification

Per DoD 8570.01-M , DFARS 252.239.7001, and DA AR 25-2 , the Contractor employees' supporting IA/IT functions shall be appropriately certified upon Contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon Contract award.

1.3.8 Handling/Access to Classified Information

The Contractor shall comply with FAR 52.204-2, Security Requirements.

This clause involves access to information classified "Confidential", "Secret", or "Top Secret" and requires Contractors to comply with (1) the Security Agreement (DD Form 441), including DOD 5220.22-M , and (2) revisions to DOD 5220.22-M .

1.3.9 Identification of Contractors

In accordance with FAR 37.114 Contract employees shall identify themselves as a Contractor while on the job, e.g., in the workplace, when attending meetings, in email, when answering Government telephones, and when making phone calls.

1.3.10 ID Badges

Provide each Contract personnel an identification (ID) badge on Contract start date or on employment start date. The ID badge shall be made of nonmetallic material, be easily readable, and shall contain the following minimum information: Employee's Name, Contract Company Name, Employee's Photograph.

SECTION 01 30 00 Page 3

Contractor personnel shall wear the ID badge when performing work under this Contract to include attending government meetings and conferences.

Unless otherwise specified in the Contract, each Contract personnel shall wear the ID badge in a conspicuous place on the front of exterior clothing and above the waist except when safety or health reasons prohibit such placement .

1.3.11 Answering Telephones

Contract personnel shall identify themselves as Contract employees when answering and making calls on government telephones.

1.3.12 Utilizing Electronic Mail

a. When Contractor personnel send e-mail messages to government personnel while performing on this Contract, the Contract personnel e-mail addresses shall include the company name together with the person's name (ex: John Smith, Contractor, ABC Company).

b. When Contract personnel require access to a government computer, the Contract personnel shall be required to obtain a Common Access Card. To do so, the Contract personnel shall request a CAC Card through the

COR.

NOTE: Return Government-issued CAC to the COR upon expiration of the Contract, replacement or termination of the Contract employee. (CAC card must be turned in to the COR on Contractor's last day of employment.)

Unauthorized possession of the CAC can be prosecuted criminally under section 701, title 18, United States Code.

Eligibility Verification for Employment

E-Verify is an Internet-based system that compares information from an employee's Form I-9, Employment Eligibility Verification, to data from U.S. Department of Homeland Security and Social Security Administration records to confirm employment eligibility. The U.S. Department of Homeland Security is working to stop unauthorized employment. By using E-Verify to determine the employment eligibility of their employees, companies become part of the solution in addressing this problem. All U.S. employers must complete and retain a Form I-9 for each individual they hire for employment in the United States. This includes citizens and noncitizens.

On the form, the employer must examine the employment eligibility and identity document(s) an employee presents to determine whether the document(s) reasonably appear to be genuine and relate to the individual and record the document information on the Form I-9. The list of acceptable documents can be found on the last page of the form. E-Verify is mandatory for employers with federal Contracts or subcontracts that contain the Federal Acquisition Regulation E-Verify clause.

1.4 PRIVATIZED UTILITIES

Utilities at Fort Gordon have been privatized. Below are the companies and their respective contact information. All utility work shall be performed by the privatized utility company as part of this contract. The work will be contracted by the Prime contractor and paid directly to the utility company as part of this contract.

Electrical: Georgia Power Mark Mills

SECTION 01 30 00 Page 4

706-564-5553 mamills@southernco.com

Water and Sewer: Augusta Utilities Stanely Aye 706-826-4788 saye@augustaga.gov

1.5 CONSTRUCTION LAYDOWN YARDS

A construction laydown yard will be assigned by the Fort Gordon Real Property office in coordination with the contracting officer. The contractor must obtain a License and Corporate Certificate for each construction company that desires to utilize a laydown area on Fort Gordon. The License and Corporate certificate must be signed and return to the real property office before a laydown area is authorized.

Contractors are not authorized to utilize parcels without prior approval.

All equipment, trailers, connex containers, materials, etc shall be removed prior to the end of construction. If items, materials and or equipment is abandoned, the contracotr will not recieve final payment. All parcels are assigned and must have approval from the Real Property office for occupancy. Operation and Maintenance will not start utilities (if readily available) without the approved license. The Government will not provide utilities or extension thereof, if they are not present and in working order at the location provided. Real Property conducts assignment and termination inspections prior to assignment and termination of the parcel. Before and after photos are taken to document the conditions.

1.6 FORT GORDON ACCESS REQUIREMENTS

All unescorted visitors 18 and older operating a vehicle, will need a visitor’s pass. A background check is required to obtain a visitor’s pass to the installation for those ages 18 and older wanting unescorted access.

Along with the pass, all persons ages 18 and older must present a valid picture identification card for access to the installation. Valid picture identification includes government-issued identification such as a drivers license, state identification, DD Form 1173 (Uniformed Services Identification and Privilege Card), DD Form 2 series or a passport issued by an authoritative agency (state/federal). Personnel under the age of 18 will not have a NCIC-III check conducted and may enter the Installation when escorted by a valid pass holder. See Attachment A "Fort Gordon Pass Procedures". Also visit Fort Gordon's gate website for current information and procedures.

https://home.army.mil/gordon/index.php/about/gate-information

1.7 NPDES CONSTRUCTION STORMWATER,LAND DISTURBANCE ACTIVITY,AND MS4 PERMITS

Obtain the applicable stormwater management permits associated with land disturbance activities for the project. The following information and references provide general guidance and guidelines to help assist site designers in understanding and meeting the Federal, State, local, and Fort Gordon permitting requirements for projects regulated under the NPDES Construction Stormwater, Land Disturbance Activity and NPDES MS4 permits.

The Fort Gordon Cantonment area falls under the jurisdiction of the state of Georgia's Environmental Protection Division (EPD) and the City of Augusta-Richmond County LIA (Local Issuing Authority. The Augusta-Richmond County LIA reviews ES&PCP for approval, conducts site inspections and

SECTION 01 30 00 Page 5 enforcement for construction activities at Fort Gordon.

Attachment B "Environmental Permit Process" explains the requirements for designing, obtaining, and maintaining a NPDES stormwater, land disturbance activity, or MS4 permit as required by the Federal Clean Water Act.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

SECTION 01 30 00 Page 6

SECTION 01 32 01

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, RO

Preliminary Project Schedule ; G, RO

Initial Project Schedule ; G, RO

Periodic Schedule Update ; G, RO

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 must be capable of meeting the requirements of this Section.

SECTION 01 32 01 Page 1

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.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the

SECTION 01 32 01 Page 2 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.

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.

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.

SECTION 01 32 01 Page 3

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

SECTION 01 32 01 Page 4

Field Activity Code Length Description

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.

Activities cannot have more than one Work Area Code.

Not all activities are required to be Work Area coded. A lack of Work

SECTION 01 32 01 Page 5

Area coding indicates the activity is not resource or space constrained.

3.3.6.4 Modification Number (MODF)

Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code.

3.3.6.5 Bid Item Coding (BIDI)

Assign a Bid Item Code to all activities using the Contract Line Item Schedule (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code.

3.3.6.6 Phase of Work Coding (PHAS)

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

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

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

3.3.6.7 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.3.6.8 Feature of Work Coding (FOW)

Assign a Feature of Work Code to appropriate activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan.

Definable Feature of Work is defined in Section 01 45 00 QUALITY CONTROL.

An activity can have only one Feature of Work Code.

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.

SECTION 01 32 01 Page 6

3.3.7.1 Project Start Date Milestone and Constraint

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

3.3.7.2 End Project Finish Milestone and Constraint

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

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

3.3.7.3 Interim Completion Dates and Constraints

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

3.3.7.3.1 Start Phase

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

3.3.7.3.2 End Phase

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

3.3.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop 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 the Special Contract Requirementns.

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.

SECTION 01 32 01 Page 7

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

SECTION 01 32 01 Page 8

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

SECTION 01 32 01 Page 9 progress payment can be made.

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

3.4.1 Preliminary Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule. The Preliminary Project Schedule may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as specified. The Preliminary Project Schedule forms the basis for the Initial Project Schedule specified herein and must include all of the required plan and program preparations, submissions and approvals identified in the contract (for example, Quality Control Plan, Safety Plan, and Environmental Protection Plan) as well as design activities, planned submissions of all early design packages, permitting activities, design review conference activities, and other non-construction activities intended to occur within the first 90 calendar days. Government acceptance of the associated design package(s) and all other specified Program and Plan approvals must occur prior to any planned construction activities. Activity code any activities that are summary in nature after the first 90 calendar days with Bid Item (CLIN) code (BIDI), Responsibility Code (RESP) and Feature of Work code (FOW).

3.4.2 Initial Project Schedule Submission

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

3.4.3 Periodic Schedule Updates

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

Provide a draft Periodic Schedule Update for review at the schedule update meetings as prescribed in the paragraph PERIODIC SCHEDULE UPDATE MEETINGS. These updates will enable the Government to assess Contractor's progress.

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

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

3.5 SUBMISSION REQUIREMENTS

Submit the following items for the Preliminary Schedule, Initial Schedule, and every Periodic Schedule Update throughout the life of the project:

SECTION 01 32 01 Page 10

3.5.1 Data CD/DVDs

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

3.5.2 Narrative Report

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

Include the following information as minimum in the Narrative Report:

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

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

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

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

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

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

3.5.3 Schedule Reports

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

Provide 3 set(s) of hardcopy reports. The following lists typical reports that will be requested:

3.5…