JP2023069729A - Information design assisting device, information design assisting method, and program - Google Patents

Abstract

To reduce the time and labor of an operation performed by a monitor of a plant to obtain concerned information.SOLUTION: An information design assisting device according to an embodiment of the present invention assists in designing information related to a power facility as information including an object class and a concern combined with each other. The information design assisting device includes a UI editing unit and a UI providing unit. The UI editing unit provides an interface for creating a UI by combining a plurality of components with respect to a combination of the object class and the concern. The UI providing unit causes a display unit to display the UI created for the combination of the object class and the concern.SELECTED DRAWING: Figure 12

Description

TECHNICAL FIELD Embodiments of the present invention relate to an information design support device, an information design support method, and a program.

2. Description of the Related Art Conventionally, there is known a technique for customizing a display screen of a plant monitoring system in order to efficiently monitor the operation status of a plant installed as power equipment or the like. For example, U.S. Pat. No. 6,200,000 discloses a graphical composition system that allows quick editing of reusable graphical elements when creating display graphics for use in user displays of plant monitoring systems.

In the technology described in Patent Document 1, a lead graphics designer of a graphical configuration system creates a template graphical element having a quick configuration form, and another graphics designer edits the quick configuration form, to obtain the desired graphical element. As described above, the conventional technology customizes an interface for monitoring the operational status of a plant in units of data items. It does not model. As a result, plant supervisors may have had to perform tedious operations to obtain information of interest.

JP 2015-130174 A

The problem to be solved by the present invention is to provide an information design support device, an information design support method, and a program that can reduce the labor of operations to be performed by a plant supervisor to acquire information of interest. to provide.

An information design support apparatus according to an embodiment includes an object class that is information obtained by categorizing information about power equipment, which is social infrastructure equipment, by defining a plurality of data items for the type of the power equipment, and an object class for the power equipment. It supports designing information that combines one or more concerns, which are information that expresses the user's interest. The information design support device includes a UI editor and a UI provider. The UI editor provides an interface for creating a UI (user interface) by combining a plurality of components for the combination of the object class and the concern. The UI providing unit causes the display unit to display the UI created for the combination of the object class and the concern.

The figure which shows an example of a structure of the system 1 containing the information provision apparatus 100 of embodiment. 4 is a diagram showing an example of a definition of an object class 160B stored in a storage unit 160; FIG. FIG. 4 is a diagram showing an example of the configuration of an object class/concern correspondence map 160C stored in a storage unit 160; 4 is a diagram showing an example of a definition of a UI class 160D stored in a storage unit 160; FIG. 5 is a diagram showing an example of information provided according to UI class 160D shown in FIG. 4; FIG. FIG. 10 is a diagram showing another example of the configuration of an object class/concern correspondence map 160C stored in the storage unit 160; FIG. 4 is a diagram showing an example of data provided corresponding to concerns having an inclusion relationship; FIG. 4 is a diagram showing an example of data provided corresponding to concerns having transition relationships; FIG. 4 is a diagram showing an example of data provided corresponding to concerns having an associative relationship; FIG. 5 is a diagram showing another example of data provided corresponding to concerns having an associative relationship; 4 is a flowchart showing an example of the flow of processing executed by the information providing apparatus 100; The figure which shows an example of a structure of the system 1 containing the information provision apparatus 100 of embodiment, and the information design support apparatus 200. FIG. FIG. 13 shows an example interface for creating a UI class 230C by combining multiple UI components 230B. FIG. 13 shows another example of an interface for creating a UI class 230C by combining multiple UI components 230B. FIG. 13 shows another example of an interface for creating a UI class 230C by combining multiple UI components 230B. The figure which shows an example of the interface for defining the containment relationship of concern to UI class 230C. FIG. 11 is a diagram showing an example of an interface for defining concern transition relationships in a UI class 230C; FIG. 10 is a diagram showing an example of an interface for defining an associative relationship of concerns in the UI class 230C; FIG. 10 is a diagram showing an example of an interface for defining an associative relationship of concerns in the UI class 230C;

An information design support apparatus, an information design support method, and a program according to embodiments will be described below with reference to the drawings.

[overall structure]
FIG. 1 is a diagram showing an example of the configuration of a system 1 including an information providing device 100 of an embodiment. As shown in FIG. 1, the system 1 includes, for example, a power facility 10, a terminal device 50, and an information providing device 100.

The power facility 10 is, for example, a power plant, and the power plant includes power equipment such as generators, turbines, pumps, valves, and boilers. In the following description, the power facility 10 is assumed to be a power plant, but the present invention is not limited to such a configuration, and generally applies to facilities having a plurality of monitored equipment. be able to.

The terminal device 50 is, for example, a computer device such as a personal computer, a tablet terminal, or a smart phone. The terminal device 50 accesses the information providing device 100 via the network NW and acquires information on each power facility installed in the power facility 10 . The user of the terminal device 50 browses the acquired information about each power equipment using a web browser of the terminal device 50 or the like.

In the prior art, when a user browses information about each power facility, the user designates the name and identification id of the power facility that the user wishes to browse information for, which is determined for each power facility 10, on the terminal device 50. After that, each data item of the applicable power equipment was confirmed. In other words, the conventional technology provides users with information on power equipment in units of data items. Units of information (that is, "concept-level" units) in which data items are organized organically based on the user's interests do not provide information to the user. As will be described in detail below, the information providing apparatus 100 of the embodiment includes an object class, which is information categorized by defining a plurality of data items for the type of power equipment, and information representing the user's interest in the power equipment. By providing information on electric power facilities based on information combined with a concern, it is possible to provide users with information on a "conceptual level" basis.

