Intellution Ifix 3 0 Manual Transmission
Abstract Modern substation automation involves integrating IEC 61850 compliant IEDs and noncompliant energy meters with an already-existing multi-vendor SCADA at the station level. Due to the lack of knowledge toward the IEC 61850 standard, it is difficult to write applications for reading and processing data from IEDs. Therefore, utilities either have to replace the older applications with IEC 61850 compliant ones or use protocol converters to acquire data from IEDs and to exchange the data with other applications. This article presents an approach for an interoperable framework of SCADA with IEC61850 compliant IEDs and non-IEC61850 energy meters for accessing data. The data are stored in an open file format that can be accessed by any other application at the station level with minimal engineering efforts.
To integrate a non-IEC61850 energy meter with the SCADA, an AMI head-end application is developed that also stores the data in an open file format. The implemented methodology allows retaining the SCADA, a non-IEC61850 compliant application, while opting for IEC61850-based substation automation systems. Abbreviations ACSI Abstract Communication Service Interface AMI Advanced Metering Infrastructure DO Data Object HMI Human–machine Interface IEC International Electrotechnical Commission IED Intelligent Electronic Device LN Logical node MMS Manufacturing Message Specification MVL MMS-Virtual-Lite OPC Object Linking and Embedding (OLE) for Process Control SCADA Supervisory Control and Data Acquisition VMD Virtual Manufacturing Device XML Extensible Markup Language XSLT Extensible Style Sheet Language Transformations. Manufacturing Message Specification in IEC61850 MMS is an international application-layer protocol for exchanging or transferring information among real devices such as IEDs and the computer applications. Communication Networks and Systems in Substations – Part 8-1: Specific Communication Service Mapping (SCSM)—Mappings to MMS (ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3, IEC 61850-8-1, 2004–05. MMS plays an important role in mapping the services of abstract communication service interface (ACSI) models of IEC61850 to the lower level and vice versa so that all the IEDs respond in the same fashion from the network point of view. This is because services provided by ACSI in IEC 68150-7-2 cannot be used directly to make communication with another device over a network.
Therefore, the objective of MMS is to specify how physical devices shall operate when the messages are received to make the communication between the devices vendor independent. For example, services provided by MMS enable the MMS-compliant device to read the variables from different MMS-compliant devices because the MMS services (e.g., read, write) and messages exchanged are identical. T.; Jaatun, M. An Analysis of the Manufacturing Messaging Specification Protocol. 5th International Conference on Ubiquitous Intelligence in Computing, 2008, 602– 615. Using a range of services, MMS provides an ability to define and explore the functionalities and capabilities of IEDs for exchanging data between the intelligent devices and other utility applications. For better clarity, a visual representation depicting an analogy between MMS and telephone communication is created in.
A caller, as shown in, speaking in the language “French” is assumed as an “MMS client” who wants to communicate with an international receiver in the United States. The communication between the French caller and the U.S. Receiver is possible only if both understand a common language, French or English. If not, then one of them has to use a local language translator, which is equivalent to a virtual manufacturing device (VMD) to ensure the correct delivery of messages between them. Therefore, VMD plays the role of language translator that provides an abstraction layer to hide the internal functionalities of real physical devices from the external environment.
The main objective of VMD is to define the following three things Communication Networks and Systems in Substations – Part 7-4: Basic Communication Structure for Substation and Feeder Equipment—Compatible Logical Node Classes and Data Classes, IEC 61850-7-4, 2004–05.:. Objects: MMS objects are the variables defined in the server device (IED). These objects provide capabilities for accessing operational, control, and other parameters defined in a physical IED. In short, MMS objects enable the client application to see what is happening inside the IED. Services: Client device or application uses various MMS services such as Read, Write, Start, Stop, and so on to manipulate the objects or to obtain the status information of the objects defined in the physical IED. Behavior: When the client device sends a service request for an object to the server, the way the server responds upon receiving the service request is called behavior. For exchanging the information between the IEC61850-compliant devices and applications, a client/server scheme is used in MMS for non-time-critical applications, which is a connection-oriented protocol.
With the client/server scheme, a client application can perform read/write operations with an IEC61850 IED only after establishing a connection with the IED described in. Some of the advantages gained by connection-oriented protocol are as follows:. It provides an acknowledgment message upon exchanging the information successfully;. Because of the acknowledgment message, read/write/start/stop and other services are more reliable; and.
Ge Intellution Ifix
It supports encoding and decoding of information from security point of view. Hierarchical Data Model of IEC61850-Based IED To establish communication between a client program and an IEC61850-based IED, it is important to understand the data model of the IED.
As the standard IEC61850 follows an object-oriented approach, it is not possible to read data of a particular object until their root nodes and subsequent nodes nomenclature is not known. The IEC61850 standard defines a number of logical nodes (LNs) to provide various virtual functionalities for representing the operations of physical devices. A virtual representation of logical devices and logical nodes of an IED correlating the physical breaker and voltage transformer is depicted in.
Instances of a circuit breaker (XCBRs) are represented as LNs, which further comprises data objects (DOs) representing variables related to status, measured and control value, and some other information of a physical IED. These data objects further provide the actual value of status, measurement settings, and other information. The standard IEC61850 has categorized all the LNs into 13 logical groups as shown in. MMS-EASE Lite: IEC 61850 for Embedded Systems. (accessed Nov. Thus, by reading the initial first character of a logical node, it is easy to identify the functionalities of that logical node.
This article is focused on metering aspects and that is why the logical node MMXU is selected. For example, in an instance MMXU1, as shown in, “M” indicates that the logical node is meant for measurement related functions. This logical node is used for measuring voltage, current, power, frequency, impedance, and so on in a three-phase system. Similarly, based on the application functional requirements, a particular logical node can be selected from.
Interoperable Framework of SCADA shows an interoperable framework of SCADA for accessing data from IEC61850-based application/IED and non-IEC61850 based application/energy meter. The configured framework operates on Ethernet layer and employs the following applications/devices:.
MMS client source code, i.e., MMS-EASE Lite (a Sisco product Thomas. S.; Ali, I.; Gupta, N. Interoperability Framework for Data Exchange between Legacy and Advanced Metering Infrastructure. Policy 2012, 2, 49– 59. ), is an IEC61850-compliant application. Hereinafter, the IEC61850-based MMS client source code will be called a “client program.”.
IEDs 1-n, as shown in, are IEC61850 relay IEDs. A server running an AMI head-end application developed in Ref. ModSim32-Application Description. (accessed Oct.
For fetching energy parameters from a network of ModSim32 virtual energy meters, which is a simulated version of non-IEC61850 meters supporting MODBUS TCP/IP protocol. Versatile Software Tool for Working with IEC 61850 Devices.
(accessed Oct. The network of energy meters are also connected to the station level. IEDScout application CMC256plus. High Precision Relay Test Set and Universal Calibrator. (accessed Oct. Is used to determine various domain names, logical nodes, and their attributes defined in IEC61850 IED so that they can be called correctly inside the client program while establishing the communication with IEC61850 IED. Hardware CMC 256plus Vijeo Citect.
10 Things You Should Know About SCADA. (accessed Nov. Plays the role of a field device and is used to provide test signals to IEC61850 relay IEDs. Vijeo Citect SCADA Vijeo Citect. 10 Things You Should Know About SCADA. (accessed Nov. Is an industrial process SCADA, i.e., a non-IEC61850 application used for accessing the data from IEC61850 IED and non-IEC61850 energy meter.
Shows the schematic of the laboratory setup that is used in implementing the proposed methodology and is available at the Substation Automation Laboratory of Jamia Millia Islamia University, New Delhi, India. The process level in the test setup is represented by the CMC 256plus test set, the bay level is represented by the relay IED, and the station level, where different applications and databases are running, is represented by the computer. The notable functionalities of the proposed methodology to achieve interoperability will be discussed next. 4.1 XML Storage Data extracted by the client program from IEC61850 IED and the data extracted by an AMI head-end application ModSim32-Application Description. (accessed Oct. From non-IEC61850 energy meters are wrapped into XML tags, which is software or hardware independent. The benefit of wrapping the data in XML tags is that it describes the structure of data in a natural language, which a user can easily understand.
A partial representation of a stored XML database created by the client program for IEC61850 IED is shown in the. The stored database refers to very simple XML relational database schema consisting of the following four levels:. IEDDatabase: the root element of the database. IEDReading and IEDMetadata: represents the elements of the database tables,.
DateTime, Voltage, Current, and other elements: represents the database records,. IEDVoltageAB, IEDVoltageAC, and IEDVoltageA: represents the database fields. Using this relational structure, the client program can add other tables, records, and fields with values. The format structure of the created storage is simple and easy to understand.
Thus it provides access to non-IEC61850 applications, to fetch data from IEC61850 IEDs, without needing the cooperation from different vendors for performing the various operations such as data extraction, data transformation, and data presentation. For fetching the IED parameters, a communication profile needs to be established between the client program and IEC61850 IED, which is described in the next section. An XML database for non-IEC61850 energy meters is being created by the AMI head-end application. ModSim32-Application Description.
(accessed Oct. To store data in a XML format, a data storage routine is being called by the developed AMI head-end application for non-IEC61850 energy meters where data is stored with the following information (i) date and time, (ii) meter model, (iii) location of the installed meter, and (iv) parameter’s value. This information helps in tracking the historical values of any parameter of interest.
The history of the logged parameters enables the utilities to generate bills, calculate load profiles, or do other analysis for taking certain actions. Also, the same AMI head-end application, which is Modbus TCP/IP compliant, can also access the database of IEC61850 IED without any protocol converter. Once the values are stored in the XML database, the utilities can share the XML database with their customers, allowing them to use their own extensible style sheet language transformations (XSLT) language for processing the XML database and displaying the parameters in the form of a Web page. Open database (i.e., XML) is used due to the following advantages:.
Easy to understand and any kind of data processing/analysis. This helps utilities in retaining SCADA for accessing data from IEC61850 IEDs without using protocol converters or OPC servers. Non-SCADA applications such as XSLT language can be used to present or process the XML data to remote users via a Web page. Using XML storage, applications can query/access the particular parameters directly from the XML database instead of sending the requests to the devices; therefore, it reduces traffic congestion at the bay level. 4.2 MMS Client-Server Communication The MMS client provides a high-level program interface layer referred to as MMS-Virtual-Lite (MVL), which is closely coupled to the lower layer subsystem components and provides an application framework that is suitable for client applications. For client applications, MVL provides easy-to-use API hooks for performing various operations such as MMS connection control and MMS read/write services. MVL supports VMD to provide a straightforward mechanism by which variables defined in the IED can be accessed.
Thus users are not required to write their own MMS programs from scratch for fetching data from IEC61850-based IEDs/devices. As discussed in, VMD provides an abstraction layer for an external world to hide the internal functionalities of a real physical IED/server. Therefore, a plurality of object models of IEC61850 are mapped to specific MMS objects as shown in. For instance, the IED server is mapped to MMS VMD, logical device object is mapped to MMS domain, logical name is mapped to MMS named variable, and data are mapped to named variable type description. Such a mapping is helpful in establishing the communication between the MMS client application and the IEC61850-based server device/IED. A communication flow for reading the IED energy parameters, e.g., frequency (Hz), using the client program is created in. While establishing connection with the remote server device, i.e., SIPROTEC 7SJ64 (IEC61850 IED), the client program uses a function domvartypeidcreate to send a request to the IED server with following parameters:.
A network connection information, to specify the remote server to which the MMS protocol data unit (PDU) is to be sent, or from which the PDU will be received. A particular variable name, e.g., MMXU 1$M X$H z$mag, whose value need to be accessed.
The format of calling the variable, e.g., variable “mag” as shown in, in the client program has the following parts:. “MMXU1” is an instance of the logical node (LN) class MMXU,. “MX” is a functional constraint related with measurement functionality. Functional constraint depicts the services that are possible for a particular DataAttributeComponent (DA). “Hz” is DataObjectComponent (DO), and.
“mag” is a DA representing the magnitude of the complex value. The function domvartypeidcreate called in the client program returns the type for any domain-specific variable and creates a unique type identifier (ID) that is used as an input to access the particular variables in the function namedvarread.
For every variable, a unique type ID is created. Once the function namedvarread is called, the client program waits for 1 second to get the server response. The waiting time for listening the server response can be varied by setting the “Timeout” parameter in the function namedvarread.
The behavior of the IED/server involves receiving the read request from the client program and processing the information to send the response (+ve response) or an error code (-ve response) back to the client program. Once the client program receives a positive response from the server, the client program polls the desired electrical parameters and stores the parameters’ value in an interoperable XML data source, as shown in, by calling an XML data storage routine similar to as provided in Ref.
Kezunovic, M. Smart Fault Location for Smart Grids. Smart Grid 2011, 2, 11– 22., In the experimental test setup, the client program (coded using MMS-EASE Lite) is customized to read and store the parameter values, i.e., Voltage for phase AB, Voltage for phase A, Current for phase A, and Frequency from IEC61850 IED in an XML data source different from the data source of energy meters.
The output of the client program is shown in. 4.3 Validation of Interoperability Using Non-IEC 61850 SCADA Vijeo Citect process SCADA, Vijeo Citect. 10 Things You Should Know About SCADA. (accessed Nov. A non-IEC61850 application, is used to validate the interoperability demonstration at the station level. This SCADA application fetches data from IEC61850 IEDs through the XML database and is implemented using Cicode, which is a scripting language similar to C language.
For validation of the interoperable framework concept, authors of this article have customized the Cicode in order to monitor the field devices. Cicode supports a multitasking and multithreading environment to interface with the plurality of XML data sources, where the energy data of IEC61850-based IED and non-IEC61850 energy meters are stored, for accessing real-time information. Shows an architecture where SCADA application needs to extract parameters from IEC61850 IEDs and also from non-IEC 61850 energy meters. The HMI of process SCADA in a tabular form is demonstrated in, where the left portion shows the value of parameters extracted from an XML data source of the IEC61850-based IED, and the right portion shows the value of parameters extracted from another XML data source of the simulated energy meter. Most of the SCADA/HMI vendors have their own scripting languages. Shows a list of major SCADA vendors, widely used in industrial applications, named with their scripting platform that can be easily customized to parse the XML data sources.
Functionality of these scripting platforms is similar to the Cicode scripting language used in this article. The Web service provides an abstraction to the remote client applications.
This abstraction helps in making the system more robust in terms of accessing the parameters of IEC61850-based IEDs or non-IEC61850 energy meters with minimal engineering efforts. Database platforms (e.g. SQL, DB2, MS Access, MySQL, Oracle, Excel) can use schema/data conversion tools to import data from the open file format, made available to the client application using the Web service, for generating bills, reports, etc. Thus this section demonstrates an interoperable framework for accessing metering data through an open file format and making it interoperable and accessible to multi-vendor utility applications. Following are the advantages of the demonstrated interoperable framework, and they are compared in with other published work.
Data from IEC61850-compliant IEDs and energy meters are accessible to traditional SCADA/HMI without needing the protocol converter or OPC interface. All types of third-party applications (Industrial SCADA or Enterprise Application) running at the station level can fetch data from XML-based platform independent storage, which was not possible earlier because of proprietary database. XML storage can support simultaneous and multiple connections with applications at the station level that help in reducing the traffic of reading the data from IEDs/meters directly.
For remote metering, Web services can be customized to tailor the data as per the user’s need. Conclusion This article presents an implementation for achieving interoperability among the applications at the station level for extracting data of IEC61850-based IEDs and non-IEC 61850 energy meters.
To demonstrate this approach for interoperability, the source code of the IEC61850-compliant application (client program) is used and customized to fetch data from a physical IEC61850 IED and stored in XML format. To integrate a non-IEC 61850 energy meter, an AMI head-end application is developed to fetch data and is used for storing the parameter values in a different XML database. The approach demonstrated in this article helps non-IEC61850 compliant applications at the station level such as SCADA or any other scripting applications in accessing the open file format to read IED or energy meter data without a protocol converter and thus avoids unnecessary delay and cost. Igi 5 pc download. Moreover, a detailed insight of a MMS model and communication profile between client and server is provided to help practicing engineers and researchers to customize the IEC61850 client program as per the requirements.
Web service has helped in demonstrating the remote metering, which enable consumers/utilities to design their own reporting templates to display fetched data. A Comparison of demonstrated framework of this article with other published work. SYNC SYNC 2000, Field IO and Communication Gateway. (accessed Nov. Yoo, B.-K.; Yang, S.-H.; Yang, H.-S.; Kim, W.-Y.; Jeong, Y.-S.; Han, B.-M.; Jang, K.-S.
Communication Architecture of the IEC 61850-based Micro Grid System. 2011, 6, 605– 612., Crispino et al. Crispino, F.; Villacorta, C. A.; Oliveira, P. P.; Jardini, J.
A.; Magrini, L. An Experiment Using an Object-oriented Standard—IEC 61850 to Integrate IEDs Systems in Substations. IEEE/PES Transmission and Distribution Conference and Exposition: Latin America 2004, 22– 27. Srinivasan et al. Seshadhri, S.; Kumar, R.; Vain, J. Integration of IEC 61850 and OPC UA for Smart Grid Automation. IEEE Conference on Innovative Smart Grid Technologies-Asia (ISGT Asia) 2013, 1– 5.
Chang, J.; Vincent, B.; Reynen, M. Protection and control system upgrade based on IEC- 61850 and PRP. 67th IEEE Annual Conference for Protective Relay Engineers 2014, 496– 517. Demonstrated framework Is protocol converter required? Yes Yes NA NA NA No, Protocol converter and OPC interface both are not required Is OPC client-server interface required? NA NA Yes Yes Yes Does it support IEC61850 compliant IED and noncompliant meters?
Yes, it supports both the devices Supports only IEC61850 based IEDs Supports only IEC61850 based IEDs Supports only IEC61850 based IEDs Supports only IEC61850 based IEDs Yes, the framework is applicable for IEC61850 compliant IEDs and noncompliant meters Does it support integration (interoperability) with 3rd party applications, e.g., billing application, XSLT? A detailed understanding of protocol converter is required for integrating the 3rd party applications No No No No Yes, 3rd party application can be integrated easily. Users need to understand only XML schema that is user friendly and is not a proprietary schema. Does it provide remote data access in the form of a Web service?
No, only remote configuration is supported for maintenance purpose No No No Yes, remote access is provided but not as a Web service Yes, the demonstrated Web service is generic and any 3rd party application can call this service for accessing data.