...
Introduction to the Runtime
Runtime Module Overview
The Runtime Module executes your configured solution, transforming the static configuration into an active system. It loads tags into memory, processes real-time data, executes scripts and alarms, and serves information to clients - making your solution come alive.
The Runtime Environment is the active stage where a Solution starts and operates.
...
When the Runtime Environment loads the module's configuration. Some settings, such as network addresses and database connections, can be applied according to the execution profile. Profiles enable the same solution configuration to interface with various databases and devices, accommodating different phases of the solution life cycle, such as Development, Validation, or Production.
On this Page:
- Runtime Module Overview
- Key Concepts
- What It Does
- Configuration Workflow
- Runtime Behavior
- Feature Highlights
Key Concepts
- TServer.exe: The core process that runs your solution
- Execution Profile: Different settings for Development vs Production
- Real-Time Database: Tags and data held in memory for fast access
- Online Changes: Modify the running solution without stopping
- Test Mode: Run and debug from within Designer
- Build & Publish: Create validated versions for deployment
What It Does
- Starts and stops solution execution
- Loads tags and templates into memory
- Runs all configured modules (Devices, Alarms, Scripts, etc.)
- Manages connections to databases and field devices
- Serves data to displays and clients
- Monitors performance and system health
Key Concepts and Terms
The purpose of the Runtime Environment is to actively operate configured solutions, executing real-time data acquisition, scripts, alarms, and all items from all modules. It represents the essential final phase of solution development, delivering the application's functionality.
...
During Runtime, the Four Pillars transform from static configuration into an active system. Each pillar operates as an independent yet interconnected layer, with data flowing from field devices through the foundation layer, processed by business logic, and presented to users through visualization interfaces.
On this Page:
- Runtime Execution Overview
- Key Concepts
- What Happens at Runtime
- Pillar Interactions
- Execution Profiles
- Performance Characteristics
...
Key Concepts
- Pillar Activation: Each pillar becomes an active process or service during execution
- Data Flow Direction: Information moves upward through pillars, commands flow downward
- Module Independence: Each pillar's modules run as separate processes
- Memory-Based Operation: UNS maintains all real-time data in RAM
- Event-Driven Architecture: Changes propagate through publish-subscribe patterns
- Profile-Based Behavior: Same configuration runs differently in Dev vs Production
...
- Runtime Information
- Solution Center → Tools → Runtime Info
- Shows module status, memory, connections
- Property Watch
- Monitor tag values in real-time
- See quality and timestamps
- Diagnostics
- View logs and traces
- Analyze performance
Runtime (Concept)
Runtime Module Overview
The Runtime Module executes your configured solution, transforming the static configuration into an active system. It loads tags into memory, processes real-time data, executes scripts and alarms, and serves information to clients - making your solution come alive.
On this Page:
- Runtime Module Overview
- Key Concepts
- What It Does
- Configuration Workflow
- Runtime Behavior
- Feature Highlights
...
Key Concepts
- TServer.exe: The core process that runs your solution
- Execution Profile: Different settings for Development vs Production
- Real-Time Database: Tags and data held in memory for fast access
- Online Changes: Modify the running solution without stopping
- Test Mode: Run and debug from within Designer
- Build & Publish: Create validated versions for deployment
...
What It Does
- Starts and stops solution execution
- Loads tags and templates into memory
- Runs all configured modules (Devices, Alarms, Scripts, etc.)
- Manages connections to databases and field devices
- Serves data to displays and clients
- Monitors performance and system health
...