The SCADA Data Source Model

e-terracontrol | Module 7

GRID
Topics

Data Sources
Data Sets
Data Items
Pseudo Points

e-terracontrol | The SCADA Data Source Model | P2

The Data Source Hierarchy
Data Source

Comm State*

Comm Error Count*

Data Set

Data Item

Comm State*

Comm Error Count*

* Pseudo points (internally sourced)

e-terracontrol | The SCADA Data Source Model | P3
Types of Data Sources (1 of 3)

Each measurement kept by the SCADA Server must have

one or more data sources.
There are four types of data sources:
Device Application
ISD Application
Calculation Module
Remote SCADA

e-terracontrol | The SCADA Data Source Model | P4

Types of Data Sources (2 of 3)

Device Application
An application that loads data via a data set configuration
(e.g. PLCReader, CFEReader, ICCP)
An EMP FEP will use the CFEReader to gather data from
field
ISD Application
An application that uses the ISD control and associated
protocol to set measurement values & quality.
An EMP FEP will use the Intersite Data app respond to
EMP polls

e-terracontrol | The SCADA Data Source Model | P5

Types of Data Sources (3 of 3)

Calculation Module
A dynamic link library containing routines to process input
measurements into output measurements
An EMP FEP will most likely not be concerned with these
Remote SCADA
Another SCADA server that can poll for data and issue
commands
Each EMP FEP can report to one of these such that the
EMP may communicate with only one redundant set of
FEPS

e-terracontrol | The SCADA Data Source Model | P6

The Data Source Object

In addition to a type, a Data Source has the following

attributes:
Name(s): Two to provide redundant sources and enable
line switching
Alarm processing behavior for: (not supported yet)
Connect to source
Disconnect from source
Priority (for measurements with redundant sources)
Good value from highest priority source chosen for display
Calculation module
Only if type is calculation
Refers to dynamic link library that contains the calculation functions

e-terracontrol | The SCADA Data Source Model | P7

Types of Data Sets

Data Sets represent the infrastructure between the source

application and the actual measurement.
Each type of data set has its own parameters to
communicate to the application about how to gather data
at the level of the data set.
Source applications can each be coded to look for their
own data set types and condition processing based on
the associated data set parameters. For example:
CFEreader, Modbus and ICCP apps use different
Dataset types.

e-terracontrol | The SCADA Data Source Model | P8

The Data Set Object

In addition to a name & type, a Data Set has the following

attributes:
For data set objects which directly own data items:
Data item initial index
Data item count
Unique parameter/value pairs dependent on type of data
set
Pseudo point directives with respect to duality
How to measure status of dataset
How to measure communication error counts for data set
Assigned areas of responsibility

e-terracontrol | The SCADA Data Source Model | P9

The Data Item Object

Data Items are associated with measurement or control

objects.
Correspond to the physical connections in the RTUs,
PLCs, and IEDs.
Linked by name to measurement or control in the
measurement model

e-terracontrol | The SCADA Data Source Model | P10

Measurement-specific dataitem parameters

Analog, scaling values much like with measurements

Raw/engineering high/low values for interpolation
Raw deadband value for reporting to server
Analog scale type for multi-segment linear scaling
Status Point bit identifier (1 data item per bit)
S: this is the normal status bit for a two-state device.
X: this is a 3 or 4-state device using a two-bit value.
M: this is the MCD bit.
Sinv: this is the normal status bit but it can be inverted before
doing any calculations. Applies to 2-state points; flips the S-
bit.
Accumulator scaling values much like with measurements.
Multiplier: scaling, converting counter difference between
reads to engineering units.
Rollover point: maximum count before rolling over to zero.
e-terracontrol | The SCADA Data Source Model | P11
Specifying Reporting for Multi-State Devices

e-terracontrol supports complete flexibility in mapping of

two-bit combinations coming from a multi-state status
point device measurement into the decimal values
0,1,2,3.
Mechanism: X bit identifier on data item object:
Xn1n2n3n4
Where:
n1 = decimal value to report for 00 bit combination
n2 = decimal value to report for 10 bit combination
n3 = decimal value to report for 01 bit combination
n4 = decimal value to report for 11 bit combination

e-terracontrol | The SCADA Data Source Model | P12

CFEReader Data Sets

Datasets

CFEReader
These are all
CFE types of data sets
Port that are
hierarchically
RTU related, each with
their own data
ScanGroup
properties as seen
Card in the following
slides.
Bucket Data Items

TimeDevice Item 0

Item 1

e-terracontrol | The SCADA Data Source Model | P13

CFEReader Data Sets
Related to COMTOP Records
Datasets
These are all types of data
CFEReader sets that correspond to records
CFE
in the communications
topology in SCADAMOM and
Port represent the front-end
RTU
software and hardware.

ScanGroup

Card

