MANAGING EVENT TIMELINES

• US 20100324948A1
• Filed: 06/18/2009
• Published: 12/23/2010
• Est. Priority Date: 06/18/2009
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kumar, Vinod, Kroening, Mary E.
• Application Number:
  US12/487,212
• Publication Number:
  US 20100324948A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group

Abstract

The present invention extends to methods, systems, and computer program products for managing event timelines. Embodiments of the invention can be used to generate a dynamic task list (or progress indicator) that shows what tasks have been completed, tasks that can be done now, and remaining tasks. Thus, the task list acts as a guide and a measure of progress. The task list also increases the chance that tasks are completed in the proper order. Accordingly, the configuration of a task list provides utility to both experienced, professional producers as well as the do it yourself producer. Users can use the task list to drive their event management or they can ignore it.

Claims

1. At a computer system including one or more processors and system memory, a method for maintaining a task list for an event, the method comprising:

an act of accessing a workflow for an event, the workflow representing a plurality of interdependent tasks for managing the event;

an act of presenting task list, the task list populated with a first one or more tasks from the workflow, the first one or more tasks currently relevant to management of the event;

an act of receiving one or more actions indicative of the first one or more tasks no longer being currently relevant to management of the event;

an act of updating the workflow to indicate that the first one or more tasks are no longer currently relevant to management of the event;

an act of analyzing the workflow to formulate the priority of any remaining non-completed tasks subsequent to updating the workflow, the formulated priority for each remaining non-completed task based on;

the dependency of the non-completed task on any previously completed tasks;

the designated importance of the non-completed task; and

the time differential between the current date and time and the scheduled data and time; and

an act of updating the task list by populating the task list with a specified number of higher priority non-completed tasks such that the task list reflects tasks that are currently relevant to management of the event in view of the received one or more actions; and

an act of presenting the updated task list, including the specified number of higher priority non-completed tasks, at a display device so as to provide a guide to managing the event, presentation of the updated task list indicating that the specified number of higher priority non-completed tasks are currently relevant to management of the event.

2. The method as recited in claim 1, further comprising:

an act of receiving event data defining the event, the event data indicating at least a scheduled date and time for the event and an event type for the event;

an act of accessing an event template for the event type;

an act of creating a workflow for the event based on the event template and in accordance with the received event data, the workflow representing a plurality of interdependent tasks for the event; and

an act of generating a initially task list for presenting actionable tasks to be completed for the event.

3. The method as recited in claim 2, wherein an act of receiving event data defining the event comprises an act of receiving settings for customizing the workflow;

and further comprising;

an act of customizing the workflow in accordance with the received settings.

4. The method as recited in claim 2, wherein an act of creating a workflow for the event based on the event template and in accordance with the received event data comprises an act of creating a hybrid polyarchical tree of tasks that is stratified based on how tasks are triggered.

5. The method as recited in claim 2, wherein an act of creating a workflow for the event comprises an act of creating a workflow for an event that is to include one or more attendees via video teleconference or Webcast.

6. The method as recited in claim 1, wherein the act of presenting task list comprises an act of presenting a list of tasks that can currently be completed and a list of tasks that can be completed in the future.

7. The method as recited in claim 1, wherein the act of receiving one or more actions indicative of the first one or more tasks no longer being currently relevant to management of the event comprises an act of receiving an action form one or more of a clock, a computer system, and a human user.

8. The method as recited in claim 1, wherein the act of receiving one or more actions indicative of the first one or more tasks no longer being currently relevant to management of the event comprises an act of receiving one or more actions indicative of a task being completed.

9. The method as recited in claim 8, wherein the act of receiving one or more actions indicative of a task being completed comprises an act of receiving one or more actions indicative of the time for completing an optional task expiring.

10. The method as recited in claim 1, wherein the an act of receiving one or more actions indicative of the first one or more tasks no longer being currently relevant to management of the event comprises an act of receiving one or more actions indicative of the importance of a task being reduced.

11. The method as recited in claim 1, wherein an act of updating the workflow to indicate that the first one or more tasks are no longer currently relevant to management of the event comprises an act of update the workflow state to indicate that some of the first one or more tasks have been completed.

12. The method as recited in claim 1, wherein the act of analyzing the workflow to formulate the priority of any remaining non-completed tasks subsequent to updating the workflow comprises an act of formulating a priority for at least one of a timeline triggered task and a user trigged task.

