Hello @dpraneeth, this may not solve the issue but have you asked Planview to restart Calendar Services?  If not, you may try this first and see if it changes what you see in the Staffing screen. 

Thanks @pamela.sargent. After we created custom calendars (which we are using as Resource Calendars - 40Hr/Wk and 35Hr/Wk), we did :

1. Refresh Calendar Lookup
2. Refresh ESE
3. Restart IIS

Apart from above, did you mean we have to request for restart of calendar services? We haven’t done that, as we did not come across such requirement in CSC.

@dpraneeth - this has been my practice over years of working in Planview. If we see a discrepancy in Staffing (previously RMA) then we would submit a case to Customer Care asking for Calendar Services to be restarted.  We’ve had good luck with it in the past. Can’t speak 100% if the calendar lookup will do everything that restarting the service will do.  Would be curious if you do this and if it did or did not help your issue. 

Thanks @pamela.sargent . I have now requested to do calendar service restart in sandbox. I will check how it goes after restart. Based on your experience, did you have scenario where there are different hrs/day based on the resource type (Perm/Contractor) and had differences in allocations displayed in Plan Vs Staffing screen?

@dpraneeth - I’m not sure that we always compared screens but when we noticed that the utilization percentage was calculating incorrectly in Staffing that is when we would submit the request. 

This is a shot in the dark, but one reason there could be discrepancies would be that the Permanents have holidays and that is subtracted from their availability. At least where I am, the Contractors do not get holiday time off.

We did restart of Calendar services, but that did not help. 

Below is an example where I am allocated 100% on a task, but still shown as 0.88f in Plan screen (instead of 1.0f) and I am assigned to 35 hr/week calendar:

From Resource manager perspective, that will show that I have 0.12f of availability. Planview is treating 1 FTE as 40 hrs. irrespective of the Resource Calendar. 

Similarly, if I change the display settings to days, I see the discrepancy in Plan and Staffing screen.

In Plan screen:

In Plan screen, system is always considering Work Standard Calendar(40hrs.) and hence in above screen that is showing 17.5d for Apr 2024.

In Staffing screen:

Number of days for Apr 2024 is shown as 20d. This is correct. 

Any advice on this issue would be helpful, as we want users to see consistency in terms of the allocations.

Hello @dpraneeth

Each work has its own calendar attribute at PPL, and that may be what is applied on the Plan screen. Maybe have a go and check what happens if you change this attribute?

Hi @Laurent, Yes, there is a standard work calendar (40hrs/week) that is being applied on the plan screen. However, as we have different work weeks for contractors and permanent employees, it is very confusing when the system is applying work calendar and not resource calendars.

@dpraneeth have you submitted a case to Customer Care on this yet?  The work schedule is driven off of the work calendar but how hours/utilization is spread is based on the resource calendar (as you probably know).  So if the two screens are reflecting different data and restarting calendar services did not help then this seems like a defect to me and should be brought up to Customer Care. 

@pamela.sargent Yes, we did raise this to customer care. Work schedule driven only by the work calendar and Staffing screen displaying based on the resource calendars is causing confusion to the end users (especially when allocations are displayed in days/FTE’s) as Permanents have different work hrs and contractors have different work hrs. When shown in hrs. we do not see this as an issue.

Was this resolved?  Interested to know if this was an internal or Planview wide issue?

@Agrant - it sounds like dpraneeth has decided to inform their users to not use FTE and instead use hours. I, personally, believe that this should be flagged as a defect by the Planview Portfolios team. We do not use FTE calculations so not something that I will be submitting as we do not have the issue. 

Here is an explanation of FTE logic. Hopefully this will clarify the discussion points above:

In Portfolios an FTE is a unit of measure for capacity and work and is a system wide definition of one person working full time and is based on the STANDARD calendar. So (assuming the STANDARD Calendar is set with a 8 hour day, 5 days per week) an FTE of effort is equivalent to:

• 8 hours in 1 day
• 40 hours in 1 week (5 days)
• 160, 168 or 176 hours in a month, depending on how many working days there are in the month (20, 21, 22 working days)

From a capacity point of view:

• A resource who is set up with a 35 hour per week calendar will be a 0.875 FTE of CAPACITY (= 35/40 hours)
• A resource who is set up with a 40 hour per week calendar will be a 1 FTE of CAPACITY (= 40/40 hours)
• A resource who is set up with a 45 hour per week calendar will be a 1.125 FTE of CAPACITY (= 45/40 hours)

When looking at planned work (requirements, reserves, allocations) in a slice of time, for example a daily, weekly or monthly column in the Plan screen, then the FTE value of teh effort you will see in the column depends on the slice of time (column) and the days, within that slice, that the work is planned. Let’s take the example of a 40 hour allocation across 1 week (5 days) for a resource that is using a 40 hour per week calendar:

• If you look at this in the Plan screen with DAILY columns then the effort on the days in which the work is happening will be 1 FTE per day
• If you look at this in the Plan screen with WEEKLY columns then the effort on the week in which the work is happening will be 1 FTE
• If you look at this in the Plan screen with MONTHLY columns then the effort on the week in which the work is happening will be 0.25 FTE (assuming 20 working days in the month)
• If you look at this in the Plan screen with YEARLY columns then the effort on the week in which the work is happening will be 0.023 FTE (220 working days in the year)

When assigning a resource of a different calendar to the calendar that the work is using then (using the example of work on a 40 hour a week calendar), then:

• Assigning a 35 hour a week (0.875 FTE capacity) resource will result in an allocation of 35 hours per week
• Assigning a 40 hour a week (1 FTE capacity ) resource will result in an allocation of 40 hours per week
• Assigning a 45 hour a week (1.125 FTE capacity) resource will result in an allocation of just 40 hours per week

@mlea - Thank you so much Malcolm for helping explain, in detail, how the system works.  I guess many of us assume that if the resource calendar is 35 hours that is 1 FTE for that calendar, or flawed thinking, but your logic makes sense.  Appreciate the time you take to explain to us all.