JP2003281339A - Method and program for supporting event - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To dispense with manual work of a conventional manager by preparing a list of all the persons to inform with respect to an event, delivering the list and automatically tabulating and presenting participants and non participants after obtaining answers as for a method and program for supporting event for presenting the list of the persons to inform of the event. <P>SOLUTION: The method comprises: a step for providing a master in which at least the names and attribute information are registered by correlating them with the contactees IDs, extracting attribute information corresponding to the ID or name from the master corresponding to the input of the ID or name of a person who becomes the center of the event and extracting other names and IDs at need of the same extracted attribute information on similar attribute information at need and the ID; and a step for presenting the list of the extracted name and the extracted IDs at need as the list of the contactees. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an event support method and an event support program for presenting a list of contact persons of an event.

[0002]

2. Description of the Related Art Conventionally, in the case of an event such as a ceremonial occasion at a workplace, for example, "Mr. A's wedding," a friend secretary who is the coordinator of the event extracts a person related to the document and creates it. And send the request to participate, send an e-mail to request the participation, call to talk about the situation and request the participation, if the participation fee is required, collect the participation fee individually I did it, I got it transferred to the secretary's account, and I managed separately the collection and transfer.

[0003]

Therefore, the event organizer makes a list of contacts who are to be contacted in relation to the event, sends the event documents to the contacts, and provides participation / non-participation answers. It is extremely difficult to get each of them and collect and manage costs individually, which is extremely difficult, and sometimes the past related parties may be missed. There was a problem that it took time.

The present invention solves these problems.
When event information is registered, the master is searched to automatically extract contact persons related to the event information, which are related to the present and past, and present a list, and the event is notified to the persons concerned through a web page or e-mail. Information, presence / absence,
We will contact you about costs etc. and collect answers and payment of costs, create a contact list at all events and deliver it, get answers and automatically aggregate and present participants and non-participants, The purpose is to eliminate the manual work of the secretary.

[0005]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG.

In FIG. 1, a server 1 performs various processes according to a program, and is composed of an event office system 2 and a personnel information database 4.

The event office system 2 refers to the personnel information database 4 and presents a list of contacts for the event.

The personnel information database 4 is a database in which a name, past and present affiliation information, and the like are registered in association with the IDs of persons to be contacted (for example, employees).

Next, the operation will be described.

In response to the input of the ID or name of the person who is the center of the event, the event office system 2 extracts the affiliation information corresponding to the ID or the name from the personnel information database 4, and the extracted affiliation information is the same or Other names and IDs of similar affiliation information are extracted as needed, and a list of the extracted names and IDs is presented as a contact target person list.

At this time, the affiliation information is the current and past affiliation information.

Further, the affiliation information is the current and past affiliation information and the period of time belonging to the affiliation information.

[0013] In addition, the event information, the answer column of presence or absence of participation, and the answer column of participation fee and payment method are set for all contact persons or designated contact persons in the contact person list. Electronic data is transmitted or accessed, and the completion is recorded when transmitted or accessed.

Further, when the reply is received from the contact target person, the answer column of the corresponding person has been received from the contact target person list,
Whether or not to participate is recorded in the participation column, and the payment method is recorded in the participation cost column if necessary.

Further, the recorded information in the answer column, the participation column, and, if necessary, the participation cost column is totaled and a list is created and presented.

Therefore, when the event information is registered, the personnel information database 4 is searched to automatically extract contacts related to the event information, which are related to the present and the past, and the list is displayed. By contacting related persons via e-mail etc. regarding event information, presence / absence, costs, etc., and responding and paying for the cost, we will create a contact list for all events and deliver them, and obtain answers. Participants and non-participants can be automatically aggregated and presented to eliminate the manual work of the secretary.

[0017]

BEST MODE FOR CARRYING OUT THE INVENTION Next, embodiments and operations of the present invention will be sequentially described in detail with reference to FIGS.

FIG. 1 shows a system configuration diagram of the present invention.

In FIG. 1, a server 1 loads a program read from an external storage device or a recording medium into a main memory and activates it to perform various processes. Here, an event office system 2 and personnel information are used. It is composed of the database 4 and the like.

The event office system 2 refers to the table and the personnel information database 4, presents a list of contacts for the event, and is composed of 21 to 28.

The event reception program 21 receives an event.

The notification destination search program 22 searches the personnel information database 4 or the like for relevant persons (notification destinations) for the received event and extracts them to create a contact list.

The event settlement program 22 setstles the participation fee of the event.

The participant confirmation program 24 confirms the participation and non-participation of the participants.

The use history table 25 manages the user history (see (a) of FIG. 19).

The notification history table 26 manages the notified history (see S in FIG. 19B).

The answer history table 27 manages the answer history (see (c) of FIG. 19).

The settlement history table 28 manages the settlement history of participants and the like (see (d) of FIG. 19).

