JP2017201562A - Event support device and event support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an event support device and an event support method for efficiently and appropriately managing an event.SOLUTION: A control unit 21 of an event support system 20 performs integrated processing of approval working flow (WF) and performs approval WF working processing if event registration is detected. Then, if an applied event is approved, the control unit 21 notifies each service management system 10 of approval. In this case, each service management system 10 performs response processing corresponding to notification. In addition, if the event support system 20 detects content change about an approved event, the event support system checks whether control change is required or not, and performs the integrated processing of the approval WF if the control change is required. On the other hand, if the control change is not required, the event support system 20 performs notification processing of change. In addition, the event support system 20 having obtained the notification of state change from each service management system 10 performs the response processing corresponding to the notification if necessary.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an event support apparatus and an event support method for supporting event execution.

  Approval work is performed based on the approval workflow for accurate control management in corporate activities. An application management system for supporting circulation of drafting documents that require approval based on such an approval workflow has been studied (for example, see Patent Document 1). In the application management system described in this document, a folder unit folder for each department is provided in a file server, and an application folder, a circulation folder, and a final approval folder are provided therein. The control unit of the application management server manages the workflow using these folders.

  In addition, a workflow management system that realizes a workflow operation linked to a schedule has been studied (for example, see Patent Document 2). The workflow management system described in this document includes a workflow server and a schedule server. The workflow server has a workflow route table that is information on a person in charge of the workflow, and the schedule server has a schedule management table that is information on the schedule of the person in charge. The workflow server calculates the shortest workflow route, which is the shortest workflow route, by selecting the person in charge having the free time at the earliest date among the persons in charge stored in the person in charge information from the schedule management table. .

JP 2012-168721 A (first page, FIG. 1) Japanese Patent Laying-Open No. 2011-191964 (first page, FIG. 1)

  As described above, in a corporate activity, it is necessary to perform an approval operation using an appropriate approval workflow according to the situation. However, corporate activities consist of a wide variety of events, and many procedures and resources (facility, information, etc.) are involved in the implementation of a single event. Approval workflow needs to be applied.

  Further, in a corporation, various resources are managed by various service management systems. For example, entry / exit to / from a corporate facility is managed by a facility management system. Information used in a corporation (for example, important information such as confidential information) is managed by an information management system. In addition, the transportation cost required for the travel of the officer / employee for the event is managed by a system for adjusting the transportation cost. In addition, when taking out corporate assets such as PCs, they are managed by the asset management system. In this way, when multiple service management systems are involved in one event, if the procedures were performed in each service management system, it would be burdensome and appropriate management due to forgotten procedures, etc. May not be possible.

In addition, the contents and participants of the event may be changed. Even in such a case, each service management system is required to respond appropriately to changes in terms of control.
The present invention has been made to solve the above-mentioned problems, and provides an event support system and an event support method for managing events efficiently and accurately.

  The event support apparatus for solving the above problems is a control connected to a first management system in which event information or ToDo information is recorded, and a plurality of service management systems that execute various processes corresponding to managed events. A part. And the said control part specified the management object event which should be managed based on the participant in the event in the event information recorded on the said 1st management system, or the operator in ToDo information, and respond | corresponded to the said management object event In order to execute various types of processing, the service management system is notified based on the management target event, and the service management system is responsible for the management target event related to the event participant or the worker. Obtaining status change information, identifying the status of the event participant or the worker according to the status change information, and determining the status of the managed event determined based on the status change information and the participant or Management following the managed event that acquired the status change information according to the state of the worker To execute the various processes corresponding to the elephant event. Thereby, based on event information, an event support apparatus and each service management system can cooperate and can perform the various processes for implementing an event.

  In the event support apparatus, it is preferable that when the control unit detects a change in the status of the managed event, the service management system is notified of the change in the managed event. Thereby, it is possible to accurately cope with a change in the situation of the event.

  In the event support apparatus, the control unit acquires status change information related to the managed event from each service management system, and determines the status of the managed event based on the status change information . As a result, it is possible to acquire a change in status from each service management system and take action according to this change.

  -In the said event assistance apparatus, it is preferable that the said control part specifies the event attribute of the said management object event, and judges the necessity of the notification to each said service management system based on the said event attribute. Thus, appropriate notification can be performed according to the event attribute.

  An event support apparatus for solving the above problem is for specifying a first management system in which event information or ToDo information is recorded, a control unit connected to the first management system, and an authorized person related to the approval. An authorized person identification part is provided. Further, an approval route management unit that determines an approval route according to the event attribute is provided. And the said control part acquires the approval path | route from the said approval path | route management part based on the event attribute of the management object event about the event information registered in the said 1st management system, or ToDo information, The said some specified In the approval route, using the authorized person identification unit, the authorized person related to the approval according to the event attribute is identified, the common execution authorized person is identified, and the common execution authorized person is not in violation of the approval rule. If it can be set, an approval route that integrates the execution authority is generated. Thereby, an approval workflow for approving this event can be determined according to the event attributes such as the event type.

  In the event support apparatus, it is preferable that the control unit specifies an authorized person related to the approval based on an attribute of a participant of the management target event.

  In the event support apparatus, the control management unit further includes a control storage unit that records individual controls for control events that require control, and the control unit requires control according to the event attributes. Preferably, a control event is specified, and the control management unit determines an approval route according to individual control for the control event. As a result, it is possible to make necessary approvals in the event implementation.

  The event support apparatus further includes an authorized person specifying unit for specifying an authorized person related to the approval, and the control unit determines an authorized person related to the approval according to the event attribute in the authorized person specifying unit. Identify. Thereby, the authorized person concerning approval can be specified.

  In the event support apparatus, the control unit identifies an authorized person related to the approval based on the attribute of the participant in the management target event or the attribute of the worker in the ToDo information. Thereby, the approval workflow according to the attribute of the participant can be determined.

  In the event support apparatus, the control storage unit records an order relationship for individual controls, and the control unit stores the order relationship of each individual control for a plurality of individual controls according to the event attribute. It is preferable to identify and generate an approval route based on the order relation. Thereby, even when approval by a plurality of procedures is required, an integrated approval workflow without waste can be generated.

  -In the said event assistance apparatus, it is preferable to record the individual control which the said authorized person should bear about the authorized person concerning the approval on the said approval path | route in the said control memory | storage part. Thereby, it is possible to accurately perform the work related to the approval with reference to the control storage unit.

  -In the said event assistance apparatus, it is preferable to confirm the presence or absence of prior approval about the said management object event, and to respond as having approved about the said individual control, when prior approval is already registered. Thereby, efficient approval work by prior approval can be performed.

  -In the said event assistance apparatus, it is preferable that the said control part performs the approval request with respect to the authorized person which concerns on the said approval path | route, and manages the approval condition in the said authorized person. Thereby, the approval workflow can be executed.

  In the event support apparatus, it is preferable that the control unit is further connected to a workflow management system, and the control unit shares an approval route and an approval status with the workflow management system. Thereby, the approval workflow can be executed in the workflow management system.

  -In the said event assistance apparatus, it is preferable that the said control part specifies the recommended participant in the said management object event, and outputs a warning when the recommended participant is not registered in the said management object event. Thereby, participation of an appropriate participant can be encouraged.

  According to the present invention, events can be managed efficiently and accurately.

Explanatory drawing of the event assistance system of this embodiment. It is explanatory drawing of the data used in this embodiment, (a) is a party management system, (b) is a work storage part, (c) is an event storage part, (d) is recorded in a service allocation table storage part. Explanatory drawing of data. It is explanatory drawing of the data used in this embodiment, Comprising: (a) is the data recorded on procedure DB, (b) is explanatory drawing of a control table. Explanatory drawing of the outline | summary of the process of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the state transition of this embodiment. Explanatory drawing of the control table of this embodiment. Explanatory drawing of the control table of this embodiment. Explanatory drawing of the control table of this embodiment. Explanatory drawing of the control table of this embodiment. It is explanatory drawing of the data used by this embodiment, (a) is a business management record, (b) is a service allocation management record, (c) is an event, (d) is a person base individual control list, (e) is Explanatory drawing of service-based approval WF. It is explanatory drawing of the data used by this embodiment, Comprising: (a) Person-based approval WF [service → person replacement version], (b) Person-based approval WF [optimized version], (c) Person-based approval Explanatory drawing of WF [actual solution version]. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of other embodiment.

  Hereinafter, an embodiment of an event support apparatus embodying the present invention will be described with reference to FIGS. In the present embodiment, it is assumed that officers and employees in a corporation perform processing at the time of event registration, implementation permission, implementation, and post-implementation. In this case, the execution of the approval process and management process necessary for the implementation of this event is supported.

  In the present embodiment, as shown in FIG. 1, a plurality of service management systems 10, an event support system 20, a party management system 22, a business storage unit 23, and an event storage unit connected via a network (not shown). 24, the procedure DB 30, the schedule management system 50, and the WF system 55 are used. In the present embodiment, an event (application event) applied in the schedule management system 50 is approved by the approval workflow in the WF system 55 and validated to become an approval event. In the event support system 20, the application event and the approval event are handled as management target events.

  The service management system 10 is a computer system that manages services for each officer. In this embodiment, as the service management system 10, a facility management system 10a for managing entry / exit to a corporate building or room, an information management system 10b for managing materials used in a meeting, etc., traffic required for the movement of officers and employees A transportation expense management system 10c for managing the expense settlement is used.

The schedule management system 50 is a computer system that manages events applied by officers and employees (application events) and ToDo for each officer and employee.
The application event is recorded when a new event is registered. As an application event, event code, event name, applicant, date / time, location, event type, business, data, and data regarding participants are recorded.

In the event code data area, data relating to an identifier for specifying each application event is recorded.
Data related to the name of the event is recorded in the event name data area.
In the applicant data area, data relating to an identifier (officer / employee code) for identifying the officer / employee who applied for the application event is recorded.

  In the date / time data area and the place data area, data related to the date and time when the application event is performed and an identifier (location code) for specifying the place where the application event is performed are recorded.

In the event type data area, data relating to an identifier for specifying the type of the application event is recorded.
In the business data area, data relating to an identifier for specifying the business to which the application event belongs is recorded.

In the material data area, data related to the material used in this application event is recorded.
In the participant data area, data relating to an identifier for identifying a participant who participates in the application event is recorded. In this data area, officer / employee codes of party information are recorded.

  In addition, ToDo records work that each officer / employee must perform for each officer / employee.

The schedule management system 50 is connected to a scheduler (schedule management application) stored in the officer / employee terminal.
This officer / employee terminal is a computer terminal used by officers / employees to apply for an event, to control the approval of the event, and to participate in the event. The officer / employee terminal includes a display unit (such as a display) and an input unit (such as a keyboard and a pointing device). In this embodiment, an officer / employee who applies for an event uses the scheduler of the officer / employee terminal to access the schedule management system 50 and register an application event. In addition, the administrator uses the officer / employee terminal to access the WF system 55 and perform confirmation related to the approval of the application event.

  The WF system 55 is a computer system that performs processing to circulate various applications to the officer / employee terminal of the authorized person related to the approval based on the approval workflow.

The event support system 20 is a computer system that manages cooperation with the following systems and the like.
・ Cooperation with schedule management system 50 via application event ・ Cooperation with WF system 55 via approval workflow responsible for approval control related to application event implementation ・ Service via status of event (approval event) approved by approval workflow Cooperation with management system 10

  The event support system 20 includes a control unit 21. The control unit 21 includes control means (CPU, RAM, ROM, etc.), such as processing (to be described later) such as a service cooperation stage related to status notification and status change, related control extraction, approval WF synthesis, and related control extraction stage related to execution of approval WF. Each processing). By executing the event support program for that purpose, the control unit 21 functions as a service cooperation unit 21A and a WF cooperation unit 21B as shown in FIG. The service cooperation unit 21 </ b> A executes processing that cooperates with the service management system 10. The WF cooperation unit 21 </ b> B executes processing that cooperates with the schedule management system 50 and the WF system 55.

The service cooperation unit 21A includes a state notification unit 211 and a state change unit 212.
The status notification unit 211 executes notification processing (broadcast) for each service management system 10 in response to the status (approval or change) of the approval event.

  The state changing unit 212 executes processing for changing the state of each approval event based on the notification about the status change acquired from each service management system 10. This change process is performed using a state change dictionary held by the state change unit 212. In this state change dictionary, whether or not to change the status of the approval event according to the status change notified from each service management system 10 and the response to be performed by the event support system 20 when the status change is performed are recorded. ing.

The WF cooperation unit 21B includes a related control extraction unit 213, an approval WF synthesis unit 214, and an approval WF execution unit 215.
The related control extraction unit 213 detects an application of an approval event or a change in content, and executes a process of extracting a management event related to the approval event or a control event related to the service management system 10.

  The approval WF synthesizing unit 214 functions as a control management unit and an authorized person specifying unit, and based on the previous control event, synthesizing an approval workflow (approval WF) related to a necessary procedure group according to the event content (event attribute) Execute. For this purpose, the approval WF synthesizing unit 214 also executes a process of specifically expanding the service name related to the procedure on the previous approval workflow and the job title on the line to the officer / employee. Further, the approval WF synthesis unit 214 holds an approval rule for determining an approval workflow. In this approval rule, rules for determining an authorized person for approval, such as prohibition of self-approval for approving one's own application, are set.

  The approval WF execution unit 215 executes an approval workflow process related to application event registration and approval event change via the WF system 55.

The event support system 20 is connected to a party management system 22 as an organization information storage unit, a business storage unit 23, and an event storage unit 24.
As shown in FIG. 2A, the party management system 22 is realized by a personnel system or a trading company management system. In the personnel system of the party management system 22, party information 220 relating to the organizational structure of a corporation and officers and employees belonging to each line is recorded. In the party information 220, data relating to the officer / employee code, name, work place, affiliation, and post is recorded.

In the officer / employee code data area, data relating to an identifier for identifying each officer / employee is recorded.
In the name data area, data related to the names of officers and employees and outsiders are recorded.
In the work place data area, data for specifying the work place of this officer / employee or outsider is recorded.

In the affiliation data area, data relating to an identifier for specifying the organization (department) to which this officer / employee or outsider belongs is recorded.
In the post data area, data relating to an identifier for specifying the post of the officer / employee or outsider is recorded.

  In the trading company management system in the party management system 22, information on officers and employees (outsiders) of other corporations (external) related to the event is managed. Information (corporation code) for specifying a corporation is added and recorded in the party information 220 of this trading company management system.

  As shown in FIG. 2B, a business management record 230 relating to business related parties is recorded in the business storage unit 23. This business management record 230 is recorded when a business performed by each officer / employee is registered. In the business management record 230, data related to a business code, a manager, a person in charge, a collaborator, and a related person are recorded.

Data relating to an identifier for identifying each business is recorded in the business code data area.
Data relating to an identifier (officer / employee code) for identifying the officer / employee who manages this work is recorded in the manager data area.

In the person-in-charge data area, data relating to an identifier (officer / employee code) for identifying the officer / employee who is in charge of this work is recorded.
In the collaborator data area, data relating to identifiers (corporation codes and officer / employee codes on a trading company management system) for identifying other corporations that cooperate with this business and officers / employees of the other corporations is recorded.
In the related party data area, data related to identifiers (department codes and officer / employee codes) for identifying other departments related to the business and officers / employees of the other departments are recorded.

  As shown in FIG. 2C, an event management record 240 for managing the application event acquired from the schedule management system 50 as a management target event is recorded in the event storage unit 24. The event management record 240 is recorded when event information about a schedule registered by the officer / employee is acquired. In the event management record 240, data relating to an event code and status is recorded.

In the event code data area, data relating to an identifier for identifying each application event registered in the schedule management system 50 is recorded.
Data relating to the status (state) of the management target event is recorded in the status data area. Here, data relating to the management target event and the state of each participant is recorded.

  Further, as shown in FIG. 1, the event support system 20 is connected to a procedure DB 30 as a control storage unit. The procedure DB 30 includes a service assignment table storage unit 32 and a policy storage unit 33.

  As shown in FIG. 2D, the service assignment table storage unit 32 records a service assignment management record 320 for registering the officer / employee who bears the service defined in each procedure. In the service assignment management record 320, data on services, organizations, and persons in charge is recorded.

In the service data area, data relating to an identifier for specifying each service is recorded.
In the organization data area, data relating to an identifier for identifying the organization for which the person in charge of the service is responsible is recorded.
In the person-in-charge data area, data relating to an identifier for identifying the officer / employee who is in charge of this service is recorded.

  As shown in FIG. 3A, the policy storage unit 33 describes the “control event” indicating the business and management target, the “service” person responsible for the control of the “control event”, and the control content of the “control event”. The “control table CT” is registered.

In the present embodiment, as “control event”, business control for each event type and management control for each of various management procedures are recorded. The “control event” includes information for determining the necessity of the control event according to the event content.
This “service” person may be appointed by a suitable person individually, or may be defined by job title or business role.

  As shown in FIG. 3 (b), this “control table CT” includes “implementation license” that determines whether or not the event implementation is approved as an aspect to be controlled (control aspect), “implementation” during the event implementation, It is managed in three stages of “implementation results” related to the implementation of the event. Further, in each “control aspect”, specific “individual controls” are defined for six “control items” of completeness, reality, legitimacy, accuracy, authority, and timeliness. Each “service” assumes (executes) “individual control” according to its role.

  Comprehensiveness means that events are recorded without omissions and duplication, and is secured by registration of events to be executed. In this embodiment, it is a mechanism for controlling the service management system 10 related to the event, and the service management system 10 can be used on condition that the event exists. This necessarily guarantees completeness.

Existence means that an event exists on a specific date and is secured by evidence that it has been performed.
Legitimacy means that the implementation and content of the event is appropriate, and is secured by confirmation or instructions from the business administrator.

Accuracy means that information is accurately recorded and provided, and is secured by review or evidence.
Authority means that information is protected from being used by anyone other than a legitimate authorized person, and is mainly secured by a function of the system (for example, IT application control (ITAP)).

The time limit means that an effective period or an end period is determined in advance, and is secured by evidence of implementation (evidence).
Furthermore, in the “individual control”, a content column and an execution column are provided for each item.
In the content column, the specific content of the control is recorded.
In the execution column, the executor responsible for the “individual control” is recorded. For example, control (ITAP) using an IT application and control (re-examination, confirmation, approval, etc.) by a “service” person are recorded.

(Function of event support system 20)
Next, the outline of the entire processing in the event support system 20 and the service management system 10 will be described with reference to FIG.

  First, the control unit 21 of the event support system 20 detects an event application registered in the schedule management system 50 (F11). This process is realized by the related control extraction unit 213 of the WF cooperation unit 21B.

Next, the control unit 21 of the event support system 20 synthesizes the approval WF (F12). This process is realized by the approval WF composition unit 214 of the WF cooperation unit 21B.
Next, the control unit 21 of the event support system 20 operates the approval WF (F13). This process is realized by the approval WF execution unit 215 of the WF cooperation unit 21B.

