SPC Data Model

Spectrum PowerTM 7
DATA MODELING (SCADA)
Restricted © Siemens AG 2015 All rights reserved. Answers for infrastructure and cities.
Page 1
Spectrum PowerTM 7
Data Modeling (SCADA)
• Spectrum Power 7 Data Model

• Realtime (RT) Instances Tree
• SCADA Only Tree
• Companies Tree
• IMM Types
Restricted © Siemens AG 2015 All rights reserved.

Page 2
Spectrum Power 7 Data Model
Types & Instances
Types e.g. Type: BusbarSection (defined as part of the product) includes a list of
Attributes that describes a busbar & Associations to other types
Attributes HighVoltageLimit, LowVoltageLimit, OnelineDisplayName, Scada B3Number, etc.
Properties EquipmentMemberOfVoltageLevel
Associations
Instance • Objects of the real world;

• Objects which describe parts of the electrical network (for e.g.,
“objects created
a specific transformer or a specific switch, and so on)
from the Type • Customer entered data
definitions”

Page 3
Instance Path
Instance Path /Network/Companies/Europe/ZONE_1/Vienna/33/BB1A
• Network is an instance of type sysNetworkCategory. It is sometimes called a folder instance as its

main purpose is to be a container of other instances.
• Companies is an instance of type sysNetCompanies. This folder instance contains most of the in-
stances that define the power system.
• Europe is an instance of type GeographicalRegion. This is a folder instance and it also contains
attrib-utes of its own, such as Interchange Control Priority. GeographicalRegion is the CIM 12 name
for Company.
• ZONE_1 is an instance of type SubGeographicalRegion. Many engineers refer to this as type Zone.
• Vienna is an instance of type Substation. A SubGeographicalRegion normally contains many Substa-
tion instances.
• 33 is an instance of type VoltageLevel. The equipment of a substation that is operating at a voltage

level of 33 KV are contained within this VoltageLevel instance.
• BB1A is an instance of type BusbarSection. This instance contains many instances of many types
that describe the measurements that are collected about BB1A instance.
• When an instance is moved, its path changes.

Page 4
Instance Path
Identifiers of Busbar GUID: {00165A66-863C-47B8-AB9A-43E0978F3848}

Instance
ObjectId: 665A16003C86B847AB9A43E0978F3848 Note, ObjectID

is the same ID as the GUID displayed, using its internal format of a
16 byte RAW value.
Siemens internal identifier – siid or iid: 38295
RDFID: _00165A66-863C-47B8-AB9A-43E0978F3848

Page 5
Instance Path
Europe
Ancestors of the BB1A BusbarSection instance

ZONE_1
• Grandparent of the
Vienna BB1A BusbarSection
instance
• Parent of the BB1A

33 BusbarSection instance
• Child of 33
BB1A VoltageLevel instance
•A parent instance may contain immediate child instances and also adopted child instances. Immediate children are
directly below the parent in the IMM path. Adopted children are related to the parent through another link

Page 6
Spectrum PowerTM 7

• SCADA Only Tree
• Companies Tree
• IMM Types

Page 7
Realtime (RT) Instances Tree
General – SCADA Tree & Network Tree

Page 8
Realtime (RT) Instances Tree
Application Flags
True => Data populated into corresponding database

Application Flags Boolean attributes
False => Data not populated/ remove from corresponding
database
SCADA Flag Controls the inclusion or exclusion of instances from the SCADA online database
AGC Flag Controls the inclusion or exclusion of instances from the AGC online database
NA Flag Controls the inclusion or exclusion of instances from the TNA online database
DMS Flag Controls the inclusion or exclusion of instances from the CDNA online database

Page 9
Spectrum PowerTM 7

• SCADA Only Tree
• Companies Tree
• IMM Types

Page 10
SCADA Only Tree
SCADA TA Hierarchy
SCADA Flag = True and NA Flag = False

Page 11
SCADA Only Tree
SCADA TA Hierarchy
Network Image (NIM)
• Blocks (stations, voltage levels, bays, network components)

• Element (circuit breakers, disconnects, measuring points, and so on)
• Info (statuses, analog values, quality codes, and so on)

Page 12
SCADA Only Tree
SCADA TA Hierarchy
Five-level combination (B1/B2/B3/Element/Info) is

referred as the technological address or TA

Page 13
SCADA Only Tree
SCADA TA Hierarchy
Note:
 Possible to have measurements and info's that pertain to a substation or voltage level,
i.e., elements can be defined directly under a B1 or B2
For example:
 B1/null/null/Element/Info (e.g., measurement of the substation)
 B1/B2/null/Element/Info (e.g., example, measurement of the voltage level)
Note:
 Each block is identified by both a name and an internal number.
 The names are called B1Name, B2Name and B3Name and their value is assigned by
the user, and may be changed.
 In IMM, these are the ODB Names. The block numbers are called B1Number,
B2Number, and B3Number
Note:
 An element is also identified by the Nimset internal number.
 These internal numbers are assigned and maintained internally by IMM.
 Migrated data may assign these internal numbers through import; but if they violate the
uniqueness constraint they will be re-assigned and a warning message is written to the
import log

Page 14
SCADA Only Tree
Operational Database Name (ODB)
Note:
 Instance names in IMM can be 255 characters long.
 Block names in the SCADA TA are limited to 8 characters
 Operational Database Name or ODB name is set to the first 8 characters of the instance name
Uniqueness constraints on the values of the ODB Names
• For B1 level types (for example, Substation, InternalControlArea, ThermalPowerPlant, B1Block, and
so on), the ODB name must be unique across all B1 instances.
• For B2 level types (for example, VoltageLevel, B2Block, and so on), the ODB name must be unique
within its parent B1.
• For B3 level types (for example, BusbarSection, PowerTransformer, ACLineSegment, and so on),
the ODB name must be unique within its parent B1 B2 combination.

