Esc

↑↓ move↵ openIndex · Pagefind
Project management

Prospective Time Impact Analysis

Definition

A forward-looking time impact analysis, done near the time of a delay event, that inserts an agreed fragnet into the current schedule update to estimate its effect on completion.

Topic: Changes & claims · Scheduling

Updated

A prospective time impact analysis models a delay event while it’s happening, or about to, to estimate its effect on completion before the work is done. The event is drawn as a small network of activities, a fragnet, and inserted into the schedule update in effect when the delay starts. The forecast completion with and without the fragnet gives the modelled impact. AACE RP 52R-06 sets out the steps. See also the general time impact analysis.

Worked example

Illustrative: an owner directs a change to the curtain wall anchors on 12 May. The contractor drafts a fragnet: redesign 10 working days, then fabrication of revised anchors 15 days, tied ahead of Install curtain wall level 3. The update in effect is the April update, data date 30 April. Inserted there, the fragnet moves the forecast completion 8 working days. The owner’s reviewer questions the redesign duration, the parties agree 7 days, and the accepted fragnet then shows a 5-day impact.

Why it matters

Agreeing the fragnet and its impact while the facts are fresh avoids a long dispute later. The value depends on using the right update, a reasonable fragnet and a clear record of review.

Common mistakes

  • Inserting the fragnet into the latest update rather than the one in effect when the delay started.
  • Leaving out other changes made to the update, so the impact mixes the event with schedule revisions.
  • Treating the modelled days as an automatic time extension.

How os.construction handles it

A fragnet is submitted with its events, basis and the contract’s time unit, reviewed by another Schedule admin, then accepted or rejected. Only an accepted fragnet is analysed, on the last approved update statused on or before the delay start. Inputs are fixed once submitted, every step is audited, and the report states that entitlement is a contract question. See Prospective time impact analysis.

FAQ

What makes a time impact analysis prospective?

It's done when the delay is happening or about to, on the schedule update in effect at that time, to forecast the effect and support a time extension request. A retrospective analysis looks back at what actually happened.

Which update should the fragnet go into?

Under AACE RP 52R-06, the update in effect: the last accepted update whose data date is on or before the start of the delay.

Is a prospective TIA one of the RP 29R-03 methods of implementation?

No. It's covered by its own recommended practice, RP 52R-06, so it carries no MIP number.

Keep exploring

Related across os.construction

Open file