Monitoring and acting on delays

Member for

11 years 5 months

Thank you for your reply.

Is the 10 day lead lag purely to give me and the PM's time to act on it?

Im not sure what i have done wrong when setting up my programmes because when i switch on "show Criticle path" all tasks are criticle. Is it becuase i have linked up every task so when i reschedule they all show criticle?

Back on the main subject.. I have been trying to monitor tasks using buffer tasks rather than lead lags. I thought that way it wouldnt push out the successors and instead consume the buffer. (i have made my buffer tasks as long as possible, in effect making them ALAPS) which is sort of what you were saying to do. I can look at all the buffer tasks in a table and can monitor them.  Do you think this is a good solution to stopping tasks being pushed out ?

Member for

19 years 10 months

Hi Sarah - Welcome to planning planet.

You need to concentrate on the availbale float so that when a design delay uses up float and becomes close to critical then you should start warning people.

At the same time you should be giving designers the Drop Dead date where their design must be complete for procurement.

This is done by setting the "design complete" milestone to ALAP with a 10 working day lead lag to the start of procurement - it will always show critical and will always attract attention.

If you have a large and complex project you can set up a "Traffic Light" system in a column that is easy to filter and report on at summary level.

Hope that helps

Best regards

Mike Testro

BTW I am pleased to note that you are using Asta as it should be done.