ModelDrivers the BCBS239 agile data management framework
•Download as PPTX, PDF•
4 likes•1,592 views
The document discusses an agile data management framework for complying with BCBS 239 regulations, which require banks to aggregate risk data and reporting. It proposes using a Data Point Model and ModelDR tool to break down data into basic units and link them dynamically. This would allow banks to integrate risk data from different systems into reports more efficiently and at scale through reverse engineering existing data formats and databases, designing new data models, and generating customized reports and queries.
Recommended
More Related Content
What's hot
What's hot (19)
Similar to ModelDrivers the BCBS239 agile data management framework
Similar to ModelDrivers the BCBS239 agile data management framework (20)
Recently uploaded
Recently uploaded (20)
ModelDrivers the BCBS239 agile data management framework
- 1. BCBS239 The Agile Data Management Framework
- 2. • BCBS 239 Risk Data Aggregation issues • 3 Big Ideas • Agile data management implementation • Demonstration • Action • Further research BCBS239 Agile 2 data management framework Agenda
- 3. BCBS 239 BCBS239 Agile data management framework 3 The Basel Committee on Banking Supervision (BCBS) has issued Regulation 239; a mandatory requirement for banks to aggregate risk data and provide comprehensive reporting. Significant new capability of Risk IT and Systems is demanded
- 4. THE ISSUE How to industrialize business reporting 4
- 5. One Piece of Data…Many ways to View BCBS239 Agile data management framework 5 Counterparty Data “I have to…” “No way can we…” “We order…” “I don’t care…”
- 6. As a Result… Bringing data together for reporting is complex, costly and manual BCBS239 Agile data management framework 6 Business Unit A Business Unit B Business Unit C Business Unit D
- 7. How does a bank manage its risk data to BCBS239 standards on systems hard coded to everyone's disparate needs? BCBS239 Agile 7 data management framework
- 8. 3 Big Ideas Congruent panoply Global Language Industrialization How to industrialize business reporting 8
- 9. The Congruent Panoply • Congruent: in agreement or harmony • Panoply: an extensive or impressive collection BCBS239 Agile data management framework 9
- 10. Global Language BCBS239 Agile data management framework You Have to Have a Global Language • FIBO (Finance Industry Business Ontology) • Data Models 10
- 11. Industrialization BCBS239 Agile data management framework 11 • Robust • At scale • Strong tooling
- 12. The Agile Data Management Implementation BCBS239 Agile data management framework 12
- 13. 1: The Data Point Model 2: ModelDR as supporting tooling How to industrialize business reporting 13
- 14. The Data Point Model BCBS239 Agile data management framework 14 Value Value Set Data Point Aspect Context Many Value 1 The data point model breaks data down to atomic units And enables it to be wire together dynamically
- 15. Model DR is the Tool for: BCBS239 Agile data management framework Importing data into Data Point Model (DPM) form: Reverse engineering from many formats - spread sheet, XBRL, FIBO, database 15
- 16. BCBS239 Agile data management framework Designing New DPMs Create a new DPM viewpoint 16
- 17. BCBS239 Agile data management framework Export a new DPM Forward engineer from DPM format to spread sheet, XBRL, FIBO, database 17
- 18. DEMONSTRATION How to industrialize business reporting 18
- 19. Reverse Engineer a Report into a DPM Y Axis Aspect Report Name Y Axis Value Set Name Y Axis Coordinate Aspect Values Reportable BCBS239 Agile data management framework 19 Aspect X Axis Aspect X Axis Value Set X Axis Coordinate Aspect Values Package Name Reportable Aspect Values
- 20. Reverse Engineer a FIBO ontology into a DPM • FIBO (Finance Industry Business Ontology) BCBS239 Agile data management framework 20 - an industry initiative to define finance industry terms - provides for data congruence - facilitates data integration, supports business process automation and enables consolidated views across the financial industry - driven by Dodd Frank regulatory requirements for improvements in data quality and transparency - FIBO ontology defines financial terms and concepts without ambiguity • XBRL (eXtensible Business Reporting Language) - a business language used by major regulators to standardise financial reporting terms - XBRL allows universal communication through metadata taxonomies which capture and define financial concepts, terms & relationships
- 21. Reverse Engineer a Data Base into a DPM Business Entity Class Level Adaptor Attribute Adaptors BCBS239 Agile 21 data management framework Adaptors Class Level Aspect Attribute Level Aspect Attribute Level Value Sets Resources
- 22. Designing a new viewpoint DPM to DPM BCBS239 Agile data management framework 22 A third DPM wired together from 2 existing DPM
- 23. Forward Engineering • Viewpoints • Complex data queries • Databases • Specifications • Software BCBS239 Agile data management framework 23
- 24. Model DR is a data design & analysis solution; not a massive technology play BCBS239 Agile data management framework 24
- 25. Baby steps forward How to industrialize business reporting 25
- 26. The data scope is enormous - where & how to begin? BCBS239 Agile data management framework 26
- 27. Start with a tactical problem with 2 disparate database Establish success criteria Model DR reverse engineers two databases into DPM form - the congruent panoply! Create links to the two existing databases Assesses against the success criteria Model DR creates a view point from the two databases e.g. a new risk report BCBS239 Agile 27 data management framework Generate report drawn from the two databases Model DR forward engineers a query drawn from the new viewpoint
- 28. Research • Contact us: - http://uk.linkedin.com/in/gregsoulsby/ - https://www.linkedin.com/profile/simonroberts/ • Web site: www.modeldrivers.us • News on twitter: https://twitter.com/model_dr • This slide deck: http://www.slideshare.net/greg.soulsby/ • EDGAR – SEC online view of submitted: http://www.sec.gov/edgar.shtml • Arelle – Open source XBRL software report: http://arelle.org/ • XBRL Abstract model specification: http://www.xbrl.org/Specification/abstractmodel-primary/PWD-2012- 06-06/abstractmodel-primary-pwd-2012-06-06.html • DATA POINT MODEL presentation, Ignacio Santos, Bank of Spain : http://www.openfiling.info/wp-content/ upLoads/data/DPMvsMDM_1.pdf • EBA’s Data Point Model: A reporting game changer for management information: http://www.frsglobal.com/news_and_events/ebas-data-point-model-a-reporting-game-changer-for-management- information.html • EBA: Implementing Technical Standard (ITS) on Supervisory Reporting (Data Point Model): http://www.eba.europa.eu/regulation-and-policy/supervisory-reporting/implementing-technical-standard- on-supervisory-reporting-data-point-model-/-/regulatory-activity/consultation-paper • The Data Point Model methodology in the European Supervision: COREP/FINREP http://www.eurofiling.info/documents/DataPointModelMethodologyIB.pdf BCBS239 Agile data management framework 28
Editor's Notes
- Maybe need to list the 6 pllars?
- All this must be true: • There can only be one source of truth • It must be concrete and accurate • Many players must view it in their own, very differently ways Unlike, say, the Arts, in business data there can be only version of the truth. But there can, is, and should be many uses and interpretations of that. Client billing people say “Clients must have a name”. So the client on boarding people make that mandatory. Then the marketing department want to send the customer sales to the ad agency, and no way can the client name be passed over. So client is one data concept, with 2 directly opposite requirements. Obviously a trite example but that problem exists in thousands of cases, and there is no economy of scale, the problems compound and you get a bigger and broader organization.
- An example of an implication of multiple view points is in business reporting and analysis. If it was only a matter of duplication of processes and systems that would not be so bad. The real costs is in the manual, error prone, and impossible data integration. So lets look at non datapoint modelling approach to data management.
- All data must be available AND Integrated (meaning you can write queries across the whole scope)
- Reverse engineering Design tooling Forward engineering Global desktop accessibility
- Agile Data Management is our approach to implementing the 3 big ideas
- Model DR Provides all users with a single, enterprise view of portfolio risk and exposure. It is not a data warehouse Data Point Model (DPM) provides a literal representation of the data, identifying all the business concepts and relations, as well as validation rules. It contains all the relevant technical specifications necessary for developing an IT reporting solution.
- Jump across to real examples here
- Model DR pilot module - enables transition towards the larger system architecture decisions
- Xbrl – extensible business reporting language All the regulators have standardised on XBRL – A GLOBAL LANGUAGE – IF YOU REPORT DATA TO LOCAL REG. – report in XBRL Standardised way of reporting
- BCBS strategy development Tooling for industrialization Training BCBS specification Developing the global language (Meta modelling) Designing and building viewpoints (Data Point Modelling) Tools usage (reverse engineering, design, forward engineering) Competency assessment of current and trainees Execution