WO2006123957A1 - Systeme de planification et d'etablissement de calendrier - Google Patents

Systeme de planification et d'etablissement de calendrier Download PDF

Info

Publication number
WO2006123957A1
WO2006123957A1 PCT/NZ2006/000127 NZ2006000127W WO2006123957A1 WO 2006123957 A1 WO2006123957 A1 WO 2006123957A1 NZ 2006000127 W NZ2006000127 W NZ 2006000127W WO 2006123957 A1 WO2006123957 A1 WO 2006123957A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
calendar
scheduling
party
schedule
Prior art date
Application number
PCT/NZ2006/000127
Other languages
English (en)
Inventor
Colin Ashton Campbell
Graeme William Mclennan
Warren John Boyd
Suresh Nimmakayla
Original Assignee
Achievement Nz Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Achievement Nz Limited filed Critical Achievement Nz Limited
Publication of WO2006123957A1 publication Critical patent/WO2006123957A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting

Definitions

  • the present invention relates to systems and methods for scheduling and calendaring events, including computerised apparatus and software for use with such systems.
  • One of the most common electronic scheduling and calendaring systems currently in use is the calendar in Microsoft® Outlook®.
  • a user receives notification of when an event is to occur or must be completed by and then enters an "appointment" into the system on the appropriate date and time.
  • the user's computer is part of, for example, a local area network, by setting appropriate permissions, other people within the organisation may enter, modify and/or delete appointments for the user and view their calendar.
  • Event - an entry to be made into the calendar of a client
  • Key event - an event in a sequence of events relative to which the location in time of other events in that sequence of events is calculated
  • the invention broadly resides in a scheduling and calendaring system including a computer processing system including one or more communication means to communicate with one or more second computer processing systems and computer memory, wherein the computer processing system is programmed and/or is operable to:
  • said first event schedule comprises a plurality of events distributed over time with at least one of said events requiring input from of a third party.
  • said second event schedule comprises a plurality of events distributed over time.
  • the first and/or second event schedules define one or more events that occur prior to or after a main event in said first and/or second event schedule.
  • the computer processing system includes a server that is able to communicate with the one or more second computer processing systems via a wide area network.
  • the one or more second computer processing systems each comprise a personal computer.
  • the computer processing system is programmed and/or is operable to perform the further step of using an electronic communication method to notify the third party that their schedule and/or calendar is being populated, optionally requesting confirmation from the third party before populating the schedule and/or before finally populating the schedule and/or calendar.
  • the computer processing system maintains in a computer memory calendars for the users and users can view each others calendar or a portion thereof with or without permission.
  • a computerised method of scheduling and/or calendaring comprising: - maintaining a calendar for at least one user and populating the calendar with at least one event sequence comprising at least one event; where one or more of said at least one event requires involvement of a third party, populating the third party's schedule and/or calendar with events that indicate their involvement, optionally seeking confirmation from the third party through electronic means that their calendar should be populated.
  • the invention broadly resides in computer software suitable for causing a computer system to operate in accordance with the method described in the immediately preceding paragraph.
  • Figure 1 shows a block diagram of a computer network in which the present invention may be implemented.
  • Figure 2 shows a flow chart of the steps involved in defining an event sequence according to an aspect of the present invention.
  • Figure 3 shows a flow chart of the steps involved in creating a client profile, including creating sub-profiles according to an aspect of the present invention.
  • Figure 4 shows a more detailed flow diagram of an example process for creating a sub-profile for a client.
  • Figure 5 shows a flow chart of the process to link a user's calendar with a third party's calendar according to an aspect of the present invention.
  • Figure 6 shows a block diagram of some of the components of a software application in accordance with the present invention.
  • Figure 7 shows a flow chart of the process for alternative linking of events within calendars.
  • FIG. 1 shows a high level block diagram of a computer network, generally referenced by arrow 100, which is suitable for implementing the present invention.
  • the computer network 100 includes a scheduling and calendaring system 101 including a web server 1 that communicates with clients 2 through a suitable client interface A, which may be formed within the internet, an intranet or other network environment.
  • the clients 2 may be personal computers located at various physical locations. Developers may optionally access the web server 1 using a client 2, using a suitable protocol such as SOAP, RMI or a custom tunnelling protocol.
  • the web server 1 handles data exchange with the clients 2 and passes data representing information and requests to the server 3.
  • the server 3, which is shown distinct from the web server 1 but is not necessarily so, manages the operation of the present invention, including acting as a database management server for a database 4. Alternatively, a separate database management server may be used, although it is anticipated that this should not be necessary for most implementations of the present invention.
  • the scheduling and calendaring system 101 allows a sequence of events to be entered into an electronic calendar.
  • Figure 2 shows a flow chart of the steps involved in defining an events sequence.
  • a key event is selected.
  • the key event will form part of a sequence of events and depend on the specific industry that the scheduling and calendaring system 101 is used for.
  • the scheduling and calendaring system 101 may support multiple clients from multiple industries, with each industry having its own standard events sequences. Each client may optionally have personalised industry events and related event sequences.
  • an event sequence for a sheep farmer is described herein.
  • An industry related event for a sheep farmer is the date that rams are introduced to a flock of ewes (ram in date) for breeding.
  • step 201 a sequence of events are defined that are related to the key event selected in step 200.
  • the related sequence of events include in their definition the time at which they occur relative to the industry event.
  • lambing may be due to start one hundred and forty seven days after the ram in date and a ram health check may be due to be carried out fourteen days before the ram in date.
  • step 202 a check of each event in the event sequence is made to determine if a third- party should be involved with the event. For example, for the event of a ram health check, the services of a vet are required. The ram health check is then tagged to indicate that a third-party (vet services) is required. The sequence is then defined and is stored in the database 4 (step 203).
  • Steps 200 to 203 may be suitably performed by an industry association, which sets best practice procedures for the industry. By having the event sequences stored in the database 4, updates to the sequences can be readily made and immediately accessed by clients 2. Steps 200 to 203 may also be completed by an individual client 2, with the sequence also being stored in the database 4, optionally only accessible and usable by that individual client 2 and such other clients 2 as are given permission to view or use the sequence of events. Depending on the particular application, some clients may not require permission to view or use the calendars of some or all other clients.
  • step 200 involves defining a key event such as the date that a student is due to start a course (course start date).
  • a sequence of events related to the course start date is defined, and the date of each event in the sequence is calculated relative to the course start date.
  • one example of such an event may be an assignment (Assignment 1) due for submission 25 days after the course start date.
  • a check is made of each event in the event sequence to determine if a third- party calendar should be updated. Using the example of the assignment, the Assignment 1 event would be tagged to state that a third-party (the course tutor) calendar should also be updated with this event.
  • the sequence is then defined and is stored in the database 4 (step 203).
  • the key event in this example could be defining the date that a building permit was issued (building start date, step 200).
  • a sequence of events for construction of a building is then generated (step 201) from this key event, from scraping the site through to marketing the property for sale.
  • Each event in the sequence is then checked for third-party involvement (step 202), which might include builders, plumbers, and electricians among others who should be updated.
  • third-party involvement might include builders, plumbers, and electricians among others who should be updated.
  • delays in one event in the sequence may trigger delays in subsequent events.
  • linked events are "bumped" i.e. correspondingly delayed in accordance with the delayed start to the instigating event. This accommodates the situation arising where a third-party contractor fails to begin on time, causing delays in the start of other contractors work.
  • the sequence is defined and stored in the database 4 (step 203).
  • a key event for a vineyard operator could be the day that vines begin flowering (flowering date). Due to regional and varietal differences, flowering is due to start on one of a number of days around the date of 1 October each year in the southern hemisphere. Different sequences can be established for different regions, and for different varieties based on established best practice models within the industry. Events within the event sequence are checked to determine if a third party calendar should be updated (step 202), such as a harvesting contractor for the harvesting event, and the sequence is then defined and stored in the database 4 (step 203).
  • Figure 3 shows a flow chart of the steps involved in creating a client profile, including creating sub-profiles.
  • the process starts by the client 2 accessing the web server 1 using browser software 2a.
  • the client 2 either enters login information if they are already registered (steps 301-303) or enters information in order to create a new profile (steps 304, 305 and 306) and then logs in (step 303).
  • the information to create a new profile may include the industry that the client works in, their contact details including their physical location and an email address and may include an option to select one or more third-parties as preferred service or product providers from a list of such providers that can service the client 2 (for example due to being the same region as the client 2), the details of the providers being stored in the database 4.
  • main profile Other information may be entered into the main profile, dependent on the specific implementation and on the industry of the client. For example, where the scheduling and calendaring system 101 provides e-commerce functionality or interfaces with an e-commerce system, then details relating to charging and payment of funds may be entered into the main profile.
  • step 307 the client 2 is asked whether a new sub-profile is to be created. If not, then the client 2 can navigate through the rest of the system, using whatever other information or functionality may be provided by the scheduling and calendaring system 101 (step 308). If the answer is yes, which may for example be indicated by the user selecting an icon on a graphical user interface, then in steps 309 and 310 the user is queried for information that is required to identify an event sequence and the location in time of the event sequence. For most industries, it is expected that the minimum information required will be the identification of an event, usually the key event and when that is to occur.
  • the farmer enters the ram in date (the key event date).
  • the physical location or region may also be important in selecting third parties and may be important for selecting the appropriate events sequence from the database 4, for example due to climate differences in different regions.
  • the calendar may be located on the server 3 and accessible by the client 2, or may be stored locally on the client 2 and able to be queried by the server 3 as required, the server 3 optionally maintaining a duplicate copy of the client's calendar, or at least the events in the calendar that have been entered by the scheduling and calendaring system 101.
  • the student creates a master profile (steps 304 - 306, if required), then creates a sub-profile for a particular learning course (steps 309 and 310). Within the sub profile, the student nominates a course start date, the key event in this example. Once the course start date is entered, the calendar will be populated with an event sequence (step 311). The student can create sub-profiles for different courses, each time specifying the course start date within the sub-profile.
  • the property developer would create a sub-profile for each new building project (steps 304 - 306), and enter the key event of the building start date for each sub-profile. Further information such as the style or size of the building may be required, and the calendar will be updated with an appropriate event sequence for the building that is being planned (steps 309 and 310).
  • the developer can create additional sub-profiles for each new building project, each time specifying the key event date within the sub-profile for the project.
  • the vineyard operator would create a sub-profile for each variety being grown, each having independent key dates (the flowering date). Once the key date for each sub-profile is entered, the calendar will be populated with an event sequence (step 311) specific to the grape variety being grown.
  • the client 2 may view the profiles of a set of third-parties that may be involved in any one of the events in the selected events sequence.
  • the client 2 can then select one of the third-parties (step 313), who have their own profile in the scheduling and calendaring system 101.
  • the scheduling and calendaring system 101 then generates an event sequence for the third-party (step 314).
  • This event sequence may be a single event, particularly if the third-party does not need to prepare prior to the event or take action after the event, or may be a series of events, the timing of which is calculated relative to the event in the event schedule of the user that triggered the entering of an event sequence in the third-party's calendar.
  • the scheduling and calendaring system 101 may populate the third party's calendar with the generated event sequence. For some events more than one event sequence may be generated for one or more third-parties.
  • a notification may be sent to that third party.
  • the notification advises the identity of the owner of the event that has caused the population of their calendar and summarise the events sequence.
  • the third-party may be given the opportunity to accept, decline and/or make variations to the event sequence.
  • Figure 4 shows a more detailed flow diagram of an example process for creating a sub- profile for a client.
  • the flow diagram starts at the "Yes" exit option for step 310 shown in Figure 3, indicating that the information required to identify an event sequence and the location in time of the event sequence has been entered.
  • step 350 the scheduling and calendaring system
  • step 351 the user is asked to check the events sequence and can indicate either that all the dates are wrong, in which case the events sequence is cleared (step 352) and the process returns to step 307 (see Figure 3), that some event dates are wrong, in which case the process proceeds to step 353,' or that all the event dates are correct, in which case the process proceeds to step 354.
  • step 354 the user alters the dates of events that require correction.
  • the selection of an alternative date may be performed automatically and the user may be asked to either confirm that the alternate date is acceptable or enter a further alternative.
  • step 353 the user has the option of setting whether or not particular events send the user a notification (see step 356).
  • the scheduling and calendaring system 101 checks if any events in the newly entered event sequence require notification on that day, which may include notifications of any events that should have occurred in the past, optionally with an alert (step 355). If there are events to be notified, then this is performed in step 356, for example by a message on-screen, an email or by some other electronic communication. The checking for event notifications should be performed regularly, for example daily, whether or not a new event sequence is entered, as indicated by step 357.
  • Figure 5 shows a flow chart of an example series of steps that the scheduling and calendaring system 101 undertakes to link a user's calendar with a third party's calendar.
  • the process starts at step 501 with a check as to whether a client has successfully logged in and then checks if a sub-profile has been created (step 502).
  • the user selects a third-party category for use with the sub-profile, optionally from a predefined list of categories for that sub-profile.
  • the category may be, for example, Vet Services and may be automatically selected by the scheduling and calendaring system for some event sequences.
  • the scheduling and calendaring system 101 displays any third-parties that are available in the selected category, taking into account any preferences that the user may have entered and optionally the physical location of the client, and the client selects a third-party.
  • the farmer might select the Vet services category (step 503), then the individual Vet for use with the sub-profile.
  • Step 505 Once a third-party has been selected, in step 505 their identification is added to the sub- profile and recorded in memory so that linking of calendars and synchronising of events can occur.
  • Step 506 is a check that a successful link has been made and may include a counter so that after a predetermined number of attempts an error message is returned.
  • step 507 the third party is notified of the linking and the client's details are entered in a contact list of the third-party. Also, the third-party's calendar is populated with the event sequence that was generated in step 314 (see Figure 3).
  • the notification is preferably by electronic messaging, suitably email, although many alternatives exist and each individual may select one or more means of notification.
  • the events sequence populated into a user's calendar or the calendar of a third party may create a conflict of events.
  • the scheduling and calendaring system 101 may automatically resolve this by shifting the location in time of particular events.
  • Each event may have a parameter that indicates the extent to which it can be shifted in time, if at all.
  • a notification may be automatically sent to all affected parties when an event is shifted and some subsequent action may be automatically taken, provided that some protection for avoiding continuous loops is present.
  • the process exits at step 315, where the client can navigate through the rest of the scheduling and calendaring system 101.
  • the student would first select a third-party category such as Course Tutors (step 503), and from within the Course Tutors category the user would select an individual Tutor.
  • the process can also force the selection of individual tutors required to be linked as third parties. This would remove the optional nature for a user of selecting a third-party calendar to synchronise with.
  • Further parties calendars also be updated on an optional or non-optional basis. This is used whereby an interested party, such as an employer or another similar interested party, may have their calendar updated with events on an observer-only basis. An example of this is where an employer is paying for the education of staff members and wishes to be kept informed as to the progress of individuals using the system.
  • the user confirms that synchronisation will take place. If optional linking does not exist for the user, this step will not be required. If the user at some stage decides they will no longer synchronise with the third-party, the user can simply disconnect the link. Again, if optional linking does not exist for the user, this step will not be required.
  • any event within an event sequence that requires this third-party to be notified will in turn populate the third parties calendar, and optional notifications will be sent to the third-party informing them of this action.
  • the user with first select a third-party category such as electricians (step 503), and from within this category the user would select an individual electrician to link to the sub-profile.
  • a third-party category such as electricians (step 503)
  • the user confirms that synchronisation will take place, and the electrician's calendar is populated (with notification of the update being sent optionally). Calendars of additional parties such as investors may also be populated by the event, but may not contain as much detail.
  • the vineyard operator may select from a third-party category such as harvesting contractors (step 503) the individual contractor they wish to link to a sub-profile. Once selected, the user confirms that synchronisation will take place, and the contractor's calendar is populated by the event.
  • Additional calendars of parties simultaneously updated in this example could include the winery manager and a specialist consultant to enable coordination with winemaking activities post harvesting. Unique events within the vineyard operator's calendar may also need to be reported to fourth and fifth parties for the purpose of monitoring spray activities and adherence to regulations. Like the other examples, if the user at some stage decides they will no longer synchronise with the third- party, they need only disconnect the link.
  • FIG. 7 shows a flowchart for alternative linking of events within calendars.
  • a user can create a new event in their calendar. When creating the event they have the option of "pushing" the event to the linked user. If they confirm this option, they can choose one or more third-parties to be updated with the event (step 706), and the user's calendar is updated simultaneously with those of the selected third- parties in step 708.
  • an email is sent to the third-party advising them of the new event posted in their calendars (step 709).
  • a Vet may create an event in their calendar that entails performing an optional health check on hoggets (step 702).
  • the Vet selects the user who is to be notified (step 706), and the user's calendar is updated with the event (step 708). Once the event is linked, any changes made to the event will update all linked calendars.
  • the course tutor may wish to create an event in their calendar that details an additional course requirement for a particular student or group of students, and have it populate the calendar of those students.
  • the tutor creates the event (step 702) and selects the student(s) (step 706), and their calendar is updated accordingly (step 708). Any changes to the event are synchronised between all linked calendars.
  • a Valuer who is a preferred supplier, may initiate an event to come and conduct a valuation of the project for mortgage purposes.
  • the Valuer creates the event (step 702) and "pushes" the event to the project developer's calendar by selecting them (as well as any other third parties) as the third-party in step 706, updating their calendar (step 708) together with those of any additional parties who are acting as observers.
  • the winery manager who is a preferred partner of a vineyard operator may initiate an event to visit the vineyard to determine the condition of grapes prior to harvesting.
  • the winery manager creates the event in step 702 and "pushes" the event to the vineyard operator's calendar together with other interested parties and observers in step 706.
  • An example of an event which the vineyard operator may create in step 702 is a new event such as spraying of grapes, which has been triggered by an environmental incident e.g. rain. Said event is required to be reported to a fourth party together with details relating to type of spray used and withholding periods, and is done so by simultaneously writing the event to a database which in turn updates the fourth party's calendar with the event (step 708).
  • Figure 6 shows a more detailed block diagram of some of the components of the web server 1 and server 3 that are used for scheduling and calendaring activities.
  • FIG. 2 The specific implementation shown in Figure 2 uses Enterprise JavaBeans (EJB) technology and the web server 1 is a Java Specification Request (JSR) 168 compatible portal server system.
  • EJB Enterprise JavaBeans
  • JSR Java Specification Request
  • server side architectures may be used, although Java has a number of features that make it advantageous for the specific implementation of a scheduling and calendaring system in accordance with the present invention.
  • Clients 2 access the web server 1 using web browser software 2a located on or accessible from their respective machines.
  • the web server 1 includes a servlet container
  • a portal collation servlet 11 provides direct access to the portal and provides the interface for web services with the clients 2.
  • the event population servlet 12 sets the event, which may include the parameters of the industry type and event type.
  • the parameters are passed on to the event population enterprise Java beans (EJB) process 13.
  • the event population EJB process 13 contains business logic that controls populating a calendar with an event sequence for each sub profile.
  • the business logic may use a key event as the base date for calculating the dates of each event and may use parameters associated with each event that specify whether the event can be automatically moved in time, whether a prompt should be sent to the user before moving an event and whether a third-party event sequence requires generation.
  • the event population EJB process 13 receives administrative data, for example the industry type, event type and event sequence from the event administration servlet 14.
  • the calendar servlet 15 contains the calendar information, defining the calendar times, days, weeks, months and years in which events may be located. For industry wide events, a master calendar may be managed by calendar servlet 15 for that industry, which populates events in all clients calendars that have set up a profile indicating that they belong to that industry. Commonly used event sequences may also be maintained by the calendar servlet as part of a sub profile calendar.
  • the calendar EJB process 16 contains the business logic to create new events within a master calendar and/or a sub profile calendar.
  • the profile servlet 17 enables the creation and maintenance of a master profile for each client and the sub-profiles associated with the master profile.
  • the master profile contains the geographical location of the client, which is used to match with 3rd parties.
  • the business logic used to set up the master and sub profiles is contained in a profile EJB process 18.
  • An administration servlet 19 acts as a database management server for a database 20.
  • the database 20 stores the data and instructions for the servlet and processes of the scheduling and calendaring system 101.
  • Communication with the database is through a database abstraction layer 21 , which may, for example include the Hybemate process provided in Java.
  • a messaging EJB process 22 manages the sending of notifications to clients who have set up a master profile, as required and as described herein above.

