comments on: thou shalt not group by wbs alone – try grouping by p6 activity codes - 瑞士vs喀麦隆足彩赔率

by: guadalupe keedah

sun, 20 jan 2019 12:36:09 +0000

nicely put, appreciate it.

http://whatsappand.tumblr.com

]]>

by: jerome ijachi odeh

mon, 07 aug 2017 07:46:32 +0000

in reply to viet tran.

viet,

how are the heat exchangers shown in p6?

without seeing your schedule but based on having done something similar a couple of years ago, i’d use 3 udf fields:

1 – total: for total number of heat exchangers in an activity
2 – completed: for number of heat exchangers cleaned
3 – cleaned %: for % complete status of cleaned heat exchangers

the “total” udf field only needs to be updated once while the “completed” udf field needs to be updated anytime the associated activity is updated. and the “cleaned %” can be updated using global change.

if your schedule is resource loaded or has cost data, you will be able to roll-up these 3 udf fields to wbs level to get summary status.

=jerome

]]>

by: viet tran

mon, 07 aug 2017 02:14:09 +0000

thanks for your writing, mr. jerome.
i have a problem need you and someone can help me. my boss want me to count the number of equipment in p6, not count the number of activities. for example, he wants me to count the number of heat exchanger has been clean and overhaul by days but i can not count because p6 only count the number of activities?

thanks all,

]]>

by: jerome ijachi odeh

fri, 14 jul 2017 11:22:45 +0000

in reply to josh.

josh,

i’m not on skype.

you can send me a message through my blog at https://plannerstips.blogspot.co.uk/p/contact.html

=jerome

]]>

by: jerome ijachi odeh

fri, 14 jul 2017 11:21:31 +0000

jonathan nielsen. thanks jonathan.]]>

by: josh

fri, 14 jul 2017 10:50:59 +0000

nice article and insightful for beginner. jerome..can you message me please josh.agyare1 on skype

]]>

by: jonathan nielsen

thu, 13 jul 2017 12:10:41 +0000

great stuff jerome, thank you for putting this together. i will definitely be referring to this in the future

]]>

by: jerome ijachi odeh

wed, 05 jul 2017 14:25:33 +0000

in reply to derek cairns.

good points derek.

thanks for reading.

=jerome

]]>

by: derek cairns

wed, 05 jul 2017 14:12:33 +0000

good article and much needed. i’ve been using activity codes like this for years, but that’s because i go back to the days when you had to. however, it’s a feature of p6 that you can still define your own coding structures. if you don’t already use code fields as a matter of course, try it out. you will soon wonder how you managed without them, whether it is to provide a separate group and sort, as described above, or for other reasons – great for filtering, for instance. a word of warning – if you have your file grouped on activity codes these will be applied automatically to ne w activities as you add them. however, your wbs will be allocated at the top level so you may need to go back and review that. alternatively. add activities under the wbs structure (safer, assuming it is important to you) you will still need to allocate the relevant code values. it is also good practice to use properly defined and structured coding – this can carry so much additional information about your project and gives you options when selecting specific filters for specific purposes. it might also help you to avoid an over-complicated wbs.

]]>