.. _dc-concepts: Data Collection Concepts ============================ This section explains the core concepts within Orchestra's Data Collection platform. Understanding these concepts will help you effectively organize and manage your sensor data. Capability ------------ A **Capability** represents a specific type of measurement or data that a sensor can provide. Examples include TEMPERATURE, HUMIDITY, PRESSURE, or PRESENCE. Capabilities are standardized to ensure consistency and interoperability. When setting up your sensors, you'll associate them with the relevant Capabilities they measure. This allows the Data Collection platform to understand the type of data being received and present it appropriately in dashboards and reports. Component Type --------------- A **Component Type** defines a template for a specific type of sensor or device. It outlines the Capabilities that the component supports and how the data is structured. Think of it as a blueprint for similar sensors. For instance, you might have a "Temperature Sensor Type" that defines the TEMPERATURE Capability and specifies the unit of measurement (°C or °F). Component Types help streamline the process of adding multiple sensors of the same kind. Component ---------- A **Component** is an instance of a Component Type. It represents a specific physical sensor or device within your system. For example, if you have a "Temperature Sensor Type", you could have multiple Components of that type, each representing an individual temperature sensor deployed in different locations. Each Component is associated with an Element in Orchestra Communications, allowing for real-time data streaming and control. Asset ------ An **Asset** represents a logical grouping of Components that belong together. Assets are used to organize data and represent real-world objects or locations. Examples of Assets could be a "Meeting Room", a "HVAC System", or a "Production Line". By grouping Components into Assets, you can easily monitor and analyze data related to a specific area, system, or piece of equipment. Assets also have location information, adding geographical context to your data. Element ------- An **Element** in Orchestra Communications corresponds to a device or entity that can send and receive data. Each Component within Data Collection is linked to an Element. This connection enables real-time data flow from the physical sensor (Component) through Orchestra Communications (Element) to the Data Collection platform for visualization and analysis. Elements are managed within the Orchestra Communications platform and serve as the communication bridge between your hardware and Data Collection. Telemetry --------- **Telemetry** refers to the actual sensor data being transmitted and collected. This data is associated with a specific Component and includes the measured value, timestamp, and any other relevant information. The Data Collection platform stores and processes telemetry data, allowing you to visualize trends, generate reports, and gain insights from your sensor network.