What P6 Schedule Comparison Tool Should You Use?

[@lisajonescastronova5599]

Excellent video Michael. Thank you for the comparison of the programs. I've used P6 Schedule Comparison quite a bit in the past and you are spot-on. It's a bit tough to shape the data once you get it. Fortunately, I have access to Fuse and use it every day... all day. I can't imagine going back to anything else. I use it for schedule reviews and delay analysis. However, I would recommend to any scheduler building and maintaining schedules to use that tool, if they can. Even if you can't, run the Schedule Comparison report straight out of P6 so you know what's been changed in your schedule from version to version, or update to update.

[@PlanAcademy]

Thanks Lisa - good suggestions on building a consistent process around these tools.

[@brocksamford1546]

Hi Lisa, nice to meet you! I am the Acumen support rep for CDM. I have only met Nick and a few others from India so far.

[@michaelcraig1388]

Great summary of the various tools utilized and in the market for Schedule Comparison. Agreed on the Acumen Deltek front. It's a hard decision of which is the best suited tool. "Fit for Purpose" if you will. Key would be to be working some where when the client pays for the Acumen Fuse license. Hard to come by. Then there's the skills required to master Acumen Fuse. I watch your videos often and I'm thrilled that you are out there providing insightful and value added knowledge to the world wide planning community.

[@PlanAcademy]

Thanks for the kuddos!

[@louiscuneo5112]

Great comparison video Michael! Well done! :)

[@PlanAcademy]

Thanks Louis! 👍

[@galvanizedgnome]

I use clam digger, ron winter, and schedule comparison.

[@stephenscott3454]

Fantastic comparison. Thank you!

[@PlanAcademy]

Very welcome!

[@AhmedAli-dj9jo]

Thank you for your time Is it ok to make changes to the program updates due to out of sequence or to match site condition or mitigate delay and submit a change log with program update

[@lisajonescastronova5599]

Check your contract specifications on the updating or revision requirements. Some specs mandate updating logic in the Schedule Update process to reflect as-built logic (correcting for out-of-sequence progress). Some specs mandate logic changes are to be submitted as a schedule revision, and not in an Update. In the absence of specification language, in my opinion, it is best practice to correct the logic of out-of-sequence progress to reflect as-built logic, especially if you're using Retained Logic. Each occurrence will have to be evaluated individually and corrected appropriately. There are multiple ways to resolve the out-of-sequence progress issues and because you chose a SS relationship to fix one, does not mean that's appropriate for the next one. Document every change. Definitely document WHY the work was performed out of sequence as this could be the basis for a change order, delay mitigation, directed acceleration, conflicts, work space availability (or lack of it), etc. etc.. Document, Document, Document.

[@AhmedAli-dj9jo]

@@lisajonescastronova5599 thank you

[@AdarshThouti-us8cc]

how to compare two or more Primavera P6 projects in power bi just by switching the project id in slicers?

[@hillangtiger2277]

Love from India🇮🇳

[@PMWorkshop]

problem with viusalizer is the output the old OPRA gave better output

[@IamSunil017]

First...😅