The salary transfer system 29 manages the transfer of the employee's salary, and here, the event participation fee is deducted from the salary.

The expense settlement system 30 setstles various expenses of the company.

The map search system 31 is a map search system for a road to a customer.

The personnel information database 4 is various personnel databases within the company, and is composed of 41 to 46 here.

The employee master 41 is the employee ID of the company
The name, affiliation code, contact information, etc. are registered in association with (employee code) (see (a) of FIG. 18).

The affiliation master 42 has affiliation names and the like registered in association with affiliation codes ((b) of FIG. 18).
reference).

The project master 43 has a project name and the like registered in association with the project code (see (b) of FIG. 18).

In the employee affiliation history table 44, the affiliation code, past affiliation start date, affiliation end date, etc. are registered in association with the employee code ((d in FIG. 18). )reference).

Employee project participation history table 45
Corresponds to the employee code, the project code,
The past start date and end date of the affiliated member are registered (see (e) in FIG. 18).

Affiliated project setting history table 46
Indicates that the name, installation start date, installation end date, etc. are registered in association with the code ((f) in FIG. 18).
reference).

The network 5 connects the server 1 and a large number of user terminals 6.

The user terminal 6 registers an event in the server 1 and receives event information from the server 1 via a web page or electronic mail.

A detailed description will be given below.

FIG. 2 shows an explanatory view of the present invention.

FIG. 2A shows a flowchart.

In FIG. 2A, S1 logs in. This is because the user operates the user terminal 6 of FIG.
Display the login screen of the event office system 2 of FIG. 2B, which will be described later, and on the screen, enter the employee code: password :, press the execute button, and the event office system 2 holds it. By referring to the company-wide common secret table of FIG. 19 (g), it is checked whether the registered employee code and password are registered, the individual authentication of the employee is performed, and if OK, the process proceeds to the next S2. In the case of NO, a predetermined number of times,
Repeat S1. When the number of times exceeds the predetermined number, a code or password error message is displayed and the process ends.

At S3, a menu screen is displayed. This displays, for example, a menu screen of the event office system of FIG. Here, FIG. 2B
The employee code input in step 1, the name retrieved by searching the employee master 41 in FIG. 18A based on the employee code, and the event menu are displayed in the lower row.

In step S4, a menu is selected. here,
1. Displayed on the menu screen of FIG. Event registration 2. Event reference / payment 3. Select one from among the participant confirmations and, in response to the selection,
The process proceeds to any one of the event registration process of 4, the event reference / settlement process of S5, and the participant confirmation process of S6.

In step S7, it is determined whether or not the process is completed. If YES, then end. If NO, the menu screen of S2 is displayed and repeated.

FIG. 2B shows an example of the login screen. This login screen is an example of the login screen that is displayed when the user operates the user terminal 6 to log in to the event office system 2. Here, the following information shown in the figure is input and the registration button is entered. Press to send.

-Employee code: -Password: When the user operates the user terminal 6 on the above login screen and inputs the employee code and password and collates and is OK, the event office system 2 It is possible to use various functions that it has, and it is possible to register an event here.

FIG. 2C shows an example of the menu screen. This menu screen allows the user to select a process to be performed by using the event office system 2. Here, one of the following three shown in the figure is used.
Choose one.

1. Event registration 2. Event reference / payment 3. Confirmation of Participants FIG. 3 shows an explanatory diagram (event registration) of the present invention. This is the process when the event registration process is selected on the menu screen in S5 of FIG.

In FIG. 3, S11 receives an event. This is because the user operates the user terminal 6 to access the event office system 2 to download and display the event reception screen of FIG. 4, which will be described later, and input necessary information such as the event type from the screen. Then, the registration button is pressed to upload to the event office system 2 of FIG. 1, and the event office system 2 receives the event.

In step S12, the notification destination is searched. This is performed according to the flow charts of FIG. 5 and FIG.
Search the notifiers of the event accepted in and create a list of notifiers.

In step S13, the notification destination is confirmed. This is S
The notification destination searched in 12 is displayed and confirmed on the screen of FIG. 7 described later.

In step S14, a notification is given. For this, the event information is notified to the notification destination (notifier) after confirmation in S13, for example, by a Web page or electronic mail.

FIG. 4 shows an example of the event reception screen of the present invention. This is because the user operates the user terminal 6 to access the event office system 2 in S11 of FIG.
It is an example of an event reception screen downloaded and displayed on the display device of the user terminal 6, and here, the following information shown in the figure is displayed.

[0057]     ・ Employee code:     ·Full name :     ・ Notified person:         □ Current department:         □ Past departments:         □ Current participating projects:         □ Past participating projects:     ・ Event Type: Wedding     ・ Event name: Takashi Saito Wedding     ・ Date: 2:00 pm, February 11, 2002     ・ Reference information: "○○ Life Survey Average"                     Boss 50,000 yen, colleague 30,000 yen     ・ Comment: The place is ○○.

For the map, please see: http: // ...

Here, as the employee code, the employee code input at the time of log-in is displayed as it is, and the name is referred to the employee master 41 in FIG. It was taken out and displayed. Select one or more of the current department, the past department, the current participating project, and the past participating project displayed in the notification target column, and the flowcharts of FIGS. 5 and 6 to be described later. The notifier is extracted for the affiliation selected in. The event type is the event type to be registered, and here is the wedding ceremony. The event name is the name of the event. For the date and time of the event, reference information, and comment, enter the event name that the registrant considers appropriate for the event.

When the event information is input on the above event registration screen and the registration button is pressed, the event is uploaded to the event office system 2 of FIG. 1 to be registered and accepted.

FIG. 5 and FIG. 6 are diagrams for explaining the operation of the present invention (search for notification destination). This is S12 of FIG.
FIG.

In FIG. 5, S21 initializes the search result list. Here, the search result list initializes variables (arrays) for setting the following values described on the right side.

-Employee code: -Name: -Contact: S22 stores the employee code of the person who becomes the center of the event in the variable EJ (here, the person who becomes the center of the event on the screen of FIG. 4). Employee code “1998121” (Hitomi Saito) is stored in the variable EJ).

In step S23, it is determined whether the current department is to be notified. This determines whether the user who registered the event has selected "inside the current department" in the notification target field on the event reception screen of FIG. If YES, the current affiliated persons are added to the list through S24 to S26. On the other hand, in the case of NO, the process skips and proceeds to S27.

In S24, it is determined in S23 that the person to be the center of the event will be notified within the current department to which the notification is sent. Therefore, in the employee master 41, EJ (= 199812).
Get the record that is equal to 2). Here, the record of the employee master 41 in FIG. 18A is searched for, found, and acquired.

In step S25, the employee master is searched for a record that is equal to the belonging code (here, "1001") of the acquired record and whose employee code is not equal to EJ. Here, the employee master 41 of FIG.
The employee codes of the record that is equal to the affiliation code “1011” of the record No. and not equal to EJ are two (1981031) 1998121.

S26 adds to the list. This is S
In the above example taken out in step 25, two employee codes are added to the list (notification destination list).

In the case of YES in S23 above (when the currently belonging department is selected on the screen of FIG. 4), S2
From 4 to S26, all other employee codes having the same current affiliation (affiliation code) of the person who is the center of the event can be extracted and added to the notified party list.

In step S27, similarly to step S23, it is determined whether or not the department to which the user belongs in the past is to be notified. This determines whether or not the user who registered the event has selected "inside past department" in the notification target column on the event reception screen of FIG. YE
In the case of S, the related persons in the past belong to S28 to S31.
To add to the list. On the other hand, in the case of NO, the process skips and proceeds to S32 in FIG.

In S28, since it has been determined in YES in S27 that the person to be the center of the event is to be notified within the past department, the EJ (= 19) in the employee affiliation history table 44.
98122) and the record whose current date is after the end date of belonging is acquired. For example, FIG.
From the record of the employee code equal to EJ in the employee belonging history table 44 in (d), the record described on the right side of is acquired as the record whose current date is after the end date of belonging.

S29 is an employee affiliation history table 44.
, The same as the acquired affiliation code ("1002" in the example), and the affiliation start date is before the affiliation end date acquired and the affiliation end date is after the acquired affiliation start date , And the employee code is not equal to EL. Here, the employee code “1998123” described on the right side is searched as the employee code of the employee affiliation history table 44 in FIG. 18D (searching for the affiliation code “1002” being equal).

In S30, the employee master 41 is searched for a record having the same employee code as obtained in S29. Here, search as described on the right side. To be done.

S31 is added to the list. This is S
List of records extracted in 30 (list of notification destinations)
Add to.

In the case of YES at S27 described above (when the past department within the department is selected on the screen of FIG. 4), S2
From 8 to S31, all other employee codes having the same past affiliation (affiliation code) of the person who becomes the center of the event can be extracted and added to the notified party list.

In step S32, it is determined whether or not the current participating project is to be notified. This determines whether the user who registered the event has selected "within the current participating project" in the notification target column on the event reception screen of FIG.
If YES, the persons involved in the current participating project are added to the list through S33 to S36. On the other hand, NO
In case of, skip and proceed to S37.

