Plan transfers in workforce-planning

奪命排骨飯

Hi,

We have a requirement in our project ( workforce-planning) to plan employee transfers from one dept to another for any future month.
For example, Employee A is getting transferred from Dept 1 to Dept 2 in Sep-13, we have built the system in such a way that the existing Dept (Dept 1) is responsible for that employee expenses till sep-13 and transfer the expenses which are after Sep-13 to dept 2. But our client wants an approval process for planning the employee transfers to avoid any failure from receiving department to recognize the incoming employee. Please let me know if you have already done some kind of approval process and provide us some overview of it. We have also seen in one of the white paper that IBM has a mechanism in their Tm1 salary model 'Blueprint', If anyone has seen the mechanism in blueprint, please share with us too.

Regards
Jagan

hezi15826738412

jagan_Palanisamy wrote:We have a requirement in our project ( workforce-planning) to plan employee transfers from one dept to another for any future month.

This depends on whether you are doing workforce planning by role, by employee or both. For the first option you should have Role Id and Department as dimensions in your planning cube. For the second option, you should have Employee Id and Department. For the latter option, you should probably have all three - this is maximum flexibility as it allows for employees to move between roles, and both employees and roles to move between departments.

jagan_Palanisamy wrote:But our client wants an approval process for planning the employee transfers to avoid any failure from receiving department to recognize the incoming employee.

Planning the costs and recognising approval workflows are two completely different things. You can have a technical solution to move employee costs around the organisation that is independent of whether the receiving department accepts them. One way to account for the separation is having different elements in a version dimension, or perhaps measures dimension, such as 'Pending' or 'Approved' to account for workflow state. You could have rules that work like this to facilitate moving the costs based on a lookup to workflow state cube:
Code: Select all['Approved'] = N: IF ( DB ( 'Transfer Approval', !Scenario, !Year, !Month, !Employee Id, !Department, 'Approved' ) @= 'Yes', ['Pending'], STET );
Now, you just have to figure out how to get department managers to enter data into the Transfer Approval cube.