Building Your Data Hub
to Support Digital
Powered by
Mark Walters
Senior Manager
Information Architecture & Design
mwalters@ybs.co.uk
You’ve gone through
the organisational
redesign for digital.
Now its time to figure
out how to expose
your data to new
digital services…
About Yorkshire Building Society
Region Est.18643m CustomersProducts
“We exist for the benefit
of our members, to provide
real help with their real
lives. This means being
there for them through the
different stages of their
lives and responding with
practical solutions and
empathy.”
- Mike Regnier CEO
Customer walks
into branch to
open a savings
account
Customer fills out
paper application
form
Our processes often involve a lot two-way interactions between customers and Branch staff
Process relies on customer bringing all relevant
documentation to Branch & colleague availability
Typical Business Processes
Branch Staff key
application onto
system
Customer
provides ID
documentation
Branch staff
copy/scan ID
documents
Branch staff
perform fraud
checks
Customer makes
opening deposit
with cash/cheque
Account open and
Welcome Pack
produced and
printed
Pack sent to
customer’s
address
Account
Open
Restrictions on our external network make it difficult to move
larger amounts data meaning that we have to host “on premise”
rather than “in the cloud”.
Around 60% of our change portfolio are projects where
integration costs outweigh costs of the new package.
Data Integration is our biggest challenge!
Current Architecture
Digital Business Unit
YBS Platforms 3rd Party Platforms
API Services
API API API
SOA Services
SOA SOA SOA
Core
Platform
YBS
Package
Apps
DB Pkg
Form
New APIs may require new SOA services.
SOA used to expose backend functionality.
Core Systems and Data
Business Services
Services
Digital Services
Packages
Authentication&Authorisation
Web Portals
Mobile
Apps
3rd
Party
Apps/
Services
3rd
Party
Websites
API Gateway
YBS Core Customer
IRESS
B2B Partnerships
Data Abstraction
ECM
Processes
Web Content
Management
Customer Collegaue
External Data Sources
Creating a data
hub as an
abstraction over
our internal and
external data
sources.
Future Architecture
Combine
With data held
in ODS
Connect
to disparate data
sources in real-time
1
2
2
Consume
Location-agnostic for
multi-cloud, hybrid
acceleration
Mobile
App
B2B
Partner
Services
3
Online
Portal
3rd Party
Apps
Data Integration Architecture
ACTIVATION FORMALISATION CONVERGENCE ADOPTION
Business strategy calls
for digital services
PoC for Denodo proves
40% cost saving for DI.
(Technology acquisition)
Pilot project delivers
MVP for mobile app
YBS Digital Platform
goes online
Reference
Architecture
for DI established
Expansion of
digital services
ODS provides core
Data Hub,
supercharged by
Denodo
Digital Journey
Percentage shift
towards
Virtual Data Hub
Digital Journey
Digital Journey
Data Hub Journey
Expected Benefits from Denodo
• Real-time integration
• Reduced time & cost for data integration
• Utilises an existing asset, our Enterprise LDM
• Ability to audit and control access (data masking)
• Componentisation of development
Lessons Learnt (thus far)
Positives
• Speed of development
• Inbuilt lineage
• Number of connectors
• Responsive vendor
• Ease of use
Challenges
• Hardware and license
costs
• Community support
• Market resource
• Performance tuning
complexity (improved
with v7)
What’s next
• Expanding our Data Hub (Marketing Automation,
Call Recording data)
• Building our core Denodo capabilities
• Looking to be part of a Denodo user community
• Hoping to upgrade to v7 ASAP
With thanks to
Strategy & Insight team
Architects:
- Tim Pryke
- Mark Williams
- Steve Grimwade

Building Your Data Hub to Support Digital

  • 1.
    Building Your DataHub to Support Digital Powered by Mark Walters Senior Manager Information Architecture & Design mwalters@ybs.co.uk
  • 2.
    You’ve gone through theorganisational redesign for digital. Now its time to figure out how to expose your data to new digital services…
  • 3.
    About Yorkshire BuildingSociety Region Est.18643m CustomersProducts “We exist for the benefit of our members, to provide real help with their real lives. This means being there for them through the different stages of their lives and responding with practical solutions and empathy.” - Mike Regnier CEO
  • 4.
    Customer walks into branchto open a savings account Customer fills out paper application form Our processes often involve a lot two-way interactions between customers and Branch staff Process relies on customer bringing all relevant documentation to Branch & colleague availability Typical Business Processes Branch Staff key application onto system Customer provides ID documentation Branch staff copy/scan ID documents Branch staff perform fraud checks Customer makes opening deposit with cash/cheque Account open and Welcome Pack produced and printed Pack sent to customer’s address Account Open
  • 5.
    Restrictions on ourexternal network make it difficult to move larger amounts data meaning that we have to host “on premise” rather than “in the cloud”. Around 60% of our change portfolio are projects where integration costs outweigh costs of the new package. Data Integration is our biggest challenge! Current Architecture Digital Business Unit YBS Platforms 3rd Party Platforms API Services API API API SOA Services SOA SOA SOA Core Platform YBS Package Apps DB Pkg Form New APIs may require new SOA services. SOA used to expose backend functionality.
  • 6.
    Core Systems andData Business Services Services Digital Services Packages Authentication&Authorisation Web Portals Mobile Apps 3rd Party Apps/ Services 3rd Party Websites API Gateway YBS Core Customer IRESS B2B Partnerships Data Abstraction ECM Processes Web Content Management Customer Collegaue External Data Sources Creating a data hub as an abstraction over our internal and external data sources. Future Architecture
  • 7.
    Combine With data held inODS Connect to disparate data sources in real-time 1 2 2 Consume Location-agnostic for multi-cloud, hybrid acceleration Mobile App B2B Partner Services 3 Online Portal 3rd Party Apps Data Integration Architecture
  • 8.
    ACTIVATION FORMALISATION CONVERGENCEADOPTION Business strategy calls for digital services PoC for Denodo proves 40% cost saving for DI. (Technology acquisition) Pilot project delivers MVP for mobile app YBS Digital Platform goes online Reference Architecture for DI established Expansion of digital services ODS provides core Data Hub, supercharged by Denodo Digital Journey Percentage shift towards Virtual Data Hub Digital Journey Digital Journey Data Hub Journey
  • 9.
    Expected Benefits fromDenodo • Real-time integration • Reduced time & cost for data integration • Utilises an existing asset, our Enterprise LDM • Ability to audit and control access (data masking) • Componentisation of development
  • 10.
    Lessons Learnt (thusfar) Positives • Speed of development • Inbuilt lineage • Number of connectors • Responsive vendor • Ease of use Challenges • Hardware and license costs • Community support • Market resource • Performance tuning complexity (improved with v7)
  • 11.
    What’s next • Expandingour Data Hub (Marketing Automation, Call Recording data) • Building our core Denodo capabilities • Looking to be part of a Denodo user community • Hoping to upgrade to v7 ASAP
  • 12.
    With thanks to Strategy& Insight team Architects: - Tim Pryke - Mark Williams - Steve Grimwade