# Presentation: 322625

## eGovernment Working Group Meeting

Chris Niedermayer, USDA eGovernment Executive

- Chris Niedermayer, USDA eGovernment Executive

## Agenda

**Smart Choice Update**
**eGovernment Integrated Reporting**
**eDeployment Business Case**
**Q&A**
**Next Steps and Wrap-up **

**Agenda**

**Notes:**
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.

## Smart Choice Update—Select Business Cases / Implementation Planning Gameboard

**Define Functional (Business) Requirements**
**Educate stakeholders**
**Identify best practice requirements**
**Review best practices with mission areas**
**Gather agency specific and strategic functional requirements**
**Synthesize functional requirements and disseminate for review**
- Finalize functional requirements

**Develop Select-Level Business Case Templates**
**Review CPIC guide**
**Create templates**
**Publish final templates**

**1**

**2**

**September 2002**

**October 2002**

**November 2002**

**Dec 2002**

**Define Technical Requirements**
**Technical Requirements**
**Security Plan**
- Telecom-munications Plan
**Analysis of Existing Systems (if applicable)**
**Technical Architecture Plan**
**eGovernment Plan**

**3**

**Complete Cost/Benefit Analysis**

**Complete Risk Management **

**Complete Implementation**
**Project Planning**

**4**

**Obtain Approval & Submit**
- Complete OMB 300
- Enter in to ITIPS
- Obtain approval from EITIRB
- Submit to OMB

**6**

**Finalize Business Cases**
**Complete executive summary and one page overviews**
- Disseminate to agencies for final review and comments
- Complete final drafts of all sections

**5**

**December 3****rd****, 2002**

- In Progress Events

- Future Events

- Color Key

**Completed Items**

**Smart Choice Update—Select Business Cases / Implementation Planning Gameboard**

## Agenda

**Agenda**

**Welcome**
**Smart Choice Update**
**eGovernment Integrated Reporting**
**eDeployment Business Case**
**Q&A**
**Next Steps and Wrap-up **

**Notes:**
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.

## Continued Progress of USDA’s eGovernment Program

**USDA eGovernment Strategic Plan and most agency eGovernment Tactical Plans completed**
**Business case development underway for Enablers “Smart Choice” initiatives **
**Participation in 19 of the 24 Presidential eGovernment Initiatives**
**Submission of USDA’s GPEA Progress Report**

## Alignment of Enterprise and Agency Planning Efforts Has Never Been More Important

**OCIO must determine how to best help agencies meet requirements and expectations accompanying development of eGovernment solutions **
**OCIO can provide support and feedback on agency plans for developing eGovernment initiatives and meeting key legislative/OMB requirements, including GPEA **

**Alignment of Enterprise and Agency Planning Efforts Has Never Been More Important**

## Old Reporting Process—Separate Collections

**Agency GPEA Submissions**
- Information collected on a PRA transaction basis
- Provide expected date of compliance

**Agency eGovernment Tactical Plans**
- Provide information on current agency eGovernment activities
- Describe agency plans for supporting USDA eGovernment Strategic Plan

- Current agency status and specific project plans for meeting GPEA mandates are not known
- Do not provide information on a form by form basis

**Agency eAuthentication Reporting**
- Identifies GPEA transactions that require an eAuthentication solution
- Created enterprise-wide functional and technical requirements

- Most plans do not include estimated budget data or schedules for completing initiatives
- Some plans do not link to priorities in Agency GPEA Submissions
- Agencies were not asked to prioritize proposed initiatives

**Reports neither linked nor coordinated**

- Data collected so far do not provide sufficient detail to complete the Information Value Chain

**Information Value Chain**

- Does not include agency eAuthentication requirements on a form-by-form basis
- Does not address other agency eAuthentication needs

## Information Value Chain - Concept

**Information Value Chain - Concept**

