2021-08-27_FPBB142001-B-3_Specs_Clean.pdf

TYPE B-3

FINAL DESIGN

SUBMITTAL

SPECIFICATIONS

CONSTRUCT OPERATIONS SPACE/MGCS

SHELTER

Contract No.: W9133L-15-D-0004

Task Order No.: W50S8N20F0014

ANG Project No.: FPBB142001

HDR Project No. 10256943

Fort Drum, New York

August 2021

FTDRUM FPBB142001

PROJECT TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 08/15 SUMMARY OF WORK

01 32 01.00 10 02/15 PROJECT SCHEDULE

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

01 33 29 02/21 SUSTAINABILITY REQUIREMENTS AND

REPORTING

01 35 26 11/20 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 11/16, CHG 1: 02/20 QUALITY CONTROL

01 57 19 11/15, CHG 4: 08/20 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 02/19, CHG 1: 08/20 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

01 78 00 05/19 CLOSEOUT SUBMITTALS

01 78 23 08/15, CHG 1: 11/20 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 05/10, CHG 2: 02/19 DEMOLITION

DIVISION 03 - CONCRETE

03 30 00 02/19, CHG 1: 02/21 CAST-IN-PLACE CONCRETE

DIVISION 05 - METALS

05 05 23.13 10 08/18 ULTRASONIC INSPECTION OF WELDMENTS

05 50 13 05/17 MISCELLANEOUS METAL FABRICATIONS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 08/16, CHG 2: 11/18 ROUGH CARPENTRY

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 21 13 02/16 BOARD AND BLOCK INSULATION

07 21 16 11/11 MINERAL FIBER BLANKET INSULATION

07 27 10.00 10 08/19, CHG 1: 02/20 BUILDING AIR BARRIER SYSTEM

07 60 00 05/17, CHG 2: 11/18 FLASHING AND SHEET METAL

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

07 92 00 08/16, CHG 3: 11/18 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 08/20 STEEL DOORS AND FRAMES

08 33 23 08/20 OVERHEAD COILING DOORS

08 71 00 02/16, CHG 3: 08/20 DOOR HARDWARE

DIVISION 09 - FINISHES

09 06 00 05/09, CHG 1: 11/13 SCHEDULES FOR FINISHES

09 22 00 02/10, CHG 2: 08/18 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 08/16, CHG 4: 02/20 GYPSUM BOARD

DIVISION 13 - SPECIAL CONSTRUCTION

13 34 19 08/20, CHG 1: 02/21 METAL BUILDING SYSTEMS

PROJECT TABLE OF CONTENTS Page 1

DIVISION 21 - FIRE SUPPRESSION

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

PROTECTION

DIVISION 22 - PLUMBING

22 00 00 11/15, CHG 3: 08/18 PLUMBING, GENERAL PURPOSE

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

23 05 15 02/14 COMMON PIPING FOR HVAC

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

HVAC

23 07 00 02/13, CHG 7: 05/20 THERMAL INSULATION FOR MECHANICAL

SYSTEMS

23 09 00 02/19, CHG 2: 02/20 INSTRUMENTATION AND CONTROL FOR HVAC

23 11 20 05/20 FACILITY GAS PIPING

23 23 00 10/07 REFRIGERANT PIPING

23 30 00 05/20 HVAC AIR DISTRIBUTION

23 54 19 11/08, CHG 2: 08/18 BUILDING HEATING SYSTEMS, WARM AIR

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

23 81 29 02/20 VARIABLE REFRIGERANT FLOW HVAC SYSTEMS

DIVISION 25 - INTEGRATED AUTOMATION

25 05 11.02 11/17 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS - CYBER DURING

CONSTRUCTION

DIVISION 26 - ELECTRICAL

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

26 51 00 05/20 INTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 10 00 08/11 BUILDING TELECOMMUNICATIONS CABLING

SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 76 08/20 INTERIOR FIRE ALARM AND MASS

NOTIFICATION SYSTEM, ADDRESSABLE

DIVISION 31 - EARTHWORK

31 00 00 08/08, CHG 2: 02/21 EARTHWORK

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 16 19 05/18 SIDEWALKS

