Page History
...
Singleton tables (SolutionSettings, AlarmsGlobalSettings, RuntimeStartup) have no key column — they contain a single configuration row. RuntimeExecutionProfiles for AI will show only the differences between Development and Production profiles, directly on the Designer UI it has more options.
...
Module Architecture
Tags — The Data Foundation
...
SecuritySecrets stores credentials for external system authentication. Secret values are write-only and cannot be read back through any API.
Settings
...
Solution and Runtime Configuration
SolutionCategories defines labels applied to any object in the solution. The predefined MCP category marks AI-created objects — AI can only modify objects that have this label.
Four singleton configuration tables
...
contain global settings with a single configuration row each:
SolutionSettings contains global solution parameters. AlarmsGlobalSettings provides alarm module defaults. RuntimeStartup controls startup behavior and runtime options. RuntimeExecutionProfiles defines connection replacements between Development and Production profiles — for example, different server addresses per execution profile
...
.
...
Runtime Architecture
Startup Sequence
...
- 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 through hot reload 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_update. That command is on Designer, Runtime Diagnostics pages, or by the AI MCP for Designer tools.
Execution Profiles
Development profile provides unrestricted access for configuration, testing, and debugging. Production profile enforces operational restrictions appropriate for live industrial environments. The MCP for Designer service operates under the Development profile.
...