JP5338601B2 - Conference facilitator selection method, apparatus and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To specify an appropriate chairperson who can finish a conference on time. <P>SOLUTION: The method for selecting the chairperson of a conference includes: a process to extract the user IDs of participants associated to the conference IDs of a conference in which a person participating in a specific conference who has participated in the past from a conference data storage part; a process to remove duplicates of the user IDs of the extracted participants and store as the user IDs of co-participants in a co-participant list storage part; a process to calculate the score indicating the degree of suitability to the chairperson of the specific conference by specifying the conference IDs associated to the user IDs of the person participating and the user IDs of the corresponding co-participants for every person participating from the conference data storage part, specifying the actual times and scheduled times of the conferences related to the specified corresponding conference IDs from the conference data storage part, calculating first values using the ratios of the actual times and the scheduled times, and determining the total of the first times; and a process to specify as the chairperson of the conference based on the calculated score. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present technology relates to a technology for selecting a facilitator of a conference.

  In general, when a meeting is held, a time is set in advance, and a conclusion is made by discussing within the time. Of course, it is not preferable that the meeting does not end even if the scheduled time is exceeded, and it is not preferable that the meeting ends significantly earlier than the scheduled time. This is because there is a possibility that there is not enough discussion.

  In such a predetermined time, the meeting can be advanced so that attendees can speak up and have lively discussions, problem solving, idea creation, consensus building, etc. The person is generally called a facilitator.

  In order to make the conference meaningful, it is desirable for a facilitator to be present at the conference, but there is not necessarily a person who is suitable for the facilitator among those scheduled to attend the conference. In such a case, it is necessary to select a facilitator suitable for the meeting to be held from a person other than those who are scheduled to attend.

  Conventionally, depth information associated with a label attached to problem information (corresponding to the agenda) selected by a conference participant in order to select the best moderator for the progress of the problem extraction meeting (that is, the problem is located). There is a technique for obtaining a moderator evaluation function for each participant based on (hierarchical information) and the number of terminal branches associated with a label.

JP 2007-257503 A

  However, the above technique is not a technique for selecting a person who can proceed with the conference so that it ends on time. In addition, only the participants are targeted for the moderator, and it is not a technique for selecting a moderator for people other than the participants. Furthermore, in reality, the optimal moderator in a meeting often depends on the combination between participants. However, in the above technique, only the agenda is considered, and the combination between participants is not considered at all. Therefore, the optimum moderator is not always selected.

  Therefore, an object of the present technology is to provide a technology for identifying an appropriate facilitator that can finish a conference on time.

  The meeting facilitator selection method according to the first aspect of the present technology stores meeting data including an attendee ID that is a user ID of a meeting attendee, a scheduled time of the meeting, and an actual time required for the meeting. It is executed by a computer that can access a conference data storage unit and a prospective attendee list storage unit that stores a prospective attendee ID that is a user ID of a prospective attendee of a specific conference scheduled to be held. Then, the method refers to the conference data storage unit, and specifies the conference data including at least one attendee ID stored in the expected attendee list storage unit, and the specified conference data includes Divergence value calculating step for calculating a divergence value representing the degree of divergence between the scheduled time and the actual time, and a score calculating step for calculating the sum of the calculated divergence values for each attendee ID And a facilitator specifying step of specifying a conference facilitator from prospective attendees of the specific conference based on the calculated sum.

  You will be able to identify the appropriate facilitator who can end the meeting on time.

1 is a configuration diagram of a system according to an embodiment of the present technology. It is a figure which shows an example of the data stored in user DB. It is a figure which shows an example of the data stored in meeting DB. It is a figure which shows an example of the data stored in speech time DB. It is a processing flow of the process in a facilitator selection apparatus. It is a figure which shows an example of a facilitator selection request screen. It is a figure which shows an example of the data stored in a prospective attendee list storage part. It is a figure which shows the processing flow of an attendance meeting specific process. It is a figure which shows an example of the data stored in an attendance meeting list storage part. It is a figure which shows the processing flow of an attendance meeting specific process. It is a figure which shows the processing flow of an attendance meeting specific process. It is a figure which shows the processing flow of a passenger identification process. (A) And (b) is a figure which shows an example of the data stored in a passenger list storage part. It is a figure which shows the processing flow of a passenger identification process. It is a figure which shows the processing flow of a score calculation process. It is a figure which shows the processing flow of a score calculation process. It is a figure which shows the processing flow of a score calculation process. It is a figure which shows an example of the data stored in a score storage part. It is a figure which shows an example of a facilitator selection result screen. It is a functional block diagram of a computer.

  FIG. 1 shows a configuration diagram of a system according to the present embodiment. For example, the facilitator selection device 100, which is a personal computer, includes a selection request reception unit 101, a prospective attendee list storage unit 103, an attendance conference identification unit 105, an attendance conference list storage unit 107, a attendee identification unit 109, The attendee list storage unit 111, the score calculation unit 113, the score storage unit 115, and the display processing unit 117 are included.

  The selection request accepting unit 101 performs a process of identifying a prospective attendee of a meeting scheduled to be held based on the data input by the user, and stores the processing result data in the prospective attendee list storage unit 103. The attendance meeting identification unit 105 performs attendance meeting identification processing for identifying a meeting in which the prospective attendee attended in the past based on the data stored in the attendance candidate list storage unit 103, and the process result data is used as the attendance meeting. Store in the list storage unit 107. Based on the data stored in the attendance meeting list storage unit 107, the attendee identification unit 109 performs a attendee identification process for identifying a person who has attended a meeting attended by a prospective attendee in the past. Is stored in the attendee list storage unit 111. The score calculation unit 113 performs a score calculation process for calculating a score for specifying the facilitator of the meeting scheduled to be held based on the data stored in the attendee list storage unit 111, and the processing result data is stored in the score storage unit 115. The display processing unit 117 specifies a person who is suitable as a facilitator based on the data stored in the score storage unit 115, and displays data relating to the specified person on the output unit 130. The attendance meeting identification process, the attendee identification process, and the score calculation process will be described in detail later.

  The facilitator selection device 100 is connected to an input unit 120 such as a keyboard and a mouse, an output unit 130 such as a display device, a user DB 140, a conference DB 150, and a speech time DB 160.

  FIG. 2 shows an example of the table configuration of the user DB 140 and stored data. In the example of FIG. 2, a user ID column and a user name column are included.

  FIG. 3 shows an example of the table configuration of the conference DB 150 and stored data. In the example of FIG. 3, a conference ID column, an attendee column, a scheduled time column, an actual time column, and a conference name column are included. A meeting whose data is not included in the actual time column is a meeting that has not yet been held. The actual meeting time is registered after the meeting ends. The other data is registered, for example, after it is decided to hold the conference and before it is held.

  FIG. 4 shows an example of the table structure of the speech time DB 160 and stored data. The example of FIG. 4 includes a conference ID column, an attendee column, and a speech time column. These data are registered after the conference ends.

  Registration and updating of data in the user DB 140, the conference DB 150, and the speech time DB 160 are performed by, for example, a conference attendant or a manager via the input unit 120, for example. Note that the speech time in the speech time DB 160 may be recorded by recording voice during the meeting, analyzing the recorded data, calculating the speech time of each attendee, and automatically registering the speech time.

  Next, processing contents of the system shown in FIG. 1 will be described with reference to FIGS. FIG. 5 shows a main processing flow. It is assumed that login processing and the like necessary for the user to use this system have already been performed. First, the selection request reception unit 101 of the facilitator selection device 100 displays a selection request reception screen on the output unit 130 (FIG. 5: Step S1).

  FIG. 6 shows an example of a facilitator selection request acceptance screen. In the example of FIG. 6, a conference ID input field, a conference name input field, a selection button for executing selection of a facilitator, a clear button for clearing data input in the conference ID input field and the conference name input field, And a return button for returning to the original menu page or the like. When requesting the selection of a facilitator for a meeting to be held, the user inputs the meeting ID or meeting name of the meeting to be held and clicks a selection button.

  Returning to the description of FIG. 5, the selection request receiving unit 101 receives an input of a conference name or a conference ID from the user via the input unit 120 and stores it in a storage device such as a main memory (step S <b> 3). Then, the selection request receiving unit 101 identifies the conference ID or user ID associated with the conference ID received in step S3 from the conference DB 150 and stores it in the planned attendee list storage unit 103 as a list of attendees LX. (Step S5).

  FIG. 7 shows an example of data stored in the attendee list storage unit 103. In the example of FIG. 7, the user ID of the person who is scheduled to attend the meeting scheduled to be held is stored.

