Start with a concrete object
Select the server, application or scope to be changed. Gather the characteristics useful for the preparation and check that the information matches the known state of your environment.
Examine the links between layers
An application may run on a logical server that is itself linked to physical infrastructure. The recorded flows and relationships let you place this component in its context.
Share the points to confirm
Use the map to prepare discussions with the teams concerned. A missing relationship does not mean that no dependency exists: links must be confirmed and completed before the decision.
Update after the change
Include updating the repository in the project tasks. Check the components created, changed or removed and the associated relationships, to keep a useful base for the next change.
Explore Rayonnement and simulate an outage
In Studio, Rayonnement explores dependencies beyond direct relationships. Impact & PRA lets you simulate the loss of a site, a rack or a server to identify the affected processes and the known single points of failure.