Enterprise Architecture – Introduction…

1. Enterprise Architecture – Introduction… Why Enterprise Architecture - aligning Business with IT

2. … with the intent of avoiding chaos… … and even if an individual house is well architected, if each house is different (e.g. different electricity voltage, water pressure) then the city will not work…

3. Benefits with Enterprise Architecture • Align business and IT objectives and resources • Efficient decision-making through established principles, models, standards, and processes • Improve communication, prioritization, and governance of initiatives • Increase time-to-market by reducing lead time for installing and testing technology (have the technology ready before it is needed) • Simplify integration problems through compliance with architecture • Reduce costs by retiring duplicative or outdated assets • Provide a foundation for skills development • Follow an established roadmap for infrastructure development

4. Following phases are defined for the Enterprise Architecture evolvement Introduction Input Roadmap Principles Target Vision • Perspective • Architectural changes • Business changes • Organization • EA realization • Principles • what it is • how to define • what it defines • Target Vision • common understanding • definition of architecture • architectural framework • ‘to be’ architecture • ownership of HBG EA • Problem Statement • architecture • business • application • information • technology • infrastructure • governance • processes • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements

5. Enterprise Architecture Definition…

6. ….there are several – here is one EA enables: • Alignment between Business and IT • Governance • Transition • Realisation of Business and IT Strategies EA ensures the architecture is maintained and used EA provides reference material in many forms “The EA discipline defines and maintains the architecture models, governance and transition initiatives needed to effectively co-ordinate semi-autonomous groups towards common business and/or IT goals.“ “The EA discipline defines and maintains the architecture models, governance and transitioninitiatives needed to effectively co-ordinate semi-autonomous groupstowards common business and/or IT goals.” An IBM study agreed a definition that balances EA’s “upstream” and “downstream” values EA is not just passive or reactive, it is proactive EA works at many levels EA can address the business and IT domains

7. “good navigation” “good engineering” Two important aspects of Enterprise Architecture“upstream” (doing the right things) and “downstream” (doing things right) • Upstream: Doing the right things • Identifying, funding & resourcing the most important programmes, in line with the business strategy and within the investment budget, in the right sequence, and with effective programme management and control. • Downstream: Doing things right • Ensuring the solutions delivered by these programmes meet the needs of the business, work within the existing IT environment andcontribute towards the realisation of the enterprise’s IT strategy.

8. Enterprise Architecture layers and structure

9. Programme Architecture Programme Architecture Soln Outline Soln Outline Macro Design Macro Design Micro Design Micro Design Devt, etc. Devt, etc. Change Programs The gap between Business and IT is something that has to be manageable and controlled; how to plan, build and maintain Enterprise Strategy Business Opportunity Technology Availability Bus Strategy IT Strategy Fire & Hope Business Operating Environment and IT Infrastructure

10. Programme Architecture Programme Architecture Soln Outline Soln Outline Macro Design Macro Design Micro Design Micro Design Devt, etc. Devt, etc. Change Programs Enterprise Architecture can be the ‘vehicle’ to align Business with IT Strategy Enterprise Strategy Business Opportunity Technology Availability Bus Strategy IT Strategy Planning Enterprise Architecture Enterprise wide Focus Designand Delivery Business Operating Environment and IT Infrastructure Program Focus

11. Strategy = “the city’s purpose & goals” Enterprise Capabilities Business Architecture Transition Planning Governance IS Architecture Technology Architecture • System Design • = “the buildings” Programme Architecture Programme Architecture Soln Outline Soln Outline Macro Design Macro Design Micro Design Micro Design Devt, etc. Devt, etc. Change Programs Good EA planning and good EA engineering can be managed using a EA framework and a EA method Strategy Enterprise Strategy Business Opportunity Technology Availability Bus Strategy IT Strategy Planning Enterprise Architecture Enterprise Architecture = “the city plan” Enterprise wide Focus Designand Delivery Business Operating Environment and IT Infrastructure Program Focus

