What it shows:
A hub-and-spoke map placing the core application in the centre and surrounding it with the specific IT Service Management (ITSM) and operational domains required to keep it running. It explicitly identifies the peripheral tools (e.g., Active Directory, Splunk, ServiceNow) used for identity management, monitoring, backups, and ticketing.
Why it’s needed:
Day-2 Operations and Support hand-off. This acts as a technical contract with the customer’s IT support staff. It proves that the deployed system is fully integrated into the existing enterprise management landscape and will not become an unmanageable “shadow IT” silo. For InfoSec, it proves that audit logs and system health metrics are actively being routed to the security operations centre.
When to use it:
Highly recommended for SADs and HLDs for any production-grade deployment—whether COTS or Custom Dev—that will be handed over to a dedicated support team, helpdesk, or managed service provider.
When NOT to use it:
Generally best to omit for short-lived Proof of Concepts (PoCs), isolated sandbox R&D environments, or standalone desktop software where the end-user is entirely responsible for their own backups and troubleshooting.
Example:
