JP2018014032A - Task monitoring device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a manager or the like to easily associate a task event with a case when it is impossible to automatically associate the task event with the case.SOLUTION: A management DB 22 manages task flow definition information defining a processing order of a plurality of different task processing for each case. A task monitoring server 10 acquires task event information related to a task event which has occurred as for the task processing, that is, task event information related to the task event causing the shift of a state of the task processing to be executed in the case. An automatic association part 34 automatically associates the task event information with the corresponding case. When any unassociated task event information which has not been automatically associated with the case exists, a candidate of the case of the association destination of the unassociated task event information is searched, and information indicating the case is output.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a business monitoring apparatus and program, and more particularly to a technology for monitoring a business processing status.

  There is a case where the business flow is monitored and the business is analyzed. For example, in a building management system, business processes (work) such as system information registration, arrangement of communication equipment set in a building, arrangement and implementation of construction and open test are performed, and each business process is managed. .

  Even when a business flow is monitored, the status of each business process is not necessarily visualized. For example, the start and end of each business process is not always managed appropriately. In such a case, problems such as inability to foresee process delays or provision of information necessary for examination of business improvement may occur. In order to cope with this, by collecting information for appropriately managing the business status from the system database (DB), logs, etc., it is possible to grasp the start and end of each business process and the frequency of occurrence of the business process. It is conceivable to analyze the business based on information such as the residence time. For example, it is conceivable to manage the business flow of each case by collecting the business event information related to the business event that changes the state of the case corresponding to the business flow and associating the business event with the case. For example, a business event is linked to a case by using a case ID included in the business event information.

  Patent Document 1 describes an apparatus that manages a list of in-process items and a list of business events including information for identifying the in-process items. It describes that a search for a business event that progresses the business status in each work-in-progress is triggered by the occurrence of a new business event.

  Patent Document 2 discloses an apparatus that manages a list of business events that can be linked to an in-process item, a list of business events that cannot be linked, and a pattern of information that is insufficient when linking to an in-process item Is described. It is described that when a business event that cannot be linked occurs, information is acquired from the linked business event of the in-process matter according to the missing information pattern and handled as a business event that can be linked. Yes.

  Patent Document 3 describes a function for mediating messages between business systems and a function for managing conditions for executing an extended function during mediation.

  Patent Document 4 discloses an apparatus that manages the occurrence timing of past business events. It describes that the timing for automatically acquiring business event information is determined according to the case ID and the past business event occurrence timing.

  Patent Document 5 describes an apparatus that manages the types of actions that change the progress state of a workflow and links arbitrary actions to the workflow.

JP 2008-84083 A JP 2008-210047 A JP 2012-14506 A Japanese Patent Laid-Open No. 2015-22475 JP 2014-96182 A

  As described above, when a business event is associated with a matter using the matter ID, if the matter ID is not included in the business event information, the business event cannot be associated with the matter. When the business event information is standard data, for example, when each business event information is created according to a common format, the other business event information including the case ID includes information included in the business event information to be linked. Related information (for example, information of the same content) may be included. In this case, the business event to be linked may be linked to the matter by referring to other business event information and matching the business event information. However, when the business event information is atypical data (for example, e-mail data), the business event may not be linked to the matter by such a linking process. For example, when different tools are used in each business process, each business event information corresponding to each business process may not be data having a common format. In this case, the other business event information does not always include information related to the information included in the business event information to be linked, so even if other business event information is referenced, The target business event cannot be linked to the matter. As described above, when different tools are used in each business process, it may occur that it is not possible to manage to which matter each business event belongs. Note that the devices described in the above Patent Documents 1-5 merely link the case with the business process when the case ID exists, and even if the case ID does not exist, Not tied to business processing.

  An object of the present invention is to enable an administrator or the like to easily associate a business event with a matter when the business event cannot be automatically associated with the matter.

  The invention according to claim 1 is a storage unit that stores business flow definition information that defines a processing order of a plurality of different business processes for each case, and an acquisition unit that acquires business event information related to a business event that has occurred in relation to the business process. An acquisition means for acquiring business event information related to a business event that causes a transition of the business process to be executed in the matter, a linking means for associating the business event information with the matter corresponding to the business event, and business event information A job monitoring apparatus comprising: output means for outputting item candidate information indicating a candidate for a case to which an unlinked business event information that is not linked to a matter in the group is associated.

  According to a second aspect of the present invention, in the business monitoring device according to the first aspect, when the business event information includes case identification information for identifying a case, the association means includes the case identification information The business event information is linked to the indicated case, the state of the business process to be executed in the case indicated by the case identification information is changed, and the output unit does not link the business event information that does not include the case identification information. The job monitoring apparatus is characterized in that the item candidate information indicating a candidate for a case to which unlinked business event information is linked is output as the linked business event information.

  According to a third aspect of the present invention, in the business monitoring device according to the second aspect, the output means includes a plurality of current statuses to be executed in each case and a plurality of business flow definition information defined in each business flow definition information. It includes an extraction unit that extracts candidates for the cases to which the unlinked business event information is linked based on the business process context and the business processing corresponding to the unlinked business event information. It is a business monitoring device that performs.

  According to a fourth aspect of the present invention, in the business monitoring device according to the third aspect, the extraction unit obtains business event information related to a business event that may occur next for each item based on the business flow definition information. A job monitoring apparatus characterized by extracting a case where the specified acquisition source type is the same as the acquisition source type of unlinked business event information as a priority candidate .

  According to a fifth aspect of the present invention, in the business monitoring device according to any one of the first to fourth aspects, the output means is based on unlinked business event information in accordance with a preset narrowing condition. The business monitoring apparatus further outputs information indicating a matching determination result between the obtained information and the information obtained from the business flow definition information.

  The invention according to claim 6 is the business monitoring apparatus according to any one of claims 1 to 5, wherein the business event information is atypical data.

  The invention according to claim 7 is the business monitoring apparatus according to claim 6, wherein the business event information is operation history information related to business processing, e-mail data related to business processing, or log information related to business processing. It is a business monitoring device characterized.

  The invention according to claim 8 obtains business event information related to a business event that has occurred in relation to a business process, management means for managing business flow definition information that defines a processing order of a plurality of different business processes for each case. An acquisition means, an acquisition means for acquiring business event information related to a business event that changes the state of the business process to be executed in the matter, a linking means for associating the business event information with the matter corresponding to the business event, and business event information This is a program that functions as an output unit that outputs item candidate information indicating candidates for a case to which unlinked business event information is not linked to a case in a group.

  According to the present invention, when a business event cannot be automatically associated with a matter, an administrator or the like can easily associate a business event with a matter.

