eGovernment ProgrameDeployment Business CaseExecutive SummaryFebruary 5

Slide 1:eGovernment Program eDeployment Business Case Executive Summary February 6, 2011

Slide 2:Agenda

High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again.

Slide 3:Business Case Team Roster

The following people assisted in the development of this business case:

Slide 4:Business Case Team Roster (Continued)

The following people assisted in the development of this business case:

Slide 5:Our Approach

For the past 90 days, cross-Agency teams have been working to define the eDeployment business case. The business case includes all sections required by the CPIC process The process the teams followed to complete the business case is as follows: Form cross-Agency teams Definebusinessrequirements Finalizebusinessrequirementsfrom allAgencies Review,modify, anddeliver finalbusinesscase Review anditeratebusinessrequirements Completeremainingbusinesscasedocuments 1. Met with Agencykey contactsand receivednames ofparticipants. 2. Facilitated breakoutsessions withfunctional teams todefine Agencybusinessrequirements. 3. After vetting withteams and withother Agencystaff, therequirementswere completed. 4. Driven by businessrequirements,teams completedremainingdocuments.(included demos,visiting SME�s, understanding bestpractices and surveys) 5. Business caseready for formalreview Completeoveralltechnologyapproach

Slide 6:Our Approach

The following are the major sections of the business case: Overview Introduction Executive Summary Concept of Operations Business Profile Performance Measures Functional Requirements Risk Profile Risk Management Plan Early Adopters Plan Financial Profile Cost Benefit and Alternatives Analysis Technological Profile Technical Requirements Security Plan Telecommunications Plan Technical Architecture Plan Management and Planning Profile Project Plan Acquisition Plan These documents are posted on the USDA eGovernment website. http://www.egov.usda.gov/resources/teamspace/enablers/selectbc.html

Slide 7:Why is eDeployment Needed?

eDeployment is the foundation that will help USDA achieve the goals and objectives outlined in the eGovernment strategy. Improves the quality and consistency of information across the enterprise. Increases the availability and accessibility of information for citizens, public and private organizations, and employees. � Improves internal efficiency by automating and streamlining business processes. Enhances collaboration with citizens, public and private organizations, and employees to develop and deliver the USDA mission. Recognizes information as a strategic resource by defining standards for information identification and decreasing search and retrieval time for current, quality information.� High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again.

Slide 8:What is eDeployment?

Web Content Management A Web Content Management solution will aid the creation, review, delivery, and maintenance of agency-defined information. Document Management A Document Management solution will enable the sharing and managing of documents and other electronic assets across USDA (according to records retention schedules.) Web Presence Web Presence will provide standards and guidelines to improve the �look and feel� and usability of Web pages and Web-based applications across USDA. Portal Services Portals will provide customers, public and private organizations, and USDA employees with integrated access to USDA information and services. Data Management Data Management will provide standards and services for data design and implementation issues to facilitate cross-Agency data sharing and reuse. eDeployment is a fusion of multiple enabling capabilities that will support delivery of USDA information and services. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again.

Slide 9:Current Environment

Existing capabilities vary by Agency and often reflect duplicative and redundant business and technical processes. Most notably, there is a lack of consistency and information sharing across the enterprise. Some Agencies are currently evaluating individual Web Content Management, Document Management, and Data Management solutions as well as separate Web Presence and Portal initiatives to meet their distinct needs. Workflow processes are conducted manually and there is no means to drive content and documents throughout their lifecycle, from creation to maintenance to archiving. Agency documents are primarily static, unstructured content that is not interactive with Web applications, databases, and multiple Web delivery mechanisms. Agencies have dissimilar technical architectures, which pose a challenge to interoperability. �Stove-pipe" delivery systems that currently exist are organization bound; content creators from subject matter expertise at any level are not able to contribute to the content that will be delivered to users. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again.

Slide 10:Business Requirements

Key Web Content Management and Document Management requirements identified by Agencies include: Enable designated authors to create Web content and documents utilizing user-friendly tools and standard templates. Provide an automated workflow capability to mirror the review process of information that is currently performed manually. � Enforce the inclusion of standard metadata, headers, footers, etc. for a file or online content. Enforcing these standards enables information to be organized, re-used, and located. Manage how information is �published� once it has been created and reviewed to ensure information integrity. Define and support standards for the maintenance of information, including expiration of outdated information, and the appropriate classification of information.� �Provide the ability to archive and delete information according to file plans and documented records retention schedules . High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again.

Slide 11:Business Requirements (Continued)

