X hits on this document

99 views

0 shares

0 downloads

0 comments

48 / 48

London Market Implementation of ACORD DRI Messages and Data

Table A.2 – Planned Delivery to Production

Planned Delivery to Production 11/9/06  

Planned Delivery to Production 27/11/06

RLC 2005.2,DRI V 1.2, AMS V 1.4

RLC 2005.2,DRI V 1.2, AMS V 1.4

Content

Content

A&S Repository

A&S Repository

Submission by DRI

'- index and store subsequent records

- Control an electronic work package submitted as a document using ACORD DRI standards

Lines of Business

Lines of Business

Direct, Fac RI, X/L, Binders, Lineslips

Lloyd's reinstatements including Sim RIP (single UMR)

New and Legacy business

DRI functions

DRI functions

Store all DRI metadata

Permit the document originator to add parties to the previously supplied ACL via Attribute Change.  This function will not be allowed for documents loaded to UCR page at this point. Attribute Change Will Not Trigger Notification at This Stage.

Establish new work space (General Utility Repository, GUR) in which folders may be created using the Create Folder mechanism or Download Folder Mechanism.

The ability to send a notification list on incoming DRI as ECF Change Request therefore will be no check against ACL and no handling of attribute change.

Facility to create a Folder in GUR Upon Receipt of a Create Folder DRI Message.   

The ability for trading partner to receive a document via DRI as a result of Notification list, on-line load or search. DRI Upload and DRI Notify and Download methods will be supported.

Facility to load documents received using ACORD DRI Standards into a folder in the GUR.  If a notification list is supplied with a document, parties on the list receive a notification that a document is loaded and are able to retrieve it using ACORD DRI standards.

Ability for trading partner to send a DRI Search, receive a notify in response and optionally download the target documents. Limited to the criteria specified in ECF change request 1c.

Receipt and Processing of an ACORD DRI Standard Download Folder Message, Resulting in the Creation of a Folder on the GUR.

Store all DRI metadata

Create folder & Outward Download Folder

Apply ACL provided with a DRI document referenced by UMR. Ignore ACL on DRI messages referenced by UCR. UCR Folder ACL updated by CLASS Data.  UMR Folder ACL NOT Updated by LIDS / POSH Data. Xchanging access to UMR documents enabled via Workorder processing.

Insert new document version

Expanded A54 Code set

Ability for trading partner to send a DRI search, receive a notify in response and optionally download the target documents - extended to include all Metadata

ECF 4.5 and DRI Change requests

As defined by the London Market ACORD DRI Technical Implementation Group and published on 31st March 2006, extend ACORD DRI ChangeAttribute message to include parties to be added to the Notification list and selective change to other metadata.  Outward Notification of any additions to NL by attribute change.  Excludes notification of any attribute change made on-line.

ECF TR Processing

Include specified Metadata in ACORD DRI ChangeAttribute message as defined by the London Market ACORD DRI Technical Implementation Group and published on 31st March 2006.

Undertake additional validation defined by London Market ACORD DRI Technical Implementation Group.  Move of business validation out of soap layer not included at this stage.

London Market Implementation of ACORD DRI Messages v1.doc

Page 48 of 48

Document info
Document views99
Page views99
Page last viewedSat Dec 03 05:10:02 UTC 2016
Pages48
Paragraphs1101
Words9338

Comments