ATTACHMENT 1 Scope of Work MATOC.docx

SCOPE OF WORK

DEPOT-WIDE MINOR CONSTRUCTION

MULTIPLE AWARD INDEFINITE DELIVERY INDEFINITE QUANTITY (IDIQ)

MULTIPLE AWARD TASK ORDER CONTRACT

(MATOC)

TOBYHANNA ARMY DEPOT

11 HAP ARNOLD BOULEVARD

TOBYHANNA, PA 18466

December 2020

TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01 PROJECT SCHEDULE

01 32 33 CONSTRUCTION PHOTOGRAPHY

01 33 00 SUBMITTAL PROCEDURES

01 33 16.00 10 DESIGN DATA (DESIGN AFTER AWARD)

01 33 29 SUSTAINABILITY REPORTING

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 35 53 ANTITERRORISM/OPERATIONS SECURITY (AT/OPSEC)

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00 QUALITY CONTROL

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19.00 06 TEMPORARY ENVIRONMENTAL CONTROLS AND PERMITS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 91 00.15 10 TOTAL BUILDING COMMISSIONING

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 82 14.00 10 ASBESTOS HAZARD CONTROL ACTIVITIES

02 83 13.00 20 LEAD IN CONSTRUCTION

02 84 16 HANDLING OF LIGHTING BALLASTS AND LAMPS CONTAINING PCBs

AND MERCURY

SECTION 01 11 00

SUMMARY OF WORK

1.0. General

1.1 Scope of Work. The objective for this Statement of Work (SOW) is to provide labor, equipment, tools, materials, supervision and transportation to successfully perform TO’s (task orders) associated with this Multiple Award Indefinite Delivery Indefinite Quantity (MATOC) contract for Tobyhanna Army Depot (TYAD). Contractors shall have the capability of 24-hour response, if necessary. Contractors must also have the capability of simultaneously managing numerous complex and multi-discipline projects. Work includes, but is not limited to depot-wide minor construction, repairs, maintenance alterations, emergency services and/or renovations. The contractor shall complete all work and services under this contract in accordance with schedules that are established in each task order. Submittal dates will be included in the individual task orders. These dates identify when information is due in the issuing Government office and other addresses identified in the individual task orders. The types and numbers submittals and dates and places for review meeting shall be established by each task order under this contract. The contractor will submit a Quality Control Plan and an Accident Prevention Plan to accommodate a basic NAICS Code 236220 projects requirements.

Background. Currently there are insufficient installation services directorate personnel to perform all infrastructure repairs, maintenance and minor construction services for the foreseeable long-term future considering the current staffing levels and the anticipated high volume of work that will be needed to implement and maintain existing and new buildings.

