H.08.04_HECSA Training Support Facility specs.pdf

US Army Corps of Engineers Baltimore District

CONSTRUCTION

SPECIFICATIONS

TRAINING SUPPORT

FACILITY

HUMPHREYS ENGINEER CENTER, VA

INVITATION FOR BIDS [REQUEST FOR PROPOSAL].

W912DR-21-R-000#

CONTRACT NO.

DATE: APR ##, 2021

USACE Training Facility 218213

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 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.00 10 QUALITY CONTROL

01 45 00.15 10 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 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

DI VI SI ON 03 - CONCRETE

03 30 00 CAST-IN-PLACE CONCRETE

DI VI SI ON 04 - MASONRY

04 20 00 UNIT MASONRY

DI VI SI ON 05 - METALS

05 12 00 STRUCTURAL STEEL

05 21 00 STEEL JOIST FRAMING

05 30 00 STEEL DECKS

05 40 00 COLD-FORMED METAL FRAMING

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 51 00 METAL STAIRS

05 51 33 METAL LADDERS

05 52 00 METAL RAILINGS

DI VI SI ON 06 - WOOD, PLASTI CS, AND COMPOSI TES

06 10 00 ROUGH CARPENTRY

06 20 00 FINISH CARPENTRY

06 41 16.00 10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL CABINETS

06 61 16 SOLID SURFACING FABRICATIONS

DI VI SI ON 07 - THERMAL AND MOI STURE PROTECTI ON

07 05 23 PRESSURE TESTING AN AIR BARRIER SYSTEM FOR AIR TIGHTNESS

07 11 13 BITUMINOUS DAMPPROOFING

07 13 53 ELASTOMERIC SHEET WATERPROOFING

07 21 13 BOARD AND BLOCK INSULATION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 22 00 ROOF AND DECK INSULATION

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 27 19.01 SELF-ADHERING AIR BARRIERS

07 27 26 FLUID-APPLIED MEMBRANE AIR BARRIERS

PROJECT TABLE OF CONTENTS Page 1

07 42 13 METAL WALL PANELS

07 45 00 MINERAL-FIBER-REINFORCED CEMENTITIOUS PANELS

07 54 19 POLYVINYL-CHLORIDE ROOFING

07 60 00 FLASHING AND SHEET METAL

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DI VI SI ON 08 - OPENI NGS

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 33 13 COILING COUNTER DOORS

08 33 23 OVERHEAD COILING DOORS

08 34 73 SOUND CONTROL DOOR ASSEMBLIES

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 44 00 CURTAIN WALL AND GLAZED ASSEMBLIES

08 51 13 ALUMINUM WINDOWS

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

DI VI SI ON 09 - FI NI SHES

09 22 00 SUPPORTS FOR GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC TILING

09 51 00 ACOUSTICAL CEILINGS

09 65 00 RESILIENT FLOORING

09 68 00 CARPETING

09 69 13 RIGID GRID ACCESS FLOORING

09 72 00 WALLCOVERINGS

09 84 20 ACOUSTICAL WALL PANELS

09 90 00 PAINTS AND COATINGS

DI VI SI ON 10 - SPECI ALTI ES

10 11 00 VISUAL DISPLAY UNITS

10 14 00.20 INTERIOR SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 22 13 WIRE MESH PARTITIONS

10 22 43 SLIDING PARTITIONS

10 26 00 WALL AND DOOR PROTECTION

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS

10 51 13 METAL LOCKERS

DI VI SI ON 12 - FURNI SHI NGS

12 48 13 ENTRANCE FLOOR MATS AND FRAMES

DI VI SI ON 14 - CONVEYI NG EQUI PMENT

14 21 23 ELECTRIC TRACTION PASSENGER ELEVATORS

DI VI SI ON 21 - FI RE SUPPRESSI ON

21 12 00 STANDPIPE SYSTEMS

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

PROJECT TABLE OF CONTENTS Page 2

DI VI SI ON 22 - PLUMBI NG

22 00 00 PLUMBING, GENERAL PURPOSE

DI VI SI ON 23 - HEATI NG, VENTI LATI NG, AND AI R CONDI TI ONI NG ( HVAC)