32 92 19 08/17 SEEDING

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 2

SECTION 01 11 00

SUMMARY OF WORK

08/15

PART 1 GENERAL

1.1 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. Submit the following in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

1.2 WORK COVERED BY CONTRACT DOCUMENTS

1.2.1 Project Description

The work includes FPBB142001 MGCS Shelter and incidental related work.

1.2.2 Location

The work is located at the Wheeler Sack Army Airfield, Fort Drum, NY as indicated. The exact location will be shown by the Government and is depicted in the Contract Drawings .

1.3 OCCUPANCY OF PREMISES

The existing remote piloted aircraft (RPA) hangars and utility rooms will be occupied during performance of work under this Contract.

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

1.4 EXISTING WORK

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

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

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

1.5 LOCATION OF UNDERGROUND UTILITIES

Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.

Coordinate with the Government at least 14 days prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.

SECTION 01 11 00 Page 1

Identify and mark all utilities . Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities are discovered. Verify the elevations of existing piping, utilities,and any type of underground obstruction , or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed.

1.5.1 Notification Prior to Excavation

Contractor shall adhere to the requirements outlined in Garrison Policy Memorandum #17-11, Excavation Permits. Notify the Contracting Officer at least 7 days prior to starting excavation work.

PART 2 PRODUCTS

Not used.

PART 3 EXECUTION

Not used.

-- End of Section --

SECTION 01 11 00 Page 2

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

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

AIR NATIONAL GUARD ENGINEERING TECHNICAL LETTERS (ANGETL)

AACE 29R-03 (2011) Forensic Schedule Analysis

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

1.2 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals Project Scheduler Qualifications ; G

Initial Project Schedule ; G Periodic Schedule Update ; G

1.3 PROJECT SCHEDULER QUALIFICATIONS

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

PART 2 PRODUCTS

2.1 SOFTWARE

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

2.1.1 Government Default Software

The Government intends to use Primavera P6.

SECTION 01 32 01.00 10 Page 1

2.1.2 Contractor Software

Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.

2.1.2.1 Primavera

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system.

2.1.2.2 Other Than Primavera

If the contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.

Prepare each Project Schedule using the Precedence Diagram Method (PDM).

3.2 BASIS FOR PAYMENT AND COST LOADING

The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment. The aggregate value of all activities coded to a contract CLIN must equal the value of the CLIN.

3.2.1 Activity Cost Loading

Activity cost loading must be reasonable and without front-end loading.

Provide additional documentation to demonstrate reasonableness if requested by the Contracting Officer.

3.2.2 Withholdings / Payment Rejection

Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and

SECTION 01 32 01.00 10 Page 2 those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

Develop the Project Schedule to the appropriate level of detail to address major milestones and to allow for satisfactory project planning and execution. Failure to develop the Project Schedule to an appropriate level of detail will result in its disapproval. The Contracting Officer will consider, but is not limited to, the following characteristics and requirements to determine appropriate level of detail:

3.3.2 Activity Durations

Reasonable activity durations are those that allow the progress of ongoing activities to be accurately determined between update periods.

Less than 2 percent of all non-procurement activities may have Original Durations (OD) greater than 20 work days or 30 calendar days.

3.3.3 Procurement Activities

Include activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.

3.3.4 Mandatory Tasks

Include the following activities/tasks in the initial project schedule and all updates.

a. Submission, review and acceptance of SD-01 Preconstruction Submittals .

b. Long procurement activities

c. Submission and approval of O & M manuals.

d. Submission and approval of as-built drawings.

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

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

SECTION 01 32 01.00 10 Page 3 j . Air and water balancing.

k. Building commissioning - Functional Performance Testing.

l . Controls testing plan submission.

m. Controls testing.

n. Performance Verification testing.

o. Other systems testing, if required.

p. Contractor's pre-final inspection.

q. Correction of punch list 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.5 Contract Milestones and Constraints

Milestone activities are to be used for significant project events including, but not limited to, project phasing, project start and end activities, or interim completion dates. The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.

Mandatory constraints that ignore or effect network logic are prohibited.

