Data Management:
- Tags (UNS) - Unified Namespace for real-time data management
- Devices - Communication with field devices and PLCs
- Historian - Time-series data storage and retrieval
- Datasets - SQL database synchronization and queries
Process Control:
- Alarms - Condition monitoring and notification management
- Scripts - Data processing and workflow automation
- Reports - Document generation (PDF/CSV) and data exchange (JSON/XML)
User Interface:
- Displays - Operator visualization and control interfaces
- Security - Access control and user authorization
The module lifecycle follows these states:
- Initialized - Module loaded, configuration read
- Starting - Resources allocated, connections established
- Running - Active operation, processing data
- Stopping - Graceful shutdown initiated
- Stopped - Resources released, module inactive
All modules communicate through the central TServer process:
- Tag Database acts as the central data hub
- Event System manages inter-module notifications
- Message Queue handles asynchronous operations
- Shared Memory enables high-speed data exchange
Pattern 1: PLC to Display
- PLC → Device Driver → Tag Database → Display Client
Pattern 2: Direct Device Binding
- PLC Address → Dynamic TagProvider → Display (bypasses Tag Database)
Pattern 3: Calculated Values
- Source Tags → Script Engine → Result Tag → Dataset → SQL Database
Pattern 4: Operator Commands
- Display Button → Tag Write → Device Driver → PLC
- Parallel Path: Tag Write → Audit Log (when enabled)
Pattern 5: Alarm Notification
- Tag Value Change → Alarm Condition → Notification System → Email/SMS