Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

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.

Calculated time vs duration

3 replies [Last post]
floris gering
User offline. Last seen 1 year 51 weeks ago. Offline
Joined: 30 Jul 2014
Posts: 23

I have for example a safety valve which has to be replaced and calculated the disassembly and assembly time for example to be 2 hours.

My colleague scheduler says he always sets the duration for this activity to 10 hours (in this case the length of a shift), because he is only interested in the fact that the work on the safety valve is done on a specific day during this shift and not exactly in which 2 hours it is done.

Is this good practice ? Why ? (or why not)


Zoltan Palffy
User offline. Last seen 2 days 13 hours ago. Offline
Joined: 13 Jul 2009
Posts: 2891
Groups: None

if the planning units is in hours then show the 2 hours because if you show 10 hours as others have stated it will over alloate the resource and it will also prevent follwo on work from starting sooner. 

bad practice

replace safety valve #1 - 10 hours-----> replace safery valves #2 - 10 hours = total 20 hours 2 valves replaced

good practice

replace safety valve #1 - 2 hours-----> replace safert valves #2 - 2 hours -------> replace safety valve #3 - 2 hours-----> 

replace safety valve #4 - 2 hours-----> replace safert valves #5 - 2 hours -------> = total 10 hours 5 valves replaced


now if your planning unit was days then the smallest unit of time that you can plan for is 1 day regarless if it takes 2 hours or 10 hours to do it is still 1 day. 


Steven Auld
User offline. Last seen 5 hours 31 min ago. Offline
Joined: 13 Sep 2017
Posts: 122


I agree with Vladimir, each activities duration should be based on how long it is estimated to take.

If you allocate 10 hours to 1 safety valve that takes only 2 hours to complete, then the Resource availability will no longer show as available for other activities.

If you have 5 safety valves to overhaul then by allocating only the required 2 hours per safety valve, then all could be completed within a 10 hour shift.

If you have allocated 10 hours then this would mean that you would not show sufficient resource availability & would drive the duration out to 5 shifts to complete this scope of work.

In the shutdown plans that I work on, resource availability is the single critical driver for the shutdown duration due to limited bed space availability. To incorrectly allocate durations would have a significant impact on the overall shutdown duration & would also reduce the amount of work that could be completed wihtin the Critical Path duration.



No, it is not best practice.

Best practice includes assigning resources to project activities and calculation of resource constrained schedule based on volumes of work to be done and assigned resource productivities. Activity duration shall be calculated and resources optimized.

Activity duration does not depend on assigned resources only for few activity types.

Duration based schedules may be used only if the job will be done by someone else and the schedule is used for contract execution analysis.

Shutdown projects are usually planned at least in hours (better in minutes) because delays cost a lot. Good schedule optimizes resource usage and minimizes project duration.