5045 TEAM Documentation IM 20111026

download 5045 TEAM Documentation IM 20111026

of 44

Transcript of 5045 TEAM Documentation IM 20111026

ACSELERATOR TEAM

SEL-5045 SoftwareDefine, Acquire, Display, Analyze, Control, and Integrate Your System Data

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

This page intentionally left blank

Table of ContentsOverview of ACSELERATOR TEAM ............................................................................................1About ACSELERATOR TEAM Architecture ........................................................................................................ 1 ACSELERATOR Database ............................................................................................................................... 1 ACSELERATOR TEAM Device Data Collection Service (DDC) ..................................................................... 1 ACSELERATOR TEAM Event Data Translator (EDT)..................................................................................... 2 ACSELERATOR TEAM Translator Manager Service (TMS) ........................................................................... 2 Device Manager............................................................................................................................................. 2 Deployment Sequences ..................................................................................................................................... 2 System Requirements ........................................................................................................................................ 2

Installation........................................................................................................................ 3Installing ACSELERATOR Software ................................................................................................................... 3 General Prerequisites ..................................................................................................................................... 3 Installing a Single-Node Configuration......................................................................................................... 4 Installing a Multinode Configuration ............................................................................................................ 5 Installing a Multitier Configuration............................................................................................................... 5

Getting Started and Managing ACSELERATOR TEAM ...............................................................5Process Overview .............................................................................................................................................. 5 Global Configuration ..................................................................................................................................... 6 ACSELERATOR TEAM DDC Configuration.................................................................................................... 6 Using the ACSELERATOR TEAM Interface......................................................................................................... 7 Working With the Connection Explorer....................................................................................................... 7 Script Manager............................................................................................................................................. 10 Password Manager....................................................................................................................................... 12 Viewing Event Reports .................................................................................................................................... 13 Event Summary ........................................................................................................................................... 13 System Incidents.......................................................................................................................................... 13 Event Data Detail......................................................................................................................................... 14 Functions ..................................................................................................................................................... 14 Preferences................................................................................................................................................... 15 ACSELERATOR TEAM Jobs and Tasks.............................................................................................................. 15 Defining TEAM Jobs..................................................................................................................................... 15 Defining Event Collection Tasks................................................................................................................. 15 Defining User Command Tasks................................................................................................................... 16

RTAC Event Collection ......................................................................................................17RTAC Polling................................................................................................................................................... 18 RTAC Listening .......................................................................................................................................... 18 Security ........................................................................................................................................................ 18

ACSELERATOR TEAM Profile ..................................................................................................18Metering Devices............................................................................................................................................. 18 Metering Point ................................................................................................................................................. 19 Metering Point Data ........................................................................................................................................ 20 Metering Device Association ...................................................................................................................... 20 Metering Data Retention.............................................................................................................................. 21 Metering Data Ownership............................................................................................................................ 21 Metering Data Collection ................................................................................................................................ 21 Time Zones .................................................................................................................................................. 21 Daylight-Saving Time (DST) ...................................................................................................................... 21 Creating a Metering Point ............................................................................................................................... 21 Metering Data Collection Jobs ........................................................................................................................ 23 Setting Up Metering Data Collection Jobs .................................................................................................. 23 Profile Collection Polling Job...................................................................................................................... 23Date Code 20111026AC SELERATOR TEAM SEL-5045 Software

ii

Table of Contents

ACSELERATOR

SER and VSSI Collection Polling Jobs ....................................................................................................... 24 TEAM Metering Data Access................................................................................................ 24

ACSELERATOR TEAM Device Data Synchronization............................................................... 24Introduction ..................................................................................................................................................... 24 Installation ....................................................................................................................................................... 25 ACSELERATOR TEAM Sync Service............................................................................................................. 25 ACSELERATOR TEAM Sync Configuration .................................................................................................. 25 Allowing Remote TEAM Station Access.................................................................................................... 26 First Run ...................................................................................................................................................... 26 Add and Connect to a Destination Station................................................................................................... 27 TEAM Station Layout ................................................................................................................................. 29 Add a Connection ........................................................................................................................................ 31 Remove a Station ......................................................................................................................................... 31 Synchronization Options ............................................................................................................................. 32 Local Station Name ..................................................................................................................................... 33 Edit a Destination ........................................................................................................................................ 33 Key Bindings ................................................................................................................................................... 33

Troubleshooting .............................................................................................................. 34ACSELERATOR TEAM ACSELERATOR TEAM

DDC Is Unable to Start, or Errors Are Generated by the Service ............................... 34 EDT Is Unable to Start, or Errors Are Generated by the Service................................ 34

ACSELERATOR TEAM Glossary

............................................................................................. 35

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

1 Overview of ACSELERATOR TEAM

Overview of ACSELERATOR TEAMThe ACSELERATOR TEAM SEL-5045 Software consists of the ACSELERATOR Database, an Open Database Connectivity (ODBC)-compliant database, used to store normalized event report data; ACSELERATOR TEAM device data collection (DDC), a Microsoft Windows service(s) that automatically retrieves event reports; ACSELERATOR TEAM event data translator (EDT), a Windows service(s) that translates event report files into normalized device data and records this information in the database; an Event Data Viewer, a component that provides event data visualization; ACSELERATOR TEAM translator manager service (TMS), a Microsoft Windows service(s) that manages device data translation; and device configuration via the Connection Explorer in ACSELERATOR QuickSet Device Manager.NOTE: This documentation introduces new, and perhaps unfamiliar, terms specific to this software. For terms not defined immediately following their occurrence within the text, please consult the ACSELERATOR TEAM Glossary on page 35.

About ACSELERATOR TEAM ArchitectureACSELERATOR DatabaseThe ACSELERATOR Database is an ODBC-compliant structured query language (SQL) database that stores all data used by the ACSELERATOR QuickSet Device Manager and ACSELERATOR TEAM Software. The database is the central component in the ACSELERATOR TEAM Software.

