JP7844907B2 - Railway revenue estimation device, railway revenue estimation method, and railway revenue estimation program - Google Patents

Description

This invention relates, for example, to a railway revenue estimation device, a railway revenue estimation method, and a railway revenue estimation program that calculate revenue for each train, station, section, and time.

When revising public transportation schedules, it is necessary not only to improve convenience for passengers but also to maximize the profits of transportation operators.
For example, Patent Document 1 discloses a method for obtaining yield management evaluation indicators that optimize revenue by adjusting the price according to demand when the right to occupy seats, berths, passenger rooms, etc., is sold together with the fare.

Furthermore, Patent Document 2 discloses a train operation management system that calculates the cost values of the train schedule (costs incurred in recovering from delays, costs of electricity consumption, costs of passenger occupancy, costs of station congestion, etc.) before and after making changes to the train schedule.

Japanese Patent Publication No. 2019-3394 Patent No. 6951996

However, the conventional methods and systems described above have the following problems.
In other words, the methods and systems disclosed in the above-mentioned publication do not allow for knowing which trains are currently generating the most fares, making it difficult to take measures such as strengthening the service of unprofitable trains or reducing the number of unprofitable trains.

Specifically, while the method described in Patent Document 1 mentions sections, occupancy rights, and fares, it does not calculate or visualize the revenue for each train.
The system configuration described in Patent Document 2 does not take into account the "revenue of each train," which is calculated by multiplying the combination of stops, fares, and passenger numbers. Therefore, it is necessary to consider which type of train is appropriate for which section of the route.

The object of this invention is to provide a railway revenue estimation device, a railway revenue estimation method, and a railway revenue estimation program capable of estimating the profitability of each train in operation.

The railway revenue estimation device according to the first invention is a railway revenue estimation device that estimates revenue for each train using passenger fare data for passengers using railway stations, and comprises a data acquisition unit, a total fare calculation unit, and a train revenue estimation unit. The data acquisition unit acquires data on the number of passengers getting on and off at each station, train operation timetable data, and fare table data for each station. The total fare calculation unit calculates the total fare for each train based on the passenger number data, operation timetable data, and fare table data acquired by the data acquisition unit. The train revenue estimation unit estimates the revenue for each train based on the total fare for each train calculated by the total fare calculation unit.

Here, using data on the number of passengers getting on and off at each station's ticket gate, data on the train schedules used by passengers, and data on fare tables between stations, the total fare paid by each passenger is calculated for each train, and the revenue for each train is estimated based on the total fares for each train.
Here, the data on the number of passengers getting on and off may be estimated based on the travel routes estimated using data from each passenger passing through the ticket gates installed at each station.

The revenue per train may be estimated, for example, as the sum of fares for each passenger who boarded or alighted on each train, or it may be estimated by taking into account the operating costs of each train.
This allows us to estimate the profitability of each train by using fare tables, train schedule data, and passenger data to calculate the total fare paid by passengers for each train.

The railway revenue estimation device according to the second invention is the same as the railway revenue estimation device according to the first invention, wherein the train revenue estimation unit estimates the revenue for each train using data on the operating costs associated with the operation of the train.
This allows us to estimate the revenue for each train on which passengers boarded or alighted, based on the total passenger fares mentioned above and the operating costs necessary for train operation (electricity costs, personnel costs, etc.).

The railway revenue estimation device according to the third invention is a railway revenue estimation device according to the first or second invention, further comprising a route estimation unit that estimates the travel route of each passenger from ticket gate passage data acquired when a passenger passes through a ticket gate installed at a railway station.
This allows us to estimate the number of passengers getting on and off each train by estimating the travel route of each passenger based on ticket gate passage data (entry and exit records, etc.).

The railway revenue estimation device according to the fourth invention is a railway revenue estimation device according to the third invention, further comprising a passenger count estimation unit that estimates the number of passengers getting on and off at each station of each train based on the travel route of each passenger estimated by the route estimation unit.
This allows the system to estimate which train each passenger boarded by using the travel route estimated by the route estimation unit, thereby estimating the number of passengers getting on and off at each station for each train.

