For Microsoft and Primavera
I have to tell you how much analyzer has helped me. I have cut my analysis time by 80%. I let Steelray Project Analyzer do it for me. My engineering group loves the Excel output.
Steelray Project Analyzer was developed with the end user in mind. I have been using this tool for a few years now and have been impressed with its ease of use and robust functionality. Project Analyzer has matured with technology by adapting to the latest versions of the products it supports. Additionally, the professional manner in which their customer support staff works with the user is top notch.
Analyzer is well thought out like they had been in my arena for the past 10 years. They really knew what issues the end user would have.
Large projects require complex schedules that affect the plans of many people—not just project resources, but finance, management and a host of interdependent departments and entities.
It’s critically important that the schedule be as accurate as possible so companies can save effort, reduce budget and enable teams to deliver on time.
Unfortunately, complex schedules in complicated scheduling software (like Microsoft Project and Primavera) are prone to errors in the critical path. This makes it difficult to trust the forecast—which undermines confidence in the program.
As the first and most powerful commercial software application in the “schedule quality” space, Steelray Project Analyzer (Analyzer, for short) continues to set the standard as the best solution to uncover issues in—and improve the accuracy of—the critical path. Here’s why:
Steelray Project Analyzer is software that takes the pain out of creating, maintaining and delivering quality schedules. With Analyzer, you can evaluate your project schedule for quality and performance in minutes and produce understandable results. Schedules can be analyzed against project management best practices, internally defined best practices and government best practices.
Analyzer supports Microsoft Project .mpp files, Project Server, Primavera P6 and UN/CEFACT XML.
Scheduling software makes it relatively easy to create schedules and calculate a critical path, but it doesn’t do much to prevent common mistakes that result in an incorrect critical path.
Based on the thousands of schedules we’ve seen in the past 15 years, we can say with certainty that almost every medium-to-large schedule contains serious mistakes, including:
Think about it: the purpose of scheduling software is to produce a good critical path, and almost all medium-to-large schedules contain mistakes that make the critical path incorrect.
Suppose a company brought you in to consult on a large project they were launching. On your first day, they give you project schedule with a finish date of December 15th that year. You load the schedule into Analyzer, run a scorecard report, and Analyzer flags six crucial problems with the schedule.
So you meet with the scheduler and stakeholders, modify the schedule and run it through Analyzer again. Now there are no longer any problems, but the finish date is February 15th, two months later than the original forecast!
The impact? You now have valuable, up-front information about the truth of the schedule—and can do something about it—several months before misinformation would have lead to the headaches of time and cost overruns.