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

Rules Menu

Main logic workers of the platform

PreviousApplicationNextRules Edit and Frequency

Last updated 1 month ago

Rules are the main logic engine for manipulating data and creating new assets, grouping, data flows and notifications.

For data manipulation asset based micro services and AI models can be facilitated in addition to rule engine.However, rules engine is the main data manipulation service with its extensive logic design capabilities.

With easy to use and/or gates, hierarchical modelling, no code integrations it covers various tasks such as grouping, notification creation, asset data calculation and manipulation.

Users can design rule hierarchies in order to create logic flows from first to last action.

Rule list can be design according to required sequence.

All rule elements aligned to the left starts at same time. Within each sequence, sub-rules are organized top-to-bottom, representing a hierarchical order of application

With this flexibility users can design sequential logical systems which are designed to handle complex tasks.

Rules Menu
Rule list details
Rule trigger sequence (Hierarchy) T0 First T0+4 Last