SICAM SCC Training

SICAM SCC Practical Training

Substation SCADA & HMI Engineering

Production Format

Each lesson should follow this structure:

Gallery Image → Voice Narration → Live Demonstration → Practical Point

For screenshots, use real SICAM SCC/PAS project screenshots wherever possible. Where a screen is not available yet, create a placeholder screenshot with the specified content.


MODULE 1 — SICAM SCC FUNDAMENTALS

Lesson 1.1 — What Is SICAM SCC?

Gallery 1 — Course Title

Screenshot:
Clean title screen:

SICAM SCC Practical Training
Substation SCADA & HMI Engineering

Voice:

“Welcome to the SICAM SCC Practical Training course. In this course, we will focus on the practical engineering and operation of SICAM SCC in substation automation systems.”


Gallery 2 — What SCC Does

Screenshot:
SICAM SCC main/runtime screen.

Highlight:

  • Main navigation
  • Process picture
  • Alarm area
  • Status area
  • Operator controls

Voice:

“SICAM SCC provides the operator interface for monitoring and controlling the substation process. It presents information received from the automation system and allows authorized operators to interact with the process.”


Gallery 3 — From Field to Operator

Screenshot/diagram:

Primary Equipment
       ↓
Protection & Control IEDs
       ↓
IEC 61850 / Communication
       ↓
SICAM PAS
       ↓
SICAM SCC
       ↓
Operator

Voice:

“This is the basic signal path that we will follow throughout the course. Information starts at the physical process and protection and control devices, passes through the communication and station automation layer, reaches SICAM PAS, and is finally presented to the operator through SICAM SCC.”


Lesson 1.2 — SCC in Substation Automation

Gallery 4 — Substation Automation Architecture

Screenshot:
Complete architecture showing:

  • Bay level
  • IEDs
  • Station bus
  • SICAM PAS
  • SICAM SCC
  • Operator station

Voice:

“SICAM SCC should not be considered as an isolated HMI application. It is one part of the complete substation automation architecture.”


Gallery 5 — Bay Level

Screenshot:
IEDs and primary equipment.

Highlight:

  • Protection relay
  • Breaker
  • Disconnector
  • CT/PT
  • Measurements

Voice:

“At bay level, protection and control devices acquire information from the electrical process and perform protection, measurement and control functions.”


Gallery 6 — Station Level

Screenshot:
PAS and SCC.

Voice:

“At station level, the automation system collects and processes this information. SICAM SCC then provides the operator with a graphical representation of the station.”


Lesson 1.3 — SCC and WinCC

Gallery 7 — WinCC/SCC Engineering Environment

Screenshot:
WinCC Explorer / SCC engineering environment.

Voice:

“SICAM SCC is closely associated with the WinCC engineering environment. However, in this course our focus is not generic WinCC programming. Our focus is the use of the environment for practical substation SCADA engineering.”


Gallery 8 — Engineering vs Runtime

Screenshot:
Side-by-side:

Engineering

  • Project configuration
  • Graphics
  • Alarms
  • Users
  • Data

Runtime

  • Process visualization
  • Alarms
  • Controls
  • Events

Voice:

“It is important to distinguish engineering from runtime. Engineering is where we build and configure the system. Runtime is where the operator monitors and controls the actual process.”


Lesson 1.4 — Typical SCC Architecture

Gallery 9 — Complete Architecture

Screenshot:
Full architecture.

Voice:

“This architecture will be our reference throughout the course. When something does not work, we will use this signal chain to determine where the problem exists.”


Gallery 10 — Troubleshooting Signal Chain

Screenshot:
Same architecture with numbered stages:

  1. IED
  2. Communication
  3. PAS
  4. SCC
  5. Graphic
  6. Operator

Voice:

“For example, if a breaker status does not change on the SCC screen, we should not immediately assume that the graphic is wrong. We must trace the signal from the IED through PAS and finally into SCC.”


Practical Exercise 1

Gallery 11 — Exercise

Screenshot:
Architecture with blank labels.

Voice:

“Your first exercise is to identify each component of the architecture and explain the role of each layer.”


MODULE 2 — INSTALLATION, PROJECT AND ENGINEERING ENVIRONMENT

Lesson 2.1 — Software Environment

Gallery 12 — Installed Components

