250 likes | 370 Views
Case Study: Scaling SOA to the Enterprise: SOA Roadmap & Governance The Hartford Insurance Group, Inc. Benjamin Moreland Director, Foundation Services. The Hartford Financial Services Group, Inc. Founded in 1810 One of the largest investment and insurance companies in the United States.
E N D
Case Study: Scaling SOA to the Enterprise: SOA Roadmap & GovernanceThe Hartford Insurance Group, Inc. Benjamin Moreland Director, Foundation Services
The Hartford Financial Services Group, Inc. • Founded in 1810 • One of the largest investment and insurance companies in the United States. • Fortune 100 company • 30,000 employees • Two Companies: • Hartford P&C – Auto, Home, Business insurance • Hartford Life – investment plans, Life insurance, Group benefits
Outline • SOA Basics • SOA Roadmap • SOA Governance • Summary
SOA Basics • Def’n: A loosely-coupled enterprisearchitecture based on industry standards that enables businessgoals • SOA is based on industry standards • It must be measured against business goals • SOA is an EA philosophy
Hartford Business Drivers • Lower total cost of IT • Increased “Ease of doing Business” • Speed to Market • Increased business agility How do you get there? An SOA Roadmap
Outline • SOA Basics • SOA Roadmap • SOA Governance • Summary
SOA Roadmap • SOA is more than standards and technology • Standards • Technology • Architecture • Organization • Governance • Process • Strategy • Evolution based • Think strategically, act tactically • Bottom-up vs Top-down vs Middle-out
SOA Strategies Top Down Process-Driven Middle Out Service-Driven Bottom Up Project-Driven Business Architecture Business Processes Business Services (Functions) Technical Services SOA Tools (App Infrastructure) Infrastructure
Level 1 – Opportunistic SOA @ The Hartford • Standards & Technology • XML web services (1999) • SOAP, WSDL (2004) • Architecture • Application Reference Architecture 1.0 (2003) • Organization • Architects Collective (2002) • Governance • “Do No Harm”, communication policy (2004) • Strategy • Select low hanging fruit (SEMCI) 2003
Level 2 – Tactical SOA @ The Hartford • Standards & Technology • WSM, UDDI Registry, WS-Addressing (2004) • Enterprise Service Bus (2004) • BPEL, WSIF (2006) • WSRP, JSR-168 (2006 • Strategy • Metrics being reported (2006) • 5 year Business / IT plan (2005) • Architecture • Integration, Security Reference Architecture 1.0 (2006) • Application Reference Architecture 2.0 (2005)
Level 2 – Tactical SOA @ The Hartford (cont) • Governance • Effective EA governance process for large projects (2005) • Organization • Enterprise Architecture Group (2004) • Process • Standards Committee (2005) • Service Committee (2006) • Cookbooks for SOA tools (2005/2006)
Level 3 – Strategic SOA @ The Hartford • Standards & Technology • WS-BasicProfile • IAA / ACORD • BPM • Strategy • Progress Metrics, Service metrics • Business Architecture defined • Application Rationalization • Architecture • JIT Reference Architecture • 1 overall Reference Architecture
Level 3 – Strategic SOA @ The Hartford (cont) • Governance • SOA Governance IT Governance (Service level governance) • Business Services Catalog (WS-Lifecycle) • Organization • Services Committee (1st qtr 2007) • SOA Education • Process • ITIL, CMMi
The Hartford’s SOA Maturity Model (Roadmap) Automated Governance, Exception proc. Function based, Not org based MDA Bus. Agility, Real-time modifications BAM, EPM, TBD 4-tierBAM, EPM, TBD Monitor & Measure for Improvement, Iterative Dev. Process working, Incentives working SOA Center Of Excellence BP Simulation, BAM, CEP, Metadata Mgmt Shared Business Functions, SCA, WS-Eventing, WS-* BPM, BRE, Integrated Svs Env. BPEL, BPMN, Vertical XML (ACORD) SOA Roles & Responsibilities, SOA Education Service Granularity BPA, Realize service Reuse, SLAs Adopt service Reuse incentives BPEL, WSM, UDDI, (ESB) Identify Key Metrics, SOA Oper Model Interdeptmt governance Formal EA Grp, Score projects BPEL, WSIF, JMS, JCA, WS-Security Identify Repeatable Patterns, Services Architects Collective Web Services, App Servers, Portal App Ref. Arch v1.0, Infra. Svs Interdeptmt communication SOAP, XML, WSDL, WSRP, JSR-168 Low hanging fruit Strategy/ Process Standards Technology Architecture Organization Governance * with collaboration from Dr. Mohamad Afshar
The Hartford’s 2006 SOA Scorecard Standards Technologies Architecture Processes Strategy Governance Organization 5 4 3 2 1
Outline • SOA Basics • SOA Roadmap • SOA Governance • Summary
Governance • Governance is about getting people to do the right thing at the right time in the right way • “In 2006, lack of working governance mechanisms in midsize-to-large (greater than 50 services) post-pilot SOA projects will be the most common reason for project failure (0.8 probability)” • Massimo Pezzini, Gartner
Governance is Key to Delivering on SOA by Design Business Strategy Business Strategy Business Plan Supporting SOA Strategy Supporting SOA Roadmap Ensure Delivery With Low Risk & Control Governance with SOA Governance with SOA IT Governance IT Governance
Policy Creation, Communication & Enforcement Enterprise Architects Governance Committee Executives Business Analysts Create Manage Developers Monitor & Enforce Architects Policies IT Managers Administrators • Communicate • Issues: • Decision Rights • Input Rights
6 Steps to Successful SOA Governance Define Goals and Strategies Standards, Policies, Processes & Organization Refine and Go to the Next Level SOA Maturity Model These 6 steps allow a company to incrementally develop and mature their overall SOA and thus business goals Define Metrics Put Governance Mechanisms in Place Analyze and Improve Existing Processes
The Hartford’s SOA Governance Strategy • Level 1 • “Do No Harm” (2004) • Project Scoring for learning purposes only (2004) • Level 2 • Score all “architecturally significant” projects (2005) • Effective governance processes (2005/2006) • All services must be WS-I compliant, must have “contract ID” in SOAP header (2006) • Level 3 • Business Services Catalog process & tools • Services, Standards committee standards included in project assessments
Summary • SOA is not an ends in itself, it is a means to achieve business goals • Without an SOA roadmap and strategy, you cannot know where you are going • SOA roadmap (maturity model) must be incremental, not big bang • 3 SOA strategies: process-driven, services-driven, project-driven
Summary (cont) • Just as IT needs IT governance, SOA requires service governance to grow • 6 step SOA governance strategy can mature with your organization • Think strategically, act tactically!!!
Q&A • Thank You • Benjamin Moreland • The Hartford Financial Services Group • Director, Foundation Services, • Enterprise Architecture Group • Find me on: https://www.linkedin.com