Chargeback use case - more generally, Enable policies to create/define metadata using arithmetic expressions.

In summary, customers want to be able to perform arithmetic expressions and, if possible, leverage db2wh functions when defining policy to assign value to a tag. For example, customer wants to assign chargeback amount to a tag, "cost" as follows:
cost = size * (cost_per_byte[tier])

oday, there are two major hurdles for doing this:
A. Discover does not enable arithmetic calculations in policy definitions.
B. Discover does not enable user-defined arrays such as the cost_per_byte array above. This could be accommodated by defining a policy for each tier though. For example, the filter would be:
tier in ('nvme')
and then calculate
cost = size * cost_per_byte_nvme
but this is still prevented by A. above.

If Discover had this capability, it could be used by customers to immediately see the value of Discover in how it can identify how to reduce storage system costs. This has been requested by customers and sales teams -again yesterday by NTT.

Even a simple step in this direction could be useful, e.g., enable multiplication so that, with tags cost, size (builtin), and cost_per_byte, they could assign value as:
cost = size * cost_per_byte
This would require user to assign a cost_per_byte value with another policy, but at least they can achieve end goal of having Discover calculcate chargeback.

Finally, yes, the user would have to sum the columns in the report generated by Discover. But, again, at least Discover is doing the "heavy lifting" for chargeback use case.

It's easy to imagine other use cases, including ternary:
cost_per_byte = (owner in ('isom') ? 0.05 : 0.03

TEMPERATURE = (atime < now() - 90 day) ? ARCHIVE : HOT

cost_savings_tape = cost - tape_cost

cost = cost + pii_search_charge

etc.