U.S. Department of Agriculture eGovernment Program January 22, 2003 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive

U.S. Department of Agriculture eGovernment Program 2  Welcome  Enablers Business Cases – Current Status & Future Direction  eGovernment Integrated Reporting Update  Proof of Concept Prototype  Q&A  Next Steps and Wrap-up Agenda

U.S. Department of Agriculture eGovernment Program 3 Define Functional (Business) Requirements Develop Select-Level Business Case Templates 1 2 September 2002 October 2002 November 2002 December 2002 Define Technical Requirements 3 4 Next Steps: Briefings with CIOs, Agency Heads, Sub-cabinet, etc. EITIRB Approval— February 18 Business Cases under Final Review 5 Enablers Business Cases and Implementation Planning Gameboard January 2003 We are here January 22

U.S. Department of Agriculture eGovernment Program 4 Enablers Business Cases – Next Steps The most important next steps are to gain buy-in and acceptance from key stakeholders and to gain funding approval from the EITIRB. Executive Council meeting now to discuss recommendations for funding. The EITIRB will consider the Enablers business cases at its next meeting on February 18. In preparation for this meeting, the eGovernment team developed a project plan and a timeline for briefing: EITIRB members, Members of the Executive Work Group (which makes investment recommendations to the EITIRB), Agency heads and Agency CIOs; and Other stakeholders.

U.S. Department of Agriculture eGovernment Program 5 Business Case Next Steps: EITIRB Approval Process JanuaryFebruary eGovernment Team/EC Briefs Agency Heads & Agency CIOs Deputy Secretary Briefing eGovernment Team/EC Briefs EITIRB Members February 18: Quarterly EITIRB Meeting February 5: Executive Working Group (EWG) Meeting eGovernment Team Briefs EWG Members EGWG Members Complete Agency Steering Committee Briefings Approach

U.S. Department of Agriculture eGovernment Program 6 Business Case Next Steps: Working Group Roles eGovernment Working Group Members should: Brief Agency eGovernment Steering Committee on business cases Provide feedback and agency perspective on business cases Act as point of contact for others to provide suggestions or other feedback on business cases Continue to communicate the eGovernment “message” to others in the agency, especially the concept and benefits of the Enablers It is particularly important for Working Group members to create ownership across the Department by communicating the specific benefits their agencies will receive from the Enablers

U.S. Department of Agriculture eGovernment Program 7 Agenda  Welcome  Enablers Business Cases – Current Status & Future Direction  eGovernment Integrated Reporting Update  Proof of Concept Prototype  Q&A  Next Steps and Wrap-up

U.S. Department of Agriculture eGovernment Program 8 Integrated eGovernment Reporting Timeline DecemberFebruary January December 9- January 23: Initial One-on-One Agency Meetings December 9- February 14: Ongoing OCIO support January 31: Final agency spreadsheets and GPEA project plans due February 17-28: Follow-up meetings held with individual agencies February 14: Updated Agency eGovernment Tactical Plans due December 4: eGovernment Team Kickoff Meeting December 4: Agency Kickoff Meeting We are here January 22

U.S. Department of Agriculture eGovernment Program 9 How will this report be compiled? The report consists of three major components: I. Spreadsheets II. Project Plan Outlines III. Revised Agency eGovernment Tactical Plan Agency eGovernment Report Due January 31st Due February 14th

U.S. Department of Agriculture eGovernment Program 10  Welcome  Enablers Business Cases – Current Status & Future Direction  eGovernment Integrated Reporting Update  Proof of Concept Prototype  Q&A  Next Steps and Wrap-up Agenda

U.S. Department of Agriculture eGovernment Program 11 Goals of the Proof of Concept A proof of concept prototype visually illustrates how eGovernment is being implemented at USDA to change the way we do business.  Showcases the vision set forth in the eGovernment strategic plan and its respective initiatives  Articulates how net-centric technology will be used to enhance program and service delivery and enhance our internal operations  Fosters discussion about changing business processes and the positive impacts that may have  Helps program managers understand how technology being implemented effects their business  Serves as a marketing and communication tool Employees see the Department making progress and begin to develop a new mindset about the current operational paradigm A consistent message can be delivered to business partners about how USDA plans to change Executive leadership can use as a consistent message to constituents about the strategic direction of the Department

