I have often been asked what is BSM? In 10 words or less, it is "Complexity presented Simply - Aligned with Business". Let's explore that in a bit more detail. We all have complex webs of distributed and mixed environments of infrastructure and have likely set priority of an incident reactively based upon who, how many and how fast the phone rings all due to not knowing what services the technology supports to the business.
You had a view of the symptoms that something is going awry ahead of an incident
You averted that incident by taking action to redirect
You knew not just severity, but also priority of events based upon business rules
You knew risk of making a change to a component prior to a change
You knew the business priority of a service and all the supporting components
You monitored service performance based upon technology availability
and value / volume of the business being transacted through the service
Now imagine that all of this is in a single, graphical view - that is Business Service Management. Managing the technology in alignment with objectives of the business.
The ability to triagulate bits of data together in a meaningful view by which to assess and take action in real time, whether it be managing the health of a service or the supporting configuration of the service, is what the Novell Business Service Management solution brings to many customers today across the globe.
Welcome to our blog, we'll continue this dialog and take the conversation deeper! Drop us a note and send us your thoughts and questions you would like to hear about too.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.