Schedule adjustment system and schedule adjustment method

Abstract

To easily accept a reservation from one or more people for one meeting schedule while preventing double-booking by using an existing schedule pre-registered in a schedule as a candidate schedule.SOLUTION: A schedule adjustment device includes an adjustment condition setting part for setting an adjustment condition template, and a schedule adjustment part for adjusting a meeting schedule based on the adjustment condition template. The adjustment condition setting part registers, in the adjustment condition template, adjustment conditions using an existing schedule specified by an adjustment initiator as a reservation frame and including specification of the reservation frame, out of existing schedules registered in schedule information managed by an external system. When an adjustment partner accesses thereto, the schedule adjustment part defines, uses, out of reservation frames, the reservation frame satisfying the adjustment conditions as a candidate schedule, displays a schedule selection screen representing the candidate schedule on a terminal device used by the adjustment partner, and determines a meeting schedule in the candidate schedule according to a selection operation of the adjustment partner on the schedule selection screen.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a schedule adjustment device, a schedule adjustment method, and a program.

Background Art

[0002] Conventionally, scheduling meetings in business is a very cumbersome and time-consuming task because there are many procedures such as checking the schedules of each participant and securing a venue.

[0003] Regarding checking the schedules of participants, recently, many business people manage their schedules using calendar tools provided on the Internet, so it is conceivable to refer to such calendar tools.

[0004] Related to calendar tools, for example, Patent Document 1 describes "a member of a system for distributing and sharing schedule information via the Internet, a plurality of applicants who apply for distribution of schedule information, and a plurality of users who use the distributed schedule information, each performing a step of registering for membership, a step executed by a scheduler for schedule management, which includes a step of publicly distributing the schedule information to the users by the applicant, a step of registering a target for which the user desires distribution of the publicly distributed schedule information, and a step of synchronizing and presetting the related schedule information to the calendars of all user terminals based on the registered desired distribution targets of the users."

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] The technology described in Patent Document 1 allows multiple users who are members of the system to share schedule information with each other, and can therefore be used to schedule meetings. However, even when using this system, the schedules of participants in meetings and other events can be updated and changed moment by moment. Furthermore, if the meeting participants include non-members of the system, it is necessary to check the schedules of these non-members individually, making it difficult to schedule the meeting without overlapping each participant's existing schedule with the meeting date, i.e., without double-booking.

[0007] Furthermore, when companies hold company information sessions or seminars, organizers often reserve the dates for these sessions in advance by registering the schedules of their participants and the venues used for the sessions. In such cases, treating reservations for company information sessions as scheduling meetings and presenting the pre-registered schedules as potential dates to prospective participants allows them to reserve their participation, which is highly convenient for both organizers and prospective participants.

[0008] Furthermore, since it is common practice to recruit multiple participants for a single event date at company information sessions and similar events, it is desirable to be able to accept reservations from multiple people for a single event date. However, there is no system in place to use existing scheduled events pre-registered in the schedule information as potential meeting dates.

[0009] This invention was made in consideration of the current situation, and aims to prevent double bookings by the organizer by allowing them to register meeting schedules in advance in the organizer's schedule information, and further, to facilitate scheduling of meetings such as company briefings by allowing existing pre-registered schedules to be used as candidate dates and accepting reservations from one or more people for a single meeting date. [Means for solving the problem]

[0010] This application includes several means to solve at least some of the above problems, and some examples are as follows.

[0011] To solve the above problems, a scheduling device according to one aspect of the present invention comprises: a scheduling condition setting unit that sets up scheduling condition templates that can be repeatedly used for scheduling different meetings; and a scheduling unit that adjusts meeting dates based on the scheduling condition templates. The scheduling condition setting unit sets up existing appointments designated by the scheduling initiator as reservation slots from among existing appointments registered in schedule information managed by an external system, and registers the scheduling conditions, including the designation of the reservation slots, in the scheduling condition templates. When a scheduling partner accesses the scheduling device based on access information corresponding to the scheduling condition templates, the scheduling unit sets up reservation slots that satisfy the scheduling conditions as candidate dates, displays a date selection screen representing the candidate dates on the terminal device used by the scheduling partner, and determines the meeting date from among the candidate dates in response to the scheduling partner's selection operation on the date selection screen.

[0012] The adjustment condition setting unit sets the schedule information specified by the adjustment initiator, which is managed by the external system, as the search target schedule information, searches for existing appointments registered in the search target schedule information that satisfy the search conditions set by the adjustment initiator, and selects an existing appointment from the search results as the reservation slot.

[0013] The person initiating the adjustment can perform the process of setting the search conditions and the process of selecting the reservation slot from the existing schedule as the search results at least once for the same adjustment condition template.

[0014] The adjustment condition setting unit can search for existing appointments registered in the search target schedule information, where the search keyword used as the search condition is included in the information about the existing appointments.

[0015] The adjustment condition setting unit can search for existing appointments registered in the search target schedule information that fall within the search period used as the search condition.

[0016] The adjustment condition setting unit may use the schedule information of members belonging to the same organization as the adjustment initiator, or the schedule information of venues available to those members, as the search target schedule information.

[0017] The adjustment condition setting unit can set an extraction period as the adjustment condition, and the scheduling unit can, when the other party accesses based on the access information, select the reservation slots within the extraction period starting from the time the other party accessed as the candidate dates.

[0018] The adjustment condition setting unit can set a maximum number of reservations as an adjustment condition, and the scheduling unit can, when a scheduling partner accesses based on the access information, select a reservation slot from among the reservation slots in which the number of reservations made by the scheduling partner is less than the maximum number of reservations as the candidate date.

[0019] The scheduling unit can add information about the person to be scheduled to meet to the existing schedule registered in the schedule information managed by the external system, which corresponds to the decided meeting date.

[0020] The scheduling unit can notify the other party of the decided meeting date, information regarding the web conference designated by the scheduling initiator for the scheduling template or the reservation slot, or information regarding the venue.

[0021] Another aspect of the present invention relates to a scheduling method which includes setting scheduling conditions, setting scheduling condition templates that can be repeatedly used for scheduling different meetings, and scheduling a meeting based on the scheduling condition templates. The setting scheduling conditions include setting existing appointments designated by the scheduling initiator as reservation slots from among existing appointments registered in schedule information managed by an external system, registering scheduling conditions including the designation of the reservation slots in the scheduling condition templates, and when a scheduling partner accesses the scheduling condition templates based on access information corresponding to the scheduling condition templates, the scheduling step includes selecting reservation slots that satisfy the scheduling conditions as candidate dates, displaying a date selection screen representing the candidate dates on a terminal device used by the scheduling partner, and determining the meeting date from the candidate dates in response to the scheduling partner's selection operation on the date selection screen.

[0022] A program according to yet another aspect of the present invention causes a computer to function as an adjustment condition setting unit that sets up adjustment condition templates that can be repeatedly used for scheduling different meetings, and a scheduling unit that adjusts meeting dates based on the adjustment condition templates, wherein the adjustment condition setting unit sets up existing appointments designated by the scheduling initiator from among existing appointments registered in schedule information managed by an external system as reservation slots, and registers adjustment conditions including the designation of the reservation slots in the adjustment condition template, and when a scheduling partner accesses the adjustment condition template based on access information corresponding to the adjustment condition template, the scheduling unit sets up reservation slots that satisfy the adjustment conditions as candidate dates, displays a date selection screen showing the candidate dates on a terminal device used by the scheduling partner, and determines the meeting date from among the candidate dates in response to the scheduling partner's selection operation on the date selection screen. [Effects of the Invention]

[0023] According to the present invention, double bookings can be prevented by using existing appointments pre-registered in the schedule as candidate dates, and furthermore, reservations from one or more people can be easily accepted for a single meeting date.

[0024] Problems, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

Brief Description of the Drawings