Screenshot:
Actual installed Siemens/SICAM/WinCC components.

Voice:

“Before starting engineering, we need to understand the installed software environment. The exact components and menus depend on the installed product versions and engineering configuration.”


Gallery 13 — Version Information

Screenshot:
Version information screen.

Highlight:

  • SCC version
  • WinCC version
  • PAS version
  • Engineering components

Voice:

“Version compatibility is particularly important in engineering projects. Always document the versions used for the project.”


Lesson 2.2 — Creating a Project

Gallery 14 — New Project

Screenshot:
New project dialog.

Voice:

“We begin by creating or opening the engineering project. In a real project, this step should be followed by a clear project naming and documentation convention.”


Gallery 15 — Project Properties

Screenshot:
Project properties.

Voice:

“Project properties contain important information about the project environment. Before engineering, verify the project configuration rather than assuming that default settings are suitable.”


Gallery 16 — WinCC Explorer

Screenshot:
WinCC Explorer.

Highlight:

  • Computer
  • Tag Management
  • Alarm Logging
  • Graphics
  • User Administration
  • Archives

Voice:

“This environment provides access to the major engineering components that we will use during the course.”


Gallery 17 — Project Tree

Screenshot:
Expanded project tree.

Voice:

“A well-organized project structure becomes increasingly important as the number of bays, signals and graphics increases.”


Lesson 2.3 — Engineering Workflow

Gallery 18 — Engineering Workflow

Screenshot/diagram:

Project
 ↓
Communication/Data
 ↓
Process Information
 ↓
Graphics
 ↓
Alarms
 ↓
Controls
 ↓
Users
 ↓
Runtime Test
 ↓
Commissioning

Voice:

“This is the engineering workflow we will follow. We first establish the project and process data, then build the operator interface, configure alarms and controls, define users and finally test the complete system.”


Practical Exercise 2

Gallery 19 — Exercise: Create Project

Screenshot:
Project creation screen.

Voice:

“For this exercise, create a training project and inspect the main project structure. Identify where graphics, alarms, process data and user administration are configured.”


MODULE 3 — PAS TO SCC INTEGRATION

Lesson 3.1 — PAS and SCC Relationship

Gallery 20 — PAS to SCC

Screenshot/diagram:

IED
 ↓
IEC 61850
 ↓
SICAM PAS
 ↓
SICAM SCC

Voice:

“SICAM PAS and SICAM SCC perform different but complementary tasks. PAS handles station automation and process information, while SCC presents this information to the operator.”


Gallery 21 — Process Information

Screenshot:
PAS process information/data point view.

Voice:

“Before building an SCC graphic, we need to understand the process information available from the automation system.”


Lesson 3.2 — Binary Status

Gallery 22 — Breaker Status

Screenshot:
Breaker status signal in PAS/SCC.

Voice:

“A simple example is breaker position. The breaker may provide open, closed or intermediate status. SCC uses this information to represent the actual process state.”


Gallery 23 — Disconnector Status

Screenshot:
Disconnector signals.

Voice:

“The same principle applies to disconnectors and other switchgear.”


Lesson 3.3 — Analog Measurements

Gallery 24 — Measurements

Screenshot:
Voltage/current/P/Q/frequency values.

Voice:

“Analog process values can include voltage, current, active power, reactive power and frequency. Correct engineering units and scaling are essential.”


Gallery 25 — Measurement Quality

Screenshot:
Process value with quality/status information.

Voice:

“Do not look only at the numerical value. Quality information can indicate whether the value is valid, uncertain, substituted or affected by a communication problem.”


Lesson 3.4 — Commands

Gallery 26 — Breaker Command

Screenshot:
Control object/dialog.

Voice:

“Commands are different from indications. An indication tells us what happened. A command requests that the process change state.”


Gallery 27 — Command Feedback

Screenshot:
Command followed by breaker status.

Voice:

“After a command, we must verify the feedback. A successful command is not simply the moment when the operator clicks the button. We must confirm that the physical or logical process state changed as expected.”


Lesson 3.5 — Signal Tracing

Gallery 28 — Signal Trace

Screenshot:
One breaker signal followed through:

IED → PAS → SCC

Voice:

“This is one of the most important troubleshooting techniques in the course. When a signal is missing, trace it through every layer rather than changing the graphic immediately.”


