 large data loads and increase data retrieval performance. March 2024: Incremental load/data refresh and LiquidLogic forms work being undertaken. Consolidation of documentation. The technical architecture diagram below describes the architecture in-place from January 2024. 21 OFFICIAL - SENSITIVE Figure 3: Technical Architecture Diagram January 2024 22 OFFICIAL - SENSITIVE 4.1.2 Technical Issues and Resolutions Issue Resolution Implemented yes/no Azure tenancy information security Virtual private network Yes Accessing AI services in a private environment The initial resolution was to build custom functions – this required specialist skills (coding c#) and bespoke configurations. The enhanced resolution was to alter the infrastructure to a data factory model, this removed the necessity to use custom functions as “off the shelf” AI services could be accessed in a private environment. Reference Fig. 3 Technical Architecture Diagram on page 22. Yes Database backup file for Azure redeployment incompatible Secured backup from logship database clone, rather than the ‘static’ backup Yes Character limits Async AI API to increase character limits from 5000 to 125000 Yes .doc files which make up 25% of the overall documents are incompatible with Azure AI services Work done to establish that these are not wholly historic files, 25% of the files added to LiquidLogic in February 2024 were .doc Resolutions could include: - Build in a step to convert .doc to .docx to the data factory process - One-off conversion of historic .doc files by undertaking a batch conversation process for all historical .doc files and saving them all as .docx prior to being sent to AI services for processing - Recommendation to disallow .doc files from being continually added to the source system No Ecomaps d