[Configuration of Information Providing Device]
The information providing device 100 is a server device that provides the terminal device 50 with information about each power facility installed in the power facility 10, and includes, for example, an information acquisition unit 110, an object class identification unit 120, and a concern reception unit 130. , an information provision type determination unit 140 , an information provision unit 150 , and a storage unit 160 . The information acquisition unit 110, the object class identification unit 120, the concern reception unit 130, the information provision type determination unit 140, and the information provision unit 150 are configured by a hardware processor such as a CPU (Central Processing Unit), for example, a program (software ) is implemented by executing Some or all of these components are hardware (circuit part; circuitry) or by cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as a HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium) and installed by mounting the storage medium in the drive device. The storage unit 160 is, for example, an HDD, a flash memory, a RAM (Random Access Memory), or the like. The storage unit 160 stores, for example, time-series data 160A, an object class 160B, an object class/concern correspondence map 160C, and a UI class 160D. In this embodiment, for convenience of explanation, an example in which the functions of the information providing apparatus 100 are realized by a single physical server will be explained, but the present invention is not limited to such a limitation. For example, the functions of the information providing apparatus 100 may be implemented as software on a cloud platform provided by multiple physical servers.

The information acquisition unit 110 acquires time-series data about each power facility from the power facility 10 via the network NW, and stores it in the storage unit 160 as time-series data 160A. For example, the information acquisition unit 110 acquires time-series data such as the flow rate, head, and ON/OFF state of a pump installed in the power facility 10, and the opening degree, temperature, and ON/OFF state of a valve installed in the power facility 10. time-series data, and time-series data such as the rotation speed, output, and ON/OFF state of the turbines installed in the power facility 10 are acquired.

Although not shown in FIG. 1, the storage unit 160 stores in advance facility ledger data of each power facility installed in the power facility 10 in addition to the time-series data 160A. The facility ledger data means data for managing each power facility of the power facility 10 . For example, in the case of a pump, the equipment ledger data includes data such as an identification number, model number, production number, manufacturer, manager, date of introduction, and the like. The facility ledger data may be updated by the information acquiring unit 110 periodically receiving the latest data from the power facility 10, or may be manually input and updated by the administrator of the information providing apparatus 100. good.

The object class identification unit 120 is used when the user designates the name or identification id of the power equipment for which information is desired to be viewed on the terminal device 50, or when a predetermined event (such as an accident) occurs in the power equipment. Accordingly, the object class 160B corresponding to the power equipment is specified. For example, when the user inputs or selects the identification id of the condensate pump on the terminal device 50, the object class identification unit 120 determines the correspondence relationship between the previously stored identification id and the object class 160B. to identify the object class 160B corresponding to the condensate pump. In addition, for example, when a predetermined event occurs for power equipment, the object class identifying unit 120 determines whether the event occurs based on the correspondence relationship between the identification information of the power equipment and the object class 160B stored in advance. Identify the object class 160B corresponding to the generated power equipment.

FIG. 2 is a diagram showing an example of the definition of the object class 160B stored in the storage unit 160. As shown in FIG. FIG. 2 shows the definition of the object class 160B for Pump A as an example. As shown in FIG. 2, the object class 160B is, for example, information in which properties and formats are associated with each other. In the case of FIG. 2, the object class 160B of the pump A includes items such as identification number, model number, serial number, manufacturer, person in charge, status, introduction date, flow rate, and head as properties. The identification number is, for example, a string type number for uniquely identifying the power equipment. The model number is, for example, a number that has a character string type and identifies the model of the power equipment. The product number is, for example, a number that has a numeric type and is used to specify the product number of power equipment. The manufacturer is, for example, a character string type and is information for specifying the manufacturer that manufactured the power equipment. The person in charge is, for example, a string type information for specifying the person in charge of managing the power equipment. The state has a boolean type, for example, and takes a value of true when the power equipment is in an operating state, and a value of false when the power equipment is in a stopped state. The installation date is, for example, date-type information indicating the date when the power facility was installed in the power facility 10 . The flow rate has, for example, a numeric type, and is information indicating the discharge amount of liquid that can be discharged per unit time when the pump is operated. The head is, for example, information that has a numeric type and indicates the height at which the pump pumps up the liquid. In the case of a pump having the object class 160B of pump A defined in FIG. The information acquisition unit 110 acquires the flow rate and the head from the power facility 10, and stores them in the storage unit 160 as the time-series data 160A.

When the user designates the name or identification id of the power equipment for which information is to be viewed on the terminal device 50, or when a predetermined event (for example, an accident) occurs in the power equipment, the concern reception unit 130 , the user's interest in the information on the power equipment, that is, the concern candidates are displayed on the terminal device 50, and the user's designation of the concern is accepted. Concerns are items of concern that users may have in common for different types of power equipment, such as, for example, "operation status", "work status", and "accident status" of the power equipment. On the other hand, for example, the "operating status" of a pump and the "operating status" of a valve generally differ in the details of the information that the user wishes to view (for example, the "operating status" of the pump is may wish to view the head, but the head is pump-specific information and has nothing to do with valve "running"). Therefore, in this embodiment, for a combination of an object class and a concern, an object class 160D that stores a UI class 160D that defines details of information to be provided to the user and an information output format (text, image, voice, etc.) A /concern mapping map 160C is provided to provide the user with detailed information appropriate to the combination of object class and concern. In other words, for the same concern, different object classes provide the user with different detailed information about the power plant.