Returning to the description of FIG. 5, the attendance meeting specifying unit 105 performs attendance meeting specifying processing (step S7). Here, the attendance meeting specifying process will be described with reference to FIGS. First, the attendance meeting specifying unit 105 specifies one unprocessed user ID from the list LX of attendees stored in the attendee list storage unit 103 (FIG. 8: Step S21). In the attendance meeting specifying process, the user ID specified in step S21 is X. Then, the attendance meeting specifying unit 105 initializes the list LK _X , the list LKD _X , the list LK _X S, and the list LK _X L (step S23). In step S23, when the data about the list LK _X , the list LKD _X , the list LK _X S, and the list LK _X L are already stored in the attendance meeting list storage unit 107, the data is cleared.

In the above, the subscript “ _X ” is attached to the list, which indicates that the list is for the user X. For example, when the user ID is H1, the list of the user H1 is a list LK _H1 , a list LKD _H1 , a list LK _H1 S, and a list LK _H1 L. FIG. 9 shows an example of data stored in the attendance meeting list storage unit 107. In the example of FIG. 9, a list ID column and a conference ID column are included. As described above, the list ID includes data for identifying which one of the above four lists and a subscript of the user ID.

Returning to the description of FIG. 8, the attendance meeting identification unit 105 reads one unprocessed record from the meeting DB 150 (step S25). Furthermore, the attendance meeting identification part 105 judges whether the record time of the meeting is included in the record read in step S25 (step S27). If not included (step S27: No route), the process proceeds to step S37. On the other hand, if it is included (step S27: Yes route), the attendance meeting identification unit 105 determines whether the user ID “X” is included in the record read in step S25 (step S29). If not included (step S29: No route), the process proceeds to step S37. On the other hand, if it is included (step S29: Yes route), the attending meeting specifying unit 105 adds the meeting ID included in the record read in step S25 to the list LK _X (step S31). That is, in step S31, the conference ID included in the record read in step S25 is stored in the attendance conference list storage unit 107 in association with the list ID “LK _X ”.

Returning to the description of FIG. 8, the attendance meeting identification unit 105 identifies the speech time T ₁ associated with the conference ID and the user ID “X” included in the record read in step S 25 from the speech time DB 160. The actual time T ₂ and all user IDs associated with the conference ID included in the record read in step S25 are specified from the conference DB 150, and T ₁ > T ₂ / U _num (U _num is It is determined whether the number of user IDs specified in the step is satisfied (step S33). When not satisfy | filling (step S33: No route), it transfers to step S37. On the other hand, if satisfied (step S33: Yes route), the attendance meeting identification unit 105 adds the meeting ID included in the record read in step S25 to the list LKD _X (step S35). That is, in step S35, the conference ID included in the record read in step S25 is stored in the attendance conference list storage unit 107 in association with the list ID “LKD _X ”.

  And attendance meeting specific part 105 judges whether it processed about all the records of meeting DB150 (Step S37). If all the records have not been processed (step S37: No route), the process returns to step S25 in order to execute the process for the next record. On the other hand, when all the records have been processed (step S37: Yes route), the process proceeds to step S39 in FIG.

Moving to the description of FIG. 10, after the terminal A, the attendance meeting specifying unit 105 specifies one unprocessed meeting ID included in the list LK _X from the attendance meeting list storage unit 107 (FIG. 10: step). S39). The attending conference identifying unit 105, a record associated with the specified conference ID time _{T 3} and the expected time _{T 4} identifies the conference DB150 in step S39 (step S41). The attending conference identifying unit 105 determines whether satisfy _{T 3} ≦ _{T 4} (step S43). When not satisfy | filling (step S43: No route), a process transfers to step S47. On the other hand, is satisfied: (step S43 Yes route), attended conference identifying unit 105, the list LK _X S, adding the meeting ID specified in Step S39 (Step S45). That is, in step S45, the conference ID specified in step S39 is stored in the attendance conference list storage unit 107 in association with the list ID “LK _X S”. And attendance meeting specific part 105 judges whether it processed about all meeting IDs contained in list LK _X (Step S47). If all the conference IDs have not been processed (step S47: No route), the process returns to step S39 in order to execute the process for the next conference ID. On the other hand, when all the conference IDs have been processed (step S47: Yes route), the processing proceeds to step S49 in FIG.

Shifting to the description of FIG. 11, after the terminal B, the attendance meeting specifying unit 105 specifies one unprocessed meeting ID included in the list LKD _X from the attendance meeting list storage unit 107 (FIG. 11: step) S49). The attending conference identifying unit 105, the actual time _{T 5} and expected time _{T 6} associated with the specified conference ID for identifying the conference DB150 in step S49 (step S51). Then, the attendance meeting specifying unit 105 determines whether T ₅ > T ₆ is satisfied (step S53). When not satisfy | filling (step S53: No route), a process transfers to step S57. On the other hand, is satisfied: (step S53 Yes route), attended conference identifying unit 105, the list LK _X L, adding the meeting ID specified in Step S49 (Step S55). That is, in step S55, the conference ID specified in step S49 is stored in the attendance conference list storage unit 107 in association with the list ID “LK _X L”. And attendance meeting specific part 105 judges whether it processed about all meeting IDs contained in list LKD _X (Step S57). If all the conference IDs have not been processed (step S57: No route), the process returns to step S49 in order to execute the process for the next conference ID.

  On the other hand, when all meeting IDs have been processed (step S57: Yes route), the attending meeting specifying unit 105 includes all user IDs included in the list LX of attendees stored in the attendee list storage unit 103. It is determined whether or not processing has been performed (step S59). If all the user IDs have not been processed (step S59: No route), the process returns to step S21 in FIG. On the other hand, if all user IDs have been processed (step S59: Yes route), the process returns to the original process.

By performing the processing as described above, the list LK _X , the list LKD _X , the list LK _X S, and the list LK _X L are generated for all prospective attendees of the conference scheduled to be held. In the present embodiment, a meeting included in the list LK _X S (that is, a meeting that ended earlier than the scheduled time) and a meeting included in the list LK _X L (that is, a meeting that exceeded the scheduled time) Both are subject to the processing described below. If the meeting ends earlier than the scheduled time, the meeting cannot proceed so that the discussion is sufficient, and conversely, if the scheduled time is exceeded, the discussion cannot be summarized. Both of these should be taken into account when calculating the score for.

Returning to the description of FIG. 5, the attendee identification unit 109 performs the attendee identification process (step S9). The attendee identification process will be described with reference to FIGS. First, the attendee identification unit 109 identifies one unprocessed user ID from the list LX of attendees stored in the attendee list storage unit 103 (FIG. 12: step S61). In the attendee identification process, the user ID identified in step S61 is X, and the meaning of the subscript “ _X ” is the same as that described in the explanation of the attendance meeting identification process. Then, the attendee identification unit 109 initializes the list LY _X (step S63). In step S63, if the data for the list LY _X is already stored in the attendee list storage unit 111, the data is cleared.

  FIGS. 13A and 13B show examples of data stored in the attendee list storage unit 111. In the example of FIGS. 13A and 13B, a list ID column and a user ID column are included. The list LY is a list that is finally generated by the attendee identification process.