Practical Exercise 3

Gallery 29 — Exercise: Breaker Status

Screenshot:
Breaker signal.

Task:

  • Identify breaker status
  • Trace it in PAS
  • Display it in SCC
  • Change the breaker state
  • Verify SCC feedback

Gallery 30 — Exercise: Measurement

Screenshot:
Voltage/current/P/Q.

Task:

“Trace at least one analog value from the source through PAS and into SCC.”


MODULE 4 — GRAPHICS AND SINGLE-LINE DIAGRAMS

Lesson 4.1 — Graphics Designer

Gallery 31 — Graphics Designer

Screenshot:
Graphics Designer open.

Voice:

“The graphics environment is where we create the operator’s visual representation of the substation.”


Gallery 32 — New Process Picture

Screenshot:
New process picture.

Voice:

“We begin by creating a process picture. The picture should be designed around the operator’s needs rather than simply reproducing engineering drawings.”


Lesson 4.2 — Basic Objects

Gallery 33 — Basic Graphic Objects

Screenshot:
Objects such as:

  • Line
  • Rectangle
  • Text
  • Symbol
  • Button

Voice:

“These basic objects form the building blocks of the operator interface.”


Gallery 34 — Busbar

Screenshot:
Busbar graphic.

Voice:

“The busbar should clearly represent the electrical topology.”


Gallery 35 — Breaker

Screenshot:
Breaker symbol.

Voice:

“The breaker symbol must provide an immediate visual indication of the equipment state.”


Gallery 36 — Disconnector

Screenshot:
Disconnector symbol.

Voice:

“Disconnectors are represented separately because their operational meaning differs from a circuit breaker.”


Lesson 4.3 — Dynamic Objects

Gallery 37 — Static vs Dynamic

Screenshot:
Same object shown in static and dynamic states.

Voice:

“A static symbol only represents an object visually. A dynamic object changes according to process information.”


Gallery 38 — Breaker Open

Screenshot:
Breaker open.

Voice:

“This is an example of the breaker in the open state.”


Gallery 39 — Breaker Closed

Screenshot:
Breaker closed.

Voice:

“After the process state changes, the graphic should represent the closed state.”


Gallery 40 — Intermediate/Unknown State

Screenshot:
Intermediate or abnormal state.

Voice:

“We should also consider abnormal or intermediate conditions. These states can be important during switching operations and troubleshooting.”


Lesson 4.4 — Measurements on SLD

Gallery 41 — Measurement Display

Screenshot:
Voltage/current/P/Q next to bay.

Voice:

“Measurements should be positioned close enough to the relevant equipment to make their meaning immediately clear.”


Lesson 4.5 — Navigation

Gallery 42 — Main Overview

Screenshot:
Substation overview.

Gallery 43 — Bay Screen

Screenshot:
Detailed bay.

Gallery 44 — Navigation Buttons

Screenshot:
Buttons linking overview and bay screens.

Voice:

“A practical SCADA project normally uses several levels of visualization. The overview provides the overall situation, while bay screens provide more detailed information.”


Practical Exercise 4

Gallery 45 — Target SLD

Screenshot:
Target bay configuration.

Task:

Create:

  • Busbar
  • Two disconnectors
  • One breaker
  • Feeder
  • Measurements
  • Status indications
  • Navigation

Gallery 46 — Completed SLD

Screenshot:
Completed practical bay.

Voice:

“This is the expected result of the graphics exercise.”


MODULE 5 — SWITCHGEAR MONITORING AND CONTROL

Lesson 5.1 — Monitoring Breakers

Gallery 47 — Breaker States

Screenshot:
Open / closed / intermediate.

Voice:

“Correct state representation is fundamental to safe operation. The operator must be able to distinguish normal states and abnormal states.”


Gallery 48 — Communication Failure

Screenshot:
Breaker with invalid/communication status.

Voice:

“A communication failure must not be confused with an actual equipment state.”


Lesson 5.2 — Local and Remote

Gallery 49 — Local/Remote Status

Screenshot:
Local/remote indication.

Voice:

“Before attempting a remote command, we must verify whether remote control is available.”


Gallery 50 — Switching Authority

Screenshot:
Control authority/status.

Voice:

“Control authority determines whether a particular operator or system is permitted to perform the requested operation.”