Abstract

L'invention concerne un système de planification et d'établissement de calendrier assorti d'un système de traitement informatique qui gère un plan d'exécution et/ou un calendrier pour une pluralité d'utilisateurs, et peut déterminer si des événements d'un premier programme d'événements nécessite un tiers et, si c'est le cas, remplir le programme et/ou le calendrier du tiers d'un second programme d'événements lié au premier.
PCT/NZ2006/000127 2005-05-20 2006-05-19 Systeme de planification et d'etablissement de calendrier WO2006123957A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
NZ540255 2005-05-20
NZ54025505 2005-05-20

Publications (1)

Publication Number Publication Date
WO2006123957A1 true WO2006123957A1 (fr) 2006-11-23

Family

ID=37431482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/NZ2006/000127 WO2006123957A1 (fr) 2005-05-20 2006-05-19 Systeme de planification et d'etablissement de calendrier

Country Status (1)

Country Link
WO (1) WO2006123957A1 (fr)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960406A (en) * 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web
US6064977A (en) * 1998-06-19 2000-05-16 International Business Machine Corporation Web server with integrated scheduling and calendaring
EP1122672A2 (fr) * 2000-02-04 2001-08-08 Palm Inc. Méthode et système pour la gestion d'un calendrier et d'informations personnelles
US6380959B1 (en) * 1996-09-27 2002-04-30 Timequarter Computing Corp. Web calendar architecture and uses thereof
WO2002097572A2 (fr) * 2001-05-31 2002-12-05 Palm, Inc. Systeme et procede de programmation d'un evenement sur un reseau
US6658427B2 (en) * 2001-06-12 2003-12-02 International Business Machines Corporation Method and system for providing multi-user electronic calendaring and scheduling functions for online instruction in an extended enterprise environment
US6781920B2 (en) * 2001-12-05 2004-08-24 International Business Machines Corporation Method for resolving meeting conflicts within an electronic calendar application
US6798753B1 (en) * 1999-10-14 2004-09-28 International Business Machines Corporation Automatically establishing conferences from desktop applications over the Internet

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6380959B1 (en) * 1996-09-27 2002-04-30 Timequarter Computing Corp. Web calendar architecture and uses thereof
US5960406A (en) * 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web
US6064977A (en) * 1998-06-19 2000-05-16 International Business Machine Corporation Web server with integrated scheduling and calendaring
US6798753B1 (en) * 1999-10-14 2004-09-28 International Business Machines Corporation Automatically establishing conferences from desktop applications over the Internet
EP1122672A2 (fr) * 2000-02-04 2001-08-08 Palm Inc. Méthode et système pour la gestion d'un calendrier et d'informations personnelles
WO2002097572A2 (fr) * 2001-05-31 2002-12-05 Palm, Inc. Systeme et procede de programmation d'un evenement sur un reseau
US6658427B2 (en) * 2001-06-12 2003-12-02 International Business Machines Corporation Method and system for providing multi-user electronic calendaring and scheduling functions for online instruction in an extended enterprise environment
US6781920B2 (en) * 2001-12-05 2004-08-24 International Business Machines Corporation Method for resolving meeting conflicts within an electronic calendar application

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Saving Time with Notes 6 Calendar and Scheduling", IBM, 1 October 2002 (2002-10-01), Retrieved from the Internet <URL:http://www.128.ibm.com/developerworks/lotus/library/ls-N6_CalSched/index.html> *

