Critical Slack Calculation
Featured Partner
Top Posters
Zine Eddine
2 posts
Alex Lyaschenko
27 posts
mxsiegel
0 posts
Mattvtek
0 posts
Gareth Evans
3 posts
PP Admin
3, 129 posts
Rajkamal Tangirala
5 posts
Rahul Kumar
1 posts
blake333_
0 posts
Jeamiell Ostrovsky
2 posts
Our Partners
Yes you are right Vladimir, resource dependencies are just as important as precedence logic, and if you touch the levelling button in MSP, you can be sure that the task flag "critical" means next to nothing.
Assuming John knows this, he could use a formula to drive one of the custom flag fields and then use that flag to mark a Gantt bar as critical based on hourly thresholds rather than the standard days.
Im out of my territory here but I think in a one-day plant shutdown resource constraints are of lesser concern.
John,
if you created resource-constrained schedule then total slacks showed by MS Project are wrong. So it does not make sense to pay attention to these data at all (days or hours - they are wrong in any case).
I think what John is referring to is the setting under [tools] [options] [calculation]: Task are critical if slack...
I also think the answer is "No"
HTH
John,
MSP uses the same unit for the critical slack duration and the task duration; key in task duration in hours to get slack in hours on the gantt chart
Alexandre