Professional Documents
Culture Documents
Product versions
When we refer to HP Service Manager or BMC Remedy in this paper, we mean the current versions of the respective products. As of
the writing of this document, unless otherwise specified, we’re referring to HP Service Manager version 7.11 and BMC Remedy IT
Service Management Suite version 7.5.
The company’s mantra was “minimal tailor- • Difficulty finding qualified resources for
ing” and it strongly encouraged its customers maintaining modified Remedy installations,
to try and use the product first, without any which resulted in higher costs, upgrade chal-
customizations, to see if changes were really lenges, and a delay in deploying important
needed. HP (Peregrine) even locked down cer- new capabilities
tain areas of the product so these areas could Of course, these disadvantages were also appar-
not be customized to “enable bad behavior.” ent with the HP/Peregrine product. It didn’t
These diverse approaches to service desk cus- eliminate customization, and many HP/
tomization continued for several years. Not Peregrine customers ran into the same problems
surprisingly, the end result was that Remedy as Remedy customers. Conversely, many
implementations had a dramatically higher Remedy customers kept their implementations
number of customizations. And, it became very clean and did not encounter any of these
clear that there were disadvantages to these issues. Without a doubt, the products fundamen-
customizations, including: tally supported a certain kind of approach—
most Remedy implementations were very heavily
• Longer deployment cycles to implement the
customized and most HP/Peregrine implemen
customizations
tations were only slightly customized.
• Additional expenses for development
resources to implement customizations More recently, BMC has taken a very different
• Increased costs required for the ongoing stance on customization. Following HP’s
maintenance and support for the approach, BMC’s recommendation now is to
customizations use the out-of-the-box functionality as much
• Product “lock-in”—the more customization, as possible and to limit customization. In some
the more difficult it is to upgrade to a newer cases BMC has actually locked down its code
version of the product, and many customers so that functionality that was configurable in
ended up using out-of-date software the past is no longer available. The partici-
pants in our study felt that the latest version
of Remedy locks too many fields and configu-
Configuration v
ersus customization ration options. As a result, what should be a
Configuration is different than customization. One example simple configuration now requires organiza-
of configuration is making basic changes to the names of tions to either customize or live with the
existing fields. In both HP Service Manager and BMC unsuitable workflows that are pre-built in the
Remedy, configuration is relatively straightforward with no Remedy product.
obvious difference in the long-term cost of ownership. It is important to note that HP has also reduced
Customization is making changes to the product. The most the ability to customize by eliminating access
typical type of customization in an ITSM product is to add to the Rapid Application Development (RAD)
a new field or to make a change to a workflow. It is these environment that was previously available to
types of customizations where we see a marked difference customers. Yet, participants in this study felt
in the cost of ownership between HP Service Manager and that this change has not been as severe and
BMC Remedy. has not resulted in the same negative impact
to customers.
Recommendation:
When purchasing an ITSM product, make sure references use
the current version of the product and get their feedback on
the costs of customization and integration.