Revised MATOC Specs 9 Jun 2012.pdf

RFP NO. : W912BV-12-R-0024

US Army Corps of Engineers

Tulsa District

ECONOMICALLY DISADVANTAGED WOMAN OWNED SMALL

BUSINESS (EDVOSB) SET ASIDE INDEFINITE DELIVERY

INDEFINITE QUANTITY (IDIQ) MULTIPLE AWARD TASK ORDER

CONTRACTS (MATOCs) FOR GENERAL CONSTRUCTION

RELATED SERVICES IN SUPPORT OF VARIOUS MILITARY AND

CIVIL WORKS CONSTRUCTION PROJECTS WITHIN BOUNDARIES

OF THE USACE TULSA DISTRICT BOUNDARIES. (“USACE Tulsa District EDWOSB IDIQ MATOCs for General Construction Related Services”)

Specifications (MATOC only)

REVISED 9 July 2012 NOTE: Specs released with Solicitation were dated June 2012, but Specs released with Amendment 2 were dated April 2012. These are the final Specs.

TABLE OF CONTENTS

USACE Tulsa District EDWOSB IDIQ MATOC For General Construction Services

- - End Table of Contents - -

SECTION TITLE

DIVISION 01 – GENERAL REQUIREMENTS

01 01 00.00 44 Work Plan Requirements 01 32 01 Project Schedule 01 33 00 Submittal Procedures 01 35 26 Governmental Safety Requirements 01 44 00 Contractor Quality Control 01 45 02 Quality Control System (QCS) 01 50 00 Temporary Construction Facilities and Controls 01 57 20 Revised Environmental Protection 01 58 00 Project Signs 01 60 00 Material and Equipment 01 78 00 Project Closeout and Submittals

ED Woman Owned Small Business MATOC FY12 EDWOSBMATOCFY12

01 01 00.00 44 Page 1

SECTION 01 01 00.00 44

WORK PLAN REQUIREMENTS

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 in the text by basic designation only.

INTERNATIONAL CODE COUNCIL (ICC)

ICC Bldg Code ICC International Building Code

INTERNATIONAL CONFERENCE OF BUILDING OFFICIALS (ICBO)

ICBO Bldg Code Uniform Building Code (3 Vol.)

UNIFIED FACILITIES CRITERIA (UFC)

UFC 3-600-01 Design: Fire Protection Engineering For Facilities

U.S. ARMY CORPS OF ENGINEERS, SOUTHWESTERN DIVISION PUBLICATIONS

(CESWD)

CESWD-01 (Current Version) Corps of

Engineers Southwestern Division Architectural and Engineering Instruction Manual (CESWD-AEIM)

1.3 SUBMISSION OF TASK ORDER DRAWINGS, SPECIFICATIONS, AND OTHER DATA

1.3.1 Number of Copies

The Contractor shall submit, in accordance with Section 00 90 00 DESCRIPTION/SPECS/WORK STATEMENT and Section 01 33 16 DESIGN AFTER AWARD (if applicable), the required number of copies of the construction drawings, specifications, calculations, equipment schedules, and all other submittal data for each review submittal. These submittals shall be in accordance with the requirements of this MATOC Contract, all current revisions, the task order, and all other terms and conditions of the Contract.

1.3.2 Task Order Drawings

See Section 01 33 16 DESIGN AFTER AWARD, if applicable, and Section 01 78 00 CONTRACT CLOSEOUT for CADD drawing requirements and standards. Provide CAD files in the format required by the installation.

1.3.2.4 Drawings Sequence

Arrange drawings by design discipline in accordance with the CESWD-01, SWD Architectural and Engineering Instruction Manual, Chapter VIII, Appendix A, Plate D1, Standard Arrangement Of Drawings.

1.3.2.5 Drawings Required

As a minimum, the construction drawings shall consist of the following as required by the task order:

01 01 00.00 44 Page 2

a. Title Sheet, Index of Drawings (each technical discipline shall have a separate drawing legend sheet located in front of each respective section), Legend, and Abbreviations and Soil Borings

b. Civil Drawings

c. Utility Drawings (Water Supply, Wastewater, Gas, Electrical, Fiber and Communication)

d. Architectural Drawings

e. Interior Design Drawings

f. Structural Drawings

g. Mechanical Drawings

h. Electrical Drawings (including security and fire alarm)

i. Lightning Protection

j. Fire Protection Drawings

k. Environmental Drawings (including identification and removal of hazardous materials from the buildings, storm water control details, etc.)

l. Kitchen Equipment Drawings

m. Landscape Architectural Drawings

n. Irrigation Layout Drawings

