Datapoints Profiles
PCL
PCL
PCL
PCL
PACiS
PACiS
PACiS
PACiS Technical
Technical
Technical
Technical Training
Training
Training
Training Level
Level
Level
Level 2
2
2
2
CS&P
CS&P
CS&P
• Content
Generalities
Inputs Profiles
Outputs Profiles
• Content
Generalities
Inputs Profiles
Outputs Profiles
Supervision Profiles …
What are Supervision DataPoint?
xPS
MV
xCT
FSS, SBMC dependency
Few acquisition options
State labels
Archive&Logging / state
Interlock Boolean / state
Alarm / state
SPS,
SPS_Profile
DPS,
DPS_Profile
MPS,
MPS_Profile
MV,
MV_Profile
Counter, Counter_Profile
FOR
Control Profiles …
What are Control DataPoint?
xPC
SetPoint
DE / SBO
Few acquisition options
State labels
Archive&Logging on event
Interlock Boolean / state
Alarm on Negative Ack.
SPC,
SPC_Profile
DPC,
DPC_Profile
SetPoint, SetPoint_Profile
FOR
• Content
Generalities
Inputs Profiles
Outputs Profiles
Single, Double, Multi Point Status : General Tab
Allow FSS on DP
Yes/No
Allow SBMC on DP
(Yes/No)
when bay has SBMC ON :
SBMC Substitutes values to RCP by: - SPS : Set/Reset/Suppressed
- DPS : Jammed/Open/Close/Suppressed - MPS : Undefined/Suppressed
Toggling Filtering for SPS, DPS
Yes/No
Initial Status
For software info => status at start-up
No
No
Never use Motion
• xPS Profiles (1)
Single, Double, Multi Point Status : State Labels tab : Alarms / Log Print
All Invalid States or FSS Label
SPS :
Set/ResetDPS :
Jammed/Open/Close/UndefinedMPS :
1 among N(<16) State0..State15/ Undefined2) 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
1) Labels are Business Language
dependant
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)
Single, Double, Multi Point Status : State Treatment Tab
Relation “has events logged on” for SOE
printing
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).
Single, Double, Multi Point Status : Interlock tab : Boolean value by state
Note : For MPS, no convention => depends on context of use
SPS Set and Reset Boolean value in all PSL and
interlocking :
convention : SET=TRUE, RESET=FALSE
DPS Jammed, Open and Closed Boolean value
in all PSL and interlocking :
convention : CLOSED=TRUE, OPEN=FALSE, JAMMED=INVALID,UNDEFINED=INVALID
Single, Double, Multi Point Status : Alarm tab, Alarm definition state by state
Alarm Generation
Appearance/Appearance disappearance 1 / 2 alarms
Alarmed state or not
Spurious SPS is Set and never reset
Alarm not generated
if state follow control (RFI SBUS)
Delay before alarm generation
(if DP reset for example)
Gravity 1->5
Audibility (klaxon)
Alarms are acknowledged by
operator, but clearing can be
manual or automatic
Relation “has alarm events
logged on” for alarm printing
Measurement Values : General tab
Allow FSS on MV
Yes/No
Allow SBMC on MV
(Yes/No)
when bay in SBMC ON:
Substitutes values by Suppressed
MV value display on OI
Mimic
No # after decimal.
U to display unit
No
No
• MV Profile (1)
Measurement Values : State Labels tab
Alarms
Log Print
IED disconnected
Board acquisition saturated
Digital Measurement coding
error
4-20mA DC input when
under 4mA
Threshold violation
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)
Measurement Values : State Treatment Tab
Note :
- Archive only for valid => value will be available for trend viewer
- Archive & Logging for SelfCheckFault and Unknown to store acquisition errors
• MV Profile (3)
Measurement Values :
Interlocking tab
Note : Goal is use MV associated status in PSL. No convention => depends on context of use
• MV Profile (4)
Measurement Values :
Alarm Management tab
Alarm Generation
Appearance/Appearance disappearance 1 / 2 alarms
Alarmed state or not
Delay before alarm generation
Gravity 1->5
Audibility (klaxon)
Alarms are acknowledged by
operator, but clearing can be
manual or automatic
Measurement Values :
Mean Value tab cf. PS06
Reference hour :
- Hour of day for min/max/average values calculation
- Daily mean values stored in monthly VTQ table for 15 months
Reference day :
- Day of month for min/max/average
values calculation
- Monthly mean values stored in yearly
VTQ table for about 5 years
Daily Monthly Yearly .csv VTQ tables SQL HISTORIAN Event SQL HISTORIAN VTQ 35 days storing 15 months storing 5 years storing
• MV Profile (6)
Single, Double CounTer: Status…
Like MV Except
Pulse value
multiplicative coefficient
Counter over max value
Double Counter invalidity
• Content
Generalities
Inputs Profiles
Outputs Profiles
Single, Double Point Control: General tab
Define SBUS control sequence
in one or two steps :
In DE :
Client send control to Server Server send back Ack to Client In SBO :
- Step Selection
kept by Server with Time Out [0..600](s)
- Step Execution
SBO Many => transformer
Note : At PACiS OI Level, DE/SBO pop-up.
DE with SBO popup = Control is DE appearing in SBO-like popup
• xPC Profiles (1)
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
Single, Double Point Control:
interlocking and FBD tab
PSL status on control
False/TrueNote : Goal is use xPC associated status in PSL.