JP5282602B2 - CONFERENCE SUPPORT DEVICE, CONFERENCE SUPPORT PROGRAM, AND CONFERENCE SUPPORT METHOD - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a participant to easily set a schedule of a conference date by predicting an extended period of time of an unheld conference. <P>SOLUTION: In a conference support device 700, a receiving part 701 receives information on an unheld conference having information on a plurality of participants and emcee information of the unheld conference and registers the received information in a conference database 200, an extracting part 703 extracts information on a held conference in which emcee information is the same as the emcee information of the unheld conference and agenda information is the same as agenda information of the information on the unheld conference from the conference database 200, and an output part 708 obtains a time difference between a scheduled time and a real conference time from the extracted information on the held conference and outputs the time difference as the extended period of time of the information on the unheld conference. <P>COPYRIGHT: (C)2010,JPO&amp;INPIT

Description

  The present disclosure relates to a conference support apparatus, a conference support program, and a conference support method that support time setting of a conference organizer.

  Conventionally, the time of an unheld meeting may be significantly extended from the scheduled time. Therefore, a technology that calculates the average meeting time from the number of meeting attendees, the number of meeting topics, and the past meeting time, and predicts the meeting time based on the calculated average meeting time and the understanding level of the meeting attendees. Is known (for example, see Patent Document 1 below).

JP 2004-295520 A

  However, depending on the compatibility of the attendees, there was a problem that the meeting time was extended at each meeting. And even if the difference of opinion between attendees occurred, there was a problem that the meeting time changed depending on the presence or absence of the presenter who can organize the meeting.

  In addition, with the technology that predicts the meeting time based on the average meeting time and the level of understanding of the meeting attendees, the effect of the combination of attendees and which attendee is the host is unknown, and the predicted meeting time There was a problem that was inaccurate. Therefore, if it is necessary to schedule a different meeting or going out after the target meeting because the meeting time is extended, there is a problem that it is difficult to make a schedule by extending the unheld meeting. there were.

  Further, depending on the agenda, there are cases where the meeting time is always extended or not extended, and there is a problem that the scheduled time or extension time of the calculated meeting time is incorrect. And even if it is the same agenda, there was a problem that the meeting contents and conclusions did not converge and the meeting time was extended due to the difference in the points of discussion for each attendee.

  In order to eliminate the above-described problems caused by the conventional technology, the disclosed technology increases the length of time for an unsented meeting based on the information on attendees, moderator information, agenda, and the degree of disagreement between the meetings. It is an object of the present invention to provide a conference support apparatus, a conference support program, and a conference support method that can predict and make it easier for attendees to schedule.

  In order to solve the above-described problems and achieve the purpose, the disclosed technology is scheduled for each held meeting and a reception unit that accepts information on unheld meetings including information on a plurality of attendees and presenter information of held meetings. The attendee information of the non-held meeting information received by the receiving means with reference to the database storing the held meeting information having the time difference between the meeting time and the actual meeting time, the attendee information and the moderator information To obtain the time difference between the extraction means for extracting the held meeting information that is the same as the presenter information of the unconventional meeting information and the held meeting information extracted by the extraction means. And an output means for outputting as an extended time of an unheld meeting.

  According to the disclosed technology, it is possible to predict the extended time of a non-held meeting based on the pair of attendee information, the moderator information, the agenda, and the degree of disagreement between points from the held meeting information.

  According to the main conference support device, the conference support program, and the conference support method, there is an effect that it is possible to make it easier for an attendee to schedule by predicting the extended time of an unheld conference.

It is explanatory drawing which shows the example of an output of extension time. It is explanatory drawing which shows the memory content of a meeting database. It is explanatory drawing which shows the memory content of a performance database. It is explanatory drawing which shows the memory content of a conference argument database. It is explanatory drawing which shows the memory content of a contention ID database. It is a block diagram which shows the hardware constitutions of the meeting assistance apparatus concerning embodiment. It is a block diagram which shows the functional structure of a meeting assistance apparatus. It is explanatory drawing which shows the input screen of unheld meeting information. It is explanatory drawing which shows the example by which the non-held meeting information is described in the meeting database. It is explanatory drawing which shows the example of holding notification of an unheld meeting. It is explanatory drawing which shows produced | generated argument ID501. It is explanatory drawing which shows the example by which K007 is described in the meeting point database 400. FIG. It is explanatory drawing which shows the example in which the discrepancy degree 304 of unheld meeting information is described. It is explanatory drawing which shows the memory content of the meeting database 200 after meeting holding. It is explanatory drawing which shows the memory content of the results database 300 after meeting holding. 10 is a flowchart showing a meeting support processing procedure of the meeting support apparatus 700. It is a flowchart which shows the process sequence of an issue point collection process. It is a flowchart which shows the process sequence of a calculation process of a mismatch degree. It is a flowchart which shows the process sequence of the setting process of extension time. It is a flowchart which shows the search process of a predetermined | prescribed discrepancy degree.

  Exemplary embodiments of a conference support apparatus, a conference support program, and a conference support method according to the present invention will be explained below in detail with reference to the accompanying drawings.

(Embodiment)
In the present embodiment, the extension time of an unheld meeting is predicted based on the degree of inconsistency between attendee information, moderator information, agenda information, and issue information. In addition, the maximum extension time for unsent meetings is predicted. FIG. 1 shows an example in which a maximum extension time is notified to an unheld meeting.

  FIG. 1 is an explanatory diagram illustrating an output example of the extension time. The extended time notification 100 includes a conference ID (IDentification) 101, an attendee list 102, a moderator 103, an agenda list 104, and an extended time 105. The conference ID 101 is information for identifying a conference allocated to each of a non-held conference and a held conference. In the extended time notification 100, the conference ID 101 is K007. In the present embodiment, K007 is the conference ID 101 of the unheld conference.

  The attendee list 102 includes all attendee information of the conference ID 101: K007. In the extended time notification 100, the attendee list 102 is “A, B, C”. Specifically, “A, B, C” is, for example, the name or employee number of the attendee. Next, the moderator 103 is the moderator information of the conference ID 101: K007. Specifically, it is attendee information included in the attendee list 102. In the extended time notification 100, the moderator 103 is A.

  The agenda list 104 is all agenda information of the conference. Agenda information is information indicating the title of each meeting. In the extension time notification 100, the agenda list 104 is “α”. Next, the extended time 105 is information set and output according to the present embodiment. Specifically, it is the time that is expected to be extended from the scheduled time of the unheld meeting. In the extension time notification 100, the extension time 105 is predicted to be 30 minutes. The extended time notification 100 is stored in the storage device.