Returning to the description of FIG. 12, the attendee identification unit 109 identifies one unprocessed conference ID from the list LK _X S stored in the attendance conference list storage unit 107 (step S65). Then, the attendee identification unit 109 identifies all user IDs associated with the conference ID identified in step S65 from the conference DB 150, and stores them in a storage device such as a main memory (step S67). Then, the user ID obtained by removing the user ID “X” from the user ID specified in step S67 is specified and added to the list LY _X (step S69). That is, in step S69, the user ID obtained by removing the user ID “X” from the user ID specified in step S67 is stored in the attendee list storage unit 111 in association with the list ID “LY _X ”.

Then, the attendee identification unit 109 determines whether or not all meeting IDs included in the list LK _X S have been processed (step S71). If all the conference IDs are not processed (step S71: No route), the process returns to step S65 in order to execute the process for the next conference ID. On the other hand, when all the conference IDs have been processed (step S71: Yes route), the process proceeds to step S73 in FIG.

14, the attendee identification unit 109 identifies one unprocessed conference ID from the list LK _X L stored in the attendance conference list storage unit 107 after the terminal D (FIG. 14). 14: Step S73). Then, the attendee identification unit 109 identifies all user IDs associated with the conference ID identified in step S73 from the conference DB 150 and stores them in a storage device such as a main memory (step S75). Then, the user ID obtained by removing the user ID “X” from the user ID specified in step S75 is specified and added to the list LY _X (step S77). That is, in step S77, the user ID obtained by removing the user ID “X” from the user ID specified in step S75 is stored in the attendee list storage unit 111 in association with the list ID “LY _X ”.

Then, the attendee identification unit 109 determines whether all meeting IDs included in the list LK _X L have been processed (step S79). If all the conference IDs have not been processed (step S79: No route), the process returns to step S73 in order to execute the process for the next conference ID. On the other hand, when the processing for all the conference ID (step S79: Yes route), sit's identification unit 109 removes the overlap of the user ID in the list LY _X (step S81). If there is no duplication of user IDs in the list LY _X , step S81 is skipped. Then, the attendee identification unit 109 determines whether all user IDs included in the list LX have been processed (step S83). If all the user IDs are not processed (step S83: No route), the process returns to step S61 in FIG.

On the other hand, when all user IDs have been processed (step S83: Yes route), the attendee identification unit 109 assigns user IDs included in the list LY _X to the attendee list storage unit for all user IDs included in the list LX. The data is read from 111 and stored in a storage device such as a main memory (step S85). The attendee identification unit 109 removes duplication of the user ID read in step S85, stores it in the attendee list storage unit 111 as a facilitator candidate list LY (step S87), and returns to the original process.

  By performing the processing as described above, not only those who are scheduled to attend the meeting scheduled to be held, but also persons other than those who are scheduled to attend are specified as facilitator candidates. Therefore, it is possible to select a more suitable facilitator than the technique of selecting a facilitator only for the prospective attendees.

Returning to the description of FIG. 5, the score calculation unit 113 performs a score calculation process (step S11). The score calculation process will be described with reference to FIGS. First, the score calculation unit 113 identifies one unprocessed user ID included in the list LY from the attendee list storage unit 111 (FIG. 15: step S91). Hereinafter, in the score calculation process, the user ID specified in step S91 is Y. Then, the score calculation unit _{113, S X, L X, S} XY, L XY, C1 X, C2 X, C3 XY, C4 XY, is set to 0 DS _Y and DL _Y (step S93). Note that the variable with the subscript “ _X ” is a variable for the attendee who has the user ID X, and the variable with the subscript “ _Y ” is for the facilitator candidate with the user ID Y. The variable to which the subscript “ _XY ” is attached indicates that the variable is a combination of a prospective attendee whose user ID is X and a facilitator candidate whose user ID is Y.

Then, the score calculation unit 113 reads one unprocessed record from the conference DB 150 (step S95). In the score calculation process, the record read in step S95 is referred to as a “record related to the process” for convenience. And the score calculation part 113 judges whether performance time is included in the record which concerns on a process (step S97). That is, it is determined whether the record is about a conference already held. If the actual time is not included (step S97: No route), the process proceeds to step S129 in FIG. On the other hand, when the actual time is included (step S97: Yes route), the score calculation unit 113 determines whether T ₇ ≦ T ₈ is satisfied for the actual time T ₇ and the scheduled time T ₈ included in the record related to the process. (Step S99). When T ₇ ≦ T ₈ is satisfied (step S99: Yes route), the score calculation unit 113 determines whether the record related to the process includes the user ID of the prospective attendee (step S101). That is, it is determined whether any of the user IDs included in the list LX is included in the record related to the process. If not included (step S101: No route), the process proceeds to step S129 in FIG.

On the other hand, if included (step S101: Yes route), the score calculation unit 113 identifies one unprocessed user ID determined to be included in the record related to the process in step S101 (step S103). ). In steps S105 to S113, the user ID specified in step S103 is set to X for convenience. Further, the score calculation unit 113 identifies the speech time T ₉ associated with the conference ID and the user ID “X” included in the record related to the processing from the speech time DB 160, and S _X = S _X + T ₈ / T ₇ × (1−T ₉ / T ₇ ) and C1 _X = C1 _X +1 are calculated and stored in a storage device such as a main memory (step S105). Then, the process proceeds to step S107 in FIG.

Shifting to the description of FIG. 16, after the terminal G, the score calculation unit 113 determines whether the user ID “Y” is included in the record related to the process (step S <b> 107). If not included (step S107: No route), the process proceeds to step S113. On the other hand, when included (step S107: Yes route), the score calculation unit 113 determines whether the user ID “X” and the user ID “Y” are the same (step S109). If they are the same (step S109: Yes route), the process proceeds to step S113. This is because Sxy is an index when the user Y is “sitting with” the user X, and therefore does not make sense as an index when the user X, the user, and Y are the same person. On the other hand, if not the same (step S109: No _route), to calculate the _{S XY = S XY + T 8} / T 7 × (1-T 9 / T 7) and _C3 XY _{= C3} XY +1, for example, a storage such as a main memory Store in the device (step S111).

Here, the meanings of S _X , S _XY , C1 _X, and C3 _XY calculated above will be described. First, the meaning of _SXY will be described. In the calculation formula of step S111, T ₈ / T ₇ is an index representing the discrepancy between the actual meeting time and the scheduled time. Therefore, as T ₈ / T ₇ is smaller, that is, as S _XY is smaller, the user Y becomes a facilitator. It can be said that it is a suitable person. However, in step S111, (1−T ₉ / T ₇ ) is further multiplied by T ₈ / T ₇ for correction. This takes into account that when the user X's speech time is long, Y who was present is likely to be a suitable person as a facilitator in relation to X. That is, by multiplying (1−T ₉ / T ₇ ) as a correction value, S _XY becomes smaller as the user X's speech time is longer, so that the person can be easily identified as a suitable facilitator. The same applies to _LXY described below.

On the other hand, S _X is intended to index the divergence between the actual time and the scheduled time of the meeting attended in the past for the individual user X, regardless of the user Y who is a facilitator candidate. Note that S _X is necessary for calculating an index to be used instead of S _XY when it is determined in step S 139 that S _XY = 0 is satisfied. The same applies to L _X described below.