When the approval workflow is approved, the control unit 21 of the event support system 20 notifies the service management system 10 of the approval (F14). This process is realized by the status notification unit 211 of the service cooperation unit 21A. Here, each participant is notified about the attendant. In addition, the control unit 21 of the event support system 20 notifies the attendance expression even when each participant related to the approved event detects the attendance expression in the schedule management system 50.
In this case, each service management system 10 performs a response according to the notification as necessary (F21).

  In addition, the control unit 21 of the event support system 20 detects a content change (including event deletion) in the schedule management system 50 (F15).

  In this case, the control unit 21 of the event support system 20 confirms whether or not there is a control change (F16). Here, when it is determined that there is a control change (when “control change is present” in F17), the control unit 21 of the event support system 20 performs the processing after the synthesis of the approval WF (F12) as described above. .

  On the other hand, when it is determined that there is no control change (in the case of “no control change” in F17), the control unit 21 of the event support system 20 notifies each service management system 10 of the change (F18).

The control unit 21 of the event support system 20 detects a change in the state of the event or the participant in the schedule management system 50 (F31). Then, the control unit 21 of the event support system 20 notifies each service management system 10 of a state change (F32). This process is realized by the state changing unit 212 of the service cooperation unit 21A.
In this case, each service management system 10 performs a response according to the notification as necessary (F41).

  When each service management system 10 senses a change in state, it notifies the event support system 20 of the change in state (F42).

  In this case, the control unit 21 of the event support system 20 performs a response corresponding to the notification (F33). In response to this, the control unit 21 of the event support system 20 detects the occurrence of a state change (F31).

(Process when event registration or content change is performed)
Next, the process in the outline of the process when the event registration or content change is performed will be described in detail with reference to FIG.

  First, the control unit 21 of the event support system 20 detects event registration in the schedule management system 50. This event registration includes data relating to the event code, applicant, date / time, place, event type, business, document, and participant.

  In this case, the control unit 21 of the event support system 20 executes an event application process (step S1-1). Specifically, the related control extraction unit 213 of the control unit 21 generates an event management record 240 and registers it in the event storage unit 24. This event management record 240 includes event code and data regarding status. Here, the application status is recorded in the status data area of the event management record 240.

  Next, the control unit 21 of the event support system 20 executes an approval WF composition process (step S1-2). Specifically, the related control extraction unit 213 of the control unit 21 extracts the “individual control” item related to the application event from the policy storage unit 33 of the procedure DB 30. Then, the approval WF synthesizing unit 214 executes an approval workflow generation process based on the extracted “individual control”. This process will be described later with reference to FIGS.

  Next, the control unit 21 of the event support system 20 executes an approval WF operation process (step S1-3). Specifically, the approval WF synthesis unit 214 of the control unit 21 instructs the approval WF execution unit 215 to execute the approval workflow. In this case, the approval WF execution unit 215 circulates the approval workflow in the WF system 55. When the WF system 55 approves the approval workflow, the approval result is recorded in the status data area of the event management record 240 of the event storage unit 24.

  If the approval workflow is approved, the control unit 21 of the event support system 20 executes an approval notification process (step S1-4). Specifically, the status notification unit 211 of the control unit 21 notifies the service management system 10 of event approval. This notification includes data related to the event content.

  In this case, each service management system 10 executes a response process according to the notification as necessary (step S1-5). Here, as will be described later, each service management system 10 executes a process corresponding to the notification acquired from the event support system 20.

  Furthermore, when the control unit 21 of the event support system 20 detects the participation expression (attendance expression, absence expression) of each participant related to the approved event in the schedule management system 50, the control unit 21 of the event support system 20 Event registration processing is executed (step S2-1). Specifically, the related control extraction unit 213 of the control unit 21 adds or deletes participants in the participant data area of the event management record 240 registered in the event storage unit 24. Then, the participation expression of each participant is recorded in the status data area of the event management record 240.

  Next, the control unit 21 of the event support system 20 executes a participation announcement notification process (step S2-2). Specifically, the status notification unit 211 of the control unit 21 notifies each service management system 10 of the participation expression of the participant in this approval event. This notification also includes data related to the event content. Also in this case, each service management system 10 executes a response process according to the notification as necessary (step S2-3).

  When the control unit 21 of the event support system 20 detects a content change (including deletion of an approval event) in the schedule management system 50, the control unit 21 of the event support system 20 performs a content change registration process. Execute (Step S3-1). Specifically, the related control extraction unit 213 of the control unit 21 corrects the content of the event management record 240 registered in the event storage unit 24.

  Next, the control unit 21 of the event support system 20 executes a process for confirming whether or not there is a control change (step S3-2). Specifically, the related control extraction unit 213 of the control unit 21 extracts “individual control” related to the approval event from the policy storage unit 33 of the procedure DB 30. Then, the related control extraction unit 213 determines that there is a control change when a difference occurs in the “individual control” due to the content change.

  Here, when it is determined that there is a control change (in the case of “YES” in step S3-3), the control unit 21 of the event support system 20 is similar to steps S1-2 to S1-4 as described above. The approval WF composition processing (step S3-4), the approval WF operation processing (step S3-5), and the approval notification processing (step S3-6) are executed. Also in this case, each service management system 10 executes a response process according to the notification as necessary (step S3-7).

  On the other hand, when it is determined that there is no control change (in the case of “NO” in step S3-3), the control unit 21 of the event support system 20 executes a change notification process (step S3-8). Specifically, the state notification unit 211 of the control unit 21 notifies the service management system 10 that the content of the approval event has been changed. This notification also includes data related to the event content. Also in this case, each service management system 10 executes a response process according to the notification as necessary (step S3-9).

(Processing when a change in the status of an event or participant is detected)
Next, with reference to FIG. 6, processing when the event support system 20 detects occurrence of a state change for an event or a participant will be described.

  In this case, the control unit 21 of the event support system 20 performs a state change detection process in the schedule management system 50 (step S4-1). Specifically, the state change unit 212 of the control unit 21 changes the status recorded in the event management record 240 of the event storage unit 24 according to the contents of the state change.

  In this case, the control unit 21 of the event support system 20 executes a state change notification process (step S4-2). Specifically, the state notification unit 211 of the control unit 21 notifies the service management system 10 that a state change has occurred. This notification also includes data related to the event content. In this case, each service management system 10 executes a response process according to the notification as necessary (step S4-3).

  Further, when each service management system 10 senses a state change, it executes a status change notification process (step S5-1). Specifically, the service management system 10 detects a change in the status of the service provided in association with the approval event. When detecting a change in the status of the service associated with the event code, the service management system 10 notifies the event support system 20 that a state change has occurred. This notification includes data related to the event code.

  In this case, the control unit 21 of the event support system 20 executes a state change process as necessary (step S5-2). Specifically, the state change unit 212 of the control unit 21 acquires a notification from the service management system 10. Then, the state change unit 212 determines whether or not it is necessary to change the state of the approval event using the state change dictionary. When the state is changed, the state change unit 212 extracts the event management record 240 in which the event code included in the notification is recorded from the event storage unit 24. Then, the state changing unit 212 changes the status recorded in the event management record 240 according to the contents of the state change. In this case, the event support system 20 performs a state change notification process on the service management system 10 (step S5-3). Also in this case, each service management system 10 executes a response process according to the notification as necessary (step S5-4).

(Related control table creation process)
Next, the related control table creation process will be described with reference to FIG.
Here, the control unit 21 of the event support system 20 executes a business control extraction process (step S6-1). Specifically, the related control extraction unit 213 of the control unit 21 specifies the event type in the event information acquired from the schedule management system 50. Then, the related control extraction unit 213 specifies a control table CT (control table CT for business control) associated with the control event corresponding to the event type in the policy storage unit 33. Next, the related control extraction unit 213 identifies the item recorded in the “permission” in the business control control table CT as the business individual control.

  Next, the control unit 21 of the event support system 20 executes management control extraction processing (step S6-2). Specifically, the related control extraction unit 213 of the control unit 21 specifies the event content in the event information acquired from the schedule management system 50. Next, the related control extraction unit 213 specifies the control table CT (control table CT of management control) associated with the control event corresponding to the management type included in the event content in the policy storage unit 33. Specifically, the related control extraction unit 213 specifies a control table CT in which the condition of the control item “coverage” of the control phase “permission” satisfies the event content. However, if anything other than “completeness” is blank, it is excluded.

(Authorization workflow generation process)
Next, an approval workflow generation process using this related control table will be described with reference to FIG.

  Here, first, the control unit 21 of the event support system 20 executes an individual control extraction process to be performed manually (step S7-1). Specifically, the approval WF synthesizing unit 214 of the control unit 21 determines that the control aspect of the control table CT (control table CT of business control and management control) specified by the related control extraction unit 213 is “permission”. Extract individual controls for which execution of individual controls is a service.

  Next, the control unit 21 of the event support system 20 executes the order relation setting process of the extracted individual controls (step S7-2). Specifically, the approval WF synthesizing unit 214 of the control unit 21 specifies the order relationship of the extracted control table CT having the individual control based on the condition in which the control items are recorded in the content area of “completeness”. To do. Similarly, the approval WF composition unit 214 specifies the order relation of individual controls in the control table CT based on the conditions recorded in the content area of the individual controls belonging to the same control table CT.

  Next, the control unit 21 of the event support system 20 executes merge processing of individual controls in the same order (step S7-3). Specifically, the approval WF synthesizing unit 214 of the control unit 21 creates a service-based approval workflow by integrating individual controls in which execution areas in the same order have the same service.

  Next, the control unit 21 of the event support system 20 executes a service-to-person deployment process based on the organization and business (step S7-4). Specifically, the approval WF synthesis unit 214 of the control unit 21 refers to each record recorded in the party management system 22, the business storage unit 23, and the service allocation table storage unit 32, and each individual service-based approval workflow. The execution authority (the authority who is responsible for determining whether individual controls are acceptable or not) is specified to execute the contents of the controls. Here, when a plurality of officers / employees have execution authority, all officers / employees are specified as execution authority.

  Next, the control unit 21 of the event support system 20 executes an approval WF optimization process (step S7-5). Specifically, the approval WF synthesizing unit 214 of the control unit 21 specifies a common execution authority in each individual control including upper and lower order relationships. If the common execution authority can be set without violating the approval rule, the approval WF synthesis unit 214 integrates the approval workflow. As a result, a person-based approval workflow is created by integrating the execution authorized persons in the service-based approval workflow.

