JP4657986B2 - Supervisory control system - Google Patents

Description

  The present invention relates to a monitoring control system for displaying messages such as device state changes and alarms in a monitoring control system such as a plant.

  In a conventional monitoring control system such as a plant, messages such as device state changes and alarms are sorted in time series and displayed on one screen (for example, see Patent Document 1). Alternatively, messages are sorted and displayed on a plurality of screens depending on the type and importance of the message (see, for example, Patent Document 2).

JP 09-198130 A JP 08-339225 A

  In a conventional monitoring control system such as a plant, the number of messages that can be displayed on the screen of the display unit is about several tens of lines due to restrictions such as the size of the screen of the display unit, the size of characters, and the screen resolution. Therefore, when several tens or more messages are displayed in the message list, a method of switching the display range by page switching or scrolling is used. However, this alone has poor operability and visibility when the amount of messages is large, so it is necessary to reduce the number of messages displayed by some means. On the other hand, in the past, messages displayed on a single screen were reduced by allocating messages to multiple list screens according to the type and importance of the message. To view messages of different types and importance However, there is a problem in that operability and visibility are poor because it is necessary to switch screens or open a plurality of screens. In addition, when a series of state changes can be assumed in advance, such as when operating a device, whether or not the expected series of state changes matches the actual state change is indicated on the message list. Each message has to be confirmed individually, which is troublesome.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a monitoring control system with good operability and visibility in monitoring by a monitored control unit.

The present invention relates to a scenario created by combining position data for each input / output of a monitored control unit in time series to control the monitored control unit in a monitoring control system for monitoring the monitored control unit Scenario data management means for accumulating and managing data, history accumulation means for accumulating input / output information of the monitored control unit as history data in units of position data, and history data accumulated in the history accumulation means And a history analysis means for generating a message list by analyzing a portion matching the scenario data from
The message list of the history analysis means is set as an aggregate list in which the portions corresponding to the scenario data in the history data are aggregated .

The supervisory control system of the present invention is a supervisory control system for monitoring a monitored control unit, and creates position data for each unit with respect to the input / output of the monitored control unit in time series to control the monitored control unit Scenario data management means for accumulating and managing stored scenario data, history storage means for accumulating input / output information of the monitored control unit as history data in units of position data, and accumulation in the history accumulation means A history analysis means for generating a message list by analyzing a portion matching the scenario data from the recorded history data,
Message list of the history analysis means, Runode is set as an aggregate list of aggregate portion corresponding to the scenario data of the historical data, by aggregating messages based on the scenario data, and displays the list The number of messages can be reduced and visibility and operability can be improved.