Key Portal Services requirements identified by Agencies include: Provide a comprehensive information architecture (organization and classification of information) to improve access to information. �� Enable a Web site or application to become a primary communication mechanism inside and outside of USDA. Provide a personalized, customizable view of information. Provide fast and accurate information retrieval capabilities. Support the ability to deliver information to multiple devices, including PDA, cell phone, etc. Provide standards and guidelines that ensure a consistent �look and feel� and navigational structure in USDA�s Web pages and Web-based applications. Key Web Presence requirements identified by Agencies include: High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again.

Slide 12:Alternatives Analyzed

Maintain the existing environment � �Status Quo� Grants the most flexibility by allowing Agencies to choose their own eDeployment solution and eliminates the need to work through culture barriers; and USDA Agencies spend millions in duplicative monies to design, build, deploy, and operate their own solutions and do not benefit from economies of scale pricing. Integrated enterprise solutions in a distributed environment Leverages existing hardware, network, and personnel resources to optimally deliver enterprise-wide services from multiple hosting facilities; Reduces integration costs and facilitates sharing of information across the enterprise; and Provides the greatest processing power to ensure optimal response time and ease of integration. Integrated enterprise solutions in a centralized environment Delivers enterprise-wide services from a centralized hosting facility; Provides an effective option if audiences are concentrated in a small geographic region and external systems that need to be integrated are few and centrally located; and Provides the same benefits as distributed environment, but the processing power would not be as great and integration would be more complex. Three implementation alternatives were considered for eDeployment.

Slide 13:Recommendation: Integrated Enterprise Solutions in a Distributed Environment

Distributed application components and data/content repositories will enable USDA to deliver robust, enterprise-wide solutions while leveraging existing technology investments and resources. Supports the ability to leverage existing USDA investments. Leverages NITC, other USDA hosting facilities, and potential third-party hosting centers; Promotes reuse of existing USDA hardware, software, network, and personnel resources; and Utilizes existing telecommunications infrastructure and future UTN plans to reduce overall telecommunications impact. Reduces the complexity of system implementation. Allows users to be brought on to the solution in the shortest amount of time. Houses enterprise solutions in the same hosting facilities as legacy systems to simplify integration. Ensures optimal performance for the end user. Provides economies of scale for software license purchases. USDADataCenter USDADataCenter USDADataCenter = Agency accessingenterprise solutions = Enterprise solutionsare housed in USDAdata centers to beleveraged by agenciesand strategic initiatives High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again. High energy Welcome. Get jazzed. Good things are happening: EITIRB meeting tomorrow for 30 minutes exclusively on eGov EC and I will be meeting with DS ideally this week as well but may slip to next week Relatively positive feedback from OMB based on our efforts � only Yellow Thanks for efforts to date. Time to roll up sleeves again.

Slide 14:Benefits

Strategic Benefits Enterprise-wide aggregation, management, and storage of content increase the amount of higher-quality information that is available to citizens. USDA employees� time saved equates to improved program and service delivery for customers. Financial Benefits Reduces the amount of time spent searching for documents and information and responding to FOIA requests. The acquisition of highly extensible and scalable enterprise-wide solutions decreases the number of redundant purchases across USDA and provides for economies of scale. Reduces paper costs related to the purchasing, printing, storing, and disposal of paper assets by accessing, storing, and managing content and documents electronically. Operational Benefits Standardized business and workflow processes instill greater accountability and improve access to more current, accurate, relevant, and organized products, services, information, and data. Web-based applications and services can be deployed more quickly. Enterprise solutions will reap financial benefits while simultaneously improving the ability for USDA to deliver online information and services.

Slide 15:Benefits

Shapes public opinions about USDA�s championing of eGovernment through an integrated online presence; Promotes increased creation and publishing of Web content that is usable for all citizens, especially those with disabilities; Improves access to more current, accurate, relevant, and organized products, services, information, and data; Enables citizens to easily search for and quickly find relevant and timely content via integration with a robust USDA taxonomy; Improves USDA compliance with Section 508 standards; and Increases the quality of data distributed across eGovernment initiatives, legacy systems, and other systems with mission critical functionality . These enterprise-wide capabilities also provide many intangible benefits.

Slide 16:Cost/Benefit Analysis

The eGovernment team followed a process in generating cost alternatives to implement and rollout the eDeployment solutions Generate costs based on functional and technical requirements Identify levers to generate alternatives Map levers to identified project risks Assess cost impact of each lever Assess qualitative impact of each lever Generate cost alternatives Cost Benefit Process Core Capabilities(Includes portals, document management, content management, EAI, search engine, common data/content repository) Pre-Implementation Tasks Vendor assessment and procurement Definition of physical architecture Implementation Design, Installation and custom development Testing Rollout usda.gov Department Portal Design, build, test, rollout Early-Adopter Support Available full-time technical expertise to assist agencies to come on-board Project Management Major Deliverables Rank levers based on qualitative impact

Slide 17:Cost/Benefit Analysis

Based on the functional and technical requirements gathered for eDeployment from all agencies and staff offices, the following are the costs: SCENARIO 1 - COST/BENEFIT BREAKDOWN Scenario 1 - Assumptions All major technology capabilities and standards implemented in Year 1 Document management, web-content management, web presence, portal services, content/data aggregation, enterprise search, Electronic Application Integration (eAI) Usage tracking and reporting delivered in Year 1 7,000 USDA employees use portal in Year 1 (unlimited number of external users) 500 developers in Year 1 using web content management 5,000 developers/users using document management in Year 1 Flexibility in choosing software and hardware is allowed: dictated by functional and technical requirements only Assumes the development of prototypes to �field-test� the newly formed web presence standards The technical architecture designed and priced is fully redundant to ensure minimal down-time Support of early adopter roll-out (FY03-FY04) Note: Risk cost not included. Cost Benefit Analysis includes detailed analysis. Labor costs to support agencies in adopting solutions included in total costs. Labor costs include project management Total costs include security costs Benefits include cost avoidance Productivity gains Cost savings Quality gains

Slide 20:Cost/Benefit Analysis

Slide 21:Cost/Benefit Analysis

The following cost/benefit scenario eliminates all cost levers that have a �low� qualitative impact: SCENARIO 2 - COST/BENEFIT BREAKDOWN COMPROMISES Reduce number of database designers to support enabler and strategic initiatives by 50% (2 full time resources) Redirect internal resources for use in implementation Use single vendor for Document and Web Content Management Note: Risk cost not included. Cost Benefit Analysis includes detailed analysis. Labor costs to support agencies in adopting solutions included in total costs. Labor costs include project management Total costs include security costs Benefits include cost avoidance Productivity gains Cost savings Quality gains

Slide 22:Cost/Benefit Analysis

This cost/benefit scenario eliminates all cost levers that have a �low� and �medium� qualitative impact: SCENARIO 3 - COST/BENEFIT BREAKDOWN COMPROMISES Internal access to the portal is limited (5000 users) Number of early-adopters for web content management is limited (150 users) Number of early adopters is limited for document management (500 users) No hardware redundancy resulting in higher risk of system downtime Reduce number of database designers to support enabler and strategic initiatives by 50% (2 full time resources) Redirect internal resources for use in implementation Use single vendor for Document and Web Content Management External content not purchased in Year 1 Note: Risk cost not included. Cost Benefit Analysis includes detailed analysis. Labor costs to support agencies in adopting solutions included in total costs. Labor costs include project management Total costs include security costs Benefits include cost avoidance Productivity gains Cost savings Quality gains

Slide 23:Cost/Benefit Analysis

This cost/benefit scenario eliminates all cost levers that have a �low�,�medium� and �high� qualitative impact: SCENARIO 4 - COST/BENEFIT BREAKDOWN COMPROMISES Searching for content across the enterprise not possible Internal access to the portal is limited (5000 users) Number of early-adopters for web content management is limited (150 users) Number of early adopters is limited for document management (500 users) No hardware redundancy resulting in higher risk of system downtime Reduce number of database designers to support enabler and strategic initiatives by 50% (2 full time resources) Redirect internal resources for use in implementation Use single vendor for Document and Web Content Management External content not purchased in Year 1 Delayed delivery of usage tracking and reporting by one year Share existing hardware with other current solutions Use open source software to save licensing costs Eliminate web presence prototypes Note: Risk cost not included. Cost Benefit Analysis includes detailed analysis. Labor costs to support agencies in adopting solutions included in total costs. Labor costs include project management Total costs include security costs Benefits include cost avoidance Productivity gains Cost savings Quality gains

Slide 24:Timeline and Milestones

Enterprise-wide implementation of eDeployment will be accomplished in a phased approach.

Slide 25:Timeline and Milestones

USDA Agencies will adopt eDeployment solutions over the next 1-5 fiscal years

Slide 26:Proposed Early Adopters

Although eDeployment provides an integrated solution, some Agencies may choose to only utilize certain capabilities of the solution. The following chart summarizes the Agencies that are interested in being early adopters of the eDeployment solution: A request was sent to all of the Agencies to determine interest in being an early adopter of the eDeployment solution.

Slide 27:Next Steps

The Next Steps to begin the eDeployment initiative are: USDA Approval and Funding Incorporate review comments into eDeployment business case; and Secure funding for eDeployment project (FY03, FY04, and FY05). OMB Approval Seek approval from OMB for FY05 budget cycle. Project Establishment and Kick Off Select eDeployment project manager(s); and Identify and staff project team to support implementation. Conduct Pre-Implementation Tasks Refine application requirements; Develop request for proposal (RFP); Conduct vendor analysis and select vendors; and Begin design of development and production environments.