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.