**Customer/**
**Stakeholder**
**Group**

**Information**
**(OMB Number & Title)**

**Form Number **
**and Title**

**Program (Sub-Program)**

** ****Agency**

- provides

- as required
- by

- which is
- administered by

**IT Investment**

**Software Application/**
**Information System**

- electronically
- enabled by

- is collected
- using

- delivers product/service or ensures compliance

- The linkages reflected in the information value chain are critical to understanding the implications of changing USDA’s business processes.  Agencies will benefit from the information value chain as they set implementation priorities and plan for IT investments.

## Information Value Chain - Reality

**Information Value Chain - Reality**

**Agricultural**
**Producer**

**Information to apply for**
** ****the Conservation **
**Reserve Program**
**(0560-0125)**

**CRP – 1,**
**Conservation Reserve **
**Program Contract**

**Conservation **
**Reserve**
**Program**

** ****FSA**

- provides

- as required
- by

- which is
- administered by

**Conservation Reserve**
**Program System**
**IT Investment**
**(005-49-01-01-03-0000-000)**

**Conservation Reserve**
**Program System**

- supports

- funds

- electronically
- enabled by

- is collected
- using

- delivers cost-share payments

- The linkages reflected in the information value chain are critical to understanding the implications of changing USDA’s business processes.  Agencies will benefit from the information value chain as they set implementation priorities and plan for IT investments.

## New Integrated Reporting Process

**Agency eAuthentication Reporting**

**Agency eGovernment Tactical Plans**

**Agency GPEA Submissions**

**All Key eGovernment Information Collected in a Single Report**

**Information Value Chain**

**Agency eGovernment Report**
- Refined/prioritized list of agency eGovernment initiatives with budget estimates and project milestones
- More detailed description of agency support for Enterprise and Presidential Initiatives
- GPEA reporting on a _**form-by-form**_ basis, including agency status and plans for reaching compliance
- Detailed agency eAuthentication requirements
- Data necessary to develop the Information Value Chain
- Serves as the basis for future quarterly eGovernment reports

**The Continuing Resolution has interrupted plans**
**for a data tool to allow agencies and OCIO **
**to enter reports and track progress**

## How will this report be compiled?

**The report consists of three major components:**
**Completion of spreadsheets that contain key GPEA, eAuthentication and Information Value Chain Information**
**Development of GPEA Compliance Project Plans that describe key milestones of current/planned initiatives to offer electronic options.  **
**Review/revision of Agency eGovernment Tactical Plans based on spreadsheets, GPEA Compliance Project Plans and other OCIO feedback **

**Agency eGovernment Report**

## Benefits to New Integrated Reporting Process

**Reduces and simplifies agency eGovernment reporting requirements**
**Helps OCIO identify where it can best assist agencies and add value**
**Informs development of enterprise-wide solutions **
**Provides OCIO with a more complete picture of agency eGovernment activities and progress on those efforts**
**Promotes the integration of eGovernment and Capital Planning activities**

## What Do I Need to Do?

**Each agency’s eGovernment Working Group member will be contacted in the near future by an eGovernment team member to arrange a meeting.**
**Tasks that you can focus on:**
**Make arrangements for appropriate agency staff to meet between December 9-20**
**Reacquaint yourself with the agency’s GPEA Progress Report submission and the latest version of the Agency eGovernment Tactical Plan**
**Plan to brief your agency eGovernment Steering Committee on the Integrated eGovernment Reporting process and Smart Choice business cases**

## Who Attends the Meeting?

**Agency eGovernment **
**Reporting Meeting**

**OCIO**

**Agency**

- Tactical Plan Coordinator
- GPEA Coordinator
- eAuthentication Team Representative

- Working Group Member
- GPEA Point of Contact
- PRA Coordinator
- Business/Technical Key Contacts
- IT Portfolio Manager
- Forms Manager
- Records Officer

## Roles and Responsibilities

**eGov Team (OCIO):  **Coordinates the Integrated eGovernment Reporting process.  Develops and pre-populates templates.  Crafts feedback and guidance for agency reporting efforts.  Works closely with agency representatives to explain the reporting process and ensure timely responses and accurate data.
**eGovernment Executive Council Member:  **Consults with eGovernment Working Group representatives to ensure they receive the support they need from the various functional areas within each agency.  Assumes responsibility for communicating the overall importance of the Integrated eGovernment Report to Agency Heads and other senior management and removing barriers to the timely completion of the report.
**eGovernment Working Group Member:  **Works with agency contacts to revise Agency eGovernment Tactical Plan.  Continues working with the agency GPEA Point of Contact to communicate the eGovernment “message” to agency staff and explain the integration of GPEA, PRA, capital planning, and records management within the context of the Department’s eGovernment strategy.   Provides leadership and coordination of the agency’s development of the Integrated eGovernment Report in a timely manner.
**GPEA Point of Contact:  **Manages the agency’s initiative to comply with GPEA.  Updates the agency’s GPEA Progress Report with additional information on a form-by-form basis to 1) reflect specific progress toward meeting the GPEA implementation date, 2) identify the connection each PRA transaction has with the agency’s programs and IT systems/investments, and 3) further analyze the agency’s eAuthentication needs.

## Roles and Responsibilities (Continued)

** ****PRA Coordinator:  **Manages the agency’s information collection approvals.  Contributes information to the information value chain to demonstrate the linkage between program areas, PRA transactions, and forms.
**IT Portfolio Manager**:  Coordinates reporting on the agency’s information technology investments.  Works with the Working Group Representative, the GPEA Point of Contact, and appropriate program staff to define the connection between a form or other public transaction, the IT system it supports or feeds, and the related IT investment.
**Forms Manager:  **Manages all forms used by the agency.  Works with the GPEA Point of Contact, the PRA Coordinator, and appropriate program staff to understand the issues involved in developing an electronic option to hardcopy forms.  Assist, as appropriate, in completing the GPEA compliance project plans to reflect specific dates for activities on the critical path for developing an electronic option and meeting the stated GPEA compliance dates.
**Records Officer:  **Manage their agency’s electronic records management program to ensure that electronic records and their documentation are retained as long as needed.  Work with the program staff to ensure that appropriate records management policy is followed.
**Key Contacts:  **Serve as subject matter experts for their agencies.  The business key contact acts as an intermediary between eGovernment efforts and program personnel to ensure that program objectives and eGovernment activities are integrated.  The technical key contact acts serves a similar role for the information technology staff.

## eGovernment Report Timeline

- December

- February

- January

**December 9-20:**
- Initial One-on-One Agency Meetings

**December 9-February 14**
- Ongoing OCIO support

**January 31:**
- Final agency spreadsheets and project plans due

**February 17-28:**
- Follow-up meetings held with individual agencies

**February 14:**
- Final Revised Agency eGovernment Reports due

## Agenda

**Agenda**

**Welcome**
**Smart Choice Update**
**eGovernment Integrated Reporting**
**eDeployment Business Case**
**Q&A**
**Next Steps and Wrap-up **

**Notes:**
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.

## Agenda

**Background and Context**
**Business Requirements**
**Alternatives Analyzed**
**Recommendation: Enterprise-wide Distributed Solutions**
**Benefits**
**Timeline & Milestones**
**Next Steps**

**Agenda**

**Notes:**
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.

## Business Case Team Roster

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

## Business Case Team Roster (Continued)

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

## Our Approach

**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

## 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
- Analysis of Existing Systems (if applicable)
- Technical Architecture Plan
**Management and Planning Profile**
- Project Plan
- Acquisition Plan

## 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.

**Notes:**
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.

## 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.***

**Notes:**
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.

## 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.

**Notes:**
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.

## 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 .

**Notes:**
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.

## 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:***

**Notes:**
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.

## 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.***

## Recommendation: Integrated Enterprise Solutions in a Distributed Environment

**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.**

**USDA****Data****Center**

**USDA****Data****Center**

**USDA****Data****Center**

- = Agency accessingenterprise solutions

- = Enterprise solutionsare housed in USDAdata centers to beleveraged by agenciesand strategic initiatives

**Notes:**
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.

## 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.***

## 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.***

## Timeline and Milestones

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

| Phase | Description | Schedule |
| --- | --- | --- |
| 1 | Pre-Implementation Tasks: 
Phase 1 consists of tasks that must be performed prior to implementation.  These initial tasks include the vendor analysis and selection process as well as creating and configuring the technology infrastructure and the physical network required for implementation. | Q2 FY2003 -       Q3 FY2003 |
| 2 | Early Adopter Implementation:
Phase 2 is the full implementation of eDeployment services for early adopter Agencies.  This includes project planning, design, build, test, conversion, pilot, and workforce transition activities.  
Early adopter Agencies will complete implementation of eDeployment capabilities in a timeframe ranging from Q4 FY2003 – Q2 FY2004. | Q2 FY2003 –      Q2 FY2004 |
| 3 | Enterprise-wide Implementation: 
Phase 3 encompasses a similar set of tasks as the Early Adopter Implementation in Phase 2.  During this time, remaining USDA Agencies will conduct full implementation of eDeployment services.  | Q3 FY2004 –      Q4 FY2007
 |

## Timeline and Milestones

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

## 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. ***

## Next Steps for the eDeployment Initiative

***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**
- Confirm approval from OMB for FY04 funding; and
- 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.

## Agenda

**Agenda**

**Welcome**
**Smart Choice Update**
**eGovernment Integrated Reporting**
**eDeployment Business Case**
**Q&A**
**Next Steps and Wrap-up **

**Notes:**
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.

## Questions and Answers

## Agenda

**Agenda**

**Welcome**
**Smart Choice Update**
**eGovernment Integrated Reporting**
**eDeployment Business Case**
**Q&A**
**Next Steps and Wrap-up **

**Notes:**
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.

## Next Steps

**Please return any comments on the eDeployment business case (as well as the other Enablers business cases) by December 13**
- Send your comments to the eGovernment Mailbox (_[egov@usda.gov](mailto:egov@usda.gov)_)
**Work with the eGovernment team to set up an initial meeting on the eGovernment Integrated Reporting Process**
**Brief your agency eGovernment Steering Committee on the Integrated eGovernment Reporting Process and Enablers business cases**
**eLearning Briefing Tomorrow**
- At 1 PM in S-107
**Schedule change for eAuthentication briefing next Wednesday**
- Meeting now scheduled for _**1 PM**_ in room S-107 on Wednesday, Dec. 11
- (Message originally sent out had indicated that the meeting is at 11 AM)