Slidesharedeck feb19

2

• Why Model DR & data point model market exists

• Regulatory environment

• Model DR solution

• What

value we offer to our customers

• What differentiates Model DR

• Questions

Global banks are

using ModelDR to

upgrade risk data

aggregation & reporting capabilities

ModelDR – a data design & analysis solution

• providing a single, enterprise view of portfolio risk and exposure

• resolving data dependency on inflexible systems architectures

• providing a congruent dataset ready for reconciled & validated report

generation

• enabling transition towards larger system architecture decisions

3

4

Financial regulation demands improvements in bank risk data aggregation and reporting

Banks must establish strong data

governance, architecture &

processes

Regulators want to know if banks

prioritise compliance as highly as

other infrastructure projects

Data warehouse

Front office systemClient ID Name Client

type1 Thatcher Gold2 Blair Silver3 Cameron Bronze

Risk system

Client ID

LEI Name Client type

Risk Rating

1 987 Thatcher Gold High

2 654 Blair Silver Medium

3 654 Cameron Bronze Medium

321 Obama LowLEI Name Risk rating

987 Thatcher High654 Blair Medium321 Obama Low

Current Data Management

5

Data Point ModelFront office systemClient ID Name Client type1 Thatcher Gold2 Blair Silver3 Cameron Bronze

Risk systemLEI Name Risk rating

987 Thatcher High654 Blair Medium321 Obama Low

Name

Client IDFront Office

Client

Client Type

LEI

Risk Client

Risk Rating

aggregates

Big data and sematic technology

6

Objective Historical Data Point ModelData panoply Duplication Semantic accessData congruence Transforms Global languageData access SQL

- One database at a time- No intelligence

SPARQL - Across databases- With inference

Visibility Silo by silo GlobalControl & lineage Distributed IndustrialDesign Physical Logic & semantics

Let’s compare & consider

7

The Data Point Model

8

Value Value SetData Point

Aspect

Context

Many

Value

1

The data point meta model separates the data point and the values

Reverse Engineer a Report into a DPM

9

Report NameY Axis Aspect Y Axis Value Set Name Y Axis Coordinate Aspect Values

ReportableAspect

X Axis Aspect

X AxisValue Set

X AxisCoordinateAspect Values

Package Name Reportable Aspect Values

10

Business Entity

Reverse Engineer a Data Base into a DPM

Class Level Adaptor

Attribute Adaptors

Adaptors Class Level Aspect

Attribute Level Aspect

Attribute LevelValue Sets

Resources

Designing a new viewpoint DPM to DPM

11

A third DPM wired together from 2

existing DPM

Regulation may be the driver but efficiencies

will evolve from a universal language across the big data

technology curve

Next Steps towards the Model DR strategic data aggregation solution

Select legacy

systems for

ModelDR to

reverse

engineer into

DPM format

ModelDR ‘wires up the new DPM viewpoint to an existing or new database

Model DR

forward

engineer

s a query

drawn

from the

new

viewpoint

New reports are drawn from old system architecture

Assessment of tactical transition to the ModelDR strategic solution