Enterprise Architecture (EA) Information Technology Project Review Committee

1. Enterprise Architecture (EA) Information Technology Project Review Committee

2. Enterprise Architecture • Background Federal Enterprise Architecture • Virginia’s Enterprise Architecture • Enterprise Business Architecture • Enterprise Business Model • Enterprise Architecture Next Steps • PPA Division Tasks and Activities • PPA Division Staffing Needs

3. Business-Driven Approach • Performance Model • Inputs, outputs, and outcomes • Uniquely tailored performance indicators Owned By Line of Business Owners Component-Based Architecture • Business Model • Lines of Business (functions and sub-functions) • Agencies, customers, partners • Service Component Model • Service domains, service types • Business and service components Owned By VITA EA • Data and Information Model • Business-focused data standardization • Cross-agency information exchanges • Technical Model • Service component interfaces, interoperability • Technologies, recommendations Federal Enterprise Architecture Models

4. Adaptation of the FEA for Virginia • Federal • Each agency must have an enterprise architecture • Must define how it relates to the OMB FEA models • Virginia • Enterprise Business Architecture (includes an adapted version of OMB’s Business Reference Model) • State government entities mapped to Virginia’s Business Model (AS IS) • Gap closing measures identified • “TO BE” Virginia Business Architecture created

5. Virginia’s Enterprise Business Architecture • Defines (from a business point of view): • Who we are • Where we are • What we do • Where we want to go

6. Virginia’s Enterprise Business Architecture • EBA Components • Organizational structure • Enterprise business model • Business strategies and strategic direction • “AS IS” enterprise business architecture • “TO BE” enterprise business architecture

7. Enterprise Business Model Structure

8. Business Areas • Services to Citizens - the mission and purpose of government • Mode of Delivery – mechanisms used to achieve the purpose of government and how services are delivered • Support Delivery of Services – policy, programmatic and managerial underpinnings that facilitate delivery of services • Management of Government Resources – resource management activities that must be performed to operate effectively

9. Services to Citizens – Lines of Business

10. Virginia EA Next Steps Develop “As Is” Enterprise Business Architecture Agencies/VITA/DPB Analysis to Identify Opportunities for Collaboration and Increased Efficiencies Agencies/VITA/DPB Develop “To Be” Enterprise Business Architecture Agencies/VITA/DPB IT Projects, Procurements, Budget Requests, Budget Recommendations Agencies/VITA/DPB Enterprise Priorities & Projects Identified Agencies/VITA/DPB Strategic Plans & Performance Measures Agencies/DPB

11. Policy, Practice, & Architecture Division • Part of the Strategic Management Services Directorate • Current Staff • Manager • 4 Architects

12. PPA Division Ongoing Activities • EA Review and Updates • Tech Domains (Platform, Network, Security, and Middleware) • External (Non EA Policies, Standards, & Guidelines • Internal VITA Policies, Standards, & Guidelines • EA Compliance Reviews (Strategic plans, projects, procurements) • Change Management Activities

13. Enterprise Architecture Development • Enterprise Business Architecture • Enterprise Information Architecture • EA Technical Domains • Database • Application • Information • Systems Management

14. Staffing Needs • Maintenance vs. Development • Highest priority (maintain existing components of the EA) • 3 additional enterprise architects needed

15. Q & A Contacts Paul Lubic Policy, Practice, and Architecture Division 804-371-0004 paul.lubic@vita.virginia.gov or Chuck Tyger Policy, Practice, and Architecture Division 804-371-5943 chuck.tyger@vita.virginia.gov