Page 15
SCADA Only Tree
SCADA TA Hierarchy versus IMM Instance Path
The SCADA TA is a portion of the full IMM instance path
For example, in the following instance path the TA portion in blue and bold is the SCADA TA
B1/B2/B3/Element/Info:
Multiple IMM instances together map to one SCADA element
For example, in the following instance path the first CB is the Breaker instance and the second
CB is the Discrete instance:
IMM Instance: IMM Instance:

Breaker Instance Discrete Instance
SCADA
Element

Page 16
SCADA Only Tree
SCADA TA Hierarchy versus IMM Instance Path
For some types, the location of an instance in the IMM path is different than it’s level in the SCADA TA
 For example, PowerTransformer's are children of Substations in IMM, but in the SCADA TA, PowerTransformer's
are a B3 under a B2 of VoltageLevel.
 To provide a means of defining this alternate parent/child SCADA TA relationship, an association called the
HasForScadaParent association exists for the relevant types.
 A link for each instance of these identifies the parent instance to be used for the SCADA TA
 The following figure shows the PowerTransformer instance
/Network/Companies/Europe/ZONE_1/Vienna/110_cmpTR11 and it's link for association Has For Scada Parent
(VoltageLevel) to the IMM sibling VoltageLevel instance /Network/Companies/Europe/ZONE_1/Vienna/110
Chapter 6.1 Overview contains a useful table that indicates which IMM types correspond to the SCADA TA
Hierarchy B1 B2 B3 Element and Info levels. It also indicates which types need a link for the
HasForScadaParent association

Page 17
SCADA Only Tree
Search by TA
B1, B2, and B3 fields are B1, B2, and B3 fields are searched in
searched in Operational B1Number, B2Number, and B3Number
Database Name Attribute… attributes. The Elem field is searched in
Elem and Info fields are the ElementName (which is a number)
searched in the Instance attribute The Info field is searching the
Name InfoNumber attribute

Page 18
SCADA Only Tree
ODB Tab on IMM UI
 It displays a subset of the attributes

and associations that exist for the ODB Tab for BusbarSection named BB2B
type, including some internal and read-
only attributes.
 The attributes included are relevant to
SCADA.
 The user may edit data in any of the
tabs

Page 19
Spectrum PowerTM 7

• SCADA Only Tree
• Companies Tree
• IMM Types

Page 20
Companies Tree
Overview
 Color coding of the type name depicts which types are SCADA block levels of B1 (blue), B2 (green) or B3 (red)

Page 21
Companies Tree
GeographicalRegion and SubGeographicalRegion

Page 22
Companies Tree
Substation

Page 23
Companies Tree
SCADA Flag
 Many IMM types have SCADA Flag

e.g. B1, B2, and B3 level, switch types and TransformerWinding's
 Only those with SCADAFlag of true will be activated into the Operational Database.
 User sets the SCADAFlag & the default value for SCADAFlag is False
 Other IMM types have an Internal SCADA Flag attribute.

e.g. Element and Info level, and Terminal's, ConnectivityNode's, Calculation's and Operand's.
 IMM sets the value of the InternalScadaFlag based on the value of SCADAFlag on the ancestor instance

Page 24
Companies Tree
SCADA Flag
 Changing SCADAFlag from True to False cascades down to all descendants, i.e., the SCADAFlag
and InternalScada flag on all descendants will also be set to False
 On job activation, these instances will be deleted from the Operational.
 On job finalization, the B1, B2, and B3 numbers, that were used by the deleted instances will be freed
up and available for reuse.
 Nimset numbers are also freed but the number is not re-used once a nimset was activated to ODB
because it is a key value used by historical data.
 If any other subsystems links to a deleted instance, that link is also deleted
 Changing SCADAFlag from True to False cascades down to all descendants, i.e., the SCADAFlag
and InternalScada flag on all descendants will also be set to False.
 This SCADAFlag change to true cascades down to descendants with InternalScadaFlag but does NOT
cascade down to descendants with SCADAFlag.
 This means, the user must explicitly change the SCADAFlag on desired child instances.
 Also, the user must explicitly link up other applications to the desired SCADA info’s using the
associations listed above
 If user mistakenly changed the SCADAFlag from True to False, then the job should be erased to
restore the instances to their original state

Page 25
Spectrum PowerTM 7

• SCADA Only Tree
• Companies Tree
• IMM Types

Page 26
IMM Types
B1 Level Types
B1 Types
B1Block
Substation
HydroPowerPlant
InternalControlArea
ThermalPowerPlant
...

Page 27
IMM Types
B1 Level Types
Attributes for B1 Level Types
Attribute Data Type Required Default/Int Notes

ernal
SCADA Flag Boolean Yes False Must be True for an instance to be part of SCADA.
ODBName String 8 Yes Yes ODB stands for Operational Database Name.
The ODBName is the B1Name in the SCADA TA hierarchy. This value must
be unique across all B1 level instances.
An error message will be issued, if a duplicate B1Name is entered. The
default is the first 8 characters of the instance name.
B1Number Long Yes Internal Unique value assigned by IMM.
LogbookText String 20 No Yes In the SCADA ODB, this is the B1Text whose length is 7 characters. The
default in IMM is the first 7 characters of the instance name.
BlockType Enum Yes No Required when SCADAFlag is True. User must select the desired BlockType
from the drop-down list based on enumeration EnumB1BlockType.
AreaOf Enum Yes Yes Also called Technological Area. User selects from the dropdown list. The
ResponsibilityId default is Syst40Bs (1). When the AreaOfResponsibilityId value is changed
on a B1, the new value is assigned to all descendents whose value matches
the old B1 value.

Page 28
IMM Types
B1 Level Types
Association used for B1 Types
Association Required Notes

Uses Global (InterlockDecisionTable) No
Uses Local (InterlockDecisionTable) No
Note
 When a B1 level instance is inserted, a child Discrete named Bl Spec is