Moreover, C1 _X is a value representing how step S105 is performed again, used in step S131. The same applies to C3 _XY .

  Returning to the description of FIG. 16, the score calculation unit 113 determines whether all user IDs determined to be included in the record related to the process in step S <b> 101 have been processed (step S <b> 113). If all the user IDs are not processed (step S113: No route), the process proceeds to step S103 via the terminal I in order to execute the process for the next user ID. On the other hand, when all the user IDs have been processed (step S113: Yes route), the process returns to step S129.

On the other hand, if T ₇ ≦ T ₈ is not satisfied in step S99 (step S99: No route), the score calculation unit 113 determines whether the record related to the process includes the user ID of the prospective attendee (step S115). . That is, it is determined whether any of the user IDs included in the list LX is included in the record related to the process. If not included (step S115: No route), the process proceeds to step S129 in FIG.

On the other hand, when included (step S115: Yes route), the score calculation unit 113 identifies one unprocessed user ID determined to be included in the record related to the process in step S115 (step S117). ). In steps S119 to S127, the user ID specified in step S117 is set to X for convenience. Further, the score calculation unit 113 specifies the speech time T ₉ associated with the conference ID and the user ID “X” included in the record related to the processing from the speech time DB 160, and L _X = L _X + T ₇ / T ₈ × (1-T ₉ / T ₇ ) and C2 _X = C2 _X +1 are calculated and stored in a storage device such as a main memory (step S119). Then, the process proceeds to step S121 in FIG.

Shifting to the description of FIG. 16, after the terminal H, the score calculation unit 113 determines whether the user ID “Y” is included in the record related to the process (step S <b> 121). If not included (step S121: No route), the process proceeds to step S127. On the other hand, when included (step S121: Yes route), the score calculation unit 113 determines whether the user ID “X” and the user ID “Y” are the same (step S123). If they are the same (step S123: Yes route), the process proceeds to step S127. This is because Lxy is an index when the user Y is “sitting with” the user X, and therefore does not make sense as an index when the user X, the user, and Y are the same person. On the other hand, if not the same (step S123: No _{route), L XY = L XY +} T 7 / T 8 × (1-T 9 / T 7) and calculates the _C4 XY _{= C4} XY +1, for example, a storage such as a main memory Store in the device (step S125).

The meanings of L _X , L _XY , C2 _X and C4 _XY are the same as S _X , S _XY , C1 _X and C3 _XY described above. However, since L _X and L _XY are indexes when T ₇ ≦ T ₈ is not satisfied (that is, when T ₇ > T ₈ ), the degree of deviation between the actual time T ₇ and the scheduled time T ₈ Is calculated as T ₇ / T ₈ .

  And the score calculation part 113 judges whether it processed about all the user IDs judged to be contained in the record which concerns on a process in step S115 (step S127). If all the user IDs have not been processed (step S127: No route), the process returns to step S117 via the terminal J in order to execute the process for the next user ID. On the other hand, when all the user IDs have been processed (step S127: Yes route), the score calculation unit 113 determines whether all the records in the conference DB 150 have been processed (step S129). If all the records have not been processed (step S129: No route), the processing returns to step S95 in FIG.

On the other hand, when all records are processed (step S129: Yes route), the score calculation unit 113 performs S _X = S _X / C1 _X and L _X = L _X / for all attendees X included in the list LX. C2 _X is calculated. Further, S _XY = S _XY / C 3 _XY and L _XY for combinations of prospective attendees X included in the list LX and facilitator candidates whose user ID is Y (except when X and Y are the same) = L _XY / C4 _XY is calculated and stored in a storage device such as a main memory (step S131). However, in step S131, when C1 _X = 0, S _X is set to 0 with the initial value, and when C2 _X = 0, L _X is set to 0 with the initial value, and C3 _{S XY} when the _XY = 0 is set to 0 from the initial value, if the _{C4 XY} = 0 _{L XY} is set to 0 from the initial value.

Note that S _X = S _X / C1 _X in step S131 corresponds to obtaining an average value of T ₈ / T ₇ × (1−T ₉ / T ₇ ) calculated in step S105. The same applies to L _X , S _XY and L _XY .

Then, the score calculation unit 113 calculates the number of non-zero S _X calculated in step S131 as CountS _X , and calculates the number of non-zero L _X calculated in step S131 as CountL _X and step S131. The number of S _XY that are not zero is counted as CountS _XY, and the number of non-zero L _XY calculated in step S131 is counted as CountL _XY , and stored in a storage device such as a main memory (step S133). ). Then, the process proceeds to step S135 in FIG.

Shifting to the description of FIG. 17, after the terminal L, the score calculation unit 113 determines that avgS = ΣS _X / CountS _X , avgL = ΣL _X / CountL _X , avgS _Y = ΣS _XY / CountS _XY and avgL _Y = ΣL _XY / calculates COUNTL _XY, and stores into a storage device such as the main memory (step S135). In step S135, avgS = ΣS _X / CountS _X corresponds to obtaining the average value of S _X calculated in step S131. That is, in step S131, since S _X is calculated for each attendee, the average value is obtained except for those where S _X = 0. The same applies to avgL, avgS _Y and avgL _Y.

Then, the score calculation unit 113 identifies one user ID of an unprocessed attendee from the list LX (step S137). In steps S139 to S151, the user ID specified in step S137 is set to X for convenience. Further, the score calculation unit 113 determines whether or not S _XY regarding the combination of the prospective attendee whose user ID is X and the facilitator candidate whose user ID is Y satisfies S _XY = 0 (step S139). If not satisfied (step S139: No route), DS _Y = DS _Y + S _XY is calculated and stored in a storage device such as a main memory (step S141). On the other hand, when S _XY = 0 is satisfied (step S139: Yes route), DS _Y = DS _Y + S _X × avg S _Y / avgS is calculated and stored in a storage device such as a main memory (step S143).

Then, the score calculation unit 113 determines whether or not L _XY regarding the combination of the attendee with the user ID X and the facilitator candidate with the user ID Y satisfies L _XY = 0 (step S145). If not satisfied (step S145: No route), DL _Y = DL _Y + L _XY is calculated and stored in a storage device such as a main memory (step S147). On the other hand, it is satisfied (step S145: Yes _route), and calculates the _{DL Y = DL Y + L X} × avgL Y / avgL, stored into a storage device such as the main memory (step S149).

Then, the score calculation unit 113 determines whether all user IDs included in the list LX have been processed (step S151). If all the user IDs have not been processed (step S151: No route), the process returns to step S137 to execute the process for the next user ID. On the other hand, when all the user IDs have been processed (step S151: Yes route), the score calculation unit 113 calculates D _Y = DS _Y + DL _Y and stores it in the score storage unit 115 in association with the user ID “Y”. (Step S153).

Here, the meaning of the processing in steps S137 to S153 will be described. As described above, S _XY is an index that represents the degree of deviation between the actual time of the meeting in which the user Y who is a facilitator candidate is present with the user X and the scheduled time (however, the actual time ≦ the scheduled time). is there. By calculating the sum of all X included in the list LX (that is, all attendees in the scheduled meeting), D _Y indicating the degree of suitability of the user Y as a facilitator in the scheduled meeting is calculated. To do. However, _SXY is 0 in relation to the specific attendee who has not been present with the specific attendee in the past. In such a case, a value obtained by correcting by multiplying avgS Y _/ avgS to S _X for that particular prospective attendees instead. That is, the value obtained by correcting the S _X for that specific attendees, the specific attendees is regarded as a value in a case which has been attended with facilitator candidates Y. Thus, it is possible to prevent that the DS _Y of that has not been attended attendees often facilitator candidate is likely to be identified as meeting facilitator is reduced.