12. Strategy = “the city’s purpose & goals” Enterprise Architecture = “the city plan” • System Design • = “the buildings” Programme Architecture Programme Architecture Soln Outline Soln Outline Macro Design Macro Design Micro Design Micro Design Devt, etc. Devt, etc. Change Programs Enterprise Architecture links strategy formulation through ensuring that “the right things are done” - upstream EA Strategy Enterprise Strategy Business Opportunity Technology Availability Bus Strategy IT Strategy Doing the right things! Planning Enterprise Architecture ”Upstream EA” Good Navigation Enterprise wide Focus Designand Delivery Business Operating Environment and IT Infrastructure Program Focus

13. Strategy = “the city’s purpose & goals” Enterprise Architecture = “the city plan” • System Design • = “the buildings” Programme Architecture Programme Architecture Soln Outline Soln Outline Macro Design Macro Design Micro Design Micro Design Devt, etc. Devt, etc. Change Programs Enterprise Architecture assets ensure that “things are done right” when building specific solutions – downstream EA Strategy Enterprise Strategy Business Opportunity Technology Availability Bus Strategy IT Strategy Doing the right things! Planning Enterprise Architecture Enterprise wide Focus ”Downstream EA” Good Engineering Doing things right! Designand Delivery Business Operating Environment and IT Infrastructure Program Focus

14. Enterprise Architecture Framework Organising, storing and using architectural information (models and building blocks) in support of transitionplanning and delivery project guidance

15. The EA Framework consist of horizontal- and vertical aspects… OperationalAspect of Architecture External to architecture Functional Aspect of Architecture EnterpriseCapabilities A good EA is driven from an assessment of the capabilities needed by the enterprise BusinessArchitecture It is helpful to describe external influences in a consistent manner, such as “requirements” We need to include elements that help us deploy our Business & IT systems in a consistent and joined up fashion InformationSystemsArchitecture Technology Architecture

16. …and then sub-dividing it into a number of “vertical” aspects to complement our “horizontal layers” OperationalAspect of Architecture External to architecture Functional Aspect of Architecture (Strategy) Events People Activities Data Location EnterpriseCapabilities We need to describe the operational structure needed and used by the enterprise; together with the manner in which the enterprise’s building blocks are distributed across this structure BusinessArchitecture We need to describe the events that the architecture must support, in terms of their business purpose and their operational characteristics We need to describe the basic building blocks from which our systems are built. Typically, in an IT centric EA, these can be categorised into… InformationSystemsArchitecture ...And data; and the things required to support their storage and use within the enterprise’s IT systems People, their roles and skills; and the things required to give them access to the enterprise’s IT systems… TechnologyArchitecture ...Activities and Processes; and the things required to automate and support their execution within the enterprise’s IT systems…

17. This gives us a powerful 2 dimensional EA architecture framework, the WORK PRODUCTS - of the EA Consulting Method’s architecture neighbourhoods Operational Aspect of Architecture External to architecture Functional Aspect of Architecture But what is the nature of these work products? Models? Sets of Building blocks? Both? We need to think again about the these relationships… Strategy Events People Activities Data Location EnterpriseCapabilities Work Product BusinessArchitecture Work Product InformationSystemsArchitecture Work Product TechnologyArchitecture Work Product

18. The EA Framework provides the structure for defining and managing Enterprise Architecture assets and functions as a reference catalog for use in solution architecting EnterpriseCapabilities Capabilities and architecture principles are defined to reflect and be consistent with the business direction i.e. business strategy and IT strategy BusinessArchitecture Business components or activities define “what the business needs to do” to realize the capabilities i.e. a business architecture has no regard for the use of automation InformationSystems Architecture Application & data (business-specific) and technology (business-independent) services define “what IT needs to do” to support the business activities.An Information Systems Architecture describes those aspects of the business that are to be automated – sometimes known as the “business dependent IT architecture” TechnologyArchitecture Application and technology components are structured into standard arrangements called Reference Architectures i.e. a Technology Architecture describes the underlying, “business independent” IT architecture needed to support automation

