Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

MSP: Elapsed total float ignored - even when increasing threshold for critical tasks

3 replies [Last post]
Fri, 2018-08-17 09:51
Henrik I
User offline. Last seen 5 years 35 weeks ago. Offline
Joined: 17 Aug 2018
Posts: 4
Groups: None

Please see attached. What is going on here? Bug?

5920
msp.png

Many thanks 
Kind regards,
Henrik

Top

Replies

Mon, 2018-08-20 13:35
#1
Tom Boyle
User offline. Last seen 4 weeks 5 days ago. Offline
Joined: 28 Nov 2006
Posts: 304
Groups: None

Henrik, glad you got it sorted.

Top
Sat, 2018-08-18 17:59
#2
Henrik I
User offline. Last seen 5 years 35 weeks ago. Offline
Joined: 17 Aug 2018
Posts: 4
Groups: None

Many thanks Tom! Brilliant :-)
I should have thought of that.

Top
Fri, 2018-08-17 16:28
#3
Tom Boyle
User offline. Last seen 4 weeks 5 days ago. Offline
Joined: 28 Nov 2006
Posts: 304
Groups: None

No bugs.

  1. Assuming you've left the project's "hours per day" at the default value of 8, then your critical slack threshold of 6 days is 6x8=48 hours.
  2. On the two tasks selected, the Total Slack is 2.63 elapsed days x 24 hours per elapsed day = 63.12 hours.
  3. Since 63.12 > 48, the two tasks are not Critical.
  4. For these tasks to show as Critical, you would need to increase the critical threshold from 6 days to 8 days (i.e. 64 hours).

In this case, your true Critical Path might be difficult to discern without tracing the driving logic.

Good luck, tom 

 

 

Top