Div 01 Specs Revised Feb 2022.pdf

DE05323-1P JOC Specifications JOCFY22 Revised February 2022.

PROJECT TABLE OF CONTENTS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 45 00.00 10 QUALITY CONTROL

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 1

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 32 01.00 10

PROJECT SCHEDULE

02/15

PART 1 GENERAL

1.1 REFERENCES

1.2 SUBMITTALS

1.3 PROJECT SCHEDULER QUALIFICATIONS

PART 2 PRODUCTS

2.1 SOFTWARE

2.1.1 Government Default Software

2.1.2 Contractor Software

2.1.2.1 Microsoft Office Project

PART 3 EXECUTION

3.1 GENERAL REQUIREMENTS

3.2 BASIS FOR PAYMENT AND COST LOADING

3.2.1 Activity Cost Loading

3.2.2 Withholdings / Payment Rejection

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

3.3.2 Activity Durations

3.3.3 Procurement Activities

3.3.4 Mandatory Tasks

3.3.5 Government Activities

3.3.6 Standard Activity Coding Dictionary

3.3.6.1 Workers Per Day (WRKP)

3.3.6.2 Responsible Party Coding (RESP)

3.3.6.3 Bid Item Coding (BIDI)

3.3.6.4 Phase of Work Coding (PHAS)

3.3.6.5 Category of Work Coding (CATW)

3.3.6.6 Definable Feature of Work Coding (FOW)

3.3.7 Contract Milestones and Constraints

3.3.7.1 Project Start Date Milestone and Constraint

3.3.7.2 End Project Finish Milestone and Constraint

3.3.8 Calendars

3.3.9 Open Ended Logic

3.3.10 Default Progress Data Disallowed

3.3.11 Out-of-Sequence Progress

3.3.12 Added and Deleted Activities

3.3.13 Original Durations

3.3.14 Leads, Lags, and Start to Finish Relationships

3.3.15 Retained Logic

3.3.16 Percent Complete

3.3.17 Remaining Duration

3.3.18 Red Zone Meeting

SECTION 01 32 01.00 10 Page 1

3.3.19 Pre-Warranty Conference

3.3.20 Cost Loading of Closeout Activities

3.3.20.1 As-Built Drawings

3.3.20.2 O & M Manuals

3.3.20.3 Closeout Documents

3.3.21 Early Completion Schedule and the Right to Finish Early

3.4 PROJECT SCHEDULE SUBMISSIONS

3.4.1 Initial Project Schedule Submission

3.4.2 Periodic Schedule Updates

3.5 SUBMISSION REQUIREMENTS

3.5.1 Narrative Report

3.5.2 Schedule Reports

3.5.2.1 Activity Report

3.5.2.2 Logic Report

3.5.3 Network Diagram

3.5.3.1 Continuous Flow

3.5.3.2 Project Milestone Dates

3.5.3.3 Critical Path

3.6 BI-WEEKLY PROGRESS MEETINGS

3.7 REQUESTS FOR TIME EXTENSIONS

3.7.1 Justification of Delay

3.7.2 Time Impact Analysis (Prospective Analysis)

3.7.3 Time Extension

3.7.4 Impact to Early Completion Schedule

3.8 FAILURE TO ACHIEVE PROGRESS

3.8.1 Artificially Improving Progress

3.8.2 Failure to Perform

3.8.3 Recovery Schedule

3.9 OWNERSHIP OF FLOAT

3.10 Microsoft Project MANDATORY REQUIREMENTS

-- End of Section Table of Contents --

SECTION 01 32 01.00 10 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.

AACE INTERNATIONAL (AACE)

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" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Project Scheduler Qualifications ; G, DPW - Engineering Division

Initial Project Schedule ; G, DPW - Engineering Division

Periodic Schedule Update ; G, DPW - Engineering Division

1.3 PROJECT SCHEDULER QUALIFICATIONS

Designate a project scheduler to be responsible for the preparation of the schedule and all required updating and production of reports. The project scheduler must have a minimum of 2-years experience scheduling construction projects similar in size and nature to this contract with scheduling software that meets the requirements of this specification.

