JP3136239B2 - Schedule management device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[Industrial applications] Collaborative work in which multiple individuals such as meetings and meetings participate by connecting a plurality of personal schedule management devices that manage individual schedules or use reservation devices such as equipment and facilities via a wired or wireless network. And a schedule management device suitable for schedule adjustment and management.

[0002]

2. Description of the Related Art In recent years, information processing apparatuses such as electronic organizers, word processors, and personal computers have been provided with a schedule management function, and personal schedule management has been carried out using this function. Some of such schedule management devices are used alone, and some are capable of communicating with each other between the schedule management devices via a wired or wireless network.

Conventionally, as a schedule management device used alone, a “schedule data registration method” is used.
(Japanese Unexamined Patent Publication No. Hei 5-151163) or "an information processing apparatus having a schedule management function" (Japanese Unexamined Patent Publication No. Hei 5-1588).
No. 84) is known. In the former method, rank data indicating priority is added to each schedule data. Then, when an overlapping schedule registration request is input during the time slot in which the schedule has been registered, the rank data of the registered schedule is compared with the rank data of the new registration request, and one of the two is determined based on the comparison result. Register a schedule. The latter device is provided with a duplication-possible mode in which a new schedule can be registered in a time zone in which a schedule has already been registered.

As a plurality of schedule management devices connected via a network, a "schedule management system" (JP-A-5-6378) is known. This system interconnects a plurality of workstations each equipped with a schedule management unit of each individual via a network, inquires individual workstations about personal schedule information via the network, and based on the answer, a plurality of participants such as a conference. The coordinating work schedule is adjusted.

[0005] For example, a case will be described in which the organizer (or clerk) of a certain conference sets the scheduled date and time of the conference. In the above-described conventional schedule management system, the presiding party issues a schedule input request for the date and time of the conference to the schedule management device of each participant. If there is a person who cannot participate in the date and time of the event, a reply indicating that the person cannot participate is returned from his / her schedule management device. If there are any non-participants, the schedule will be cancelled,
Set a new date and time and reissue the schedule input request. If there are no non-participants, the date and time of the meeting is automatically registered in each participant's personal schedule.

[0006]

However, according to the above-described conventional schedule management method and schedule management apparatus, there are two schedules: mechanically searching for a schedule and registering if there is a vacancy, or unconditionally registering a schedule. Only the mode is considered, and there is a problem that the user of the schedule management device cannot judge whether to accept the schedule input request.

[0007] Also, in the method of adding rank data indicating priority to each schedule data, if a schedule having the highest priority has already been registered, even if a higher priority event occurs later, There was a problem that the schedule could not be registered.

When one schedule management device manages both an individual schedule and an allocation schedule of use time periods of equipment and facilities, individual schedule management in which individual judgment is to be taken into consideration, There has been a problem that the processing method with the schedule management of the equipment and facilities to be accepted without duplication on a first-come-first-served basis cannot be changed.

Furthermore, in a conventional system in which a plurality of schedule management devices are connected, when determining the schedule of a cooperative work that requires the participation of a plurality of persons, such as setting the date and time of holding a conference, it is appropriate that even one person is inconvenient. If the schedule cannot be determined and a date and time at which all the members can participate cannot be found, there is a problem that the schedule for the collaborative work such as the meeting date cannot be determined.

[0010] In view of the above problems, an object of the present invention is to provide a schedule management system in which a plurality of schedule management devices are connected via a network, wherein a user himself / herself accepts a schedule input request received from another schedule management device. It is an object of the present invention to provide a schedule management system capable of making a determination as to whether or not the schedule management system is in a normal state.

Another object of the present invention is to provide a schedule management apparatus capable of changing a processing method of an individual schedule management in which individual judgment is to be taken into consideration and a schedule management of equipment and facilities to be accepted without duplication on a first-come-first-served basis. To provide. Further, another object of the present invention is to provide a schedule management system capable of presenting a candidate date and time with a high degree of satisfaction based on a certain evaluation method even if a date and time at which all the participants of the collaborative work cannot participate is not found. That is.

[0012]

To solve the above problems, the present invention has the following arrangement. That is, in the first invention, in a schedule management device that has a schedule storage unit and is capable of mutually registering schedules in the schedule storage unit via a network, a schedule requester selects from among a plurality of processing types by a registration requester. Transmitting means for adding the specified processing type to each schedule registration request and transmitting the same , and receiving the storage contents of the schedule storage unit.
A schedule search unit that searches according to the schedule registration request, and checks whether a corresponding time slot is vacant or closed, a user inquiry unit that inquires a receiving user about whether or not the received schedule registration request can be registered, A registration control unit that processes a schedule registration request according to a processing type. And said
The processing type is that the schedule registration request is unconditionally registered.
Registered if there is free space in the required time zone
Registration after obtaining the normal type and the receiving user's approval
Approval type to be used.

[0013] The second invention each have a schedule storage unit, said schedule to each other via a network
In a schedule management device capable of registering a schedule in a file storage unit, a process type and schedule selected by a registration requester from a plurality of process types
Transmitting means for adding the priority of the registration request to each schedule registration request and transmitting the same; and searching the storage contents of the schedule storage unit in accordance with the received schedule registration request to determine whether a corresponding time slot is vacant or closed. and schedule search unit to examine, and the user inquiry section for inquiring the receiving user for registration whether the received said schedule registration request, according to the processing type received a registration control unit that processes the schedule registration request,
A schedule management device comprising: The processing type is a schedule registration request.
Type is registered unconditionally, and schedule registration
When the recording request does not overlap with the registered schedule
Is registered and if it overlaps, the registered schedule
Compare the registration request with the registration request.
If it is the same, contact the receiving user,
Normal type not registered if low, and approval of the receiving user
And an approval type registered after the acquisition.

[0014] In the third invention, each of the schedule records
Storage unit and mutually communicate with each other via a network.
Schedule that can be registered in the schedule storage section
Registered from multiple processing types in the rule management device
Schedule with the processing type selected by the requester
Transmission means for adding and transmitting each registration request, and a plurality of schedules
From the module registration request processing mode
Processing mode storage unit for storing the processing mode selected by
Before storing the contents stored in the schedule storage unit
Search according to the schedule registration request and the corresponding time
Schedule to check if obi is vacant or blocked
Search part and registration of the received schedule registration request possible
User inquiry to inquire the receiving user about rejection
And the processing mode is given priority over the processing type.
And a registration control unit that processes the schedule registration request.
A schedule management device comprising:
In the processing type, there is no schedule registration request.
Unconditional type registered in the condition and schedule registration required
If the request does not overlap with the registered schedule,
If there is an overlap, the registered schedule and registration
The request is compared with the registration request.
Record, and if they are the same, contact the receiving user and
Normal type that does not register if received, and approval of the receiving user
Approval type registered after that. The processing mode
Is unconditionally registered in the received schedule registration request.
Unconditional registration mode and schedule registration request
Mode according to the type of processing performed and all schedules
Authorization mode to ask the user for a
Including.

[0015] The fourth aspect of the present invention provides the first, second or third aspect.
In the description, the user inquiry unit includes a schedule
Use the schedule search result that includes the time zone
Includes a display control unit that is displayed simultaneously on the user inquiry screen.
When the user receiving the schedule registration request rejects the registration, the registration control unit automatically switches the display screen to the message transmission screen, and transmits the schedule registration request together with information indicating that the input request has not been registered. Includes a response unit that sends messages from rejected users.

According to a fifth aspect of the present invention, each of the schedules has a schedule storage unit, and the schedules are mutually exchanged via a network.
In the schedule management device capable of registering a schedule in the rule storage unit, any one or a combination or a plurality of each of the prospective participants of the cooperative work, the equipment / equipment used for the cooperative work, the date and time of the cooperative work, or each is pre-weighted. An evaluation function setting unit for setting an evaluation function relating to a schedule by attaching a schedule, and a transmission unit for transmitting a schedule registration request including the time and date and time of the cooperative work to each scheduled participant and / or the schedule management device of the equipment / equipment; A schedule search unit that searches the storage contents of the schedule storage device in accordance with the schedule registration request to create a free time list, a transmission unit that transmits the free time list to a schedule registration request source, and searches the received free time list And the time zone of the schedule registration request does not match the free time of all participants An evaluation function calculation unit that automatically searches the free time list to obtain a plurality of candidate schedules and evaluation function calculation values in the candidate schedules for different time zones; and sorts the evaluation function calculation values in descending order. A schedule management device comprising: a sorting unit; and a display control unit that displays a time zone corresponding to the evaluation function calculation value in a sorting order.

[0017]

According to a first aspect of the present invention, the information is transmitted via a network.
Schedule registration request should be processed
It is sent with the processing type added. Receive registration request
The schedule management device that has
Unconditional type to register contents unconditionally, to schedule
Normal type to register if available, ask the receiving user
Approval type that is registered after obtaining the approval 3
Determine the three processing types. And each processing module
Process the schedule registration request according to the protocol.

Further, in the second invention, the processing type is usually
The schedule data, the schedule search section
Searches the contents of the storage unit and responds to the schedule registration request.
Check whether the time zone is free
Determine whether If not, register. Heavy
If it is duplicated, it is already stored in the schedule data storage unit 5.
The priority of the registered schedule and the priority of the registration request
Compare. As a result of this comparison, if the priority of the registration request is high
register. If the priority of the registration request is low, it is determined not to be registered.
If the priorities are equal, ask the user. Third
In the invention, the registration control unit gives priority to the processing mode over the processing type
And perform the processing. Therefore, stored in the processing mode storage unit
Processing mode is determined and processed accordingly.
You. If the processing mode is the processing type determination mode, receive
The processing is performed according to the processing type.

Furthermore, the fifth invention is suitable for schedule management of a joint work such as a conference by a plurality of participants, and determines an evaluation function by weighting each participant and the equipment and facilities used for the joint work. This evaluation function becomes the maximum value when all the members of the joint work and all the necessary equipment / equipment are available.
Coefficients for each member and equipment / equipment are determined so that if equipment is missing, the value will be small. Then, a schedule registration request is transmitted to the schedule management device and the device / equipment reservation management device (also belonging to the schedule management device) of the members of the joint work via the network.

