Scalable – from Startups to Enterprises

WATS offers multiple pre-paid data plans to give you a fixed and predictable subscription cost. These data-plans are based on the amount of test data that you plan on uploading for processing, regardless of how many systems you source this data from or how many users that need access to the data.

Should your sales and production volumes be higher than forecasted, all paid subscriptions gives you the option of analyzing data beyond your included data quota. Either for a one-time over-consumption fee based on the actual data consumption for the previous month. Or by simply upgrading your data-plan. Annually paid plans also includes data-rollover for when your data consumption for the month is less than your included data-quota.

This WATS subscription model provides you with the ideal mix of flexibility and cost-predictability, and allows you to scale your solution from early stage Startups all they way to large Enterprises.

What do you mean by 50 and 100 MB included in the subscription plans?

One of the components in the WATS subscription model is the volume of test and repair data that you process. We measure this in the megabyte size of converted test reports uploaded to your WATS account per month. 50 and 100 MB are included in the base-level plans per month, and you can increase these sizes through pre-payable add-ons. The average test report in WATS is approximately 50 kB, meaning that 50 MB equals 1000 such reports analyzed each month.

How does WATS calculate the consumed data?

The size of data processed is calculated AFTER the data has been converted into our standard XML format and received by your WATS account. And it is the size of these XML files that are used to calculate your actual data consumption. In other words, if you are post-converting your test reports to WATS, the size and format of the original report file is irrelevant.

What are some expected sizes of converted XML files, and examples of cost per test report?

The content of a test report varies greatly from company to company, product to product, and test process to test process. A rough estimation for a test report containing single-numeric measurement test are shown below.

#Test Steps per reportSize per reportApproximate number of reports analyzed per month with 300MB data-planApproximate cost per test report processed with WATS Analytics 300MB data-plan
5020 kb15000€ 0.04
13050 kb6000€ 0.1
20075 kb4000€ 0.16
350125 kb2400€ 0.26

How can we calculate our requirement for included data per month?

There are two alternatives to get a good understanding on how much data you need.

  1. Download this Excel calculator and input your production volumes and the content of your different test reports and formats.
  2. Run a free WATS Trial where you upload your own production data. We can then show the exact size in total and per test report, that you can use to extrapolate out to your total production volume.

How can we estimate the data processing cost per product that we produce?

With the WATS pricing model, you can very easily assign a data-processing cost component to each product. This makes good sense, since the value added to your company with Manufacturing Intelligence is very related to the fixed and overhead costs of manufacturing that again are spread across the Cost-of-Goods-Sold. A basic estimate can be found by identifying the number of UUT reports that goes into a final product, the total size of these, and the ratio of this compared to your total data consumption and subscription price.

WATS Subscription price per test report

How can we keep track our monthly consumed data?

The Account Page section inside of your WATS account will provide you with information on your current and historical consumption of data. You will also receive a notification if the quota is exceeded, so that you can determine if you would like to upgrade to a higher data-plan for the current month, or pay a one-time fee for the current overconsumption.

We do not want prices that are variable as they provide less predictability of our budget

The good option is then to select a pre paid data-plan that is well beyond the size of your generated data from manufacturing. When this is combined with our standard data-rollover feature, the probability that you will encounter variable overage rates are minimal.

A better option is to budget for a plan beyond your requirement, and request an internal Frame Order for this. But then activate the subscription on a lower priced plan. That gives you the flexibility to upgrade as needed without paying any premium.

We will host the solution internally, how do you calculate the size of data that is processed?

This model does not apply for On Premise installations. For On Premise, the cost is based on licenses for the selected features, and number of connected test systems. In addition there is an annual service and maintenance that is calculated based on the initial license cost. Contact our sales team for more info on this license model.

We have very high production volumes. How much data per month is WATS able to process?

Our standard pre-paid options exceeds 300 GB of converted test data processed per month, that equals more than 6.5 million test reports per month, at 50 numerical measurements per report. Contact us for a discussion if your requirement goes beyond this.

We have very low production volumes, and the price per processed report becomes high. What should we do?

There are two categories of savings WATS contributes to, variable production costs and different types of overhead costs. The relative sizes of these savings will depend on your production volumes.

The per-unit-saving (price-per-processed-report) view is more appropriate where the volumes are relatively high, as you can evaluate the potential savings per product built vs the subscription price.

When production volumes are low it is likely that savings in overhead costs are more prominent, and you should rather emphasize potential time savings for staff such as Test Engineering and R&D who no longer needs to develop or maintain custom tools, or do data mining.