ACSELERATOR TEAM Device Data Collection Service (DDC)The ACSELERATOR TEAM DDC is a Windows service that runs unattended and retrieves device data from SEL intelligent electronic devices (IEDs). The DDC uses a direct serial, modem, or Ethernet connection to communicate with devices. Based on your custom installation, the DDC will retrieve event reports and run commands on any device, including non-SEL devices. It can be programmed to retrieve virtually any data from any device that uses ASCII communication and store those data on a computer or network drive. The DDC can also delegate further processing to external scripts (example: Python), allowing actions to be taken in response to user commands (example: emailing breaker wear). Device data retrieval is triggered by a polling frequency (see Polling) or as the result of a listening operation (see Listening) that is executed in response to new event notification from a communications processor, or an endpoint device such as the SEL-734. The ACSELERATOR TEAM DDC has no user interface: its configuration is accomplished using the TEAM node in the Device Manager Connection Explorer. The ACSELERATOR TEAM DDC has been designed to use input/output (I/O) completion ports, which means that all I/O is performed by the operating system via dedicated threads. This permits the DDC to connect to hundreds of devices at once and perform simultaneous communication with all connected devices. Multiple instances of the ACSELERATOR TEAM DDC can be installed on separate personal computers (PCs) to allow for the retrieval of data from thousands of devices simultaneously. An ACSELERATOR TEAM DDC communicates with the ACSELERATOR Database, recording event report retrievals and the names of files containing user command results.

PollingThe ACSELERATOR TEAM DDC can be configured to call SEL devices periodically to check for new events or run customized user-based commands. During this operation, the DDC always initiates the connection.

ListeningWhen the ACSELERATOR TEAM DDC is configured for listening, it monitors modem, serial, or Ethernet communications channels, looking for the notification that occurs when a device (SEL communications processor, for example) detects a new event. Upon notification, the DDC queries the device to discover the set of communications ports that have reported new events to the communications processor. The DDC queries devices connected to those ports and retrieves any new event reports meeting event retrieval conditions. If configured, user commands also run, and the DDC saves the results. The ACSELERATOR Database records event reports and file names for user command results.

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

2 Overview of ACSELERATOR TEAM

ACSELERATOR TEAM Event Data Translator (EDT)The ACSELERATOR TEAM EDT is a Windows service that runs unattended, translates event report data collected by an ACSELERATOR TEAM DDC, and stores these data in the ACSELERATOR Database. When a DDC retrieves an event report, it records the report location in the ACSELERATOR Database and copies the file to the user-specified event report directory. The EDT periodically queries the ACSELERATOR Database to discover newly retrieved event reports. When it discovers a new event report, the EDT opens the event report file, translates the file, normalizes the data, and records the data in the ACSELERATOR Database. While it is usually unnecessary to have more than one PC on which you have installed the ACSELERATOR TEAM EDT service, you can install one copy of the service on each of several PCs.

ACSELERATOR TEAM Translator Manager Service (TMS)The ACSELERATOR TEAM TMS is a Windows service that runs unattended. It discovers the device data files that the ACSELERATOR TEAM DDC collects, and it then parses the device data and records this information in the ACSELERATOR Database.

Device ManagerThe SEL ACSELERATOR QuickSet Device Manager is a device asset management system with two types of configuration views. The device view is a top-level view of where devices are located (e.g., in a region, area, substation); the connection view includes the connection hops to the device for communication. The Device Manager manages devices and connection information, stores the information in the ACSELERATOR Database, and facilitates viewing of device data.

Deployment SequencesThe general sequence of events for deploying ACSELERATOR TEAM Software can be as follows: 1. Install all the necessary components for your configuration (refer to Installation on page 3). 2. Use ACSELERATOR QuickSet Device Manager to add new devices and configure communication. 3. Use theTEAM node in the ACSELERATOR QuickSet Device Manager to define jobs that need to be done throughout the system. 4. Assign one or many jobs to devices that have been created in the Device Manager. 5. Fine tune the system configuration and any related parameters (refer to Installation on page 3).

System RequirementsYou can install ACSELERATOR TEAM Software on a single PC with one ACSELERATOR Database and one instance each of the ACSELERATOR TEAM DDC service and ACSELERATOR TEAM EDT service. Operating system requirements are as follows: 800 MHz or faster processor Microsoft Windows XP with 512 MB RAM, Windows Server 2003, Windows 7 with 1 GB

RAM 1 GB hard disk space Microsoft Internet Explorer 6.0 or greater Default printer installed for printing settings VGA 1024 x 768 or higher resolution monitor Mouse or other pointing device Administrative privileges required for installation Serial or Ethernet connection to allow communication to SEL devices

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

3 Installation

InstallationInstalling ACSELERATOR SoftwareACSELERATOR TEAM

and ACSELERATOR QuickSet components need to be installed on a server or client machine and then configured. You can customize the configuration to suit your needs. The architecture you choose at the time of installation determines subsequent access to each individual component.

This section describes how to install the components of ACSELERATOR TEAM and ACSELERATOR QuickSet applications. You can install these components on the same system, on multiple systems, or in a parent/child multitier configuration. Components can also reside anywhere within an enterprise. Possible installed components on any given machine include the following: ACSELERATOR QuickSet: A front-end interface for the configuration of devices in the Connection

Explorer window. ACSELERATOR QuickSet TEAM Plug-in: A plug-in application for configuring ACSELERATOR

TEAM options. ACSELERATOR TEAM DDC Service: A back-end service that manages communications and the

execution of jobs created by the end user. ACSELERATOR TEAM EDT Service: A back-end service that runs unattended, translates data

collected by an ACSELERATOR TEAM DDC, and stores these data in the ACSELERATOR Database. ACSELERATOR TEAM TMS Service: A back-end service that runs unattended, translates device

data, and records this information in the ACSELERATOR Database. ACSELERATOR Database Server: A back-end server for the SQL database used by ACSELERATOR

TEAM products. The following installed components run as services, which you can monitor, start, and stop with Windows services. ACSELERATOR TEAM DDC ACSELERATOR TEAM EDT ACSELERATOR TEAM TMS ACSELERATOR DatabaseNOTE: If you have a remote connection to an ACSELERATOR Database, then you will have read-only access. You will be able to view location, device, and connection information, and TEAM location and device options. You will also be able to view event reports. However, you will be unable to define system incidents, import events, or enter or modify information in the ACSELERATOR TEAM forms or wizards.

General Prerequisites All the machines on which the components are to be installed should match the hardware and

software requirements listed under System Requirements on page 2. Ensure that Microsoft .NET 4.0 is installed properly. Ensure that your PC is turned on and that all other applications are closed. Once you have reached the User Information window (see the following figure), enter your License

