Setting Up Custom Metrics

  1. In the Business Intelligence menu, click Custom Metrics, or in the Environmental menu, click Measure.

    BUS_custom_metric_profiles_list.png
  2. Users can view all measures that are not prohibited (see Setting Up Roles), but only an administrator can add or edit a metric.
    This list of measures includes the standard Cority Measures that are read-only and cannot be edited nor assigned to a location or user. These measures  can only be used in equations within custom metrics and the Data Cube. When you click on one of these you will see the metric information in a read-only state.
    A measure cannot be deleted if it is part of a campaign (see Grouping Metrics into a Campaign).

    If you want to create a custom measure linked to a Report Writer subquery, you must use a custom layout that includes the Subquery field. A custom measure linked to a subquery cannot contain an equation, be a target, or have locations/assignees records, and no findings or actions can be created against the metrics in the Completion/History tab.

  3. Click a link to edit an existing measure, or click New.

    BUS_custom_metric_profiles_details.png
  4. To create a metric that is very similar to an existing one, select the metric and choose Actions»Clone Custom Metric. A copy is created with “Cn” appended to the name. Open and edit the copied metric as required.

  5. On the Profile tab, enter the following information:

  6. When a custom metric has a related target, Cority ensures that their recurrence frequencies cannot be mismatched.

    You can define a metrics tree to organize and aggregate metrics in a parent-child relationship. The Equation field of the top/parent metric will reflect its children. See Creating a Metrics Tree below.

    If you select this check box, you can override the default notification settings if necessary: select Override System-wide MAEN Settings for this metric, and change the settings in the Automatic Email Notifications section as required. The settings in this section, whether default or overwritten, will apply to each metric assignment associated with the record.

  7. On the Locations and Assignees tab, click New:

  8. Only one assignee is permitted per metric/location for a particular time period.
    If added to a custom layout, you can assign the metric to an asset or a group of assets (if defined in the EquipmentGroup look-up table).
    If you attempt to create more than one assignment with the same asset, GDDLOFB and time period, you will receive an error message.
    If you create more than one assignment with the same GDDLOFB and time period but with unique assets, you will be advised that the assignment may result in duplicate aggregations for this tree combination if reported data is not filtered or displayed by asset.

  9. The Completion/ History tab shows all metric entries (regular users will only see metrics to which they have been assigned).

  10. To quickly update multiple metrics, select the check boxes beside them and click Edit. The Value field becomes editable directly in the list.

  11. The Findings and Actions tab displays all findings and actions relating to this metric. For information about recording a finding and its actions, see Recording a New Finding.

A metric entry cannot be approved by the administrator until all actions are also closed.

Approved metric entries are locked from further edits and are available for use in the Data Cube (see Using the Data Cube).

How Are Due Dates Calculated?

Each metric entry’s due date is calculated based on the metric’s Start Date and Recurrence Frequency. For example if the metric’s start date is March 1:

Recurrence

Metric Entry 1
Due Date

Metric Entry 2
Start Date

Metric Entry 2
Due Date

none

--

--

--

weekly

March 7

March 8

March 14

monthly

March 31

April 1

April 30

quarterly

May 31

June 1

August 31

If a user was assigned after a due date has passed, the next due date applies. In the monthly example above, the first due date is March 31. A user assigned on April 15 will only have one due metric entry (due April 30) -- any metric entries of this metric before April 15 will not be deemed due/overdue.

Exceptions:

Creating a Metrics Tree

Use the Metrics Tree to create, organize, view, and aggregate/roll-up metrics in parent-child relationships using a tree structure.

BUS_metric_tree.gif

Metrics are organized in Categories at the highest level in the tree (below the Root). Each category can be rolled up independently. You can create as many categories as required. Nodes are added below categories in the following possible levels:

In the example above, there are two categories: Greenhouse Gases Emissions and Water. Below Water are two Metrics (Water Consumption and Water Wit). Water Wit includes a SubMetric (Well Water), which contains an Input Metric (Well Water City) and an Equation Metric (Water Plant from Wells).

Creating a metrics tree:

  1. In the Business Intelligence menu, click Metrics Tree.

  2. To add a category, hover over the Root and click +. Enter a Code and Description.

  3. Add nodes below categories to create the Metrics (and SubMetrics, if required) levels. Hover over a level and click + to add a node below it.

  4. Leaf levels are first created as a node, then defined as a measure:

All metrics in the tree will be displayed in the Custom Metrics list. The Equation field of the top/parent metric will reflect its children. The metrics tree and aggregated metrics are available for use in the Data Cube.

Managing nodes: