Chartered bus system, chartered bus processing method, and chartered bus processing program
The chartered bus system addresses the inefficiencies in existing reservation systems by integrating travel agency and bus operator devices to generate quotes based on both user and operator conditions, enabling efficient and rational bus allocation for large events.
Patent Information
- Application Number
- JP2024091039
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-06-04
- Publication Date
- 2025-12-16
AI Technical Summary
Existing chartered bus reservation systems do not consider the conditions of bus operators, leading to inefficient and manual processes for travel agencies when arranging chartered buses for large events, where multiple bus operators must be contacted and quotes compared, and there are limitations on vehicle availability.
A chartered bus system and method that includes a travel agency device and a bus operator device, with a storage means for operator conditions, an estimate generation means to satisfy both user and operator conditions, and an allocation means to allocate chartered buses to multiple operators, generating quotes based on allocated numbers.
Facilitates smooth, easy, and rational arrangements for chartered buses at large events by considering both user and operator conditions, reducing manual processes and optimizing vehicle allocation.
Smart Images

Figure 2025183111000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a chartered bus system, a chartered bus processing method, and a chartered bus processing program that can execute estimates and orders for chartered bus operations, particularly estimates and orders for large events. [Background technology]
[0002] BACKGROUND ART Chartered bus services (general chartered passenger automobile transportation businesses) in which buses are chartered and operated for a specified period of time for purposes such as company trips have been known for some time. When using a chartered bus service, many end users apply to a travel agency (including travel agents, tour operators, and travel brokers), which then applies for a chartered bus on behalf of the end user to a bus operator (also called a bus company). Specifically, the travel agency requests a quote from the bus operator based on the information (travel period, departure point, arrival point, etc.) provided by the end user at the time of application. Travel agencies can also request quotes from multiple bus operators (competitive quotes). This allows travel agencies to check which bus operators are cheaper and then make reservations for chartered buses.
[0003] Patent Document 1 discloses a chartered bus reservation system. In this chartered bus reservation system, a management server that accepts reservation requests from users is set up on the Internet, and users transmit their desired conditions, including their budget, to the management server via a terminal. When bus information that meets all of the desired conditions is provided by the management server, if the desired bus information is available, the users transmit reservation request information to the management server. The management server searches registered data for bus information that satisfies the user's desired conditions, transmits the bus information to the user's terminal if any, and when a reservation request is made from the terminal, notifies the terminal of the corresponding bus company of the reservation request via the Internet. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-373280 Summary of the Invention [Problem to be solved by the invention]
[0005] However, this charter bus reservation system takes into consideration the desired conditions of the user, but does not take into consideration the conditions of the bus operator at all. Furthermore, while the "users" in Patent Document 1 are end users, in reality, in many cases travel agencies act as agents to transact with bus operators. In addition, there are many travel agencies, and bus operators may want to vary the quote depending on their relationship with the travel agency, such as offering services to travel agency A at a lower or higher price than travel agency B. In addition, the Ministry of Land, Infrastructure, Transport and Tourism has set minimum fares and charges (unit price) for general chartered passenger vehicle transportation businesses, and bus operators are required to submit quotes that meet these regulations, so it was necessary to improve the conventional manual method. In particular, chartered buses are sometimes ordered by travel agencies and used as a means of transportation for large events such as the Olympics and the National Sports Festival, and in such cases, bus operators are required to secure a large number of vehicles. However, there is a limit to the number of vehicles that a single bus operator can arrange. This means that travel agencies must go through the tedious process of requesting (securing) vehicles from multiple bus operators, referring to their responses, determining which bus operator to use for each itinerary, and requesting quotes. Furthermore, travel agencies were manually handling all of these processes related to large-scale events using email, fax, telephone, etc., so there was room for improvement.
[0006] The present invention has been proposed to solve the problems associated with the conventional technology described above, and aims to provide a charter bus system, a charter bus processing method, and a charter bus processing program that enable smooth, easy, and rational arrangements for charter buses for large events. [Means for solving the problem]
[0007] In view of the above problems, one aspect of the present invention provides a chartered bus system for chartered bus services, comprising a travel agency device managed by an ordering travel agency and a bus operator device managed by an order-receiving bus operator, the chartered bus system comprising: a storage means for storing bus operator condition information indicating the bus operator's conditions that can be input by the bus operator device; an estimate generation means for generating estimate information that satisfies both the user's conditions and the bus operator's conditions based on user condition information indicating the user's conditions for a chartered bus that can be input by the travel agency device and the bus operator condition information; and an allocation means for allocating the specified number of chartered buses to multiple bus operators when the user condition information includes information indicating a large-scale project that requires the arrangement of a specific number of chartered buses, and the estimate generation means generates estimate information for each bus operator based on the number of buses allocated to each bus operator allocated by the allocation means.
[0008] In addition, another aspect of the present invention is a chartered bus processing method for chartered bus services, which uses a travel agency device managed by an ordering travel agency and a bus operator device managed by an order-receiving bus operator, and includes a first step of allocating a planned number of vehicles to multiple bus operators in advance in accordance with the operation of the travel agency device, a second step of allocating a specific number of vehicles to multiple bus operators based on the planned number of vehicles allocated in the first step, a third step of generating quotation request information for each bus operator based on the allocation results allocated in the second step, and a fourth step of sending the quotation request information to each bus operator device managed by each bus operator.
[0009] In addition, a chartered bus processing program according to another aspect of the present invention relates to a chartered bus service, and causes a travel agency device managed by an ordering travel agency, a bus operator device managed by an order-receiving bus operator, and connected information processing devices to function as a first allocation means for allocating a planned number of vehicles to multiple bus operators in advance in accordance with the operation of the travel agency device, a second allocation means for allocating a specific number of vehicles to multiple bus operators based on the planned number of vehicles allocated by the first allocation means, a quotation request information generation means for generating quotation request information for each bus operator based on the allocation result allocated by the second allocation means, and a quotation request means for transmitting the quotation request information to each bus operator device managed by each bus operator. [Effects of the Invention]
[0010] According to the present invention, arrangements for chartered buses for large-scale events can be made smoothly, easily, and rationally. [Brief explanation of the drawings]
[0011] [Figure 1] 1 is a schematic diagram of a chartered bus ordering system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a hardware configuration diagram of a server. [Figure 3] FIG. 2 is a hardware configuration diagram of a travel agency device. [Figure 4] FIG. 2 is a hardware configuration diagram of a bus operator device. [Figure 5] FIG. 2 is a functional configuration diagram of a server. [Figure 6] FIG. 2 is a diagram illustrating a database configuration. [Figure 7] 10 is a diagram showing an example of an AGT master. [Figure 8] 10 is a diagram illustrating an example of a bus operator master. [Figure 9] 10 is a diagram showing an example of a detailed vehicle rank master; [Figure 10] 10 is a diagram illustrating an example of a sales office master. [Figure 11] 10 is a diagram showing an example of an AGT group master. [Figure 12] 10 is a diagram showing an example of the AGT group fare master. [Figure 13] 10A is a diagram showing an example of a guide fee master A corresponding to actual driving time, and FIG. 10B is a diagram showing an example of a guide fee master B corresponding to detention time. [Figure 14] 10 is a diagram showing an example of a Hokkaido District Transport Bureau master. [Figure 15] 10 is a diagram illustrating an example of an outside business area master. [Figure 16] 10 is a diagram showing an example of a fare and charge master. [Figure 17] This is a chart showing an example of the AGT Group fare calendar. [Figure 18] 10 is a diagram showing an example of an estimate list. [Figure 19] 10 is a table showing an example of vehicle usage status information; [Figure 20] 10 is a table showing an example of OB setting information. [Figure 21] FIG. 10 is an explanatory diagram of the OB function. [Figure 22] 10 is a time chart showing a chartered bus processing method. [Figure 23] 10 is a flowchart showing a method for generating estimate information. [Figure 24] FIG. 10 is a diagram illustrating an example of a quote request input screen. [Figure 25] FIG. 10 is a diagram illustrating an example of an estimated itinerary. [Figure 26] 10 is a flowchart showing the procedure of arrangement processing. [Figure 27] 10 is a flowchart showing the procedure for changing and deleting. [Figure 28] FIG. 1 is a functional configuration diagram of a server 1 having a configuration capable of managing and providing guide information. [Figure 29] FIG. 10 is an explanatory diagram of a guide management sales office group. [Figure 30] 10 is an example of guide information. [Figure 31] 10 is a display example of the number of remaining buses and the number of remaining guides on a bus operator device. [Figure 32] 10 is a display example of vehicle availability and guide availability on a travel agency device. [Figure 33] FIG. 10 is a functional configuration diagram of a server that executes the process of arranging chartered buses for large-scale projects. [Figure 34] FIG. 1 is a sequence diagram showing the overall flow of the process for arranging a chartered bus for a large-scale project. [Figure 35] FIG. 10 is a diagram illustrating an example of a menu screen. [Figure 36] FIG. 10 is a diagram illustrating an example of a large-scale project registration screen. [Figure 37] FIG. 10 is a diagram illustrating an example of a registered large-scale project list screen. [Figure 38] FIG. 10 is a diagram illustrating an example of a required number registration screen. [Figure 39] FIG. 10 is a diagram showing an example of a supplier bus company selection (subscription) screen. [Figure 40] FIG. 10 is a diagram illustrating an example of an adjustment number registration screen. [Figure 41] Fig. 41(a) is an example of the number of vehicles adjustment request information sent to the bus operator device 3 for the AA bus, Fig. 41(b) is the number of vehicles adjustment request information sent to the bus operator device 3 for the BB bus, Fig. 41(c) is the number of vehicles adjustment request information sent to the bus operator device 3 for the CC bus, and Fig. 41(d) is the number of vehicles adjustment request information sent to the MM bus. [Figure 42] 10A and 10B are diagrams showing examples of response information: (a) is response information sent from the bus operator device 3 for the AA bus to the server 1, (b) is response information sent from the bus operator device 3 for the BB bus to the server 1, (c) is response information sent from the bus operator device 3 for the CC bus to the server 1, and (d) is response information sent from the bus operator device 3 for the MM bus to the server 1. [Figure 43] FIG. 10 is a diagram illustrating an example of an answer information screen. [Figure 44] FIG. 10 is a diagram illustrating an example of a planned number registration screen. [Figure 45]1 is a diagram showing an example of planned number information transmitted from server 1 to the bus operator side. (a) is the planned number information transmitted to bus operator device 3 for AA buses, (b) is the planned number information transmitted to bus operator device 3 for BB buses, (c) is the planned number information transmitted to bus operator device 3 for CC buses, and (d) is the planned number information transmitted to MM buses. [Figure 46] FIG. 10 is a diagram showing an example of a one-step itinerary registration screen. [Figure 47] FIG. 10 is a diagram showing an example of a second itinerary registration screen. [Figure 48] FIG. 10 is a diagram showing an example of an entire itinerary information screen for the XX International Convention (operating area: Okayama, Hiroshima, Kagawa). [Figure 49] FIG. 10 is a diagram showing an example of a screen for selecting a bus company to which a quote is requested. [Figure 50] 10A and 10B are diagrams showing examples of the quotation information input screen, where (a) shows the state at the time when information for the first trip is input, and (b) shows the state after quotation information for the entire trip related to the XX International Tournament has been input. [Figure 51] FIG. 10 is a diagram showing an example of an estimate response (summary information) screen. [Figure 52] FIG. 10 is a diagram illustrating an example of an order screen. [Figure 53] 10 is a flowchart showing a processing procedure for determining a bus business operator to which a quote is to be requested and the number of vehicles for which a quote is to be requested. [Figure 54] This is an example of aggregated data on the number of reservations per date for large (unspecified) vehicles at the XX International Convention. [Figure 55] This is an example of aggregated data on the estimated number of vehicles required for a large (unspecified) international tournament. [Figure 56] This is a diagram showing an example of a double pie chart in which the planned number ratio for each bus company is shown in the inner pie chart and the number of buses for which estimates have been requested for each bus company is shown in the outer pie chart. [Figure 57] FIG. 10 is a diagram showing a modified example of a large-scale project registration screen. DETAILED DESCRIPTION OF THE INVENTION
[0012] A preferred embodiment of the chartered bus ordering system (chartered bus system) of the present invention will be described.
[0013] FIG. 1 is a schematic diagram of a chartered bus ordering system according to one embodiment of the present invention. As shown in the figure, the chartered bus ordering system of this embodiment includes a server 1, a travel agency device 2, a bus operator device 3, and a map search site 4. The server 1 is connected via the Internet 9 to a travel agency device 2 managed by a travel agency and a bus operator device 3 managed by a bus operator (bus company), and by processing information received from the travel agency device 2 and the bus operator device 3, matches orders for chartered buses that meet both the end user conditions provided by each travel agency and the conditions of each bus operator. The server 1 and the travel agency device 2 can be connected to a map search site 4 via the Internet 9 . There are a plurality of travel agencies, each of which has at least one travel agency device 2. There are a plurality of bus operators, each of which has at least one bus operator device 3 . That is, the server 1 is communicably connected to a plurality of travel agency devices 2a, 2b, . . . and a plurality of bus operator devices 3a, 3b, .
[0014] FIG. 2 is a diagram showing the hardware configuration of the server 1. As shown in FIG. The server 1 includes a control unit 101 , a memory 102 , a storage unit 103 , and a communication device 104 . The control unit 101 is a processor that executes a program, controls each unit of the server 1, and performs processing to realize the functions of the server 1. The control unit 101 uses a CPU (Central Processing Unit). The memory 102 is a computer-readable recording medium that stores the program executed by the control unit 101 . For example, a RAM (Random Access Memory) and a ROM (Read Only Memory) are used for the memory 102. The ROM stores programs. The storage unit 103 is a computer-readable recording medium (storage) that stores various types of data. The storage unit 103 may be, for example, a hard disk drive (HDD) or a solid state drive (SSD). The communication device 104 is connected to the Internet 9 and performs data communication with the travel agency device 2 and the bus operator device 3 via the Internet 9 . The communication device 104 receives, for example, quotation request information from the travel agency device 2 and transmits quotation information to the travel agency device 2 and the bus operator device 3. Furthermore, the communication device 104 performs data communication with the map search site 4 via the Internet 9 (API linkage). The communication device 104 transmits, for example, the departure point, intermediate points, and destination to the map search site 4, and receives from the map search site 4 the distance and time it takes to travel from the departure point to the destination.
[0015] FIG. 3 is a diagram showing the hardware configuration of the travel agency device 2. The travel agency device 2 includes a control unit 201 , a memory 202 , a storage unit 203 , an operation device 204 , a display device 205 , and a communication device 206 . The control unit 201 is a processor that executes a program, controls each unit of the travel agency device 2, and performs processing to realize the functions of the travel agency device 2. The control unit 201 uses a CPU (Central Processing Unit). The memory 202 is a computer-readable recording medium that stores the programs executed by the control unit 201 . For example, a RAM (Random Access Memory) and a ROM (Read Only Memory) are used for the memory 202. The ROM stores programs. For example, a travel agency core program (a well-known travel industry package including business processes related to quotation and reservation of chartered buses) is stored, and a mechanism is provided for API linkage between this program and the program of server 1. The storage unit 203 is a computer-readable recording medium (storage) that stores various data. The storage unit 203 may be, for example, a hard disk drive (HDD) or a solid state drive (SSD). The operation device 204 is used to operate the travel agency device 2. The operation device 204 corresponds to, for example, a keyboard or mouse of a personal computer, or a touch panel of a smartphone or tablet terminal. The display device 205 displays various screens. For example, a liquid crystal display is used as the display device 205. The display device 205 may be integrated with a touch sensor to form a touch panel. The communication device 206 is connected to the Internet 9 and performs data communication with the server 1 via the Internet 9 . The communication device 206 transmits quotation request information to the server 1 and receives quotation information from the server 1 based on, for example, API cooperation. Furthermore, the communication device 206 performs data communication with the map search site 4 via the Internet 9 (API linkage). The communication device 104 receives map information, and the name and location information of a place specified on the map from the map search site 4 based on, for example, API cooperation. A web browser is pre-installed on the travel agency device 2.
[0016] FIG. 4 is a hardware configuration diagram of the bus operator device 3. As shown in FIG. The bus operator device 3 includes a control unit 301 , a memory 302 , a storage unit 303 , an operation device 304 , a display device 305 , and a communication device 306 . The control unit 301 is a processor that executes a program, controls each unit of the bus operator device 3, and performs processing to realize the functions of the bus operator device 3. The control unit 301 uses, for example, a CPU (Central Processing Unit). The memory 302 is a computer-readable recording medium that stores the program executed by the control unit 301 . For example, a RAM (Random Access Memory) and a ROM (Read Only Memory) are used for the memory 302. The ROM stores programs. For example, a traffic management program (a publicly known traffic management package capable of managing inventory of chartered buses, etc.) is stored, and this program and the program of the server 1 are linked via API. The storage unit 303 is a computer-readable recording medium (storage) that stores various data. The storage unit 303 may be, for example, a hard disk drive (HDD) or a solid state drive (SSD). The operation device 304 is used to operate the bus operator device 3. The operation device 304 corresponds to, for example, a keyboard and a mouse of a personal computer, or a touch panel of a smartphone or a tablet terminal. The display device 305 displays various screens. For example, a liquid crystal display is used as the display device 305. The display device 305 may be integrated with a touch sensor to form a touch panel. The communication device 306 performs data communication with the server 1 via the Internet 9 (API linkage). For example, based on API integration, the communication device 306 sends information such as the AGT group master 155, AGT group fare master 156, guide fee master 157, AGT group fare calendar 161, and OB setting information 163 to the server 1, and receives quotation information, quotation request information, etc. from the server 1. Furthermore, the communication device 306 performs data communication with the map search site 4 via the Internet 9 (API linkage). The communication device 306 receives map information, the name of a place specified on the map, and location information (for example, location information setting information included in the business office master 154) from the map search site 4 based on, for example, API cooperation. The bus operator device 3 has a web browser pre-installed.
[0017] FIG. 5 is a functional configuration diagram of the server 1. As shown in the figure, the server 1 is the core device of the chartered bus ordering system, and when it receives quotation request information for chartered bus services from each travel agency device 2, it automatically generates quotation information for bus operators that can accommodate the request. Subsequently, the server 1 can also perform processing related to ordering, such as reservation processing, arrangements, and changes and deletions of reservation and arrangement details. As shown in Figure 5, the server 1 of the chartered bus ordering system includes a storage means 111, an extraction means 112, a calculation means 113, an output means 114, a display control means 115, and a loan car management means 116.
[0018] The storage means 111 stores a DB (database) 150 . 6, the DB 150 is composed of an AGT master 151, a bus operator master 152, a vehicle class detail master 153, a sales office master 154, an AGT group master 155, an AGT group fare master 156, a guide fee master 157, a Hokkaido Regional Transport Bureau master 158, an outside sales area master 159, a fare and fee master 160, an AGT group fare calendar 161, vehicle usage status information 162, and OB setting information 163. The storage means 111 (DB 150) stores guide usage status information (not shown).
[0019] The AGT master 151 is master information that stores basic information about each travel agency (AGT). For example, as shown in FIG. 7, the travel agency, branch office, person in charge, telephone number, fax number, etc. are stored (managed) in association with the travel agency ID. The AGT master 151 allows the travel agency employee (including the manager, same below) to operate the travel agency device 2 to input and store the above information online.
[0020] The bus operator master 152 is master information that stores basic information about each bus operator. For example, as shown in FIG. 8, the bus company, sales office, person in charge, telephone number, fax number, etc. are stored in association with the bus company ID. Although the bus operator ID is not shown in the sales office master 154 (Figure 10), AGT group master 155 (Figure 11), AGT group fare master 156 (Figure 12), guide fare master 157 (Figure 13), AGT group fare calendar 161 (Figure 17), and OB setting information 163 (Figure 20), which will be described later, in reality, a bus operator ID corresponding to the bus operator is assigned. The bus company master 152 allows employees of the bus company to input and store the above information online by operating the bus company device 3.
[0021] The detailed vehicle rank master 153 is information indicating the detailed rank of the vehicle. For example, as shown in Figure 9, large vehicles are available in models with 12 rows of seats, equipped with a toilet, and models with fewer than 12 rows of seats. The detailed vehicle rank master 153 is information common to all bus operators and is stored in advance.
[0022] The business office master 154 is master information that stores information about the business offices of each bus company. For example, as shown in Figure 10, the bus operator, the relevant transport bureau, the operating area, the excluded operating area in the same prefecture, the additional operating area in neighboring prefectures, the location information (latitude, longitude), and the toll distance limit are linked and stored. "Jurisdictional Transport Bureau" means the Transport Bureau that has jurisdiction over the business office. The "sales area" is the prefecture to which the sales office belongs. However, areas outside the sales area, such as Hokkaido and Okinawa, are managed separately without regard to the sales area. Hokkaido is managed by each transport bureau (Figure 14), and areas outside the sales area, for example, Okinawa Prefecture, are managed separately by dividing the main island of Okinawa and its outlying islands (Figure 15). In the general chartered passenger automobile transportation business, the Ministry of Land, Infrastructure, Transport and Tourism stipulates that either the departure point or the arrival point must be within the bus operator's operating area (hereinafter also referred to as the "operating area regulation"). By referring to the operating office master 154, the Hokkaido Transport Bureau master 158, and the outside operating area master 159, it is possible to identify (extract) the operating offices and bus operators that satisfy the regulation (i.e., bus operators and their subordinate operating offices in operating areas that include the departure point or arrival point).
[0023] In addition, "excluded business areas of the same prefecture" refers to areas that fall within a prefecture, but are excluded from that prefecture. "Additional business areas of neighboring prefectures" refers to additional business areas that belong to neighboring prefectures of the target prefecture but are exceptionally included as business areas of the target prefecture. "Excluded business areas within the same prefecture" and "additional business areas within neighboring prefectures" are business areas that are outside the business area but are exceptionally recognized as being within the business area due to geographical reasons. "Toll road distance limit" indicates that the use of toll roads (expressways, etc.) will be restricted if the distance from the departure or arrival point to the office is less than the distance specified in the column. For example, in Figure 10, the toll distance limit for Office A is 10 km, so if the distance from the departure or arrival point to Office A is 10 km or less, the use of toll roads is restricted, and if the distance is 10 km or more, the use of toll roads is permitted. The business office master 154 allows the bus company employee to input and store the above information online by operating the bus company device 3.
[0024] The AGT group master 155 is information on the AGT group of each travel agency set by the bus company. For example, Figure 11(a) shows the setting information input by the bus operator device 3 of AA Bus, where travel agencies aa, bb, cc, and dd belong to group A, and travel agencies ee and ff belong to group B. Therefore, for example, when a request for a quote is made from aa company to AA Bus, the price is calculated based on the unit price set for group A (FIGS. 12, 17, etc.). Figure 11(b) shows the setting information input by the bus operator device 3 of BB Bus, where travel agency: cc company belongs to group A, travel agency: aa company belongs to group B, and travel agency: bb company belongs to group C. Therefore, for example, when a request for a quote is made from Company aa to BB Bus, the price is calculated based on the unit price set for Group B (FIGS. 12, 17, etc.). The AGT group master 155 can set (store) the above information online by an employee of the bus company operating the bus company device 3.
[0025] The AGT group fare master 156 is a fare and charge (unit price, etc.) based on the standard fare and charge set by the bus operator for each AGT group. That is, the AGT group fare master 156 includes information (regulation information) relating to regulations for the rental bus service. The bus company "AA Bus" portion of FIG. 12 is the fare and charges for each rank (A to C) of each AGT group (groups A to D) set by operating the bus company device 3 of AA Bus. As shown in the figure, for example, for Group A, Rank A (peak season, etc.), the kilometer-based fare (unit price per kilometer) for large vehicles is 210 yen, the hourly fare (unit price per hour) is 7,230 yen, the kilometer-based fare for replacement drivers is 40 yen, the hourly fare is 2,770 yen, the late-night and early-morning operation surcharge is the standard fare x 1 yen (see Figure 16), and the special vehicle surcharge is the standard fare x 2 yen (see Figure 16). Rank B of Group A (during normal times, etc.) has cheaper fares and charges than Rank A. Rank C of Group A (off-season, etc.) has cheaper fares and charges than Rank B.
[0026] For Group B, Rank A (peak season, etc.), the kilometer-based fare for large vehicles is 195 yen, the hourly fare is 6,675 yen, the kilometer-based fare for replacement drivers is 38 yen, the hourly fare is 2,558 yen, the late-night / early-morning operation surcharge is the standard fare x 1 yen, and the special vehicle surcharge is the standard fare x 2 yen. Rank B of Group B (under normal circumstances) has cheaper fares and charges than Rank A, and also cheaper fares and charges than Rank B of Group A. Rank C of Group B (off-season, etc.) has cheaper fares and charges than Rank B, and also cheaper fares and charges than Rank C of Group A.
[0027] For Group C, Rank A (peak season, etc.), the kilometer-based fare for large vehicles is 180 yen, the hourly fare is 6,120 yen, the kilometer-based fare for replacement drivers is 35 yen, the hourly fare is 2,345 yen, the late-night / early-morning operation surcharge is the standard fare x 1 yen, and the special vehicle surcharge is the standard fare x 2 yen. Rank B of Group C (normal times, etc.) has cheaper fares and charges than Rank A, and has cheaper fares and charges than Rank B of Group B. Rank C of Group C (off-season, etc.) has cheaper fares and charges than Rank B, and also cheaper fares and charges than Rank C of Group B.
[0028] The bus company "BB Bus" portion of FIG. 12 is the fare and charge for each rank of each AGT group set by operation of the bus company device 3 of BB Bus. As shown in the figure, for example, for Group A, Rank A (peak season, etc.), the kilometer-based fare (unit price per kilometer) for large vehicles is 200 yen, the hourly fare (unit price per hour) is 7,220 yen, the kilometer-based fare for replacement drivers is 39 yen, the hourly fare is 2,760 yen, the late-night and early-morning operation surcharge is the standard fare x 1 yen, and the special vehicle surcharge is the standard fare x 2 yen. For Group B, Rank B (normal periods), the kilometer-based fare (price per kilometer) for large vehicles is 170 yen, the hourly fare (price per hour) is 6,110 yen, the kilometer-based fare for replacement drivers is 34 yen, the hourly fare is 2,340 yen, the late-night and early-morning operation surcharge is the standard fare x 1 yen, and the special vehicle surcharge is the standard fare x 2 yen.
[0029] In this way, the AGT group fare master 156 (FIG. 12) allows the bus company employee to input and store the above information online by operating the bus company device 3. The fares and charges (unit prices) set in the AGT group fare master 156 are unit prices that satisfy the provisions of the fares and charges (FIG. 16) stipulated by the Ministry of Land, Infrastructure, Transport and Tourism. Therefore, any fare or charge can be set as long as it is within the range of the prescribed fare or charge (referred to as prescribed fare or charge), not limited to the above example.
[0030] The guide fee master 157 is a fee for bus guides set by the bus company according to ranks for each office and busy / unbusy periods, actual driving time, and on-duty time. The chartered bus system of this embodiment calculates the bus guide fee based on the "duty time." "Duty time" is the "actual vehicle time" plus the time for out-of-service driving and roll call inspection. For convenience, the following explains how to calculate the bus guide fee based on "actual driving time." However, if the bus guide fee is calculated based on "on-duty time," simply read "Guide fee master A in Figure 13(a)" below as "Guide fee master B in Figure 13(b)," and "actual driving time" below as "on-duty time." For example, in the guide fee master A of Figure 13(a), the guide fee for rank A (busy season, etc.) of AA Bus C Office is set to 10,000 yen if the actual driving time is 0 to less than 2 hours, 15,000 yen if the actual driving time is 2 to less than 5 hours, and 20,000 yen if the actual driving time is 5 to less than 24 hours. In addition, the guide fee for rank B (normal times, etc.) at BB Bus f Office is set at 18,000 yen for actual driving time of 5 hours or more but less than 24 hours. The guide fare master 157 allows the bus company employee to input and store the above information online by operating the bus company device 3.
[0031] The "rank" is not limited to three levels (A to C), but can be set to any level, including three levels or less, or four levels or more. For example, in the guide fee master B of FIG. 13(b), 10 ranks (A1 to A3, B1 to B4, C1 to C3) are set based on the "duration of time."
[0032] The Hokkaido Transport Bureau master 158 is master information that stores the association between branch offices belonging to the Hokkaido Transport Bureau and cities, towns, and villages. For example, as shown in FIG. 14, Sapporo City and Otaru City belong to the Sapporo Transport Branch Office, and Hakodate City and Hokuto City belong to the Hakodate Transport Branch Office. This means that if the departure point is Sapporo and the arrival point is Otaru, the departure and return destinations can be any office belonging to the Sapporo Transport Bureau. In addition, if the departure point is Sapporo and the arrival point is Hakodate, this means that the departure and return destinations can be offices belonging to the Sapporo Transport Branch Office or the Hakodate Transport Branch Office.
[0033] The outside business area master 159 classifies each city, town, village, and county in Okinawa prefecture as either the main island of Okinawa or an outlying island. For example, as shown in Figure 15, Naha City and Urasoe City belong to the main island of Okinawa, while Ishigaki Island belongs to an outlying island. For example, if the departure and arrival points are in Ishigaki City and the business office is located on the main island of Okinawa, operation is not permitted as it is outside the business area. The Hokkaido Regional Transport Bureau master data 158 and the outside business area master data 159 are stored in advance in the server 1.
[0034] The fare and charge master 160 is information indicating the specified fare and charge itself, and is stored in advance in the server 1. For example, as shown in Figure 16, the fares (unit price) for large vehicles in the Chugoku Transport Bureau's operating area are stipulated as follows: kilometer-based fares have a minimum limit of 150 yen / km, and time-based fares have a minimum limit of 5,010 yen / hour. In addition, with regard to the fees (unit price, etc.) for large vehicles within the Chugoku Transport Bureau's operating area, the minimum kilometer rate for replacement driver allocation fees is 30 yen / km, the minimum hourly rate is 1,920 yen / hour, the late-night and early-morning operation surcharge is 20% of the hourly fare and replacement driver allocation fee (hourly rate), and it is stipulated that a surcharge rate that takes into account the equipment, purchase price, etc. can be applied to the special vehicle surcharge.
[0035] The AGT group fare calendar 161 is information in which the bus operator assigns fare ranks for each AGT group to dates. Figure 17(a) shows the information set by AA Bus, where Group A on June 20th and 21st is set to Rank A. FIG. 17(b) shows the information set by BB Bus, where Group B on June 20th and 21st is set to Rank B. The check mark "Reply for loaner car required" indicates that "if a loaner car is used or there is a possibility of using one, an explanation (reply) to that effect is required." The bus operator checks the dates on which there is a possibility of using a loaner or chartered vehicle for operation. Note that, since both loaner and chartered vehicles involve using other commercial vehicles or vehicles of the bus operator, in this embodiment, the terms "loaner" and "chartered vehicle" are synonymous. For example, if you are receiving a reservation due to overbooking, if the vehicle is usually busy and overbooking is expected this year as well, if the vehicle is for a short period of time or is operated in conjunction with other projects and a replacement or hired vehicle is expected, check the appropriate dates and groups. In this case, specifically, the server 1 stores flag information (loan car required response flag) in association with the checked date and group. As a result, the server 1 can notify the travel agency that has requested the estimate by sending a message to the travel agency device 2 of the travel agency that "there is a possibility that a loaner car will be used" together with the estimate information. The AGT group fare calendar 161 can be set by an employee of each bus company operating the bus company device 3.
[0036] In this way, the storage means 111 stores bus operator condition information indicating the conditions of each bus operator that can be input (set) by each bus operator device 3. "Bus operator condition information" includes information regarding the price of a chartered bus, which varies for each travel agency depending on the bus operator's settings, such as information regarding the AGT group master 155, AGT group fare master 156, guide fee master 157, and AGT group fare calendar 161. Among these, the AGT group fare master 156 corresponds to the regulation information.
[0037] The extraction means 112 extracts bus operators from among multiple bus operators that can provide a rental bus that meets both the user's conditions and the bus operator's conditions, based on user condition information indicating the conditions of the user who uses a chartered bus, which can be input (set) by the travel agency device 2, and bus operator condition information stored by the storage means 111. "User condition information" is information on the conditions desired by the end user. Examples of "user condition information" include information regarding the travel agency that requested the quote, the duration of the trip, the number of people, the vehicle class (details of the vehicle class) and number of vehicles, whether a guide is required, whether overnight stays are required, the departure point (point of departure), intermediate points, arrival point (point of arrival), and the times of these points. The "user condition information" is information entered when requesting a quote by operating the travel agency device 2, and is included in the quote request information sent from the travel agency device 2 to the server 1 (see FIGS. 24 and 25).
[0038] For example, the extraction means 112 identifies the "point of departure" and "point of arrival" from the user condition information contained in the quotation request information sent from the travel agency device 2, and extracts bus operators that have offices within the operating area of either the "point of departure" or the "point of arrival" from the office master 154 (Figure 10). For example, if the departure point is Okayama Prefecture and the arrival point is Okayama Prefecture, bus operators (AA Bus and BB Bus) with offices in Okayama Prefecture are extracted, and if the departure point is Okayama Prefecture and the arrival point is Osaka Prefecture, bus operators (AA Bus) with offices in Okayama Prefecture or Osaka Prefecture are extracted (see Figure 10). This makes it possible to extract offices and bus operators that meet the operating area regulations.
[0039] The calculation means 113 calculates the price of a chartered bus from the bus company extracted by the extraction means 112 based on the "user condition information" and the "bus company condition information." An example of "user condition information" is quotation request information (travel period, vehicle class, departure point, arrival point, etc.), and an example of "bus operator condition information" is the AGT group fare master 156 or the AGT group fare calendar 161.
[0040] First, the sales office from which the goods will be shipped (returned) is determined. For example, let us explain the case where the travel agency requesting the quote is AA Company, the travel period is: June 20th to June 21st, 2022 (hereafter, the year will be omitted), the number of people: 20, the type of vehicle: large, the number of vehicles: 1, the guide: required, the overnight stay: not required (see Figure 24), the itinerary for the first day is: departure point: Kurashiki Station, stop 1: Kurashiki Bikan Historical Quarter, stop 2: Washuyama Observatory, stop 3: Kojima Jeans Street, arrival point: Okayama Hotel, and the itinerary for the second day is: departure point: Okayama Hotel, stop 1: Bizen Pottery Workshop, stop 2: Okayama Korakuen, arrival point: Kurashiki Station (see Figure 25). In this case, the server 1 extracts the AA bus and the BB bus by referring to the sales office master 154, and then selects the sales office closest to the departure point from among the sales offices belonging to the extracted AA bus and BB bus as the departure and return destinations. The term "closest" may be determined based on the distance between the two points that can be calculated by the map search site 4 based on the location information of each office and the location information of the departure and arrival points. The sales office closest to the destination may be selected as the departure and return destination. Alternatively, the sales office closest to the departure point may be selected as the departure destination, and the sales office closest to the arrival point may be selected as the return destination. In this embodiment, the closest office to the departure point is assumed to be office c for AA buses and office f for BB buses. As a result, Depot c is determined as the departure and return destination for AA buses, and Depot f is determined as the departure and return destination for BB buses.
[0041] The cost of chartering a bus consists of a "fare" and a "charge." First, we will explain how to calculate the "fare." There are two types of fares: distance fares, which are calculated by multiplying the kilometer fare (price per kilometer) by the distance traveled (km), and time fares, which are calculated by multiplying the hourly fare (price per hour) by the travel time (hours). "Distance traveled" includes "dead-way distance" and "actual vehicle distance," and "travel time" includes "dead-way time," "actual vehicle time," and "inspection time." "Forwarding" refers to moving a chartered bus from the departure office to the departure point, or moving a chartered bus that has arrived at the destination from the destination to the return office. "Actual vehicle" means moving a chartered bus with passengers on board from the departure point to the destination.
[0042] The method for calculating the deadhead distance and deadhead time will be explained. The calculation of the travel distance and travel time is performed in cooperation with a known map search site 4. Specifically, the server 1 activates the "route search function" of this site based on API cooperation with the map search site 4. The "route search function" allows you to input your departure and arrival locations and your mode of transportation to calculate the distance and travel time required to travel from your departure location to your destination using that mode of transportation. For the first day, the server 1 inputs the address of AA Bus's "Office c" as the departure location, "Kurashiki Station" as the arrival location, and "bus" as the means of transportation into the route search function. As a result, the route search function can obtain the travel distance and travel time when traveling on the road from Sales Office C to Kurashiki Station at a speed of 40 km / h (average travel speed of a bus). The server 1 acquires this travel distance and travel time from the map search site 4 as "travel distance" and "travel time", respectively. Specifically, the server 1 acquires, for the AA bus, the deadhead distance from the c office to Kurashiki station on the first day: 1.4 km and the deadhead time: 0.05 hours. Similarly, the server 1 also acquires the deadhead distance from Kurashiki Station to c office on the second day: 1.4 km, and the deadhead time: 0.05 hours. As a result, the server 1 acquires the following information regarding the AA bus: a deadhead distance of 2.8 km (=1.4 km+1.4 km) and a deadhead time of 0.1 hours (=0.05 hours+0.05 hours). Similarly, server 1 obtains the travel distance for BB Bus from "f Depot" to "Kurashiki Station" on the first day as 77 km and the travel time as 1.5 hours, and also obtains the travel distance from "Kurashiki Station" to "f Depot" on the second day as 77 km and the travel time as 1.5 hours. As a result, the server 1 acquires the following information for the BB bus: deadhead distance: 154 km (= 77 km + 77 km) and deadhead time: 3 hours (= 1.5 hours + 1.5 hours).
[0043] The method for calculating the actual driving distance and actual driving time will be explained. The actual driving distance and time are also calculated in cooperation with the map search site 4 (route search function). The "route search function" allows you to input your departure point, intermediate and destination locations, and mode of transportation to calculate the distance and travel time required to travel from your departure point to your destination, passing through the intermediate locations, using that mode of transportation. Server 1 inputs the departure point for day 1, "Kurashiki Station," stop 1, "Kurashiki Bikan Historical Quarter," stop 2, "Washiuyama Observatory," stop 3, "Kojima Jeans Street," destination, "Okayama Hotel," and mode of transportation, "bus," into the route search function. As a result, the server 1 obtains from the map search site 4 the "travel distance" and "travel time" when traveling from Kurashiki Station to Kurashiki Station Scenic Area to Washuyama Observatory to Kojima Jeans Street to Okayama Hotel at a speed of 40 km / h (average bus speed) as the "actual driving distance" and "actual driving time." Specifically, the server 1 acquires the actual driving distance from Kurashiki Station to Okayama Hotel on the first day: 40 km and the actual driving time: 6.5 hours. Similarly, the server 1 also acquires the actual driving distance from Okayama Hotel to Kurashiki Station on the second day: 30 km and the actual driving time: 5 hours. As a result, the server 1 acquires the actual driving distance: 70 km (= 40 km + 30 km) and the actual driving time: 11.5 hours (= 6.5 hours + 5 hours). In addition, since the actual travel distance and travel time are common to all bus operators, there is no need to calculate them separately for AA buses and BB buses.
[0044] The inspection time will be explained. The standard fares and charges are as follows: "The time from leaving the depot to entering the depot plus one hour for inspection of leaving the depot and one hour for inspection of returning to the depot, totalling two hours, is multiplied by the hourly fare." For this reason, in this embodiment, the "travel time" is defined as the deadhead time + actual vehicle time + inspection time (2 hours). Specifically, Server 1 calculates the travel time for AA buses to be 13.6 hours (= 0.1 hour of out-of-service time + 11.5 hours of actual vehicle time + 2 hours of inspection time), and calculates the travel time for BB buses to be 16.5 hours (= 3 hours of out-of-service time + 11.5 hours of actual vehicle time + 2 hours of inspection time).
[0045] As a result, server 1 calculates "travel distance: 72.8 km" (= 2.8 km out-of-service distance + 70 km actual vehicle distance) and "travel time: 13.6 hours" for AA bus, and "travel distance: 224 km" (= 154 km out-of-service distance + 70 km actual vehicle distance) and "travel time: 16.5 hours" for BB bus. Distances less than 10km will be rounded up to 10km, and driving times less than 30 minutes will be rounded down, and times 30 minutes or more will be rounded up to 1 hour. Therefore, for AA buses, the distance traveled is 80 km and the travel time is 14 hours, and for BB buses, the distance traveled is 224 km and the travel time is 17 hours.
[0046] The method for determining kilometer-based fares and time-based fares will be explained. The kilometer-based fare and time-based fare are determined by referring to the AGT group master 155 (FIG. 11), the AGT group fare calendar 161 (FIG. 17), and the AGT group fare master 156 (FIG. 12).
[0047] Regarding the AA bus, referring to the AGT group master 155 (FIG. 11(a)), the AGT group of company aa is set to "Group A." Referring to the AGT group fare calendar 161 (Figure 17(a)), group A is assigned rank A for both the travel period of June 20th and June 21st. If the travel period spans multiple days, the highest rank is applied. Therefore, the server 1 determines "kilometer-based fare (large vehicle): 210 yen" and "time-based fare (large vehicle): 7,230 yen" from the data corresponding to "Rank A" of "Group A" of "AA Bus" in the AGT group fare master 156 (Figure 12). In other words, for AA buses, the kilometre-based fare will be 210 yen and the hourly fare will be 7,230 yen.
[0048] Regarding the BB bus, referring to the AGT group master 155 (FIG. 11(b)), the AGT group of company aa is set to "Group B." Referring to the set AGT group fare calendar 161 (FIG. 17(b)), it is found that group B is assigned rank B for both June 20th and June 21st, which are the travel periods. Therefore, the server 1 determines "kilometer-based fare (large vehicle): 170 yen" and "time-based fare (large vehicle): 6110 yen" from the data corresponding to "Rank B" of "Group B" of "BB Bus" in the AGT group fare master 156 (Figure 12). In other words, for BB Bus, the kilometer-based fare will be 170 yen and the hourly fare will be 6,110 yen.
[0049] The server 1 calculates a distance fare by multiplying the determined kilometer-based fare by the travel distance, and calculates a time fare by multiplying the specified time-based fare by the travel time. Therefore, the distance and time fares for AA Bus and BB Bus are calculated as follows: "AA Bus distance fare" = 210 yen x 80km = 16,800 yen "AA Bus hourly fare" = 7,230 yen x 14 hours = 101,220 yen Therefore, the AA Bus fare is calculated as 118,020 yen (= 16,800 yen + 101,220 yen). "BB Bus distance fare" = 170 yen x 224 km = 38,080 yen "BB Bus hourly fare" = 6,110 yen x 17 hours = 103,870 yen Therefore, the BB Bus fare is calculated as 141,950 yen (= 38,080 yen + 103,870 yen).
[0050] Next, we will explain how fees are calculated and determined. The charges include "surcharge for late-night and early-morning operations," "substitute driver charge," "special vehicle charge," "guide charge," and "paid return shipping charge."
[0051] Regarding the "surcharge for late-night and early-morning operations," the standard fares and charges also state that "for operations between 22:00 and 5:00, a 20% surcharge will be applied." Therefore, if the operating hours identified from the user condition information overlap with the time period between 22:00 and 5:00, a late-night / early-morning operating surcharge can be included in the price of the chartered bus. In this case, as shown in Figure 17, the rank of the AGT group on the operation day assigned to the AGT group fare calendar 161 is identified, and the "late night / early morning operation surcharge" corresponding to that rank is extracted from the AGT group fare master 156 (Figure 12). For example, if a travel agency belonging to Group A requests AA Bus for a quote for a bus operating from 22:00 to 5:00 on June 26th, Server 1 can identify that the rank of Group A's operating day (6 / 26) is Rank A (see Figure 17(a)), and therefore determines the "late night / early morning operating surcharge" to be "prescribed fare x 1 yen" (see Figure 12).
[0052] Regarding the "replacement driver fee," the prescribed fares and charges also include a provision that "when a replacement driver is assigned for safe driving in long-distance, long-duration, or night-time operations, the fees published by each transport bureau shall apply." The "fees published by each transport bureau" are amounts equal to or greater than the lower limit of the "kilometer-based fee" and "hourly fee" in the fare and fee master 160 (FIG. 16). Therefore, if the travel distance exceeds a specific distance (specified 600 km), if the travel time exceeds a specific time (specified 16 hours), or if the operating hours specified by the itinerary are early morning or late night (specified 10 pm to 5 am), a "substitute driver fee" can be included in the price of the chartered bus. In this case, the server 1 identifies the rank of the AGT group on the operation day assigned to the AGT group fare calendar 161 (Figure 17) and extracts the "replacement driver placement fee" corresponding to the identified rank from the AGT group fare master 156 (Figure 12). For example, if a travel agency belonging to Group A requests AA Bus for a quote for a long-distance trip on June 26th, Server 1 determines that the rank of Group A's trip date (6 / 26) is Rank A (see Figure 17), and therefore determines the "kilometer-based fare = 40 yen" and "hourly fare = 2,770 yen." Therefore, Server 1 calculates the "replacement driver fee" as the sum (45,139 yen) of the distance traveled (82.8 km) multiplied by the kilometer-based fee of 40 yen (3,312 yen) and the driving time (15.1 hours) multiplied by the hourly fee of 2,770 yen (41,827 yen).
[0053] The standard fares and charges stipulate that when providing special vehicles such as salon cars and buses with lifts, a surcharge can be applied that takes into account the equipment, purchase price, etc. Therefore, if the vehicle class included in the user condition information is a special vehicle, a special vehicle surcharge can be included in the price of the chartered bus. For example, if a travel agency belonging to Group A requests AA Bus for a quote on the conditions for operating a special vehicle on June 26th, Server 1 can determine that the rank of Group A on the operating date (6 / 26) is Rank A (see Figure 17(a)), and therefore determines the "special vehicle surcharge" to be x2 yen (see Figure 12). This "special vehicle surcharge" is a charge to which a predetermined surcharge rate is applied, taking into account the equipment, purchase price, etc. (see Figure 16).
[0054] "Guide fee" is the fee that can be applied if you request a bus guide. Specifically, if the user condition information includes "guide: required" (see FIG. 24), the guide fee can be included in the price of the chartered bus. Note that "Guide: Required" indicates that one guide is required, but multiple guides can also be requested. In this case, for example, an input field for the number of guides required can be provided for each vehicle class, and the required number of guides can be entered in that input field. In this case, the server 1 determines the guide fee by referring to the guide fee master 157 (FIG. 13). The guide fee is determined for each bus operator's office according to its rank, which indicates busy or slow periods, and the amount of time the bus is actually in operation. In this embodiment, "commitment time" is used instead of "actual vehicle time." Specifically, it is calculated as "commitment time = actual vehicle time + deadheading time + time before and after leaving the depot (roll call inspection time)." The "time before and after leaving the depot" can be set for each bus company. For this reason, for example, the "time before and after leaving the depot" may be linked to each bus company and stored in advance in the storage unit 103 of the server 1 in response to an operation of the bus company device 3. This allows the server 1 to determine the "detention time" (= "actual vehicle time" + "depot time" + "time before and after leaving the depot") by calculation. For convenience, the ranking according to busy and slow periods will be explained as being the same as the AGT Group Fare Calendar 161 (Figure 17), but it is also possible to set up a calendar that assigns ranks to dates and use it as a reference. In this example, the "user condition information" indicates that a guide is required, a quote is requested from a travel agency (company aa) belonging to group A, and the operation dates are June 20th and 21st. Referring to the AGT Group Fare Calendar 161 (Figure 17(a)), for AA Bus, the rank of aa Company (Group A) on June 20th and 21st is identified as Rank A. Therefore, the server 1 refers to the guide fee master 157 (Figure 13) and determines a guide fee of 20,000 yen because the actual driving time on the first day of the guide was 6.5 hours (more than 5 hours but less than 24 hours), and determines a guide fee of 20,000 yen because the actual driving time on the second day was 5 hours (more than 5 hours but less than 24 hours). Therefore, the server 1 calculates the guide fee for the AA bus as 40,000 yen (= 20,000 yen + 20,000 yen). On the other hand, with regard to BB Bus, referring to the AGT Group Fare Calendar 161 (Figure 17(b)), the rank of Company aa (Group B) on June 20th and 21st is identified as Rank B. Therefore, the server 1 refers to the guide fee master 157 (Figure 13) and determines the guide fee to be 18,000 yen because the actual driving time on the first day was 6.5 hours (more than 5 hours but less than 24 hours), and determines the guide fee to be 18,000 yen because the actual driving time on the second day was 5 hours (more than 5 hours but less than 24 hours). Therefore, the server 1 calculates the guide fee for the BB bus to be 36,000 yen (= 18,000 yen + 18,000 yen). Specific examples of applying "constraint time" will be omitted.
[0055] "Paid return shipping fee" can be included in the price when a toll road (such as an expressway) is used and the return distance (the distance from the delivery office to the departure point or the distance from the arrival point to the return office) exceeds a specified distance (the toll return distance limit). The "predetermined distance (paid transport distance limit)" is determined for each sales office in the sales office master 154 (FIG. 10). Therefore, if the destination office is AA Bus C Office, the paid return distance limit is 10 km, so if the return distance exceeds 10 km, the return fee can be charged. In this example, the distance from AA Bus C Office to the departure and arrival points is 1.4 km (less than 10 km), so the paid return shipping fee cannot be recorded. Here, whether to use a toll road is a matter that the end user must choose. For this reason, if the delivery distance exceeds a predetermined distance (a toll delivery distance limit), the server 1 may, for example, notify the estimate information by including an approximate "toll delivery fee" if a toll road is used.
[0056] This allows the freight and charges to be calculated, and quotation information can be generated based on these calculation results. As a result, estimate information regarding the cost of chartered buses can be generated for the two bus companies, AA Bus and BB Bus. In the above example, we have explained the case where there are two bus operators (i.e., AA Bus and BB Bus are requested to make a quote), but there may be three or more bus operators (three or more companies are requested to make a quote).
[0057] The output means 114 outputs the estimate information regarding the price calculated by the calculation means 113 to the travel agency device 2. Specifically, a list of quotation information is generated, and the quotation list is sent to the travel agency device 2 of the travel agency that has requested the quotation. This allows the travel agency that has requested the quotation to display, print, or transmit the quotation list (competitive quotation information) to the user terminal on the travel agency device 2. The server 1 also transmits the estimate list to the bus operator device 3. This allows the bus operator to check the estimate results. FIG. 18 is an example of an estimate list. The top column shows the estimate information for the AA bus, and the bottom column shows the estimate information for the BB bus.
[0058] As described above, the estimate information may be generated automatically, but manual processing may also be involved. For example, the calculation of the fee may be performed and the estimate information may be transmitted to the bus operator device 3 so that the bus operator can check it in advance. If the confirmation shows that no corrections are necessary, the quotation information can be sent to the travel agency device 2 by performing an operation to that effect, and if corrections are necessary, the corrections can be made and the corrected quotation information can be sent to the travel agency device 2.
[0059] (About the overbooking function) It is preferable for charter bus services to accept quotes and reservations for more buses than they actually have in stock. In the past, the operation management package maintained a limit on the number of OB vehicles, but was unable to accurately manage the number of OB vehicles. For this reason, the chartered bus ordering system of this embodiment is equipped with an overbooking function (OB function) that allows the number of overbooking (OB) vehicles to be set using replacement vehicles or hired vehicles to be set by date, vehicle class details, and business area. In addition, a "substitute vehicle" refers to the operation of a vehicle managed by another office of the same bus company, and a "chartered vehicle" refers to the operation of a vehicle managed by another bus company.
[0060] FIG. 19 is an example of vehicle utilization status information 162 relating to occupancy information of chartered buses at a bus company. The information shown in the figure is acquired by the server 1 through API cooperation with the operation management package of the bus operator device 3 of AA Bus. The acquired vehicle usage status information 162 is stored in the storage means 111 every time it is acquired. Therefore, the server 1 always stores the latest vehicle usage status information 162. FIG. 19 is an example of vehicle usage status information 162 of the offices (four offices: office a, office b, office c, and office d) belonging to the AA Bus business area: Okayama Prefecture on August 1st. As shown in the figure, the vehicle usage status information 162 is composed of bus company, date, office, vehicle class details, total number of vehicles, number of reserved vehicles, number of OB reserved vehicles, and number of charter reserved vehicles. "Total number" is the total number of rental buses in stock managed by the sales office. "Number of reserved buses" is the number of buses for hire that have been reserved (arranged). "Number of OB reserved vehicles" is the number of reserved vehicles including overbookings. "Number of vehicles reserved for hire" is the number of vehicles reserved, including overbooking due to hire.
[0061] FIG. 20 is a table showing an example of the OB setting information, and FIG. 21 is an explanatory diagram of the OB function. FIG. 20 shows the number of large (12-row) OB buses set for each office in the AA Bus business area "Okayama Prefecture" on August 1st. As shown in Figure 21(a), if two units have been reserved at each of four sales offices, each with a total of two units, a sales office a, b, and c, and only sales office d has zero reservations (number of available units: 2), an estimate will be automatically generated with sales office d as the shipping destination. Here, the number of OB vehicles set is set for each business area. Therefore, as shown in FIG. 20, when the number of OB vehicles set for the business area: Okayama prefecture is set to 10, each business office belonging to Okayama prefecture can freely OB within the range of 10 vehicles. For example, as shown in Figure 21(b), if the number of OB-set vehicles is 10 and the number of reserved vehicles is 3 for office a, 7 for office b, 4 for office c, and 2 for office d, the number of available vehicles at each office is zero, but the number of reserved OB vehicles is 1 for office a, 5 for office b, and 2 for office c, for a total of 8 vehicles, so the remaining 2 OBs are possible in this sales area. In this case, the number of available units at each sales office is set to "2" based on the number of available units taking into account the number of OB units set. This means that each office will appear to have only two available vehicles, so the office closest to the departure point can be used as the departure destination. The number of OB vehicles set in FIGS. 21(b) and 21(c) is assumed to be OB vehicles (that is, replacement vehicles) managed within the bus company.
[0062] FIG. 21(c) shows a case where, after FIG. 21(b), two reservations for vehicles are added with the delivery destination being Sales Office c. In this case, the actual number of available vehicles is zero, and even when the number of OB set vehicles is taken into consideration, the number of available vehicles is still zero.
[0063] The OB function when OB is performed using a loaner car and a chartered car will be described with reference to FIG. 21(d). FIG. 21(d) is an example in which the number of OB-set vehicles is 15, which is five more than in FIG. 21(c). These five vehicles are assumed to be chartered vehicles. Therefore, as shown in the figure, even if two vehicles are reserved with delivery to Sales Office B, a chartered vehicle can be allocated, and the remaining three vehicles can be allocated by OB. In this case, the number of available vehicles at each sales office is set to "3" based on the number of available vehicles taking into account the number of OB-set vehicles. This means that each office will appear to have three available vehicles, so the office closest to the departure point can be used as the departure destination.
[0064] The reason why the number of available vehicles, taking into account the number of OB vehicles set, is allocated to each sales office in this way is as follows. As a premise, the server 1 transmits occupancy information of each sales office to the travel agency device 2 in response to a request from the travel agency device 2, and causes the travel agency device 2 to display the information (Web display). That is, the server 1 includes a display control means 115 that causes the travel agency device 2 to display the number of available buses for hire for each office of the bus company that manages the chartered buses. However, for simplicity's sake, the availability of the OB function and the number of vehicles that can be OB are not notified. For this reason, travel agency employees may mistakenly assume that reservations are unavailable simply by looking at the number of available spaces. It is also possible to display the number of OB vehicles by sales area, but in that case it is difficult to know which sales office the vehicle will be shipped to. Therefore, in the chartered bus ordering system of this embodiment, the number of available buses is allocated to each office, taking into account the number of OB buses set, so that such problems do not occur. Specifically, the server 1 is equipped with a rental car management means 116 that manages rental cars for each business area consisting of one or more offices, and the display control means 115 allocates the number of available rental cars to each office if there are available rental cars in the business area, even if there are no available cars at a specific office among the offices that make up the business area, and displays this number as the number of available rental buses on the travel agency device 2.
[0065] (Charter bus handling method) The chartered bus processing method will be described with reference to FIG. FIG. 22 is a sequence diagram showing the processing procedure of the chartered bus processing method of this embodiment. It is assumed that each travel agency device 2 has a travel business package installed, and each bus operator device 3 has an operation management package installed. It is also assumed that the DB 150 (FIG. 6), the AGT group fare calendar 161, the OB setting information 163, etc. are stored in the server 1 in advance. The chartered bus processing program on server 1 and the travel agency package on each travel agency device 2 are linked via an API, allowing server 1 to share some of the functions of each travel agency package (such as applying for a chartered bus and displaying quotation information). In addition, the chartered bus processing program on server 1 and the operation management package of each bus operator device 3 are linked via API, which allows server 1 to share some of the functions of each operation management package (obtaining the total number of vehicles at the office, the number of available vehicles, etc.).
[0066] As shown in FIG. 22, it is assumed that a quotation request for a chartered bus (quote request information is input) is made to the travel agency device 2 (S11). 24 and 25 are diagrams showing examples of input screens (web screens) for quotation request information. The quotation request information input screen can be displayed on the server 1 by accessing a predetermined URL from the travel agency device 2. As shown in these figures, when requesting a quote, you will enter information indicating the travel agency (Company AA) that is requesting the quote, the travel period (June 20th to June 21st), the number of people (20 people), the size of the vehicle (large), the number of vehicles (1), whether a guide is required (yes), whether overnight stays are required (no), and the itinerary for one trip (Day 1: departure point: Kurashiki Station, stop 1: Kurashiki Bikan Historical Quarter, stop 2: Washuyama Observatory, stop 3: Kojima Jeans Street, arrival point: Okayama Hotel; Day 2: departure point: Okayama Hotel, stop 1: Bizen Pottery Workshop, stop 2: Okayama Korakuen, arrival point: Kurashiki Station). 24 and 25 show the screens that appear after the quotation request information has been entered. The travel agency name, telephone number, branch office, and person in charge are input by quoting from the AGT master 151 (FIG. 7) when the travel agency ID is input at login. The "travel agency system reservation record number" is a unique number assigned to each case. Tour name: "ABC Company Company Trip" is text information. Travel period: "June 20th" to "June 21st" can be selected from the calendar. Number of people: "20 people" is text information. Vehicle class: "Large" is the information selected in the combo box. Vehicle classes include large (12 rows, with toilet, etc.), medium, small, and special (salon car, lift-equipped bus). Number of units: "1 unit" is text information. The number of vehicles is judged to be correct or incorrect in relation to the vehicle class and the number of people. For example, if the maximum number of people allowed for a large vehicle is 24, then 24 people x number of vehicles: 1 vehicle = 24 people, and the number of people is "20 people" or more, so it is judged to be "correct." If the number is incorrect, an error message or a message prompting re-entry can be displayed. Estimate type: "Estimate / reservation required" is information selected by the radio button. Estimate types include estimate / reservation required and estimate / no reservation required. Travel type: "General" is information selected by the combo box. The travel type includes general, school education law application, welfare law application, and recruitment. Guide: "Required" is the information selected by the radio button. There are two types of guide: required and not required. Overnight stay: "No need" is information selected by the radio button. Overnight stay can be either required or not required. When you select "Next" on the first page of the quotation request input screen (Figure 24), the screen will transition to the quotation itinerary on the second page (Figure 25).
[0067] On the Estimated Itinerary screen (Figure 25), enter the itinerary for June 20th (first day) and the itinerary (details) for June 21st (second day). Specifically, enter the departure time and location names for the "departure point," "transit point," and "arrival point" for the first and second days. The departure time and location name can be easily entered by linking with the map search site 4. For example, on the first day, the itinerary is Kurashiki Station (starting point) - Kurashiki Bikan Historical Quarter (way point 1) - Washuyama Observatory (way point 2) - Kojima Jeans Street (way point 3) - Okayama Hotel (arrival point), and the names of each location can be entered by specifying the point on the map. When a place name is input, the travel agency device 2 receives the location information (latitude, longitude) of the place name from the map search site 4, and stores the information in association with the corresponding departure point, intermediate point, and arrival point. The departure time is entered manually. In this case, based on API cooperation with the map search site 4, it is possible to judge whether the departure time is appropriate (to judge whether the entered departure time will not allow the bus to arrive at the stopover or destination by that time), and if it is judged to be inappropriate, to display a message to that effect and to prompt the user to re-enter the time. Furthermore, by linking with the API, it is possible to automatically input the departure time from each stopover and arrival point simply by inputting the departure time from the departure point. Specifically, the map search site 4 calculates the travel time from the departure point to the stopover, between stopovers, and from the stopover to the arrival point, and the calculated time, taking into account rest times, is input as the departure time for each stopover and arrival point. In addition, you can automatically enter the departure times of the stopover points by simply entering the departure times of the departure point and the arrival point.
[0068] On the second day, enter the departure time and name of each point: Okayama Hotel (starting point) - Bizen Pottery Workshop (stopover 1) - Okayama Korakuen (stopover 2) - Kurashiki Station (arrival point). In addition to the above items, a memo section can also be provided. In addition, in the case of a manual quotation request, it is possible to attach a quotation schedule (PDF or other image file) in addition to the quotation schedule described above. After the quotation request information is input, the travel agency device 2 transmits the quotation request information to the server 1. That is, all the information displayed in FIGS. 24 and 25 is sent to the server 1.
[0069] When the server 1 receives the quotation request information from the travel agency device 2, it generates quotation information (S12).
[0070] In generating estimate information, as shown in FIG. 23, first, a bus company is identified (S21). Specifically, the server 1 refers to the estimate request information and identifies bus operators that have offices at the departure and arrival points based on the office master 154 (FIG. 10). In this example, a bus company whose business area is Okayama Prefecture is identified. If multiple bus companies are identified, estimate information for the multiple bus companies will be generated. In this example, the AA bus and the BB bus are identified. If there is no corresponding bus operator, information to that effect is sent to the travel agency device 2.
[0071] Next, the business offices to which the goods are to be delivered and returned are identified (S22). Specifically, based on the location information of the departure point and the location information of each office, the nearest office closest to the departure point is identified as the departure destination, and based on the location information of the arrival point and the location information of each office, the nearest office closest to the arrival point is identified as the return destination.
[0072] However, the destination and return offices will be identified based on the occupancy information of each office. This is because there may not be any available units at the nearest sales office. Therefore, if the nearest branch office has available units, the nearest branch office will identify the branch office to which the vehicle is to be shipped or returned, but if the nearest branch office does not have available units, it will then identify other branches in its service area that have available units. Furthermore, if there are no available vehicles at any of the sales offices within the sales area, it is possible to use loaner vehicles or chartered vehicles managed by the sales area (OB function), and in this case, the nearest sales office can be identified as the sales office from which the vehicle will leave or return (see Figure 21, etc.). As for AA Bus, since the departure point and arrival point are Kurashiki Station, based on the location information of each AA Bus office and the location information of Kurashiki Station, office c is identified as the nearest office. Since BB Bus only has f office, f office is identified.
[0073] Next, the travel distance and travel time are calculated (S23). The travel distance is the sum of the deadhead distance and the actual vehicle distance, and the travel time is the sum of the deadhead time, the actual vehicle time, and the inspection time. In this example, as described above, the travel distance of the AA bus is calculated to be 80 km and the travel time is calculated to be 14 hours. The BB bus's travel distance is calculated to be 224 km and its travel time is calculated to be 17 hours.
[0074] Next, the kilometer-based fare and the time-based fare are determined (S24). In other words, the unit price is determined as a kilometer fare, which is the fare per kilometer, and an hourly fare, which is the fare per hour. These have a minimum fare and charge limit (see Figure 16). For this reason, the chartered bus ordering system of this embodiment is designed to comply with these regulations and allows the bus operator to set a rank for each travel agency (see Figure 12), and further allows the bus operator to set this rank for each date (see Figure 17). This allows bus operators to set unit prices that take into account their relationship with travel agencies (for example, based on past transactions, they may be willing to accept CC Bus even if it is cheaper), or unit prices that correspond to busy and slow periods such as weekdays, holidays, and seasons (for example, they may want to offer higher prices during busy periods than during slow periods). This will make it possible to set prices that take into account the intentions and wishes of bus operators. In this example, as described above, the kilometer-based fare for AA buses is determined to be 210 yen, and the time-based fare is determined to be 7,230 yen. For BB Bus, the kilometer-based fare will be 170 yen and the time-based fare will be 6,110 yen.
[0075] Next, the fare is calculated (S25). The fare is calculated based on the distance and time calculated in S23 and the kilometer-based fare and time-based fare determined in S24. Specifically, the distance fare is calculated by multiplying the distance traveled by the kilometer-based fare, the hourly fare is calculated by multiplying the travel time by the hourly fare, and the fare is calculated by adding up these calculation results. In this example, for AA Bus, the distance fare is calculated to be 16,800 yen and the hourly fare is calculated to be 101,220 yen, resulting in a total fare of 118,020 yen. For BB Bus, the distance fare is calculated to be 38,080 yen and the hourly fare is 103,870 yen, resulting in a total fare of 141,950 yen.
[0076] Next, the fee is calculated (S26). Specifically, there are surcharges for late-night and early-morning operations, charges for assigning replacement drivers, surcharges for special vehicles, guide fees, and paid return shipping fees, and the necessary fees are calculated from these. In this example, a guide fee applies. For AA buses, the guide fee is calculated as 40,000 yen, and for BB buses, the guide fee is calculated as 36,000 yen. The applicable conditions and calculation methods for each fee are as described above, so explanations will be omitted.
[0077] Then, estimate information is generated (S27). Specifically, estimate information is generated based on the fare calculated in S25 and the fee calculated in S26. For example, as shown in FIG. 18, it is possible to automatically generate a quote list that allows comparison of quotes from multiple bus companies (in this example, AA Bus and BB Bus).
[0078] Returning to FIG. 22, the server 1 then transmits the quotation information to the travel agency device 2 (S14). This allows the travel agency to check the quotation information. The server 1 can also transmit estimate information to the bus operator device 3. This allows bus operators to check the quote information as well.
[0079] Next, the server 1 stores the estimate information (S15). Specifically, the unique estimate number (in this example, 20220501001) is linked to the data and stored in the storage unit 103. This allows you to smoothly identify the project and its contents when later checking the estimate, making a reservation (arrangement), or changing or deleting.
[0080] Next, it is determined whether or not a reservation is required (S16). Specifically, it is confirmed whether the "quote type" in the quotation request information is "quote / reservation required" or "quote / reservation not required." If a reservation is not required (S16-No), that is, if a quote / reservation is not required, the process ends. If a reservation is required (S16-Yes), that is, if a quote / reservation is required, the ordering process is executed.
[0081] FIG. 26 is a flowchart showing the procedure of the arrangement process. As shown in the figure, first, the server 1 executes an arrangement instruction (S31). For example, when quotation information is generated for multiple bus operators, information is sent to the travel agency device 2 to confirm which bus operator's chartered bus to reserve, and one bus operator is selected based on the reply result, and arrangement information for the selected bus operator is sent to the bus operator device 3. As a result, the travel agency places an order for the rental bus, and the bus company completes the order for the rental bus.
[0082] Next, the vehicle is allocated (S32). Specifically, the bus operator will secure the vehicle. For example, when an arrangement instruction is given to AA Bus, one large vehicle will be secured at Sales Office c for the operation days of June 20th and 21st. When the vehicle allocation is completed, the bus operator device 3 notifies the server 1 of the completion of allocation in response to an operation by an employee.
[0083] Next, the server 1 generates, stores, and notifies the order information (S33). Specifically, information about the case for which arrangements have been completed and its contents is generated and saved together with the arrangement number. The server 1 transmits (notifies) the arrangement information to the travel agency device 2 and the bus operator device 3.
[0084] This section explains the procedure for changing and deleting an already arranged matter. FIG. 27 is a flowchart showing the procedure for the change / order process. As shown in the figure, first, the server 1 is accessed (S41). Specifically, a specific URL is entered into the web browser of the travel agency device 2. This will take you to the change / delete web page, which has a field for entering the order number.
[0085] Next, the case is identified and notified based on the order number (S42). Specifically, enter the order number of the item to be changed or deleted in the order number input field on the web page. Next, it is determined whether the change or deletion is to be performed (S43). Specifically, it is determined whether the employee has selected "change" or "delete" through operation of the travel agency device 2.
[0086] If a change is required (S43-change), the content is changed (S44). Specifically, the travel period, vehicle class, number of vehicles, etc. can be changed. Next, the vehicle is allocated (S45). Then, the arrangement information is generated, saved, and notified (S47). The allocation of vehicles in S45 is the same process as in S32, and the generation, storage, and notification of arrangement information in S47 are the same as in S33, so detailed explanations will be omitted.
[0087] In the case of deletion (S43-delete), the case is deleted (S48). For example, the saved data of the case is deleted.
[0088] Thus, in the chartered bus processing method of the present invention, the process of performing information processing between multiple travel agency devices 2 and multiple bus operator devices 3 includes the following steps: a first step of storing bus operator condition information indicating the conditions of the bus operator that can be input by the bus operator device 3; a second step of extracting from multiple bus operators bus operators that can provide a rental bus that meets both the user's conditions and the bus operator's conditions based on the user condition information indicating the conditions of the user of the chartered bus that can be input by the travel agency device 2 and the bus operator condition information; a third step of calculating the price of the chartered bus from the bus operator extracted in the second step based on the user condition information and the bus operator condition information; and a fourth step of outputting estimate information based on the price calculated in the third step to the travel agency device 2.
[0089] (For other configurations) Status Management The server 1 stores and updates status information for each of the various states after receiving a request for quotation. For example, when the quotation request screen is displayed but the quotation request has not been completed, the status is stored as "Quotation request (not completed)", when the quotation request has been completed (quote request information has been received), the status is updated to "Quotation request (completed)", when the quotation information has been sent, the status is updated to "Quotation response (completed)", when a formal order has been placed by the travel agency with the bus operator, the status is updated to "Ordered", and when the bus operator has processed the order, the status is updated to "Ordered". When a change request is made, the status is updated to "change request", and then updated to "change received" upon receipt. Also, when a cancellation (deletion) request is made, the status is updated to "cancellation request", and then updated to "cancellation received" upon receipt. Each time this status information is updated, it is sent to the travel agency device 2 and the bus operator device 3 so that it can be displayed. This allows the status of each case to be shared between the travel agency and the bus operator. This can reduce reservation errors (for example, forgetting to make a reservation, forgetting to arrange, forgetting to delete, etc.).
[0090] -Reminder function When the reservation is completed, the server 1 can set (store) a date several days before the operation date (for example, the day before) as the reminder date. At this time, the email addresses of travel agency employees (persons in charge) and end users can also be registered as recipients of reminder information. This allows Server 1 to send reminder information (for example, "A chartered bus has been booked for tomorrow, month, day. Please arrive at Kurashiki Station by _____ o'clock.") to the registered email address on the reminder date.
[0091] Quote expiration date The server 1 can automatically set and notify the expiration date of the quotation information. For example, the expiration date can be one year. In this case, if the quotation information is sent on May 1, 2022, the server 1 stores May 1, 2023 in the storage means 111 as the last day of the validity period. Server 1 can include "Quote expiration date: May 1, 2023" in the quote information. In this case, the server 1 can delete the project information when the quotation expiration date (May 1, 2023) is reached or exceeded.
[0092] Designation of bus operators It is also possible to allow travel agencies to choose from when requesting quotes. In this case, for example, a field for specifying the party to whom a quote is to be requested can be provided in the quote request information, and if the party to whom a quote is to be requested is entered in that field in the received quote request information, server 1 can calculate the fare and charges for the bus company that is the party to whom a quote is to be requested, generate quote information, and send it to the travel agency. Furthermore, the server 1 can extract bus operators with available vehicles based on the quotation request information and transmit a list of these to the travel agency device 2. In this case, the travel agency device 2 may display the received list of bus operators, allowing the employee to select any bus operator from the list. When the travel agency device 2 receives the information on the selected bus company, it calculates the fare and charges for that bus company, generates estimate information, and transmits it to the travel agency.
[0093] Display of standard fares and charges in quotation information By including the specified fare and charges in the estimate information, it is possible to display on the travel agency device 2 that the price is above the specified minimum amount. For example, in this example, since the vehicle is a large vehicle operated by the Chugoku Transport Bureau, the minimum kilometer fare is 150 yen and the minimum hourly fare is 5,010 yen, which are displayed in the estimate list. This allows end users such as travel agencies to double-check that the price is above the minimum limit, and it also allows them to emphasize that compliance with laws and regulations and fair fare prices are guaranteed, giving end users a sense of security.
[0094] Remote support The travel agency device 2 need only be under the control of the bus operator, and does not need to be installed at the travel agency. The same applies to the bus operator device 3, which does not need to be installed at the bus operator. This allows, for example, a travel agency employee with a terminal device such as a PC or mobile terminal to remotely access server 1 from a remote location outside the company, such as their home or a satellite office, to request a quote, etc.
[0095] As described above, the chartered bus ordering system of this embodiment includes a server 1 that performs information processing between multiple travel agency devices 2 and multiple bus operator devices 3, a storage means 111 that stores bus operator condition information (office master 154, AGT group master 155, AGT group fare master 156, AGT group fare calendar 161, etc.) that indicates the conditions of the bus operator and can be input by the bus operator device 3, an extraction means 112 that extracts from multiple bus operators bus operators that can provide a rental bus that meets both the user's conditions and the bus operator's conditions based on user condition information (quote request information, etc.) that indicates the conditions of the user of the chartered bus and can be input by the travel agency device 2, a calculation means 113 that calculates the price of the chartered bus from the bus operator extracted by the extraction means 112 based on the user condition information and the bus operator condition information, and an output means 114 that outputs quotation information based on the price calculated by the calculation means 113 to the travel agency device 2. This makes it possible to automatically generate a quote that meets the conditions of both the travel agency (including the end user) and the bus operator. This makes it possible to provide a charter bus ordering system that is useful for both parties. In particular, in the past, employees had to take the time to check whether the calculated price met the regulations (whether it was above the specified minimum amount), and furthermore, prices were set differently for each travel agency at the discretion of the employee, which resulted in variations in pricing and a lack of consistency and reproducibility.However, with the chartered bus ordering system of the present invention, server 1 automatically executes estimates that meet the regulations, eliminating these conventional problems.
[0096] In addition, in the chartered bus ordering and purchasing system of this embodiment, the bus company condition information includes regulation information (such as AGT group fare master 156), which is information regarding regulations for chartered bus services, and the extraction means 112 extracts bus companies that can provide rental buses that meet both the user's conditions and regulations based on the user condition information and regulation information. In addition, in the chartered bus ordering system of this embodiment, the bus company condition information includes standard unit prices for each travel agency and each date (AGT group fare master 156, AGT group fare calendar 161, etc.) which can be input by the bus company device 3, and the calculation means 113 calculates the price of a chartered bus from the bus company extracted by the extraction means 112 based on the operation date included in the user condition information (travel period, estimated itinerary, etc. in the quotation request information) and the standard unit price included in the bus company condition information. This allows automatic generation of quotes that meet the conditions of travel agencies (including end users) and bus operators, as well as regulations. This allows estimates to be generated easily and accurately.
[0097] In addition, the chartered bus ordering system of this embodiment is equipped with a display control means 115 that causes the travel agency device 2 to display the number of available rental buses for each bus company office that manages the chartered buses, and a loaner vehicle management means 116 that manages loaner vehicles for each business area consisting of one or more offices.Even if there are no available vehicles at a specific office among the offices that make up the business area, if there are available loaner vehicles in the business area, the display control means 115 allocates the number of available loaner vehicles to each office and displays them as the number of available rental buses on the travel agency device. This allows the system to show or process a vehicle as available even if there are no available vehicles at each sales office if there are replacement vehicles or chartered vehicles available for the sales section.
[0098] Although the preferred embodiments of the present invention have been described above, it goes without saying that the present invention is not limited to the above-described embodiments, and various modifications can be made within the scope of the present invention. The configuration of the chartered bus ordering system is not limited to the above-described embodiment, and some or all of the configuration of one device may be provided by another device. For example, although the configuration has been described in which quotation request information is sent from the travel agency device 2 to the server 1 by operating the travel agency device 2, the quotation request information may also be stored in the storage means 111 by, for example, inserting a storage medium storing the quotation request information into the server 1 or manually entering the quotation request information into the server 1. Also, an automatic estimate does not have to be used. For example, when a request for an estimate is made, the server 1 notifies the bus operator device 3 of the bus operator extracted by the extraction means 112. In this case, an employee of the bus operator manually prepares an estimate and returns the estimate information to the travel agency or the travel agency device 2 via the server 1.
[0099] In addition, a user terminal (not shown) such as a personal computer or smartphone owned by the end user may be provided. In this case, the user terminal and the travel agency device 2 are capable of communicating, and the travel agency device 2 accepts the chartered bus service online in response to the operation of the user terminal. The travel agency device 2 then transmits the information entered at the time of acceptance to the server 1, and various processes such as quotation and reservation for the chartered bus service are then carried out by the server 1. Alternatively, the user terminal and the server 1 may communicate directly in response to an operation of the user terminal, without going through the travel agency device 2, and the server 1 may execute processes such as quotation and reservation for chartered bus services.
[0100] It is also possible to establish a system that allows bus operators to mutually support each other in assets and facilities such as parking lots and chartered buses. For example, calendar information that can identify vacant parking spaces and vacant buses is stored in the server 1, and can be viewed (shared) on the terminal devices (bus company devices, etc.) of each bus company. This means that, for example, bus operators who do not have available parking spaces at their offices can apply online to other bus operators to rent out their parking spaces, and bus operators who do not have available rental buses at their offices can apply online to other bus operators to rent out (charter) their buses.
[0101] In the above-described embodiment, a package program is installed in the travel agency device 2 and the bus operator device 3, and the server 1 and the travel agency device 2 and the bus operator device 3 are configured to cooperate via API, but the present invention can be implemented even without these configurations. In this case, for example, the bus operator device 3 can transmit vehicle vacancy information (number of vacant vehicles by date and vehicle class, number of replacement vehicles, number of chartered vehicles, etc.) in advance for each bus operator, each operating section, and each operating office, and store this information in the server 1, which can then be referenced when a request for a quote is received.
[0102] The estimate list shown in FIG. 18 is an example, and various information can be incorporated into the list. For example, the list can include end user names, trip duration, itinerary (start point, stopover points, destination points), etc. This makes it easy to confirm whether a request for quotation has been received from multiple travel agencies for the same project, for example, when the same end user requests competitive quotations from multiple travel agencies. For example, by displaying quote lists side by side or overlapping them, it is easy to visually determine whether they are for the same project or not. In this regard, with the conventional manual method, it was time-consuming to perform similar estimate work for the same project while paying attention to regulations and travel agencies each time.However, on the other hand, performing estimate work from different perspectives can sometimes lack consistency and reproducibility, which was extremely wasteful and cumbersome for bus company employees. In addition, in the past, there was a risk of double booking of chartered buses and the resulting excess inventory, resulting in lost opportunities. According to the present invention, it is possible to prevent double reservations and lost opportunities by displaying estimate lists and statuses.
[0103] The travel agency device 2 may also adopt a "client-server model." Specifically, a travel agency server and terminal devices (clients) that can be operated by employees are installed within the travel agency in a state where they can communicate via a LAN or the like. For example, when an employee of a travel agency requests a quote using the chartered bus ordering system, he or she can access the travel agency server by operating a terminal device, and based on this access, the travel agency server can access server 1, allowing data communication between travel agency device 2 and server 1. Interdepartmental communication can also be carried out via communication between terminal devices. For example, when an order is placed with a bus operator from a terminal device at a travel agency's sales site (outside the company), a notification to that effect is sent to a terminal device in the travel agency's bus procurement and arrangement department (inside the company), and once the department has carried out the required processing (approval processing, etc.), the order information is sent to server 1. The server 1 can process orders to bus operators based on the order information received from the travel agency device 2. Similarly, the bus operator device 3 can adopt a "client-server model."
[0104] (Guide related) The chartered bus system of the present invention is provided with an additional function that allows for the management and provision of information about guides. FIG. 28 is a functional configuration diagram of the server 1 having a configuration capable of managing and providing guide information. As shown in the figure, the server 1 (control unit 101) includes a guide information storage means 121, a remaining guide number calculation means 122, a first display control means 123, a second display control means 124, a bus information storage means 125, a remaining bus number calculation means 126, and an estimate limiting means 127. Each means will be described below. Note that the storage means 111, extraction means 112, calculation means 113, output means 114, display control means 115, and loan car management means 116 have the same configuration as described above (see FIG. 5), so their description will be omitted.
[0105] The guide information storage means 121 stores information about guides (guide information) including the total number of guides and the number of reservations for guides in the storage unit 103. Guide information is managed by each bus company, just like chartered buses (vehicles), but while chartered buses are managed by prefecture (operating area), guides are managed by area, which is different from the operating area. That is, guide information is managed for each group of offices belonging to the same area. This group is called a "office office group for guide management." Note that guide management office groups do not have to be set for each area, but can be set arbitrarily by the bus company, for example.
[0106] FIG. 29 is an explanatory diagram of a guide management office group. A guide management office group is made up of one or more offices that belong to the same area. For example, as shown in FIG. 29, AA Bus has guide management office groups for the Okayama area and the Okayama North area in Okayama prefecture. The Okayama area group consists of three offices, A to C, and the Okayama North area group consists of one office, D. The definition (conditions) of the same area and the offices belonging to one group may be set arbitrarily by the bus operator. For example, if a sales office in Hiroshima Prefecture (called sales office e) is close to sales office d in Okayama Prefecture (i.e., they can be determined to be in the same area), the group for the Okayama North area may be made up of two sales offices, sales office d and sales office e, and the group for the Hiroshima area may be made up of two sales offices, sales office d and sales office e.
[0107] FIG. 30 is a chart showing an example of guide information stored by the guide information storage means 121. As shown in FIG. As shown in Figure 30, the guide information includes the total number of company guides, the total number of other company guides, the total number of guides, the number of guide reservations, the number of remaining guides, the ratio of remaining guides, etc., and is stored in association with the bus operator, guide management office group, vehicle class, operation date, and time slot. Figure 30 shows an example of the total number of company guides, total number of other company guides, total number of guides, number of guide reservations, number of remaining guides, and remaining guide ratio for the operation date: April 21st, vehicle type: large, bus operator: AA Bus, guide management office group: Okayama area. Detailed illustrations are omitted, but guide information is registered and managed in a manner that links together bus operator, operation date (corresponding to "date"), guide management office group, vehicle class (corresponding to "vehicle class details"), total number of company guides, total number of other company guides, total number of guides (corresponding to "total number"), number of guide reservations (corresponding to "number of reserved vehicles"), remaining number of guides, and remaining guide ratio, for example, as shown in the vehicle usage information in Figure 19. Please note that the guide arrangement and management does not include functions for OB or chartered vehicles.
[0108] Of these, the “number of guide reservations” is managed by a program (operation management package) stored in the bus operator device 3. The operation management package has a function of storing the number of guide reservations in the storage unit 203 of the bus business device 3, and when a guide reservation process is executed manually or automatically, the stored number of guide reservations is updated. The operation management package (bus operator device 3) is linked to the server 1, and every time the number of guide reservations is updated (reserved), the updated number of guide reservations is sent to the server 1. Therefore, the server 1 can receive and acquire the number of guided tour reservations transmitted from the bus operator device 3 every time the number of guided tour reservations is updated.
[0109] Other guide information (guide information other than the number of guide reservations) does not depend on the operation management package, but like the number of guide reservations, is sent from the bus operator device 3 to the server 1 in response to an operation of the bus operator device 3. The server 1 receives and acquires guide information transmitted from the bus operator device 3 (for example, the total number of guides from the bus operator's company, the total number of guides from other companies). The guide information transmitted from the bus operator device 3 may be information for each business office. In this case, when the server 1 receives the number of guide reservations and the number of guides for each office, it identifies the "office group for guide management" and calculates the total number as the "number of guide reservations" and the "total number of guides." In this way, the server 1 stores part of the guide information received from the bus operator device 3 (e.g., number of guide reservations, total number of company guides, total number of other company guides) as is, or stores guide information calculated based on this information (e.g., total number of guides, remaining number of guides, remaining guide ratio).
[0110] "Total number of company guides" is the total number of guides in the sales group for guide management. In other words, it is the total number of guides who belong to each sales office in the same area. The "total number of company guides" is set and stored in accordance with the operation of the bus operator device 3. In this embodiment, an example is shown in which the bus company is AA Bus, the guide management office group is Okayama area, the operation date is April 21st, and the total number of company guides in the large vehicle category is "8" (FIG. 30).
[0111] "Total number of guides from other companies" is the number of guides that can be dispatched from other companies (for example, external guide dispatch companies affiliated with the bus operator). "Total number of guides from other companies" is the estimated number of guides that can be dispatched from other companies to the guide management office group. The "total number of other company guides" is set and stored in response to an operation of the bus operator device 3. In this embodiment, an example is shown in which the bus company is AA Bus, the guide management office group is Okayama area, the operation date is April 21st, and the vehicle class is large, and the ``total number of other company guides'' is ``2'' (Figure 30).
[0112] "Total number of guides" is the sum (total number) of the total number of guides from our company and the total number of guides from other companies. In other words, "Total number of guides" includes the number of guides that can be dispatched from outside (total number of guides from other companies). Therefore, the "total number of guides" means the maximum number of guides that can be arranged in a guide management sales office group. In this embodiment, an example is shown in which the bus operator is AA Bus, the guide management office group is Okayama area, the operation date is April 21st, and the vehicle class is large, with the "total number of guides" being "10" (= total number of our own guides: 8 + total number of guides from other companies: 2) (Figure 30).
[0113] "Number of guide reservations" is the number of guides that have been booked. The "number of guide reservations" is the total number of guide reservations in the guide management sales office group. In this embodiment, an example is shown in which the bus company is AA Bus, the guide management office group is Okayama area, the operation date is April 21st, and the vehicle class is large, and the "number of guide reservations" is "8" (Figure 30).
[0114] "Number of remaining guides" is guide information calculated by subtracting the total number of guide reservations from the total number of guides. The "guide information" is calculated by the remaining guide number calculation means 122 based on the total number of guides and the number of guide reservations. Therefore, the "remaining number of guides" means the number of guides that can actually be arranged in the guide management sales office group. In other words, the "remaining number of guides" can be said to be information indicating the availability of guides for each guide management sales office group. In this embodiment, an example is shown in which the "number of remaining guides" is "2" (= total number of guides: 10 - number of guide reservations: 8) for the bus company: AA Bus, guide management office group: Okayama area, operation date: April 21st, and vehicle class: large (Figure 30).
[0115] The "remaining number of guides" will be shown to the bus operator upon request. Specifically, the server 1 (control unit 101), as the first display control means 123, transmits information (first information) regarding the remaining number of guides to the bus operator device 3, and the bus operator device 3 displays the received remaining number of guides on the display device 305. In the example of this embodiment, when the server 1 receives information from the AA Bus bus operator device 3 indicating a request to display the "remaining number of guides" for the guide management office group: Okayama area, operation date: April 21st, and vehicle class: large, the server 1 extracts the guide information stored in the memory unit 103 and returns it to the bus operator device 3. Based on the received guide information, AA Bus's bus operator device 3 (display device 305) displays the remaining number of guides for bus operator: AA Bus, guide management office group: Okayama area, operation date: April 21st, and vehicle class: large. This allows each bus operator to accurately determine the number of guides they can arrange for each area. However, the "number of remaining guides" is not shown to the travel agency, but instead, "information suggesting the number of remaining guides" is shown, as described below.
[0116] The "remaining guide number ratio" is the ratio (proportion) of the remaining number of guides to the total number of guides. The server 1 (control unit 101) calculates the "remaining guide number ratio" by "remaining number of guides / total number of guides." In this embodiment, an example is shown in which the ``remaining guide ratio'' for the bus operator: AA Bus, guide management office group: Okayama area, operation date: April 21st, and vehicle class: large is ``0.20'' (= remaining guides 2 / total guides 10) (Figure 30).
[0117] The server 1 (control unit 101), as the second display control means 124, causes the travel agency device 2 to display information (second information) relating to the remaining number of guides. Specifically, the server 1 transmits "information suggesting the remaining number of guides" as the second information to the travel agency device 2, and the travel agency device 2 receives the second information transmitted from the server 1 and displays it on the display device 205. In the chartered bus system of this embodiment, a symbol can be displayed as the second information. That is, the second display control means 124 causes a symbol (second information) corresponding to the ratio of remaining guides to be displayed on the travel agency device 2. This symbol corresponds to the ratio of remaining guides, and therefore can also be said to be information corresponding to the number of remaining guides. For example, the server 1 transmits information about a symbol corresponding to the remaining guide number ratio to the travel agency device 2, and the travel agency device 2 displays the symbol based on the received information.
[0118] A plurality of types of symbols can be set depending on the ratio of remaining guides. For example, if "0.3≦remaining guide number ratio", it can be set as "◯", if "0.2≦remaining guide number ratio<0.3", it can be set as "△", and if "remaining guide number ratio<0.2", it can be set as "×". The information is not limited to symbols, but may be graphics, letters, numbers, or other information that indicates the availability of guides, such as the number of remaining guides or the ratio of remaining guides. Furthermore, the number of levels is not limited to three, i.e., circle, triangle, and cross, but may be two or less levels or four or more levels. In this embodiment, the AA Bus bus operator device 3 (display unit) determines based on the received guide information that the "remaining guide ratio" for bus operator: AA Bus, guide management office group: Okayama area, operation date: April 21st, and vehicle class: large is "0.2", and therefore the symbol "△" corresponding to this remaining guide ratio is displayed on the travel agency device 2. This allows each travel agency to get an overview of the availability of guides by area (group) for each bus operator.
[0119] As described above, the chartered bus system of this embodiment is equipped with a guide information storage means 121 that stores the total number of guides and the number of guide reservations, a remaining guide number calculation means 122 that calculates the remaining number of guides based on the total number of guides and the number of guide reservations, a first display control means 123 that causes the bus operator device 3 to display first information, which is information regarding the remaining number of guides, and a second display control means 124 that causes the travel agency device 2 to display second information, which is information regarding the remaining number of guides and is different from the first information, and the remaining number of guides is displayed as the first information, and information (symbol) indicating the remaining number of guides is displayed as the second information.
[0120] In other words, in the chartered bus system of this embodiment, the "remaining number of guides" of the bus company is shown to the bus company, and "information suggesting the remaining number of guides" of each bus company is made public to travel agencies. The effect will be explained by taking as an example a case where the remaining guide number is "1" and the remaining guide number ratio is "less than 0.2". In this case, the bus operator can accurately grasp the remaining number of guides that can be arranged, "1", and by subscribing to the service related to this system, they can properly manage guides. In response to this, an "X" will be displayed to the travel agency, and when the travel agency staff sees this, they will understand that "X = 0 remaining guides = no available guides" and will likely give up on requesting a quote or placing an order with that bus company.However, on the other hand, if a travel agency knows that "X does not necessarily mean 0 remaining guides," they can be given preferential treatment by allocating guides that correspond to the actual remaining number. Also, since "x does not necessarily mean that the number of remaining guides is 0," if the number of remaining guides is 1, a guide corresponding to that number of remaining guides can be secured as a spare guide. Therefore, even if a person is unable to board the chartered bus on the day of operation due to an emergency such as illness, the remaining guides can be arranged as backup guides without having to secure a specialized backup guide in advance.
[0121] The disclosure of "information suggesting the number of remaining guides" can be set by each bus operator at their own discretion. Specifically, depending on whether the bus operator device 3 is turned on or off, the operator can select whether to make public or private information indicating the remaining number of guides of the operator. The server 1 stores the "on" information and "off information" in the storage unit 103 in association with the information of the bus company that made the request based on the above operation. As a result, when on information is stored, the "information suggesting the number of remaining guides" for the bus operator linked to that information can be displayed on the travel agency device 2, but when off information is stored, the "information suggesting the number of remaining guides" for the bus operator linked to that information cannot be displayed on the travel agency device 2.
[0122] Instead of "x", the symbol "*" can be displayed to indicate that an inquiry is required. For example, in response to an operation of the bus operator device 3, one of "x" and "*" can be selected as the symbol to be displayed when the "ratio of remaining guide numbers<0.2". If "*" is displayed, travel agency employees can find out whether a guide is available (whether there are any remaining or how many are remaining) by contacting the designated contact point. It should be noted that the "remaining number of guides" can be applied instead of or in addition to the "remaining number of guides ratio." Also, for example, if "remaining number of guides≦0", "x" may be displayed, or if "0<remaining number of guides ratio<0.2", "*" may be displayed.
[0123] (Regarding remaining number of guides and chartered buses and availability) The remaining number of guides and the remaining number of buses can be displayed together, and information suggesting the remaining number of guides and information suggesting the remaining number of buses can be displayed together. The method for calculating the remaining number of buses will be described below. The number of remaining buses is calculated based on the total number of chartered buses (total number of buses) and the number of chartered bus reservations (number of bus reservations), just like the number of remaining guides. In other words, the number of remaining buses is the total number of buses minus the number of bus reservations. However, unlike the remaining number of guides managed for each group, the remaining number of buses is calculated for each office using the total number of buses and the number of reserved buses managed for each office. For example, as shown in Figure 19, rented buses (vehicles) are managed by bus company, date, business office, and vehicle class (vehicle class details), and the total number of buses, which corresponds to the total number of buses, and the number of bus reservations, which corresponds to the number of reserved buses, are linked and managed as bus information. Time slots can also be added to the bus information (not shown). In other words, the server 1 is equipped with a bus information storage means 125 that stores bus information including the total number of buses and the number of bus reservations for each office, and a remaining bus number calculation means 126 that calculates the remaining number of buses for each office based on the total number of buses and the number of bus reservations. Then, the first display control means 123 of the server 1 causes the bus operator device 3 to display both the number of remaining guides and the number of remaining buses as the first information.
[0124] FIG. 31 shows a bus guide remaining number display screen displayed on the bus operator device 3 (display device 305). As shown in the figure, the remaining number of guides and the remaining number of buses can be displayed together. For example, an employee of a bus company can operate the bus company device 3 of his / her own company to display the remaining number of buses and guides on the remaining bus guide number display screen. For example, FIG. 31 shows a bus guide remaining number display screen displayed on the bus operator device 3 (display device 305) of AA Bus. This screen is a bus guide remaining number display screen when the prefecture: Okayama, vehicle class: large, and display period: April 15, 2024 to July 15, 2024 are specified by operating the operating device 304. As a result, for example, AA Bus employees can see that there are 5 buses and 5 guides remaining on April 15th, and that there is 1 bus and 1 guide remaining on April 20th (Figure 31). In other words, by specifying the area (area of the guide management office group), vehicle class, and operation date (display period), bus operators can grasp both the number of remaining guides and buses for their company in the specified area, vehicle class, and operation date. This allows bus operators to simultaneously grasp the number of remaining guides as well as the number of remaining buses, allowing them to appropriately manage and arrange guides and vehicles.
[0125] FIG. 32 is a diagram showing an example of an availability display screen displayed on the travel agency device 2 (display device 205). As shown in the figure, the guide availability and the vehicle availability (bus availability) can be displayed together. The availability display screen allows travel agency employees to operate their own travel agency device 2 to display information indicating the relevant availability of vehicles and guides (i.e., information indicating the number of remaining buses and guides). For example, FIG. 32 shows an availability display screen displayed on the travel agency device 2 (display device 205) of a certain travel agency. This screen is an availability display screen when the prefecture: Okayama, vehicle class: large, and display period: April 15, 2024 to July 15, 2024 are specified by operating the operation device 304. As a result, for example, a travel agency employee can know that the availability of AA buses and guides on April 15th is both "Good," and that the availability of AA buses and guides on April 20th is both "Poor." In addition, a travel agency employee can know that the availability of BB buses on April 15th is "Good" and the availability of guides is "Poor," and that the availability of BB buses on April 20th is "Poor" and the availability of guides is "Good." In other words, by specifying the area (area of the guide management office group), vehicle class, and operation date (display period), travel agencies can grasp both the availability of buses and guides for each bus operator in the specified area, vehicle class, and operation date. This allows travel agencies to simultaneously grasp the availability of guides and buses at each bus operator, and can use this information when ordering guides and vehicles or requesting quotes. In Figure 32, "○: Available", "△: Limited availability", "※: Please inquire", and "×: Full" are displayed as <Vacancy status>, and "Availability", "△: Limited availability", "※: Please inquire", and "×: No availability" are displayed as <Guide availability status>, but the display format is not limited to this. For example, either "*: Please inquire" and "x: Full" or "x: No vacancies" may be displayed. Alternatively, only the symbols may be displayed.
[0126] (Limitation of automatic quotation output) The chartered bus system of this embodiment is a system that performs information processing between multiple travel agency devices 2 and multiple bus operator devices 3, and its basic feature is that it automatically creates and outputs quotation information that meets the conditions of both the travel agency terminal 2 and the bus operator device 3. That is, it is equipped with a storage means 111 that stores bus operator condition information that indicates the conditions of the bus operator and can be input by the bus operator device 3, an extraction means 112 that extracts bus operators that can provide a rental bus that meets both the user's conditions and the bus operator's conditions from among multiple bus operators based on user condition information that indicates the conditions of the user of a chartered bus and the bus operator condition information that can be input by the travel agency device 2, a calculation means 113 that calculates the price of a chartered bus from the bus operator extracted by the extraction means 112 based on the user condition information and the bus operator condition information, and an output means 114 that outputs estimate information based on the price calculated by the calculation means 113 to the travel agency device 2.
[0127] However, problems may arise if quotation information is automatically created and output uniformly for all quotation requests. In other words, there are cases where making an artificial response brings about greater benefits for one or both parties, and cases where not making an artificial response brings about less disadvantages for one or both parties. For example, if quotation information is created and output uniformly for all quotation requests that state "guide required" when the number of remaining guides is 0, the travel agency that receives the quotation information will likely perceive the bus company that sent the quotation information as "accepting orders" and therefore "possible to place orders," and the actions of the bus company that responded even though they were unable to arrange a guide could become a problem later on. Furthermore, problems can arise not only when the remaining number of guides is not 0, but also when the remaining number of guides is small. For example, when the number of remaining guides is 1 and multiple travel agencies (say, travel agency A and travel agency B) request quotes for a "guide required," the bus operator may wish to prioritize orders from travel agency A over travel agency B for various reasons. However, since the bus operator is forced to prioritize the earliest reservation associated with the quote request or order, the bus operator's wishes may not be reflected.
[0128] Therefore, in the chartered bus system of this embodiment, when the "remaining number of guides who can automatically respond" is equal to or greater than the "number of guides required for a quote request," server 1 allows the automatic generation and output of quote information, and when the "remaining number of guides who can automatically respond" is less than the "number of guides required for a quote request," it restricts the automatic generation and output of quote information. Specifically, if the number of guides required for the quotation request is less than or equal to the "remaining number of guides who can automatically reply" = "number of guides who can automatically reply for quotation" - "number of guide reservations", it is determined that there are available guides and the quotation information is automatically generated and output. The "number of guides who can automatically reply" is calculated for each route, each operation date, each vehicle class, and each issuing office. In other words, the "number of guides who can automatically respond to estimates" is managed for each sales office, unlike the "total number of guides" which is managed for each sales group for guide management. Note that the "number of guides who can automatically respond to estimates" may also be managed for each sales group for guide management. When restricting the automatic generation and output of quotation information, the travel agency may be notified of this automatically or manually (for example). In the "automatic" case, the server 1 simply sends information to the travel agency device 2 of the relevant travel agency, and in the "manual" case, an employee of the relevant bus operator simply notifies the travel agency of this via email, fax, or telephone.
[0129] As explained above, the chartered bus system of this embodiment, for chartered bus services, is equipped with a travel agency device managed by the ordering travel agency and a bus operator device managed by the receiving bus operator, and is equipped with a guide information storage means 121 that stores the total number of guides and the number of guide reservations, a remaining guide number calculation means 122 that calculates the remaining number of guides based on the total number of guides and the number of guide reservations, a first display control means that causes the bus operator device 3 to display first information that is information regarding the remaining number of guides, and a second display control means that causes the travel agency device 2 to display second information that is information regarding the remaining number of guides and is different from the first information, wherein the first information is the remaining number of guides and the second information is information that suggests the remaining number of guides. This allows bus operators to accurately grasp the remaining number of guides that can be arranged, allowing them to properly manage guides. In response, travel agencies can grasp the availability of guides at an overview level, as well as allocate guides to specific travel agencies on a priority basis and use remaining guides as reserve guides. Therefore, according to the chartered bus system of this embodiment, guides can be appropriately managed, arranged, and information provided. In addition, the chartered bus system of this embodiment can provide the above-mentioned guide-related functions in addition to the basic function that is useful for both the travel agency (including the end user) and the bus operator, namely, the ability to automatically generate quotes that meet the conditions of both the travel agency and the bus operator.
[0130] In contrast, conventional charter bus reservation systems (for example, JP Patent Publication No. 2002-373280) take into consideration the desired conditions of users, but do not take into consideration the conditions of the bus operator. In addition, the management of remaining guide numbers and the provision of information to travel agencies (such as information on remaining numbers) are done manually, leaving room for improvement. According to the chartered bus system of this embodiment, the way the number of remaining guides is displayed is different between the travel agency and the bus operator, so that some or all of the conventional problems can be solved.
[0131] (Large event) The chartered bus system of the present invention has an additional function that allows smooth, easy, and rational processing of vehicle arrangements for large-scale events. "Large-scale events" refer to events such as the Olympics and the National Sports Festival, which require the arrangement of a large number of buses for a specific period and area. In this embodiment, a "large event" refers to a case in which multiple bus companies need to arrange for the use of multiple (especially multiple) chartered buses. Hereinafter, a large event will also be referred to as a "large case."
[0132] In the case of "large-scale projects," travel agencies do not arrange vehicles until the detailed itinerary (course) has been decided, but rather check vehicle arrangement availability in advance. As the first step in "confirming vehicle arrangement quotas," the travel agency will request multiple bus operators to secure the "required number" of chartered buses (also called the "adjusted number"). In response, bus operators will respond with the "number of vehicles available for chartering" (also called the "number of vehicles provided"). If a bus operator can provide more than the "number of required vehicles," they will respond with the "number of vehicles available." The travel agency will decide the "planned number of vehicles" based on the responses from the bus operators. Once the travel agency has determined the planned number of vehicles for each bus company, it will notify each bus company of that number. The bus company will then secure the planned number of vehicles. In other words, the planned number imposes a performance obligation on the bus company as the number of vehicles they must secure. This completes the first step.
[0133] Once the detailed itinerary has been decided, the travel agency then requests quotes from each bus operator, and after referring to the quote information, negotiates the price as necessary before placing an order. Requests for quotes are generally made to bus operators who have notified them of the "planned number of vehicles." It is also possible to request competitive quotes from multiple bus operators through a single request for quote. It is expected that after referring to the quotation information, the travel agency may place an order with a bus company other than the one that secured the vehicle due to issues such as cost, but since this is not directly related to this function, for the sake of simplicity, we will assume that the order will be placed with the bus company that received the quotation. In addition, while bus operators involved in large-scale projects are generally required to be subscribed to this service, it is also possible for bus operators that are not subscribed to the service to participate.
[0134] Ideally, travel agencies would allocate the number of vehicles that matches the "planned number" to each bus operator and then request quotes and place orders, but the planned number, which is only an estimate, and the number of vehicles requested for quotes, which assume an order, are generally different numbers. For this reason, travel agencies would prefer to set the number of buses to request quotes for while referring to the allocation status (ratio, etc.) of the planned number of buses, but the allocation of the number of buses to request quotes is done manually, and it is extremely difficult and cumbersome to allocate the number of buses to a large number of bus operators in a rational manner, especially in the case of large events. Therefore, the chartered bus system of this embodiment is provided with a function to automatically allocate the number of vehicles for which estimates are requested based on the planned number of vehicles for large-scale projects, and a function to assist in rationally allocating the number of vehicles for which estimates are requested based on the planned number of vehicles.
[0135] FIG. 33 is a functional configuration diagram of the server 1 having a configuration capable of executing the process of arranging a chartered bus for a large-scale project. As shown in the figure, the server 1 (control unit 101) includes a first allocation means 131, a second allocation means 132, a quote request information generation means 133, a quote request means 134, and a support display means 135. Note that the storage means 111, extraction means 112, calculation means 113, output means 114, display control means 115, loaner car management means 116, guide information storage means 121, remaining guide number calculation means 122, first display control means 123, second display control means 124, bus information storage means 125, remaining bus number calculation means 126, and estimate restriction means 127 have the same configuration as already described (see Figures 5 and 28), so their explanations will be omitted.
[0136] The first allocation means 131 allocates the planned number of buses to a plurality of bus operators in advance in response to the operation of the travel agency device. The second allocation means 132 allocates the “specific number of vehicles” to a plurality of bus operators based on the planned number of vehicles allocated by the first allocation means 131. The quotation request information generating means 133 generates quotation request information for each bus operator based on the “allocation result” allocated by the second allocation means 132. The estimate request means 134 transmits the estimate request information to each bus operator device 3 managed by each bus operator. The "specific number of units" corresponds to the "estimated number of units required." The "allocation result" corresponds to the "quantity of units requested for quotation." This will be explained in detail below.
[0137] FIG. 34 is a sequence diagram showing the overall flow of the process for arranging a chartered bus for a large-scale project. As shown in FIG. 34, first, in response to a request from a client (for example, a planning company for a large project), a "large project registration" is executed (S101). The "large-scale project registration" is executed in response to an operation on the travel agency device 2 (operation device 204). FIG. 35 is a diagram showing an example of a menu screen displayed on the travel agency device 2 (display device 205). On the menu screen, if you select the "Large Projects" area (e.g., click with a mouse), you will be taken to the large project registration screen (Figure 36), and if you select the "Regular Projects" area, you will be taken to the regular quotation request input screen (Figure 24). The processing after input on the quotation request input screen (FIG. 24) is as described above (for example, paragraphs 0066 onward), and is not related to this function, so a description thereof will be omitted.
[0138] In "Large-item registration," the basic information of the large-item is entered by operating the operation device 204 while the "Large-item registration screen" (FIG. 36) is displayed. Fig. 36 is a diagram showing an example of a large-scale project registration screen. As shown in Fig. 36, the project registration screen has input fields for "project name," "sales area," "operation period," "vehicle class details," etc. Enter the name of the large project (project name) in the "Project Name" field. Figure 36 shows an example where the project name "XX International Tournament" has been entered. In the "Business Area" field, multiple business areas for chartered buses related to large-scale projects are specified. Figure 36 shows an example in which "Okayama, Hiroshima, Kagawa" are specified as business areas. In the "Operation Period" field, enter the operation period of the chartered bus. Figure 36 shows an example where "May 2nd to 6th, 2024" is entered as the operation period. In "Vehicle Class Details," enter the details of the class of the chartered bus. Figure 36 shows an example in which "Large (unspecified)," "Large (12 rows)," "Large (with toilet)," "Medium," and "Small" are selected from the options for vehicle class details: "Large (unspecified)," "Large (12 rows)," and "Medium." By selecting the "Register" area, a large-scale item registration operation is performed. In response to this registration operation, the travel agency device 2 transmits the above-mentioned registration information (project name, business area, operation period, vehicle class details) to the server 1. Upon receiving the registration information (job name, business area, operation period, vehicle class details), the server 1 stores it in the storage unit 103 (S102), thereby completing the registration of the large job. In FIG. 34, the rectangular area inside the server 1 schematically represents the storage unit 103. FIG. 37 is a diagram showing an example of the registered large-scale project list screen. The registered large-scale project list screen is a screen that can display a list of large-scale projects for which large-scale project registration has been completed. The process of arranging chartered buses for large-scale projects can be roughly divided into the pre-process "vehicle coordination flow" and the post-process "quote request flow."
[0139] (Vehicle adjustment flow) In the "vehicle adjustment flow", first, "registration of required number of vehicles" is executed (S103). The "registration of required number of vehicles" is executed following the processing of S102 in response to an operation on the travel agency device 2 (operation device 204). On the Registered Large Project List screen, radio buttons are provided for each large project, allowing users to select any large project. Figure 37 shows an example where "XX International Competition" has been selected. When you select the "Register required number of units" area, you will be taken to the "Register required number of units screen" (Figure 38). By selecting the "Register Case" area, "Register Itinerary" area, or "Check Arrangement Status" area, you can transition to a screen where you can perform the selected process (registration / confirmation).
[0140] FIG. 38 is a diagram showing an example of the required number registration screen. On the "Required Number Registration Screen", select the "operation area" and enter the required number of vehicles for each operation date and vehicle class details to register. The "operation area" can be selected from among the business areas. Figure 37 shows an example in which "Okayama" is selected as the operation area from among the business areas: Okayama, Hiroshima, and Kagawa. "Operating area: Okayama" specifically refers to the operating sections Okayama-Hiroshima, Okayama-Kagawa, Hiroshima-Okayama, Kagawa-Okayama, and Okayama-Okayama. Similarly, "Operating area: Hiroshima" refers to the operating sections Hiroshima-Okayama, Hiroshima-Kagawa, Okayama-Hiroshima, Kagawa-Hiroshima, and Hiroshima-Hiroshima, while "Operating area: Kagawa" refers to the operating sections Kagawa-Okayama, Kagawa-Hiroshima, Okayama-Kagawa, Hiroshima-Kagawa, and Kagawa-Kagawa.
[0141] As shown in FIG. 38, the required number of vehicles registration screen is provided with an input field (required number of vehicles input field d1) in which the required number of vehicles can be input for each operation date and each detailed vehicle class. Therefore, the travel agency employee can simply operate the operation device 204 to input the required number of vehicles in the required number input field d1. Figure 38 shows an example where the required numbers of vehicles for a large-scale project, "XX International Convention" (operating area: Okayama, Hiroshima, Kagawa; operation period: May 2-6, 2024; operation area: Okayama), are entered as follows: on May 2nd, large (no designation): 50 vehicles, large (12-row): 10 vehicles, medium: 0 vehicles; on May 3rd, large (no designation): 100 vehicles, large (12-row): 10 vehicles, medium: 10 vehicles; on May 4th, large (no designation): 100 vehicles, large (12-row): 0 vehicles, medium: 10 vehicles; on May 5th, large (no designation): 150 vehicles, large (12-row): 10 vehicles, medium: 10 vehicles; and on May 6th, large (no designation): 100 vehicles, large (12-row): 10 vehicles, medium: 0 vehicles. When the "required number of vehicles registration" operation is completed, the travel agency device 2 transmits the registration information (operation area, operation date, vehicle class details, required number of vehicles: required number information) to the server 1. When the server 1 receives the registration information, it stores the received registration information (required number information) in the storage unit 103 (S104).
[0142] Next, "Selection of a source bus company" is executed (S105). The "selection of supplier bus company" is executed in response to an operation on the travel agency device 2 (operation device 204). The "procuring bus operator" is the bus operator that requests the procurement of vehicles, and can also be said to be the bus operator that plans to request a quote or place an order. FIG. 39 is a diagram showing an example of the supplier bus company selection (subscription) screen. A list of bus operators whose operating area is the aforementioned "operating area" is displayed in Figure 39. "Bus operators whose operating area is the operating area" can be identified by referring to the business office master 154 (Figure 10). For this reason, the procurement bus operator selection (subscription) screen displays a list of bus operators who have subscribed to this service. The business office master 154 can also store evaluation information such as each bus operator's "safety evaluation certification type (evaluation certification type regarding safety and efforts to ensure safety)," "number of chartered buses owned," and "cooperative membership (member of the Japan Bus Association)." This also makes it possible to display bus company evaluation information on the procurement bus company selection screen (Figure 39). The supplier bus company selection screen has a check box for each bus company. Therefore, employees of a travel agency can select a bus company for which they wish to request a quote or place an order (i.e., for which they wish to arrange or operate a chartered bus) by checking the checkbox of that bus company. FIG. 39 shows an example in which the AA bus, BB bus, and CC bus are selected. AA Bus is a bus operator whose operating area covers Okayama and Hiroshima prefectures, BB Bus is a bus operator whose operating area covers Okayama prefecture, and CC Bus is a bus operator whose operating area covers Okayama, Hiroshima, Osaka, and Kyoto prefectures. When the “registration of the bus company to be adjusted” operation is completed, the travel agency device 2 transmits the above-mentioned registration information (information on the bus company to be adjusted) to the server 1. When the server 1 receives the registration information, it stores the received registration information (information on the bus operator to be adjusted) in the storage unit 103 (S106). In addition, in response to a predetermined operation (for example, a selection operation in the "Check vehicle status" area), the available vehicle status of any bus operator can also be displayed.
[0143] In addition, bus operators that are not members of this service can also be selected as procurement sources. In this case, information about the desired bus operators can be individually registered, and the "registration and request for adjustment of number of buses" process, which will be described later, can be executed based on the registered information. In this example, it is assumed that MM Bus, whose operating area is Okayama Prefecture and Hiroshima Prefecture, is registered as a bus company that is not a subscriber to this service (not shown).
[0144] Next, the "registration and request for adjustment number of units" is executed (S107). The "registration and request for adjustment of number of vehicles" is executed in response to an operation on the travel agency device 2 (operation device 204). FIG. 40 is a diagram showing an example of the adjusted number registration screen. As shown in FIG. 40, the adjustment number registration screen has an input field for the adjustment number (adjustment number input field d2) in an area corresponding to the operation date and the bus company. The travel agency employee inputs the desired number of vehicles to be adjusted in the adjustment number input field d2. Figure 40 is the adjusted vehicle number registration screen for operation area: Okayama, vehicle class details: large (unspecified), and shows that for AA buses, the following have been entered: May 2nd: 20 units, May 3rd: 40 units, May 4th: 40 units, May 5th: 40 units, May 6th: 40 units; for BB buses, the following have been entered: May 2nd: 10 units, May 3rd: 20 units, May 4th: 20 units, May 5th: 20 units, May 6th: 20 units; and for CC buses, the following have been entered: May 2nd: 10 units, May 3rd: 20 units, May 4th: 20 units, May 5th: 20 units, May 6th: 20 units. When the operation of “registration and request for adjustment number of vehicles” is completed, the travel agency device 2 transmits the above-mentioned registration information (bus company, operation date, vehicle class details, adjustment number of vehicles: adjustment number information) to the server 1. When the server 1 receives the registration information, it stores the received registration information (adjusted number information) in the storage unit 103 (S108).
[0145] Next, the server 1 executes the "number of units adjustment request" process (S108a). Specifically, the server 1 (communication device 104) transmits vehicle number adjustment request information for each bus company to the bus company side. Fig. 41 shows examples of vehicle number adjustment request information. Fig. 41(a) is the vehicle number adjustment request information sent to the bus operator device 3 for the AA bus, Fig. 41(b) is the vehicle number adjustment request information sent to the bus operator device 3 for the BB bus, Fig. 41(c) is the vehicle number adjustment request information sent to the bus operator device 3 for the CC bus, and Fig. 41(d) is the vehicle number adjustment request information sent to the MM bus. In other words, in this example, the adjustment numbers for AA buses are sent to the bus operator device 3 for AA buses (May 2nd: 20 units, May 3rd: 40 units, May 4th: 40 units, May 5th: 40 units, May 6th: 40 units), the adjustment numbers for BB buses are sent to the bus operator device 3 for BB buses (May 2nd: 10 units, May 3rd: 20 units, May 4th: 20 units, May 5th: 20 units, May 6th: 20 units), and the adjustment numbers for CC buses are sent to the bus operator device 3 for CC buses (May 2nd: 10 units, May 3rd: 20 units, May 4th: 20 units, May 5th: 20 units, May 6th: 20 units). Employees of AA Bus to CC Bus can display the adjusted number of buses for their company on the display device 305 of each bus company device 3 (web browser display or app display). The travel agency staff will notify MM Bus of the adjusted number of buses via email, fax, or telephone, without going through server 1. 34 shows that bus operators who are not subscribing to this service communicate directly with the server 1 (S108a), but this is merely a representation for the sake of convenience. In other words, notifications between MM Bus and travel agencies relating to not only S108a but also S109b, S113a, S126a, S127b, S132b, and S133b (described later) are executed without going through the server 1. This allows employees of AA Bus, BB Bus, CC Bus, and MM Bus to check the adjusted number of vehicles for their company. The adjustment quantity request information (FIG. 41) may include display information for input fields for the "responded quantity" and "reserved quantity" (responded quantity field d3 and reserved quantity field d4) described later. This allows the bus operator's device 3 (display device 305) for each of the AA bus, BB bus, CC bus, and MM bus companies to display input fields for "number of responded vehicles" and "number of remaining vehicles" (number of responded vehicles field d3 and number of remaining vehicles field d4), allowing the operator to enter their own number of responded vehicles and number of remaining vehicles in these input fields.
[0146] The bus operator confirms the adjusted number of buses and responds by making an adjustment response (S109a, S109b). The adjusted response consists of the "responded number of units" and the "remaining number of units." An employee of the bus company inputs the number of buses available in the response number field d3 and the available number of buses field d4 displayed on the bus company device 3 of his / her company. The "number of vehicles" is the number of vehicles that can be arranged out of the "adjusted number" requested by the travel agency. Therefore, the "number of vehicles" to be entered should be less than the "adjusted number." In the "excess number of vehicles" field, if it is possible to arrange vehicles in excess of the adjusted number, the excess number is entered. When the input of the response information (responded number of vehicles and available number of vehicles) is completed, the bus operator transmits the response information to the server 1. Bus operators (AA Bus, BB Bus, CC Bus) who subscribe to this service select the "Response" area on the display screen (web image) for the adjustment number request information, and response information (response number and remaining number of vehicles) is sent from the bus operator device 3 to the server 1. Bus operators (MM Bus) that are not members of this service will notify travel agency employees of the response information (number of responded vehicles and number of available vehicles) via email, fax, or telephone. When the server 1 receives the response information (the number of responded vehicles and the number of available vehicles), it stores the received response information in the storage unit 103 (S110). The response information of bus operators that are not members of this service may be stored in the storage unit 103 via manual access to the server 1 by employees of the travel agency.
[0147] Fig. 42 is a diagram showing examples of response information. Fig. 42(a) is the response information sent from the bus operator device 3 of AA Bus to the server 1, Fig. 42(b) is the response information sent from the bus operator device 3 of BB Bus to the server 1, Fig. 42(c) is the response information sent from the bus operator device 3 of CC Bus to the server 1, and Fig. 42(d) is the response information sent from MM Bus to an employee of the travel agency. As shown in Figure 42, for AA Bus, on May 2nd, the adjusted number of vehicles was 20, but the number of responses was 20 and the number of available vehicles was 10; on May 3rd, the adjusted number of vehicles was 40, but the number of responses was 40 and the number of available vehicles was 0; and on May 4th, the adjusted number of vehicles was 40, but the number of responses was 40 and the number of available vehicles was 0; and it is shown that response information indicating this was sent from AA Bus's bus operator device 3 to server 1. Furthermore, for BB Bus, on May 2nd, the adjusted number of vehicles was 10, but the number of responses was 10 and the number of available vehicles was 0; on May 3rd, the adjusted number of vehicles was 20, but the number of responses was 15 and the number of available vehicles was 0; and on May 4th, the adjusted number of vehicles was 20, but the number of responses was 20 and the number of available vehicles was 5; and it is shown that response information indicating this was sent from BB Bus's bus operator device 3 to server 1. Furthermore, for CC Bus, on May 2nd, the adjusted number of vehicles was 10, but the number of responses was 5 and the number of available vehicles was 0; on May 3rd, the adjusted number of vehicles was 20, but the number of responses was 20 and the number of available vehicles was 5; and on May 4th, the adjusted number of vehicles was 20, but the number of responses was 20 and the number of available vehicles was 0; and it is shown that response information indicating this was sent from CC Bus's bus operator device 3 to server 1. Furthermore, for MM Bus, on May 2nd, the adjusted number of vehicles was 5, but the number of responses was 5 and the number of spare vehicles was 5; on May 3rd, the adjusted number of vehicles was 5, but the number of responses was 5 and the number of spare vehicles was 5; and on May 4th, the adjusted number of vehicles was 5, but the number of responses was 5 and the number of spare vehicles was 5; and it is shown that the response information indicating this was notified to the travel agency employees by MM Bus.
[0148] Next, the answer is confirmed (S111). Specifically, the response information stored in the server 1 is displayed (Web display) on the travel agency device 2 to confirm the response. FIG. 43 is a diagram showing an example of the answer information screen. As shown in FIG. 43, the travel agency device 2 can display all the response information of the bus companies that have responded. In the example shown in Figure 43, for AA Bus, the response information displayed indicates that on May 2nd, the adjusted number of vehicles was 20, but the number of responded vehicles was 20 and the number of available vehicles was 10; on May 3rd, the adjusted number of vehicles was 40, but the number of responded vehicles was 40 and the number of available vehicles was 0; and on May 4th, the adjusted number of vehicles was 40, but the number of responded vehicles was 40 and the number of available vehicles was 0. Additionally, for BB Bus, the response information displayed shows that on May 2nd, the adjusted number of vehicles was 10, but the number of responses was 10 and the number of available vehicles was 0; on May 3rd, the adjusted number of vehicles was 20, but the number of responses was 15 and the number of available vehicles was 0; and on May 4th, the adjusted number of vehicles was 20, but the number of responses was 20 and the number of available vehicles was 5. In addition, for CC Bus, the response information displayed shows that on May 2nd, the adjusted number of vehicles was 10, but the number of responses was 5 and the number of available vehicles was 0; on May 3rd, the adjusted number of vehicles was 20, but the number of responses was 20 and the number of available vehicles was 5; and on May 4th, the adjusted number of vehicles was 20, but the number of responses was 20 and the number of available vehicles was 0. In addition, for MM Bus, the response information displayed shows that on May 2nd, the adjusted number of vehicles was 5, but the number of responses was 5 and the number of available vehicles was 5; on May 3rd, the adjusted number of vehicles was 5, but the number of responses was 5 and the number of available vehicles was 5; and on May 4th, the adjusted number of vehicles was 5, but the number of responses was 5 and the number of available vehicles was 5.
[0149] Next, the travel agency registers and notifies the planned number of vehicles (S112). FIG. 44 is a diagram showing an example of the planned number registration screen. As shown in FIG. 44, the travel agency device 2 can display a planned number registration screen on which the planned number of vehicles for the bus company can be entered in the planned number field d5 while displaying response information from the bus company. The information on each planned number of vehicles entered in the planned number of vehicles field d5 is sent to the corresponding bus operator. In the example shown in Figure 44, for AA buses, the planned number of vehicles for May 2nd: 25 vehicles, the planned number of vehicles for May 3rd: 40 vehicles, and the planned number of vehicles for May 4th: 40 vehicles is input; for BB buses, the planned number of vehicles for May 2nd: 10 vehicles, the planned number of vehicles for May 3rd: 15 vehicles, and the planned number of vehicles for May 4th: 23 vehicles is input; for CC buses, the planned number of vehicles for May 2nd: 5 vehicles, the planned number of vehicles for May 3rd: 25 vehicles, and the planned number of vehicles for May 4th: 20 vehicles is input; and for MM buses, the planned number of vehicles for May 2nd: 10 vehicles, the planned number of vehicles for May 3rd: 10 vehicles, and the planned number of vehicles for May 4th: 10 vehicles is input. When the "Number of vehicles notification" area is selected, the travel agency device 2 transmits the planned number of vehicles information for each bus company to the server 1 (planned number registration / notification). When the server 1 receives the planned number of vehicles information transmitted from the travel agency device 2, it stores it in the storage unit 103 (S113). This registers the planned number of vehicles. This registration is performed by the first allocation means 131. That is, the first allocation means 131 executes a process of allocating the planned number of buses to a plurality of bus operators in advance in response to an operation of the travel agency device 2.
[0150] The server 1 executes the "planned number notification" process (S113a). Specifically, the server 1 (communication device 104) notifies the bus operator device 3 of the planned number of vehicles information for each bus operator through API cooperation. That is, the server 1 transmits the planned number of vehicles information to the bus operator device 3. Figure 45 is a diagram showing an example of planned number of vehicles information transmitted from server 1 to the bus operator side. Figure 45(a) is the planned number of vehicles information transmitted to bus operator device 3 for AA bus, Figure 45(b) is the planned number of vehicles information transmitted to bus operator device 3 for BB bus, and Figure 45(c) is the planned number of vehicles information transmitted to bus operator device 3 for CC bus. Note that Figure 45(d) is the planned number of vehicles information notified to MM bus by a travel agency employee or the like via email, fax, or telephone (S114b). As shown in Figure 45(a), the planned number of vehicles for May 2nd: 25 vehicles, the planned number of vehicles for May 3rd: 40 vehicles, and the planned number of vehicles for May 4th: 40 vehicles are transmitted from the server 1 to the bus operator device 3 of AA Bus. Also, as shown in Figure 45(b), the planned number of vehicles for May 2nd: 10 vehicles, the planned number of vehicles for May 3rd: 15 vehicles, and the planned number of vehicles for May 4th: 23 vehicles are transmitted from the server 1 to the BB Bus bus operator device 3. Also, as shown in Figure 45(c), the planned number of vehicles for May 2nd: 5 vehicles, the planned number of vehicles for May 3rd: 25 vehicles, and the planned number of vehicles for May 4th: 20 vehicles are transmitted from the server 1 to the CC bus operator device 3. Also, as shown in Figure 45(d), it is shown that the planned number of vehicles for May 2nd: 10 vehicles, the planned number of vehicles for May 3rd: 10 vehicles, and the planned number of vehicles for May 4th: 10 vehicles have been notified to MM Bus.
[0151] Each bus company secures a vehicle (S114a, S114b). Specifically, each bus operator device 3 (operation management package) performs processing related to securing vehicles (for example, recording, notifying, and displaying the planned number of vehicles associated with vehicle class, date, etc., updating vehicle usage status information, etc.) based on the planned number of vehicles information received from the server 1 based on API integration. This will require each bus operator to secure the planned number of vehicles. The bus operator's device 3 can also display the planned number of buses. The bus operator device 3 of the AA bus displays the information shown in FIG. 45(a). The bus operator device 3 of the BB bus displays the information shown in FIG. 45(b). The bus operator device 3 of the CC bus displays the information shown in FIG. 45(c). The MM bus checks the information shown in FIG. 45(d) that has been notified via email, fax, or telephone. As a result, AA Bus confirms that the planned number of vehicles for May 2nd is 25, the planned number of vehicles for May 3rd is 40, and the planned number of vehicles for May 4th is 40 (Figure 45(a)). BB Bus also confirms that the planned number of buses for May 2nd is 10, the planned number of buses for May 3rd is 15, and the planned number of buses for May 4th is 23 (Figure 45(b)). In addition, CC Bus confirms that the planned number of buses for May 2nd is 5, the planned number of buses for May 3rd is 25, and the planned number of buses for May 4th is 20 (Figure 45(c)). In addition, MM Bus confirms that the planned number of vehicles for May 2nd is 10, the planned number of vehicles for May 3rd is 10, and the planned number of vehicles for May 4th is 10 (Figure 45(d)). Each bus operator will determine the number of vehicles required based on the planned number above and secure the vehicles accordingly. This is the end of the "vehicle adjustment flow" processing.
[0152] (Quote request flow) The "quote request flow" is executed after a "considerable period" has elapsed following the "vehicle adjustment flow." When the "Vehicle Adjustment Flow" is executed, details such as the itinerary are often not yet decided, but if a request to arrange vehicles is made just before placing an order, the bus company may not be able to accommodate, so an approximate number of vehicles is requested in advance. On the other hand, the "quote request flow" is a flow that is executed after details such as the itinerary have been decided and before an order is placed with the bus company. The "equivalent period" may be, for example, several months, one year, several weeks, or several days, but is not limited to these and may be one day (the next day) or zero days (the same day).
[0153] In the "quote request flow," first, the process and schedule are registered (S121). FIG. 46 is a diagram showing an example of the itinerary registration 1 screen, and FIG. 47 is a diagram showing an example of the itinerary registration 2 screen. First, with the Itinerary Registration 1 screen (FIG. 46) displayed, the first information is entered in the input field d6. The "first information" includes the itinerary name, departure area, arrival area, number of nights, vehicle class details, and information indicating whether the itinerary is registered. After inputting the first information, the user selects the "Register" area to complete the registration of the first information. The lower part of Figure 46 shows that the travel agency device 2 (display device 205) displays that the following has been registered: itinerary name: Okayama Airport to Okayama H, vehicle class details: large (not specified) and medium, itinerary name: Hiroshima Airport to Okayama H, vehicle class details: large (not specified) and medium, itinerary name: Takamatsu Airport to Okayama H, vehicle class details: large (not specified), medium and small, itinerary name: Okayama H to Okayama H, vehicle class details: large (not specified), etc. When the registration of the first information is completed, the display screen of the travel agency device 2 transitions to the itinerary registration 2 screen (FIG. 47).
[0154] Next, with the itinerary registration 2 screen (FIG. 47) displayed, the second information is entered in the input field d7. "Second information" includes the departure date (operation date), vehicle class details, number of vehicles (required number of vehicles), etc. After inputting the second information, the user selects the "Register" area to complete the registration of the second information. The bottom of Figure 47 shows that for the itinerary name: Okayama Airport to Okayama H, on departure date: May 2nd, vehicle class details: large (not specified): 20 vehicles, medium: 3 vehicles have been registered, on departure date: May 3rd, vehicle class details: large (not specified): 5 vehicles, and on May 4th, vehicle class details: large (not specified): 10 vehicles, medium: 3 vehicles have been registered, as displayed on travel agency device 2 (display device 205). In response to this, the travel agency device 2 transmits the registration information (such as the itinerary name, operation dates, and required number of vehicles) to the server 1 (S121). When the server 1 receives the registration information from the travel agency device 2, it stores it in the storage unit 103 (S122). FIG. 48 is a diagram showing an example of an entire journey information screen for the XX International Convention (operation area: Okayama, Hiroshima, Kagawa). Figure 48 shows that the travel agency device 2 (display device 205) displays all itinerary information that has been registered, such as "Departure date: May 2nd, itinerary name: Okayama Airport - Okayama H, vehicle class details: large (not specified), number of vehicles: 20," "Departure date: May 2nd, itinerary name: Okayama Airport - Okayama H, vehicle class details: medium, number of vehicles: 3," "Departure date: May 3rd, itinerary name: Okayama Airport - Okayama H, vehicle class details: large (not specified), number of vehicles: 5," "Departure date: May 4th, itinerary name: Okayama Airport - Okayama H, vehicle class details: large (not specified), number of vehicles: 5," and "Departure date: May 4th, itinerary name: Okayama Airport - Okayama H, vehicle class details: medium, number of vehicles: 3." When the registration of all the itinerary information is completed, the display screen of the travel agency device 2 transitions to a screen for selecting a bus company to which a quote is to be requested (FIG. 49).
[0155] Next, the bus company to which the estimate is to be requested is selected (S123). FIG. 49 is a diagram showing an example of a screen for selecting a bus company to which a quote is requested. The screen for selecting bus operators to request a quote from will display bus operators who have notified the number of reservations for the XX International Convention (i.e., bus operators whose operating areas include one or more of Okayama Prefecture, Hiroshima Prefecture, and Kagawa Prefecture). The travel agency employee operates the travel agency device 2 (operation device 204) to select multiple bus companies to request a quote from among the bus companies displayed on the quote request destination bus company selection screen. When a quote request destination is selected, the travel agency device 2 transmits to the server 1 the bus company from which the quote request has been made (requested bus company information). When the server 1 receives the requested bus operator information transmitted from the travel agency device 2, it stores it in the storage unit 103 (S124). Furthermore, when a bus company to which a quote is to be requested is selected, the display screen of the travel agency device 2 transitions to a quote information input screen (FIG. 50). FIG. 50 is a diagram showing an example of the quotation request information input screen. FIG. 50(a) shows the screen at the time when the quotation request information for the first process is entered. Specifically, when the AA bus is selected (Figure 49), a screen is displayed (not shown) that allows you to select any itinerary, and Figure 50(a) shows the screen that is displayed when you select any itinerary (Okayama Airport to Okayama H) on that screen. Vehicle class details and number of vehicles can be entered via this screen. That is, Figure 50(a) shows an example in which AA Bus is selected, the route for May 2nd (Okayama Airport to Okayama H) is selected, and the vehicle class details: large (not specified) and number of vehicles: 20 are entered. When the "Register" area is selected, the quotation request information registration process is executed. By performing this registration process for each bus company and each itinerary, quotation request information for the entire itinerary can be registered. FIG. 50(b) shows the screen after the quotation request information for the entire process of the XX international tournament has been entered and registered. As shown in Figure 50(b), once the quotation request information for the entire process has been registered, the "quote request" area is displayed. When the "quote request" area is selected, the quotation request process is executed (S125). Specifically, the travel agency device 2 transmits quotation request information for the entire itinerary to the relevant bus operators separately.
[0156] When the server 1 receives the quotation request information transmitted from the travel agency device 2, it stores the quotation request information in the storage unit 103 (S126) and transmits it to the bus operator device 3 and the like (S126a). For example, to AA Bus, send the following request for quotation information: "Project name: XX International Convention, Operation area: Okayama, Hiroshima, Kagawa, Departure date: May 2, 2024, Route name: Okayama Airport to Okayama H, Vehicle class details: Large (unspecified), Number of vehicles: 20." Send CC Bus the following request for quotation: "Project name: XX International Tournament, Operation area: Okayama, Hiroshima, Kagawa, Departure date: May 2, 2024, Route name: Okayama Airport to Okayama H, Vehicle class details: Medium, Number of vehicles: 3" or the following request for quotation: "Project name: XX International Tournament, Operation area: Okayama, Hiroshima, Kagawa, Departure date: May 4, 2024, Route name: Okayama Airport to Okayama H, Vehicle class details: Medium, Number of vehicles: 3". It is also possible to generate a single quotation request information item that is addressed to the same bus company, and then transmit the generated quotation request information item to the bus company device 3 of the corresponding bus company.
[0157] The bus company submits a quotation response (S127a, S127b). First, when the bus business operator device 3 receives the quotation request information transmitted from the server 1, it displays the quotation request information. That is, an employee of the bus business operator visually checks the displayed quotation request information to confirm the contents of the quotation request. Then, the bus company device 3 sends an estimate. For example, AA Bus creates quotation information of "6 million yen" in response to quotation request information of "Project name: XX International Convention, Operation area: Okayama, Hiroshima, Kagawa, Departure date: May 2, 2024, Itinerary name: Okayama Airport to Okayama H, Vehicle class details: Large (not specified), Number of vehicles: 20" and sends the quotation information to Server 1. Note that the quotation information can include detailed quotation information, but the explanation thereof is omitted here.
[0158] When the server 1 receives the estimate responses (quotation information) sent from each bus operator device 3, it generates information summarizing the estimate responses (quotation response summary information), stores it in the memory unit 103, and sends it to the travel agency device 2 (S128). When the travel agency device 2 receives the estimate response summary information transmitted from the server 1, it displays the estimate response summary information. This allows the travel agency to check the quotation response (S129). FIG. 51 is a diagram showing an example of an estimate response summary information screen displayed on the travel agency device 2. Figure 51 shows that in response to a request for a quote for "Project name: XX International Convention, Operation area: Okayama, Hiroshima, Kagawa, Departure date: May 2, 2024, Route name: Okayama Airport to Okayama H, Vehicle class details: Large (not specified), Number of vehicles: 20," AA Bus responded with a quote of "6 million yen."
[0159] Next, the travel agency executes the order (S130). FIG. 52 is a diagram showing an example of an order screen displayed on the travel agency device 2. An "Order" area is displayed on the order screen, and by selecting this "Order" area, the order processing for the contents (order information) displayed on the order screen will be executed for each bus operator. When the order processing is executed, the order information is sent to the server 1. When the server 1 receives the order information transmitted from the travel agency device 2, it stores the order information in the storage unit 103 (S131) and transmits it to each bus operator (S131a). The "order information" includes the project name, departure date, itinerary name, vehicle class details, number of vehicles, etc. For example, the ordering information for AA Bus includes: "Project name: XX International Convention, Operation area: Okayama, Hiroshima, Kagawa, Departure date: May 2, 2024, Route name: Okayama Airport to Okayama H, Vehicle class details: Large (unspecified), Number of units (ordered): 20 units." The order information for MM Bus includes "Project name: XX International Convention, Operation area: Okayama, Hiroshima, Kagawa, Departure date: May 4, 2024, Route name: Okayama Airport to Okayama H, Vehicle class details: Large (unspecified), Number of units (ordered): 10 units." This order information is notified to MM Bus by employees of the travel agency, etc. via email, fax, or telephone.
[0160] Upon receiving the order information, the bus operator device 3 executes order acceptance processing (S132a, S132b). Specifically, the bus operator device 3 stores the received order information in the storage unit 103 and sets the status to "ordered" (S132a). The bus operator device 3 can also display on a display device that the order has been received. In response to the order, the bus company's employees secure the ordered number of vehicles (S133a, S133b). The bus operator device 3 transmits order information (not shown) to the server 1 in response to a predetermined operation. When the server 1 receives the order information transmitted from the bus operator device 3 or the like, the server 1 stores the order information in the storage unit 103 (S134). The server 1 also transmits the order information to the travel agency device 2. When the travel agency device 2 receives the order information transmitted from the server 1, it completes the order (S135). For MM Bus, the "order" is completed when an employee of the travel agency notifies the order information via email, fax, or telephone (S132b), and the vehicle is reserved (S133b). The employee of MM Bus completes the order by notifying the travel agency employee of the order information via email, fax, or telephone (S135). The order information and order information regarding MM Bus may be stored in server 1, or may be stored in storage unit 103 via access to server 1 by an employee of the travel agency (S134).
[0161] (Automatic quote request) Next, the automatic quotation request will be described. The automatic quotation request is a configuration related to the aforementioned "function to automatically allocate the number of buses requested for quotation in large-scale projects," and has the function to automatically select bus operators to request quotation from and allocate the required number of buses. That is, the aforementioned selection of bus operators to whom estimates are requested (see FIG. 50) and allocation of the number of buses to which estimates are requested to each bus operator are automatically performed.
[0162] FIG. 53 is a flowchart showing the processing procedure for determining the bus company to which a quote is to be requested and the number of vehicles for which a quote is to be requested. As shown in FIG. 53, in this process, first, a preparation process is executed (S201). The preparation process includes a first preparation process and a second preparation process. It is assumed that the planned number of vehicles has been allocated and the details of the itinerary have been finalized.
[0163] As the first preparation process, the server 1 (controller 101) counts the “number of reserved vehicles” for each detailed vehicle rank, for each bus company, and for each date, and stores the counting results in the memory unit 103. FIG. 54 is an example of aggregated data of the number of reservations by date and by bus company for the project name: XX International Convention and vehicle class details: large (unspecified). Please note that the aggregated data on the number of reservations for vehicle class details (large (12-row) and medium-sized vehicles) will be omitted.
[0164] As the second preparation process, the server 1 (controller 101) tallies the "estimated required number of vehicles" for each detailed vehicle class, each journey, and each date, and stores the tallied results in the storage unit 103. It is assumed that the entire itinerary for the XX International Tournament has been decided, and the estimated number of vehicles required for each itinerary and date has been determined. FIG. 55 is an example of aggregate data of the estimated number of vehicles required for each itinerary and each date for the project name: XX International Convention and vehicle class details: large (unspecified). Figure 55 shows that the estimated required number of vehicles for Route 1: Okayama Airport to Okayama H is 25 vehicles on May 2nd, 30 vehicles on May 3rd, and 10 vehicles on May 4th, and the estimated required number of vehicles for Route 2: Hiroshima Airport to Okayama H is 20 vehicles on May 2nd, 10 vehicles on May 3rd, and 20 vehicles on May 4th.
[0165] After the preparation process, the control unit 101 determines the target journey (S201). The "target process" is a process that is the target when determining the company to request an estimate from and the number of vehicles to request an estimate for each process. In this embodiment, the target journeys are selected in the following order (ascending order): journey 1 → journey 2 → ... In other words, initially, "travel 1" is determined as the target journey. Next, the control unit 101 determines the target date (S202). The "target date" is the target date (operation date) when determining the company and the number of vehicles for which estimates are requested for each date. In this embodiment, the target dates are selected in ascending order, such as first day → second day → .... In other words, "May 2nd" is initially determined as the target date. The target itinerary and target date are not limited to those described above, and may be determined based on various other criteria (for example, descending order, or order of most or least number of reserved vehicles, etc.).
[0166] Next, the control unit 101 determines the bus company to which the estimate is to be requested (S204). Specifically, the bus operator is determined based on the total number of reservations, assuming that the bus operator has a number of reservations set for the target itinerary and target date. "Total number of reserved vehicles" is the total number of reserved vehicles, for example, 155 AA buses, 110 BB buses, and 90 CC buses (Figure 54). More specifically, the bus operators are determined in descending order of total number of reservations. For example, when determining the party to request a quote for journey 1: May 2, which corresponds to the first trip, the bus company with the largest number of reservations, AA Bus, is determined to be the party to request a quote. When there are multiple bus operators with the same total number of reservations, the bus operator may be determined based on a specific rule. For example, all bus operators may be ranked in advance, and the bus operators with the highest rankings may be given priority when requesting quotes. Specifically, the bus operator with the highest ranking (one company) may be selected, or several companies (multiple companies) may be selected from the top rankings. The "ranking" can be set, for example, so that the more units planned, the higher the ranking, or the more units actually ordered in the past (last year), or it can also be set taking into account evaluation information such as the type of safety evaluation certification, number of units owned, and cooperating members.
[0167] Next, the control unit 101 determines the number of units for which a quotation is requested (S205). Specifically, if "number of reserved vehicles≧number of vehicles required for estimation" (first condition) is met, the "number of vehicles requested for estimation" is determined as the "number of vehicles required for estimation." For example, the estimated required number of vehicles (initial) for journey 1: May 2nd is 25 (Figure 55), and the number of vehicles reserved (initial) for AA Bus on May 2nd is 30 (Figure 54), so the first condition is met. In this case, the number of vehicles requested for a quote from AA Bus for journey 1: May 2nd is determined to be 25 (estimated required number of vehicles). If multiple bus companies are requested to make quotations, the number of requested quotations may be allocated equally to each bus company, or may be allocated proportionally based on the remaining number ratio (the ratio of the remaining number of requested quotations to the planned number of cars). If "number of reserved units < number of units required for quotation" (second condition) is met, the "number of units requested for quotation" will be determined as the "number of reserved units." For example, if the quote request destination for journey 1: May 3rd has been determined to be AA Bus, the estimated required number of vehicles (initial) for journey 1: May 3rd is 30 (Figure 55), and the number of vehicles reserved (initial) for AA Bus on May 3rd is 25, so the second condition is met. In this case, the number of vehicles requested for quote from journey 1: May 3rd's quote destination: AA Bus is determined to be 25 (number reserved). The determined details (journey 1: date: bus company: number of buses requested for quotation) are stored in the storage unit 103. As a result, the requested quotation quantity is registered. The requested quotation quantity is registered by the second allocation means 132. That is, the second allocation means 132 executes a process of allocating the estimated required number of vehicles (specific number of vehicles) to a plurality of bus operators based on the planned number of vehicles allocated by the first allocation means 131.
[0168] Next, the estimated required number of units is updated (S206). Specifically, the number of units required for estimation is updated to a number obtained by subtracting the number of units for which an estimate has been requested. For example, if the requested quotation quantity for AA Bus for journey 1: May 2nd is determined to be 25 units, the estimated required quantity for journey 1: May 2nd: 25 units will be updated to 0 units, which is the estimated required quantity minus the requested quotation quantity. In addition, if the requested number of bids for AA Bus on May 3rd, Path 1, is determined to be 25 units, the estimated required number of 30 units on May 3rd will be updated to 5 units, which is the estimated required number minus the requested number of bids.
[0169] Next, the control unit 101 updates the planned number of vehicles (S207). Specifically, the planned number is updated to the number obtained by subtracting the number of units for which a quote has been requested. For example, if the number of AA buses requested for quotation on May 2nd for itinerary 1 is determined to be 25, the planned number of AA buses for May 2nd (30) will be updated to 5, which is the planned number minus the number of AA buses requested for quotation. In addition, if the number of AA Buses requested for quotation on May 3rd for Itinerary 1 is determined to be 25, the planned number of AA Buses on May 3rd (25) will be updated to 0, which is the planned number minus the number of quotations requested.
[0170] In this way, the allocation of the estimated required number of units (second allocation means 132) is composed of allocations for multiple journeys (all journeys), including allocation for the first journey (e.g., journey 1) and allocation for the second journey (e.g., journey 2) following the first journey, and the allocation for the second journey (travel 2) is carried out based on the allocation results for the first journey (travel 1). For example, an update process is performed to subtract the number of units requested for quotation allocated in step 1 from the initially planned number of units and the initially estimated number of units required, and the number of units requested for quotation in step 2 is determined based on the updated planned number of units and the updated number of units requested for quotation.
[0171] Next, the control unit 101 determines whether the estimated required number of units is "0" (S208). That is, it is determined whether the estimated required number of units after the update (S206) is "0 units." If the estimated required number of units is determined to be "0" (S208-Yes), the process proceeds to S209, and if the estimated required number of units is not determined to be "0" (S208-No), the process returns to S204. For example, if the estimated required number of units for Step 1 on May 2nd has been updated to "0 units", the process proceeds to S209, but if the estimated required number of units for May 2nd has not been updated to "0 units", the process returns to S204. When the process returns to S204, the processes of S204 to S208 are repeated until the estimated required number of units for the same date becomes "0".
[0172] If the estimated required quantity is determined to be "0" (S208-Yes), the control unit 101 determines whether there are any undetermined dates (S209). Specifically, an "undecided date" refers to a date on which the estimated required number of units is not "0." If it is determined that there is an undetermined date (S209-Yes), the process returns to S204, and if it is not determined that there is an undetermined date (S209-No), the process proceeds to S210. For example, if the estimated required quantities for May 2nd to 4th in itinerary 1 have all been updated to "0 units," the process proceeds to S209. However, even if the estimated required quantities for May 2nd in itinerary 1 have been updated to "0 units," if the estimated required quantities for May 3rd and May 4th have not been updated to "0 units," the process returns to S203. When the process returns to S203, the processes of S203 to S209 are repeated until the estimated required number of units for all dates becomes "0".
[0173] If it is determined that there is no undetermined date (S209-No), the control unit 101 determines whether there is an undetermined itinerary (S210). Specifically, an "undecided itinerary" refers to a itinerary that includes a date on which the estimated required number of units is not "0." If the estimated number of vehicles required for all trips has been updated to "0" (S210-Yes), the process ends. However, if there is a date on which the estimated number of vehicles required for even one trip has not been updated to "0" (S210-No), the process returns to S202. When returning to S202, the processes of S202 to S210 are repeated until the estimated required number of vehicles for all dates of all journeys becomes "0".
[0174] When this is completed, a quotation request is made (S125 in FIG. 34). That is, the bus operator device 3 determines the number of vehicles to be requested for quotation through the process of S205 described above and transmits the quotation request information including the number of vehicles to be requested for quotation through the process of S205 described above (S126a in FIG. 34). As a result, the bus operator of the bus operator device 3 that received the quotation request information can confirm the requested number of vehicles included in the quotation request information and can respond with a quotation (S127a, S127b in FIG. 34). The travel agency can then confirm the estimate response (S129 in FIG. 34) and proceed to placing an order (S130 in FIG. 34). The number of vehicles registered at the time of ordering will be reflected as the number of vehicles in use on the vehicle status confirmation screen.
[0175] As such, the chartered bus system of this embodiment comprises a first allocation means 131 that allocates a planned number of vehicles to multiple bus operators in advance in accordance with the operation of the travel agency device 2, a second allocation means 132 that allocates a specific number of vehicles (estimated required number of vehicles) to multiple bus operators based on the planned number of vehicles allocated by the first allocation means 131, a quotation request information generation means 133 that generates quotation request information for each bus operator based on the allocation result (number of vehicles requested for quotation) allocated by the second allocation means 132, and a quotation request means 134 that transmits the quotation request information to each bus operator device 3 managed by each bus operator. As a result, in the past, when chartered buses were used as a means of transportation for large events such as the Olympics or the National Sports Festival, that is, when a large number of vehicles were required, travel agencies had to manually request vehicle coordination (reservation) from multiple bus companies, and then, while referring to the responses, select bus companies for each itinerary and request quotes, performing almost all of this tedious processing.However, with the present invention, the main parts of this processing can be performed automatically. This makes it possible to smoothly and easily arrange charter buses for large events. For bus operators, simply by subscribing to this service, they can gain opportunities to receive large orders from various travel agencies without having to build a new system, and can smoothly secure vehicles for those orders.Furthermore, even if they are not subscribing to this service, they can still receive opportunities to receive large orders. In addition, the chartered bus system of this embodiment can automatically generate quotes that meet the conditions of both travel agencies (including end users) and bus operators, providing basic functions and guide-related functions that are useful to both parties, as well as functions that allow for effective arrangements for chartered buses for large events.
[0176] (About the support display function) As mentioned above, the second allocation means 132 can allocate the estimated required number of buses (specific number of buses) to "multiple bus companies" in response to input operations on the travel agency device 2. Therefore, the chartered bus system (server 1) of this embodiment is equipped with a support display means 135 that displays information on the travel agency device 2 to support input operations on the travel agency device 2 when allocating the estimated required number of vehicles to multiple bus operators. For example, the estimated number of units can be displayed (visualized) on the quotation request information input screen (FIG. 50) so that it can be referenced when inputting quotation request information, and the input number can be changed. In addition to or instead of the "planned number of vehicles," the "proportion of planned number of vehicles" can also be displayed (visualized). "Planned number ratio" is the ratio of each bus operator's total planned number of vehicles to the total planned number of vehicles for large-scale projects. For example, we will explain the case where the total planned number of vehicles: 100 is allocated to three bus companies: A Bus, B Bus, and C Bus. In this case, if the total planned number of buses A is 50, the total planned number of buses B is 40, and the planned number of buses C is 10, the planned number ratio for buses A: 50% (= 50 / 100), the planned number ratio for buses B: 40%, and the planned number ratio for buses C: 10% will be displayed, and you can refer to these to input or change the number of buses you wish to request a quote for from each bus operator.
[0177] Furthermore, the "planned number of units" and the "number of units requested for quotation" can be displayed (visualized) side by side for comparison. It is also possible to visualize the "proportion of planned units" and the "proportion of units for which estimates have been requested" so that they can be compared. In particular, the "planned number of units proportion graph" and the "quote requested number of units proportion graph" can be displayed side by side for comparison. FIG. 56 is an example of a screen displaying a planned number ratio graph and a quotation request number ratio graph in association with each other. FIG. 56(a) is an example of a screen displaying a bar graph of the planned number ratio and a bar graph of the quotation request number ratio arranged vertically. FIG. 56(b) is an example of a screen displaying a pie chart of the planned number of units and a doughnut chart of the number of units for which estimates have been requested, arranged inside and outside. This screen allows the user to input or change the requested quotation quantity while referring to the planned quantity ratio. For example, for BB Bus, it is clear at a glance that the proportion of requested quotations is low compared to the proportion of planned buses. Therefore, the travel agency staff can consider increasing the number of buses for which they request quotes from BB Bus. If you wish to increase the number of units for which you wish to request a quote, simply change the values on the quote request information input screen (Figure 50).
[0178] The number of units for which a quote is requested can also be changed by selecting and operating the graph area. For example, as shown in Figure 56, if the ratio of requested quotations for the BB bus is less than the planned ratio, you can click on the boundary of the BB bus with the mouse, move the cursor in the direction that increases the ratio of requested quotations, and release it (drag and drop), thereby increasing the number of requested quotations for the BB bus in accordance with the amount of movement (see the arrow in the figure). Furthermore, since the graph of the number of units requested for quotation is composed of graphs of multiple processes, by placing the cursor at any position, it is possible to display (visualize) the graph area of the process corresponding to the placement position. That is, by simply placing the cursor over a graph area, the user can visually confirm the number of vehicles for which quotations have been requested for the journey corresponding to that area. Furthermore, it is possible to easily coordinate between bus operators regarding the number of buses for which quotations are requested. As shown in FIG. 56, a case will be described in which the ratio of the number of HH buses for which quotations have been requested is greater than the ratio of the planned number, and the number of BB buses for which quotations have been requested is less than the ratio of the planned number. In this case, if you can visually determine that the size of the graph area when you place the cursor at any position on the HH bus is approximately equivalent to the shortfall in the number of units for which quotes have been requested compared to the planned number of units on the BB bus (the difference between the arrows in Figure 56), click on the ``any position'' in the graph area of the HH bus, move the cursor into the graph area of the BB bus, and release it (drag and drop). This allows the number of BB buses for which quotations are requested to be increased by the amount of the shortage, and the number of HH buses for which quotations are requested to be decreased by the amount of the shortage. In other words, the number of units for which a quote is requested can be adjusted smoothly using a GUI (Graphical User Interface). As described above, the chartered bus system of this embodiment is equipped with a distinctive support display function, making it possible to rationally arrange chartered buses for large events.
[0179] (About the consolidating company) FIG. 57 shows a modified example of the large-item registration screen. On the large-scale project registration screen shown in Figure 57, by selecting the "Select a consolidating company" area, a bus company (referred to as a "consolidating company") that will consolidate the large-scale project can be selected from among the bus companies. Multiple consolidating companies can also be selected. In that case, the "travel agency" should be read as the "aggregator company" and the travel agency device 2 should be read as the bus operator device 3. In other words, in this case, instead of the travel agency employee, an employee of the aggregating company operates the bus operator device 3 to register the required number of vehicles, select the bus operator to be adjusted, register the adjusted number of vehicles, register the planned number of vehicles, etc.
[0180] (Method for determining the company to request a quote from and the number of units to request a quote from) The bus company to which the quote is requested can be determined not only based on the total number of reservations, but also based on the rate of quote requests and the number of remaining buses. Specifically, first, the lower the "quote request rate," the higher the priority, and second, the higher the "remaining number of units," the higher the priority. The "quotation request rate" is the ratio of the number of units for which quotation requests have been made to the planned number of units. The "remaining number of units" is the number of units for which quotation requests remain compared to the planned number of units, and can be calculated by subtracting the total planned number of units from the number of units for which quotation requests have been made. For example, if the total planned number of buses is 150 AA buses, 50 BB buses, and 100 CC buses, and the estimated number of buses required for the first trip is 30, AA buses will be selected as the bus supplier for quotes, and the number of buses to be requested for quotes will be determined to be 30. At this point in time, the "quotation request rate" is 20% for AA buses, 0% for BB buses, and 0% for CC buses, and the "remaining number of buses" is 120 for AA buses, 50 for BB buses, and 100 for CC buses. In the second step, AA Bus is excluded from the list of companies to which bids are requested because AA Bus receives more bids than other bus operators. Here, the quotation request rates for both BB buses and CC buses are 0%, but the remaining number of CC buses (100) is greater than the remaining number of BB buses (50). Therefore, if the estimated required number of vehicles for the second journey is 10, the company to request a quote from will be determined to be CC Bus, and the number of vehicles to request a quote from will be determined to be 10. The planned number of units used to calculate the "quote request rate" and the "remaining number of units" may be the total planned number of units for the entire job. In addition, instead of the "quotation request rate," an "order rate" which is the ratio of the number of units already ordered to the planned number of units may be used. In this case, the "remaining number of units" is the number of units remaining for which quotation requests have been made relative to the planned number of units, and can be calculated by subtracting the number of units ordered from the total planned number of units.
[0181] (Regarding vehicle arrangement status confirmation) The server 1 manages (stores) the vehicle arrangement status for each operating area, each vehicle class, each bus company, and each operating date. The travel agency device 2 can display and confirm the vehicle arrangement status. By selecting the bus company you would like to request a quote from, you can display the vehicle arrangement status screen. For bus operators who subscribe to the service, the number of vehicles used will be counted at the time of ordering, and the number of vehicles used and unused will be displayed. For bus operators that are not subscribed to the service, the number of vehicles in use can be entered directly and the number of unused vehicles will be displayed.
[0182] (Variation) Artificial processing can also be performed automatically or semi-automatically using AI (Artificial Intelligence). For example, the bus company to which the estimate is requested and the number of buses to be estimated are basically manually determined by an employee of the travel agency (S121 to S125), but they may also be determined by AI. Specifically, for past large-scale projects, past accumulated information consisting of bus operators that allocated planned numbers of vehicles and the planned number of vehicles for those bus operators, as well as bus operators that received requests for quotes and the number of vehicles requested for quotes from those bus operators, is used as training data for machine learning (supervised learning). The training data may include one or more pieces of information including the operating area, route, vehicle class details, operating period, and date. This makes it possible to generate a prediction model that outputs the bus company to which a quotation is requested and the number of buses to be quoted by inputting the bus company to which the quotation is to be requested and the number of buses to be quoted by that bus company. If such a prediction model is stored on server 1, when an inquiry for a new large project is received, the bus operator and the planned number of vehicles can be input into the prediction model, and the bus operator to which a quote has been requested for the large project and the number of vehicles for which a quote has been requested can be output from the prediction model. The server 1 generates quotation request information based on the output bus operators to which quotation requests have been made and the number of buses for which quotation requests have been made, and transmits the generated quotation request information to each bus operator device 3. This allows the quotation request to be executed automatically.
[0183] It is also possible to utilize generative AI (artificial intelligence chatbots) such as ChatGPT. For example, the total planned number of vehicles (A) shown in Figure 54 and the total estimated number of vehicles required (B) shown in Figure 55 are read into the generation AI in advance, and a configuration is set up that automatically prompts for commands such as "Based on A and B, please determine the bus company and the number of vehicles to be requested for a quote for each itinerary and each date," as well as predetermined conditions (such as determining the bus operator in descending order of the total number of reservations, applying specific rules as necessary, and determining the number of vehicles to be requested for a quote based on the above-mentioned method based on the first and second conditions). Then, the server 1 automatically generates quotation request information based on the output information (the bus operator to which the quotation is requested and the number of vehicles for which quotation is requested), and transmits the generated quotation request information to each bus operator device 3.
[0184] (others) In the above embodiment, the case where the planned number of units and the estimated number of units required are updated at the quotation request stage has been described. However, in addition to or instead of this, the planned number of units and the number of units required to be ordered may also be updated at the ordering stage. For example, in the case of the planned number of units, a process is executed to subtract the ordered number of units from the planned number of units when the order is completed. Furthermore, although vehicle reservation is carried out twice (S114, S133), the first vehicle reservation (S114) can be performed without imposing an obligation to reserve a vehicle on the bus operator. [Explanation of symbols]
[0185] 1: Server, 101: Control unit, 102: Memory, 103: Storage unit, 104: Communication device, 111: Storage means, 112: Extraction means, 113: Calculation means, 114: Output means, 115: Display control means, 116: Loan car management means, 121: Guide information storage means, 122: Remaining guide number calculation means, 123: First display control means, 124: Second display control means, 125: Bus information storage means, 126: Remaining bus number calculation means, 127: Estimate limiting means, 131: First allocation means, 132: Second allocation means, 133: Estimate request information generation means, 134: Estimate request means, 135: Support display means, 150: Database (DB), 151: AGT master, 152: Bus operator master, 15 3: Vehicle class detail master, 154: Sales office master, 155: AGT group master, 156: AGT group fare master, 157: Guide fare master, 158: Hokkaido Transport Bureau master, 159: Outside business area master, 160: Fare and charge master, 161: AGT group fare calendar, 162: Vehicle usage status information, 163: OB setting information, 2: Travel agency device, 201: Control unit, 202: Memory, 203: Storage unit, 204: Operation device, 205: Display device, 206: Communication device, 3: Bus operator device, 301: Control unit, 302: Memory, 303: Storage unit, 304: Operation device, 305: Display device, 306: Communication device, 4: Map search site, 9: Internet
Claims
1. A chartered bus system for chartered bus services includes a travel agency device managed by an ordering travel agency and a bus company device managed by an order-receiving bus company, a first allocation means for allocating a planned number of buses to a plurality of bus operators in advance in response to an operation of the travel agency device; a second allocation means for allocating a specific number of buses to a plurality of bus operators based on the planned number of buses allocated by the first allocation means; a quotation request information generating means for generating quotation request information for each bus operator based on the allocation result obtained by the second allocation means; a quotation request means for transmitting the quotation request information to each bus operator device managed by each bus operator; A chartered bus system.
2. The second allocation means a plurality of allocations of steps including an allocation of a first step and an allocation of a second step after the first step; The allocation of the second process is performed based on the allocation result of the first process.
2. The chartered bus system according to claim 1.
3. The second allocation means This can be done by taking into account the ratio of the number of units for which quotation requests have been made to the planned number of units and the number of units remaining for which quotation requests have been made to the planned number of units.
3. The chartered bus system according to claim 1 or 2.
4. The second allocation means The specific number of buses can be allocated to multiple bus operators in response to input operations of the travel agency device, and a support display means for displaying information on the travel agency device to support the input operation when allocating the buses to the plurality of bus operators.
2. The chartered bus system according to claim 1.
5. A chartered bus processing method using a travel agency device managed by an ordering travel agency and a bus company device managed by an order-receiving bus company, for a service related to a chartered bus, a first step of allocating a planned number of buses to a plurality of bus operators in advance in response to an operation of the travel agency device; a second step of allocating a specific number of buses to a plurality of bus operators based on the planned number of buses allocated in the first step; a third step of generating quotation request information for each bus operator based on the allocation result obtained in the second step; a fourth step of transmitting the quotation request information to each bus operator device managed by each bus operator. A chartered bus processing method.
6. A travel agency device managed by an ordering travel agency and a bus operator device managed by an order-receiving bus operator, and an information processing device connected thereto, for a service related to chartered buses, a first allocation means for allocating a planned number of buses to a plurality of bus operators in advance in response to an operation of the travel agency device; a second allocation means for allocating a specific number of buses to a plurality of bus operators based on the planned number of buses allocated by the first allocation means; a quotation request information generating means for generating quotation request information for each bus operator based on the allocation result obtained by the second allocation means; and functioning as a quotation request means for transmitting the quotation request information to each bus company device managed by each bus company. A charter bus processing program.
Citation Information
Patent Citations
Chartered bus reservation system
JP2002373280A