The fifth invention relates to a railway revenue estimation device, which is the same as the fourth invention, wherein the data acquisition unit acquires the number of passengers getting on and off at each station for each train, which is estimated by the passenger passenger estimation unit.
This allows the passenger count estimation unit to obtain the number of passengers getting on and off at each station for each train, which can then be used to estimate the revenue for each train.

The railway revenue estimation device according to the sixth invention is a railway revenue estimation device according to any one of the first to fifth inventions, wherein the total fare calculation unit calculates the total fare paid by the passenger for each station where the passenger disembarks.
This allows for easy identification of stations with high and low total fares by calculating the total fare for each station where a passenger disembarks, based on the fare paid by the passenger.

The railway revenue estimation device according to the seventh invention is a railway revenue estimation device according to any one of the first to sixth inventions, further comprising a display control unit that causes the estimation results from the train revenue estimation unit to be displayed on a display device.
This allows the profitability of each train, estimated by the train revenue estimation unit, to be displayed on the display device, making it easy to recognize, for example, which trains are highly profitable.

The railway revenue estimation device according to the eighth invention is a railway revenue estimation device according to any one of the first to seventh inventions, further comprising a storage unit that stores data on the number of passengers, data on train schedules, and data on fare tables.
This allows the system to retrieve passenger boarding and alighting data, train schedule data, and fare table data for each station from the memory unit, enabling the estimation of revenue for each train as described above.

The ninth invention relates to a railway revenue estimation method that estimates revenue for each train using passenger fare data for passengers using railway stations, and comprises a data acquisition step, a total fare calculation step, and a train revenue estimation step. In the data acquisition step, data on the number of passengers boarding and alighting at each station, train operation timetable data, and fare table data for each station are acquired. In the total fare calculation step, the total fare for each train is calculated based on the passenger boarding and alighting data, operation timetable data, and fare table data acquired in the data acquisition step. In the train revenue estimation step, the revenue for each train is estimated based on the total fare for each train calculated in the total fare calculation step.

Here, using data on the number of passengers getting on and off at each station's ticket gate, data on the train schedules used by passengers, and data on fare tables between stations, the total fare paid by each passenger is calculated for each train, and the revenue for each train is estimated based on the total fares for each train.
Here, the data on the number of passengers getting on and off may be estimated based on the travel routes estimated using data from each passenger passing through the ticket gates installed at each station.

The revenue per train may be estimated, for example, as the sum of fares for each passenger who boarded or alighted on each train, or it may be estimated by taking into account the operating costs of each train.
This allows us to estimate the profitability of each train by using fare tables, train schedule data, and passenger data to calculate the total fare paid by passengers for each train.

The tenth invention relates to a railway revenue estimation program that estimates revenue for each train using passenger fare data for railway stations. The program causes a computer to execute a railway revenue estimation method comprising a data acquisition step, a total fare calculation step, and a train revenue estimation step. The data acquisition step acquires data on the number of passengers boarding and alighting at each station, train schedule data, and fare table data for the sections between stations. The total fare calculation step calculates the total fare for each train based on the passenger boarding and alighting data, schedule data, and fare table data acquired in the data acquisition step. The train revenue estimation step estimates the revenue for each train based on the total fare calculated in the total fare calculation step.

Here, using data on the number of passengers getting on and off at each station's ticket gate, data on the train schedules used by passengers, and data on fare tables between stations, the total fare paid by each passenger is calculated for each train, and the revenue for each train is estimated based on the total fares for each train.
Here, the data on the number of passengers getting on and off may be estimated based on the travel routes estimated using data from each passenger passing through the ticket gates installed at each station.

The revenue per train may be estimated, for example, as the sum of fares for each passenger who boarded or alighted on each train, or it may be estimated by taking into account the operating costs of each train.
This allows us to estimate the profitability of each train by using fare tables, train schedule data, and passenger data to calculate the total fare paid by passengers for each train.

According to the railway revenue estimation device of the present invention, it is possible to estimate the profitability of each train in operation.

A control block diagram showing the configuration of a railway revenue estimation device according to one embodiment of the present invention. A graph showing the total fares paid by passengers for each train, as estimated by the train revenue estimation unit of the railway revenue estimation device shown in Figure 1. Figure 1 shows an example of a display showing the total amount of fares paid by passengers at each station, calculated by the total fare calculation unit of the railway revenue estimation device, indicated by the size of the circles. A flowchart illustrating the processing flow of the railway revenue estimation method of the present invention.

