You can use an Availability Plan Document to describe how your system will be made available by capturing the hardware and software aspects of your solution setup.

Use an Availability Plan Document to:

  • Ensure that your system responds correctly to requests, is adequately maintained and communicates with interfacing components, such as network and servers.
  • Measure how often your data and applications are ready to be accessed when needed.
  • Capture areas such as training requirements for System Administrators, processes for performing maintenance tasks and itemizing hardware, software and other components.

Table of Contents

1 Introduction
1.1 Overview
1.2 Background
1.3 Justification
1.4 Document overview
1.5 Identification
1.6 Goals, objectives & rationale
1.7 Points of contact
2 Roles and Responsibilities
3 Current State Assessment
3.1 Processes
3.2 Maintenance
3.3 Inventory
4 Redundancy Strategy
5 Hardware
5.1 Commodity hardware
5.2 Spares
5.3 Standby
5.4 Preparation
5.5 Fault Tolerant Components
5.6 Backup
6 Software
6.1 System integration testing
6.2 Training
6.3 Software deployment
6.4 Software Support & Monitoring Plans
6.5 Application isolation
7 Appendix A: References
8 Appendix B: Acronyms, Abbreviations & Definitions

If you want some perspective on how you or your company needs to enhance their Sales/Client Management Capabilities, please email me (Shubhanjan Saha) at This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Comments:

blog comments powered by Disqus