1.3.3 Task Order Specifications

Construction specifications shall be in sufficient detail to fully describe and demonstrate the quality of materials, the installation and performance of equipment, and the quality of workmanship. Use any commercially available guide specifications such as "SpecText" published by The Construction Specifications Institute, manufacturers' product specifications utilizing CSI's Manu-Spec format, or the Corps of Engineers Unified Facilities Guide Specifications (UFGS), the Tulsa District's local guide specifications. The specifications shall clearly identify, where appropriate, the specific products chosen to meet the requirements of the Contract (manufacturers' brand names and model numbers or similar product information). The Contractor shall be responsible for coordinating references, along with the Contract performance requirements, to specific specification sections (number and title) within the construction specifications.

1.3.3.1 Commercially Available Guide Specifications

When commercially available construction guide specifications are used, change references to the "Architect", "Engineer", and "Owner" to refer to the "Government" or "Contracting Officer".

1.3.3.2 Guide Specification Editing

01 01 00.00 44 Page 3

When the UFGS are used, specification paragraphs and subparagraphs shall not be rewritten to lessen the quality of materials as specified in the original guide specifications. Edit to tailor the specifications to fit the project.

1.3.3.3 Format

Submit construction specifications, including cover page and Project Table of Contents, using software applicable to the guide specification version; the current version of Specsintact for UFGS guides and Microsoft Word 2003 or later version for other commercially available guide specifications. Print hard copies using laser or inkjet printer and good quality white bond paper (75 g/m 2 (20 pound Copier/Laser/Fax/Inkjet/Offset type), 215 mm by 279 mm (8 1/2 by 11 inch) in size. Review copies shall be the marked-up version with the editing shown by using redlining for text insertions and strikeouts for text deletions. The corrected 100 percent specifications with review comments incorporated shall be cleaned up (markings for insertion and deletion removed) and submitted in both hard copy and on magnetic media (CD-ROM disk).

Carbon copies are not acceptable. Electronic version: Print the specifications to Adobe Acrobat .pdf format and include on the CD-ROM disc with the drawings. The specifications shall be a single file with bookmarks utilized for each section. File shall open with bookmarks showing. Include the native word files of the specifications on the CD for the final submitted specifications. Include Adobe Acrobat Reader and the Contract Viewer software on the CD Disc. Contract Viewer software, along with instructions, can be copied from the Solicitation files.

1.3.3.4 Submittal Register

Submit a submittal register with each task order. See Sections 01 45 01.10 10 QUALITY CONTROL SYSTEM (QCS) and 01 33 00 SUBMITTAL PROCEDURES. Use the Corps QCS software described in Section 01 45 01.10 10 QUALITY CONTROL SYSTEM (QCS) When UFGS guide specifications are used, the Specsintact software can be used to generate the submittal register. Submit with the review and final submittals.

1.3.3.5 Cover Page

Include the following information:

a. Project title, location, and task order title

b. Construction contract number

c. Task Order number

d. Construction Contractor's name and address

1.3.4 Task Order Documents

In general, task order documents shall include construction drawings, specifications, Storm Water Pollution Prevention Plan if applicable, construction schedule, and calculations for categories such as, but not limited to, architectural, structural, mechanical, electrical, grading, drainage, paving, and outside utility services. Detailing and installation of all equipment and materials shall comply with the manufacturers' recommendations. See also Sections 00 90 00 DESCRIPTION/SPECS/WORK STATEMENT and 01 33 16 DESIGN AFTER AWARD.

1.3.5 Task Order Reviews

01 01 00.00 44 Page 4

See Sections 01 33 16 DESIGN AFTER AWARD and Sections 00 90 00 DESCRIPTION/SPECS/WORK STATEMENT for review requirements.

1.3.5.1 Material normally required for preliminary submittal

a. Drawings; All drawings required for completion of the task order, developed to approximately 35 percent completion.

b. Specifications; Draft of specifications for task work, including index and manufacturers' catalog and engineering data.

c. SID Interior and Exterior Finish Samples; See Section 01 33 16 DESIGN

AFTER AWARD.

d. Calculations; Calculations developed to the extent required to support the task order development of that portion of utility distribution, structural, electrical, and mechanical systems included in this submittal.

e. Storm Water Pollution Prevention Plan (SWPPP)

f. Construction Schedule; Construction schedule shall conform to the requirements Section.

1.3.5.2 Material normally required for final (100 percent) submittal Includes all documents submitted for the preliminary review, upgraded to 100 percent completion.

a. Drawings

1) Site Drawings; Site drawings shall include plans and details required by the task order.