A railway revenue estimation device relating to one embodiment of the present invention will be explained below using Figures 1 to 4.
In this embodiment, unnecessary details may be omitted. For example, detailed explanations of already well-known matters or redundant explanations of substantially identical configurations may be omitted. This is to avoid the following explanation becoming unnecessarily verbose and to facilitate understanding for those skilled in the art.
Furthermore, the applicant provides the accompanying drawings and the following description so that those skilled in the art may fully understand the present invention, and not intends to limit the subject matter described in the claims.

(1) Configuration of the Railway Revenue Estimation Device 10 As shown in Figure 1, the railway revenue estimation device 10 according to this embodiment is connected to an input device 2, a data server 21, and a display device 30. It obtains passenger pass-through data for each passenger recorded at the ticket gates 20a, 20b, and 20c from the data server 21 and estimates the revenue for each train based on the passenger fare data.

Here, the multiple ticket gates 20a, 20b, and 20c shown in Figure 1 are, for example, automatic ticket gates installed at stations A, B, and C, respectively, which read information recorded on IC cards or magnetic tickets held by passengers and determine whether or not each passenger is allowed to pass through.
The passenger passage data acquired at each ticket gate 20a, 20b, and 20c is transmitted to the data server 21 when the passenger passes through the ticket gate 20a, 20b, and 20c, and is stored as ticket gate passage OD (Origin-Destination) data.

The input device 2 receives input from the operator, including data used in the railway revenue estimation device 10 (for example, train schedule data D2, etc.) and commands to start the revenue estimation process for each train, which will be described later.
The data server 21 stores ticket gate passage data D1, which is recorded when a passenger passes through ticket gates 20a to 20c. The ticket gate passage data D1 is generated based on entry and exit records collected from ticket gates 20a, 20b, and 20c installed at each railway station.

The "entry record" included in the ticket gate passage data D1 contains information including the entry station and the time of passage through the ticket gate. The "exit record" included in the ticket gate passage data D1 contains information including the exit station and the time of passage through the ticket gate. A set of data consisting of an entry record and its corresponding exit record (sometimes referred to as "trip data") identifies a single trip for a particular passenger, detailing when and where they departed and when they arrived.

Unless otherwise specified, one "passenger" refers to the subject of one trip. One trip corresponds one-to-one with one passenger. "Estimated current route" is information indicating which trains each passenger used in the current train schedule to complete one trip.
The display device 30 displays the results of the revenue estimation for each train estimated by the railway revenue estimation device 10, as well as the total fares for each train and each station.

As shown in Figure 1, the railway revenue estimation device 10 of this embodiment includes a route estimation unit 11, a passenger passenger estimation unit 12, a storage unit 13, a data acquisition unit 14, a total fare calculation unit 15, a train revenue estimation unit 16, and a display control unit 17.
The route estimation unit 11 obtains ticket gate passage data D1, which is recorded when a passenger passes through ticket gates 20a to 20c, from the data server 21, and, by referring to the train schedule data, estimates the route that each passenger will take to travel from the station they entered to the station they exited, according to the train schedule.

The passenger boarding/alighting estimation unit 12 estimates the number of passengers boarding and alighting for each train by estimating which train each passenger boarded and alighted on, based on the travel route of each passenger estimated by the route estimation unit 11.
As shown in Figure 1, the memory unit 13 stores fare tables, operating cost tables, data on the number of passengers getting on and off at each station for each train, and operating schedule data D2, etc.

The fare table data shows the fare between the entry station and exit station of the train the passenger boarded, and is predetermined by the railway company.
The operating cost table contains data related to the costs of operating a train (electricity costs, labor costs, etc.), and is set for each train according to the distance traveled (between the entry station and the exit station).

The data on the number of passengers getting on and off at each station for each train is stored as the estimation result of the passenger count estimation unit 12 described above.
The D2 timetable data corresponds to the current train timetable and represents information showing the train timetable, or the train operation plan. In typical railway passenger transport, daytime is the "operating time" when passenger transport takes place, and the time from late night to early morning is the "maintenance time" when passenger transport is suspended and track maintenance work is carried out. The operating time and maintenance time repeat in a 24-hour cycle. The timetable data is composed of the operation data for each train that operates within a single operating time period.