automatically inserted by IMM when SCADAFlag is true

Page 29
IMM Types
B2 Level Types
B2 Types
B2Block
TiePoint
VoltageLevel
LFCDynamicSchedule
ThermalGeneratingUnit
HydroGeneratingUnit
VirtualUnitGroupThermal
VirtualUnitGroupHydro
...

Page 30
IMM Types
B2 Level Types
Attribute Data Type Required Default/Int Notes

ernal
The ODBName is the B2Name in the SCADA TA hierarchy. This
value must be unique across all B2 level instances that are
children of the same B1 instance. This includes adopted siblings
using a HasForScadaParent link. An error message will be
issued if a duplicate B2Name is entered.
The default is the first 8 characters of the instance name.
B2Number Long Yes Internal Unique value within the parent B1 assigned by IMM.
LogbookText String 20 No Yes In the SCADA ODB, this is the B2Text whose length is 3
characters. The default in IMM is the first 3 characters of the
instance name.
BlockType Enum Yes No Required when SCADAFlag is True. User must select the desired
BlockType from the drop-down list based on enumeration
EnumB2BlockType.
AreaOf Enum Yes Yes Also called Technological Area. User selects from the dropdown
ResponsibilityId list. The default is the value of parent B1’s
AreaOfResponsibilityId.
When the AreaOfResponsibilityId value is changed on a B2, the
new value is assigned to all descendents whose value matches
the old B2 value.

Page 31
IMM Types
B2 Level Types

Note
 The B1 parent of a B2 instance is normally the parent in the IMM tree hierarchy. For some types, the B1 is
specified using a link for a HasForScadaParent association, these are identified in the section de-scribing those
types.
 When a B2 instance is inserted, a child Discrete Bl Spec is automatically inserted by IMM, when SCA-DAFlag is
true

Page 32
IMM Types
B3 Level Types
B3 Types
B3Block
Equipment
Network Components
PowerSystemResource
SCADA B3
...

Page 33
IMM Types
B3 Level Types
Note
 All equipment in a substation operating at a particular rated voltage belong to one voltage level.
 In IMM, the following B3 equipment instances are children of a VoltageLevel instance.
 Types marked with an asterisk * uses the HasForScadaParent link to indentify their B2 level parent.
 ACLineSegment *
 B3Block – Generic B3 level SCADA block
 Bay (also called switching fields)
 BusbarSection
 ComplexTransformer *
 ConformLoad
 CustomerLoad
 DC Injections
 DCLineSegment *
 EnergyConsumer
 InductionMotorLoad
 Load
 NonConformLoad
 PowerTransformer *
 SeriesCompensator
 ShuntCompensator
 StationSupply
 SynchronousMachine

Page 34
IMM Types
B3 Level Types
Attribute Data Type Required Default/Inte Notes

rnal
SCADA Flag Boolean Yes False Must be TRUE for an instance to be part of SCADA.
The ODBName is the B3Name in the SCADA TA hierarchy. This value
must be unique across all B3 level instances. This includes adopted
siblings using a HasForScadaParent link.
An error message will be issued if a duplicate B3Name is entered. The
default is the first 8 characters of the instance name.
B3Number Long Yes Internal Unique value within the parent B1/B2 assigned by IMM.
Nimset Long Yes Internal Unique value assigned by IMM. Uniqueness is within the Norm Element
Type.
LogbookText String 20 No Yes In the SCADA ODB, this is the B3Text whose length is 9 characters.
The default in IMM is the first 9 characters of the instance name.
BlockType Enum Yes No Required when SCADAFlag is True. User must select the desired
BlockType from the drop-down list based on enumeration
EnumB3BlockType.
AreaOf ResponsibilityId Enum Yes Yes Also called Technological Area. User selects from the drop-down list.
The default is the value of parent B2’s AreaOfResponsibilityId.
When the AreaOfResponsibilityId value is changed on a B3, the new
value is assigned to all descendents whose value matches the old B3
value.

Page 35
IMM Types
B3 Level Types

Note
 When a B3 is inserted, a child Discrete Bl Spec is automatically inserted by IMM, when SCADAFlag is true.
 When a B3 instance is inserted which SCADAFlag of true, a child Discrete Topo Cmp is inserted with attribute
ElementType assigned a value corresponding to the IMM type. If the user explicitly defined a child Topo Cmp,
the ElementType provided is maintained. This allows an ElementType value different then the default to be
specified.
 B3 level types have a Nimset value. This Nimset internal number value is assigned by IMM and is based on
NormElement of BlocHead for all B3 level types.
 There are some B3 block type values which indicates that a Nimset value should not be assigned. These
block types are set during parameterization and include B3 Dev (4), B3 RTU (5), B3 Comp (8), swMeas (53),
B3 AD (67), noNeElgr (82), and EndStBlt (129). Normally, these block type values are used only on instances
of type B3Block

Page 36
IMM Types
Element Level Types
Element Types
Discrete Measurement CB Status, Transformer Tap Changer Value
MW, MVAr, Voltage, Ampere, Phase Angle (Voltage),

Analog Measurement
Phase Angle (Current)
Accumulator Measurement
RedundantDiscrete
ConnectivityNode
...

Page 37
IMM Types
Element Level Types
Example of Analog Instance in ODB Tab

Page 38
IMM Types
Element Level Types
Attributes for Element Level Types
Attribute Data Type Required Default/ Notes