Embodiment 1 FIG.
Embodiments of the present invention will be described below. 1 is a diagram showing a configuration of a monitoring control system according to Embodiment 1 of the present invention, FIG. 2 is a diagram showing a record configuration of position data in the monitoring control system shown in FIG. 1, and FIG. 3 is a monitoring configuration shown in FIG. FIG. 4 is a diagram showing a record configuration of history data in the control system, FIG. 4 is a diagram showing a configuration of scenario data in the monitoring control system shown in FIG. 1, and FIG. 5 is a current position data having the position data configuration shown in FIG. FIG. 6 is a diagram showing an example of scenario data in the monitoring control system shown in FIG. 1, and FIG. 7 is an example before aggregation of the message list of history data in the message list display means shown in FIG. FIG. 8 is a diagram showing an example of a message list aggregation display method in the message list display means shown in FIG.

  In FIG. 1, a monitoring control system 100 performs monitoring control on a monitored control unit 4 composed of a plant composed of a plurality of devices, for example, and an input unit 12 that receives an input of a control command from an operator, A control output processing means 8 for performing a control output to the monitored control section 4 based on an input received by the input section 12, a monitoring input processing means 9 for obtaining and processing a monitoring input from the monitored control section 4, History storage means 7 for inputting control output of the control output processing means 8 and monitoring input data of the monitoring input processing means 9 and storing the data as history data in time series for each position data, and position data for managing and managing the position data Management means 10, scenario data management means 6 for storing and managing scenario data, history storage means 7 based on position data and scenario data The history analysis unit 5 that analyzes the history data stored in the message list and creates a message list, and the message list display that performs display processing on the display unit 3 that displays the message list analyzed by the history analysis unit 5 on the screen And means 11.

  In FIG. 2, the record structure of the position data is composed of a position ID 21, a data name 22, and a status 23. Here, “position data” is a minimum unit of information handled in the monitoring control system 100, and handles input / output to the monitored control unit 4, various statuses handled in the monitoring control system 100, and the like as position data. One record of position data is assigned to one piece of position data. The position ID 21 is a unique number among all the position data in the position data record. The data name 22 is a name used when displaying the change history of the position data in the message list. The status 23 holds the current state of the position. FIG. 5 shows an example of position data indicating the current state. For example, the position data of position ID = 2002 indicates that the data name = “switch 1 open / close state input” and the current state (status) is “open”. Show.

  In FIG. 3, the record structure of history data stores an index 31, an occurrence time 32 indicating the time when input / output occurred, a position ID 33 indicating the correspondence with the position data, and an input / output state (ON / OFF). Status 34, an aggregation ID 35 used for aggregate display, and an aggregation flag 36. The history data is configured in this way, and holds the change in status of each position in time series together with the time when the change occurred.

  In FIG. 4, the scenario data is composed of an index 41 indicating the order of occurrence of the scenario (time series), a position ID 42 indicating the correspondence between the position data stored and managed by the position data management means 10, and The status 43 representing the state (ON / OFF) of the data, and the aggregation flag 44 indicating which data is aggregated when being aggregated and displayed on the message list. Scenario data is assumed to occur in a predetermined order (time series), such as when a switch is operated, for example (when the monitored control unit 4 is controlled in advance) Change of the series of position data) is registered in advance, and it is assumed that the position data of the position ID 42 changes to the status 43 in the order of the index 41. Is. One scenario data is composed of a plurality of scenario data records 45 and a scenario ID 46 that is unique among all scenario data.

  FIG. 6 shows an example of scenario data, which consists of scenario data records in which one scenario data is composed of five position data. Then, for example, the record with index = 01 indicates “switch 1 selection output, ON” by comparing with the position data of FIG. 5 stored and managed in the position data management means 10 based on the position ID. I understand. In the example of FIG. 6, “switch 1 selection output ON is output to the monitored control unit 4 (switch 1 is selected in the monitored control unit 4)” → “switch 1 selection state input ON is monitored control unit 4 ”input” → “Switch 1 control output closed to the monitored control unit (switch 1 in the monitored control unit 4 changes to open / closed state closed)” → “Switch 1 open / closed state input closed monitored control This is an example of a control scenario for the switch 1 such as “input from the unit” → “determined that the control result of the switch 1 is“ successful ”within the monitoring control system”.

  Next, the operation of the monitoring control system of the first embodiment configured as described above will be described. First, when control is performed, a control command from an operator is received by the input unit 12, and a control command is output to the monitored control unit 4 by the control output processing unit 8, and information on the control output is stored as history data in the history storage unit. 7 is accumulated in time series. On the other hand, the status and alarm of each device in the monitored control unit 4 are input by the monitoring input processing means 9, and the input information is stored in the history storage means 7 in time series as history data. Next, the history analysis means 5 accesses the scenario data of the scenario data management means 6 and the position data of the position data management means 10, and from the history data stored in the history storage means 7, a series of positions indicated by the scenario data. It is searched whether there is history data that matches the change in the status of the data.

  Specifically, for each scenario data record 45 of the scenario data, data with a matching position ID and status is searched from the history data. In this search, when the scenario data with index = n matches the history data with index = m, the search range of scenario data with index = n + 1 is newer than that, that is, index = 1 to m−1. Then, regarding all scenario data records of the scenario data, when a matching record is found in the history data, the scenario data is considered to match the history data. When the scenario data and the history data match, a unique ID is set as the aggregation ID 35 of each record of the matched history data. When there are a plurality of portions in the history data that match certain scenario data, different aggregation IDs are set. Further, the history data aggregation flag of the scenario data record 45 corresponding to the scenario data aggregation flag = 1 is set to 1.

  For example, when changes in position data are accumulated in the history data as shown in FIG. 7, the position ID, status, and generation order are analyzed using the position ID as a key, and the indexes in FIG. 6 = 01, 02, 03, 04 , 05 detect that the history data index of FIG. 7 is equal to 0008, 0007, 0005, 0004, 0003, respectively. Therefore, the history data in FIG. 7 has data that matches the scenario data No. 001 in FIG. For this reason, a unique ID (for example, 01) is set as the aggregation ID of records of history data index = 0008, 0007, 0005, 0004, 0003. Here, an example is shown in which the portion matching the scenario data No. 001 is one place in the history data. However, when there are a plurality of places, a different aggregation ID, for example, an aggregation ID 02 is set. Further, since the aggregation flag of the scenario data index = 05 is 1, the aggregation flag of the corresponding history data index = 0003 is set to 1.

  Next, the operation of the message list aggregation display method will be described. Normally, the position data retrieved from the position ID of the history data is retrieved by the position data management means 10, and the data name is acquired. Then, as shown in FIG. 8C, a message list is created, and the message list display means 11 displays it on the display unit 3. Here, if there is history data having the same aggregation ID in the history data, a message list that displays only the history data of the aggregation flag 1 is created among them as shown in FIG. A history data record of 0 is not displayed in the message list. As a result, messages can be aggregated and displayed. The aggregated message is displayed with a specific symbol in the corresponding line of the message list so that it can be distinguished from other displays so that it can be seen that it has been aggregated. For example, as shown in FIG. 8D, in the example of the message list (after aggregation), the symbol “■” is displayed at the left end of the row of the aggregated message, thereby indicating the aggregation display. . In addition to the display by analysis of the history analysis unit 5, the message list display unit 11 displays the history data as it is from the history data of the history storage unit 7 and the position data of the position data management unit 10 on the display unit 3 as in the past. Needless to say, it can also be displayed.

  According to Embodiment 1 configured as described above, it is possible to create a message list by analyzing whether scenario data is included in the history data based on predefined scenario data, Also, history data on the message list can be aggregated for each scenario data, so even if there is a lot of history data displayed on the message list, the number of history data can be reduced by aggregation, screen switching etc. Fewer operations. Furthermore, since the number of history data is small, the visibility is excellent.

  In the first embodiment, the position data management means is provided and the position data is stored and managed for each position ID, and the stored data and scenario data are analyzed using the position ID as a key. For example, the data name of the position data is directly stored instead of the position ID of the scenario data and the accumulated data, and the accumulated data and the scenario data are analyzed with the data name of the position data. Although it is not efficient as compared with the case where the position ID is used as a key, it is needless to say that the same effect can be obtained as in the first embodiment.

  In the first embodiment, the “■” symbol is displayed in the message line aggregated on the message list to indicate that the line is aggregated. However, the present invention is not limited to this. Any setting can be adopted as long as it can be distinguished from other displays. Other symbols are displayed in place of the “■” symbol, or the font and font of the relevant line are different from the font and font of other lines. Display different from unaggregated messages, such as changing, changing the text color or background color of the line to the color or background color of another line, or displaying an underline only on the line Various examples can be considered, and it goes without saying that the same effects as those of the first embodiment can be obtained.

