Professional Documents
Culture Documents
3
Table Of Contents
Availability
Risk
adjusted
returns
Reliability
Capital
manage
ment
Enterprise risk
view across
credit, market, Granularity
Increasing Velocity liquidity,
operational….
and Complexity of
Calculations
Data
Management
Building Blocks
Shared components across applications – necessitate a common sourcing strategy
Computations Common Tools Business Rules Stochastic Modeling These common “building blocks”
are fully leveraged from
application to application to
FINANCIAL SERVICES ANALYTICAL APPLICATIONS DATA MODEL ensure data consistency,
traceability and availability
Pre-Integrated/
Data Common Objects Common Dimensions
Extensible
High Volume throughout the enterprise…
Sources
In order to position the Data Integration Hub effectively, we need to determine
the specific drivers at the account level.
Tier One Banks Regional Banks
Highly disparate SORs with duplication of Expectation of Growth and Regulatory
data, competing definitions and quality Responsibilities
standards.
Analytical Capability Optimization
Regulatory triggers creating demand for Process and Cost Optimization
data programs
BCBS239 Data and Channel type proliferation
CCAR Maturing Markets
Strategic Programs such as Risk/Finance Expansion into new LoBs
Transformation M&A
Analytics based strategies coming to
fore
Data and channel proliferation
Oracle Confidential – Restricted 9
2 Mins and 20 Mins Pitch
DIH Solution rationale: DIH optimizes the OFSAA data value proposition
The DIH addresses the challenge of needing to be able to 1. Enhances the implementation risk mitigation of pre-built
source, standardize and manage the data from systems of assets through the pre-built data mappings and
record into the FSDF’s single data environment. relationships to the Stage and Results Areas of the FSDF.
It also addresses the challenge of maintain the mappings 2. Enhances the TCO profile of OFSAA as future on-ramping of
and standardizations over time as the OFSAA environment new SORs needed for new Use-Cases become both easier to
changes and with it the FSDF. It reduces cost, complexity implement and maintain.
and TCO of the OFSAA solution environment.
3. Create a single-source of data ingestion across the
enterprise.
11
Data standardization for a typical enterprise is a daunting
task…
Regulatory Pressures
Manual Processes
Silo’d Views
Numerous Data Integrity Issues
Disparate Spreadsheets Inconsistencies
Capital Plans
Systems FR-Y14’s
Quality Concerns
Multiple Data
Warehouses Challenges
12
Data Integration Challenges
Moving Forward
Standardize
and unify data
OOTB sourcing Reduce effort
integration of spent on
OFSAA with ongoing
Oracle products maintenance
Reduces
Build interfaces
inbound ETL Integrate
with other
and enables Data source systems
Lineage
Oracle Financial Services Data Integration Hub
Key Features
Open Tool for Partners Logical Data Mapping
& Customers to build or
extend connectors
Oracle
Financial
Services Data
Integration
Pre-built Oracle Hub Simplified Object Representation
Product Integrations & OFSAA Lineage
Legacy
Files
DIH
XML
Who to sell to - Stakeholders
19
Unified Data Provisioning for
Analytics across the Bank
– Play 1
Bundle 1 Smallest Bundle
A data environment
that can align the data
needs of Risk, Finance
and Regulatory
mandates
20
Finance and Risk – Play 2
Transformation Bundle
OFSAA ‘Platform’ Bundle
2
Customer Need
Requirement to align +
Role to focus on the data consistency
and transparency
between Finance and FSDF
Risk functions of the
GL Recon
CIO/CRO/CFO bank
Enable complex
aggregations of Risk
and Finance data for
multiple reporting +
requirements across
functions and
regulations from
single environment.
Wholesale/
Retail Bank
Enable reconciled, DIH
timely data AAI
provisioning at levels
of granularity to
support net new +
business capabilities
21
Sales Challenges – Challenge questions and
Responses
• Many banks have been ‘burned’ with data management vendor solutions that demanded extensive
project cost and time commitments and yielded little real value.
• Data Governance is difficult to get right and tends to make banks lean towards more tactical deliveries
which in turn support the ‘build’ against the ‘buy’.
• Many clients have a great deal of business logic, technical meta-data and data treatments baked into
their existing ETL tools. We must be able to show either compatibility with or leverage of that built in IP.
• Ease of Implementation, Use and Maintenance of the DIH is critical to overcome tool-specific bias born
from having in-house skill sets around specific ETL technologies.
23
Comments Counters Opportunities
We already have 1. DIH has many ETL capabilities but it does Show how the DIH can both
considerable investment not have to be deployed as a rip/replace complement the existing ETL assets
in our ETL tool. Why do of your existing ETL infrastructure. and rationalize – rapidly and safely
we need to add another Rather it can be deloyed as means of – the ones that were created for
one? supporting the data sourcing needs of silo’d reasons and are now more
your OFSAA specific requirements more burden than benefit.
rapidly and cost effectively than
standard ETL. You can migrate as much
or little of the data transformation needs
to DIH depending on your needs.
2. DIH will give you a much easier
maintenance obligation as it will be
updated in lock-step with the OFSAA
environment. Your ETL commitments will
be meaningfully reduced and
governance capabilities therefore
enhance and assured with respect to
OFSAA and other applications
provisioned from DIH.
24
Competition & OFSAA solution's competitive
differentiators
27
Oracle Value Proposition – Time & Risk
Standard DW Implementation: significant time to design, build, implement & test.
Production &
Requirements & Analysis Design, Build, & Test Rollout
2+ Years
Requirements &
Design, Build,
Production &
Rollout
& Test
18-26 Weeks
Sample Use-Case Studies
Loans Customer
OFSA Applications
Deposits Account
Regulatory
Reporting
Trades D Ledger
I
H Master
D
Risk Factors
Third party Applications I OBIEE
Data Quality Management
H Reporting
Gl Balances
GL Recon
30
Oracle Confidential –
Integration Use Case - Data Management (BCBS239)
Enterprise Business Glossary
Metadata browser
Transactions ICAAP
D
Customer I Customer
Basel Analytics
(OCH) H
D ESTCP
Collaterals I
Third party Applications
MDM H Reg. Reporting
(DRM) Master Data
Solvency II
31
Oracle Confidential –
Integration Use Case - Pre-built Integrations for Enterprise Risk & Finance
Common Accounting Hub General Ledger Financial Management Analysis &
Source Systems Staging Reporting
Detailed GL Balances Ledger Consolidation
Balances
Data
Billing and Structures Daily Average Financial Close &
DIH
Revenue Customer Accounting Balances Disclosure
Account Rules
CRM Transactions Balances Dashboards,
Ledger Balances Reports, Ad Hoc
… Financial Adjustments
Core Banking
Systems Common Processing
Enterprise Common Results
DIH
34
Key Take-Away: Pre-Built, Rapid Delivery of Source data mapping for optimization of
OFSAA environment
Internal resources available
• FS Central
– DIH Product Deck
– DIH Recorded Presentation
– Solution Lead – bijan.olfati@oracle.com
• Product Manager – Bhargava Srinivasa
• Product Marketing – Jenna Denko, Amy Bielecki
37