Please enable JavaScript.
Coggle requires JavaScript to display documents.
pBDaaS (Why (Traditional approach (DIY, CAPEX, long procurement, test,…
pBDaaS
Why
Human +MC data 10X growth
masks complexity
lack of deep expertise
architecture challenges
need careful integration
HPE seen pitfalls
frees staff
Want a data Lake
Not ponds
Traditional approach
DIY
CAPEX
long procurement
test
Need expertise
Public Cloud
fast implementation
OPEX
data privacy
variable latency
lock-in, soveignty risks
low barrier to entry
What
alternative data management
Server to data not VV
On premise, cloud like
e2e solution
grows as needed
managed by HPE, customer control
Customer Requirements
No upfront Investment
Reduce time to market
Avoid over/under prov
Reduce Complexity
SPOC
Qs
Analysing any BD projects or use cases
Looking for BD use case that cover tehir busienss/market
Looking for 1 provider to give e2e?
Inc uses Cases?
providing BD to other internal custs
Who
Consulting
Chris Smith
Bus Dev
Maria Ridruejo
Andy Fletcher
Consumption
Telefonica
Antonio Amor
pBDaaS stack
DC support, install, etc
OSS
request fulfilment
User creation
Patch updates
periodic review
Log files
install
testtg
New Worker deployment
$/unit decreases
custom deal
4 price bands
8
Advisory & Prof Svcs
Above HW
CLuster config
Hadoop ecosystem
Haddop monitoring config
Product planning
Design
Adv Config
Fixed fee
Price based on # worker nodes
Solutions
HPE Servers
HPE networking
BD OS +Stack
Cloudera
Hortonworks
Not
MapR