every planner knows that wbs and code structure are essential elements needed to successfully maintain a primavera p6 schedule network.
but what about your primavera p6 activity names?
a sometimes overlooked schedule quality issue is the use of well articulated activity descriptions. planners who began their career in p3 or earlier versions were limited to 48 characters in the activity description. this has created an industry habit of abbreviations and acronyms that at times may only be understood by a small group of individuals knowledgeable of the project. one of the key roles of a planner is to present the execution plan to the project team. poorly named activities can cause confusion, disagreement among the vested stakeholders and in some extreme cases manifest themselves in schedule delays.
5 tips to improve your primavera p6 activity names
newer versions of primavera p6 and beyond allow many more characters in the activity description field. follow these 5 simple tips to improve the overall quality of your schedule network and respective activity descriptions.
1. use an action word.
when adding an activity description you always want to add an action word first. for construction related activities consider such words as install, construct, place, or fabricate. for engineering use action words such as develop, issue, or incorporate. make sure you follow the action by the activity to be performed.
for example: “install lower base slab”.
2. don’t abbreviate unless you absolutely have to.
when developing your activity descriptions do your best to spell out what you are trying to say.
for example instead of
“frep lwr fndn concrete”
try
“form, rebar, embed & place lower foundation concrete.”
the more abbreviations your schedule contains, the greater potential for confusion, particularly for those unfamiliar with the schedule or your naming conventions.
3. be descriptive!
the activity description needs to be as descriptive and detailed as possible. for construction activities consider adding the location, utilizing column references, direction, room numbers, and floor elevation.
example: “install north lower base slab col 1 – col 5, floor 1”.
this type of description will give your reader vital information about where this activity is physically located. always assume that your reader will not be using your code grouping & sorting when reading yours schedule. make sure each activity can stand on its own without any coding headers.
4. uniformity
developing standard activity descriptions, similar to activity ids, will help standardize your schedule. try to come up with a standard structure that can be conveyed to the entire planning team. this is especially good practice when working with multiple users in the same program.
an example for an engineering schedule could be “*action word* – *deliverable* – *system*”. below are some other examples to help keep uniformity in the schedule.
use the <action word> – <deliverable> – <system> template.
1). develop mechanical data sheet – horizontal pump
2). issue piping isometrics (dwg #) – cooling water system
3). issue rfq (po #) – horizontal pump
4). award purchase order (po #) – horizontal pump
5. don’t scream!
there is no need for all of your activities descriptions to be capitalized! for some reason there are several planners that prefer to work in all-caps. do us all a favor and please turn the caps lock off. there is no need to scream and it adds no value to the final product.
wrap-up
tell us what other rules you use for naming your activities when developing a schedule network.