Lesson 5.3 — Control Dialog

Gallery 51 — Control Dialog

Screenshot:
Breaker control window.

Voice:

“This control dialog allows the operator to issue an authorized command.”


Gallery 52 — Command

Screenshot:
Command action.

Voice:

“Before issuing a command, verify the equipment, its current state, the operating authority and the intended action.”


Gallery 53 — Feedback

Screenshot:
Breaker state after command.

Voice:

“After the command, verify the feedback. The final state is more important than the button press itself.”


Gallery 54 — Failed Command

Screenshot:
Failed command/unsuccessful operation.

Voice:

“If the command fails, do not immediately repeat the command. First determine why it failed. Possible causes include communication problems, local mode, interlocking, permission problems or equipment conditions.”


Practical Exercise 5

Gallery 55 — Control Test

Screenshot:
Before command.

Gallery 56 — Command

Screenshot:
Control action.

Gallery 57 — Feedback

Screenshot:
New breaker state.

Task:

“Perform the command sequence and document the initial state, command and final feedback.”


MODULE 6 — ALARM LOGGING, EVENTS AND MESSAGES

Lesson 6.1 — Alarm vs Event

Gallery 58 — Alarm/Event Concept

Screenshot/diagram:

Process Change
      ↓
Event
      +
Abnormal Condition
      ↓
Alarm

Voice:

“An event records something that happened. An alarm normally indicates a condition that requires operator attention.”


Lesson 6.2 — Alarm Logging

Gallery 59 — Alarm Logging

Screenshot:
Alarm Logging configuration.

Voice:

“Alarm Logging provides the framework for managing process alarms and messages.”


Gallery 60 — Alarm List

Screenshot:
Runtime alarm list.

Highlight:

  • Time
  • Message
  • Priority
  • State
  • Acknowledgement

Voice:

“The operator should be able to understand what happened, when it happened and whether the alarm has been acknowledged.”


Gallery 61 — Message Classes

Screenshot:
Message classes.

Voice:

“Message classes help organize different types of process information.”


Gallery 62 — Alarm Priority

Screenshot:
Priority configuration.

Voice:

“Priority should reflect the operational significance of the condition. The goal is not simply to create more alarms, but to provide useful information to the operator.”


Lesson 6.3 — Acknowledgement

Gallery 63 — Unacknowledged Alarm

Screenshot:
Alarm before acknowledgement.

Gallery 64 — Acknowledged Alarm

Screenshot:
Alarm after acknowledgement.

Voice:

“Acknowledgement tells the system that the operator has recognized the alarm. It does not necessarily mean that the underlying condition has disappeared.”


Lesson 6.4 — Historical Events

Gallery 65 — Event History

Screenshot:
Historical event list.

Voice:

“Historical events are particularly useful during disturbance analysis and troubleshooting.”


Gallery 66 — Filtering

Screenshot:
Filter by time/source/message.

Voice:

“Filtering allows the operator or engineer to reduce a large event list to the information relevant to the investigation.”


Practical Exercise 6

Gallery 67 — Simulated Protection Alarm

Screenshot:
Protection operation alarm.

Gallery 68 — Communication Alarm

Screenshot:
Communication alarm.

Gallery 69 — Breaker Change

Screenshot:
Breaker event.

Gallery 70 — Filtered History

Screenshot:
Filtered event list.

Task:

“Generate or simulate several events and verify their appearance, acknowledgement, timestamp and historical record.”


MODULE 7 — MEASUREMENTS, TRENDS AND PROCESS VALUES

Lesson 7.1 — Analog Process Values

Gallery 71 — Voltage

Screenshot:
Voltage display.

Gallery 72 — Current

Screenshot:
Current display.

Gallery 73 — Active Power

Screenshot:
P display.

Gallery 74 — Reactive Power

Screenshot:
Q display.

Gallery 75 — Frequency

Screenshot:
Frequency display.

Voice:

“Typical electrical measurements include voltage, current, active power, reactive power and frequency. These values provide the operator with an overview of the electrical condition of the substation.”


Lesson 7.2 — Units and Scaling

Gallery 76 — Engineering Units

Screenshot:
Example of value with unit.

Voice:

“Always verify the engineering unit and scaling. A technically correct numerical value can still be misleading if the scaling or unit is incorrect.”


