企业绩效管理网

 找回密码
 立即注册

QQ登录

只需一步,快速开始

查看: 384|回复: 1

Plan transfers in workforce-planning

[复制链接]

81

主题

411

帖子

598

积分

高级会员

Rank: 4

积分
598
QQ
发表于 2014-4-28 09:48:36 | 显示全部楼层 |阅读模式
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
回复

使用道具 举报

85

主题

414

帖子

607

积分

高级会员

Rank: 4

积分
607
QQ
发表于 2014-4-28 11:18:29 | 显示全部楼层
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.
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

QQ|手机版|小黑屋|企业绩效管理网 ( 京ICP备14007298号   

GMT+8, 2022-6-30 18:16 , Processed in 0.100380 second(s), 14 queries , Memcache On.

Powered by Discuz! X3.1 Licensed

© 2001-2013 Comsenz Inc.

快速回复 返回顶部 返回列表