No constrained dates are allowed in the schedule other than those specified herein. Submit additional constraints to the Contracting Officer for approval on a case by case basis.

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

SECTION 01 32 01.00 10 Page 4 in that phase is later than the specified interim completion date.

3.3.5.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.5.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.6 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.

If an activity is weather sensitive it should be assigned to a calendar showing non-work days on a monthly basis, with the non-work days selected at random across the weeks of the calendar, using the anticipated adverse weather delay work days provided in the Special Contract . 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.7 Open Ended Logic

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

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

3.3.8 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.9 Out-of-Sequence Progress

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

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

SECTION 01 32 01.00 10 Page 5

3.3.10 Added and Deleted Activities

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

3.3.11 Original Durations

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

3.3.12 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.13 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.14 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.15 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.16 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity not less than 1 percent of the present contract value. Activity 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).

SECTION 01 32 01.00 10 Page 6

3.3.16.1 As-Built Drawings

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

3.3.16.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.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The data 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 do not relieve the Contractor from compliance with requirements of the Contract Documents.

3.4.1 Project Schedule Submission

Within 15 calendar days after the NTP is acknowledged submit the Project Schedule defining the planned operations detailed for approval. The approved Project Schedule will be used for payment purposes not to exceed 90 calendar days. Completely cost load the Project Schedule to balance the contract award CLINS shown on the Price Schedule. The 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.

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

3.5 SUBMISSION REQUIREMENTS

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

3.5.1 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

SECTION 01 32 01.00 10 Page 7 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.2 Schedule Reports

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

3.5.2.1 Activity Report

List of all activities sorted according to activity number.

3.5.2.2 Logic Report

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

3.5.2.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 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 Contracting Officer will use, but is not limited to, the following conditions to review compliance with this paragraph:

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

SECTION 01 32 01.00 10 Page 8 earned value on the diagram.

3.5.3.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.3.3 Critical Path

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

3.5.3.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.3.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. Provide a draft of the proposed narrative report and schedule data file to the Government a minimum of two workdays in advance of the meeting. The Contractor's Project Manager and scheduler must attend the meeting with the authorized representative of the Contracting Officer. Superintendents, foremen and major subcontractors must attend the meeting as required to discuss the project schedule and work.

Following the periodic schedule update meeting, make corrections to the draft submission. Include only those changes approved by the Government in the submission and invoice for payment.

3.6.2 Update Submission Following Progress Meeting

Submit the complete Periodic Schedule Update of the Project Schedule containing all approved progress, revisions, and adjustments, pursuant to paragraph SUBMISSION REQUIREMENTS not later than 4 work days after the periodic schedule update meeting.

SECTION 01 32 01.00 10 Page 9

3.7 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) between the meetings described in paragraph entitled PERIODIC SCHEDULE UPDATE MEETINGS for the purpose of jointly reviewing the actual progress of the project as compared to the as planned progress and to review planned activities for the upcoming two weeks. Use the current approved schedule update for the purposes of this meeting and for the production and review of reports. At the weekly progress meeting, address the status of RFIs, RFPs and Submittals.

3.8 REQUESTS FOR TIME EXTENSIONS

Provide a justification of delay to the Contracting Officer in accordance with the contract provisions and clauses for approval within 10 days of a delay occurring. Also prepare a time impact analysis for each Government request for proposal (RFP) to justify time extensions.

3.8.1 Justification of Delay

Provide a description of the event(s) that caused the delay and/or impact to the work. As part of the description, identify all schedule activities impacted. Show that the event that caused the delay/impact was the responsibility of the Government. Provide a time impact analysis that demonstrates the effects of the delay or impact on the project completion date or interim completion date(s). Evaluate multiple impacts chronologically; each with its own justification of delay. With multiple impacts consider any concurrency of delay. A time extension and the schedule fragnet becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.8.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by the Contracting Officer based on industry standard AACE 52R-06 . Utilize a copy of the last approved schedule prior to the first day of the impact or delay for the time impact analysis. If Contracting Officer determines the time frame between the last approved schedule and the first day of impact is too great, prepare an interim updated schedule to perform the time impact analysis. Unless approved by the Contracting Officer, no other changes may be incorporated into the schedule being used to justify the time impact.

