IT Service Management
The processes and frameworks that govern enterprise IT.
IT Service Management (ITSM)
ITSM is the discipline of designing, delivering, managing, and improving IT services to meet business needs, focusing on people, processes, and technology from a customer-centric view.
ITSM is like running a hotel. You have a front desk (service requests), maintenance workers (incident management), and planners for remodeling (change management). It’s how IT provides a smooth service to everyone else.
ITSM focuses on operations over pure development. Core processes include Incident, Problem, Change, Configuration, Service Request, and Asset Management. Leading platforms like ServiceNow orchestrate these workflows to guarantee SLA adherence and business alignment.
Kumar Nikhil operates deeply within ITSM environments using ServiceNow and HPSM to orchestrate critical service delivery functions, ensuring operations align with business objectives and SLAs.
Incident Management
The process to restore normal service operation as quickly as possible and minimize business impact.
When a computer system breaks or stops working, Incident Management is the emergency response. Fix it fast so people can get back to work.
Incident Management follows a strict ITIL lifecycle: Identification -> Logging -> Categorization -> Prioritization -> Diagnosis -> Escalation -> Resolution -> Closure. Prioritization is based on Business Impact and Urgency.
Kumar Nikhil owns end-to-end Incident Management. He regularly handles detection, logging in ServiceNow, prioritization, scaling to specialized teams, and validating resolution while strict SLA and OLA thresholds are monitored.
Change Management
A controlled process to manage all changes to IT services with minimum disruption.
If you want to upgrade a massive computer system, you can't just unplug it. Change Management is the strict planning and permission process to make sure the upgrade doesn't break anything.
Change Management (or Change Enablement in ITIL 4) controls lifecycle changes via RFCs. Changes are classified as Standard, Normal, or Emergency. It requires deep impact and risk assessments, CAB/eCAB approvals, testing verifications, and Post Implementation Reviews (PIRs).
Kumar acts as a gatekeeper in this space. Before any change reaches the Change Advisory Board (CAB), he actively validates the technical scope, dependencies, risk level, and potential production impact, coordinating with security, network, and storage teams.