IMPART Phasing Discussion

1. IMPART Phasing Discussion 8/13/2009

2. Project Phasing • Agenda: • Discuss overall phasing of Troux capabilities • Talk through potential Phase 1 use cases for IMPART • Goal: • Determine what piece of IMPART to tackle first, and what to address second • What to do next: • Quickly identify who to partner with to make Use Case a reality • Begin defining use case in detail and gathering data

3. eaGov Base Capabilities

4. Potential Phase 1 Use Cases • Use Case 1: Priority Segment Architecture Analysis • Use Case 2: Office of Water Segment Question • Use Case 3: OCFO Question • Use Case 4: System to Performance Measure Relationship Question • Use Case 5: Mapping Systems to Enterprise Tools • Use Case 6: Cloud Computing Analysis • Use Case 7: QTS IT Infrastructure/Business Driver Analysis Plus • Use Case 8: Align Agency Systems to Standards • Use Case 9: Create Enterprise Transition Plan using Project and Program Milestones

5. Use Case 1: Priority Segment Architecture Potential Value • Will gain favor with segments • Will further mature segment architectures • Focus on EPA’s priority segments (Air/IT Infra) Risks of Early Adoption • Will need to interview segments to determine who should be chosen • Not using Troux’s time for building more complex collectors (ex: READ) Benefits of Early Adoption • Can show value to one specific segment and may gain other segment buy-in • Will understand the maturity of all the segments’ architectures after interviews Beneficiaries • One segment architect

6. Use Case 2: Office of Water Segment Question Potential Value • Quick ability to show architecture analysis in tool • Gaining a strong support partner and evangelist for IMPART Risks of Early Adoption • Setting precedent for catering to specific program needs • Not using Troux’s time for building more complex collectors (ex: READ) Benefits of Early Adoption • Architecture information already exists • Willing Volunteer • Working with mature segment (architecturally) Beneficiaries • OW Architects • OW Management

7. Use Case 3: OCFO Question Potential Value • Quick ability to show architecture analysis in tool • Gaining a strong support partner and evangelist for IMPART Risks of Early Adoption • Setting precedent for catering to specific system’s needs • Not using Troux’s time for building more complex collectors (ex: READ) • Unsure of OCFO’s Architecture needs at this stage of lifecycle Benefits of Early Adoption • Architecture information already exists in Metis format • Working with mature solution architecture information Beneficiaries • OCFO Architects • OCFO Management

8. Use Case 4: System to Performance Measure Relationship Question Potential Value • Setting precedent for catering to specific program needs • Not using Troux’s time for building more complex collectors (ex: READ) Risks of Early Adoption • Setting precedent for catering to specific program needs • Not using Troux’s time for building more complex collectors (ex: READ) Benefits of Early Adoption • High Visibility with management early in lifecycle • Uses Troux’s time for building complex collectors (ex: READ) Beneficiaries • Program Management • System Managers • ISS

9. Use Case 5: Mapping Systems to Enterprise Tools Potential Value • Addresses OTOP Management Priority • Highlights Enterprise Tool usage • Can be used to identify reuse statistics Risks of Early Adoption • Will need to gather and validate information and which systems are using enterprise tools (some exists) Benefits of Early Adoption • High Visibility with management early in lifecycle • Uses Troux’s time for building complex collectors (ex: READ) Beneficiaries • OEI Management • System Managers • Chief Architect • ISS

10. Use Case 6: Cloud Computing Analysis Potential Value • Getting ahead of data.gov and other Federal mandates for analysis Risks of Early Adoption • Represents future needs, not immediate value • Cost data needed Benefits of Early Adoption • High Visibility with topic management is interested in • Uses Troux’s time for building complex collectors (ex: CPIC) • Shows Investment Portfolio analysis capability Beneficiaries • All major system owners • OEI management

11. Use Case 7: QTS IT Infrastructure/Business Driver Analysis (Plus) Potential Value • OEI Management Visibility • Support of QTS • Showing how architecture information benefits IT Infrastructure planning Risks of Early Adoption • QTS IT Infra analysis was already completed, will we be able to show additional value? • Not focused on a segment Benefits of Early Adoption • High Visibility with topic management is interested in • Information exists in rough format • Could possibly expand analysis into another impact of business drivers across the agency Beneficiaries • QTS • OEI management

12. Use Case 8: Align Agency Systems to Standards Potential Value • OEI Management Visibility • Support of QTS • Showing how architecture information benefits technology planning Risks of Early Adoption • Data gathering needed on how systems are implementing standards Benefits of Early Adoption • Exposure of standards to systems in central location • Audit capability on which standards are in use and who is out of compliance • Could provide information on what technologies should become standard • Could provide information on what standards are not in use and support could be discontinued to save costs Beneficiaries • QTS • OEI management • Technology Standards Group

13. Use Case 9: Create Enterprise Transition Plan using Project and Program Milestones Potential Value • OEI Management Visibility • Gain insight into who will be adopting enterprise tools Risks of Early Adoption • No immediate value to the programs Benefits of Early Adoption • Helps EA Planning and Chief Architect • Helps OMB submission of ETP • Helps plan program’s adoption of enterprise tools Beneficiaries • EA Program • OEI management