3.8.3 Forensic Schedule Analysis (Retrospective Analysis)

Prepare an analysis for approval by the Contracting Officer based on industry standard AACE 29R-03 .

3.8.4 Fragmentary Network (Fragnet)

Prepare a proposed fragnet for time impact analysis consisting of a sequence of new activities that are proposed to be added to the project schedule to demonstrate the influence of the delay or impact to the project's contractual dates. Clearly show how the proposed fragnet is to be tied into the project schedule including all predecessors and successors to the fragnet activities. The proposed fragnet must be approved by the Contracting Officer prior to incorporation into the project schedule.

SECTION 01 32 01.00 10 Page 10

3.8.5 Time Extension

The Contracting Officer must approve the Justification of Delay including the time impact analysis before a time extension will be granted. No time extension will be granted unless the delay consumes all available Project Float and extends the projected finish date ("End Project" milestone) beyond the Contract Completion Date. The time extension will be in calendar days.

Actual delays that are found to be caused by the Contractor's own actions, which result in a calculated schedule delay will not be a cause for an extension to the performance period, completion date, or any interim milestone date.

3.9 FAILURE TO ACHIEVE PROGRESS

Should the progress fall 5% or greater behind the approved CPM or fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer shall require provision of a written recovery plan for approval. The plan must detail how progress will be made-up to include which activities will be accelerated by adding additional crews, longer work hours, extra work days, etc.

3.9.1 Artificially Improving Progress

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited. Indicate assumptions made and the basis for any logic, constraint, duration and calendar changes used in the creation of the recovery plan. Any additional resources, manpower, or daily and weekly work hour changes proposed in the recovery plan must be evident at the work site and documented in the daily report along with the Schedule Narrative Report.

3.9.2 Failure to Perform

Failure to perform work and maintain progress in accordance with the supplemental recovery plan may result in an interim and final unsatisfactory performance rating and may result in corrective action directed by the Contracting Officer pursuant to FAR 52.236-15 Schedules for Construction Contracts, FAR 52.249-10 Default (Fixed-Price Construction), and other contract provisions.

3.9.3 Recovery Schedule

Should the Contracting Officer find it necessary, submit a recovery schedule pursuant to FAR 52.236-15 Schedules for Construction Contracts.

3.10 OWNERSHIP OF FLOAT

Float available in the schedule, at any time, may not be considered for the exclusive use of either the Government or the Contractor including activity and/or project float. Activity float is the number of work days that an activity can be delayed without causing a delay to the "End Project" finish milestone. Project float (if applicable) is the number of work days between the projected early finish and the contract completion date milestone.

SECTION 01 32 01.00 10 Page 11

3.11 TRANSFER OF SCHEDULE DATA INTO RMS/QCS

Import the schedule data into the Quality Control System (QCS) and export the QCS data to the Government. This data is considered to be additional supporting data in a form and detail required by the Contracting Officer pursuant to FAR 52.232-5 Payments under Fixed-Price Construction Contracts. The receipt of a proper payment request pursuant to FAR 52.232-27 Prompt Payment for Construction Contracts is contingent upon the Government receiving both acceptable and approvable hard copies and matching electronic export from QCS of the application for progress payment.

3.12 PRIMAVERA P6 MANDATORY REQUIREMENTS

If Primavera P6 is being used, request a backup file template (.xer) from the Government, if one is available, prior to building the schedule. The following settings are mandatory and required in all schedule submissions to the Government:

a. Activity Codes must be Project Level, not Global or EPS level.

b. Calendars must be Project Level, not Global or Resource level.

c. Activity Duration Types must be set to "Fixed Duration & Units" .

d. Percent Complete Types must be set to "Physical".

e. Time Period Admin Preferences must remain the default "8.0 hr/day, 40 hr/week, 172 hr/month, 2000 hr/year". Set Calendar Work Hours/Day to

8.0 Hour days.

f. Set Schedule Option for defining Critical Activities to "Longest Path".

g. Set Schedule Option for defining progressed activities to "Retained Logic".