13. The method as recited in claim 1, wherein the act of analyzing the workflow to formulate the priority of any remaining non-completed tasks subsequent to updating the workflow comprises an act of formulating a priority for at least on task based on the completion of tasks that task depended on.

14. At a computer system including one or more processors and system memory, the computer system also including a workflow for managing an event timeline for an event, a method for maintaining the workflow, the method comprising:

an act of accessing a workflow for an event, the workflow configured to represent the current status of a plurality of interdependent tasks for managing the event;

an act of receiving one or more actions from each of a plurality of different entities acting upon the workflow, at least two of the plurality of different entities having different roles for participating in the event, the received actions corresponding to tasks that are currently relevant to management of the event;

for each task included in the plurality of interdependent tasks, an act of analyzing the workflow to determine if a combination of received actions are indicative of the task being completed; and

an act of adjusting the configuration of the workflow to update the status of the plurality of interdependent tasks based on the received actions and based on the indicated completion of any tasks.

15. The method as recited in claim 14, further comprising:

an act of analyzing the adjusted configuration of the workflow to formulate the priority of any remaining non-completed tasks in the plurality of interdependent tasks, the formulated priority for each remaining non-completed task based on;

the dependency of the non-completed task on any previously completed tasks;

the designated importance of the non-completed task; and

the time differential between the current date and time and the scheduled data and time; and

an act of populating a task list with a specified number of higher priority non-completed tasks such that the task list reflects tasks that are currently relevant to management of the event in view of any received actions; and

an act of presenting the task list, including the specified number of higher priority non-completed tasks, at a display device so as to provide a guide to managing the event, presentation of the task list indicating that the specified number of higher priority non-completed tasks are currently relevant to management of the event.

16. The method as recited in claim 14, further comprising:

an act of determining that actions indicating completion of task violate the dependency conditions of the task; and

an act of sending a notification to alert an event participant to the violation.

17. The method as recited in claim 14, wherein an act of receiving one or more actions from each of a plurality of different entities acting upon the workflow comprises an act of receiving actions from an entity having a role selected from among:

all participants, approved participants, registered participants, attendees, company, presenters, producer, mail handler, and registration handler.

18. The method as recited in claim 14, wherein the act of analyzing the workflow to determine if a combination of received actions are indicative of the task being completed comprises an act of analyzing the workflow to determine that the time for completing an optional task has expired.

19. The method as recited in claim 14, wherein the act adjusting the configuration of the workflow to update the status of the plurality of interdependent tasks comprises an act of updating workflow state to indicate that a task is completed.

20. An event management system for managing events that are to include human attendees, the system comprising:

system memory;

one or more processors;

one or more computer storage media having stored thereon one or more event templates, an event database, and a task database, the computer storage media also having stored thereon computer-executable instructions representing an event module, a workflow analyzer, and a user-interface, wherein the event module is configured to;

process event data defining an event, the event data indicating at least a scheduled date and time for the event and an event type for the event;

access an event template for the event type;

create an event workflow for the event based on the event template and in accordance with the received event data, the event workflow configured to represent the current status of a plurality of interdependent tasks for the managing event;

wherein the workflow analyzer is configured to;

access an event workflow for an event;

an act of receiving one or more actions from each of a plurality of different entities acting upon the event workflow, at least two of the plurality of different entities having different roles for participating in the event, the received actions corresponding to tasks that are currently relevant to management of the event, the plurality of different entities including a clock, a computer system, and a human user;

for each task included in the plurality of interdependent tasks, analyze the workflow to determine if a combination of received actions are indicative of the task being completed;

update the event workflow to indicate tasks are that are no longer currently relevant to management of the event;

analyze the event workflow to formulate a task priority for tasks subsequent to updating the workflow, the formulated task priority for each task based on;

the dependency of the task on any previously completed tasks;

the designated importance of the task; and

the time differential between the current date and time and the scheduled data and time; and

update the task list by populating the task list with a specified number of higher priority tasks such that the task list reflects tasks that are currently relevant to management of the event in view of the received one or more actions; and

wherein the user-interface is configured to;

receive event data defining an event, the event data indicating at least a scheduled date and time for the event and an event type for the event; and

present the updated task list, including the specified number of higher priority tasks, at a display device so as to provide a guide to managing the event, presentation of the updated task list indicating that the specified number of higher priority tasks are currently relevant to management of the event.