Reserve Admin and KTLO Time for Resources
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2016 06:50 PM
We're just getting ready to start using resource management for the first time in Geneva and have been building out test cases. I'd like to reserve Admin and KTLO hours for a given resource so that time is reserved on the Resource Management Workbench when people are looking to book them to projects and they don't risk getting overbooked. An example would be for someone who spending 10 hours a week on Admin and has 30 hours available for project work. What would be the best way to show the 10 hours baselined for that resource? I would need to vary it by resource so that a different resource might have only 5 hours of Admin time per week reserved.
I think this could be done by setting up a KTLO project and allocating resources to that project, but we'd like to use the KTLO bucket as is in the time cards since we were advised against this project based approach during earlier Service Now meetings.
Any advice or related experiences would be appreciated.
Thanks!
Erin
- Labels:
-
Resource Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2016 07:38 PM
A completely different approach: Have you considered reducing the 'Average daily FTE Hours' value for users?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2016 06:21 AM
Thanks, Kelly. We were hoping to keep see the planned Admin and planned KTLO assumptions in the application for each person so we could track against them, but if needed, I suppose we could keep those assumptions offline. Thanks for the suggestion.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2016 06:26 AM
Hi Erin,
Are you using Demand management? If so, what do you think about creating a new type of Demand for Operational Work (Resource Plan)?
The guidance about NOT logging time against the project is that you lose a lot of granularity in data that you could otherwise have if you logged your operational time directly against a incident, change, problem, etc.
The only downside is that you wouldn't get the actuals logged directly against the resource plan OOB. You would have to "compare" the planned hours from the resource plan with the actuals from time cards. You could manually allocate this time to the resource plan though..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2016 06:43 AM
Thanks, Emily. We are planning to use Demand Management and that approach was our first inclination. I appreciate the clarification on the guidance not to use the project, that makes sense.
If I created an Admin demand record for all of department members, I would need to create multiple tasks for each group or resource in order to have it pull the task into their timecard when they "Generate Time Cards", right? Just want to make sure I'm playing the scenario out correctly.