UAT Maintenance Service Updates 

MAINTENANCE AND SERVICE UPDATES

The next release, BinderCloud UAT v3.1.1.1, will be available from Tuesday 23rd February 2016.

(BinderCloud UAT will briefly be unavailable between 6am – 9am on Tuesday 23rd February while essential updates are processed)

The following items are included in this release and will be available in Production from Tuesday 8^th March 2016.

• Data Vault Restrictions
• Workflow

Data Vault Restrictions

On a per Binder basis, the Owner of the Binder (Contract Owner) should be able to permit/deny access for associated 3rd Parties to data/documents stored within the Repository and DataVault independently of each other.

The process for setting access permissions to the Data Vault is the following:

1.     When a contract is created (from within BinderCloud, the contract upload or via the external API) for Brit (the customer) who has purchased the Data Vault, the access permission will be granted to all Trading Partners (MGA/Coverholder, Broker, TPA’s and Carriers)

2.     If a Trading Partner is changed or added to the contract then access permission will be granted to them.

3.     To allow (grant) or withdraw (deny) access to the Repository and/or the Data Vault for any Trading Partner the [Contract ACL] option is selected from the side bar menu which is visible when the contract is in ‘Edit’ mode.

4.     To withdraw (deny) access to both the Repository and the Data Vault, the ‘Silent mode’ button should be selected.

Workflow

The end to end tracking of all Bordereaux processes, beginning with Bordereaux due, through to mapping and approval of a processed Bordereaux . Notifications are to be sent to the appropriate recipients throughout the process.

The process for Workflow is as follows:

1.     A Bordereau document will be loaded into the Contract within the BinderCloud Repository

2.     If a mapping exists the Bordereau will enter the Bordereaux Processing Queue, if a mapping does not exist, the mapping team will be notified and a mapping project created.

3.     The project will pass between the DUS On and Off Shore team until the mapping is ready to be released and the customer notified.

4.     The customer has the option to review and query the mapping, providing relevant supporting notes which will be reviewed by the DUS on shore team member.

5.     Once the mapping has been amended, it will be released back to the customer for review.

6.     The customer has the option to approve the mapping which will allow the mapping team to synchronise the mapping with the contract and begin bordereaux processing.

7.     Bordereaux will go through the existing processing process with the additional ability for DUS on shore users to assign bordereaux with errors, to the customer for review.

8.     Customers will have the ability to approve or reject the processed data which will result in either mapping changes or new data needed to be provided by the Coverholder/Broker.

9.     A new dashboard will be created to allow users to review the current mapping, bordereaux processing and data approval statuses in one place, with the ability to extract results into Microsoft Excel.

10.  Nil Bordereaux submissions may be advised to the DUS team from either Coverholder, Broker or customer. The DUS team will assign the “Nil Bordereaux” status to the period which will set the data approval status to “Data Awaiting Approval”