On the other hand, the actual time> About also planned is the time conference, to calculate the DL _Y in the same manner. And, finally, we calculate the score for determining whether the Y is worthy of a facilitator candidate as a facilitator in the scheduled meeting as a _{D Y = DS Y + DL Y} .

  FIG. 18 shows an example of data stored in the score storage unit 115. In the example of FIG. 18, a user ID column and a score column are included. As described above, in this embodiment, the smaller the score, the more suitable the facilitator.

  Returning to the description of FIG. 17, it is determined whether or not all user IDs included in the list LY have been processed (step S155). If all the user IDs have not been processed (step S155: No route), the process returns to step S91 in FIG. On the other hand, when all the users have been processed (step S155: Yes route), the process returns to the original process.

By carrying out the aforementioned processing, to calculate the score D _Y for all facilitators candidates included in the list LY. As noted above, because the score D _Y reflects the degree of divergence between actual time and the scheduled time of the conference, it is used as a score to identify the facilitator may terminate the conference on time be able to.

  Returning to the description of FIG. 5, the display processing unit 117 specifies a facilitator based on the score stored in the score storage unit 115, and displays the data of the specified facilitator on the output unit 130 (step S <b> 13). In step S13, for example, a person within a higher predetermined rank when scores are arranged in ascending order or a person whose score is smaller than a predetermined threshold is specified as a facilitator. Further, for example, the user name associated with the user ID of the facilitator is extracted from the user DB 140 and used as the data of the facilitator.

  FIG. 19 shows an example of a facilitator selection result screen. In the example of FIG. 19, the data of the name of the facilitator and the data of the conference ID and the conference name of the conference specified by the user in step S3 are included. The user can confirm such a screen and recognize a person suitable as a facilitator.

  By carrying out the processing as described above, it becomes possible to select an appropriate facilitator that can finish the conference on time.

  Although one embodiment of the present technology has been described above, the present technology is not limited to this. For example, the functional block diagram of the facilitator selection device 100 described above does not necessarily correspond to an actual program module configuration.

  Further, the configuration of each table described above is an example, and the configuration as described above is not necessarily required. Further, in the processing flow, the processing order can be changed if the processing result does not change. Further, it may be executed in parallel.

  Note that the stand-alone type system shown in FIG. 1 is an example, and may be implemented by, for example, a client server type.

In the score calculation process, S _X , L _X , avgS and avgL are calculated multiple times when there are multiple facilitator candidates, but the second and subsequent calculations are not performed. Also good.

  In this embodiment, the list LY of facilitator candidates is generated and the facilitator is specified from the list LY. However, the facilitator may be specified from the list LX of attendees. That is, the facilitator may be specified from those who are scheduled to attend the meeting that is scheduled to be held.

In this case, in step S91 of the score calculation process, the user ID of the facilitator candidate is specified from the list LX instead of the list LY. In steps S111 and S125, S _XY , C3 _XY , L _XY and C4 _XY are set for each pair of the user ID specified from the list LX as a facilitator candidate and the user ID specified from the list LX as a prospective attendee. calculate. Similar to the processing described above, if the user ID specified from the list LX as a facilitator candidate is the same as the user ID specified from the list LX as an attendee, these values are not calculated. . For the calculations in steps S131 to S151, the same processes as described above are performed using the calculation results in steps S111 and S125.