Train schedules are created separately for each direction, such as "upbound" and "downbound," and these schedules are further created on a daily basis. The schedule data includes multiple types of data depending on the direction and day.
Furthermore, the train schedule data includes not only the northbound and southbound schedules, but also daily variations such as the weekday schedule, which applies to weekday operating hours, and the holiday schedule, which applies to holiday operating hours. In addition, it also includes seasonal schedules, which apply only to weekends during limited periods, such as autumn, and include extra trains operated to transport tourists.

The data acquisition unit 14 acquires fare tables, operating costs, passenger numbers at each station for each train, and train schedule data stored in the memory unit 13, which are used to estimate revenue for each train.
The total fare calculation unit 15 calculates the total fare paid by passengers for each train based on the passenger count data, the train schedule data, and the fare table data acquired by the data acquisition unit 14.

Specifically, the total fare calculation unit 15 estimates which train each passenger boarded and alighted at based on the passenger data. Then, the total fare calculation unit 15 calculates the fare from the boarding station to the alighting station for each passenger, assigns that fare to the train they rode, and calculates the total. This allows the system to estimate how much fare was paid for each train and each station a passenger disembarked at.

The train revenue estimation unit 16 estimates the revenue for each train based on the total fares for each train calculated by the total fare calculation unit 15.
The revenue estimated by the train revenue estimation unit 16 may be shown for each train as the total amount of fares for passengers estimated to have ridden that train, as shown in Figure 2, or it may be shown as the amount after deducting the operating costs incurred when running the train from the starting station to the final station, taking into account the operating cost data stored in the memory unit 13.

Figure 2 shows trains (train numbers) ranked in descending order of estimated total fare revenue for a selected day, from highest to lowest. For example, train number 1704, estimated to have the highest revenue, is estimated to have had a total fare revenue of approximately 800,000 yen for the selected day. Train number 1708, estimated to have the second highest revenue, is estimated to have had a total fare revenue of approximately 750,000 yen for the selected day.

Furthermore, the revenue estimated by the train revenue estimation unit 16 may be calculated for each station where a passenger disembarks.
For example, in Figure 3, the total amount of fares paid by passengers at each station, calculated by the total fare calculation unit 15 of the railway revenue estimation device 10, is shown by the size of the circles.
In other words, in Figure 3, the center of the circle indicates the location (latitude and longitude) of the station, and the size of the circle indicates the total amount of fares paid by passengers who disembarked at that station. Therefore, the larger the circle, the greater the total amount of fares paid by passengers who disembarked at that station.

This makes it easy to identify which disembarking stations result in a higher or lower total fare paid by passengers.
The display control unit 17 controls the display device 30 based on the estimated revenue for each train estimated by the train revenue estimation unit 16.
Specifically, the display control unit 17 causes the display device 30 to display a graph showing the estimated total fare paid by passengers for each train, as shown in Figure 2. Furthermore, as shown in Figure 3, the display control unit 17 controls the display device 30 to display information indicating the relative size of the total fare paid by passengers at each station where they disembark.

This allows the display screen of the display device 30 to display data showing the profitability of each train as shown in Figures 2 and 3, data showing the revenue for each station where passengers disembark, etc., making it easy to recognize which trains are currently generating the most fares. Therefore, railway companies can take measures such as strengthening the types and operating sections of highly profitable trains or reducing the number of less profitable trains.
As a result, by providing railway companies with useful information regarding railway operations, new value will be created in station management evaluations, and by using this information as reference during timetable revisions, it will be possible to optimize railway business revenue.

<Method for Estimating Railway Revenue>
The railway revenue estimation device 10 of this embodiment, with the configuration described above, calculates the total fare for each train and each station, and estimates the revenue for each train. Here, the processing flow of the railway revenue estimation method will be explained using Figure 4.

In other words, as shown in Figure 4, in step S11, the route estimation unit 11 of the railway revenue estimation device 10 acquires ticket gate passage data D1 from the data server 21 in order to estimate the number of passengers getting on and off at each station for each train, which is necessary to estimate the revenue for each train.
Next, in step S12, the route estimation unit 11 estimates the travel route, including information such as which train was boarded, by referring to the train schedule, based on the entry station, exit station, entry time, and exit time included in the ticket gate passage data D1 acquired in step S11.