(Conference database)
FIG. 2 is an explanatory diagram showing the contents stored in the conference database. The conference database 200 is a database that stores information for specifying a conference. The conference database 200 includes a conference ID 101, an attendee list 102, a moderator 103, an agenda list 104, a scheduled time 201, an actual conference time 202, a conference name 203, a date / time 204, and a place 205. The value of each field item is held as a record for each meeting. Hereinafter, the record for each conference is referred to as “conference information”.

  First, the scheduled time 201 is the time of a meeting scheduled before the meeting is held. The actual meeting time 202 describes the meeting time input after the meeting is held. In the conference IDs 101: K001 to K006 of the conference database 200, the actual conference time 202 is described, respectively. Therefore, it turns out that meeting ID101: K001-K006 is held meeting information.

  The conference name 203 is the name of each conference. Specifically, for example, the conference name 203 is “design conference”. The agenda information is, for example, “XX product design meeting” and “XX product design meeting”. In this way, the conference name 203 is the title of the higher-level conference of all the agenda information. Therefore, if the agenda information is single, it is the same as the conference name 203. The date 204 is information indicating the date and time of each meeting.

  Further, the issue point information is the central content discussed with respect to the agenda information. For example, the issue point information is “determination of person in charge” or “determination of due date”. A place 205 is information on a place where each meeting is held. The conference database 200 is stored in a storage device or a storage device of an accessible external computer.

(Result database)
FIG. 3 is an explanatory diagram showing the contents stored in the performance database. The result database 300 is a database that stores the results of the conference. The result database 300 holds conference information of held conferences. Specifically, the performance database 300 includes the conference ID 101, the attendee a301, the attendee b302, the facilitator 103, the agenda 303, the discrepancy degree 304, and the risk time 305 as field items. Holds the value of each field item as a record. The attendee a301 and the attendee b302 are a pair of attendee information. The discrepancy degree 304 indicates the degree of deviation between the issue point information of the attendee a301 and the issue point information of the attendee b302. The discrepancy degree 304 predicts a shift in the issue information between the attendee a301 and the attendee b302. A method for calculating the degree of mismatch 304 will be described later.

  The risk time 305 is a time difference between the actual meeting time 202 and the scheduled time 201. However, when the scheduled time 201 is larger than the actual meeting time 202, the risk time 305 is set to 0 [minutes]. For example, the scheduled time 201 of the conference ID 101: K006 is 90 [minutes], and the actual conference time 202 is 110 [minutes]. Therefore, the risk time 305 of the conference ID 101: K006 is 20 [minutes].

  For example, the scheduled time 201 of the conference ID 101: K003 is 60 [minutes], and the actual conference time 202 is 50 [minutes]. In the case of the conference ID 101: K003, the actual conference time 202 is shorter than the scheduled time 201. Therefore, the risk time 305 of the conference ID 101: K003 is 0 [minutes]. The result database 300 is stored in a storage device or a storage device of an accessible external computer.

  For example, the degree of mismatch 304 between A and B attending the meeting with the meeting ID 101: K002 is 0.5. The risk time 305 is 0 [minutes]. Therefore, the conference ID 101: K002 indicates that the point information of A and B does not match, but the conference has not been extended.

  Further, for example, the degree of mismatch 304 between A and B attending the conference ID 101: K004 is 0.5. The risk time 305 is 20 minutes. Therefore, the conference ID 101: K004 indicates that the point information of A and B is inconsistent and the conference has been extended.

(Discussion point database)
FIG. 4 is an explanatory diagram showing the stored contents of the meeting discussion point database. The conference issue point database 400 is a database that stores information for specifying a conference issue point. The conference issue point database 400 uses the conference ID 101, the attendee 401, the agenda 303, and the issue ID list 402 as field items, and holds the value of each field item as a record for each conference. The attendee 401 is attendee information in the attendee list 102 of the conference ID 101. The issue ID list 402 is a list including IDs of issue information corresponding to the agenda 303 for each attendee 401 of the conference ID 101. The discussion point database 400 is stored in a storage device or a storage device of an accessible external computer.

(Discussion ID database)
FIG. 5 is an explanatory diagram showing the contents stored in the issue ID database. The issue ID database 500 is a database that identifies the type of issue. The issue ID database 500 uses the issue ID 501 and the issue 502 as field items, and holds the value of each field item as a record for each meeting. The issue point ID 501 is an ID corresponding to each issue point 502. The issue ID 501 described in the issue ID list 402 of the meeting discussion point database 400 described above is described in the issue ID database 500.

  For example, when the issue ID list 402 of the meeting discussion point database 400 is S001, S001 is retrieved from the issue ID database 500, and it is found that the issue 502 of the meeting is “determination of person in charge”. The point ID database 500 is stored in a storage device or a storage device of an accessible external computer.

(Hardware configuration of conference support device)
FIG. 6 is a block diagram of a hardware configuration of the conference support apparatus according to the embodiment. In FIG. 6, the conference support device includes a CPU (Central Processing Unit) 601, a ROM (Read-Only Memory) 602, a RAM (Random Access Memory) 603, a magnetic disk drive 604, a magnetic disk 605, and an optical disk drive. 606, an optical disk 607, a display 608, an I / F (Interface) 609, a keyboard 610, a mouse 611, a scanner 612, and a printer 613. Each component is connected by a bus 600.

  Here, the CPU 601 governs overall control of the conference support apparatus. The ROM 602 stores programs such as a boot program. The RAM 603 is used as a work area for the CPU 601. The magnetic disk drive 604 controls the reading / writing of the data with respect to the magnetic disk 605 according to control of CPU601. The magnetic disk 605 stores data written under the control of the magnetic disk drive 604.

  The optical disk drive 606 controls the reading / writing of the data with respect to the optical disk 607 according to control of CPU601. The optical disk 607 stores data written under the control of the optical disk drive 606, and causes the computer to read data stored on the optical disk 607.

  A display 608 displays data such as a document, an image, and function information as well as a cursor, an icon, or a tool box. As the display 608, for example, a CRT, a TFT liquid crystal display, a plasma display, or the like can be adopted.

  An interface (hereinafter abbreviated as “I / F”) 609 is connected to a network 614 such as a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet through a communication line, and the other via the network 614. Connected to other devices. The I / F 609 manages an internal interface with the network 614 and controls data input / output from an external device. For example, a modem or a LAN adapter can be employed as the I / F 609.

  The keyboard 610 includes keys for inputting characters, numbers, various instructions, and the like, and inputs data. Moreover, a touch panel type input pad or a numeric keypad may be used. The mouse 611 performs cursor movement, range selection, window movement, size change, and the like. A trackball or a joystick may be used as long as they have the same function as a pointing device.

  The scanner 612 optically reads an image and takes in the image data into the conference support apparatus. Note that the scanner 612 may have an OCR (Optical Character Reader) function. The printer 613 prints image data and document data. As the printer 613, for example, a laser printer or an ink jet printer can be employed.

