Event management device, storage medium and event management method
By introducing the mechanism of event acquisition, registration tag extraction and searching tag prompts in the event management system, the problem of difficulty for users to retrieve appropriate event keywords is solved, efficient retrieval and prompt of event information is achieved, and the efficiency and knowledge of the system are enhanced Inheritance ability.
Patent Information
- Application Number
- CN201980090058.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-01-25
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2039-01-25
AI Technical Summary
In the event management system, it is difficult for users who inherit experience to effectively retrieve appropriate event keywords, resulting in the inability to effectively utilize stored event information.
An event management device is designed, including an event acquisition unit, a registration tag extraction unit, a registration tag management unit, a condition acquisition unit, a search tag extraction unit, a registration tag prompt unit and an event prompt unit, through text input, meta-information extraction, and tags Management and conditional input to achieve efficient retrieval and prompts of events.
It improves the user's retrieval efficiency in the event management system, can find event information with high similarity to the user's input conditions more effectively, and enhances the inheritance and application capabilities of knowledge.
Smart Images

Figure CN113330431B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to techniques for managing episodes. Background Art
[0002] Conventionally, in organizations such as companies, there is known an event management system that uses a database that stores, as event information, situations when problems occur in business operations and countermeasures to the problems to achieve knowledge sharing within the organization.
[0003] In addition, in the event management system, event information stored in the database can be searched by keywords, thereby allowing users to access event information presented as search results. According to such a search, at least a portion of the sentence contained in the event information, or event information consistent with the keyword attached to the event information, is presented as a search result for the keyword input by the user.
[0004] There are situations where an event management system is used to enable a successor to inherit knowledge (Japanese: ナレッジ), specifically, to inherit the insights, experience (know-how), etc. of an experienced person. In such a situation, generally speaking, the user as an experienced person registers the event in the database, and the user as the successor uses the event prompted as a search result to solve the problem.
[0005] In addition, as a related technology, there is known a case management device that manages cases in product manufacturing, and the case management device comprises: a storage unit; a keyword management unit that accepts parameters of a product related to the case input by a user as keyword items and registers them in the storage unit; a first display unit that reads the keyword items from the storage unit and displays them; and a product information management unit that accepts keywords corresponding to the keyword items input by the user and information required for product manufacturing as product information and registers them in the storage unit (Patent Document 1).
[0006] Prior art literature
[0007] Patent Literature
[0008] Patent Document 1: Japanese Patent Application Publication No. 2008-52592 Summary of the invention
[0009] Problems to be solved by the invention
[0010] However, when using events stored in the database, the successor who is to inherit the experience has difficulty in thinking of keywords suitable for searching for desired events, and therefore cannot use the event management system as effectively as experienced professionals.
[0011] The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a technology capable of utilizing stored events more effectively.
[0012] Means used to solve problems
[0013] In order to solve the above-mentioned problems, an embodiment of the present invention is an event management device capable of managing events in a shared manner, wherein the event management device comprises: an event acquisition unit, which acquires events for which text has been input by a registered user who registers an event; an event management unit, which manages the acquired events; a registration tag extraction unit, which extracts registration tags as meta-information of the event based on the acquired events; a registration tag management unit, which manages the extracted registration tags as tag information corresponding to the managed events; a condition acquisition unit, which acquires conditions input by a search user who searches for events as condition information; a search tag extraction unit, which extracts search tags from the condition information; a registration tag prompting unit, which prompts the search user in a selectable manner a registration tag in the tag information managed by the registration tag management unit that has a high similarity with the search tag; and an event prompting unit, which prompts the search user in an event managed by the event management unit that has a high similarity with the registration tag selected by the search user. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 This is a schematic diagram showing the overall structure of the event management system according to the embodiment.
[0015] Figure 2 This is a schematic diagram showing a facility in which an event management system according to an embodiment is applied.
[0016] Figure 3 This is a block diagram showing the hardware configuration of the event management device.
[0017] Figure 4 This is a block diagram showing the functional structure of the event management device.
[0018] Figure 5 This is a flowchart showing the overall operation of the event management device.
[0019] Figure 6 This is a flowchart showing the operation of event registration processing.
[0020] Figure 7 This is a diagram showing an event registration screen.
[0021] Figure 8 This is a diagram showing the extraction of registered tags and related tags.
[0022] Fig. 9 This is a flowchart showing the operation of event search processing.
[0023] Fig.10 This figure shows the event search screen.
[0024] Fig.11 This is a flowchart showing the operation of the registration tag presentation process.
[0025] Fig.12 This is a flowchart showing the operation of the related tag prompting process.
[0026] Fig.13 is a graph showing the suggested related tags.
[0027] Fig.14 This is a flowchart showing the operation of event presentation processing.
[0028] Fig.15 This is a diagram showing an event notification screen.
[0029] Fig.16 This is a flowchart showing the operation of the network display process.
[0030] Fig.17 This figure shows a network display screen. DETAILED DESCRIPTION
[0031] Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0032] (Overall composition)
[0033] The overall configuration of the event management system according to this embodiment will be described. Figure 1 is a schematic diagram showing the overall structure of the event management system of this embodiment. Figure 2 This is a schematic diagram showing the facilities where the event management system is operated.
[0034] like Figure 1 As shown, the event management system 1 of this embodiment includes an event management device 10, at least one or more client devices 20, a user log management device 30, and a device log management device 40. The event management device 10 is a device that stores and manages events, and is connected to the one or more client devices 20, the user log management device 30, and the device log management device 40 via a network. In this embodiment, the event management system 1 is used to share events between multiple users belonging to a specified organization, and the events are knowledge and experience related to the achievement of the goals of the organization.
[0035] In this embodiment, it is assumed that the event management system 1 is used in a company having a plurality of facilities as production organizations, and each facility is assumed to be a factory F. Figure 2As shown, the factory F has a plurality of production lines L therein. Each production line L has a plurality of work steps P, and each work step P is provided with equipment E for processing a workpiece W. In addition, a user U who uses the event management system 1 is provided as an operator who performs production work in each work step P.
[0036] The client device 20 is a terminal device operated by the user U when using the event management system 1. The user U registers events to be shared in the enterprise in the event management device 10 via the client device 20, and obtains events registered in the event management device 10 from the client device 20.
[0037] It is assumed that each user U who performs work in the factory F carries a HID (Human Interface Device) with him / her. The HID is provided as a measuring device for measuring the actions of the user U involved in the work using the device E, the position of the user U in the factory F, and a microphone for recording the voice uttered by the user U, for example, provided as a wristband-type device that can be worn on the wrist of the user U. The measurement data and voice data as the user log of each user U measured by such an HID are sent to the user log management device 30 via the network. The user log management device 30 establishes a correspondence between the device ID that uniquely represents the HID and the received user log, adds a time stamp and manages it in time series, and sends the user log to the event management device 10 according to a request from the event management device 10.
[0038] Equipment sensors are provided for the equipment E installed in the factory F. The equipment sensors are sensors that measure changes caused by the operation of the equipment E, such as temperature and vibration. In addition, when an error occurs, each equipment E outputs an error code, which is an identifier indicating the type of error. The sensor value and error code of each equipment E measured by such equipment sensors are sent to the equipment log management device 40 via the network as equipment logs. The equipment log management device 40 establishes a correspondence between the received equipment logs and each equipment E, adds a time stamp and manages them in time series, and sends the equipment logs to the event management device 10 according to a request from the event management device 10.
[0039] (Hardware Configuration)
[0040] The hardware configuration of each device in the event management system is described. Figure 3 This is a block diagram showing the hardware configuration of the event management device.
[0041] like Figure 3As shown, the event management device 10 includes, as hardware, a CPU (Central Processing Unit) 11, a RAM (Random Access Memory) 12, a storage device 13, an input / output I / F (Interface) 14, and a network I / F 15. The CPU 11 and the RAM 12 cooperate to perform various functions, and the storage device 13 stores various data used by the processing (event management program) performed by the various functions. The input / output I / F 14 performs input and output of data between input devices such as a keyboard and output devices such as a display connected to the event management device 10. The network I / F 15 performs wired or wireless communication with other devices such as the client device 20, the user log management device 30, and the device log management device 40. In the present embodiment, the client device 20, the user log management device 30, and the device log management device 40 have substantially the same hardware configuration as the event management device 10, and therefore the description thereof is omitted.
[0042] (Functional structure of event management device)
[0043] The functional structure of the event management device is described. Figure 4 This is a block diagram showing the functional structure of the event management device.
[0044] like Figure 4 As shown, the event management device 10 includes, as functions, a user management unit 101, an authentication processing unit 102, an event acquisition unit 103, a user log acquisition unit 104, a facility management unit 105, a device log acquisition unit 106, an event management unit 107, a registration tag extraction unit 108, a registration tag management unit 109, a condition acquisition unit 110, a retrieval tag extraction unit 111, a registration tag prompt unit 112, a related tag prompt unit 113, and an event prompt unit 114.
[0045] The user management unit 101 manages the user ID, which is an identifier that uniquely represents the user, the password, which is authentication information, and the device ID of the HID carried by the user as user information. In addition, in the user information, the facility ID, production line ID, and operation process ID described later are associated with the user ID as the department to which the user belongs.
[0046] The authentication processing unit 102 authenticates the user based on the user ID and the corresponding password. The event acquisition unit 103 acquires the event input by the user text after being authenticated by the authentication processing unit 102. The user log acquisition unit 104 acquires the user log associated with the device ID corresponding to the user ID from the user log management device 30.
[0047] The facility management unit 105 associates facility IDs that uniquely represent multiple facilities owned by the enterprise using the event management system 1, production line IDs that uniquely represent production lines belonging to each facility, operation process IDs that uniquely represent operation processes belonging to each production line, and equipment IDs that uniquely represent equipment installed in each operation process in a manner that indicates their ownership, and manages them as facility information. In addition, the facility ID, production line ID, operation process ID, and equipment ID are pre-registered by the administrator of the event management system 1 before the event management system 1 is used.
[0048] The equipment log acquisition unit 106 acquires equipment logs associated with equipment IDs from the equipment log management device 40. As described in detail later, the equipment ID used to acquire the equipment logs is the equipment ID associated with the work process ID acquired when acquiring an event in the facility information.
[0049] The event management unit 107 manages the content information including the user ID authenticated by the authentication processing unit 102, the event acquired by the event acquisition unit 103, the user log acquired by the user log acquisition unit 104, and the device log acquired by the device log acquisition unit 106 by establishing a correspondence with the content ID which is an identifier uniquely representing the content information.
[0050] The registration tag extraction unit 108 extracts meta information about the content information from the event included in the content information as a registration tag. Here, the registration tag extraction unit 108 extracts the registration tag by text mining of the event and obtaining the error code included in the device log. Regarding the event, as described in detail later, a related tag represented as a group of two extracted tags is further extracted.
[0051] The registered tag management unit 109 manages tag information including the registered tags and related tags extracted by the registered tag extraction unit 108 in association with content IDs indicating content information from which the tag information is extracted.
[0052] The condition acquisition unit 110 acquires conditions input by the user in order to obtain desired content information managed by the event management unit 107. As described in detail later, the user inputs or selects a facility ID, a work process ID, a line ID, a text, a label, etc. as conditions.
[0053] The search tag extraction unit 111 extracts a search tag based on the condition acquired by the condition acquisition unit 110. The search tag is an error code included in the equipment log associated with the facility ID, operation process ID, and production line ID acquired as the condition in the equipment log management device 40, or a word extracted by text mining of the text input as the condition.
[0054] The registered tag presenting unit 112 calculates scores for the tag information managed by the registered tag managing unit 109 based on the search tags extracted by the search tag extracting unit 111 , arranges the registered tags in descending order according to the scores, and presents them to the user in a selectable manner.
[0055] The related tag presenting unit 113 calculates scores for tag information managed by the registered tag management unit 109 based on the registered tag selected by the user among the registered tags presented by the registered tag presenting unit 112 , and presents the user with related tags included in tag information having a score greater than or equal to a predetermined score.
[0056] The event presentation unit 114 calculates scores for the tag information managed by the registered tag management unit 109 based on all the registered tags selected by the user, and presents the content information managed by the event management unit 107 to the user in descending order of the scores calculated for the corresponding tag information.
[0057] (Overall Operation of Event Management Device)
[0058] The overall operation of the event management device is described. Figure 5 is a flowchart showing the overall operation of the event management device. Figure 5 In the process, authentication of specified users is performed in advance.
[0059] like Figure 5 As shown, the event management device 10 first determines whether a process request is made from the user via the client device 20 (S101).
[0060] When a processing request is made (S101, Yes), the event management device 10 determines whether the processing request from the user is a registration request (S102).
[0061] When the processing request is not a registration request (S102, No), the event management device 10 determines whether the processing request from the user is a search request (S103).
[0062] When the processing request is a search request (S103, Yes), the event management device 10 executes an event search process described later (S104), and determines again whether a processing request has been made from the user (S101).
[0063] On the other hand, when the processing request is not a retrieval request (S103, No), the event management device 10 determines again whether a processing request has been made by the user (S101).
[0064] In addition, in step S102, when the processing request is a registration request (S102, Yes), the event management device 10 executes the event registration process described below (S105) and determines again whether a processing request has been made by the user (S101).
[0065] In addition, in step S101, when no processing request has been made (S101, No), the event management device 10 determines again whether a processing request has been made by the user (S101).
[0066] (Event registration process)
[0067] The event registration process will be described. Figure 6 is a flowchart showing the operation of the event registration process. Figure 7 is a diagram showing the event registration screen. Figure 8 is a diagram showing the extraction of registration labels and related labels.
[0068] As Figure 6 shown, first, the event acquisition unit 103 acquires event information input from the user via the client device 20 (S201). This event information is obtained by the user selecting or entering text in each item on the event registration screen as Figure 7 shown. In this event information, it includes the user ID of the input user, "facility", "operation process", "production line", "time range", "subject", "phenomenon (in Japanese: 事象)", and "response" as input items.
[0069] For each of the items "facility", "operation process", and "production line", as information indicating the location where the registered event occurred, the facility ID, operation process ID, and production line ID managed by the facility management unit 105 are presented in a manner that can be selected by the user. The options in each of the items "facility", "operation process", and "production line" are presented as the names of the objects represented by the identifiers, such as "First Factory", "Upper Surface Grinding", and "Production Line 1". In addition, for each of the items "facility", "operation process", and "production line", as default settings, the facility ID, production line ID, and operation process ID corresponding to the user ID in the user information are pre-selected.
[0070] The "time range" item has two text input fields as information for indicating the time range in which the registered event occurs. The date and time of the event occurrence is input in one text input field, and the date and time of the event end is input in the other text input field.
[0071] Each of the items "Subject", "Phenomenon", and "Response" has a text input field. In "Subject", enter the name of the event so that other users can easily understand the outline of the event. In "Phenomenon" and "Response", enter text that expresses the event. It is assumed that in "Phenomenon", enter text that indicates the occurrence of the event to be responded to, and in "Response", enter text that indicates the appropriate response to the occurrence of the event entered in "Phenomenon".
[0072] After the event acquisition unit 103 acquires the event information, the user log acquisition unit 104 acquires the user log information from the user log management device 30 based on the user ID and time range included in the event information (S202). Here, the user log acquisition unit 104 refers to the user information managed by the user management unit 101, acquires the device ID associated with the user ID, and acquires the user log in the time range included in the event information from the user log associated with the device ID in the user log management device 30 as the user log information.
[0073] In addition, the device log acquisition unit 106 acquires the device log information from the device log management device 40 based on the facility ID, production line ID, operation process ID and time included in the event information (S203). Here, the device log acquisition unit 106 acquires the device ID corresponding to the combination of the facility ID, production line ID and operation process ID included in the event information from the facility information managed by the facility management unit 105, and acquires the device log belonging to the time range included in the event information from the device log corresponding to the device ID in the device log management device 40 as the device log information.
[0074] Next, the event management unit 107 establishes a correspondence between the event information obtained by the event acquisition unit 103, the user log information obtained by the user log acquisition unit 104, and the device log information obtained by the device log acquisition unit 106, and manages them as content information by attaching a content ID that uniquely represents the content information (S204).
[0075] Next, the registration tag extraction unit 108 extracts registration tags based on the content information (S205). Specifically, the registration tag extraction unit 108 extracts registration tags for the event information and the device log information in the content information. The names of the objects represented by the facility ID, the production line ID, and the operation process ID are extracted from the event information as registration tags, a part of the text input as "phenomenon" and "response" is extracted as a registration tag, and a related tag indicating the correlation between the two registration tags is extracted. In addition, when an error code is included in the device log information, the error code is extracted as a registration tag.
[0076] The registered tags are extracted as a set of key and value, with the value extracted as the registered tag being substituted into the value and the category to which the value belongs being substituted into the key. For cases other than the registered tags extracted from the text, the categories used as keys include "facility", "production line", "operation process", "error code", etc. For example, "facility = first factory", "operation process = upper surface grinding", "production line = production line 1", "error code = ERR001", etc. are expressed in the form of "key = value".
[0077] Here, we will explain how to extract registration tags from text. Figure 8 As shown, sentences input as "phenomenon" and "response" are extracted through text mining processing, and "phenomenon", "treatment", and "object" are used as keys. Before the text mining processing, machine learning is performed to extract phrases representing passively occurring events as values of "phenomenon", extract phrases representing actively occurring events as values of "treatment", and further extract the subject or object of the occurring event described as "phenomenon" or "treatment" as values of "object". The text mining processing performed by the registration label extraction unit 108 extracts registration labels based on the prediction model obtained by such machine learning. In addition, the registration label extraction unit 108 extracts a group of registration labels extracted as "object" and registration labels extracted as "phenomenon" or "treatment" with the registration label as the subject or object as related labels.
[0078] After extracting the registration tag and the related tag, the registration tag management unit 109 adds the content ID added to the content information as the extraction source to the tag information including the registration tag and the related tag, and manages them (S206), and ends the event registration process.
[0079] (Event retrieval processing)
[0080] The event search process is described. Fig. 9 This is a flowchart showing the operation of event search processing. Fig.10 This figure shows the event search screen.
[0081] like Fig. 9 As shown, first, the condition acquisition unit 110 acquires search information input from the user via the client device 20 (S301). The search information is obtained by the user Fig.10 The search information is obtained by selecting or inputting text for each item on the event search screen shown in the figure. The search information includes the user ID of the input user, and "facility", "operation process", "production line" and "free word" as input items.
[0082] Similar to the items on the above-mentioned event registration screen, the items "facility", "operation process", and "production line" are information indicating the place where the event for which the prompt is requested has occurred, that is, the place where the event requested as a search result has occurred, and the facility ID, operation process ID, and production line ID managed by the facility management unit 105 are prompted in a manner that can be selected by the user. In addition, the facility ID, production line ID, and operation process ID associated with the user ID are pre-selected in the user information as default settings for the items "facility", "operation process", and "production line", which is also the same as the event registration process.
[0083] The "free word" item has a text input field in which the user enters text representing the event to be responded to, similar to the "phenomenon" item on the event registration screen, in order to investigate how other users responded to the same event in the past.
[0084] After obtaining the search information, the condition acquisition unit 110 determines whether the corresponding error code is included in the device log information managed by the device log management device 40 based on the facility ID, production line ID, operation process ID and current time contained in the search information (S302). Here, the condition acquisition unit 110 obtains the device ID corresponding to the combination of the facility ID, production line ID and operation process ID contained in the search information from the facility information managed by the facility management unit 105, and determines in the device log management device 40 whether there is an error code corresponding to the time range from the time traced back to the preset time to the current time among the error codes of the device log corresponding to the device ID.
[0085] When the corresponding error code is included (S302, Yes), the condition acquisition unit 110 acquires the error code and includes the error code in the search information (S303).
[0086] Next, the search tag extraction unit 111 extracts search tags based on the search information (S304). Specifically, the search tag extraction unit 111 extracts the names of the objects represented by the facility ID, production line ID, and operation process ID, respectively, from the search information as search tags, and extracts a part of the text input as a "free word" as a search tag. In addition, in the case where the search information contains an error code obtained by the condition acquisition unit 110, the error code is extracted as a search tag. In addition, the search tag is extracted as a group of key and value, similar to the registration tag. The search tag is extracted from the text input as a "free word", and similar to the registration tag, it is extracted through text mining processing based on a prediction model, and the keys are "phenomenon" and "object".
[0087] After extracting the search tag, the registration tag prompting unit 112 Fig.10 As shown in FIG. 1 , a registration tag presentation process (S305) is executed to present a registration tag to the user on the event search screen. The registration tag presentation process will be described in detail later.
[0088] Next, the related tag presenting unit 113 determines whether the user has selected at least one of the registered tags presented to the user in the registered tag presenting process ( S306 ).
[0089] When the user selects a registered tag (S306, Yes), the related tag prompting unit 113 determines whether the user has made a related tag prompting request (S307). Fig.10 Click the "Related Tags" button on the event search screen shown.
[0090] When no relevant tag presentation request is made (S307, No), the event presentation unit 114 determines whether the event presentation request is made by the user (S308). Fig.10 Click the "Search" button on the event search screen shown.
[0091] When an event presentation request is made (S308, Yes), the event presentation unit 114 executes an event presentation process for presenting an event to the user based on the selected registration tag (S309), and ends the event search process. This event presentation process will be described in detail later.
[0092] On the other hand, when the event presentation request has not been made ( S308 , No), the related tag presentation unit 113 determines again whether the related tag presentation request has been made by the user ( S307 ).
[0093] In addition, in step S307, when a related tag prompt request is made (S307, Yes), the related tag prompt unit 113 performs a related tag prompt process for prompting the user of the related tag based on the selected registered tag (S310), and the event prompt unit 114 determines whether an event prompt request is made by the user (S308). In addition, the related tag prompt process will be described in detail later.
[0094] In step S306 , if the user has not selected a registration tag ( S306 , Yes), the related tag presenting unit 113 determines again whether the user has selected at least one of the registration tags presented to the user in the registration tag presenting process ( S306 ).
[0095] Furthermore, in step S302 , when the corresponding error code is included ( S302 , No), the search tag extraction unit 111 extracts the search tag based on the search information ( S304 ).
[0096] (Registration tag prompt processing)
[0097] The registration tag prompt process is described. Fig.11 This is a flowchart showing the operation of the registration tag presentation process.
[0098] like Fig.11 As shown, first, the registered tag presenting unit 112 determines whether there is a registered tag matching any of the search tags extracted by the search tag extracting unit 111 among the registered tags included in all the tag information managed by the registered tag managing unit 109 ( S401 ).
[0099] When there is a registered tag that matches the search tag (S401, Yes), the registered tag presenting unit 112 calculates a score (S402) for each tag information of all tag information managed by the registered tag management unit 109. The score calculated here is expressed as a numerical value indicating the degree of match with the search tag, and is calculated in such a way that the more registered tags that match the search tag, the higher the numerical value.
[0100] After calculating the score, the registered label prompting unit 112 selects label information whose calculated score is greater than a predetermined value (S403). In addition, here, the registered label prompting unit 112 only needs to select label information whose calculated score is relatively high. For example, when the scores are sorted in descending order, a predetermined number of label information may be selected from the upper position.
[0101] Next, the registration tag prompting unit 112 removes duplicate registration tags from all the selected tag information and counts the number of duplicates (S404). Fig.10As shown, the items are sorted in descending order according to the number of repetitions, and are presented to the user in a selectable manner (S405). Fig.10 In the example, the registration tags are prompted by category, that is, by the value set as the key.
[0102] In step S401 , if there is no registered tag matching the search tag ( S401 , No), the registered tag presentation unit 112 presents an error message to the user indicating that there is no registered tag matching the search tag ( S406 ), and ends the registered tag presentation process.
[0103] In this way, by presenting the registered tags that match the search tags extracted from the conditions input by the user, it is possible to select a registered tag that is suitable for the search event.
[0104] (Related tag prompts processing)
[0105] Explain the related tag prompt processing. Fig.12 This is a flowchart showing the operation of the related tag prompting process. Fig.13 is a graph showing the suggested related tags.
[0106] like Fig.12 As shown, first, the related tag prompting unit 113 calculates a score (S501) for each of all tag information managed by the registered tag management unit 109. The score calculated here is expressed by a numerical value to indicate the degree of consistency with the selected registered tag, and is calculated in such a way that the more registered tags that are consistent with the selected registered tag, the higher the numerical value.
[0107] After calculating the score, the related label prompting unit 113 selects label information whose calculated score is greater than a specified value (S502). In addition, here, the related label prompting unit 113 only needs to select label information with a relatively high calculated score. For example, when sorting from high to low scores, a specified number of label information can also be selected from the upper position.
[0108] Next, the related tag prompting unit 113 removes duplicate related tags from all the related tags included in all the selected tag information, and counts the number of duplicates (S503). Fig.13 As shown, the related tags with a count of more than a specified value are presented to the user in a selectable manner (S504). Fig.13 In the example, two related labels are presented in a selectable manner by means of check boxes that can toggle the values to true or false.
[0109] Next, the related tag prompting unit 113 determines whether the user has selected the suggested related tag (S505). In this embodiment, the related tag prompting unit 113 sets one of the check boxes attached to the related tags suggested to the user to true, and determines that the related tag is selected when the "Select Registration Tag" button is pressed.
[0110] When the user selects the presented related tag ( S505 , Yes), the related tag presentation unit 113 selects a registered tag included in the selected related tag ( S506 ), and ends the related tag presentation process.
[0111] On the other hand, when the user does not select the presented related tag ( S505 , No), the related tag presenting unit 113 ends the related tag presenting process.
[0112] In this way, by presenting relatively repeated related tags included in the related tags contained in the tag information including many registered tags that match the registered tag selected by the user in a selectable manner to the user, the user can select a combination of registered tags suitable for the search event.
[0113] (Event prompt processing)
[0114] The event notification process is described. Fig.14 This is a flowchart showing the operation of event presentation processing. Fig.15 This is a diagram showing an event notification screen.
[0115] like Fig.14 As shown, first, the event presentation unit 114 calculates a score (S601) for each tag information of all tag information managed by the registration tag management unit 109. The score calculated here is expressed by a numerical value to indicate the degree of consistency with the selected registration tag, and is calculated in such a way that the more registration tags that are consistent with the selected registration tag, the higher the numerical value.
[0116] After calculating the score, the event prompt unit 114 selects tag information whose calculated score is greater than a predetermined value (S602). In addition, here, the event prompt unit 114 only needs to select tag information whose calculated score is relatively high. For example, when the scores are sorted in descending order, a predetermined number of tag information can also be selected from the upper position.
[0117] Next, the event presentation unit 114 selects content information corresponding to the selected tag information, that is, content information to which the same content ID as the selected tag information is added, from the content information managed by the event management unit 107 ( S603 ).
[0118] After selecting the content information, the event prompting unit 114 sorts the selected content information and tag information in descending order according to the calculated scores and prompts the user (S604). Here, the event prompting unit 114 lists the event information contained in the selected content information. Specifically, Fig.15 In the event prompt screen shown, "Subject", "Phenomenon", and "Disposal" in the event information are displayed for each event. In addition, a "Details" button is displayed corresponding to each of the events displayed in the list. By pressing the "Details" button, the user log information, device log information, and registered tag information corresponding to the event are displayed to the user. In addition, the "Network Display" button for the user to request network display is displayed in the event prompt screen.
[0119] Next, the event presentation unit 114 determines whether a network display is requested ( S605 ).
[0120] When network display is requested (S605, Yes), the registered tag presentation unit 112 executes a network display process for displaying the correlation between the registered tags included in the selected tag information (S606), and ends the event presentation process. The network display process will be described in detail later.
[0121] On the other hand, when the network display is not requested ( S605 , No), the event presentation unit 114 ends the event presentation process.
[0122] (Network display processing)
[0123] The network display process is described. Fig.16 This is a flowchart showing the operation of the network display process. Fig.17 is a diagram showing a network display screen. In addition, the network display process connects and displays the registered tags in the order of the specified categories (key values). Fig.16 In the example, the order of the categories is set in advance. In addition, the tag information used in the network display process is the tag information selected in step S602 in the above-mentioned event presentation process.
[0124] First, if Fig.16 As shown, the registered tag prompting unit 112 selects unselected tag information (S701), and selects unselected categories in the categories for which the category order is set in sequence according to the category order (S702). Next, the registered tag prompting unit 112 selects a registered tag whose key value is the category being selected as a connection source (S703), selects a registered tag whose category is the next one in the category order to the category being selected as a connection target (S704), and connects the two registered tags.
[0125] After the registration tags are connected, the registration tag presenting unit 112 determines whether there are two or more unselected categories among the categories for which the order is set ( S705 ).
[0126] When there are less than two unselected categories ( S705 , No), the registered tag presentation unit 112 determines whether or not there is unselected tag information ( S706 ).
[0127] If there is no unselected tag information (S706, No), the registered tag presenting unit 112 selects a category for merging the registered tags (S707). Here, the registered tag presenting unit 112 selects a category that is not selected in the selection for merging from the categories for which the category order is set.
[0128] After the category is selected, the registered tag presenting unit 112 determines whether there is a duplicate registered tag in the selected category, that is, whether there is a registered tag having the same value as another registered tag ( S708 ).
[0129] If there are duplicate registration tags (S708, Yes), the registration tag presenting unit 112 merges the duplicate registration tags (S709). Here, the registration tag presenting unit 112 treats the duplicate registration tags as one registration tag while maintaining the connection with other registration tags, and counts the number of duplicate registration tags.
[0130] After the registered tags are merged, the registered tag presenting unit 112 determines whether there is an unselected category among the options for merging ( S710 ).
[0131] When there is no unselected category ( S710 , No), the registered label presentation unit 112 displays the network of the registered label ( S711 ), and ends the network display process.
[0132] On the other hand, when there is an unselected category ( S710 , Yes), the registered label presentation unit 112 selects the unselected category again ( S707 ).
[0133] In addition, in step S708, when there is no duplicate registered label (S708, No), the registered label presentation unit 112 determines whether there is an unselected category (S710).
[0134] In addition, in step S706 , when there is unselected tag information ( S706 , Yes), the registered tag presentation unit 112 selects the unselected tag information again ( S701 ).
[0135] In addition, in step S705 , when there are two or more unselected categories ( S705 , Yes), the registered label presentation unit 112 selects an unselected category again ( S702 ).
[0136] The network of registered labels generated in this way is Fig.17 As shown, it includes a node N representing each registration label and a link L connecting two nodes belonging to two adjacent categories in a preset category order, duplicate registration labels in the same category are merged, the connection relationship between the registration labels is displayed as the relationship represented by the link L, and the number of repetitions of each registration label is represented as the size of a circle, and the circle is a graphic representing the node N in the form of a bubble. According to the network display of the registration labels, the user can intuitively grasp the registration labels connected by multiple registration labels as important registration labels when retrieving events. In addition, by making the display of the node N different according to the category to which the registration label indicated by the node N belongs, the user can easily understand to which category the node N of interest belongs. In addition, in Fig.17 The order of categories displayed as a network in is set to "part", "phenomenon", and "treatment". Fig.17 In FIG. 1 , the drawing color of the node N differs for each category, but for example, the shape of the graphic representing the node N may differ for each category.
[0137] In the present embodiment, the event management program is recorded as an event management program pre-installed inside the above-mentioned event management device, but the event management program in the present invention also includes an event management program stored in a storage medium. Here, the so-called storage medium refers to all media that can be read and executed by the computer serving as the above-mentioned event management device, such as tapes, disks (hard disk drives, etc.), optical disks (CD-ROMs, DVD disks, etc.), magneto-optical disks (MO, etc.), flash memories, etc., which can be removed from the event management device, and media that can be transmitted via a network.
[0138] The embodiments of the invention have been described, but the embodiments are presented as examples and are not intended to limit the scope of the invention. The new embodiments can be implemented in various other ways, and various omissions, substitutions, and changes can be made without departing from the scope of the invention. The embodiments and their variations are included in the scope or spirit of the invention, and are included in the invention described in the claims and the scope of their equivalents.
[0139] Description of Reference Numerals
[0140] 10Event Management Device
[0141] 103 Incident Acquisition Department
[0142] 107 Incident Management Department
[0143] 108 Registration Tag Extraction Unit
[0144] 109 Registration Label Management Department
[0145] 110 condition acquisition department
[0146] 111 Search Tag Extraction Unit
[0147] 112 Registration Label Reminder Department
[0148] 114 Incident Notification Department
Claims
1. An event management device capable of managing events in a shared manner, characterized in that: The event management device has: An event acquisition unit that acquires an event in which a text input is performed by a registration user who registers the event; An event management department, which manages the acquired events; A registration tag extraction unit extracts registration tags as meta information of the event through text mining based on the acquired event; a registration tag management unit that manages the extracted registration tags as tag information corresponding to the managed event; A condition acquisition unit that acquires a condition input by a search user who searches for an event as condition information; A search tag extraction unit extracts search tags from the condition information; a registered tag presenting unit for presenting, to the search user, a registered tag having a high degree of similarity with the search tag from among the tag information managed by the registered tag managing unit in a selectable manner; as well as an event presenting unit for presenting to the search user an event having a high degree of similarity with the registration tag selected by the search user among the events managed by the event management unit, The extracted registration tags include a phrase indicating a passive occurrence of an event, a phrase indicating an active occurrence of an event, and a subject or object of the occurrence of the event. The registered tag extraction unit extracts a related tag by text mining based on the acquired event, wherein the related tag is meta information indicating a correlation between two registered tags. The registered tag management unit further establishes a correspondence between the related tags in the tag information and manages them. The event management device further includes a related tag prompting unit that presents the search user with a selectable representation of related registration tags by each related tag included in tag information including a plurality of registration tags that match the registration tag selected by the search user.
2. The event management device according to claim 1, characterized in that: The registration tag and the search tag are expressed in the same format as each other.
3. The event management device according to claim 1 or 2, characterized in that: The registered tag presenting unit presents, to the search user, selected registered tags from among the tag information managed by the registered tag managing unit, including the most registered tags matching the search tag.
4. The event management device according to claim 1 or 2, characterized in that: The event presenting unit presents, to the search user, an event associated with tag information including the most registered tags selected by the search user, among the events managed by the event management unit.
5. The event management device according to claim 1 or 2, characterized in that: The event management device is connected to a device log management device, which establishes a correspondence between at least one device and the device log, and manages the correspondence in time series, by measuring the measured value of a sensor that measures the change caused by the operation of the device or the error code output by the device as a device log. The event acquisition unit acquires device information and time information, wherein the device information indicates the device involved in the event input by the registered user, and the time information indicates the time range involved in the event. The event management device further includes a device log acquisition unit that acquires the device log from the device log management device based on the acquired device information and time information. The event management unit associates the acquired event with the acquired device log and manages the event.
6. The event management device according to claim 5, characterized in that: When the acquired device log includes an error code, the registration label extraction unit extracts the error code as the registration label.
7. The event management device according to claim 1 or 2, characterized in that: Each of the users holds a measuring device for measuring the user's behavior. The event management device, connected to a user log management device, which manages the measured values of at least one measuring device in a time series by associating the measured values of the measuring device with the measuring device as a user log, The device further comprises a user management unit for managing by associating user information uniquely indicating a predetermined user with measurement device information uniquely indicating the measurement device possessed by the user. The event acquisition unit is characterized by acquiring user information of a registered user who inputs an event and time information indicating a time range involved in the event. The event management device further includes a user log acquisition unit that acquires the user log from the user log management device based on the measurement device information associated with the acquired user information by the user management unit and the acquired time information. The event management unit associates the acquired event with the acquired user log and manages the event.
8. The event management device according to claim 1 or 2, characterized in that: The registered tag extraction unit classifies the registered tags into predetermined categories and extracts them. The registration tag management unit manages the registration tag by adding the category to which the registration tag belongs. The registered tag prompting unit connects the registered tags contained in each tag information of the managed tag information in a preset category order, merges the registered tags that are repeated with the registered tags contained in other tag information in the same category, and prompts the user with a network display that visualizes the number of repeated registrations.
9. A storage medium storing an event management program capable of managing events in a shared manner, characterized in that: The event management program enables the computer to function as the following: An event acquisition unit that acquires an event in which a text input is performed by a registration user who registers the event; An event management department, which manages the acquired events; A registration tag extraction unit extracts registration tags as meta information of the event through text mining based on the acquired event; a registration tag management unit that manages the extracted registration tags as tag information corresponding to the managed event; A condition acquisition unit that acquires a condition input by a search user who searches for an event as condition information; A search tag extraction unit extracts search tags from the condition information; a registered tag presenting unit for presenting, to the search user, a registered tag having a high degree of similarity with the search tag from among the tag information managed by the registered tag managing unit in a selectable manner; as well as an event presenting unit for presenting to the search user an event having a high degree of similarity with the registration tag selected by the search user among the events managed by the event management unit, The extracted registration tags include a phrase indicating a passive occurrence of an event, a phrase indicating an active occurrence of an event, and a subject or object of the occurrence of the event. The registered tag extraction unit extracts a related tag by text mining based on the acquired event, wherein the related tag is meta information indicating a correlation between two registered tags. The registered tag management unit further establishes a correspondence between the related tags in the tag information and manages them. The event management device further includes a related tag prompting unit that presents the search user with a selectable representation of related registration tags by each related tag included in tag information including a plurality of registration tags that match the registration tag selected by the search user.
10. An event management method capable of managing events in a shared manner, characterized in that: In this event management method, computer, Acquires an event in which a text input is performed by the user who registered the event. managing the obtained events, Based on the acquired event, a registration tag as meta information of the event is extracted by text mining, The extracted registration tag is managed as tag information corresponding to the managed event, Acquire the conditions input by the search user who searches for the event as condition information, Extracting a search tag from the condition information, presenting the search user with a selected registration tag having a high degree of similarity to the search tag among the managed tag information, presenting to the search user an event having a high degree of similarity with the registration tag selected by the search user among the managed events, The extracted registration tags include a phrase indicating a passive occurrence of an event, a phrase indicating an active occurrence of an event, and a subject or object of the occurrence of the event. The computer further Based on the acquired event, extracting related tags by text mining, wherein the related tags are meta information indicating the correlation between two registered tags. The related tags are further associated and managed in the tag information. The search user is presented with a selectable form of the registered tags represented by each of the related tags included in the tag information including a large number of registered tags that match the registered tag selected by the search user.