Then, finally, per each user ID in the list LX, _{D Y} is calculated in step S153. Then, in step S13, it identifies the facilitator among attendees based on D _Y.

  As shown in FIG. 20, the facilitator selection device 100 includes a memory 2501 (storage unit), a CPU 2503 (processing unit), a hard disk drive (HDD) 2505, a display control unit 2507 connected to the display device 2509, and a removable device. A drive device 2513 for the disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519. Application programs including the OS and the Web browser are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations. Further, data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary. Such a computer realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above with the OS and necessary application programs.

  The embodiments of the present technology described above are summarized as follows.

  The meeting facilitator selection method according to the first aspect of the present technology stores meeting data including an attendee ID that is a user ID of a meeting attendee, a scheduled time of the meeting, and an actual time required for the meeting. It is executed by a computer that can access a conference data storage unit and a prospective attendee list storage unit that stores a prospective attendee ID that is a user ID of a prospective attendee of a specific conference scheduled to be held. Then, the method refers to the conference data storage unit, and specifies the conference data including at least one attendee ID stored in the expected attendee list storage unit, and the specified conference data includes Divergence value calculating step for calculating a divergence value representing the degree of divergence between the scheduled time and the actual time, and a score calculating step for calculating the sum of the calculated divergence values for each attendee ID And a facilitator specifying step of specifying a conference facilitator from prospective attendees of the specific conference based on the calculated sum.

  This makes it possible to select an appropriate facilitator who can finish the specific meeting on time from those scheduled to attend the specific meeting scheduled to be held.

  In addition, the conference facilitator selection method described above specifies the attendee ID included in the conference data for all the conference data specified in the specific step described above, and the sum of the specified attendee IDs. You may make it further include the step which stores a group in a attendee list storage part as attendee ID. Then, in the score calculation step described above, the sum of the divergence values is calculated for each attendee ID stored in the attendee list storage unit, and based on the calculated sum in the facilitator specifying step described above, The meeting facilitator may be specified from the attendee. In this way, the person who is identified as the meeting facilitator is the person who has attended the meeting who is scheduled to attend the specific meeting. Can be useful. Therefore, it can be expected that a person who is more suitable as a meeting facilitator can be selected.

  Further, in the divergence value calculating step described above, a divergence value is calculated for each pair of the attendee ID stored in the attendee list storage unit and the attendee ID stored in the attendee list storage unit, In the above-described score calculation step, the sum of the calculated divergence values may be calculated for each attendee ID stored in the attendee list storage unit. The optimum facilitator in the conference is considered to be largely determined depending on the relationship between the facilitator and the attendees of the conference (for example, the hierarchical relationship in the company). As described above, by reflecting the deviation value calculated for each pair of attendees (that is, candidates for facilitators) and prospective attendees in the score, those who are suitable for facilitators in relation to attendees of the meeting Can be identified.

  In addition, for a pair for which a divergence value has not been calculated in the score calculation step described above, a value to be used as the divergence value of the pair is calculated based on the average value of the divergence values calculated in the divergence value calculation step. It may be. If you have attended any attendee of any particular meeting, you will be identified as an attendee and a divergence value will be calculated for the pair with that attendee but you will not be attending The divergence value is not calculated for these pairs. This is because there is no conference data including both user IDs. In such a case, calculating an alternative value and using it for the calculation of the score will reduce the score of those who have many attendees who have not attended the meeting, making it easier to identify the facilitator of the meeting. Has been eliminated.

  In the divergence value calculation step described above, the ratio between the scheduled time and the actual time may be calculated for each meeting, and the divergence value may be calculated using the average value of the calculated ratios. This is because the ratio between the scheduled time and the actual time is an index representing the degree of deviation between the planned time and the actual time.

  The meeting facilitator selection method according to the second aspect of the present technology is a meeting data storage that stores a user ID of a meeting attendee, a scheduled time of the meeting, and an actual time required for the meeting in association with the meeting ID. The attendee list storage unit that stores the user IDs of attendees of a specific meeting scheduled to be held, the attendance conference list storage unit, the attendee list storage unit, and the score storage unit A computer-implemented method capable. In this method, (a) the conference ID associated with the user ID of the prospective attendee stored in the attendee list storage unit is identified from the conference data storage unit and stored in the attendance conference list storage unit. An attendance meeting specifying step; (b) an extraction step of extracting the attendee's user ID associated with the meeting ID stored in the attendance meeting list storage section from the meeting data storage section; A specific step of identifying the user ID obtained by removing the user ID of the prospective attendee from the extracted attendee's user ID, and (d) removing all duplicate user IDs identified in the specific step Storing in the attendee list storage unit as the attendee's user ID; and (e) for each attendee, the attendee's user ID and the attendee's The conference ID associated with the user ID is identified from the conference data storage unit, the actual and scheduled times of the conference relating to the identified conference ID are identified from the conference data storage unit, and the actual time and the A first calculation step of calculating an index value representing a degree of deviation between the actual time and the scheduled time for each meeting using a ratio with the scheduled time, and calculating a first value that is an average value of the index values; (F) For each attendee, a score representing the degree suitable for the facilitator of a specific meeting is calculated by calculating the sum of the first values calculated for each attendee, and the score is stored in the score storage unit And (g) identifying a fellow member whose score stored in the score storage unit is equal to or less than a predetermined threshold or a fellow member in a higher predetermined rank as a meeting facilitator when the scores are arranged in ascending order. Include

  In this method, the following processing is roughly performed. That is, (1) Identify the meeting that the prospective attendee of the specific meeting to be held has attended in the past ((a) above), and (2) Identify the person who was present at the identified meeting as the attendee (B) (c) (d) above, (3) The degree of suitability for the facilitator of a specific meeting by using the actual time and the scheduled time in the meeting where the attendee was present with each attendee And (4) specify the meeting facilitator based on the calculated score ((g) above).

  As described above, according to the present method, it is possible to identify an appropriate meeting facilitator capable of ending a specific meeting on time. And since the person to be identified as a meeting facilitator is a person who has attended a specific meeting attendee, it is not only a prospective attendee of a specific meeting but a person other than the prospective attendee. Can also be a meeting facilitator. Therefore, it can be expected that a person who is more suitable as a meeting facilitator can be identified than a method that targets only the prospective attendees.

  In addition, the method for selecting a conference facilitator described above specifies, for each prospective attendee, the conference ID associated with the user ID of the prospective attendee from the conference data storage unit, and the identified conference ID The actual time and the scheduled time of the conference are specified from the conference data storage unit, the index value is calculated for each conference using the ratio between the actual time and the scheduled time, and the second value that is the average value of the index values A second calculating step for calculating a value, a step of calculating an average value of the second values calculated for each attendee as a third value, and a first calculated for each attendee for each attendee A step of calculating an average value of 1 as a fourth value, and for each attendee, an attendee who has a first value of 0 among attendees is identified, and the identified attendee is identified To the second value, to the same person for the third value The fifth value may further include the steps of calculating by multiplying the ratio of the fourth value of are. The score calculation step described above is calculated for the attendees whose first value is 0 when the attendees whose first value is 0 among the attendees are identified. Calculating a score by calculating the sum of the fifth values and calculating the sum of the sum of the fifth values and the sum of the first values calculated for attendees whose first value is not 0 May be included.

  In this method, if you have attended any attendee of a specific meeting, you will be identified as the attendee and the first value will be calculated in relation to the attendee. The first value is not calculated in relation to an attendee who has no attendance, and is zero. In such a case, by calculating the fifth value and using it for calculating the score, the score of those who have many attendees who have not attended the meeting will be smaller, and it will be easier to identify them as meeting facilitators. It eliminates irrationalities.

  Further, the computer can access a speech time storage unit that stores the speech time of the attendee in association with the conference ID and the user ID of the attendee of the conference, and the first calculation step described above includes the attendance For each planner, the speech time associated with the user ID of the prospective attendee and the conference ID is specified, and the first correction is made for each conference using the ratio of the specified speech time to the specified actual time And calculating the index value by multiplying the ratio between the specified actual time and the specified scheduled time by the first correction value, and the second calculation step described above includes The speech time associated with the user ID of the prospective attendee and the identified conference ID is specified, and the second correction value is set for each conference using the ratio of the specified speech time with respect to the specified actual time. Calculation , It may include a step of calculating an index value by multiplying the second correction value to the ratio of the estimated time identified as specified actual times.

  Talk time is an indicator of the positiveness of participation in discussions. Therefore, by calculating the index value reflecting the speech time, it is possible to more appropriately determine whether it is suitable for the meeting facilitator.

  In addition, the attendance meeting identification step described above identifies, for each prospective attendee, the conference ID associated with the user ID of the prospective attendee from the meeting data storage unit, and the user ID of the prospective attendee and The step of storing in the attendance meeting list storage unit in association with the first list ID, and storing each of the prospective attendees in the attendance meeting list storage unit in association with the user ID of the attendance candidate and the first list ID For each conference ID, the speech time associated with the conference ID and the user ID of the prospective attendee is identified from the speech time storage unit, and the actual time and user associated with the conference ID When the ID is specified from the conference data storage unit, the value obtained by dividing the actual time by the number of the user IDs is less than the specified speech time, and the determination result is affirmative A step of storing the meeting ID in the attendance meeting list storage unit in association with the user ID and the second list ID of the attendee, and for each attendee, the user ID of the attendee and the second For each conference ID stored in the attendance conference list storage unit in association with one list ID, the actual time and the scheduled time associated with the conference ID are specified from the conference data storage unit, and the actual time is It is determined whether the time is less than the scheduled time, and if the determination result is affirmative, the conference ID is stored in the attendance conference list storage unit in association with the user ID of the attendee and the third list ID. For each prospective attendee, for each conference ID stored in the attendance conference list storage unit in association with the user ID and the second list ID of the prospective attendee, the conference I The actual time and the scheduled time associated with are identified from the meeting data storage unit, and it is determined whether the actual time is longer than the scheduled time. If the determination result is affirmative, the meeting ID is the attendance And the step of storing in the attendance meeting list storage unit in association with the user ID of the prospective person and the fourth list ID, the extraction step for each prospective attendee, The conference ID associated with the list ID or the fourth list ID is identified from the attendance conference list storage unit, and the user ID of the attendee associated with the identified conference ID is extracted from the conference data storage unit The step of performing may be included.

  In this way, it is determined whether the actual time is longer than the scheduled time for a meeting in which the speaking time of the scheduled attendee is longer than the average of the speaking time of the attendees of the meeting. If the scheduled time of the meeting is relatively short but the scheduled time of the meeting is exceeded, the person who was present is considered unsuitable as a meeting facilitator in relation to the scheduled attendance. Because.

  A program for causing a computer to perform the processing according to the above method can be created. The program can be a computer-readable storage medium such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, a hard disk, or the like. It is stored in a storage device. The intermediate processing result is temporarily stored in a storage device such as a main memory.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Appendix 1)
A meeting data storage unit that stores meeting data including an attendee ID that is a user ID of a meeting attendee, a scheduled time of the meeting, and an actual time required for the meeting, and a specific meeting scheduled to be held A meeting facilitator selection method executed by a computer accessible to a prospective attendee list storage unit that stores a prospective attendee ID that is a user ID of a prospective attendee,
A specifying step of referring to the conference data storage unit and specifying conference data including at least one of the attendee IDs stored in the attendee list storage unit;
A divergence value calculating step for calculating a divergence value indicating a divergence degree between the scheduled time and the actual time based on the scheduled time and the actual time included in the identified meeting data;
A score calculating step for calculating the sum of the calculated divergence values for each of the attendee IDs;
A facilitator identifying step for identifying a conference facilitator from prospective attendees of the specific conference based on the calculated sum;
Meeting facilitator selection method including

(Appendix 2)
For all the conference data specified in the specifying step, the attendee ID included in the conference data is specified, and the union of the specified attendee IDs is stored in the attendee list storage unit as the attendee ID Further including
In the score calculating step,
Calculating the sum of the divergence values for each attendee ID stored in the attendee list storage unit;
In the facilitator specifying step,
The meeting facilitator selection method according to appendix 1, wherein a meeting facilitator is identified from the attendees based on the calculated sum.