19. The Enterprise Framework consist of Work Products – called ABB (Architectural Building Blocks) - used for documentation and guiding in system modelling OperationalAspect of Architecture External to architecture Functional Aspect of Architecture Strategy Events People Activities Data Location EnterpriseCapabilities Strategic CBM Information Resources Skills Resources Locations List Activity Resources Business Scenarios EA Guiding Principles BusinessArchitecture Enterprise Info Model Roles Business Activity Mdl Business Structure Business Event List Usage matrices Bus Strategy WPs Usage matrices Usage matrices And/or Bus Strategy WPs Locations Model Business Services Model Bus Strategy WPs Component Business Model Bus Strategy WPs Enterprise KPIs Skills Activities Information Business Operational RAs Business Functional Reference Architectures InformationSystemsArchitecture ApplicationGroups DataStores Deployment Unit Matrices Placement Guidelines And/or IS Strategy WPs Standard Use Cases User Groups IS Strategy WPs Application Services Model IS Strategy WPs Deployment Units IS) AC Map IS Strategy WPs Standard IS NFRS Data Function IS Functional Reference Architectures IS Operational RAs TechnologyArchitecture IT Components (s/w & h/w) Presentation Services ApplicationServices DataServices IT Nodes IT Systems Management WPs IT Strategy WPs IT Strategy WPs IT Strategy WPs IT Systems Operational WPs IT Strategy WPs Technology Functional Reference Architectures Technology Operational RAs

20. Enterprise Architecture – using a Method

21. Proposal and Engagement Planning ClientObjectives Enterprise Capabilities Current Environment EmergingOpportunities Business Architecture IS Architecture Strategic Gap Analysis Technology Architecture Governance The structure of the architecture neighbourhoods in the EA Method Transition

22. Enterprise Capabilities Business Architecture IS Architecture Strategic Gap Analysis Technology Architecture Governance The EA Method provides the process of developing the EA Framework Transition Business Directions Capability Model Strategic CBM Management Action Plan Transition Initiatives Resources Business Scenarios EA Guiding Principles Transition Management Strategy EA Overview Diagram Critical issues, opportunities & rec’ns Integrated Transition Plan Business Activity Mdl Business Structure Business Event List Enterprise Information Model Enterprise KPIs Usage Matrices Locations EA Neighborhood Gaps Ident’n EA Neighborhood Assessments EA Capability Assessment Roles Business Reference Architectures Application Groups Deployment Unit Matrices Standard Use Cases DataStores Deployment Units (IS) Standard NFRs IT Components IT Nodes User Groups Placement Guidelines IS Reference Architectures Technology Reference Architectures Decision Model Principles, Policies & Guidelines Architecture Management Processes Architecture ManagementRoles / Resp Architecture ManagementMetrics

23. Enterprise Capabilities Business Architecture IS Architecture Technology Architecture From the ‘Enterprise Architecture’ on ‘one page’ there is a relation to the EA Method and the EA Framework Enterprise Architecture Method Enterprise Architecture on one page Enterprise Architecture Framework

24. Enterprise Architecture Framework BusinessArchitecture IT Architecture Business Architecture IS Architecture Users Applications Data Market Market Business Plans Business Plans Insured Party Insured Party Sponsoring Organization Sponsoring Organization Prospects Prospects POLICY POLICY Insured Objects Insured Objects Policy Policy Insurance Product Insurance Product Policy Financials Policy Financials Info Info Objects Objects Claim Claim Technology Architecture Claimant Claim Claimant Claim Service Providers Service Providers Producer Producer Producer Compensation Producer Compensation Business Partners Business Partners TechnologyArchitecture Third Parties Third Parties External Agencies External Agencies Legal & Recovery Actions Legal & Recovery Actions Training, Education, Advice Training, Education, Advice Inquiries Inquiries Functional view User view Data view The notion of work product dependencies hints at another dimension in which to think about an EA’s architecture framework Enterprise Capabilities Capability Model Business Directions Strategic CBM Resources Business Scenarios EA Overview Diagram EA Guiding Principles BusinessArchitecture Showing only a few, representative, work product dependencies Business Activity Mdl Business Event List Business Structure Enterprise Information Model Enterprise KPIs Usage Matrices Locations Roles IS Architecture Business Reference Architectures IT Components IT Nodes Deployment Unit Matrices Application Groups Standard Use Cases Technology Reference Architectures Deployment Units (IS) DataStores TechnologyArchitecture Standard NFRs User Groups Placement Guidelines IS Reference Architectures