The information provision type determination unit 140 searches the object class/concern correspondence map 160C using the combination of the specified object class and the accepted concern, and determines the UI class 160D corresponding to the combination and the output format of the information. to determine. The information providing unit 150 provides the terminal device 50 with information on power equipment according to the determined UI class 160D and information output format. The object class/concern map 160C is an example of a "database", and the UI class 160D and information output format are examples of an "information provision type".

FIG. 3 is a diagram showing an example of the configuration of the object class/concern correspondence map 160C stored in the storage unit 160. As shown in FIG. As shown in FIG. 3, the object class/concern correspondence map 160C associates information such as UI classes (or paths to UI classes) and output formats with combinations of object classes and concerns. In FIG. 3, object classes such as Pump A, Pump B, and Valve A are shown by way of example, but object classes may also include object classes for other power equipment such as turbines, generators, and boilers. Further, in FIG. 3, concerns such as "operation status", "work status", and "accident status" are shown as examples. It can also include other concerns such as "situation". The information provision type determination unit 140 refers to the object class/concern correspondence map 160C to determine the information provision type, thereby providing detailed information on power equipment suitable for the combination of each object class and concern according to the situation at that time. The information can be provided to the user in an output form according to the situation (for example, audio information is output when an accident occurs).

FIG. 4 is a diagram showing an example of the definition of the UI class 160D stored in the storage unit 160. As shown in FIG. FIG. 4 shows, as an example, the definition of a UI class 160D corresponding to a combination in which the object class is pump A and the concern is "operating status". In the left part of FIG. 4, it is defined to display the identification number, model number, manufacturing number, manufacturer, person in charge, status, and introduction date of the pump as equipment information, and in the right part of FIG. , is defined to display a curve showing the relationship between pump flow rate and head. By predefining the detailed format of the information to be provided to the user in accordance with the combination of the object class and the concern, the user can obtain the information of interest by specifying each data item one by one. can be reduced.

FIG. 5 is a diagram showing an example of information provided according to UI class 160D shown in FIG. As shown in FIG. 5, the information providing unit 150 provides the terminal device 50 with the equipment ledger data and the time-series data 160A of the power equipment that the user desires to view, to the UI class 160D. Generate real data. At this time, the information providing unit 150 selects the power equipment to which the data is to be input, the name or identification id of the power equipment specified by the user on the terminal device 50, or a predetermined event (for example, an accident) for the power equipment. It can be identified according to what happened. The information providing unit 150 transmits the generated actual data to the terminal device 50 via the network NW.

In the object class/concern correspondence map 160C of this embodiment, as an example, a UI class is defined for a combination of an object class and a concern, but the present invention is not limited to such a configuration. For example, one UI class may be defined for each concern, and detailed items of the UI class may branch according to the object class to which it is applied. For example, if the UI class 160D in FIG. 4 is generally defined as a UI class corresponding to "operational status", when the UI class is applied to pump A, "person in charge" is displayed, while pump B A branch may be set such that the "responsible" is not displayed when applied to.

[Type of Concern]
Next, with reference to FIGS. 6 to 10, types of concerns defined and displayed in this embodiment will be described. FIG. 6 is a diagram showing another example of the configuration of the object class/concern correspondence map 160C stored in the storage unit 160. As shown in FIG. In addition to the data items defined in the object class/concern correspondence map 160C shown in FIG. 4, the object class/concern correspondence map 160C shown in FIG. 6 further includes data items such as containment relations, transition relations, and association relations. It is a thing.

A containment relation means a relation established between a certain concern and a plurality of concerns obtained by further breaking down the content of the concern. For example, when a user wants to know the "status" of a certain power facility, the user may select "operation status", "work status", "site status" of the power facility as further details of the "status". , and “alarm occurrence status”. That is, interest in "status" can potentially include interest in "operational status," "work status," "site status," and "alarm status." For this reason, the information providing unit 150 has an inclusion relationship in which a certain concern (parent concern) includes another concern (child concern) in the object class/concern correspondence map 160C (that is, the object class/concern correspondence map 160C " other concerns are stored in the "containment relationship" data item), then in addition to the UI class 160D corresponding to the parent concern, the UI class 160D corresponding to the child concern also provides information about the power equipment. Alternatively, if there are multiple child concerns, the UI class 160D corresponding to the parent concern is defined as a combination of UI classes 160D corresponding to multiple child concerns.

FIG. 7 is a diagram showing an example of data provided corresponding to concerns having an inclusion relationship. The left part of FIG. 7 shows the inclusion relationship defined in the first line of the object class/concern correspondence map 160C shown in FIG. 6, and the right part of FIG. Figure 3 shows data about the "status" of Pump A provided. As shown in the left part of FIG. 7, the "situation" concern includes "operation status", "work status", "site status", and "alarm occurrence status" concerns. Therefore, the information providing unit 150 divides the UI class 160D corresponding to the "status" of the pump A into the UI class 160D corresponding to the "operation status" of the pump A and the UI class 160D corresponding to the "work status" of the pump A. , UI class 160D corresponding to the "site situation" of pump A and UI class 160D corresponding to the "alarm occurrence situation" of pump A are combined to define and correspond to the defined "situation" of pump A. Provides information about the pump according to UI class 160D.

More specifically, for example, as shown in the right part of FIG. 7, the information providing unit 150 displays work status, Display information on site conditions and alarm occurrence conditions. In this manner, a display method in which information of the UI class 160D corresponding to a plurality of child concerns is combined and displayed as information of the UI class 160D corresponding to the parent concern is called a "dashboard format". For example, when the user clicks the information of the UI class 160D corresponding to the child concern on the terminal device 50, the information providing unit 150 further details the information corresponding to the child concern (for example, enlarges the information). to display).

