Local Tags vs Remote Tags
The licensing of N3uron modules is categorized into two types: Local Tags (Local Licenses) and Remote Tags (Remote Licenses).
Local Licenses
In a distributed architecture where each node operates independently, we utilize Local Licenses.
Definition: A N3uron module is considered Local when it processes data originating from its own host node (e.g., through physical drivers like Modbus Client, OPC UA Client or Siemens Client).
Use Case: If an Edge node collects data from a local PLC and sends it directly to a third-party MQTT Broker or a SCADA system, the OPC UA Client, Modbus Client, MQTT Client or OPC UA Server modules in that node are licensed as Local.
Value: This model is ideal for standalone sites where data processing and external communication must be handled on-site without dependency on a central hub.
Remote Licenses
When employing a Centralized Architecture (using N3uron Links), the central node often requires Remote Licenses.
Definition: A module is classified as Remote when it acts upon data received from other N3uron nodes via Links.
The "Data Origin" Rule: If the Central Node uses a module (e.g., Historian, MQTT Client, Derived Tags) to process, store or forward data that was collected by Edge nodes, that module must be licensed as Remote.
Real-time visualization of local and remote tags on the N3uron DMZ22 node. Remote data is pulled from the REM22 node via Links.