V2/CMS Tutorial/User Tools/Creating Content/Automation/Expression

Add Expression

This section covers the following topics:

• General Steps
• Construct Expression
• Configure Nodes

Note: Mandatory fields are marked with an ‘*’. The following steps assume that the user is already logged in to the CMS.

Steps

1. Go to the Automation tab.
2. Select the EXPRESSION tab and then ADD NEW.
3. Fill in Name of the Expression.
4. Set the Type of the Expression by choosing from the Type dropdown list.
   • Immediate (Default): Expression is checked when new values are received for any of the selected Input Measurement.
   • Polling: Expression is checked periodically regardless of whether there are new values for any of the selected Input Measurement.
5. Choose to enable or disable the expression.
6. Construct Expression.
7. Select SUBMIT (top right corner) to create the expression.

Note: When you are editing an existing expression, deleting any connection between nodes will automatically disable the expression.

Construct Expression

This section will guide you on how to construct an expression using the EXPRESSION EDITOR when adding an expression in the CMS. The goal here is to tell Senfi how to detect an event that you want to be notified of/should be responded to.

The Expression Editor is a graph-based Drag & Drop editor.

Expression Editor

Arrows coming in from the left of a node indicate its input and those going out from its right indicate its output.

Input & Output of a Node

Each Node falls into one of the following categories:

• Asset Identifier
• Input
• Data Transformation
• Logic
• Result
• Event

Data originates from Metric nodes, is transformed by Data Transformation and/or Logic nodes, and eventually consumed by Result & Event nodes.

See Node Type for more information about each Node Type.

Steps

Note: Apart from the "Result" node, all other nodes must be configured.

1. Create "Metric" nodes, one for each Input metric.
2. Attach an "Asset" node (input) to each "Metric".
3. Transform data using "Data Transformation" nodes (if necessary).
4. Create "Compare" and/or "Logic" nodes. (more information) to construct the necessary logic.
   • Logic graph should output a single Boolean (True/False) value.
   • "Compare" and "Logic" nodes can be nested.
   • More than 2 inputs can be attached to each "Logic" node.
5. Attach output of Logic graph to the "Result" node.
6. Create "Event" nodes, one for each desired Event.
7. Attach the "Result" node (input) to each "Event" node.

event_3 is triggered when result changes from False to True
event_4 is triggered when result changes from True to False

Configure Nodes

Each node contains attributes & options which you can modify. To modify the attributes of a node, simply select the node (in the working area). A window will popup to allow you to configure the node.

Metric node

Apart from the "Measurement" and "Metric" options, you can also modify the "Type" option.

Below explains the output of each "Type" option:

• Last-known value of (Default): Last known value of the metric.
• Range value of: Range of values associated with the metric.
  • This option accepts an additional "Start" and "End" (Optional) parameter
  • All values received within the "Start" and "End" timeframe will be returned.
  • The desired time unit (seconds, minutes, hours, days, values) can be changed by choosing from the dropdown list.

Note:

• "Start" > "End".
• If "End" is not specified, all values received in the past "Start" timeframe will be returned.

Aggregate Node

This section explains the output of each "Aggregate" node option.

• Sum: Sum of all input values.
• Count: Number of input values.
• Average: Average of the input values.
• Median: Median value of the input values.
• Max: Largest input value.
• Min: Smallest input value.
• Mode: Input value that appears most often.
• Range: Difference between the largest and smallest input value (max - min).
• Stddev: standard deviation
• Percentile: percentile.
  • This option accepts an additional "Percentile Value" parameter.
• Every: Outputs true if every input value fulfils the condition.
  • This option accepts an additional "Condition" parameter.
• Any: Outputs true if at least 1 input value fulfils the condition.
  • This option accepts an additional "Condition" parameter.

Function Node

This section explains the output of each "Function" node option.

• Absolute value of: Absolute value of the input.
• Round to nearest integer: Input rounded to the nearest integer.
• Round up: Input rounded up.
• Round down: Input rounded down.
• Custom transformation (Map): Input transformed based on a custom mathematical expression.
  • This option accepts an additional "mathematical operator" and "value" parameter to form a custom mathematical expression.

Event Node

This section explains how to retrieve values from expressions to be embedded in the event's input:

• Input formula must begin with "${" and end with "}".
• Content enclosed within the brackets consist of 1 to 4 words, separated by ".".
  • General: ${<node_id>.<2nd word>.<3rd word>.<4th word>}
    • node_id is located at the top left corner of a node in the working area.
      

      node_id = asset_3
  • 2nd to 4th word depend on the node type.
  • Supported node types:
    • Asset
    • Metric in single value mode
    • Aggregate
    • Function in single value mode
    • Attribute
    • Location
    • Compare
    • Logic

Embed Information of Asset Node Information

• Retrieve asset_id of asset: ${<node_id>}
  • E.g. ${asset_3}
• Retrieve value of metric: ${<node_id>.<measurement_code>.<metric_code>}
  • E.g. ${asset_3.temp_sensor.temp}
• Retrieve BBL id of asset: ${<node_id>.location.<building | block | level>}
  • E.g. ${asset_3.location.building}
• Retrieve attribute of asset: ${<node_id>.attribute.<attribute_name>[.<language_code>]}
  • If <language_code> is not specified, default language is used.
  • E.g. ${asset_3.attribute.model}
  • E.g. ${asset_3.attribute.model.ch}

Embed Information of All other Node types

• Retrieve value of the node: ${<node_id>}
  • E.g. ${compare_3}