An Adaptive Priority Approach For Effective Problem Resolution in ITSM
An Adaptive Priority Approach For Effective Problem Resolution in ITSM
Discovered CIs
Incident
Service Catalog
Networks events & alerts are continuously monitored using network monitoring tools, and only the escalated alarms are logged in the service
management tool. The change management module helps plan future changes and execute any corrective actions in the network.
Growing customer base & Difficulty in identifying the Identifying the number of affected
changing needs signals out of noise customers & impact intensity
With the exponential growth in Isolating a nuisance or a noisy Identifying the accurate number of
a number of incidents, the key event can be a challenge. end users/customers affected due to
challenges faced by the Increased noisy events often network incidents is a real challenge.
operations team are identifying cause delays & visibility issues Monitoring & operations tools are
the high-priority issues, when for critical events, leading even unable to provide this essential
to address them, and whom to to customer churn. information.
assign them.
There is always a need Only reactive approach High MTTR leads to high
for an expert system - discovering problems OPEX
when users complain
Support teams have a real Currently a majority of the time is
challenge in raising multiple Inability of the current system spent in identifying & isolating a
tickets and following up on to come up with predictive & problem, rather than fixing it.
emails. There is a constant need proactive measures to prevent Hence higher MTTR (Mean Time To
for an expert system that can the incident from happening Resolve) leads to higher
automatically categorize, operational cost.
correlate & assign appropriate
severity to an incident.
IT & network systems have seen major evolutions during the last few decades. Strategies that helps CSPs in Adaptive Priority Model implementation
With tremendous changes in technology & services growing in leaps and bounds,
monitoring applications are unable to fulfill the dynamic demands of response
time and stringent SLAs. The number of incidents and alarms generated in the IT & Mapping business services to infrastructure
network landscape of a CSP is constantly on the rise. It is important to prioritize components
the incoming incidents with the right priority based on various attributes. However Map each business processes directly to
most ITSM systems are still prioritizing the incidents only based on urgency & infrastructure to identify impact on any service
impact. disruption. This factor improves relation between
service item and your affected incidents.
This insights main focus is prioritizing incidents with adaptive model which helps in faster & effective resolution of a problem
Below solution diagram shows how incidents are analysed by the Adaptive priority Model (a plug-in integrated with existing ITSM) leveraging its
inbuilt Topology Analyser to assign right priority
As the number of incidents grows, the support team finds it challenging to handle them. The existing
URGENCY
incident priority calculation model using traditional method is shown in the below matrix which is based on
impact vs. urgency.
Recommended Solution
Traditional ITSM systems depend only on impact & urgency factors to determine the incident priority while Adaptive Incident Priority Model Plugin equips
ITSM systems with additional capability of looking into multiple influencing factors, which helps in determining the right priority. Without a framework for
establishing correct priority, it is very difficult to meet service level agreements & trigger incident escalations appropriately.
Enriching the incident with intelligent data helps in effective problem identification & resolution.
Adaptive Priority Incident Model solution is based on new business logic/algorithm with various input parameters which include:
Business area (residential, B2B, IT) | Service affected (local, urban, regional) | Service category (DTV, CRM, billing)
| Impacted customers (0~500,501~5000,5001~50,000)
Open API availability on CMDB or network topology database makes it easier for adaptive plugin integration.
Copyright 2017 Prodapt Solutions. All Rights Reserved. 6
Confidential & Restricted
Recommendations - Prioritization of incidents based on number of end-users ..Part(2/2)
RELATIONSHIP
A typical network is a complex system which comprises multiple telecom nodes from
different vendors across multiple domains. Accurately identifying the number of affected
end-users because of an incident is a real challenge. NODE RELATIONSHIP
For e.g., smooth operation of a wireless network depends on the underlying fiber RELATIONSHIP
network.
NODE
Recommended Solution
Topology Analyzer - an intuitive GUI, which is used to traverse the entire network of the CSP.
Based on the relationship between two nodes in a telecom network, we can identify its type of relationship i.e. either its a parent-child or uncle-nephew.
If a port does not exist without a card, it is an example for parent-child relationship.
Based on selected incident from the network, the faulty element can be identified through the Topology Analyzer which in turn helps in identifying the
number of end-users affected or the portion of customer base impacted on the specific node through its relationship data. Adaptive priority model
helps in assigning the right priority to the incidents based on this info.
Prerequisite for implementing relationship based prioritization model is the availability of relationship data of entire network
Business Area Service Impact Impacted Customers Service Category Key Service Impact Urgency Priority
Residential Local 0-500 DTV Tier 2 4-Minor/Localized Low Low
IT Urban 501-5000 CRM Tier 2 2-Significant/Large Medium Medium
IT Regional 5001-50000 Billing Tier 1 1-Extensive/Widespread High High
Nationwide or Multiple
B2B Countries 50001-999999999 Customer-facing Mail B2B Tier 1 1-Extensive/Widespread Critical Critical
Element ID
Type of Customer DTV Internet Voice B2B
1611E- 08-008 No. of affected customers 15 28 26 3
03 In radar monitoring
Continuous monitoring of affected configuration items(CIs) in
service impacted areas
04 Proactive notifications
Incident priority-based notifications to all relevant stake
holders & the management team depending on the escalation
matrix
London
New York
Tualatin THANK YOU!
Dallas
Bengaluru
Chennai
Johannesburg