JP2010277532A - Meeting room reservation management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a meeting room reservation management system that securely and efficiently performs interruption without waiting for cancellation of reservation made by another user, and fairly provides meeting rooms even to the interrupted user. <P>SOLUTION: A client 100 is used for inputting and displaying user attribute information and meeting room attribute information required for a meeting room reservation. According to management information stored and managed in a meeting room reservation management DB 300, a schedule registration processing part 170 of a server 160 makes a reservation based on the date and hours of the meeting if conditions of attribute values of the attribute information are satisfied, stores the new user to attribute information in a waiting list if there is no available room, compares new users on the waiting list and the past users on the basis of a confidentiality level in the attribute information to update the priority of all the participants in meetings, and performs interruption 260 if the user who has the highest priority in all the new users in the waiting list has the highest confidentiality level. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a conference room reservation system that manages conference room reservations, and more particularly to a conference room reservation management system that can perform interrupts safely and efficiently based on confidentiality.

  Conventionally, as a conference room reservation system of this type, for example, when a conference room overlap reservation occurs, a user who desires the overlap reservation is registered in a cancellation waiting list, and the reservation is performed when the cancel occurs (Patent Document) 1), or the one in which the priority can be changed by updating the priorities of a plurality of reservation waiting users existing in the cancellation waiting list (see Patent Document 2).

JP 2000-40112 A JP 2004-206318 A

  Since the conference room reservation system according to Patent Document 1 is premised on waiting for cancellation as the operation of the conference room, whether or not the reservation can be made is left to the judgment of the already-reserved person. Since it is necessary to cancel the reservation in order to determine whether the user can execute the interruption, from the viewpoint of the reservation waiting user in the waiting list, the personnel (for example, employees of the management organization) are freed up. The technical method for effectively allocating to the conference room, which is a public property, is not considered.

  For this reason, assuming that an interruption by a reservation waiting user waiting for cancellation is rejected, if the reservation for the desired conference room is not established, the user information waiting in the waiting list of the conference room is wasted. In addition to continuing to wait, there is a possibility that nothing can be obtained, and there is a problem that the efficiency of the operation management of the conference room is poor.

  In addition, the reservation system according to Patent Document 2 is capable of changing the rank by updating the priority of a plurality of reservation waiting users existing in the cancellation waiting list. It is considered that the problem that the user waiting for cancellation in the case of Patent Document 1 waits wastefully for the reservation cancellation of the already reserved person is considered to be considerably improved. From the viewpoint, the confidentiality of the conference conducted by the user is not taken into consideration at all so that the purpose of selecting the conference room by the new reservation person or the purpose of allocating the conference room to the already reserved person who has been interrupted is given.

  For this reason, it is difficult to safely and efficiently perform interruptions based on confidentiality. For example, it is difficult to provide a reservation service that can sufficiently prevent information leakage due to a conference, such as being unable to provide a confidential meeting room exclusively. There is a difficulty.

  The present invention has been made to solve such problems, and its technical problem is that it is possible to safely and efficiently perform an interruption without wastefully waiting for reservation cancellation of a reserved person, It is an object of the present invention to provide a conference room reservation management system capable of providing a conference room to an already reserved person who has been interrupted without any absurdity and capable of a reservation service that can sufficiently prevent information leakage due to the conference.

  In order to achieve the above technical problem, the conference room reservation management system of the present invention includes user attribute information indicating attribute information about a user who reserves a conference room, and conference room attribute information indicating attribute information of the conference room. A schedule including an interrupt process by a new reservation user for the user for a conference room reserved by a reserved person for the user based on the user attribute information and the conference room attribute information, and a client capable of inputting and displaying A conference room reservation management system configured to be connected via a network to a server that performs reservation management of the conference room by registration processing, and the server includes a conference room including user attribute information and conference room attribute information A conference room reservation management database that stores and manages all management information required for reservation management, and a schedule that performs schedule registration processing based on the management information A schedule registration processing unit, and the schedule registration processing unit includes a meeting execution date and time zone that a new reservation person wants to schedule when the conditions match by comparing attribute values in the conference room attribute information and the user attribute information. A reservation execution function that makes a reservation based on the waiting list, and when all of the conference rooms cannot be used by a reserved person at the time of reservation, the user attribute information and meeting room attribute information about the new reservation person are stored in the waiting list. As a user by comparing the confidentiality level of a new reservation person in the waiting list with the confidentiality level of an existing reservation person based on the list storage function and the confidentiality level included in the user attribute information A priority update function that updates the priority of all participants in the meeting, and a confidentiality level for the highest priority user among new reservations in the waiting list. Based on the result of comparison with the existing reservation's sensitivity level, characterized in that and a interrupt enforcement functions to carry out the interrupt processing when the sensitivity level of the user is the highest.

  In one embodiment of the conference room reservation management system, the server is included in the management information, and processing that occurs when the user attribute information and the conference room attribute information are updated and stored in the conference room reservation management database. A storage means for temporarily saving and saving data is provided. The priority update function uses at least the conference room search condition and confidentiality level as conference room attribute information, and the confidentiality level and priority as user attribute information. And a process of determining whether or not an interrupt process can be performed on a desired object in the conference room.

  In another embodiment of the conference room reservation management system according to any one of the above, the interrupt execution function provides another conference room to a reserved person who has lost a designated one of the conference room by an interrupt process by a new reservation person. Including processing.

  In another embodiment of the conference room reservation management system according to any one of the above, the priority update function is updated by adding user attribute information indicating participation in a conference in which a priority is set by a new reservation user in the waiting list. Accordingly, the priority order is dynamically changed.

  According to still another embodiment of any one of the above conference room reservation management systems, the interrupt execution function may be used in a meeting of a new reservation person based on the importance of the document used in the meeting as the confidentiality level of the user attribute information. When the document to be handled is more important than the document to be handled at the conference of the reserved person, an interrupt process is performed for the one designated by the conference room.

  According to still another embodiment of any one of the conference room reservation management systems described above, the client includes display means for displaying the user attribute information and the conference room attribute information on the reservation screen so as to allow operation input, and the interrupt execution function is used. The interrupt processing corresponds to the specification of the scheduled start time and the scheduled end time of the conference as the user attribute information on the reservation screen of the display means, and the specification of the allowable range that allows the time zone deviation related to the required time of the conference. It is characterized by working.

  According to the conference room reservation management system of the present invention, since a new reservation person having a high confidentiality level has a function capable of interrupting a reserved person having a low confidentiality level, the reservation cancellation of the reserved person is made. Can be safely and efficiently interrupted without waiting for a long time, and can provide a conference room without any absurd reservations, and only for reservations with high confidentiality levels. Since the conference room can be provided, information leakage due to the conference can be sufficiently prevented. As a result, it is possible to efficiently allocate conference rooms to users, reduce the operation and management costs of conference rooms, and select conference rooms that take into account the confidentiality of conferences conducted by users. To prevent information leakage.

