(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.
Here's some quick tips on how to show near critical activities in Primavera P6 http://ow.ly/z50rY
Printer-friendly version
Send to friend
With limited resources P6 does not calculate floats correctly. So both critical and near critical activities may be wrong if to apply recommended filters.
Hi, Emily.
Information about near-critical tasks is certainly relevant, and it's good that Primavera makes it easy to get those data. But surely what's more important is near-NON-critical tasks? :-) In other words, tasks that ARE critical and therefore adding time to the project duration, but that we might be able to remove from the CP (and thus compress the project schedule) by shortening them or otherwise performing them differently?
The measurement of the amount a critical path activity needs to be shortened in order to become non-critical is of course critical path drag, and it's more important (more "critical"?) and much more costly than float. Unfortunately Primavera still doesn't compute it. If you have the ear of someone at Primavera, you might suggest to them that they start including such basic functionality. Have them contact me if they're not sure how to write the algorithm.
Fraternally in project management,
Steve the Bajan
Email: PPadmin@planningplanet.com
Replies