<<Project Name>>

Current State Infrastructure

Customer Name

Directions for using template:

Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this template. Then delete the Guidance and replace the placeholder within <<Begin text here>> with your response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used.

Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size:

Heading 1 – Arial Bold 16 font
Heading 2 – Arial Bold Italic 14 font
Heading 3 – Arial Bold 13 font
Heading 3 – Arial Bold Italic 12 font

You may elect to indent sections for readability.

Author
Author Position
Date

Version: 1.0

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Microsoft and Visual Basic are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.

Revision & Sign-off Sheet

Change Record

Date	Author	Version	Change Reference

Reviewers

Name	Version Approved	Position	Date

Distribution

Name	Position

Document Properties

Item	Details
Document Title	Current State Infrastructure Assessment
Author
Creation Date
Last Updated

Description: The Current State Infrastructure Report, begun during envisioning, is documentation of an accurate description of the environment and its corresponding variables in which the solution will reside. The document provides information about all the legacy systems in place that may affect and/or be accounted for in the solution design. This is a “living document” as its contents are typically elements that are constantly under change, thus making the data collection and upkeep a priority for the team.

Justification: An accurate understanding of the current state of the existing infrastructure increases the probability of successful solution planning, development, and deployment. Comprehensive information about the environment, available up front in the project, can facilitate minimizing changes late in the development stage. This will prevent any significant cost increases due to re-design or risks.

{Team Role Primary: The Release Management role is the gateway to the operations team, thus all current infrastructure being managed by the customer operations can be assessed and documented via this role. There may be architect and development input required which the release lead can acquire as necessary.

Team Role Secondary: The Program Management role is required to provide support in facilitating the gathering of the content for the assessment. Typically Program Management handles this document’s initiation by lining up the appropriate customer staff who are knowledgeable in the topics needed to complete the document content. Then, as a lead is assigned to the Release Management role, that person takes primary responsibility for content update and delivery.}]

Summary

[Description: Provide an overall summary of the contents of this document. Be sure to include highlights on missing, high risk, or poorly documented sections that require immediate attention.

Justification: Some project participants may need to know only the highlights of the assessment, and summarizing creates that user view. It also enables the full reader to know the essence of the document before they examine the details.]

Objectives

[Description: The Objectives section describes the key objectives of the infrastructure assessment process.

Justification: Identifying the objectives signals that the assessment process has occurred within strategic parameters established before the assessment began.]

Project Scope

[Description: The Project Scope section is a restatement of the project’s scope with a specific slant toward how it relates to the current infrastructure. For example, if a complete network design is considered out of scope, but the current state assessment finds areas where the current network design will affect the solution, then restate the scope to set expectations.]

Recommendation

[Description: The Recommendation section identifies any data from the assessment elements collected so far that may cause specific implications to the proposed solution. It should also suggest possible ways to resolve those issues.

Justification: This information may significantly impact the project and should be documented and transmitted formally.]

Site Visits

[Description: The Site Visits section provides a brief overview of site visits, how and what information was gathered. It should also identify what information the team still needs or where difficulties exist in obtaining the appropriate information.]

Data Sufficiency Status

[Description: The Data Sufficiency Status section describes for each key infrastructure item (hardware information, network data, etc.) 1) if the team does not have sufficient information and this is causing risk, 2) if the team has complete information, or 3) if the team is making progress toward collecting sufficient information. It should also make clear which information has been recently updated.

Justification: This status enables the team to understand where it is in the collection process and generate plans for completion.]

Hardware Groups

[Description: The Hardware Groups section lists and characterizes (see previous section on status) any groups of commonly configured hardware. Examples might include:

Inventories

[Description: The Inventories section provides the inventory for each hardware group. Include such things as:

This section should also characterize this inventory as described in the status section.]

Technology Architecture

[Description: The Technology Architecture section provides details on the following architecture items to the appropriate level that enables the team to make appropriate solution design decisions. Include any graphs or maps useful for these areas.]

Network Architectures

Windows Domain Architectures

Windows Security

Network Infrastructure Services

Information Infrastructure and Services

Current System Usage

[Description: The Current System Usage section delineates the system usage as it pertains to the proposed solution – examples include network and domain patterns upon logon by users in the AM.]

Usage Metrics

[Description: The Usage Metrics section identifies which elements within the current system are measured and how these items are measured.]

Future State System Usage Analysis

[Description: The Future State System Usage Analysis section delineates the system usage as it pertains to any upcoming changes to patterns that may occur.]

Projected Metrics

[Description: The Projected Metrics section identifies which elements within the future system must be measured that are not currently, and how will these items be measured.]

Operating Environment Analysis

[Description: The Operating Environment Analysis section describes the operating environment, noting such variables as:

n Whether the computing environment is “friendly,” like an office environment, or “hostile,” like a factory floor.]

SLAs

[Description: The SLAs section describes any Service Level Agreements currently in-place, who these agreements are with (internal, vendor, etc), and what affects or constraints these may have on the solution.]

Security Analysis

[Description: The Security Analysis section describes the in-place security standards that have been assessed, any security issues that need attention, and any planned changes for the future which may affect the solution or the environment (including users) in which it will operate.]

Current State

[Description: The Current State section provides details on the current security standards and procedures.]

Future State Requirements

[Description: The Future State Requirements section describes any security standards and procedures that are planned that may have an impact on the solution.]