Connect inventories to the Enterprise Model to enable impact analysis

Overview

The ultimate purpose of building and connecting enterprise inventories is to enable impact analysis — the ability to answer questions like: if this system is retired, what breaks? If this vendor relationship ends, what services are disrupted? If this regulation changes, what processes and data assets are implicated? These questions are only answerable when the relevant inventory items are connected through well-maintained cross-inventory relationships. Impact analysis without the Enterprise Model is guesswork. Impact analysis with it is evidence-based.

Best Practice

Explicitly design every inventory initiative around the impact analysis use cases it is intended to support. Before designing an inventory’s schema, define the impact questions the inventory will help answer and ensure the schema captures the relationship attributes needed to answer them. Build and test impact analysis queries as part of every inventory deployment. Make impact analysis a first-class, named capability of the Enterprise Model rather than an emergent benefit that may or may not be achievable.

Benefit(s)

An Enterprise Model designed explicitly for impact analysis delivers immediate, tangible organizational value. Change decisions are informed by evidence of their consequences. Risk assessments are grounded in actual dependency data. Regulatory compliance analyses cover all implicated assets rather than only the assets that were known to be relevant. The organization makes better decisions with less rework because the consequences of decisions are understood before they are made rather than discovered after.