1.2 Qualifications for Award. The goal of this acquisition is to obtain high quality contractors at a reasonable and realistic price, providing the best value to the government thru this MATOC thru multiple awarded TO’s. Each firm-fixed price task order awarded will delineate the negotiated price, the scope of work and the performance period. The government will evaluate submitted Quality Control Plan (QCP) and Accident Prevention Plan (APP) for thoroughness in accordance with UFGS Quality Control Requirements and applicable United States Corps of Engineers (USACE) Construction Quality Control Management (CQCM) standards, processes and procedures, and United States Corps of Engineers Engineering Manual 385-1-1 (USACE-EM385)Site Safety and Health requirements and make multiple contract awards based on those plans without discussions with offerors (except clarifications as described in FAR 15.306(a).

1.3. Ordering Period: The contract ordering period shall be for five (5) years beginning May 2021 through April 2026

1.4. Notice to Proceed (NTP). Post notification of MATOC award and upon award of task order (TO), after acceptance and approval of the bonds and insurance, a NTP will be issued.

1.5. Duration of Project. Each firm-fixed price task order awarded will delineate its own individual performance period. Upon award of Bid Options, the POP may be adjusted for performance of Options.

1.6. Specifications. Detailed specifications shall be submitted as part of the design submission described in the individual task orders (TO) specifications in the event a TO is issued as a design build project. Utilize Specs Intact and Unified Facilities Guide Specifications (UFGS) for applicable specification sections relating to the project. Tobyhanna Army Depots (TYAD) base award specifications will be utilized for all TYAD task orders (TOs) associated with this MATOC IDIQ.

1.7. Cost Proposal_ Cost Narrative is required. In effort to allow the government the opportunity to fully evaluate and validate contractor pricing and desired intent of the cost proposal; for each individual task order (TO), the Contractor shall provide a written narrative to support the cost data in the contractors cost proposal. Detailed breakout for all pricing in proposal is required; lump sum pricing is unacceptable. Pricing shall include and explain the price proposal assumptions and methodologies. Cost proposal shall include a detailed narrative describing approach to accomplishing scope of work and clearly stating all assumptions included in proposal price.

1.8. Where Applicable. Cost Proposal_ Reconciliation of Contractor Pricing is required. As the basis for the contractor pricing and in an effort to assist the government with the reconciliation of which items in the contractor’s price proposal are considered New vs Re-used the contractor shall include a spreadsheet with the cost proposal which clearly state what those items are. This requirement is for each individual task order (TO) in which the contractor (once awarded the MATOC) choses to bid on.

2.0. DESCRIPTION

2.1 Project Description. The intent of this MATOC is to provide onsite supervision, transportation, materials, labor, administrative oversight, possible design(s) pending task order (TO) specifics and complete project management to be able to successfully accomplish the tasks in the individual task order(s) individual SOWs.

The Contractor’s efforts shall comply with the specifications and requirements contained herein and in each individual task orders SOW. The project requirements and technical criteria cited within this SOW establishes minimum standards for construction quality.

2.2. Overall Design and Renovation and Repair Activities. The Contractor shall prepare the work plan(s) and design for this project using the guidance and the requirements contained in this SOW, the various referenced requirements (UFCs, UFGS, etc.) and all applicable codes and standards including historical and preservation compliance.

The Contractor’s efforts shall comply with the specifications and requirements contained herein this SOW in accordance with the base contract Specifications. The project requirements and technical criteria cited within this SOW establishes minimum standards for construction quality.

SECTION 01 14 00

WORK RESTRICTIONS

1.1 SUBMITTALS

Government approval is required for submittals with a "G" designation; submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals Personnel List; G List of Contact Personnel; G Vehicle List; G Statement of Acknowledgement Form SF 1413; G

1.2 CONTRACTOR ACCESS AND USE OF PREMISES

1.2.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 hard hats in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Mark Contractor equipment for identification.

1.2.1.1 Subcontractors and Personnel Contacts

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

1.2.1.2 No Smoking Policy

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

1.2.2 Working Hours

Regular working hours for TYAD are 07:00 to 16:30 Monday through Friday, excluding Government holidays. The contractor will perform their contractual obligations within these times/days unless individual task order (TO) Specifications state otherwise.

1.2.3 Work Outside Regular Hours

Work outside regular working hours requires Government Designated Representative (GDR) 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 GDR 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 GDR. Make utility cutovers after normal working hours or on Saturdays, Sundays, and Government holidays unless directed otherwise.

1.2.4 Occupied Building

The Contractor shall be working in an existing building which is occupied. Do not enter the building without prior approval of the Government Designated Representative (GDR). 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 GDR. Provide dust covers or protective enclosures to protect existing work that remains and Government material located in the work area during the construction period. Relocate movable furniture as required to perform the work, protect the furniture, and replace the furniture in its original locations upon completion of the work. Leave attached equipment in place, and protect it against damage, or temporarily disconnect, relocate, protect, and reinstall it at the completion of the work. The Government will remove and relocate other Government property in the areas of the building scheduled to receive work.

1.2.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 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, and compressed air are considered utility cutovers pursuant to the paragraph WORK OUTSIDE REGULAR HOURS. Such interruptions are further limited to 6 hours. This time limit includes time for deactivation and reactivation.

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 GDR giving reasonable advance notice when such operation is required.

1.3 SECURITY REQUIREMENTS

Contract Clause FAR 52.204-2 Security Requirements and Alternate II, "FAC 5252.236-9301, Special Working Conditions and Entry to Work Area," and the following apply:

Submit Statement of Acknowledgement Form SF 1413.

1.3.1 Identification Badges

Identification badges, if required, will be furnished without charge. Application for and use of badges will be as directed. Furnish a completed EMPLOYMENT ELIGIBILITY VERIFICATION (DHS FORM I-9) form for all personnel requesting badges. This form is available at http://www.uscis.gov/files/form/I-9_IFR_02-02-09.pdf. Immediately report instances of lost or stolen badges to the Depot Security Office and to the Government Designated Representative (GDR).

1.3.2 1.4.1.4 Personnel Entry Approval Failure to obtain entry approval will not affect the contract price or time of completion.

SECTION 01 30 00

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

U.S. ARMY CORPS OF ENGINEERS (USACE) EM 385-1-1 (2014) Safety and Health Requirements Manual

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation; submittals not having a "G" designation are for information only. When used, designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals View Location Map; G Progress and Completion Pictures; G

1.3 VIEW LOCATION MAP

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

1.4 PROGRESS AND COMPLETION PICTURES

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

1.5 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.6 SUPERVISION

1.6.1 Minimum Communication Requirements

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

1.6.2 Superintendent Qualifications

The project superintendent must have a minimum of 10 years’ experience in construction with at least 5 of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Government Designated Representative (GDR) may request proof of the superintendent's qualifications at any point in the project or if the performance of the superintendent is in question. For minor construction routine projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00 QUALITY CONTROL the superintendent must have qualifications in accordance with that section.

1.6.2.1 Duties

The project superintendent is primarily responsible for managing and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.

1.6.3 Non-Compliance Actions

The contractor’s onsite management staff are subject to removal by the Government Designated Representative (GDR) for non-compliance with requirements specified in the contract and for failure to manage the project to insure timely completion. Furthermore, the GDR may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.

1.7 PRECONSTRUCTION CONFERENCE

After award of the contract but prior to commencement of any work at the site, meet with the Government Designated Representative (GDR) to discuss and develop a mutual understanding relative to the administration of the value engineering and safety program, preparation of the schedule of prices or earned value report, shop drawings, and other submittals, scheduling programming, prosecution of the work, and clear expectations of the "Interim DD Form 1354" Submittal. Major subcontractors who will engage in the work must also attend.

1.8 PARTNERING

To most effectively accomplish this contract, the Government requires the formation of a cohesive partnership within the Project Team whose members are from the Government, the Contractor and their Subcontractors. Key personnel from the Supported Command, the End User (who will occupy the facility), the Government Design and Construction team and Subject Matter Experts, the Installation, the Contractor and Subcontractors, and the Designer of Record will be invited to participate in the Partnering process. The Partnership will draw on the strength of each organization in an effort to achieve a project that is without any safety mishaps, conforms to the Contract, and stays within budget and on schedule. The Government Designated Representative (GDR) will provide Information on the Partnering Process and a list of key and optional personnel who should attend the Partnering meeting.

1.8.1 Informal Partnering

The GDR will organize the Partnering Sessions with key personnel of the project team, including Contractor personnel and Government personnel. The Initial Partnering session should be a part of the Pre-Construction Meeting. Partnering sessions will be held at a location agreed to by the GDR and the Contractor (typically a conference room provided by the Resident Engineer office or the Contractor). The Initial Informal Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by the GDR. The Partners will determine the frequency of the follow-on sessions, at no more than 3 to six month intervals.

1.9 ELECTRONIC MAIL (E-MAIL) ADDRESS

Establish and maintain electronic mail (e-mail) capability along with the capability to open various electronic attachments as text files, pdf files, and other similar formats. Within 10 days after contract award, provide the Government Designated Representative (GDR) a single (only one) e-mail address for electronic communications from the GDR related to this contract including, but not limited to contract documents, invoice information, request for proposals, and other correspondence. The GDR may also use email to notify the Contractor of base access conditions when emergency conditions warrant, such as hurricanes or terrorist threats. Multiple email addresses are not allowed. It is the Contractor's responsibility to make timely distribution of all GDR initiated e-mail with its own organization including field office(s). Promptly notify the GDR, in writing, of any changes to this email address.

1.10 MEETING INVITATIONS/NOTIFICATIONS

Notify the Government Designated Representative (GDR) of all scheduled meetings a minimum of 48 hours in advance utilizing Microsoft Office Outlook Invite for invitations/notifications unless otherwise noted.

SECTION 01 32 01

PROJECT SCHEDULE

PART 1 GENERAL

1.1 REFERENCES

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

AACE INTERNATIONAL (AACE)

AACE 29R-03 (2011) Forensic Schedule Analysis AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction U.S. ARMY CORPS OF ENGINEERS (USACE) ER 1-1-11 (1995) Administration -- Progress, Schedules, and Network Analysis Systems

1.2 SUBMITTALS

Government approval is required for submittals with a "G" designation; submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals Project Scheduler Qualifications; G 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 of 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.

2.1.1 Government Default Software

The Government intends to use Microsoft Project.

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 Microsoft Project compatible file must be created and supported by the software manufacturer.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15, SCHEDULE 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 is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. 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 Government Designated Representative (GDR).

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met. In the event that the Government Designated Representative (GDR) directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the GDR 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 Government Designated Representative (GDR) 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 of mechanical/electrical/information systems layout drawings.

c. Long procurement activities

d. Submission and approval of O & M manuals.

e. Submission and approval of as-built drawings.

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

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

h. Submission of TAB specialist design review report.

i. Submission and approval of fire protection specialist.

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

k. Air and water balancing.

l. Building commissioning - Functional Performance Testing.

m. Controls testing plan submission.

n. Controls testing.

o. Performance Verification testing.

p. Other systems testing, if required.

q. Contractor's pre-final inspection.

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

s. Government's pre-final inspection.

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

u. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress. These activities include, but are not limited to: environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.

3.3.6 Standard Activity Coding Dictionary

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein. A template SDEF compatible schedule backup file is available on the QCS web site: http://rms.usace.army.mil. The SDEF format is as follows:

Field Activity Code Length Description 1 WRKP 3 Workers per day 2 RESP 4 Responsible party 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 Field Activity Code Length Description 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 Government Designated Representative (GDR). Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.6.2 Responsible Party Coding (RESP)

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency (ies) responsible for performing the activity.

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, Government design reviews, environmental permit approvals by State regulators, Government Furnished Property/Equipment (GFP) and Notice to Proceed (NTP) for phasing requirements.

b. Activities cannot have more than one Responsibility Code. Examples of acceptable activity code values are: DOR (for the designer of record); ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for USACE).

