Skip to main content

Metrics

The Metrics screen is the short list of licensing metrics Nomasx-1 supports. One line per metric. Each row carries the metric identifier (referenced by the Subscribed Licenses and Pricing tables) and a friendly description.

The metric defines how a component is counted — by named user, by processor, by employee, by application user…. Changing a metric on a contract changes how compliance is computed.

At a glance​

Nomasx-1 · Settings · Pricing · MetricsMETRIC IDDESCRIPTIONAPP_USERApplication UserNUPNamed User PlusPROCProcessor

Goal of the view​

  • Declare the licensing metrics the contracts use. Each metric is referenced by the Subscribed Licenses and Pricing tables.
  • Short by design. Most companies live with four or five metrics — APP_USER, NUP, PROC, EMP, SE.

Columns​

ColumnSourceWhat it tells you
Metric IDMET_ID — identifier.Reference used by other tables.
DescriptionMET_DESCRIPTION — friendly label.Oracle name of the metric (Application User, Named User Plus, Processor, …).

Edit dialog​

Click Add to declare a new metric, or double-click a row to edit.

Edit metricMetric IDNUPDescriptionNamed User Plus
FieldWhat to enter
Metric IDShort identifier (e.g. APP_USER, NUP, PROC, EMP). Referenced by Pricing and Subscribed Licenses.
DescriptionOracle official metric name. Used when matching against the contract.

Tips & best practices​

  • Keep the catalog minimal. A handful of metrics is enough — invent more only when a contract actually requires it.
  • Always describe the metric with the Oracle official label so the auditor can match it against the contract.