JPH0581285A - Method for conference room reservation - Google Patents

Abstract

PURPOSE:To provide a conference room reserving method capable of shortening time required from the user's input of a conference room reserving condition up to the reception of information indicating the validity/invalidity of reservation registration and storing reserving information and conference room history information in one file. CONSTITUTION:A CPU 9 stores a time band from which a time secured by the reservation of one conference room at the same date in a vacant room managing file 7 in each reservation, judges whether a time band to be reserved by a successively inputted reservation has been secured or not, informs the validity/invalidity of the formation of the inputted reservation to a reservation inputting user through a CRT 1, and stores the information of the conference room to be used by the inputted reservation, the information of a using date, charging information, and reservation validity/invalidity information in a conference room reserving file 6.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a conference room reservation system.

[0002]

2. Description of the Related Art FIG. 7 is a block diagram of a conventional conference room reservation system, FIGS. 8 and 9 are diagrams showing the contents of a conference room reservation file 6'and a conference room history file 8 in FIG. 7, respectively. FIG. 11 is a flow chart of reservation registration of a conference room, FIG. 11 is a flow chart of reservation cancellation, and FIG. 12 is a flow chart of reservation change.

This conference room reservation system, as shown in FIG. 7, has a CRT 1 and a keyboard for inputting reservation conditions (reservation date, reserved conference room, start time and end time of use of the conference room) of the conference room, and the like. 2, an IC card reader 3 for reading a user code in an IC card 4 owned by the user, a hard disk device 5 including a conference room reservation file 6 ′ and a conference room history file 8, a keyboard 2, and a 1C card reader 3
Based on the reservation conditions and user code input from, the conference room reservation file 6 ', records are added to or deleted from the conference room history file 8 to register and cancel the reservation of the conference room.
It is composed of a CPU 9'for making a reservation change and notifying the user of reservation registration, reservation cancellation, and availability of reservation change through the CRT 1.

As shown in FIG. 8, the conference room reservation file 6'changes a reservation number, a reservation date, a reserved conference room, a start time and an end time of using the conference room, and an amount of money used in the conference room. It consists of a pre-booking number. Here, the reservation number is the key, and the reservation date and the reserved conference room are the secondary keys. As shown in FIG. 9, the conference room history file 8 is composed of a reservation number, a reservation date, a reserved conference room, a start time and an end time of using the conference room, a reservation person code, and a fee. Here, the reservation number is the key.

First, the reservation registration of the conference room will be described with reference to the flowchart of FIG. The conference room code, date, and reservation code of the reservation target are input (step 41). Next, referring to the input conference room code of the reservation target and the date of the reservation target,
The secondary key indicated by is created (step 42). This 2
The next key is used for extracting reservations of the same date in one conference room. The number of extracted reservations increases as the one conference room is finely divided on the same date and used. For example, if the conference room A101 is divided into two reservations, such as a reservation from 8:00 to 12:00 and a reservation from 13:00 to 17:00 on April 4, 1991, it is extracted. The number of records is 2. Similarly, when the conference room A101 is divided into 10 and used, the number of records to be extracted is 10, and the record search time is longer than when divided into 2 and used. Next, the records are sequentially searched by the secondary key to obtain the use time (step 43). Next, the vacant time is checked from the total use time (step 44). next,
It is determined whether the input time is empty (step 45). If it is not empty, the process returns to step 41 to re-enter the conference room code and date of the reservation target. If it is empty, the reservation number is automatically collected and the conference room reservation file 6 'To add a record (step 4
6) Notify the reservation input person of the reservation number (step 4)
7).

The time indicated by phase 40 in FIG. 10 is the time from when the user inputs the reservation conditions to when the user is notified of the reservation registration. The time from the reservation condition input to the notification of reservation registration availability depends on the number of records of the same date in one conference room. Further, a method of storing history information in the conference room reservation file 6 ′ by using a flag (hereinafter referred to as a cancellation flag) indicating whether or not this reservation is valid is as follows:
It could not be used in the operation where many changes and cancellations occur, because it greatly affects the response. Therefore, only the history information is written to the conference room history file 8 which is a separate file, and the fee for canceling the reservation or changing the reservation is held.

Next, cancellation of reservation will be described with reference to the flowchart of FIG. First, the reservation number and the reservation person code are input (step 51). Next, it is calculated whether or not the reservation number can be canceled (step 52), and it is judged whether or not the reservation number can be canceled (step 53). If the cancellation is not possible, the reservation input person is notified that the cancellation is not possible (step 57). If the cancellation is possible, the reservation input person is notified that the cancellation is possible and confirmed (step 5).
4) Then, a record is added to the conference room history file 8 (step 55) and the record of the conference room reservation file 6'is deleted (step 56).

As shown in FIG. 12, the reservation change can be made as shown in FIG.
After canceling the reservation (step 61), the reservation registration shown in FIG. 10 is performed (step 62).

[0009]

The conventional conference room reservation system described above has the following drawbacks.

