WO2023171461A1 - Operation management system, method, and program - Google Patents
Operation management system, method, and program Download PDFInfo
- Publication number
- WO2023171461A1 WO2023171461A1 PCT/JP2023/007254 JP2023007254W WO2023171461A1 WO 2023171461 A1 WO2023171461 A1 WO 2023171461A1 JP 2023007254 W JP2023007254 W JP 2023007254W WO 2023171461 A1 WO2023171461 A1 WO 2023171461A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- revenue
- cluster
- user
- vehicle
- request
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 3
- 238000004364 calculation method Methods 0.000 claims abstract description 8
- 238000007726 management method Methods 0.000 claims description 60
- 230000008859 change Effects 0.000 claims description 10
- 238000005516 engineering process Methods 0.000 abstract description 4
- 230000004044 response Effects 0.000 abstract description 2
- 230000009471 action Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 8
- 230000012447 hatching Effects 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000033001 locomotion Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000029305 taxis Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/40—Business processes related to the transportation industry
Definitions
- the present disclosure relates to technology for realizing mobility services that operate on demand.
- Mobility-as-a-Service is a service that centrally manages various means of transportation using Information Technology (IT) and realizes planning, reservations, and payments for user movement from origin to destination. It is.
- MaaS makes it possible to provide a flexible and highly real-time means of transportation by using an information system realized in the cloud or the like from a smartphone.
- the means of transportation provided by MaaS include not only vehicles used by individuals such as taxis and car sharing, but also public transportation vehicles such as trains and buses that are shared by multiple users.
- Variable route type The starting and ending points of the bus are fixed, but the operating route between them can be changed to a certain extent. The user can specify the pick-up and drop-off points within the variable range of the operating route.
- the demand-based operation system of Patent Document 1 is intended to improve convenience for users without increasing the burden on transportation companies that provide public transportation such as buses.
- the demand-based operation system of Patent Document 1 does not take into account the profitability of the transport company, and cannot necessarily be said to be able to secure profits for the transport company.
- One objective included in the present disclosure is to provide a technology that enables both securing profits for transportation companies and convenience for users.
- An operation management system is an operation management system that manages the operation of a vehicle that can be jointly used by a plurality of users in a demand-responsive manner by paying a usage fee.
- a reception unit that accepts a request specifying a desired specified time width, a cluster in which multiple requests are configured with overlapping specified time widths, and operating the vehicle for the cluster to collect the usage fee according to the usage fee.
- a state calculation unit that calculates expected revenue; and an operation determination unit that determines to operate the vehicle for the cluster when the revenue is equal to or greater than a predetermined revenue threshold;
- FIG. 1 is a block diagram of a traffic management system.
- FIG. 2 is a block diagram showing the logical configuration of a traffic management server. It is a block diagram showing the hardware configuration of an operation management server.
- FIG. 2 is a block diagram showing the logical configuration of a user terminal.
- 3 is a flowchart showing the operation of the traffic management system. It is a figure showing an example of a screen of a transportation company portal site.
- FIG. 3 is a diagram showing an application screen of a user terminal. It is a figure which shows the other application screen of a user terminal. It is a figure which shows yet another application screen of a user terminal. It is a time chart showing the status of a request.
- FIG. 2 is a conceptual diagram for explaining how a mobility service is used.
- FIG. 1 is a block diagram of the traffic management system.
- the operation management system 10 is an information system that realizes a mobility service that provides demand-responsive operation of buses, which are vehicles that can be used jointly by users, by paying usage fees.
- the mobility service of this embodiment is a fixed route type in which the bus route from the starting point to the final destination is fixed, and the user specifies his/her desired pick-up and drop-off points on the bus route.
- the traffic management system 10 includes a user terminal 301, a traffic management server 401, and a transportation company terminal 601.
- the user terminal 301 is a terminal device used by each user to utilize mobility services.
- the user terminal 301 is a user's own smartphone on which an application dedicated to mobility services is installed. From the user terminal 301, the user can request bus service and check the status of other users' requests, bus service schedules, and the like.
- the operation management server 401 is a server device that coordinates this mobility service and determines bus operations in response to requests from users.
- the traffic management server 401 of this embodiment may be constructed on a cloud.
- the operation management server 401 determines the operation of buses so as to ensure both the transportation company's profits and the user's convenience. Details of the processing executed by the traffic management server 401 will be described later.
- the transport operator terminal 601 is a terminal device used by a transport operator that operates buses in this mobility service.
- the transport operator performs settings and operations necessary for the mobility service on the transport operator terminal 601 from the portal provided by the operation management server 401. Further, the transportation company receives a request for bus operation from the operation management server 401 on the transportation company terminal 601, and operates the actual bus according to the request.
- FIG. 2 is a block diagram showing the logical configuration of the traffic management server.
- the operation management server 401 includes a reception section 402, a status calculation section 403, and an operation determination section 404.
- the reception unit 402 receives a request from a user to use the bus via the user terminal 301.
- the pick-up time is specified within a range of times. This time will be referred to as a designated time width.
- the status calculation unit 403 identifies a cluster in which requests from multiple users overlap in specified time widths, and operates a bus for that cluster, thereby providing a fee to the transportation company based on the usage fee paid by the user. Calculate expected revenue. If the revenue is equal to or greater than a predetermined revenue threshold, the operation determining unit 404 determines that the profitability of the transportation company is secured, and determines to operate a bus for that cluster. This enables demand-responsive mobility services for users to both secure revenue for transport operators and provide convenience for users.
- FIG. 3 is a block diagram showing the hardware configuration of the traffic management server.
- the traffic management server 401 of this embodiment is a server device that can be connected from a personal computer, a smart phone, etc. via a communication network such as the Internet.
- the traffic management server 401 has a processor 411, a main memory 412, a storage device 413, a communication device 414, an input device 415, and a display device 416 as hardware, and these are connected to a bus 417.
- the storage device 413 is a device that stores data in a writable and readable manner.
- the storage device 413 stores software programs and data used for processing the software programs.
- the processor 411 reads the software program stored in the storage device 413 to the main memory 412 and uses the main memory 412 to execute processing of the software program.
- the receiving section 402, the state calculating section 403, and the operation determining section 404 shown in FIG. 2 are realized.
- the communication device 414 transmits information processed by the processor 411 via a communication network including wired and/or wireless communication, and also transmits information received via the communication network to the processor 411. The received information is used for processing by the processor 411.
- the input device 415 is a device that accepts information inputted by an operator such as a keyboard or a mouse, and the input information is used for processing by the processor 411.
- the display device 416 is a device that displays image and text information on a display screen in accordance with processing by the processor 411.
- the traffic management server 401 is a computer on the cloud
- the processor 411, main memory 412, storage device 413, and communication device 414 are on the cloud
- the input device 415 and display device 416 are external and cannot be connected to the computer on the cloud. It may be something that connects.
- FIG. 4 is a block diagram showing the logical configuration of the user terminal.
- the user terminal 301 has an action section 302 and a guide section 303.
- the action unit 302 provides the user with a GUI (Graphical User Interface) for inputting each information of a request and transmitting the request to the operation management server 401.
- the guide unit 303 provides the user with a GUI that presents a recommendation to change the specified time period if the bus does not operate within the specified time period set in the request because the transportation company's profitability cannot be ensured. .
- FIG. 5 is a flowchart showing the operation of the traffic management system.
- step S101 the transport operator accesses the transport operator portal site provided by the operation management server 401 from the transport operator terminal 601 and sets various parameters.
- FIG. 6 is a diagram showing an example of the screen of the transport operator portal site.
- a starting point & ending point upload button 612 Arranged on the screen 611 are a starting point & ending point upload button 612, a time frame & reception end time setting button 613, a profit threshold setting button 614, a discount rate setting button 615, and an operation plan reception button 616.
- the start point & destination point upload button 612 is a button that moves to a sub-screen where the start point and destination point of the bus operated by the transportation company are registered. Information on the starting point and ending point set on the sub-screen is stored as parameters in the database (not shown) of the operation management server 401.
- the time frame & acceptance end time setting button 613 is a sub-screen for setting the time frame that is the unit of time for aggregating requests from users, and the time at which the acceptance of requests for that time frame will end (reception end time). This is the button to move to.
- Information on the time frame and reception end time set on the sub-screen is stored as parameters in the database (not shown) of the operation management server 401.
- the profit threshold setting button 614 sets a threshold (profit threshold) for determining how much profit is expected to be made by operating the bus when it is decided to operate the bus. This is a button to move to a sub-screen for. Information on the revenue threshold set on the sub-screen is stored as a parameter in the database (not shown) of the operation management server 401.
- the discount percentage setting button 615 is a sub-screen for setting the percentage of the discount amount to be presented to other users (discount percentage) with respect to the difference between the amount expressed by the user who wishes to use the bus and the basic price. This is a transition button. Information on the discount rate set on the sub-screen is stored as a parameter in the database (not shown) of the operation management server 401.
- the operation plan reception button 616 is a button for the transportation company to manually acquire the bus operation plan from the operation management server 401. By pressing this button, the bus operation plan is downloaded from the operation management server 401 to the transportation company terminal 601 and displayed on the screen.
- step S301 the user terminal 301 uses the action unit 302 to acquire information input by the user for requesting bus service.
- FIG. 7 is a diagram showing the application screen of the user terminal.
- Screen 101 is a screen for the user to select a desired bus boarding location and alighting location.
- a plurality of selection buttons 102 are arranged on the screen 101.
- a selection button 102 is provided for each combination of pick-up and drop-off locations.
- FIG. 8 is a diagram showing another application screen of the user terminal.
- Screen 103 is a screen for selecting a time frame in which the user wishes to use the bus.
- a plurality of selection buttons 104 are arranged on the screen 103.
- a selection button 104 is provided for each time frame. For each time frame, the start time and end time 105 of the time frame, and the reception end time 106 are predetermined.
- the application on user terminal 301 displays a screen for generating a request and prompts the user. Prompt for information input.
- FIG. 9 is a diagram showing still another application screen of the user terminal.
- Screen 107 is a screen for the user to input various information regarding the request. Three areas are arranged on the screen 107: a status display area 108, a guide display area 109, and an action display area 110.
- the status display area 108 includes the remaining time until the reception end time of the target time frame, and the pick-up and drop-off locations selected by the user.
- the status display area 108 further includes a time chart showing the status of the request for the time frame. This time chart displays the request status calculated by the operation management server 401 by totaling the requests.
- the action display area 110 shows a screen where the user can input information for sending a request.
- the action display area 304 in an initial state, the desired ride time tk, the ride time margin mk, and the proposed payment amount Pk that the user k has selected in a previously transmitted request are displayed.
- the desired boarding time tk is the time range in which user k desires to board the bus, that is, the start time of the designated time range.
- the boarding time margin mk is the specified time width desired by the user k.
- the proposed payment amount Pk is the amount that the user k proposes to pay as a bus usage fee.
- a basic price is set as the minimum necessary amount for bus usage fees.
- the proposed payment amount Pk can be set within the range of Pk ⁇ P0. If any user presents a proposed payment amount Pk that is higher than the basic price P0, the difference is applied to discount the usage price for other users who use the time frame.
- User k can send a request with the same desired boarding time tk, boarding time margin mk, and proposed payment amount Pk that are displayed in the initial state, or can change these values and send the request. You can also do it.
- User k selects the pick-up and drop-off locations and time slots on the screens 101 and 103 of the mobile application of the user terminal 301, and enters the desired boarding time, boarding time margin, and proposed payment amount on the screen 107.
- the action unit 302 transmits the request to the operation management server 401 in step S302.
- the operation management server 401 When the operation management server 401 receives a request in step S201, it starts batch processing to process the request in step S202.
- step S203 which is a batch processing stage, the operation management server 401 aggregates requests from multiple users, checks whether the specified time widths of the requests overlap, and classifies the parts where the specified time widths overlap into clusters of requests. Specify as.
- step S204 the operation management server 401 calculates potential revenue based on the degree of overlap of the specified time widths of requests in each cluster, and compares the value of the revenue with the revenue threshold. , it is determined whether a predetermined profit of the transport operator in the cluster is secured.
- the operation management server 401 aggregates the amount of payment offered by each user who sent a request included in the cluster for each identified cluster. If the proposed payment amount of a user included in a cluster is equal to the basic price P0, the minimum amount required to be paid in order to join the cluster and use the bus remains unchanged at the basic price. On the other hand, if some users in a cluster offer a higher payment amount than the base price, they can join that cluster and buy the bus by using the amount that their payment amount exceeds the base price. The minimum amount you need to pay for access will be lowered. For example, a user included in a cluster where the transportation operator's revenue does not reach a predetermined revenue threshold can invite other users to join that cluster by setting their own payment offer higher. . As described above, the ratio of the discount amount for other users to the additional payment amount for which the proposed payment amount exceeds the basic price is set in advance as a parameter.
- FIG. 10 is a time chart showing the status of requests.
- a time chart 201 shows requests received from each user for a time frame from time T1 to time T2. Requests from each user are shown as rectangles over a specified time range, and clusters of requests are shown as hatched rectangles. Clusters in which a predetermined profit is expected to be secured are indicated by downward hatching to the right, and clusters in which a predetermined profit is expected to be secured are indicated by upward hatching to the right.
- a cluster in which there are duplicate requests from three users who have presented the basic price as their proposed payment amount is expected to be profitable.
- step S205 the operation management server 401 determines whether the reception end time D for the time frame has been reached. If the reception end time D has not been reached, the operation management server 401 saves the latest cluster state and notifies the user terminal 301 of the state information in step S206. Upon receiving the notification, the user terminal 301 uses the action unit 302 to acquire the latest cluster status and causes the status to be reflected in the status display area 108 on the screen 107 .
- the time chart in the status display area 108 is a display equivalent to the display presented to the mobility service provider by the operation management server 401.
- a time period in which there is a request from a user but profitability for the transportation company is not ensured is shown as a time period hatched upward to the right on the time chart. If a user sets a proposed payment amount that exceeds the basic price in a request for such a time range, the difference between the proposed payment amount and the basic price, that is, the price with a discount according to the additional payment amount (post-discount price) ) will be displayed. This discount serves as an incentive to induce requests from other users for a time period in which a predetermined profitability of the transport company is not secured.
- the guide unit 303 displays a guide message indicating a proposal to the user in the guide display area 109 as appropriate.
- the message in the guide display area 109 illustrated in FIG. 9 indicates that the request of the user k is not currently in the cluster that satisfies the profitability of the transportation company, but if the boarding time margin is increased by m', the transportation business will It has been announced that you can join the cluster that meets the profitability of your company.
- step S303 the action unit 302 of the user terminal 301 periodically checks whether the reception end time has been reached. If the acceptance end time has been reached, in step S304, the user terminal 301 causes the action unit 302 to determine whether the revenue of the transportation company has reached a predetermined revenue threshold in the cluster that includes the user's request. That is, it is determined whether or not it is possible to operate a bus to the cluster.
- the action unit 302 of the user terminal 301 reserves the bus for the user in step S305. The user is prompted to confirm the reservation, and when the user performs the confirmation operation, the reservation is confirmed.
- step S304 if the transportation business operator's revenue has not reached the predetermined revenue threshold in the cluster that includes the user's request, the action unit 302 causes the transportation business operator's revenue to reach the predetermined revenue threshold for the user. Offer to join clusters that have reached a revenue threshold. If the user accepts the proposal and desires to change to a certain cluster, the action unit 302 sends a changed request to the traffic management server 401 to use a bus operated for that cluster.
- the operation management server 401 When the operation management server 401 receives a changed request from the user terminal 301 after the acceptance end deadline has been reached in step S205, the operation management server 401 additionally registers the user in a desired cluster according to the request in step S207. . At this time, the time width and price of the cluster do not change. The operation management server 401 further requests the transport operator terminal 601 to set bus operation within the time range of the cluster in which the profitability of the transport operator is ensured.
- FIG. 11 is a conceptual diagram for explaining how the mobility service is used.
- a mobility service is provided that operates demand-responsive buses between a remote or rural area 505 and a commercial area 504 near a station as shown in FIG.
- the reception end time for that time frame is 14:30.
- multiple users 501, 502, 503 move from the same remote or rural area 505 to the same commercial area 504 near the station. It is assumed that the users 501, 502, and 503 move with some time margin. It is assumed that all three users 501, 502, and 503 can move to the same time frame.
- the user 501 sends a request in which the desired boarding time is 16:15 and the boarding time margin is 30 minutes.
- the user 502 sends a request in which the desired boarding time is 16:05 and the boarding time margin is 15 minutes.
- the user 503 sends a request in which the desired boarding time is 16:15 and the boarding time margin is 10 minutes. It is assumed that all the users 501, 502, and 503 have presented the basic price as the proposed payment amount.
- a cluster including requests from three people is configured in the time span from 16:15 to 16:20.
- the total amount of payments offered by the three persons shall cause the transportation operator's revenue to exceed a predetermined revenue threshold. Therefore, three users 501, 502, and 503 can travel to commercial area 504 by jointly using one bus. If the service provided by the traffic management system 10 of this embodiment were not provided, the users 501, 502, and 503 might have to pay a fee individually to travel by taxi or shared car.
- a traffic management system that manages the operation of a vehicle that can be jointly used by multiple users by paying a usage fee in a demand-responsive manner has a reception unit that accepts requests from users specifying a specified time range in which they wish to use the ride, and a multiple a state calculation unit that identifies clusters in which the requests are configured with overlapping specified time widths, and calculates the revenue expected from the usage fee by operating the vehicle for the cluster; and an operation determining unit that determines to operate the vehicle for the cluster when the revenue is equal to or greater than a revenue threshold.
- the operation management system changes a request to a user included in a cluster whose revenue does not reach the revenue threshold so that the user is included in a cluster whose revenue is equal to or higher than the revenue threshold.
- the operation determining unit further includes a guide unit that presents a recommendation proposing that the cluster is selected, and when the user accepts the recommendation and changes the specified time range and the revenue exceeds the revenue threshold, the operation determining unit A decision is made to operate the vehicle. According to this, even if the transport operator's profitability is not secured according to the user's initial request, the user is suggested to change the specified time range in a way that will ensure profitability, so that the transport operator's profits can be secured. User convenience can be further improved.
- a basic price is set in advance as the minimum necessary amount of the usage fee, and the reception unit is configured to accept an amount equal to or higher than the basic price in the request.
- the state calculating unit calculates the revenue in the cluster based on the proposed payment amount in the request included in the cluster, and the operation determining unit determines that the revenue is within the revenue threshold
- a user who intends to use the vehicle is presented with a discount from the basic price for the usage fee of a cluster in which there is a user who has submitted a payment offer amount higher than the basic price. According to this, if the user's original request is unlikely to ensure the profitability of the transport operator, by giving the user the means to solicit other users by paying an additional fee, the transport operator can It is possible to secure profits and improve user convenience.
- the reception unit allows the user to specify a desired boarding time, which is a time at which the user wishes to board the board, and a boarding time margin, which is a time range in which a change in the desired boarding time is allowed. accepts the designation of the designated time width. According to this, the user can intuitively specify the specified time range by specifying the desired time and the time that can be changed.
Landscapes
- Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- General Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Provided is a technology which enables both stable profits for a transport provider and user convenience. This operation management system manages the operations of vehicles that are available for collective use in a demand response by receiving fares from a plurality of users. The operation management system comprises: a reception unit which receives, from users, requests for designating designation time widths for which the users desire to use the vehicles; a state calculation unit which specifies a cluster configured by a plurality of requests that cause the designated time widths to overlap, and calculates profits expected from the fares by operating the vehicles for the cluster; and an operation determination unit which, when the profits are equal to or greater than a prescribed profit threshold, determines to operate the vehicles for the cluster.
Description
本開示は、オンデマンドで運行するモビリティサービスを実現する技術に関する。
The present disclosure relates to technology for realizing mobility services that operate on demand.
Mobility-as-a-Service(MaaS)は、Information Technology(IT)によって各種の移動手段を一元的に管理し、出発地から目的地までのユーザの移動に関する計画、予約、および支払いを実現するサービスである。MaaSでは、クラウド等で実現された情報システムをスマートフォンから利用することにより、柔軟でリアルタイム性の高い移動手段の提供が可能となる。MaaSで提供される移動手段には、タクシーやカーシェアリングなどの個人で利用する乗物だけでなく、鉄道やバスなど複数のユーザが共同利用する公共交通機関の乗物も含まれる。
Mobility-as-a-Service (MaaS) is a service that centrally manages various means of transportation using Information Technology (IT) and realizes planning, reservations, and payments for user movement from origin to destination. It is. MaaS makes it possible to provide a flexible and highly real-time means of transportation by using an information system realized in the cloud or the like from a smartphone. The means of transportation provided by MaaS include not only vehicles used by individuals such as taxis and car sharing, but also public transportation vehicles such as trains and buses that are shared by multiple users.
駅や都市部から遠隔にある地域や人口密度の低い農村地域では移動手段の利用者が少ないことが想定される。そのような遠隔地域や農村地域においては、オンデマンドで運行するバスに複数のユーザが相乗り可能なデマンドレスポンシブバスサービスが注目されている(特許文献1参照)。
It is assumed that there will be fewer users of transportation in areas that are far from stations and urban areas, and in rural areas with low population density. In such remote and rural areas, demand-responsive bus services that allow multiple users to ride on a bus that operates on demand are attracting attention (see Patent Document 1).
デマンドレスポンシブバスサービスには主に次の3つのタイプが考えられている。
The following three types of demand-responsive bus services are considered:
(1)固定ルートタイプ:バスの始発地点から終着地点までの運行ルートが固定されており、ユーザはその運行ルート上で自身の乗車地点と降車地点を指定する。
(1) Fixed route type: The operating route from the starting point to the ending point of the bus is fixed, and the user specifies his or her boarding point and alighting point on the operating route.
(2)可変ルートタイプ:バスの始発地点と終着地点は固定されているが、その間の運行ルートはある程度まで変更が可能である。ユーザは運行ルートの可変範囲内で乗車地点および降車地点を指定できる。
(2) Variable route type: The starting and ending points of the bus are fixed, but the operating route between them can be changed to a certain extent. The user can specify the pick-up and drop-off points within the variable range of the operating route.
(3)フリールートタイプ:ユーザからの要求に応じて、出発地点および終着地点を含めてバスの運行ルートが柔軟に設定される。
(3) Free route type: The bus route, including the starting point and ending point, is flexibly set according to the user's request.
特許文献1のデマンド型運行システムは、バスなどの公共交通機関を提供する輸送事業者の負担を増大させずにユーザの利便性を向上させようというものである。しかしながら、特許文献1のデマンド型運行システムには、輸送事業者の収益性の観点がなく、必ずしも輸送事業者の収益を確保できるものとは言えなかった。
The demand-based operation system of Patent Document 1 is intended to improve convenience for users without increasing the burden on transportation companies that provide public transportation such as buses. However, the demand-based operation system of Patent Document 1 does not take into account the profitability of the transport company, and cannot necessarily be said to be able to secure profits for the transport company.
本開示に含まれるひとつの目的は、輸送事業者の収益の確保とユーザの利便性との両立を可能にする技術を提供することである。
One objective included in the present disclosure is to provide a technology that enables both securing profits for transportation companies and convenience for users.
本開示に含まれるひとつの態様による運行管理システムは、複数のユーザが利用料金を支払ってデマンドレスポンシブに共同で利用可能な乗物の運行を管理する運行管理システムであって、ユーザから乗物の利用を希望する指定時間幅を指定したリクエストを受け付ける受付部と、複数のリクエストが指定時間幅を重複させて構成されたクラスタを特定し、該クラスタに対して前記乗物を運行させることで前記利用料金によって見込まれる収益を算出する状態算出部と、前記収益が所定の収益しきい値以上である場合に、前記クラスタに対して前記乗物を運行することを決定する運行決定部と、
An operation management system according to one aspect included in the present disclosure is an operation management system that manages the operation of a vehicle that can be jointly used by a plurality of users in a demand-responsive manner by paying a usage fee. A reception unit that accepts a request specifying a desired specified time width, a cluster in which multiple requests are configured with overlapping specified time widths, and operating the vehicle for the cluster to collect the usage fee according to the usage fee. a state calculation unit that calculates expected revenue; and an operation determination unit that determines to operate the vehicle for the cluster when the revenue is equal to or greater than a predetermined revenue threshold;
を有する。
has.
本開示に含まれるひとつの態様によれば、輸送事業者の収益の確保とユーザの利便性との両立が可能となる。
According to one aspect included in the present disclosure, it is possible to both secure profits for transportation companies and provide convenience for users.
以下、本発明の実施形態について図面を参照して説明する。
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
図1は、運行管理システムのブロック図である。運行管理システム10は、ユーザが利用料金を支払ってデマンドレスポンシブに共同で利用可能な乗物であるバスの運行を提供するモビリティサービスを実現する情報システムである。本実施形態のモビリティサービスは、バスの始発地点から終着地点までの運行ルートが固定されており、ユーザはその運行ルート上で自身の希望する乗車地および降車地を指定する固定ルートタイプである。
FIG. 1 is a block diagram of the traffic management system. The operation management system 10 is an information system that realizes a mobility service that provides demand-responsive operation of buses, which are vehicles that can be used jointly by users, by paying usage fees. The mobility service of this embodiment is a fixed route type in which the bus route from the starting point to the final destination is fixed, and the user specifies his/her desired pick-up and drop-off points on the bus route.
運行管理システム10は、ユーザ端末301、運行管理サーバ401、および輸送事業者端末601を有している。
The traffic management system 10 includes a user terminal 301, a traffic management server 401, and a transportation company terminal 601.
ユーザ端末301は、各ユーザがモビリティサービスを利用するために用いる端末装置である。本実施形態では、ユーザ端末301は、ユーザ自身のスマートフォンにモビリティサービスに専用のアプリケーションをインストールしたものである。ユーザは、ユーザ端末301から、バスの運行を要求したり、他のユーザの要求やバス運行の予定等の状態を確認したりすることができる。
The user terminal 301 is a terminal device used by each user to utilize mobility services. In this embodiment, the user terminal 301 is a user's own smartphone on which an application dedicated to mobility services is installed. From the user terminal 301, the user can request bus service and check the status of other users' requests, bus service schedules, and the like.
運行管理サーバ401は、本モビリティサービスと統括し、ユーザからのリクエストに応じてバスの運行を決定するサーバ装置である。本実施形態の運行管理サーバ401はクラウド上に構築されるものであってもよい。運行管理サーバ401は、輸送事業者の収益の確保とユーザの利便性とを両立させるようにバスの運行を決定する。運行管理サーバ401が実行する処理の詳細は後述する。
The operation management server 401 is a server device that coordinates this mobility service and determines bus operations in response to requests from users. The traffic management server 401 of this embodiment may be constructed on a cloud. The operation management server 401 determines the operation of buses so as to ensure both the transportation company's profits and the user's convenience. Details of the processing executed by the traffic management server 401 will be described later.
輸送事業者端末601は、本モビリティサービスにてバスを運行する輸送事業者が利用する端末装置である。輸送事業者は、輸送事業者端末601上で、運行管理サーバ401により提供されるポータルからモビリティサービスに必要な設定や操作等の作業を行う。また、輸送事業者は、運行管理サーバ401からバスの運行の依頼を輸送事業者端末601上で受け、その依頼に従って実際のバスを運行させる。
The transport operator terminal 601 is a terminal device used by a transport operator that operates buses in this mobility service. The transport operator performs settings and operations necessary for the mobility service on the transport operator terminal 601 from the portal provided by the operation management server 401. Further, the transportation company receives a request for bus operation from the operation management server 401 on the transportation company terminal 601, and operates the actual bus according to the request.
図2は、運行管理サーバの論理構成を示すブロック図である。
FIG. 2 is a block diagram showing the logical configuration of the traffic management server.
運行管理サーバ401は、受付部402、状態算出部403、および運行決定部404を有する。
The operation management server 401 includes a reception section 402, a status calculation section 403, and an operation determination section 404.
受付部402は、ユーザ端末301を介してユーザからバスの利用を希望するリクエストを受け付ける。リクエストでは、ユーザが希望する乗車地および降車地に加え、乗車時刻が幅を持った時間で指定される。この時間を指定時間幅と称することにする。状態算出部403は、複数のユーザからのリクエストが指定時間幅を重複させて構成されたクラスタを特定し、そのクラスタに対してバスを運行させることで、ユーザが支払う利用料金によって輸送事業者に見込まれる収益を算出する。運行決定部404は、その収益が所定の収益しきい値以上であれば、輸送事業者の収益性が確保されると判断し、そのクラスタに対してバスを運行することを決定する。これにより、ユーザへのデマンドレスポンシブなモビリティサービスにおいて輸送事業者の収益の確保とユーザの利便性との両立が可能になる。
The reception unit 402 receives a request from a user to use the bus via the user terminal 301. In the request, in addition to the pick-up and drop-off locations desired by the user, the pick-up time is specified within a range of times. This time will be referred to as a designated time width. The status calculation unit 403 identifies a cluster in which requests from multiple users overlap in specified time widths, and operates a bus for that cluster, thereby providing a fee to the transportation company based on the usage fee paid by the user. Calculate expected revenue. If the revenue is equal to or greater than a predetermined revenue threshold, the operation determining unit 404 determines that the profitability of the transportation company is secured, and determines to operate a bus for that cluster. This enables demand-responsive mobility services for users to both secure revenue for transport operators and provide convenience for users.
図3は、運行管理サーバのハードウェア構成を示すブロック図である。本実施形態の運行管理サーバ401は、インターネット等の通信ネットワーク経由でパーソナルコンピュータやスマートホン等から接続可能なサーバ装置である。
FIG. 3 is a block diagram showing the hardware configuration of the traffic management server. The traffic management server 401 of this embodiment is a server device that can be connected from a personal computer, a smart phone, etc. via a communication network such as the Internet.
運行管理サーバ401は、ハードウェアとして、プロセッサ411、メインメモリ412、記憶装置413、通信装置414、入力装置415、および表示装置416を有し、それらがバス417に接続されている。
The traffic management server 401 has a processor 411, a main memory 412, a storage device 413, a communication device 414, an input device 415, and a display device 416 as hardware, and these are connected to a bus 417.
記憶装置413は、書込みおよび読み出しが可能にデータを記憶する装置である。記憶装置413には、ソフトウェアプログラムおよびそのソフトウェアプログラムの処理に利用されるデータが格納される。プロセッサ411は、記憶装置413に記憶されたソフトウェアプログラムをメインメモリ412に読み出し、メインメモリ412を利用してソフトウェアプログラムの処理を実行する。プロセッサ411がソフトウェアプログラムを実行することにより、図2に示した受付部402、状態算出部403、および運行決定部404が実現される。通信装置414は、プロセッサ411にて処理された情報を有線または無線あるいはそれら両方を含む通信ネットワークを介して送信し、また通信ネットワークを介して受信した情報をプロセッサ411に伝達する。受信した情報はプロセッサ411にて処理に利用される。入力装置415は、キーボードやマウスなど操作者による操作入力による情報を受け付ける装置であり、入力された情報はプロセッサ411にて処理に利用される。表示装置416は、プロセッサ411による処理に伴って画像やテキストの情報をディスプレイ画面に表示する装置である。運行管理サーバ401がクラウド上のコンピュータである場合、プロセッサ411、メインメモリ412、記憶装置413、通信装置414はクラウド上にあり、入力装置415および表示装置416は外部にあってクラウド上のコンピュータに接続するものであってもよい。
The storage device 413 is a device that stores data in a writable and readable manner. The storage device 413 stores software programs and data used for processing the software programs. The processor 411 reads the software program stored in the storage device 413 to the main memory 412 and uses the main memory 412 to execute processing of the software program. When the processor 411 executes the software program, the receiving section 402, the state calculating section 403, and the operation determining section 404 shown in FIG. 2 are realized. The communication device 414 transmits information processed by the processor 411 via a communication network including wired and/or wireless communication, and also transmits information received via the communication network to the processor 411. The received information is used for processing by the processor 411. The input device 415 is a device that accepts information inputted by an operator such as a keyboard or a mouse, and the input information is used for processing by the processor 411. The display device 416 is a device that displays image and text information on a display screen in accordance with processing by the processor 411. When the traffic management server 401 is a computer on the cloud, the processor 411, main memory 412, storage device 413, and communication device 414 are on the cloud, and the input device 415 and display device 416 are external and cannot be connected to the computer on the cloud. It may be something that connects.
図4は、ユーザ端末の論理構成を示すブロック図である。
FIG. 4 is a block diagram showing the logical configuration of the user terminal.
ユーザ端末301は、アクション部302およびガイド部303を有している。アクション部302は、ユーザに、リクエストの各情報を入力し、そのリクエストを運行管理サーバ401に送信するためのGUI(Graphical User Interface)を提供する。ガイド部303は、ユーザに、輸送事業者の収益性が確保されないためにリクエストに設定された指定時間幅にバスが運行されない場合に指定時間幅の変更を提案するレコメンドを提示するGUIを提供する。
The user terminal 301 has an action section 302 and a guide section 303. The action unit 302 provides the user with a GUI (Graphical User Interface) for inputting each information of a request and transmitting the request to the operation management server 401. The guide unit 303 provides the user with a GUI that presents a recommendation to change the specified time period if the bus does not operate within the specified time period set in the request because the transportation company's profitability cannot be ensured. .
図5は、運行管理システムの動作を示すフローチャートである。
FIG. 5 is a flowchart showing the operation of the traffic management system.
ステップS101にて、輸送事業者は、輸送事業者端末601から、運行管理サーバ401により提供される輸送事業者ポータルサイトにアクセスし、各種パラメータを設定する。
In step S101, the transport operator accesses the transport operator portal site provided by the operation management server 401 from the transport operator terminal 601 and sets various parameters.
図6は、輸送事業者ポータルサイトの画面の一例を示す図である。
FIG. 6 is a diagram showing an example of the screen of the transport operator portal site.
画面611には、始発地点&終着地点アップロードボタン612、時間枠&受付終了時刻設定ボタン613、収益しきい値設定ボタン614、値引き割合設定ボタン615、および運行計画受信ボタン616が配置されている。
Arranged on the screen 611 are a starting point & ending point upload button 612, a time frame & reception end time setting button 613, a profit threshold setting button 614, a discount rate setting button 615, and an operation plan reception button 616.
始発地点&終着地点アップロードボタン612は、輸送事業者が運行するバスの始発地点と終着地点を登録するサブ画面に移行するボタンである。サブ画面で設定された始発地点および終着地点の情報はパラメータとして運行管理サーバ401のデータベース(不図示)に格納される。
The start point & destination point upload button 612 is a button that moves to a sub-screen where the start point and destination point of the bus operated by the transportation company are registered. Information on the starting point and ending point set on the sub-screen is stored as parameters in the database (not shown) of the operation management server 401.
時間枠&受付終了時刻設定ボタン613は、ユーザからのリクエストを集計する時間単位となる時間枠と、その時間枠に対するリクエストの受け付けを終了する時刻(受付終了時刻)とを設定するためのサブ画面に移行するボタンである。サブ画面で設定された時間枠および受付終了時刻の情報はパラメータとして運行管理サーバ401のデータベース(不図示)に格納される。
The time frame & acceptance end time setting button 613 is a sub-screen for setting the time frame that is the unit of time for aggregating requests from users, and the time at which the acceptance of requests for that time frame will end (reception end time). This is the button to move to. Information on the time frame and reception end time set on the sub-screen is stored as parameters in the database (not shown) of the operation management server 401.
収益しきい値設定ボタン614は、バスを運行することによりどれだけの収益が見こまれる場合にバスを運行することにするかを判定するためのしきい値(収益しきい値)を設定するためのサブ画面に移行するボタンである。サブ画面で設定された収益しきい値の情報はパラメータとして運行管理サーバ401のデータベース(不図示)に格納される。
The profit threshold setting button 614 sets a threshold (profit threshold) for determining how much profit is expected to be made by operating the bus when it is decided to operate the bus. This is a button to move to a sub-screen for. Information on the revenue threshold set on the sub-screen is stored as a parameter in the database (not shown) of the operation management server 401.
値引き割合設定ボタン615は、バスの利用を希望するユーザが表明した金額と基本価格との差額に対する、それにより他のユーザに提示する値引き金額の割合(値引き割合)を設定するためのサブ画面に移行するボタンである。サブ画面で設定された値引き割合の情報はパラメータとして運行管理サーバ401のデータベース(不図示)に格納される。
The discount percentage setting button 615 is a sub-screen for setting the percentage of the discount amount to be presented to other users (discount percentage) with respect to the difference between the amount expressed by the user who wishes to use the bus and the basic price. This is a transition button. Information on the discount rate set on the sub-screen is stored as a parameter in the database (not shown) of the operation management server 401.
運行計画受信ボタン616は、輸送事業者が運行管理サーバ401からバス運行計画を手動で取得するためのボタンである。このボタンを押下することにより、運行管理サーバ401から輸送事業者端末601にバス運行計画がダウンロードされ、画面に表示される。
The operation plan reception button 616 is a button for the transportation company to manually acquire the bus operation plan from the operation management server 401. By pressing this button, the bus operation plan is downloaded from the operation management server 401 to the transportation company terminal 601 and displayed on the screen.
図5に戻り、ステップS301にて、ユーザ端末301は、アクション部302により、ユーザによる入力されたバスの運行を要求するための情報を取得する。
Returning to FIG. 5, in step S301, the user terminal 301 uses the action unit 302 to acquire information input by the user for requesting bus service.
図7は、ユーザ端末のアプリケーション画面を示す図である。画面101は、ユーザが希望するバスの乗車地と降車地とを選択するための画面である。画面101には複数の選択ボタン102が配置されている。選択ボタン102は乗車地と降車地の組み合わせ毎に設けられている。
FIG. 7 is a diagram showing the application screen of the user terminal. Screen 101 is a screen for the user to select a desired bus boarding location and alighting location. A plurality of selection buttons 102 are arranged on the screen 101. A selection button 102 is provided for each combination of pick-up and drop-off locations.
図8は、ユーザ端末の他のアプリケーション画面を示す図である。画面103は、バスの利用を希望する時間枠を選択するための画面である。
FIG. 8 is a diagram showing another application screen of the user terminal. Screen 103 is a screen for selecting a time frame in which the user wishes to use the bus.
画面103には複数の選択ボタン104が配置されている。選択ボタン104は時間枠毎に設けられている。各時間枠には、その時間枠の開始時刻および終了時刻105と、受付終了時刻106とが予め定められている。
A plurality of selection buttons 104 are arranged on the screen 103. A selection button 104 is provided for each time frame. For each time frame, the start time and end time 105 of the time frame, and the reception end time 106 are predetermined.
ユーザが、図7の画面101から乗車地点および降車地点を選択し、図8の画面103から時間枠を選択すると、ユーザ端末301のアプリケーションは、リクエストを生成するための画面を表示し、ユーザに情報の入力を促す。
When the user selects a pick-up point and a drop-off point from screen 101 in FIG. 7 and a time frame from screen 103 in FIG. 8, the application on user terminal 301 displays a screen for generating a request and prompts the user. Prompt for information input.
図9は、ユーザ端末の更に他のアプリケーション画面を示す図である。画面107は、ユーザがリクエストの各種情報を入力するための画面である。画面107には、状態表示領域108、ガイド表示領域109、アクション表示領域110の3つの領域が配置されている。
FIG. 9 is a diagram showing still another application screen of the user terminal. Screen 107 is a screen for the user to input various information regarding the request. Three areas are arranged on the screen 107: a status display area 108, a guide display area 109, and an action display area 110.
状態表示領域108には、対象の時間枠の受付終了時刻までの残り時間と、ユーザが選択した乗車地および降車地とが含まれている。状態表示領域108には、更に、当該時間枠に対するリクエストの状態を示すタイムチャートが含まれている。このタイムチャートには、運行管理サーバ401がリクエストを集計することにより算出したリクエストの状態が表示される。
The status display area 108 includes the remaining time until the reception end time of the target time frame, and the pick-up and drop-off locations selected by the user. The status display area 108 further includes a time chart showing the status of the request for the time frame. This time chart displays the request status calculated by the operation management server 401 by totaling the requests.
アクション表示領域110には、ユーザがリクエストを送るための情報入力が可能な画面が示されている。アクション表示領域304には、初期状態では、当該ユーザkが以前に送信したリクエストで選択したことのある乗車希望時刻tk、乗車時刻マージンmk、および支払い提示金額Pkが表示されている。
The action display area 110 shows a screen where the user can input information for sending a request. In the action display area 304, in an initial state, the desired ride time tk, the ride time margin mk, and the proposed payment amount Pk that the user k has selected in a previously transmitted request are displayed.
乗車希望時刻tkは、ユーザkがバスの乗車を希望する時間幅すなわち指定時間幅の開始時刻である。乗車時刻マージンmkは、ユーザkが希望する指定時間幅の幅である。支払い提示金額Pkは、ユーザkがバスの利用料として支払うことを提示する金額である。バスの利用料金には必要最低限の金額として基本価格が設定されている。支払い提示金額Pkは、Pk≧P0の範囲内で設定することができる。いずれかのユーザが基本価格P0よりも高い支払い提示金額Pkを提示した場合、その差額は、当該時間枠を利用する他のユーザに対する利用価格の値引に充てられる。
The desired boarding time tk is the time range in which user k desires to board the bus, that is, the start time of the designated time range. The boarding time margin mk is the specified time width desired by the user k. The proposed payment amount Pk is the amount that the user k proposes to pay as a bus usage fee. A basic price is set as the minimum necessary amount for bus usage fees. The proposed payment amount Pk can be set within the range of Pk≧P0. If any user presents a proposed payment amount Pk that is higher than the basic price P0, the difference is applied to discount the usage price for other users who use the time frame.
ユーザkは、初期状態で表示された以前と同じ乗車希望時刻tk、乗車時刻マージンmk、および支払い提示金額Pkでリクエストを送信することもできるし、それらの数値を変更してリクエストを送信することもできる。
User k can send a request with the same desired boarding time tk, boarding time margin mk, and proposed payment amount Pk that are displayed in the initial state, or can change these values and send the request. You can also do it.
ユーザkがユーザ端末301のモバイルアプリケーションの画面101、103上でユーザが乗車地および降車地と時間枠を選択し、画面107上で乗車希望時刻、乗車時刻マージン、および支払い提示金額を入力してリクエストを送信する操作を行うと、ユーザ端末301は、アクション部302により、ステップS302にて、リクエストを運行管理サーバ401に送信する。
User k selects the pick-up and drop-off locations and time slots on the screens 101 and 103 of the mobile application of the user terminal 301, and enters the desired boarding time, boarding time margin, and proposed payment amount on the screen 107. When the user terminal 301 performs the operation of transmitting a request, the action unit 302 transmits the request to the operation management server 401 in step S302.
運行管理サーバ401は、ステップS201にてリクエストを受信すると、ステップS202にてそのリクエストを処理するバッチ処理を開始する。
When the operation management server 401 receives a request in step S201, it starts batch processing to process the request in step S202.
運行管理サーバ401は、バッチ処理ステージであるステップS203にて、複数のユーザからのリクエストを集計し、リクエストの指定時間幅の重複を確認し、指定時間幅が重複している箇所をリクエストのクラスタとして特定する。
In step S203, which is a batch processing stage, the operation management server 401 aggregates requests from multiple users, checks whether the specified time widths of the requests overlap, and classifies the parts where the specified time widths overlap into clusters of requests. Specify as.
更に、運行管理サーバ401は、ステップS204にて、各クラスタにおけるリクエストの指定時間幅の重複の度合いに基づく潜在的な収益を算出し、その収益の値と収益しきい値とを比較することにより、当該クラスタにおける輸送事業者の所定の収益が確保されるか否か判断する。
Furthermore, in step S204, the operation management server 401 calculates potential revenue based on the degree of overlap of the specified time widths of requests in each cluster, and compares the value of the revenue with the revenue threshold. , it is determined whether a predetermined profit of the transport operator in the cluster is secured.
このとき、運行管理サーバ401は、特定された各クラスタについてそのクラスタに含まれるリクエストを送信した各ユーザの支払い提示金額を集計する。クラスタに含まれるユーザの支払い提示金額が基本価格P0に等しければ、そのクラスタに参加してバスを利用するために支払うことが必要な最低限の金額は基本価格のまま変更されない。一方、クラスタ内の一部のユーザが基本価格よりも高い支払い提示金額を提示している場合、その支払い提示金額が基本価格を超過した分を使用することにより、そのクラスタに参加してバスを利用するために支払うことが必要な最低限の金額が引き下げられる。例えば、輸送事業者の収益が所定の収益しきい値に達していないクラスタに含まれるユーザが、自身の支払い提示金額を高く設定することにより、そのクラスタに他のユーザを勧誘するすることができる。上述したように、支払い提示金額が基本価格を超過した追加支払い金額に対する、他のユーザに対する値引金額の割合はパラメータとして予め設定されている。
At this time, the operation management server 401 aggregates the amount of payment offered by each user who sent a request included in the cluster for each identified cluster. If the proposed payment amount of a user included in a cluster is equal to the basic price P0, the minimum amount required to be paid in order to join the cluster and use the bus remains unchanged at the basic price. On the other hand, if some users in a cluster offer a higher payment amount than the base price, they can join that cluster and buy the bus by using the amount that their payment amount exceeds the base price. The minimum amount you need to pay for access will be lowered. For example, a user included in a cluster where the transportation operator's revenue does not reach a predetermined revenue threshold can invite other users to join that cluster by setting their own payment offer higher. . As described above, the ratio of the discount amount for other users to the additional payment amount for which the proposed payment amount exceeds the basic price is set in advance as a parameter.
図10は、リクエストの状態を示すタイムチャートである。タイムチャート201には、時刻T1から時刻T2までの時間枠に対して各ユーザから受信したリクエストが示されている。各ユーザからのリクエストが指定時間幅にわたる矩形で示され、リクエストのクラスタがハッチング付き矩形で示されている。所定の収益が確保される見込みのクラスタが右下がりハッチングで示され、所定の収益が確保されるクラスタが右上がりハッチングで示されている。ここでは一例として、支払い提示金額として基本価格を提示した3人のユーザのリクエストが重複するクラスタは収益性が確保される見込みとなっている。
FIG. 10 is a time chart showing the status of requests. A time chart 201 shows requests received from each user for a time frame from time T1 to time T2. Requests from each user are shown as rectangles over a specified time range, and clusters of requests are shown as hatched rectangles. Clusters in which a predetermined profit is expected to be secured are indicated by downward hatching to the right, and clusters in which a predetermined profit is expected to be secured are indicated by upward hatching to the right. Here, as an example, a cluster in which there are duplicate requests from three users who have presented the basic price as their proposed payment amount is expected to be profitable.
図5に戻り、運行管理サーバ401は、ステップS205にて、当該時間枠の受付終了時刻Dに達しているか否か判定する。受付終了時刻Dに達していなければ、運行管理サーバ401は、ステップS206にて、最新のクラスタの状態を保存するとともに、その状態の情報をユーザ端末301に通知する。通知を受けたユーザ端末301は、アクション部302により、最新のクラスタの状態を取得し、その状態を画面107における状態表示領域108の表示に反映させる。
Returning to FIG. 5, in step S205, the operation management server 401 determines whether the reception end time D for the time frame has been reached. If the reception end time D has not been reached, the operation management server 401 saves the latest cluster state and notifies the user terminal 301 of the state information in step S206. Upon receiving the notification, the user terminal 301 uses the action unit 302 to acquire the latest cluster status and causes the status to be reflected in the status display area 108 on the screen 107 .
状態表示領域108のタイムチャートには、運行管理サーバ401により、モビリティサービス事業者に提示される表示と同等の表示である。ユーザからのリクエストはあるが輸送事業者の収益性が確保されていない時間幅は、タイムチャート上の右上がりのハッチングが施されている時間幅として示されている。そのような時間幅に対するリクエストにおいて基本価格を超える支払い提示金額を設定したユーザがいる場合、支払い提示金額と基本価格との差額つまり追加支払い金額に応じた値引を行った価格(値引後価格)を示す吹き出しメッセージが表示される。この値引きは、輸送事業者の所定の収益性が確保されていない時間幅へ他のユーザのリクエストを誘引するインセンティブとなる。
The time chart in the status display area 108 is a display equivalent to the display presented to the mobility service provider by the operation management server 401. A time period in which there is a request from a user but profitability for the transportation company is not ensured is shown as a time period hatched upward to the right on the time chart. If a user sets a proposed payment amount that exceeds the basic price in a request for such a time range, the difference between the proposed payment amount and the basic price, that is, the price with a discount according to the additional payment amount (post-discount price) ) will be displayed. This discount serves as an incentive to induce requests from other users for a time period in which a predetermined profitability of the transport company is not secured.
更に、ユーザ端末301では、ガイド部303が、適宜、ガイド表示領域109にユーザへの提案を示したガイドのメッセージを表示する。
Further, in the user terminal 301, the guide unit 303 displays a guide message indicating a proposal to the user in the guide display area 109 as appropriate.
図9に例示したガイド表示領域109のメッセージは、現在、当該ユーザkのリクエストは輸送事業者の収益性を満たすクラスタに入っていないが、乗車時刻マージンをm´だけ増大させれば、輸送事業者の収益性を満たすクラスタに入ることができることを通知している。
The message in the guide display area 109 illustrated in FIG. 9 indicates that the request of the user k is not currently in the cluster that satisfies the profitability of the transportation company, but if the boarding time margin is increased by m', the transportation business will It has been announced that you can join the cluster that meets the profitability of your company.
図5に戻り、ステップS303にて、ユーザ端末301では、アクション部302が定期的に受付終了時刻に達しているか否か確認する。受付終了時刻に達していれば、ステップS304にて、ユーザ端末301は、アクション部302により、当該ユーザのリクエストを含むクラスタにおいて輸送事業者の収益が所定の収益しきい値に達しているか否か、すなわち当該クラスタに対してバスを運行させることが可能であるか否か判定する。
Returning to FIG. 5, in step S303, the action unit 302 of the user terminal 301 periodically checks whether the reception end time has been reached. If the acceptance end time has been reached, in step S304, the user terminal 301 causes the action unit 302 to determine whether the revenue of the transportation company has reached a predetermined revenue threshold in the cluster that includes the user's request. That is, it is determined whether or not it is possible to operate a bus to the cluster.
当該ユーザのリクエストを含むクラスタにおいて輸送事業者の収益が所定の収益しきい値に達している場合には、ユーザ端末301にて、アクション部302は、ステップS305にて、当該ユーザのバスの予約を確定するようにユーザに促し、ユーザが確定の操作を行うと、予約を確定させる。
If the revenue of the transportation company in the cluster that includes the user's request has reached the predetermined revenue threshold, the action unit 302 of the user terminal 301 reserves the bus for the user in step S305. The user is prompted to confirm the reservation, and when the user performs the confirmation operation, the reservation is confirmed.
ステップS304にて、当該ユーザのリクエストを含むクラスタにおいて輸送事業者の収益が所定の収益しきい値に達していない場合、アクション部302は、当該ユーザに対して、輸送事業者の収益が所定の収益しきい値に達しているクラスタへ参加することを提案する。ユーザがその提案を受け入れて、あるクラスタへの変更を希望した場合、アクション部302は、そのクラスタに対して運行されるバスを利用するように変更されたリクエストを運行管理サーバ401へ送信する。
In step S304, if the transportation business operator's revenue has not reached the predetermined revenue threshold in the cluster that includes the user's request, the action unit 302 causes the transportation business operator's revenue to reach the predetermined revenue threshold for the user. Offer to join clusters that have reached a revenue threshold. If the user accepts the proposal and desires to change to a certain cluster, the action unit 302 sends a changed request to the traffic management server 401 to use a bus operated for that cluster.
運行管理サーバ401は、ステップS205にて、受付終了期限に達した後、ユーザ端末301から変更されたリクエストを受信すると、ステップS207にて、そのリクエストに従って当該ユーザを所望のクラスタに追加で登録する。このとき、クラスタの時間幅および価格には変化は生じない。運行管理サーバ401は、更に、輸送事業者端末601に対して、輸送事業者の収益性が確保されたクラスタの時間幅内にバスの運行を設定するように依頼する。
When the operation management server 401 receives a changed request from the user terminal 301 after the acceptance end deadline has been reached in step S205, the operation management server 401 additionally registers the user in a desired cluster according to the request in step S207. . At this time, the time width and price of the cluster do not change. The operation management server 401 further requests the transport operator terminal 601 to set bus operation within the time range of the cluster in which the profitability of the transport operator is ensured.
図11は、モビリティサービスが利用される様子を説明するための概念図である。図11に示すような遠隔地域あるいは農村地域505と駅付近の商業地域504との間にデマンドレスポンシブなバスを運行するモビリティサービスが提供されている。本例では、15:00から18:00までの時間枠があり、その時間枠に対する受付終了時刻が14:30であるものとする。また、複数のユーザ501、502、503が、同じ遠隔または農村の地域505から同じ駅付近の商業地域504に移動するというシナリオを想定する。ユーザ501、502、503はある程度の時間的な余裕をもって移動を行うものとする。3人のユーザ501、502、503の全員が同じ上記時間枠に移動できるものとする。
FIG. 11 is a conceptual diagram for explaining how the mobility service is used. A mobility service is provided that operates demand-responsive buses between a remote or rural area 505 and a commercial area 504 near a station as shown in FIG. In this example, it is assumed that there is a time frame from 15:00 to 18:00, and the reception end time for that time frame is 14:30. Also assume a scenario in which multiple users 501, 502, 503 move from the same remote or rural area 505 to the same commercial area 504 near the station. It is assumed that the users 501, 502, and 503 move with some time margin. It is assumed that all three users 501, 502, and 503 can move to the same time frame.
図11の例では、ユーザ501は、乗車希望時刻であり16:15であり、乗車時刻マージンが30分であるリクエストを送っている。ユーザ502は、乗車希望時刻であり16:05であり、乗車時刻マージンが15分であるリクエストを送っている。ユーザ503は、乗車希望時刻であり16:15であり、乗車時刻マージンが10分であるリクエストを送っている。そして、全てのユーザ501、502、503が支払い提示金額として基本価格を提示したものとする。
In the example of FIG. 11, the user 501 sends a request in which the desired boarding time is 16:15 and the boarding time margin is 30 minutes. The user 502 sends a request in which the desired boarding time is 16:05 and the boarding time margin is 15 minutes. The user 503 sends a request in which the desired boarding time is 16:15 and the boarding time margin is 10 minutes. It is assumed that all the users 501, 502, and 503 have presented the basic price as the proposed payment amount.
この例では、16:15から16:20の時間幅に3人のリクエストを含むクラスタが構成される。3人の支払い提示金額の合計額により、輸送事業者の収益は所定の収益しきい値を超えるものとする。したがって、3人のユーザ501、502、503は、1台のバスを共同で利用して商業地域504に移動することができる。もし、本実施形態の運行管理システム10によるサービスが提供されていなければ、ユーザ501、502、503は個々に料金を支払ってタクシーやシェアカーで移動することになったかもしれない。
In this example, a cluster including requests from three people is configured in the time span from 16:15 to 16:20. The total amount of payments offered by the three persons shall cause the transportation operator's revenue to exceed a predetermined revenue threshold. Therefore, three users 501, 502, and 503 can travel to commercial area 504 by jointly using one bus. If the service provided by the traffic management system 10 of this embodiment were not provided, the users 501, 502, and 503 might have to pay a fee individually to travel by taxi or shared car.
上述した実施形態は、本発明の説明のための例示であり、本発明の範囲をそれらの実施形態にのみ限定する趣旨ではない。当業者は、本発明の範囲を逸脱することなしに、他の様々な態様で本発明を実施することができる。
The embodiments described above are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the invention in various other ways without departing from the scope of the invention.
上述した実施形態には以下に示す事項が含まれている。ただし、本実施形態に含まれる事項が以下に示すもののみに限定されることはない。
The embodiment described above includes the following items. However, the matters included in this embodiment are not limited to only those shown below.
(事項1)
複数のユーザが利用料金を支払ってデマンドレスポンシブに共同で利用可能な乗物の運行を管理する運行管理システムは、ユーザから乗物の利用を希望する指定時間幅を指定したリクエストを受け付ける受付部と、複数のリクエストが指定時間幅を重複させて構成されたクラスタを特定し、該クラスタに対して前記乗物を運行させることで前記利用料金によって見込まれる収益を算出する状態算出部と、前記収益が所定の収益しきい値以上である場合に、前記クラスタに対して前記乗物を運行することを決定する運行決定部と、を有する。
これによれば、ユーザへのデマンドレスポンシブな移動手段の提供において輸送事業者の収益の確保とユーザの利便性との両立が可能になる。 (Item 1)
A traffic management system that manages the operation of a vehicle that can be jointly used by multiple users by paying a usage fee in a demand-responsive manner has a reception unit that accepts requests from users specifying a specified time range in which they wish to use the ride, and a multiple a state calculation unit that identifies clusters in which the requests are configured with overlapping specified time widths, and calculates the revenue expected from the usage fee by operating the vehicle for the cluster; and an operation determining unit that determines to operate the vehicle for the cluster when the revenue is equal to or greater than a revenue threshold.
According to this, in providing a demand-responsive means of transportation to users, it is possible to both secure profits for transportation companies and provide convenience for users.
複数のユーザが利用料金を支払ってデマンドレスポンシブに共同で利用可能な乗物の運行を管理する運行管理システムは、ユーザから乗物の利用を希望する指定時間幅を指定したリクエストを受け付ける受付部と、複数のリクエストが指定時間幅を重複させて構成されたクラスタを特定し、該クラスタに対して前記乗物を運行させることで前記利用料金によって見込まれる収益を算出する状態算出部と、前記収益が所定の収益しきい値以上である場合に、前記クラスタに対して前記乗物を運行することを決定する運行決定部と、を有する。
これによれば、ユーザへのデマンドレスポンシブな移動手段の提供において輸送事業者の収益の確保とユーザの利便性との両立が可能になる。 (Item 1)
A traffic management system that manages the operation of a vehicle that can be jointly used by multiple users by paying a usage fee in a demand-responsive manner has a reception unit that accepts requests from users specifying a specified time range in which they wish to use the ride, and a multiple a state calculation unit that identifies clusters in which the requests are configured with overlapping specified time widths, and calculates the revenue expected from the usage fee by operating the vehicle for the cluster; and an operation determining unit that determines to operate the vehicle for the cluster when the revenue is equal to or greater than a revenue threshold.
According to this, in providing a demand-responsive means of transportation to users, it is possible to both secure profits for transportation companies and provide convenience for users.
(事項2)
事項1に記載の運行管理システムは、前記収益が前記収益しきい値に達しないクラスタに含まれるユーザに対して、前記収益が前記収益しきい値以上であるクラスタに入るようにリクエストを変更することを提案するレコメンドを提示するガイド部を更に有し、前記運行決定部は、前記ユーザが前記レコメンドを受け入れて指定時間幅を変更し前記収益が前記収益しきい値以上になったら、前記クラスタに対して前記乗物を運行することを決定する。
これによれば、ユーザの当初のリクエストによって輸送事業者の収益性が確保されない場合でも収益性が確保されるような指定時間幅の変更をユーザに提案するので、輸送事業者の収益の確保とユーザの利便性とをより高めることができる。 (Item 2)
The operation management system according toitem 1 changes a request to a user included in a cluster whose revenue does not reach the revenue threshold so that the user is included in a cluster whose revenue is equal to or higher than the revenue threshold. The operation determining unit further includes a guide unit that presents a recommendation proposing that the cluster is selected, and when the user accepts the recommendation and changes the specified time range and the revenue exceeds the revenue threshold, the operation determining unit A decision is made to operate the vehicle.
According to this, even if the transport operator's profitability is not secured according to the user's initial request, the user is suggested to change the specified time range in a way that will ensure profitability, so that the transport operator's profits can be secured. User convenience can be further improved.
事項1に記載の運行管理システムは、前記収益が前記収益しきい値に達しないクラスタに含まれるユーザに対して、前記収益が前記収益しきい値以上であるクラスタに入るようにリクエストを変更することを提案するレコメンドを提示するガイド部を更に有し、前記運行決定部は、前記ユーザが前記レコメンドを受け入れて指定時間幅を変更し前記収益が前記収益しきい値以上になったら、前記クラスタに対して前記乗物を運行することを決定する。
これによれば、ユーザの当初のリクエストによって輸送事業者の収益性が確保されない場合でも収益性が確保されるような指定時間幅の変更をユーザに提案するので、輸送事業者の収益の確保とユーザの利便性とをより高めることができる。 (Item 2)
The operation management system according to
According to this, even if the transport operator's profitability is not secured according to the user's initial request, the user is suggested to change the specified time range in a way that will ensure profitability, so that the transport operator's profits can be secured. User convenience can be further improved.
(事項3)
事項2に記載の運行管理システムは、前記利用料金の必要最低限の金額として基本価格が予め設定されており、前記受付部は、前記リクエストにおいて前記基本価格と同額または前記基本価格よりも高い金額の支払い提示金額を受け付け、前記状態算出部は、前記クラスタにおける前記収益を該クラスタに含まれるリクエストにおける支払い提示金額に基づいて算出し、前記運行決定部は、前記収益が前記収益しきい値に達しておらず前記基本価格よりも高い支払い提示金額を提示したユーザが存在するクラスタの利用料金を前記基本価格から値引きすることを、前記乗物を利用しようとするユーザに対して提示する。
これによれば、ユーザの当初のリクエストによって輸送事業者の収益性が確保されそうもない場合に、追加の料金を支払って他のユーザを勧誘する手段をユーザに与えることにより、輸送事業者の収益の確保とユーザの利便性とをより高めることができる。 (Item 3)
In the operation management system described in Item 2, a basic price is set in advance as the minimum necessary amount of the usage fee, and the reception unit is configured to accept an amount equal to or higher than the basic price in the request. The state calculating unit calculates the revenue in the cluster based on the proposed payment amount in the request included in the cluster, and the operation determining unit determines that the revenue is within the revenue threshold A user who intends to use the vehicle is presented with a discount from the basic price for the usage fee of a cluster in which there is a user who has submitted a payment offer amount higher than the basic price.
According to this, if the user's original request is unlikely to ensure the profitability of the transport operator, by giving the user the means to solicit other users by paying an additional fee, the transport operator can It is possible to secure profits and improve user convenience.
事項2に記載の運行管理システムは、前記利用料金の必要最低限の金額として基本価格が予め設定されており、前記受付部は、前記リクエストにおいて前記基本価格と同額または前記基本価格よりも高い金額の支払い提示金額を受け付け、前記状態算出部は、前記クラスタにおける前記収益を該クラスタに含まれるリクエストにおける支払い提示金額に基づいて算出し、前記運行決定部は、前記収益が前記収益しきい値に達しておらず前記基本価格よりも高い支払い提示金額を提示したユーザが存在するクラスタの利用料金を前記基本価格から値引きすることを、前記乗物を利用しようとするユーザに対して提示する。
これによれば、ユーザの当初のリクエストによって輸送事業者の収益性が確保されそうもない場合に、追加の料金を支払って他のユーザを勧誘する手段をユーザに与えることにより、輸送事業者の収益の確保とユーザの利便性とをより高めることができる。 (Item 3)
In the operation management system described in Item 2, a basic price is set in advance as the minimum necessary amount of the usage fee, and the reception unit is configured to accept an amount equal to or higher than the basic price in the request. The state calculating unit calculates the revenue in the cluster based on the proposed payment amount in the request included in the cluster, and the operation determining unit determines that the revenue is within the revenue threshold A user who intends to use the vehicle is presented with a discount from the basic price for the usage fee of a cluster in which there is a user who has submitted a payment offer amount higher than the basic price.
According to this, if the user's original request is unlikely to ensure the profitability of the transport operator, by giving the user the means to solicit other users by paying an additional fee, the transport operator can It is possible to secure profits and improve user convenience.
(事項4)
事項1に記載の運行管理システムにおいて、前記受付部は、乗車を希望する時刻である乗車希望時刻と該乗車希望時刻の変更を許容できる時間幅である乗車時刻マージンとを前記ユーザに指定させることによって、前記指定時間幅の指定を受け付ける。
これによれば、希望時刻とその変更を許容できる時間とを指定させることによりユーザに直感的に指定時間幅を指定させることができる。 (Item 4)
In the traffic management system according toItem 1, the reception unit allows the user to specify a desired boarding time, which is a time at which the user wishes to board the board, and a boarding time margin, which is a time range in which a change in the desired boarding time is allowed. accepts the designation of the designated time width.
According to this, the user can intuitively specify the specified time range by specifying the desired time and the time that can be changed.
事項1に記載の運行管理システムにおいて、前記受付部は、乗車を希望する時刻である乗車希望時刻と該乗車希望時刻の変更を許容できる時間幅である乗車時刻マージンとを前記ユーザに指定させることによって、前記指定時間幅の指定を受け付ける。
これによれば、希望時刻とその変更を許容できる時間とを指定させることによりユーザに直感的に指定時間幅を指定させることができる。 (Item 4)
In the traffic management system according to
According to this, the user can intuitively specify the specified time range by specifying the desired time and the time that can be changed.
10…運行管理システム、101…画面、102…選択ボタン、103…画面、104…選択ボタン、105…終了時刻、106…受付終了時刻、107…画面、108…状態表示領域、109…ガイド表示領域、110…アクション表示領域、301…ユーザ端末、302…アクション部、303…ガイド部、304…アクション表示領域、401…運行管理サーバ、402…受付部、403…状態算出部、404…運行決定部、411…プロセッサ、412…メインメモリ、413…記憶装置、414…通信装置、415…入力装置、416…表示装置、417…バス、501…ユーザ、502…ユーザ、503…ユーザ、504…商業地域、505…遠隔地域あるいは農村地域、601…輸送事業者端末、611…画面、612…始発地点&終着地点アップロードボタン、613…時間枠&受付終了時刻設定ボタン、614…値設定ボタン、615…割合設定ボタン、616…運行計画受信ボタン
10...Operation management system, 101...Screen, 102...Selection button, 103...Screen, 104...Selection button, 105...End time, 106...Reception end time, 107...Screen, 108...Status display area, 109...Guide display area , 110... action display area, 301... user terminal, 302... action section, 303... guide section, 304... action display area, 401... operation management server, 402... reception section, 403... state calculation section, 404... operation determination section , 411... Processor, 412... Main memory, 413... Storage device, 414... Communication device, 415... Input device, 416... Display device, 417... Bus, 501... User, 502... User, 503... User, 504... Commercial area , 505...Remote area or rural area, 601...Transport operator terminal, 611...Screen, 612...Start point & destination point upload button, 613...Time frame & acceptance end time setting button, 614...Value setting button, 615...Ratio Setting button, 616...Operation plan reception button
Claims (10)
- 複数のユーザが利用料金を支払ってデマンドレスポンシブに共同で利用可能な乗物の運行を管理する運行管理システムであって、
ユーザから乗物の利用を希望する指定時間幅を指定したリクエストを受け付ける受付部と、
複数のリクエストが指定時間幅を重複させて構成されたクラスタを特定し、該クラスタに対して前記乗物を運行させることで前記利用料金によって見込まれる収益を算出する状態算出部と、
前記収益が所定の収益しきい値以上である場合に、前記クラスタに対して前記乗物を運行することを決定する運行決定部と、
を有する運行管理システム。 An operation management system that manages the operation of a vehicle that multiple users can jointly use in a demand-responsive manner by paying a usage fee,
a reception department that accepts requests from users specifying a specified time range in which they wish to use a vehicle;
a state calculation unit that identifies a cluster in which a plurality of requests are configured with overlapping specified time widths, and calculates expected revenue from the usage fee by operating the vehicle for the cluster;
an operation determining unit that determines to operate the vehicle for the cluster when the revenue is equal to or greater than a predetermined revenue threshold;
A traffic management system with - 前記収益が前記収益しきい値に達しないクラスタに含まれるユーザに対して、前記収益が前記収益しきい値以上であるクラスタに入るようにリクエストを変更することを提案するレコメンドを提示するガイド部を更に有し、
前記運行決定部は、前記ユーザが前記レコメンドを受け入れて指定時間幅を変更し前記収益が前記収益しきい値以上になったら、前記クラスタに対して前記乗物を運行することを決定する、
請求項1に記載の運行管理システム。 a guide unit that presents a recommendation to a user included in a cluster where the revenue does not reach the revenue threshold, suggesting that the user change the request so that the user is included in a cluster where the revenue is equal to or greater than the revenue threshold; It further has
The operation determining unit determines to operate the vehicle for the cluster when the user accepts the recommendation, changes the specified time range, and the revenue becomes equal to or higher than the revenue threshold.
The traffic management system according to claim 1. - 前記利用料金の必要最低限の金額として基本価格が予め設定されており、
前記受付部は、前記リクエストにおいて前記基本価格と同額または前記基本価格よりも高い金額の支払い提示金額を受け付け、
前記状態算出部は、前記クラスタにおける前記収益を該クラスタに含まれるリクエストにおける支払い提示金額に基づいて算出し、
前記運行決定部は、前記収益が前記収益しきい値に達しておらず前記基本価格よりも高い支払い提示金額を提示したユーザが存在するクラスタの利用料金を前記基本価格から値引きすることを、前記乗物を利用しようとするユーザに対して提示する、
請求項2に記載の運行管理システム。 A basic price is set in advance as the minimum necessary amount of the usage fee,
The reception unit accepts a proposed payment amount equal to or higher than the base price in the request;
The state calculation unit calculates the revenue in the cluster based on the payment amount proposed in the request included in the cluster,
The operation determining unit may reduce the usage fee from the base price of a cluster in which there is a user whose revenue has not reached the revenue threshold and who has submitted a payment offer amount higher than the base price. Presented to users who intend to use the vehicle,
The traffic management system according to claim 2. - 前記受付部は、乗車を希望する時刻である乗車希望時刻と該乗車希望時刻の変更を許容できる時間幅である乗車時刻マージンとを前記ユーザに指定させることによって、前記指定時間幅の指定を受け付ける、
請求項1に記載の運行管理システム。 The reception unit accepts the designation of the specified time range by having the user specify a desired boarding time, which is the time when the user wishes to board the board, and a boarding time margin, which is a time range that allows for a change in the desired boarding time. ,
The traffic management system according to claim 1. - 複数のユーザが利用料金を支払ってデマンドレスポンシブに共同で利用可能な乗物の運行を管理するための運行管理方法であって、
ユーザから乗物の利用を希望する指定時間幅を指定したリクエストを受け付け、
複数のリクエストが指定時間幅を重複させて構成されたクラスタを特定し、該クラスタに対して前記乗物を運行させることで前記利用料金によって見込まれる収益を算出し、
前記収益が所定の収益しきい値以上である場合に、前記クラスタに対して前記乗物を運行することを決定する、
ことをコンピュータが実行する運行管理方法。 An operation management method for managing the operation of a vehicle that can be jointly used by multiple users in a demand-responsive manner by paying a usage fee, the method comprising:
Accepts requests from users specifying the specified time range in which they wish to use the vehicle,
Identifying a cluster in which multiple requests overlap in specified time widths, calculating expected revenue from the usage fee by operating the vehicle for the cluster,
determining to operate the vehicle to the cluster if the revenue is greater than or equal to a predetermined revenue threshold;
An operation management method in which a computer performs the operations. - 前記収益が前記収益しきい値に達しないクラスタに含まれるユーザに対して、前記収益が前記収益しきい値以上であるクラスタに入るようにリクエストを変更することを提案するレコメンドを提示し、
前記ユーザが前記レコメンドを受け入れて指定時間幅を変更し前記収益が前記収益しきい値以上になったら、前記クラスタに対して前記乗物を運行することを決定する、
ことをコンピュータが実行する、
請求項5に記載の運行管理方法。 presenting a recommendation to a user included in a cluster where the revenue does not reach the revenue threshold, suggesting that the user change the request so that the user is included in a cluster where the revenue is equal to or greater than the revenue threshold;
If the user accepts the recommendation and changes the specified time range and the revenue becomes equal to or greater than the revenue threshold, determining to operate the vehicle for the cluster;
A computer performs
The operation management method according to claim 5. - 前記利用料金の必要最低限の金額として基本価格が予め設定されており、
前記リクエストにおいて前記基本価格と同額または前記基本価格よりも高い金額の支払い提示金額を受け付け、
前記クラスタにおける前記収益を該クラスタに含まれるリクエストにおける支払い提示金額に基づいて算出し、
前記収益が前記収益しきい値に達しておらず前記基本価格よりも高い支払い提示金額を提示したユーザが存在するクラスタの利用料金を前記基本価格から値引きすることを、前記乗物を利用しようとするユーザに対して提示する、
ことをコンピュータが実行する、
請求項6に記載の運行管理方法。 A basic price is set in advance as the minimum necessary amount of the usage fee,
accepting a proposed payment amount equal to or higher than the base price in the request;
Calculating the revenue in the cluster based on the payment amount offered in the request included in the cluster,
In order to reduce the usage fee from the base price of a cluster in which there is a user whose revenue has not reached the revenue threshold and who has submitted a payment offer higher than the base price, the user attempts to use the vehicle. to present to the user,
A computer performs
The operation management method according to claim 6. - 複数のユーザが利用料金を支払ってデマンドレスポンシブに共同で利用可能な乗物の運行を管理するための運行管理プログラムであって、
ユーザから乗物の利用を希望する指定時間幅を指定したリクエストを受け付け、
複数のリクエストが指定時間幅を重複させて構成されたクラスタを特定し、該クラスタに対して前記乗物を運行させることで前記利用料金によって見込まれる収益を算出し、
前記収益が所定の収益しきい値以上である場合に、前記クラスタに対して前記乗物を運行することを決定する、
ことをコンピュータに実行させる運行管理プログラム。 An operation management program for managing the operation of a vehicle that can be jointly used by multiple users in a demand-responsive manner by paying a usage fee,
Accepts requests from users specifying the specified time range in which they wish to use the vehicle,
Identifying a cluster in which multiple requests overlap in specified time widths, calculating expected revenue from the usage fee by operating the vehicle for the cluster,
determining to operate the vehicle to the cluster if the revenue is greater than or equal to a predetermined revenue threshold;
An operation management program that makes a computer perform certain tasks. - 前記収益が前記収益しきい値に達しないクラスタに含まれるユーザに対して、前記収益が前記収益しきい値以上であるクラスタに入るようにリクエストを変更することを提案するレコメンドを提示し、
前記ユーザが前記レコメンドを受け入れて指定時間幅を変更し前記収益が前記収益しきい値以上になったら、前記クラスタに対して前記乗物を運行することを決定する、
ことをコンピュータに実行させる、
請求項8に記載の運行管理プログラム。 presenting a recommendation to a user included in a cluster where the revenue does not reach the revenue threshold, suggesting that the user change the request so that the user is included in a cluster where the revenue is equal to or greater than the revenue threshold;
If the user accepts the recommendation and changes the specified time range and the revenue becomes equal to or greater than the revenue threshold, determining to operate the vehicle for the cluster;
make a computer do something
The operation management program according to claim 8. - 前記利用料金の必要最低限の金額として基本価格が予め設定されており、
前記リクエストにおいて前記基本価格と同額または前記基本価格よりも高い金額の支払い提示金額を受け付け、
前記クラスタにおける前記収益を該クラスタに含まれるリクエストにおける支払い提示金額に基づいて算出し、
前記収益が前記収益しきい値に達しておらず前記基本価格よりも高い支払い提示金額を提示したユーザが存在するクラスタの利用料金を前記基本価格から値引きすることを、前記乗物を利用しようとするユーザに対して提示する、
ことをコンピュータに実行させる、
請求項9に記載の運行管理プログラム。 A basic price is set in advance as the minimum necessary amount of the usage fee,
accepting a proposed payment amount equal to or higher than the base price in the request;
Calculating the revenue in the cluster based on the payment amount offered in the request included in the cluster,
In order to reduce the usage fee from the base price of a cluster in which there is a user whose revenue has not reached the revenue threshold and who has submitted a payment offer higher than the base price, the user attempts to use the vehicle. to present to the user,
make a computer do something
The operation management program according to claim 9.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2022035662A JP2023131019A (en) | 2022-03-08 | 2022-03-08 | Operation management system, method, and program |
JP2022-035662 | 2022-03-08 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023171461A1 true WO2023171461A1 (en) | 2023-09-14 |
Family
ID=87935205
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2023/007254 WO2023171461A1 (en) | 2022-03-08 | 2023-02-28 | Operation management system, method, and program |
Country Status (2)
Country | Link |
---|---|
JP (1) | JP2023131019A (en) |
WO (1) | WO2023171461A1 (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014002267A1 (en) * | 2012-06-29 | 2014-01-03 | トヨタ自動車株式会社 | On-demand vehicle operation management device, on-demand vehicle operation management method, and on-demand vehicle operation management system |
JP2020067932A (en) * | 2018-10-26 | 2020-04-30 | マツダ株式会社 | Automobile operation management system |
WO2020262673A1 (en) * | 2019-06-28 | 2020-12-30 | 株式会社NearMe | Information processing device, information processing method and program |
-
2022
- 2022-03-08 JP JP2022035662A patent/JP2023131019A/en active Pending
-
2023
- 2023-02-28 WO PCT/JP2023/007254 patent/WO2023171461A1/en unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014002267A1 (en) * | 2012-06-29 | 2014-01-03 | トヨタ自動車株式会社 | On-demand vehicle operation management device, on-demand vehicle operation management method, and on-demand vehicle operation management system |
JP2020067932A (en) * | 2018-10-26 | 2020-04-30 | マツダ株式会社 | Automobile operation management system |
WO2020262673A1 (en) * | 2019-06-28 | 2020-12-30 | 株式会社NearMe | Information processing device, information processing method and program |
Also Published As
Publication number | Publication date |
---|---|
JP2023131019A (en) | 2023-09-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210319380A1 (en) | System and method for facilitating a transport service for drivers and users of a geographic region | |
JP5928588B2 (en) | On-demand vehicle operation management device, on-demand vehicle operation management method, and on-demand vehicle operation management system | |
US20170169366A1 (en) | Systems and Methods for Adjusting Ride-Sharing Schedules and Routes | |
US20150032485A1 (en) | Digital method For Providing Transportation Services | |
JP2022093574A (en) | Shared vehicle management device, shared vehicle management system, and shared vehicle management method | |
KR101718433B1 (en) | The method of proving taxi carpool service | |
JP7007938B2 (en) | Information processing methods, information processing systems and programs | |
KR101771512B1 (en) | Apparatus and method for providing chaufferur service | |
KR101742963B1 (en) | Relay system and method for personal based sharing of rental cars | |
KR101851893B1 (en) | The method of proving taxi carpool service | |
JP2003308596A (en) | Taxi-sharing reservation operation system | |
US20220027818A1 (en) | Information processing apparatus, information processing method and non-transitory storage medium | |
JP2002024659A (en) | Taxi dispatch reserving system | |
US11694271B2 (en) | Multicomputer processing of user data with centralized event control | |
WO2023171461A1 (en) | Operation management system, method, and program | |
JP2002230246A (en) | Resource allocation management system | |
JP7295720B2 (en) | Vehicle allocation management device and vehicle allocation management method | |
JP6409159B1 (en) | Bus arrangement operation method, server and program | |
KR101924346B1 (en) | Method, system and non-transitory computer-readable recording medium for managing real-time automobile reservation | |
JP2004030265A (en) | Vehicle dispatching management apparatus and vehicle dispatching management method | |
US20170039504A1 (en) | Systems and methods to administer a dispatch platform affiliate program | |
KR102435961B1 (en) | Apparatus and method for dispatching construction vehicles in ranking order based on crew(association) | |
US12051115B2 (en) | Multicomputer processing of user data with centralized event control | |
JP7072197B1 (en) | Operation planning equipment, operation planning method, and operation planning program | |
JP7483272B2 (en) | PROGRAM AND INFORMATION PROCESSING APPARATUS |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23766639 Country of ref document: EP Kind code of ref document: A1 |