English Testing and Documentation Experiences must be delivered to the Museum at least six weeks in advance of when they launch in the gallery, exact timing will be agreed upon during the contract phase. Digital experiences must be thoroughly tested before delivery by the vendor on the same hardware that they will be running on in-gallery. Refer to Hardware, Software, Web Infrastructure for more details. Analytics capture also requires testing before final delivery to confirm that all events are being recorded accurately. Refer to Analytics for more details. Auckland Museum’s digital experiences undergo user testing which the internal Visitor Market Research team lead. Most experiences include 1-2 testing sessions with visitors, after which a report is prepared informing improvements and updates to the user experience. This testing is worked into the timeline and allows all parties to produce the best possible experience for visitors. Soak testing will occur for at least 1 week, whilst experiences are still under vendor warranty, any errors and changes will be reported promptly as required. Any code created will be placed into the Museum’s github repository. The source of truth should always be the AM Github repository. Any future updates or patches need to be updated in the github repository. Any deployment of code needs to involve AM ICT or AM DX for the best way to provision equipment. All code created must be owned by the Museum. Full source code must be provided – this includes the ability to compile any experience be it online or in gallery – as an example a single binary export from Unreal Engine would not be sufficient, instead all required code to build the binary including any licenses for any third party libraries or other assets included. Instructions must be provided for compiling any content. Any CMS or content – where possible will leverage the Museum’s existing technology e.g. using our existing Kentico CMS if possible. If not possible it should be able to be hosted by the Museum directly.