Next, the schedule management device and the device / equipment management device of each member that has received the schedule registration request search the free time from the schedule storage unit in the own device and create a free time list. Then, the idle time list is returned to the schedule registration request source.

The schedule management device that has issued the schedule registration request searches the idle time list returned from each communication destination schedule management device, and determines, for each predetermined unit time, the members and equipments whose time zones are idle. The equipment is totalized and the evaluation function is calculated. Then, the values of the evaluation function are sorted in descending order, and are displayed in order from the time zone in which the value of the evaluation function is large. Thus, even if there is no time zone in which all members and equipment / equipment are available, a schedule of joint work can be set in a time zone in which members, equipment / equipment and the like with high importance are available to some extent.

[0022]

Embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing the configuration of the first embodiment of the schedule management device according to the present invention . In the figure, 1 is an input unit for inputting a schedule registration request, 2 is an input buffer for temporarily storing a schedule registration request, 3 is a processing mode storage unit for specifying a processing mode of the schedule input request, and 4 is a processing mode based on the processing mode. A registration control unit 5 for controlling schedule registration by using a schedule data storage unit for storing schedule data that has already been registered; 6 a search for schedule data that has already been registered based on the registration request schedule data held in the input buffer. A schedule search unit that detects duplication, 7 is a user inquiry unit that makes a user inquiry in an approval mode, 8 is a schedule data registration unit that writes a requested schedule into the schedule data storage unit 5, and 9 is whether schedule data has been registered. Results that temporarily hold the results Buffer, 10 denotes an input request, the display unit for displaying the results, 11 a network interface unit for transmitting and receiving an input request and the registration result to another schedule management apparatus via a network (hereinafter, a network I
A network 12 connects a plurality of schedule management devices to each other. The schedule registration request may be input by the user himself from the input unit 1 or may be sent from another schedule management device via the network 12.

In the first embodiment, the processing mode selected by the user from the following four processing modes is stored in the processing mode storage unit 3. The first mode is an unconditional registration mode in which an input schedule registration request is unconditionally registered. The second mode is a normal mode in which registration is performed if the time slot of the schedule registration request is vacant. The third mode is a duplication approval mode in which registration is performed if the time slot of the schedule registration request is vacant, and if not, the user is inquired about whether or not registration is possible.
The fourth mode is an approval mode for inquiring the user of all schedule registration requests.

Next, the operation of the first embodiment will be described with reference to the flowchart of FIG. First, when a schedule registration request is input to the input buffer 2, it is determined whether the schedule registration request is received via the network or input by the user himself (step S1).
1). When the user himself inputs (N in step S11)
In o), the schedule is stored in the schedule data storage unit 5 (step S12), and the fact that the schedule has been registered is displayed on the display unit 10 in the own device via the result buffer 9 (step S13).

If the determination in step S11 is Yes,
Next, the processing mode stored in the processing mode storage unit 3 is determined (step S14). If the processing mode is the unconditional registration mode, the process proceeds to step S12, where the contents of the input buffer 2 are registered in the schedule data storage unit 5 by the schedule data registration unit 8.

If the processing mode is the normal mode, the schedule search unit 6 searches the contents of the schedule data storage unit 5 and checks whether a time slot corresponding to the schedule registration request in the input buffer 2 is vacant. It is determined whether there is any overlap (step S15). If there is no overlap, the process proceeds to step S12. If they overlap, a non-registration notification is stored in the result buffer 9 and the
The unit 11 notifies the schedule registration request source of non-registration via the network 12 (step S16).

If the processing mode is the overlapping approval mode,
The schedule search unit 6 searches the contents of the schedule data storage unit 5, checks whether a time slot corresponding to the schedule registration request in the input buffer 2 is vacant, and determines whether the time zone is duplicated (step S17). . If there is no overlap, the process proceeds to step S12. If they overlap, the user inquiry section 7 inquires of the user whether or not to register a schedule (step S1).
8). If the result of the inquiry is a registration instruction, the process proceeds to step S12. If the result of the inquiry is a registration rejection instruction, the process proceeds to step S16, and a non-registration notification is made.

If the processing mode is the approval mode, the user inquiry section 7 inquires of the user whether or not to register a schedule (step S18). If the result of the inquiry is a registration instruction, the process proceeds to step S12.
If the result of the inquiry is a registration rejection instruction, the process proceeds to step S16, and a non-registration notification is made.

In the above processing flow, all the schedule registration requests input by the user are registered. However, similar to the schedule registration requests sent from other schedule management devices via the network, duplication determination is performed. It can be changed to perform.

Next, the use of the first embodiment and the setting of the processing mode corresponding thereto will be described. For example, when one schedule management device has a role of a schedule board for storing schedules of all members, the processing mode of the schedule management device is set to the unconditional registration mode, and Can input his / her own schedule to the schedule management device dedicated to himself / herself, and at the same time, can transmit a schedule registration request to the schedule management device that manages the schedule board and write the schedule board. Since the schedule board management device unconditionally registers and stores all schedule registration requests, the schedule board management device stores all the schedules of the members regardless of the overlapping of the schedules.