(1) Since there are a plurality of reservations of the same date in one conference room, it takes a long time from when the user inputs the reservation condition to when the reservation registration approval notification is received.

(2) Further, in the operation using the conference room reservation file and the conference room history file, if the data of the two files is not organized and associated and stored, the meaning of the data will be lost and the system maintainer will be burdened. Since the files are given and two files are handled, the usage fee, fee calculation, and billing become complicated.

The object of the present invention is to shorten the time from when the user inputs the reservation conditions of the conference room to when the user receives the notification of whether or not the reservation can be registered, and stores the reservation information and the conference room history information in one file. It is to provide a possible meeting room reservation method.

[0013]

The meeting room reservation method of the present invention is a vacant room management file every time a reservation is made in a time zone excluding the time secured by the reservation of the same date in one meeting room. The reservation input person is notified whether or not the entered reservation is satisfied by determining whether or not the time slot to be reserved for the reservation entered thereafter is already reserved by another reservation. The conference room reservation file stores the input information about the conference room to be used in the reservation, the information about the date and time of use, the information about the user, the billing information generated by the use, and the valid / invalid information of the reservation.

[0014]

[Operation] The time zone excluding the time secured by the reservation of the same date in one conference room is stored in the vacancy management file every time the reservation is made, and the time to reserve the reservation to be input thereafter is reserved. Since it is determined whether or not the obi has already been secured by another reservation, the time from when the user inputs the reservation condition to when the user receives the reservation registration approval / disapproval notification can be shortened as compared with the conventional case. Further, since the information of the conference room to be used in the inputted reservation, the information of the date and time of use, the information of the user, the information of the charge generated by the use, and the information of the valid / invalid of the reservation are stored in the conference room reservation file, It is no longer necessary to store the data of the conventional conference room reservation file and the conference room history file in association with each other.
The system can also be simplified for calculation of fees and billing.

[0015]

Embodiments of the present invention will now be described with reference to the drawings.

FIG. 1 is a block diagram of a conference room reservation system showing an embodiment of the present invention, and FIGS. 2 and 3 are views showing the contents of a conference room reservation file 6 and a vacant room management file 7 in FIG. 1, respectively. FIG. 4 is a flow chart of reservation registration of the conference room, FIG. 5 is a flow chart of reservation cancellation, and FIG. 6 is a flow chart of reservation change.

As shown in FIG. 1, this conference room reservation system includes a CRT 1 and a keyboard 2 for inputting reservation conditions (reservation date, reserved conference room, start time and end time of use of the conference room) of the conference room. Input from the IC card reader 3 for reading the user code in the IC card 4 owned by the user, the hard disk device 5 including the conference reservation file 6 and the vacancy management file 7, the keyboard 2, and the IC card reader 3. Based on the reservation conditions and user code, records are added to and deleted from the conference room reservation file 6 and vacancy management file 7 to make reservations, cancellations, and changes of reservations for reservations, reservations, and cancellations. , Reservation change availability CRT1
It is composed of a CPU 9 for notifying the user through.

As shown in FIG. 2, the conference room reservation file 6 includes a reservation number, a reservation date, a reserved conference room, a start time and an end time of using the conference room, a reservation person code, and use of the conference room. It is composed of the amount of money, the reservation number before change, the fee, and a cancellation flag (“1” in case of cancellation). Here, the reservation number is the key. As shown in FIG. 3, the vacancy management file 7 is composed of a reservation date, a reserved conference room, and a start time and an end time of use of the conference room. It is a mechanism that indicates the time zone reserved for the date reservation. For example,
For empty start 1, in the first record in FIG.
A value of "0" has been entered, and "080" is set for empty end 1.
The value "0" is entered. This means that in the A101 conference room, which is the key of the first record,
On the 4th of the month, there is no reservation between 0:00 and 8:00. Similarly, the meaning that the value “1200” is input to the empty start 2 and the value “1300” is input to the empty end 2 of the first record of the vacancy management file 7 is A1.
01 in the conference room on April 4, 1991 at 12:00
It indicates that there is no reservation from 1 minute to 13:00. Conversely, from these two, 1 in the A101 conference room
On April 4, 991, it indicates that there is a reservation between 8:00 and 12:00, which corresponds to the first record of the conference room reservation file 6 in FIG. Thus, in the vacant room management file 7, the reserved time of one day for one conference room is expressed in one record by having an array of vacant time as an item. As a rule, time is 0
One day is from 0:00 to 24:00, and the empty start time and empty end time are input to the vacancy management file 7 in order of earliest time. Further, n in the empty end n in FIG. 3 indicates the maximum array number. This n is the minimum time zone when the conference room is rented on a timed basis and depends on the rental time zone. For example, the minimum rental time is 1/2 hour,
If the rental time zone is from 0:00 to 24:00,
The maximum number of sections to rent is 24 hours ÷ 1/2 hours = 48 sections, and the maximum number of arrays when it is used or unused every 1/2 hour is n = 48 x 1/2 = 24. Become. Specifically, empty start 1 = 0000, empty end 1 = 00
30, empty start 2 = 0100, empty end 2 = 0130, empty start 3 = 0200, ..., Empty end 24 = 2330.

