Metric definition types

Release version: Yokohama

Updated January 30, 2025

3 minutes to read

Summarize

Summarized using AI

Summary of Metric definition types

In ServiceNow GRC: Metrics, a metrics manager creates metric definitions as template-level records to define core properties such as unit, direction, nature, precision, and category. These definitions serve as templates that collect scores, which then roll up into the metric definition for reporting and analysis. There are three primary types of metric definitions supported:

Show full answer Show less

Key Features

Automated Metric Definition: Data is collected automatically based on predefined conditions, including metric properties, collection method, and schedule. The method specifies the source table or script and filtering criteria to gather metric data efficiently.
Manual Metric Definition: Data collection is manual, requiring the designated data owner to provide metric data following instructions set by the metrics manager. A metric data task is created per the defined frequency and assigned to the data owner with email notifications. The due dates and schedules are configurable. Manual metrics support both quantitative and qualitative data and can be converted to and from automated metrics after closing any open tasks.
Calculated Metric Definition: Scores are computed by aggregating data from child metrics, which may include automated, manual, or other calculated metrics of the same frequency. The rollup property includes the formula and schedule for calculating the aggregated scores.

Applying Metric Definitions to Entities

Metric definitions can be applied across multiple organizational entities, allowing you to define a metric once and reuse it for various entities. This approach saves time and ensures consistency. For example, a metric definition for greenhouse gas emissions can be applied to multiple entities rather than defined separately for each one. Automated and manual metric definitions can be assigned to relevant entities based on the metric category and organizational policies.

A metrics manager defines the metrics by creating a metric definition. A metric definition is a template-level record. In the metric definition, you set the core properties of the metric, such as unit, direction, nature, precision, and category. The metrics collect the scores, and these scores get rolled up into the metric definition.

The GRC: Metrics application provides the following types of metric definitions:

Automated metric definition: Data is collected automatically.
Manual metric definition: Data is collected manually.
Calculated metric definition: Data is collected by aggregating scores from other child metrics.

These types of metric definitions are further explained in the following sections.

Automated metric definition

In automated metric definitions, the data is collected automatically based on the conditions defined in the metric definition, such as metric properties, method, and schedule. For the method, the metrics manager specifies the source table or the script that is used for collecting the metric data and the filtering criteria to filter the metric data. See Create an automated metric definition for more information.

Manual metric definition

In manual metric definitions, the mode of data collection is manual. The data owner for a particular metric provides the metric data by going through the instructions. As the metrics manager, you have to define the metric properties, method, and schedule for the metric definition. In the method, specify the instructions for the metric definition as the metrics manager. Also, specify the data collection details such as data owner type, data owner, and approval details.

In a manual metric definition, a metric data task is generated depending upon the frequency defined in the metric definition. As a metrics manager, you can assign the task to a data owner who provides the data for the task. See Create a manual metric definition for more information. When a metric data task is created, a system generated email notification is sent to the task owner. As a metric data owner, you can provide the data for multiple metrics using the Metrics tasks module (). For more information, refer to Provide data for multiple metrics.

Each metric data task has a due date defined in the manual metric definition form. By default, the due date follows the schedule of 8-5. However, a risk administrator can also modify the schedule. For more information, refer to Create a new schedule. If the risk administrator wants to overwrite the schedule, then the risk administrator can modify the sn_grc_metric.metric_data_task_schedule property.

Both quantitative and qualitative category of metrics can be created using the manual metric definition.

It is possible to convert a manual metric definition to an automated metric definition and an automated metric definition to a manual metric definition. In the event that a manual metric definition has open tasks, it is necessary to first close them prior to converting the manual metric definition.

Calculated metric definition

A calculated metric definition calculates the scores from its children. It can include the automated and manual metric definitions, metrics (quantitative), and other calculated metric definitions of identical frequency. As the metrics manager, you have to specify how you want to calculate the metric definitions score and how frequently you want to calculate them.

The calculated metric definition rolls up the scores from its children. The rollup property defined in the calculated metric definition consists of a rollup formula and schedule for the rollup frequency. A calculated metric definition can include those automated and manual metric definitions, and metrics as its children which are of the same frequency as that of the parent calculated metric definition. See Create a calculated metric definition for more information.

Applying the metric definition to the entities

You can apply the metric definitions to the entities in your organization. Instead of defining the metric for each entity, you can define the metric definition once and then apply that metric definition to your entities.

For example, assume you want to measure the greenhouse gas emissions for the entities in your organization. Defining the metric for each entity is a time-consuming process. By creating a metric definition, you can define the metric once and then apply that metric definition to your entities.

The following illustration shows how you can apply the metric data definition to an entity. If you have an automated metric definition for the purchased goods metric category, the metric can be applied to the Products entity and IT entity in your organization. If you have a manual metric definition such as Employee Travel, the metric can be applied to the Enterprise entity in your organization as the travel policy applies to everyone across the enterprise.