u.s. department of agriculture egovernment program january 8, 2003 egovernment working group meeting...

U.S. Department of Agriculture

eGovernment Program

January 8, 2003

eGovernment Working Group Meeting

Chris Niedermayer, USDA eGovernment Executive

2

U.S. Department of Agriculture eGovernment Program

Welcome

Enablers Business Cases – Next Steps/Future Direction

eGovernment Integrated Reporting FAQ

eGovernment Act Update

Q&A

Next Steps and Wrap-up

Agenda

3


Define Functional (Business) Requirements

Educate stakeholdersIdentify best practice

requirementsReview best practices

with mission areasGather 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 PlanTelecom-

munications PlanAnalysis of

Existing Systems (if applicable)

Technical Architecture Plan

eGovernment Plan

3 Complete Cost/Benefit Analysis

Complete Risk Management

Complete ImplementationProject 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

In Progress Events

Future Events

Color Key

Completed Items

Enablers Business Cases and Implementation Planning Gameboard

4


Enablers Business Cases – Current Status

• Draft business cases for all three Enablers are now complete

• As a result of EITIRB being delayed by two weeks and to give agencies more time for feedback, the period for comment and feedback has been extended

• Comments now due to the eGovernment Team by January 10

• All comments will be incorporated and the draft documents finalized by January 17.

• The eGovernment Team has developed a plan to secure approval for the business cases from the Enterprise Information Technology Information Review Board (EITIRB)

• Details follow on next slides

• Additional actions to plan for the Enablers and prepare for their implementation are in the works

5


Enablers Business Cases – Next Steps

• With the completion of draft business cases for the three eGovernment Enablers, the most important next steps are to gain buy-in and acceptance from key stakeholders and to gain funding approval from the Executive Information Technology Information Review Board (EITIRB).

• The EITIRB will consider the Enablers business cases at its next meeting on February 18. In preparation for this meeting, the eGovernment team is working with the Executive Council to develop 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.

6


Business Case Next Steps:EITIRB Approval Process

January February

eGovernment Team/EC Briefs Agency Heads &

Agency CIOs

Deputy Secretary Briefing

eGovernment Team/EC Briefs

EITIRB Members

February 18:

Quarterly EITIRBMeeting

February 4:

Executive Working Group (EWG) Meeting

eGovernment Team Briefs

EWG Members

EGWG Members Complete Agency

Steering Committee Briefings

Business Case Comments Due to eGovernment

Team

Proposed Schedule

7


Business Case Next Steps:Roles and Responsibilities

• eGovernment Team (OCIO): Coordinate the process of briefing key stakeholders and gaining buy-in in preparation for the February EITIRB meeting, including briefing individual EITIRB and Executive Work Group members and agency CIOs. Act as a central point of contact to answer questions and provide support on the Enablers business cases.

• eGovernment Working Group Members: Brief Agency eGovernment Steering Committee on business cases, provide feedback and agency perspective on business cases, and act as point of contact for others to provide suggestions or other feedback on business cases. Also, continue to communicate the eGovernment “message” to others in the agency, especially the concept and benefits of the Enablers.

• eGovernment Executive Council Members: Brief agency heads within the mission area on Enablers business cases, provide feedback on business cases, and act as point of contact for senior executives on business-case related issues or questions. Attend individual EITIRB member meetings and February 18th meeting.

8


Agenda

Welcome




Q&A


9


Integrated Reporting:Frequently Asked Questions

• What if my agency has forms or transactions that will not be compliant with GPEA by October of 2003? If compliance will occur at a later date, provide that date and explain the need for

extra time

OCIO must have the “full story” behind these forms/transactions to best defend USDA’s GPEA compliance efforts to OMB and Capitol Hill

• Do I have to complete a GPEA Project Plan for every form or interaction with the public? No. There should be a project plan for every form or interaction for which an

electronic alternative will be offered, however …

Forms can be aggregated together if a single project plan addresses each of them

10


• How can I complete these GPEA Project Plans without more information on the enterprise-wide eAuthentication effort? Integrated eGovernment Reporting asks agencies to determine the level of

security they need on a form-by-form basis to help prepare for the eventual roll-out of enterprise-wide solutions

Large amount of activity going on with the development of USDA eAuthentication Select-Level Business Case

Next steps will include eAuthentication team members meeting with agencies to review agency inputs