Internal
ElementName Enum Yes No Chosen from a list of values.
For additional information, refer to 5.5.2.2 Element Name, Element Name
String, Element Number, Element Type.
ElementType Enum Yes No Chosen from a list of values.
ElementText String 20 No No In the SCADA ODB, this is the ElementText whose length is 20 characters.
AreaOf Enum Yes Yes Also called Technological Area. User selects from the dropdown list. The
ResponsibilityId default is the value of parent block’s AreaOfResponsibilityId.
Internal SCADAFlag Boolean Yes Internal Must be TRUE for an instance to be part of SCADA. Set by IMM to same
value as parent’s SCADAFlag.
Nimset Long Yes Internal Unique value assigned by IMM.
For additional information, refer to 5.5.2.3 Nimset and Norm Element Type.
The value is null if InternalScadaFlag is False.
Element Name String String 8 Yes Internal ElementNameString is internally maintained by IMM. The value corresponds
to the specified Element Name (which is a number). This value is the
parameterized name of the element within the SCADA ODB.
Norm Element Type Long Yes Internal Norm Element Type (also called NormElement, NoElType, or Noel) is
internally maintained by IMM. The value corresponds to the specified
ElementType.

Page 39
IMM Types
Info Level Types
Note
 SCADA Info's are specific pieces of information about an element
 Within IMM instances of types AccumulatorLimit and AnalogLimit that may or may not be children of an element.
 Limits may have an intermediate LimitSet container instance
 AccumulatorInfo
 AccumulatorLimit
 AccumulatorValue
 AnalogInfo
 AnalogLimit
 AnalogValue
 DiscreteInfo
 DiscreteValue
 RedundantDiscreteInfo
 SeasonalAnalogLimit
 VoltageAnalogLimit

Page 40
IMM Types
Info Level Types
Attributes for Info Level Types
Attribute Data Type Required Default/Intern Notes

al
InfoName Enum Yes No Chosen from a list of values.
For additional information, refer to 5.6.2.3 Information Name and
Information Number.
Value Double No No Initial value to assign to the Info during job activation.
Internal SCADAFlag Boolean Yes Internal Must be TRUE for an instance to be part of SCADA. Set by IMM to
same value as ancestor’s SCADAFlag.
InfoNumber Long Yes Internal Value assigned by IMM. This value is calculated from the InfoName
enum value.
Information Number and 5.5.2.3 Nimset and Norm Element Type.
Info Name String String 8 Yes Internal InfoNameString is internally maintained by IMM. Its value corresponds
to the specified Info Name enum. This is the parameterized name of
the Info within the SCADA ODB.
Information Number.

Page 41
IMM Types
Switch Types
Note
 The IMM type of Switch is abstract which means that no instances of type Switch are ever created.
 Instances are created as one of the following subtypes of Switch
 Breaker
 Disconnector
 Fuse
 GroundDisconnector
 Jumper
 LoadBreakSwitch
 LoadDisconnectSwitch
 Recloser

Page 42
IMM Types
Switch Types
Attributes for Switch Types

Internal
AreaOf ResponsibilityId Enum Yes Yes Also called Technological Area. User selects from the dropdown list.
The default is the value of parent Bays AreaOfResponsibilityId.
Note
 Switch instances must be children of a Bay. The Switch instance must have one and only one child in-stance
of type Discrete. Child instances of other types may exist. These two instances together (the Switch and
Discrete) comprises a complete SCADA element under the B3 of Bay.
 When a Switch instance is inserted, two child Terminal's T1 and T2 are automatically inserted by IMM. This
happens without regard to the SCADAFlag value. The user must connect these terminals to different Con-
nectivityNodes using association TerminalConnectedToConnectivityNode. Notice exceptions called out per
switch type below.
 None of the attributes of the switch subtypes are activated into the SCADA ODB. Rather, it is the connec-
tions between the child Terminals and ConnectivityNodes that is activated into the SCADA ODB

Page 43
IMM Types
Topology
Terminals are associated with each physical power system resource. A terminal allows
Terminals definition of where the resource is connected to the network. Some power system
resources have single terminals (for e.g., loads, generators) and some have two
terminals (for e.g., transmission lines, circuit-breakers)
2 Key Concepts
Connectivity A connectivity node represents a point in the network where power system resources
Nodes are connected together
Note
 To create the desired network topology, the terminal(s) of each power system resource should be connected to
(associated with) a connectivity node(s).
 Each terminal can only be connected to one connectivity node but a connectivity node can have the terminal of
several devices connected to it

Page 44
IMM Types
Topology
Connectivity for Different Types of Power System Devices
Note
 In the e.g., two circuit breakers (Breaker1 and
Breaker2) and 1 busbar (Busbar) are connected to a
common connectivity node (CN1). Similarly, the load
and generator are connected to a common connectivity
node CN2. CN3 is used to connect the transmission
line to its controlling circuit breaker (Breaker 2) through
connectivity node CN3.
Note
 The circuit breakers and transmission line are examples of two-terminal devices while the busbar, load, and
generator are single terminal devices.
 The two IMM types involved in the topology definition are Terminal and ConnectivityNode

Page 45
IMM Types
Topology
Terminal
 A terminal defines where equipment is connected to the network.

 Terminals are children of B3 level equipment. For B3=Bay, the Terminal is a child of a Switch (for example,
Breaker, Disconnector, and so on) and grandchild of the Bay.
 Terminals are linked to a ConnectivityNode using association TerminalConnectedToConnectivityNode

Page 46
IMM Types
Topology
Connectivity Nodes
Note
 A connectivity node represents a point in the network  Each ConnectivityNode instance is connected to either a
where power system resources are connected together. BusbarSection or a Bay using a link for one of associations
 In IMM, ConnectivityNode instances are children of a ConnectivityNodeHasForSpectrumParentB3BusbarSection
VoltageLevel instance. or ConnectivityNodeHasForSpec-trumParentB3Bay.
 In SCADA ODB, ConnectivityNode instances are  A link should not exist for both of these associations.
children of a Bay or BusbarSection.  For microtopology, when a ConnectivityNode is connected
 ConnectivityNode's are also SCADA elements to a BusbarSection, the ConnectivityNode is considered to
be owned by the BusbarSection.
 All other ConnectivityNode’s are owned by the Bay
 A maximum of ten ConnectivityNodes are allowed