2) Architectural Drawings; Architectural drawings shall include plans, elevations, building sections; fire exits; wall, ceiling, and floor fire ratings; and details required by the task order.

3) Structural Drawings; Structural drawings shall include plans, details, and connections applicable to the task order.

4) Mechanical and Electrical Drawings; Mechanical/electrical drawings, with complete schematics, shall show all heating, air conditioning, plumbing and electrical work.

5) Fire Protection Drawings; Fire Protection drawings, with complete schematics, shall show all fire sprinkler system layout, pipe sizes, locations of heads, details, etc. as required for construction and to meet the codes.

6) Equipment Schedules; Based on the results of calculations, provide a complete list(s) of the materials and equipment proposed for heating, air conditioning and plumbing, with the manufacturer's published cataloged product installation specifications and roughing-in data. The heating and air conditioning equipment data shall include the manufacturer's wiring diagrams, installation specifications, ARI certification, 01 01 00.00 44 Page 5 and the standard warranty for the equipment. When new diffusers are required in a task order, provide the manufacturer's published cataloged capacities for supply diffusers as evidence that the arrangement of supply air outlets in each room will provide the throw and spread characteristics required to cover completely all exterior wall surfaces with the blanket of warm air at the proper design velocities.

b. Specifications; Specifications for all task order work upgraded to 100 percent completion. Contractor shall make final proposal of all materials and finishes at this submittal.

c. Calculations; Complete calculations for utility distribution systems, structural elements, and electrical and mechanical systems. Include computations for sizing equipment, air duct arrangement, and R-values for ceilings, roofs and exterior walls and floors. Calculations shall conform to the military installation’s yearly energy budget requirements (i.e. BTU's and KW's). Include codes, manuals, and criteria used for calculations. Include, as applicable:

1) loads, load factors, and allowances for future loads,

2) energy performance calculations,

3) working stresses and factors of safety,

4) deflection calculations,

5) Expansion-, contraction-, and crack-control measures,

6) Foundation characteristics,

7) Construction or erection limitations, and

8) Fire Protection: Comprehensive analysis of all fire-safety factors with indication of treatment provided for each potential hazard.

d. Construction Schedule

e. Submittal Register; Printed copy shall be provided. Upon approval of the government, the register shall be loaded into QCS by the contactor.

1.3.7 Common Design Deficiencies

The work involved in making corrections due to common deficiencies becomes lost effort and time for both the designer and the reviewer. Contractor and Designer shall carefully compare the design and contract documents with all requirements at several points in the design process to avoid unnecessary changes at a later date. Some of the requirements which are most often overlooked include:

a. Requirements of required design publications, such as the Border Patrol design guides or the CESWD-01, Southwestern Division's ARCHITECTURAL AND ENGINEERING INSTRUCTIONS MANUAL (SWD-AEIM), have been repeatedly overlooked in the past.

b. Not using correct abbreviations or terminology on the drawings.

Abbreviations must match what is used on the standard abbreviation sheet and terminology must match what is used in the standard technical guide specifications.

c. Not using the correct scales, north arrow designation, section cut system, or incomplete dimensioning on the drawings. Failure to orient

01 01 00.00 44 Page 6 the North arrow in the same direction on all sheets (civil, site, arch).

d. Failure to use the latest edition (at time of task order start) of applicable criteria unless a specific edition is specified.

e. Not providing sufficient space for door operation hardware at doors which swing into a wall running perpendicular to the opening. 4 inches (100 mm) minimum is required between edge of door frame and perpendicular walls. Proper mechanical and electrical clearances to meet building codes.

f. Not providing correct and complete Design Analysis information written in the present tense. The Design Analysis will be written following the format indicated herein. A separate Fire Protection section in the Design Analysis with input from all disciplines is one area which is often overlooked and shall be included.

g. Not correctly presenting or coordinating (to avoid interference) features of Fire Protection, Noise Control, Mechanical Systems, and Physical Security.

h. Not correctly referencing and cross referencing building sections, wall sections, details, etc.

i. Not sufficiently providing enough architectural details to show how building envelope requirements will meet the testing criteria to include provision of supporting calculations.

j. Failure to read and use technical notes in editing technical guide specifications.

k. Failure to coordinate all disciplines prior to review submittals.

l. Improper use of fire-retardant wood. Fire-retardant wood is combustible; its use in buildings that are of noncombustible construction is extremely limited (see ICBO Bldg Code,or ICC Bldg Code for the minor allowable uses). Because of the potential for severe degradation, fire retardant plywood shall not be used in a roof or roofing system or in structural applications.