In the case where one schedule management device has a function of managing reservation of use of equipment and facilities such as reservation of a conference room, the normal mode is set. In the normal mode, only one of the schedule registration requests, which is the earliest in time, is accepted, and a first-come-first-served reservation system can be realized.

When used for other purposes, the processing mode may be set according to the user's preference. If it is not desired that a schedule request from another person be registered without permission, this can be realized by setting an approval mode.

As a modification of this embodiment, the processing mode can be changed only at a specific date and time. For example,
If another schedule is to be restricted on Friday for a specific job, it is possible to use the schedule registration on Friday as the approval mode and the other day as the overlap mode.

FIG. 2 is a block diagram showing the configuration of a second embodiment of the schedule management device according to the present invention . In the figure, 1 is an input section for inputting a schedule registration request, 2 is an input buffer for temporarily storing a schedule registration request, 3 is a processing type buffer for storing a processing type for each schedule input request, and 4 is a processing type buffer. A registration control unit 5 for controlling schedule registration by using a schedule data storage unit for storing schedule data that has already been registered; 6 a search for schedule data that has already been registered based on the registration request schedule data held in the input buffer. Schedule search unit for detecting duplication, 7
Is a user inquiry section for inquiring of the user whether or not schedule registration is possible, 8 is a schedule data registration section for writing the requested schedule to the schedule data storage section 5, and 9 is a temporary storage of whether or not schedule data has been registered. A result buffer 10, a display unit for displaying input requests, results, and the like; 11, a network IF unit for transmitting and receiving input requests and registration results to other schedule management devices via a network; Network to connect to.

In the second embodiment, a processing type selected by the schedule registration requester from the following three processing types is added to each schedule registration request. The first type is an unconditional registration type in which an input schedule registration request is unconditionally registered. Second
Is a normal type in which registration is performed if schedule registration requests do not overlap, and processing is divided into registration, user inquiry, and non-registration by priority comparison if they overlap. The third type is an approval type for inquiring a user of a schedule registration request. In this embodiment, the priority is added to each of the normal registration type schedule registration requests. If the schedules overlap, the priority of the already stored schedule is compared with the priority of the registration request. Register if the priority of is high,
If the priorities are the same, an inquiry is made to the user, and if the priority of the registration request is low, the registration is not performed.

Next, the operation of the second embodiment will be described with reference to the flowchart of FIG. First, when a schedule registration request is input to the input buffer 2, it is determined whether the schedule registration request is received via the network or input by the user himself (step S2).
1). When the user himself inputs (N in step S21)
In o), the schedule is stored in the schedule data storage unit 5 (step S22), and the fact that the schedule has been registered is displayed on the display unit 10 in the own device via the result buffer 9 (step S23).

If the determination in step S21 is Yes,
Next, the processing type stored in the processing type storage unit 3 is determined (step S24). If the processing type is the unconditional registration type, the process proceeds to step S22, and the contents of the input buffer 2 are registered in the schedule data storage unit 5 by the schedule data registration unit 8.

If the processing type is the normal type, the schedule search unit 6 searches the contents of the schedule data storage unit 5 and checks whether a time slot corresponding to the schedule registration request in the input buffer 2 is vacant. It is determined whether or not they overlap (step S25). If there is no overlap, the process proceeds to step S22. If they overlap, the priority of the schedule already stored in the schedule data storage unit 5 is compared with the priority of the registration request (step S26).

As a result of the comparison, if the priority of the registration request is high, the process proceeds to step S22 for registration. If the priority of the registration request is low, the process moves to step S27 to deregister.
If the priorities are equal, the process moves to step S28 to be described later to inquire the user. In step S27, the non-registration notification is stored in the result buffer 9, and the network IF unit 1
1. A non-registration notification is sent to the schedule registration request source via the network 12.

If the processing type is the approval type, the user inquiry section 7 inquires of the user whether or not to register a schedule (step S28). If the result of the inquiry is a registration instruction, the process moves to step S22.
If the result of the inquiry is a registration rejection instruction, the flow proceeds to step S27, and a non-registration notification is made.

FIG. 3 is a block diagram showing the configuration of the third embodiment of the present invention. In the figure, 1 is an input unit for inputting a schedule registration request, 2 is an input buffer for temporarily storing a schedule registration request, 3 is a processing mode storage unit for specifying a processing mode of the schedule input request, and 13 is each schedule input request , A registration control unit for controlling the schedule registration based on the processing mode and the processing type, 5 a schedule data storage unit for storing the already registered schedule data, and 6 an input buffer. A schedule search unit for searching for already registered schedule data based on the held registration request schedule data and detecting duplication, 7
Is a user inquiry section for inquiring of the user whether or not schedule registration is possible, 8 is a schedule data registration section for writing the requested schedule to the schedule data storage section 5, and 9 is a temporary storage of whether or not schedule data has been registered. A result buffer 10, a display unit for displaying input requests, results, and the like; 11, a network IF unit for transmitting and receiving input requests and registration results to other schedule management devices via a network; Network to connect to.

