Solution Providers Forum

1
Solution Providers Forum

• April 2007

2
Agenda

• Market Reform Programme Update
• General Update Rob Campbell
• AS Update Pat Talbot
• ACORD London Market Plans Roy Laker
• TCF
• London Plans
• ACORD DRI Update Drew Bolton

3
ACORD London Market Plans
4
ACORD Testing Certification Facility
5
ACORD Testing Certification Facility

• Software that confirms messages are ACORD
  compliant
• Test own systems as though interacting with real
  business partner
• Performs data and business validation
• Ensures new business partners are ready before
  becoming engaged
• ACORD have an effective and efficient method of
  certifying messages

6
London Plans
7
London Projects the ACORD involvement

• Placing
• Implement the ACORD Slip (GPD)
• Implement ACORD Placing message
• AS
• Implement AS Repository
• Implement ACORD messages for Bureau and non
  Bureau accounting
• Claims
• Implement Electronic Claims File

8
ACORD Implementations

• The ACORD messages are usually large with lots of
  functionality
• Organisations tend to implement in bite size
  chunks
• Start with skinny messages
• Enhance functionality gradually
• Roadmaps are needed to explain implementation
  phases and plans
• Implementation guides are developed that reflect
  the agreed phased implementations
• Benefits
• Implementations are tighter, simpler, more
  manageable and cost effective

9
Placing
Quote
Place
Endorse
10
Placing
Quote
Place
Endorse
Implemented
Implemented
MR slip
G6
Implemented
Complete pilot end Q2 2007
MRSIG
G6 phase 1
Implementation from June 2007
G6 phase 2 (Two-way messaging)
11
Placing
Quote
Place
Endorse
Implemented
Implemented
MR slip
G6
Implemented
Complete pilot end Q2 2007
MRSIG
G6 phase 1
Implementation from June 2007
G6 phase 2 (Two-way messaging)
Completed - awaits MRG decision on rollout
GPD
Update to include MRSIG Q3 2007
PLACING IMPLEMENTATION GUIDE
Publish June 2007 (G6 incorporated)
PLACING IMPLEMENTATION GUIDE
DOCUMENT REPOSITORY INTERFACE IMPLEMENTATION GUIDE
Re-publish June 2007 with London rules
incorporated
TESTING AND CERTIFICATION FACILITY

• Already implemented with London DRI rules
  included
• Support for placing targeted for June 2007

12
Global Placing Document (GPD)

• The ACORD Slip
• Implementation Guide with examples
• Originally based on LMP (MR) Slip
• Extended to include additional content for
  specific areas of business
• GPD is mapped to the ACORD Placing message

13
Placing Implementation Guide (PIG)

• An implementation guide for the ACORD Placing
  message Processes and data required at each
  stage
• Build client agent negotiations about the
  structure of a proposed placement. ACORD messages
  allow agents to propose terms for their client to
  review and approve or decline.
• Quotation where a client (or their agent)
  approaches one or more carriers for a quotation.
  ACORD messages allow clients, carrier and agents
  to request and provide quotations.
• Client Approval where a client has engaged an
  agent and wishes to approve their work before any
  contracts are placed. ACORD messages allow
  clients to approve the work of their agents
  before the placement is continued.
• Order the process of binding and formally
  accepting a contract. ACORD messages allow for
  clients and carriers to enter into a binding
  contract (either directly or via their agents),
  as well as indicate declinatures, supply
  conditions and manage contracts post-bind.
• Endorsement the amending of a contract after it
  has been bound, ACORD messages allow clients,
  carrier and agents to propose, agree and notify
  endorsements.

14
Placing
Quote
Place
Endorse
Implemented
Implemented
MR slip
G6
Implemented
Complete pilot end Q2 2007
MRSIG
G6 phase 1
Implementation from June 2007
G6 phase 2 (Two-way messaging)
Completed - awaits MRG decision on rollout
GPD
Update to include MRSIG Q3 2007
PLACING IMPLEMENTATION GUIDE
Publish June 2007 (G6 incorporated)
PLACING IMPLEMENTATION GUIDE
DOCUMENT REPOSITORY INTERFACE IMPLEMENTATION GUIDE
Re-publish June 2007 with London rules
incorporated
TESTING AND CERTIFICATION FACILITY

• Already implemented with London DRI rules
  included
• Support for placing targeted for June 2007

