Glossary of Key Terms
Use this glossary to understand the words used in NEQTO.ai. Terms are grouped by task, with links to the detailed instructions. Select a Term or Type header to sort within that table; select a badge to sort that table by type.
Accounts and Access · Devices and Payloads · Alert Rules and Notifications · Connectivity and Anomalies · Dashboards and Values · Tags and Device Organization · AI Assistance and Analysis · Networking and Architecture
Accounts and Access
Understand who owns resources and where a user’s permissions apply.
| Term | Type | Definition |
|---|---|---|
| Account | Platform | Your organization’s top-level environment in NEQTO.ai. An Account holds users, Roles, billing, Devices, Endpoints, and Applications. Applications select resources within that Account. Use Account for this product concept; see Administration. |
| Application | Platform | A project or team’s view of selected Account Devices and Endpoints, with its own Dashboards, Alerts, Systems, Tags, and members. Analytics and Reports work within that Application. Assigning an Endpoint includes its current and future Devices. See Applications. |
| Role-Based Access Control (RBAC) | Platform | Access granted through Roles containing permissions for specific actions. Account Roles apply at Account scope; Application Roles apply within a particular Application. A user can have both, and can hold different Roles in different Applications. |
Devices and Payloads
Follow a reading from its connection through Device identification and Attribute mapping.
| Term | Type | Definition |
|---|---|---|
| Attribute | Platform | One kind of reading reported by a Device, such as temperature, humidity, or battery level. NEQTO.ai maps readings from supported incoming payloads to Attributes. Check the resulting value and unit after the first payload is processed. |
| Auto-Parsing | AI Feature | The processing that maps supported incoming payloads to Devices and Attributes. It handles flexible JSON and supported BLE and EnOcean decoding. Inspect ingestion feedback if a payload cannot be mapped; support for one format does not mean that arbitrary proprietary bytes can be decoded. |
| Device | Platform | An identified source of readings, such as a sensor, gateway-connected instrument, or simulated sensor. A Device registers automatically after a valid payload with a stable identifier is processed through an Endpoint, provided the Account has capacity. |
| device_id | Platform |
The stable identifier used to distinguish a Device’s readings. The recommended envelope
puts it in device_id. Keep it consistent across sends; changing it can
cause NEQTO.ai to register another Device instead of continuing the same reading
history.
|
| Endpoint | Platform | The inbound connection settings that hardware or software uses to send data to NEQTO.ai. An Endpoint can receive readings from many Devices. Choose a connection type, such as MQTT with TLS, HTTPS, or WSS, when you create it; the type cannot be changed later. |
| neqtoai-std Payload | Platform |
The recommended JSON envelope for Device readings. It uses
payload_format: "neqtoai-std", timestamp,
device_id, and a data object containing readings with explicit
value and unit fields. Other supported JSON shapes are
accepted. See
Endpoints & Devices for
examples.
|
Naming note: the API calls an Attribute a data type and an Endpoint a data source. The user interface uses Attribute and Endpoint.
Alert Rules and Notifications
Define conditions, choose recipients, and track the resulting events.
| Term | Type | Definition |
|---|---|---|
| Alert History | Platform | The record of Alert events raised for your Devices. Use it to inspect the Device, event time, condition, and reading, then track work with New, In Progress, Pending, Completed, or Dismissed status. See Alerts. |
| Notification Group | Platform | A reusable set of notification recipients within an Application. It can contain users or external contacts with email or SMS destinations. Attach the group to relevant Alerts so you can maintain the recipient list in one place. |
| Threshold Alert | Platform | An Alert that tests a Device Attribute against conditions you define, such as temperature greater than 30 °C. A rule supports up to 10 conditions combined with AND, OR, or NOR, plus per-condition negation. AND requires all conditions, OR requires any condition, and NOR requires none. |
| Unlock Condition | Platform | The setting that controls when a fired Threshold Alert can trigger again. It can use elapsed time or a separate data condition. Check the unlock settings when a repeated test reading does not produce another Alert event. |
Connectivity and Anomalies
Distinguish missing reports from readings outside expected bounds.
| Term | Type | Definition |
|---|---|---|
| Anomaly Alert | Platform | An Alert that responds when a reading falls outside the applicable anomaly bounds. Statistical bounds come from the Device’s historical readings and need enough data for warm-up; physical bounds are a separate check. Enable the relevant Alert and configure its notification actions, then confirm events in Alert History. See Alerts for setup and notification behavior. |
| Anomaly Detection | AI Feature | Checking readings against supported physical bounds and statistically learned ranges. Statistical checks learn from Device history and require enough readings to complete warm-up. Review the Attribute’s warm-up state and current learned bounds in the Device’s Anomaly Detection Settings before testing statistical detection. |
| Connectivity Alert | Platform | An Alert for a Device that stops reporting for longer than its Offline Timeout. Configure it from the Device’s Connectivity Monitoring tab. Connectivity status is based on arriving data, so choose a timeout longer than the expected gap between reports. |
| Offline Timeout | Platform | The allowed gap between a Device’s reports before it is considered offline. Set it on the Device in whole minutes, with a minimum of 10. To receive a notification when the timeout is exceeded, configure Connectivity Monitoring and its notification settings. |
| Sigma Multiplier | Platform | A setting from 1 to 5, with a default of 2, that controls the width of the learned statistical anomaly range around the mean. The control accepts increments of 0.1, such as 2.5. A higher value makes the range wider and detection less sensitive; a lower value makes it narrower. It is not a guaranteed accuracy or confidence score. |
Dashboards and Values
Choose how readings and calculations appear in a Dashboard.
| Term | Type | Definition |
|---|---|---|
| Dashboard | Platform | An Application view where you arrange Widgets to display Device readings. Use charts, gauges, tables, and other Widget types to monitor the data you choose. You can open multiple Dashboards as tabs. See Dashboards. |
| Spacer | Platform | A visual divider across a Dashboard grid. Use it to separate groups of Widgets, such as current values and historical charts. A Spacer organizes the layout and does not display Device readings. |
| Statistic (Aggregation) | Platform | The calculation that combines readings in a time window into a value for a chart. The six options are Max, Min, Average, Sum, Max Absolute, and Min Absolute. Choose the calculation that matches what you want the plotted values to mean. |
| Widget | Platform | A visual component on a Dashboard. Configure it to display selected Device Attributes or calculated values. Types include charts, gauges, labels, tables, maps, progress bars, and pie or doughnut charts. See Widget Calculations for computed values. |
Tags and Device Organization
Label Devices so you can find and filter the ones you need.
| Term | Type | Definition |
|---|---|---|
| Intelligent Tagging | AI Feature | Using Tags to describe and find Devices, with manual assignment or help from Ask AI. You can request suggested Tag changes in plain language, review the affected Devices and Tags, and confirm the change. See Tags for supported workflows. |
| Tag | Platform |
A reusable key:value label, such as floor:3 or
Location:Los Angeles, assigned to Devices. Create it in Tag Management,
apply it to the relevant Devices, and use it to filter the Device list. Tags have no
parent-child hierarchy.
|
| Tag Management | Platform | The screen for creating, editing, and deleting Tags. Account-level Tags are available across Applications; Application Tags are available within their Application. Open Tag Management at the scope where you want the Tag to be maintained. |
AI Assistance and Analysis
Use these terms when working with Ask AI or reading an AI Analysis Report.
| Term | Type | Definition |
|---|---|---|
| Agentic AI | AI Feature | AI that can use tools to carry out parts of a task. In NEQTO.ai, Ask AI can retrieve information and prepare supported changes, such as a draft Alert. Your permissions and the action’s review or confirmation steps still apply. |
| AI Analysis Report | AI Feature | An AI-generated summary of one Application over a selected period. It uses aggregated Device readings and Alert activity to describe Application Overview, Sensor Health, and Alert Posture. Open Analytics to review the report and its supporting data. |
| Alert Posture | AI Feature | The part of an AI Analysis Report that summarizes Alert activity during the selected period, including which Alerts fired, how often, and their severity. It helps you decide which events to investigate. |
| Ask AI | AI Feature | The assistant for questions and supported tasks in NEQTO.ai. Ask for a sensor value, a maximum over a period, an explanation of Alert activity, or a draft Widget, Alert, Tag change, or simulation. Review and confirm proposed changes. See Ask AI for the available workflows. |
| Large Language Model (LLM) | AI Feature | A model trained to process and generate language. NEQTO.ai uses language models for features such as Ask AI and AI Analysis Reports, combining the request with the data and context available for that task. |
| LLM Token Usage | Platform | The metered AI usage associated with processing requests and generating responses, including Ask AI and AI Analysis Reports. A token is a unit of text processed by a model. Check your plan’s allowance and current usage; an exhausted allowance can prevent further AI requests. |
| Retrieval-Augmented Generation (RAG) | AI Feature | A method that retrieves relevant information before a language model answers a question. For example, the assistant can retrieve a documentation section and use it to explain how a NEQTO.ai feature works. |
| Sensor Health | AI Feature | The part of an AI Analysis Report that summarizes how an Application’s Devices and readings behaved during the selected period. Use the supporting readings and events to investigate the conditions it describes. |
Networking and Architecture
These general terms describe connected devices, communication, and shared services.
| Term | Type | Definition |
|---|---|---|
| Internet of Things (IoT) | Industry | Physical devices that collect or exchange data over a network. For example, a temperature sensor can send readings through a gateway so an application can display them or raise an Alert. |
| MQTT (Message Queuing Telemetry Transport) | Industry | A publish/subscribe messaging protocol commonly used by sensors and gateways. A sender publishes a message to a named topic on a broker, and subscribers receive messages for their topics. MQTT with TLS encrypts the connection. |
| Multi-Tenancy | Architecture | A software architecture in which multiple tenants, such as customer organizations, share a service while their access and data are separated. In NEQTO.ai, use the documented Account, Application, and Role controls to understand the scope of a user’s access. |
| Protocol | Industry | The rules that two systems use to exchange messages. MQTT, HTTP, and WebSocket are examples. The sender and Endpoint must use compatible connection settings and message formats. |
| WebSocket (WSS) | Industry | WebSocket keeps a connection open so either side can send messages without starting a new request for each one. WSS is WebSocket over TLS. It is used for continuous communication between devices, applications, and servers. |
