Transcript Global Claims Definition project

Insurers’ Market Repository –
Where are we, and where are we going?
Gary Bass, Pat Talbot and Laura Bramble
20th May 2009
•
AGENDA
•
Brief History of the IMR
•
Some useful IMR Statistics
•
IMR Infrastructure Upgrade
•
IMR Security Model Enhancements (ACLs)
•
Binders
IMR Usage
•
Some useful statistics
•
Nos. of Users at January 2008
1800
•
Nos. of Users at April 2009
5763 + 316%
•
Premium transactions during 2008
885000 per month
•
Premium transactions to April 2009
311000
•
933000 +5%
Annualised
•
ECF Claims processed during April 2008
•
ECF Claims processed during April 2009
•
Nos of documents in IMR at April 2009
•
Daily average of docs added
•
Nos. DRI Messages per month
284000
•
All Contractual SLAs (17) currently
Green
8000
17500 +118%
5,577,000
18000 per day
IMR Infrastructure Upgrade
Background
•
The IMR is now more than 5 years old
•
The underlying third party document management software is being upgraded
•
Existing hardware being replaced with new
•
Software is being upgraded
•
The ‘look and feel’ of all IMR screens will change
• Consistent font size
• Consistent use of field names on all screens
• Consistent layout of fields, columns etc
• What will not change
• Absolutely no changes to IMR functionality
• Absolutely no changes to navigation of IMR screens
IMR Infrastructure Upgrade
•Market Acceptance Testing (MAT)
•
As there are no functional nor navigational changes to IMR – MAT will be ‘risk based’
•
Testing will be minimal, but will cover all A&S and ECF processes (we have 26A&S
test scripts and 28 ECF test scripts)
•
Organisations from all Communities, plus 4 Software houses taking part (16 Orgns in
total)
•
MAT will only commence once XIS internal test plan has been reviewed and ‘sign off’
by Project Board
•
MAT exit (success) criteria agreed by all parties
•
Planned Implementation date July 6th, 2009
• MAT status
•
XIS Internal testing two week delay in completion
•
MAT will take 4 weeks to complete
•
Currently confident that new (version) IMR will be Implemented as planned
IMR Security Model – Enhancements
The objectives of the IMR Security Model are:
1.
To deliver a Solution to support all standard and identified ‘exception’ user access
scenarios
1.
Exception scenario’s being
1.
2.
3.
4.
5.
Mid Term Broker Changes
Mid term carrier changes
Third Party Access
Conflicts of interest
Confidential terms.
2.
To deliver functional enhancements to the IMR to provide a document access
solution for all identified ‘exception’ scenarios.
3.
To deliver functional changes to other impacted London Market systems in order to
support end-to-end business processes for all identified ‘exception’ scenarios.
4.
To standardise, where-ever possible, the processes for the processing of user
access requirements in all identified ‘exception’ scenarios.
IMR Security Model Enhancements
•
What will the changes mean
•
Approx 7-9% increase in transactions
•
Exception ‘scenarios’ will be in scope, thus increased A&S and ECF usage
•
Further barrier lifted for the removal of paper from the Market –
Reform
Agenda – “bring all premiums and claims into scope for electronic processing”
•
ECF and A&S extended to Third Party Agencies who in future will be assigned
‘roles’ to carry out specific functions on each contract
•
Ability to ‘manage’ Conflicts of interest managed at document or user level
•
Ability to maintain ‘confidentiality of terms’ for all vertical and Multi section policies
•
Fully auditable
•
Security Access in place to enable Binder Prototype to progress
Project Delivery Plan
Task/Step
Resp
January
February
March
April
May
June
July
August
September
October
November
December
5 12 19 26 2 9 16 23 2 9 16 23 30 6 13 20 27 4 11 18 25 1 8 15 22 29 6 13 20 27 3 10 17 24 31 7 14 21 28 5 12 19 26 2 9 16 23 30 7 14 21 28
1 Functional Design
BA
## ## ## ## ## 5.0 5.0
2 High-Level Technical Design
PM
## ## ## ## ## ## 7.5
Detailed Delivery Estimates Released
LIMCLM Changes Notified
3.1 Detailed Technical Design
PM
## ## ## ## ## ## ## ##
3.2 Build & Unit Test
PM
4.1 Test Planning & Control
PM
4.2 System Test Execution
TPM
5.1 UAT/MAT
PM
## ## ## ## ## ## ## ## ## ## ##
5.2 Regression/Performance TestingPM
5.0 5.0 5.0 ## ## ## ## ## ## ## ##
System Test Sign-Off
## ## ## ## ## ## ## ## ## ## ## ## ##
## ## ## ##
Connectivity Test Complete
7.5 ## ## ## ## ## ##
MAT Sign-Off
6.1 Documentation
BA
## ## ## ##
6.2 Service Definition
BA
7 Implementation
TPM
8 Post-Implementation
PM
## ##
9.1 Project Management
PM
8.0 8.0 8.0 8.0 3.0 8.0 7.0 ## ## ## ## ## ## ## ## ## 8.0 ## ## ## ## ## 9.0 ## ## 6.0 9.0 ## ## ## 7.0 ## ## ## ## 9.0 ## ## ## ## ## ## 6.0 7.0
9.2 Programme Office
PM
10 Contingency
PM
Go Live
4.0 4.0 5.0 2.0
## ## ##
Key Market Activities and Dates
Activity
Start Date
End Date
Responsibility
Agree Test Execution Plan
04/05/2009
26/06/2009
Market
Xchanging
Preparation of MAT Scripts (DRI and Direct
Load)
04/05/2009
26/06/2009
Market
Confirmation of Direct Load Participants
06/07/2009
31/07/2009
Market
Confirmation of DRI Participants
06/07/2009
31/07/2009
Market
Connectivity Testing for DRI Participants
17/08/2009
04/09/2009
Market
Xchanging
Connectivity Testing for Direct Load
Participants
17/08/2009
MAT for DRI Participants
07/09/2009
04/09/2009
Market
Xchanging
16/10/2009
Market
Xchanging
MAT for Direct Load Participants
21/09/2009
30/10/2009
Market
Xchanging
Key Market Activities and Dates (continued)
Other Deliverables
Document Name
Start Date
End Date
Market Responsibility
A&S User Guide
26/06/2009
13/07/2009
Review and sign-off
ECF User Guide (Broker and Carrier Online Guides)
03/07/2009
20/07/2009
Review and sign-off
Updated User Request Forms
10/07/2009
27/07/2009
Review and sign-off
MTBC Instruction Form
10/07/2009
27/07/2009
Review and sign-off
Third Party Access Authorisation Form
10/07/2009
27/07/2009
Review and sign-off
IMR Security Model Market Implementation Guide
07/08/2009
24/08/2009
Review and sign-off
DRI Implementation Guide
08/06/2009
19/06/2009
For information only
LIMCLM Market Communication
29/05/2009
19/06/2009
For information only
MTBC Sample Letter of Authority
TBD
14/08/2009
Production of documentation
MTBC Best Practice Guidelines
TBD
14/08/2009
Production of documentation
Claims SP&P (Lloyd’s and IUA)
TBD
14/08/2009
Production of documentation
Binders and ECF
What is in scope?
What is out of scope?
•
Co-lead claims
•
60 – 80% of binder contracts
Binders and ECF
What changes have been requested?
•
Usability issues
•
Co-lead claims
•
Agreement parties
•
Net settlement
Binders and ECF
How will these be resolved?
•
Initial investigation completed
•
Prototype (September – December 2009)
– Initially develop using storyboards
– Develop working application
– Process extensive variety of binder cases via prototype
– Review outcome of prototyping
Binders and ECF
•
Critical dependencies (must be delivered prior to or as part of binders solution)
– Broker claim entry – new user interface
– Claims workflow triggers (CWT) &/or new carrier user interface including writeback
– Claims database – available as full operational datastore
– Access control database – supporting inputs from sources other than CLASS
– New version of LIMCLM for binder brokers only (minor change & not mandatory)
•
Non critical dependencies – preferably implemented but not essential
– Document file viewer (although significant impact on usability if not included)
– ACORD broker input and response
– Translation from LIMCLM to ACORD
•
There may be other potential dependencies which emerge during prototype stage
Binders and ECF
Jul-09
Oct-09
Jan-10
Apr-10
Jul-10
Oct-10
Jan-11
Apr-11
Jul-11
Oct-11
Tentative Dates
Start
Prototype
(Sep 09)
Implement
First Release
Prototype
Findings
(Jul 10)
(Dec 09)
Subsequent Releases and Full Binders Module