1. 0 Un ited States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Enterprise Architecture Working Group Session April 10, 2008

2. 1 Agenda 9:00 a.m.Welcome & IntroductionsJ. Sullivan 9:05 a.m. Update on 2008 Architecture Development Standards and Guidance J. Hugney 9:45 a.m.Emergency Management architectureJ. Karrie 10:15 a.m.IT Governance Support System updateL. Ford 11:00 a.m.AdjournJ. Sullivan Postponed

3. 2 Architecture Development Standards and Guidance 2008 Edition The 2008 Architecture Development Standards and Guidance employs a modified approach to documenting solution and segment architecture Recap of updates for 2008 (as presented at March EAWG) Level of effort and prerequisites are provided for each step. The Detailed Solution Architecture requirements include two new templates and an update to the Performance Management Framework. The Segment Architecture requirements include new templates and require review & approval of the framework used during 2007 segment reviews. Additional Information To minimize the burden placed on personnel, the EA team will be providing packets with pre-populated templates. At today’s EAWG meeting, we will review the detailed templates for collecting this information

4. 3 Architecture Development Standards and Guidance Timeline There following outlines the milestones for completing all Architecture Development Standards and Guidance requirements APRIL 10, 2008 Issue final 2008 Architecture Development Standards and Guidance April 18 EA Team provides Solution Architecture pre-populated templates for review and completion April 28 – May 2 First Solution and Segment Architecture Training at Potomac Yards May 5 – May 9 Second Solution and Segment Architecture Training at Potomac Yards May 16 Final due date to provide last SOLUTION documentation to the EA Team September 30 Final due date to provide SEGMENT documentation to the EA Team

5. 4 Architecture Development Standards and Guidance 2008 Distinctions – Solution Architecture The Performance Management Framework requirement has been updated The Performance Management Framework 2.0 has been improved in several ways The framework is due on May 16, 2008 2008 Information Requirements Description of Proposed Template Performance Management Framework, v2.0 The following adjustment have been made to the 2007 spreadsheet: Now links measurement indicators to Strategic Goal(s) supported Now links measurement indicators to parent indicators (e.g. Tech. to Process)

6. 5 Architecture Development Standards and Guidance 2008 Distinctions – Solution Architecture The Performance Management Framework template snapshot This template will be pre-populated with existing information from the Exhibit 300s and last year’s framework See Handouts

7. 6 Architecture Development Standards and Guidance 2008 Distinctions – Solution Architecture Two of the Solution Architecture models have been combined The Data Model and System Interface Diagram have been combined into one artifact – the Solution Information Flow & Interface Profile The artifact is due on May 16, 2008 2008 Information Requirements Description of Template Solution Information Flow & Interface Profile Complete a table, illustrating the following: Who provides information to this system? What information is provided to this system? How is the information provided to this system? Where is data stored for this system? Who uses information from this system?

8. 7 Architecture Development Standards and Guidance 2008 Distinctions – Solution Architecture Solution Information Flow & Interface Template snapshot See Handouts

9. 8 Architecture Development Standards and Guidance 2008 Distinctions – Solution Architecture There is a new Solution Architecture technology focus The Solution Architecture Technology Requirements Indicators Crosswalk is a new artifact that the EA team will provide for verification by the Solution Architect The crosswalk is due May 16, 2008 2008 Information Requirements Description of Template Solution Technology Requirements Indicators Crosswalk Capture alignment of your milestones to indicators of technology requirements: Indicators (pre-populated) Related Milestone(s) from the 2008 Transition Strategy and Sequencing Plan Additional details when no milestone relationship exists but there are plans for technology change Capture changes to your milestones, where applicable: New milestones Revised milestones

10. 9 Architecture Development Standards and Guidance 2008 Distinctions – Solution Architecture Solution Technology Requirements Indicators Crosswalk template snapshot This template will be pre-populated with existing information from the Transition Strategy and QTS Milestone Analysis See Handouts