Lesson 7.3 — Trends

Gallery 77 — Trend Configuration

Screenshot:
Trend configuration.

Gallery 78 — Runtime Trend

Screenshot:
Trend display.

Voice:

“Trends provide historical visualization of process values and can help identify changing operating conditions.”


Practical Exercise 7

Gallery 79 — Measurement Dashboard

Screenshot:
U, I, P, Q, frequency.

Task:

“Create a measurement display and configure at least one trend for an electrical quantity.”


MODULE 8 — USER MANAGEMENT AND SECURITY

Lesson 8.1 — Users and Groups

Gallery 80 — User Administration

Screenshot:
User management.

Voice:

“User management determines who can access the system and which operations each user is authorized to perform.”


Gallery 81 — Operator Group

Screenshot:
Operator group permissions.

Voice:

“An operator normally needs access to process monitoring and authorized operational functions.”


Gallery 82 — Engineer Group

Screenshot:
Engineering permissions.

Voice:

“Engineering users may require additional access for diagnostics and configuration.”


Gallery 83 — Administrative Access

Screenshot:
Administrator permissions.

Voice:

“Administrative access should be controlled carefully because it can affect the complete system configuration.”


Lesson 8.2 — Login/Logout

Gallery 84 — Login

Screenshot:
Login screen.

Gallery 85 — Logged-In User

Screenshot:
Runtime showing user.

Gallery 86 — Logout

Screenshot:
Logout action.


Practical Exercise 8

Gallery 87 — Permission Test

Screenshot:
Operator attempting restricted function.

Voice:

“Test the permissions rather than assuming they work correctly. Verify what each user can and cannot do.”


MODULE 9 — TIME SYNCHRONIZATION AND EVENT TIMESTAMPING

Lesson 9.1 — Why Time Matters

Gallery 88 — Event Timeline

Screenshot/diagram:

10:32:15.100  Protection Trip
10:32:15.120  Breaker Open
10:32:15.150  Alarm
10:32:15.200  Operator Acknowledgement

Voice:

“In substation automation, accurate timestamps are essential. During a disturbance, the sequence of events can be as important as the events themselves.”


Lesson 9.2 — Time Synchronization

Gallery 89 — NTP Architecture

Screenshot/diagram:

Time Source
    ↓
SICAM PAS
    ↓
SCC / IEDs

Voice:

“The station architecture should use a consistent time reference so that different devices report events using a common time base.”


Gallery 90 — Time Configuration

Screenshot:
Actual time configuration screen.


Gallery 91 — Timestamp Problem

Screenshot:
Events with inconsistent timestamps.

Voice:

“If timestamps are inconsistent, investigate the time source, synchronization status, timezone and device configuration.”


Practical Exercise 9

Gallery 92 — Timestamp Analysis

Screenshot:
Three or more events with different timestamps.

Task:

“Determine whether the event sequence is technically consistent and identify possible time synchronization problems.”


MODULE 10 — DIAGNOSTICS AND TROUBLESHOOTING

Lesson 10.1 — Troubleshooting Philosophy

Gallery 93 — Troubleshooting Flowchart

Screenshot/diagram:

Problem
 ↓
Identify Signal
 ↓
Check Source
 ↓
Check Communication
 ↓
Check PAS
 ↓
Check SCC
 ↓
Check Graphic
 ↓
Test

Voice:

“The most effective troubleshooting approach is systematic. We should move through the signal chain step by step rather than making random configuration changes.”


Lesson 10.2 — Breaker Status Not Updating

Gallery 94 — Problem Screen

Screenshot:
Breaker remains in old state.

Voice:

“Imagine that the physical breaker has changed state, but the SCC graphic has not changed.”


Gallery 95 — Check PAS

Screenshot:
PAS signal.

Voice:

“First, determine whether PAS receives the new state.”


Gallery 96 — Check SCC

Screenshot:
SCC process value.

Voice:

“If PAS contains the correct state but SCC does not, continue the investigation on the SCC side.”


Lesson 10.3 — Missing Measurement

Gallery 97 — Missing Measurement

Screenshot:
Blank/invalid value.

Voice:

“A missing measurement can result from the source device, communication, data processing, scaling or visualization.”


Gallery 98 — Measurement Trace