Representative must have a comprehensive knowledge of CPM scheduling principles and application.

PART 2 PRODUCTS

2.1 SOFTWARE

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

SECTION 01 32 01.00 10 Page 3

2.1.1 Government Default Software

The Government intends to use Microsoft Office 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 file must be created and supported by the software manufacturer.

2.1.2.1 Microsoft Office Project

If Microsoft Office Project is selected for use, provide the export file in a version of Microsoft Office Project importable by the Government system.

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 on site 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 initial or periodic schedule updates and subsequent rejection of payment requests until compliance is met.

In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount s from each payment period until such revisions to the project schedule have been made.

SECTION 01 32 01.00 10 Page 4

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 DPW 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 45 calendar days.

3.3.4 Mandatory Tasks

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

a. Notice to Proceed (NTP)

b. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each).

c. Submission of mechanical/electrical/information systems layout drawings incidental design items as per individual task order, shop drawings for steel .

d. Long procurement activities

e. Red Zone Meeting.

f. Pre-Warranty Conference

g. Submission and approval of O & M manuals.

h. Submission and approval of as-built drawings.

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

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

k. Submission of TAB specialist design review report.

l . Submission and approval of fire protection specialist.

SECTION 01 32 01.00 10 Page 5

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

n. Air and water balancing.

o. Building commissioning - Functional Performance Testing.

p. Controls testing plan submission.

q. Controls testing.

r . Performance Verification testing.

s. Other systems testing, if required.

t . Contractor's pre-final inspection.

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

v. Government's pre-final inspection.

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

x. Final inspection.

y. Submission of closeout docs.

z. Notice of Acceptance (NOA)

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

SECTION 01 32 01.00 10 Page 6

Field Activity Code Length Description

2 RESP 4 Responsible party

3 AREA 4 Area of work

4 MODF 6 Modification Number

5 BIDI 6 Bid Item (CLIN)

6 PHAS 2 Phase of work

7 CATW 1 Category of work

8 FOW 20 Feature of work*

*Some systems require that FEATURE OF WORK values be placed in several activity code fields. The notation shown is for Primavera P6. Refer to the specific software guidelines with respect to the FEATURE OF WORK field requirements.

3.3.6.1 Workers Per Day (WRKP)

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.

3.3.6.2 Responsible Party Coding (RESP)

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

a. Activities coded with a Government Responsibility code include, but are not limited to: Government approvals, 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: PCON (for the prime contractor) ;

ELEC (for the electrical subcontractor); MECH (for the mechanical subcontractor); and GOVT (for DPW).

3.3.6.3 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.4 Phase of Work Coding (PHAS)

Assign Phase of Work Code to all activities. Examples of phase of work are procurement phase and construction phase. Each activity can have only one Phase of Work code.

SECTION 01 32 01.00 10 Page 7

a. 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.5 Category of Work Coding (CATW)

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.

3.3.6.6 Definable Feature of Work Coding (FOW)

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

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

3.3.7 Contract Milestones and Constraints

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

Mandatory constraints that ignore or effect network logic are prohibited.

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

3.3.7.1 Project Start Date Milestone and Constraint

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

3.3.7.2 End Project Finish Milestone and Constraint

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

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

3.3.8 Calendars

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the

SECTION 01 32 01.00 10 Page 8 physical work plan with non-work periods identified including weekends and holidays.

If an activity is weather sensitive it shall 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 Requirements.

Assign non-work days over a seven-day week as weather records are compiled on seven-day weeks, which may cause some of the weather related non-work days to fall on weekends .

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 Contracting Officer's approval.

3.3.10 Default Progress Data Disallowed

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

3.3.11 Out-of-Sequence Progress

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

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

3.3.12 Added and Deleted Activities

Do not delete activities from the project schedule or add new activities to the schedule without approval from the DPW. Activity ID and description changes are considered new activities and cannot be changed without DPW 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 DPW.

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