(Specific example of state transition)
First, with reference to FIG. 9, event transitions for application and implementation of events and participants of approval events will be described.

  When it is detected that a new event is registered in the schedule management system 50, the control unit 21 of the event support system 20 recognizes the event as an application event and sets the application state (ST11). Then, an approval workflow for the application event is generated and executed. If you change the contents of the application event while in the application state, it remains in the application state. Similarly, when the approval workflow is activated and the application is returned to the applicant by the authorized person, the application state remains unchanged.

In addition, when the application is canceled in the application state, the application is in a canceled state (ST12).
When the application is approved, the approval state (ST13) is entered. When a change occurs in the approval event contents in this approval state, the state changes depending on whether or not the control object has been changed. If the control does not change, the approval state (ST13) is maintained. On the other hand, when a change occurs in the control target, the process returns to the application state (ST11), and an approval workflow for requesting the change is generated and executed. It is also possible to cancel an approval event that has already been approved. In this case, it will be in a canceled state as with the withdrawal in the application state.

And when an approval event is started, it will be in an implementation state (ST14). Further, when the approval event ends, the end state (ST15) is entered.
If a participant for the approval event is set, each participant is in a participation request state (ST21). Here, when a participation expression is made in each participant, a state of absence or attendance is announced (ST22) according to the contents. Then, there are two states (ST23) of absence and attendance as an actual participation situation for the attendance expression. In the case of a participant who is scheduled to attend from the beginning, the participation request state (ST21) is changed to the participation state state (ST23). Regardless of whether there is an expression of participation or the contents of the participation expression, if you actually attend, the actual participation status will be attendance.

  Furthermore, each participant has the attribute of participation form (AT1) in parallel with the attendance expression state (ST22). Specifically, when the participant is an officer / employee or an outsider, there may or may not be movement depending on the participant's work location. In this embodiment, the entrance management may or may not have the entrance / room authority. Here, if there is a move depending on the work place of the participant, there is no entry authority and a new entry / entry setting is required. On the other hand, when there is no movement, the user has authority to enter the room, and no new entry / entry setting is required.

  When all participants who have attended in the participation state (ST22) and have attended in the participation state (ST23) have left, it is determined that the approval event has ended. For participation setters whose participation status (ST23) is not “attendance” at the end of the approval event, the participation status (ST23) becomes “absent” regardless of the participation request status, participation status, etc.

[Specific example of a meeting]
Next, a specific example of a conference will be described with reference to FIGS.
(Specific example of control table)
Next, a specific example of the control table used in the management of the conference in which the state transition described above occurs will be described with reference to FIGS.

FIG. 10 shows a control table CT1 for “business control: meeting (internal meeting, visit, visit)”. Here, “ITAP” means “IT application control”.
FIG. 11 shows a control table CT2 for “management control: information (use and take-out of event material)”.

FIG. 12 shows a control table CT3 for “management control: facility (entrance / room entry)”.
FIG. 13 shows a control table CT4 for “management control: movement (settlement of transportation expenses)”. In the control table CT4, individual controls after the event are registered.

(Specific examples of event management)
Next, event management processing when the above-described conference is performed will be described with reference to FIGS. 7, 8, and 14 to 19.

  Here, as shown in FIG. 14A, a case where a business management record 231 in which the parties related to the project Y (officers and employees A, B, C...) Are registered is recorded in the business storage unit 23. Suppose.

Further, as shown in FIG. 14B, a case where a service assignment management record 321 in which information managers (officers / employees A, Z...) Of related parts are registered is recorded in the service assignment table storage unit 32. Suppose.
Then, as shown in FIG. 14C, it is assumed that an event 500 is registered for the conference.

  First, as illustrated in FIG. 7, the control unit 21 of the event support system 20 executes a related control table creation process.

  Here, the control unit 21 of the event support system 20 executes a business control extraction process (step S6-1). Specifically, the related control extraction unit 213 of the control unit 21 controls the control table CT (business control table) in which the event type (internal meeting) of the event 500 is recorded as a control event in the policy storage unit 33 of the procedure DB 30. Specify the control table CT). Here, the control table CT1 for “conference” shown in FIG. 10 is specified.

  Next, the control unit 21 of the event support system 20 executes management control extraction processing (step S6-2). Specifically, the related control extraction unit 213 of the control unit 21 specifies a control table CT (control table CT of management control) that matches the event content of the event 500 as a control event. Here, the control table CT2 for “information” shown in FIG. 11 is specified.

Next, as illustrated in FIG. 8, the control unit 21 of the event support system 20 executes an approval workflow generation process.
First, the control unit 21 of the event support system 20 executes an individual control extraction process to be performed manually (step S7-1). Specifically, the approval WF composition unit 214 of the control unit 21 specifies an individual control that needs to be confirmed by an administrator or a service person in the related control table.

  As a result of this processing, a person-based individual control list 510 of individual controls to be performed manually as shown in FIG. 14D is generated. Here, it is shown that it is necessary for the business administrator to check the validity (problem of business) and authority (business authority) of the application event (conference). Further, when the validity and authority of the application event (conference) are confirmed, it indicates that the information manager needs to confirm the validity of information management.

  Further, the control unit 21 of the event support system 20 executes the extracted individual control order relation setting process (step S7-2). And the control part 21 of the event assistance system 20 performs the merge process of the individual control in the same order (step S7-3).

  With this process, a service-based approval workflow 520 shown in FIG. 14E is generated. That is, the business manager first performs the “confirmation legitimacy” and “conference authority” confirmation processing 521, and then the information manager performs the “information (management) legitimacy” confirmation processing 522.

  Next, the control unit 21 of the event support system 20 executes a service-to-person deployment process based on the organization and business (step S7-4). Specifically, the approval WF synthesizing unit 214 of the control unit 21 specifies the target project Y in the event information of FIG. 14C as a business administrator, and in the business management record 231 of FIG. The officer / employee A who is the leader of Project Y is identified. Further, as the information manager, the officer / employee (A, Z) is specified as the one-part information manager in the service assignment management record 321 of FIG. 14B.

  With this process, a person-based approval workflow 530 shown in FIG. 15A is generated. Here, the officer / employee A confirms the “validity of the meeting” and the “authority of the meeting”. Moreover, the officer / employee A or officer / employee Z confirms the “validity of information”. Thereby, an approval workflow in which the service is replaced with a person is generated.

  Next, the control unit 21 of the event support system 20 executes an approval WF optimization process (step S7-5). Specifically, the approval WF composition unit 214 of the control unit 21 specifies a common execution authority in each individual control. Here, individual controls are integrated for each execution authorized person who is assigned an approval workflow. Here, the officer / employee A has the authority to confirm the “validity of the meeting”, “authority of the meeting”, and “validity of information”.

  In this case, as shown in the optimized version approval workflow 540 (person-based approval WF (optimized version)) shown in FIG. 15B, the officer / employee A performs the “validity of meeting”, “authority of meeting”, and All of the “information validity” may be checked at once. Alternatively, the officer / employee A may confirm the “validity of the meeting” and the “authority of the meeting”, and the officer / employee Z may confirm the “validity of information”.

  Furthermore, when performing a confirmation operation on an actual WF system, it is more realistic to integrate authorized persons who have the same logical order. Specifically, as in the actual solution approval workflow 550 (person-based approval WF (actual solution version)) shown in FIG. “Validity of meeting” and “Authority of meeting” are indispensable, and “Validity of information” is optional. When the officer / employee A performs all confirmations, the approval workflow is terminated, and the application event is approved. On the other hand, when the officer / employee A has not confirmed the “validity of information”, the operation of confirming the “validity of information” by the officer / employee Z is essential.

(Cooperation with each service management system)
Next, cooperation between the event support system 20 and the service management system 10 will be described with reference to FIG. Here, the cooperation in the meeting mentioned above is demonstrated. In the present embodiment, cooperation between the event support system 20 and each service management system 10 of the facility management system 10a, the information management system 10b, and the transportation expense management system 10c is assumed. The processing in the facility management system 10a will be described later with reference to FIG. 17, the processing in the information management system 10b in FIG. 18, and the processing in the transportation cost management system 10c with reference to FIG.

First, when an event is applied (step S8-1), the event is not approved, and the event support system 20 and the service management system 10 are not linked.
Until the application event is approved and actually executed, operations related to the event contents are performed as follows.
・ Event approval (step S8-2)
・ Attendance statement about participants (step S8-3)
・ Attendance statement about participants (step S8-4)
-Document change for approval event (step S8-5)
-Change of location for approval event (step S8-6)
-Cancellation of approval event (step S8-7)

  The operations related to these event contents (steps S8-2 to S8-7) are notified to the service management system 10 from the service cooperation unit 21A of the event support system 20 (notifications F14 and F18 in FIG. 4), and service management is performed. In the system 10, a response is made according to the notification.