per Bay.
 A maximum of one ConnectivityNodes are allowed per
 The value of attribute Element Name must be
BusbarSection. The value of attributes Element Name
unique for all ConnectivityNodes within same Bay
must be Topo 1 and Element Type must be TopoConn.
pointed to by link HasForSpectrumParentB3Bay.
 Each ConnectivityNode instance may connect to zero or
 The value of attribute Element Type must be
more Terminal's using a link for association
TopoConn.
TerminalConnectedToConnectivityNode.
 A ConnectivityNode instance may not connect to
 A ConnectivityNode instance may not connect to both
two different Bays
Terminals (T1 T2) of a single two-terminal device

Page 47
IMM Types
Topology
Validation of Topology
Validation Check
• A Terminal instance must be linked to a ConnectivityNode instance using association. If link is

missing, a warning message will be issued and the Terminal will not be activated into the SCADA
ODB.
• ConnectivityNode may not be connected to both Terminals (T1 T2) of a two-terminal device,
regardless of SCADAFlag.
• If a ConnectivityNode is connected to any B3 with SCADAFlag=True, then that ConnectivityNode
must also have a connection to either a BusbarSection or Bay.
• One ConnectivityNode cannot be linked to two different Bays with SCADAFlag=True.
• One ConnectivityNode cannot be linked to two different BusbarSections with SCADAFlag=True.
• If ConnectivityNode connected to a BusbarSection with SCADAFlag=True, then ConnectivityNode
must have link ConnectivityNodeHasForSpectrumParentB3BusbarSection but not
ConnectivityNodeHa-sForSpectrumParentB3Bay.
• If ConnectivityNode connected to a Bay with SCADAFlag=True (but not BusbarSection with SCADA-
Flag=True), then ConnectivityNode must have link HasForSpectrumParentB3Bay but not
HasForSpec-trumParentB3BusbarSection

Page 48
IMM Types
Topology
Validation of Topology
Validation Check - continued
• If link HasForSpectrumParentB3BusbarSection exists, then ElementName=Topo 1, ElementType is

one of the TopoConn values, and Nimset must have a value. The linked BusbarSection's SCADA-
Flag=True
• If link HasForSpectrumParentB3Bay exists, then ElementName=Topo 1..10, ElementType is one of
the TopoConn values and Nimset must have a value. The linked Bay's SCADAFlag=True.
• ElementName must be unique for all ConnectivityNodes within same Bay pointed to by link HasFor-
SpectrumParentB3Bay.
• Maximum of ten ConnectivityNodes per Bay whose SCADAFlag=True.
• Two equipments may be connected to a ConnectivityNode without a Bay or BusbarSection between
them

Page 49
IMM Types
Calculation
Formula
• the mathematical base for the calculation of derived values (analog values,
accumulator values, or messages).

Page 50
IMM Types
Calculation
Formula Definition
/.General - SCADA/.Spectrum Formulas/Formula
 Formula definitions (IMM type = CalculationRule) are located within the IMM hierarchy as children of in-stance:
/.General - SCADA/.Spectrum Formulas/Formula
 IMM is the master for defining Formulas.
 Once defined, they can be transferred and activated using the cur-rent activation process to populate the ODB.
 These CalculationRule instances are linked to/from Realtime-Calculation instances.
 They are also used during validation of the calculations that use the formulas
 The definition of a formula includes defining its operands as defined in Formula Definition.
 In the e.g. above, the formula (if a then b+0.25 else b) has two operands, a and b, so two FormalOperand
instances have to be defined under the formula.
 Validation checks if the right number of operands have been de-fined. If a formula has been defined but never
linked to a RealtimeCalculation, the formula can still be up-dated.
 Once the formula is used (linked to a RealtimeCalculation), it cannot be updated anymore

Page 51
IMM Types
Function Definition
/.General - SCADA/.Spectrum Formulas/Function
 Function definitions (IMM type CalculationFunction) are located within the IMM hierarchy as children of in-
stance:
 /.General - SCADA/.Spectrum Formulas/Function
 These function definitions must match the functions in the SCADA ODB. The function definitions should not be
modified in IMM. The source data for the functions is the SCADA ODB and these definitions are reverse
transferred out of the ODB and imported into IMM.
 These CalculationFunction instances are linked to/from RealtimeCalculation instances. They are also used
during validation of the calculations that use the functions
 The RealtimeCalculation instances, that link to Functions, have to match the number
of operands defined by the Function.
 The next sections describe how RealtimeCalculation instances use these formulas or
functions.

Page 52
IMM Types
Calculation
RealtimeCalculation
 The Formulas and Functions defined above are used by instances of RealtimeCalculation. RealtimeCalcu-
lation instances are always children of an Info instance.
 After the RealtimeCalculation instance is created, it is linked to either a Formula using association
RealtimeCalculationAssociatedWithCalculationRule, or to a Function using association RealtimeCalcula-
tionAssociatedWithCalculationFunction. The RealtimeCalculation is now using the Formula or Function.
 Based on what Formula or Function the RealtimeCalculation is linked to, correct set of Operands need to be
defined. The Operands can be of type “DynamicOperand” or “ConstantOperand”. These Dynamic or Con-stant
Operands must exactly match the FormalOperands of the Formula (CalculationRule) or Function
(CalculationFunction) the RealtimeCalculation is linked to.
 DynamicOperands are linked to an info whose value is to be used by the calculation. ConstantOperands are
not linked

Page 53
IMM Types
Calculation
Attributes of the RealtimeCalculation instance used by SCADA
Attribute Data Type Required Default/ Internal Notes

Calculation Processing Enum Yes No Chosen from a list of values.
Type
Calculation Delay Time Long No No The number of seconds to delay before performing
the calculation.
Calculation Priority Long Yes No Defines the order of calculations. Lower values are
higher priority, meaning the calculation is
performed before those of lower priority.
CalcType Enum Yes Yes The default is Formula (default).
Internal SCADAFlag Boolean Yes Internal Must be TRUE for an instance to be part of
SCADA. Set by IMM to same value as ancestor’s
SCADAFlag.
Associations of the RealtimeCalculation used by SCADA