11. 10 Architecture Development Standards and Guidance 2008 Distinctions – Segment Architecture There are new segment architecture artifacts that will require verification The segment artifacts will be provided to the relevant segment architects for verification, so the burden on the individual, and/or team, will be minimized. Verification and approval will be necessary for the following (by September 30, 2008): 2008 Information Requirements Description of Template Segment Performance Alignment Framework Capture relationships between measures and systems in the segment: Related Goal, Objective, and Sub-Objective Related Measures (e.g. from the OCFO Performance & Accountability Report) Investments System(s) that support the performance sub-objective chosen for #3 and can be measured using the measure in #4. Segment EM LoB Partnership Profile Identify federal partners, indicating the name of the federal agency and whether or not: The partner is a supplier or consumer of information A formal agreement is currently in place (if yes, explain) There is a system that EPA interacts with at the federal agency (if yes, explain)

12. 11 Architecture Development Standards and Guidance 2008 Distinctions – Segment Architecture Segment Performance Alignment Framework Template The framework is due September 30, 2008 See Handouts

13. 12 Architecture Development Standards and Guidance 2008 Distinctions – Segment Architecture Segment EM LoB Partnership Profile Template The profile is due September 30, 2008 See Handouts

14. 13 Architecture Development Standards and Guidance 2008 Distinctions – Segment Architecture There are new segment architecture artifacts that will require verification, cont’d 2008 Information Requirements Description of Template Document Relationship between Systems in the Segment Identify relationships between systems in segment’s IT portfolio Users Application Interfaces Data Repositories Data Application Services Application Interfaces Verify & Approve the Business Transformation Framework Verify/Approve an executive overview, called the “Business Transformation Framework” Strategic Goals and Drivers impacting the segment Services provided by the segment Program budget information within the segment Key IT investments within the segment Core data partners Transformation objectives that are being considered in planning and influencing decision-making across the segment. The framework and relationship diagram should be reviewed, approved, and submitted by September 30, 2008

15. 14 Architecture Development Standards and Guidance 2008 Distinctions – Solution Architecture Segment System Interface Diagram Template snapshot The following diagram will help show each segment’s IT portfolio, and its dependency upon other segments, as well as the Agency’s set of Enterprise Tools. Defining target information in this way allows the segment architect an opportunity to illustrate areas of reuse, consolidation and retirement in their target architecture. See Handouts

16. 15 Architecture Development Standards and Guidance 2008 Distinctions – Segment Architecture Business Transformation Framework See Handouts

17. 16 2007 Information Requirements 2008 Information Requirements Basic Solution Architecture (All Investments)  READ Record  Business Case (CPIC Lites or Exhibit 300s)  READ Record (due April 30)  Business Case (CPIC Lites or Exhibit 300s) (see http://intranet.epa.gov/cpic/by2010/index.htm ) Detailed Solution Architecture (Major and Select Non-Major Investments) Four Models Required:  Performance Management Framework  Business Process Diagram  Data Model  System Interface Diagram Three Artifacts Required (due May 16):  Performance Management Framework Version 2.0  Solution Information Flow & Interface Profile  Solution Technology Requirements Indicators Crosswalk Segment Architecture (12 Defined Segments)  Status on 2006 Action Plan  Verified Strategic Business & Data  Verified Application Inventory  Verified Technology Standards  Approved Baseline Four Artifacts Required (due Sep. 30):  Segment Performance Alignment Framework  Segment EM LoB Partnership Profile  Segment System Interface Diagram  Verify & Approve the Business Transformation Framework Note: The EA Team will work with the relevant architects to complete the documentation (NEW) NO UPDATES NEEDED (NEW) (UPDATED) Below is a summary of changes made to the Architecture Development Standards and Guidance document requirements Architecture Development Standards and Guidance Summary of Changes (NEW)

18. 17 EA Training at Potomac Yards– spaces still available Enterprise Architecture Training at Potomac Yard South, Room S-4350 (to register, email IT Training Program)email IT Training Program Monday April 28 - Wednesday April 30 (8:30 am – 3:30 or 4:30 pm)— Segment Architecture Thursday May 1 - Friday May 2 (8:30 am - 4:30 pm)— Solution Architecture Monday May 5 - Wednesday May 7 (8:30 am – 3:30 or 4:30 pm)— Segment Architecture Thursday May 8 - Friday May 9 (8:30 am - 4:30 pm)— Solution Architecture

19. 18 Additional presentations Emergency Management architecture (see handout)Joan Karrie IT Governance Support System updateLaurie Ford Postponed

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