Create New Metric Definition form
Detailed explanation of the fields on the manual metric definition form.
| Field | Description |
|---|---|
| Basic details | |
| Name | Name of the manual metric definition. For example, Number of incidents. |
| Active | Option to mark the manual metric definition as active. |
| Description | Brief description of the manual metric definition. |
| Category | Category of the metrics data. The choices are as follows:
Note: This fields Nature, Direction, Precision, and Unit are only displayed only when the category of the manual metric
definition is Quantitative. |
| Unit | Unit for the manual metric definition. |
| Aggregation method | Method used to calculate the metric data for all the entities. For example, if you have a metric that you want to measure for multiple entities such as people, departments, or regions. You want to know how to calculate
the scores for each entity into a single score that represents the overall performance. Your choice of aggregation method depends on your goal of metric collection. For example, if you’re interested in overall performance and
want to account for differences in scale or size between entities, the sum or average is more appropriate. If you’re interested in identifying the best-performing entity, the maximum may be more appropriate, while if you’re
interested in identifying the worst-performing entity, the minimum may be more appropriate. The aggregation happens across time periods based on the frequency defined in the metric definition. If the frequency is monthly, the
calculation takes place every month. The four choices for aggregation methods are as follows:
|
| Precision |
Number of decimal places after the decimal point on a score. This field is automatically set to 0. When the Precision is set to 0, the result is rounded to the nearest whole number. For example, if a metric definition with Precision 0 calculates the values 7 + (5 / 2), the result rounds up to 10. When the Precision is set to greater than 0, the result is rounded to the nearest decimal point for the given precision. For example, Precision 1 rounds a result of 4.45 as 4.5. |
| Class | Class to which the metric definition belongs. The choices are as follows:
Important: This field appears only when the metric definition is created from the IRM suite of applications. It doesn’t appear for Operational Sustainability Management. |
| Calendar | Calendar to use for metric aggregation. Only the configured calendar options are available for selection. This field is automatically set to Standard Calendar. Note: Standard calendar refers to the
Gregorian calendar. |
| Frequency | Frequency at which the metric definition should collect the scores. The choices are as follows:
|
| First run date | Start date of the metric definition execution for the collection of data according to the frequency. |
| Data collection | |
| Data owner assignment type | Type of the data owner assignment for the metrics within the metric definition. The choices are as follows:
|
| Data owner type | Type of the data owner responsible for the manual metric definition. The choices are as follows:
|
| Data owner | Data owner responsible for the manual metric definition. Note: If you selected the advanced option for Data owner assignment type, this will be the assigned data owner if the assignment configuration
doesn’t return any results. |
| Result type | The format that you want to be available for responses in assigned metric data tasks. This applies to responses and overridden responses.
|
| Choice table | Table the choices are being populated from. This field appears when the Result type field is set to Choice. |
| Choice field | Field and its values from the selected table that are displayed for each choice. This field appears when the Result type field is set to Choice. |
| Choice condition | Option to only show certain fields or certain values within the Choice field under set conditions. Select Set conditions to open the condition builder. This field appears when the Result type field is set to Choice. |
| Instructions | Instructions for the data owner. Method of collection for the manual metric definition. |
| Approval required | Option to indicate if an approval is required for the manual metric definition. Note: When the Approval required option is enabled, the Approver type and
Approver fields are displayed. |
| Approver type | Type of the approver of the metric definition. The choices are as follows:
Note: This field appears only when the Approval required option is selected. |
| Approver | User or group that is responsible approving the metric definition. Note: This field appears only when the Approval required option is selected. |
| Metric Properties | |
| Type | Method used to determine if the score is collected manually or in an automated manner. The choices are as follows:
Select Manual. |
| Enterprise Owner Type | Type of enterprise owner responsible for the manual metric definition. The choices are as follows:
|
| Direction | Direction that you want to see the metric in. The choices are as follows:
Note: Thresholds can be set for all directions excluding Milestone. For more information on creating thresholds, see Create a threshold for a metric definition. |
| Group | Area that the metric relates to. |
| Reporting classification | Tag used to categorize the metric. |
| Due date offset | Number of days after the schedule end date when the metric data task becomes overdue. For example, if the frequency of a metric definition is monthly and if you enter 15 in this field, then the due date for metric data task will be overdue 15 days after the month ends. |
| Enterprise owner | Enterprise owner of the manual metric definition. |
| Nature | Nature of the manual metric definition. The choices are as follows:
|
| Subgroup | Subgroup that the metric relates to |
| Key metric | Option to indicate if it’s a key metric for your business. |
| Confidentiality | |
Note: This section only appears when:
|
|
| Confidential | Option to mark the record as confidential. |
| Allowed users | Users who can view the record. Note: By default, the logged-in user is added to the list of confidential users. |
| Allowed groups | Groups that can view the record. |