(Functional configuration of conference support device)
Next, the functional configuration of the conference support apparatus will be described. FIG. 7 is a block diagram illustrating a functional configuration of the conference support apparatus. The meeting support apparatus 700 includes a reception unit 701, a selection unit 702, an extraction unit 703, a determination unit 704, a calculation unit 705, a search unit 706, a setting unit 707, and an output unit 708. is there. Specifically, the functions (accepting unit 701 to output unit 708) serving as the control unit are, for example, programs stored in a storage device such as the ROM 602, RAM 603, magnetic disk 605, and optical disc 607 shown in FIG. The function is realized by executing the function or by the I / F 609.

  First, the reception unit 701 receives unheld meeting information including a plurality of attendee information and moderator information of an unheld meeting. Specifically, for example, the organizer inputs information on a non-held meeting to be held on the input screen.

  Specifically, for example, when non-held conference information is input, the CPU 601 accesses the conference database 200 to search for an unassigned conference ID 101. When the unassigned conference ID 101 is searched, the searched conference ID 101 is generated as the conference ID 101 of the unheld conference, and the input conference name 203, date 204, place 205, agenda 303, The scheduled time 201 and the attendee 401 are substituted. FIG. 8 and FIG. 9 show an example in which the organizer registers the non-held conference information in the conference database 200.

  FIG. 8 is an explanatory diagram showing an input screen for unheld conference information. The input screen 800 includes a conference name input field 801, a date and time input field 802, a place input field 803, an agenda input field 804, a scheduled time input field 805, an attendee input field 806, and a moderator input field 807. It is included.

  For example, the organizer inputs a meeting name input field 801, a date and time input field 802, a place input field 803, an agenda input field 804, a scheduled time input field 805, an attendee input field 806, and a moderator input field 807. Enter each information in. Then, the conference ID 101 of the unheld conference is issued, and the unheld conference information input by the organizer is registered in the conference database 200. FIG. 9 shows an example in which an unheld meeting is described in the meeting database 200.

  FIG. 9 is an explanatory diagram illustrating an example in which unheld conference information is described in the conference database 200. In the conference database 200, K007, which is the conference ID 101 of the unheld conference information, is issued. K007 is the conference ID 101 of the unheld conference information. In the conference database 200, K007 is described. K007 describes conference information excluding the actual conference time 202 (enclosed by a dotted line). Next, after the non-held meeting information is registered in the meeting database 200, the holding of the non-held meeting is notified to each attendee. FIG. 10 shows a holding notification example.

  FIG. 10 is an explanatory diagram illustrating an example of a notification of an unheld meeting. For example, the holding notification 1000 includes a meeting name 203, a date and time 204, a place 205, and an agenda 303. Then, it is shown that all the attendees reply to the organizer on the topic information that they want to discuss on each agenda 303. Specifically, for example, the CPU 601 accesses the conference database 200 and reads the conference name 203, the date and time 204, the location 205, and the agenda 303 of the non-held conference information. Then, the read information on the unheld meeting is output to the template of the holding notification 1000.

  Further, for example, the organizer may manually create the holding notification 1000. For example, the event notice 1000 may be stored in the storage device as a template.

  Next, issue point information is acquired corresponding to each agenda 303 for each attendee 401. Then, the discussion point information is registered in the meeting discussion point database 400 for each attendee 401 of the unheld conference information. For example, the CPU 601 acquires the point information corresponding to the agenda 303 for each attendee 401. Then, the issue point ID 501 of the issue point information acquired from the issue point database 500 is searched.

  For example, the issue point information regarding α of A who attends a non-held meeting is “determination of person in charge” and “determination of department policy”. Specifically, for example, the CPU 601 accesses the storage device and searches the issue ID ID database 500 for the issue ID 501 whose issue 502 is “determination of the person in charge”. Then, the searched S001 is output to the meeting discussion point database 400. Similarly, the “determination of department policy” and the issue point ID 501 of the issue point information for α of B are retrieved and output to the meeting discussion point database 400.

  The issues 502 for C α are “determination of person in charge” and “examination of report contents to customer”. Similarly to the search process in which the A and B issue IDs 501 are searched, the C issue ID 501 is searched.

  Specifically, for example, the CPU 601 accesses the storage device, and searches the issue ID database 500 for the issue ID 501 whose content is “Examination of report content to customer”. However, the issue ID 501 of “examination of report contents to customer” is not registered in the issue ID database 500. Therefore, the CPU 601 generates an issue ID 501 of “Examination of report contents to customer” and outputs it to the issue ID database 500. Then, the generated discussion point ID 501 is output to the meeting discussion point database. FIG. 11 shows the generated issue point ID 501.

  FIG. 11 is an explanatory diagram showing the generated issue point ID 501. In the issue ID database 500, S005 of the issue ID 501 is issued to describe “Review of report contents to customer” of issue 502. Next, FIG. 12 shows the issue ID 501 searched for the agenda 303 for each attendee 401.

  FIG. 12 is an explanatory diagram showing an example in which K007 is described in the meeting discussion point database 400. In the conference issue point database 400, a conference ID 101: K 007 is generated, and the issue point ID 501 searched for the agenda 303 for each attendee 401 is described in the issue ID list 402. Next, a method for setting the extension time 105 and a method for calculating the degree of mismatch 304 will be described.

  Returning to FIG. 7, the selection unit 702 sequentially selects a pair of attendee information from among a plurality of attendee information of the unheld conference information received by the reception unit 701. Specifically, for example, the CPU 601 accesses the conference database 200 to search for K007, which is the conference ID 101 of the unheld conference information, and reads the attendee list 102. Then, a pair of attendees 401 is selected from the attendee list 102.

  For example, from “A, B, C”, a pair of attendee information is selected with A as the attendee a301 and B as the attendee b302. Next, A and C are selected, B and C are selected, and a pair of attendee information is sequentially selected.

  Next, the extraction unit 703 includes at least a part of attendee information of the unheld meeting information received by the receiving unit 701 and is the host information that is the same as the host information of the unheld meeting information. Extract completed conference information.

  Specifically, for example, the CPU 601 accesses the performance database 300 and extracts the conference ID 101 of the held conference information including attendee information. Then, the conference ID 101 that is the same moderator 103 as the moderator 103 of the non-held conference information is extracted from the extracted conference ID 101. The extracted conference ID 101 is stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607.

  In addition, each time the selection unit 702 selects the extraction unit 703, the extraction unit 703 extracts held conference information that includes a pair of attendee information and is the same host information as the moderator information of the unheld conference information. Specifically, for example, the CPU 601 accesses the performance database 300 and extracts the conference ID 101 of the held conference information including a pair of attendee information. Then, the conference ID 101 that is the same moderator 103 as the moderator 103 of the non-held conference information is extracted from the extracted conference ID 101.

  The extracted conference ID 101 is stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607. In this embodiment, the extraction unit 703 will be described using an example including a pair of attendee information.

  For example, A is the moderator 103 of the unheld conference information. When the selected pair of attendee information is A and B, K002 to K004 and K006 are extracted from the conference ID 101 of the record database 300. For example, if the selected pair of attendee information is A and C, K002 to K006 are extracted from the conference ID 101 of the record database 300. Next, when the selected pair of attendee information is B and C, K002-4 and K006 of the result database 300 are extracted.

