DPM ARCHITECT RELATIONAL DATABASE BACK-END

Transcription

1 DPM ARCHITECT RELATIONAL DATABASE BACK-END Miguel Morales IT Project Manager Banco de España EUROFILING XBRL WEEK Frankfurt, June 2017

2 DPM ARCHITECT FOR XBRL: COMPUTER AIDED DESIGN OF FINANCIAL MODELS 1 2 XBRL Taxonomy files Data Architects DPM Architect EBA Abstract Model EBA Taxonomy Architecture 2

3 DPM ARCHITECT: CURRENT STATUS Successfully used in Bank of Spain: taxonomies already in Production - Used by business users to author taxonomies Already in use by other institutions: - Support agreement with the ECB - EBA - Review of EBA taxonomies by most NCAs - New taxonomies and extensions by some NCAs - Database taxonomy loading process by some NCAs Available for free on request (no support): - Distribution list with 150+ users Please, subscribe to: 3

4 DPM ARCHITECT: SOME FEATURES User oriented - Hides XBRL technical details - Extensibility made easy - Solid modelling approach Table linkbase graphical editor - Link between the model and the view - Integrated instance editor - Generation of sample instance documents Powerful validation rule editor - Dual view of formulae: graphical view and data centric view - Generation of descriptions, error messages and documentation - Instance editor and test lab (plugins by vendors available) 4

5 NEW REQUIREMENTS DPM Architect Concurrent work - Integrity - Auditability - Reliability - Traceability DPM Architect XBRL Taxonomy files Relational Database DPM Architect XBRL Taxonomy files DPM Architect 5

6 Corporate Mode Standalone Mode STANDALONE VS CORPORATE MODE SQL*Server Compact DPM Architect XBRL Taxonomy files DPM Architect Relational Database DPM Architect 6

7 DPM ARCHITECT WORK MODES - Standalone: - Local database (SQL Compact) - Single logical area - Limited by local filesystem - Open model from XBRL files: - XBRL models: EBA 2.7, SRB LTD. - Open Corporate Model: - Database collaborative mode: - 3 logical areas 7

8 CORPORATE MODE LOGICAL AREAS 8

9 CORPORATE MODE ROLES Business side Data Architects Deployment Responsible Production Access (Read Only) IT Side Deployment to Collection System of XBRL instances Final deploy to DPM Architect Production Area 9

10 CORPORATE MODE - ACTIONS - XBRL Input - Import Taxonomies - Import Corrections - XBRL Output - Export Model 10

11 CORPORATE MODE IMPORT TAXONOMIES - Browse for Taxonomy Documents i.e. EBA Taxonomy The new taxonomies will be imported in the Work logical area. - Automatic dependency detection 11

12 CORPORATE MODE IMPORT CORRECTIONS - Import Corrections at taxonomy level - Browse for Taxonomy Documents i.e. corrections from already published taxonomies - The modifications will be imported in the Work logical área. - Keeps information from extensions: modules, labels 12

13 CORPORATE MODE - ACTIONS Actions on Logical Areas - >> Deployment Mode: Work Deploy - >> Deployment Restore Mode: Deploy Production - Deploy to PRODUCTION 13

14 CORPORATE MODE - ACTIONS Actions between logical areas Distribute Taxonomies - Functionality: - Distribute changes in one or more taxonomies from one logical area to another 14

15 CORPORATE MODE - ACTIONS Actions between logical areas Distribute Taxonomies - Steps: - Taxonomy selection (origin) - Compare taxonomy versions: - Report: Changes to be applied in the destiny (logical area) - Highlights differences - Save model 15

16 COLLABORATIVE WORK MODE Concurrent Work Timelime example Table F01.02 blocked New Version Work Mode Blocked Table F01.03 blocked 16

17 COLLABORATIVE WORK MODE Concurrent Work Blocked (Checked out) elements by another Data Architect Data Architect 2 Blocked 17

18 COLLABORATIVE WORK MODE Access to a element with a new version available Data Architect 1 New Version 02/06/ :54:06 "es_tf_ F (my change)" reloaded because it was modified by user 'qmmoral' at 02/06/ :53:11 18

19 COLLABORATIVE WORK MODE Save and Undo Changes - Save & Undo - Modified Element Level - Hierarchy Level 19

20 THE RELATIONAL MODEL BEHIND Internal object model of DPM Architect based on EBA s abstract model* Mapped to relational model using ORM techniques Possibility of creating views 20

21 OPENING THE DOOR TO NEW FEATURES Reporting capabilities - Analysis of usage of a certain concept - Unused concepts - Quality controls based on usage patterns - Changes report Metadata access - Existing export capabilities require ETL processes - Better integration with in-house solutions - Possibility to create additional services Collaborative work - Construction of models collaboratively - Discussions on changes 21

22 SCHEDULE March 2017 Mid April End of 2017 Development & testing Acceptance tests First Public Release 22

23 THANKS FOR YOUR ATTENTION Miguel Morales Subscribe!