Enterprise Architecture Working Group Session June 12, 2008

1. United States Environmental Protection AgencyOffice of Environmental InformationEnterprise Architecture Program Enterprise Architecture Working Group SessionJune 12, 2008

2. Agenda

3. EAWG Discussion Board • An online discussion board has been established for EAWG members (see handout EAWG discussion board instructions) • To register, place a in the right column on today’s sign-in roster. If you are not present at the meeting but would like to join, please email roberts.eric@epa.gov • Initial purpose: • To solicit feedback on 2008 architecture process, EA training, and EAWG meetings. • To evaluate whether it is useful to have an online discussion board, and if so, whether to use Oracle Collaborative Workspaces or try a different tool. Intranet link (in slide show view)

4. EAWG Discussion Board Five forums established; more can be added later.

5. READ Record Update • Statistics: • Initial deadline of April 30, 2008; review completed; new deadline of June 9, 2008 • 105 records (all CPIC Majors and Lites) • 30 fields in record to be completed • 10 program offices • Changes this year: • Integrated EA READ data call with John Harman’s basic READ data call • 2006-2011 Strategic Plan added to READ • New fields required for EA compliance: • Planned/Initial Operation and Termination Dates; Additional Details about your system; any Major Enhancements planned over the next year Progress so far: 92% of all READ records updated

6. READ Record Update Current Level of READ Record Completeness *Review of records incomplete due to data sensitivity issues

7. READ Record Update—Suggestions for Improvement? • Create ‘N/A’ fields in READ • Better alignment between READ data fields and what is required in the Exhibit 300s and CPIC Lite proposal forms • Any other suggestions?

8. Solution Architecture – Progressing in Value The 2008 solution architecture process is intended to provide increased business value by using solution information to result in business analysis. 2007 detailed solution architecture process Complete investment/system information Submit finalized information Import into ART Investment /System Owner Investment /System Owner Investment /System Owner Investment /System Owner EA Team EA Team EA Team FOCUS: Documenting current and target solution’s relevant information 2008 detailed solution architecture process Newly suggested steps for 2008 Conduct analysis Identify information gaps Communicate gaps with stakeholders Update/submit investment/system Information Import information into ART Complete /submit investment/system information Review information for completeness and accuracy EA Team EA Team EA Team FOCUS: Educating solution owners, increasing data quality, conducting analysis

9. Solution Architecture – What is the expected timeframe? Current resource allocation suggests analysis of solution information for business purposes is intended for completion within 2008. 2008 detailed solution architecture process Conduct analysis Complete /submit investment/system information Review information for completeness and accuracy Identify information gaps Communicate gaps with stakeholders Update/submit investment/system Information Import information into ART Investment /System Owner Investment /System Owner EA Team EA Team Status: Complete Status: Pending Status: Pending Status: Pending Status: Pending Status: Pending Status: Pending Expected: June Expected: June Expected: July/August Expected: Jul/Aug/Sep Expected: Sep/Oct Expected: Oct/Nov EA Team EA Team EA Team

10. Solution Architecture – What are the inputs and outputs? Gap analysis, facilitated working sessions, and preparation of solution architecture data are key outputs for 2008. 2008 detailed solution architecture process Conduct analysis Complete /submit investment/system information Review information for completeness and accuracy Identify information gaps Communicate gaps with stakeholders Update/submit investment/system Information Import information into ART Investment /System Owner Investment /System Owner EA Team EA Team Status: Complete Status: Pending Status: Pending Status: Pending Status: Pending Status: Pending Status: Pending Expected: June Expected: June Expected: July/August Expected: Jul/Aug/Sep Expected: Sep/Oct Expected: Oct/Nov Analyze Models, Views, and Reports Prepare Models, Views, and Reports Solution Architecture Template Working Sessions Quality and Content Review Architectural Analysis Solution Architecture Templates Updated Solution Architecture Template EA Team EA Team EA Team

11. Solution Architecture – What is the End Result? Making the solution architecture process relevant to EA stakeholders is key to gaining further EA buy-in and ensuring a smooth process for years to come. Question: How can solution architecture information become relevant to EA stakeholders? Answer: By taking raw data of limited use (from solutions) and conducting analysis to turn data into valuable and relevant information for EA stakeholders. Conduct analysis Complete /submit investment/system information Review information for completeness and accuracy Identify information gaps Communicate gaps with stakeholders Update/submit investment/system Information Import information into ART *Note: stakeholder benefits are samples only

12. Contact Information If you have any questions about the information presented today, please contact one of the following individuals David Prompovitch EPA EA Team Lead 202.564.0588 (office) prompovitch.david@epa.gov Joanna Hugney PPC EA Program Manager 703.748.7094 (office) jhugney@ppc.com John Sullivan EPA Chief Architect 202.566.0328 (office) sullivan.john@epa.gov