The conference ID 101 extracted from the conference ID 101 in the results database 300 based on the attendee information and the moderator information is shown below.
Meeting ID 101 for A and B: K002 to K004, K006
Meeting ID 101 for A and C: K002 to K006
Meeting ID 101 for B and C: K002 to K004, K006

  Next, the setting unit 707 acquires a time difference from the held conference information extracted by the extraction unit 703 for each pair of attendee information, and sets it as the extended time 105 of the unheld conference. Specifically, for example, the CPU 601 reads the risk time 305 of the conference ID 101 extracted by accessing the performance database 300. Then, the read risk time 305 is set as the extension time 105.

  For example, when the pair of attendee information is A and B, 0 [minute] of the risk time 305 is read from the meeting ID 101: K002 of the result database 300. The read 0 [minute] is set as the extension time 105 of the non-held conference information. By the same process, the conference IDs 101: K003 to K004 and K006 for A and B, the extension time 105 of the unheld conference information for A and C, and B and C are set.

The extended time 105 set for each pair of attendee information is shown below.
・ Extended time for A and B 105: 0, 0, 20, 20 [minutes]
・ Extended time for A and C 105: 0, 0, 20, 30, 20 [minutes]
・ Extended time for B and C 105: 0, 0, 20, 20 [minutes]

  This predicts an extended time 105 that may occur due to the influence of attendees and presenters. Accordingly, it is possible to make it easier for attendees who attend an unheld meeting to schedule a date. Furthermore, the organizer can set the time for the conference and the reservation time for the materials used in the conference to allow sufficient time.

  In addition, the setting unit 707 acquires a time difference from the held conference information extracted by the extraction unit 703 for each pair of attendee information, and sets the maximum time difference as the extension time 105 of the unheld conference. Specifically, for example, the CPU 601 reads the risk time 305 of the conference ID 101 extracted by accessing the performance database 300. Next, the maximum risk time 305 is searched from the read risk time 305. Then, the retrieved risk time 305 is set as the extension time 105.

The extended time 105 set as the maximum risk time 305 for each pair of attendee information is shown below.
・ Extended time for A and B 105: 20 [minutes]
・ Extended time for A and C: 105: 30 [minutes]
・ Extended time for B and C: 105: 20 [minutes]

The extended time 105 set as the maximum risk time 305 for each meeting information is shown below.
・ Maximum extension time of K007 105: 30 [minutes]

  This predicts the maximum extension time 105 that can occur due to the influence of attendees and presenters. Accordingly, it is possible to make it easier for attendees who attend an unheld meeting to schedule a date.

  More specifically, for example, the CPU 601 reads the risk time 305 of the conference ID 101 extracted by accessing the result database 300. Next, the average of the read risk time 305 is calculated. Then, the calculated risk time 305 is set as the extension time 105.

The extension time 105 set to the average risk time 305 and the extension time 105 of the unheld conference information for each pair of attendee information described above are shown below.
・ Extended time for A and B 105: 10 [minutes]
・ Extended time for A and C 105: 14 [minutes]
・ Extended time for B and C: 105: 10 [minutes]
・ Average extension time of K007 105: 12 [minutes] (rounded to the nearest decimal place)

  Further, each time the selection unit 702 selects the extraction unit 703, the extraction unit 703 further extracts the held conference information in which the agenda information of the unheld conference information is the same agenda information. Specifically, for example, the CPU 601 extracts the conference ID 101 of the held conference information that is the same agenda 303 as the agenda 303 of the non-held conference information from the conference ID 101 of the held conference information in the result database 300. . The extracted conference ID 101 is stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607.

  For example, a conference ID 101 that is the same as the agenda 303 of the conference ID 101: K007 is extracted from the conference ID 101 extracted from the conference ID 101 of the held conference information in the performance database 300 based on the attendee information and the moderator information. To do. The agenda 303 of K007 is α. Therefore, in the case of A and B, K002, K004, and K006 are extracted.

The conference ID 101 extracted from the conference ID 101 of the results database 300 based on the attendee information, the moderator information, and the agenda information is shown below.
Meeting ID 101 for A and B: K002, K004, K006
Meeting ID 101 for A and C: K002, K004 to K006
Meeting ID 101 for B and C: K002, K004, K006

The extended time 105 set for each pair of attendee information of the unheld meeting information based on the extraction result extracted based on the attendee information, the presenter information, and the agenda information is shown below.
・ Extended time for A and B 105: 0, 20, 20 [minutes]
・ Extended time for A and C 105: 0, 20, 30, 20 [minutes]
・ Extended time for B and C 105: 0, 20, 20 [minutes]

The maximum risk time 305 and the average risk time 305 of the conference ID 101 extracted based on the attendee information, the presenter information, and the agenda information are set as the extension time 105 for each pair of attendee information. And the setting result set to the extension time 105 of the unheld conference information is shown below.
・ Maximum extension time for A and B 105: 20 [minutes]
・ Maximum extension time for A and C 105: 30 [minutes]
・ Maximum extension time for B and C 105: 20 [minutes]
・ Maximum extension time of K007 105: 30 [minutes]
-Average extension time for A and B 105: 13 [minutes] (rounded to the nearest decimal place)
-Average extension time for A and C 105: 18 [minutes] (rounded to the nearest decimal place)
・ Average extension time for B and C 105: 13 [minutes] (rounded off to the nearest decimal place)
・ Average extension time of K007 105: 15 [minutes]

  Thereby, the extended time 105 that may occur due to the influence of the agenda 303 is predicted. The accuracy of the set extension time 105 can be improved by adding the agenda 303 to the attendee information and the moderator information and predicting the extension time 105. Accordingly, it is possible to make it easier for attendees who attend an unheld meeting to schedule a date.

  Next, each time the selection unit 702 selects the determination unit 704, the determination unit 704 determines the difference between the issue point information of one attendee information and the issue information of the other attendee information in the pair of attendee information. Specifically, for example, the CPU 601 accesses the meeting discussion point database 400 and reads the issue point ID list 402 of one attendee 401 and the issue point ID list 402 of the other attendee 401. The difference between the read-out point ID 501 of the issue ID list 402 of the one attendee 401 and the issue ID 501 of the issue ID list 402 of the other attendee 401 is determined.

  For example, the total number of different issue point IDs 501 depending on the determination result is set in Y. X is set to the total number of types in the argument ID list 402 of one and the other attendees 401 based on the determination result. The determination result is stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607.

  For example, the case where a pair of attendee information is A and B will be described. The A discussion point ID list 402 of K007 is read from the conference discussion point database 400. The issue ID list 402 of A is S001 and S004. Next, the B discussion point ID list 402 of K007 is read from the meeting discussion point database 400. The issue ID list 402 of B is S002 and S004.

  Y in the case of A and B is 2 because S001 and S002 are different. Next, X in the case of A and B is 3 because there are three types of S001, S002, and S004.

  Next, based on the number of differences determined by the determination unit 704, the calculation unit 705 calculates the degree of disagreement 304 between the issue information of one attendee information and the issue information of the other attendee information. Specifically, for example, the CPU 601 accesses the storage device and reads X and Y. Then, the degree of inconsistency 304 is calculated by dividing Y by X. The calculation formula is shown in the following formula (1). Z is the mismatch degree 304.

