The management of meetings by grouping. In particular, methods and apparatuses are disclosed according to which individual meetings may be associated with one or more other meetings and modifications may be applied to the associated meetings as a group.
Various devices and applications are available that allow persons to maintain records of scheduled meetings and events. Such devices and applications often include features that allow users to modify entries. For example, the time and/or place of scheduled meetings can be modified by the user by changing the appropriate field or fields containing such information. In addition, such applications also commonly provide for reminder and alarm features.
Project planning applications are also available that allow users to coordinate events comprising a larger overall project. More particularly, project planning applications can provide a central location in which a number of related events can be graphically juxtaposed with one another to assist planners in efficiently scheduling such events.
The scheduling of meetings can be complicated, because, by definition, meetings require the participation of two or more persons. The scheduling of meetings is further complicated where there are a large number of participants or where participants are located in different time zones. As a result, scheduling a meeting can be a time consuming and complicated task.
Oftentimes, it is necessary to reschedule meetings. For example, due to changes in travel plans, a user may need to reschedule a meeting to comply with the new travel schedule. Although a change in a single meeting can be accommodated by modifying related information, such as the scheduled date and time of the meeting, conventional application programs have been unable to identify a group of meetings needing to be rescheduled due to changes in travel plans or other events. As a result, users have had to reschedule each individual meeting within a group of related meetings needing to be rescheduled on an individual basis. In addition, application programs have been incapable of allowing users to make changes to groups of related meetings, and provide the user with an indication as to whether the proposed change to the group of meetings introduces scheduling or other conflicts. Application programs have also been unable to allow users to create other groups of meetings and allow the meetings to be manipulated by the grouping.
According to the embodiments of the present invention, a scheduling process or application incorporating or associated with a grouping application that allows for the creation of groups of meetings is provided. The scheduling application and the grouping application may further be provided as part of a meeting management application. According to further embodiments of the present invention, groups of meetings that have been defined can be manipulated as a group. Therefore, a modification can be applied to a number of meetings automatically, without requiring manual entry or human assistance with respect to each meeting to which the modification is applied. As a result, the management of related meetings is facilitated, and the need for repetitive rescheduling of related meetings can be avoided.
The scheduling application incorporates or is associated with a grouping application. In general, the scheduling application maintains records of meetings entered by a user. Information associated with each entered meeting can include a description, date, time, place, participants, required resources or other information describing or related to the meeting. In addition, the scheduling application may provide a user interface, to allow the user to enter new meeting information, or to modify previously entered meeting information. The grouping application allows for the identification and/or definition of groups of meetings. In addition, the grouping application may provide a user interface that allows a user to specify or determine the meetings that are included in different groups of meetings. For example, the grouping application may allow the user to enter one or more pieces of information characterizing a group of meetings that the user used to create or designate the group. The grouping application may then operate as a filter, to locate meetings maintained by the scheduling application that meet the specified criteria.
The scheduling application may also allow a user to modify information pertaining to each meeting within a group of meetings automatically (i.e. without requiring manual entry of the modification with respect to each individual meeting included in the grouping). The scheduling application may additionally provide information regarding conflicts between meetings, or between a meeting and another scheduled activity. This facility is particularly useful where one or more meetings within a first group also belong to another group. Furthermore, identification of conflicts may be performed in connection with every meeting in an identified first group of meetings, or within any other groups that a meeting within the first group belongs.
In accordance with other embodiments of the present invention, a process or method for managing meetings by grouping is provided. According to such a method, a user may enter meeting information through a scheduling application. As information is entered, the scheduling application may check for potential conflicts with other meetings or events. According to the method, a user may also modify information related to meetings. Modified meeting information may also be checked to determine whether it presents a potential conflict. Embodiments of the present invention also allow a user to define or identify a group of related meetings. The identification or definition of a group of meetings may comprise receiving information comprising grouping criteria from the user. Once a grouping has been defined, information associated with each meeting included in the grouping can be modified globally by the user. In response to a global modification, the scheduling application may determine whether the modification applied to all the meetings in the grouping presents a potential conflict to any other meeting or event.
Additional features and advantages of the present invention will become more readily apparent from the following discussion, particularly when taken together with the accompanying drawings.
In
In general, a computing device 104 in accordance with embodiments of the present invention may comprise any device capable of executing or implementing a meeting management application 106. Accordingly, examples of a computing device include various integrated computing devices, such as a general purpose computing device (e.g. a personal computer), a personal digital assistant (PDA) a cellular telephone incorporating or providing scheduling functionality, a dedicated scheduling device or electronic calendar, or other device. Furthermore, the execution of a meeting management application 106 may be distributed among a number of computing devices. For example, data may be maintained in a computing device comprising a network storage device.
As can be appreciated by one of skill in the art, different computing devices 104 and/or different meeting management applications 106 may be associated with different users. For example, the first computing device 104 and the associated meeting management application 106 may be used by a first user and may include meeting information entered by the first user, while the second computing device 104 and the associated meeting management application 106 may be associated with a second user and may include meeting information entered by the second user. As can further be appreciated by one of skill in the art, the communication network 112 may facilitate the exchange of meeting and other information between scheduling applications 108, whether those scheduling applications are part of a meeting management application 106 incorporating a grouping application 116 as described herein, or otherwise.
With reference to
A computing device 104 may additionally include memory 208 for use in connection with the execution of programming by the processor 204, and for the temporary or long term storage of data or program instructions. For example, the memory 208 may be used in connection with the operation of a scheduling application 108 and/or a grouping application 116 as described herein. The memory 208 may comprise solid state memory resident, removable or remote in nature, such as DRAM and SDRAM. Where the processor 204 comprises a controller, the memory 208 may be integral to the processor 204.
In addition, various user input devices 212 and user output devices 216 may be provided. A user input device 212 may comprise a means for receiving meeting information and group selection parameters. Examples of input devices 212 include a keyboard, a numeric keypad, a pointing device combined with a screen or other position encoder, and a microphone. A user output device 216 may comprise a means for outputting at least some information related to a group of selected meetings. Examples of user output devices 216 include a graphic display, an alpha-numeric display, a printer, indicator lamp, and speaker.
A computing device 104 may also include data storage 220 for the storage of application programming and/or data. For example, operating system software, 224 may be stored in the data storage 220. Examples of applications that may be stored in the data storage 220 include scheduling application 108 and grouping application 116 software, as described herein. As illustrated, the scheduling application 108 and the grouping application 116 may together comprise a meeting management application 106. Furthermore, the scheduling application 108 may comprise a means for storing and organizing meeting information, and for detecting conflicts between meetings. Accordingly, the scheduling application 108 in accordance with embodiments of the present invention may include or operate in association with an automated rules engine that operates to detect conflicts. Furthermore, a scheduling application 108 incorporating or associated with an automated rules engine may suggest a resolution to a detected conflict. The grouping application 116 may comprise a means for selecting meetings according to group selection parameters.
Other applications that may be stored in data storage 220 include applications associated with performing any functions that may be performed in addition to the functions associated with execution of the scheduling application 108 and the grouping application 116. Particular examples of such additional applications include a telephony, email, address book, calculator or other applications.
A computing device 104 may additionally include a communication network interface 228. An example of a communication network interface 228 includes a packet data network interface, such as a wired or wireless Ethernet interface, for example where the computing device 104 comprising a general purpose computer. Additional examples of a communication network interface 228 include a telephony network interface, such as a CDMA, TDM, GSM, PSM, or satellite interface, Bluetooth, WIFI, IrDA or other wireless or wire line interface.
With reference again to
Although the system 100 illustrated in
With reference now to
At step 308, a determination may be made as to whether entered (or modified) meeting information presents a potential conflict. Potential conflicts can be identified by searching scheduling application records 108 for conflicts. Examples of conflicts include different meetings having a common participant that are scheduled for the same time, different meetings booked for the same place at the same time, meetings booked at a time during which one or more of the participants has been scheduled to participate in another event, or meetings scheduled in time or place such that one or more of the participants would be unable to attend. As can be appreciated by one of skill in the art from the description provided herein, information related to potential conflicts with an entered meeting can comprise other meeting information, or information related to other activities. Furthermore, potentially conflicting information can be entered into a scheduling application 108 operating to check for potential conflicts, and/or such information can be available to a scheduling application 108, for example in the form of scheduling information stored in data storage 220 on the computing device 104 on which the scheduling application 108 is running, or on another computing device 104. If the entered (or modified) meeting information presents a potential conflict, the user is notified of the potential conflict (step 312). Notification of the potential conflict may be in the form of a textual and/or visual message indicating the existence of a conflict. The information provided to the user may include an identification of the conflicting meeting or event. Notification may additionally include suggestions for alternate times in which to schedule the meeting for which information has been entered or modified, or for the conflicting meeting or event.
After notifying the user of a potential conflict (at step 312) or after determining that the entered (or modified) meeting information does not present a potential conflict (at step 308), a determination is made as to whether a user has entered modified meeting information (step 316). Re-entry of modified meeting information may include changes to previously entered meeting information. Such changes may be entered in response to various information or eventualities, including notification received from the scheduling application 108 of a potential conflict at step 312. If modified information has been entered, the process may return to step 308 to check for potential conflicts.
If the user has not entered modified meeting information, the process may determine whether the user has defined or identified a group of related meetings (step 320). As will be described in greater detail elsewhere herein, the definition or identification of a group of related meetings can comprise the execution of a query entered by the user, the application of a user defined filter to information related to a number of meetings, or the tagging or identification of a number of meetings by the user as being associated with one another. If the user has defined or identified a group of related meetings, a determination may then be made as to whether the user has then entered a modification for application to meeting information for some or all of the meetings in the defined group (step 324). For example, a user who has defined a group of meetings by identifying all meetings occurring on a particular day at a particular location may enter a modification comprising a change in the date for all such identified meetings in response to a change in the user's travel plans that necessitate rescheduling the meetings to a new day. As another example, modified meeting information in the form of the persons scheduled to participate in one of the meetings in a group may be entered. Furthermore, the modified meeting information may be applied to all of the meetings in a defined group automatically, where automatically means that the information is applied to all of the meetings in a group without human assistance. For example, the information can be entered by a user once, and then automatically applied to all of the meetings within a group by entering a command to apply the information to all of the meetings within the group, and without requiring individual entry of the information by the user for each of the meetings. In accordance with further embodiments of the present invention, modified meeting information may be applied automatically to each meeting within a group to which the modification is relevant. For example, the removal of one meeting participant may be applied to those meetings in the group that included meeting information that included the removed participant.
In response to determining that a modification for application to all or a number of the meetings in a group has been entered, a determination as to whether the modification applied to the meetings presents a potential conflict (step 328). That is, a check may be made to determine whether any of the meetings included in the defined group subject to the entered modification conflicts with any other meeting or event. Furthermore, a check for conflicts may be made with respect to any other meeting or event in the group, and/or any other meeting or event in any group. If a conflict or potential conflict is identified, the user is notified of the potential conflict (step 332). As another example, if the time of a group of meetings is shifted such that at least one of the meetings is scheduled outside of normal business hours, the user may be notified, and the process may offer to reschedule that meeting or meetings for the next day. After notifying the user of the potential conflict, or after determining that no potential conflicts exist, a determination may be made as to whether new or modified meeting information has been entered (step 336). That is, a user may continuously enter new or modified meeting information as part of the operation of a scheduling application 108. If new or modified meeting information has been entered, the process may return to step 308. If new or modified meeting information has not been entered, a determination may be made as to whether the user has elected to exit the meeting management application 106. If the user has not chosen to exit the meeting management application 106, a determination may be made as to whether a command to exit the meeting management application 106 has been received (step 340). If a command to exit is not received, the process may return to step 336 to await new or modified meeting information. Alternatively, if a command to exit has been received, the process for entering new or modified meeting information may end.
In accordance with embodiments of the present invention, when a user enters a modification to a meeting that is part of a group (e.g., at step 316), the user may be provided with an option to apply the modification to each meeting in the group. For example, a change or shift in the time that a meeting is to occur can be applied to each meeting in an associated group. The option to apply a change in one meeting to each meeting in a group can be presented to the user through a pop-up dialog asking if the modification should be applied to the group or just the single meeting. Alternatively or in addition, a menu item or button can be provided to allow a user to select whether the modification will apply to the group or just the single meeting.
With reference now to
At step 412, the results of performing the requested grouping are displayed to the user. For example, a list of meetings associated with the group criteria entered by the user may be listed. For example, the group criteria may comprise at least one user selected or entered term. At step 416, determination is made as to whether additional criteria have been entered by the user. For example, a user may wish to narrow the list of meetings included in a group by entering additional terms or criteria. Alternatively, the user may wish to enter different criteria or may wish to remove criteria, in order to modify the meetings included in the group. If additional or different criteria is entered by the user, the process may return to step 408, and the list of meetings included in the group may be revised. Group criteria that may be entered include the identity of one or more meeting participants, the place of the meeting, the meeting topic, the day of the week scheduled for the meeting, or any other meeting information. In accordance with further embodiments of the present invention, one or more sub-groupings may be established within a larger group of meetings, which may themselves be analyzed and modified as a group if desired.
If no additional criterion is entered by the user, a determination may be made as to whether the user has indicated that the identified group of meetings should be saved (step 420). If the group is to be saved, the results of the groupings are stored, for example as a list of included meetings (step 424). After storing the group or determining that an identified group is not to be stored, a determination is made as to whether the user desires to create additional groups of meetings (step 428). If it is determined that an additional group is to be created, the process may return to step 404. If no additional groups are to be created, the process may end.
In accordance with embodiments of the present invention, a user may enter modified meeting information on a provisional basis. That is, a user may enter modified information as part of performing a “what if” scenario, to determine the effects of a potential change. If the modified information entered provisionally creates unacceptable conflicts or is otherwise determined to be undesirable, that information may be discarded, without having changed the stored meeting information. Alternatively, if the modified information does not create any unacceptable conflicts, the user may choose to apply the modified meeting information. As can be appreciated by one of skill in the art after appreciation of the present disclosure, modified information entered on a provisional basis may apply to a single meeting or to a group of meetings. Accordingly, embodiments of the present invention can comprise a planning tool that provides a convenient means for determining the effects of potential changes.
The foregoing discussion of the invention has been presented for purposes of illustration and description. Further, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, within the skill or knowledge of the relevant art, are within the scope of the present invention. The embodiments described hereinabove are further intended to explain the best mode presently known of practicing the invention and to enable others skilled in the art to utilize the invention in such or in other embodiments and with various modifications required by their particular application or use of the invention. It is intended that the appended claims be construed to include alternative embodiments to the extent permitted by the prior art.
Number | Name | Date | Kind |
---|---|---|---|
4819191 | Scully et al. | Apr 1989 | A |
4831552 | Scully et al. | May 1989 | A |
5050077 | Vincent | Sep 1991 | A |
5124912 | Hotaling et al. | Jun 1992 | A |
5197000 | Vincent | Mar 1993 | A |
5206903 | Kohler et al. | Apr 1993 | A |
5216603 | Flores et al. | Jun 1993 | A |
5323314 | Baber et al. | Jun 1994 | A |
5428784 | Cahill, Jr. | Jun 1995 | A |
5555346 | Gross et al. | Sep 1996 | A |
5619555 | Fenton et al. | Apr 1997 | A |
5627978 | Altom et al. | May 1997 | A |
5774867 | Fitzpatrick et al. | Jun 1998 | A |
5793365 | Tang et al. | Aug 1998 | A |
5813013 | Shakib et al. | Sep 1998 | A |
5828747 | Fisher et al. | Oct 1998 | A |
5889945 | Porter et al. | Mar 1999 | A |
5893073 | Kasso et al. | Apr 1999 | A |
5905793 | Flockhart et al. | May 1999 | A |
5920701 | Miller et al. | Jul 1999 | A |
5960406 | Rasansky et al. | Sep 1999 | A |
5963913 | Henneuse et al. | Oct 1999 | A |
5982873 | Flockhart et al. | Nov 1999 | A |
6064976 | Tolopka | May 2000 | A |
6085166 | Beckhardt et al. | Jul 2000 | A |
6101480 | Conmy et al. | Aug 2000 | A |
6147685 | Bliss et al. | Nov 2000 | A |
6163607 | Bogart et al. | Dec 2000 | A |
6173053 | Bogart et al. | Jan 2001 | B1 |
6192111 | Wu | Feb 2001 | B1 |
6192122 | Flockhart et al. | Feb 2001 | B1 |
6272074 | Winner | Aug 2001 | B1 |
6360217 | Gopal et al. | Mar 2002 | B1 |
6363352 | Dailey et al. | Mar 2002 | B1 |
6377965 | Hachamovitch et al. | Apr 2002 | B1 |
6434571 | Nolte | Aug 2002 | B1 |
6570555 | Prevost et al. | May 2003 | B1 |
6594637 | Furukawa et al. | Jul 2003 | B1 |
6640230 | Alexander et al. | Oct 2003 | B1 |
6662309 | Ando et al. | Dec 2003 | B2 |
6675356 | Adler et al. | Jan 2004 | B1 |
6694335 | Hopmann et al. | Feb 2004 | B1 |
6731323 | Doss et al. | May 2004 | B2 |
6988128 | Alexander et al. | Jan 2006 | B1 |
7007235 | Hussein et al. | Feb 2006 | B1 |
7016909 | Chan et al. | Mar 2006 | B2 |
7027995 | Kaufman et al. | Apr 2006 | B2 |
7035865 | Doss et al. | Apr 2006 | B2 |
7082402 | Conmy et al. | Jul 2006 | B2 |
7113797 | Kelley et al. | Sep 2006 | B2 |
7130885 | Chandra et al. | Oct 2006 | B2 |
7149810 | Miller et al. | Dec 2006 | B1 |
7155435 | Day et al. | Dec 2006 | B1 |
7187384 | Noyle | Mar 2007 | B2 |
7188073 | Tam et al. | Mar 2007 | B1 |
7254569 | Goodman et al. | Aug 2007 | B2 |
7343312 | Capek et al. | Mar 2008 | B2 |
7343313 | Dorenbosch et al. | Mar 2008 | B2 |
7353466 | Crane et al. | Apr 2008 | B2 |
7363590 | Kerr et al. | Apr 2008 | B2 |
7383291 | Guiheneuf et al. | Jun 2008 | B2 |
7383303 | Bort | Jun 2008 | B1 |
7395221 | Doss et al. | Jul 2008 | B2 |
7436654 | Cho | Oct 2008 | B2 |
7440961 | Matousek | Oct 2008 | B1 |
7519672 | Boss et al. | Apr 2009 | B2 |
7595717 | Boss et al. | Sep 2009 | B2 |
7693734 | Christenson et al. | Apr 2010 | B2 |
20010054072 | Discolo et al. | Dec 2001 | A1 |
20020085701 | Parsons et al. | Jul 2002 | A1 |
20020117847 | Ede et al. | Aug 2002 | A1 |
20020120600 | Schiavone et al. | Aug 2002 | A1 |
20020144136 | Stornetta et al. | Oct 2002 | A1 |
20030046304 | Peskin et al. | Mar 2003 | A1 |
20030069880 | Harrison et al. | Apr 2003 | A1 |
20030149606 | Cragun et al. | Aug 2003 | A1 |
20030154293 | Zmolek | Aug 2003 | A1 |
20030163537 | Rohall et al. | Aug 2003 | A1 |
20040054726 | Doss et al. | Mar 2004 | A1 |
20040128181 | Zurko et al. | Jul 2004 | A1 |
20040168133 | Wynn et al. | Aug 2004 | A1 |
20040192857 | Borer et al. | Sep 2004 | A1 |
20040199663 | Horvitz et al. | Oct 2004 | A1 |
20040254998 | Horvitz | Dec 2004 | A1 |
20050069099 | Kozdon et al. | Mar 2005 | A1 |
20050125246 | Muller et al. | Jun 2005 | A1 |
20050165631 | Horvitz | Jul 2005 | A1 |
20050192857 | Levine | Sep 2005 | A1 |
20050198144 | Kraenzel et al. | Sep 2005 | A1 |
20060004843 | Tafoya et al. | Jan 2006 | A1 |
20060020889 | Coppinger et al. | Jan 2006 | A1 |
20060031326 | Ovenden | Feb 2006 | A1 |
20060031470 | Chen et al. | Feb 2006 | A1 |
20060047557 | Bieselin et al. | Mar 2006 | A1 |
20060069686 | Beyda et al. | Mar 2006 | A1 |
20060184584 | Dunn et al. | Aug 2006 | A1 |
20060190485 | Adams et al. | Aug 2006 | A1 |
20060242109 | Pereira et al. | Oct 2006 | A1 |
20070016878 | Forlenza et al. | Jan 2007 | A1 |
20070118415 | Chen et al. | May 2007 | A1 |
20070174104 | O'Sullivan et al. | Jul 2007 | A1 |
20070265903 | Blair et al. | Nov 2007 | A1 |
20080005685 | Drews et al. | Jan 2008 | A1 |
20080034425 | Overcash et al. | Feb 2008 | A1 |
20080037733 | Chen et al. | Feb 2008 | A1 |
Number | Date | Country |
---|---|---|
1014286 | Jun 2000 | EP |
1 560 138 | Aug 2005 | EP |
WO 2005010715 | Feb 2005 | WO |