Resourcing on a 24hr Calendar

Hi Aaron,

Simple questions first.

What TIME does your Task start (Tools > Options > View > Date format Ddd dd/mm/yyyy hh:mm)

and

Are ALL of your calendars in sync?

Regards,

Darren Kosa

Make sure DD and project start are set to start at 00:00 hours. I believe this is Darren suggestion but in other words.

If the above does not solve the issue then, maybe when you first created the resource the active calendar was a calendar starting at 8:00 AM and then you changed the resource calendar to a 24 hour calendar. There is a possibility that resource availability was set to start at 8:00 AM on that day. The resource was scheduled to work 16 hours out of 24 hours this day and 8 out of 24 on last day, while 24 out of 24 on intermediate days. Check on the resource definition table to make sure availability starts at 00:00 hours.

Yep, I picked up my problem shortly after I posted about it. While my calendars were synced and correct and the working time was correct tasks were begginning at 8am due to an earlier constraint keeping everything out eight hours.

Then right answer, "none of the above" is no surprise to me.

I believe MSP 2010 has an option to set any or all of your activities to auto-schedule, this can solve the issue on constraints placed by the software but not by the user, this is how MSP works. This new functionality should be your default setting, can protect you from other surprises.

Rafael,

Maybe a bit off-topic, but the auto-schedule option in MSP 2010 is identical to the regular task behavior under the scheduling setting "Calculation mode: Automatic" in MSP 200x.

The manual-schedule task setting is a different thing altogether. It allows you set specific lines to "Calculate mode: Manual" which is interesting (to say the least) because it will then for instance: ignore schedule logic, allow you to enter "about a month" as duration, or "end of September" as start date. (it will also allow "when pigs fly" by the way)

Microsoft is selling this as "User Controlled Scheduling" but from what I've tested so far it gives me the creeps. For instance, I've played around with summary tasks on manual and the underlying tasks to automatic. This has profound implications on the critical path, and any 'old school' definition of a critical path and total float will go out of the window.

When time permits, I will start a new topic with my observations so far, because I'm really interested what other schedulers have found.

Niek.

Niek,

I do not have MSP but frequently import MSP files. I used it before and believe there is more than what you said, go for the new topic. I am sure others that have MSP will join.

Rafael