EPLC_AOA_v . .doc

<Project Name> Operational Analysis Version: <1.0>

Food and Drug Administration

<Project Name & Release Version #> Enterprise Performance LifeCycle Annual Operational Analysis

Document Version Number: <1.0> Document Version Date: <mm/dd/yyyy> Notes to the Author

[This document is a template of an Annual Operational Analysis document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project.

Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.

Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to a particular project.

Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

When using this template for your project document, it is recommended that you follow these steps:

Replace all text enclosed in angle brackets (e.g.,, <Project Name>) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected):

a. Select File>Properties>Summary and fill in the Title field with the Document Name and the Subject field with the Project Name.

b. Select File>Properties>Custom and fill in the Last Modified, Status, and Version fields with the appropriate information for this document.

c. After you click OK to close the dialog box, update the fields throughout the document with these values by selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update an individual field by clicking on it and pressing F9. This must be done separately for Headers and Footers.

2. Modify boilerplate text as appropriate to the specific project.

3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.

4. To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”

5. Before submission of the first draft of this document, delete this “Notes to the Author” page and all instructions to the author, which appear throughout the document as blue italicized text enclosed in square brackets.]

VERSION HISTORY

[Provide information on how the development and distribution of the Annual Operational Analysis was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.]

By Revision

Date Approved

By Approval

Date Description of and

Reason for

Change

Table of Contents 61.0

INVESTMENT OVERVIEW

62.0

STRATEGIC AND BUSINESS RESULTS

63.0

USER/CUSTOMER ASSESSMENT

74.0

PERFORMANCE ASSESSMENT

85.0

FINANCIAL PERFORMANCE

86.0

INNOVATION

87.0

ENTERPRISE ARCHITECTURE

88.0

SECURITY AND PRIVACY

89.0

RECOMMENDATIONS

89.1

INVESTMENT MANAGER RECOMMENDATIONS

1.0 INVESTMENT OVERVIEW

Name of System or Application

Agency/Office

Program/Business Function Supported by this Investment

Key Personnel Participating in this Review (IPT-Stakeholders)

System Owner Signature/Title

2.0 STRATEGIC AND BUSINESS RESULTS

[Provide a brief summary describing the asset and a description of the business processes that the investment supports. Description should include an explanation of how the investment is continuing to meet each OPDIV and Department mission or strategic goals and how it supports the Department’s e-Government Strategy.]

3.0 USER/CUSTOMER ASSESSMENT

[Briefly describe the investment's users and the process (e.g., surveys, user group meetings, customer focus groups, etc.) used to assess user or customer satisfaction. Summarize the results of surveys or other user or customer inputs, and usage trends. Is the existing system providing customers the needed functionality and performance? Based on your user or customer inputs, is actual performance consistent with user or customer expectations, or do the current performance goals reflect current user or customer functional or performance requirements? Has the investment exceeded expectations, and the performance measures need to be re-baselined? Discuss how your project addresses the following operational indicators: efficiency, effectiveness, maintainability, productivity, security, availability, reliability, energy usage.]

[Graph can be used to show summary of customer satisfaction]

4.0 PERFORMANCE ASSESSMENT

[For the prior and current fiscal year, provide the Performance Goals and Measures table(s) with prior year actual results and current year interim results, if known. If the project collects, manages or reports to other performance goals and measures, add rows to record those goals and measures.] Fiscal Year

Measurement Area

Measurement Category

Measurement Indicator

Baseline

Planned Improvements to the Baseline

Actual Results

[Also provide information regarding statistics for up-time, the number of defects opened, number of enhancements mad, and problems reported.]

5.0 FINANCIAL PERFORMANCE

[A. Cost- Describe specific periodic budget reviews including who participates, the process for how, how frequently, etc.

B. Schedule- Describe specific periodic schedule status reviews including who participates, the process for how, how frequently, etc. For example: “The matrix annual operating plan is used to track key milestones….” Were milestones met? If yes, what? If not, why?]

6.0 INNOVATION

[Describe the new innovation and initiatives that anticipate changing customer needs. Sample language follows, which can be used and modified where applicable: The following investment is being implemented to address future challenges, better meet customer needs, make better use of technology, and lower operation costs.]

7.0 ENTERPRISE ARCHITECTURE

[In this section, describe how this investment is consistent with Enterprise Architecture. Include information about “As-Is” and “To-Be” architecture. For example: The system was evaluated against <OPDIV> Enterprise “As-Is” and “To-Be” Architectures. It has been determined that this system is/is not included in the “As-Is” architecture. It has also been determined that this system supports/does not support the “To-Be” (target) architecture.]

8.0 SECURITY AND PRIVACY

[In this section, describe how this investment pursues the remediation and resolution of known system issues.]

9.0 RECOMMENDATIONS

[Justify if the existing system should continue in operation as is, be enhanced, or terminated. If the system is to be enhanced or terminated, summarize the actions to be taken this fiscal year]

9.1 INVESTMENT MANAGER RECOMMENDATIONS

Investment [is ___ is not __] meeting its performance goals as identified within the scope of the operational analysis

___ Investment should remain in steady state or mixed life cycle for foreseeable future

___ Investment team should commence planning for DME (Development, Modernization, & Enhancement) in order to ensure continued investment viability

___ Operational Analysis results suggest that investment should be discussed at IT-Investment Review Board

___ Operational Analysis results suggest that IT-Investment Review Board does not need to discuss this investment

IT Review Board Recommendation and Signature:

Signature:

Date:

[mm/dd/yyyy] Print Name:

Title:

Role:

Project Manager

Project Manager:

Signature:

Date:

[mm/dd/yyyy] Print Name:

Title:

Role:

Business Owner

APPENDIX A: KEY TERMS

[Insert terms and definitions used in this document. Add rows to the table as necessary.

The following table provides definitions for terms relevant to this document.

Template Version 2.1 (Last Modified on Aug. 7, 2009)

PAGE

Revision Date:

Operational Analysis - DRAFT