Skysens Docs
  • Getting Started
  • Agile Predictive Monitoring
    • Concept
    • Hardware
    • Wireless Networks
    • Platform
    • AI
  • Main Menu and Overview
    • Overview Usecases
    • Widget Types
      • Value
      • Gauge
      • Image
      • Notification
      • Map
      • Text
      • Intensity Chart (Heatmap)
      • Table
      • Line Chart
      • Bar Chart (Histogram)
      • Line - Bar Chart
      • Pie Chart
      • Sankey Diagram
    • Best Practices
  • Notifications
    • Notification Menu
    • Notification Types
  • Asset
    • Asset Types
    • Asset Listing
    • Asset Details
    • Application
  • Rules Menu
    • Rules Edit and Frequency
      • Condition
      • Action
  • Sources
    • Connection Types
      • Modbus TCP
      • MQTT
      • HTTP
    • Device Catalog (LoRaWAN)
    • Network Management (LoRaWAN)
      • Gateway
      • Device
    • Virtual Sensor
      • Value
      • Form
      • Simulation
  • Settings
    • Account Settings
    • Location Management (Settings)
    • User/Role Management (Settings)
  • Reports
    • Advanced Reporting
  • Logs
Powered by GitBook
On this page
  1. Rules Menu
  2. Rules Edit and Frequency

Condition

How things will be handled

PreviousRules Edit and FrequencyNextAction

Last updated 1 month ago

Condition and action sides of the rule edit menu starts with condition checker cards which are basically programmable micro services for logic design purposes:

Offline Status Checker:

This is a checkbox for asset offline checker service. Offline checker service is a micro-service which automatically checks physical assets connection offline status in predetermined time. (As default, time of the incoming data interval multiplied by 3)

When If its checked, all drop-downs and switches other than asset selection will be inactive.

After this checked users can design action side and decide what to do if device becomes offline such as sending text message or triggering another field or sending webhook to another system.

Asset:

Any asset on the users list can be selected here wheter its a digital or physical assets.

Field:

Fields related to selected asset can be selected here.All type of data will be listed here as default without any filtering for booleanor integer because of that user needs to select non-string field to make logic test and data manipulation relevant.

Data Time:

Since multiple condition checks can be created, user needs to select data time from this drop-down additionally. Similar to rule trigger data frequency selection, user can select "current" mode which triggers with incoming data without any time delay.

In addition to current mode user can select time options from the list or can create its on timing.

Value Type:

Value type has 2 option, those are "Single" and "Multiple" data types and it directly works with "Data Time" and "Data Manipulation" selection.

If "Single" is selected, condition checker takes first single data point before selected "Data Time" time and process it.If single is selected "Data Manipulation" option will be inactive.

If "Multiple" is selected, condition checker will require "Data Manipulation" input and process entire data in "Data Time" selected period according to selected data manipulation algorithm.

"Current" option wont be available if "Multiple" is selected.

Data Manipulate:

It is only active if "Value Type" is selected as "Multiple".

It is basically an algorithm service similar to widgets configuration menu and its being used to do sub-calculations for complex analytics.

-Average: It takes arithmetic average of all data in time period selected in "Data Time".

-Sum: It takes total sum of all data in time period selected in "Data Time".

-Minimum: It takes mathematically minimum valued data of all data in time period selected in "Data Time".

-Maximum: It takes numerical maximum valued data of all data in time period selected in "Data Time".

-Multiply: It multiplies all data with each other in time period selected in "Data Time".

-Division:It divides all data with each other in time period selected in "Data Time".

-Difference(Range):It calculates absolute difference between maximum and minimum numerically valued data points in the data cluster in time period selected in "Data Time".Useful to track performance or anomalies.

-Consumption:It calculates absolute numerical difference between last and first data point in time period selected in "Data Time".Useful to monitor consumption of resources or metering.

Logic Test:

User can create mathematical logic tests in condition cards as an option to create more complex rule designs.

After selecting operator user needs to input value. Condition card will work as a sub logic controller and will jump to next condition card or action side if logic turns out to be true

Adding Another Condition Card

Users can add additional condition card with And/Or logic gates and crate chain conditions easily.

Details of Condition Cards
Data Manipulation Options
Logic Tests
Using Two Condition Cards With "And" Logic