Monitor systems, manage alarms, and ensure uptime.
Next → Control | IT | Operations | System Integrators
Operations and maintenance teams ensure 24/7 system reliability. This guide navigates you through runtime monitoring, alarm response, and diagnostic procedures.
Core Responsibilities:
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Essential Tools:
Core Documentation:
Trending Tools:
Severity | Acknowledge | Resolve | Escalate |
---|---|---|---|
Critical | < 1 min | < 15 min | Immediate |
High | < 5 min | < 60 min | If unresolved |
Medium | < 15 min | End of shift | As needed |
Low | < 60 min | Scheduled | No |
Symptom | Check | Reference |
---|---|---|
Tag not updating | Device status | [Devices Monitor Reference] |
Client slow | Display complexity | [Performance optimization] |
Trend gaps | Historian service | [Historian Monitor Reference] |
Login fails | User permissions | [Security RuntimeUsers Reference] |
Documentation Requirements:
FrameworX Operations Specialist
Week 1 Focus:
Week 2 Focus:
Essential References:
Examples & Best Practices:
Support:
Page Tree | ||
---|---|---|
|
or: Control-Room Operators, Maintenance Techs
Focus: Runtime monitoring & diagnostics
Operators and maintenance staff responsible for day-to-day running of FrameworX solutions: monitoring health, responding to alarms, reviewing trends/reports, performing basic diagnostics, and executing shift handovers. (See AlarmViewer, TrendChart, Runtime System Monitor, Diagnostics Tools, Audit Trail, Security/RuntimeUsers, ReportViewer in the docs.)
Monitor system health and data flows in real time
Respond to alarms consistently and document actions
Use trends, annotations, and reports to investigate issues
Perform first-line diagnostics on comms, clients, and historian
Execute shift handover & maintain audit/compliance records
Apply runtime security best practices and least-privilege access
...
Your Role
...
Primary Focus
...
Essential Pages
...
Advanced Topics
...
System Integrator
...
Full platform
Implementation
...
Platform Overview
The Four Pillars
...
Solution Lifecycle
P1: UNS Foundation
...
Security & Operations
Key Differentiators
...
Control Engineer
...
Field connectivity
Process Control
...
Solution Lifecycle
P1: UNS Foundation
...
P2: Process Modules
Devices Module
...
Alarms Module
Historian Module
...
HMI Developer
...
User interfaces
Visualization
...
Designer
P4: Operator UI
...
Displays Module
Runtime
...
Security Module
P3: Application Modules
...
IT Administrator
...
Deployment
Maintenance
...
Architecture
Security & Operations
...
Runtime
Solution Center
...
Product Editions
Datasets Module
...
Project Manager
Evaluator
...
Capabilities
Planning
...
Platform Overview
Key Differentiators
...
Product Editions
The Four Pillars
...
Technology Foundation
Architecture
Topics
SmartClient / Web Client basics: login, navigation, bookmarks, user settings
Display layouts, symbols, and operator-level interactions (buttons, popups, dashboards)
Report viewing (ReportViewer) and quick exports
Exercise:
Log in with an operator role; open the overview display; bookmark three critical pages; run a daily production report; export to CSV/PDF.
Quick-Check Card (post on the wall)
Check | How |
---|---|
Server/Runtime status | Runtime System Monitor page |
Client connectivity | Web Client Connection Checklist |
Time sync | Verify NTP source in system notes |
Topics
Alarm philosophy recap (states, severity, shelving/ack, notes)
AlarmViewer usage: filters, areas, duration field, history drill-down
Notifications and escalation overview (email/SMS policies)
Playbook (baseline)
Identify alarm → confirm area & equipment
Acknowledge with note (reason/action)
Execute SOP steps; verify return-to-normal
Annotate trend; create follow-up task if recurrence
Shift log entry + handover
Exercise:
Run three alarm scenarios (process limit, device offline, bad quality). Capture notes, annotations, and outcome.
Topics
TrendChart basics: pens, cursors, time windows, annotations, saving views
Historian concepts: tags, retention, exporting to CSV; Historian Monitor
Daily/weekly reports for production and alarm KPIs
Lab:
Create a saved trend view for a critical asset; add two annotations linked to an alarm; export a 24-hour CSV; attach to a shift report.
Topics
Runtime System Monitor: services, CPU/RAM, queue/backlog indicators
Device/connection monitors; quick comms checks (Ping/SNMP)
Diagnostics Tools & common issues (HTTPS/SSL, client download blocks)
Diagnostics Matrix (use on incidents)
Symptom | First Checks | Likely Fix |
---|---|---|
Tag stale/bad | Device node status; channel link | Re-establish comms; check routing/firewall |
Client slow | Display point count; network latency | Use smaller views; verify bandwidth |
Trend gap | Historian service & storage | Confirm service; free disk space |
Login fails | AD/LDAP reachability; role | Verify directory & permissions |
Topics
Audit Trail usage during operations (who did what/when)
RuntimeUsers, permissions, and least-privilege access
Shift handover notes and attachments; report bundles
Deliverables
Shift Handover Template (what happened, alarms of concern, pending work orders)
Operator SOP binder: alarm response, comms check, report schedule
Topics
Using trends/reports to spot drift; simple KPIs per asset
Creating “watch” views; thresholds for early warnings
Optional: link to CMMS via datasets/exports (process outline)
Exercise:
Define three early-warning indicators and a weekly review report.
Topics
Roles/permissions for operators vs. maintenance; temporary elevation process
AD/LDAP integration overview; policy for password/account hygiene
Exercise:
Review current roles; remove excess privileges; test operator sign-in & access to required pages only.
Topics
Display optimization habits (lazy loading, fewer live points per view)
Historian query hygiene (time windows, pen counts)
Client/network basics (when to call IT vs. fix locally)
Lab:
Split an overloaded display into two; measure load improvement; document best practice.
Topics
Hot-standby / redundancy overview; operator steps during failover
Backup/restore awareness; where to find runbooks
Notification test: confirm emails/SMS reach the right on-call list
Drill:
Simulate primary outage; execute client reconnection & verification checklist; record times.
Operator Practical (90 min)
Handle a 3-alarm sequence with notes, annotations, and report
Diagnose a comms outage using monitors/diagnostics
Complete shift handover with audit proof
Certification: FrameworX Operations Specialist
Format: scenario practical + short quiz; validity 2 years; CE via annual drill.
Alarm Severity → Response Time
Severity | Target Ack | Target Resolve |
---|---|---|
Critical | ≤ 1 min | ≤ 15 min |
High | ≤ 5 min | ≤ 60 min |
Medium | ≤ 15 min | Shift |
Low | ≤ 60 min | As scheduled |
Daily Runtime Checklist
Review Runtime System Monitor (CPU/RAM/queues)
Scan AlarmViewer filters for standing alarms
Verify historian ingestion & free disk space
Run daily production/alarm report and archive
Note issues in shift log; prep handover
Shift Handover Essentials
Top 5 alarms & status, open actions
Equipment on watch, current trends attached
Any client/network anomalies observed
Maintenance requests raised & references
Sign-off with Audit Trail entry
AlarmViewer Control & Alarm Areas/Module pages (operations UI)
TrendChart Control & Trend Settings (trending & annotations)
Runtime System Monitor & Diagnostics Tools / Common Issues
Audit Trail; Security RuntimeUsers / AD-LDAP (accountability & access)
ReportViewer Control & Reports Module (daily/weekly reports)
...