What is IT Operations Management (ITOM)?

IT operations management (ITOM) is the set of practices and tools IT teams use to keep services running day to day: monitoring systems, handling outages, scheduling changes and tracking dependencies.

What is IT operations management?

ITOM covers the running of technology services after they are built. Where a service desk answers requests from users, ITOM watches the systems underneath: it detects that something is wrong, routes the alert to the right responder, coordinates the fix and records what changed. The work draws on several ITIL 4 practices, among them incident management and change enablement, and it depends on an accurate record of which systems support which business services (ITIL on SmartSuite's glossary).

What does IT operations management include?

Function	What it does	What the record shows
Event and alert management	Receives alerts from monitoring tools and decides which need action	Source, severity, owner and outcome
Incident and outage coordination	Assigns responders and tracks a disruption to resolution	Impact, timeline and responsible team
Change and release scheduling	Plans maintenance windows, changes and deployments so they do not collide	Approvals, schedule and affected services
Dependency mapping	Links systems and applications to the services that rely on them	Configuration items and their relationships
On-call and escalation	Keeps schedules and escalation rules so the right person is notified	Rotation, contact path and response times
Operational reporting	Tracks health and trends across services	Incident volumes, change outcomes and service status

How is ITOM different from ITSM?

IT service management (ITSM) organizes how IT delivers services to people: requests, incidents, problems and changes as managed processes. ITOM focuses on the health of the infrastructure and applications behind those services. In practice the two share records. An alert found through ITOM becomes an incident in ITSM, and a change approved in ITSM appears on the ITOM calendar, so most teams run them against one set of data.

Why does IT operations management matter?

• Faster response. Routing each alert to a named responder shortens the gap between a failure and the first action.
• Fewer collisions. A shared calendar of changes, releases and maintenance windows shows conflicts before they cause an outage.
• Clear impact. Mapping dependencies shows which business services an outage touches, so stakeholders get accurate status.

Related terms

• IT service management
• CMDB
• Configuration management
• Incident
• Problem management
• Change enablement

In SmartSuite

SmartSuite's IT operations management solution brings release planning, maintenance scheduling, outage coordination and dependency visibility into one workspace, with products such as On-Call Management and Configuration Management (CMDB).

Frequently asked questions

What is the difference between ITOM and ITSM?

ITSM manages how IT delivers services to users through processes such as incident, problem and change management. ITOM manages the health of the systems that run those services, through monitoring, events, outages and scheduling. They overlap at incidents and changes, and most teams connect the two so an alert becomes a tracked incident.

What does an ITOM team do day to day?

An ITOM team watches alerts from monitoring tools, decides which need action, assigns responders and tracks outages to resolution. It also schedules changes, releases and maintenance windows, keeps the record of how systems depend on services, and reports on operational health so leaders can see trends.

Do you need a CMDB for ITOM?

A CMDB is not required to start, but it makes ITOM more useful. It records configuration items and the relationships between them, so when an alert fires the team can see which services depend on the affected system. Teams often begin with their most critical services and extend the record over time.

Conclusion

ITOM keeps technology services running by connecting alerts, responders, changes and dependencies in one record. Start with the services the business cannot do without, map the systems behind them, and add scheduling and on-call routing as the record proves accurate.