[0025] [Figure 1] FIG. 1 is a diagram showing a configuration example of a schedule adjustment system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram showing an example of each of member information, user information, adjustment condition template information, and schedule adjustment information. [Figure 3] FIG. 3 is a sequence diagram illustrating an example of processing at the time of use registration. [Figure 4] FIG. 4 is a sequence diagram illustrating an example of adjustment condition template creation processing. [Figure 5] FIG. 5 is a diagram showing a display example of an adjustment condition template list screen. [Figure 6] FIG. 6 is a diagram showing a display example of a template management information input screen. [[ID=2�]] [Figure 7] FIG. 7 is a diagram showing a display example of a meeting type selection screen. [Figure 8] FIG. 8 is a diagram showing a display example of a reservation frame list screen. [Figure 9] FIG. 9 is a diagram showing another display example of a reservation frame list screen. [Figure 10] FIG. 10 is a diagram showing a display example of a reservation frame addition screen. [Figure 11] FIG. 11 is a diagram showing a display example of a reservation frame list screen. [Figure 12] FIG. 12 is a diagram showing a display example of a reservation reception setting screen. [Figure 13] FIG. 13 is a sequence diagram illustrating an example of schedule adjustment processing. [Figure 14] FIG. 14 is a diagram showing a display example of an adjustment condition template list screen. [Figure 15] FIG. 15 is a diagram showing a display example of a comment confirmation screen. [Figure 16] FIG. 16 is a diagram showing a display example of a schedule selection screen. [Figure 17]Figure 17 shows an example of the schedule confirmation screen. [Figure 18] Figure 18 shows an example of the display of the reservation information input screen. [Figure 19] Figure 19 shows an example of the display of the schedule notification screen. [Modes for carrying out the invention]

[0026] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In all drawings used to describe an embodiment, the same reference numerals will be used for identical components, and repeated descriptions will be omitted. Furthermore, in the following embodiment, it goes without saying that the components (including element steps, etc.) are not necessarily essential unless otherwise explicitly stated, or unless they are clearly essential in principle. Also, when we say "consisting of A," "made of A," "having A," or "including A," it goes without saying that other elements are not excluded unless otherwise explicitly stated. Similarly, in the following embodiment, when referring to the shape, positional relationship, etc. of components, etc., it will include those that are substantially similar or approximate to their shape, etc., unless otherwise explicitly stated, or unless otherwise clearly stated in principle.

[0027] <Schedule adjustment system 10 for a newly acquired population> Figure 1 shows an example configuration of a scheduling system 10 according to one embodiment of the present invention.

[0028] The scheduling system 10 includes a scheduling device 20 connected via a network 11, an external system 30, and terminal devices 40A, 40M, and 40X.

[0029] Network 11 is a two-way communication network, such as the Internet or a mobile phone network.

[0030] The scheduling device 20 treats, for example, company information sessions and seminars that require reservations as meetings, and supports the reservation acceptance by the organizer and the reservation application by prospective participants for such meetings. Hereinafter, prospective participants who apply to reserve a spot at a meeting will be referred to as "scheduling partners." Although Figure 1 only shows scheduling partner X as an example, there can be multiple scheduling partners. Participants on the organizer's side of a company information session, etc., are assumed to include scheduling initiator A, and members B, C, D, etc. (including member administrator M (details below)) of the organization (company, etc.; corporate member described later) to which scheduling initiator A belongs. In this specification, "participants" of a meeting are defined as participants on the organizer's side among those who actually attend the meeting, and unless explicitly stated, scheduling partner X who attends the meeting is not included in "participants" (and is not referred to as "participant").

[0031] External system 30 refers to a system that widely provides a calendar tool 31 as a web application to general consumers and corporations, either for a fee or free of charge. Examples of calendar tools 31 include Google Calendar (trademark) and Microsoft Outlook (trademark). The calendar tool 31 maintains schedule information 311, which contains the planned activities of its users and the reservation status of meeting venues available to them. In other words, external system 30 manages the schedule information 311, which contains the planned activities of its users and the reservation status of meeting venues available to them.

[0032] The terminal device 40A used by scheduling initiator A consists of a general-purpose computer such as a personal computer or smartphone that can connect to the scheduling device 20 via the network 11. Similarly, the terminal device 40M used by member administrator M and the terminal device 40X used by scheduling partner X consist of general-purpose computers.

[0033] In this embodiment, the coordinating party X participating in the meeting operates the terminal device 40X, but in reality, the coordinating party X's agent (such as a secretary) may operate the terminal device 40X.

[0034] The scheduling initiator A is an employee of a company or other organization that has completed member registration and user registration (registration of information necessary to enable the use of the scheduling function in the scheduling device 20) with the scheduling device 20. Hereinafter, companies or other organizations that have completed member registration with the scheduling device 20 will be referred to as corporate members. Furthermore, among the employees belonging to corporate members (companies, etc.), those employees who have a user account for the scheduling device 20 will be defined as users. It is essential that scheduling initiator A is a user. Therefore, hereafter, scheduling initiator A may be referred to as user A. Note that users can also register for the scheduling device 20, not just companies or other organizations. In that case, the individual who has completed user registration will be referred to as an individual member. Individual members and users can be considered the same.

[0035] Member administrator M is a member of the same corporate member organization as coordinator A, and manages the member account as a corporate member. Coordinator A and member administrator M may be different people or the same person.

[0036] Member administrator M and other members belonging to the same corporate member as coordinator A (B, C, D, etc.) may be users, but this is not required.

[0037] Members of the corporate member of the scheduling device 20 manage their own schedules using the calendar tool 31 provided by the external system 30. In addition, corporate members of the scheduling device 20 manage the reservation status of meeting rooms, reception rooms, spare rooms, etc. that their members can use as meeting venues using the calendar tool 31 provided by the external system 30.

[0038] Therefore, in this case, the calendar tool 31 holds schedule information 311 which contains the schedules of coordinators A and others who may be participants on the organizing side of the meeting, and the reservation status of meeting venues available to coordinators A and others.

[0039] Specifically, the organizer of the meeting will register multiple dates that could be used as reservation slots for company information sessions, etc., in advance as scheduled events in the schedule information 311 of the organizer's participants and venue (conference room, etc.). As a result, the schedule information 311 of the organizer's participants and venue will retain existing scheduled events that could be used as reservation slots for company information sessions, etc. Furthermore, since the dates of the organizer's participants and venue related to company information sessions, etc. will be reserved in advance in the schedule information 311, double bookings will be prevented.

[0040] Note that the scheduling partner X may be a user of the scheduling device 20, but this is not required. Also, the scheduling partner X may use the calendar tool 31, but this is not required. Furthermore, the scheduling partner X may use a calendar tool provided by a different vendor than the calendar tool 31 used by scheduling initiator A.

[0041] The scheduling device 20 comprises functional blocks: a processing unit 21, a storage unit 22, and a communication unit 23. The scheduling device 20 consists of a general computer such as a server computer equipped with a processor such as a CPU (Central Processing Unit), memory such as DRAM (Dynamic Random Access Memory), storage such as an HDD (Hard Disk Drive) or SSD (Solid State Drive), input devices such as a keyboard, mouse, and touch panel, output devices such as a display, and a communication module such as a NIC (Network Interface Card) (all not shown).

[0042] The processing unit 21 is implemented by the computer's processor. The processing unit 21 has the following functional blocks: an authentication unit 211, an adjustment condition setting unit 212, and a scheduling unit 213. These functional blocks are implemented by the computer's processor executing a predetermined program loaded into memory. However, some or all of these functional blocks may be implemented as hardware using integrated circuits or the like.

[0043] The authentication unit 211 accepts member registration from, for example, member administrator M using terminal device 40M and creates member information 221. The authentication unit 211 also responds to the user's first login from, for example, adjustment initiator A using terminal device 40A, and creates user information 222 if predetermined conditions are met.

[0044] Furthermore, the authentication unit 211 accesses the external system 30 via the network 11 and performs authentication processing using, for example, the administrator privilege account included in the member information 221 held by the storage unit 22 and the user account included in the user information 222 corresponding to the adjustment initiator A (user A) (both in Figure 2), in accordance with a protocol such as OAuth. However, the administrator privilege account and user account only need to be used for the first authentication process; for subsequent authentication processes, the administrator authentication information (access token, etc.) and user authentication information (access token, etc.) (both in Figure 2) sent from the external system 30 when the first authentication process is completed can be used.

[0045] The adjustment condition setting unit 212 displays a series of adjustment condition template creation screens (Figures 6 to 12) on the terminal device 40A for creating an adjustment condition template consisting of multiple items necessary for scheduling a meeting (hereinafter referred to as the adjustment condition template), and creates the adjustment condition template in response to input from the adjustment initiator A to the adjustment condition template creation screen. The adjustment condition setting unit 212 then stores the created adjustment condition template in the storage unit 22 as adjustment condition template information 223 associated with user information 222 corresponding to the adjustment initiator A.

