I dont understand why it shouldnt work. this is the explanation.
1 day is calculated as 8 hours per day depending on what you assigned in the hours per day. elapsed days has 24 hours(3 days as calculated using 8 hours per day), thats why in a critical path, task with elapsed days will have around 2 days slack always(about 16 hours). It sounds weird, but thats how MSP is calculating the slack. Try it with only 4 tasks, you will see what I mean.
Or maybe youre right. Its possible they havent addressed this issue for MSP 2002.
Difficult question as I don’t know how many tasks you have that are ‘elapsed’
I have had a similar problems in the past and kept coming across this glitch, so I don’t use edays anymore.
If I know that I’m going to have to use elapsed time in a schedule, then I create a copy of the Standard Calendar and call it something like Elapsed Calendar, remove all the public holidays and make all the weekends non-default working time.
Then using the Gantt Chart view I insert the Task Calendar column and every task that would have had to use edays, I change the calendar from None to Elapsed Calendar and use normal duration to get the correct Start / Finish dates.
Because it uses a copy of the Standard Calendar and the working times are now 0900 – 1700, then the new created elapsed tasks should show as critical.
Hopefully this makes sense and you can use this method too.
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.
I dont understand why it shouldnt work. this is the explanation.
1 day is calculated as 8 hours per day depending on what you assigned in the hours per day. elapsed days has 24 hours(3 days as calculated using 8 hours per day), thats why in a critical path, task with elapsed days will have around 2 days slack always(about 16 hours). It sounds weird, but thats how MSP is calculating the slack. Try it with only 4 tasks, you will see what I mean.
Or maybe youre right. Its possible they havent addressed this issue for MSP 2002.
yes, with 3 days too, but my tasks with elapsed durations are still not critical.
I think it is a bug in MSP-2002, a friend has tried on MSP-2007 and it seams to work.
have you tried it?
any change with 2 days.
Hi Bertrand,
Try 2 days for your slack threshold. Well discuss later why it should be 2 days not 1 day.
I hope this helps.
Se
Hi Bertrand
Difficult question as I don’t know how many tasks you have that are ‘elapsed’
I have had a similar problems in the past and kept coming across this glitch, so I don’t use edays anymore.
If I know that I’m going to have to use elapsed time in a schedule, then I create a copy of the Standard Calendar and call it something like Elapsed Calendar, remove all the public holidays and make all the weekends non-default working time.
Then using the Gantt Chart view I insert the Task Calendar column and every task that would have had to use edays, I change the calendar from None to Elapsed Calendar and use normal duration to get the correct Start / Finish dates.
Because it uses a copy of the Standard Calendar and the working times are now 0900 – 1700, then the new created elapsed tasks should show as critical.
Hopefully this makes sense and you can use this method too.
Regards,
Darren
Hi Darren,
You are right.
Task1 (days) Start 8:00 Finish 17:00 Critical
Task2 (edays) Start 17:00 Finish 17:00 No Critical
Task3 (days) Start 8:00 Finish 17:00 Critical
What can I do ? I have lots of elapsed duration.
In Tools>Options>Calculation I use "Tasks are critical if slack is less than or equal to 1 days". But seams doesnt work.
Hi Bertrand
It probably has to do with edays using a 24hr calendar and your normal tasks using a standard calendar.
As a simple example, if you have 3 tasks with the 2nd task using elapsed duration.
The 1st task will start at 0900 and finish at 1700 as per the standard calendar.
The 2nd task will start at 1700 and finish at 1700 but on a different calendar.
The 3nd Task will then start at 0900 but back on the standard calendar, so MS Project thinks there is float and hence it won’t show critical.
I believe this is what you’re experiencing, but it’s easier to see if you have time showing on your Start and Finish columns.
Have a look Tools > Options > View and then change the date format to include time.
Regards,
Darren