SOW - Doc A5 - Time Impact Analysis.pdf

Time Impact Analysis

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. The schedule submission must consist of three native files:

(1) Fragnet used to define the scope of the changed condition

(2) Most recent accepted schedule update as of the time of the proposal or claim submission that has been updated to show all activity progress as of the time of the impact start date.

(3) The impacted schedule that has the fragnet inserted in the updated schedule and the schedule "run" so that the new completion date is determined.

b. For claimed as-built project delay, the inserted fragnet TIA method must be modified to account for as-built events known to occur after the data date of schedule update used.

c. 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) Use functional theory to analyze concurrent delays, where:

Separate delay issues delay project completion, do not necessarily occur at same time, rather occur within same monthly schedule update period at minimum, or within same as-built period under review. If a combination of functionally concurrent delay types occurs, it is considered Concurrent Delay, which is defined in the following combinations:

(a) Government-delay concurrent with Contractor-delay: Excusable time extension, classified non-compensable event.

(b) Government-delay concurrent with force majeure delay: Excusable time extension, classified non-compensable event.

(c) Contractor-delay concurrent with force majeure delay: Excusable time extension, classified non-compensable event.

(3) A pacing delay, reacting to another delay (parent delay) equally or more critical than paced activity, must be identified prior to pacing.

Contracting Officer will notify Contractor prior to pacing. Contractor must notify Contracting Officer prior to pacing. Notification must include identification of parent delay issue, estimated parent delay time period, paced activity(s) identity, and pacing reason(s). Pacing Concurrency is defined as follows:

(a) Government-delay concurrent with Contractor-pacing: Excusable time extension, classified compensable event.

(b) Contractor-delay concurrent with Government-pacing: Inexcusable time extension, classified non-compensable event.