How does Subvise work?
Subvise uses a series of automated proprietary processes to stay up to date and synchronised with the primary sources of Reach related data.
Every day outside of business hours, these Subvise processes automatically retrieve the regulatory data from the various sources.
It then compares this new data with the current version within Subvise and performs certain operations on it.
Subvise pays close attention to data that is new data, removed or modified.
Subvise then sends out email notifications of any changes to affected users.
Once a week Subvise sends out an automatically generated email to show the results of the weeks automation. This includes the name of the source that has changed and the amount of items from that source that are new, removed or modified.
With an automatic synchronisation system such as the one described, one which relies heavily on external (and sometimes poor quality and poorly formatted) data, there are often quirks with the output. These outputs can result in Subvise sending change notifications to users that describe insignificant or inconsequential changes.
Important things to be aware of when interpreting Subvise notifications includes but is not limited to the following:
- Items that are flagged as 'modified' will not always necessarily be caused by changes to important data. For example, if the primary source had an item with a spelling mistake and it was fixed then Subvise recognises this as a change. Similarly, changes in the formatting of an item in the source will be flagged as modified by Subvise.
- If changes in the source are made to the identifiers (usually CAS, EC numbers or name) then Subvise will treat the existing item as removed and the new items as newly added.
- If the schema of a source is changed dramatically then it is possible that an entire list is marked as removed and then all items will become 'newly added'. This will be infrequent but not impossible, we have for example seen this case once with changes to the SIN list.
- When dealing with sometimes volatile and ofter poor quality third party data there is a lot of room for inconsistencies. Sometimes there is changes to the source data that Subvise simply doesn't know how to handle, such as poorly formatted dates or poorly formatted identifiers. When this happens the item is handled manually by the Subvise team.
If you have any further questions about Subvise or how Subvise works, please use the contact form.