MXDP22-1013_Sub 05_Final Specifications.pdf

Specifications Replace Foam Fire Suppression System, B50

100% Design

Laughlin Air Force Base, Texas

June 30, 2023

Replace Foam Fire Suppression System, B50 FA8903-21-D-0039

100% Design MXDP-22-1013

00 01 07 Page 1

00 01 07

SEALS AND SIGNATURES

Lucas Mendoza, PE

License No. 127717

The seal and signature to the left applies to the following

Specifications divisions and sections of this project manual:

• 02 41 00

• 03 30 53

• 05 05 20

• 05 30 00

Andrew Matjasko, RA

License No. 15179

Specifications divisions and sections of this project manual:

• 07 84 00

• 09 90 00

• 10 44 16

Russell Miller, PE

License No. 139919

Specifications divisions and sections of this project manual:

• 21 13 13

• 21 30 00

• 28 31 70

100% Design MXDP-22-1013

00 01 07 Page 1

Brian Perlberg, PE

License No. 115197

Specifications divisions and sections of this project manual:

• 23 03 00.00 20

• 23 05 93

• 23 30 00

• 23 81 00

• 23 82 46.00 40

Krystal Le, PE

License No. 123779

Specifications divisions and sections of this project manual:

• 26 20 00

• 26 28 01.00 10

• 26 51 00

Engineer’s seal and signature does not apply to the documents that comprise Division 00, Bidding and Contracting Requirements.

It is a violation of applicable laws and regulations governing professional licensing and registration for any person, unless acting under the direction of the licensed and registered design professional(s) indicated above, to alter in any way the Specifications in this project manual.

END OF SEALS AND SIGNATURES

Final Design MXDP-22-1013

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 08/15, CHG 2: 08/21 SUMMARY OF WORK

01 14 00 11/22, CHG 1: 02/23 WORK RESTRICTIONS

01 30 00 11/20, CHG 2: 05/22 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 02/15 PROJECT SCHEDULE

01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 11/16, CHG 2: 11/21 QUALITY CONTROL

01 50 00 11/20, CHG 2: 08/22 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 08/22 TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00 08/19, CHG 5: 08/22 PROJECT IDENTIFICATION

01 74 19 02/19, CHG 3: 11/21 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

01 78 00 05/19, CHG 1: 08/21 CLOSEOUT SUBMITTALS

01 78 23 08/15, CHG 2: 08/21 OPERATION AND MAINTENANCE DATA

01 91 00.15 10 05/19, CHG 3: 05/22 TOTAL BUILDING COMMISSIONING

DI VI SI ON 02 - EXI STI NG CONDI TI ONS

02 41 00 08/22 DEMOLITION

DI VI SI ON 03 - CONCRETE

03 30 53 05/14 MISCELLANEOUS CAST-IN-PLACE CONCRETE

DI VI SI ON 05 - METALS

05 05 20 05/22 POST-INSTALLED CONCRETE AND MASONRY

ANCHORS

05 30 00 05/15, CHG 2: 08/18 STEEL DECKS

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

07 84 00 05/10, CHG 1: 08/13 FIRESTOPPING

DI VI SI ON 09 - FI NI SHES

09 90 00 02/21 PAINTS AND COATINGS

DI VI SI ON 10 - SPECI ALTI ES

10 44 16 11/19 FIRE EXTINGUISHERS

DI VI SI ON 21 - FI RE SUPPRESSI ON

21 13 13 08/20 WET PIPE SPRINKLER SYSTEMS, FIRE

PROTECTION

21 30 00 04/08, CHG 1: 08/13 FIRE PUMPS

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

23 03 00.00 20 08/10, CHG 3: 08/18 BASIC MECHANICAL MATERIALS AND METHODS

23 05 93 11/15 TESTING, ADJUSTING, AND BALANCING FOR

HVAC

23 30 00 05/20, CHG 1: 02/22 HVAC AIR DISTRIBUTION

PROJECT TABLE OF CONTENTS Page 1

23 81 00 05/18, CHG 1: 02/21 DECENTRALIZED UNITARY HVAC EQUIPMENT

23 82 46.00 40 05/17 ELECTRIC UNIT HEATERS

DI VI SI ON 25 - I NTEGRATED AUTOMATI ON

25 05 11 05/21 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS - FIRE AND LIFE SAFETY

(FLS)

DI VI SI ON 26 - ELECTRI CAL

26 20 00 08/19, CHG 3: 11/21 INTERIOR DISTRIBUTION SYSTEM

26 28 01.00 10 08/21 COORDINATED POWER SYSTEM PROTECTION

26 29 23 02/20, CHG 1: 05/21 ADJUSTABLE SPEED DRIVE (ASD) SYSTEMS

UNDER 600 VOLTS

26 51 00 05/20, CHG 2: 11/21 INTERIOR LIGHTING

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

28 31 70 08/20 INTERIOR FIRE ALARM SYSTEM, ADDRESSABLE

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

SECTION 01 11 00

SUMMARY OF WORK

08/ 15, CHG 2: 08/ 21