3.3.6.3 Area of Work Coding (AREA)

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Examples of Work Area Coding include different areas within a floor of a building, different floors within a building, and different buildings within a complex of buildings. Activities cannot have more than one Work Area Code. Not all activities are required to be Work Area coded. A lack of Work 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 GDR. 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 work are procurement phase and construction phase. Each activity can have only one Phase of Work code.

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

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

c. 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 submittals, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.3.6.8 Feature of Work Coding (FOW)

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

Definable Feature of Work is defined in Section 01 45 00 QUALITY CONTROL. An activity can have only one Feature of Work Code.

3.3.7 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited. Mandatory constraints that ignore or effect network logic are prohibited. No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Government Designated Representative (GDR) 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 Seasonal 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 days provided in the contract clause TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends.

3.3.9 Open Ended Logic

Only two open ended activities are allowed: the first activity "NTP Acknowledged" may have no predecessor logic, and the last activity -"End Project" may have no successor logic. Predecessor open ended logic may be allowed in a time impact analyses upon the Government Designated Representative (GDR)'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 Government Designated Representative (GDR). 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 Government Designated Representative (GDR). Activity ID and description changes are considered new activities and cannot be changed without GDR 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 Government Designated Representative (GDR).

3.3.14 Leads, Lags, and Start to Finish Relationships

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