Z = Y / X
... (1)

  For example, if the pair of attendee information is A and B, Z is 2 divided by 3 or 0.67. Therefore, in the case of A and B, the mismatch degree 304 is 0.67.

  Then, the output unit 708 outputs the discrepancy degree 304 calculated by the calculation unit 705 to the unheld meeting information. Specifically, for example, the CPU 601 accesses the performance database 300 and searches for the conference ID 101 of the unheld conference information, and searches for the selected pair of attendee information. Then, Z is output to the mismatch ID 304 of the retrieved conference ID 101 and the pair of attendee information. The output result is stored in the storage device. FIG. 13 shows the output result.

  FIG. 13 is an explanatory diagram showing an example in which the discrepancy degree 304 of unheld conference information is described. In the record database 300, the degree of inconsistency 304 is described for each pair of K007 attendee information (indicated by a dotted line). For example, in the case of A and B, the mismatch degree 304 is 0.67. Next, in the case of A and C, the mismatch degree 304 is 0.67. In the case of B and C, the mismatch degree 304 is 1. A mismatch degree 304 of 1 indicates that none of the issue point IDs 501 match.

  As a result, it is possible to predict how much there is between the attendees in the discussion point information of the unheld meeting. Therefore, the organizer can grasp how much the issue point information is different between the attendees, and can consider the unification of issue point information in advance. In addition, the meeting time can be shortened.

  Returning to FIG. 7, the search unit 705 then selects the degree of inconsistency 304 of the pair of attendee information in the non-held conference information output by the output unit 708 from the held conference information extracted by the extraction unit 703. To held conference information with a discrepancy degree 304 within a predetermined range. Specifically, for example, the CPU 601 accesses the storage device and reads the extracted conference ID 101 stored therein. Then, the discrepancy degree 304 of the pair of attendee information in the unheld conference information is read out.

  Next, the difference of the mismatch degree between the read mismatch degree 304 and the read mismatch ID 304 of the paired attendee information of the conference ID 101 is calculated for each read conference ID 101. The calculation formula is shown in the following formula (2).

Difference between discrepancies = | Discrepancy between a pair of attendee information in unconventional conference information
−Incompatibility of a pair of attendee information in held conference information ｜
... (2)

  Then, for example, the CPU 601 searches for the conference ID 101 having the smallest difference in the mismatch degree. Therefore, the retrieved conference ID 101 has the mismatch degree 304 that is the closest value to the mismatch degree 304 of the unheld conference information.

  For example, the CPU 601 reads the risk time 305 of the pair of attendee information of the conference ID 101 searched by accessing the result database 300. The read risk time 305 is added with identification information that can be identified as a search result, and stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607.

  For example, when the pair of attendee information is A and B, the conference IDs 101 extracted based on the attendee information, the moderator information, and the agenda information are K002, K004, and K006. In the case of A and B of K007 (in this embodiment, it is unheld conference information), the result database 300 shows that the degree of mismatch 304 is 0.67. Similarly, the degree of inconsistency 304 of the extracted conference ID 101 is obtained from the result database 300.

  First, in the case of the conference ID 101: K002, the degree of mismatch 304 between A and B is 0.5. Therefore, in the case of A and B, the difference in the degree of mismatch between K002 is 0.17. Next, in the case of the conference ID 101: K004, the mismatch degree 304 between A and B is 0.5. Therefore, in the case of A and B, the difference in the degree of mismatch of K004 is 0.17. In the case of the conference ID 101: K006, the degree of mismatch 304 between A and B is 1. Therefore, in the case of A and B, the difference in the degree of mismatch between K006 is 0.33.

  As a result, the conference ID 101 having the smallest difference in the mismatch degree among the extracted conference IDs 101 is K002 and K004. Therefore, the risk times 305 of K002 and K004 are read from the performance database 300, respectively.

  Similarly, the difference degree difference calculation process, the search process, and the risk time 305 reading process are performed for each pair of attendee information. The processing results of the calculation process of the mismatch degree 304 and the reading process of the risk time 305 are shown below for each pair of attendee information.

First, the calculation result of the difference degree difference calculation process is shown. The following is (Meeting ID 101, Difference in discrepancy).
In the case of A and B: (K002, 0.17), (K004, 0.17), (K006, 0.33)
In the case of A and C: (K002, 0.34), (K004, 0.17), (K005, 0), (K006, 0)
In the case of B and C: (K002, 0.33), (K004, 0.33), (K006, 0.33)

Next, a search processing result for searching for the conference ID 101 having the smallest difference in the mismatch degree is shown.
Meeting ID 101 for A and B: K002, K004
Meeting ID 101 for A and C: K005, K006
Meeting ID 101 for B and C: K002, K004, K006

And the risk time 305 of meeting ID101 searched shows the read result read from the performance database 300. FIG.
・ Risk time for A and B 305: 0, 20 [minutes]
・ Risk time for A and C 305: 30, 20 [minutes]
-Risk time for B and C 305: 0, 20, 20 [minutes]

  Accordingly, the extended time 105 is predicted depending on whether or not there is a deviation in the issue point 502 of the agenda 303. Accordingly, it is easier for attendees who attend an unheld meeting to schedule the date of the meeting.

  Next, the setting unit 707 sets the risk time 305 of the held conference information searched by the search unit 705 as the extension time 105 of the unheld conference information. Specifically, for example, the CPU 601 accesses the storage device and reads the risk time 305 based on the identification information that indicates that the search result is stored. Then, the read risk time 305 is set as the extension time 105 of the non-held meeting information. The setting result is stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607.

  Further, for example, the CPU 601 reads the risk time 305 based on the identification information that indicates that the search result is stored by accessing the storage device. Then, the maximum risk time 305 among the read risk times 305 is set as the extension time 105 of the unheld conference information.

  Further, for example, the CPU 601 reads the risk time 305 based on the identification information that indicates that the search result is stored by accessing the storage device. Then, the average of the read risk time 305 is calculated. Next, the calculation result is set to the extension time 105 of the non-held conference information. The setting result is stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607.