SECTION 01 32 01.00 10 Page 9 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 Red Zone Meeting

Cost load the Red Zone Meeting activity not less than 2.5% of the Contract Value.

3.3.19 Pre-Warranty Conference

Cost load the Pre-Warranty Conference activity not less than 2.5% of the Contract Value.

3.3.20 Cost Loading of Closeout Activities

Cost load the "Correction of punch list from Government pre-final inspection" activity(ies) not less than 2.5 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.20.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 2.5 percent of the present contract value. Activity will be declared 100 percent complete upon the Government's approval.

3.3.20.2 O & M Manuals

Cost load the "Submission and approval of O & M manuals" activity not less

SECTION 01 32 01.00 10 Page 10 than 2.5 percent of the Contract Value . Activity will be declared 100 percent complete upon the Government's approval of all O & M manuals.

3.3.20.3 Closeout Documents

Cost load the "Closeout Documents" activity not less than 2.5 percent of the Contract Value.

3.3.21 Early Completion Schedule and the Right to Finish Early

An Early Completion Schedule is an Initial Project Schedule (IPS) that indicates all scope of the required contract work will be completed before the contractually required completion date.

a. No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and manhours) and the Government agreeing that the schedule is reasonable and achievable.

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

3.4 PROJECT SCHEDULE SUBMISSIONS

Provide the submissions as described below. The schedule data , reports, and network diagrams required for each submission are contained in paragraph SUBMISSION REQUIREMENTS , refer to parragrph 3.5 . 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 Initial Project Schedule Submission

Submit the Initial Project Schedule as a SD-01 prior to the PRECON meeting .

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.2 Periodic Schedule Updates

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

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 Initial Schedule, and for every Periodic Schedule Update throughout the life of the project:

SECTION 01 32 01.00 10 Page 11

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 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 DPW. 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.3 Network Diagram

The Network Diagram is required for the 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:

SECTION 01 32 01.00 10 Page 12

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 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.6 BI- WEEKLY PROGRESS MEETINGS

Conduct bi- weekly Progress Review meetings 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.7 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.

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

3.7.2 Time Impact Analysis (Prospective Analysis)

Prepare a time impact analysis for approval by DPW 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.

SECTION 01 32 01.00 10 Page 13

3.7.3 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.7.4 Impact to Early Completion Schedule

No extended overhead will be paid for delay prior to the original Contract Completion Date for an Early Completion IPS unless the Contractor actually performed work in accordance with that Early Completion Schedule. The Contractor must show that an early completion was achievable had it not been for the impact.

3.8 FAILURE TO ACHIEVE PROGRESS

Should the progress fall behind the approved project schedule for reasons other than those that are excusable within the terms of the contract, the Contracting Officer may 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.8.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.8.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.8.3 Recovery Schedule

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

SECTION 01 32 01.00 10 Page 14

3.9 OWNERSHIP OF FLOAT

Except for the provision given in the paragraph IMPACT TO EARLY COMPLETION SCHEDULE, 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.

3.10 Microsoft Project MANDATORY REQUIREMENTS

If Microsoft Project is being used, 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.

-- End of Section --

SECTION 01 32 01.00 10 Page 15

SECTION TABLE OF CONTENTS

DIVISION 01 - GENERAL REQUIREMENTS

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/ 18, CHG 4: 02/ 21

PART 1 GENERAL

1.1 DEFINITIONS

1.1.1 Submittal Descriptions (SD)

1.1.2 Approving Authority

1.1.3 Work

1.2 SUBMITTALS

1.3 SUBMITTAL CLASSIFICATION

1.3.1 Government Approved (G)

1.3.2 For Information Only

1.4 PREPARATION

1.4.1 Transmittal Form

1.4.2 Submittal Format

1.4.2.1 Format of SD-01 Preconstruction Submittals

1.4.2.2 Format for SD-02 Shop Drawings

1.4.2.2.1 Drawing Identification

1.4.2.3 Format of SD-03 Product Data

1.4.2.3.1 Product Information

1.4.2.3.2 Standards

