Over the years, IT systems management has evolved dramatically. What started as monitoring just the network infrastructure via ping/telnet/SNMP has transformed into monitoring and managing multi-tier, geographically distributed IT infrastructures and applications deployed on physical and virtual environments as well as private, public and hybrid cloud environments.
Around a decade ago, Application Performance Management (APM) emerged as an independent category within systems management. APM enables one to measure and eventually ensure availability, response time, and integrity of critical application services used by the business, i.e., the consumers of the IT application services. A couple of years later, another IT management technology called Business Service Management (BSM) emerged to align IT with business objectives.
Now, interest in BSM is resurging as companies strive to make their IT departments more responsive to their business needs. Simultaneously, APM has also emerged stronger in the last few years to encompass a broader scope in IT management. This two-article series looks at the evolution of BSM and APM, the key drivers for both technologies, and how we're seeing them converge to fulfill the promise of aligning IT with business.
In the last decade, IT teams were often left in the dark whenever a problem in the IT infrastructure led to the unavailability or poor responsiveness of an IT application service used by the organization's business process. The problem? The lack of mature IT processes and tools meant IT teams rarely had any insight into the impact of the problem on the business.
As a result, IT was often criticized for being not aligned with the needs of the business. This led to the coining of the term "business service" which was different from an IT service. A business service was defined as an IT service that was provided by the IT team to the business and that had an intrinsic financial value associated with it.
Any impact to a business service always had a financial implication, and it was all the C-level executives cared about. This led to the pursuit of the lofty goal of identifying, measuring and ensuring availability and response time of business services, aka Business Service Management (BSM).
BSM dynamically linked business-focused IT services to the underlying IT infrastructure. It was what the CIOs and IT heads of the time wanted to hear, and the marketeers served up BSM to them as the holy grail of IT.
- Alignment of IT and business: BSM was typically sold to the C-level executives as "The Tool" - a magic pill that could automatically help them align IT with business. Numerous productivity numbers and terms such as "time to gather business insights" were thrown up to justify BSM purchases.
- Faster time to resolve problems: BSM users were touted to be an order of magnitude faster in isolating and diagnosing problems compared to those not using it.
- Easier implementation: Not only could BSM improve IT productivity and business profitability, it was also supposed to be a breeze to set up and automatically configure.
- Better TCO and ROI: IT operations would be able to reactively and proactively determine where they should be spending their time to best impact the business. The cost savings in faster troubleshooting and increased business profitability would justify the investment in BSM.
- Power and control for business owners: Business owners were promised visibility and control into what was happening and how it could be fixed.
BSM Oversold and Under Delivered
As organizations started gradually buying and using BSM products, they realized that those products required a lot of manual effort and complex procedures to work. It was not the plug-and-play solution that was originally promoted.
BSM was a term coined to fill the gap between businesses' needs and IT capabilities. When business failed to see the value in BSM, the BSM promises fell flat.
So why didn't BSM live up to expectations? Probably because:
- BSM did not truly reflect the financial impact of IT on business.
- BSM did not have automated, real-time updates to reflect the current status of IT. As IT changed, BSM systems would either have older data or require manual update of the status.
- There was no easy and automated way to capture all the dependencies of a business process on the underlying IT components. Capturing such details was complex and often inaccurate, and it required a lot of effort.
- BSM was probably ahead of its time. BSM-required technologies such as automated discovery and dependency mapping and end-user monitoring were not sufficiently matured at that time.
As originally brought to market, BSM solutions failed to deliver the coveted alignment of IT and business. However, the initial failure did little to discourage organizations from pursuing their goal.
In the second article of this two-part series, we will take a look at the rising popularity of APM and the resurgence of BSM as companies continue to seek alignment.
Read Part 2 of this article: IT and Business Alignment: Has APM Evolved to Fulfill the Promise of BSM? Part 2
The tech world may be falling in love with artificial intelligence and automation, but when it comes to managing critical assets, old school tools like spreadsheets are still in common use. A new survey by Ivanti illustrates how these legacy tools are forcing IT to waste valuable time analyzing assets due to incomplete data ...
Over 70% of C-Suite decision makers believe business innovation and staff retention are driven by improved visibility into network and application performance, according to Rethink Possible: Visibility and Network Performance – The Pillars of Business Success, a survey
conducted by Riverbed ...
Modern enterprises rely upon their IT departments to deliver a seamless digital customer experience. Performance and availability are the foundational stepping stones to delivering that customer experience. Along those lines, this month we released a new research study titled the IT Downtime Detection and Mitigation Report that contains recommendations on how to best prevent, detect or mitigate brownouts and outages, given the context of today’s IT transformation trends ...
While Application Performance Management (APM) has become mainstream, with a majority of tech pros using APM tools regularly, there's work to be done to move beyond troubleshooting ...
Over the last few decades, IT departments have decreased budgets in part because of recession. As a result, they have are being asked to do more with less. The increase in work has amplified the need for automation ...
Many variables must align for optimum APM, and security is certainly among them. I offer the following APM predictions for 2020, which revolve around the reality that we will definitely begin to see much deeper integration of WAN technology on the security front. Look for this integration to take shape in the following ways ...
When it comes to growing a successful company, research shows it isn't about getting the most out of employees, but delivering an experience that empowers them to be and do their best. And according to Priming a New Era of Digital Wellness, a new study conducted by Quartz Insights in partnership with Citrix Systems, technology is the secret to doing so ...
Only 11% of website decision-makers feel that they have complete insight into the scripts that they use on their websites. However, industry estimates state that about 70% of the code on a website comes from a third-party library or service. Research highlights a clear need to raise awareness of the potential threats associated with the vulnerabilities inherent in third-party code ...
The ever-increasing access and speeds offered by today's modern networks offer many advantages to businesses and consumers, but also make the integrity of their performance and security more paramount than ever before. Organizations are struggling to manage the constant fluctuations in network conditions and security threats. This has prompted many to explore how automation can help to streamline network management and security processes ...
The demand to deliver a consistently positive and innovative customer experience is something that many companies — more specifically, their DevOps teams — are currently grappling with. While the ability to push out multiple features a week may appear as a great accomplishment for DevOps teams, our survey showed that 82% commonly discover bugs in production ...