STEP 5. ACQUISITION PLAN
Table of Contents
ACQUISITION PLAN INSTRUCTIONS
The Introduction should cover purpose, project history, references and methodology used to produce the project.
Describe the acquisition strategy, inclusive of development and operational factors (e.g., size, speed and capabilities of hardware, software, and/or telecommunications equipment) method(s) of acquisition, selection process, constraints, organizations affected, etc.
These objectives may include factors and rationale to be specified/explained when telecommunications equipment, a piece of hardware, or packaged software must be acquired.
Provide a general description of the system for which the acquisition plan will be implemented.
Provide all references to SC and DOE documents that were used in developing the Acquisition Plan.
This section should describe the development factors, constraints, and selection process by which the equipment is obtained. Note: If the acquisition activity requires multiple components (hardware, software, and/or telecommunications equipment), the strategies, and factors may differ depending on the component. If so, this section should be repeated for each class of component.
2.1 Strategy Development Factors
Identify the factors which must be considered (e.g., size, speed, availability, etc.), and which may impact on the selection of a specific strategy.
Describe the method chosen (credit card, ODC, other contract vehicle) and give the rationale used. Provide schedule information that includes all of the relevant procurement activities, including acquisition lead times and the date when the product must be available and operational.
3.0 HARDWARE SPECIFICATIONS
This section should address hardware compatibility and also describe the type of processing equipment, communications, special equipment, support services and site preparation required.
3.1 Hardware Compatibility
Identify any hardware compatibility issues that may impact the acquisition process. Be specific in terms of types of hardware, vendors, versions, software operating system, etc.
3.2 Required Capabilities and Features
Product name, manufacturer, specific features/attributes (minimum/recommended), and quantity.
Provide a detailed description of the communications equipment (related software), services and facilities required by the system. If applicable, this may include information on existing or proposed networks.
3.4 Special Equipment
Identify any special equipment to be acquired, such as emergency power generators, etc. Specify the date required, possible sources, and estimated costs, as well as the person or staff responsible for overseeing the equipment.
3.5 Support Services
Identify the support services, if applicable, that are required to install and maintain the hardware and software. Such services may include repair, maintenance and training.
3.5 Site Preparation
Identify the sites or facilities, which will require modification or preparation in order to receive the computer or communications equipment, hardware or software. Briefly describe the nature of the required modifications.
4.0 SOFTWARE SPECIFICATIONS
This section should describe the required capabilities, features, and capacity of the software. It should also address hardware compatibility issues, system documentation, training, and maintenance of the system.
4.1 Required Capabilities and Features
List the required capabilities of the software. In most instances, the capabilities should be determined before evaluating the various packages or products. It is suggested that weighing factors be developed to allow separation of mandatory requirements from desirable ones.
Some software becomes less efficient when handling large volumes of data. Estimate as accurately as possible, the volumes of data that will be handled after the system is running for several years.
Identify the manuals that will be necessary for proper installation and operation of the software. Availability, cost, and quality of the manuals are factors that should be considered.
4.4 Training Program
The training of users of software should be considered in the statement of requirements (inclusive of initial and follow up training, and source(s) of training materials. This section covers only training required for IM Team.
4.5 Maintenance Features
Describe the potential vendorís method (support) of handling errors or "bugs" in the software, as well as the Departmentís method, if applicable. Revisions or updates to the software, as well as access to backup copies, should also be considered.
Based on the required capabilities, the statement of requirements should include the potential sources of products. The source information should include, at a minimum, the manufacture and/or distributor names, lead times, and estimated costs.
Briefly describe any hardware or software that is needed to support this product that was not mentioned in Sections 3 and 4 above.
Provide a glossary of all technical terminology and acronyms used within the document.
Include an appropriate SC concurrence/approval section.