Traffic rescheduling support device and method
The train replanning support device addresses the challenge of inexperienced dispatchers by offering transparent, data-driven rescheduling plans with delay recovery rates and costs, enabling effective train rescheduling.
Patent Information
- Application Number
- JP2022142542
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-09-07
- Publication Date
- 2025-10-22
- Estimated Expiration
- 2042-09-07
AI Technical Summary
Existing train traffic rescheduling systems require experienced dispatchers to manually correct errors and lack transparency in rescheduling plans, making it difficult for inexperienced dispatchers to judge appropriateness and improve their skills.
A train replanning support device that calculates delay recovery rates and costs, stores disruption and replanning data, and presents past replanning information to dispatchers, allowing them to make informed rescheduling decisions.
Enables inexperienced dispatchers to perform effective train rescheduling independently by providing transparent, data-driven proposals considering both delay recovery and cost, enhancing their skills without relying on experience.
Smart Images

Figure 0007758645000001 
Figure 0007758645000002 
Figure 0007758645000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a train traffic rescheduling support device and method, which is suitable for application to, for example, a train traffic management system that manages train operations. [Background technology]
[0002] In traffic control systems, such as those for trains, when a transportation disruption such as an accident or bad weather occurs and causes a disruption to the train schedule, dispatchers will reschedule operations to minimize the disruption. Here, "rescheduling" refers to the process of changing the operation plan to return trains to normal operation, such as by suspending train operations, changing the timetable for trains arriving and departing from stations, or replacing some or all of the cars that make up the train.
[0003] Disruptions to train schedules have a high public impact, including on passengers, and require a prompt response through traffic rescheduling. However, the skills of each dispatcher in traffic rescheduling vary, and it is particularly difficult for inexperienced dispatchers to reschedule smoothly.
[0004] Therefore, in order to enable even inexperienced dispatchers to carry out smooth traffic rescheduling work, techniques have been proposed to present and implement optimal traffic rescheduling plans in the event of a transportation disruption.
[0005] For example, Patent Document 1 discloses a traffic rescheduling support system that stores the type of transportation disruption and the details of traffic rescheduling implemented in response to that disruption in a database, and when a new transportation disruption occurs, reads from the database the details of past traffic rescheduling implemented when the same transportation disruption occurred and executes them.
[0006] Furthermore, Patent Document 2 discloses a timetable rescheduling support device that, when creating a timetable rescheduling plan, quantitatively calculates the loss due to delays of each train as loss points and presents a timetable rescheduling plan that includes the loss points. [Prior art documents] [Patent documents]
[0007] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-173530 [Patent Document 2] Japanese Patent Application Laid-Open No. 2014-104794 Summary of the Invention [Problem to be solved by the invention]
[0008] In recent years, there have been problems with dispatchers using traffic control systems, such as a shortage of experienced dispatchers and the aging of experienced dispatchers, making it an urgent task to improve the skills of inexperienced young dispatchers.
[0009] In this regard, the traffic rescheduling support system disclosed in Patent Document 1 only implements the proposed traffic rescheduling plan itself, and does not provide the dispatcher with the reasons or background for deriving the proposed traffic rescheduling plan, meaning that the dispatcher has no way of knowing why the proposed traffic rescheduling plan was derived. This poses a problem in that it is difficult for inexperienced dispatchers to judge the appropriateness of the implemented traffic rescheduling plan.
[0010] Furthermore, according to the traffic rescheduling support system disclosed in Patent Document 1, if there is an error in the traffic rescheduling implemented by the traffic rescheduling support system, the dispatcher must manually correct the traffic rescheduling, but correcting the error is also a difficult task for an inexperienced dispatcher, which is a problem.
[0011] For this reason, a dispatcher who uses the traffic rescheduling support system disclosed in Patent Document 1 is required to have a certain level of knowledge and experience regarding traffic rescheduling work, and it is difficult for an inexperienced dispatcher to master this traffic rescheduling support system. In addition, it is difficult to expect that the use of this traffic rescheduling support system will improve the dispatcher's traffic rescheduling skills.
[0012] On the other hand, according to the train rescheduling support device disclosed in Patent Document 2, as described above, the losses due to delays of each train are quantitatively calculated as loss points, and a train rescheduling plan is presented including the calculated loss points. This allows the dispatcher to understand the basis for the presented train rescheduling plan and its effectiveness, which is thought to be useful in assisting train rescheduling work.
[0013] However, a traffic rescheduling plan with a low loss point is not necessarily the optimal plan, and when making traffic rescheduling plans, it is necessary to consider not only the loss point but also the overall delay recovery time of the schedule.
[0014] The present invention has been made in consideration of the above points, and aims to propose a traffic rescheduling support device and method that can support traffic rescheduling work so that dispatchers can make appropriate traffic rescheduling operations without relying on experience. [Means for solving the problem]
[0015] In order to solve this problem, in the present invention, a train replanning support device that supports train replanning operations includes a delay recovery rate calculation unit that calculates the train delay recovery rate due to a train replanning implemented in response to a transport disruption that has occurred, a cost calculation unit that calculates the cost required for the replanning, a storage unit that stores the details of the transport disruption, the details of the replanning implemented in response to the transport disruption, the delay recovery rate calculated for the replanning, and the cost calculated for the replanning as associated train replanning information, and a train replanning proposal presentation unit that, when a new transport disruption occurs, reads out the train replanning information of a train replanning implemented in the past when a transport disruption with the same or similar details as the current transport disruption occurred, and, based on the read out train replanning information, presents to a dispatcher the details of the transport disruption corresponding to the train replanning information, the details of the train replanning implemented in response to the transport disruption, the delay recovery rate calculated for the train replanning, and the cost calculated for the train replanning. The timetable rescheduling proposal presentation unit displays the details of timetable rescheduling implemented when a past transportation disruption occurred that is the same as or similar to the new transportation disruption, the delay recovery rate calculated for the timetable rescheduling, and the cost calculated for the timetable rescheduling, as well as the train timetables for all or some of the trains scheduled to operate on that day, so that the details of timetable rescheduling can be formulated by changing the times and time slots for trains stopping at each station and the train speeds between each station in the train timetable. I did so.
[0016] Furthermore, the present invention provides a train replanning support method executed by a train replanning support device that supports train replanning operations, the method comprising: a first step of calculating a train delay recovery rate due to a train replanning implemented in response to a transport disruption that has occurred and a cost required for the replanning; a second step of storing the details of the transport disruption, the details of the replanning implemented in response to the transport disruption, the delay recovery rate calculated for the replanning, and the cost calculated for the replanning as train replanning information in association with each other; and a third step of, when a new transport disruption has occurred, reading out the train replanning information of a train replanning implemented in response to a transport disruption that has occurred in the past with the same or similar details as the transport disruption in question, and presenting to a dispatcher the details of the transport disruption corresponding to the train replanning information, the details of the train replanning implemented in response to the transport disruption, the delay recovery rate calculated for the train replanning, and the cost calculated for the train replanning based on the read-out train replanning information; and Organize The support device displays the details of train operation adjustments implemented when a past transportation disruption occurred that is the same as or similar to the new transportation disruption, the delay recovery rate calculated for the relevant train operation adjustments, and the cost calculated for the relevant train operation adjustments, as well as the train operation timetables for all or some of the trains scheduled to operate on that day, so that the details of train operation adjustments can be formulated by changing the times and periods when trains stop at each station and the train speeds between stations in the train operation timetables.
[0017] According to the traffic rescheduling support device and method of the present invention, when a new transportation disruption occurs, the details of traffic rescheduling implemented when the same or similar traffic disruption occurred in the past are presented as a traffic rescheduling proposal, along with the delay recovery rate and cost required for the traffic rescheduling. This allows the dispatcher to refer to the presented traffic rescheduling proposal and implement an appropriate traffic rescheduling that takes into account both the delay recovery rate and cost. [Effects of the Invention]
[0018] According to the present invention, it is possible to realize a timetable rescheduling support device and method that can support dispatchers to carry out appropriate timetable rescheduling work independent of experience. [Brief explanation of the drawings]
[0019] [Figure 1] 1 is a block diagram showing a schematic configuration of a train traffic control system to which the present invention is applied. [Figure 2] FIG. 1 is a diagram illustrating a train operation timetable. [Figure 3] 1 is a block diagram showing a hardware configuration of a timetable replanning support device according to an embodiment of the present invention. [Figure 4] FIG. 2 is a block diagram showing an example of a table configuration in a database server device. [Figure 5] 10 is a diagram showing an example of the configuration of a commander information management table. [Figure 6] 10 is a diagram showing an example of the configuration of a schedule change parameter management table. [Figure 7] 10 is a diagram showing an example of the configuration of a timetable rescheduling information management table. [Figure 8] FIG. 2 is a block diagram showing the logical configuration of the timetable replanning support device. [Figure 9] 10 is a flowchart showing the processing steps of a timetable adjustment information registration process. [Figure 10] 10 is a flowchart showing a processing procedure for delay recovery rate calculation processing; [Figure 11] 10 is a flowchart showing the processing procedure of a cost calculation process. [Figure 12] 10 is a flowchart showing the processing steps of a timetable replanning proposal presentation process. [Figure 13] FIG. 10 is a diagram showing an example of the configuration of a timetable rescheduling planning screen. DETAILED DESCRIPTION OF THE INVENTION
[0020] An embodiment of the present invention will be described in detail below with reference to the drawings.
[0021] (1) Configuration of the train traffic control system according to this embodiment In Fig. 1, reference numeral 1 denotes a train traffic control system to which the present invention is applied as a whole. This train traffic control system 1 is a system that collectively manages train operations in accordance with a pre-created operation plan (planned timetable), and is configured with a train rescheduling support device 2, a timetable management device 3, and a database server device 4.
[0022] The traffic rescheduling support device 2 is a computer device used by a dispatcher to reschedule trains when a transportation disruption occurs and the train schedule is disrupted. When a dispatcher uses the traffic rescheduling support device 2, the dispatcher logs in by entering an ID, password, etc. that are assigned to the dispatcher in advance.
[0023] By performing a predetermined operation, the train rescheduling support device 2 can display, for example, a train schedule as shown in Fig. 2. The train schedule is a line graph with time on the horizontal axis, station order on the vertical axis, and the names of stations through which the train runs on the vertical axis. The train schedule shown in Fig. 2 shows the timetable for one train, but it is also possible to display the timetables for multiple trains on a single graph.
[0024] As will be described later, when a transportation disruption occurs, the dispatcher can formulate the details of the traffic rescheduling while visually checking the train operation timetable, and the revised planned timetable according to the formulated details of the traffic rescheduling is transmitted to the timetable management device 3 and the database server device 4. The traffic rescheduling support device 2 can also display the details of the traffic disruption when it occurs.
[0025] The timetable management device 3 is a computer device that has the function of controlling the interlocking device 5 so that each train operates according to a planned timetable, which will be described later, stored in the database server device 4. The interlocking device 5 controls switches and signals according to instructions from the timetable management device 3.
[0026] Furthermore, when the timetable management device 3 receives a revised planned timetable for traffic rescheduling from the traffic rescheduling support device 2, it checks the consistency of the timetable rescheduling (for example, consistency when instructions to change the planned timetable are received from multiple traffic rescheduling support devices 2). If the timetable management device 3 confirms that such consistency can be ensured, it then controls the operation of each train (controls the interlocking device 5) based on the revised planned timetable.
[0027] The database server device 4 is a server device that has the function of storing various information related to traffic management. The "information related to traffic management" here includes, for example, information on the planned timetable, which is a train operation plan created in advance (hereinafter referred to as planned timetable information), and information on the changed planned timetable that has been changed in accordance with the content of traffic rescheduling carried out by the dispatcher using the traffic rescheduling support device 2 (hereinafter referred to as changed timetable information).
[0028] The hardware configuration of the timetable replanning support device 2 is shown in Fig. 3. As shown in Fig. 3, the timetable replanning support device 2 is configured to include a CPU (Central Processing Unit) 10, a memory 11, a storage device 12, an input device 13, a display device 14, and a communication device 15.
[0029] The CPU 10 is a processor that controls the overall operation of the timetable replanning support device 2. The memory 11 is composed of, for example, a volatile semiconductor memory, and is used as a working memory for the CPU 10. The storage device 12 is composed of a large-capacity nonvolatile storage device such as a hard disk drive or SSD (Solid State Drive), and is used to store various programs and data that needs to be stored for a long period of time.
[0030] When the timetable replanning support device 2 is started or when needed, the necessary programs are read from the storage device 12 to the memory 11 by the CPU 10, and the programs read into the memory 11 are executed by the CPU 10, thereby performing various processes for the timetable replanning support device 2 as a whole, as described below.
[0031] The input device 13 is composed of, for example, a keyboard, a mouse, etc., and is used by the dispatcher to input various information and commands to the traffic replanning support device 2. The display device 14 is composed of, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display, etc., and is used to display necessary information. Note that instead of the input device 13 and the display device 14, a touch panel that integrates these may be used.
[0032] The communication device 15 is configured by, for example, a NIC (Network Interface Card) and performs protocol control when the traffic replanning support device 2 communicates with the timetable management device 3 and the database server device 4.
[0033] (2) Traffic rescheduling support function according to this embodiment Next, we will explain the traffic replanning support function according to this embodiment, which is installed in the traffic replanning support device 2. This traffic replanning support function accumulates information about traffic replanning implemented by the dispatcher when a transportation disruption occurs, and when a new transportation disruption occurs and causes a disruption to the train schedule, it presents to the dispatcher information about traffic replanning implemented when a similar transportation disruption occurred in the past as a traffic replanning proposal for the current traffic replanning.
[0034] In practice, the train rescheduling support device 2 accumulates and displays such "information regarding train rescheduling" as the details of the train rescheduling, the details of the transportation disruption that prompted the train rescheduling, information regarding the dispatcher who performed the train rescheduling, the delay recovery rate due to the train rescheduling, and the cost required for the train rescheduling.
[0035] Here, "delay recovery rate" refers to the rate at which train delays are recovered due to the rescheduling, and "costs required for rescheduling" refers to refund fees and electricity charges incurred due to the rescheduling. The calculation methods for "delay recovery rate" and "costs required for rescheduling" will be described later.
[0036] As a means for realizing the operation rescheduling support function according to this embodiment, the database server device 4 stores a planned timetable management table 20, a changed timetable management table 21, a timetable management table before and after operation rescheduling 22, a dispatcher information management table 23, a timetable change parameter management table 24, and an operation rescheduling information management table 25, as shown in Figure 4.
[0037] The planned timetable management table 20 is a table that stores a planned timetable that has been created in advance, and the changed timetable management table 21 is a table that stores the changed planned timetable that has been changed due to the current timetable reorganization. The pre- and post-timetable reorganization management table 22 is a table that stores the actual timetables of each train before and after the timetable reorganization.
[0038] On the other hand, the commander information management table 23 is a table used to manage information about each commander, and is created in advance and stored in the database server device. As shown in Fig. 5, this commander information management table 23 is configured with at least an ID column 23A, a name column 23B, a password column 23C, and a years of experience column 23D. In the commander information management table 23, one record (row) corresponds to one commander.
[0039] The ID column 23A stores the identification information (ID) assigned to the corresponding dispatcher, and the name column 23B stores the name of the dispatcher. The password column 23C stores the password used by the dispatcher to log in to the timetable replanning support device 2, and the years of experience column 23D stores the number of years of experience the dispatcher has in timetable replanning work.
[0040] The timetable change parameter management table 24 is a table for managing parameters used when calculating costs such as refund fees and electricity usage that arise as a result of timetable rescheduling, and is created in advance and stored in the database server device 4. As shown in Fig. 6, this timetable change parameter management table 24 is configured with a timetable rescheduling type column 24A, a loss cost column 24B, and an electricity usage column 24C. In the timetable change parameter management table 24, one record (row) corresponds to one type of change to the planned timetable, etc., that is implemented as timetable rescheduling (hereinafter referred to as a timetable rescheduling type).
[0041] The traffic rescheduling type column 24A stores specific examples of the corresponding traffic rescheduling types, such as "service suspension" which suspends train operations, "time change" which changes the train's arrival and departure times at stations, and "car change" which changes the cars that make up a train.
[0042] The loss cost column 24B stores parameters (hereinafter referred to as loss cost calculation parameters) for calculating the loss cost incurred when a timetable rescheduling of the corresponding timetable type is implemented.
[0043] For example, if the type of operation rescheduling is "service suspension," a loss cost calculation parameter with a value corresponding to the amount of loss due to ticket refunds and the like that occurs when one train is suspended at one station is stored in the loss cost column 24B. Also, if the type of operation rescheduling is "time change," a loss cost calculation parameter with a value corresponding to the amount of decrease in sales expected per unit time for one train at one station that occurs when users change to other means of transportation due to a change in train operating times is stored in the loss cost column 24B. Furthermore, if the type of operation rescheduling is "car replacement," a loss cost calculation parameter with a value corresponding to the amount of loss for one train at one station that occurs due to car replacement is stored in the loss cost column 24B.
[0044] Furthermore, the power consumption column 24C stores the change in power consumption per kilometer when a corresponding type of rescheduling is implemented as a parameter for calculating power consumption. Therefore, in the example of Figure 6, when the type of rescheduling is "suspension of service," the power consumption changes by "-2" kWh for each kilometer of one train (power consumption decreases by 2 kWh per kilometer), and when the type of rescheduling is "time change" or "car replacement," there is no change in power consumption (0 kWh).
[0045] The timetable information management table 25 is a table used to manage and store information relating to timetable rescheduling that has been implemented in the past (hereinafter referred to as timetable rescheduling information), and as shown in Figure 7, is configured with a transport disruption details column 25A, a timetable rescheduling details column 25B, a dispatcher column 25C, years of experience column 25D, a delay recovery rate column 25E, and a cost column 25F. In the timetable information management table 25, one record (row) corresponds to timetable rescheduling information relating to one timetable rescheduling that has been implemented in the past.
[0046] The transport disruption details column 25A stores the details of the transport disruption for which the corresponding rescheduling was carried out. The "transport disruption details" includes not only information on the event that occurred, such as a "personal injury accident" or a "power outage," but also information on the location where the event occurred, such as the station or section where the event occurred. The rescheduling details column 25B stores all the types of rescheduling that were actually carried out in response to the transport disruption.
[0047] Furthermore, the dispatcher column 25C stores the name of the dispatcher who performed the rescheduling, and the years of experience column 25D stores the number of years of experience the dispatcher had in rescheduling work at the time of performing the rescheduling. Furthermore, the delay recovery rate column 25E stores the recovery rate of the delay time recovered by the corresponding rescheduling (hereinafter referred to as the delay recovery rate), and the cost column 25F stores the cost required for the rescheduling.
[0048] On the other hand, as means for realizing the above-described operation rescheduling support function according to this embodiment, the operation rescheduling support device 2 is provided with a screen display unit 30, a screen operation unit 31, a dispatcher identification unit 32, a transportation disruption acquisition unit 33, a timetable information storage unit 34, a timetable prediction unit 35, a delay recovery rate calculation unit 36, a cost calculation unit 37, an operation rescheduling proposal unit 38, an operation rescheduling information acquisition unit 39, and a communication unit 40, as shown in FIG. 8.
[0049] The screen display unit 30, screen operation unit 31, dispatcher identification unit 32, transportation disruption acquisition unit 33, timetable information storage unit 34, timetable prediction unit 35, delay recovery rate calculation unit 36, cost calculation unit 37, timetable rescheduling plan proposal unit 38 and timetable information acquisition unit 39 are functional units that are realized by the CPU 10 of the timetable rescheduling support device 2 described above in relation to Figure 3 reading out corresponding programs stored in the storage device 12 into the memory 11 and executing them, and the communication unit 40 is a functional unit that conceptualizes the communication function provided by the communication device 15 (Figure 3).
[0050] The screen display unit 30 has the function of acquiring information on the current planned timetable (planned timetable information) from the planned timetable management table 20 (Figure 4) or the changed timetable management table 21 (Figure 4) stored in the database server device 4, and based on the acquired planned timetable information, displaying the train operation timetable of one or more trains described above in Figure 2 on the display device 14 (Figure 3), and also displaying information on operation timetables implemented in the past as operation timetable proposals superimposed on the train operation timetable, as will be described later in Figure 13.
[0051] The screen operation unit 31 also has a function of receiving an operation input made by the commander using the input device 13 (FIG. 3) and outputting necessary commands and information to the corresponding functional units based on the received operation input. For example, the screen operation unit 31 instructs the screen display unit 30 to enlarge, reduce, or move the display screen of the display device 14 in accordance with the operation input made by the commander using the input device 13.
[0052] The controller identification unit 32 has the function of identifying a controller who has logged in by entering an ID and password by referring to the controller information management table 23 stored in the database server device 4, and obtaining information such as the controller's name and years of experience in train rescheduling work from the controller information management table 23 (Figure 5).
[0053] The transportation disruption acquisition unit 33 also has a function of acquiring information about the transportation disruption that triggered the traffic rescheduling. In the following, when a dispatcher carries out traffic rescheduling, it is assumed that various information about the transportation disruption that triggered the traffic rescheduling is input to the traffic rescheduling support device 2, and the transportation disruption acquisition unit 33 acquires the information about the transportation disruption input by the dispatcher. However, the transportation disruption acquisition unit 33 may also automatically acquire information about the transportation disruption from another device.
[0054] The timetable information storage unit 34 has the function of collecting the actual timetables of each train before and after the timetable rescheduling when the timetable rescheduling is implemented, and registering the collected timetable information in the timetable management table 22 before and after the timetable rescheduling of the database server device 4 (Figure 4).
[0055] The timetable prediction unit 35 also has the function of predicting the timetable of each train before and after traffic reordering, based on the timetable information of the actual timetable of each train before and after traffic reordering registered in the timetable management table 22 before and after traffic reordering by the timetable information storage unit 34. Here, the "timetable of each train before traffic reordering" refers to the subsequent timetable predicted for each train in the case where traffic reordering is not carried out after a transportation disruption occurs (hereinafter, these will be referred to as the predicted timetable), and the "predicted timetable of each train after traffic reordering" refers to the subsequent predicted timetable of each train after traffic reordering is carried out. The same applies hereinafter.
[0056] The delay recovery rate calculation unit 36 has a function to calculate the delay recovery rate caused by the rescheduling, based on the planned timetable and the predicted timetables of each train before and after the rescheduling predicted by the timetable prediction unit 35. The cost calculation unit 37 has a function to calculate the cost required for the rescheduling.
[0057] Furthermore, the traffic rescheduling information acquisition unit 39 has a function of acquiring information (information on the revised planned timetable, hereinafter referred to as traffic rescheduling plan information) on the traffic rescheduling plan for the current transportation disruption that the dispatcher has formulated using a traffic rescheduling formulation screen 50 shown in FIG. 13 displayed on the display device 14, which will be described later, via the screen operation unit 31. The traffic rescheduling information acquisition unit 39 generates a planned timetable, which is a train operation plan, based on the acquired traffic rescheduling plan information. update The updated planned timetable is then notified to the timetable management device 3 (FIG. 1) and stored in the changed timetable management table 21 (FIG. 4).
[0058] When a transportation disruption occurs, the timetable replanning proposal proposal unit 38 has a function of proposing to the dispatcher as a timetable replanning proposal information of timetable replanning implemented when a transportation disruption with the same content as the current transportation disruption occurred in the past. In practice, when a transportation disruption occurs, the timetable replanning proposal proposal unit 38 acquires from the timetable replanning information management table 25 the timetable replanning information of timetable replanning implemented when a transportation disruption with the same content as the current transportation disruption occurred in the past, acquired by the transportation disruption acquisition unit 33. The timetable replanning proposal proposal unit 38 then displays the acquired timetable replanning information on the display device 14 via the screen display unit 30 as a timetable replanning proposal for the current transportation disruption.
[0059] (3) Various processes related to the traffic rescheduling support function Next, the details of various processes executed by the timetable replanning support device 2 in relation to the timetable replanning support function described above will be described. (3-1) Traffic rescheduling information registration process Figure 9 shows the flow of a series of processes (hereinafter referred to as the timetable information registration process) executed by the timetable rescheduling support device 2 to register timetable rescheduling information related to the timetable rescheduling in the timetable rescheduling information management table 25 (Figure 7) in the database server device 4 after timetable rescheduling is implemented due to a transportation disruption.
[0060] This timetable rescheduling information registration process is started when the implemented timetable rescheduling is completed. First, the dispatcher identification unit 32, the transportation disruption acquisition unit 33, and the timetable rescheduling information acquisition unit 39 described above with reference to Fig. 3 acquire necessary information (S1).
[0061] Specifically, the dispatcher identification unit 32 obtains the name of the dispatcher who performed the train schedule rescheduling and the number of years of experience in train schedule rescheduling work from the dispatcher information management table 23 (Figure 5) stored in the database server device 4 based on the login information (ID and password) of the dispatcher who performed the train schedule rescheduling at that time.
[0062] The transport disruption acquisition unit 33 also acquires the details of the transport disruption that triggered the rescheduling, which were entered by the dispatcher before the rescheduling began. Furthermore, the traffic rescheduling information acquisition unit 39 acquires, via the screen operation unit 31, traffic rescheduling plan information for the traffic rescheduling that the dispatcher formulated using the traffic rescheduling formulation screen 50, which will be described later with reference to Figure 13, displayed on the display device 14.
[0063] Next, the timetable prediction unit 35 predicts the expected timetables for each train before and after the rescheduling, and based on the predicted timetables for each train before and after the rescheduling, the delay recovery rate calculation unit 36 and the cost calculation unit 37 calculate the delay recovery rate of the train due to the rescheduling and the cost required for the rescheduling (S2).
[0064] Thereafter, the timetable rescheduling information acquisition unit 39 registers the name and years of experience of the dispatcher who performed the timetable rescheduling, the details of the transportation disruption that triggered the timetable rescheduling, details of the timetable rescheduling, the delay recovery rate due to the timetable rescheduling, and the cost required for the timetable rescheduling, acquired as described above, in the timetable rescheduling information management table 25 in the database server device 4 as timetable rescheduling information (S3). This completes the timetable rescheduling information registration process.
[0065] Next, a method for calculating the above-mentioned "delay recovery rate" by the delay recovery rate calculation unit 36 and a method for calculating the above-mentioned "cost required for traffic rescheduling" by the cost calculation unit 37 will be described.
[0066] Figure 10 shows the processing procedure for the delay recovery rate calculation process executed by the delay recovery rate calculation unit 36 in step S2 of the timetable rescheduling information registration process described above with reference to Figure 9. The delay recovery rate calculation unit 36 calculates the delay recovery rate due to the timetable rescheduling implemented at that time according to the processing procedure shown in Figure 10.
[0067] In practice, when the operation rescheduling information registration process proceeds to step S2, the delay recovery rate calculation unit 36 starts this delay recovery rate calculation process, and first obtains the timetable information of the planned timetables of all trains that were scheduled to operate on the day (today) when the operation rescheduling was implemented from the planned timetable management table 20 in the database server device 4, and also obtains the timetable information of each predicted timetable before and after the operation rescheduling of each of these trains predicted by the timetable prediction unit 35 from the timetable prediction unit 35 (S10).
[0068] Next, the delay recovery rate calculation unit 36 selects one train that has not been processed after step S12 from among all trains that were scheduled to operate on the day the rescheduling was implemented (S11), and extracts the timetable information of the planned timetable of the selected train (hereinafter referred to as the first selected train) and the timetable information of the predicted timetable of the first selected train before the rescheduling from the timetable information obtained in step S10 (S12).
[0069] Next, the delay recovery rate calculation unit 36 determines whether it is predicted that the first selected train would have been delayed if the rescheduling had not been implemented, based on the timetable information of the planned timetable extracted in step S12 and the timetable information of the predicted timetable before the rescheduling (S13).
[0070] If the delay recovery rate calculation unit 36 obtains a negative result in this determination, it returns to step S11, and thereafter switches the train selected in step S11 to another train for which step S12 and subsequent steps have not yet been processed, and executes step S12 and subsequent steps.
[0071] In contrast, if the delay recovery rate calculation unit 36 obtains a positive result in the judgment of step S13, it calculates a predicted value for the delay time of the first selected train if the corresponding rescheduling were not made, based on the timetable information of the planned timetable of the first selected train and the timetable information of the predicted timetable before the rescheduling (S14).
[0072] Specifically, the delay recovery rate calculation unit 36 calculates the delay in the predicted arrival time for each stop station by subtracting the time when the first selected train is expected to arrive at that stop station in the planned timetable from the time when the first selected train is predicted to arrive at that stop station in the predicted timetable, and calculates the actual delay time by adding up the delays for all these stop stations.
[0073] Next, the delay recovery rate calculation unit 36 determines whether or not the processing from step S12 onwards has been completed for all trains that were scheduled to operate on the day the train rescheduling was implemented (S15). If the determination returns a negative result, the delay recovery rate calculation unit 36 returns to step S11, and thereafter repeats the processing from step S11 to step S15 while sequentially switching the train selected in step S11 to other trains that have not yet been processed from step S12 onwards.
[0074] Then, when the delay recovery rate calculation unit 36 obtains a positive result in step S15 by completing calculations of the predicted delay times for all trains that were scheduled to operate on the day the rescheduling was implemented, it adds up the delay times for all trains that have been calculated up to that point (S16).
[0075] Next, the delay recovery rate calculation unit 36 selects one train that has not been processed after step S18 from among all trains that were scheduled to operate on the day the rescheduling was implemented (S17), and extracts the timetable information of the planned timetable of the selected train (hereinafter referred to as the second selected train) and the timetable information of the predicted timetable of the second selected train after the rescheduling from the timetable information obtained in step S10 (S18).
[0076] Next, the delay recovery rate calculation unit 36 determines whether or not it is predicted that the second selected train would have been delayed after the rescheduling, based on the timetable information of the planned timetable extracted in step S18 and the timetable information of the predicted timetable after the rescheduling (S19).
[0077] If the delay recovery rate calculation unit 36 obtains a negative result in this determination, it returns to step S17, and thereafter switches the train selected in step S17 to another train for which step S18 and subsequent steps have not yet been processed, and executes step S18 and subsequent steps.
[0078] In contrast, if the delay recovery rate calculation unit 36 obtains a positive result in the judgment of step S19, it calculates a predicted value of the delay time of the second selected train after the corresponding rescheduling based on the timetable information of the planned timetable of the second selected train and the timetable information of the predicted timetable after the rescheduling (S20).
[0079] Specifically, the delay recovery rate calculation unit 36 calculates the delay in the predicted arrival time for each stop station by subtracting the time when the second selected train is expected to arrive at that stop station in the planned timetable from the time when the second selected train is predicted to arrive at that stop station in the predicted timetable, and calculates the actual delay time by adding up the delays for all these stop stations.
[0080] Next, the delay recovery rate calculation unit 36 determines whether or not the processing from step S18 onwards has been completed for all trains that were scheduled to operate on the day the train rescheduling was implemented (S21). If the determination is negative, the delay recovery rate calculation unit 36 returns to step S17, and thereafter repeats the processing from step S17 to step S21 while sequentially switching the train selected in step S17 to other trains that have not yet been processed from step S18 onwards.
[0081] Then, when the delay recovery rate calculation unit 36 obtains a positive result in step S21 by completing calculations of the predicted delay times after the rescheduling for all trains that were scheduled to operate on the day the rescheduling was implemented, it adds up the delay times of all trains that have been calculated up to that point (S22).
[0082] Furthermore, the delay recovery rate calculation unit 36 calculates the recovery rate of train delays recovered by the traffic reordering (delay recovery rate) by dividing the sum of the delay times of each train after traffic reordering calculated in step S22 by the sum of the delay times of each train before traffic reordering calculated in step S16 (S23). Note that the smaller the delay recovery rate calculated at this time, the greater the degree of delay recovery. The delay recovery rate calculation unit 36 then ends this delay recovery time calculation process.
[0083] On the other hand, Fig. 11 shows the processing procedure of the cost calculation processing executed by the cost calculation unit 37 in step S2 of the timetable rescheduling information registration processing described above with reference to Fig. 9. The cost calculation unit 37 calculates the cost incurred by the timetable rescheduling performed at that time according to the processing procedure shown in Fig. 11.
[0084] In practice, when the timetable rescheduling information registration process proceeds to step S2, the cost calculation unit 37 starts this cost calculation process and first reads the timetable change parameter management table 24 (FIG. 6) stored in the database server device 4 (S30).
[0085] Next, the cost calculation unit 37 selects one timetable rescheduling type that has not been processed from step S32 onwards from among the timetable rescheduling types registered in each timetable rescheduling type column 24A (Figure 6) of the timetable change parameter management table 24 read in step S30 (S31).
[0086] Next, the cost calculation unit 37 determines whether or not part or all of the content of the currently implemented timetable rescheduling matches the type of timetable rescheduling selected in step S31 (hereinafter referred to as the selected timetable rescheduling type) (S32). If the cost calculation unit 37 obtains a negative result in this determination, it returns to step S31, and then switches the type of timetable rescheduling selected in step S31 to another type of timetable rescheduling that has not been processed in steps S31 and onwards, and executes the processing from step S32 onwards.
[0087] In response to this, if the cost calculation unit 37 obtains a positive result in the judgment of step S32, it extracts all trains and stations related to the selected type of timetable rescheduling in the current timetable rescheduling from the information about the timetable rescheduling implemented at that time that is temporarily stored in memory 11 (Figure 3) etc. (S33).
[0088] For example, if the selected type of traffic rescheduling is "suspension of service," the cost calculation unit 37 extracts all trains whose services have been suspended and all stations where those trains were supposed to stop. Furthermore, if the selected type of traffic rescheduling is "time change," the cost calculation unit 37 extracts all trains whose times have been changed and all stations where those trains' times have been changed. Furthermore, if the selected type of traffic rescheduling is "car swap," the cost calculation unit 37 extracts all trains whose cars have been swapped.
[0089] After this, the cost calculation unit 37 uses the loss cost calculation parameters stored in the loss cost column 24B (Figure 6) of the record corresponding to the selected timetable rescheduling type in the timetable change parameter management table 24 and the timetable change parameters stored in the power consumption column 24C (Figure 6) to calculate the cost incurred by performing timetable rescheduling of the selected timetable rescheduling type for the trains and stations extracted in step S33 (hereinafter referred to as the selected timetable rescheduling type implementation cost) (S34).
[0090] Specifically, for example, if the selected type of operational rescheduling is "service suspension," the cost calculation unit 37 calculates the amount of loss due to ticket refunds, etc. by multiplying the total number of stations at which each suspended train would have stopped by a loss cost calculation parameter defined for "service suspension." The cost calculation unit 37 also calculates the electricity usage fee avoided by suspending the trains by multiplying the total distance each suspended train would have traveled if it had not been suspended by a power usage calculation parameter. The cost calculation unit 37 then calculates the implementation cost of the selected operational rescheduling type incurred by implementing the selected operational rescheduling type by subtracting the electricity usage fee from the loss amount.
[0091] Furthermore, if the selected type of operational rescheduling is "time change," the cost calculation unit 37 calculates the total delay time of the arrival times of each train that has undergone a time change at each station where it has stopped, and multiplies the calculation result by a loss cost calculation parameter defined for "time change" to calculate the amount of loss in sales caused by users changing to another means of transportation.The cost calculation unit 37 then regards the calculated amount of loss in sales as the selected operational rescheduling type implementation cost incurred as a result of implementing the selected operational rescheduling type.
[0092] Furthermore, if the selected type of timetable rescheduling is "vehicle replacement," the cost calculation unit 37 calculates the cost incurred by the vehicle replacement by multiplying the total number of vehicles that underwent vehicle replacement by a loss cost calculation parameter defined for "vehicle replacement."The cost calculation unit then regards the calculated cost as the selected timetable rescheduling type implementation cost incurred by implementing the selected timetable rescheduling type.
[0093] Next, the cost calculation unit 37 determines (S35) whether or not the processing from step S32 onwards has been completed for all the timetable rescheduling types registered in the timetable change parameter management table 24. If the cost calculation unit 37 obtains a negative result in this determination, it returns to step S31, and thereafter repeats the processing from step S31 to step S35 while sequentially switching the timetable rescheduling type selected in step S31 to other timetable rescheduling types for which step S32 onwards has not been processed.
[0094] When the cost calculation unit 37 finally obtains a positive result in step S35 by completing the processing of steps S32 to S34 for all timetable rescheduling types registered in the timetable change parameter management table 24, it calculates the total value of all selected timetable rescheduling implementation costs calculated up to that point in step S34 as the cost incurred by implementing the corresponding timetable rescheduling (S36).The cost calculation unit 37 then terminates this cost calculation process.
[0095] (3-2) Processing of traffic rescheduling proposals On the other hand, Figure 12 shows the flow of a series of processes (hereinafter referred to as the timetable replanning proposal presentation process) executed by the timetable replanning support device 2 when, due to the occurrence of some kind of transportation disruption, the dispatcher inputs the details of the transportation disruption that has occurred at that time and an instruction to propose a timetable replanning (hereinafter referred to as the timetable replanning proposal presentation instruction) into the timetable replanning support device 2.
[0096] When such an instruction to present a timetable replanning proposal is input to the timetable replanning support device 2, the timetable replanning proposal presentation process is started, and first the timetable replanning proposal proposal unit 38 acquires the details of the transportation disruption that occurred at that time, as input by the dispatcher (S40).
[0097] Next, the timetable rescheduling proposal unit 38 acquires all timetable rescheduling information (timetable rescheduling information) relating to timetable reschedulings that have the same content as the transportation disruption acquired in step S40 from the information (timetable rescheduling information) relating to each timetable rescheduling that has been implemented in the past that is stored in the timetable rescheduling information management table 25 in the database server device 4 (S41).
[0098] Next, if the timetable rescheduling proposal unit 38 has acquired multiple pieces of timetable rescheduling information in step S41, it sorts each piece of acquired timetable rescheduling information in order of priority (conditions) previously set by the dispatcher (S42). Note that the "order of priority (conditions)" here can be, for example, ascending order of power consumption, descending order of cost required for the timetable rescheduling, or descending order of years of experience of the dispatcher who performed the timetable rescheduling.
[0099] After this, the timetable replanning proposal proposing unit 38 sorts each piece of timetable replanning information acquired in step S41 in the order sorted in step S42 and displays them as timetable replanning proposals on the timetable replanning formulation screen 50, which will be described later with reference to Figure 13 (S43). At this time, it may be configured to display only a predetermined number of the top pieces of timetable replanning information sorted in step S42 as timetable replanning proposals. This completes the timetable replanning proposal presentation process.
[0100] (4) Operational rescheduling screen 13 shows an example of the configuration of a timetable rescheduling screen 50 that can be displayed on the display device 14 (FIG. 3) by a predetermined operation. This timetable rescheduling screen 50 is a screen that a dispatcher uses to formulate the details of timetable rescheduling in order to resolve a train schedule disruption caused by a transportation disruption.
[0101] On this operation rescheduling planning screen 50, initially, the train schedule 51 of the train described above in Fig. 2 according to the current operation plan (planned timetable) is displayed on a graph 52. Note that Fig. 13 illustrates an example in which only the train schedule 51 of one train is displayed, but it is also possible to display the train schedules 51 of all trains scheduled to operate on that day superimposed on the graph 52.
[0102] On the train operation rescheduling screen 50, the specific details of the train operation rescheduling can be formulated by extending and / or shifting horizontally the portion of the train operation timetable 51 for each train displayed on the graph 52 that is parallel to the time axis (horizontal axis) that represents the stop times at each station, thereby changing the time and period when the train stops at that station, and the train speed between each station.
[0103] In addition, on the timetable replanning formulation screen 50, a timetable replanning proposal display area 53 is provided at the bottom right of the screen, and one or more timetable replanning proposals 54 selected by the timetable replanning proposal proposal unit 38 through the timetable replanning proposal presentation process described above with reference to Figure 12 are displayed in this timetable replanning proposal display area 53.
[0104] This traffic rescheduling plan 54 includes the name of the dispatcher who has previously performed the corresponding traffic rescheduling, the number of years of experience of the dispatcher in traffic rescheduling work, the details of the traffic rescheduling, the delay recovery rate due to the traffic rescheduling, and the costs incurred due to the traffic rescheduling. This allows the dispatcher to formulate the specific details of the desired traffic rescheduling as described above, while referring to the displayed traffic rescheduling plan 54.
[0105] In addition, the display position of the operation replanning proposal display area 53 within the operation replanning formulation screen 50, the number of operation replanning proposals 54 to be displayed within the operation replanning proposal display area 53, the range of information to be displayed as each operation replanning proposal, whether or not to display operation replanning proposals, and the above-mentioned "priority order" may be freely set or changed at the desired timing.
[0106] Furthermore, the dispatcher can reflect the thus-formulated timetable rescheduling in the current operation plan by performing a predetermined operation. In practice, in response to such a predetermined operation by the dispatcher, the timetable rescheduling support device 2 transmits the updated planned timetable formulated by the dispatcher at that time to the timetable management device 3. Thus, at this time, the timetable management device 3 updates the planned timetable that it manages to the updated planned timetable provided by the timetable rescheduling support device 2, and then controls the operation of each train via the interlocking device 5 in accordance with this updated planned timetable.
[0107] (4) Effects of this embodiment As described above, according to the timetable replanning support device 2 of this embodiment, when a new transportation disruption occurs, the details of timetable replanning implemented when the same transportation disruption occurred in the past are presented as a timetable replanning proposal, along with the delay recovery rate and cost required for that timetable replanning. Therefore, even an inexperienced dispatcher can use the presented timetable replanning proposal as a reference to formulate and implement an appropriate timetable replanning that takes both the delay recovery rate and cost into consideration. Therefore, the timetable replanning support device 2 can support timetable replanning work so that dispatchers can perform appropriate timetable replanning without relying on experience.
[0108] Furthermore, when displaying the information on traffic rescheduling that has been implemented in the past as a traffic rescheduling proposal, the traffic rescheduling support device 2 also displays the name of the dispatcher who implemented the traffic rescheduling and the number of years of experience the dispatcher has in traffic rescheduling work. Therefore, with the traffic rescheduling support device 2, if the dispatcher wants to know the background and reasons for the traffic rescheduling, he or she can identify the dispatcher who implemented the traffic rescheduling and interview the dispatcher directly, which can be expected to improve the dispatcher's autonomous traffic rescheduling work skills.
[0109] (5) Other embodiments In the above-described embodiment, the various functional units for realizing the timetable replanning support function of this embodiment are described as being installed in one computer device (timetable replanning support device 2), but the present invention is not limited to this, and such functional units may be distributed and installed in multiple computer devices that constitute a distributed computing system.
[0110] In addition, in the above-described embodiment, when a new transportation disruption occurs, the information on traffic rescheduling that was implemented when a transportation disruption of the same nature occurred in the past is read from the database server device 4, and the content is displayed as a traffic rescheduling proposal. However, the present invention is not limited to this, and it is also possible to read from the database server device 4 not only traffic rescheduling that was implemented when a transportation disruption of the same nature occurred, but also traffic rescheduling information for similar transportation disruptions (for example, transportation disruptions that occur at nearby stations or sections), and display the content as a traffic rescheduling proposal.
[0111] Furthermore, in the above-described embodiment, the case was described in which the name of the dispatcher who implemented traffic rescheduling when a traffic disruption similar to the one that has occurred this time occurred in the past is displayed on the traffic rescheduling planning screen 50 described above with reference to Figure 13, as identification information of that dispatcher. However, the present invention is not limited to this, and instead of or in addition to the name, identification information such as the dispatcher's ID may be displayed. [Industrial Applicability]
[0112] The present invention can be applied to a train timetable rescheduling support device that supports train timetable rescheduling work. [Explanation of symbols]
[0113] 1...Train operation management system, 2...Train rescheduling support device, 3...Timetable management device, 4...Database server device, 5...Interlocking device, 10...CPU, 14...Display device, 20...Planned timetable management table, 21...Changed timetable management table, 22...Timetable before and after timetable rescheduling management table, 23...Dispatcher information management table, 24...Timetable change parameter management table, 25...Train rescheduling information management table, 30...Screen display unit, 31...Screen operation unit, 32...Dispatcher identification unit, 33...Transportation disruption acquisition unit, 34...Timetable information storage unit, 35...Timetable prediction unit, 36...Delay recovery rate calculation unit, 37...Cost calculation unit, 38...Train rescheduling proposal unit, 39...Train rescheduling information acquisition unit, 50...Train rescheduling formulation screen, 51...Train operation timetable, 54...Train rescheduling proposal
Claims
1. In a train rescheduling support device that supports train rescheduling operations, a delay recovery rate calculation unit that calculates a train delay recovery rate due to train rescheduling implemented in response to the transportation disruption that has occurred; a cost calculation unit that calculates the cost required for the train rescheduling; a storage unit that stores the details of the traffic disruption, the details of the traffic rescheduling implemented for the traffic disruption, the delay recovery rate calculated for the traffic rescheduling, and the cost calculated for the traffic rescheduling as traffic rescheduling information in association with each other; a timetable rescheduling proposal presentation unit that, when a new transportation disruption occurs, reads out the timetable rescheduling information of the timetable rescheduling implemented when a transportation disruption of the same or similar content as the current transportation disruption occurred in the past, and based on the read out timetable rescheduling information, presents to a dispatcher the content of the transportation disruption corresponding to the timetable rescheduling information, the content of the timetable rescheduling implemented for the current transportation disruption, the delay recovery rate calculated for the current timetable rescheduling, and the cost calculated for the current timetable rescheduling; Equipped with The timetable rescheduling proposal presentation unit The system displays the details of traffic rescheduling implemented when a past traffic disruption occurred that is the same as or similar to the new traffic disruption, the delay recovery rate calculated for the traffic rescheduling, and the cost calculated for the traffic rescheduling, as well as the train schedule for all or part of the trains scheduled to operate on that day, so that the details of traffic rescheduling can be formulated by changing the times and time slots when trains stop at each station and the train speed between each station in the train schedule. A traffic rescheduling support device characterized by:
2. The storage unit Further storing a first parameter for calculating the amount of loss that will occur when the operational reordering is implemented, which is preset for each type of operational reordering, and a second parameter for calculating the amount of electricity usage fee that will be saved when the operational reordering is implemented, The cost calculation unit Calculating the cost required for the corresponding operation rescheduling based on the loss amount calculated using the first parameter and the power usage fee calculated using the second parameter.
2. The timetable replanning support device according to claim 1.
3. The traffic rescheduling information includes identification information of the dispatcher who implemented the corresponding traffic rescheduling and / or information on the number of years of experience of the dispatcher in traffic rescheduling work, The timetable rescheduling proposal presentation unit The identification information and / or the number of years of experience based on the train schedule information read from the storage unit are further presented.
2. The timetable replanning support device according to claim 1.
4. The timetable rescheduling proposal presentation unit When the traffic rescheduling information for a plurality of traffic reschedulings is read out from the storage unit, the traffic rescheduling information is sorted in a predetermined order of priority, and the details of the corresponding transport disruption, the details of the traffic rescheduling implemented for the transport disruption, the delay recovery rate calculated for the traffic rescheduling, and the cost calculated for the traffic rescheduling are presented in the sorted order.
2. The timetable replanning support device according to claim 1.
5. A train rescheduling support method executed by a train rescheduling support device that supports train rescheduling work, a first step of calculating a train delay recovery rate due to a train rescheduling implemented in response to a transport disruption that has occurred, and a cost required for the train rescheduling; a second step of associating the details of the traffic disruption, the details of the traffic rescheduling implemented for the traffic disruption, the delay recovery rate calculated for the traffic rescheduling, and the cost calculated for the traffic rescheduling, and storing them as traffic rescheduling information; a third step of, when a new transportation disruption occurs, reading out the traffic reorganization information of the traffic reorganization implemented when a transportation disruption of the same or similar content as the current transportation disruption occurred in the past, and based on the read traffic reorganization information, presenting to a dispatcher the content of the transportation disruption corresponding to the traffic reorganization information, the content of the traffic reorganization implemented for the current transportation disruption, the delay recovery rate calculated for the current traffic reorganization, and the cost calculated for the current traffic reorganization; Equipped with In the third step, the timetable replanning support device The system displays the details of traffic rescheduling implemented when a past traffic disruption occurred that is the same as or similar to the new traffic disruption, the delay recovery rate calculated for the traffic rescheduling, and the cost calculated for the traffic rescheduling, as well as the train schedule for all or part of the trains scheduled to operate on that day, so that the details of traffic rescheduling can be formulated by changing the times and time slots when trains stop at each station and the train speed between each station in the train schedule. A traffic rescheduling support method.
6. The timetable replanning assistance device a first parameter for calculating the amount of loss that will occur when the operational reordering is implemented, which is preset for each type of operational reordering, and a second parameter for calculating the amount of electricity usage fee that will be saved when the operational reordering is implemented; In the first step, the timetable replanning support device Calculating the cost required for the corresponding operation rescheduling based on the loss amount calculated using the first parameter and the power usage fee calculated using the second parameter. The method for assisting traffic rescheduling according to claim 5 .
7. The traffic rescheduling information includes identification information of the dispatcher who implemented the corresponding traffic rescheduling and / or information on the number of years of experience of the dispatcher in traffic rescheduling work, In the third step, the timetable replanning support device The identification information and / or the number of years of experience based on the train rescheduling information is further presented to the dispatcher. The method for assisting traffic rescheduling according to claim 5 .
8. In the third step, the timetable replanning support device The traffic rescheduling information for the plurality of traffic reschedulings is sorted in a predetermined order of priority, and the details of the corresponding transport disruption, the details of the traffic rescheduling implemented for the transport disruption, the delay recovery rate calculated for the traffic rescheduling, and the cost calculated for the traffic rescheduling are presented to the dispatcher in the sorted order. The method for assisting traffic rescheduling according to claim 5 .
Citation Information
Patent Citations
Manufacture of high strength ceramic sintered body
JP1987072551A
Circuit board work system and state setting method
JP2003046299A
Operation arrangement apparatus in operation management system
JP2008222004A
Operation arrangement support device and operation arrangement system using the device
JP2011111058A
Operation arrangement support system and method thereof
JP2011173530A