(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.
Both the SCL and AACE recognise the inaccuracy that can result from performing TIA when there is a gap between the delay event and the programme status date. The recommendation is generally to update the programme to immediately before the delay event.
The contract often provides deadlines for the submission of EoT claims, expressed as x days from becoming aware of a critical delay.
If one becomes aware of a delay event which will commence in 30 days time, but the contract requires an EOT claim to be submitted within 20 days of becoming aware, how should one proceed?
Printer-friendly version
Send to friend
Assuming no unusual provisions in the contract, the time bar clock starts ticking when the effect that the event has on the completion time becomes determinate.
I guess the delay event already started, in this case the delayed activies should follow 20 days after the delay event start, TIA is about adding the delay event(s).
52R-06: Time Impact Analysis AACE 52R-06
4 Most Used Delay Analysis Methods (Their Pros and Cons)
This is one of the most recommended methods by delay analysis experts. Adopting this method, the baseline schedule should be updated with the actual progress to a point just before the delay event takes place. Therefore, it takes in account the effect of actual progress combined with timing of delay. TIA often undertaken in time slices (windows).
Good luck with the dark arts!
Email: PPadmin@planningplanet.com
Replies