09-28-2010, 10:58 AM
June 15, 2010
At HP Software & Solutions we have decided to release the next versions of our BTO Operations products with the version number 9. This decision reflects our commitment to better aligning our BTO Operations product releases over the coming years. Our strategy is to manage BTO Operations product releases as a whole, aligning them around timing and common requirements, such as platform support.
Alignment on common requirements will occur in several stages. This year we focused on the Business Service Management (BSM) suite, which includes HP Network Node Manager, HP Operations Manager, and HP Business Availability Center, offering deep integration and unprecedented usage of common technology. For other products, such as HP Service Manager, we continued their integration and platform support plans, strengthening their integration with HP uCMDB and other HP Software products.
To minimize the impact of this new strategy on our customers, we have decided not to align all BTO Operations products to 9.0 major releases. Some releases will be minor ones. You can easily differentiate between a major release and a minor release. If the version number for a release is 9.0, it is the most recent major release. If the version number is anything else, such as 9.10 or 9.20, it is a minor release.
For example, the latest release of Service Manager is 9.20. This is a minor release. The latest release of Operations Manager is 9.0. This is a major version.
Releasing a major version for the entire BTO Operations product portfolio would not have made sense. A few products recently released major versions and are not planning another major release anytime soon. Moving forward, our aim is to release a major version for all BTO Operations products at the same time, with as few exceptions as possible.
Are there exceptions to this new release renaming?
Yes, for those products that are being discontinued, such as HP Service Desk, and for first versions of brand-new products.
Are HP Software & Solution’s policies for versioning and obsolescence changing?
No. We did not alter the HP Software & Solutions versioning and obsolescence policies.
What will be the release policy for BTO Operations products going forward?
Our goal is to align major releases of BTO Operations products on a regular basis. This release alignment will focus on timing, shared technology, supported platforms, integrations, and coexistence. Some groups of products will also be aligned on minor releases.
What are the customer benefits of HP Software & Solution’s new BTO Operations product release train strategy?
Customers will benefit from a consistent set of product releases occurring at the same time. These product releases will feature shared technology, common platforms, integrations, solutions, upgrade tools, and professional services offerings.
At HP Software & Solutions we have decided to release the next versions of our BTO Operations products with the version number 9. This decision reflects our commitment to better aligning our BTO Operations product releases over the coming years. Our strategy is to manage BTO Operations product releases as a whole, aligning them around timing and common requirements, such as platform support.
Alignment on common requirements will occur in several stages. This year we focused on the Business Service Management (BSM) suite, which includes HP Network Node Manager, HP Operations Manager, and HP Business Availability Center, offering deep integration and unprecedented usage of common technology. For other products, such as HP Service Manager, we continued their integration and platform support plans, strengthening their integration with HP uCMDB and other HP Software products.
To minimize the impact of this new strategy on our customers, we have decided not to align all BTO Operations products to 9.0 major releases. Some releases will be minor ones. You can easily differentiate between a major release and a minor release. If the version number for a release is 9.0, it is the most recent major release. If the version number is anything else, such as 9.10 or 9.20, it is a minor release.
For example, the latest release of Service Manager is 9.20. This is a minor release. The latest release of Operations Manager is 9.0. This is a major version.
Releasing a major version for the entire BTO Operations product portfolio would not have made sense. A few products recently released major versions and are not planning another major release anytime soon. Moving forward, our aim is to release a major version for all BTO Operations products at the same time, with as few exceptions as possible.
Are there exceptions to this new release renaming?
Yes, for those products that are being discontinued, such as HP Service Desk, and for first versions of brand-new products.
Are HP Software & Solution’s policies for versioning and obsolescence changing?
No. We did not alter the HP Software & Solutions versioning and obsolescence policies.
What will be the release policy for BTO Operations products going forward?
Our goal is to align major releases of BTO Operations products on a regular basis. This release alignment will focus on timing, shared technology, supported platforms, integrations, and coexistence. Some groups of products will also be aligned on minor releases.
What are the customer benefits of HP Software & Solution’s new BTO Operations product release train strategy?
Customers will benefit from a consistent set of product releases occurring at the same time. These product releases will feature shared technology, common platforms, integrations, solutions, upgrade tools, and professional services offerings.