--- title: Monitoring AI operations in ITOM as an admin description: The AIOps home page tracks operator activity and key metrics in real-time. It is available to all customers. Once your AI Specialist is active, additional metrics and capabilities unlock to help you measure impact, spot issues early, and report on AI performance over time. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/ai-specialist-dashboard-metrics.html release: australia topic_type: reference last_updated: "2026-11-02" reading_time_minutes: 5 keywords: [Dashboard, metrics, AI specialist, MTTR, performance] breadcrumb: [Manage the AI specialist, AIOps AI Specialist, ITOM AIOps specialists, AI in ITOM AIOps, ITOM AIOps, IT Operations Management] --- # Monitoring AI operations in ITOM as an admin The AIOps home page tracks operator activity and key metrics in real-time. It is available to all customers. Once your AI Specialist is active, additional metrics and capabilities unlock to help you measure impact, spot issues early, and report on AI performance over time. ## Overview tab The **Overview** tab is your team's command center. It gives you a real-time snapshot of alert activity, workload distribution, and the impact AI is having on your team's performance- all in one place. Use the **Overview** tab to spot imbalances, track resolution speed, and see at a glance whether your team and your AI specialist are keeping up with incoming alerts. **Note:** The Admin \[evt\_mgmt\_admin\] can view metrics for all teams. The AIOps Manager \[evt\_aiops\_manager\] can view metrics only for the teams they are responsible for. Both the Event Management Admin \[evt\_mgmt\_admin\] and the AIOPs Manager \[evt\_aiops\_manager\] have access to [AIOps home page](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/ai-specialist-dashboard-metrics.md). If you don't install the ServiceNow Otto for IT Operations Management \(ITOM\) plugin, AI-related KPIs aren't visible. \[Omitted image "ai-specialist-dashboard-overview.png"\] Alt text: Dashboard showing alerts, workload, and MTTR metrics.
| Metrics | What it shows | Why it matters |
|---|---|---|
| AI Efficiency | ||
| Alert MTTR using AI | Mean time to resolve an alert with AI active. | Tracks the mean time to resolve an alert when AI is active. An increase in this metric indicates a reduction in AI effectiveness and requires investigation. |
| Alert MTTR without AI | Mean time to resolve an alert manually. | Tracks the mean time to resolve an alert without AI. The difference between this value and the Alert MTTR with AI represents the efficiency gained through AI adoption. |
| Time saved using AI | Total time recovered through AI-assisted resolutions in a given period. | Represents the total time saved through AI-assisted alert resolution. This recovered time can be redirected toward higher-value tasks and activities. |
| Time saved by automation | Time saved through fully automated actions, separate from AI recommendations. | Represents the time saved through automation, independent of AI assistance. Combined with the time saved using AI, this metric provides a complete view of the manual effort eliminated. |
| Workload status | ||
| Assigned vs unassigned alerts & incidents | Side-by-side count of alerts and incidents that have an owner versus those that don't.The **sn\_sow\_em.aiops\_manager\_homepage\_assignment\_scope** property controls whether the homepage overview includes alerts that are unassigned to any group, in addition to alerts from the groups you manage. | Provides a side-by-side count of alerts and incidents with and without an assigned owner. Persistently high unassigned counts indicate a backlog risk and may require a review of routing rules or staffing coverage. |
| Team assignment | ||
| Managed team\(s\) assignment | Per-person breakdown of open alerts and incidents across each team member. | Provides a per-person breakdown of open alerts and incidents across each team member. Use this metric to identify workload imbalances and rebalance assignments proactively to prevent SLA breaches. |
| Alert severity | ||
| Open alerts by severity | Total open alerts broken down by severity — Critical, Major, Minor, and Low. | Provides the overall alert load and helps prioritize attention accordingly. A spike in Critical or Major alerts requires immediate action. |
| Incident priority | ||
| Open incidents by priority | Total open incidents across five priority tiers — 1-Critical, 2-High, 3-Moderate, 4-Low, and 5-Planning. | Helps you focus immediate attention on the highest-priority incidents while using the Planning tier to anticipate and forecast upcoming team demand. |
| Personal workload | ||
| My open alerts | The manager's personal queue — open alerts assigned directly to them. | Helps you monitor your own workload alongside your team's and ensure your assigned alerts are not overlooked. |
| My open incidents | The manager's personal queue — open incidents assigned directly to them. | Helps you monitor your own workload alongside your team's and ensure your assigned incidents are not overlooked. |