JP4004829B2 - Event support method and event support program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an event support method and an event support program for presenting a list of event contacts.
[0002]
[Prior art]
Conventionally, in the case of an event such as a ceremonial occasion at the workplace, for example, “Mr. A's wedding”, a person who is the organizer of a friend who is the organizer of the event is extracted and a document is prepared and sent. Ask for participation, send an email to request participation, talk about the situation and ask for participation, if you need participation fee, collect the participation fee individually, secretary I had you transfer it to my account, and I managed the collected and transferred individually.
[0003]
[Problems to be solved by the invention]
For this reason, the event organizer creates a list of contacts to be contacted in connection with the event, sends the event document to the contact, receives an answer of participation / non-participation, collects the expenses. It is necessary to manage each of them individually, etc., which is extremely difficult, sometimes causes troubles such as leakage of related parties in the past, and takes a lot of time. there were.
[0004]
In order to solve these problems, the present invention eliminates the possibility of registering event information, searching the master, and automatically extracting contacts related to the event information in the past and presenting a list. Communicate event information, presence / absence of participation, expenses, etc. to related parties via web page or e-mail, etc., receive and aggregate payment of responses and expenses, create and distribute all contact lists for the event, and send responses The purpose is to automatically collect and present participants and non-participants and eliminate the manual work of the secretary.
[0005]
[Means for Solving the Problems]
Means for solving the problem will be described with reference to FIG.
[0006]
In FIG. 1, a server 1 performs various processes according to a program, and includes an event office system 2 and a personnel information database 4.
[0007]
The event office system 2 refers to the personnel information database 4 and presents a list of contacts for the event.
[0008]
The personnel information database 4 is a database in which names, past and present affiliation information, and the like are registered in association with IDs of contact persons (for example, employees).
[0009]
Next, the operation will be described.
[0010]
The event office system 2 extracts the affiliation information corresponding to the ID or name from the personnel information database 4 in response to the input of the ID or name of the person who will be the center of the event, and the extracted affiliation information is the same or as necessary Thus, other names and IDs of similar affiliation information are extracted, and a list of the extracted names and IDs is presented as a contact person list.
[0011]
At this time, the affiliation information is current and past affiliation information.
[0012]
In addition, the affiliation information includes current and past affiliation information and a period of belonging to the affiliation information.
[0013]
In addition, electronic data with event information, a reply column for participation status, and a reply field for participation fee and payment method as necessary is sent to all contact persons in the list of contact persons or the specified contact person. Send or access, and record when finished sending or accessing.
[0014]
In addition, when receiving a response from the contact person, the response field of the corresponding person has been received from the contact person list, whether or not to participate in the participation field, and if necessary, record the payment method in the participation cost field. ing.
[0015]
In addition, the recorded answer field, participation field, and information on the participation cost field as necessary are compiled and presented as a list.
[0016]
Therefore, when event information is registered, the personnel information database 4 is searched and contacts related to the event information are automatically extracted in the past, and a list is displayed. The event information, presence / absence of participation, costs, etc. are communicated to the respondents, and the responses and expenses are paid and aggregated. Non-participants can be automatically tabulated and presented, eliminating the traditional secretary's manual work.
[0017]
DETAILED DESCRIPTION OF THE INVENTION
Next, embodiments and operations of the present invention will be described in detail sequentially with reference to FIGS.
[0018]
FIG. 1 shows a system configuration diagram of the present invention.
[0019]
In FIG. 1, a server 1 loads a program read from an external storage device or a recording medium into a main memory, starts it, and performs various processes. Here, an event office system 2 and a personnel information database 4 are used. It is comprised from.
[0020]
The event office system 2 refers to the table and the personnel information database 4 and presents a list of contacts for the event, and is composed of 21 to 28 and the like.
[0021]
The event reception program 21 receives events.
[0022]
The notification destination search program 22 searches the personnel information database 4 and the like for related persons (notification destinations) for the received event, and creates a contact list.
[0023]
The event settlement program 22 settles event participation fees and the like.
[0024]
The participant confirmation program 24 confirms the participation and non-participation of the participant.
[0025]
The usage history table 25 manages the user history (see FIG. 19A).
[0026]
The notification history table 26 manages the notified history (see S in FIG. 19B).
[0027]
The answer history table 27 manages the answer history (see (c) of FIG. 19).
[0028]
The settlement history table 28 manages settlement history of participants and the like (see (d) of FIG. 19).
[0029]
The salary transfer system 29 manages the transfer of employee salaries, and here, the participation fee for the event is deducted from the salary.
[0030]
The expense settlement system 30 settles various company expenses.
[0031]
The map search system 31 is a map search system such as a road to a customer.
[0032]
The personnel information database 4 is various personnel databases in the company, and is composed of 41 to 46 and the like here.
[0033]
The employee master 41 is registered with a name, affiliation code, contact information, etc. in association with an employee ID (employee code) of the company (see (a) of FIG. 18).
[0034]
The affiliation master 42 is a affiliation name registered in association with an affiliation code (see FIG. 18B).
[0035]
The project master 43 is a project name registered in association with a project code (see FIG. 18B).
[0036]
The employee affiliation history table 44 is registered with an affiliation code, an affiliation code, a affiliation start date of affiliation in the past, an affiliation end date, and the like (see FIG. 18D). .
[0037]
The employee project participation history table 45 is a table in which project codes, past affiliation start dates, affiliation end dates, etc. are registered in association with employee codes (see (e) of FIG. 18). ).
[0038]
The affiliation project setting history table 46 registers names, installation start dates, installation end dates, etc. in association with codes (see (f) of FIG. 18).
[0039]
The network 5 connects the server 1 and many user terminals 6.
[0040]
The user terminal 6 registers events in the server 1 or receives event information and the like from the server 1 via Web pages or e-mails.
[0041]
Details will be sequentially described below.
[0042]
FIG. 2 is an explanatory diagram of the present invention.
[0043]
FIG. 2A shows a flowchart.
[0044]
In FIG. 2A, S1 logs in. This is because the user operates the user terminal 6 in FIG. 1 to display a login screen of the event office system 2 in FIG.
・ Employee code:
·password:
, Press the execution button, refer to the company-wide common password table in FIG. 19G held by the event office system 2, and check whether it is a registered employee code and password. Personal authentication is performed, and if OK, the process proceeds to the next S2. In the case of NO, S1 is repeated a predetermined number of times. If it exceeds the predetermined number of times, a code or password error message is displayed and the process is terminated.
[0045]
S3 displays a menu screen. For example, the menu screen of the event office system shown in FIG. Here, the employee code input in FIG. 2B, the name retrieved from the employee master 41 in FIG. 18A based on the employee code, and the event menu in the lower row are displayed. indicate.
[0046]
In S4, a menu is selected. Here, it is displayed on the menu screen of FIG.
1. Event registration
2. Event reference / settlement
3. Participant confirmation
In response to the selection, the process proceeds to an event registration process in S4, an event reference / settlement process in S5, or a participant confirmation process in S6, which will be described later.
[0047]
In S7, it is determined whether or not the process is finished. If YES, the process ends. If NO, the menu screen of S2 is displayed and repeated.
[0048]
FIG. 2B shows an example of a login screen. This login screen is an example of a login screen that is displayed when a user operates the user terminal 6 to log in to the event office system 2. Here, the following information shown in FIG. Press to send.
[0049]
・ Employee code:
·password:
Various functions of the event office system 2 can be used when the user operates the user terminal 6 on the above login screen, inputs the employee code and password, and collates them. Then, it becomes possible to register events.
[0050]
FIG. 2C shows an example of a menu screen. This menu screen is used to select a process to be performed by the user using the event office system 2, and here, one of the following three shown in the figure is selected.
[0051]
1. Event registration
2. Event reference / settlement
3. Participant confirmation
FIG. 3 is an explanatory diagram (event registration) of the present invention. This is a process when the event registration process is selected on the menu screen in S5 of FIG.
[0052]
In FIG. 3, S11 accepts an event. This is because the user operates the user terminal 6, accesses the event office system 2, downloads and displays an event reception screen shown in FIG. 4 to be described later, and inputs necessary information such as an event type from the screen. Then, the registration button is pressed and uploaded to the event office system 2 in FIG. 1, and the event office system 2 accepts the event.
[0053]
In S12, a notification destination is searched. According to the flowcharts of FIGS. 5 and 6 described later, this searches for the notifier of the event accepted in S11 and creates a list of notifiers.
[0054]
In step S13, the notification destination is confirmed. This is confirmed by displaying the notification destination searched in S12 on the screen of FIG.
[0055]
S14 notifies. In this case, event information is notified to the notification destination (notifier) after confirmation in S13, for example, notification is made by a Web page or e-mail.
[0056]
FIG. 4 shows an example of an event reception screen of the present invention. This is an example of the event reception screen that the user accesses the event office system 2 by operating the user terminal 6 and downloads and displays it on the display device of the user terminal 6 in S11 of FIG. Here, the following information shown in the figure is displayed.
[0057]
・ Employee code:
·Full name :
・ Person to be notified:
□ Current department:
□ In the past department:
□ Currently participating projects:
□ In the past participating projects:
・ Event type: Wedding
・ Event name: Takashi Saito's wedding
・ Date: February 11, 2002, 2pm
・ Reference information: "XX life survey average" boss 50000 yen, colleagues 30000 yen
・ Comment: The place is ○○.
[0058]
Please see: http: // ... for the map.
[0059]
Here, the employee code is displayed as it is the employee code entered at the time of login, and the name is displayed by referring to the employee master 41 of FIG. 18A based on the employee code. It is a thing. One or more of the current department, the past department, the current participating project, and the past participating project displayed in the notification target person column are selected 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 an event type to be registered, and here is a wedding. The event name is the name of the event. For the date and time, reference information, and comments, enter the event name that the registrant thinks appropriate for the event.
[0060]
When event information is input on the event registration screen described above and the registration button is pressed, it is uploaded to the event office system 2 in FIG. 1 and registered and accepted.
[0061]
5 and 6 are diagrams for explaining the operation (notification destination search) of the present invention. This shows a detailed explanatory view of S12 of FIG. 3 described above.
[0062]
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.
[0063]
・ Employee code:
·Full name:
·contact information:
In S22, the employee code of the person who becomes the center of the event is stored in the variable EJ (here, the employee code “1998121” (Hitomi Saito) of the person who becomes the center of the event on the screen of FIG. 4 is changed to the variable EJ. To store).
[0064]
In step S23, it is determined whether the current department is a notification target. This is to determine whether the user who registered the event has selected “within current department” in the notification target column on the event reception screen of FIG. In the case of YES, the parties belonging to the current affiliation are added to the list through S24 to S26. On the other hand, if NO, the process skips to S27.
[0065]
In S24, since YES in S23, it became clear that the current department of the person who is the center of the event is the notification destination, the employee master 41 obtains a record equal to EJ (= 1998122). Here, the record (1) of the employee master 41 in FIG. 18 (a) is searched and found and acquired.
[0066]
S25 searches the employee master for a record that is equal to the affiliation code of the acquired record (here, “1001”) and whose employee code is not equal to EJ. Here, the employee code of the record that is equal to the affiliation code “1011” of the record (1) of the employee master 41 in FIG.
・ 1981031
・ 1998121
Take out the two.
[0067]
S26 is added to the list. In this example, two employee codes extracted in S25 are added to the list (notification destination list).
[0068]
In the case of YES in S23 described above (when the current department is selected on the screen of FIG. 4), the current affiliation (affiliation code) of the person who is the center of the event is determined from S24 to S26. All the same other employee codes can be extracted and added to the notification list.
[0069]
In S27, as in S23, it is determined whether the past department is to be notified. This is to determine whether the user who registered the event has selected “in the past department” in the notification target field on the event reception screen in FIG. In the case of YES, the past affiliated persons are added to the list through S28 to S31. On the other hand, if NO, the process skips to S32 in FIG.
[0070]
S28 is YES in S27, and it has been found that the past department of the person who is the center of the event is the notification destination, so in the employee affiliation history table 44, it is equal to EJ (= 1998122) and the current date belongs. Get records after end date. For example, among the records of the employee code equal to EJ of (2) in the employee affiliation history table 44 of FIG. 18 (d) to be described later, as the record whose current date is after the affiliation end date, (3) Get the record described on the right side of.
[0071]
S29 is the employee affiliation history table 44, which is equal to the acquired affiliation code (“1002” in the example of (3)), and the affiliation start date is before the acquired affiliation end date, and the affiliation end A record in which the date is after the acquired affiliation start date and the employee code is not equal to EL is retrieved. Here, (4) (employee code “1998123” described on the right side is searched as the employee code of (4) in the employee affiliation history table 44 in FIG. 18 (d) (affiliation code “1002” is equal). As search).
[0072]
In S30, the employee master 41 searches for a record equal to the employee code acquired in S29. Here, the search is performed as in (5) described on the right side.
Is done.
[0073]
S31 is added to the list. This adds the record extracted in S30 to the list (notification destination list).
[0074]
In the case of YES in S27 described above (when the past department is selected on the screen of FIG. 4), the past affiliation (affiliation code) of the person who becomes the center of the event is determined from S28 to S31. All the same other employee codes can be extracted and added to the notification list.
[0075]
In S32, it is determined whether the current participating project and the inside are to be notified. This is to determine whether the user who registered the event has selected “in current participating project” in the notification target column on the event reception screen in FIG. If YES, the parties involved in the current participating project are added to the list through S33 to S36. On the other hand, if NO, the process skips to S37.
[0076]
S33 is YES in S32 and it has been found that the current participation project of the person who will be the center of the event is the notification destination, so in the employee project participation history table 45, it is equal to EJ (= 1998122) and the current date is The record after the start date of participation and the current date before the end date of participation is acquired. Here, the record (6) (project code “P01101”) in the employee project participation history table 45 in FIG. 18E is searched for and obtained.
[0077]
S34 searches the employee project participation history table 45 for a record that is the same as the acquired project code (here, “P01101” and not equal to EJ. Here, the employee project participation in FIG. 18E). The record (7) (employee code (1981031)) of the history table 45 is searched.
[0078]
S35 searches the employee master 41 for a record equal to the acquired employee code. Here, (8) of the employee master 41 in FIG.
[0079]
S36 is added to the list.
[0080]
In the case of YES in S32 above (when the current participation project is selected on the screen of FIG. 4), the current participation project (project code) of the person who will be the center of the event is obtained from S33 to S36. All the same other employee codes can be extracted and added to the notification list.
[0081]
In S37, it is determined whether the past participating projects and the inside are to be notified. This is to determine whether the user who registered the event has selected “in the past participating projects” in the notification target column on the event reception screen in FIG. In the case of YES, the parties related to the past participating projects are added to the list through S38 to S41. On the other hand, in the case of NO, the duplication of the list is deleted in S42 and the process is terminated.
[0082]
S38 is determined to be the notification destination in the past participation project of the person who will be the center of the event in YES of S37, so in the employee project participation history table 45, the current date is equal to EJ (= 1998122). Get records after the end date of participation. Here, the record (9) (project code “P98001”) in the employee project participation history table 45 in FIG. 18E is searched for and obtained.
[0083]
S39 searches the employee project participation history table 45 for a record that is equal to the acquired project code (here, “P98001” and not equal to EJ. Here, the employee project participation in FIG. 18E). The record (9) '(employee code (1998124)) of the history table 45 is searched.
[0084]
In S40, the employee master 41 searches for a record equal to the acquired employee code. Here, (9) '' of the employee master 41 in FIG.
[0085]
S41 is added to the list.
[0086]
In the case of the above S37 YES (when the past participation project is selected on the screen of FIG. 4), the past participation project (project code) of the person who will be the center of the event is obtained from S38 to S41. All the same other employee codes can be extracted and added to the notification list.
[0087]
FIG. 7 shows an example of a notification destination confirmation screen of the present invention. The notification destination confirmation screen displays and confirms the following information shown in the figure.
[0088]
・ Employee code:
·Full name:
・ Event name:
・ Date and time:
-Notification destination selection:
Here, the employee code is input by the user at the time of login, and the name is displayed by referring to the employee master 41 based on the employee code. The event name is the name of the event entered by the user, and the event information confirmation in the upper right corner displays the linked event details information (event name, date and time, reference information, comments, etc.) when the event information confirmation is clicked. The In the notification destination selection, a list (list) of notification destinations (related parties) automatically extracted in FIG. 5 and FIG. When the notification button is pressed, event information is sent to the selected notification destination to a Web page, an e-mail, or a notification destination management file. It is displayed as a list shown in FIG.
[0089]
FIG. 8 shows a notification event display flowchart of the present invention. This shows a detailed flowchart when the notification event of FIG. 9 described later is displayed.
[0090]
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.
[0091]
In S52, the employee master 41 obtains a record equal to the employee code input at the time of login. Here, the record of (8) ((8) of the employee master 41 in FIG. 18A) described on the right side is acquired.
[0092]
In step S53, the acquired employee code and name are displayed. As a result, the fourth and fifth lines on the screen of FIG.
・ Employee code: 1981031
・ Name: Suzune Toda
Is displayed.
[0093]
S54 acquires a record equal to the employee code input at the time of login in the notification history table 26. Here, the following items described on the right side are acquired from the record (1) in the notification history table 26 of FIG.
[0094]
Event management code: 1000502
・ Opening flag: Not yet
S55 searches the usage history table 26 for a record that is equal to the acquired event management code (here, “1000502”).
[0095]
In S56, a record that is equal to the employee code input at the time of login and equal to the acquired event management code is acquired in the answer history table 27.
[0096]
In S57, the data with the unsealed flag “not yet” among the data acquired in the search A (S54) is displayed in a list. “Not yet” is displayed at the beginning of the line. Embed event management code as hidden link information. As a result, the unopened list is displayed on the screen of FIG.
[0097]
S58 displays in the list the data that has been opened in the search A (S54) and the opening flag is “completed” and no corresponding record exists in the search B (S56). “Open” is displayed at the beginning of the line. Embed event management records as hidden link information. As a result, the opened list is displayed on the screen of FIG.
[0098]
S59 displays a list of data that has been opened in the search A (S54) and that has the open flag and the corresponding record exists in the search B (S56). Display "Done" at the beginning of the line. Embed event management code as hidden link information. As a result, the answered list is displayed on the screen of FIG.
[0099]
FIG. 9 shows an example of a notification event screen of the present invention. The notification event screen shown in FIG. 8 is displayed according to the flowchart of FIG. 8 described above, and the notification event list is displayed in an easy-to-understand manner. In addition, a list of the notification date, the notification person, and the event name is displayed by displaying either “open” (opened), which is not displayed, at the top.
[0100]
FIG. 10 shows a flowchart of the answer input screen of the present invention. This is a flowchart for displaying, for example, an answer input screen shown in FIG. 11 described later when an arbitrary event is selected from the event list on the screen shown in FIG.
[0101]
In FIG. 10, S61 is changed to “Done” when the opening flag of the code equal to the event management code is “not yet” in the notification history table 26. For example, when the first event is selected from the event list on the screen of FIG. 9, the opening flag is “not yet” here, so that it is changed to “done”.
[0102]
S62 displays the current date.
[0103]
S63 is the employee master 41. Get a record equal to the employee code entered at login. For example, as described on the right side.
[0104]
S64 displays the acquired employee code and name.
[0105]
In S65, the usage history table 25 acquires a record equal to the event management code. In this case, the information is acquired from the usage history table 25 in FIG.
[0106]
In S66, the employee master 41 acquires a record equal to the acquired notification employee code. Here, it acquires from the employee master 41 of FIG. 18A as described on the right side.
[0107]
In S67, the employee master 41 acquires a record that is equal to the other acquired notification destination employee code. Here, it acquires from the employee master 41 of FIG. 18A as described on the right side.
[0108]
S68 displays the acquired notification destination employee code and name, search condition employee code and name, event name, event date and time, and reference information. This is displayed as shown in FIG.
[0109]
In S69, a comment column is displayed. This displays the comment field of FIG. 11 according to the flowchart of FIG.
[0110]
S70 displays an answer column. This displays the answer column (○ participation, ○ non-participation) at the bottom of the screen of FIG.
[0111]
In S71, an answer is input. This is answered from the screen shown in FIG. 11 on which the user is displayed (selected answer of either ○ participation or ○ non-participation).
[0112]
In S72, it is determined whether to answer. If YES, the process proceeds to S73. In the case of NO, since the user has decided not to answer, the screen returns to the list screen (screen of FIG. 9).
[0113]
In S73, it is determined whether or not to participate. It is determined whether or not the user has selected “Join” on the screen of FIG. In the case of YES, a record is added as a participation in the answer history table 27 in S74 (added to the answer history table 27 in FIG. 19C), and the process proceeds to S76. On the other hand, in the case of NO in S73, since it has been determined that it has not participated, in S75, a record is added to the answer history table 27 as non-participating, and the screen returns to the list screen (screen of FIG. 9).
[0114]
In S76, it is determined whether or not to settle. In the case of YES, the process proceeds to the settlement process (FIG. 13). In the case of NO, the screen returns to the list screen (FIG. 9).
[0115]
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. When the user views the displayed event information and answers participation or non-participation, FIG. The record of participation / non-participation is added to the response history table 27 of (c), and the response result is automatically saved.
[0116]
FIG. 11 shows an example of an answer input screen according to the present invention. This answer input screen is automatically displayed when the event list on the screen of FIG. 9 described by the user selects an event, and the user decides whether to participate or not participate by looking at the event information. When one of “participation” and “non-participation” is selected and answered, it is automatically added to the answer history table 27 of FIG. 19C as a participation / non-participation record and automatically recorded.
[0117]
FIG. 12 shows a comment column display flowchart of the present invention. This is a detailed flowchart for displaying the comment field on the answer input screen of FIG. 11 in S69 of FIG.
[0118]
In FIG. 12, S81 acquires a record equal to the event management code in the usage history table 25. For example, it is acquired from the usage history table 25 of FIG.
[0119]
S82 acquires a record equal to the acquired search condition employee code in the employee affiliation history table 44. For example, the information is acquired from the employee affiliation history table 44 in FIG.
[0120]
S83 is the employee affiliation history table 44. Records that are equal to the employee code input at the time of login, equal to the acquired affiliation code, and before the acquired affiliation end date and after the affiliation start date are recorded. get. For example, the information is acquired from the employee affiliation history table 44 in FIG.
[0121]
In S84, in the affiliation project installation history table 46, the acquired affiliation codes are equal, and the records before the acquired affiliation end date and after the acquired affiliation start date are acquired. For example, it is acquired from the affiliated project installation history table 46 of FIG.
[0122]
S85 acquires a record equal to the search condition employee code acquired in the search A (S81) in the employee project participation history table 45. For example, it is acquired from the employee project participation history table 45 in FIG.
[0123]
S86 is an employee project participation history table 45 that is equal to the employee code entered at the time of login, equal to the acquired project code, and before the acquired participation end date and after the acquired participation start date. Get the record. For example, it is acquired from the employee project participation history table 45 in FIG.
[0124]
S87 acquires a record in the affiliated project installation history table 46 that is equal to the acquired project code, is before the acquired participation end date, and after the acquired participation start date. For example, it is acquired from the affiliated project installation history table 46 of FIG.
[0125]
In S88, the names acquired in Search B (S84) and Search C (S87) are added to the comment acquired in Search A (S81) and displayed on the screen. This is displayed as described on the right.
[0126]
With the above procedure, the comment field of FIG. 11 described above is displayed.
[0127]
FIG. 13 shows a flowchart of the settlement processing screen of the present invention. This is executed when it is determined that the settlement is made in the above-described YES in S76 of FIG.
[0128]
In FIG. 13, S91 displays the current date. For example, the current date is displayed on the settlement processing screen of FIG.
[0129]
In S92, the employee master 41 obtains a record equal to the employee code input at the time of login. For example, it is acquired from the employee master 41 in FIG.
[0130]
S93 displays the acquired employee code and name. For example, the employee code and name acquired in S92 are displayed on the screen of FIG.
[0131]
In S94, a record equal to the event management code is acquired in the usage history table 25. For example, it is acquired from the usage history table 25 of FIG.
[0132]
S95 displays the event name, the event date and time, and reference information. Displayed as shown in FIG.
[0133]
In S96, the employee master 41 acquires a record equal to the acquired notification destination employee code. For example, it is acquired from the employee master 41 of FIG.
[0134]
S97 displays the employee code and name of the acquired notifier (notification destination). Displayed as shown in FIG.
[0135]
In S98, the employee master 41 acquires a record equal to the acquired search condition employee code. For example, it is acquired from the employee master 41 in FIG.
[0136]
S99 displays the employee code and name of the person who will be the center of the acquired event. Displayed as shown in FIG.
[0137]
In step S100, an answer column is displayed.
[0138]
S101 displays a deposit column.
[0139]
S102 acquires a record equal to the acquired type code in the event-specific reference information list. For example, it is acquired from the event-specific reference information list shown in FIG.
[0140]
In step S103, payment method options (selection options) are displayed on a screen corresponding to the acquired payment method and a specified value.
[0141]
In S104 of FIG. 14, payment is designated. This is because, as the user wrote on the right side,
・ Payment destination:
・ Payment amount:
·Payment Method
Is specified.
[0142]
In S105, it is determined whether or not to deposit. In the case of YES, data is added to the settlement history table 28 ((d) in FIG. 19) in S106, the existing settlement system linkage processing is performed in S107, and the list screen (FIG. 9) is returned. On the other hand, in the case of NO in S105, the screen returns to the list screen (FIG. 9).
[0143]
The settlement screen of FIG. 15 is displayed by the above procedure, and the user can make a settlement by selecting and inputting a deposit destination, a deposit amount, and a payment method.
[0144]
FIG. 15 shows an example of a settlement screen of the present invention. The settlement screen is displayed in accordance with the flowcharts of FIGS. 13 and 14 described above. When the settlement is made by looking at the contents displayed on the screen, the user pays the deposit destination, the deposit amount, and the payment method. It is possible to easily perform a settlement process by selecting and inputting and pressing the deposit button.
[0145]
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, which is a list of the response status (participation, non-participation, unanswered) (list of response histories shown in FIG. 19C described above). 27, the number of participation and non-participation in the answer column, and the number of persons (number of persons) who exclude the number of participation and non-participation from the notification destination number of the event in the notification history table 26 of FIG.
[0146]
FIG. 17 shows a notification list list example of the present invention. Here, the following information shown is registered and managed in association with each other.
[0147]
-Notification employee code:
·Full name:
・ Affiliation code:
・ Affiliation name:
・ Status (answer: participation, non-participation, unanswered):
·Amount of money:
-Notification destination: System, e-mail address, etc.
・ Other:
As described above, by managing the person related to the person who is the center of the event as a notification list, it is possible to accurately manage the individual situation and the total result of the above-described notifier of FIG. 16 and display the screen as necessary. It is possible to confirm it by displaying it above.
[0148]
FIG. 18 shows an example of a master / table of the present invention.
[0149]
FIG. 18A shows an example of an employee master. The employee master 41 registers and manages the following information shown in association with each other.
[0150]
・ Employee code:
·Full name:
・ Affiliation code:
·contact information:
・ Other:
Here, the employee code is a unique identifier assigned to an employee of the company. Name is the name of the employee. The affiliation code is the code of the department to which the employee belongs. The contact information is a contact information such as an e-mail address, a telephone number or a FAX telephone number.
[0151]
FIG. 18B shows an example of affiliation master. The affiliation master 42 registers the affiliation name of the affiliation code.
[0152]
FIG. 18C shows an example of the project master. The project master 43 is a project name registered in association with a project code.
[0153]
FIG. 18D shows an example of an employee affiliation history table. The employee affiliation history table 44 registers the past affiliation history of the employees, and here, the affiliation history table 44 is registered in association with the following shown in the figure.
[0154]
・ Employee code:
・ Affiliation code:
・ Start date of affiliation:
・ Affiliation end date:
・ Other:
Here, the employee code is an employee code registered in the employee master 41 of FIG. The affiliation code is an affiliation code indicating the department to which the employee belongs. It is recorded that he / she belonged to the department of the affiliation code of the entry from the affiliation start date to the affiliation end date.
[0155]
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, the participation start date, and the participation end date of the project to which the employee currently belongs in the past are associated and registered.
[0156]
FIG. 18F shows an example of the affiliation / project installation history table. The affiliation / project installation history table 46 is a table in which affiliations and project installation histories are registered in association with the following information shown in the figure.
[0157]
・ DP code:
·name:
・ Installation start date:
・ Installation end date:
FIG. 19 shows an example table / list of the present invention.
[0158]
FIG. 19A shows an example of a usage history table. The usage history table 25 is registered in association with the following information shown in the figure.
[0159]
・ Management code:
·the date of use:
・ Notifier (notification destination) employee code:
・ Search condition employee code:
-Notification target code:
・ Type code:
・ Event name:
・ Event dates:
·Reference information:
·comment:
Here, the management code is a unique code for managing the event, and the usage date is the date used (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 a notification target. The type code is a code representing the event type. The event name is an easily understood name of the event. The event date is the date and time when the event is held. The reference information is information that is useful for the event. The comment is a comment for the event.
[0160]
FIG. 19B shows an example of a notification history table. The notification history table 26 is a history of a notification person who has notified an event, and is registered with the following information shown in the figure.
[0161]
・ Notification number:
-Notification employee code:
-Event management code:
・ Opening flag:
Here, the notification number is a unique, for example, sequential number when an event is notified. The notification destination employee code is the code of the employee who notified the event. The event management code is the management code of the event notified to the notified employee. The opening flag is not opened when the employee to whom the notification is made is not opened, and is viewed when the employee is opened, and the person outside the system is blank.
[0162]
FIG. 19C shows an example of an answer history table. The response history table 27 stores response histories, and registers the following information shown in association with each other.
[0163]
・ Answer number:
・ Answer date:
・ Respondent employee code:
-Event management code:
·Answer:
Here, the answer number is a unique sequential number assigned to the answer. The response date is the date when the response was received. The respondent employee code is the employee code that responded. The event management code is the management code of the event that has been answered. The answer is the distinction between participation and non-participation in the event.
[0164]
FIG. 19D shows an example of a settlement history table. The settlement history table 28 is registered in association with information for settlement of the participation fee for the event, and here, the following information shown in the figure is associated and registered.
[0165]
・ Settlement number:
·the date of use:
Payer employee code:
・ Recipient employee code:
·Amount of money:
·Payee:
-Event management code:
Here, the settlement number is a unique number for settlement. The payer employee code is the employee code of the employee who paid the event participation fee. The recipient employee code is the employee code of the received employee. The amount is the amount paid. The transfer destination is a transfer destination of the amount. The event management code is the management code of the event for which the expense has been paid.
[0166]
FIG. 19E shows an example of a search condition list. The search condition list is a list in which search condition display sentences are registered in association with notification target codes. Here, the search target code is a code set in the notification target code column of the usage history table 25 in FIG. 19A described above, and for example, “01” is a code for searching within the current department. is there. Each of these notification target codes can be logically described by AND or OR.
[0167]
FIG. 19F shows an example of the reference information list for each event. In the event-specific reference information list, event names, settlement method designation fields, and reference information are registered as shown in the figure in association with the type codes.
[0168]
FIG. 19G shows an example of a company-wide common authentication table. The company-wide authentication table is for authenticating an employee by registering a password in association with the employee code entered by the employee when logging in.
[0169]
(Appendix 1)
In the event support method that presents a list of contacts for the event,
Establish a master that registers at least the name and affiliation information in correspondence with the ID of the contact person,
In response to the input of the ID or name of the person who will be 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 as necessary Extracting other names and IDs as needed;
Presenting the extracted name and a list of IDs extracted as necessary as a contact person list;
An event support method.
[0170]
(Appendix 2)
The event support method according to appendix 1, wherein the affiliation information is current and past affiliation information.
[0171]
(Appendix 3)
The event support method according to appendix 1, wherein the affiliation information includes current and past affiliation information and a period of belonging to the affiliation information.
[0172]
(Appendix 4)
Send electronic data with event information, answer field for participation, and answer field for participation fee and payment method as necessary to all contact persons in the list of contact persons or specified contact persons Alternatively, the event support method according to any one of Supplementary Note 1 to Supplementary Note 3, further comprising a step of recording the completion when accessed and transmitted or accessed.
[0173]
(Appendix 5)
When a response is received from the contact person, the response field of the corresponding person has been received from the above list of contact persons, and there is a step of recording the payment method in the participation cost field as necessary, whether or not to participate in the participation field The event support method according to appendix 4.
[0174]
(Appendix 6)
The event support method according to appendix 5, further comprising a step of creating and presenting a list by collecting information on the recorded answer field, participation field, and participation cost field as necessary.
[0175]
(Appendix 7)
In the event support program that presents a list of contacts for the event, a master is provided that registers at least the name and affiliation information in association with the ID of the contact person.
In response to the input of the ID or name of the person who will be 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 as necessary Extracting other names and IDs as needed;
Presenting the extracted name and a list of IDs extracted as necessary as a contact person list;
Event support program to make the computer function.
[0176]
(Appendix 8)
In the event support device that presents a list of contacts for the event,
A master that registers at least the name and affiliation information in association with the ID of the person to be contacted;
In response to the input of the ID or name of the person who will be 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 as necessary Means to extract other names and IDs as needed,
Means for presenting the extracted name and a list of IDs extracted as necessary as a contact person list;
An event support apparatus comprising:
[0177]
(Appendix 9)
In a computer-readable recording medium recording an event support program that presents a list of contacts for an event,
Establish a master that registers at least the name and affiliation information in correspondence with the ID of the contact person,
In response to the input of the ID or name of the person who will be 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 as necessary Extracting other names and IDs as needed;
Presenting the extracted name and a list of IDs extracted as necessary as a contact person list;
The computer-readable recording medium which recorded the program made to function as a computer.
[0178]
【The invention's effect】
As described above, according to the present invention, when event information is registered, the personnel information database 4 or the like can be searched to automatically extract current and past contacts related to the event information and present a list. In addition to eliminating this, the event information, presence / absence of participation, costs, etc. are communicated to the parties concerned via Web pages, e-mails, etc., and the response and payment of expenses are received and tabulated. It is possible to create and deliver a complete list, receive answers, automatically count and present participants and non-participants, and eliminate the manual work of the secretary.
[Brief description of the 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 according to 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 according to 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 according to the present invention.
FIG. 10 is a flowchart of an answer input screen according to the present invention.
FIG. 11 is an example of an answer input screen according to the present invention.
FIG. 12 is a comment column display flowchart of the present invention.
FIG. 13 is a flowchart (part 1) of a settlement processing screen according to the present invention.
FIG. 14 is a flowchart (part 2) of the settlement processing screen according to the present invention.
FIG. 15 is an example of a settlement screen according to the present invention.
FIG. 16 is an example of a participant list screen according to the present invention.
FIG. 17 is a notification list example of the present invention.
FIG. 18 is an example of a master / table of the present invention.
FIG. 19 is a table / list example of the present invention.
[Explanation of symbols]
1: Server
2: Event office system
21: Event reception program
22: Notification destination search program
23: Event settlement program
24: Participant confirmation program
25: Usage history table
26: Notification history table
27: Answer history table
28: Settlement history table
29: Salary transfer system
30: Expense settlement system
31: Map search system
4: HR 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)

In the event support method in which the server executes a program and outputs a list of contacts for the event,
The server receives the ID of the employee who is the center of the event from the user terminal;
An employee who has registered at least his / her name, current and past affiliation information in association with an employee ID stored in a storage device accessible by the server using the received ID as a key read the affiliation information searched for a matching entry master, further, ID of the entry having been the affiliation information read the key, the same affiliation information and affiliation information with the key to search for the employee master of the steps of extracting the name of the entry is associated with a different ID from the ID of the received,
A method in which the server outputs a list of names extracted in the step as a list of contact persons related to an employee who is the center of the event. The employee master further stores information related to a contact in association with the employee ID, and the contact associated with all contact persons in the contact person list or designated to the contact associated with the contact subject, information related to the event, answer to the presence of participants, and if necessary to set the answer to join cost and payment method electronic data to the user terminal The event support method according to claim 1, further comprising a step of recording information indicating whether or not an answer has been received from the transmitted user terminal . In the event support program that the server executes and outputs a list of contacts for the event,
The server receives the ID of the employee who is the center of the event from the user terminal;
An employee who has registered at least his / her name, current and past affiliation information in association with an employee ID stored in a storage device accessible by the server using the received ID as a key read the affiliation information searched for a matching entry master, further, ID of the entry having been the affiliation information read the key, the same affiliation information and affiliation information with the key to search for the employee master of the steps of extracting the name of the entry is associated with a different ID from the ID of the received,
An event support program for causing the server to function as a step of outputting a list of names extracted in the step as a contact target person list relating to an employee who is the center of the event.

Images