Acquisition Plan Template

[Download Sample Chapters]

What is it?
The acquisition plan describes which products, services, hardware, software, infrastructure etc are required for a project.

Who uses it?
IT Managers, Procurement Officers, Test Manager, Project Manager, Development Manager, Documentation Manager, Technical Writers, System Administrator.

When is it used?
The acquisition plan is used to analyze the technical options and the lifecycle plans for development, production, training, and support related items. It also assists IT Managers and Procurement Officers when making procurement decisions; ensuring the availability of funding; providing technical evaluation personnel with data for analyzing and evaluating vendor proposals; ensuring that vendors have adequate information for preparing bids and adequate information on which to base a selection.

Table of Contents

1    Introduction
1.1    Objectives
1.2    Background
1.3    Document Overview
1.4    Acquisition Plan Thresholds
1.5    Risk Assessment
1.6    System Overview
1.7    Scope
1.8    References
1.9    Relationship to Other Plans
1.10    Key Stakeholders
1.11    Points of Contact
1.12    Methodology, Tools, and Techniques
1.13    Policies, Directives and Procedures

2    Acquisition Strategy
2.1    Tasks
2.2    Competition
2.3    Sources
2.4    Selection Procedures
2.5    Subcontract Evaluation
2.6    Budgeting and Funding
2.7    Acquisition Factors
2.7.1    Existing Products
2.7.2    Constraints
2.8    Method of Acquisition
2.9    Acquisition Strategy
2.9.1    Method of Acquisition
2.9.2    Regulations
2.9.3    Funding
2.9.4    Approvals
2.9.5    Lead Time
2.9.6    Procurement
2.10    Considerations

3    Hardware Specifications
3.1    Hardware Compatibility
3.2    Processing Equipment
3.3    Communications
3.4    Special Equipment
3.5    Support Services
3.6    Site Preparation

4    Software Specifications
4.1    Required Capabilities
4.2    Capacity
4.3    Documentation
4.4    Maintenance Features
4.5    Sources
4.6    Impact

5    Project Management
5.1    Master Schedule
5.2    Activity Timeframe
5.3    Risks
5.4    Constraints
5.5    Issues
5.6    Assumptions
5.7    Dependencies
5.8    Sign-Off Criteria

6    Project Team
6.1    Roles and Responsibilities
6.2    Responsibilities
6.3    Software Tools
6.4    Training

7    Appendix A
7.1    Glossary of Terms
7.2    Acronyms and Abbreviations

Page Count: 24

Related Documents