A transition relation means a relation that holds between a concern and another concern that the user is supposed to be interested in next after resolving the concern. For example, when a user wants to know the "patrol inspection plan" of a certain power facility, the user is expected to want to "implement the patrol inspection" after confirming the patrol inspection plan. be done. Furthermore, it is assumed that the user wants to perform "diagnostic analysis of deterioration" after performing "perform inspection tour". That is, the interest in "planning inspection tours" potentially transitions to the interest in "implementing inspection tours", and the interest in "implementing inspection tours" potentially transitions to "diagnostic analysis of deterioration". ” can transition to interest. Therefore, in the object class/concern correspondence map 160C, the information providing unit 150 has a transition relation in which a certain concern (pre-transition concern) transitions to another concern (transition destination concern) (that is, the object class/concern correspondence map 160C other concerns are stored in the data item of "transition relation" of ), after providing information about the power equipment according to the UI class 160D corresponding to the pre-transition concern, according to the UI class 160D corresponding to the destination concern, Provide information about power equipment.

FIG. 8 is a diagram showing an example of data provided corresponding to concerns having transition relationships. The left part of FIG. 8 shows the transition relation defined in the eighth and ninth lines of the object class/concern correspondence map 160C shown in FIG. 6, and the right part of FIG. 4 shows data relating to the “patrol inspection plan” of pump A provided by the providing unit 150. FIG. As shown in the left part of Fig. 8, the concern of "planning of patrol inspection" transitions to the concern of "implementation of patrol inspection", and the concern of "implementation of patrol inspection" transitions to the concern of "diagnostic analysis of deterioration". . Therefore, the information providing unit 150 provides information about the pump according to the UI class 160D corresponding to the "planning of patrol inspection" of the pump A, and then provides information about the pump according to the UI class 160D corresponding to the "implementation of the patrol inspection" of the pump A. Provide information and then provide information about the pump according to UI class 160D corresponding to Pump A's "Diagnostic Analysis of Deterioration".

More specifically, for example, as shown in the right part of FIG. The information of the UI class 160D corresponding to "implementation" is displayed, and to the right of it, the information of the UI class 160D corresponding to "diagnostic analysis of deterioration" of pump A is displayed. In this way, the display method of displaying the information of the UI class 160D corresponding to the concern before transition after the information of the UI class 160D corresponding to the concern before transition is called "flow chart form". For example, when the user clicks on the terminal device 50 the information of the UI class 160D corresponding to the pre-transition concern or the transition destination concern, the information providing unit 150 responds to the pre-transition concern or the transition destination concern. The information to be displayed may be displayed in more detail (for example, enlarged).

Regarding the transition relation of concerns in this embodiment, the description "after" does not necessarily mean that the display timing of the information is shifted (that is, the information corresponding to the transition destination concern is displayed at a later timing than the information corresponding to the pre-transition concern). For example, as long as the transition relationship is clearly indicated by notation such as an arrow, the information corresponding to the transition destination concern and the information corresponding to the pre-transition concern may be displayed at the same time. .

An association relationship means a relationship that exists between a concern and another concern that a user is supposed to be interested in in relation to that concern. In that sense, the inclusion relationship and the transition relationship can also be said to be a kind of associative relationship, but the associative relationship means a weaker relationship than the inclusion relationship and the transition relationship. For example, when a user wants to know the "operational status" of a certain power facility, the user may ask the "inventory status" or "patrol inspection plan" of the power facility in relation to the confirmation of the operating status. It is also assumed that you want to check the That is, an interest in "operational status" can potentially be related to an interest in "inventory status" and "planned inspection tours." Therefore, in the object class/concern correspondence map 160C, the information providing unit 150 has an associative relation in which a certain concern (association source concern) relates to another concern (association destination concern) (that is, the object class/concern correspondence map 160C other concerns are stored in the data item of the "association relation" of the association), the information of the UI class 160D corresponding to the association destination concern is displayed in a form linked to the information of the UI class 160D corresponding to the association source concern. do.

FIG. 9 is a diagram showing an example of data provided corresponding to concerns having an associative relationship. The left part of FIG. 9 shows the association defined in the first line of the object class/concern correspondence map 160C shown in FIG. 6, and the right part of FIG. Figure 3 shows data on the "running status" of Pump A provided. As shown in the left part of FIG. 9, the "operational status" concern is related to the "inventory status" and "patrol plan" concerns. Therefore, the information providing unit 150 displays information about the "inventory status" of the pump A and the information about the "patrol inspection plan" in a form that is linked to the information about the "operation status" of the pump A. FIG.

More specifically, the information providing unit 150, for example, as shown in the right part of FIG. Display as selectable. The information providing unit 150 may display information on the "inventory status" and "patrol inspection plan" as a slide and switch the display at predetermined time intervals, or the user may click an arrow displayed on the slide. The display may be switched according to the Such a display method for selectively displaying information on a plurality of associative destination concerns in a slide format is called a "slide show format". For example, the information providing unit 150 provides more detailed information (for example, , enlarged).

