Expose the Unified Namespace to external clients, AI systems, and other FrameworX solutions.
Modules → Data Foundation → Data Services | Reference
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.
| Setting | Description |
|---|---|
| Port | Default: 4840 |
| Security Mode | None, Sign, SignAndEncrypt |
| User Authentication | Anonymous, Username/Password, Certificate |
→ See OPC UA Server Reference for complete configuration
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.
| Setting | Description |
|---|---|
| TCP Port | Default: 1883 |
| WebSocket Port | Default: 8083 |
| Authentication | Anonymous, Username/Password |
| TLS | Optional encryption |
→ See MQTT Broker Reference for complete configuration
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
| Tool | Description |
|---|---|
| Get Value | Read current tag values |
| Get Historian | Query historical data |
| Get Alarms | Retrieve alarm status |
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 guide
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
+-------------+ +-------------+ +-------------+
| EDGE 1 | | EDGE 2 | | EDGE 3 |
| (Publish) | | (Publish) | | (Publish) |
+-------------+ +-------------+ +-------------+
| |
+--------------------------------------+
|
|
+-----------------+
| UI Solution |
| (DataHub Service|
| Port 30001) |
+-----------------+
Configuration
| Setting | Description |
|---|---|
| Listening Port | Default: 30001 |
| Access Key | Authentication for connections |
| Access Mode | Read, Write, or ReadWrite |
→ See Data Hub Communication Service for complete configuration
Enabling Services at Runtime
Built-in services are enabled on the Runtime → Startup page:
| Service | Startup Option | Configuration Location |
|---|---|---|
| OPC UA Server | ?? OPCServer | TagProvider Services |
| MQTT Broker | ?? MQTTBroker | TagProvider Services |
| MCP for Runtime | Enabled via Scripts | Scripts → Classes |
| DataHub Service | ?? Publish to DataHub | TagProvider Services |
Partner APIs
For development partners requiring direct programmatic access, additional APIs are available:
| API | Description |
|---|---|
| .NET API | Native .NET library for direct solution integration |
| REST API | HTTP-based access for web and cloud applications |
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