The movement related to the execution of the approval event is notified to the event support system 20 as a status change detected by the service management system 10 (steps S9-1 to S9-4).
For example, when the facility management system 10a detects the entry of the participant, the facility management system 10a notifies the event support system 20 of the entry of the participant in response to the notification F42 of FIG. 4 (step S9-1).

  When the information management system 10b detects the attendance of the participant, the information management system 10b notifies the attendance of the participant to the event support system 20 in response to the notification F42 of FIG. 4 (step S9- 2).

  In this case, the control unit 21 of the event support system 20 recognizes the start of the event (step S8-8) corresponding to step S5-2 (FIG. 6), and transitions the event to the implementation state (ST14 in FIG. 9). ). The control unit 21 of the event support system 20 notifies the service management system 10 that the event has changed to the implementation state (notification F32 in FIG. 4).

  When the information management system 10b detects the end of the event, the information management system 10b notifies the event support system 20 of the end of the event in response to the notification F42 of FIG. 4 (step S9-3).

  In this case, the control unit 21 of the event support system 20 recognizes the end of the event (step S8-9) corresponding to step S5-2 (FIG. 6), and transitions the event to the end state (ST15 in FIG. 9). ). The control unit 21 of the event support system 20 notifies the service management system 10 that the event has transitioned to the end state (notification F32 in FIG. 4).

When the facility management system 10a detects the participant's exit, the facility management system 10a notifies the event support system 20 of the exit of the participant in response to the notification F42 of FIG. 4 (step S9-4).
When the event end notification is received, the transportation cost management system 10c performs processing (generation, application, approval) of transportation expenses for event attendees (steps S9-5 to S9-7).

(Processing in each service management system)
Next, processing executed in each service management system 10 when the conference of the specific example described above is performed will be described with reference to FIGS.

(Admission / room management process)
Next, an entrance / room management process will be described with reference to FIG. This process is performed based on the notification from the event support system 20 shown in FIG. 16 (FIG. 4). Here, the “looping arrow” symbol means repetition. The “diamond” symbol means judgment. The facility management system 10a includes an entrance / entrance setting DB for managing entrance / entrance. In the admission / entry setting record of the admission / entry setting DB, data relating to the visitor code, base, time, and event are recorded.

In the visitor code data area, the officer / employee code recorded in the party management system 22 is recorded in order to identify the visitor.
In the base data area, data relating to an identifier for specifying a base visited by a visitor is recorded.

In the time data area, data related to the date and time when the visitor visits is recorded corresponding to the event holding time.
In the event data area, data relating to an identifier (event code) for specifying an approval event that is a visit purpose is recorded.

Hereinafter, information processing executed in the facility management system 10a will be described.
When an event approval notification is provided from the control unit 21 of the event support system 20 (step S8-2 in FIG. 16), the facility management system 10a enters an attendee who has attended the event (meeting). An entrance determination process is executed (step S10-1). Specifically, the facility management system 10a checks for each attendant who is present, whether the attendant has authority to enter and enter the event (conference) venue. Here, the facility management system 10a determines the presence / absence of entry authority (AT1) of the participation form of each participant claimant based on the result.

  If the attendant has no authority to enter or enter an event (conference) venue (hereinafter referred to as a “visitor”), the facility management system 10a executes entrance / entry setting addition processing (step) S10-2). Specifically, the facility management system 10a generates an admission / entry setting record including data related to a visitor code, a base, a time, and an event for the attendant, and records it in the admission / entry setting DB. The facility management system 10a generates a two-dimensional code that records an event code and a visitor's corporate name and name for outsiders. Then, the facility management system 10a transmits this two-dimensional code to an outsider's mobile terminal.

  In addition, the facility management system 10a newly adds a notification of change (attendance announcement) of a participant of an approval event from the control unit 21 of the event support system 20 (step S8-3 in FIG. 16). For the participant who has announced attendance, the admission / entry setting necessity determination process (step S10-1) and admission / entry setting addition (step S10-2) are executed as necessary.

  On the other hand, when the control unit 21 of the event support system 20 gives a notification of change (absence announcement) of a participant of the approval event (step S8-4 in FIG. 16), the facility management system 10a If is a visitor, an admission / entry setting deletion process is executed (step S10-3). Specifically, the admission / entry setting record of the visitor's event is deleted from the admission / entry setting DB.

  Also, when the control unit 21 of the event support system 20 receives a cancellation notification of the approval event (step S8-7 in FIG. 16), the facility management system 10a deletes the visitor's entry / entry setting (step S10-3) is executed.

  On the other hand, when the change notification of the approval event is provided from the control unit 21 of the event support system 20, the facility management system 10a first determines whether the facility is changed. In the case of facility change (step S8-6 in FIG. 16), the facility management system 10a performs a visitor entry / room entry setting deletion process (step S10-3).

  Furthermore, the facility management system 10a performs an entrance / entry setting necessity determination process (step S10-1) and an entrance / entry setting addition process (step S10-2) as necessary for each attendant. Run.

  If there is no change in the facility, the facility management system 10a executes a setting change process for the visitor (step S10-4). For example, the time of the approval event is changed by changing the time of the admission / entry setting record recorded in the admission / entry setting DB.

  If the visitor is an officer / employee, an employee ID (ID card) will be used if it is near the time (event holding time) recorded in the admission / entry setting DB based on the admission / entry setting record information in the admission / entry setting DB・ Entering is possible. When actually entering or entering the room, hold the ID card over the gate opening / closing card reader, and enter the room.

  If the visitor is an outsider of another corporation, the employee does not have an employee ID card (ID card), so an external visitor ID card is lent at the window. Specifically, the sent two-dimensional code is read by a two-dimensional code reader at the facility reception, and the event and the visitor are specified. Next, the external visitor ID card to be lent is read by the card reader, and the event and the visitor are linked, so that the external visitor ID card is entered into the admission / entry setting record information of the admission / entry setting DB. Tie it. As a result, as in the case of officers and employees, it is possible to enter and enter the room with the ID card for external visitors as long as it is near the event holding time.

  When a visitor entry is detected, the facility management system 10a executes a visitor entry process (step S10-5). In this case, the facility management system 10a notifies a visitor to the event support system 20 (step S9-1 in FIG. 16).

  In addition, the facility management system 10a receives information from the facility by an operation of leaving the facility with an employee ID card (IC card) in the case of an officer / employee visitor, and an operation of accepting and returning an ID card for an external visitor in the case of an outsider. Detect exit. When the exit is detected, the facility management system 10a executes a visitor exit process (step S10-6). In this case, the facility management system 10a notifies the event support system 20 of an exit about the visitor (step S9-4 in FIG. 16).

(Information management process)
Next, the information management process will be described with reference to FIG. The information management system 10b includes an event material DB for distributing information to participants. In this event material DB, distribution material (event material) registered by the event applicant in association with the event code is recorded. Furthermore, the importance of information such as [general, important, confidential] is added to the handout material. The information management system 10b is connected to a smart terminal via a network. This smart terminal is a computer terminal for browsing information for an event.

Hereinafter, information processing executed in the information management system 10b will be described.
When an event approval notification is provided from the control unit 21 of the event support system 20 (step S8-2 in FIG. 16), the information management system 10b displays a distribution document that can be viewed in advance as a smart terminal that is in charge of the attendant (Step S11-1). Specifically, the information management system 10b determines the distribution material that can be viewed in advance for each attendance presenter according to the access authority of the event material based on the affiliation / post of the presenter and the importance of the distribution material. . Then, the information management system 10b distributes (pushes) distribution materials determined to be pre-viewable to each attendance claimant to the smart terminal that is in charge of the attendance claimant.

  As described above, when the notification (change of attendance) of the approval event participant is notified from the control unit 21 of the event support system 20 (step S8-3 in FIG. 16), the information management system 10b is in advance The distribution material that can be browsed is pushed to the smart terminal that is in charge of the new attendant (step S11-1).

  In addition, when the control unit 21 of the event support system 20 notifies the change (distribution material) of the approval event (step S8-5 in FIG. 16), as described above, the information management system 10b determines the additional material. Then, the handout material that can be browsed in advance is pushed to the smart terminal of the attendant who is in attendance (step S11-1).

  On the other hand, if there is a deleted material, the information management system 10b deletes the deleted material from the smart terminal that is in charge of the participation demonstrator (step S11-2). Specifically, the information management system 10b instructs the smart terminal of the attendant who has attended to delete the deleted material. If there is a document instructed to be deleted, the smart terminal deletes it.

  When the control unit 21 of the event support system 20 notifies the change (participation of absence) of the participant of the approval event (step S8-4 in FIG. 16), the information management system 10b determines the smart of the person who is absent. Delete the deleted material from the terminal (step S11-2).

  When the approval event is canceled by the control unit 21 of the event support system 20 (step S8-7 in FIG. 16), the information management system 10b retrieves the event material from the smart terminals that are in charge of all attendees. Delete (step S11-2).

When the information management system 10b detects that the participant's smart terminal is outside the company, the information management system 10b turns off the access authority (R / W function) to the event material (step S11-3).
On the other hand, when the attendance of the participant's approval event is detected (when it is detected that the participant is in the venue at the event holding time), the access authority (R / W function) to the event material is turned on (step S11-4). ). Then, the attendance notification of the participant is given to the event support system 20. This attendance notification for participants includes information for identifying events and participants.

  Further, when the end of the approval event is detected (when the event holding time is exceeded or the departure from the holding place is detected), the information management system 10b deletes the event material (step S11-5).

  When the information management system 10b detects the end of all the participants, an event end notification is transmitted to the event support system 20. The event end notification includes information for identifying the event.

