SOA Presentation


Published on

Given to Fiserv Insurance Solutions clients in Tuscon, Arizona.

  • Be the first to comment

  • Be the first to like this

SOA Presentation

  1. 1. Proprietary  2008 Fiserv Insurance Solutions, Inc.
  2. 2. Taking SOA For A Spin Todd Eyler – CTO Mark Goetsch – VP, Strategy & Architecture Session 0000
  3. 3. Agenda <ul><ul><li>Why insurers are interested in SOA </li></ul></ul><ul><ul><li>Realizing value from SOA </li></ul></ul><ul><ul><li>Web services as an enabler for SOA </li></ul></ul><ul><ul><li>15 rules of the road for how SOA should be implemented </li></ul></ul>
  4. 4. New Demands From The Business Are Intensifying Too much complexity Compliance Aligning with Business Too many platforms High integration costs Lack of flexibility Business visibility Prove the value of IT Information overload Do more with less Deliver faster Become consumer-centric Simplify processes Grow revenue
  5. 5. Why Insurers Are Interested In SOA <ul><li>Why Is SOA Important? </li></ul><ul><li>Extension of legacy systems </li></ul><ul><li>Support of transactions with value chain </li></ul><ul><li>Improvement of processes in legacy systems </li></ul><ul><li>Making sub-processes that are reusable across systems or LOB </li></ul>BPM SOA Business-driven Focus on process effectiveness Business strategy and the associated IT tools Significantly IT Driven Often emerging out of legacy discussions Not always focused on process improvement Strong focus on integration Definition: Services-oriented architecture (SOA) means functions that are like legos - modular, distributable, sharable, and loosely coupled.
  6. 6. The Evolution of SOA for Insurers Server virtualization, BPM, golden copy CIF’s Web services, portals, data sharing for BI Underwriting, illustration, rating Policy, claims * Celent categories Sophistication Enterprise Value Services-Based Application Integration Application Componentization Business Process Architecture
  7. 7. Meaningful Tangible Benefits Are Being Realized Business Benefits Cost Reduction Productivity Revenue $$$$ IT & SOA Benefits Development Maintenance Re-use $$ Examples AAA Carolinas - 2 month ROI on data warehouse, SOA integration The Hartford – 15% overall reduction in maintenance costs Guardian Life – 30% reduction in development costs Hanover Insurance – doubled capacity of IT organization Met Life – 75% improvement in time to deploy services Penn National – 20-30% increase in STP rates for new business
  8. 8. <ul><li>Historical tracking of: </li></ul><ul><ul><li>Project costs </li></ul></ul><ul><ul><li>Project times </li></ul></ul><ul><ul><li>Project quality </li></ul></ul><ul><ul><li>Resource utilization </li></ul></ul><ul><li>Benchmarking against similar projects </li></ul><ul><li>Formalized reporting of successes, business value </li></ul>Diligent Tracking is Important to Prove the Value
  9. 9. Web Services and SOA
  10. 10. Web Services Are An Important Enabler for SOA
  11. 11. Implemented Using Common Standards
  12. 12. That Fit In With Current Existing Applications
  13. 13. How IT is Traditionally Implemented
  14. 14. What the Business Understands
  15. 15. SOA = Business View + Web Services
  16. 16. <ul><ul><li>Level of granularity for services </li></ul></ul><ul><ul><li>Function separation & versioning </li></ul></ul><ul><ul><li>Exception processes </li></ul></ul><ul><ul><li>Locating services </li></ul></ul>Service Service Service Service Service Service Service Service The Proliferation of Web Services Creates an Unmet Need for Improvements in a Few Key Areas
  17. 17. 15 Rules of the Road for Successful SOA <ul><li>Domains are either business functions or explicit “shared” functions. </li></ul><ul><li>A service should be exposed through only one domain. </li></ul><ul><li>Use a unique exception message or message number. </li></ul><ul><li>Always return either the requested message or an exception. </li></ul><ul><li>Log every exception independent of the service implementation. </li></ul><ul><li>Check the version of the service, and the version of the message. </li></ul><ul><li>Create an identity mechanism that will let you interrogate versions. </li></ul><ul><li>When a new version of a service is created keep the old version as well. </li></ul><ul><li>Have a “sunset” strategy where the service will be removed. </li></ul><ul><li>Every service entry has a readable description. </li></ul><ul><li>Provide version checking to the repository. </li></ul><ul><li>Provide “version forwarding”. </li></ul><ul><li>Use standardized messaging including standards like ACORD. </li></ul><ul><li>Use multiple related workflows to define a single service. </li></ul><ul><li>Use service level agreements with every service. </li></ul>
  18. 18. Web Services And SOA Together Offer Significant Value! <ul><li>Business Value </li></ul><ul><li>Functions not implementation. </li></ul><ul><li>Not bound to specific application. </li></ul><ul><li>“ Best of Breed” solutions. </li></ul><ul><li>Easily add outsourcing. </li></ul><ul><li>Predictably. </li></ul><ul><li>Operational not capital expense. </li></ul><ul><li>IT Value </li></ul><ul><li>Integrate unrelated technologies. </li></ul><ul><li>Manage services in a consolidated fashion. </li></ul><ul><li>Reduce the risk in upgrading technologies. </li></ul><ul><li>Reduce the need for highly specialized developers. </li></ul><ul><li>Separate between building and using. </li></ul><ul><li>Amortize costs across the enterprise. </li></ul>
  19. 19. Please Complete a Session Evaluation <ul><li>Tear out an evaluation sheet </li></ul><ul><li>Fill it out </li></ul><ul><li>Give it to the room host when you leave </li></ul><ul><li>Thank you for your feedback! </li></ul>
  20. 20. Proprietary  2008 Fiserv, Inc.
  21. 21. Questions <ul><li>Presenters’ Names </li></ul><ul><ul><li>Todd Eyler </li></ul></ul><ul><ul><li>781-400-5139 </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>Mark Goetsch </li></ul></ul><ul><ul><li>847-956-5700 </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>