Page History

...

untime Execution Overview

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

...

• 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

...

What Happens at Runtime

When a solution starts, each pillar activates in sequence:

1. Foundation loads - Tags and templates enter memory
2. Process modules connect - Field devices start communicating
3. Application logic initiates - Scripts and datasets begin processing
4. Interface serves - Displays become available to clients

...

[Field] → [Devices] → [UNS Tags] → [Scripts] → [Displays]
           ↓            ↓            ↓           ↓
        [Alarms]    [Historian]  [Datasets]  [Clients]

Communication Methods

...

Execution Profiles

Different runtime behaviors for the same configuration:

Development Profile

• Local SQLite databases
• Full diagnostic logging
• Online configuration allowed
• Test data sources
• Debug information visible

...

• Execution model (Runtime, services, UNS)

• Client types (desktop, web)

• Basic diagnostics you’ll use first

Runtime Components

Execution Modes

Development Mode

...

Development vs Production

Simple Monitoring

Access runtime information through:

...

Performance Characteristics

Memory Usage by Pillar

Processing Distribution

Parallel Execution: Each pillar's modules run independently

...

1. TServer.exe starts (< 5 seconds)

   • Loads tag database
   • Initializes memory structures

2. Module activation (5-30 seconds)

   • Process modules connect to devices
   • Application modules initialize
   • Interface prepares client services

3. Steady state (< 60 seconds)

   • All communications established
   • Full data flow active
   • Clients can connect

untime Behavior

Solution Management Process

The Solution Center maintains a real-time view of all available solutions through file system monitoring and server connections. Solution files (.dbsln) contain complete configurations as encrypted embedded SQL databases, enabling portability and backup.

Access Methods

Solution Center supports three primary access modes:

Local Access: Direct file system access to solutions on the local computer

• Immediate file operations
• Single-user exclusive mode available
• No network requirements

Server Connection: Remote access via TWebServices

• Multi-user collaboration support
• Centralized solution management
• Requires port 10108 open

Web UI Access: Browser-based interface

• URL format: http://<server>:10108/solutions
• No local installation required
• Click-Once Designer deployment

Solution Execution States

...