Licensed users are average plus power. Effective usage users applies the power multiplier and drives consumption only. The pool is provisioned upfront for the whole term and expires at term end, so the calculation is one bucket against total term consumption rather than a monthly cap.

Oracle publishes estimates measured against simple accounts. Testing the documented example questions against real transaction data has produced consumption above the published ceiling. The multiplier applies to every feature range that has not been manually overridden below. Per feature overrides always win.

Uses per day is the average per user per day. Type any value, for example 0.2 for one use every five days, or 3 for three a day. Basis switches a row from per user to an account wide total, which is what scripted features need since they fire per record rather than per person. Days chooses whether the frequency applies to working days only or to every calendar day.

Additional units are sold in fixed pools. No list price is published, so cost stays blank until a quote is entered. Pack counts are the negotiating figure on their own, because they show how far the granted allocation falls short before any price is agreed.

The final column scales every active feature by the same factor so the modelled mix fits inside the granted pool for the full term. Those are the frequencies a usage policy would have to hold people to, at the midpoint estimate.

This is the allocation rate that would carry the modelled usage through the whole term without a top up. Against the standard 1,000 per licensed user per month, the gap is the renewal ask.