- Source data is captured in dedicated silo's
- Easy to understand mapping between source data and datasets
- Less control over data quality
- Limited data lineage capabilities
The data flows within RegNxt
Manual vs automated data flows
When it comes to populating the reports, users can feed the cells through manual input or copy-past operations from external sources. (see blue arrows).Of course, automated data flows are the preferred solution. Not only are programmatic data loads less error-prone, they also offer immediate or scheduled triggering (allowing outside business hours loads).
For some existing vendor platforms, we offer out-of-the-box plugins, which do not need tailor made ETL (see green arrows).
For those cases,we have already prepared the necessary processes to transform the vendors data model into RegNxt's optimized data model.
When data is transferred diretly from the source data, client specific ETL processes are to be developped (see purple arrows).
The ideal combination, is having automated data flows, with manual adjustments (when corrections are needed).
Minimal vs full level automated data flows
In belows diagram, the different options are shown on how to integrate with the source data.We offer 3 different levels of integration, each with their pros and cons:
Minimal integration
Hybrid integration
- Taking advantage of granular source data
- All data is captured in generic (mult-purpose) data foundation layer
- Intermediate complexity turning into datasets
- Limited data lineage capabilities
Full integration
- Ful granularity of data
- Full control over data quality (could even serve to improve data quality in source systems)
- Full data lineage coverage (drill through between all layers)
- Complex implementation
- Heavy processing to move through the various layers
Common data flow
The dataset serves as central data feed for the workbooks, whatever scenario is put in place.
From there on, a standardized process can push the data into the workbooks.
Standard functionality covers both directions between workbook and report.
The workbook values can be transmitted into the submission format to generate a report, and generated submissions files can be imported back into a workbook.
From there on, a standardized process can push the data into the workbooks.
Standard functionality covers both directions between workbook and report.
The workbook values can be transmitted into the submission format to generate a report, and generated submissions files can be imported back into a workbook.