RealtimeCalculationAssociatedWithCalculationRul Yes Link to the formula that performs this realtime calculation.
e
RealtimeCalculationAssociatedWithCalculationFun Yes Link to the function that performs this realtime calculation.
ction

Page 54
IMM Types
Calculation
DynamicOperand
- to define the Info whose value is used in the calculation

- name of the DynamicOperand instance must match the name of a
FormalOperand of the formula or function linked by the parent
RealtimeCalculation

DynamicOperandDefineByInfo Yes Link to the Info instance whose value is used by the calculation.

Page 55
IMM Types
Calculation
ConstantOperand
- to define a constant value to be used in the calculation

- name of the ConstantOperand instance must match the name of a
FormalOperand of the formula or function linked by the parent
RealtimeCalculation
Attribute Data Type Required Default/ Internal Notes

Constant Value String 255 Yes No Provide a value for the constant to be used in the
calculation.
SCADAFlag.

Page 56
IMM Types
Typified Calculation
 To define rules for value combinations

 Processing of message, analog value and accumulated data information
 These information can be used as parameters of one formula for building new
information (analog value, accumulated data or message).
 The term “typified” means that those combinations refer to identical

element/info or element/element type/info combinations in the data
system

Page 57
IMM Types
Typified Calculation Definition
/.General - SCADA/Typified Calculations
Typified Calculation Tree
Typified Calculation’s Links

Page 58
IMM Types
Typified Calculation’s Links

Page 59
IMM Types
Attribute Data Type Required Default/Internal Notes

Calculation Processing Type Enum Yes No Chosen from a list of values.
Calculation Delay Time Long No No The number of seconds to delay before performing
the calculation.
Calculation Priority Long Yes No Defines the order of calculations. Lower values are
higher priority, meaning the calculation is
performed before those of lower priority.
CalcType Enum Yes Yes The default is Formula (default).
SCADAFlag.

RealtimeCalculationAssociatedWithCal Yes Link to the formula that performs this realtime calculation.
culationRule
(key) Element Yes Link to the Element instance that defines the ElementName of the instance
whose value is used in the calculation.
(key) Info Yes Link to the Info instance that defines the InformationType of the instance
(key) Element Type No Link to the ElemType instance that defines the ElementType of the instance

Page 60
IMM Types
Dynamic Typified Operand
- to define the identical Element/Info combination of the instance whose

value is used in the calculation
Attribute Data Type Required Default/Internal Notes

SCADAFlag.
Operand Label String 255 No No Label of the operand that must match the name
of a FormalOperand of the formula linked by the
parent Typified Calculation.

(key) Element Yes Link to the Element instance that defines the ElementName of the
instance whose value is used in the calculation.
(key) Info Yes Link to the Info instance that defines the InformationType of the instance

Page 61
IMM Types
Constant Typified Operand
- to define a constant value to be used in the calculation of the value

(analog value, accumulated data or message)

Internal
Constant Value String 255 Yes No Provide a value for the constant to be used in the
calculation.
Internal SCADAFlag Boolean Yes Internal Must be TRUE for an instance to be part of SCADA. Set
by IMM to same value as ancestor’s SCADAFlag.
Operand Label String 255 Yes No Label of the operand that must match the name of a
FormalOperand of the formula linked by the parent
Typified Calculation.

Page 62
IMM Types
Multisite
/.General/.MultisiteControlCenter
Multisite Control Center Tree
ControlCenterDataAccessRight
Control Center Data Access Right

Page 63
IMM Types
Multisite

Internal
Control Permission Enum Yes Yes Chosen from a list of values. Defines whether a control center
has the right to control a point and which control center is the
preferred site for the control.
The default is Control Center can never have control
permission.
Is Available Boolean No Yes Defines whether the Control Center requests the data from the
Master.
The default is False.
Master Priority Long Yes Yes MasterPriority defines whether the ControlCenter can become
master for the data and its priority as a master for the data. A
MasterPriority of 0, means that the ControlCenter can never
become master. A MasterPriority of 1, means that the
ControlCenter is the normal master.
The default is 0.

ControlCenterDataAccessRightAssignedTo Yes Link to a MultisiteControlCenter
MultisiteControlCenter

Page 64
IMM Types
SCADA Decision Table
 Instances of B1, B2, and B3 level types may have two links to InterlockDecisionTable instances – one for
Global and one for Local.
 When using association UsesGlobalInterlockDecisionTable, choose an InterlockDecisionTable in-stance
whose attribute DecisionTableType is Global.
 When using association UsesLocalInterlockDecisionTable, choose an InterlockDecisionTable instance
whose attribute DecisionTableType is Local

Page 65
IMM Types
Interlock Decision Table

Page 66
IMM Types
Steps to Define SCADA Decision Tables
When defining a SCADA decision table, insert the instances in the following order, using either the IMM Single
Instance Editor or the IMM Table Editor:
 Define an Operand Set:
o Insert one instance of type InterlockOperandSet.
o Insert one or more child instances of type InterlockOperand. Use the IMM Table Editor to see these in a
tabular format. Refer the following figure IMM UI Table Editor of InterlockOperands.
 Define the Decision Table:
o Insert one instance of type InterlockDecisionTable.
o Insert link to the InterlockOperandSet instance defined above.
 Define the Rules:
o Insert one or more instances of type InterlockRule as children of the InterlockDecisionTable in-stance. Use
either the Single Instance Editor or Table Editor.
o Hint: Copy/paste from the Single Instance Editor will copy a rule and all its child conditions; whereas
duplicate from the Table Editor will only copy the rule itself, not the children.
o For attribute Priority on the child rule instance(s), assign sequential, ascending values beginning at 1.
 Define the Conditions under each rule:
o Insert one or more instances of type InterlockCondition as children of the InterlockRule instance. Use either
the Single Instance Editor or Table Editor. See figure IMM UI Table Editor of Inter-lockCondition.
o From each InterlockCondition instance, insert link to the corresponding InterlockOperand in-stance.
o Verify the Diagnostic Number on the linked InterlockOperand instance has the correct value.

Page 67
IMM Types
IMM UI Table Editor of InterlockOperand

Page 68
IMM Types
IMM UI Table Editor of InterlockCondition

Page 69
IMM Types
InterlockDecisionTable

Internal
Name String 8 Yes No This is the instance name. Only the first 8 characters are used.
Decision Table Long Yes Internal Internal number assigned by IMM.
Number
Decision Table Type Enum Yes No Chosen from a list of values. One of: FunctionSpecific, Global,
Local, System
Description String 80 No No Comment about the InterlockDecisionTable. Note that only the first
80 characters from the instance description (which has a maximum
length of 1000 characters) are activated into the SCADA ODB.
A link for association InterlockDecisionTableUsesAInterlockOperandSet is required

Page 70
IMM Types
InterlockRule

Internal
Priority Long Yes No Priority must be a unique, consecutive number starting with 1 and a
maximum of 64.
InterlockCondition

Internal
Condition String 8 No No Enter the value of the condition of the corresponding info.
For example, for a status of a breaker use on/off, for a disturbance use
yes/no, and so on.
InterlockOperandSet
InterlockCondition

Internal
Norm Element Name String 8 Yes No The value entered must be a valid NormElement of type
NormElementDiscrete. These instances are children of instance
/.General - SCADA/.DoNotModify/Norm Elements.
Norm Element Long Yes No The value entered must be the value of attribute NoElType from
Number type NormElememtDiscrete for the same as the above name.

Page 71
IMM Types
InterlockOperand

Internal
Operand Sequence Long Yes No For the InterlockOperand sibling instances under one
InterlockOperandSet, the value of OperandSequence must start at
1 and be consecutive without gaps. The maximum value is 50.
Code Word Number Enum No No Chosen from a list of values. For additional information, refer to
Appendix
Element Name String 8 No No May specify the Element Name that will exist as an element level
instance under the B1 or B2 or B3 linking to the
InterlockDecisionTable instance using the HasLocal or HasGlobal
association.
Element Number Long No No If specified, must correspond to the Element Name value above.
Info Name String 8 No No May specify the Info Name that will exist under the element level
instance specified above.
Info Number Long No No If specified, must correspond to the Info Name value above.
Diagnostic Number Long No No Number corresponding to the diagnostic text. Note, these numbers
are defined during parameterization in svctext.
Rule Filter Boolean No No When true, it means that if the condition is not true then move on to
next rule.
Unlock Boolean Yes False When true, it means that if the condition is locked it can be
unlocked.

Page 72
IMM Types
Graphic Decision Table

defined using instances of types WorldmapDecisionTable, WorldmapRule,
WorlmapCondition, WorldmapOperandSet, and WorldmapOperand
Worldmap Decision Tables
defined using instances of types PresentationDecisionTable and
PresentationRule
Presentation Decision Tables
 A PresentationLogic instance will have a link to both a WorldmapDecisionTable instance and a

PresentationDecisionTable instance.
 The WorldmapDecisionTable determines which rule out of the PresentationDecisionTable applies based on the
runtime status of the object

Page 73
IMM Types
Steps to Define Worldmap Decision Tables
Worldmap Decision Table
Worldmap Operand Set

Page 74
IMM Types
Steps to Define Worldmap Decision Tables
When defining a worldmap decision table, insert the instances in this order using either the IMM Single In-stance
Editor or the IMM Table Editor:
 Define an Operand Set:
o Insert one instance of type WorldmapOperandSet.
o Insert one or more child instances of type WorldmapOperand. Use the IMM Table Editor to see these in a
tabular format
o Insert one instance of type WorldmapDecisionTable.
o Insert link to the WorldmapOperandSet instance defined above.
o Insert one or more instances of type WorldmapRule as children of the WorldmapDecisionTable instance.
Use either the Single Instance Editor or Table Editor.
Hint: Copy/Paste from the Single Instance Editor will copy a rule and all its child conditions; whereas duplicate
from the Table Editor will only copy the rule itself, not the children.
o For attribute Priority on the child rule instances, assign sequential, ascending values beginning at one.
 Define the Conditions under each rule:
o Insert one or more instances of type WorldmapCondition as children of the WorldmapRule in-stance. Use
either the Single Instance Editor or Table Editor.
o From each WorldmapCondition instance, insert link to the corresponding WorldmapOperand in-stance.

Page 75
IMM Types
WorldmapDecisionTable

Internal
Name String 8 Yes No This is the instance name. Only the first 8 characters are
used.
Decision Table Long Yes Internal Internal number assigned by IMM.
Number
Decision Table Enum Yes No Chosen from a list of values. One of: Element Specific,
Type Keybox Specific, or Network Element Specific
Note:
KeyboxSpecific is used only by GE’s SvgExport. Any
WorldmapDecisionTable which has Keybox Specific is
not activated into the SCADA ODB.
Description String 80 No No Comment about the WorldmapDecisionTable.
Note: That only the first 80 characters from the instance
description (which has a maximum length of 1000
characters) are activated into the SCADA ODB.
A link for association WorldmapDecisionTableUsesAWorldmapOperandSet is required

Page 76
IMM Types
WorldmapRule

Internal
Priority Long Yes No The Priority defines in which sequence the rules are
processed. The highest priority equals 1. Priority must be a
unique, consecutive number starting with 1 and a maximum of
32767.
Alternative Long No No The Alternative defines the index of the figure/attribute
representation which is used when the rule evaluates to true.
WorldmapCondition