Screenshot:
Source → PAS → SCC.


Lesson 10.4 — Alarm Not Appearing

Gallery 99 — Missing Alarm

Screenshot:
Expected alarm absent.

Voice:

“Check whether the source condition exists, whether the signal reaches PAS, whether the message is correctly configured and whether the SCC alarm configuration is correct.”


Lesson 10.5 — Command Failure

Gallery 100 — Command Failure

Screenshot:
Failed control.

Voice:

“Command failures require a structured investigation. Check authorization, local or remote mode, communication, interlocking, command configuration and feedback.”


Lesson 10.6 — Communication Failure

Gallery 101 — Communication Diagnostic

Screenshot:
Communication status/diagnostics.

Voice:

“Communication diagnostics can help distinguish a process problem from a communication problem.”


Gallery 102 — Troubleshooting Checklist

Screenshot:

□ Source device
□ Communication
□ PAS
□ Process data
□ SCC data
□ Graphic
□ Alarm configuration
□ User permissions
□ Time synchronization

Voice:

“ ”


Practical Exercise 10

Gallery 103 — Fault 1

Breaker status not updating.

Gallery 104 — Fault 2

Measurement missing.

Gallery 105 — Fault 3

Alarm missing.

Gallery 106 — Fault 4

Command unsuccessful.

Gallery 107 — Fault 5

Incorrect timestamp.

Voice:

“For the troubleshooting exercise, investigate each fault systematically. Do not change multiple parameters at the same time. Identify the cause first, then make the correction and retest.”


MODULE 11 — COMPLETE PRACTICAL SUBSTATION PROJECT

This module should contain the largest number of screenshots because it becomes the main practical project of the course.

Lesson 11.1 — Project Definition

Gallery 108 — Final Project Architecture

Screenshot:

             SICAM SCC
                 |
             SICAM PAS
                 |
       IEC 61850 / Station Bus
                 |
     -------------------------
     |           |           |
 Incomer 1   Incomer 2    Feeder

Voice:

“We will now build a complete small substation SCADA project using the concepts introduced in the previous modules.”


Gallery 109 — Project Scope

Screenshot/table:

  • 2 bus sections
  • 2 incomers
  • 1 outgoing feeder
  • Breakers
  • Disconnectors
  • Measurements
  • Protection alarms
  • Communication alarms

Lesson 11.2 — Signal List

Gallery 110 — Signal List

Screenshot:
Engineering signal list.

Voice:

“Before building graphics, define the required process information. A clear signal list makes the engineering process much easier to control.”


Gallery 111 — Binary Signals

Screenshot:
Breaker/disconnector/status signals.


Gallery 112 — Analog Signals

Screenshot:
U/I/P/Q/frequency signals.


Gallery 113 — Commands

Screenshot:
Open/close commands.


Lesson 11.3 — Main Overview

Gallery 114 — Main SLD

Screenshot:
Complete overview.

Voice:

“This is the main operator overview. The operator should be able to understand the station topology and overall operating condition immediately.”


Gallery 115 — Bus Section 1

Screenshot:
First bus.

Gallery 116 — Bus Section 2

Screenshot:
Second bus.


Lesson 11.4 — Incomer Bay

Gallery 117 — Incomer 1

Screenshot:
Complete incomer bay.

Gallery 118 — Incomer 2

Screenshot:
Complete second incomer.


Lesson 11.5 — Feeder Bay

Gallery 119 — Outgoing Feeder

Screenshot:
Complete feeder.


Lesson 11.6 — Measurements

Gallery 120 — Complete Measurement Display

Screenshot:
All U/I/P/Q/frequency values.


Lesson 11.7 — Alarms

Gallery 121 — Protection Alarms

Screenshot:
Protection alarm list.

Gallery 122 — Communication Alarms

Screenshot:
Communication alarm list.

Gallery 123 — Combined Alarm View

Screenshot:
Complete alarm screen.


Lesson 11.8 — Control

Gallery 124 — Breaker Control

Screenshot:
Control dialog.

Gallery 125 — Command Feedback

Screenshot:
Successful feedback.


Lesson 11.9 — Users

Gallery 126 — User Configuration

Screenshot:
Users/groups.

Gallery 127 — Permission Test

Screenshot:
Restricted function.


Lesson 11.10 — Runtime Test