15
Accounting and Settlement
Close
Account
Settle
16
Accounting and Settlement
Close
Account
Settle
Guide for ongoing reference
AS Strategic
Implemented
AS phase 1
Signing messages BSM, CSM, USM
Implemented
Generally available from October 2007
ELPAN2
Implemented internationally, not yet in London
Peer to Peer accounting
17
Accounting and Settlement
Close
Account
Settle
Guide for ongoing reference
AS Strategic
Implemented
AS phase 1
Signing messages BSM, CSM, USM
Implemented
Generally available from October 2007
ELPAN2
Implemented internationally, not yet in London
Peer to Peer accounting
Publish June 2007 with ELPAN2 and EBOT
requirements incorporated
ACCOUNTING CLAIMS IMPLEMENTATION GUIDE ELPAN2
Bureau EBOT Non Bureau
DOCUMENT REPOSITORY INTERFACE IMPLEMENTATION GUIDE
Re-publish June 2007 with London rules
incorporated
TESTING AND CERTIFICATION FACILITY

• Already implemented with London DRI rules
  included
• Support for Accounting targeted for August 2007

18
Claims
Advice
Payment
Settle
19
Claims
Advice
Payment
Settle
Implemented
Implemented
CLASS (Company market)
Signing messages BSM, CSM, USM
Rolling out
CLASS (Lloyds)
Rolling out
ECF
Implemented internationally
Peer to Peer claims
20
Claims
Advice
Payment
Settle
Implemented
Implemented
CLASS (Company market)
Signing messages BSM, CSM, USM
Rolling out
CLASS (Lloyds)
Rolling out
ECF
Implemented internationally
Peer to Peer claims
ACCOUNTING CLAIMS IMPLEMENTATION GUIDE EBOT
Non Bureau
Publication with EBOT requirements targeted June
2007
DOCUMENT REPOSITORY INTERFACE IMPLEMENTATION GUIDE
Re-publish June 2007 with London rules
incorporated
TESTING AND CERTIFICATION FACILITY
Already implemented with London DRI rules included
21
ACORD Key dates for London in 2007

• TCF
• DRI messages Complete
• Placing messages June 2007
• Accounting messages August 2007
• Placing Implementation Guide
• Complete for current work load June 2007
• Updated for London Endorsements Q3 2007
• Accounting Implementation Guide
• EBOT June 2007
• ELPAN2 June 2007
• DRI
• Guide enhanced June 2007
• Forums
• IT Club Ongoing
• Service Providers Forum Ongoing

22
ACORD DRI Update
23
Agenda

• What DRI is
• Why send a message triggers
• Message creation step by step
• What a message looks like
• Constructing a message step by step
• Responses
• What is checked and when
• Documentation available

24
What DRI is

• Purpose
• Transfer insurance documents with insurance
  metadata (UMR/UCR etc)
• Access market-based repositories (e.g. IMR)
• Control access rights to documents
• Processes
• Supports
• Document push
• Pull
• Search and Retrieval
• Complements and supports the exchange of
  structured data via ACORD RLC messages
• Benefits
• Brokers can share documents with many parties via
  a single interface
• Removes system-specific quirks
• Carriers do not need multiple log-ins for each
  broker
• Leverages existing ACORD implementations
• Provides full audit trails and security

25
Why send a message the triggers

• You want to send a document to someone (Push)
• Upload to another repository through Upload
  message
• You want to let someone know a document is
  available for retrieval (Pull)
• Notify other repository in Notify message
• Alternately embed notification inside a RLC
  business message (e.g. Placing, Technical
  Account)
• Download to your repository in Download message
• You want to search someone elses repository and
  download file(s) as a result (Search Retrieve)
• Automated search through Search message
• Download to your repository through Download
  message

26
Agenda

• What DRI is
• Why send a message triggers
• Message creation step by step
• What a message looks like
• Constructing a message step by step
• Responses
• What is checked and when
• Documentation available

27
Overview

• Two DRI messages
• Two messages a request (Rq) response (Rs)
• You must send a DRI Response message to every DRI
  Request message you receive
• Seven functions, four in common use in London.
• Major Upload, Download, Search, Notify
• Sent using AMS
• 8 functions only two used in London
• Each consists of a pairs a request (Rq) and a
  response (Rs)
• You must send an AMS Response message to every
  AMS Request message you receive
• Two functions are
• Call/Call synchronous (often used for Search)
• AMS CallRs and DRI Rs must both be sent
  immediately
• Both responses sent in the same, single, message
• Inbox/Post asynchronous (often used for
  Upload/Download/Notify)
• AMS PostRs must be sent immediately
• DRI Rs is then sent later via a new PostRq
  message
• This must also be responded to with a PostRs.

28
Example Flow
29
Message creation step by step

• An XML message is created according to the
• DRI standard (Document repository
  Interoperability)
• Details of the document(s) name, size, filetype
• It may also contain insurance meta data from the
• RLC standard (Reinsurance Large Commercial)
• Details of the relevant claim / contract
  UMR/UCR
• The files are attached to the message (if there
  are any)
• For example, they would be sent with an Upload
  message, but not with a Search message.
• The message and files is then wrapped up and sent
  using the