1.4.2.3.3 Data Submission

1.4.2.4 Format of SD-04 Samples

1.4.2.4.1 Sample Characteristics

1.4.2.4.2 Sample Incorporation

1.4.2.4.3 Comparison Sample

1.4.2.5 Format of SD-05 Design Data

1.4.2.6 Format of SD-06 Test Reports

1.4.2.7 Format of SD-07 Certificates

1.4.2.8 Format of SD-08 Manufacturer's Instructions

1.4.2.8.1 Standards

1.4.2.9 Format of SD-09 Manufacturer's Field Reports

1.4.2.10 Format of SD-10 Operation and Maintenance Data (O&M)

1.4.2.11 Format of SD-11 Closeout Submittals

1.4.3 Source Drawings for Shop Drawings

1.4.3.1 Source Drawings

1.4.3.2 Terms and Conditions

1.4.4 Electronic File Format

1.5 QUANTITY OF SUBMITTALS

1.5.1 Number of SD-01 Preconstruction Submittal Copies

1.5.2 Number of SD-02 Shop Drawing Copies

1.5.3 Number of SD-03 Product Data Copies

1.5.4 Number of SD-04 Samples

1.5.5 Number of SD-05 Design Data Copies

1.5.6 Number of SD-06 Test Report Copies

1.5.7 Number of SD-07 Certificate Copies

1.5.8 Number of SD-08 Manufacturer's Instructions Copies

1.5.9 Number of SD-09 Manufacturer's Field Report Copies

SECTION 01 33 00 Page 1

1.5.10 Number of SD-10 Operation and Maintenance Data Copies

1.5.11 Number of SD-11 Closeout Submittals Copies

1.6 INFORMATION ONLY SUBMITTALS

1.7 INDIVIDUAL PROJECT SUBMITTAL REGISTER

1.7.1 Submittal Management

1.7.2 Contractor Use of Submittal Register

1.7.3 Approving Authority Use of Submittal Register

1.7.4 Action Codes

1.7.4.1 Government Review Action Codes

1.7.4.2 Government Review Action Codes

1.7.5 Delivery of Copies

1.8 VARIATIONS

1.8.1 Considering Variations

1.8.2 Proposing Variations

1.8.3 Warranting that Variations are Compatible

1.8.4 Review Schedule Extension

1.9 SCHEDULING

1.10 GOVERNMENT APPROVING AUTHORITY

1.10.1 Review Notations

1.11 DISAPPROVED SUBMITTALS

1.12 APPROVED SUBMITTALS

1.13 APPROVED SAMPLES

PART 2 PRODUCTS

PART 3 EXECUTION

SECTION 01 33 00 Page 2

SECTION 01 33 00

SUBMITTAL PROCEDURES

08/ 18, CHG 4: 02/ 21

PART 1 GENERAL

1.1 DEFINITIONS

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

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

Work Plan

Quality Control (QC) plan

Environmental Protection Plan

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.

SECTION 01 33 00 Page 3

Samples of warranty language when the contract requires extended product warranties.

SD-04 Samples

Fabricated or unfabricated physical examples of materials, equipment or workmanship that illustrate functional and aesthetic characteristics of a material or product and establish standards by which the work can be judged.

Color samples from the manufacturer's standard line (or custom color samples if specified) to be used in selecting or approving colors for the project.

Field samples and mock-ups constructed on the project site establish standards ensuring work can be judged. Includes assemblies or portions of assemblies that are to be incorporated into the project and those that will be removed at conclusion of the work.

SD-05 Design Data

Design calculations, mix designs, analyses or other data pertaining to a part of work.

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.

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.

SECTION 01 33 00 Page 4

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

Office or designated person authorized to approve the submittal.

SECTION 01 33 00 Page 5

1.1.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.2 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or “S” classification are for Contractor Quality Control approval and are not required to be submitted .

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Quality Control Plan, G - DPW Engineering Division

Accident Prevention Plan, G - DPW Engineering Division

Environmental Protection Plan , G - DPW Environmental Division

