Presentation is loading. Please wait.

Presentation is loading. Please wait.

Objectives, solution architecture and development status

Similar presentations


Presentation on theme: "Objectives, solution architecture and development status"— Presentation transcript:

1 Objectives, solution architecture and development status
Tool for Undertakings Objectives, solution architecture and development status

2 Overview of the solutionn Tool for Undertakings (T4U) and NCAs toolkit
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 Windows T4U – component to be used by Undertakings to manage (produce, edit/correct, review, etc.) their XBRL filings with a Windows application 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 NCAs Undertakings 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.

3 Work streams first betas
TFU Work stream Windows T4U (June Release) provide a user friendly interface for rendering Solvency II templates, manual input of data and validation; create, read and validate XBRL reports; validate and view the created XBRL reports using a third-party viewer and validator; database-based: built around a database with architecture similar to CRDIV, and with structures to facilitate extensive data migrations; import capabilities from Excel (plain Excel files). Excel Add In T4U (August Release) provide input forms for the Solvency II templates with functionalities similar to the Windows application, but based on Excel. developed as a back-up solution in case the Windows based application does not meet all the user requirements as agreed in the functional requirements (the excel import function); in comparison to the Windows application this will be: easier to integrate as it will be Excel based; better for automatic migration of data to Excel structures; more complex to develop and to deploy. NCA Toolkit Work stream (September Release) - as a second work stream the NCA Toolkit will be developed to extend the above and add the following functionalities to the tool: handling of XBRL reports received by the NCAs from the undertakings and facilitating second-level reporting to EIOPA; provision of guidelines on the creation of new input templates and/or the algorithm to generate input templates for NCA extensions; provision of tools that may help NCAs when creating extension taxonomies; provision of basic business intelligence functionalities using external tools. June August September These timelines correspond to versions made available to EIOPA members. Public version may differ 1 or 2 months.

4 T4U: value for undertakings and NCAs
The Tool for Undertakings (T4U) is a tentative solution aiming to enable small and medium reporting entities as well as European National Competent Authorities to input/load data using common interfaces and manage data using centralised database, designed to process data structures represented in the EIOPA Solvency II XBRL DPM-based taxonomy, in order to produce XBRL reports compliant with the Solvency II requirements. Help for Undertakings with: Help for NCAs with: 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 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 aiming to be in PoC functionality after-PoC functionality Legend PoC functionality

5 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

6 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 1 2a Translations DPMdict BT Business Rules 9 BL Deci-mate A Flags (FS concepts), derived values, subsets (aggregations) 22 EBA MS Access DPM Database AT Technical annotation 2b D T4U 8 Interim format/tools C B 10 5 DPM Architect EB Excel Add-In 4 XBRL taxonomy E Database H 3a 6 Design stage DPM Metadata Windows application F 12 V Validations 7 EBA-like deliverables (PDF, XLS) DR 3c DPM-RS map G 21 Aggregations AA Other UIs (e.g. mobile) 16 W DV 3b Definition of views Relational Structures Excel RS Views 23 RX 3f Applications’ information

7 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

8 Architecture (Secondary reporting)

9 T4U Database DPM Metadata and Data vs Relational Structures
Templates Data in Relational Structures: S Page PL C10 C20 C30 C40 C50 R10 2345 345 436 R20 R30 R40 4567 R50 234 S C10 C20 C30 C40 12 PL 1001 0.15 322 ES 2034 0.34 Table: 1365_S InstanceID Page R10C10 R10C20 R10C30 R10C40 R10C50 R20C10 1 eu_GA:PL 2345 345 436 Table: 1699_S InstanceID C10 C20 C30 C40 1 12 PL 1001 0.15 322 ES 2034 0.34 DPM Annotated Templates Metadata DPM and Relational Structures Mapping: Table: mTable TableID TableCode 1365 S 1699 S Table: mAxisOrdinate AxisID OrdinateID OrdinateCode IsRowKey 122 201 10 202 20 203 30 204 40 205 50 123 210 211 212 213 214 124 215 131 428 true 132 429 133 439 440 Table: mOrdinateCategorisation OrdinateID DimensionCode MemberCode 201 MET mi2 BAS x26 202 mi5 203 mi10 204 mi12 205 mi1 210 PFL x12 211 x24 212 x32 213 x43 214 x23 215 CTP open 428 IDC 429 439 mi67 440 pi68 Table: mMapping TableID RSTableName RowColumnCode Signature 1365 S PAGE1 s2c_CTP(*) R10C10 MET(s2md_mi2)|s2c_BAS(s2c_BL:x26)|s2c_PFL(s2c_PL:x12) R10C20 MET(s2md_mi2)|s2c_BAS(s2c_BL:x26)s2c_PFL(s2c_PL:x12) 1399 S C10 s2c_IDC(*) S C20 S C30 MET(s2md_mi67)|s2c_BAS(s2c_BA:x12) S C40 MET(s2md_pi68) Table: mTableAxis TableID AxisID 1365 122 123 124 1699 131 132 133 DPM Data: Table: dFact InstanceID Signature Value Unit Decimals 1 MET(s2md_mi2)|s2c_BAS(s2c_BA:x26)|s2c_CTP(eu_GA:PL)|s2c_PFL(s2c_PL:x12) 2345 EUR MET(s2md_mi10)|s2c_CTP(eu_GA:PL)|s2c_PFL(s2c_PL:x12) 345 MET(s2md_mi12)|s2c_CTP(eu_GA:PL)|s2c_PFL(s2c_PL:x12) 436 MET(s2md_mi67)|s2c_BAS(s2c_BA:x12)|s2c_CTP(eu_GA:PL)|s2c_IDC("12") 1001 MET(s2md_pi68)|s2c_CTP(eu_GA:PL)|s2c_IDC("12") 0.15 pure 2 MET(s2md_mi67)|s2c_BAS(s2c_BA:x12)|s2c_CTP(eu_GA:Es)|s2c_IDC("322") 2034 MET(s2md_pi68)|s2c_CTP(eu_GA:ES)|s2c_IDC("322") 0.34 Table: mAxis AxisID Orientation 122 X 123 Y 124 Z 131 132 133 Table: mOpenAxisValueRestriction AxisID HierarchyID 124 12 132

10 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) NetOffice (MIT License) ExcelDNA (Custom open License) Obejctlistview: for open tables in Windows T4U Trello, Microsoft Word+ Project + Visio for documentation Arelle

11 Technical solution implementation

12 Current Team


Download ppt "Objectives, solution architecture and development status"

Similar presentations


Ads by Google