(Management processing of transportation expense settlement)
Next, transportation cost adjustment management processing will be described with reference to FIG. The transportation expense management system 10c is connected to the movement DB and transportation expense settlement DB. A travel expense detail record is recorded in the movement DB. In this transportation expense detail record, data relating to transportation expense detail code, date, destination (event location), purpose (event type), event, route, amount, settlement date, and officer / employee are recorded.

In the transportation expense detail code data area, data relating to an identifier for specifying each transportation expense detail record is recorded.
In the date data area, data related to the event date is recorded.
In the destination data area, data for specifying the event location is recorded.
Data for specifying the event type is recorded in the target data area.
In the event data area, data relating to an identifier (event code) for identifying a participating approval event is recorded.

In the route data area, data related to the moved route is recorded.
In the amount data area, data relating to the amount of transportation expenses required for movement is recorded.
In the settlement date data area, the date of settlement application is recorded.
In the officer / employee data area, data relating to an identifier (an officer / employee code) for identifying the officer / employee who has moved for the approval event is recorded.

  A transportation expense settlement management record is recorded in the transportation expense settlement DB. In this transportation expense settlement management record, data relating to officers / employees, period, amount, transportation expense detail code, and settlement status is recorded.

In the officer / employee data area, data relating to an identifier (an officer / employee code) for specifying an officer / employee for which transportation expenses are to be settled is recorded.
In the period data area, data relating to a period for which transportation expenses are to be settled is recorded. In this embodiment, it is set for every period (for example, April 2013 period) determined by the closing date of transportation expense settlement.

In the amount data area, data relating to the amount to be paid by the officer / employee is recorded.
In the transportation cost detail code data area, data relating to an identifier for specifying a transportation expense detail record to be settled for transportation expenses is recorded.

In the settlement status data area, a flag for specifying the settlement status of the officer / employee is recorded.
Note that the transportation expense settlement management record in the transportation expense settlement DB holds the transportation expense detail record in the mobile DB during the period (the settlement target period) as an element.

Hereinafter, information processing executed in the transportation cost management system 10c will be described.
When the event end notification is provided from the control unit 21 of the event support system 20 (step S8-9 in FIG. 16), the transportation cost management system 10c executes attendee movement determination processing (step S12-1). ). Specifically, the transportation cost management system 10c identifies officers / employees (moving participants) who have moved to attend the event. Specifically, the determination is made by comparing the office of the officer / employee and the location of the event (meeting).

And the transportation expense management system 10c performs the production | generation process of movement information for every movement participant (step S12-2). Specifically, the transportation expense management system 10c generates the following transportation expense detail record for each movement participant based on the event information on which movement has occurred and records it in the movement DB.
Transportation Cost Detail Record Date = Event Date Transportation Cost Detail Record Destination = Event Location Transportation Cost Detail Record Purpose = Event Type Transportation Cost Detail Record Event = Event ID
Officers / employees of the transportation expense detail record = officer / employee code of the moving participant

  In addition, when the event destination is a customer related to a company base, a project, or the like, a predetermined value may be set for the route and the amount as the approval route. In this case, the transportation cost management system 10c holds default values of the route and the amount corresponding to the company base and the customer.

  If there is no unsettled transportation expense settlement management record for the settlement target period to which the event date related to the mobile participant belongs in the transportation expense settlement DB, the transportation expense settlement management record for the settlement target period to which the event date related to the mobile participant belongs Is generated. The travel expense adjustment management record associates both records by recording the travel expense detail code of the previously generated transportation expense detail record.

  Then, the transportation expense management system 10c transmits a ToDo notification about transportation expense settlement to the event support system 20 (step S9-5 in FIG. 16). In response to this notification, the event support system 20 registers transportation expense settlement as ToDo of the mobile participant in the schedule management system 50 (step S8-10 in FIG. 16).

  In addition, when there is an unsettled transportation expense settlement management record for the settlement target period to which the event date related to the moving participant belongs in the transportation expense settlement DB, this transportation expense settlement management record holds the previous transportation expense detail record. .

  When the transportation expense settlement deadline has arrived, the transportation expense management system 10c executes a confirmation process for unpaid transportation expense settlement (step S12-3). Specifically, the transportation expense management system 10c extracts a transportation expense settlement management record that has not been settled from the transportation expense settlement DB.

  Next, the transportation expense management system 10c executes transportation expense settlement arousing processing for officers and employees recorded in the transportation expense settlement management record that has not been settled (step S12-4). Specifically, the transportation cost management system 10c transmits an e-mail for alerting to the officer / employee who has not yet settled the transportation expenses indicating that there is unpaid transportation expenses.

  When the officer / employee selects the transportation expense settlement ToDo registered in the schedule management system 50, the transportation expense settlement application function of the transportation expense management system 10c is activated. Executives and employees use this function to apply for transportation expenses. Specifically, a route is set for the transportation expense adjustment details outside the approved route. In this case, the transportation expense management system 10c automatically calculates the amount according to the route. About the transportation expense adjustment details of the approval route, a predetermined value is set as the route and the amount of money. Here, correction can be performed as necessary, but if the correction is performed, the approval route is not met.

Then, confirm and set all the travel expense settlement details and apply (step S12-5).
When the application for transportation expense settlement is made, the transportation expense management system 10c notifies the event support system 20 of ToDo application for transportation expense settlement (step S9-6 in FIG. 16). Upon receiving this notification, the event support system 20 sets the travel expense settlement ToDo of the moving participant of the schedule management system 50 to the application state (step S8-11 in FIG. 16).

  Next, the transportation expense management system 10c executes transportation expense settlement approval processing (step S12-6). Specifically, in accordance with “management control: movement (transportation expense settlement)” in the control table CT4 of FIG. 13, the transportation expense management system 10c determines the legitimacy of the route for transportation expense settlement details that are outside the approved route. Ask the accountant for confirmation. Transportation costs are approved if confirmed by the accounting staff.

  When transportation expense settlement is approved, the transportation expense management system 10c notifies the event support system 20 of ToDo approval for transportation expense settlement (step S9-7 in FIG. 16). Upon receiving this notification, the event support system 20 sets the travel expense settlement ToDo of the mobile participant in the schedule management system 50 in an approved state (step S8-12 in FIG. 16).

  When the application for transportation expense settlement is approved, the transportation expense management system 10c executes transportation expense settlement processing (step S12-7). Specifically, the transportation expense management system 10c performs an approved transportation expense payment process for each officer.