In the third embodiment, the processing mode of the first embodiment and the processing type of the second embodiment are used together.
As the processing mode, a processing mode selected by the user from the following three processing modes is stored in the processing mode storage unit 3. The first mode is an unconditional registration mode in which an input schedule registration request is unconditionally registered. The second mode is a mode according to the processing type added to the schedule registration request. The third mode is an approval mode for inquiring the user of all schedule registration requests.

As the processing type, a processing type selected by the schedule registration requester from the following three processing types is added to each schedule registration request. First
Is an unconditional registration type in which the input schedule registration request is unconditionally registered. The second type is a normal type in which schedule registration requests are registered if they do not overlap, and if they do, processing is divided into registration, user inquiry, and non-registration by priority comparison. The third type is an approval type for inquiring a user of a schedule registration request.

In this embodiment, as in the second embodiment,
A priority is added to each schedule registration request of the normal registration type. If the schedules overlap, the priority of the already stored schedule is compared with the priority of the registration request. If the priority of the registration request is high, If the registration and the priority are equal, the user is inquired. If the priority of the registration request is low, the registration is not performed.

Next, the operation of the third embodiment will be described with reference to the flowchart of FIG. First, when a schedule registration request is input to the input buffer 2, it is determined whether the schedule registration request is received via the network or input by the user himself (step S3).
1). When the user himself inputs (N in step S31)
In o), the schedule is stored in the schedule data storage unit 5 (step S32), and the fact that the schedule has been registered is displayed on the display unit 10 in the own device via the result buffer 9 (step S33).

If the determination in step S31 is Yes,
Next, the processing mode stored in the processing mode storage unit 3 is determined (step S34). If the processing mode is the unconditional registration mode, the process proceeds to step S32, where the contents of the input buffer 2 are registered in the schedule data storage unit 5 by the schedule data registration unit 8.

If the processing mode is the processing type determination mode, the processing type stored in the processing type buffer 13 is determined (step S35). If the processing type is the unconditional registration type, the process proceeds to step S32, where the contents of the input buffer 2 are registered in the schedule data storage unit 5 by the schedule data registration unit 8.

If the processing type is the normal type, the schedule search unit 6 searches the contents of the schedule data storage unit 5 and checks whether a time slot corresponding to the schedule registration request in the input buffer 2 is vacant. It is determined whether there is any overlap (step S36). If there is no overlap, the process moves to step S32. If they overlap, the priority of the schedule already stored in the schedule data storage unit 5 is compared with the priority of the registration request (step S37).

As a result of the comparison, if the priority of the registration request is high, the process proceeds to step S32 for registration. If the priority of the registration request is low, the process proceeds to step S38 for non-registration.
If the priorities are equal, the process moves to step S39 to be described later to inquire the user. In step S38, the non-registration notification is stored in the result buffer 9, and the network IF unit 1
1. A non-registration notification is sent to the schedule registration request source via the network 12.

If the processing type is the approval type, the user inquiry section 7 inquires of the user whether or not to register a schedule (step S39). If the result of the inquiry is a registration instruction, the process moves to step S32.
If the result of the inquiry is a registration rejection instruction, the process moves to step S38, and a non-registration notification is made.

In the present embodiment, the processing mode is determined prior to the processing type, but the processing type may be determined prior to the processing mode.

FIG. 7 shows a screen display example of a user inquiry in the above embodiment. Suppose that Togawa Manager sent a schedule request for “Meeting from 15:00 to 18:00 on December 9” to a certain user U. The schedule management device that has received the schedule registration request displays the schedule registration request 101 and
The schedules 102 before and after the schedule request are read from the schedule data storage unit and displayed at the same time. Thus, the user U can immediately determine whether to accept or reject the schedule registration request only by looking at the display screen of the schedule management device. In addition,
While displaying the schedule registration request 101, [Registration] 103
And [Cancel] 104 indicate the type of input by the user, such as a key or a touch panel, for a response.

[Cancel] on the operation screen shown in FIG.
When a response of 104 is made, the screen is switched to the operation screen of FIG. 8, and an operation screen 105 for returning a rejection response to the schedule registration request is displayed. Then, on the operation screen of FIG. 8, it is possible to transmit a message about the reason of schedule registration refusal, etc., and when there is a message, [Yes]
106 is designated, and when there is no such designation, [none] 107 is designated.

In the operation screen shown in FIG.
Is designated, a message is input from the attached keyboard or handwriting input device or the like and displayed on the operation screen. FIG. 9 shows the state of the operation screen after the message is input. In this example, a message is written saying, "We are closed all day for the new WS workshop. OK in the morning of the 8th." This message is returned to the requesting schedule management device together with the information that the schedule registration request has been rejected.