Bucket Data Items

TimeDevice Item 0

Item 1

e-terracontrol | The SCADA Data Source Model | P14

CFEReader Data Sets
Related to RTUTOP Records
Datasets

CFEReader

CFE

Port These are all

types of data sets
RTU
that correspond to
ScanGroup records in the RTU
topology in
Card SCADAMOM and
Data Items
represent the field
Bucket
devices.
TimeDevice Item 0

Item 1

e-terracontrol | The SCADA Data Source Model | P15

CFEReader Data Set

Represents the CFEReader application.

Defines the global settings of a CFE Reader application such as:
Heart beat rate
Exploratory scan rate
Time bias test rate
RTU Synchronization rate
For e-terraplatform users, it corresponds to the TFE record.
Note: More than one CfeReaderDataSet may be generated for
the same TFE record since one CfeReaderDataSet is
generated for each NETSRV referenced by a CHANEL under
a TFE record.
One instance of the CFE Reader application must be
started for each CfeReaderDataSet.
e-terracontrol | The SCADA Data Source Model | P16
CFE Data Set

Contains the configuration parameters for a CFE.

In the communications hierarchy, it is a child of the
CfeReaderDataSet .
For e-terraplatform users, it corresponds to the CHANEL
record type.

e-terracontrol | The SCADA Data Source Model | P17

Port Data Set

Contains the configuration parameters for a Port (either

COM or TCP/IP).
Contains port-specific parameters such as:
Baud rate for communications
Protocol-type for communications with field devices
Contains modem parameters such as:
Protocol-specific timeout values
no-reply timeouts
interbyte gap timeouts
In the communications hierarchy, it is a child of the CfeDS
For e-terraplatform users, it corresponds to the PATH
record type
e-terracontrol | The SCADA Data Source Model | P18
Dialup and Modem Data Sets

DialupDS contains the configuration parameters for a

dialup master port.
ModemDS contains the configuration parameters for a
dialup modem port.
Dialup ports (DialupDS and ModemDS) must be modeled
under a separate CfeDS from non-dialup ports (PortDS).
In the communications hierarchy, they are children of the
CfeDS.
For e-terraplatform users, it corresponds to the PATH
record type

e-terracontrol | The SCADA Data Source Model | P19

RTU Data Set

Contains the configuration parameters for an RTU or other

field device.
Contains RTU-specific parameters such as:
RTU type
MCD support
Freeze/activate addresses
In the communications hierarchy, it is a child of the PortDS.
For e-terraplatform users, it corresponds to the RTU and
RTUC record types.

e-terracontrol | The SCADA Data Source Model | P20

DRTU Data Set

Contains the configuration parameters for a dialup RTU or

other field device.
In the communications hierarchy, it is a child of the Dialup
or Modem Data Set.
For e-terraplatform users, it corresponds to the RTU and
RTUC record types.

e-terracontrol | The SCADA Data Source Model | P21

Scan Group Data Set (1 of 2)

Contains the configuration parameters for a Scan Group

within an RTU.
Scan Groups are of two basic types
Periodic: in which case, the state of the group contributes
to state of parent RTU, Port, etc.
Non-periodic: in which case, the state of the group does
not contribute to state of parents

e-terracontrol | The SCADA Data Source Model | P22

Scan Group Data Set (1 of 2)

Contains scan group-specific parameters such as:

Periodic scan rate
Integrity scan rate
Number of retries on scan error
In the communications hierarchy, it is a child of the RtuDS
or DrtuDS.
For e-terraplatform users, it corresponds to the ADRS
record type.

e-terracontrol | The SCADA Data Source Model | P23

Card Data Set

Contains the configuration parameters for an RTU Card.

Cards are the owners of data items and, as such, contain:
Initial item index
Data item count
In the communications hierarchy, it is a child of the
ScanGroupDS.
For e-terraplatform users, it corresponds to the CARD
record type.

e-terracontrol | The SCADA Data Source Model | P24

Bucket Data Set

Defines up to 16 custom counters for errors to be reported

at an RTU or Scan Group level. By default the
scangroup counts CRC and NoReply errors. Typically
the bucket record counts Other types of errors.
For e-terraplatform users, it corresponds to the BUCKET
record type.

e-terracontrol | The SCADA Data Source Model | P25

Time Device Data Set

Identifies a time device when it is defined as a child record

of a CFEreader dataset
Supports TrueTime card or PC Clock when defined with
the names TIME590X or PCCLOCK
Poll rate is specified in the CFE reader time device display,
default value is 60 seconds
On the EMS, this is related to the CHANEL record

e-terracontrol | The SCADA Data Source Model | P26

 End of module 7
Next module :
EMSP009_08_I_eterracontrol_iec61850_Alstom_2011.03.07_.ppt

e-terracontrol | The SCADA Data Source Model | P27