Next, in step S13, the passenger number estimation unit 12 estimates the number of passengers getting on and off each train along the travel route estimated by the route estimation unit 11.
Next, in step S14, the data acquisition unit 14 acquires the operation schedule data and fare table data stored in the storage unit 13.
Next, in step S15, the total fare calculation unit 15 calculates the total fare for each train and each station where passengers disembark, based on the estimated number of passengers getting on and off each train, while referring to the train schedule data and fare table data acquired in step S14.

Next, in step S16, the train revenue estimation unit 16 estimates the revenue for each train based on the total fare for each train and each station where the passenger disembarked, calculated in step S15, and the operating cost data for each train stored in the memory unit 13.
Next, in step S17, the display control unit 17 causes the display device 30 to display a graph or the like (see Figure 2) showing the revenue for each train estimated in step S16.

<Main Features>
The railway revenue estimation device 10 of this embodiment comprises a data acquisition unit 14, a total fare calculation unit 15, and a train revenue estimation unit 16. The data acquisition unit 14 acquires data on the number of passengers getting on and off the trains through ticket gates 20a to 20c installed at each station, data on train schedules, and data on fare tables between stations. The total fare calculation unit 15 calculates the total fare for each passenger based on the passenger data, schedule data, and fare table data acquired by the data acquisition unit 14. The train revenue estimation unit 16 estimates the revenue for each train based on the total fare for each passenger calculated by the total fare calculation unit 15.
This allows us to estimate the profitability of each train on which passengers boarded or alighted by calculating the total fare paid by passengers using fare tables, train schedule data, and passenger count data.

[Other embodiments]
Although one embodiment of the present invention has been described above, the present invention is not limited to the above embodiment, and various modifications are possible without departing from the spirit of the invention.

(A)
In the above embodiments, examples of the present invention were described as a railway revenue estimation device and a railway revenue estimation method. However, the present invention is not limited thereto.
For example, the present invention may be implemented as a railway revenue estimation program that causes a computer to execute the railway revenue estimation method described above.

This railway revenue estimation program is stored in the memory (storage unit) installed in the railway revenue estimation device. The CPU reads the railway revenue estimation program stored in memory and causes the hardware to execute each step. More specifically, the same effect as above can be obtained by the CPU reading the railway revenue estimation program and executing the data acquisition step, the total fare calculation step, and the train revenue estimation step described above.
Furthermore, the present invention may be implemented as a recording medium storing a railway revenue estimation program.

(B)
In the above embodiment, an example was described in which the data acquisition unit 14 acquires data from the storage unit 13 that results from estimating the number of passengers getting on and off the train along the travel route of each passenger estimated from the ticket gate passage data D1. However, the present invention is not limited to this.
For example, the data regarding the number of passengers getting on and off at each station for each train may not be estimated based on the estimation results of the route estimation unit described above, but rather may be data acquired by other means and stored in the memory unit.

(C)
In the above embodiment, an example was described in which a storage unit 13 for storing data such as the number of passengers, fare tables, and operating schedules used to estimate revenue for each train is provided within the railway revenue estimation device 10. However, the present invention is not limited thereto.

For example, the storage unit that stores data such as the number of passengers getting on and off, fare tables, and train schedules may be located on a server or the like, which is located outside the railway revenue estimation device.
Even in this case, the train revenue estimation unit 16 can obtain data such as the number of passengers, fare tables, and operating schedules from a server located outside the railway revenue estimation device 10, thereby achieving the same effect as described above.

(D)
In the above embodiment, an example was described in which a display control unit 17 provided in the railway revenue estimation device 10 controls the display of an externally provided display device 30. However, the present invention is not limited to this.
For example, the railway revenue estimation device may be configured to include a display unit.

(E)
In the above embodiment, the total fare calculation unit 15 of the railway revenue estimation device 10 was described as calculating the total fare paid by passengers at each station where the passenger disembarked. However, the present invention is not limited to this.
For example, the total fare calculation unit may be configured to calculate the total fare paid by the passenger for each station where the passenger boarded the train.

