Page History

Expose the Unified Namespace to external clients, AI systems, and other FrameworX solutions.

Modules → Data Foundation → Data Services (Concept) | How-to | Reference

FrameworX as Client vs Server

TagProvider Services: You connect TO external systems
Data Servers: External systems connect TO you

→ See TagProvider Services for connecting to external data sources

Available Services

OPC UA Server

Expose your UNS to external OPC UA clients using industry-standard protocols.

Capabilities:

• Browse and subscribe to any tag in the UNS
• Read/write access with configurable security
• Historical data access (if Historian configured)
• Alarm and event subscriptions

Configuration

Navigate to Unified Namespace → TagProvider Services and click the OPC UA Server icon.

→ See OPC UA Server Reference for complete configurationSee UNS Data Servers Reference for configuration details

MQTT Broker

Built-in MQTT broker for publish/subscribe messaging without external infrastructure.

Capabilities:

• Full MQTT 3.1.1 and MQTT 5.0 support
• Sparkplug B compatibility
• Topic-to-tag mapping
• QoS 0, 1, and 2 support
• WebSocket transport option

Configuration

Navigate to Unified Namespace → TagProvider Services and click the MQTT Broker icon.

→ See MQTT Broker UNS Data Servers Reference for complete configuration details

MCP for Runtime

Enable AI language models to query live solution data through Model Context Protocol.

Capabilities:

• Query tag values from the UNS
• Retrieve alarm status and history
• Access historian data for trend analysis
• Extend with custom tools via Script Classes

How It Works

AI Model (Claude) ←→ MCP Protocol ←→ TMCPServerStdio.exe ←→ TServer.exe

↓

[Live UNS Data Access]

Built-in Tools

Custom Tools

Create solution-specific tools using Script Classes. AI models can invoke any method you expose.

→ See AI MCP for Runtime Connector for setup → See AI MCP for Runtime Tutorial for step-by-step guideand configuration

DataHub Service

Distributed data aggregation for multi-solution architectures. Enables multiple FrameworX solutions to share and access tag, device, server, and alarm namespaces.

Capabilities:

• Multi-solution data synchronization
• Centralized UI solution consuming data from multiple edge solutions
• Shared alarm management across solutions
• Scalable distributed architecture

Architecture Pattern:

+-------------+     +-------------+     +-------------+
|   EDGE 1    |     |   EDGE 2    |     |   EDGE 3    |
|  (Publish)  |     |  (Publish)  |     |  (Publish)  |
+-------------+     +-------------+     +-------------+
        |
     ?               ?               ?
     ?????????????????????????????????
          |        
        +--------------------------------------+             	
?
              ???????????????
        |
            ? |UI  Solution ?
    +------------------+
  |   UI Solution    |
 ? | (DataHub) Service |?
  |   Port 30001)    |   
  +------------------+

Configuration

  ???????????????

→ See Data Hub Communication Service for

configuration

details

Configuration Location

Designer: Unified Namespace → Data Servers

Each service has its own configuration dialog accessible via the edit icon.

Data Servers Links

Explanation - to understand concepts
→ You are here

How-to Guides - to accomplish specific tasks
→ How to Enable Data Servers

Reference - technical details
→ UNS Data Servers Reference — All settings and configuration options
→ AI MCP for Runtime Connector — MCP setup and tutorial
→ Data Hub Communication Service — Multi-solution architecture details

See Also

• TagProvider Services — Connect to external systems (FrameworX as client)
• Data Foundation — UNS overview
• AI Integration — AI capabilities overview

Enabling Services at Runtime

Built-in services are enabled on the Runtime → Startup page:

Partner APIs

For development partners requiring direct programmatic access, additional APIs are available:

Contact Tatsoft for partner API access and documentation.

See Also

• TagProvider Services — Configure built-in services
• AI MCP for Runtime Connector — AI integration details
• Data Hub Communication Service — Multi-solution architecture
• Data Foundation — UNS overview