Resource loaded schedule has decimals in the Total Slack.

[Jim]

Resource loaded schedule (using Project Server, MSP 2013) has decimals in the Total Slack column even though none of the duration’s have decimals. How do I remove the decimals in the Total Slack?
Particulars:
-Time is entered in hours
-Type is Fixed Work
-Summary “Type” is default “Fixed Duration”
-Even after the logic is removed from a milestone the Total Slack has decimals but when a dummy milestone is added after the current latest date in the schedule the decimals go away from anything without logic. However, if I zero duration the latest existing activity it doesn’t remove the decimals from unconnected milestones.
-We added a resource that wasn’t in the Pool in the Server Resource Pool and that activity went decimal so we removed her and that removed that associated decimal in the Total Slack but other Total Slack decimals related to other activities/milestones remained
-The project calendar is five days with holidays
-All are on the default calendar
-We Leveled the Resources and it had no effect on the decimals
-Could a resource have an individual calendar that impacts the project calendar even if it isn’t listed?

We’ve done a lot of trouble shooting and we think the problem is associated with the Resources but need some help.

[Larry Christofaro]

Jim, I don’t have an answer to your issue, but one response is that every resource has a resource calendar. It shouldn’t make a difference in slack but wanted to respond to your last comment (and get notified in case someone else responds). Good luck and hope you get an answer.

[Thomas Boyle]

Hi Jim,
It’s also not obvious to me what’s going on in your project, nor what troubleshooting you may have done already, but here are some comments that may (or may not) help you.
– The third bullet of your post implies that the current last task in your schedule (but not the schedule overall) has an imposed constraint whose time of day is slightly offset from the default calendar. This can happen when you change the calendar (and associated default start/finish times) after imposing the constraint. The constraint could be an explicitly defined SNLT, FNLT, or Deadline on the last task. It could also be inherited from any summary tasks above it. Be alert to Manually Scheduled tasks that may have crept into the schedule. They can have the same impact as explicit constraints and can be well hidden especially as summary tasks.
– Suggest that your date format (in General Options) should be one that shows complete time of day in hh:mm. Since you’ve said, “Time is entered in hours,” I would expect this to already be the case. I would also expect that your decimals in Total Slack are referring to partial hours rather than partial days, not that this makes any difference.
– Total Slack is strictly a Task property, reflecting task early dates, late dates, and assignment/leveling delays (if any). While your resource calendars can certainly affect these, the first step in troubleshooting your unexpected Slack values is to examine the late dates of your tasks from last to first looking for deviations from your expected time. I first typically look at Late Finish.

[Author]

Posts