m. Not listing the ANSI/BHMA numbers in addition to trade names in door hardware specifications and failure to correctly specify hardware finishes.

n. Not showing control joints in CMU walls or brick expansion joints in face brick on both architectural plans, elevations and structural plans, or the joints are inconsistent. Also, locate and coordinate control joints for floor tile in accordance with the Tile Council of America recommendations.

o. For LEED projects, not properly defining in the specifications the design and construction deliverables required to meet USGBC requirements or to allow the Quality Control Manager in the field to understand what LEED requirements must be met and how.

01 01 00.00 44 Page 7

p. Failure to delete all publications which do not apply to the particular project.

1.4 COE GUIDE SPECIFICATIONS AND SOFTWARE

The Corps of Engineers Unified Facilities Guide Specifications (UFGS) can be downloaded from the Corps of Engineers web site. These guide specifications (UFGS) are in the Specsintact SGML format. The UFGS guide specifications are in the current CSI MasterFormat 2004 division and section numbering series.

a. The Corps of Engineers Specsintact software can be downloaded free of charge from the Internet at the following address:

http://specsintact.ksc.nasa.gov/software/software.htm

b. The Corps of Engineers UFGS Guide Specifications, Lighting Fixture Standard Drawing 40-06-04 Details, and Design Criteria (e.g. Unified Facilities Criteria, Army Technical Manuals (TM's), Engineering Manuals, Engineering Technical Letters, Engineer Circulars, Engineer Pamphlets, Design Guides, and Military Handbooks) can be downloaded from the Huntsville Division's Techinfo web site at the following address: http://www.hnd.usace.army.mil/techinfo/

c. UFGS guide specifications and other design guides can also be obtained from the National Institute of Building Sciences (NIBS)'s Construction Criteria Base (CCB) Whole Building Design Guide web site at:

http://www.ccb.org/.

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION (NOT USED)

-- End of Section --

SECTION 01 32 01

PROJECT SCHEDULE

08/08

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)

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 (TRO = Tulsa Resident Office). The following shall be submitted in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Schedule; G, TRO

1.3 QUALITY ASSURANCE

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling projects similar in nature and complexity to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the design and construction sequences, is required. The scheduling of the project is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development. Personnel working on the project shall 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.

SECTION 01 32 01 Page 1

SECTION 01 32 01

PROJECT SCHEDULE

08/08

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)

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 (TRO = Tulsa Resident Office). The following shall be submitted in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Schedule; G, TRO

1.3 QUALITY ASSURANCE

Designate an authorized representative to be responsible for the preparation of the schedule and all required updating (activity status) and preparation of reports. The authorized representative shall be experienced in scheduling projects similar in nature and complexity to this project and shall be experienced in the use of the scheduling software that meets the requirements of this specification.

PART 2 PRODUCTS (NOT USED)

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to the Contract Clause, SCHEDULE FOR CONSTRUCTION CONTRACTS. Show in the schedule the sequence in which the Contractor proposes to perform the work and dates on which the Contractor contemplates starting and completing all schedule activities. The scheduling of the entire project, including the design and construction sequences, is required. The scheduling of the project is the responsibility of the Contractor. Contractor management personnel shall actively participate in its development. Personnel working on the project shall 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.

SECTION 01 32 01 Page 1

3.1.1 Approved Project Schedule

Use the approved Project Schedule to measure the progress of the work and to aid in evaluating time extensions.

3.1.2 Schedule Status Reports

Provide a Schedule Status Report on at least a monthly basis. If, in the opinion of the Contracting Officer, the Contractor falls behind the approved schedule, the Contractor shall take steps necessary to improve its progress including those that may be required by the Contracting Officer, without additional cost to the Government. In this circumstance, the Contracting Officer may require the Contractor to increase the number of shifts, overtime operations, days of work, and/or the amount of construction plant, and to submit for approval any supplementary schedule or schedules as the Contracting Officer deems necessary to demonstrate how the approved rate of progress will be regained.

3.1.3 Default Terms

Failure of the Contractor to comply with the requirements of the Contracting Officer shall be grounds for a determination, by the Contracting Officer, that the Contractor is not prosecuting the work with sufficient diligence to ensure completion within the time specified in the contract. Upon making this determination, the Contracting Officer may terminate the Contractor's right to proceed with the work, or any separable part of it, in accordance with the default terms of the contract.

3.2 BASIS FOR PAYMENT

