Electronic Logbook. Hedgehog-2. version 2.7. Quick Start. Revision 1.3 of 10/31/2012

Transcription

1 Electronic Logbook Hedgehog-2 version 2.7 Quick Start Revision 1.3 of 10/31/2012 Monitor Electric, 2012

2 2 CONTENTS Introduction 3 Entry List 4 Event Entry 4 Filtering and Sorting 6 Chaining 7 Attachments, Notes, Authorization 7 Overwriting and Editing 8 Printing, Exporting, ing and Texting 9 External Program Interaction 9 Shift Turnover 10 Logbook Configuration 10 Other Features 11

3 3 Introduction Electronic logbook Hedgehog-2 is designed for operational record entry, safe storage and analysis by dispatchers and managers at electric power utilities control centers. The client-server architecture of the logbook allows it be used on a network of computers as well as on a single machine. A logbook client may be installed on every operator, engineer and manager console. The logbook clients connect to the logbook server that centralizes data entry and keeps it in the database. Despite multiple concurrent data entry points, the logbook contains a single database whose entries can be searched, examined and processed at any of the client machines. This way, the logbook presents a single point of access for the operational information record keeping. A SCADA/EMS or any other external application may be designed to automatically create logbook entries. To protect against hardware failure, a backup logbook server with a copy of the database may be run concurrently with the primary server. Control Center operator console automatic entries primary logbook server logbook database entries logbook desktop client SCADA/ EMS replication backup logbook server logbook database engineer console logbook desktop client The major item of logbook manipulation is an operational entry. The philosophy of the logbook is to reliably record the entries; then make them available for searching, printing and dissemination. To ensure the permanency of the record, once the entry is input, it cannot be accidentally or willfully erased. This guide focuses on activities to be done with these entries in Hedgehog-2. The guide is organized as follows.

4 4 We describe the Entry List the main window of the logbook and entry manipulation related to this list.. We then cover several supporting programs: shift turnover, logbook configuration. Some of the programs and features are too detailed for this guide. We quickly introduce them at the end of this guide without going into the specifics of their operation. Entry List Entry List is the main record processing window of the logbook. The entries are shown as lines in a table. On the left of the entry line, there is a flag area to visually denote specific properties of the entry. The flags are followed by entry fields. You can configure which fields are displayed and in what order. Commonly used fields are: time of receiving notification of the event, time of occurrence, the category of event, the facility or equipment where the event occurred, the detailed description of the event, the person who made the entry and the person who communicated the event. Event Entry To create a new event entry, select Entry New from the pull-down menu or click on the New icon of the toolbar. The Logbook Entry dialog box appears. This dialog box lets you enter the information associated with the event. The information is as follows:

5 5 The first field in the dialog box contains a list of categories and subcategories to be associated with the event. For example, switching off a reactor may be classified under System state management/voltage regulation. These categories are customizable to the needs of the control center. This customization is done using Logbook Configuration tool. The Facility/Equipment field allows you to specify the location of the event. For example, if there is an outage, it may be associated with a facility such as a substation or a power plant. The event location may be narrowed to a particular piece of equipment such as a generator or a transformer. The facility and equipment that appear as options for the event may be determined by already selected category/subcategory. For example, if the category is voltage regulation, the facility/equipment may present the list of all generators, reactors and batteries available in the power system. Such association simplifies event entry. This association is also configured in Logbook Configuration tool. The recorded entry may be about operator communication: either notification given to the operator or directive issued by the operator. For example, the operator may give a directive to substation personnel to manually disconnect a reactor. The other communicating party can be selected from the list of the personnel. The list of personnel is configured through the Logbook Configuration. Note that the communicating party may be at a facility that is different from the location of the incident. For example, an outage at a substation may need to be reported to a reliability coordinator control center. Each entry has two timestamps. The time of event occurrence of the event is manually entered by the operator. Local time of the computer where logbook is installed is automatically added as the time of entry recording.

6 6 The event description field is to hold the narrative of the event entry. For routine event description entry, each event category can be configured with associated keywords (standard phrases). Click on the keyword to insert it into the event description. For ease of visual identification, an icon can be selected for the entry. The list of icons is configured in Logbook Configuration. Once the entry is made, this icon appears in the icon field of the flag area of this entry s row. It may be necessary to enter several similar entries. In this case, check Duplicate entry field. If this field is checked, once the entry is created, the entry dialog box remains open with all the fields filled exactly as in the already recorded entry. To record a similar entry, you just need to modify the fields that are different. In case such similar entries are made frequently, the entry may be saved as a template. Such a template can be quickly invoked by selecting template button in the toolbar in the entry list window. Filtering and Sorting The number of entries in a typical logbook quickly grows into thousands and becomes a challenge to navigate. Hedgehog-2 simplifies dealing with such a large list of entries through filtering and sorting.

7 7 To the left of the entry list, there is a filtering and sorting configuration pane. You can toggle displaying of this pane by clicking on the configuration button in the entry list toolbar at the top of the entry list window. Entries can be filtered by various timing parameters and records. A filter can be temporarily created for quick entry lookup or named and saved for repeated use. The named filters are listed below the filter toolbar. The toolbar gives you access to filter manipulation functions. Some of the common functions are as follows: To create or modify a filter, click on the filter editing button ; To apply already created filter, click this button. Chaining Several entries may be related to the same incident. For example, first, there may be an abnormal state and operator mitigating actions entry. Then, the entry that establishes the cause, a faulty transformer, is recorded. It then may be followed by a maintenance request entry, granting of the request, taking the transformer offline, a successful repair, testing and bringing the transformer back online. For quick filtering and display such related events can be linked in a chain. To view chained entries or to add chains, click on the chain icon in the filtering pane or right-click on the entry row in the entry list and select link from the dropdown menu. If the entry is chained, the chain icon appears in the flags area of the entry row. Attachments, Notes, Authorization Once the entry is made, you can add attachments related to this entry. The attachments can be in a variety of formats: scanned documents, communication transcripts, photographs, audio and video recordings. The attachments are stored in the same database as the entries themselves. Hence, the

