Keir,
From what I understand you have a requirement to change the calendar on certian activities????

This being the case you can use the global change to do this.

If the issue is the change in durations, dates and float, then I’m afraid this will happen, nothing you can do except manage each activity on it’s own.

If you can provide more detail as to what you are doing then we could guide you better.

Andy

Keir,
This is an expected outcome of doing what you did.
The dates are different as the schedule would be about 3 times longer in duration and the individual floats, (If you can beleive Primavera at all - but that’s a different subject) would have changed as a result of the individual activities now being 3 times as long and the non linear relationship between the new durations and the new critical path.

This is my point when these calendars are concerned, that you can’t just change them for fun or without reason as the way this tool (P5) calculates it will mess with your head when you try to analyse it.

Andy

Keir,
This is the standard Modus Operandi of Primavera.

As Imran has said the admin user preferences can be set to allow each user to set their own ‘units per time period’.

From what I’ve witnessed over the last few months Primavera has dropped the ball here with these settings along with the issues surrounding the ‘Default’ global calendar selection.

The default calendar is used by Primavera to schedule the default or user selected ‘hours per time period’ in line with the selected activity calendar.

Note – As Primavera schedules in hours this is the point where the user gets confused with the activity Vs summary durations. This is because the summary durations are calculated by using the ‘Units per time period’ scheduled against the default calendar and not the activity calendar.

Now – If you set the user preference to allow the user to set the ‘units per time period’ themselves, you can get a third answer from the same project at both the summary and activity durations.

Currently my database administrator or people with the privilege to change the default calendar, do so at will dependant on the project within the EPS that they are working on so they can use the default calendar for each new activity that they create. Even though, each project has a default calendar for new activity setting. IMHO the project level setting for the default calendar ‘Units per time period’ should be locked to that project and each user of that project should be constrained to use that figure.

The project level default calendar figure for ‘Units per time period’ should be set to the planned expenditure of effort for that project either based on full work hours per day or a utilisation factor per day, then if other calendars are selected at various activities to allow schedule compression or for specific constraints on that activity, the durations will be correctly compressed based on the new daily or weekly cycle.

If you look at this forum thread Calculation Of Activity Duration ??????????????? you will find that the issue is quite interesting

So there you have it

Andy