The schedule shall be the basis for measuring Contractor progress. Lack of an approved schedule update, or qualified scheduling personnel, will result in the inability of the Contracting Officer to evaluate the Contractor's progress for the purposes of payment. Failure of the Contractor to provide all required information, as specified below, will result in the disapproval of the entire Project Schedule submission and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes. In the event schedule revisions are directed by the Contracting Officer and those revisions have not been included in subsequent revisions or updates, the Contracting Officer may hold retainage up to the maximum allowed by contract, each payment period, until such revisions to the Project Schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

The computer software system utilized to produce and update the Project Schedule shall be capable of meeting all requirements of this specification. Failure of the Contractor to meet the requirements of this specification will result in the disapproval of the schedule. Manual methods used to produce any required information shall require approval by the Contracting Officer.

3.3.1 Critical Path Method

Use the Critical Path Method (CPM) of network calculation to generate the Project Schedule. Prepare the Project Schedule using the Precedence Diagram Method (PDM).

SECTION 01 32 01 Page 2

3.3.2 Level of Detail Required

Develop the Project Schedule to an appropriate level of detail. Failure to develop the Project Schedule to an appropriate level of detail, as determined by the Contracting Officer, 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.1 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods. Less than two percent of all non-procurement activities shall have Original Durations (OD) greater than 20 work days or 30 calendar days. Procurement activities are defined herein.

3.3.2.2 Procurement Activities

The schedule must include activities associated with the submittal, approval, 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. A typical procurement sequence includes the string of activities: submit, approve, procure, fabricate, and deliver.

3.3.2.3 Mandatory Tasks

The following tasks must be included and properly scheduled:

a. Submission, review and acceptance of design packages.

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

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

e. Not used.

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

g. Submission of TAB specialist design review report.

h. Submission and approval of fire protection specialist.

i. Submission and approval of testing and balancing of HVAC plus commissioning plans and data. Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with ECB 2005-10.

j. Air and water balancing.

k. HVAC commissioning.

l. Controls testing plan submission.

m. Controls testing.

n. Performance Verification testing.

SECTION 01 32 01 Page 3

o. Other systems testing, if required.

p. Contractor's pre-final inspection.

q. Correction of punchlist from Contractor's pre-final inspection.

r. Government's pre-final inspection.

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

t. Final inspection.

3.3.2.4 Government Activities

Show Government and other agency activities that could impact progress.

These activities include, but are not limited to: inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.2.5 Responsibility

All activities shall be identified in the project schedule by the party responsible to perform the work. Responsibility includes, but is not limited to, the subcontracting firm, contracting work force, or government agency performing a given task. Activities shall not belong to more than one responsible party. The responsible party for each activity shall be identified by the Responsibility Code.

3.3.2.6 Work 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. Activities shall not have more than one Work Area Code. Not all activities are required to be Work Area coded. A lack of Work Area coding will indicate the activity is not resource or space constrained.

3.3.2.7 Contract Changes/Requests for Equitable Adjustment (REA) Coding

(MODF)

Assign Activity code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by the Contracting Officer, with a Contract Changes/REA Code. Key all Code values to the Government's modification numbering system. Any activity or sequence of activities added to the schedule as a result of alleged constructive changes made by the Government may be added to a copy of the current schedule, subject to the approval of the Contracting Officer.

Assign Activity codes for these activities with a Contract Changes/REA Code. Key the code values to the Contractor's numbering system. Approval to add these activities does not necessarily mean the Government accepts responsibility and, therefore, liability for such activities and any associated impacts to the schedule, but rather the Government recognizes such activities are appropriately added to the schedule for the purposes of maintaining a realistic and meaningful schedule. Such activities shall not be Responsibility Coded to the Government unless approved. An activity shall not have more than one Contract Changes/REA Code.

SECTION 01 32 01 Page 4

3.3.2.8 Proposal Item/Contract Line Item (CLIN)

All activities shall be identified in the project schedule by the Proposal Item/CLIN to which the activity belongs. An activity shall not contain work in more than one Proposal Item/CLIN. The item for each appropriate activity shall be identified by the Proposal Item/CLIN code.

3.3.2.9 Phase of Work

All activities shall be identified in the project schedule by the phase of work in which the activity occurs. Activities shall not contain work in more than one phase of work. The project phase of each activity shall be by the unique Phase of Work Code.

3.3.2.10 Category of Work Coding (CATW)

Assign Category of Work Code to all Activities based upon the category of work to which the activity belongs. Category of Work Code must include, but is not limited to: Approvals, Acceptance, Procurement, Fabrication, Delivery, Weather Sensitive Installation, Non-Weather Sensitive Installation, Start-Up, Test and Turnover. Assign a Category of Work Code to each activity. Each activity shall have only one Category of Work Code.

