For Operations & Maintance

or: Control-Room Operators, Maintenance Techs

Focus: Runtime monitoring & diagnostics

Target Audience

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.)

Learning Objectives

• 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

Week 1: Foundation

Day 1 — Clients & Navigation

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)

Day 2 — Alarm Operations

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)

1. Identify alarm → confirm area & equipment

2. Acknowledge with note (reason/action)

3. Execute SOP steps; verify return-to-normal

4. Annotate trend; create follow-up task if recurrence

5. Shift log entry + handover

Exercise:

Run three alarm scenarios (process limit, device offline, bad quality). Capture notes, annotations, and outcome.

Day 3 — Trends & Reporting

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.

Day 4 — System Health & First-Line Diagnostics

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)

Day 5 — Shift Handover, Audit & Compliance

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

Week 2: Advanced Operations

Day 1 — Preventive Maintenance & Asset Watch

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.

Day 2 — Runtime Security & Access

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.

Day 3 — Performance Awareness for Operators

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.

Day 4 — Resilience Drills & Backups

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.

Day 5 — Assessment & Certification

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.

Reference Cards & Checklists (printables)

Alarm Severity → Response Time

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

Additional Resources (link from the O&M page)

• 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)

Notes: Page labels above map to the FrameworX 10.1 doc sections (e.g., AlarmViewer on p.11; TrendChart on p.10; Runtime System Monitor & Deployment on p.10; Diagnostics/Common Issues on p.11; Audit Trail in Alarms Module on p.8; Security/RuntimeUsers on p.9; ReportViewer on p.11).