One other thought that might be a simpler alternative than creating and maintaining a slew of custom calendars. We have a couple thousand resources in our organization that are scheduled to projects. About 10-15% of them have custom work schedules that equate to less than 40 hours per week with varying days on/off. Rather than trying to come up with lots of custom calendars, we decided to focus on the total work each resource can complete each week regardless of the days the work is actually performed. With this approach, we have ONE standard M-F 40 hour company calendar and we control how many productive hours we expect from each resource each week by setting their Max Units value. For examples:
* An in-house full time resource (40 hours per week) is considered to be available 85% for project work(company standard), so those resources have a Max Units of 85%. 85% of their enterprise level 40 hours means we can count on 34 hours of project work per week from a full time resource.
* For a 20 hour per week resource, the Max Units value is 42% (85% of 20 hours per week =17 hours / 40 =42%). Note that we don’t care what days the work gets done within the week. We just know we’ll get 17 hours from that person each week.
* For a full time contractor resource the Max Units value is left at 100%. They aren’t give the 15% deduction for non-project meetings and such so they stay at 100%.
This approach works quite nicely and it’s completely controlled through our AD Sync process driven by our HR system. The HR system tracks the resources relationship to a full time resource based on a factor of 1. 1 = full time 40 hours per week. .5 = 20 hour per week person and so on. By building this Max Units calculation into the AD Sync process any HR hours per week changes automatically adjust the resource’s Max Units accordingly.