In S33, it is determined in YES in S32 that the person who becomes the center of the event is notified within the currently participating project. Therefore, in the employee project participation history table 45, it is equal to EJ (= 1998122), and Records of which the date is after the participation start date and the current date is before the participation end date are acquired. Here, the record (project code “P01” in the employee project participation history table 45 of FIG.
101 ") to find and obtain.

In S34, the employee project participation history table 45 is searched for a record that is equal to the acquired project code (here, "P01101" and is not equal to EJ. Here, the employee of FIG. The record (employee code (1981031)) of the member project participation history table 45 is searched.

In step S35, the employee master 41 is searched for a record having the same employee code. here,
The employee master 41 of FIG. 18A on the right side is taken out.

S36 adds to the list.

In the case of YES at S32 above (when the current participating project is selected on the screen of FIG. 4), the process of the current participating project (project) of the person who is the center of the event is carried out at S33 to S36. All other employee codes with the same code) have been extracted and added to the notification list.

In S37, it is determined whether or not the past participating projects are to be notified. This determines whether the user who registered the event has selected "inside past project" in the notification target field on the event reception screen of FIG.
If YES, the persons involved in the past participating projects are added to the list through S38 to S41. On the other hand, NO
In the case of, the duplication of the list is deleted in S42 and the process ends.

In S38, it is determined that the notification is made in the past participating project of the person who becomes the center of the event in YES in S37. Therefore, in the employee project participation history table 45, it is equal to EJ (= 1998122), and Gets records whose date is after the end date of participation.
Here, the record (project code "P98001") of the employee project participation history table 45 of (e) of FIG. 18 is searched for and acquired.

In S39, the employee project participation history table 45 is searched for a record that is equal to the acquired project code (here, "P98001" and is not equal to EJ. Here, the employee of FIG. The record “employee code (1998124) in the member project participation history table 45 is searched.

In step S40, the employee master 41 is searched for a record having the same employee code. here,
The ″ of the employee master 41 of FIG. 18A on the right side is taken out.

S41 adds to the list.

In the case of YES at S37 above (when the past participating project is selected on the screen of FIG. 4), the past participating project (project of the person who is the center of the event) is selected at S38 to S41. All other employee codes with the same code) have been extracted and added to the notification list.

FIG. 7 shows an example of the notification destination confirmation screen of the present invention. The notification destination confirmation screen displays and confirms the following information shown in the figure.

-Employee code: -Name: -Event name: -Holding date: -Notification destination selection: Here, the employee code is entered by the user when logging in, and the name is based on the employee code. Is displayed with reference to the employee master 41. The event name is the name of the event entered by the user. To check the event information in the upper right, click the event information check to display detailed event information (event name, event date, reference information, comments, etc.). It In the notification destination selection, the list (list) of the notification destinations (related persons) automatically extracted in FIGS. Then, when the notification button is pressed, the event information is sent to the selected notification destination, such as a web page, an electronic mail, or a management file of the notification destination. It is displayed as a list shown in FIG. 9 described later.

FIG. 8 shows a notification event display flowchart of the present invention. This shows a detailed flow chart when displaying the notification event of FIG. 9 described later.

In FIG. 8, S51 displays the current date. here. January 22, 2002 is displayed as shown in the third line of the screen of FIG.

In step S52, the employee master 41 acquires a record having the same employee code as that input at the time of login. Here, the record (of the employee master 41 in (a) of FIG. 18) described on the right side is acquired.

In S53, the acquired employee code and name are displayed. As a result, the employee code: 1981031, the name: Suzune Toda is displayed in the fourth and fifth lines on the screen of FIG.

At S54, the record having the same employee code as that input at the time of login is acquired from the notification history table 26. Here, the notification history table 2 of FIG.
From the record of 6, get the following listed on the right.

Event management code: 1000502 Open flag: Not S55 searches the usage history table 26 for a record equal to the acquired event management code (here, “1000502”).

In step S56, the record of the response history table 27 that is equal to the employee code input at the time of login and the acquired event management code is acquired.

In S57, among the data acquired in the search A (S54), the data whose open flag is "not yet" is displayed in a list. "Not" is displayed at the beginning of the line. The event management code is embedded as hidden information in the link. As a result, the unopened list is displayed on the screen of FIG.

In S58, of the data acquired in the search A (S54), the open flag is "completed" and the search B (S5).
In 6), the data for which the corresponding record does not exist is displayed in the list. "Open" is displayed at the beginning of the line. The management record of the event is embedded as hidden information of the link. As a result, the opened list is displayed on the screen of FIG.

In S59, of the data acquired in the search A (S54), the open flag is "completed" and the search B (S5).
In 6), the data in which the corresponding record exists is displayed in a list. "Done" is displayed at the beginning of the line. The event management code is embedded as hidden information in the link. This allows
The answered list will be displayed on the screen of FIG.

FIG. 9 shows an example of the notification event screen of the present invention. The notification event screen shown in the figure is displayed according to the flow chart of FIG. 8 described above, and is a display of the notification event list in an easy-to-understand manner. In addition, one of the open (opened), which is not displayed, is displayed at the top to display a list of notification date, notifier, and event name.

FIG. 10 shows a flow chart of the answer input screen of the present invention. This is because when an arbitrary event is selected from the event list on the screen of FIG. 9 described above,
For example, it is a flowchart for displaying the answer input screen of FIG. 11 described later.

In FIG. 10, S61 changes the notification history table 26 to "completed" when the open flag of the code equal to the event management code is "not yet". This means that, for example, when the first event is selected from the event list on the screen of FIG. 9, the opening flag is “uncompleted” here, so it is changed to “completed”.

At S62, the current date is displayed.

In S63, the employee master 41 is executed. Get the record that is equal to the employee code entered at login. For example, it is acquired as described on the right side.

In step S64, the acquired employee code and name are displayed.

In step S65, a record having the same event management code as the usage history table 25 is acquired. Here, it is acquired as described on the right side from the usage history table 25 of FIG.

In step S66, the employee master 41 acquires a record having the acquired notification employee code. Here, it is acquired as described on the right side from the employee master 41 of FIG.

In S67, the employee master 41 obtains a record having the same other employee code as the notified recipient.
Here, it is acquired as described on the right side from the employee master 41 of FIG.

In S68, the acquired notification destination employee code and name, search condition employee code and name, event name, event holding date and time, and reference information are displayed. This is displayed as shown in FIG. 11 described later.

In S69, the comment column is displayed. This displays the comment column of FIG. 11 according to the flowchart of FIG. 12 described later.

In S70, the answer column is displayed. This displays the lower answer column (○ participation, ○ non-participation) on the screen of FIG.

At S71, the answer is input. This is answered from the screen of FIG. 11 on which the user is displayed (selection participation of ○ participation or ○ non-participation).

A step S72 decides whether or not to answer. If YES, the process proceeds to S73. In the case of NO, since the user has decided not to reply, the screen returns to the list screen (screen in FIG. 9).

At S73, it is determined whether or not to participate. It is determined whether the user has selected "○ participation" on the screen of FIG. Y
In the case of ES, a record is added to the response history table 27 as a participation (addition to the response history table 27 of FIG. 19C) in S74, and the process proceeds to S76. On the other hand, N in S73
In the case of O, since it has been determined that the participant has not participated, a record is added to the response history table 27 as a participant who did not participate, and the list screen (screen in FIG. 9) is returned to.

In S76, it is determined whether or not the payment is made. In the case of YES, the processing proceeds to the settlement processing (FIG. 13). In the case of NO, the screen returns to the list screen (FIG. 9).

As described above, when the user selects an event from the event list on the screen of FIG. 9, the screen of FIG. 11 is displayed, and when the user looks at the displayed event information and answers participation or non-participation, Records of participation and non-participation are added to the response history table 27 of FIG. 19C, and the response result is automatically saved.

FIG. 11 shows an example of the answer input screen of the present invention. This response input screen is automatically displayed when the user selects the event from the event list on the screen of FIG. 9 already described, and the user sees the event information and participates, decides not to participate, and answers (○) When one of "participation" and "non-participation" is selected and answered, it is automatically added and recorded as a record of participation and non-participation in the answer history table 27 of FIG. 19C.

FIG. 12 shows a comment column display flowchart of the present invention. This is a detailed flowchart of displaying the comment field on the answer input screen of FIG. 11 in S69 of FIG. 10 described above.

In FIG. 12, S81 acquires a record having the same event management code as the usage history table 25. For example, the usage history table 25 of FIG.
Get as described on the right from.

S82 is the employee affiliation history table 44.
In, obtain the record that is equal to the retrieved search condition employee code. For example, it is acquired as described on the right side from the employee affiliation history table 44 of FIG.

S83 is an employee affiliation history table 44.
Then, the record equal to the employee code input at the time of login and equal to the acquired affiliation code, before the acquired affiliation end date, and after the affiliation start date is acquired. For example, it is acquired as described on the right side from the employee affiliation history table 44 of FIG.

In S84, the belonging project installation history table 46 is used to obtain records having the same belonging codes, before the acquired ending date of the belonging, and after the income starting date of the belonging. For example, it is acquired as described on the right side from the belonging project installation history table 46 of (f) of FIG.

In S85, the employee project participation history table 45 is obtained, and a record equal to the retrieval condition employee code obtained in the retrieval A (S81) is obtained. For example, in FIG.
(E) is acquired from the employee project participation history table 45 as described on the right side.

S86 is the employee project participation history table 45, which is equal to the employee code input at the time of login, is equal to the acquired project code, is less than the acquired participation end date, and is the acquired participation start year. Fetch records after the date. For example, it is acquired as described on the right side from the employee project participation history table 45 of FIG.

In step S87, records belonging to the belonging project installation history table 46 that are equal to the acquired project code, before the acquired participation end date, and after the acquired participation start date are acquired. For example, it is acquired as described on the right side from the belonging project installation history table 46 of (f) of FIG.