In this embodiment, the reservation of the conference room is registered using the vacant room management file 7 according to the procedure shown in FIG. First,
A reservation meeting room, a reservation date and time, and a reservation person code are input (step 11). Next, the vacant room management file 8 is searched using the reserved conference room / date and time as a key (step 12), and it is calculated whether or not the reservation time can be secured (step 13). It is judged whether or not the reservation is possible (step 13). If the reservation is impossible, the reservation conference room and the reservation date and time are input again (step 1).
1) If possible, rewrite the vacancy management file 7 (step 15), collect the reservation number, add a record to the conference room reservation file 6 (step 16), and notify the reservation input person of the reservation number through the CRT 1. Yes (Step 1
7). In addition, the calculation of whether reservation time can be secured is
Start time of conference room reservation file 6 ≧ vacancy management file 7
It is realized by searching whether or not there is an empty start x of x and an end time of the conference room reservation file 6 ≦ empty end x of the empty room management file 7 between 1 and n. If x exists, it can be secured, and if x does not exist, it cannot be secured.

The key of the vacancy management file 7 is unique in this system. Therefore, of the time shown in phase 10 of FIG. 4 (the time from when the user inputs the reservation conditions to when the user is notified of whether or not the reservation can be registered), the time for searching the vacancy management file 7 is It is logically constant regardless of the number of reservations made on the same year / month / day in one conference room in the room reservation file 6. Further, since it is a key search of the index sequential file, it is much faster than the sequential search of the secondary index of the conventional conference room reservation system.

By making the phase 10 in FIG. 4 constant, it becomes possible to retain the history by giving the cancellation flag in the conference room reservation file 6 shown in FIG.

Cancellation of a reservation in this embodiment is performed according to the procedure shown in FIG. Steps 21, 22, 23, 24, 27
Are steps 51, 52, 53 and 5 in FIG. 11, respectively.
Same as 4 and 57, after step 24, the record of the conference room reservation file 6 is searched using the reservation number as a key, and the cancellation flag, the used amount, and the fee are rewritten (step 2
5) Rewrite the vacancy management file 7 (step 2)
6).

The reservation change in this embodiment is carried out by the procedure shown in FIG. 6, and after the reservation cancellation shown in FIG. 5 (step 3).
1) The reservation registration shown in FIG. 4 is performed (step 32).

[0024]

As described above, according to the present invention, the time zone excluding the time secured by the reservation of the same date in one conference room is stored in the vacancy management file every time the reservation is made, After that, by determining whether the time slot for the reservation to be entered, which is to be reserved, is already reserved by another reservation, the time from when the user inputs the reservation conditions until when the reservation registration approval notification is received The time can be shortened as compared with the conventional one, and the conference information about the conference room used in the entered reservation, the date and time of the use, the user information, the billing information generated by the use, and the valid / invalid information of the reservation are conferenced. By storing in the room reservation file, it is no longer necessary to store the data of the conventional conference room reservation file and the meeting room history file in association with each other, and in addition, it is possible to calculate usage charges, fees, and bills. There is effect that it is possible to simplify the system even.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a conference room reservation system according to an embodiment of the present invention.

FIG. 2 is a diagram showing the contents of a conference room reservation file 6 in FIG.

FIG. 3 is a diagram showing the contents of a vacancy management file 7 in FIG.

4 is a flow chart of conference room reservation registration in the embodiment of FIG.

5 is a flow chart of reservation cancellation in the embodiment of FIG.

6 is a flow chart of reservation change in the embodiment of FIG.

FIG. 7 is a configuration diagram of a conventional conference room reservation system.

8 is a diagram showing the contents of a conference room reservation file 6'in FIG.

9 is a diagram showing the contents of a conference room history file 8 in FIG.

10 is a flow chart of conference room reservation registration in the conventional example of FIG.

11 is a flowchart of reservation cancellation in the conventional example of FIG.

12 is a flow chart of reservation change in the conventional example of FIG.

[Explanation of symbols]

 1 CRT 2 keyboard 3 IC card reader 4 IC card 5 hard disk device 6, 6'conference room reservation file 7 vacancy management file 8 conference room history file 9, 9 'CPU 11-17, 21-27, 31, 32 step 41 ~ 47,51 ~ 57,61,62 Steps 10,40 Phase

Claims (1)

[Claims] 1. A time zone excluding the time secured by the reservation of the same date in one conference room is stored in a vacancy management file every time a reservation is made, and an attempt is made to secure a reservation input thereafter. It determines whether the time zone to be reserved is already reserved by another reservation, notifies the reservation input person whether the input reservation is established, information of the conference room to be used in the input reservation, A conference room reservation method in which information on dates and times of use, user information, billing information generated by use, and valid / invalid information of reservation is stored in a conference room reservation file.