Numeric Values Scoring – RevOS Documentation & Support

Scoring of numeric values works based on two parameters:

Metric thresholds - lower and upper bounds

Metric direction - wherever higher value is considered to be ‘better’ or lower value is considered to be ‘better’

Please note that low/red values include lower bound values and high/green values include higher bound. See examples below.

Examples

Monthly active users (higher is better)

Monthly active users (MAU) is a frequently used metric that count a number of unique users active within one month. For this example we consider higher number of monthly active users to trigger higher score (green) where low number of monthly active users to be lower score (red). Based configuration above:

A customer account with MAU = 8 or lower still be considered red (lower bound included)

A customer account with MAU = 9 will be considered yellow

A customer account with MAU = 73 will be considered yellow

A customer account with MAU = 74 or more will be considered green (upper bound included)

Number of open issues (lower is better)

Another good example is number of open tickets, e.g. open tickets in the support and ticketing system of a customer account:

Here we want to score good/green when number of low and and score will decrease with increasing number of open tickets. In the example we will have:

A score of the customer account will be green if number of open tickets will be 1 or less

A score of the customer account will be yellow if number of open tickets will be 2

A score of the customer account will be yellow if number of open tickets will be 7

A score of the customer account will be red if number of open tickets will be 8 or more