Chapter 04 - User Access Management

8/11/2019 Chapter 04 - User Access Management

1/17

ETAP

PowerStation4.0

User Guide

Copyright 2001

Operation Technology, Inc.

All Rights Reserved

This manual has copyrights by Operation Technology, Inc. All rights reserved. Under thecopyright laws, this manual may not be copied, in whole or in part, without the written consent of

Operation Technology, Inc. The Licensee may copy portions of this documentation only for the

exclusive use of Licensee. Any reproduction shall include the copyright notice. This exception

does not allow copies to be made for other persons or entities, whether or not sold. Under this

law, copying includes translating into another language.

Certain names and/or logos used in this document may constitute trademarks, service marks, or

trade names of Operation Technology, Inc. or other entities.

Access, Excel, ODBC, SQL Server, Windows NT, Windows 2000, Windows Me, Windows

98, Windows XP, and Microsoft Word are registered trademarks of Microsoft Corporation.

AutoCad is a registered trademark of Autodesk. Oracle is a registered trademark of Oracle Corporation.

PowerPlot is a registered trademark of Jackson & Associates.

Crystal Reports is a registered trademark of Seagate Software.

MATLAB and Simulink are registered trademarks of MathWorks

Screen shot(s) reprinted by permission from Microsoft Corporation.

Operation Technology, Inc. believes that the information contained herein is accurate as of its

publication date, and such information is subject to change without notice. This information is

provided as is without warranty of any kind, either expressed or implied, including but not

limited to the implied warranties of merchantability, fitness for a particular purpose, or non-

infringement. Operation Technology, Inc. assumes no responsibility for errors or omissions in

this publication or any other documents referenced in this publication.

Operation Technology, Inc.Southern California

(949) 462-0100 Sales

(949) 462-0400 Fax

(949) 462-0400 User Support


2/17

Chapter 4

User Access Management

PowerStation relies on two tiers of user access control to provide program security. The first level is

provided by the operating system under which PowerStation is running (Windows 98, NT, 2000, Me, or

XP). In the case of Windows NT, 2000, or XP, the user must be an authorized user as determined by the

operating system administrator. When using Windows 98 or Me, the user must have logged on the PC

with a valid user ID if one is required by the operating system.

Operation Technology, Inc. 4-1 ETAP PowerStation 4.0


3/17

PowerStation provides the second level of access control by assigning one or more of the nine access

level permissions available in PowerStation to an authorized user for each individual project. These

access levels are:

Off-Line


(PowerStation)

On-Line


(PSMS)Administrator X X

Project Editor X X

Base Editor X -

Revision Editor X -

Checker X -

Browser X -

Librarian X -

Controller - X

Operator - X

Users may be assigned one, all, or any combination of access level permissions, but each user must have

at least one access level permission to open a project. The level of access and responsibility are differentfor each permission. A user may access a project under only one permission level at a time.

If a password is not required for a project, PowerStation will automatically default to the highest assigned

permission level for that user and open the project. While passwords are recommended for optimal

security, they are not required.

The Administrator is responsible for assigning and maintaining the status of the other users and their

permissions and passwords only. As an administrator, you do not have access to the project one-line

diagram, underground system, or editors. The first level of authority on a given project is Project Editor,

which has access to all functions except disabling accounts and changing passwords.

It should be noted that Project Editors and Base Editors CANNOT be Checkers for the same engineering(equipment) data that they have added or modified. You can have access to the same project as a Checker

(if Checker access level permission has been assigned to you), but you cannot check the same data that

you have modified.

The PowerStation libraries, which are stored in Microsoft compound files, are opened in Read Only mode

for all access levels except Project Editor and Librarian. Project Editor and Librarian can open the

libraries in Read/Write mode. Consequently, only one user can access a library at any given time.

Changes made to the PowerStation libraries are not permanent until the user saves the entire library,

either explicitly or when prompted while quitting the program.

PowerStation project data are stored via ODBC (in non-exclusive mode) and CANNOT have multiple

readers or writers at the same time. PowerStation data is structured in such a way that transactioningsupport by the database is not required.

This chapter consists of the following sections:

Access Levels

User Management Creating A New Project File Opening An Existing Project File



4/17

User Access Management Access Levels

4.1 Access LevelsWhen a PowerStation project file is created or opened, there are several functions that can be done with

each device or the entire project. The use of these functions varies for different access levels. These

functions can be categorized in two groups:

Group 1 Changes Group 2 ChangesMove Elements Add (Drop) Elements

Change Element Sizes Cut (Delete) Elements to Dumpster

Change Element Symbols Copy Elements to Dumpster

Change Element Annotation Orientation Paste Elements from Dumpster

Edit Engineering Properties Move Elements from Dumpster

Change Operating Status Connect Elements

Hide or Show Protection Devices Purge Elements from Dumpster

Autoroute Connections Re-sizing Elements (UGS)

Change Bus to Node Symbols or the reverse Merge Data Revisions to Base Data

Purge Data Revisions

Merge Data Revisions to other Revisions

4.1.1 AdministratorThe Administrator access level is only for user management and cannot access projects for editing. This

means that an Administrator can access any project file for administration purposes, but not for editing

the project. The Administrator is responsible for establishing and maintaining all user access control on aspecific project basis. The Administrator can:

Add, modify, or delete user accounts and passwords

Add, modify, or delete user access levels

The Administrator cannot delete himself/herself or a user while he/she has a project open and running.

Once assigned, only the Default Administrator, Admin, may delete a user from the Administratorpermission. Also note that if two or more administrators have been assigned to a project, one can delete

the other.

Every project must have at least one user with Administrator access. There is a permanent administrator

with the user ID Admin that cannot be deleted from the project. When you create a new project, the

password for Admin is defaulted to password. Note that if a project requires a password and Admin is

the only administrator, if you change the password for Admin and forget the password, you cannot add,

delete, or modify user access levels for this project, i.e., you cannot open this project; there is no back

door around this. We recommend that either you do not require a password, do not change the Admin

password, or that you have multiple Administrators and record your password.

4.1.2 Project EditorProject Editor is the highest access level to project files. When a new project file is created, PowerStation

will automatically log you in as a Project Editor.



5/17


In the on-line mode (PowerStation Management System, PSMS) the Project Editor constructs the project

database, creates and audits field equipment software interfaces, and can upload the database to the PSMS

Server. The Project Editor can perform any function involved with the engineering, installation, or

operation of PSMS, including taking the system off-line and performing control operations (if equipped.)

Project Editor is the highest access level to project files.

Can Change CANNOT ChangeUser Access Management X

Project Data / Defaults XBase Data X

Revision Data X

Group 1 Changes X

Group 2 Changes X

Configuration Status XLibrary Data X

Library Path X

4.1.3 Base EditorBase Editor access is more restrictive than Project Editor access. The Base Editor cannot change the

library data nor access the User Access Management functions.


Project Data / Defaults X

Base Data X

Revision Data X

Group 1 Changes X

Group 2 Changes X

Configuration Status X

Library Data XLibrary Path X

4.1.4 Revision EditorRevision Editor access is more restrictive than the Base Editor. The Revision Editor can change Revision

Data only, i.e., the Revision Editor cannot change Base Data.



Base Data X

Revision Data XGroup 1 Changes X

Group 2 Changes X


Library Data & Path X



6/17


Note that you need to access a project as a Project Editor or Base Editor in order to add or rearrange the

one-line diagram or the underground raceway systems. Revision Data reflects the difference (delta)

between the engineering properties in the Base and Revision Data. Therefore, if a new substation needs

to be added and studied for future installation, you need to add it to the system as a Base Editor. The

elements in this substation can be flagged Out of Servicefor the Base Data so they would not change the

results of the existing system.

4.1.5 CheckerChecker access level is provided for verification of the engineering properties for both Base and Revision

Data.

Can Check CANNOT ChangeUser Access Management X


Base Data Yes X

Revision Data Yes X

Group 1 Changes X

Group 2 Changes XConfiguration Status X

Library Data X

Library Path X

When you logon as a Checker, you are provided with a Checker dialog box (as shown below) to verify

changes to the engineering properties.

Checker dialog box for Cable 11before and after it is checked by a user



7/17


Edited By

Displayed here are the user name (ID) and the date that the properties of the selected element(s) were last

changed. In this case, the last user who has modified Cable11is OTI on 4-17-2000. Note that OTI might

have changed one or a number of properties of Cable11.

Checked By

After you click on the Check button, your user name (ID) and the date are stamped as the checker for this

element and displayed here. In this case the user name is MyName, who has checked this element on 4-

20-2000.

Filter By

Use this command to select the elements you wish to check from the pop-up list provided by

PowerStation.

Element Type

Select from the list box which elements you want to view for checking. This list includes:

Entire System

All Generators & Loads

All Branches

All Protective Devices

All Meters

All DC Elements

Dumpster

Individual AC Elements

Individual AC-DC Elements

Individual DC Elements

Individual UGS Elements

Composite Motors

Composite Networks

Skip Checked Elements

Use this command if you do not want to view elements that have already been checked.

Date

Use this command to display a range of dates when changes have taken place. You can change the dates

by clicking on Select Datesand entering new dates, as shown below:



8/17


Display EditorsUse this command to display the editors for the elements that you are checking. From the editor, you see

any change or modification of individual fields displayed in red.

Check/Uncheck Data

When you click on the Check button, the color changes to blue and a red check mark appears in the

corner. If you click again, it will uncheck the selected element.

Check All

Press this button to check all unchecked elements. PowerStation requests confirmation for this command.

Controlled Dumpster

The controlled dumpster is a mechanism for locking information into the dumpster and is used only when

the PowerStation project is passwords-enabled.

When PowerStation cuts any elements from a UGS or OLV, the dumpster cell to which the elements are

assigned is designated as a controlled dumpster cell. When the dumpster cell is designated as a controlleddumpster, the designation has NO meaning unless the project is passwords enabled.

When passwords are enabled, the controlled dumpster is treated as a special entity with the following

attributes:

1. The controlled dumpster is displayed as a controlled dumpster by displaying the designation (C) or

(CC) on its title (in the Dumpster list window).

The designation C (Controlled Dumpster Cell) is used to indicate that this is a controlled

dumpster cell which is not checked. These cells cannot be purged until they are checked.

The designation CC (Checked Controlled Dumpster Cell) is used to indicate that this is a

controlled dumpster cell and it has been checked by a checker. A user with Project or Base Editorpermissions can purge these cells.

2. The background of a (C) controlled dumpster is painted the color of INI values, ControlUGSColor or

ControlOLVColor. The background is painted in the specified color only when the project setting has

Project/Options/Display changed data in RED selected or the project user is a Checker.



9/17


3. When moving a cell from a controlled dumpster to the one-line diagram or UGS, two

behaviors are exhibited:

If the controlled dumpster cell is a (C) dumpster, the elements are simply moved as normal, i.e., no

special action is taken to flag elements checked or unchecked. The dumpster cell is then destroyed

as normal.

If the controlled dumpster cell is a (CC) dumpster, the elements are moved as normal but, in

addition, all property values are forced dirty and are flagged as unchecked (will show red in the

editors). This is, for all purposes, identical to dropping a new element on the one-line diagram or

UGS. The dumpster cell is then destroyed as normal.

4. When in checker mode, the controlled dumpster cells appear in the checkers list and can be

checked as any other element can be checked. The act of checking a controlled dumpsterchanges its designation from (C) to (CC). This also sets the dumpster background color to

normal.

5. A Project Editor (or Base Editor) cannot purge a controlled dumpster with designation (C).

The Project Editor can purge a controlled dumpster with designation (CC). The checkermust check a controlled dumpster cell before it can be purged.

4.1.6 BrowserBrowser access level does not allow any modification of the project or library data. With this access level

you can view the one-line diagram and underground raceway systems, browse the editors and libraries,

and print.


Project Data / Defaults XBase Data X

Revision Data XGroup 1 Changes X

Group 2 Changes X

Configuration Status XLibrary Data X

Library Path X

4.1.7 LibrarianThe Librarian can browse the project file and modify the library data.

Can Change CANNOT Change

User Access Management XProject Data / Defaults X

Base Data X

Revision Data X

Group 1 Changes X

Group 2 Changes X


Library Data X

Library Path X



10/17


4.1.8 OperatorOperator access level is used for on-line mode. Operator access level allows the user to acknowledge

alarms, playback system actions, and run simulation studies (predicting system response to operator

actions) based on the latest system or stored data.

4.1.9 ControllerController access level is used for on-line mode. Controller access level gives the user the authority to

control, take elements out of service, set operating limits, set alarm levels, and set PSMS to supervisory

control, in addition to the permissions that an operator has.

The Controller can perform operations for monitoring and control of the electric system. The Controller

is restricted from reloading the PSMS Server database. The Controller can take the PSMS system off-

line, save the console database, perform electric system control operations, and pin protective devices and

meters.



11/17

User Access Management User Management

4.2 User ManagementThe User Manager dialog box will come up when you logon as an Administrator.

As an Administrator you can add, modify, and delete user accounts, but cannot access the project itself.

To access the project, you must close the User Manager dialog box and re-open the project with another

access level. There is a permanent administrator with the user ID Adminthat cannot be deleted from the

project. When you create a new project, the password for Admin is defaulted to password.

4.2.1 Change PasswordClick on this button to change the password of a user. Passwords can be up to 12 characters long.



12/17


4.2.2 Disable PasswordClick on this button to enable, disable, or change the password requirements for this project.

Project files can be set up with or without user password requirements. Passwords are recommended for

optimal security. If a password is required, every user must enter their user name and password beforeaccessing the project. If a user forgets their name or password, the project administrator must reset the

passwords. If a password is not required for a project, PowerStation will automatically add the user name

to the user list for the project and default to the highest assigned permission level (Project Editor) and

open the project.

Every project must have at least one user with Administrator access. There is a permanent administrator

with a user ID Adminthat cannot be deleted from the project. When you create a new project, the default

password for Admin is password. Logon as Admin to open the User Manager dialog box to disable or

enable the password requirement at any time.

4.2.3 User InformationThe User Information dialog box allows you to add new users or modify existing users (full name and

password), and assign various combinations of access level permissions. This dialog box is similar to the

one that you get when you create a new project, except here the Administrator can delete users and

disable user accounts.

User Name

The logon user name is displayed here. The user name cannot be changed from here.



13/17


Full Name

Enter or modify the full name of the user here. This information will not be printed in any report and is

only available to the project administrator for identification of users.

DescriptionThis field is used to describe the type of user for further identification by the project administrator and

will not be printed in any report. For projects that do not require a password, the default for this field is

Instant User.

Access Level Permission

Select one or all access levels permitted for this user.

OK

Saves the information on the page to the access list.

DeleteThis button is active when you bring up the User Information dialog box from the User Manager dialog

box. The Delete button is used to delete a selected user from the user list.

4.2.4 Add UserThe Add User dialog box is similar to the User Information dialog box except you can enter the user

name and password.

4.2.5 ODBC Parameters



14/17


Driver Options

Buffer SizeThe Buffer Sizeis the internal buffer, in kilobytes, that is used to transfer data to and from PowerStation

to the associated project database. The PowerStation project default for the Buffer Size is 4096.

Page TimeoutThe Page Timeoutspecifies the period of time, in tenths of a second that an unused page of data remains

in the buffer before being removed. The PowerStation project default for the Page Timeout is 600.

Database

The User ID andPasswordare associated with the database itself. When you open the database using a

third party database manager (such as Microsoft Access), the database will require the User ID and

Password to open it. This User ID and Password are not to be confused with the PowerStation logon and

password, which enable you to open and edit the PowerStation project.

User IDThis is where you input the third party database managers User ID.

PasswordEnter the third party database managers password to authorize the proper access level to the project.

Oracle Database

The Connect String (DBQ) must be entered here in order to associate this PowerStation project database

with your Oracle file server system. The default DBQ is setup for a personal Oracle database. If the

Oracle database is different, then the correct DBQ and User ID must be specified here. Contact your

database administrator for these parameters.



15/17

User Access Management Creating A New Project File

4.3 Creating A New Project FileTo create a new project, click on New Project in the File menu or the first button on the Project Toolbar.

Project File

NameEnter a new name for the Project File Name, up to 30 characters. PowerStation prevents you from

entering illegal characters for the project name.

DirectoryPowerStation automatically sets up a subdirectory in the PowerStation directory for your new project. If

you want to place your project in a different subdirectory, click on Browseto select a directory.

Unit System

Select English or Metric as the default unit system for your project. Note that after a project is createdyou can change the defaults at any time. However, after a project is created, you must change the defaults

for each element individually.

Password

Project files can be set up with or without passwords, but passwords are recommended for optimal

security. If a password is required, every user must enter his/her user name and password before

accessing the project. If a password is not required for a project, PowerStation will automatically add the

user name to the user list for that project and default to the highest assigned permission level (Project

Editor) and open the project. If you store project files locally on your computer and you can control

access to your computer and project files, you do not need to use the password requirement.

ODBC

DriverSelect MS Access, Oracle, or SQL Server from the list box. Note that the ODBC driver must be

installed in your computer with the Data Source set tootiaccess.

4-14 ETAP PowerStation 4.

See Section 4.2.4, Advanced ODBC Parameters.Advanced Parameters

Operation Technology, Inc. 0


16/17

User Access Management Opening An Existing Project File

4.4 Opening An Existing Project FileTo open an existing project file, click on Open in the File menu or click on the second button on the

Project Toolbar, and then select a file with an .OTIextension from the Open dialog box.

4.4.1 LogonThe Logon dialog box is then provided to enter your user name and password, if a password is required.

The user name which you used to logon to Windows (NT, 2000, 95, or 98) is placed here as the default.

If you have changed your user name for this project, you will need to use that name to log on to this

project.



17/17

User Access Management Opening An Existing Project File

If this project does not require a password and this is the first time you are accessing this project, you will

be logged in automatically as a Project Editor and will be added to the project user list as an Instant User.

If your user name is listed in the project user list (because you have opened this project before or the

administrator has added your name to the user list), then you will be logged in with the highest access

level available to you, i.e., Project Editor, Base Editor, Revision Editor, Checker, etc.

Project File

NameThis is the file name for the file you are currently working on.

Compact DatabaseThe Compact Database feature will optimize the database, removing discarded information and all

elements deleted from the Dumpster, as well as other data that is no longer being used by PowerStation.

When deleting or updating a Microsoft Access database, the database will become fragmented and may

not grow in proportion with your project size. This feature is used to de-fragment and compact the

database. In most cases the size of the database is reduced. It will not remove columns of information

added to the PowerStation database through a third party database manager such as Microsoft Access.

You may also compact a Microsoft Access database by selecting Control Panel/ODBC, which runs the

ODBC Data Source Administrator dialog. For more details, see Chapter 2, Section 3, Configuring

ODBC. When you select the Compact Database command, the ODBC Data Source Administrator

automatically compacts your Microsoft Access database when the project is closed.

If this project requires a password, PowerStation prompts you to open the project file with one of the

access levels available to you. Only those access levels assigned to you are available for selection; all

others are grayed out. Select a desired access level (except Administrator) in the Select Access Level

dialog box. Click on OK. The project file will then be opened. Note that if you have only one access

level permission, PowerStation does not prompt you for access level selection and automatically logs you

in with that access level.


Documents

Chapter 04 - User Access Management