(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.
Hello all,
What are the best practices that should be considered when reviewing a P6 schedule from a contractor? Most especially when an heinous contractor (trying to manipulate) is involved.
All opinions shall be appreciated.
thanks
Bayo
Printer-friendly version
Send to friend
you can run claim digger
you can set the previous update as a baseline and compare the varainces in column
I appreciate all thoughts and suggestions.
Most important now is on how to easily spot/filter the difference in performance % btw previous and present DD.
Any idea on that???
Folahan,
While reviewing the updated schedule, the main foccus should be the critical path. Any delay on critical path will delay the project completion. You also need to check if some recovery plan has been incorporated to avoid any slippage on critical path. Contractor should be asked to submit a Modification Log with every schedule update to explain the changes and reasons of change. I recommend you to run "Schedule Comparison/claim digger" for duration, percent complete, constraints, added/deleted activities and relationships and then compare the results with Modification Log to find any missing items.
If crashing technique has been used contractor need to submit a complete plan how duration of some certain tasks can be reduced. by engaging extra resources or working extra hours???
Float Burn Index (How quickly the float is being used) of non-critical activities should also be tracked every month. Higher value of FBI will increase the likelihood of a non critical activity become critical.
Syed
Hi Syed,
Thanks for your input and sorry that I didnt lay emphasy on Updated schedule which is actually the main focus.
Adding to your list, I usually perform the ffg while reviewing updated schedules:
- Run filter to check activities with illogical start or finish dates. No start activities in a future start date; nor completed in a future finish date
- Check to see activities with broken logic
- Look out for Lags manipulations
- Comparing longest path from previous DD and the present to observe the swing
- Indepth check of progress % on major activities (I am yet to find a filter or UDF to compare previous and present percentages easily: pls share if you have an easy way)
Hoping to have inputs from other experts in the house.
Bayo.
Folahan,
Reviewing baseline schedule will be different from updated schedule. I usually run some filters to check some basic CPM requirements.
Activities without predecessor/successor--only start task should be without predecessor and Finish task/milestone should be without successor.
Constraints--- unless justified in Narrative. Only soft constraints should be allowed.
Negative floats--baseline should not have any negative float
longest path-- starting from project start task/milestone and ending at project finish task/milestone. Constraints may force to skip one or both ends.
lags/leads--Lags should not be used to delay the start of activity. Start of an activity can be delayed by using 'As late as possible' constraint or by inserting new task which will replace the lag. Negative lags shouldn't be allowed anyway.
SF relationship shold not be allowed as it produces reverese logic and need to be avoided.
check calendars are as per required working days.
Check if complete scope of work has been included.
sequence of events is in line with schedule specifications provided in contract/subcontract.
Experts, Please add if I missed something.
Syed
Email: PPadmin@planningplanet.com
Replies