Carriers case study

Amlin has established an electronic trading vision to enable the company to integrate either directly with broking markets or to clients and brokers using a trading service. They have put in place a gateway and workflow solution to handle electronic submissions and also to have the ability to download policy information to their back-office systems.

Amlin approached RI3K to create a set of interfaces between the Marketplace and their own underwriting systems with a view to underwriters reviewing submissions created on RI3K inside their own workflow solution but also accessing RI3K’s underwriting processes to manage subjectivities and complex binding.

RI3K and Amlin proceeded to integrate the Marketplace and Amlin systems using the ACORD quotation request, request for line and signed line request placing messages, as well as ACORD DRI messages for contract and supporting information. The RLC data message is sent with an accompanying link for the Amlin system to pull the submission documents or contracts which reside on RI3K.

This type of integration allows brokers to distribute their risks, documents and data directly to Amlin’s workflow where Amlin underwriters are able to set up their risks quickly and manage the quotation process inside their own environment. It provides a more compliant process, ensures that a consistent set of data and documents are being shared between broker and underwriter and allows Amlin to provide a better service back to their brokers.

At the point of binding a risk, Amlin underwriters access RI3K’s workflow to capture their written lines and any outstanding subjectivities. Final business terms and signed line advices are updated in Amlin’s systems automatically.

Technical specifications:

1. The following ACORD XML Messages from were used at the different stages of the life cycle of a risk:
   At the quotation stage, the Marketplace sends Amlin an ACORD quotation_request Placing Message and ACORD Document Repository Interface (DRI) Messages for the Contract and Supporting Documents.
2. At the firm order stage, the Marketplace sends Amlin an ACORD request_for_line_or_binder Placing Message and ACORD Document Repository Interface (DRI) Messages for the Contract and Supporting Documents.
3. When the placement is signed and closed, the Marketplace sends Amlin an ACORD signed_line_advice Placing Message and ACORD Document Repository Interface (DRI) Messages for the Contract and Supporting Documents.

The DRI Messages are based on the following:

1. Marketplace provides references and metadata details of the Contract and each Supporting Document in the Placing Message. This is sometimes referred to as DRI slice(s) in the Placing Message.
2. Amlin sends Marketplace an ACORD DRI RepositoryOperationRq Message to request the Contract and each Supporting Document.
3. Marketplace responds to each RepositoryOperationRq Message by sending an ACORD DRI RepositoryOperationRs Message with the related Contract or Supporting Document.
4. When the Placing Message and all DRI Messages have been exchanged, Amlin send the Marketplace an ACORD Acknowledgement Message to confirm successful receipt of all Messages or report any errors.

The Messages sent and received with Amlin use the following ACORD standards:

1. ACORD SOAP Message Standards 1.4.0
2. ACORD Placing Message Standards 2009-1
3. ACORD DRI Message Standards 1.2.0