Maintenance The data in the system is maintained on an ongoing basis from the input into the system. Reports can be generated to monitor relevant expiry of documentation and safety briefings. The maintenance of hosts and user lists is manual and should be undertaken by the users’ nominated system administrators. At the end of its lifespan the data can be purged manually by the Vendor with direct access to the SQL database. It can be provided to the client in format. Additionally the data can be purged on demand to a specific requirement i.e. – data older than XxX. Archive Any deleted data is archived in nominated tables to maintain referential integrity. You can notify the vendor of any ‘deleted’ requirement to archive in line with policy. This will be carried out as part of your support on the hosted server. Data Volume Data storage is provided by Vendor on hosted server. No charges are made in relation to storage used. Data Flow Infrastructure Protocol Start/End Sizing Frequency Latency Security Link Point Locations Client Business User 38kb per visitor Varies per < 100ms SSL to Web Server site/reception Disaster Recovery Tier / Component Description of DR Data Synchronisation High Cutover High level Cutback capability Approach Process Process Data Tier Server replication incl UKFast monitored and n/a booker will work in n/a booker will work in Data replication with managed offline mode offline mode RPO of 60 mins. Presentation Tier Booker Corruption Automatic on login Login direct to cloud Login direct to cloud local database and delete local cache and delete local cache Reinstall from website in first instance in first instance Business Tier Printer failure Next Replacement business day warranty Business Tier Camera Failure Next Replacement under business day warranty Business Tier QR Code Scanner Replacement under failure Next business warranty day Persistence Tier Local MSSQL Db Automatic in line with Delete cache Delete local cache settings through interface through interface – – will recreate on next will recreate on next login login
Maintenance The data in the system is maintained on an ongoing basis from the input into the system. Reports can be generated to monitor relevant expiry of documentation and safety briefings. The maintenance of hosts and user lists is manual and should be undertaken by the users’ nominated system administrators. At the end of its lifespan the data can be purged manually by the Vendor with direct access to the SQL database. It can be provided to the client in format. Additionally the data can be purged on demand to a specific requirement – i.e. data older than XxX. Archive Any deleted data is archived in nominated ‘deleted’ tables to maintain referential integrity. You can notify the vendor of any requirement to archive in line with policy. This will be carried out as part of your support on the hosted server. Data Volume Data storage is provided by Vendor on hosted server. No charges are made in relation to storage used. Data Flow Infrastructure Link Protocol Start/End Point Locations Sizing Frequency Latency Security Client Business User to Web Server 38kb per visitor Varies per site/reception < 100ms SSL Disaster Recovery Tier / Component Description of DR capability Data Synchronisation Approach High Cutover Process High level Cutback Process Data Tier Server replication incl Data replication with RPO of 60 mins. UKFast monitored and managed n/a booker will work in offline mode n/a booker will work in offline mode Presentation Tier Booker Corruption local database Reinstall from website Automatic on login Login direct to cloud and delete local cache in first instance Login direct to cloud and delete local cache in first instance Business Tier Printer failure Next business day Replacement warranty Business Tier Camera Failure Next business day Replacement under warranty Business Tier QR Code Scanner failure Next business day Replacement under warranty Persistence Tier Local MSSQL Db Automatic in line with settings Delete cache through interface – will recreate on next login Delete local cache through interface – will recreate on next login