In S88, the names acquired in the search B (S84) and the search C (S87) are added to the comment acquired in the search A (S81), and the comment is displayed on the screen. This is displayed as described on the right.

By the above procedure, the comment section of FIG. 11 described above is displayed.

FIG. 13 shows a flow chart of the screen of the settlement processing of the present invention. This is executed when it is determined in S76 of FIG. 10 described above that the payment is made.

In FIG. 13, S91 displays the current date. For example, the current date is displayed on the settlement processing screen of FIG. 15 described later.

In S92, the employee master 41 acquires a record having the same employee code as that input at the time of login. For example, it is acquired as described on the right side from the employee master 41 in FIG.

In S93, the acquired employee code and name are displayed. This displays the employee code and name acquired in S92 on the screen of FIG. 15, for example.

In S94, the usage history table 25 is used to acquire a record having the same event management code. For example, it is acquired as described on the right side from the usage history table 25 of FIG.

[0132] S95 displays the event name, the event date and time, and reference information. It is displayed as shown in FIG.

In step S96, the employee master 41 acquires a record having the acquired notification-destination employee code. For example, it is acquired from the employee master 41 of FIG. 19A as described on the right side.

In S97, the employee code and name of the acquired notifier (notification destination) are displayed. It is displayed as shown in FIG.

In S98, the employee master 41 obtains a record having the obtained retrieval condition employee code. For example, it is acquired as described on the right side from the employee master 41 in FIG.

In step S99, the employee code and name of the person who is the center of the acquired event are displayed. It is displayed as shown in FIG.

At step S100, the answer column is displayed.

In step S101, the deposit column is displayed.

In step S102, a record having the same type code as the acquired type information is acquired.
For example, it is acquired as described on the right side from the event-specific reference information list in FIG.

In step S103, the payment method options (selection) are displayed on the screen corresponding to the acquired payment method and designated value.

In S104 of FIG. 14, payment is designated. As described on the right side by the user, this is as follows: -Payment destination: -Payment amount: -Specify payment method.

In step S105, it is determined whether or not to deposit the money. Yes
In the case of, the payment history table 28 (see FIG.
(D)), data is added, the existing payment system cooperation processing is performed in S107, and the screen returns to the list screen (FIG. 9). On the other hand, S1
In the case of NO at 05, the screen returns to the list screen (FIG. 9).

By the above procedure, the settlement screen of FIG. 15 is displayed, and the user can select and input the payee, the deposit amount, and the payment method to make the settlement.

FIG. 15 shows an example of the payment screen of the present invention. The payment screen is displayed according to the flowcharts of FIGS. 13 and 14 described above. When the user looks at the contents displayed on the screen and makes a payment, the user pays in, the amount of payment, and the payment method. By selecting and inputting and pressing the deposit button, it becomes possible to easily perform the payment processing.

FIG. 16 shows an example of a participant list screen of the present invention. This is an example of a list screen of participants in the event, and is a list of response statuses (participation, non-participation, unanswered), which is displayed in a list (the answer history table of (c) of FIG. 19 described above). The number of participants and the number of non-participants in the response column of 27, and the number of persons (the number of people) who has excluded the number of participants and the number of non-participants from the number of notification destinations of the event in the notification history table 26 of FIG.

FIG. 17 shows an example of the notification list list of the present invention. Here, the following information shown in the figure is associated and registered and managed.

-Notification employee code: -Name: -Affiliation code: -Affiliation name: -Status (Answer: Participation, Non-participation, Unanswered):-Amount: -Notification: System, email address, etc.-Other : As described above, by managing the person related to the person who is the center of the event as a list of notifications, the individual status and totalized result of the notifiers in FIG. 16 described above can be accurately managed, and as necessary. It is possible to confirm it by displaying it on the screen.

FIG. 18 shows an example of the master / table of the present invention.

FIG. 18A shows an employee master example. The following information shown in the figure is registered and managed in the employee master 41 in association with each other.

-Employee code: -Name: -Affiliation code: -Contact: -Others: Here, the employee code is a unique identifier given to an employee of the company. The name is the employee's name. The affiliation code is the code of the department to which the employee belongs. The contact information is an email address, a contact information such as a telephone or FAX telephone number.

FIG. 18B shows an example of the belonging master.
The affiliation master 42 is for registering the affiliation name of the affiliation code.

FIG. 18C shows an example of the project master. The project master 43 is a project name registered in association with a project code.

FIG. 18D shows an example of an employee affiliation history table. The employee affiliation history table 44 is a record of past affiliation histories of employees, and here,
The following items are shown in correspondence with each other and registered.

-Employee code: -Affiliation code: -Affiliation start date: -Affiliation end date: -Others: Here, the employee code is registered in the employee master 41 of FIG. 18 (a). Employee code. The affiliation code is an affiliation code indicating the department to which the employee belongs.
From the start date of belonging to the end date of belonging, it is recorded that the member belongs to the department of the belonging code of the entry.