As described above, according to the present embodiment, the following effects can be obtained.
(1) In the above embodiment, when the registration of the application event is detected, the control unit 21 of the event support system 20 executes the approval WF composition process (step S1-2). Here, the control unit 21 of the event support system 20 executes a business control extraction process (step S6-1). Further, the control unit 21 of the event support system 20 executes management control extraction processing (step S6-2). Thereby, a related control table for managing each individual control can be created according to the event.

  Further, the control unit 21 of the event support system 20 executes an individual control extraction process to be performed manually (step S7-1). And the control part 21 of the event assistance system 20 performs the order relationship setting process of the extracted individual control (step S7-2). Thereby, even when a plurality of approvals are required for one event, it is possible to perform an appropriate approval work in consideration of the preconditions.

  In addition, the control unit 21 of the event support system 20 executes the merge processing of the individual controls in the same order (Step S7-3). Thereby, even when a plurality of approvals are required for one event, the approval work can be performed collectively.

  In addition, the control unit 21 of the event support system 20 executes a service-to-person deployment process based on the organization and business (step S7-4). And the control part 21 of the event assistance system 20 performs the optimization process of approval WF (step S7-5). Thereby, even when a plurality of approvals are required for one event, the approval work can be performed collectively.

  (2) In the above embodiment, when an event approval notification is provided from the control unit 21 of the event support system 20, the facility management system 10a enters / enters the attendant of this event (meeting). A setting necessity determination process is executed (step S10-1). If the attendant has no authority to enter or enter an event (conference) venue, the facility management system 10a executes an entrance / entry setting addition process (step S10-2). Thereby, based on the approval of the event, it is possible to perform procedures for entering and entering the room necessary for the implementation of the event.

  In addition, when the control unit 21 of the event support system 20 receives a notification of a change (attendance announcement) of a participant in an approval event, the facility management system 10a sets the entrance / entry setting for the newly announced attendee Necessity determination processing is executed (step S10-1). Thereby, procedures for entering and entering the room can be performed in accordance with the change in the situation.

  In addition, when the control unit 21 of the event support system 20 notifies a change (absence announcement) of a participant of an approval event, the facility management system 10a enters the building if the absentee is a visitor. A room entry setting deletion process is executed (step S10-3). Thereby, according to the situation change, it is possible to carry out a procedure for a related person who is no longer required to enter or enter the room.

  If there is no change in the facility, the facility management system 10a executes a setting change process for the visitor (step S10-4). Thereby, the procedure for entering or entering the room can be changed in accordance with a change in the situation.

  In addition, when the visitor's entrance is detected by reading the card reader, the facility management system 10a executes the visitor entrance process (step S10-5). In this case, the facility management system 10a notifies the event support system 20 of an entry about the participant. Thereby, the event support system 20 can grasp the participation status of the event participants.

  If the visitor's exit is detected by reading the card reader, the facility management system 10a executes a visitor exit process (step S10-6). In this case, the facility management system 10a notifies the event support system 20 of the participant's exit. Thereby, the event support system 20 can grasp the progress of the event.

  (3) In the above embodiment, when an event approval notification is provided from the control unit 21 of the event support system 20, the information management system 10 b sends a distribution document that can be browsed in advance to the smart terminal that is in charge of the attending person. Push (step S11-1). Thereby, the material used in the event can be distributed accurately.

  In addition, when the control unit 21 of the event support system 20 notifies the change (participation announcement) of the participant of the approval event, the information management system 10b manages the distribution material that can be browsed in advance as the new attendance applicant. To the smart terminal (step S11-1). Thereby, even when the participant is changed, the material can be distributed accurately.

  Further, when the control unit 21 of the event support system 20 notifies the change (distribution material) of the approval event, the information management system 10b transmits the distribution material that can be browsed in advance for the additional material. Push to the smart terminal (step S11-1). Thereby, even when the material is changed, the material can be distributed accurately.

  In addition, when the control unit 21 of the event support system 20 notifies the change (absence announcement) of the participant of the approval event, the information management system 10b deletes the deleted material from the smart terminal that is in charge of the absence applicant. (Step S11-2). Thereby, when it becomes impossible to participate in an event, the distributed material can be deleted.

  If the approval event is canceled by the control unit 21 of the event support system 20, the information management system 10b deletes the event material from all the smart terminals that are in charge of the attendees (step S11-2). ). As a result, even if the event is canceled, the distributed material can be deleted.

  When the attendance of the participant's approval event is detected, the access authority (R / W function) to the event material is turned on (step S11-4). In this case, the smart terminal sends a participant attendance notification to the event support system 20. Thereby, the event support system 20 can grasp the attendance status of the event participants.

  When the information management system 10 b detects the end of the approval event, it transmits an event end notification to the event support system 20. Thereby, the event support system 20 can grasp the progress of the event.

  (4) In the above embodiment, when the event end notification is provided from the control unit 21 of the event support system 20, the transportation cost management system 10c executes the attendee movement determination process (step S12-1). . Thereby, in the transportation expense management system 10c, the officer / employee who needs the transportation expense can be specified, and the transportation expense can be settled.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, the status notification unit 211 of the event support system 20 broadcasts a status change to the service management system 10. Instead of this, a state notification dictionary may be held in the state notification unit 211, and notification processing may be performed according to the state notification dictionary. In this case, in the status notification dictionary, a condition for notification to each service management system 10 corresponding to the contents of the status change of the approval event and a response corresponding to the condition are recorded. The status notification dictionary can be implemented as a rule or a program.

  In the above embodiment, the state change of the state change unit 212 of the event support system 20 is performed using the state change dictionary held by the state change unit 212. Instead, the state change dictionary may be held in each service management system 10. The state change dictionary may be implemented as a rule or a program.

  In the above embodiment, the event support system 20 is connected to the party management system 22, the business storage unit 23, and the event storage unit 24 as an organization information storage unit via a network. The hardware configuration of the party management system 22, the business storage unit 23, and the event storage unit 24 is not limited to this, and can be realized by a configuration such as being provided in the event support system 20.

  In the above embodiment, the event support system 20 and the schedule management system 50 are connected via a network. Instead of this, the event support system 20 and the schedule management system 50 may be constructed as one system. In this case, the status of the approval event is managed in the schedule management record.

  In the above embodiment, the event storage unit 240 records the event management record 240 related to the application event acquired from the schedule management system 50. In this event management record 240, event code and data related to status are recorded. Instead, the schedule management system 50 may manage the status. Here, when the event support system 20 detects a change in the event state, the schedule management system 50 updates the status.

  In the above embodiment, the event storage unit 240 records the event management record 240 related to the application event acquired from the schedule management system 50. In this event management record 240, event code and data related to status are recorded. Here, the event management record 240 may be recorded with data related to the event code, event name, applicant, date / time, location, event type, business, material, and participant.

  In the above embodiment, the status notification unit 211 executes notification processing for each service management system 10 in response to event registration or change determined by approval or the like. This notification process is performed using a dictionary held by the state notification unit 211. Here, the state notification unit 211 may broadcast the notification to all the service management systems 10. In this case, each service management system 10 determines the necessity of handling based on the notification acquired from the event support system 20. For this reason, each service management system 10 is provided with information (for example, “determination condition for notification to be handled” and “corresponding under this determination condition” for performing a response corresponding to the notification acquired from the event support system 20 The dictionary which associates “the processing content to be processed” is stored. Each service management system 10 determines whether the notification acquired from the event support system 20 is related to the provided service based on the content of the notification. The service management system 10 executes a process corresponding to this notification when the content is related to the provided service.

  In the above embodiment, each participant has the attribute of participation form (AT1) in parallel with the attendance expression state (ST22). Regarding entrance management, if there is a move depending on the work location of the participant, a new entrance / entry setting is required, and if there is no transfer, a new entrance / entry setting is not required. Instead of this, the entrance / entry setting may be performed for each officer / employee based on the facilities that can be entered / entered. In this case, the party management system 22 records the facilities that can be entered and entered for each officer. If the location of the approval event is not registered as a facility that can be entered or entered, a new entry / entry setting is performed.

  In the above embodiment, the control unit 21 of the event support system 20 executes the approval WF operation process (Step S1-3). Here, the participant management process for checking the recommended participant of the application event and the balance of the event participant may be performed. In this case, recommended participants who are desired to participate are registered in the control table CT according to the event type. Further, other recommended participants may be registered according to the event participants. And the control part 21 of the event support system 20 performs a participant management process at the time of the application for an event.

The participant management process will be described with reference to FIG.
First, the control unit 21 of the event support system 20 executes an event registration process (step S13-1). Specifically, the control unit 21 of the event support system 20 detects event registration in the schedule management system 50.

  Next, the control unit 21 of the event support system 20 executes an event party identification process (step S13-2). Specifically, the related control extraction unit 213 of the control unit 21 identifies the participant recorded in the participant data area of the registered event management record 240 as an event related person.

  Next, the control unit 21 of the event support system 20 executes a determination process as to whether or not there is a leak in the related parties (step S13-3). Specifically, the related control extraction unit 213 of the control unit 21 specifies a recommended participant in the control table CT based on the event type and target of the event management record 240. When the recommended participant is registered as an event related person, it is determined that there is no omission in the related person. On the other hand, when a recommended participant not included in the event related party is detected, it is determined that there is a leak in the related party.

  When it is determined that there is a leakage in the related parties (in the case of “YES” in step S13-3), the control unit 21 of the event support system 20 executes alert processing (step S13-4). Specifically, the related control extraction unit 213 of the control unit 21 outputs an alarm screen to the applicant's officer / employee terminal. This alarm screen is provided with a participant change input field together with an OK button.

  Next, the control part 21 of the event assistance system 20 performs the determination process about whether there exists any change (step S13-5). Specifically, the related control extraction unit 213 of the control unit 21 determines whether or not there is an input in the change input field of the participant, and whether or not there is a change due to the addition of the participant.

  When there is an input in the change input field of the participant and it is determined that there is a change (in the case of “YES” in step S13-5), the control unit 21 of the event support system 20 executes a change process (step S13— 6). Specifically, the related control extraction unit 213 of the control unit 21 changes the officer / employee code recorded in the participant data area of the event management record 240 of the event storage unit 24. And the process after step S13-3 is repeated.

  On the other hand, when it is determined that there is no input in the change input field of the participant and there is no change (in the case of “NO” in step S13-5), the control unit 21 of the event support system 20 performs the alert processing in the approval workflow. Is executed (step S13-7). Specifically, the related control extraction unit 213 of the control unit 21 includes a message indicating that there is no problem in the approval workflow.

  And the control part 21 of the event assistance system 20 performs the approval WF operation | movement process similarly to step S1-2 (step S13-8). Even when it is determined that there is no omission in the related parties (in the case of “NO” in step S13-3), the control unit 21 of the event support system 20 executes the approval WF operation process (step S13-8). .

  -In above-mentioned embodiment, when the participation expression (attendance expression or absence expression) of a participant is detected, the control part 21 of the event assistance system 20 performs a participant change notification process (step S8-3, S8-4). ). Here, proxy participation may be allowed. In this case, the event support system 20 transmits a participant change notification including proxy participant information to each service management system 10. In this case, each service management system 10 handles the proxy participant based on the authority of the original participant.

  In the above embodiment, the end of the approval event is determined in the information management system 10b according to the information usage status of the event participant. The end determination of the approval event is not limited only to information usage. For example, in the information management system 10b, when the end cannot be detected, the end of the approval event may be determined based on the time zone in which the approval event is set. In this case, it is determined that the event has ended when a predetermined time has elapsed from the event date.

  In the above embodiment, when the registration of the application event is detected, the control unit 21 of the event support system 20 executes the approval WF composition process (step S1-2). Instead, when the prior approval is performed for the individual control in the application event, the approval workflow for the individual control may be omitted. In this case, the event support system 20 is provided with an approval information storage unit that records pre-approval information for the event type, date / time, location, and target. And the control part 21 of the event assistance system 20 confirms the presence or absence of prior approval in an approval information memory | storage part based on event content, when registration of an application event is detected. If pre-approval is already registered, this individual control is approved and the approval workflow is omitted. Thereby, it is possible to efficiently approve event contents by prior approval.

  In the above embodiment, the control unit 21 of the event support system 20 generates the related control table by executing the business control extraction process (step S6-1) and the management control extraction process (step S6-2). To do. Then, an approval workflow is generated based on the related control table. In this case, an approval workflow may be generated according to the application event attribute. For example, the necessary approval workflow is determined according to the applicant of the application event, the date and time, the location, and the attributes of the participants.

  In the above embodiment, the control unit 21 of the event support system 20 transmits various notifications regarding the approval result and the approval event to all the service management systems 10. Instead, the service management system 10 that transmits the notification may be selected according to the attribute of the approval event. In this case, the event support system 20 is provided with a notification destination information storage unit that designates the service management system 10 that transmits the notification according to the individual control.

  In the above embodiment, the transportation cost management system 10c generates a travel information generation process (step S12-2), an unsettled transportation cost settlement confirmation process (step S12-3), and transportation expense settlement for each traveling participant. The process (step S12-4) is executed. Here, the transportation expense management system 10c may immediately execute the transportation expense settlement application to approval processing.

  In the above embodiment, the procedure DB is used when creating an approval workflow in the WF cooperation unit 21B of the event support system 20. Here, you may make it use for the service management system 10 of a cooperation target, and the logic check of the process in a cooperation destination. For example, in the control table CT4 of FIG. 13, “Management Control: Movement (Transportation Expenses)” has an implementation result as a control aspect. The “completeness” of the implementation result defines that the participant is a visitor at the end of the event (“implementation result”). From here, the steps (steps S12-1, S12-2) of the transportation expense settlement system can be derived. Similarly, (Step S12-6) can be derived from “legitimacy” and “accuracy”. Further, (Step S12-3) can be derived from the “time limit system”.

  In the above embodiment, the facility management system 10a generates a two-dimensional code for an outsider and transmits it to the mobile terminal of the outsider. When an outsider visits, the sent two-dimensional code is read by a two-dimensional code reader at the facility reception, and the event and the visitor are specified. Subsequently, the external visitor ID card to be lent is read by the card reader, and the external visitor ID card is linked to the admission / entry setting record information in the admission / entry setting DB. It is also possible to use near field communication (NFC) in place of the two-dimensional code or ID card. In this case, an NFC-equipped device is used as an ID card. In addition, when an identification code of an NFC-equipped device owned by an external visitor can be grasped in advance, it is also possible to perform entry / entry settings using this identification code.

  In the above embodiment, the facility management system 10a executes the entrance / entrance setting addition process (step S10-2). Here, when participating in a plurality of events, the entrance / room entry settings may be registered together. For example, in the case of an in-house officer / employee, the earliest time to the latest time of a plurality of events are registered in the admission / room entry setting DB. Moreover, in the case of an outsider, it collects to one ID card for external visitors. In this case, for each event, the admission / entry setting record associated with the external visitor ID card is registered in the admission / entry setting DB.

  In the above-described embodiment, when there is a deleted material, the information management system 10b deletes the event material from the smart terminal that is in charge of the participation demonstrator (step S11-2). Here, it may be deleted when not referenced by anyone (garbage collection method). Thereby, it is possible to cope with the case where the same file is used in a plurality of events.

  In the above embodiment, the WF cooperation unit 21B of the control unit 21 of the event support system 20 detects an event application registered in the schedule management system 50 (F11). Here, the cooperation between the schedule management system 50 and the WF system 55 performed by the WF cooperation unit 21B may be performed at the time of executing the approval workflow in addition to the time of registration (application).

  Further, the application event may be registered not in the schedule management system 50 but in the WF system 55. In other words, when the WF cooperation unit 21B of the event support system 20 detects an application event registered in the WF system 55, the information is registered in the event storage unit 24. Further, the WF cooperation unit 21 </ b> B distributes event registration information to the schedule management system 50. Thereafter, as described above, the approval workflow according to the contents of the application event is synthesized and executed.

  In the above-described embodiment, the WF system 55 performs processing for circulating various applications to the officer / employee terminal of the authorized person related to the approval based on the approval workflow. Here, when executing the approval workflow, the ToDo of the schedule management system 50 may be used to notify an authorized person who performs control such as confirmation next. In this case, the WF cooperation unit 21B (approval WF execution unit 215) of the event support system 20 notifies ToDo of the authorized person who should perform control such as confirmation next in accordance with the approval workflow. In this ToDo, a link to the confirmation screen of the WF system 55 is set. Then, the confirmation work can be performed on the confirmation screen of the WF system 55. Further, the confirmation may be performed directly on the ToDo screen without linking to the confirmation screen of the WF system 55 from ToDo.

  In the above embodiment, the schedule management system 50 manages events (application events) applied by officers / employees and ToDo for each officer / employee. Here, the service cooperation unit 21A of the control unit 21 of the event support system 20 may notify the schedule management system 50 of the event state change sequentially. Further, the WF cooperation unit 21B of the control unit 21 may sequentially notify the confirmation status of the approval workflow to the schedule management system 50. In this case, the schedule management system 50 registers the event state. Thereby, the state of the event can be confirmed using the scheduler of the schedule management system 50.

  DESCRIPTION OF SYMBOLS 10 ... Service management system, 10a ... Facility management system, 10b ... Information management system, 10c ... Transportation expense management system, 20 ... Event support system, 21 ... Control part, 211 ... Control extraction part, 212 ... WF generation part, 213 ... WF execution unit, 215 ... status notification unit, 216 ... state change unit, 22 ... party storage unit, 23 ... business storage unit, 24 ... event storage unit, 30 ... procedure DB, 32 ... service allocation table storage unit.

