The following steps allow users to configure a N3uron node in order to collect, process and contextualize data from field devices and exchange it bidirectionally with other systems.
Step 1: Setup Modules to Activate Features
N3uron functionalities are enabled using modules. In order to use a specific feature, the corresponding module must be installed during the setup process and activated in the configuration settings. For example, the WebUI is a module that is automatically activated, making it instantly accessible as soon as the installation is complete.
Since N3uron is a microservice-oriented architecture, each module runs as an independent process. Bootstrap is the core service that manages the rest of the processes.
Active functionalities or modules also require licensing. Each module requires a valid license to run in production mode. If a module doesn’t find a valid license, it will run in demo mode for two hours. In order to restart the demo period, the module must be restarted.
Click here for more information about Modules
Step 2: Configuration of Data Source Modules (Field Connections)
This step involves configuring all connections with field devices and is only necessary for source modules that require field connections, such as OPC UA client, OPC DA client, Modbus client, Siemens client, DLMS Client, IEC 102 Client, IEC 104 Client, etc.
Step 3: Setup of Data Tags
In order to create tags, all main properties must be provided:
Data type/format
Scaling and engineering units
Data Source (binding the tag to a connection configured in the previous step)
Alarms (thresholds, deadbands, severity, delays, etc.)
Historization (sampling, aggregation, storage policy)
After saving the configuration, you can monitor the tag values from the Real-Time view in the WebUI. If historization is enabled, you can also view historical data in Historical.
Click here for more information about Tags
Step 4: Edge Computing
N3uron is built to process and contextualize data at the edge before exchanging it with other systems by applying logic close to the source.
Derived Tags: Create computed tags from existing signals using low-code / no-code configuration (e.g., calculations, aggregation, statistical metrics/KPIs such as min/max/avg, normalization, redundancy handling, diagnostics).
Scripting: Run event-driven automation and workflows in the node (e.g., timers, tag changes/conditions, system events) using JavaScript.
Step 5: Configuration of Data Destination Modules
N3uron can expose data for read/write integration in several different ways:
Industrial servers: OPC UA server, Modbus server, DNP3 server, and IEC 104 server.
MQTT: Publish data to Azure, Amazon Web Service,s or standard MQTT brokers.
Sparkplug (Sparkplug B over MQTT): Publish Sparkplug payloads so Sparkplug consumers—e.g., Ignition (via Cirrus Link)—can auto-discover and consume N3uron data.
Historian and databases: Send data to Historian (MongoDB or TimescaleDB) or to a SQL database.
REST API server: Provide real-time data, node status, and historical data.
MCP Server: Standard Model Context Protocol (MCP) interface for AI agents to integrate with N3uron programmatically.
OSISoft PI: UFL connector to OSISoft PI (CSV files containing events).
File Output: XML and CSV files (events and aggregated data), delivered to destinations such as an SFTP server or an AWS S3 bucket.
Critical Infrastructures: Send data securely through a data diode in critical installations.
Click here for more information about Data Delivery Modules
Step 6: Distributed Architecture (N3uron Links)
N3uron Links enable secure, bidirectional communication between N3uron nodes, making it easy to build distributed architectures (multiple sites, edge-to-central, hub-and-spoke).
Key benefits include:
Store & Forward for reliable delivery.
Encrypted communications between nodes to protect data in transit.
Firewall-friendly connectivity (typically outbound-only from remote sites).
Bandwidth-efficient operation for constrained networks.
Time-consistent data exchange (origin timestamps preserved).
Click here for more information about N3uron Links
Step 7: Web SCADA/HMI Visualization and Control (Web Vision)
Web Vision allows you to build web-based HMI/SCADA applications for monitoring and control on top of your N3uron data model—from plant-level SCADA to Layer 2 operational SCADA and centralized control center views.
Typical use cases include:
Plant HMI/SCADA screens for operators (real-time monitoring, alarms, and control).
Layer 2 SCADA for multi-area supervision and coordination.
Control center dashboards aggregating data from multiple sites/nodes.
Click here for more information about Web Vision
.jpg)