h. Set up cost loading using a single lump sum labor resource. The Price/Unit must be $1/hr, Default Units/Time must be "8h/d", and settings "Auto Compute Actuals" and "Calculate costs from units" selected.

i. Activity ID's must not exceed 10 characters.

j. Activity Names must have the most defining and detailed description within the first 30 characters.

SECTION 01 32 01.00 10 Page 12

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/18, CHG 4: 02/21

PART 1 GENERAL

1.1 SUMMARY

1.1.1 Submittal Information

The Contracting Officer may request submittals in addition to those specified when deemed necessary to adequately describe the work covered in the respective sections. Each submittal is to be complete and in sufficient detail to allow ready determination of compliance with contract requirements.

Units of weights and measures used on all submittals are to be the same as those used in the contract drawings.

1.1.2 Project Type

The Contractor's Quality Control (CQC) System Manager are to check and approve all items before submittal and stamp, sign, and date indicating action taken. Proposed deviations from the contract requirements are to be clearly identified. Include within submittals items such as:

Contractor's, manufacturer's, or fabricator's drawings; descriptive literature including (but not limited to) catalog cuts, diagrams, operating charts or curves; test reports; test cylinders; samples; O&M manuals (including parts list); certifications; warranties; and other such required submittals.

1.1.3 Submission of Submittals

Schedule and provide submittals requiring Government approval before acquiring the material or equipment covered thereby. Pick up and dispose of samples not incorporated into the work in accordance with manufacturer's Safety Data Sheets (SDS) and in compliance with existing laws and regulations.

1.2 DEFINITIONS

1.2.1 Submittal Descriptions (SD)

Submittal requirements are specified in the technical sections. Examples and descriptions of submittals identified by the Submittal Description (SD) numbers and titles follow:

SD-01 Preconstruction Submittals

Submittals that are required prior to or at the start of construction (work) or the next major phase of the construction on a multiphase contract.

For Government approved division 01 preconstruction submittals that are required prior to or commencing with the start of work shall be submitted within 30 calendar days of contract award .

SECTION 01 33 00 Page 1

Preconstruction Submittals include schedules and a tabular list of locations, features, and other pertinent information regarding products, materials, equipment, or components to be used in the work.

Certificates Of Insurance

Surety Bonds

List Of Proposed Subcontractors

List Of Proposed Products

Baseline Network Analysis Schedule (NAS)

Submittal Register

Schedule Of Prices Or Earned Value Report

Accident Prevention Plan

Work Plan

Quality Control (QC) plan

Environmental Protection Plan

SD-02

SD-02 Shop Drawings

Drawings, diagrams and schedules specifically prepared to illustrate some portion of the work.

Diagrams and instructions from a manufacturer or fabricator for use in producing the product and as aids to the Contractor for integrating the product or system into the project.

Drawings prepared by or for the Contractor to show how multiple systems and interdisciplinary work will be coordinated.

SD-03 Product Data

Catalog cuts, illustrations, schedules, diagrams, performance charts, instructions and brochures illustrating size, physical appearance and other characteristics of materials, systems or equipment for some portion of the work.

Samples of warranty language.

SD-06 Test Reports

Report signed by authorized official of testing laboratory that a material, product or system identical to the material, product or system to be provided has been tested in accord with specified requirements. Unless specified in another section, testing must have been within three years of date of contract award for the project.

Report that includes findings of a test required to be performed on an actual portion of the work or prototype prepared for the project before shipment to job site.

SECTION 01 33 00 Page 2

Report that includes finding of a test made at the job site or on sample taken from the job site, on portion of work during or after installation.

Investigation reports

Daily logs and checklists

Final acceptance test and operational test procedure

SD-07 Certificates

Statements printed on the manufacturer's letterhead and signed by responsible officials of manufacturer of product, system or material attesting that the product, system, or material meets specification requirements. Must be dated after award of project contract and clearly name the project.

Document required of Contractor, or of a manufacturer, supplier, installer or Subcontractor through Contractor. The document purpose is to further promote the orderly progression of a portion of the work by documenting procedures, acceptability of methods, or personnel qualifications.

Confined space entry permits

Text of posted operating instructions