23 00 00 AIR SUPPLY, DISTRIBUTION, VENTILATION, AND EXHAUST SYSTEMS

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.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS

23 11 25 FACILITY GAS PIPING

23 23 00 REFRIGERANT PIPING

23 81 00 DECENTRALIZED UNITARY HVAC EQUIPMENT

23 82 01.00 10 WARM AIR HEATING SYSTEMS

DI VI SI ON 25 - I NTEGRATED AUTOMATI ON

25 05 11.01 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS: HVAC

25 05 11.02 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS: FIRE

ALARM

25 05 11.03 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS: ESS

25 08 10 UTILITY MONITORING AND CONTROL SYSTEM TESTING

25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END

AND INTEGRATION

DI VI SI ON 26 - ELECTRI CAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 08 00 APPARATUS INSPECTION AND TESTING

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 13 SWITCHBOARDS

26 26 00 POWER DISTRIBUTION UNITS

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 28 05 ARC-FLASH STUDY

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 32 13.00 20 SINGLE OPERATION GENERATOR SETS

26 32 33.00 10 UNINTERRUPTIBLE POWER SUPPLY (UPS) SYSTEM

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DI VI SI ON 27 - COMMUNI CATI ONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

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

28 10 05 ELECTRONIC SECURITY SYSTEMS (ESS)

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DI VI SI ON 31 - EARTHWORK

31 00 00 EARTHWORK

31 05 19 GEOTEXTILE

31 11 00 CLEARING AND GRUBBING

PROJECT TABLE OF CONTENTS Page 3

31 61 00 AGGREGATE PIERS

DI VI SI ON 32 - EXTERI OR I MPROVEMENTS

32 01 19 FIELD MOLDED SEALANTS FOR SEALING JOINTS IN RIGID

PAVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 11 10 PAVEMENT DRAINAGE LAYER (RDM)

32 11 23 DENSE GRADED AGGREGATE (DGA) BASE COURSE

32 12 17.05 BITUMINOUS PAVING - VIRGINIA (SUPERPAVE)

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 17 23 PAVEMENT MARKINGS

32 31 13.53 HIGH-SECURITY CHAIN LINK FENCES AND GATES

32 92 19 SEEDING

32 92 23 SODDING

DI VI SI ON 33 - UTI LI TI ES

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 30 00 SANITARY SEWERAGE

33 40 00 STORM DRAINAGE UTILITIES

33 46 13 FOUNDATION DRAINAGE SYSTEM

33 46 16 SUBDRAINAGE SYSTEM

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 4

SECTION 01 11 00

SUMMARY OF WORK

08/15

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes construction of a new 66,000 square foot climate-controlled storage and training facility with related site improvments and incidental related work.

1.1.2 Location

The work is located at the Humphreys Engineering Center in northern Virginia.

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

Identify and mark all utilities. 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 or encased obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.

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

11/11

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

List of Contact Personnel

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.1 Visitor Control

Construction Workers (clearance, vetting procedures): Contractor must comply with the requirements and procedures as noted in the Security Requirements for FY21 Construction Projects memorandum included at the end of this section.

1.2.2 Activity Regulations

Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear hard hats 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.2.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.2.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.

SECTION 01 14 00 Page 1

1.2.3 Working Hours

Regular working hours must consist of an 8 1/2 hour period established by the Contracting Officer, Monday through Friday, , excluding Government holidays.

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

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 2

DEPARTMENT OF THE ARMY

U.S. ARMY CORPS OF ENGINEERS

HUMPHREYS ENGINEER CENTER

7701 TELEGRAPH ROAD

ALEXANDRIA, VIRGINIA 22315-3860

REPLY TO

ATTENTION OF

CEHEC-SC

MEMORANDUM FOR Baltimore District (ATTN: Joan Pamperien)

SUBJECT: Security Requirements for FY21 Construction Projects

1. References.

a. AR 190-13, Physical Security, 27 June 19.

b. AR 525-13, Antiterrorism, 17 Feb 17.