In this case, it is easy to identify which station the passengers who boarded the train from paid the highest fare.

The railway revenue estimation device of the present invention has the effect of estimating the profitability of each train in operation, and therefore can be widely applied to various systems for managing railway profitability.

2 Input device 10 Railway revenue estimation device 11 Route estimation unit 12 Passenger/alighter passenger estimation unit 13 Storage unit 14 Data acquisition unit 15 Total fare calculation unit 16 Train revenue estimation unit 17 Display control units 20a, 20b, 20c Ticket gate 21 Data server 30 Display device D1 Ticket gate passage data D2 Operation timetable data

Claims (6)

A railway revenue estimation device that estimates revenue for each train using passenger fare data for passengers using railway stations,
A data acquisition unit that acquires data on the number of passengers getting on and off at each station through the ticket gates, train schedule data, and fare table data for each station.
Based on the passenger data, the train schedule data, and the fare table data acquired by the data acquisition unit, the total fare calculation unit calculates the total fare for each train and the total fare paid by each passenger at each station where the passenger disembarked .
A train revenue estimation unit estimates the revenue for each train based on the total fare for each train calculated by the total fare calculation unit,
A railway revenue estimation device equipped with the following features. A railway revenue estimation device that estimates revenue for each train using passenger fare data for passengers using railway stations,
A data acquisition unit that acquires data on the number of passengers getting on and off at each station through the ticket gates, train schedule data, and fare table data between stations.
Based on the passenger data, the train schedule data, and the fare table data acquired by the data acquisition unit, the total fare calculation unit calculates the total fare for each train and the total fare paid by each passenger at each station where the passenger boarded.
A train revenue estimation unit estimates the revenue for each train based on the total fare for each train calculated by the total fare calculation unit,
A railway revenue estimation device equipped with the following features. A railway revenue estimation method that estimates revenue for each train using passenger fare data for passengers using railway stations,
A data acquisition step to obtain data on the number of passengers who boarded or alighted at each station, train schedule data, and fare table data for each station.
A total fare calculation step is performed to calculate the total fare for each train and the total fare paid by each passenger at each station where the passenger disembarked, based on the passenger data, the train schedule data, and the fare table data obtained in the data acquisition step.
A train revenue estimation step is performed to estimate the revenue for each train based on the total fare for each train calculated in the total fare calculation step,
A railway revenue estimation method equipped with the following features. A railway revenue estimation method that estimates revenue for each train using passenger fare data for passengers using railway stations,
A data acquisition step to obtain data on the number of passengers who boarded or alighted at each station, train schedule data, and fare table data for each station.
A total fare calculation step is performed to calculate the total fare for each train and the total fare paid by each passenger at each station where the passenger boarded, based on the passenger data, the train schedule data, and the fare table data obtained in the data acquisition step.
A train revenue estimation step is performed to estimate the revenue for each train based on the total fare for each train calculated in the total fare calculation step,
A railway revenue estimation method equipped with the following features. A railway revenue estimation program that estimates revenue for each train using passenger fare data for passengers using railway stations,
A data acquisition step to obtain data on the number of passengers who boarded or alighted at each station, train schedule data, and fare table data for each station.
A total fare calculation step is performed to calculate the total fare for each train based on the passenger data, the train schedule data, and the fare table data obtained in the data acquisition step,
A train revenue estimation step estimates the revenue for each train based on the total fare for each train calculated in the total fare calculation step, and the total fare paid by each passenger at each station where the passenger disembarked.
A railway revenue estimation program that causes a computer to execute a railway revenue estimation method equipped with [specific features/features]. A railway revenue estimation program that estimates revenue for each train using passenger fare data for passengers using railway stations,
A data acquisition step to obtain data on the number of passengers who boarded or alighted at each station, train schedule data, and fare table data for each station.
A total fare calculation step is performed to calculate the total fare for each train based on the passenger data, the train schedule data, and the fare table data obtained in the data acquisition step,
A train revenue estimation step estimates the revenue for each train based on the total fare for each train calculated in the total fare calculation step, and the total fare paid by the passenger at each station where the passenger boarded.
A railway revenue estimation program that causes a computer to execute a railway revenue estimation method equipped with [specific features/features].