110 likes | 496 Views
Tool for Undertakings. Objectives, solution architecture and development status. Overview of the solution n Tool for Undertakings (T4U) and NCAs toolkit. The main goals of the XBRT (component of which is the T4U) in order of importance are:
E N D
Tool for Undertakings Objectives, solution architecture and development status
Overview of the solutionnTool for Undertakings (T4U) and NCAs toolkit The main goals of the XBRT (component of which is the T4U) in order of importance are: • to easily create, edit/correct/complete and validate XBRL instance documents, in order to help Undertakings without XBRL knowledge to implement Solvency II harmonized quantitative reporting in XBRL, • to provide a reusable solution for other projects and specifically for NCAs’ local requirements, • to provide a reusable solution for internal EIOPA and NCAs’ needs to manage XBRL reporting. eXtensible Business Reporting Toolkit - a set of tools/services developed by/for EIOPA to manage the process of data description, exchange/collection, validation, storage, analysis and decision making, in particular related to the Solvency II information requirements modelled according to the DPM and exchanged in the XBRL format. Some components of this solution can be used by the Undertakings (T4U) or NCAs (XBRT component for national extensions, etc.). NCA Toolkit– component supporting NCAs with extensions and second level reporting Excel Add in T4U– component to be used by the Undertakings to manage (produce, edit/correct, review, etc.) their XBRL filings with an Excel Add In Windows T4U – component to be used by Undertakings to manage (produce, edit/correct, review, etc.) their XBRL filings with a Windows application NCAs Undertakings
T4U: value for undertakings and NCAs T4U Help for Undertakings with: Help for NCAs with: • XBRL technology: handle XBRL instances received from the undertakings and facilitate second-level reporting • substantial data volumes: structures to create efficient ETL • data presentation and input: rendering and modifying data with user friendly interfaces • customising / tailoring data scope collected using T4U: extension capability • data validation: validate data with XBRL and other alternatives • data analysis: provide basic BI capabilities • generation of XBRL Taxonomy according to Eurofiling Architecture • XBRL technology: create and read XBRL instances from source data • substantial data volumes: structures to create efficient ETL • data presentation and input: rendering and modifying data with user friendly interfaces • standardising European supervisory architecture: applying standards common with EBA and ECB • data validation: validate data with XBRL and other alternatives Legend PoC functionality aiming to be in PoC functionality after-PoC functionality
T4U functions: in- and out-of-scope Easy-to-use with multiple data input/load interfaces Generation of XBRL reports according to Solvency II DPM XBRL Taxonomy (Level 1 & 2) Reports and submissions management XBRL validation (open source component) for reported data XBRL load, validation and creation with database approach Support for other XBRL Architectures than EIOPA/Eurofiling DPM-based database for metadata and data storage Generation of XBRL taxonomy according to the Eurofiling architecture Advanced data analysis Basic BI analysis capabilities Second-level reporting support First-level reporting support/services for extensions T4U functionality Out-of-scope
Architecture (Design) • Business Templates and Business Logs • modification of content (preparatory/full) • inclusion of row/column codes • translations • flagging (aggregates, FS, derived values, etc.) • business/validation rules notation • DPM Dictionary and Annotated Templates • as above (BT+BL) but in structured manner (including normalization of tables) • business annotation – new approach (including codes, clear relations to hierarchies) • technical annotation – named ranges and styles • Database population • from DPM dict + AT using new business and technical annotation • reverse engineering of the input • migration of EBA MS Access content to T4Udb • Database • DPM Metadata – as in EBA + EIOPA S2 T4U specific structures • Relational Structures – explained later • Validation/Aggregations – defined as metadata using row/column codes; execution on Relational Structures • Applications’ information – localization and translations of menu, buttons, messages, … • Interfaces • Windows application – reading from DPM Metadata with Design stage; linking to Relational Structures in progress • Other – first draft of iOS app (reusing code/logic of Windows application) • Excel Add-In – works restarted now, • Excel RS Views – new concept under consideration • Longer term: • XBRL taxonomy generation (with DPM Architect engine) • other supportive deliverables 2a Translations 1 DPMdict 9 BT Business Rules Deci-mate BL A Flags (FS concepts), derived values, subsets (aggregations) EBA MS Access DPM Database 22 AT Excel RS Views 2b Technical annotation D T4U 8 Interim format/tools B C 10 DPM Architect 5 EB 4 Excel Add-In XBRL taxonomy E Database H 3a DPM Metadata 6 Design stage Windows application F V 12 7 EBA-like deliverables (PDF, XLS) Validations DR 3c G DPM-RS map Aggregations AA 21 Other UIs (e.g. mobile) 16 DV W Definition of views 3b Relational Structures 23 RX 3f Applications’ information
Architecture (Primary reporting) • Interfaces – work in progress on read/write to Relational Structures • Data in Relational Structures • validations (with support of views) on data in Relational Structures • migration of data in Relational Structures (between information requirements versions) • Maps and conversion between Relational Structures and DPM data • Generation/load of XBRL from/to DPM data using Arelle engine + validation if required
T4U DatabaseDPM Metadata and Data vs Relational Structures Templates Data in Relational Structures: DPM Annotated Templates Metadata DPM and Relational Structures Mapping: DPM Data:
Technologies used • EIOPA’s Subversion repository (Apache licence before GitHub was used) • IIS for the website and Arelle validation service • VM ware for testing machines • Microsoft Excel 2007 and 2013 (For Excel T4U and testing) • SQLite 3.0 Public Domain License (database repository, used as open source) • SQLite Studio (v 2.1.5) GNU General Public License (Database manager for SQLite) • SQLite POCO entities and SQLite driver + Entity Framework 5.0 (for data access) • Visual Studio (for all solutions except non windows based) • Xamarin (iOS and non windows interfaces) • C# with .Net framework 3.5 (Windows T4U) • C# 4.0 (Excel T4U add-in) • NetOfficehttp://netoffice.codeplex.com/ (MIT License) • ExcelDNAhttp://exceldna.codeplex.com/ (Custom open License) • Obejctlistview: for open tables in Windows T4U • Trello, Microsoft Word+ Project + Visio for documentation • Arelle