CIS - DF Roles, Personas, and Responsibilities

Administers CMDB configuration, tools, health, and day-to-day CMDB operations.

Keep the CMDB usable, governed, healthy, and correctly configured.

The administrator configures and operates the CMDB; the steward focuses on data quality and ownership.

CMDB Administrator focuses on CMDB structure, health, and data; Platform Admin manages broader platform administration.

Maintains CMDB data standards, quality rules, and record consistency.

Owns the quality, accuracy, completeness, and compliance of assigned data.

Review and remediate poor-quality or noncompliant CMDB data.

The owner is accountable for the data; the steward helps maintain and improve it.

Accountable person or group for a data domain, CI class, service, or key attribute set.

Owns the configuration management process and governance model.

The CMDB supports reliable operational, audit, and service management outcomes.

The manager governs the process; the administrator runs and configures the CMDB.

Owns expectations for a CI class, including attributes, lifecycle, and data quality.

Helps decide which attributes are required, recommended, or meaningful for a class.

Defines how records in the class should be created, maintained, retired, or archived.

Responsible for the accuracy and operational relevance of a specific configuration item.

Group responsible for supporting or resolving issues for a CI.

Group used to route work related to a CI.

Group accountable for managing a CI or service record.

Person or group accountable for the CI, service, or record.

Designs the CMDB/CSDM approach to fit the platform, products, integrations, and long-term architecture.

Avoid designs that create technical debt or break upgradeability.

Accountable for the ServiceNow platform strategy, governance, and value delivery.

The owner is accountable for direction and value; the architect designs how it should work.

Builds or extends platform logic while respecting CMDB/CSDM design and upgradeability.

Custom logic that bypasses IRE or creates nonstandard data patterns.

Designs and configures the implementation to meet CMDB/CSDM requirements.

Helps design, configure, and deliver the CMDB implementation.

Administrator, steward, configuration manager, class owner, architect, owner, developer, consultant.

Provides authority, funding, and organizational support for CMDB governance.

Cross-functional group that makes CMDB standards, ownership, and exception decisions.

Rules, roles, processes, and accountability that keep CMDB data trustworthy.

Usually leads to stale, incomplete, or disputed CMDB data.

Clarifies who is responsible, accountable, consulted, and informed.

Ultimately answerable for the outcome or decision.

Performs the work needed to complete the task.

Provides input before a decision or action is completed.

Kept aware of decisions, outcomes, or changes.

Owns the design and performance of a process that uses CMDB data.

Needs accurate CI and service data for routing, impact, and reporting.

Needs reliable CI relationships and ownership for risk and impact assessment.

Uses CMDB relationships and history to support root-cause analysis.

Owns asset lifecycle, financial, contractual, and inventory data.

Asset Manager tracks asset lifecycle and cost; CI Owner focuses on operational configuration data.

Usually shared between asset management and configuration management stakeholders.

Accountable for a service and its value, performance, and lifecycle.

Owns a business-facing service and its expected outcomes.

Owns a technical service used to support applications or business services.

Owns operational accuracy and impact visibility for an application service.

Accountable for an application, its lifecycle, and its business/technical fit.

Owns the business application from a portfolio and lifecycle perspective.

Owns product direction, backlog priorities, and business value for a product or platform capability.

Maintains or governs contract-related foundation data.

Maintains core reference data such as organizations, users, groups, locations, and companies.

Connects the right owners to the right CSDM domains and records.

Process owners, data stewards, product owners, and contract managers.

Application service owners, technology service owners, and technology consumers.

Consumes technical service offerings, often through a request catalog.

Owns infrastructure or platform services delivered to technology consumers.

Reviews and certifies whether assigned data is still accurate.

Person asked to confirm or correct CI data.

Defines governance intent, scope, remediation expectations, and accountable parties.

Person or group expected to act on generated data tasks.

Person or group accountable for fixing a specific data issue.

Reviews duplicate candidates and decides merge, de-duplicate, or no action.

Owns quality expectations for an important class monitored in CMDB health.

Whether to use an existing class, extend a class, or avoid unnecessary customization.

Maintains identification and reconciliation behavior for CI data sources.

Owns the quality and reliability of a CMDB data source.

Owns Discovery configuration, credentials, schedules, and scan reliability.

Owns connector configuration and source data quality for imported CI data.

Maintains MID Server health, connectivity, credentials, and operational readiness.

Needs accurate CI data for risk, vulnerability, compliance, and regulatory tracking.

Needs evidence that required CMDB data meets policy or regulatory expectations.

Needs traceable, reliable records showing control and data quality.

Ensures compliance identifiers are tracked against the correct CSDM objects.

Ensures CI and service relationships are accurate enough for impact and dependency analysis.

Maintains CIs that cannot be discovered or automatically populated.

Maintains important attributes that automated tools cannot reliably discover.

Uses workspace views and tasks to manage CMDB quality and remediation.

Uses CMDB dashboards to identify trends, risks, and remediation priorities.

Defines or monitors the metric used to judge CMDB process success.

Owns a critical success factor tied to CMDB value or governance outcomes.

Ensures CMDB governance becomes recurring work, not a one-time cleanup.

Confirms whether stale records should be updated, retired, archived, or excluded.

Defines how CI states move from active to retired, archived, or obsolete.

Approves justified deviations from CMDB standards or health rules.

Ensures unresolved data quality issues reach the right accountable leader.

Ensures CMDB contributors understand standards, tools, and expectations.

Anyone who creates, updates, validates, or consumes CMDB data.

No one knows who owns a CI, class, service, or data quality issue.

Clear owners, recurring reviews, actionable dashboards, and closed remediation tasks.