3.3.2.11 Definable Features of Work Coding (FOW1, FOW2, FOW3)

Assign a Definable Feature of Work Code to appropriate activities based on the definable feature of work to which the activity belongs. An activity shall not have more than one Definable Feature of Work Code. Not all activities are required to be Definable Feature of Work Coded.

3.3.3 Scheduled Project Completion and Activity Calendars

The schedule interval shall extend from NTP date to the required contract completion date. The contract completion activity (End Project) shall finish based on the required contract duration in the accepted contract proposal, as adjusted for any approved contract time extensions. The first scheduled work period shall be the day after NTP is received by the Contractor. Schedule activities on a calendar to which the activity logically belongs. Activities may be assigned to a seven day calendar when the contract assigns calendar day durations for the activity such as a Government Acceptance activity. If the Contractor intends to perform physical work less than seven days per week, schedule the associated activities on a calendar with non-work periods identified including weekends and holidays. Assign the Category of Work Code - Weather Sensitive Installation to those activities that are weather sensitive.

Original durations must account for anticipated normal adverse weather.

The Government will interpret all work periods not identified as non-work periods on each calendar as meaning the Contractor intends to perform work during those periods.

3.3.3.1 Project Start Date

The schedule shall start no earlier than the date on which the NTP was acknowledged. Include as the first activity in the project schedule an activity called "Start Project"( or NTP). The "Start Project" activity shall have an "ES" constraint date equal to the date that the NTP was acknowledged, and a zero day duration.

SECTION 01 32 01 Page 5

3.3.3.2 Schedule Constraints and Open Ended Logic

Constrain completion of the last activity in the schedule by the contract completion date. Schedule calculations shall result in a negative float when the calculated early finish date of the last activity is later than the contract completion date. Include as the last activity in the project schedule an activity called "End Project". The "End Project" activity shall have an "LF" constraint date equal to the contract completion date for the project, and with a zero day duration or by using the "project must finish by" date in the scheduling software. The schedule shall have no constrained dates other than those specified in the contract. The use of artificial float constraints such as "zero fee float" or "zero total float" are typically prohibited. There shall only be 2 open ended activities:

Start Project (or NTP) with no predecessor logic and End Project with no successor logic.

3.3.3.3 Early Project Completion

In the event the Preliminary or Initial project schedule calculates an early completion date of the last activity prior to the contract completion date, identify those activities that it intends to accelerate and/or those activities that are scheduled in parallel to support the Contractor's "early" completion. The last activity shall have a late finish constraint equal to the contract completion date and the schedule will calculate positive float. The Government will not approve an early completion schedule with zero float on the longest path. The Government is under no obligation to accelerate activities for which it is responsible to support a proposed early contract completion.

3.3.4 Interim Completion Dates

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

3.3.4.1 Start Phase

Include as the first activity for a project phase an activity called "Start Phase X" where "X" refers to the phase of work. The "Start Phase X" activity shall have an "ES" constraint date equal to the date on which the NTP was acknowledged, and a zero day duration.

3.3.4.2 End Phase

Include as the last activity for a project phase an activity called "End Phase X" where "X" refers to the phase of work. The "End Phase X" activity shall have an "LF" constraint date equal to the specified completion date for that phase and a zero day duration.

3.3.4.3 Phase "X" Hammock

Include a hammock type activity for each project phase called "Phase X" where "X" refers to the phase of work. The "Phase X" hammock activity shall be logically tied to the earliest and latest activities in the phase.

3.3.5 Default Progress Data Disallowed

Do not automatically update Actual Start and Finish dates with default mechanisms that may be included in the scheduling software. Activity

SECTION 01 32 01 Page 6

Actual Start (AS) and Actual Finish (AF) dates assigned during the updating process shall match those dates provided from Contractor Quality Control Reports. Failure of the Contractor to document the AS and AF dates on the Daily Quality Control report for every in-progress or completed activity, and failure to ensure that the data contained on the Daily Quality Control reports is the sole basis for schedule updating shall result in the disapproval of the Contractor's updated schedule and the inability of the Contracting Officer to evaluate Contractor progress for payment purposes.

Updating of the percent complete and the remaining duration of any activity shall be independent functions. Disable program features which calculate one of these parameters from the other.

3.3.6 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 all out of sequence progress or justify not changing the sequencing for approval prior to submitting an updated project schedule. Correct out of sequence progress that continues for more than two update cycles by logic revision, as approved by the Contracting Officer.

3.3.7 Negative Lags and Start to Finish Relationships

Lag durations contained in the project schedule shall not have a negative value. Do not use Start to Finish (SF) relationships.

