Clarity

Hello,

I have a client who wants to use Other Work in order to plan and track non project time ( vacation, absence, sick, training, etc).

They want each OBS unit manager be able to plan their resources non project time in the corresponding Other Work NPIO, the will have one for each type, for example: vacation, training, absence, etc. They will assign all the resources of all the units to each of these Other Works, the problem is that  each manager could see and modify other managers resources, the client wants each manager can see and modify only their resources. The only way I think this could be done is to have Other Work separated for each OBS and give access rights by OBS. 

Do you have any recommendation or have you use a different approach to solve a similar situation?

Thanks a lot for your advice.

Pilar

We currently have the same issue and have developed a slightly different solution.  Once we have finished testing I will post the solution.  We will implement January 1, 2017 so we are almost finished.

Keith

Thanks very much for your answer Keith, have you go to production with your solution.?. I will appreciate very much if you could share some details about .

Best Regards

Pilar

We're converting from Indirect to Other Work for the same set of topics that you reference.  We are creating separate instances of each - 8 groups, 8 instances each of absence, vacation, training, etc.  Then,

- put each groups' instances under a parent instance which is turned off to time entry

- assign one manager from each group to manage the group's instances

- create a security group that has booking rights for the groups resources and other work instances

- carryover the Charge Codes we had used in Indirect, assigning them to our new Other Work instances

This way, each group owns their own set of "indirect" Other Work instances - they own it and they can manage their own resource allocations according to local needs.

We are also changing the Team\Default Allocation value to 0%.  Now, this value is applied to all investment types and we have some groups upset that the default will be 0% on projects, too.  For them, we are training them on how to use the "Set Allocation" action on the Team\Staff page, and we are also considering the development of a custom "Set All Allocations" action, one which will set the default allocation of all team\staff as the out of the box action is limited to selecting one page of Team\Staff at a time.

We stay away from granting rights directly to OBS branches.  Granting rights via OBS branches is easy, but its very difficult later to trouble shoot/maintain.  Also, we want to separate the acts of resource editing vs. security access - we don't want a resource editor to be able to change the security access rights of a user by changing the user's assigned OBS branch.  But, that's us.  Can also envision a scenario where one might move the OBS fields on resource to a secured subpage and develop a portlet that would display the rights assigned to OBS branches - a scenario where the trouble shooting/maintenance/security issues are addressed.  If one doesn't address such concerns, stick with using security groups.

Expect to go live before end of 2017Q1.

Thanks a lot Dale for your very detail explanation, it is what my client needs to do, have each group been able to manage only their own resources for the other work instances.

Best regards

Pilar