Performance Bond ; G - DPW Engineering Division

1.3 SUBMITTAL CLASSIFICATION

1.3.1 Government Approved (G)

Government approval is required for critical materials, variations, equipment whose compatibility with the entire system must be checked, and 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.3.2 For Information Only

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

1.4 PREPARATION

1.4.1 Transmittal Form

1.4.2 Submittal Format

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

SECTION 01 33 00 Page 6

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

1.4.2.2 Format for SD-02 Shop Drawings

Provide electronic copies (pdf) of shop drawings. 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.

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

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

Where equipment or materials are specified to conform to industry or technical-society reference standards of such organizations as the

SECTION 01 33 00 Page 7

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.4.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 for expedition of the construction effort.

1.4.2.4 Format of SD-04 Samples

1.4.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 8 1/2 by 11 inches : Cut down to 8 1/2 by 11 inches and adequate to indicate color, texture, and material variations.

d. Sample of Linear Devices or Materials: 10 inch length or length to be supplied, if less than 10 inches . Examples of linear devices or materials are conduit and handrails.

e. Color Selection Samples: 2 by 4 inches . Where samples are specified for selection of color, finish, pattern, or texture, submit the full set of available choices for the material or product specified. Sizes and quantities of samples are to represent their respective standard unit.

1.4.2.4.2 Sample Incorporation

Reusable Samples: Incorporate returned samples into work only if so specified or indicated. Incorporated samples are to be in undamaged condition at the time of use.

Recording of Sample Installation: Note and preserve the notation of any area constituting a sample installation, but remove the notation at the

SECTION 01 33 00 Page 8 final clean-up of the project.

1.4.2.4.3 Comparison Sample

Samples Showing Range of Variation: Where variations in color, finish, pattern, or texture are unavoidable due to nature of the materials, submit sets of samples of not less than three units showing extremes and middle of range. Mark each unit to describe its relation to the range of the variation.

When color, texture, or pattern is specified by naming a particular manufacturer and style, include one sample of that manufacturer and style, for comparison.

1.4.2.5 Format of SD-05 Design Data

Provide design data and certificates in electronic format(pdf) . Provide a bound volume for submittals containing numerous pages.

1.4.2.6 Format of SD-06 Test Reports

Provide reports in electronic format (pdf) in a complete bound volume.

By prominent notation, indicate each report in the submittal. Indicate the specification number and paragraph number to which each report pertains.

1.4.2.7 Format of SD-07 Certificates

Provide design data in electronic format(pdf) and certificates in electronic format (pdf). Provide a bound volume for submittals containing numerous pages.

1.4.2.8 Format of SD-08 Manufacturer's Instructions

Present manufacturer's instructions submittals for each section in electronic format (pdf) . Include the manufacturer's name, trade name, place of manufacture, and catalog model or number on product data. Also include applicable federal, military, industry, and technical-society publication references. If supplemental information is needed to clarify the manufacturer's data, submit it as specified for SD-07 Certificates.

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

SECTION 01 33 00 Page 9

1.4.2.9 Format of SD-09 Manufacturer's Field Reports

Provide reports in electronic format (pdf) .

By prominent notation, indicate each report in the submittal. Indicate the specification number and paragraph number to which each report pertains.

1.4.2.10 Format of SD-10 Operation and Maintenance Data (O&M)

Comply with the requirements specified in Section 01 78 23 OPERATION AND MAINTENANCE DATA for O&M Data format.

1.4.2.11 Format of SD-11 Closeout 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.4.3 Source Drawings for Shop Drawings

1.4.3.1 Source Drawings

The entire set of source drawing files (DWG) will not be provided to the Contractor. Request the specific Drawing Number for the preparation of shop drawings. Only those drawings requested to prepare shop drawings will be provided. These drawings are provided only after award.

1.4.3.2 Terms and Conditions

Data contained on these electronic files must not be used for any purpose other than as a convenience in the preparation of construction data for the referenced project. Any other use or reuse is at the sole risk of the Contractor and without liability or legal exposure to the Government.