Telemetry and remote operation of assets: architecture and integration

Component architecture

Things AITHA organizes device telemetry, provides web, mobile, and remote APIs, and integrates hardware through MQTT, HTTP, CoAP, or REST API.

It integrates with other AITHANEX products through a common foundation of permissions, history, and traceability.

Component	Function
Ingestion engine	Receives device data through multiple protocols and normalizes it.
Asset manager	Organizes devices by customer, installation, hierarchy, and customizable profile.
Rules engine	Evaluates conditions, thresholds, and events to trigger automatic actions.
Alarm system	Detects, classifies, propagates, and records operational events with traceability.
Remote control	Sends commands to compatible devices and records the result.
OTA and configuration	Deploys firmware and parameters when supported by the device.
History	Stores telemetry, events, states, commands, and configuration changes.
Operational interfaces	Web application, maps, mobile app, and APIs.

Protocol / Mechanism	Use
MQTT	Real-time telemetry from devices and gateways.
HTTP	Request-based ingestion and integration endpoints.
CoAP	Resource-constrained devices.
WebSocket	Real-time updates to the web interface.
REST APIs	Integration with external systems, ERP, or third-party platforms.

Third-party devices integrate through a gateway, API, or compatible protocol. Support depends on the hardware and configuration.

Entity	Description
Asset	Any monitored element, device, control point, or infrastructure.
Telemetry	Numerical variables, states, and metrics sent by the device.
Event	State change, exceeded condition, or loss of communication.
Alarm	Classified event with a criticality level, tracking status, and history.
Command	Action sent to the device with a recorded result.
Installation	Grouping of assets by location or project.
Customer / Tenant	Logical segmentation separating data, permissions, and configuration.

Each asset supports custom attributes and profiles according to the equipment or installation type.

Element	Scope
Condition	Threshold, state change, loss of communication, received event, or combined rule.
Level	Informational, warning, critical, or another level defined by the deployment.
Context	Affected asset, location, customer, installation, group, or equipment type.
Action	Notification, escalation, or incident record.
Status	Open, acknowledged, under review, resolved, or closed.
History	Record of occurrence, changes, responsible parties, actions, and final result.

Capabilities:

Receive telemetry from AITHANEX system devices and third-party hardware with a compatible protocol.
Execute remote commands on devices when supported by firmware and permissions.
Expose data and actions to AITHANEX AI, ERP, internal systems, or external APIs.
Operate in multi-tenant deployments with logical separation by customer and/or installation.

Limitations:

Remote control requires the device to support the corresponding command protocol.
OTA updates depend on the capabilities of the target device firmware.
Integration with external systems requires APIs, credentials, and exchange rules defined by project.
AITHANEX AI integration capabilities are optional and enabled through configuration.

Area	Scope
Authentication	User and system access through credentials managed by the platform.
Permissions	Role-based control for reading, operation, configuration, and administration.
Segmentation	Logical isolation of data and operations by customer and installation.
Communication	Encryption according to deployment configuration and enabled protocols.
Traceability	Record of actions, commands, configuration changes, and access by user.

Things AITHA supports logical separation by customer and/or installation.

Each tenant has separate assets, data, alarms, permissions, and configuration. Cross-tenant access requires explicit system administration.

Area	Requirement
Devices	Ability to publish data or integrate through a gateway, API, or compatible protocol.
External systems	APIs, credentials, and exchange rules defined by project.
Users	Roles, permissions, and segmentation configured for each deployment.
Data	Minimum asset, event, state, and metric model for traceable operations.

Product	Technical relationship
AITHANEX AI	Consumes telemetry, alarms, and states for operational assistance and controlled actions.
AITHA Inbox	Can receive Things events or states to provide context for support.
AITHANEX Platform	Optional operations layer with unified permissions, history, auditing, and traceability.
AITHA IoT Core	Publishes telemetry and events to Things.
AURA X36	Connects distributed signals, sensors, and actuators to the platform.