Connect UNS to external data services.

Reference → Modules → UNS → UI → Asset | Tags | UserTypes | Enumerations | Services | Monitor

UNS TagProvider Services (Reference) enable direct interaction with variables in remote systems without creating local tags. TagProvider Services provide:

  • Dynamic external data access
  • Tagless connections to remote systems
  • Automatic data model discovery
  • Real-time structure updates
  • Multi-protocol support
  • Historian integration capabilities

TagProviders allow consuming external data models directly, ideal for IoT systems and dynamic environments where device configurations change frequently.

Find a TagProvider Service

TagProviders vs Devices

AspectDevicesTagProviders
Data StructureStatic, predefinedDynamic, discovered
Tag CreationRequired locallyNot required
MetadataFull controlLimited control
SecurityGranular per tagConnection level
Use CaseSCADA/HMI systemsIoT/Monitoring
ValidationStrict (FDA)Flexible
ConfigurationDesign-timeRuntime discovery

Supported TagProviders

Communication Protocols

  • MQTT - Standard and SparkPlugB
  • OPC UA - Industrial standard
  • ControlLogix - Rockwell PLCs
  • Codesys - PLC Handler
  • TwinCAT - Beckhoff systems

Application Integration

  • Server to Server - Solution interconnection
  • LineMonitor - Production monitoring

Historian Systems

  • Canary Labs - Enterprise historian
  • InfluxDB - Time-series database
  • GE Proficy - Industrial historian
  • SQL Database - Generic SQL sources


Historian TagProviders provide two additional features:

  1. Automatic historian querying for TrendCharts using Asset() syntax
  2. Can be used as Storage Locations for archiving time-series data


Configuration

Creating Connections

  1. Navigate to Unified Namespace → TagProvider Connections
  2. Click New Item button
  3. Select protocol from list
  4. Configure connection parameters
  5. Test connection
  6. Asset folder auto-created

Common Parameters

ParameterDescriptionRequired
NameConnection identifierYes
ProtocolCommunication typeYes
PrimaryStationMain endpointYes
BackupStationRedundant endpointNo
AccessRead/Write/ReadWriteYes
TimeoutResponse timeoutYes
DescriptionDocumentationNo

All Properties


PropertyDescriptionType
ProtocolCommunication protocolSelection
ProtocolOptionsProtocol-specific settingsString
PrimaryStationMain connection endpointString
BackupStationBackup endpointString
SettingsConfiguration parametersString
TimeoutResponse timeout (ms)Integer
IsHistorianHistorian capabilityBoolean
AccessRead/Write permissionsEnum
ServerIPRemote server addressString



Protocol-Specific Settings

Protocol-Specific Settings

OPC UA


SettingDescription
Server URLOPC UA endpoint (e.g., opc.tcp://server:4840)
Security PolicyNone, Basic128Rsa15, Basic256, Basic256Sha256
Security ModeNone, Sign, SignAndEncrypt
AuthenticationAnonymous, Username/Password, Certificate

MQTT


SettingDescription
BrokerMQTT broker address
PortBroker port (default: 1883)
Topic StructureTopic pattern for subscription
QoSQuality of Service level (0, 1, 2)
Client IDUnique client identifier

ControlLogix


SettingDescription
IP AddressPLC IP address
SlotCPU slot number
PathOptional routing path

Using TagProviders

SQL Database

SettingDescription
Connection StringDatabase connection string
QuerySQL query for data retrieval
Refresh RatePoll interval (ms)

Data Type Handling

WPF Displays (.NET Framework 4.8)

Dynamic handling supported — types are automatically resolved.

HTML5/Portable (NetStandard 2.0)

Explicit conversion required:

MethodReturns
TK.ToInt(value)Integer
TK.ToDouble(value)Double
TK.ToString(value)String
TK.ToDigital(value)Boolean
TK.ToDateTime(value)DateTime


Asset() Syntax Reference

Basic Syntax

Asset("/TagProviderName/Path/To/Tag")

ControlLogix Syntax

Asset("/MyPLC/DataType:TagName")
Asset("/MyPLC/DINT:MyTag")
Asset("/MyPLC/DINT:MyArray[0]")
Asset("/MyPLC/REAL:Temperature")

Supported Operations


OperationSyntax
Readvalue = Asset("/path")
WriteAsset("/path") = value
SubscribeAutomatic in displays


Historian Integration

As Data Source

When a TagProvider has IsHistorian = true:

  • TrendCharts automatically query historical data
  • Use Asset() syntax for historian path
  • Time range passed automatically from chart

As Storage Location

Historian TagProviders can be configured as storage targets:

  • Configure in Historian → Storage Locations
  • Select TagProvider as destination
  • Tags are logged to external historian

Supported Historian Protocols

ProtocolReadWrite
Canary Labs??
InfluxDB??
GE Proficy??
SQL Database??

Access Modes

ModeDescription
ReadRead-only access to external data
WriteWrite-only access (rare)
ReadWriteFull bidirectional access

See Also

  • TagProvider Services — Concept overview
  • TagProvider Services How-to — Step-by-step procedures
  • TagProvider Services Technology — Architecture deep dive
  • Connectors Library — All available protocols


In this section...