Skip to main content

7 Must-Have Capabilities for BSM Service Impact

The following 7 requirements for a BSM Service Impact solution are based on the minimal criteria for inclusion in the “EMA Radar For Business Service Management: Service Impact”.

1. Support for service monitoring from a cross-domain perspective

The tool should be able to capture, reconcile and correlate cross-domain interdependencies impacting business service performance. Functionality could include performance management databases looking at performance or time series information; event-management-centric integrations; or self-learning heuristics.

2. Reconciliation of information from multiple sources

The solution should offer capabilities for reconciling information from multiple sources, including multiple brands of management tools.

3. Insight into user experience

The ideal BSM Service Impact product should be able to monitor and assimilate user experience metrics, a key indicator of business impact.

4. Automated linkages between IT service performance and business outcomes

At a minimum, the tool should alert the user to issues regarding SLA commitments and penalties. Other business outcomes can also include business process impacts, direct revenue impacts, and other business activity-related impacts.

5. Capture of application/infrastructure interdependencies

The BSM Service Impact tool should capture some level of interdependencies between IT applications and infrastructure, whether for in-depth configuration or for more real-time application flows, or at minimum for cross-domain diagnostic purposes.

6. Policy-driven automation

The solution should support some level of policy-driven automation for aligning service monitoring with active outcomes in terms of remediation. This would include closed-loop incident management and problem resolution, as well as configuration changes required for automated
Remediation.

7. Support for multiple roles across IT and the business

BSM Service Impact technology should support multiple roles inside and outside of IT, through dashboards and analytics, for critical decision-making and purposes of automation.

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

7 Must-Have Capabilities for BSM Service Impact

The following 7 requirements for a BSM Service Impact solution are based on the minimal criteria for inclusion in the “EMA Radar For Business Service Management: Service Impact”.

1. Support for service monitoring from a cross-domain perspective

The tool should be able to capture, reconcile and correlate cross-domain interdependencies impacting business service performance. Functionality could include performance management databases looking at performance or time series information; event-management-centric integrations; or self-learning heuristics.

2. Reconciliation of information from multiple sources

The solution should offer capabilities for reconciling information from multiple sources, including multiple brands of management tools.

3. Insight into user experience

The ideal BSM Service Impact product should be able to monitor and assimilate user experience metrics, a key indicator of business impact.

4. Automated linkages between IT service performance and business outcomes

At a minimum, the tool should alert the user to issues regarding SLA commitments and penalties. Other business outcomes can also include business process impacts, direct revenue impacts, and other business activity-related impacts.

5. Capture of application/infrastructure interdependencies

The BSM Service Impact tool should capture some level of interdependencies between IT applications and infrastructure, whether for in-depth configuration or for more real-time application flows, or at minimum for cross-domain diagnostic purposes.

6. Policy-driven automation

The solution should support some level of policy-driven automation for aligning service monitoring with active outcomes in terms of remediation. This would include closed-loop incident management and problem resolution, as well as configuration changes required for automated
Remediation.

7. Support for multiple roles across IT and the business

BSM Service Impact technology should support multiple roles inside and outside of IT, through dashboards and analytics, for critical decision-making and purposes of automation.

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...