ections should be stored and shared to enable the organisation and wider sector to:  Learn from mistakes  Gather best practice  Build trust  Identify, document and analyse insights and patterns 4.1.6 Technical Guidance A document collating technical information/guidance has been drafted and is available at Appendix 4 (Data Factory Documentation). This reflects technical information and learning from the pilot project and development of the version of the prototype that was tested by users at pilot workshops in February and March 2024. Packaged technical elements have been prepared and included, these are a starting point and would require manual work by someone with the ability to configure connection strings and user IDs within the scripts in order to successfully deploy. This is because private data (e.g., account names, connection strings, URLs) has been removed from them and relevant local details would need to be provided for successful deployment. The SQL database is available as a DAC Package (see Deploy a Data-tier Application - SQL Server | Microsoft Learn) [10] – this is a single .dacpac file, this would typically be deployed using SQL Server Management Studio. Appendix 5 (SQL DAC Package .dacpac). Data Factory clone is available as an ARM template (see Copy or clone a data factory in Azure Data Factory - Azure Data Factory | Microsoft Learn – follow the steps for point 3: “Live Mode”) [11], the ARM template would be deployed via the Azure Portal. This is a small number of .json files. Appendix 6 (ARM template for Data Factory Clone Zip). Universal usability has been a key consideration for development (see section 4.1.4 Progress Against Requirements). The infrastructure is purposefully system agnostic in terms of the source system. The elements built with