Summary
This page discusses risks and mitigation relating to exporting data from Tideway Foundation. The accuracy of Tideway foundation data merits ensuring that it is exported correctly and with the right frequency to be useful throughout the IT organisation.
| | |
|---|
| - Frequency of export does not meet requirements
* Export process is too slow
| * Workshop and document all export requirements and approve with Sponsors
* Increase the number of Appliances to facilitate dual export of data
* Consider exporting just changed records |
| - Data mapping is inaccurate
* Not all attributes can be exported
| * Review available attributes for mapping using Foundation Taxonomy and prepare to use other commands to collect missing attribute data
* Document and test data mapping and ensure data source expert is engaged in the design process
* Review Foundation data quality and resolve any missing or unexpected values on a proactive basis
* Note all limitations in the solution architecture document and review with Tideway Product Management |
| - 3rd Party import process is too slow
* Not all attributes can be imported by 3rd party
| * Workshop and engage with 3rd party to review speed issues based on Lab and speeds established during Lab/Dev testing
* Plan any required changes to the export solution and document in the solution architecture document
* Reduce scope of Foundation export to provide a working solution with a plan to review status with Tideway Product Management |
| - Not all changes are exported
* 3rd party product requires 'all or nothing'
| * Always design solution to assume 'just changes'need to be exported (this is the most complex option)
* Convert to an 'All'solution only if necessary |
