Important The Process Runs consumption units exclusively apply to the OWOX BI Transformation product.
OWOX BI Transformation: Terms of Usage
The OWOX BI Transformation product allows users to create a Transformation object within their OWOX BI project. A Transformation comprises one or more Operations, representing a sequence of SQL queries designed to prepare and update data stored in Google BigQuery within the customer's active Google Cloud Platform (GCP) project.
When a user runs a Transformation, all internal Operations are executed sequentially. Each successful execution of an Operation is calculated as a Process Run. These Operations are processed using the customer's GCP project, with all associated costs covered by the customer.
How Are Process Runs Calculated?
- Each successful execution of an individual Operation within a Transformation counts as 1 Process Run.
- At the end of each calendar month, the total Process Runs are rounded to the nearest hundred.
- It makes no difference whether the Transformation/Operation was triggered manually or automatically; both are calculated equally.
- The type of SQL query executed (e.g.,
SELECT,UPDATE,DELETE) does not impact the calculation of Process Runs.
Examples of Calculating Consumption Units
#1. Process Runs in One Transformation
The table below illustrates how Process Runs are calculated for running the Transformation, called 'Sessions', which contains three Operations.
| Operation name | Process Runs |
|---|---|
| #1. Preclean data | 1 |
| #2. Preparation data | 1 |
| #3. Creating sessions | 1 |
| Total Process Runs in one Transformation run | 3 |
In this example, we see that the calculation is made per Operation, not per Transformation. The Transformation simply aggregates the total Process Runs for all successfully executed Operations.
The results of these calculations are recorded in the Transformation's history log for each Operation, allowing users to review and validate them at any time.
#2. Process Runs for a Month
The OWOX BI platform collects the results of each Process Run and provides a summarized total. This example expands upon the previous case, showing how the 'Sessions' Transformation runs are calculated over a month.
| Action | Transformation runs | Process Run per month |
|---|---|---|
| Schedule Transformation run: Everyday Transformation run 'Sessions' |
1 Transformation run per day |
90 |
| Manual Transformation run: that users made for any reason |
3 Transformation runs |
9 |
| Total per month |
99 (90 auto + 9 manual) |
|
| Grand total Process Runs after rounding up to the monthly bill | 100 Process Runs | |
This detailed breakdown helps users understand how Process Runs are calculated both per Transformation and across monthly activity, ensuring clarity in usage and billing.
0 Comments