1 Baseline 6 Revisions - TIA

Hi Stephen

In a typical Time Impact Analysis (SCL Definition) it is necessary to update progress for the whole project just before the date of impact of the event.

Therefore provided you have sufficient as built records it doesnt matter what level of detail it is in provided it is placed on the original baseline programme.

It is best to work on the UTID rather than the WBS to cross link A B data to programme tasks.

If this is going to arbitration you will need an expert witness to give evidence so get someone on board ASAP plus a switched on solicitor.

Best regards

Mike Testro

Thanks Mike.

In order to avoid presuming something false; UTID? Unique Tracking ID, so could that be a WBS Level Summary Bar in Primavera? I am in the unfortunate circumstance, all the source files are on Microsoft Project.

Agreed on the expert witness; we should have one joining soon to attest to the procedure and be fully convesant come time of the tribunal.

I have followed your input throughout the threads and it appears prior to any execution of TIA, most of my time needs to be spent on worksheets, so I will be preparing an Events Schedule.

All the best,

S.

Also in addition, the TIA to be conducted will be under the 'window' analysis, an option I am unsure how it could effectively be used and prove useful.

If the as-planned is largely different from the as-built, I don't see how 1 or 3 month windows can provide much clarity, in particular if 2 additional elevation levels have been constructed,

I am of the idea to impact every event over the full course, in hope that I will see some alignment, or misalignment between the as-built summary, as 3 month windows would be useless over a project that has doubled in project duration.

Hi Stephen

UTID = Unique Task Identification.

It is a code that is unique to every task - not the same as a WBS which stops at trade level and is used mainly by bean counters.

Some planners just let the software generate random numbers of UTID but I prefer to have some meaning - for instance:

Design starts with D - Procurement P - Construction C - Test T etc.

Location add DL5 for level 5

Trade add DL5Ele  for electrical work

In this way you can generate UTID codes from level 1 to 5 level which will correlate to the levels in your programme.

This makes cross referencing the Events schedules amd As Built schedules much easier and is worth a little time before you start.

Don't bother with a "windows" analysis it just adds another layer of complication.

Make sure your events schedule shows the impact date of the event - not just the date on the document.

Good luck

Mike Testro