Specifically, version 7.0 of PPM automates portfolio optimization, adds the ability to standardize project health indicators across multiple instances, and provides new capabilities to oversee project initiatives from top down or bottom up.
At first glance, the portfolio optimization capability doesn’t appear to be anything new, as this is what PPM systems were designed to do. But in previous versions of the Mercury offering, optimizing the project mix by targets (such as having the right mix of high, medium, and low risk projects) based on budget and resource constraints was largely a manual process. The new release introduces some algorithms that automate the balance of supply and demand.
Another new feature automates the detail of Work Breakdown Structures (WBS) down to task level, providing the ability to manage top down or bottom up. That means you can allocate resources across individual tasks (juggling parallel and sequential tasks) or across projects (juggling resources between projects).
The new version also provides the ability to standardize project health indicators across multiple organizations, and multiple sub-instances of the PPM system. It is accomplished through a policy engine that can rollout out thresholds for project key performance indicators, so all projects (or groups of projects) are tracked by the same metrics.
Also added is a native plug-in to Microsoft Project. Previously, tie-ins with Microsoft Project were through an import and export process. However, with the new release, which has changed the web client from Java applets to Ajax, enables the PPM systems to provide more native integration.
An architectural change is that the Java applet web client has been replaced with Ajax. That eliminated some platform barriers, enabling more direct integration with Microsoft Project. Previously, you could export project plan changes to Microsoft Project and vice versa. The new Ajax front end enables the PPM system to operate as, in effect, a web-based plug-in to Microsoft Project.
The result is a slightly smoother workflow between PPM and Microsoft Project. Typically, when you change a project resource allocation and export it to Microsoft Project, the Microsoft system will often juggle project plans in response. The new link, within the same screen, lets you more effectively synchronize updates between both systems.
As this is the first PPM release since HP’s acquisition of Mercury closed last month, the release had a few rough edges. For instance, while HP said it would phase out the Mercury name, the press release titled the new release Mercury Project and Portfolio Management Center 7.0.
At any rate, HP promises a product roadmap for the acquired Mercury products by mid December. Version 7.0 of PPM is available now.
