Historian architecture overview in SCADA systems - Mini Project: Build & Apply

Historian Architecture Overview

📖 Scenario: You are working with a SCADA system that collects data from industrial sensors. To analyze and store this data efficiently, you need to understand the historian architecture that manages time-series data storage and retrieval.

🎯 Goal: Build a simple representation of a historian architecture using data structures to model data collection, configuration, data filtering, and output display.

📋 What You'll Learn

Create a dictionary to represent sensor data with exact timestamps and values

Add a configuration variable for a time threshold to filter recent data

Use a comprehension to filter sensor data newer than the threshold

Print the filtered data to show the final output

💡 Why This Matters

🌍 Real World

Historian architectures are used in SCADA systems to store and retrieve time-series data from sensors for monitoring and analysis.

💼 Career

Understanding historian data structures and filtering is essential for roles in industrial automation, DevOps for SCADA, and data engineering in manufacturing.

1

Create initial sensor data dictionary

Create a dictionary called sensor_data with these exact entries: '2024-06-01T10:00:00': 23.5, '2024-06-01T10:05:00': 24.0, '2024-06-01T10:10:00': 23.8, '2024-06-01T10:15:00': 24.2

SCADA systems

# Create the sensor_data dictionary with exact timestamps and values
# Your code here

Hint

Use a dictionary with timestamps as keys and sensor values as floats.

2

Add time threshold configuration

Create a variable called time_threshold and set it to the string '2024-06-01T10:05:00' to filter data newer than this timestamp

SCADA systems

sensor_data = {
    '2024-06-01T10:00:00': 23.5,
    '2024-06-01T10:05:00': 24.0,
    '2024-06-01T10:10:00': 23.8,
    '2024-06-01T10:15:00': 24.2
}
# Create the time_threshold variable with the exact timestamp string
# Your code here

Hint

Set the time_threshold variable to the exact timestamp string.

3

Filter sensor data newer than threshold

Create a dictionary called filtered_data using a dictionary comprehension that includes only entries from sensor_data where the timestamp key is greater than time_threshold

SCADA systems

sensor_data = {
    '2024-06-01T10:00:00': 23.5,
    '2024-06-01T10:05:00': 24.0,
    '2024-06-01T10:10:00': 23.8,
    '2024-06-01T10:15:00': 24.2
}
time_threshold = '2024-06-01T10:05:00'
# Create filtered_data dictionary with entries newer than time_threshold
# Your code here

Hint

Use a dictionary comprehension with timestamp and value from sensor_data.items() and filter by timestamp > time_threshold.

4

Print the filtered sensor data

Write a print statement to display the filtered_data dictionary

SCADA systems

sensor_data = {
    '2024-06-01T10:00:00': 23.5,
    '2024-06-01T10:05:00': 24.0,
    '2024-06-01T10:10:00': 23.8,
    '2024-06-01T10:15:00': 24.2
}
time_threshold = '2024-06-01T10:05:00'
filtered_data = {timestamp: value for timestamp, value in sensor_data.items() if timestamp > time_threshold}
# Print the filtered_data dictionary
# Your code here

Hint

Use print(filtered_data) to show the filtered dictionary.

Practice

1. What is the main purpose of a historian in SCADA systems?

easy

A. To collect and store time-stamped data from machines

B. To control machine operations directly

C. To replace human operators in factories

D. To design machine hardware

Solution

1. Step 1: Understand the role of a historian

   A historian is designed to collect and store data over time from machines and processes.

2. Step 2: Compare options with historian function

   Only To collect and store time-stamped data from machines matches this function; others describe unrelated tasks.

3. Final Answer:

   To collect and store time-stamped data from machines -> Option A

4. Quick Check:

   Historian = Data collection and storage [OK]

Hint: Remember: historian stores data, not controls machines [OK]

Common Mistakes:

• Confusing historian with control system
• Thinking historian replaces operators
• Assuming historian designs hardware

2. Which component is NOT typically part of a historian architecture?

easy

A. Data collector

B. Storage database

C. Dashboard interface

D. Machine actuator

Solution

1. Step 1: Identify common historian components

   Historians usually have data collectors, storage, and dashboards for visualization.

2. Step 2: Check which component is unrelated

   Machine actuators control machines physically and are not part of historian architecture.

3. Final Answer:

   Machine actuator -> Option D

4. Quick Check:

   Actuator ≠ historian component [OK]

Hint: Actuators act on machines, historians collect data [OK]

Common Mistakes:

• Confusing actuators with data collectors
• Thinking dashboards control machines
• Assuming storage is optional

3. Given this simplified historian data flow:

Machine Sensor -> Data Collector -> Storage -> Dashboard

What will the dashboard show if the storage is empty?

medium

A. Control commands to machines

B. Real-time machine data

C. No historical data available

D. Error message from data collector

Solution

1. Step 1: Understand data flow in historian

   Data flows from sensors to storage before dashboard can display it.

2. Step 2: Analyze dashboard output with empty storage

   If storage is empty, dashboard has no historical data to show, so it displays none.

3. Final Answer:

   No historical data available -> Option C

4. Quick Check:

   Empty storage means no data on dashboard [OK]

Hint: Dashboard shows stored data, empty storage means no data [OK]

Common Mistakes:

• Assuming dashboard shows real-time data directly
• Expecting control commands on dashboard
• Thinking data collector errors show on dashboard

4. A historian system is not showing updated data on the dashboard. Which fix is most likely correct?

medium

A. Replace the machine sensors

B. Restart the data collector service

C. Upgrade the dashboard software

D. Increase storage database size

Solution

1. Step 1: Identify cause of no updated data

   Data collector failure often stops new data from reaching storage and dashboard.

2. Step 2: Choose the most direct fix

   Restarting the data collector service restores data flow quickly.

3. Final Answer:

   Restart the data collector service -> Option B

4. Quick Check:

   Data collector restart fixes data update issues [OK]

Hint: Restart data collector first to fix no updates [OK]

Common Mistakes:

• Replacing sensors unnecessarily
• Upgrading dashboard without checking data flow
• Increasing storage size unrelated to update issue

5. In a historian architecture, how can you ensure data integrity when multiple data collectors send data simultaneously?

hard

A. Use timestamp synchronization and unique data IDs

B. Allow collectors to overwrite each other's data

C. Disable data collectors except one at a time

D. Store data only on local machines, not centralized

Solution

1. Step 1: Understand data integrity challenges

   Multiple collectors sending data can cause conflicts or duplicates without coordination.

2. Step 2: Identify best practice for integrity

   Using synchronized timestamps and unique IDs prevents data conflicts and ensures correct ordering.

3. Final Answer:

   Use timestamp synchronization and unique data IDs -> Option A

4. Quick Check:

   Sync timestamps + unique IDs ensure data integrity [OK]

Hint: Sync time and use unique IDs to avoid data conflicts [OK]

Common Mistakes:

• Overwriting data causes loss
• Disabling collectors reduces data completeness
• Local storage prevents centralized analysis