3.3.8 Calculation Mode

Schedule calculations shall retain the logic between predecessors and successors even when the successor activity starts and the predecessor activity has not finished. 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") will not be allowed.

3.3.9 Milestones

The schedule must include milestone activities for each significant project event including but not limited to: milestone activities for each fast track design package released for construction; design complete;

foundation/substructure construction complete; superstructure construction complete; building dry-in or enclosure complete to allow the initiation of finish activities; permanent power complete; and building systems commissioning complete.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD, reports, and network diagrams required for each submission are contained in paragraph

SUBMISSION REQUIREMENTS.

3.4.1 Preliminary Project Schedule Submission

Submit the Preliminary Project Schedule, defining the Contractor's planned operations for the first 90 calendar days for approval within 15 calendar days after the NTP is acknowledged. 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

SECTION 01 32 01 Page 7 balance the contract award CLINS shown on the Price Schedule. Detail it for the first 90 calendar days. It may be summary in nature for the remaining performance period. It must be early start and late finish constrained and logically tied as previously 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, the 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. Schedule any construction activities planned for the first 90 calendar days after NTP. Constrain planned construction activities by Government acceptance of the associated design package(s) and all other specified Program and Plan approvals. Activity code any activities that are summary in nature after the first 90 calendar days with Responsibility Code (RESP) and Feature of Work code (FOW1, FOW2, FOW3).

3.4.2 Initial Project Schedule Submission

Submit the Initial Project Schedule for approval within 14 calendar days after NTP. The schedule shall demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period. The Initial Schedule shall be at a reasonable level of detail as determined by the Contracting Officer.

3.4.3 Periodic Schedule Updates

Based on the result of the meeting, specified in PERIODIC SCHEDULE UPDATE MEETINGS, submit periodic schedule updates. These submissions will enable the Contracting Officer to assess Contractor's progress. If the Contractor fails or refuses to furnish the information and project schedule data, which in the judgment of the Contracting Officer or authorized representative is necessary for verifying the Contractor's progress, the Contractor shall be deemed not to have provided an estimate upon which progress payment may be made.

3.4.4 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11, Appendix A. This exact structure is mandatory, even if some fields are not used. A template SDEF compatible schedule backup file (sdef.prx) is available on the QCS website:

http://rms.usace.army.mil/. The SDEF format is as follows:

SDEF Format

Field Activity Code Length Description

1 WRKP 3 Workers per Day

2 RESP 4 Responsible Party (e.g. GC, subcontractor, USACE)

3 AREA 4 Area of Work

4 MODF 6 Modification or REA number

SECTION 01 32 01 Page 8

SDEF Format

Field Activity Code Length Description

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of Work

7 CATW 1 Category of Work

8 FOW1 10 Feature of Work (used up to 10 characters in length)

9 FOW2 10 Feature of Work (used up to 20 characters in length)

10 FOW3 10 Feature of Work (used up to 30 characters in length)

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:

3.5.1 Data CD's

Provide two sets of data CD's containing the project schedule in the backup format. Each CD shall also contain all previous update backup files. File medium shall be CD. Label each CD indicating the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and file name. Each schedule shall have a unique file name as determined by the Contractor.

3.5.2 Narrative Report

Provide a Narrative Report with the Preliminary, Initial, and each Periodic Update of the project schedule, as the basis of the progress payment request. The Narrative Report shall include: a description of activities along the 2 most critical paths where the total float is less than or equal to 20 work days, 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. The narrative report is expected to communicate to the Government, the Contractor's thorough analysis of the schedule output and its plans to compensate for any problems, either current or potential, which are revealed through that analysis. Identify and explain why any activities that, based their calculated late dates, should have either started or finished during the update period but did not.

3.5.3 Approved Changes Verification

Include only those project schedule changes in the schedule submission that have been previously approved by the Contracting Officer. The Narrative Report shall specifically reference, on an activity by activity basis, all changes made since the previous period and relate each change to documented, approved schedule changes.

3.5.4 Schedule Reports

The format, filtering, organizing and sorting for each schedule report

SECTION 01 32 01 Page 9 shall be as directed by the Contracting Officer. Typically reports shall 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. The following lists typical reports that will be requested. One or all of these reports may be requested for each schedule submission.

3.5.4.1 Activity Report

A list of all activities sorted according to activity number.

3.5.4.2 Logic Report

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

3.5.4.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.4.4 Earnings Report by Proposal Item/CLIN

