Skip to main content
This page documents the Ratings cube’s measures. The Ratings cube publishes 14 visible measures of its own across five folders, not counting the engine’s contributors.COUNT and update.TIMESTAMP, and exposes them through the IRatingsCubeMeasures API. The scorecard results sit at the root of the Ratings folder, so the folder a user opens holds only the figures the template reports; the calculation intermediates and the surfaced configuration are in sub-folders beneath it. A measure’s folder and the accessor group it is declared on are independent: the folder says where a user finds it, the accessor group which interface returns it. Reported Metrics Count is the clearest case: it publishes into Ratings\Components but is declared on IRatingsBaseMeasures alongside the other base metric measures.

What does Metric Value show?

Metric Value is the value each metric is graded from. It switches on Rating Method: each rating component’s value factory reads the value, and the measure answers with the value of the component the metric declares. See Rating components for the value key that selects the factory.
  • With Period End Date on an axis, a metric read as a period average shows each period’s own value.
  • A metric read as its latest value shows that value only where Period End Date is not on an axis.
  • Selecting a subset of periods renormalizes the period weights over the periods selected.
This display rule applies to Metric Value alone. The ratings and scores read the latest value on every reporting period, so with Period End Date on an axis each period’s Internal Rating adds the scores of the components read as period averages, built from that period’s own values, to the scores of the components read as latest values. The building blocks are hidden. A hidden measure stays queryable by name in MDX and is left out of discovery. Every measure carries its own description in the cube metadata, which Atoti UI shows on hover.

Limits measures

The Ratings cube publishes four kinds of limit measure, only when at least one limit method is configured under limit-methods. They are exposed through IRatingsCubeMeasures.limitCapacityMeasures(), which returns null when no method is configured. Each measure shows a value only where the cell resolves to one counterparty and one relationship type the counterparty holds, however each is picked: by Counterparty ID, name or structure, and by Relationship Type or Relationship Type Name. Above that, the measures show nothing, since capacities do not add up across relationship types. For how bounds are written and the capacity is formed, see Limit capacity. A bound that returns a value that is not a number fails the query with an error naming the bound key and the method.