Authorization Code (LAC) number printed on the case label. The installation will contact the license web service automatically. The web service will generate a license file for the application and distribute it to your machine.

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

4 Installation

Figure 1

Enter LAC Dialog

Automated licensing requires an Internet connection. If you do not have an Internet connection, or have difficulties during the licensing process, please read the LicenseInfo.txt file located in the directory where the application was installed. If a license already exists in the installation directory, the application will load the file automatically and continue with the installation. If you have any difficulties installing or licensing the software, contact your customer service representative or the SEL factory for assistance.

Installing a Single-Node ConfigurationIn a single-node configuration, all components are installed on a single PC or server. This configuration can be used for applications that have a limited number of users or for systems that do not require fail-over or load balancing.

ACSELERATOR ACSELERATOR TEAM DDC

Database

ACSELERATOR TEAM EDT

Data Access

ACSELERATOR QuickSet

Configuration

Figure 2

Single-Node Configuration

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

5 Getting Started and Managing ACSELERATOR TEAM

Installing a Multinode ConfigurationIn this configuration, front-end servers and configuration tools are installed on one server, and the back-end servers are installed on one or multiple servers or PCs. A multinode installation facilitates load-balanced and failover configurations.

ACSELERATOR

ACSELERATOR

Database

QuickSet

Server Historian

ACSELERATOR TEAM DDC

ACSELERATOR TEAM DDC

ACSELERATOR TEAM DDC

ACSELERATOR TEAM EDT

ACSELERATOR TEAM EDT

ACSELERATOR TEAM EDT

Collection Server

Collection Server

Collection Server

Figure 3

Multinode Configuration

Installing a Multitier ConfigurationA multitier configuration facilitates centralized management through a single console. It can be designed to support enterprises with collection services running in many different locations.

Getting Started and Managing ACSELERATOR TEAMProcess OverviewWhen the ACSELERATOR QuickSet TEAM plug-in is installed in ACSELERATOR QuickSet, you will see the TEAM node in the Connection Explorer. To select ACSELERATOR TEAM options, navigate to a node in the tree and double-click to display corresponding forms for completing actions. For example, selecting the Event Collection Tasks node will display the Event Collection Tasks tab where you will create and edit event collection tasks. Add device and location nodes in the Connection Explorer by right-clicking in the open area at the bottom of the Connection Explorer, selecting Add, then selecting Device or Location. Select a device from the listing that appears, or select Maintain to define your own custom device type, and click OK to have that device node appear in the Connection Explorer listing. Upon clicking Location, a new location node appears in the Connection Explorer listing. You can also right-click on any device or location node in the Connection Explorer listing, select Add, and then select Device or Location to similarly add a new device or location below the node you originally selected. Double-clicking a specific device node in the Connection Explorer displays a corresponding device tab with four tabs at the left. In the Device tab, provide specific device information such as the FID string and passwords. In the Connection tab, specify device connection and communications information. The Documents tab lets you attach documents with the device. The TEAM tab lets you choose an ACSELERATOR DDC service and assign polling and listening jobs.Date Code 20111026AC SELERATOR TEAM SEL-5045 Software

6 Getting Started and Managing ACSELERATOR TEAM

Double-clicking a location node in the Connection Explorer displays a corresponding location tab with two tabs from which you can define a location and assign ACSELERATOR TEAM polling jobs.

Global ConfigurationDouble-click on the TEAM node in the Connection Explorer to display the TEAM tab. Click on the Global Options tab on the left to display four additional tabs where you can define TEAM options that apply throughout the application.

File Name Templates TabUse the File Name Templates tab to define date and time formats, specify the directory location for event reports (EARCHIVE) and user command results (UARCHIVE), and define the file name template to use when creating event report and user command result files. Click Configure to display the Global Options Wizard. The wizard will guide you through the process of defining global options. Click Apply when finished.

Communications Processor TabThe Communications Processor tab lets you define the parameters necessary for communication with a communications processor such as the SEL-2032. The parameters you can define are as follows: WhoAreYou String: The text sent to a communications processor during listening operations. Logic Bit String: Identifies the logic bit that the communications processor will use during listening

operations. Fault Label: Identifies the name of the fault label the communications processor will use. New Event String: The actual string communications processors send to notify the ACSELERATOR

TEAM DDC of a new event.

Email Server TabThe Email Server tab lets you define the parameters that are used for email notifications. They include the usual: SMTP Server, SMTP Port, and SMTP From Address. If you choose to use POP3 authentication, the usual parameters are POP3 Host, User Name, and Password.

Advanced TabIn the Advanced tab, you can select a date before which event reports will not be collected. You can also choose to save your character encoding (.CEV) event files as COMTRADE files following ACSELERATOR TEAM EDT translation of event report files.

ACSELERATOR TEAM DDC ConfigurationACSELERATOR TEAM DDC is a Windows service that begins operating at installation. The primary responsibility of a DDC is to run device data collection jobs. You can install the DDC service on multiple computers, but only one per computer. The DDC instances work together to retrieve event reports and the results of user commands.

Double-click the TEAM node in the Connection Explorer to display the TEAM tab. Click on the DDC Instances tab to display all instances of the ACSELERATOR TEAM DDC that have been installed. The host computer name displays for each DDC service installation. Right-click on a DDC instance to remove it from ACSELERATOR TEAM. When you select an ACSELERATOR TEAM DDC service, you can use the tabs at the bottom of the form to define or modify service communications connections and archive directories. To add a new ACSELERATOR TEAM DDC connection, click Add to launch the Device Data Collection Wizard. The wizard lets you select the communications method, specify ports, and choose whether to enable listening. To modify an existing connection, select one from the list and then click Edit. To delete a connection, select it and then click Delete. Click the Archive Directories tab to specify where you want the selected ACSELERATOR TEAM DDC to save event reports and user command results.

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

7 Getting Started and Managing ACSELERATOR TEAM

Using the ACSELERATOR TEAM InterfaceWorking With the Connection ExplorerThe ACSELERATOR TEAM welcome screen visible from ACSELERATOR QuickSet and ACSELERATOR QuickSet Designer SEL-5031 Software consists of the following main sections: Connection Explorer Template Palette Status Window

You can open the Connection Explorer by clicking Tools > Device Manager > Device Manager.

Types of NodesDevice Node: This type of node is tied to the equipment configuration within Device Manager. You can configure any available devices within this type (see Editing Device Nodes on page 8). Location Node: Use this type of node for organization. Name these types of nodes in a way that helps you manage your devices.

Managing NodesThis section covers the creation of new nodes regardless of type, editing any node attributes, closing any opened nodes, deleting nodes, finding nodes, and moving nodes within the Connection Explorer window. By using the right-click options via your mouse, you can access all options for managing nodes. Options can vary, depending upon the item you select in the Connection Explorer window. The following options are available for selection from an area within the Connection Explorer window: Add > Device or Add > Location: Add devices or locations anywhere in the Connection Explorer

window. Expand All/Collapse All: Expand or collapse any trees within the Connection Explorer window. Find (): Find any node quickly within the Connection Explorer window.

The following options are available for selection from a device node within the Connection Explorer window: Connect: Connect to the device according to your configuration. Disconnect: Disconnect from the connected device. Device Tasks: Access tasks you would commonly use when you work with ACSELERATOR

QuickSet products. Examples include reading, sending, and opening an HMI. Add > Device or Add > Location: Add devices or locations as subcategories (child nodes) under

the selected device. This setting is available only when you are selecting a communications device. Cut/Copy/Paste: Cut, copy, or paste a selected node. Delete: Delete a selected node and any of its child nodes. Rename (): Rename the selected node. Expand All/Collapse All: Expand or collapse any trees within whichever node you select. Find (): Find quickly any node within the node you select.

The following options are available for selection from a location node within the Connection Explorer window: Add > Device or Add > Location: Add devices or locations as subcategories (child nodes) under

the selected device. Cut/Copy/Paste: Cut, copy, or paste a selected node. Delete: Delete a selected node and any of its child nodes. Rename (): Rename whichever node you select.

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

8 Getting Started and Managing ACSELERATOR TEAM Expand All/Collapse All: Expand or collapse any trees within the node you select. Find (): Find any node quickly within whichever node you select.

MovementYou can use this application to drag and drop devices throughout the Connection Explorer window. Simply select a node, hold down the left mouse button, and drag the node you have selected to the necessary location. The application indicates whether a move is possible for a particular node type. Hold down the key while dragging a node to see more options.

Template PaletteThe graphical user interface (GUI) allows you to drag and drop devices defined in the Template Palette. You can customize individual devices, as well as entire substations, with the Template Palette. The application gives you the option to add or delete any number of subcategories within the Template Palette. To add extra categories, right-click anywhere in the Template Palette and select Add Category. Adding devices to the Template Palette is as easy as dragging and dropping devices into the Connection Explorer window. Simply drag a device or any node from within Connection Explorer and drop that item into the Template Palette to create templates.

Editing Device NodesEdit device nodes by first double-clicking to open the selected device tab, then click the Edit button on the tab that displays to modify any of the node attributes. Click the Apply button to save any changes you make pertaining to the opened node. Click Cancel to cause the Device Manager to ignore all changes you make that you have not applied previously.

Device TabThe Device tab, which displays after you select the tab for a device from among the tabs at the top of the status window, contains tabs that let you define the device, provide device connection information, attach documents to the device, and configure TEAM jobs. Device Type: Select any predefined device types present in the application. If you do not see a device type from the drop-down menu, click the Maintain button to create and edit types according to your requirements. In Service: This option indicates whether the relay is in service. Device Name: User-defined label. Define your own identifier for this entry. Use this field as well as the Find feature to view devices within the Connection Explorer. Serial Number: User-defined label. Use this field typically to identify the serial number of the device. Firmware Version: User-defined label. Use this field to identify the firmware version for the device. Part Number: User-defined label. Use this field to identify the part number for the device. FID String: User-defined label. This field is the firmware identification string for the SEL device. WhoAreYou Response: User-defined label. This field stores any WhoAreYou responses that the selected device sends as necessary. Level 1 Password: User-defined label. This field stores Access Level 1 passwords for the device you select. Breaker Password: User-defined label. This field stores breaker passwords for the device you select. Level 2 Password: User-defined label. Use this field to store Access Level 2 passwords for the device you select. Description: User-defined field. Use this field to add any additional information for a node. Custom Attributes: Custom attributes provide a powerful method for managing your group requirements. The application will predefine some attributes, but you can create or manage extra attributes when necessary. Click the Maintain Custom Attribute Types button to create as many attributes as you need.

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

9 Getting Started and Managing ACSELERATOR TEAM

Connection TabAccess Script: Choose which access script you want Device Manager to use during a connection. Predefined scripts usually populate these values, but you can create and customize the values as necessary. Terminate Script: Choose which terminal script you want Device Manager to use during a disconnect. Predefined scripts usually populate these values, but you can create and customize the values as necessary. Timeout: User-defined label. Define how long a connection should wait to connect. This timeout has a field value in milliseconds. Pass Through Port: User-defined label. Define the number for the port to which the device you select is connected on a pass-through server. Connection Type: Define the type of connection you have to the edited device. See Communication Parameters in the ACSELERATOR QuickSet help for more details on different options.

Documents TabClick the Documents tab to attach documents to the device node. Click Edit to activate the form and then Attach to locate a document. Check the Import box (default) if you want to import the document into the database. You can open a document for reading by clicking Open or double-clicking on the file name.

TEAM TabClick the TEAM tab to set up the communications channel for the device, select a job for the listening operation, or assign polling jobs to the device. A communications channel is the path from an ACSELERATOR TEAM DDC to the device. It defines how the DDC will communicate with the device.

Server Configuration WizardSelect Add from within the TEAM tab to display the Server Configuration Wizard. The wizard will take you through the process of selecting an ACSELERATOR TEAM DDC service and the service connection. You first select the ACSELERATOR TEAM DDC and then the connection that has been defined elsewhere. For example, you may have defined a serial connection on communications Port 2. You can proceed only if the connection selection you make matches the communications channel you already defined.

Listening OperationIf you have set up your ACSELERATOR TEAM DDC for listening operations, then the default listening job for that device will appear in a drop-down list in the middle of the TEAM tab. You can select another job for the listening job if you have defined it, and if it contains an event collection task.

Polling Job Assignment WizardThe Polling Job Assignment Wizard lets you assign jobs for an ACSELERATOR TEAM DDC service to run on a device. Select the tab for a device from among the tabs at the top of the status window, select TEAM, and then click the Add button to launch the wizard. Select the ACSELERATOR TEAM DDC service, choose a polling job from those that have been defined, and define the polling frequency (once, every minute, hourly, daily, and monthly). For example, you can choose to have the DDC run your polling job every four days at 5:00 a.m. You will also choose whether to enable the polling job. Click the Edit button to modify a polling job that has been assigned. If the polling job had been assigned at a location node (or communications processor node) above the device, then you are given the option of having your edits either apply only to this polling job for this device or to this polling job for all those devices that use it and are under the location node. Click Remove to delete the selected polling job for this device only.

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

10 Getting Started and Managing ACSELERATOR TEAM

Editing Location NodesEdit location nodes by first double-clicking to open the selected location tab, then clicking the Edit button to access two tabs from which you can define a location and assign ACSELERATOR TEAM polling jobs for all devices at that location. Click the Apply button to save any changes you make pertaining to the opened node. Click Cancel to cause the Device Manager to ignore all changes you make that you have not applied previously.

Location TabThe Location tab contains options allowing you to provide naming, type, and other identifying attributes for a particular location node. Location Type: Select any predefined location types available in the application. If you cannot find a location type within the drop-down menu, click the Maintain button to create and edit location types according to your requirements. Location Name: User-defined label. You can define the label for this entry. Use this field as well as the Find feature to view devices within the Connection Explorer. Description: User-defined field. Use this field to add any additional information for a node.

TEAM TabClick the TEAM tab to assign polling jobs to all devices at the location you specify (all devices below the location node in the Connection Explorer tree). The same polling job(s) will be used for all devices, but you can modify polling job assignments for an individual device by editing that device node (see Editing Device Nodes on page 8). Click Edit to enable the form. Click Add to add a polling job. To modify a polling job, select that job, then click Edit. Or click Remove to remove a polling job. All operations performed on polling jobs at the location node will apply to all devices below the location node. For example, if you remove a polling job that had been assigned at a location node, that polling job will be removed for all devices under that location node. Or if you change the polling frequency for that polling job, the change will apply to all devices that have that polling job assigned.

Polling Job Assignment WizardThe Polling Job Assignment Wizard lets you assign polling jobs for an ACSELERATOR TEAM DDC service to run on a device. After you first select a location from among the tabs at the top of the status window and click the TEAM tab, click the Add button to launch the wizard. Select the ACSELERATOR TEAM DDC service for the polling job, choose a polling job from those that have been defined, and define the polling frequency (once, every minute, hourly, daily, and monthly). For example, you can choose to have the DDC run your polling job every four days at 5:00 a.m. You will also choose whether to enable the polling job.

Script ManagerScript Manager, which you access by clicking Tools > Device Manager > Script Manager, provides a means for you to manage both your customized scripts and those that come preloaded with the software. Uses for scripts range from device connection to custom maintenance applications. The ability of Script Manager to associate scripts with a device configured in the software provides you a great deal of flexibility when you work with SEL products. Example scripts can vary from simple connections to complex breaker commands. You can build scripts to not only collect information, but also to parse and execute an action.

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

11 Getting Started and Managing ACSELERATOR TEAM

Available CommandsWrite(string, [string, string, string], integer): Use this command to write text to the connected device. Descriptions of command arguments are as follows: Argument 1 is a string containing the text that you want to write to the connected device. Applications interpreting this command and such additions as a carriage return/line feed (CR/LF) will not alter the argument in any way. Use WriteLn if you want to add a CR/LF to the argument. Argument 2 is an array of one or more strings that determines when execution can continue to the next line. If any string in this array appears in the read buffer, execution continues to the next statement. Argument 3 is an integer timeout expressed in seconds. Execution moves to the next statement when this timeout expires, regardless of the contents of the read buffer. WriteLn(string, [string, string, string], integer): This command differs from Write in that it appends a CR/LF automatically to the text to be written. Otherwise, it behaves identically to the Write command. If(string): Use this command for decision making. It takes a single string argument. If that argument (a substring) exists in the read buffer, then execution of the next script line or group of statements occurs. If the argument does not appear in the read buffer, execution continues with the first statement that appears after the next statement or group of statements. IfNot(string): If the string text argument is in the read buffer, then Device Manager executes the next script line or group of statements. This is the inverse of If statement execution. Save(): This command causes Device Manager to save read buffer contents to file. CaptureOn(String): This command causes Device Manager to capture all data written to or read from the connected device. The string argument for this command is the full name of the file to which you will be writing or appending (if the file already exists) the capture. Writing the capture immediately reduces the possibility that helpful troubleshooting information will be lost. CaptureOff(): Turn capturing off. Sleep(integer): Causes the interpreting application to stop processing script commands until expiration of a time interval. This interval, the only argument for the command, is an integer expressing a number of seconds. ExecuteScript(string): Use this command to trigger the execution of an external application, such as a Python script. The argument for this command provides the name of the program or Python script to be executed. ExecuteScript(string, string): This command triggers the execution of an external application such as a Python script. Its first argument provides the name of the program or Python script to be executed. The second argument will be the name of the file containing the data upon which you want the external application or script to operate. Normally, the file you saved previously through use of the Save command contains this information. Halt(string): Terminate script execution through use of this command. The argument for this command, (string), provides text that you can use to log the reason for the termination. GotoLevel(string): This command takes one argument and navigates a device automatically to the specified access level. Its argument will be a string literal that specifies the destination access level. Strings can include the following: ACC: Navigates the device to Access Level 1 BAC: Navigates the device to the Breaker Access Level 2AC: Navigates the device to Access Level 2

GotoPort(): This command takes no arguments, but it issues an ASCII command automatically with the intent of establishing a transparent connection to the device to which the connection script is assigned. The application that interprets the script will be responsible for determining the command (e.g., POR), the port number from which the connection will be made, and any optional parameters (e.g., D for a communications processor direct connection). For instance, if the application using this script must establish a direct connection via Port 2 to make a connection to the scripted device, the ASCII resulting from this command would be POR 2 D. Terminate(): This command takes no arguments, but it issues automatically the control codes used to terminate a transparent connection. The application that interprets the script will be responsible for using tertime1 and tertime2 during termination of the transparent connection. For instance, if the application using this script needs to terminate a transparent connection via (code \004), the application must at least wait the second delay time before checking to see if the transparent communication has been terminated.Date Code 20111026AC SELERATOR TEAM SEL-5045 Software

12 Getting Started and Managing ACSELERATOR TEAM

LogMessage(message): Use this command to log a message to file. Each existence of this command in a script logs to the same file. For instance, if the application using this script comes across the first instance of this command, the application creates the log file and logs the message. Each subsequent instance of this command will use the same file-to-log messages. The next execution of this script will produce another log file.

Available Variables_GetPortNumber(): The script interpreter replaces this variable with the actual communications port number that the script will use. For instance, if a connection was using port number 2, then Send(POR + _GetPortNumber() + D would result in the script interpreter sending the following command to the device POR 2 D _GetPassword(Title): The script interpreter replaces this variable with the decrypted password from the database device_password table. For instance, assume that the following line appears in the script: WriteLn(_GetPassword(Default_ACC) Assume also that the device_password table contains a record where the title is Default_ACC and a password value that, after decryption, will be the string Password. The script interpreter would then send the word Password, followed by a CR/LF, to the device. _GetUserName(Title): The script interpreter would replace this variable with the username in the device_password database table for which device_password.title equals argument Title. For instance, if the following line appeared in the script: WriteLn(_GetUserName(Default_ACC) the device_password table contained a record where title was Default_ACC, and a username was ACC, then the script interpreter would send the word ACC, followed by CR/LF, to the device. _TerminateString(): The script interpreter would replace this variable with the control codes necessary to terminate a transparent connection.

Password ManagerUse the Password Manager, which you access by clicking Tools > Device Manager > Password Manager, to manage global passwords you create. Use these passwords within any script you create for connections. In creating names and passwords for use with scripts, for example, an administrator who wants to hide passwords from a user can create within the system global passwords that users cannot view.

ExamplesUser-Based CommandsSER 100 Collection Script

SEL.GotoLevel(ACC) SEL.WriteLn(SER 100,[=>],60) SEL.Save()MET H Collection Script

SEL.GotoLevel(ACC) SEL.WriteLn(MET H,[ =>],60) SEL.Save()BAT Collection Script

SEL.GotoLevel(ACC) SEL.WriteLn(BAT,[=>],60) SEL.Save()

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

13 Getting Started and Managing ACSELERATOR TEAM

Viewing Event ReportsWith the ACSELERATOR TEAM Events viewer, you view, organize, import and export, and print event report data from the ACSELERATOR Database. To view collected event reports, right-click on a device node or location node from within Device Manager and select View Events. The events associated with the selected device are displayed. Use the several tabs on the left of the Viewer tab to view and organize your event report data.

Event SummaryIn the Event Summary tab, you can view summary information about an event report. The data display in a grid format, with each row representing data from one event report. You can organize the data easily to suit your preferences by ordering columns (left-click and move) and ordering rows (sort by column heading). Additional options are available by right-clicking on a column header. In the Event Summary tab, you can acknowledge an event report to indicate that you have viewed it. Note that you can hide acknowledged events by checking the Hide Acknowledged Events check box at the top of the Event Summary tab. Several options are available by right-clicking on a selected row in the Event Summary tab. They include the following: View Event Data: Takes you to the detailed data view for that event report. Create System Incident: Lets you define a new system incident (see System Incidents on page 13). Export as COMTRADE: Creates an ASCII COMTRADE file from the event report data. Save Copy of Original Report: You will be prompted for a directory location. Save Copy of Original Reports As Single File: Saves multiple event reports into a single file when

you select multiple rows. You will be prompted for a file name to save as. Print All Summaries: Prints all event summaries in the summary view. Print Selected Summaries: Prints selected event summaries in the summary view. Export All Summaries: Exports all summaries that appear in the summary view in Microsoft

Excel format (.xls), or another format of your choice. Export Selected Summaries: The selected summaries will be exported in Microsoft Excel format

(.xls), or another format of your choice. Import Events: Prompts you for location of event report files you want to import. Refresh Grid: Necessary after import operations that added new data to database. Delete Event: Removes specified event data from the database.

System IncidentsThe System Incidents tab is a powerful feature of the ACSELERATOR TEAM Events viewer that lets you define a system incident, e.g., a tornado, and select event reports to associate with that system incident. The top of the tab displays defined system incidents. Selecting an incident displays information about that incident to the right. The Filter Incidents dialog box lets you choose incidents to view by type, date, and location. For example, you can choose to see outages between June 1 and September 1 for a specific area. There are several buttons that let you define system incidents, view their event data, and print reports. Define New: Displays the Define New System Incident dialog box, in which you name the

incident, define or select the type and location, give a description, and define the start/end date/time of the incident. From the Device Events grid view, you can check which events to associate with the incident. You can also associate a document with a system incident by clicking the Select Document button and selecting a file to associate. Edit: Lets you edit a system incident that you defined previously.

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

14 Getting Started and Managing ACSELERATOR TEAM Print: Prints a system incident report. A print preview displays the formatted report and a menu bar

with additional options. For example, from the File menu you can choose Export Document to save the file in a variety of file formats. You can also choose to email the report. View Event Data: Takes you to the Event Data Detail tab (described below) with the events

associated with the selected system incident. Remove: Deletes the selected system incident. Open Document: When you select a system incident and it has an associated document, the file

name path will be displayed. Click the Open Document button to open the document for display.

Event Data DetailThis tab presents detailed data from the selected event report. The top grid displays summary data for each event report. When you select a row, the lower grids display detailed data for that report. The Min/Max Analog Values grid displays the minimum and maximum values for each analog channel. Left-clicking on the column headers will toggle the row order (ascending/descending). Right-clicking on a column header presents more advanced sorting and grouping options. By right-clicking on a selected row, you can choose to view the data sample that has that minimum or maximum value. The row in the Sample Data grid to the right will be highlighted. The specific value (min or max) will not be highlighted. If multiple analog samples have the same minimum or maximum value, a pop-up dialog box will appear that allows you to select the row sample to display. The Sample Data grid displays all the data for the selected event report. Each row represents one sample time. You cannot reorder these columns, but you can toggle the row order by left-clicking on a column heading. You can expand an unexpanded column heading by moving your mouse cursor over the heading. Right-clicking on a column header presents more advanced sorting and grouping options. Several options are available by right-clicking on a selected row in the Event Summary tab. They include the following: Launch Waveform Analysis: Launches an analysis application such as the ACSELERATOR

Analytic Assistant SEL-5601 Software with the selected event report. Note that you must first use the Preferences tab to select a viewer you want to use. Create System Incident: Lets you create a system incident and add this event to that incident. Export as COMTRADE: Creates an ASCII COMTRADE file from the event report data. Save Copy of Original Report: You will be prompted for a directory location. Print All Summaries: Prints all event summaries in the summary view. Print Selected Summaries: Prints selected event summaries in the summary view. Export All Summaries: Exports all summaries that appear in the summary view in Microsoft

Excel format (.xls), or another format of your choice. Export Selected Summaries: The selected summaries will be exported in Microsoft Excel format

(.xls), or another format of your choice.

FunctionsFrom the Functions tab you can invoke special ACSELERATOR TEAM functions. Currently, the only function available lets you import event reports (.CEV or COMTRADE files). Selecting Import Event Reports displays a dialog box that lets you locate the file to import. After selecting the file, another dialog box lets you associate the event report with a specific device. Clicking OK will import the file and return you to the viewer. If the file to import contains multiple event reports (.CEV files only), ACSELERATOR TEAM will import them as separate files. To view the event summaries for these reports, right-click on the associated device and select View Events, or, if not associated, right-click below the device tree and select View Events (the software may need you to close the viewer first). To further identify files imported from a multiple events file, right-click on a column heading and select the Column Chooser. In the Column Chooser, select Event Number. This will display a new column containing the order of the event report in the file.

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

15 Getting Started and Managing ACSELERATOR TEAM

PreferencesIn the Preferences tab, you can restore the default layout view and select the waveform viewer to use when launching a waveform analysis application such as the ACSELERATOR Analytic Assistant. Note that if you have not selected a waveform viewer before attempting to launch it, you will receive a warning in the status window.

ACSELERATOR TEAM Jobs and TasksThe ACSELERATOR TEAM DDC processes user-defined jobs. All jobs run independently, thus allowing the software to optimize data collection from supported devices. Each job consists of one or many tasks that can collect event reports and run user-based commands. You can set up event collection jobs to poll devices at specific date and time intervals, or listen for incoming calls from communications processors or Ethernet connections. An ACSELERATOR TEAM job consists of a list of device tasks that run to carry out polling or listening operations on IEDs. There are two types of device tasks: 1) data collection and 2) user command. A device data collection task is an operation to collect specific types of device data from IEDs. Device data types include event reports; Sequential Events Recorder (SER) reports; load profile reports; voltage sag, swell, and interruption (VSSI) reports; and metering data. An event collection task can be defined to collect standard .CEV quarter cycle , standard .CEV long, and COMTRADE event reports. The first release of ACSELERATORTEAM will support event collection tasks only, although you can apply user commands toward reading other types of data. A user command task issues a user command to a device. Types of user commands include STA, SET, PASSWORD, SER, TRI, and BRE. Use the TEAM Device Scripting Language to define user commands in user command scripts. A script editor lets you easily create a script of user commands and verify the syntax. The following sections will take you through the process of defining jobs, defining event collection tasks and user command tasks, associating tasks with devices, and assigning tasks to jobs.

Defining TEAM JobsSelect the TEAM > Jobs node to display the Jobs tab. ACSELERATOR TEAM ships with a default event report listening job for every supported device. Click Create to create a new job. The Jobs Wizard will step you through the process of naming the job, adding event collection or user command tasks, and setting up the file name templates. The Edit button lets you edit an existing job, and Delete will delete the selected job.

Defining Event Collection TasksYou can define an event collection task by navigating to the Event Collection Tasks node under the TEAM > Jobs node. Double-click to display the Event Collection Tasks tab. In this tab, you will define your event collection tasks, the device-specific commands that the task will execute, and the device types that can accept the commands. For example, the default 1/4-Cycle Task has the command Standard CEV Quarter Cycle that defines the CEV # command that can read compressed event reports from an SEL device.

Event Collection TasksIn the left column, you can select or define a task. There are three defined default tasks that apply to three types of event reports. You can click the Edit button to change a task name or the Create button to add a new task. You can delete a task by selecting the task and clicking the Delete button.

Event Collection CommandsAfter you have selected a task, you can then define the commands for that task to execute in the center column. When you select a command name, the actual command displays in the area immediately below. For example, for the default command named Standard CEV Quarter Cycle the specific device command CEV # displays in the Command area. Click the Create button to create a new command or the Edit button to modify an existing command. The Event Collection Command Wizard will help you to define an event collection command (see Event Collection Command Wizard).

Device Type AssignmentsAfter you have defined a task and its commands, you need to specify the device types that support each command. In the right column, you can define the device types to assign to your command names.Date Code 20111026AC SELERATOR TEAM SEL-5045 Software

16 Getting Started and Managing ACSELERATOR TEAM

First select a task and then a command name. Then click the Edit button (in the Device Types column) to display the Event Command Assignment dialog box. Use the arrows or cursor to locate the devices you want to assign. Click >> to assign a device to the event command name. You can remove a device by selecting and clicking ], 45) SEL.Save() Click Create to create a new script or Edit to modify an existing script. Performing either act launches the User Command Script editor. Click Edit to activate the editor. Enter a name for the script. In the Script Text window, type SEL. exactly as shown to display a list of allowable SEL scripting language commands. Select the command you want by doubleclicking on the command. Click Enter to move to the next line. You can click Check Syntax at any time to check the syntax of your script. You can also enter a description for your script. Click Apply when finished. You return to the User Command Tasks tab with the script displayed with its associated script name.

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

17 RTAC Event Collection

User Command Script AssignmentsAfter you have defined a task and its scripts, you need to specify the device types for which the scripts are targeted. In the right column, you define the device types to assign to your script names. You first select a task (from first column) and then a script name. Then select Edit (in the right column) to display the User Command Assignment dialog box. Use the arrows or cursor to locate the devices you want to assign. Click >> to assign a device to the User Command Script Name. You can remove a device by selecting and clicking Jobs node in the Connection Explorer to view these jobs.

Metering DeviceA device (IED) connected to a region of common measurement (RCM) that collects metering data. An SEL-734 is one type of metering device. Multiple metering devices can collect data from the same metering point. Some metering devices can collect data from multiple metering points.

Metering PointA device- and location-independent entity that represents a set of measurements of a particular type that ACSELERATOR TEAM collects from an RCM. A metering point represents the point in the electrical system at which a metering device is connected to measure power system quantities, namely voltage and current.

Metering Point WizardThis wizard enables you to create and manage metering points.

New EventA text message a communications processor sends via a communications channel to an ACSELERATOR TEAM DDC service to notify the DDC that one or more connected devices has reported a new event.

Polling FrequencyThe frequency at which a a device executes a polling job to determine whether a new event report exists.

Polling JobA scheduled task that executes a predefined set of commands and saves the command results according to a polling frequency. A polling job services only one device as the result of the polling frequency. Individual devices can have multiple polling jobs.

Polling Job Assignment WizardThe Polling Job Assignment Wizard lets you assign jobs to an ACSELERATOR TEAM DDC service. You can access this wizard from the TEAM tab within the tab for a device you select in the Connection Explorer.

Profile Collection Polling JobAn ACSELERATOR TEAM polling job that you can schedule to retrieve profile data from SEL devices that ACSELERATOR TEAM supports. A typical profile collection polling job will collect load profile data from SEL734/735 metering devices.

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

38ACSELERATOR TEAM Glossary

Profile DataRefers primarily to load profile (LDP) data that several SEL devices generate, particularly the SEL-734/735 device families. These devices generate load profile binary files that ACSELERATOR TEAM retrieves, translates, and stores in the ACSELERATOR Database.

Region of Common Measurement (RCM)A physical region within an electrical power infrastructure from which any two measurements of the same quantity taken at the same time instant will always yield the same value (allowing for some margin of error).

Script ManagerThe Script Manager is a component within the SEL ACSELERATOR TEAM Device Manager to manage the users connection scripts for such things as connecting to and disconnecting from devices.

SEL-5040 Event Summary DatabaseThe Microsoft Access database resulting from ACSELERATOR Report Server SEL-5040 installation. It contains summary information describing power system event reports the SEL-5040 has retrieved. It also contains corresponding pathnames to event report files.

SER Collection Polling JobAn ACSELERATOR TEAM polling job that you can schedule to retrieve SER data from SEL devices that ACSELERATOR TEAM supports. A typical SER collection polling job will collect SER data from SEL-734/735 metering devices.

SER DataMost SEL devices generate Sequential Events Recorder (SER) reports. ACSELERATOR TEAM retrieves, translates, and stores SER reports in the ACSELERATOR Database.

ServiceA software application that can begin as soon as the computer starts. It runs as long as the computer has power, and it needs no direct user input. A Microsoft Windows operating system would have Windows services, while a Linux operating system would have Daemon services.

System IncidentA powerful feature of ACSELERATOR TEAM that lets you define a system incident (a tornado, for example) and select event reports to associate with that incident. A system incident will typically cause one or more device events.

TaskOne specific action a job performs to retrieve one collection of device data or execute one user command. An example of a task would be retrieving a single event report or executing a single user command. Whereas jobs are containers for all operations the ACSELERATOR TEAM DDC performs during a listening or polling operation, tasks are the individual operations a job contains.

TEAM Device Scripting LanguageAn SEL proprietary scripting language the ACSELERATOR TEAM DDC uses to establish communication with devices and to run user commands.

TEAM JobAn operation the ACSELERATOR TEAM DDC performs and which results from a polling or listening operation that causes execution of one or more tasks. A TEAM job consists of a list of device tasks that run to carry out polling or listening operations on IEDs. There are two types of device tasks: 1) data collection and 2) user command. Each job consists of one or many tasks that can collect event reports and run user-based commands. You can set up event collection jobs to poll devices at specific date and time intervals or to listen for incoming calls from communications processors or Ethernet connections.

AC SELERATOR TEAM SEL-5045 Software

Date Code 20111026

39ACSELERATOR TEAM Glossary

A job consists of two lists. The first list enumerates the event report collection tasks the job is to execute. The second list enumerates the user command tasks the job is to execute. For every job, there will be at least one task definition. For event report collection jobs, there will be at least one event report collection task definition.

Template PaletteThe graphical user interface (GUI) that allows the user to drag and drop devices the Template Palette defines. You can use the Template Palette to customize individual devices, as well as entire substations.

Transparent ConnectionA transparent connection provides a data tunnel between two or more Ethernet or serial communications ports.

User CommandAn ASCII or File Read command that an ACSELERATOR TEAM DDC sends to a device with the purpose of retrieving device-related data and saving those data to a local file, or of executing a command (e.g., getting device status).

User Command ResultsThe result of executing a user command. This is either an ASCII capture saved to a file or files that were transferred from the device.

User Command Script EditorThe Script Editor lets you easily create a script of user commands and verify syntax. Access the Script Editor by selecting User Command Scripts under the TEAM > Jobs node in the Connection Explorer.

User Command TaskSpecifies the actual script that executes when a job-specified user command type is to be executed. An operation to issue a user command to a device. Types of user commands include STA, SET, PASSWORD, SER, TRI, and BRE. Use the TEAM Device Scripting Language to define user commands in user command scripts.

User Command TypeA classification of user commands based on function (e.g., device status, breaker, SER). Categorization of every user command occurs through use of a single user command type. Every user command will be associated with one, and only one, user command type. SEL can specify user command types at product release. Users can also define new user command types.

UTCCoordinated Universal Time. ACSELERATOR TEAM converts all metering data timestamps to UTC before recording data in the ACSELERATOR Database.

VSSI Collection Polling JobAn ACSELERATOR TEAM polling job that you can schedule to retrieve VSSI data from SEL devices that ACSELERATOR TEAM supports. A typical VSSI collection polling job will collect VSSI data from SEL-734/735 metering devices.

VSSI DataSEL devices such as the SEL-735 generate VSSI reports. ACSELERATOR TEAM retrieves, translates, and stores VSSI reports in the ACSELERATOR Database. ACSELERATOR TEAM stores both summary and detailed VSSI data.

VSSI Detailed ReportThe detailed VSSI report that includes a point-by-point record of each VSSI value. This report can be useful for postdisturbance graphing of data.

2011 Schweitzer Engineering Laboratories, Inc. All rights reserved.

Date Code 20111026

AC SELERATOR TEAM SEL-5045 Software

This page intentionally left blank