Value & Adoption

AtlasAI helps you prove value and track adoption so you can report on ROI and guide rollout. This page describes where these capabilities live and how to use them.

Where value and adoption show up

Depending on your deployment and plan, you may see:

• Value dashboard — KPIs such as incidents auto-resolved, MTTR/MTTD, time saved, cost avoided. Often reachable from the Command Center pipeline (e.g. Value stage) or a dedicated Value or Reports area.
• Adoption / maturity — How much of the platform is in use: connectors, discovery jobs, runbooks, automation runs, active users. Sometimes presented as a maturity score or checklist.
• Reports — Prebuilt or custom reports (e.g. incident volume, automation success rate, RCA accuracy) that you can export or share. See Reports.
• FinOps — Cost and efficiency metrics when FinOps is enabled. See FinOps.

Value dashboard (if enabled)

Purpose: Single view of “how well is autonomous IT working?” for stakeholders.

Typical metrics:

• MTTD (Mean Time to Detect) — How quickly issues are detected.
• MTTR (Mean Time to Resolve) — How quickly incidents are resolved.
• Automation success rate — % of automation runs that succeed.
• Self-healing rate — % of incidents resolved without manual intervention (or with minimal steps).
• Incidents by severity — Volume and trend.
• Time/cost saved — Estimated savings from automation and faster resolution (if calculated).

How to use:

1. Open Value from the Command Center pipeline strip, or Reports → Value (or equivalent in your deployment).
2. Choose a time range (e.g. last 30 days).
3. Use the metrics to report to leadership or to tune operations (e.g. add runbooks where automation rate is low).

Adoption and maturity

Purpose: See how fully the platform is adopted so you can prioritize rollout (e.g. more data sources, more runbooks, more services under automation).

Typical dimensions:

• Data: Connectors configured, discovery jobs running, services in topology/CMDB.
• Operations: Incidents created and resolved, runbooks created and approved, automation runs.
• People: Active users, roles assigned, SSO vs password.
• Coverage: % of critical services with runbooks, % of incidents with RCA run.

How to use:

1. Open the Adoption or Maturity view (may be under Settings, Reports, or Command Center).
2. Review gaps (e.g. “No runbooks for payment service”) and plan next steps (e.g. add runbooks, connect more data).
3. Use it for onboarding new teams: show what “good” looks like and what’s left to do.

Reports

The Reports module provides prebuilt and custom reports. Use them to:

• Export incident and automation metrics for external dashboards or leadership.
• Build custom reports (if your deployment supports it) for value and adoption.
• Schedule report delivery (e.g. weekly summary email) if that feature is available.

See Reports for details.

How this fits the user journey

• Pipeline: The Value stage in the Command Center pipeline is the “proof” stage: data from Connect → … → Improve flows into value metrics.
• Improve: Post-incident tuning (runbooks, policies) improves automation and RCA over time, which then shows up in value and adoption metrics.

Summary

See also

• Pipeline: Connect → Improve — How the Value stage fits
• Reports — Reporting capabilities
• FinOps — Cost and efficiency
• How it works — Key metrics (MTTD, MTTR, etc.)