Resource Management - Troubleshooting Guide

[abhinaykumar]

This article provides detailed steps for troubleshooting aggregate-related issues and using Resource Diagnostics to identify data anomalies. 

1.How to proceed when the schedule is updated, but the aggregate tables do not reflect hours? 

Scenario-1: 

In Resource Management, schedules are cached to improve the performance, please clear the cache when there is a change in the schedule and then update the capacity. 

Scenario-2: 

Dates on the schedule are not completely covering the duration of capacity you are looking for. Review the dates on the schedule - The date value on ‘Start date time’ field is the start date of the schedule and ‘Repeat until’ field is the end date of schedule. 

2.What to do when capacity is not reduced after defining a holiday in the schedule?   

Scenario-1: 

If holiday is added in Schedule Entry, then record type must be Excluded. 

  

Scenario-2: 

If holidays are in Child schedule, then Child schedule type must be Include.  

3.How to resolve the issue of capacity splitting between days?  

Check the Time zone field on schedule. 

The Time zone field value on the schedule must be Floating. If the value is not Floating, the Time zone field value must be same as that of the Time zone field value of the user record for which the schedule is attached, or for the user who updates the aggregates. 

4.How to allocate resources only up to  user’s capacity? 

If you do not want to over-allocate a user, always use Resource Finder for confirming / allocating the resource plans. This is because resource finder restricts the confirmation / allocation only up to the scheduled hours whereas form or workbench confirmation / allocation will attempt to allocate up to 24 hours. 

5.How to avoid the situation of having left-over capacities when users schedules are in decimal? 

Resource allocations use the calendar event duration (‘com.snc.resource_management.allocation_interval_minutes’) property to create allocations with a decimal value.  

If the value of this property is set to 60 minutes, the allocation is given to the 60-minute block.  

If the value of this property is set to 30 minutes, and 1 hour needs to be allocated to the user, the allocation is divided into the two 30-minute blocks when the user is available.   

If User’s Scheduled Hours, ends with	Calendar Event Duration, value should be set to
0.5	30
0.25/0.5/0.75	15
0.2/0.4/0.6/0.8	12
0.1,0.2….	6

 NOTE: It is recommended to set this property to 60. If your organisation is keen in tracking time in minutes, it can be set to a lower value. 

If the scheduled hours are not divisible by the calendar event property, then there will be a loss of few hours for each day.  

Example: User’s per day scheduled hours are 8.5 and if the calendar event property value is 60. 

In this case the maximum allocated hours for each day will be 8, resulting in a loss of 0.5 hours per day. 

  

6.How to proceed when there is over or under allocation after allocating for the FTE or Person Days plan? 

The ’Average Daily FTE Hours’ field value on the User or Group record should be same as the scheduled hours for a day. If the values are not same, then the resources might get over or under allocated when resource plan of FTE or Person days type is allocated. 

 The Average Daily FTE Hours (‘com.snc.resource_management.average_daily_fte’ )property value is used as the full-time equivalent if no value is specified in the ‘Average Daily FTE Hours’ field on the user or group record.  

Resource Diagnostics:  

Resource Diagnostics can be run by users with the ‘pps_admin’ role to detect corrupt aggregates and daily allocation data.  

Following are resource management diagnostics: 

• Dailies without top task 

               -Identifies project-related resource allocation dailies without a top task. 

• Duplicate aggregates for users  

                -Identifies ‘project_allocated’ or ‘project_confirmed’ category entries in all resource aggregate tables with empty task. 

• Aggregate issues with demand to project conversion (Available from ‘Quebec’ release onwards) 

                 -Identifies all resource allocation daily and all resource aggregate table entries that are still pointing to demand after project conversion. 

• Top task on allocations is no longer a top task (Available from ‘Quebec’ release onwards) 

                 -Identifies all resource allocation daily entries that have top task pointing to previous top task after reparenting project.

[Aditya24]

Hi Abhinay,

I am observing a different behavior for the calendar event property than what is mentioned in this article. I was hoping if you can suggest me why this is like that.

I have my daily FTE for a user as 7.6 and my calendar event property is set to 60 minutes.

Case 1: Now when I create a resource plan (spanned over two day period) of 10 hours with FRONT LOAD and confirm the same. It generates two entries, one for 7.6 hours and other for 2.4 hours. Question is, why it is not taking that 60 minute event property and generating decimal value entries?

Case 2: When I create a resource plan for 7.6 hours for one day only and confirm the same. It generate one entry which is of 7 hour only. Here it is taking the property in consideration but not in case 1. 

Case 3: I create a resource plan of 1 FTE for a day then it creates an entry only for 7 hours so it works in all the cases except for case 1.

Please suggest what I am missing.

[abhinaykumar]

Hi @Aditya 

The idea behind front load is to completely allocate one day before moving on to the next. There will be no capacity gaps because it is designed in this way.

If you need to plan for 7.6 hours, change the calendar property to 12 and it will work in all cases.

Thanks,

Abhinay Kumar Nandagiri.

[PaulaaO]

@abhinaykumnandagiri Thanks for sharing this article.

I'm trying now to familiarise myself with the Resource Diagnostics feature - may I ask whether I can check the output of the scan anywhere? Or does it just require of me to built a fix script to correct the data? I would be interested in seeing it first, if possible. Thank you.

[abhinaykumar]

Hi @Paula 

Data correction scripts are typically not included with diagnostic scripts because the data must be corrected based on the situation at hand.

We also need to figure out what is causing the corruption.

Please open a case and describe the issue; we will assist you in determining the root cause and correcting the data.

[Michelle Alexan]

We have created a schedule for 7.5 hours a day.  We have set the following properties:

Average Daily FTE Hours/Hours Per Person Day (This value is used for converting FTE and person days to hours in resource plans) 7.5

Calendar Event Duration (Minutes) 30

We have updated resource aggregates and resource capacity.

It does not seem to be updating the resource plans fully.

Can anyone advise what will be updated on the resource plan and what will require a fix it script?

FTE to Planned Hours Ratio?

Planned hours breakdown?

Allocated hours breakdown?

If a fix it script is required can anyone provide any tips to ensure all items are updated appropriately?

[Talya]

Hi @Michelle Alexan , 

I am in the same situation. We have created a schedule for 7.5 hours a day. Calendar Event Duration (Minutes) 30.

Can you please tell me the activities done other than updating resource aggregates and resource capacity?

It will be very helpful.

Thanks,

Talya

[ChrisUSC84]

What does the property com.snc.resource_management.percentage_allocation_normal update? It isn't the capacity planner grid.

[psyherin]

Hi @abhinaykumar ,

With property Average Daily FTE Hours (‘com.snc.resource_management.average_daily_fte’ ) which cannot be changed to decimal (default is 8).

The problem is that in the Project management workspace and Resource Management workspace it always looks at this FTE value and compares it with the FTE on group or the user record (for eg. 7.5). Once we assign the work to the resource it still leaves the left over. 

What is the fix to it ?

Regards

Herin