Change impact analysis without a CMDB takes 4+ hours of manual cross-checking across emails, spreadsheets and tribal knowledge — and still misses hidden dependencies. A visual dependency map cuts this to 10 minutes by traversing the CI graph instantly.

Without dependency data, change management is blind: changes take down services nobody knew were connected, and incidents take hours longer to diagnose because nobody knows the blast radius.

Utilyx delivers a CMDB lite — enough structure to map services and run impact analysis, without the multi-year implementation — as an executable no-code decision tree.

The workflow is structured as a decision tree with 4 main branches (CI Registration, Dependency Mapping, Impact Analysis, Reporting) triggered on every change request or CI update, with parallel confirmation sub-branches and 7 steps end-to-end. Every step is executed by a named actor (IT Architect, AI Copilot, CAB, Change Manager) and every action is appended to the timeline_ci audit subtable.

• Step 1 (Start — IT Architect): configuration items are registered via sql-query with fields ci_id, ci_name, ci_type (server / application / network_device / database), owner, location, criticality (low / medium / high), environment (prod / preprod / dev) — validated by the workflow.

• Step 2 (Dependency mapping — AI Copilot): the Copilot suggests dependencies based on discovery signals (network flows, shared storage, app config) and the tree splits — Branch A (auto-suggested, confidence > 80%): auto-link pending architect confirmation; Branch B (low confidence): manual link creation by the architect.

• Step 3 (Architect confirmation): the architect confirms or edits each suggested link, assigning relationship type (depends_on / hosts / connects_to / uses_service) — written via sql-query to the ci_dependency table.

• Step 4 (Visual service map): the workflow renders a visual service map — nodes for CIs, edges for dependencies — clickable and exportable, kept in sync with the ci_dependency table.

• Step 5 (Impact analysis — triggered by change request): before any change, the Copilot runs an impact analysis traversing the dependency graph and splits — Branch A (blast radius ≤ 2 CIs, low risk): auto-approve; Branch B (blast radius > 2 CIs or high-criticality CI affected): route to CAB review with affected_ci_list and suggested rollback steps.

• Step 6 (usePDF topology report): usePDF generates a service topology report (CI inventory, dependency graph, impact analysis result) for audits and DR planning, in 7 languages.

• Step 7 (useArchive): useArchive stores every CI and dependency change in a versioned audit trail with index fields ci_id, ci_type, change_type, change_date for the legal retention period.

Teams deploying Utilyx's CMDB lite cut change impact analysis from 4+ hours to 10 minutes (graph traversal is instant), reduce incident diagnosis time by 40% (blast radius known on click), prevent 80% of change-induced outages (impact analysis flags risks before CAB), and produce DR plans in hours instead of weeks.

The no-code designer and AI copilot let an IT architect build the CMDB in days, not months — at 70% lower TCO than legacy CMDB suites, with no certified consultants required.