Similar Documents

Publication Publication Date Title
US7640165B2 (en) Web based methods and systems for managing compliance assurance information
US8296170B2 (en) Process management system and method
US7006978B2 (en) Method and systems for developing an acquisition integration project plan
US7877282B2 (en) System and method for a planner
US8041648B2 (en) Retail location services
Sheu et al. The effect of national differences on multinational ERP implementation: an exploratory study
US20020059283A1 (en) Method and system for managing customer relations
US20030040970A1 (en) Online classified advertising creation, management and viewing system
US8589308B1 (en) Grant management system and method
US20030088479A1 (en) Online scheduling system
US20070073572A1 (en) Data collection and distribution system
CN102122373A (zh) 基于网络的实施门户网站的自动化系统和方法
CA2579873A1 (fr) Systeme de gestion de listes de clients potentiels
CN100594494C (zh) 变更导航工具包
US20070011678A1 (en) Methods and systems for managing shared tasks
US20020016797A1 (en) Network based interviewing and processing system
US20030135403A1 (en) Method for tracking future support engineering requests
US20130031052A1 (en) Automated Database-Population Tool
US20090063223A1 (en) Systems and methods for assessing the level of conformance of a business process
US20080109267A1 (en) Online startup of an innovation project
US20040172268A1 (en) Method for creating a human resources and benefits website
JP2008527500A (ja) 自動化プロジェクトオフィス並びに自動リスク評価及び報告のためのシステム及び方法
JP6298089B2 (ja) 在宅ワーカーグループ集中管理装置及び在宅ワーカーグループ集中管理方法
WO2006123957A1 (fr) Systeme de planification et d&#39;etablissement de calendrier
US9110854B1 (en) Web-based community for disabled individuals

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06747704

Country of ref document: EP

Kind code of ref document: A1