It is the block diagram which showed the basic composition of the conference room reservation management system which concerns on Example 1 of this invention. FIG. 3 illustrates a reservation screen display related to user attribute information input on a display provided on the client side provided in the conference room reservation management system shown in FIG. 1. It is the flowchart which showed the operation | movement process which concerns on the user attribute information input process part of the client with which the meeting room reservation management system shown in FIG. 1 is equipped. It is the flowchart which showed the operation | movement process which concerns on the schedule registration process part of the server with which the meeting room reservation management system shown in FIG. 1 is equipped. It is the flowchart which showed the detailed operation | movement process concerning the attribute information reception process included in the operation | movement process which concerns on the schedule registration process part shown in FIG. It is the flowchart which showed the detailed operation | movement process concerning the attribute information update process included in the attribute information reception process shown in FIG. It is the flowchart which showed the detailed operation | movement process which concerns on the user priority update process contained in the attribute information reception process shown in FIG. It is the flowchart which showed the detailed operation | movement process concerning the confidentiality level update process included in the attribute information reception process shown in FIG. It is the flowchart which showed the detailed operation | movement process which concerns on the conference room attribute comparison process contained in the operation | movement process which concerns on the schedule registration process part shown in FIG. It is the flowchart which showed the detailed operation | movement process which concerns on the user confidentiality level comparison process contained in the operation | movement process which concerns on the schedule registration process part shown in FIG. 5 is a flowchart showing detailed operation processing related to interrupt processing included in the operation processing related to the schedule registration processing section shown in FIG. 4. FIG. 4 illustrates data of an employee table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1. FIG. 3 illustrates data of a new reservation person attribute table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1. FIG. 3 illustrates data of a conference participant table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1. FIG. 3 illustrates data of a conference room attribute table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1. FIG. 4 illustrates data of a cancellation waiting table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1. FIG. 3 illustrates data of a reservation information management table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1. FIG. 3 illustrates data of an equipment table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1. FIG. 3 illustrates data of a post priority selection table constructed in a conference room reservation management DB of a server provided in the conference room reservation management system shown in FIG. 1.

  Hereinafter, an embodiment of a conference room reservation management system of the present invention will be described in detail with reference to the drawings.

  First, a technical outline of the basic functional configuration of the conference room reservation management system of the present invention will be briefly described. The conference room reservation management system of the present invention includes a client capable of operating and displaying user attribute information indicating attribute information about a user who reserves a conference room and conference room attribute information indicating attribute information of the conference room. , A server that performs conference room reservation management by schedule registration processing including interrupt processing by a new reservation user related to a user for a conference room reserved by a reserved user related to the user based on user attribute information and conference room attribute information Are connected via a network.

  Of these, the server stores a conference room reservation management database that stores and manages all management information required for conference room reservation management including user attribute information and conference room attribute information, and schedule registration processing based on the management information. A schedule registration processing unit to be performed.

  This schedule registration processing unit performs a reservation based on a meeting execution date and time zone that a new reservation person wants to schedule when a condition is matched by comparing attribute values in the meeting room attribute information and the user attribute information. Function, waiting list storage function for storing user attribute information and meeting room attribute information about a new reservation person in the waiting list when all the conference rooms cannot be used by a reserved person at the time of reservation, and user attribute information Update the priority of everyone who joins the conference as a user by comparing the confidentiality level for new reservations in the waiting list with the confidentiality level for existing reservations based on the confidentiality level contained in The priority update function and the confidentiality level of the highest priority user among the new reservation users in the waiting list are compared with the confidentiality level of the reserved user. User confidentiality level on the basis of the results and a, and interrupt enforcement functions to carry out the interrupt processing when the highest.

  In addition, the server temporarily saves and stores processing data that is included in the management information and that is generated when the user attribute information and the meeting room attribute information are updated and stored in the meeting room reservation management database. A storage means is provided.

  As for the above-described priority update function, at least the conference room search condition and the confidentiality level as the conference room attribute information, and the confidentiality level and the priority as the user attribute information are used to interrupt the target of the conference room. Including a process of determining whether or not the above can be implemented. The interrupt execution function includes a process of providing another conference room to a reserved person who has lost a designated room by an interrupt process by a new reservation person. Here, the priority order update function dynamically changes as the priority level in the waiting list is updated by adding user attribute information indicating participation in a conference set by a new reservation person. It is preferable. The interrupt execution function is used when the confidentiality level of the user attribute information is based on the importance of the document used in the meeting and the document handled in the new reservation meeting is more important than the document handled in the existing reservation meeting. It is preferable to perform an interrupt process for a designated room.

  Further, the client in this conference room reservation management system includes display means for displaying user attribute information and conference room attribute information on the reservation screen so that operation input is possible. In such a configuration, the interrupt processing by the interrupt execution function is performed by specifying the scheduled start time and the scheduled end time of the conference as the user attribute information on the reservation screen of the display means, and the time zone shift related to the required time of the conference. It is preferable to work according to the specification of the allowable tolerance.

  FIG. 1 is a block diagram showing a basic configuration of a conference room reservation management system according to Embodiment 1 of the present invention.

  The conference room reservation management system includes a client 100 including a user attribute information input processing unit 110 that inputs various data indicating attribute information about a user required for conference room reservation, and conference room reservation management. The conference room reservation management DB 300 having various tables for storing various data of management information (including user attribute information and conference room attribute information) required by the user, and the user attribute information input by the user at the client 100 are the network 150. In addition to the attribute information reception processing unit 190 that performs various update processes by receiving via, access to various tables of the conference room reservation management DB 300 according to the user attribute information, registration of the schedule required for conference room reservation management Schedule registration processing unit 170 that performs reservation management processing by performing processing, and user attribute information And the server 160 having the physical memory 270 for temporarily storing processing data when the conference room attribute information is updated and stored in the conference room reservation management DB 300 is connected via the network 150 so as to be accessible to each other. Has been configured.

  The user attribute information input processing unit 110 in the client 100 includes a known attribute information receiving process 120 for receiving the user's known attribute information requested to the server 160 via the network 150 as a flow of the input processing function, and a known by the user. It has various functions for a user input value acquisition 130 that receives input of attribute information, and a new attribute information transmission process 140 that transmits newly updated new attribute information to the server 160 via the network 150.

  Also, the schedule registration processing unit 170 in the server 160 has an attribute information transmission processing 180 for transmitting user attribute information requested from the client 100 and a client 100 implemented in the attribute information reception processing unit 190 as a schedule registration processing function. Attribute information receiving process 200 for receiving new attribute information transmitted from the user, and attribute information for all participants from the conference participant table 340 of the conference room reservation management DB 300 to obtain attribute information other than user priority and confidentiality level Attribute information update processing 210 for updating the information, and as a waiting list, update information related to the priority order of users in the waiting list for cancellation 370 created when the reservation information is registered in the reservation management information table 380 of the conference room reservation management DB 300 User priority update processing 220 and conference room reservation tube And confidentiality level update processing 230 be calculated from the conference all participants of the conference participants table 340 of DB300, has various functions for.

  Further, the schedule registration processing function in the schedule registration processing unit 170 includes a conference room attribute comparison process 240 that is a process for searching for a conference room that meets the conditions of a new reservation person, and a waiting for cancellation in the conference room reservation management DB 300. It is determined that interruption can be executed by the user confidentiality level comparison processing 250 for comparing the new reservation information waiting for reservation stored in the table 370 and the reserved user confidentiality level, and the user confidentiality level comparison processing 250. It has various functions for an interrupt process 260 that is a process for interrupting a new reservation person who has been made into a reservation of an already reserved person.

  The various tables in the conference room reservation management DB 300 include an employee table 310 that stores employee information, a new reservation user attribute table 320 that stores user information to be newly reserved, and conference participants added by the new reservation user. Conference participant table 340 for storing information, conference room attribute table 360 for storing attribute information of each conference room, and cancel wait for storing and managing a reservation person determined as a duplicate reservation in each conference room A table 370; a reservation management information table 380 for storing and managing reservation information for a user who has reserved a conference room; and facility-related information relating to conference room attribute information of new reservation users and conference participants. Management table 400, and job titles that store and manage job priority levels used when calculating user priority levels based on job titles of conference participants Sakido configured to include a selection table 410, the.

  The schedule registration processing unit 170 in the server 160 uses the conference room reservation management DB 300 in cooperation with the client 100 to wait for cancellation of a reserved person in the cancellation waiting table 370 and update priority information at that time. can do. Among the users in the cancellation waiting table 370, the user with the highest priority executes the user confidentiality level comparison process 250 using the new reservation user attribute table 320 and the reservation management information table 380 to enable or disable interruption. By determining the above, it becomes possible to implement the interrupt process 260.

  FIG. 2 illustrates a reservation screen display related to user attribute information input on a display provided on the client 100 side.

  The reservation screen 001 requests and receives the user's known information from the server 160 to display a conference room usage status as the user's known information, and to search for reservations, interrupts, and conference rooms. It is divided into a reservation information input display unit 010 for inputting necessary information.

  The usage status display unit 002 refers to the employee table 310 in the conference room reservation management DB 300 of the server 160 as user information that is known information provided from the server 160. User information includes items of user name 003, employee ID 004, title 005, organization 006, base 007, conference attendance rate 008, and busy rate 009.

  The reservation information input display unit 010 provides two access methods depending on whether the user is a new reservation person or a participant as a user, and whether the user is a new reservation person or a reservation person. In order to specify whether or not the user is a participant of the reserved conference, items of new reservation 011 and participant update 012 are provided.

  In the reservation screen 001 shown in FIG. 2, since the user has checked the check box of the new reservation 011 in the reservation information input display unit 010, the input is treated as a new reservation 011. In this case, it is required to input information in all the input fields at the bottom. The information in the new reservation person input field includes a desired conference room 013, a date 014, a start time to an end time 015, and an input field for a conference participant 016 to which a participant can be added. In the input field for the conference participant 016, All the names of the added conference participants are displayed, and the number of conference participants is also updated and displayed.

  In addition, in the case of a new reservation person, as an input field similar to the check box of the update 012 of the conference participant, a time difference that occurs when interrupting the meeting time of the already reserved person (slide of conference required time) Conference time tolerance range 017 used for adjusting (allowable time), desired equipment 018 for selecting a desired equipment required when comparing a new reservation person attribute with an existing reservation person attribute and a conference room attribute, There are input fields for the confidentiality level 019 for making a decision and the purpose of use 020 of the conference room. The information input in the input fields for these new reservation users is transmitted to the server 160 when the user clicks on the input field of the registration 021.

  The reservation screen 001 shown in FIG. 2 is an example of entry by a new reservation person, and the new reservation person designates the meeting room G as the desired meeting room 013. The information on the conference room G desired by the new reservation person is used as the location of the conference room when the reservation is made. Information input by each conference room participant is used to update attribute information of the reservation person who added the participant. Information entered in the input fields in the usage status display section 002 and the reservation information input display section 010, which are already known information on the reservation screen 001, by the reserved person is used to determine whether to reserve a new conference room, wait for cancellation, and whether or not to interrupt. used. The user attribute information in the reservation information can increase the interrupt priority by updating the user priority in the cancellation waiting table 370 of the conference room reservation management DB 300 for determining whether or not interrupt is possible. This information increases the data update frequency, and as a result, it is possible to improve the interruption frequency of the user who is waiting for the cancellation of the reserved person in the user cancellation waiting table 370. It is recommended to enter data in all fields.

  Incidentally, in the input on the reservation screen 001 used as the user interface of the client 100, when the check box of the participant update 012 is checked for use, the above-described conference time allowable range 017, desired equipment 018, confidential It is set so that only the input and selection of the sex level 019 and the purpose of use 020 can be performed, and the other input fields cannot be edited.

  In the following, referring to the reservation screen 001 in FIG. 2, as an example of determining whether or not an interruption is possible in the conference room reservation management system, a series of flows in which a new reservation person performs an interruption to a conference room of an already reserved person will be described.

  In such a case, first, the new reservation person accesses the server 160 on the conference room reservation management side via the network 150 from the client 100. The user selects a new reservation 011 on the reservation screen 001, and inputs information necessary for reservation of the conference room, update of the priority waiting for reservation, and interrupt determination. When the registration 021 is clicked after this input, the entered user attribute information is transmitted to the server 160 via the network 150. After this processing, the server 160 creates a conference participant table 340 that is a table of added conference participants including a new reservation person in the conference room reservation management DB 300. This table is an attribute table for each conference participant to connect to the server 160 and update information. Thereby, all the conference participants can update the conference participant table 340 from the display screen of the client 100. At this time, for example, notification by e-mail is performed as means for prompting all the conference participants to perform update processing.

  Each conference participant who has received the e-mail notification using this conference room reservation management system continues to update the participant attributes up to three days before the scheduled conference implementation date on the reservation screen 001 of the user interface of the client 100. To continue.

  The update by the individual conference participants here updates the reservation information that is statistically calculated from the attribute information of all the participants. Since whether or not to perform this update process is left to the conference participants, if it is not updated, the connection information in the new reservation user attribute table 320 (see the data example of the new reservation person attribute table 320 shown in FIG. 13) is used. The attribute information including the certain priority 325 and the confidentiality level 326 are not updated from the reservation execution time of the new reservation person, and the priority cannot be increased in the list of the cancellation waiting table 370 in the conference room reservation management DB 300. Therefore, there is a higher possibility that sufficient authority to execute the interruption cannot be obtained.

  Therefore, the server 160 attempts to make a reservation within a range that does not exceed the specified date 014, start time to end time 015, and specified conference time allowable range 017 based on the input information as the new reservation. Assuming that the current date and time is 2008/10/16, the date is 2008, which is 3 days before 2008/10/22, which is the scheduled date and time of conference execution set by the user of 005511 in the employee ID 321 of the new reservation person in the record 336. Since it is possible to interrupt and wait for cancellation until / 10/19, the update of the priority of the new reservation person in the cancellation waiting table 370 can be continued until 3 days before the conference. If an existing reservation person who has reserved the desired conference room 013 desired by the new reservation person can be interrupted after updating the priority 325 and comparing the confidential level 326, the existing reservation person and the new reservation person And interrupts after notifying by e-mail. In such a case, the reserved person who has been interrupted loses the conference room, so as another process for dealing with absurdity, the desired meeting reserved by other reserved persons whose confidentiality level 326 is lower than the reserved person himself / herself. In the room 013, reservation, reservation waiting, or interruption is performed at a place where conditions such as the purpose of use 020 of the conference and the start time to end time 015 indicating the time zone match.

  FIG. 3 is a flowchart showing an operation process related to the user attribute information input processing unit 110 of the client 100 provided in the conference room reservation management system.

  This operation process is performed in a state where the client 100 can transmit and receive information to and from the server 160 via the network 150.

  In the first known information reception process 120, when the user attribute information is requested from the server 160 (step S001) and the attribute information is transmitted from the server 160 (step S002), the attribute information is received from the server 160 (step S003). ) Is performed, whereby the process of displaying known information of user attributes (step S004) is performed.

  That is, in the process of requesting user attribute information from the server 160 (step S001), access to the server 160 of the conference room reservation management system is started (logged in), and user's known attribute information is requested from the server 160. . In the process of transmitting attribute information from the server 160 (step S002), the server 160 performs the attribute information transmission process 180. As this attribute information, the user's known attribute information is acquired from the employee table 310 of the conference room reservation management DB 300, and transmitted as a response to the client 100 via the network 150. In the process of receiving attribute information from the server 160 (step S003), the attribute information receiving process 120 of the client 100 receives the user's known attribute information. In the process of displaying known information of user attributes (step S004), the received known information of the user is displayed on the usage status display unit 002 of the reservation screen 001.

  Next, in the processing of the user input value acquisition 130 for acquiring information input by the user at the client 100, whether the input information is a new reservation after performing the input reception (step S005) processing, Alternatively, it is determined whether it is an update (step S006). As a result of the determination, if it is a new reservation, a process of acquiring reservation information (step S007) is performed, and if it is an update, a process of acquiring update information (step S008) is performed. After performing the process of transmitting the input new attribute information to the server 160 (step S009), the operation process is terminated.

  In other words, the input acceptance process (step S005) represents a process of accepting reservation information in which the user inputs information necessary for a new reservation person or an updater to the reservation screen 001. The reservation information entered by the user ends when the user clicks on registration 021. In the determination of whether it is a new reservation or an update (step S006), it is determined whether the new attribute information transmission process 140 is a new reservation 011 or a participant update 012. When the user selects the new reservation 011, the process proceeds to processing for acquiring reservation information (step S 007). When the user selects the participant update 012, the process proceeds to a process of acquiring update information (step S 008). In the process of acquiring the reservation information (step S007), as reservation information, known information acquired from the employee table 310 of the conference room reservation management DB 300, and an employee ID that is information as a new reservation input by the input person , Reservation ID, prospective meeting participant (name), confidential level, (meeting room) purpose of use, facilities, base, desired meeting room, date, start to end time, and allowable range of meeting time. In the process of acquiring update information (step S008), the employee ID, reservation ID, participant name, priority, confidential level, purpose of use, equipment, base, and allowable range of meeting time are acquired. Here, in particular, the priority 325, the confidentiality level 326, the purpose of use 327, the facility 328, the desired conference room 330, and the information for updating the allowable time in the new reservation person attribute table 320 (see FIG. 13) of the conference room reservation management DB 300 are displayed. A case of storing in the memory 270 can be exemplified. In the process of transmitting the new attribute information input by the user to the server 160 (step S009), the new attribute information of the new reservation person or the updater stored in the memory 270 is transmitted to the server 160.

  FIG. 4 is a flowchart showing an operation process related to the schedule registration processing unit 170 of the server 160 provided in the conference room reservation management system.

  The operation process of the schedule registration processing unit 170 is the center of the process in the conference room reservation management system. First, in response to a data transmission request from the user attribute information input processing unit 110 of the client 100, the server 160 receives, as attribute information about the user of this system, an employee table 310 in the conference room reservation management DB 300 (FIG. 12). Employee ID 311 and organization 312 of a detailed example), name 313, title 314, attendance rate 315, busy rate 316, and base 317 about the reservation person are transmitted (step S011). For example, in the data of the employee table 310 shown in FIG. 12, the case where a new reservation person corresponds to the record 318 of 00111 in the employee ID 311 can be exemplified.

  Next, the attribute information reception processing unit 190 of the server 160 performs attribute information reception processing (step S012), and updates the table information of the conference room reservation management DB 300 based on the information input by the user. The attribute information reception processing unit 190 is a process for updating information necessary for updating the priority of the waiting list in this system, whether or not an interruption can be made by updating the security level, and searching for a meeting room that matches the user condition. As the attribute information reception process 200, the attribute information update process 210, the user priority update process 220, and the confidentiality level update process 230. The details of each process associated with the attribute information reception process (step S012) will be described in detail later.

  Further, the server 160 converts the information in the new reservation person attribute table 320 (detailed example is shown in FIG. 13) and the information in the conference room attribute table 360 (detailed example is shown in FIG. 15) in the conference room reservation management DB 300. A conference room attribute comparison process 240 (step S013) is performed by performing a process of searching for a conference room based on the process. In the conference room search process, if the attribute information matches, the conference room ID 361 is stored in the memory 270 as a result, and is associated with the employee ID of the new user. This meeting room attribute comparison process (step S013) will also be described in detail later.

  Subsequently, the server 160 uses the conference room ID 361 acquired in the conference room attribute comparison process (step S013) and the start time 332 and end time 333, which are the attribute information of the new reservation person table 320, to determine the target conference room. By determining whether there is a reserved person, the process of determining whether or not the conference room is reserved (step S014) is performed. In this determination, the conference room ID 382 stored in the reservation management information table 380 (shown in detail in FIG. 17) and the conference room ID 361 acquired from the conference room attribute table 360 stored in the memory 270 are equal. The information on the reserved person is searched from the reservation management information table 380, the date 386, the start time 387, the end time 388, and the status 391 are acquired from the reservation information of the reserved person, and the reservation is made based on the status 391. If it is not confirmed, it is determined whether the time overlaps between the new user and the reserved user.

  If there is a reserved person in the time zone input by the new user in the reservation information of the reservation management information table 380, the reservation ID 381 corresponding to the reserved user is acquired, and the reservation time zone which is the next processing is obtained. The process proceeds to the process of determining whether or not the allowable range is exceeded (step S015). However, if there is no reserved person, the process proceeds to the process of considering the normal reservation and setting the value of the interrupt flag to 0 (step S016). .

  In the determination of whether or not the reservation time zone exceeds the allowable range (step S015), the reservation ID 381 acquired when there is a reserved person in the determination of whether or not the conference room has been reserved (step S014) is used. The reservation management information table 380 is accessed again, the start time 332 and end time 333 of the new user attribute table 320 are compared with the start time (387 and end time 388) of the reservation management information table 380, and the new reservation user attribute table By referring to the allowable range of the conference time from the allowable range 334, which is the information of 320, it is determined whether or not the reservation overlap can be resolved simply by shifting the conference time zone of the new reservation person by the allowable range time.

  As a result of this determination, if the reservation time zone exceeds the allowable range and the reservation cannot be made, the process proceeds to the process of storing in the waiting list (step S017), but if the reservation can be made within the allowable range. In order to make a normal reservation without interrupting, the information of the start time 332, end time 333, and allowable range 334 of the new reservation user attribute table 320 is updated by the shift of the time zone, and then the value of the interrupt flag is set to 0 (step S016). ). Note that the process of setting the value of the interrupt flag to 0 (step S016) invalidates the right of interrupt, and thereafter, the process proceeds to the interrupt process (step S022).

  In the process of storing in the waiting list (step S017), the user enters the reservation ID 371, conference room ID 372, priority 373, and interrupt flag 374 in the cancellation waiting table 370 (detailed example is shown in FIG. 16) created by the reserved person. Store information. The priority value is the lowest in the initial registration, and the value of the interrupt flag 374 is set to 0 because it is not determined whether or not an interrupt is possible.

  Thereafter, the server 160 refers to the reservation ID 322 in the new reservation user attribute table 320 for the reservation ID 371 in the cancellation waiting table 370 as a precondition for determining whether or not an interruption is possible, and acquires the confidentiality level 326 of the user. The confidentiality level 326 is compared with the confidentiality level 326 obtained in the same manner based on the reservation ID of the reserved person, and the confidentiality level 326 of the user waiting for cancellation is higher than the confidentiality level 326 of the reserved person. For example, the user confidentiality level comparison process 250 (step S018) is performed by setting the interrupt flag to 1 and enabling the interrupt. This user confidentiality level comparison process (step S018) will also be described in detail later.

  Further, the server 160 determines whether or not the conference room can be interrupted based on whether or not the value of the interrupt flag is 1 (step S019). If the result of this determination is that the interrupt flag value is 1 and an interrupt is possible, the process moves to the order of priority in the waiting list (step S020), but the interrupt flag value is 0 and no interrupt is possible. If not, the process returns to the conference room attribute comparison process (step S013).

  In the process of sorting in order of priority in the waiting list (step S020), the reservation ID 371 for each user is acquired from each item in the column in the cancellation waiting table 370, and the new reservation user attribute table 320 is obtained based on each reservation ID 371. After obtaining the priority 325 which is an item in the column of, the priority 373 of all users in the cancellation waiting table 370 is given the priority 325, and all the records 376, 377,. Are sorted in the order of users with the highest priority 373.

  In view of this, the server 160 refers to the cancellation wait table 370 and determines whether or not the priority of the new reservation holder is the highest in the waiting list (step S021). As a result of this determination, if the priority is highest, the process proceeds to the interrupt process 240 (step S022). If it is any other priority, the process returns to the conference room attribute comparison process (step S013).

  In the interrupt process (step S022), it is determined that the interrupt can be performed in the determination (step S021) of whether or not the priority of the new reservation person in the previous stage is the highest. Exit. This interrupt process (step S022) will also be described in detail later.

  FIG. 5 is a flowchart showing detailed operation processing related to the attribute information reception processing 200 included in the operation processing related to the schedule registration processing unit 170 described above.

  This attribute information reception process 200 receives user reservation information and update information from the user attribute information input processing unit 110 of the client 100 and performs processing for updating information in various tables in the conference room reservation management DB 300. Is.

  More specifically, this operation process is started after new attribute information input from the user attribute information input processing unit 110 of the client 100 is transmitted to the schedule registration processing unit 170 of the server 160 via the network 150. The attribute information reception processing unit 190 performs processing of attribute information reception (step S031) from the client 100. Here, all user input information related to the update process by the user and the participant transmitted from the client 100 is received and stored in a variable of the memory 270.

  Next, the attribute information reception processing unit 190 performs a process of determining whether the received information is a new reservation of the user or an update by the participant (step S032). As a result of this determination, if it is a new reservation person, the process proceeds to the process of updating the conference participant table for updating the information in the conference participant table 340 (step S033). The process proceeds to the determination (step S035).

  In the conference participant table update (step S033), a reservation ID 322, which is a column of the new reservation user attribute table 320, is automatically generated, and information of the number of conference participants including the new reservation user is stored in the conference participant table 340. Store the acquired information in the column. At this time, values that can be referred to from the employee table 310 based on the employee ID 311 are stored in the columns of members other than the new reservation person who are not acquired as update information, and the new reservation person attribute table 320 based on the information. Update various columns. After this, in order to prompt the process of updating the information of all participants whose reservation ID 322 of the new reservation person in the new reservation person attribute table 320 is the same as the reservation ID 342 of the meeting participant table 340, all the meeting participants are e-mailed. After executing the process of mail notification (step S034) by the above, the operation process is terminated.

  In the process of determining whether or not it is three days or more until the conference is performed (step S035), the status 391 is other than “confirmed” with reference to the reservation confirmation remaining days 392, which is a column of the reservation management information table 380. Judging. There are three status values: “empty”, “provisionally determined”, and “confirmed”. If “confirmed”, the reservation has been confirmed, and an interrupt cannot be executed. When the status is “confirmed”, the value of the number of remaining reservation confirmation days 392 in the reservation management information table 380 that stores the number of remaining days of the conference implementation date is less than 3 days, which is the reservation confirmation deadline, or the maximum confidentiality level This indicates that the reservation person who has a reservation occupies the conference room at a desired time zone without a plan to cancel, so that the conference cannot be interrupted. For this reason, if the status is “confirmed”, the operation process is terminated without performing the update, but if it is confirmed from the status 391 that the number of remaining reservation confirmation days is 3 days or more (3 days or more until the conference is performed) If so, attribute information update processing 210 for searching for meeting rooms that meet the conditions (step S036), when the reserved room cannot be reserved by the reserved person in the list of the waiting list for cancellation 370 In the user priority update process 220 (step S037) required for executing the update process of the priority column, whether or not the reserved person can be interrupted when the priority is the highest in the waiting list. After performing sequentially the confidentiality level update process 230 (step S038) necessary for determining whether or not, the operation process ends.

  FIG. 6 is a flowchart showing detailed operation processing related to the attribute information update processing 210 (step S036) described above.

  This attribute information update process 210 is one of the update processes in the attribute information reception processing unit 190, and compares the conference room requested by the user with the conference room attribute information, and searches for a conference room with matching conditions. is there.

  More specifically, the attribute information reception processing unit 190 here first accesses the conference room reservation management DB 300, the reservation ID 322 of the new reservation person attribute table 320 generated for the new reservation person, and the new reservation person. The conference participant table is created by referring to the reservation ID 342 of the conference participant table 340 assigned to all the conference participants and acquiring the employee IDs 341 of all the conference room members in ascending order. A process of referring to 340 (step S041) is performed.

  Next, the attribute information reception processing unit 190 performs a process of statistics (step S042) of the purpose of meeting use of all participants based on the acquired employee ID 341. Here, the information on the purpose of use 349 of the conference room of all the participants belonging to the new reservation person is acquired, and if there is the one with the largest duplicate value among them, it is secured as a variable in the memory 270, and other information is influential. Among the conference participants existing in the conference participant table 340, the usage purpose 327 of the new reservation user attribute table 320 is stored as a variable in the memory 270. In addition to this, the new reservation person attribute table 320 stores the desired facilities and bases of all participants and the minimum allowable meeting time as attribute information. These pieces of attribute information are used when compared with the conference room attributes.

  Further, the attribute information reception processing unit 190 performs a process of statistics (step S043) of all desired facilities of all the conference participants. Here, all the facilities desired by all the conference participants are stored in the facility 328 of the new reservation person attribute table 320. This facility 328 is equipped with facilities necessary for the desired conference room 330. Examples of the equipment 328 include a white board, a multifunction machine, a projector, a large monitor, a partition, a private room, a large screen, reception, a telephone conference, a video conference, and a video camera. Since these do not require user input, an equipment table 400 is provided in the conference room reservation management DB 300 to manage the equipment names so that the equipment names can be identified. In addition to being able to identify, equipment can be added variably as needed. Since these pieces of equipment information are information updated by the users of each conference room, all of the added equipment information is secured as variables in the memory 270 so as to be reflected in the equipment in the new reservation user attribute table 320. To keep.

  Subsequently, the attribute information reception processing unit 190 performs a process of statistics (step S044) on the optimum base from the bases of all the conference participants. Here, it is determined in which base the conference room is reserved. First, the bases 351 of all the participants are acquired from the conference participant table 340, and the base having the largest number of duplicates is stored in the memory 270 as a variable. To secure as. If the locations do not match, the location 351 of the participant with the highest post among all the conference participants in the conference participant table 340 is secured in the memory 270 as a variable. When the participant with the highest position shown in the position priority 345 overlaps and the bases 351 are different, they are sorted in ascending order by the acquisition process of the employee IDs 341 of all the meeting participants acquired in the meeting participant table 340. The participant with the highest post that overlaps in order is selected, and its base 351 is secured in the memory 270 as a variable.

  Further, the attribute information reception processing unit 190 performs a process of calculating the minimum allowable meeting time (step S045) by calculating the minimum allowable time in the conference implementation time zone. Here, in order to store in the allowable time 334 of the new user attribute table 320 using the result of adding up the allowable ranges accepted by all the participants, it is reserved as a variable in the memory 270.

  Further, the attribute information reception processing unit 190 performs a process of storing the attribute information secured as a variable in the memory 270 in the new user attribute table 320 (step S046), and then ends the operation process. Here, the purpose of use 327, the equipment 328, the recommended base 329, and the desired meeting which are the columns of the new user attribute table 320 using the variables secured in the memory 270 as attribute information in the above-described processes (steps S042 to S045). Processing to store in the chamber 330 and the allowable range 334 is performed.

  FIG. 7 is a flowchart showing detailed operation processing related to the above-described user priority update processing 220 (step S037).

  The user priority update process 220 is a process for updating the priority 325 in the new reservation user attribute table 320.

  More specifically, the attribute information reception processing unit 190 here acquires the employee IDs 341 of all the conference participants in the conference participant table 340 by using the reservation ID 322 that is a column of the new reservation person attribute table 320. By doing so, the process which refers to the meeting participant table 340 (step S051) is performed.

  Next, the attribute information reception processing unit 190 corresponds to the job priority 345 of each conference participant based on the employee ID 341 of the conference participant acquired in the process of referring to the conference participant table 340 (step S051). Information is acquired with reference to the data in the job priority selection table 410 and the average of those is calculated to calculate the job priority from the job titles of all the participants (step S052). The average values of the respective job priority rates obtained here are secured as variables in the memory 270 in order to calculate the priority 325 which is a column of the new reservation person attribute table 320.

  Further, the attribute information reception processing unit 190 acquires the conference attendance rate 346 of all the conference participants based on the employee IDs 341 of the conference participants acquired in the process of referring to the conference participant table 340 (step S051). By calculating those average values, the process of calculating the average attendance rate from the conference attendance rates of all the participants (step S053) is performed. The value of the average attendance rate obtained here is also secured as a variable in the memory 270 in order to calculate the priority 325 that is a column of the new reservation person attribute table 320.

  Subsequently, the attribute information reception processing unit 190 acquires the busy rate of all the conference participants based on the employee IDs 341 of the conference participants acquired in the process of referring to the conference participant table 340 (step S051), and acquires those busy rates. By calculating the average, the average busy rate is calculated from the busy rate of all participants (step S054). The value of the average busy rate obtained here is also secured as a variable in the memory 270 in order to calculate the priority 325 that is a column of the new reservation person attribute table 320.

  Furthermore, the attribute information reception processing unit 190 calculates the new reservation user priority from the job priority, the meeting attendance rate, and the busy rate calculated using the variables secured in the memory 270 in the above-described processes (steps S052 to S054). The calculation (step S055) is performed. Here, a value obtained by dividing the average value of the job title priority of all the conference participants, the average value of the conference attendance rate, and the average value of the busy rate by 3 is secured as a variable in the memory 270 as the value of the priority 325. Keep it.

  Further, the attribute information reception processing unit 190 stores the value obtained in the process of calculating the new reservation priority from the calculated position priority, meeting attendance rate, and busy rate (step S055) in the new user attribute table 320. After performing the process (step S056), the operation process is terminated. Here, a process of storing the calculated new reservation user priority in the priority 325 that is a column of the new reservation user attribute table 320 is performed.

  FIG. 8 is a flowchart showing detailed operation processing related to the confidentiality level update processing 240 (step S038) described above.

  The confidentiality level update process 240 represents a process in which the confidentiality level 326 of the new reservation person attribute table 320 is updated as a result of input by each conference participant.

  More specifically, the attribute information reception processing unit 190 here acquires the employee IDs 341 of all the conference participants in the conference participant table 340 by using the reservation ID 322 that is a column of the new reservation person attribute table 320. By doing so, the process which refers to the meeting participant table 340 (step S061) is performed. All the confidentiality levels 348 of all the conference participants are secured in the memory 270 based on the employee IDs 341 of the conference participants acquired here.

  Next, the attribute information reception processing unit 190 uses the variable N to grasp the position of the person having the highest confidentiality level among the participants in the meeting participant table 340 belonging to the meeting of the new reservation person. Then, the variable N is initialized to N = 0 (step S062).

  Furthermore, the attribute information reception processing unit 190 has the highest numerical value among the confidentiality levels of all conference participants having the same reservation ID 322 secured in the process of referring to the conference participant table 340 (step S061). The employee ID 341 of each participant is stored in the variable N by storing the employee ID 341 of the participant having the highest confidentiality level (1-3) of the documents used in the conference by the variable N (step S063). Process. At this time, if the participants having the highest confidentiality level (1 to 3) are duplicated, the order of arrival is the first-come-first-served basis.

  Subsequently, the attribute information reception processing unit 190 stores the employee ID 341 of the participant having the highest confidentiality level (1 to 3) of the document used by each participant in the meeting in the variable N (step S063). The process of storing the value of N indicating the highest confidentiality level among the conference participants stored in N as the confidentiality level and storing it in the confidentiality level 326 which is a column of the new reservation person attribute table 320 (step S064). After the execution, the operation process is terminated. The value of the confidentiality level 326 here is used to determine whether or not a new reservation person can execute an interruption for an existing reservation person.

  FIG. 9 is a flowchart showing detailed operation processing related to the conference room attribute comparison processing 240 included in the operation processing related to the schedule registration processing unit 170 of the server 160.

  The operation process of the conference room attribute comparison process 240 describes a comparison process for selecting a conference room that matches a condition specified in advance by a new user.

  More specifically, the schedule registration processing unit 170 refers to the data of each item in the column of the new reservation person attribute table 320, thereby performing the process of referring to the new reservation person attribute table 320 (step S071).

  Next, the schedule registration processing unit 170 uses purpose 327, equipment 328, recommended base 329, date 331, start time of the new reservation person attribute table 320 referred to in the process of referring to the new reservation person attribute table 320 (step S071). By acquiring values of 332, end time 333, and allowable range 334, a process of acquiring user attribute information (step S072) is performed.

  Further, the schedule registration processing unit 170 refers to the conference room attribute table 360 by referring to the data of each item in the column of the conference room attribute table 360 (detailed example is shown in FIG. 15) (step S073). To implement.

  Subsequently, after the process of referring to the conference room attribute table 360 (Step S073), the schedule registration processing unit 170 acquires the conference room ID 361, the number of people accommodated 363, the purpose of use 364, the equipment 365, the base 366, and the confidentiality level 367. Thus, the process of acquiring the attribute information of the conference room (step S074) is performed. The acquired attribute information of the conference room is stored in the memory 270 as a variable.

  Thereafter, the schedule registration processing unit 170 compares the values obtained in the process of acquiring the attribute information of the previous user (step S072) and the process of acquiring the attribute information of the conference room (step S074), and The process of determining whether or not the condition matches in the attribute value comparison is performed (step S075). As a result of this determination, if the conditions match, the operation process is terminated. If the conditions do not match, the process returns to the process of referring to the conference room attribute table 360 (step S073) and information on other conference rooms is obtained. By referring to information (data) of each item of a subsequent record, the conference room attribute comparison is repeated. However, if there is no information about the conference room to be compared, the conference room attribute comparison operation process is terminated.

  By the way, each item of the record that is a comparison between the attribute information of the new reservation user (user) and the attribute information of the conference room here is the purpose of use (intention to use), the number of people (capacity), the desired equipment (equipment) ), And recommended locations (locations). The value of each item of the other extracted records is used in the subsequent processing when the conditions match.

  FIG. 10 is a flowchart showing detailed operation processing related to the user confidentiality level comparison processing 250 included in the operation processing related to the schedule registration processing unit 170 of the server 160.

  The operation processing of the user confidentiality level comparison processing 250 is performed by a confidentiality level 326 that is a column of the new reservation user table 320 related to the new reservation user and a confidentiality level 390 that is a column of the reservation management information table 380 related to the reserved user. And a process of setting a flag for determining whether or not interrupt is possible. Note that the confidentiality level 326 here indicates the confidentiality of the documents that are scheduled to be used by the conference participants including the reservation person. Specifically, “confidential” is level 3 and “confidential” is the level. 2. “General” is set to level 1 and is set in 3 stages.

  Specifically, the schedule registration processing unit 170 first initializes the value of a flag used for determining whether or not an interrupt is possible to 0 (step S081). The flag value here means that 0 is not interruptible and 1 is interruptible.

  Next, the schedule registration processing unit 170 acquires the confidentiality level of the user corresponding to the reservation ID 371 that is a column of the cancellation waiting table 370 at a predetermined time from the confidentiality level 326 that is a column of the new reservation user attribute table 320. By doing so, the process of acquiring the confidentiality level 326 of the user waiting for cancellation (step S082) is performed.

  Further, the schedule registration processing unit 170 is a column of the reservation management information table 380 in which the reservation ID of the reserved person is stored, similarly to the process of acquiring the confidentiality level 326 of the previous user waiting for cancellation (step S082). From this, the value stored in the confidentiality level 390 is acquired, so that the confidentiality level 390 of the reserved person is acquired (step S083).

  Subsequently, the schedule registration processing unit 170 obtains the confidentiality level 326 of the previous user waiting for cancellation (step S082) and the confidentiality acquired in the processing of obtaining the confidentiality level 390 of the reserved user (step S083). By comparing the values of the security level and determining whether or not the confidentiality level 326 of the user attribute information owned by the new reservation person is higher than the confidentiality level 390 of the reserved person, It is determined whether or not it is higher than the user level (step S084).

  As a result of this determination, if the user level is higher than the existing user level, an interrupt is possible. Therefore, the process of setting the interrupt flag value to 1 (step S085) is performed, and then the operation process is terminated. If the user's level is not higher than the existing user level (if it is lower), an interrupt is impossible, and the operation process is terminated as it is (initially keeping the value of the interrupt flag at 0).

  As for the case where interruption is possible, for example, the case where the confidentiality level 326 is a new user of level 3 or the case where the confidentiality level 390 of the reserved person is 2 or less can be exemplified. On the other hand, as a case where interruption is possible, a case where the confidentiality level 390 of the reserved person is 3 can be exemplified.

  In the process of setting the value of the interrupt flag to 1 (step S085), 1 is stored in the value of the interrupt flag 374 that is a column of the cancellation wait table 370 that is a table for recording the availability of interrupts, and then the operation process ends. .

  Incidentally, in order for a new reservation person to perform an interruption based on the cancellation waiting table 370, the confidentiality level must be 3, but the reserved person who has been interrupted by the new reservation person exists in the cancellation waiting table 370. In addition, the confidentiality level must be 2 when performing an interrupt. Accordingly, a user in the cancellation waiting table 370 who has a confidentiality level of 1 and cannot expect an interruption cannot perform the interruption and is stored in the cancellation waiting table 370 only for waiting for cancellation. It becomes.

  FIG. 11 is a flowchart showing detailed operation processing related to the interrupt processing 260 included in the operation processing related to the schedule registration processing unit 170 of the server 160.

  The operation processing of the interrupt processing 260 is performed when an interrupt is made to a conference room where there is an existing reservation for a new reservation who can be executed when the value of the interrupt flag is 1, and when the value of the interrupt flag is 0 Two processes for making a reservation are performed.

  More specifically, the schedule registration processing unit 170 first refers to the value of the interrupt flag, determines whether or not the value of the interrupt flag is 1 (step S091), and the user (new reservation person) has already made a reservation. It is determined whether or not the person can be interrupted.

  As a result of this determination, if the interrupt flag value is not 1 (if the interrupt flag value is 0), a normal reservation that cannot be interrupted is performed [the interrupt flag value shown in FIG. Step S016) is a process that inherits the process, and it is possible to determine that the reservation made by another person is not in that time zone]. After the conference room is reserved (step S092), the operation process ends, but the interrupt If the value of the flag is 1, a process of notifying the reserved person of the execution of interruption (step S093) is performed.

  In the process of notifying the reserved person of the execution of the interruption (step S093), the new reservation person occupies the time period in order to execute the interruption in the time period reserved by the reserved person from the cancellation waiting table 370. Is notified to all the reserved persons who receive an interruption by e-mail or the like.

  Next, the schedule registration processing unit 170 loses the relationship with the reservation information of the reserved person in the conference room due to the interruption, so that the reserved person is registered as a registration process for newly allocating the conference room to the reserved person. The schedule registration flow (step S094) is executed. This schedule registration flow (step S094) is basically the same as the operation process of the schedule registration processing unit 170 shown in FIG. In the above example, the confidentiality level of the reserved person is lower than level 2. Therefore, in the comparison of the confidentiality level, unless the value of itself is level 2 and the reservation destination of the interruption destination is level 1, it is interrupted. The right to cancel the reservation is only valid.

  Further, the schedule registration processing unit 170 performs a process of overwriting the reserved person's schedule (step S095) by performing a process of replacing the conference room information deleted by the reserved person with the information of the new reservation person. Do.

  The schedule registration processing unit 170 continues to store the reservation information from the cancellation wait table 370 together with the reservation ID 381 in the reservation information management table 380 due to the execution of the interrupt. The user information is deleted from the cancellation waiting table 370 (step S096).

  In addition, the schedule registration processing unit 170 finally performs a process of notifying the new reservation person of completion of interruption by e-mail or the like (step S097), and then ends the operation process.

  According to the processing function of the schedule registration processing unit 170, as a result, a new reservation person with a high confidentiality level has a function that can execute an interruption for an existing reservation person with a low confidentiality level. Reservation can be made safely and efficiently without waiting for the user to cancel the reservation, and the conference room can be provided without any absurd reservations. Since a dedicated conference room can be provided, information leakage due to the conference can be sufficiently prevented.

  FIG. 12 illustrates data of the employee table 310 constructed in the conference room reservation management DB 300 of the server 160.

  This employee table 310 is a table used when user information is referred to by a new reservation. More specifically, the table is a table for referring to known information using the employee ID 311 as a primary key. The columns of this table include employee ID 311, organization 312, name 313, title 314, meeting attendance rate 315, The items of busy rate 316 and base 317 are arranged, and data of each of these items is stored. Of these, the position 314 is the title information, the meeting attendance rate 315 is the information (percentage) updated by calculating the monthly meeting attendance rate of each conference participant, and the busy rate 316 is the meeting from the total working hours of the month. The information (percentage) calculated from the schedule registration information executed is stored, and the base information of each employee is stored in the base 317. For example, the user of the record 318 can exemplify a case where the position 314 is a section manager, the conference attendance rate 315 is 90%, the busy rate 316 is 80%, and the base 317 is A.

  These pieces of information (data) are not only referred to as known information display on the reservation information input screen (reservation screen 001) of the client 100 in the conference room reservation management system, but also used in the columns of the cancellation waiting table 370. In order to raise the priority order 373 of a person, it is referred to every time a conference participant updates as a reference for comparison with other users.

  As an example of the update described above, on the reservation screen 001 used by the user at the client 100, the user selects the participant update 012 as the updater, and the information entered in the confidentiality level 019 in the input field is the conference participation. Stored in the confidentiality level 348 of the person table 340, this information is managed among members having the same reservation ID 322 value in the column of the new reservation person attribute table 320, and the updated information is reflected in the new reservation person attribute table 320 The process to be referred to is performed.

  FIG. 13 illustrates data of the new reservation person attribute table 320 constructed in the conference room reservation management DB 300 of the server 160.

  This new reservation person attribute table 320 is a table that manages user information used at the time of new reservation or update in an integrated manner. Various attribute information updated by the conference participants is collected and attribute information and priority are stored in this table. The confidentiality level is calculated from all participants and stored. The columns of the new reservation person attribute table 320 include employee IDs 321, reservation IDs 322, reservation persons 323, the number of participants 324, the priority 325 calculated from all new reservation persons and meeting participants, and reference when determining whether or not an interruption is possible. Used 327, equipment 328, recommended base 329, desired conference room 330, date 331, start time 332, end time 333, and allowable range 334 as attribute information used for comparison with the conference room. Are arranged, and data of each of these items is stored. These pieces of information (data) are calculated at the time of update by the attribute information reception processing unit 190 that performs update processing of the conference participant table 340, respectively.

  For example, a user of record 335 has a priority 325 of 43%, a confidentiality level 326 of level 2, a usage purpose 327 of a presentation, an equipment 328 of 1, 2, 3, 4, 10 and a recommended base 329 A of a desired meeting. The room 330 is the conference room G, the date 331 is 10/22, the start time 332 is 13:30, the end time 333 is 15:30, and the allowable range 334 is 20 min. 325 is 55%, confidentiality level 326 is level 2, purpose of use 327 is discussion between departments, equipment 328 is 1, 2, 3, 4, 8, recommended base 329 is D, desired conference room 330 is conference room C, date 331 is 10/19, start time 332 is 10:00, end time 333 is 12:00, allowable range 334 is 10 min, and the user of record 337 has a priority of 32. 37%, confidentiality level 326 is level 3, purpose of use 327 is presentation, equipment 328 is 1, 2, 3, 4, 10, recommended base 329 is A, desired conference room 330 is conference room G, date 331 is 10 / 22, the start time 332 is 13:30, the end time 333 is 14:30, and the allowable range 334 is 5 min.

  FIG. 14 illustrates data of the conference participant table 340 constructed in the conference room reservation management DB 300 of the server 160.

  The conference participant table 340 manages reservation information that can be updated by all the conference participants used when calculating update information of the new reservation user attribute table 320. Since the priority 325 of the column of the new reservation person attribute table 320 is referred to in order to increase the priority 373 in the cancellation waiting table 370, the priority of job title necessary for calculating the priority 325 is determined in the conference participant table 340. The degree 345, the meeting attendance rate 346, the busy rate 347, and the like can be updated and referred to. In the column of the new reservation person attribute table 320, in addition to the above-mentioned post priority 345, meeting attendance rate 346, busy rate 347, employee ID 341, reservation ID 342, organization 343, participant 344, confidentiality level 348, use Items of purpose 349, equipment 350, base 351, and allowable range 352 are arranged, and data of each item is stored.

  For example, regarding the users of the records 353 and 354 having the common “presentation” of the purpose of use 349 and “confidentiality” of the confidentiality level 348, the user of the record 353 is the section manager of the job priority 345 and the attendance rate 346 of the meeting is 90%, busy rate 347 has entered 80%, and the user of record 354 has chief job priority 345, meeting attendance rate 346 has entered 99%, busy rate 347 has entered 40% The case can be illustrated.

  By the way, as an example when calculating the above-described priority 325, in order to obtain the user 325 from the attribute of one person and obtain the priority 325, (post priority 345 × 70%) + (meeting attendance rate 346 / Month × 15%) + (busy rate 347 / month × 15%) may be calculated. Further, the calculation is performed for all the participants and the average value is obtained and stored as the priority 325 of the new reservation user attribute table 320. When the above-mentioned position priority 345 is obtained, 70% of the total priority is calculated from the positions of all the meeting participants. When the priority 325 of the new reservation person attribute table 320 is calculated using the post priority 345, the post 411 and the priority rate 412 in the column of the post priority selection table 410 (shown in detail in FIG. 19) are set. Use. In addition, in order to calculate the priority 325, the conference attendance rate 346 and the busy rate 347 in the column of the conference participant table 340 are used. The meeting attendance rate 346 represents the attendance rate of each employee's meeting, and is obtained from the meeting attendance rate 315 in the column of the employee table 310 for each update. The busy rate 347 is a value obtained by dividing the total meeting hours for each employee last month by the total work time, and is obtained from the busy rate 316 in the column of the employee table 310 for each update. This value is used to determine the average value of all participants, and the average value is used to calculate the priority 325. In addition, as information to be updated, there are a purpose of use 349, an equipment 350, a base 351, an allowable range 352, and a confidentiality level 348, which are attribute information.

  Of the various attribute information when the update occurs due to the registration of each conference participant, the statistical method of the purpose of use 349 will be exemplified. The attribute information of which the reservation ID 342 number of the conference participant table 340 is 000001 includes the use purpose 349 of the conference room, the desired equipment 350, the desired base 351, and the allowable range 352 of the conference time.

  First, the case where the purpose of use 349 of the conference room is calculated from the user attribute data updated for all the conference participants will be described. The member whose reservation ID 342 is 000001 is the purpose of use 349 of the meeting of all the members, and is the same as the request of the new reservation person, and all of them match, so the purpose of use 327 of the new reservation person attribute table 320 Stores “presentation”.

  Next, the case of the desired equipment 350 will be described. The user information is input to the usage status display unit 002 on the reservation screen 001 with reference to the equipment table 400 (shown in detail in FIG. 18). The conference participants whose reservation ID 342 is 000001 are all the presentations whose purpose of use 349 is presentation. Therefore, the equipment in the column of the conference participant table 340 is separated from the equipment table 400 by a comma as equipment necessary for the presentation. Stored in 350. Among these pieces of information, the facility information input by the new reservation person whose reservation ID 342 is 000001 is 1, 2, 3, 4 and the conference participant whose employee ID 341 number of the record 354 is 004321 is updated in the equipment table 400 at the time of update. It can be seen that the tenth of the equipment ID 401 is selected and the equipment 402 for video conference is added. With this addition, 1, 2, 3, 4, and 10 are input to the facility 328 of the record 335 of the new reservation user attribute table 320.

  Furthermore, the update of the conference time allowable range 352 will be described using an example. Both the new reservation person and the conference participants who are members of the new reservation person can shift the time zone of the start time and the end time of the meeting inputted by the new reservation person by a value of an allowable range. In order to shift this value greatly, it is necessary that there is room in the schedules before and after the scheduled meeting time of all conference participants. As an example of this update, the case where 13:30 is input to the start time 332, 15:30 to the end time 332, and 20 min to the allowable range 334 of the record 335 of the new reservation person attribute table 320 can be illustrated.

  FIG. 15 illustrates data of the conference room attribute table 360 constructed in the conference room reservation management DB 300 of the server 160.

  This meeting room attribute table 360 manages the attribute information of each meeting room. More specifically, the columns of this table include the conference room ID 361, the conference room name 362, the capacity 363, the purpose of use 364, the equipment 365, the base 366, and the confidentiality level 367. Is stored. Among these, for the conference room name 362, the capacity 363, the purpose of use 364, the equipment 365, the base 366, and the confidentiality level 367, the number of participants 324, the confidentiality level 326, the purpose of use in the column of the new reservation person attribute table 320 327, equipment 328, recommended base 329, and desired conference room 330, which are used for conference room search and selection processing. For example, regarding the users of the records 368 and 369 having the same purpose of use 364 and the base 366, the user of the record 368 is a meeting of the conference room name 362 in which the confidentiality level 367 is level 2 and the accommodating number 363 is eight. The room A is input, and the user of the record 369 can exemplify the case where the conference room G of the conference room name 362 in which the confidentiality level 367 is level 3 and the accommodating number 363 is 20 is input. .

  FIG. 16 shows an example of data in the cancellation waiting table 370 constructed in the conference room reservation management DB 300 of the server 160.

  The cancellation waiting table 370 is a table created by each reservation person of the reservation management information table 380 and represents registered user information waiting for reservation. For example, the user of record 377 first reserves conference room G by setting the value of priority 373 in the column of this table to 1, and the user of record 376 requests the same conference room at the same time during standby. As a result of the reservation, the results of updating the priority order 373 stored in this table are sorted in records 376 and 377. In FIG. 16, the user of the record 378 is the same as the user of the record 377, and another conference room is searched and the conference room E whose conference room ID 372 is 00005 can be reserved. In the column of this table, in addition to the above-described conference room ID 372 and priority 373, items of reservation ID 371, interrupt flag 374, and status 375 are arranged, and data of these items is stored.

  FIG. 17 shows an example of data in the reservation information management table 380 constructed in the conference room reservation management DB 300 of the server 160.

  This reservation information management table 380 is a table that stores reservation management information when a new reservation person makes a normal reservation, a reservation after waiting for cancellation, or an interrupt reservation. For example, there are a case where a desired conference room such as the desired conference room 383 and the corresponding conference room 384 in the column of this table can be reserved, and a case where another conference room is reserved by interruption or the like. The case where the reservation is finalized can be exemplified up to three days before the date and time of the conference. In such a case, setting is made so that the immediately preceding interruption cannot be made before the conference. Further, the status 391 is provisionally determined when the confidential level 390 is level 2 as in the record 393, and the status 391 is confirmed when the confidential level 390 is level 3 as in the record 394, but the confidential level 390 is level 3. However, until the reservation is completely confirmed, it is possible to search for a meeting room that meets the conditions. In the column of this table, the desired conference room 383, the corresponding conference room 384, the confidential level 390, the status 391, the reservation ID 381, the conference room ID 382, the purpose of use 385, the date 386, the start time 387, the end time 388, Items of user priority 389 and reservation confirmation remaining days 392 are arranged, and data of these items is stored.

  FIG. 18 illustrates the data of the equipment table 400 constructed in the conference room reservation management DB 300 of the server 160.

  The equipment table 400 is a table for converting the equipment list from a string to a numerical value. In the column of this table, items of equipment ID 401 and equipment 402 are arranged, and data of these items is stored. As an example of the facility 402, a white board that is first in the facility ID 401 of the record 403 can be exemplified. By using such an equipment ID 401, the name of the equipment 402 can be easily grasped correspondingly, and therefore, it is possible to reduce the input load as the reservation information of the user.

  FIG. 19 illustrates data of the post priority selection table 410 constructed in the conference room reservation management DB 300 of the server 160.

  This post priority selection table 410 is a table for displaying the difference in priority according to post in percentage. In the column of this table, items of title 411 and priority 412 are arranged, and data of these items is stored. For example, in the case of the record 413, the position 411 is the president and the priority rate 412 is 100%, and in the case of the record 414, the position 411 is an officer and the priority rate 412 is 90%. This job priority selection table 410 is a value used for referring to the desired facility selection 018 on the reservation screen 001 of the client 100. Also in the conference participant table 340, the priority 325 stored in the new reservation user attribute table 320 is stored. Used to calculate.

  As described above, in the processing function of the conference room reservation management system according to the first embodiment, when the desired conference room is not available in the desired time zone, the reservation is made as a reservation waiting in the dedicated table waiting for cancellation provided for each conference room. In addition to waiting the waiting user, an attribute table for calculating the priority of each user is used to update the priority order of the users in the waiting list. At this time, in the user table, the attribute information for calculating the priority at any time is updated by the participant, and the reservation waiting user with the highest priority when the reserved person cancels the conference room is Preferential reservations can be made. If the reservation is not possible, that is, even if cancellation is not performed by the reserved person, there is a plan to hold an important meeting compared with the reserved person so that the user waiting for cancellation does not wait in vain For reservation waiting users, it has a function that can interrupt the conference room, and on the interrupted reserved user side, search for another conference room that meets the requirements of the conference room that they want. And has a function of registering in a reservation or cancellation waiting list. Thereby, it is possible to provide a conference room without any absurdity even to an interrupted reserved person.

  In addition, this conference room reservation management system plans to implement new reservations by analyzing the information on the reservations of already booked conference rooms and the importance of the content of the new reservations who are considering interruptions. It has a function to compare the contents of the conference from the various viewpoints with the importance of the conference of the reserved person. With this function, when it is determined that the meeting of the new reservation person is important, it is possible to execute an interruption without being caught by the determination of the existing reservation person. In addition, it is possible to guide an alternative conference room to a reserved person who has been interrupted. As a result, the meeting room according to the confidentiality of the meeting that is held without considering the important meeting that the new reservation person wants, and the reserved person who is planning to hold the unimportant meeting in consideration of information leakage. Because it is possible to make reservations, it is possible to implement both security improvements and reductions in conference room operating costs.

