F
Frank Jutte
Hi,
I would like to share my experience with settin up a Timesheet Approval
Route in combination with a RBS. Before I explain my rather simple scenario I
must say that this is one of the area's in Project Server where you have to
do a lot of research on your own, there's not that much info on the net or
anywhere else that explains in detail how to handle. Anyway, this is my
scenario and solution:
1) We have a delivery manager that is the only person in the org that should
be able to approve all Timesheets
2) We have multiple Managing Consultants that have the DM as their default
Timesheet Manager, they must be able to accept Timesheets but not be able to
finally approve them
3) We have multiple Resources that each report to one of the Managing
Consultants (set by the Default Timesheet Manager property)
My RBS looks like this:
Holding
|------------Delivery Management
|------------ Managing Consultant Projects
|------------Project Managers
|------------Engineers
|------------Developers
|------------Managing Consultants Managed Services
|------------Service Managers
|------------Engineers
|------------Developers
2 specific permissions that play an important role are:
Accept TimeSheets : Both the Managing Consultants and the Delivery Manager
need this permission. Having only this permission will prevent you from final
approvement of a TimeSheet
Approve TimeSheets : Only the Delivery Manager needs this permission as this
person is the only person that is allowed to finally approve a TimeSheet
These permission will be handled by a security template that I will describe
later.
How did I set up this scenario in Project Server 2007:
Group: Delivery Management
Group: Managing Consultants
Add applicable user(s)
Add applicable user(s)
Group Global Permission: Accept Timesheets ---------------->
Group Global Permission: Accept Timesheets ---------------->
(needs to be set explicitly, even when set in a
|
|
security template, cannot
explain this but you
|
|
need it!!!)
v
v
Category: MyDirectReports Delivery Management
Category: My Direct Reports
Resource section: They are descendants of the user via RBS
Resource section: They are direct descendants of the user via RBS
Groups & Users: Delivery Management
Groups & Users: Managing Consultants (and the Resource Managers by
default)
^
^
|
|
|
|
Create Security Template: TimeSheet Manager DM
Create Security Template: TimeSheet Manager MC
Permissions: Accept TimeSheets and Approve TimeSheets
Permissions: Accept Timesheet (means you cannot finally approve a TimeSheet)
You can apply the TimeSheets by selecting the Group (or User) in the
Category, a permission grid will appear and below the grid you can choose a
security template and apply it to the group.
So in short what this set up does for you is:
It lets the Delivery Manager directly final approve TS's from the MC's
It lets the Delivery Manager indirectly final approve the TS's from other
resources in the org (1 or multiple levels below him/her in the RBS)
It lets the Managing Consultant to accept TS's from their resources without
the ability to final approve these Timesheets, Next Approver is by default
the Delivery Manager
It lets the Resources to submit TS's to their (default) Managing Consultant
TS's from the Delivery Manager will be auto approved by the system
A TS rejected by either the MC or the DM will result in returning the TS to
the resource directly.
If no fixed approval routing has been set then resources will be able to
point to another TS manager in case their default TS manager is unavailable
(holiday etc.).
Hope this explains the way you can combine the RBS with a TimeSheet approval
route. As said this is quite a challenging area in PS2007 that needs a lot of
trial and error bfore you get a grip on it. The one thing in this set up that
is not clear to me is why I have to set the Accept Timesheet permission in
the Group's Global Permission area as well as in the Security Template, I
would have thought that setting it in the Security Template (just as the
Approve TimeSheet permission) would be sufficient.
Rgds,
Frank Jutte
Winvision
http://www.winvision.nl
I would like to share my experience with settin up a Timesheet Approval
Route in combination with a RBS. Before I explain my rather simple scenario I
must say that this is one of the area's in Project Server where you have to
do a lot of research on your own, there's not that much info on the net or
anywhere else that explains in detail how to handle. Anyway, this is my
scenario and solution:
1) We have a delivery manager that is the only person in the org that should
be able to approve all Timesheets
2) We have multiple Managing Consultants that have the DM as their default
Timesheet Manager, they must be able to accept Timesheets but not be able to
finally approve them
3) We have multiple Resources that each report to one of the Managing
Consultants (set by the Default Timesheet Manager property)
My RBS looks like this:
Holding
|------------Delivery Management
|------------ Managing Consultant Projects
|------------Project Managers
|------------Engineers
|------------Developers
|------------Managing Consultants Managed Services
|------------Service Managers
|------------Engineers
|------------Developers
2 specific permissions that play an important role are:
Accept TimeSheets : Both the Managing Consultants and the Delivery Manager
need this permission. Having only this permission will prevent you from final
approvement of a TimeSheet
Approve TimeSheets : Only the Delivery Manager needs this permission as this
person is the only person that is allowed to finally approve a TimeSheet
These permission will be handled by a security template that I will describe
later.
How did I set up this scenario in Project Server 2007:
Group: Delivery Management
Group: Managing Consultants
Add applicable user(s)
Add applicable user(s)
Group Global Permission: Accept Timesheets ---------------->
Group Global Permission: Accept Timesheets ---------------->
(needs to be set explicitly, even when set in a
|
|
security template, cannot
explain this but you
|
|
need it!!!)
v
v
Category: MyDirectReports Delivery Management
Category: My Direct Reports
Resource section: They are descendants of the user via RBS
Resource section: They are direct descendants of the user via RBS
Groups & Users: Delivery Management
Groups & Users: Managing Consultants (and the Resource Managers by
default)
^
^
|
|
|
|
Create Security Template: TimeSheet Manager DM
Create Security Template: TimeSheet Manager MC
Permissions: Accept TimeSheets and Approve TimeSheets
Permissions: Accept Timesheet (means you cannot finally approve a TimeSheet)
You can apply the TimeSheets by selecting the Group (or User) in the
Category, a permission grid will appear and below the grid you can choose a
security template and apply it to the group.
So in short what this set up does for you is:
It lets the Delivery Manager directly final approve TS's from the MC's
It lets the Delivery Manager indirectly final approve the TS's from other
resources in the org (1 or multiple levels below him/her in the RBS)
It lets the Managing Consultant to accept TS's from their resources without
the ability to final approve these Timesheets, Next Approver is by default
the Delivery Manager
It lets the Resources to submit TS's to their (default) Managing Consultant
TS's from the Delivery Manager will be auto approved by the system
A TS rejected by either the MC or the DM will result in returning the TS to
the resource directly.
If no fixed approval routing has been set then resources will be able to
point to another TS manager in case their default TS manager is unavailable
(holiday etc.).
Hope this explains the way you can combine the RBS with a TimeSheet approval
route. As said this is quite a challenging area in PS2007 that needs a lot of
trial and error bfore you get a grip on it. The one thing in this set up that
is not clear to me is why I have to set the Accept Timesheet permission in
the Group's Global Permission area as well as in the Security Template, I
would have thought that setting it in the Security Template (just as the
Approve TimeSheet permission) would be sufficient.
Rgds,
Frank Jutte
Winvision
http://www.winvision.nl