Financial and regulatory bodies, such as the
EBA ,
IFRS and
CEN/WS XBRL, are using
data point modeling as a methodology for modeling financial and risk data submissions. In '
Developers' Notes: Importing Data and Models' we discussed translating data from the EBA data model to the data point model used by the
Firm Data Submission Framework (FDSF) (see also '
Data Designer: Modeling the Firm Data Submission Framework').
Figure 1 shows the results of that conversion. Here we see FinRep / CoRep model elements organised according to the FDSF data model.
 |
| Figure 1: FinRep / CoRep model elements using the FDSF data model |
As we mentioned in the Developer's Notes, this conversion is not necessary to use Data Designer. We can use any data model and associated data in Data Designer. But working off the same data model provides benefits. For example, we can produce
HTML documentation (figure 2) and
XSD generation based off the same model, providing a consistent look and feel to users.
 |
| Figure 2: Generated HTML documentation for FinRep and CoRep data elements |
Of significant value is the ability to reuse data elements between frameworks. For example, FDSF's financial statement data requests are based largely off of FinRep to manage overlap between them. Currently these same overlapping elements are managed separately between the two data sets. This introduces the risk of inconsistencies developing over time between two different versions of the same data element.
For example, 'Intangible assets' is a member of the FDSF domain 'Balance Sheet Level 1'. Instead of maintaing this separately in FDSF, figure 3 shows that we can create a hierarchy in FDSF that directly links to 'Intangible assets' in the 'Main category' domain of FinRep. That way if any aspect of this domain member changes (e.g., label, definition, etc.) the change will automatically be reflected in FDSF.
 |
| Figure 3: Adding a FinRep domain member to a FDSF hierarchy |