FIG. 10 is a diagram showing another example of data provided corresponding to concerns having an associative relationship. For example, as shown in the right part of FIG. 10, the information providing unit 150 selectably displays information on "inventory status" and "patrol inspection plan" below the information on "operation status" of pump A. The information providing unit 150 displays a list of information related to the "inventory status" and the "plan of patrol inspection" as selection items. to display information related to the patrol inspection plan. Such a display method for selectively displaying information on a plurality of associative destination concerns in a list format is called a "navigation format".

7 to 10, for convenience, the information providing unit 150 displays only information on any one of the inclusive relationship, the transitional relationship, and the associative relationship on the screen. However, the present invention is not limited to such a configuration, and if a concern has a plurality of relationships with a plurality of other concerns, the information providing unit 150 displays information regarding all of these relationships on the same screen. You may For example, if a certain concern (first concern) has an inclusion relationship that includes another concern (second concern) and at the same time has an associative relationship with another concern (third concern), the information providing unit 150 may display information about the first concern at the top of the same screen, below that, information about the second concern, and below that, information about the third concern.

7 to 10 above, the information providing unit 150 determines whether a concern has a containment relationship, a transition relationship, or an associative relationship with another concern according to a preset object class. This is specified by referring to the /concern correspondence map 160C. However, the present invention is not limited to such a configuration, and the information providing unit 150 determines whether a concern has an inclusion relationship, a transition relationship, or an associative relationship with another concern, based on the concern specification history by the user. You may specify whether For example, if the user frequently checks the information on the "work situation" after confirming the information on the "site situation", the information providing unit 150 changes the concern of the "job situation" to the concern of the "work situation". It may be determined to have an associative relationship in association. At this time, when determining that a concern has an associative relationship with another concern in the same object class, the information providing unit 150 determines that these concerns have a "thing associative relationship" in the object class. . Also, for example, when the user confirms information about a plurality of other concerns after confirming information about "site conditions", the concern of "site conditions" has an associative relationship in relation to these multiple concerns. may be determined to have In that case, the information providing unit 150 may receive a user's designation by displaying a list of selection items for selecting one of the plurality of concerns in descending order of frequency confirmed in the past.

Furthermore, as another form, the information providing unit 150 may be a user with a high skill as an engineer (the level of skill may be determined based on the registration period or position of the user registered in the information providing apparatus 100, for example). based on the designation history of concerns, and for users with low engineering skills, multiple concerns are determined according to these inclusion relationships, transition relationships, or associative relationships. may be displayed. For example, when a highly skilled user frequently checks information on "work situation" after checking information on "site situation", the information providing unit 150 determines that the concern of "job situation" is "work situation". When a low-skilled user confirms the information on the "site situation", display the information on the "work situation" in a selectable slide show format or list format. may

[Flow of operation]
Next, with reference to FIG. 11, the flow of processing executed by the information providing apparatus 100 will be described. FIG. 11 is a flow chart showing an example of the flow of processing executed by the information providing apparatus 100. As shown in FIG.

First, the information acquisition unit 110 acquires time-series data regarding the power equipment installed in the power facility 10 from the power facility 10 (step S101). Next, the object class identification unit 120 determines whether the user designates the name or identification id of the power equipment for which information is desired to be viewed on the terminal device 50, or whether a predetermined event for the power equipment has occurred. is determined (step S102).

If the user designates the name or identification id of the power equipment for which information is to be viewed on the terminal device 50, or if it is determined that a predetermined event for the power equipment has not occurred, the object class identification unit 120 , the process of step S102 is executed again. On the other hand, if the user designates the name or identification id of the power equipment for which information is to be viewed on the terminal device 50, or if it is determined that a predetermined event has occurred for the power equipment, the object class identification unit 120 specifies an object class corresponding to the power equipment (step S103).

Next, the concern receiving unit 130 displays on the terminal device 50 candidate concerns for the power equipment designated by the user, and determines whether or not designation of a concern has been received from the user (step S104). If it is determined that the specification of the concern from the user has not been accepted, the concern accepting unit 130 waits until the specification of the concern is accepted from the user. On the other hand, if it is determined that the specification of the concern has been received from the user, the information provision type determining unit 140 searches the object class/concern correspondence map 160C using a combination of the specified object class and the accepted concern. determines the output format of the UI class 160D and information corresponding to the combination of the object class and concern (step S105). The information providing unit 150 provides information on power equipment according to the determined UI class 160D and information output format (step S106). This completes the processing of this flowchart.

According to at least one embodiment described above, based on the object class corresponding to the power facility specified by the user or in which a predetermined event has occurred, and the concerns that the user has about the power facility, An information provision type of information to be provided to the user is determined, and information on the power equipment is provided according to the determined information provision type. This makes it possible for the plant supervisor to reduce the effort of the operations to be performed to obtain the information of interest.

[Configuration of information design support device]
As described above, the storage unit 160 pre-stores the UI classes 160D corresponding to combinations of object classes and concerns, and the information providing apparatus 100 refers to the object class/concern correspondence map 160C to obtain the UI classes to be displayed. 160D is decided. That is, the UI class 160D is created in advance by an engineer who is familiar with the management of the electric power facility 10, considering combinations of object classes and concerns, and stored in the object class/concern correspondence map 160C. The information design support device 200 that supports creation of the UI class 160D will be described below.