25. Enterprise Architecture Framework BusinessArchitecture IT Architecture Users Market Market Business Plans Business Plans Insured Party Insured Party Sponsoring Organization Sponsoring Organization Prospects Prospects POLICY POLICY Insured Objects Insured Objects Policy Policy Insurance Product Insurance Product Policy Financials Policy Financials Info Info Objects Objects Claim Claim Claimant Claim Claimant Claim Service Providers Service Providers Producer Producer Producer Compensation Producer Compensation Business Partners Business Partners Third Parties Third Parties External Agencies External Agencies Legal & Recovery Actions Legal & Recovery Actions Training, Education, Advice Training, Education, Advice Inquiries Inquiries Applications Data TechnologyArchitecture We can develop this way of thinking about an EA architecture framework a little more. Functional Aspect of Architecture Business Architecture A business architecture has no regard for the use of automation “line of automation” An information systems architecture describes those aspects of the business that are to be automated – sometimes known as the “business dependent IT architecture” Information Systems Architecture A technology architecture describes the underlying, “business independent” IT needed to support automation “line of business interest” Technology Architecture

26. Enterprise Architecture Deliverables From the abstract EA level to concrete documentations

27. ALL deliverables created by Solution Architects across the business and IT architecture domains should, ideally, be guided by the EA’s framework… PLAN BUILD RUN Business andIT environment Programmes & Projects 1 Enterprise Architecture 2 n BusinessArchitecture BusinessInfrastructure Business SolutionWork Products BA WP BA WP BA WP IT Solution Requirements Analysis WPs IS Architecture InformationSystemsInfrastructure IS Arch WP IS Arch WP IT Solution Architecture WPs IS Arch WP TechnologyArchitecture TechnologyInfrastructure TechnologyWP TechnologyWP TechnologyWP Solution Guidance Solution Deployment

28. …which may be at its most powerful when the Solution Architect also uses the Work Products PLAN BUILD RUN Business andIT environment Programmes & Projects 1 Enterprise Architecture 2 n BusinessArchitecture BusinessInfrastructure Business SolutionWork Products Business Events KPIs Business Process Model Involved Locations BA WP Logical Data Model Solution Business Structure BA WP Solution Business Roles Etc. BA WP IT Solution Requirements Analysis WPs IS Architecture InformationSystemsInfrastructure SCD Solution Use Cases Solution NFRs IS Arch WP IS Arch WP IT Solution Architecture WPs IS Arch WP Architecture Overview Diagrams Operational Aspect Functional Aspect ComponentModel Specified/Physical OM TechnologyArchitecture TechnologyInfrastructure Business Dependent components Conceptual Operational Model Etc. Etc. DeploymentUnits TechnologyWP Business Independent components Logical Operational Model Etc. Etc. TechnologyWP TechnologyWP Solution Guidance Solution Deployment

29. Enterprise Architecture Governance – ‘doing it right’ “Balancing good Enterprise Design with good Solution Design”

30. Proposal and Engagement Plan ClientObjectives Enterprise Capabilities Business Directions Capability Model Strategic CBM Resources Management Action Plan Transition Initiatives Business Scenarios EA Guiding Principles EA Overview Diagram Transition Management Strategy Integrated Transition Plan Critical issues, opportunities & rec’mendations Transition EmergingOpportunities Current Environment IS Architecture Business Architecture Business Services Model Business Structure Business Event List Component Business Model Locations EA Neighborhood Assessments Activities Info-mation EA Neighborhood Gaps Ident’n Business Reference Architectures Skills EA Capability Assessment Functional Operational Strategic Gap Analysis Technology Architecture Application Services Model ACMap IS deployment units Function ETF Data IT Components IT Nodes Placement Guidelines User Groups IS Reference Architectures Reference Architectures Functional Operational Functional Operational Governance Decision Model Principles, Policies & Guidelines Architecture Management Processes Architecture ManagementRoles / Resp Architecture ManagementMetrics EA Governance neighborhood - the Architecture Management Processes, Roles, Responsibilities.

