> ## Documentation Index > Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt > Use this file to discover all available pages before exploring further. # Design limits > Guidance on key choices when designing a limit, including KPI type, polling frequency, warning threshold, and scope. This section outlines your available choices when creating limits. In particular, it focuses on the following fields of the [Limit Structure](./create-limit-ui#create-a-limit-structure) panel:

Field Name	Description
Rule	The supported limit rules are: - Greater Than: The limit has a breach status when the measure value is greater than the specified value. - Less Than: The limit has a breach status when the measure value is less than the specified value.
Warning	Enables or disables warning status when utilization reaches a specified percentage of the limit value. This is useful when you want to monitor when limits have high utilizations, for example, over 80%.
Warn when utilization reaches % of a limit	The warning threshold defines how close the value is to the limit before triggering a warning. The KPI status is displayed as an amber triangle in the pivot table when the status is a warning. For example, for a “greater than” limit of 10,000 and a warning set at 90%, a warning is generated when the value reaches 9,000, which means there is 10% of the limit remaining before a breach. For a “less than” limit of 10,000 and a warning set at 90%, a warning is generated when the value reaches 11,000, which means there is 10% of the limit remaining before a breach.
Value/Absolute Value	Sets whether the measure value should be interpreted as an absolute value when comparing to limit value. This is useful, for example, when you want to set sensitivity limits, which can be positive or negative numbers, but should be monitored as an absolute value.

In essence, you have the following options available when designing a limit: * **Rule**: Choose between **Greater Than** and **Less Than**. * **Warn utilization reaches % of a limit**: Choose between **true** and **false**. If **true**, specify the percentage. * **Absolute Value**: Choose between **true** and **false**. This means that there are 8 possible combinations that can be used when designing a limit:

	Rule	Warning	Absolute Value
1.	GREATER\_THAN	True (80%)	True
2.	LESS\_THAN	True (80%)	True
3.	GREATER\_THAN	False	True
4.	LESS\_THAN	False	True
5.	GREATER\_THAN	True (80%)	False
6.	LESS\_THAN	True (80%)	False
7.	GREATER\_THAN	False	False
8.	LESS\_THAN	False	False

The following section visualizes what this means for your limits. ## Overview In the following examples we will use similar data to illustrate the different combinations of limit design. The data is as follows: * the limit value will be 1,000 or -1,000 * when used, the warning threshold will be 80% of the limit value In the cases where the limit uses an absolute value, the visualization of both the negative and the positive limit will be the same, so only one diagram is required. In the following diagrams, given the scenarios for each case, the colored zones illustrate numerical regions where the limit will: * breach, denoted by red zones * warn, denoted by amber zones * pass, denoted by green zones ### Case 1

Rule	Warning	Absolute Value
GREATER\_THAN	True (80%)	True

### Case 2

Rule	Warning	Absolute Value
LESS\_THAN	True (80%)	True

### Case 3

Rule	Warning	Absolute Value
GREATER\_THAN	False	True

### Case 4

Rule	Warning	Absolute Value
LESS\_THAN	False	True

### Case 5

Rule	Warning	Absolute Value
GREATER\_THAN	True (80%)	False

#### Positive Limit Value (1,000) Case 5 positive

#### Negative Limit Value (-1,000) Case 5 negative

### Case 6

Rule	Warning	Absolute Value
LESS\_THAN	True (80%)	False

#### Positive Limit Value (1,000) Case 6 positive

#### Negative Limit Value (-1,000) Case 6 negative

### Case 7

Rule	Warning	Absolute Value
GREATER\_THAN	False	False

#### Positive Limit Value (1,000) Case 7 positive

#### Negative Limit Value (-1,000) Case 7 negative

### Case 8

Rule	Warning	Absolute Value
LESS\_THAN	False	False

#### Positive Limit Value (1,000) Case 8 positive

#### Negative Limit Value (-1,000) Case 8 negative

## Setting the limit value to 0 We will also consider four special cases where the limit value is 0. When the limit value is 0, it is not possible to generate a warning. This is because the calculation of the warning range multiplies the warning threshold by the limit value, which always results in zero in this case. This also means the [utilization](../../cube/utilization) cannot be calculated due to the zero denominator. It is also not possible for breaches to occur when the limit value is 0, the rule is set to **LESS\_THAN**, and the absolute value is set to **True**, as the measure value will always be greater than or equal to 0. This is shown in [Zero case 4](#zero-case-4) below. Combinations with a limit value = 0:

	Rule	Absolute Value
Zero Case 1	GREATER\_THAN	True
Zero Case 2	GREATER\_THAN	False
Zero Case 3	LESS\_THAN	False
Zero Case 4	LESS\_THAN	True

Rule	Absolute Value
GREATER\_THAN	True

Rule	Absolute Value
LESS\_THAN	True