A setting result in which the maximum risk time 305 and the average risk time 305 are set as the extension time 105 for each pair of attendee information and is set as the extension time 105 of the unheld meeting information is shown below.
・ Maximum extension time for A and B 105: 20 [minutes]
・ Maximum extension time for A and C 105: 30 [minutes]
・ Maximum extension time for B and C 105: 20 [minutes]
・ Maximum extension time of K007 105: 30 [minutes]
-Average extension time for A and B 105: 10 [minutes]
-Average extension time for A and C 105: 25 [minutes]
・ Average extension time for B and C 105: 13 [minutes] (rounded off to the nearest decimal place)
・ Average extension time of K007 105: 16 [minutes] (rounded to the nearest decimal place)

  Then, the output unit 708 outputs the extended time 105 set by the setting unit 707. Specifically, for example, the CPU 601 accesses the storage device, reads out the setting result, and outputs it. Examples of the output format include display on the display 608, print output to the printer 613, and transmission to an external device via the I / F 609. Further, it may be stored in a storage device such as the RAM 603, the magnetic disk 605, and the optical disk 607. In the present embodiment, the maximum extension time 105 of K007 is output as the extension time 105 of the extension time notification 100 shown in FIG.

  Next, for example, when an unheld meeting is held, the organizer registers the actual meeting time 202 in the meeting database 200. For example, the CPU 601 calculates the risk time 305 in the performance database 300 based on the scheduled time 201 and the actual conference time 202 in the conference database 200. 14 to 15 show the conference database 200 and the results database 300 after the conference of the non-held conference.

  FIG. 14 is an explanatory diagram showing the contents stored in the conference database 200 after the conference is held. 105 [minutes] is described in the actual conference time 202 of the conference ID 101: K007 (enclosed by a dotted line). Therefore, in this embodiment, K007, which is non-held conference information, is used for setting the extended time 105 of other non-held conference information as held conference information when the actual conference time 202 is described. Next, the result database 300 after the conference is held is shown in FIG.

  FIG. 15 is an explanatory diagram showing the stored contents of the results database 300 after the conference is held. 25 is described in the risk time 305 of the conference ID 101: K007 (enclosed by a dotted line). The scheduled time 201 of the conference ID 101: K007 is 80 [minutes], and the actual conference time 202 is 105 [minutes]. Therefore, the risk time 305 that is the time difference between the scheduled time 201 and the actual meeting time 202 is 25 [minutes].

  Note that the selection unit 702 to the output unit 708 described above, specifically, the CPU 601 executes a program recorded on a recording medium such as the ROM 602, the RAM 603, and the magnetic disk 605 shown in FIG. Realize its function.

