U.S. Department of Agriculture eGovernment Program Integrated eGovernment Reporting May 2004.

Slides:



Advertisements
Similar presentations
CPIC Training Session: Enterprise Architecture
Advertisements

How to Document A Business Management System
Information Governance and the Presidential Memo on Managing Government Records: Converging Issues and the Search for New Ideas Presidential Memorandum:
U.S. Department of Agriculture eGovernment Program February 2004 eAuthentication Integration Status eGovernment Program.
Presented By: Thelma Ameyaw Security Management TEL2813 4/18/2008Thelma Ameyaw TEL2813.
Enterprise Architecture. 2 Agenda What is Enterprise Architecture (EA)? Roles in EA? Why is EA Important? Tangible Benefits from EA? What Do We Need to.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
Electronic Government: Law, Policy, and Practice Jonathan P. Womer Information Policy and Technology Office of Management and Budget
SE 555 Software Requirements & Specification Requirements Management.
U.S. Department of Agriculture eGovernment Program eLearning Pre-Implementation Approach May 2003.
Expanded Version of COSO a presentation by Steve Wadleigh Expanded Version of COSO a presentation by Steve Wadleigh Standards for Internal Control in the.
The E-Authentication Initiative: A Status Report Presented at Educause Meeting June 16, 2004 The E-Authentication Initiative.
Archived File The file below has been archived for historical reference purposes only. The content and links are no longer maintained and may be outdated.
0 Un ited States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Enterprise Architecture Working Group.
Enterprise IT Decision Making
The Microsoft Office 2007 Enterprise Project Management Solution:
Version 1.0– June 18, Leveraging the Texas Project Delivery Framework and.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive February 25, 2004.
NIST Special Publication Revision 1
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Information Assurance The Coordinated Approach To Improving Enterprise Data Quality.
U.S. Department of Agriculture eGovernment Program Select Level Business Cases Overview of Business Case Sections.
U.S. Department of Agriculture eGovernment Program August 14, 2003 eAuthentication Agency Application Pre-Design Meeting eGovernment Program.
U.S. Department of Agriculture eGovernment Program July 23, 2003 eAuthentication Initiative Agency Responsibilities and Funding Discussion eGovernment.
3.08 b Determine venture’s information technology.
U.S. Department of Agriculture eGovernment Program March 27, 2002 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
December 14, 2011/Office of the NIH CIO Operational Analysis – What Does It Mean To The Project Manager? NIH Project Management Community of Excellence.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
U.S. Department of Agriculture eGovernment Program July 10, 2002 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
U.S. Department of Agriculture eGovernment Program April 9, 2002 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive September 3, 2003.
1 What’s Next for Financial Management Line of Business (FMLoB)? AGA/GWSCPA 6 th Annual Conference Dianne Copeland, Director, FSIO May 8, 2007.
U.S. Department of Agriculture eGovernment Program May 12, 2004 eGovernment Working Group U.S. Department of Agriculture eGovernment Program.
U.S. Department of Agriculture eGovernment Program July 15, 2003 eAuthentication Initiative Pre-Implementation Status eGovernment Program.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive March 24, 2004.
U.S. Department of Agriculture eGovernment Program February 5, 2003 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
U.S. Department of Agriculture eGovernment Program Design Approach for usda.gov April 2003.
U.S. Department of Agriculture eGovernment Program January 8, 2003 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
Enterprise Architecture, Enterprise Data Management, and Data Standardization Efforts at the U.S. Department of Education May 2006 Joe Rose, Chief Architect.
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 eGovernment Working Group Meeting February 11, 2004.
U.S. Department of Agriculture eGovernment Program Government Paperwork Elimination Act (GPEA) Kickoff Meeting Nancy Sternberg, USDA GPEA Point of Contact.
U.S. Department of Agriculture eGovernment Program April 14, 2003 eGovernment Working Group Investment Year 2006 Planning/Budgeting Activities U.S. Department.
U.S. Department of Agriculture eGovernment Program July 9, 2003 eAuthentication Initiative Update for the eGovernment Working Group eGovernment Program.
Department of Defense Knowledge Fair Tim Young Office of Management and Budget September 27, 2007.
EPA Geospatial Segment United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Segment Architecture.
Catawba County Board of Commissioners Retreat June 11, 2007 It is a great time to be an innovator 2007 Technology Strategic Plan *
U.S. Department of Agriculture eGovernment Program eAuthentication Draft Business Case Executive Summary January 2003.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive October 1, 2003.
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
Internal Controls FMC September Introduction Internal Controls and the BCR/CAFR Green Book Current State Vision for the Future Agenda.
U.S. Department of Agriculture eGovernment Program January 9, 2002 eGovernment Working Group Chris Niedermayer, USDA eGovernment Executive Barbara LaCour.
1 Geospatial Line of Business Update FGDC Coordination Group April 14, 2009.
CIWQS Review Phase II: Evaluation and Final Recommendations March 14, 2008.
U.S. Department of Agriculture eGovernment Program March 19, 2003 Overview of Mid-Year Progress Report on GPEA Implementation Activities Nancy Sternberg.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive December 3, 2003.
U.S. Department of Agriculture eGovernment Program January 17, 2002 eGovernment Executive Council Chris Niedermayer, USDA eGovernment Executive Barbara.
U.S. Department of Agriculture eGovernment Program eDeployment Kickoff August 26, 2003.
The Solutions Exchange Bill Piatt August 17, 2004.
U.S. Department of Agriculture eGovernment Program December 4, 2002 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
U.S. Department of Agriculture eGovernment Program February 25, 2003 USDA Presidential Initiatives Meeting Chris Niedermayer, USDA eGovernment Executive.
U.S. Department of Agriculture eGovernment Program Smart Choice Pre-Select Phase Transition September 2002.
U.S. Department of Agriculture eGovernment Program October 2, 2002 eGovernment Working Group Meeting Chris Niedermayer, USDA eGovernment Executive.
U.S. Department of Agriculture eGovernment Program May 26, 2004 eGovernment Working Group U.S. Department of Agriculture eGovernment Program.
Federal Enterprise Architecture (FEA) Architecture Plus Meeting December 4, 2007 Kshemendra Paul (Acting) Chief Architect.
ICS Area Managers Training 2010 ITIL V3 Overview April 1, 2010.
Data Management Program Introduction
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
Presentation transcript:

U.S. Department of Agriculture eGovernment Program Integrated eGovernment Reporting May 2004

U.S. Department of Agriculture eGovernment Program 2 Agenda I. Introduction and Purpose II. New Initiatives III. Data Reconciliation Process IV. IR Tool Demo V. eAuthentication Assurance Level VI. Contact Information

U.S. Department of Agriculture eGovernment Program 3 What is the Integrated eGovernment Report?  The original three components of the Integrated eGovernment Report were a data spreadsheet, GPEA Compliance Project Plans, and Agency eGovernment Tactical Plans. These components are interwoven and reinforce the relationship between various information technology and eGovernment activities.  Agencies are encouraged to view the Integrated eGovernment Report as a set of tools for managing their eGovernment activities and for communicating information about eGovernment activities and priorities within an agency in a manner that will further develop a deep understanding across all staff of how different initiatives are related to one another. The Integrated eGovernment Reporting process was launched in December 2002 as a way of promoting stronger integration among eGovernment and IT functions and streamlining the reporting requirements imposed on agencies.

U.S. Department of Agriculture eGovernment Program 4 Background – Previous Reporting Approach 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

U.S. Department of Agriculture eGovernment Program 5 eGovernment Tactical Plan - Information Value Chain  The information value chain is a key tool for enabling the transformation process.  By highlighting the integration of information and functions, agencies are able to achieve eGovernment principles and improve service delivery Customer Program (Line of Business) Product/ Service IT Investment Information (OMB Approved Collection) Forms provides Software Application/ Information System supports funds electronically enabled by collected using as required by delivers integrates with Enterprise eAuthentication Solution Agency eGovernment Tactical Plans Integrated Reporting Tool Acquisition Review Process

U.S. Department of Agriculture eGovernment Program 6 Current Integrated eGovernment Report GPEA Project Plans Integrated Reporting Tool Information Agency eGovernment Tactical Plan Due Date: April 30th Due Date: June 18th