U.S. Department of Agriculture eGovernment Program 12 Goals of the Proof of Concept The proof of concept will be comprised of various “scenarios” which take the viewer through a series of functional or mock screens. The scenarios have been grouped into three areas*:  New services / business process improvements Scenarios showing how the use of net-centric technology can streamline a business process or enable the creation of a new service to enhance a program Aggregation of data from across the enterprise to deliver new or enhanced online services to customers  Internal operations Scenarios showing positive changes in the way USDA conducts business internally  Innovative use of technology Forward-looking scenarios that show how next generation technology may impact how USDA’s programs are delivered to customers *Scenarios already may be USDA eGovernment initiatives or Presidential Initiatives

U.S. Department of Agriculture eGovernment Program 13 Goals of the Proof of Concept To complete the proof of concept quickly, most scenarios will be mock-ups, but a small number of scenarios identified as “quick hits” may be implemented  Mock-up screens will be HTML-only, functional screens will utilize a COTS package and/or custom code  Scenarios will be hosted on a secure server to enable access from remote locations but will also be able to run locally  Scenarios may involve other tools besides a Web browser, i.e. cell phones, pagers, PDA’s, and high technologies such as RFID tags  Because this is a proof of concept, it will not meet 508 compliance nor be compatible with a wide array of browsers  Scenarios will be easily updatable so quick reaction to feedback will be possible

U.S. Department of Agriculture eGovernment Program 14 Implementation Plan The quickest path to implementation:  Various project teams working in parallel with a project lead  Scenarios are finalized by project teams under the leadership of OCIO Core team includes a small business and IT steering committee, e.g. business case leads  COTS packages are chosen by development team without an elongated vendor selection process

U.S. Department of Agriculture eGovernment Program 15 Implementation Plan The prototype implementation team includes a technical implementation team, COTS product engineers, and business subject matter experts eGovernment PMO Implementation Team Lead COTS Product Engineers Business SME Lead UI Designer Graphic Artist HTML/Script Developers USDA SMEs Industry SMEs Recommended Implementation Team  The implementation team would be managed by the eGovernment Program Management Office  The implementation team is responsible for designing templates, coding HTML and scripts, and setting up the necessary technical architecture  The COTS product engineers are responsible for installing their solution, performing necessary customization, and ensuring it is functioning appropriately  The Business SMEs are responsible for working to define scenarios, define process flows, write content, and confirm final output meets the scenario’s specifications Team Roles

U.S. Department of Agriculture eGovernment Program 16 Proof of Concept Prototype: Next Steps The following are the immediate next steps to move forward in developing the prototype:  Define priorities for the development of the prototype Time to completion, accuracy, project teams, marketing tool, etc.  Define detailed tasks and budget based on implementation plan approach  Obtain contractor resources to assist in the development of the prototype  Identify USDA stakeholders and full-time team members

U.S. Department of Agriculture eGovernment Program 17  Welcome  Enablers Business Cases – Current Status & Future Direction  eGovernment Integrated Reporting Update  Proof of Concept Prototype  Q&A  Next Steps and Wrap-up Agenda

U.S. Department of Agriculture eGovernment Program 18 Questions and Answers

U.S. Department of Agriculture eGovernment Program 19  Welcome  Enablers Business Cases – Current Status & Future Direction  eGovernment Integrated Reporting Update  Proof of Concept Prototype  Q&A  Next Steps and Wrap-up Agenda

U.S. Department of Agriculture eGovernment Program 20 Next Steps Provide feedback on the eGovernment Newsletter, as well as any story ideas/suggestions you may have, to the eGovernment Mailbox Continue to work on the requirements for the Integrated eGovernment Reporting Process and contact us with any questions or concerns If you have not yet done so, brief your agency eGovernment Steering Committee on the Integrated eGovernment Reporting Process and Enablers business cases Next eGovernment Working Group meeting will be on February 5 in S-107