268   PTOC Enabling Blocking by Harmonic restraint

Created: 08 Dec 2005

Status: In Force (green)

Part: Part 7-4 (2003)


Page: 29

Clause: 5.4.18


Category: Issue for edition 2 of this part


PHAR defines and detects harmonic and the resulting restraints to block protection functions. Depending on the protection function and the overall protection scheme, not all protection functions should be blocked in the same situation. But there is not setting parameter to define if the protection function should be blocked or not.


It is proposed to add to PTOC and other protection functions a setting which defines the requested blocking behavior:

EnaHRst (SPG) Enable blocking of the function by harmonic restraint

Discussion Created Status
No additional comments within the ballot period. Final proposal accepted. 13 Jul 06 In Force (green)
Add a data object (SPG) for enabling the blocking behavior and
add a data object showing that the output(s) is(are) blocked to
all P LN Classes
08 Jun 06 Ballot Period
I always got the impression that all logic connecting protection functions (e.g. blocking trips or starts)is in PTRC. If we need additional enablings directly at a protection function, then this is a general issue and not restricted to PHAR. However, all internal logic (like enabling or blocking from some outside signal) is not standardized. So, what we could do is just proved an Enabled or Blocked status indication, which is different from Mod, and may be a reference DATA (CDC ORG or similar?) to some project or implementaion defined blocking input as a specialization of already demanded general input signal references. 09 Dec 05 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.