Release 1.3 and Release 1.4 scope & readiness materials

• Pre-M&A access controls & entity names on DCOM for affected organisations

To be:

• Enables automated data fix process in DCOM to update access controls and entity names on contracts for affected organisations. Note – The release does not automatically trigger the M&A process. Once the functionality is live, the relevant Lloyds teams will conduct each M&A separately.

As is:

• Only notifications for the Create flow complete, notifications for endorsements, renewal, terminate had to be de-scoped due to capacity in MVP
• Notifications are not as clear as they can be in places

To be:

• Add in high priority notifications e.g. for endorsement, renewal
• Re-word notifications

As is:

• Privacy notices sent to a user each time they are named on a contract, regardless of whether they have received one before

To be:

• Privacy notices only sent once to a user
• Re-word notifications

As is: 

• Review task sent from contract creator to all section leads to check data in DCOM is what was agreed offline
• Section leads can approve/reject as appropriate
• If they reject, contract creator must update & send back to leads
• Currently, there is no summary to see what has been changed on DCOM, so leads can end up re-reviewing all info (not just the changes they requested)

To be: 

• Tracked changes for returned review tasks gives leads confidence that they can see all changes made instantly

As is: 

• At go-live, logic built into DCOM meaning that tasks auto-NTUd too quickly.
• Consequently, auto-NTU functionality was switched off, but due to tactical nature of the fix, notifications were not

To be:

• Re-instate simplified auto-NTU logic to only occur every 365 days from last update
• Update Notifications' wording and logic

As is:

• Currently an endorsement requires all section leads to approve review tasks, even if the section they are on is not affected by the endorsement

To be: 

• Allow users to select which section(s) are being changed by an endorsement, and only send review tasks to lead(s) on these section(s)

As is:

• When adding a limit, currently it is only possible to delete it and re-add another one, rather than amend

To be: 

• Ability to amend limit rather than delete and re-add

As is:

• Users must toggle on auto-save in each contract registration, there is no ability to turn it on for all contracts

To be:

• Ability to turn auto-save on for all contracts (new and existing)

As is:

• Currently there are ~250 mandatory/conditionally mandatory questions in DCOM. An exercise has been undertaken to reduce this by ~40

To be: 

• 9 mandatory fields made non mandatory
• 8 removed for all users as not required
• 26 removed for non-DDM users

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:

• 9 targeted reports required by Lloyd’s to meet regulatory reporting requirements
• ~2 years' worth of data can be extracted from DCOM

As is:

• Registration info for all DDM contracts is passed to DDM through API

To be:

• Only contracts which DDM is being used will be passed to DDM through API