to restricted records The product(s) will have universal usability and should not be restricted to one model of service delivery, cloud storage, case management system or technology partner (as far as practically possible e.g., ) Achieved (partial, not tested). Universal usability has been a key consideration for development - it is appreciated that other organisations may have differing source systems. With this in mind the infrastructure is purposefully system agnostic in terms of the source system, the tool developed can take data from many sources and display them all together and the design includes standardised database structures, pipelines and visualisation tool. The elements built within Azure (Data Factory and the ARM template) are specific to Azure (Microsoft) because that was the environment where the development took place. For the purposes of sharing a deployment package the elements built within Azure cannot be system/provider agnostic as there is little or no compatibility between the various cloud services. One of the reasons for selecting Power BI as the User Interface/visualisation was that it is commonly used and familiar amongst other LAs. Data source refresh/update – the process for regular updates/real-time updates, the capability to auto- update the search/ecomaps when new data or changes in children's records occur in the source system Achieved (partial). The current iteration is built with staging and enterprise layers with the intention of trafficking new data through the staging layer into the enterprise layer on an incremental/maybe daily basis. Further development work is required implement and test this, but the infrastructure would allow for this to be completed in the future. User Interface (UI) - interactive, user-friendly that allows u