(Appendix 3)
In the deviation value calculating step,
Calculating the divergence value for each pair of the attendee ID stored in the attendee list storage unit and the attendee ID stored in the attendee list storage unit;
In the score calculating step,
The meeting facilitator selection method according to appendix 2, wherein the calculated sum of the deviation values is calculated for each of the attendee IDs stored in the attendee list storage unit.

(Appendix 4)
In the score calculating step,
For the pair for which the divergence value has not been calculated, a value used as the divergence value of the pair is calculated based on an average value of the divergence values calculated in the divergence value calculation step. The meeting facilitator selection method described.

(Appendix 5)
In the deviation value calculating step,
The meeting facilitator selection method according to appendix 1, wherein a ratio between the scheduled time and the actual time is calculated for each meeting, and the deviation value is calculated using an average value of the calculated ratios.

(Appendix 6)
A device for selecting a facilitator for a specific meeting scheduled to be held,
A conference data storage unit that stores conference data including an attendee ID that is a user ID of a conference attendee, a scheduled time of the conference, and an actual time required for the conference, and a specific scheduled to be held Identifying means for identifying meeting data including at least one of the attendee IDs stored in the attendee list storage unit that stores attendee IDs, which are user IDs of prospective attendees;
Based on the scheduled time and the actual time included in the identified meeting data, a divergence value indicating a divergence degree between the scheduled time and the actual time is calculated, and the sum of the calculated divergence values is calculated for each attendee ID. A score calculating means for calculating;
Based on the calculated sum, facilitator identifying means for identifying a conference facilitator from attendees of the specific conference;
A meeting facilitator selection device having

(Appendix 7)
A program for selecting facilitators for a specific meeting that is scheduled to be held,
A conference data storage unit that stores conference data including an attendee ID that is a user ID of a conference attendee, a scheduled time of the conference, and an actual time required for the conference, and a specific scheduled to be held A specifying step of identifying meeting data including at least one of the attendee IDs stored in the attendee list storage unit that stores attendee IDs that are user IDs of attendees of the meeting;
A divergence value calculating step for calculating a divergence value indicating a divergence degree between the scheduled time and the actual time based on the scheduled time and the actual time included in the identified meeting data;
A score calculating step for calculating the sum of the calculated divergence values for each of the attendee IDs;
A facilitator identifying step for identifying a conference facilitator from prospective attendees of the specific conference based on the calculated sum;
Meeting facilitator selection program to make the computer execute.

(Appendix 8)
A meeting data storage unit that stores the user ID of the attendee of the meeting, the scheduled time of the meeting, and the actual time required for the meeting in association with the meeting ID, and the attendee of a specific meeting scheduled to be held A meeting facilitator selection method executed by a computer accessible to the attendee list storage unit, the attendance conference list storage unit, the attendee list storage unit, and the score storage unit,
An attendance meeting identification step of identifying a meeting ID associated with a user ID of the prospective attendee stored in the attendance list storage section from the meeting data storage section and storing the meeting ID in the attendance meeting list storage section; ,
Extracting the attendee's user ID associated with the conference ID stored in the attendance conference list storage unit from the conference data storage unit;
For each of the attendees, a specific step of identifying a user ID obtained by removing the user ID of the attendee from the extracted user ID of the attendee,
Storing all the user IDs identified in the identifying step in the attendee list storage unit as duplicate user IDs by removing duplication; and
For each attendee, for each attendee, the conference ID associated with the user ID of the attendee and the user ID of the attendee is identified from the conference data storage unit, and the identified The actual time and the scheduled time of the conference related to the conference ID are identified from the conference data storage unit, and an index value representing the degree of deviation between the actual time and the scheduled time is determined using the ratio between the actual time and the scheduled time. A first calculation step of calculating a first value that is calculated every time and is a mean value of the index values;
For each of the attendees, a score indicating a degree suitable for the facilitator of the specific meeting is calculated by obtaining the sum of the first values calculated for each attendee, and stored in the score storage unit A score calculating step;
Identifying a fellow member whose score stored in the score storage unit is equal to or less than a predetermined threshold or a fellow member in a higher predetermined order when the scores are arranged in ascending order as a meeting facilitator;
Meeting facilitator selection method including

(Appendix 9)
For each prospective attendee, the conference ID associated with the user ID of the prospective attendee is specified from the conference data storage unit, and the actual and scheduled times of the conference relating to the specified conference ID are specified in the conference. A second calculation step that specifies from the data storage unit, calculates the index value for each meeting using a ratio of the actual time and the scheduled time, and calculates a second value that is an average value of the index values; ,
Calculating an average value of the second values calculated for each prospective attendee as a third value;
For each of the attendees, calculating an average value of the first values calculated for each scheduled attendee as a fourth value;
For each of the attendees, the attendees whose first value is 0 among the attendees are identified, and the second value for the identified attendee is set to the second value for the third attendant Calculating a fifth value by multiplying the proportion of the fourth value for the attendee;
Further including
The score calculating step includes:
The sum of the fifth values calculated for the attendees whose first value is 0 when the attendees who have the first value of 0 among the prospective attendees is identified. And calculating the score by obtaining the sum of the sum of the fifth values and the sum of the first values calculated for the attendees whose first value is not 0. The meeting facilitator selection method described.

(Appendix 10)
The computer can access a conference time and a speech time storage unit that stores a speech time of the attendee in association with the conference ID and the user ID of the attendee of the conference,
The first calculating step includes:
For each prospective attendee, the speech time associated with the user ID of the prospective attendee and the conference ID is specified, and the ratio of the specified speech time to the specified actual time is used for each conference. Calculating a first correction value, and calculating the index value by multiplying the ratio of the specified actual time and the specified scheduled time by the first correction value,
The second calculating step includes
The speech time associated with the user ID of the prospective attendee and the identified conference ID is identified, and the second for each conference using the ratio of the identified speech time to the identified actual time. The meeting facilitator selection method according to appendix 9, further comprising the step of calculating a correction value and calculating the index value by multiplying the ratio of the specified actual time to the specified scheduled time by the second correction value. .

(Appendix 11)
The attendance meeting specifying step includes:
For each prospective attendee, a conference ID associated with the user ID of the prospective attendee is identified from the conference data storage unit, and is associated with the user ID and the first list ID of the prospective attendee. Storing in the attendance meeting list storage unit;
For each prospective attendee, for each conference ID stored in the attendance conference list storage unit in association with the user ID and the first list ID of the prospective attendee, the conference ID and the prospective attendee The speech time associated with the user ID is identified from the speech time storage unit, the actual time and user ID associated with the conference ID are identified from the conference data storage unit, and the actual time is It is determined whether the value divided by the number of user IDs is equal to or less than the specified speech time. If the determination result is affirmative, the conference ID is assigned to the user ID of the prospective attendee and the second list. Storing in the attendance meeting list storage unit in association with the ID;
Each attendee is associated with the conference ID for each conference ID stored in the attendance conference list storage unit in association with the user ID of the attendee and the first list ID. The actual time and the scheduled time are identified from the conference data storage unit, and it is determined whether the actual time is less than or equal to the scheduled time. If the determination result is affirmative, the conference ID is assigned to the user of the prospective attendee Storing in the attendance meeting list storage unit in association with the ID and the third list ID;
Each attendee is associated with the conference ID for each conference ID stored in the attendance conference list storage unit in association with the user ID of the attendee and the second list ID. The actual time and the scheduled time are specified from the conference data storage unit, and it is determined whether the actual time is longer than the scheduled time. If the determination result is affirmative, the conference ID is set as the user ID of the scheduled attendee. And storing in the attendance meeting list storage unit in association with the fourth list ID;
Including
The extraction step comprises:
For each prospective attendee, the attendee ID and the conference ID associated with the third list ID or the fourth list ID are identified from the attendance conference list storage unit, The meeting facilitator selection method according to supplementary note 10, including a step of extracting a user ID of an attendee associated with the meeting ID from the meeting data storage unit.

