Core concepts

The platform organizes field resources into organizations, projects, devices, and points.

Organization: a company or team workspace
  └─ Project: a site or business use case
       └─ Device: a connected gateway, DTU, or controller
            └─ Point: a measurement, status, or control channel

Organizations and projects

An organization holds members, permissions, access tokens, plans, and shared configurations. An account can join multiple organizations. Use the selector at the top left to switch workspaces.

A project groups devices at one site. Create separate projects for different locations, customers, or sites that need separate access permissions. Projects also hold schedules, automation rules, notification settings, and screen point groups.

You can bind a device to an organization before assigning it to a project. After assignment, open it from that project's device list. See Add and manage devices.

Devices and points

A device represents a physical terminal connected to the platform. One gateway can connect several sensors or actuators, each represented by a point.

Example point	Meaning	Use
Greenhouse temperature	A sensor reading	View live values, history, and thresholds
Ventilation fan	Equipment status and control	Turn on or off, schedule, or control through a rule
Gateway status	A status channel	Track status changes

A point type defines the reading's meaning, unit, display, and some available actions. Modbus parameters define where to read the data and how to decode it. Configure both correctly; see Configure points.

Live and historical data

Live data is a point's latest value. Historical data consists of records saved over time. A live value can update even when no historical records exist for the selected range. Check the update time, device status, and query range together.

Control, automation, and alerts

• Manual control: an operator sends an action to a control point from the interface.
• Schedules: the cloud sends an action at a configured time.
• Automation rules: a point value or status triggers configured actions.
• Alerts: records of threshold violations or rule-generated conditions, with separate recovery and acknowledgment states.
• Notifications: alerts, system messages, and recommendations shown to users; configured email or SMS destinations can also receive messages.

API, forwarding, and exports

Method	Direction	Use
Open API	An external system requests data or actions	Query data, manage settings, control devices
Data forwarding	The platform pushes new data to an external system	Synchronize readings or store them in another database
Data export	The platform creates a downloadable history file	Analysis, reports, and record retention