FIG. 18E shows an example of an employee project participation history table. The employee project participation history table 45 is a table in which the project code of the project to which the employee currently belongs, the start date of participation, and the end date of participation are registered in association with each other.

FIG. 18F shows an example of the affiliation / project installation history table. The affiliation / project installation history table 46 is a table in which the affiliation and the project installation history are associated and registered with the following information shown in the figure.

DP code: ·name: ・ Installation start date: ・ Installation end date: FIG. 19 shows an example table / list of the present invention.

FIG. 19A shows an example of the usage history table. The usage history table 25 is a table in which the following information shown in the figure is associated and registered.

-Management code: -Usage date: -Notifier (notification destination) employee code: -Search condition employee code: -Notification target code: -Type code: -Event name: -Event date: -Reference information : -Comment: Here, the management code is a unique code for managing the event, and the usage date is the usage date (current date). The notifier employee code is the employee code of the registered employee. The search condition employee code is the employee code of the person who is the center of the event. The notification target code is a code representing the notification target. The type code is a code indicating the event type. The event name is an easy-to-understand name of the event. The event date is the date and time when the event is held. The reference information is information that serves as a reference for the event. The comment is a comment for the event.

FIG. 19B shows an example of the notification history table. The notification history table 26 is the history of the notified person who has notified the event, and is the one in which the following information shown in the figure is registered.

Notification number: Notification destination employee code: Event management code: Open flag: Here, the notification number is a unique, for example, sequential number when the event is notified. The notified employee code is the code of the employee who notified the event. The event management code is a management code of the event notified to the notified employee. The open flag has not been set when the employee to be notified is unopened, it has been set when opened, and the person outside the system is blank.

FIG. 19C shows an example of the answer history table. The response history table 27 stores the response history, and is registered in association with the following information shown in the figure.

Response number: Response date: Respondent employee code: Event management code: Response: Here, the response number is a unique sequential number assigned to the response. The answer date is the day when there was an answer. The respondent employee code is the employee code that responded. The event management code is the management code of the event for which there is a response. The answer is whether to attend the event or not.

FIG. 19D shows an example of the settlement history table. The payment history table 28 is information in which the payment of the participation fee for the event has been registered in association with each other, and here, the following information shown in the figure is associated and registered.

-Payment number: -Usage date: -Payer employee code: -Recipient employee code: -Amount: -Transfer destination: -Event management code: Here, the settlement number is the unique number that was settled . The payer employee code is the employee code of the employee who paid the participation fee for the event. The payee employee code is the employee code of the received employee. The amount is the amount paid. The transfer destination is where the amount is transferred. The event management code is the management code of the event that paid the cost.

FIG. 19E shows an example of the search condition list. The search condition list is a list of search condition display sentences registered in association with the notification target code. Here, the search target code is the usage history table 2 of FIG.
It is a code set in the notification target code column 5 and, for example, "01" is a code for searching within the current department. Each of these notification target codes is AND or O
It can be described logically in R.

FIG. 19F shows an example of the reference information list for each event. The event-specific reference information list is a list of event names, payment method designation fields, and reference information associated with the type codes as shown in the figure.

FIG. 19G shows an example of a company-wide common authentication table. The company-wide common authentication table is for authenticating employees by registering a password in association with an employee code input by an employee when logging in.

(Supplementary Note 1) In the event support method of presenting a list of contact persons for an event, I
A master in which at least name and affiliation information is registered in association with D is provided, and in response to the input of the ID or the name of the person who is the center of the event, the ID of the master concerned
Alternatively, a step of extracting the affiliation information corresponding to the name and extracting another name and ID of the affiliation information that is the same or similar if necessary, and the extracted name and the required affiliation information. ID extracted accordingly
And a step of presenting the above list as a contact target list.

(Supplementary Note 2) The event support method according to Supplementary Note 1, wherein the affiliation information is current and past affiliation information.

(Supplementary Note 3) The event support method according to Supplementary Note 1, wherein the affiliation information is present and past affiliation information and a period of time belonging to the affiliation information.

(Supplementary Note 4) Event information, a response column indicating whether or not participation has been made, and a response column indicating the participation fee and payment method, as necessary, for all contact persons or designated contact persons in the contact person list above. 4. The event support method according to any one of appendices 1 to 3, which has a step of transmitting or accessing electronic data set with, and recording the completion when the electronic data is transmitted or accessed.

(Supplementary note 5) When the reply is received from the contact person, the answer column of the corresponding person has been received from the list of contact persons, whether or not to participate in the participation column, and payment to the participation cost column as necessary. 5. The event assistance method according to appendix 4, comprising the step of recording the method.

(Appendix 6) The answer column, the participation column,
And the event support method described in appendix 5, which has a step of totalizing information in the participation cost column to create and present a list as necessary.

