1755   Event driven schedules – Add DO to stop schedule by event

Created: 16 Feb 2021

Status: Discussion (red)

Part: Part 7-4 (2020; Edition 2.1)

Links: #1756 Event driven schedules – Extend description

Page: 169/482

Clause: 6.6.9 Table 70

Paragraph: Table 70


The possibility to stop an event driven schedule by another event is missing.
Defining an additional DO would allow that starting and stopping a event driven schedule could be represented by two independent trigger events.

Example: A local DO event may represent a communication failure. The transition (False to True) of the DO referenced by InSyn could indicate that the communication has a failure (which should start a specific schedule). The transition (False to True) of the DO referenced by (new) DO InSynStop could indicate that the communication is again operating properly (which should cause the schedule to stop immediately).


Add a new DO InSynStop after InSyn with the CDC ORG.
Presence condition shall be optional (to ensure backwards compatibility).

Add DO description:
“Object reference of the external trigger to stop the schedule
if the schedule is triggered by an event.
The Type of the external trigger Data Attribute
shall be BOOLEAN.”

Add Note: This Data Attribute may be located in the same IED (local issue how the event is communicated) or in another IED (needs GOOSE or Report to communicate the event from one IED to another IED).

Discussion Created Status
I support the proposal to add a DO InSynStop (ORG, optional or conditional [C:if InSyn is modelled]). 23 Feb 21 Discussion (red)
Accepted. 16 Feb 21 Accepted


Privacy | Contact | Disclaimer

Tissue DB v.