31. Governance in a context of Enterprise Architecture Strategicintent Are we still moving in the right direction Are our target architecture still right? BusinessArchitecture Governance Enterprise ITArchitecture EA Transition Functional Operational Are we doing these projects the way we said we want them done? "This is the waythese projects shouldbe architected” "These are the projects we should do” Solution “Business as Usual” project prioritisation & planning Macro Design Micro Design Build Cycle Deployment Outline Solution Macro Design Micro Design Build Cycle Deployment Outline Strategicdelivery Solution Macro Design Micro Design Build Cycle Deployment Outline Solution Projects

32. Architecture P Project P Arch Architecture Dev’t Dev’t D D D D D An enterprise will use its Enterprise Architecture to guide the interpretation of its business and IT strategies across the multiple layers of its development Strategy Enterprise Architecture Architecture Infrastructure Architecture Dev’t Programme Programme, or Solution Architecture Infra. Proj

33. The Enterprise Architecture Governance consist of‘three bodies’ • Ensure solution designs comply with the architecture • Maintain the architecture Architecture Review Board • Decides on which architecture is best suited for the needs of the enterprise • Decides when a change in the architecture is needed • Prioritise Initiatives Technical Review Board Architecture Sponsors Enterprise Architects • Uses the architecture to best satisfy the project’s needs Project Design Authority Solution Architects

34. We have the ‘important peoples’ – approving the architecture… Invited Enterprise Architects Council chair Chief Architect Architecture Review Board Business Representatives Technical Review Board a.k.a. “Architecture Council”: maintaining the authority of the EA ARB TRB Project Design Authorities DA

35. ARB TRB DA …and we have the ‘clever peoples’ - creating the architectures Business experts (on secondment) Chief Architect Architecture Review Board Project Architects (on secondment) Enterprise Architects Technical ReviewBoard a.k.a.The Office of the Chief architect: maintaining the vitality and use of the EA Project Design Authorities

36. ARB TRB DA …and we have the peoples who will use the architecture in the solution projects Architecture Review Board Technical ReviewBoard Solution Projects with Design Authorities Project Design Authorities

37. ARB TRB DA These three bodies exercise a number of different processes… Is used by the TRB Is used by the TRB Is used by the ARB Selection Conformance Vitality Enterprise Architecture Management Processes Is used by the ARB Exceptions Communication Used by all

38. Common Services Portal Services Making an EA Using an EA Use Publish Create Govern Vitality On Demand – Technology Overview – Detail View Business Services … … … Reporting … Workflow Collaboration Acquired Services Personalization ETL Policy Based Orchestration Presentation … Services Integration Frameworks … Selection Business Connection Web Services Application Connectivity Services Adaptors/Connectors Events Mediation … Data Access Services License Mgmt Services Rating Billing Metering Services Conformance nt Vitality Policy Based Orchestration Capacity Management … Vitality Enterprise Architecture Management Processes Exceptions Communication ..that work together to ensure the architecture is managed and exploited to the benefit of the enterprise as a whole

39. Enterprise Architecture as a Management Tool Strategic and long term; Value Proposition Business Vision Business Product Roadmap General Management Product Development Architecture Office Planning and Design Product Line Plans Market Needs Operation Technical Vision Architecture Principle, Vision Architecture Roadmap Construction and Delivery

40. Enterprise Architecture Measurements”If you can’t measure it, you can’t manage it”

41. Metrics – how do we know EA is providing us value Why should you measure?What should you measure?How do you measure?What should you do with measurements?What are the metric traps?

42. The Value of EA Metrics • Helps us understand how activities contribute to business results • Motivates those responsible to reach highest potential • Guides / Drives decision making and behavior • Leverages strengths – identifies weaknesses / opportunities • Helps in resource allocation • Increases competitive edge through the deployment of technology