FIG. 10 is a block diagram showing the configuration of a fourth embodiment of the schedule management device according to the present invention . In the figure, 1 is an input unit for inputting a schedule registration request and a search request, 2 is an input buffer for temporarily holding an input, 5 is a schedule data storage unit for storing already registered schedule data, and 6 is a requested data. A schedule search unit for searching for a schedule of a condition, 8 is a schedule data registration unit for writing a schedule in the schedule data storage unit 5, 9 is a search result buffer for temporarily holding a search result of schedule data, 10 is a search request, search result, and registration. Display section for displaying requests, registration results, etc., 1
1 is a network interface for transmitting / receiving a search request, a search result, and the like to / from another schedule management device via a network.
And 12, a network for interconnecting a plurality of schedule management devices, 16 an evaluation function operation unit for calculating the value of the schedule evaluation function, and 17 a sorting unit for sorting the evaluation function values for each search result.

In the fourth embodiment, a schedule of cooperative work is set from the master schedule management device to a plurality of slave schedule management devices, and all schedule management devices connected to the network are set. Have the same configuration, the schedule of the cooperative work can be set from any schedule management device. However, it goes without saying that the dedicated master schedule management device and slave schedule management device may be mutually connected via a network.

Next, the operation of the fourth embodiment will be described with reference to a flowchart. FIG. 11 shows a processing flow on the master schedule management device side for transmitting a search request for setting a schedule for cooperative work. First, in the initial state, the process waits for the user of the schedule management device to input a schedule search request (step S41). The search request includes the contents of the schedule (for example, the name of the meeting), the required time, the range of the desired setting date and time, the members of the cooperative work (for example, the person to be invited to the meeting), and the equipment and equipment necessary for the cooperative work (for example, , Meeting room, blackboard).

Next, when a schedule search request is input from the input unit 1, the schedule is requested via the network IF unit 11 to each slave schedule management device that manages the schedule of the target person and the equipment / equipment. Send a free time search request (step S4)
2). In the slave schedule management device, one schedule management device may manage one schedule or a plurality of schedules. The same applies to the device / equipment schedule management device. One schedule management device may manage the schedule of one device / equipment, or may manage the schedule of a plurality of devices / equipment.

Next, a response to the search request is waited for from the slave schedule management device of the communication destination (step S).
43). When a search result is returned as a free time list from all slave schedule management apparatuses, the free time list is stored in the search result buffer 9. And
The evaluation function calculation unit 16 totals the free time of the target person for each candidate time zone, and calculates an evaluation value in that time zone. Next, the evaluation values are sorted in descending order, and the evaluation values are arranged in order from the candidate time zone having the highest evaluation value (that is, having the highest degree of participation satisfaction) (step S44). Next, the schedule setting candidate time zone, which is the search result, is displayed on the display unit 10 (step S45).

Here, the user of the master schedule management device (that is, the person who sets and uses the schedule of the cooperative work) sees this display and selects and inputs the time zone for which the schedule is to be set from the candidate time zones. If there is no satisfactory time zone, the schedule setting is canceled (step S46). Once the user ’s time of day selection results are entered,
A schedule registration request is transmitted for the selected time zone (step S47). The transmission destination here may be a device that manages the schedule of the schedule management target (person, equipment / equipment) specified by the user in step S41, or if the schedule is vacant in the time zone selected in step S46. It may be limited to only the target that is present.

This is because, on the side receiving the schedule registration request, there may be a case where the registration is performed after confirming the intention of the cooperative work participant in addition to the case where the schedule is automatically registered. . This is because when confirming the intention of the individual, even if another schedule has already been input, the schedule may be canceled and the schedule received this time may be registered.

Next, an answer to the schedule registration request is received (step S48), and the result of the schedule registration is displayed (step S49). This is because the schedule is vacant, but there is a case where the person who received the registration request refuses the registration (replying that he / she will not participate), so that the participants are finally displayed.

FIG. 12 shows a processing flow of the slave schedule management device which receives the schedule search request. First, it is checked whether the schedule search request has arrived via the network (step S).
51). When the search request arrives, a process of receiving the search request is performed (step S52). Next, it is checked whether the registration request has arrived (step S53). When a registration request arrives, schedule registration processing is performed (step S
54). The schedule registration process may be performed by, for example, registering the schedule of the request if the schedule has not been input in the time slot in which the registration request has been made, or registering the schedule after confirming with the user of the slave schedule management device.

The processing flow of the master schedule management device (transmission side) in FIG. 11 and the processing flow of the slave schedule management device (reception side) in FIG. 12 are described separately. It may have both functions so that it may become a slave schedule management device or a master schedule management device. When the person who sets the schedule of the cooperative work also serves as the participant, the master schedule management device also serves as one slave schedule management device.

FIG. 13 is a process flow for explaining the details of the search request receiving process. This corresponds to step S5 in FIG.
2 is supported. First, a free time is searched from the schedule data stored in the schedule management device (step S61). Next, it is determined whether the searched free time satisfies the required condition (step S62). If the required condition is satisfied, the idle time is stored (step S63). Next, it is checked whether there is no data for the period to be searched (step S64). If data for the period to be searched remains, the process returns to step S61. If there is no data for the period to be searched, the idle time list is transmitted to the master schedule management device.