Internal
Condition String 8 No No Enter the value of the condition of the corresponding info.
For example, for a status of a breaker, use on/off, or for a
disturbance, use yes/no.

Page 77
IMM Types
WorldmapOperandSet

Internal
Norm String 8 Yes No The value entered should be a valid NormElement of type
Element NormElementDiscrete. These instances are children of instance
Name /.General - SCADA/.DoNotModify/Norm Elements
Norm Long Yes No The value entered must be the value of attribute NoElType from
Element type NormElememtDiscrete for the same as the above name.
Number

Page 78
IMM Types
WorldmapOperand

Internal
Operand Sequence Long Yes No For the WorldmapOperand sibling instances under
one WorldmapOperandSet, the value of
OperandSequence must start at 1 and be
consecutive without gaps. The maximum value is
50.
Element Name String 8 No No When the parent WorldmapOperandSet is linked to
a WorldmapDecisionTable whose
DecisionTableType equals:
Network Element Specific, then Element Name
should be null.
Element Specific, then specify the Element Name.
Element Number Long No No Required, if Element Name is specified. Value must
correspond to the Element Name.
Info Name String 8 Yes No May specify the Info Name that will exist under the
element level instance specified above.
Info Number Long Yes No Required if Info Name above is specified. Value
must correspond to the Info Name.

Page 79
IMM Types
Steps to Define Presentation Decision Tables
Presentation Decision Table

Page 80
IMM Types
Steps to Define Presentation Decision Tables
When defining a presentation decision table, insert the instances in this order using either the IMM Single Instance
Editor or the IMM Table Editor:
o Insert one instance of type PresentationDecisionTable.
o For attribute Presentation Group ID, assign sequential, ascending values beginning at zeor.
o Insert one or more instances of type PresentationRule as children of the PresentationDeci-sionTable instance.
Use either the Single Instance Editor or Table Editor.
o Hint: Copy Paste from the Single Instance Editor will copy a rule and all it’s child conditions; whereas duplicate
from the Table Editor will only copy the rule itself, not the children.

Page 81
IMM Types
PresentationDecisionTable

Internal
Presentation Group ID Long Yes No Unique identifier for the Presentation Group.
Combination of attributes PresentationGroupId and
PresentationGroupType must be unique across all instances of
type PresentationDecisionTable.
Presentation Group Enum Yes No Describes the Presentation Type. Chosen from a list of values.
Type
PresentationRule

Internal
Alternative Long Yes No Index of element in figure or attribute group.
Default Boolean Yes True Indicates whether this rule is assumed to apply if no other rule fits the
conditions. Only one PresentationRule sibling instance may have a
value of True, the others should be False.
Flashing Short Integer Yes Zero Flashing property of rule. Currently both zero and non-zero mean
flashing. In the future, a non-zero will indicate the frequency of flashing.
Index Short Integer Yes No Index of attribute in colour relation (FXCOLOUR) or index of attribute in
figure relation (FXFIGURE).
Style Name String 255 Yes Internal Assigned by IMM to the name of the instance pointed to by link for
association PresentationRuleHasAGraphicPresentation with a suffix of
.emf
Page 82
Thank you for your attention!
Restricted © Siemens AG 2015 All rights reserved. Answers for infrastructure and cities.
Page 83

SPC Data Model

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SPC Data Model

Enviado por

Direitos autorais:

Formatos disponíveis

Spectrum PowerTM 7

DATA MODELING (SCADA)

• Spectrum Power 7 Data Model

Restricted © Siemens AG 2015 All rights reserved.

Attributes HighVoltageLimit, LowVoltageLimit, OnelineDisplayName, Scada B3Number, etc.

Instance • Objects of the real world;

Restricted © Siemens AG 2015 All rights reserved.

Instance Path /Network/Companies/Europe/ZONE_1/Vienna/33/BB1A

• Network is an instance of type sysNetworkCategory. It is sometimes called a folder instance as its

• 33 is an instance of type VoltageLevel. The equipment of a substation that is operating at a voltage

• When an instance is moved, its path changes.

Restricted © Siemens AG 2015 All rights reserved.

Identifiers of Busbar GUID: {00165A66-863C-47B8-AB9A-43E0978F3848}

ObjectId: 665A16003C86B847AB9A43E0978F3848 Note, ObjectID

Restricted © Siemens AG 2015 All rights reserved.

Ancestors of the BB1A BusbarSection instance

• Parent of the BB1A

Restricted © Siemens AG 2015 All rights reserved.

• Spectrum Power 7 Data Model

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

True => Data populated into corresponding database

Restricted © Siemens AG 2015 All rights reserved.

• Spectrum Power 7 Data Model

Restricted © Siemens AG 2015 All rights reserved.

SCADA Flag = True and NA Flag = False

Restricted © Siemens AG 2015 All rights reserved.

Network Image (NIM)

• Blocks (stations, voltage levels, bays, network components)

Restricted © Siemens AG 2015 All rights reserved.

Five-level combination (B1/B2/B3/Element/Info) is

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

Uniqueness constraints on the values of the ODB Names

Restricted © Siemens AG 2015 All rights reserved.

The SCADA TA is a portion of the full IMM instance path

Multiple IMM instances together map to one SCADA element

IMM Instance: IMM Instance:

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

 It displays a subset of the attributes

Restricted © Siemens AG 2015 All rights reserved.

• Spectrum Power 7 Data Model

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

 Many IMM types have SCADA Flag

 Other IMM types have an Internal SCADA Flag attribute.

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

• Spectrum Power 7 Data Model

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

Attributes for B1 Level Types

Attribute Data Type Required Default/Int Notes

B1Number Long Yes Internal Unique value assigned by IMM.

Restricted © Siemens AG 2015 All rights reserved.

Association used for B1 Types

Association Required Notes

Restricted © Siemens AG 2015 All rights reserved.

Restricted © Siemens AG 2015 All rights reserved.

Attributes for B2 Level Types