SmartSuite for the Configuration Manager

Asset config. Maintains configuration items, attributes and service relationships in a CMDB with audit history and the data quality rules you define.

Change. Provides impact analysis for change requests from the service map and records configuration updates after deployment.

Incident. Links incidents and problems to the configuration items affected for faster diagnosis.

Continuity. Supplies the system and dependency inventory that DR and continuity plans rely on.

Reporting. Reports CMDB completeness, accuracy and audit results to IT leadership.

What does a Configuration Manager own in an IT organization?

The Configuration Manager owns service configuration management: the CMDB, the configuration items in it, their relationships to services and the data quality rules that keep it trustworthy. That includes the configuration management plan and data model, the definition of item types and attributes, control over changes to configuration records, audits for accuracy and the integration of discovery, asset and cloud sources. Incident, change, asset and risk processes all work from the picture this role maintains.

How does SmartSuite help a Configuration Manager keep the CMDB accurate?

Configuration Management (CMDB) maintains configuration items, their attributes and their relationships to services in one CMDB, with an audit history on every record and the data quality rules you define for ownership, relationships and review dates. Because every change to a configuration record is logged, you can run accuracy audits against the history rather than reconstructing what happened. IT Asset Management and Enterprise Assets & Structure hold the asset and organizational records the CMDB links to, so the estate is described once and referenced everywhere.

How does the CMDB support impact analysis for change requests?

When a change request is raised, SmartSuite provides impact analysis from the service map held in Configuration Management (CMDB), so the Change and Release Manager can see which services and dependencies a change touches before it is approved. After deployment, Change Management records the configuration updates back into the CMDB, which keeps the service map current instead of drifting from the live estate. The Configuration Manager owns that loop: the map informs the change, and the change updates the map.

How are incidents linked to configuration items in SmartSuite?

IT Incident Management links each incident and problem to the configuration items affected, so the Incident and Problem Manager can see which services depend on the failing item and diagnose faster. For the Configuration Manager, those links are also a quality signal: incidents that cannot be matched to a configuration item point to gaps in the CMDB. The same system and dependency inventory supplies the IT Disaster Recovery Lead with the data that DR and continuity plans rely on.

How does a Configuration Manager report CMDB health to IT leadership?

SmartSuite reports CMDB completeness, accuracy and audit results to IT leadership from the same records the processes use, so the Configuration Manager does not assemble a separate reporting pack. Completeness and accuracy are measured against the data quality rules and the audit history, and audit results record what was checked and what was corrected. The IT Service Manager sees the same figures, which turns the conversation about investment in discovery or clean-up into a factual one.

What does it take to get a CMDB started in SmartSuite?

Start with the configuration item types, attributes and service relationships defined in your configuration management plan, then load the records you already trust from discovery, asset and cloud sources. SmartSuite holds them with audit history and data quality rules from the first record, so quality improves as you go rather than waiting for a complete load. Scope can begin with the services that matter most to incident and change and widen from there; the IT Asset Manager and Systems Administrator are usually the next users.