A compilation of the Contractor's Total Earnings on the project from the NTP to the data date. This report shall reflect the earnings of specific activities based on the agreements made in the schedule update meeting defined herein. Provided that the Contractor has furnished a complete schedule update, this report shall serve as the basis of determining progress payments. Group activities by CLIN item number and sort by activity number. This report shall: sum all activities coded to a particular CLIN and provide a CLIN item percent earned value; and complete and sum CLIN items to provide a total project percent complete. The printed report shall contain, for each activity: the Activity Number, Activity Description, Original Budgeted Amount, Total Quantity, Quantity to Date, Percent Complete (based on cost), and Earnings to Date.

3.5.5 Network Diagram

The network diagram is required for the Preliminary, Initial and Periodic Updates. The network diagram shall depict and display the order and interdependence of activities and the sequence in which the work is to be accomplished. The Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.5.1 Continuous Flow

Diagrams shall show a continuous flow from left to right with no arrows from right to left. Show the activity number, description, duration, and estimated earned value on the diagram.

3.5.5.2 Project Milestone Dates

Show dates on the diagram for start of project, any contract required interim completion dates, and contract completion dates.

SECTION 01 32 01 Page 10 ED Woman Owned Small Business MATOC FY12EDWOSBMATOCFY12

3.5.5.3 Critical Path

Clearly show the critical path.

3.5.5.4 Banding

Organize activities as directed to assist in the understanding of the activity sequence. Typically, this flow will group activities by category of work, work area and/or responsibility.

3.5.5.5 S-Curves

Earnings curves showing projected early and late earnings and earnings to date.

3.6 PERIODIC SCHEDULE UPDATE MEETINGS

Conduct periodic schedule update meetings for the purposes of reviewing the Contractor's proposed out of sequence corrections, determining causes for delay, correcting logic, maintaining schedule accuracy and determining earned value. Meetings shall occur at least monthly within five days of the proposed schedule data date and after the Contractor has updated the schedule with Government concurrence respecting actual start dates, actual finish dates, remaining durations and percent complete for each activity it intend to status. Provide a computer with the scheduling software loaded and a projector during the meeting which allows all meeting participants to view the proposed schedule update during the meeting. The meeting and resultant approvable schedule update shall be a condition precedent to a formal submission of the update as described in SUBMISSION REQUIREMENTS and to the submission of an invoice for payment. The meeting will be a working interactive exchange which will allow the Government and the Contractor the opportunity to review the updated schedule on a real time and interactive basis. The Contractor's authorized scheduling representative will organize, sort, filter and schedule the update as requested by the Government. The meeting will last no longer than 8 hours. A rough draft of the proposed activity logic corrections and narrative report shall be provided to the Government 48 hours in advance of the meeting. The Contractor's Project Manager and Authorized Scheduler shall attend the meeting with the Authorized Representative of the Contracting Officer.

3.6.1 Update Submission Following Progress Meeting

Submit a complete update of the project schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 working days after the periodic schedule update meeting, reflecting only those changes made during the previous update meeting.

3.6.2 Status of Activities

Update information, including Actual Start Dates (AS), Actual Finish Dates (AF), Remaining Durations (RD), and Percent Complete shall be subject to the approval of the Government prior to the meeting. As a minimum, address the following items on an activity by activity basis during each progress meeting.

3.6.2.1 Start and Finish Dates

Accurately show the status of the AS and/or AF dates for each activity

SECTION 01 32 01 Page 11 currently in-progress or completed since the last update. Only assign AS dates when actual progress occurs on an activity.

3.6.2.2 Remaining Duration

Update the estimated RD for all incomplete activities independent of Percent Complete. Remaining Durations may exceed the activity OD or may exceed the activity's prior update RD if the Government considers the current OD or RD to be understated based on current progress, insufficient work crews actually manning the job, unrealistic OD or deficiencies that must be corrected that restrain successor activities.

3.6.2.3 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, cost load the correction of punch list from Government pre-final inspection activity(ies) not less than 1 percent of the total contract value, which activity(ies) may be declared 100 percent complete upon completion and correction of all punch list work identified during Government pre-final inspection(s).

3.6.2.4 Logic Changes

Specifically identify and discuss all logic changes pertaining to NTP on change orders, change orders to be incorporated into the schedule, Contractor proposed changes in work sequence, corrections to schedule logic for out-of-sequence progress, and other changes that have been made pursuant to contract provisions. The Government will only approve logic revisions for the purpose of keeping the schedule valid in terms of its usefulness in calculating a realistic completion date, correcting erroneous logic ties, and accurately sequencing the work.

3.6.2.5 Other Changes

Other changes required due to delays in completion of any activity or group of activities include: 1) delays beyond the Contractor's control, such as strikes and unusual weather.