Page 1 of 1

How to separate Capex & Opex WBSs?

PostPosted: Tue Jun 03, 2014 9:32 am
by Bezladnova
Hi Gurus,

Please can you knidly share how other companies differentiate between Capex & Opex WBSs?

We normally have some Capex & some Opex WBS under one Project Profile. So we need different validations & user input depending on if it is Capex or Opex WBS.

Ideally, we would have user just choosing between Capex or Opex option & all validations & diffrence in required input to follow.

Currently we use Field Keys for this & later refer to them in a validations. This has lots of disadvantages, so I wonder how other companies do it.


Thank you!

Re: How to separate Capex & Opex WBSs?

PostPosted: Thu Jun 05, 2014 10:54 am
by knowledgeWorx
We have a fixed naming scheme, usually our WBS are named <project id>.x.12345 where x is either 1 or 7, indicating capex or opex. The structure is created from a project template, of course. However, I'm not sure if this solution is optimal either. Would also like to hear how others do it.