Data Intelligence Metering and Billing
HiveMQ Data Intelligence bills on usage, not on feature tiers. Your monthly charge depends on how many nodes of your information model you keep active. HiveMQ does not charge for topic discovery or for data models, at any scale.
This page defines what Data Intelligence bills, how HiveMQ calculates the billed quantity, and what your invoice shows. For current rates and allowance quantities, see your order form, your checkout confirmation, or your confirmation email.
What Data Intelligence Bills
Data Intelligence applies two charges:
-
Active billable nodes: HiveMQ counts each tag that you activate, including assets and other tag subtypes.
-
Premium charge (computations & links): HiveMQ counts each active tag or field that takes its value from a computation or a link. A computation is a calculation or an expression.
HiveMQ assesses the two charges separately, so a single tag can incur both. For example, a tag that gets its value from a link counts as an active billable node and also carries the premium charge. HiveMQ never bills a field as a node. However, a computation or link on a field does incur the premium charge.
What Data Intelligence Does Not Bill
Data Intelligence does not bill the following parts of your information model:
-
Folders: This category includes the ISA-95 subtypes enterprise, site, area, and line.
-
Fields: A field is a child element of a tag that holds structured data, such as JSON. HiveMQ bills the parent tag, not each field.
-
Metadata: Metadata is a set of key-value entries attached to a node. Metadata is not a node.
-
Data models and their instances: When you create an instance, HiveMQ adds the tags of the model to your namespace as regular tags. HiveMQ bills those tags as active billable nodes. The instance itself carries no additional charge.
Node Activation
Activation connects your namespace to your bill. Data Intelligence counts a node because you activated it, not because the node exists. You can model as much of your operation as you want and pay only for the part that you activate.
Every node starts inactive. The rule applies to nodes that discovery finds and to nodes that you add manually.
An inactive node is still a full part of your namespace. You can create it, rename it, move it in the hierarchy, add metadata, and define computations that use it. None of that work depends on activation.
Activation controls execution, not definition. When you activate a node, HiveMQ stores its history, reports deviations, and runs its computations. The node counts toward your bill each day that it is active. While the node is inactive, HiveMQ performs none of this work, and the node does not count toward your bill.
A field follows its parent tag, and a data model instance activates as a whole. You cannot activate a field or an instance on its own, and neither adds directly to your bill. For the full list of what carries no charge, see What Data Intelligence Does Not Bill.
How Activation Affects Your Bill
Activation applies to a whole subtree. When you activate a folder, HiveMQ activates every node beneath it. When you deactivate the folder, HiveMQ deactivates those nodes as well. Activation also reaches the nodes that supply the value of the node that you select.
Before you apply a change, a confirmation dialog in the console shows how many nodes the change affects and how many of them are billable.
Without the Data Intelligence add-on, the activation limit blocks any action that exceeds it. The dialog then reports how much of the limit is left, and offers an upgrade in place of the activation. See Activation Limits and the Free Allowance.
For the cascade rules, the steps in the console, and what a deactivation costs, see Activate and Deactivate Nodes.
Activation Limits and the Free Allowance
The activation limit and the free allowance are separate mechanisms. The activation limit controls what you can activate The free allowance controls what you pay for.
The activation limit caps how many entities you can keep active at the same time. HiveMQ checks the limit at the moment you activate a node, and never blocks a deactivation.
The free allowance is a monthly quantity that Data Intelligence includes for each billed category. HiveMQ subtracts the allowance from your metered usage before it prices the remainder. The allowance is part of your subscription and appears as a separate line on your invoice.
Two rules apply to every free allowance:
-
The allowance does not carry over between months. An unused allowance in one month does not increase the allowance in the next month.
-
Computations and links draw on a single shared allowance, not on one allowance each. Each one can consume the entire allowance.
The Data Intelligence add-on removes the activation limit for your organization. Without the add-on, the activation limit applies, and HiveMQ does not send you a Data Intelligence invoice. With the add-on, the activation limit no longer applies. HiveMQ meters your usage, subtracts the free allowance, and sends you a monthly invoice.
How HiveMQ Calculates the Billed Quantity
HiveMQ calculates your monthly quantity in six steps. All dates and day boundaries use Coordinated Universal Time (UTC).
-
Count each day. If a node is active at any point during a UTC day, the node counts for that day. A node that you never activate never counts.
-
Resolve the data source. Each tag or field resolves to exactly one data source per day. If more than one data source overlaps during the day, the last one applies. If no computation, expression, or link applies, the data source is MQTT, and the node incurs no premium charge.
-
Sum your organization. HiveMQ adds the daily counts of all nodes in your organization, separately for each category.
-
Monthly average. HiveMQ divides the sum of daily counts by the number of days in the calendar month. Days without data count as zero. HiveMQ rounds the result down to a whole number.
-
Subtract the free allowance. HiveMQ subtracts the free allowance of each category from the quantity of that category.
-
Price the remainder. HiveMQ prices active billable nodes at the graduated rate, and the premium charge at a flat rate per unit.
Rate Structure
Active billable nodes use a graduated volume rate. HiveMQ divides usage into bands, and each band has its own rate. HiveMQ charges each part of your quantity at the rate of the band it falls into. The effective price per node falls as your usage grows.
The premium charge uses a flat rate per unit.
Data Intelligence bills in arrears. Each invoice covers the month that has ended. For the current bands, rates, and allowance quantities, see your order form, your checkout confirmation, or your confirmation email.
What the Invoice Shows
Data Intelligence bills as a subscription that is separate from your HiveMQ broker invoice.
The graduated rate prints one line for each band that you consume, not one line for the category. A quantity that spans two bands therefore appears as two lines for active billable nodes. Each free allowance prints as its own line at a zero unit price, so you can see how much of the allowance you used.
The line descriptions on your invoice match the terms that this page uses.
Why the Console Count and the Invoice Can Differ
The activation limit and metering measure different things. The activation limit on the console shows how many nodes are active at a given moment. The metering counts on your invoice include every node that was active at any point during the month.
For example, you activate a set of tags, deactivate them, and activate a different set in the same month. You stay within the activation limit throughout. Your metered quantity still covers both sets, because each set was active during the month. In that case, the figure on your invoice exceeds the highest figure that the console showed.
Start and End of a Subscription
The billing cycle starts on the first day of each calendar month.
Days before your subscription starts and days after it ends count as zero in the sum of daily counts. However, those days still count when HiveMQ divides by the number of days in the month. A subscription that starts or ends in the middle of a month therefore prorates automatically, and needs no separate proration rule.
Related
-
Account & Administration Overview: Find billing, licenses, and add-ons in the console.
-
Organization: Manage the account container that owns your billing information.
-
Define Namespace: Create and organize the nodes that activation applies to.
-
Discovery: Approve discovered topics into your namespace.