(Conference support processing procedure of the conference support apparatus 700)
A meeting support processing procedure of the meeting support apparatus 700 according to the embodiment will be described. FIG. 16 is a flowchart showing a meeting support processing procedure of the meeting support apparatus 700. It is a flowchart which shows estimating the extension time of a non-holding meeting. In FIG. 16, the attendee indicates attendee information, the presenter indicates presenter information, the agenda indicates agenda information, and the issue indicates issue information.

  First, the attendant 701, the agenda, and the scheduled time are acquired by the reception unit 701 (step S1601), and the conference ID of the unheld meeting is issued (step S1602). For example, the organizer inputs attendee information, moderator information, agenda information, and scheduled time on the input screen 800. Next, for example, the computer acquires the attendee list 102, the moderator 103, the agenda list 104, and the scheduled time 201 of the non-held meeting information. Then, the conference ID 101 of the unheld conference is issued and the acquired information is output to the conference database 200.

  Next, the meeting attendance is notified to the attendees attending the non-held meeting (step S1603), the points of issue are obtained from each attendee attending the unheld meeting (step S1604), and the process of collecting the points is executed (step S1604). S1605). For example, each attendee is notified so as to notify the meeting notice 1000 for the agenda for each agenda by indicating the information of the unheld meeting. Next, issues are entered for each agenda by attendees. Then, the computer outputs to the meeting discussion point database 400.

  Next, a mismatch degree calculation process is executed (step S1606). The mismatch degree 304 corresponding to each agenda is calculated for each pair of attendee information by the mismatch degree calculation process. This makes it possible to predict how much of the attendees will be at the issue of the unsent meeting. Therefore, the organizer can grasp how much the issue point information is different between the attendees, and can examine the unification of issue points in advance. In addition, the meeting time can be shortened.

  Next, an extension time setting process is executed (step S1607), the output unit 708 outputs the maximum extension time (step S1608), and the series of processes ends. The extension time 105 is set based on the inconsistency 304 of the attendee information, the moderator information, the agenda information, and the calculated point information calculated by the setting process.

  This predicts the maximum extension time 105 that can occur due to the influence of attendees and presenters. Further, an extended time 105 that may occur due to the influence of the agenda information is predicted. Then, the extension time 105 is predicted depending on whether or not there is a deviation in the agenda information. Accordingly, it is possible to make it easier for attendees who attend an unheld meeting to schedule a date.

  Next, the above-described issue collection processing (step S1605) will be described. FIG. 17 is a flowchart illustrating a processing procedure of the issue point collection processing. In the issue collection process, the issue ID of the issue information acquired for each attendee information is registered in the meeting discussion point database 400. In FIG. 17, the attendee indicates attendee information, and the issue points indicate issue information. In FIG. 17, first, it is determined whether there is an attendee who has not yet been processed for collecting points (step S1701). Thereby, the collection process of the issue point information is ended, or the attendee information for performing the issue point information collection process is selected.

  When it is determined that there is an attendee who has not yet processed the issue collection process (step S1701: Yes), the issue ID corresponding to each issue is searched (step S1702), and whether or not there is an issue with no issue ID. Judgment is made (step S1703). If it is determined that there is an issue point having no issue point ID (step S1703: YES), the issue point ID is generated and the issue point and the issue point ID are stored (step S1704). If the issue ID 501 corresponding to the issue information is not registered in the issue ID database 500, a new issue ID 501 is issued and the issue information is registered in the issue ID database 500.

  Then, the attendee and the issue ID are associated with each other and stored (step S1705). On the other hand, if it is determined that there is no issue point with no issue ID (step S1703: No), the process proceeds to step S1705.

  On the other hand, when it is determined that there is no attendee who has not yet processed the issue collection process (step S1701: No), the process proceeds to step S1606. As a result, the issue ID 501 is registered in the issue ID list 402 for each attendee information in the meeting discussion point database 400. Therefore, the organizer can search the issue points 502 of each attendee based on the conference ID 101 and attendee information. Thus, the organizer can grasp the issue information, notify the attendee of the issue information, and unify the issue information. Therefore, the meeting time can be shortened.

  Next, the above-described mismatch degree calculation process (step S1606) will be described. FIG. 18 is a flowchart illustrating a processing procedure of the mismatch degree calculation processing. In the mismatch degree calculation process, the mismatch degree, which is the ratio at which the point information of the pair of attendee information is shifted, is calculated. In FIG. 18, a pair of attendees indicates a pair of attendee information, and an attendee indicates attendee information.

  In FIG. 18, first, the selection unit 702 determines whether or not there is a pair of attendees whose disagreement degrees are not calculated (step S1801). Accordingly, a pair of attendee information is sequentially selected from the attendee list 102. Then, each time a selection is made, a calculation process of the mismatch degree 304 is executed.

  First, when it is determined that there is a pair of attendees whose disagreement degrees are not calculated (step S1801: Yes), i = 1, j = 1, and Y = 0 are executed (step S1802), and the determination unit 704 Then, it is determined whether the i-th issue ID of one attendee is different from the j-th issue ID of the other attendee (step S1803). If it is determined that the i-th issue ID of one attendant is different from the j-th issue ID of the other attendant (step S1803: Yes), Y = Y + 1 is executed (step S1804), j <the other It is determined whether or not the total number of issue point IDs of the attendees (step S1805).

  On the other hand, if it is determined that the i-th issue ID of one attendee and the j-th issue ID of the other attendant are the same (step S1803: No), the process proceeds to step S1805. If it is determined that j <the total number of issue IDs of the other attendee (step S1805: Yes), j = j + 1 is executed (step S1806), and the process returns to step S1803.

  On the other hand, if it is determined that j is not the total number of issue IDs of the other attendee (step S1805: No), it is determined whether i is less than the total number of issue IDs of the one attendee (step S1807). If it is determined that i <the total number of issue IDs of one attendee (step S1807: YES), i = i + 1, j = 1 is executed (step S1808), and the process returns to step S1803.

  On the other hand, if it is determined that i <not the total number of issue point IDs of one attendant (step S1807: No), X = the total number of issue ID types is executed (step S1809), and the calculation unit 705 causes the mismatch degree = Y / X is executed (step S1810), the pair of attendees and the degree of inconsistency are stored in association with each other (step S1811), and the process returns to step S1801.

  On the other hand, when it is determined that there is no pair of attendees for which the degree of inconsistency is not calculated (step S1801: No), the process proceeds to step S1607. As described above, the mismatch degree 304 is calculated based on the difference between the point information of the pair of attendee information by the mismatch degree calculation process. This makes it possible to predict how much of the attendees will be at the issue of the unsent meeting. Therefore, it is possible for the organizer to grasp how much the issue point is different between the attendees, and to notify the issue point in advance. In addition, the meeting time can be shortened.

  Next, the extension time setting process (step S1607) will be described. FIG. 19 is a flowchart illustrating a processing procedure of the extension time setting process. In the extension time setting process, the extension time of the non-held meeting information is set based on the attendee information, the moderator information, the agenda information, and the degree of mismatch. In FIG. 19, a pair of attendees indicates a pair of attendee information, a moderator indicates moderator information, and an agenda indicates agenda information.

  In FIG. 19, first, the selection unit 702 determines whether there is a pair of attendees who have not set an extension time (step S1901). Accordingly, a pair of attendee information is sequentially selected from the attendee list 102. Then, each time a selection is made, an extension time 105 of the unheld meeting is set.

  When it is determined that there is a pair of attendees for whom the extension time is not set (step S1901: Yes), the extraction unit 703 includes a pair of attendees of the unheld meeting, and the conference ID is the same as the chairperson and agenda. Is extracted (step S1902). This predicts an extended time 105 that may occur due to the influence of attendees and presenters. In addition, the extended time that may occur due to the influence of the agenda information is predicted.

  Next, the search unit 705 executes search processing with a predetermined mismatch degree (step S1903). Thereby, the extended time 105 is predicted depending on whether or not there is a deviation in the agenda information. Then, the maximum risk time is obtained from the retrieved conference ID (step S1904), the risk time is set as an extended time by the setting unit 707 (step S1905), and the pair of attendees are associated with the extended time and stored. (Step S1906), the process returns to Step S1901. Thereby, the maximum extension time is predicted for each pair of attendee information.

  On the other hand, when it is determined that there is no pair of attendees for whom no extension time has been set (step S1901: No), the extension time stored for each pair of attendee information is searched to obtain the maximum extension time. (Step S1907), the maximum extension time of the unheld meeting is set (Step S1908), and the process proceeds to Step S1608. Accordingly, the maximum extension time 105 is predicted based on the pair of attendee information, the moderator information, the agenda information, and the degree of mismatch 304. Accordingly, it is possible to make it easier for attendees who attend an unheld meeting to schedule a date.

  Next, the above-described search process (step S1903) for the predetermined mismatch degree will be described. FIG. 20 is a flowchart showing search processing for a predetermined degree of mismatch. In the search processing of a predetermined mismatch level, the held conference information having a mismatch level 304 with a small difference from the mismatch level 304 of the pair of attendee information of the unheld conference information is searched.

  In FIG. 20, first, k = 1 and P = 1 are executed (step S2001), and it is determined whether k> total number of extracted conference IDs (step S2002). When it is determined that k> the total number of extracted conference IDs (step S2002: Yes), the difference of the kth mismatch level = | the mismatch level of the unheld conference−the mismatch level of the kth conference ID | (Step S2003). Thereby, the difference of each mismatch degree is calculated. Then, it is determined whether or not P ≧ difference level difference (step S2004).

  If it is determined that P ≧ difference difference (step S2004: Yes), it is determined whether P = difference difference (step S2005). If it is determined that P = difference difference (step S2005: Yes), the kth conference ID is additionally stored (step S2006), k = k + 1 is executed (step S2009), and the process returns to step S2002. As a result, it is possible to search for all the conference IDs 101 having the discrepancy degree 304 with a small difference from the discrepancy degree 304 of the unheld conference information.

  On the other hand, if it is determined that P = not a difference in mismatch degree (step S2005: No), P = kth difference in mismatch degree (step S2007), and the mismatch degree between the non-held conference information and the mismatch degree is small. The conference ID stored as a certain conference ID is deleted, the kth conference ID is stored (step S2008), and the process proceeds to step S2009. As a result, all the conference IDs 101 having the discrepancy degree 304 having the smallest difference from the discrepancy degree of the non-held conference information are searched.

  On the other hand, when it is determined that the difference is not P ≧ mismatch degree (step S2004: No), the process proceeds to step S2009. On the other hand, if it is determined that k is not the total number of extracted conference IDs (step S2002: No), the process proceeds to step S1904. Thereby, the extended time 105 is predicted depending on whether or not there is a deviation in the agenda information. Accordingly, it is possible to make it easier for attendees who attend an unheld meeting to schedule a date.

  As described above, according to the conference support device, the conference support program, and the conference support method, the attendee information of at least a part of the attendee information of the unheld conference information includes the presenter information of the unheld conference information and The risk information is acquired by extracting the information of the already held conference. Then, the acquired risk time is output as an extension time of the non-held meeting information. As a result, an extended time that may occur due to the influence of the attendees and the presenter is predicted, and attendees attending the unheld meeting can easily schedule the date of the meeting.

  In addition, if multiple held meeting information that includes at least a part of the attendee information in the unconventional meeting information and is the same as the moderator information in the unheld meeting information is extracted, the maximum risk time is not Output as extended time of conference information. As a result, the maximum extension time that may occur due to the influence of the attendees and the moderator is predicted, and attendees attending the unheld meeting can easily schedule the date of the meeting.

  In addition, by setting the extension time of the information on the non-held meeting based on the information of the held meeting that has the same agenda information of the non-held meeting, the extended time that may occur due to the influence of the agenda information is predicted and not held Attendees attending the meeting can easily schedule the date of the event.

  In addition, by selecting a pair of attendee information from among the information on the non-held meeting and calculating the degree of disagreement of the issue information for each selected pair of attendee information, how much the issue of the unheld meeting is between the attendees You can predict whether it has shifted. Therefore, the organizer can grasp how much the issue points are different among the attendees, and can consider the unification of the issue points in advance. In addition, the meeting time can be shortened.

  Further, by searching for held conference information that is a value close to the degree of discrepancy between the pair of attendee information of the non-held conference information, the extended time that may occur due to the influence of whether or not the issue is deviated is expected. Accordingly, it is possible to make it easier for attendees who attend an unheld meeting to schedule a date.

  The conference support method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. The conference support program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. The conference support program may be distributed via a network such as the Internet.

