Forum to discuss challenges and successes regarding Project and Turnaround Management methodologies. Specifically, the theme will focus on the development and integration of planning and scheduling best practices for On-Shore and Off-Shore asset Turnarounds, Projects and O&M activities. By applying simple processes aligning key stakeholders addressing real issues at the right time the facilities we operate will be sustainable and safe.
Saturday, March 5, 2011
Primavera WBS
It seems that quite a few of us are not using Primavera's WBS structure. Recently I have been developing the WBS down to the WO#; the latest being 6 levels. Is anyone else doing this for TA's?
3 comments:
Anonymous
said...
MIKE
I have the turnaround project schedule which uses wbs structure to only level 1. I dont know the benefits of using more levels of WBS.Most of the time i will be using the activity codes to sort and group the projectas per the reqirement.
I have the turnaround project schedule which uses wbs structure to only level 1. I dont know the benefits of using more levels of WBS.Most of the time i will be using the activity codes to sort and group the projectas per the reqirement.
Yes...one WBS Level is very common. I use both activity codes and a detailed WBS. Typically, what works for me is a a loading layout which is similar to the Classic WBS with all columns for activity codes. This allows me to use the fill down option to save time. More to do with the detailed WBS levels. I find the reporting capibilites better. This way I can report to any indvidual area, asset etc more accurately. Futhermore understanding variance and risks by location.
When the TAR is over and you wish to create a reusable template schedule the WBS easily allows the scheduler a clean avenue to update by component.
3 comments:
MIKE
I have the turnaround project schedule which uses wbs structure to only level 1.
I dont know the benefits of using more levels of WBS.Most of the time i will be using the activity codes to sort and group the projectas per the reqirement.
MIKE
I have the turnaround project schedule which uses wbs structure to only level 1.
I dont know the benefits of using more levels of WBS.Most of the time i will be using the activity codes to sort and group the projectas per the reqirement.
Yes...one WBS Level is very common. I use both activity codes and a detailed WBS. Typically, what works for me is a a loading layout which is similar to the Classic WBS with all columns for activity codes. This allows me to use the fill down option to save time.
More to do with the detailed WBS levels. I find the reporting capibilites better. This way I can report to any indvidual area, asset etc more accurately. Futhermore understanding variance and risks by location.
When the TAR is over and you wish to create a reusable template schedule the WBS easily allows the scheduler a clean avenue to update by component.
Post a Comment