2. Background: In support of a tenant organization on Humphreys Engineer Center (HEC), the Baltimore District has awarded design contracts for the construction of multiple new buildings, with anticipated construction for at least one of the projects beginning in FY21. An Architectural and Engineering (A&E) firm working on some of the projects has requested language for security requirements to incorporate into the Specifications document of the design package. Representatives from the A&E firm met with the HEC Support Activity (HECSA) on 13 February 2020 to discuss the requirements. The HECSA Security Office recommends the clauses below, but specific formatting is left to the discretion of the A&E firm and Baltimore District.

3. Physical Security Requirements:

a. All Contractor and associated sub-contractors employees shall comply with applicable installation, facility and area Commander installation/facility access and local security policies and procedures (provided by the government representative). The Contractor shall also provide all information required for background checks to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. The Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA, and/or local policy. In addition to any changes otherwise authorized in the contract, the Government may require changes in Contractor security matters or processes due to changes in Force Protection Condition (FPCON) or security posture.

b. All Contractor and associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center- Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) in accordance with ref. a. These checks are performed at the Fort Belvoir Visitor Control Center (VCC), and must be complete prior to accessing HEC.

FOR OFFICIAL USE ONLY

c. Contractor and sub-contractor employees performing on the contract who have obtained a pass through the Fort Belvoir VCC may request a HEC access badge. The HEC badge shall be issued only for the period of time necessary, not to exceed one year. If needed, the HEC badge can be renewed annually after an additional NCIC-III check at the Fort Belvoir VCC.

d. All persons entering HEC are subject to search. Prohibited items include firearms of any kind, knives exceeding three inches, or any other form of dangerous weapon.

Violators are subject to criminal prosecution. All vehicles are subject to search by HEC Security Guards; the Contractor should anticipate delays in the morning due to high traffic volume. To facilitate vehicle screening, construction traffic may queue in a designated area to be coordinated between the Contractor and HEC Security.

e. Access to HEC for the purpose of performing on the contract does not suggest or imply authorized access to all areas (including buildings) of the installation. Contractor and sub-contractor employees shall only access the respective project sites while on HEC, with the exception of scheduled meetings.

4. Antiterrorism Requirements:

a. Antiterrorism (AT) Level I Awareness Training: Full-time Contractor and sub-contractor employees in positions of senior management (e.g., Superintendent, Project Managers, etc.) shall complete AT training within 30 calendar days after contract start date, or reporting for duty after contract award. The Contractor shall submit any training certificates within 5 calendar days after completion of training. Refresher training is required annually. Training is available at the following website:

https://jko.jten.mil/courses/atl1/launch.html (URL subject to change).

b. All Contractor and sub-contractors employees shall receive a brief or other training materials (provided by the requiring activity) regarding the local suspicious activity reporting (SAR) program. This locally-developed training teaches Contractor employees the types of behavior to watch for, and how to report suspicious activity.

This training shall be completed within 30 calendar days of contract award or within 30 calendar days of new employees performing on the contract. The Contractor shall certify in writing, when requested by the government representative, that all Contractor and sub-contractor employees have received the information.

5. General Security Requirements:

