HP PPM Version 9.22: Additions to the Application Portfolio Management Module

We have finally arrived at our last entry of the PPM 9.22 blog series.  So far on our journey, we have explored usability enhancements made to the resource management module, improvements to the PPM – ALM integration and how additions to the PPM Center – Agile Manager relationship provided users with a simpler way to import agile effort.  Today, we conclude our series by examining the changes made to the Application Portfolio Management (APM) module in HP PPM. 

To recap, HP Project and Portfolio Management (PPM) Center provides users with visibility into strategic and operational demand, as well as ongoing projects across your organization.  It provides an integrated platform that easily manages and organizes all projects within your portfolio.  With the addition of HP Application Portfolio Management (APM) module, detailed application assessment and current state data is fed into the center, while project and program management capabilities provide real time visibility into the project lifecycle at all levels.  In the end, the result of the co-existence of these two easily integrated HP products is that you can improve project success rates and shrink or modernize your application portfolio.  

In our latest version, 9.22, the HP PPM team has added two new capabilities that have enhanced the APM module. 

Integrating HP Application Portfolio Management (APM) with HP Universal CMDB (UCMDB): 

  • The integration between HP APM and HP Universal CMDB enables users to share information from UCMDB with HP APM.  Users can utilize the integration to automatically create and update applications in APM, which frees users from repetitive and manual input of information into HP APM.   This will ensure that APM is kept up to date with real, accurate, discovered data in your environment.
  • Since data from the UCMDB and data from HP APM is defined in different data models, it’s important to distinguish the two.  Data from the UCMDB is a Configuration Item or CI, while data from HP APM is in the form of an application.  To retrieve data from the Universal CMDB, the data must first be retrieved via TQL query by the push engine in UCMDB.  It is then pushed to the integration service where the data will be converted by the push adapter from CIs into application data.  Finally, the REST APIs will transfer the converted data into HP APM’s own database.

Below is a graphic showing the entire integration process:

 

APM 1.png

 

Roadmap Entity Added to HP APM: 

  • Roadmap has been introduced to HP APM in the newest version of PPM.  This new entity is a roadmap for an individual application or service, or a group of them, and includes lifecycle statuses (roadmap phases) and milestones.  Users can create a roadmap entity for any other existing APM entity.
  • When users create, serach or edita  roapmap, information in the following three sections needs to be entered or updated:
  • Identity: Information in the identity section helps identify the roadmap of interest.
  • Phases: Information in the phases section helps dictate the phases the roadmap will go through. 
  • Milestones: Information in the milestones section helps users set milestones for each roadmap.

Below is a figure which illustrates the workflow step of a default roadmap:APM 2.png

 

If you are interested in a more detailed look at our additions to our ALM module, please view our release notes here. For all things HP PPM, please visit hp.com/go/ppm 

Resource: HP

Article source: HP PPM Blog

Leave a Reply

Skip to toolbar