Technical Brief Guide ITSM Architecture

ServiceNow ITSM Module

A comprehensive guide to digitizing IT service delivery through a single platform architecture, automation, and relational data structures.

Overview

ServiceNow ITSM (IT Service Management) is a comprehensive suite designed to digitize and streamline IT service management processes. It leverages a single platform architecture to automate workflows, improve service delivery, and enhance user experience.

1

Core ITSM Components in ServiceNow

Incident Management

incident

Purpose: Restore normal service operation quickly after an unplanned interruption.

Key Features
  • Incident logging (manual and automated)
  • Categorization, prioritization, and assignment rules
  • SLA (Service Level Agreement) tracking
  • Lifecycle: New → In Progress → On Hold → Resolved → Closed
Technical Elements
  • Business rules for notifications & escalations
  • Workflows and Flow Designer for automation

Problem Management

problem

Purpose: Identify root causes of incidents and prevent recurrence.

Key Features
  • Problem detection (manual or incident trends)
  • Root Cause Analysis (RCA)
  • Known Error Database (KEDB) integration
  • Lifecycle: New → Assess → RCA → Resolved → Closed
Technical Elements
  • Linkage between problems and incidents for impact analysis
  • Automated notifications and task assignments

Change Management

change_request

Purpose: Manage the lifecycle of all changes to minimize risk and impact.

Key Features
  • Categorization (Standard, Normal, Emergency)
  • Change approval workflows & risk assessments
  • Implementation and review processes
Technical Elements
  • Change Advisory Board (CAB) scheduling & approval flows
  • CMDB integration for asset impact assessment

Request Management

sc_request

Purpose: Handle user requests for IT services or products.

Key Features
  • Service Catalog & Request Fulfillment
  • Catalog item creation with variable sets
  • Request tracking and SLA adherence
Technical Elements
  • sc_request and Requested Item (sc_req_item)
  • Integration with fulfillment systems and asset provisioning

Configuration Management (CMDB)

cmdb_ci

Purpose: Maintain an accurate database of IT assets and their relationships.

Key Features
  • Configuration Items (CIs) tracking
  • CI relationship mapping
  • Impact analysis for incident, problem, and change management
Technical Elements
  • CMDB tables (cmdb_ci and extensions)
  • Discovery tool for automated CI population
  • Dependency Views and Service Maps
2

Technical Architecture & Tools

Platform & Database
  • Built on the Now Platform using proprietary JavaScript-based server-side and client-side scripting.
  • Uses a relational CMDB structure with tables and relationships.
  • Tables are extendable for custom ITSM processes.
Automation & Workflows
  • Flow Designer: Low-code interface to build flows automating tasks across ITSM.
  • Business Rules: Server-side scripts triggered on database operations.
  • Script Includes: Reusable server-side functions.
  • UI Policies & Actions: Client-side form behaviors and validations.
Reporting & Dashboards
  • Real-time reports using Performance Analytics.
  • Customizable dashboards for SLA, incident trends, and change success rates.
  • Scheduled reports and automated email notifications.
Integrations & APIs
  • REST and SOAP APIs for external system integration.
  • Integration with Discovery, Event Management, and Orchestration modules.
  • Webhooks and inbound email actions for automated ticket creation.

Key Concepts to Remember

SLA (Service Level Agreement): Defines expected service levels and is critical across Incident, Problem, and Change Management.

Lifecycle States: Each ITSM process follows specific states for tracking progress through to completion.

CMDB Integration: Central for understanding asset relationships and running real-time impact analysis.

Automation: Flow Designer and scripting reduce manual efforts and operational errors.

Security & Roles: Role-based access controls (e.g., itil, admin) govern visibility and record actions.

3

Technical Tables & Relationships

Table Name Table Label Description
incident Incident Stores incident records
problem Problem Stores problem records
change_request Change Request Stores change request records
sc_request Service Catalog Request Represents an overall service request
sc_req_item Requested Item Individual items within a service request
task Task Base table for work-related records (parent of incident, problem, change, etc.)
cmdb_ci Configuration Item Base table for configuration items (CIs)
cmdb Configuration Management Database Parent table for all CMDB data
sys_user User Stores user information
sys_user_role User Role Defines user roles
sys_user_grmember Group Member Links users to groups
task_sla SLA Tracks SLA records linked to tasks

  1. Task Table Hierarchy: task is the core parent table. incident, problem, change_request, and sc_req_item all extend from it, inheriting shared attributes like state, priority, assignment, and SLA tracking.
  2. Incident Management: Extends task. Linked to cmdb_ci to identify affected CIs. Related incidents group via parent-child task relationships.
  3. Problem Management: Extends task. Links to multiple incidents for root cause analysis via the incident field. Known errors are stored in kb_knowledge/kb_knowledge_base.
  4. Change Management: Extends task. Creates change tasks via change_task table. Approvals are managed via sys_approval_approver and sys_approval_group.
  5. Request Management: sc_request holds overall service requests, which contain multiple sc_req_item records (each extending task).
  6. CMDB: cmdb_ci is the base for all CIs. Extended by specialized types (servers, apps). Relationships between CIs are stored in cmdb_rel_ci.
  7. SLA Management: Definitions live in contract_sla. SLA execution/tracking records are stored in task_sla linked directly to tasks.
Summary Data Model
sys_user
   │
   ├── task (parent)
   │     ├── incident (cmdb_ci ref)
   │     ├── problem (cmdb_ci ref)
   │     │     └── linked incidents
   │     ├── change_request (cmdb_ci ref)
   │     │     └── change_task
   │     └── sc_req_item (part of sc_request)
   │
sc_request
   │
cmdb_ci
   └── cmdb_rel_ci (relationships)
   │
task_sla (linked to task)

ServiceNow ITSM Technical Brief Guide • Built for Now Platform Architects & Developers