It is a block diagram which shows an example of the work monitoring system which concerns on embodiment of this invention. It is a block diagram which shows an example of the work monitoring server which concerns on embodiment of this invention. It is a block diagram which shows an example of a business server. It is a block diagram which shows an example of a mail server. It is a block diagram which shows an example of a business terminal device. It is a block diagram which shows an example of the automatic correlation part and management DB which concern on this embodiment. It is a block diagram which shows an example of the manual association part and management DB which concern on this embodiment. It is a figure which shows an example of business flow definition information. It is a figure which shows an example of the business event management table. It is a figure which shows an example of a business management table. It is a figure which shows an example of a narrowing-down condition table. It is a flowchart which shows an example of the process by the work monitoring server which concerns on this embodiment. It is a figure which shows the flow of a business flow. It is a figure which shows an example of a search result list. It is a figure which shows an example of the screen for a correlation.

  FIG. 1 shows an example of a business monitoring system according to an embodiment of the present invention. The business monitoring system according to the present embodiment is a system that monitors a business flow related to building management, for example. Of course, the business monitoring system according to the present embodiment may monitor a business flow related to a business other than building management.

  As an example, the business monitoring system includes a business monitoring server 10, a business server 12, a mail server 14, a business terminal device 16, and an administrator terminal device 18. These are connected to a communication path N such as a network, and communicate with each other via the communication path N. In the example illustrated in FIG. 1, the business server 12, the mail server 14, and the business terminal device 16 are included in the business monitoring system as examples of business processing devices. However, these business processing devices are merely examples. . Another business processing device may be included in the business monitoring system. As another example, some or all of these may not be included in the business monitoring system, and another business processing device may be included in the business monitoring system.

  The business monitoring server 10 corresponds to an example of a business monitoring device, and is a device that monitors a business flow for each item. The business flow is composed of a plurality of different business processes. For example, the processing order of each business process is set in advance, and the business process is executed according to the processing order. The business process is a unit of a process constituting the business flow, and examples thereof include customer information registration, equipment arrangement, execution of construction / opening test, and the like. Of course, these business processes are merely examples, and another process may be included in the business flow as the business process, or one or a plurality of business processes illustrated may not be included in the business flow. As will be described later, the business monitoring server 10 acquires business event information related to a business event that has occurred regarding business processing from the business server 12, the mail server 14, and the business terminal device 16, and based on the business event information, Manage the status of Items. A business flow is applied to a case, and for example, a case is established for each customer or each service.

  The business server 12 is a device that executes business processing and manages the history of business processing. Of course, the business server 12 may manage the business process history without executing the business process itself. The business server 12 executes customer information registration as business processing, for example, and manages a history related to customer information registration. When a business event relating to customer information registration (for example, operation, work, or processing) occurs, the business server 12 manages the history of the business event. For example, the business server 12 creates information (history information) indicating the history, and stores the history information as business event information.

  The mail server 14 is a device that manages transmission and reception of electronic mail. For example, transmission / reception of electronic mail corresponds to an example of a business event. When transmission / reception of electronic mail (business event) occurs, the mail server 14 stores the data of the electronic mail as business event information.

  The business terminal device 16 is a device such as a personal computer (PC), a tablet PC, a smartphone, or a mobile phone, and is a device that executes business processing and manages a log of business processing. Of course, the business terminal device 16 may manage the business process log without executing the business process itself. The business terminal device 16 executes a construction / opening test as a business process, for example, and manages a log related to the construction / opening test. When a business event (for example, operation, work, or processing) related to a construction / opening test occurs, the business terminal device 16 manages a log of the business event. For example, the business terminal device 16 creates information (log information) indicating the log, and stores the log information as business event information.

  The manager terminal device 18 is a device such as a PC, a tablet PC, a smartphone, or a mobile phone, and is a device used by a manager or operator of the business monitoring system. As will be described later, the manager terminal device 18 is used when manually associating a business event and a case.

  In the business monitoring system according to the present embodiment, each business process is executed according to the business flow, and a business event related to each business process occurs. The business monitoring server 10 collects business event information related to business events from the business server 12, the mail server 14, and the business terminal device 16, and associates the business events with the matter. A business event that is not automatically associated with a case is provided to an administrator or an operator. In addition, candidates for cases to which the business event is linked are also provided to the administrator, the operator, and the like. An administrator, an operator, or the like manually associates a business event and a matter with reference to the provided information.

  Hereinafter, the business monitoring system according to the present embodiment will be described in detail.

  First, the business monitoring server 10 will be described in detail with reference to FIG. The business monitoring server 10 includes, for example, a communication unit 20, a management DB 22, an automatic linking unit 34, and a manual linking unit 36.

  The communication unit 20 is a communication interface and has a function of transmitting data to another device and a function of receiving data from another device via the communication path N.

  The management DB (database) 22 is a storage device such as a hard disk or a memory, and stores various data. The management DB 22 includes, for example, a business event management unit 24, a filter definition management unit 26, a business flow definition management unit 28, a case management unit 30, and a narrowing condition management unit 32. Hereinafter, each management unit will be described.

  The business event management unit 24 is a storage device such as a hard disk or a memory, and stores business event information collected from business processing devices (for example, the business server 12, the mail server 14, the business terminal device 16 and the like). Every time business event information is collected, the collected business event information is stored and managed in the business event management unit 24.

  The business event information includes, for example, business event identification information, item association state information, occurrence time information, resource type information, and event content information.

  The business event identification information is information (for example, an event ID) for identifying a business event. For example, when the business event information is collected by the business monitoring server 10, the business event identification information is uniquely given to the business event information and added to the business event information.

  The case linking state information is information indicating a linking state of business event information to the case (for example, unlinked, linked, unlinked, etc.). As will be described later, when the business event information is linked to the matter by the automatic linking unit 34 or the manual linking unit 36, the linking state is updated to linked.

  The occurrence time information is information indicating the date and time when the business event occurred, and is added to the business event information by a business processing device (for example, the business server 12, the mail server 14, the business terminal device 16 or the like). .

  The resource type information is information indicating the type of the business processing device that is the acquisition source of the business event information, and is added to the business event information by the business processing device that is the acquisition source. For example, the business event information related to customer information registration includes resource type information indicating the business server 12 or resource type information indicating a device (for example, a database) configuring the business server 12. The business event information related to device arrangement includes resource type information indicating the mail server 14 or resource type information indicating electronic mail. The business event information related to the construction / opening test includes resource type information indicating the business terminal device 16 or resource type information indicating log information.

  The event content information is information indicating the content of the business event. The business event information related to customer information registration includes operation history information related to customer information registration. The business event information related to device arrangement includes information indicating the contents described in the body text, title, etc. of the e-mail. The business event information related to the construction / opening test includes log information related to the construction / opening test.

  The business event information may include item identification information (for example, item ID) for identifying the item. Further, the service event information may include service name information indicating the name of a service provided for the case (hereinafter referred to as “service name”). Further, the business event information may include information indicating the name of an application related to business processing (hereinafter referred to as “application name”).

  The filter definition management unit 26 is a storage device such as a hard disk or a memory, and stores determination condition information as filter definition information. The determination condition information is information for determining whether or not a business event that has occurred in the business processing device corresponds to a business event that changes the state of the business processing in the matter. The determination condition information is created in advance and stored and managed in the filter definition management unit 26.

  The business flow definition management unit 28 is a storage device such as a hard disk or a memory, and stores business flow definition information for each business flow. The business flow definition information is information that defines the processing order of a plurality of different business processes. The business flow definition information is created in advance and stored and managed in the business flow definition management unit 28.

  As an example, the business flow definition information includes service name information, business flow name information, business process identification information, start event information, end event information, and specific definition information (for example, BPMN) of the business flow.

  The service name information is information indicating the service name of the target business flow. The business flow name information is information indicating the name of the business flow. The business process identification information is identification information (for example, a business process name) for identifying each business process included in the business flow. A plurality of business processes are defined in the business flow, and the business process identification information for each business process is included in the business flow definition information. The start event information is information indicating a business event corresponding to the start timing of each business process (for example, information indicating a resource type in which the start event has occurred). The end event information is information indicating a business event corresponding to the end timing of each business process (for example, information indicating a resource type in which the end event has occurred). The processing order of each business process is specifically defined by specific definition information of the business flow.

  The case management unit 30 is a storage device such as a hard disk or a memory, and stores information (hereinafter, “case information”) indicating the state of the case (that is, the status of the business process to be executed in the case) for each case. The matter information is updated each time the matter status changes.

  For example, the case information includes case identification information for identifying the case (for example, case ID), business flow name information indicating the name of the business flow applied to the case, and the current execution target in the case. Business process identification information for identifying the current business process, and status information indicating the status of the business process to be executed.

  The narrowing condition management unit 32 is a storage device such as a hard disk or a memory, and stores narrowing condition information. The narrowing condition information is information indicating a condition for narrowing down the candidates of the cases to which the business event information (hereinafter referred to as “unlinked business event information”) that is not linked to the matter is linked.

  The automatic associating unit 34 has a function of automatically associating business event information collected from the business processing apparatus with a corresponding matter and updating the state of the matter. For example, when the case identification information is included in the business event information, the automatic association unit 34 associates the business event information with the case indicated by the case identification information, and updates the state of the case.

  The manual linking unit 36 extracts unlinked business event information that has not been linked by the automatic linking unit 34, and extracts candidate items that are linked to the unlinked business event information. It has a function to output attached job event information and item candidate information indicating item candidates. Further, the manual linking unit 36 has a function of linking unlinked business event information to a matter in accordance with an instruction from a user such as an administrator or an operator.

  Next, the business server 12 will be described in detail with reference to FIG. The business server 12 executes, for example, customer information registration as business processing, and manages an operation history related to customer information registration. Of course, the business server 12 may manage the history by executing another business process. The business server 12 includes, for example, a communication unit 38, a control unit 40, a business DB (database) 42, and a collection unit 44.

  The communication unit 38 is a communication interface and has a function of transmitting data to another device and a function of receiving data from another device via the communication path N.

  The control unit 40 controls the operation of each unit of the business server 12. Further, the control unit 40 executes customer information registration as business processing and manages an operation history related to customer information registration. Operations and work related to customer information registration correspond to an example of a business event. The business event in this case is, for example, new registration of a case for each customer, approval of the registration, and the like. For example, a business system is realized by the control unit 40 executing a business processing application, and an operator operates the business system to newly register or approve a case for each customer. When a business event such as new registration or approval occurs, the control unit 40 manages an operation history corresponding to the business event. The control unit 40 creates information indicating the operation history (hereinafter referred to as “operation history information”), and stores the operation history information in the business DB 42 as business event information. The operation history information is, for example, standard data, and is data created according to a preset format. The operation history information includes, for example, item identification information (for example, item ID and item name) for identifying an item, information indicating the contents of a business event (for example, new registration, registration approval, etc.), and the like. Of course, the operation history information may be atypical data. In this case, the operation history information is data created according to an arbitrary format, and may not include item identification information.

  The business DB 42 is a storage device such as a hard disk or a memory, and stores operation history information (business event information).

  The collection unit 44 has a function of collecting business event information from the business DB 42. The business event information collected by the collection unit 44 is transmitted to the business monitoring server 10 via the communication path N by the communication unit 38.

  Next, the mail server 14 will be described in detail with reference to FIG. The mail server 14 is a device that transmits and receives e-mails and manages the e-mails. Of course, the mail server 14 may manage an electronic mail related to another business process. The mail server 14 includes, for example, a communication unit 46, a control unit 48, a mail box 50, an account storage unit 52, and a collection unit 54.

  The communication unit 46 is a communication interface and has a function of transmitting data to another device and a function of receiving data from another device via the communication path N.

  The control unit 48 controls the operation of each unit of the mail server 14. The control unit 48 controls transmission / reception of electronic mail. Transmission / reception of electronic mail corresponds to an example of a business event. For example, an operator uses a terminal device or the like to send and receive electronic mail related to device arrangement. When an electronic mail transmission / reception (business event) relating to device arrangement occurs, the control unit 48 stores the electronic mail data in the mail box 50 as business event information. The e-mail data is, for example, atypical data, and is not data created according to a preset format. The format of the body and title of the e-mail is an arbitrary format, and the format varies depending on, for example, the worker or the e-mail application. Therefore, the case identification information may be described in the text or title of the e-mail, or the case identification information may not be described.

  The mail box 50 is a storage device such as a hard disk or a memory, and stores electronic mail data.

  The account storage unit 52 is a storage device such as a hard disk or a memory, and stores information indicating a business mailing list, information indicating a monitoring mail account, and the like. The business mailing list includes a monitoring mail account. The control unit 48 stores e-mail data corresponding to the monitoring e-mail account in the mail box 50, for example.

  The collection unit 54 has a function of collecting business event information from the mailbox 50. The business event information collected by the collection unit 54 is transmitted to the business monitoring server 10 via the communication path N by the communication unit 46.

  Next, the business terminal device 16 will be described in detail with reference to FIG. The business terminal device 16 executes, for example, a construction / opening test as a business process, and manages a log related to the construction / opening test. Of course, the business terminal device 16 may manage the log by executing another business process. The business terminal device 16 includes, for example, a communication unit 56, a control unit 58, a storage unit 60, and a collection unit 62.

  The communication unit 56 is a communication interface, and has a function of transmitting data to another device and a function of receiving data from another device via the communication path N.

  The control unit 58 controls the operation of each unit of the business terminal device 16. In addition, the control unit 40 executes a construction / opening test as a business process and manages a log related to the construction / opening test. Operations and work related to construction / opening tests correspond to examples of business events. The business event in this case is, for example, communication start, communication success, or the like. For example, when the control unit 58 executes a business processing application and the operator operates the business processing application, the construction / opening test is executed. When a business event such as communication start or communication success occurs, the control unit 58 manages a log corresponding to the business event. The control unit 58 creates information indicating the log (hereinafter referred to as “log information”), and stores the log information in the storage unit 60 as business event information. The log information is, for example, standard data, and includes, for example, item identification information, information indicating the contents of business events (for example, communication start, communication success, etc.), and the like. Of course, the log information may be atypical data.

  The storage unit 60 is a storage device such as a hard disk or a memory, and stores business event information including log information.

  The collection unit 62 has a function of collecting business event information from the storage unit 60. The business event information collected by the collection unit 62 is transmitted to the business monitoring server 10 via the communication path N by the communication unit 56.

  Hereinafter, the business monitoring server 10 according to the present embodiment will be described in more detail.

  First, the automatic linking unit 34 will be described in detail with reference to FIG. FIG. 6 shows the automatic linking unit 34 and the management DB 22. For convenience of explanation, FIG. 6 does not show the refinement condition management unit 32 included in the management DB 22. The automatic association unit 34 includes, for example, a business event collection unit 64, a business event determination unit 66, a case update unit 68, and a notification unit 70.

  The business event collection unit 64 has a function of collecting business event information transmitted from a business processing device (for example, the business server 12, the mail server 14, and the business terminal device 16). The business event collection unit 64 adds the business event identification information to the business event information, stores the business event information in the business event management unit 24, and outputs the business event information to the business event determination unit 66.

  The business event determination unit 66 determines whether or not the business event indicated by the business event information collected by the business event collection unit 64 corresponds to a business event that changes the state of the business processing in the matter. For example, when the case identification information is included in the business event information, the case indicated by the case identification information is the case corresponding to the business event indicated by the business event information. In this case, the business event determination unit 66 determines whether or not the business event indicated by the business event information corresponds to a business event that changes the state of the business processing in the case indicated by the case identification information. Specifically, the business event determination unit 66 refers to the information stored in the case management unit 30 to identify the case information including the case identification information included in the business event information, and includes the case information in the case information. Get business flow name information. The business event determination unit 66 acquires the business flow definition information including the business flow name information from the business flow definition management unit 28, and the business flow content indicated by the business flow definition information and the business event content indicated by the business event information. To determine whether or not the business event corresponds to a business event that changes the state of business processing in the matter. Specifically, the business event determination unit 66 acquires the determination condition information from the filter definition management unit 26, and according to the determination condition indicated by the determination condition information, the content of the business flow indicated by the business flow definition information and the business event information Is matched with the content of the business event indicated by, it is determined whether or not the business event corresponds to a business event that changes the state of business processing in the matter. For example, when determining whether or not a running business process has ended, the service names indicated by the business flow definition information and the business event information match, and the business process name and the application name match. If the resource type corresponding to the business process in the business flow matches the resource type from which the business event information is acquired, the business event indicated by the business event information changes the state of the business process. It is determined that it corresponds to the business event to be ended (for example). This conditional expression is only an example, and may be used for other conditional expressions.

  In addition, the business event determination unit 66 outputs information indicating the determination result to the business event management unit 24, and updates the case association state information included in the business event information according to the determination result. For example, when it is determined that the business event corresponds to a business event that changes the state of the business process in the matter, the association state between the business event and the matter is updated to “linked”. That is, since the business event information includes the case identification information, the case to which the connection is made is specified, and the connection state is “attached”. Even if the business event does not correspond to a business event that changes the status of business processing in the matter, if the business event information includes matter identification information, the business event is linked to the matter The state may be updated to “linked”.

  If the business event information does not include the case identification information, the business event and the case cannot be linked using the case identification information, and the linked state of the business event is “unlinked”.

  When it is determined that the business event corresponds to a business event that changes the state of the business process in the matter, the matter update unit 68 updates the state of the business process in the matter according to the content of the business event. For example, when the case identification information is included in the business event information, the case update unit 68 searches the case management unit 30 for the case information including the case identification information and updates the state information included in the case information. To do. For example, when the business event corresponds to a business event that ends the business process, the matter update unit 68 records the end of the business process. If Item identification information is not included in the business event information, the Item status is not updated.

  As described above, the business event determination unit 66 and the case update unit 68 automatically associate the business event with the case and update the state of the case. For example, when the matter identification information is included in the business event information, the business event and the matter are linked, and when the business event corresponds to the business event that changes the state of the matter, the state of the matter is updated. On the other hand, if the matter identification information is not included in the business event information, the matter corresponding to the business event cannot be identified depending on the matter identification information, so the business event and the matter are not linked, and the matter status Will not be updated.

  The notification unit 70 has a function of notifying a business event that is not automatically associated with a case (hereinafter referred to as “unlinked business event”). For example, information indicating that an unlinked business event exists is transmitted to the manager terminal device 18 via the communication path N and displayed.

  Next, the manual tying portion 36 will be described in detail with reference to FIG. FIG. 7 shows the manual linking unit 36 and the management DB 22. For convenience of explanation, the filter definition management unit 26 included in the management DB 22 is not shown in FIG. The manual association unit 36 includes, for example, a business event search unit 72, a case search unit 74, a business process search unit 76, and a case update unit 78.

  The business event search unit 72 has a function of searching the business event management unit 24 for unlinked business event information related to an unlinked business event that is not linked to a matter. Information indicating the search result (for example, business event identification information of an unlinked business event) is transmitted to the manager terminal device 18 via the communication path N and displayed.

  The case search unit 74 has a function of searching for a case in the case management unit 30. For example, in the manager terminal device 18, when an unlinked business event is designated by an administrator or the like, the matter search unit 74 searches for a matter. Unlinked business event information and item information are output to the business process search unit 76.

  The business process search unit 76 acquires the business flow definition information from the business flow definition management unit 28, acquires the narrowing condition information from the narrowing condition management unit 32, and the business flow definition information and the business flow definition information according to the narrowing condition indicated by the narrowing condition information It has a function to search for candidate candidates associated with unlinked business events from unlinked business event information. For example, when a list of unlinked business events is displayed on the administrator terminal device 18 and an unlinked business event is designated by the administrator or the like from the list, the business process search unit 76 displays the unlinked business event. Search for the candidate for the case to which the attached business event is linked. The case candidate information indicating the candidate for the case is transmitted to the manager terminal device 18 and displayed on the manager terminal device 18.

  The business process search unit 76, for example, the current state of the execution target (for example, being executed) in each case and the context of a plurality of business processes defined in each business flow definition information (process order context) Based on the business process corresponding to the unlinked business event information, the candidate of the case to which the unlinked business event information is linked is searched. More specifically, the business process search unit 76 specifies the type (resource type) of the business event information acquisition source for the business event that can occur next, based on the business flow definition information for each case, and specifies that Cases in which the assigned resource type is the same as the resource type of the unlinked business event information are extracted as priority candidates.

  The case update unit 78 receives the case identification information for identifying the case and the business event identification information for identifying the unlinked business event from the manager terminal device 18, and receives the business process in the case. Update state. In addition, the case update unit 78 accesses the business event management unit 24 and updates the case association state information included in the unlinked business event information. In this case, the linking state between the unlinked business event and the case is updated to “linked”.

  Hereinafter, the business monitoring system according to the present embodiment will be described in detail with specific examples.

  First, a specific example of business flow definition information will be described with reference to FIG. FIG. 8 shows an example of a business flow definition. This business flow definition information is created in advance and stored in the business flow definition management unit 28. The service name of this business flow is “Facima Support Contract”. This business flow includes “customer information registration”, “device arrangement”, and the like as business processing. The business DB and the mailbox correspond to examples of resource types.

  Next, a specific example of business event information will be described with reference to FIG. FIG. 9 shows a business event management table as an example of business event information. The business event management table is a table showing a list of business event information, and the data of the table is stored in the business event management unit 24. Each time business event information is collected by the business event collection unit 64, the business event information is added to the business event management table and the business event management table is updated. In the business event management table, as an example, for each business event, EID (event ID) as business event identification information, information indicating a resource type, PID (case ID) as case identification information, and detailed information correspond It is attached. This resource type is the resource type from which the business event is acquired. For example, the business event information with the event ID “2” is information collected from the business DB (the business DB 42 of the business server 12). The detailed information includes information indicating the contents of the business event information. Further, although not shown, the business event management table includes item association state information, occurrence time information, and the like. Since the business event information with the event ID “2” includes the case ID “XXX”, the business event with the business ID associated with the business event information is identified. As a result, the business event with the event ID “2” is identified. And the case with the case ID “XXX” are associated with each other. On the other hand, the business event information with the event ID “3” does not include the case ID, so the case to which the business event information is linked is not specified. Therefore, the business event with the event ID “3” is not linked to the matter, and the business event is handled as an unlinked business event.

  Next, a specific example of the case information will be described with reference to FIG. FIG. 10 shows a case management table as an example of case information. This case management table is a table showing a list of case information, and the data of the table is stored in the case management unit 30. Each time a new matter is registered, matter information is added to the matter management table and the matter management table is updated. In the case management table, for example, for each case, PID (case ID) as case identification information, business flow name information indicating the name of the business flow applied to the case, execution target (for example, executing) Information indicating the business process is associated with status information indicating the status of the business process. As an example, when a case with the case ID “XXX” is described, the name of the business flow applied to the case is “Facema support contract / facima support preparation”, and the business that is currently being executed The process is “customer information registration”, and the “customer information registration” is completed. Information indicating the business process to be executed and status information indicating the status of the business process are updated by the case update unit 68 at the time of automatic association, and updated by the case update unit 78 at the time of manual association.

  Next, a specific example of narrowing-down condition information will be described with reference to FIG. FIG. 11 shows a narrowing condition table as an example of narrowing condition information. This narrowing condition table is a table showing a list of narrowing conditions, and data of the table is created in advance and stored in the narrowing condition management unit 32. In the refinement condition table, information indicating a tag name and information indicating a refinement conditional expression are associated with each refinement condition. The tag name is the name of the narrowing-down condition. The conditional expression is a conditional expression for narrowing down the candidate for the case associated with the unlinked business event. For example, the conditional expression with the tag name “matching person in charge” is a narrowing-down condition when the unlinked business event information is e-mail data. In this example, the case where the person in charge email address included in the matter information matches the email address of the sender included in the unlinked business event information (the email address described in the FROM header) is not linked. Searched as a candidate for a business event linked to a business event. The conditional expression whose tag name is “match resource type” is a conditional expression for searching for a candidate for a case based on the resource type of the unlinked business event information. In this example, the business event resource type that can occur next and the resource type of the unlinked business event information for the business process of the execution target (for example, running) in the business flow corresponding to the matter match However, it is searched as a candidate for a case to which an unlinked business event is linked.

  The business process search unit 76 may search for a candidate for a case according to a preset narrowing condition, or may search for a case according to a narrowing condition specified by an administrator or the like. Further, the business process search unit 76 may search for cases according to one narrowing condition, or may search for cases according to a plurality of narrowing conditions. When using a plurality of filtering conditions, an “AND condition search” that searches for jobs that satisfy all filtering conditions may be performed, or “OR that searches for a job that satisfies at least one of the filtering conditions” “Condition search” may be executed. The search method is selected by an administrator or the like, for example. Of course, the search method may be set in advance.

  Hereinafter, with reference to FIG. 12, the process by the work monitoring server 10 will be described. FIG. 12 is a flowchart showing the processing.

  When a business event occurs in a business processing device (for example, business server 12, mail server 14, business terminal device 16), the business event collection unit 64 of the business monitoring server 10 receives business event information from each business processing device. Are collected (S01). The collected business event information is stored in the business event management unit 24.

  When the business event information is collected, the business event determination unit 66 changes the state of the business process in the matter according to the determination condition indicated by the determination condition information stored in the filter definition management unit 26 (for example, It is determined whether or not the business event is to be started or ended (S02). Information indicating the determination result is output to the business event management unit 24, and the business event association response is updated according to the determination result. For example, when matter identification information is included in the business event information, if it is determined that the business event corresponds to a business event that changes the state of business processing in the matter, the business event and the matter are linked. The status is updated to “Linked”. Of course, even if the business event does not correspond to a business event that changes the state of business processing in the matter, if the business event information includes matter identification information, the business event may be linked to the matter. On the other hand, when the case identification information is not included in the business event information, the business event is not linked to the case, and the business event information is managed as unlinked business event information.

  When the business event corresponds to a business event that changes the state of the business process in the matter, the matter update unit 68 updates the state of the matter according to the content of the business event (S03). That is, the case update unit 68 changes (for example, starts or ends) the state of the business process to be executed in the case (the business process corresponding to the business event).

  When there is unlinked business event information, the fact is notified to the manager terminal device 18 (S04). Hereinafter, manual tying work is performed.

  First, when an administrator or the like uses the manager terminal device 18 to instruct a search for an unlinked business event, the business event search unit 72 of the business monitoring server 10 causes the business event management unit 24 to execute an unlinked business event. Search for an event (S05). Information indicating the search result (for example, business event identification information of an unlinked business event) is transmitted to the manager terminal device 18 and displayed. For example, a list of unlinked business events is displayed.

  Next, when the administrator uses the manager terminal device 18 to select an unlinked business event to be linked from the list of unlinked business events, the matter search unit 74 of the business monitoring server 10 Searches for a case in the case management unit 30 (S06). Information indicating a search result (a list of cases) is output to the business process search unit 76 of the business monitoring server 10.

  The business process search unit 76 searches for a candidate for a case to which an unlinked business event is linked from the list of cases according to the narrowing-down conditions (narrows down) (S07). For example, if the resource type of the unlinked business event matches the resource type corresponding to the business process to be executed in the business flow corresponding to the matter, the matter is extracted as a candidate for the linked destination matter. The As another example, when the service name indicated by the service name information included in the unlinked business event information matches the service name of the case, the case is extracted as a candidate for the linked destination case. Of course, a candidate for a linked item may be extracted according to another narrowing condition.

  Information indicating the search result of the case (list of cases) is transmitted to and displayed on the manager terminal device 18 (S08). For example, in the list of cases, cases that meet the narrowing-down conditions are displayed preferentially. Items that have a larger number of matches of the filtering conditions may be preferentially displayed, or items that match a specific filtering condition may be displayed with priority.

  When an administrator or the like uses the administrator terminal device 18 to specify a case to be linked from among the cases and gives a linking instruction, the case update unit 78 of the business monitoring server 10 Are associated with the business event of the designated association destination (S09). As a result, in the business event management unit 24, the case linking state information included in the business event information to be linked is updated, and the linking status becomes “linked”. Further, the case update unit 78 changes the state of the case of the association destination. Thereby, in the case management unit 30, the state (for example, start or end) of the business process to be executed (for example, being executed) in the case of the association destination is changed.

  Hereinafter, the process according to the present embodiment will be described with a specific example.

  First, an example of the flow of business flow will be described in detail with reference to FIG. This business flow includes customer information registration indicated by reference numeral 80, equipment arrangement indicated by reference numeral 82, and construction / opening test indicated by reference numeral 84 as business processes, and each business process is executed in this order.

  The resource type corresponding to the business process “customer information registration” is the business server 12 (business DB 38). That is, business event information (operation history information) related to the business process “customer information registration” is collected from the business server 12. The resource type corresponding to the business process “device arrangement” is the mail server 14 (e-mail indicated by reference numeral 86). That is, business event information (electronic mail data) related to the business process “device arrangement” is collected from the mail server 14. The resource type corresponding to the business process “construction / opening test” is the business terminal device 16 (log indicated by reference numeral 88). That is, the business event information (log information) related to the business process “construction / opening test” is collected from the business terminal device 16.

  The operation history related to the business process “customer information registration” is managed by the business server 12 described above, and the operation history information is stored in the business DB 38. For example, when “new registration” or “approval” of a matter corresponding to a customer is performed as a business event related to the business process “customer information registration”, operation history information indicating “new registration” or “approval” is stored in the business DB 38. Remembered. In the example illustrated in FIG. 13, as business events related to the business process “customer information registration”, “new registration” for the matter “XXX”, “new registration” for the matter “YYY”, and “approval” for the matter “YYY”. In addition, “Approval” for the item “XXX” is performed, and each operation history information is stored in the business DB 38. The operation history information is collected as business event information by the business event collection unit 64 of the business monitoring server 10 and stored in the business event management unit 24.

  The operation history information (business event information) for the business process “customer management registration” is, for example, standard data, and each operation history information (each business event information) has a case ID (for example, “XXX” as the case identification information). "," YYY "). Therefore, by referring to the operation history information, the linked event is specified, the business event and the job can be automatically linked, and the linked status of each business event is “linked”. In the business event management unit 24, the case association state information of each business event is updated, and the association state is already associated.

  The business event “new registration” is a business event that corresponds to the “start” of the business process “customer information registration” and changes the state of the business process “customer information registration”. Therefore, when the business event information (operation history information) indicating the business event “new registration” for the case “XXX” is collected, the case management unit 30 updates the state of the case “XXX”. That is, the status of the business process “customer information registration” in the case “XXX” is updated to “start”.

  The business event “approval” corresponds to the “end” of the business process “customer information registration” and changes the state of the business process “customer information registration”. Therefore, when the business event information (operation history information) indicating the business event “approval” for the case “XXX” is collected, the case management unit 30 updates the state of the case “XXX”. That is, the status of the business process “customer information registration” in the case “XXX” is updated to “finished”.

  Similarly, when the business event information indicating the business event “new registration” for the case “YYY” is collected, the state of the business process “customer information registration” in the case “YYY” is set to “started” in the case management unit 30. Is updated. When the business event information indicating the business event “approval” for the case “YYY” is collected, in the case management unit 30, the status of the business process “customer information registration” in the case “YYY” is changed to “finished”. Updated.

  Note that, as described above, the business event determination unit 66 determines whether or not the business event corresponds to a business event that changes the state of the business process, and the business process state update unit 68 updates the business process state. Is done by.

  E-mail data related to the business process “device arrangement” is managed by the above-described mail server 14 and stored in the mail box 50. For example, when an electronic mail is transmitted / received as a business event related to the business process “device arrangement”, the data of the electronic mail is stored in the mail box 50 of the mail server 14. In the example illustrated in FIG. 13, as a business event related to the business process “equipment arrangement”, an e-mail including contents related to the case “XXX”, a reply of e-mail including contents related to the case “XXX”, and a content related to the customer “A” And the like, and the data of each e-mail is stored in the mail box 50. The email data is collected as business event information by the business event collection unit 64 of the business monitoring server 10 and stored in the business event management unit 24.

  The e-mail data for the business process “device arrangement” is, for example, atypical data, and there may be a case ID as case identification information in the body or title of each e-mail. It may not be described. When the case ID is described in the body text or title of the email, by referring to the email data as the business event information, the target event can be identified and the business event and the matter can be automatically linked. Thus, the association state of the business event is “associated”. In the business event management unit 24, the matter association state of the business event is updated, and thereby the association state is updated to the association state. On the other hand, if the case ID is not described in the body or title of the e-mail, even if the e-mail data is referenced, the case of the association destination is not specified, and the association state of the business event is “unlinked” Become. In the business event management unit 24, the matter association state of the business event is maintained as unassociated.

  In the example shown in FIG. 13, the title of the electronic mail indicated by reference numeral 90 includes “Bill (XXX)”. Since “XXX” is a case ID, the case “XXX” to which this e-mail is linked is specified. Therefore, it is possible to automatically associate the e-mail data (business event information) with the matter “XXX”, and the business event management unit 24 updates the matter associating state of the e-mail data so as to associate the matter. Will be linked. Similarly, since there is a description “RE: Bill (XXX)” in the title of the e-mail indicated by reference numeral 92, the case “XXX” to which this e-mail is linked is specified. Therefore, it is possible to automatically associate the e-mail data (business event information) with the matter “XXX”, and the business event management unit 24 updates the matter associating state of the e-mail data so as to associate the matter. Will be linked. On the other hand, the title of the e-mail indicated by reference numeral 94 has a description of “case of customer A”, but the case ID is not described in the title and text. Therefore, the link destination of this e-mail is not specified. In the business event management unit 24, the association state of the email data is maintained unassociated. That is, the e-mail data indicated by reference numeral 94 is managed as unlinked business event information.

  The business event “e-mail transmission” is a business event corresponding to the “start” of the business process “device arrangement” and changes the state of the business process “device arrangement”. The processing for the electronic mail indicated by reference numeral 90 is “transmission”. Therefore, when the electronic mail data (business event information) indicated by reference numeral 90 is collected, the case management unit 30 updates the state of the case “XXX”. That is, the status of the business process “device arrangement” in the case “XXX” is updated to “start”.

  The business event “reply to electronic mail” is a business event that corresponds to the “end” of the business process “device arrangement” and changes the state of the business process “equipment arrangement”. The processing for the electronic mail indicated by reference numeral 92 is “reply”. Therefore, when the electronic mail data (business event information) indicated by the reference numeral 92 is collected, the case management unit 30 updates the state of the case “XXX”. That is, the status of the business process “device arrangement” in the case “XXX” is updated to “finished”.

  Since e-mail data (business event information) related to the case “YYY” is not collected, the state of the business process “device arrangement” in the case “YYY” does not change.

  The log relating to the business process “construction / opening test” is managed by the business terminal device 16 described above. For example, when “communication start” or “communication success” occurs as a business event related to the business process “construction / opening test”, log information indicating “communication start” or “communication success” is stored in the business terminal device 16. The In the example illustrated in FIG. 13, “communication start” for the project “XXX”, “communication success” for the project “XXX”, and the like are performed as business events related to the business process “construction / opening test”. Log information is stored in the business terminal device 16. The log information is collected as business event information by the business event collection unit 64 of the business monitoring server 10 and stored in the business event management unit 24.

  The log information regarding the business process “construction / opening test” is, for example, standard data, and each log information (each business event information) includes a case ID as case identification information. Therefore, by referring to the log information, the linked event is specified, the business event and the job can be automatically linked, and the linked status of each business event is “linked”. In the business event management unit 24, the case association state information of each business event is updated, and the association state is already associated.

  The business event “communication start” is a business event that corresponds to the “start” of the business process “construction / opening test” and changes the state of the business process “construction / opening test”. Therefore, when the business event information (log information) indicating the business event “communication start” for the case “XXX” is collected, the case management unit 30 updates the state of the case “XXX”. That is, the status of the business process “construction / opening test” in the case “XXX” is updated to “start”.

  The business event “successful communication” is a business event corresponding to the “end” of the business process “construction / opening test” and changing the state of the business process “construction / opening test”. Therefore, when the business event information (log information) indicating the business event “communication success” for the case “XXX” is collected, the case management unit 30 updates the state of the case “XXX”. That is, the status of the work process “construction / opening test” in the case “XXX” is updated to “finished”.

  Here, paying attention to the case “YYY”, the business process is finished up to “customer information registration”, and the next business process is “device arrangement”. The business event related to the business process “device arrangement” is transmission / reception of an electronic mail. The resource type of the electronic mail is the mail server 14 (mail box 50). Since the resource type of the e-mail data (unlinked business event information) indicated by reference numeral 94 is the mail server 14, the resource type is the resource of the business event related to the next business process “device arrangement” in the case “YYY”. Matches the type. Therefore, when “match resource type” is selected as the filtering condition, the case “YYY” is preferentially used as a candidate for the case to which the e-mail data (unlinked business event information) indicated by reference numeral 94 is linked. Searched. This search process is performed by the business process search unit 76 described above.

  Further, by adding a narrowing condition, it becomes possible to extract more accurate cases. For example, when “Responsible Person Match” is specified as the filtering condition, and the name of the person in charge is described in the body or title of the e-mail, the case that includes the same person in charge as the name of the person in charge is Search with priority.

  When a search instruction for an unlinked business event is given in the administrator terminal device 18, an unlinked business event is searched, and a list of unlinked business events is displayed on the administrator terminal device 18. When an unlinked business event is specified from the list by an administrator, etc., and a narrowing condition is set, search for candidate cases that are linked to the specified unlinked business event according to the filtering condition Is done. This search is performed by the business process search unit 76. Information indicating the search result is transmitted to and displayed on the manager terminal device 18. For example, a list of candidate candidates for association is displayed.

  FIG. 14 shows a list of search results (candidates for linking destinations). In the search result, for each case, the PID (case ID) of the case, information indicating the name of the business flow applied to the case, information indicating the state of the case, and candidate business events that can occur next The information and the information indicating the matching condition in the filtering condition are associated with each other. The matter status is the current matter status, that is, the status of the business process currently being executed (for example, being executed). For example, the business process to be executed in the case “XXX” is “customer information registration”, and the state is “finished”. That is, in the case “XXX”, the process up to the business process “customer information registration” is completed. The case “XXX” will be explained. Since the current business process is “customer information registration”, the next business process is “equipment arrangement”, and the next business event that can occur is “start equipment arrangement”. It is. The matching condition corresponds to an example of the matching determination result, is a condition included in the narrowing-down condition, and is a condition that matches between the unlinked business event and the matter. For example, in the case “XXX”, the person-in-charge name and the resource type match with the unlinked business event information to be linked. That is, information indicating the name of the person in charge is included in the unlinked business event information to be linked, and the name of the person in charge is the same as the name of the person in charge of the case “XXX”. Further, the resource type of the business event information related to the business event that can occur next in the case “XXX” is the same as the resource type of the unlinked business event information to be linked.

  The case “XXX” will be described in more detail as an example. Since the business event candidate is “start device arrangement”, the resource type is the mail server 14. If the resource type of the unlinked business event to be linked is the mail server 14, these resource types match. Further, the name of the person in charge of the case “XXX”, that is, the information indicating the name of the person in charge included in the case information of the case “XXX” indicates the name of the person in charge included in the unlinked business event information to be linked. If the information matches, the names of the persons in charge match. In the example shown in FIG. 14, the case “XXX” and the unlinked business event have the same person name and the same resource type.

  Next, an example of a linking screen will be described with reference to FIG. The association screen 96 is a screen that is displayed on the manager terminal device 18 when manually associating a business event with an item, and displays a list of the search results (association candidate candidates). It is a screen including. On the association screen 96, search conditions and search results are displayed. The search condition is an unlinked business event as a condition for searching for a candidate for a linked destination case, and is an unlinked business event to be linked. For example, an unlinked business event to be linked is selected from the list of unlinked business events by an administrator or the like, and detailed information on the unlinked business event to be linked is displayed. For example, as detailed information, EID (event ID), business event occurrence date and time, resource type, service name, application name, and the like are displayed. In addition, the contents of the unlinked business event are displayed. Here, the unlinked business event information is electronic mail data, and the contents (subject name and text) of the electronic mail are displayed.

  The search result is a candidate for the linked item. As a result of the search, a list of matters being executed is displayed. As a search result, a case ID, a business flow name, a case state, a business event candidate, a matching condition as a matching determination result, and the like are displayed. The unlinked business event with the event ID “003” and the case with the case ID “1234567” will be described. The service name, the resource type, and the person in charge match with each other. That is, the service name described in the text or subject of the electronic mail that is unlinked business event information matches the service name of the matter. Further, the resource type of the e-mail, which is unlinked business event information, matches the resource type of the next business event in the matter. Further, the name of the person in charge described in the text or subject of the e-mail that is unlinked business event information matches the name of the person in charge of the matter.

  Items with a larger number of matching conditions are displayed with priority over items with a smaller number of matching conditions. For example, a case with a larger number of matching conditions is displayed higher than a case with a smaller number of matching conditions.

  The administrator or the like uses the manager terminal device 18 to specify a case to which the unlinked business event is linked from the list of cases (search result). A linking button 98 is displayed on the linking screen 96. When the linked item is specified by the administrator or the like and the link button 98 is pressed by the administrator or the like, the unlinked business event and the item are linked. For example, as indicated by reference numeral 100, when the case with the case ID “1234567” is designated as the connection destination and the link button 98 is pressed, the case with the case ID “1234567” and the event ID “003” are displayed. Business event ". In the business event management unit 24, the case association state for the business event having the event ID “003” is updated to “correlated”. In addition, the state of the case with the case ID “1234567” is updated, and the state of the case, that is, the state of the business process is changed to the next state. This update is performed by the case update unit 78.

  As described above, according to this embodiment, an unlinked business event is notified to an administrator or the like, so that the business flow can be appropriately monitored. For example, even when atypical data is used as business event information, such as e-mail, the business flow can be appropriately monitored.

  In addition, according to the narrowing-down conditions, candidates for the cases to which the unlinked business event is linked are searched. For example, even if atypical data is used as business event information, candidates for a case to which an unlinked business event is linked are searched. In addition, by displaying preferentially the cases that meet the narrowing-down conditions, it becomes easier for the administrator or the like to find the case of the linked destination when manually associating the unlinked business event with the item. Therefore, manual tying work is prepared, and the work efficiency is improved.

  In addition, after the list of all cases is displayed on the association screen 96, the cases that meet the narrowing conditions may be preferentially displayed, or the list of all cases may not be displayed and included in the narrowing conditions. Only cases that meet at least one condition may be displayed. In addition, a list of all cases may be displayed, and cases where the number of matches in the filtering condition is greater than or equal to a preset number may be preferentially displayed, and each case may be displayed according to the priority according to the number of matches. May be displayed. As another example, the list of all cases may not be displayed, and only cases where the number of matches of the filtering conditions is equal to or more than a preset number may be displayed.

  The business monitoring server 10 is realized by cooperation of hardware resources and software as an example. Specifically, the business monitoring server 10 includes one or more processors such as a CPU (not shown). The processor reads and executes a program stored in a storage device (not shown), thereby realizing the functions of the respective units of the business monitoring server 10. The program is stored in the storage device via a recording medium such as a CD or DVD, or via a communication path such as a network. As another example, each unit of the task monitoring server 10 may be realized by hardware resources such as one or a plurality of processors and electronic circuits. In the realization, a device such as a memory may be used. As another example, each unit of the business monitoring server 10 may be realized by a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or the like.

  10 business monitoring server, 12 business server, 14 mail server, 16 business terminal device, 18 administrator terminal device, 20 communication unit, 22 management DB (database), 24 business event management unit, 26 filter definition management unit, 28 Business flow definition management unit, 30 case management unit, 32 narrowing condition management unit, 34 automatic association unit, 36 manual association unit, 64 business event collection unit, 66 business event determination unit, 68, 78 case update unit, 70 notification Department, 72 Business event search part, 74 Case search part, 76 Business process search part.

Claims (8)

Storage means for storing business flow definition information defining a processing order of a plurality of different business processes for each case;
An acquisition means for acquiring business event information related to a business event that has occurred in relation to a business process, wherein the acquisition means acquires business event information related to a business event that changes a state of a business process to be executed in the matter;
A linking means for linking business event information to a matter corresponding to a business event,
An output means for outputting matter candidate information indicating a candidate for a matter to be associated with unlinked business event information not linked to a matter in the business event information group;
A business monitoring device. In the work monitoring apparatus according to claim 1,
In the case where the case identification information for identifying the case is included in the business event information, the linking means links the business event information to the case indicated by the case identification information, and in the case indicated by the case identification information Transition the state of the business process to be executed,
The output means outputs the item candidate information indicating candidates for the cases to which the unlinked business event information is linked, with the business event information not including the case identification information as unlinked business event information;
A business monitoring device characterized by that. In the work monitoring apparatus according to claim 2,
The output means includes a current status of business processes to be executed in each case, a context of a plurality of business processes defined in each business flow definition information, and business processes corresponding to unlinked business event information. , Based on, including an extraction means for extracting candidate cases of unlinked business event information linked to,
A business monitoring device characterized by that. In the work monitoring apparatus according to claim 3,
The extraction unit specifies, for each item, a type of acquisition source of business event information related to a business event that may occur next based on the business flow definition information, and the type of the specified acquisition source is an unlinked business Extract the case that is the same as the type of event information acquisition source as a priority candidate,
A business monitoring device characterized by that. In the work monitoring apparatus according to any one of claims 1 to 4,
The output means further outputs information indicating a match determination result between the information obtained from the unlinked business event information and the information obtained from the business flow definition information in accordance with a preset narrowing condition.
A business monitoring device characterized by that. In the work monitoring apparatus according to any one of claims 1 to 5,
Business event information is atypical data.
A business monitoring device characterized by that. In the work monitoring apparatus according to claim 6,
The business event information is operation history information related to business processing, e-mail data related to business processing, or log information related to business processing.
A business monitoring device characterized by that. Computer
Management means for managing business flow definition information that defines the processing order of multiple different business processes for each matter
An acquisition means for acquiring business event information related to a business event that has occurred in relation to a business process, wherein the acquisition means acquires business event information related to a business event that causes a transition of the business process to be executed in the matter,
A linking method for linking business event information to a matter corresponding to a business event,
An output means for outputting matter candidate information indicating a candidate for a matter to be associated with unlinked business event information not linked to a matter in the business event information group,
Program to function as.

Images