8 8 attachments are subject to the same protections and security. There are several ways to add an attachment to an entry. You can double-click on the attachment field of the entry s row, right-click on the row and select Attachments from the dropdown menu or select Entry Attachments form the pulldown menu. Once at least one attachment is added to the entry, the attachment icon is displayed in the flag area of this entry row. A note with a commentary can be attached to the entry. In fact, several different users may attach notes to form a mini-discussion regarding this entry. To attach a note, double click on the note field of the entry row. You can also select this option from the pull-down or drop-down right-click menu. An authorization is a specialized note for providing feedback to the entry author. For example, a head dispatcher would like to leave a comment to the operator who made the entry and make sure that the operator reads it. To leave an authorization, double-click on the authorization field of the entry row. If the authorization is attached to the record, the corresponding icon is displayed in the flag area of the entry. The icon is displayed in red to alert the entry author. The red color is removed once the entry author double clicks on the authorization icon and reads the entry. Overwriting and Editing There are two ways to correct an erroneous entry: to overwrite it or to edit it. However, in order to prevent the information loss, the old entry is retained in the logbook database. The old entry is shown in gray with overstrike font. Old entries are read-only and cannot be further modified. Overwriting allows you to comment on the entry and remove it. The commentary may contain the reason for entry removal. That is, overwriting is a way to strike out an erroneous entry. To overwrite an entry, select Overwrite from either the Entry option of the pulldown menu or from the right-click dropdown menu. The old entry cannot be overwritten again. By default, the old and the new entries are displayed next to each other in the list of entries with overwriting flag entry. The flag is blue for the new entry and red for the old one. in the flag field of each Editing allows you to modify an entry in an arbitrary manner. To edit an entry, select Edit from the pulldown menu or from the right-click dropdown menu. Similar to overwriting, the new and old entries are listed next to each other and denoted by edited flag.

9 9 Each time an entry is edited, the old entry is saved. Revision navigation buttons list toolbar may be used go back and forth between these revisions of the entry. in the entry Printing, Exporting, ing and Texting Hedgehog-2 contains a number of functions for entry printing and dissemination. The functions are available in the Tools section of the pulldown menu. Logbook entries can be exported to a Microsoft Excel spreadsheet, printed or ed. In each case, the active filter is used to select entries for dissemination. In other words, the entries currently shown in the Entry List window will be printed or exported. Printing is done according to pre-configured printing template. One particular printing report is Shift Log. This report lists all the entries made during current shift. The shift log s is intended to be printed as a part of shift turnover protocol. To print this report, select Tools Print Shift Log option from the pull-down menu. The logbook may be configured to send text-message or notifications if events of certain categories or related to certain locations occur. For example, a powerplant owner may wish to be notified in case there is an incident in the owner s facility or a reliability engineer may need to be kept appraised of the entries in the power system state category. External Program Interaction Hedgehog-2 stores record entries in a Microsoft SQL database. However, due to logbook security and integrity concerns, direct modification of database records is prohibited. Instead, the logbook has an open application programming interface (API) for logbook entry manipulation. This allows external programs to access the logbook. Frequently, the logbook is integrated with a SCADA/EMS system installed in the control center and this SCADA/EMS automatically makes entries in the logbook. For example, an operator entry in SCADA/EMS about a certain field devices supplying incorrect

10 10 measurement may be copied to the logbook. For another example, scheduled power interchanges or maintenance events can also migrate to the logbook from SCADA/EMS. Shift Turnover Shift turnover is a logbook component for recording the beginning and ending of the shift and the name of the new shift operator who will be making entries in the logbook. The shift turnover process should happen at each operator workstation. The ending shift operator hands over the shift by entering his password. The new shift operator selects his name and provides the password to confirm the turnover. The logbook automatically makes two records about the turnover: shift provider and shift receiver. Logbook Configuration Hedgehog-2 is made to be easily customizable to the needs of a particular control center. Logbook Configuration program gives access to Hedgehog-2 parameters.

11 11 Other Features We would like to mention several other logbook features whose detailed description is beyond the scope of this guide. The login authorization system of the networked version of the logbook is integrated into Microsoft Windows Active Directory. This way, there is a single place for login, password, and privilege configuration across multiple workstations and servers. In a single machine version, the logbook uses local Microsoft Windows accounts for authorization. To prevent data loss in case of hardware failure, a backup logbook server may be running concurrently with the primary server. The backup maintains an up-to-date copy of the database. The data may be further backed up on backup media for storage. Replication Manager of the logbook is a tool used to configure the logbook server configuration,

12 12 replication parameters, depth of database entry storage (how long the old entries need to be stored online before they are moved to backup media) and other parameters. To prevent unauthorized tampering with the database, the logbook implements a security system. This system contains a separate security log that records all database access sessions, entry manipulation events, parameter changes, account creation and other service information. Security Manger is a configuration tool for this system.