U.S. Department of Agriculture eGovernment Program 7 Who is Involved in Preparing the Integrated eGovernment Report?  GPEA Coordinators  Information Collection Coordinators  IT Portfolio Managers  Forms Managers  Records Officers  Business/Program Representatives The eGovernment Working Group representative from each agency chairs an eGovernment Steering Committee comprised of individuals from a variety of functions. Input from many of these individuals is necessary to complete this report including:

U.S. Department of Agriculture eGovernment Program 8 Agenda I. Introduction and Purpose II. New Initiatives III. Data Reconciliation Process IV. IR Tool Demo V. eAuthentication Assurance Level VI. Contact Information

U.S. Department of Agriculture eGovernment Program 9 Business Gateway Presidential Initiative The Business Gateway (BG) Presidential Initiative is a government-wide effort to reduce the burden (financial and non-financial) associated with Federal information collection requirements and Government forms levied on citizens, businesses, and Government.  The Business Gateway is comprised of two components; 1) The Business Portal, which will be the single access point for all the Federal government services and information needed to start, run and grow a business and 2) the E- Forms Catalog, a single electronic forms management infrastructure across Federal government designed to reduce the regulatory paperwork burden.  Objectives of the initiative include: - Improve GPEA compliance - Reuse data and solutions to reduce redundancy and cost - Cut across stovepipes and agency boundaries to improve customer service and Government efficiency - Deliver high quality services and infrastructure to agencies to free them to focus on their core missions

U.S. Department of Agriculture eGovernment Program 10 Agenda I. Introduction and Purpose II. New Initiatives III. Data Reconciliation Process IV. IR Tool Demo V. eAuthentication Assurance Level VI. Contact Information

U.S. Department of Agriculture eGovernment Program 11 What Actions Are Required to Complete the Reconciliation?  Agencies are required to maintain up-to-date information in the Integrated Reporting Tool on an ongoing basis. Due to changes resulting from the implementation of final eAuthentication guidance and improvements to the Integrated Reporting Tool, each agency is required to perform a data reconciliation process to verify that the information in the Integrated Reporting tool is accurate and reflects the information and intentions of each agency.  By June 18th 2004, at the close of the reconciliation process, each Agency Head will be required to certify through signature on a memorandum that the information in the Integrated Reporting tool is correct. This will include data related to: 1) eAuthentication assurance level requirements, 2) commitments to migrate to the USDA eAuthentication service, and 3) GPEA compliance plans.  The reconciliation process will not be considered completed until the Agency Head has certified through signature on a memorandum that the information and commitments in the Integrated eGovernment Report (the collection of information in the IR Tool and other documents) is complete and accurate.

U.S. Department of Agriculture eGovernment Program 12 Data Reconciliation Process Steps Completing the current Integrated eGovernment Report consists of several activities aimed at correcting and/or reconciling existing data and adding new information. The specific steps that each agency should address to accomplish to complete the report are described below. 1)Assess interactions in the IR Tool that are impacted by the final version of the OMB E-Authentication Guidance. Final E-Authentication guidance was issued by OMB in December An analysis of the impact of this guidance on interactions in the tool for which an assurance level had already been assigned revealed that about 500 interactions in the IR Tool are impacted by the changes resulting from this guidance. A report of the affected interactions, if any, will be provided to the eGovernment Working Group representative and the GPEA Coordinator in a separate . As a general rule, the suggested assurance level of all 500 of these interactions would be decreased by 1 level if the new OMB Guidance is applied to the existing Impact Profile Assessment data. Each interaction listed for an agency should be reviewed and discussed with the appropriate program area so that a final decision on the assurance level can be made.

U.S. Department of Agriculture eGovernment Program 13 Data Reconciliation Process Steps - Continued 2)Review interactions in the IR Tool that require an authentication assurance level 3 or 4. These interactions should be carefully reviewed to see if mitigating controls allow their assurance level to be decreased to level 1 or 2. If a level 3 or 4 is required, then a written narrative justifying the agency’s business decision for this level of assurance must be developed. This narrative should be submitted to OCIO as an attachment to the Agency Head's certification memorandum. 3)Review interactions in the IR Tool that have no GPEA compliance date, or whose GPEA compliance date is beyond These interactions should be carefully assessed to determine whether they are in fact practicable, and to work to implement a GPEA compliance plan. Compliance plans for all interactions with a GPEA compliance date beyond today’s date should be completed and submitted to OCIO as an attachment to the Agency Head's certification memorandum. The remaining list of "not practicable" interactions should be certified as accurate by your Agency Head. NOTE: The CIO has committed USDA to 100% GPEA compliance by the end of FY 2004.

