Curt C
Project has three types of calendars, project calendar (Project > Properties group > Project Information > Calendar), task calendars (Task Calendar field on Gantt Chart view), and resource base calendars (Base Calendar field on Resource Sheet).
The project calendar drives everything unless, a task requires specific work days and/or times that differ from the project calendar. A "none" entry in the Task Calendar field indicates that task follows the project calendar. It is best to first set up the project calendar with all common non-working periods (e.g. holidays and work hours). Deviations from that for specific tasks and/or resources are set in custom calendars for those objects.
The Base Calendar field on the Resource Sheet indicates which calendar that resource follows. A resource's calendar will "trump" a task's calendar unless the option "scheduling ignores resource calendars" (Task Information > Advanced tab > Calendar). A resource's calendar will also "trump" the project calendar.
Custom project or task calendars are created via Project > Change working time. As good practice, the Standard, or any other built-in calendar, should NOT be directly modified, rather, a custom calendar, (perhaps based on a built-in calendar), should be given it's own name. Custom task based calendars (project or task calendars) will show up on the Calendars tab in the Organizer.
Resource calendars are created via Resource Information > Change Working time. Resource based calendars do NOT appear on the Calendars tab in the Organizer.
Although Project allows multiple calendars only one can be used as the project calendar. If the plan consists of multiple work shifts across tasks the project calendar should be set to encompass the full work days and times of all custom calendars. This is often done by using the built-in 24 hour calendar as the project calendar.
Project only allows one definition for a "day" (and hours per week and days per month) and that definition is used to calculate the the value in the Duration field and custom Duration fields (i.e Duration1 thru Duration10). The units displayed in the duration field can be in minutes, hours, weeks, and/or months either as working time (default) or calendar time (elapsed time). The default units for the Duration field is set via File > Options > Schedule group. That option applies only to new tasks, it will not "reset" any previously entered duration values.
For reference, Project calculates all time periods to the nearest minute regardless of what unit is selected for duration.
Hopefully that covers a whole lot of questions you might have and clarifies things.
Now a few comments on the screen shots you posted in response to Trevor.
- It looks like you have directly modified by the Standard and 24 hour built-in calendars. I suggest you rethink that approach. For common non-working time (e.g. holidays) create a custom calendar perhaps based on the Standard or 24 Hour but with it's own calendar name (e.g. XYZ Construction). Make that your project calendar. Then create and apply separate task calendars ONLY if the task requires different work days/hours. The same for resources.
- You have a custom "Concrete Curing" calendar. I can't in any scenario imagine why a calendar would be created for curing concrete. Concrete curing is not a "scheduled" activity. Curing is the result of a concrete pour and is best defined as a delay after the pour or 7, 14 or 28 days depending on the successor task (e.g. 46 + 3ed), meaning 3 elapsed days after the pour for column 01. As an alternate you can show the cure as a separate task (as you have shown) but with an elapsed duration and no custom calendar.
- You say you have multiple task and/or resource calendars. Too many or unnecessary custom calendars can drive you nuts. Using what I explained above, take a hard look at what you have and what you need and make adjustments where necessary
John