a. Leads (negative lags) are prohibited.

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

3.3.15 Retained Logic

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

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, whichever 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 Anticipated Adverse Weather

Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

3.3.20 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 man-hours) and the Government agreeing that the schedule is reasonable and achievable.

b. The Government is under no obligation to accelerate work items it is responsible for to ensure that the early completion is met nor is it responsible to modify incremental funding (if applicable) for the project to meet the contractor's accelerated work.

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data CD/DVD, reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS. If the Contractor fails or refuses to furnish the information and schedule updates as set forth herein, then the Contractor will be deemed not to have provided an estimate upon which a 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:

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 Government Designated Representative (GDR). 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.

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. The Government Designated Representative (GDR) will use, but is not limited to, the following conditions to review compliance with this paragraph:

3.5.4.1 Continuous Flow

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.4.2 Project Milestone Dates

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

3.5.4.3 Critical Path

Show all activities on the critical path. The critical path is defined as the longest path.

3.5.4.4 Banding

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

3.5.4.5 Cash Flow / Schedule Variance Control (SVC) Diagram

With each schedule submission, provide a SVC diagram showing 1) Cash Flow S-Curves indicating planned project cost based on projected early and late activity finish dates, and 2) Earned Value to-date.

3.6 PERIODIC SCHEDULE UPDATE

3.6.1 Periodic Schedule Update Meetings

Conduct periodic schedule update meetings for the purpose of reviewing the proposed Periodic Schedule Update, Narrative Report, Schedule Reports, and progress payment. Conduct meetings at least monthly within five days of the proposed schedule data date. Provide a computer with the scheduling software loaded and a projector which allows all meeting participants to view the proposed schedule during the meeting. The Contractor's authorized scheduler must organize, group, sort, filter, perform schedule revisions as needed and review functions as requested by the Contractor and/or Government. The meeting is a working interactive exchange which allows the Government and Contractor the opportunity to review the updated schedule on a real time and interactive basis. The meeting will last no longer than 8 hours.