IBM Aspera licensing explained.

A volume based metric, not a core based one

Aspera moves large data sets at high speed across networks, and its licensing reflects that purpose. Rather than counting processor value units across the cores it runs on, Aspera entitlements are typically expressed in terms of data volume transferred or the capacity of the transfer tier deployed. The practical consequence is that the usual sub-capacity conversation, which dominates products like WebSphere and Db2, is not the center of an Aspera finding. The center is measured volume against the entitled volume, and whether the tier deployed matches the tier purchased.

Where Aspera findings come from

Because the metric is volume and capacity, the exposure points are different from core based products:

• Transferred volume exceeds the entitled allowance. Where the data moved over the measured period exceeds the volume the entitlement covers, the gap is the finding. The first question is always whether the volume attributed to your entitlement is measured correctly and over the right period.
• A higher capacity tier deployed than entitled. Aspera transfer capabilities come in tiers, and running a higher throughput tier than purchased creates an entitlement mismatch independent of total volume.
• Additional components counted as separate entitlements. Aspera deployments often include several cooperating components, and counting an included component as a separate chargeable product inflates the finding.
• Embedded or bundled Aspera used beyond its scope. Aspera ships embedded inside other IBM offerings with restricted rights, and using an embedded instance outside its allowed scope produces a finding that looks like standalone Aspera.

How an Aspera finding is challenged

The defense is to reconstruct the volume and capacity picture from your own measurement rather than accept the audit's attribution. That means confirming how transferred volume was measured and over what period, matching the deployed tier to what was entitled, separating included components from separately chargeable ones, and distinguishing embedded Aspera from standalone entitlements. Each of these is a question of correct attribution, and correcting attribution usually narrows a volume based finding considerably, because the headline number rests on measurement choices that can be examined and corrected.