JPH05134989A - Schedule managing system - Google Patents

Abstract

PURPOSE:To perform reasonable scheduling by judging whether or not a newly registered schedule is feasible from relation with an already registered schedule. CONSTITUTION:When a conference presidency side inputs an opening notice to this system, the system takes out the information of a place before or after the conference schedule time of the day fixed for conference by making access the schedule list of every person concerned. When the information of the place is obtained. the system makes access a travel time data base, and retrieves travel time in the intervals of the informed place fixed for conference and the place before or after the conference schedule time of the day fixed for conference in the day fixed for conference obtained from an informed place of conference and the above-mentioned individual schedule table. The system judges whether or not the person can attend the conference from retrieved travel time and a time when a job is finished before the schedule time of conference. The system automatically updates the place fixed for conference, the place fixed for conference, and the content fixed for conference. etc., automatically updated on the schedule table of the person concerned completing an operation in step S6.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a schedule management system for registering various schedules.

[0002]

2. Description of the Related Art Conventionally, in a schedule management system, for example, when registering a meeting schedule, the administrator inputs a meeting notification to the related persons and at the same time, the schedule table of the persons concerned is automatically filled. ing.

[0003]

However, in the above-mentioned conventional example, since there is no consideration of the traveling time and the like, an unreasonable schedule is set up so that the meeting is too late, and it is apparently impossible to attend. , There was a defect that the information did not reach the administrator.

The present invention has been made in view of the above problems, and when a new schedule is registered in an individual schedule table, this new schedule can be executed in relation to the already registered schedule. An object of the present invention is to provide a schedule management system that performs reasonable scheduling by determining whether or not it is.

[0005]

In order to achieve the above object, a schedule management system according to the present invention has the following configuration. That is, in a schedule management system having a schedule input means for registering a new schedule in the personalized schedule table, it is determined whether or not the schedule newly input by the input means can be executed from the relationship with the already registered schedule. Determination means to
Update means for executing the update of the individual schedule table based on the result determined by the determining means.

[0006]

When a new schedule is registered in the personalized schedule table, it is possible to perform reasonable scheduling by judging whether or not this new schedule can be executed based on the relationship with the already registered schedule.

[0007]

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

<First Embodiment> FIG. 1 is a block diagram showing the configuration of the schedule management system of the present embodiment.
1 is a schedule management server that manages the schedule of each registered user, 2 is a database in which the travel time between regions is registered, and 3, 4 and 5 are data for users to use the server function. The communication device 6 is a LAN that connects the data communication devices (3, 4, 5) and the schedule management server 1.

FIG. 2 is a schedule table managed by the schedule management server 1 of this embodiment. In FIG. 2, (a) is a schedule table of Mr. A, (b) is a schedule of Mr. B, and (c) is a schedule table of Mr. C.

FIG. 3 is a travel time table of the database 2 in which travel times between regions are registered. In the table, the time 8 required to move between the areas designated in the section 7 is registered.

FIG. 4 is a flow chart showing the operation of the schedule management system according to the present embodiment by taking a notification of holding a conference as an example.

The operation of the schedule management system of this embodiment will be described with reference to the flow chart of FIG.

First, in step S1, the conference organizer inputs a notice of holding into the present system. At that time, the keywords are the selected parties (which must have a count in the system in advance), the date and time of the meeting, and the place where the meeting is held. Now, here is 1
The venue will be Tokyo Headquarters from 5:30 to 17:30.

Next, in step S2, the present system accesses the schedule table of the selected persons in the schedule management server 1 and extracts the information about the place before and after the scheduled conference time of the conference. Figure 2 on the schedule
It contains the information of the place from what time to what time. Here, Mr. A of (a) is scheduled to participate in the meeting in Tokyo until 15:00 and then from 18:00. In addition, Mr. B of (b) will meet in Chiba until 15:00 and will participate in the meeting in Tokyo from 18:00. And C in (c)
He will meet in Tokyo until 15:00 and will participate in the meeting in Yokohama from 18:00.

