Connect to Applications
Once your Tags are modeled and your data is ready, the next step is to deliver it to your business systems. In EasyEdge, this is done by creating an Application, which defines how and where the data will be sent—whether to a cloud platform, database, or on-prem system.
Applications use Application Connectors, which are protocol-specific connector engines that handle communication with external systems such as AWS, Azure, Snowflake, InfluxDB, MQTT brokers, and more.
In this example, we'll demonstrate how to connect your project to an external Application using the MQTT Application Connector.
VIDEO TO BE ADDED
Step-by-Step Example: Connect to an MQTT Application
1. Open the System Overview
In EasyEdge Studio, go to your System and click Add Application. This opens the Application configuration wizard.
2. Choose the Application Connector
From the list of available options, select the Application Connector that matches your destination platform.
3. Name the Application and choose the Default Binding Method
After choosing the Application Connector:
Name your Application for easier identification.
Choose the Default Binding Method:
Collect Only – Data flows from Edge to the Application (read-only).
Control Only – The Application can write control signals to the Edge (write-only).
Collect and Control – Bi-directional data flow (read/write).
4. Configure the Application Connection
This step allows you to define how EasyEdge will communicate with the external Application. Each Application Connector will present its own specific configuration options. In this example, we’re configuring an MQTT Application Connector.
Connection
Set the IP address and port of the MQTT Broker you want to connect to. Optional fields like Username, Password, and Client ID can be configured as needed. The QoS (Quality of Service) level can also be set depending on your data delivery needs.
Security
Use this settings to enable encrypted communication with the broker. This helps ensure the security of the data sent from the edge.
Payload and Topic
Customize how messages are structured and routed. This includes setting the topic template, formatting the payload, and choosing data formatting options like string escaping and delimiters. You can also define how data is aggregated and sent.
Data Flow
Configure how frequently data should be sent. The Maximum Idle Time and Maximum Wait Time control the timing of message dispatch. Enabling Continuous Mode ensures that every event is transmitted individually, which is especially useful for high-precision use cases.
5. Configure the Application Namespace
In this step, you define the Namespace structure that will organize and contextualize the data delivered to the Application.
You can:
Edit the Namespace prefix, which acts as a base path for all Data Streams in this Application.
Create Namespace Folders by importing existing Tags Folders or by building your own structure manually.
Add individual Data Streams within each Folder, using Tags available in the System.
This flexible Namespace structure allows you to tailor the way data is delivered to match the specific format and hierarchy expected by each Application.
5.1 Edit Namespace Prefix
The Namespace Prefix defines the starting point of your Application’s data structure. It acts as the root path for all Data Streams delivered to the Application.
You can also configure:
Default level separator: Used between levels of the Namespace structure (e.g.,
/forEnterprise/Site/System/...)Last level separator: Used to separate the Data Stream name from the property (e.g.,
/DataStreamName/Value)
This step gives you flexibility to align the output Namespace with the requirements of the destination Application—such as compliance with ISA-95, MQTT topic formatting, or custom naming conventions.
5.2 Create Folders to build Your Namespace structure
Folders allow you to organize your Namespace tree before mapping individual Data Streams.
You can choose one of two options when adding a new folder:
✅ From Tags Folder: Automatically creates a Namespace folder and generates Data Streams based on the Tags inside that folder. Useful when reusing structures already defined on the Edge side.
➕ Empty Folder: Creates a blank Namespace folder. Data Streams can then be added manually, one by one, offering full control over the structure and mapping.
This step allows you to build a clean, hierarchical Namespace that reflects your project’s organization—from enterprise-level views down to individual assets or measurements.
5.3 Create Data Streams
Data Streams define what data is sent to your Application through the Namespace structure.
You can create a Data Stream in two ways:
🔗 From a Tag: Creates a direct reference to a specific Tag from any EdgeNode in the System.
✏️ From Scratch: Allows you to define a custom Expression using one or more Tags to calculate or transform the data before it is sent.
For both types of Data Streams, you can:
Apply Transformations to format or convert the data
Add Filters to include only the values that match specific criteria
Each Data Stream becomes part of the Application Namespace and is structured under the appropriate folder for clarity and consistency.
5.4 Edit Data Stream
Just like Asset Tags, each Data Stream can be fully edited and configured to meet your Application’s requirements.
Clicking on a Data Stream opens the Edit Data Stream overlay where you can:
Rename the Data Stream
Modify the Data Type (conversion handled automatically by EasyEdge at runtime)
Assign or update the Write Expressions (used to send values to the Application)
Assign or update the Usage Expressions (used for control or monitoring scenarios)
Add calculations, scaling, or logic to adapt raw data to Application needs
You can bind a Data Stream to:
A single Tag
Multiple Tags using Expressions (e.g., averages, conditionals, aggregations)
EasyEdge ensures Data Integrity even when converting between different data types, enabling flexible yet robust configurations for diverse industrial use cases.
5.5 Configure Filter Sequences
Filter Sequences allow you to apply edge-side data conditioning before values are sent to Applications.
In this step, you can:
Create and manage reusable Filter Sequences from your Account (shared across all Systems)
Select a Filter Sequence per Data Stream during Namespace configuration
Chain multiple filters (e.g., anti-aliasing, averaging, range filters) to fine-tune the data output
Each filter includes customizable parameters. For example, an Average On Period filter can be set to output the average of incoming values over a 15-minute window.
This enables lightweight data processing and noise reduction directly at the Edge, reducing bandwidth and improving data quality for the Application.
6. Validate and Finish
You're almost done. The final step is to review your configuration and confirm the Application setup.
Summary Includes:
Application Connector The Application Connector instance selected for this project (e.g., MQTT, REST, Snowflake)
Application Details
Custom name defined for this Application (e.g.,
MyMQTT)Binding method (e.g.,
collect only,publish, etc.)
Connection Settings The specific configuration fields required by the Application Connector
Once everything looks correct, click Finish to save and activate the Application.
The Application is now ready to:
Start receiving data from Data Streams in your Namespace
Run according to your configured filters and transformations
Send or collect data from connected systems, platforms, or services
Last updated