(Supplementary Note 7) In an event support program for presenting a list of contact persons for an event, a master in which at least name and affiliation information is registered in association with the ID of the contact person is provided, and the person who becomes the center of the event is described above. In response to the input of the ID or name, belonging information corresponding to the ID or name is extracted from the master, and the extracted belonging information is the same or, if necessary, another name of similar belonging information and if necessary. And an ID support program for causing the computer to function as a step of presenting the extracted name and a list of the extracted ID as necessary as a contact person list.

(Supplementary Note 8) In the event support device that presents a list of contact persons for the event, I
A master in which at least name and affiliation information is registered in association with D, and affiliation information corresponding to the ID or name is extracted from the master in response to input of the ID or name of the person who is the center of the event. The contact target person is a means for extracting other names and IDs of the belonging information which are the same or similar if necessary, and the list of the extracted names and the extracted IDs as necessary. An event support device, comprising: means for presenting as a list.

(Supplementary Note 9) A computer-readable recording medium recording an event support program for presenting a list of contact persons for an event is provided with a master in which at least name and affiliation information is registered in association with the ID of the contact person. In response to the input of the ID or name of the person who is the center of the event, the affiliation information corresponding to the ID or name is extracted from the master, and the extracted affiliation information is the same or similar affiliation as necessary. Extracting the other name of the information and the ID if necessary,
A computer-readable recording medium recording a program that functions as a step of presenting the extracted name and a list of IDs extracted as necessary as a contact person list.

[0178]

As described above, according to the present invention,
When the event information is registered, the personnel information database 4 and the like are searched to automatically extract contacts related to the event information, which are related to the present and the past, and present a list, so that the contact information can be completely removed. Since we have adopted a configuration that informs related parties of event information, presence / absence of participation, costs, etc. and collects responses and payment of costs, we will create and deliver a list of all contacts at the event and deliver it.
After receiving the answers, participants and non-participants are automatically tabulated and presented to eliminate the manual work of the secretary.

[Brief description of drawings]

FIG. 1 is a system configuration diagram of the present invention.

FIG. 2 is an explanatory diagram of the present invention.

FIG. 3 is an explanatory diagram (event registration) of the present invention.

FIG. 4 is an example of an event reception screen of the present invention.

FIG. 5 is an explanatory diagram of the present invention (notification destination search, part 1).

FIG. 6 is an explanatory diagram of the present invention (notification destination search, part 2).

FIG. 7 is an example of a notification destination confirmation screen of the present invention.

FIG. 8 is a notification event display flowchart of the present invention.

FIG. 9 is an example of a notification event screen of the present invention.

FIG. 10 is a flowchart of an answer input screen of the present invention.

FIG. 11 is an example of an answer input screen of the present invention.

FIG. 12 is a comment column display flowchart of the present invention.

FIG. 13 is a flowchart (No. 1) of the payment processing screen of the present invention.

FIG. 14 is a flowchart (No. 2) of the payment processing screen of the present invention.

FIG. 15 is an example of a payment screen of the present invention.

FIG. 16 is an example of a participant list screen of the present invention.

FIG. 17 is an example of a notification list list of the present invention.

FIG. 18 is an example of a master / table of the present invention.

FIG. 19 is an example table / list of the present invention.

[Explanation of symbols]

1: Server 2: Event office system 21: Event reception program 22: Notification destination search program 23: Event payment program 24: Participant confirmation program 25: Usage history table 26: Notification history table 27: Answer history table 28: Payment history table 29: Payroll transfer system 30: Expense payment system 31: Map search system 4: Personnel information database 41: Employee master 42: Affiliation master 43: Project master 44: Employee affiliation history table 45: Employee project participation history table 46: Affiliated project installation history table 5: Network 6: User terminal

Claims (3)

[Claims] 1. An event support method for presenting a list of contact persons for an event, wherein a master in which at least name and affiliation information is registered in association with the ID of the person to be contacted is provided, and the ID of the person who is the center of the event or Corresponding to the input of the name, the belonging information corresponding to the ID or the name is extracted from the master, and the extracted belonging information is the same or, if necessary, the other name of the similar belonging information and the ID if necessary. And a step of presenting a list of the extracted names and, if necessary, the extracted IDs as a contact target person list. 2. The event support method according to claim 1, wherein the affiliation information is current and past affiliation information. 3. An event support program for presenting a list of contact persons for an event, wherein a master in which at least name and affiliation information is registered in association with the ID of the person to be contacted is provided, and the ID of the person who becomes the center of the event or Corresponding to the input of the name, the belonging information corresponding to the ID or the name is extracted from the master, and the extracted belonging information is the same or, if necessary, the other name of the similar belonging information and the ID if necessary. And an event support program for causing a computer to function as a step of presenting the extracted name and a list of IDs extracted as necessary as a contact target person list.