Claims (14)

An event support apparatus comprising a control unit connected to a first management system in which event information or ToDo information is recorded, and a plurality of service management systems that execute various processes corresponding to managed events,
The control unit is
In order to identify a management target event to be managed based on an event participant in the event information recorded in the first management system or a worker in ToDo information, and to execute various processes corresponding to the management target event , To notify each service management system based on the managed event,
From each service management system, obtain status change information related to a managed event related to the event participants or workers,
According to the status change information, the state of the event participant or the worker is specified, and the status of the managed event determined based on the status change information and the status of the participant or the worker are determined. An event support apparatus that executes various processes corresponding to a management target event subsequent to the management target event for which the situation change information has been acquired.   The event according to claim 1, wherein when the control unit detects a change in status of the managed event, the control unit notifies the service management system of the change in the managed event. Support device. The control unit identifies an event attribute of the managed event,
The event support apparatus according to claim 1, wherein it is determined whether notification to each service management system is necessary based on the event attribute. An event support apparatus comprising a first management system in which event information or ToDo information is recorded, a control unit connected to the first management system, and an authorized person identifying unit for identifying authorized persons related to approval ,
The control unit further includes an approval route management unit that determines an approval route according to an event attribute,
The control unit acquires an approval route from the approval route management unit based on the event attribute of the management target event for event information or ToDo information registered in the first management system,
In the plurality of identified approval paths, using the authorized person identification unit, identify the authorized person related to the approval according to the event attribute, identify the common execution authorized person, and does not violate the approval rule, An event support apparatus that generates an approval route in which execution authority is integrated when a common execution authority can be set.   5. The event support apparatus according to claim 4, wherein the control unit identifies an authorized person related to the approval based on an attribute of a participant in the managed event or an attribute of a worker in ToDo information. The approval route management unit further includes a control storage unit that records individual controls for control events that require control,
The control unit is
6. The control event that requires control is specified according to the event attribute, and the approval route management unit determines an approval route according to individual control for the control event. The event support apparatus described. In the control storage unit, information on order relations for individual controls is recorded,
The control unit is
For a plurality of individual controls specified according to the event attribute, specify the order relationship of each individual control,
The event support apparatus according to claim 6, wherein an approval route is determined based on the order relation.   8. The event support apparatus according to claim 6, wherein the control storage unit records individual controls to be performed by the authority for the authority related to the approval on the approval path. The control unit is
Check for prior approval of the managed event,
The event support apparatus according to any one of claims 6 to 8, wherein when the prior approval is already registered, the individual control is handled as being approved.   The event according to any one of claims 4 to 9, wherein the control unit issues an approval request to an authority related to approval in the approval route, and manages an approval status of the authority. Support device. The control unit is further connected to a workflow management system,
The event support apparatus according to claim 4, wherein the control unit shares an approval route and an approval status with the workflow management system. The control unit is
Identify recommended participants in the managed event;
The event support device according to any one of claims 1 to 11, wherein an alert is output when a recommended participant is not registered in the managed event. Event support using an event support device having a control unit connected to a first management system in which event information or ToDo information is recorded and a plurality of service management systems that execute various processes corresponding to the managed event A method of performing
The control unit is
In order to identify a management target event to be managed based on an event participant in the event information recorded in the first management system or a worker in ToDo information, and to execute various processes corresponding to the management target event , To notify each service management system based on the managed event,
From each service management system, obtain status change information related to a managed event related to the event participants or workers,
According to the status change information, the state of the event participant or the worker is specified, and the status of the managed event determined based on the status change information and the status of the participant or the worker are determined. An event support method comprising: executing various processes corresponding to a management target event subsequent to the management target event for which the situation change information has been acquired. Using an event support apparatus comprising a first management system in which event information or ToDo information is recorded, a control unit connected to the first management system, and an authorized person identification unit for identifying authorized persons for approval A method of providing event support,
The control unit further includes an approval route management unit that determines an approval route according to an event attribute,
The control unit acquires an approval route from the approval route management unit based on the event attribute of the management target event for event information or ToDo information registered in the first management system,
In the plurality of identified approval paths, using the authorized person identification unit, identify the authorized person related to the approval according to the event attribute, identify the common execution authorized person, and does not violate the approval rule, An event support method characterized by generating an approval route in which execution authority is integrated when a common execution authority can be set.

Images