{'Using GRC': 'Metrics to provide data'} › {'GRC': 'Metrics'} › Operational Sustainability Management \(formerly Environmental › Social › and Governance\)

Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Update a manually created metric

Update a manually created manual metric to add goals, metric data, and targets. Associate citations to the metric.

Before you begin

Role required: sn_esg.metric_manager

Procedure

Navigate to All > Operational Sustainability Management > Operational Sustainability Workspace > Metrics.
Select a manually created metric from the list.
On the form, update the fields as necessary.

Field	Description
Tabs
Name	Name for the metric. For example, `Number of incidents- ACME Asia`.
Description	Brief description of the metric.
Metric definition	Metric definition associated with the metric.
Entity	Entity associated with the metric.
Enterprise Owner Type	Enterprise owner type who is responsible for the metric. This field is automatically set to display the enterprise owner type.
Type	Type of metric definition. This field is automatically set.
Active	Option to mark the metric definition as active. This field is automatically set.
Key metric	Option to mark the metric definition as a key metric. This field is automatically set.
Enterprise owner	Enterprise owner of the metric definition. This field is automatically set.
Metric Properties
Direction	Direction of the metric definition. This field is automatically set.
Precision	Precision for the metric definition. This field is automatically set.
Unit	Unit for the metric definition. This field is automatically set.
Nature	Nature of the metric definition. This field is automatically set.
Method
Instructions	Instructions for the data owner. Method of collection for the manual metric definition. This field is automatically set.
Schedule
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	Collection frequency with which the metric is executed. Indicates how often the metric definition should collect the data. The choices are as follows:- Daily - Weekly - Monthly - Quarterly - Semi-annually - Annually This field is automatically set.
First run date	Date for the first run time. This field is automatically set.
Next run date	Date for the next run time.
Period date	Date used to specify the start and end dates for the data collection period.
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. This field is automatically set.
Data Collection Details
Data owner type	Data owner type such as User.
Data owner	Name of the user as the data owner.
Approval
Approval required	Option to be enabled if an approval is requested for the metric.
Metric data tasks tab	Information about the metric data task, such as name, number, assigned to, priority, and state
Classification
Group	Area that the metric relates to. This field is automatically set.
Subgroup	Tag used to categorise the metric. This field is automatically set.
Reporting classification	Tag under which the metric definition and metric is categorized. For example, GRI, SASB, or Steering Committee Review.
Related lists
Goals	Details of the goals associated with the metric, such as name, state, category, start date, end date, owner, and status. To add a new goal, select Add.
Metric data	Details of the metric data such as start date, end date, value, collector metric data, collection frequency, and type. Start date: The start date is the date that the data collection begins. End date: The end date is the end of the period date that determines the interval for which the score is calculated. The end date depends on the frequency of the metric definition. The end date is used for tracking the scores. Every score is time-dependent and it has a reference to the interval end date. Collection frequency: The options in the collection frequency field are: Daily: Score that gets created for each day. Weekly: Score that gets created by the end of the week date (Sunday). Monday is the start of the week and Sunday is the end of the week. Monthly: Score that gets created by the end of the month. Quarterly: Score that gets created by the end of the quarter. For example, Q1 ends on March 31, Q2 ends on June 30, Q3 ends on September 30, and Q4 ends on December 31 in a year. Semi-annually: Score that is created by the end of the 6-month period. The end date for the semester is June 30 and December 31 in a year. Annually: Score that gets created by the end of the year. The end date for the year is December 31.
Targets	Details of the targets associated with the metric, such as name, state, owner, start date, end date, type, and measure. To add a new target, select Add.
Citations	Details of the citations, such as reference, name, authority document, description, and compliance score percentage (%). To add a new citation, select Add.
Thresholds	Details of the thresholds associated with the metric, such as type, related metric, valid dates, threshold color, and target value. To add a new citation, select Add.

To save the metric, select Save.
To delete the metric definition, select Delete.
To execute the metric, select Execute.

A metric data score is created if it doesn’t exist for the current interval. Re-executing a metric or a metric definition for the current interval only updates the score.
To visually explore the 360° relationship view of the metric definition, select 360° view.

Parent Topic:Using GRC: Metrics to provide data