09 Specs_amendment 4.pdf

AMENDMENT #4

RENOVATE CHILD DEVELOPMENT CENTER CDC B164

PROJECT NUMBER AFPID 1007645

5 APRIL 2024

AMENDMENT ITEMS LIST:

1. Replace Specifications section 01 32 01.00 10 project schedule with 01 32 16.00 20 small project construction progress schedule. Replace Specifications section 01 32 01.00 10 project schedule with 01 32 16.00 20 small project construction progress schedule in the table of contents.

SECTION 01 32 16.00 20

SMALL PROJECT CONSTRUCTION PROGRESS SCHEDULES

08/18, CHG 1: 08/20

PART 1 GENERAL

1.1 SUBMITTALS

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Baseline Construction Schedule;

SD-07 Certificates

Monthly Updates

1.2 PRE-CONSTRUCTION SCHEDULE REQUIREMENT

Within 30 calendar days after contract award and Prior to the start of work, prepare and submit to the Contracting Officer a Baseline Construction Schedule in the form of a Bar Chart Schedule in accordance with the terms in Contract Clause FAR 52.236-15 Schedules for Construction Contracts, except as modified in this contract. The approval of a Baseline Construction Schedule is a condition precedent to:

a. The Contractor starting demolition work or construction stage(s) of the contract.

b. Processing Contractor's invoice(s) for construction activities/items of work.

c. Review of any schedule updates.

Submittal of the Baseline Construction Schedule, and subsequent schedule updates, is understood to be the Contractor's certification that the submitted schedule meets the requirements of the Contract Documents, represents the Contractor's plan on how the work will be accomplished, and accurately reflects the work that has been accomplished and how it was sequenced (as-built logic).

1.3 SCHEDULE FORMAT

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.

1.3.1 Activity Identification

a. Identify Government, Construction Quality Management (CQM), Construction activities planned for the project and other activities that could impact project completion if delayed.

b. Identify administrative type activity/milestones including pre-construction submittal and permit requirements prior to demolition or construction stage.

c. Create separate activities for each Phase, Area, Floor Level, and Location the activity is occurring.

]1.3.2 Bar Chart Schedule

Use the critical path method (CPM) to schedule and control project activities. The Bar Chart must, as a minimum, show work activities, submittals, Government review periods, material/equipment delivery, utility outages, on-site construction, inspection, testing, and closeout activities. The Bar Chart must be time scaled and generated using an electronic spreadsheet program. Government and Contractor on-site work activities must be driven by calendars that reflect Saturdays, Sundays and all Federal Holidays as non-work days for 5-day work week calendars.

a. (1) Include the following Contract Milestones:

(a) Include as the first activity on the schedule a start milestone titled "Contract Award", which must have a Mandatory Start constraint equal to the Contract Award Date;

(b) Include Interim or Phased Completion Milestones required by the Contract or as approved by the Contracting Officer;

(c) Include Facility Turnover Planning Meeting Milestones;

(d) Include an unconstrained finish milestone on the schedule titled "Substantial Completion". Substantial Completion is defined as the point in time the Government would consider the project ready for beneficial occupancy wherein by mutual agreement of the Government and Contractor. Government use of the facility is allowed while construction access continues in order to complete remaining items (e.g. punch list and other close out submittals).

(e) Include an unconstrained finish milestone on the schedule titled "Projected Completion". Projected Completion is defined as the point in time the Government would consider the project complete. This milestone must have the Contract Completion Date (CCD) milestone as its only successor.

(f) Include as the last activity on the schedule a finish milestone titled "Contract Completion (CCD)" with constraint type "Must Finish No Later Than". Calculation of schedule updates must be such that if the finish of the "Projected Completion" milestone falls after the contract completion date, then negative float will be calculated on the longest path and if the finish of the "Projected Completion" milestone falls before the contract completion date, the float calculation must reflect positive float on the longest path. This milestone must be set to 5:00 pm.

(2) Provide lead time for major equipment.

b. Anticipated Weather Lost Work Days

Reference section 01 14 00 Work restrictions- Paragraph applicable to contracts with clause entitled TIME EXTENSIONS FOR UNUSUALLY SEVERE WEATHER. Reflect the number of anticipated adverse weather delays allocated to a weather sensitive activity in the activity's calendar.

1.3.3 Schedule Submittals and Procedures

Submit Schedules and updates in hard copy and on electronic media that is acceptable to the Contracting Officer. Submit an electronic back-up of the project schedule in an import format compatible with the Government's scheduling program.

1.4 SCHEDULE MONTHLY UPDATES

Update the Construction Schedule at monthly intervals or when the schedule has been revised. Keep the updated schedule current, reflecting actual activity progress and plan for completing the remaining work. Submit copies of purchase orders and confirmation of delivery dates as directed by the Contracting Officer.

a. Narrative Report: Identify and justify the following:

(1) Progress made in each area of the project;

(2) Longest Path: Include printed copy on 11 by 17 inch paper, landscape setting;

(3) Date/time constraint(s), other than those required by the contract;

