How Does Virima Support ITIL Change Management? CMDB, Impact Analysis, and ViVID Explained

Virima 6.1.1 is an ITIL v4-compliant change management platform that uses live CMDB data and ViVID Service Maps to deliver accurate change impact analysis, automated stakeholder approval routing, pre/post change configuration verification, and risk register integration — all in one unified platform.

Does Virima support ITIL v4 change management?

Yes. Virima 6.1.1 is fully aligned with ITIL v4 Change Enablement principles. It supports all three ITIL change types — standard, normal, and emergency — with distinct workflow paths for each. ITIL 4 Foundation guidance defines Change Enablement as the practice of maximizing successful IT changes by ensuring risks are properly assessed and authorized before deployment — exactly what Virima automates.

Standard changes follow pre-authorized templates. Normal changes trigger full impact analysis and multi-stakeholder approval workflows. Emergency changes use abbreviated approval paths with post-implementation review. All three change types maintain complete audit trails and connect to the Virima CMDB for CI context and relationship data.

Virima’s change management module enforces process compliance through automation — not through manual process management — which aligns with ITIL v4’s emphasis on value-driven, automated service management.

How does Virima use CMDB data for change impact analysis?

Virima uses CMDB relationship data to map every configuration item, service, and stakeholder affected by a proposed change. When a change record targets a specific CI, Virima traverses the CMDB relationship graph to identify:

• All CIs that depend on the target CI (runs-on, depends-on, connected-to relationships)
• All business services composed of affected CIs
• All concurrent open change records on related CIs
• All owners and stakeholders associated with affected CIs and services

This relationship traversal is automatic — it runs against the CMDB’s live data, not static documentation. Because Virima populates its CMDB through continuous Discovery, the relationship data reflects the actual state of the IT environment at the time of change planning.

What does ViVID show during change planning?

ViVID (Virima Visual Impact and Dependency) Service Maps provide a real-time visual graph of every CI, service, and dependency in the scope of a proposed change. During change planning, the ViVID map displays:

• The target CI and its attributes — configuration state, criticality, ownership, and open risk register items.
• Downstream dependencies — every CI that depends on the target, rendered as a connected graph with relationship type labels.
• Affected business services — service containers showing which business services include the affected CIs.
• Pending concurrent changes — open change records on related CIs, flagged visually to identify scheduling conflicts.
• Stakeholder ownership — CI owners and service owners for every node in the map.

The ViVID map gives change engineers and CAB reviewers a complete, visual impact analysis in seconds — replacing manual dependency research.

How does Virima verify configurations before and after a change?

Virima uses its Discovery engine for pre-change and post-change configuration verification.

Before the change window opens, Discovery runs a targeted scan of the CIs in the change scope. The scan captures the current configuration state — installed software, running services, open ports, network connections, and other CI attributes — and stores the result as a baseline snapshot attached to the change record.

After the change is implemented, Discovery runs again on the same CI set. The post-change scan results are compared against the pre-change baseline. Virima surfaces the configuration differences: expected changes (those specified in the change record) and unexpected changes (unintended configuration drift).

This pre/post verification model provides a complete, timestamped audit trail for every change, supporting both change governance and post-incident analysis.

Can Virima automate change approval workflows?

Yes. Virima 6.1.1 supports configurable, automated change approval workflows that derive approver lists from CMDB relationship data.

When a change record is created, Virima reads the ViVID Service Map to identify CI owners, service owners, and dependency owners in the change scope. It then routes approval requests to the identified stakeholders in the sequence defined by the change type and approval rules.

Approval workflows can be configured by:

• Change type (standard, normal, emergency)
• CI criticality level
• Number of affected services
• Presence of risk register items on affected CIs

Approvers receive the change record with the full ViVID impact map and risk context — so approvals are informed decisions, not form acknowledgments.

How does Virima connect change records to risk register items?

Virima 6.1.1 allows change records to be directly associated with CI risk register items. When a CI in the change scope has open risk register entries — known vulnerabilities, compliance obligations, historical incident associations, or deferred maintenance records — those entries appear in the change record.

This association gives change approvers a risk-weighted view of the change: not just what is affected, but what risks are already attached to the affected CIs. It also allows change managers to escalate changes that touch high-risk CIs to CAB-level review, even if the change would otherwise qualify for a streamlined approval path. For foundational guidance on maintaining accurate CI risk data, see Virima’s CMDB best practices guide.

Does Virima support emergency changes?

Yes. Virima 6.1.1 includes dedicated emergency change workflows that balance speed with governance.

Emergency changes use an abbreviated approval path — a smaller set of pre-authorized emergency approvers, rather than the full stakeholder set required for normal changes. This allows emergency changes to be authorized quickly during active incidents or service outages. For a broader look at how change management processes handle all change types in modern IT organizations, see Virima’s change management guide.

Despite the abbreviated approval, Virima maintains a full change audit trail for emergency records. Post-implementation review is built into the emergency change workflow, ensuring that the full CAB or change manager reviews the emergency change after the immediate crisis is resolved.

Conclusion

Virima 6.1.1 delivers ITIL v4-compliant change management backed by live CMDB data, ViVID Service Maps, automated stakeholder workflows, and Discovery-based configuration verification. Every major capability — from impact analysis to risk register integration — connects to the same CMDB that powers Virima’s IT asset management, ITOM, and service mapping modules.

Schedule a Demo at virima.com to see Virima change management in action.

This article is based on Virima 6.1.1 capabilities. Feature availability may vary by deployment configuration.