Embodiment 2. FIG.
FIG. 9 is a diagram showing a record structure of the history data of the supervisory control system in the second embodiment of the present invention, and FIG. 10 shows an example of a message list aggregation display method of the supervisory control system in the second embodiment of the present invention. FIG. In the figure, the same parts as those in the first embodiment are denoted by the same reference numerals, and the description thereof is omitted. In the second embodiment, as shown in FIG. 9, the record structure of the history data is a case where the non-scenario flag 37 is added in the case of the first embodiment.

  Next, the operation of the monitoring control system according to the second embodiment configured as described above will be described with respect to differences from the first embodiment. First, the scenario data and the history data are analyzed as in the first embodiment. If history data that does not match the scenario data is included between the history data corresponding to the first record of the scenario data and the history data corresponding to the last record of the scenario data, the scenario of that history data Set the outside flag to 1. Then, when displaying the message list, a specific symbol is displayed in the corresponding line of the message list so that the history data with the non-scenario flag = 1 indicates that the message is outside the scenario data. For example, as shown in FIG. 10 (a), there is history data (index = 0006) that does not match scenario data in history data (index = 0003 to 0008) that matches scenario data. The flag is set to 1. Further, in the message list (after aggregation) in FIG. 10D, a “Δ” symbol is displayed at the left end of the message line outside the scenario to indicate that the message is outside the scenario.

  According to the second embodiment configured as described above, the scenario data and the actual input / output data (history data) are compared as well as the same effects as the first embodiment. By notifying the operator of excess or deficiency, unexpected input / output can be easily found.

  In the second embodiment, the “△” symbol is displayed in the message line outside the scenario data on the message list to indicate that the line is outside the aggregated scenario data. It is not limited, and any setting can be adopted as long as it can be distinguished from other displays. Other symbols are displayed instead of the “△” symbol, or the font and font of the line are changed to other lines. Scenario data such as changing the font or font of the current line, changing the color or background color of the line to the color or background color of another line, or displaying an underline only on the line Various examples are possible such as displaying differently from other messages, and it goes without saying that the same effects as those of the second embodiment can be obtained.

