{'fraction_non_alphanumeric': 0.01758366420873511, 'fraction_numerical': 0.017016449234259785, 'mean_word_length': 5.3, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
IEC 61850 Testing and Commissioning Advantages Using GOOSE Messaging

When a utility looks at implementing new changes with technology or their engineering and design standards, it is human nature to be resistant to these changes. This also holds true when a utility makes the transition from a conventional substation protection and control (P&C) system to a fully digital IEC 61850 based scheme. Existing testing procedures for conventional P&C schemes involves testing every element associated with that scheme. This often requires lengthy testing procedures and modifications to the relay setting. The modifications include assigning multiple protection elements, time overcurrent pickups, logic pickups, timers, and mapping elements to additional output contacts. When the transition from these conventional systems to IEC 61850 occurs, the question is raised “How am I going to test a protection or control scheme with no test switches to isolate the equipment?” This paper explores how IEC61850 can provide a more efficient testing and commissioning solution to the utility. It creates a more user-friendly interface with the equipment and an opportunity to provide a solution to existing problems. One of those opportunities that can be provided by IEC61850 utilizes GOOSE messages. The messages can be published from the devices for not only normal operation, but also contain data sets for testing purposes. By adding data sets for testing purposes, such as time overcurrent pick up (PTOC.Str) to the GOOSE message we eliminate the need for relay technicians to modify the relay settings. IEC61850 has built in testing capabilities directly and indirectly into the standard, this paper will examine how these implementation differences can be exploited.