The purpose of this step is to facilitate communication with stakeholders and benchmark applications. It ensures a comprehensive understanding of the technology stack and its relationship to vital services.
Note: This step of the methodology is optional. It is recommended for teams that need a deeper understanding of infrastructure dependencies.
The mapping is based on a list of services defined by IT Group Production. These services form the "Core IT Infrastructure & Production" Vital Service.
Not all services are meant to remain operational in a worst-case scenario. The mapping helps identify if an application requires a service that might be unavailable during a disaster or outage.
The following table lists the seven infrastructure categories and their associated services:
| Category | Services |
|---|---|
| Network Services | Micro-segmentation, External Internet Access, Datacentre Interconnections, Domain Name Services (incl. DHCP), Remote Access Services (AnyConnect) |
| Security Services | Authentication (incl. SSO, Secure ID), Active Directory, Password Vault, Mainframe Security (IBM MFA) |
| Data Services | DB Storage Mainframe, NWK Storage NAS / SAN, Back-Up & Archive Services |
| Collaborative Services | Desktop Infrastructure (SCCM), Messaging Collaboration (email exchange), Office 365 (for Vital documents) |
| Operations Services | Scheduler Open (Linux, AIX, Windows), Scheduler Mainframe, DevOps Toolchains, Robotic |
| Compute Services | Virtualisation Open, Virtualisation Mainframe |
| Communication Services | Mainframe Transactional (GOAL, WAM, IMS, CICS...), Messaging Open (MQ), Messaging Mainframe (MQ), File Transfer Open (CFT, XFB), File Transfer Mainframe (CFT), API Platform |
Each application is analysed to identify which of these infrastructure services it relies on. The results distinguish between critical services (absolutely required for the application to function) and important services (relied upon but not immediately fatal to the core function if unavailable).
The following diagram illustrates the mapping for the MTM Application against the Core IT Infrastructure & Production Services.
Each application is analysed to identify dependencies and interconnections. This helps in infrastructure optimisation, capacity planning, and resilience.
The mapping summarises infrastructure services required by vital applications, distinguishing between critical and important services. For worst-case scenario planning, critical services must be preserved, while important services may be temporarily discontinued.