It is a figure which shows the structure of the monitoring control system in Embodiment 1 of this invention. It is a figure which shows the record structure of the position data of the monitoring control system shown in FIG. It is a figure which shows the record structure of the historical data of the monitoring control system shown in FIG. It is a figure which shows the structure of the scenario data of the monitoring control system shown in FIG. It is a figure which shows the example in the position data shown in FIG. It is a figure which shows the example in the scenario data shown in FIG. It is a figure which shows the example in the log | history data shown in FIG. It is a figure which shows the example of a display of the message list of the monitoring control system shown in FIG. It is a figure which shows the record structure of the historical data of the monitoring control system in Embodiment 2 of this invention. It is a figure which shows the example of a display of the message list of the monitoring control system shown in FIG.

Explanation of symbols

3 display unit, 4 monitored control unit, 5 history analysis unit, 6 scenario data management unit,
7 history storage means, 8 control output processing means, 9 monitoring input processing means,
10 position data management means, 11 message list display means, 12 input section,
21 Position ID, 22 Data name, 23 Status, 31 Index,
32 Time of occurrence, 33 Position ID, 34 Status, 35 Aggregation ID,
36 aggregation flag, 37 non-scenario flag, 41 index,
42 Position ID, 43 Status, 44 Aggregation flag,
45 Scenario data record, 46 Scenario ID, 100 Monitoring and control system.

Claims (6)

In the monitoring control system for monitoring the monitored control unit, scenario data created by combining the position data for each input / output of the monitored control unit in time series to control the monitored control unit. Scenario data management means for accumulation management, history accumulation means for accumulating input / output information of the monitored control unit as history data in units of the position data in time series, and history accumulated in the history accumulation means A history analysis means for analyzing the portion matching the scenario data from the data and creating a message list ,
The monitoring control system according to claim 1, wherein the message list of the history analysis means is set as an aggregate list in which portions corresponding to the scenario data in the history data are aggregated. In the monitoring control system for monitoring the monitored control unit, scenario data created by combining the position data for each input / output of the monitored control unit in time series to control the monitored control unit. Scenario data management means for accumulation management, history accumulation means for accumulating input / output information of the monitored control unit as history data in units of the position data in time series, and history accumulated in the history accumulation means A history analysis means for analyzing the portion matching the scenario data from the data and creating a message list,
The history analysis means analyzes the position data that does not match the scenario data existing between the position data that matches the scenario data in the history data, and the message list of the history analysis means includes the scenario data A monitoring control system, wherein the display of the position data not matching the above is set to be distinguished from other displays. In the monitoring control system for monitoring the monitored control unit, scenario data created by combining the position data for each input / output of the monitored control unit in time series to control the monitored control unit. Scenario data management means for accumulation management, history accumulation means for accumulating input / output information of the monitored control unit as history data in units of the position data in time series, and history accumulated in the history accumulation means A history analysis means for analyzing the portion matching the scenario data from the data and creating a message list,
The message list of the history analysis means is set as an aggregate list in which portions corresponding to the scenario data in the history data are aggregated,
The history analysis means analyzes the position data that does not match the scenario data existing between the position data that matches the scenario data in the history data, and the message list of the history analysis means includes the scenario data A monitoring control system, wherein the display of the position data not matching the above is set to be distinguished from other displays. Said scenario data are all of claims 1 to 3, characterized in that any of said position data of said each position data included in the scenario data to use to the aggregate list is set monitoring and control system according to any one of claims. Message list of the history analysis means, according to claim 1 to claim 4 any one, characterized in that the display of any of the message list is set to distinguish the display of the other if it were the aggregate list The monitoring control system described in 1. 6. The monitoring control system according to claim 1, further comprising message list display means for displaying the message list on a display unit.

Images