OWOX BI Transformation: Terms of usage

General information

Product Transformation provides users with the possibility to create object Transformation in the OWOX BI project. Transformation may have some Operations as the sequence of SQL queries. Every time when an Operation runs counts as 'Operation Run' and means a Consumption Unit.

One Operation Run has a limited amount of processed data - up to 20 Gb.

Excess of the processing limit is counted as a new Operation Run.

All Operation Runs are rounded to the whole hundred if less within a calendar month.

There is no difference in the calculation of how the Operation was run - automatically or manually.

There is no difference in what kind of SQL statement was executed (select, update, delete, etc) for calculating Consumption Units. They all apply the common rule about the amount of processed data.


Example of Operation Run calculation in one Transformation

There are two cases of running the equal Transformation 'Sessions' with three Operations inside. They have different amounts of processed data.

The next table presents the calculation logic of the Operation Run Consumption Unit for these two cases.

Operation name Case 1 Case 2
  Processed data, Gb Operation Run Processed data, Gb Operation Run
#1. Preclean data 5 1 (<20Gb) 28 2 (20Gb+8Gb)
#2. Preparation data 16 1 (<20Gb) 216 11
#3. Creating sessions 12 1 (<20Gb)


4 (3*20Gb+19Gb)
Total Operation Runs in one Transformation run 3 (1+1+1) 17 (2+11+4)


So, in this example, we can see that calculation is made by Operation, but not by Transformation. The Transformation just summarizes the result of the Operation Run for all successfully executed Operations.

The result of such calculation is presented in the history log of the Transformation for every Operation and the client is able to see and validate it.


Example of Operation Run for a month

OWOX platform collects the result of every Operation Run calculation and provides this summarized result.

This example uses the previous example for the Transformation 'Session' calculation but for a month period.

Activity Case 1 Case 2
Everyday Transformation run 'Sessions' for the previous day

1 Transformation run per day

3 Operation Run per day


Every week Transformation 'Sessions' run for the previous week


1 Transformation run per week
17 Operation Run per week
Total Operation Run that was run automatically per month 90 (3×30 days) 68 (17×4 weeks)
Manual Transformation run that users made for any reason per month

3 Transformation run
9 Operation Run

2 Transformation run
34 Operation Run
Total for automatic and manual Transformation run per month 99 Operation Run
90 auto + 9 manual
102 Operation Run
68 auto + 34 manual
Grand total Operation Run after rounding up to the monthly bill 100 200
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.