[0046] Specifically, the adjustment condition setting unit 212 refers to the schedule information to be searched (schedule information 311 of participants or venues on the organizer's side of the meeting) specified by the adjustment initiator A, and searches for existing appointments that meet the search conditions set by the adjustment initiator A (for example, search period, search keywords, etc.). Then, the adjustment condition setting unit 212 registers the existing appointments selected by the adjustment initiator A from the searched existing appointments as meeting reservation slots in the adjustment condition template information 223. Details of the adjustment condition template information 223 will be described later.

[0047] When the scheduling partner X uses terminal device 40X to access the reservation acceptance URL (Uniform Resource Locator) set by scheduling initiator A for accessing a series of reservation acceptance screens (Figures 15-18) for making reservations to participate in a meeting, the scheduling unit 213 refers to the schedule information 311 managed by the external system 30 at that time and extracts as candidate dates reservation slots that still exist as existing appointments that have not been changed since scheduling initiator A designated them as reservation slots, and that also satisfy the scheduling conditions (extraction period, maximum number of reservations, etc.). The scheduling unit 213 then displays a date selection screen as a reservation acceptance screen representing the candidate dates on terminal device 40X. The reservation acceptance URL corresponds to the access information of the present invention.

[0048] Furthermore, when the scheduling unit 213 selects and confirms a meeting date from the candidate dates displayed on the date selection screen, it creates scheduling information 224, associates it with the scheduling initiator A, stores it in the storage unit 22, and registers information about the scheduling partner X. In addition, the scheduling unit 213 adds the name of the scheduling partner X to the remarks column of the existing schedule corresponding to the meeting date (reservation slot) confirmed by the scheduling partner X in the schedule information 311 managed by the external system 30.

[0049] Furthermore, even in the short time between when the scheduling partner X selects a candidate date displayed on the date selection screen and confirms it as the meeting date, it is possible that, for example, the number of reservations for the selected candidate date (reservation slot) may reach the maximum number of reservations. Therefore, the scheduling unit 213 makes a final check just before the scheduling partner X confirms the meeting date that the number of reservations for the selected candidate date (reservation slot) is less than the maximum number of reservations. If the number of reservations for the selected candidate date (reservation slot) has reached the maximum number of reservations, the unit 213 should display a message on the terminal device 40X such as "The selected date is full. Please select a date again," and return the user to the date selection screen. This prevents reservations from exceeding the maximum number of reservations.

[0050] The memory unit 22 is implemented using the computer's memory and storage. The memory unit 22 holds member information 221, user information 222, adjustment condition template information 223, and scheduling information 224. In addition, the memory unit 22 may store information and data other than the above-mentioned information.

[0051] The communication unit 23 is implemented by a computer communication module. The communication unit 23 communicates various data and information by connecting to external systems 30, terminal devices 40A, 40M, 40X, etc. via the network 11.

[0052] Furthermore, some or all of the functional blocks that constitute the scheduling device 20 may be implemented by hardware such as integrated circuits. In addition, the scheduling device 20 may be implemented by multiple computers, in which case the functional blocks described above may be distributed among the multiple computers.

[0053] Next, Figure 2 shows an example of member information 221, user information 222, adjustment condition template information 223, and schedule adjustment information (confirmed information) 224 that are stored in the memory unit 22.

[0054] Member information 221 consists of information about corporate members who have completed member registration with the scheduling device 20. In addition, member information 221 includes information about corporate members that is added when a corporate member registers to use the scheduling device 20. Specifically, member information 221 includes member account, administrator privilege account, administrator authentication information, basic information, affiliation information, and venue information.

[0055] The member account is information used by the member administrator M of a corporate member (company, etc.) to log in to the scheduling device 20. The administrator privilege account is information used by the member administrator M of a corporate member (company, etc.) to access the external system 30 with administrator privileges. It is desirable that the member account and the administrator privilege account (for example, the email address of member administrator M, etc.) be the same, but they may be different. If the member account and the administrator privilege account are the same, registration of the administrator privilege account for the member information 221 can be omitted.

[0056] Administrator authentication information is an access token, etc., obtained from the external system 30 as a result of the successful authentication process when the authentication unit 211 of the scheduling device 20 performs the authentication process to the external system 30 for the first time using an administrator privilege account. After obtaining administrator authentication information, the authentication unit 211 can perform the authentication process to the external system 30 more quickly using the administrator authentication information without having to use an administrator privilege account.

[0057] Basic information includes the name of the corporate member (company name, etc.). This basic information is recorded during member registration and can be changed after registration. Affiliation information is a list of names of employees belonging to the corporate member company, etc., and user accounts, etc., that these employees use to access the external system 30. Affiliation information is obtained and recorded from the external system 30, assuming that employees of the corporate member who may be participants on the organizing side of the meeting are already using the calendar tool 31.

[0058] The venue information is a list of names of meeting rooms, reception rooms, spare rooms, etc., that can be used by members of the corporate member for meetings, as well as venue identification IDs in external systems. The venue information is obtained and recorded from the external system 30, assuming that the schedules of all venues necessary for scheduling are already managed by the calendar tool 31.

[0059] Furthermore, affiliation information and venue information can only be obtained from the external system 30, in whole or in part, when accessing the external system 30 with an administrator account. For example, if an account without administrator privileges is used instead of an administrator account, or if an account with equivalent privileges to an administrator account accesses the external system 30 as a user account, the information cannot be obtained (however, depending on the type of external system 30, some of the information may be obtainable).

[0060] User information 222 consists of information about users who belong to a corporate member and have completed registration to use the scheduling device 20. User information 222 is created when each user logs into the scheduling device 20 for the first time, successfully completes the authentication process with the external system 30, and is confirmed to be included in the member information 221. User information 222 is then associated with member information 221.

[0061] User information 222 includes user account, user authentication information, and basic user information.

[0062] A user account is information used by a user, such as scheduling initiator A, to log in to the scheduling device 20. It is desirable that the user account be the same as the account used by the user to access the external system 30, but it may be different. The following explanation assumes that the user account is the same as the account used to access the external system 30.

[0063] User authentication information is the access token, etc., obtained from the external system 30 as a result of the successful authentication process when the authentication unit 211 first performs authentication processing on the external system 30 using the user account. After obtaining user authentication information, the authentication unit 211 can perform authentication processing on the external system 30 more quickly using the user authentication information without using the user account.

[0064] User basic information includes the user's name, etc., and is read and recorded from the affiliation information in member information 221 based on the user account used when the user first logs in to the scheduling device 20. User basic information recorded in user information 222 may be made editable by the user themselves.

[0065] The adjustment condition template information 223 is created in association with the user information 222. The adjustment condition template information 223 includes a template ID to uniquely identify any multiple adjustment condition template information 223s, a list of reservation slots (such as the schedule ID of existing appointments and the date and time of the reservation slots), adjustment conditions specified in advance by the user according to the purpose of the meeting (such as the extraction period and the maximum number of reservations), a URL for accepting reservations, and screen display information (such as the title of the reservation acceptance screen, comments, and the web conference URL).

[0066] Since the adjustment condition template information 223 is created by the user, it is associated with the user information 222. However, for example, the adjustment condition template information 223 may be associated with the member information 221, allowing users belonging to the corporate member corresponding to the member information 221 to share the adjustment condition template information 223. Alternatively, an adjustment condition template created by one user may be made available for use by other users.

[0067] The scheduling information 224 is created for each booking made by the scheduling partner X when X completes a booking for a meeting, and is associated with the user information 222 and scheduling condition template information 223 corresponding to each user. Note that, considering that a user other than the one who created the scheduling condition template may use the template to schedule a meeting, the scheduling information 224 may also be directly associated with the member information 221 of the corporate member to which the user belongs.

[0068] The scheduling information 224 records the template ID, reservation acceptance URL, existing schedule ID, confirmed meeting date and time, location or meeting method (Web conference URL, etc.), information of the scheduling partner X (name, email address, etc.), and comments from both scheduling initiator A and scheduling partner X.

[0069] <Processing during user registration by the scheduling system 10> Next, Figure 3 is a sequence diagram illustrating an example of the processing performed when a user registers using the scheduling system 10.

[0070] As a prerequisite, it is assumed that the calendar tool 31 provided by the external system 30 is used for managing the schedules of members of the corporate member to which the scheduling initiator A and member administrator M belong, as well as for managing the schedules of venues that these members can use for meetings. Furthermore, it is assumed that the external system 30 already manages the member information and venue information recorded in the member information 221. The external system 30 is specified to supply at least one of the member information and venue information recorded in the member information 221 to the scheduling device 20 in response to a request from the scheduling device 20 accessed using an administrator privilege account (or administrator authentication information).

[0071] First, when member administrator M uses terminal device 40M to apply for member registration to scheduling device 20 via network 11 (step S1), the authentication unit 211 of scheduling device 20 creates member information 221 and records it in storage unit 22 (step S11). However, the member information 221 created here only includes the member account and basic information, and does not include administrator privilege account, administrator authentication information, affiliation information, or venue information.

[0072] Next, when member administrator M enters an administrator privilege account for the external system 30 and requests authentication processing from the scheduling device 20 (step S2), the authentication unit 211 then uses the administrator privilege account to perform authentication processing on the external system 30 (step S12).

[0073] As a variation, steps S1 and S11 may be executed after steps S2 and S12.

[0074] Then, as a result of the successful authentication process in step S12, administrator authentication information (such as an access token) is sent from the external system 30 to the scheduling device 20. Next, the authentication unit 211 registers the administrator privilege account and administrator authentication information in the member information 221 created and recorded in step S11 (step S13). For example, OAuth can be used for the authentication process, and by having member administrator M enter a password to the external system 30 without going through the authentication unit 211, the administrator privilege account entered by member administrator M is authenticated by the external system 30. The same applies to the authentication process for other persons such as scheduling initiator A.

[0075] Next, the authentication unit 211 connects to the external system 30 using the administrator authentication information of the member information 221 and obtains the affiliation information and venue information of the corporate member to which the member administrator M belongs, which is managed by the external system 30 (step S14). Next, the authentication unit 211 registers the affiliation information and venue information obtained in step S14 into the member information 221 created and recorded in step S11 (step S15).

[0076] After this, when scheduling initiator A logs in to the scheduling device 20 for the first time via the network 11 using terminal device 40A with their own user account (step S31), the authentication unit 211 of the scheduling device 20 confirms the existence of member information 221 in which affiliation information including scheduling initiator A's user account is registered, and obtains scheduling initiator A's name (basic user information) from the affiliation information (step S16). Next, the authentication unit 211 performs authentication processing with the external system 30 using scheduling initiator A's user account (step S17).

[0077] Then, as a result of the successful authentication process in step S17, user authentication information (such as an access token) is sent from the external system 30 to the scheduling device 20. Next, the authentication unit 211 creates user information 222 corresponding to scheduling initiator A, associates it with the member information 221 confirmed in step S16, and records it in the storage unit 22. The user account of scheduling initiator A, user authentication information, and basic user information obtained in step S16 are registered in the user information 222 (step S18). This completes the user registration process.

[0078] As described above, the registration process has linked the member information 221 of the corporate member to which scheduling initiator A belongs with the user information 222 of scheduling initiator A. Therefore, from this point onward, even if member administrator M is not logged into the scheduling device 20, if scheduling initiator A, who is a user, is logged into the scheduling device 20, the scheduling unit 213 of the scheduling device 20 can access and update schedule information 311, which is stored in the external system 30 and contains the schedules of scheduling initiator A and other affiliates B, C, D, etc., belonging to the same corporate member as scheduling initiator A, as well as schedule information 311, which contains the schedules of meeting venues (conference rooms, etc.) that can be used by scheduling initiator A and other affiliates B, C, D, etc., belonging to the same corporate member as scheduling initiator A, for example, via a Web API (Application Programming Interface).

[0079] In the above-described user registration process, it was assumed that corporate member information 221 existed, and user information for users belonging to the corporate member was generated. As a variation, if the organization to which a user belongs is not a corporate member and member information 221 does not exist, an individual may log in to the scheduling device 20 and create user information 222. Then, the individual may perform a new authentication process with the external system 30 using an administrator account. In this case, the individual may be considered a corporate member, and their user account may be considered a member account. Based on the individual's user information 222, member information 221 associated with the individual may be generated.

[0080] Furthermore, in this embodiment, the member information and venue information acquired from the external system 30 are registered in the member information 221 stored in the storage unit 22. However, the member information and venue information may not be registered in the member information 221, and instead, they may be acquired from the external system 30 whenever it is necessary to refer to them.

[0081] Furthermore, in this embodiment, member information and venue information were obtained using an administrator account on the external system 30. However, if it is difficult to use the administrator account on the external system 30 for security reasons or other reasons, the member information and venue information may be directly registered to the scheduling device 20 without using the administrator account on the external system 30. For example, the member administrator M or a user of the corporate member may upload data containing the member information and venue information to the scheduling device 20, or directly input it into the user registration screen displayed on the terminal device 40M or terminal device 40A by the scheduling device 20, thereby directly registering the member information and venue information to the scheduling device 20. Alternatively, without using an administrator account, only the member information and venue information obtainable from the external system 30 may be obtained from the external system 30 using the user account privileges of the member administrator M or a user of the corporate member, and registered to the scheduling device 20.

[0082] Furthermore, in order to address situations where it becomes necessary to edit (add, change, or delete) the affiliation information or venue information registered in the member information 221, the member administrator M may log in to the scheduling device 20 using the member account and, through a prescribed operation, display the affiliation information editing screen or the venue information editing screen (neither of which is shown) on the terminal device 40M, thereby enabling editing of the affiliation information or venue information.

[0083] Furthermore, the affiliation information that member administrator M registers with the scheduling device 20 can include information on external individuals (such as external partners or employees of affiliated companies) who do not belong to the same organization as scheduling initiator A and member administrator M. In some calendar tools, if an external individual included in the affiliation information uses the same type of calendar tool as the organization to which scheduling initiator A belongs, and if scheduling initiator A or the organization to which scheduling initiator A belongs has special calendar sharing settings, then scheduling initiator A's authentication information and the ID used to identify the external individual in the external system 30 can be used to access and update the external individual's schedule information 311. In other words, the external individual can be treated the same as a participant in a meeting belonging to the same organization as scheduling initiator A. Furthermore, even if an external individual exists in the affiliation information that member administrator M registers with the scheduling device 20, if scheduling initiator A's authentication information cannot access the schedule information 311 managing the external individual's schedule, an error should be generated, preventing the external individual from being treated as a participant. In this embodiment, it is assumed that the external parties included in the member information registered by member administrator M in the scheduling device 20 have a special calendar sharing setting with scheduling initiator A or the organization to which scheduling initiator A belongs, and that they can be treated as participants designated by scheduling initiator A. Therefore, they will be described as "members belonging to the same organization as scheduling initiator A."

[0084] <Process for creating a template for scheduling conditions using the scheduling system 10> Next, Figure 4 is a sequence diagram illustrating an example of the process of creating a template for adjustment conditions by the scheduling system 10.

[0085] Users such as Coordinator A can create templates for coordination conditions according to the purpose of the meeting, such as for the first interview for new graduates, the second interview for new graduates, the final interview for new graduates, or for accepting reservations for company information sessions.

[0086] First, scheduling initiator A logs in to the scheduling device 20 via the network 11 using terminal device 40A (step S101). Next, the authentication unit 211 of the scheduling device 20 uses the user account (or user authentication information) contained in the user information 222 corresponding to scheduling initiator A, which is held in the storage unit 22, to perform authentication processing with the external system 30 (step S111).

[0087] Next, the scheduling device 20's scheduling condition setting unit 212 displays a selection screen (not shown) on the terminal device 40A for selecting either "use template" or "custom scheduling" as the method of scheduling (step S112). Here, "use template" is a method of scheduling using a scheduling condition template that can be repeatedly used for multiple meetings on different dates. "Custom scheduling" is a method of scheduling by setting scheduling conditions for each meeting. The following will explain in detail the case where scheduling initiator A selects "use template," and will omit the explanation of the case where "custom scheduling" is selected.

[0088] Next, when scheduling initiator A selects "Use template" as the method for scheduling on the selection screen (step S102), the scheduling condition setting unit 212 of the scheduling device 20 then refers to the scheduling condition template information 223 associated with the user information 222 corresponding to scheduling initiator A, and displays the scheduling condition template list screen 1000 (Figure 5), which shows a list of scheduling condition templates that have been created and are currently available for scheduling initiator A, on the terminal device 40A (step S113).

[0089] Figure 5 shows an example of the display of the adjustment condition template list screen 1000 shown on the terminal device 40A.

[0090] The Adjustment Condition Template List screen 1000 includes a "New Creation" button 1001 to direct the user to the template management information input screen 1200 (Figure 6) where new adjustment condition templates can be created, and a template list 1002 showing a list of adjustment condition templates available to adjustment initiator A. The template list 1002 displays the management name, classification, description, and reservation acceptance URL for each template. Furthermore, the template list 1002 includes an "Edit" button 1003 for directing the user to a screen (not shown) where the created adjustment condition template can be edited, and a "Copy URL" button 1004 for directing the user to copy the reservation acceptance URL.

[0091] Returning to Figure 4, when user A, who initiated the adjustment, operates the "Create New" button 1001 on the adjustment condition template list screen 1000 displayed on terminal device 40A (step S103), the adjustment condition setting unit 212 then displays the template management information input screen 1200 (Figure 6), which serves as the adjustment condition template creation screen, on terminal device 40A (step S114).

[0092] Figure 6 shows an example of the display of the template management information input screen 1200.

[0093] The template management information input screen 1200 includes input fields 1201 for entering the template's management name, 1202 for entering the template's classification, and 1203 for entering the template's purpose and description, as management information for the user of the corporate member to which the coordinator A belongs. The template management information input screen 1200 also includes input fields 1204 for entering the screen title, 1205 for entering the reservation acceptance URL, and a "Next" button 1206 to direct the user to the next screen, the meeting type selection screen 1210 (Figure 7), as information for the reservation acceptance screen that accepts reservations from the coordinating partner X.

[0094] The reservation acceptance URL must be determined by the scheduling initiator A, etc., and entered into the input field 1205, but the scheduling condition setting unit 212 may automatically generate it and reflect it in the input field 1205. Furthermore, when the scheduling partner X accesses the reservation acceptance URL, the scheduling adjustment unit 213 must be able to uniquely identify the scheduling condition template information 223 corresponding to that reservation acceptance URL. Therefore, when creating the scheduling condition template, the scheduling condition setting unit 212 confirms that the determined reservation acceptance URL is unique within the scheduling device 20.

[0095] Figure 7 shows an example of the meeting type selection screen 1210 as a template creation screen for adjustment conditions. The meeting type selection screen 1210 includes radio buttons 1211 for selecting "Accept reservation on available dates" or "Accept reservation on existing dates" as reservation acceptance patterns, radio buttons 1212 for selecting the type of meeting, and an "OK" button 1213 to instruct the user to move to the next reservation slot list screen 1300 (Figure 8, etc.).

[0096] If the reservation pattern "Reservation accepted using existing schedule" is selected via radio button 1211, the existing schedule designated by the coordinator A from the schedule information 311 of the corporate member to which the coordinator A belongs, or the venue, will be used as the reservation slot, and the reservation slot that meets the prescribed adjustment conditions will be presented to the coordinating partner X as a candidate date for the meeting (details below). Conversely, if the reservation pattern "Reservation accepted using available dates" is selected, the dates that meet the prescribed adjustment conditions and are also available to the participants will be presented to the coordinating partner X as candidate dates (details omitted).

[0097] The "Meeting Type" setting is a behavioral control item used to coordinate the meeting location with coordinator X, or to notify coordinator X of the meeting location. For example, if "Telephone / Web Conference" is selected as the meeting type, the "Web Conference URL (and the passcode required to participate, etc.)" which is the location of the web conference, will be set in the coordination condition template, and the "Web Conference URL" will be notified to coordinator X.

[0098] For example, if you select "Going Out" or "Visiting Guests" as the type of meeting, you will set the meeting location (address, building name, etc.) in the scheduling condition template and notify the scheduling partner X of the meeting location. Note that you can set the same location for all reservation slots. You can also set different locations for each reservation slot. Furthermore, for example, if you select "Other (General)" as the type of meeting, you will set a comment such as "The location is planned to be near Shinjuku Station. I will let you know once the location is decided" in the scheduling condition template and notify the scheduling partner X of this comment.

[0099] Returning to Figure 4, when the scheduling initiator A inputs the management information and reservation acceptance screen information on the template management information input screen 1200 displayed on the terminal device 40A, for example as shown in Figure 6, and operates the "Next" button 1206 (step S104), the scheduling condition setting unit 212 then displays the meeting type selection screen 1210 (Figure 7) on the terminal device 40A (step S115). Next, on the meeting type selection screen 1210, the scheduling initiator A selects the reservation acceptance pattern "Reservation acceptance with existing schedule" and the meeting type "Telephone / Web conference" and operates the "OK" button 1213, for example as shown in Figure 7 (step S105), the scheduling condition setting unit 212 then displays the reservation slot list screen 1300 (Figure 8) on the terminal device 40A (step S116).

[0100] Figure 8 shows an example of the display of the reservation slot list screen 1300 as a template creation screen for adjustment conditions. The reservation slot list screen 1300 displays a list of reservation slots 1308, which shows the type of meeting selected on the meeting type selection screen 1210 (Figure 7), the reservation acceptance pattern, and the reservation slots set for the template.

[0101] Figure 8 shows an example of the reservation slot list screen 1300 when "Set the same web conference URL for all reservation slots" is selected using radio button 1304. In this case, the reservation slot list 1308 displays the date and time, subject, participants, and number of reservations (maximum number of reservations, number of reservations already made) for each reservation slot. However, since no reservation slots have been added in Figure 8, there are 0 reservation slots.

[0102] Regarding the maximum number of reservations, it is possible to set only one maximum number of reservations in a single adjustment condition template and apply that same maximum number to all reservation slots. Alternatively, it is possible to set a maximum total number of reservations across all reservation slots in a single adjustment condition template.

[0103] The reservation slot list screen 1300 includes a "Reselect" button 1301 to redisplay the meeting type selection screen 1210 and reselect the meeting type and reservation acceptance pattern, an input field 1302 for entering comments for the coordinating partner X, a checkbox 1303 to select whether or not to automatically notify the coordinating partner X of the web conference URL when the schedule is confirmed, a radio button 1304 to select "Set the same web conference URL for all reservation slots" or "Set a different web conference URL for each reservation slot", a radio button 1305 for selecting a web conferencing tool, an input field 1306 for entering the web conference URL to be notified to the coordinating partner X, and an input field 1307 for entering information necessary to participate in the web conference (meeting ID, passcode, etc.) that should be notified to the coordinating partner X along with the web conference URL. Note that the information necessary to participate in the web conference differs depending on the type of web conferencing tool, so it may be possible to change the information to be entered in input field 1307 depending on the type of web conferencing tool selected.

[0104] In this embodiment, the Web conference URL, meeting ID, and passcode must be obtained by the scheduling initiator A from the Web conference tool and entered into input fields 1306 and 1307. However, the scheduling condition setting unit 212 may generate Web conference information by sending a request to the Web conference tool, obtain the Web conference URL, meeting ID, and passcode from the Web conference tool, and reflect them in input fields 1306 and 1307.

[0105] Furthermore, the reservation slot list screen 1300 includes an "Add Reservation Slot" button 1310 to move to the Add Reservation Slot screen 1400 (Figure 10) for adding reservation slots, a selection input field 1311 for specifying the extraction period for candidate dates and the calculation method for the number of days in the extraction period (for example, calculated on weekdays, on business days, on calendar days, etc.), a "Back" button 1312 to return to the template management information input screen 1200, and a "Next" button 1313 to move to the next reservation acceptance setting screen 1500 (Figure 12).

[0106] The selection input field 1311 allows you to specify the extraction period for candidate dates, the starting point of the extraction period (the next day in the diagram), the duration (8 days in the diagram), and the calculation method for the number of extraction days (calculated on weekdays in the diagram), all based on when the other party X accesses the reservation acceptance URL. Therefore, the adjustment condition template can be used repeatedly to schedule different meetings.

[0107] Next, Figure 9 shows an example of the reservation slot list screen 1300 when "Set a different Web conference URL for each reservation slot" is selected using radio button 1304. In this case, radio button 1305 and input fields 1306 and 1307 are omitted. The reservation slot list 1308 in Figure 9 displays the date and time, subject, participants, number of reservations (maximum number of participants, number of reservations), as well as Web conference information (Web conference URL, meeting ID, and passcode) for each reservation slot. However, since no reservation slots have been added in Figure 9, there are 0 reservation slots. Note that the Web conference information in Figure 9 has three input fields, which is the maximum number of items for commonly used Web conferencing tools. However, radio button 1305 from Figure 8 may also be included in Figure 9. Alternatively, the system may be configured to allow users to specify a Web conferencing tool for each reservation slot, and the input fields for Web conference information may change depending on the type of Web conferencing tool.

[0108] Returning to Figure 4, when the person initiating the adjustment, A, operates the "Add Reservation Slot" button 1310 on the reservation slot list screen 1300 displayed on the terminal device 40A (step S106), the adjustment condition setting unit 212 then displays the Add Reservation Slot screen 1400 (Figure 10) on the terminal device 40A (step S117).

[0109] Figure 10 shows an example of the display of the reservation slot addition screen 1400 as a template creation screen for adjustment conditions. The reservation slot addition screen 1400 includes a search condition setting field 1401 for setting search conditions, a "Search" button 1405 for instructing the search to be executed, a "Clear" button 1406 for clearing the search conditions, a search results list 1407 showing a list of existing appointments found through searching, a "Back" button 1408 for canceling the addition of a reservation slot and returning to the reservation slot list screen 1300, and a "Confirm" button 1409 for adding an existing appointment selected by the adjustment initiator A from the existing appointments in the search results to the reservation slot.

[0110] The search criteria setting field 1401 includes a selection input field 1402 for setting the search period for existing appointments, a selection input field 1403 for selecting the schedule information to be searched, and an input field 1404 for entering search keywords.

[0111] In the selection input field 1403, the adjustment condition setting unit 212 can select the schedule information 311 of members of the corporate member to which adjustment initiator A belongs, or of venues available to those members, by referring to the member information 221 of the corporate member to which adjustment initiator A belongs, or venue information.

[0112] The search results list 1407 displays the date, time, subject, and participants of existing appointments as search results. Additionally, the search results list 1407 includes checkboxes 1410, allowing users to choose whether to add all existing appointments displayed as search results, or each appointment individually, to the list of potential booking slots.

[0113] On the reservation slot addition screen 1400, you can select potential reservation slots by checking some or all of the existing appointments displayed as search results for a given search condition using the checkbox 1410. Then, even if you perform a new search with different search conditions, you can further increase the number of potential reservation slots from the results of the new search. In this case, existing appointments that have been checked as potential reservation slots will not disappear from the display of the search results list 1407 even if you perform a new search with different search conditions. Instead, they will remain displayed at the top of the search results list 1407 with a changed row color, and the new search results obtained during the new search will be displayed below the checked existing appointments. In this way, even if you repeat the search and selection of potential reservation slots multiple times, you can confirm all the potential reservation slots you have selected on the same screen and make your final decision on which slots to add.

[0114] Returning to Figure 4, when the person initiating the adjustment, A, sets the search conditions in the search condition setting field 1401 and operates the "Search" button 1405 on the reservation slot addition screen 1400 displayed on the terminal device 40A (step S107), the adjustment condition setting unit 212 then refers to the search target schedule information managed by the external system 30 and searches for existing appointments within the search period that contain the search keyword in the subject. The unit then obtains the appointment ID, date and time, subject, participants, etc. of the found existing appointments (step S118) and reflects them in the search results list 1407 on the reservation slot addition screen 1400 displayed on the terminal device 40A (step S119). In this embodiment, existing appointments containing the search keyword in the subject are searched, but it is also possible to search for existing appointments that contain the search keyword in other attribute items held by the appointment in the schedule information 311, such as the appointment's remarks.

[0115] In this case, the person initiating the scheduling, A, in the booking slot addition screen 1400, sets the search period to May 8, 2021 to May 31, 2021, the target schedule information to be searched to A's own schedule information 311, and the search keyword to "company information session," and instructs the system to perform a search. As a result, seven existing scheduled events are displayed in the search results list 1407.

[0116] Next, when the person initiating the adjustment, A, selects an existing appointment to be added to the reservation slot from the existing appointments displayed in the search results list 1407 of the reservation slot addition screen 1400 and operates the "Confirm" button 1409 (step S108), the adjustment condition setting unit 212 then displays the reservation slot list screen 1300 (Figure 11) that reflects the addition of the reservation slot on the terminal device 40A (step S120).

[0117] In this case, it is assumed that person A, who initiated the adjustment, selects all seven existing appointments displayed in the search results list 1407 on the booking slot addition screen 1400 and operates the "Confirm" button 1409, thereby adding seven booking slots.

[0118] Figure 11 shows an example of the reservation slot list screen 1300 displaying the addition of reservation slots when "Set the same web conference URL for all reservation slots" is selected using radio button 1304. However, the display example in Figure 11 omits the display of the meeting type and meeting method that were shown on the reservation slot list screen 1300 in Figures 8 and 9.

[0119] The reservation list screen 1308 on the reservation list screen 1300 displays the date and time, subject, participants, and number of reservations (maximum number of reservations, number of reservations already made) for each reservation slot. Reservation initiator A can set the maximum number of reservations for each reservation slot. Reservation initiator A can also delete each reservation slot individually.

[0120] Although not shown in the diagram, if "Set a different web conference URL for each reservation slot" is selected using radio button 1304, the reservation slot list 1308 will display the date and time, subject, participants, and number of reservations (maximum number of participants, number of reservations already made) for each reservation slot, as well as the web conference information (web conference URL, meeting ID, and passcode). In this case, scheduling initiator A can set the maximum number of participants and the web conference information for each reservation slot. Furthermore, scheduling initiator A can delete each reservation slot individually.

[0121] Returning to Figure 4, when the adjustment initiator A sets the adjustment conditions such as the maximum number of reservations and the extraction period for candidate dates for each reservation slot displayed in the reservation slot list 1308 on the reservation slot list screen 1300 and operates the "Next" button 1313 (step S109), the adjustment condition setting unit 212 then displays the reservation acceptance setting screen 1500 (Figure 12) on the terminal device 40A for setting various behaviors during and after reservation acceptance (step S121).

[0122] Figure 12 shows an example of the reservation acceptance setting screen 1500 as a template creation screen for adjustment conditions. The reservation acceptance setting screen 1500 includes a checkbox 1501 for setting the input items to be requested from the adjustment partner X (reservant) when accepting a reservation, a checkbox 1502 for setting whether or not there are any contact details after acceptance, a checkbox 1503 for setting whether or not the reservation can be canceled by the reservation holder, and an input field 1504 for entering cautionary explanations for the reservation holder. Furthermore, the reservation acceptance setting screen 1500 includes a checkbox 1505 for selecting participants as internal notification recipients upon completion of the reservation, a checkbox 1506 for selecting non-participants, an input field 1507 for entering the email address of non-participant notification recipients, a "Back" button 1508 to return to the reservation slot list screen 1300 (Figure 11), and a "Complete" button 1509 to indicate the completion of settings on the reservation acceptance setting screen 1500 and the completion of the series of settings on the adjustment condition template creation screen (Figures 6 to 12).

[0123] Returning to Figure 4, when the person initiating the adjustment, A, sets the input items for acceptance, notification destinations upon completion, etc. on the reservation acceptance setting screen 1500 and operates the "Complete" button 1509 (step S110), the adjustment condition setting unit 212 then generates new adjustment condition template information 223 associated with the user information 222 of the person initiating the adjustment, A, and stores it in the storage unit 22. The management information set on the template management information input screen 1200, the information on the reservation acceptance screen, the type of meeting, the meeting method, the list of reservation slots (schedule ID of existing schedules, date and time of reservation slots, etc.) set on the meeting type selection screen 1210 and the reservation slot list screen 1300, as well as the adjustment conditions (extraction period for candidate dates, maximum number of reservations, etc.), the input items for acceptance, notification destinations upon completion, etc. set on the reservation acceptance setting screen 1500 are registered in the adjustment condition template information 223 (step S122). This completes the adjustment condition template creation process.

[0124] The adjustment condition template creation process described above allows for the creation of adjustment condition templates that can be repeatedly used to schedule different meetings. Furthermore, existing appointments designated by the adjustment initiator A as reservation slots, which belong to the same corporate member as the adjustment initiator A, or are registered in the venue's schedule information 311, can be presented to the adjustment partner X as candidate meeting dates.

[0125] <Schedule adjustment process using adjustment condition template> Next, Figure 13 is a sequence diagram illustrating an example of a scheduling process that uses the adjustment condition template created by the adjustment condition template creation process shown in Figure 4.

[0126] The scheduling process follows the same steps S101, S111, S112, S102, and S113 as the scheduling condition template creation process shown in Figure 4.

[0127] Figure 14 shows an example of the display of the adjustment condition template list screen 1000 shown on the terminal device 40A in step S113. The adjustment condition template list screen 1000 in Figure 14 has an adjustment condition template with the management name "Reservation acceptance for new graduate recruitment company information sessions" added to the adjustment condition template list screen 1000 in Figure 5 as a result of the adjustment condition template creation process described above.

[0128] Return to Figure 13. Next, the person initiating the scheduling process, A, operates the "Copy URL" button 1004 on the scheduling condition template list screen 1000 (Figure 14) for the scheduling condition template with the management name "Reservation Acceptance for New Graduate Recruitment Company Information Session" to copy the reservation acceptance URL, paste it into an email or similar, and send it to the scheduling partner X's terminal device 40X (Step S141). Alternatively, instead of sending the reservation acceptance URL to scheduling partner X via email or similar, or in addition, the reservation acceptance URL may also be made public on the organizer's website, for example. No further action is required from the person initiating the scheduling process, A.

[0129] Next, when the scheduling partner X accesses the reservation acceptance URL using the terminal device 40X (step S151), the scheduling unit 213 displays the comment confirmation screen 1600 (Figure 15) as the reservation acceptance screen on the terminal device 40X (step S161).

[0130] Figure 15 shows an example of the display of the comment confirmation screen 1600. The comment confirmation screen 1600 displays information about the meeting entered by the scheduling initiator A, such as comments from the organizer. The comment confirmation screen 1600 also has a checkbox 1601 to check when the comments from the organizer have been confirmed, and a "Go to Date Selection" button 1602 to direct the user to the date selection screen 1800 (Figure 16) where the date to be reserved can be selected.

[0131] In this embodiment, the comment confirmation screen 1600 unilaterally displays only the organizer's comments to the adjustment partner X. However, the comment confirmation screen 1600 may also allow the adjustment partner X to input comments in response to the organizer's comments. Furthermore, when the adjustment initiator A creates the adjustment condition template, it may be possible to set whether or not to allow the adjustment partner X to input comments.

[0132] Return to Figure 13. Next, when the scheduling partner X checks the checkbox 1601 on the comment confirmation screen 1600 and operates the "Proceed to Date Selection" button 1602 (step S152), the scheduling unit 213 reads the reservation slot list (schedule ID of existing schedule, date and time of reservation slot, etc.) and scheduling conditions (extraction period, maximum number of reservations) from the scheduling condition template information 223 of scheduling initiator A corresponding to the reservation acceptance URL, and refers to the existing schedule corresponding to the reservation slot in the schedule information 311 managed by the external system 30, and confirms that the start date and end date and time of the existing schedule remain in the schedule information 311 without being changed from the date and time of the reservation slot stored in the reservation slot list of the scheduling condition template information 223. In addition, if there is scheduling information 224 associated with the scheduling condition template information 223, the scheduling unit 213 refers to it and identifies a reservation slot in which the number of scheduling partners who have been scheduled (booked) is less than the maximum number of reservations. Then, the scheduling unit 213 extracts reservation slots within the extraction period as candidate dates if the corresponding existing schedule remains in the schedule information 311 without any changes to its start and end dates, the number of coordinated partners is less than the maximum number of reservations (step S162).

[0133] Next, the scheduling unit 213 displays the schedule selection screen 1800 (Figure 16) and the schedule confirmation screen 1900 (Figure 17) on the terminal device 40X in order to present the extracted candidate dates to the scheduling partner X and allow them to select one (step S163).

[0134] Figure 16 shows an example of the display of the schedule selection screen 1800. The schedule selection screen 1800 displays a calendar 1801 with dates on the horizontal axis and times on the vertical axis in a grid pattern, and a list of candidate dates 1803. The schedule selection screen 1800 also has an "Inconvenient" button 1804 for use if the candidate dates shown on the schedule selection screen 1800 are inconvenient, and a "Next" button 1805 for confirming the selected meeting date.

[0135] In Calendar 1801, candidate date slots 1802 are displayed with a different color or other indication to distinguish them from the other slots. The coordinating partner X can select a meeting date by selecting one of the candidate date slots 1802 in Calendar 1801, or one of the candidate date slots in the candidate date list 1803, which lists the candidate dates.

[0136] If the scheduling partner X presses the "Inconvenient" button 1804, the scheduling unit 213 interrupts the currently running scheduling process and notifies the scheduling initiator A that the scheduling partner X has pressed the "Inconvenient" button 1804. If the scheduling partner X presses the "Next" button 1805, the scheduling unit 213 displays a scheduling confirmation screen 1900 (Figure 17) to the terminal device 40X for the scheduling partner X to confirm the meeting date selected by themselves.

[0137] In this case, suppose the scheduling partner X selects a candidate date, for example, Monday, May 10th, from 16:00 to 17:00 on the schedule selection screen 1800 (Figure 16), and then clicks the "Next" button 1805.

[0138] Next, Figure 17 shows an example of the display of the schedule confirmation screen 1900. The schedule confirmation screen 1900 displays a calendar 1901 with dates on the horizontal axis and times on the vertical axis in a grid pattern, as well as the meeting schedule 1903.

[0139] In Calendar 1901, the meeting schedule frame 1902, which represents the meeting date selected by the scheduling partner X on the schedule selection screen 1800, is displayed with a different color or other indication to distinguish it from the other frames. Additionally, the meeting date 1903 displays the meeting date selected by the scheduling partner X.

[0140] Furthermore, the schedule confirmation screen 1900 includes a "Back" button 1904 to return to the schedule selection screen 1800 (Figure 16), and a "Next" button 1905 to move to the reservation information input screen 2000 (Figure 18).

[0141] Returning to Figure 13, when the scheduling partner X operates the "Next" button 1905 on the schedule confirmation screen 1900 (Figure 17) displayed on the terminal device 40X (step S153), the scheduling unit 213 then displays the reservation information input screen 2000 (Figure 18) on the terminal device 40X as a reservation acceptance screen for the scheduling partner X to enter the reservation information (step S164).

[0142] Figure 18 shows an example of the reservation information input screen 2000. The reservation information input screen 2000 includes an input field 2001 for the coordinating partner X to enter the company name (school name), an input field 2002 for entering the name, an input field 2003 for entering the email address, checkboxes 2004 and 2005 to specify the timing of notification of the notification email informing about the meeting details, a "back" button 2006 to return to the schedule confirmation screen 1900, and a "confirm" button 2007 to instruct the user to confirm the input on the reservation information input screen 2000 and to confirm the series of operations on the reservation acceptance screen (Figures 15 to 18).

[0143] Return to Figure 13. On the reservation information input screen 2000, when the coordinating partner X enters their own reservation information (company name (school name), name, email address) and operates the "Confirm" button 2007 (step S154), the scheduling unit 213 then makes a final confirmation that the meeting date (reservation slot) that coordinating partner X is trying to confirm is still available for reservation at that time (step S165).

[0144] Specifically, the scheduling unit 213 refers to the schedule information 311 managed by the external system 30 and makes a final confirmation that the existing schedule corresponding to the meeting date (reservation slot) that the scheduling partner X is trying to confirm remains in the schedule information 311 without any changes from the start date and end date and time of the reservation slot held in the scheduling condition template information 223. Furthermore, the scheduling unit 213 refers to the scheduling information 224 associated with the said scheduling condition template information 223 and confirms that the number of scheduling partners who have already made arrangements (reservations) for the meeting date (reservation slot) that is trying to confirm is less than the maximum number of reservations.

[0145] Here, if at least one of the start and end dates of an existing appointment corresponding to the meeting date (reservation slot) that coordinating partner X is trying to confirm has been changed since it was saved as a reservation slot in the adjustment condition template information 223, or if the existing appointment has been deleted, or if the number of coordinating partners who have already made adjustments (reservations) for the meeting date (reservation slot) that is trying to confirm has reached the reservation limit, then a message such as "The selected date is full. Please select again" will be displayed on the terminal device 40X, and the process will be returned to step S162, restarting from the operation of coordinating partner X on the date selection screen 1800.

[0146] Conversely, if an existing schedule corresponding to the meeting date (reservation slot) to be confirmed remains in the schedule information 311 without any changes to the start and end dates of the reservation slot, and it is finally confirmed that the number of people who have made adjustments (reservations) for the meeting date (reservation slot) to be confirmed is less than the maximum number of reservations, the scheduling unit 213 will treat the date as a confirmed meeting date and add the names and other information entered as reservation information to the remarks column of the existing schedule corresponding to the confirmed meeting date in the schedule information 311 managed by the external system 30. In addition, the scheduling unit 213 will register new scheduling information 224 as information that the person making the adjustment, X, has completed the reservation, in association with the user information 222 of the person making the adjustment, A, and the adjustment condition template information 223 used (step S166). Furthermore, the scheduling unit 213 will display the scheduling notification screen 2100 (Figure 19) on the terminal device 40X (step S167).

[0147] Figure 19 shows an example of the display of the schedule notification screen 2100. The schedule notification screen 2100 displays the date and other details of the confirmed meeting. The schedule notification screen 2100 also has a "Register to Calendar Tool" button 2101 and a "Register to Schedule App" button 2102. If the coordinating partner X is using the calendar tool 31, they can register the confirmed meeting as their own schedule in the calendar tool 31 by operating the "Register to Calendar Tool" button 2101. Alternatively, the coordinating partner X can register the confirmed meeting in their own schedule management application program by operating the "Register to Schedule App" button 2102.

[0148] Next, the scheduling unit 213 sends a notification email to the email address specified by the scheduling partner X, informing the scheduling partner X of the details of the meeting, according to the notification timing selected by the scheduling partner X (step S168).

[0149] However, in this embodiment, it is assumed that the scheduling partner X receives an email on the terminal device 40X, and in step S168, an arrow is shown from the scheduling device 20 to the terminal device 40X. However, the scheduling partner X may receive the notification email from the scheduling device 20 using an electronic device other than the terminal device 40X.

[0150] Next, the scheduling unit 213 sends a notification email to the company's participants, etc., informing them of the meeting details, according to the "Notification to our company" setting on the reservation acceptance setting screen 1500 (Figure 12) (step S169).

[0151] According to the scheduling process described above, the only action required of scheduling initiator A is to create a scheduling condition template, select the template, and send the reservation acceptance URL to scheduling partner X. This allows for automatic acceptance of reservations for company information sessions, significantly reducing the workload for scheduling initiator A.

[0152] Furthermore, the scheduling process allows existing appointments registered in the schedule information 311 managed by the external system 30 to be set as reservation slots in the scheduling condition template. In addition, reservations from the scheduling partner X can be easily and efficiently accepted for candidate dates extracted from the reservation slots, while adhering to the maximum number of reservations.

[0153] Furthermore, in situations such as company information sessions or seminars where multiple people make reservations for a single meeting date (reservation slot), the location is often determined in advance. Therefore, simultaneously accepting the reservation for the meeting date and notifying the other party X of the meeting location (including the web conferencing method) can significantly reduce the workload for the person initiating the scheduling, A.

[0154] Furthermore, the scheduling template can be reused, and the reservation acceptance URL corresponding to the scheduling template is fixed. Therefore, by, for example, linking to it on the company's homepage or providing a link to the reservation acceptance URL after the user fills out an inquiry form, scheduling can be done without the need to send the reservation acceptance URL to the other party X.

[0155] Furthermore, by including a reservation URL in a mass email, the reservation URL can be sent simultaneously to multiple contacts X.

[0156] The scheduling device of this embodiment typically provides various operation screens, for example, as web pages, which can be displayed on the web browser of a terminal device. However, it is not limited to this embodiment. For example, a dedicated application with various operation screens may be installed on the terminal device. In this case, the scheduling device can display the various operation screens on the dedicated application of the terminal device simply by transmitting some of the content to be displayed on the various operation screens (data such as candidate dates) to the terminal device. In other words, the scheduling device of the present invention can include various embodiments that allow the terminal device to display screens.

[0157] The present invention is not limited to the embodiments and modifications described above, and various further modifications are possible. For example, the embodiments and modifications described above are explained in detail for the purpose of clearly illustrating the present invention, and are not necessarily limited to those having all the configurations described. Furthermore, it is possible to replace parts of one modification with other modifications or to combine modifications.

[0158] Furthermore, each of the above configurations, functions, processing units, and processing means may be implemented in hardware, either partially or entirely, by designing them as integrated circuits, for example. Alternatively, each of the above configurations and functions may be implemented in software by a processor interpreting and executing programs that implement each function. Information such as programs, tables, and files that implement each function can be stored in memory, recording devices such as hard disks and SSDs, or recording media such as IC cards, SD cards, and DVDs. Also, control lines and information lines are shown only if deemed necessary for explanation, and not all control lines and information lines are necessarily shown in the actual product. In practice, it can be assumed that almost all configurations are interconnected. [Explanation of Symbols]

[0159] 10... Schedule adjustment system, 11... Network, 20... Schedule adjustment device, 21... Processing unit, 211... Authentication unit, 212... Adjustment condition setting unit, 213... Schedule adjustment unit, 22... Storage unit, 221... Member information, 222... User information, 223... Adjustment condition template information, 224... Schedule adjustment information, 23... Communication unit, 30... External system, 31... Calendar tool, 311... Schedule information Report, 40A...Terminal device, 40M...Terminal device, 40X...Terminal device, 1000...Adjustment condition template list screen, 1200...Template management information input screen, 1300...Reservation slot list screen, 1400...Add reservation slot screen, 1500...Reservation acceptance setting screen, 1600...Comment confirmation screen, 1800...Schedule selection screen, 1900...Schedule confirmation screen, 2000...Reservation information input screen, 2100...Schedule notification screen

Claims

1. A schedule adjustment system in which a schedule adjustment device, a first terminal device used by an adjustment initiator, and a second terminal device used by an adjustment partner are connected via a network, and which adjusts a meeting schedule based on adjustment conditions related to the meeting, the first terminal device displays an adjustment initiator operation screen for the adjustment initiator and receives an input from the adjustment initiator; the second terminal device displays a adjustment partner operation screen for the adjustment partner and receives an input from the adjustment partner; The schedule adjustment device includes: Among existing plans registered in schedule information managed by a calendar tool, the existing plan designated by the adjustment initiator is set as a reservation slot, and the adjustment conditions including the designation of the reservation slot are registered in an adjustment condition template that can be repeatedly used for adjusting the schedule of different meetings; When the adjustment partner accesses based on access information corresponding to the adjustment condition template, the reservation slots among the reservation slots that satisfy the adjustment condition are set as candidate dates, a date selection screen showing the candidate dates is displayed on the second terminal device as the adjustment partner operation screen, and the selected candidate date is determined as the meeting date in response to an operation of the adjustment partner to select one of the candidate dates on the date selection screen. Scheduling system.

2. The schedule adjustment system according to claim 1, The schedule adjustment device includes: The schedule information managed by the calendar tool and designated by the adjustment initiator is set as search target schedule information; A search is performed for existing plans that satisfy a search condition set by the adjustment initiator among the existing plans registered in the search target schedule information; Among the existing schedules as a result of the search, the existing schedule selected by the adjustment initiator is set as the reservation slot. Scheduling system.

3. The schedule adjustment system according to claim 2, The adjustment initiator executes, for the same adjustment condition template, one or more times a process of setting the search conditions and a process of selecting the reservation slot from the existing schedule as the search result. Scheduling system.

4. The schedule adjustment system according to claim 2, The schedule adjustment device includes: Among the existing plans registered in the search target schedule information, a search keyword as the search condition is included in information about the existing plan, and the existing plan is searched for. Scheduling system.

5. The schedule adjustment system according to claim 2, The schedule adjustment device includes: Among the existing plans registered in the search target schedule information, existing plans within a search period as the search condition are searched for. Scheduling system.

6. The schedule adjustment system according to claim 2, The schedule adjustment device includes: The schedule information of a member of the same organization as the coordination initiator, which is specified by the coordination initiator, or the schedule information of a venue available to the member is set as the search target schedule information. Scheduling system.

7. A schedule adjustment system according to any one of claims 1 to 6, The schedule adjustment device includes: An extraction period is set as the adjustment condition, When the adjustment partner accesses the schedule based on the access information, the reservation slots within the extraction period starting from the timing when the adjustment partner accesses the schedule are set as the candidate schedule. Scheduling system.

8. A schedule adjustment system according to any one of claims 1 to 6, The schedule adjustment device includes: Set a reservation limit for the number of people as the adjustment condition, When the person to be adjusted accesses the reservation schedule based on the access information, the reservation slot in which the number of people who have made reservations with the person to be adjusted is less than the upper reservation limit number is set as the candidate date. Scheduling system.

9. A schedule adjustment system according to any one of claims 1 to 6, The schedule adjustment device includes: Add information about the person to be coordinated to the existing plan registered in the schedule information managed by the calendar tool, which corresponds to the determined meeting date. Scheduling system.

10. A schedule adjustment system according to any one of claims 1 to 6, The schedule adjustment device includes: The determined meeting schedule and information about the Web conference or the location designated by the coordination initiator for the coordination condition template or the reservation slot are notified to the coordination partner. Scheduling system.

11. A schedule adjustment method for a schedule adjustment system in which a schedule adjustment device, a first terminal device used by an adjustment initiator, and a second terminal device used by an adjustment partner are connected via a network, and a meeting schedule is adjusted based on adjustment conditions related to the meeting, comprising: the first terminal device displays an adjustment initiator operation screen for the adjustment initiator and receives an input from the adjustment initiator; the second terminal device displays a adjustment partner operation screen for the adjustment partner and receives an input from the adjustment partner; The schedule adjustment device Among existing plans registered in schedule information managed by a calendar tool, the existing plan designated by the adjustment initiator is set as a reservation slot, and the adjustment conditions including the designation of the reservation slot are registered in an adjustment condition template that can be repeatedly used for adjusting the schedule of different meetings; When the adjustment partner accesses based on access information corresponding to the adjustment condition template, the reservation slots among the reservation slots that satisfy the adjustment condition are set as candidate dates, a date selection screen showing the candidate dates is displayed on the second terminal device as the adjustment partner operation screen, and the selected candidate date is determined as the meeting date in response to an operation of the adjustment partner to select one of the candidate dates on the date selection screen. How to schedule, including steps.

Images