Is it possible to add columns to the labor rules calculations?

I need to have two different incentive plan calculations depending on the employee level. I wanted to populate a new column called Employee level and add in the advanced rules conditions for each of the employee level to drive the incentive plan calculation. 

Hmm no takers for this one, yet. Let's try some CSMs with impressive ITP skills. Kelly @Kelly De Bartok or Brittany @Brittney Rodriguez do you know?

Hi.

Currently the labor rates functionality does not allow you to add user-defined columns or attributes.  Off the op of my head, have you considered creating multiple roles for each employee level?  For example, "Director - Level A" and "Director - Level B".  This should allow you to then apply different incentive plan rates for each.  The downside would be that you will need to maintain two (or more) of each role.  In some organizations it may not be an issue but if you have a very deep org title structure then this may not be the best option. 

I'll see if I can think of some other way to provide the flexibility you're looking for.

Hi,

Bill is correct, you can not add an additional coloumn into the labor allocation rules. I have however had a request from another customer to add incentives based on a level and so we added level into the roles reference dataset so we could filter on this in the line items view. Then before we uploaded the base compensation into the labor rates reference dataset we calculated the incentive in excel and added it there (base compensation + Incentive). This way you do not have to maintain two roles for each but you end up with the additional level information in ITPF. It does however add more manual work before loading into ITPF but at least it gives you an accurate compensation and in turn a more accurate budget.

I do suggest that you add this to the ideas page on the IT Planning product page so other people can vote on it and maybe it can end up in the product as I think it is a great feature for the future:https://tbmcouncil.jiveon.com/community/apptio/product-central/itplanning/create-idea!input.jspa?containerID=2162&contai… 

Please let me know if you have any additional questions. I will also keep on thinking of a better solution within the tool.

Thanks,
Lauren Griessel

Thank you @Bill Baroniunas and @Lauren Griessel for your ideas and feedback. You made me think of another alternative that will fit better in my environment. I already use the vendor column to determine when to calculate labor chargeback, since the population I need to account for the incentive plan does not do project work, I will create a new "vendor" for this purpose.

The role and level columns I need to preserve intact to move data back and forth with Hyperion.

Great idea.  I had another client who did something similar where they used the Vendor field and added a vendor called "HR" to handle that use case.