43. Metrics Metrics Metrics Value to the Business Value to the Business Value to the Business $6.3M $6.3M Cost Savings Cost Savings Cost Savings in costs savings identified by in costs savings identified by Costs savings identified by having EA mission and team in place having EA mission and team in place having EA mission and team in place $4.3M $4.3M Cost Avoidance Cost Avoidance Cost Avoidance in costs reduction identified by Costs reduction identified by in costs reduction identified by having EA mission and team in place having EA mission and team in place having EA mission and team in place Integration and Reuse Integration and Reuse Integration and Reuse 15 specific instances of reuse or Instances of reuse or 15 specific instances of reuse or integration savings from having EA integration savings from having EA integration savings from having EA discipline in place discipline in place discipline in place R R Risk Reduction Risk Reduction Risk Reduction 5 specific instances where the risk Instances where the risk 5 specific instances where the risk has been mitigated has been mitigated has been mitigated Time to Market Time to Market Time to Market 18 instances where EA has reduced Instances where EA has reduced 18 instances where EA has reduced the time to market the time to market the time to market Quality Quality Quality 7 instances where EA effected 7 instances where EA effected Instances where EA effected measurable quality improvement measurable quality improvement measurable quality improvement Leverage Leverage Leverage Instances of Leverage Resources 3 instances of Leverage Resources 3 instances of Leverage Resources L L not within CIO Office not within CIO Office not within CIO Office Metrics –”If you can’t measure it, you can’t manage it” IT and Business Metrics Scorecard EA metrics score cards EA Metrics Scorecard

44. Measurement – example

45. Hansabank Enterprise Architecture input Introduction Input Roadmap Principles Target Vision • Perspective • Architectural changes • Business changes • Organization • EA realization • Principles • what it is • how to define • what it defines • Target Vision • common understanding • definition of architecture • architectural framework • ‘to be’ architecture • ownership of HBG EA • Problem Statement • architecture • business • application • information • technology • infrastructure • governance • processes • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements For the ‘Input’ Team Exercise you are asked to use these ‘architecture viewpoints’

46. Defining Principles Fundamental truths or propositions which an organisation will use to make decisions about the selection, utilisation and deployment of all business and IT resources and assets, across the enterprise

47. Enterprise Architecture Principles Introduction Input Roadmap Principles Target Vision • Perspective • Architectural changes • Business changes • Organization • EA realization • Principles • what it is • how to define • what it defines • Target Vision • common understanding • definition of architecture • architectural framework • ‘to be’ architecture • ownership of HBG EA • Problem Statement • architecture • business • application • information • technology • infrastructure • governance • processes • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements

48. Proposal and Engagement Planning ClientObjectives Enterprise Capabilities EmergingOpportunities Current Environment Business Architecture IS Architecture Strategic Gap Analysis Technology Architecture Governance Principles are defined as part of the Governance Neighbourhood in the Enterprise Architecture Method Enterprise Guiding Principles Business Directions Capability Model Strategic CBM Transition Resources Management Action Plan Transition Initiatives Business Scenarios EA Guiding Principles EA Overview Diagram Transition Management Strategy Critical issues, opportunities & rec’ns Integrated Transition Plan Business Activity Mdl Business Structure Business Event List Enterprise Information Model Enterprise KPIs Usage Matrices Locations EA Neighborhood Gaps Ident’n EA Neighborhood Assessments EA Capability Assessment Roles Business Reference Architectures Application Groups Deployment Unit Matrices Standard Use Cases DataStores Deployment Units (IS) Standard NFRs IT Components IT Nodes User Groups Placement Guidelines IS Reference Architectures Technology Reference Architectures Project Guiding Principles Decision Model Principles, Policies & Guidelines Architecture Management Processes Architecture ManagementRoles / Resp Architecture ManagementMetrics

49. It is convenient to classify EA Principles to assist in understanding and communication. Guiding Principles: • Executive-level focus • Strong business flavour Used for the construction of EA 8 to 10 Guiding Principles Used to control and manage EA Guiding Detailed Principles: • Focus on more detailed and specific principles • Tend to have more of a technology focus Governance Principles 15 to 20 Detailed Principles Used by the Solution Projects Application Data Usage Principles • Policies and Standards will affect all levels of Principles • Architecture Decisions are Project Centric

50. Relation between Policy, Guiding Principle, Principle and Architectural Decision Static Change over time to meet new Requirements Policy Guiding Principle Principle Architectural Decision Business Enterprise Architect Solution Architect IT