One possible workaround for your immediate problem would be to replace all lags with dummy tasks. You may then control the calendar of the dummy tasks.
It is indeed true; MS Project uses the project default calendar for lags. P3 uses the predecessor activitys calendar, and P3ec uses any calendar it wants to. Good luck!
There is a long discussion on the subject (albeit at a more general level) where it is easy to see that different scheduling packages handle multiple calendars and calendars for lag relationships very differently:
I really did not wish to disclose which systems I was using, but since you have a direct question and a specific need, I will share that in my testing, it appeared that MS Project was indeed using the default project calendar for the lag relationships irrespective of the calendars for the predecessor or successor tasks. I did not attempt to import an existing schedule into another schedule using a different default calendar, but it would appear from your post that doing so does not change the calendar for the lag activities.
You might try exporting the most basic data possible and re-importing. Perhaps you can find a medium that does not communicate the calendars for relationships.
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.
One possible workaround for your immediate problem would be to replace all lags with dummy tasks. You may then control the calendar of the dummy tasks.
Bernard Ertl
eTaskMaker Project Planning Software
It is indeed true; MS Project uses the project default calendar for lags. P3 uses the predecessor activitys calendar, and P3ec uses any calendar it wants to. Good luck!
There is a long discussion on the subject (albeit at a more general level) where it is easy to see that different scheduling packages handle multiple calendars and calendars for lag relationships very differently:
What do you expect?
I really did not wish to disclose which systems I was using, but since you have a direct question and a specific need, I will share that in my testing, it appeared that MS Project was indeed using the default project calendar for the lag relationships irrespective of the calendars for the predecessor or successor tasks. I did not attempt to import an existing schedule into another schedule using a different default calendar, but it would appear from your post that doing so does not change the calendar for the lag activities.
You might try exporting the most basic data possible and re-importing. Perhaps you can find a medium that does not communicate the calendars for relationships.
Bernard Ertl
eTaskMaker Project Planning Software