(Appendix 12)
The conference data storage unit stores the user ID of the prospective attendee of the conference and the scheduled time of the conference in association with the conference ID of the conference scheduled to be held,
Receiving an input of a conference ID of the specific conference;
Identifying a user ID of a prospective attendee associated with the input conference ID of the specific conference from the conference data storage unit, and storing the user ID in the prospective attendee list storage unit;
The meeting facilitator selection method according to any one of appendices 8 to 11, further including:

(Appendix 13)
A device for selecting a facilitator for a specific meeting scheduled to be held,
Stores the user ID of the attendee of the specific meeting from the meeting data storage unit that stores the user ID of the meeting attendee, the scheduled time of the meeting, and the actual time required for the meeting in association with the meeting ID. An attendance meeting identifying means for identifying the meeting ID associated with the user ID stored in the attendee list storage section and storing the meeting ID in the attendance meeting list storage section;
The attendee's user ID associated with the conference ID stored in the attendance meeting list storage unit is extracted from the conference data storage unit, and for each prospective attendee, from the extracted attendee's user ID A attendee identification unit that identifies a user ID excluding the user ID of the prospective attendee and stores all the identified user IDs in the attendee list storage unit as user IDs of the attendees by removing duplication ,
For each attendee, for each attendee, the conference ID associated with the user ID of the attendee and the user ID of the attendee is identified from the conference data storage unit, and the identified The actual time and the scheduled time of the conference related to the conference ID are identified from the conference data storage unit, and an index value representing the degree of deviation between the actual time and the scheduled time is determined using the ratio between the actual time and the scheduled time. It is suitable for the facilitator of the specific meeting by calculating every time, calculating a first value that is an average value of the index values, and calculating the sum of the first values calculated for each attendee. A score calculating means for calculating a score representing the degree and storing the score in a score storage unit;
Display processing means for identifying a co-having person whose score stored in the score storage unit is a predetermined threshold or less or a co-having person who is in a higher predetermined order when the scores are arranged in ascending order, as a meeting facilitator;
A meeting facilitator selection device having

(Appendix 14)
A program for selecting facilitators for a specific meeting that is scheduled to be held,
Stores the user ID of the attendee of the specific meeting from the meeting data storage unit that stores the user ID of the meeting attendee, the scheduled time of the meeting, and the actual time required for the meeting in association with the meeting ID. An attendance meeting identification step for identifying a meeting ID associated with the user ID stored in the attendee list storage section and storing the meeting ID in the attendance meeting list storage section;
Extracting the attendee's user ID associated with the conference ID stored in the attendance conference list storage unit from the conference data storage unit;
For each of the attendees, a specific step of identifying a user ID obtained by removing the user ID of the attendee from the extracted user ID of the attendee,
Storing all the user IDs identified in the identifying step in the attendee list storage unit as duplicate user IDs with duplicates removed;
For each attendee, for each attendee, the conference ID associated with the user ID of the attendee and the user ID of the attendee is identified from the conference data storage unit, and the identified The actual time and the scheduled time of the conference related to the conference ID are identified from the conference data storage unit, and an index value representing the degree of deviation between the actual time and the scheduled time is determined using the ratio between the actual time and the scheduled time. A first calculation step of calculating a first value that is calculated every time and is a mean value of the index values;
A score representing the degree suitable for the facilitator of the specific meeting by calculating the sum of the first values calculated for each of the attendees for each attendee, and storing the score in the score storage unit A calculation step;
Identifying a fellow member whose score stored in the score storage unit is equal to or less than a predetermined threshold or a fellow member in a higher predetermined order when the scores are arranged in ascending order as a meeting facilitator;
Meeting facilitator selection program to make the computer execute.

DESCRIPTION OF SYMBOLS 100 Facilitator selection apparatus 101 Selection request reception part 103 Attendance person list storage part 105 Attendance meeting specification part 107 Attendance meeting list storage part 109 Attendee specification part 111 Attendee list storage part 113 Score calculation part 115 Score storage part 117 Display processing part 120 Input unit 130 Output unit 140 User DB 150 Conference DB
160 Speech time DB

Claims (7)

A meeting data storage unit that stores meeting data including an attendee ID that is a user ID of a meeting attendee, a scheduled time of the meeting, and an actual time required for the meeting, and a specific meeting scheduled to be held A meeting facilitator selection method executed by a computer accessible to a prospective attendee list storage unit that stores a prospective attendee ID that is a user ID of a prospective attendee,
A specifying step of referring to the conference data storage unit and specifying conference data including at least one of the attendee IDs stored in the attendee list storage unit;
A divergence value calculating step for calculating a divergence value indicating a divergence degree between the scheduled time and the actual time based on the scheduled time and the actual time included in the identified meeting data;
A score calculating step for calculating the sum of the calculated divergence values for each of the attendee IDs;
A facilitator identifying step for identifying a conference facilitator from prospective attendees of the specific conference based on the calculated sum;
Meeting facilitator selection method including For all the conference data specified in the specifying step, the attendee ID included in the conference data is specified, and the union of the specified attendee IDs is stored in the attendee list storage unit as the attendee ID Further including
In the score calculating step,
Calculating the sum of the divergence values for each attendee ID stored in the attendee list storage unit;
In the facilitator specifying step,
The conference facilitator selection method according to claim 1, wherein a conference facilitator is identified from the attendees based on the calculated sum. In the deviation value calculating step,
Calculating the divergence value for each pair of the attendee ID stored in the attendee list storage unit and the attendee ID stored in the attendee list storage unit;
In the score calculating step,
The meeting facilitator selection method according to claim 2, further comprising: calculating a total sum of the calculated deviation values for each of the attendee IDs stored in the attendee list storage unit. In the score calculating step,
The pair used as the divergence value of the pair is calculated based on an average value of the divergence values calculated in the divergence value calculation step for the pair for which the divergence value is not calculated. 3. A method for selecting a meeting facilitator according to 3. In the deviation value calculating step,
The meeting facilitator selection method according to claim 1, wherein a ratio between the scheduled time and the actual time is calculated for each meeting, and the deviation value is calculated using an average value of the calculated ratios. A device for selecting a facilitator for a specific meeting scheduled to be held,
A conference data storage unit that stores conference data including an attendee ID that is a user ID of a conference attendee, a scheduled time of the conference, and an actual time required for the conference, and a specific scheduled to be held Identifying means for identifying meeting data including at least one of the attendee IDs stored in the attendee list storage unit that stores attendee IDs, which are user IDs of prospective attendees;
Based on the scheduled time and the actual time included in the identified meeting data, a divergence value indicating a divergence degree between the scheduled time and the actual time is calculated, and the sum of the calculated divergence values is calculated for each attendee ID. A score calculating means for calculating;
Based on the calculated sum, facilitator identifying means for identifying a conference facilitator from attendees of the specific conference;
A meeting facilitator selection device having A program for selecting facilitators for a specific meeting that is scheduled to be held,
A conference data storage unit that stores conference data including an attendee ID that is a user ID of a conference attendee, a scheduled time of the conference, and an actual time required for the conference, and a specific scheduled to be held A specifying step of identifying meeting data including at least one of the attendee IDs stored in the attendee list storage unit that stores attendee IDs that are user IDs of attendees of the meeting;
A divergence value calculating step for calculating a divergence value indicating a divergence degree between the scheduled time and the actual time based on the scheduled time and the actual time included in the identified meeting data;
A score calculating step for calculating the sum of the calculated divergence values for each of the attendee IDs;
A facilitator identifying step for identifying a conference facilitator from prospective attendees of the specific conference based on the calculated sum;
Meeting facilitator selection program to make the computer execute.

Images