Enforcement Targeting & Data Division (ETDD) Architecture

1. Enforcement Targeting & Data Division (ETDD) Architecture Scope, Accomplishments, Challenges ETDD Architecture Group

2. Topics • What we’re doing • What we’ve accomplished • Our challenges ETDD Architecture Group

3. The charge to the ETDD Architecture Group • per the Office of Compliance A/B/C priority list…“Continue planning and implementation of ETDD Information Architecture”or, as we see it… • “Develop an initial ETDD architecture that will meet the needs of OC and its customers” ETDD Architecture Group

4. What that means… This is the part we’re doing, but just for an ETDD Architecture (not for the entire Enforcement & Compliance segment) ETDD Architecture Group

5. What that also means… We’re addressing boxes 1 and 2 only ETDD Architecture Group

6. Our Overall Approach • Using architecture as our methodology: • Confirm our strategic intent for the project • Describe our baseline state, • Identify our desired target state, • Develop an actionable plan for moving from baseline to target, and • Propose an approach for maintaining the architecture over time. ETDD Architecture Group

7. What we’ve accomplished • Developed a collaboration site, core team, management team • Drafted a charter and project plan • Obtained advice and education • Reviewed last year’s architecture thoughts • Explored ETDD’s functions, drivers, challenges • Developed some initial priority principles • Worked to clarify our strategic intent, begin documenting our baseline, and begin identifying strategic improvement opportunities ETDD Architecture Group

8. What we’ve accomplished – selected artifacts – • Major drivers for ETDD • Initial priority principles (coming from our internal pain points) • Charter and project plan • Product-stakeholder lists, and matrix • Operational context diagram(s) • SWOT analysis ETDD Architecture Group

9. Some Drivers and Challenges • Some Other Challenges • E&C performance measures are constantly changing • Other organizations want us to implement their prototypes • CWA Enforcement Action Plan’s many new ideas • Push for universal e-reporting from permittees • Demand for increased agility • Competition from other solutions providers Business drivers • Shrinking federal/state budgets • New enforcement goals & evolving programmatic needs • Push for more transparency (of data, of our processes) • Increasing pace of technological change • Increased desire to manage from data ETDD • Design drivers • Portable devices • Virtual & cloud computing • Savvy, demanding users with high expectations for speed, capability & ease of use • Privacy & security concerns ETDD Architecture Group

10. Draft Architecture Principles • Common Vocabulary & Data Definitions – data are defined consistently throughout the enterprise, and the definitions are understandable and available to all users. • Primacy of Requirements – all plans made and actions taken are in satisfaction of requirements, and all requirements are identified and prioritized. • Design for Concepts (technology independence) – we design for the concepts and remain independent of specific technologies. • Control Technical Diversity – we use unified toolsets & technologies to minimize the cost of maintaining expertise in, and connectivity between, multiple processing environments. • Enterprise Perspective – we manage our data, applications, websites, IT services, IT infrastructure, and IT contracts as one division. ETDD Architecture Group

11. Architecture Group Charter • Mission alignment for the program purpose • A challenging goal for the project • Ambitious objectives • Few assumptions, but many serious constraints • A clear scope and approach ETDD Architecture Group

12. Overall Project Plan We also have a detailed draft project plan in Microsoft Project ETDD Architecture Group

13. ETDD’s Major Stakeholders • General Public & Interest Groups • Regulated Community • Co-Regulators • OECA Offices • Other EPA Offices • Other Federal Government (Agencies, Branches, Departments) ETDD Architecture Group

14. ETDD’s Major Products • Specified, raw datasets • Information and reports (derived from data) • Systems, software, and databases • Customer service products • Policies and guidance ETDD Architecture Group

15. Product-Stakeholder matrix ETDD Architecture Group

16. SWOT analysis ETDD Architecture Group

17. Our challenges (for now) • What strategic/performance improvements do we really want to end up with? • What artifacts are essential for our sub-segment? • How can we do this at a level commensurate with the resources dedicated to it? • How can we get ahead of the investment decision-making? • What should we do next? ETDD Architecture Group