EBA Presentation


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

EBA Presentation

  1. 1. Enterprise Architecture (EA) Information Technology Project Review Committee
  2. 2. Enterprise Architecture <ul><li>Background Federal Enterprise Architecture </li></ul><ul><li>Virginia’s Enterprise Architecture </li></ul><ul><li>Enterprise Business Architecture </li></ul><ul><li>Enterprise Business Model </li></ul><ul><li>Enterprise Architecture Next Steps </li></ul><ul><li>PPA Division Tasks and Activities </li></ul><ul><li>PPA Division Staffing Needs </li></ul>
  3. 3. Federal Enterprise Architecture Models <ul><li>Performance Model </li></ul><ul><ul><li>Inputs, outputs, and outcomes </li></ul></ul><ul><ul><li>Uniquely tailored performance indicators </li></ul></ul><ul><li>Business Model </li></ul><ul><ul><li>Lines of Business (functions and sub-functions) </li></ul></ul><ul><ul><li>Agencies, customers, partners </li></ul></ul><ul><li>Service Component Model </li></ul><ul><ul><li>Service domains, service types </li></ul></ul><ul><ul><li>Business and service components </li></ul></ul><ul><li>Data and Information Model </li></ul><ul><ul><li>Business-focused data standardization </li></ul></ul><ul><ul><li>Cross-agency information exchanges </li></ul></ul><ul><li>Technical Model </li></ul><ul><ul><li>Service component interfaces, interoperability </li></ul></ul><ul><ul><li>Technologies, recommendations </li></ul></ul>Component-Based Architecture Business-Driven Approach Owned By Line of Business Owners Owned By VITA EA
  4. 4. Adaptation of the FEA for Virginia <ul><li>Federal </li></ul><ul><ul><li>Each agency must have an enterprise architecture </li></ul></ul><ul><ul><li>Must define how it relates to the OMB FEA models </li></ul></ul><ul><li>Virginia </li></ul><ul><ul><li>Enterprise Business Architecture (includes an adapted version of OMB’s Business Reference Model) </li></ul></ul><ul><ul><li>State government entities mapped to Virginia’s Business Model (AS IS) </li></ul></ul><ul><ul><li>Gap closing measures identified </li></ul></ul><ul><ul><li>“ TO BE” Virginia Business Architecture created </li></ul></ul>
  5. 5. Virginia’s Enterprise Business Architecture <ul><li>Defines (from a business point of view): </li></ul><ul><ul><li>Who we are </li></ul></ul><ul><ul><li>Where we are </li></ul></ul><ul><ul><li>What we do </li></ul></ul><ul><ul><li>Where we want to go </li></ul></ul>
  6. 6. Virginia’s Enterprise Business Architecture <ul><li>EBA Components </li></ul><ul><ul><li>Organizational structure </li></ul></ul><ul><ul><li>Enterprise business model </li></ul></ul><ul><ul><li>Business strategies and strategic direction </li></ul></ul><ul><ul><li>“ AS IS” enterprise business architecture </li></ul></ul><ul><ul><li>“ TO BE” enterprise business architecture </li></ul></ul>
  7. 7. Enterprise Business Model Structure
  8. 8. Business Areas <ul><li>Services to Citizens - the mission and purpose of government </li></ul><ul><li>Mode of Delivery – mechanisms used to achieve the purpose of government and how services are delivered </li></ul><ul><li>Support Delivery of Services – policy, programmatic and managerial underpinnings that facilitate delivery of services </li></ul><ul><li>Management of Government Resources – resource management activities that must be performed to operate effectively </li></ul>
  9. 9. Services to Citizens – Lines of Business Workforce Management Environmental Management Unclaimed Property Energy Transportation Emergency & Disaster Mgt. Natural Resources Electoral Services Litigation & Judicial Activities Education Legislative Representation Economic Development Law Enforcement Defense & Virginia Security Income Security Correctional Activities Homeland Security Consumer Protection Health Community & Social Services
  10. 10. Virginia EA Next Steps Develop “As Is” Enterprise Business Architecture Agencies/VITA/DPB Develop “To Be” Enterprise Business Architecture Agencies/VITA/DPB Analysis to Identify Opportunities for Collaboration and Increased Efficiencies Agencies/VITA/DPB Enterprise Priorities & Projects Identified Agencies/VITA/DPB Strategic Plans & Performance Measures Agencies/DPB IT Projects, Procurements, Budget Requests, Budget Recommendations Agencies/VITA/DPB
  11. 11. Policy, Practice, & Architecture Division <ul><li>Part of the Strategic Management Services Directorate </li></ul><ul><li>Current Staff </li></ul><ul><ul><li>Manager </li></ul></ul><ul><ul><li>4 Architects </li></ul></ul>
  12. 12. PPA Division Ongoing Activities <ul><li>EA Review and Updates </li></ul><ul><ul><li>Tech Domains (Platform, Network, Security, and Middleware) </li></ul></ul><ul><li>External (Non EA Policies, Standards, & Guidelines </li></ul><ul><li>Internal VITA Policies, Standards, & Guidelines </li></ul><ul><li>EA Compliance Reviews (Strategic plans, projects, procurements) </li></ul><ul><li>Change Management Activities </li></ul>
  13. 13. Enterprise Architecture Development <ul><li>Enterprise Business Architecture </li></ul><ul><li>Enterprise Information Architecture </li></ul><ul><li>EA Technical Domains </li></ul><ul><ul><li>Database </li></ul></ul><ul><ul><li>Application </li></ul></ul><ul><ul><li>Information </li></ul></ul><ul><ul><li>Systems Management </li></ul></ul>
  14. 14. Staffing Needs <ul><li>Maintenance vs. Development </li></ul><ul><li>Highest priority (maintain existing components of the EA) </li></ul><ul><li>3 additional enterprise architects needed </li></ul>
  15. 15. Q & A <ul><li>Contacts </li></ul><ul><li>Paul Lubic </li></ul><ul><li>Policy, Practice, and Architecture Division </li></ul><ul><li>804-371-0004 </li></ul><ul><li>paul [email_address] </li></ul><ul><li>or </li></ul><ul><li>Chuck Tyger </li></ul><ul><li>Policy, Practice, and Architecture Division </li></ul><ul><li>804-371-5943 </li></ul><ul><li>[email_address] </li></ul>