• What if my agency has not obtained tools for providing online forms? Several USDA agencies have purchased tools already and have experience in this

area

OCIO will facilitate meetings between agencies to determine if there are opportunities to partner and build upon existing agency efforts


11


• Should my revised Agency eGovernment Tactical Plan represent more than my GPEA Project Plans? Yes. The eGovernment Tactical Plan should represent all of your agency’s high-

priority eGovernment efforts, including those that are not related to GPEA

Additionally, eGovernment Tactical Plans should include proposals that address employee needs and do not involve interactions with the public

Each GPEA Project Plan must be reflected in an initiative within the eGovernment Tactical Plan

• Should I still include information on my agency’s efforts to support Smart Choice and/or Presidential Initiatives? Yes. If your agency’s top eGovernment priorities include work on any of the

Smart Choice proposals or Presidential Initiatives, they should be included either in the section describing Current eGovernment Efforts (Section III) or the section addressing Proposed eGovernment Opportunities (Section IV)

The section included in the previous eGovernment Tactical Plan template that dealt specifically with agency support of Smart Choice initiatives was eliminated to simplify and clarify the purpose of these plans


12


• With the Integrated eGovernment Report complete, how often will I need to update this information? This is to be determined—the possibility of additional OMB requirements/data

requests prevents OCIO from developing a long-term schedule

OCIO intends to coordinate updates of all information collected in the Integrated eGovernment Report


13


Welcome




Q&A


Agenda

14


eGovernment Act of 2002

• The eGovernment Act was signed into law by President Bush in December 2002. The Act passed both Houses unanimously.

• Importantly, the eGovernment Act codifies much of the President’s Management Agenda and introduces a wide range of new programs, procedures, and regulations, including:

• A centralized Office of Electronic Government in OMB to more centrally manage Federal eGovernment activities/initiatives

• A government-wide eGovernment Fund

• New, more flexible options for technology exchanges with the private sector and use of share-in-savings contracts

• Additional eGovernment reporting requirements from agencies to OMB and from OMB to Congress

• Additional information security requirements designed to standardize and strengthen agency security programs.

15


eGovernment Act: New Roles for OMB and GSA

• The New Office of Electronic Government in OMB will expand upon the current eGovernment organization headed by Mark Forman to:

Develop and manage government-wide eGovernment and IT strategies and initiatives Act as a central point of contact and coordination for eGovernment issues with Federal

agencies and set standards/policies to enable multi-agency coordination and collaboration

Lead the CIO Council and partner with GSA on common eGovernment initiatives Bring together the public and private sectors to share best practices Oversee development of agency and Federal Enterprise Architectures, oversee develop-

ment of agency IRM policies, and ensure compliance with system accessibility standards Develop standardized reporting processes, both from agencies to OMB and from OMB to

Congress

• An eGovernment Fund within GSA will fund innovative interagency eGovernment initiatives

GSA will administer the fund with oversight from OMB By FY 2006, $150 million per year in funding will be authorized

16


• The Act adds several responsibilities to USDA when planning for and implementing eGovernment. Specifically, the Department must: Develop performance goals and measures, linked to key stakeholder groups,

that demonstrate how electronic government enables progress towards agency strategic goals

For all initiatives, consider privacy impacts and impacts on Americans without Internet access

Submit an annual eGovernment Report to OMB on the status of implementing eGovernment initiatives and compliance with the eGovernment Act.

Post all regulatory information that must appear in the Federal Register on agency Web sites

Accept electronic input from citizens for the rulemaking process

The Act also provides additional contracting and procurement opportunities for USDA by: Allowing more share-in-savings contracts for IT procurement Authorizing new public-private technology transfer programs

eGovernment Act: Impacts for USDA

17


Welcome




Q&A


Agenda

18


Questions and Answers

19


Welcome




Q&A


Agenda

20


Next Steps

• Please forward the eGovernment Newsletter to your agency eGovernment Steering committee and anyone else you feel may benefit from reading it• Additionally, please provide feedback and any story ideas/suggestions you

may have to the eGovernment Mailbox ([email protected]).

• Continue to meet with the eGovernment Team on the new Integrated 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 by January 10

• Next meeting will be on January 22 in S-107

u.s. department of agriculture egovernment program january 8, 2003 egovernment working group meeting...

Documents