Detailed business description of the metric, containing the purpose of the metric and information helpful for understanding the metric’s calculation.

For instance, Occupancy (%), might be described as: "Occupancy density calculated as the Number of Occupants/ Number of Seats"

The business import of the metric. This text states what the metric means and what actions managers might take based on that metric's information. For instance, the implication for "Occupancy (%)" might be:

"Too low of a value indicates that the portfolio is not being used as efficiently as possible. Too high indicates that space is cramped and the organization cannot accommodate change or growth. More space or an alternative workspace strategy may be indicated."

All metric values are of Numeric data type. This field indicate how the metrics display controls should display the metric values:

• Number -- as they are (e.g. 100,000.12)
• Percentage -- multiplied by 100 (e.g. 23%)
• Base-Unit Area -- converted from the stored value in the Base-Area Units of the project (e.g. sqM) to the user-display area units (e.g. sqM or sqft depending on the user's locale)
• Organizational Budget Currency -- converted from the common budget currency (as defined in the AbCommonResources-Budget Currency application parameter) to the user-display currency (e.g. dollars or euros based on the user's locale).

By default all metrics are collected and stored with 2 decimals of precision in the afm_metric_trend_values table. This field specifies the rounding that the display controls should perform on values when displaying them.

For instance, you can display "10,000,000.12" with the following rounding values:

• “2 Places” -- 10,000,000.12
• “1 Place” -- 10,000,000.1
• “0 Places” -- 10,000,000.

• "Hundreds" -- 100,000H

• “Thousands” -- 10,000K
• “Millions” -- 10M

• "Billions" (i.e. "thousand-millions") -- 0.01G

If this value is "Active", the metrics rule will collect metric trend data per the metric definition.

If this value is "Deactivated", the metric rule will skip this definition. Useful for turning off metrics that are tested but that you do not want in production.

Records the recurring rule pattern that defines the collection recurrence -- how often the metrics rule will run this particular metric definition. The metrics rule runs every day. If the current date matches the Collect Recurrence (e.g. Monthly, on the 1st Day of the Month, Yearly, on the Last Day of the Year, etc.) the metrics rule will collect a set of metrics trend data according to the metric definition.

Ignore the existing Collect Frequency ( collect_frequency ) field, which is used for legacy metric defined prior to V.21.2.

Use this field when defining metrics on transaction tables to specify the date the metric rule should examine to determine if a record falls within the current recurrence interval. The record falls in that interval if the value of the collect_date_field falls within the interval. The metric rule measures the interval from the metric recurrence date back to the beginning of the recurrency period (e.g. back one week, one month, one year, etc. depending on the recurrence).

Do not use this field if your metric definition is on an inventory table. In this case, the metric rule creates a snapshot of the inventory data on the recurrence date.

This attribute is used for trend direction interpretation, which specifies whether an increase in this metric’s values from the last time period represents a positive or negative outcome for the organization. Possible selections are:

• Smaller is Better
• Larger is Better
• On Target is Better
• No Significance

When displaying stoplight colors, the Report: Trend Direction indicates whether the program compares against the "high" limits (when "Smaller is Better", the "low" limits (when "Larger is better") or both ("On Target" is better).

Specifies the numerator metric (e.g. fin_RealEstateOpEx_monthly) in a ratio metric.

If you specify a Ratio Metric Numerator, you must also specify a Ratio Metric Denominator.