102 Attendee List 103 Moderator 105 Extended Time 200 Conference Database 201 Scheduled Time 202 Actual Conference Time 300 Results Database 303 Agenda 304 Inconsistency 400 Conference Issue Database 401 Attendee 502 Issue 700 Conference Support Device 701 Reception Unit 702 Selection Unit 703 Extraction Unit 704 Judgment unit 705 Calculation unit 706 Search unit 708 Output unit

Claims (6)

Accepting means for receiving information on a plurality of attendees of a non-held meeting, discussion information corresponding to the agenda information for each of the attendee information, and unconventional meeting information having moderator information;
For each held meeting, the held meeting information including the time difference between the scheduled meeting time and the actual meeting time, the attendee information, the issue information corresponding to the agenda information for each attendee information, and the chairperson information is stored. A conference that includes at least a part of attendee information of the non-held conference information received by the receiving means and is the same as the moderator information of the non-held conference information Extraction means for extracting information;
A selection means for sequentially selecting a pair of attendee information from the unheld meeting information;
Judgment means for judging the difference between the issue information of one attendee information and the issue information of the other attendee information, among the pair of attendee information, each time selected by the selection means;
Based on the number of differences determined by the determining means, calculating means for calculating the degree of inconsistency between the issue information of the one attendee information and the issue information of the other attendee information;
Obtaining a time difference of the held conference information extracted by the extracting means and outputting it as an extended time of the unheld meeting, and outputting means for outputting the inconsistency calculated by the calculating means to the unheld meeting information ;
A conference support apparatus comprising: The output means includes
When a plurality of held conference information is extracted by the extraction unit, the largest time difference is acquired from the time differences of the plurality of held conference information and set as an extension time of the unheld conference. The conference support apparatus according to claim 1. The non-held conference information and the held conference information in the database include the respective agenda information,
The extraction means includes
3. The meeting support apparatus according to claim 1, further comprising: held meeting information that is the same agenda information as the agenda information of the non-held meeting information from the database. Held meeting information in the database has a discrepancy for each combination of attendee information,
The extraction means includes
Referencing the database, extracting unheld meeting information including a pair of attendee information of the unheld meeting information,
From the held meeting information extracted by the extracting means, the held meeting information that is a mismatch degree within a predetermined range from the mismatch degree of the pair of attendee information of the unheld meeting outputted by the output means. A search means for searching,
The output means includes
The conference support apparatus according to claim 1, wherein a time difference between the held conference information searched by the search unit is output as an extension time of the non-held conference information. Computer
Accepting means for receiving information on unheld meetings having a plurality of attendee information of unheld meetings, issue information corresponding to agenda information for each of the attendee information, and moderator information,
For each held meeting, the held meeting information including the time difference between the scheduled meeting time and the actual meeting time, the attendee information, the issue information corresponding to the agenda information for each attendee information, and the chairperson information is stored. A conference that includes at least a part of attendee information of the non-held conference information received by the receiving means and is the same as the moderator information of the non-held conference information Extraction means for extracting information,
A selection means for sequentially selecting a pair of attendee information from the unheld meeting information,
Judgment means for judging the difference between the issue point information of one attendee information and the issue information of the other attendee information among the pair of attendee information each time selected by the selection means,
Based on the number of differences determined by the determining means, calculating means for calculating the degree of inconsistency between the issue information of the one attendee information and the issue information of the other attendee information,
An output unit that obtains a time difference of the held conference information extracted by the extraction unit and outputs the time difference as the extension time of the non-held conference, and outputs the degree of inconsistency calculated by the calculation unit to the non-held conference information;
A conference support program characterized by functioning as Computer
Accepting step of receiving unconventional meeting information having a plurality of attendee information of unconventional meetings, issue information corresponding to agenda information for each attendee information, and moderator information,
For each held meeting, the held meeting information including the time difference between the scheduled meeting time and the actual meeting time, the attendee information, the issue information corresponding to the agenda information for each attendee information, and the chairperson information is stored. Held conference that includes at least a part of attendee information of the non-held conference information received by the reception step and is the same as the moderator information of the non-held conference information An extraction process for extracting information,
A selection step of sequentially selecting a pair of attendee information from the unheld meeting information,
A determination step of determining the difference between the issue information of one attendee information and the issue information of the other attendance information among the pair of attendance information each time selected by the selection step,
Based on the number of differences determined by the determination step, a calculation step of calculating a degree of disagreement between the issue information of the one attendee information and the issue information of the other attendee information,
Obtaining the time difference of the held conference information extracted by the extraction step and outputting it as an extended time of the non-held conference, and outputting the mismatch degree calculated by the calculation step to the non-held conference information,
The meeting support method characterized by performing.

Images