ior to being sent to AI services for processing - Recommendation to disallow .doc files from being continually added to the source system No Ecomaps display a maximum of 500 nodes Include this in practice guidance. Recommendation to understand how are the 500 selected and reference in documentation No Children record counts are vast and importing these into visual tool (Power BI) causes serious performance issues Create materialised views to source the data from the database. Set Power BI to obtain records via ‘direct query’ from the views on a per child basis to vastly improve data retrieval performance Yes Table 5: Technical Issues and Resolutions 23 OFFICIAL - SENSITIVE 4.1.3 Dataset Summary Below is a summary of the dataset consumed by the product during this project:  456,970 children – this is children only (e.g., cases), all have unique case reference numbers  2,058,858 documents – average 19 per child (documents in this instance, refers to files attached to a case and uploaded to the file store i.e. docx/pdfs etc. It is not referring to the forms in LCS)  7,523,745 case notes – average 87 per child  1,100,567 significant adults – this is probably more accurately described as a “Child+Adult relationship”. If a parent has two children in the system, there will be two significant adult records for that person. One for Parent->Child A, another for Parent->Child B.  331,539 case workers – this works similar to the relationship above, except this is for “Child+Worker relationship”. This record also has start and end dates, so contains a history of those relationships. If a case worker has been assigned a role working with the child over three time periods, there will be three records in for that Child+Worker combination. After all documents and case notes are pro