a. The Contractor shall pre-screen employees using the E-verify (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Contractor must ensure that the employee has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. This requirement applies to employees of the Contractor, and all sub-contractors.

FOR OFFICIAL USE ONLY

b. All Contractor and sub-contractor employees who are not in possession of the appropriate security clearance or access privileges, will be escorted in areas where they may be exposed to classified and/or sensitive materials, and/or accessing sensitive or restricted areas.

c. Full-time Contractor and sub-contractor employees in positions of senior management (e.g., Superintendent, Project Managers, etc.) shall complete Level I OPSEC Training within 30 calendar days after contract start date, or reporting for duty after contract award. The Contractor shall submit to the government representative any training certificates within 5 calendar days after completion of training. Refresher training is required annually. OPSEC awareness training is available at the following websites: https://www.iad.gov/ioss/ or http://www.cdse.edu/catalog/operations-security.html (URLs subject to change).

d. The government is not responsible for the security of Contractor or sub-contractor vehicles, equipment, tools, materials, supplies, etc. The use of fencing around lay-down yards and project sites is encouraged to prevent loss, damage, or theft.

e. Photography of the project site or other areas of the installation shall be coordinated in advance with the HEC Security Office. The use of small unmanned aerial systems (e.g., drones) for any purpose, including collecting progress images of the project site, is strictly prohibited.

5. The points of contact for this memorandum are:

a. Chief, HECSA Security: Mr. Jeffrey Hill, 202-761-8243, jeffrey.w.hill@usace.army.mil.

b. Physical Security: Mr. Douglas Roberts, 703-428-6974, douglas.l.roberts@usace.army.mil.

c. Antiterrorism: Mr. Franklin Barrett, 703-428-6223, franklin.barrett@usace.army.mil.

JEFFREY W. HILL

Chief, HECSA Security

EXISTING DROP ARM GATE

(APPROX. LOCATION)

INSPECTION AREA (80' X 20')

VEHICLE PORTAL, SEE NOTE 9

TEMPORARY RESTRIPING OF

EXISTING ENTRANCE AREA

12' LANE WIDTH, TYP.

TRUCK STAGING AREA

EXISTING MANUAL CHAINLINK VEHICLE GATE

L

E

A

F

R

O

A

D

T

E

L

E

G

R

A

P

H

R

A

D

K

I N

G

M

A

N

R

O

A

D

S O

L I C

I T

A T

I O

N

N

O

D E

S I G

N E

D

B

Y

D E

S C

R I P

T I O

N

A

M A

R K

S I Z

E

S U

B M

I T

T E

D

B

Y

D A

T E

C O

N T

R A

C T

N

C H

E C

K E

D

B

Y

D R

A W

N

B

Y

I S

S U

E

D

A T

E

SHEET ID

B

C

D

E

F

G

2 3 4 5 6 7 8 9 10

US Army Corps of Engineers

U S

A

R M

Y

C

O R

S

E

N G

I N

E E

R S

A N

S I

B

W

X

X X

X

X X

X

W

X

X X

X

X X

X

O C

T O

B E

R

B A

L T

I M

O R

E

M

D

H

O P

K I N

S

P

L A

Z A

B A

L T

I M

O R

E

D

I S

T R

I C

T

A L E

X A

N D

R I A

V

A

E

I S

E N

H O

W E

R

A

V E

S

U I T

E

W I L E

Y

W

I L

S O

N

H U

M P

H R

E Y

E

G

I N

E E

R

C

E N

T E

R

H

E C

V

A

100% DESIGN SUBMISSION

X-000

C O

N S

T R

U C

T I O

N

A

C C

E S

S

S

I T

E

M

A P

G

N

E W

M A

N

G

N

E W

M A

N

C

K

I N

G S

L A

N D

G O

R D

O N

Feet

0 50 100

UNCLASSIFIED//FOR OFFICIAL USE ONLY

S O

L I C

I T

A T

I O

N

N

O

D E

S I G

N E

D

B

Y

D E

S C

R I P

T I O

N

A

M A

R K

S I Z

E

S U

B M

I T

T E

D

B

Y

D A

T E

C O

N T

R A

C T

C H

E C

K E

D

B

Y

D R

A W

N

B

Y

I S

S U

E

D

A T

E

SHEET ID

B

C

D

E

F

G

2 3 4 5 6 7 8 9 10

US Army Corps of Engineers

U S

A

R M

Y

C

O R

E

N G

I N

E E

R S

UNCLASSIFIED//FOR OFFICIAL USE ONLY

NOTES:

1. CONTRACTOR IS RESPONSIBLE FOR SITE SECURITY AND

JOB SAFETY.

2. COORDINATE ALL TEMPORARY TRAFFIC CONTROL WITH

COR AND HEC. NO MODIFICATIONS WILL BE MADE TO

TEMPORARY TRAFFIC CONTROL WITHOUT PROPER

NOTIFICATION AND PERMISSION FROM HEC.

3. MAINTAIN ANY PEDESTRIAN, BUS, AND ACCESSIBLE

ROUTES.

4. TRAFFIC SIGNAGE AND MARKINGS SHALL CONFORM TO

VDOT MUTCD.

5. DAMAGE RESULTING FROM CONSTRUCTION LOADS ARE

RESPONSIBILITY OF CONTRACTOR FOR REPAIR AT NO

ADDED COST.

6. RETURN AREA INDICATED TO ORIGINAL EXISTING

CONDITIONS (CLEANUP, REPAIRS, ETC) UPON COMPLETION.

7. MAINTAIN ACCESS CONTROL MEASURES AT INSPECTION

POINT.

8. STABILIZE ALL DISTURBED AREAS.

9. VEHICLE PORTAL: PLACE CONCRETE CONSTRUCTION

BARRIERS TO CREATE A 12' WIDE ANC MINIMUM 20' LONG

VEHICLE PORTAL. EXTEND FLANKING CONCRETE

CONSTRUCTION BARRIERS PERPENDICULAR TO THE

ROADWAY TO WITHIN 4' OF ADJACENT TREE TRUNKS.

CONSTRUCTION TRAFFIC ARROW

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

08/15

PART 1 GENERAL

1.1 REFERENCES

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submittals with an "S" are for inclusion in the Sustainability eNotebook, 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

View Location Map; G , RO

Progress and Completion Pictures; G , RO

1.3 VIEW LOCATION MAP

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

1.4 PROGRESS AND COMPLETION PICTURES

Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten views from points located by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures. Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file. Include a date designator in file names. Cross reference submittals in the appropriate daily report. Photographs provided are for unrestricted use by the Government.

SECTION 01 30 00 Page 1

1.5 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage specified in the Project Solicitation.

1.6 SUPERVISION

1.6.1 Minimum Communication Requirements

Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of contract work. In addition, if a Quality Control (QC) representative is required on the contract, then that individual must also have fluent English communication skills.

1.6.2 Superintendent Qualifications

The project superintendent must have a minimum of 10 years experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.

1.6.2.1 Duties

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

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

1.6.3 Non-Compliance Actions

The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to insure timely completion.

Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.7 PRECONSTRUCTION CONFERENCE

After award of the contract but prior to commencement of any work at the site, meet with the Contracting Officer to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule of prices or earned value report, shop drawings, and other submittals, scheduling programming, prosecution of the work, and clear expectations of the "Interim DD Form 1354" Submittal, and the processes for joint risk management between the Contractor and Government. Major subcontractors who will engage in the

SECTION 01 30 00 Page 2 work must also attend.

1.8 PARTNERING

To most effectively accomplish this contract, the Government requires the formation of a cohesive partnership within the Project Team whose members are from the Government, the Contractor and their Subcontractors. Key personnel from the Supported Command, the End User (who will occupy the facility), the Government Construction team and Subject Matter Experts, the Installation, the Contractor and Subcontractors will be invited to participate in the Partnering process. The Partnership will draw on the strength of each organization in an effort to achieve a project that includes joint risk management, is without any safety mishaps, conforms to the Contract, and stays within budget and on schedule.

The Contracting Officer will provide Information on the Partnering Process and a list of key and optional personnel who should attend the Partnering meeting.

1.8.1 Formal Partnering

Provide and host the Partnering sessions with key personnel of the Project Team, including Contractor personnel and Government personnel. Pay all costs associated with the Partnering effort including the Facilitator, the meeting room, and other incidental items. In exception, each participant bears their own costs for meals, lodging, and transportation associated with the Partnering sessions.

Before a Partnering session, coordinate with the Facilitator all requirements for incidental items (such as audio-visual equipment, easels, flipchart paper, colored markers, note paper, pens/pencils, colored flash cards), and have these items available at the Partnering session. Provide copies of documents for distribution to all attendees. Provide a Facilitator experienced in conducting Partnering Workshops, and who is acceptable to both the Government and the Contractor. The Facilitator is responsible for leading the team in a timely manner and making sure that issues are identified and resolved. A list of Partnering Facilitators is available from the Contracting Officer.

a. Schedule the Initial Partnering Session for a duration of one day minimum. Locate this session at a place off the construction site, as agreed to by the Contracting Officer and the Contractor. It may take place concurrently with the Pre-Construction Meeting.

b. Schedule follow-on Partnering Session(s) for a maximum of 4 hours.

Schedule them at no more than 3 to six month intervals. Participants are encouraged to utilize electronic means to expedite meetings.

Meetings may be held at a location off-Base, at the project site, or in a Government Facility on Base. Follow-on meetings may be held concurrently with other scheduled meetings. Attendees need only be those required to resolve current issues. Recommend using the same Facilitator from the Initial Partnering session to achieve best results and for continuity.

1.9 ELECTRONIC MAIL (E-MAIL) ADDRESS

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

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

1.10 PERMITS

The following permits and approvals are required prior to construction.

1.10.1 Virginia Department of Environmental Quality

The following permits and approvals are required from the Virginia Department of Environmental Quality (VADEQ).

1.10.1.1 Virginia Pollutant Discharge Elimination System Permit

The contractor must obtain permission to operate under the Virginia Pollutant Discharge Elimination System (VDPES) Construction General Permit (CGP). The Designer of Record (DOR) will have obtained plan approval from VADEQ for both stormwater management and erosion and sediment control. A Stormwater Pollution Prevention Plan (SWPPP) has been partially prepared by the DOR for completion by the contractor. The contractor is responsible for keeping the SWPPP up to date throughout construction. The contractor is responsible for filing a Registration Statement with VADEQ, paying the required submission fees, and completing all other required criteria for obtaining coverage under the CGP. Coverage under the CGP is required prior to any land disturbance onsite. The contractor is responsible for filing a Transfer of Ownership Agreement, if needed, during construction. The contractor is responsible for filing a Notice of Termination (NOT) within 30 days of implementing all necessary permanent control measures, ensuring all controls are in place and functioning, and achieving final stabilization onsite. The contractor shall hire a 3rd party to complete the Engineer's Certification Statement and as-built plans to accompany the NOT. See specification 33 44 00 for more information regarding construction inspections by a 3rd party.

1.10.2 Dominion Energy

The project requires new service from Dominion Virginia Power (DVP). The DOR initiated new service with DVP and provided a load letter. Contractor is responsible for coordination with HECSA and DVP to confirm adequate power source, location, and service routing as well as the installation, inspection, and cost of all temporary and permanent power requirements.

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 30 00 Page 4

SECTION 01 30 00 Page 5

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

U.S. ARMY CORPS OF ENGINEERS (USACE)

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

1.2 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. 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, 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.

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.

Activities cannot have more than one Work Area Code.

SECTION 01 32 01.00 10 Page 5

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.

No constrained dates are allowed in the schedule other than those

SECTION 01 32 01.00 10 Page 6 specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

3.3.7.1 Project Start Date Milestone and Constraint

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

3.3.7.2 End Project Finish Milestone and Constraint

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

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

3.3.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 Clauses or Requirements. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends. Weather delay work days are provided below .

3.3.9 Time Extensions For Unusually Severe Weather

3.3.9.1 Procedure for Determination

This provision specifies the procedure for determination of time extensions for unusually severe weather in accordance the contract clause 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:

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

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

SECTION 01 32 01.00 10 Page 7

3.3.9.2 Anticipated Adverse Weather Delays

The following schedule of monthly anticipated adverse weather delays 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.

MONTHLY ANTICIPATED ADVERSE WEATHER DELAY

WORK DAYS BASED ON (5) DAY WORK WEEK

(a) FORT BELVOIR, HEC

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

6 6 6 8 6 6 7 5 3 5 5 5

3.3.10 Open Ended Logic

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

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

3.3.11 Default Progress Data Disallowed

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

3.3.12 Out-of-Sequence Progress

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.

Propose logic corrections to eliminate out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Address out of sequence progress or logic changes in the Narrative Report and in the periodic schedule update meetings.

3.3.13 Added and Deleted Activities

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

3.3.14 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work

SECTION 01 32 01.00 10 Page 8 item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

3.3.15 Leads, Lags, and Start to Finish Relationships

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

a. Leads (negative lags) are prohibited.

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

3.3.16 Retained Logic

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

3.3.17 Percent Complete

Update the percent complete for each activity started, based on the realistic assessment of earned value.