FIG. 12 is a diagram showing an example of the configuration of the system 1 including the information providing device 100 and the information design support device 200 of the embodiment. As shown in FIG. 12 , system 1 includes information design support device 200 in addition to power facility 10 , terminal device 50 and information providing device 100 .

The information design support device 200 is a server device that provides the terminal device 50 with functions as a development environment for supporting the creation of the UI class 160D. a portion 230; The UI editing unit 210 and the UI presenting unit 220 are implemented, for example, by a hardware processor such as a CPU (Central Processing Unit) executing a program (software). Some or all of these components are hardware (circuit part; circuitry) or by cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as a HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium) and installed by loading the storage medium into a drive device. The storage unit 160 is, for example, an HDD, a flash memory, a RAM (Random Access Memory), or the like. The storage unit 230 stores, for example, an object class 230A, a UI component 230B, and a UI class 230C.

In the following description, the information design support device 200 and the terminal device 50 are separate entities, and the user, for example, uses a web browser (an example of a “display unit”) of the terminal device 50 to operate the information design support device. 200 provided by the development environment, the present invention is not limited to such a configuration. For example, the functions of the development environment provided by the information design support device 200 described below may be installed in the terminal device 50 as applications, or the information provision device 100 described above may serve as the information design support device 200. It may also have the functions of

The UI editing unit 210 creates a UI class 230C by combining a plurality of UI components 230B such as text boxes, graphics, object class property values, graphs, images, or moving images for combinations of object classes and concerns. provide an interface for

FIG. 13 is a diagram showing an example of an interface for creating a UI class 230C by combining multiple UI components 230B. As shown in the right part of FIG. 13 , for example, on the terminal device 50, the user selects “pump A” as the object class and “operating status” as the concern. An interface is provided to the terminal device 50 for creating the UI class 230C corresponding to the combination of the object class of "pump A" and the concern of "operating status". Note that the UI editing unit 210 may provide a function for the user to not only select an existing object class and concern, but also define a new object class or concern and edit the UI class 230C.

When the name of an object class is selected on the screen of the terminal device 50, the UI editing unit 210 refers to the object class 230A stored in the storage unit 230, acquires the properties of the object class, and creates the UI class 230C. can be used for editing. For example, as shown in FIG. 2, the object class of "pump A" includes items such as identification number, model number, product number, manufacturer, person in charge, status, introduction date, flow rate, and head as properties. Therefore, as shown in the lower right part of FIG. 13, the UI editing unit 210 can select these properties associated with the "pump A" object class and embed them in the created UI class 230C.

As shown in the left part of FIG. 13, the user inputs characters into a text box TXTBX, which is a kind of UI component 230B, on the terminal device 50, for example. In the example of FIG. 13, on the terminal device 50, the user inputs "pump operation status" in the text box TXTBX1 and "equipment information" in the text box TXTBX2. The user further draws a figure such as a square SQ1 on the terminal device 50, for example. Further, the user can display the values of properties such as identification number PR1, model number PR2, and product number PR3 as properties on the terminal device 50 by dragging and dropping them from the property list. Let

FIG. 14 is a diagram showing another example of an interface for creating a UI class 230C by combining multiple UI components 230B. FIG. 14 shows the situation in which the user has completed the definition of the equipment information of the UI class 230C in the scene of FIG.

As shown in the left part of FIG. 14 , the user inputs “performance characteristics” in the text box TXTBX3 on the terminal device 50, for example. Next, the user embeds a graph in the UI class 230C, for example, by invoking a graph function, which is a type of UI component 230B, on the terminal device 50 (eg, by right-clicking the mouse). At this time, for example, as shown in the left part of FIG. 14, the UI editing unit 210 presents a dialog box asking the user to specify explanatory variables and objective variables for the graph. A graph can be defined by selecting an explanatory variable and an objective variable.

In the example of FIG. 14, the user has selected the flow rate as the explanatory variable and the head as the objective variable. Accordingly, the UI class 230C defines a performance curve showing the relationship between flow rate and head. Through the above processing, a UI class 230C that is the same as the UI class 160D shown in FIG. 4 is created for a combination of the "pump A" object class and the "operating status" concern.

In this embodiment, a simple example of designating an explanatory variable and an objective variable is shown as a graph function, which is a kind of UI component 230B. The plug-in may be created as a plug-in and stored in the storage unit 230, and the UI editing unit 210 may call the plug-in stored in the storage unit 230 and embed it in the UI class 230C.

The UI presentation unit 220 transmits the UI class 230C created for the combination of the object class and concern to the terminal device 50 for display. At this time, the UI presentation unit 220 may display the created UI class 230C as a template as shown in FIG. By inputting sample data to UI class 230C, it may be displayed as actual data as shown in FIG. After that, the created UI class 230C is deployed to the storage unit 160 of the information providing apparatus 100 as a UI class 160D.

13 and 14 show interface screens when the user creates UI classes 230C for individual combinations of object classes and concerns. On the other hand, for the same concern, common (or partly common) UI items may be defined even if the object classes are different. In that case, it would not be efficient to manually create a UI class 230C for each combination of object class and concern.

