Enterprise Architecture


Published on

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

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

No notes for slide
  • Agile: moving quickly and lightly, "the old dog was so spry it was halfway up the stairs before we could stop it" On strategic focus: Today, most clients spend only 10% of their technology budgets for new business innovation. 90% is required to operate and maintain their existing environment. The potential for NGBSI is to allow clients to spend much more of their budgets on innovation!
  • Allows for the evaluation of all IT investments in comparable terms and provides for the development of actionable investment recommendations based on the total value of an investment and the goals of the IT portfolio
  • Enterprise Architecture

    1. 1. NYC Technology Forum Enterprise Architecture Greg Lomow Chief Architect BearingPoint, Inc. November 6 th , 2008
    2. 2. Enterprise Architecture Session Agenda <ul><li>The purpose of Enterprise Architecture is to manage and align business processes with software components, systems, networks, operations and projects. </li></ul><ul><li>The goal is simple: to operate better, faster and cheaper by leveraging a consistent architecture throughout the enterprise. </li></ul><ul><li>This session will focus specifically on the newly created Enterprise Architecture from DoITT </li></ul><ul><li>Speakers </li></ul><ul><ul><li>Greg Lomow, Senior Manager, Public Services Solutions Group, BearingPoint, Inc. </li></ul></ul><ul><ul><li>Anthony Insolia, Department of Information Technology and Telecommunications (DoITT), City of New York </li></ul></ul><ul><ul><li>Jane L. Landon, Deputy Commissioner and Chief Information Officer, Department of Finance, City of New York </li></ul></ul>
    3. 3. Government Challenges <ul><li>Tight budgets </li></ul><ul><ul><li>“ Do more with less” </li></ul></ul><ul><li>Cost overruns </li></ul><ul><li>Non-Compliance </li></ul><ul><li>Redundant Processes, Data, Systems </li></ul><ul><ul><li>Rework, re-entry of data </li></ul></ul><ul><li>Out-dated, non-supported technologies </li></ul><ul><li>Stove-piped, non-integrated systems </li></ul><ul><li>Lack of standardization </li></ul><ul><li>Enterprise Architecture is integral to improving the government’s efficiency and effectiveness by </li></ul><ul><ul><li>Improving mission outcomes </li></ul></ul><ul><ul><li>Helping to deliver better services to citizens and business </li></ul></ul><ul><ul><li>Promoting collaboration among agencies for government-wide improvement </li></ul></ul><ul><ul><li>Maximizing technology investments to achieve better mission results </li></ul></ul><ul><ul><li>Facilitating horizontal and vertical integration of IT resources </li></ul></ul><ul><ul><li>Obtaining cost savings by eliminating or consolidating duplicative processes or systems. </li></ul></ul>
    4. 4. What is Enterprise Architecture <ul><li>Enterprise Architecture is … </li></ul><ul><ul><li>A planning framework for ensuring that an organization’s use of and investment in information resources and technologies align with and support its business needs </li></ul></ul><ul><ul><li>A means of looking holistically at an entire enterprise , across barriers that have developed over time in many organizations (functional, programmatic, or organizational stovepipes) </li></ul></ul><ul><ul><li>A view of the current environment ( baseline ), a vision for the future ( target ), and a plan for moving from the baseline to the target environment ( implementation plan , migration plan, or transition plan) </li></ul></ul><ul><ul><li>Just one interlocking piece of a broader planning framework that includes strategic planning, capital planning and investment control, budgeting, systems development/ acquisition life cycle management, and other key processes </li></ul></ul><ul><li>Enterprise Architecture IS NOT … </li></ul><ul><ul><li>Business process reengineering </li></ul></ul><ul><ul><li>A simple one-size-fits-all approach </li></ul></ul><ul><ul><li>Detailed system-level designs or architectures </li></ul></ul><ul><ul><li>A panacea that will solve all of an organization’s information management problems </li></ul></ul>
    5. 5. Why Enterprise Architecture <ul><li>Reduced time and cost of change </li></ul><ul><li>Adaptive to market changes </li></ul><ul><li>Platform that enables efficient changes to the business process </li></ul><ul><li>Leverage existing IT investment and exploit commonality </li></ul><ul><li>Do more with less </li></ul><ul><li>Lower deployment and maintenance costs </li></ul><ul><li>Speed of execution and deployment </li></ul><ul><li>Platform that allows reusing and redeploying assets across business initiatives </li></ul><ul><li>Ability to realize and monitor targeted benefits and ROI </li></ul><ul><li>Unlock IP from proprietary vendor technologies </li></ul><ul><li>Increased % of IT spend on business innovation </li></ul>
    6. 6. Enterprise Architecture and Enterprise Governance <ul><li>Enterprise Architecture provides structure to ensure that investment decisions and project efforts are in line with strategic goals, organizational standards, core principles, mission performance goals, and ability to execute. </li></ul>GOVERNANCE Enterprise Architecture Portfolio Management Mission Execution Measure & Evaluate Enterprise Performance Business Intelligence Mission Goals Principles Initiatives Business Improvements Strategic Plan Lessons Learned Technology Standards Investment Decisions New Systems & Processes Financial & Performance Measures Performance Measures GOVERNANCE GOVERNANCE GOVERNANCE
    7. 7. Enterprise Architecture Uses Select Control Evaluate Requirements Analysis/Design Develop Test Deploy O&M Identify Specify Configure Test Deploy O&M Strategic: Portfolio Management Solution: Solution Development Technical: IT Infrastructure
    8. 8. Enterprise Architecture Methodology Technical: IT Infrastructure Solution: Solution Development Strategic: Portfolio Management
    9. 9. Alignment Between Strategy, Performance Goals, Constraints and Proposed Investments <ul><li>Environmental Trends </li></ul><ul><ul><li>ET-19: Lack of Qualified Treatment Providers in the District </li></ul></ul><ul><li>Enterprise Business Strategies </li></ul><ul><ul><li>EBS-8: Treatment and Service Quality Management Program </li></ul></ul><ul><ul><li>EBS-10: Partner Evaluation Strategy </li></ul></ul><ul><li>Modernization Approaches </li></ul><ul><ul><li>MA-11: Customer Relationship Management (CRM) </li></ul></ul>
    10. 10. An Illustration of the Execution Framework: Identification of Different Architecture Views Technology View Integration, Infrastructure & Technology Reference Model Organizational View Communities of Interest, Roles, Organizational Structure Disaster Recovery Privacy Impact Controls Authentication Certification & Accreditation Performance View Goals & Objectives Business Services Process Threads Solution View Business Processes Business View Information View Use Case (UML) Enterprise Service Bus Shared Technical Services Technology Re-engineered Process & Activities Finance Enterprise Applications Value Chain Security View ERD/ IER Subject Areas <ul><li>Cash Mgmt. </li></ul><ul><li>Inspections </li></ul><ul><li>Compliance </li></ul><ul><li>Enforcement </li></ul><ul><li>Compensation </li></ul>HRMS Supply Chain Case Mgmt. Meta Data
    11. 11. Enterprise Architecture Frameworks: DoDAF, FEA and Zachman Frameworks
    12. 12. Enterprise Architecture Frameworks: Zachman Framework Physical Logical Conceptual Contextual Why How What Where When Who Business Drivers, Mission Alignment ConOps, Value Chain List of Business Objects and Subjects List of Locations List of Key Business Events List of Roles, COIs & Organization Requirements, Performance Objectives, Service Descriptions Business Services Process Flow, Process Definitions (BPMN) ERD, Information Exchange Matrix, Business Vocabularies Locations mapped to roles and processes Business Domain Event Models Mapping of roles and processes to COIs and Organization Business Activity Monitoring Business Process Management, COTS Applications Data Domain Services Infrastructure Domain Services Business Process Management, COTS Applications Security Domain Services (SSO) Business Rules, Business & Technical Service Levels Process Simulation (BPEL & UML) Use Cases (UML) Data Flow Diagrams, Business Taxonomy, Ontology, & Semantics Systems Architecture, Managed Services locations Process Orchestration User Profiles