#05 - DataSync, When do you want the Information refreshed?
When do you want the Information refreshed?
Once I have captured the delivery types as outlined in my previous post:
I move onto the fifth area, the DataSync.
In the DataSync area I determine how often the information should be refreshed, indicating when new information should appear in the Information Product for consumption.
I am interested in how often I have to synchronise new data from the System of Capture through to the final consumable Information Product.
DataSync is the frequency data is collected from a System of Record to update or refresh the data within the Information Product.
The frequency of data updates is a critical facet of your Information Product, significantlyÂ
Stakeholders often consider when they want to access the Information, not when the Information Product needs to be refreshed with new data. DataSync involves synchronising new data from the Systems of Capture all the way through to the final Information Product.
The ideal DataSync frequency is dependent on several factors, including the data’s nature, the personas needs, and your organisation’s technical capabilities. Some Information Products may only need monthly or weekly updates, whereas others might demand daily, hourly, or even near real-time updates.
For instance, a Contact Centre Leader’s Call Volume dashboard might need near real-time updates to reflect the latest call volumes. Conversely, an executive leader’s monthly financial report might only require updating once a month.
DataSync expectations help the Agile Data Team in estimating the complexity and effort required to refresh the Information Product at this frequency. There’s a considerable difference in engineering updates once a day compared to every 2 hours, every 15 minutes, or in near real-time.