When the location information is obtained, the system accesses the travel time table (FIG. 3) of the travel time database 2 in step S3. As shown in FIG. 3, the travel time 8 in the regional section 7 is registered in the travel time table. Next, in step S4, the travel time in the section between the conference holding place notified in step S1 and the place before and after the scheduled conference holding time on the conference holding date obtained in step S2 is searched. According to FIG. 3, the travel time between Tokyo and Chiba is 80 minutes, and the travel time between Tokyo and Yokohama is 40 minutes. Here, the travel time between Tokyo and Tokyo is regarded as 0 minutes because the location does not change.

In step S5, the system determines whether the relevant person can attend the meeting based on the retrieved travel time, the time when the work before the meeting is scheduled to end, and the meeting holding time. In the case of Mr. A, both before and after the scheduled meeting time are in Tokyo, and the schedule is vacant in terms of time. In this way, if the distance is such that there is no problem in terms of time, the system automatically updates the schedule table of the person concerned with the holding time, holding place, holding contents, etc. in step S6 and ends.

In the case of Mr. B, he is in Chiba before the scheduled conference time and takes 80 minutes to travel, so it is impossible to attend the conference. Also, in the case of Mr. C, he must be in Yokohama by 18:00 at the scheduled meeting time, and it will be searched that it will take 40 minutes to move, so he cannot be in Tokyo until 17:30. In this way, when it is determined that it is not possible to move in time, the system does not update the schedule table of the people concerned, but leaves only the notice that the conference will be held in step S7 as an email, and in step S8 the list of conference absentees. Is created on the system side.

<Embodiment 2> In the above embodiment, for example, in the case of Mr. C of FIG. 2, if the meeting from 15:30 is left early, the next meeting can be attended. In this way, a system that considers the wishes of the parties concerned can be considered. This will be described as a second embodiment.

FIG. 5 shows a flow chart of the second embodiment.
Steps S11 to S17 are step S1 in FIG.
To S7. The difference is step S1
8 and step S19. In step S15,
After it is determined that the user cannot attend the conference based on the traveling time, the user receives the notice of holding the conference in step S17. In step S18, the system waits for an attendance reply.
The user himself / herself answers the attendance of the conference, and the system receives and judges it in step S19.

If the answer is attendance, step S1
In step 6, the system inserts the time schedule, venue, content, etc. into the schedule of the relevant persons and ends. If you are absent, the system ends. Further, when the absence is set in step S19, it is possible to create the absence list of the conference on the system side as in the first embodiment.

Further, in the above-mentioned conventional example, whether or not the schedule can be executed is determined by focusing only on the travel time between regions, but the present invention is not limited to this, and priority may be added in addition to the travel time. It is possible.

As described above, according to the present embodiment, it is possible to set up a schedule that is comfortable for the travel time in each person's schedule table, and the administrator can find out who is absent from the list. There is an effect.

The present invention may be applied to either a system composed of a plurality of devices or an apparatus composed of a single device. Further, it goes without saying that the present invention can be applied to the case where it is achieved by supplying a program to a system or an apparatus.

[0024]

As described above, according to the schedule management system of the present invention, when a new schedule is registered in the personalized schedule table, the new schedule is registered because of the relationship with the already registered schedule. Reasonable scheduling can be performed by determining whether the schedule is feasible.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of a schedule management system according to an embodiment.

FIG. 2 is a diagram showing a schedule table managed by a schedule management server according to the present embodiment.

FIG. 3 is a diagram showing a travel time table of a database in which travel times between regions are registered.

FIG. 4 is a flow chart showing an operation of the schedule management system according to the first embodiment, taking an example of a notice of holding a conference.

FIG. 5 is a flowchart illustrating an operation of a schedule management system according to a second exemplary embodiment using a notice of holding a conference.

[Explanation of symbols]

 1 Schedule Management Server 2 Travel Time Database 3, 4, 5 Data Communication Device 6 LAN

Claims (3)

[Claims] 1. A schedule management system for registering and updating schedule information for each individual, and a judging means for judging whether or not a predetermined individual's schedule can be executed based on the registered schedule information, and a judgment by the judging means. A schedule management system comprising: an updating unit that updates the schedule information of the individual based on the result. 2. The schedule management system according to claim 1, wherein the determination means is implemented based on a designated time and a travel time between locations. 3. The schedule management system according to claim 1, further comprising a determination result output unit that outputs the scheduling status of each individual based on the determination result by the determination unit.