MicroSCADA Pro DMS System Administration

Transcription

1

2

3 Issued: Version: A/ Contents: 1. About this manual Copyrights Trademarks General Use of symbols Document conventions Terminology Abbreviations Related documents Document revisions Introduction General about DMS 600 software Software release updates New features and functions in New features and functions in DMS New features and functions in DMS Operational environment System requirements Requirements for fault location Architecture of DMS General about DMS 600 architecture DMS 600 Network Editor DMS 600 Workstation DMS 600 Server Application Hot stand by Hot Stand By Replication Slow network connections Terminal services Communication in DMS 600 software General about communication Communication between DMS 600 and MicroSCADA General about communication between DMS 600 and MicroSCADA Communication with SCIL API interface Communication with OPC Data Access interface Licenses

4 5.1. General about licenses Functionality of DMS Dimensions of the network Number of workstations Initialization of DMS Initialization of DMS User and region management General about user and region management Logoff mode User levels Regions Region types Defining dynamic region Defining extra region Controlling user rights Changing user identifiers or user rights Changing password Defining password policy settings DMS 600 SA Functions of DMS 600 SA Setting up DMS 600 SA interfaces Configuring SCIL API interface Configuring OPC interface Interfaces in DMS 600 SA Controlling of DMS 600 SA Starting DMS 600 NE Starting DMS 600 NE with DMS 600 interface User interface General about user interface User interface settings Network windows General about network windows Controlling the views in network windows Operational zooming System specific zooms Session specific zooms Coloring of network windows Displaying conductor codes and line types Hiding voltage levels

5 Coloring in network and protection analysis of DMS 600 WS Code and label controls Showing free database objects, texts and measurements Showing temporary network data Showing network plan data Symbol legend Parallel network views Network diagrams General about network diagrams Coloring in network diagrams Codes and labels in network diagrams Internal station diagrams Coloring in the station diagrams General about other fixed medium and low voltage diagrams Online help Initialization of background maps General about background maps Directories for background maps Titles for map materials Default values for background maps Modification of the background maps General about background maps Conversion of raster formatted maps Modification of raster formatted maps Conversion of vector formatted maps Adjustment of background maps Beginning of the adjustment Adjustment of vector formatted maps Adjustment of raster formatted maps General about adjustment of raster formatted maps Adjustment based on map corners Adjustment based on free selection Update of the adjustment data Initializing GPS service General about GPS device Creating connection between MAGELLAN Meridian Platinum and DMS 600 NE Databases General about network database Network database model

6 Network database tables Network database component codes Updating network data to workstations Definitions to network database Defining free database object type and text object type Defining new fields to outage reporting Importing customer information Definitions to DMS 600 database General about DMS 600 database Defining LV switch changes Defining reports and forms Defining GSM messages Defining GPS data of field groups Defining outage data export Other database definitions Defining telephone answering machine Defining switching state document General about switching state document Static texts in switching state document Using switching state document in web browser Custom database table settings Important network data for DMS 600 software functions Troubleshooting network data Basic principles for managing network data Notices Data editing modes Basic commands Fixed data forms General about fixed data forms Opening fixed data forms Browsing fixed data forms Content of fixed data forms Free data forms General about free data forms Changing labels or language Defining drop-down lists Opening free data forms Browsing free data forms Content of free data forms Editing free data forms Selecting node, line section, site node or diagram Graphical selection of nodes Multiselection of line sections

7 15. DXF import General about DXF import DXF import tools Launching DXF Import Tool Exporting network data to DMS 600 database Managing and viewing DXF/DWG import data DXF import settings Defining symbol block settings Defining DXF layer settings Defining DXF co-ordinate conversion settings Defining node connectivity Saving DXF/DWG import data into DMS 600 database General network management tasks Inserting medium and low voltage network lines and components Defining site node Creating site node diagram Defining states of switches Mass update of component/object data Mass update of line section data Defining node labels and symbols Location and color settings of codes and labels Moving node label Rotating conductor code Editing label of free database object Rotating node symbol Defining nodes, line sections or station/site nodes Changing node type Resizing the diagram Moving node or site node Removing node Removing line section Removing free database object or site node Inserting new node or new point to existing line section Moving point in existing line section Removing point in existing line section Changing line section end node Hiding line sections, nodes, free database objects and diagrams GPS waypoints Using GPS waypoints during editing Continuous locating of GPS device Pole data General about pole data

8 Inserting and editing pole locations Moving pole locations Inserting and editing pole data Removing the pole Inserting and editing the condition data of the pole Carrying out the pole and condition data mass update Separate network management tasks Managing parallel network views Inserting HV/MV station Inserting primary station data Inserting primary transformer data Inserting MV/LV station Inserting MV/LV transformer Inserting LV station Inserting LV box Inserting generator Inserting arc suppression coil Inserting MV fuse Inserting LV switch Inserting measurement transformer data Inserting grounding data Measurements General about measurements Inserting measurement Defining current measurement Defining voltage measurement Defining separate load point Defining power values to motors and generators Inserting free database object Inserting component and conductor type data General about inserting component and conductor type data Inserting disconnector type data Inserting MV and LV fuse type data Inserting MV and LV conductor type data Relay data Inserting relay data Inserting free data Reclosing curve Inserting overcurrent relay data Inserting earth-fault relay data Inserting reclosing relay data Inverse time curves About inverse time curves Calculating operation times

9 Adding inverse time curves Modifying inverse time curves Removing inverse time curves Hiding inverse time curves Selecting operation mode for relay Moving part of the network Copying part of the network Deleting part of the network Moving low voltage network Attaching and removing documents Inserting load data General about inserting data Inserting load data to MV/LV station Inserting load data to low voltage customer Manually inserting load data for load curve modeling Temporary network data General about temporary networks Inserting temporary network data Removing temporary network data Fault handling areas Viewing fault handling areas Creating a new fault handling area Deleting a fault handling area Integration of DMS 600 and Microscada General about integration of DMS 600 and MicroSCADA Offline functionality Integration tools Importing old style HV/MV station diagram from MicroSCADA Old style HV/MV diagrams Generation of input files in MicroSCADA Importing station diagrams Finalizing the station diagram Connecting unconnected lines Inserting missing station components Defining feeding points Completing data forms Importing new style HV/MV station diagram from MicroSCADA New style HV/MV diagrams Generation of import files in MicroSCADA Importing station diagrams Component integration when using SCIL API Process objects Cross-connecting components with process object IDs

10 Primary stations and primary transformers Circuit breakers, disconnectors, feeders and fault detectors MicroSCADA measurements Virtual process points Component integration when using OPC Data Access General about component integration Configuring and managing OPC Server Configuring OPC group Adding OPC items to group Connecting OPC items to network components General about connecting OPC items Circuit breakers, disconnectors, feeders and fault detectors MicroSCADA measurements Connecting Remote OPC with Windows Enabling of Distributed COM Defining access permissions Defining launch and activation permissions Defining DCOM settings for OPC server Defining DCOM settings for OPC Server Enumerator Starting OpcEnum service Local Security Policy settings Data Execution Prevention (DEP) Configuring Windows Firewall for Remote Use Configuring the OPC item suffixes for fault location using OPC Picture names General about picture names Old style station pictures New style station pictures Other MicroSCADA pictures Data transfer between DMS 600 and MicroSCADA using SCIL API Periodical and spontaneous data transfer Root point coloring and load flow direction Operational flows Fault case Fault detector data change Updating repaired fault Updating automatic fault isolation and restoration data Troubleshooting DMS 600/MicroSCADA integration AMR alarm settings

11 19.1. AMR alarm setting definitions Settings in the AmrConf.amr file OPC settings in the common.prm file AMR communication settings OPC item subscription Linking subscriptions to a customer AMR alarm symbol Integration of AMR alarm to SYS Symbols General about symbols Blinking symbols Symbols for free database objects and text object types Defining symbol zoom ranges Special symbols Defining symbols Defining symbols Defining subtype symbols Defining symbol font Defining outline for symbol Defining background for symbol Defining code label for symbol Updating symbol angles for all disconnector symbols MV/LV transformer symbols Settings General about settings Network view settings User interface language settings User interface fonts settings User interface default font settings Symbol zoom range settings Visibility and alarming settings Defining visibility and alarming settings Setting the alarming of looped feeders Defining code info Network window sizing settings Diagram showing settings Snap and grid settings Network and protection analysis settings General network analysis settings Protection analysis settings Meshed network analysis settings General planning calculation settings Color settings General about color settings

12 MV/LV station, switch and customer code color settings Settings of background color for network windows and diagrams Network line color and line width settings Defining network line color and line width Using network line colors Network line color and line width settings for voltage levels Drawing order of network window and line colors General network analysis settings Defining general network analysis settings Load calculation settings Protection analysis settings Alternative feeding network impedances Background map settings General about background maps Map material titles Outlook of background maps Defining workstation specific outlook Color definitions of background maps Map datum parameters Storage location of background maps Auto sequence control settings Defining auto sequence control Automatic fault isolation and restoration settings Automatic updating of unsupplied MV/LV substations settings Defining outage GSM messages to settings file Defining telephone answering machine usage to settings file Defining diagram opening to settings file Defining scheduled update of binary network file Defining automatic creation of switching state document Regular creation of switching state document Creation of switching state document after fault location General functions Selecting region Selecting operational modes Controlling voltage levels Locating network components Management of MV/LV substation texts Browsing the attached documents

13 22.7. Displaying MV feeder information Downstream and upstream traces Traces in network window Traces in network diagrams Showing important transformers Map printing Map printing procedure Map printing parameters Showing notice and event list Adding own features to menu Network analysis General about Network Analysis Load modeling Setting date and time for network analysis Load forecasting and load curve modeling Using starting motors in network analysis Performing the network analysis Protection analysis Showing protection relay settings data Notices of protection analysis Performing protection analysis Showing protection analysis results of given fault location Showing network analysis results in network windows Showing numerical network analysis results Calculation results Calculation summaries Saving and printing calculation results Description of result window columns Load flow result window columns Short-circuit calculation result window Earth fault result window columns MV network load flow summary window columns LV network calculation result window data Network planning General about network planning Managing network plans Starting a new plan Opening existing plan Locating plan Deleting plan Comparing plans Saving network plan Saving switching state Performing mass change of conductor types

14 Excluding line sections from planning calculation Dimensioning a line section Parameters Calculation Calculation result listing Optimization Importing network plan to database Simulated network analysis Changing switching state Changing relay settings Changing network analysis settings Changing planning parameters Simulation using expected load data Inserting load data to MV/LV station Inserting load data to customer Defining load calculation settings for all loads Defining load calculation settings for defined MV/LV substations Reliability analysis General about reliability analysis Performing reliability analysis Required input data and parameters General reliability analysis results Browsing results geographically Viewing detailed results for a selected feeder Database analysis General about database analysis Query results and design in MS Access Query results in MS Access Query design in MS Access Queries in DMS 600 software Query results in DMS 600 software Performing ready graphical query Graphical restriction of the query focus Creating simple graphical query in DMS 600 software Reporting Adding query command to menu How to solve problems connecting to SQL Server Appendix Quick guide Appendix

15 Tables of the network database Appendix Designing TrueType symbols with CorelDraw Appendix Default symbols Appendix Structure of station diagram import file Appendix Load curve editor Appendix User level rights Appendix Localization of DMS Appendix Field Crew management and workgroup positioning Index

16 16

17 1. About this manual 1.1. Copyrights The information in this document is subject to change without notice and should not be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any errors that may appear in this document. In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Oy be liable for incidental or consequential damages arising from the use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB Oy, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. Copyright 2009 ABB Oy. All rights reserved. Document number: Release: A/ Trademarks Registration and trademarks used in this document include: AutoCAD : Registered trademark of Autodesk, Inc. Citrix and Metaframe : Registered trademarks of Citrix Systems, Inc. CorelDraw : Registered trademark of Corel Corporation. FontLab : Registered trademark of FontLab Ltd. Hummingbird : Trademark of the International Business Machines Corp. Intel and Pentium : Registered trademarks of Intel Corporation. Microsoft and Windows : Registered trademarks of Microsoft Corporation. Windows Server and Internet Explorer : Trademarks of Microsoft Corporation. 17

18 PaintShopPro : Trademark of JASC, Inc. Other brands or product names are trademarks or registered trademarks of their respective holders General This manual describes the initialization of Distribution Management System DMS 600 (later in this manual DMS 600) software and the functions needed by the administrator of the system (available in DMS 600 Network Editor and DMS 600 Server Application). is a direct successor to DMS /4.2 and Open++ Opera 3.3. This manual describes the properties of all DMS 600 NE and DMS 600 SA functions by supposing that all licenses and optional functions are included and there are no user level restrictions. The absence of a license, the absence of an optional function, or user level restrictions may remove or make certain functions unavailable in the user interface. This document complies with the program version 4.3. Additional information such as Release Notes can be found on the program distribution media Use of symbols This publication includes warning, caution and information symbols where appropriate to point out safety-related or other important information. It also includes tips to point out useful hints to the reader. The corresponding symbols should be interpreted as follows: Warning icon indicates the presence of a hazard which could result in personal injury. Caution icon indicates important information or a warning related to the concept discussed in the text. It might indicate the presence of a hazard, which could result in corruption of software or damage to equipment/property. Information icon alerts the reader to relevant factors and conditions. 1

19 Tip icon indicates advice on, for example, how to design your project or how to use a certain function. Although warning hazards are related to personal injury, and caution hazards are associated with equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all warnings and caution notices Document conventions The following conventions are used for the presentation of material: The names of menus and menu items are boldfaced. For example, the File menu. The following convention is used for menu operations: MenuName > MenuItem > CascadedMenuItem. For example: select File > Coloring > Topology by Feeders. The Start menu name always refers to the Start menu on the Windows Task Bar. System prompts/messages and user responses/input are shown in the Courier font. For example, if you enter a value out of range, the following message is displayed: Entered value is not valid. The value must be 0 to 30. The names of push and toggle buttons are boldfaced. For example, click OK. The words in names of screen elements (for example, the title in the title bar of a window, the label for a field of a dialog box) are initially capitalized. Capital letters are used for the name of a keyboard key if it is labeled on the keyboard. For example, press the ENTER key. Lowercase letters are used for the name of a keyboard key that is not labeled on the keyboard. For example, the space bar, comma key, and so on. Press CTRL+C indicates that you must hold down the CTRL key while pressing the C key (to copy a selected object in this case). Press ESC E C indicates that you must press and release each key in sequence. The names of the directories and files (for example, DMS600/Settings.exe) are initially capitalized and shown in the italic font. The names of MS Access tables, queries and fields are capitalized (for example CODE field in INFOCODE table). 19

20 1.6. Terminology The following is a list of terms associated with DMS 600 that you should be familiar with. Term Application Extension Program; AEP Application Program Interface; API Binary network model; Network.dat Certainty factor DMS 600 database DMS 600 Network Editor; DMS 600 NE DMS 600 Server Application; DMS 600 SA DMS 600 Workstation; DMS 600 WS Data transfer group Draw upon map DWG DXF Fault distance Fault file Free data form Free database object Description An external program which extends the application with Application Program Interface. See also Application Program Interface. A set of routines that an application program uses to request and carry out lower-level services performed by a computer operating system. Model of a relational network database used to speed up the operation of DMS 600 software. Certainty factors are used during inferencing to define the stress on individual inference rules. Database for dynamic data in DMS 600. A program primarily used to model the distribution network onto the network database. An application used for data exchange between MicroSCADA and the instances of DMS 600. A program for the operative personnel of electric companies to monitor and operate their medium and low voltage distribution networks. A user-defined process object group, which consists of the same kind of process objects. A vector map which is drawn after other map materials and is on the top of other maps on the screen. AutoDesk drawing format. World's leading CAD software binary data format. AutoCAD Drawing exchange Format. Contains an AutoDesk Drawing. World's leading CAD software ASCII data format. The fault distance is determined by comparing the measured short-circuit current and the type of fault with the calculated short-circuit currents along the feeder in which a fault has been occurred. The fault location of DMS 600 WS is based on fault distance calculation and fault detector data. Fault snapshot file created by DMS 600 SA. File names of fault snapshot files are Fau<xxx>.txt, where <xxx> is a running number. Free data forms are the general way to present DMS 600 database content. Free database objects are user-defined object types which can be added to the network database. 20

21 Term Hot Stand By; HSB Internet Protocol; IP IP address Load current compensation Local Area Network; LAN MicroSCADA monitor MicroSCADA Monitor Pro MicroSCADA OPC Server MicroSCADA station picture Network database OPC item DMS Interface Package Process object Protocol Raster map SCIL API Scada code Description A system to secure database connection with two servers. Each server is capable of continuing service alone, if the connection to the other is lost. The messenger protocol of TCP/IP is responsible for addressing and sending TCP packets over the network. IP provides a besteffort, connectionless delivery system that does not guarantee that packets arrive at their destination or that they are received in the sequence in which they were sent. See also Transmission Control Protocol. Internet address (for example, ) In load current compensation the load current just before the fault is subtracted from the measured fault current, or, in the more accurate model, the load behavior caused by the voltage drop during the fault is taken into account. A group of computers and other devices dispersed over a relatively limited area and connected by a communications link that enables any device to interact with any other device on the network. See also Wide Area Network. Enables interaction with the operator and the base system computer. The monitor may be of Visual SCIL or X-monitor type. MicroSCADA monitors are always connected to SYS 500 or SYS 600. MicroSCADA Monitor Pro is a new application that can show the Monitor Pro graphics of SYS 600. The MicroSCADA OPC Data Access Server is an implementation of OPC Data Access Custom Interface Standard, Version 2.05A, which is the interface specification in the MicroSCADA system. A type of MicroSCADA application picture, which gives an overview of the processes in a station. The station picture is often designed according to a single line diagram. Database for network data. An index for a MicroSCADA process object that contains the whole path with an application number. OPC item has properties (process object attributes) such as alarms and time stamps. A tool used to cross-connect MicroSCADA and DMS 600. A MicroSCADA process object, which has a connection to a real process. A set of semantic and syntactic rules that determine the behavior of functional units in archiving communication. Map information consisting of dots. The number of dots depends on the resolution of the map. Each dot has some color information according to the number of colors used. See also Vector map. MicroSCADA API for C programmers that is used to connect DMS 600 to MicroSCADA. Process object identification in DMS

22 Term Description Support System Interface; SSI System specific settings TCP port Temporary network file Transmission Control Protocol; TCP Transmission Control Protocol/Internet Protocol; TCP/IP Vector map Virtual process point Wide Area Network; WAN Workstation specific settings A standardized method of transferring data between applications. The settings which define the functions of all instances of DMS 600 NE and DMS 600 WS. Service Access Point of a TCP port. See also Transmission Control Protocol. The file containing temporary network data (Tempnet.dat). A software protocol developed by the Department of Defense for communications between computers. This is a connectionbased Internet protocol responsible for breaking data into packets which the IP protocol sends over the network. This protocol provides a reliable, sequenced communication stream for network communication. See also Internet Protocol. A set of networking protocols that provides communications across interconnected networks made up of computers with diverse hardware architectures and various operating systems. TCP/IP includes standards for computer communication and conventions for network connections and traffic routing. See also Transmission Control Protocol and Internet Protocol. Map information that consists of lines and curves. See also Raster map. A MicroSCADA process point which does not have a connection to a real process. A communications network that connects geographically separated areas. See also Local Area Network. The settings which define the functions of a local workstation (DMS 600 NE or DMS 600 WS) Abbreviations Abbreviation AEP AI API BI bmp CDR DB DMS DMS 600 Description Application Extension Program Analog Input Application Program Interface Binary input Windows bitmap format CorelDraw file binary input Distribution Management System Distribution Management System DMS

23 Abbreviation Dxf GPS GSM HV HSB IEC 6150 IP IX LAN LIB 500 LIB 510 LN LV MicroSCADA Mtc Mto MV NMEA-013 SCADA SCIL SMS SSI SYS 600 TAM TCP TCP/IP Tiff Ttf VPCT Description Vector file format Global Positioning System Global System for Mobile Communication High voltage Hot Stand By Standard defined by IEC: Communication networks and systems in substations Internet Protocol Index Local Area Network MicroSCADA Application Library MicroSCADA MV Application Library Logical Name Low voltage MicroSCADA SYS 500 version.4.2,.4.3,.4.4 or.4.5 or Control System SYS 600 version 9.x Station diagram transfer file of MicroSCADA Topology Generator. Station diagram transfer file of MicroSCADA Topology Generator. Medium voltage NMEA-013 is a serial communications standard for the encoding and sending of GPS and other navigation information between devices. Supervisory Control And Data Acquisition Supervisory Control Implementation Language. SCIL is a picture and object oriented, high-level language for application programming in MicroSCADA. Short Message Service. Service for sending messages to mobile phones that use Global System for Mobile (GSM) communication. Support System Interface Control System SYS 600 version 9.x Telephone Answering Machine Transmission Control Protocol Transmission Control Protocol/Internet Protocol Raster file format TrueType file format Virtual Point Creation Tool 23

24 Abbreviation WAN Vg2 Description Wide Area Network DMS 600 internal vector file format 1.. Related documents Table 1.-1 DMS 600 related documents Name of the manual MRS number 1MRS System Overview 1MRS Integration with SYS 600 1MRS Operation Manual 1MRS75666 Installation Manual SYS MRS System Configuration SYS MRS Picture Editing SYS MRS Process Display Design SYS MRS Installation and Administration Manual 1.9. Document revisions Version Revision number Date History A New document 24

25 2. Introduction 2.1. General about DMS 600 software Distribution Management System (DMS 600) is a direct successor to DMS /4.2 and Open++ Opera software version 3.3 with extended functionality. DMS 600 functionality is very deeply integrated to Control System SYS 600 version 9.x (SYS 600). Most of the functionality can be used also with MicroSCADA SYS 500 version.4.2,.4.3,.4.4 or.4.5. The abbreviation SYS 600 is used only when the topic is valid only for SYS 600. Abbreviation MicroSCADA is used when the topic is valid for both SYS 500 and SYS 600. DMS 600 is a geographical distribution network management system (DMS). The software extends traditional SCADA capabilities by providing geographically based network views. DMS 600 (Base) package provides network component data management and network modeling to provide network overview and topological coloring to see the network's state. In addition, DMS 600 has many optional modules with advanced functions. DMS 600 can be used with MicroSCADA, without SCADA or with other SCADA systems using OPC Data Access interface. The software has been designed to assist the operation's personnel of electric companies in monitoring and operating their networks. Both raster and vector based maps can be used as backgrounds for the network window. It is also possible to create and use schematic network views, instead of geographically based network presentations and maps. The software runs on PCs using MS Windows operating systems. For supported versions, see, 4.1, System requirements. Only 32 bit versions of operating systems are officially tested and supported. Additional (regional) servers can be used to store network data to keep the start up time reasonable in low speed LAN/WAN networks. MS SQL Server, Oracle or MS Access can be used as database for DMS 600. Also other database servers can be used if they support the required features of a DMS 600 database. The graphics-based user interface of DMS 600 is unambiguous and the standard Windows look and feel, together with the online help, makes it easy to learn. 25

26 3. Software release updates 3.1. New features and functions in Inverse time curves An inverse curve (or inverse time curve) is a curve that is used to define an operation time of a protection relay. The input is typically a relation between set current value (Iset) and measured fault current (I) => ( I / Iset ). Inverse time curves are defined with various equations. Some of them are defined in international standards (IEC/IEEE) and some are industrial de facto standards (IAC) or manufacturer-specific curves (RI, RD). Extended Trouble Call Management Trouble Call Management is used to handle customer complaints and fault notifications. Trouble Call Management uses the Disturbance Data Form to collect information about the faults, such as the nature and location of the fault. The Trouble Call Management sublicense is required to enable this feature. AMR extensions DMS 600 can be integrated into AMM/AMR (Automatic Meter Management / Automatic Meter Reading) systems. This enables using the communication and device infrastructure created mainly for energy metering to also remotely monitor the low voltage networks. The monitoring can include receiving spontaneous alarms regarding network faults and voltage violations, as well as reading measurement values when exact data is needed. DMS 600 combines information from several customer points and can inference, for example, a probably blown fuse in the LV network. DMS 600 uses OPC DA client to connect to AMR system and, thus can receive events close to real-time. Improved fault management The fault management includes the following improvements: Fault handling areas can be used to allow automatic fault location only in selected areas. The areas can be defined separately for each switching device. Possibility to set the fault status. Fault repairing time estimate can be set directly from the fault list without the telephone answering machine functionality. General information window shows duration of the fault, number of unsupplied customers per fault even without fault location or opening the switching plan. 26

27 The fault distance in meters is available from some protection devices. The distance can be used instead or parallel to reactance and fault current in the fault location. Possibility to change the intervals for reading outage data and for unsupplied MVLV substation data. Possibility to create a fault for areas fed by a disconnector or a MV fuse. OPC interface extension The OPC interface extension includes the following new functionalities: The system administrator is able to configure the OPC item name suffixes. The DMS 600 SA subscribes the TRIGGER OPC items for each circuit breaker in order to initialize the fault creation functionality. All available OPC items constituting faults are subscribed. This function is performed right after the TRIGGER OPC item has been activated. For the OPC items to be available, the OPC item name must be configured, and the process object must be created in SYS 600. Possibility to create a new fault for further processing. The subscribed OPC items are reset so that they can be reused in the next fault case. A notification of changed OPC configuration. DMS 600 SA reflects the changes in the OPC configuration without the need to restart it. Integrating manual switches to SYS 600 offers a practical way to display also switching operations of manually operated switches in the SYS 600 event list. Improved switching planning The following improvements have been made for switching planning: Fully supported MV fuses. The MV fuses can be handled in the same way as manually controlled disconnectors. The breaking capacity of a switch is checked against the calculated load current when opening a switch. Fully supported CBs with trucks. Locking switches open from the control dialog is supported. Transformer model changes The Transformer model is renewed to better meet the needs of three winding transformers. The data forms of the MV/LV transformer and primary transformer are renewed. Also, the transformer series functionality has been made easier to use. 27

28 Network planning With the network planning feature of DMS 600 NE the user can design the network before adding it to the network database. It enables comparing the alternative network structures, monitoring investment and interruption costs, as well as making calculations based on suggested network components. DXF import for network data DXF import for network data, initially exported from 3rd party GIS system, is now present in the DMS 600 Network Editor's basic functionality. The user is able to define the DXF layers, line routes and symbol blocks to be imported into the DMS 600 database. All the desired MV/LV the line sections and nodes are imported directly into DMS 600 network model. In addition to DXF format, also the AutoCAD's DWG format is able to use in DXF import function. The new DMS 600 DXF Import Tool, launched from NE, uses Open Design Alliance's (ODA) DWGdirect library in reading DXF and DWG formats New features and functions in DMS Extended automatic fault isolation and restoration In addition to control actions, the generated sequence file includes the circuit breakers to be checked. The information can be used to check that the circuit breaker feeding the back-up connection remains closed. If that circuit breaker is opened due to relay trip, the restoration will be cancelled. Switch state updates with modified time and possibility to correct times in event list The switch control dialog for manual devices includes a control that gives the real time when the switch was operated. In addition, the event time can be changed in the DMS 600 event list afterwards. This enables, for example, the creation of outage reports with corrected event times. Relational database servers DMS 600 can use relational database servers (such as MS SQL Server and Oracle) instead of MS Access database to store data. The connection to a database is made using ODBC data source name (DSN) definitions. MS Access databases without DSN definitions are 2

29 still supported. For Hot Stand By systems, two relational database servers with a replication feature are recommended instead of Access databases. Parallel network views It is possible to select the used network view independently in each program instance (workstation). The user has the possibility to create a new view by moving and hiding nodes and lines in the main view without overwriting already existing data. For example, a parallel schematic diagram can be created (orthogonal schema) to make network operation clear and effective but exact locations of objects can be viewed on a map using a geographic view. All views can use the real time network coloring to show the state of the network as before. Switch state quality (status) separated from switch state Separate symbols can be defined for uncertain switch states (open, uncertain or closed, uncertain). These symbols are used when the switch state is known in the SCADA database but quality is uncertain. In the OPC interface this means that OPC quality QUALITY_UNCERTAIN used, and in the SCIL API interface the status values 1, 2 or 3 are used. The OPC quality QUALITY_BAD or status 10 (not sampled) cause the state of the switch to be shown as error, as before. The user can define if uncertain state will cause network coloring to use unknown color. Error state will always cause unknown coloring. Manual state update for switches connected to SCADA Disconnectors and circuit breakers that normally reserve the state from SCADA can be moved to manual state update in DMS 600. This can be used as a temporary solution, for example, to see known state in DMS 600 if communication to station is broken and SCADA is not showing the known state. There are separate symbol definitions for closed and open, manually updatable switches. Distribution Contingency analysis The user can define sequences that can be used to check if the system is capable of handling known fault situations with present loads. For example, the sequence can check whether there are acceptable back-up feeds when some main transformers have to be switched off. The power of generators and motors can be changed in the study, too. 29

30 Power values for motors and generators Real time measurement values from SCADA can be linked to motors and generators so that the load flow calculation in state monitoring mode can use measured values. In the simulations the user of WS can change the values with simulation dialogs. IED (relay) modeling For documentation purposes the network database can include data for any kinds of protection and control devices. For example, distance and differential protection devices with their properties and setting values data can be added. The user can define additional data fields for any protection devices. LIB 500 not required anymore DMS 600 can be used with SYS 600 without installing LIB 500. The tools that were earlier available only when also LIB 500 was installed are now available without a LIB 500 installation. Improved fault management Switching to another fault instance is faster than before since all existing faults are in main memory. Operation is faster when there are several unrepaired faults since switch state changes are not anymore stored to each fault file. For reporting the switch state changes are read from the event log instead of the fault files. The Fault Management dialog is resizable. For example, the list presentation of present faults can be increased so that more information can be seen at the same time. Extreme conditions switch is added. When there are a lot of simultaneous faults and lots of switch state changes, the operation of the system can be changed by pressing one button so that the screen update interval is increased and automatic load flow after changes is switched off. Customer service points in MV network A customer service point can be added to the MV network to represent a so called MV customer that has their own transformers. The load or energy data can be given for a service point so that the service point will be included in the load flow calculation without modeling MV/LV transformers owned by the customer. 30

31 Generic OPC DA client The DMS 600 OPC DA client can be used with any compatible OPC DA server to get real time switch states and measurements to DMS. However, alarm indications can be obtained with OPC DA only from SYS 600 by using SYS 600 specific alarm attributes. Extended tracing functionality The user has a possibility to view all switching devices along the selected trace in the tracing order. The list shows the type and the existing state of each switch. Through this dialog a selected switch can be located and it s switching state can be changed. If the state of any of the switches in the list is changed, the dialog becomes outdated and the trace coloring will be cancelled and the dialog closed. The network window can be zoomed to show all line sections included in the trace to easily see how far the trace continues in the network. This zoom function is available in same shortcut menu where trace functions are located. Network presentation enhancements A radial network fed by a circuit breaker but not having any loads connected can be presented with a special no-load color. This helps the user to see which circuit breakers can be opened without harm. There is a different symbol for unsupplied primary transformers. This clarifies the network view and switching operations on substations. A dashed line can be used for coloring an unsupplied (no voltage) network New features and functions in DMS The table below lists the main new features in 4.1. Table New features and functions in DMS New Feature or Function Advanced Switch Order Management Network coloring by nominal voltage levels Fixed colors for main transformers and feeders Faults without opened circuit-breaker to outage reporting Changing feeding voltage in simulation Checking voltage levels and transformer phasor groups Load-protection coordination More Information Operation Manual , General about network windows and , Network line color and line width settings for voltage levels 17.4, Inserting primary transformer data Operation Manual Operation Manual 17.4, Inserting primary transformer data 31

32 New Feature or Function Impedance based fault location for earth faults in isolated or compensated networks License structure changed. The module "Outage Reporting and Statistics" can be added without the module fault location. More Information Operation Manual 5.1, General about licenses 32

33 4. Operational environment 4.1. System requirements The following table shows the minimum software and hardware requirements for DMS 600 distribution management system. The proposed system configuration contains 1-3 PC's with possible Hot Stand By support. DMS 600 can also be used without MicroSCADA or other SCADA systems. Table System requirements for DMS 600 Component Computer Memory Requirement Intel Pentium processor 512 MB Recommended amount of RAM is 500 Mb at minimum. Disk space Monitor Mouse Optional components For basic installation 100 Mb free disk space is enough but the real need depends on the amount of background maps which can use even a few gigabytes of server disk space. VGA, 1024x76 resolution, colors (16-bit), 70 Hz refresh frequency Any Windows compatible mouse One or more network adapter cards, when using DMS 600 software on a LAN with a TCP/IP protocol CD-ROM drive Software Optional software DMS 600 supports the following Microsoft Windows 32-bit operating systems: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 200 and Windows 7. MicroSCADA SYS 500 version.4.2,.4.3,.4.4,.4.5 with LIB 500 Application Library and LIB 510 MV Application Library version , or or Control System SYS 600 version 9.x. MS Access 2000 or MS Access 2002 relational database software (MS Access 95 or 97 during upgrading) The Hummingbird Exceed version or later. In some PC workstations the full hardware acceleration setting in display properties can cause several zoom window lines to be visible on screen. In that case lower the hardware acceleration setting. 33

34 4.2. Requirements for fault location The following is a list of the protection units that can be used with fault location of DMS 600 WS. Other equipment capable of providing at least the minimum data required can be used as well. Table ABB protection units for fault location of DMS 600 SPACOM modules SPCJ 1C7 SPCJ 1C SPCJ 1C20 SPCJ 2C30 SPCJ 3C3 SPCJ 3C4 SPCJ 3C35 SPCJ 4D24 SPCJ 4D2 SPCJ 4D29 SPCJ 4D34 SPCJ 4D36 SPACOM modules SPCJ 4D40 SPCJ 4D44 SPCJ 4D61 SPCS 2D26 SPCS 2D32 SPCS 2D37 SPCS 3C4 SPCS 4D11 SPCS 4D12 SPCS 4D13 SPCS 3C2 REF units REF 541 REF 542 REF 542plus REF 543 REF 545 REF 610 REF 615 REX units REX Architecture of DMS General about DMS 600 architecture The DMS 600 system consists of three programs from the user s point of view: DMS 600 Network Editor (DMS 600 NE), DMS 600 Server Application (DMS 600 SA), and DMS 600 Workstation (DMS 600 WS). All programs (DMS 600 NE, DMS 600 SA, and DMS 600 WS) can run on the same or different computers. Additionally, programs can run on the MicroSCADA system computer. DMS 600 WS and DMS 600 NE can be used in a multiscreen environment without 'dialog box-centering' or similar features in a multiscreen graphics adapter. DMS 600 supports running several instances of DMS 600 WS in the same workstation computer. In a standard workstation, only one DMS 600 NE is allowed. 34

35 DMS 600 Network Editor DMS 600 Network Editor (DMS 600 NE) is primarily used to model the distribution network onto the network database located in the primary fileserver of the fileserver system. It is also the administrator's tool for managing the whole DMS. The system can be used to manage both medium and low voltage distribution networks. The initialization of the background maps, defining of symbols and participation to the management of the integration between MicroSCADA and DMS 600 are the important tasks of this program. Many other descriptions and definitions are made by DMS 600 NE. DMS 600 NE can be used while DMS 600 SA and instances of DMS 600 WS are running. DMS 600 NE can be started only if the primary fileserver is connected. Several DMS 600 NE sessions can be run at the same time. The number of simultaneously allowed DMS 600 workstations is defined by the license. The users have a responsibility, however, to check that they are not editing the same electrical components (same area) of the medium voltage network at the same time. DMS 600 NE updates the binary network file (Network.dat) of the network database and the temporary network file (Tempnet.dat) from the user input. Binary network modeling is used to speed up the operations of DMS 600 software. A mechanism for informing DMS 600 SA and instances of DMS 600 WS from the new binary network and temporary network files is included. The users receive information about new network data and can choose, by the user input, to load the new models at once or later. In the fileserver system, network database is not replicated to secondary fileserver. For more information about licenses, see 5.1, General about licenses. Open++ Integra is a geographical distribution network information management system, which can be used to replace DMS 600 NE in DMS 600 -distribution management system DMS 600 Workstation DMS 600 Workstation (DMS 600 WS) is a program for the operative personnel of electric companies to monitor and operate their medium and low voltage distribution networks. The program contains the following functions: Alarming, Network topology management, Network analysis including power flow and fault current calculations together with protection analysis, Operational simulations, Fault location based on fault distance calculation and fault detector data, Restoration, 35

36 Switching planning, Contingency analysis, Outage data management, Field crew management, Load estimation, Customer service, Database analysis, Document archive and Map printing. The functional content of the system depends on the licenses, sublicenses and definition of optional functions. The basis of DMS 600 WS is a distribution network database managed by DMS 600 NE and real time process data from MicroSCADA. Control actions can be done using MicroSCADA station pictures and control dialogs can be opened directly from DMS 600 WS. In the opened control dialog the user has control rights only if the username and password in the DMS 600 match with the user information in SYS 600 and if the user is authorized to control the selected switch DMS 600 Server Application The main function of DMS 600 Server Application (DMS 600 SA) is to serve communication routines for DMS 600 software. The communication routines of DMS 600 SA consist of two parts: communication between DMS 600 SA and MicroSCADA, and communication between DMS 600 software. The connection between DMS 600 SA and MicroSCADA is defined by the sublicense. Earlier Open++ Opera versions' communication has been based on DMS 600 SA communication (SCIL API interface), and it is possible to use it also in DMS 600. OPC Data Access interface of DMS 600 can be used parallel with SCIL API in some communication tasks, if Control System SYS 600 version 9.x (SYS 600) and Micro- SCADA SYS 500 version.4.5 are used. The user interface of DMS 600 SA is very simple and without network presentation. In SCIL API interface, DMS 600 SA provides real time information as well as station and control pictures from MicroSCADA for instances of DMS 600 WS. Information is transferred via the DMS 600 database and fault files (Fau<xxx>.txt) Hot stand by Hot Stand By Hot Stand By (HSB) is a system used to secure database connections with two servers, which are capable of continuing service alone if the connection to the other is lost. 36

37 HSB support is included in the Support System Interface (SSI), the dynamic DMS 600 database, binary network file and the fault files, if so defined in the sublicense. In the SSI, DMS 600 SA must be ready to reconnect to HSB SYS of MicroSCADA. DMS 600 databases and fault files are redundant, so the malfunction of a DMS 600 SA computer does not stop operation of the system. DMS 600 WS can be started using the redundant fileserver and DMS 600 SA. When using MS Access databases, DMS 600 NE can be started only if the primary fileserver is connected. If there are two SA instances running simultaneously, the DMS will handle this itself internally. Though this is an error, it will not prevent the usage of the system. The last SA instance that was started takes over and continues normally. Two relational databases with a replication feature are recommended for HSB systems Replication A replication list contains all replication items which the system has not been able to save, delete or update in both DMS 600 databases. This kind of situation happens, for example, when the connection to the fileserver is lost. The replication list is saved and the contents of the list will be replicated later, for example, when the fileserver is reconnected. Replication lists are used to check information in the following DMS 600 database tables: FAULTDETECTORSTATE FIELDGROUP LINESTATES LV_SWITCH_CHANGES LV_TEXTS MEASUREVALUES OPERASETTINGS SWITCHINGCOMPONENT FAULTS A replication list is used also to check information in the following files: Fault files (Fau<xxx>.txt saved to folder \Outage) Switching state files (Switching_State_yyyy_ww.stf in, where yyyy is year and ww is week and saved to folder \Data\SState) Event log files (Opera_Event_Log_yyyy_ww.log, where yyyy is year and ww is week and saved to folder Data/Log directory) Replication is managed by DMS 600 WS and DMS 600 SA. If DMS 600 WS or DMS 600 SA is closed and there is still something that could not have been replicated, all replication data is saved to the file ReplicationInfoFile.txt. DMS 600 NE adds replication items directly to this file. 37

38 The file ReplicationInfoFile.txt is saved to data directories of fileservers or to the DMS 600 directory if neither of the two fileservers is connected. DMS 600 WS or DMS 600 SA searches for possible files, reads the contents of the file and tries to replicate occasionally and during every start up. Replication list can contain 1000 items at most. If the limit is reached, a warning message is displayed. You are given the option of saving these 1000 items to a text file (saving may take several minutes). After that, the replication list is cleared. If the fileserver is disconnected for a long time (for example, due to a service break) it is advised temporarily to disable the HSB system and to copy databases manually when the server is reconnected Slow network connections DMS 600 can be optimized for slow network connections. This feature is useful if there is a slow Wide Area Network (WAN) connection instead of a LAN between central and district offices and terminal services are not used. Additional regional servers can be used to store network data to keep the start-up time of the programs reasonable. For information about terminal services, see 4.6, Terminal services Terminal services Normally DMS 600 uses client-server architecture, which means that for example DMS 600 applications are run using the client computer processor and memory. The network model is loaded to the main memory of the client workstation. However, DMS 600 programs can be run in a terminal session using Windows 2000 Server or Windows Server 2003 (these include Terminal Services). This is advantageous for example in case of slow network connections or when using dial-up networking with modems. This is often needed in order to use DMS 600 in a home workstation. Additionally, it can be advantageous that occasional users from office workstations use terminal services since upgrading and maintenance of the software need to be done only on the server. Simultaneously in the same system the power users for example in the control center can use standard workstations. With SYS 600 new monitor type ( Monitor Pro) terminal services are used instead of Exceed to spread applications to workstations at least when Monitor Pro graphics and tools are used. In this case also DMS 600 shall be run under terminal services so that the integration of user interfaces can work. The Windows Terminal Server can be expanded using Citrix Metaframe software. In this case DMS 600 can be safely published as an application for remote use and this 3

39 makes the management easier. With MetaFrame DMS 600 can even be run embedded in Internet Explorer. Using Internet Explorer requires also a Web server for example MS Internet Information Server Communication in DMS 600 software General about communication DMS 600 has three communication interfaces (numbers referred in image below): 1. SCIL-API interface 2. OPC interface 3. DMS600 internal communication interface Figure DMS 600 communication interfaces DMS_communication_interfaces.png Figure DMS 600 Database and file interactions DMS_database_file_interactions.png 39

40 -arrow lines: read and write actions Single-arrow lines: read only actions -arrow dashed lines: create/modify DMS 600 software applications use a dedicated Windows service as a message routing component. This service has a crucial part in DMS 600 messaging as all messages are routed through it. In an HSB environment, the service is redundant. DMS 600 messaging uses TCP protocols directly through the Windows Sockets API. DMS 600 NE updates network data changes directly to the relational network database of the local workstation or of the primary fileserver in the fileserver system. Ready changes are then saved into the binary network file to achieve fast upload to workstation memory. Information about the new binary network file is sent to DMS 600 SA, as well as DMS 600 WS and DMS 600 NE. These read the new network data from the binary network file. DMS 600 WS uses the source network database only when opening a network component or free form object data. DMS 600 NE uses a temporary network file for temporary network data that is read together with real network data into the memory of DMS 600 WS workstations Communication between DMS 600 and MicroSCADA General about communication between DMS 600 and MicroSCADA DMS 600 SA is used for data exchange between MicroSCADA and instances of DMS 600 software by using SCIL API and Support System Interface (SSI). Earlier Open++ Opera version's communication was totally based on SCIL API interface, which can be used also in DMS 600, if Control System SYS 600 version 9.x (SYS 600) and MicroSCADA SYS 500 version.4.5 are used. Control System SYS 600 version 9.x and MicroSCADA SYS 500 version.4.5 have a new communication feature based on OPC Data Access. All the process objects of SCADA are exposed by the server as OPC items and all the attributes of process objects as OPC item properties. If defined, the OPC interface is primarily used for communication. Only if the OPC interface is closed, the SCIL API interface is open and also scada code for the component is defined, the SCIL API interface is used for communication. The OPC Data Access interface of DMS 600 can be used parallel with SCIL API in: Transferring state changes, measurement, alarm and warning data and Transferring feeder root point coloring and load flow direction. 40

41 The SCIL API interface of DMS 600 is used: In transferring the fault data and During automatic fault isolation and restoration. The COM interface is used in: Importing SYS 600 station pictures to network database, Opening SYS 600 station pictures or control dialogs from network map, Locating network components, Showing downstream trace, Showing feeder information and Zooming in and out network map from SYS 600 station pictures Communication with SCIL API interface The Support System Interface (SSI) consists of Application Extension Program and Service Application Program. MicroSCADA has SCIL command procedures for starting and stopping Application Extension Program (SCIL API). Application Extension Program is automatically started when MicroSCADA state changes to hot. During the start up procedures, Application Extension Program checks that Service Application Program is installed and running. Service Application Program is a MS Windows service, which is installed once and after that it is always running. Application Extension Program also automatically starts DMS 600 SA. Real-time switch state change causes sending of an event-based data message from MicroSCADA to DMS 600 SA. DMS 600 SA then sends this data message to all DMS 600 Workstations. DMS 600 WS does not read a server disk or database in this case. Switch state changes are also updated to DMS 600 database. Measurement values are obtained to DMS 600 SA like switching states. New measurement values are updated to DMS 600 database and sent to all DMS 600 Workstations. Measurement data is transferred cyclically and in an event-based manner from MicroSCADA to DMS 600 software. Alarm and warning attributes are handled together with switching states and measurement values through the SCIL API interface. When a new fault occurs, an event-based data message is sent to DMS 600 SA from MicroSCADA. DMS 600 SA saves fault data into a fault file, part of the fault data (the running number of the fault, the state of the fault, and the title of the fault) into the DMS 600 database, and sends a message to all DMS 600 Workstations. DMS 600 Workstations then read additional data from fault files and DMS 600 database. See also , Fault case, , Fault detector data change and , Updating repaired fault. Automatic fault isolation and restoration is managed from only one DMS 600 Workstation. The generated switching sequence in DMS 600 WS is automatically transferred from DMS 600 WS to MicroSCADA and execution is started. A special process object is used to indicate the automatic fault isolation and restoration sequence status. 41

42 DMS 600 WS programs use a message while opening a picture. The message includes the opening coordinates of the picture and a picture name or scada code. DMS 600 SA receives the message and sends it forward to Support System Interface program and so on. The settings for the feeders' root point coloring are sent from DMS 600 to MicroSCADA Communication with OPC Data Access interface This chapter is valid only for Control System SYS 600 version 9.x (SYS 600) and for MicroSCADA SYS 500 version.4.5. The OPC Server and OPC Clients are used for data exchange between SCADA and the instances of DMS 600 software by using OPC Data Access. The OPC Client interface opens automatically when you start DMS 600 SA or DMS 600 WS. The iinterface can be closed and reopened with a menu command. All the objects of SCADA are exposed by the server as OPC items and all the attributes of objects as OPC item properties. In communication with DMS 600 and SCADA, OPC items will be handled as groups. The group level properties are the update interval and the type of the group. For the position indication types of groups the default value of the update interval is zero, and for other types 1000 ms. If there is a change in real-time switching states or measurement values, an event is sent from MicroSCADA SYS 600 OPC Server to all DMS 600 WS workstations (3) and also DMS 600 SA. DMS 600 sends feedback for the event data if this is defined in the settings. Alarm and warning properties with time stamps are handled together with switching state values. New style station pictures are primary used in DMS 600 WS. In that case a station picture is opened using the COM interface. A request to open old style station pictures uses DMS 600 SA. The switch and measurement objects can have both an OPC code and a scadacode defined. If the OPC interface is closed in DMS 600 SA, the switch states and measurement values having scadacode definition are still transferred through the SCIL API interface. If the OPC interface is closed in DMS 600 WS, the switch states and measurement values that are transferred through SCIL API interface of DMS 600 SA are also transferred to DMS 600 WS. DMS 600 contains an ActiveX Server component (DMSMethods.exe) which is used to execute methods or query information from different applications (DMS 600 SA, DMS 42

43 600 NE, DMS 600 WS, MicroSCADA). This interface deals with the starting of client software, integrated login from SYS 600 to DMS 600, zooming in and out network maps from SYS 600, locating network objects, tracing electrical supply, SYS 600 diagram importing and querying feeder information. 43

44 5. Licenses 5.1. General about licenses The functioning of DMS 600 software depends on the licenses and sublicenses containing information about the main and optional functions together with information about the connection between DMS 600 SA and SCADA. The available commands in the user interface reflect the capabilities of the program in accordance with the installed licenses, sublicenses and selectable functions. DMS 600 software 4.3 requires licenses for the version 4.3 to function correctly. Additionally, version 4.0/4.1 licenses are compatible and accepted for 4.3. If previous license (Open++ Opera version 3.2 or 3.3 license) is used with DMS 600 software version 4.3, warnings message "License version number is incorrect! ABB assumes no responsibility for any error that may occur while using this program!" is displayed. DMS 600 software version 4.3 licenses are delivered with DMS 600 software version 4.3 program update Functionality of DMS 600 Table Functionality of DMS 600 licenses License Sublicense Selectable Functions Operational Functions DMS 600 (Base) Temporary network data Events Distribution network topology management Temporary network data SCADA connection Connection between DMS 600 SA and SCADA Hot Stand By Two server systems to secure database connection Demo Demo to allow introducing of DMS 600 software with limited MicroSCADA connection (6 hours without reopening) and network editing only to temporary networks Low voltage networks Management of low voltage network GPS Support GPS data in network editing and field crew management 44

45 License Sublicense Selectable Functions Operational Functions General extensions Extended Data Management Network Analysis Fault Location Outage Reporting and Statistics GSM messages Switching State Document Extended Load Modeling Operations Planning Reconfiguration Restoration Support Automatic Fault Isolation and Restoration Telephone answering machine Advanced Report Management Field crew management Customer information Alarms Document archive Free database objects Free data form Free data form for DMS 600 WS Queries Load estimation Use of Velanders factors or load curves GSM messages used for sending outage information or other messages. Switching state document Field crew management Map printing Customer information Alarm and warning presentation Measurements presentation Document archive Free database objects Free data forms Queries Network and protection analysis Operational simulations Load estimation Load curves Switching planning Contingency analysis Reconfiguration Fault management Fault simulation Fault restoration Automatic fault isolation and restoration Outage information using telephone answering machine Outage report Outage data export 45

46 License Sublicense Selectable Functions Operational Functions Parallel Network Views User can create several network presentations. For example a schematic diagram in addition to geographic presentation DMS 600 Base license authorizes the most limited functionality of the program. General extensions license is always required for additional functionality licenses. The following list contains some recommendations for licenses: Network Analysis license is strongly recommended for optimal performance of restoration support functionality. Low voltage networks and operations planning are strongly recommended for optimal performance of outage reporting and statistics. The following figure shows license modules and their dependencies in DMS In version 4.3 license "Outage Reporting and Statistics" can be added without the module "Fault Location". Figure DMS 600 software licenses DMS_licenses_a.jpg 46

47 5.3. Dimensions of the network License files define not only the functionality of DMS 600 software but also the dimensions of the network database (number of primary substations having a feeding primary transformer, transformers and disconnectors). Network size can be Small, Medium, Large or No Limit. Table Maximum numbers of network components for different licenses Network size Small Medium Large Extra Large- No Limit Number of network components 5 feeding HV/MV primary substations, 400 transformers and 00 disconnectors 15 feeding HV/MV primary substations, 1000 transformers and 3000 disconnectors 30 feeding HV/MV primary substations, 4000 transformers and 000 disconnectors Unlimited number of feeding HV/MV primary substations, transformers and disconnectors 5.4. Number of workstations License files define also the number of DMS 600 software workstations (DMS 600 NE and DMS 600 WS workstations used simultaneously). The number of workstations can be between

48 6. Initialization of DMS Initialization of DMS 600 The foundation of DMS 600 is an existing SCADA application, network data and background map material. DMS 600 can also be used without MicroSCADA or other SCADA systems. The network database can be created using DMS 600 NE or it can be imported from another system. The DMS 600 distribution management system is created by the Setup Program of DMS 600, MicroSCADA tools and DMS 600 NE. To create the distribution management system: 1. Install DMS 600 software and licenses (For more information about installation and updating of the licenses, see Installation Manual). 2. Start DMS 600 NE (For more about starting, see 9.1, Starting DMS 600 NE with DMS 600 interface). During the start up process, DMS 600 software asks about login information. Give the predefined administrator user name and password (For more information about user management, see 7.1, General about user and region management). 3. Define the regions and the users with the User Manager (For more information about user management, see 7.1, General about user and region management. 4. Create the required MicroSCADA pictures and process database with MicroSCADA tools. 5. Initialize the background maps of DMS 600 software with DMS 600 NE (For more information, see 11.1, General about background maps). 6. Import the MicroSCADA station diagrams to the DMS 600 network database with DMS 600 NE (For more information, see 1.4.1, Old style HV/MV diagrams or 1.5.1, New style HV/MV diagrams). 7. Create the distribution network database with DMS 600 NE. Also, insert relay settings and load data in the DMS 600 database (For more information about creating the distribution network database, see 13.1, General about network database).. Configure the data transfer groups by using the LIB 500 Application Library DMS Interface Package of MicroSCADA (For more information, see Integration with SYS 600) or the OPC configuration tool of DMS 600 NE. 9. Define the process objects, virtual process points and picture names with the DMS 600 NE and LIB 500 Application Library DMS Interface Package (Some process object names, for example, circuit breakers are updated automatically when importing MicroSCADA station diagrams, for more information about DMS 600/MicroSCADA integration, see 1.1, General about integration of DMS 600 and MicroSCADA and Integration with SYS 600) or OPC items with DMS 600 NE. 10. Set the DMS 600 SA interface settings and open a connection to MicroSCADA via DMS 600 SA or the OPC Server (For more information about DMS 600 SA, see.2.1, Configuring SCIL API interface and.3, Controlling of DMS 600 SA and Installation Manual. 4

49 11. Define the measurements in DMS 600 NE (For more information about Micro- SCADA measurements, see , General about measurements). 12. Define the symbols (For more information, see 20.1, General about symbols). 13. Set the system specific settings of DMS 600 software with DMS 600 NE (For more information, see 21.1, General about settings). 49

50 7. User and region management 7.1. General about user and region management User management enables login and logoff functions with user identifiers without restarting the software. Region management enables dividing the network data into several regions according to feeding primary transformers and generators. The total amount of feeding primary transformers and generators defines the maximum number of regions. The user right level can be defined for each region separately. User management data is saved into the DMS 600 database. After installing the DMS 600 software, there is one predefined user with all rights in the administrator level. The user name and password for that user is ADMIN. After installing there is also one predefined region. The password of the username ADMIN must be changed right after installation to prevent unauthorized access to the system. If DMS 600 WS and DMS 600 NE are started from MicroSCADA, SYS 600 login information is automatically used. If the username and password entered in SYS 600 login do not match, the user name and the password are required. Last successful login username is proposed in the Login window. After a successful login, network windows show all parts of the medium voltage network that associate with the regions that the user has rights to view. The program operates according to the rights given to the logged in user. The user management of DMS 600 software supports Hot Stand By (HSB). Login will succeed in HSB, if one fileserver is connected. However, the user manager can be used only if the primary fileserver is connected Logoff mode If the login is quitted or failed during start up, DMS 600 NE will return to the logoff mode. DMS 600 WS also returns to the logoff mode when you click File > Logoff. You can login with the menu command File > Login. DMS 600 software has very strictly restricted functions in the logoff mode. 50

51 Table The operation of DMS 600 during logoff state Software DMS 600 NE DMS 600 WS DMS 600 SA Operation Viewing the medium voltage network state Zooming and panning the network window Login to the software Restricted closing of the program Most menu commands disabled Viewing the medium voltage network switching state Viewing the fault list (fault location is not working) Zooming and panning the network window Login to the software Most menu commands disabled Restricted closing of the program Operates normally Most menu commands disabled Restricted closing of the program 7.3. User levels DMS 600 contains five user levels with different rights: Table User levels and user rights Number User Level User Rights Admin Common User Guest No view rights Customer Servant Administrator, all rights Control rights View rights No view rights View rights + Findings The user level with no viewing rights can be used to prevent viewing the network of some special region. The user level information is saved to the network or DMS 600 database (user levels to USER_LEVELS table and user identifiers to LOGIN_INFORMATION table). The passwords are saved encrypted. Do not edit user level numbers manually. Otherwise the software will not operate correctly. Editing of user level descriptions is allowed. 51

52 In the user interface an action is visible but disabled, if the user does not have enough rights to perform the action. The table of rights for different user levels are presented in Appendix 7, User level rights Regions Region types DMS 600 software uses three different types of regions: Dynamic region contains all supplied network components of the feeding primary transformer or generator in the current switching state. The region content changes dynamically according to the switching state. Unsupplied section of the network is not included in the region. Normal region contains all network components during normal switching state (also an unsupplied network component). The content of normal region is automatically saved, when the normal switching state is saved in DMS 600 WS and after that updating the binary network database for WS in DMS 600 NE. The user rights of an unsupplied network component are defined by normal region. Extra regions can be defined to contain freely chosen network components and nodes. This makes it possible for example to control the same switching device from control rooms of several regions. Extra regions can be defined to only for example disconnectors and switching devices, or to all nodes in a selected area. To carry out a switching operation, the user needs the control rights to only one region type (dynamic, normal or extra region) Defining dynamic region Since user rights are defined separately for each region, define first regions and then user rights for each region. Region management is not needed if only one region will be used. It is recommended to plan region definitions carefully before defining regions. Changing the regions afterwards will cause extra work. 52

53 After installation there is one predefined region called All regions. This region is not shown in the REGION table. To define a region: 1. Login to DMS 600 NE using the predefined username and password. 2. Select View > Regions > Edit REGION Table with MS Access. MS Access and the REGION table in the network database will be opened. OR If the table is not accessible using MS Access, the table has to be opened for modification using database server tools. 3. Insert a code for the region (the CODE field, three characters containing characters a..z, 0 9 and _ ). Insert a name for the region (NAME field). 4. Exit MS Access. 5. Select File > Update Network Database. 6. Open a primary transformer or generator data form. 7. Choose the region using the list in the REGION CODE field. The region data is saved into the network database. The update of binary network file for WS must be done after the region definition. However, the region definitions can be changed after user rights have been defined. You must have administrator rights for all regions when adding and changing regions or defining extra-regions Defining extra region To define an extra region: 1. Switch to Data Edit Mode. 2. Select Settings > Node Region Definitions. 3. Select a node type. 4. Point a network area with the mouse. All selected nodes of the chosen node type are shown in the dialog. 5. Click Node Region Settings in the dialog. 6. Select all the regions that will be extra regions for the selected nodes. 7. Click Add region to nodes.. Click Swap regions and nodes to view a list of selected nodes. Use the Locate and Delete buttons to locate or delete the node. Click Save to save information to the NODE_REGIONS table in the DMS 600 database and in HSB-system also in the NODE_REGIONS2 table in the DMS 600 database of the second server (the NODECODE and REGION_CODE fields). Open table with MS Access button opens the NODE_REGIONS table in MS Access. 53

54 Controlling user rights Select Settings > User Manager to manage user infrormation and user rights. User names, descriptions and user manager admin rights are displayed in the User Manager dialog. Depending on the user manager admin rights of the logged-in user, the following tasks are enabled in the User Manager dialog: Table User manager admin rights User Manager Admin Yes No Tasks Adding, editing and deleting user information and user rights Viewing user's own information Changing user's own password Changing user identifiers or user rights To add or change user information or user rights, you must log in with User Manager Admin rights. To add or change user information and user rights: 1. Select Add New or Edit. The User Properties dialog opens. 2. If a new user is added, define first the username. Then add a description and password for the user. Confirm the password. The length of the user name and the password must be 4 to 20 characters. 3. Define User Manager Admin rights by selecting Yes or No. 4. Click User Levels for Regions to change the user levels for regions. User Levels for Regions dialog opens. The dialog shows all defined regions and user levels for each region. The default value for the regions is zero, which means that the highest user level will be used. 5. Click Change User Level to change the user level for the selected region. 6. Define the rights for user manager. To delete a user identifier, click Delete first in the User Manager dialog and then in the User Properties dialog. DMS 600 passwords are now case-sensitive. In addition, the following special characters are accepted: % *. _. 54

55 Changing password To change your password when you do not have User Manager Admin rights: 1. Select Change password. The User Properties dialog opens. 2. Define the new password and confirm it. The length of the password must be 4 to 20 characters. DMS 600 passwords are now case-sensitive. In addition, the following special characters are accepted: % *. _ Defining password policy settings By enabling the password policy all users of the system have a password that complies with the password policy settings. You can define the count and type of characters allowed in the passwords. By default, the password policy is disabled. To enable the password policy and edit the settings, you must log in with User Manager Admin rights. To define the password policy settings: 1. Login to DMS 600 NE using the predefined username and password. 2. Select Settings > User Manager In the User Manager dialog, click Password policy. The Password Policy dialog opens. Figure Password Policy dialog Password_policy 55

56 4. In the Password policy dialog, enable the password policy by selecting the Use password policy check box. 5. Define the password length and count of different characters. Give the settings within the following restrictions. Table Password policy settings Setting Minimum Maximum Default Minimum password length Minimum count of lower case letters required Minimum count of upper case letters Minimum count of numerics Minimum count of special characters The information field below the value fields informs about the validity of the values. The value fields with incorrect or not recommended values are highlighted. 6. Accept the changes by clicking OK. 56

57 . DMS 600 SA.1. Functions of DMS 600 SA The main function of DMS 600 SA is to serve communication routines for DMS 600 software. The communication routines of DMS 600 SA consist of two parts: communication between DMS 600 SA and MicroSCADA, and communication between DMS 600 software. Earlier Open++ Opera versions' communication has been based totally on DMS 600 SA communication (SCIL API interface) which is possible to use also in DMS 600. OPC Data Access interface of DMS 600 can be used in parallel with SCIL API in some communication tasks, if Control System SYS 600 version 9.x (SYS 600) or MicroSCADA SYS 500 version.4.5 is used. DMS 600 SA functions for MicroSCADA integration are: Establishing and breaking a connection to MicroSCADA. Managing switching state, measurement, alarm and warning data from MicroSCADA to DMS 600 WS when using SCIL API (For more information about data transfer see 1.7.1, General about component integration, alternatively can be managed with OPC Data Access interface). Sending a request to open a picture from DMS 600 WS to MicroSCADA when using SCIL API (For more information about MicroSCADA pictures, see 1..1, General about picture names, alternatively can be managed with OPC Data Access interface). Sending information about a new fault and managing fault location information from MicroSCADA to DMS 600 WS (For more information about data transfer during fault, see , Fault case). Management of automatic fault isolation and restoration. Changing the position data of manual fault detectors in MicroSCADA (For more information about data transfer of fault detectors , Fault detector data change). Controlling feeder's root point coloring to MicroSCADA when using SCIL API (For more information about root point coloring, see 1.9.2, Root point coloring and load flow direction, alternatively can be managed with the OPC Data Access interface). DMS 600 SA functions for DMS 600 WS and DMS 600 NE are: Managing the login information (For more information about user rights, see 7.1, General about user and region management). Changing system-specific settings. Changing data in the DMS 600 network data. Informing about database updates. 57

58 .2. Setting up DMS 600 SA interfaces.2.1. Configuring SCIL API interface During initialization DMS 600 SA is started and the connection to MicroSCADA is opened manually. MicroSCADA normally starts DMS 600 SA. To change the DMS 600 SA specific Support System Interface settings after start up: 1. Select Settings > SCIL API Parameters. The Settings dialog opens. 2. Define the settings described in the following table. Table SCIL API parameters Box Function Notes Username Password IP-address (Primary Micro- SCADA) TCP-port (Primary Micro- SCADA) IP-address (Secondary Micro- SCADA) TCP-port (Secondary Micro- SCADA) Data transfer intensity level Username for the Support System Interface Password for the Support System Interface IP address of the primary MicroSCADA (normal state hot) TCP port of the primary Micro- SCADA (normal state hot) IP address of the secondary MicroSCADA (normal state warm) TCP port of the secondary MicroSCADA (normal state warm) Defines DMS 600 SA frequency of operation and its internal waiting times characters Default: ABB characters Default: Opera Default: Used only if the SCADA Connection sublicense is included. Default: 1333 Used only if the SCADA Connection sublicense is included. Default: Used only if the SCADA Connection sublicense is included. Default: 1333 Used only if the SCADA Connection sublicense is included. The IP address " " refers to the used computer. Because the MicroSCADA base system is always running on the same computer, no other address is needed and it is not possible to change the default value. Analog username, password, IP address and TCP port settings are defined in the DMS Grouping Tool (for more information about the DMS Grouping Tool, see Integration with SYS 600). 5

59 The updating of connections to MicroSCADA server computers is done through a separate program (for more information about updating MicroSCADA connections, see Installation Manual) Configuring OPC interface This chapter is valid only for Control System SYS 600 version 9.x (SYS 600) and for MicroSCADA SYS 500 version.4.5. To change DMS 600 SA specific OPC Data Access interface settings after start up: 1. Select Settings > OPC Parameters. The Settings dialog opens. 2. Configure the settings of the following table. Table OPC interface settings Box Function Notes Data transfer intensity level Position indication updateinterval Measurement indication updateinterval Alarm indication updateinterval Burst timeout Defines the functionality of OPC interface. Defines how often all OPC items of the position indication group are updated (seconds). Defines how often all OPC items of the measurement indication group are updated (seconds). Defines how often all OPC items of the alarm indication group are updated (seconds). If the amount of new events from OPC Server are so high that DMS 600 SA cannot handle them all during given Burst timeout, DMS 600 SA will enter into the burst situation mode. 1 5 Default: 3 = most delays and waiting times are 1000 ms The burst situation mode means that all data values are updated only to the memory and the display, not to the database Interfaces in DMS 600 SA DMS 600 can use both SCIL API and OPC Data Access interfaces for switching states and for measurement value updates from MicroSCADA to DMS 600 WS. DMS 600 SA is used to configure and control both interfaces. 59

60 If defined, the OPC interface is primarily used for communication. Only if the OPC interface is closed, the SCIL API interface is open and also scadacode for the component is defined, SCIL API interface is used for communication. The Interface > Open SCIL API interface command opens a SCIL API connection to MicroSCADA and the Interface > Close SCIL API interface command ends it. Interface > Open OPC interface opens an OPC connection to MicroSCADA and Interface > Close OPC interface ends it. The OPC interface can also be opened and closed by selecting File > Open OPC interface File > Close OPC interface in DMS 600 WS. Table DMS 600 Interface alternatives Interface SCIL API OPC SCIL API OPC SCIL API OPC SCIL API OPC SCIL API OPC SCIL API OPC SCIL API OPC SCIL API OPC State Open Open Open Closed Closed Open Closed Closed Open Not exist Not exist Open Closed Not exist Not exist Closed DMS 600 SA interface state Interfaces is Open. Interfaces is Open. SCIL API interface is Open. OPC interface is Closed. SCIL API interface is Closed. OPC interface is Open. Interfaces are Closed. SCIL API interface is Open. OPC interface is Open. SCIL API interface is Closed. OPC interface is Closed. On the right of the taskbar of MS Windows there is a small icon for DMS 600 SA. If the user moves the pointer over the icon of DMS 600 SA, the information text including connection status information can be viewed..3. Controlling of DMS 600 SA During initialization DMS 600 SA is started and the connection to MicroSCADA is opened manually. MicroSCADA normally starts DMS 600 SA. 60

61 On the right of the MS Windows taskbar there is a small icon for DMS 600 SA. If you move the pointer over the DMS 600 SA icon, you can see the information text including connection status information. To hide DMS 600 SA window, right-click the DMS 600 SA icon. To show the DMS 600 SA information window, click the DMS 600 SA icon. You can monitor DMS 600 SA through the information window which contains the following tabs: Table.3-1 Information in DMS 600 SA window Tab Notices Events Application Extension Program Notices Service Application Notices Content Contains log messages from DMS 600 SA itself. Contains login and logoff event information and information about data transfer. Contains log messages from the Application Extension Program (Bdu_ssiaep.exe). Contains log messages from the Service Application (Bdu_ssiser.exe). Select File > Login to log in and File > Logoff to log off DMS 600 SA. Select File > Exit to end the MicroSCADA connection and exit DMS 600 SA. The user who wants to use the exit command of DMS 600 SA needs to have Administrator Privileges in MS Windows. Select Interface > Log File to open the log file of DMS 600 SA in Notepad. This log file includes general messages about program operation. It does not include events which are stored to separate event logs. Select Interface > Change MicroSCADA password to change the password for MicroSCADA Windows user account using the SYS 600 tool. You must also change the password to the DMS600 Server Application with this menu item. You must restart the DMS600 Server Application after you have changed the password. Optionally, you can change the password by running ChangeMicroSCADAPassword.bat found from file server on Server Application computers. In this case the Server Application does not need to be running. If the Server Application was running, you must restart it. With Settings > Languages you can switch the user interface language of DMS 600 SA. Select Help > About to open the information dialog box of DMS 600 SA. 61

62 9. Starting DMS 600 NE 9.1. Starting DMS 600 NE with DMS 600 interface DMS 600 NE is normally started from the SYS 600 menu Tools > DMS 600 Network Editor (Open++ Opera > OperaNE in older MicroSCADA versions). SYS 600 login information is automatically used. If the username and password entered in SYS 600 login do not match, the user name and the password are required (For more information about user management, see 7.1, General about user and region management). Last successful login username is proposed in the Login window. If DMS 600 NE is started by double-clicking the shortcut of the software or the file name OperaNE.exe, the user name and the password are required. If the DMS 600 NE is started but is in the logoff state, select the File > Login menu command. During the start up process, DMS 600 NE with DMS 600 interface: 1. Tests the connections to the MicroSCADA system and the fileserver. If the connection to MicroSCADA is not in use, a message is displayed. If the primary fileserver is disconnected, DMS 600 NE is quitted. 2. Loads the medium voltage distribution network data from the binary network file of the workstation or fileserver depending on which one is the latest one. 3. Creates a medium voltage distribution network topology from the distribution network data and the state of the switches in the network database. 4. Represents the medium voltage distribution network in a network window and auxiliary network window, colored according to the switching state of the feeders. Upon the completion of the start up process, DMS 600 NE is in Data View Mode. If login is quitted or failed software starts in logoff state (For more information about logoff state, see 7.2, Logoff mode). The network shown in the network windows is based on the data and the state of the switches in the network database. The temporary network is not loaded (For more information about temporary networks, see , General about temporary networks). During the first initialization of DMS 600 NE the network database is empty and contains no network data. Also, the background maps are not saved and initialized for the system. After the first start-up process, the DMS 600 NE user interface contains only two empty network windows. Select File > Logoff to log off and File > Exit to close the software. 62

63 10. User interface General about user interface In the user interface data is represented in dialog boxes, lists, graphics-based network windows and diagrams, geographic maps, and colors. You can select functions from menus and submenus that are controlled with the mouse and keyboard, or with toolbar buttons. The dialog boxes contain scrolling bars, list boxes, check boxes, option buttons, command buttons, and other elements similar to MS Windows user interfaces. The user interface of DMS 600 NE consists of title bar, menu, toolbar, toolbox, status bar, and main and auxiliary network windows showing the distribution network. The toolbar and toolbox can be hidden with the Window > Toolbar and Window > Toolbox commands. If not restricted by the administrator, the Window > Arrange Windows command arranges the windows back to their preset places. Network data and other data are presented using data forms and dialog boxes, together with colors in graphics-based network windows and diagrams. The Windows 'Move' cursor is used as a pointer when a moving function has been selected. In the same way, the + character refers to an addition function. If the pointer is held for a moment over a toolbar button, a description of the function pops up near the button. At the same time, text describing the function is displayed on the status bar. To display a shortcut menu, right-click the main network window. The menu content depends on the position of the mouse. To open the Print shortcut menu, right-click any list window. The command opens a separate window for saving or printing the list data. The width of columns can be changed in the preview window. The font used in printing is the defined Base font (for more information about font definitions, see , User interface fonts settings) User interface settings Every DMS 600 software has default values for primary network symbols and coloring, as well as for other network view settings, but you can easily change them, if necessary. The settings affecting the user interface are described in , User interface language settings. The administrator can specify the symbols, line colors and background color used in the network windows and diagrams (For more information, see , Defining symbol font and , General about color settings). 63

64 DMS 600 software uses geographic maps as a background for the distribution network. The administrator can set background map usage (For more information about initialization of the background maps, see 11.1, General about background maps and 11.1, General about background maps). The outlook and location of map material can be set workstation-specifically in all DMS 600 software. The background maps can also be disabled by selecting Settings > Maps > Outlook (for more information about map outlook and location, see Installation Manual and , Storage location of background maps). Free database layout can be set component-specifically using the functions in the appropriate data form. For more information about free data form layout, see , Content of free data forms. The size and location of most windows can be changed. The state of the windows (visibility, size and location) is saved when quitting the program and during the DMS 600 user's logoff Network windows General about network windows DMS 600 represents the distribution network in two network windows. The auxiliary network window always shows the whole network or selected region(s). The view of a low voltage network with a very accurate zoom is an exception. In that case, the auxiliary network window shows a more general view from the appropriate low voltage network. The main network window shows a specific area of the network in more detail. The area covered by the main network window is shown as a rectangle in the auxiliary network window. Normally the medium voltage network is visible in network windows. Low voltage networks are always read separately to the memory. If you hold the mouse cursor for a moment over the network node in the main network window, a tool tip is opened presenting information about the node. 64

65 Figure Network windows NEUI.jpg Controlling the views in network windows Network windows can be zoomed and panned. If not restricted by the administrator, the size and location of network windows can be changed. This information is saved during the shutdown of the program. The network view shown in the main network window can be changed by: Choosing the area from either network window by clicking the left mouse button down on one corner of the area and releasing it on the opposite corner (zooming). Grasping the rectangle of the auxiliary network window with the right mouse button and dragging it to the new location. Clicking the left mouse button to the center of the new location in the auxiliary network window. The rectangle of the auxiliary network window moves to the pointed new location. Right-clicking the main network window, moving the mouse in the desired direction, and releasing it (panning). Zooming the main network window step by step with View > Zoom In or View > Zoom Out commands or returning to the previous zoom with View > Zoom Previous command (or with Previous Zoom shortcut menu command). Click the middle mouse button (or wheel) in the main network window to define the center point for the new location of the zoom area Scrolling the mouse to zoom the main network window in and out. You can disable/enable the mouse scroll wheel zooming by keeping the shift button down and 65

66 at the same time rotating the mouse scroll wheel at least 6 clicks. Further, you can change the mouse scroll zooming mode (direction) by keeping the CTRL-button down while rotating the mouse scroll wheel a few times. Zooming out the main network window by keeping the shift button down and at the same time clicking one corner of the area, dragging and releasing the button in the opposite corner. When View > Zoom All is selected the main network window will show the whole network in case All Regions (default) is selected, or no regions have been defined. If one specific region is selected, the network associating to that region will be visible in the main window. View > Save/Restore Zoom... to enable the management of the zoom views in a separate dialog: Save zoom saves the current view of the main network window by the name written into Zoom name box Delete zoom deletes the selected zoom view Restore zoom restores the selected zoom view into the main network window Cancel restores the previous zoom before opening the dialog; assuming that no zooming or panning functions have been carried out after the dialog was opened Close closes the dialog keeping the last restored zoom view in the main network window Operational zooming System specific zooms It is possible to define system specific operational zoom areas in DMS 600. To save and restore the system specific zoom areas: 1. Select the View > Save/Restore Zoom... to open the Save / Restore Zoom dialog, then select the Share tab. 2. Move to the zoom area you want to save and click Save zoom button on Save / Restore Zoom dialog to save the current view of the main network window by the name written into Zoom name box. 3. To delete a selected zoom, click Delete zoom button in the Save / Restore Zoom dialog. 4. To restore a selected zoom into the main network window, click Restore zoom button in the Save / Restore Zoom dialog. 5. Cancel restores the previous zoom before opening the dialog. 6. To hide the Save / Restore Zoom dialog, select View > Temporary Zooms > Hide/Show Save / Restore Zoom Dialog (Alt+V). 7. To close the dialog, click Close. 66

67 Session specific zooms Session specific operational zoom areas can be saved and restored in DMS 600. To save and restore the session specific zoom areas: 1. Select the View > Save/Restore Zoom... to open the Save / Restore Zoom dialog, then select the Temporary tab. 2. Move to the zoom area you want to save and select View > Temporary Zooms > Save Temporary Zoom... (Alt+S). 3. Enter a name for the zoom, and click Save. All the zoom names you save appear in the temporary zoom list. 4. To restore a zoom area, select View > Temporary Zooms > Restore Next Temporary Zoom (Alt+X) or Restore Previous Temporary Zoom (Alt+Z). The next temporary zoom from the list is restored to the main network window. When you reach the end of the zoom list, 'next zoom' jumps back to the beginning of the list. The previous temporary zoom from the list is restored to the main network window. When you reach the start of the zoom list, 'previous zoom' jumps back to the end of the list. 5. To hide the Save / Restore Zoom dialog, select View > Temporary Zooms > Hide/Show Save / Restore Zoom Dialog (Alt+V). 6. To close the dialog, click Close Coloring of network windows The information displayed in the two network windows can be chosen using the submenus in the View > Coloring menu. The functions focus on the active network window. The colors represent different kinds of information. The colors of the network lines are defined with the command Settings > General (For more information, see , Network line color and line width settings for voltage levels). When presenting feeder topology (View > Coloring > Topology by Feeders), adjacent feeders are colored with a separate color so that an open switch is easy to find. Cold lines, lines in looped connections, earthed and uncertain lines are presented with separate colors. Primary transformer topology (View > Coloring > Topology by Primary Transformers) and conductor types, according to their resistance and type of conductor, (View > Coloring > Line Types) are presented. MV voltage levels (View > Coloring > Voltage levels) can be presented with different colors An extra window with color information is opened into the screen if needed. The symbols of MV/LV transformers and substations (diagrams) can be drawn with the defined feeder color regardless of the selected coloring option. The color of symbols, including subsymbols and special symbols, is changed to match the feeder color. You can turn this coloring option on and off by selecting View > Coloring > Use Feeder Colors For MV/LV Substations. 67

68 You can switch between fixed and dynamic coloring modes by clicking View > Coloring > Use Fixed Colors or by clicking the Fix button in the toolbar. The function Use Fixed Colors is common for the coloring modes Topology by Primary Transformers and Topology by Feeders. It is common also for the network windows. When Use Fixed Colors is selected, a line color legend appears to show the defined colors for the Feeders / Primary Transformers that are visible in the primary network window. The temporary network data is shown using colors during Temporary Network Mode by View > Coloring > Temporary Network command. For more information about usage of line colors, see , Using network line colors. View > Feeder command enables the selection of the feeder by the name or code. The selected feeder is shown in the main network with a warning color, automatically zoomed to the feeder area. Meshed network feeders cannot be zoomed. View > Show > Unsupplied MV/LV Stations command shows the unsupplied MV/LV stations, View > Show > Remote Disconnectors command shows the remotely operated switches and View > Show > Transformer Switches command causes the transformer switches to be represented with white symbols in the network window. The function focuses on the active switching state. Unsupplied line sections can be drawn using the dashed line. For more information, see , Defining network line color and line width. Sections fed by one circuit breaker but not having any loads connected can be presented using a specific no-load color and line width. For more information, see , Using network line colors Displaying conductor codes and line types To display conductor codes, select View > Show > Conductor Codes. To view the conductors by the line types defined for each conductor, select the menu option View > Show > Show Conductors by Line Types Hiding voltage levels It is possible to hide selected MV levels. When hidden the levels are not shown in any of the coloring modes. Hiding is done in the dialog that includes the list of all MV levels. To hide the selected levels, select View > Coloring > Hide voltages. 6

69 Coloring in network and protection analysis of DMS 600 WS DMS 600 WS includes a network and protection analysis function. According to the results of the network and protection analysis the network lines can be colored in main or auxiliary network window to indicate: Voltage drops in medium and low voltage networks (View > Coloring > Voltage Drops). Detection ability of short-circuit protection in medium voltage networks (View > Coloring > Detection Ability to Overcurrent Fault) and fault current/fuse value in low voltage networks (View > Coloring > Fault Current/Fuse). 3-phase short-circuit capacity in medium voltage networks (View > Coloring > 3- phase Short circuit Capacity) and the detection of short-circuit protection in low voltage networks (View > Coloring > Short circuit Protection). Detection ability of earth-fault protection in medium voltage networks (View > Coloring > Earth Fault Protection). Load levels in medium voltage networks (View > Coloring > Load Levels) and detection of overload protection in low voltage networks (View > Coloring > Overload Protection). Warning level and alarm level colors are used to present network and protection analysis results when the calculated values exceed the corresponding settings for the limits. The way the calculation results are presented depends on the network coloring limits. During the representation of calculation or analysis results, white is used to represent the lines which cannot be calculated because of the lack of source information (for example earthfault relay data). For more information about coloring of network and protection analysis results, see Operation Manual Code and label controls The presentation of network component codes and labels assists in finding the network component in the network. The View > Show > Substation Labels command contains a submenu for defining codes or labels of the substations shown in the network window. View > Show > MV/LV Station Labels, View > Show > Switch Labels, View > Show > Motor Labels, View > Show > Generator Labels, View > Show > Circuit Breaker Labels, View > Show > Primary Transformer Labels and View > Show > Feeder Labels commands contain submenus for defining codes or labels of the appropriate network components to be shown. The switch codes and labels in the medium voltage level correspond to customer codes and names in the low voltage level. The state of presentation of the codes and labels is saved when quitting the program. 69

70 Showing free database objects, texts and measurements The View > Show >Object Types command opens a dialog box for defining the visibility of free database object types and measurements in the network window (for more information about measurements, see , Defining free database object type and text object type and , General about measurements. The symbols and/or labels used to show the free database object types, text object types and measurements are defined in a similar way to other symbols of the network components (for more information about measurement definition, see 20.3, Symbols for free database objects and text object types ). Free database object types can also be represented with symbols in the auxiliary network window Showing temporary network data In the Temporary Network Mode the View > Coloring > Temporary Network command shows the data of temporary networks with the colors in the network window (For more information about temporary networks, see , Showing temporary network data) Showing network plan data This chapter does not apply to the DMS 600 (Base) license. The Network Planning license is required for showing network plan data. In Planning Mode, select View > Coloring > Planning to view with colors in the network window insertions, deletions and modifications to network components belonging to an open plan Symbol legend Selecting Window > Symbol Legend opens a window showing the symbols visible in the main network window. The symbols are defined in DMS 600 NE. Definition of the symbols is described in more detail in 20.1, General about symbols and , Symbol zoom range settings Parallel network views A network presentation can consist of several parallel network views that can be loaded independently in the memory of any DMS 600 WS or NE. 70

71 For example, the main network view can be a topographical representation with background maps, while the parallel network views can be orthogonal schematic diagrams that represent different parts of the network when parts of the network are hidden. A schematic diagram (orthogonal schema) is often used to make network operation cleared and more effective. A new view is created based on an existing view. The view can then be modified by moving large parts of the network or single network components, or by hiding some parts of the network. It is also possible to modify the line sections between nodes by removing all coordinate points on one or several sections. For the functionality of the parallel network views, see table below. Function Main view Parallel network view Add, remove, or move section points Add or remove any other network component Move, hide, or unhide section, node, diagram or measurement Define symbols Temporary network changes. Yes Yes Yes Yes Yes Yes, section points are saved separately for each view. No (in a temporary network components can be added and removed) Yes, coordinates and visibility are saved separately for each view. Yes, each view has its own symbols. Yes, each view has its own temporary network data file. After creating a new view temporary network changes have to be done for each view. For more information on hiding network components, see , Hiding line sections, nodes, free database objects and diagrams. For more information on managing parallel network views, see 17.1, Managing parallel network views Network diagrams General about network diagrams DMS 600 software can also present selected parts of a network as diagrams. A network diagram is generated automatically using the existing network data so that no special tasks are needed during network data entry. The network diagram window opens automatically when you click Diagram in the shortcut menu that opens when you right-click the network location in the main network window. The size of the diagram can be modified. 71

72 Use the left mouse button to select a node or line section for closer observation. The Node information dialog opens. Figure An example of a network diagram help0010.jpg Coloring in network diagrams The colors and symbols used in the network diagram window are the same as in the feeder topology presentation mode of the network window (View > Coloring > Topology by Feeders) Codes and labels in network diagrams MV/LV station and switch codes are always shown in the network diagram. Codes are replaced with labels when they are selected to be displayed in the network window Internal station diagrams If you open a station diagram, you can handle the station components in more accurate detail and you can see the switching states. 72

73 DMS 600 NE uses internal station diagrams contrary to DMS 600 WS which uses both station and control pictures from MicroSCADA and internal station diagrams. Normally internal station diagrams are imported from MicroSCADA. Station diagrams can be created in DMS 600 NE. A particular symbol in the network window means that the object has a station diagram presentation. Internal station diagrams can be seen on the network window when zooming close enough to a station. The View > Show > Substation Labels command contains a submenu for defining the showing of codes or names of substations in the network window. In DMS 600 NE the internal station diagram and in DMS 600 WS the MicroSCADA station or control picture is opened to a separate window when the symbol or station diagram in the network window is clicked with the right mouse button and then clicked the Diagram command from the shortcut menu. The View > Station Diagram command can also be used to open separate station diagram windows. This function asks for the name of the station to be opened in a diagram window. It is possible to have multiple station diagram windows open at the same time. Editing of the diagrams is made in the network window (not in a separate diagram window). However, inserting a new feeder is an exception and can be started inside the network diagram window. Figure An example of an internal station diagram help0012.jpg 73

74 10.7. Coloring in the station diagrams The colors of the feeders in the station diagram windows are always the same as the feeder colors in the feeder topology presentation mode of the network window (the View > Coloring > Topology by Feeders command is selected). If View > Coloring > Use Fixed Colors is selected, the same fixed colors can also be seen in the station diagram windows. The colors of the root points of the feeders in the MicroSCADA station and control pictures in DMS 600 WS are also always the same as in the feeder topology presentation mode (For more information about root point coloring, see 1.9.2, Root point coloring and load flow direction) General about other fixed medium and low voltage diagrams Other medium and low voltage network diagrams can also be created in DMS 600 NE. These diagrams contain network objects that can be shown more accurately in the diagram mode (for example MV/LV stations and disconnector stations). This type of connection between network objects is called a site node. To display the diagrams in more detail, zoom in close enough. To open the fixed diagram window: 1. Open a shortcut menu by right-clicking the site node in the main network window. 2. Select Diagram in the shortcut menu. The administrator can set a dynamic network diagram to open instead of a fixed diagram when Diagram is selected ( for more information about configuring the way the diagrams are opened, see. You can switch the type of opened diagram window by holding down CTRL key and simultaneously clicking Diagram Online help DMS 600 has an Online Help. It contains the following functions: Help > Contents and Index starts the online help. The help navigator contains four tabs: Contents shows the contents of the DMS 600 WS Help Index shows the index list of the DMS 600 WS Help Find enables full text search Favorites enables the definition of favorite pages Help > What's This? changes the pointer into a question mark and after the user clicks a place on the screen, a help window about the chosen function pops up. Help > About opens a window that shows DMS 600 version information. This command also prints the license information to the alarms list. 74

75 The online help can also be opened by: Pressing the F1 key. The help displays the help window associated to the active function of the program. Clicking Help in some dialog boxes. The help displays the help window associated to the active dialog box. The user interface of the help contains a navigator, toolbar and the actual content. You can open the shortcut menu by right-clicking in the help screen. 75

76 11. Initialization of background maps General about background maps Raster and vector based geographic maps can be used as background maps in DMS 600. The system supports the following map formats: Raster maps in BMP (Windows bitmap format). Vector maps in AutoCAD dxf format. All background maps used in DMS 600 software should be converted to these map formats and adjusted to a single orthogonal orientation, that is, where the x-axis is horizontal (from left to right) and the y-axis is vertical (from down to up). Take backup copies of the installed background maps Directories for background maps Several subdirectories are reserved for different kinds of map materials. In the six fixed subdirectories under the user-definable Map directory you can install different background map materials. Each subdirectory can contain monochrome raster maps, multicolored raster maps or vector maps. In addition, there are three fixed subdirectories for draw upon vector maps that are always drawn on the top of the screen. All three draw upon vector map materials have their own color definitions (For more information about color definitions, see 11.1, General about background maps). The titles of the different map materials are defined in DMS 600 NE (For more information about defining the titles for the maps, see , Map material titles). Each fixed subdirectory has also a fixed Material subdirectory for the original map material. Save monochrome raster maps, multicolored raster maps and vector maps to their own subdirectories. Different materials must be saved to subdirectories of their own, even if the only difference would be the accuracy level (that is, the raster size in pixels differs) of the same material. After the installation of DMS 600, the original map materials (the source files) must be saved to the Material subdirectories of the corresponding map directories Titles for map materials Titles for map materials and draw upon map materials are used in dialog boxes for different maps. 76

77 To define the system specific titles for map materials: 1. Select Settings > General. 2. Open the Map materials tab. Use the scrolling arrows to scroll the tabs if needed. 3. Insert the titles for material1 material6 and draw_upon_material1 draw_upon_material Default values for background maps The default values for the map adjustment data and the settings related to the DXF conversion can be defined by running the Installation Program (For more information about installation definitions, see Installation Manual). The defined values will be saved in the settings file (Common.prm) on the fileserver. After installation the default values can be changed using a separate settings program. For more information about this settings program, see Installation Manual Modification of the background maps General about background maps All background map material must be converted to either.bmp or.vg2 format. The.vg2 format is an internal vector format of DMS 600 products. You can also modify raster formatted map material by editing the color palettes, cutting large bmp raster maps into smaller pieces and resizing them into different accuracy levels, and saving them into individual map material directories. With this kind of modification you can speed up the handling of background maps on the screen. After modification, you must adjust the converted map materials by the functions of DMS 600 NE (For more information about the adjustment, see , Beginning of the adjustment). The zoom ranges for each map material (accuracy level) must also be set. For more information about zoom range definitions, see , Defining workstation specific outlook Conversion of raster formatted maps Raster material can be obtained from computer data or scanned from paper maps. Convert other raster formats (for example TIFF) to BMP by using an external tool, for example PaintShopPro. To convert raster format to BMP in PaintShopPro: 1. Open the original raster map in PaintShopPro 2. Select File > Save as. 3. Select BMP from the List File of Type menu. 77

78 Monochrome raster maps should be saved using either the BMP subformat OS/2 or the BMP subformat Windows RGB encoded. For color raster maps the BMP subformat Windows RLE encoded is the most efficient. The maximum color depth of the color bitmaps is 256 colors (that is, bits/pixel) Modification of raster formatted maps You can also use an external tool to edit the color palette of BMP formatted map material, to cut the BMP formatted map material into smaller pieces and to resize them into different accuracy levels. It is recommended to cut each BMP formatted raster map to under 3 MB (preferably < 1 MB). When decreasing the accuracy level for larger views, even a few hundred kilobytes is big enough. BMP formatted raster maps designated for adjustment must be placed directly in the corresponding map material subdirectory (not to the Material subdirectory) Conversion of vector formatted maps Select Settings > Maps > DXF Conversion in DMS 600 NE to convert supported DXF vector formatted maps into the DMS 600's internal vg2 format. Here are some remarks associated with the DMS 600 NE DXF conversion: Dxf formatted maps cannot be rotated during DMS 600 NE dxf conversion. If rotation is necessary, you must rotate the map to the proper orthogonal direction by using, for example, the Rotate command in AutoCAD. Dxf formatted maps can be moved and scaled during the DMS 600 NE dxf conversion (or later map-specifically by giving the displacement in the x and y direction). Use the Installation Program or the Settings.exe program to change the corresponding settings. For more information about programs, see Installation Manual. The UCS (User Coordinate System) definition in AutoCAD dxf format is ignored by DMS 600 NE. Therefore, if the adjustment of maps using AutoCAD is desired, the UCS definition must be removed and only the Move and Rotate commands used. s are converted to a text file (.txt), which will be adjusted with the map file (.vg2). All AutoCAD BLOCKS will be omitted during the conversion from dxf to vg2! Run the EXPLODE command in AutoCAD several times to get rid of BLOCKS within BLOCKS. Some line types of the latest AutoCAD versions are not supported. If possible, save the dxf file by using the Save As command and select AutoCAD R12 DXF format. DMS 600 NE dxf conversion function adjusts the vector-formatted maps automatically during the conversion, so there is no need for adjustments in normal cases. (For 7

79 more information about adjustment, see , Adjustment of vector formatted maps). The converted and adjusted vg2-maps with txt files are saved into the corresponding map material subdirectories (not to Material subdirectory). The map data is also saved into the network database after the adjustment. The update of the binary network file must be done after dxf-conversion. During the dxf conversion, the text file Dxf_layers.def is created into the Material directory of the original dxf files. The def file contains the layer information of the original dxf file. The default color for every new layer will be the color used in AutoCAD. You can edit the layer colors in the Dxf_layers.def file with, for example, the Notepad editor. After the editing of color information, you can run the dxf conversion again Adjustment of background maps Beginning of the adjustment You can adjust the background maps using DMS 600 NE. The map data is saved into the network database after the adjustment. The update of the binary network file must be done after the adjustment. The File > Update Network Database command is used to update the binary network file from the inserted and/or updated map data in the original network database. When this command is given, a message is sent to all workstations to inform them about new data. This data can be updated immediately by accepting the suggestion in the message window or later by selecting File > Refresh Network Data in DMS 600 WS. If raster maps are used, you should enter the coordinates of upper left and lower right corners or the coordinates of the upper left corner and the meter or pixel value of bitmap. The coordinates of vector maps are automatically defined. The following adjusted data is saved in the database: The name of the map file. The format (raster/vector). The map type (normal or draw-upon). The map color (yes/no). 79

80 The accuracy level (the accuracy level defines which subdirectory is used). The coordinates of the upper left and lower right corners. Select Settings > Maps > Adjustment to open the Adjustment of Background Maps dialog box. To change the adjustment data of the adjusted maps, click Adjusted Maps (For more information about updating the adjustment data, see , Update of the adjustment data) Adjustment of vector formatted maps The DMS 600 NE DXF conversion function adjusts the vector maps automatically during the conversion. Therefore, there is no need for adjustments in normal cases. However, vector maps in the vg2 format can be adjusted without a new conversion (For more information about updating the adjustment data, see , Update of the adjustment data). The vg2 vector maps designated for new adjustment must be placed in the corresponding Material subdirectory. When adjusting vector-formatted maps, select first the adjusted map material under the Vector maps frame. Adjust opens the File List dialog box for the files in the corresponding directory. After the selection of file the vector map material is read, the required data is updated automatically, and the map material is copied from the material directory to the corresponding subdirectory Adjustment of raster formatted maps General about adjustment of raster formatted maps BMP formatted raster maps designated for adjustment must be placed directly in the corresponding subdirectory (not to the Material subdirectory). To adjust BMP formatted map material: 1. Select Raster maps to open the Adjustment of Raster Maps dialog box. 2. Select the adjusted map material under Map material. 3. Then click Select map to open a standard dialog box in which you can select the map to be adjusted. To show the selected map in a separate window, click Show. If the selected map is a color bitmap, the Color bitmap check box will automatically be checked. If the adjustment is based on corners and the coordinates of corners are inserted manually, you do not need to click Show. 0

81 The selected map can be adjusted in two different ways: Based on corners (based on the coordinates of the map corners) Free selection (you can select the coordinates freely) Select the method by clicking the appropriate option Adjustment based on map corners You can enter the coordinates of the Left-top corner and the Right-bottom corner of a map from the keyboard or indicate them with the mouse on the screen. If entering the coordinates from the keyboard: 1. Enter the coordinates. 2. Click Adjust. This updates the data in the database. If using the mouse: 1. Click Point out. 2. Indicate the map corners (that is, the upper left and lower right corners respectively) with the mouse on the existing background map on the screen. 3. Click Adjust. Coordinates indicated with the mouse can be adjusted using the keyboard. The user can also indicate the first corner with the mouse and the other corner from the keyboard. If the user gives only the upper left corner coordinates before clicking Adjust, a separate dialog box is opened asking for the meter or pixel value of the bitmap. Then the lower right corner coordinates are calculated using the data Adjustment based on free selection First click Adjustm.Point and then indicate two adjustment points with the mouse on the map being adjusted, which is shown in the separate window (Show). Do not change the size of the separate window. After that the geographical coordinates of the corresponding points can be entered from the keyboard or with the mouse. When entering the points from the keyboard, first write the coordinates and then click Adjust, which updates the corresponding location in the data file. If using the mouse, first click Map Point, which closes the separate window, then indicate the points (the corresponding adjustment points which have just been entered) with the mouse on the existing background map on the screen. Finally click Adjust. Coordinates indicated with the mouse can be adjusted from the keyboard. The user can also indicate the first corner with the mouse and the other corner from the keyboard. If the user gives only the upper left corner coordinates before clicking Adjust, a separate dialog box is opened asking for the meter or pixel value of the bitmap. Then the lower right corner coordinates are calculated using the data. 1

82 Update of the adjustment data Adjusted Maps opens the dialog box which is used to update the adjustment of both raster and vector formatted background map data afterwards or to remove the adjustment data from the database. The Adjusted Maps dialog box contains all the adjusted maps. Choose one of the map files to show the adjustment data in the bottom of the dialog box. You can change the adjustment data of raster formatted maps using the keyboard and save the new data using Update. If the map is a color map, select the Color Map check box. After the selection of a vector-formatted map, click Update. Dialog boxes are used to insert the changes in x- and y-directions and to update the adjustment data. The default value is the last inserted value. Restore Initial Value restores the last inserted value. Remove removes adjustment data of the chosen map (both raster and vector formatted maps). 2

83 12. Initializing GPS service General about GPS device A GPS device can be used to collect coordinate data (waypoints) from the terrain. GPS waypoints are inserted as batched or continuous to the network database. These points can then be used during network editing. The GPS waypoints are stored using WGS4 datum in latitude/longitude format. The continuous locating of GPS device supports both WGS4 and national map datum (for more information about map datum settings, see , Map datum parameters). GPS data communication in DMS 600 is based on NMEA-013 standard which is a serial communications standard for the encoding and sending of GPS and other navigation information between devices. The standard allows individual manufacturers to define proprietary sentence formats. NMEA does not support Hand Shake mode Creating connection between MAGELLAN Meridian Platinum and DMS 600 NE The configuration example has been made using the MAGELLAN Meridian Platinum GPS device (GPS RS-232) and NMEA v 2.1 GSA. The only proprietary sentence used in this solution is PMGNCMD. The command is specific to MAGELLAN GPS devices. It is used to download all waypoint data stored in GPS device's memory. You can import GPS data from the GPS device to the computer is using the serial port and serial cable. To configure the serial port communication: 1. Set the serial port settings of the computer: a. Open Windows Device Manager and select Ports. b. Select Communication Ports (COM1) and Port Settings. c. Define the port settings: Bits per second to 9600, Data bits to, Parity to None, Stop pits to 1 and Flow control to None. 2. Check the communication settings of the GPS device (for more information, see the GPS device's user manual). a. Set the GPS device to send NMEA-013 data. b. Set GPS device's Baud rate to match the serial port settings of the computer (9600 bits/s). 3. Connect your GPS device to the computer using a serial cable. 4. Use Windows HyperTerminal program or any convenient terminal program (Telix, Procomm, Windows Terminal, etc.) to check that your COM port is receiving data. If the COM port is receiving data, you will see NMEA messages starting with $. 5. Set up communication settings in DMS 600 NE: 3

84 a. Select Edit > GPS Data to start the GPS interface. The GPS NMEA Data dialog opens. Buttons are enabled or disabled depending on the GPS device status. b. Click Setup Comm. c. Define the serial port settings. Default is Port 1 and Baud 9600 bit/s. d. Click Connect to GPS to establish the connection to the GPS device. Real time positioning data is read, if the GPS device is valid. DMS 600 NE saves the waypoint data into the file (wpf) in the following format: $PMGNWPL, ,N, ,E, ,M, STATION,MOSCOW,a*41. If the waypoint data is needed to read from other files, it must be in the same format. 4

85 13. Databases General about network database The network database is a central part of the DMS 600 software. The database contains data about the lines and components of the distribution network. Depending on the license, the network database includes only medium voltage or both medium and low voltage networks. Load and relay data also have to be imported into the network database if the network and protection analysis are included. You can also obtain relay setting data from the relays via MicroSCADA. Additionally, the database can contain free database objects (for example, data of tenancies and measurements), documents attached to the components, temporary network data and customer data. The inserting and updating of network data is allowed in the Data Edit Mode. The Data View Mode only allows the browsing of existing network data. You can browse, update and insert temporary network data in the separate Temporary Network Mode. Network data is managed by the graphics-based user interface of DMS 600 NE with network windows and geographic background maps. You can insert and edit graphicsbased data using the mouse in the network windows and non-graphics-based data via data forms or free data forms. You can import internal station diagrams from MicroSCADA. The integration of DMS 600 and MicroSCADA requires that links between network components in different software are included in the database. The links between process objects, the virtual points and MicroSCADA measurements to the network components are updated in DMS 600 NE and saved to the DMS 600 database. Cross-connections between MicroSCADA pictures and DMS 600 stations are also saved in the database. GPS waypoints (terrain coordinates) from a GPS device can be inserted to the network database to help when adding electrical networks to correct locations on map (for more information about inserting GPS waypoints, see , Using GPS waypoints during editing). Network data can also be imported from another system. This alternative will need specific engineering Network database model Network database tables The basic data items consist of nodes and line sections between them. DMS 600 also uses the concept "site node". A site node contains network objects located near each other. For example, a disconnector station can be depicted with a site node. 5

86 Tables representing data from different components are linked to the nodes. A data model of the network is presented below. Figure Network data model DMS_data_model_a.jpg A description of the network database tables is in Appendix 2, Tables of the network database Network database component codes Component codes used in the network database: Table Component codes Code Component Code Component A Busbar P Primary transformer B Shunt reactor Q Capacitor C Current transformer, neutral current transformer R LV substation D Fault detector S Feeding point E Disconnector T Not used F Free object U Voltage transformer G Generator V Not used 6

87 Code Component Code Component H Serial reactor W LV switch I Conductor joint X Branching point J LV box Y Not used k LV feeding point (transformer) Z Arc suppression coil K Circuit breaker $ Customer L Open line end Light (lighting network) M Transformer # LV switch (lighting network) N Motor + Lighting network feeding point (lighting network) O Fuse & LV substation (lighting network) Updating network data to workstations DMS 600 software uses two kinds of databases: the original network database and the binary network file (Network.dat). The temporary network data can be maintained using a separate temporary network file (Tempnet.dat). The network database is created using the functions of DMS 600 NE. The updates of network data go directly to the original network database. Select File > Update Network Database command to update the binary network file (Network.dat) from the inserted and/or updated network data in the original network database. When you give this command, a message is sent to all workstations to inform them about the new network data. You can update this data immediately by accepting the suggestion in the message window or also later by selecting File > Refresh Network Data in the instances of DMS 600 WS. The binary network file is saved only to the local workstation, if the updating for all is prohibited. A scheduled update can be defined to ensure that the last network changes are available in all workstations. The scheduled update requires that definitions to the settings file are made and that the DMS 600 NE software is running in the selected workstation (For more information about making definitions to the settings file, see 21.10, Defining scheduled update of binary network file). You can leave DMS 600 NE in logoff state to avoid unauthorized using. If DMS 600 NE is in logon state during a scheduled update, a message is displayed and you can prevent the update by clicking the Stop button or the ESC key within 10 seconds. When the binary network file (Network.dat) is updated, a log file (Networkupdated.txt) is created or updated. The log file is placed in the Data directory of the server. The file contains the date and time of the update and the name of the computer that has updated the binary network file. 7

88 13.4. Definitions to network database Defining free database object type and text object type Free database enables the definition of customized object types and free fields to primary network components. The administrator of DMS 600 defines the free database object types into the network database using database management tools: 1. Make a copy of the model table COMPONENTCLASS SPECIFIC MODEL TABLE of the network database and rename the table according to the object type to be created. 2. Add fields to the table. 3. For each object type also add a record to the COMPONENTCLASS table and enter the name of the specific table to the COMPONENTCLASS field. COMPONENT- CLASSID can be any unique number, but it is recommended to number them 1,2,3 and so on. Define the voltage level for an object type with the NETLEVEL field. 0 means medium voltage level, 1 low voltage level and 2 both medium and low voltage levels. 4. If you want to alter the box label text shown in the free data form, enter the original field name in the CODE field in the language-specific table of Genlang.mdb and enter the text to be shown in the GENTXT field. If you want to restrict the label text usage to one table only, use the form [TABLE NAME].[FIELD NAME] in the TEXTKEY field. Otherwise, the box with that name in all tables will be labeled according to the definition. 5. In order to implement a list in the box shown in the free data form, define the code infos (for more information about code info, see , Defining code info). 6. In order to attach to an auxiliary table from where to select records (for example type data), create a relation between the appropriate fields of the two tables. 7. Define the symbol for the object type. For text object types, define only the size and color for codes without the symbol definition. For more information about symbols, see 20.3, Symbols for free database objects and text object types. When you have defined or updated object types, you must restart DMS 600 NE and update the network database to use the new objects Defining new fields to outage reporting With free database you can add new fields into the free data form of the outage report in DMS 600 WS. Add desired fields into the following tables.

89 Table Tables for outage reporting Report type: Fault report Maintenance outage report LV network outage report Reclosing report Table name FAULTREPORT MAINTENANCEOUTAGEREPORT LVOUTAGEREPORT RECLOSINGREPORT Importing customer information DMS 600 contains functions where customer information is required. These include Customer Service and Trouble Call Management functions. DMS 600 software can also be defined to use load curves for load modeling. DMS 600 does not include customer data management. The customer data with customer loads can be imported to the network database using import functions (for example, via an ASCII text file). You can also create a linked table in the network database to directly use an external customer database. To import customer information: 1. Create a table or view/query named CUSTOMER (obligatory) with the fields LV_NETWORK (obligatory) and CODE (obligatory) to the network database. The records describe all the electricity meters in the network as customer points. LV_NETWORK field contains the information about the MV/LV substation to which the appropriate customer defined with the CODE field belongs to. Additional fields can be added freely to CUSTOMER table or query. 2. If load curves are used, create also the following fields: Table Tables for outage reporting Field CURVE ENERGY1 ENERGY2 Number, integer Number, long integer Number, long integer Content The load curve number given by Load Curve Editor (For more information, see Appendix, Load curve editor) Annual energy1 in kwh. The annual energy can be given using only this energy field. Annual energy2 in kwh Both energy fields are usable, for example, in case of 2-time tariff where 2 annual energies are measured for the customer. 9

90 Field CUSTOMER_NODE, 15 characters Content The field is required if LV networks are included in the DMS network model. This is the code (or number) of the LV network service point that feeds the electricity meters 3. Save the table containing the customer information in the network database. To create the query CUSTOMER using obligatory field names if the external customer database does not include those fields: 1. Save the table containing the customer information into the table CUSTOMER_EXT in the network database. 2. Create an auxiliary table CUSTOMER_AUX including the obligatory fields associated to corresponding fields in the external customer table CUSTOMER_EXT. 3. Create a query named CUSTOMER including the customer data of the obligatory fields via the auxiliary table CUSTOMER_AUX. 4. Insert the customer energy data directly to the table, if it is not available in the external customer database. For more information about manual inserting of load curve data, see , Manually inserting load data for load curve modeling. When LV network modeling is included in the DMS 600 system, the DMS 600 NE maintains the LV network to which the customer belongs. The data is updated to the LV_NETWORK field in the LV_CUSTOMER_NODE table. The information can be fetched with the CUSTOMER_NODE field that has to be available in the imported customer data, or otherwise maintained, for example, in the CUSTOMER_AUX table Definitions to DMS 600 database General about DMS 600 database The DMS 600 database is another central part of the DMS 600 software. DMS 600 database contains: User level information Region information Login information Customer information (internal or linked) Customer load information (internal or linked) Real-time states of switches LV switch state changes Line section state Measurement data Alarms data 90

91 Part of the fault data (manually defined exact fault location, manually changed fault detector state, responsibility, state of the fault) Outage data Outage reports Outage archives Field group information LV text data Notes GSM message information Defining LV switch changes You can save the changes of the switching state in the low voltage network to DMS 600 WS. LV switch change data is saved into the table LV_SWITCH_CHANGES. The updating of LV switch changes in DMS 600 NE (that is, updating the normal switching state) updates the table LV_SWITCH_CHANGES, if necessary Defining reports and forms Definitions of reports and forms enable the reporting of network database content using DMS 600 menu commands (for more information about reporting, see 26.4, Reporting). MS Access is used as a reporting tool with DMS 600. Reports and forms can be saved directly into the network database if an MS Access database is used. If a database server, such as MS SQL Server, is used, you must create links to the required tables. For this purpose, you can use the Network.mdb that is installed to the data directory. The empty local tables are replaced by links to database server tables. The administrator of DMS 600 defines the reports and forms using MS Access as described below: 1. Create reports and forms using MS Access functions. 2. Open the table SETTINGS of DMS 600 database in MS Access. 3. Define the following two records for the amounts of reports and forms to the table: Table Records for the amounts of reports and forms SETTINGGROUP SETTINGKEY SETTINGUSER SETTINGVALUE AccessReports Number Common Amount of reports AccessForms Number Common Amount of forms 4. Define the following kind of records to each report and form of the table: 91

92 Table Records to reports and forms SETTINGGROUP SETTINGKEY SETTINGUSER SETTINGVALUE AccessReports Running number for report (1...n) Common Name of the MS Access report AccessForms Running number for form (1...n) Common Name of the MS Access form 5. Save the table. When you have defined and updated reports or forms, you must restart DMS 600 NE to use the new definitions Defining GSM messages With DMS 600 WS you can send GSM messages about an outage to important customers automatically after faults or manually in any outages. GSM messages are based on SMSServ 2.1 software (Apex Automation Oy) and Micro- SCADA. A message is sent as a command procedure using the SCIL API layer. For more information about engineering required in MicroSCADA, see Integration with SYS 600. Some definition is also required to the settings file (for more information about settings, see 21.7, Defining outage GSM messages to settings file. The automatic composition of GSM messages can be based on a separate text database, or required tables and queries can be included to the DMS 600 database. The content of GSM message is formulated using specification texts and outage areas from SMS_CODES and SMS_AREAS tables. The choice of the area for an automatic GSM message is based on scadacode of the circuit breaker in the SCADACODE field in SMS_AREAS. In manual GSM message generation, the drop-down list of the areas is defined using the TECHNICAL_DESCRIPTION field of SMS_AREAS tables. Table Symbol usage for time and date in Info fields of SMS_CODES table Symbol Use Symbol Use %s DMS 600 WS inserts text to this field. %M Minutes as a decimal number (00 59) %a Abbreviated weekday name %p Current locale s A.M./P.M. indicator for 12-hour clock %A Full weekday name %S Seconds as a decimal number (00 59) %b Abbreviated month name %U Week of year as a decimal number, with Sunday as the first day of week (00 53) %B Full month name %w Weekday as a decimal number (0 6; Sunday is 0) 92

93 Symbol Use Symbol Use %c Date and time representation appropriate for locale %W Week of year as a decimal number, with Monday as the first day of week (00 53) %#c Long date and time representation, appropriate for current locale. For example: Tuesday, March 14, 1995, 12:41:29. %x Date representation for current locale %d Day of month as a decimal number (01 31) %X Time representation for current locale %H Hour in 24-hour format (00 23) %y Year without century, as a decimal number (00 99) %I Hour in 12-hour format (01 12) %Y Year with century, as a decimal number %j Day of year as a decimal number ( ) %z, %Z Time-zone name or abbreviation; no characters if time zone is unknown %m Month as a decimal number (01 12) %% Percent sign An example: The formulation of GSM message uses the specification text "Distribution outage in %s of FAULT_TEXT field in the SMS_CODES table. The characters %s are replaced with the outage area value of the field AREA_TEXT in the SMS_AREAS table. In automatic sending, the area for the GSM message is based on the SCADACODE field of the same table. In manual sending, you can define the area. The other part of the GSM message is based on specification texts defined by the REPAIRED and NO_TIME fields. If time data for repairing is not defined, the specification text "Fault clearing has been started. of the NO_TIME field is used. Otherwise, the specification of the REPAIRED field with time data is used in the form "Distribution will be back %s at time %s, in which the first %s is replaced with the specification texts of the TODAY or TOMORROW fields. The second %s is replaced with the defined time data formulated according to the TIME field. The specification text of END_NOTE field is added in the end of the GSM message. DMS 600 WS uses the SMS_CUSTOMERS and SMS_IMPORTANT_CUSTOMERS queries to define the receivers and their telephone numbers. Both queries have to contain the following fields. Table Obligatory fields in the SMS_CUSTOMERS and SMS_IMPORT- ANT_CUSTOMERS queries Field CODE Meaning Code of the customer, same as in the CUS- TOMER table 93

94 Field NAME LV_NETWORK CUSTOMER_NODE TELEPHONE_NUMBER Meaning Name of the customer, same as in the CUS- TOMER table Code of the customer LV network, same as in the CUSTOMER table Customer node code, same as in the CUS- TOMER table Telephone number of the customer The query SMS_CUSTOMERS has to give all customers to whom GSM messages will be sent and the query SMS_IMPORTANT_CUSTOMERS has to give those customers to whom a new message will be sent automatically if a new fault occurs. The information of sent GSM messages is saved into the tables SMS_MESSAGES, SMS_MESSAGE_CUSTOMER and SMS_MESSAGE_NUMBER. To generate GSM messages in other languages: 1. Create a new field to the SMS_CODES table. Insert a name for the field, for example, SVENSKA. 2. Translate the text in the INFO field into this new field. 3. Start DMS 600 WS. 4. The SMS Messages dialog will contain a new drop-down list above the message window. When you select the created new language (in this example, Svenska), the GSM message will be generated using the translated texts Defining GPS data of field groups On-line GPS data can be used for the definition of field crew location in DMS 600 WS. DMS 600 provides the standard interface for the data. The functions require the definition of a table for GPS data. Communication with GPS devices is very much country and project-specific and is out of the scope of this manual. GPS data is located in the FIELDGROUPLOCATIONS table of the DMS 600 database. Third-party software products communicating both with a specific GPS device and with the DMS 600 database produce the coordinates of field crews into the table. The data can be inserted or linked to the table. If the database is not duplicated, both databases have to contain the link to the external database. The DMS 600 database is used only for reading GPS data. The FIELDGROUPLOCATIONS table must contain three fields with the following contents: Table Required fields in FIELDGROUPLOCATIONS table Field Content CODE Field crew ID code 94

95 Field Content LATI LONGI Latitude of field crew location, for example "27, ", OR "E ,". Longitude of field crew location, for example, "61,621111", negative number for southern hemisphere, or "N ,6", "S" for southern hemisphere You can define whether the coordinate system in the table (or query) is in WGS4 datum or in national datum. Some GPS devices can produce the coordinates only in WGS4 datum Defining outage data export DMS 600 WS enables the exporting of defined outage data. This outage data file can then be imported, for example, to a customer information system. An export file contains outage areas and data about them. Every outage area is saved to the export file only once. Exported outage data is collected from reported outages in the DMS 600 database using the query. The query is formed using the outage type, starting and ending dates and duration of the outage. To manage the outage data file, you must add the EXPORTDATE field to the OUT- AGEAREAS table and to every outage report archive table in the DMS 600 database. The EXPORTDATE field of the outage is saved when you export an outage area to the export file (for example, :03:36). The way to formulate the name of an export file is OutageExport_<year-month-date>_<hour-minute-second>.txt, for example OutageExport_2002_10_25_1_03_36.txt. The file is saved into the subdirectory Outage/Export. The DMS 600 WS software does not contain the commands for the management of EXPORTDATE field in outage achieve tables. The administrator of DMS 600 software manages the EXPORTDATE field in the DMS 600 database using MS Access, that is, the field is required to be clear for the exporting of outage areas again. The export file is an ASCII file containing rows. Every row contains data of one outage area separated with commas. The content of each row in the export file is described in the following table. 95

96 Table Content of each row in the outage export file Field description Outage type Content 0 = fault 1 = maintenance 2 = LV fault 3 = LV maintenance 4 = reclosing 5 = delayed reclosing Outage area code Outage starting time Outage ending time Disturbed LV networks (separated with #) Name of the region Duration of outage Number of disturbed LV networks in outage area (pcs) Sum of duration in LV networks in outage area (h) Number of disturbed LV customers in outage area (pcs) Sum of duration of disturbances in LV networks in outage area (h) Not delivered energy in outage area (kwh) Number of breaks in outage area LV customers (separated with #) For example "A2002/6" (=archive table named OUTAGEAREAS2002 outage area 6) or "92" (=Outage 92 from OUTAGEAREAS table) :07: :24:5 3012#3013#3057#3067#3075#3115#311#3174 VIRRAT 00:17: # #... # #.. Concerns only in low voltage fault or maintenance, otherwise clear Other database definitions Defining telephone answering machine DMS 600 WS has a function to control a telephone answering machine for informing a calling customer about maintenance and fault outages. The telephone answering machine is based on NextInfo (Voicebit Oy). 96

97 The message of the answering machine can be created partly automatically using fault data. The composition of answering machine messages is based on a separate TAM database. Some definition is also required to the settings file (for more information about setting up a telephone answering machine, see 21., Defining telephone answering machine usage to settings file). Define the message information into the LOCATION table of the database using MS Access as described in the following table: Table Fields in the LOCATION table Field LOCATION SCADACODE Meaning Name of the recorded voice file. Data used also in the switching state document (for more information, see , General about switching state document). For feeders, the scadacode of the feeding circuit breaker For DTUs, scadacode for disconnector normally feeding the zone (any other individual scadacode of DTU can be used, if only manual messages are needed). For circuit breakers' zone, individual code deviating from the circuit breaker scadacode. Scadacode is needed for automatic message generation for the faulted feeder or DTU. Field can be left empty, if only manual messages will be used. TECHNICAL_DESCRIPTION GROUP TEXT FIXALARM Short description about the area shown in the DMS 600 WS dialog. Definition used for filtering in the DMS 600 WS message management. Grouping against primary substation number as a default. Recorded message in written form. Data used also in the switching state document (for more information, see , General about switching state document). Data about sending the internal alarm. 0 = no alarm 1 = alarm CUSTOMERALARM Data about sending the customer alarm. 0 = no alarm 1 = alarm In a duplex busbar system, two different circuit breakers (with different codes) can feed the same feeder. Define the same message for both of these circuit breakers. Define the subareas into the CONNECT table of the database using MS Access as described in the following table: 97

98 Table Fields in the CONNECT table Field AREA SUBAREA Meaning Scadacode of the larger area, normally circuit breaker zone. Scadacode of the smaller area, normally disconnector. The same disconnector can be defined under many circuit breakers (for alternate switching states). Created alarm messages are saved into the MESSAGES table which contains the following fields: Table Fields in the MESSAGES table Field ID LOCATION INFO2 NAME INFO ALARM Meaning Identification number of the message. Name of the recorded voice file. Data used also in the switching state document (for more information, see , General about switching state document). Estimated day for repairing. Cause of the outage. Describes the state of the alarming. 0 = new 1 = read Defining switching state document General about switching state document A switching state document is a colored graphical representation of the whole distribution network above a geographical background map. The document contains information about unsupplied MV/LV stations. A switching state document can be created manually or automatically in DMS 600 WS (for more information about setting automatic creation, see , Regular creation of switching state document). The document is created using MS Word, which has to be installed in the workstation. The supported MS Word versions are 97, 2000 and The administrator is responsible for deleting the outdated switching state documents. 9

99 Static texts in switching state document A switching state document contains static texts, which are managed in DMS 600 WS (for more information, see Operation Manual). Static text data is saved to the DOCU- MENT_TEXTS table of DMS 600 database. The folder for document file is defined in DMS 600 WS during the first manual creation of the document and can be changed later on (for more information, see Operation Manual). The document name (for example, DistributionState) is defined using static texts. Both automatically or manually created documents will use this document name after the definition. The default types of the created documents are doc and htm (for example, DistributionState.doc and DistributionState.htm). The created Word document is also copied using the name, date and time in the format DistributionState_dd-mmyyyy_hh-mm.doc. Static texts contain area information which needs also information from the telephone answering machine database (Tam.mdb) (for more information see , Defining telephone answering machine). The fields LOCATION and TEXT in the LOCATION table and the LOCATION OF MESSAGES table are needed. An example of area information may be: "Interrupted areas: Vuohijärvi and Mäntyharju to the north from Jaala, in the area of Siikakoski and Huhdasjärvi." Using switching state document in web browser To open a switching state document (for example, DistributionState.htm) in a web browser, use a link file (for example, StateWebPage.htm). It is important to be able to assure that the original switching state document is updated. The link file enables the refreshing of the original switching state file into the web browser, for example, every 60 seconds. The link file must contain the following rows with definitions to the location of the original switching state document (an example shown below) and refreshing information: <FRAME SRC="C:\DMS600\StateDoc\DistributionState.htm"> <META HTTP-EQUIV=Refresh CONTENT="60">) Custom database table settings It is possible to define database tables to reside in different databases. However these tables must use MS Access database. This may be useful for example when defining customer data table location. Definitions are made by editing the common.prm file manually. The format is: [TablesInAccess] 99

100 tb1=customer;c:\customtablesdb.mdb Note that the identifier of custom database table must be unique (tb1, tb2, tb3 ). Use the ; character as a separator in table name and database name. The custom table definition overrides all other tables with the same name in DMS 600 databases Important network data for DMS 600 software functions The following table lists some important data for DMS 600 software functions: Table Important data for DMS 600 software functions Data Location Use of data Customer information Picture names Scada codes OPC codes Distributed generator with fixed reactive power Automatically controlled arc suppression coil Nominal voltage and short-circuit impedance of feeding primary stations Off load tap changer step of MV/LV station Type data of disconnectors, MV and LV conductors Type definition and connection data of measurements MV and LV conductor type data for line sections Equivalent temperature for MV and LV conductor types Load data CUSTOMER table or query in network database Data forms of primary substations, primary transformers, circuit breakers, feeders, disconnectors and fault detectors Data forms of primary substations, primary transformers, circuit breakers, feeders, disconnectors and fault detectors Block transformer between generator and network (the Generator block transformer check box in transformer data form) Inside HV/MV station Feeding primary station data form MV/LV station data form Data forms of disconnector type, MV and LV conductor types Measurement data form Line section data form Data form of MV and LV conductor types Data form of MV/LV station or customer Customer service function Management of switching state in DMS 600 Management of switching state in DMS 600 Network analysis Network analysis Network analysis Network analysis Network analysis Network analysis Network analysis Network analysis Network analysis 100

101 Data Medium voltage fuse type data Relay data Voltage level for network components and line sections Feeder node type State control of MV fuse Switching state data Code for network components and line sections Negative sequence and zero sequence resistance and reactance Phasor group, Uk, Pk, P0, Z0 of primary transformers Zero resistance and Zero reactance values for MV conductor type Location MV fuse type data form Data forms of relays Data forms of components and line sections Inside HV/MV station and the first node of the MV network feeder MV fuse data form (The State control enabled check box) Data forms of circuit breakers, disconnectors and MV fuses Data forms of components and line section Data form of feeding primary stations Primary transformer data form Data form of MV conductor type Use of data Protection analysis Protection analysis Topology creation Topology creation Topology creation Topology creation Topology creation Unbalanced fault analysis Unbalanced fault analysis Unbalanced fault analysis 13.. Troubleshooting network data Table Troubleshooting network data Problem object type text is not shown on the network window. Free database object is not shown on the network window. Cause 1. The text object type is not defined to be shown in the network window. Click the View > Show > Object Types command and select the text object type. 2. object type symbol definition is not properly made. Define the size and color for the code, but not for the label line and the symbol. 1. The object type is not defined to be shown in the network window. Click the View > Show > Object Types command and select the object type. 2. The symbol definition for object type is not properly made. 101

102 14. Basic principles for managing network data Notices The medium voltage network data of an area is not allowed to be updated at the same time in different workstations. Graphics-based changes to station components can only be made in the network window (not in separate station diagram windows). When inserting network data, the active voltage level must be set correctly. Activate the low voltage network by reading the existing low voltage network into the memory. Some node types have restrictions on the number of the connectable line sections. Two line sections can be connected to the switch and feeder node types. Only one same voltage level line section can be connected to MV/LV station (except Generator block transformer and three winding distribution transformers), generator and feeder point nodes. The grounding data of medium and low voltage networks can be added to the network database. The groundings can be seen on the network window, but the data is not used in the network analysis of DMS 600 WS. The type definition of the measurement node is important if the measurement is needed in the network calculations of DMS 600 WS. The measurement node must also be connected to the network component. Insert all values of the conductor type data form for the corresponding voltage. If the same conductor type is used for many voltage levels, define a separate conductor type for each voltage level. 102

103 To cancel the instant tripping, set the operating current of instant tripping to zero. The operating current of the time tripping must be smaller than the operating current of the instant tripping if both trippings are in use. The short-circuit times of the instant tripping must be shorter than short-circuit times of the time tripping. Load data is inserted to MV/LV stations if only medium voltage networks are used in DMS 600 software. If a low voltage network is used, the load data is entered to the low voltage consumer. If you are using MS Access, before using customer load data in the medium voltage network, perform the LV/MV loads from LV-networks query in the MS Access. The query calculates the loads for MV/LV substations using the customer load data. If you are using MS SQL Server, perform the corresponding procedure in the SQL Server. The temporary network components cannot be integrated to the process points of MicroSCADA. Integration needs the components to be inserted in the network database Data editing modes In the Data View Mode of DMS 600 NE, you can only browse the existing network data. Modifications to network data are made in the Data Edit Mode of DMS 600 NE. Select Edit > Edit Network Data to change between these modes. Update and insertion of temporary network data is made in Temporary Network Mode. Edit > Temporary Network changes DMS 600 NE to that mode Basic commands Select Edit > New Line to add new network data. Select both Edit > Selection of Node and Edit > Site Data to add a site node data. The "+" character is shown near the pointer. The components of existing network can be selected from the network window. A network diagram or other internal diagrams can also be used to indicate the node or line section. 103

104 When updating the existing network database data, the object type selected determines the opened dialog box. The object type can be selected using toolbox buttons, the Edit > Selection of Node (Node Selection Mode) command, or the Edit > Selection of Line Section (Line Section Selection Mode) command. The Edit > Site Data command is used, together with node selection, when site nodes are selected. The Edit > Zoom, Edit > Pan, and Edit > Cancel commands can be used to change the network view during management of the network database when the mouse is reserved for other tasks. To save the inserted or changed data, select Save or Update. These buttons are only available in Data Edit Mode. To delete the data, click Delete or Remove. To close the dialog without changing the information, click Cancel or Close. After saving, the dialog can be closed with Close without loosing the inserted data. To remove the station or site node, select the diagram and Remove in the dialog. The diagram is removed and the system asks you to confirm the removing of all components and line sections inside the station or site node. If any other parallel network view than the main view is loaded in the memory, the adding and removing of network components is disabled Fixed data forms General about fixed data forms In DMS 600 NE data for distribution network components can be entered and updated by using ready-made data forms. Data forms are views into the DMS 600 network database. The data of the primary network database components can also be displayed with free data forms. During the addition of new lines to the network, empty data forms are automatically opened when new component data is required. These data forms can be completely filled in at this time or just given some primary data (generally code and voltage level) and filled in with extra data later Opening fixed data forms There are three ways to open fixed data forms: Select File > Database and then the component type (only applies to component types: MV/LV Stations and Transformers). 104

105 Open the data form of the component associated with the open fixed data form by clicking the button in that data form (for example, Transf.Data or Disconn.Data in the MV/LV substation data form). Choose a node or line section from the network window, network diagram or station diagram, or select Node Information from the shortcut menu opened by rightclicking the node in the main network window. Then click Data Form. Node Data in the section dialog opens a data form for the end node of the chosen line section. If you choose the site node and click Data Form, the first component of the chosen site node is shown in the fixed data form. If a disconnector station has been selected, individual disconnectors can be browsed by using the arrows on the fixed data form. If you choose the station diagram and click Data Form, the station data form is opened. The menu commands show the data forms sorted by their component codes. Use buttons in data forms and point a network to show the fixed data form of an appropriate node/line section Browsing fixed data forms Browsing methods depend on the data form type. The following methods are used: Arrow buttons at the bottom of the form Table Arrow buttons at the bottom of the form Button Function Shows the first form according to the code of the component. Shows the previous form according to the code of the component Shows the next form according to the code of the component. Shows the last form according to the code of the component. Transformer data forms have a code box which contains a list of all the codes in the database. The transformer can be chosen from this list. MV/LV substation data forms have a search function with a text box and the Search button. To browse between disconnectors/transformers inside the station, you can use browsing arrows in the disconnector station and MV/LV substation data forms. The same buttons are used in the measurement data form (For more information about measurements, see , General about measurements). 105

106 Content of fixed data forms Fixed data forms consist of boxes and buttons, which are used to insert and update component data. The administrator of the system can define the contents of the lists by code info (For more information about code info, see , Defining code info). The upper right corner of the fixed data forms contains two important buttons. Close closes the data form. The changes, which have been made, are not updated to the database. Save saves the additional and changed data in the database. This button is only available in Data Edit Mode. After saving, the fixed data form can be closed with Close without losing the inserted data. Saving the contents of the fixed data form to default data can be used in addition of new components Free data forms General about free data forms Free data forms provide a view to DMS 600 database contents. These can be used, for example, to browse network data and locate objects. Several free data forms can be opened simultaneously. In DMS 600 NE, free data forms display the object data of the free database and data of the documents (For more information, see 17.16, Inserting free database object). Also the data of the primary network database components can be displayed with free data forms. Free data forms can be used to define the layout of the free data forms. DMS 600 WS does not use the fixed data forms but uses free data forms for the browsing of components and object data Changing labels or language The free data form reads the table or query contents and shows all the data fields. By default the label for each control is the field's name. If you want to alter the data field label text shown in the free data form, enter the original field name in the CODE field in the language-specific table Genlang.mdb and enter the text to be shown in the GENTXT field. If you want to restrict the label text usage to one table only, use the form [TABLE NAME].[FIELD NAME] in the TEXTKEY field. Otherwise, the data field with that name in all tables or queries will be labeled according to the definition. More information about localization and Genlang.mdb can be found in Appendix, Localization of DMS

107 Defining drop-down lists Instead of edit controls, free data forms can present in drop-down lists for defined data fields. By using drop-down lists you have ready-made alternatives to update data and to avoid misspellings that cause harm in database reporting, etc. For more information about defining drop-down lists, see , Defining code info Opening free data forms There are three ways to open free data forms: Select File > Database > Objects and then select the object type. Choose the node or line section from the network window, network diagram or station diagram or select Node Information from the shortcut menu opened by right-clicking the node in the main network window. Then check the Use free data form check box and click Data Form. If you choose the site node, check the Use free data form check box and click Data Form. The first component of the chosen site node is shown in the free data form. If you choose the station diagram and click Data Form, the station data form is opened. Select Data Form from the shortcut menu opened by right-clicking over the node or line section in the main network window. The command opens a free data form of the node or the end node of the chosen line section. The menu commands show the free data forms sorted by their component codes. Point a node or line section of network to show the free data form of the appropriate node/line section Browsing free data forms This chapter does not apply to the DMS 600 (Base) license. The Extended Data Management license is required for free data forms. The arrow buttons in the bottom of the free data form are used to change the record: Table Arrow buttons in the bottom of the free data form Button: Function: Moves to the first record. Moves to the previous record. Moves to the next record. Moves to the last record. 107

108 If a free data form is operated in Data Edit Mode, user rights for the selected node are checked every time the user changes record Content of free data forms This chapter does not apply to the DMS 600 (Base) license. The Extended Data Management license is required for free data forms. Free data forms consist of boxes and buttons which are used to insert and update network component data. The administrator of the system can define the contents of the forms by code info (For more information about code info, see , Defining code info). The bottom of the free data forms contains two important buttons. Close closes the active free data form. The changes that have been made are not updated to the database. Update saves the additional and changed data in the database. This button is only available in the Data Edit Mode. During mass updating the data is saved to the database immediately without using Update (For more information about mass updating, see 16.5, Mass update of component/object data and 16.6, Mass update of line section data). After saving, the data form can be closed with Close without losing the inserted data. Help opens the help for the active window. The user can revise the free data form using the layout functions. Settings is used to define the fields that are displayed and the order of fields. The free data form changes according to the new definitions immediately after the dialog box is closed. The location of the table can be changed with the mouse. The location and layout of the free data form are saved for each network component or object type when closing the free data form Editing free data forms Some boxes of free data forms cannot be changed (for example, Node code and Scada- Code in disconnector free data form). Fields having another free data form attached are presented using red bolded font (for example, the disconnector type field). Define the value of that field using the attached form. You can open the attached form by double-clicking the field. Select the value and close the form with Close. 10

109 14.6. Selecting node, line section, site node or diagram Use the node, line section, site node or diagram dialog to browse and update the data: 1. Select the object type using the Edit > Selection of Node or Edit > Selection of Line Section commands or Edit > Selection of Node and Edit > Site Data commands together. 2. Select the component by clicking the selected object type in the main network window, network diagram or internal station diagram. Diagrams can be selected by clicking a corner of the diagram, when the diagram is colored black. 3. If needed, select the node from a list of all nodes near the chosen point. The Node dialog can also be opened by selecting Node Information from the shortcut menu opened by right-clicking the node in the main network window. The dialog box contains some basic information and buttons for browsing and editing node/line section/site node/diagram data. The Node dialog box always contains the node type and the node code. The Line section dialog box always contains data on the start and end node codes, conductor type, and the length of the line sections (calculated length in parenthesis if it differs from the entered length). Definition of the content for dialog box data is made during projecting Graphical selection of nodes Nodes with the same component/object type can be selected graphically. Selection can then be used to focus the query or in a mass update. To perform the selection: 1. Define the components/objects graphically by selecting View > Database Queries > Select Nodes in Network Window and select the area with the mouse from the network window. 2. Define the component/object type. 3. Click Delete to remove the desired nodes from the selection. 4. Click Browse to open the free data form containing the selected components/objects Multiselection of line sections Multiple line sections can be selected graphically. The selection can then be used to focus a query or a mass update (for example, the update of conductor data) or to move, delete or copy a larger part of the network. To perform the selection: 1. To select one line section, hold down the Control key when selecting the line section. 2. To select many line sections, hold down the Shift key and select upstream or downstream line section. All line sections between the first and selected line sections will be selected. 109

110 3. To select line sections inside the area, hold down the Control key when selecting the area with the mouse. 4. To remove the line section, hold down the Control key and reselect the line section. Select line sections only from one voltage level. The first line section defines the acceptable voltage level. 110

111 15. DXF import General about DXF import The DXF import tool is used for reading DXF/DWG files containing the network data exported from third-party GIS systems, and writing the data into the DMS 600 database. Follow the instructions and proceed with the DXF import in the given order DXF import tools In the DMS 600 NE, you can use the following toolbox for DXF import functions: Figure DXF import toolbox You can select the tools also from Window > DXF Import Toolbox. DXF_toolbox.png Table Description of DXF import tool icons Tool icon Description Launch DMS 600 DXF Import Tool Manage DXF/DWG Import Data... Save DXF/DWG Import Data into DMS 600 Database Stop DXF/DWG import DXF import Edit Mode - Draw Only DXF Picture DXF Import - Lines DXF Import - Symbol Blocks (Nodes) DXF Import - s DXF Import - Connectivity Node Management DXF Import - Settings Launching DXF Import Tool To launch the DXF Import Tool: 111

112 1. In the DMS 600 NE, select File > DXF/DWG Network Data Import > Launch DMS 600 DXF Import Tool. 2. Select the DXF/DWG file to be imported from the dialog. 3. Open the selected file into DMS 600 DXF Import Tool by clicking Open Exporting network data to DMS 600 database Save the DXF/DWG picture containing nework data to the DMS 600 database by selecting File > Export to DMS 600 Database. The system saves the DXF picture into the DXF tables of the DMS 600 database. The content of the DXF import tables in the DMS 600 database is described in the following table. Table DXF import tables in the DMS 600 database DXF import table DXF_IMPORTFILES DXF_LAYERS DXF_SYMBOL_BLOCKS DXF_SECTION DXF_SECTIONPOINT DXF_NODE DXF_TEXT DXF_OBJECTS Content of the DXF import table DXF/DWG File ID, filename and export time DXF Layer definitions DXF Symbol Block definitions DXF Polyline objects The section points of the DXF Polyline objects DXF Symbol Block objects, i.e. the Component Nodes DXF objects DXF picture structure in a nutshell (informative table) Managing and viewing DXF/DWG import data To manage the DXF/DWG import data: 1. In the DMS 600 NE, select File > DXF/DWG Network Data Import > Manage DXF/DWG Import Data... The DXF/DWG Network Data Import dialog opens. 112

113 DXF_DWG_data_import.png Figure DXF/DWG Network Data Import dialog You can remove individual or all DXF/DWG files from the DMS 600 database with the Remove and Remove All buttons. 2. To view the file in the DMS 600 NE, select the file imported to the DMS 600 database and click Read. You can see the DXF Import Toolbox on the right. For more information on the tools, see 15.2, DXF import tools. Figure DXF/DWG Network Data view in the DMS 600 NE The undefined DXF blocks are shown as white dots. DXF_NE_view.png DXF import settings Defining symbol block settings To specify the details for each symbol block to be imported to the DMS 600 database: 1. In the DMS 600 NE, select Settings from the toolbar. The DXF Import - Settings dialog opens. 113

114 DXF_settings_tab1.png Figure DXF Symbol Blocks settings tab of the DXF Import -Settings dialog 2. On the DXF Symbol Blocks tab, give a name for the block. Undefined block names are not imported. 3. Select the node type from the Node Type list. 4. Define the text layer for the node type. The system cannot find the node codes for the components unless you define the text layers. 5. Specify the maximum number of line sections in the Max Line Sections field. The default is 1. For disconnectors, fuses and circuit brakers the default is 2, and for branch nodes Specify the subtype in the Disc/Trafo Type (special symbol) field if the node type is either Disconnector or MV/LV substation. Fill in SubSymbolDiscTypes for the node type Disconnector, and SubSymboTrafo for MV/LV substation. With the Save as Default you can save the common defaults into the DMS 600 database. By selecting Load Defaults you can load the common defaults for the settings on the DXF Symbol Blocks tab. The Apply and OK buttons save all definitions on all tabs. The network window is redrawn based on the new settings. 114

115 Defining DXF layer settings To define the DXF layers (for example, nodes, texts or line sections) you want to import from the DXF/DWG file: 1. In the DMS 600 NE, select Settings from the toolbar. The DXF Import - Settings dialog opens. 2. Select the DXF Layers tab. Figure DXF Layers settings tab DXF_settings_tab2.png 3. Turn a DXF layer on or off. Only the DXF layers that are on, are displayed in the list, and imported. You can turn all layers on or off with the All Layers: ON and All Layers: OFF buttons. 4. Select the voltage level for the layer. 5. Select the conductor type. If you want to select an LV conductor type, the voltage level in the Voltage level (kv) list must be 0.4 kv. Otherwise, only MV conductor types are available in the list. With the Save as Default button you can save the common defaults into the DMS 600 database. By selecting Load Defaults you can load the common defaults for the settings on the DXF Symbol Blocks tab. 115

116 The Apply and OK buttons save all definitions on all tabs. The network window is redrawn based on the new settings Defining DXF co-ordinate conversion settings To define the X and Y co-ordinate settings: 1. In the DMS 600 NE, select Settings from the toolbar. The DXF Import - Settings dialog opens. 2. Select the DXF Co-ordinate Conversion tab. DXF_settings_tab3.png Figure DXF Co-ordinate Conversion settings tab of the DXF Import -Settings dialog 3. Define the X/Y Scale Factors for converting the original DXF co-ordinate units into meters. 4. Define the X/Y Add in DXF Import (M) parameters for defining the correct false easting/false northing values to match with the X/Y co-ordinates used in DMS Specify the maximum difference between the current DMS 600 network data coordinates and the new DXF/DWG network data package co-ordinates in meters in the Tolerance for Incremental DXF Import (M) field. The default value is 0. The system imports only new nodes and line sections. Therefore, the system does not import in the DXF/DWG network data package nodes and line sections, whose X and Y co-ordinates match with the existing network data co-ordinates, and that are within the defined tolerance. 116

117 With the Save as Default button you can save the common defaults into the DMS 600 database. By selecting Load Defaults you can load the common defaults for the settings on the DXF Symbol Blocks tab. The Apply and OK buttons save all definitions on all tabs. The network window is redrawn based on the new settings Defining node connectivity To view node connections and import data to the NE window: 1. In the DMS 600 NE window, select Connectivity Node Management from the File menu or from the toolbar. The following dialog opens. Figure Connectivity Management dialog connectivity_by_sections.png You can view the connection by line sections (Connectivity By Sections tab), or by nodes (Connectivity By Nodes tab). The Counter number of each component node is the total number of nodes that match exactly the co-ordinates of the same connectivity node. The Counter number of line section objects connected to a connectivity node is always 0. If there are more than one component nodes whose coordinates match exactly the connectivity node's co- 117

118 ordinates, the status in the Connected status list shows No. Nevertheless, the system imports such component nodes to the database. 2. View/import data by selecting one of the following options: Import All Data imports all nodes and sections that do not exist in the current DMS 600 network model. If some previously imported nodes or line sections are deleted or moved in the current DMS 600 network model, they will be reimported. Import New Data Only imports all nodes and sections that do not exist in the current DMS 600 network model. But if some imported nodes or line sections have been deleted or moved since the previous DXF import function, they will be ignored during the next DXF import. If you want to import the whole DXF/DWG picture in spite of the existing nodes and line sections, delete them manually from the DMS 600 database. If you do not want to import an already imported node or a line section again, answer No to the question appearing in the DMS 600 NE window Do you want the deleted node(s) and line section(s) to be created again during the next DXF import operation. 3. To view the DXF object in the DMS 600 NE window, click Locate. 4. To view details of the DXF object in the DMS 600 NE, and in the Connectivity Management dialog, select Draw Only DXF Picture from the toolbar, and then select Lines, Symbol Blocks, or s. You can do this also by right-clicking the DXF object in the NE window, and by selecting Show on list. Lines displays the start and end terminals of the line sections. Symbol Blocks displays the component nodes to be imported to the DMS 600 database. s displays all text objects, when the Symbol Size Class is 1 (check it from Settings > General... > Symbol Limits tab). 5. Complete the connectivity definitions by clicking Accept Connectivity Saving DXF/DWG import data into DMS 600 database To save DXF/DWG import data into the DMS 600 database: 1. Click the Save DXF/DWG Import Data into DMS 600 Database button from the toolbar. 11

119 If an error occurs during the procedure, the corrupted file will be rolled back from the DMS 600 database. If the import data is saved successfully, the following dialog appears. Figure Binary file update dialog 2. Update the binary network data by clicking OK. The DXF import is now complete. update_binary_file.png 119

120 16. General network management tasks Inserting medium and low voltage network lines and components To add the network line one line section at a time: 1. Insert the line section start node. a. Click the starting point of the line section with the left mouse button in the network window, network diagram or station diagram. If the starting point is located near existing nodes, a list of those nodes is shown. b. Select the start node type or choose the start node from the list containing the existing nodes. Click Cancel while viewing that list to create a new node. The start node type of the feeder must be Feeder. 2. Indicate the route of the line section. Indicate the route of the line section by clicking all points of the line section. 3. Insert the line section end node. a. Right-click the ending point of the line section in the network window, network diagram or station diagram. If the ending point is located near existing nodes, a list of those nodes is shown. b. Select the end node type or choose the end node from the list containing the existing nodes. To create a new end node, click Cancel while viewing the list. 4. Insert the line section data forms a. Insert line section data to the data form. DMS 600 NE automatically fills in the length of the line section, presumed conductor type, and voltage level. The voltage level depends on the voltage level of the connected network. The presumed conductor type is the type of the last connected line section. The conductor type data is needed for network and protection analysis. For more information about component and conductor type data, see , Inserting MV and LV conductor type data. 5. Insert the component data forms a. Insert component data of the start node and end node to the data forms. Some node types have restrictions on the number of the connectable line sections. Two line sections can be connected to switch and feeder node types. Only one line section with the same voltage can be connected to a MV/LV station (except Generator block transformer and three winding distribution transformers), a generator and feeder point nodes Defining site node A site node contains medium or low voltage network objects located near each other. For example, a disconnector station or LV box can be depicted with a site node. 120

121 To add site node data: 1. Insert site node components as described in 16.1, Inserting medium and low voltage network lines and components. 2. Define the site node selection by selecting both the Edit > Selection of Node command and the Edit > Site Data command. 3. Select one object from the site node. 4. To define the objects of the site node to be connected or disconnected, click Connect or Disconnect. After clicking either button, indicate the node from the network window with the mouse Creating site node diagram The medium and low voltage network site node diagrams show connections of site nodes. A diagram can be created if the selected site node has transformers or disconnectors. When inserting the MV/LV substation select new node type MV/LV substation to create the diagram automatically (for more information, see 17.5, Inserting MV/LV station). Select new node type MV/LV transformer if there is no need to create diagram (for more information, see 17.6, Inserting MV/LV transformer). To add the site node diagram data: 1. Define the site node selection. 2. Select one object from the site node by selecting both the Edit > Selection of Node command and the Edit > Site Data command. 3. Click Diagram in the site node dialog to create the diagram automatically. See 16..1, Changing node type for a more detailed description of how to handle the diagram and its components Defining states of switches After DMS 600 NE starts up, a medium voltage network topology is displayed on the screen according to the states of the switches in the binary network file (Network.dat). Load the appropriate low voltage networks into the memory to see the switching state of the low voltage network. The switching state data in the network database can be changed via switching device data forms in DMS 600 NE. The change in switching state updates automatically the network topology on screen. The File > Update Network Database command saves new switching state data of the medium voltage network to the binary network file (Network.dat) and for the use for instances of DMS 600 software. The binary network file is saved only to the local workstation, if the updating for all is prohibited. If there is need to change the normal switching state of the low voltage network dealing with more than one LV network, save the changes to the network database with the special command Edit > Save LV Topology. The command updates the LV network 121

122 specific data, saves the normal state of the LV switches and every LV network is correctly loaded to the memory next time. If DMS 600 has been integrated with the scada system. DMS 600 SA maintains the real time switching status data in the DMS 600 database on the fileserver. Selecting View > Current Switching State updates the network topology on the DMS 600 NE screen in accordance with the data in the DMS 600 database. This command changes the network topology on the screen, but not the states of the switches in the network database. Selecting View > Switching state in database restores the network topology according to the states of the switching state in the network database. DMS 600 SA saves the switching state file automatically in the beginning of the each week. The switching state file is named Switching_State_yyyy_ww.stf, where yyyy is year and ww is week and saved to folder \Data\SState. At the same time a new weekly *.log file of DMS 600 WS is saved Mass update of component/object data With a mass update you can insert and update data for all component/object type records or for graphically selected targets of the same component/object type. To perform a mass update for object types: 1. If the mass update is focused to selected target objects, perform the graphical selection of a node as described in 14.7, Graphical selection of nodes and click Browse to open a free data form. 2. The mass update is started using the Update All command of the free data form. If the update is focused on all records of the object type, open the free data form of the object type and select Update All. 3. Confirm the mass update Mass update of line section data You can use a mass update to update graphically selected line section data (for example, conductor data). To perform a mass update for line sections: 1. Perform the multi-selection of line sections according to 14., Multiselection of line sections. 2. Open a free data form by clicking Data Form. 3. Select Update All from the shortcut menu. 4. Confirm the mass update. 122

123 16.7. Defining node labels and symbols Location and color settings of codes and labels The location of codes and labels can be defined with the function in the node, line section and station and site node dialog box (for more information about node and line section dialog, see 16..1, Changing node type). The system-specific color settings of the codes and labels are defined during the symbol definition (For more information, see , Defining symbols) or by selecting Settings > General (For more information, see , MV/LV station, switch and customer code color settings) Moving node label To move the node or line section code/name or base node code/name of a site node: 1. Make codes or names visible using the View > Show menu. 2. Select the node, line section or station/site node. 3. Click Move Code in the node, line section or site node diagram. 4. Click once with the left mouse button in the network window. 5. Click the left mouse button again to move the node code or name to a new location. 6. Confirm the moving after closing the node, line section or station/site node diagram Rotating conductor code To rotate a line section conductor code: 1. Make conductor codes visible by selecting View > Show > Conductor Codes. 2. Select the line section. 3. Click Rotate Code in the line section diagram. 4. Click once with the left mouse button in the network window. 5. Click the left mouse button again to rotate the conductor code to a new angle. 6. Confirm the rotation after closing the line section diagram Editing label of free database object The label of a free database object is used especially for text object types (For more information about labels with the symbols, see 20.1, General about symbols): To edit the label of a free database object: 1. Make free database object types visible by selecting View > Show > Object Types. 2. Select the node. 3. Click Edit Label in the node dialog. 4. Insert a new label to the dialog. 123

124 Rotating node symbol To rotate a node symbol: 1. Select the node. 2. Click Rotate in the node dialog. 3. Accept or decline the suggested automatic rotation. Automatic rotation calculates the mean of the angles of the two line sections connected to the node and sets the symbol angle accordingly. 4. If you decline the automatic rotation, give the rotation angle manually by pointing it with the mouse. A line is shown between the node and the pointer to indicate the angle. 5. Confirm the rotation after closing the line section diagram Defining nodes, line sections or station/site nodes Changing node type To change the node type of an existing node: 1. Select the node. 2. Click Change in the node dialog. 3. Select the new node type using the dialog Resizing the diagram To resize a diagram: 1. Select the diagram. 2. Click Move in the diagram dialog. 3. Click the corner point of the diagram to be moved. 4. Click the left mouse button again to move the corner into a new location. 5. Confirm the resizing after closing the diagram dialog Moving node or site node To move a node or site node diagram (with all nodes in this site node and the diagram): 1. Select the node or station/site node. 2. Click Move in the node or site node dialog. 3. If moving a node, click once with the left mouse button in the network window. 4. If moving a site node, click the site node once with the left mouse button. 5. Click the left mouse button again to move the node or site node to a new location. 6. Confirm the moving after closing the node dialog. 124

125 Removing node To remove a node: 1. Select the node. 2. Click Change in the node dialog. 3. Select Delete in the dialog Removing line section To remove a line section: 1. Select the line section. 2. Click Delete in the line section dialog. 3. Confirm the removal right away. 4. Accept or decline the moving of line section data to line section history. 5. Give date for the moving Removing free database object or site node To remove a free database object and site node diagram: 1. Select the free database object or site node diagram. 2. Click Remove in the node or diagram dialog. 3. Confirm the removing right away. 4. If you are removing a site node diagram, accept or decline the removing of all components of the site node Inserting new node or new point to existing line section To insert a new node or point to an existing line section: 1. Select the line section. 2. Click New Node or New Point in the line section dialog. 3. Click the location for the new node or new point. 4. For the new node, select the node type. 5. For the new node, insert the data form Moving point in existing line section To move a point in an existing line section: 1. Select the line section. 2. Click Move Point in the line section dialog. 3. Select the point to be moved. 4. Click a new location for the point. 125

126 Removing point in existing line section To remove a point in an existing line section: 1. Select the line section. 2. Click Remove Point in the line section dialog. 3. Select the point you want to remove. To remove several points in a pointing area: 1. Select the pointing area. 2. Click Remove point in the dialog. To remove all points in several line sections at the same time: 1. Select the line sections, (see 14., Multiselection of line sections). 2. Click Remove point in the multiselection dialog Changing line section end node To change an end node in an existing line section: 1. Select the line section. 2. Click Move Point in the line section dialog. 3. Select the end point of the line section. 4. Click the new location for the end point. If there is an existing node in the new location, it will be used. If there is no existing node, select the node type and insert the data form Hiding line sections, nodes, free database objects and diagrams To hide a line section, node, free database object or diagram: 1. Select the line section, node, free database object or diagram you want to hide. 2. Click Hide in the line section, node, free database or diagram dialog. To unhide a line section, node, free database object or diagram: 1. Select the line section, node, free database object or diagram you want to hide. 2. Click Unhide in the line section, node, free database or diagram dialog. To hide several line sections at the same time: 1. Select the line sections you want to hide (see 14., Multiselection of line sections): 2. Click Hide in the multiselection dialog. To unhide several line sections at the same time: 1. Select the line sections you want to unhide (see 14., Multiselection of line sections). 2. Click Unhide in the multiselection dialog. To enable drawing of hidden objects: 1. Select Edit > Show. 2. Disable drawing of the hidden objects by reselecting Edit > Show hidden objects. 126

127 16.9. GPS waypoints Using GPS waypoints during editing To insert GPS device data into the network database: 1. Select Edit > GPS data to start the GPS interface. The GPS NMEA Data dialog opens. 2. Click Get Waypoints to retrieve all waypoint data stored in the GPS devices' memory. Retrieved waypoints are displayed in the waypoint list. Click Save Waypoints to save the waypoint list for future use. File extension is always wpf. To load saved waypoint from the file, click Load Waypoints. Lists can be combined by loading various waypoint files. 3. To draw one waypoint, select the waypoint from the waypoint list, right-click the list and select Draw waypoint from the shortcut menu. To draw all waypoints on the list, right-click and select Draw all waypoints from the shortcut menu. Waypoints are drawn with a static waypoint symbol in the main network window. Waypoint data is presented in a tool tip window when the mouse pointer is moved on top of the waypoint symbol in the main network window. 4. Right-click and select Delete all drawn waypoints. To show the selected waypoint in the main network window, click Locate Waypoint. A predefined zoom is used to center the located waypoint in the window. To clear all waypoint symbols shown in the main network window, click Clear Nodes. To remove one waypoint, select the waypoint, right-click and select Delete waypoint from list. To remove all waypoints, right-click and select Delete all waypoints. To print a waypoint list, right-click and select Print Continuous locating of GPS device The continuous locating function shows the real time location of a GPS device connected to, for example, a laptop computer, carried by a field crew. The continuous locating of GPS device supports both WGS4 and national map datum. DMS 600 NE and the GPS device must be set to use the same WGS4 and national map datum in order to make the continuous locating work properly. The coordinate transformation method Transverse Mercator must be used to transform the coordinates bidirectionally between WGS4 and national orthogonal coordinate system required by DMS 600. The user can define the Transverse Mercator parameters, in order to define the correct map datum for national orthogonal coordinate systems (for more information about map datum settings, see , Map datum parameters). 127

128 Pole data General about pole data This chapter does not apply to the DMS 600 (Base) license. The Network Planning (NIP) license and the sublicense Poles Management are required for pole management using Network Editor program. Pole data contains information about the medium and low voltage distribution network poles and their location. You can use the database, for example, to manage the condition data of the poles. You can do queries to the pole database NE, or using MS Access (for more information about database queries, see 26.1, General about database analysis) Inserting and editing pole locations You can insert pole locations to the database at the same time as, or after, inserting other network data. For information on inserting lines and components, see 16.1, Inserting medium and low voltage network lines and components Inserting pole locations with other network data To insert and edit the pole locations with other network data: 1. Select the Add poles to end and deviation points box in the Line section dialog. The system then inserts the pole location automatically to all deviation points and end points. 2. Insert the line route by clicking all deviation points of the line section. 3. Press the key 1 on the keyboard. Inserting pole locations after inserting other network data To insert and edit the pole location after inserting other network data: 1. Select the Add poles to end and deviation points box in the Line section dialog. The system then inserts the pole location automatically to all deviation points and end points. 2. Select Edit > Pole information. 3. Click the new pole location in the network window. 12

129 The system adds the pole location to the database. The pole location is shown in gray in the network window. The fields for entering the pole data are opened in the dialog. For more information about inserting pole data, see , Inserting and editing pole data. 4. Click the lower Add button. Right-click the line and insert the number of pole locations to the dialog. The number of the pole locations must equal the number of inserted lines Moving pole locations To move the pole location: 1. Select Edit > Pole information, or click. 2. Select the existing pole location. The selected pole location is shown in gray in the network window. 3. Press Move. 4. Click the new pole location in the network window Inserting and editing pole data To insert or edit the pole data of the pole location: 1. Select Edit > Pole information, or click. 2. Select the existing pole location in the network window. The selected pole location is shown in gray in the network window. The pole data of the first pole in the selected pole location is opened in a dialog. 3. Add a new pole by clicking the upper Add button. Information on the number of poles in the pole location and the pages of the pole information is shown on the left. You can browse the information using the following buttons: Button Function Browses backwards the pole data of the selected pole location. Browses forward the pole data of the selected pole location. 4. Change the pole information if necessary. 5. Click Save Removing the pole To remove an existing pole: 129

130 1. Select Edit > Pole information, or click. 2. Select the existing pole location in the network window. The selected pole location is shown in grey. 3. Select the pole data by browsing with the arrow buttons. 4. Click Delete Inserting and editing the condition data of the pole To insert and edit the condition data of the pole locations: 1. Select Edit > Pole information, or click. 2. Select the existing pole location in the network window. The selected pole location is shown in gray. 3. Select the pole data by browsing with the arrow buttons. 4. Click Condition data. The button changes into Pole data. You can return to the pole data view by clicking it. Information on the number of pages of the pole condition data is shown on the left. You can browse the information using the following buttons. Button Function Browses backwards the condition data of the selected pole location. Browses forward the condition data of the selected pole location. 5. Edit the condition data if necessary. 6. Click Save Carrying out the pole and condition data mass update The mass update enables inserting and updating data for graphically selected targets of the poles. To carry out the mass update for poles: 1. Select Edit > Pole information, or click. 2. Select the pole locations by zooming with the mouse. 3. Drag from one corner and release in the opposite corner. The selected pole locations are shown as red points in the network window. The number of the pole locations is shown in the dialog. Repeat the selection to add more pole locations. You can remove the pole locations by clicking Remove, and by selecting the pole locations in the network window. To remove all selected pole locations, click Delete all. 130

131 To add more pole locations, click Add. The button changes between Add/Remove/Select off. 4. Click Select off. 5. Click Condition Data/Pole Data depending on which data you are inserting or updating. 6. Browse to the pole or condition data that will be the base data of the mass update, or click Initialize to clear the fields in the pole or condition data. 7. Insert or update the pole or condition data.. Click Save. Only the data of the filled fields is updated in the database. 131

132 17. Separate network management tasks Managing parallel network views To create a new view: 1. Select Edit > New network view. 2. Type a name for the view. If a view with this name already exists, you will be asked whether you want to replace or update the view. 3. Select an existing view on which the new view is based. 4. Select Background maps if background maps are used in the new view. Note that this background maps will be visible only after the new view has been loaded in to the memory. 5. Click OK to generate and initialize database tables for the new view. To load an existing view in to the memory: 1. Select Edit > Load network view. 2. Select the view you want to load. To remove an existing view: 1. Select Edit > Remove network view. 2. Select the view to be removed. 3. After confirmation all database tables and files associated to view will be deleted. To update the binary network file of an existing view: 1. Select Edit > Load network view. 2. Select the view to be updated. 3. Select File > Update network database. Any changes made to network data (added and removed nodes, sections, busbars and diagrams) are normally made also to all parallel views, but if you import network data form outside sources, you need to update the view manually. To update network data of an existing view manually: 1. Select Edit > Update network view. 2. Select the view to be updated. 3. Select an existing view (normally the Main View) on which the view is based. Any changes made to network data in the base view will be made to the selected view. Also the binary network file of the selected view will be updated Inserting HV/MV station To add new HV/MV station data: 1. Create the diagram for the new HV/MV station. a. Use the scale indicator in the lower left corner of the main network window to zoom in close enough for a detailed view before entering the new station (the 132

133 station area width preferably less than 100 meters, definitely less than 500 meters). b. Click one corner of the diagram. c. Choose the node type Primary substation. d. Click the opposite corner of the diagram. 2. Insert station data to the primary station data form. For more information about primary station data, see 17.3, Inserting primary station data. 3. Add station busbars to the diagram. a. Click the starting point of the busbar in the substation diagram window of the network window (not in a separate substation diagram window). b. Select the start node type Busbar. c. Indicate the route of the busbar by clicking all the points of the busbar. d. Indicate the ending point of the busbar by right-clicking. e. The end node type is not asked at all when the start node type is a busbar. 4. Insert the primary transformer. a. Select the node type Primary transformer. b. Insert data to the primary transformer data forms. For more information about primary transformer data, see 17.4, Inserting primary transformer data. 5. Add the other station components and feeding line sections. a. Click the starting point of the line section in the station diagram. b. Select the start node type. c. Indicate the route of the line section by clicking on all the points of the line section. d. Indicate the ending point of the line section by right-clicking. e. Select the end node type. Select Feeder for the end node of the feeding line section. f. Insert data to the component data forms. 6. Add the feeders one at a time. a. Click the starting point of the feeder in the station diagram. The start node type must be Feeder. For more information about inserting new a network line section, see 16.1, Inserting medium and low voltage network lines and components. 7. Insert measurement transformer and relay data a. Open the circuit breaker data form. b. Click New Relay. c. Insert the measurement transformer and relay data. For more information about the measurement transformer and relay data, see 17.13, Inserting measurement transformer data and , Inserting relay data. See 16..1, Changing node type for a more detailed description of how to handle this diagram and its components Inserting primary station data To open the primary station data form of an existing station, click Data Form in the internal station diagram. 133

134 The primary station data form contains the code and name of the primary station. The scada code and picture names are used when integrating DMS 600 and MicroSCADA (for more information about DMS 600/MicroSCADA integration, see 1.6.1, Process objects and 1..1, General about picture names). Technical data of the feeding primary stations is needed for the network and protection analysis of DMS 600 WS. The primary substations, in which one nominal voltage is above transmission voltage level (for more information about defining the transmission voltage level, see Installation Manual), are functioning as feeding points. The technical data fields can be left empty for other stations. The nominal voltage is the voltage level at which the short-circuit impedance is given. In any case, DMS 600 NE calculates the resulting impedance for the medium voltage side. You can give the feeding short-circuit impedance either as 3-phase short-circuit current or as short-circuit resistance and reactance (both are not required). If you give the reactance in ohms, this is always used. For more information about using nominal voltage in network analysis, see , Defining voltage measurement and , Defining general network analysis settings. Negative sequence and zero sequence resistance and reactance values are used for unbalanced fault analysis of DMS 600 WS. Default values for negative sequence values are the same as short-circuit values and for zero sequence values 0 ohm Inserting primary transformer data The primary transformer data form of the existing primary transformer can be opened as described in , Opening fixed data forms. Scadacode is used when integrating DMS 600 and MicroSCADA (for more information about DMS 600/MicroSCADA integration, see 1.6.1, Process objects). The technical data of the primary transformers needed for the unbalanced fault analysis of DMS 600 WS is presented in the following. To insert the primary transformer data: 1. Select coupling of the windings from the list. See Table Table Phasor groups Connections of windings Representation per phase Comments Primary Secondary 134

135 Connections of windings Representation per phase Comments YN Y D D D Y Yn Yn Yn Y D yn (d) Zero sequence currents free to flow in both primary and secondary circuits No path for zero sequence currents in primary circuits 1-phase currents can circulate in the delta but not outside it No flow of zero sequence currents possible No flow of zero sequence currents possible Tertiary winding provides path for zero sequence currents Table Electric data Input value Symbol Unit Description Rated apparent power in terminals S n1, S n2, S n3 MVA Rated apparent power of transformer terminal. For two winding terminals, only one value is needed (same for both terminals). Rated voltage of terminals U n1, U n2, U n3 kv Rated voltage of the transformer terminal. Needed for each terminal. Relative short circuit voltage between terminals U k12, U k13, U k23 % Relative short circuit impedance between two terminals. Note that the relative value is based on the rated apparent power between terminals. Load loss between terminals P k12, P k13, P k23 kw Real power loss between windings when rated apparent power is flowing between terminals. No-load losses P0 kw No-load losses/iron losses. Relative short circuit impedance between windings in zero sequence network Z0 12, Z0 13, Z0 23 % Used instead of U k values when calculating zero sequence network. 135

136 1. Give the Clock (Phasor group) Code (0-11) for the secondary voltage level. When there are three winding Primary Transformers, give the Clock Code also for the tertiary voltage level. The Clock Code for the Primary voltage level is always 0 (zero). 2. Give the grounding data in the bottom of the data form only with small or zero grounding resistances and reactances. Primary winding resistance and reactance values should be used only with separately earthed zero points. 3. Define the Fixed Colors (the Primary Transformer Pen s color and width) for the secondary voltage level, and when there are three winding Primary Transformers also for the tertiary voltage level. The fixed pen color/width for the primary voltage level is reserved for future use Inserting MV/LV station To add a MV/LV station (for general information about inserting the lines and components, see 16..7, Inserting new node or new point to existing line section): 1. Select the node type MV/LV substation. 2. Insert feeding line disconnector data to the data form. 3. Give the number of line disconnectors in the separate dialog box. 4. Give the MV/LV station code in the separate dialog box. 5. Insert other line disconnector data to the data forms. 6. Insert data to the MV/LV substation data form. Off load tap changer step in the MV/LV station data form affects to network analysis by increasing the reduction factor of the transformer. Negative values can also be used. 7. Select an existing transformer from the list or add a new MV/LV transformer by clicking Add.. Define the date of the transfer. 9. Insert the MV/LV transformer data to the data form. See 16..1, Changing node type for a more detailed description of how to handle this diagram and its components Inserting MV/LV transformer The MV/LV transformer data form of an existing MV/LV transformer can be opened as described in , Opening fixed data forms. An MV/LV transformer can also be added together with a MV/LV station. For more information about MV/LV stations, see 17.5, Inserting MV/LV station. For general information about inserting the lines and components, see 16.1, Inserting medium and low voltage network lines and components. For general information about MV/LV transformer data, see 17.4, Inserting primary transformer data. 136

137 To add the MV/LV transformer data: 1. Select the node type MV/LV transformer. 2. Insert feeding line disconnector data to the data form. 3. Select an existing transformer from the list or add the new MV/LV transformer by clicking Add. 4. Define the date of the transfer. 5. Insert the MV/LV transformer data to the data form. Off load tap changer data in the transformer data form is informative and, unlike the off load tap changer step data in the MV/LV station data form, does not affect the network analysis. With the importance field you can classify and find easily the MV/LV transformers in the order of their importance (for more information about showing the important transformers, see 22.9, Showing important transformers ). An existing MV/LV transformer can be removed or transferred to other MV/LV substations, warehouses or other location (defined by the user with code info, for more information about code info, see , Defining code info). To maintain the history data of the transformer, click History in the MV/LV transformer data form. If the Transformer size not found error message is displayed when inserting a new transformer, add the transformer data to the TRANSFORMERS_IN_PLANNING table of the network database and try again Inserting LV station To add an LV substation (For general information about inserting the lines and components, see 16.1, Inserting medium and low voltage network lines and components): 1. Select the node type LV substation. 2. Insert feeding switch data to the data form. The Feeder field contains a label for the feeding switch. Click Close and confirm not to add a switch, if you want the feeding to be connected to the busbar without cells. 3. Give the number of cells in separate dialog box. 4. Give the number of cells for feeding if the feeding will not be connected to the busbar without cells. 5. Insert data to the LV box data form. 6. Insert other line sections and switch data to the data forms. 7. Adapt the LV substation diagram, if needed. See 16..1, Changing node type for a more detailed description on how to handle this diagram and its components. 137

138 17.. Inserting LV box To add an LV box (For general information about inserting the lines and components, see 16.1, Inserting medium and low voltage network lines and components): 1. Select the node type LV box. 2. Insert feeding switch data to the data form. The Feeder field contains the label for the feeding switch. 3. Give the number of cells in the separate dialog box. 4. Give the number for incoming cell in the separate dialog box. 5. Insert data to LV box data form. 6. Insert other line section and LV switch data to the data forms (For more information about LV switch data form, see 17.12, Inserting LV switch). 7. Adapt the LV box diagram, if needed. See 16..1, Changing node type for a more detailed description on how to handle this diagram and its components Inserting generator You can add two types of generators to the network. These generators are taken into account in the load flow calculations of DMS 600 WS. Large regulating generators in power plants, which are used for regulating the voltage. Smaller distributed controlling generators which produce active power and reactive power by regulating the produced reactive power. It is also possible to link a measurement from the SYS 500/600 database to automatically update the values for generator s P and Q. Even if there exists a link to a measurement it is possible to change the values in Simulation mode in the workstation. To add the generator data (For general information about inserting the lines and components, see 16.1, Inserting medium and low voltage network lines and components): 1. Select the node type Generator. 2. Insert generator data to the data form. Select the type of the generator by checking the Reactive power for distributed generators and Voltage for power plants in the generator data form. 3. Connect the distributed generator with fixed or measured reactive power to the network using a block transformer. For successful load flow calculation, use a separate load point. In case of a MV network, this is done by using a block transformer. A block transformer as a MV/LV transformer is added to the network feeding the generator node. Indicate the MV/LV transformer to be the block transformer by selecting the Generator block transformer check box in the transformer data form. In case of an LV network, this is done using a customer node. The customer node must feed the generator. There must be a direct connection with only one line section between the customer node and the generator node. If there is also electricity con- 13

139 sumption at the location, the consumption data can be given normally to the customer node. The generator data affects the total load Inserting arc suppression coil You can add two types of arc suppression coils to the MV network: Automatically controlled arc suppression coil Distributed stationary arc suppression coil. To add the arc suppression coil data (For general information about inserting the lines and components, see 16.1, Inserting medium and low voltage network lines and components): 1. Select the node type Arc suppression coil. Insert the automatically controlled arc suppression coil into the HV/MV station. 2. Insert arc suppression coil data to the data form. Arc suppression coils in the stations are not imported during the importation of station diagrams from MicroSCADA Inserting MV fuse You can add MV fuses to the MV network. The fuses are taken into account in the protection analysis of DMS 600 WS. The fuse state can also be used for defining the topology. To add MV fuse data: 1. Select the node type Fuse. 2. Insert MV fuse data to the data form. Check the State control enabled check box to use the fuse state in topology definition. Define the fuse state in the network database using DMS 600 NE and the real time state in DMS 600 WS. If the state control is disabled, the MV fuse switching state is closed and it is noticed only as a protection device. For general information about inserting the lines and components, see 16.1, Inserting medium and low voltage network lines and components Inserting LV switch You can add LV switches to the LV network. LV switches are taken account in the protection analysis of DMS 600 WS (For more information about LV protection analysis settings, see , Protection analysis settings). The switch state is also used in the topology definition. To add the LV switch data: 1. Select the node type Fuse. 139

140 2. Insert LV switch data to the data form. Select the switch type using the list in the Switch field. The LV switch type can be a circuit breaker or an LV fuse. 3. Select also the fuse type (defines the fuse size). Click Fuse type to open the LV fuse types data form. If the defined fuse type data is not inserted, the default melting curve for that nominal current is used. For general information about inserting the lines and components, see 16.1, Inserting medium and low voltage network lines and components Inserting measurement transformer data Summation current transformer, neutral current transformer and voltage transformer data can be inserted to the database. Measurement transformer data is used to define the relay values for the protection analysis of DMS 600 WS. To add the measurement transformer data: 1. Open the circuit breaker data form. 2. Click New Relay in the bottom of the data form. 3. Give a code for the new component using the dialog. 4. Right click Protection units and select an appropriate measurement transformer (current, voltage and neutral current) from the popup menu. 5. Give a code for the new component using the dialog. 6. Insert measurement transformer data to the data form. Measurement transformers in the stations are not imported when importing station diagrams from MicroSCADA. Inserting measurement transformer into its own node A measurement transformer can be inserted into its own node or as an additional component in a circuit breaker node. For instructions on inserting a measurement transformer to a circuite breaker node, see 17.13, Inserting measurement transformer data. For instructions on inserting a measurement transformer into its own node, see 16.1, Inserting medium and low voltage network lines and components. A measurement transformer located into its own node can be linked with a protection relay. To link existing measurement transformer to protection relay: 1. After completing steps 1-5 in the instructions above, click Update. 2. Press Yes when asked if you want to edit existing measurement transformer. Protection relay is now linked with existing measurement transformer. 140

141 Inserting grounding data The grounding data of medium and low voltage networks can be added to the network database. The groundings can be seen on the network window, but the data is not used in the network analysis of DMS 600 WS. To add the grounding data: 1. Select Edit > Add Earthing. 2. Click a point in the network window. 3. Insert grounding data to the data form Measurements General about measurements MicroSCADA uses process objects to present the quantities measured from the network process. After the definition of the connection, you can see the process measurement values in the network window. Additionally, the measurement value is used in DMS 600 WS to make the network calculations more accurate. Measurements from MicroSCADA are updated automatically to the use of DMS 600 software. With a manually updateable measurement node you can also model a separate load point or a disconnector which is the ending point of a branch. This data is used in the network calculations of DMS 600 WS. Manually updateable measurement values are inserted to the use of DMS 600 software Inserting measurement To add a measurement: 1. Select Edit > Add Measurement. 2. Click a point in the network window. The measurement data form opens. 3. Select the process object from the list in the SCADA object field, if you use MicroSCADA measurement value (For more information about integration of MicroSCADA measurements, see , MicroSCADA measurements). If you are using the OPC interface, select Edit > OPC Codes before adding the measurement. The process object is selected using the Select OPC code field (for more information about integration of MicroSCADA measurements, see , MicroSCADA measurements). 4. Define the type of the measurement node in the Type box. The type definition is important if the measurement is needed in network calculations of DMS 600 WS (for more information about using measurements in the network analysis, see 141

142 , Defining current measurement, , Defining voltage measurement and , Defining separate load point). 5. Connect the measurement node to the component of the network database by using the Connected network object box. The connection is important if you must use the measurement data in the network calculations of DMS 600 WS (for more information about using measurements in the network analysis, see , Defining current measurement, , Defining voltage measurement and , Defining separate load point). Choose the node of the network from the network window by clicking it when the Measurement data form is open. After selection of the node, the node code is shown in the node dialog box (For more information about the node dialog, see 14.6, Selecting node, line section, site node or diagram). Click Connect to make the connection between the selected node and the measurement node. The thin reference line is shown between the network node and the measurement node. Click Disconnect to remove the connection between the network node and the measurement node. 6. Use the Prefix, Unit, Factor, Decimal place and Default value to define the data form for every measurement object. The Preview box displays the outlook of the measurement. 7. To add a new measurement object for the measurement node, click Add. You can connect 1-5 MicroSCADA measurement objects to one measurement node. Use the arrow buttons to browse the measurement objects inside the measurement node.. If you define more than one MicroSCADA measurement objects for one measurement node, you can use the Operation field to define how to calculate one value to be presented in the network window. The type definition of a measurement node is important if you must use the measurement in the network calculations of DMS 600 WS. The measurement node must also be connected to the network component Defining current measurement The current measurement is used in the load estimation to define the load data of the feeder and MV/LV stations more accurately. Define only one current measurement object per one measurement node. Further, you can use the current measurement to define power values for motors or generators (for more information see , Defining power values to motors and generators). To define current measurement: 1. Choose the measurement type Current measurement in measurement data form. 2. Define the unit of the current measurement to be amperes (A). If the original measurement is in another unit, use the scale factor to convert the unit to ampere. 3. Connect the current measurement node to some node along the medium voltage feeder or to the feeder node connecting the MV/LV station and the feeder. If you 142

143 want to use current measurements in a load estimation, they cannot be connected to a node belonging to a feeding HV/MV substation Defining voltage measurement The primary substation voltage measurement is used as a supplying voltage for feeders in load flow calculations. The voltage measurement is always used instead of the primary station nominal voltage or the setting of default busbar voltage when it is available (For more information about default busbar voltage setting, see , Defining general network analysis settings). To define voltage measurement: 1. Choose the measurement type Voltage measurement in the measurement data form. 2. Define the unit of the voltage measurement to be kilovolts (kv). If the original measurement is in another unit, use the scale factor to convert the unit to kilovolts. 3. Connect the voltage measurement node to some node belonging to a HV/MV substation. If you want to use voltage measurements in the load flow calculation, they cannot be connected to a feeder node Defining separate load point Manually updateable, separate load points can be used in network calculation to supply an additional load or supply from a neighboring network that is not included in the network database. To define a separate load point: 1. Choose the measurement type Manual Active Power in the measurement data form. 2. Define the unit of the manual active power to be kilowatts (kw). If the original measurement is in another unit, use the scale factor to convert the unit to kilowatts. 3. Connect the additional load measurement node to any node of the medium voltage network and the neighboring supply measurement node to a disconnector which is the ending point of the branch. The system takes separate load points into account during network calculation by adding the active power of the measurement node to an active power of the network node. To insert the manual active power value in DMS 600 NE, open the measurement data form by clicking Measurement Value and inserting the value into the dialog. Insert the manual active power value in DMS 600 WS by opening the measurement data form and inserting the value into the dialog Defining power values to motors and generators It is possible to link a measurement from SYS 500/600 database to automatically update the values of active (P) and reactive (Q) power of motors and generators. 143

144 Used measurement types are Active power, Reactive power and Current measurement. If only the current measurement is available, the voltage in the measurement point is used to estimate the total power (S). This value is divided into active and reactive parts using the proportions of statically given P and Q. To insert a motor measurement point: 1. Using NE, insert a new measurement point near the motor node that you just created by selecting Edit > Add Measurement. 2. Enter the node code of the motor (for example, N1 ) to the Connected network object Node code box and click Connect. 3. Select the Measurement object type (Current measurement, Active Power measurement and Reactive Power measurement). 4. Select the corresponding SCADA object code to create the online connection between MicroSCADA and DMS 600. Click Save. 5. If you want to add another new measurement object type for the same network object (motor), click Add and repeat steps 1 to After you have inserted the measurement points connected to the motor(s), you must update the binary network database by selecting File > Update Network Database. The change in the motor measurement data affects the load flow calculation results in the radial calculation of the WS. To insert a generator measurement point: 1. Using NE, insert a new measurement point near the generator node that you just created by selecting Edit > Add Measurement. 2. Enter the node code of the generator (e.g N1 ) to the Connected network object Node code box and click Connect. 3. Select the Measurement object type (Current measurement, Active Power measurement and Reactive Power measurement). 4. Select the corresponding SCADA object code to create the online connection between MicroSCADA and DMS 600. Click Save. 5. If you want to add another new measurement object type for the same network object (generator), click Add and repeat steps 1 to After you have inserted the measurement points connected to the generator(s), you must update the binary network database by selecting File > Update Network Database. The change in the generator measurement data affects the meshed network load flow calculation results in the loop calculation of the WS Inserting free database object The free database can be used to add free database object types and data to the network database. You can define the required object types by making changes within the database tables. The data in the free database is presented in the free data form. Only the label text is displayed for text object types. With the free database you can also add extra fields 144

145 to the tables of existing node and line section types that contain the initial fixed data content. Also text data is managed with the free database objects. To add the free database object: 1. Select Edit > Add Object. 2. Select the object type from the list that contains the predefined object types (For more information about object type definition, see , Defining free database object type and text object type). 3. Click a point in the network window. 4. Insert the label for the new object. In the case of text data, write the text into the label field. 5. Insert the object data to the free data form. (For more information about free data forms, see , General about free data forms). If you use text data, more information is not needed. 6. For the same object type node, click the point in the network window and continue from step 4. For other object type nodes, select Edit > Add Object again Inserting component and conductor type data General about inserting component and conductor type data The type data of disconnectors, MV fuses, MV and LV conductors of a network are saved using the type data forms. The type data is used in the network analysis of DMS 600 WS. The fuse type data is used in the protection analysis of DMS 600 WS Inserting disconnector type data To add disconnector type data: 1. Open the type data form by selecting File > Database > Disconnector Types or clicking Type Info in the disconnector data form. 2. To add a new disconnector type data, click Add in disconnector type data form. 3. Insert disconnector type data to the data form Inserting MV and LV fuse type data To add MV or LV fuse type data: 1. Open the type data form by clicking Fuse Types in the MV fuse or LV switch data form. 2. Click New in the fuse type data form to add a new type data. 3. Insert MV or LV fuse type data to the data form. 145

146 Give at least two operation times for each MV fuse type. Missing operations times are calculated on the basis of given values Inserting MV and LV conductor type data To add MV and LV type data: 1. Open the type data form by selecting File > Database > MV Conductor Types or File > Database > LV Conductor Types or by clicking Conductors in the line section data form. 2. Click New Type in the conductor's type data form to add new type data. 3. Insert conductor type data to the data form. Define the Equivalent temperature field to calculate the conductor resistance. The value must be between C. If the field is left empty, the default value + 20 C is used. The Zero resistance and Zero reactance values are needed for the unbalanced fault analysis. 4. Select the Color (0 ) of the line type, which defines conductor type presentation after selecting View > Coloring > Line Types (for more information about colors, see , Using network line colors). 5. Define the Line Type (Solid Line, Dashed Line, etc.). The conductors are presented in the defined line type when one of the topology coloring modes is selected. Line types are definable for every conductor. The definition is added into the device card of MV conductor. Insert all values from the conductor type data form for the corresponding voltage. If the same conductor type is used for many voltage levels, define a separate conductor type for each voltage level Relay data Inserting relay data Protection relay data must be entered in the database by using data forms for each protection unit: overcurrent, earth-fault, reclosing, differential and distance. Relay data is needed for the protection analysis in DMS 600 WS. Differential and distance relay units exist for documentation purposes only and they are not handled in protection studies. To add relay data: 1. Open the circuit breaker data form. 2. Click New Relay in the bottom of the data form. 146

147 3. Give a code for the new component using the dialog. 4. Right click Protection units and choose an appropriate relay unit (overcurrent, earth-fault, reclosing, differential or distance) from the popup menu. 5. Give a code for the new component using the dialog. 6. Insert relay data to the data form. For more information about the data, see , Inserting overcurrent relay data, , Inserting earth-fault relay dataand , Inserting reclosing relay data. Relays in the stations are not imported during importation of station diagrams from MicroSCADA. To show the relay settings of the feeder, click Relay Data in the circuit breaker data form or select Relay from the shortcut menu opened by right-clicking over the feeder in the main network window Inserting free data You can add free data fields for every protection unit (overcurrent, earth-fault, reclosing, differential and distance) and measurement transformers. To insert a free data field and value: 1. Right-click Free data and select Add property in the drop down list. 2. Fill in Property and Value in the Add free data dialog. Free data can also be linked with data in the CODEINFO table in the database. To link data: 1. Right-click Free data and select Add property in the drop down list. 2. Fill in Property in the Add free data dialog. 3. Insert a new INFOTYPE in the CODEINFO table. Always name INFOTYPE in the following format: RELAYPROPERTY_<property>, where <property> is the name (Property) of the free data field given in the previous step. The user interface for editing the CODEINFO table is described in , Defining code info. Now values inserted in the INFO field in the CODEINFO table with INFOTYPE field RELAYPROPERTY_<property> can be chosen from the drop down list Reclosing curve The principle of reclosing a curve is presented in the figure, where: t1 is the time delay before the fast reclose including the operating time of the relay and circuit breaker. t11 is the operation time given by inverse time characteristic function. t2 is the rest time in fast reclosings. 147

148 t3 is the time delay before the delayed reclosing including the operating time of the relay and circuit breaker. t31 is the operation time given by inverse time characteristic function. t4 is the rest time in delayed reclosings. t5 is the time delay after the delayed reclosing including the operating time of the relay and circuit breaker. t51 is the operation time given by the inverse time characteristic function. Figure Reclosing curve DMS_reclosing_curve_a.png Inserting overcurrent relay data You can analyse two types of overcurrent relays in the protection analysis of DMS 600 WS: Definite time-delay type and Inverse time type. To insert the operating data both for the time tripping and the instant tripping: 1. Select from the list the characteristics curve that defines the type of the relay. 2. Insert the operating current. You can insert the primary operating current or the secondary operating current with current transformer data. 3. Insert short-circuit durations before fast reclosing and before and after delayed reclosing. The short-circuit duration consist of the delay value set for the relay, and the operating times of the relay and circuit breakers. For more information about operation times, see , Reclosing curve. 4. For user-defined inverse time characteristic, insert also alfa and beta values. 5. Insert the time multiplayer for inverse time characteristic. 6. Insert the number of fast and delayed reclosings (>=0). 7. Right-click Protection stage and select Lockings from the popup menu. Select a relay unit and click Add. Locking prevents the relay operation by signal from other relay(s). Lockings are used to make selectivity to function properly. To cancel the instant tripping, set the operating current of instant tripping to zero. If both trippings are in use, the operating current of time tripping must be smaller than the operating current of instant tripping. The short-circuit times of the 14

149 instant tripping must be shorter than the short-circuit times of time tripping Inserting earth-fault relay data The protection analysis function of DMS 600 WS can analyze isolated or neutral compensated networks. To insert the operating data for both time tripping and instant tripping: 1. Select the relay protection type from the list. 2. Insert directional angle and operational angle. 3. Select the action of the earth-fault relay to be tripping or alarming. 4. For an electronic type relay, insert the neutral current I0 and neutral voltage U0 settings. You can insert the neutral current setting separately for instant tripping. Give the settings as secondary side values - primary side values are also visible in the form. 5. For a mechanical relay, insert the operating values P0 and Q0. 6. Insert time settings. 7. Insert the number of fast and delayed reclosings (>=0) Inserting reclosing relay data Insert the following reclosings data for the protection analysis of DMS 600 WS: Rest time in a delayed reclosing Rest time in a fast reclosing Number of fast reclosings (>=0) Number of delayed reclosings (>=0) Start from trip info and start delay or Additional time delay for autoreclose shots 1-6 The number of fast and delayed reclosings mentioned in , Inserting overcurrent relay data and , Inserting earth-fault relay data is replaced with a common setting for autoreclose unit. About reclosing data Reclosing relay data is divided into two parts: 1. Data common for all reclosing operations. 2. Data specific to a certain autoreclose shot. 149

150 Part one consists of rest time for fast reclosing and delayed reclosing, number of fast reclosings and number of delayed reclosings. Part two comprises data of six separate autoreclose shots, each of which is composed of information if operation of shot is started from trip of other protection function, or from start command of protection. In addition, each shot has a time setting which indicates Start delay or Additional time delay used in protection. Shots 1-3 are related to over current protection stage one (time tripping) and shots 4-6 are related to over current protection stage 2 (instant tripping). Shots 3 and 6 describe the final trip function which is used when final tripping is handled with the autoreclosing unit. Autoreclosing shots initiated by earth fault protection stages cannot be edited separately. However, settings in part one are affecting them. Defining trip time during autoreclose operation In part one, rest time of fast reclosing represents time t2 and rest time of delayed reclosing represents time t4 in , Reclosing curve. For shots 1 and 4 time t1 + t11 can be set two different ways: 1. If start from trip is set to No, time t1 + t11 is directly the value set to the field Start delay of the autoreclose shot. 2. If start from trip is set to Yes, time t1 + t11 is calculated as a sum of the operation time of the protection stage and the time value set to the field Additional time delay of the autoreclose shot. In the first case the value set to the protection stages and the Operate time is ignored. For shots 2 and 5 time t1 + t11 is replaced with time t3 + t31 and for shots 3 and 6 with time t5 + t51. If the Operation mode is selected as any of the inverse time operation modes, the Operate time above is replaced with time calculated from the selected inverse time curve Inverse time curves About inverse time curves An inverse time curve is a curve that is used to define an operation time of a protection relay. The input is typically a relation between set current value and measured fault current. Inverse time curves are defined with various equations. Some of them are defined 150

151 in international standards (IEC/IEEE) and some are industrial de facto standards (IAC) or manufacturer specific curves (RI, RD) Calculating operation times The software calculates the operation time for protection based on calculated fault current and relay settings in the memory. Equation used when calculating operation time depends on the curve type used. Equations are presented in Table Table Inverse time curve equations used in DMS 600 Curve type Definite time Curve equation About curve Defined in IEC IEC Defined in IEC IEEE/ANSI Defined in IEEE standard C In standard constant D is always 1. IAC Used before C37.112, for example by GE. RI Origin of this curve is in old ASEA (nowadays ABB) relays RD Origin of this curve is in old ASEA (nowadays ABB) relays In all equations of Table the equation I > I set must be true to initiate protection. In addition, if the calculated operation time is shorter than the set minimum operation time, the set minimum time is used. Correspondingly, if the result of the calculation is longer than the set maximum operation time, the maximum time is used. To calculate operation times: 1. Open the DMS 600 Network Editor. 2. Right-click on the required feeder. 151

152 3. Select Relay. 4. Click the Overcurrent tab. 5. Ensure the Stage 1 Operation mode is set to constant current. 6. Ensure the Stage 2 Operation mode is set to constant current. 7. Click Close Adding inverse time curves To add inverse time curves: 1. Open the Inverse time curve manager dialog by selecting File > Database > Inverse time curve manager. 2. Click Add. 3. Enter the curve name in the text box and press Enter. 4. Select the curve type. The default type is IEC. 5. Enter the curve constant values. Only constants related to the selected curve type are available. For example, A and B are allowed for IEC and A to D are allowed for IEEE. All constants are allowed for IAC. 6. To set the curve visibility, check or uncheck Visible. The default is Visible (checked). 7. Click Update.. To close the Inverse time curve manager, click Close Modifying inverse time curves To modify inverse time curves: 1. Open the Inverse time curve manager dialog by selecting File > Database > Inverse time curve manager. 2. Select the required user defined inverse curve. 3. To edit the inverse time curve, click the curve name on the list. 4. To stop editing, press Enter. 5. The curve type, visibility, and curve constants of the selected curve can be edited. 6. Click Update. 7. To close the Inverse time curve manager, click Close Removing inverse time curves To remove inverse time curves: 1. Open the Inverse time curve manager dialog by selecting File > Database > Inverse time curve manager. 2. Select the required user defined inverse curves. User defined inverse curves are displayed in black. 3. Click Remove. 4. Click Yes. 5. To close the Inverse time curve manager, click Close. 152

153 Hiding inverse time curves To hide inverse time curves: 1. Open the Inverse time curve manager dialog by selecting File > Database > Inverse time curve manager. 2. Select the required inverse time curve. 3. Uncheck Visible. 4. Click Update. 5. To close the Inverse time curve manager, click Close Selecting operation mode for relay To select the operation mode for a relay: 1. Right-click the required circuit breaker node. 2. Select Relay. 3. Click the Overcurrent unit or Earth fault unit tab. 4. Click Operation mode. 5. Select the required operation mode Moving part of the network To move a larger part of the network (for example, a total feeder or station): 1. Perform the multiselection of line sections as described in 14., Multiselection of line sections. 2. Click Move in the Sections-Multiselection dialog. A rectangle containing all selected sections will appear in the network window. 3. Move the rectangle into the desired position and click with the mouse. The selected line sections with existing connections will be moved into the new position. To move station diagrams, you must select all sections of the station Copying part of the network To copy a larger part of the network (for example, a total feeder or station): 1. Perform the multiselection of line sections as described in 14., Multiselection of line sections. 2. Click Copy in the Sections-Multiselection dialog. A rectangle containing all selected sections will appear in the network window. 3. Move the rectangle into the desired position and click with the mouse. The selected line sections with existing connections will be copied into the new position. 4. Select how to define the codes for new components. Codes can be given separately for each one, generated automatically or searched with the Find/Replace method. 153

154 If you use the Find/Replace method, and the Find string is not found in the source component code, a new component code will be prompted. To copy a station diagram, you must select all sections of the station. It is also possible to copy relay data and configuration data of circuit breaker Deleting part of the network To delete a larger part of the network (for example, a whole feeder or station): 1. Perform the multiselection of line sections as escribed in 14., Multiselection of line sections. 2. Click Delete in the Sections-Multiselection dialog. 3. Confirm the deletion of selected line sections. 4. Confirm the saving of line section history data. 5. Confirm the deletion of possible unconnected nodes. 6. Give the new location for a possible removed transformer. To delete a station diagram, you must select all sections of the station Moving low voltage network To move the whole low voltage network of an MV/LV transformer: 1. Read the low voltage network/networks to be moved into the memory. 2. Select Edit > Move LV Network. 3. Insert the distance to be moved in meters in the direction of X and Y. 4. Confirm the moving. If only parts of the low voltage networks have to be moved, see 16..3, Moving node or site node and 16.., Moving point in existing line section Attaching and removing documents Documents are data (for example, pictures, text documents or video clips) that are attached to the nodes of the network database (network components or free form objects). Attaching documents to the nodes is managed in DMS 600 NE. You can browse the attached documents in DMS 600 WS. To attach a document: 1. Click the component/line section to open the node/line section dialog. 154

155 2. Click Add Docum. (For more information about node/line section dialogs, see 16..1, Changing node type) or click Add Docum. in the free data form. 3. Select the document to be attached using the standard file-opening dialog. The default directory is Doc. If the selected document is not located in the Doc directory, the file is proposed to be copied into that directory. The copying to the Doc directory is recommended. All the attached documents are then located in the same directory which can be used by everyone. Avoid leaving the attached document only to your own workstation. If copying is allowed, the system asks a permission to remove the original file. 4. Insert the data of the document into the dialog. Click Remove to remove the attachment between the network node and the document. After the confirmation the document file is also removed. If the document is attached to other nodes, the removal is not prompted Inserting load data General about inserting data Load data is needed for the network analysis in DMS 600 WS. Load data must be entered into the database. DMS 600 uses Velanders factors or defined load models (load curves) when changing the annual energy information of active and reactive power. The load model is selected normally during installation (see Installation Manual). The selected load model affects the inserting of load data. The load model selection can be changed later on. In this case you must restart the programs and update the network database. Load data is inserted to MV/LV stations if only the medium voltage network is used in DMS 600. If the low voltage network is used, the load data is entered to the low voltage consumer. The loads inside the primary substations are not modeled Inserting load data to MV/LV station If DMS 600 uses Velander's factors for load modeling, and only the medium voltage network is used, insert the load data into each MV/LV station. If many transformers are located in the same MV/LV substation, the load is allocated to the first transformer. Load data to MV/LV station can be entered while adding a new MV/LV station, or inserted later. 155

156 To insert load data to an existing MV/LV station: 1. Select the MV/LV station and click Load Data in the site node diagram or click Load Data in the shortcut menu opened by right-clicking an MV/LV station or a line section connected to the MV/LV station. 2. Insert one or several load measurements or estimates. Use Real power (kw) or Annual energy (kwh). Additionally, Power factor (cosfii) can be given for each load measurement. If the load is given as annual energy, empirical factors (Velander's factors) are used to convert the annual energy to peak power Inserting load data to low voltage customer If DMS 600 uses Velander's factors for load modeling and the low voltage network is used, insert the load data into each customer nodes. Load data to customer can be entered while adding a new customer node or it can be inserted afterwards. To insert the load data to an existing customer node: 1. Read the low voltage network into the memory. 2. Select the customer node. 3. Click Load Data in the node diagram. 4. Insert one or several load measurements or estimates. Use Real power (kw) or Annual energy (kwh). Additionally, the Power factor (cosfii) can be given for each load measurement. If the load is given as annual energy, empirical factors (Velander s factors) are used to convert the annual energy to peak power. Before using load data in the medium voltage network, open the network database and run the macro MV_LV_LOAD_UPDATE (or select MV/LV loads from LV-networks from the menu. The query calculates the loads for MV/LV substations using the customer load data Manually inserting load data for load curve modeling If DMS 600 uses defined load models (load curves), and the real customer energy data cannot be imported from an external customer database, insert load data directly to the database table. For more information about table definitions, see , Importing customer information. If LV networks are not included in the network analysis, insert "virtual customer data" to the database table. 156

157 To create "virtual customer data": 1. Insert the total annual energy and load curve number for each MV/LV substation directly to the database table. 2. Create load curves for every important MV/LV substation using Load Curve Editor (for more information see Appendix, Load curve editor). The maximum number of simultaneous load curves is You can use the "virtual customer data" for MV/LV substations only if LV networks are not included in network analysis Temporary network data General about temporary networks The management of temporary networks enables the maintaining of medium and low voltage temporary network data. The data is saved in a separate file from the network database (Netdata/Tempnet.dat). The file contains the additions, removals and changes made in Temporary Network Mode. The temporary network components cannot be integrated to the process points of MicroSCADA. For integration, you must insert the component in the network database. During the start up of DMS 600 NE, only the real network data from the binary network file is loaded. The handling of temporary network data always occurs in separate Temporary Network Mode. DMS 600 WS loads the temporary network data during start -up and shows the data together with other network data in the network windows Inserting temporary network data Management of temporary network data is done in Temporary Network Mode. First select Edit > Edit Network Data to switch to Data Edit Mode. Then select Edit > Temporary Network to switch to Temporary Network Mode. If you want to insert low voltage networks into the temporary network data, change the voltage level to low voltage. In Temporary Network Mode the editing and inserting of temporary network data is done in the same way as in Data Edit Mode. Temporary networks have the following differences: Disconnector and MV/LV transformer data forms are different containing less technical data. 157

158 Integration of components to process points of MicroSCADA is not supported. Commands Edit > Move LV Network and Edit > Save LV Topology are disabled. The measurement transformers cannot be inserted. The relays are handled as a block attached to the circuit breaker. To save the temporary network data to a separate file (Tempnet.dat), click Save in the Temporary Network dialog. The data is updated to other workstations in the same way as other network data. For more information about updating of the network data to other workstations, see 13.3, Updating network data to workstations Removing temporary network data To remove the temporary network data: 1. Select the temporary network node or line section in Temporary Network Mode. 2. Click Remove tmp in the node or line section dialog Fault handling areas Viewing fault handling areas This chapter does not apply to the DMS 600 (Base) license. The Fault Location license is required for fault management. To view fault handling areas in the network window: 1. In the DMS 600 NE, select Settings > Fault Handling Areas. 2. Select one of the following: View > Show > Area Components > Show Areas by Outlines. View > Show > Area Components > Show Areas by Filled Colors. 3. Select the area from the list. The area is highlighted in the network window Creating a new fault handling area This chapter does not apply to the DMS 600 (Base) license. The Fault Location license is required for fault management. To create a new fault handling area: 15

159 1. In the DMS 600 NE, select Edit > Edit Network Data. 2. Select Settings > Fault Handling Areas... > New Area. 3. Give border points for the new area by clicking in the network window. 4. Give the last border point by right-clicking in the network window. 5. Give a name for the new area Deleting a fault handling area To delete an existing fault handling area: 1. In the DMS 600 NE, select Edit > Edit Network Data. 2. Select Settings > Fault Handling Areas... > New Area. 3. Select the area from the list. 4. Click Delete Area. 159

160 1. Integration of DMS 600 and Microscada 1.1. General about integration of DMS 600 and MicroSCADA DMS 600 functionality is very deeply integrated to Control System SYS 600 version 9.x (SYS 600). Most functionalities can be used also with MicroSCADA SYS 500 versions.4.2,.4.3,.4.4 or.4.5. The abbreviation SYS 600 is used when the topic is valid only for SYS 600. The abbreviation MicroSCADA is used when the topic is valid for both SYS 500 and SYS 600. The connection between MicroSCADA and DMS 600 is operational, if the SCADA connection sublicense is used. MicroSCADA OPC Data Access Server is an implementation of the interface specification OPC Data Access Custom Interface Standard, Version 2.05A, on the MicroSCADA system. All the process objects of MicroSCADA are exposed by the server as OPC items and all the attributes of process objects as OPC item properties. Earlier Open++ Opera version's communication has been based totally on SCIL API interface which can be used also in DMS 600. The OPC Data Access interface of DMS 600 can be used in parallel with SCIL API in some communication tasks, if MicroSCADA Pro Control System SYS 600 version 9.x (SYS 600) and MicroSCADA SYS 500 version.4.5 are used. DMS 600 can also communicate with other SCADA systems using the OPC Data Access interface. The integration of DMS 600 and MicroSCADA enables: Importing of station pictures from MicroSCADA to the network database in DMS 600 NE using import files generated by Picture Editor or Display Editor or using automatic (COM interface) send function of the Display Builder (for more information about importing, see 1.4.1, Old style HV/MV diagrams and 1.5.1, New style HV/MV diagrams). Starting a DMS 600 session via MicroSCADA using SCIL API or COM interface method (SYS 600) (For more information about required engineering, see Integration with SYS. Control actions by opening old or new style (SYS 600) MicroSCADA graphics or SYS 600 control dialogs from DMS 600 WS using the SCIL API or COM interface (SYS 600) (For more information about control actions, see 1.6.1, Process objects, 1.7.1, General about component integration and 1..1, General about picture names.) Getting all position indication data from SCADA to the topology management of DMS 600 WS using SCIL API or OPC Data Access (SYS 600) (For more information about position indication data, see 1.6.1, Process objects and 1.7.1, General about component integration.) 160

161 Getting measurement, alarm and warning data from SCADA to the load estimation, alarming and displaying of DMS 600 WS using SCIL API or OPC Data Access (SYS 600) for more information about measurement etc. data, see 1.6.1, Process objects and 1.7.1, General about component integration.) Getting the required process data for DMS 600 fault location functions using SCIL API (for more information about engineering required, see Integration with SYS 600.) Automatic fault isolation and restoration using the switching plan produced by DMS 600 WS to control the MicroSCADA using SCIL API (for more information about the required engineering, see Integration with SYS 600.) Getting real relay settings for DMS 600 WS protection analysis (for more information about the required engineering, see Integration with SYS 600.) The transfer of root point coloring and power flow direction from DMS 600 WS to MicroSCADA station pictures using SCIL API or OPC Data Access (SYS 600) (for more information about the required engineering, see Integration with SYS 600.) Locating of network components in DMS 600 WS network window from the Monitor Pro graphics and alarm and events lists using COM interface (no special engineering required). Downstream tracing feeder in DMS 600 WS network window from the Monitor Pro graphics (line indicator and circuit breaker) using COM interface (no special engineering required). Showing feeder information from DMS 600 WS in SYS 600 single line diagrams using COM interface (no special engineering required). Zooming in and out in DMS 600 WS network window from the Monitor Pro graphics using COM interface (no special engineering required). For more information about DMS 600/MicroSCADA integration functions in Micro- SCADA, see Integration with SYS 600. DMS 600 WS can be connected to MicroSCADA without using MicroSCADA station and control pictures. For more information about the MicroSCADA monitor setting, see 5.1, General about licenses Offline functionality The connection between MicroSCADA and DMS 600 functions requires the SCADA connection sublicense. DMS 600 can be used with MicroSCADA, without SCADA or with other SCADA systems using the OPC Data Access interface. The offline functionality can be used also, for example, in the beginning of MicroSCADA or DMS 600 projects. If an OPC interface is defined, it is used for communication primarily. The SCIL API interface is used for communication only if the OPC interface is closed, the SCIL API interface is opened, and the scadacode for the component is defined. 161

162 DMS 600 SA is set to start automatically during the installation of DMS 600, if the MicroSCADA is not installed. DMS 600 SA takes care of the data communication routines between DMS 600 applications. During offline functionality the communication functions between DMS 600 SA and the service program of the Support System Interface (Bdu_ssiser.exe) and DMS 600 and OPC Server are disabled. Almost all events and messages between DMS 600 programs are used in the same way as during the communication with MicroSCADA Integration tools Depending on the DMS 600/MicroSCADA communication method, you can use two integration tools: DMS Interface Package of MicroSCADA LIB 500 Application Library contains the support for DMS 600 distribution management system using SCIL API. OPC data configuration tool of DMS 600 NE. The integration of DMS 600 and MicroSCADA requires some tasks in DMS 600 NE: MicroSCADA station diagrams have to be converted to the network database of DMS 600. The process object codes (scadacodes) must be defined for components needed in DMS 600. The file saving the virtual process points has to be created for the integration of MicroSCADA and DMS 600. The picture names for primary substations must be defined. The MicroSCADA measurements used in DMS 600 must be defined Importing old style HV/MV station diagram from MicroSCADA Old style HV/MV diagrams The picture format of SYS or later is different from previous revisions. However, old format pictures are fully supported in the.4.2 and later revisions of SYS 500/600. An old style HV/MV station diagram can be imported from MicroSCADA or a station diagram can be created and updated in DMS 600 NE. The creation and editing of station diagrams is described in 17.2, Inserting HV/MV station. The station diagram import function is intended for the importing of HV/MV station diagrams, not for the importing of disconnectors or other station diagrams. 162

163 The station import function does not support parallel editing from other instances of DMS 600 NE Generation of input files in MicroSCADA MicroSCADA Topology Generator generates input files for station diagram import. Topology Generator generates two files in the directory Sc/Apl/Apl_name/Pict/Topology. The file name extensions for these files are.mto and.mtc. Delete old mto and mtc files from the Sc/Apl/Apl_name/Pict/Topology directory before the transfer. MicroSCADA Topology Generator allows transfer files to be generated from several station and control pictures. However, this feature is not fully supported in DMS 600 NE. If this feature is used, LINE type PFs must be checked so that they are not transferred twice. In addition, PFs that contain the same LNs should not be imported to DMS 600 NE Importing station diagrams To import station diagrams to DMS 600 NE: 1. Zoom in (to about m) and pan to the correct place in the network window. Check that the grid settings allow enough space for components in planned station area, so that the grid point distance is greater than the distance needed between the components. (For more information about network editing settings, see 21.2., Snap and grid settings.) 2. Select File > Import SYS 500 graphics. 3. Select the corresponding station diagram file (.mto) for importing and click Open. Make a shortcut that points to the directory Sc/Apl/Apl_name/Pict/Topology in the data directory of the primary fileserver. It makes it easier to find the mto and mtc files. 4. Indicate the upper left and lower right corners of the station with the left mouse button. 5. Insert the primary station data to the data form (For more information on station data, see 17.3, Inserting primary station data). 6. Define the default process object type. The choices are DB, AI, BI. (For more information about process objects, see 1.6.1, Process objects.) The defined object type will be used as a default value in generating Scada codes for circuit breakers and disconnectors during station diagram import. If the types of some switches differ, they must be changed manually afterwards. It is therefore useful to select the most common process object type. 7. Insert default line section data to the data form. The defined line section data will be used as a default value in generating line sections during station diagram import. 163

164 If the line section data differ, they must be changed manually afterwards. It is useful to select the most common conductor type or leave the field empty.. Confirm the station diagram import. 9. Finalize the importing. See , Connecting unconnected lines. If there are error warnings during importing, DMS 600 NE will launch Notepad to display the error warnings Finalizing the station diagram Connecting unconnected lines Check all line sections in the station diagram. Insert any missing line sections. In MicroSCADA Busbar Coloring Function one LINE type PF object can consist of separate drawing units. These drawing units are topologically connected after importing the station diagram to DMS 600 NE only if they have common points in horizontal and vertical lines. See below for examples. DMS_drawing_units_a.jpg Figure Examples of connections made in DMS 600 NE between different drawing units Inserting missing station components Insert missing components manually. At least the station components that are not connected to other objects are omitted when diagrams are imported. The following components are necessary for fault calculations and fault location in DMS 600 WS: The circuit breaker relays The current transformers 164

165 The voltage transformers Arc suppression coils The following components are also omitted when diagrams are imported. They are not necessary for the operation of the product, but they can be added to the database for data management purposes: The reactor The capacitor The generator Defining feeding points The station import function imports the feeding points of a station in MicroSCADA as feeders in DMS 600 NE. In order to get the station electrified, insert the feeding points manually in DMS 600 NE. See the examples below. Figure Adding feeding points to a station feeding_points2.jpg 165

166 Another option is to remove the line sections from the upper voltage level of the primary transformers. See the examples below. removing_line_sections2.jpg Figure Removing line sections from the upper voltage level of primary transformers Completing data forms DMS 600 NE uses some default values when importing diagrams. The following values must be manually updated, if the default values do not match the real ones, or the values are missing: Table Fields to checked after importation Data Form Line section Field Voltage level Conductor type Primary transformer Scada code Nominal voltage Circuit breaker Scada code Truck code Disconnector Feeder Primary station Scada code Scada code Scada code Scada picture name Station diagram transfer files (.mto and.mtc) do not include data on the voltage levels for line sections. For this reason all line sections are marked as being at the same voltage level. The voltages for primary transformers are also marked as having one common 166

167 value. The voltage for primary transformers and line sections is obtained from the station's nominal voltage. If there is a LINE type PF object between TRUCK and CB type PF objects, DMS 600 NE will import the truck as a disconnector and the circuit breaker as a circuit breaker without a truck code. If both TRUCKs have the same LN and IX, the first TRUCK will be imported to DMS 600 NE, but the last one will be ignored. If TRUCK and CB type PF objects are connected to each other directly, DMS 600 NE will import them as one compound circuit breaker having the truck's scada code as truck code Importing new style HV/MV station diagram from MicroSCADA New style HV/MV diagrams New style HV/MV station diagram can be imported from MicroSCADA, or a station diagram can be created and updated in DMS 600 NE. The creation and editing of station diagrams is described in 17.2, Inserting HV/MV station Generation of import files in MicroSCADA The import file is generated automatically when the picture is saved in SYS 600 Display Builder, if the Actions > Options > Build DMS Import File on Save option is selected. The file can be generated also by selecting Actions > Build DMS Import File on Display Builder. The station pictures are saved with the extension.v in MicroSCADA (for example, StationX.v). For DMS import the file is saved in the given file name and ini file format into the same directory with the extension.is6g (for example, StationX.is6g). For more information about the structure of import files, see Appendix, Structure of station diagram import file Importing station diagrams To import station diagrams to DMS 600 NE: 1. The SYS 600 Display Builder sends the import file automatically to DMS 600 NE after the file has been generated, if Actions > Options > Send DMS Import File to Network Editor after Build option is selected in Display Builder. You can also start the import from DMS 600 NE by selecting File > Import SYS 600 graphics and selecting the corresponding station diagram file (is6g) for import. 2. When you have confirmed the import startup question, the system asks for the diagram's location. Indicate the location by clicking the corners of the diagram. 167

168 3. Insert the default voltage level when prompted. 4. If, for some reason, the import file does not include all the needed information for complete importation, you will be asked to fill in the missing data. When all the needed information is given, you will be asked to confirm the import. All the objects and coordinates are stored to DMS database during the import. The OPC item names of primary transformers, disconnectors, circuit breakers and line indicators are also saved to the database and are included in the OPC configuration, so that needed values are subscribed automatically. The nominal voltages of primary transformers, windings, generators and line indicators are stored and, with connectivity analysis, they are used to get the nominal voltage level for the line sections in the station Component integration when using SCIL API Process objects All process objects that are involved in data transfer via the Support System Interface (SSI) between MicroSCADA and DMS 600, should be cross-connected by the process object's logical name in MicroSCADA. The cross-connection between components in the network database of DMS 600 and MicroSCADA process objects is created with DMS 600 NE and LIB 500 Application Library DMS Interface Package. For more information about the DMS 600/MicroSCADA integration functions of DMS Interface Package, see Integration with SYS 600. Virtual process points that refer to manually operated switches and to the connection between the primary substations and the MicroSCADA station and control pictures are created with DMS 600 NE. To be included in MicroSCADA alarm and event lists, it is recommended to connect all switches of the network (also the manually operated ones) to the MicroSCADA database and data transfer groups. The presentation of MicroSCADA alarms in DMS 600 WS does not require any extra engineering work. Alarm attributes are available with process object states. The following network components are parts of the data transfer between MicroSCADA and DMS 600: Primary stations Primary transformers Circuit breakers Disconnectors Feeders 16

169 Fault detectors Measurements Cross-connect these components with process object IDs from MicroSCADA in data forms of DMS 600. The position and measurement data is always transferred during the start up of DMS 600 WS and later at regular intervals. All measurement data is updated to the use of DMS 600 WS at minutes intervals depending on the settings of DMS 600 SA.(For more information about SCIL API interface settings, see.2.1, Configuring SCIL API interface.) Cross-connecting components with process object IDs Primary stations and primary transformers The data form of a primary station or a primary transformer includes a box called Scada Code. To insert a process object ID into the Scada Code field. Table Format of process object ID <logical name> :P <object type> <index> The logical name of the process object (LN), a string with a length of 1 to 10 characters. The database object type of MicroSCADA (P=process object). The type of process object. Integration supports three process object types: BI binary input DB double binary input AI analog input The index number of a process object. An integer between 1 and Circuit breakers, disconnectors, feeders and fault detectors The data forms of feeders, circuit breakers, disconnectors, and fault detectors include the Scada Code button which opens a separate dialog box for scada code definition. At start up, DMS 600 SA creates a file Scode.lst to the Data directory on the fileserver. This file contains all process objects and measurements that belong to the data transfer groups defined by the DMS Grouping Tool (For more information about the DMS 600/MicroSCADA integration functions of the DMS Grouping Tool, see Integration with SYS 600). Select All to include all the process object IDs of the data transfer groups into the list, or select Unused to include only those IDs that have not yet been selected. Select the 169

170 scada code from the list in the Select SCADA Code field. The list includes the contents of the Scode.lst file. Two different components cannot have the same scada code in DMS 600. A new selection is always compared to all other components in DMS 600 to avoid the duplication of scada code. Select File > Remote Switches Without Scadacode to generate a list of all remotely operated switches in the network database which has no defined scadacode MicroSCADA measurements The measurement process object points used in MicroSCADA correspond the quantities measured from the network process. The analogical type measurement data of Micro- SCADA can be connected to the network database of DMS 600 NE. After the connection has been defined, the process measurement values are displayed in the network window. Additionally, the measurement value is used in DMS 600 WS to make network calculations more accurate. To define the measurements: 1. Open the measurement data form. 2. Select the process object from the list in the SCADA object field. The list contains all the AI typed process objects of the data transfer groups in file Scode.lst. For more information about connecting measurements, see , General about measurements Virtual process points Manually operated switches (that is, the control type is manual, not remote) included in the DMS 600 network database can be defined as virtual process objects in the Micro- SCADA database. DMS 600 Network Editor generates a.vpc file containing the MicroScada code for all manually operated switching devices. At the same time the NE updates the database with the values of all new items. The updated fields are ScadaCode and OPCCode in the SwitchingComponent table. After the file is created and saved, the OPC Data Subscription Configuration Tool dialog is opened. Loading the OPC configuration is not possible at this point, as virtual points are not yet created on the Micro- SCADA s OPC server (OPCS.exe). After the.vpc file is used to create the virtual point to the MicroSCADA s process object database, the OPC configuration is loaded and saved, using the OPC Data Subscription Configuration Tool dialog. 170

171 The dialog generates OPC group and OPC item definitions to the Opera.opc file. The configuration for new items is now ready. The network.dat file must be updated by saving the network data for the workstation. Before creating this file, ensure the following: The control types of the switches are correct (remote control or manual control). The remote readable switches that are connected to processes have scada codes (process object IDs). They can be manually or remotely controllable. To create the virtual process points: 1. Select File > Virtual Point Export. 2. Insert the prefix for all the virtual process points. If the virtual process points are created in several steps, the prefix should be the same every time. The prefix is used to identify all virtual process points created by MicroSCADA. 3. In the VPC dialog, use the explorer view to select the location to save the.vpc file. Enter the name of the file, and click Save. 4. Enter the value for the MicroSCADA application number. Click OK. 5. Import the resulting file to MicroSCADA with the LIB 500 Application Library Virtual Point Creation Tool (for more information, see Integration with SYS 600). If the process points are not created according to the names created automatically by DMS 600 NE, the scada codes of the switches must be manually updated using the data forms of DMS 600 NE Component integration when using OPC Data Access General about component integration This chapter is valid only for Control System SYS 600 version 9.x (SYS 600) and for MicroSCADA SYS 500 version.4.5. In SYS 600 all MicroSCADA objects are exposed by the server as OPC items with codes and all the attributes of objects as OPC item properties. Communication between DMS 600 and MicroSCADA requires a connection between OPC items and DMS 600 components. The connection is made in DMS 600 NE using the configuration tool and data forms. OPC items and group information are stored to the configuration file Opera.opc. The connection of OPC items and DMS network components is made using data forms and saved to the DMS 600 database. The connection contains an OPC item as a key value, and object type and DMS network component codes as data values. 171

172 To be included in MicroSCADA alarm and event lists, it is recommended that all switches of the network, also manually operated ones, are connected to the MicroSCADA database and groups. MicroSCADA alarms presentation in DMS 600 WS does not require any extra engineering work. Alarm properties are available with item states Configuring and managing OPC Server This chapter is valid only for Control System SYS 600 version 9.0 (SYS 600) and for MicroSCADA SYS 500 version.4.5. To configure and manage the OPC Server: 1. Select Settings > OPC Configuration. The OPC Data Subscription Configuration Tool dialog opens. 2. Click Load to load an existing configuration from the Opera.opc file. 3. Define and manage the OPC Server as described in the following table: Table Fields and buttons configuring and managing OPC Server Field or button ProgId Description Defines the program of OPC DA Server. Default: ABB.MicroSCADA.OPC.Server.DA.1 Machine Defines the machine for the OPC DA connection, if not in the same computer. Otherwise empty. If the field is empty or a DMS 600 SA computer name (primary or secondary), the connection to the OPC DA server is tried first to the computer that is currently running DMS 600 SA. If this fails or DMS 600 SA is not running, the connection is tried to the computer in which DMS 600 NE is running. Connect Disconnect Load Save Creates a connection between the OPC Data Subscription Configuration Tool and the OPC DA Server. Disconnects the OPC Data Subscription Configuration Tool from the OPC DA Server. Reads existing configuration from the file Opera.opc, and creates the connection between the OPC Data Subscription Configuration Tool and the OPC DA Server. Saves configuration to file Opera.opc and sends a message about the new configuration to all DMS 600 WS and DMS 600 SA computers. 172

173 Field or button OPC 2.0 Description Defines the used OPC Server standard. If not checked, version 1.0 is used Configuring OPC group This chapter is valid only for Control System SYS 600 version 9.0 (SYS 600) and for MicroSCADA SYS 500 version.4.5. In communication with DMS 600 and MicroSCADA, OPC items will be handled as groups. To configure the OPC group: 1. Select Settings > OPC Configuration. OPC Data Subscription Configuration Tool dialog opens. 2. Click Add Group in the Groups section to add new group. The Add group dialog opens for group properties definition. To edit an existing group, select it and click Modify Group. The Modify group dialog opens for the selected group. The group is also created or modified to the OPC Server. 3. Define the following fields: Table Group definition fields Field or button Group Name Update Rate Subscribe Alarms Description Defines the unique name for the group. Defines the time cycle when event data changes of the group are updated. Time is given as milliseconds. If checked, alarm property is subscribed for all items in the group. For position types of groups properties are AL and AR. For measurement types of groups also property AZ is subscribed. Properties are not subscribed for the topology types of group alarms. Group Type Defines the item type of the group. Position: binary and double binary indication type of items. Measurement: analog measurement type of items. Topology: analog line indicator type of items. Used only for writing values to DMS 600 SA. Other: reserved for future use. 173

174 4. Use the Activate and Deactivate buttons to authorize/prohibit feedback of event data for all data in the selected group. 5. Use the Advise and Unadvise buttons to enable/disable data change events between the selected OPC group and the OPC Data Subscription Configuration Tool. 6. Click Refresh to force a data change call for all active items in the selected group. 7. Click Save. A message of the new configuration is sent to DMS 600 SA and all instanced of DMS 600 WS. To select all defined groups, click Select All. To remove a group, select the group and click Remove Group Adding OPC items to group This chapter is valid only for Control System SYS 600 version 9.0 (SYS 600) and for MicroSCADA SYS 500 version.4.5. To add an OPC item to a group: 1. Select Settings > OPC Configuration. The OPC Data Subscription Configuration Tool dialog opens. 2. Click Load. 3. Select the group from the Groups section. 4. Click Add Item in the Items section to add a new item. You can select items in the opened Add items to group dialog. 5. Select the item/items to be added to the group. Give the name manually to the OPC item field, browse the items with the tree view or search the items using the name filter options. The Filter field can include the * character. Filter text will apply only to item names (indexes), not for a full path. Click Apply to perform the search. Select This level -> Down or All items to apply filtering only to the selected level in the tree view and to the items below the level, or to all items. Use drop-down list to select filtering be applied to all, analog, binary or double binary item types. Check Unsubscribe box to select only unsubscribed items to be applied to filtering. If you want to select more than one item from the list at the same time, make selections by pressing CTRL+left mouse button or shift+left mouse button at the same time. Click Select All to select all items from the list. Remove removes the selected items from the list. See also the example below. 6. Check the Create Items as Active box to create item/items as active. If the item and group are defined to be active, the configuration tool receives data changes immediately. In some cases this can cause errors, because the configuration tool is not yet ready to handle them. Solve this by creating the 174

175 item first as inactive, or setting the group state as inactive, or unadvising the group. 7. Click Add to add the selected item/items to the group.. Click Done. 9. Use the Activate and Deactivate buttons to authorize/prohibit feedback of event data for all data in the selected item. 10. Click Save. A message of the new configuration is sent to DMS 600 SA and all DMS 600 WS. To select all defined items, click Select All. To remove the item, select the item and click Remove item. Example: Selecting all double binary state indication items with index Select the application number in tree view (for example, ROOT\APL\1). 2. Insert the filter (for example, 10). 3. Select item type using the the drop-down list (for example, Binary ). 4. Click Apply. 5. Click Select All under the results window. 6. Click Add. 7. Click Done Connecting OPC items to network components General about connecting OPC items This chapter is valid only for Control System SYS 600 version 9.0 (SYS 600) and for MicroSCADA SYS 500 version.4.5. The following network components have to be connected using OPC items: Circuit breakers Disconnectors Fault detectors Feeders (line indicator in MicroSCADA) Measurements Connect these components with OPC item codes from MicroSCADA in the data forms of DMS 600. In communication with DMS 600 and MicroSCADA, OPC items will be handled as groups. The group level properties are the update interval and the type of the group. For 175

176 the position indication types of groups, the default value of the update interval is zero and for other types 1000 ms. (For more information about setting up the OPC interface, see.2.2, Configuring OPC interface.) Circuit breakers, disconnectors, feeders and fault detectors This chapter is valid only for Control System SYS 600 version 9.0 (SYS 600) and for MicroSCADA SYS 500 version.4.5. Select Edit > OPC Codes to define the OPC item for the network component. The selection defines the usage of the configuration file Opera.opc in scada code selection. If the selection is not made, the content of Scode.lst file is used. For more information about creating the Opera.opc file, see 1.7.1, General about component integration. The data forms of circuit breakers, disconnectors, feeders and fault detectors include the Scada Code button which opens a separate dialog box for scada code definition. Select an OPC item for the network component from the drop-down list. Select All to include all the OPC items of the data transfer groups into the list or Unused to include only those items which have not yet been selected. Select the scada code from the list in the Select OPC Code field. The list includes the contents of the Opera.opc file. Two different components cannot have the same scada code in DMS 600. The new selection is always compared to all other components in DMS 600 to avoid the duplication of scada code. Select File > Remote Switches Without Scadacode to generate a list of all remotely operated switches in the network database which has no defined scadacode. When SYS 600 configuration files for switches are available, you can open the SYS 600 switch control dialog directly by selecting the remotely operated switch in the network window or the diagram or in switch device lists in DMS 600 WS. When using the Monitor Pro graphics, these configuration files are always available, but they can be created also when classic monitor graphics are used. This method uses OPC item names for switches and is available only when the OPC connection is used. With the classic monitor you can open the selected station or control picture by selecting the remotely operated switch. This picture can then be used to open the control dialog. You have control rights in the opened control dialog only if your username and password in the DMS 600 match with the user information in SYS 600 and if you are authorized to control the selected switch. 176

177 MicroSCADA measurements This chapter is valid only for Control System SYS 600 version 9.0 (SYS 600) and for MicroSCADA SYS 500 version.4.5. The measurement process object points used in MicroSCADA correspond to the quantities measured from the network process. The analogical type measurement data of MicroSCADA can be connected to a network database of DMS 600 NE. After the definition of the connection, the process measurement values can be seen in the network window. Additionally, the measurement value is used in DMS 600 WS to make the network calculations more accurate. To define the measurements: 1. Select Edit > OPC Codes. The selection defines the usage of configuration file Opera.opc in scada code selection. If the selection in not made, the content of Scode.lst file is used. 2. Open the measurement data form. 3. Select the OPC item from the list in Select OPC Code field. The list contains all the AI-typed OPC items in the file Opera.opc. For more information about connecting measurements, see , General about measurements Connecting Remote OPC with Windows Enabling of Distributed COM Use this procedure to change the DCOM settings for client and server applications: 1. Go to Start > Settings > Control Panel > Administrative Tools. 2. Select Component Services. 3. Expand Component Services > Computers. 4. Right-click My Computer. 5. Select Properties. 6. Select the Default Properties tab and check Distributed COM enabled on this computer. 7. Set the Default Authentication Level to Connect and Default Impersonation Level to Identify. When the authentication level is Connect, Windows users on remote clients must be authenticated on the server. If both computers belong to a domain, the OPC client computer must be logged in with a domain user account. If the OPC server does not belong 177

178 to a domain, the OPC client and OPC server computer must have matching user name and password to allow authentication Defining access permissions When the OPC client tries to access the OPC server, the COM security permissions defined by the Windows operating system are applied. Use this procedure to define access permissions: 1. Go to Start > Settings > Control Panel > Administrative Tools. 2. Select Component Services. 3. Expand Component Services > Computers. 4. Right-click My Computer and select Properties. 5. Select the COM Security tab. 6. In the Access Permissions pane, click Edit Limits. 7. Check Allow for both local and remote access permissions for Anonymous Logon, Everyone, Interactive, Network and System groups.. Click OK. 9. In the Access Permissions pane, click Edit Defaults. 10. Check Allow for both local and remote access permissions for Anonymous Logon, Everyone, Interactive, Network and System groups. 11. Click OK Defining launch and activation permissions When OPC client performs launch and activation towards the OPC Server, for example, automatic DCOM server start-up, the COM security permissions defined by the Windows operating system are applied. These permissions are defined in the COM Security tab of My Computer Properties dialog. Use this procedure to define launch and activation permissions: 1. Go to Start > Settings > Control Panel > Administrative Tools. 2. Select Component Services. 3. Expand Component Services > Computers. 4. Right-click My Computer and select Properties. 5. Select the COM Security tab. 6. In the Launch and Activation Permissions pane, click Edit Limits. 7. Check Allow for both local and remote access permissions for Anonymous Logon, Everyone, Interactive, Network and System groups.. Click OK. 9. In the Launch and Activation Permissions pane, click Edit Default. 10. Check Allow for both local and remote access permissions for Anonymous Logon, Everyone, Interactive, Network and System groups. 11. Click OK. 17

179 Defining DCOM settings for OPC server Each OPC server has its own DCOM settings for controlling access to this particular server. Use this procedure to define the DCOM settings for OPC server: 1. Go to Start > Settings Control Panel > Administrative Tools. 2. Click Component Services. Expand Component Services > Computers > My Computer > DCOM Config. 3. Right-click OPC Server (ABB MicroSCADA OPC DA server), and select Properties. 4. Select the General tab, set Authentication Level to Connect. 5. Select the Security tab. 6. In the Launch and Activation Permissions pane, select Customize and click Edit. 7. Allow both local and remote launch and activation permissions to Everyone, Interactive, and Network and System groups.. Click OK. 9. In the Access Permissions pane, select Customize and click Edit. 10. Allow both local and remote launch and activation permissions to Everyone, Interactive, and Network and System groups. 11. Click OK. 12. Select the Identity tab. 13. Verify that the MicroSCADA user information has been defined correctly. 14. Click OK Defining DCOM settings for OPC Server Enumerator OPC Server Enumerator (OpcEnum) is a server application used by OPC clients to find OPC servers on a computer using OPC Server names. Use this procedure to configure OpcEnum: 1. Go to Start > Settings Control Panel > Administrative Tools. 2. Click Component Services. Expand Component Services > Computers > My Computer > DCOM Config. 3. Right-click OpcEnum, and select Properties. 4. Select the General tab, set Authentication Level to Connect. 5. Select the Security tab. 6. In the Launch and Activation Permissions pane, select Customize and click Edit. 7. Allow both local and remote launch and activation permissions to Everyone, Interactive, and Network and System groups.. Click OK. 9. In the Access Permissions pane, select Customize and click Edit. 10. Allow both local and remote launch and activation permissions to Everyone, Interactive, and Network and System groups. 11. Click OK. 179

180 12. Select the Identity tab, and verify that OpcEnum is available to the user or the system account. 13. Click OK. If OpcEnum is not found from the DCOM Config list, then the component has not been installed. The installation file can be found from the following location after SYS 600 installation: \sc\setup\opc_core_components. Copy this file to the target OPC client computer, and run the Windows Installer Package file Starting OpcEnum service On the OPC server computer OPC enumerator service must be running. Use this proceedure to ensure the OPC enumerator starts: 1. Go to Start > Settings > Control Panel > Administrative Tools. 2. Open Services. 3. Right-click OpcEnum, and select Properties from the context menu. 4. Change Startup type to Automatic. 5. Click OK Local Security Policy settings Use this procedure to establish the OPC communication: 1. Go to Start > Settings > Control Panel > Administrative Tools. 2. Open Local Security Policy. 3. Expand the Security Settings > Local Policies > Security Options. 4. Right-click DCOM: Machine Access Restrictions in Security, and select Properties. 5. Click Edit Security. Allow both local and remote access permissions to Everyone, Interactive, Network and System groups. 6. Click OK. 7. Right-click DCOM: Machine Launch Restrictions in Security. and select Properties.. Click Edit Security. Allow both local and remote access permissions to Everyone, Interactive, Network and System groups. 9. Click OK. 10. Right-click Network access: Let Everyone permissions apply to anonymous users, and select Properties. 11. Select Enabled. 12. Click OK. 13. Right-click Network access: Sharing and security model for local accounts, and select Properties. 10

181 14. Select Classic - local users authenticate as themselves. 15. Click OK Data Execution Prevention (DEP) Data Execution Prevention (DEP) is a set of hardware and software technologies that perform additional checks on memory to help prevent malicious code from running on a system. DEP is used, for example, in Windows XP Service Pack 2. DEP can prevent many installations from running and it should be disabled for OPC software. 1. Right-click My Computer and select Properties. Alternatively, go to Start > Control Panel and open System. 2. Select the Advanced tab. 3. In the Performance pane, click Settings. 4. Select the Data Execution Prevention tab. 5. Select Turn on DEP for essential windows programs and services only. 6. Click OK. Restart the computer, if necessary Configuring Windows Firewall for Remote Use If other systems than MicroScada Pro SYS 600 are used, download instructions at > Downloads > White papers > Using OPC via DCOM with Windows XP Service Pack 2. Use this procedure to configure Windows Firewall to work with OPC between MicroScada Pro SYS 600 and DMS 600 applications: 1. Go to Start > Control Panel, and open Windows Firewall. 2. Select On and ensure that Don't allow exceptions is not selected. 3. Select the Exceptions tab. 4. Click Add programs. To add OPC Server Enumerator 1.10, click Browse and enter the path to OPCENUM.EXE. Click OK. This is for Micro SCADA server only. To add Micro SCADA Pro DMS Network Editor, select Network Editor. Click OK. To add Micro SCADA Pro DMS Workstation, select Workstation. Click OK. To add Micro SCADA Pro DMS Server Application, select Server Application. Click OK. Click OK. 5. Click Add port. For each port, enter the name, port number, and select TCP as shown in Table Table Exception ports Name TCP_320 Port number 320 TCP/UDP TCP 11

182 Name DCOM DMSSocketService Port number (*) TCP/UDP TCP TCP (*) is valid, if the environment variable DMSComPort has not been defined. If the DMSComPort environment variable has been defined, the port is according that value, see Figure Figure Windows Environment variables enviroment_variables.png Configuring the OPC item suffixes for fault location using OPC You need User Manager Admin rights to configure the OPC item suffixes. To configure the OPC item suffixes: 1. In the DMS 600 NE, select Settings > OPC Configuration > OPC Fault Configuration In the OPC suffix configuration dialog, enter the mandatory values. 12

183 The mandatory values are highlighted using red font color. You can edit all values. For more information of the suffixes, see Integration with SYS Click Save. 1.. Picture names General about picture names DMS 600 WS uses two kinds of station presentations: old and new style (SYS 600) station and control pictures from MicroSCADA. The new style pictures are primarily used. The administrator defines the cross-connections between MicroSCADA station and control pictures and DMS 600 stations by using DMS 600 NE. The data is saved into the network database Old style station pictures At start up, DMS 600 SA creates a file Scadapic.lst to the Data directory on the fileserver. This file contains all configured MicroSCADA station and control picture names. To define the cross-connection between MicroSCADA station and control pictures and DMS 600 stations: 1. Open the station data form. 2. Select the MicroSCADA station or control picture name from the list in the Scada picture name field. The list includes the contents of the Scadapic.lst file. All defined MicroSCADA station and control picture names are saved to the Common.prm file. Whenever a station is selected in DMS 600 WS in State Monitoring Mode, the selected MicroSCADA station or control picture is opened in the separate window of the DMS 600 WS screen New style station pictures This chapter is valid only for Control System SYS 600 version 9.x (SYS 600) and for MicroSCADA SYS 500 version.4.5. To define the cross-connection between MicroSCADA station and control pictures and DMS 600 stations: 1. Open the station data form. 2. Click Browse. Select the MicroSCADA station or control picture file (names with.v extensions). 13

184 Whenever a station is selected in DMS 600 WS in State Monitoring Mode, the selected MicroSCADA station or control picture is opened in MicroSCADA Monitor Pro Other MicroSCADA pictures Other MicroSCADA pictures (for example, alarm lists) can also be opened in DMS 600 WS when they have been defined. Select File > Open Scada Pictures to open the defined pictures. To define the other pictures: 1. Select Settings > Scada Pictures. 2. Click All possibles to select a picture from the list of all the picture names stored in the Scadapic.lst file, or click the Defined in DMS to select a picture from a list of all the picture names stored in the Common.prm file. 3. Click Add to store the selected picture name in the Common.prm file. Remove is available, if Defined in DMS is selected. Add is available, if All possibles is selected Data transfer between DMS 600 and MicroSCADA using SCIL API Periodical and spontaneous data transfer DMS 600 SA asks periodically for data of all data transfer groups. DMS 600 SA sends a data request to MicroSCADA (for example, at 20 minute intervals) for every data group. The interval between data requests depends on the data transfer intensity level of DMS 600 SA. (For more information about DMS 600 SA settings, see.2.1, Configuring SCIL API interface.) You can also define a spontaneous data transfer by using the events of MicroSCADA. The transfer method is defined by the DMS Grouping Tool (for more information, see Integration with SYS 600), where spontaneous data transfer can be defined for a group. Normally all switching state data and measurement values are defined to be updated spontaneously by using MicroSCADA events Root point coloring and load flow direction The colors of feeder root points and the load flow directions of DMS 600 WS and MicroSCADA are the same, if the feeder network components are cross-connected to MicroSCADA process objects (For more information about feeder cross-connection, see Integration with SYS 600 and , Circuit breakers, disconnectors, feeders and fault detectors.) 14

185 DMS 600 SA takes automatically care of the operations after changes in network colors or load flow and updates the MicroSCADA station and control pictures. To disable root point coloring in SYS 600: 1. Select Tools > System Tools > Busbar Coloring in MicroSCADA Monitor Pro. The Busbar Coloring Settings dialog opens. 2. Select the Coloring Modes tab. 3. Check the Allow DMS 600 to change coloring of voltage sources box. 4. Click OK Operational flows Fault case When MicroSCADA detects a new fault (numbers in the parenthesis refer to the figure): 1. The required fault data is automatically (on the basis of events) transferred to DMS 600 SA through the SSI (1). 2. DMS 600 SA creates a snapshot of the faulted feeder using the real time state of the switches and measurements just before and during the fault. The snapshot data is stored in the fault file (Fau<xxx>.txt) (2). 3. Part of the fault data (the running number of the fault, the state of the fault, and the title of the fault) is saved to the DMS 600 database (3). 4. An event alert is sent to all instances of DMS 600 WS (4). 5. DMS 600 WS reads the fault data from the fault file (5) and the DMS 600 database (6). 6. DMS 600 WS runs the fault location function. 15

186 DMS_fault_flow_a.jpg Figure An example of the operational flow when a new fault has been detected During offline state, the operator can give the initial information of the real fault, and the snapshot of the fault is created by DMS 600 WS Fault detector data change Fault detector operations during a fault situation are updated to the fault file. The states of the remote readable fault detectors are obtained from MicroSCADA. On-site readable detectors are managed by the user interface of DMS 600 WS (for more information, see Operation Manual.) The fault location function always uses the fault detector data stored in the fault files; the real time DMS 600 database stores the real time information. When MicroSCADA detects a change in the fault detector state (the numbers in the parenthesis refer to the figure): 1. The established fault detector state is automatically (on the basis of events) transferred to DMS 600 SA through the SSI (1). 2. The new state and operational time is stored in the DMS 600 database (3) and into the corresponding fault file (2)(Fau<xxx>.txt). 3. An event alert is sent to all instances of DMS 600 WS telling them to read the new fault detector state (4). 16

187 4. DMS 600 WS reads the fault detector data from the fault file (5) and the DMS 600 database (6). 5. If there is an active fault undergoing a fault location process in the instances of DMS 600 WS, the change of the fault detector state causes the fault location function to be run again with the new fault detector information. 6. A re-established remotely readable detector (state has changed from operated to non-operated) that is obtained from MicroSCADA is not updated to the fault file of DMS 600 WS, only to the DMS 600 database. Thus, all the operated states are saved in the fault files, unless the operation is updated manually from DMS 600 WS. If you change the operational state of a remote readable detector manually (for example, a wrong operation detected by DMS 600 WS has been updated), the information on the new state is stored in the fault files. Figure Operational flow for updating remote readable fault detector data DMS_detector_flow_a.jpg When the operational state of the on-site readable detectors is changed using the fault detector data form in DMS 600 WS (numbers in the parenthesis refer to the following figure): 1. The snapshot of the fault is updated by DMS 600 WS to the fault file (1) and DMS 600 database (2). 2. An event alert is sent to DMS 600 SA (3) and all instances of DMS 600 WS (4). 3. Fault data is read from the DMS 600 database to DMS 600 SA. (5) 4. Every DMS 600 WS reads the new fault detector state from fault file (6) and DMS 600 database (7). 17

188 DMS_on_site_flow_a.jpg Figure Operational flow for updating on-site readable fault detector data If DMS 600 WS is in Simulation Mode (for example, to study an old repaired fault), it asks for permission to permanently update the file. The selection always affects the network model and the fault file under simulation Updating repaired fault All the faults that have not been repaired yet are stored in the memory of DMS 600 SA and the instances of DMS 600 WS. When the fault has been repaired, it can be acknowledged as repaired in DMS 600 WS. When the fault is acknowledged to be repaired (numbers in the parenthesis refer to the figure): 1. The state of the fault is updated in the DMS 600 database (1). 2. An event alert is sent to DMS 600 SA (2) and all the other instances of DMS 600 WS (3). 3. The state of the fault is automatically updated to repaired and it is removed from the list of unrepaired faults in all instances of DMS 600 WS. 4. If there are no remaining faults, DMS 600 WS returns to State Monitoring Mode, or, if some faults do remain, it continues to the next unrepaired fault. 1

189 Figure The operational flow for updating a repaired fault DMS_on_site_flow_a.jpg Updating automatic fault isolation and restoration data Automatic fault isolation and restoration is managed from only one DMS 600 WS workstation, for more information about settings, see , Automatic fault isolation and restoration settings. A special process object is used to indicate the status of the automatic fault isolation and restoration sequence. When the automatic fault location is started, the process object is updated to -1. When the automatic fault location is stopped (not in use any more) it is updated to -2. This can be used, for example, to make events and to generate an alarm in MicroSCADA if automatic fault location is not in use. Table Meanings of automatic fault isolation and restoration sequences status process object values Process Object Value or higher Meaning No sequence running / previous sequence was successful (ready) Sequence running (set by DMS 600 WS) Error or sequence not successful (set by MicroSCADA) > Automode interrupted 19

190 DMS_repaired_flow_a.jpg Figure The operational flow for automatic fault isolation and restoration After the successful fault location of DMS 600 WS in Automatic fault isolation mode: 1. DMS 600 WS sends the request for automatic fault isolation to DMS 600 SA (1) and further to MicroSCADA (2) and sets the process object value to DMS 600 WS writes the automatic sequence to an automatic sequence file defined in the settings (3). For more information about the settings see , Automatic fault isolation and restoration settings. 3. MicroSCADA reads the automatic sequence from the file (4) 4. DMS 600 WS in Automatic fault isolation and restoration mode gets the return value of a called sequence from MicroSCADA (2 and 1) 5. If the whole sequence is run successfully and the process object value 0 is returned from MicroSCADA, DMS 600 WS continues normally and starts another restoration sequence if a new fault appears. The process object value 2 or higher indicates an error or a stopped sequence. In this case DMS 600 WS is blocked so that it cannot start another sequence before it is reset manually. During automatic fault isolation, other fault data is delivered from MicroSCADA as normally (see , Fault case) Troubleshooting DMS 600/MicroSCADA integration If you encounter a problem perform the following steps: 1. Check that DMS 600 SA, the service program of the Support System Interface (Bdu_ssiser.exe), and the Application Extension Program of the Support System Interface (Bdu_ssiaep.exe) are running on the server. 190

191 Bdu_ssiser.exe and Bdu_ssiaep.exe can only be found in the task manager process list. 2. Check that the connection to MicroSCADA is opened in DMS 600 SA. The status bar of DMS 600 SA displays a message text. 3. Check that the connection between DMS 600 SA and DMS 600 WS/DMS 600 NE is open. If there is no connection between DMS 600 SA and DMS 600 WS/DMS 600 NE, DMS 600 SA connection is broken is displayed in the alarm list of DMS 600 software. Table Troubleshooting DMS 600/MicroSCADA integration Problem Cause Application Extension Program (Bdu_ssiaep.exe) is started in the program start up, but it is soon quitted. The states of the switches in MicroSCADA are not updated in DMS 600 WS. DMS 600 WS does not open MicroSCADA station or control pictures, but opens a switching state dialog or internal station diagram. The message "Picture open request has failed" is received while trying to select a switch. The message The requested MicroSCADA picture is missing is received while trying to select a switch. DMS 600 SA cannot establish a scada connection. The automatic start up of the busbar coloring (BCU_TPSTRT:C) is called after the start up of Application Extension Program (Bdu_ssiaep.exe). It must be called before. Edit the MicroSCADA initialization command procedure APL INIT 2:C correspondingly. The process objects are not defined and/or included in the interface (SSI data transfer groups or OPC groups). For more information, see 1.6.1, Process objects and Integration with SYS 600. The scada code of the switch or scada picture name of the primary station is not defined (For more information about scada code, see 1.6.1, Process objects.) The switch is not defined and/or included in the interface (SSI data transfer groups or OPC interface). For more information, see 1.6.1, Process objects and Integration with SYS 600. If the switch is connected to a process in MicroSCADA, the picture name is not defined or the defined picture cannot be found. (For more information about picture names, see 1..1, General about picture names and Integration with SYS 600.) Check the username, password, IP address, and TCP port of DMS 600 SA settings. Check the username, password, and TCP port settings in the DMS Grouping Tool of the LIB 500 Application Library DMS Interface Package. The username, password, and TCP port settings must be the same as in DMS 600 SA. The IP address must be the same as the IP address of the computer, where DMS 600 SA runs. 191

192 Problem Cause The root point colors and power flow directions are not automatically updated to MicroSCADA. DMS 600 WS opens a monitor to a wrong MicroSCADA application. Virtual process point prefixes are given incorrectly during creation of virtual process points. The feeders do not have defined scada codes in the DMS 600 network database (For more information about scada codes, see 1.6.1, Process objects or , Circuit breakers, disconnectors, feeders and fault detectors). The root point objects have not been added to the interface (SSI data transfer groups or OPC interface). For more information, see Integration with SYS 600. The feeder process objects of the Micro- SCADA station pictures have incorrect update sources in MicroSCADA. (Should be MicroTOPOLOGY.) The color update is not allowed in Micro- SCADA (For more information, see Integration with SYS 600). Pre-defined monitors can be defined to simplify and automate the start up of MicroSCADA monitors. The MicroSCADA monitors are defined in the file Monitors.dat located in the \Sc\Sys\Active\Sys_ folder of the base system computer. Remove all codes with the incorrect prefix in the SCADACODE column of the SWITCHINGCOMPONENT table in the DMS 600 database. Update data into the screen of DMS 600 NE with the File > Update Network Database command. Remove the virtual process points also in MicroSCADA. Use the LIB 500 Application Library Virtual Point Creation Tool or remove objects straight from the process database of MicroSCADA. Define the data transfer groups again using the DMS Grouping Tool of MicroSCADA (For more information about data transfer groups, see Integration with SYS

193 19. AMR alarm settings AMR alarm setting definitions To be able to use DMS Workstation with AMR alarms, you must define settings in the following three files: AmrConf.amr file in the data directory. Created or modified manually. AMR.itm file in the data directory. Created manually or by the Network Editor OPC Configuration Tool. AMR.opc file in the data directory. Created manually or by the Network Editor OPC Configuration Tool Settings in the AmrConf.amr file The AmrConf.amr file is used to define what alarms are available in the AMR system and how these are found from the OPC server. The line 1 =.diagnostics.1.e1 in the AmrConf.amr file means that DMS Workstation will handle messages representing blown fuse cases. The value of item 1 means that the suffix for each fuse blow OPC item is.diagnostics.1.e1. This suffix is combined to each item listed in the AMR.opc file representing meters. In Figure you can see example of an OPC tag (jenergia.mp1.diagnostics.1.e1) used for detecting fuse blows. Figure OPC tag suffix example OPC_item_suffix.jpg 1 2 Subscribed OPC tag Suffix definition for Fuse blow cases Define each item used using running sequence numbering. If some event is not used, define the number but leave the value empty. The following is an example of acceptable configuration, where event 2 (zero line cut) is ignored: 193

194 // blown fuse 1=.diagnostics.blown_fuse.E1 // zero line cut 2= // rotation error 3=.diagnostics.rotation_error.E3 [Events] block values The following is an example of [Events] block values in the AmrConf.amr file. // SulakePalo / blown fuse 1=.diagnostics.blown_fuse.E1 // Nollajohdin poikki / zero line cut 2=.diagnostics.zero_line_cut.E2 // Kiertosuunta vaihtunut / rotation error 3=.diagnostics.rotation_error.E3 // Keskijännitejohdin poikki / medium_voltage_line_cut 4=.diagnostics.medium_voltage_line_cut. E4 // Alijännite / under voltage alert 5=.diagnostics.under_voltage_alert.E5 // Ylijännite / over voltage alert 6=.diagnostics.over_voltage_alert.E6 // Alijännite laukaisu / under voltage action 194

195 7=.diagnostics.under_voltage_action.E7 // Ylijännite laukaisu / over voltage action =.diagnostics.over_voltage_action.e // Katkaisulaitteen tila / switch state ( currently not in use ) 9= // Automaattisulake I> / automatic fuse lower limit I> 10=.diagnostics.automatic_fuse_lower_limit.E10 // Automaattisulake I>> / automatic fuse upper limit I>> 11=.diagnostics.automatic_fuse_upper_limit.E11 // Jännitekatko / Outage ( currently not in use ) 12= [Settings] block values The [Settings] block follows the same formula as in Figure You can add as many settings as needed. It is also possible to define a description text ( D + number of the setting ) and value range ( R + number of the setting ) for each setting. The settings numbering must be continuous. The following is an example of [Settings] block settings: [Settings] 1=.diagnostics.broken_fuse.S1 D1=Broken fuse alarm active/not active (0=not, 1= logging, 2= alarm active, 4= switch active) R1=

196 [Measurements] block values The [Measurements] block follows the same formula as in Figure The number of measurements is not restricted. Each measurement can have a description definition (D + number of the setting). The following is an example [Measurements] block values: [Measurements] 1=.measurements.I1 D1=Phase voltage U1 2=.measurements.I5 D2=Phase current I OPC settings in the common.prm file You can define the common AMR OPC server settings in the parameters in the common.prm file. These settings are mandatory for the DMS Workstations to successfully create a connection to the AMR OPC server. You can define the settings manually, or they can be created automatically by using DMS Network Editors OPC Data Subscription Configuration Tool. The parameter OPCServer may be empty indicating that the local machine will be used. [AMR_Settings] OPCServer=FIXXX-X-4XXXXXX OPCProgId=AMRSystem.OPCServer AMR communication settings In the AMR environment, only one DMS Workstation instance is responsible of automatically managing the fault situations. This covers all related calculations and the loading of required low voltage networks into memory. This specific instance is called the AMR Fault Administrator. All other instances of the DMS Workstations simply listen to the messages sent by the AMR Fault Administrator. 196

197 For the AMR Fault Administrator definition, define one additional setting manually into the common.prm file under the AMR_SETTINGS section by giving the computer name or ip-address. AMRFaultAdmin=FIXX-X-XXXXXX OPC item subscription You can subscribe OPC items manually, or using DMS Network Editors OPC Data Subscription Configuration Tool. To subscribe an OPC item: 1. In the DMS 600 NE, select Settings > OPC Configuration > OPC Configuration In the OPC Data Subscription Configuration Tool dialog, select the AMR configuration check box. The application makes a difference between AMR and normal OPC configuration. The functionality has the following exceptions compared to making a normal OPC client configuration: The state group functionality is irrelevant to the AMR configuration. The items added to the AMR group are normally not actually added to the OPC server because they are not fully qualified OPC tags. Activate/Deactivate OPC items are not functional. The reason is the same as above, thus it is not possible to see the active value of these OPC tags. 3. Create the OPC group, and add items to it. For more information, see 1.7.3, Configuring OPC group and 1.7.4, Adding OPC items to group. 4. To speed up things, you can select the Reversed selection check box. This action reverses the behavior of the OPC namespace browsing. You can now select OPC branches instead of OPC leafs. The subscription of OPC branches may be rejected by the OPC server. In this case, the selection is forced even though it did not succeed on the OPC server level. 5. Click Add, and Close. 6. Click Save to save the active AMR OPC configuration. The application asks if you want to delete all customer links that are no longer valid from the database. This is because the OPC item is no longer included in the subscribed OPC items. 7. If you want the customer linking to subscribed items to be done automatically, click Yes. This functionality resolves all matching meter and customer names, and the entries are added directly to the database. After all subscribed items have been looped, items that were not linked are listed in a dialog box. This option is applicable if the metering point numbers and the customer 197

198 service points codes are exactly the same. Otherwise, they need to be linked manually, see 19.6, Linking subscriptions to a customer. If the meter number is changed, or if the meter cannot be used in the DMS integration anymore, remove the item Linking subscriptions to a customer The application uses one database table explicitly for AMR mapping. The name of the table is AMR_OPC_CODES and it is located in the Network database. The table consists of the following four text fields: Code,, Size 32, required (may not be null) CustomerNode,, Size 50 OPCCode,, Size 255 LV_Network,, Size 50 If the meter ids in the AMR system are the same as the customer (meter) ids in the DMS database, DMS NE can generate the links automatically when the AMR OPC Configuration is saved. Otherwise, create the links for meters and OPC codes manually in the customer data form as follows: 1. In the Consumer node dialog, click Customer OPC node. Figure Consumer node dialog Consumer_node.jpg 19

199 The OPC mapping is done the same way as defining OPC/Scada codes for switching devices. 2. Select the OPC code from the drop-down list. By leaving the field empty the existing definition is removed. 3. Click OK AMR alarm symbol Symbols for active AMR alarm are defined in the same way as all other True Type symbols. The item reserved for this use is called AMR alarm. The AMR alarms are drawn using blinking symbols. Use other color than red as the font color, because the default color used for blinking is red. The network data must be saved before AMR alarm symbols can be used by DMS Workstations Integration of AMR alarm to SYS 600 It is possible to integrate AMR alarms to the SYS 600 event and alarm lists by using the process object LV_ALARM (PJ_HALYTYS in Finnish). Create the process object to the application with desired alarm generation and event attributes. The following is an example of used BI-type indexes with OI attribute. IX OI LV LV LV MV LV FUSEBLOWN ZEROCOND BROKEN ROTATION ERROR COND BROKEN UNDERVOLTAGE 199