Gallery 128 — Runtime Overview

Screenshot:
Complete running system.

Gallery 129 — Bay Navigation

Screenshot:
Overview → bay.

Gallery 130 — Alarm Test

Screenshot:
Alarm appearing.

Gallery 131 — Control Test

Screenshot:
Breaker command.

Gallery 132 — Event History

Screenshot:
Historical events.


Lesson 11.11 — Communication Failure Test

Gallery 133 — Normal Operation

Screenshot:
Normal communication.

Gallery 134 — Communication Failure

Screenshot:
Failure condition.

Gallery 135 — SCC Response

Screenshot:
How SCC represents the problem.

Voice:

“An important part of commissioning is testing abnormal conditions. We should verify not only normal operation but also how the system behaves when communication or process information becomes unavailable.”


Gallery 136 — Recovered Communication

Screenshot:
System restored.

Voice:

“After restoring communication, verify that the system returns to the expected state and that no important information has been lost.”


MODULE 12 — COMMISSIONING AND FINAL PRACTICAL TEST

Lesson 12.1 — Commissioning Checklist

Gallery 137 — Commissioning Checklist

Screenshot:

□ Communication
□ Process data
□ Breaker status
□ Disconnector status
□ Measurements
□ Alarms
□ Events
□ Commands
□ Feedback
□ Time synchronization
□ User permissions
□ Graphics
□ Documentation

Voice:

“This checklist summarizes the main commissioning activities.”


Lesson 12.2 — Communication Test

Gallery 138 — Communication Test

Screenshot:
Communication status.

Voice:

“First verify that communication is healthy and all required process information is available.”


Lesson 12.3 — Status Test

Gallery 139 — Switchgear Status Test

Screenshot:
Breaker/disconnector states.

Voice:

“Test every important switchgear indication under normal and changing conditions.”


Lesson 12.4 — Measurement Test

Gallery 140 — Measurement Verification

Screenshot:
U/I/P/Q/frequency.

Voice:

“Verify the value, unit, scaling and quality of each important measurement.”


Lesson 12.5 — Alarm Test

Gallery 141 — Alarm Test

Screenshot:
Alarm appearing.

Voice:

“Generate the required alarm conditions and verify message text, priority, timestamp and acknowledgement.”


Lesson 12.6 — Command Test

Gallery 142 — Command Test

Screenshot:
Control dialog.

Voice:

“Test each authorized command and verify the corresponding process feedback.”


Lesson 12.7 — Time Test

Gallery 143 — Time Synchronization

Screenshot:
Time/status.

Voice:

“Verify that the SCC, PAS and relevant devices use a consistent time reference.”


Lesson 12.8 — User Permission Test

Gallery 144 — User Test

Screenshot:
Different user permissions.

Voice:

“Verify that each user group has exactly the required access.”


FINAL PRACTICAL TEST

Gallery 145 — Final Test Introduction

Screenshot:

FINAL PRACTICAL TEST
Diagnose and Correct Five SCADA Problems

Voice:

“We have now reached the final practical test. You will investigate several intentionally introduced problems in the SICAM SCC project.”


Gallery 146 — Problem 1

Screenshot:
Breaker status problem.

Task:

“Determine why the breaker status is not updating.”


Gallery 147 — Problem 2

Screenshot:
Missing measurement.

Task:

“Trace the missing measurement from the source to SCC.”


Gallery 148 — Problem 3

Screenshot:
Missing alarm.

Task:

“Determine why the expected alarm does not appear.”


Gallery 149 — Problem 4

Screenshot:
Failed command.

Task:

“Determine why the operator command is unsuccessful.”


Gallery 150 — Problem 5

Screenshot:
Timestamp problem.

Task:

“Analyze the event sequence and identify the time synchronization problem.”


COURSE SUMMARY

Gallery 151 — What We Covered

Screenshot:

SICAM SCC
    ↓
Engineering
    ↓
PAS Integration
    ↓
Graphics
    ↓
Control
    ↓
Alarms
    ↓
Measurements
    ↓
Security
    ↓
Time Synchronization
    ↓
Diagnostics
    ↓
Commissioning

Voice:

“In this course, we have moved from the fundamentals of SICAM SCC to a complete practical substation SCADA project.”


Gallery 152 — Complete Architecture

