From Process to Data through Services

1. From Process to Data through Services Ric Gingell Chief Architect Amarta Thursday September 1st, 2005 VLDB 2005 Trondheim

2. Life and Pensions • Life insurance • Long term savings • Policies are long-term contracts - decades • Now an essential part of the social responsibility

3. Life and Pension Policy Administration • Well established • Fairly common processes • A few specialised areas • Well suited to automation • Well suited to batch processes

4. Business Processes Business Process Business Rules Manual Task Procedure Automatic Task Manual Task Procedure

5. New Business Process

6. Start Here Development Environment Runtime User Interface (HTML/JavaScript) Process Model Process Metadata Business Rules Business Rules Web Server UI Controller Data Model Database Schema UI Model UI Model RDBMS Generate

7. Life and Pensions Policy Administration Knowledge & Information Management Infrastructure Services Access, Contact & Presentation General Information Management Post E-mail Telephony Web (PC, PDA, EDI) Others Image Mgt. Content Mgt. FAQ Call-back SMTP Service Storage CTI/CLI PABX Scan/OCR Fax Voice Mail DocumentConstruction Personalisation Collaboration Auto Reply IVR Index Voice Record Backup ACD ‘EDI’ Messages Auto Response NLIVR Barcode DocumentDistribution HTTP Service Forms Reporting Archiving RT Monitoring Term Emul. Forms Proc. SMS Scripting VoIP Browser Act. Monitor E-mail Mgt. Search Print Services Replication Business & Channel Integration Intranet EAI Messaging Distribution Workflow Directory Svcs Extranet Unified Messaging Data Transformation Service Process Definition Service Messaging Service Distribution Service Process Execution Service System Mgt. ConfigurationManagement Migration Business Application Services Extraction SystemManagement Common Services Agent Desktop Service (Common Front End) Brand Interfaces Change Management Transform Sales Stats Business Rules ResourcePlanning Core Product Engine Loading General Ledger Unit Linked Pricing Valuations Compliance Policy Servicing Premiums Security Authorisation Reassurance Payments New Business Unit Allocation Agency Mgt. Application Server Event Notification Knowledge Management Authentication Box Management BACS Claims Underwriting Office Services HR Virus Protection Portal DMZ Services Search Data Services Analysis & Reporting Persistence Services Data Repositories Data Warehousing Other Structured Data Persistence Platforms Contact Repository Customer Repository Data Marts OLAP Network Unstructured Data Persistence Meta Data Product Data Repository Warehouse Repository

8. SO – the Four Tenets • Boundaries are Explicit • Services are Autonomous • Services Share Schema and Contract, not Class • Service Compatibility is based upon Policy

9. SOA – Basic Patterns • Document Processor • “How do you create a simple to use, well defined contract that remains compliant with the SO design tenets?” • Loose-coupling • Represent a business process as a complete unit of work • Idempotent Message • How can you ensure messages are idempotent • Insist on a unique “Unit of Work” ID in each message • Reservation • How can you maintain data consistency across a long running process? • Tentative operations • Confirmation, Cancellation, Timeout • Service Compatibility is based upon Policy

10. SOA – Baseline A XML XML RDBMS

11. SO – Common Customer Database • People have more than 1 Policy • Have to deal with more than 1 system – not happy • Ownership • Services for change • Replication, Versioning and Notification • Semantics • Keys

12. SOA - Composability

13. Conclusion • Service Orientation is Important for Insurers • Systems will change to loosely-coupled asynchronous collections of services • Far fewer assumptions, consistent architecture is essential • Tools, methodology and language need work