PART 1 GENERAL

1.1 WORK COVERED BY CONTRACT DOCUMENTS

1.1.1 Project Description

The work includes This project is located at Laughlin Air Force Base (AFB), Texas, Building 50. This project includes work to remove the existing high expansion foam system (HEFS) in Building 50 “Hangar 1” and replace with an automatic water sprinkler system in accordance with the Sundown Policy for Foam Fire Suppression Systems, the HEFS system shall be replaced with automatic water sprinkler system. Building 50 contains fueled aircraft, with the primary function of the hangar being general aircraft maintenance. The hangar was constructed in 1954 and the fire suppression system (FSS) was installed in 2004. The aircraft servicing (hangar bay) area is approximately 37,200 square feet (SF). and incidental related work.

1.1.2 Location

The work is located at the Laughlin AFB, Building 50, approximately as indicated. The exact location will be shown by the Contracting Officer.

1.2 OCCUPANCY OF PREMISES

Building(s) will be occupied during performance of work under this Contract.

Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.

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

SECTION 01 11 00 Page 1 indicated on contract drawings, within area of work.

Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities are discovered. Verify the elevations of existing piping, utilities,and any type of underground 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.4.1 Notification Prior to Excavation

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

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 14 00

WORK RESTRICTIONS

11/ 22, CHG 1: 02/ 23

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

List of Contact Personnel

1.2 SPECIAL SCHEDULING REQUIREMENTS

b. Have materials, equipment, and personnel required to perform the work at the site prior to the commencement of the work. Specific items of work to which this requirement applies include:

c. The building will remain in operation during the entire construction period. The Contractor must conduct his operations so as to cause the least possible interference with normal operations of the activity.

d. Permission to interrupt any Activity roads, railroads, or utility service must be requested in writing a minimum of 15 calendar days prior to the desired date of interruption.

1.3 CONTRACTOR ACCESS AND USE OF PREMISES

1.3.1 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 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. Ensure all Contractor equipment, include delivery vehicles, are clearly identified with their company name.

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

SECTION 01 14 00 Page 1

Contracting Officer will identify designated smoking areas.

1.3.2 Working Hours

Regular working hours between 7 a.m. and 4 p.m., Monday through Friday , , excluding Government holidays.

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

1.3.4 Occupied Buildings

The Contractor shall be working in an existing building which is occupied.

The existing buildings and their contents must be kept secure at all times. Provide temporary closures as required to maintain security as directed by the Contracting Officer.

Provide dust covers or protective enclosures to protect existing work that remains, and Government material located in the building during the construction period.

Relocate movable furniture away from the Contractor's working area , protect the furniture, and replace the furniture in their original location s upon completion of the work. Leave attached equipment in place, and protect them against damage, or temporarily disconnect, relocate, protect, and reinstall them at the completion of the work.

1.3.5 Utility Cutovers and Interruptions

a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in paragraph WORK OUTSIDE REGULAR HOURS.

b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.

c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, compressed air, are considered utility cutovers pursuant to the paragraph WORK

OUTSIDE REGULAR HOURS.

d. Operation of Station Utilities: The Contractor must not operate nor disturb the setting of control devices in the station utilities system, including water, sewer, electrical, and steam services. The Government will operate the control devices as required for normal conduct of the work. The Contractor must notify the Contracting Officer giving reasonable advance notice when such operation is required.

SECTION 01 14 00 Page 2

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

SECTION 01 14 00 Page 3

SECTION 01 30 00

ADMINISTRATIVE REQUIREMENTS

11/ 20, CHG 2: 05/ 22

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 -- Safety and Health Requirements Manual

1.2 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

View Location Map

Progress and Completion Pictures

SD-04 Samples

Color Boards; G

1.3 COLOR BOARDS FOR AIR FORCE PROJECTS

Submit two sets of color boards within 90 calendar days after Contract Award. Each set of boards must include samples of colors and finishes of interior surfaces, such as walls, floors, and ceilings. Present the samples on 8 by 10-1/2 inches boards (modules) with a maximum spread of 24 by 31-1/2 inches for foldouts. Design modules to fit in a standard loose-leaf, three-ring binder. Where special finishes such as architectural concrete, carpet, or prefinished textured metal panels are required, submit samples not less than 12 inches square with the board.

If more space is needed, more than one board per set may be submitted.

Certify that the color samples have been reviewed in detail, and that the color samples are in strict accordance with contract drawings and specifications, except as may be otherwise explicitly stated. Submittal of color samples does not relieve the Contractor of the responsibility to submit samples required elsewhere herein.

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

SECTION 01 30 00 Page 1

1.5 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 different viewpoints selected by the Contractor unless otherwise directed 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. Photographs provided are for unrestricted use by the Government.

1.6 MINIMUM INSURANCE REQUIREMENTS

Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by State law.

1.7 SUPERVISION

1.7.1 Superintendent Qualifications

Provide project superintendent with 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.

For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.

1.7.2 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.7.3 Duties

The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend Red Zone meetings, partnering meetings, and quality control meetings. The