Screenshot:
Final polished architecture:

               OPERATOR
                   |
              SICAM SCC
                   |
              SICAM PAS
                   |
        IEC 61850 / Station Bus
                   |
       ------------------------
       |          |           |
      IED        IED         IED
       |          |           |
       -------- Electrical ----
             Process

Voice:

“The most important concept to remember is that SCC is part of a complete system. When troubleshooting, always understand the complete path from the physical process to the operator interface.”


Gallery 153 — Practical Engineering Philosophy

Screenshot:

Don’t only configure the screen.
Understand the complete signal path.

Voice:

“Good SCADA engineering is not simply about creating attractive screens. It requires understanding process information, communication, control, alarms, timestamps and diagnostics.”


Gallery 154 — Final Message

Screenshot:

From IED Data
to PAS
to SCC
to Operator

Complete Substation SCADA Engineering

Voice:

“You should now have a practical understanding of how SICAM SCC fits into a substation automation system and how to approach engineering, testing and troubleshooting in a structured way.”


RECOMMENDED GALLERY NAMING SYSTEM

To keep your Elec-Engg course easy to maintain, I recommend naming the actual uploaded Gallery images consistently.

For example:

SCC-M01-L01-01-Course-Title
SCC-M01-L01-02-SCC-Main-Screen
SCC-M01-L01-03-Signal-Path

SCC-M01-L02-01-SA-Architecture
SCC-M01-L02-02-Bay-Level
SCC-M01-L02-03-Station-Level

SCC-M03-L01-01-PAS-SCC-Architecture
SCC-M03-L01-02-Process-Information
SCC-M03-L01-03-Breaker-Status

SCC-M04-L01-01-Graphics-Designer
SCC-M04-L01-02-New-Process-Picture
SCC-M04-L01-03-Basic-Objects

This makes it much easier to replace or update a screenshot later.


RECOMMENDED VIDEO PRODUCTION FORMAT

For each lesson, use this sequence:

1. Introduction Screenshot

Show the lesson title.

  • :
  • In this lesson, we will learn…”
  • Before working with the software, it is important to understand…”
  • Record the actual mouse operation.
  • “Pay attention to this section…”
  • “Now I will create/configure/test…”
  • “This is the final result…”
  • “Now let’s introduce a problem and see how we can diagnose it…”
  • “Now it is your turn. Repeat this procedure…”


SCREENSHOT TYPES TO CAPTURE

For the actual production of the course, I would divide screenshots into five categories.

A. Concept Screenshots

Used for explaining architecture:

  • SICAM SCC architecture
  • PAS/SCC relationship
  • Station/bay level
  • Signal flow
  • Troubleshooting flow

B. Engineering Screenshots

Actual configuration:

  • Project creation
  • WinCC Explorer
  • Graphics Designer
  • Alarm Logging
  • User Administration
  • Process information
  • Communication
  • Time configuration

C. Runtime Screenshots

Actual operator experience:

  • Main overview
  • SLD
  • Bay screen
  • Breaker status
  • Measurements
  • Alarm list
  • Event list
  • Control dialog
  • Trends

D. Diagnostic Screenshots

Very important for your practical style:

  • Communication failure
  • Missing signal
  • Bad quality
  • Failed command
  • Incorrect timestamp
  • Missing alarm
  • Wrong status
  • User permission problem

E. Practical Exercise Screenshots

Use screenshots showing the target result, rather than giving the entire answer.

For example:

Exercise: Create the following bay screen.

Then show the target SLD.

The learner performs the configuration independently.


FINAL PRODUCTION TARGET

The complete course can therefore contain approximately:

ModuleApprox. Gallery Screenshots
1. Fundamentals11
2. Engineering Environment8
3. PAS–SCC Integration11
4. Graphics & SLD16
5. Control11
6. Alarms & Events13
7. Measurements9
8. Security8
9. Time Synchronization5
10. Troubleshooting15
11. Complete Project29
12. Commissioning8
Final Practical Test/Summary10
Total~153 Gallery items

You do not need 153 separate videos. Many Gallery images can be displayed inside the same lesson while you record one continuous narration.

The most important part is that the real SCC screens, PAS screens and practical project screenshots become the core of the course, while the conceptual diagrams are used only where they make the engineering easier to understand.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top