DESCRIPTION OF SYMBOLS 100 Client 110 User attribute information input process part 120 Attribute information reception 130 User input value acquisition 140 New attribute information transmission 150 Network 160 Server 170 Schedule registration process part 180 Attribute information transmission 190 Attribute information reception process part 200 Attribute information reception process 210 Attribute information update process 220 User priority update process 230 Security level update process 240 Conference room attribute comparison process 250 User confidentiality level comparison process 260 Interrupt process 270 Memory 300 Conference room reservation management DB
310 Employee Table 320 New Reservation Attribute Table 340 Conference Participant Table 360 Conference Room Attribute Table 370 Cancellation Waiting Table 380 Reservation Management Information Table 400 Equipment Table 410 Post Priority Selection Table

Claims (6)

User attribute information indicating attribute information about a user who reserves a conference room, a client capable of inputting and displaying conference room attribute information indicating attribute information of the conference room, the user attribute information, and the conference A server that performs reservation management of the conference room by schedule registration processing including interruption processing by a new reservation person related to the user with respect to the conference room reserved by the reserved person related to the user based on the room attribute information. A conference room reservation management system configured to be connected via
The server includes a conference room reservation management database for accumulating and managing all management information required for reservation management of the conference room including the user attribute information and the conference room attribute information, and the schedule based on the management information. A schedule registration processing unit for performing registration processing,
The schedule registration processing unit makes a reservation based on a meeting execution date and time zone that the new reservation person wants to schedule when a condition is matched by comparing attribute values in the meeting room attribute information and the user attribute information. A reservation execution function, and a waiting for storing the user attribute information and the conference room attribute information for the new reservation user in a waiting list when all of the conference rooms cannot be used by the reserved user when the reservation is performed. Comparing the confidentiality level of the new reservation person in the waiting list with the confidentiality level of the reserved person based on the list storage function and the confidentiality level included in the user attribute information The priority update function for updating the priority of all the users who participate in the conference as the user, and the new reservation person in the waiting list is the best. Interrupt execution for executing the interrupt process when the confidentiality level of the user is the highest based on a result of comparing the confidentiality level of the user with a higher rank with the confidentiality level of the reserved user And a conference room reservation management system.   2. The conference room reservation management system according to claim 1, wherein the server is stored in the conference room reservation management database so that the user attribute information and the conference room attribute information can be updated while being included in the management information. Storage means for temporarily saving and storing processing data generated when the process is performed, and the priority order update function includes at least the conference room search condition and confidentiality level as the conference room attribute information, and the user attribute information A conference room reservation management system comprising: determining whether the interrupt process can be performed on a desired target of the conference room using the confidentiality level and priority.   3. The conference room reservation management system according to claim 1, wherein the interrupt execution function is configured to provide another conference room for the reserved person who has lost the designated room by the interrupt process by the new reservation person. A conference room reservation management system comprising a process for providing a conference room.   4. The conference room reservation management system according to claim 2, wherein the priority update function adds the user attribute information indicating participation in a conference in which the priority is set by the new reservation user in the waiting list. The conference room reservation management system, wherein the priority order is dynamically changed as it is updated by the above.   The conference room reservation management system according to any one of claims 1 to 4, wherein the interrupt execution function is based on the importance level of documents used in a meeting as the confidentiality level of the user attribute information. A conference room reservation management system, wherein the interruption processing is performed for a designated document of the conference room when the document handled in the conference of the reservation person is more important than the document handled in the conference of the reserved person. .   The conference room reservation management system according to any one of claims 1 to 5, wherein the client includes display means for displaying the user attribute information and the conference room attribute information so that an operation can be input on a reservation screen. The interrupt processing by the interrupt execution function includes, as the user attribute information on the reservation screen of the display means, designation of a scheduled start time and a scheduled end time of a conference, and a time zone shift related to the required time of the conference. A conference room reservation management system characterized by working according to the specification of an allowable range.

Images