KPI dashboards in SCADA systems - Step-by-Step Execution

Process Flow - KPI dashboards

Collect Data from Sensors

↓

Process & Aggregate Data

↓

Calculate KPIs

↓

Update Dashboard Visuals

↓

User Views & Interprets KPIs

↓

Decide Actions Based on KPIs

Data flows from sensors to processing, KPIs are calculated, dashboard updates, and users make decisions.

Execution Sample

SCADA systems

sensor_data = [80, 85, 90, 95]
kpi_avg = sum(sensor_data) / len(sensor_data)
dashboard['Average Temp'] = kpi_avg
print(dashboard)

Calculate average temperature KPI from sensor data and update dashboard.

Process Table

Step	Action	Data/Variable	Result/Value	Dashboard Update
1	Read sensor data	sensor_data	[80, 85, 90, 95]	No change
2	Calculate average	kpi_avg	87.5	No change
3	Update dashboard	dashboard['Average Temp']	87.5	{'Average Temp': 87.5}
4	Print dashboard	dashboard	{'Average Temp': 87.5}	Dashboard shows Average Temp: 87.5

💡 All sensor data processed and dashboard updated with KPI.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
sensor_data	[]	[80, 85, 90, 95]	[80, 85, 90, 95]	[80, 85, 90, 95]	[80, 85, 90, 95]
kpi_avg	None	None	87.5	87.5	87.5
dashboard	{}	{}	{}	{'Average Temp': 87.5}	{'Average Temp': 87.5}

Key Moments - 2 Insights

Why do we calculate the average after reading all sensor data?

Because the average KPI depends on all sensor values, so calculation happens after collecting all data (see Step 2 in execution_table).

Why does the dashboard update only after KPI calculation?

Dashboard shows KPIs, so it updates only after KPI values are ready (Step 3). Updating before calculation would show wrong or empty data.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of kpi_avg at Step 2?

A 87.5

B None

C 90

D 95

💡 Hint

Check the 'Result/Value' column at Step 2 in execution_table.

At which step does the dashboard get updated with the KPI?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Dashboard Update' column to see when the dashboard changes.

If sensor_data had one more value 100, how would kpi_avg change at Step 2?

A It would decrease

B It would stay the same

C It would increase

D It would become zero

💡 Hint

Adding a higher value to sensor_data increases the average (see variable_tracker for kpi_avg).

Concept Snapshot

KPI dashboards collect sensor data,
process it to calculate KPIs,
then update visuals for users.
Data flows: Sensors -> Processing -> KPIs -> Dashboard.
Dashboards help quick decisions by showing key metrics.

Full Transcript

KPI dashboards in SCADA systems start by collecting data from sensors. This data is processed and aggregated to calculate key performance indicators (KPIs). Once KPIs are calculated, the dashboard visuals update to show these values. Users then view the dashboard to interpret the KPIs and decide on actions. For example, sensor data like temperatures are averaged to create an 'Average Temp' KPI, which updates the dashboard display. This flow ensures users see up-to-date, meaningful metrics to monitor system health.

Practice

1. What is the main purpose of a KPI dashboard in a SCADA system?

easy

A. To generate detailed reports for auditors

B. To store raw sensor data for later analysis

C. To control machine operations automatically

D. To display key performance indicators clearly and quickly

Solution

1. Step 1: Understand the role of KPI dashboards

   KPI dashboards focus on showing important numbers that reflect system performance.

2. Step 2: Differentiate from other SCADA functions

   Storing data, controlling machines, and generating reports are different tasks from displaying KPIs.

3. Final Answer:

   To display key performance indicators clearly and quickly -> Option D

4. Quick Check:

   KPI dashboard = clear key numbers [OK]

Hint: KPI dashboards show key numbers fast and clear [OK]

Common Mistakes:

• Confusing dashboards with data storage
• Thinking dashboards control machines
• Mixing dashboards with report generation

2. Which of the following is the correct way to highlight a KPI value that is below target using color in a dashboard?

easy

A. Use red color for values below target

B. Use yellow color for values below target

C. Use blue color for values below target

D. Use green color for values below target

Solution

1. Step 1: Understand color conventions in KPI dashboards

   Red usually signals a problem or below target performance.

2. Step 2: Match color to KPI status

   Green means good, red means bad, so below target should be red.

3. Final Answer:

   Use red color for values below target -> Option A

4. Quick Check:

   Below target = red color [OK]

Hint: Red means below target or problem [OK]

Common Mistakes:

• Using green for bad performance
• Choosing blue which is neutral
• Using yellow which means caution, not failure

3. Given a SCADA KPI dashboard showing machine uptime percentages: Machine A = 95%, Machine B = 88%, Machine C = 92%. If the target uptime is 90%, which machines should be highlighted in red?

medium

A. Machine B only

B. Machine A and Machine C

C. Machine A only

D. Machine B and Machine C

Solution

1. Step 1: Compare each machine's uptime to the target

   Machine A: 95% > 90% (above target), Machine B: 88% < 90% (below target), Machine C: 92% > 90% (above target).

2. Step 2: Identify which machines are below target

   Only Machine B is below the 90% target and should be highlighted in red.

3. Final Answer:

   Machine B only -> Option A

4. Quick Check:

   Below 90% uptime = red highlight [OK]

Hint: Highlight only below target values in red [OK]

Common Mistakes:

• Highlighting machines above target
• Including machines that meet or exceed target
• Ignoring the target threshold

4. You created a KPI dashboard but the color coding does not change when values go below target. What is the most likely cause?

medium

A. The data source is missing some sensor readings

B. The dashboard layout is too complex

C. The color rules are not linked to the KPI values correctly

D. The target values are set too high

Solution

1. Step 1: Check the color coding logic

   If colors do not change, the rules linking KPI values to colors are likely not set or connected properly.

2. Step 2: Rule out other causes

   Layout complexity or missing data won't directly stop color changes; target values affect performance but not color logic.

3. Final Answer:

   The color rules are not linked to the KPI values correctly -> Option C

4. Quick Check:

   Color rules linked properly = color changes [OK]

Hint: Check color rule connections first when colors don't update [OK]

Common Mistakes:

• Blaming layout instead of logic
• Assuming missing data causes color issues
• Thinking target values affect color coding directly

5. You want to design a KPI dashboard for a SCADA system that shows temperature, pressure, and flow rate KPIs. Which layout approach best supports quick understanding?

hard

A. Display all raw sensor data in a large table with no colors

B. Arrange KPIs in a simple grid with clear labels and color-coded status

C. Show only the average values without any target or color indicators

D. Use multiple pages with detailed charts for each KPI

Solution

1. Step 1: Identify best practices for KPI dashboard layout

   Simple grids with clear labels and color coding help users quickly see status and compare KPIs.

2. Step 2: Evaluate other options

   Raw data tables, averages without targets, or multi-page charts reduce clarity and speed of understanding.

3. Final Answer:

   Arrange KPIs in a simple grid with clear labels and color-coded status -> Option B

4. Quick Check:

   Simple, clear, color-coded layout = fast understanding [OK]

Hint: Use simple grids and colors for fast KPI reading [OK]

Common Mistakes:

• Showing raw data instead of KPIs
• Omitting targets and colors
• Splitting KPIs across many pages