Website Upgrade Incoming - we're working on a new look (and speed!) standby while we deliver the project

Tips on using this forum..

(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.

How to deal with Bad Records

2 replies [Last post]
Aidan Kelly
User offline. Last seen 13 years 1 week ago. Offline
Joined: 5 May 2011
Posts: 24

Hi all

 

Ive been asssigned onto a civil project that is approx 50% complete and has no approved or logical baseline (open ends, hanging activites and unapplicable activties).

Records to date have been inaccurate. The entire management structure has been changed and i've assigned to compile change orders for extra scope, disruption and EOT. Change order is the only mechanism in the contract for cost/time increase.

For EOT demonstration has anyone got some advise on dealing with poor records?

The current recovery/forecast schedule (level 4) has absorbed all the delays to date without culpability or payment to contractor (us). Most of the delays are underground obstructions, change in working methods and procedures.

Would a very theoretical approach suit in this case?

Regards


Aidan 

Replies

Aidan Kelly
User offline. Last seen 13 years 1 week ago. Offline
Joined: 5 May 2011
Posts: 24

Thanks Mike for the tips.

Baseline is not resourced but the disruption or more accuately described as lost/unproductive hours is quantifiable as it is mainly the delay in issuing permits resulting in idle time.

Will look up other threads on this.

Regards

Aidan

 

 

 

 

 

 

Mike Testro
User offline. Last seen 28 weeks 6 days ago. Offline
Joined: 14 Dec 2005
Posts: 4420

Hi Aidan

In other words -situation normal.

Since your programme is currently unapproved I would start from the original programme before any progress updates and then tighten up the logic and removing all constraints - try to establish a clear critical path.

Make sure you do this BEFORE making a detailed study of the delay events.

Hint - this is done much quicker if you open up the .xer file in PowerProject - make the adjustments and save it back as an .xer for P6.

Then make a spreadsheet log of all your change orders and make a chronological list of dtate of event impact of the events - that is the earliest possible date that the affected task could have started.

Now create dummy tasks of each event in turn and impact it to the affected task - reschedule and note the effect.

Go on to the next delay event and repeat the process.

Make sure that all contractor's delay events are included in the matrix.

This will establish your entitlement to any EoT.

Disruption is a totally different matter and you will need a fully resourced baseline programme before you even think about it.

Check other threads on the topic anmd come back if you need more help.

Best regards

Mike Testro