Do you generally calculate time for prep activity as some sort of percentage time , utilised for actual actvity.
Today i was surprised tolearn that the activity of 10 hrs duration ,which i am tracking ,required an effort of 3 persons for full 12 hours yesterday so that activity can be started today .
I guess it is time for me to keep eye on preparatory activites , and resources required for the same.
Food for thought about prepartory activities . . . if there is a resource change of hands, even within the same company, consider breaking out the acitivity. Additionally, be guided by managable activity durations. Site activities greater than 30 calendar days should be split into increments not exceeding 30 calendar days to enable identification of slippage or production deviation in time to recover.
This is always something that we encounter when describing activities. When discussing with the engineers, they always fail to think of the "preparatory" activities. As a result the activities always take longer that shown on the project.
Yes, you could insert the prep. activities as an individual task, but it then becomes a monster to update. Personally, I try to ensure that the duration of the task takes account of the prep. activities. This is where the individual programmers style is employed - in knowing the full content of the activity as opposed to just its name.
James.
Member for
20 years 6 months
Member for20 years7 months
Submitted by Zhang Haixiang on Sun, 2006-08-27 22:41
Member for
19 years 2 monthsRE: Delay due to preparatory activities.
Hi guys ,
Do you generally calculate time for prep activity as some sort of percentage time , utilised for actual actvity.
Today i was surprised tolearn that the activity of 10 hrs duration ,which i am tracking ,required an effort of 3 persons for full 12 hours yesterday so that activity can be started today .
I guess it is time for me to keep eye on preparatory activites , and resources required for the same.
Member for
20 years 9 monthsRE: Delay due to preparatory activities.
Food for thought about prepartory activities . . . if there is a resource change of hands, even within the same company, consider breaking out the acitivity. Additionally, be guided by managable activity durations. Site activities greater than 30 calendar days should be split into increments not exceeding 30 calendar days to enable identification of slippage or production deviation in time to recover.
Member for
21 years 1 monthRE: Delay due to preparatory activities.
Hi,
In cases as descibed - I usually use the activty description as "Procure & Install" and have a duration that reflects the activity.
John
Member for
19 years 5 monthsRE: Delay due to preparatory activities.
Hi Vinod,
This is always something that we encounter when describing activities. When discussing with the engineers, they always fail to think of the "preparatory" activities. As a result the activities always take longer that shown on the project.
Yes, you could insert the prep. activities as an individual task, but it then becomes a monster to update. Personally, I try to ensure that the duration of the task takes account of the prep. activities. This is where the individual programmers style is employed - in knowing the full content of the activity as opposed to just its name.
James.
Member for
20 years 6 monthsRE: Delay due to preparatory activities.
for me this is not a problem.
task name is only a short description of a set of works.
e.g. "nozzle installation" make contains some hidden works, get the nozzle from warehouse, then goto jobsite....
any delay will cause "nozzle installtion" delay, so when update this task, show the delay thats all.
You do not need to think in such a detail way.
But some preparation works are very important, and should be consider as task. for example pipe fabrication,equipment procurement/delivery...
HTH