Creating the metric catalog
The Metrics tab is the master list of approved companion metrics.
Each metric record defines the metric code, name, optional target, and optional unit of measure.
This creates the reference structure that teams use when they load actual and planned metric values later.
What you can do
-
Add a new metric.
-
Review the existing metric list.
-
Update metric definitions when naming or targets change.
-
Remove metrics that are no longer needed, subject to data dependencies in the environment.
Metric fields
|
Field name |
What it is for |
Mandatory |
|---|---|---|
|
Code |
Unique short code for the metric |
Yes |
|
Name |
Display name for the metric |
Yes |
|
Target |
Optional target value used for comparison |
No |
|
Units |
Optional unit of measure such as GB, Count, or Dollar |
No |
How to use Metrics well
Define metrics in a way that stays stable over time.
Use names that business and reporting teams will recognize.
Use units consistently so actual and planned values can be interpreted correctly in downstream reporting.
If a target is meaningful for the metric, define it once here so teams can compare actual or planned values against the same baseline.
When to add a new metric
Add a new metric when:
-
a reporting or planning workflow needs a non-financial measure that does not exist yet
-
the team needs to compare spend to output, demand, service volume, or another operational signal
-
a forecast or actual process depends on a governed metric name and unit
Good to know
-
Keep codes short and unambiguous.
-
Avoid duplicate metrics with slightly different names.
-
Align the unit of measure to the value you plan to upload later.
Next step
Related content