When an activity has "None" in the field/cell for calendar it just means that no calendar has been assigned to the activity and as default value takes the project calendar. "None" is therefore not a calendar, neither does it mean "Standard", but merely a reference to the calendar chosen to be the project calendar by the "planner".
Microsoft should maybe more logically have selected another word than "None", likewise they should have let the default calendar for resources to be the "none" instead of the "Standard" calendar, so calendars for the task and the resource where the same in those instances where people hadn't given the calendars any thoughts (and there are many of those people out there...)
I've just tried to make an actual calendar named "None" only allowing it to work Mondays (1 day pr. week) and assigning it to a task. However MSP couldn't handle that - it still used the default project calendar (working 5 days a week). Therefore, lesson learned: Never name a user-made calendar "None" in MSP.
When the activity Calendar is defined as "None", MSP is using the calendar you have defined as "Calendar" under "Project Information". For many users this will be the "Standard"-calendar (e.g. for those who just open a new file and start to plan without giving calendars any attention), however not for those users who have chosen another calendar to the be project calendar. That chosen project calendar will then be the "None"-calendar.
Be aware that for some strange reason resources are always using the "Standard"-calendar as their base calendar if nothing else applied, not the project calendar, meaning one can get into a bit of problems when the project calendar is another than the "Standard".
Therefore, always be in total control of all your calendars before starting to plan and do not assume that MSP will do the most logical.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
Hi Bo
Thanks for the information - another good reason to avoid MSP.
You are quite correct that planners do not understand the significance of different calendars - particularly in respect of resources.
In PowerProject there is a tick box in the resource dialogue which says "Use Task Calendar" which keeps it very simple.
I once put together a complete EoT delay analysis and Acceleration claim using nothing but different calendars on the baseline.
Best regards
Mike Testro
Mike,
When an activity has "None" in the field/cell for calendar it just means that no calendar has been assigned to the activity and as default value takes the project calendar. "None" is therefore not a calendar, neither does it mean "Standard", but merely a reference to the calendar chosen to be the project calendar by the "planner".
Microsoft should maybe more logically have selected another word than "None", likewise they should have let the default calendar for resources to be the "none" instead of the "Standard" calendar, so calendars for the task and the resource where the same in those instances where people hadn't given the calendars any thoughts (and there are many of those people out there...)
I've just tried to make an actual calendar named "None" only allowing it to work Mondays (1 day pr. week) and assigning it to a task. However MSP couldn't handle that - it still used the default project calendar (working 5 days a week). Therefore, lesson learned: Never name a user-made calendar "None" in MSP.
Regards,
Bo
Bo Johnsen,
Thank you verry mutch for your help.
Regards.
Hi Bo
Surely a "None" calendar means a 24/7 construction period with no work pattern or holidays.
At least that is what it is in all other software I have used.
I don't use MSP so I would not be surprised to learn that None means Standard in their strange environment.
Best regards
Mike Testro
Ahmed,
When the activity Calendar is defined as "None", MSP is using the calendar you have defined as "Calendar" under "Project Information". For many users this will be the "Standard"-calendar (e.g. for those who just open a new file and start to plan without giving calendars any attention), however not for those users who have chosen another calendar to the be project calendar. That chosen project calendar will then be the "None"-calendar.
Be aware that for some strange reason resources are always using the "Standard"-calendar as their base calendar if nothing else applied, not the project calendar, meaning one can get into a bit of problems when the project calendar is another than the "Standard".
Therefore, always be in total control of all your calendars before starting to plan and do not assume that MSP will do the most logical.
Regards,
Bo