Device and device profile

Device and device profile

A device represents physical equipment that is monitored, generates data, or sends data to the SolarTools platform.

Meters, energy analyzers, sensors, inverters, PLC systems, and similar field equipment can be defined as devices within the platform.

The device structure makes field equipment visible, manageable, and traceable within the platform.

What is a device profile?

A device profile is a template structure used to centrally manage the shared configurations, data models, and platform behaviors of devices with similar characteristics.

A platform may contain hundreds of devices of the same type. Instead of defining connection settings, telemetry structures, alarms, and data models individually for each device, a standardized and sustainable management structure can be created through device profiles.

With this architecture, devices connected to the same profile can operate under shared rules, maintain consistent data structures, and allow new devices to be integrated into the system much faster.

  • Shared structure management → Allows similar device types to be centrally managed with common settings, data structures, and platform behaviors.
  • Telemetry definitions → Helps organize expected measurements, tag structures, and telemetry data points in a standardized way.
  • Alarm and rule structures → Enables shared alarm scenarios, threshold values, and automation rules for specific device groups.
  • Connection configurations → Manages how devices connect to the platform and how communication is established through different protocols.
  • Bulk device management → Simplifies centralized monitoring, updating, and management of devices linked to the same profile.
  • Standardized data model → Ensures that data from different devices is processed within a unified and consistent platform structure.
Device profile architecture significantly simplifies management processes, especially in large-scale energy, automation, and IoT systems containing many similar devices.

Device profile architecture

The device profile architecture is a centralized management model that organizes similar devices under a shared structure within the platform.

A device profile is created first. This profile contains shared properties such as telemetry structures, alarm rules, connection settings, and device behavior configurations.

Devices with similar characteristics are then linked to the same profile. This eliminates the need to configure each device individually and creates a standardized management structure.

For example, energy analyzers of the same model can be connected to a single device profile. All devices associated with that profile operate with the same data model, alarm structures, and communication settings.

  1. A device profile is created
  2. Telemetry structures, alarm rules, and connection settings are defined within the profile
  3. Similar devices are connected to the related profile
  4. The platform processes incoming device data through a unified data model
  5. Dashboards, alarms, and analytics systems operate on this standardized structure
Template

Device Profile

Central template that carries shared configuration for similar devices.

Telemetry StructureAlarm RulesConnection SettingsData Model
Device #1

↳ inherits profile

Device #2

↳ inherits profile

Device #3

↳ inherits profile

SolarTools Platform

Processes data through the unified data model; dashboards, alarms, and reports run on this standard structure.

Figure — Device profile architecture: from shared template to devices and onto the platform
This architecture makes device structures within the platform more organized, scalable, and centrally manageable.

Role within the platform

Devices and device profiles play a core role in the data organization layer of the SolarTools platform. Devices represent field data, while profiles define how those devices behave.

  1. Device generates data from the field
  2. Gateway or connector transfers this data to the platform
  3. The platform associates the device with its device profile
  4. Tags and telemetry structures are organized through the device
  5. Dashboards, alarms, and reports use this data

Use Cases

Device and device profile structures are used to provide centralized management and standardized data organization in energy, automation, and IoT systems containing large numbers of similar devices.

Energy analyzers → Energy analyzers of the same model can be connected to a single device profile and centrally managed with shared telemetry, alarm, and connection settings.

📡

Sensor groups → Temperature, humidity, pressure, and environmental sensors can be organized through a shared data model and monitored consistently across the platform.

🏭

Industrial automation devices → PLC, RTU, and field control devices can be managed through shared device profiles, helping maintain standardized data structures and platform behaviors.

🔌

Bulk device management → Simplifies centralized monitoring, updating, and management processes for devices connected to the same profile.

📊

Standard telemetry organization → Ensures telemetry data from different devices is processed consistently using shared tag structures and unified data models across the platform.


Why use device profiles?

In large systems, configuring each device separately is time-consuming and error-prone. Device profiles standardize this process and provide more controlled management.

  • Reduces repetitive settings for similar devices
  • Centralizes device management
  • Keeps telemetry and tag structures consistent
  • Standardizes alarm and automation rules
  • Speeds up the new device onboarding process

Next step

After understanding devices and device profiles, continue with the tag and telemetry model to explore how device data is organized within the platform.

Device and device profile | SolarTools