Risk Data Aggregation
& Reporting
Adjustments and traceability – BCBS 239
Risk Data Aggregation
& Reporting
Corrections and traceability
Client testimonials
Interview: Silvia Caffi
Intesa Sanpaolo
Data Technology Information Systems Management Manager
Silvia Caffi participated as a speaker at the Irion Innovation Day 2019 event, held in Milan at the Cariplo Foundation.
Among the topics addressed:
audit, data quality, data aggregation, reporting, risk management
REQUIREMENTS, CHALLENGES & SOLUTION
The need
A unified, traceable, and maintainable solution
Efficiency
Unique and centralized solution with all the classic Data Management features
Traceability
Storage of all adjustment operations (data and metadata).
Search and reporting features.
Maintainability
New applications are added to the already enabled platforms via parametrization.
Automated adaptation to changes that applications make to data structures (tables, columns) without manual maintenance.
The solution
Adjustments and traceability with Irion EDM®
Capabilities
Some of the Irion EDM® features used:
Metadata Driven Engine, Execution & Datastore
Data Editing & Human Task Interface
Business Workflow & Collaboration
One-Click Web API
External Command & API Call
Results achieved
October 2018: Active Remediation Repository
December 2018: Active Remediation Engine
July 2019: Active Remediation Explorer
Average E2E processing time:
20′- 40′ for 8 million records table
From publishing to storing on the Remediation Registry
The challenges
Data Editing
Integration
Differences related to data source
(Teradata, SAS, Oracle)
Differences related to database use model.
Metadata Complexity
Dictionary of adjustable objects, available and not, including structure information such as columns, data types, primary Key, where condition, etc.
Data Quality
Need for formal and key controls on the adjusted records based on the metadata the application provides.
Usability
Timely and massive Data Editing via script
Orchestration
Request Response
Services
On-Demand
Process Activation
Integration
Differences related to data source
(Teradata, SAS, Oracle)
Differences related to database use model.
Metadata Complexity
Dictionary of adjustable objects, available and not, including structure information such as columns, data types, primary Key, where condition, etc.
Data Quality
Need for formal and key controls on the adjusted records based on the metadata the application provides.
Usability
Timely, massive Data Editing via script
Orchestration
Request Response
Services
On-Demand
Process Activation
You may also be interested in:
