Datapoints Profiles

DS Agile Training Level 2

Global Systems Engineering
03/05/2012

GRID

GSE
SAM
 Summary

1) Generalities Page 3

2) Inputs Profiles Page 6

3) Outputs Profiles Page 19

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 2
 1.1) SCE Profiles : Input Profiles

Supervision Profiles … What are Supervision DataPoint?

xPS SPS, SPS_Profile FSS, SBMC dependency

DPS, DPS_Profile Few acquisition options
MPS, MPS_Profile
MV State labels
MV, MV_Profile
FOR Archive&Logging/state
(6)
xCT Interlock boolean/state
Counter, Counter_Profile
Alarm/state

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 3
 1.2) SCE Profiles : Output Profiles

Control Profiles … What are Control DataPoint?

xPC SPC, SPC_Profile DE / SBO

DPC, DPC_Profile Few acquisition options

SetPoint State labels

SetPoint, SetPoint_Profile
FOR Archive&Logging on event
(6)
Interlock boolean / state

Alarm on Negative Ack.

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 4
 Summary

1) Generalities Page 3

2) Inputs Profiles Page 6

3) Outputs Profiles Page 19

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 5
 2.1) xPS Profiles (1)

Single, Double, Multi Point Status : General Tab

Allow FSS on DP Initial Status
Yes/No For software info => status at start-up
No Never use Motion

Allow SBMC on DP Toggling Filtering for SPS, DPS

(Yes/No) Yes/No
when bay has SBMC ON :
SBMC Substitute value to RCP
SPS : Set/Reset/Suppressed
DPS : Jammed/Open/Close/Suppressed
MPS : Undefined/Suppressed
GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 6
 2.1) xPS Profiles (2)

Single, Double, Multi Point Status : State Labels tab : Alarms / Log Print
SPS : Set/Reset
DPS : Jammed/Open/Close/Undefined
MPS : 1 among N(<16) State0..State15/
Undefined

All Invalid States or FSS Label

1) Labels are Business Language dependant
2) On OI : printer and viewers labels are concatenation of
Force/Substitute & Value (open/close) : “forced open”
3) Profile is linked to DP then words can change
DPS Switch gear => Open/Close
R/L => Remote/Local
MPS N and associate DP impact labels GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 7
 2.1) xPS Profiles (3)

Single, Double, Multi Point Status : State Treatment Tab (1)

State by State, archiving policy
For OI :
- No Archive, No logging = nothing in SQL Historian database
- Archive only = all states in VTQ (states/values) SQL Historian database tables (Trend Viewer)
- Archive & Logging = all states in VTQ (states/values) SQL Historian database tables + states marked with
“Logging” in Events SQL database table (Event Viewer + Archive viewer + printer)

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 8
 2.1) xPS Profiles (4)

Single, Double, Multi Point Status : State Treatment Tab (2)

For C264 :
- Archive & Logging = Archive means stored in event list (2048 events in memory) & Logging means
displayed in event list of front face (200 events).

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 9
 2.1) xPS Profiles (5)

Single, Double, Multi Point Status : Interlock tab : Boolean value by state
SPS Set and Reset Boolean value in all PSL and interlockings :
convention : SET=TRUE, RESET=FALSE

DPS Jammed, Open and Closed Boolean value in all PSL and interlockings :
convention : CLOSED=TRUE, OPEN=FALSE, JAMMED=INVALID, UNDEFINED = INVALID

Note : For MPS, no convention => depends on context of use

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 10
 2.1) xPS Profiles (6)

Single, Double, Multi Point Status : Alarm tab, Alarm definition state by
state
Delay before alarm generation
Alarm not generated
(if DP reset for example)
if state follow control (RFI SBUS)
Gravity 1->5
Audibility (klaxon)

Alarm Generation Alarmed state or not Alarms are acknowledged by

Appearance/Appearance disappearance operator, but clearing can be manual
1 / 2 alarms or automatic

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 11
 2.2) MV Profile (1)

Measurement Values : General tab

Allow FSS on MV No Allow SBMC on MV

Yes/No (Yes/No)
(when bay in SBMC ON)
Substitutes values by Suppressed

MV value display on OI Mimic

No # after decimal
U to display unit
GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 12
 2.2) MV Profile (2)

Measurement Values : State Labels tab Alarms / Log /Print

IED disconnected Board acquisition saturated Threshold violation

Digital Measurement coding error 4-20mA DC input when under

4mA

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 13
 2.2) MV Profiles (3)

Measurement Values : State Treatment Tab

State by State, archiving policy
For OI :
- No Archive, No logging = nothing in SQL Historian database
- Archive only = all states in VTQ (states/values) SQL Historian database tables (Trend Viewer)
- Archive & Logging = all states in VTQ (states/values) SQL Historian database tables + states marked
with “Logging” in Events SQL database table (Event Viewer + Archive viewer + printer)

Note :
- Archive only for valid => value will be available for trend viewer
- Archive & Logging for SelfCheckFlt and Unknown to store acquisition errors
GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 14
 2.2) MV Profile (4)

Measurement Values : Interlocking tab

Note : Goal is use MV associated status in PSL.

No convention => depends on context of use

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 15
 2.2) MV Profile (5)

Measurement Values : Alarm Management tab

Alarm Generation Alarmed state or not
Appearance/Appearance disappearance
1 / 2 alarms

Alarms are acknowledged by

Delay before alarm generation operator, but clearing can be manual
Gravity 1->5 or automatic
Audibility (klaxon)

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 16
 2.2) MV Profile (6)

Measurement Values : Mean Value tab cf. PS06

Reference hour :
-Hour of daily min/max/average values calculation
-Daily mean values stored in monthly VTQ table for 15
.csv VTQ tables month.
SQL
HISTORIAN 35 days storing
Daily
VTQ

SQL
HISTORIAN Monthly 15 months storing
Event

Yearly 5 years storing

Reference day :
-Day of monthly min/max/average values calculation
-Monthly mean values stored in yearly VTQ table for
about 5 Years

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 17
 2.3) Counter Profile

Single, Double CounTer: Status…
Like MV Except :

Pulse value
multiplicative coefficient

Counter over max value

Double Counter invalidity

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 18
 Summary

1) Generalities Page 3

2) Inputs Profiles Page 6

3) Outputs Profiles Page 19

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 19
 3.1) xPC Profiles (1)

Single, Double Point Control: General tab

Define SBUS control sequence in one or two steps :

In DE : In SBO :
Client send control to Server - Step Selection
Server send back Ack to Client kept by Server with Time Out [0..600](s)
- Step Execution
SBO Many => transformer

Note : At DS Agile OI Level, DE/SBO pop-up.

DE with SBO popup = Control is DE appearing in SBO-like popup

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 20
 3.1) xPC Profiles (2)

Single, Double Point Control: use and labels

Set Point => no order Usage :
Some controls are using only one
“channel” e.g. Master Trip Reset

Labels “status” for control send

logging, alarms, popup buttons
On Control

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 21
 3.1) xPC Profiles (3)

Single, Double Point Control: interlocking and FBD tab

PSL status on control False/True

Note : Goal is use xPC associated status in PSL.

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 22
 3.1) xPC Profiles (4)

Single, Double Point Control: Alarm on NACK

Alarm on control Yes/No Clearing Acknowledged alarms

Delay [0..120]
Gravity [1..5]
Klaxon [Yes/No] + Relation

GSE
L2-03-DATAPOINTS PROFILES - Rev G - P 23
 www.alstom.com

GRID

GSE
SAM