FIG. 14 is a processing flow for explaining details of prioritization of search results in the master schedule management device. This corresponds to step S44 in FIG. First, a two-dimensional table is created in which participants, equipment / equipment, and candidate time zones of the cooperative work have respective dimensions, and the idle time received from each slave schedule management device is entered in this table (step S71). This is expressed as data in a two-dimensional array, the details of which will be described later.

Next, an evaluation value for each unit time is calculated using the created table. Next, the evaluation values for each unit time that is temporally adjacent are added by the length of the schedule required time to obtain an overall evaluation value (step S73). Next, the total evaluation values are sorted and arranged in the descending order of the values (the descending order of the priority) (step S74).

Next, details of the above-described search result prioritization will be described based on a specific schedule setting example. FIG. 15 is a display example of a screen for receiving a schedule setting request. In FIG. 15, an underlined portion indicates an input from the user. In this example, a two-hour "progress meeting" is set between March 1 and March 2. Further, in the example of FIG. 15, the communication partner stored in the schedule management device is displayed on the window, and the user simply transmits the schedule search request by designating the location where the name of the person to be invited to the conference is displayed. You should be able to identify who you should be. At the same time, facilities and equipment such as a conference room and an electronic blackboard are also displayed in the window, and when these are designated, the schedule management device managing the reservation for use can be selected as the communication partner.

FIG. 16 shows a state where the conference room 2 has been selected. The user has selected “required” as the priority of the conference room 2. Priority indicates the degree to which members or equipment / equipment, etc. are required for collaborative work to be scheduled, and it is essential (very important), high importance, and low importance Is set.

However, if there are two meeting rooms and it is essential that only one of them can be used, an item “essential (only one of the previous selection item and one of the previous selection items)” is prepared. This is OK if one of the required items selected before that can be participated or used.

FIG. 17 shows an example of a condition for setting the priority and an example of an expression for calculating an evaluation value (evaluation function) created from the condition. This evaluation function is calculated every certain unit time. This unit time is a minimum unit for storing a schedule, in other words, a minimum block for setting a schedule. The setting of the unit time may be 15 minutes, 30 minutes, 1 hour, or the like. If you set the unit time too small,
The storage capacity required for schedule storage increases, and processing such as idle time search becomes slow. Also, if the unit time is set long, even if there is a short idle time, it will not be used effectively.

In the calculation formula of FIG.
Is the name of a binary variable that becomes 1 if the schedule of the conference room 1 is vacant and 0 if it is closed in a certain unit time. The operator “or” indicates a logical sum, the operator “and” indicates a logical product, the operator “*” indicates an arithmetic product, and the operator “+” indicates an arithmetic sum.

TH1, TH2, and TH3 are constants to be multiplied according to the degree of importance, respectively, and TH1>TH2> TH3
In a relationship. If these constants are set to the power of 2, the multiplication is replaced with a shift, and the calculation of the evaluation function can be speeded up. In addition, other conditions for determining the priority of the schedule can be considered.For example, the time elements such as morning is desirable, Friday is desired to be avoided, and the earliest possible is evaluated by a logical expression, multiplication, and addition. Can be expressed in functions.

FIG. 18 is an example of a table created on the memory after receiving an answer under the conditions of FIG.
Here, 8-18: 00 on March 1 (8-17 on the display)
Hour), and a table for 8-18 o'clock on March 2 is created with a unit time of one hour. In the figure, the portion indicated by ● indicates a time slot in which the schedule is vacant, and indicates that the schedule is closed in other times.

The item of “priority” in the second line from the bottom in FIG. 18 is a value for each unit time obtained according to the evaluation formula in FIG. The bottom line is the overall priority. This is not the evaluation value of the unit time but the sum of all the evaluation values in the requested time zone. Here, since the conference is set for two hours, it is obtained by adding the evaluation values for two hours. For example, at 8:00 on March 1, 12 + 123 is obtained as the comprehensive evaluation value in the time zone from 8:00 to 10:00, and 135 is described.

FIG. 19 shows a list displayed in descending order of the total priority sorting result of FIG. In FIG. 19, 9-11: 00 on March 1 (overall evaluation value 246), March 1
10-12: 00 on the day (Comprehensive evaluation value 236), March 2 13-
15:00 (overall evaluation value 236) and March 1st, 12-14 o'clock (overall evaluation value 235) are displayed. Then, the user sees this screen, selects at which time zone the conference is to be set, and inputs the number by number. The lower half of FIG.
This is a display after the user response is input, and transmits a schedule registration request to this conference participant (schedule management device) for this time zone. Similarly, the reservation request is transmitted to the schedule management device that manages the reservation for using the conference room 1 and the electronic blackboard.

When the schedule registration request and the equipment / equipment reservation request are transmitted to all the related schedule management apparatuses, and all the replies are returned, the user is asked "conference room 1, electronic blackboard, A manager, B section manager, C,
"We held the schedule for D, E, and X." and "Meeting room 1, electronic blackboard, director A, and C, D, E, and X, but section B had a production confirmation meeting. And cannot attend the meeting. "

