Watch full webinar here: https://bit.ly/44FT2VT Frédérick MISZEWSKI, Digital & Data Architect OnePoint, illustre les attentes, besoins et contraintes d’Epex Spot, société leader sur le marché de l’achat/vente d’énergie. Les besoins identifiés, un nouveau schéma d’architecture se dessine pour prévoir l’intégration des données, leur analyse, l’agrégation et la traçabilité en toute sécurité et dans le respect des contraintes de conformité (RGPD notamment). OnePoint a proposé Denodo Platform comme nouvelle voie centralisée et a obtenu des résultats significatifs sous 3 semaines.

2. •
•

3. •
•
•
•
•

4. Minimized
TCO
Modern CRM
with Open Data,
& Data
Platform
Optimized
ROI
Capitalized
on the
best of legacy
Reduced
Time to Market
Replaced
obsolete tools IT
characteristics
Business
benefits
Better
360° customer
vision
Agile and
modular
architecture
Urbanized and
rationalized
assets
Data Centric
Open
(through API)
Real time
processes when
needed
Cloud ready and
opportunist
Upgraded and
rationalized
IT skills
Improved
security
Clear
Build vs. Buy
approach
Unique &
shared
Members
database
Improved
user experience
and user
satisfaction
Digitalized
with
omnichannel
capabilities
Empowered
for
new markets &
products
Challenged
competitors in
their own fields
Strategic
stakes
Differentiated
from
the competitors
Innovative
and attractive
image
Armed
against
competitors on
their own fields
▪ Smoothen the switch from R&D to
industrialization on the BI Reports and
tools in Python
▪ …
▪ Study the deployment of a CRM solution with 360° Customer vision
integrating CRM activities and Legacy activities in a single place : Big Data
Platform
▪ “NDA”
▪ API opening must be seen as an opportunity:
o Expose services
o Expose/sell EPEX Data
▪ Value all EPEX data by building a state of the art Big Data Platform
▪ POC on data processing from the real time trading APIs to be
conducted
▪ Coherent ecosystem fitting the backend data and front end with strong
integration, seamless user experience and added value
▪ …
▪ Move the architecture and solutions
to more configurable ones
▪ Ease of use for new building blocks

6. o
o
o
•
o
o
o
•
•

8. DATA
Govern and expose cross domain
repositories through a centralized
data platform
Data centric at every level of the
business projects
Analysis and data processing
solutions via a central data
platform
Centralized analysis and reporting
tools within one single platform
Govern and expose external
repositories through a centralized
data platform
Adopt a data by design approach, by integrating data across the entire life cycle of the projects The
solutions must allow the exposure of their data in a secured manner.
The EPEX data platform carries out the functions of data analysis and must be used by all businesses to
carry out their jobs ( Operational reporting, Analytics, Data Science). Data access must be well secured and
filtered, depending on user’s credentials and data privacy
The tools must be centralized and managed by the EPEX data platform, with consolidated and aggregate
data, the calculation and the presentation of KPIs. Steering governance is supported by the functionalities
of this data platform
The EPEX data platform governs and exposes consolidated business systems of record. The platform also
performs functions related to the quality, security and traceability of this data.
The EPEX data platform shall govern and expose all the internal consolidated aggregated repositories.
Anonymization must be applied whenever required (to be GRPD compliant).

9. •
•
•

10. •
•
•
•

11. 1
2
3
Build a centralized Data
products point of truth
Leverage the built-in request
optimization engine
Isolate physical models to
consumers, adapt to consumers
need
CONNECT
Physical layer
CONSUME
Valorization layer
Visualization
Fresh data as
they come
Business
Intelligence
Data
exposition
(API)
Data
exploration
& Data
Science
COMBINE
Logical layer
U
J Union
Join
Clients
(CRM,
RDMS…)
Continuous
Order
history
HDFS
Stream
Continuous
market
M7
ORDERS
ORDERS
CLIENTS ORDERS
Auction
Order
history
HDFS
CONT_ORDERS_HIST AUCT_ORDERS_HIST
AUCT_ORDERS
ORDERS_LIVE
CUSTOMERS
CONT_ORDERS
TRADES PER CUSTOMER
API SQL GraphQL
4 Guaranty Time To Market (no new
techies and not required stacks,
leverage strong SQL expertise) – No
change for consumers used to access
Oracle

12. •
•
DATA DOMAINS CORE BUSINESS​
Prospects Legal customer
Physical custo
mer
Products Contract Marketing Claims
Identity​ Identity​ Identity​ Product Type​ Contract type​ campains​ Claim_Type​
Contact data​ Contact Data​ Contact Data​ Pricing​ Customer data​ Client events​
Scoring​ BankInfo​ Roles​ Product details​ Validity period​
Membership type​ Attachement​ Attachement​ Status​
Status​
EpexCode​ …​
Membership type​ …​
Business
domains
• Data owner
• End user oriented
Data as a
product
• Facilitated
consumption
• Quality
Self-service
data
• Catalog
• Monitoring
Federated
governance
• Interoperability
• Documentation
• Security

13. •
•