Table of Contents

Management Summary

  1. Introduction
    1. Purpose
    2. Background
    3. References
    4. Methodology
  2. General Information
    1. Current Systems Processes
    2. Project Objectives
    3. Project Scope
    4. Issues
    5. Business Requirements
    6. Assumptions and Constraints
  3. Alternatives Considered
    1. Background
    2. Project Implementation
  4. Comparison of Alternatives
  5. Recommendations and Conclusions
  6. Approval/Concurrence
  7. Glossary



Feasibility Assessment Instructions

The Feasibility Assessment document is an optional first step in the Life Cycle process. It allows either 1) a SPA initiated set of capabilities to be scoped and alternatives with preliminary cost estimates to be developed, or 2) an unplanned requirement scoped alternatives developed and preliminary costing information to be developed. The sections include a Management Summary, Introduction, General Information, Alternatives Considered, Comparison of Alternatives, Recommendations and Conclusions, Approvals/Concurrence and a Glossary.

Management Summary

The management summary should include a description of the proposed project and reference the SC strategic plan and business model requirement being satisfied by the proposed effort. It should also summarize the results of the assessment and identify the best recommendation to proceed to the project planning stage.

  1. Introduction

  2. The introduction should cover purpose, project history, references and methodology used to produce the study.

    1. Purpose

      Describe the business requirement and reference the business model functions satisfied by the proposed project.
    2. Background
    1. References
    2. Provide all references to SC and DOE documents used in developing the feasibility assessment.

    3. Methodology

Identify the methodology used to develop this assessment.

  1. General Information
    1. Current Systems and Processes
    2. Provide a description of the SC organization/business environment currently serviced by existing systems and/or technology solutions to include current operations, physical environment and user-organizations serviced.

    3. Project Objectives
    4. Identify the business objectives to be addressed by the proposed project.

    5. Project Scope
    6. Provide a complete project scope identifying the technical boundaries of the project with respect to processes, products and/or benefits to be realized by the project.

    7. Issues
    8. Identify all issues that may impact the development, implementation and operations of the proposed project.

    9. Business Requirements
    10. Identify strategic level requirements of the proposed project.

    11. Assumptions and Constraints

    Identify all assumptions and constraints that may impact the development, implementation and operations of the proposed project.

  2. Alternatives Considered
  3. Identify all alternatives for the proposed project

    1. Background
    2. Describe research performed to develop alternatives.

    3. Project Implementation Alternatives

    Identify hardware, software and technology components necessary for each proposed alternative and review the economic feasibility of the proposed technology.


  4. Comparison of Alternatives
  5. Comparison of Alternatives
  6. Provide a complete comparison of each alternative option including costs, benefits and impacts to the organization.

  7. Recommendations and Conclusions
  8. Prepare recommendation and requirement action items to initiate the project.

  9. Approval/Concurrence
  10. Include an appropriate SC concurrence/approval section

  11. Glossary

Provide a glossary of all technical terminology used within the document.


Use appendices to document any specific alternative vendor information.