Your problem is probably caused by a good mix of calendars and that some of the settings are wrong before starting to entering task.
Under Format-Options-Calendar you state that a day is defined as 14 hrs, but the Estándar calendar only allows them to work 10 hrs – and the Estándar calendar is still applied to all your resources. Furthermore, you have default start time of the day set as 07.00 (also the Calendar-tab).
Now you suddenly change the project to a 24 hrs calendar, meaning that all tasks that don’t have any calendar assigned to them (=None) take upon this 24 hrs calendar, however, the Estándar-calendar is still assigned to all resources with only 10 hrs of allowable working time per day and a day defined as 14 hrs starting at 07:00 and not 00:00 when you have a 24 hrs calendar. Furthermore, all your tasks are defined as fixed units, meaning the duration will change as you change calendar and there are a SNET-constraint set to start at 07:00. All in all, you can’t almost avoid to end up with odd comma-days.
My suggestion – and as you only have 18 activities – start a new project, get the settings correct (the maths have to agree), be aware of which calendar is assigned to the task, which calendar is assigned to the resources, how a day is defined by MSP, etc.
Using a Standard Calendar as per your definition I got the following. Perhaps constraints are having a different impact on total duration depending on calendar. Hammer Rule would be handy, hit it with a hammer until it fits.
Hi Rafael Thanks but if you saw my project file the problem isnt the 24 hours calendar...cause i did it that you say me...but the wrong duration still in my project.
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.
Orozco,
Your problem is probably caused by a good mix of calendars and that some of the settings are wrong before starting to entering task.
Under Format-Options-Calendar you state that a day is defined as 14 hrs, but the Estándar calendar only allows them to work 10 hrs – and the Estándar calendar is still applied to all your resources. Furthermore, you have default start time of the day set as 07.00 (also the Calendar-tab).
Now you suddenly change the project to a 24 hrs calendar, meaning that all tasks that don’t have any calendar assigned to them (=None) take upon this 24 hrs calendar, however, the Estándar-calendar is still assigned to all resources with only 10 hrs of allowable working time per day and a day defined as 14 hrs starting at 07:00 and not 00:00 when you have a 24 hrs calendar. Furthermore, all your tasks are defined as fixed units, meaning the duration will change as you change calendar and there are a SNET-constraint set to start at 07:00. All in all, you can’t almost avoid to end up with odd comma-days.
My suggestion – and as you only have 18 activities – start a new project, get the settings correct (the maths have to agree), be aware of which calendar is assigned to the task, which calendar is assigned to the resources, how a day is defined by MSP, etc.
Regards,
Bo
Are you getting this? About 25.42 days?


Using a Standard Calendar as per your definition I got the following. Perhaps constraints are having a different impact on total duration depending on calendar. Hammer Rule would be handy, hit it with a hammer until it fits.
Best Regards,
Rafael
Hi Rafael Thanks but if you saw my project file the problem isnt the 24 hours calendar...cause i did it that you say me...but the wrong duration still in my project.
Orozco,
If you wan to use a 24hr calendar define work hours/days/month as follows.
Go to Tools/Change Working Time/Options and make;
Hours per day = 24.00
Hours per week = 168.00
Days per month = 30.00
Best regards.
Rafael