JP2008186401A - Database management system and database management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To simplify data structure and retrieval processing in a database management system. <P>SOLUTION: A database has a data structure allowing a plurality of monitoring objects to belong to a plurality of logical groups in management of the plurality of monitoring objects grouped for operational reasons while a tree structure of database based on physical inclusion relations of the monitoring objects itself is maintained by building the database having a tree structure as hitherto with respect to physical inclusion relations that define location relations etc. of the monitoring objects. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a database management system and a database management method. More specifically, the present invention relates to a database management system and a database management method suitable for database management in a supervisory control system.

  In various fields, a monitoring control system has been constructed as a system that centrally monitors and controls equipment, resources, and the like (hereinafter referred to as monitoring objects) to be monitored and controlled. In recent years, a method of modeling an object to be monitored as an object class using an object-oriented technique and designing an object for managing facility configuration data and state / measurement values is becoming popular.

  Since the monitoring control system requires real-time property, in consideration of minimization of access time to data and the like, an object representing a monitoring object is often represented by a tree structure. This tree structure is constructed by using the physical inclusion relationship of the monitoring object. For example, in the case of a monitoring control system in a water reclamation center (sewage treatment plant), a certain electric motor is equipped in the pump. In this case, the objects representing the pump and the motor are nodes of a tree structure, the object representing the pump forms a parent node, and the object representing the motor forms a child node. Further, since this tree structure is large-scale, it is necessary to use a database management system when creating, updating, deleting, searching, etc. for data.

  In a database having such a tree structure, there is one pointer from an upper node to a certain node, and there is no pointer pointing from the lower node to the upper node, that is, the parent node and the child node are 1: n. It must be a relationship. For example, in the access control list generation method described in Patent Document 1, the organization structure between a user group positioned at a node and its users and user groups is represented by a tree structure, and an arbitrary member is a single user. You are forced to belong to a group (parent node).

  On the other hand, as a database management system using a data structure other than a tree structure, there is a management system that performs database management using a relational model. For example, in the access control system described in Patent Document 2, a user can belong to a plurality of groups by constructing a knowledge database.

Japanese Patent Laid-Open No. 11-313102 Japanese Patent Laid-Open No. 2006-12117

  However, if data representing a monitoring target is represented as a tree-structured node using a database having a tree structure as in the technique described in Patent Document 1, the following problem occurs.

  In the monitoring and control business, apart from the physical inclusion relationship that defines the positional relationship etc. of monitoring objects, multiple monitoring objects are grouped and managed for operational reasons (hereinafter referred to as this management relationship). Is also called a logical group).

  A logical group is, for example, in a monitoring and control system in a water reclamation center, when an object representing a gate and an object representing a pump are included in different parent nodes on the tree structure and there is no physical inclusion relationship, In order to control the gate opening and pump pumping speed so that the water level of the tank where the gate is installed at the water inflow point and the pump is installed to pump out the water is kept constant. Set as a group. In addition to the logical classification of whether or not there is an interlocking relationship with other devices in this way, for example, when managing who is the administrator of each monitored object, when is the maintenance time, etc. You must also set up logical groups.

  Since this logical group cannot be represented by a tree structure such as the technique described in Patent Document 1 in which the parent node and the child node have a 1: n constraint, the tree structure described in Patent Document 1 is not represented. Even if it is used, there is a problem that a logical group cannot be managed.

  This problem can be managed by using a data structure other than a tree structure such as a relational model, using a separate table, or attaching a link from a separate tree structure database as described in Patent Document 2. However, the data structure is complicated, and as a result, search processing and data maintenance are complicated. For example, since the physical inclusion relationship and the logical group cannot be represented by a single tree structure, there is a problem that different search methods must be set for each, that is, the search program must be designed. Further, there is a problem that the search process cannot be easily and quickly performed because the difference in the table, the link, and the like must be taken into consideration when executing the search.

  Further, for example, a logical group such as who is managing the monitoring object is not the monitoring object itself, and therefore it is easy to change. When data changes, deletions, etc. occur in this way, it is necessary to correct data at multiple locations in consideration of the database relationship, and it is difficult to correct data for consistency and maintenance is complicated. Problem arises. In addition, since the monitoring and control work requires real-time properties, there is a problem that the processing speed of search processing and the like becomes slow when a data structure other than a tree structure is used together.

  Therefore, the present invention makes it possible to belong to a plurality of logical groups at the same time while maintaining the tree structure of the database based on the physical inclusion relationship of the monitored objects. It is an object of the present invention to provide a database management system and a database management method capable of performing a search by the same search method as a simple tree structure search method and simplifying a search process and a data structure.

  In order to achieve this object, the database management system according to claim 1 defines a monitoring object to be monitored and controlled as an object class, and manages the database in the monitoring control system that uses an object for monitoring control of the monitoring object. In the system, the database logically classifies the monitoring objects in the operation of the “equipment” class representing the monitoring object and the monitoring control business while maintaining the tree structure representing the physical inclusion relationship of the monitoring object. Both the “operation group” class that represents the logical group for management and the “equipment accommodation” class that manages both the “equipment” class and the “operation group” class, which are object classes representing the monitoring targets, and the logical and physical relationship Inherit the "monitoring" interface that defines the format of the methods the class has In addition, the “operation group” class can be included in the “equipment accommodation” class, and the “inclusion relationship” that defines the processing when it becomes the parent node of the tree structure with reference to the “monitoring target” interface The “node” interface and the “equipment accommodation” class include zero or more “equipment” classes and zero or more “operation group” classes, and further inherit the “monitoring target” interface. It has a data structure using an object class structure.

  The database management method according to claim 2 is a database management method in a monitoring control system in which a monitoring object to be monitored and controlled is defined as an object class, and the object is used for monitoring control of the monitoring object. In order to logically classify the monitoring objects in the operation of the “equipment” class that represents the monitoring objects and the monitoring control work, while maintaining the tree structure representing the physical inclusion relationship of the monitoring objects Both the “operation group” class that represents the group has the “equipment” class that is the object class that represents the monitoring target, the “operation group” class, and the “equipment accommodation” class that manages the logical and physical relationship together. Inherit the "monitoring target" interface that defines the method format, and the "operation group" class It is possible to be included in the “container” class, and it also inherits the “inclusion relation node” interface that defines the processing when it becomes the parent node of the tree structure with reference to the “monitoring target” interface and “equipment accommodation” The “class” includes zero or more “equipment” classes and zero or more “operation group” classes, and further has a data structure using an object class structure characterized by inheriting the “monitoring target” interface. The database is configured.

  Therefore, with regard to the physical inclusion relationship that defines the positional relationship and the like of the monitoring target object, a database tree based on the physical inclusion relationship of the monitoring target object is constructed by constructing a database having a tree structure as in the past. While maintaining the structure itself, it is provided with a data structure that allows a plurality of monitoring objects to belong to a plurality of logical groups at the same time for group management for operational reasons.

  In other words, both the “equipment” class representing the physical monitoring object and the “operation group” class representing the logical group inherit the “monitoring object” interface that defines the format of the method of the object class representing the monitoring object. Therefore, in the search process, both the “operation group” object and the “equipment” object can be regarded as “monitoring targets”.

  In addition, the “operation group” class can be included in the “equipment accommodation” class that manages logical and physical relationships together. By referring to the “monitoring target” interface, the “operation group” class can be included. The class and the “equipment” class are related via the “monitoring target” interface, and further, by providing a process for becoming a parent node of the tree structure by inheriting the “inclusion relation node” interface, When searching for a physical monitoring target from a group, the "operation group" class refers to the monitoring target of the "equipment" class that inherits the "monitoring target" interface after referring to the "monitoring target" interface be able to.

  In addition, the “equipment accommodation” class includes zero or more “equipment” classes and zero or more “operation group” classes, and can be handled as a monitoring target by inheriting the “monitoring target” interface. is there.

  According to the database management system and the database management method according to the present invention, the positional relationship of the monitoring objects that have not been represented by the same data structure and must be managed using another database, another table, or the like. It is possible to integrate and manage a logical group which is a logical classification in the operation of the monitoring and control business such as a physical inclusion relationship.

  As a result, the data is handled as an integrated data structure, and the physical inclusion relationship and the logical group are handled in common, for example, when searching for an object, for example, and there is one physical parent node. However, it is possible to perform processing corresponding to each of cases having different aspects such as logical classification can be freely performed.

  In addition, since there is no link to other databases, tables, etc. and the data structure is simplified, the maintainability of the software constituting the database management system is improved.

  In addition, the physical inclusion relationship and logical group search process can be performed without referring to links to other databases, tables, etc., and the search process is simplified, so the time until the search result is obtained. Can be shortened. That is, in the search process, both the “operation group” object and the “equipment” object can be regarded as “monitoring targets”. By realizing the three search methods, the search method as “monitoring target”, the search method as “operation group”, and the search method as “equipment” without providing another search method in this way, the operator can A search can be executed without recognizing the difference.

  Hereinafter, the configuration of the present invention will be described in detail based on embodiments shown in the drawings.

  The database management system of the present invention defines a monitoring object to be monitored and controlled as an object class, and in the database management system in the monitoring control system using an object for monitoring control of the monitoring object, the database is the monitoring object. While maintaining the tree structure that represents the physical inclusion relationship, at least the “equipment” class that represents the monitored object and the “operation” that represents the logical group for logically classifying the monitored object in the operation of the monitoring control business The “group” class defines the format of methods that the “equipment” class, which is the object class that represents the monitoring target, the “operation group” class, and the “equipment accommodation” class that manages logical and physical relationships together. Inherit the "monitoring target" interface, and the "operation group" class It is possible to be included in the “equipment accommodation” class, and further, by referring to the “monitoring target” interface, inheriting the “inclusion relation node” interface that defines the processing when it becomes a parent node of the tree structure, and “ The “equipment accommodation” class includes zero or more “equipment” classes and zero or more “operation group” classes, and further has a data structure using an object class structure characterized by inheriting the “monitoring target” interface. It is to be prepared.

  First, the system configuration of the database management system of this embodiment will be described. In the present embodiment, as an example, a case where the database management system is applied to a monitoring control system of a water reclamation center will be described as an example. The target monitoring control system is not particularly limited, and may be, for example, a monitoring system in a water treatment facility, a garbage incineration facility, or the like.

  The configuration of the monitoring control system 1 of the water reclamation center is, for example, a hardware configuration as shown in FIG.

  The monitoring control system 1 according to this embodiment includes a central monitoring control facility 2, a process controller 3, and a sequencer 4. Hereinafter, the process controller 3 and the sequencer 4 are collectively referred to as a local control facility 6.

  The database management system 10 of the present invention is configured in the central monitoring control facility 2. The central monitoring and control facility 2 includes an output device such as a display, an input device such as a keyboard and a mouse, a central processing arithmetic device (CPU) that performs arithmetic processing, and a main memory that stores data, parameters, and the like being calculated. A workstation (RAM), a hard disk as an auxiliary storage device in which each database, calculation results, and the like are recorded, a workstation equipped with a communication interface for communicating with the outside, and a dedicated computer are used. Hereinafter, the main storage device and the auxiliary storage device are collectively referred to simply as a storage device. The hardware resources are electrically connected through a bus, for example.

  An example of the hierarchical structure in the database management system 10 of this embodiment is shown in FIG. An object group is a collection of programs for realizing a monitoring control function. Each object group 12 to 15 is recorded in an auxiliary storage device, and a workstation or a dedicated computer functions as the central monitoring control facility 2 by reading and executing each program by the CPU. Data, parameters, and the like necessary for the execution are loaded into the RAM. In addition, “search results”, “search target nodes” (see FIG. 6), “result list” (see FIG. 8), etc., which will be described later, are also stored in the RAM during processing.

  The central supervisory control facility 2 has, for example, a function of displaying the monitoring information 28 on the operator 11 based on the monitoring data 21 sent from the process controller 3, and a target process based on an operation 27 from the operator 11. A function for instructing the controller 3 to set devices and values, a function for recording logs necessary for monitoring and control work, a function for providing necessary data to an information management facility (not shown) for organizing operation records, etc. It is. The information management facility is connected to the central monitoring control facility 2 via a communication network. In addition, calculations necessary for controlling the individual devices 5 a to 5 d are not executed by the central monitoring control facility 2 but are executed by the process controller 3.

  The boundary object group 12 provides a human interface for the operator 11 and an interface for realizing system cooperation with other programs.

  The control object group 13 processes data obtained from other object groups and activates screen display and data transfer to the local control facility 6 which is a remote device.

  The communication module object group 14 provides a communication function with the local control facility 6 installed at the same location as the facility to be monitored and controlled.

  The internal object group 15 is a set of object classes that collectively represent the monitoring control data for each “equipment” class or for each “operation group” class, and the frequency of correction is low during the lifetime of the database. Details of each object class will be described later.

  The exchange of data of each object group will be described below. The monitoring data 21 transmitted from the local control facility 6 to the communication module object group 14 is classified into an analog value (measured value, continuous value) and a digital value (on / off information, 0-1 value). In addition, each record of the monitoring data 21 is given a unique ID (device ID) to each device, and is automatically transmitted to each device at a predetermined time interval. At this time, the correspondence between each device ID and the device may be stored in the auxiliary storage device as an initial setting file.

  The analog value of the monitoring data 21 includes, for example, a water level (m), a pump output (%), a valve opening / closing degree (%), a current value (A), and the like. The water level is the difference from the reference water level.

  On the other hand, the digital value of the monitoring data 21 includes, for example, the valve closing status (ON = fully closed, OFF = inch open), the status of the switchgear in the power receiving / transforming equipment (ON = input, OFF = open), and the pump operation. There are situations (ON = running, OFF = stopped), various alarms (presence / absence of occurrence of ground fault, etc.).

  Similarly, the operation data 22 transmitted from the communication module object group 14 to the local control facility 6 can be roughly divided into analog values and digital values.

  The analog value of the operation data 22 includes, for example, a pump output set value (%), a valve opening set value (%), a medicine injection rate (%), and the like, and the digital value includes, for example, a pump, a blower, etc. There are operation commands (ON = operation, OFF = stop), valve opening / closing commands (ON = close, OFF = open), etc. for each device.

  The operation result / monitoring information transmission / reception path includes transmission 23a from the communication module object group 14 to the control object group 13, transmission 23b from the control object group 13 to the boundary object group 12, and transmission from the control object group 13 to the internal object group 15. There are three paths for transmission 23c.

  The operation result / monitoring information 23 a transmitted from the communication module object group 14 to the control object group 13 is obtained by converting the monitoring data 21 received from the local control facility 6 into a format that can be handled by the control object group 13. For example, since the monitoring data 21 has a different file format depending on the manufacturer of the equipment constituting the local control facility 6, the digital monitoring data 21 is received as a bit from the local control facility 6 and converted into Boolean in the program. After that, the process of the corresponding control object group 13 may be called. Therefore, the data item to be handled is the same as the monitoring data 21.

  In addition, the operation result / monitoring information 23b transmitted from the control object group 13 to the boundary object group 12 includes, for example, information on the display method of icons and buttons constituting the monitoring control screen for the operator 11 displayed on the output device. Applicable. The control object group 13 changes the color of a corresponding icon or button or displays a value based on the operation result / monitoring information 23a received from the communication module object group 14. Therefore, the data item to be handled is the same as the monitoring data 21.

  The operation result / monitoring information 23c transmitted from the control object group 13 to the internal object group 15 corresponds to information necessary for creating a history in the internal object, for example. The control object group 13 stores data in the internal object group based on the operation result / monitoring information 23 a received from the communication module object group 14. Therefore, the data item to be handled is the same as the monitoring data 21.

  The operation command transmission / reception path includes transmission 24b from the boundary object group 12 to the control object group 13, transmission 24a from the control object group 13 to the communication module object group 14, and transmission 24c from the control object group 13 to the internal object group 15. There are three paths.

  The operation command 24b transmitted from the boundary object group 12 to the control object group 13 calls, for example, the process of the control object group 13 according to the input of the pump output setting by the operator 11 from the monitoring control screen. It is. Therefore, the data item to be handled is the same as the operation data 22.

  In the case of the operation command 24a transmitted from the control object group 13 to the communication module object group 14, a process of transmitting operation data corresponding to each facility is started. Therefore, the data item to be handled is the same as the operation data 22.

  In the case of transmission 24 c from the control object group 13 to the internal object group 15, a process for saving a record is started in the object representing the facility to be operated. Therefore, the data item to be handled is the same as the operation data 22.

  The search 25 from the control object group 13 to the internal object group 15 refers to an operation for searching for an object to be operated from the internal object group 15. For example, it is a process of searching for an object representing a pump that is a monitoring target. In addition, a corresponding object is searched from the name of the monitoring object, or an object that satisfies a certain condition (for example, driving) is searched.

  The data 26 is data (search result) passed in response to a search request for the control object group 13. For example, the water level history of the tank corresponds to this.

  The process controller 3 is mainly a hardware device developed exclusively for at least an arithmetic unit (CPU), a storage device, a communication interface, and the like.

  The process controller 3 performs calculations such as integral calculation and differential calculation necessary for feedback control based on the data sent from the sequencer 4, and sends a command based on the calculation result to the sequencer 4 and the central monitoring control equipment 2. A function for setting control calculation parameters based on the received command values and sending an operation command for the device to the sequencer 4 is provided.

  For example, a programmable logic controller (PLC) is used for the sequencer 4, and for example, a pump 5a, a valve 5b, a conveyor 5c, a blower 5d, and the like are connected to each of the sequencers 4a to 4d.

  The sequencer 4 receives a signal from the process controller 3 that receives the signal indicating the analog value or the digital value from each of the devices 5a to 5d, receives the command from the process controller 3, and the command from the process controller 3 or the signal from the device. Is provided with a function of performing sequence control based on the above, a function of transmitting signals to the devices 5a to 5d, a function of transmitting monitoring data to the process controller, and the like. For example, a remote input / output device is used to transmit / receive signals to / from the devices 5a to 5d.

  As described above, in the monitoring control system 1 in the water reclamation center, facilities such as a pump and a blower are physical monitoring objects. For such a physical monitoring target, it has been possible to construct a database with a tree structure and perform a search process. However, logical groups such as pumps and valves having an interlocking relationship as described above cannot be managed with the same tree structure.

  Therefore, in the database management system of the present embodiment, the database tree structure itself based on the physical inclusion relationship of the monitoring target is maintained by constructing a database having a tree structure using the object class configuration shown in FIG. However, it is possible to belong to a plurality of logical groups at the same time. Note that the class diagram in FIG. 3 is expressed in UML (Unified Modeling Language), which is a standard notation method for object classes.

  In FIG. 3, the square indicates the object class, and the characters in the square indicate the object class name. Associations between object classes are represented using lines. A solid line represents an association between object classes. The relation connected by the triangle arrow and the solid line represents the inheritance relationship, which means that the other object class has the characteristics (attributes and methods) of the object class accompanied by the triangle. A relationship connected by a triangular arrow and a broken line indicates a mounting relationship. The number attached to the line indicates the multiplicity.

  White diamonds indicate aggregation (whole-partial structure). Aggregation is a relationship in which one part forms part of the other, and the one with the rhombus is the entire side. Black diamonds indicate the composition. The composition is a stronger aggregation in which the life cycle matches the original object, and indicates an aggregation to an object that disappears when the original object disappears.

  A description surrounded by “<<>” above each object class name is a stereotype, which indicates that the object class has a described feature. “<< Interface >>” in FIG. 3 indicates an interface that defines only the format of a method used for interaction with another object. “<< Abstract >>” indicates that an instance of the object class is It indicates that an instance of an object class that is not generated but has an inheritance relationship is an generated abstract class. “<< Internal >>” indicates the internal object group 15, and “<< Control >>” indicates the control object group 13.

  Hereinafter, each object class in the database management system of the present embodiment will be described, but the name of each object class is an example, and the present invention is not limited to this.

  The “name operation” interface 31 defines a format of a method for performing an operation of a name to be given to an instance. For example, the method to get the name is defined as getName with no argument and no return value, and the method for setting the name is defined as setName with a string as the argument and a boolean value as the return value . The interface is a collection of only method declarations, and is used only after other classes are implemented.

  The “name” class 33 defines features common to object classes (“measurement item” class 37, “equipment” class 36, and “operation group” class 39) that need to manage names assigned to instances. . That is, a character string representing an object name is used as an attribute, and a specific processing procedure of a method defined in the “name operation” interface 31 is related to the operation of the name. For example, a character string “Pump No. 1” is stored, and the getName method for acquiring the character string has a procedure of returning this character string as it is.

  The “inclusion relation node” interface 35 represents a feature when a node is provided at a lower level. Therefore, the node located at the lowest layer of the tree structure cannot be the “inclusion relation node” interface 35. The “inclusion relation node” interface 35 has no attribute, and defines the formats of the “inclusion determination” method and the “search” method.

  The “inclusion determination” method is a method for determining whether or not a given “monitoring target” object exists (is included) as a lower node of an object having an “inclusion relation node” interface.

  The “search” method finds an object having a given name from a sub-tree below the object having the “inclusion relation node” interface 35. If it exists, the object exists. It is a method that returns a value indicating that it is not.

  The “monitoring target” interface 32 defines a format of a method of an object class (“equipment” class 36, “operation group” class 39, “equipment accommodation” class 40) representing the monitoring target. Examples of the method possessed by the object class representing the monitoring target include setting / acquisition / release of the “measurement processing” object.

  The “equipment” class 36 inherits the characteristics of the “name” class 33 and defines the physical configuration, that is, the characteristics common to the devices to be monitored or the components constituting them and the facilities that accommodate them. It is. The main attributes include the presence / absence of a major failure (0-1 value), the presence / absence of a minor failure (0-1 value), the operating state (0-1 value), and the like. The main methods include cancellation of occurrence of major faults, cancellation of occurrence of minor faults, and storage and acquisition of operating conditions.

  Furthermore, the “equipment” class 36 defines the specific processing of the method defined by the “monitoring target” interface 32, and contains zero or more “measurement item” objects, and one “measurement processing”. It has an association to an object. Note that an object class representing a specific facility, such as an electric motor or a pump, is derived from this class.

  The “operation group” class 39 inherits the characteristics of the “name” class 33 and defines the characteristics common to the logical group, that is, the group created for the monitoring control operation. There are no attributes, and the “inclusion relationship node” interface 35 and the “monitoring target” interface 32 define the specific processing of the method. For example, a method for registering a new object as a lower node is defined (see FIG. 10). In addition, zero or more “operation group” objects are aggregated and related to zero or more “facility” objects and one “measurement processing” object.

  The “facility accommodation” class 40 inherits the characteristics of the “facility” class 36 and manages logical and physical relationships together. In other words, it defines the characteristics when physically storing what the “equipment” class represents, or when accompanied by what the “operation group” class 39 represents. For example, a method for obtaining all objects having a physical or logical relationship and existing as lower nodes in the data structure is provided. There is no attribute, and there is a method related to addition / deletion of equipment, and the “inclusion relation node” interface 35 defines specific processing of the method whose format is defined. Also, zero or more “facility” objects are aggregated.

  The “object search” class 34 provides a function of searching a database according to a given search condition and acquiring all corresponding objects. For example, when searching for an object having a specific name, the object is acquired through the “inclusion relation node” interface 35 or the “monitoring target” interface 32 based on a character string representing the given name. is there.

  The character string representing the name is composed of all object names that have passed from the root object of the data structure to the object in the data structure constructed using the object class shown in FIG. For example, as shown in FIG. 4, when “valve: washing water valve” surrounded by a dotted line indicated by reference numeral 42 is designated, “water-blocking door / sand basin equipment / weight conveyor No. 1 / washing water valve” Enter as follows. Note that a delimiter “/” is set between the object names and can be extracted as an element. The input of the character string is not limited to the case where the operator directly inputs it, but may be input from another system such as a form management system linked to the monitoring control system 1.

  In addition, it is possible to set a search range and search conditions and acquire a plurality of corresponding objects at the same time. For example, as shown in FIG. 5, the search range includes a first search range 44 that targets only the designated object 43, a second search range 45 that targets an object group directly included in the specified object 43, A third search range 46 that targets up to N levels of the subtree starting from the specified object 43, a fourth search range 47 that targets all subtrees starting from the specified object 43, and the like are possible. is there. In addition to the object name, the search conditions include software level information such as an object class name, conditions derived from data such as an object whose measured value is larger (or smaller) than a given value, etc. Can be set. For example, in addition to “equipment” and “operation group”, “object class type”, “object class type not considering inheritance”, “objects with unresolved alarms”, and the like can be set.

  The search range and search conditions are set by, for example, displaying the GUI on the output device so that the inspector can select from the monitoring control screen.

  The “measurement item” class 37 inherits the characteristics of the “name” class 33 and defines common characteristics in managing the measurement items. It has an attribute indicating whether the measurement item is being measured, and methods such as addition and acquisition of measurement values and acquisition of the number of measurement value data. Also, zero or more “measurement value” objects are aggregated.

  The “measurement value” class 38 is a class for storing a value measured at a certain time. It has attributes representing measurement time and measurement value, and methods such as measurement time acquisition and measurement value acquisition.

  The “measurement process” class 41 performs a process of adding a measurement value to an appropriate measurement item of an appropriate facility for the monitoring data 23 a received by the database management system 10. When additional processing such as display on an output device is performed, a class derived from this class is created.

  In addition, an object class that realizes a specific monitoring control function may be appropriately defined as necessary, and is not particularly limited, and thus description thereof is omitted.

  The main features of the object class configuration of the database management system of the present invention described above are summarized as follows.

(1) Both the “equipment” class 36 representing a physical monitoring object and the “operation group” class 39 representing a logical group inherit the “monitoring object” interface.
(2) The “operation group” class 39 can be included in the “equipment accommodation” class 40, and the “operation group” class 39 and the “equipment” class 36 are referred to by referring to the “monitoring target” interface 32. Are associated via the “monitoring target” interface 32 and further include a process in the case of becoming a parent node of a tree structure by inheriting the “inclusion relation node” interface 35.
(3) The “equipment accommodation” class 40 includes zero or more “equipment” classes 36 and zero or more “operation group” classes 39, and further inherits the “monitoring object” interface 32 to monitor. It can be handled as

  By configuring as described above (particularly (1) to (3)), in the search process, both the “operation group” object and the “equipment” object can be regarded as “monitoring targets”. That is, it is possible to realize three search methods: a method of searching as “monitoring target”, a method of searching as “operation group”, and a method of searching as “equipment” without providing another search method. Therefore, the operator can execute the search without recognizing the difference.

  Further, as shown in (3), the physical inclusion relationship such as the positional relationship of the monitoring object must be unique due to the constraints of the tree structure, so that the “monitoring object” interface 32 as shown in (2). Therefore, it is assumed that the “operation group” class 39 has no inclusion relationship. That is, when searching for a physical monitoring object (for example, “valve”, “valve”) from a logical group (for example, “interlocking relationship”), the “operation group” class 39 is “ With reference to the “monitoring target” interface 32, it is possible to indicate the monitoring target object of the “facility” class 36 that inherits the “monitoring target” interface 32.

  By constructing a tree-structured database using the object class structure having these characteristics, other tables, links to other databases, etc. are set for logical groups in accordance with the physical inclusion relationship. It is possible to represent the data with one data structure.

  In the following, an example of search processing using the object class configuration shown in FIG. 3 will be described. However, the search processing method is not limited to the method described below. By using the object structure described above, it can be handled as a data structure that integrates physical inclusion relations and logical groups, so links to other databases, tables, etc., as well as physical inclusion relation retrieval methods. Since the logical group search process can also be performed without referring to, the search process can be simplified.

  First, FIG. 6 shows a flowchart for searching for an object having a certain name in the method in the “object search” class 34. This search returns an object with a name (a character string representing a name) delimited by a given delimiter or a null value as a result.

  As described above, the search in the present embodiment is to search for an object to be operated, and how to monitor and control each monitored object after the search separately includes classes, methods, etc. Is different from the object of the present invention.

  First, a character string to be searched is input. If the given character string is not null (S101: No), it is determined whether or not the first element of the given character string matches the root node name of the tree structure (S102). : Yes), the root node of the tree structure is registered as a search result (S103). On the other hand, if the given character string is null (S101: Yes) and if the first element of the given character string does not match the root node name of the tree structure (S102: No), the search result is null. Is returned (S104).

  Next, it is determined whether the reference position of the character string element is the second from the end (S105). For example, the determination is performed by counting and storing the number of character string elements delimited by delimiters in advance, setting a counter and counting from 0 (see S109), referring to the numerical value of the counter, If is a value smaller by one than the number of character string elements, it can be determined that the reference position is the second from the end. Note that the bottom element may not be the “inclusion relation node” interface 35, so this determination is made (see S 106).

  If it is not the second from the end (S105: No), it is determined whether the search result is the “inclusion relation node” interface 35 (S106). If it is the “inclusion relation node” interface 35 (S106: Yes), the search result is obtained. Is registered in the “search target node” (S108). On the other hand, if it is not the “inclusion relation node” interface 35 (S106: No), null is returned as a result (S107).

  Next, the reference position of the character string element is advanced by one (S109), and an object having the name of the character string element referred to from among those included in the search target node is registered as a search result (S110). Return to S105. The search target node is a node that is a starting point when searching for a name corresponding to a name in a given character string from among its lower nodes. On the other hand, although the node corresponding to the finally given character string is included in the search result, the node on the path that reaches the final result is included during the search. The search result is the “monitoring target” interface 32, and the search target node is the “inclusion relation node” interface 35, and this processing is performed because the object classes are different.

  On the other hand, if it is the second from the end (S105: Yes), it is determined whether or not the final element of the given character string matches the object name registered in the search result (S111). (S111: Yes) The search result is returned (S112). If there is no match (S111: No), there is no search result, so null is returned as a result and the process ends (S113).

  Next, FIG. 7 shows a flowchart for selecting a corresponding object when a method in the “object search” class 34 sets a search range (see FIG. 5) and search conditions starting from a certain object. The object that is the starting point of the search is specified using a name, and the object is specified by the procedure shown in FIG.

  First, the “search” method of the “object search” class 34 having the procedure shown in FIG. 6 with the given character string as an argument is activated (S201), and the return value of the method is substituted into the search origin object (S202). ).

  Next, it is determined whether or not the search starting object is empty (S203). If it is empty (S203: Yes), the process ends as it is, but if it is not empty (S203: No), a process of collecting objects existing in the search range (S204, see FIG. 8) is performed. Further, an object that does not satisfy the search condition is deleted from the collected objects (S205), and the remaining object is used as a search result (S206).

  Next, FIG. 8 shows a detailed flowchart of the process of collecting the objects existing in the search range in the “equipment accommodation” class 40 and collecting the objects existing there (hereinafter also referred to as “collecting objects in the search range”, S204). Show.

  If the subtree is in the search range (S301: Yes), it is determined whether or not there is an “equipment” object at the lower level (S302). If it exists (S302: Yes), the lower level “equipment” that has not been searched for. It is determined whether or not an object remains (S303). This process is realized by the method of the “equipment accommodation” class 40, and the “equipment accommodation” class 40 has a reference to the “equipment” class 36 located at the lower level of the tree structure. Therefore, if there is no reference, it can be determined that there is no “facility” object in the lower order.

  On the other hand, when the subtree below the search starting point is not in the search range (S301: No), the process ends.

  If there is a subordinate “facility” object that has not been searched (S303: Yes), one of the subordinate “equipment” objects is set as a search target (S304), and the search target object is the “equipment accommodation” class. It is determined whether it is 40 (S305). If it is “equipment accommodation” class 40 (S305: Yes), “object collection within search range” to be searched is recursively executed (S306). On the other hand, if it is not “equipment accommodation” class 40 (S305: No), the search target is added to the result list (S307) and the process returns to S303.

  On the other hand, when there is no “equipment” object at the lower level (S302: No) and when there are no lower “equipment” objects that have not been searched (S303: No), there is a lower “operation group” object. (S308: Yes), if it exists (S308: Yes), it is determined whether there are any subordinate “operation group” objects that have not been searched (S309). If they exist (S309: Yes) Then, one of the subordinate “operation group” objects is set as a search target (S310), and “search object collection within search range” of the search target is recursively executed (S311).

  On the other hand, when there is no “operation group” object at the lower level (S308: No) and when there is no lower “operation group” object that has not been searched (S309: No), this method is executed. The object is added to the result list and the process is terminated.

  As described above, in “collection of objects within search range”, “collection of objects within search range” is executed recursively along the data structure (S306, S310), and the obtained objects are stored in the result list. (S312).

  Next, FIG. 9 shows a flowchart of processing for adding a certain object as an inclusion target in the “facility accommodation” class 40.

  First, it is determined whether the given object is the “equipment” class 36 (S401). If the given object is the “equipment” class 36 (S401: Yes), the “equipment” having the same name as the name of the given object is determined. It is determined whether the object has already been registered (S402).

  If it is not registered (S402: No), it is registered as “equipment” containing the given object (S404), the path name of the given object is set (S406), and the given object This object is registered as a parent node of (S408). On the other hand, if it has already been registered (S402: Yes), the process ends.

  On the other hand, if the given object is not the “equipment” class 36 (S401: No), it is determined whether or not the “operation group” object 39 having the same name as the given object name has already been registered. (S403).

  If not registered (S403: No), it is registered as an “operation group” containing the given object (S405), and the path name of the given object is changed (S407). On the other hand, if it has already been registered (S403: Yes), the process ends as it is.

  In this way, by distinguishing between the case where the type of the object to be included is the “facility” object 36 representing a physical monitoring object and the case of the “operation group” object 39 that is a logical group, The uniqueness of the object name in the tree structure is ensured, and the “operation group” object can be handled as a component of the data structure that can use the same search method as the tree structure.

  Next, FIG. 10 shows an example of a flowchart when an object in the “operation group” class 39 is added as an inclusion target.

  In this process, it is determined whether or not a “monitoring target” object having the same name as the given object name has already been registered (S501). If not registered (S501: No), the given object Is registered (S502), and the process ends. However, if registered (S501: Yes), the process ends.

  As described above, in the “operation group” class 39, the uniqueness of the name in the entire tree structure does not matter, and therefore, the processing can be performed with a simpler procedure than the “equipment” class shown in FIG. .

  The above-described embodiment is a preferred embodiment of the present invention, but is not limited thereto, and various modifications can be made without departing from the gist of the present invention.

It is a figure which shows an example of the hardware constitutions of a monitoring control system. It is a figure which shows an example of the hierarchical structure in the database management system of this embodiment. It is a class diagram which shows the relationship of the object class of the database management system of this embodiment. It is an example of the figure for demonstrating the character string showing the name of an object. It is an example of the figure for demonstrating a search range. It is a flowchart which shows an example of the process which searches the object which has a certain name using the object class structure shown in FIG. It is a flowchart which shows an example of the process which searches an applicable object when a search range and search conditions are set from a certain object. 12 is a flowchart illustrating an example of a process of collecting objects existing in a search range in the “facility accommodation” class. 10 is a flowchart illustrating an example of processing for adding an object as an inclusion target in the “facility accommodation” class. 12 is a flowchart illustrating an example of processing for adding a certain object as an inclusion target in an “operation group” class.

Explanation of symbols

1 monitoring control system 10 database management system 32 “monitoring target” interface 35 “inclusion relation node” interface 36 “facility” class 39 “operation group” class 40 “facility accommodation” class

Claims (2)

  In a database management system in a monitoring control system that defines a monitoring object to be monitored and controlled as an object class, and uses the object for monitoring control of the monitoring object, the database has a physical inclusion relationship of the monitoring object. While maintaining the tree structure to be represented, at least the “equipment” class representing the monitored object and the “operation group” class representing the logical group for logically classifying the monitored object in the operation of the monitoring control work Both define the format of the methods possessed by the “facility” class, which is an object class representing a monitoring target, the “operation group” class, and the “facility accommodation” class that manages the logical and physical relationship together. Inheriting the "monitoring target" interface, the "operation group" class It is possible to be included in the “accommodation” class, and further, by referring to the “monitoring target” interface, inheriting the “inclusion relation node” interface that defines the processing when it becomes a parent node of the tree structure; The “facility accommodation” class includes zero or more “equipment” classes and zero or more “operation group” classes, and further inherits the “monitoring target” interface. A database management system characterized by having a data structure.   A method for managing a database in a monitoring control system that defines a monitoring object to be monitored and controlled as an object class and uses an object for monitoring control of the monitoring object, the physical inclusion relationship of the monitoring object being While maintaining the tree structure to be represented, at least the “equipment” class representing the monitored object and the “operation group” class representing the logical group for logically classifying the monitored object in the operation of the monitoring control work Both define the format of the methods possessed by the “facility” class, which is an object class representing a monitoring target, the “operation group” class, and the “facility accommodation” class that manages the logical and physical relationship together. Inheriting the “monitoring target” interface, the “operation group” class is changed to the “facility accommodation” class. In addition, referring to the “monitoring target” interface, inheriting the “inclusion relation node” interface that defines the processing in the case of becoming the parent node of the tree structure, and the “facility accommodation” class Includes a data structure using an object class structure including zero or more “facility” classes and zero or more “operation group” classes, and further inheriting the “monitoring target” interface. A database management method characterized by comprising a database.

Images