Item | Description | Readiness Materials
|
Agreement template change | As is: - Users can request a template change via the Market Support Centre Portal
To be: - Ability to self-serve contract template changes in DCOM at Draft/Renewal stage
- Once Registered/Active, Lloyd’s can change certain template types, but it is not possible to switch between Coverholder and Service templates for contracts created in DCOM once registered
| View Knowledge Article & video |
Reference data versioning | As is: - There is no concept of reference data versioning, so all reference data is included regardless of the period it is/was effective
To be: - Ability to create and store history of all reference data meaning drop-downs have up-to-date, appropriate values and improving data quality
| N/A - background system change to improve user experience, no user training impact |
Mid-term broker change (MTBC) | As is: - MTBCs are not currently supported in DCOM
To be: - Ability to self-serve changing the Broker associated to an active contract
| View Knowledge Article & video |
Provide history of comments for MA review tasks* | As is: - MAs need to check outside the review task for updates they have requested previously
To be: - All review task comments for the create task can be viewed in one place for the specific MA who has made them
| View Knowledge Article & video |
Associate email addresses with user groups* | As is: - Managerial group MA users must check dashboards to see when a review task has been sent by the contract creator for their review
To be: - MAs will receive an email when they receive a review task. They are still able to check dashboards if they wish
| View Knowledge Article & video |
Provide DXC access to Drafts* | As is: - DXC have access to Active / Registered contracts, but not Drafts
To be: - DXC will have access to Draft / Active / Registered contracts. This will speed up processing as they can review tasks earlier in the process
| N/A - no market change |
Lloyd’s reporting MVP | As is: - Only one overarching report available for Lloyd's users to run
- Only 3 months' worth of data can be extracted from DCOM in one go. If > 3 months' data is required, it is stitched together in Excel to meet regulatory requirements
To be: - Foundational functionality for:
- 9 targeted reports required by Lloyd’s to meet regulatory reporting requirements
- ~2 years' worth of data can be extracted from DCOM
| N/A - no market change |
DCOM changes for DDM MVP | Changes have been made to the Contract API in order to enhance the DCOM-DDM Integration when it is live. Key aims of R1.2 were: - Decrease the number of contracts that fail to be created in DDM, by adjusting how DCOM presents data in the API
- Provide additional, relevant data that is currently mandatory and required for DDM
- Decrease number of workarounds DDM needs to do in order to capture data correctly
- Increase the number of contracts recognised as renewals
As is: - Claims Authority limit captured per section
- No question asking if each binder is a master non-premium earning contract
- Manual renewal links cannot be established before the contract is registered i.e. whilst it is a draft
- Premium paid field for reporting channels non mandatory (“Maximum number of days for reporting / submission“)
- Fields for contract API v3.0.6 missing
To be: - Capture the Claims Authority limit per Coverholder
- Ask a question to determine if each binder is a master non-premium earning contract and use this to ensure the correct information is captured under the reporting channels. This will ensure that users only answer bordereaux processing data when required.
- Manual renewal links can be established for the renewal contract when in draft / registered / active / expired states
- Make premium paid field mandatory for reporting channels (“Maximum number of days for reporting / submission“)
- New fields added in accordance with v3.0.6
| Knowledge Article showing key changes, no video deemed required as these are ad hoc changes to specific fields View Knowledge Article |
Defect fixes from prior releases | As is: To be: | N/A – no new functionality implemented, fixes of existing scope |