| Module | Tables/UI | Runtime NS | Description |
|---|---|---|---|
| Uns | UnsTags | Tag | |
| UnsagProviders | - | ||
| Alarms | AlarmsGrups | Alarm.Group.<name |
Comprehensive product knowledge, for AI integration builders and advanced users.
...
The Solution Designer is the Windows-based configuration environment where solutions are built and tested. The Runtime Engine (TServer.exe) executes solutions on any supported platform. Operator interfaces run as Rich Clients (WPF desktop), Web Clients (WebAssembly), or Mobile Clients. The Solution Manager SolutionCenter provides a visual launcher for selecting and starting solutions.
...
MainPage plays a dual role. It is the default display loaded into the Content region at startup, and it also serves as the solution preview image — the Solution Manager SolutionCenter shows whatever is rendered on MainPage as the solution thumbnail when selecting solutions to open.
...
- TStartup.exe launches — loads the solution file, reads configuration, parses command line arguments, and activates the runtime engine
- TServer.exe starts — loads all objects, tags, templates, and assets into the real-time in-memory database and establishes the communication service
- Modules initialize — Historian, Alarms, Devices, Scripts, Datasets, and Reports start their services and connect to the main runtime process
- Execution profiles applied — modules configure themselves according to the selected profile (Development provides full access for testing; Production restricts modifications for operational safety)
- Designer auto-connects — if the Solution Designer is open, it connects to the running solution for live monitoring and diagnostics
- Client displays open — operator interfaces (WebAssembly or WPF) can be launched from any networked computer
- Online changes applied — configuration changes made during runtime are applied without disrupting the running solution. If the online configuration is enabled, the modifications are pushed right away. If the configuration online is disabled, or the modifications requires restart of modules, like changing UTDs, tag types, or other modifications there requires validation of scripts, or may have global impact, those require the command hot_updaterreload. That command is on Designer, Runtime Diagnostics pages, or by the AI MCP for Designer tools.
...
| Term | Definition |
|---|---|
| Solution | A FrameworX project stored as a .dbSLN file containing all configuration |
| Tag | A data element in the Unified Namespace — the atomic unit of real-time data |
| UserType (UDT) | A custom tag template that defines member tags and auto-updates instances |
| Point | A tag mapped to a physical device address for reading/writing field data |
| Channel | A protocol configuration defining how to communicate with a class of devices |
| Node | A specific device address within a channel |
| Display | An operator interface screen (Canvas for absolute layout, Dashboard for grid layout) |
| Symbol | A user-authored reusable graphic component with customizable appearance and behavior |
| WizardSymbol | A pre-built symbol (TANK, VALVE, PUMP, MOTOR, BLOWER) with easy customization |
| CodeBehind | C# or VB.NET code embedded in a display for event handling and custom actions |
| Layout | A screen region definition (Header, Footer, Menu, SubMenu, Content) for the running application |
| Hot UpdateReload | Applying configuration changes to a running solution without restart |
| Execution Profile | Development (unrestricted) or Production (operational restrictions) mode |
| TagProvider | An external data source that dynamically populates the UNS with tags |
| Asset() | A function for dynamic access to UNS paths, essential for TagProvider data |
| SolutionCenter | The application for selecting, launching, and managing solutions |
| SolutionCategories | Object labels applied across the solution — the MCP label marks AI-created objects. The labels each object has are visible on the Column/Property Category of the object. |
...
Overview
Content Tools
Tasks