Free Templates

Current State Assessment Template

0. Document Information

0.1 Document History

1. Introduction

1.1 Purpose

The purpose of this document is to provide an understanding of current xxx infrastructure. The level of detail should not exceed that of a high-level design.

  1. In-Scope Details
  2. Platform/Infrastructure landscape high level diagram(s) summarising current infrastructure architecture and technology used for software and services linked to xxx (i.e. on-premises MS Windows, MS Azure, M365, AWS etc)
  3. Identify technical debt and risks such as equipment, services and or software that has is reaching end of life (it will no longer be supported)
  4. List of current issues and pain points
  5. Regulatory and compliance requirements
  6. Policies and standards
  7. Roles and responsibilities
  8. Delivery partners and their roles (ATOS, somethings, something)
  9. Usage persona’s (i.e. internal user, external users, suppliers, developer, operations, security etc)

1.3 Out of scope details

  • Inventory of technology such as identifying number of servers
  • Capacity planning

2. Policies and requirements

2.1 Regulatory and compliance requirements

2.2 Policies and standards

3. Infrastructure Landscape Overview

Platform/Infrastructure landscape high level diagram(s) summarising current infrastructure architecture and technology used for software and services linked to xxx (i.e. on-premises MS Windows, MS Azure, M365, AWS, Google etc)

3.1 Service component 1

3.1.1 High level Overview of the service

Provide an overview of the service, showing its boundaries, scope and integration elements

3.1.2 Role of Delivery Partners

Delivery partners and their roles (ATOS, something, something).

3.1.3 Stakeholders

Identify product owner and various stakeholders associated with this service

3.1.4 Personas

Usage persona’s (i.e. internal user, external users, suppliers, developer, operations, security etc)

3.1.4 Licencing and costs

Identify licencing, support and maintenance costs

3.2 Service component 2

3.3 Service component 3

4. Risk, Technical Debt Assessment and pain points

Identify technical debt and risks such as equipment, services and or software that has is reaching end of life (it will no longer be supported). Provide a list of current issues and pain points

4.1 Infrastructure Risks

4.2 Technical Debt

4.3 Single Points of Failure

4.4 End-of-Life Technologies

4.5 Security Risks

4.6 List of current issues and pain points

5. Appendices

A Referenced Documents

B Glossary of Terms and Acronyms

C System Dependency Maps

D Stakeholder List

E Supporting Data