• AMS standard (Acord Messaging Service)
• This requires a MIME-standard message to be
  created and sent via SOAP over HTTP

30
What does a message look like?

• All messages have the same layout
• HTTP used to send the message
• MIME used to separate different parts of the
  message
• SOAP Envelope in first MIME part
• AMS message inside body
• Business message in next MIME part
• Files then added, each in their own MIME part.

31
A DRI message from top to bottom
32
Sending a message the transport layer

• To establish the HTTP connection
• Make sure you know and can contact the remote
  servers IP address
• Use the recipients public key to encrypt the
  session
• Use HTTP POST (not GET)
• Add HTTP/MIME Headers
• Content-Type
• multipart/related type"text/xml
• boundary ltboundary stringgt
• startltcontent ID of SOAP MIME partgt (optional)
• Content-Length
• Length of entire message in bytes
• SOAP Action
• see ACORD AMS SOAP Guide, 6.6.2 9.3
• User-Agent, Host, Accept Connection (etc)
• Set by your web server

33
Sending a message the first MIME part

• Add a MIME part to the message
• MIME boundary
• Use the string listed in the MIME header
• Content-Type (again)
• For XML, this must be set to text/xml
  charsetutf-8/16/32
• Content-Transfer-Encoding
• 8bit or binary for XML
• Content-ID
• Unique identifier free text, often but not
  always a GUID
• Content-Length
• Length of this part of the message
• Insert a SOAP Header
• Defines how the message should be processed
• Contains security signature information
• Insert a SOAP Body
• Contains AMS message defines
• Sender, Receiver, Roles (broker, insurer, service
  provider etc)
• Identifies business message location, ID and type
• Lists message manifest what is in the message,
  and its content-ID

34
Sending a message the remaining MIME parts

• Add another MIME part to the message
• MIME boundary Content Length as before
• Content-ID
• This must be the ID listed in the AMS manifest
• Content-Type
• For XML, this must again be set to text/xml
  charsetutf-8/16/32
• Otherwise set it to the relevant file type e.g.
  application/pdf
• Charsets only need be declared for text MIME
  parts (XML, RTF, CSV etc)
• Content-Transfer-Encoding
• 8bit or binary for XML
• binary or base64 for files
• Add the business message or file suitably
  encoded
• Then start a new MIME part for the next item

35
Agenda

• What DRI is
• Why send a message triggers
• Message creation step by step
• What a message looks like
• Constructing a message step by step
• Responses
• What is checked and when
• Documentation available

36
Responses

• Three level of responses
• All must be given in case of success otherwise
  stop at first failure
• HTTP (synchronous immediate response)
• HTTP 400/Bad Request or 500/Server Error if
  problem
• E.g. SSL failure, or message truncated
• Otherwise HTTP 200/OK
• SOAP/AMS (synchronous immediate response)
• Send SOAP Fault if severe failure
• E.g. MIME part missing, or SOAP/AMS XML not
  well-formed
• Send AMS rejected response if other problem
  with message
• E.g. Message failed schema validation, or sender
  not known
• Otherwise sent AMS received response
• DRI (either synchronous or asynchronous sent
  later)
• Send DRI rejected message if problem
• E.g. requested document not found, or UMR not
  recognised
• Otherwise send DRI acknowledged message
• Full list of checks and possible reasons for
  rejection given in ACORD AMS SOAP Guide 7.6.2

37
Agenda

• What DRI is
• Why send a message triggers
• Message creation step by step
• What a message looks like
• Constructing a message step by step
• Responses
• What is checked and when
• Documentation available

38
Documentation

• AMS SOAP Guide v1.4 (latest version 1.5)
• Guide to using MIME, SOAP and AMS
• DRI Reference Guide v1.2 (latest version 1.3)
• Guide to using DRI
• DRI/RLC/AMS Integration Guide (draft)
• Guide to using DRI with RLC and AMS in London
  Market
• Connectivity Best Practice v1.0
• Guide to project managing ACORD implementations
• List of common mistakes

39
Gibson Hall17 18 October 2007
40
ACORD Forum London

• Strategies for Today Visions for Tomorrow
• Gibson Hall no registration fee.
• Program
• Dennis Mahoney, Keynote
• Transforming the international insurance
  business 
• Anticipating 750 delegates during event.

41
Opportunities

• Stalls 3mX3m member/non member pricing.
• Top sponsorships include stall and video
  presence.
• Specific item sponsorships available.
• See flyer for details and pricing.
• For up-to-date information
• www.acord.org/londonforum

42
For more information

• Or to discuss creative ideas
• Call Rick Gilman at 020 7648 4413
• or
• Alisen Herman via email at aherman_at_acord.org

43
World Headquarters Two Blue Hill Plaza 3rd
Floor Pearl River, NY 10965 USA
1 845 620 1700

SLIDE 43