Of course, even if not all responses have returned, a status report can be presented after a certain period of time, or a status report can be displayed on the screen whenever the user instructs to view the current response status. preferable. In this case, it says, "We have held the schedule for meeting room 1, electronic blackboard, director A, and X. We have not yet received a reply for the schedule for section B, C, D, and E." Display.

[0079]

As described above, according to the present invention, in a schedule management system in which a plurality of schedule management devices are connected via a network, a user himself / herself responds to a schedule input request received from another schedule management device. There is an effect that it is possible to provide a schedule management system capable of determining whether or not to accept. Further, according to the present invention, it is possible to provide a schedule management device capable of changing a processing method of an individual schedule management in which individual judgment is to be considered and a schedule management of equipment and facilities to be accepted without duplication on a first-come-first-served basis. This has the effect.

Further, according to the present invention, there is provided a schedule management system capable of presenting a candidate date and time with a high degree of satisfaction based on a certain evaluation method even if a date and time at which all the participants of the cooperative work cannot participate is found. There is an effect that can be.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a first embodiment of a schedule management device according to the present invention.

FIG. 2 is a block diagram showing a configuration of a second embodiment of the schedule management device according to the present invention.

FIG. 3 is a block diagram showing a configuration of a third embodiment of the schedule management device according to the present invention.

FIG. 4 is a flowchart showing the operation of the first embodiment of the schedule management device according to the present invention.

FIG. 5 is a flowchart showing an operation of the second embodiment of the schedule management device according to the present invention.

FIG. 6 is a flowchart showing an operation of the third embodiment of the schedule management device according to the present invention.

FIG. 7 is a screen display example of the schedule management device according to the present invention.

FIG. 8 is a screen display example of the schedule management device according to the present invention.

FIG. 9 is a screen display example of the schedule management device according to the present invention.

FIG. 10 is a block diagram showing a configuration of a fourth embodiment of the schedule management device according to the present invention.

FIG. 11 is a flowchart showing the operation of the master schedule management device of the fourth embodiment.

FIG. 12 is a flowchart showing an operation of the slave schedule management device of the fourth embodiment.

FIG. 13 is a flowchart illustrating details of a search request receiving process according to the fourth embodiment.

FIG. 14 is a flowchart illustrating details of a search result prioritization process according to the fourth embodiment.

FIG. 15 is a display example of a schedule input screen according to the fourth embodiment.

FIG. 16 is a display example of a priority order input screen according to the fourth embodiment.

FIG. 17 is a display example of an evaluation function setting screen according to the fourth embodiment.

FIG. 18 is an example of a table created from a schedule search result of the fourth embodiment.

FIG. 19 is a display example of a screen on which a user of the fourth embodiment inputs schedule selection.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 Input part 2 Input buffer 3 Processing mode storage part 4 Registration control part 5 Schedule data storage part 6 Schedule search part 7 User inquiry part 8 Schedule data registration part 9 Result buffer 10 Display part 11 Network interface part 12 Network 13 Processing type buffer 14 Registration control unit 15 Registration control unit

────────────────────────────────────────────────── ─── Continuation of the front page (56) References JP-A-6-119272 (JP, A) JP-A-5-1665836 (JP, A) JP-A-5-6378 (JP, A) JP-A-1- 206459 (JP, A) JP-A-63-85967 (JP, A) JP-A-6-4542 (JP, A) JP-A-6-139248 (JP, A) JP-A-64-21446 (JP, A) JP-A-1-116880 (JP, A) JP-A-2-292665 (JP, A) JP-A-1-206460 (JP, A) JP-A-64-109060 (JP, A) (58) (Int.Cl. ⁷ , DB name) G06F 17/60 162

Claims (1)

(57) [Claims] And a schedule storage unit.
The schedules are mutually stored in the schedule storage unit via the network.
To a schedule management device that can register joules
Oite is selected by the registration requester from among a plurality of processing types
And the processing type added to each schedule registration request.
Transmitting means to communicate with, and the receiving side from among a plurality of schedule registration request processing modes.
A processing mode for storing the processing mode selected by the user.
The storage contents of the schedule storage unit and the schedule storage unit.
Search according to the schedule registration request, and the corresponding time zone
Scheduled search to find out if it is empty or blocked
And whether or not the received schedule registration request can be registered
A user inquiring unit for inquiring of a receiving side user ;
A registration control unit for processing a schedule registration request , wherein the processing type is an unconditional type in which the schedule registration request is unconditionally registered.
And the schedule registration request overlaps with the registered schedule
Register if not, registered if duplicate
The schedule of the registration request is compared with the schedule of the registration request.
If the priority is high, register it.
Normal type that is queried and not registered if low, and approval type that is registered after receiving the approval of the receiving user
When, wherein the said processing mode, no reception schedule registration request is registered unconditionally
According to the condition registration mode and the processing type added to the schedule registration request
Mode and a request to inquire the user of all schedule registration requests.
Schedule management apparatus which comprises a certification mode, the.