FIG. 15 is a diagram showing another example of an interface for creating a UI class 230C by combining multiple UI components 230B. As shown in the right part of FIG. 15, the user selects "operation status" as a concern and selects "pump A", "pump B", and "valp A" as object classes on the terminal device 50, for example. . At this time, the UI editing unit 210 provides the terminal device 50 with an interface for creating the UI class 230C corresponding to the "operation status" concern, and the created UI class 230C is "pump A", "pump B" and "bulp A" object classes. For example, after editing the UI items common to the object classes of "Pump A", "Pump B", and "Valp A", the user switches to the interface shown in FIGS. You may edit the UI item of . As a result, UI classes 230C can be efficiently created for a plurality of object classes having UI items common to a certain concern.

Next, with reference to FIGS. 16 to 19, interfaces for defining containment relationships, transition relationships, and associative relationships of concerns in the UI class 230C will be described. FIG. 16 is a diagram showing an example of an interface for defining a containment relationship of concerns in the UI class 230C. As in FIG. 13, the user selects, for example, "pump A" as the object class and "situation" as the concern on the terminal device 50, so that the UI editing unit 210 displays "pump A". It provides the terminal device 50 with an interface for creating a UI class 230C corresponding to the combination of the object class and the "situation" concern.

As shown in the lower right part of FIG. 16, the UI editing unit 210 displays a plurality of concerns in list form as concerns that are candidates to be included in the "situation", that is, as included concerns. The user, for example, on the terminal device 50, by dragging and dropping "operation status", "work status", "site status", and "alarm occurrence status" from the list of included concerns, a UI class 230C corresponding to the combination of the "pump A" object class and the "operation status" concern, and a UI class 230C corresponding to the combination of the "pump A" object class and the "work status" concern; A UI class 230C corresponding to the combination of the "pump A" object class and the "site situation" concern, and a UI class 230C corresponding to the combination of the "pump A" object class and the "alarm occurrence situation" concern. , UI class 230C corresponding to the combination of the object class of "Pump A" and the concern of "Situation". When an inclusion relationship is defined for a certain UI class 230C, the inclusion relationship is reflected in the object class/concern correspondence map 160C stored in the information providing apparatus 100. FIG.

FIG. 17 is a diagram showing an example of an interface for defining concern transition relationships in the UI class 230C. In the case of FIG. 17, for example, the user selects "Pump A" as the object class on the terminal device 50, and selects "Planning of patrol inspection" as the concern. ' object class and the 'patrol inspection plan' concern.

As shown in the lower right part of FIG. 17, the UI editing unit 210 displays a plurality of concerns in a list format as concerns that are candidates to which a certain concern transitions next, that is, as transition destination concerns. For example, on the terminal device 50, the user drags and drops "Diagnostic Analysis of Deterioration" from the list of transition destination concerns to the "Implementing Patrol Inspection" concern, thereby creating an object class of "Pump A". and the "Diagnostic Analysis of Deterioration" concern combination is displayed after the UI class 230C corresponding to the combination of the "Pump A" object class and the "Perform a Patrol Inspection" concern. can be done. The user further drags and drops "notification of alarm" from the list of transition destination concerns to the concern of "diagnostic analysis of deterioration" to create an object class of "pump A" and "diagnostic analysis of deterioration". may be displayed after the UI class 230C corresponding to the combination of the "Pump A" object class with the "Perform a Patrol" concern. As a result, for the combination of the object class of "pump A" and the concern of "planning of patrol inspection", the transition is made in the order of "execution of patrol inspection", "diagnostic analysis of deterioration", and "notification of alarm". A UI class 230C is defined. When a transition relationship is defined for a certain UI class 230C, the transition relationship is reflected in the object class/concern correspondence map 160C stored in the information providing apparatus 100. FIG. Also in this case, the description "later" does not necessarily mean that the display timing of the information is shifted. The information and the information corresponding to the pre-transition concern may be displayed at the same time.

FIG. 18 is a diagram showing an example of an interface for defining an associative relationship of concerns in the UI class 230C. In the case of FIG. 18, for example, the user selects "pump A" as the object class and "operating status" as the concern on the terminal device 50, whereby the UI editing unit 210 displays the "pump A" It provides the terminal device 50 with an interface for creating the UI class 230C corresponding to the combination of the object class and the "operational status" concern.

As shown in the lower right part of FIG. 18, the UI editing unit 210 displays a plurality of concerns in a list format as concerns as candidates related to "operation status", that is, as related concerns. For example, on the terminal device 50, the user drags and drops "inventory status" from the associative concern list to create a UI class corresponding to the combination of the "pump A" object class and the "work status" concern. On 230C, the UI class 230C corresponding to the combination of the "pump A" object class and the "inventory status" concern is selectably displayed as a slide. The UI presentation unit 220 slide-displays the information on the "inventory status" as a selection item, and displays the information on the "inventory status" in more detail (for example, magnify) to display. When an association relationship is defined for a certain UI class 230C, the association relationship is reflected in the object class/concern correspondence map 160C stored in the information providing apparatus 100. FIG.

FIG. 19 is a diagram showing an example of an interface for defining an associative relationship of concerns in the UI class 230C. In the case of FIG. 19, for example, on the terminal device 50, the user selects "pump A" as the object class and selects "operation status" as the concern. It provides the terminal device 50 with an interface for creating the UI class 230C corresponding to the combination of the object class and the "operational status" concern.

