SIRQ™ Engine (Qlik Rapid Deployment System) allows you to (re)configure the data reading algorithm, instead of rewriting the script from scratch for different applications.
SIRQ™ engine brings value both during the initial deployment, but also during the whole lifecycle of the analytical app developed.
The more complex ETL required, the higher delivered value by SIRQ™.
In the initial phase here are the benefits:
- better structured ETL definition (first look at the table level processes, afterwards get into the details, such as table processing conditions and afterwards fields processing details)
- easy to find details through filtering in any column
- increased transparency
- faster reuse of existing scripts, since the borrowing and adjustments are more structured and easier to follow
- easier reuse of existing interface, since final destination field names can be kept, and from here almost no interface editing is required (even further expanded in value with additional QQtools, such as QQrapid.interface engine)
- data processing documentation is the definition of the processing, step by step and can be provided to end users within Qlik™ apps interface, if required. Most important, though, there is no more deviation between processing definition and processing documentation, since they are one and the same !
- all the above means shorter development cycles, including smaller budgets and faster deadlines.
Since any BI project is a living project, that requires continuous improvements and adaptation to the ever changing markets realities and management needs, there are several additional long term benefits:
- easier (& faster & cheaper ) to identify ETL modification place and content
- keep documentation in sync with latest ETL modifications
- faster reuse in similar projects
- as a result a lower TCO of any BI app.
The SIRQ™ Components are:
1. Config SIRQ (tables)
are 2 related tables that contain the metadata regarding the ETL to be executed.
They can be used either as MS Excel tables, or Google Spreadsheets, but we recommend the usage of an (online) database for maximum value and ease of use.
Contains 1 row for each LOAD/ SELECT instruction to be executed in the ETL
This includes all the table-level details of the processing (source and destination table name, any special clauses for order, group, filtering, joining or concatenating, depivoting, etc).
Also contains options deciding to store and/or drop the tables or just keep them resident.
Both tables contains a column that allows fast activation/ deactivation of certain parts of the ETL.
Contains 1 row for each field created within each LOAD/ SELECT instruction defined in the SIRQ.Tables.
Most important columns are:
– SourceField_Formula – contains either the field or a formula that will define the field content
– Destination Field – with the final name of the field.
2. QQc_SIRQ (script subroutine)
The Qlik™ script subroutine provides reads of the above mentioned tables, converting the read metadata into a valid Qlik™ script and execution of the ETL process defined in the Config SIRQ tables.
For information about Qlik, visit this page: qlik.com.
If you are interested in SIRQ™ product, please fill in the form here !
In order to be in touch with the latest news in the field, uniques solutions explained, but also with our personal perspectives regarding the world of management, data and analytics, we recommend the QQblog !