SECTION 01 30 00 Page 2 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.7.4 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 ensure 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.8 PRECONSTRUCTION

Immediately after award , prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction . The must take place within 35 calendar days after award of the contract, but prior to commencement of any work at the site.

The purpose of this is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to: daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.

1.8.1 Attendees

Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.

1.9 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)

Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start planning the turnover process at the Pre-Construction Conference meeting with a discussion of the Red Zone process and convene at regularly scheduled NRZ Meetings beginning at approximately 75 percent of project completion.

Include the following in the facility Turnover effort:

1.9.1 Red Zone Checklist

a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the Red Zone Checklist template.

b. Prior to 75 percent completion, modify the Red Zone Checklist template by adding or deleting critical activities applicable to the project and assign planned completion dates for each activity. Submit the modified Red Zone Checklist to the Contracting Officer. The Contracting Officer may request additional activities be added to the Red Zone Checklist at any time as necessary.

SECTION 01 30 00 Page 3

1.9.2 Meetings

a. Conduct regular Red Zone Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.

b. The Contracting Officer will establish the frequency of the meetings, which is expected to increase as the project completion draws nearer.

At the beginning, Red Zone meetings may be every two weeks then increase to weekly towards the final month of the project.

c. Using the Red Zone Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.

d. During the Red Zone Meetings discuss with the COTR any upcoming activities that require Government involvement.

e. Maintain the Red Zone Checklist by documenting the actual completion dates as work is completed and update the Red Zone Checklist with revised planned completion dates as necessary to match progress.

Distribute copies of the current Red Zone Checklist to attendees at each Red Zone Meeting.

1.10 PARTNERING

Contractor shall host the partnering session within 45 calendar days of contract award. To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.

1.10.1 Team-Led (Informal) Partnering

a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be co-led by the Government Construction Manager and Contractor's Project Manager.

b. The Initial Team-led Partnering session may be held concurrently with the Pre-Construction meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.

c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.

d. The Partners will determine the frequency of the follow-on sessions.

e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.

SECTION 01 30 00 Page 4

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

Not Used

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 (2017) Administration -- Project Schedules

1.2 SUBMITTALS

Government approval is required for submittals with a "G" classification.

Submittals not having a "G" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications; G

Preliminary Project Schedule; G

Initial Project Schedule; G

Periodic Schedule Update; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

PART 2 PRODUCTS

2.1 SOFTWARE

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

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

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

SECTION 01 32 01.00 10 Page 3

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:

Field Activity Code Length Description

1 WRKP 3 Workers per day

SECTION 01 32 01.00 10 Page 4

Field Activity Code Length Description

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

SECTION 01 32 01.00 10 Page 7

Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic.

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

3.3.10 Default Progress Data Disallowed

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

3.3.11 Out-of-Sequence Progress

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

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

3.3.12 Added and Deleted Activities

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

3.3.13 Original Durations

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

3.3.14 Leads, Lags, and Start to Finish Relationships

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

a. Leads (negative lags) are prohibited.

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

SECTION 01 32 01.00 10 Page 8 allowed.

3.3.16 Percent Complete

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

3.3.17 Remaining Duration

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

3.3.18 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 1 percent of the present contract value. Activity(ies) may be declared 100 percent complete upon the Government's verification of completion and correction of all punch list work identified during Government pre-final inspection(s).

3.3.18.1 As-Built Drawings

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

3.3.18.2 O & M Manuals

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

SECTION 01 32 01.00 10 Page 9 the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a progress payment can be made.

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

3.4.1 Preliminary Project Schedule Submission

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

3.4.2 Initial Project Schedule Submission

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

3.4.3 Periodic Schedule Updates

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

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

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

b. AS and AF dates must match the date(s) reported on the Contractor's 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.00 10 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 2 set(s) of hardcopy reports. The following lists typical reports that will be requested:

3.5.3.1 Activity Report

List of all activities sorted according to activity number.

3.5.3.2 Logic Report

List of detailed predecessor and successor activities for every activity in ascending order by activity number.

SECTION 01 32 01.00 10 Page 11

3.5.3.3 Total Float Report

A list of all incomplete activities sorted in ascending order of total float. List activities which have the same amount of total float in ascending order of Early Start Dates. Do not show completed activities on this report.

3.5.3.4 Earnings Report by CLIN

A compilation of the Total Earnings on the project from the NTP to the data date, which reflects the earnings of activities based on the agreements made in the schedule update meeting defined herein. Provided a complete schedule update has been furnished, this report serves as the basis of determining progress payments. Group activities by CLIN number and sort by activity number. Provide a total CLIN percent earned value, CLIN percent complete, and project percent complete. The printed report must contain the following for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Earnings to Date, Earnings this period, Total Quantity, Quantity to Date, and Percent Complete (based on cost).

3.5.3.5 Schedule Log

Provide a Scheduling/Leveling Report generated from the current project schedule being submitted.

3.5.4 Network Diagram

The Network Diagram is required for the Preliminary, Initial and Periodic Updates. Depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished.