WO2018062611A1 - Method for constructing general-purpose operating system applicable to various microgrids and power distribution systems, and operating system constructed thereby - Google Patents

Abstract

The present invention provides a method for constructing a general-purpose operating system applicable to various microgrids and power distribution systems, wherein the method comprises: configuring solution modules for operating a microgrid or power distribution system; extracting solution modules, which satisfy an operational purpose, a system configuration scheme, and a server structure of the microgrid or power distribution system, from the configured solution modules; and deriving a final operating system by combining the extracted solution modules. The present invention can be extensively applied to various types of microgrids and power distribution systems which are different in end user type, system morphology, scale, and the like.

Description

General operating system construction method applicable to various microgrids and distribution systems and operating system constructed by the same

The present invention relates to a method of constructing an operating system that is universally applicable to various types of microgrids and distribution systems, and to an operating system constructed thereby.

Microgrids, depending on the size and scope of their application, can be linked to on-premises customers (buildings, factories, campuses, etc.), small (e.g. households) and large (e.g. Ulleungdo) islands, and some areas of the distribution system. Or the like.

If different operating systems have to be developed and applied according to these various applications and their operation methods, there are many problems in actual commercialization.

In general, a microgrid operating system is largely a) a platform that acquires information from a terminal device or a local controller, processes it into the required information, and finally delivers the information to a computing device (usually software) that derives a solution ( platform), 2) an application that receives this information and generates final control values (to be delivered to the user or to a device or device) by internal logic, and 3) manages the model of the overall structure. In addition, it can be divided into a data management system (DBMS) that supplies data modeled for the platform or application to perform its functions.

The data management system may be a management system for large-scale database processing such as Oracle, MS-SQL, etc., which we usually use, or in the case of a very small single bus structure (1 bus type) microgrid, it may be managed as a file. have.

Various existing technologies related to operating systems such as microgrids have the following problems.

The prior art is systems for application to microgrids and large-scale distribution systems of a particular shape or scale.

In other words, the technology applied to microgrids having a single busbar system structure does not consider a part of a distribution system or a large island. In addition, in the case of a technique for applying to a large distribution system, it cannot be considered to apply to a small microgrid.

Therefore, there is only a technology that can be applied only to a specific type of target system, and if the existing technology is applied, the system must be newly developed for each application, which is difficult economically and timely.

In addition, various types of targets (consumers (buildings, factories, campuses), communities (area scale), some areas of the distribution system, etc.), types of systems (small linked, large linked, small independent, large independent) and scale It does not present an operating system for common application.

Therefore, the operating system must then be rebuilt according to the target, which is very inefficient and lossy in terms of economics.

In addition, when solutions are hierarchically connected, the configuration of the entire system must be changed in order to mount a solution for another purpose.

The matters described in the background art are provided to help the understanding of the background of the invention, and may include matters that are not already known to those skilled in the art.

The present invention has been made to solve the above-described problems, the present invention is to build an operating system that can be universally applied to various types of microgrids and distribution systems that differ in the type, scale, etc. of the target type Its purpose is to provide a method and an operating system built thereby.

The general purpose operating system construction method applicable to various microgrids and distribution systems according to an aspect of the present invention comprises a solution module for operating a microgrid or a distribution system, and the microgrid or distribution system among the configured solution modules. It is implemented by extracting a solution module that satisfies the operation purpose, system configuration, and server structure, and combining the extracted solution modules to derive the final operating system.

The application program mounted on the final operating system may be selectively applicable to the functions required for the microgrid or the distribution system.

The solution module for operating the microgrid or the distribution system includes: a node monitoring unit for monitoring a process processing unit, a data management unit for generating, modifying and deleting data stored in a database, and a data processing unit for processing measured and calculated data , An application manager for managing driving of the driven application program, a terminal data processor for processing data collected from a system, an external data processor for managing data received from an external system, a screen processor for displaying an operating system status, and a database It characterized in that the plurality of solution modules selected from the report management unit for creating and editing the report using.

Each of the plurality of solution modules is modular, characterized in that the operating system to build the removable system.

In addition, data linkage between the solution modules may be performed through middleware provided on a separate memory.

According to an aspect of the present invention, a general-purpose operating system applicable to various microgrids and distribution systems includes a plurality of solution modules for operating a microgrid or a distribution system, an operation purpose of the microgrid or a distribution system, and a system configuration method. And selectively coupled to suit the structure of the server.

The application program may further include an application program to which the function required for the microgrid or the distribution system is selectively applied.

The solution module manages the operation of a node monitoring unit for monitoring a process processor configured, a data management unit for generating, modifying and deleting data stored in a database, a data processing unit for processing measured and calculated data, and a running application program. To create and edit reports using an application program management unit, a terminal data processing unit processing data collected from a system, an external data processing unit managing data received from an external system, a screen processing unit displaying a state of an operating system, and a database. A plurality of report management units may be selected.

The plurality of solution modules are each modular, characterized in that the removable to the operating system.

In addition, the processor may further include middleware provided on a separate memory and performing data linkage between the solution modules.

On the other hand, for linked microgrid systems such as factories and buildings whose output stabilization and peak reduction are based on renewable power generation and ESS schedule control, the Eng / common element module for collecting terminal data and processing of measurement data The data processing module and the screen processing module for monitoring the device are selectively combined, and application programs for load and power generation prediction and ESS scheduling are applied.

In addition, for community-type microgrid system that aims to reduce peaks by independent operation in emergency and ESS schedule control, Eng / common element module for processing database and collection of terminal data, processing of measurement data and historical data The data processing module and the screen processing module for monitoring the device are selectively combined, and application programs for topology processing, fault processing, load and power generation prediction, and ESS scheduling are applied.

Or, for small independent microgrid systems whose purpose is to maintain frequency stability through ESS schedule control and generation and load control, and to reduce power generation fuel cost by increasing renewable capacity, Eng / common element for collecting terminal data. The module and the data processing module for the processing of the measurement data and the screen processing module for monitoring of the device are selectively combined, and application programs for load and power generation prediction and ESS scheduling are applied.

In addition, for large-scale standalone microgrid systems whose purpose is to maintain frequency stability and to handle faults in power systems through ESS schedule control, generation and load control, Eng / Common element modules for database management and terminal data collection. The data processing module for processing measurement data and historical data and data synchronization and the screen processing module for monitoring of the device are selectively combined, and application programs for topology processing, troubleshooting, load and power generation prediction, and ESS scheduling are applied. It is characterized by.

In addition, for the distribution automation system for the purpose of remote monitoring and fault handling of the distribution system, it is necessary to process the data and the synchronization of the Eng / Common element module for the database management, the collection of the terminal data and the node monitoring, the measurement data and the historical data. It is characterized in that the data processing module and the screen processing module for monitoring the device is selectively coupled.

In addition, for the DMS system which aims to optimize the distribution system optimization using an application program, the Eng / Common element module for database management, terminal data collection and node monitoring, processing of data and historical data, and data synchronization are performed. The data processing module and the screen processing module for monitoring the device are selectively combined, and applications for topology processing, system operation and control, load and power generation prediction, and ESS scheduling are applied.

According to the method for constructing a general-purpose operating system applicable to various microgrids and distribution systems according to the present invention, and the operating system constructed thereby, an operating system that can be universally applied to distribution systems and microgrids (independent type, linked type, etc.) It is possible to build.

The operating system constructed by the present invention is a component can be modularized and detachable (plug-in / out) as necessary, various target types (consumers (building, factory, campus), community (Area scale), distribution system) In some areas, etc.), system type (small chain type, large scale linked type, small scale standalone type, large scale standalone type) and scale, so that it is not necessary to rebuild the operating system according to the target object. great.

In addition, unlike the conventional solution (application-based) in the case of modular and removable, so that can be freely selected and used according to the purpose and configuration of the target system.

In addition, the operating system must secure the continuity of operation by quickly reflecting the change history of some systems. For this purpose, other elements in the system can be directly modified (add / delete / change data) by the operator of the DB without any change. This maintenance is easy.

1 illustrates a method for constructing a general-purpose operating system applicable to various microgrids and distribution systems according to the present invention.

Figure 2 shows the structure of a universal operating system applicable to various microgrids and distribution systems of the present invention.

3 is a form of a modular structure by linking each module and the middleware memory of the present invention.

Figure 4 shows the operation flow of the node monitoring unit constituting the operating system of the present invention.

5 is a flowchart illustrating the operation of the data management unit constituting the operating system of the present invention.

6 is a flowchart illustrating an operation of a data processing unit constituting an operating system of the present invention.

7 illustrates a detailed configuration and operation principle of an application program management unit constituting the operating system of the present invention.

8 is a flowchart illustrating the operation of the terminal data processing unit constituting the operating system of the present invention.

9 is a flowchart illustrating the operation of the screen processing unit constituting the operating system of the present invention.

FIG. 10 illustrates a more detailed operation flow of the screen processor of FIG. 9.

11 and 12 illustrate life and death screening and lineage reconstruction.

13 illustrates a troubleshooting process.

In order to fully understand the present invention, the operational advantages of the present invention, and the objects achieved by the practice of the present invention, reference should be made to the accompanying drawings which illustrate preferred embodiments of the present invention and the contents described in the accompanying drawings.

In describing the preferred embodiment of the present invention, well-known techniques or repeated descriptions that may unnecessarily obscure the subject matter of the present invention will be shortened or omitted.

The prior art described above does not have universal applicability for the following reasons.

1) In order to have universal applicability, all should be applicable regardless of the topology structure of the system (single bus or multiple bus). For example, in the case of the linked microgrid, which was constructed on the premises of the Power Research Institute in 2010, and the stand-alone microgrid, which was constructed in Gaza, Jeollanam-do in 2014, was a single bus structure in which multiple generators and loads were combined in one bus. On the other hand, systems for general distribution system operation and large independent microgrids such as Ulleungdo are multi-bus structures.

Thus, there is a need for a data management and platform that can accommodate any type of system topology.

2) Having universal applicability does not mean that all applications that derive the solution are identical. However, this means that there is a data management system composed of common facility models, and is configured to accommodate various applications required for the operation of microgrids and distribution systems for different purposes.

If the necessary application program can be selected and used according to the operation purpose of the target system, it can be applied to various microgrid and distribution system operation.

3) Various components for operating system platform and application program must be configured independently of each other so that it can be plug-in / out to fit various types of systems as mentioned in 1). This is possible only if the operating system is modulated.

4) An operating system that is developed and applied once requires maintenance on a periodic and aperiodic basis. The most frequent of these items is data management (data addition / deletion / change).

Therefore, a general purpose operating system must provide a tool for this.

A typical system for system operation (monitoring / control) (PC or workstation based) can be distinguished for its operational purposes by several things.

1) System for remote monitoring and control

The purpose is to measure the current state (analog, discrete) of the terminal device and transmit it to the operating system, and allow the operator to visually recognize the state.

In the case of control, it is the degree of changing the state of the remote equipment by the operator, and there are representative supervised control and data acquisition (SCADA) and automation system of distribution system.

2) Remote monitoring and control using application program

1) and monitoring function is similar, and it uses the operation result of various applications as well as the operator for control.

Relevant application environment and screen processing are required, and typical examples include microgrid and distribution management system.

Next, according to the system configuration method (system modeling) can be classified as follows.

1) single bus configuration

The topology of the system is treated as having all the devices (generation and load) connected to one bus, and is used for relatively small systems.

These include small standalone linked microgrids and consumer microgrids.

2) Multiple busbar configuration

The topology of the system is regarded as a device connected to a plurality of buses, and the connection relationship between the devices is identified through the open / close state of node-branches and switching devices.

It is used in relatively large scale systems, typically in power distribution automation systems and in silver, large scale standalone and linked microgrids.

In addition, the structure of the server is classified as follows according to the above-mentioned operation purpose (related to the importance) and system size.

1) single server

It is used when the operating system consists of one PC or workstation, and when the importance and the size of the target system are both small.

Typical examples are consumer microgrids.

2) multiple servers

The operating system is divided into main and additional devices (screen processing device, database management device, terminal data collection device, etc.), and is used when the size of the target system is relatively large and the importance (severity of operation interruption) is relatively small. If one PC or workstation has too much data to process, configure it for the purpose of distributing it.

This is typically the case for large standalone, linked microgrids.

3) Redundant Server

The operating system consists of multiple servers, of which two or more important devices are configured independently. Use when the target size and importance (the impact of downtime) is very large.

Typical examples include distribution automation and DMS, and sometimes large standalone and linked microgrids can be configured as well.

The general purpose operating system construction method applicable to the various microgrids and the distribution system according to the present invention is based on the operating system solution and structure that can be universally applied to the aforementioned various operation purposes, system configuration methods and server structures.

1 illustrates a method for constructing a general-purpose operating system applicable to various microgrids and distribution systems according to the present invention.

As referred to in Figure 1, the present invention solves the problem of the absence of universal applicability of the prior art in the following way.

That is, by constructing a solution module (S10) that satisfies the various operational purposes, system configuration method and the structure of the server (S10), and extracting and combining the necessary modules according to the final operating system (S20) finally the operating system To derive (S30).

Among the elements necessary for deriving the final operating system, the application program is configured to selectively apply the functions required by each operating system, and through this, the required application programs are mounted on the common platform as if they were assembled as blocks.

It aims to solve the problem of lack of versatility by standardizing the data model that is necessary to implement this, and by providing tools to enable engineering design and implementation thereof.

The structure of the operating system for realizing a general operation system construction method applicable to various microgrids and distribution systems of the present invention is shown in FIG.

2, the general purpose operating system applicable to various microgrids and power distribution systems according to the present invention includes a node main device 100, a backup device 200 and middleware 300, more specifically Node monitoring unit 110, data management unit 120, data processing unit 130, application program management unit 140, application program 150, terminal data processing unit 160, external data processing unit 170, screen processing unit ( 180 and a module of the report management unit 190.

Each of these modules is connected independently through the middleware 300 memory to form a modular structure that can be linked in the form of a block, so that the modular operating system can be detachably attached to various applications regardless of size, application target, or system structure. It makes application possible.

The role of each component is summarized as follows.

1) Node main device 100, backup device 200

The main device and backup device are PCs or workstations, the environment in which the operating system's software runs, and basically include an operating system (OS).

The node main unit is a space where all operations during normal operation are performed directly, and in case of maintenance and damage to the main unit, the operation right is transferred to the backup unit. In order to ensure immediate operation (operation continuity) at the time of transfer of the operating right, all data of the main device is synchronized with the backup device, which is in charge of the data synchronization processing unit inside the data processing unit 130. The same processing unit exists in the main device and the backup device.

2) node monitoring unit 110

All the processing units (processors) in the main unit and the backup unit are constantly monitored, and the heart beat with the backup unit is also checked. If there is a problem with some of the processing, it can be done automatically and manually by the operator.

3) Data management unit 120

If the non-real time (static) data related to the operation is managed by a file or a database management system (DBMS), it is the role of the data manager 120 to manage the creation, modification and deletion thereof.

The data management unit consists of a data conversion unit in charge of converting existing DB or commercial DB files, a data generation unit using schematic diagram editing, a data management unit in consultation in charge of DB schema management, and a report management unit for creating and editing reports. .

4) data processing unit 130

Responsible for the management and processing of all measured and calculated real-time data, and backs up what is needed as historical data after processing. It is also responsible for data synchronization between the main device and the backup device.

5) Application management unit 140

It starts and monitors all the running application programs and manages the data necessary to run them. The application manager also includes functions for performing real-time data exchange with the data manager 120 and monitoring the driving state of the application.

6) Applications (150)

All applications for monitoring, interpreting, and controlling the state of the microgrid and the distribution system are applicable thereto, and the driving is controlled by the application manager 140.

Each application program does not interfere with each other, and the data for execution and the resultant data exist on a separate memory managed by the application manager 140. In addition, those necessary for a screen, a history, etc. of the result are also moved by the application manager 140.

7) terminal data processing unit 160

It is a place to collect the periodic and aperiodic data of field devices coming through the communication device, and the list of field devices to be processed can be changed by setting.

8) external data processing unit 170

This is the place where data is measured in the field equipment or not its simple calculation data. It processes the weather information data and the data to be received from other systems for estimating load and power generation.

9) screen processing unit 180

It is intended to visualize the transfer of data between the system and the operator and the communication of the operator's commands. It is responsible for alarm / event handling, instrument monitoring and control, schematic / schematic diagrams and specific diagram display, and application result display.

10) Report Management Department (190)

Creates periodic or non-periodic report using historical DB, and is responsible for editing report format.

The main feature of the present invention is that each module can be detached as if the modules are assembled according to the characteristics of the target system to be installed in the operating system.

The data path for the organic coupling of each module is called middleware (300, middleware), through which the data linkage between the gig modules is performed. In addition, since it is made on a separate memory independently of each module it may be possible to modularize the block assembly form.

3 illustrates a form of a modular structure through linkage between the modules proposed in the present invention and the middleware memory.

As shown in FIG. 3, all modules (nodes and processes) are linked with respect to middleware memory data, and the physical meaning of each part of the memory is defined in the database DB through the data manager 120.

Each module that uses middleware memory data reads this definition information from the database at system startup.

Such modular structure of the present invention as shown is characterized as follows.

Among the modules, the data management unit 120 and the report management unit 190 are directly connected to the physical database to manage the creation, modification, etc. of the database, and to output the report. Create

The middleware memory includes a node, a part 310 for processing state monitoring information of a process, a part 320 for processing measurement data from a terminal device and a control command data to the terminal device, and an expression based on the measurement data. A part 330 for processing the calculated calculation data, and a part 340 for input and output to the screen processing unit 180, etc. of the application program data.

The node / process status monitoring information processing part 310 is composed of node and process IDs defined in the database, status information of each node / process, and update time.

The node monitoring unit 110, which performs the state monitoring function, brings relevant definition data from a database at system startup. After that, the definition information and the middleware memory data are linked and processed.

The measurement / control data processing part 320 is composed of each device ID, communication status, analog and binary point values, and update time.

It consists only of values, and the physical meaning of each value (open / close switch, A-phase voltage, B-phase current, etc.) of each value is determined by the data processing unit 130 that processes measurement / control data. It is taken from the database and associated with this information and memory data values.

The calculated data processing part 330 is composed of a formula ID, a device ID and a point ID, a previous / current value, an update time, and the like. In this case, as described above, the data processing unit 130 for processing the data retrieves the relevant information from the database and processes the information in association with the memory data.

Application data processing part 340 is composed of the equipment ID or hierarchical group ID (not the actual equipment such as substations, DL, MTR, etc., but the group concept of many equipment in the hierarchical structure of the system) and application calculation values.

Similarly, there is only a value, and the actual physical meaning is taken from the database at the time of startup by the screen processing unit 180 and the application program manager 140 which processes it, and processes it.

Measurement / control data transmission between the terminal data processing unit 160 and the measurement data processing unit in the data processing unit 130 uses a message transmission method (a method of directly transferring data between two processes without using a middleware memory).

Therefore, in order to use the measurement data processor process of the data processor module, the terminal data processor module is necessary.

The external data processor 170 (external data through the Internet network such as weather information) is also connected to the application manager 140 in a message communication manner. Therefore, if there is an application program using external data among the application programs, an external data processor module is necessary.

Hereinafter, the operation flow of each module will be described with reference to FIGS. 4 to 13.

4 illustrates an operation flow of the node monitor 110.

As illustrated by FIG. 4, the node monitoring unit 110 has a function of infinitely repeating and monitoring only driving states of individual processes, and thus the state (driving or stopping of driving) information of each process is almost in real time on the middleware. Status information is updated in the management point. In addition, the state is displayed on the screen by the screen processing unit 180. If the process status is "normal drive" continue to check the process run status.

If the process status is "stopped", the process will be restarted automatically if the predefined restarts are not exceeded. The screen processor 180 may manually restart the process. If the number of restarts is exceeded, it is switched to the backup system 200.

If the system is a small system without the backup system 200, the process is maintained in the driving stop state and is displayed in the screen processing unit 180 in the stopped state.

5 illustrates an operation flow of the data manager 120.

The data manager 120 is composed of a database (DB), a data converter 121, a negotiated data manager 122, a data generator 123, a report manager 124.

Database is divided as follows.

Fixed data: A database of equipment and topologies based on IEC 61970 and 61968, including all hierarchical and non-hierarchical models. This data is called static (DB) because it is fixed regardless of operational / measurement data.

Operational data: This is a DB that manages the format of data to be used by the data processing unit 130 and the screen processing unit 180. This is copied to the middleware memory 300 as it is used at system startup.

Application program data: This is a DB that manages the format of data to be used by the application manager 140.

Matching information data of application data and application program usage data: This is a DB used by the data processing unit 130 and the screen processing unit 180 for data exchange with the application program managing unit 140.

Historical data: This is a DB that is stored in the data processing unit 130, the application program management unit 140, and the like after being stored after a predetermined time interval or the end of the driving of the application and stacked for later analysis.

The data conversion unit 121 uses a conversion function for generating fixed data and operational data through conversion of commercial data and existing use data, and application data and operation and application data using the converted fixed data and operational data. Has a function of generating matching information data.

The data manager 122 has a function of editing a schema of fixed data, operational data, and application data. It also has a history data management function.

The data generation unit 123 has a schematic diagram editing and systematic data input function for newly generating fixed data without data conversion, a function for adding / editing a library of frequently used data, and a function for generating middleware memory.

The report manager 124 has a function of generating a report by using the historical data and a function of editing the format of the report.

Next, the middleware memory 300 is a volatile data memory, in which all functions (measurement data processing unit, screen processing unit, application program management unit, etc.) during operation are referred to the memory, and the database DB is changed. The same structure remains until you update the memory.

It is created using the operational data created in the database, and the measurement data processing unit stores / updates the measurement data from the field device in this memory, and the remaining screen processing unit and application program management unit store this measurement data in the middleware memory. Copy and use and copy the result back to this memory.

The data management unit 120 allows data generation / management (editing, modifying, etc.) using the schematic editing and input functions as shown in the city in order to perform common DB management on the change of the topology characteristics of the target system.

The database is divided into three parts as follows to manage all the data necessary for the operation and maintenance of the system.

Basic DB: Based on the international standard CIM (IEC 61970/61968), the hierarchical structure of the grid configuration (power management station, substation, D / L or feeder, etc.), the topology structure, the properties of the grid equipment (transformers, lines, generators, etc.) It is a place to store the information of the other two DBs are created based on this information.

Operational DB: It stores a real-time operational DB (usually located in memory) for use in data processing, application management, and individual applications. Its structure is created in Basic DB and is filled as measurement and operational data are continuously replaced. .

Historical DB: It is a place to store data for analyzing and reporting the operation status through periodic / non-periodic storage of operation data (measurement, application running result, alarm and event). The contents are periodically accumulated and stored in the data processor and the application manager.

Next, an operation flow of the data processing unit 130 that performs measurement, calculation, history data processing, switching between main / backup, and data synchronization at system restart is shown in FIG. 6.

Referring to FIG. 6, the terminal data processing unit copies (transfers) measurement data to a middleware linkage (associated memory between the terminal data processing unit and the data processing unit) by attaching the ID and the point number of the corresponding terminal device. The transmitted data is monitored indefinitely by the data processing unit to determine newly changed data. It is determined whether the new change information is alarm / event information, and if not, the new change information is stored in the corresponding data storage location on the middleware memory. If this information is information of alarm / event characteristics, the information is transferred to the historical data management unit of the data management unit of FIG. 5, the history is stored, transmitted to the local memory of the screen processing unit, and output on the screen in real time.

Next, when a predetermined operation data period (for example, 10 seconds) is reached, calculation data processing (measured data) is performed using a calculation expression (copied to Operational DB on the middleware memory) stored in the operation data formula management unit of the data management unit 120. And create new data using and expressions). The generated operation data is also updated in the corresponding memory on the middleware.

In addition, the result of the application program operation is also periodically transmitted from the application management unit to the middleware link memory (associated memory between the application manager and the data processor) for screen output and history storage, and the transmitted data is repeatedly monitored in the data processor. Judge the newly changed data. The application program data thus transmitted is also updated in the corresponding memory on the middleware.

Thereafter, it is determined whether the history storage cycle of the preset measurement / operation data and the application program history data storage cycle have been performed, and if so, the measurement / operation data and the application program data are stored in the history DB.

Also, it is determined whether the backup storage cycle and the application program backup data storage cycle of the preset measurement / computation data have been completed and, if applicable, stored in a file or a database. Backup data is a device for data synchronization when switching between primary and backup servers or when restarting a single server.

7 illustrates the detailed configuration and operation principle of the application manager 140.

Referring to FIG. 7, the application program management unit includes an M / W (middleware) linked memory manager 141, an Appl (application, application) memory manager 142, a process monitor 143, and a drive manager 144. It is. The detailed composition and role of each part is as follows.

M / W associated memory management unit 141: This is a measurement data acquisition function and event that transfers the field device acquisition data acquired by the terminal data processing unit 2-8 and processed through the data processing unit 130 to the memory DB to the application program. It consists of a function to get information, asynchronous message monitoring functions on screens and other devices, and a function to send the result of an application program to the M / W for services such as screens.

Appl memory management unit 142: This is to process the data randomly passed from the M / W associated memory management unit as a snapshot data set to finally perform an operation by the application program using this data set Memory management function. These memories include a base memory that updates measurement data at that time by the M / W linked memory management unit, a real-time memory that periodically constitutes one set for driving a periodic application program, and an application program driven by event generation. It consists of an event memory that constitutes one set when an event occurs for driving. It consists of memory management functions and memory copy and delete functions.

Process monitoring unit 143: It is composed of a function of monitoring the running state of the application program and managing communication between the linked programs.

Drive management unit 144: This is composed of a configuration management function, a sequential / event drive function, an application program stop function, etc. of the application program to be driven, for the sequential or event driving of the individual application program.

The data flow between these management units is as follows.

Input measurement data and transmit the result of application program between M / W linked memory manager and Appl memory manager.

In the M / W associated memory management unit, the process monitoring unit transmits an application program driving and stop request transmitted from the node monitoring unit 110, and the process monitoring unit transfers the application program driving result data from the M / W linked memory management unit. Is passed. When the transfer request is received, the M / W-associated memory manager receives the application program result data in the Appl memory manager.

In addition, an application program driving and stop request signal and an application program completion signal are exchanged between the process monitoring unit and the driving management unit.

Appl memory creation, copy and delete requests are transferred between the process monitor and the Appl memory manager. This command is not sent directly from the drive manager to the Appl memory manager, but through the process monitor.

8 is a flowchart illustrating the operation principle of the terminal data processing unit 160.

As illustrated in FIG. 8, the terminal data processor has the following features.

The system proposed in this patent considers data connection with an external system as follows.

That is, all terminal devices of the system controlled by the proposal system are directly connected to the proposal system through wired / wireless communication networks and communication devices, and data processing thereof is performed by the terminal data processing unit.

In addition, the terminal device connected to the connected external system is recognized as another terminal device from the viewpoint of the proposed system. Similarly, the transmission / reception of the measurement / computation data and the transmission / reception of control commands (data) are similar to those of the terminal device directly connected. Likewise performed by the terminal data processing unit.

When measurement and control commands for the terminal device directly connected by the data processing unit and the terminal device connected to the external system are transmitted (both transmitting and receiving), the measurement and control are divided and the control signal is transmitted to the corresponding terminal device or external system in the case of the control command. The control result is received from the corresponding terminal device or external system, and if the data of the external system is transmitted, the result value is transmitted to the virtual terminal device managed as a separate memory in the data processing unit. The final result is sent to the data processor, whether directly connected terminal devices or virtual terminal devices of external systems.

In case of the general measurement command, it checks whether the preset total measurement period is reached. If it is, the entire measurement is performed. If not, the event measurement is requested to the terminal device. If the measurement is for a terminal device of the external system, as described above, the result value is transmitted to the memory area of the virtual terminal device, and all data is transmitted to the data processing unit. In the present invention, the measurement data is classified as follows.

Event measurement: Request for changed information of all terminal equipment (including external system).

Total measurement: Requests all information of all terminal devices (including external system) (with or without change), and sets the measurement cycle by multiple of event measurement cycle (once every X event measurement).

Next, a flowchart of main functions of the screen processor 180 using the data collected by the data processor 130 is illustrated in FIG. 9.

As referred to in FIG. 9, the screen processor 180 has the following features.

Measurement data and alarm / event data are copied to the screen processing unit memory via the terminal data processing unit 160 and the data processing unit 130, and analog measurement values are displayed on the disconnection diagram and the ESS dedicated screen.

A state of charge (SOC) of the ESS is input, and an ESS SOC violation blocking operation is performed as shown in FIG. 10 with reference to a preset maximum / minimum setting value and a deadband setting value.

As shown in FIG. 10, when SOC violation occurs, the screen processing unit outputs a violation message, switches the ESS to stand-by, and stops the ESS automatic schedule control application program currently being executed. When the user sets the charging / discharging mode change and forcibly executes a run, a message is displayed to switch to the discharge mode when the current SOC violation is in the charging mode when the violation is in the maximum value violation state. It is executed again in the discharge mode. If you try to switch the mode after re-execution, if the current SOC is lower than the maximum dead zone setting value (Amax), mode switching is performed. Otherwise, a message is displayed to maintain the discharge mode. For example, if the current SOC is 80% and the maximum dead zone set value Amax is 70%, a discharge mode maintenance message is output.

On the other hand, if the state is in violation of the minimum value when the re-execution from the discharge mode, a message to switch to the charging mode is output. If it is in the charging mode, it will be restarted. If you try to switch the mode after re-execution, if the current SOC is higher than the minimum dead zone setting value (Amin), mode switching is performed. Otherwise, a message is displayed to maintain the charging mode. For example, if the current SOC is 20% and the minimum dead zone setting value (Amin) is 30%, a charge mode maintenance message is output.

When the switch state change data is input, life and death test and system reconfiguration are performed as shown in FIGS. 11 and 12.

As shown in Figure 11 and 12, life and death line processing is the drawer in the path (1) system (feeder start point breaker if the distribution system, branch breaker / switchgear with the utility system in the case of the customer system) to see the state of the device from Determination of the live / live line through the search to the open switch, and path 2) Determination of the live / live line through the search to the open switch from here. Segments that do not belong to either path are de-energized. The one-line diagram creates a tree structure based on facility data using the system topology and the closed state of the switchgear (breaker and switchgear), sets the branching direction of the tree, and coordinates according to the branching direction. It automatically inputs information, checks for collisions between equipment objects, and if a collision occurs, avoids collisions and resets coordinates to reset the branching direction to resolve the collisions.

When the alarm / event data is input, the newly generated alarm / event information is first displayed on the alarm / event display screen, and when a fault-related event occurs, the fault handling process is executed. As shown in FIG. 13, the failure determination for operating the failure processing process is divided into three processes as follows.

Fault occurred between the automated switchgear in the system jurisdiction system: Determines whether a fault signal (fault indicator signal, FI alarm) occurs, and if a FI occurs, it determines the temporary / momentary fault condition and performs fault handling.

Draw-out in the system jurisdiction system (feeder start point in the distribution system, branch point from the utility company's system in the case of distribution system)

Higher system that is not a system jurisdiction system (Failure occurred in the power transmission system if the distribution system, or in the distribution system if the customer system) Failure: The state of the draw-out protection device is "close" or the voltage is measured with no voltage. Determination as a failure and processing of the failure

The screen processor repeats and monitors the alarm data indefinitely. When an alarm occurs, the above three types of failures are distinguished. Is displayed (12-3). In case of a failure directly under the draw protection device in the system jurisdiction system, the phase information of the fault current is judged, and the fault is also displayed on the disconnection diagram. In case of upper system failure, it is judged whether there is a voltage abnormality and switch open / closed state, and if both conditions are met, it also indicates the failure in disconnection diagram.

The fault occurrence is displayed on the disconnection diagram, and the troubleshooting process screen is displayed at the bottom of the disconnection diagram. In addition, several blocking commands are transmitted at the same time as the occurrence of a failure, and the application management unit stops the periodic driving application program according to the transmitted signal. After determining whether to execute the fault section search and executing, the operation command of the fault section search application is transmitted to the application program manager in the form of a message. The application program manager organizes the information related to the fault and generates a memory in the Appl memory manager for driving the application program, drives the application program, and sends the result back to the screen processor. The screen processing unit displays the result (operation switch list for fault section isolation and its operation sequence) on the screen. The operator can operate according to the switch list and the operation sequence output by the application program result, or if the result is determined to be inaccurate for the operator (12-9). When the power failure recovery is performed outside the fault section, the operation result of the switchgear device up to that point is transmitted as a message to the application program manager, and at the same time, the driving command of the power failure recovery program is transmitted. Then, the execution result of the power failure recovery program is displayed on the screen, and the operation of the power failure section is restored through an operation by the operator. The user can terminate the troubleshooting process, in which case the previously generated blocking instruction is released (12-14). It is determined whether both the failure section isolation procedure and the blackout section recovery procedure have been processed (12-15), and if all have been processed, the corresponding failure case is added (12-16) on the failure history information screen. The fault occurrence time, the list of operating switch, etc. are recorded in this order. Finally, the operator inputs the duration of the fault on the fault history information screen (this can be very different from the fault occurrence time), and when it is finished, the information related to the fault is stored in the history DB.

Hereinafter, an embodiment in which individual modules are combined and configured according to respective application points by a general operating system construction method applicable to various microgrids and distribution systems according to the present invention will be described.

1) Linked MG system of factories and buildings

Operational purpose is output stabilization and peak reduction through renewable power generation and ESS schedule control. In this case, the module is composed of Eng / common elements (terminal data collection) + data processing (measured data processing) + application (prediction / ESS scheduling) + screen processing (device monitoring, application). / Consists of ESS control program for power generation forecasting, peak reduction and independent operation switching.

2) Community MG system of distribution system

The purpose of operation is to reduce peak by independent operation in emergency and ESS schedule control. In this case, the module is composed of Eng / common elements (DB management, terminal data collection) + data processing (measurement data processing, history data processing) + application (topology processing, failure processing, prediction / ESS scheduling) + screen processing (drawing Processing, device monitoring, and application program), and the application program consists of load prediction, ESS control for peak reduction, and automation of troubleshooting.

3) standalone MG system for small books

The purpose of operation is to maintain the frequency stability through ESS schedule control and generation / load control, and to reduce the generation fuel cost by increasing the renewable capacity. In this case, the module is composed of Eng / common elements (terminal data collection) + data processing (measurement data processing) + application (prediction / ESS scheduling) + screen processing (device monitoring, application) and loads the application program. And ESS SOC prediction through power generation forecast and emergency control (load / generator) program.

4) standalone MG system for large scale books

The purpose of operation is to maintain frequency stability through ESS schedule control and generation / load control, and to troubleshoot distribution system. In this case, the module configuration consists of Eng / common elements (DB management, terminal data collection) + data processing (measurement data processing, history data processing, data synchronization), application programs (topology processing, failure processing, prediction / ESS scheduling) + screen It consists of processing (drawing process, equipment monitoring, application program), and the application program consists of ESS SOC forecasting through load and generation forecasting, emergency control (load / generator), and failure handling automation program.

5) Distribution automation system of distribution system

Operational purpose is remote monitoring of power distribution system and troubleshooting by operator. In this case, the module consists of Eng / common elements (DB management, terminal data collection, node monitoring) + data processing (measurement data processing, history data processing, data synchronization) + screen processing (drawing processing, device monitoring), There is no special configuration for the application.

6) DMS system of distribution system

The purpose of the operation is to optimize the distribution system (voltage, fault handling) using the application program. In this case, the module configuration consists of Eng / common elements (DB management, terminal data collection, node monitoring) + data processing (measurement data processing, history data processing, data synchronization) + application (topology processing, system operation / control, prediction / Schedule) + screen processing (drawing processing, device monitoring, application program), and the application program includes topology processing, status estimation, load estimation, voltage control, and failure automation.

Although the present invention as described above has been described with reference to the illustrated drawings, it is not limited to the described embodiments, it can be variously modified and modified without departing from the spirit and scope of the present invention is common knowledge in the art Self-evident to those who have Therefore, such modifications or variations will have to belong to the claims of the present invention, the scope of the invention should be interpreted based on the appended claims.

* Explanation of the sign

S10: Battery SOC Measurement

S20: comparison of SOC and substandard 1

S21: Controllable Load Break

S22: Battery SOC Measurement

S23: comparison of SOC and substandard 2

S24: Diesel generator operation output command transmission

S30: Comparison of SOC and higher standard 1

S31: controllable load input

S32: Battery SOC Measurement

S33: SOC vs. Upper Standard 2

S34: Renewable Energy Power Output Control

Claims (16)

Configure solution modules for the operation of microgrids or distribution systems, Extracting a solution module that satisfies the operational purpose of the microgrid or the distribution system, the system configuration method and the server structure among the configured solution modules, Combining extracted solution modules to derive the final operating system, General purpose operating system construction method applicable to various microgrids and distribution systems. The method according to claim 1, Characterized in that the application to be mounted on the final operating system can be selectively applied to the function required for the micro grid or power distribution system, General purpose operating system construction method applicable to various microgrids and distribution systems. The method according to claim 2, Solution module for the operation of the micro grid or distribution system, A node monitoring unit for monitoring a configured process processing unit, a data management unit for creating, modifying, and deleting data stored in a database, a data processing unit for processing measured and calculated data, an application program managing unit for driving a driven application program, Selected from the terminal data processing unit for processing data collected from the system, the external data processing unit for managing data received from the external system, the screen processing unit for displaying the status of the operating system and the report management unit for creating and editing the report using the database Characterized in that a plurality of solution modules, General purpose operating system construction method applicable to various microgrids and distribution systems. The method according to claim 3, The plurality of solution modules are each composed of a modular, characterized in that the operating system to build a removable system, General purpose operating system construction method applicable to various microgrids and distribution systems. The method according to claim 4, Characterized in that the data linkage between the solution module is performed through the middleware provided on a separate memory, General purpose operating system construction method applicable to various microgrids and distribution systems. A plurality of solution modules for the operation of the micro grid or the distribution system are selectively combined according to the operation purpose of the micro grid or the distribution system, the configuration of the system and the structure of the server, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 6, Further comprising an application to which the function required for the microgrid or power distribution system is selectively applied, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 7, The solution module, A node monitoring unit for monitoring a configured process processing unit, a data management unit for creating, modifying, and deleting data stored in a database, a data processing unit for processing measured and calculated data, an application program managing unit for driving a driven application program, Multiple selection among a terminal data processing unit for processing data collected from the system, an external data processing unit for managing data received from an external system, a screen processing unit for displaying the status of the operating system, and a report management unit for creating and editing a report using a database Characterized in that General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 8, The plurality of solution modules are each modular, characterized in that removable to the operating system, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 9, It is provided on a separate memory, further comprising middleware that performs data linkage between the solution module, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 10, For linked microgrid systems such as factories and buildings where output stabilization and peak reduction through renewable energy generation and ESS schedule control are intended for operation, data processing for the processing of Eng / common element modules for collecting terminal data and measurement data Characterized in that the module and the screen processing module for monitoring of the device is selectively coupled, the application program for load and generation prediction and ESS scheduling is applied, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 10, For community-type microgrid system that aims to reduce peak by independent operation and control of ESS schedule in case of emergency, Eng / common element module for database management and collection of terminal data, data for processing measurement data and historical data Characterized in that the processing module and the screen processing module for monitoring of the device is selectively combined, and application programs for topology processing, fault handling, load and power prediction and ESS scheduling, is applied, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 10, For small stand-alone microgrid systems whose purpose is to maintain frequency stability through ESS schedule control and power generation and load control, and to reduce power generation fuel cost by increasing renewable capacity, Eng / Common element module for collecting terminal data and A data processing module for processing measurement data and a screen processing module for monitoring the device may be selectively combined, and application programs for load and power generation prediction and ESS scheduling may be applied. General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 10, Eng / common element module and measurement data for database management and collection of terminal data for large scale standalone microgrid system whose purpose is to maintain frequency stabilization through ESS schedule control and generation and load control and to troubleshoot power system. And a data processing module for processing historical data and data synchronization and a screen processing module for monitoring the device, and an application program for topology processing, failure processing, load and power generation prediction, and ESS scheduling is applied. Made, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 10, For distribution automation system with the purpose of remote monitoring and fault handling of distribution system, Eng / common element module for database management, terminal data collection and node monitoring, processing of measurement data and historical data, and data processing for data synchronization Characterized in that the module and the screen processing module for the monitoring of the device is selectively coupled, General purpose operating system applicable to various microgrids and distribution systems. The method according to claim 10, For the DMS system with the goal of optimizing the distribution system optimization using the application program, Eng / Common element module for database management, terminal data collection and node monitoring, and data for processing and data synchronization of measurement data and historical data The processing module and the screen processing module for monitoring of the device are selectively combined, and application programs for topology processing, grid operation and control, load and power generation prediction, and ESS scheduling are applied. General purpose operating system applicable to various microgrids and distribution systems.

Images