U.S. Department of Agriculture eGovernment Program 14 Data Reconciliation Process - Continued 4)Evaluate interactions in the IR Tool that require electronic authentication but which do not have an assurance level OR an eAuthentication integration date. All interactions which require electronic authentication should have an assurance level as well as a planned eAuthentication integration date. This includes interactions which presently use a different form of electronic authentication. Integration plans for all interactions with a planned eAuthentication date later than 2004 should be completed and submitted to OCIO as an attachment to the Agency Head's certification memorandum. 5)Validate URLs for all interactions that offer an electronic form or other electronic option (GPEA compliant capability). Each interaction for which an electronic form or other electronic option for transacting business is available should provide an accurate URL. Where URL’s are already present, the link should be verified.

U.S. Department of Agriculture eGovernment Program 15 Data Reconciliation Process - Continued 6)Review each interaction to complete new fields and update others. Every interaction will need to be reviewed to complete data in several new fields. Additionally, because the new release of the IR Tool is more tightly integrated with the Enterprise Architecture repository and the WorkLenz tools, the universe of responses has changed for some existing fields. When a user modifies an interaction, they will be prompted to update some fields that previously had information.

U.S. Department of Agriculture eGovernment Program 16 Agenda I. Introduction and Purpose II. New Initiatives III. Data Reconciliation Process IV. IR Tool Demo V. eAuthentication Assurance Level VI. Contact Information

U.S. Department of Agriculture eGovernment Program 17 Integrated Reporting Tool The Integrated Reporting Tool stores and displays information about each USDA online and paper-based “interaction” between USDA and the public. This may be a form or a different form of information exchange. Information captured about each interaction now includes: Interaction Information Forms Information Business Information IT Information and eAuthentication Information New features of the IR Tool include: Data Integrity features (agency data may only be manipulated by agency personnel and eGovernment personnel Improved usability Adherence to the new USDA web presence style guidelines Updates to the eAuthentication assurance level calculations in accordance with the finalized OMB E-Authentication Guidance

U.S. Department of Agriculture eGovernment Program 18 Agenda I. Introduction and Purpose II. New Initiatives III. Data Reconciliation Process IV. IR Tool Demo V. eAuthentication Assurance Level VI. Contact Information

U.S. Department of Agriculture eGovernment Program 19 eAuthentication Assurance OMB E-Authentication Guidance OMB has released final guidance on how to assess the systems and interactions that require eAuthentication. Many interaction assessments that were completed previously in the Integrated Reporting Tool will result in a lower assurance level when following the new guidance. Assurance level guidance is available through the OMB Guidance, but the decision of which assurance level to apply to an individual interaction is at the judgment of the business owner and the Agency decision maker. Information about mitigating controls that may reduce the required assurance level is available from the eGovernment eAuthentication team. Assurance Level Calculator The eAuthentication Assurance Level calculator is available to assist in applying the final OMB E-Authentication Guidance to interactions or applications. It is available for download from the IR Tool or from the eGov web site. The questions in the Assurance Level calculator require a knowledge of the impact of an authentication error, and may be more easily answered after a risk assessment of the application or interaction which requires electronic authentication.

U.S. Department of Agriculture eGovernment Program 20 Agenda I. Introduction and Purpose II. New Initiatives III. Data Reconciliation Process IV. IR Tool Demo V. eAuthentication Assurance Level VI. Contact Information

U.S. Department of Agriculture eGovernment Program 21 Integrated Reporting Tool Contact Information Integrated eGovernment Reporting/GPEA Coordinator Nancy Sternberg Acting Records Manager Barbara LaCour Paperwork Reduction Act Coordinator/Business Gateway Lead Marty Mitchell eGovernment Program eGovernment