WO2020256116A1

WO2020256116A1 - Schedule adjustment method and storage medium for storing schedule adjustment program

Info

Publication number: WO2020256116A1
Application number: PCT/JP2020/024171
Authority: WO
Inventors: 夏樹塚野; 俊二川村; 暖山本; 圭北原
Original assignee: 株式会社日立製作所
Priority date: 2019-06-20
Filing date: 2020-06-19
Publication date: 2020-12-24
Also published as: JP7261878B2; JPWO2020256116A1

Abstract

A schedule adjustment method for a schedule adjustment system configured from a terminal device connected to a network, a schedule adjustment server and an external service provider, wherein the schedule adjustment server ascertains the state of congestion during the commuting time frame of a user on the basis of user information from the terminal device and past congestion conditions from the external service provider, and also executes congestion state adjustment processing when the user is attempting to commute while it is congested and there is an empty room at a shared office near a location which is closer than is the commuting destination, on the basis of shared office information from the external service provider.

Description

Storage medium that stores the schedule adjustment method and schedule adjustment program

The present invention relates to a technique for adjusting a user's schedule.

In recent years, in order to improve the quality of life of all people and realize a society where they can work and play an active role, work style reforms, ingenuity in transportation behavior, shared offices, satellite offices, coworking spaces (hereinafter, "shared offices, etc."" There is a social trend in which various work styles are recognized. On the other hand, frameworks and technologies for managing, collecting, and utilizing personal information such as information banks and PDSs (Personal Data Stores) are being developed.

There is Patent Document 1 that manages or adjusts the schedule as a tool for efficiently promoting business toward the realization of work style reform. Patent Document 1 discloses a technique for proposing an optimum schedule by adjusting one's own schedule and the schedule of conference participants in consideration of travel time and importance when creating or adding a schedule. ..

As a device for traffic behavior, there is Patent Document 2 for the purpose of alleviating road congestion. Patent Document 2 discloses a technique for making a road traffic reservation, predicting the degree of congestion from the reservation result, reflecting the predicted degree of congestion in the toll, and mixing the congestion.

Japanese Unexamined Patent Publication No. 2013-3877 WO13 / 018656

However, Patent Document 1 does not consider the creation of free time by devising traffic behavior or using shared offices when adjusting the schedule. Further, Patent Document 2 does not present a method of avoiding congestion, only motivation for avoiding congestion time zone. That is, there is a problem that commuting congestion is not alleviated even if the schedule during work is streamlined.

The present invention has been made in view of such circumstances, and an object of the present invention is to adjust a schedule that can create free time while avoiding commuting during busy hours.

In view of the above background technology and problems, the present invention is, for example, a schedule adjustment method of a schedule adjustment system composed of a terminal device connected to a network, a schedule adjustment server, and an external service provider. Based on the user's information from the device and the past congestion status from the external service provider, the schedule adjustment server grasps the congestion status during the user's commuting time, and the user is in a congested state. If you are going to work and there is a vacancy in the shared office near the place before commuting based on the shared office information from the external service provider, the schedule adjustment server performs the congestion status adjustment process.

Details of at least one implementation of the subject matter disclosed herein are described in the accompanying drawings and in the description below. Other features, aspects, and effects of the disclosed subject matter are manifested in the disclosures, drawings, and claims below.

According to the present invention, it is possible to provide a schedule adjustment method and a schedule adjustment program capable of performing schedule adjustment that can create free time while avoiding commuting during busy hours.

It is a block diagram which shows an example of the whole structure of the schedule adjustment system in an Example. It is a block diagram which shows an example of the hardware composition of the schedule adjustment server 102 in an Example. It is a block diagram which shows an example of the hardware composition of the information bank 103 in an Example. It is a sequence which shows an example of the processing procedure of the schedule adjustment system in an Example. It is a figure which shows an example of the contents of the user basic information, the user schedule, and the execution place information held in the user information holding part of the schedule adjustment server in an Example. It is a figure which shows an example of the contents of the operation information, the timetable information, the shared office information, and the past congestion information held in the external service information holding part of the schedule adjustment server in an Example. It is a figure which shows an example of the content example of the congestion information stored in the congestion information holding part of the schedule adjustment server in an Example. It is a flow chart which shows an example of the congestion situation grasp process of the schedule adjustment server in an Example. It is a flow chart which shows an example of the schedule adjustment processing of the schedule adjustment server in an Example. It is a conceptual diagram which shows an example of the image before and after the schedule adjustment of the schedule adjustment system in an Example.

Hereinafter, examples of the present invention will be described with reference to the drawings. The same components and processes are designated by the same reference numerals throughout the drawings, and duplicate description thereof will be omitted.

In this embodiment, a system that adjusts the schedule so that the user can commute to work while avoiding commuting congestion will be described based on the schedule of each user.

FIG. 1 is a block diagram showing the overall configuration of the schedule adjustment system in this embodiment. In FIG. 1, the schedule adjustment system is a service system composed of a plurality of terminal devices 101, a schedule adjustment server 102, an information bank 103, and an external service provider 104 connected to a network 105 such as the Internet. ..

The terminal device 101 is a device held for each user and can be realized by a general computer. Although the figure is omitted, it includes a calculation unit, a communication unit, a storage unit, an input / output unit, and a position information acquisition unit. The communication unit can communicate with a network such as the Internet. The position information acquisition unit acquires the position information of the user, and is composed of an application or the like running on the terminal device 101. The user can exchange information with the schedule adjustment system and use various services provided by the information bank and the external service provider by using the Web browser, the application and the add-on installed in the terminal device.

The external service provider 104 can be realized by a general server device, and can be used for various services such as confirmation of availability information and reservation management of satellite offices, provision of past congestion information, schedule management, and the like. Providing services.

FIG. 2 is a block diagram showing the hardware configuration of the schedule adjustment server 102 in this embodiment. In FIG. 2, the schedule adjustment server 102 can be realized by a general server device, from the calculation unit 201 that grasps the congestion status and adjusts the schedule according to the congestion status, the congestion status, the user information, and the external service. A storage unit 202 that stores acquired information, a communication unit 203 that exchanges information with a terminal device 101, an information bank 103, and an external service provider 104 via a network 105, and an input / output unit 204 that receives input from a server administrator. Each part is connected by BUS or the like.

The calculation unit 201 avoids congestion based on the congestion status grasping processing unit 205 that calculates the congestion status from the user information and the information acquired from the external service provider 104, and the grasped congestion status and the user's schedule and intention. It has a congestion adjustment processing unit 206 that adjusts so as to be.

The storage unit 202 includes a congestion information holding unit 207 that holds the congestion information that is the processing result of the congestion status grasping processing unit 205 including a history, basic information of the user such as an address and main commuting means, and a user. User information holding unit 208 that holds information on the schedule and location where the schedule is implemented, and external service information holding that holds past congestion status, location and availability information of shared office services acquired from the external service provider 104, etc. It has a part 209.

The communication unit 203 transmits the result processed by the calculation unit 201 to the terminal device 101, the information bank 103, and the external service provider 104 via a network such as the Internet, or information necessary for processing by the calculation unit 201. And the information stored in the storage unit 202 is received from the terminal device 101, the information bank 103, and the external service provider 104.

FIG. 3 is a block diagram showing the hardware configuration of the information bank 103 in this embodiment.

The information bank 103 can be realized by a general server device, and has a calculation unit 301 for managing personal data, a storage unit 302 for holding personal data, a terminal device 101, a schedule adjustment server 102, an external service provider 104, and a network 105. It is composed of a communication unit 303 for exchanging information via the information bank 103 and an input / output unit 304 for receiving input from the administrator of the information bank 103, and each unit is connected by a BUS or the like.

The calculation unit 301 includes an information cooperation unit 305 that exchanges personal data with the user using the terminal device 101 and exchanges personal data with the schedule adjustment server 102 and the external service provider 104 based on the contract with the user. It has a personal data management unit 306 that controls access, controls the information collection period, deletes information, and the like based on a contract with a user.

The storage unit 302 has a personal data holding unit 307 that holds personal data obtained as a result of the processing of the information linking unit 305.

The communication unit 303 transmits the result processed by the calculation unit 301 to the terminal device 101, the schedule adjustment server 102, and the external service provider 104 via a network such as the Internet, or is required for processing by the calculation unit 301. Information and information stored in the storage unit 302 are received from the terminal device 101, the schedule adjustment server 102, and the external service provider 104.

Note that various programs executed by the calculation unit 201 and the calculation unit 301, or a part thereof, may be referred to as "part", "unit", "means", "function", "module" or the like. Further, the configuration of this embodiment may be configured by a single computer including a CPU, a memory, an external storage device, or the like, or any part of the input device, output device, processing device, storage device, etc. may be connected to a network. It may consist of a plurality of connected computers.

In the above configuration, the processing of the arithmetic unit 201 and the arithmetic unit 301 can be realized by the CPU executing a predetermined program loaded in the memory. That is, the

communication units

203 and 303 can be realized by the CPU using the communication device. The input /

output units

204 and 304 are realized by the CPU using an input device or an output device. Further, the

storage units

202 and 302 are realized by the CPU using a memory or an external storage device. Further, the

calculation units

201 and 301 are realized as CPU processes.

These programs may be pre-stored in the computer's memory or external storage, and when needed, from removable storage media available to the computer, or from communication media (such as the network 105, or them). It may be introduced from other devices via a carrier wave or digital signal propagating over it.

Further, a plurality of storage units having different storage methods such as RDB (Relational Database), file server, KVS (Key-Value Store), etc., depending on the size and format of the data stored in the storage unit 202 and the storage unit 302. It may be composed of. Further, a part or all of the data equivalent to the stored data may be provided from a plurality of other servers connected to the network 105 such as the Internet, or by a removable storage medium.

Further, each component shown in FIGS. 2 and 3 does not need to be physically separated, and one component may also serve as the other.

FIG. 4 is a sequence showing the processing procedure of the schedule adjustment system in this embodiment. That is, it shows a series of processing flows in which the schedule adjustment system acquires information from the user, grasps the congestion status, and adjusts the schedule so as to avoid congestion.

In FIG. 4, the user first uses his / her own terminal device 101 to register his / her own information in the information bank 103, set which service is permitted to use his / her own information, and the like, and then sets the information bank 103. Stores information in the personal data holding unit 307 (S401). Note that step S401 may be performed at any timing desired by the user, such as when the user starts using a new service.

Next, the user uses his / her own terminal device 101 to use the service using the personal data provided by the external service provider 104 (S402). External service providers provide various services, such as schedule sharing services and route guidance services. Note that step S402 may be performed at any time when the user desires to use the external service.

Next, the external service provider 104 provides the service usage history, the information input by the user at the time of using the service, and the stored information to the information bank 103, and the information bank 103 provides the data provided to the personal data holding unit 307. Is memorized (S403). Note that step S403 may be performed at a timing agreed between the information bank 103, the external service provider 104, and the user, such as the date and time, weekly, and the timing when the information is changed.

Next, the information bank 103 sets the schedule adjustment server for the user basic information 501, the user schedule 502, and the implementation location information 503, which will be described later, among the personal data held in the personal data holding unit 307, which are necessary for schedule adjustment. The information is transmitted to 102, and the schedule adjustment server 102 stores the received information in the user information holding unit 208 (S404). The information of the user basic information 501, the user schedule 502, and the implementation location information 503 may be directly obtained from the user by the schedule adjustment server 102 via the terminal device 101. Further, even if the user of the information bank 103 is not the user of the schedule adjustment system, the information of the user who is permitted to provide the information to the schedule adjustment system can be obtained from the information bank 103. It should be noted that step S404 may be carried out daily, weekly, at the timing when the information is changed, at the timing when the user requests it, or the like.

Next, the schedule adjustment server 102 acquires the past congestion information 605 from the external service provider 104 and stores it in the external service information holding unit 209 (S405).

Next, the schedule adjustment server 102 stores the basic user information 501, the user schedule 502, the implementation location information 503, and the past congestion information 605 stored in the user information holding unit 208 of the storage unit 202. Based on the information, the processing shown in FIG. 8 described later is performed to create the congestion information 701, which is stored in the congestion information holding unit 207. (S406). Note that step S406 may be performed daily, weekly, or at the timing when the user schedule is updated.

Next, the schedule adjustment server 102 acquires the shared office information 603, which will be described later, including the location and vacancy status of the facility from the external service provider 104, and stores it in the external service information holding unit 209 (S407). Note that step S407 may be performed daily, weekly, at the timing when information is changed, at the timing when there is a request from the user, or the like. In addition, the information to be acquired may be only the information that has been added or changed.

Next, the schedule adjustment server 102 performs the processes shown in steps S901 to S908 of FIG. 9, which will be described later, using the information stored in the storage unit 202, and the shared office is used as the congestion adjustment content for each user. Determine the working hours and new commuting hours. (S408) In step S408, daily, weekly, timing requested by the user, timing set by the user in advance, timing when the congestion rate of the congestion information 701 exceeds or falls below a certain value. Etc. may be carried out.

Next, the schedule adjustment server 102 presents the time zone for working in the shared office or the like and the new commuting time to the user using the terminal device 101 (S409). As a method of presenting to the user, a dedicated application, a Web browser, an application of another service, an add-on to the Web browser, or the like can be used.

Next, the user who uses the terminal device 101 decides to approve or reject the presented schedule, and transmits the result to the schedule adjustment server 102 (S410). It should be noted that this process may be performed at any time, such as on weekends, when the schedule is changed, or between work, according to the user's situation. As a method for the user to send the result to the schedule adjustment server 102, a dedicated application, a Web browser, an application of another service, an add-on to the Web browser, or the like can be used.

Next, the schedule adjustment server 102 performs the process of step S911 or S912 of FIG. 9 described later based on the result of approval or rejection indicated by the user, and the user schedule 502 and shared office information 603 described later Is updated (S411).

Finally, the schedule adjustment server 102 transmits to the external service provider 104 and the information bank 103 whether or not the shared office is used and the contents of the schedule change (S412, S413). The information bank 103 and the external service provider 104 store the received information.

Next, the data structure of the information held by the user information holding unit 208 of the schedule adjustment server 102 in this embodiment will be described with reference to FIG. The user basic information 501, the user schedule 502, and the implementation location information 503 shown in FIG. 5 are structural examples of user information for a certain user. This information exists in the database for at least the number of users. Further, each setting item may be automatically acquired from the information bank 103, or the user may access the schedule adjustment server 102 from the terminal device 101 and set it individually.

In FIG. 5, (a) basic user information 501 includes [address], [main means of commuting], [station closest to home], [station closest to work], [commuting route], [working style], [ Includes items such as [Standard Commuting Time], [Standard Boarding Time], [Regular Schedule], and [Intention to Change Schedule].

The [Address] item is an item in which the user's address is set. For example, the city, ward, town, village, town area, street address, building name, room number, etc. are set. A postal code or a prefecture name may be set.

[Main means of commuting] sets the means of transportation used for commuting. For example, items such as public transportation such as trains and buses, private cars, walking, and bicycles can be set.

[Station closest to home], [Station closest to work], and [Commuting route] are items to be set when public transportation such as train or bus is selected in [Main means of commuting], and the station name and route name are set. Set. If there are multiple offices, it can be set for each office. Also, if you select a private car, walk, bicycle, etc. as the main means of commuting, set the work address instead of [the nearest station to work], or set the road route as [commuting route]. Can be done.

[Working style] can set working styles such as flex, shift time, and discretionary work. In the case of flex, the core time can be set, and in the case of shift work, the time can be set for 2 shifts, 3 shifts, and each shift.

[Standard commuting time] sets the standard time for the user to commute, excluding non-standard times such as business trips, half-day holidays, late arrivals, and early departures. The figure shows an example in which it takes one hour to commute, the outbound route is from 7:30 to 8:30, and the return route is from 17:30 to 18:30. If there are multiple standard commuting hours in the shift time system, multiple registrations may be made.

[Standard boarding time] is the time when the user is commuting to work as [Standard commuting time] and is boarding a train or bus.

[Regular schedule] sets the name and time of the schedule and the type of repetition for the regular schedule that the user carries out on a daily, weekly, or monthly basis. This appointment may be a business appointment or a personal appointment. As for business, morning assembly, regular meetings, evening meetings, etc. can be considered. Personal regular schedules include pick-up and drop-off at nursery schools, hobby lessons (fitness, cooking classes, etc.), and long-term care schedules.

[Intention to change schedule] is an item to set the user's intention, such as wanting to move the commuting time forward or backward when changing the commuting time due to expected commuting congestion.

The [Main means of commuting], [Station closest to home], [Station closest to work], [Commuting route], and [Working style] can be selected by the user from the values preset by the server administrator. It may be possible to set.

In FIG. 5, (b) user schedule 502 includes items of [implementation period (start / end date)], [schedule name], and [implementation place name].

[Implementation period (start / end date)] sets the date and time for each schedule.

The name of the schedule entered by the user is set in [Schedule name]. The system may automatically input a regular schedule that can be inferred from the user basic information 501 such as commuting and fitness.

[Implementation location name] is set to the name of the implementation location of the schedule entered by the user. In the example, "meeting room A" which is the name of the conference room and "A sports gym" which is the name of the sports gym are exemplified. If there is no place to carry out, such as when [Schedule name] is "Commuting", it will not be set.

In FIG. 5, (c) implementation location information 503 includes items of [implementation location name] and [address].

[Implementation location name] is set to the implementation location name set in the user schedule 502.

[Address] is set to the location of the place of implementation. For example, a city, ward, town, town area, street address, building name, room number, etc. are set. A postal code or a prefecture name may be set. The latitude / longitude information acquired from the position information acquisition unit of the terminal device 101 held by the user may be input.

Next, the data structure of the information held by the external service information holding unit 209 of the schedule adjustment server 102 in this embodiment will be described with reference to FIG. As shown in FIG. 6, the external service information holding unit 209 includes operation information 601, operation plan information 602 (hereinafter, operation plan is referred to as a timetable), shared office information 603, vacancy status 604, and past congestion information 605. Information is retained.

In FIG. 6, (a) operation information 601 includes items of [train number], [capacity], [link to timetable], and [route name].

Information for distinguishing the operating trains is set in the [Train number] item. Although it is described as "0001A" and "0003B" in the figure, other numbers and symbols may be used, and it may be set in a different format for each railway company.

[Capacity] is set for each train. The capacity is set according to the vehicle formation, seats, and standing arrangement method.

[Link to timetable] is a reference of which timetable information 602 the train operates based on.

In [Route name], information on which route the train runs is set. When traveling on a plurality of routes by direct operation, a plurality of routes may be set.

In FIG. 6, (b) timetable information 602 includes items of [station name], [arrival time], and [departure time]. The timetable information 602 is an example of a data structure for a certain train. These data will exist in the database for at least the number of trains. The timetable information 602 has a unique identifier for each train, and by setting one identifier as [link to the timetable] in the operation information 601 it is possible to refer to the timetable information for each train.

[Station name] is the name of the station related to the arrival, departure, passage, etc. of the train.

[Arrival time] is the time when the train arrives at the station. If there is no arrival time due to passing or the like, a mark indicating that there is no data such as "*" is input.

[Departure time] is set to the time when the train departs from the station. The departure time may include the transit time. Although not provided in FIG. 6B, the transit time data may be provided separately from the departure time. According to the timetable information 602 of FIG. 6B, the first train at station A departs at 8:00, arrives at station B at 8:00:02, and departs station B at 8:02:50. It is shown. Although omitted as "..." in 601 and 602, there is actually a line indicating station information related to the arrival, departure, passage, etc. of the train.

In FIG. 6, (c) shared office information 603 includes items of [shared office name], [address], [link to availability], and [reservation site URL].

The name of the shared office is set in the [Shared office name] item. For example, "shared office A" or "shared office B" is set.

The item of [Address] is an item in which the location of the shared office is set. For example, a city, ward, town, village, town area, street address, building name, room number, etc. are set. A postal code or a prefecture name may be set.

The item of [Link to vacancy status] is set to refer to the vacancy status of each space in the shared office.

The URL of the reservation site of the shared office is set in the [Reservation site URL] item.

If the shared office publishes the API, the API information may be retained.

In FIG. 6, (d) vacancy status 604 includes items of [space ID], [vacancy date / time], and [space type]. Vacancy is an example of a structure for a shared office. There will be at least a few minutes of these data in the database for shared offices. The vacancy status has a unique identifier for each shared office, and by setting one identifier as [link to vacancy status] in the shared office information 603, the vacancy status for each shared office can be referred to. Can be done.

[Space ID] is a unique identifier assigned to each place where reservations can be made in a certain shared office or the like. For example, a space ID is assigned to each seat and each private room. The space ID may be different for each company that provides the shared office or the like.

[Vacancy date and time] is a daily list of available seats or private rooms with the space ID. For example, in FIG. 6D, it is shown that ROOM1 is vacant from 7:00 to 9:00 and 13:00 to 17:00 on December 1, 2018, and can be reserved.

In [Space type], the nature of the space with the space ID, such as a private room, a shared space, or a conference room, is set.

In FIG. 6, (e) past congestion information 605 includes items of [route name], [section], [congestion rate at peak time], and [peak time zone]. From this information, it is possible to acquire the congestion rate for each section and the time zone when congestion occurred.

In [Route name], the name of the route on which congestion information is shown is set.

[Section] sets the section of the station for which the congestion rate is measured. It is assumed that the section setting method may differ depending on the survey method and the survey company, and may be set at two adjacent stations or may be set across a plurality of stations.

[Peak-time congestion rate] indicates the peak-time congestion rate of the section on the route.
[Peak time zone] sets a time zone that becomes [congestion rate at peak time] in the relevant section of the route.

Next, the data structure of the information held by the congestion information holding unit 207 of the schedule adjustment server 102 in this embodiment will be described with reference to FIG. 7. As shown in FIG. 7, the congestion information holding unit 207 holds the information of the congestion information 701.

In FIG. 7, the congestion information 701 includes items of [route name], [train number], [section], [congestion rate], [departure time], [arrival time], and [change history]. Since this congestion information is created based on the user's schedule, different information is created for each date. In the example of the congestion information 701, the congestion information for a certain day is shown, but the congestion information holding unit holds the congestion information for a preset date, for example, one month.

Information for distinguishing the operating trains is set in the [Train number] item. In the example, "0001A" and "0002C" are written, but other numbers and symbols may be used, and they may be set in different formats for each railway company.

[Section] sets the section of the station for which the congestion rate is calculated. As a general rule, the section is set from the departure of a certain station to the next stop. For example, if the train stops at each station, adjacent stations are set, and if it is an express or limited express train, a station that straddles multiple stations is set. Whether it is an express train or a limited express train can be determined by whether or not there is a passing station in the timetable information 602.

[Congestion rate] indicates the congestion rate of the section on the route.
[Departure time] is set to the time when the train departs from the departure station of the section.
In [Arrival time], the time when the train arrives at the arrival station in the section is set.

[Change history] retains history information in which congestion information has been changed. In the first row of FIG. 7, it is shown that the congestion rate was 198 on March 18, 2019. The congestion information may be changed multiple times a day, and in that case, the change history is set by adding time.

Next, in FIG. 8, in step S406, the congestion status grasping processing unit 205 of the schedule adjustment server 102 in this embodiment sets the user basic information 501, the user schedule 502, various information of the implementation location information 503, and the operation information 601. The process of creating congestion information based on the timetable information 602 and the past congestion information 605 is shown.

In FIG. 8, first, the [main commuting means], [commuting route], [standard boarding time], and the schedule name of the user schedule 502, which are commuting information of the user basic information 501 of all users, are shown. Acquiring the "commuting" schedule (S801) The range of the schedule acquired in this step may be the period for which the congestion information is to be calculated, and for example, one week's worth or one month's worth is acquired.

Next, the operation information 601 and the timetable information 602 are acquired, and the [standard boarding time] and the [route information] of the users whose [main commuting means] is "train" are compared, and all the users , [Train number] of the train to be boarded, and the section to be boarded in the timetable information 602 (S802).

Next, the processes of steps S803 to S805 are performed for all the diamonds of the diamond information 602. That is, in step S803, the number of passengers between stations is calculated. Next, in step S804, the number of passengers obtained in step S803 is divided by the [capacity] for each train to calculate the congestion rate. If the number of users of the schedule adjustment system is smaller than the actual number of passengers, such as when the system has just started operating, the past congestion rate will be reflected at a fixed rate. As a reflection method, if information on the number of passengers in the past can be obtained, the ratio between the users of the schedule adjustment system and the number of passengers in the past can be obtained, and the congestion rate can be increased according to the calculated ratio. .. Further, even if the information on the actual number of passengers cannot be obtained, it can be reflected at a fixed ratio such as 30%. Next, in step S805, the congestion rate calculated in step S804 is added to the congestion information holding unit.

This process is performed daily or when the user's schedule is changed. Moreover, it is not necessary to perform all the calculations each time, and the difference is calculated as needed.

Next, in FIG. 9, the congestion adjustment processing unit 206 of the schedule adjustment server 102 in this embodiment shows various types of user basic information 501, user schedule 502, and implementation location information 503 in steps S408 to S413 of FIG. The process of adjusting the congestion based on the information and operation information 601, the timetable information 602, the shared office information 603, and the vacancy status 604 is shown.

In FIG. 9, first, the [main commuting means], [commuting route], and [standard boarding time] of the user basic information 501 held in the user information holding unit 208 of the user to be adjusted, and the user. Acquire the schedule 502 (S901).

Next, the congestion information held in the congestion information holding unit 207 is acquired (S902).

Next, compare the [standard boarding time], [commuting route], and congestion information of the user to be adjusted, and obtain all the congestion rates between stations where the train to be boarded stops. Next, it is determined whether or not the acquired congestion rate exceeds the threshold value (S903). For example, when the threshold value is 100%, it is determined that the congestion rate exceeds the threshold value when the congestion rate of each station exceeds 100%. The threshold value can be changed according to the route and the intention of the user. Further, before comparing the congestion rate and the threshold value, the congestion rate between stations where the train to be boarded may be averaged and the averaged congestion rate and the threshold value may be compared.

If the congestion rate does not exceed the threshold value, the congestion adjustment process is unnecessary and this process ends. When the congestion rate exceeds the threshold value, it is determined whether or not the commuting schedule can be changed to a time other than the congestion time zone with reference to the user schedule 502 (S904). For example, if you plan to commute between 7:30 and 8:30 and the meeting is scheduled for the day from 10:00 to 12:00, there is no schedule until 10:00, so the commuting time is between 9:00 and 10:00. Judge that it can be changed to. At the time of determination, the congestion rate of the commuting time of the change destination is confirmed again, and it is confirmed that the congestion rate is below the threshold value in the commuting time of the change destination. For example, if there is a meeting that starts at 9 o'clock, it is possible to change the commuting time from 7:30 to 8:30 from 8 o'clock to 9 o'clock, but in this case, even if it is changed, the congestion rate will fall below the threshold value. I can think that there is no such thing. In such a case, it is determined that the commuting schedule cannot be changed, and this process ends. In this example, the case of moving backward is shown, but as the intention of the user, refer to the items of [Regular schedule] and [Intention to change schedule] in Fig. 5 (a) Basic user information 501. If you wish to advance your commuting time, you may advance your commuting time.

Next, if it is determined that the commuting schedule can be changed to a time other than the busy hours, the commuting time candidate and the shared office usage time candidate are acquired from the external service information holding unit 209 (S905). This candidate acquires multiple candidates in consideration of the fact that the shared office is not available. First, the user schedule 502 and the [working style] of the user basic information 501 are referred to, and the time that can be pushed back most of the commuting time candidates is acquired. For example, if you normally commute between 7:30 and 8:30, but you work flextime and the core time is from 10 o'clock, the maximum commuting time is from 9 to 10 o'clock. Next, from 7:30 to 9:00, a time zone in which the congestion rate is below the threshold value when commuting to work every 30 minutes is extracted. For example, if you commute from 7:30 to 8:30 and from 8:00 to 9:00, the congestion rate will exceed the threshold, but if you commute from 8:30 to 9:30 and if you commute from 9:00 to 10:00. If the congestion rate is below the threshold value, 8:30 to 9:30 and 9 to 10 o'clock are acquired as commuting time candidates. Next, the shared office usage time candidate corresponding to the commuting time candidate is acquired. The shared office usage time is the time from the originally planned commuting time to the commuting time candidate. For example, if the originally planned commuting time is from 7:30 to 8:30, and the commuting time candidates are from 8:30 to 9:30 and from 9:00 to 10:00, the shared office usage time candidate is 7:00. It will be from half to 8:30 and from 7:30 to 9:00. In addition, when acquiring the commuting time candidate and the shared office usage time candidate, it may be arbitrarily set in increments of 10 minutes or 15 minutes instead of 30 minutes.

Next, the shared office information 603 and the vacancy status 604 stored in the external service information holding unit 209 are acquired (S906). In addition, when acquiring, if you want to advance the commuting time on the outbound route, and if the office is not open, acquire information on the shared office near the nearest station or the business trip destination, and set the commuting time on the outbound route. If you want to move backwards, get information about the shared office near the nearest station to your home. In addition, if you want to advance the commuting time on the return trip, get information on the shared office near the station closest to your home or near the planned implementation location after work, and if you want to advance the commuting time on the return trip, basically I will work at my place of employment, and if I plan to commute, I will get information about shared offices. The availability of the shared office is acquired from the external service information holding unit 209, but the latest information may be acquired from the external service provider 104.

Next, the acquired share office information 603 and vacancy status 604 are compared with the share office usage time candidates, and it is confirmed whether the share office is vacant at that time (S907).

If the shared office is not available, the congestion adjustment process is not possible, so this process ends. When the shared office is vacant, the user is presented with the shared office usage time candidate for which the shared office was vacant and the corresponding commuting time candidate as candidates for changing the schedule (S908). At this time, if there are multiple candidates, multiple candidates will be presented. In addition, confirm with the user in advance about the intention to use the shared office usage time, the candidate for the maximum shared office usage time, the candidate for the shared office usage time to be the time desired by the user, and the shared office usage time. The candidate that becomes the minimum may be presented preferentially.

Next, it is determined whether the user has approved it (S909), and if it is not approved, this process is completed. If approved, the commuting time candidate and the shared office usage time approved by the user are displayed in the shared office. A usage reservation is made, the schedule is changed, and the vacancy status of the vacancy status 604 held in the external service information holding unit 209 is updated (S910). The shared office usage reservation is made to the external service provider 104, and the fixed commuting time and shared office usage time are transmitted to the information bank 103 as a result of adjusting the schedule. This completes the schedule adjustment process.

If the commuting time change process described above is performed for all users, it is expected that some trains will have a reduced congestion rate and some trains will have an increased congestion rate. Therefore, in the following, the processing when the congestion rate is changed and the threshold value is newly exceeded will be described. It is assumed that this processing is performed by batch processing such as daily.

That is, after the processing up to step S902 in FIG. 9 is performed, the change history of the congestion information 701 is acquired, and the trains and sections where the congestion rate increases and the threshold value is exceeded, the departure time and the arrival time are obtained. Identify. Next, with reference to the user basic information 501 of all users, the user who uses the section is specified, the user schedule 502 of the specified user is acquired, and the commuting date exceeding the threshold value is obtained. Determine if the time zone overlaps the departure and arrival times that exceed the threshold. If they overlap, the congestion rate is changed at the timing when the user schedule is updated, so the processes after step S904 are performed.

Next, with reference to FIG. 10, an example of a screen for presenting the schedule adjustment result in this embodiment to the user is shown. As shown in FIG. 10, the user is presented with the schedule before and after the adjustment. In FIG. 10, as a pre-adjustment schedule, commute between 7:30 and 8:30, hold a meeting between 10 and 12 o'clock, commute between 17:30 and 18:30, and 18:30. The schedule for fitness is shown from.

The adjusted schedule is to work in a shared office from 7:30 to 9:00, commute between 9:00 and 10:00, hold meetings between 10:00 and 12:00, commute between 15:00 and 16:00, and from 16:00. The schedule for working in a shared office between 6:30 pm and fitness from 6:30 pm is shown.

As described above, according to this embodiment, commuting congestion can be predicted based on the schedules of all users, and commuting congestion can be avoided by working in a shared office or the like during busy hours. It is possible to provide a schedule adjustment device and a schedule adjustment program capable of performing schedule adjustment that can create time. This can be expected to have the effect of improving the quality of life of the user.

Although the examples have been described above, the present invention is not limited to the above-mentioned examples, and various modifications are included without departing from the technical idea or the main features thereof. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to those having all the described configurations.

101: Terminal equipment, 102: Schedule adjustment server, 103: Information bank, 104: External service provider, 105: Network such as the Internet, 201: Calculation unit, 202: Storage unit, 203: Communication unit, 204: Input / output unit, 205: Congestion status grasping processing unit, 206: Congestion adjustment processing unit, 207: Congestion information holding unit, 208: User information holding unit, 209: External service information holding unit, 301: Calculation unit, 302: Storage unit, 303: Communication unit, 304: Input / output unit, 305: Information cooperation unit, 306: Personal data management unit, 307: Personal data retention unit, 501: Basic user information, 502: User schedule, 503: Implementation location information, 601: Operation information, 602: timetable information, 603: shared office information, 604: availability, 605: past congestion information, 701: congestion information.

Claims

It is a schedule adjustment method of a schedule adjustment system consisting of a terminal device connected to the network, a schedule adjustment server, and an external service provider.
Based on the user's information from the terminal device and the past congestion status from the external service provider, the schedule adjustment server grasps the congestion status of the user during the commuting time zone.
The schedule adjustment is performed when the user is trying to commute in a crowded state and there is a vacancy in the shared office near the place before commuting based on the shared office information from the external service provider. A schedule adjustment method characterized in that the server performs congestion status adjustment processing.
The schedule adjustment method according to claim 1.
The grasping of the congestion situation is a schedule adjusting method characterized in that the congestion rate is calculated based on the schedules and commuting information of all the users of the schedule adjusting system and the congestion situation is grasped.
The schedule adjustment method according to claim 2.
A schedule adjustment method characterized in that when the number of users of the schedule adjustment system is small, the past congestion status is reflected in the congestion rate at a constant rate.
The schedule adjustment method according to claim 2.
The congestion status adjustment process is characterized in that, when the congestion rate is larger than the threshold value, the time to work in the shared office and the new commuting time are determined, and the schedule is adjusted so as to work in the shared office. Adjustment method.
The schedule adjustment method according to claim 4.
The congestion status adjustment process is a schedule adjustment method characterized in that the schedule is adjusted by confirming whether the shared office is available at the time of the shared office usage time candidate.
The schedule adjustment method according to claim 4.
A schedule adjustment method, characterized in that, when the congestion rate is changed by the congestion situation adjustment process and the changed congestion rate exceeds the threshold value, the schedule of the corresponding user is adjusted.
The schedule adjustment method according to claim 4.
The congestion status adjustment process is a schedule adjustment method characterized in that the schedule is adjusted based on the user's intention to change the schedule.
It is a schedule adjustment method of the schedule adjustment server that adjusts the schedule so as to avoid congestion. It acquires information on the user and the past congestion status, and based on the information on the user and the past congestion status, the user. If you are trying to commute to work while the users are crowded by grasping the congestion situation during the commuting time, and acquiring the shared office information, and based on the shared office information, near the place before commuting. A schedule adjustment method characterized in that when there is a vacancy in a shared office, the time to work in the shared office and a new commuting time are determined and a congestion status adjustment process is performed.
The schedule adjustment method according to claim 8.
The congestion status grasping is a schedule adjustment method characterized in that the congestion rate is calculated based on the schedules and commuting information of all the users of the schedule adjustment server and the congestion status is grasped.
The schedule adjustment method according to claim 9.
When the number of users of the schedule adjustment server is small, the schedule adjustment method is characterized in that the past congestion status is reflected in the congestion rate at a constant rate.
The schedule adjustment method according to claim 9.
The congestion status adjustment process is characterized in that, when the congestion rate is larger than the threshold value, the time to work in the shared office and the new commuting time are determined, and the schedule is adjusted so as to work in the shared office. Adjustment method.
The schedule adjustment method according to claim 11.
The congestion status adjustment process is a schedule adjustment method characterized in that the schedule is adjusted by confirming whether the shared office is available at the time of the shared office usage time candidate.
The schedule adjustment method according to claim 11.
A schedule adjustment method, characterized in that, when the congestion rate is changed by the congestion situation adjustment process and the changed congestion rate exceeds the threshold value, the schedule of the corresponding user is adjusted.
The schedule adjustment method according to claim 11.
The congestion status adjustment process is a schedule adjustment method characterized in that the schedule is adjusted based on the user's intention to change the schedule.
A storage medium that stores a schedule adjustment program in a schedule adjustment server that adjusts the schedule so as to avoid congestion.
The calculation unit,
Obtain information on users and past congestion status,
Based on the information on the user and the past congestion status, the congestion status of the user during the commuting time can be grasped.
Get shared office information,
When the user is trying to commute in a crowded state, and there is a vacancy in the shared office near the place before commuting based on the shared office information, the time to work at the shared office and A storage medium that stores a schedule adjustment program, which is characterized by determining a new commuting time and making it function to perform congestion status adjustment processing.