Please enable JavaScript.
Coggle requires JavaScript to display documents.
WhitBread RFP - Coggle Diagram
WhitBread RFP
Design Considerations
- we would want to consider table, row and attribute level access levels and full auditability around who is accessing the data, when and for what - particularly around data access to highly sensitive data.
- The new solution will need to ensure the policies are in place to manage localisation, with particular regard to the requirements around German/UK data storage and access.
- Data anonymized for non-prod instances
- Whitbread would like to move into the proposed Whitbread Data Platform in future, and incorporate relevant solution design aspects (e.g. security and authorisations) while finalising the High Level Design.
Architecture principles
-
-
-
-
-
-
-
-
-
Manage Technical Debt - Remove technical risk, cost & improve efficiency
-
-
Design Principles
Must ensure scalability, resilience & manageability
Ensure solution can automatically recover from failures with no manual intervention and ensure failures can be monitored (auto re-tries, failover, DLQs)
-
-
-
-
Point-point integration should be avoided, with AIL inbetween
based on the business requirements applicable for all the regions. These details will be made available during the Analysis and High Level Design phase.
- historic HR data from current business systems will be migrated AS-IS with preserving source data model
- Data Governance guidelines
Need to be able to prove data quality, so need to define & agree data quality rules for critical data
Data must be accessible, so a Data Catalogue must be produced & kept relevant
-
All sensitive data must be stored in a secure areas of the data platform with separate access requirements to the core data platform
All data storage, access & retention policies need to be considered against UK & German data
Data should only be moved into the Data Warehouse where there is an analytical reporting requirement for that data
Where ingested data does not have an analytical reporting requirement, data should be stored in the Delta Lake
Data for business critical, operational use cases should not be sourced from the DWH. This data should be sourced from an ODS or other appropriate data store that has the appropriate business criticality rating & support
Access to sensitive data must be needs-based only, with access revocation rules in place (e.g. change of job role, frequency of access, etc)
- Current assumption is that archival data will be access via SQL queries
- current Breakglass process for getting access to Data
-
-
-
HR Insights, Security & SDM notified & permission requested
If approved, User assigned to read only AD group
-
When issue is resolved, original ticket is updated with details of the user added, what the did and during what timeframe
-
-
-
-
- Archived data SLA for accessing
This data would be accessed on Ad Hoc basis and 1 days turnaround to access the data would be acceptable.
Our current integration design caters for the batch load with the data updates done on a daily basis. This will be reviewed further during the High Level Design phase and any changes will be agreed based on the business need.
-
Company Overview
-
purpose
To provide quality, affordable hotels for our guests to help them to live and work well and to positively impact the world around us. With no barriers to entry or limits to ambition, we will provide meaningful work, skills and career development opportunities for our teams.
Business
At Premier Inn, we’re here to help the nation rest easy, whether it’s a choice of rooms across our c.850 hotels, comfy beds that guests won’t want to leave or food to fuel the start and end of every day.
range of flexible rates to suit everyone, friendly team members who genuinely care and a level of consistency that ensures everyone knows exactly what they’re going to get. It’s comfort that everyone can count on
Whitbread employs over 35,000 people in over 1,300 Premier Inn hotels and restaurants across the UK
Premier Inn currently operates 43 hotels in Germany, including Frankfurt, Hamburg and Munich with plans to continue to grow the brand in Germany
-
Timelines
Data Archival solution must be in place by Feb'25 and historical data transferred from the legacy HR Systems.