634   status consistency

Created: 27 Feb 2009

Status: Future Improvement

Part: Part 7-420 (2008; DER)

Links:

Page:

Clause: 5.3.3

Paragraph:

Category: Issue for edition 2 of this part

Issue

Many possible combinations of status indicate known inconsistent states. For example, a device cannot be both starting and stopping at the same time. The present situation would force each client to read all objects and then perform consistency checks on every access.

Proposal

Add text indicating that it is the responsibility of the server to present consistent information at the interface. For example, both ModStr and ModStop must not both be simultaneously TRUE.

Discussion Created Status
Need to assess the structure of the operational mode status points, including the development of a state machine for the possible states.
Jacob and Masatake will take a stab at this by the next WG17 meeting. 		08 Oct 13 Future Improvement
Agree conceptually, but I feel this kind of responsibility to present consistent information is inherent in good system design. I am not sure it needs to be explicitly stated in the standard. It should be stated in a Users Guide or similar White Paper on using IEC 61850. 27 Feb 09 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1