As shown in the lower right part of FIG. 19, the UI editing unit 210 displays a plurality of concerns in a list format as concerns as candidates related to "operation status", that is, as related concerns. For example, on the terminal device 50, the user drags and drops "inventory status" from the associative concern list to create a UI class corresponding to the combination of the "pump A" object class and the "work status" concern. On 230C, a UI class 230C corresponding to the combination of the "pump A" object class and the "inventory status" concern is displayed in a selectable manner. The UI presenting unit 220 displays a list of information related to "inventory status" as selection items, and displays the information related to "inventory status" when the user clicks on the selection items displayed in the list. By the above processing, the containment relationship, transition relationship, and associative relationship of concerns are defined in the UI class 230C.

Note that FIGS. 18 and 19 describe the case where the user manually sets the associative relationship of concerns. However, as described above, the associative relation of concerns can also be obtained by learning each user's associative tendency based on, for example, histories of concerns specified by users. Therefore, the information providing unit 150 may, for example, display only one of the associative concern obtained by learning and the manually set associative concern, or may display them simultaneously so as to be distinguishable. . In addition, for example, the information providing unit 150 displays manually set associative concerns by default, and as each user's learning of associative tendencies progresses, the concerns that are frequently specified by the user replace the default displayed concerns. You can display it like this:

According to at least one embodiment described above, according to the combination of the object class, which is information that categorizes the type of power equipment, and the concern, which is the concern that the user has about the power equipment, It provides an interface for creating a UI to be provided, and provides information about power equipment based on the created UI. This makes it possible for the plant supervisor to reduce the effort of the operations to be performed to obtain the information of interest.

In addition, in the present embodiment, the case where the present invention is applied to a plant installed with electric power equipment or the like has been described as an example. However, the present invention is not limited to such a configuration, and can be applied to monitoring facilities of various social infrastructures such as water, gas, medical, road, railway, and airport. For example, when the present invention is applied to water supply facilities, it is possible to set a receiving tank, a water pipe, etc. as object classes, and set operation statuses and inspection statuses as concerns. Further, for example, when the present invention is applied to gas supply equipment, it is possible to set bulk storage tanks, overfill prevention devices, etc. as object classes, and set operation statuses and inspection statuses as concerns.

While several embodiments of the invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and modifications can be made without departing from the scope of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, as well as the scope of the invention described in the claims and equivalents thereof.

DESCRIPTION OF SYMBOLS 10... Power facility, 50... Terminal device, 100... Information providing apparatus, 110... Information acquisition part, 120... Object class identification part, 130... Concern reception part, 140... Information provision type determination part, 150... Information provision part, 160 Storage unit 160A Time-series data 160B Object class 160C Object class/concern correspondence map 160D UI class 200 Information design support device 210 UI editing unit 220 UI presentation unit 230 Storage unit 230A... Object class 230B... UI component 230C... UI class

Claims (8)

An object class, which is information categorized by defining a plurality of data items for information about power equipment, and one or more concerns, which is information representing a user's interest in the power equipment. An information design support device that supports designing as combined information,
a UI editing unit that provides an interface for creating a UI (user interface) by combining a plurality of components for a combination of the object class and the concern;
a UI providing unit that causes a display unit to display the UI created for the combination of the object class and the concern;
Information design support device. the one or more concerns include a plurality of concerns;
The UI editing unit provides the interface for defining a relationship in which a first concern of the plurality of concerns includes a second concern of the plurality of concerns;
The UI providing unit displays the UI corresponding to the combination of the object class and the first concern and the UI corresponding to the combination of the object class and the second concern on a display unit.
The information design support device according to claim 1. the one or more concerns include a plurality of concerns;
The UI editing unit provides the interface for defining a relationship in which a first concern among the plurality of concerns transitions to a second concern among the plurality of concerns,
After causing the display unit to display the UI corresponding to the combination of the object class and the first concern, the UI providing unit displays the UI corresponding to the combination of the object class and the second concern to the display unit. to display
3. The information design support device according to claim 1 or 2. the one or more concerns include a plurality of concerns;
The UI editor provides the interface for defining a relationship in which a first concern of the plurality of concerns relates to a second concern of the plurality of concerns;
The UI providing unit causes the display unit to display the UI corresponding to the combination of the object class and the first concern in a manner associated with the UI corresponding to the combination of the object class and the second concern.
The information design support device according to any one of claims 1 to 3. The UI editing unit provides the interface for defining in list form a relationship in which a first concern of the plurality of concerns relates to a second concern of the plurality of concerns;
The UI providing unit causes the display unit to display the UI corresponding to the combination of the object class and the first concern and the UI corresponding to the combination of the object class and the second concern in the list format. ,
5. The information design support device according to claim 4. The UI editing unit provides the interface for defining in a slide format a relationship in which a first concern of the plurality of concerns relates to a second concern of the plurality of concerns;
The UI providing unit causes the display unit to display the UI corresponding to the combination of the object class and the first concern and the UI corresponding to the combination of the object class and the second concern in the slide format. ,
5. The information design support device according to claim 4. the computer
An object class, which is information categorized by defining a plurality of data items for information about power equipment, and one or more concerns, which is information representing a user's interest in the power equipment. Supporting design as combined information,
providing an interface for creating a UI (user interface) by combining a plurality of components for the combination of the object class and the concern;
causing a display to display the UI created for the combination of the object class and the concern;
Information design support method. to the computer,
An object class, which is information categorized by defining a plurality of data items for information about power equipment, and one or more concerns, which is information representing a user's interest in the power equipment. Let us help you design as combined information,
providing an interface for creating a UI (user interface) by combining a plurality of components for the combination of the object class and the concern;
causing a display to display the UI created for the combination of the object class and the concern;
program.

Images