1. U.S. Department of Agriculture eGovernment Program March 19, 2003 Overview of Mid-Year Progress Report on GPEA Implementation Activities Nancy Sternberg

2. U.S. Department of Agriculture eGovernment Program 2 Integrated eGovernment Reporting – Overview 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  GPEA reporting on a form-by-form basis, including agency status and plans for reaching compliance  Refined/prioritized list of agency eGovernment initiatives with budget estimates and project milestones  Detailed agency eAuthentication requirements  Data necessary to develop the Information Value Chain  Serves as the basis for future quarterly eGovernment reports

3. U.S. Department of Agriculture eGovernment Program 3 Integrated eGovernment Reporting – Greater Detail Previously, GPEA compliance data was gathered at a Paperwork Reduction Act (PRA) “transaction” level Integrated eGovernment Reporting required GPEA compliance information on a form-by-form or customer interaction basis This “new scale” should be considered when comparing Integrated eGovernment Reporting data with information collected in September 2002 469 PRA Transactions 3,146 GPEA Customer Interactions

4. U.S. Department of Agriculture eGovernment Program 4 Integrated eGovernment Reporting – GPEA Compliance Based on the greater detail gathered through the Integrated eGovernment Reporting process, the Department’s GPEA compliance estimates have been revised from 58 to 36 percent. The most frequent justifications for identifying a customer interaction as “not practicable” for meeting GPEA include:  Delivery of products/services through an intermediary  Physical restrictions  Face-to-face requirements GPEA Compliance Status

5. U.S. Department of Agriculture eGovernment Program 5 Integrated eGovernment Reporting – eAuthentication Of the 3,146 customer interactions identified, agencies indicate that 1,400 (45%) will require some form of electronic signature capability. Twenty-two percent do not require electronic signature and 33% customer interactions were incomplete or are still under evaluation. eSignature Needs

6. U.S. Department of Agriculture eGovernment Program 6 GPEA Implementation Progress Reports Mid-Year Progress Report on Implementing GPEA, March 2003 354(11%) 774(25%) 422(13%) 1,596 1 (51%) 3,146(100%) 77(16%) 194(41%) 24(5%) 174(37%) 469(100%) Transactions Completed to Date: Transactions to be Completed by 10/2003 Transactions to be Completed after 10/2003 Transactions that will not be Completed Total Annual Progress Report on Implementing GPEA, September 2002 1 This number represents an aggregate of customer interactions that agencies indicate will not offer an electronic transaction as well as those interactions that are incomplete.

7. U.S. Department of Agriculture eGovernment Program 7 One-stop shopping, one-stop benefits across federal Departments, and/or between levels of governments Inter-agency Unification Fillable on-line forms/printable and faxed, mailed, e-mailed, or hand-carried for delivery Electronic Forms Web services beyond electronic forms—provides two-way electronic communication via the web Electronic Transaction Electronic transactions tied to a reengineered process Process Streamlining One-stop shopping, one-stop benefits among bureaus/agencies within the Department Intra-agency Unification Complexity Value The Transformation Continuum Copyright 2001 Accenture. All rights reserved. GPEA Compliant 12% 32% 9% 1% 0% What level of electronic interaction will agencies be offering customers?

8. U.S. Department of Agriculture eGovernment Program 8 Integrated eGovernment Reporting – Next Steps Agencies should continue work towards completing the GPEA Compliance Project Plans and updates to the eGovernment Tactical Plans; please submit these as soon as possible. The eGovernment Team will be developing comprehensive feedback and analyses of the information provided. Follow-up meetings with most agencies will commence in the near future to resolve GPEA compliance questions and refine electronic signature requirements. GPEA compliance commitments recorded in the data spreadsheets will be referenced in the Paperwork Reduction Act (PRA) approval process during the review of information collection packages as well as in the regulatory review process. The updated eGovernment Tactical Plans will become the new baseline for measuring agency eGovernment activity and progress through a quarterly reporting process.