SD-08 Manufacturer's Instructions

Preprinted material describing installation of a product, system or material, including special notices and (SDS)concerning impedances, hazards and safety precautions.

SD-09 Manufacturer's Field Reports

Documentation of the testing and verification actions taken by manufacturer's representative at the job site, in the vicinity of the job site, or on a sample taken from the job site, on a portion of the work, during or after installation, to confirm compliance with manufacturer's standards or instructions. The documentation must be signed by an authorized official of a testing laboratory or agency and state the test results; and indicate whether the material, product, or system has passed or failed the test.

Factory test reports.

SD-10 Operation and Maintenance Data

Data provided by the manufacturer, or the system provider, including manufacturer's help and product line documentation, necessary to maintain and install equipment, for operating and maintenance use by facility personnel.

Data required by operating and maintenance personnel for the safe and efficient operation, maintenance and repair of the item.

Data incorporated in an operations and maintenance manual or control

SECTION 01 33 00 Page 3 system.

SD-11 Closeout Submittals

Documentation to record compliance with technical or administrative requirements or to establish an administrative mechanism.

Submittals required for Guiding Principle Validation (GPV) or Third Party Certification (TPC).

Special requirements necessary to properly close out a construction contract. For example, Record Drawings and as-built drawings. Also, submittal requirements necessary to properly close out a major phase of construction on a multi-phase contract.

1.2.2 Approving Authority

Office or designated person authorized to approve the submittal.

1.2.3 Work

As used in this section, on-site and off-site construction required by contract documents, including labor necessary to produce submittals, construction, materials, products, equipment, and systems incorporated or to be incorporated in such construction. In exception, excludes work to produce SD-01 submittals.

1.3 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or “S” classification are for information only. Submit the following in accordance with Section

01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Submittal Register ; G

1.4 SUBMITTAL CLASSIFICATION

1.4.1 Government Approved (G)

Government approval is required for any variations from the Solicitation or the Accepted Proposal and for other items as designated by the Government.

Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, submittals are considered to be "shop drawings."

1.4.2 Design-Build Submittal Classifications

1.4.2.1 Designer of Record Approved/Government Conformance Review (DA/CR)

1.4.2.1.1 Variations from the Accepted Design

Government's approval is required for any proposed variation from the accepted design that still complies with the contract before the Contractor is authorized to proceed with material acquisition or installation. The Government reserves the right to review the submittal

SECTION 01 33 00 Page 4 before providing an opinion. The Government reserves the right to reject any design, variation that may affect furniture, furnishings, equipment selections, or operational decisions that were made, based on the reviewed and concurred design.

1.4.2.1.2 Substitutions

Unless prohibited or otherwise provided for elsewhere in the contract, where the Accepted Proposal named products, systems, materials or equipment by manufacturer, brand name, model number, or other specific identification, and the Contractor desires to substitute a manufacturer or model after award, submit a requested substitution for Government concurrence. Include substantiation, through identifying information that the substitute meets the contract requirements and that it is equal in function, performance, quality, and salient features to that in the accepted contract proposal. If the contract otherwise prohibits substitutions of equal named products, systems, materials or equipment by manufacturer, brand name, model number or other specific identification, the request is considered a "variation" to the contract. Variations are discussed below in paragraphs: "GOVERNMENT APPROVED" and VARIATIONS.

1.4.2.2 Government Approved (DA/GA)

In addition to the above-stated requirements for proposed variations to the accepted design, Government Approval and, where applicable, a contract modification are required before the Contractor is authorized to proceed with material acquisition or installation for any proposed variation to the contract that constitutes a change to the contract terms. The Government reserves the right to accept or reject any such proposed variation.

1.4.3 For Information Only

Submittals not requiring Government approval will be for information only. Within the terms of the Contract Clause SPECIFICATIONS AND DRAWINGS FOR CONSTRUCTION, they are not considered to be "shop drawings."

1.4.4 Sustainability Reporting Submittals (S)

Submittals for Guiding Principle Validation (GPV) or Third Party Certification (TPC) are indicated with an "S" designation. These submittals are for information only and for use as specified in Section

01 33 29 SUSTAINABILITY REPORTING.

