Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Becoming a Connected Insurer With API-led Connectivity

1 237 vues

Publié le

Becoming a Connected Insurer With API-led Connectivity

Insurance firms are under threat from rising competition, low interest rates, and historically low rates of insurance. insurance. Learn how one of the oldest insurance firms in North America is increasing operational efficiency, improving customer satisfaction and driving future growth with Anypoint Platform.

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Becoming a Connected Insurer With API-led Connectivity

  1. 1. 2 Becoming a Connected Insurer with API-Led Connectivity Patricia Hines, CTP Industry Solutions Director, FS&I MuleSoft Teri Townsend, MBA, PMP Vice President Technology Sagicor Life Insurance Company Alex Sherry Senior Solutions Consultant MuleSoft
  2. 2. 3 Alex Sherry Claims Management Demo
  3. 3. 4 Business needs •  Richer customer engagement •  Empower agents/partners
  4. 4. 5 What’s holding us back •  Legacy services for internal consumption only •  Do we do nothing at all? •  Rip & replace core business capabilities? •  Change is dangerous -  Facebook, Microsoft, Dropbox, Google, Adobe
  5. 5. 6 What’s the solution •  Expose services •  Governance •  Modernized API for mobile device consumption
  6. 6. 7     Integra)on  Pla-orm   Anypoint  Studio   HYBRID   Accounts   Database   JDBC   Orchestra3on   Before Modernization Ac3vi3   REST   Ac3veMQ   JMS   Drools   Rules   3rd  Party   Registry   HTTP   WEB  Service  (SOAP)   HTTP/REST   Connector   JMS   Connector   Drools   Connector   Database   Connector   HTTP/REST   Connector  
  7. 7. 8     API  Gateway   Integra)on  Pla-orm   Anypoint  Studio   Claims   API   API  Manager   HYBRID   Accounts   Database   JDBC   Orchestra3on   Web  Services   Consumer   After Modernization Ac3vi3   REST   Ac3veMQ   JMS   Drools   Rules   3rd  Party   Registry   HTTP   WEB  Service  (SOAP)   HTTP/REST   Connector   JMS   Connector   Drools   Connector   Database   Connector   HTTP/REST   Connector  
  8. 8. 9 Claims Web Service
  9. 9. 10 Legacy Web Service for Claims The  Claims  department  ini3ally   implemented  a  web  service  to   expose  func3onality  
  10. 10. 11 Claims Services Modernized
  11. 11. 12 RAML for Delightful APIs Claims  dept  designed  a  RESTful  API  and  leveraged  the   mocking  service  to  engage  API  consumers  prior  to   implementa3on  and  allow  them  to  test  out  the  service.  
  12. 12. 13 Modernized Claims Service The  “APIKit  Router”  handles   incoming  RESTful  API   requests  and  routes  to  the   appropriate  flow  below   The  “Web  Service  Consumer”   provides  a  drop-­‐down   configura3on  to  access  a   web  service.   The  datamapper   components  translate  the   web  service  call  data  into   RESTful  JSON  responses.  
  13. 13. 14 API Governance Governing  who  can  consume  the   API,  at  what  rates  and  by  what   authoriza3on  mechanism  
  14. 14. 15 API Analytics
  15. 15. 16     API  Gateway   Integra)on  Pla-orm   Anypoint  Studio   Claims   API   API  Manager   HYBRID   Accounts   Database   JDBC   Orchestra3on   Web  Services   Consumer   After Modernization Ac3vi3   REST   Ac3veMQ   JMS   Drools   Rules   3rd  Party   Registry   HTTP   WEB  Service  (SOAP)   HTTP/REST   Connector   JMS   Connector   Drools   Connector   Database   Connector   HTTP/REST   Connector  
  16. 16. 17 Thank You

×