(4) Listing of changes made between the previous schedule and current updated schedule including: added or removed activities, original and remaining durations for activities that have not started, logic (sequence, constraint, lag/lead), milestones, planned sequence of operations, longest path, calendars or calendar assignments, and cost loading.

(5) Any decrease in previously reported activity Earned Amount;

(6) Pending items and status thereof, including permits, changes orders, and time extensions;

(7) Status of Contract Completion Date and interim milestones;

(8) Current and anticipated delays (describe cause of delay and corrective actions(s) and mitigation measures to minimize);

(9) Description of current and future schedule problem areas.

For each entry in the narrative report, cite the respective Activity ID and Activity Name, the date and reason for the change, and description of the change.

1.5 CONTRACT MODIFICATION

Submit a Time Impact Analysis (TIA) with each cost and time proposal for a proposed change. TIA must illustrate the influence of each change or delay on the Contract Completion Date or milestones. No time extensions will be granted nor delay damages paid unless a delay occurs which consumes all available Project Float, and extends the Projected Finish beyond the Contract Completion Date.

a. Each TIA must be in both narrative and schedule form. The narrative must define the scope and conditions of the change; provide start and finish dates of impact, successor and predecessor activity to impact period, responsible party, describe how it originated, and how it impacts the schedule.

b. TIAs must include any mitigation, and must determine the apportionment of the overall delay assignable to each individual delay. Apportionment must provide identification of delay type and classification of delay by compensable and non-compensable events. The associated narrative must clearly describe analysis methodology used, and the findings in a chronological listing beginning with the earliest delay event.

(1) Identify and classify types of delays as follows:

(a) Force majeure delay (e.g. weather delay): Any delay event caused by something or someone other than the Government (including its agents) or the Contractor, or the risk of which has not been assigned solely to the Government or the Contractor. If the force majeure delay is on the critical path, in absence of other types of concurrent delays, the Contractor is granted an extension of contract time, classified as a non-compensable event.

(b) A Contractor-delay: Any delay event caused by the Contractor, or the risk of which has been assigned solely to the Contractor.

If the contractor-delay is on the critical path, in absence of other types of concurrent delays, Contractor is not granted extension of contract time, and classified as a non-compensable event. Where absent other types of delays, and having impact to project completion, provide a Corrective Action Plan, identifying plan to mitigate delay, to the Contracting Officer.

(c) A Government-delay: Any delay event caused by the Government, or the risk of which has been assigned solely to the Government.

If the Government-delay is on the longest path, in absence of other types of concurrent delays, the Contractor is granted an extension of contract time, and classified as a compensable event.

(2) If a combination of any of the delay types outlined above occurs, it is considered a Concurrent Delay, which will require an analysis of the facts to determine compensability and entitlement to any time extension under the applicable contract clauses.

1.6 CORRESPONDENCE AND TEST REPORTS:

Correspondence (e.g., letters, Requests for Information (RFIs), e-mails, meeting minute items, Production and QC Daily Reports, material delivery tickets, photographs) must reference Schedule Activities that are being addressed. Test reports (e.g., concrete, soil compaction, weld, pressure) must reference Schedule Activities that are being addressed.

1.7 ADDITIONAL SCHEDULING REQUIREMENTS

Any references to additional scheduling requirements, including systems to be inspected, tested and commissioned, that are located throughout the remainder of the Contract Documents, are subject to all requirements of this section.

PART 2 PRODUCTS

Not used.

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.

3.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 those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.

3.3 PROJECT SCHEDULE DETAILED REQUIREMENTS

3.3.1 Level of Detail Required

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

3.3.2 Activity Durations

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

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

3.3.3 Procurement Activities

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

3.3.4 Mandatory Tasks

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

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

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

c. Long procurement activities

d. Submission and approval of O & M manuals.

e. Submission and approval of as-built drawings.

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

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

h. Submission of TAB specialist design review report.

i. Submission and approval of fire protection specialist.

j. Submission and approval of Building Commissioning Plan, test data, and reports: Develop the schedule logic associated with testing and commissioning of mechanical systems to a level of detail consistent with the contract commissioning requirements. All tasks associated with all building testing and commissioning will be completed prior to submission of building commissioning report and subsequent contract completion.

k. Air and water balancing.

l. Building commissioning - Functional Performance Testing.

m. Controls testing plan submission.

n. Controls testing.

o. Performance Verification testing.

p. Other systems testing, if required.

q. Contractor's pre-final inspection.

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

s. Government's pre-final inspection.

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

u. Final inspection.

3.3.5 Government Activities

Show Government and other agency activities that could impact progress.

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

3.3.6 Closeout Activities

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

3.3.6.1 O & M Manuals

Schedule shall show 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 SUBMISSION REQUIREMENTS

Submit the following items for the Baseline Construction Schedule and every Monthly Schedule Update throughout the life of the project:

3.5 WEEKLY PROGRESS MEETINGS

Conduct a weekly meeting with the Government (or as otherwise mutually agreed to) 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.6 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.6.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 becomes part of the project schedule and all future schedule updates upon approval by the Contracting Officer.

3.6.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.6.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 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.7.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.7.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.7.3 Recovery Schedule

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

-- End of Section --