Schedule submittals for these items throughout the course of construction as provided; do not wait until closeout.

1.5 PREPARATION

1.5.1 Transmittal Form

Use the AF Form 3000 transmittal form for submitting both Government-approved and information-only submittals. Submit in accordance with the instructions on the reverse side of the form. Properly complete this form by filling out all the heading blank spaces and identifying each item submitted. Exercise special care to ensure proper listing of the specification paragraph and sheet number of the contract drawings pertinent to the data submitted for each item.

SECTION 01 33 00 Page 5

1.5.2 Submittal Format

1.5.2.1 Format of SD-01 Preconstruction Submittals

When the submittal includes a document that is to be used in the project, or is to become part of the project record, other than as a submittal, do not apply the Contractor's approval stamp to the document itself, but to a separate sheet accompanying the document.

Provide data in the unit of measure used in the contract documents.

1.5.2.2 Format for SD-02 Shop Drawings

Provide shop drawings not less than 8 1/2 by 11 inches nor more than 30 by 42 inches , except for full-size patterns or templates. Prepare drawings to accurate size, with scale indicated, unless another form is required.

Ensure drawings are suitable for reproduction and of a quality to produce clear, distinct lines and letters, with dark lines on a white background.

a. Include the nameplate data, size, and capacity on drawings. Also include applicable federal, military, industry, and technical society publication references.

b. Dimension drawings, except diagrams and schematic drawings. Prepare drawings demonstrating interface with other trades to scale. Use the same unit of measure for shop drawings as indicated on the contract drawings. Identify materials and products for work shown.

Present shop drawings sized 8 1/2 by 11 inches as part of the bound volume for submittals. Present larger drawings in sets. Submit an electronic copy of drawings in PDF format.

1.5.2.2.1 Drawing Identification

Include on each drawing the drawing title, number, date, and revision numbers and dates, in addition to information required in paragraph

IDENTIFYING SUBMITTALS.

Number drawings in a logical sequence. Each drawing is to bear the number of the submittal in a uniform location next to the title block. Place the Government contract number in the margin, immediately below the title block, for each drawing.

1.5.2.3 Format of SD-03 Product Data

Present product data submittals for each section as a complete, bound volume . Include a table of contents, listing the page and catalog item numbers for product data.

Indicate, by prominent notation, each product that is being submitted;

indicate the specification section number and paragraph number to which it pertains.

1.5.2.3.1 Product Information

Supplement product data with material prepared for the project to satisfy the submittal requirements where product data does not exist. Identify this material as developed specifically for the project, with information and format as required for submission of SD-07 Certificates.

SECTION 01 33 00 Page 6

Provide product data in units used in the Contract documents. Where product data are included in preprinted catalogs with another unit, submit the dimensions in contract document units, on a separate sheet.

1.5.2.3.2 Standards

Where equipment or materials are specified to conform to industry or technical-society reference standards of such organizations as the American National Standards Institute (ANSI), ASTM International (ASTM), National Electrical Manufacturer's Association (NEMA), Underwriters Laboratories (UL), or Association of Edison Illuminating Companies (AEIC), submit proof of such compliance. The label or listing by the specified organization will be acceptable evidence of compliance. In lieu of the label or listing, submit a certificate from an independent testing organization, competent to perform testing, and approved by the Contracting Officer. State on the certificate that the item has been tested in accordance with the specified organization's test methods and that the item complies with the specified organization's reference standard.

1.5.2.3.3 Data Submission

Collect required data submittals for each specific material, product, unit of work, or system into a single submittal that is marked for choices, options, and portions applicable to the submittal. Mark each copy of the product data identically. Partial submittals will not be accepted .

Submit the manufacturer's instructions before installation.

1.5.2.4 Format of SD-04 Samples

1.5.2.4.1 Sample Characteristics

Furnish samples in the following sizes, unless otherwise specified or unless the manufacturer has prepackaged samples of approximately the same size as specified:

a. Sample of Equipment or Device: Full size.

b. Sample of Materials Less Than 2 by 3 inches : Built up to 8 1/2 by 11 inches .

c. Sample of Materials Exceeding…