Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
ControlSystemsDesigninIndustrialProcessPlants
Author: Mark Grant
Whats Inside
1. Load Shedding System (LSS)
2. Elecsolve Power Modeling
3. Event Disturbance Record System
4. References
LoadSheddingSystem
LoadSheddingSystem
LoadSheddingSystem
LoadSheddingSystem
LoadSheddingSystem
The functionalities of the Master Station are achieved through the following components:
The LSS Master Station is integrated into the Invensys Generation Management System on the ArchestrA Application
Platform environment
The main LSS logic runs within the ArchestrA objects on a dedicated Application Engine
The Configuration of the LSS is provided by the Foxboro IDE (Integrated Development Environment)
The LSS History data functions are provided by Foxboro SCADA/GMS Historian
The LSS Alarm functions are provided by Foxboro SCADA/GMS Alarm System
Data communication to Main controller and Local controllers is implemented via DNP protocol on Ethernet
The load shedding detection algorithm runs every 10 milliseconds. When the load shed condition is detected, a predetermined matrix of truth tables is searched for the correct load shed sequence to follow.
Once the load shed sequence has been determined (within 10 msec of the event), a dedicated message will be
broadcast to all of the LSS Local Controllers in the other substations using a dedicated fiber network. Using a dedicated
fiber network is critical to maintain less than 100 millisecond response from event recognition to substation actions such
as opening breakers, shutting down motors, etc Each local controller shall receive an index which is used locally in
each local controller to determine which relays to operate. In order to maintain a level of redundancy good,
engineering practice defines that each local load shed controller in each substation shall run the algorithm redundantly.
It, therefore, provides the local trip signals to the local breakers according to the pre-determined load shed sequence.
Foxboro SCD5200
6
LoadSheddingSystem
LoadSheddingSystem
LoadSheddingSystem
The load shedding matrix is a set of truth tables that are designed to develop a set of instructions that drive opening of certain
relays down to feeder relays to each process area. Load shedding scope is to assure loads at the plant are maintained related to tie
lines or generator trips. These are typically encountered when power demand exceeds available supply. Under frequency control is
critical during islanding to minimize the chances of total facility blackout.
The following diagram (Vuan, Hernandez, and Mattos) shows various tie lines and feeders from a pulp and paper mill. These feeders
are directed at specific plant areas and decisions can be made to shut down specific processes by opening up various feeders.
Decisions are typically made prior to installation.
Pre-installation studies on load situations can be run prior to the implementation of the load shedding matrix tables. This is done in
some cases using simulators but plant information such as the list below should be considered during creation of the matrix
algorithm.
ElecsolvePowerModeling
2.2 Introduction
During the engineering stage, power generation and plant system simulators are utilized to test the control system capability and
effectiveness, as the actual field devices are not available in the engineering staging facilities and actual system response is thus
unknown. An example for electrical system simulator can be used to simulate a system disturbance (such as loss of a generator), the
following system condition will occur.
Local controller of on line generators (Generator controller) act to increase the generator output to meet power
demand, due to frequency or voltage drop in the system.
Load Management System Load Shedding Control acts to shed non-critical load to ensure sufficient power supply for
Train operation.
Based on the transient of the system, Load Management Shedding Power Generation Control acts on generator and
OLTC to ensure desired load sharing among all power sources, and to maintain system frequency and bus voltage
(when islanded) or to maintain grid import power (when connected to grid).
The system eventually stabilized at its new set points.
EventDisturbanceRecordSystem
The functionality of the simulator used during testing and commissioning can be extended to become a fully fledged Operator
Training Simulator (OTS). In addition to the full feature of classroom training system, the emphasis is to have the simulation system
behave exactly the same as actual hardware and software. The operator will be able to practice the routine operation procedure,
such as opening and closing of a circuit breaker, as well as advanced operation, such as power generation control, load shedding
control and synchronization operation.
2.5 Elecsolve
ElecSolve software adds a DYNSIM library for modeling three phase electrical networks. The solver algorithms make the following
important assumptions:
Phases are balanced.
Electromagnetic transients happen much faster than solver time steps.
These assumptions provide the ability to solve networks while neglecting electromagnetic transients and out of balance currents.
The solver works out a steady state electrical solution at every time step given boundary conditions form the generators and loads.
The electromechanical dynamics are represented in first principles. The complex impedance of each component and transmission
line is taken into account.
The library has two co-operating solvers:
The Power Flow solver calculates a consistent set of voltages for the network that satisfies the voltage and load
boundaries.
The Machine Dynamics solver - integrates synchronous machine and voltage controller states to solve machine speeds
and AVR dynamics.
At each DYNSIM calculation step the power flow solver is executed before the machine dynamics solver. At the end of the step we
arrive at a consistent set of bus voltages, power flow and machine speeds.
EventDisturbanceRecordSystem
Local RTU. This significantly minimizes costs from GPS clocks and wiring. Since the local RTU holds the time synchronized data it is
also available at the Master SCADA Station. It is typically recommended that the time synchronized data be made available
manually or on detection of an event.
The Event Disturbance Record System utilizes the DNP3 event system to collect information from various Intelligent Electrical
Devices (IED) into the SCD5200 RTU Station Control Devices. As events occur, these are collected and then transferred to the master
station, where the events are recorded in the standard Historian and Alarm Database.
Each Local RTU records the events independently in the SCD5200 and sends the data to the centralized Historian for permanent
storage. The data points and event definition are configured in SCD5200 as well as in the Integrated Development Environment
(IDE) and Historian.
The Historian collects data associated with events. In many cases the Historian is not on the same computer as the post event
package although all the points associated with a particular event have to be in the same historian server.
3.2.1 Overview
The Post Event Report package is a decision support tool which aids in the analysis of system operations before and after an event.
An event can be defined as any data point monitored by the system, either internal in the control system, or in the process,
production, or SCADA system. Examples of the types of data which are monitored include equipment going offline or a unit trip or
a breaker trip.
A Post Event Report package will generate a report based on the historical data related to the event from the historian database. For
example, after a boiler goes off line, the user will be able to inquire about the history of its temperature, pressure, electricity usage,
and other variables for the moment immediately before it went down.
The report generation is executed automatically by an ArchestrA object. The reports are saved in pre-defined location for any users
to access. The configuration attributes of the Post Event Report object are described in detail in Table 1.
An ArchestrA object tool is an ideal way to manage a package of information. The ArchestrA object is designed to include all the
User Defined Attributes associated with the Post Event Report package. The object is assigned to each device and should the report
need to be changed, the change can be made in the object template and deployed to any combination of the devices. This
provides a huge advantage to the user in terms of (a) lowering the risk or errors in matching of tags to reports and historian event
database; (b) lowering the cost to make the engineering changes; and (c) creating consistent reports from engineer to engineer by
virtue of an approved template that is accessed by in a template toolbox.
12
EventDisturbanceRecordSystem
Attribute
Description
PreEventInterval
The time in minutes that the history data should be included in the event report
before the event occurred. Default value is 10.
PostEventInterval
The time in minutes that the history data should be included in the event report
after the event occurred. Default value is 10.
EventReportPointNames
A group of InSQL Historian tag names that are included in the event report. The
user shall make sure that these names are valid tag names in InSQL database.
EventSearchStartMinute
It is used for the program to set up a time range to search for event in the InSQL
Event History database. The start minute is the time in minutes from the start of
the program execution. Normally it could be set to 10 to 15.
EventSearchEndMinute It is used for the program to set up a time range to search for event in the InSQL
Event History database. . The end minute is the time in minutes from the start of
the program execution. Normally it can be set to 0 (meaning the search ends at
the current time).
InSQLEventTagName
InSQLServerName
InSQLUserName
InSQLPassword
ReportFolderName
2012 Invensys Systems, Inc. All rights reserved. Avantis, Eurotherm, Foxboro, InFusion, Invensys, SimSci-Esscor, Triconex, Validation Technologies and Wonderware are
trademarks of Invensys plc, its subsidaries and affiliated companies. All other product names are the trademarks of their respective holders.
13