18
Mapped service components
Operational Context
Understand what a service depends on before you change it or troubleshoot it.
The asset and dependency view is now route-native in `apps/web`, connecting services to systems, owners, vendors, and shared components for better incident, change, and problem interpretation.
6
Critical services
3
Shared dependency hotspots
100%
Tracked assets with named owner
Service Dependency Register
A dependency model becomes useful when it helps explain service risk, change impact, and incident scope.
| Service | Depends On | Owner | Risk Note |
|---|---|---|---|
| Remote access service | Gateway cluster, identity service, vendor support channel | Infrastructure lead | Vendor and gateway are shared choke points during high-severity incidents |
| Leadership dashboard reporting | Public data refresh jobs, reporting model, source system feed | Data / reporting owner | Source feed delays can affect both internal reporting and public updates |
| Energy Strategy publishing | CMS platform, content owner approvals, publish workflow | Web platform owner | Approval and content readiness often drive timing more than the publish action itself |
| Teams workspace governance | Workspace ownership rules, manager approvals, retention settings | Collaboration owner | Governance drift creates recurring cleanup and access churn |